From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gary Grebus Subject: Re: losetup -f not working on SLES10 Date: Fri, 11 Dec 2009 10:03:55 -0500 Message-ID: <4B225F5B.6070502@oracle.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Andre Przywara , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > Fine by me. > > K. > > On 11/12/2009 10:03, "Andre Przywara" wrote: > >> Hi, >> >> c/s 20404 (http://xenbits.xen.org/xen-unstable.hg?rev/830bda7a9c75) >> introduces "losetup -f" to the hotplug scripts to find a free loop >> device. This option does not exists on SLES10, so Xen unstable does not >> work any longer on top on SLES10. I see that using -f is much smarter >> than the old-fashioned way, but shouldn't we keep compatibility with >> older Dom0 userlands? Ooops. I thought I checked that SLES10 had "-f", but apparently it was openSUSE. >> Is a patch providing fallback to the old code an option? Or maybe cleaner to just scan the output of "losetup -a" for the first unassigned device? I can work up a patch. /gary