On Thu, Mar 9, 2017 at 12:40 PM, Marvin Gülker <m-guel...@phoenixmail.de> wrote: > On Thu, Mar 09, 2017 at 07:57:19AM -0500, Rich Freeman wrote: >> Honestly, as somebody who monitors all the systemd bugs on Gentoo it >> isn't actually that much work, and I suspect that it wouldn't be that >> much work maintaining openrc scripts on Arch. I doubt they rename the >> apache binary 3x per year, or move its location around the filesystem. > > Maybe not the apache binary, but who keeps track of things like sticking > the logrotate cronjob into systemd timer unit files (something I just > recently experienced on an Arch machine when I was looking for where > logrotate was called from and how often)?
We don't generally create timer units for cron jobs installed by packages. We do have systemd-cron which can be a cron substitute using timers if you prefer for things in cron.d directories, or you can just run a regular cron. > Changes to mount units? We certainly don't do anything with mount units, and I'd be surprised if Arch messes with them though they could certainly do so. We just use fstab, and systemd has a generator by default which handles fstab. I'm not aware of anybody using mount units as a substitute for fstab, though it might make sense in situations where you want to use a mount as a dependency for a service. > Other > things absorbed by systemd? It's not like going without systemd is just > about setting different compilation options on upstream software. Not to > mention upstream software that has a hard dependency on systemd, like > GNOME I have heard -- these are going to require patching. Things like > these are going to grow rather than shrink, so I expect much work to come > onto the no-systemd people. > Well, if Arch is using these kinds of features then sure that is more work, and Gnome is a whole different beast. If nobody bothers to package a network manager because networkd is popular that would be a gap (though I doubt that is the case since networkd doesn't handle some cases). Most of the stuff that systemd does is at a moderate level of functionality. timedatectl certainly is good enough for a typcial system but it isn't intended to be an ntpd server implementation. networkd will handle a lot of typical cases, especially on servers, but as far as I'm aware it isn't really a great solution for laptops using Wifi. Resolved can handle the client side of DNS but certainly can't be an authoritative name server. The general goal systemd has is to provide a lot of the guts of a typical system to cut down on the variety of 3rd party stuff, but still allow that stuff to be used when it adds value. So, journald isn't a complete syslog implementation, but for what most people need it is adequate, etc. I guess all it is missing is an MTA. :) -- Rich
