And here is the modified upstart containing only th elocal FSs dep.
---------------------------------------------------------------------------------------------------
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
done.
Begin: Running /scripts/local-premount ... done.
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
fsck from util-linux-ng 2.17.2
udevd[429]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/51-android.rules:1/dev/sda1: clean, 178247/15269888 files, 3542118/61049344 blocks init: ureadahead-other main process (757) terminated with status 4 init: Failed to spawn network-manager main process: unable to execute: No such file or directory * Starting AppArmor profiles [240G [234G[ OK ] ------------------------------------------------------------------------------------------------ On Sun, Apr 10, 2011 at 12:14 PM, Nathanel Titane <[email protected] > wrote: > Actually, I'M sorry... please disregard the previous log... it had a typo > and didn't even load up... > > Here's the good default one: > > -------------------------------------------- > Begin: Loading essential drivers ... done. > Begin: Running /scripts/init-premount ... done. > Begin: Mounting root file system ... Begin: Running /scripts/local-top .. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/750786 Title: nmbd job fails to start on boot -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
