Anything with the 'user' fs option, should probably be ignored/skipped by mountall to begin with, as those filesystems are generally not wanted at boot time.
According to fstab(5) (but not mountall) you can pass the 'optional' option to unknown fstypes, or the 'nobootwait' option to not hold up the boot waiting for a filesystem. For the case of something in /media, you probably need 'nobootwait'. I can confirm this behavior in Lucid (10.04). I would expect mountall to ignore fstab entries with the user option. -- If a drive in the fstab is missing at boot, the boot process hangs for user input https://bugs.launchpad.net/bugs/623303 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
