All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Rene Rebe <rene.rebe@gmx.net>
Cc: jonathan@daria.co.uk, linux-kernel@vger.kernel.org
Subject: Re: Q: device(file) permissions for USB
Date: Thu, 6 Dec 2001 16:00:55 -0800	[thread overview]
Message-ID: <20011206160055.O2710@kroah.com> (raw)
In-Reply-To: <fa.ljcupnv.1ghotjk@ifi.uio.no> <664.3c0fd1b7.a66fa@trespassersw.daria.co.uk> <20011206223050.179cd30e.rene.rebe@gmx.net> <20011206152721.M2710@kroah.com> <20011207004521.19a131d4.rene.rebe@gmx.net>
In-Reply-To: <20011207004521.19a131d4.rene.rebe@gmx.net>

On Fri, Dec 07, 2001 at 12:45:21AM +0100, Rene Rebe wrote:
> 
> For usbfs I have to do script-hacking in /sbin/hotplug (I do not know
> how I did it since it is on my brothers box somewhere at the other
> end of Germany ... - but is was some if [$1 = "usb"]; then; chmod
> or maybe even some find /proc -name "xyz..." ...). Especially because
> I only got one parameter ($1 == usb?) the rest was empty. So even
> providing filesnames what got hot-plugged would be nice.

It's there in the DEVICE environment variable.  See
http://linux-hotplug.sourceforge.net/?selected=usb for more
documentation.

So a simple /sbin/hotplug script of:
	#!/bin/sh
	if [ "$1" == "usb" ]; then
		chmod 666 $DEVICE
	fi

would work just fine for your needs.

> Wouldn't it be nicer to use devfs and add this procfs hack for the
> "major dists"? - They could even mount devfs to /devfs and so use
> all the old-way in /dev and only use devfs for the usb stuff.

It's not a procfs hack, it is a stand alone filesystem.  The fact that
you happen to mount it within the /proc filesystem is your option.

The USB developers did not want to force people to use devfs to use USB
devices, and based on the fact that not a single distro is using devfs
(the one that did, now recommends that you disable it) backs up this
choice.

> I do not know why they adapt so slowly to such a cool technology
> anyway ...

See the numerous lkml posts about why this is so.

thanks,

greg k-h

  reply	other threads:[~2001-12-07  0:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.ljcupnv.1ghotjk@ifi.uio.no>
2001-12-06 20:14 ` Q: device(file) permissions for USB Jonathan Hudson
2001-12-06 21:30   ` Rene Rebe
2001-12-06 23:27     ` Greg KH
2001-12-06 23:37       ` Alexander Viro
2001-12-06 23:57         ` Rene Rebe
2001-12-07  0:09           ` Alexander Viro
2001-12-07  0:20             ` Rene Rebe
2001-12-07  0:21             ` Richard Gooch
2001-12-07  0:35               ` Rene Rebe
2001-12-06 23:45       ` Rene Rebe
2001-12-07  0:00         ` Greg KH [this message]
2001-12-07  0:11           ` Rene Rebe
2001-12-07  0:21             ` Greg KH
2001-12-06 20:01 kees

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=20011206160055.O2710@kroah.com \
    --to=greg@kroah.com \
    --cc=jonathan@daria.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.rebe@gmx.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.