libreboot
/
lbwww
1
0
Fork 0
Code Packages Projects Releases Activity

remove obsolete note 

Signed-off-by: Leah Rowe <info@minifree.org>
master
Leah Rowe 2024-12-31 21:44:38 +00:00
parent ab51fb8ba6
commit c5273bc020
2 changed files with 8 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
site/docs/build/index.md vendored
View File

@ -13,18 +13,6 @@ who encrypt their home directory with cryptfs; use a serious distro like
Debian or Arch please. And use a decent file system; zfs or perhaps mdcrypt Debian or Arch please. And use a decent file system; zfs or perhaps mdcrypt
with btrfs will do nicely. with btrfs will do nicely.
WARNING: Flash from bin/, NOT elf/
==================================
**WARNING: When you build a ROM image from the Libreboot build system, please
ensure that you flash the appropriate ROM image from `bin/`, NOT `elf/`.
The `elf/` coreboot ROMs do not contain payloads. Libreboot's build system
builds no-payload ROMs under `elf/`, and payloads separately under `elf/`. Then
it copies from `elf/` and inserts payloads from `elf/`, and puts the final ROM
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/)**
Introduction Introduction
============ ============

20
site/docs/build/index.uk.md vendored
View File

@ -3,19 +3,15 @@ title: Побудова з джерельного коду
x-toc-enable: true x-toc-enable: true
... ...
WARNING: Flash from bin/, NOT elf/ WARNING: eCryptfs file name limits
================================== =================================
TODO: translate this section into ukrainian language Do not run the build system on a eCryptfs file system, because it has
very short file name limits and Libreboot's build system deals with very
**WARNING: When you build a ROM image from the Libreboot build system, please long file names. We commonly get reports from this by Linux Mint users
ensure that you flash the appropriate ROM image from `bin/`, NOT `elf/`. who encrypt their home directory with cryptfs; use a serious distro like
The `elf/` coreboot ROMs do not contain payloads. Libreboot's build system Debian or Arch please. And use a decent file system; zfs or perhaps mdcrypt
builds no-payload ROMs under `elf/`, and payloads separately under `elf/`. Then with btrfs will do nicely.
it copies from `elf/` and inserts payloads from `elf/`, and puts the final ROM
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/)**
Introduction Introduction
============ ============