On ven, 2009-01-16 at 01:06 -0200, Henrique de Moraes Holschuh wrote: > > I think it makes sense to tie them to uevents on the appropriate generic > > devices. Even if most hardware doesn't generate them, the ability to pop > > up a notification telling the user that the firmware thinks their system > > is too hot is useful. > > Well, it should actually be useful even without the uevents... as long as > the desktop environments are actually smart enough to notice the kernel > really wants to tell the user something when it outputs CRITICAL, ALERT and > EMERGENCY level messages... I'm not sure hal is able to do that atm, but it could, when receiving such events, pass them to a notification daemon so at least the user is warned. More stuff could be done but I guess it depends mainly on desktop people. Cheers, -- Yves-Alexis
Attachment:
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
