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:58:27 +0200 Message-ID: <20100527225827.GA29722@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> <20100527222641.GA25018@wavehammer.waldi.eu.org> <4BFEF43D.90101@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <4BFEF43D.90101@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: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.