|
|
|
|
|
by tombert
201 days ago
|
|
systemd solves problems that are not easily solvable in the old SysV init way. If you need resources to load in a specific order, for example, it’s trivial to do this with systemd, but you have to muck with weird symlink stuff to get the same effect with SysV. There are lots of things like that. You can hand wave this away and act like it’s not important, but it absolutely can be important to correctly make sure services load in the right order, and being abke to designate dependencies if services. Of course I have run non-systemd distros, like Ubuntu (back when it used upstart), Gentoo, and of course FreeBSD (yes I know it’s not a Linux distro but close enough for this particular point), so it’s not like non-systemd stuff is foreign to me, and I am just not convinced it is actually causing more headaches than other systems. |
|