This is a wordy explanation of the solution. If you don't care, trash me now!
Tehhee.
TurboTex wrote:
> /etc/conf.modules holds the clue. It needs to be told to start up the
> interface.
> http://ccms.net/~mhtexcollins/presentation.html
"Zacary M. Brown" wrote:
>
> R.J.,
>
> is any of your networking being started on boot? do you get a
> "delaying eth0 initialization", or what?
Well, as it turned out, the two of you put me on the right track. The problem
was that /etc/rc.d/init.d/network was not being run on boot up. A quick check
(actually I think it took me hours to stumble onto this) to "chkconfig --list"
revealed that the network init script was not being run for init levels 3, 4, or
5. "chkconfig" helped me fix that. The first reboot was nasty b/c modprobe
searched for all ~40 eth devices. Boy did it complain. Teheh. After that,
modprobe shut up and everything works like a charm.
Thanks a bunch for your fast input. This is my first experience with support
from this group in a long time. It was a good one.
R. J. 5-29-99 5:27a.
> "R. J. Woodward" wrote:
> > Paul Sack wrote:
> > > Well I don't know which script does it, but the easy/novice way I do it is
> > > through netcfg.
> >
> > Yea, I tried that too. I think netcfg also writes /etc/.../ifcfg-eth0. Sure
> > enough, "at boot" was checked.
> >
> > Next?
> >
> > Tehehe.
> > R. J. 5-27-99 4:13a.
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
