mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rene Rebe <rene.rebe@gmx.net>
To: Alexander Viro <viro@math.psu.edu>
Cc: greg@kroah.com, jonathan@daria.co.uk,
	linux-kernel@vger.kernel.org,
	Clifford Wolf <clifford@clifford.at>,
	Valentin Ziegler <ziegler@informatik.hu-berlin.de>
Subject: Re: Q: device(file) permissions for USB
Date: Fri, 7 Dec 2001 01:20:37 +0100	[thread overview]
Message-ID: <20011207012037.71556cb0.rene.rebe@gmx.net> (raw)
In-Reply-To: <Pine.GSO.4.21.0112061903230.29985-100000@binet.math.psu.edu>
In-Reply-To: <20011207005707.6a09706a.rene.rebe@gmx.net> <Pine.GSO.4.21.0112061903230.29985-100000@binet.math.psu.edu>

On Thu, 6 Dec 2001 19:09:57 -0500 (EST)
Alexander Viro <viro@math.psu.edu> wrote:

> On Fri, 7 Dec 2001, Rene Rebe wrote:
> 
> > > > usbdevfs does not require devfs, which enables the majority of Linux
> > > > users to actually use it.
> > > 
> > > s/majority of/& sane/
> > 
> > Writing bash scripts is easier than adding two lines to devfsd.conf?? Btw.
> > sane users do not use such a mahor/messy distro ...
> 
> Sane users don't run stuff with known unfixable security holes.  The only
> variant that has any promise to get that crap fixed got no testing to
> speak about.

Hm. OK. Due to lag of time I was too long not on the mailing-list. :-(
I this is true it is a very strong point aganst devfs :-[[

> Ask Richard if you don't believe me - or grep the l-k archives.  Again,
> all variants of devfs up to and including 2.4.16 are unfixable according
> to devfs author.

Hm.

> BTW, which distro are you talking about?

ROCK Linux (www.rocklinux.org)

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.

  parent reply	other threads:[~2001-12-07  0:20 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 [this message]
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
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=20011207012037.71556cb0.rene.rebe@gmx.net \
    --to=rene.rebe@gmx.net \
    --cc=clifford@clifford.at \
    --cc=greg@kroah.com \
    --cc=jonathan@daria.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    --cc=ziegler@informatik.hu-berlin.de \
    /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®