From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Name of event-channel and other devices vs. udev Date: Thu, 27 May 2010 15:37:49 -0700 Message-ID: <4BFEF43D.90101@goop.org> References: <20100526105144.GA28280@wavehammer.waldi.eu.org> <20100527073512.GA17135@wavehammer.waldi.eu.org> <20100527143104.GB6040@wavehammer.waldi.eu.org> <4BFEEC96.3010207@goop.org> <20100527222641.GA25018@wavehammer.waldi.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100527222641.GA25018@wavehammer.waldi.eu.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Bastian Blank , xen-devel@lists.xensource.com, Keir Fraser List-Id: xen-devel@lists.xenproject.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