Bug#316808: discover1: Discover uses lib and data in /usr, which may not be mounted when discover runs
Package: discover1
Version: 1.7.7
Severity: important
Umm well, as title really. If you have /usr on a separate volume,
the first run of discover on boot will not run, leading to a number of
errors as things aren't discovered. Because of the data, this bug also
applies to discover1-data.
Moving the library is just a matter of adding --libdir=/lib to the
configure call, but I don't know where Policy would suggest the data goes.
/etc/rcS.d/S15discover
/etc/rcS.d/S35mountall.sh
~# fgrep /usr /etc/fstab
/dev/mapper/VG1-Usr /usr reiserfs notail 0 2
~# ldd /sbin/discover
libdiscover.so.1 => /usr/lib/libdiscover.so.1 (0xb7fb8000)
libm.so.6 => /lib/tls/libm.so.6 (0xb7f95000)
libc.so.6 => /lib/tls/libc.so.6 (0xb7e60000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xb7fea000)
~# dpkg -L discover1-data | fgrep /usr | wc -l
18
discover:
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (2, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-k7
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages discover1 depends on:
ii ash 0.5.2-5 Compatibility package for the Debi
ii dash 0.5.2-5 The Debian Almquist Shell
ii debconf 1.4.30.13 Debian configuration management sy
ii discover1-data 1.2005.01.08 hardware lists for libdiscover1
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libdiscover1 1.7.7 hardware identification library
-- debconf information excluded
Reply to: