The current ide_disk part in Etherboot only scan 10 (???) sectors from /dev/hda header. So the user muse cat boot.elf /dev/hda, I have modified Etherboot source code to scan more sectors so it can find elf in /dev/hda1. (the /dev/hda1 should be physical partition 1). The Linux Distribution is installed from /dev/hda2. then I can use kernel and initrd in /boot to produce elf and cat that in /dev/hda1. After that, I can boot from NIC or HD via cmos conf.
The Etherboot group seems to stop enhancing the ide_disk part. I think maybe because
In normal bios, when booting Etherboot with ASK_BOOT, and using Q can exit from Etherboot and back into BIOS, then can boot into HD and use HD
bootloader.
And most users of Etherboot are from Normal BIOS ???? ( they don't like pxe ??)
How much works need to done to put filo in Etherboot for LinuxBIOS users?
PS: Nobody in PPC is using Etherboot???
Regards
YH
-----邮件原件----- 发件人: Greg Watson [mailto:gwatson@lanl.gov] 发送时间: 2004年4月3日 17:29 收件人: Yinghai Lu 抄送: 'SONE Takeshi'; 'Eric W. Biederman'; linuxbios@clustermatic.org 主题: Re: 答复: FILO 0.4 [PMX:#]
Yeah sorry, I kind of did that by stealth. Ron and I get lots of requests from people wanting to use LB but who don't know how to deal with the payload issue. We decided that it would be really nice to have a simple bootloader that understands some basic filesystems built into LB. That way people can get going without having to deal with etherboot or FILO directly. A nice side effect is that it simplifies the FILO code significantly - in fact the only code that is really required is the filesystem support. Also, another major plus is that the code supports PPC as well as x86. Up to now I've had no bootloaders (etherboot or FILO) that work on PPC.
Greg
On 03/04/2004, at 4:56 PM, Yinghai Lu wrote:
It seems someone (Greg ???) merge FILO into the LinuxBIOS hardwaremain.c and it is can be loaded instead of elfboot.
In normal bios, when booting Etherboot with ASK_BOOT, and using Q can exit from Etherboot and back into BIOS, then can boot into HD and use HD bootloader.
In LinuxBIOS, if LinuxBIOS is using elfboot to boot Etherboot elf, when Q from Etherboot, should continue to do the code after elfboot. So may put the filo after elfboot.
But I think the best way is merged filo into Etherboot instead of Linuxbios directly. Then We can use tg3-fs_stream.zelf or tg3_filo.zelf as payload of LinuxBIOS.
It is more better if filo support boot loader (lilo) in HD.
Regards
Yinghai Lu
-----邮件原件----- 发件人: linuxbios-admin@clustermatic.org [mailto:linuxbios-admin@clustermatic.org] 代表 Eric W. Biederman 发送时间: 2004年4月3日 13:02 收件人: SONE Takeshi 抄送: linuxbios@clustermatic.org 主题: Re: FILO 0.4
SONE Takeshi ts1@tsn.or.jp writes:
I just released FILO 0.4. http://te.to/~ts1/filo/
I'll work on config file support next time.
Is this work still ongoing? At first stab at a config file could hard code it's location like you currently do the kernel image.
Another question listing files. Currently you have that support completely removed from the Grub code. Any thoughts on adding that.
Eric _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios