From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [PATCH 0/9] tools: remove or disable old/useless/unused/unmainted stuff Date: Wed, 31 Jul 2013 16:57:44 +0100 Message-ID: <51F933F8.5080404@citrix.com> References: <1375283736.7382.100.camel@kazak.uk.xensource.com> <51F92D63.2000802@citrix.com> <1375284927.7382.107.camel@kazak.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1375284927.7382.107.camel@kazak.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: Ian Jackson , Keir Fraser , xen-devel List-Id: xen-devel@lists.xenproject.org On 31/07/13 16:35, Ian Campbell wrote: > On Wed, 2013-07-31 at 16:29 +0100, Andrew Cooper wrote: >> On 31/07/13 16:15, Ian Campbell wrote: >>> depends on "autoconf: regenerate configure scripts with 4.4 version" >>> >>> This series removes some of the really old deadwood from the tools build >>> and makes some other things which are on their way out configurable at >>> build time with a default depending on how far down the slope I judge >>> them to be. >>> >>> * nuke in tree copy of libaio >>> * nuke obsolete tools: xsview, miniterm, lomount & sv >>> * make xend optional, still on by default (for now!) >>> * disable blktap1 by default (needs qemu patch, just posted) >>> * some cleanup of .*ignore >>> >>> Ian. >> In what way is lomount obsolete? XenServer relies on it and I am >> unaware of any alternative. > As referenced in the actual patch: kpartx Sorry - I hadn't read that far before replying. I have quickly played with kpartx and it appears to be a suitable alternative. I shall see about moving across. ~Andrew > >> Other than that, I am very happy about the other nuked items which >> allows me to clean up some of our local hacks to the upstream build system. >> >> ~Andrew >> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xen.org >>> http://lists.xen.org/xen-devel >