3 ms·
> Forget about your system dir layout. Lets change it and mix everything up into / Actually, everything is put into /usr, in / you have just symlinks. And ther
by vetinari 9y ago
> Forget about your system dir layout. Lets change it and mix everything up into /
Actually, everything is put into /usr, in / you have just symlinks. And there's a reason for that.
> wtf systemd ? Now i have to read up on this new sh*t that they are pushing down my throat. Oh wait there is no documentation.
One would say, that after 8 years you would be able to find the documentation. It has manpages too.
- Drdrdrq 9y agoAlso, while I still oppose systemd (because it's a monolith, because it reinvents logging and because... it comes from the people behind DBus :) I must admit that lately I prefer writing systemd units to making nohup workarounds. I never did grok init.d scripts and from what I've seen neither did lots of other people. So that's a big plus in my book.
- acdha 9y agoI’m not in love with everything about systemd but I’ve noticed that about 90% of the attacks sound to an experienced sysadmin more like the person making the claim has never encountered/ understood the need for that particular feature. Many people will talking lovingly about SysV init without any mention of the many things people did to hack around limitations or the downtime suffered because they didn’t. (Yeah, it’s not perfect but the rough parts can be improved and I’m looking forward to standardization meaning we never talk about daemonization, automatic restarts, or logging again)
- JdeBP 9y agoYou have constructed the classic fallacious dichotomy between van Smoorenburg init and systemd. * http://uselessd.darknedgy.net/ProSystemdAntiSystemd/ http://uselessd.darknedgy.net/ProSystemdAntiSystemd/