this post was submitted on 12 Nov 2023
675 points (94.6% liked)

linuxmemes

21019 readers
329 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    [email protected]
    [email protected]
    [email protected]
    675
    Screw init wars, real OGs discriminate based on DE (lemmy.ml)
    submitted 11 months ago by [email protected] to c/[email protected]
    123 comments fedilink hide all child comments
     

    I use plasma, BTW

    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 6 points 11 months ago (1 children)

    At the level I care about, which is "I want this daemon to start when I boot up the computer", systemd is much better. I can write a ~5 line unit file that will do exactly that, and I'll be done.

    With init, I needed to copy-paste a 50-line shell script that I don't really understand except that a lot of it seemed to be concerned with pid files. Honestly, I fail to see how that's better...

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

    Yeah, that does sound better. What are the arguments for init?

    [–] [email protected] 4 points 11 months ago (2 children)

    The only arguments against I have seen so for is systemd does a lot more than just handing system startup (systemd-resolved is one such example) and files that was previously stored as text now require systemd's own tool to read (journalctl?).

    So not the actual startup function, just everything else.

    [–] [email protected] 5 points 11 months ago* (last edited 11 months ago)

    Mmm I have a general dislike of systemd because it doesn't adhere to the "do one thing and do it well" approach of traditional Unix systems.

    It's a big old opaque blob of software components that work nicely together but don't play well with others, basically.

    Edit: but it solved a particular set of problems in serverspace and it's bled over to the consumer Linux side of things and generally I'm ok with it if it simplifies things for people. I just don't want a monoculture to spring up and take root across all of Linux as monocultures aren't great for innovation or security.

    [–] [email protected] 3 points 11 months ago* (last edited 11 months ago) (1 children)

    Based on the video someone posted, it's not very portable either.

    I feel that little part of my brain that wants to add yet another standard itching. Easily starting something at boot is good, but I don't see why that has to come with loss of modularity.

    [–] [email protected] 1 points 11 months ago

    Afaik they don't care about being portable to instead focus as much as possible on being fast and whatever