This bug report tracks the bug where the loopback interface failed to be brought up due to a missing /etc/network/interfaces. You appear to be describing a new bug, not previously reported; please open a new bug report for this. If the problem is a missing event from upstart-udev-bridge, you should file this new bug report against the upstart package.
Interesting! I bet there would be people on ubuntu-devel interested in knowing about this. BTW, I think the graph needs to express dependencies in more detail; there's no way to tell from this graph which dependencies are "or"ed dependencies, and which are "and"ed dependencies. Even better would be if you could graph the actual events that trigger at boot time by processing /var/log/syslog... (only works if you boot with --verbose)
wodny,
This bug report tracks the bug where the loopback interface failed to be brought up due to a missing /etc/network/ interfaces. You appear to be describing a new bug, not previously reported; please open a new bug report for this. If the problem is a missing event from upstart- udev-bridge, you should file this new bug report against the upstart package.
> As an additional project I've created a upstart start map generator: /bitbucket. org/wodny/ upstart- map
> https:/
> Results attached.
Interesting! I bet there would be people on ubuntu-devel interested in knowing about this. BTW, I think the graph needs to express dependencies in more detail; there's no way to tell from this graph which dependencies are "or"ed dependencies, and which are "and"ed dependencies. Even better would be if you could graph the actual events that trigger at boot time by processing /var/log/syslog... (only works if you boot with --verbose)