diff --git a/site/docs/build/index.md b/site/docs/build/index.md index 7b7a9e5..b324b91 100644 --- a/site/docs/build/index.md +++ b/site/docs/build/index.md @@ -15,11 +15,6 @@ images (containing payloads) in `bin/`. This design is more efficient, and permits many configurations without needless duplication of work. More info is available in the [lbmk maintenance manual](../maintain/)** -Also, this page currently only refers to the build system as it exists -in `lbmk.git`. A massive re-design of lbmk has been in progress, since the -Libreboot 20230625 release. When the next version after 20230625 comes out, -this page will once again match the current tarball release. - Introduction ============ @@ -37,10 +32,25 @@ This version, if hosted live on libreboot.org, assumes that you are using the `lbmk` git repository, which you can download using the instructions on [the code review page](../../git.md). -If you're using a release archive of libreboot, please refer to the -documentation included with *that* release. libreboot releases are only intended -as *snapshots*, not for development. For proper development, you should always -be working directly in the libreboot git repository. +A note about documentation (and this page) +------------------------------------------ + +From Libreboot 20231021 onwards, *all* releases (including 20231021) +have `lbwww.git` (the website) and `lbwww-img.git` (images for the website) +archived in the *src* tar archive for that release; older releases were hit +or miss, from 20210522 to 20230625, as to whether they came with documentation; +releases older than 20210522 generally always came with documentation. Modern +Libreboot documentation is written in Markdown (pandoc variant) + +If you're working with *release* documentation, you don't get the full HTML +files (such as the one you're viewing now, if you're reading *this* page in a +web browser), so either read the Markdown files directly, or compile them to +HTML using the [Untitled Static Site Generator](https://untitled.vimuser.org/) +(which is what the Libreboot project uses to generate HTML from those files). + +NOTE: `av.libreboot.org` is hardcoded as the domain name where images are +pointed to, in `lbwww.git`, so you will need to replace these references in +your local version, unless you're happy to just continue using those. Git === @@ -76,14 +86,17 @@ On Fedora, you can use the following sudo dnf install python-unversioned-command -Building Libreboot -================== +How to compile Libreboot +======================== -Actual development/testing is always done using `lbmk` directly, and this +Actual development/testing is always done using lbmk directly, and this includes when building from source. Here are some instructions to get you started: -libreboot includes a script that automatically installs build dependencies +First, install build dependencies +--------------------------------- + +Libreboot includes a script that automatically installs build dependencies according to the selected linux distro. The currently supported distros are: Debian/Ubuntu/Linux Mint/Pop!\_OS, Fedora, Arch Linux/Parabola or Void Linux. @@ -115,7 +128,10 @@ Technically, any Linux distribution can be used to build libreboot. However, you will have to write your own script for installing build dependencies. -libreboot Make (lbmk) automatically runs all necessary commands; for +Next, build ROM images +---------------------- + +Libreboot MaKe (lbmk) automatically runs all necessary commands; for example, `./build roms` will automatically run `./build grub` if the required GRUB payload (under `elf/grub/`) does not exist. @@ -132,6 +148,9 @@ or get a list of supported build targets: ./build roms list +Or maybe just build payloads? +----------------------------- + If you wish to build payloads, you can also do that. For example: ./build grub @@ -145,6 +164,17 @@ individual parts of the build system manually, if you choose. This may be beneficial when you're making changes, and you wish to test a specific part of lbmk. +Want to modify Libreboot? +------------------------- + +Check the [lbmk maintenance manual](../maintain/) for guidance. You may for +example want to modify a config, e.g.: + + ./update trees -m coreboot x200_8mb + +Or perhaps add a new board! The maintenance manual will teach you how the +Libreboot build system (lbmk) works! + Post-compilation steps ====================== @@ -242,9 +272,10 @@ Libreboot automatically fetches this during the build process, inserting it into the very same ROM image that can be flashed on either model, but the VGA ROM will only be *executed* if you actually have the Nvidia *GPU* on your board. -ALSO: Libreboot 20230625 did not support Nvidia models at all (only Intel). +**ALSO: Libreboot 20230625 did not support Nvidia models at all (only Intel). +In releases, only Libreboot 20231021 and newer will support it.** -Pre-built ROM images from release archives after 20230625 will *not* contain +Pre-built ROM images from release archives since 20231021 will *not* contain this file by default, but it will be present if you compiled directly from lbmk. To remove it, do this: @@ -258,26 +289,3 @@ correctly on Intel GPU variants of E6400, but you probably knew that already! (If you're using a release archive instead, you can re-insert the VGA ROM by following [these instructions](../install/ivy_has_common.md)) - -20230625 build error (release archive) -====================================== - -When building ROM images from the release archives, the following error -is observed in some cases, depending on distro: - -``` -In file included from src/lib/version.c:4: -build/build.h:10:32: error: 'libreboot' undeclared here (not in a function) - 10 | #define COREBOOT_MAJOR_VERSION libreboot-20230625 - | ^~~~~~~~~ -src/lib/version.c:35:46: note: in expansion of macro 'COREBOOT_MAJOR_VERSION' - 35 | const unsigned int coreboot_major_revision = COREBOOT_MAJOR_VERSION; - | ^~~~~~~~~~~~~~~~~~~~~~ -``` - -This happened when a user tried to build for ThinkPad W541 on an Arch Linux -system. The fix is available here: - - - -Apply this patch to your local release archive, and it should fix the issue. diff --git a/site/docs/build/index.uk.md b/site/docs/build/index.uk.md index e2a0eea..100eda9 100644 --- a/site/docs/build/index.uk.md +++ b/site/docs/build/index.uk.md @@ -17,11 +17,6 @@ images (containing payloads) in `bin/`. This design is more efficient, and permits many configurations without needless duplication of work. More info is available in the [lbmk maintenance manual](../maintain/)** -Also, this page currently only refers to the build system as it exists -in `lbmk.git`. A massive re-design of lbmk has been in progress, since the -Libreboot 20230625 release. When the next version after 20230625 comes out, -this page will once again match the current tarball release. - Introduction ============ @@ -121,26 +116,3 @@ or get a list of supported build targets: окремі частини системи побудови власноруч, якщо виберете. Це може бути вигідно, коли ви робите зміни, та бажаєте протестувати конкретну частину lbmk. - -20230625 build error (release archive) -====================================== - -When building ROM images from the release archives, the following error -is observed in some cases, depending on distro: - -``` -In file included from src/lib/version.c:4: -build/build.h:10:32: error: 'libreboot' undeclared here (not in a function) - 10 | #define COREBOOT_MAJOR_VERSION libreboot-20230625 - | ^~~~~~~~~ -src/lib/version.c:35:46: note: in expansion of macro 'COREBOOT_MAJOR_VERSION' - 35 | const unsigned int coreboot_major_revision = COREBOOT_MAJOR_VERSION; - | ^~~~~~~~~~~~~~~~~~~~~~ -``` - -This happened when a user tried to build for ThinkPad W541 on an Arch Linux -system. The fix is available here: - - - -Apply this patch to your local release archive, and it should fix the issue. diff --git a/site/docs/hardware/e6430.md b/site/docs/hardware/e6430.md index ef0f701..f1fcdc8 100644 --- a/site/docs/hardware/e6430.md +++ b/site/docs/hardware/e6430.md @@ -54,6 +54,9 @@ P*: Partially works with blobs Introduction ============ +**Libreboot 20231021 and releases newer than this have ROMs available for +Dell Latitude E6430.** + ROM images for Dell Latitude E6430 are available for flashing in the Libreboot releases *after* 20230625, or you can compile a ROM image for installation via lbmk, see: [build instructions](../build/) diff --git a/site/docs/hardware/hp2170p.md b/site/docs/hardware/hp2170p.md index db9e6a1..77b44f8 100644 --- a/site/docs/hardware/hp2170p.md +++ b/site/docs/hardware/hp2170p.md @@ -65,7 +65,7 @@ this is no longer true; it's in the latest GRUB revisions, and Libreboot's version of GRUB contains this fix. **Unavailable in Libreboot 20230625 or earlier. You must [compile from -source](../build/), or use the next release after Libreboot 20230625.** +source](../build/), or use at least Libreboot 20231021.** Build ROM image from source --------------------------- diff --git a/site/docs/hardware/hp8470p.md b/site/docs/hardware/hp8470p.md index f6e1f5d..b963e29 100644 --- a/site/docs/hardware/hp8470p.md +++ b/site/docs/hardware/hp8470p.md @@ -58,7 +58,7 @@ Introduction ============ **Unavailable in Libreboot 20230625 or earlier. You must [compile from -source](../build/), or use the next release after Libreboot 20230625.** +source](../build/), or use at least Libreboot 20231021.** Official information about the laptop can be found here: diff --git a/site/docs/hardware/t1650.md b/site/docs/hardware/t1650.md index 7cec1f4..f3cde31 100644 --- a/site/docs/hardware/t1650.md +++ b/site/docs/hardware/t1650.md @@ -56,7 +56,7 @@ Introduction ============ **Unavailable in Libreboot 20230625 or earlier. You must [compile from -source](../build/), or use the next release after Libreboot 20230625.** +source](../build/), or use at least Libreboot 20231021.** Official information about the laptop can be found here: diff --git a/site/docs/install/e6400.md b/site/docs/install/e6400.md index 2144d72..efc813a 100644 --- a/site/docs/install/e6400.md +++ b/site/docs/install/e6400.md @@ -12,8 +12,9 @@ Initial flashing instructions for the E6400. release](../../news/libreboot20230423.md), and subsequent releases.** **Variants with Nvidia GPUs are NOT supported in Libreboot 20230423 -or 20230625. Please -see below for further guidance (experimental support available in `lbmk.git`).** +or 20230625.** + +**Variants with Nvidia GPUs are supported in Libreboot 20231021 or higher.** This guide is for those who want libreboot on their Latitude E6400 while they still have the original Dell BIOS present. This guide can also be @@ -126,7 +127,8 @@ more efficient if that can (and it does) support both variants. Actual installation is the same as with regular E6400 (Intel GPU) variants. Refer to the [E6400 flashing instructions](../docs/install/e6400.md). -The `e6400nvidia_wip` is used, because this version is still under development. +The `e6400nvidia_wip` branch is obsolete, and it is merely referenced for +historical purposes. Problems with Linux video drivers on Nvidia ------------------------------------------- diff --git a/site/docs/linux/encryption.md b/site/docs/linux/encryption.md deleted file mode 100644 index ab74b68..0000000 --- a/site/docs/linux/encryption.md +++ /dev/null @@ -1,123 +0,0 @@ -# Fully Encrypted Boot and Root Partitions with Libreboot - -# THIS ARTICLE IS OBSOLETE (and will probably be deleted) - -See news article: [Encrypted /boot/ on LUKSv2 now possible in Libreboot -GRUB (PHC argon2 imported)](../../news/argon2.html) - -The article, written below, was merged *before* argon2 support became possible -in GRUB, within Libreboot. The Libreboot 20230625 release doesn't have it, but -it will be present in releases after Libreboot 20230625. For now, you can -[download lbmk.git](../../git.md) and [build from source](../build/) to get -the latest Libreboot, if you want argon2 support. - -The guide below assumes that GRUB *cannot* handle argon2 key derivation, which -is most common now on LUKSv2 setups, so it has you using the older PBKDF2 -algorithm in GRUB. - -Encrypted LUKSv2 `/boot` is once again possible in Libreboot, but this page -has not yet been updated to contain guidance for that. You can most likely just -adapt the instructions below. - -# Article, as-is: - -The following guide will explain how to create: - -+ A boot partition (/dev/sda1 in this example) that GRUB can decrypt with 'passphrase1' -+ A root partition (/dev/sda2) with stronger encryption using 'passphrase2' - -This guide assumes you are working from a live disk of your preffered distro. - -# Creating Encrypted Boot Partition - -Grub2 currently (Oct 2021) supports luks2 encryption, which is great, but only the (not very strong) PBKDF2 algorithm. -Start by creating a boot partition of around 1GB, you don't have to format it to anything as LUKS will overwrite it anyway. - -**Step 1:** -Create a LUKS2 formatted device with the PBKDF2 algorithm. -You can play around with the iteration count. -A higher iteration is more secure but will take GRUB a **very** long time to decrypt. -The [debian encrypted boot guide](https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html) recommends a count of 500,000 which will still take GRUB a very long time (around 25 seconds) but is faster than the default 1000,000. -Use whatever count makes you feel comfortable. -I'll use and arbitrarily low count. -You'll also want to use a different password than you intend to use for your root partition. -We don't want someone to be able to get our root key by brute-forcing our less secure boot key. - -`sudo cryptsetup luksFormat /dev/sda1 --type luks2 --pbkdf pbkdf2 --pbkdf-force-iterations 200000` - -**Step 2:** -Format and mount the new LUKS2 device. - -``` -sudo cryptsetup luksOpen /dev/sda1 boot -sudo mkfs.ext4 -L boot /dev/mapper/boot -sudo mount /dev/mapper/boot /boot -``` -**Note:** -If you wish to change the passphrase for the boot partition in the future then you'll need to pass the same arguments to cryptsetup as when you created it. -If you don't pass any special arguments, the key will be changed to the distro's default encryption and grub won't be able to decrypt it. -The command to use is: - -`cryptsetup luksChangeKey /dev/sda1 --type luks2 --pbkdf pbkdf2 --pbkdf-force-iterations 200000` - -# Root Partition - -Setting up the root partion is generally simple. -Use the same command without the given parametres used to make the device decryptable by GRUB. - -`cryptsetup luksFormat /dev/sda2 root` - -# Set Up Grub and Install - -You will need to pass the correct kernel parametres to your kernel on boot to allow you to use your encryption passphrase to decrypt the root partition. -These parametres can be passed via a grub config in the boot partition by editing `/etc/default/grub.` - -Add the necessary parametres to the line `GRUB_CMDLINE_LINUX_DEFAULT` as follows: - -`GRUB_CMDLINE_LINUX_DEFAULT="loglevel=4 rd.auto=1 cryptdevice=/dev/sda2:root"` - -*rd.auto=1* tells linux that you want to decrypt all disks. -*cryptdevice* tells linux the block device and mapped name you want to use for the root partition. -Note that the mapped name **must** match what you have it `/etc/fstab.` - -From here, you can generally follow the install guide from your distro's docs. -Make sure that the generated `/boot/grub/grub.cfg` file indeed contains the necessary kernel parametres and that the `/etc/default/grub` file on the disk has the same modifications described above. - -# Set up Fstab - -> The device holding the kernel (and the initramfs image) is unlocked by GRUB, but the root device needs to be unlocked again at initramfs stage, regardless whether it’s the same device. This is because GRUB boots with the given vmlinuz and initramfs images, but there is currently no way to securely pass cryptographic material (or Device Mapper information) to the kernel. Hence the Device Mapper table is initially empty at initramfs stage; in other words, all devices are locked, and the root device needs to be unlocked again. -> -> \- [Debian Guide](https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html) - -**Step 1:** -Here, we're not trying to store the root key as we don't want to jeopardize the integrity of our root device. -Instead, we want to store the key for the boot device on the root partition. - -``` -sudo mkdir -m0700 /etc/keys -su -c '( umask 0077 && dd if=/dev/urandom bs=1 count=64 of=/etc/keys/boot.key conv=excl,fsync )' -sudo cryptsetup luksAddKey /dev/sda1 /etc/keys/boot.key -``` - -**Step 2:** -Add your boot device to your crypttab. -You'll need to have the device's UUID. -You can obtain the UUID from `blkid` or simply use the linux block device name `/dev/sda1,` acknowleding it may lead to another device if your disk configuration changes. - -```bash -lsblk -o 'PATH,LABEL,UUID' # to get UUID -sudo vim /etc/crypttab - -> boot_crypt UUID=YOUR_UUID /etc/keys/boot.key luks,key-slot=1 -``` -**Step 3:** -Add the crypt device to your fstab. -Use 'mount -a' to test your fstab configuration. -NOTE: you will not be able to mount the device until it has been unlocked and mapped, rebooting with your new crypttab should do this automatically. - -``` -sudo vim /etc/fstab - -> /dev/mapper/boot_crypt /boot ext4 defaults 0 1 -sudo mount -a -``` diff --git a/site/docs/linux/grub_cbfs.md b/site/docs/linux/grub_cbfs.md index 0d2d648..b47fa02 100644 --- a/site/docs/linux/grub_cbfs.md +++ b/site/docs/linux/grub_cbfs.md @@ -117,10 +117,10 @@ machine powered down) and read the contents of the boot flash. Extract grub.cfg ================ -Releases *after* Libreboot 20230625 +Libreboot 20231021 or newer ----------------------------------- -Releases after Libreboot 20230625 contain `grub.cfg` inside the GRUB memdisk, +Releases or or after 20231021 contain `grub.cfg` inside the GRUB memdisk, inaccessible directly from CBFS, but the memdisk is inside `grub.elf` which gets put inside CBFS. @@ -130,15 +130,20 @@ auto-switch to `grubtest.cfg`, but the test config will be available in the menu to switch to, if present. You can find `grub.cfg` under lbmk (for this purpose, it's best to use the -lbmk one, not the release one - unless you're using a release after 20230625). -Find it at path: `config/grub/config/grub.cfg`. +lbmk one, not the release one - unless you're using a release image). +Find it at path (in current lbmk): `config/grub/config/grub.cfg`. So, you can *add* `grubtest.cfg` as normal, test that, and then *add* `grub.cfg` once you're happy, and it will override the default. -Libreboot 20230625 and below: +Libreboot 20230625 or older ---------------------------- +NOTE: This information will probably be deleted after a certain time has passed. +Libreboot changed a lot, as of release 20231021 in reference to 20230625, so it +may take a while before people adjust; therefore, this information is provided +for reference, but you should consider it to be deprecated: + libreboot images that use the GRUB bootloader will have *two* configuration files in CBFS: @@ -171,7 +176,7 @@ from your ROM image. Insert new grub.cfg =================== -NOTE: As stated above, releases after Libreboot 20230625 only default to +NOTE: As stated above, releases on or after Libreboot 20231021 only default to the config in memdisk, and lack a CBFS config, so you can skip the *remove* step below and just directly add the new `grub.cfg` - unless you already added one before, in which case removal is required first. diff --git a/site/docs/linux/index.md b/site/docs/linux/index.md index af3c64d..737df0c 100644 --- a/site/docs/linux/index.md +++ b/site/docs/linux/index.md @@ -52,20 +52,47 @@ executed from Libreboot's SeaBIOS payload. Encrypted (LUKS/dm-crypt) installations ======================================= -A better solution for encryption would be a Linux payload in flash, handling the -encryption, at least if you want to use Linux, because then it'll have -perfect LUKS support. +Full encryption for basic LUKS2 (with PBKDF or argon2 key derivation) is +supported in libreboot. Legacy LUKS1 is also supported. -GRUB otherwise has good filesystem support, so if you have a valid `grub.cfg` -in `/boot/grub` on your installed system, Libreboot's GRUB configuration has -logic in it that will try to automatically use whatever you have installed, -by switching to it. In this way, most installations Just Work, so long as -the `/boot` partition is accessible. +This is a boon for security, because it's harder +to tamper with, and you could potentially write-protect plus maybe provide +a [password](grub_hardening.md) in GRUB at boot time. -Full encryption for basic LUKS2 is supported in libreboot. -See [the guide](encryption.md) for more detail. +The easiest way to use it is like this: in Linux, set up your partitions like +you would, but use LVM volume groups, with group name `grubcrypt` and either: -[The ZFSbootmenu guide](zfsbootmenu.md) builds upon the main encryption guide but describes a setup with ZFS native encryption and ZFSbootmenu. +* `/` as volume name `rootvol` and `/boot` as volume name `bootvol` +* `/` as volume name `rootvol` and `/boot` exists within it (no `bootvol`) + +If your distro then installs GRUB, and provides a `grub.cfg` file +under `/boot/grub` (within the distro, on your SSD/HDD file system), it should +work. Libreboot's GRUB will automatically give you a passphrase prompt, where +you type your passphrase and it unlocks the volume. Then it will find your +LVMs and it'll boot from that. + +Otherwise, to manually unlock it, you drop to the GRUB shell with C and do: + + cryptomount -a + +Or on a specific device, e.g. + + cryptomount (ahci0,1) + +This is similar to `cryptsetup luksOpen` in Linux. + +Libreboot GRUB merges the PHC argon2 implementation, so it has full support +for LUKS2 installations in addition to LUKS1. Libreboot 20231021 and higher +has argon2 support, but older releases only supported PBKDF2 which would make +LUKS2 dysfunctional unless you swapped it to use PBKDF2 (not argon2) and/or +downgraded to LUKS1. + +With modern Libreboot, you can just use LUKS2 as-is, on most/all Linux distros. +At the time of the Libreboot 20231021 release, the GRUB upstream (on gnu.org) +did not have these argon2 patches in its source tree, but Libreboot merges and +maintains them out of tree. + +NOTE: You should also read the instructions about about `GRUB_TERMINAL`. Rebooting system in case of freeze =================================== diff --git a/site/docs/linux/zfsbootmenu.md b/site/docs/linux/zfsbootmenu.md deleted file mode 100644 index e853324..0000000 --- a/site/docs/linux/zfsbootmenu.md +++ /dev/null @@ -1,124 +0,0 @@ ---- -title: ZFSbootmenu with Full Disk Encryption Guide -x-toc-enable: true -... - -This article is obsolete! -========================= - -**NOTE: [Encrypted /boot with LUKS2 on argon2 key derivation is now -possible](../../news/argon2.md) but not yet documented by this guide.** - -zfsbootmenu is still nice, but no longer required. Use latest Libreboot and -boot encrypted /boot (with argon2) directly from GRUB if you want to. Guides -need to be written for this, and are not yet present on the Libreboot site. - -Article -======= - -As described in the [general encryption guide,](encryption.md) Libreboot allows for full disk encryption including the boot partition. -Just as with the general guide, this explanation will demonstrate how to create a partition with moderate encryption for GRUB as well as a root partition with strong encryption. -The major differences between the encryption method described in the general guide and this guide are: - -+ `/boot` must remain on the *root* zfs encrypted partition -+ The root partition will be encrypted with ZFS native encryption rather than LUKS -+ ZFSbootmenu will be loaded at the second boot stage (after Libreboot itself) rather than directly loading the operating system kernel/initramfs - -[ZFSbootmenu](https://docs.zfsbootmenu.org/en/latest/) works by placing modified versions of the operating system kernel where they can be loaded by the system's bootloader. -ZFSbootmenu provides installation guides for various major distros in their [official docs.](https://docs.zfsbootmenu.org/en/latest/) -You should follow those docs for installation, only noting the differences necessary for full disk encryption described below. -The only differences between this guide and the docs are: - -+ You need not install/configure syslinux as GRUB in Libreboot will be used to load the ZFSbootmenu kernel/initramfs -+ The ZFSbootmenu kernel/initramfs will reside on a LUKS encrypted partition you will create in this guide -+ Cryptsetup must be installed and configured to mount the LUKS encrypted partition - -## Creating Encrypted Partition for GRUB - -The following section is mostly identical to the main encryption guide except for the naming conventions of the partition in question. -When using ZFSbootmenu, the OS kernel/initramfs will reside on the root partion in the `/boot` directory; **not** on a separate boot partition. -The partition created in this section is only used to load the ZFSbootmenu kernel/initramfs itself and is therefore referred to as the 'pre-boot environment' *(pbe)* partition. - -**Step 1:** -Create a LUKS2 formatted device with the PBKDF2 algorithm. -You can play around with the iteration count. -A higher iteration is more secure but will take GRUB a **very** long time to decrypt. -The [debian encrypted boot guide](https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html) recommends a count of 500,000 which will still take GRUB a very long time (around 25 seconds) but is faster than the default 1,000,000. -Use whatever count makes you feel comfortable. -I'll use an arbitrarily low count. -You'll also want to use a different password than you intend to use for your root partition. -We don't want someone to be able to get our root key by brute-forcing our less secure boot key. - -`sudo cryptsetup luksFormat /dev/sda1 --type luks2 --pbkdf pbkdf2 --pbkdf-force-iterations 200000` - -**Step 2:** -Format and mount the new LUKS2 device. - -``` -sudo cryptsetup luksOpen /dev/sda1 pbe -sudo mkfs.ext4 -L boot /dev/mapper/pbe -sudo mkdir -p /boot/pbe -sudo mount /dev/mapper/boot /boot/pbe -``` -**Note:** -If you wish to change the passphrase for the boot partition in the future then you'll need to pass the same arguments to cryptsetup as when you created it. -If you don't pass any special arguments, the key will be changed to the distro's default encryption and grub won't be able to decrypt it. -The command to use is: - -`cryptsetup luksChangeKey /dev/sda1 --type luks2 --pbkdf pbkdf2 --pbkdf-force-iterations 200000` - -## Configure ZFSbootmenu - -The [official ZFSbootmenu docs](https://docs.zfsbootmenu.org/en/latest/guides/general.html) will provide the most up-to-date information. -The only differences from the official documentation relevant here are that anything related to syslinux can be ignored and the configuration must be tailored to create only a single kernel/initramfs set. -Note that you should follow the *MBR/syslinux* guide for your distro if you are using the ZFSbootmenu guides. - -Here is an example configuration: - -``` -> vim /etc/zfsbootmenu/config.yaml - -Global: - ManageImages: true - BootMountPoint: /boot/pbe - DracutConfDir: /etc/zfsbootmenu/dracut.conf.d - PreHooksDir: /etc/zfsbootmenu/generate-zbm.pre.d - PostHooksDir: /etc/zfsbootmenu/generate-zbm.post.d - InitCPIOConfig: /etc/zfsbootmenu/mkinitcpio.conf -Components: - ImageDir: /boot/pbe/zfsbootmenu - Versions: false - Enabled: true - syslinux: - Config: /boot/syslinux/syslinux.cfg - Enabled: false -EFI: - ImageDir: /boot/pbe - Versions: false - Enabled: false -Kernel: - CommandLine: ro quiet loglevel=4 -``` - -## Final Steps - -Refer to the [general guide](encryption.md) on how to set up fstab/crypttab to mount the pre-boot environment on boot. -Replace references to *boot* with *pbe* if copying commands from the guide. -For example: make sure the partition is mounted at `/boot/pbe` rather than just `/boot.` - -Ensure that your OS kernel/initramfs is generated with LUKS support. -LUKS support is generally automatically enabled in the kernel upon installing *cryptsetup.* - -Create a simulated grub configuration to point Libreboot's GRUB to ZFSbootmenu. -Libreboot will search for and source a grub configuration file on boot/decryption automatically. -**Do not** actually install GRUB. -Simply create a file on the partition created for GRUB at `/boot/pbe/grub/grub.cfg` which points to the ZFSbootmenu kernel/initramfs. - -``` -mkdir -p /boot/pbe/grub -> vim /boot/pbe/grub/grub.cfg - -linux /zfsbootmenu/vmlinuz-* loglevel=4 -initrd /zfsbootmenu/initramfs-* -boot -``` diff --git a/site/download.html b/site/download.html new file mode 100644 index 0000000..66f061b --- /dev/null +++ b/site/download.html @@ -0,0 +1,294 @@ + + + + + + + + + + + + + + + + + + Libreboot – Downloads + + + + +
+
+
+ +

Downloads

+
+ +
+
+ +
+

English | українська

+

Return to index

+

New releases are announced in the main news +section.

+

If you’re more interested in libreboot development, go to the libreboot development page, which also includes +links to the Git repositories. The page on /docs/maintain/ describes how Libreboot is put +together, and how to maintain it. If you wish to build Libreboot from +source, read this page.

+

READ +THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE

+

On newer Intel platforms that require Intel ME and/or MRC +firmware, such as ThinkPad X230 or T440p, and/or HP laptops that require +KBC1126 EC firmware, the release ROMs of Libreboot are MISSING certain +files, that you must insert yourself. FAILURE to adhere to this warning +may result in you bricking your machine (rendering it unbootable), if +you were to flash the release ROMs without modifying them in any way. +For more information, please read:

+

Insert vendor +files on Sandybridge/Ivybridge/Haswell

+

NOTE: This warning does not apply to ROMs that you compiled yourself, +using lbmk. It only applies to release ROMs, because ME/MRC/EC firmware +is deleted in release ROMs. The link above says how to re-add +them. When building ROM images yourself, from source, Libreboot’s build +system automatically handles it. See: Libreboot +build instructions

+

This isn’t required on all Libreboot-supported boards, but +if in doubt, follow these instructions anyway. If you run the vendor +scripts on a board that doesn’t need blobs, nothing will happen.

+

GPG signing key

+

The latest release is Libreboot 20231021, under the +testing directory.

+

NEW KEY

+

Full key fingerprint: +98CC DDF8 E560 47F4 75C0 44BD D0C6 2464 FA8B 4856

+

This key is for Libreboot releases after the 20160907 +release.

+

Download the key here: lbkey.asc

+

Libreboot releases are signed using GPG.

+

OLD KEY:

+

This key is for Libreboot 20160907, and releases older than +20160907:

+

Full key fingerprint: CDC9 CAE3 2CB4 B7FC 84FD C804 969A 9795 05E8 +C5B2

+

The GPG key can also be downloaded with this exported dump of the +pubkey: lbkeyold.asc.

+
sha512sum -c sha512sum.txt
+gpg --verify sha512sum.txt.sig
+

Git repository

+

Links to regular release archives are listed on this page.

+

However, for the absolute most bleeding edge up-to-date version of +Libreboot, there is a Git repository that you can download from. Go +here:

+

How to download Libreboot from Git

+

HTTPS mirrors

+

The latest release is Libreboot 20231021, under the +testing directory.

+

These mirrors are recommended, since they use TLS (https://) +encryption.

+

You can download Libreboot from these mirrors:

+ +

RSYNC mirrors

+

The following rsync mirrors are available publicly:

+ +

Are you running a mirror? Contact the libreboot project, and the link +will be added to this page!

+

You can make your rsync mirror available via your web server, and +also configure your own mirror to be accessible via rsync. +There are many resources online that show you how to set up an rsync +server.

+

How to create your own rsync mirror:

+

Useful for mirroring Libreboot’s entire set of release archives. You +can put an rsync command into crontab and pull the files into a +directory on your web server.

+

If you are going to mirror the entire set, it is recommended that you +allocate at least 25GiB. Libreboot’s rsync is currently about 12GiB, so +allocating 25GiB will afford you plenty of space for the future. At +minimum, you should ensure that at least 15-20GiB of space is available, +for your Libreboot mirror.

+

It is highly recommended that you use the libreboot.org +mirror, if you wish to host an official mirror. Otherwise, if you +simply want to create your own local mirror, you should use one of the +other mirrors, which sync from libreboot.org.

+

Before you create the mirror, make a directory on your web server. +For example:

+
mkdir /var/www/html/libreboot/
+

Now you can run rsync, for instance:

+
rsync -avz --delete-after rsync://rsync.libreboot.org/mirrormirror/ /var/www/html/libreboot/
+

You might put this in an hourly crontab. For example:

+
crontab -e
+

Then in crontab, add this line and save/exit (hourly crontab):

+
0 * * * * rsync -avz --delete-after rsync://rsync.libreboot.org/mirrormirror/ /var/www/html/libreboot/
+

It’s extremely important to have the final forward slash (/) +at the end of each path, in the above rsync command. Otherwise, rsync +will behave very strangely.

+

NOTE: rsync.libreboot.org is not directly +accessible by the public, except those whose IPs are whitelisted. For +bandwidth reasons, the firewall running on libreboot.org blocks incoming +rsync requests, except by specific IPs.

+

If you wish to run an rsync mirror, sync from one of the +third party mirrors above and set up your mirror. You can then contact +Leah Rowe, to have your IP addresses whitelisted for rsync usage - if +the IP addresses match DNS A/AAAA records for your rsync host, this can +be used. A script runs in an hourly crontab on libreboot.org, that +fetches the A/AAAA records of whitelisted rsync mirrors, automatically +adding rules permitting them to get through the firewall.

+

If you wish to regularly keep your rsync mirror updated, you can add +it to a crontab. This page tells you how to use crontab: https://man7.org/linux/man-pages/man5/crontab.5.html

+

HTTP mirrors

+

The latest release is Libreboot 20231021, under the +testing directory.

+

WARNING: these mirrors are non-HTTPS which means that they are +unencrypted. Your traffic could be subject to interference by +adversaries. Make especially sure to check the GPG signatures, assuming +that you have the right key. Of course, you should do this anyway, even +if using HTTPS.

+ +

FTP mirrors

+

The latest release is Libreboot 20231021, under the +testing directory.

+

WARNING: FTP is also unencrypted, like HTTP. The same risks are +present.

+ +

Statically linked

+

Libreboot includes statically linked executables in some releases, +built from the available source code. Those executables have certain +libraries built into them, so that the executables will work on many +Linux distros.

+

To comply with GPL v2, source ISOs are supplied by the Libreboot +project. You can find these source ISOs in the ccsource +directory on the rsync mirrors.

+

Libreboot releases past version 20160907 do not distribute statically +linked binaries. Instead, these releases are source-only, besides +pre-compiled ROM images for which the regular Libreboot source code +archives suffice. These newer releases instead automate the installation +of build dependencies, with instructions in the documentation for +building various utilities from source.

+

These executables are utilities such as flashrom.

+ +

Markdown file for this page: https://libreboot.org/download.md

+

Site map

+

This HTML page was generated by the untitled static site +generator.

+
+
+ + diff --git a/site/download.md b/site/download.md index a8f8943..3bd26c6 100644 --- a/site/download.md +++ b/site/download.md @@ -36,7 +36,7 @@ need blobs, nothing will happen. GPG signing key --------------- -**The latest release is Libreboot 20230625, under the `stable` directory.** +**The latest release is Libreboot 20231021, under the `testing` directory.** ### NEW KEY @@ -73,7 +73,7 @@ there is a Git repository that you can download from. Go here: HTTPS mirrors {#https} ------------- -**The latest release is Libreboot 20230625, under the `stable` directory.** +**The latest release is Libreboot 20231021, under the `testing` directory.** These mirrors are recommended, since they use TLS (https://) encryption. @@ -166,7 +166,7 @@ crontab. This page tells you how to use crontab: HTTP mirrors {#http} ------------ -**The latest release is Libreboot 20230625, under the `stable` directory.** +**The latest release is Libreboot 20231021, under the `testing` directory.** WARNING: these mirrors are non-HTTPS which means that they are unencrypted. Your traffic could be subject to interference by @@ -180,7 +180,7 @@ if using HTTPS. FTP mirrors {#ftp} ----------- -**The latest release is Libreboot 20230625, under the `stable` directory.** +**The latest release is Libreboot 20231021, under the `testing` directory.** WARNING: FTP is also unencrypted, like HTTP. The same risks are present. diff --git a/site/download.md.date b/site/download.md.date new file mode 100644 index 0000000..f6ca8f7 --- /dev/null +++ b/site/download.md.date @@ -0,0 +1 @@ +1697840199 diff --git a/site/download.uk.html b/site/download.uk.html new file mode 100644 index 0000000..1e3ecd6 --- /dev/null +++ b/site/download.uk.html @@ -0,0 +1,299 @@ + + + + + + + + + + + + + + + + + + Libreboot – Завантаження + + + + +
+
+
+ +

Завантаження

+
+ +
+
+ +
+

English | українська

+

попередній індекс

+

Нові випуски оголошуються в основній секції +новин.

+

Якщо ви більше зацікавлені в розробці libreboot, пройдіть на сторінку розробки libreboot, яка також включає +посилання на репозиторії Git. Сторінка на /docs/maintain/ описує те, як Libreboot +складається разом, і як підтримувати його. Якщо ви бажаєте зібрати +Libreboot із джерельного кода, прочитайте цю +сторінку.

+

READ +THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE

+

On newer Intel platforms that require Intel ME and/or MRC +firmware, such as ThinkPad X230 or T440p, and/or HP laptops that require +KBC1126 EC firmware, the release ROMs of Libreboot are MISSING certain +files, that you must insert yourself. FAILURE to adhere to this warning +may result in you bricking your machine (rendering it unbootable), if +you were to flash the release ROMs without modifying them in any way. +For more information, please read:

+

Insert vendor +files on Sandybridge/Ivybridge/Haswell

+

NOTE: This warning does not apply to ROMs that you compiled yourself, +using lbmk. It only applies to release ROMs, because ME/MRC/EC firmware +is deleted in release ROMs. The link above says how to re-add +them. When building ROM images yourself, from source, Libreboot’s build +system automatically handles it. See: Libreboot +build instructions

+

This isn’t required on all Libreboot-supported boards, but +if in doubt, follow these instructions anyway. If you run the vendor +scripts on a board that doesn’t need vendor files, nothing will +happen.

+

Код підпису GPG

+

Останнім випуском є Libreboot 20231021, в директорії +testing.

+

НОВИЙ КЛЮЧ

+

Повний відбиток ключа: +98CC DDF8 E560 47F4 75C0 44BD D0C6 2464 FA8B 4856

+

Вищезазначений ключ для Libreboot 20231021, та наступних +випусків.

+

Завантажте ключ тут: lbkey.asc

+

Випуски Libreboot підписані з використанням GPG.

+

СТАРИЙ КЛЮЧ:

+

Цей ключ для Libreboot 20160907 та всіх старіших випусків:

+

Повний відбиток ключа: CDC9 CAE3 2CB4 B7FC 84FD C804 969A 9795 05E8 +C5B2

+

Ключ GPG також може бути завантажений разом із цим експортованим +дампом публічного ключа: lbkeyold.asc.

+
sha512sum -c sha512sum.txt
+gpg --verify sha512sum.txt.sig
+

Репозиторій Git

+

Посилання на архіви регулярних випусків зазначені на цій +сторінці.

+

Однак, для абсолютно найновішої версії Libreboot, існує репозиторії +Git, з якого можна завантажити. Ідіть сюди:

+

Як завантажити Libreboot через Git

+

Дзеркала HTTPS

+

Останнім випуском є Libreboot 20231021, в директорії +testing.

+

Дані дзеркала є рекомендованими, оскільки використовують TLS +(https://) шифрування.

+

Ви можете завантажити Libreboot через дані дзеркала:

+ +

Дзеркала RSYNC

+

Наступні дзеркала rsync доступні публічно:

+ +

Ви підтримуєте роботу дзеркала? Зв’яжіться з проектом libreboot, і +посилання буде додано до цієї сторінки!

+

Ви можете зробити своє дзеркало rsync доступним через свій +веб-сервер, а також налаштувати ваше власне дзеркало бути +доступним через rsync. Є багато онлайн-ресурсів, які показують вам те, +як налаштувати сервер rsync.

+

Як створити ваше власне дзеркало rsync:

+

Корисно для відзеркалювання повного набору архівів випусків +Libreboot. Ви можете розмістити команду rsync в crontab та витягувать +файли в директорію на вашому веб-сервері.

+

Якщо ви збираєтесь відзеркалювати повний набір, рекомендовано, щоб +вами було виділено хоча би 25 ГБ. Rsync Libreboot наразі приблизно 12 +ГБ, таким чином виділення 25 ГБ забезпечить вам багато місця на +майбутнє. Мінімально, ви маєте переконатись, що хоча би 15-20 ГБ +простору доступно, для вашого дзеркала Libreboot.

+

Настійно рекомендується, щоб ви використовували дзеркало +libreboot.org, якщо бажаєте розміщувати офіційне дзеркало. В іншому +випадку, якщо ви просто бажаєте створити своє власне локальне дзеркало, +вам варто використовувати одне з інших дзеркал, яке синхронізується з +libreboot.org.

+

Перед створенням дзеркала, зробіть директорію на вашому веб-сервері. +Для прикладу:

+
mkdir /var/www/html/libreboot/
+

Тепер ви можете виконувати rsync, для прикладу:

+
rsync -avz --delete-after rsync://rsync.libreboot.org/mirrormirror/ /var/www/html/libreboot/
+

Ви могли би розмістить це в щогодинний crontab. Для прикладу:

+
crontab -e
+

Потім в crontab, додайте цей рядок і збережіться/вийдіть (щогодинний +crontab):

+
0 * * * * rsync -avz --delete-after rsync://rsync.libreboot.org/mirrormirror/ /var/www/html/libreboot/
+

Це надзвичайно важливо, щоб мати в кінці косу лінію (/) в +кінці кожного шляху, в вищезазначеній команді rsync. В інакшому випадку, +rsync буде поводитись дуже дивно.

+

ПОМІТКА: rsync.libreboot.org не є напряму +доступним для громадськості, окрім тих, чиї IP у білому списку. Через +пропускну здатність, Брандмауер, який працює на libreboot.org, блокує +вхідні запити rsync, окрім окремих IP.

+

Якщо ви бажаєте запустити дзеркало rsync, синхронізуйте з +одного з дзеркал третіх сторін вище і встановіть своє дзеркало. Ви +можете потім зв’язатись з Лією Роу, щоб мати ваші адреси IP внесеним в +білий список для використання rsync - якщо адреси IP відповідають DNS +A/AAAA записам для вашого хоста rsync, це може бути використано. +Сценарій виконується в щогодинному crontab на libreboot.org, який +отримує A/AAAA записи внесених в білий список дзеркал rsync, автоматично +додаючи правила, які дозволяють їм проходити через +брандмауер.

+

Якщо ви бажаєте регулярно тримати свої дзеркала rsync оновленими, ви +можете додати це до crontab. Ця сторінка розповідає вам, як +використовувати crontab: https://man7.org/linux/man-pages/man5/crontab.5.html

+

Дзеркала HTTP

+

Останнім випуском є Libreboot 20231021, під директорією +testing.

+

УВАГА: ці дзеркала є не-HTTPS, що означає, що вони незашифровані. Ваш +трафік може бути об’єктом втручання противників. Особливо ретельно +переконайтесь, щоб перевірити підписи GPG, передбачаючи, що ви маєте +правильний ключ. Звісно, вам варто зробити це в будь-якому випадку, +навіть при використанні HTTPS.

+ +

Дзеркала FTP

+

Останнім випуском є Libreboot 20231021, під директорією +testing.

+

УВАГА: FTP є також незашифрованим, подібно HTTP. Ті ж самі ризики +присутні.

+ +

Статично зв’язані

+

Libreboot включає статично зв’язані виконувані файли в деяких +випусках, побудовані з доступного джерельного кода. Ці виконувані файли +мають деякі бібліотеки, вбудовані в них, так щоб виконувані файли +працювали на багатьох дистрибутивах Linux.

+

Для дотримання GPL v2, джерельні ISO постачаються проектом Libreboot. +Ви можете знайти ці джерельні ISO в директорії ccsource на +дзеркалах rsync.

+

Попередні випуски Libreboot 20160907 не розповсюджують статично +зв’язані двійкові файли. Натомість ці випуски є лише вихідними кодами, +окрім попередньо скомпільованих образів ПЗП, для яких достатньо +звичайних архівів джерельного коду Libreboot. Ці новіші випуски +натомість автоматизують встановлення залежностей побудови, з інструкцієї +в документації для побудови різних утиліт з джерельного коду.

+

Ці виконувані файли є утилітами, подібними flashrom.

+ +

Markdown: https://libreboot.org/download.uk.md

+

Індекс сайта

+

Ця сторінка була створена з untitled static site +generator.

+
+
+ + diff --git a/site/download.uk.md b/site/download.uk.md index 3cb4b25..33d4ac0 100644 --- a/site/download.uk.md +++ b/site/download.uk.md @@ -36,13 +36,13 @@ need vendor files, nothing will happen. Код підпису GPG --------------- -**Останнім випуском є Libreboot 20230625, в директорії `stable`.** +**Останнім випуском є Libreboot 20231021, в директорії `testing`.** ### НОВИЙ КЛЮЧ Повний відбиток ключа: `98CC DDF8 E560 47F4 75C0 44BD D0C6 2464 FA8B 4856` -Вищезазначений ключ для Libreboot 20230625, та наступних випусків. +Вищезазначений ключ для Libreboot 20231021, та наступних випусків. Завантажте ключ тут: [lbkey.asc](lbkey.asc) @@ -73,7 +73,7 @@ need vendor files, nothing will happen. Дзеркала HTTPS {#https} ------------- -**Останнім випуском є Libreboot 20230625, в директорії `stable`.** +**Останнім випуском є Libreboot 20231021, в директорії `testing`.** Дані дзеркала є рекомендованими, оскільки використовують TLS (https://) шифрування. @@ -166,7 +166,7 @@ crontab. Ця сторінка розповідає вам, як викорис Дзеркала HTTP {#http} ------------ -**Останнім випуском є Libreboot 20230625, під директорією `stable`.** +**Останнім випуском є Libreboot 20231021, під директорією `testing`.** УВАГА: ці дзеркала є не-HTTPS, що означає, що вони незашифровані. Ваш трафік може бути об'єктом втручання @@ -180,7 +180,7 @@ crontab. Ця сторінка розповідає вам, як викорис Дзеркала FTP {#ftp} ----------- -**Останнім випуском є Libreboot 20230625, під директорією `stable`.** +**Останнім випуском є Libreboot 20231021, під директорією `testing`.** УВАГА: FTP є також незашифрованим, подібно HTTP. Ті ж самі ризики присутні. diff --git a/site/download.uk.md.date b/site/download.uk.md.date new file mode 100644 index 0000000..596e8ae --- /dev/null +++ b/site/download.uk.md.date @@ -0,0 +1 @@ +1697840147 diff --git a/site/index.de.html b/site/index.de.html new file mode 100644 index 0000000..fc201a0 --- /dev/null +++ b/site/index.de.html @@ -0,0 +1,212 @@ + + + + + + + + + + + + + + + + + + Libreboot – Libreboot projekt + + + + +
+
+
+ +

Libreboot projekt

+
+ +
+
+ +
+

English | Deutsch | Français | Italiano +| українська | 简体中文

+

Das Libreboot Projekt bietet eine freie Boot Firmware welche auf +bestimmten Intel/AMD x86 und ARM Geräten +die Hardware initialisiert (z.b. Speicher-Controller, CPU, Peripherie), +und dann einen Bootloader für dein Betriebssystem startet. Linux sowie BSD werden +gut unterstützt. Es ersetzt proprietäre BIOS/UEFI Firmware. Hilfe ist +verfügbar via #libreboot und Libera IRC.

+

+

NEUESTE VERSION: Die neueste Version von Libreboot ist +20231021, veröffentlicht am 21. Oktober 2023. Siehe auch: Libreboot 20231021 release +announcement.

+

Warum solltest Du +Libreboot verwenden?

+

Libreboot gibt dir Freiheit welche Du mit den +meisten Boot Firmwares nicht hast, und zusätzlich schnellere Boot +Geschwindigkeiten sowie höhere +Sicherheit. Es ist extrem leistungsfähig und für viele Einsatzzwecke +konfigurierbar.

+

Du hast Rechte. Das Recht auf Privatsphäre, Gedankenfreiheit, +Meinungsäußerungsfreiheit, und Informationsfreiheit. In diesem +Zusammenhang, Libreboot gibt dir diese Rechte. Deine Freiheit ist +wichtig. Das Recht auf +Reparatur ist wichtig. Viele Menschen verwenden proprietäre +(non-libre) Boot Firmware, sogar wenn Sie ein Libre OS verwenden. Proprietäre +Firmware enthält häufig Hintertüren, und kann fehlerhaft sein. Das +Libreboot Projekt wurde im Dezember 2013 gegründet, mit dem Ziel, +Coreboot Firmware auch für technisch unerfahrene Nutzer verfügbar zu +machen.

+

Das Libreboot Projekt verwendet Coreboot für die +Initialiserung der Hardware. Die Coreboot Installation ist für +unerfahrene Benutzer überaus schwierig; sie übernimmt lediglich die +Basis Initialisierung und springt dann zu einem separaten payload Programm (z.B. +GRUB, Tianocore), welche zusätzlich +konfiguriert werden muss. Libreboot löst dieses Problem; es ist +eine Coreboot Distribution mit einem automatisierten Build System welches vollständige +ROM images für eine robustere Installation erstellt. +Dokumentation ist verfügbar.

+

Libreboot ist kein Coreboot +Fork

+

+

Tatsächlich versucht Libreboot so nah am regulären Coreboot zu +bleiben wie möglich, für jedes Board, aber mit vielen automatisch durch +das Libreboot Build System zur Verfügung gestellten verschiedenen +Konfigurationstypen.

+

Ebenso wie Alpine Linux eine Linux Distribution +ist, ist Libreboot eine Coreboot Distribution. Sofern Du ein +ROM Image von Grund auf herstellen möchtest, musst Du zunächst +Konfigurationen auf Experten Level durchführen, und zwar für Coreboot, +GRUB sowie sämtliche Software die Du sonst noch verwenden möchtest um +das ROM Image vorzubereiten. Mithilfe von Libreboot kannst Du +sprichwörtlich von Git oder einem anderen Quell-Archiv herunterladen, +anschliessend make ausführen, und es wird komplette ROM +Images herstellen, ohne das Benutzer Eingaben oder Eingreifen von Nöten +sind. Die Konfiguration wurde bereits im Vorfeld erledigt.

+

Sofern Du das reguläre Coreboot herstellen wollen würdest, ohne +hierfür das automatisierte Libreboot Build System zu verwenden, würde +dies deutlich mehr Eingreifen und ein sehr tiefgreifendes technisches +Verständnis voraussetzen um eine funktionsfähige Konfiguration +herzustellen.

+

Reguläre Binär Veröffentlichungen bieten diese ROM Images +vor-kompiliert, und Du kannst dies einfach installieren ohne spezielle +technische Kenntnisse oder Fertigkeiten abgesehen von der Fähigkeit +einer vereinfachten Anleitung, geschrieben für +technisch unerfahrene Benutzer zu folgen.

+

Wie kann ich helfen

+

+

Der beste Weg wie Du helfen kannst, ist das hinzufügen neuer +Mainboards in Libreboot, indem Du eine Konfiguration zur Verfügung +stellst. Alles was von Coreboot unterstützt wird kann auch in Libreboot +integriert werden, mithilfe von ROM Images in den Veröffentlichungen. +Siehe auch:

+ +

Zudem ist da noch Pflege des Build Systems (siehe oben), sowie +Dokumentation welche wir sehr ernst nehmen. Dokumentation ist +wichtig, in jedem Projekt.

+

Hilfe für Benutzer ist ebenso wichtig. Bleibe im IRC Chat, +und falls Du kompetent genug bist jemandem bei seinem Problem zu helfen +(oder bereit mit der Person gemeinsam zu lernen), dann ist dies ein +wichtiger Beitrag zum Projekt. Viele Leute fragen zudem unter dem +Subreddit r/libreboot nach Hilfe.

+

Eine Liste mit Bugs gibt es unter Bug Tracker.

+

Sofern Du einen Bug findest oder einen Fix hast, hier sind Anleitungen um Patches zu schicken, +oder Du kannst davon berichten. Diese Website ist zudem in Markdown +geschrieben und verfügbar in einem separaten Repository für +welches Du auch Patches schicken kannst.

+

Sämtliche Diskussionen über Entwicklung sowie Hilfe für Nutzer findet +im IRC Kanal statt. Mehr Informationen gibt es unter Kontakt.

+

Übersetzungen für +libreboot.org benötigt

+

Libreboot hat derzeit übersetzte Webseiten in ukrainisch und +französisch (aber bislang nicht für alle Seiten für keine der +Sprachen)

+

Sofern Du mit Übersetzungen helfen möchtest, kannst Du Seiten +übersetzen, existierende Übersetzungen überarbeiten oder deine +übersetzten Versionen schicken. Für Anleitungen, siehe bitte hier:

+

Wie man Übersetzungen für +libreboot.org bereitstellt

+

Auch wenn jemand bereits an einer Übersetzung in einer bestimmten +Sprache arbeitet, so können wir immer mehrere Leute gebrauchen. Desto +mehr desto besser!

+ +

Markdown-Datei: https://libreboot.org/index.de.md

+

Website karte

+

Diese HTML-Seite wurde von untitled static site generator +erstellt.

+
+
+ + diff --git a/site/index.de.md b/site/index.de.md index d80c421..91146bf 100644 --- a/site/index.de.md +++ b/site/index.de.md @@ -15,9 +15,9 @@ und [Libera](https://libera.chat/) IRC. -**NEUESTE VERSION: Die neueste Version von Libreboot ist 20230625, veröffentlicht am -25. Juni 2023. -Siehe auch: [Libreboot 20230625 release announcement](news/libreboot20230625.md).** +**NEUESTE VERSION: Die neueste Version von Libreboot ist 20231021, veröffentlicht am +21. Oktober 2023. +Siehe auch: [Libreboot 20231021 release announcement](news/libreboot20231021.md).** Warum solltest Du *Libreboot* verwenden? ---------------------------- diff --git a/site/index.de.md.date b/site/index.de.md.date new file mode 100644 index 0000000..687be2e --- /dev/null +++ b/site/index.de.md.date @@ -0,0 +1 @@ +1697839978 diff --git a/site/index.fr.html b/site/index.fr.html new file mode 100644 index 0000000..7cb4f11 --- /dev/null +++ b/site/index.fr.html @@ -0,0 +1,209 @@ + + + + + + + + + + + + + + + + + + Libreboot – Projet Libreboot + + + + +
+
+
+ +

Projet Libreboot

+
+ +
+
+ +
+

English | Deutsch | Français | Italiano +| українська | 简体中文

+

Libreboot est un micrologiciel de démarrage libéré qui initialise le matériel (càd le +contrôleur mémoire, CPU, périphériques) sur des +ordinateurs x86/ARM spécifiques et lance un chargeur d’amorçage pour +votre système d’exploitation. Linux et BSD sont bien supportés. C’est un remplacement pour +le micrologiciel UEFI/BIOS propriétaire. Des canaux d’aide sont +disponibles dans le canal #libreboot sur le serveur +IRC Libera.

+

+

NOUVELLE VERSION: La dernière version est Libreboot 20231021, sortie le 21 +octobre 2023.

+

Pourquoi devriez-vous +utiliser Libreboot?

+

Libreboot vous donne des libertés que nous n’auriez pas +autrement avec d’autre micrologiciel de démarrage. Il est extremement puissant et configurable pour plein de cas +d’utilisations.

+

Vous avez des droits. Un droit à la vie privée, liberté de pensée, +liberté d’espression et le droit de lire. Dans ce contexte là, Libreboot +vous permet d’avoir ces droits. Votre liberté compte. Le Droit à la réparation +est important. Beaucoup de personnes utilisent un micrologiciel de +démarrage propriétare (non libre), même si ils utilisent un système d’exploitation libre. Les +micrologiciels propriétaires contiennent +souvent des portes dérobées et peuvent être +instable. Libreboot a été fondé en Décembre 2013 avec le but de rendre +le libre au niveau du micrologiciel accessible pour les utilisateurs +non-techniques.

+

Libreboot utilise coreboot +pour l’initialisation +matérielle Coreboot est renommé comme être difficilement installable +par des utilisateurs non technique; il se charge seulement de +l’initialisation basique puis bascule sur un programme de charge utile (par ex. +GRUB, Tianocore), qui doit lui aussi +être configuré. Libreboot règle ce problème; c’est une +distribution de coreboot avec un système +de compilation automatisé, crééant des images ROM complètes +pour une installation plus robuste. De la documentation est +disponible.

+

De quelle façon +Libreboot diffère de Coreboot?

+

+

Contrairement à l’opinion populaire, le but principal de Libreboot +n’est pas de fournir un Coreboot déblobbé; ceci n’est simplement qu’une +des politiques de Libreboot, une importante certes, mais qui n’est qu’un +aspect mineur de Libreboot.

+

De la même façon que Alpine Linux est une distribution +Linux, Libreboot est une distribution coreboot. Si vous voulez +compilé une image ROM en partant des bases, vous devez alors effectuer +une configuration experte de Coreboot, GRUB et n’importe quel autre +logiciel dont vous avez besoin afin de préparer la ROM. Avec +Libreboot, vous pouvez télécharger la source depuis Git ou une +archive, exécuter make etça compilera une image ROM +entières. Le système de compilation automatisé de Libreboot nommé +lbmk (Libreboot MaKe), compile ces images ROM +automatiquement, sans besoin d’entrées utilisateur or intervention +requise. La configuration est faite à l’avance.

+

Si vous devriez compiler du coreboot classique sans utiliser le +système de build automatisé de Libreboot, ça demanderait bien plus +d’effort et de connaissances techniques décente pour écrire une +configuration qui marche.

+

Les versions de Libreboot fournissent ces images ROM pré-compilés et +vous pouvez les installez simplement, sans connaissance ou compétence +particulière à savoir, sauf suivre des +instructions simplifiés écrite pour des utilisateurs non +techniques.

+

Comment aider

+

+

The single biggest way you can help it to add new +mainboards to Libreboot, by submitting a config. Anything coreboot +supports can be integrated in Libreboot, with ROM images provided in +releases. See:

+ +

After that, there is build system maintenance (see above), and +documentation which we take seriously. Documentation is +critical, in any project.

+

User support is also critical. Stick around on IRC, and if +you’re competent to help someone with their issue (or wily enough to +learn with them), that is a great service to the project. A lot of +people also ask for user support on the r/libreboot +subreddit.

+

Vous pouvez allez voir les bugs listés sur le traqueur de +bugs.

+

Si vous trouvez un bug et avez un correctif, voici +les instructions pour envoyer des patchs, et vous pouvez aussi nous +les signaler. Par ailleurs, ce site est écrit en Markdown et hébergé +dans un dépôt séparé +où vous pouvez envoyer vos patchs.

+

La discussion sur le dévéloppement de Libreboot et le support +utilisateur se font toutes sur le canal IRC. Plus d’information est +disponible sur la page de contact.

+

Translations needed, for +libreboot.org

+

Libreboot currently has translated Web pages in Ukrainian and French +(but not for all pages, yet, on either language).

+

If you want to help with translations, you can translate pages, +update existing translations and submit your translated versions. For +instructions, please read:

+

How to submit translations for +libreboot.org

+

Even if someone is already working on translations in a given +language, we can always use multiple people. The more the merrier!

+ +

Fichier Markdown pour cette page: https://libreboot.org/index.fr.md

+

Plan du site

+

Cette page HTML a été générée par le untitled static site +generator.

+
+
+ + diff --git a/site/index.fr.md b/site/index.fr.md index 8111f1b..fe75373 100644 --- a/site/index.fr.md +++ b/site/index.fr.md @@ -13,8 +13,8 @@ dans le canal [\#libreboot](https://web.libera.chat/#libreboot) sur le serveur I -**NOUVELLE VERSION: La dernière version est [Libreboot 20230625](news/libreboot20230625.md), sortie -le 25 Juin 2023.** +**NOUVELLE VERSION: La dernière version est [Libreboot 20231021](news/libreboot20231021.md), sortie +le 21 octobre 2023.** Pourquoi devriez-vous utiliser *Libreboot*? ----------------------------------- diff --git a/site/index.fr.md.date b/site/index.fr.md.date new file mode 100644 index 0000000..23e21bc --- /dev/null +++ b/site/index.fr.md.date @@ -0,0 +1 @@ +1697839885 diff --git a/site/index.html b/site/index.html new file mode 100644 index 0000000..9606705 --- /dev/null +++ b/site/index.html @@ -0,0 +1,203 @@ + + + + + + + + + + + + + + + + + + Libreboot – Libreboot project + + + + +
+
+
+ +

Libreboot project

+
+ +
+
+ +
+

English | Deutsch | Français | Italiano +| українська | 简体中文

+

The Libreboot project provides free, open source (libre) boot +firmware based on coreboot, replacing proprietary BIOS/UEFI firmware on +specific Intel/AMD x86 and ARM based +motherboards, including laptop and desktop computers. It initialises +the hardware (e.g. memory controller, CPU, peripherals) and starts a +bootloader for your operating system. Linux +and BSD are well-supported. Help is available +via #libreboot on Libera IRC.

+

+

NEW RELEASE: The latest release is Libreboot 20231021, +released on 21 October 2023. See: Libreboot 20231021 release +announcement.

+

Why should you use +Libreboot?

+

Libreboot gives you freedoms that you otherwise +can’t get with most other boot firmware, plus faster boot speeds and better security. It’s +extremely powerful and configurable for +many use cases.

+

We believe the freedom to study, share, modify and use +software, without any restriction, is one of the fundamental human +rights that everyone must have. In this context, software +freedom matters. Your freedom matters. Education matters. Right to repair matters. +Many people use proprietary (non-libre) boot firmware, even if they use +a libre OS. Proprietary firmware +often contains backdoors, and can be buggy. The Libreboot +project was founded in December 2013, with the express purpose of making +coreboot firmware accessible for non-technical users.

+

The Libreboot project uses coreboot for hardware +initialisation. Coreboot is notoriously difficult to install for +most non-technical users; it handles only basic initialization and jumps +to a separate payload program (e.g. +GRUB, Tianocore), which must also be +configured. Libreboot solves this problem; it is a coreboot +distribution with an automated build +system that builds complete ROM images, for more robust +installation. Documentation is provided.

+

Libreboot is not a fork of +coreboot

+

+

In fact, Libreboot tries to stay as close to stock coreboot +as possible, for each board, but with many different types of +configuration provided automatically by the Libreboot build system.

+

In the same way that Alpine Linux is a Linux +distribution, Libreboot is a coreboot distribution. If you +want to build a ROM image from scratch, you otherwise have to perform +expert-level configuration of coreboot, GRUB and whatever other software +you need, to prepare the ROM image. With Libreboot, you can +literally download from Git or a source archive, and run +make, and it will build entire ROM images. An automated +build system, named lbmk (Libreboot MaKe), builds these ROM +images automatically, without any user input or intervention required. +Configuration has already been performed in advance.

+

If you were to build regular coreboot, without using Libreboot’s +automated build system, it would require a lot more intervention and +decent technical knowledge to produce a working configuration.

+

Regular binary releases of Libreboot provide these ROM images +pre-compiled, and you can simply install them, with no special knowledge +or skill except the ability to follow simplified +instructions, written for non-technical users.

+

How to help

+

+

The single biggest way you can help is to add new +mainboards in Libreboot, by submitting a config. Anything coreboot +supports can be integrated in Libreboot, with ROM images provided in +releases. See:

+ +

After that, there is build system maintenance (see above), and +documentation which we take seriously. Documentation is +critical, in any project.

+

User support is also critical. Stick around on IRC, and if +you’re competent to help someone with their issue (or wily enough to +learn with them), that is a great service to the project. A lot of +people also ask for user support on the r/libreboot +subreddit.

+

You can check bugs listed on the bug tracker.

+

If you spot a bug and have a fix, here are +instructions for how to send patches, and you can also report it. +Also, this entire website is written in Markdown and hosted in a separate repository +where you can send patches.

+

Any and all development discussion and user support are all done on +the IRC channel. More information is on the contact page.

+

Translations needed, for +libreboot.org

+

Libreboot currently has translated Web pages in Ukrainian and French +(but not for all pages, yet, on either language).

+

If you want to help with translations, you can translate pages, +update existing translations and submit your translated versions. For +instructions, please read:

+

How to submit translations for +libreboot.org

+

Even if someone is already working on translations in a given +language, we can always use multiple people. The more the merrier!

+ +

Markdown file for this page: https://libreboot.org/index.md

+

Site map

+

This HTML page was generated by the untitled static site +generator.

+
+
+ + diff --git a/site/index.it.html b/site/index.it.html new file mode 100644 index 0000000..6efb7e7 --- /dev/null +++ b/site/index.it.html @@ -0,0 +1,213 @@ + + + + + + + + + + + + + + + + + + Libreboot – Progetto Libreboot + + + + +
+
+
+ +

Progetto Libreboot

+
+ +
+
+ +
+

English | Deutsch | Français | Italiano +| українська | 简体中文

+

Il progetto Libreboot fornisce avvio libero e open source grazie al firmware +basato su coreboot, sostituendo cosi’, firmware BIOS/UEFI proprietario +su alcune schede madri basate su Intel/AMD x86 +o ARM, in computer fissi e portatili. Inizializza l’hardware +(controller di memoria, CPU, periferiche) e avvia un bootloader per il +tuo sistema operativo. Linux e BSD sono ben supportati. L’aiuto e’ disponibile sul +canale IRC #libreboot +su Libera.

+

+

ULTIMO RILASCIO: L’ultimo rilascio e’ Libreboot 20231021, +rilasciato il 21 ottobre 2023. Vedi: Libreboot 20231021 annuncio di +rilascio.

+

Per quale ragione +utilizzare Libreboot?

+

Libreboot ti permette liberta’ che non potresti +ottenere con altri firmware di boot, velocita’ di avvio maggiori e migliore sicurezza. E’ +estremamente flessibile e configurabile per +la maggior parte dei casi.

+

Noi crediamo nella liberta’ di studiare, condividere, modificare +and usare il software, senza restrizione alcuna, in quanto e’ uno +dei fondamentali diritti umani che chiunque deve avere. In questo +contesto, il software libero conta. La tua liberta’ conta. La +formazione personale conta. Il diritto di riparare +conta. Molte persone usano firmware di boot proprietario (non-libero), +anche se usano un sistema operativo +libero. Firmware proprietari spesso contengono vulnerabilita’, e possono essere difettosi. Il +progetto libreboot venne fondato nel Dicembre 2013, con lo scopo +prefissato di permettere che il firmware coreboot sia accessibile anche +per utenti con scarsa formazione tecnica.

+

Il progetto Libreboot fa uso di coreboot per l’inizializzazione +hardware. Coreboot e’ notoriamente difficile da installare per +utenti che hanno una scarsa formazione tecnica; gestisce solo +l’inizializzazione di base e successivamente carica un programma come payload (ad esempio. +GRUB, Tianocore), i quali possono essere +configurati a piacere. Libreboot risolve questo problema; e’ +una distribuzione di coreboot con un sistema di compilazione automatizzato che produce +immagini ROM complete, per una installazione piu’ robusta. +Viene fornito con apposita documentazione.

+

Libreboot non deriva da +coreboot

+

+

In effetti, Libreboot tenta di essere il piu’ possibile simile alla +versione ufficiale di coreboot, per ogni scheda, ma con diversi +tipi di configurazione forniti automaticamente dal sistema di +compilazione automatico di Libreboot.

+

Esattamente come Alpine Linux e’ una distribuzione +Linux, Libreboot e’ una distribuzione coreboot. Per fare +un immagine ROM da zero, hai bisogno di esperienza necessaria nel +configurare coreboot, GRUB e qualunque altra cosa ti serve. Con +Libreboot, che puoi scaricare da Git o da un archivio di codici +sorgenti, puoi far partire make, e questo mettera’ su +automaticamente le immagini ROM richieste. Un sistema di compilazione +automatico, chiamato lbmk (Libreboot MaKe), mettera’ su +quelle immagini ROM automaticamente, senza troppi interventi da parte +dell’utente. Le configurazioni di base sono gia’ state previste in +precedenza.

+

Se avresti voluto compilare coreboot normalmente senza il sistema di +compilazione automatico di Libreboot, ti troveresti ad affrontare molte +piu’ difficolta senza adeguate competenze tecniche per produrre una +configurazione funzionante.

+

I rilasci binari di Libreboot forniscono immagini ROM precompilate, +che puoi semplicemente installare senza troppe conoscenze tecniche o +abilita’ particolari ad eccezione del seguire semplici istruzioni scritte per chiunque.

+

Come essere d’aiuto

+

+

Il modo migliore col quale puoi aiutarci e’ quello di +aggiungere nuove schede condividendone la configurazione. +Qualunque cosa sia supportata da coreboot puo’ essere integrata in +Libreboot, con immagini ROM fornite nei rilasci. Vedi anche:

+ +

Dopo di che c’e’ da tenere seriamente in considerazione la +manutenzione della compilazione automatica (guarda sopra), e la +documentazione. La documentazione e’ critica in ogni +progetto.

+

Il supporto utente e’ inoltre un fattore critico. Resta +collegato su IRC, e se hai sufficiente esperienza puoi aiutare qualcuno +in difficolta’ (o anche imparare insieme a loro), in questo modo sarai +di grande aiuto al progetto. Un sacco di persone chiedono inoltre aiuto +nel subreddit r/libreboot.

+

Puoi controllare l’elenco dei bugs sul bug tracker.

+

Se hai notato un difetto (bug) e hai trovato una soluzione, qui puoi trovare istruzioni su come inviare delle +correzioni (patches) o puoi semplicemente farne rapporto. Inoltre +tutto questo sito internet e’ scritto in Markdown e ospitato su un repository separato, +dove puoi inviare correzioni (patches).

+

Qualunque discorso relativo a sviluppo e supporto utente viene fatto +sul canale IRC. Puoi avere piu’ informazioni sulla pagina dei contatti.

+

Servono traduzioni per +libreboot.org

+

Libreboot attualmente ha pagine Web tradotte in Ucraino and Francese +(ma non ancora in ogni pagina e per ogni lingua).

+

Se vuoi essere d’aiuto con le traduzioni, puoi tradurre le pagine, +aggiornare traduzioni esistenti e condividere le tue versioni tradotte. +Per saperne di piu’ puoi leggere: come +condividere traduzioni per libreboot.org

+

Anche se qualcuno sta gia’ lavorando sulle traduzioni in una +determinata lingua, possiamo sempre avvalerci di piu’ contributori. Piu’ +siamo e meglio e’!

+ +

Markdown file: https://libreboot.org/index.it.md

+

Site map

+

This HTML page was generated by the untitled static site +generator.

+
+
+ + diff --git a/site/index.it.md b/site/index.it.md index a85c6b6..1e29f09 100644 --- a/site/index.it.md +++ b/site/index.it.md @@ -14,8 +14,8 @@ su [Libera](https://libera.chat/). -**ULTIMO RILASCIO: L'ultimo rilascio e' Libreboot 20230625, rilasciato il 25 Giugno 2023. -Vedi: [Libreboot 20230625 annuncio di rilascio](news/libreboot20230625.md).** +**ULTIMO RILASCIO: L'ultimo rilascio e' Libreboot 20231021, rilasciato il 21 ottobre 2023. +Vedi: [Libreboot 20231021 annuncio di rilascio](news/libreboot20231021.md).** Per quale ragione utilizzare *Libreboot*? ----------------------------------------- @@ -116,4 +116,4 @@ e condividere le tue versioni tradotte. Per saperne di piu' puoi leggere: [come condividere traduzioni per libreboot.org](news/translations.md) Anche se qualcuno sta gia' lavorando sulle traduzioni in una determinata lingua, -possiamo sempre avvalerci di piu' contributori. Piu' siamo e meglio e'! \ No newline at end of file +possiamo sempre avvalerci di piu' contributori. Piu' siamo e meglio e'! diff --git a/site/index.it.md.date b/site/index.it.md.date new file mode 100644 index 0000000..7103e44 --- /dev/null +++ b/site/index.it.md.date @@ -0,0 +1 @@ +1697839851 diff --git a/site/index.md b/site/index.md index 5c83942..75ae416 100644 --- a/site/index.md +++ b/site/index.md @@ -15,9 +15,9 @@ on [Libera](https://libera.chat/) IRC. -**NEW RELEASE: The latest release is Libreboot 20230625, released on -25 June 2023. -See: [Libreboot 20230625 release announcement](news/libreboot20230625.md).** +**NEW RELEASE: The latest release is Libreboot 20231021, released on +21 October 2023. +See: [Libreboot 20231021 release announcement](news/libreboot20231021.md).** Why should you use *Libreboot*? ---------------------------- diff --git a/site/index.md.date b/site/index.md.date new file mode 100644 index 0000000..9c64fe7 --- /dev/null +++ b/site/index.md.date @@ -0,0 +1 @@ +1697839617 diff --git a/site/index.uk.html b/site/index.uk.html new file mode 100644 index 0000000..c8803c1 --- /dev/null +++ b/site/index.uk.html @@ -0,0 +1,204 @@ + + + + + + + + + + + + + + + + + + Libreboot – Проект Libreboot + + + + +
+
+
+ +

Проект Libreboot

+
+ +
+
+ +
+

English | Deutsch | Français | Italiano +| українська | 简体中文

+

Проект Libreboot надає вільну завантажувальну +прошивку, яка ініціалізує апаратне забезпечення (наприклад, +контролер пам’яті, ЦП, периферію) на конкретних +цілях Intel/AMD x86 та ARM, що потім розпочинає завантажувач для +вашої операційної системи. Linux та BSD добре підтримуються. Це заміняє пропрієтарну +BIOS/UEFI прошивку. Допомога доступна через #libreboot на Libera IRC.

+

+

НОВИЙ ВИПУСК: Останній випуск Libreboot 20231021, випущено 21 +жовтень 2023. Дивіться: Оголошення +про випуск Libreboot 20231021.

+

Чому вам варто +використовувати Libreboot?

+

Libreboot надає вам свободи, які в іншому випадку +ви не можете отримати з більшістю інших завантажувальних прошивок. Він +надзвичайно потужний та налаштовується для багатьох випадків +використання.

+

У вас є права. Право на конфіденційність, свобода мислення, свобода +висловлювання та право читати. В цьому контексті, Libreboot надає вам ці +права. Ваша свобода має значення. Право на ремонт має +значення. Багато людей використовують пропрієтарну (невільну) +завантажувальну прошивку, навіть якщо вони використовують вільну операційну систему. +Пропрієтарна прошивка часто містить лазівки, та може бути глючною. Проект +Libreboot було засновано в грудні 2013 року, з явною метою зробити +прошивку coreboot доступною для нетехнічних користувачів.

+

Проект Libreboot використовує coreboot для ініціалізації +апаратного забезпечення. Coreboot помітно складний для встановлення +для більшості нетехнічних користувачів; він виконує тільки базову +ініціалізацію та перестрибує до окремої програми корисного навантаження +(наприклад, GRUB, Tianocore), які також мають бути +налаштованими. Програмне забезпечення Libreboot вирішує цю +проблему; це дистрибутив coreboot з автоматизованою системою побудови, +яка збирає завершені образи ROM, для більш надійної установки. +Документація надається.

+

Чим +Libreboot відрізняється від звичайного coreboot?

+

+

Таким же самим чином, як Debian це дистрибутив Linux, +Libreboot це дистрибутив coreboot. Якщо ви хочете зібрати образ +ROM з нуля, вам інакше довелось би виконати налаштування експертного +рівня coreboot, GRUB та будь-якого іншого потрібного програмного +забезпечення, для підготування образа ROM. З Libreboot, ви +можете буквально завантажити з Git або архіву джерельного коду, та +запустити make, і це побудує всі образи ROM. Автоматизована +система побудови, названа lbmk (Libreboot MaKe), збирає ці +образи ROM автоматично, без будь-якого вводу користувача або потрібного +втручання. Налаштування вже виконано заздалегідь.

+

Якщо би ви збирали звичайний coreboot, не використовуючи +автоматизовану систему побудови Libreboot, це вимагало би набагато +більше втручання та гідних технічних знань для створення робочої +конфігурації.

+

Звичайні бінарні випуски Libreboot надають ці образи ROM попередньо +зібраними, і ви можете просто встановити їх, не маючи спеціальних знань +або навичок, окрім можливості слідувати спрощеним інструкціям, написаним для нетехнічних +користувачів.

+

Як допомогти

+

+

Єдиний найбільший шлях, яким ви можете допомогти є +додавання нових материнських плат до Libreboot, за допомогою +відправки конфігурації. Що завгодно, що підтримує coreboot може бути +інтегровано в Libreboot, з образами ROM наданими в випусках. +Дивіться:

+ +

Після цього, є обслуговування системи побудови (дивіться зверху), та +документація, до якої ми ставимося серйозно. Документація є +критичною, в будь-якому проекті.

+

Користувацька ідтримка є також критичною. Тримайтесь поряд +на IRC, і якщо ви компетентні допомогти комусь з їх проблемним питанням +(або досить вправні, щоб навчитись з ними), це є чудовою послугою для +проекту. Багато людей також запитує підтримки користувачів на subreddit +r/libreboot.

+

Ви можете перевірити помилки, перелічені в системі відстеження +помилок.

+

Якщо ви помітили помилку і маєте виправлення, ось інструкції щодо надсилання виправлень, а +також ви можете повідомити про це. Також, весь цей веб-сайт написаний +Markdown та розміщений в окремому сховищі, де ви +можете надсилати виправлення.

+

Усі обговорення розробки та підтримка користувачів відбуваються на +IRC каналі. Більше інформації на сторінці +зворотнього зв’язку.

+

Переклади потрібні, для +libreboot.org

+

Libreboot наразі має перекладеними веб-сторінки українською та +французькою (але не для всіх сторінок, ще, жодною з мов).

+

Якщо ви бажаєте допомогти з перекладами, ви можете перекласти +сторінки, оновити існуючи переклади та надати ваші перекладені версії. +Для інструкцій, будь ласка прочитайте:

+

Як надати переклади для +libreboot.org

+

Навіть якщо хтось вже працює над перекладами даною мовою, ми можемо +завжди використовувати багато людей. Чим більше, тим краще!

+ +

Markdown: https://libreboot.org/index.uk.md

+

Індекс сайта

+

Ця сторінка була створена з untitled static site +generator.

+
+
+ + diff --git a/site/index.uk.md b/site/index.uk.md index a0bd249..c93d44a 100644 --- a/site/index.uk.md +++ b/site/index.uk.md @@ -15,8 +15,8 @@ x-toc-enable: true -**НОВИЙ ВИПУСК: Останній випуск Libreboot 20230625, випущено 25 червня 2023. -Дивіться: [Оголошення про випуск Libreboot 20230625](news/libreboot20230625.md).** +**НОВИЙ ВИПУСК: Останній випуск Libreboot 20231021, випущено 21 жовтень 2023. +Дивіться: [Оголошення про випуск Libreboot 20231021](news/libreboot20231021.md).** Чому вам варто використовувати *Libreboot*? ---------------------------- diff --git a/site/index.uk.md.date b/site/index.uk.md.date new file mode 100644 index 0000000..6058e77 --- /dev/null +++ b/site/index.uk.md.date @@ -0,0 +1 @@ +1697839522 diff --git a/site/index.zh-cn.html b/site/index.zh-cn.html new file mode 100644 index 0000000..ad87eb0 --- /dev/null +++ b/site/index.zh-cn.html @@ -0,0 +1,171 @@ + + + + + + + + + + + + + + + + + + Libreboot – Libreboot 项目 + + + + +
+
+
+ +

Libreboot 项目

+
+ +
+
+ +
+

English | Deutsch | Français | Italiano +| українська | 简体中文

+

Libreboot 项目基于 coreboot 提供了自由且开源的引导固件，替代了特定基于 +Intel/AMD x86 及 ARM 的主板（包括笔记本和桌面计算机）上的专有 BIOS/UEFI +固件。它首先对硬件（如内存控制器、CPU、外设）进行初始化，然后为操作系统启动 +bootloader。本项目对 Linux 和 BSD 支持良好。寻求帮助，可以前往 Libera IRC 上的 #libreboot 频道。

+

+

新版发布: 最新版本 Libreboot 20231021 已在 2023 年 10 月 21 +日发布。详见: Libreboot 20231021 +发布公告.

+

为什么要使用 Libreboot?

+

Libreboot 赋予了你自由，而这等自由，是你用其他引导固件得不到的。同时，它的启动速度更加快，安全性也更加高。在各种情况下使用，它都十分强大，具有高度可配置性。

+

我们相信，不受限制地研究、分享、修改及使用软件的自由，是每个人都必须享有的基本人权的一部分。这时，软件自由至关重要。你的自由至关重要。教育至关重要。修理权至关重要。尽管许多人在用自由的操作系统，但他们用的引导固件却是专有（非自由）的。专有固件常常包含了后门，并且也可能出问题。2013 年 12 +月，我们建立了 Libreboot 项目，目的是让不懂技术的用户能使用 coreboot +固件。

+

Libreboot 项目使用 coreboot +来初始化硬件。对大部分不懂技术的用户来说，coreboot +是出了名地难安装；它只处理了基础的初始化，然后跳转进入单独的 payload 程序（例如 GRUB、Tianocore），而后者也需要进行配置。Libreboot +解决了这样的问题；他是一个 coreboot 发行版，配有自动构建系统，能够构建完整的 ROM +镜像，从而让安装更加稳定。另有文档可参考。

+

Libreboot 不是 coreboot +的分支

+

+

事实上，Libreboot 对每一块主板，都尽可能保持与标准的 +coreboot 接近，但 Libreboot 构建系统也自动提供了许多不同类型的配置。

+

Libreboot 是一个 coreboot 发行版，就好比 Alpine +Linux 是一个 Linux 发行版。如果你想要从零开始构建 ROM +镜像，那你需要对 coreboot、GRUB +以及其他所需软件进行专业级别的配置，才能准备好 ROM 镜像。有了 +Libreboot，你只需要下载 Git 仓库或者源代码归档，然后运行 +make，接着就能构建整个 ROM 镜像。一套自动构建系统，名为 +lbmk（Libreboot Make），将自动构建 ROM +镜像，而无需任何用户输入或干预。配置已经提前完成。

+

如果你要构建常规的 coreboot，而不使用 Libreboot +的自动构建系统，那么需要有很多的干预以及相当的技术知识，才能写出一份能工作的配置。

+

Libreboot 的常规二进制版本，提供了这些预编译的 ROM +镜像。你可以轻松安装它们，而无需特别的知识和技能，只要能遵循写给非技术用户的简单指南。

+

如何帮忙

+

+

要帮忙的话，最最好的方式，就是通过提交配置文件，来为 +Libreboot 添加新的主板。coreboot 支持的任何东西，都能并入 +Libreboot，并且带有 ROM 镜像。见：

+ +

然后，就是构建系统的维护（见下）以及重要的文档。文档十分重要，在任何项目都是如此。

+

用户支持也十分重要。多瞧一瞧 +IRC，如果你有能力帮别人解决问题（或者愿意跟他们一起学习），那对本项目的贡献会很大。许多人也在 +reddit 版块 r/libreboot 寻求用户支持。

+

你可以检查缺陷追踪系统列出的缺陷。

+

如果你发现了一个缺陷，并且有解决方案，这里说明了发布补丁的方法，你也可以提交报告。同时，本站完全使用 +Markdown 编写，并托管在了一个单独的仓库，你可以在那里发送补丁。

+

所有开发方面的讨论以及用户支持，都是在 IRC +频道上完成的。了解更多，可以查看联系页面。

+

libreboot.org 需要翻译

+

Libreboot +目前有乌克兰语和法语的网页翻译（但两个语言都还没翻译完所有页面）。

+

如果你想帮忙翻译，你可以翻译网页、更新已有翻译并提交你的译本。请阅读下面的指南：

+

如何提交 libreboot.org 翻译

+

即使已经有人在进行某个语言的翻译了，我们也总是欢迎更多人。多多益善！

+ +

本页面的 Markdown 文件： https://libreboot.org/index.zh-cn.md

+

网站地图

+

本 HTML 页面使用 untitled +静态网站生成器生成。

+
+
+ + diff --git a/site/index.zh-cn.md b/site/index.zh-cn.md index a307690..ad8dbe8 100644 --- a/site/index.zh-cn.md +++ b/site/index.zh-cn.md @@ -7,7 +7,7 @@ x-toc-enable: true -**新版发布: 最新版本 Libreboot 20230625 已在 2023 年 6 月 25 日发布。详见: [Libreboot 20230625 发布公告](news/libreboot20230625.md).** +**新版发布: 最新版本 Libreboot 20231021 已在 2023 年 10 月 21 日发布。详见: [Libreboot 20231021 发布公告](news/libreboot20231021.md).** 为什么要使用 *Libreboot*? ---------------------------- diff --git a/site/index.zh-cn.md.date b/site/index.zh-cn.md.date new file mode 100644 index 0000000..aeb6076 --- /dev/null +++ b/site/index.zh-cn.md.date @@ -0,0 +1 @@ +1697839453 diff --git a/site/news/argon2.md b/site/news/argon2.md index b693b43..1703ddc 100644 --- a/site/news/argon2.md +++ b/site/news/argon2.md @@ -49,11 +49,14 @@ setup. How to get it ------------- -This is unavailable in the current Libreboot 20230625 release, but will be -available in the next Libreboot release. For now, you can compile a ROM image -yourself from the Libreboot build system, lbmk, like so: +This is unavailable in the Libreboot 20230625 release, but will be +available in the next Libreboot release. -[How to build Libreboot ROM images from source](../docs/build/) +**UPDATE (21 October 2023): +This is available in Libreboot 20231021, and releases after that. Alternatively, +you may still compile a ROM image yourself from the Libreboot build system. See:** + +**[How to build Libreboot ROM images from source](../docs/build/)** Further reading =============== diff --git a/site/news/censored-libreboot20230710.md b/site/news/censored-libreboot20230710.md index 847d8cf..be61008 100644 --- a/site/news/censored-libreboot20230710.md +++ b/site/news/censored-libreboot20230710.md @@ -5,6 +5,9 @@ Warning ======= +**Update 21 October 2023: This is quite obsolete now, because +[Libreboot 20231021](libreboot20231021.md) is out.** + **This release is *not* recommended for general use. You should still use the recent [Libreboot 20230625](libreboot20230625.md) release, which is the current stable release. Please also read the [Binary Blob Reduction diff --git a/site/news/e6400nvidia.md b/site/news/e6400nvidia.md index 1b3eff9..c960265 100644 --- a/site/news/e6400nvidia.md +++ b/site/news/e6400nvidia.md @@ -25,9 +25,12 @@ available for variants with GPU: Nvidia Quadro NVS 160M. The Dell Latitude 6400 XFR (rugged variant) was also tested today (Intel graphics) and confirmed working in Libreboot as of release 20230423. -The *Nvidia* variants are *not* supported in Libreboot 20230423 or 20230625. -Support is available in an experimental branch of Libreboot. 6400 XFR -testing+photo provided, courtesy Mark Cornick (`mcornick` on Libreboot IRC). +**UPDATE 21 October 2023: The Nvidia GPU variant is supported +in [Libreboot 20231021](libreboot20231021.md) and newer - versions older +than Libreboot 20231021 only support the Intel GPU variant.** + +The 6400 XFR testing+photo was provided, courtesy Mark Cornick (`mcornick` on +Libreboot IRC). Dell Latitude E6400 with Nvidia GPU =================================== diff --git a/site/news/gnuboot.md b/site/news/gnuboot.md index 037a156..9eb1ea9 100644 --- a/site/news/gnuboot.md +++ b/site/news/gnuboot.md @@ -2,6 +2,35 @@ % Leah Rowe % 17 July 2023 +**UPDATE 21 October 2023: [Libreboot 20231021](libreboot20231021.md) is out, +and it's vastly superior to Libreboot 20230625 or nonGeNUine Boot 20230717; +and GNU Boot 0.1 RC is still not much different than the state GNU Boot was in +at the time of the article below. GNU Boot 0.1 RC (the latest version of GNU +Boot as of 21 October 2023) is essentially just Libreboot 20220710 plus patches +I made for them enabling KGPE-D16 to build correctly on modern Linux distros.** + +**It's likely that another FSDG-compatible variant of Libreboot will be made, +again for fun, based on Libreboot 20231021. Watch this space! tl;dr Libreboot +is vastly superior in the October 2023 revision compared to June 2023, and +the June 2023 revision is still superior to GNU Boot (still uses newer coreboot +revisions, has better error handling in the build system, builds more efficiently +and is generally just better, because it's literally about 8 months ahead in +development, and supports more hardware such as gru chromebooks with u-boot or +the Dell Latitude E6400 - which GNU Boot still doesn't support. Libreboot today +is now lightyears ahead, and the recent October 2023 release has coreboot +revisions 2 years ahead of the ones used in GNU Boot's default coreboot tree.** + +**Two years. Anyway, the original article is as follows (prior to the above):** + +The purpose of the original article below was to promote my own FSDG-compliant +fork of Libreboot 20230625, which I released as Censored-Libreboot 20230710 and +then nonGeNUine Boot 20230717, with the intent that *GNU Boot* re-use the work, +but they never re-used any of it except for my D16 build fixes, and one or two +minor things. + +Original article as it was written, 17 July 2023: +================================================= + People have been waiting for me to break the silence about this. I go on about it on IRC. This article is intended to address it once and for all, officially. diff --git a/site/news/libreboot20231021.md b/site/news/libreboot20231021.md index 2e3ee6f..61f1956 100644 --- a/site/news/libreboot20231021.md +++ b/site/news/libreboot20231021.md @@ -1115,26 +1115,3 @@ Downloads You can find this release on the downloads page. At the time of this announcement, some of the rsync mirrors may not have it yet, so please check another one if your favourite one doesn't have it. - -Post-release errata -=================== - -When building ROM images from the release archives, the following error -is observed in some cases, depending on distro: - -``` -In file included from src/lib/version.c:4: -build/build.h:10:32: error: 'libreboot' undeclared here (not in a function) - 10 | #define COREBOOT_MAJOR_VERSION libreboot-20230625 - | ^~~~~~~~~ -src/lib/version.c:35:46: note: in expansion of macro 'COREBOOT_MAJOR_VERSION' - 35 | const unsigned int coreboot_major_revision = COREBOOT_MAJOR_VERSION; - | ^~~~~~~~~~~~~~~~~~~~~~ -``` - -This happened when a user tried to build for ThinkPad W541 on an Arch Linux -system. The fix is available here: - - - -Apply this patch to your local release archive, and it should fix the issue.