Making it possible to uninstall initscripts / insserv and facilities

[Michael Biebl]

Am 24.11.2015 um 19:44 schrieb Michael Biebl:
> Am 24.11.2015 um 19:32 schrieb Petter Reinholdtsen:
>> [Michael Biebl]
>>> a/ Pere suggested to turn the Required- dependencies into Should-
>>> dependencies. This means, as long as initscripts is not installed,
>>> insserv does not fail, but potentially calculates a wrong ordering.
>>> This is not fatal for systemd though, as the ordering is not used by
>>> systemd, only the enabled state is relevant.
>>
>> Can you explain this bit some more?  What does it mean that the ordering
>> isn't used by systemd?
> 
> insserv looks at the dependencies specified in the LSB header and then
> generates symlinks in /etc/rc?.d/ including a start priority.
> 
> The priority is not used by systemd, only the information if a service
> is enabled or not. The start order is determined by systemd itself by
> looking at the LSB header of sysv init scripts and native unit files and
> then generating a dependency graph dynamically during boot.

To follow up on that:
In systemd, we mask or alias the facilities provided by the initscripts
package.

E.g hostname is a masked, i.e. a symlink to /dev/null (the hostname is
set by systemd before any other unit is started).
So if a sysv init script has a dependency on hostname, this becomes a nop.
Others are symlinks, because they are provided by native
implementations, say urandom is a symlink to systemd-random-seed.service.

So, sysv init scripts are correctly ordered against the facilities
provided by systemd.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151124/462986c7/attachment-0002.sig>