Date: Thu, 09 Apr 2009 16:38:23 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Tim Kientzle <kientzle@freebsd.org> Cc: Joe Marcus Clarke <marcus@freebsd.org>, Freddie Cash <fjwcash@gmail.com>, current@freebsd.org Subject: Re: Hal and KDM breakage (was Re: KDE4 and input events stalled) Message-ID: <49DE86EF.3030409@FreeBSD.org> In-Reply-To: <49DC405B.7090208@freebsd.org> References: <934e1d760904061455o4736d643o1d07e3292192d94c@mail.gmail.com> <1239078081.1908.41.camel@balrog.2hip.net> <49DAE987.7090802@freebsd.org> <1239086408.35025.59.camel@shumai.marcuscom.com> <20090407185915.GY31409@albert.catwhisker.org> <49DBA371.3080804@freebsd.org> <92cd2ff70904071637h362da63ua13c1f8eca6fc616@mail.gmail.com> <1239147806.98664.12.camel@shumai.marcuscom.com> <92cd2ff70904071653r4bf3b381lf5de220b2e280c0c@mail.gmail.com> <1239150469.98664.18.camel@shumai.marcuscom.com> <b269bc570904072214n55d93ea6t309c83e5eafbdd5d@mail.gmail.com> <49DC405B.7090208@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Not sure if this is even possible, but I thought I'd throw it out
there. Would starting hald before ttys are loaded, then restarting it
again at the end of the boot process work to solve this issue? It
seems that you have 2 distinct 'flavors' of hald here (with vty
support, and without), so if it's smart enough to do the right thing
for its consumers when it is restarted I think this approach might work.
Just a thought,
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49DE86EF.3030409>