From: "Måns Rullgård" <mru@kth.se>
To: linux-kernel@vger.kernel.org
Subject: Re: Allow userspace do something special on overtemp
Date: Wed, 11 Aug 2004 11:18:49 +0200 [thread overview]
Message-ID: <yw1x657q9gna.fsf@kth.se> (raw)
In-Reply-To: <1092215024.2816.8.camel@laptop.fenrus.com>
Arjan van de Ven <arjanv@redhat.com> writes:
> On Wed, 2004-08-11 at 10: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.
>
> why not call /sbin/hotplug ????
Good idea, then udev could create /dev/blowtorch so some other program
can do ioctl(SCSI_STOP) (or just run cdrecord dev=6,6,6 -eject).
Besides, it is called HOTplug for a reason.
Seriously, though, isn't hotplug supposed to handle plugging and
unplugging of hardware, rather than any random events detected by the
kernel?
--
Måns Rullgård
mru@kth.se
next prev parent reply other threads:[~2004-08-11 9:18 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 [this message]
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
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=yw1x657q9gna.fsf@kth.se \
--to=mru@kth.se \
--cc=linux-kernel@vger.kernel.org \
/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