Linux

48044 readers

784 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

[email protected]

142

Niche Distro Users: Why? (lemmy.ml)

submitted 2 months ago by [email protected] to c/[email protected]

92 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

[–] [email protected] 17 points 2 months ago (1 children)

Also on modern firebreathers.

I like runit better than systemd, the packages are current, and it has most of what I want in the main repos.

I also found the documentation excellent in thst it's a cohesive list of real-world topics rather than a 500-km-deep wiki or forum archive.

I should try a modern Slackware one day. I loved it back before I had broadband and just ordered a burned CD for each new release, but I should try following -current and the Slackbuilds stuff.

[–] [email protected] 6 points 2 months ago* (last edited 2 months ago)

Slackbuilds are really nice. Sbopkg lets you download queue files for each program, then automatically install necessary dependencies in the correct order, no matter if they're available as packages or from source. Unfortunately, Slackware is so bare-bones out of the box that there are still pitfalls. For example, LibreOffice depends on avahi. And to successfully install that, you first need to create an avahi user and group, then install avahi, then write an init script that starts the avahi daemon and another one to stop it on shutdown.
-Current is much too active for my personal taste. I run Slackware because I'm a lazy Slacker.
The laziest approach to Slacking today is to install the default full install, then do:

wget https://github.com/sbopkg/sbopkg/releases/download/0.38.2/sbopkg-0.38.2-noarch-1_wsr.tgz    #Download the Slackbuilds helper Sbopkg  
slackpkg install sbopkg-0.38.2-noarch-1_wsr.tgz                                                  #Install it  
sbopkg -r                                                                                        #Sync its local repository to Slackbuilds   
sqg -a                                                                                           #Build queue files (dependency info) for the repository
sbopkg -i flatpak                                                                                #Install Flatpak and its dependencies  
flatpak remote-add --user flathub https://dl.flathub.org/repo/flathub.flatpakrepo                #Add the Flathub repo