Commit bd759702 authored by Tollef Fog Heen's avatar Tollef Fog Heen
Browse files

Document that /etc/network/run should be a symlink

parent a7432c14
......@@ -16,4 +16,14 @@ Known bugs and problems
The PAM module makes su exit with an error after running the command,
hiding the real exit status of the process.
-- Tollef Fog Heen <>, Sun, 29 Aug 2010 10:39:57 +0200
ifupdown's postinst has a bug where it ends up creating
/etc/network/run as a normal directory rather than a symlink to
/dev/shm or /lib/init/rw. This can cause network interfaces to not
start correctly on boot. The easiest way to fix this is to run:
mv /etc/network/run /etc/network/run.old
ln -s /lib/init/rw/network /etc/network/run
mv /etc/nework/run.old/* /etc/network/run
rmdir /etc/nework/run.old/
-- Tollef Fog Heen <>, Sun, 26 Dec 2010 20:29:37 +0100
......@@ -9,6 +9,8 @@ systemd (15-1) experimental; urgency=low
* Remove -s from getty serial console invocation.
* Add dependency on new util-linux to make sure /sbin/agetty exists
* Don't mount /var/lock with gid=lock (Debian has no such group).
* Document problem with ifupdown's /etc/network/run being a normal
[ Michael Biebl ]
* Revert upstream change which requires libnotify 0.7 (not yet available in
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment