2008/1/28, Richard Hughes <[EMAIL PROTECTED]>:
> On Sun, 2008-01-27 at 14:51 -0600, Victor Lowther wrote:
> > Minor updates to README -- /etc/pm/hooks has not existed in a long
> > time.
Please also consider the attached patch (/etc/pm/config is no longer supported)
Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
From 6b58f4f7b2c84d857438c15dddb95c9b34103645 Mon Sep 17 00:00:00 2001
From: Michael Biebl <[EMAIL PROTECTED]>
Date: Mon, 28 Jan 2008 21:52:08 +0100
Subject: [PATCH] Remove even more outdated documentation.
---
README | 14 ++++++--------
1 files changed, 6 insertions(+), 8 deletions(-)
diff --git a/README b/README
index 5d20b6d..170ffe3 100644
--- a/README
+++ b/README
@@ -30,24 +30,22 @@ How do "hooks" work?
hibernate is called, several things happen:
1) a new virtual terminal is alloced and switched to
- 2) /etc/pm/config is evaluated . This config file that should only be
- modified by end-users.
- 3) /etc/pm/config.d/* are evaluated in C sort order. These files can be
+ 2) /etc/pm/config.d/* are evaluated in C sort order. These files can be
provided by individual packages outside of pm-utils. If a global config
variable is set, the value set to will overwrite the previous value.
If any other variable is set, it will be ignored.
- 4) each of /etc/pm/sleep.d/* are executed in C sort order. The first command
+ 3) each of /etc/pm/sleep.d/* are executed in C sort order. The first command
line argument is "suspend" or "hibernate". These files may source
configuration files from /etc/pm/config.d/ on their own in order to pick
up variables set there that aren't part of the global list. Note that
hooks should take care to preserve any global configuration variable
which _that_ hook will later need to use, as sourcing this config file
will clobber any such variables.
- 5) the system suspends or hibernates.
- 6) some event happens to wake the machine up
- 7) each of /etc/pm/sleep.d/* are executed in reverse C sort order. The first
+ 4) the system suspends or hibernates.
+ 5) some event happens to wake the machine up
+ 6) each of /etc/pm/sleep.d/* are executed in reverse C sort order. The first
command line argument is "resume" or "thaw".
- 8) the system switches back to the original virtual terminal from step 1.
+ 7) the system switches back to the original virtual terminal from step 1.
That's it!
--
1.5.3.8
_______________________________________________
Pm-utils mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/pm-utils
