From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bastian Blank <waldi@debian.org>
Subject: Re: [PATCH] xc: deal with xen/evtchn and xen/gntdev
	device names
Date: Tue, 1 Jun 2010 10:17:07 +0200
Message-ID: <20100601081707.GA24351@wavehammer.waldi.eu.org>
References: <4C00690B.2020303@goop.org>
	<1275379012.24218.20337.camel@zakaz.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <1275379012.24218.20337.camel@zakaz.uk.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, Xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On Tue, Jun 01, 2010 at 08:56:52AM +0100, Ian Campbell wrote:
> Does any of this logic really belong in libxc in the first place? 

No.

> Can we not just rip it all out and make it the distro/platform's
> responsibility to ensure these devices exist and are correct?

Thats what I forced in Debian right now.

>                                                               Perhaps
> that might involve shipping some default/example udev rules instead.

With the fixed kernel this needs no rules. Even with devtmpfs (some
people call it devfs version 2) and no udev it will work then.

Bastian

-- 
Vulcans believe peace should not depend on force.
		-- Amanda, "Journey to Babel", stardate 3842.3