From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] udev - add %s{filename} to man page
Date: Tue, 17 Feb 2004 18:47:02 +0000 [thread overview]
Message-ID: <20040217184702.GA7726@vrfy.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 120 bytes --]
Add the new %s{filename} to the udev man page.
And add the automatic start of udevd to the udevd man page.
thanks,
Kay
[-- Attachment #2: 01-add-s-format-to-man-page.patch --]
[-- Type: text/plain, Size: 1200 bytes --]
===== udev.8 1.39 vs edited =====
--- 1.39/udev.8 Tue Feb 17 02:26:34 2004
+++ edited/udev.8 Tue Feb 17 19:39:30 2004
@@ -195,6 +195,13 @@
(This does not work within the
.B PROGRAM
field for the obvious reason.)
+.br
+A single part of the string, separated by the space character
+my be selected by specifying the part number as a attribute:
+.BI %c{ part }
+.TP
+.BI %s{ filename }
+The content of a sysfs attribute.
.TP
.B %%
The '%' char itself.
===== udevd.8 1.1 vs edited =====
--- 1.1/udevd.8 Tue Feb 17 04:09:57 2004
+++ edited/udevd.8 Tue Feb 17 19:30:47 2004
@@ -20,16 +20,20 @@
.BR udev (8)
instance is executed in the background. All further events for the same device
are delayed until the execution is finished. This way it will never run more
-than one instance for a single device.
+than one instance for a single device at the same time.
.br
.B udevd
receives the events from
.B udevsend
which is called by
-.BR hotplug (8)
-
+.BR hotplug (8).
+If
+.B udevd
+isn't already running,
+.B udevsend
+will start it.
.SH "SEE ALSO"
-.BR udev (8)
+.BR udev (8), hotplug (8)
.SH AUTHORS
.B udevd
was developed primarily by Kay Sievers <kay.sievers@vrfy.org>, with much help
next reply other threads:[~2004-02-17 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 18:47 Kay Sievers [this message]
2004-02-17 19:03 ` [PATCH] udev - add %s{filename} to man page Greg KH
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=20040217184702.GA7726@vrfy.org \
--to=kay.sievers@vrfy.org \
--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 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.