* Haines Brown (brownh@hartford-hwp.com) [030506 20:29]: > ...the following configuration: > > title debian 2.4.18-686 > root (hd0,0) > kernel /vmlinuz-2.4.18-686 root=/dev/sdb1 > initrd (hd1,0)/initrd.img-2.4.18-686 > > is not looking for vmlinuz-2.4.18-686 in debian's /boot directory > (hd1,0), but in RedHat's (hd0,0). Well, yeah. That's precisely what it says. =) Use root (hd1,0) or kernel (hd1,0)/vmlinuz-2.4.18-686 root=/dev/sdb1 Actually, I thought you said that your kernel resides under /boot on your / partition ((hd1,0)), so you'd need: kernel (hd1,0)/boot/vmlinuz-2.4.18-686 root=/dev/sdb1 initrd (hd1,0)/boot/initrd.img-2.4.18-686 My understanding was that this should work instead: title debian 2.4.18-686 root (hd1,0) kernel /boot/vmlinuz-2.4.18-686 root=/dev/sdb1 initrd /boot/initrd.img-2.4.18-686 But earlier in the thread others have said that it wouldn't. > When I reboot, I gather that grub's root command not only specifies > grub's root device and partition, but mounts it so files can be read > (this a rough summary of a grum manual). This is open to several > interpretations, I think. "Root" for grub is its own parent directory > (/boot). Then it is mounted so that files (the kernel I assume) can be > read. It may be that root is enabling grub to find the kernel in its > own (RedHat) /boot directory, but not Debian's. I'll give this a try: > > root (hd1,0) > > but not optimistic things are so simple. Your reading of the manual is my understanding as well. Give it a try. I think it will work, and it will be the simplest/cleanest way, if it does. good times, Vineet -- http://www.doorstop.net/ -- "Great spirits have always found violent opposition from mediocre minds. The latter cannot understand it when a man does not thoughtlessly submit to hereditary prejudices but honestly and courageously uses his intelligence." -- Albert Einstein
Attachment:
pgpK6eOxW6GBe.pgp
Description: PGP signature