I'm still going back and forth on this. There's also bug #1152274,
which I'm marking as a duplicate. We really should do something better
here, I'm just not sure what.
FWIW, printing messages to the console just got harder, because mountall
has just been changed to log to /var/log/upstart instead of being bound
to the console at all. Maybe we need to revisit that decision.
** Summary changed:
- boot fails when a mount is a dangling symlink
+ boot fails when a tmpfs can't be mounted due to a dangling symlink
** Changed in: mountall (Ubuntu)
Status: Won't Fix => Triaged
** Summary changed:
- boot fails when a tmpfs can't be mounted due to a dangling symlink
+ boot fails when a kernel filesystem can't be mounted (e.g., due to a dangling
symlink)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096079
Title:
boot fails when a kernel filesystem can't be mounted (e.g., due to a
dangling symlink)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1096079/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
