Linux

48356 readers

663 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 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r

140

Niche Distro Users: Why? (lemmy.ml)

submitted 3 months ago by BaumGeist@lemmy.ml to c/linux@lemmy.ml

89 comments fedilink hide all child comments

I occasionally see love for niche small distros, instead of the major ones...

And it just seems to me like there's more hurdles than help when it comes to adopting an OS whose users number in the hundreds or dozens. I can understand trying one for fun in a VM, but I prefer sticking to the bigger distros for my daily drivers since the they'll support more software and not be reliant on upstream sources, and any bugs or other issues are more likely to be documented abd have workarounds/fixes.

So: What distro do you daily drive and why? What drove you to choose it?

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

[–] cizra@lemm.ee 6 points 3 months ago (1 children)

What's the Slackware way of managing package dependencies, then?

[–] superkret@feddit.org 7 points 3 months ago (3 children)

For Slackware itself, you install all available software up front. That way, all dependencies are resolved.
You then just hide the stuff you don't need from your DE using its menu editor, or ignore it.
During an update, the package manager updates all installed packages, installs all packages that were added to the repo and removes all packages that are obsolete.

For additional software, there is a semi-official repo that's very similar to Arch's AUR.
And like the AUR, it offers several helper scripts and additional package managers that do dependency resolution.
Or you use Flatpaks.

[–] 0x0@programming.dev 9 points 3 months ago (1 children)

you install all available software up front.

That's unnecessary and inefficient, you can install a small subset and go from there.

[–] superkret@feddit.org 4 points 3 months ago* (last edited 3 months ago)

Until you start installing stuff from Slackpackages, whose dependency info assumes everything in the default install is there and doesn't need mentioning.
Or new packages are added to the repo which depend on something you didn't install.

[–] tetris11@lemmy.ml 3 points 3 months ago (1 children)

How long do software updates take then, if you're updating the entire software stack? I can imagine the answer being anywhere from "hours" to "same as the incremental software updates on other distros"

[–] superkret@feddit.org 7 points 3 months ago* (last edited 3 months ago)

There are very few updates. It's more stable than Debian. And the repo isn't huge, maybe twice the size of other distros default installed size.

[–] cizra@lemm.ee 1 points 3 months ago

Cool, thanks. Didn't realize you can use this neat trick :)