Why is the Linux boot sequence is organized the way it is?
Power on + BIOS runs hardware initialisation and self tests, LILO/GRUB etc... but why is it organised the way it is?
Would I be right saying it is primarily for debugging purposes?
migrated from stackoverflow.com Jan 6 '11 at 16:19
This question came from our site for professional and enthusiast programmers.
That is not specifically the Linux boot sequence. That is how the original IBM PC system worked and the PC you're currently using is just an evolved version of that original system due to people putting too much importance on backwards compatibility.
Lots of computers that does not need to be backwards compatible to the IBM PC architecture boot Linux differently. My handphone boots directly into U-Boot which then boots Linux. No BIOS there. Same as my web/SAN server which is ARM based. It boots directly into Redboot which then boots Linux. No BIOS. Google Chrome OS is rumored to have even gotten rid of bootloaders altogether and boots directly into a Linux kernel burned into the first address of memory.
In short, it's mostly legacy junk. There is no real good reason current hardware work the way they do except that if they work differently they won't be able to boot Windows.