Package: initscripts
Version: 2.87dsf-8
Severity: normal

Hi.

I'm not sure if this really belongs to initscripts, but as running "mount -a" from the already booted system works I'd suggest so.

I have a fstab, that contains entries whose device-files do not exist per default (at least not during boot), but the options include noauto.

When booting with such a fstab, the boot process fails, complaining that the device file doesn't exist, and goes into maintenance mode.

As it should not mount "noauto" filesystems anyway, why does it have to fail here?


A typical use case for the above scenario could be: Using encrypted filesystems with dm-crypt. The /dev/mapper/something device might be created manually when the user sets up the mapping (either manually or via cryptdisks_start),... still one might want to have a fstab entry for this.


Cheers,
Chris.



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

Kernel: Linux 2.6.31-fermat (SMP w/4 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 initscripts depends on:
ii  coreutils                     7.5-6      GNU core utilities
ii debianutils 3.2.1 Miscellaneous utilities specific t
ii  libc6                         2.10.1-5   GNU C Library: Shared libraries
ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip ii mount 2.16.1-4 Tools for mounting and manipulatin ii sysv-rc 2.87dsf-8 System-V-like runlevel change mech
ii  sysvinit-utils                2.87dsf-8  System-V-like utilities

Versions of packages initscripts recommends:
ii e2fsprogs 1.41.9-1 ext2/ext3/ext4 file system utiliti ii psmisc 22.8-1 utilities that use the proc file s

initscripts suggests no packages.

-- no debconf information

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




--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to