- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Very interesting and understandable explanations of low level architecture and filesystems, namespaces, userspace, kernel functions, drivers etc.
Highly recommend!
Very interesting and understandable explanations of low level architecture and filesystems, namespaces, userspace, kernel functions, drivers etc.
Highly recommend!
It would at least protect the core parts of the kernel itself
Sure but protect from what? Apple, Sony and Microsoft can just use BSD or any other proprietary kernel. Nobody will try to create the “new proprietary Linux” out of it because getting OS market share is hard even for an Open Source standard like Linux, let alone for some proprietary crap.
A potential issue is someone like Qualcom who makes their own proprietary fork which works on their hardware only. So instead of digging through the tens of thousand lines of code which Qualcom publishes for their out of tree Linux kernels, you can only reverse engineer. But again we are talking about a microkernel so most of these lines of code would be proprietary regardless. At least we save time of these crazy developers who try to bring out of tree stuff into mainline.
It stops parts of Linux becoming proprietary, and becoming the dominant version users interact with. Comparisons with other kernels are irrelevant
Comparisons with other kernels is imo relevant. Protecting software that has many alternatives from becoming proprietary is nice but not really important when the potential software vendor can just choose a different but equivalent project. It would not really matter if people interacted with this proprietary fork of RedoxOS or BSD, they would get screwed either way.
Note: the original comment was “GPL or bust”. imo GPL is nice but in this case it’s a minor thing