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