this post was submitted on 27 Oct 2024
1269 points (99.2% liked)

linuxmemes

21138 readers
726 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
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 46 points 4 days ago (2 children)

    Usually such things have a simple explanation. systemd does a lot ~~with time and date, for example scheduling tasks. It's quite obvious that it has this capabilities, when you think about it.~~

    FTFY

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

    Not that that's bad when it's stuff like this

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

    Too much

    But that has been a complaint for 10 years and it's only gotten worse

    I wouldn't mind systemd if it weren't for the fact that it was to be a startup system that promised to make everything easier and faster to startup yet managing systemd is a drag at best, and of it did one thing it's making my systems boot up like mud

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

    I feel like the glued together collection of scripts was way worse to manage than systemd.

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

    Is it? It was always super easy to get anything done and with systems it suddenly got factors more complicated. Port assignment was super easy to do, note the past tense. It now requires systemd and instead of a 15 second config file change and service restart I now need to create and delete files, restart multiple services, God knows what in systems.

    Simply put: why? If you make an alternative solution AT LEAST it shouldn't become way more over complicated to get basic tasks done

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

    I definitely think so. Init was a mess of bash scripts and concurrency and whatnot was a problem. Making a script to start a service was very dependent on the distro, their specific decisions and whatnot. Systemd services and timers make things very easy and they have great tools to manage those. And now it's basically the same on every distro.