From: Bastian Blank <waldi@debian.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com, Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: Name of event-channel and other devices vs. udev
Date: Fri, 28 May 2010 00:58:27 +0200 [thread overview]
Message-ID: <20100527225827.GA29722@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <4BFEF43D.90101@goop.org>
On Thu, May 27, 2010 at 03:37:49PM -0700, Jeremy Fitzhardinge wrote:
> On 05/27/2010 03:26 PM, Bastian Blank wrote:
> > 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?
No, there is no autoloading possible; neither now nor with the patch.
The default udev config is correct in this case.
Bastian
--
Warp 7 -- It's a law we can live with.
prev parent reply other threads:[~2010-05-27 22:58 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
2010-05-27 22:58 ` Bastian Blank [this message]
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=20100527225827.GA29722@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).