Hello, This is a follow-up after using our system for a couple of days. The system was converted from FC2 to Gentoo. Mostly things went well. One thing I had not done much of was reboot. I've been trying this today. Unfortunately it seems that the Gentoo network init scripts are not treating me as kindly as the Fedora Core 2 scripts were.
The situation here is that the power I'm getting to this box from the router is pretty weak. The wireless network sometimes drops out but it worked well enough for us under FC2 to live with it and we've done what I know how to do to make it better without spending money. (Being out of work makes me tend to be that way) Anyway, with the FC2 scripts Linux would work pretty hard to get the network attached but even if it didn't attach it would set up all the info in ifconfig such that the interface showed and the Gateway address was set. Then after a user logged in all we had to do was start pinging and eventually we got connected. With Gentoo (or the way things are configured with default settings) it appears that if it cannot find the network it just gives up and requires root access to get it going. The file that's attached has a run through of what I'm seeing. Basically the driver is installed but the network is not up. I'm forced to bring up by hand continually until it finally gets to the router. From then on things are fine. How can I make the scripts try harder. It's not OK here to require root access to get this going. It's my wife's machine and she won't know how to do this. Thanks in advance, Mark On 4/19/05, Nicolas Bailey <[EMAIL PROTECTED]> wrote: > > The reason I used eth0 (which AFAIK is created by baselayout) is that > > this is the way older versions of baselayout do it. The latest versions > > put everything into net.lo and link net.eth0 to it (so the above still > > works) but linking to net.lo will break on older baselayouts. As I use > > ~arch everywhere, I'm not sure what the current stable baselayout uses, > > so I erred on the side of caution. > > > > On my one machien that isn't ~arch, net.eth0 isn't a link to net.lo > and net.lo wouldn't work, so your erring on the side of caution was a > good move. > > I guess the more complete solution is to use net.eth0 if you are on a > stable system and net.lo if you are running ~arch. > > Nick > > -- > [email protected] mailing list > >
bootup.info
Description: Binary data
