Date: Wed, 7 Dec 2005 20:59:37 +0100 From: Jose M Rodriguez <josemi@freebsd.jazztel.es> To: freebsd-gnome@freebsd.org Cc: Stefan Thurner <thurners@nicsys.de> Subject: Re: gdm keyboard Message-ID: <200512072059.38550.josemi@redesjm.local> In-Reply-To: <1132997999.843.8.camel@xris.fu41.vpn> References: <1132997999.843.8.camel@xris.fu41.vpn>
next in thread | previous in thread | raw e-mail | index | archive | help
El S=E1bado, 26 de Noviembre de 2005 10:39, Stefan Thurner escribi=F3: > > FirstVT=3D9 > > VTAllocation=3Dtrue > > Yes I found the same solution for the problem. But why does not > everybody encounter this problem. > > To me it seems that the speed of the computer and how fast all > virtual terminals are spawned before gdm is started is the reason for > the problem. On slower computers gdm is started before all virtual > terminals are spawned and then gdm takes one of the active virtual > terminals. > Soory for the delay ... But you're wrong in part gdm is allways launch before init can launch gettys. In a slow computer, gdm spend enough time before try to get the next VT. =20 In the meantime, the rc script ends and init can launch the gettys=20 _before_ gdm try to get next VT. In a fast computer, or when the rc script spends more time after gdm.sh,=20 gdm gets vt1 and init's gettys are dump enough to not test before alloc=20 VTs. And you end with both an init getty and gdm on vt1. =2D- josemi -- This mail was scanned by AntiVir Milter. This product is licensed for non-commercial use. See www.antivir.de for details.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200512072059.38550.josemi>