I figured some things out... SOME.... I modified the kernel to answer the questions for me :)
So now I have Oxygen booting with a standard Linux kernel - very nice. Too bad that the initrd_archive patch seems to be going away... On 12/28/01 at 12:45 AM, David Douthitt <[EMAIL PROTECTED]> wrote: > After reading initrd.txt yet again.... I still don't understand when > /linuxrc is run, and reading the source doesn't help, and reading > kernel source documentation books don't help either. > > I'm working with a Linux 2.2.20 kernel with > CONFIG_BLK_DEV_INITRD set to "y", and with Openwall > patches loaded and NO LRP patches at all. > > Questions I have that I need answers for: > > 1. What is the value of ROOT=? Kernel sources and > initrd.txt imply it should be /dev/ram, but I'm not sure > why. This was the BIG trip up; ROOT= must NOT be /dev/ram or /dev/ram0, but anything else. initrd.txt never says this... in fact, initrd.txt never considers the fact that it might be used for a floppy-based Linux... > 2. How does all of this interact with the kernel value returned by > rdev? Apparently, ROOT= overrides the rdev value - so, essentially, they operate as the same value. This suggests that the ROOT= parameter is not needed at all in an unpatched kernel environment, unless /linuxrc uses it. Oxygen now writes to /proc/sys/kernel/real-root-dev the value 0x101 - /dev/ram1 - so the rdev value could be anything except /dev/ram0 or /dev/ram. > 4. Does it matter whether a zImage or bzImage is made? I > thought not - but then initrd.txt implies that it matters, > as there is a "bzImage+initrd" patch alluded to... I'm not sure, but I switched to zImage right after the first mail went out - and it works... -- David Douthitt UNIX Systems Administrator HP-UX, Unixware, Linux [EMAIL PROTECTED] _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
