this post was submitted on 26 Jun 2023
267 points (97.5% liked)

linuxmemes

21103 readers
1689 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
     
    top 23 comments
    sorted by: hot top controversial new old
    [–] [email protected] 7 points 1 year ago (2 children)

    "a popular init system"? It's the main init system now. Look at it. Systemd is the captain now.

    You'll have to learn it if you use any mainstream distro. Like at work. It is inevitable.

    [–] [email protected] 5 points 1 year ago (1 children)

    It makes my work so much easier than it could've.

    Imagine having to tweak sysvinit script at work.

    [–] [email protected] 2 points 1 year ago

    Yeah, nope I'll pass. Unit files for me please thank you.

    [–] [email protected] 3 points 1 year ago

    Yes, that's what 'popular' becomes.

    Note that it's often labeled as 'popular' and not 'good'.

    I'm sick of redhat's internal junk. It's just to sell courses anyway.

    [–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (2 children)

    If it was only an init system I'd be ok with it. But it isn't...

    [–] [email protected] 1 points 1 year ago

    You need to use its init system (systemd), its logging system (systemd-journald, and can be forwarded to old school syslog), and some dbus implementation.

    If that's an unreasonable requirement for your usecase, check out OpenRC

    [–] [email protected] 0 points 1 year ago (2 children)

    then what would you define it as?

    [–] [email protected] 4 points 1 year ago

    It's a system daemon that manages way more than an init system, hence the name "systemd".

    [–] [email protected] 1 points 1 year ago

    Hard question I guess. Middleware maybe?

    [–] [email protected] 1 points 1 year ago (1 children)

    The left and right one should be swapped.

    [–] [email protected] 1 points 1 year ago (2 children)
    [–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

    Yes, popular. Many distros use it and, believe it or not, most people don't care it's there. It works.

    [–] [email protected] 2 points 1 year ago

    All the major distros use systemd now.

    [–] [email protected] 1 points 1 year ago

    I knew a Arch guy who called it Sys-dumb-d. He refused to run systemd.

    I could mostly care less. It's.....fine. I miss upstart and it's simplicity. Kind of wish it had been actually developed to maturity, but here we are with an init system that also wants to do DNS.

    [–] [email protected] 0 points 1 year ago

    SOYSTEMD LOL 😂😂😂 (i use systemd)

    [–] [email protected] -3 points 1 year ago (3 children)

    It's never been popular by anybody except RedHat, that's how they sell courses end certifications.

    Still haven't found a way to start something after networking has finished when it takes a bit to set everything up. (and no, not going to limit vlans, tunnels,...)

    It's a technical 'solution' for a marketing problem.

    [–] [email protected] 3 points 1 year ago (1 children)

    Wouldn't you just set "networking" as a dependency on the unit of whatever you need started after?

    [–] [email protected] 1 points 1 year ago

    That's what you would do with the init scripts, as that environment waits until the previous one is finished. (ie you know you have working network) Systemd is in a hurry and there 'after' seems to mean 'not before' instead of 'after <specified> is finished', so after networking is started it advances to the next in line.

    [–] [email protected] 1 points 1 year ago

    Does After= not fit your use case? I was under the impression it does what you're looking for.

    [–] [email protected] 0 points 1 year ago (1 children)
    [–] [email protected] -2 points 1 year ago

    I love how fucking lennaert subtly changed that. Who cares that it complicates classic tools.