From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH v4 05/11] osstest: add script for building custom mfsBSD images Date: Thu, 19 Mar 2015 15:16:20 +0000 Message-ID: <1426778180.21742.31.camel@citrix.com> References: <1424276291-6872-1-git-send-email-roger.pau@citrix.com> <1424276291-6872-6-git-send-email-roger.pau@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YYcFU-0004d4-F0 for xen-devel@lists.xenproject.org; Thu, 19 Mar 2015 15:20:40 +0000 In-Reply-To: <1424276291-6872-6-git-send-email-roger.pau@citrix.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: Roger Pau Monne Cc: xen-devel@lists.xenproject.org, Ian Jackson List-Id: xen-devel@lists.xenproject.org On Wed, 2015-02-18 at 17:18 +0100, Roger Pau Monne wrote: [...] > We would need to have a local copy of them in order to have a push gate like > we do for Linux, Qemu or SeaBIOS. > > The workflow of this would be: > > 1. Setup a FreeBSD host using a RELEASE image (10.1 right now). > 2. Fetch upstream FreeBSD sources and compile a fresh FreeBSD world + > kernel. > 3. Generate a mfsBSD image using the output from the FreeBSD build process. > 4. Stash all the resulting build files (MANIFEST, kernel.txz, base.txz and > mfsbsd.img). > 5. Use the newly created mfsBSD image in order to boot and the uploaded > install sets with zfsinstall. Is all this a bunch of TODO items or things which will happen later in the series? The actual script seems reasonable.