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

[Timo Hoenig]

Hi,

On Tue, 2005-08-02 at 12:18 +0100, Richard Hughes wrote:

> Isn't HAL the only thing that should be reading /proc/acpi/event?

Why would a kernel interface should be exclusively used by only one
specific application?  Since the interface can only be read by a single
process, user space is responsible to distribute those.  Our well-tried
solution for this purpose is  acpid.

> Anything else is legacy code that should be using the hal-backend
> anyway. I figure ACPI isn't likely to be restarted for the duration of
> the session. Is this too harsh?

Think of updating HAL which most likely implies a restart of  hald
without rebooting.

As long as HAL does not distribute ACPI events in the exact manner like
acpid  does (socket),

      * we break user space applications relying on the socket of  acpid
      * we run into race conditions as discussed

I'm still seeing HAL, well, yes, as the hardware abstraction layer.  We
really should not bloat it with things like the distribution of ACPI
events.

> Richard.

See you,

   Timo

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