From: Tollef Fog Heen Date: Sat, 5 Jun 2010 16:47:10 +0000 (+0200) Subject: Update a few gotchas X-Git-Tag: 0.git+20100605+dfd8ee-1~2 X-Git-Url: https://err.no/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ec42efa5422eaec999bc8d0cf7dae3c9dd55c2a5;p=systemd Update a few gotchas --- diff --git a/debian/README.Debian b/debian/README.Debian index 6e537b89..494e6cb1 100644 --- a/debian/README.Debian +++ b/debian/README.Debian @@ -10,11 +10,21 @@ init=/bin/systemd to the kernel command line and then rebooting. -There are some known bugs and problems associated with systemd and -other packages in Debian at the moment. The main one is a race -condition between / being mounted read-write and udev calling ifup on -network interfaces. This will, in some cases, cause interfaces which -have "allow-hotplug" set for them, but not "auto" fail to come up. -This is a known bug and being fixed in udev's net.agent. - - -- Tollef Fog Heen , Sat, 5 Jun 2010 08:41:51 +0200 +Known bugs and problems +======================= + +There is a race condition between / being mounted read-write and udev +calling ifup on network interfaces. This will, in some cases, cause +interfaces which have "allow-hotplug" set for them, but not "auto" +fail to come up. This is a known bug and being fixed in udev's +net.agent. + +The error reporting when you have loops or unsatisfiable conditions +between init scripts is not very good, it will cause systemctl to +respond with "invalid argument". Inspecting the dmesg can give useful +clues in that case. + +Restarting DBus breaks systemctl, since there is then no way to +connect to the bus that systemd thinks it's connected to. + + -- Tollef Fog Heen , Sat, 5 Jun 2010 18:41:06 +0200