From: Enno Fennema <e.fennema@tiscali.nl>
To: linux-hotplug@vger.kernel.org
Subject: Incomplete man page udev
Date: Fri, 09 Nov 2007 13:41:25 +0000 [thread overview]
Message-ID: <47346385.8070209@tiscali.nl> (raw)
Recently I update to Linux 2.6 and find major changes to udev.
Unfortunately the udev manpage provided with SuSE 10.3 appears broken.
The last line I get is
...
The following keys can get values assigned:
EOF
The internet is awash with udev man pages but most of them for older
versions. Where can I get an up to date one?
Thanks,
Enno Fennema
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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-11-09 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 13:41 Enno Fennema [this message]
2007-11-09 14:05 ` Incomplete man page udev Kay Sievers
2007-11-09 14:14 ` Enno Fennema
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=47346385.8070209@tiscali.nl \
--to=e.fennema@tiscali.nl \
--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.