Before being merged with the commitdc6e1f32c1
("Import website-build to build the GNU Boot website."), website-build was a separate git repository. And so, even after the merge, until the commit20d122e94a
("website-build: use website from local git repository."), it still worked in the same way and still downloaded the website from git. This prevented merging the website and website-build directories together as the GNU Boot repository also needed to be a valid Untitled website repository as well. Now after this commit, the website is built from the same git tree, so we can simply adjust the build scripts to be able to move things around. In addition of making things more clear for contributors, it also simplify the migration to haunt as with haunt we typically have the haunt.cfg (and the autotools build code if needed) code in the top directory and the markdown files in a subdirectory. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> Acked-by: Adrien 'neox' Bourmault <neox@gnu.org>
3.6 KiB
title | x-unreviewed |
---|---|
BSD operating systems | true |
It is highly recommended that you use the SeaBIOS payload. ROM images are available in the latest Libreboot release, which start with the SeaBIOS payload.
The ROM images with GNU GRUB also have SeaBIOS available in the boot menu.
GNU GRUB, when compiled as a coreboot payload, runs on bare metal and it can
boot any other coreboot payload if you use the chainloader
command.
The way to use SeaBIOS is fairly self-explanatory. SeaBIOS functions the way you would expect on a typical computer. Libreboot currently lacks any sort of documentation for SeaBIOS, but you can refer to their website: https://seabios.org/SeaBIOS
SeaBIOS is especially recommended if you're doing an encrypted installation.
The benefit to using SeaBIOS is that it's basically more reliable. For example, ZFS support is less reliable in GRUB, but a FreeBSD system booted in SeaBIOS would work just fine because you'd be using FreeBSD's own bootloader in that instance.
GNU GRUB payload
GRUB can directly boot many BSD kernels, but support for this is quite unreliable compared to its support for booting Linux kernels. However, you can use GRUB.
When you use GNU GRUB directly, in this way, the various BSD bootloaders are bypassed entirely.
We have separate pages for each BSD system: