ethernet probs me in person??

Jerry Feldman gaf at
Tue Feb 15 21:36:56 EST 2000

I can't give you any hardware advice on this because it is a Mac, but the 
first thing you should check is that the kernel recognizes eth0. As I had 
mentioned yesterday, networking is brought up by the scripts when you 
transition from single to multi-user mode. The lo interface is just a 
loopback in the kernel. I suspect that somehow the scripts are not being 
executed. Different releases of Linux assign different run levels for thing.
SuSE, for example uses run level 2 for command line and run level 3 for 
GUI, Red Hat uses 3 and 5 respectively. The location of the scripts is in 
the init.d directory which can be a subdirectory of /etc or /etc/rc.d or 
/sbin depending on the distribution. There are symbolic links to these in 
directories rcn.d, where n == run level. Again, the rcn.d directtories are 
usually in the same directory as init.d, or subdirectories of init.d. 
(Confusing, but its different with each distribution). It will look l;ike 
lrwxrwxrwx   1 root     root           10 Feb  8 16:23 K40network -> 
lrwxrwxrwx   1 root     root           10 Feb  8 16:23 S05network -> 
When transitioning to multi-user the specified or default run level will be 
executed. The symlinks in the rcn.d directory wil be executed. The Knn 
scripts will be executed with the stop parameter, and the S scripts will be 
executed with the start parameters. Generally, the network script will 
bring up .
On SuSE, lo is brought up by the boot script and on Red Hat via the network 
script execuing /etc/sysconfig/network-scripts/ifcfg-lo.

You might just try bringing lo up by hand:
/sbin/ifconfig lo netmask up 
This should bring up the local loopback interface. 

The symlinks will look like:

Josh Forman wrote:
> Ok, I seem to have some things under control.   I am now booting "normally"
> - normal except for the fact that interfaces eth0 and lo aren't brought up.\

Jerry Feldman <gaf at>
Boston Linux and Unix user group

Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at (Subject line is ignored).

More information about the Discuss mailing list