Date: Tue, 27 Jan 2009 20:51:38 +0100 From: Dominic Fandrey <kamikaze@bsdforen.de> To: Robert Noland <rnoland@FreeBSD.org> Cc: ports@freebsd.org Subject: Re: xorg upgrade and /etc/ttys regression Message-ID: <497F65CA.9060308@bsdforen.de> In-Reply-To: <1233084594.1981.24.camel@wombat.2hip.net> References: <20090127190217.de1802b5.lehmann@ans-netz.de> <497F5F68.3090308@bsdforen.de> <1233084594.1981.24.camel@wombat.2hip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Noland wrote: > On Tue, 2009-01-27 at 20:24 +0100, Dominic Fandrey wrote: >> Oliver Lehmann wrote: >>> Hi, >>> >>> I've used to start my login manager with /etc/ttys for years now (After I >>> considered myself became to lazy to type startx). >>> >>> After yesterdays xorg upgrade I've noticed, that the login manager which >>> comes up right after going to multiuser has no working mouse or keyboard >>> support. This is probably because the login manager gets started by >>> /sbin/init which uses getttyent which parses /etc/ttys. This all happens >>> before hald is being started which is the problem here. >> /etc/ttys is the very last thing in the boot process. >> >>> So the solution seems to be to drop/remove login manager startups >>> from /etc/ttys and move over to rc.d startup. >> It's much more likely that hald isn't working properly. Even if hald >> started late, as soon as it started, your mouse and keyboard would >> start working as soon as hald detects them (that's the whole point >> of using hald, runtime detection). > > I think the root of the issue here is that X isn't able to establish a > connection to hald at startup and does not retry. ... This implies to me that hald forks before it is connectable. This sounds rather annoying.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?497F65CA.9060308>