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: Wed, 26 May 2010 17:08:50 -0700 Message-ID: <4BFDB812.9040607@goop.org> References: <20100526105144.GA28280@wavehammer.waldi.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100526105144.GA28280@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/26/2010 03:51 AM, Bastian Blank wrote: > 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. > Yep, looks reasonable to me. J