BLINDAUER Emmanuel wrote:
Le Mercredi 29 Octobre 2003 00:41, Han Boetes a �crit :
S01xfs S02dm S03iptables S09network
Yes but dm needs networking at the least. This solution may work for you but mandrake has to have sane defaults for everyone. Which is the general problem with suggestions. Most people only take their own preferences and situation in account.
Starting X and the correspondant dm take some time, perhaps 2 ou 3 second, to be operational to input a login name. I think that this time can be used to start network and related stuff. other process like postfix or cups can be started at later time, because the logging action take some time
Since it seems that networking is one of the bottlenecks:
Having networking up is generally just to have the loopback interface running. Without knowing more, does dm's/X need more than that really?
I'd then propose to set up net interfaces in parallell:
loopback - guess it starts 'instantly', fine for most dependencies
eth0 - dhcp/zcip might take some time: comes up when it comes up
eth1 - static? fine & dandy!
...
ethN
The only problem I see is services that are bound to specific ip:s.
How does Apache react when it want's to bind to a specific ip that doesn't exist?
On the other hand, starting interfaces in the order of loopback, static interfaces and last dhcp/zcip and returning a [OK] after static is done
would solve that problem.
Yes, this is maybe a solution for my needs, but it seems like it could catch many situations in the wild.
Maybe initscripts..rpm should fork a initscripts-hiavail for servers...
Or better: check to see if we are in runlevel 5 or not, since a server normally don't run X (or?).
Just my swedish krona...
/m
