diff --git a/site/docs/build/index.md b/site/docs/build/index.md index 7b7a9e5e80932fad65a34cbd991f11ac6599a41f..b324b91fa58c5dc40fe75eda21a0e448bebb1c2c 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: - -<https://browse.libreboot.org/lbmk.git/patch/?id=f34e07ae27e3e6e8508cdebcbd09fdf73fca302d> - -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 e2a0eeadb4e29aaec09f51ec893a1e0a65f54e2c..100eda9bf4a4648f93db65b15da404b4e3b49886 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: - -<https://browse.libreboot.org/lbmk.git/patch/?id=f34e07ae27e3e6e8508cdebcbd09fdf73fca302d> - -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 ef0f701fda13fec076483f38b80367334771a016..f1fcdc8c2acfc72996b0d0555e7e4c912f3f83fd 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 db9e6a1cb44a5b20b8b13e960e892c1ede1d9a73..77b44f8e9784908781b5180893dd3f61089639db 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 f6e1f5d262adc0bb2ff6bafe94f1b81b8083da9b..b963e2981d6a8fa55d36e013b8b697526c421f6e 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: <https://support.hp.com/gb-en/document/c03374369> diff --git a/site/docs/hardware/t1650.md b/site/docs/hardware/t1650.md index 7cec1f4ea0806b7c5f8690fba8ea936952d17c3f..f3cde3195b87529a6bfd1bbecd1991d0c89ea790 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: <https://i.dell.com/sites/csdocuments/Shared-Content_data-Sheets_Documents/en/uk/Dell_Precision_T1650_Spec_Sheet.pdf> diff --git a/site/docs/install/e6400.md b/site/docs/install/e6400.md index 2144d72ae2b8310233bbe87518c60c492c19abcc..efc813a1989bc7d1d0f5badd15c16832ed9c870e 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 ab74b68b9d7eefe8bafcc3107d0bfe402f2e6496..0000000000000000000000000000000000000000 --- 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 0d2d6485466f843b8edb002c8b899f74babeecf2..b47fa02ccedcb1d454f1cd5ad0691cec5494444f 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 af3c64dbd5ce09782b61ff58f19f16ad9da44205..737df0c5c550640d3eac931f476615bfe9d397fc 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 e8533246bedf5cfa38e37093df47f5f56bf60da2..0000000000000000000000000000000000000000 --- 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 0000000000000000000000000000000000000000..66f061b26d5c78f8424302437924d7963ad2025f --- /dev/null +++ b/site/download.html @@ -0,0 +1,294 @@ +<!DOCTYPE html> +<html lang="en" dir="ltr"> +<head> + <meta charset="utf-8"> + <meta name="generator" content="pandoc"> + <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes"> + +<!-- anti-social media tags --> + <meta property="og:title" content="Libreboot – Downloads"> + <meta property="og:type" content="article" /> + <meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg"> + <meta property="og:url" content="https://libreboot.org/download.html"> + <meta name="twitter:card" content="summary_large_image"> + <meta property="og:description" content="Libreboot – Downloads"> + <meta property="og:site_name" content="Libreboot – Downloads"> + <meta name="twitter:image:alt" content="Libreboot – Downloads"> + + <title>Libreboot – Downloads</title> + <link rel="stylesheet" href="/global.css"> +<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/> +</head> +<body> +<div class="page"> +<header> +<div class="title"> +<p class="title-logo"> +<img loading="lazy" class="title-logo" alt="Libreboot logo" src="/favicon.ico" /> +</p> +<h1 class="title">Downloads</h1> +</div> +<ul> +<li><a href="/">Home</a></li> +<li><a href="/faq.html">FAQ</a></li> +<li><strong><a href="/freedom-status.html">Freedom status</a></strong></li> +<li><strong><a href="/download.html">Download</a></strong></li> +<li><a href="/docs/install/">Install</a></li> +<li><a href="/docs/">Docs</a></li> +<li><a href="/news/">News</a></li> +<li><a href="https://codeberg.org/libreboot/lbmk/issues">Bugs</a></li> +<li><a href="/git.html">Send patch</a></li> +<li><strong><a href="https://www.patreon.com/libreleah">Donate</a></strong></li> +<li><a href="/contact.html">Contact</a></li> +<li><strong><a href="https://minifree.org/">Buy preinstalled</a></strong></li> +</ul> +<hr/> +</header> +<nav id="TOC"> +<h1>Navigate this page:</h1> +<ul> +<li><a +href="#read-this-before-updating-libreboot-or-you-might-brick-your-machine">READ +THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE</a> +<ul> +<li><a href="#gpg-signing-key">GPG signing key</a> +<ul> +<li><a href="#new-key">NEW KEY</a></li> +<li><a href="#old-key">OLD KEY:</a></li> +</ul></li> +<li><a href="#git-repository">Git repository</a></li> +<li><a href="#https">HTTPS mirrors</a></li> +<li><a href="#rsync">RSYNC mirrors</a></li> +<li><a href="#http">HTTP mirrors</a></li> +<li><a href="#ftp">FTP mirrors</a></li> +<li><a href="#statically-linked">Statically linked</a></li> +</ul></li> +</ul> +</nav> +<div class="pagetext"> +<p><a href="download.html">English</a> | <a +href="download.uk.html">українÑька</a></p> +<p><a href="./">Return to index</a></p> +<p>New releases are announced in the <a href="news/">main news +section</a>.</p> +<p>If you’re more interested in libreboot development, go to the <a +href="../git.html">libreboot development page</a>, which also includes +links to the Git repositories. The page on <a +href="docs/maintain/">/docs/maintain/</a> describes how Libreboot is put +together, and how to maintain it. If you wish to build Libreboot from +source, <a href="docs/build/">read this page</a>.</p> +<h1 +id="read-this-before-updating-libreboot-or-you-might-brick-your-machine">READ +THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE</h1> +<p><strong>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:</strong></p> +<p><strong><a href="docs/install/ivy_has_common.html">Insert vendor +files on Sandybridge/Ivybridge/Haswell</a></strong></p> +<p>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 <em>deleted</em> 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: <a href="docs/build/">Libreboot +build instructions</a></p> +<p>This isn’t required on <em>all</em> 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.</p> +<div class="h"><h2 id="gpg-signing-key">GPG signing key</h2><a aria-hidden="true" href="#gpg-signing-key">[link]</a></div> +<p><strong>The latest release is Libreboot 20231021, under the +<code>testing</code> directory.</strong></p> +<div class="h"><h3 id="new-key">NEW KEY</h3><a aria-hidden="true" href="#new-key">[link]</a></div> +<p>Full key fingerprint: +<code>98CC DDF8 E560 47F4 75C0 44BD D0C6 2464 FA8B 4856</code></p> +<p>This key is for Libreboot releases <em>after</em> the 20160907 +release.</p> +<p>Download the key here: <a href="lbkey.asc">lbkey.asc</a></p> +<p>Libreboot releases are signed using GPG.</p> +<div class="h"><h3 id="old-key">OLD KEY:</h3><a aria-hidden="true" href="#old-key">[link]</a></div> +<p>This key is for Libreboot 20160907, and releases older than +20160907:</p> +<p>Full key fingerprint: CDC9 CAE3 2CB4 B7FC 84FD C804 969A 9795 05E8 +C5B2</p> +<p>The GPG key can also be downloaded with this exported dump of the +pubkey: <a href="lbkeyold.asc">lbkeyold.asc</a>.</p> +<pre><code>sha512sum -c sha512sum.txt +gpg --verify sha512sum.txt.sig</code></pre> +<div class="h"><h2 id="git-repository">Git repository</h2><a aria-hidden="true" href="#git-repository">[link]</a></div> +<p>Links to regular release archives are listed on this page.</p> +<p>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:</p> +<p><a href="git.html">How to download Libreboot from Git</a></p> +<div class="h"><h2 id="https">HTTPS mirrors</h2><a aria-hidden="true" href="#https">[link]</a></div> +<p><strong>The latest release is Libreboot 20231021, under the +<code>testing</code> directory.</strong></p> +<p>These mirrors are recommended, since they use TLS (https://) +encryption.</p> +<p>You can download Libreboot from these mirrors:</p> +<ul> +<li><a href="https://www.mirrorservice.org/sites/libreboot.org/release/" +class="uri">https://www.mirrorservice.org/sites/libreboot.org/release/</a> +(University of Kent, UK)</li> +<li><a href="https://mirrors.mit.edu/libreboot/" +class="uri">https://mirrors.mit.edu/libreboot/</a> (MIT university, +USA)</li> +<li><a href="https://mirror.math.princeton.edu/pub/libreboot/" +class="uri">https://mirror.math.princeton.edu/pub/libreboot/</a> +(Princeton university, USA)</li> +<li><a href="https://mirror.shapovalov.tech/libreboot/" +class="uri">https://mirror.shapovalov.tech/libreboot/</a> +(shapovalov.tech, Ukraine)</li> +<li><a href="https://mirror.koddos.net/libreboot/" +class="uri">https://mirror.koddos.net/libreboot/</a> (koddos.net, +Netherlands)</li> +<li><a href="https://mirror-hk.koddos.net/libreboot/" +class="uri">https://mirror-hk.koddos.net/libreboot/</a> (koddos.net, +Hong Kong)</li> +<li><a href="https://mirror.cyberbits.eu/libreboot/" +class="uri">https://mirror.cyberbits.eu/libreboot/</a> (cyberbits.eu, +France)</li> +<li><a href="https://mirror.mangohost.net/libreboot/" +class="uri">https://mirror.mangohost.net/libreboot/</a> (mangohost.net, +Moldova)</li> +</ul> +<div class="h"><h2 id="rsync">RSYNC mirrors</h2><a aria-hidden="true" href="#rsync">[link]</a></div> +<p>The following rsync mirrors are available publicly:</p> +<ul> +<li><a href="rsync://rsync.mirrorservice.org/libreboot.org/release/" +class="uri">rsync://rsync.mirrorservice.org/libreboot.org/release/</a> +(University of Kent, UK)</li> +<li><a href="rsync://mirror.math.princeton.edu/pub/libreboot/" +class="uri">rsync://mirror.math.princeton.edu/pub/libreboot/</a> +(Princeton university, USA)</li> +<li><a href="rsync://rsync.shapovalov.tech/libreboot/" +class="uri">rsync://rsync.shapovalov.tech/libreboot/</a> +(shapovalov.tech, Ukraine)</li> +<li><a href="rsync://ftp.linux.ro/libreboot/" +class="uri">rsync://ftp.linux.ro/libreboot/</a> (linux.ro, Romania)</li> +<li><a href="rsync://mirror.koddos.net/libreboot/" +class="uri">rsync://mirror.koddos.net/libreboot/</a> (koddos.net, +Netherlands)</li> +<li><a href="rsync://mirror-hk.koddos.net/libreboot/" +class="uri">rsync://mirror-hk.koddos.net/libreboot/</a> (koddos.net, +Hong Kong)</li> +<li><a href="rsync://mirror.mangohost.net/libreboot/" +class="uri">rsync://mirror.mangohost.net/libreboot/</a> (mangohost.net, +Moldova)</li> +</ul> +<p>Are you running a mirror? Contact the libreboot project, and the link +will be added to this page!</p> +<p>You can make your rsync mirror available via your web server, and +also configure your <em>own</em> mirror to be accessible via rsync. +There are many resources online that show you how to set up an rsync +server.</p> +<p>How to create your own rsync mirror:</p> +<p>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.</p> +<p>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.</p> +<p><em>It is highly recommended that you use the libreboot.org +mirror</em>, 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.</p> +<p>Before you create the mirror, make a directory on your web server. +For example:</p> +<pre><code>mkdir /var/www/html/libreboot/</code></pre> +<p>Now you can run rsync, for instance:</p> +<pre><code>rsync -avz --delete-after rsync://rsync.libreboot.org/mirrormirror/ /var/www/html/libreboot/</code></pre> +<p>You might put this in an hourly crontab. For example:</p> +<pre><code>crontab -e</code></pre> +<p>Then in crontab, add this line and save/exit (hourly crontab):</p> +<pre><code>0 * * * * rsync -avz --delete-after rsync://rsync.libreboot.org/mirrormirror/ /var/www/html/libreboot/</code></pre> +<p><strong>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.</strong></p> +<p><strong>NOTE: <code>rsync.libreboot.org</code> 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.</strong></p> +<p><strong>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.</strong></p> +<p>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: <a +href="https://man7.org/linux/man-pages/man5/crontab.5.html" +class="uri">https://man7.org/linux/man-pages/man5/crontab.5.html</a></p> +<div class="h"><h2 id="http">HTTP mirrors</h2><a aria-hidden="true" href="#http">[link]</a></div> +<p><strong>The latest release is Libreboot 20231021, under the +<code>testing</code> directory.</strong></p> +<p>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.</p> +<ul> +<li><a href="http://mirror.linux.ro/libreboot/" +class="uri">http://mirror.linux.ro/libreboot/</a> (linux.ro, +Romania)</li> +<li><a href="http://mirror.helium.in-berlin.de/libreboot/" +class="uri">http://mirror.helium.in-berlin.de/libreboot/</a> +(in-berlin.de, Germany)</li> +</ul> +<div class="h"><h2 id="ftp">FTP mirrors</h2><a aria-hidden="true" href="#ftp">[link]</a></div> +<p><strong>The latest release is Libreboot 20231021, under the +<code>testing</code> directory.</strong></p> +<p>WARNING: FTP is also unencrypted, like HTTP. The same risks are +present.</p> +<ul> +<li><a href="ftp://ftp.mirrorservice.org/sites/libreboot.org/release/" +class="uri">ftp://ftp.mirrorservice.org/sites/libreboot.org/release/</a> +(University of Kent, UK)</li> +<li><a href="ftp://ftp.linux.ro/libreboot/" +class="uri">ftp://ftp.linux.ro/libreboot/</a> (linux.ro, Romania)</li> +</ul> +<div class="h"><h2 id="statically-linked">Statically linked</h2><a aria-hidden="true" href="#statically-linked">[link]</a></div> +<p>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.</p> +<p>To comply with GPL v2, source ISOs are supplied by the Libreboot +project. You can find these source ISOs in the <code>ccsource</code> +directory on the <code>rsync</code> mirrors.</p> +<p>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.</p> +<p>These executables are utilities such as <code>flashrom</code>.</p> +<div id="footer"> +<hr /> +<ul> +<li><a href="/news/policy.html">Binary Blob Reduction Policy</a></li> +<li><a href="/git.html">Edit this page</a></li> +<li><a href="/who.html">Who develops Libreboot?</a></li> +<li><a href="/license.html">License</a></li> +<li><a href="/template-license.html">Template</a></li> +<li><a href="/logo-license.html">Logo</a></li> +<li><a href="/contrib.html">Authors</a></li> +</ul> +<hr /> +</div> +<p>Markdown file for this page: <a +href="https://libreboot.org/download.md" +class="uri">https://libreboot.org/download.md</a></p> +<p><a href="/sitemap.html">Site map</a></p> +<p>This HTML page was generated by the <a +href="https://untitled.vimuser.org/">untitled static site +generator</a>.</p> +</div> +</div> +</body> +</html> diff --git a/site/download.md b/site/download.md index a8f8943c29dcfd5dff8533cbcf929deedff377ec..3bd26c6c2b8b525b46c8c8461f8377368cddc2c5 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 0000000000000000000000000000000000000000..f6ca8f71e0d6aad66636778180ed15df1bac2d8d --- /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 0000000000000000000000000000000000000000..1e3ecd6a8fb2b3a3f387e6631f71573ed44b626c --- /dev/null +++ b/site/download.uk.html @@ -0,0 +1,299 @@ +<!DOCTYPE html> +<html lang="uk" dir="ltr"> +<head> + <meta charset="utf-8"> + <meta name="generator" content="pandoc"> + <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes"> + +<!-- anti-social media tags --> + <meta property="og:title" content="Libreboot – ЗавантаженнÑ"> + <meta property="og:type" content="article" /> + <meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg"> + <meta property="og:url" content="https://libreboot.org/download.uk.html"> + <meta name="twitter:card" content="summary_large_image"> + <meta property="og:description" content="Libreboot – ЗавантаженнÑ"> + <meta property="og:site_name" content="Libreboot – ЗавантаженнÑ"> + <meta name="twitter:image:alt" content="Libreboot – ЗавантаженнÑ"> + + <title>Libreboot – ЗавантаженнÑ</title> + <link rel="stylesheet" href="/global.css"> +<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/> +</head> +<body> +<div class="page"> +<header> +<div class="title"> +<p class="title-logo"> +<img loading="lazy" class="title-logo" alt="Логотип Libreboot" src="/favicon.ico" /> +</p> +<h1 class="title">ЗавантаженнÑ</h1> +</div> +<ul> +<li><a href="/index.uk.html">ДомашнÑ</a></li> +<li><a href="/faq.html">FAQ</a></li> +<li><strong><a href="/freedom-status.html">Ð¡Ñ‚Ð°Ñ‚ÑƒÑ Ñвободи</a></strong></li> +<li><strong><a href="/download.uk.html">ЗавантаженнÑ</a></strong></li> +<li><a href="/docs/install/">Ð’ÑтановленнÑ</a></li> +<li><a href="/docs/index.uk.html">ДокументаціÑ</a></li> +<li><a href="/news/">Ðовини</a></li> +<li><a href="https://codeberg.org/libreboot/lbmk/issues">Помилки</a></li> +<li><a href="/git.uk.html">Відправити виправленнÑ</a></li> +<li><strong><a href="https://www.patreon.com/libreleah">Пожертвувати</a></strong></li> +<li><a href="/contact.uk.html">Зв'Ñзок</a></li> +<li><strong><a href="https://minifree.org/">Придбати передвÑтановленим</a></strong></li> +</ul> +<hr/> +</header> +<nav id="TOC"> +<h1>ÐÐ°Ð²Ñ–Ð³Ð°Ñ†Ñ–Ñ Ñ†Ñ–Ñ”ÑŽ Ñторінкою:</h1> +<ul> +<li><a +href="#read-this-before-updating-libreboot-or-you-might-brick-your-machine">READ +THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE</a> +<ul> +<li><a href="#код-підпиÑу-gpg">Код підпиÑу GPG</a> +<ul> +<li><a href="#новий-ключ">ÐОВИЙ КЛЮЧ</a></li> +<li><a href="#Ñтарий-ключ">СТÐРИЙ КЛЮЧ:</a></li> +</ul></li> +<li><a href="#репозиторій-git">Репозиторій Git</a></li> +<li><a href="#https">Дзеркала HTTPS</a></li> +<li><a href="#rsync">Дзеркала RSYNC</a></li> +<li><a href="#http">Дзеркала HTTP</a></li> +<li><a href="#ftp">Дзеркала FTP</a></li> +<li><a href="#Ñтатично-звÑзані">Статично зв’Ñзані</a></li> +</ul></li> +</ul> +</nav> +<div class="pagetext"> +<p><a href="download.html">English</a> | <a +href="download.uk.html">українÑька</a></p> +<p><a href="./">попередній індекÑ</a></p> +<p>Ðові випуÑки оголошуютьÑÑ Ð² <a href="news/">оÑновній Ñекції +новин</a>.</p> +<p>Якщо ви більше зацікавлені в розробці libreboot, пройдіть на <a +href="../git.html">Ñторінку розробки libreboot</a>, Ñка також включає +поÑÐ¸Ð»Ð°Ð½Ð½Ñ Ð½Ð° репозиторії Git. Сторінка на <a +href="docs/maintain/">/docs/maintain/</a> опиÑує те, Ñк Libreboot +ÑкладаєтьÑÑ Ñ€Ð°Ð·Ð¾Ð¼, Ñ– Ñк підтримувати його. Якщо ви бажаєте зібрати +Libreboot із джерельного кода, <a href="docs/build/">прочитайте цю +Ñторінку</a>.</p> +<h1 +id="read-this-before-updating-libreboot-or-you-might-brick-your-machine">READ +THIS BEFORE UPDATING LIBREBOOT, OR YOU MIGHT BRICK YOUR MACHINE</h1> +<p><strong>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:</strong></p> +<p><strong><a href="docs/install/ivy_has_common.html">Insert vendor +files on Sandybridge/Ivybridge/Haswell</a></strong></p> +<p>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 <em>deleted</em> 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: <a href="docs/build/">Libreboot +build instructions</a></p> +<p>This isn’t required on <em>all</em> 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.</p> +<div class="h"><h2 id="код-підпиÑу-gpg">Код підпиÑу GPG</h2><a aria-hidden="true" href="#код-підпиÑу-gpg">[link]</a></div> +<p><strong>ОÑтаннім випуÑком Ñ” Libreboot 20231021, в директорії +<code>testing</code>.</strong></p> +<div class="h"><h3 id="новий-ключ">ÐОВИЙ КЛЮЧ</h3><a aria-hidden="true" href="#новий-ключ">[link]</a></div> +<p>Повний відбиток ключа: +<code>98CC DDF8 E560 47F4 75C0 44BD D0C6 2464 FA8B 4856</code></p> +<p>Вищезазначений ключ Ð´Ð»Ñ Libreboot 20231021, та наÑтупних +випуÑків.</p> +<p>Завантажте ключ тут: <a href="lbkey.asc">lbkey.asc</a></p> +<p>ВипуÑки Libreboot підпиÑані з викориÑтаннÑм GPG.</p> +<div class="h"><h3 id="Ñтарий-ключ">СТÐРИЙ КЛЮЧ:</h3><a aria-hidden="true" href="#Ñтарий-ключ">[link]</a></div> +<p>Цей ключ Ð´Ð»Ñ Libreboot 20160907 та вÑÑ–Ñ… Ñтаріших випуÑків:</p> +<p>Повний відбиток ключа: CDC9 CAE3 2CB4 B7FC 84FD C804 969A 9795 05E8 +C5B2</p> +<p>Ключ GPG також може бути завантажений разом із цим екÑпортованим +дампом публічного ключа: <a href="lbkeyold.asc">lbkeyold.asc</a>.</p> +<pre><code>sha512sum -c sha512sum.txt +gpg --verify sha512sum.txt.sig</code></pre> +<div class="h"><h2 id="репозиторій-git">Репозиторій Git</h2><a aria-hidden="true" href="#репозиторій-git">[link]</a></div> +<p>ПоÑÐ¸Ð»Ð°Ð½Ð½Ñ Ð½Ð° архіви регулÑрних випуÑків зазначені на цій +Ñторінці.</p> +<p>Однак, Ð´Ð»Ñ Ð°Ð±Ñолютно найновішої верÑÑ–Ñ— Libreboot, Ñ–Ñнує репозиторії +Git, з Ñкого можна завантажити. Ідіть Ñюди:</p> +<p><a href="git.html">Як завантажити Libreboot через Git</a></p> +<div class="h"><h2 id="https">Дзеркала HTTPS</h2><a aria-hidden="true" href="#https">[link]</a></div> +<p><strong>ОÑтаннім випуÑком Ñ” Libreboot 20231021, в директорії +<code>testing</code>.</strong></p> +<p>Дані дзеркала Ñ” рекомендованими, оÑкільки викориÑтовують TLS +(https://) шифруваннÑ.</p> +<p>Ви можете завантажити Libreboot через дані дзеркала:</p> +<ul> +<li><a href="https://www.mirrorservice.org/sites/libreboot.org/release/" +class="uri">https://www.mirrorservice.org/sites/libreboot.org/release/</a> +(КентÑький універÑитет, ВеликобританіÑ)</li> +<li><a href="https://mirrors.mit.edu/libreboot/" +class="uri">https://mirrors.mit.edu/libreboot/</a> (УніверÑитет МТІ, +СШÐ)</li> +<li><a href="https://mirror.math.princeton.edu/pub/libreboot/" +class="uri">https://mirror.math.princeton.edu/pub/libreboot/</a> +(ПрінÑтонÑький універÑитет, СШÐ)</li> +<li><a href="https://mirror.shapovalov.tech/libreboot/" +class="uri">https://mirror.shapovalov.tech/libreboot/</a> +(shapovalov.tech, Україна)</li> +<li><a href="https://mirror.koddos.net/libreboot/" +class="uri">https://mirror.koddos.net/libreboot/</a> (koddos.net, +Ðідерланди)</li> +<li><a href="https://mirror-hk.koddos.net/libreboot/" +class="uri">https://mirror-hk.koddos.net/libreboot/</a> (koddos.net, +Гонконг)</li> +<li><a href="https://mirror.cyberbits.eu/libreboot/" +class="uri">https://mirror.cyberbits.eu/libreboot/</a> (cyberbits.eu, +ФранціÑ)</li> +<li><a href="https://mirror.mangohost.net/libreboot/" +class="uri">https://mirror.mangohost.net/libreboot/</a> (mangohost.net, +Moldova)</li> +</ul> +<div class="h"><h2 id="rsync">Дзеркала RSYNC</h2><a aria-hidden="true" href="#rsync">[link]</a></div> +<p>ÐаÑтупні дзеркала rsync доÑтупні публічно:</p> +<ul> +<li><a href="rsync://rsync.mirrorservice.org/libreboot.org/release/" +class="uri">rsync://rsync.mirrorservice.org/libreboot.org/release/</a> +(КентÑький універÑитет, ВеликобританіÑ)</li> +<li><a href="rsync://mirror.math.princeton.edu/pub/libreboot/" +class="uri">rsync://mirror.math.princeton.edu/pub/libreboot/</a> +(ПрінÑтонÑький універÑитет, СШÐ)</li> +<li><a href="rsync://rsync.shapovalov.tech/libreboot/" +class="uri">rsync://rsync.shapovalov.tech/libreboot/</a> +(shapovalov.tech, Україна)</li> +<li><a href="rsync://ftp.linux.ro/libreboot/" +class="uri">rsync://ftp.linux.ro/libreboot/</a> (linux.ro, РумуніÑ)</li> +<li><a href="rsync://mirror.koddos.net/libreboot/" +class="uri">rsync://mirror.koddos.net/libreboot/</a> (koddos.net, +Ðідерланди)</li> +<li><a href="rsync://mirror-hk.koddos.net/libreboot/" +class="uri">rsync://mirror-hk.koddos.net/libreboot/</a> (koddos.net, +Гонконг)</li> +<li><a href="rsync://mirror.mangohost.net/libreboot/" +class="uri">rsync://mirror.mangohost.net/libreboot/</a> (mangohost.net, +Moldova)</li> +</ul> +<p>Ви підтримуєте роботу дзеркала? Зв’ÑжітьÑÑ Ð· проектом libreboot, Ñ– +поÑÐ¸Ð»Ð°Ð½Ð½Ñ Ð±ÑƒÐ´Ðµ додано до цієї Ñторінки!</p> +<p>Ви можете зробити Ñвоє дзеркало rsync доÑтупним через Ñвій +веб-Ñервер, а також налаштувати ваше <em>влаÑне</em> дзеркало бути +доÑтупним через rsync. Є багато онлайн-реÑурÑів, Ñкі показують вам те, +Ñк налаштувати Ñервер rsync.</p> +<p>Як Ñтворити ваше влаÑне дзеркало rsync:</p> +<p>КориÑно Ð´Ð»Ñ Ð²Ñ–Ð´Ð·ÐµÑ€ÐºÐ°Ð»ÑŽÐ²Ð°Ð½Ð½Ñ Ð¿Ð¾Ð²Ð½Ð¾Ð³Ð¾ набору архівів випуÑків +Libreboot. Ви можете розміÑтити команду rsync в crontab та витÑгувать +файли в директорію на вашому веб-Ñервері.</p> +<p>Якщо ви збираєтеÑÑŒ відзеркалювати повний набір, рекомендовано, щоб +вами було виділено хоча би 25 ГБ. Rsync Libreboot наразі приблизно 12 +ГБ, таким чином Ð²Ð¸Ð´Ñ–Ð»ÐµÐ½Ð½Ñ 25 ГБ забезпечить вам багато міÑÑ†Ñ Ð½Ð° +майбутнє. Мінімально, ви маєте переконатиÑÑŒ, що хоча би 15-20 ГБ +проÑтору доÑтупно, Ð´Ð»Ñ Ð²Ð°ÑˆÐ¾Ð³Ð¾ дзеркала Libreboot.</p> +<p><em>ÐаÑтійно рекомендуєтьÑÑ, щоб ви викориÑтовували дзеркало +libreboot.org</em>, Ñкщо бажаєте розміщувати офіційне дзеркало. Ð’ іншому +випадку, Ñкщо ви проÑто бажаєте Ñтворити Ñвоє влаÑне локальне дзеркало, +вам варто викориÑтовувати одне з інших дзеркал, Ñке ÑинхронізуєтьÑÑ Ð· +libreboot.org.</p> +<p>Перед ÑтвореннÑм дзеркала, зробіть директорію на вашому веб-Ñервері. +Ð”Ð»Ñ Ð¿Ñ€Ð¸ÐºÐ»Ð°Ð´Ñƒ:</p> +<pre><code>mkdir /var/www/html/libreboot/</code></pre> +<p>Тепер ви можете виконувати rsync, Ð´Ð»Ñ Ð¿Ñ€Ð¸ÐºÐ»Ð°Ð´Ñƒ:</p> +<pre><code>rsync -avz --delete-after rsync://rsync.libreboot.org/mirrormirror/ /var/www/html/libreboot/</code></pre> +<p>Ви могли би розміÑтить це в щогодинний crontab. Ð”Ð»Ñ Ð¿Ñ€Ð¸ÐºÐ»Ð°Ð´Ñƒ:</p> +<pre><code>crontab -e</code></pre> +<p>Потім в crontab, додайте цей Ñ€Ñдок Ñ– збережітьÑÑ/вийдіть (щогодинний +crontab):</p> +<pre><code>0 * * * * rsync -avz --delete-after rsync://rsync.libreboot.org/mirrormirror/ /var/www/html/libreboot/</code></pre> +<p><strong>Це надзвичайно важливо, щоб мати в кінці коÑу лінію (/) в +кінці кожного шлÑху, в вищезазначеній команді rsync. Ð’ інакшому випадку, +rsync буде поводитиÑÑŒ дуже дивно.</strong></p> +<p><strong>ПОМІТКÐ: <code>rsync.libreboot.org</code> не Ñ” напрÑму +доÑтупним Ð´Ð»Ñ Ð³Ñ€Ð¾Ð¼Ð°Ð´ÑькоÑÑ‚Ñ–, окрім тих, чиї IP у білому ÑпиÑку. Через +пропуÑкну здатніÑÑ‚ÑŒ, Брандмауер, Ñкий працює на libreboot.org, блокує +вхідні запити rsync, окрім окремих IP.</strong></p> +<p><strong>Якщо ви бажаєте запуÑтити дзеркало rsync, Ñинхронізуйте з +одного з дзеркал третіх Ñторін вище Ñ– вÑтановіть Ñвоє дзеркало. Ви +можете потім зв’ÑзатиÑÑŒ з Лією Роу, щоб мати ваші адреÑи IP внеÑеним в +білий ÑпиÑок Ð´Ð»Ñ Ð²Ð¸ÐºÐ¾Ñ€Ð¸ÑÑ‚Ð°Ð½Ð½Ñ rsync - Ñкщо адреÑи IP відповідають DNS +A/AAAA запиÑам Ð´Ð»Ñ Ð²Ð°ÑˆÐ¾Ð³Ð¾ хоÑта rsync, це може бути викориÑтано. +Сценарій виконуєтьÑÑ Ð² щогодинному crontab на libreboot.org, Ñкий +отримує A/AAAA запиÑи внеÑених в білий ÑпиÑок дзеркал rsync, автоматично +додаючи правила, Ñкі дозволÑÑŽÑ‚ÑŒ їм проходити через +брандмауер.</strong></p> +<p>Якщо ви бажаєте регулÑрно тримати Ñвої дзеркала rsync оновленими, ви +можете додати це до crontab. Ð¦Ñ Ñторінка розповідає вам, Ñк +викориÑтовувати crontab: <a +href="https://man7.org/linux/man-pages/man5/crontab.5.html" +class="uri">https://man7.org/linux/man-pages/man5/crontab.5.html</a></p> +<div class="h"><h2 id="http">Дзеркала HTTP</h2><a aria-hidden="true" href="#http">[link]</a></div> +<p><strong>ОÑтаннім випуÑком Ñ” Libreboot 20231021, під директорією +<code>testing</code>.</strong></p> +<p>УВÐГÐ: ці дзеркала Ñ” не-HTTPS, що означає, що вони незашифровані. Ваш +трафік може бути об’єктом Ð²Ñ‚Ñ€ÑƒÑ‡Ð°Ð½Ð½Ñ Ð¿Ñ€Ð¾Ñ‚Ð¸Ð²Ð½Ð¸ÐºÑ–Ð². ОÑобливо ретельно +переконайтеÑÑŒ, щоб перевірити підпиÑи GPG, передбачаючи, що ви маєте +правильний ключ. ЗвіÑно, вам варто зробити це в будь-Ñкому випадку, +навіть при викориÑтанні HTTPS.</p> +<ul> +<li><a href="http://mirror.linux.ro/libreboot/" +class="uri">http://mirror.linux.ro/libreboot/</a> (linux.ro, +РумуніÑ)</li> +<li><a href="http://mirror.helium.in-berlin.de/libreboot/" +class="uri">http://mirror.helium.in-berlin.de/libreboot/</a> +(in-berlin.de, Ðімеччина)</li> +</ul> +<div class="h"><h2 id="ftp">Дзеркала FTP</h2><a aria-hidden="true" href="#ftp">[link]</a></div> +<p><strong>ОÑтаннім випуÑком Ñ” Libreboot 20231021, під директорією +<code>testing</code>.</strong></p> +<p>УВÐГÐ: FTP Ñ” також незашифрованим, подібно HTTP. Ті ж Ñамі ризики +приÑутні.</p> +<ul> +<li><a href="ftp://ftp.mirrorservice.org/sites/libreboot.org/release/" +class="uri">ftp://ftp.mirrorservice.org/sites/libreboot.org/release/</a> +(КентÑький універÑитет, ВеликобританіÑ)</li> +<li><a href="ftp://ftp.linux.ro/libreboot/" +class="uri">ftp://ftp.linux.ro/libreboot/</a> (linux.ro, РумуніÑ)</li> +</ul> +<div class="h"><h2 id="Ñтатично-звÑзані">Статично зв’Ñзані</h2><a aria-hidden="true" href="#Ñтатично-звÑзані">[link]</a></div> +<p>Libreboot включає Ñтатично зв’Ñзані виконувані файли в деÑких +випуÑках, побудовані з доÑтупного джерельного кода. Ці виконувані файли +мають деÑкі бібліотеки, вбудовані в них, так щоб виконувані файли +працювали на багатьох диÑтрибутивах Linux.</p> +<p>Ð”Ð»Ñ Ð´Ð¾Ñ‚Ñ€Ð¸Ð¼Ð°Ð½Ð½Ñ GPL v2, джерельні ISO поÑтачаютьÑÑ Ð¿Ñ€Ð¾ÐµÐºÑ‚Ð¾Ð¼ Libreboot. +Ви можете знайти ці джерельні ISO в директорії <code>ccsource</code> на +дзеркалах <code>rsync</code>.</p> +<p>Попередні випуÑки Libreboot 20160907 не розповÑюджують Ñтатично +зв’Ñзані двійкові файли. ÐатоміÑÑ‚ÑŒ ці випуÑки Ñ” лише вихідними кодами, +окрім попередньо Ñкомпільованих образів ПЗП, Ð´Ð»Ñ Ñких доÑтатньо +звичайних архівів джерельного коду Libreboot. Ці новіші випуÑки +натоміÑÑ‚ÑŒ автоматизують вÑÑ‚Ð°Ð½Ð¾Ð²Ð»ÐµÐ½Ð½Ñ Ð·Ð°Ð»ÐµÐ¶Ð½Ð¾Ñтей побудови, з інÑтрукцієї +в документації Ð´Ð»Ñ Ð¿Ð¾Ð±ÑƒÐ´Ð¾Ð²Ð¸ різних утиліт з джерельного коду.</p> +<p>Ці виконувані файли Ñ” утилітами, подібними <code>flashrom</code>.</p> +<div id="footer"> +<hr /> +<ul> +<li><a href="/news/policy.html">Політика бінарних блобів</a></li> +<li><a href="/git.html">Редагувати цю Ñторінку</a></li> +<li><a href="/who.uk.html">Хто розроблÑÑ” Libreboot?</a></li> +<li><a href="/license.html">ЛіцензіÑ</a></li> +<li><a href="/template-license.uk.html">Шаблон</a></li> +<li><a href="/logo-license.uk.html">Логотип</a></li> +<li><a href="/contrib.uk.html">Ðвтори</a></li> +</ul> +<hr /> +</div> +<p>Markdown: <a href="https://libreboot.org/download.uk.md" +class="uri">https://libreboot.org/download.uk.md</a></p> +<p><a href="/sitemap.html">Ð†Ð½Ð´ÐµÐºÑ Ñайта</a></p> +<p>Ð¦Ñ Ñторінка була Ñтворена з <a +href="https://untitled.vimuser.org/">untitled static site +generator</a>.</p> +</div> +</div> +</body> +</html> diff --git a/site/download.uk.md b/site/download.uk.md index 3cb4b25b6da6ca4857bdfb00816d8591bae7c6be..33d4ac0308badcaf0faef0a272823e566c29c515 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 0000000000000000000000000000000000000000..596e8ae9920a8801fd8b239a4f0e5bc522304929 --- /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 0000000000000000000000000000000000000000..fc201a0677142d8312a97fec113be0fd9d4eef7a --- /dev/null +++ b/site/index.de.html @@ -0,0 +1,212 @@ +<!DOCTYPE html> +<html lang="de" dir="ltr"> +<head> + <meta charset="utf-8"> + <meta name="generator" content="pandoc"> + <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes"> + +<!-- anti-social media tags --> + <meta property="og:title" content="Libreboot – Libreboot projekt"> + <meta property="og:type" content="article" /> + <meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg"> + <meta property="og:url" content="https://libreboot.org/index.de.html"> + <meta name="twitter:card" content="summary_large_image"> + <meta property="og:description" content="Libreboot – Libreboot projekt"> + <meta property="og:site_name" content="Libreboot – Libreboot projekt"> + <meta name="twitter:image:alt" content="Libreboot – Libreboot projekt"> + + <title>Libreboot – Libreboot projekt</title> + <link rel="stylesheet" href="/global.css"> +<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/> +</head> +<body> +<div class="page"> +<header> +<div class="title"> +<p class="title-logo"> +<img loading="lazy" class="title-logo" alt="Libreboot logo" src="/favicon.ico" /> +</p> +<h1 class="title">Libreboot projekt</h1> +</div> +<ul> +<li><a href="/index.de.html">Home</a></li> +<li><a href="/faq.html">FAQ</a></li> +<li><strong><a href="/freedom-status.html">Freiheits Status</a></strong></li> +<li><strong><a href="/download.html">Download</a></strong></li> +<li><a href="/docs/install/">Installation</a></li> +<li><a href="/docs/">Dokumentation</a></li> +<li><a href="/news/">Neuigkeiten</a></li> +<li><a href="https://codeberg.org/libreboot/lbmk/issues">Bugs</a></li> +<li><a href="/git.de.html">Patch senden</a></li> +<li><strong><a href="https://www.patreon.com/libreleah">Spenden</a></strong></li> +<li><a href="/contact.de.html">Kontakt</a></li> +<li><strong><a href="https://minifree.org/">Vorinstalliertes Gerät kaufen</a></strong></li> +</ul> +<hr/> +</header> +<nav id="TOC"> +<h1>Navigate this page:</h1> +<ul> +<li><a href="#warum-solltest-du-libreboot-verwenden">Warum solltest Du +<em>Libreboot</em> verwenden?</a></li> +<li><a href="#libreboot-ist-kein-coreboot-fork">Libreboot ist kein +Coreboot Fork</a></li> +<li><a href="#wie-kann-ich-helfen">Wie kann ich helfen</a></li> +<li><a href="#übersetzungen-für-libreboot.org-benötigt">Ãœbersetzungen +für libreboot.org benötigt</a></li> +</ul> +</nav> +<div class="pagetext"> +<p><a href="./">English</a> | <a href="index.de.html">Deutsch</a> | <a +href="index.fr.html">Français</a> | <a href="index.it.html">Italiano</a> +| <a href="index.uk.html">українÑька</a> | <a +href="index.zh-cn.html">简体ä¸æ–‡</a></p> +<p>Das <em>Libreboot</em> Projekt bietet eine <a +href="freedom-status.html">freie</a> <em>Boot Firmware</em> welche auf +<a href="docs/hardware/">bestimmten Intel/AMD x86 und ARM Geräten</a> +die Hardware initialisiert (z.b. Speicher-Controller, CPU, Peripherie), +und dann einen Bootloader für dein Betriebssystem startet. <a +href="docs/linux/">Linux</a> sowie <a href="docs/bsd/">BSD</a> werden +gut unterstützt. Es ersetzt proprietäre BIOS/UEFI Firmware. Hilfe ist +verfügbar via <a +href="https://web.libera.chat/#libreboot">#libreboot</a> und <a +href="https://libera.chat/">Libera</a> IRC.</p> +<p><img loading="lazy" tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span></p> +<p><strong>NEUESTE VERSION: Die neueste Version von Libreboot ist +20231021, veröffentlicht am 21. Oktober 2023. Siehe auch: <a +href="news/libreboot20231021.html">Libreboot 20231021 release +announcement</a>.</strong></p> +<h2 id="warum-solltest-du-libreboot-verwenden">Warum solltest Du +<em>Libreboot</em> verwenden?</h2> +<p>Libreboot gibt dir <a +href="https://writefreesoftware.org/">Freiheit</a> welche Du mit den +meisten Boot Firmwares nicht hast, und zusätzlich schnellere Boot +Geschwindigkeiten sowie <a href="docs/linux/grub_hardening.html">höhere +Sicherheit</a>. Es ist extrem leistungsfähig und für viele Einsatzzwecke +<a href="docs/maintain/">konfigurierbar</a>.</p> +<p>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. <a href="https://yewtu.be/watch?v=Npd_xDuNi9k">Das Recht auf +Reparatur</a> ist wichtig. Viele Menschen verwenden proprietäre +(non-libre) Boot Firmware, sogar wenn Sie ein <a +href="https://www.openbsd.org/">Libre OS</a> verwenden. Proprietäre +Firmware <a href="faq.html#intel">enthält</a> häufig <a +href="faq.html#amd">Hintertüren</a>, 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.</p> +<p>Das Libreboot Projekt verwendet <a +href="https://www.coreboot.org/">Coreboot</a> für <a +href="https://doc.coreboot.org/getting_started/architecture.html">die +Initialiserung der Hardware</a>. Die Coreboot Installation ist für +unerfahrene Benutzer überaus schwierig; sie übernimmt lediglich die +Basis Initialisierung und springt dann zu einem separaten <a +href="https://doc.coreboot.org/payloads.html">payload</a> Programm (z.B. +<a href="https://www.gnu.org/software/grub/">GRUB</a>, <a +href="https://www.tianocore.org/">Tianocore</a>), welche zusätzlich +konfiguriert werden muss. <em>Libreboot löst dieses Problem</em>; es ist +eine <em>Coreboot Distribution</em> mit einem <a +href="docs/build/">automatisierten Build System</a> welches vollständige +<em>ROM images</em> für eine robustere Installation erstellt. +Dokumentation ist verfügbar.</p> +<h2 id="libreboot-ist-kein-coreboot-fork">Libreboot ist kein Coreboot +Fork</h2> +<p><img loading="lazy" tabindex=1 class="l" style="max-width:25%;" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /></span></p> +<p>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.</p> +<p>Ebenso wie <em>Alpine Linux</em> eine <em>Linux Distribution</em> +ist, ist Libreboot eine <em>Coreboot Distribution</em>. 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 <em>Libreboot</em> kannst Du +sprichwörtlich von Git oder einem anderen Quell-Archiv herunterladen, +anschliessend <code>make</code> 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.</p> +<p>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.</p> +<p>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 <a href="docs/install/">vereinfachten Anleitung, geschrieben für +technisch unerfahrene Benutzer</a> zu folgen.</p> +<div class="h"><h2 id="wie-kann-ich-helfen">Wie kann ich helfen</h2><a aria-hidden="true" href="#wie-kann-ich-helfen">[link]</a></div> +<p><img loading="lazy" tabindex=1 class="l" style="max-width:15%;" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /></span></p> +<p>Der beste Weg wie Du helfen kannst, ist das <em>hinzufügen</em> 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:</p> +<ul> +<li><a href="docs/maintain/testing.html">Bewerbe dich um Boards zu +testen oder zu pflegen</a></li> +<li><a href="docs/maintain/porting.html">Anleitung um neue Mainboards +hinzuzufügen</a></li> +<li><a href="docs/maintain/">Libreboot Build System +Dokumentation</a></li> +</ul> +<p>Zudem ist da noch Pflege des Build Systems (siehe oben), sowie +<em>Dokumentation</em> welche wir sehr ernst nehmen. Dokumentation ist +wichtig, in jedem Projekt.</p> +<p><em>Hilfe für Benutzer</em> 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 <code>r/libreboot</code> nach Hilfe.</p> +<p>Eine Liste mit Bugs gibt es unter <a +href="https://codeberg.org/libreboot/lbmk/issues">Bug Tracker</a>.</p> +<p>Sofern Du einen Bug findest oder einen Fix hast, <a +href="git.de.html">hier sind Anleitungen um Patches zu schicken</a>, +oder Du kannst davon berichten. Diese Website ist zudem in Markdown +geschrieben und verfügbar in einem <a +href="https://codeberg.org/libreboot/lbwww">separaten Repository</a> für +welches Du auch Patches schicken kannst.</p> +<p>Sämtliche Diskussionen über Entwicklung sowie Hilfe für Nutzer findet +im IRC Kanal statt. Mehr Informationen gibt es unter <a +href="contact.de.html">Kontakt</a>.</p> +<h2 id="übersetzungen-für-libreboot.org-benötigt">Ãœbersetzungen für +libreboot.org benötigt</h2> +<p>Libreboot hat derzeit übersetzte Webseiten in ukrainisch und +französisch (aber bislang nicht für alle Seiten für keine der +Sprachen)</p> +<p>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:</p> +<p><a href="news/translations.de.html">Wie man Ãœbersetzungen für +libreboot.org bereitstellt</a></p> +<p>Auch wenn jemand bereits an einer Ãœbersetzung in einer bestimmten +Sprache arbeitet, so können wir immer mehrere Leute gebrauchen. Desto +mehr desto besser!</p> +<div id="footer"> +<hr /> +<ul> +<li><a href="/news/policy.html">Binäre Blob Richtlinie</a></li> +<li><a href="/git.de.html">Diese Seite bearbeiten</a></li> +<li><a href="/who.de.html">Wer entwickelt Libreboot?</a></li> +<li><a href="/license.html">Lizenz</a></li> +<li><a href="/template-license.html">Vorlage</a></li> +<li><a href="/logo-license.html">Logo</a></li> +<li><a href="/contrib.html">Autoren</a></li> +</ul> +<hr /> +</div> +<p>Markdown-Datei: <a href="https://libreboot.org/index.de.md" +class="uri">https://libreboot.org/index.de.md</a></p> +<p><a href="/sitemap.html">Website karte</a></p> +<p>Diese HTML-Seite wurde von <a +href="https://untitled.vimuser.org/">untitled static site generator</a> +erstellt.</p> +</div> +</div> +</body> +</html> diff --git a/site/index.de.md b/site/index.de.md index d80c421bbf3dc03ca1c3d5f4235c05c3e98abc27..91146bfc10058b42ecbc5aeebbd3755714c3f630 100644 --- a/site/index.de.md +++ b/site/index.de.md @@ -15,9 +15,9 @@ und [Libera](https://libera.chat/) IRC. <img tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span class="f"><img src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span> -**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 0000000000000000000000000000000000000000..687be2ec56f623f485abb6048011d7c5cbb128bb --- /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 0000000000000000000000000000000000000000..7cb4f11e85db601268acf8e23b9f2f9644763f7d --- /dev/null +++ b/site/index.fr.html @@ -0,0 +1,209 @@ +<!DOCTYPE html> +<html lang="fr" dir="ltr"> +<head> + <meta charset="utf-8"> + <meta name="generator" content="pandoc"> + <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes"> + +<!-- anti-social media tags --> + <meta property="og:title" content="Libreboot – Projet Libreboot"> + <meta property="og:type" content="article" /> + <meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg"> + <meta property="og:url" content="https://libreboot.org/index.fr.html"> + <meta name="twitter:card" content="summary_large_image"> + <meta property="og:description" content="Libreboot – Projet Libreboot"> + <meta property="og:site_name" content="Libreboot – Projet Libreboot"> + <meta name="twitter:image:alt" content="Libreboot – Projet Libreboot"> + + <title>Libreboot – Projet Libreboot</title> + <link rel="stylesheet" href="/global.css"> +<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/> +</head> +<body> +<div class="page"> +<header> +<div class="title"> +<p class="title-logo"> +<img loading="lazy" class="title-logo" alt="Libreboot logo" src="/favicon.ico" /> +</p> +<h1 class="title">Projet Libreboot</h1> +</div> +<ul> +<li><a href="/">Home</a></li> +<li><a href="/faq.html">FAQ</a></li> +<li><strong><a href="/freedom-status.html">Freedom status</a></strong></li> +<li><strong><a href="/download.html">Download</a></strong></li> +<li><a href="/docs/install/">Install</a></li> +<li><a href="/docs/">Docs</a></li> +<li><a href="/news/">News</a></li> +<li><a href="https://codeberg.org/libreboot/lbmk/issues">Bugs</a></li> +<li><a href="/git.html">Send patch</a></li> +<li><strong><a href="https://www.patreon.com/libreleah">Donate</a></strong></li> +<li><a href="/contact.html">Contact</a></li> +<li><strong><a href="https://minifree.org/">Buy preinstalled</a></strong></li> +</ul> +<hr/> +</header> +<nav id="TOC"> +<h1>Navigate this page:</h1> +<ul> +<li><a href="#pourquoi-devriez-vous-utiliser-libreboot">Pourquoi +devriez-vous utiliser <em>Libreboot</em>?</a></li> +<li><a href="#de-quelle-façon-libreboot-diffère-de-coreboot">De quelle +façon Libreboot diffère de Coreboot?</a></li> +<li><a href="#comment-aider">Comment aider</a></li> +<li><a href="#translations-needed-for-libreboot.org">Translations +needed, for libreboot.org</a></li> +</ul> +</nav> +<div class="pagetext"> +<p><a href="./">English</a> | <a href="index.de.html">Deutsch</a> | <a +href="index.fr.html">Français</a> | <a href="index.it.html">Italiano</a> +| <a href="index.uk.html">українÑька</a> | <a +href="index.zh-cn.html">简体ä¸æ–‡</a></p> +<p>Libreboot est un micrologiciel de démarrage <a +href="freedom-status.html">libéré</a> qui initialise le matériel (cà d le +contrôleur mémoire, CPU, périphériques) sur <a href="docs/hardware/">des +ordinateurs x86/ARM spécifiques</a> et lance un chargeur d’amorçage pour +votre système d’exploitation. <a href="docs/linux/">Linux</a> et <a +href="docs/bsd/">BSD</a> sont bien supportés. C’est un remplacement pour +le micrologiciel UEFI/BIOS propriétaire. Des canaux d’aide sont +disponibles dans le canal <a +href="https://web.libera.chat/#libreboot">#libreboot</a> sur le serveur +IRC <a href="https://libera.chat/">Libera</a>.</p> +<p><img loading="lazy" tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span></p> +<p><strong>NOUVELLE VERSION: La dernière version est <a +href="news/libreboot20231021.html">Libreboot 20231021</a>, sortie le 21 +octobre 2023.</strong></p> +<h2 id="pourquoi-devriez-vous-utiliser-libreboot">Pourquoi devriez-vous +utiliser <em>Libreboot</em>?</h2> +<p>Libreboot vous donne des <a +href="https://writefreesoftware.org/">libertés</a> que nous n’auriez pas +autrement avec d’autre micrologiciel de démarrage. Il est extremement <a +href="docs/linux/grub_hardening.html">puissant</a> et <a +href="docs/maintain">configurable</a> pour plein de cas +d’utilisations.</p> +<p>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 <a +href="https://yewtu.be/watch?v=Npd_xDuNi9k">Droit à la réparation</a> +est important. Beaucoup de personnes utilisent un micrologiciel de +démarrage propriétare (non libre), même si ils utilisent <a +href="https://www.openbsd.org/">un système d’exploitation libre</a>. Les +micrologiciels propriétaires <a href="faq.html#intel">contiennent</a> +souvent des <a href="faq.html#amd">portes dérobées</a> 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.</p> +<p>Libreboot utilise <a href="https://www.coreboot.org">coreboot</a> +pour <a +href="https://doc.coreboot.org/getting_started/architecture.html">l’initialisation +matérielle</a> 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 <a +href="https://doc.coreboot.org/payloads.html">charge utile</a> (par ex. +<a href="https://www.gnu.org/software/grub/">GRUB</a>, <a +href="https://www.tianocore.org/">Tianocore</a>), qui doit lui aussi +être configuré. <em>Libreboot règle ce problème</em>; c’est une +<em>distribution de coreboot</em> avec un <a href="docs/builds/">système +de compilation automatisé</a>, crééant des <em>images ROM</em> complètes +pour une installation plus robuste. De la documentation est +disponible.</p> +<h2 id="de-quelle-façon-libreboot-diffère-de-coreboot">De quelle façon +Libreboot diffère de Coreboot?</h2> +<p><img loading="lazy" tabindex=1 class="l" style="max-width:25%;" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /></span></p> +<p>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.</p> +<p>De la même façon que <em>Alpine Linux</em> est une distribution +Linux, Libreboot est une <em>distribution coreboot</em>. 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 +<em>Libreboot</em>, vous pouvez télécharger la source depuis Git ou une +archive, exécuter <code>make</code> etça compilera une image ROM +entières. Le système de compilation automatisé de Libreboot nommé +<code>lbmk</code> (Libreboot MaKe), compile ces images ROM +automatiquement, sans besoin d’entrées utilisateur or intervention +requise. La configuration est faite à l’avance.</p> +<p>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.</p> +<p>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 <a href="docs/install/">suivre des +instructions simplifiés écrite pour des utilisateurs non +techniques</a>.</p> +<div class="h"><h2 id="comment-aider">Comment aider</h2><a aria-hidden="true" href="#comment-aider">[link]</a></div> +<p><img loading="lazy" tabindex=1 class="l" style="max-width:15%;" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /></span></p> +<p>The <em>single</em> biggest way you can help it to <em>add</em> new +mainboards to Libreboot, by submitting a config. Anything coreboot +supports can be integrated in Libreboot, with ROM images provided in +releases. See:</p> +<ul> +<li><a href="docs/maintain/testing.html">Apply to become a board +maintainer/tester</a></li> +<li><a href="docs/maintain/porting.html">Porting guide for new +mainboards</a></li> +<li><a href="docs/maintain/">Libreboot build system +documentation</a></li> +</ul> +<p>After that, there is build system maintenance (see above), and +<em>documentation</em> which we take seriously. Documentation is +critical, in any project.</p> +<p><em>User support</em> 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 <code>r/libreboot</code> +subreddit.</p> +<p>Vous pouvez allez voir les bugs listés sur le <a +href="https://codeberg.org/libreboot/lbmk/issues">traqueur de +bugs</a>.</p> +<p>Si vous trouvez un bug et avez un correctif, <a href="git.html">voici +les instructions pour envoyer des patchs</a>, et vous pouvez aussi nous +les signaler. Par ailleurs, ce site est écrit en Markdown et hébergé +dans un <a href="https://codeberg.org/libreboot/lbwww">dépôt séparé</a> +où vous pouvez envoyer vos patchs.</p> +<p>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 <a href="contact.html">page de contact</a>.</p> +<h2 id="translations-needed-for-libreboot.org">Translations needed, for +libreboot.org</h2> +<p>Libreboot currently has translated Web pages in Ukrainian and French +(but not for all pages, yet, on either language).</p> +<p>If you want to help with translations, you can translate pages, +update existing translations and submit your translated versions. For +instructions, please read:</p> +<p><a href="news/translations.html">How to submit translations for +libreboot.org</a></p> +<p>Even if someone is already working on translations in a given +language, we can always use multiple people. The more the merrier!</p> +<div id="footer"> +<hr /> +<ul> +<li><a href="/news/policy.html">Binary Blob Reduction Policy</a></li> +<li><a href="/git.html">Edit this page</a></li> +<li><a href="/who.html">Who develops Libreboot?</a></li> +<li><a href="/license.html">License</a></li> +<li><a href="/template-license.html">Template</a></li> +<li><a href="/logo-license.html">Logo</a></li> +<li><a href="/contrib.html">Authors</a></li> +</ul> +<hr /> +</div> +<p>Fichier Markdown pour cette page: <a +href="https://libreboot.org/index.fr.md" +class="uri">https://libreboot.org/index.fr.md</a></p> +<p><a href="/sitemap.html">Plan du site</a></p> +<p>Cette page HTML a été générée par le <em><a +href="https://untitled.vimuser.org/">untitled static site +generator</a></em>.</p> +</div> +</div> +</body> +</html> diff --git a/site/index.fr.md b/site/index.fr.md index 8111f1b0779833ed1953f5e01551538da3e87e51..fe7537372c77237cfee4d845c839fc900dd5dde4 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 <img tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span class="f"><img src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span> -**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 0000000000000000000000000000000000000000..23e21bc9665b4f944d161719138532377364439e --- /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 0000000000000000000000000000000000000000..9606705e6f001b0064061c2fecdf08788146391b --- /dev/null +++ b/site/index.html @@ -0,0 +1,203 @@ +<!DOCTYPE html> +<html lang="en" dir="ltr"> +<head> + <meta charset="utf-8"> + <meta name="generator" content="pandoc"> + <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes"> + +<!-- anti-social media tags --> + <meta property="og:title" content="Libreboot – Libreboot project"> + <meta property="og:type" content="article" /> + <meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg"> + <meta property="og:url" content="https://libreboot.org/"> + <meta name="twitter:card" content="summary_large_image"> + <meta property="og:description" content="Libreboot – Libreboot project"> + <meta property="og:site_name" content="Libreboot – Libreboot project"> + <meta name="twitter:image:alt" content="Libreboot – Libreboot project"> + + <title>Libreboot – Libreboot project</title> + <link rel="stylesheet" href="/global.css"> +<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/> +</head> +<body> +<div class="page"> +<header> +<div class="title"> +<p class="title-logo"> +<img loading="lazy" class="title-logo" alt="Libreboot logo" src="/favicon.ico" /> +</p> +<h1 class="title">Libreboot project</h1> +</div> +<ul> +<li><a href="/">Home</a></li> +<li><a href="/faq.html">FAQ</a></li> +<li><strong><a href="/freedom-status.html">Freedom status</a></strong></li> +<li><strong><a href="/download.html">Download</a></strong></li> +<li><a href="/docs/install/">Install</a></li> +<li><a href="/docs/">Docs</a></li> +<li><a href="/news/">News</a></li> +<li><a href="https://codeberg.org/libreboot/lbmk/issues">Bugs</a></li> +<li><a href="/git.html">Send patch</a></li> +<li><strong><a href="https://www.patreon.com/libreleah">Donate</a></strong></li> +<li><a href="/contact.html">Contact</a></li> +<li><strong><a href="https://minifree.org/">Buy preinstalled</a></strong></li> +</ul> +<hr/> +</header> +<nav id="TOC"> +<h1>Navigate this page:</h1> +<ul> +<li><a href="#why-should-you-use-libreboot">Why should you use +<em>Libreboot</em>?</a></li> +<li><a href="#libreboot-is-not-a-fork-of-coreboot">Libreboot is not a +fork of coreboot</a></li> +<li><a href="#how-to-help">How to help</a></li> +<li><a href="#translations-needed-for-libreboot.org">Translations +needed, for libreboot.org</a></li> +</ul> +</nav> +<div class="pagetext"> +<p><a href="./">English</a> | <a href="index.de.html">Deutsch</a> | <a +href="index.fr.html">Français</a> | <a href="index.it.html">Italiano</a> +| <a href="index.uk.html">українÑька</a> | <a +href="index.zh-cn.html">简体ä¸æ–‡</a></p> +<p>The <em>Libreboot</em> project provides <a +href="freedom-status.html">free, open source</a> (<em>libre</em>) boot +firmware based on coreboot, replacing proprietary BIOS/UEFI firmware on +<a href="docs/hardware/">specific Intel/AMD x86 and ARM based +motherboards</a>, including laptop and desktop computers. It initialises +the hardware (e.g. memory controller, CPU, peripherals) and starts a +bootloader for your operating system. <a href="docs/linux/">Linux</a> +and <a href="docs/bsd/">BSD</a> are well-supported. Help is available +via <a href="https://web.libera.chat/#libreboot">#libreboot</a> on <a +href="https://libera.chat/">Libera</a> IRC.</p> +<p><img loading="lazy" tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span></p> +<p><strong>NEW RELEASE: The latest release is Libreboot 20231021, +released on 21 October 2023. See: <a +href="news/libreboot20231021.html">Libreboot 20231021 release +announcement</a>.</strong></p> +<h2 id="why-should-you-use-libreboot">Why should you use +<em>Libreboot</em>?</h2> +<p>Libreboot gives you <a +href="https://writefreesoftware.org/">freedoms</a> that you otherwise +can’t get with most other boot firmware, plus faster boot speeds and <a +href="docs/linux/grub_hardening.html">better security</a>. It’s +extremely powerful and <a href="docs/maintain/">configurable</a> for +many use cases.</p> +<p><em>We</em> believe the freedom to <a +href="https://writefreesoftware.org/">study, share, modify and use +software</a>, without any restriction, is one of the fundamental human +rights that everyone must have. In this context, <em>software +freedom</em> matters. Your freedom matters. Education matters. <a +href="https://yewtu.be/watch?v=Npd_xDuNi9k">Right to repair</a> matters. +Many people use proprietary (non-libre) boot firmware, even if they use +<a href="https://www.openbsd.org/">a libre OS</a>. Proprietary firmware +often <a href="faq.html#intel">contains</a> <a +href="faq.html#amd">backdoors</a>, 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.</p> +<p>The Libreboot project uses <a +href="https://www.coreboot.org/">coreboot</a> for <a +href="https://doc.coreboot.org/getting_started/architecture.html">hardware +initialisation</a>. Coreboot is notoriously difficult to install for +most non-technical users; it handles only basic initialization and jumps +to a separate <a +href="https://doc.coreboot.org/payloads.html">payload</a> program (e.g. +<a href="https://www.gnu.org/software/grub/">GRUB</a>, <a +href="https://www.tianocore.org/">Tianocore</a>), which must also be +configured. <em>Libreboot solves this problem</em>; it is a <em>coreboot +distribution</em> with an <a href="docs/build/">automated build +system</a> that builds complete <em>ROM images</em>, for more robust +installation. Documentation is provided.</p> +<h2 id="libreboot-is-not-a-fork-of-coreboot">Libreboot is not a fork of +coreboot</h2> +<p><img loading="lazy" tabindex=1 class="l" style="max-width:25%;" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /></span></p> +<p>In fact, Libreboot tries to stay as close to <em>stock</em> coreboot +as possible, for each board, but with many different types of +configuration provided automatically by the Libreboot build system.</p> +<p>In the same way that <em>Alpine Linux</em> is a <em>Linux +distribution</em>, Libreboot is a <em>coreboot distribution</em>. 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 <em>Libreboot</em>, you can +literally download from Git or a source archive, and run +<code>make</code>, and it will build entire ROM images. An automated +build system, named <code>lbmk</code> (Libreboot MaKe), builds these ROM +images automatically, without any user input or intervention required. +Configuration has already been performed in advance.</p> +<p>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.</p> +<p>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 <a href="docs/install/">simplified +instructions, written for non-technical users</a>.</p> +<div class="h"><h2 id="how-to-help">How to help</h2><a aria-hidden="true" href="#how-to-help">[link]</a></div> +<p><img loading="lazy" tabindex=1 class="l" style="max-width:15%;" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /></span></p> +<p>The <em>single</em> biggest way you can help is to <em>add</em> new +mainboards in Libreboot, by submitting a config. Anything coreboot +supports can be integrated in Libreboot, with ROM images provided in +releases. See:</p> +<ul> +<li><a href="docs/maintain/testing.html">Apply to become a board +maintainer/tester</a></li> +<li><a href="docs/maintain/porting.html">Porting guide for new +mainboards</a></li> +<li><a href="docs/maintain/">Libreboot build system +documentation</a></li> +</ul> +<p>After that, there is build system maintenance (see above), and +<em>documentation</em> which we take seriously. Documentation is +critical, in any project.</p> +<p><em>User support</em> 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 <code>r/libreboot</code> +subreddit.</p> +<p>You can check bugs listed on the <a +href="https://codeberg.org/libreboot/lbmk/issues">bug tracker</a>.</p> +<p>If you spot a bug and have a fix, <a href="git.html">here are +instructions for how to send patches</a>, and you can also report it. +Also, this entire website is written in Markdown and hosted in a <a +href="https://codeberg.org/libreboot/lbwww">separate repository</a> +where you can send patches.</p> +<p>Any and all development discussion and user support are all done on +the IRC channel. More information is on the <a +href="contact.html">contact page</a>.</p> +<h2 id="translations-needed-for-libreboot.org">Translations needed, for +libreboot.org</h2> +<p>Libreboot currently has translated Web pages in Ukrainian and French +(but not for all pages, yet, on either language).</p> +<p>If you want to help with translations, you can translate pages, +update existing translations and submit your translated versions. For +instructions, please read:</p> +<p><a href="news/translations.html">How to submit translations for +libreboot.org</a></p> +<p>Even if someone is already working on translations in a given +language, we can always use multiple people. The more the merrier!</p> +<div id="footer"> +<hr /> +<ul> +<li><a href="/news/policy.html">Binary Blob Reduction Policy</a></li> +<li><a href="/git.html">Edit this page</a></li> +<li><a href="/who.html">Who develops Libreboot?</a></li> +<li><a href="/license.html">License</a></li> +<li><a href="/template-license.html">Template</a></li> +<li><a href="/logo-license.html">Logo</a></li> +<li><a href="/contrib.html">Authors</a></li> +</ul> +<hr /> +</div> +<p>Markdown file for this page: <a href="https://libreboot.org/index.md" +class="uri">https://libreboot.org/index.md</a></p> +<p><a href="/sitemap.html">Site map</a></p> +<p>This HTML page was generated by the <a +href="https://untitled.vimuser.org/">untitled static site +generator</a>.</p> +</div> +</div> +</body> +</html> diff --git a/site/index.it.html b/site/index.it.html new file mode 100644 index 0000000000000000000000000000000000000000..6efb7e75526ef099ebcf0cd29085e7ae85ece609 --- /dev/null +++ b/site/index.it.html @@ -0,0 +1,213 @@ +<!DOCTYPE html> +<html lang="it" dir="ltr"> +<head> + <meta charset="utf-8"> + <meta name="generator" content="pandoc"> + <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes"> + +<!-- anti-social media tags --> + <meta property="og:title" content="Libreboot – Progetto Libreboot"> + <meta property="og:type" content="article" /> + <meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg"> + <meta property="og:url" content="https://libreboot.org/index.it.html"> + <meta name="twitter:card" content="summary_large_image"> + <meta property="og:description" content="Libreboot – Progetto Libreboot"> + <meta property="og:site_name" content="Libreboot – Progetto Libreboot"> + <meta name="twitter:image:alt" content="Libreboot – Progetto Libreboot"> + + <title>Libreboot – Progetto Libreboot</title> + <link rel="stylesheet" href="/global.css"> +<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/> +</head> +<body> +<div class="page"> +<header> +<div class="title"> +<p class="title-logo"> +<img loading="lazy" class="title-logo" alt="Libreboot logo" src="/favicon.ico" /> +</p> +<h1 class="title">Progetto Libreboot</h1> +</div> +<ul> +<li><a href="/index.it.html">Home</a></li> +<li><a href="/faq.html">FAQ</a></li> +<li><strong><a href="/freedom-status.html">Grado di liberta' possibile</a></strong></li> +<li><strong><a href="/download.html">Download</a></strong></li> +<li><a href="/docs/install/">Installazione</a></li> +<li><a href="/docs/">Documentazione</a></li> +<li><a href="/news/">Notizie</a></li> +<li><a href="https://codeberg.org/libreboot/lbmk/issues">Difetti (bugs)</a></li> +<li><a href="/git.html">Spedisci correzioni (patches)</a></li> +<li><strong><a href="https://www.patreon.com/libreleah">Donazioni</a></strong></li> +<li><a href="/contact.html">Contatti</a></li> +<li><strong><a href="https://minifree.org/">Compra un PC con libreboot gia' installato</a></strong></li> +</ul> +<hr/> +</header> +<nav id="TOC"> +<h1>Sfoglia questa pagina:</h1> +<ul> +<li><a href="#per-quale-ragione-utilizzare-libreboot">Per quale ragione +utilizzare <em>Libreboot</em>?</a></li> +<li><a href="#libreboot-non-deriva-da-coreboot">Libreboot non deriva da +coreboot</a></li> +<li><a href="#come-essere-daiuto">Come essere d’aiuto</a></li> +<li><a href="#servono-traduzioni-per-libreboot.org">Servono traduzioni +per libreboot.org</a></li> +</ul> +</nav> +<div class="pagetext"> +<p><a href="./">English</a> | <a href="index.de.html">Deutsch</a> | <a +href="index.fr.html">Français</a> | <a href="index.it.html">Italiano</a> +| <a href="index.uk.html">українÑька</a> | <a +href="index.zh-cn.html">简体ä¸æ–‡</a></p> +<p>Il progetto <em>Libreboot</em> fornisce avvio <a +href="freedom-status.html">libero e open source</a> grazie al firmware +basato su coreboot, sostituendo cosi’, firmware BIOS/UEFI proprietario +su <a href="docs/hardware/">alcune schede madri basate su Intel/AMD x86 +o ARM</a>, in computer fissi e portatili. Inizializza l’hardware +(controller di memoria, CPU, periferiche) e avvia un bootloader per il +tuo sistema operativo. <a href="docs/linux/">Linux</a> e <a +href="docs/bsd/">BSD</a> sono ben supportati. L’aiuto e’ disponibile sul +canale IRC <a href="https://web.libera.chat/#libreboot">#libreboot</a> +su <a href="https://libera.chat/">Libera</a>.</p> +<p><img loading="lazy" tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span></p> +<p><strong>ULTIMO RILASCIO: L’ultimo rilascio e’ Libreboot 20231021, +rilasciato il 21 ottobre 2023. Vedi: <a +href="news/libreboot20231021.html">Libreboot 20231021 annuncio di +rilascio</a>.</strong></p> +<h2 id="per-quale-ragione-utilizzare-libreboot">Per quale ragione +utilizzare <em>Libreboot</em>?</h2> +<p>Libreboot ti permette <a +href="https://writefreesoftware.org/">liberta’</a> che non potresti +ottenere con altri firmware di boot, velocita’ di avvio maggiori e <a +href="docs/linux/grub_hardening.html">migliore sicurezza</a>. E’ +estremamente flessibile e <a href="docs/maintain/">configurabile</a> per +la maggior parte dei casi.</p> +<p><em>Noi</em> crediamo nella liberta’ di <a +href="https://writefreesoftware.org/">studiare, condividere, modificare +and usare il software</a>, senza restrizione alcuna, in quanto e’ uno +dei fondamentali diritti umani che chiunque deve avere. In questo +contesto, <em>il software libero</em> conta. La tua liberta’ conta. La +formazione personale conta. <a +href="https://yewtu.be/watch?v=Npd_xDuNi9k">Il diritto di riparare</a> +conta. Molte persone usano firmware di boot proprietario (non-libero), +anche se usano <a href="https://www.openbsd.org/">un sistema operativo +libero</a>. Firmware proprietari spesso <a +href="faq.html#intel">contengono</a> <a +href="faq.html#amd">vulnerabilita’</a>, 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.</p> +<p>Il progetto Libreboot fa uso di <a +href="https://www.coreboot.org/">coreboot</a> per <a +href="https://doc.coreboot.org/getting_started/architecture.html">l’inizializzazione +hardware</a>. 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 <a +href="https://doc.coreboot.org/payloads.html">payload</a> (ad esempio. +<a href="https://www.gnu.org/software/grub/">GRUB</a>, <a +href="https://www.tianocore.org/">Tianocore</a>), i quali possono essere +configurati a piacere. <em>Libreboot risolve questo problema</em>; e’ +una <em>distribuzione di coreboot</em> con un <a +href="docs/build/">sistema di compilazione automatizzato</a> che produce +<em>immagini ROM</em> complete, per una installazione piu’ robusta. +Viene fornito con apposita documentazione.</p> +<h2 id="libreboot-non-deriva-da-coreboot">Libreboot non deriva da +coreboot</h2> +<p><img loading="lazy" tabindex=1 class="l" style="max-width:25%;" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /></span></p> +<p>In effetti, Libreboot tenta di essere il piu’ possibile simile alla +versione <em>ufficiale</em> di coreboot, per ogni scheda, ma con diversi +tipi di configurazione forniti automaticamente dal sistema di +compilazione automatico di Libreboot.</p> +<p>Esattamente come <em>Alpine Linux</em> e’ una <em>distribuzione +Linux</em>, Libreboot e’ una <em>distribuzione coreboot</em>. Per fare +un immagine ROM da zero, hai bisogno di esperienza necessaria nel +configurare coreboot, GRUB e qualunque altra cosa ti serve. Con +<em>Libreboot</em>, che puoi scaricare da Git o da un archivio di codici +sorgenti, puoi far partire <code>make</code>, e questo mettera’ su +automaticamente le immagini ROM richieste. Un sistema di compilazione +automatico, chiamato <code>lbmk</code> (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.</p> +<p>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.</p> +<p>I rilasci binari di Libreboot forniscono immagini ROM precompilate, +che puoi semplicemente installare senza troppe conoscenze tecniche o +abilita’ particolari ad eccezione del seguire <a +href="docs/install/">semplici istruzioni scritte per chiunque</a>.</p> +<div class="h"><h2 id="come-essere-daiuto">Come essere d’aiuto</h2><a aria-hidden="true" href="#come-essere-daiuto">[link]</a></div> +<p><img loading="lazy" tabindex=1 class="l" style="max-width:15%;" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /></span></p> +<p>Il <em>modo migliore</em> col quale puoi aiutarci e’ quello di +<em>aggiungere</em> nuove schede condividendone la configurazione. +Qualunque cosa sia supportata da coreboot puo’ essere integrata in +Libreboot, con immagini ROM fornite nei rilasci. Vedi anche:</p> +<ul> +<li><a href="docs/maintain/testing.html">Richiedi di collaudare o +mantenere una scheda</a></li> +<li><a href="docs/maintain/porting.html">Guida per rendere nuove schede +compatibili</a></li> +<li><a href="docs/maintain/">Documentazione del sistema di compilazione +automatica di Libreboot</a></li> +</ul> +<p>Dopo di che c’e’ da tenere seriamente in considerazione la +manutenzione della compilazione automatica (guarda sopra), e la +<em>documentazione</em>. La documentazione e’ critica in ogni +progetto.</p> +<p><em>Il supporto utente</em> 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 <code>r/libreboot</code>.</p> +<p>Puoi controllare l’elenco dei bugs sul <a +href="https://codeberg.org/libreboot/lbmk/issues">bug tracker</a>.</p> +<p>Se hai notato un difetto (bug) e hai trovato una soluzione, <a +href="git.html">qui puoi trovare istruzioni su come inviare delle +correzioni (patches)</a> o puoi semplicemente farne rapporto. Inoltre +tutto questo sito internet e’ scritto in Markdown e ospitato su un <a +href="https://codeberg.org/libreboot/lbwww">repository separato</a>, +dove puoi inviare correzioni (patches).</p> +<p>Qualunque discorso relativo a sviluppo e supporto utente viene fatto +sul canale IRC. Puoi avere piu’ informazioni sulla <a +href="contact.html">pagina dei contatti</a>.</p> +<h2 id="servono-traduzioni-per-libreboot.org">Servono traduzioni per +libreboot.org</h2> +<p>Libreboot attualmente ha pagine Web tradotte in Ucraino and Francese +(ma non ancora in ogni pagina e per ogni lingua).</p> +<p>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: <a href="news/translations.html">come +condividere traduzioni per libreboot.org</a></p> +<p>Anche se qualcuno sta gia’ lavorando sulle traduzioni in una +determinata lingua, possiamo sempre avvalerci di piu’ contributori. Piu’ +siamo e meglio e’!</p> +<div id="footer"> +<hr /> +<ul> +<li><a href="/news/policy.html">Politica di riduzione di parti binarie +proprietarie (blobs)</a></li> +<li><a href="/git.de.html">Modifica questa pagina</a></li> +<li><a href="/who.de.html">Chi sviluppa Libreboot?</a></li> +<li><a href="/license.html">Licenza</a></li> +<li><a href="/template-license.html">Modelli di licenze</a></li> +<li><a href="/logo-license.html">Logo</a></li> +<li><a href="/contrib.html">Autori</a></li> +</ul> +<hr /> +</div> +<p>Markdown file: <a href="https://libreboot.org/index.it.md" +class="uri">https://libreboot.org/index.it.md</a></p> +<p><a href="/sitemap.html">Site map</a></p> +<p>This HTML page was generated by the <a +href="https://untitled.vimuser.org/">untitled static site +generator</a>.</p> +</div> +</div> +</body> +</html> diff --git a/site/index.it.md b/site/index.it.md index a85c6b665576e43c96e65975352c2745b3bb6da3..1e29f094e7df97eeea572b3817bfc1af6f403bbb 100644 --- a/site/index.it.md +++ b/site/index.it.md @@ -14,8 +14,8 @@ su [Libera](https://libera.chat/). <img tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span class="f"><img src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span> -**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 0000000000000000000000000000000000000000..7103e44b53152ec1df34c3283ce0d9970fe07028 --- /dev/null +++ b/site/index.it.md.date @@ -0,0 +1 @@ +1697839851 diff --git a/site/index.md b/site/index.md index 5c8394270a19ac8c11b7917ceff9ce24c4bdad93..75ae41634ad1056a73b6c789434af60937dbd21f 100644 --- a/site/index.md +++ b/site/index.md @@ -15,9 +15,9 @@ on [Libera](https://libera.chat/) IRC. <img tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span class="f"><img src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span> -**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 0000000000000000000000000000000000000000..9c64fe7c9208e2089a753378643ecc79aa7dd0cf --- /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 0000000000000000000000000000000000000000..c8803c163f00ab30dea43d1d740283275fc89e91 --- /dev/null +++ b/site/index.uk.html @@ -0,0 +1,204 @@ +<!DOCTYPE html> +<html lang="uk" dir="ltr"> +<head> + <meta charset="utf-8"> + <meta name="generator" content="pandoc"> + <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes"> + +<!-- anti-social media tags --> + <meta property="og:title" content="Libreboot – Проект Libreboot"> + <meta property="og:type" content="article" /> + <meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg"> + <meta property="og:url" content="https://libreboot.org/index.uk.html"> + <meta name="twitter:card" content="summary_large_image"> + <meta property="og:description" content="Libreboot – Проект Libreboot"> + <meta property="og:site_name" content="Libreboot – Проект Libreboot"> + <meta name="twitter:image:alt" content="Libreboot – Проект Libreboot"> + + <title>Libreboot – Проект Libreboot</title> + <link rel="stylesheet" href="/global.css"> +<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="/feed.xml"/> +</head> +<body> +<div class="page"> +<header> +<div class="title"> +<p class="title-logo"> +<img loading="lazy" class="title-logo" alt="Логотип Libreboot" src="/favicon.ico" /> +</p> +<h1 class="title">Проект Libreboot</h1> +</div> +<ul> +<li><a href="/index.uk.html">ДомашнÑ</a></li> +<li><a href="/faq.html">FAQ</a></li> +<li><strong><a href="/freedom-status.html">Ð¡Ñ‚Ð°Ñ‚ÑƒÑ Ñвободи</a></strong></li> +<li><strong><a href="/download.uk.html">ЗавантаженнÑ</a></strong></li> +<li><a href="/docs/install/">Ð’ÑтановленнÑ</a></li> +<li><a href="/docs/index.uk.html">ДокументаціÑ</a></li> +<li><a href="/news/">Ðовини</a></li> +<li><a href="https://codeberg.org/libreboot/lbmk/issues">Помилки</a></li> +<li><a href="/git.uk.html">Відправити виправленнÑ</a></li> +<li><strong><a href="https://www.patreon.com/libreleah">Пожертвувати</a></strong></li> +<li><a href="/contact.uk.html">Зв'Ñзок</a></li> +<li><strong><a href="https://minifree.org/">Придбати передвÑтановленим</a></strong></li> +</ul> +<hr/> +</header> +<nav id="TOC"> +<h1>ÐÐ°Ð²Ñ–Ð³Ð°Ñ†Ñ–Ñ Ñ†Ñ–Ñ”ÑŽ Ñторінкою:</h1> +<ul> +<li><a href="#чому-вам-варто-викориÑтовувати-libreboot">Чому вам варто +викориÑтовувати <em>Libreboot</em>?</a></li> +<li><a href="#чим-libreboot-відрізнÑєтьÑÑ-від-звичайного-coreboot">Чим +Libreboot відрізнÑєтьÑÑ Ð²Ñ–Ð´ звичайного coreboot?</a></li> +<li><a href="#Ñк-допомогти">Як допомогти</a></li> +<li><a href="#переклади-потрібні-длÑ-libreboot.org">Переклади потрібні, +Ð´Ð»Ñ libreboot.org</a></li> +</ul> +</nav> +<div class="pagetext"> +<p><a href="./">English</a> | <a href="index.de.html">Deutsch</a> | <a +href="index.fr.html">Français</a> | <a href="index.it.html">Italiano</a> +| <a href="index.uk.html">українÑька</a> | <a +href="index.zh-cn.html">简体ä¸æ–‡</a></p> +<p>Проект <em>Libreboot</em> надає <a +href="freedom-status.uk.html">вільну</a> <em>завантажувальну +прошивку</em>, Ñка ініціалізує апаратне Ð·Ð°Ð±ÐµÐ·Ð¿ÐµÑ‡ÐµÐ½Ð½Ñ (наприклад, +контролер пам’ÑÑ‚Ñ–, ЦП, периферію) на <a href="docs/hardware/">конкретних +цілÑÑ… Intel/AMD x86 та ARM</a>, що потім розпочинає завантажувач Ð´Ð»Ñ +вашої операційної ÑиÑтеми. <a href="docs/linux/">Linux</a> та <a +href="docs/bsd/">BSD</a> добре підтримуютьÑÑ. Це замінÑÑ” пропрієтарну +BIOS/UEFI прошивку. Допомога доÑтупна через <a +href="https://web.libera.chat/#libreboot">#libreboot</a> на <a +href="https://libera.chat/">Libera</a> IRC.</p> +<p><img loading="lazy" tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span></p> +<p><strong>ÐОВИЙ ВИПУСК: ОÑтанній випуÑк Libreboot 20231021, випущено 21 +жовтень 2023. ДивітьÑÑ: <a href="news/libreboot20231021.html">ÐžÐ³Ð¾Ð»Ð¾ÑˆÐµÐ½Ð½Ñ +про випуÑк Libreboot 20231021</a>.</strong></p> +<h2 id="чому-вам-варто-викориÑтовувати-libreboot">Чому вам варто +викориÑтовувати <em>Libreboot</em>?</h2> +<p>Libreboot надає вам <a +href="https://writefreesoftware.org/">Ñвободи</a>, Ñкі в іншому випадку +ви не можете отримати з більшіÑÑ‚ÑŽ інших завантажувальних прошивок. Він +надзвичайно <a href="docs/linux/grub_hardening.html">потужний</a> та <a +href="docs/maintain/">налаштовуєтьÑÑ</a> Ð´Ð»Ñ Ð±Ð°Ð³Ð°Ñ‚ÑŒÐ¾Ñ… випадків +викориÑтаннÑ.</p> +<p>У Ð²Ð°Ñ Ñ” права. Право на конфіденційніÑÑ‚ÑŒ, Ñвобода миÑленнÑ, Ñвобода +виÑÐ»Ð¾Ð²Ð»ÑŽÐ²Ð°Ð½Ð½Ñ Ñ‚Ð° право читати. Ð’ цьому контекÑÑ‚Ñ–, Libreboot надає вам ці +права. Ваша Ñвобода має значеннÑ. <a +href="https://yewtu.be/watch?v=Npd_xDuNi9k">Право на ремонт</a> має +значеннÑ. Багато людей викориÑтовують пропрієтарну (невільну) +завантажувальну прошивку, навіть Ñкщо вони викориÑтовують <a +href="https://www.openbsd.org/">вільну операційну ÑиÑтему</a>. +Пропрієтарна прошивка чаÑто <a href="faq.uk.html#intel">міÑтить</a> <a +href="faq.uk.html#amd">лазівки</a>, та може бути глючною. Проект +Libreboot було заÑновано в грудні 2013 року, з Ñвною метою зробити +прошивку coreboot доÑтупною Ð´Ð»Ñ Ð½ÐµÑ‚ÐµÑ…Ð½Ñ–Ñ‡Ð½Ð¸Ñ… кориÑтувачів.</p> +<p>Проект Libreboot викориÑтовує <a +href="https://www.coreboot.org/">coreboot</a> Ð´Ð»Ñ <a +href="https://doc.coreboot.org/getting_started/architecture.html">ініціалізації +апаратного забезпеченнÑ</a>. Coreboot помітно Ñкладний Ð´Ð»Ñ Ð²ÑÑ‚Ð°Ð½Ð¾Ð²Ð»ÐµÐ½Ð½Ñ +Ð´Ð»Ñ Ð±Ñ–Ð»ÑŒÑˆÐ¾ÑÑ‚Ñ– нетехнічних кориÑтувачів; він виконує тільки базову +ініціалізацію та переÑтрибує до окремої програми <a +href="https://doc.coreboot.org/payloads.html">кориÑного навантаженнÑ</a> +(наприклад, <a href="https://www.gnu.org/software/grub/">GRUB</a>, <a +href="https://www.tianocore.org/">Tianocore</a>), Ñкі також мають бути +налаштованими. <em>Програмне Ð·Ð°Ð±ÐµÐ·Ð¿ÐµÑ‡ÐµÐ½Ð½Ñ Libreboot вирішує цю +проблему</em>; це <em>диÑтрибутив coreboot</em> з <a +href="docs/build/index.uk.html">автоматизованою ÑиÑтемою побудови</a>, +Ñка збирає завершені <em>образи ROM</em>, Ð´Ð»Ñ Ð±Ñ–Ð»ÑŒÑˆ надійної уÑтановки. +Ð”Ð¾ÐºÑƒÐ¼ÐµÐ½Ñ‚Ð°Ñ†Ñ–Ñ Ð½Ð°Ð´Ð°Ñ”Ñ‚ÑŒÑÑ.</p> +<h2 id="чим-libreboot-відрізнÑєтьÑÑ-від-звичайного-coreboot">Чим +Libreboot відрізнÑєтьÑÑ Ð²Ñ–Ð´ звичайного coreboot?</h2> +<p><img loading="lazy" tabindex=1 class="l" style="max-width:25%;" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /></span></p> +<p>Таким же Ñамим чином, Ñк <em>Debian</em> це диÑтрибутив Linux, +Libreboot це <em>диÑтрибутив coreboot</em>. Якщо ви хочете зібрати образ +ROM з нулÑ, вам інакше довелоÑÑŒ би виконати Ð½Ð°Ð»Ð°ÑˆÑ‚ÑƒÐ²Ð°Ð½Ð½Ñ ÐµÐºÑпертного +Ñ€Ñ–Ð²Ð½Ñ coreboot, GRUB та будь-Ñкого іншого потрібного програмного +забезпеченнÑ, Ð´Ð»Ñ Ð¿Ñ–Ð´Ð³Ð¾Ñ‚ÑƒÐ²Ð°Ð½Ð½Ñ Ð¾Ð±Ñ€Ð°Ð·Ð° ROM. З <em>Libreboot</em>, ви +можете буквально завантажити з Git або архіву джерельного коду, та +запуÑтити <code>make</code>, Ñ– це побудує вÑÑ– образи ROM. Ðвтоматизована +ÑиÑтема побудови, названа <code>lbmk</code> (Libreboot MaKe), збирає ці +образи ROM автоматично, без будь-Ñкого вводу кориÑтувача або потрібного +втручаннÑ. ÐÐ°Ð»Ð°ÑˆÑ‚ÑƒÐ²Ð°Ð½Ð½Ñ Ð²Ð¶Ðµ виконано заздалегідь.</p> +<p>Якщо би ви збирали звичайний coreboot, не викориÑтовуючи +автоматизовану ÑиÑтему побудови Libreboot, це вимагало би набагато +більше Ð²Ñ‚Ñ€ÑƒÑ‡Ð°Ð½Ð½Ñ Ñ‚Ð° гідних технічних знань Ð´Ð»Ñ ÑÑ‚Ð²Ð¾Ñ€ÐµÐ½Ð½Ñ Ñ€Ð¾Ð±Ð¾Ñ‡Ð¾Ñ— +конфігурації.</p> +<p>Звичайні бінарні випуÑки Libreboot надають ці образи ROM попередньо +зібраними, Ñ– ви можете проÑто вÑтановити Ñ—Ñ…, не маючи Ñпеціальних знань +або навичок, окрім можливоÑÑ‚Ñ– Ñлідувати <a +href="docs/install/">Ñпрощеним інÑтрукціÑм, напиÑаним Ð´Ð»Ñ Ð½ÐµÑ‚ÐµÑ…Ð½Ñ–Ñ‡Ð½Ð¸Ñ… +кориÑтувачів</a>.</p> +<div class="h"><h2 id="Ñк-допомогти">Як допомогти</h2><a aria-hidden="true" href="#Ñк-допомогти">[link]</a></div> +<p><img loading="lazy" tabindex=1 class="l" style="max-width:15%;" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /></span></p> +<p><em>Єдиний</em> найбільший шлÑÑ…, Ñким ви можете допомогти Ñ” +<em>додаваннÑ</em> нових материнÑьких плат до Libreboot, за допомогою +відправки конфігурації. Що завгодно, що підтримує coreboot може бути +інтегровано в Libreboot, з образами ROM наданими в випуÑках. +ДивітьÑÑ:</p> +<ul> +<li><a href="docs/maintain/testing.html">Подача на ÑÑ‚Ð°Ð½Ð¾Ð²Ð»ÐµÐ½Ð½Ñ +Ñупровідником/випробувачем плати</a></li> +<li><a href="docs/maintain/porting.uk.html">Керівництво перенеÑÐµÐ½Ð½Ñ Ð´Ð»Ñ +нових материнÑьких плат</a></li> +<li><a href="docs/maintain/">Ð”Ð¾ÐºÑƒÐ¼ÐµÐ½Ñ‚Ð°Ñ†Ñ–Ñ ÑиÑтеми побудови +Libreboot</a></li> +</ul> +<p>ПіÑÐ»Ñ Ñ†ÑŒÐ¾Ð³Ð¾, Ñ” обÑÐ»ÑƒÐ³Ð¾Ð²ÑƒÐ²Ð°Ð½Ð½Ñ ÑиÑтеми побудови (дивітьÑÑ Ð·Ð²ÐµÑ€Ñ…Ñƒ), та +<em>документаціÑ</em>, до Ñкої ми ÑтавимоÑÑ Ñерйозно. Ð”Ð¾ÐºÑƒÐ¼ÐµÐ½Ñ‚Ð°Ñ†Ñ–Ñ Ñ” +критичною, в будь-Ñкому проекті.</p> +<p><em>КориÑтувацька ідтримка</em> Ñ” також критичною. ТримайтеÑÑŒ порÑд +на IRC, Ñ– Ñкщо ви компетентні допомогти комуÑÑŒ з Ñ—Ñ… проблемним питаннÑм +(або доÑить вправні, щоб навчитиÑÑŒ з ними), це Ñ” чудовою поÑлугою Ð´Ð»Ñ +проекту. Багато людей також запитує підтримки кориÑтувачів на subreddit +<code>r/libreboot</code>.</p> +<p>Ви можете перевірити помилки, перелічені в <a +href="https://codeberg.org/libreboot/lbmk/issues">ÑиÑтемі відÑÑ‚ÐµÐ¶ÐµÐ½Ð½Ñ +помилок</a>.</p> +<p>Якщо ви помітили помилку Ñ– маєте виправленнÑ, <a +href="git.uk.html">оÑÑŒ інÑтрукції щодо надÑÐ¸Ð»Ð°Ð½Ð½Ñ Ð²Ð¸Ð¿Ñ€Ð°Ð²Ð»ÐµÐ½ÑŒ</a>, а +також ви можете повідомити про це. Також, веÑÑŒ цей веб-Ñайт напиÑаний +Markdown та розміщений в <a +href="https://codeberg.org/libreboot/lbwww">окремому Ñховищі</a>, де ви +можете надÑилати виправленнÑ.</p> +<p>УÑÑ– Ð¾Ð±Ð³Ð¾Ð²Ð¾Ñ€ÐµÐ½Ð½Ñ Ñ€Ð¾Ð·Ñ€Ð¾Ð±ÐºÐ¸ та підтримка кориÑтувачів відбуваютьÑÑ Ð½Ð° +IRC каналі. Більше інформації на <a href="contact.uk.html">Ñторінці +зворотнього зв’Ñзку</a>.</p> +<h2 id="переклади-потрібні-длÑ-libreboot.org">Переклади потрібні, Ð´Ð»Ñ +libreboot.org</h2> +<p>Libreboot наразі має перекладеними веб-Ñторінки українÑькою та +французькою (але не Ð´Ð»Ñ Ð²ÑÑ–Ñ… Ñторінок, ще, жодною з мов).</p> +<p>Якщо ви бажаєте допомогти з перекладами, ви можете переклаÑти +Ñторінки, оновити Ñ–Ñнуючи переклади та надати ваші перекладені верÑÑ–Ñ—. +Ð”Ð»Ñ Ñ–Ð½Ñтрукцій, будь лаÑка прочитайте:</p> +<p><a href="news/translations.html">Як надати переклади Ð´Ð»Ñ +libreboot.org</a></p> +<p>Ðавіть Ñкщо хтоÑÑŒ вже працює над перекладами даною мовою, ми можемо +завжди викориÑтовувати багато людей. Чим більше, тим краще!</p> +<div id="footer"> +<hr /> +<ul> +<li><a href="/news/policy.html">Політика бінарних блобів</a></li> +<li><a href="/git.html">Редагувати цю Ñторінку</a></li> +<li><a href="/who.uk.html">Хто розроблÑÑ” Libreboot?</a></li> +<li><a href="/license.html">ЛіцензіÑ</a></li> +<li><a href="/template-license.uk.html">Шаблон</a></li> +<li><a href="/logo-license.uk.html">Логотип</a></li> +<li><a href="/contrib.uk.html">Ðвтори</a></li> +</ul> +<hr /> +</div> +<p>Markdown: <a href="https://libreboot.org/index.uk.md" +class="uri">https://libreboot.org/index.uk.md</a></p> +<p><a href="/sitemap.html">Ð†Ð½Ð´ÐµÐºÑ Ñайта</a></p> +<p>Ð¦Ñ Ñторінка була Ñтворена з <a +href="https://untitled.vimuser.org/">untitled static site +generator</a>.</p> +</div> +</div> +</body> +</html> diff --git a/site/index.uk.md b/site/index.uk.md index a0bd249a5633fad48f62d9ff18efd1fada8d8d7b..c93d44afca1d6eb8670a8b311ca94ce992f07924 100644 --- a/site/index.uk.md +++ b/site/index.uk.md @@ -15,8 +15,8 @@ x-toc-enable: true <img tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span class="f"><img src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span> -**ÐОВИЙ ВИПУСК: ОÑтанній випуÑк 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 0000000000000000000000000000000000000000..6058e7792ba3aec859bb57bee7611c2edf03df8b --- /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 0000000000000000000000000000000000000000..ad87eb07d5ba9505e993f081519918ec9008515b --- /dev/null +++ b/site/index.zh-cn.html @@ -0,0 +1,171 @@ +<!DOCTYPE html> +<html lang="zh-cn" dir="ltr"> +<head> + <meta charset="utf-8"> + <meta name="generator" content="pandoc"> + <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes"> + +<!-- anti-social media tags --> + <meta property="og:title" content="Libreboot – Libreboot 项目"> + <meta property="og:type" content="article" /> + <meta property="og:image" content="https://av.vimuser.org/bootmenu.jpg"> + <meta property="og:url" content="https://libreboot.org/index.zh-cn.html"> + <meta name="twitter:card" content="summary_large_image"> + <meta property="og:description" content="Libreboot – Libreboot 项目"> + <meta property="og:site_name" content="Libreboot – Libreboot 项目"> + <meta name="twitter:image:alt" content="Libreboot – Libreboot 项目"> + + <title>Libreboot – Libreboot 项目</title> + <link rel="stylesheet" href="/global.css"> +<link rel="alternate" type="application/rss+xml" title="RSS æº" href="/feed.xml"/> +</head> +<body> +<div class="page"> +<header> +<div class="title"> +<p class="title-logo"> +<img loading="lazy" class="title-logo" alt="Libreboot å›¾æ ‡" src="/favicon.ico" /> +</p> +<h1 class="title">Libreboot 项目</h1> +</div> +<ul> +<li><a href="/">主页</a></li> +<li><a href="/faq.html">常è§é—®é¢˜</a></li> +<li><strong><a href="/freedom-status.html">自由度现状</a></strong></li> +<li><strong><a href="/download.html">下载</a></strong></li> +<li><a href="/docs/install/">安装</a></li> +<li><a href="/docs/">文档</a></li> +<li><a href="/news/">æ–°é—»</a></li> +<li><a href="https://codeberg.org/libreboot/lbmk/issues">缺陷</a></li> +<li><a href="/git.html">å‘é€è¡¥ä¸</a></li> +<li><strong><a href="https://www.patreon.com/libreleah">æèµ </a></strong></li> +<li><a href="/contact.html">è”ç³»</a></li> +<li><strong><a href="https://minifree.org/">è´ä¹°é¢„装å“</a></strong></li> +</ul> +<hr/> +</header> +<nav id="TOC"> +<h1>本页导航:</h1> +<ul> +<li><a href="#为什么è¦ä½¿ç”¨-libreboot">为什么è¦ä½¿ç”¨ +<em>Libreboot</em>?</a></li> +<li><a href="#libreboot-ä¸æ˜¯-coreboot-的分支">Libreboot ä¸æ˜¯ coreboot +的分支</a></li> +<li><a href="#如何帮忙">如何帮忙</a></li> +<li><a href="#libreboot.org-需è¦ç¿»è¯‘">libreboot.org 需è¦ç¿»è¯‘</a></li> +</ul> +</nav> +<div class="pagetext"> +<p><a href="./">English</a> | <a href="index.de.html">Deutsch</a> | <a +href="index.fr.html">Français</a> | <a href="index.it.html">Italiano</a> +| <a href="index.uk.html">українÑька</a> | <a +href="index.zh-cn.html">简体ä¸æ–‡</a></p> +<p><em>Libreboot</em> 项目基于 coreboot æ供了<a +href="freedom-status.md">自由且开æº</a>的引导固件,替代了特定基于 +Intel/AMD x86 åŠ ARM 的主æ¿ï¼ˆåŒ…括笔记本和桌é¢è®¡ç®—机)上的专有 BIOS/UEFI +固件。它首先对硬件(如内å˜æŽ§åˆ¶å™¨ã€CPUã€å¤–设)进行åˆå§‹åŒ–,然åŽä¸ºæ“作系统å¯åŠ¨ +bootloader。本项目对 <a href="docs/linux/">Linux</a> å’Œ <a +href="docs/bsd/">BSD</a> 支æŒè‰¯å¥½ã€‚寻求帮助,å¯ä»¥å‰å¾€ <a +href="https://libera.chat/">Libera</a> IRC 上的 <a +href="https://web.libera.chat/#libreboot">#libreboot</a> 频é“。</p> +<p><img loading="lazy" tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span></p> +<p><strong>新版å‘布: 最新版本 Libreboot 20231021 已在 2023 å¹´ 10 月 21 +æ—¥å‘布。详è§: <a href="news/libreboot20231021.html">Libreboot 20231021 +å‘布公告</a>.</strong></p> +<div class="h"><h2 id="为什么è¦ä½¿ç”¨-libreboot">为什么è¦ä½¿ç”¨ <em>Libreboot</em>?</h2><a aria-hidden="true" href="#为什么è¦ä½¿ç”¨-libreboot">[link]</a></div> +<p>Libreboot èµ‹äºˆäº†ä½ <a +href="https://writefreesoftware.org/">自由</a>,而这ç‰è‡ªç”±ï¼Œæ˜¯ä½ 用其他引导固件得ä¸åˆ°çš„。åŒæ—¶ï¼Œå®ƒçš„å¯åŠ¨é€Ÿåº¦æ›´åŠ 快,<a +href="docs/linux/grub_hardening.md">å®‰å…¨æ€§ä¹Ÿæ›´åŠ é«˜</a>。在å„ç§æƒ…况下使用,它都å分强大,具有高度<a +href="docs/maintain/">å¯é…置性</a>。</p> +<p><em>我们</em>相信,ä¸å—é™åˆ¶åœ°<a +href="https://writefreesoftware.org/">ç ”ç©¶ã€åˆ†äº«ã€ä¿®æ”¹åŠä½¿ç”¨è½¯ä»¶</a>的自由,是æ¯ä¸ªäººéƒ½å¿…须享有的基本人æƒçš„一部分。这时,<em>软件自由</em>至关é‡è¦ã€‚ä½ çš„è‡ªç”±è‡³å…³é‡è¦ã€‚教育至关é‡è¦ã€‚<a +href="https://yewtu.be/watch?v=Npd_xDuNi9k">ä¿®ç†æƒ</a>至关é‡è¦ã€‚尽管许多人在用<a +href="https://www.openbsd.org/">自由的æ“作系统</a>,但他们用的引导固件å´æ˜¯ä¸“有(éžè‡ªç”±ï¼‰çš„。专有固件常常<a +href="faq.html#intel">包å«</a>了<a +href="faq.html#amd">åŽé—¨</a>,并且也å¯èƒ½å‡ºé—®é¢˜ã€‚2013 å¹´ 12 +月,我们建立了 Libreboot 项目,目的是让ä¸æ‡‚技术的用户能使用 coreboot +固件。</p> +<p>Libreboot 项目使用 <a href="https://www.coreboot.org/">coreboot</a> +æ¥<a +href="https://doc.coreboot.org/getting_started/architecture.html">åˆå§‹åŒ–硬件</a>。对大部分ä¸æ‡‚技术的用户æ¥è¯´ï¼Œcoreboot +是出了å地难安装;它åªå¤„ç†äº†åŸºç¡€çš„åˆå§‹åŒ–,然åŽè·³è½¬è¿›å…¥å•ç‹¬çš„ <a +href="https://doc.coreboot.org/payloads.html">payload</a> 程åºï¼ˆä¾‹å¦‚ <a +href="https://www.gnu.org/software/grub/">GRUB</a>ã€<a +href="https://www.tianocore.org/">Tianocore</a>),而åŽè€…也需è¦è¿›è¡Œé…置。<em>Libreboot +è§£å†³äº†è¿™æ ·çš„é—®é¢˜</em>;他是一个 <em>coreboot å‘行版</em>,é…有<a +href="docs/build/">自动构建系统</a>,能够构建完整的 <em>ROM +é•œåƒ</em>ï¼Œä»Žè€Œè®©å®‰è£…æ›´åŠ ç¨³å®šã€‚å¦æœ‰æ–‡æ¡£å¯å‚考。</p> +<h2 id="libreboot-ä¸æ˜¯-coreboot-的分支">Libreboot ä¸æ˜¯ coreboot +的分支</h2> +<p><img loading="lazy" tabindex=1 class="l" style="max-width:25%;" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/thinkpadcollection/thinkpadcollection1-min.jpg" /></span></p> +<p>事实上,Libreboot 对æ¯ä¸€å—主æ¿ï¼Œéƒ½å°½å¯èƒ½ä¿æŒä¸Ž<em>æ ‡å‡†</em>çš„ +coreboot 接近,但 Libreboot 构建系统也自动æ供了许多ä¸åŒç±»åž‹çš„é…置。</p> +<p>Libreboot 是一个 <em>coreboot å‘行版</em>,就好比 <em>Alpine +Linux</em> 是一个 <em>Linux å‘行版</em>ã€‚å¦‚æžœä½ æƒ³è¦ä»Žé›¶å¼€å§‹æž„建 ROM +é•œåƒï¼Œé‚£ä½ 需è¦å¯¹ corebootã€GRUB +以åŠå…¶ä»–所需软件进行专业级别的é…置,æ‰èƒ½å‡†å¤‡å¥½ ROM é•œåƒã€‚有了 +<em>Libreboot</em>ï¼Œä½ åªéœ€è¦ä¸‹è½½ Git 仓库或者æºä»£ç 归档,然åŽè¿è¡Œ +<code>make</code>,接ç€å°±èƒ½æž„建整个 ROM é•œåƒã€‚一套自动构建系统,å为 +<code>lbmk</code>(Libreboot Make),将自动构建 ROM +é•œåƒï¼Œè€Œæ— 需任何用户输入或干预。é…置已ç»æå‰å®Œæˆã€‚</p> +<p>å¦‚æžœä½ è¦æž„建常规的 coreboot,而ä¸ä½¿ç”¨ Libreboot +的自动构建系统,那么需è¦æœ‰å¾ˆå¤šçš„干预以åŠç›¸å½“的技术知识,æ‰èƒ½å†™å‡ºä¸€ä»½èƒ½å·¥ä½œçš„é…置。</p> +<p>Libreboot 的常规二进制版本,æ供了这些预编译的 ROM +é•œåƒã€‚ä½ å¯ä»¥è½»æ¾å®‰è£…å®ƒä»¬ï¼Œè€Œæ— éœ€ç‰¹åˆ«çš„çŸ¥è¯†å’ŒæŠ€èƒ½ï¼Œåªè¦èƒ½éµå¾ª<a +href="docs/install/">写给éžæŠ€æœ¯ç”¨æˆ·çš„简å•æŒ‡å—</a>。</p> +<div class="h"><h2 id="如何帮忙">如何帮忙</h2><a aria-hidden="true" href="#如何帮忙">[link]</a></div> +<p><img loading="lazy" tabindex=1 class="l" style="max-width:15%;" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /><span +class="f"><img loading="lazy" src="https://av.libreboot.org/hp8200sff/grub_open.jpg" /></span></p> +<p>è¦å¸®å¿™çš„è¯ï¼Œ<em>最</em>最好的方å¼ï¼Œå°±æ˜¯é€šè¿‡æ交é…置文件,æ¥ä¸º +Libreboot <em>æ·»åŠ </em>新的主æ¿ã€‚coreboot 支æŒçš„任何东西,都能并入 +Libreboot,并且带有 ROM é•œåƒã€‚è§ï¼š</p> +<ul> +<li><a +href="docs/maintain/testing.html">申请æˆä¸ºä¸»æ¿ç»´æŠ¤è€…/测试者</a></li> +<li><a href="docs/maintain/porting.html">新主æ¿ç§»æ¤æŒ‡å—</a></li> +<li><a href="docs/maintain/">Libreboot 构建系统文档</a></li> +</ul> +<p>然åŽï¼Œå°±æ˜¯æž„建系统的维护(è§ä¸‹ï¼‰ä»¥åŠé‡è¦çš„<em>文档</em>。文档å分é‡è¦ï¼Œåœ¨ä»»ä½•é¡¹ç›®éƒ½æ˜¯å¦‚æ¤ã€‚</p> +<p><em>用户支æŒ</em>也å分é‡è¦ã€‚多瞧一瞧 +IRCï¼Œå¦‚æžœä½ æœ‰èƒ½åŠ›å¸®åˆ«äººè§£å†³é—®é¢˜ï¼ˆæˆ–è€…æ„¿æ„跟他们一起å¦ä¹ ),那对本项目的贡献会很大。许多人也在 +reddit ç‰ˆå— <code>r/libreboot</code> 寻求用户支æŒã€‚</p> +<p>ä½ å¯ä»¥æ£€æŸ¥<a +href="https://codeberg.org/libreboot/lbmk/issues">缺陷追踪系统</a>列出的缺陷。</p> +<p>å¦‚æžœä½ å‘现了一个缺陷,并且有解决方案,<a +href="git.md">这里说明了å‘布补ä¸çš„方法</a>ï¼Œä½ ä¹Ÿå¯ä»¥æ交报告。åŒæ—¶ï¼Œæœ¬ç«™å®Œå…¨ä½¿ç”¨ +Markdown 编写,并托管在了一个<a +href="https://codeberg.org/libreboot/lbwww">å•ç‹¬çš„仓库</a>ï¼Œä½ å¯ä»¥åœ¨é‚£é‡Œå‘é€è¡¥ä¸ã€‚</p> +<p>所有开å‘æ–¹é¢çš„讨论以åŠç”¨æˆ·æ”¯æŒï¼Œéƒ½æ˜¯åœ¨ IRC +频é“上完æˆçš„。了解更多,å¯ä»¥æŸ¥çœ‹<a +href="contact.html">è”ç³»</a>页é¢ã€‚</p> +<div class="h"><h2 id="libreboot.org-需è¦ç¿»è¯‘">libreboot.org 需è¦ç¿»è¯‘</h2><a aria-hidden="true" href="#libreboot.org-需è¦ç¿»è¯‘">[link]</a></div> +<p>Libreboot +ç›®å‰æœ‰ä¹Œå…‹å…°è¯å’Œæ³•è¯çš„网页翻译(但两个è¯è¨€éƒ½è¿˜æ²¡ç¿»è¯‘完所有页é¢ï¼‰ã€‚</p> +<p>å¦‚æžœä½ æƒ³å¸®å¿™ç¿»è¯‘ï¼Œä½ å¯ä»¥ç¿»è¯‘网页ã€æ›´æ–°å·²æœ‰ç¿»è¯‘并æäº¤ä½ çš„è¯‘æœ¬ã€‚è¯·é˜…è¯»ä¸‹é¢çš„指å—:</p> +<p><a href="news/translations.html">如何æ交 libreboot.org 翻译</a></p> +<p>å³ä½¿å·²ç»æœ‰äººåœ¨è¿›è¡ŒæŸä¸ªè¯è¨€çš„翻译了,我们也总是欢迎更多人。多多益善ï¼</p> +<div id="footer"> +<hr /> +<ul> +<li><a href="/news/policy.html">二进制 blob 政ç–</a></li> +<li><a href="/git.html">编辑本页é¢</a></li> +<li><a href="/who.html">è°åœ¨å¼€å‘ Libreboot?</a></li> +<li><a href="/license.html">许å¯è¯</a></li> +<li><a href="/template-license.html">模æ¿</a></li> +<li><a href="/logo-license.html">å›¾æ ‡</a></li> +<li><a href="/contrib.html">作者</a></li> +</ul> +<hr /> +</div> +<p>本页é¢çš„ Markdown 文件: <a +href="https://libreboot.org/index.zh-cn.md" +class="uri">https://libreboot.org/index.zh-cn.md</a></p> +<p><a href="/sitemap.html">网站地图</a></p> +<p>本 HTML 页é¢ä½¿ç”¨ <a href="https://untitled.vimuser.org/">untitled +é™æ€ç½‘站生æˆå™¨</a>生æˆã€‚</p> +</div> +</div> +</body> +</html> diff --git a/site/index.zh-cn.md b/site/index.zh-cn.md index a30769052820ace35c985c09ec3c2f29ac1bd852..ad8dbe81d38e68c8a9a3e9aa3400b59c4dc1b1a6 100644 --- a/site/index.zh-cn.md +++ b/site/index.zh-cn.md @@ -7,7 +7,7 @@ x-toc-enable: true <img tabindex=1 class="r" src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /><span class="f"><img src="https://av.libreboot.org/hp9470m/9470m+2560p.jpg" /></span> -**新版å‘布: 最新版本 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 0000000000000000000000000000000000000000..aeb60760db1c41b54904ca13e15b8c69c122afd1 --- /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 b693b43f2b9ad8128c87f56ec644bbe2be92f43e..1703ddc52b5d21139447e6ffde43b076d87f1fa5 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 847d8cfd389263bfc26f478260ef697e8428f056..be610085729cb8cc64d310aa90e6a650610b8961 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 1b3eff963b1fea07e8157caa025b47c6c8aefe15..c96026513b657ee30ca48be75d2f707451f0f759 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 037a1566aa45604c45ca9529c636d9ad4fb5c1e8..9eb1ea9fadb5252df6827027f6214a63b0827836 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 2e3ee6fc2ef55c86aca122476fa1d5d4e38e2f42..61f19561fad7d21075d70588655e0cb4cc185b16 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: - -<https://browse.libreboot.org/lbmk.git/patch/?id=f34e07ae27e3e6e8508cdebcbd09fdf73fca302d> - -Apply this patch to your local release archive, and it should fix the issue.