<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2"> </HEAD> <BODY> On Tue, 2005-11-15 at 16:12 -0500, Dimi Paun wrote: <BLOCKQUOTE TYPE=CITE> <PRE> From: "Luke Macken" <<A HREF="mailto:lmacken@redhat.com">lmacken@redhat.com</A>> > o FAST AS HELL[0] Fast, but can we do better? Why do we need to bring up the networking before we start X? Also, is it feasible to probe for just some hardware (disk, video), start x, then continue with the hardware probing? Will it be any faster if we get rid of the wrappers? Would readahead help here at all? Basically, can we have X up in 10s? :) </PRE> </BLOCKQUOTE> We sometimes need X to have network connectivity. The reason is a simple one: X is a network protocol and X is used to login remotely to other hosts. GDM can query these hosts using XDM Broadcast iirc. We also might need the authentication system to be up and running. That can be LDAP or Kerberos or Samba or something else, which might require network support. There are many reasons I can think of that require network to be started first. But it's mainly for the ones that I can't think of right now that I hope we can get Network Support before X. I doubt that we can have X up in 10s in some cases. In my case I have to start 2 ethernet interfaces and 10 vlans and 4 vpn and one pppoe connection before I get network support. Load the firewall and start the quagga-bgp daemon. This will always take more than 10 seconds. After that the LDAP support must come up. And only then I am willing to talk about GDM. Then again, one that does not have all these to worry about, would be fine having X start before network and LDAP. Cheers, Razvan <TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%"> <TR> <TD> </TD> </TR> </TABLE> </BODY> </HTML>