On Thu, Feb 14, 2008 at 03:03:17PM -0500, Paul Cartwright wrote: > 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?
Well, I suppose on the face of it, but this is how it is on my box and it works fine. Renumbering the scripts would be a very last resort. Try doing the procedure I suggested and see what happens. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
