this post was submitted on 04 Oct 2023
715 points (95.3% liked)

linuxmemes

20756 readers
1357 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
poopsmith@lemmy.world
zephyr@lemmy.world
715
i find it's a great tool. (lemmy.world)
submitted 11 months ago by SatansMaggotyCumFart@lemmy.world to c/linuxmemes@lemmy.world
205 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] xcutie@linux.community 8 points 11 months ago* (last edited 11 months ago) (6 children)

I find everything so complicated with systemd.

SysV was just intuitive for me and my knowledge. There was just one directory with all the startup scripts in it. And they were run in their alphanumerical ordner. Just that simple. If I wanted to change the order in which the scripts started, I just had to rename the file. You don't want a script to run at all? Just remove it.

I assume, systemd has many advantages for a knowledged user. But for me, it still is just a hassle.

[–] Jimbob0i0@lemmy.world 8 points 11 months ago (1 children)

And what happened if one of those scripts failed?

How did your express a dependency of a service on data being mounted?

Did you ever have to face debugging failing networking via scripts?

[–] xcutie@linux.community 1 points 11 months ago

I just debuged it like every other of my scripts that failed. Again, I didn't need any special knowledge of the init process, just general (and for me: very limited) knowledge.

The answer to your other questions: I don't thing I ever did that.

load more comments (4 replies)