linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: [udev] man page with udev.permissions wildcard
Date: Wed, 19 Nov 2003 12:55:45 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-106924906701698@msgid-missing> (raw)

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

Hi Greg,
here is the permissions wildcard text for the man page.
Oh, my queue is emtpy now. I have to look at the TODO in the next few days :)

thanks,
Kay


07-udev.8-perissions-wildcard.diff
  man page - mention wildcard support in udev.permissions

[-- Attachment #2: 07-udev.8-perissions-wildcard.diff --]
[-- Type: text/plain, Size: 734 bytes --]

--- ../udev/udev.8	2003-11-19 12:56:50.000000000 +0100
+++ udev.8	2003-11-19 13:42:56.000000000 +0100
@@ -116,13 +116,16 @@
 The file consists of a set of lines. All empty lines and
 lines beginning with a '#' will be ignored.
 .br
-Every line lists a device name followed by owner, group and permission mode. All values are separated by colons.
+Every line lists a device name followed by numeric owner, group and permission
+mode. All values are separated by colons. The name field may end with a
+wildcard to apply the values to a whole class of devices.
 .sp
 A sample \fIudev.permissions\fP might look like this:
 .sp
 .nf
 #name:user:group:mode
-ttyUSB1:root:uucp:0666
+ttyUSB1:0:8:0660
+video*:500:500:0660
 dsp1:::0666
 .fi
 

             reply	other threads:[~2003-11-19 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 12:55 Kay Sievers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-20 18:41 [udev] man page with udev.permissions wildcard 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=marc-linux-hotplug-106924906701698@msgid-missing \
    --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 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).