The point of the mountall2 script was to introduce the idea of a more
intelligent booting process, with pre and post mount hooks and the
ability to check the progress of the FSCK remotely.

I shied away from using the nobootwait option because I needed a
postmount script to restart some services once the filesystem gets
online.

If the original mountall generates UPSTART events, then I supposed it is
possible to trigger a post-mount script that way.

GĂ©rald

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/614662

Title:
  A better mountall

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/614662/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to