From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Greg KH <gregkh@suse.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: [GIT PATCH] Remove devfs from 2.6.17
Date: Mon, 19 Jun 2006 10:52:17 +0200 [thread overview]
Message-ID: <20060619085217.GG4253@implementation.labri.fr> (raw)
In-Reply-To: <20060619031521.GA4651@suse.de>
Greg KH, le Sun 18 Jun 2006 20:15:21 -0700, a écrit :
> On Sun, Jun 18, 2006 at 05:54:27PM -0700, H. Peter Anvin wrote:
> > It would be nice if udev could be fed not just from the kernel, but from
> > the repository of modules that are available for loading. That may
> > require additional module information.
>
> There's no reason it could not be, but usually a simple, "modprobe loop"
> works good enough for everyone :)
Not for non-root people. (And yes, they may want to do non-root things
with such virtual devices, in the dummy sequencer case for instance).
Samuel
prev parent reply other threads:[~2006-06-19 8:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 22:13 [GIT PATCH] Remove devfs from 2.6.17 Greg KH
2006-06-18 22:45 ` Michal Piotrowski
2006-06-18 23:06 ` Greg KH
2006-06-18 23:00 ` Samuel Thibault
2006-06-18 23:12 ` Greg KH
2006-06-18 23:35 ` Samuel Thibault
2006-06-19 0:48 ` Nick Piggin
2006-06-19 3:22 ` Greg KH
2006-06-19 8:23 ` Samuel Thibault
2006-06-19 9:30 ` Marcel Holtmann
2006-06-19 9:39 ` Samuel Thibault
2006-06-19 10:22 ` Marcel Holtmann
2006-06-19 0:54 ` H. Peter Anvin
2006-06-19 1:17 ` Joshua Hudson
2006-06-19 1:35 ` H. Peter Anvin
2006-06-19 5:55 ` Will Dyson
2006-06-19 7:14 ` Alexander E. Patrakov
2006-06-19 22:14 ` Daniel Barkalow
2006-06-19 22:17 ` H. Peter Anvin
2006-06-19 3:15 ` Greg KH
2006-06-19 8:52 ` Samuel Thibault [this message]
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=20060619085217.GG4253@implementation.labri.fr \
--to=samuel.thibault@ens-lyon.org \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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