Package: mount
Version: 2.13.1.1-1
Severity: important

Hi.

I think I've discovered a bug in mount (maybe this belongs to initscripts but I don't think so).

When I specify mount-points in /etc/fstab via UUID= (and probably also via LABEL= or by specifying a device-file) mount tries to find that UUID/LABEL/etc. at boot even when I've specified noauto as mountoption.
I get some errormessage where it complains that it cannot find the device/etc.

This should be fixed that for entries with noauto mount doesn't try to find the UUID/LABEL/device-file when invoked via mount -a or so...

The UUID/LABEL/device-file might not yet exist, for examples (like in my case), as it's a dm-crypt encrypted filesystem and the UUID/LABEL/device-file won't appear before I do some cryptsetup magic...


Thanks in advance,
Chris.

PS: I've set this to important as it blocks booting ;)

-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mount depends on:
ii  libblkid1                     1.41.3-1   block device id library
ii  libc6                         2.7-16     GNU C Library: Shared libraries
ii  libselinux1                   2.0.65-5   SELinux shared libraries
ii  libuuid1                      1.41.3-1   universally unique id library

mount recommends no packages.

Versions of packages mount suggests:
ii nfs-common 1:1.1.4-1 NFS support files common to client

-- no debconf information


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to