Date: Tue, 7 Apr 2009 16:37:43 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Joe Marcus Clarke <marcus@freebsd.org> Cc: current@freebsd.org, Robert Noland <rnoland@freebsd.org> Subject: Re: Hal and KDM breakage (was Re: KDE4 and input events stalled) Message-ID: <92cd2ff70904071637h362da63ua13c1f8eca6fc616@mail.gmail.com> In-Reply-To: <49DBA371.3080804@freebsd.org> References: <934e1d760904061455o4736d643o1d07e3292192d94c@mail.gmail.com> <1239075455.1908.36.camel@balrog.2hip.net> <49DACDBD.3030809@freebsd.org> <1239077210.1908.39.camel@balrog.2hip.net> <49DAD429.6090309@freebsd.org> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
> > See /usr/ports/x11/gdm/files/gdm.in. This is working for GNOME users. > I agree that kdm and xdm should have rc.d scripts. Almost every other system is enabled through rc.conf and kdm and xdm should be the same. But, there's an enormous amount of documentation all over that says to enable kdm or xdm through /etc/ttys. I consider this a real POLA problem. I think that we need to continue to support the /etc/ttys mechanism for a while longer (and add a comment to the stock /etc/ttys to document that xdm/kdm/gdm shouldn't be started that way). I also feel pretty strongly that if kdm/xdm/gdm are all started through rc.d, then we really have to fix the post-/etc/ttys dependency handling. Your scripts are very confusing and basically broken. For example, "REQUIRE: hald" has absolutely no effect. Of course, I'm still confused about why hald has to start after gettys. I thought the whole point of hald was to monitor and publish changes to the system. Why can't it do the same with available consoles? Is there some missing kernel capability that makes this impossible? Or is there an architectural issue with hald that makes this harder than it sounds? Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?92cd2ff70904071637h362da63ua13c1f8eca6fc616>