From: "Gabor Z. Papp" <gzp@myhost.mynet>
To: linux-kernel@vger.kernel.org
Subject: devfs permissions
Date: Sat, 22 Dec 2001 22:14:42 GMT [thread overview]
Message-ID: <27e4.3c2505d3.14a5@gzp1.gzp> (raw)
In-Reply-To: <20011207084910.7ec3b9c3.rene.rebe@gmx.net> <20011207003528.1448673e.rene.rebe@gmx.net> <200112070609.fB769Eo08508@vindaloo.ras.ucalgary.ca> <20011207084910.7ec3b9c3.rene.rebe@gmx.net> <200112071641.fB7GfpS14840@vindaloo.ras.ucalgary.ca>
* Richard Gooch <rgooch@ras.ucalgary.ca>:
|> (which worked before but won't any more) do:
|> REGISTER ^sound/.* PERMISSIONS root.audio 0664
|> or something similar.
And what about subdirs, like in case of /dev/ide/...
REGISTER ^ide/.* PERMISSIONS root.disk 0660
sets the permission 0660 on /dev/ide/host0/ also.
next prev parent reply other threads:[~2001-12-22 22:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 23:35 devfs unable to handle permission: 2.4.17-pre[4,5] / ALSA-0.9.0beta[9,10] Rene Rebe
2001-12-07 6:09 ` Richard Gooch
2001-12-07 15:22 ` Roman Zippel
2001-12-07 15:59 ` Richard Gooch
2001-12-07 19:17 ` devfs unable to handle permission: 2.4.17-pre[4,5] /ALSA-0.9.0beta[9,10] Roman Zippel
2001-12-07 20:08 ` Richard Gooch
2001-12-07 20:37 ` Roman Zippel
2001-12-09 3:08 ` Richard Gooch
2001-12-09 4:02 ` Roman Zippel
2001-12-09 4:48 ` Richard Gooch
2001-12-09 14:44 ` Roman Zippel
2001-12-09 19:45 ` Marcelo Tosatti
2001-12-09 21:26 ` Richard Gooch
2001-12-09 22:26 ` Roman Zippel
2001-12-09 21:20 ` Marcelo Tosatti
2001-12-10 0:11 ` Richard Gooch
2001-12-09 23:00 ` Marcelo Tosatti
2001-12-09 23:03 ` Marcelo Tosatti
2001-12-07 16:41 ` devfs unable to handle permission: 2.4.17-pre[4,5] / ALSA-0.9.0beta[9,10] Richard Gooch
2001-12-22 22:14 ` Gabor Z. Papp [this message]
2001-12-23 0:11 ` devfs permissions Pozsar Balazs
2001-12-07 7:49 ` devfs unable to handle permission: 2.4.17-pre[4,5] / ALSA-0.9.0beta[9,10] Rene Rebe
2001-12-10 10:46 ` [Alsa-devel] " Takashi Iwai
2001-12-23 0:13 devfs permissions Pozsar Balazs
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=27e4.3c2505d3.14a5@gzp1.gzp \
--to=gzp@myhost.mynet \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®