[Pkg-ltsp-devel] Bug#403187: ltsp-client: need writeable
/etc/network/run for proper loopback device configuration
Vagrant Cascadian
vagrant+bugs at freegeek.org
Fri Dec 15 08:40:19 UTC 2006
Package: ltsp-client
Version: 0.99debian8
Severity: important
/etc/network/run should be added to the rw_dirs variable in
/etc/default/ltsp-client-setup, or else ifupdown can't write to
/etc/network/run/ifstate, and the loopback/lo device is not properly
configured.
without a proper loopback device, some software fails to function in an
ltsp-client environment.
--- debian/ltsp-client.ltsp-client-setup.default 2006-03-08
13:25:51 +0000
+++ debian/ltsp-client.ltsp-client-setup.default 2006-12-15
04:14:45 +0000
@@ -13,7 +13,7 @@
# tmpfs/bind directions that get mounted with only directory structure
# preserved
-rw_dirs="/var/cache/man /var/lib/xkb /var/lock /var/run /var/log
/var/spool /var/tmp /tmp /var/lib/discover /etc/hotplug/.run
/var/lib/nfs"
+rw_dirs="/var/cache/man /var/lib/xkb /var/lock /var/run /var/log
/var/spool /var/tmp /tmp /var/lib/discover /etc/hotplug/.run
/var/lib/nfs /etc/network/run"
# tmpfs/bind directions that get mounted with directory structure and
# data
# copied
live well,
vagrant
-- Package-specific info:
packages in chroot: /opt/ltsp/i386
ii initramfs-tools 0.85c tools for generating an initramfs
ii ldm 0.99debian8 LTSP display manager
ii ltsp-client 0.99debian8 LTSP client environment
More information about the Pkg-ltsp-devel
mailing list