From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932349AbWFSKW2 (ORCPT ); Mon, 19 Jun 2006 06:22:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932350AbWFSKW2 (ORCPT ); Mon, 19 Jun 2006 06:22:28 -0400 Received: from coyote.holtmann.net ([217.160.111.169]:13197 "EHLO mail.holtmann.net") by vger.kernel.org with ESMTP id S932349AbWFSKW2 (ORCPT ); Mon, 19 Jun 2006 06:22:28 -0400 Subject: Re: [GIT PATCH] Remove devfs from 2.6.17 From: Marcel Holtmann To: Samuel Thibault Cc: Greg KH , linux-kernel@vger.kernel.org, greg@kroah.com, linux-hotplug-devel@lists.sourceforge.net In-Reply-To: <20060619093953.GI4253@implementation.labri.fr> References: <20060618221343.GA20277@kroah.com> <20060618230041.GG4744@bouh.residence.ens-lyon.fr> <20060618231204.GB2212@suse.de> <20060618233508.GH4744@bouh.residence.ens-lyon.fr> <20060619032259.GB4651@suse.de> <20060619082355.GE4253@implementation.labri.fr> <1150709431.4277.4.camel@localhost> <20060619093953.GI4253@implementation.labri.fr> Content-Type: text/plain Date: Mon, 19 Jun 2006 12:22:31 +0200 Message-Id: <1150712551.4277.13.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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