> > goes on and off of the 1394 drive. > > This page looks useful: > > http://www.ibiblio.org/peanut/initrd$.txt > > Basically, an initrd is good for loading the drivers you need to complete > the boot process. I don't know if it'll work for your situation, but > another solution that often works is just to build the kernel with the > necessary drivers hardwired in (a choice you make when configuring the > kernel). Such a kernel can then find the devices and immediately mount > the desired root device, without requiring the intermediate step of > booting into an initrd and then swapping in a new root drive. >
Nathan, You're suggestion was my original thought, but there seems to be a difference of opinion in the 1394 developers arena as to whether the 1394 drivers can be built into the kernel and actually work. There are apparently issues about when, in the boot process, SCSI support comes up, and when the 1394 bus is actually scanned to find the drives. I'm going to try this out, I think, as it seems straight forward, with the understanding that it just might not work. The thing I'm very unclear about is where, physically, the '/' directory is. Is this actually on the EIDE drive? Or is in in memory only? Or is it in memory only when you use an initrd? (I think this is the case...) If it resides in memory, then the EIDE drive /boot partition could be mounted to it, but so could the 1394 /usr, /home, and other partitions, if the system can find them. And the system needs to find them to find other modules that are in /lib/modules/... It's an interesting problem and a good opportunity to finally get into understanding how this works, at least logically. Thanks, Mark -- [EMAIL PROTECTED] mailing list
