mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Rene Rebe <rene.rebe@gmx.net>
Cc: linux-kernel@vger.kernel.org, alsa-devel@lists.sourceforge.net
Subject: Re: devfs unable to handle permission: 2.4.17-pre[4,5] / ALSA-0.9.0beta[9,10]
Date: Fri, 7 Dec 2001 09:41:51 -0700	[thread overview]
Message-ID: <200112071641.fB7GfpS14840@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <20011207084910.7ec3b9c3.rene.rebe@gmx.net>
In-Reply-To: <20011207003528.1448673e.rene.rebe@gmx.net> <200112070609.fB769Eo08508@vindaloo.ras.ucalgary.ca> <20011207084910.7ec3b9c3.rene.rebe@gmx.net>

Rene Rebe writes:
> On Thu, 6 Dec 2001 23:09:14 -0700
> Richard Gooch <rgooch@ras.ucalgary.ca> wrote:
> 
> > Rene Rebe writes:
> > > At least since 2.4.17-pre4 and -pre5 devfs is not handling
> > > permissions in the right way with ALSA:
[...]
> > > rene@jackson:/dev > l dsp sound/dsp 
> > > ls: sound/dsp: Permission denied
> > > lr-xr-xr-x   1 root     root            9 Dec  7 00:14 dsp -> sound/dsp
> > > rene@jackson:/dev > cd sound/
> > > bash: cd: sound/: Permission denied
> > > rene@jackson:/dev > 
> > > 
> > > rene@jackson:/dev > l snd
> > > ls: snd/..: Permission denied
> > > ls: snd/.: Permission denied
> > > ls: snd/controlC0: Permission denied
> > > ls: snd/controlC1: Permission denied
> > > ls: snd/timer: Permission denied
> > > ls: snd/midiC0D0: Permission denied
> > > ls: snd/pcmC0D2p: Permission denied
> > > ls: snd/pcmC0D1c: Permission denied
> > > ls: snd/pcmC0D0p: Permission denied
> > > ls: snd/pcmC0D0c: Permission denied
> > > ls: snd/midiC1D0: Permission denied
> > > ls: snd/pcmC1D0p: Permission denied
> > > ls: snd/pcmC1D0c: Permission denied
> > > total 0
> > > 
> > > They all have 666 (or 777 for dirs)!

Are you positive the directory has 777 permissions?

Thomas Hood may have found your problem:
> Some devfs permission problems may have arisen because of the
> fact that devfs now notifies devfsd of the creation of
> directories.  Many people have devfsd configured to set
> permissions to all devices matching a certain regular
> expression --- e.g., all devices with "sound" in their
> pathname.  The problem is that the "sound" directory itself
> matches this regular expression, and so will have its perm
> bits set exactly like the device files' perm bits---e.g.,
> with the eXamine bit cleared.  The solution is to edit the
> devfsd config so that it excludes the directory.  E.g.,
> instead of:
>     REGISTER sound PERMISSIONS root.audio 0664
> (which worked before but won't any more) do:
>     REGISTER ^sound/.* PERMISSIONS root.audio 0664
> or something similar.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  parent reply	other threads:[~2001-12-07 16:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-06 23:35 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   ` Richard Gooch [this message]
2001-12-22 22:14     ` devfs permissions Gabor Z. Papp
2001-12-23  0:11       ` 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

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=200112071641.fB7GfpS14840@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.rebe@gmx.net \
    /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®