this post was submitted on 25 Apr 2026
89 points (94.1% liked)

Linux

65201 readers
682 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 7 years ago
MODERATORS
top 50 comments
sorted by: hot top controversial new old
[–] chrash0@lemmy.world 39 points 2 weeks ago (2 children)

there’s a world of options. this is an LTS distro. use Arch or Nix or whatever if you want the latest packages. i actually switched to NixOS because the CUDA drivers were too new on Arch, and i wanted a better way to pin versions.

or i dunno keep publicly complaining about it until someone does the work for you

[–] grue@lemmy.world 14 points 2 weeks ago (2 children)

I mean, even in an LTS distro, it sure would be nice if the packages were reasonably up-to-date on the day the version was released.

[–] chrash0@lemmy.world 11 points 2 weeks ago (1 children)

i guess it would be nice, but packages being a few months out of date is pretty normal for Ubuntu, in my experience. i’m not sure what their testing process is like, but part of using something like Ubuntu is stability guarantees. if they felt like the couldn’t do that for newer versions for whatever reason (resource constraints, lack of downstream interest from stakeholders, etc) they’re not necessarily obligated to.

[–] adarza@lemmy.ca 11 points 2 weeks ago

2 months. lts or not, ubuntu's freeze date is and has historically been about two months before release.

if the 2 year cycle between lts is too long for someone, they don't have to stay on that ride.

[–] non_burglar@lemmy.world 5 points 2 weeks ago

It would be nice, but the time it takes to do the work of validating package versions for LTS candidacy is either limited or not free, so this is the acceptable compromise.

[–] caseyweederman@lemmy.ca 5 points 2 weeks ago (2 children)
[–] Strit@lemmy.linuxuserspace.show 5 points 2 weeks ago

But its software freeze was a couple of months ago.

[–] chrash0@lemmy.world 3 points 2 weeks ago (7 children)

it’s Ubuntu dawg. you get what you pay for.

[–] cravl@slrpnk.net 2 points 2 weeks ago (1 children)

…and you pay more for other distros?

[–] chrash0@lemmy.world 11 points 2 weeks ago (1 children)

just a silly turn of phrase meaning: you should know that this is what you signed up for

[–] cravl@slrpnk.net 2 points 1 week ago

Yeah I know, just making a terrible attempt at humor. 😅

[–] melroy@kbin.melroy.org 1 points 2 weeks ago

I didn't pay? Even if I did you got the same result, 🤣

load more comments (5 replies)
[–] Lemmchen@feddit.org 17 points 2 weeks ago (1 children)

But It's Months Out-Of-Date

So, par for the course for Ubuntu, no?

[–] Wolf314159@startrek.website 4 points 2 weeks ago

More like by design for an LTS release.

[–] AndrewZabar@lemmy.world 13 points 2 weeks ago (1 children)

I don’t think I know what rocm is 🤪

load more comments (1 replies)
[–] savvywolf@pawb.social 11 points 2 weeks ago (1 children)

Especially with the newer ROCm 7.2.x releases improving hardware support and other improvements. Especially with the rate of improvements to ROCm recently, it's unfortunate to see ROCm 7.1 shipped in the Ubuntu 26.04 archive.

Improvements!

But yeah, 3 months out of date for software that isn't security critical is fine. Probably just hit the feature freeze at a bad time. It still presumably works well enough for most people.

[–] Bloefz@lemmy.world 9 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

3 months isn't bad though. Especially since it's going to be locked out of changes so in 5 years it will be 5 years and 3 months out of date. The bigger problem with rocm is that they cut off older cards way too soon.

I bought a radeon pro vii brand new from a shop (granted it was a runout sale) and it was already cut off. It still works but not supported.

AMD can't keep complaining everyone focuses on CUDA when they don't even bother to support their own product. It supports very few cards and they get cut off way too soon.

Nvidia supports even midrange consumer cards and they keep supporting them a long time.

[–] kunaltyagi@programming.dev 1 points 2 weeks ago

Support for older cards is getting more common. Some of them are working but not officially supported but I've seen more cards entering support than leaving

[–] doodoo_wizard@lemmy.ml 8 points 2 weeks ago

Rocmuh balls

[–] stupidcasey@lemmy.world 4 points 2 weeks ago

Why is this surprising? I would be more surprised if it didn't.

[–] middlemanSI@lemmy.world 3 points 2 weeks ago (1 children)

Being old != bad. Some software is not critical in terms of cyber security. You have to assess the use case. Feels like you're screaming wolf, without knowing the package.

[–] Lemmchen@feddit.org 5 points 2 weeks ago

For rocm, old is bad.

[–] Stupendous@lemmy.world 2 points 2 weeks ago

Ehh. 7.1 isnt that old. If they don't make any newer available until 28.04, then this'll just be a major baseline. It'll nice regardless just if it leads to more rocm support. The package and maintainers are in place for this to keep going every 6 months

[–] WormFood@lemmy.world 1 points 2 weeks ago

Rocm is the singular worst piece of software I've ever used

[–] Kanda@reddthat.com 1 points 2 weeks ago

Just build it from source, then

The most success I had at getting rocm working was just using containers.

[–] umbrella@lemmy.ml 1 points 2 weeks ago (2 children)

this is why we are moving to packaging like flatpak.

[–] thingsiplay@lemmy.ml 5 points 2 weeks ago (1 children)

Or this is why we are moving to a rolling-release model.

[–] IEatDaFeesh@lemmy.world 1 points 2 weeks ago

Or this is why I'm rolling over.

[–] ohshit604@sh.itjust.works 5 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Yeah, would much rather a package designed for my distro than a flatpak.

I recall a time where the native package on my distro wasn’t working at all, I think this was when I was using discord and tried to use Vencord on Debian 12, so I tried the flatpak version and again it did not work. I was between a rock and a hard place, do I troubleshoot what is essentially a containerized/sandboxed application or try to figure out what’s going on my host machine.

I chose the latter and eventually got it working, but now I don’t use discord so waste of my time regardless.

[–] umbrella@lemmy.ml 2 points 2 weeks ago (1 children)

if properly implemented, it shouldn't matter. much the same way android apks works in pretty much any android "distro", despite a few snags on the more aggressive manufacturer roms.

[–] excel@lemming.megumin.org 1 points 2 weeks ago (1 children)

No, Flatpak limitations literally make it impossible to get all Discord features working. It’s not a problem with the config, it’s a design flaw of Flatpak itself.

[–] umbrella@lemmy.ml 1 points 2 weeks ago* (last edited 2 weeks ago)

then it's not properly implemented yet, on either side.

i'm curious as to which ones though, what can't you do? i have everything working.

load more comments
view more: next ›