Ollie
I think your message got chopped off. Were you saying that linuxbios could
host the tiara forth code, i.e. boot sequence is linuxbios loads tiara,
then tiara loads linux?
One thing I do want to preserve is the ability to boot linux out of flash.
I am working now with the Alpha cluster that uses linuxbios+scyld to do
this and it is quite heavenly. I am going to have something like 1024 or
more machines which need to boot with no user interaction at all. Also,
there is some exotic hardware here that I want my bootstrap to use on
boot, such as Myrinet, GigaNet, Gig-E, SCI, and Quadrics; I would rather
use the Linux drivers for these than write ones for tiara, not to mention
the problem of non-bootp-style boot protocols.
So maybe what I'd like to have as options:
1. linuxbios -> tiara -> boot linux from flash
2. linuxbios -> boot linux from flash
3. linuxbios -> tiara -> interact with tiara, boot os of choice
(including flash as an option)
4. linuxbios -> boot linux from flash ->
interact with tiara embedded in linux -> boot os of choice
That last option is kind of interesting to me. It gets all the linux
drivers, network protocols, and file systems while also allowing the
option of a tiara-style interactive boot. Can tiara be embedded in linux?
comments?
ron
