On Fri, 2005-01-28 at 14:29 +1300, Nick Rout wrote: > in /etc/conf.d/net > > iface_eth0="dhcp" > dhcpcd_eth0="-t 3" > > the comment says: > > # For DHCP set iface_eth? to "dhcp" > # For passing options to dhcpcd use dhcpcd_eth? > > -t is the timeout, as per man dhcpcd > > what about static addresses? can you still pass options to the eth's?
> On Thu, 27 Jan 2005 19:39:30 -0500 > Nick Smith <[EMAIL PROTECTED]> wrote: > > > On Fri, 2005-01-28 at 12:12 +1300, Nick Rout wrote: > > > I simply put a small timeout into dhcp - 3 seconds or so - and then if > > > eth0 is not connected it doesn't get an ip address and is never brought > > > up. > > > > > > similarly if there is no access point, or no wireless dhcp server on > > > that access point, eth1, the wireless one never gets brought up. > > > > > > > > where is the time out specified? i would love to do that with my laptop, > > would be easier than managing 4 separate run levels. > > > > > On Thu, 27 Jan 2005 22:27:02 +0100 > > > Mats Lidell <[EMAIL PROTECTED]> wrote: > > > > > > > Hi, > > > > > > > > What is the right way to make the boot go fast when a laptop isn't > > > > connected to eth0? > > > > > > > > I sometimes connect wireless and sometimes I use a cable. With my > > > > current setup it always tries to bring up eth0 during the boot. This > > > > is no good when there is no cable connected. > > > > > > > > Is there some convenient way to resolve this so that when there is no > > > > cable but a wireless net it is used instead directly. Or can I use > > > > some boot parameter to guide the boot process to ignore eth0 when I > > > > intend to use wireless? > > > > > > > > Yours > > > > -- > > > > %% Mats > > > > > > > > > > > > -- > > > > [email protected] mailing list > > > > > > -- > > > Nick Rout <[EMAIL PROTECTED]> > > > > > > > > > > > > -- > > [email protected] mailing list > > -- > Nick Rout <[EMAIL PROTECTED]> > > -- [email protected] mailing list
