1 |
> The long answer: We try to cater to the majority of our users. The |
2 |
> majority of our users use DHCP and modules, so we're unlikely to disable |
3 |
> them. |
4 |
I also use dhcp and modules but modules get updated automatically if I |
5 |
compile them so I do not need to update them again if I reboot. |
6 |
> Now, I believe that newer versions of the init scripts allow for |
7 |
> much more customization of the networking capabilities of Gentoo and I |
8 |
> am sure something could be worked out to remove this "delay". At the |
9 |
> same time, have you considered a "no-network" runlevel? |
10 |
No-network runlevel is manual work for every user for a general |
11 |
problem that exists in everyy Gentoo install. And I do not like to |
12 |
have to select a runlevel every time I boot. |
13 |
> |
14 |
> As for the module updates, I agree that something can be done to speed |
15 |
> it up or have it only run when needed, but at the moment we do not have |
16 |
> a way, which is why we are discussing this now to see if a workable |
17 |
> solution can be found. |
18 |
Modules get updated after compile so why do we update them on boot |
19 |
again? If you really need to, I think a config option for most of the |
20 |
speed-oriented Gentoo-users would be in place. |
21 |
|
22 |
For DHCP: |
23 |
I suggest backgrounding it as is done in knoppix. It will not hurt and |
24 |
bring the delay to 0 sec without shortening usability. |
25 |
I surrently use the network config option and a delay of 2 secs for |
26 |
dhcp. But you feel that delay when you boot w/o network connection. |
27 |
|
28 |
Same for netmount .. I hacked the init-script to background it. |
29 |
|
30 |
Stefan Schweizer |
31 |
|
32 |
-- |
33 |
gentoo-dev@g.o mailing list |