From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: ACLs in udev-add.c?
Date: Fri, 09 Apr 2004 18:51:19 +0000 [thread overview]
Message-ID: <20040409185119.GA17057@kroah.com> (raw)
In-Reply-To: <1081478175.18546.1397.camel@matt>
On Thu, Apr 08, 2004 at 08:36:15PM -0600, Matthew Mastracci wrote:
> I'm curious about what sort of work might be required to change
> udev-add.c to support filesystem ACLs.
>
> I'd like to have each of my console-type devices have an ACL list sync'd
> with the currently logged-in users. I run X on two consoles with two
> different users and the permissions are currently a pain to maintain.
>
> I don't mind getting my hands dirty in udev, but it looks like the
> udevice structure would need to be extended to support multiple owners
> (but only on udev storage that supports it).
>
> Is this a reasonable thing to have in udev, or should it be part of the
> hotplug scripts?
It could go in udev, or as a script/program that udev calls after it
runs. See the /etc/dev.d framework for more info on this. Just plop a
program down in /etc/dev.d/default/ with the extension .dev and it will
always be called. See my previous announcements for full details.
Hope this helps,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
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
prev parent reply other threads:[~2004-04-09 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-09 2:36 ACLs in udev-add.c? Matthew Mastracci
2004-04-09 18:51 ` Greg KH [this message]
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=20040409185119.GA17057@kroah.com \
--to=greg@kroah.com \
--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).