From: "Theodore Ts'o" <tytso@mit.edu>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: udev on 2.6.14 fails to create /dev/input/event2 on T40 Thinkpad
Date: Mon, 7 Nov 2005 00:36:49 -0500 [thread overview]
Message-ID: <20051107053648.GA7521@thunk.org> (raw)
In-Reply-To: <20051106203421.GB2527@kroah.com>
On Sun, Nov 06, 2005 at 12:34:21PM -0800, Greg KH wrote:
> On Sun, Nov 06, 2005 at 12:47:02AM -0500, Theodore Ts'o wrote:
> > +P: /class/input/input3/event3
>
> No, this shows a post-2.6.14 kernel, not 2.6.14 as what is located on
> kernel.org, right? I'm guessing 2.6.14-git1? Or is this a distro based
> kernel?
>
> If so, you need to upgrade udev, as the Documentation says to :)
>
> If not, and this is 2.6.14, something is very wrong...
Yes, sorry, I got confused about which tree I had booting; this was
indeed a post-2.6.14 kernel (pulled using hg).
Documentation/changes at the tip as of tonight still says use "udev
version 071", which is what I have installed. I note that the latest
version on kernel.org is udev 072 --- is that what is going to be
required for 2.6.15? If so, better warn folks at distro's like Debian
unstable. If not, what do I need to change so I can easily test post
2.6.14 kernels --- and where was it documented that I needed a newer
version of udev?
- Ted
next prev parent reply other threads:[~2005-11-07 5:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-06 5:47 udev on 2.6.14 fails to create /dev/input/event2 on T40 Thinkpad Theodore Ts'o
2005-11-06 10:08 ` Jiri Slaby
2005-11-06 13:55 ` Theodore Ts'o
2005-11-06 15:03 ` Kay Sievers
2005-11-06 20:34 ` Greg KH
2005-11-07 5:36 ` Theodore Ts'o [this message]
2005-11-07 15:52 ` Greg KH
2005-11-07 18:17 ` Theodore Ts'o
2005-11-07 18:24 ` Greg KH
2005-11-08 3:30 ` Theodore Ts'o
2005-11-08 4:43 ` Greg KH
2005-11-08 13:14 ` Theodore Ts'o
2005-11-08 18:34 ` Greg KH
2005-11-08 21:52 ` Marco d'Itri
2005-11-08 21:56 ` Greg KH
2005-11-08 23:09 ` maximilian attems
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=20051107053648.GA7521@thunk.org \
--to=tytso@mit.edu \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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