> From: Simon Richter
> > We are going to need some software that handles button
> events, as well as
> > thermal events, battery events, polling the battery, AC
> adapter status
> > changes, sleeping the system, and more.
>
> Yes, that will be a separate daemon that will also get the
> events. But I
> think it's a good idea to have a simple interface that allows
> the user to
> run arbitrary commands when ACPI events occur, even without
> acpid running
> (think of singleuser mode, embedded systems, ...).
Fair enough. I don't think I would be out of line to say that our resources
are focused on enabling full ACPI functionality for Linux, including a
full-featured PM policy daemon. That said, I don't think there's anything
precluding the use of another daemon (or whatever) from using the ACPI
driver's interface.
> > Unix philosophy: "do one thing and do it well".
>
> Another Unix philosophy: "keep it simple, stupid". :-)
OK one more silly aphorism and I'll shut up. ;-) "Make it as simple as
possible, but no simpler."
Regards -- Andy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Apr 23 2001 - 21:00:27 EST