Jonathan Dieter wrote: > On Sat, 2007-10-20 at 12:00 -0500, Les Mikesell wrote: >> Jonathan Dieter wrote: > >>> The other thing you might try would be to use Rom-o-matic to generate an >>> etherboot floppy image for your network card and write it to a small >>> (~1MB) partition on your hard drive. Then, in Grub do the whole >>> rootnoverify(hd0,x), chainloader +1 and see how that works. I haven't >>> actually tried this method, but it seems that it should work. >> Going this route, I'd rather not have to dedicate a partition. Is there >> any way to put it in /boot along with a linux boot setup? > Etherboot will produce bootable floppy images. I don't remember for sure, but I believe it will also produce a Grub loadable image just like Memtest86 does. Chainloading to the floppy image should work, but if it will produce a directly loadable file, that would be better. > As far as I can tell, no. Grub is able to grab files from a filesystem, > but I don't think it can set its root device to be a file. > The Grub root device is where the base of where it looks for the file. According to the manual, you can use a file name in the chanloader command, or specify where to read from, and how much to read. So something like "chainloader boot.img" should work. I believe there was a thread on this before where we were using a floppy image designed to let you boot from a CD on systems where the BIOS did not support it to give Grub a boot from CD option. You may want to look at Grub network support. There is supposed to be a PXE stage 2 image for Grub. You can then select the boot image from the server. It did not say, but I suspect it will also let you boot from the local drive. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
Attachment:
signature.asc
Description: OpenPGP digital signature
