Herbert Xu <[EMAIL PROTECTED]> wrote:
> Why are you trying to use initrd anyway? It's much easier to build
> the drivers into the kernel.
Now, I must agree with that.
At the begining, it looked as a good idea to compile one kernel which
can be used on scsi and ide systems, etc. S
Jean Charles <[EMAIL PROTECTED]> wrote:
> There no ext2 nor ext3 modules on your initrd.img-2.4.22-pre3c0, are
> those filesystems compiled in the kernel ?
ext2 is compiled in the kernel:
CONFIG_EXT2_FS=y
After a few days, let me summarise:
a) 2.4.21 kernel as it is in debian kernel-sour
On # Mon, 7 Jul 2003 13:38:35 -0400, Matt Zimmerman wrote:
>> RAMDISK: cramfs filesystem found at block 0
>> RAMDISK: loading 1032 blocks [1 disk] into ram disk... done.
>> Freeing initrd memory: 1032k freed
>> cramfs: wrong magic
>> Kernel panic: VFS: Unable to mount root
> Since it is a moving target, kernel compilation is a difficult
> subject that may confuse even the most admired developer:
> [Debian Reference]
What is the status of initrd kernel building process (only on i386),
while using stock kernels (from kernel.org)?
Kernel-source-2.4
4 matches
Mail list logo
