Linux

59207 readers

410 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

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

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

founded 6 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Different installation methods and system stability (lemmy.ml)

submitted 3 days ago by Stopwatch1986@lemmy.ml to c/linux@lemmy.ml

20 comments fedilink hide all child comments

I recently moved my work machine from Windows to Linux and chose Debian Trixie + KDE Plasma for the stability. The advice is that if stability is your priority, you should try to avoid breaking Debian. I understand that adding third-party sources can cause dependencies conflicts, and must be avoided at all costs. I also understand that Flatpaks, AppImages, Snaps, and Docker/Podman images are safe because they don't interfere with the system dependencies. So far, so good. What I don't understand is what happens with other ways of installing software (eg .deb, tarballs).

I know it's a contentious subject but if stability is the priority, how would you rank different methods? I may be wrong but my take is:

Debian repository > Flatpak > Appimage > Docker/Podman > Snap > tarball

To be avoided: .deb for Debian > .deb for Ubuntu > PPAs

Eg Viber is available as an official AppImage (with certain bugs), unofficial flatpak (with other bugs), and an official .deb for Ubuntu (which is probably a bad idea for Debian anyway). Viber support told me they don't support my OS.

you are viewing a single comment's thread
view the rest of the comments

[–] non_burglar@lemmy.world 5 points 3 days ago (1 children)

How were dist upgrades going bad?

[–] HelloRoot@lemy.lol 2 points 3 days ago* (last edited 3 days ago) (2 children)

I don't have a good memory, because it was about 15-10 years ago.

I remember one time where the dist upgrade finished, but after a reboot most apps would crash with core dumps and I wasn't able to use apt for anything.

One time I did the dist upgrade too late and the repos were gone. It would have probably worked by manually pointing at the archive, but I was a newbie back then.

One time I had some ppa for work, that blocked the upgrade and I would have to completely remove it, but there was no version for the new release yet, even though I needed (also for work) a feature from some tool that was updated in the new release. So I was stuck between having one or the other but not both.

But like I said, it's all cloudy.

[–] eldavi@lemmy.ml 3 points 2 days ago

something like this happened to be too circa 2005 and it made me switch to debian; which stayed rocked solid until 2016 when the motherboard died.

[–] non_burglar@lemmy.world 3 points 3 days ago

Oh, yeah, I remember that time. Upgrading between major versions isn't perfect, but it has improved dramatically since about 2017 on both Ubuntu and Debian.

Debian has also just implemented apt v3, which adds many basic http/s quality-of-life improvements to package downloading and installing (like multithread, better config definitions, easier key mgmt, etc)

I don't know about Ubuntu because I moved from Ubuntu to debian 4 years ago for other reasons, but I'm sure they have aptv3 as well.