*** This bug is a duplicate of bug 459642 *** https://bugs.launchpad.net/bugs/459642
Can you explain why this was marked as a duplicate of https://bugs.launchpad.net/bugs/459642 Is there an implicit 'bind' mount when trying to mount /var/log to tmpfs? That bug has been marked "won't fix" because "upstart/mountall doesn't handle bind mounts reliably". (I don't really see why 'unreliable' is a valid justification for not fixing it, but perhaps I don't understand the politics involved.) Regardless, do the unreliable bind mounts apply to mounting /var/log to tmpfs? It sounds to me like upstart/mountall should be able to handle all of this since these mounts can be accomplished later. Some serious functionality has been lost with the change to upstart. -- failed to boot if /var/tmp and /tmp specified in /etc/fstab https://bugs.launchpad.net/bugs/471794 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