From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [PATCH] xc: deal with xen/evtchn and xen/gntdev device names Date: Tue, 01 Jun 2010 09:35:11 -0700 Message-ID: <4C0536BF.7070605@goop.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 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1275379012.24218.20337.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: Bastian Blank , Xen-devel List-Id: xen-devel@lists.xenproject.org On 06/01/2010 12:56 AM, Ian Campbell wrote: > Does any of this logic really belong in libxc in the first place? > No. It's a relic of a simpler time. > Can we not just rip it all out and make it the distro/platform's > responsibility to ensure these devices exist and are correct? Perhaps > that might involve shipping some default/example udev rules instead. > I only kept it because I didn't want to break any existing installs, but updating the kernel's name is going to do that anyway. Unfortunately the current libxc code is broken in the worst possible way - it will unlink an existing correct device and then fail to replace it - so even if the system has set it up correctly it will still screw things up. I think we're just going to have to have a flag day and fix kernel, libxc and udev (assuming it needs it) all at once... J