From: Scott Cuyle Fritzinger <scottf@med.unr.edu>
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug ownership/permissions
Date: Tue, 04 Dec 2001 17:51:13 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100748822419800@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100741069725050@msgid-missing>
On Tue, 4 Dec 2001, Tim Waugh wrote:
> On Mon, Dec 03, 2001 at 04:05:26PM -0800, David Brownell wrote:
> > > here's the logic behind this: by running every matching map entry's
> > > module/script, we can guarantee that a single script won't hog the device.
> > > the usb.agent will set owner/perms AFTER every script has run so that the
> > > perms are guaranteed.
> >
> > I'm missing something here. Suppose two different apps want to
> > assign the device to two different users? One's on the console,
> > another's on a remote X display (or SSH)?
>
> I think that for the vast majority of cases, console-user permissions
> are desired.
definitely. in the case of system discs (mounted USB discs), you may want
different permissions (root:root), but for most 'personal' peripherals,
you'd want ownership to be that of the console user.
-=Scott
_______________________________________________
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:[~2001-12-04 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 20:07 hotplug ownership/permissions Scott Cuyle Fritzinger
2001-12-03 23:28 ` Scott Cuyle Fritzinger
2001-12-04 0:05 ` David Brownell
2001-12-04 7:33 ` Tim Waugh
2001-12-04 17:51 ` Scott Cuyle Fritzinger [this message]
2001-12-04 22:46 ` David Brownell
2001-12-04 22:59 ` Scott Cuyle Fritzinger
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=marc-linux-hotplug-100748822419800@msgid-missing \
--to=scottf@med.unr.edu \
--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).