From owner-freebsd-stable@freebsd.org Wed Dec 19 06:50:09 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57C07134D805 for ; Wed, 19 Dec 2018 06:50:09 +0000 (UTC) (envelope-from brian@aceshardware.com) Received: from mail.aceshardware.com (mail.aceshardware.com [52.52.37.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0AFEC6C4D9 for ; Wed, 19 Dec 2018 06:50:07 +0000 (UTC) (envelope-from brian@aceshardware.com) Received: from [IPv6:::ffff:10.0.0.117] (unknown [71.145.208.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.aceshardware.com (Postfix) with ESMTPSA id 93FAC201307 for ; Wed, 19 Dec 2018 06:49:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aceshardware.com; s=dkim; t=1545202199; h=from:from:sender:reply-to:subject:subject:date:date:message-id:to:to: cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:references; bh=sHUhVPwmztb75QgmpXz5kW1LGx7lmGBQxkEyAG1bkf8=; b=Z5Lfo0Sb2MXVZjLWcikENXDmm5FDwnXOERNzMUFcRSFCCfzPPD/kKg4+btN6gKmJ4/5xHl Dc+2m+YOhsu39hRmHlJmqOvZkEfUkuQ46wygQ5bIpVIUAzlt4JFOMrb5GhfLfcFkaQmz7/ UPRdJcwaSERErH6TAdqPkUnrgSNynjrwVrbR13gtcJiFiSurnrM79LwvOMUOQzrRrjy8bx oa5Xi7vRb25prMC7lKu1OfbIoD+WPh6kRfjsy9K4gGJ2yz6TX+QRtqCBsi3KWtmVdXgYEn jzXxTdFCu7h+UP6qrLgWDaxcFkaEt4u4XT+i2prC6rHMBSyWqLIDz1TMQpSJ2A== MIME-Version: 1.0 To: "freebsd-stable@freebsd.org" From: Brian Neal Subject: Upgrading 11.2 -> 12.0 on EC2 Date: Tue, 18 Dec 2018 22:50:00 -0800 Importance: normal X-Priority: 3 X-Rspamd-Queue-Id: 0AFEC6C4D9 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aceshardware.com header.s=dkim header.b=Z5Lfo0Sb; dmarc=pass (policy=none) header.from=aceshardware.com X-Spamd-Result: default: False [-0.52 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[aceshardware.com:s=dkim]; NEURAL_HAM_MEDIUM(-0.65)[-0.650,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.88)[-0.878,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; MISSING_MID(2.50)[]; DKIM_TRACE(0.00)[aceshardware.com:+]; DMARC_POLICY_ALLOW(-0.50)[aceshardware.com,none]; HAS_X_PRIO_THREE(0.00)[3]; MX_GOOD(-0.01)[mail.aceshardware.com]; TO_DN_EQ_ADDR_ALL(0.00)[]; R_SPF_NA(0.00)[]; NEURAL_HAM_SHORT(-0.43)[-0.428,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; IP_SCORE(-0.26)[asn: 16509(-1.20), country: US(-0.08)]; ASN(0.00)[asn:16509, ipnet:52.52.0.0/15, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 06:50:09 -0000 Hello, I=E2=80=99m looking for advice on doing a release upgrade of a running inst= ance. It looks like the normal procedure using freebsd-update requires a r= eboot between invocations of the install command, but after the first reboo= t, most of the userland is non-functional, including most importantly sshd.= Is it safe to run the install commands back to back without rebooting? Or= is the only safe procedure to build a new instance from scratch for each r= elease? Cheers, -Brian