Date: Tue, 07 Apr 2009 23:12:43 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Freddie Cash <fjwcash@gmail.com> Cc: Joe Marcus Clarke <marcus@freebsd.org>, current@freebsd.org Subject: Re: Hal and KDM breakage (was Re: KDE4 and input events stalled) Message-ID: <49DC405B.7090208@freebsd.org> In-Reply-To: <b269bc570904072214n55d93ea6t309c83e5eafbdd5d@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
>>> I'm still curious whether it's feasible to just not monitor the vtys.
>> Sure, you can try it. Especially if you're not using GNOME, this might
>> be fine. Just remove the hacks from hald's rc.d script.
I think I finally understand the issue here. Basically,
there seem to be two options:
Option 1: Comment out this line from /usr/local/etc/rc.d/hald
#start_cmd="hald_start"
After this change, the rc.d/hald script will start hald
immediately, so that hald will be running before /etc/ttys
is processed.
This allows KDM/xdm/gdm to be started either from /etc/ttys
or from a very simple rc.d script (in particular, the 'lshal'
and 'getty' checks are not necessary in this case).
The risk with this approach is that hald on 7-STABLE and
earlier may be unable to detect whether the user is local or
using a remote X terminal, and hence the auto-mount features
of KDE and Gnome may not function properly. On FreeBSD-CURRENT,
this should be fine and everything should work properly.
Option 2: Use the current hald script as-is.
With this, the rc.d/hald script sets up a background process
that will start hald only after /etc/ttys has been processed.
As a result, KDM cannot be started in the traditional fashion
from /etc/ttys because KDM cannot be started before hald.
(Although Robert claims this should work...)
In this case, KDM can only be started from an rc.d script,
and that rc.d script needs to use some variant of the
"lshal" hack to ensure that KDM won't start before hald.
The advantage of this approach is that auto-mount should
function correctly in KDE and Gnome, even on 7-STABLE
and earlier.
Joe: Did I get this right?
Freddie Cash pointed out:
> Doesn't work, at least not in my quick-n-dirty testing, using the kdm4
> script I just posted. If you remove the lshal checks, then the
> keyboard doesn't work once kdm starts.
Freddie: If you remove the lshal checks from the kdm startup
script, then you have to also remove the hald_start
call from the hald startup script. Otherwise, kdm
will start before hald and bad things will happen
(keyboard/mouse failures at a minimum; I get a complete
black screen in this case).
Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49DC405B.7090208>