Linux installation: Second Ethernet interface ...

[Mike Bilow]

HORNE wrote in a message to Mike Bilow:

 H> It's conf.modules, not modules.conf.  

 H> [root at ppro /etc]# ls *mod*
 H> Xmodmap       conf.modules

The old name, now deprecated, was "conf.modules".  To be consistent with the
other similarly named configuration files, "modules.conf" is now preferred. 
The "depmod" utility will actually read both.

 H> I've spent a couple days now setting up cable modem, firewall, 
 H> "new" dual ppro, using redhat 4.2 (it's what I had). It has the 
 H> control panel.  Works ok for some things, but was certainly the 
 H> cause of at least one obscure failure.

As I said, I'm not a Red Hat expert.

 H> In rh4.2 (and presumably other versions) the network GUI writes 
 H> data into files like /etc/sysconfig/network-scripts/eth0. (The 
 H> firewall, with two cards, also has an eth1).  Then the scripts 
 H> like ifup, invoked by the scripts in rc.d, use that info.

 H> Seems awfully baroque to me, and a pain to dig through when
 H> something goes wrong. But it does work, most of the time.

Most distributions use a much simpler organization, but the various levels of
indirection across separate files would make it a lot easier for the programmer
writing the GUI tool.
 
-- Mike