Timeline for How did Linux/xBSD boot before GRUB?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 9, 2019 at 11:37 | comment | added | bodgit | @JörgWMittag this neat feature allowed a few Mac-flavoured PCI devices to work in Sun workstations if you didn't want to pay for an equivalent Sun-branded device. IIRC Adaptec and Matrox made such things although the Mac-flavoured version was generally scarcer than its PC sibling | |
| Jan 8, 2019 at 14:21 | comment | added | Stephen Kitt | @炸鱼薯条德里克 NTLDR can chainload any boot sector; so you can use it with Grub, or LILO, to boot Linux — and ISTR using a simpler boot sector back in the day, without Grub or LILO (that was nearly twenty years ago, I don’t remember the exact details; I have the setup on tape somewhere but I’d have to dig it out). | |
| Jan 8, 2019 at 14:13 | comment | added | Jörg W Mittag | GRUB can operate in a similar way, but the difference is that all those drivers have to be written specifically for GRUB, whereas the beauty of OFW was that the device would bring its drivers with it, which means that even devices that didn't yet exist when the OFW environment was written would just "magically" work. UEFI can also operate in a similar way, but its "portable bytecode format" is essentially a subset of DOS, which is the main reason why Itaniums still need an x86 emulator. | |
| Jan 8, 2019 at 14:10 | comment | added | Jörg W Mittag | E.g. you could have RAID adapter which has its OpenFirmware driver inside a ROM chip, then the OpenFirmware environment could use that driver to access the RAID, inside the RAID, there could be another driver for the partition table format, which would allow the OFW environment to find the partitions, at the beginning of each partition would be an OFW driver for the filesystem, which would allow the OFW system to find the kernel, and the kernel would have a small bootloader written in OFW bytecode at the beginning. | |
| Jan 8, 2019 at 14:07 | comment | added | Jörg W Mittag | @slebetman: More precisely, OpenFirmware was developed by Sun for SPARC and then adopted by the PowerPC alliance (IBM, Apple, Motorola) for the PowerPC Reference Architecture, and specifically by Apple for PowerPC-based Macintoshs. One of the powerful aspects was that simple drivers could be stored inside ROM chips on the expansion cards, or in some designated boot area of a HDD, and since they were written in bytecode against a known specified ABI, they would work regardless of which CPU architecture and OS you were trying to boot. | |
| Jan 8, 2019 at 4:09 | comment | added | 炸鱼薯条德里克 | Hey, just curious, NTLDR can load linux kernel directly? I heard that NTLDR can chainloader grub4dos and then load the linux kernel. | |
| Jan 8, 2019 at 1:21 | comment | added | slebetman | The PowerPC architecture is also interesting because some motherboards had a Turing-complete BIOS - Openfirmware (basically the Forth programming language with some preinstalled functions). This allowed booting directly from BIOS without bootloader if you know how to configure your BIOS | |
| Jan 7, 2019 at 12:26 | history | edited | Stephen Kitt | CC BY-SA 4.0 |
Current kernels can boot from EFI, and there's U-Boot too.
|
| Jan 7, 2019 at 12:18 | history | answered | Stephen Kitt | CC BY-SA 4.0 |