From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Bastian Blank <waldi@debian.org>,
xen-devel@lists.xensource.com,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: Name of event-channel and other devices vs. udev
Date: Thu, 27 May 2010 15:37:49 -0700 [thread overview]
Message-ID: <4BFEF43D.90101@goop.org> (raw)
In-Reply-To: <20100527222641.GA25018@wavehammer.waldi.eu.org>
On 05/27/2010 03:26 PM, Bastian Blank wrote:
> It does the following:
> - Search in /sys/**/evtchn for the device number, this fails.
> - Compares the existing /dev/xen/evtchn with the error and unlinks it.
> - Tries to mknod it again with the error value, this fails.
>
That's unfortunate.
>> What other changes are needed to keep things working after this change?
>>
> To possibilities:
> - Fix the error detection in this crude device creation code.
> - Rip it out and always rely on the system to provide the devices.
>
> For Debian I already decided to use the later one.
>
Yes, that seems like the cleanest approach. Does it need any udev
config to get that right? In particular, is there a mechanism to
autoload misc device modules?
J
next prev parent reply other threads:[~2010-05-27 22:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 10:51 Name of event-channel and other devices vs. udev Bastian Blank
2010-05-27 0:08 ` 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 [this message]
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=4BFEF43D.90101@goop.org \
--to=jeremy@goop.org \
--cc=Keir.Fraser@eu.citrix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.