765
submitted 3 weeks ago* (last edited 3 weeks ago) by renzev@lemmy.world to c/linuxmemes@lemmy.world
you are viewing a single comment's thread
view the rest of the comments
[-] savvywolf@pawb.social 129 points 3 weeks ago

"I hate systemd, it's bloated and overengineered" people stay, perched precariously on their huge tower of shell scripts and cron jobs.

[-] Damage@feddit.it 48 points 3 weeks ago

huge tower of shell scripts and cron jobs.

That's bloat. I start all my services manually according to my needs. Why start cupsd BEFORE I need to print anything?

[-] EddyBot@discuss.tchncs.de 38 points 3 weeks ago

thats what systemd sockets are here for

[-] pmc@lemmy.blahaj.zone 9 points 3 weeks ago
[-] corsicanguppy@lemmy.ca 25 points 3 weeks ago

“I hate systemd, it’s bloated and overengineered”

And built poorly by people who don't work well with others and then payola'ed onto the world.

people stay, perched precariously on their huge tower of shell scripts and cron jobs.

Fucking UNIX is shell scripts and cron jobs, skippy. Add xinetd and you're done.

[-] HubertManne@moist.catsweat.com 8 points 3 weeks ago

yeah I just hate the move away from flat text files honestly. Its one thing I did not like about windows NT with the registry. databasing up the config.

[-] Laser@feddit.org 4 points 3 weeks ago

Which part of systemd's config is not text-based? The only "database" it uses for configuration is the filesystem

[-] HubertManne@moist.catsweat.com 2 points 3 weeks ago

well its text but its just a bit more complex of a flat file. like yaml. like one thing I really liked about cisco ios was how the config file the commands where pretty much the same thing. granted thats not unix but its the simplicity level that is ideal to me.

[-] Laser@feddit.org 8 points 3 weeks ago

systemd config is inspired by INI, with section headers and key-value pairs. It doesn't get much flatter than that. It doesn't compare to YAML or JSON.

[-] HubertManne@moist.catsweat.com 1 points 3 weeks ago

ini as in windows init files?

[-] Laser@feddit.org 1 points 3 weeks ago
[-] barsquid@lemmy.world 18 points 3 weeks ago

If systemd was only managing services there would be less opposition. People opposed don't want a single thing doing services and boot and user login and network management and...

[-] SomethingBurger@jlai.lu 17 points 3 weeks ago* (last edited 3 weeks ago)

Are they also opposed to coreutils being a single project with dozens of executables doing different things?

[-] barsquid@lemmy.world 12 points 3 weeks ago

IDK, ask them. There are some in this thread. I'm addressing the strawman argument that people against it are luddites set in their ways over their beloved cron jobs.

[-] azertyfun@sh.itjust.works 8 points 3 weeks ago

Wait until you learn about debhelper.

If you use a debian-based system, unless you have actively looked at the DH source, the one thing that built virtually every package on your system, you do not get to say anything about "bloat" or "KISS".

DH is a monstrous pile of perl scripts, only partially documented, with a core design that revolves around a spaghetti of complex defaults, unique syntax, and enough surprising side effects and crazy heuristics to spook even the most grizzled greybeards. The number of times I've had to look at the DH perl source to understand a (badly/un)documented behavior while packaging something is not insignificant.

But when we replaced a bazillion bash scripts with a (admittedly opinionated but also stable and well documented) daemon suddenly the greybeards acted like Debian was going to collapse under the weight of its own complexity.

[-] wax@feddit.nu 3 points 3 weeks ago* (last edited 3 weeks ago)

Oh yes, fuck dh with a rusty pole. I've had to paclage some stuff at work, and it's a nightmare. I love having to relearn everything on new compat levels. But the main problem is the lack of documentation and simple guidelines

this post was submitted on 23 Sep 2024
765 points (95.5% liked)

linuxmemes

20993 readers
1667 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