Things aren't quite that simple. /home is an NFS mount transported over VPN, and mountall generally dosn't mount it (presumably because the VPN isn't up quickly enough). It nevertheless happily emits the "filesystem" event. We tried solving the problem by adding the explicit "mounted" event and starting a third mountall run. So is the real problem here that mountall emits "filesystem" even if it didn't mount all of them?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964207 Title: Dependency loops due to ANDed start conditions leave system unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/964207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
