From: Phillip Susi <psusi@cfl.rr.com>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] Fix typo in udev man page
Date: Mon, 05 Mar 2007 21:06:14 +0000 [thread overview]
Message-ID: <11731287743253-git-send-email-psusi@cfl.rr.com> (raw)
The udev man page said that a PROGRAM rule is true if the program
returned _without_ an exit code of 0. This is backwards. The
program returns _with_ exit code 0 to indicate success, and thus
the rule is true.
---
udev.7 | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/udev.7 b/udev.7
index 7dd3c1f..13f3356 100644
--- a/udev.7
+++ b/udev.7
@@ -153,7 +153,7 @@ keys can be specified per rule. Dependin
.PP
\fBPROGRAM\fR
.RS 4
-Execute external program. The key is true, if the program returns without exit code zero. The whole event environment is available to the executed program. The program's output printed to stdout is available for the RESULT key.
+Execute external program. The key is true, if the program returns with exit code zero. The whole event environment is available to the executed program. The program's output printed to stdout is available for the RESULT key.
.RE
.PP
\fBRESULT\fR
--
1.4.1
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2007-03-05 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 21:06 Phillip Susi [this message]
2007-03-05 23:44 ` [PATCH] Fix typo in udev man page Bryan Kadzban
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=11731287743253-git-send-email-psusi@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=linux-hotplug@vger.kernel.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).