From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: Patrick Mochel <mochel-3NddpPZAyC0@public.gmane.org>
Cc: Erik van Pienbroek
<admin-0LxUhLuGNoZIf6P1QZMOBw@public.gmane.org>,
ACPI Mailinglist
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: Re: System hang when trying to enter sleep/standby state
Date: Wed, 12 Feb 2003 21:36:37 +0100 [thread overview]
Message-ID: <20030212203637.GA32274@hell.org.pl> (raw)
In-Reply-To: <Pine.LNX.4.33.0302121042480.1479-100000-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
Thus wrote Patrick Mochel:
> ACPI should not allow a user to write '5' to that file. It used to be that
> way, but someone clever decided that that interface should support _all_
> sleep states. (It might have been me, in one of my finer moments).
May I ask: why? Is it really dangerous to leave it like it is now? Does it
break anything? I actually used it a couple of times, not bothering to hold
my poweroff button for the time needed to poweroff the machine completely.
As for potential dangers, I see many other ways of using the /proc
interface that can be really *much* more harmful to the system, yet they
don't cease to exist. However confusing it might be now, it is fully
functional, at least. I can't really see any reason for crippling that
functionality. Please, do leave it the way it is.
Gosh, where's my manners... I hereby say hello to everyone. Hope you don't
take the above too personal or whatever, I'm a newbie to ACPI and I might
as well miss the whole point there.
Regards,
--
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-02-12 20:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-08 15:41 System hang when trying to enter sleep/standby state Erik van Pienbroek
[not found] ` <026401c2cf88$9b26d330$0a0110ac-QyX2VyNvpUU@public.gmane.org>
2003-02-08 16:19 ` Jean-Pierre Schwickerath
2003-02-08 18:59 ` Pavel Machek
[not found] ` <02bc01c2d030$ac23f340$0a0110ac@erik>
[not found] ` <20030209114731.GD26151@atrey.karlin.mff.cuni.cz>
[not found] ` <20030209114731.GD26151-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org>
2003-02-11 18:10 ` Erik van Pienbroek
[not found] ` <1044987042.1149.4.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2003-02-12 16:47 ` Patrick Mochel
[not found] ` <Pine.LNX.4.33.0302121042480.1479-100000-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2003-02-12 20:36 ` Karol Kozimor [this message]
[not found] ` <20030212203637.GA32274-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-02-12 21:08 ` Patrick Mochel
-- strict thread matches above, loose matches on Subject: below --
2003-02-13 6:59 Jens Haug
[not found] ` <200302130659.h1D6x7D22714-sBhUd1W9t4xfrO0PeCDDO4ECbGbo6+O1OOFObY0sJ7w@public.gmane.org>
2003-02-13 16:01 ` Patrick Mochel
2003-02-13 16:28 Jens Haug
[not found] ` <200302131628.h1DGSID27482-sBhUd1W9t4xfrO0PeCDDO4ECbGbo6+O1OOFObY0sJ7w@public.gmane.org>
2003-02-13 16:46 ` Patrick Mochel
[not found] ` <Pine.LNX.4.33.0302131031290.1133-100000-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2003-02-13 21:32 ` Karol Kozimor
2003-02-13 22:09 ` Pavel Machek
2003-02-13 19:00 ` Darren Benham
[not found] ` <51181.64.164.111.5.1045162852.squirrel-FG1iuTdj8bisTnJN9+BGXg@public.gmane.org>
2003-02-13 19:02 ` Matthew Wilcox
2003-02-14 7:50 Jens Haug
2003-02-14 7:53 Jens Haug
[not found] ` <200302140753.h1E7rOD00889-sBhUd1W9t4xfrO0PeCDDO4ECbGbo6+O1OOFObY0sJ7w@public.gmane.org>
2003-02-14 14:38 ` Patrick Mochel
[not found] ` <Pine.LNX.4.33.0302140836140.1067-100000-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2003-02-17 5:40 ` Christian Zoz
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=20030212203637.GA32274@hell.org.pl \
--to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=admin-0LxUhLuGNoZIf6P1QZMOBw@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=mochel-3NddpPZAyC0@public.gmane.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