> 
> > LinuxBIOS + TIARA combination will be a rescue for them. This will
> > immediately multiply the user base of LinuxBIOS since most people on
> > the list are asking about how to get a DoC or M/B with 32 DIP socket.
> 
> I think that makes sense. 
> 
> So are you doing this or am I or can we convince someone to do it?
> 
I think we can take it on here at UMD.  We've been looking into ways to
get LinuxBIOS down below 512KB, and this may be the ticket.  Let us look
into it a bit, and get back to the list.

Also to avoid confusion, I'd like to propose a renaming of the base init
code either back to OpenBIOS or perhaps OpenInit.  Calling it LinuxBIOS
may cause confusion, i.e.

        Flash                                   Net/IDE/SCSI
        -----                                   ------------
Open[BIOS/Init]->LinuxBIOS
Open[BIOS/Init]->TIARA-------------------------->OS of choice

BTW- Now's probably a good time to make a preliminary announcement about
what we'll be doing here at UMD.  We were just notified that we'll be
receiving a two year contract from DARPA to add assurance to the
bootstrap. This means we'll be adding integrity checks as well as support
for crypto using both HW and SW.  We'll also be working on trying to
increase the supported base as well (more details on that later when talks
with a major vendor are completed). I know what your saying now- you've
done all of this great work to speed up the boot process and the security
guys come in and slow it down. :-)  Our plan is to make it a compile time
options for those that what higher assurance.

DARPA's support means that we'll have three graduate and one undergrad
working on the project. We'll have a web page up in a few weeks that will
provide the exacting details.

Bill

-------------------------------------------------------------------
Bill Arbaugh                                    www.cs.umd.edu/~waa
University of Maryland                               [EMAIL PROTECTED]
College Park                                           301.405.2774
-------------------------------------------------------------------

Reply via email to