From b45cdbfd67620af1d3800dcb31aa65e9a06768bb Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Fri, 28 Mar 2014 13:50:58 +0100 Subject: Try to better explain why 03-systemd.patch is needed --- debian/patches/03-systemd.patch | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) (limited to 'debian/patches/03-systemd.patch') 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 --- a/data/NetworkManager.service.in +++ b/data/NetworkManager.service.in -- cgit 1.3.0-6-gf8a5