On Thu February 14 2008, Douglas A. Tutty wrote: > My guess is that in your particular installation, there is a conflict of > boot dependancies, e.g. networking can't start until a module is loaded > but that happens in a later init script. This manual booting procedure > will track this down. Then you can make a temporary fix (even if its > adding a symlink to start networking again at a later point in the > boot), and report the bug.
this is what I think also.. once I figure out when networking should start, I need to rename the networking script in /etc/rcS.d to a... larger number? right now there are these 3 scripts: S38resolvconf S39ifupdown S40networking wouldn't you think ifupdown would come after networking? -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459
