From: Keir Fraser Subject: Re: [PATCH] large file support for lomount (for 32-bit dom0) Date: Fri, 06 Nov 2009 22:16:30 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" 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: Dan Magenheimer , "Xen-Devel (E-mail)" Cc: Ian Jackson List-Id: xen-devel@lists.xenproject.org On 06/11/2009 22:11, "Keir Fraser" wrote: >> Since it is very helpful for recovering from an update to >> an in-guest kernel (which is often useful in xen development >> but probably also periodically useful to support xen distros), I'd >> propose that CONFIG_LOMOUNT get turned on by default in Config.mk. >> If we get complaints, it's easy enough to turn it back off later. > > Another point is that it's almost certainly Linux-specific; at least the bit > that sets up the loopback mount. We could perhaps just get rid of > CONFIG_LOMOUNT and unconditionally build lomount on Linux only. Ah, now I see lomount was disabled by default in c/s 16742, which was by Ian Jackson and has a detailed changeset comment. It seems he thinks there are fine alternatives to lomount these days. -- Keir