From owner-freebsd-questions@freebsd.org Wed Aug 30 21:43:57 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E672FE0AF80 for ; Wed, 30 Aug 2017 21:43:57 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "bs1.fjl.org.uk", Issuer "bs1.fjl.org.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9AA83817A6 for ; Wed, 30 Aug 2017 21:43:57 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from [192.168.1.35] (host86-191-18-76.range86-191.btcentralplus.com [86.191.18.76]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id v7ULhtxH082095 for ; Wed, 30 Aug 2017 22:43:55 +0100 (BST) (envelope-from frank2@fjl.co.uk) Subject: Re: VPS that will run xBSD References: <673b7208-c0d9-5179-407a-2cf9d276e1a8@fjl.co.uk> <031E40A6-0C53-47B2-BA86-E9932E02000B@sigsegv.be> <31D122B4-EC3C-41C0-9C72-7D859DD6492E@rafal.net> Cc: freebsd-questions@freebsd.org From: Frank Leonhardt Message-ID: <2894b33a-ee7d-0a3f-4a3d-e4f03a2c38e2@fjl.co.uk> Date: Wed, 30 Aug 2017 22:43:56 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <31D122B4-EC3C-41C0-9C72-7D859DD6492E@rafal.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2017 21:43:58 -0000 On 30/08/2017 22:39, Rafal Lukawiecki wrote: > While I am not a FreeBSD expert, I have built a good few AWS AMIs (Amazon Machine Images) for various Linuxes I have used over the years. The process generally requires you to use an existing available machine (say FreeBSD RELEASE) to build what you need first. You should use a pricier and a much faster machine for that, but you can change the underlying hardware just for this purpose, switching down to a cheaper one later. > > In the process, you create an AWS ESB volume that contains your desired new OS (say STABLE in your case). You snapshot that, which is an easy AWS operation, and you register that snapshot as a new AMI that you can now use to launch any number of new machines with your desired kernel and config. > > Bear in mind this is an oversimplification of the process, as you have to pay attention to the needs of the hypervisor and the provided hardware. However, all of this has been done for us by Colin Percival. Have a look at his article in which he explained how to build your own FreeBSD AWS AMIs: > > http://www.daemonology.net/blog/2015-11-21-FreeBSD-AMI-builder-AMI.html > > If you do not need an AMI, that is you only want to update the very machine on which you are working, you can simply change to a new kernel and reboot. Caveat: I have not tried that with FreeBSD (yet) only CentOS. > > Rafal > -- > Rafal Lukawiecki > Data Scientist and Director > Project Botticelli Ltd Thanks - interesting to know. This is really just-for-fun so I might well give this a try.