Package: discover Version: 2.0.7-2 Severity: minor Discover stores and reads the crash file from /var/lib/discover, but that location could or could not be mounted (for example, if /var would be a mountpoint). Usually the mounted state is consistent across reboots etc though, so it usually doesn't matter too much.
However, cluttering the mountpoint /var with directories & files when /var is still to be mounted is not very clean, and it could happen that sometimes /var is, and sometimes isn't mounted. Best would be IMHO to use /discover-modprobe.crash or something in an always-present directory, as it's just a very temporary file. Alternatively /var/lib/discover could be created by the package, and /var/lib/discover used if it exists, and fallbackup to /discover-modprobe if it doesn't. This will at least prevent cluttering up the /var mountpoint. --Jeroen -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Versions of packages discover depends on: ii libdiscover2 2.0.7-2 hardware identification library -- no debconf information -- Jeroen van Wolffelaar [EMAIL PROTECTED] http://jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
