linux-hotplug.vger.kernel.org archive mirror
 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@vger.kernel.org
Subject: Re: [GIT PATCH] Remove devfs from 2.6.17
Date: Mon, 19 Jun 2006 09:30:31 +0000	[thread overview]
Message-ID: <1150709431.4277.4.camel@localhost> (raw)
In-Reply-To: <20060619082355.GE4253@implementation.labri.fr>

Hi Samuel,

> > Or just tell your users to make sure that they have the uinput driver
> > loaded,
> 
> 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.

Regards

Marcel



_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2006-06-19  9:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060618221343.GA20277@kroah.com>
     [not found] ` <20060618230041.GG4744@bouh.residence.ens-lyon.fr>
     [not found]   ` <20060618231204.GB2212@suse.de>
     [not found]     ` <20060618233508.GH4744@bouh.residence.ens-lyon.fr>
     [not found]       ` <20060619032259.GB4651@suse.de>
2006-06-19  8:23         ` [GIT PATCH] Remove devfs from 2.6.17 Samuel Thibault
2006-06-19  9:30           ` Marcel Holtmann [this message]
2006-06-19  9:39             ` Samuel Thibault
2006-06-19 10:22               ` Marcel Holtmann

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=1150709431.4277.4.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-hotplug-devel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).