| 1 |
I'm talking about setting a default that's less than 60 seconds. I know i can |
| 2 |
change it, but IMO 60 seconds is an annoying wait when you're stuck booting a |
| 3 |
machine some other admin just bootstrapped. |
| 4 |
|
| 5 |
I think the people who NEED to wait 60 seconds should increase it. Or better |
| 6 |
yet, they should fix their network. |
| 7 |
|
| 8 |
You should get a DHCP response in < 10 seconds, it's as simple as that. If you |
| 9 |
don't, something is screwed up. |
| 10 |
|
| 11 |
The vast majority of people would be ok with a 10 second dhcp timeout, and |
| 12 |
those who aren't can increase it. |
| 13 |
|
| 14 |
Mark Dierolf |
| 15 |
|
| 16 |
|
| 17 |
|
| 18 |
|
| 19 |
|
| 20 |
On Thursday 14 October 2004 10:22 am, Jason Rhinelander wrote: |
| 21 |
> Mark Dierolf wrote: |
| 22 |
> > As long as there is an option to change the timeout, I don't think we'll |
| 23 |
> > get many complaints. |
| 24 |
> |
| 25 |
> There is, it's called dhcpcd_eth0 in /etc/conf.d/net. Just add "-t 10" |
| 26 |
> and you have your 10 second timeout. Alternatively, set up your boot |
| 27 |
> loader to give you a choice - I do this, and I choose "Gentoo" (boots |
| 28 |
> with softlevel=default, which starts net.eth0), or "Wireless" (boots |
| 29 |
> with softlevel=wireless, which starts net.wlan0 and NOT net.eth0) or |
| 30 |
> "Networkless" (boots with softlevel=nonetwork). After all, YOU are |
| 31 |
> hopefully going to know better than Gentoo whether or not your network |
| 32 |
> should be up. |
| 33 |
> |
| 34 |
> -- Jason Rhinelander |
| 35 |
> |
| 36 |
> -- |
| 37 |
> gentoo-dev@g.o mailing list |
| 38 |
|
| 39 |
-- |
| 40 |
gentoo-dev@g.o mailing list |
Archives