From owner-freebsd-cloud@freebsd.org Wed Feb 10 09:16:24 2016 Return-Path: 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 C9F1DAA3E7E for ; Wed, 10 Feb 2016 09:16:24 +0000 (UTC) (envelope-from rj@obsigna.com) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A8DDE28 for ; Wed, 10 Feb 2016 09:16:23 +0000 (UTC) (envelope-from rj@obsigna.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1455095781; l=537; s=domk; d=obsigna.com; h=To:References:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From: Subject:Mime-Version:Content-Type; bh=oLisbXUDbC8hC8jNL8wZw+DFV0U9kRuhK9BGAMXUUCE=; b=SyTuKiPE+87f/lKV1Fcnbd0N+4PwkmIKOez4PibpVlGvTl8DsX3V0F81sYDwHVUj2jY x966L2b8cEu7ID2K4SSHXzwbgx6O58Fg87ep7MavdQP/5AhwEJROPRN5hux7HJ3ioKc7E /rqJnmkbP9BkOynhyqJpUGNA7lmdaSr3KWY= X-RZG-AUTH: :O2kGeEG7b/pS1EK7WHa0hxqKZr4lnx6UhToX1IWHkW4X7v2ImaU2CVqpyLmhRLYu0vEWnk0= X-RZG-CLASS-ID: mo00 Received: from mail.obsigna.com (b150a194.virtua.com.br [177.80.161.148]) by smtp.strato.de (RZmta 37.18 DYNA|AUTH) with ESMTPSA id h04f97s1A9GJ6x5 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate); Wed, 10 Feb 2016 10:16:19 +0100 (CET) Received: from rolf.projectworld.net (rolf.projectworld.net [192.168.222.5]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.obsigna.com (Postfix) with ESMTPSA id A262675900; Wed, 10 Feb 2016 07:16:16 -0200 (BRST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: What is the best method to keep FreeBSD on AWS-EC2 up to date? From: "Dr. Rolf Jansen" In-Reply-To: <00000152c9fa9b4d-48381ee7-9b7a-4547-9981-3945dbd242dd-000000@email.amazonses.com> Date: Wed, 10 Feb 2016 07:16:14 -0200 Cc: freebsd-cloud@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <83A5F020-ABC6-4CA8-B78A-A2A84ABE509A@obsigna.com> References: <00000152c9fa9b4d-48381ee7-9b7a-4547-9981-3945dbd242dd-000000@email.amazonses.com> To: Colin Percival X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Feb 2016 09:16:24 -0000 > Am 10.02.2016 um 04:59 schrieb Colin Percival : >=20 > On 02/09/16 17:59, Dr. Rolf Jansen wrote: >>> =E2=80=A6 =46rom 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). >>=20 >> When I cannot use freebsd-update, what else should I do to keep the = system updated? >=20 > You can use freebsd-update. The text on that Marketplace page is out = of date. OK, thank you very much!