libreboot / lbwww (public) (License: Unspecified) (since 2023-04-11) (hash sha1)
libreboot website (markdown files). https://libreboot.org/
Clone URLs: https://rocketgit.com/user/libreboot/lbwww ssh://rocketgit@ssh.rocketgit.com/user/libreboot/lbwww git://git.rocketgit.com/user/libreboot/lbwww
25.04 master
List of commits:
Subject Hash Author Date (UTC)
snip 7c63e81b3212e22324bb300e30cba3f109a8ddcf Leah Rowe 2025-01-18 02:07:42
grammar 927a06cdc65281ceff6efdca058cf1cd4725e096 Leah Rowe 2025-01-17 13:24:59
snip 62b5b1950e8d862924b6c92fc2d8c1ae91c75f1c Leah Rowe 2025-01-17 10:41:44
further calamity 5662b578d8c97c024161bd9dd3d3f5c1fedb66f3 Leah Rowe 2025-01-17 10:15:39
clarification 0d6d90bf1eabd0d75c8b902fca8123af4f8c6617 Leah Rowe 2025-01-17 10:13:29
Libreboot 2025 release schedule 55722b56431b61b204efe00127cb9db089965342 Leah Rowe 2025-01-17 10:03:06
t480 notes: mention rollback protection 6cfd22e1f6e2104b99850546bf9f7743cc82f285 Leah Rowe 2025-01-17 01:42:41
other.md: merge chrultrabook with mrchromebox ee096776a97410398581e125397ee9b5a3bbd03c Leah Rowe 2025-01-14 17:59:28
snip e64e6a065d55c680b21948e833234f019c32b2c6 Leah Rowe 2025-01-14 13:30:29
correction 3f51720e2aaa51ddc5de19757b06d4715526d67e Leah Rowe 2025-01-14 12:57:06
snip a5a8a8daea53761ebceb53bf09c2acddadb49d04 Leah Rowe 2025-01-13 15:47:37
priority 5d516331cb506a2b1d929add03227b20860cab37 Leah Rowe 2025-01-13 15:38:13
fix oversight ceaaeb98d924d89fd91bda78300423348f48bf79 Leah Rowe 2025-01-13 14:50:27
expand other.md but shorten the intro e5d30675db4119269259b3c4539278639da28522 Leah Rowe 2025-01-13 13:37:18
simplify the skulls section in other.md 4702e167673363af0e63c0de51fbd220d7f45a55 Leah Rowe 2025-01-12 12:36:05
payloads, not "programs" 97b0fa3c600b3a2dc0446029c38a7d538078ab7c Leah Rowe 2025-01-12 04:20:27
link to coreboot build docs on other.md c278f8b5bf1fb020d9bec53c93c620aa1c9469c2 Leah Rowe 2025-01-12 02:05:08
more links ec57689078a54afe1c0ba5a73f3cdb3f4ce46759 Leah Rowe 2025-01-12 01:29:32
reparieren der deutschen homepage 572ea3bdc15b8a33016888333e731307f0edab57 Leah Rowe 2025-01-12 00:43:39
homepage: emphasize the coreboot distro aspect f78ee7861af3a6b930cf640d7dfce1942dad4a2b Leah Rowe 2025-01-12 00:34:05
Commit 7c63e81b3212e22324bb300e30cba3f109a8ddcf - snip
Signed-off-by: Leah Rowe <leah@libreboot.org>
Author: Leah Rowe
Author date (UTC): 2025-01-18 02:07
Committer name: Leah Rowe
Committer date (UTC): 2025-01-18 02:07
Parent(s): 927a06cdc65281ceff6efdca058cf1cd4725e096
Signer:
Signing key:
Signing status: N
Tree: 7edc7814ca460c0f9531ff61e3e4a82f258ba4bf
File Lines added Lines deleted
site/news/10.md 85 75
File site/news/10.md changed (mode: 100644) (index 244d6a7..c5a2b07)
... ... and professional, with clear documentation. Coreboot documentation today is
106 106 much better, but it was very poor quality in 2013 (MediaWiki site with lots much better, but it was very poor quality in 2013 (MediaWiki site with lots
107 107 of errant pages, poorly organised). of errant pages, poorly organised).
108 108
109 It came with a twist: Libreboot initially complied with the FSF's own RYF
110 criteria, and the GNU FSDG (Free System Distribution Guidelines). Under this
109 It came with a twist: Libreboot initially only permitted libre code. Under this
111 110 policy, no binary blobs are allowed. I believed in it then, because in practise policy, no binary blobs are allowed. I believed in it then, because in practise
112 111 it seemed like a good idea and didn't do any harm. It would later become a it seemed like a good idea and didn't do any harm. It would later become a
113 112 liability, for reasons laid out in Libreboot's modern [Binary Blob Reduction liability, for reasons laid out in Libreboot's modern [Binary Blob Reduction
 
... ... generator of any kind.
463 462 On the coding side of things, many GNU programs use things like GNU Autoconf On the coding side of things, many GNU programs use things like GNU Autoconf
464 463 for configuration, in build systems, and GNU has a certain *coding style* that for configuration, in build systems, and GNU has a certain *coding style* that
465 464 is preferred. To speed up entry into GNU, many of the requirements were is preferred. To speed up entry into GNU, many of the requirements were
466 overlooked since, ideologically speaking, Libreboot aligned with the GNU
467 Free System Distribution Guidelines (FSDG) at that time, so Libreboot officially
468 joined GNU on 14 April 2016, under the assumption that it would gradually
465 overlooked since, ideologically speaking, Libreboot was otherwise entirely free.
466 We joined GNU on 14 April 2016, under the assumption that it would gradually
469 467 start integrating with the GNU infrastructure. start integrating with the GNU infrastructure.
470 468
471 469 *Three* Libreboot releases were released, during its GNU membership, namely: *Three* Libreboot releases were released, during its GNU membership, namely:
 
... ... Libreboot's popularity reached great heights during this time, greatly expanding
478 476 and attracting many new developers. Joining GNU accelerated this further, and attracting many new developers. Joining GNU accelerated this further,
479 477 though it came with certain drawbacks. though it came with certain drawbacks.
480 478
481 At that time, I believed in the GNU FSDG policy, and I saw GNU membership as
482 beneficial to the Libreboot project, not because I was interested in GNU for
483 any technical merit; Libreboot is boot firmware, whereas GNU has always been
484 about providing an operating system with the libc and many useful applications.
485 Libreboot did not really fit into the GNU infrastructure, but it aligned with
486 the ideology both in theory and in practise, and the prestige of it at that time
487 would attract more help.
488
489 479 I later realised otherwise, regarding the ideology; more on this later, in I later realised otherwise, regarding the ideology; more on this later, in
490 480 the sections about osboot, and the osboot/libreboot merge, and events after the sections about osboot, and the osboot/libreboot merge, and events after
491 481 that. that.
 
... ... when the latter forked from Freenode after a hostile takeover. Thankfully, that
1149 1139 drama ended quickly and we ended up with Libera being the clear winner. drama ended quickly and we ended up with Libera being the clear winner.
1150 1140
1151 1141 Anyway: I finally did get a new Libreboot release out, based on the work that Anyway: I finally did get a new Libreboot release out, based on the work that
1152 I had started in osboot, but at that time still complying with the GNU Free
1153 System Distribution Guidelines, like 2016 Libreboot did.
1142 I had started in osboot, but at that time Libreboot had the blob-free policy.
1154 1143
1155 1144 I did not use any of the work in the *Paper* re-write. I used precisely zero I did not use any of the work in the *Paper* re-write. I used precisely zero
1156 1145 lines of code from Sebastian and Andrew's work. I did it all myself. My decision lines of code from Sebastian and Andrew's work. I did it all myself. My decision
 
... ... Osboot from 2021-2022
1174 1163
1175 1164 The *osboot* project continued, since December 2020 when it started. I started The *osboot* project continued, since December 2020 when it started. I started
1176 1165 adding many new boards to it. The purpose of Osboot was the same as Libreboot, adding many new boards to it. The purpose of Osboot was the same as Libreboot,
1177 except that it had the [Binary Blob Reduction Policy](policy.md) that Libreboot
1178 now uses, but back then, Libreboot adhered to GNU FSDG.
1166 except that it had the [Binary Blob Reduction Policy](policy.md) instead.
1167 This is the policy that *modern* Libreboot uses, since merging with osboot.
1179 1168
1180 1169 Goals of osboot Goals of osboot
1181 1170 --------------- ---------------
1182 1171
1183 1172 I *wanted* to start a project like osboot much earlier, in 2017. In fact, I was I *wanted* to start a project like osboot much earlier, in 2017. In fact, I was
1184 1173 going to, but real life got in the way and I went on hiatus for a few years. going to, but real life got in the way and I went on hiatus for a few years.
1185 I concluded as early as 2017 that the FSDG policy was a liability, especially
1174 I concluded as early as 2017 that the no-blob policy was a liability, especially
1186 1175 after `me_cleaner` became available. I realised that there were many more after `me_cleaner` became available. I realised that there were many more
1187 1176 machines out there, that I then considered acceptable from a software freedom machines out there, that I then considered acceptable from a software freedom
1188 perspective, even if they did not comply with FSF RYF or GNU FSDG; I regard
1189 the FSF policy as overly dogmatic, and I've always thought so, but in practise
1177 perspective, even if they did require an additional blob or two; I regard
1178 the no-blob policy as overly dogmatic, and I've always thought so, but in practise
1190 1179 it didn't hurt anything because Intel ME was always a problem. I didn't know it didn't hurt anything because Intel ME was always a problem. I didn't know
1191 1180 ME neutering was possible, until I found out about `me_cleaner` - I would never ME neutering was possible, until I found out about `me_cleaner` - I would never
1192 1181 provide anyone with a setup that uses a non-neutered ME, because of the networking provide anyone with a setup that uses a non-neutered ME, because of the networking
 
... ... everyone supported this move. Sure enough, I saw a relative lack of opposition
1257 1246 to it; though, some of the more dogmatic members of the FSF were quite upset. to it; though, some of the more dogmatic members of the FSF were quite upset.
1258 1247 This level of upset later caused.... well, that's what I'm going to cover next. This level of upset later caused.... well, that's what I'm going to cover next.
1259 1248
1260 GNU Boot
1249 FSF fork
1261 1250 ======== ========
1262 1251
1263 1252 The purpose of today's article has been to write a rigorous history section for The purpose of today's article has been to write a rigorous history section for
 
... ... in 2017.
1311 1300 I don't feel bad about what I did. What they did is widely considered to be I don't feel bad about what I did. What they did is widely considered to be
1312 1301 a *dick move* in the free software movement; it is widely considered impolite a *dick move* in the free software movement; it is widely considered impolite
1313 1302 to fork an active project and use the same name. The unwritten rule is always to fork an active project and use the same name. The unwritten rule is always
1314 that you use a new name. It's more than that though: in their initial fork, and
1315 also in GNU Boot, they didn't just say: this is what we are, what we do and why
1316 you should use our product. No. They put a paragraph in their documentation,
1303 that you use a new name. It's more than that though: in the FSF's fork, they
1304 didn't just say: this is what we are, what we do and why you should use our
1305 product. No. They put a paragraph in their documentation,
1317 1306 urging people to *delete* links to libreboot.org, and link to them. *They were urging people to *delete* links to libreboot.org, and link to them. *They were
1318 1307 out for blood*. out for blood*.
1319 1308
1320 Fork attempt 2: GNU Boot
1321 ------------------------
1309 Fork attempt 2: GNU
1310 -------------------
1322 1311
1323 1312 So I've responded in kind, ever since. Regardless of whether they succeed or So I've responded in kind, ever since. Regardless of whether they succeed or
1324 1313 whether they are competent, a thought exists in their head. A dream, you could whether they are competent, a thought exists in their head. A dream, you could
1325 1314 say. Their dream is a world in which Leah Rowe and Libreboot no longer exist. say. Their dream is a world in which Leah Rowe and Libreboot no longer exist.
1326 1315 They wanted to destroy me. It's evident in Denis's LP2023 talk, where he said They wanted to destroy me. It's evident in Denis's LP2023 talk, where he said
1327 1316 he wanted to "continue" the Libreboot project. In his mind, there is no room for he wanted to "continue" the Libreboot project. In his mind, there is no room for
1328 disagreement over policy; it's FSDG or nothing. I had to play by their rules,
1329 or go home.
1317 disagreement over policy; it's their way or nothing. I had to play by their
1318 rules, or go home.
1330 1319
1331 1320 During that time, and subsequently, I and others had repeatedly put pressure During that time, and subsequently, I and others had repeatedly put pressure
1332 1321 on them to rename. I personally came up with the name *GNU Boot* - and suggested on them to rename. I personally came up with the name *GNU Boot* - and suggested
 
... ... that they use it. It's a name that I myself came up with several years prior,
1334 1323 when I was considering whether to work for GNU again *myself*, but as an actual when I was considering whether to work for GNU again *myself*, but as an actual
1335 1324 fork of coreboot. The name just works. fork of coreboot. The name just works.
1336 1325
1337 They did rename, to GNU Boot, but only after I forced them to do so. I forced
1326 GNU did rename their project, but only after I forced them to do so. I forced
1338 1327 them to do so, by exposing the moral bankrupcy on their part, in their initial them to do so, by exposing the moral bankrupcy on their part, in their initial
1339 effort to steal the Libreboot name.
1328 effort to steal the Libreboot name. Their initial plan was to create a newly
1329 established *GNU Libreboot* project.
1340 1330
1341 On this day, GNU Boot 0.1 RC3 was imminent for release, on this day, and it
1331 By 2023-12-12, GNU's fork had a new RC imminent for release, on this day, and it
1342 1332 was still based largely on Libreboot 20220710, with only superficial changes on was still based largely on Libreboot 20220710, with only superficial changes on
1343 1333 top of it. it still has all the old, obsolete revisions for all projects, top of it. it still has all the old, obsolete revisions for all projects,
1344 1334 including coreboot. It still has all of the same bugs, that Libreboot has since including coreboot. It still has all of the same bugs, that Libreboot has since
1345 1335 fixed, especially during 2023. Libreboot is *vastly* superior, in every way. fixed, especially during 2023. Libreboot is *vastly* superior, in every way.
1346 1336
1347 Unlike with their first attempt, GNU Boot is fully hosted on the GNU Savannah
1348 infrastructure, as any proper GNU project should be. I *respect* the GNU Boot
1337 Unlike with their first attempt, GNU's new project is hosted on the GNU Savannah
1338 infrastructure, as any proper GNU project should be. I *respect* the latter GNU
1349 1339 project more, because it is its own thing, that doesn't try to ride off of my project more, because it is its own thing, that doesn't try to ride off of my
1350 1340 coattails. However, my perception of them is permanently coloured by their coattails. However, my perception of them is permanently coloured by their
1351 1341 initial hostile actions; and the only reason they ceased such actions was initial hostile actions; and the only reason they ceased such actions was
 
... ... and now:
1416 1406 Canoeboot Canoeboot
1417 1407 --------- ---------
1418 1408
1419 Purely for my own entertainment, I decided to re-create FSDG Libreboot *myself*.
1420 FSDG is the policy that GNU Boot uses, that Libreboot previously used, before
1421 it adopted the modern [Binary Blob Reduction Policy](policy.md) - GNU Boot
1422 started, specifically because it opposed the new policy in Libreboot.
1409 Purely for my own entertainment, I decided to re-create blob-free Libreboot *myself*.
1410 It is the same one that GNU uses, that Libreboot previously used, before
1411 it adopted the modern [Binary Blob Reduction Policy](policy.md) - GNU started
1412 their new project, specifically because it opposed the new policy in Libreboot.
1423 1413
1424 Well, GNU Boot seemed to be going nowhere fast. I monitor their Git activity
1414 Well, GNU's fork seemed to be going nowhere fast. I monitor their Git activity
1425 1415 daily, and their development pace is much slower than mine; slower than mine, daily, and their development pace is much slower than mine; slower than mine,
1426 1416 even when I'm going slow. I thought to myself: what if a *competently* even when I'm going slow. I thought to myself: what if a *competently*
1427 engineered solution existed, like GNU Boot but not?
1417 engineered solution existed? One maintained by someone who's been doing this
1418 for over a decade?
1428 1419
1429 1420 And thus, [Canoeboot](https://canoeboot.org/) was born. I still mainly develop And thus, [Canoeboot](https://canoeboot.org/) was born. I still mainly develop
1430 1421 Libreboot, but I spend a few hours after each release, bringing Canoeboot up Libreboot, but I spend a few hours after each release, bringing Canoeboot up
 
... ... Canoeboot is even listed on the FSF's
1436 1427 Topham approved it, he's the FSF's current licensing and compliance manager, Topham approved it, he's the FSF's current licensing and compliance manager,
1437 1428 at least on 12 December 2023. at least on 12 December 2023.
1438 1429
1439 The purpose of Canoeboot is to simply exist, complying with GNU Boot policy
1440 while being superior to it in every way, outcompeting it so fast that the
1441 GNU Boot project is constantly behind - it's done, specifically to demonstrate
1430 The purpose of Canoeboot is to simply exist, adhering to the no-blob policy
1431 while being superior to GNU in every way, outcompeting it so fast that GNU's
1432 own project is constantly behind - it's done, specifically to demonstrate
1442 1433 the superiority of Libreboot policy, by showing what Libreboot *would have the superiority of Libreboot policy, by showing what Libreboot *would have
1443 been*, if it didn't adopt the new policy.
1434 been*, if it didn't adopt the [Binary Blob Reduction Policy](policy.md) policy.
1444 1435
1445 1436 The FSF failed in its coup. My countercoup was a success. I madly beat them at The FSF failed in its coup. My countercoup was a success. I madly beat them at
1446 1437 their own game. The FSF's strategy *might* have worked, if I hadn't been so their own game. The FSF's strategy *might* have worked, if I hadn't been so
 
... ... new Libreboot release. I actually *describe* how this syncing is done, in great
1458 1449 detail, on Canoeboot's [about page](https://canoeboot.org/about.html) - and detail, on Canoeboot's [about page](https://canoeboot.org/about.html) - and
1459 1450 the first Canoeboot release was done, based on the latest Libreboot release at the first Canoeboot release was done, based on the latest Libreboot release at
1460 1451 that time, in only 2 days, with all of Libreboot's vast improvements in it that time, in only 2 days, with all of Libreboot's vast improvements in it
1461 compared to GNU Boot. As of this day, 12 December 2023, Canoeboot is about 1
1462 year ahead of GNU Boot in terms of code development, and 2 years ahead on the
1463 writing of documentation. Conversely, GNU Boot is 1 year and 2 years out of
1452 compared to GNU's work, or lack thereof. As of this day, 12 December 2023,
1453 Canoeboot is about 1 year ahead of GNU in terms of code, and 2 years ahead on
1454 the writing of documentation. Conversely, GNU is *1 year* and *2 years* out of
1464 1455 date, in terms of code and documentation respectively. date, in terms of code and documentation respectively.
1465 1456
1466 1457 2024 reconciliation intentions 2024 reconciliation intentions
 
... ... date, in terms of code and documentation respectively.
1471 1462 The *FSF* started the coldboot war. Libreboot merely won it. The *FSF* started the coldboot war. Libreboot merely won it.
1472 1463
1473 1464 From 2024 onward, unless more hostilities develop from FSF/GNU's side, I intend From 2024 onward, unless more hostilities develop from FSF/GNU's side, I intend
1474 to adopt a more conciliatory approach toward GNU Boot. I won the battle of 2023.
1465 to adopt a more conciliatory approach toward GNU/FSF. I won the battle of 2023.
1475 1466 I won the *cold boot war*, but the real battle is this: how do we get free boot I won the *cold boot war*, but the real battle is this: how do we get free boot
1476 1467 firmware to non-technical end users, efficiently and reliably? The answer to firmware to non-technical end users, efficiently and reliably? The answer to
1477 that question is projects such as Libreboot, or indeed others like GNU Boot,
1478 Heads, Skulls, MrChromebox... you name it. Distros, designed similarly to
1479 Linux distros, but for building boot firmware instead.
1468 that question is projects such as Libreboot, or indeed others like, Heads,
1469 Skulls, MrChromebox... you name it. Distros, designed similarly to Linux
1470 distros, but for building boot firmware instead.
1480 1471
1481 1472 The *first* coldbootwar occured between 19 March 2023 and 31 December 2023, The *first* coldbootwar occured between 19 March 2023 and 31 December 2023,
1482 1473 described in the article above. described in the article above.
 
... ... Much of 2023 was spent counteracting the FSF's coup, because they were hostile
1485 1476 to the Libreboot project, but I decided that I will avoid any such counter to the Libreboot project, but I decided that I will avoid any such counter
1486 1477 action from now on. I will stil develop Canoeboot, but my main focus is action from now on. I will stil develop Canoeboot, but my main focus is
1487 1478 Libreboot. My conclusion is that, so long as my own efforts exist, and I keep Libreboot. My conclusion is that, so long as my own efforts exist, and I keep
1488 working on everything, the GNU Boot project is no threat to Libreboot whatsoever.
1479 working on everything, the GNU project is no threat to Libreboot whatsoever.
1489 1480
1490 Towards the end of 2023, there *was* in fact cooperation, between the GNU Boot
1481 Towards the end of 2023, there *was* in fact cooperation, between the GNU project
1491 1482 and Libreboot projects, in the form of small patches; Denis Carikli sent a few and Libreboot projects, in the form of small patches; Denis Carikli sent a few
1492 1483 patches and reports to Canoeboot and the Untitled Static Site Generator, and I patches and reports to Canoeboot and the Untitled Static Site Generator, and I
1493 1484 did similar for the GNU boot project. The FSF themselves even decided to did similar for the GNU boot project. The FSF themselves even decided to
1494 1485 accept Canoeboot, on their Free Software Directory. See: accept Canoeboot, on their Free Software Directory. See:
1495 1486 <https://directory.fsf.org/wiki/Canoeboot> <https://directory.fsf.org/wiki/Canoeboot>
1496 1487
1497 My only issue with GNU Boot at the start of 2023 was that they wanted
1488 My only issue with GNU and FSF at the start of 2023 was that they wanted
1498 1489 to *replace* the Libreboot project, by using the same name. They *did* try to to *replace* the Libreboot project, by using the same name. They *did* try to
1499 1490 destroy the Libreboot project, and take it for themselves. Things pretty much destroy the Libreboot project, and take it for themselves. Things pretty much
1500 1491 calmed towards the end of 2023, and now the two projects/communities operate calmed towards the end of 2023, and now the two projects/communities operate
 
... ... anymore; to do so was necessary, when they themselves did the same, because
1509 1500 the FSF is a well-funded organisation with much bigger reach and would walk the FSF is a well-funded organisation with much bigger reach and would walk
1510 1501 all over me if I allowed it, so it was necessary to show strength. all over me if I allowed it, so it was necessary to show strength.
1511 1502
1512 However, throughout 2024, GNU Boot has essentially been a dead project; they
1503 However, throughout 2024, GNU's fork has essentially been a dead project; they
1513 1504 haven't done any work on their build system of any consequence, and haven't haven't done any work on their build system of any consequence, and haven't
1514 1505 even updated their documentation that heavily. Their main focus was on even updated their documentation that heavily. Their main focus was on
1515 1506 integrating the Untitled Static Site Generator into their infrastructure, integrating the Untitled Static Site Generator into their infrastructure,
1516 1507 which otherwise relies heavily on TexInfo documents and CVS (Untitled relies on which otherwise relies heavily on TexInfo documents and CVS (Untitled relies on
1517 1508 Markdown and Git heavily - the FSF actually made a special rsync server for Markdown and Git heavily - the FSF actually made a special rsync server for
1518 GNU Boot to manually upload HTML files to, generated by Untitled, which they
1519 wrapped around directly, within the GNU Boot build system).
1509 to manually upload HTML files to, generated by Untitled, which they
1510 wrapped around directly, within their fork of the Libreboot build system).
1520 1511
1521 1512 Last remarks Last remarks
1522 1513 ============ ============
 
... ... your patience and your courage with a cool easter egg:
1536 1527
1537 1528 The `minifree.org` domain name initially hosted a website that was teaching The `minifree.org` domain name initially hosted a website that was teaching
1538 1529 people how to use VPNs and Tor, and it contained information about how to people how to use VPNs and Tor, and it contained information about how to
1539 be private on the internet. I later planned on making it into an FSDG-compliant
1530 be private on the internet. I later planned on making it into a blob-free
1540 1531 fork of *Puppy Linux* - because Puppy is small, lightweight, and mini is another fork of *Puppy Linux* - because Puppy is small, lightweight, and mini is another
1541 1532 word for *small*, and it was to be a fully free distribution, containing no word for *small*, and it was to be a fully free distribution, containing no
1542 1533 blobs, not even firmware. Minifree GNU/Linux. I later scrapped the plan, and blobs, not even firmware. Minifree GNU/Linux. I later scrapped the plan, and
 
... ... on [minifree.org](https://minifree.org/).
1550 1541 January 1st, 2025, UPDATE! January 1st, 2025, UPDATE!
1551 1542 ======================== ========================
1552 1543
1553 The truce of 2024 has ended. GNU Boot did a talk during 38C3 conference, where
1544 The truce of 2024 has ended. GNU did a talk during 38C3 conference, where
1554 1545 they spent at least *one third* of the talk, telling people to stop using they spent at least *one third* of the talk, telling people to stop using
1555 1546 Libreboot, to stop promoting Libreboot, stop contributing to it. This is an Libreboot, to stop promoting Libreboot, stop contributing to it. This is an
1556 1547 act of war against the Libreboot project. act of war against the Libreboot project.
 
... ... is that there is no longer good will from Libreboot towards the GNU project.
1561 1552
1562 1553 Canoeboot will be developed as aggressively as before, if not more so. It will Canoeboot will be developed as aggressively as before, if not more so. It will
1563 1554 be maintained and updated aggressively, but now with this fact in mind, and be maintained and updated aggressively, but now with this fact in mind, and
1564 with the view that the GNU Boot project must be contained; the mere existence
1565 of the Canoeboot project is a direct attack on GNU Boot, and it will continue.
1555 with the view that the GNU project must be contained; the mere existence
1556 of the Canoeboot project is a direct attack on GNU, and it will continue. It
1557 is an attack, because *they* can't attack *Canoeboot* lest they look like
1558 hypocrites, which they are, but looking like it is worse. They were the ones
1559 who tried to steal the Libreboot name, and they the aggressors; Canoeboot was
1560 formed as an act of self defense to protect Libreboot, and Canoeboot is a fun
1561 technical challenge.
1566 1562
1567 1563 I was going to approach the GNU project and start a discussion about shutting I was going to approach the GNU project and start a discussion about shutting
1568 down the Canoeboot project, and merge it with GNU Boot, helping them to bring
1569 their project up to date - for example, as of January 2025, GNU Boot *still*
1570 uses the same late 2021 coreboot and GRUB revisions that it used when GNU
1571 Boot started back in June 2023.
1564 down the Canoeboot project, and merge it with GNU. As of January 2025, GNU's
1565 own Libreboot fork *still* uses the same late 2021 coreboot and GRUB revisions
1566 that it used when they started back in June 2023. As of December 2024, the
1567 Canoeboot project used upstream revisions *from December 2024* and with
1568 completely up to date documentation.
1572 1569
1573 1570 Such an attempt at collaboration was made before, and it was rejected. It is Such an attempt at collaboration was made before, and it was rejected. It is
1574 clear now that the GNU Boot developers have nothing but contempt. Therefore,
1575 the agenda from 1 January 2025 onward, is to *replace* GNU Boot; to move
1571 clear now that the GNU/FSF developers have nothing but contempt. Therefore,
1572 the agenda from 1 January 2025 onward, is to *replace* GNU, not join it; to move
1576 1573 so far ahead of the project on a technical level, and to overwhelm it so much so far ahead of the project on a technical level, and to overwhelm it so much
1577 in that regard, that the project effectively no longer exists as a practical
1578 matter.
1579
1580 Canoeboot is vastly superior to GNU Boot. Its [design](https://canoeboot.org/docs/maintain/)
1574 in that regard, yet offer no truce and no way out for GNU. The end result shall
1575 be that FSF/GNU fans only have Canoeboot, and nothing else. GNU has shown
1576 historical opposition and hostility to the Libreboot project, to the extent
1577 that they even tried to steal the name; therefore, I will show no mercy.
1578
1579 This is not about tech. This is about dreams. A battle of dreams. My dream is
1580 to maintain a highly popular [Free Software](https://writefreesoftware.org/learn)
1581 boot project, namely Libreboot and Canoeboot; this dream exists because I enjoy
1582 the work, and I believe in Free Software. GNU's dream has been to steal mine;
1583 I do all the work, and they wanted to steal my thunder.
1584
1585 Canoeboot is vastly superior to anything GNU would ever do, or has done.
1586 Canoeboot's highly efficient [design](https://canoeboot.org/docs/maintain/)
1581 1587 is much simpler and more powerful in practise, doing *more* in fewer lines is much simpler and more powerful in practise, doing *more* in fewer lines
1582 1588 of code - and it supports more hardware. Canoeboot is, at this time, interested of code - and it supports more hardware. Canoeboot is, at this time, interested
1583 1589 in more GM45-based Dell Latitude models and X4x-based Dell OptiPlex 780 variants, in more GM45-based Dell Latitude models and X4x-based Dell OptiPlex 780 variants,
 
... ... In general, Libreboot's [Binary Blob Reduction Policy](policy.md) dictates
1598 1604 that if Free Software *can* be used, it must be - as a result, many systems that if Free Software *can* be used, it must be - as a result, many systems
1599 1605 supported by Libreboot, boot entirely with free software. Libreboot is a free supported by Libreboot, boot entirely with free software. Libreboot is a free
1600 1606 software project, whose primary goal is to increase software freedoms for users software project, whose primary goal is to increase software freedoms for users
1601 by providing them with free boot firmware. And yet: GNU Boot's talk strongly
1607 by providing them with free boot firmware. And yet: GNU talk strongly
1602 1608 suggests that Libreboot is a *proprietary software project*. suggests that Libreboot is a *proprietary software project*.
1603 1609
1604 In GNU Boot's talk, they directly state that I, Leah Rowe, am "against 100%
1610 In GNU talk, they directly state that I, Leah Rowe, am "against 100%
1605 1611 free software" - also false. I want everyone to use Free Software exclusively, free software" - also false. I want everyone to use Free Software exclusively,
1606 1612 but the reality is that this is literally impossible, on any hardware. The but the reality is that this is literally impossible, on any hardware. The
1607 1613 reason is strongly described in Libreboot's [Freedom Status](../freedom-status.md) reason is strongly described in Libreboot's [Freedom Status](../freedom-status.md)
1608 1614 and [Binary Blob Reduction Policy](policy.md) pages. and [Binary Blob Reduction Policy](policy.md) pages.
1609 1615
1610 It is clear, then, that the GNU Boot project wishes to undermine the Libreboot
1616 It is clear, then, that the GNU project wishes to undermine the Libreboot
1611 1617 project; their dream is that Libreboot will one day cease to exist. So in project; their dream is that Libreboot will one day cease to exist. So in
1612 response, Libreboot has this dream too, but about GNU Boot.
1618 response, Libreboot has this dream too, but about GNU. My revenge shall be
1619 to continue maintaining Libreboot and Canoeboot, to a high standard, and to
1620 get ever further ahead of them both technically, and politically.
1613 1621
1614 1622 The outcome of coldbootwar2 will be described in the *next* decade anniversary page, The outcome of coldbootwar2 will be described in the *next* decade anniversary page,
1615 1623 on 12 December 2033. It is strongly expected that Libreboot will continue to on 12 December 2033. It is strongly expected that Libreboot will continue to
1616 1624 exist and thrive by then; today's Libreboot will be vastly inferior to that exist and thrive by then; today's Libreboot will be vastly inferior to that
1617 future Libreboot, and it is expected that GNU Boot will have been dead for years.
1625 future Libreboot, and it is expected that GNU will have long given up the ghost.
1618 1626 Canoeboot will still be maintained regularly. That is the dream, and it is my Canoeboot will still be maintained regularly. That is the dream, and it is my
1619 1627 wish that this dream be fully realised. It shall be done. wish that this dream be fully realised. It shall be done.
1628
1629 I'm not allowed to win, but I will.
Hints:
Before first commit, do not forget to setup your git environment:
git config --global user.name "your_name_here"
git config --global user.email "your@email_here"

Clone this repository using HTTP(S):
git clone https://rocketgit.com/user/libreboot/lbwww

Clone this repository using ssh (do not forget to upload a key first):
git clone ssh://rocketgit@ssh.rocketgit.com/user/libreboot/lbwww

Clone this repository using git:
git clone git://git.rocketgit.com/user/libreboot/lbwww

You are allowed to anonymously push to this repository.
This means that your pushed commits will automatically be transformed into a merge request:
... clone the repository ...
... make some changes and some commits ...
git push origin main