public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Bastian Blank <waldi@debian.org>,
	xen-devel@lists.xensource.com,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix name of Xen event-channel device
Date: Fri, 28 May 2010 17:41:53 +0400	[thread overview]
Message-ID: <4BFFC821.1020509@msgid.tls.msk.ru> (raw)
In-Reply-To: <AANLkTinmhitag1oTssXB_ICXIriubGLNBvltS-Fuc8Cg@mail.gmail.com>

Kay Sievers wrote:
> On Thu, May 27, 2010 at 19:13, Bastian Blank <waldi@debian.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

  reply	other threads:[~2010-05-28 13:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100526105144.GA28280@wavehammer.waldi.eu.org>
     [not found] ` <20100527073512.GA17135@wavehammer.waldi.eu.org>
     [not found]   ` <20100527143104.GB6040@wavehammer.waldi.eu.org>
2010-05-27 15:02     ` [PATCH] Fix name of Xen event-channel device Bastian Blank
2010-05-27 16:26       ` [Xen-devel] " Konrad Rzeszutek Wilk
2010-05-27 16:50       ` Michael Tokarev
2010-05-27 17:13         ` Bastian Blank
2010-05-28 13:24           ` Kay Sievers
2010-05-28 13:41             ` Michael Tokarev [this message]
2010-05-28 23:20           ` Jeremy Fitzhardinge

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=4BFFC821.1020509@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=jeremy@goop.org \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=waldi@debian.org \
    --cc=xen-devel@lists.xensource.com \
    /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