Julien Cristau wrote: > On Thu, May 14, 2009 at 17:42:16 +0200, Michael Biebl wrote: > >> I guess it should just assume AutoAddDevices "false" in such a case and use the >> settings from xorg.conf (or if they are not set, use a basic us keyboard layout >> and mouse) >> > How can I make a distinction between "hal won't be started" and "hal > takes a while to start"? I guess you can't. But do you want to wait (possibly indefinitly) for hal to show up, leaving the user without a usable keyboard/mouse? Is your concern, that during bootup, hal takes to long to start and is not yet available when X starts? Wouldn't something like a 10sec timeout within Xorg help here? Assuming NoAutoAddDevices if hal isn't there > when we start up means getting duplicated events whenever it shows up. I thought, if NoAutoAddDevices is used, that Xorg ignores devices reported via hal? Or maybe I'm just misunderstanding what you mean with duplicated events. > (also, xorg.conf devices are currently set up before the hal stuff, so > it's not clear -to me anyway- how to make this work without changing the > dix/ddx interface) Can't comment on that. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Description: OpenPGP digital signature