equivalent of chkconfig

[Tom H]

On Mon, Aug 17, 2015 at 9:41 AM, Ralf Mardorf
<ralf.mardorf at alice-dsl.net> wrote:
> On Mon, 17 Aug 2015 08:43:50 -0400, Luis Mondesi wrote:
>>
>> When you do a clean install of 15.10 you get the Full Systemd
>> Experience ™ It's very awkward for the first 30 seconds or so, but one
>> gets used to its quirks very fast.
>>
>> Cannot really complaint about it. Just continue on...
>
> I strongly disagree.
>
> For my everyday production environment I run Arch Linux since February
> 2012 with a clean systemd.
>
> This year in July I installed Wily from the server ISO on this
> multi-boot machine. What I got wasn't a "Full Systemd Experience", but
> a mess with init scripts and wrappers/workarounds.
>
> Btw. I'm still not used to systemd after using it for around 3 years,
> but for my workflow a clean systemd at least is easier to handle, than
> the Wily hybrid.
>
> You might get used to the Wily hybrid systemd within 30 seconds, you
> also might get used to a clean systemd within 30 seconds, but Wily
> definitively is a mix including init script and wrappers/workarounds and
> absolutely _not_ a "Full Systemd Experience".

1) Neither upstart nor systemd could've been introduced without being
able to handle sysvrc scripts.

2) The Ubuntu patches are in
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/patches?h=ubuntu/224-1ubuntu3
although not all Ubuntu changes are here. For example, if a systemd
unit replaces a sysvrc script but has a different name, there'll be a
symlink to "/dev/null" for that script in "/lib/systemd/system/" so
this must be done by something else in "debian/" (I haven't looked for
it).

I doubt that they make your Arch systemd very different from your
Ubuntu systemd (other than being in /usr/lib rather than /lib) except
for:

a) Ubuntu disables systemd's vconsole feature and uses its own
console-setup package instead.

b) Ubuntu doesn't provide a systemd service for all of its daemons so
some daemons are launched by scripts in "/etc/init.d/" via
runtime-generated systemd files in "/run/systemd/generator.late/".
It's a bit messy, SOMETIMES.

Even though I don't use systemd on Gentoo, I prefer its setup whereby
systemd doesn't use anything in "/etc/init.d/". It had a choice
between adapting systemd to understand openrc scripts and adding
systemd units to as many packages as possible and it chose the latter.
I doubt that it even considered the former.

Unless Ubuntu decides "we're going to provide native systemd units for
all packages that have sysvrc scripts in Ubuntu version X", these
units'll be provided at whatever pace the maintainers of packages with
sysvrc scripts choose to do so; and it's not a big deal.