kernel forks
The intent and the pragmatic conditions
What we committed to do and its practical applications
After the late October 2024 removal of developers/maintainers of the linux code by the heads of the project on the basis of the natinality and origin of their employers (not in terms of ability, character, and quality of contributions) and the nationalist racist remarks that accompanied the removal (some nonsense about baseless history of Finland ) we had decided to halt following development of the kernel, and just rebuild the last editions of 5.10/5.15/6.6 .. of the time, we are now seeing this becoming harder to do for the following reasons.
1 It is evident through interaction with users that this intent is not shared by the user base, which can also be perceived positively as users in order to get the latest of kernel development were forced to build their own. If they make this leap of building a kernel for their system then they can build everything we offer, which was a very encouraged objective since day one. So we seem compelled to admit that our criteria in this manner are not widely shared, not in practical terms anyhow.
2 We anticipated that there would have been a fork of the kernel critically adopting development of current and LTS kernels without admitting new corporate product code. There was one initiative CINUX early on that froze in time and received no commits. We haven't been able to find any other projects.
3 As we were traumatized to discover gcc15 rebasing its libC from 17 to 23 was unable to compile the kernels as they were. Many other software have the same problem, and arch either uses a 2nd batch of gcc branded gcc14 (huge) or exporting a build flag for gcc to use 11 or 17 as its base to compile, but doing so sufficiently slower and less efficiently than gcc 14. Eventually the kernels that are current and marked as LTS will receive changes so they can comply with 23 standards and could compile with gcc15 without any hacky measures such as those used by arch lately.
4 We have moved back to gcc 14 but in the latest stable edition released late May (14.3.0) and we have been happily building since using this new tool chain. We needed to see whether kernels would compile and build as they did in the past, and we were successful. So we built the latest edition of linux 5.15.184
5 So for now we violated our declaration of boycotting the LinFo/US-SD tendencies and racism to provide an alternative. Since 5.10 has had much longer development we will keep rebuilding that late October 2024 edition for now. With linux 6.6 we are ambivolent, and next release may see a build. Since kernels built before 4/29/25 are kept in the frozen 429 project repository, this is becoming enormous to keep 6 kernels and headers in our "free" repository. The idea behind 429 was to provide an alternative to Arch's gcc15 move, which since our re-edition of gcc14 it has lost its purpose.
6 Enjoy trials of linux{,-headers}-5.15.184-01 being uploaded as we speak
truly free and open software can and should see no divisions among humans
those that see race gender ethnicity religion divisions among free-open software communities are an offense to Free and Open principles themselves
True Free and True Open development can not succumb to state and war mongers' dictation of us/them. Corporations and States will always be them to us
cinux/README.md at master · Cqinux/cinux
cqwrteur's fork of Linux kernel, rename it to Cinux - Cqinux/cinuxGitHub
Iri Yan
in reply to joborun linux • • •For those who are concerned on that move back on Oct 2024 stick to the "safe" editions as listed before here and in an article at sysdfree.wordpress.com
For those who think "development" of the latest kernel is of their interest get that binary.
All lts kernels have a tentrative death day on Dec 2026, except for 6.1 getting one extra year. 5.4 is out this December.
If you think things will continue to roll as they have in the past place your bet. All indications show that something dramatic is cooking under the drama we witness from kernel to gnu/gcc to X, to wayland. Someone is shaking the pan underneath and heads are rolling due to those moves.
Maybe joborun appeared just in the right time of getting one clean last healthy system before it all turns to crap. I'd keep copies of images and repos, you never know when we are going to need older/cleaner ones when crap gets revealed.
And that's my 2c
treu
in reply to joborun linux • • •joborun linux
in reply to joborun linux • • •I think it is more of a matter of consciousness than a practical/technical issue. Just like strict FOSS/libre sw and not-so-free software. In debian in order to use non-free firmware you must enable the non-free repositories, and if that is the only way to make your machine work, who is there to judge you?
If you say I'd rather not use wifi than use non-free software, all power to you.
But some how and someone needs to speak up about what is going on, and the loudest voice is the collective voice. Hiding behind some legality of "Open Free" software, abiding by "war-time" passive-aggressive doctrine of the type "whoever does business with them is not our friend and our friends better not be working together with our enemies", then dumping long term "co-workers" on the basis of their national origin or that of their employer, is way beyond what I would perceive as free. It is abiding by fascism and doing so unilaterally as the sole dictator of the project.
Remember one of the 12 dumped wasn't even removed from the list, he quit in protest of that happened.
Also those comments about history and relations between Finns and Russians are totally biased and a perverse way of looking at history. This is clearly neo-nazi rhetoric based on lies and propaganda. If he had clarified his world views 20 some years ago I don't think his work and fame would have gotten this far. So he speaks based on the deception of upholding Open & Free values and principles, which he took a crap on!