Starting a new thread on the FILO subject because it isn't really about "BIOS" stuff anymore. What about this theory. FILO searches for a filo.conf file on the first drive it finds in the first partition root directory. If it does not find filo.conf it prompts the user for a configuration. At the end, it prompts the user if they want to save it and writes a new filo.conf file to the first drive it finds in the first partition root directory. This way the next time you boot the configuration (filo.conf) is found, it has a timeout for user intervention (to add/change the configuration, or manually boot) and it boots that config.
Joseph Smith wrote:
FILO searches for a filo.conf file on the first drive it finds
Scanning for drives has been considered before but always dismissed because it will potentially take a very long time for FILO to start if it needs to wait for drives to start.
As an optional feature, everyone pretty much said they want to be able to do such a drive scan only a few days ago. Would be great if you want to hack on it! :)
//Peter
On Thu, 11 Sep 2008 23:07:32 -0400, Joseph Smith joe@settoplinux.org wrote:
Starting a new thread on the FILO subject because it isn't really about "BIOS" stuff anymore. What about this theory. FILO searches for a filo.conf file on the first drive it finds in the first partition root directory.
If
it does not find filo.conf it prompts the user for a configuration. At
the
end, it prompts the user if they want to save it and writes a new filo.conf file to the first drive it finds in the first partition root directory. This way the next time you boot the configuration (filo.conf) is found,
it
has a timeout for user intervention (to add/change the configuration, or manually boot) and it boots that config.
Just wanted to add that this method would also cut us free from using any other kind of Boot Manger (GRUB). We wouldn't have to deal with any legacy "BIOS" stuff. I think it would simplify things greatly.
Joseph Smith wrote:
Just wanted to add that this method would also cut us free from using any other kind of Boot Manger (GRUB).
FILO is already independent of GRUB.
We wouldn't have to deal with any legacy "BIOS" stuff.
We already do not deal with any legacy BIOS stuff in FILO.
I think it would simplify things greatly.
Yes, it does.
//Peter
Ok then it is settled. This is my direction on this. If anyone else has any thooughts on this, please share.