23
submitted 13 hours ago by nobody_1677@lemmy.world to c/linux@lemmy.ml

Highlights

  • Rust rewrite of GNU coreutils and sudo-rs
  • TPM-backed Full Disk Encryption now considered stable
  • More secure services (don't run as root if not needed, AppArmor profiles)
  • AppArmor prompting for snaps is still experiemental unfortunately
top 8 comments
sorted by: hot top controversial new old
[-] amaryllisfever@lemmychan.org 2 points 5 hours ago

Do they still lock security updates behind paywalls? 🤣

[-] GnuLinuxDude@lemmy.ml 12 points 12 hours ago

Not interested in an MIT-licensed coreutils. Thanks, but no thanks!

[-] nobody_1677@lemmy.world 4 points 12 hours ago

I can understand MIT being an issue in some cases. For example, VSCode is a proprietary fork of the MIT open-source Code. If Microsoft wanted, they could stop publishing the MIT open source version. Of course that code would still exist as MIT, but development would slow down without Microsoft.

But I don't see uutils being MIT as an issue. It's primary goal is to be compatible with GNU coreutils. You can't really rug pull a project with a goal like that. And permissively licensed utils have been around thanks to BSD and it's never been an issue. You don't see companies like Apple using proprietary forked versions as benefit. The "value" they add is higher up the tech stack with their own truly proprietary stuff or open stuff that encourages lock-in to its ecosystem, like Swift.

[-] GnuLinuxDude@lemmy.ml 5 points 9 hours ago

And permissively licensed utils have been around thanks to BSD and it’s never been an issue.

The distinction is that BSD coreutils are not attempting to be a drop-in 1:1 compatible replacement of GNU coreutils. The Rust coreutils has already accomplished this with its inclusion into Ubuntu 26.04.

If I wanted a permissively licensed system, I'd use BSD. I don't, so I primarily use Linux. I think citing a proprietary OS like macOS as a reason why permissively licensed coreutils are OK is kind of funny. It's easy to forget that before before the GPL there were many incompatible UNIX systems developed by different companies, and IMO the GPL has kept MIT and BSD-licensed projects "Honest", so-to-speak. Without the GPL to keep things in check, we'd be back to how things were in the 80s.

So what's next on the docket for Ubuntu? A permissively licensed libc?

[-] db2@lemmy.world 7 points 12 hours ago
[-] nobody_1677@lemmy.world 8 points 12 hours ago

Snap as a technology is so interesting and more versatile than other formats. It's just unfortunate that Canonical is in charge of the project, they've made some baffling decisions and continue to shoot themselves in the foot.

[-] umbrella@lemmy.ml 9 points 12 hours ago

no closed down walled garden will ever be interesting or versatile

[-] nobody_1677@lemmy.world 10 points 12 hours ago

That's part of what I mean. Snap could be so much more interesting and useful if not for Canonical doing stuff like only allowing one store and slacking on proper support for non-AppArmor distros.

One of the more bizarre experiences I've had is that a Canonical employee packaged a version of a Minecraft launcher. It was absolutely garbage, didn't even start. The first thing that comes to mind is that snap is just garbage. But for fun, I made my own package of it, and it just worked perfectly. Which just leaves me the question of why a Canonical employee who works on snap can't create a good snap package.

There's also the weird fact that Ubuntu dropped the ball with its core24 runtime. For some reason, Canonical's own snaps stuck to core22 up until this month. Like, why wouldn't they upgrade to their latest runtime? If there was an issue with it, why has it been broken for 2 years? Doesn't inspire trust.

this post was submitted on 10 Apr 2026
23 points (96.0% liked)

Linux

63789 readers
791 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 6 years ago
MODERATORS