At present I am still trying to learn the differences, so I am learning new commands and what is doing what. I guess this falls into the "new/unfamiliar" category that TrashyMG mentioned, and yes, it has been annoying for me, slowed me down, and caused some problems since I lack some fairly basic knowledge again.I never suggested you should. I've no experience with systemd at all, so have nothing to base an opinion on other than hearsay. Most of the arguments I've heard against it however were things that ultimately don't make a lot of difference to the end user. (or they don't have to) You're the first person criticising it that I've come across whose argument wasn't just that they disliked it on principle. (for any number of ultimately inconsequential reasons) You implied that you've tried it, but didn't like it, hence my wondering why. Thanks for your answer.Frankly, why should I like something that I dislike ? Why should I be forced to use something that I don't need ?
I suppose the biggest thing for me personally, though, is I do dislike systemd on principle. I have become quite fond of *nix since the 90s, and most of that is due to Linux. I appreciate that it has changed during this time, and I do see a lot of good from this, however the more it changes the less it is the thing that I loved, or at least some distros are. I play with a bunch of OSs, so it isn't like I am stuck with systemd or Linux, but if I am trying to use more than a few distros I am stuck with what it has done to Linux. I like options, and a lot of them are going away (although I hope systemd and the controversy over it will add more options in the long run, which it seems it will, even if it remains dominant in Linux). It is also nice to be able to have the stuff that I do for fun help me with skills in my professional life. Recently I felt like I didn't know anything while trying to work on something. While not entirely true, it turned out that I do now lack skills to do some very simple common things that I didn't have trouble with in the past. I really just underestimated how different things were going to be, and I DO need to learn it, regardless of my preferences, and that sucks.The only major annoyance I've had with systemd is that it throws me into an emergency shell whenever it can't mount a disk under boot, without telling me why. It used to just hang systemd completely, but that changed in an update. For what it's worth, sysvinit would just happily continue booting the system with the disk unmounted.
Another example about how shitty systemd is :What was annoying about it? (How did it affect your usage of the system?)
No, not reading the manual and omitting the "nofail" option in fstab is stupid.This is what I randomly commented in the fstab to make it boot :
#usbfs /proc/bus/usb usbfs defaults 0 0
So basically, you have a bad entry in the fstab, the boot fails.
This is S T U P I D.
At the very least I'd call that an odd design decision... Wouldn't it have made more more sense to make that the default, and add an option to mark particular volumes as being required to continue booting?