Linux

59278 readers

698 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

nooter692@lemmy.ml

AgreeableLandscape@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Different installation methods and system stability (lemmy.ml)

submitted 1 week ago by Stopwatch1986@lemmy.ml to c/linux@lemmy.ml

21 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

[–] Stopwatch1986@lemmy.ml 1 points 4 days ago (1 children)

I share your concerns about trust. With flatpaks we can still read the source and commits, but not many will or can do this every time they install and update software anyway. In this sense, we have little choice but to trust the verified developer and the community, who may of course be compromised too, regardless of distribution method. I suppose with flatpaks we have to check permissions and make them as restrictive as possible.

[–] stupid_asshole69@hexbear.net 1 points 4 days ago

I’m pretty sure flatpaks don’t require that the source of any of the weird shit in them be open.

It’s also probably worth it not to hold open source up above closed source in terms of security since neither of us is conducting a meticulous audit of the stuff we run.

Regardless, my point was to figure out what works for you. When I ran Slackware I got comfortable doing manual dependency management so breaking Debian by doing a bunch of manual installs is fine for me.

If you feel most comfortable with using flatpaks or appimages then use those.