From: Dax Kelson <dax@gurulabs.com>
To: Pavel Machek <pavel@suse.cz>
Cc: trenn@suse.de, seife@suse.de,
kernel list <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>
Subject: Re: Allow userspace do something special on overtemp
Date: Wed, 11 Aug 2004 18:08:30 -0600 [thread overview]
Message-ID: <1092269309.3948.57.camel@mentorng.gurulabs.com> (raw)
In-Reply-To: <20040811085326.GA11765@elf.ucw.cz>
On Wed, 2004-08-11 at 02:53, Pavel Machek wrote:
> Hi!
>
> This patch cleans up thermal.c a bit, and adds possibility to react to
> critical overtemp: it tries to call /sbin/overtemp, and only if that
> fails calls /sbin/poweroff.
>
> Could it be applied?
> Pavel
Why invent Yet-Another-Call-To-Userland-Interface when either
hotplug/dbus, netlink or an ACPI event will do?
The argument "well what if hotplug of acpid don't know what to do" is,
IMO, bogus since:
* Obviously systems today are functioning
* Hardware will poweroff off on overheat anyway (not graceful, but will
save hardware components)
* Teaching hotplug/apcid isn't hard
* Policy should be kept out of the kernel if at all possible
Dax
next prev parent reply other threads:[~2004-08-12 0:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 8:53 Pavel Machek
2004-08-11 9:03 ` Arjan van de Ven
2004-08-11 9:06 ` Pavel Machek
2004-08-11 14:49 ` Len Brown
2004-08-11 14:52 ` Wichert Akkerman
2004-08-11 15:28 ` Thomas Renninger
2004-08-11 21:08 ` Kronos
2004-08-11 20:26 ` Pavel Machek
2004-08-11 9:18 ` Måns Rullgård
2004-08-11 18:22 ` Olaf Hering
[not found] ` <411A239C.8060606@blue-labs.org>
2004-08-11 20:22 ` Pavel Machek
2004-08-12 0:08 ` Dax Kelson [this message]
2004-08-12 3:29 ` Len Brown
2004-08-12 7:40 ` Pavel Machek
2004-08-12 14:28 ` Len Brown
2004-08-12 20:24 ` Pavel Machek
2004-08-12 22:51 ` Len Brown
2004-08-12 23:21 ` Pavel Machek
2004-08-12 7:35 ` Pavel Machek
2004-08-12 15:19 ` Len Brown
2004-08-12 15:16 ` Randy.Dunlap
2004-08-12 15:50 ` Stefan Seyfried
2004-08-12 17:27 ` [ACPI] " Stefan Dösinger
2004-08-12 22:53 ` Len Brown
[not found] <fa.fd8nc62.oig6ao@ifi.uio.no>
[not found] ` <fa.g1p407b.1c569pj@ifi.uio.no>
2004-08-13 4:22 ` Robert Hancock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1092269309.3948.57.camel@mentorng.gurulabs.com \
--to=dax@gurulabs.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=seife@suse.de \
--cc=trenn@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome