Linux

48102 readers

1120 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@lemmy.nz

-81

Systemd is far from being perfect (discuss.online)

submitted 10 months ago by Unsafe@discuss.online to c/linux@lemmy.ml

40 comments fedilink hide all child comments

Systemd-init has a larger attack surface compared to runit, openrc, or sysVinit.
Systemd-logind relies on systemd, so we need to adapt it for non-systemD distributions to ensure compatibility with certain applications like GNOME.
Udev also depends on systemd.
SystemD is specific to Linux, which makes porting software to *BSD even more challenging. It's uncertain what the future holds, and there may be circumstances where Linux becomes unusable for you (e.g., compatibility issues with your laptop). Having a good alternative that doesn't require relearning everything is generally beneficial.
SystemD-based distributions often come with more than just "systemd-init." They include additional components like logind, resolved, networkd, systemd-timers, etc. However, many people still prefer using the alternatives they were accustomed to before systemd became popular, such as dhcpcd and cron. Consequently, having both sets of tools installed can increase the attack surface.

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

[–] SnotFlickerman@lemmy.blahaj.zone 12 points 10 months ago* (last edited 10 months ago) (1 children)

There is no such thing as a perfect OS where there is no attack surface or dependencies.

OP, you're absolutely right about systemd, but similar critiques can be given to nearly any underlying OS service. (Also, I'm sure this is in response to other posts praising systemd)

I'm just starting to feel like it's a little silly to even have a conversation one way or another about these things instead of just accepting that people could and should use the tools that fit their use case scenario the best.

For most people, the stuff they gain from things (for example, systemd) outweighs the downsides.

We don't make such choices in a vacuum. It's important to know limitations, attack surfaces, and dependencies, but it's important mostly for being able to choose the right GNU tools for yourself.

Nobody can tell you what the best OS/Kernel/GNU tool is to use, because that's always deeply dependent on your specific needs for the task at hand. While PCs are "general purpose computing," they all can have wildly different hardware and software hiccups, and only you can use your own knowledge to choose the best tools for your use-case.

[–] Unsafe@discuss.online -5 points 10 months ago

What an average Mint user gains from systemd? A bit slower boot time? A bit more ram used? 50mb heavier system updates? What problems systemd solves? I use systemd, runit and openrc on different machines and I don't face any significant problems.