On Thu, 30 Jan 2003, Alex Chudnovsky wrote: > On Wednesday 29 January 2003 23:00, Tzafrir Cohen wrote: > > On Wed, 29 Jan 2003, Alex Chudnovsky wrote: > > > On Wednesday 29 January 2003 21:42, David Harel wrote: > > > > > > Driver that detects its hardware first ( meaning usually driver that is > > > loaded first, except USB, PCMCIA and other hotplugs ), gets eth0. And I > > > HATE THIS WAY, as it doesn't play well with hotplugging. This stupidity > > > should have been improved before long. > > > > How else can you identify eth0? > Why should it be "eth0 and eth1" at all, and not "cable_usb_modem_0 and > internal_nic_0", for example? >
What's the big deal? internal nic will get loaded as eth0 . That can be easily aranged. You Do want the internal nic loaded automatically with the network startup. However I'm not so sure how smart is it to load the external interface as a part of /etc/init.d/network start : Suppose that the cables network is unavailable for some reason . What happens then? You can't even access your computer from the local console, because it is still delayed trying to connect to the cables. On my home network I set it not to load the external NIC "automatically". It is loaded from init.d, but only after sshd starts, so I have some access to my computer. -- Tzafrir Cohen mailto:[EMAIL PROTECTED] http://www.technion.ac.il/~tzafrir ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
