From: Rene Rebe <rene.rebe@gmx.net>
To: Greg KH <greg@kroah.com>
Cc: jonathan@daria.co.uk, linux-kernel@vger.kernel.org
Subject: Re: Q: device(file) permissions for USB
Date: Fri, 7 Dec 2001 01:11:34 +0100 [thread overview]
Message-ID: <20011207011134.04c2a4af.rene.rebe@gmx.net> (raw)
In-Reply-To: <20011206160055.O2710@kroah.com>
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> <20011206160055.O2710@kroah.com>
On Thu, 6 Dec 2001 16:00:55 -0800
Greg KH <greg@kroah.com> wrote:
Ok I did not searched this far. But this way you also change the nodes for
USB hard-discs, net-interfaces, ... to 666 - the same insecure as my find
solotion ...
> So a simple /sbin/hotplug script of:
> #!/bin/sh
> if [ "$1" == "usb" ]; then
> chmod 666 $DEVICE
> fi
>
> would work just fine for your needs.
> 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.
Yes my mistake - sorry.
> 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.
OK. Might be well for backward-compatibility - but the devfs solution
would be a very nice option.
> > 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.
We at ROCK linux (www.rocklinux) use it for years - and never had a
problem (maybe some have - because they use the www.ibm.org/linu-docs-somewhere
approach of taring them on shutdown and untar it on bootup. Using devfsd.conf
is hust fine! (I'll try to search the archive for devfs posts ...)
> thanks,
>
> greg k-h
k33p h4ck1n6
René
--
René Rebe (Registered Linux user: #248718 <http://counter.li.org>)
eMail: rene.rebe@gmx.net
rene@rocklinux.org
Homepage: http://www.tfh-berlin.de/~s712059/index.html
Anyone sending unwanted advertising e-mail to this address will be
charged $25 for network traffic and computing time. By extracting my
address from this message or its header, you agree to these terms.
next prev parent reply other threads:[~2001-12-07 0:11 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 ` 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:35 ` Rene Rebe
2001-12-07 0:20 ` Rene Rebe
2001-12-07 0:21 ` Richard Gooch
2001-12-06 23:45 ` Rene Rebe
2001-12-07 0:00 ` Greg KH
2001-12-07 0:11 ` Rene Rebe [this message]
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=20011207011134.04c2a4af.rene.rebe@gmx.net \
--to=rene.rebe@gmx.net \
--cc=greg@kroah.com \
--cc=jonathan@daria.co.uk \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®