this post was submitted on 24 Mar 2025
108 points (92.9% liked)

Linux

53000 readers
776 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

At first I was sceptical, but after a few thought, I came to the solution that, if uutils can do the same stuff, is/stays actively maintained and more secure/safe (like memory bugs), this is a good change.

What are your thoughts abouth this?

(page 2) 19 comments
sorted by: hot top controversial new old
[–] [email protected] 6 points 2 weeks ago (4 children)

I wonder whether Linux Mint will follow suit?

[–] [email protected] 5 points 2 weeks ago* (last edited 2 weeks ago)

As I recall Ubuntu will allow to switch uutils to coreutils. So it looks like Linux Mint will continue to use coreutils

[–] [email protected] 5 points 2 weeks ago

Likely not anytime soon as they tend to hold off latest features and prefer older (but maintained) LTS versions of just about everything. Also especially not if it turns out to be a bad idea; they explicitly build Mint without Snaps since their inclusion in the Ubuntu base.

load more comments (2 replies)
[–] [email protected] 30 points 2 weeks ago (2 children)

Time for Mecha-Stallman to declare war.

[–] [email protected] 17 points 2 weeks ago

The time has come to GNU-slash the enemies of freedom!

load more comments (1 replies)
[–] [email protected] 6 points 2 weeks ago (2 children)

So i hear that removing all the gnu stuff opens linux to be redistributed with a bew liesinse like mit. Which means its a little more closed iff a little more monitized.

Not knowledge enough on my own to know for sure. If someone with more knowledge could explain.

[–] [email protected] 19 points 2 weeks ago (2 children)

This is one of the old-time original arguments in the OSS community.

The crux of the matter is that the GNU licenses require that modifications be released back to the community. Other "more permissible" licenses like MIT do not.

So if you want to make a commercial version of X, and X is under a GPL, then any changes you make need to be released under the GPL. The idea being "I shared this code with the community with the intent that you can use it for free and modify it as you like, but you need to share back what you do." Also called "Share and share alike".

This defends against "embrace, extend, extinguish" tactics that companies like Microsoft has loved to do. They can't take your code, modify it for their own purposes and re-sell it possibly making a more popular version that is now proprietary.

load more comments (2 replies)
load more comments (1 replies)
[–] [email protected] 15 points 2 weeks ago (3 children)

I personally don't see the point.

[–] [email protected] 9 points 2 weeks ago (4 children)

I fear moving away from GPL that moving to Rust seems to bring, but Rust does fix real memory issues.

Take the recent rsync vulnerabilities for example.

https://www.cyberciti.biz/linux-news/cve-2024-12084-rsyn-security-urgent-update-needed-on-unix-bsd-systems/#more-2215

At least this one in a Rust implementation of rsync would have very likely been avoided:

CVE-2024-12085 – A flaw was found in the rsync daemon which could be triggered when rsync compares file checksums. This flaw allows an attacker to manipulate the checksum length (s2length) to cause a comparison between a checksum and uninitialized memory and leak one byte of uninitialized stack data at a time. Info Leak via uninitialized Stack contents defeats ASLR.

load more comments (4 replies)
[–] [email protected] 8 points 2 weeks ago (5 children)

Mainly memory safety; split (which is also used for other programs like sort) had a memory heap overflow issue last year to name one. The GNU Coreutils are well tested and very well written, the entire suite of programs has a CVE only once every few years from what I can see, but they do exist and most of those would be solved with a memory and type safe language.

That said, Rust also handles parallelism and concurrency much better than C ever could, though most of these programs don't really benefit from that or not much since they already handled this quite well, especially for C programs.

load more comments (5 replies)
[–] [email protected] 29 points 2 weeks ago (1 children)

See other comments: all these rewrites are not using the GPL but rather permissive licenses like MIT. Bye-bye FOSS (in those ecosystems).

[–] [email protected] 14 points 2 weeks ago (2 children)

I don't like them moving away from gpl but there were already plenty of non-gpl coreutils clones, so, i'm not sure how much it really matters as long as the linux kernel is still gpl.

[–] [email protected] 11 points 2 weeks ago* (last edited 2 weeks ago) (4 children)

Unlike the other alternative coreutils, uutils focuses on GNU compatibility. If you depend on GNUisms, uutils allow you to unGNU & unGPLv3+ your system.

load more comments (4 replies)
[–] [email protected] 10 points 2 weeks ago (1 children)
[–] [email protected] 4 points 2 weeks ago (1 children)
load more comments (1 replies)
[–] [email protected] 81 points 2 weeks ago (4 children)

the deGPLification of the Linux ecosystem ffs

[–] [email protected] 17 points 2 weeks ago

Kinda like a full 180° back to UNIX™.

[–] [email protected] 77 points 2 weeks ago (15 children)

I would love this news if it didn't move away from the GPL.

Mass move to MIT is just empowering enshittification by greedy companies.

load more comments (15 replies)
load more comments (2 replies)
load more comments
view more: ‹ prev next ›