Linux

65393 readers

1022 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 7 years ago

MODERATORS

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

187

Reclaiming the desktop: Why I’m still on Linux in 2026 (the.unknown-universe.co.uk)

submitted 1 month ago by TheIPW@lemmy.ml to c/linux@lemmy.ml

48 comments fedilink hide all child comments

I’ve been using Linux for years, but as the proprietary alternatives get more aggressive with telemetry and adverts, I wanted to document the choices that actually keep my desktop predictable.

This isn't a manual, but a practical overview of my setup. From why I’ve settled on CachyOS and KDE Plasma for my main rig, to the reality of dealing with proprietary software and app compatibility in 2026. It’s just an honest look at the transition and why I’m done with the corporate defaults.

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

[–] dan@upvote.au 1 points 4 weeks ago

Yes, unstructured. Every script is its own special snowflake that does things a bit differently.

There's no guarantee of the verbs that the script implements. start, stop and restart are common, but the implementation is up to each individual script. I'm most familiar with Debian where some service (but not all) implemented it with start-stop-daemon, but other distros and OSes handled it differently.

Basic, commonly needed functionality, like restarting a crashed service after waiting for some delay, need to be implemented per app.

When sysvinit was widespread, there was a reason a lot of people used systems line supervisord to deploy services, rather than dealing with sysvinit scripts. It was a pain.

Systemd units were a logical progression from supervisord services.