All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] udev - udevd/udevsend man page
Date: Tue, 17 Feb 2004 02:20:11 +0000	[thread overview]
Message-ID: <20040217022011.GA5949@vrfy.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 117 bytes --]

Here is the missing man page for udevd/udevsend.

Hey, I get a beer now, this is my 100th udev patch :)

thanks,
Kay

[-- Attachment #2: 01-man-udevd.patch --]
[-- Type: text/plain, Size: 2082 bytes --]

diff -Nru a/Makefile b/Makefile
--- a/Makefile	Tue Feb 17 03:09:57 2004
+++ b/Makefile	Tue Feb 17 03:09:57 2004
@@ -361,6 +361,8 @@
 	fi
 	$(INSTALL_DATA) -D udev.8 $(DESTDIR)$(mandir)/man8/udev.8
 	$(INSTALL_DATA) -D udevinfo.8 $(DESTDIR)$(mandir)/man8/udevinfo.8
+	$(INSTALL_DATA) -D udevd.8 $(DESTDIR)$(mandir)/man8/udevd.8
+	- ln -f -s ./udevd.8 $(DESTDIR)$(mandir)/man8/udevsend.8
 	- rm -f $(DESTDIR)$(hotplugdir)/$(ROOT).hotplug
 	- rm -f $(udevdir)/.udev.tdb
 	- ln -f -s $(sbindir)/$(SENDER) $(DESTDIR)$(hotplugdir)/$(ROOT).hotplug
diff -Nru a/udevd.8 b/udevd.8
--- /dev/null	Wed Dec 31 16:00:00 1969
+++ b/udevd.8	Tue Feb 17 03:09:57 2004
@@ -0,0 +1,36 @@
+.TH UDEVD 8 "February 2004" "" "Linux Administrator's Manual"
+.SH NAME
+udevd \- udev event serializer daemon
+.br
+udevsend \- sends the event to udevd
+.SH "DESCRIPTION"
+.B udevd
+allows the serialization of
+.BR hotplug (8)
+events. The events generated by the kernel may arrive in random order
+in userspace, that makes it neccessary to reorder it.
+.br
+.B udevd
+takes care of the kernel supplied sequence number and arranges the events for
+execution in the correct order. Missing sequences are delaying the
+execution of the following events until a timeout of a maximum of 5 seconds
+is reached.
+.br
+For each event a
+.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.
+.br
+.B udevd
+receives the events from
+.B udevsend
+which is called by
+.BR hotplug (8)
+
+.SH "SEE ALSO"
+.BR udev (8)
+.SH AUTHORS
+.B udevd
+was developed primarily by Kay Sievers <kay.sievers@vrfy.org>, with much help
+from others.
diff -Nru a/udevinfo.8 b/udevinfo.8
--- a/udevinfo.8	Tue Feb 17 03:09:57 2004
+++ b/udevinfo.8	Tue Feb 17 03:09:57 2004
@@ -1,4 +1,4 @@
-.TH UDEVINFO 8 "October 2003" "" "Linux Administrator's Manual"
+.TH UDEVINFO 8 "January 2004" "" "Linux Administrator's Manual"
 .SH NAME
 udevinfo \- retrieve information from udev
 .SH SYNOPSIS

             reply	other threads:[~2004-02-17  2:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17  2:20 Kay Sievers [this message]
2004-02-17 19:00 ` [PATCH] udev - udevd/udevsend man page Greg KH
2004-02-17 19:50 ` Kay Sievers
2004-02-18 18:04 ` Greg KH
2004-02-18 19:07 ` Kay Sievers
2004-02-18 19:20 ` 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=20040217022011.GA5949@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.