From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastian Blank Subject: Re: Name of event-channel and other devices vs. udev Date: Fri, 28 May 2010 00:26:41 +0200 Message-ID: <20100527222641.GA25018@wavehammer.waldi.eu.org> References: <20100526105144.GA28280@wavehammer.waldi.eu.org> <20100527073512.GA17135@wavehammer.waldi.eu.org> <20100527143104.GB6040@wavehammer.waldi.eu.org> <4BFEEC96.3010207@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <4BFEEC96.3010207@goop.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: Jeremy Fitzhardinge Cc: xen-devel@lists.xensource.com, Keir Fraser List-Id: xen-devel@lists.xenproject.org On Thu, May 27, 2010 at 03:05:10PM -0700, Jeremy Fitzhardinge wrote: > On 05/27/2010 07:31 AM, Bastian Blank wrote: > > Xen themself is responsible for this behaviour. > You presumably don't mean the hypervisor. No. But Xen as delivered == hypervisor + tools. > Do you mean the toolstack is > doing something bad when the misc device has a '/' in it? I noticed > when I applied your change it does things like look in > /sys/class/xen/evtchn (or something). 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. > 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. Bastian -- We'll pivot at warp 2 and bring all tubes to bear, Mr. Sulu!