public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, greg@kroah.com,
	linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [GIT PATCH] Remove devfs from 2.6.17
Date: Mon, 19 Jun 2006 12:22:31 +0200	[thread overview]
Message-ID: <1150712551.4277.13.camel@localhost> (raw)
In-Reply-To: <20060619093953.GI4253@implementation.labri.fr>

Hi Samuel,

> > > They can't, since without it they can't even type things.
> > 
> > if you install a program or a driver that needs uinput loaded, then you
> > have a clean requirement. So simply add a "modprobe uinput" to its init
> > script.
> > 
> > Look at the TUN/Tap driver which has the same problem. The boot up
> > scripts of various daemons (for example OpenVPN etc.) are making sure
> > that the driver is loaded.
> 
> And vtun's script in debian doesn't, so that I had to load it by hand.
> Don't justify lack of support thanks to corrections that people had to
> add ;)
> 
> The problem I'm raising is that with udev we seem to be heading to
> asking every program to know which module it should load by hand before
> being able to use a /dev entry. This looks odd to me (why not opening
> the /dev entry itself shouldn't autoload the driver?).

I don't see any problems that every program knows what kernel module it
requires. In case of misc character devices with dynamic minor numbers,
I would actually prefer that the application or an init scripts triggers
the module loading. Unless the module is loaded, the kernel doesn't know
anything about this device.

Regards

Marcel



  reply	other threads:[~2006-06-19 10:22 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 [this message]
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

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=1150712551.4277.13.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samuel.thibault@ens-lyon.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