docs/build,ivy_common: mention cryptfs bug

139 characters is so 1992

Signed-off-by: Leah Rowe <info@minifree.org>
Signed-off-by: Leah Rowe <leah@libreboot.org>

site/docs/build/index.md

@@ -3,6 +3,16 @@ title: Build from source
 x-toc-enable: true
 ...
 
+WARNING: cryptfs file name limits
+=================================
+
+Do not run the build system on a cryptfs file system, because it has
+very short file name limits and Canoeboot's build system deals with very
+long file names. We commonly get reports from this by Linux Mint users
+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
+with btrfs will do nicely.
+
 WARNING: Flash from bin/, NOT elf/
 ==================================
 

site/docs/build/index.uk.md

@@ -35,30 +35,6 @@ libreboot з доступного джерельного коду.
 Наступний документ описує те, як працює `lbmk`, і як ви можете робити зміни
 до нього: [керівництво обслуговування libreboot](../maintain/)
 
-Release status
-==============
-
-Information about status will be reported during builds; if a board is
-marked as stable, the build proceeds without further input. If the board is
-marked anything other, a warning appears asking if you wish to proceed; to
-disable these warnings, do this before building (not recommended):
-
-	export XBMK_STATUS=n
-
-In Libreboot, we specify: `stable`, `unstable`, `broken` or `untested`.
-The "unstable" marking means that the board boots mostly/entirely reliably
-annd should be safe to use, but may have a few issues, but nothing which would,
-for example, cause safety issues e.g. thermal, data reliability etc.
-
-The `broken` setting means that a given board will likely brick if flashed.
-The `untested` setting means untested.
-
-Release status is always set with regards to the current lbmk revision, on
-the theory that the current revision is being used to generate a full release.
-The setting is decided on a board-by-board basis, taking its various quirks
-and idiosynrasies into account.
->>>>>>> a2164297 (snip)
-
 Multi-threaded builds
 =====================
 

site/docs/install/t400.md

@@ -79,11 +79,6 @@ modified descriptor: see [../install/ich9utils.md](../install/ich9utils.md)*
 Flashing instructions can be found at
 [../install/\#flashprog](../install/#flashprog)
 
-**NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
-now, as of 27 January 2024, which is a fork of flashrom.
-The reason why was explained, in
-the [Libreboot 20240225 release](../../news/libreboot20240225.md#flashprog-now-used-instead-of-flashrom)**
-
 EC update {#ecupdate}
 =========
 

site/docs/install/t500.md

@@ -81,11 +81,6 @@ modified descriptor: see [../install/ich9utils.md](../install/ich9utils.md)*
 Flashing instructions can be found at
 [../install/\#flashprog](../install/#flashprog)
 
-NOTE: Canoeboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
-now, as of 27 January 2024, which is a fork of flashrom.
-The reason why was explained, in
-the [Libreboot 20240225 release](../../news/libreboot20240225.md#flashprog-now-used-instead-of-flashrom)**
-
 EC update {#ecupdate}
 =========
 

site/docs/install/x60_unbrick.md

@@ -3,11 +3,6 @@ title: ThinkPad X60 Recovery guide
 x-toc-enable: true
 ...
 
-**NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
-now, as of 27 January 2024, which is a fork of flashrom.
-The reason why was explained, in
-the [Libreboot 20240225 release](../../news/libreboot20240225.md#flashprog-now-used-instead-of-flashrom)**
-
 "Unbricking" means flashing a known-good (working) ROM. The problem:
 you can't boot the system, making this difficult. In this situation,
 external hardware is needed which can flash the SPI chip (where Canoeboot

site/docs/install/x60tablet_unbrick.md

@@ -3,11 +3,6 @@ title: ThinkPad X60 Tablet Recovery guide
 x-toc-enable: true
 ...
 
-**NOTE: Libreboot standardises on [flashprog](https://flashprog.org/wiki/Flashprog)
-now, as of 27 January 2024, which is a fork of flashrom.
-The reason why was explained, in
-the [Libreboot 20240225 release](../../news/libreboot20240225.md#flashprog-now-used-instead-of-flashrom)**
-
 "Unbricking" means flashing a known-good (working) ROM. The problem:
 you can't boot the system, making this difficult. In this situation,
 external hardware is needed which can flash the SPI chip (where Canoeboot