From: Martin Schlemmer <azarah@gentoo.org>
To: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
Cc: Pavel Roskin <proski@gnu.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.5.68-bk1 crash in devfs_remove() for defpts files
Date: 24 Apr 2003 09:39:18 +0200 [thread overview]
Message-ID: <1051169958.3604.2619.camel@workshop.saharact.lan> (raw)
In-Reply-To: <1050957875.1224.2.camel@flat41>
On Mon, 2003-04-21 at 22:44, Grzegorz Jaskiewicz wrote:
> to use devfs only, it is funny but fe to open /dev/sound/* you need to
> be root, or chmod it manually before use. (i've got seperate
> /etc/init.d/chdevfsmod file to do that)
>
Add to /etc/devfsd.conf:
-----------------------------
REGISTER sound/.* PERMISSIONS root.audio 660
REGISTER snd/.* PERMISSIONS root.audio 660
-----------------------------
Or whatever perms you wish ...
Regards,
--
Martin Schlemmer
next prev parent reply other threads:[~2003-04-24 7:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 17:49 [PATCH] 2.5.68-bk1 crash in devfs_remove() for defpts files Pavel Roskin
2003-04-21 17:55 ` Christoph Hellwig
2003-04-21 17:58 ` Christoph Hellwig
2003-04-21 18:53 ` Pavel Roskin
2003-04-21 19:00 ` Christoph Hellwig
2003-04-21 19:44 ` Pavel Roskin
2003-04-21 19:56 ` Christoph Hellwig
2003-04-21 20:35 ` Pavel Roskin
2003-04-21 20:44 ` Grzegorz Jaskiewicz
2003-04-21 20:56 ` Pavel Roskin
2003-04-24 7:39 ` Martin Schlemmer [this message]
2003-04-24 7:57 ` Grzegorz Jaskiewicz
2003-04-24 11:46 ` Martin Schlemmer
2003-04-24 12:03 ` Grzegorz Jaskiewicz
2003-04-21 20:57 ` Christoph Hellwig
2003-04-21 21:15 ` Pavel Roskin
2003-04-21 21:23 ` Christoph Hellwig
2003-04-21 21:45 ` Pavel Roskin
2003-04-21 22:25 ` Christoph Hellwig
2003-04-21 22:37 ` Pavel Roskin
-- strict thread matches above, loose matches on Subject: below --
2003-04-22 10:12 Chuck Ebbert
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=1051169958.3604.2619.camel@workshop.saharact.lan \
--to=azarah@gentoo.org \
--cc=gj@pointblue.com.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.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