Eric,
Are you adding features to filo?
I hope it can 1. understand grub.conf in HD --- and append console=tty0 console=ttyS0,115200 automatically 2. understand Linux Installation CD: /boot/loader/isolinux.cfg --- and append console=tty0 console=ttyS0,115200 automatically 3. editor to boot command line 4. auto items for elf image in rom ( 64k or 32k segement from 0xfff80000) mem@0xfff80000 mem@0xfff90000 mem@0xfffa0000 mem@0xfffb0000 ....
Regards
YH
YhLu YhLu@tyan.com writes:
Eric,
Are you adding features to filo?
I've thought about it but I don't have the time at the moment :(
I hope it can
- understand grub.conf in HD --- and append console=tty0
console=ttyS0,115200 automatically
It currently does not look at any configuration files.
- understand Linux Installation CD: /boot/loader/isolinux.cfg --- and
append console=tty0 console=ttyS0,115200 automatically
Nope it does not do that either.
- editor to boot command line
It does have that.
- auto items for elf image in rom ( 64k or 32k segement from 0xfff80000) mem@0xfff80000 mem@0xfff90000 mem@0xfffa0000 mem@0xfffb0000 ....
That is certainly a sane idea.
Eric
On Tue, Apr 13, 2004 at 09:50:55AM -0700, YhLu wrote:
I hope it can
- understand grub.conf in HD --- and append console=tty0
console=ttyS0,115200 automatically 2. understand Linux Installation CD: /boot/loader/isolinux.cfg --- and append console=tty0 console=ttyS0,115200 automatically
I don't like the idea to have compatibility to existing bootloaders. It sounds like a beginning of nightmare.
Instead, Linux CDs can directly support FILO. Boot CDs can have /boot/filo.conf, and installers can generate /boot/filo.conf in the installed hard disk. It's technically easy. Stefan Reinauer was positive to add this support to SuSE's installation CD when I talked to him about this issue.
- editor to boot command line
It already has very limited editor.
- auto items for elf image in rom ( 64k or 32k segement from 0xfff80000) mem@0xfff80000 mem@0xfff90000 mem@0xfffa0000 mem@0xfffb0000 ....
Maybe, we can make FILO to have the default config file in ROM, which includes the filo.conf from boot device (CD or HD). So the config file in ROM knows how to boot Etherboot in ROM. But this is too complicated at the moment.
-- Takeshi
On Thu, 15 Apr 2004, Takeshi Sone wrote:
On Tue, Apr 13, 2004 at 09:50:55AM -0700, YhLu wrote:
I hope it can
- understand grub.conf in HD --- and append console=tty0
console=ttyS0,115200 automatically 2. understand Linux Installation CD: /boot/loader/isolinux.cfg --- and append console=tty0 console=ttyS0,115200 automatically
I don't like the idea to have compatibility to existing bootloaders. It sounds like a beginning of nightmare.
yes.
I really am not enthusiastic about turning filo back into grub.
ron
* ron minnich rminnich@lanl.gov [040414 23:34]:
I really am not enthusiastic about turning filo back into grub.
I think the idea is great, honestly. The menu/user interface code is not grub's weakness. Neither is the config file syntax. What started out with a half-ways clean design was just featurized beyound reusability.
Stefan
* Takeshi Sone ts1@tsn.or.jp [040414 17:37]:
On Tue, Apr 13, 2004 at 09:50:55AM -0700, YhLu wrote:
I hope it can
- understand grub.conf in HD --- and append console=tty0
console=ttyS0,115200 automatically 2. understand Linux Installation CD: /boot/loader/isolinux.cfg --- and append console=tty0 console=ttyS0,115200 automatically
I don't like the idea to have compatibility to existing bootloaders. It sounds like a beginning of nightmare.
Not necessarily. One could do this modular, just like the sound drivers are now.. :)
Instead, Linux CDs can directly support FILO. Boot CDs can have /boot/filo.conf, and installers can generate /boot/filo.conf in the installed hard disk. It's technically easy. Stefan Reinauer was positive to add this support to SuSE's installation CD when I talked to him about this issue.
For the user interface, one could go the way with modular code, too. Elilo, the EFI boot loader, does a nice thing there. It has a "chooser" interface, allowing several user interfaces. Each user interface has a name, a probe function and a choose function. The probe function can check whether the current chooser works on the current machine (on Itanic this could be checking UGA availability before trying to show a graphical menu)
Maybe, we can make FILO to have the default config file in ROM, which includes the filo.conf from boot device (CD or HD). So the config file in ROM knows how to boot Etherboot in ROM. But this is too complicated at the moment.
How would that config file have to look? Something similar to the grub menu.lst would be fitting, wouldn't it?
title Linux kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 console=ttyS0,115200n8 initrd (hd0,0)/boot/initrd
Stefan
On Fri, Apr 16, 2004 at 02:10:29PM +0200, Stefan Reinauer wrote:
For the user interface, one could go the way with modular code, too. Elilo, the EFI boot loader, does a nice thing there. It has a "chooser" interface, allowing several user interfaces. Each user interface has a name, a probe function and a choose function. The probe function can check whether the current chooser works on the current machine (on Itanic this could be checking UGA availability before trying to show a graphical menu)
That sounds nice.
Maybe, we can make FILO to have the default config file in ROM, which includes the filo.conf from boot device (CD or HD). So the config file in ROM knows how to boot Etherboot in ROM. But this is too complicated at the moment.
How would that config file have to look? Something similar to the grub menu.lst would be fitting, wouldn't it?
title Linux kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 console=ttyS0,115200n8 initrd (hd0,0)/boot/initrd
Similar, but not the same. Grub has many commands that FILO would never understand.
-
ebiederman＠lnxi.com -
ron minnich -
Stefan Reinauer -
Takeshi Sone -
YhLu