From owner-freebsd-cloud@freebsd.org  Wed Feb 10 06:59:56 2016
Return-Path: <owner-freebsd-cloud@freebsd.org>
Delivered-To: freebsd-cloud@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 A33DCAA35D8
 for <freebsd-cloud@mailman.ysv.freebsd.org>;
 Wed, 10 Feb 2016 06:59:56 +0000 (UTC) (envelope-from
 00000152c9fa95e9-5c023d6f-98aa-4ee3-a784-1b816d739bb3-000000@amazonses.com)
Received: from a8-60.smtp-out.amazonses.com (a8-60.smtp-out.amazonses.com
 [54.240.8.60])
 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6DD38CC1
 for <freebsd-cloud@freebsd.org>; Wed, 10 Feb 2016 06:59:56 +0000 (UTC)
 (envelope-from
 00000152c9fa95e9-5c023d6f-98aa-4ee3-a784-1b816d739bb3-000000@amazonses.com)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
 s=vnqrkfnvu6csdl6mwgk5t6ix3nnepx57; d=tarsnap.com; t=1455087588;
 h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding;
 bh=u5QA4HvGeevHbvz1AWyy/QYLkW3RVaaFbMM4LfG/ilQ=;
 b=ZoGlprosCZph0N7VFiEBE4trqLwgospIzMcGkyfJAzpwShEV7UUvm9Phfzwl14Q+
 XtqwdfU1rpFmLliayIRDggW2s/7APNlSeNnXL2rx5UefuLXY/UPNqVL/J/dZU1Or5pk
 jKo7CyaC8AfS4mKpqq5J6sBO2tX0+o4SGBVbM4Ns=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
 s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1455087588;
 h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:Feedback-ID;
 bh=u5QA4HvGeevHbvz1AWyy/QYLkW3RVaaFbMM4LfG/ilQ=;
 b=Hoz/NogOSDBuw7n76/Ika8QCwumOd05KMZz3xfUBjn40/SQEpfoXsB9NL4l8Vnow
 E2Hz5ms+MLQwIM486rG0oclzj5IbsnNlWN52jf+jX5EPxB7lD9crttrEQreEvstMx0c
 2nmeEqBNLnFm59gAMttkhn/bneKtHZOUDYvAKYb4=
Subject: Re: What is the best method to keep FreeBSD on AWS-EC2 up to date?
To: "Dr. Rolf Jansen" <rj@obsigna.com>, freebsd-cloud@freebsd.org
References: <E656B964-8E45-4CE5-AD6F-00A601A36714@obsigna.com>
From: Colin Percival <cperciva@tarsnap.com>
Message-ID: <00000152c9fa95e9-5c023d6f-98aa-4ee3-a784-1b816d739bb3-000000@email.amazonses.com>
Date: Wed, 10 Feb 2016 06:59:48 +0000
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101
 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <E656B964-8E45-4CE5-AD6F-00A601A36714@obsigna.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-SES-Outgoing: 2016.02.10-54.240.8.60
Feedback-ID: 1.us-east-1.Lv9FVjaNvvR5llaqfLoOVbo2VxOELl7cjN0AOyXnPlk=:AmazonSES
X-BeenThere: freebsd-cloud@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure,
 etc.\)" <freebsd-cloud.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-cloud>,
 <mailto:freebsd-cloud-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-cloud/>
List-Post: <mailto:freebsd-cloud@freebsd.org>
List-Help: <mailto:freebsd-cloud-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-cloud>,
 <mailto:freebsd-cloud-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2016 06:59:56 -0000

On 02/09/16 17:59, Dr. Rolf Jansen wrote:
>> … From there on, standard FreeBSD usage and system configuration applies, except that freebsd-update cannot be used (due to local patches needed for the FreeBSD/EC2 platform).
> 
> When I cannot use freebsd-update, what else should I do to keep the system updated?

You can use freebsd-update.  The text on that Marketplace page is out of date.

-- 
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid