From: Avery Pennarun <apenwarr@worldvisions.ca>
To: daenzerm@student.ethz.ch
Cc: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
Hadess <hadess@writeme.com>,
debian-powerpc@lists.debian.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: apmd and other archs
Date: Thu, 23 Nov 2000 03:08:08 -0800 [thread overview]
Message-ID: <20001123030808.A13371@worldvisions.ca> (raw)
In-Reply-To: <3A1CF40F.5A509ACB@relog.ch>; from daenzer@relog.ch on Thu, Nov 23, 2000 at 11:40:15AM +0100
On Thu, Nov 23, 2000 at 11:40:15AM +0100, Michel Dänzer wrote:
> > > > /proc/apm and /dev/apm_bios are so simple that it should be easy to
> > > > convince any power management system to provide those API's.
> > >
> > > The info logged to /proc/apm is currently logged to /etc/power/apm. I
> >
> > Is this a typo? Why is status information in /etc?
>
> Because it's from pmud, which can't create /proc entries.
Then it should go in /var, I think. We have standards for this stuff.
(FSSTND, FHS, Debian policy.) I might want to mount /etc read-only (and
/usr too, while I'm at it)... and this sounds like it would prevent me from
doing so.
Thanks,
Avery
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-11-23 11:08 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20001122143042.A28078@worldvisions.ca>
2000-11-23 8:47 ` apmd and other archs Michael Schmitz
2000-11-23 10:09 ` Avery Pennarun
2000-11-23 10:40 ` Michel Dänzer
2000-11-23 11:08 ` Avery Pennarun [this message]
2000-11-23 11:15 ` Michael Schmitz
2000-11-23 11:31 ` Avery Pennarun
2000-11-23 13:36 ` Michael Schmitz
2000-11-23 14:18 ` Gabriel Paubert
2000-11-23 18:40 ` Michael Schmitz
2000-11-24 14:23 ` Gabriel Paubert
2000-11-24 18:29 ` Takashi Oe
2000-11-24 14:47 ` Olaf Hering
2000-11-24 15:23 ` Michael Schmitz
2000-11-23 11:37 ` Gabriel Paubert
2000-11-23 13:32 ` Tony Mantler
2000-11-23 14:12 ` Gabriel Paubert
2000-11-23 14:24 ` Adrian Cox
2000-11-24 10:07 ` Gabriel Paubert
2000-11-24 2:42 ` Josh Huber
2000-11-23 11:11 ` Michael Schmitz
2000-11-23 13:36 ` Hadess
2000-11-23 13:54 ` Michael Schmitz
2000-11-27 13:23 ` Michael Schmitz
2000-11-27 14:53 ` Benjamin Herrenschmidt
2000-11-27 15:34 ` Michael Schmitz
2000-11-27 20:50 ` Michael Schmitz
2000-11-24 13:51 ` Benjamin Herrenschmidt
2000-11-24 15:11 ` Bastien Nocera
2000-11-24 13:40 ` Benjamin Herrenschmidt
2000-11-24 14:29 ` Gabriel Paubert
2000-11-24 15:33 ` Benjamin Herrenschmidt
2000-11-24 16:26 ` Gabriel Paubert
2000-11-24 17:31 ` Benjamin Herrenschmidt
2000-11-24 17:56 ` Geert Uytterhoeven
2000-11-24 19:27 ` Gabriel Paubert
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=20001123030808.A13371@worldvisions.ca \
--to=apenwarr@worldvisions.ca \
--cc=daenzerm@student.ethz.ch \
--cc=debian-powerpc@lists.debian.org \
--cc=hadess@writeme.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.