On 1/19/07, Alessandro Di Marco <[EMAIL PROTECTED]> wrote:
The patch in attachment fixes some silly bugs of the previous version.
Regards,
Hi, attached is a patch for your gentable file, rewriting some of the
user prompts to make them more readable.
Regards,
scott
--- gentable 2007-01-19 11:39:28.000000000 -0600
+++ gentable-new 2007-01-19 11:39:28.000000000 -0600
@@ -31,9 +31,9 @@
cat <<EOF
-SIN wakes up periodically and checks for user activity occurred in the
-meantime; this options lets you to specify how much frequently SIN should be
-woken-up. Its value is expressed in tenth of seconds.
+SIN wakes up periodically and checks whether user activity has occurred
+since it last ran; the next option lets you to specify how frequently
+SIN should wake up. Its value is expressed in tenth of seconds.
EOF
@@ -45,9 +45,9 @@
cat <<EOF
-Asleep or not, SIN constantly monitors the input devices searching for user
-activity. This option lets you choose which device have to be monitored. At
-least one device is needed and please avoid the duplicates.
+Asleep or not, SIN constantly monitors the input devices watching for user
+activity. The next option lets you choose which device have to be monitored.
+You must specify at least one device and must not specify duplicates.
EOF
@@ -65,7 +65,7 @@
cat <<EOF
-SIN produces ACPI events depending on the user activity. To do this you have to
+SIN produces ACPI events depending on the user activity. You must
specify a suitable handler that will be used as originator.
EOF
@@ -74,7 +74,7 @@
cat /proc/sin/acpi
echo
-input "Please digit the corresponding number" handle
+input "Please enter the number corresponding to the handler" handle
if [ -z "${handle}" ]; then
handle="0"
@@ -82,19 +82,19 @@
cat <<EOF
-SIN produces events in base to rules. Each rule is a triple composed by a
-"counter", a "type" and a "data". Once awaken, a global counter is increased if
-SIN detects no user activity and reset to zero, otherwise. When this global
-counter reaches the value specified in the counter field of a rule, an event is
-generated with the corresponding "type" and "data". Clearly, different rules
-should have different "type" and "data" fields to convey different signals to
-the user space daemon.
+SIN produces events based on rules. Each rule is a triple composed by a
+"counter", a "type", and a "data" value. When SIN awakens, a global counter
+is increased if SIN detects no user activity and reset to zero, otherwise.
+When this global counter reaches the value specified in the counter field
+of a rule, an event is generated with the corresponding "type" and "data".
+Different rules should have different "type" and "data" fields to convey
+different signals to the user space daemon.
For example, the rule "60 1 19" produces the ACPI event "XXXX 00000001
-00000019" right after one minute of user inactivity (assuming pace=10.)
+00000019" when SIN recognizes one minute of user inactivity (assuming pace=10.)
-Please specify each rule as a space-separated triple; to finish just press
-enter.
+Please specify each rule as a space-separated triple on a separate line;
+when finished, just press enter.
EOF
@@ -114,9 +114,9 @@
cat <<EOF
-A special event has been provided to better help those of us who wanna use SIN
+A special event has been provided to simplify using SIN
as a screen-blanker. It will be generated as soon as some user activity is
-detected, but only after one or more rule have been triggered.
+detected, but only after one or more rules have been triggered.
EOF
@@ -128,16 +128,16 @@
cat <<EOF
-Usually a rule-list terminates with dead-end actions such as suspend or
-hibernate, requiring the user interaction to wake-up the system. Unfortunately
-this activity occurs when SIN, as well as the kernel, are not ready to capture
-these events yet. As a consequence, no special event will ever be generated and
+Often an SIN event results in suspending or hibernating the system,
+hibernate, requiring user interaction to wake-up the system. Unfortunately
+that interaction occurs when SIN, as well as the kernel, cannot capture
+it. As a consequence, no event will ever be generated and
the system will remain in the state associated with the next-to-last rule
-(e.g. blanked screen, wireless powered off, etc.) In such cases this field
-forces the special event generation, resetting simultaneously the global
-counter to an arbitrary value, so to reinstate the rule-list evaluation to the
-beginning. Possible value ranges are described below, where N is the maximum
-counter in the rule list:
+(e.g. blanked screen, wireless powered off, etc.). The next option
+allows you to request a special event, resetting the global
+counter to an arbitrary value, so to restart the rule-list evaluation.
+Possible value ranges are described below, where N is the maximum
+counter in the current rule list:
[0, N] => reset the global counter to the specified value
otherwise => do nothing, the global counter goes on and on and on...
@@ -163,8 +163,8 @@
# modprobe sinmod
# echo $1 >/proc/sin/table
-An "Invalid argument" error signals a mismatch in the table file, usually due
-to wrong acpi or input device specified. In these cases restart from scratch
-double checking your answers. Have fun!
+An "Invalid argument" error indicates a mismatch in the table file, usually
+due to specifying an invalid acpi or input device. In that case, restart from
+scratch, double checking your inputs. Have fun!
EOF
