[PATCH] command line options for hald-addon-acpi

Timo Hoenig thoenig at suse.de
Tue Aug 2 11:13:18 PDT 2005


Hi,

On Tue, 2005-08-02 at 13:33 -0400, David Zeuthen wrote:

> > Agreed regarding the D-BUS system bus, but not HAL.  Client applications
> > waiting for messages of HAL being sent on the system bus are happily
> > working even if HAL gets restarted.
> 
> These applications might lose events from HAL when HAL is not running.
> Thus they need to check the HAL state (properties) when HAL is restarted
> (they know from NameOwnerChanged).

Events can be cached or sent out asynchronous once clients are back on
the bus.  A concrete example which leads to serious system
inconsistencies would help me to understand the problem.

In any case, we really do not want to see systems rebooting all day long
because of software updates, do we?  "Other" operating systems have
exactly this drawback and we really should not imitate this behavior.
We can do it without reboots.  Wait, just let me check my uptime... ;-)

[...]

> Because you need to reboot anyway because of kernel updates which are
> probably more frequent than userland updates.

This might be true, but it is not an reason not to try to prevent
rebooting on software updates other than the kernel.

> Plus, the really important
> reason is that we don't want semantics that makes it an order of
> magnitude more difficult to developer applications (handle
> disconnect/reconnect)
> 
> Btw, this has already been discussed; see this thread
> 
>  http://mail.gnome.org/archives/networkmanager-list/2005-March/msg00022.html
> 
> for details (it's a huge thread). Thanks.

I will.

[...]

> I believe we already have this today with HAL - what are you missing?

There are drivers (IBM ACPI, Panasonic ACPI, Sony ACPI just to name a
few) generating ACPI events which are not handled by HAL and thus get
lost if HAL claims /proc/acpi/event.  Yes, there is a generic hotkey
driver on its way to make the specific drivers obsolete but it does not
yet provide the wide range of functionality the specific ones do.

Without changing the kernel's ACPI implementation,  acpid  will be
obsolete with the day HAL can ensure the distribution of all ACPI
events.

> Cheers,
> David

See you,

   Timo


_______________________________________________
hal mailing list
hal at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/hal



More information about the Hal mailing list