From owner-freebsd-doc@freebsd.org Tue Jan 10 04:23:04 2017 Return-Path: Delivered-To: freebsd-doc@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 D1987CA8B28 for ; Tue, 10 Jan 2017 04:23:04 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id B1D001119 for ; Tue, 10 Jan 2017 04:23:04 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: by mailman.ysv.freebsd.org (Postfix) id B1335CA8B27; Tue, 10 Jan 2017 04:23:04 +0000 (UTC) Delivered-To: doc@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 B0D7BCA8B25 for ; Tue, 10 Jan 2017 04:23:04 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-7.mit.edu (dmz-mailsec-scanner-7.mit.edu [18.7.68.36]) (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 6572A1118 for ; Tue, 10 Jan 2017 04:23:03 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074424-87bff700000009ba-b9-587461a0d592 Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id 78.25.02490.0A164785; Mon, 9 Jan 2017 23:22:56 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id v0A4MtGP018651; Mon, 9 Jan 2017 23:22:55 -0500 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v0A4MqZm029208 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 9 Jan 2017 23:22:54 -0500 Date: Mon, 9 Jan 2017 22:22:52 -0600 From: Benjamin Kaduk To: Eric Rucker Cc: doc@freebsd.org Subject: Re: FreeBSD 11.0-RELEASE upgrading comments Message-ID: <20170110042251.GN8460@kduck.kaduk.org> References: <20170110001533.GK8460@kduck.kaduk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrOIsWRmVeSWpSXmKPExsUixG6norsgsSTC4M8ccYud9xYzWUz9uJPV gcljxqf5LB47Z91lD2CK4rJJSc3JLEst0rdL4MrY9vQra8Ed1orHCztYGxhPs3QxcnBICJhI TD6S3sXIxSEk0MYk8ebQT0YIZwOjxPZXXSwQzhUmiS/3fzN3MXJysAioSHxadIEFxGYDshu6 L4PFRYDsOxd+gsWZBYQlZvR8BbOFgTbcfTGHDcTmFTCWWPT+B9SGg4wSe9/2sEIkBCVOznwC 1awlcePfSyaQ85gFpCWW/+MACXMKBEr0NLUygtiiAsoSDTMeME9gFJiFpHsWku5ZCN0LGJlX Mcqm5Fbp5iZm5hSnJusWJyfm5aUW6Zrr5WaW6KWmlG5iBIepi8oOxu4e70OMAhyMSjy8EROK I4RYE8uKK3MPMUpyMCmJ8qbolkQI8SXlp1RmJBZnxBeV5qQWH2KU4GBWEuGdGA+U401JrKxK LcqHSUlzsCiJ817KdI8QEkhPLEnNTk0tSC2CycpwcChJ8EokADUKFqWmp1akZeaUIKSZODhB hvMADfcCqeEtLkjMLc5Mh8ifYtTlOPB+xVMmIZa8/LxUKXHeqSAXCIAUZZTmwc0BpReJ7P01 rxjFgd4S5tUAGcUDTE1wk14BLWECWhJpVwyypCQRISXVwLil1P5G5a8pqyZIhvCcbnbS+u2e Gjmf+QDP/p9nHW7EzxJZ/XzVjuOfX97cs2/7XOcsSe4WS3Xl+NOV+T7v90pn7rpl4qYn9+3o bj1t1X0PTj061RjPPJ0vRFXFTuLH9F3HVx74U8w3ofNbT5hl0HpX7bv1+uWPTqXyZBaYBpcZ +7/dsN5OLVCJpTgj0VCLuag4EQCiPZ2RCgMAAA== X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 04:23:04 -0000 On Mon, Jan 09, 2017 at 07:26:41PM -0500, Eric Rucker wrote: > Ben, > > I've already upgraded to 10.3-RELEASE, and do not have uname -a output > available from the system before the upgrade. But, this should be good > enough, from the last kernel log from before I upgraded: > > +FreeBSD 9.3-RELEASE-p49 #0: Fri Oct 21 21:01:08 UTC 2016 > + root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > I was at the latest patchlevel (p53 - p49 was the last kernel > patchlevel, it appears) before attempting the upgrade. Okay, thanks for the confirmation. Unfortunately, it is not always easy to change the release notes after the release is finalized, but we can see what could be done. -Ben