From owner-freebsd-current@FreeBSD.ORG Thu Apr 9 23:38:40 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C9341065670 for ; Thu, 9 Apr 2009 23:38:40 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with ESMTP id 893FA8FC1B for ; Thu, 9 Apr 2009 23:38:39 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 15766 invoked by uid 399); 9 Apr 2009 23:38:35 -0000 Received: from localhost (HELO 192-168-180-198.nodomain) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 9 Apr 2009 23:38:35 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <49DE86EF.3030409@FreeBSD.org> Date: Thu, 09 Apr 2009 16:38:23 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.21 (X11/20090321) MIME-Version: 1.0 To: Tim Kientzle 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> <49DC405B.7090208@freebsd.org> In-Reply-To: <49DC405B.7090208@freebsd.org> X-Enigmail-Version: 0.95.7 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Joe Marcus Clarke , Freddie Cash , current@freebsd.org Subject: Re: Hal and KDM breakage (was Re: KDE4 and input events stalled) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Apr 2009 23:38:40 -0000 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