Re: Fwd: Should Canoeboot become GNU Canoeboot?
Le lundi 13 mai 2024 à 17:58 +0100, Leah Rowe via libreplanet-discuss a écrit : > I actually submitted extensive patches to gnuboot in January 2024: > > https://lists.gnu.org/archive/html/gnuboot-patches/2024-01/index.html > > https://web.archive.org/web/20240511074211/https://lists.gnu.org/archive/html/gnuboot-patches/2024-01/index.html > > The patches were never reviewed, let alone merged, but they: Btw, this is untrue. They have been reviewed, and some rejected, and some applied. > > My patches fixed all of the fundamental issues with GNU Boot, without > rewriting the build system; they use an older version of the Libreboot > build system, prior to my re-write of the latter half of 2023 (my > re-write makes the build system much smaller and more efficient. These changes were not necessary or needed since we're reworking the build system to use GNU Guix instead. > > All of the above improvements *and much more* is in Canoeboot. In terms > of development, Canoeboot is about 2 years ahead of GNU Boot; Canoeboot > has since far surpassed the improvements sent to GNU Boot in January, so > even if they did merge them now, they'd still be behind. And ? What's the point ? We're talking about firmware, the less it does sometimes, the better. We're not trying to compete on functionnality but we think for long term maintainance and integrating GNU Guix and repairing RAM init on D16 for example is much more efficient for us than supporting a lot of boards with a lot of functionalities. > > I may be missing a thing or two, above, but one thing I'm not missing is > my strong and stable commitment to the free software movement, even when > I'm dealing with hostile project maintainers who won't even consider my > patches. They have been considered and some applied, please stop trying to lie about verifiable facts... Happy hacking, anyway. signature.asc Description: This is a digitally signed message part ___ libreplanet-discuss mailing list libreplanet-discuss@libreplanet.org https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
Re: Should Canoeboot become GNU Canoeboot?
On Mon, May 13, 2024 at 9:04 AM Andy Tai <[1]a...@atai.org> wrote: why not just call it GNU Libreboot. The Libreboot name is well known. Suggestion: Accept Libreboot as GNU. Leave GNU Boot alone. If that project is dead, let it die. Do not force its developers to do anything one way or another. The developer's of GNU Boot (in conjunction with GNU) should decide the future of their own package. Attempts to do otherwise might find Canoeboot paddling upstream! :-) As Andy suggested, why not "GNU Libreboot"? Happy Hacking Adrienne -- Freedom - no pane, all gaiGN! References: 1. GNU C-Graph: [2]http://www.gnu.org/software/c-graph 2. Code Art Now: [3]http://codeartnow.com 3. Abertheid Campaign: [4]http://www.abertheid.info/icc/pre-indictment-brief-05. 10.2006.pdf 4. Follow me on Twitter: [5]@AdrienneGT [6]@GNUcgraph 5. Let's Link Up: [7]https://www.linkedin.com/in/adriennegt/ 6. Knees On My Neck: [8]https://twitter.com/AdrienneGT/status/1288648018783277068 7. Rise Up for Richard Stallman: [9]https://www.stallmansupport.org References 1. mailto:a...@atai.org 2. http://www.gnu.org/software/c-graph 3. http://codeartnow.com/ 4. http://www.abertheid.info/icc/pre-indictment-brief-05.10.2006.pdf 5. http://twitter.com/adriennegt 6. http://twitter.com/GNUcgraph 7. https://www.linkedin.com/in/adriennegt/ 8. https://twitter.com/AdrienneGT/status/1288648018783277068 9. https://www.stallmansupport.org/ ___ libreplanet-discuss mailing list libreplanet-discuss@libreplanet.org https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
Re: Fwd: Should Canoeboot become GNU Canoeboot?
I actually submitted extensive patches to gnuboot in January 2024:
[1]https://lists.gnu.org/archive/html/gnuboot-patches/2024-01/index.htm
l
[2]https://web.archive.org/web/20240511074211/https://lists.gnu.org/arc
hive/html/gnuboot-patches/2024-01/index.html
The patches were never reviewed, let alone merged, but they:
* Replace "Libreboot" with "GNU Boot" in several places on the
documentation (**THIS IS THE ONLY PATCH THEY MERGED**)
* Fix major build issues, allowing GNU Boot to build on modern distros
(GNU Boot only builds on Trisquel 10, my patches make it build on 12.
also Gentoo-libre and Arch/Parabola)
* Add Dell Latitude E6400 support
* Fix hang in GRUB caused when there is a stuck key, by disabling the
"Unknown key" spew message
* ESP and btrfs subvol support in grub.cfg
* Fixes building KGPE-D16 on newer distros, by skipping GNAT which
isn't needed
* Add gru_bob support (rk3399 chromebooks, with free EC and *no*
microcode) - ditto gru_kevin
* Keyboard fix for GRUB: force it to use scancode set 2 translated,
instead of untranslated set 2 to work around buggy ECs such as Dell
Latitude E6400
* Avoid spewing the Unknown prefix message in GRUB
* Adds the dell-flash-unlock tool from Nicholas Chin, allowing internal
flashing from factory BIOS to GNU Boot, on the E6400
* cache cbfstool/ifdtool builds to speed up build time
* better caching of coreboot rom images during build, to speed up build
time
* Prevent future GRUB build errors by disabling -Werror
* Support for *building* U-Boot as a coreboot payload, on gru bob/kevin
chromebooks (GNU Boot only archives it, doesn't build it)
A second patch set that I sent does the above, and also:
* Updates GRUB, coreboot and SeaBIOS to newer revisions from late 2023
(GNU Boot uses late 2021 revisions)
* Adds Argon2 KDF support, for booting from LUKS2-encrypted /boot (GNU
Boot can't boot from encrypted LUKS2 /boot without this patch)
* Reduced the number of modules in GRUB to only those needed, saving
100KB of space in flash
* Update memtest86+ to v6.x instead of 5.x
I sent all of these patches to GNU Boot while bored, and it only took
me 1 day to implement all of them, re-using what I had done in
Canoeboot months beforehand
My patches fixed all of the fundamental issues with GNU Boot, without
rewriting the build system; they use an older version of the Libreboot
build system, prior to my re-write of the latter half of 2023 (my
re-write makes the build system much smaller and more efficient.
All of the above improvements *and much more* is in Canoeboot. In terms
of development, Canoeboot is about 2 years ahead of GNU Boot; Canoeboot
has since far surpassed the improvements sent to GNU Boot in January,
so even if they did merge them now, they'd still be behind.
I may be missing a thing or two, above, but one thing I'm not missing
is my strong and stable commitment to the free software movement, even
when I'm dealing with hostile project maintainers who won't even
consider my patches.
This is why I will no longer assist the GNU Boot project. Because I
tried to help them; and this wasn't my first attempt to help, either.
Also: Canoeboot has since added more GRUB improvements, such as a
native xHCI (USB 3.0) driver.
On 12/05/2024 17:23, Leah Rowe wrote:
[3]https://canoeboot.org/news/gnu.html
Discussion welcome
Forwarded Message
Subject: Should Canoeboot become GNU Canoeboot?
Date: Sun, 12 May 2024 15:50:42 +0100
From: Leah Rowe [4]
To: [5]gnue...@gnu.org
CC: [6]ksiew...@fsf.org, [7]z...@fsf.org, Mike Gerwitz [8],
[9]si...@josefsson.org, [10]christ...@grothoff.org,
[11]gnu-advis...@gnu.org, [12]r...@gnu.org, [13]b...@proulx.com
Hi
This is sent to GNU Eval team, but CC'd to others. My main recipient is the GNU
Eval team.
I want GNU Canoeboot. This is my official contact with GNU, as the lead develope
r and founder of the Canoeboot project, a fully free coreboot distro based on Li
breboot.
Canoeboot has recently removed all opposition to the FSF and decided to staunchl
y promote it instead, in addition to FSDG. This is part of a general desire I've
had since the start of the year, to seek reconcilliation with the FSF and GNU p
roject, after the drama that ensued first with libreboot.org vs libreboot.at, an
d then libreboot.org vs GNU Boot.
This change is permanent, whether GNU accepts my proposal today; even if Canoebo
ot does not become GNU Canoeboot, it will continue to operate as it does now. I
recently did a release which is staunchly pro-FSF. I've done this, precisely bec
ause GNU Boot is no longer competition to Canoeboot in any way; GNU Boot seems t
o have stalled, so Canoeboot has, with this moved, effectively replaced it. I do
n't say this as an attack, but it is a fact that GNU Boot has, as I write this,
not submitted
Re: Should Canoeboot become GNU Canoeboot?
My apology. Sorry I was just referencing the first message. If both projects are going well, let them both keep going. For history reasons if the two projects can or cannot combine, let them be. Code can still flow between them as the code is free software. On Mon, May 13, 2024 at 7:34 AM Adrien 'neox' Bourmault wrote: > > I wonder why you'd say our project is dead, it's a bit harsh given the > activity on the patch list, on the repository, in the living room, > and given the fact that I've been working full-time on the project at > the moment (notably to make the D16 RAM initialization more reliable) > since March and at least until August. GNUtoo is working on integrating > Guix. > > > ___ libreplanet-discuss mailing list libreplanet-discuss@libreplanet.org https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
Re: Should Canoeboot become GNU Canoeboot?
Le dimanche 12 mai 2024 à 15:10 -0700, Andy Tai a écrit : > why not just call it GNU Libreboot. The Libreboot name is well known. > Suggestion: Accept Libreboot as GNU. Leave GNU Boot alone. If that > project is dead, let it die. Do not force its developers to do > anything one way or another. > > ___ > libreplanet-discuss mailing list > libreplanet-discuss@libreplanet.org > https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss I wonder why you'd say our project is dead, it's a bit harsh given the activity on the patch list, on the repository, in the living room, and given the fact that I've been working full-time on the project at the moment (notably to make the D16 RAM initialization more reliable) since March and at least until August. GNUtoo is working on integrating Guix. We don't have much time and we're short of people to take care of communication, so we can't say what we're doing very often, but we're planning a little newsletter soon. Anybody on our IRC channel knows what we do, though. Anyway, happy hacking! -- Adrien Bourmault Maintainer, GNU Boot project Associate member, Free Software Foundation GPG : 9AA8CDA0DC9C0604D26AE4A72974E1D5F25DFCC8 signature.asc Description: This is a digitally signed message part ___ libreplanet-discuss mailing list libreplanet-discuss@libreplanet.org https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
Re: Should Canoeboot become GNU Canoeboot?
I agree LibreBoot makes sense as a name, and makes it clear what it does. One of the issues with Free (and some open source) software the name has nothing to do with what the program does, hence people can sometimes never remember the name of software. Makes it more of a barrier to wider adoption Paul On 12/05/2024 23:10, Andy Tai wrote: why not just call it GNU Libreboot. The Libreboot name is well known. Suggestion: Accept Libreboot as GNU. Leave GNU Boot alone. If that project is dead, let it die. Do not force its developers to do anything one way or another. ___th libreplanet-discuss mailing list libreplanet-discuss@libreplanet.org https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss ___ libreplanet-discuss mailing list libreplanet-discuss@libreplanet.org https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
Re: Should Canoeboot become GNU Canoeboot?
why not just call it GNU Libreboot. The Libreboot name is well known. Suggestion: Accept Libreboot as GNU. Leave GNU Boot alone. If that project is dead, let it die. Do not force its developers to do anything one way or another. ___ libreplanet-discuss mailing list libreplanet-discuss@libreplanet.org https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
