[lkml]   [2000]   [Nov]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectlinux 2.4.0-test9

Linux 2.4.0-test9 can be built and booted via initrd when running
a 2.2.17 kernel.

However when running, the new kernel 2.4.0-test9, can't be used to
make a usable initrd ram disk. The result being that 2.4.0-test9
can't, itself, build an "initrd" bootable system.

Before everybody screams that I don't know what I'm doing, let me
assure you that I know that the two kernels put their modules in
different directories and the new directory scheme seems to require
the latest and greatest version of modutils.

I have two ways of building an initial RAM disk (they both use
scripts, not provided with any distribution). One uses the loop-device
and the other uses the RAM disk directly. Because of previous
problems, on some kernel versions, with the loop device (it was
being mucked with for encription), I exclusively use the RAM disk
to build initrd.

Therefore, the problem seems to be that 2.4.0-test9 has a problem
with the RAM Disk.

Dick Johnson

Penguin : Linux version 2.2.17 on an i686 machine (801.18 BogoMips).

"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:45    [W:0.135 / U:0.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site