unaligned compliance

when i made peace with fsf back in february 2025, it was never
my intention to align with fsf. i feel that the changes i  made
went too far.

i am returning to a lack of FSDG promotion; Canoeboot will FULLY
COMPLY WITH the GNU FSDG, but shall not promote it. that is why,
for example, it has its own *Binary Blob Extermination Policy*,
which implements, in substance, the exact same laws as GNU FSDG.

GNU is not my friend. what happened in February 2025 was a ceasefire,
to prevent further escalation of the *Cold Boot War*.

this change is more like, zerokelvin boot war.

keep GNU at ARM64's distance, is what i mean to say.

they're not my enemy.

but they're not my friend, and i will not promote their dogma.
canoeboot repeats their same dogma, but without censorship;
for example the Blob Extermination Policy openly and boldly
tells the user all the problems associated with excluding
CPU microcode updates, while continuing to exclude them.
GNU will *lie to you*, by suggesting that they are not required;
they are required, and not using them is foolish, but Canoeboot
is made for fools. Libreboot will always be superior, in every way.

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

site/about.md

@@ -29,8 +29,7 @@ for most non-technical users, but Libreboot and Canoeboot make it easier.
 
 More specifically, Canoeboot is a *fork* of Libreboot, maintained in parallel
 as per each Libreboot release; Canoeboot maintains
-a [zero-blob policy](news/policy.md), adhering to the [GNU Free System Distribution
-Guidelines](https://www.gnu.org/distros/free-system-distribution-guidelines.en.html),
+a [zero-blob policy](news/policy.md), adhering to the GNU Free Software Definition
 in contrast to Libreboot's
 *[Binary Blob Reduction Policy](https://libreboot.org/news/policy.html)*.
 Canoeboot consequently supports far less hardware than Libreboot. Canoeboot
@@ -40,8 +39,8 @@ boot firmware that is *fully* [Free Software](https://writefreesoftware.org/lear
 for the purists out there, whereas Libreboot *does* permit blobs under strict
 circumstances.
 
-The result is that Canoeboot fully complies with the [GNU Free System
-Distribution Guidelines](https://www.gnu.org/distros/free-system-distribution-guidelines.en.html),
+The result is that Canoeboot fully complies with the GNU philosophy, both in
+spirit and in practise,
 and that is the entire purpose of Canoeboot. This means that an organisation
 such as the *Free Software Foundation* shall continue to have a viable project
 which they can use on all of their computers.
@@ -59,7 +58,7 @@ in such cases, e.g. Intel MRC/FSP).
 However, this move made a bunch of FSF people very angry. Canoeboot was later
 created, to provide a spiritual successor to the *old* Libreboot project, from
 before it changed. Despite Libreboot's principles, they are now at odds with
-the much stricter policies set by the GNU FSDG, so Canoeboot was created to
+the much stricter policies set by the GNU project, so Canoeboot was created to
 continue providing a viable coreboot distribution under *its* terms.
 
 In practise, Libreboot *also* provides fully free firmware on a lot of
@@ -80,7 +79,7 @@ distributing the Intel ME; instead, it tells you how to disable the ME by
 simply setting HAP bit, and has you flash Canoeboot while not overwriting the
 original ME; by comparison, Libreboot downloads a new `me.bin` at build time
 and has you flash the entire chip. Canoeboot can't do it Libreboot-style,
-because that would violate GNU FSDG, which states that a project must not
+because that would violate GNU policy, which states that a project must not
 distribute non-free software, nor facilitate its use; re-using what's already
 there doesn't count, since then you're not telling the user to install it, as
 its already installed, so Canoeboot need only ensure that *it* is free software.
@@ -89,8 +88,8 @@ More information about precisely how *Libreboot* differs from Canoeboot,
 and therefore how Canoeboot differs from Libreboot, can be gleaned by looking
 at the following resources:
 
-* [Libreboot Binary Blob Reduction Policy](https://libreboot.org/news/policy.html)
-* [Canoeboot Binary Blob Extermination Policy](news/policy.md) (adhering to GNU FSDG)
+* [Libreboot Binary Blob Reduction Policy](https://libreboot.org/news/policy.html) (unGNU-friendly)
+* [Canoeboot Binary Blob Extermination Policy](news/policy.md) (GNU-friendly)
 * [Libreboot Freedom Status](https://libreboot.org/freedom-status.html)
 
 And check the hardware compatibility list of both projects:

site/docs/install/ga-g41m-es2l.md

@@ -112,7 +112,7 @@ NOTE: due to a bug in the hardware, the MAC address is hardcoded in
 coreboot. Therefore, you must set your own MAC address in your
 operating system.
 
-Use [macchanger](http://www.gnu.org/software/macchanger) in your
+Use GNU macchanger in your
 distro, to set a valid MAC address. By doing this, your NIC should
 work nicely.
 

site/docs/maintain/index.md

@@ -99,7 +99,7 @@ These distros, specifically, are the *most* well-tested:
 * Arch
 * Fedora
 
-You may also have some success with GNU FSDG compliant distros such as Trisquel
+You may also have some success with GNU adherent distros such as Trisquel
 or Parabola. Your mileage may vary.
 
 NOTE: Some patching is also done for non-glibc-based systems, such as

site/faq.md

@@ -165,7 +165,7 @@ NOTE2: In addition to running `me_cleaner`, you could also instead just set
 the HAP bit (ME AltDisable) in the Flash Descriptor, which would disable the
 ME after early BringUp (only the ME's BUP module will be used). Since 23
 May 2025, Canoeboot supports Intel Sandybridge, Ivybridge and Haswell gen,
-and disables the Intel ME using *this method* instead, because under GNU FSDG
+and disables the Intel ME using *this method* instead, because under GNU policy
 it will not distribute such files itself.
 
 On *most* current Intel platforms that have Intel ME, it is now possible

site/index.md

@@ -29,8 +29,8 @@ of these payloads in a single image, and you choose one at boot time.
 Canoeboot is a *special fork* of [Libreboot](https://libreboot.org/), maintained
 in parallel to it by the same developer (Leah Rowe), who maintains both projects.
 Canoeboot [removes all binary blobs](news/policy.md) from coreboot, in
-adherence to the *GNU Free System Distribution Guidelines* (GNU FSDG), unlike
-Libreboot which has a more
+full adherence to the noble and quite correct *GNU Free Software Definition*,
+unlike Libreboot which has a more
 pragmatic [Binary Blob Reduction Policy](https://libreboot.org/news/policy.html).
 Canoeboot is provided for [Free Software](https://writefreesoftware.org/learn)
 purists, who *only* want Free Software, regardless of technical details. [Canoeboot

site/news/policy.md

@@ -9,11 +9,10 @@ code, replacing it with Free Software whenever possible, but also supports
 much newer hardware than Canoeboot, and certain vendor code is still required
 on many newer machines. Libreboot's policy enables newer hardware support, but
 does mean that certain binary blobs may sometimes be provided; meanwhile,
-Canoeboot is maintained specifically in adherence to the *[GNU Free System
-Distribution Guidelines](https://www.gnu.org/distros/free-system-distribution-guidelines.en.html)*,
+Canoeboot is maintained specifically in adherence to the GNU Free Software Definition,
 ensuring that Canoeboot only ever distributes entirely *Free Software*.
 
-Canoeboot, then, is a GNU FSDG compliant coreboot distribution. The page you're
+Canoeboot, then, is a holy GNU compliant coreboot distribution. The page you're
 reading now, will attempt to describe *how* Canoeboot complies with it,
 specifically, on a technical level. Some nuance is always present, in any such
 effort, so it's critical that users do understand this. Please also read