Hi Fionn, thanks for taking the time back in June to file this bug
report and help us make Ubuntu better.
This is most likely a problem in mountall, which does the actual
processing of fstab entries, though it is tightly integrated with
upstart as it emits upstart events directly.
I will say that I was unable to reproduce this on natty. I created a
mount point
/dev/noexist1 /mnt defaults 0 2
And I received a message from plymouth telling me that that the disk
drive for $mountpoint is missing, and giving me the option to skip
(press S) or do manual recovery (M).
Can you explain what you mean by a missing mount point so we can make
another attempt to reproduce the problem?
Marking Incomplete pending response from Fionn
** Changed in: upstart (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589643
Title:
missing mount targets in fstab block startup completely
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
