[LinuxBIOS] Names names.. [was: Linux vs. Open?]
cro_marmot at comcast.net
Tue Mar 15 07:21:32 CET 2005
HASH - Hardware And SHit
"LinuxBIOS begins in the HASH stage where it initializes the memory
controller and CPU, scans system busses, etc. before booting a payload."
We could call the bootloader stage BASH, external ROMs (SCSI, VGA) RASH,
and any other software SASH. The -ASH ending is incredibly versatile.
Or if you prefer names without profanity:
HIC: Hardware initialization code
HEC: Hardware enabling code
MIR: Mainboard Initialization Routines
MIS: Mainboard Initialization Stuff
NAB: Not A Bootloader
NAP: Not A Payload
I'm still not entirely clear on why a new acronym is necessary, though.
Perhaps we should try to clear up the definition of the word "payload"
more than using another acronym to describe what is meant by the word
"BIOS" since BIOS is already sort of a generic term for a wad of
hardware initialization routines. Then we can explain why "Linux" is in
the name of the project. Or perhaps the solution would be to change the
name of the project back to FreeBIOS. If not that, we can call it
Minnich's BIOS (Since it rhymes with LinuxBIOS) and pray that nobody
calls it MinixBIOS :)
On Mon, 14 Mar 2005 19:00:06 -0800
Nathanael Noblet <nathanael at gnat.ca> wrote:
> On Mar 14, 2005, at 6:38 PM, Bari Ari wrote:
> > Peter Stuge wrote:
> >> I would like to have a name for the part that isn't the payload.
> >> Suggestions? I've called it "the initialization part|code" but I
> >> don't like that too much.
> > How about Pre Payload Environment - PPE? Since PXE is already taken.
> Basic System Initialization
> [Basic] Memory Hardware Initialization
> Hardware Discovery [Environment | Phase]
> Nathanael D. Noblet
> Gnat Solutions
> 204 - 131 Gorge Road E
> Victoria, BC V9A 1L1
> T 250.385.4613
> C 250.893.4613
> LinuxBIOS mailing list
> LinuxBIOS at openbios.org
More information about the coreboot