[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BFFC821.1020509@msgid.tls.msk.ru>
Date: Fri, 28 May 2010 17:41:53 +0400
From: Michael Tokarev <mjt@....msk.ru>
To: Kay Sievers <kay.sievers@...y.org>
CC: Bastian Blank <waldi@...ian.org>, xen-devel@...ts.xensource.com,
Jeremy Fitzhardinge <jeremy@...p.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix name of Xen event-channel device
Kay Sievers wrote:
> On Thu, May 27, 2010 at 19:13, Bastian Blank <waldi@...ian.org> wrote:
[]
>>> Also, how about other xen-related
>>> devices which are moved to /dev/xen in that same udev rules?
>> This is the only device currently supported by the vanilla kernel,
>> everything else is in the Xen tree only.
>
> And naming of primary device nodes is no longer udev's task. All these
> rules are removed from the default udev rules. These names must all
> come from the kernel these days. Udev will log errors if udev rules
> specify names which are not in sync with the kernel, so they can be
> fixed in the kernel or in the rules.
Finally!... It's been hashed and rehashed back when udevd were
invented to replace devfs and we returned back to traditional
kernel-generated names for a base. Oh well...
That's, actually, _excellent_ news, something that bothered me
for all these years since 2.4 kernel - that I don't have some
devices in /dev (because they're named differently or moved to
a subdir) which are mentioned in dmesg or sysfs. Hooray!
Will check for all sound (/dev/snd/), input (/dev/input/), usb
(/dev/usb/) and oh, the famous tun (/dev/net/tun) devices - you
intrigued me!.. ;)
Thanks!
/mjt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists