From: Bastian Blank <waldi@debian.org>
To: xen-devel@lists.xensource.com
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Name of event-channel and other devices vs. udev
Date: Wed, 26 May 2010 12:51:44 +0200 [thread overview]
Message-ID: <20100526105144.GA28280@wavehammer.waldi.eu.org> (raw)
Hi
Currently udev overwrites the name of the event-channel device to
/dev/xen/evtchn. This approach is about to be discontinued and needs to
be fixed on either side.
| udevd-work[549]: kernel-provided name 'evtchn' and NAME= 'xen/evtchn' disagree, please use SYMLINK+= or change the kernel to provide the proper name
There are several fixes for that:
- Make the kernel name the device "xen/evtchn".
- Remove the rule and convert to another name. Either /dev/evtchn, which
is a bit to generic or something like xen-evtchn.
The first should be the more compatible one.
Bastian
--
A princess should not be afraid -- not with a brave knight to protect her.
-- McCoy, "Shore Leave", stardate 3025.3
next reply other threads:[~2010-05-26 10:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 10:51 Bastian Blank [this message]
2010-05-27 0:08 ` Name of event-channel and other devices vs. udev Jeremy Fitzhardinge
2010-05-27 7:35 ` Bastian Blank
2010-05-27 14:31 ` Bastian Blank
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
2010-05-28 23:20 ` Jeremy Fitzhardinge
2010-05-27 22:05 ` Name of event-channel and other devices vs. udev Jeremy Fitzhardinge
2010-05-27 22:26 ` Bastian Blank
2010-05-27 22:37 ` Jeremy Fitzhardinge
2010-05-27 22:58 ` Bastian Blank
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=20100526105144.GA28280@wavehammer.waldi.eu.org \
--to=waldi@debian.org \
--cc=Keir.Fraser@eu.citrix.com \
--cc=jeremy@goop.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;
as well as URLs for NNTP newsgroup(s).