diff options
| author | Michael Biebl <biebl@debian.org> | 2014-03-28 13:50:58 +0100 |
|---|---|---|
| committer | Michael Biebl <biebl@debian.org> | 2014-03-28 13:52:02 +0100 |
| commit | b45cdbfd67620af1d3800dcb31aa65e9a06768bb (patch) | |
| tree | ee3c26888b1f7ef80169d33aa10d2b304bb27f07 | |
| parent | 4689c8081228091bab4714ee0af2e2ce015596c2 (diff) | |
Try to better explain why 03-systemd.patch is needed
| -rw-r--r-- | debian/patches/03-systemd.patch | 16 |
1 files changed, 14 insertions, 2 deletions
diff --git a/debian/patches/03-systemd.patch b/debian/patches/03-systemd.patch index 2597d698..cb3c9d6f 100644 --- a/debian/patches/03-systemd.patch +++ b/debian/patches/03-systemd.patch @@ -1,6 +1,18 @@ Description: Debian specific tweaks for NetworkManager systemd service file - - Do not install NetworkManager into the network.target, as this will lead to a - dependency loop (NetworkManager is installed in /usr). + This patch is needed to avoid a dependency loop which is generated + by early boot (rcS) SysV init scripts depending on the $network LSB + system facility (either directly or indirectly via $remote_fs). + . + The $network LSB system facility is mapped to network.target. + . + Those rcS SysV init scripts are started in sysinit.target, + NetworkManager.service is started via multi-user.target, which depends + on sysinit.target. + . + As long as we have rcS SysV init scripts which such a dependency on + $remote_fs or $network we can not make NetworkManager.service a provider + for network.target. + Author: Michael Biebl <biebl@debian.org> --- a/data/NetworkManager.service.in +++ b/data/NetworkManager.service.in |