From: "H. Peter Anvin" <hpa@zytor.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Greg KH <gregkh@suse.de>, 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: Sun, 18 Jun 2006 17:54:27 -0700 [thread overview]
Message-ID: <4495F5C3.1030203@zytor.com> (raw)
In-Reply-To: <20060618230041.GG4744@bouh.residence.ens-lyon.fr>
Samuel Thibault wrote:
>
> There has been at least my complaint about udev not being able to
> auto-load modules on /dev entry lookup (28th March 2006):
>
> « Given a freshly booted linux box, hence uinput is not loaded (why
> would it be, it doesn't drive any real hardware) ; what is the right
> way(tm) for an application to have the uinput module loaded, so that it
> can open /dev/input/uinput for emulating keypresses?
>
> - With good-old static /dev, we could just open /dev/input/uinput
> (installed by the distribution), and thanks to a
> alias char-major-10-223 uinput
> line somewhere in /etc/modprobe.d, uinput gets auto-loaded.
>
> - With devfs, it doesn't look like it works (/dev/misc/uinput is not
> present and opening it just like if it existed doesn't work). But I
> read in archives that it could be feasible.
>
> - With udev, this just cannot work. As explained in an earlier thread,
> even using a special filesystem that would report the opening attempt
> to udevd wouldn't work fine since udevd takes time for creating the
> device, and hence the original program needs to be notified ; this
> becomes racy.
>
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.
-hpa
next prev parent reply other threads:[~2006-06-19 0:54 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 [this message]
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=4495F5C3.1030203@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.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