From: Manish Ahuja <ahuja@austin.ibm.com>
To: Nathan Lynch <ntl@pobox.com>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH]Enabling Auto poweron after power is restored.
Date: Wed, 10 Jan 2007 14:58:40 -0600 [thread overview]
Message-ID: <45A55380.9020402@austin.ibm.com> (raw)
In-Reply-To: <20070109150519.GD8122@localdomain>
Nathan Lynch wrote:
> Paul Mackerras wrote:
>
>> Manish Ahuja writes:
>>
>>
>>> During power outages, the ups notifies the system for a shutdown. In the
>>> current setup, it isn't possible to power on when power is restored.
>>> This patch fixes the issue by calling the right ibm,power-off-ups token
>>> during such events. It also adds a proc interface so that rc.powerfail
>>> can parse the epow events and modify the power-off behavior accordingly
>>> to enable the right token to be called.
>>>
>> Creating new non-process-related files in /proc is frowned upon these
>> days, so we'll have to find somewhere in /sys for this. Anybody got a
>> suggestion?
>>
>
> Maybe a sysctl instead?
>
Wouldn't sysctl be /proc/sys/something again.
I did look under /sys but couldn't come up with a location to create
this new file.
Although creating new files under /proc is frowned upon, the subset of
files in the directory
seemed similar in functionality and connected to the new file I was
creating and hence this new file in
/proc/ppc64/rtas.
linux:/proc/ppc64/rtas # ls -x
. .. clock error_log frequency poweron poweron_auto
progress rmo_buffer sensors volume
I don't mind creating a /sys entry if anyone has a good suggestion.
next prev parent reply other threads:[~2007-01-10 20:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 18:28 [PATCH]Enabling Auto poweron after power is restored Manish Ahuja
2006-12-04 15:48 ` Will Schmidt
2006-12-04 19:31 ` Linas Vepstas
2006-12-04 19:49 ` Olof Johansson
2006-12-04 21:26 ` Manish Ahuja
2006-12-05 21:41 ` Manish Ahuja
2006-12-08 6:09 ` Paul Mackerras
2006-12-24 16:56 ` Manish Ahuja
2006-12-24 17:50 ` Manish Ahuja
2007-01-09 4:16 ` Paul Mackerras
2007-01-09 14:21 ` Segher Boessenkool
2007-01-09 15:05 ` Nathan Lynch
2007-01-10 20:58 ` Linas Vepstas
2007-01-10 20:58 ` Manish Ahuja [this message]
2007-01-12 0:38 ` Linas Vepstas
2007-02-03 4:16 ` Manish Ahuja
2007-02-06 17:58 ` Linas Vepstas
2007-02-07 2:24 ` Paul Mackerras
2007-02-07 19:42 ` Manish Ahuja
2007-02-08 22:01 ` Manish Ahuja
2007-02-07 16:59 ` Olof Johansson
2007-02-07 17:05 ` Manish Ahuja
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=45A55380.9020402@austin.ibm.com \
--to=ahuja@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.com \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).