From: Johannes Erdfelt <johannes@erdfelt.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Libusb-devel] udev craze: need /dev/bus/usb rationale
Date: Fri, 27 Jan 2006 02:26:15 +0000 [thread overview]
Message-ID: <20060127022615.GQ26629@sventech.com> (raw)
In-Reply-To: <20060126094517.GA4063@bode.aurel32.net>
On Fri, Jan 27, 2006, Kay Sievers <kay.sievers@vrfy.org> wrote:
> On Thu, Jan 26, 2006 at 06:08:11PM -0800, Johannes Erdfelt wrote:
> > I want to understand the reason for these device nodes since they seem
> > to duplicate the nodes found in /proc/bus/usb. Is this just part of the
> > long term plans to remove usbdevfs?
>
> Yes, we want to leave /proc with all stuff that isn't process related.
> And as all the major distros depend on udev and have /dev on tmpfs, having
> usb devices in /proc makes no sense anymore.
>
> We also want the option to apply access control lists to device nodes,
> to allow a set of users (fast-user-switching) access to a device and
> this would not work with /proc files, which can only have primary
> ownership.
Ahh, sounds great. I've checked in the change to CVS. It will only check
/dev/bus/usb and /proc/bus/usb now, in that order.
I haven't seen any of the conversations about this, but what will happen
to /proc/bus/usb/devices?
Unrelated, but I may make a 0.1.12 release sometime soon because there
have been a surprising amount of changes since 0.1.11 was released.
JE
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
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:[~2006-01-27 2:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 9:45 [Libusb-devel] udev craze: need /dev/bus/usb rationale Aurelien Jarno
2006-01-26 10:16 ` Linus Walleij
2006-01-27 2:08 ` Johannes Erdfelt
2006-01-27 2:17 ` Kay Sievers
2006-01-27 2:25 ` Greg KH
2006-01-27 2:26 ` Johannes Erdfelt [this message]
2006-01-27 3:01 ` Kay Sievers
2006-01-27 3:17 ` Greg KH
2006-01-27 3:38 ` Charles Lepple
2006-01-27 3:51 ` Kay Sievers
2006-01-27 3:53 ` Kay Sievers
2006-01-27 4:01 ` Andrey Borzenkov
2006-01-27 4:05 ` Andrey Borzenkov
2006-01-27 4:11 ` Kay Sievers
2006-01-27 4:20 ` Greg KH
2006-01-27 4:21 ` Greg KH
2006-01-27 4:23 ` Greg KH
2006-01-27 7:50 ` Linus Walleij
2006-01-27 11:56 ` Olivier Blin
2006-01-27 17:04 ` David Zeuthen
2006-01-27 17:15 ` Olivier Blin
2006-01-27 17:28 ` Darren Salt
2006-01-27 17:33 ` Bill Nottingham
2006-01-27 19:29 ` Johannes Erdfelt
2006-01-27 19:39 ` Linus Walleij
2006-01-27 19:44 ` Johannes Erdfelt
2006-01-27 20:45 ` Greg KH
2006-01-28 0:12 ` Greg KH
2006-02-06 23:29 ` Johannes Erdfelt
2006-02-06 23:53 ` Greg KH
2006-02-07 0:00 ` Johannes Erdfelt
2006-02-07 0:23 ` Greg KH
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=20060127022615.GQ26629@sventech.com \
--to=johannes@erdfelt.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).