tone the README way, way down
canoeboot is a fsdg coreboot distro, so it should talk like one Signed-off-by: Leah Rowe <info@minifree.org>audit2-merge1
parent
29d6d294ab
commit
97d502ccc8
37
README.md
37
README.md
|
@ -18,27 +18,31 @@ prefer Canoeboot, which is essentially a *censored* Libreboot (no binary
|
|||
blobs allowed, so only few boards supported whereas Libreboot supports more
|
||||
boards while minimising the number of blobs to zero when possible).
|
||||
|
||||
For more context, please read Libreboot's Binary Blob Reduction Policy:
|
||||
Canoeboot is provided for the purists who absolutely wish to have no proprietary
|
||||
software of any kind. Regardless of any other firmware that exists outside of it,
|
||||
the boot flash on your system will be *entirely free software* if you install
|
||||
Canoeboot on it. That includes a complete lack of CPU microcode updates, as per
|
||||
FSF policy.
|
||||
|
||||
<https://libreboot.org/news/policy.html>
|
||||
More specifically: Canoeboot is engineered to comply with the GNU Free System
|
||||
Distribution Guidelines. It has, as of November 2023 releases, been strictly
|
||||
audited by FSF licensing staff (Craig Topham lead the audit), and it is listed
|
||||
on the FSF's own Free Software Directory.
|
||||
|
||||
You may also read Canoeboot's about page, which contains more history pertaining
|
||||
to *Canoeboot*. Please read this page:
|
||||
|
||||
<https://canoeboot.org/about.html>
|
||||
|
||||
Canoeboot is inferior to Libreboot, in every way, and you should never use it.
|
||||
Libreboot previously complied with that same policy, but changed to a different
|
||||
one permitting binary blobs in limited circumstances, so as to support more newer
|
||||
machines. Canoeboot is, then, a continuation of the traditional Libreboot
|
||||
project prior to that policy change. Some users still want it, so, Canoeboot
|
||||
releases are rigoriously maintained, re-basing on newer Libreboot releases over
|
||||
time, just like how, say, Trisquel, re-bases itself on each new Ubuntu release.
|
||||
|
||||
Project goals
|
||||
=============
|
||||
|
||||
- Be Libreboot, but adhere to GNU FSDG as policy. This means that many boards
|
||||
from Libreboot must be removed; Canoeboot is therefore inferior to Libreboot,
|
||||
and always will be. It provides a useful proof of concept, showing what
|
||||
is still possible when you completely bastardise Libreboot in like with
|
||||
FSF/GNU dogma - and Canoeboot does it better than GNU ever could.
|
||||
- *Support as much hardware as possible!* (within the restrictions imposed
|
||||
by GNU FSDG policy)
|
||||
- Obviously, support as much hardware as possible (within the limitations
|
||||
imposed by GNU FSDG, and using what coreboot happens to have in its source
|
||||
tree - Canoeboot also heavily patches coreboot, sometimes adding new
|
||||
mainboards out-of-tree).
|
||||
- *Make coreboot easy to use*. Coreboot is notoriously difficult
|
||||
to install, due to an overall lack of user-focused documentation
|
||||
and support. Most people will simply give up before attempting to
|
||||
|
@ -64,7 +68,8 @@ Not a coreboot fork!
|
|||
--------------------
|
||||
|
||||
Canoeboot is not a fork of coreboot. Every so often, the project
|
||||
re-bases on the latest version of coreboot, with the number of custom
|
||||
re-bases on the latest version of coreboot, by virtue of maintaining sync
|
||||
with Libreboot releases (minus un-GNU parts), with the number of custom
|
||||
patches in use minimized. Tested, *stable* (static) releases are then provided
|
||||
in Canoeboot, based on specific coreboot revisions.
|
||||
|
||||
|
|
Loading…
Reference in New Issue