From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and access control lists
Date: Thu, 06 Jan 2005 01:38:46 +0000 [thread overview]
Message-ID: <1104975527.4734.34.camel@localhost.localdomain> (raw)
In-Reply-To: <41DC6816.30801@mathematica.scientia.net>
On Wed, 2005-01-05 at 23:20 +0100, Christoph Anton Mitterer wrote:
> I'd like to set some ACLs one some devicefiles so I tried the
> following (of course with uid 0 ;-) ):
> $ setfacl -m u:cam:r /dev/hdc
> setfacl: /dev/hdc: Operation not supported
> According to mount's output I thought that my /dev/ is mounted on a
> tmpfs filesystem. Is this the case?
Yes, seems so.
> So I looked through the kernel-config an found EAs for tmpfs but not
> ACLs... :-(
> Is it under development or is there another solution?
I don't think so. EA's were just recently added to support SELinux.
Seems you need to use a different filesystem for ACL's.
> By the way,.. is it possible to configure udev in such a way that it
> automatically sets ACLs?
You can create a dev.d/ script which is called on node creation time to
do this.
Kay
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
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 prev parent reply other threads:[~2005-01-06 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 22:20 udev and access control lists Christoph Anton Mitterer
2005-01-06 1:38 ` Kay Sievers [this message]
2005-01-06 11:52 ` Christoph Anton Mitterer
2005-01-06 12:10 ` Christoph Anton Mitterer
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=1104975527.4734.34.camel@localhost.localdomain \
--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).