From owner-freebsd-stable@freebsd.org Wed Jan 11 22:46:23 2017 Return-Path: Delivered-To: freebsd-stable@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 9A99BCAB30C for ; Wed, 11 Jan 2017 22:46:23 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [IPv6:2001:418:3fd::f7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A4FF1FFD for ; Wed, 11 Jan 2017 22:46:23 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:418:3fd::1f] (haymarket.m5p.com [IPv6:2001:418:3fd::1f]) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTP id v0BMkGvP061134; Wed, 11 Jan 2017 17:46:21 -0500 (EST) (envelope-from george+freebsd@m5p.com) Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" To: Kevin Oberman References: Cc: FreeBSD Stable Mailing List From: George Mitchell Message-ID: Date: Wed, 11 Jan 2017 17:46:09 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="6l4MamM01nvoHHHrGOW0Fxre6sNuE1bCm" X-Spam-Status: No, score=-3.8 required=10.0 tests=ALL_TRUSTED, RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.1 (mailhost.m5p.com [IPv6:2001:418:3fd::f7]); Wed, 11 Jan 2017 17:46:22 -0500 (EST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Jan 2017 22:46:23 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6l4MamM01nvoHHHrGOW0Fxre6sNuE1bCm Content-Type: multipart/mixed; boundary="UhONn4HQJKSfS0uQ6hLgB4OWVLT5WCDO1"; protected-headers="v1" From: George Mitchell To: Kevin Oberman Cc: FreeBSD Stable Mailing List Message-ID: Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" References: In-Reply-To: --UhONn4HQJKSfS0uQ6hLgB4OWVLT5WCDO1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 01/11/17 17:20, Kevin Oberman wrote: > [...] >=20 > While I have no suggestions about the error building libc, your stateme= nt > that you can't use freebsd-update due to your use of a custom kernel is= > incorrect. This is a common misconception and, in cases of very limited= > disk space, may be true, it is rare. It is helped by the fact that the = man > page makes no mention of how to so this. (You do still need to build a = new > kernel if the update does, indeed, touch the kernel.) >=20 > All you need is a GENERIC kernel in /boot/GENERIC. You can either build= it > or download it. See the FreeBSD Handbook Section 23.2.3.1, =E2=80=9CCus= tom Kernels > with FreeBSD 9.X and Later=E2=80=9D > > for details on downloading a GENERIC kernel. Before any upgrade, major = or > minor, you might wat to re-reas that section. >=20 > Once the GENERIC kernel is in /boot, you may use freebsd-update and, if= the > GENERIC kernel is not updated, you're good to go. If it is, you will ne= ed > to build and install a new custom kernel and reboot. Since most securit= y > patches don't touch the kernel, this is usually not needed. I believe t= hat > the 10.3 kernel was last touched in p11. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.or= g" >=20 Thanks, I'll try that the next time I have a chance. When I naively tried a straight "freebsd-update" a few months ago, of course it overwrote my SCHED_4BSD kernel with a SCHED_ULE one. -- George --UhONn4HQJKSfS0uQ6hLgB4OWVLT5WCDO1-- --6l4MamM01nvoHHHrGOW0Fxre6sNuE1bCm Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlh2tbEACgkQwRES3m+p 4flClw//cILXOVZq3Tz+PoVThfnCP6mMSiw3W+gj/6g9b432vMIPugwsOt02Egh7 hMvnKLL0jIo/oW4GveqMuOiqv/lSKUIUFYGC3JRH8qmL4u1c3UKiAU6sdFZ8L9+b PCKeHD4RsudlL3obpg40RqekzLCRawU8q/K7Zwayhuvfe7zHT30PBWP/dfrCAFq1 E3x0q/+Aqey2KdUCkqOVEmPz+tY8tZlLNPAf5D8S/e06h7pfjVtbP01c2K0ejg5S fi0EFBQ5gV9lS3/PfCpdRLmps+F5afwWdXJDtA4bWR9/Lt5ug3MC0rPWECldOzLs E6fIpXEWKOKaqbbXFB4RrQcIKYX+3FJOvtfP51ZHGNa+M5fKim8b2iQjbGoOKRK8 xmMWWH5LvYVpMaUFcqYxPya9WkngP+dpD9AKN5zc4UkkwrYOqcFEzA3edkmcfIXl ad7WlT60Ql41IUUKA979/7fWdpxLp78Hl22p9D3VrS+bH+gnHfx9QHKdo+zulik+ /hrGKHh6GQHZv96tDwZA8gSv+ylqNNjpFxGqfdleGS9ApNFS3vzSLQv0302047iG +bliKxv0iRLb7YFJkQITLxcbsIYDt7pQLlU30jiTPf6ByPjryvCThZ/XYicfNxBH VIYykrWxdsD1oWK3eHNCG7AQ+kTSrSyTvzbubnnR1U1IeciCNc0= =847g -----END PGP SIGNATURE----- --6l4MamM01nvoHHHrGOW0Fxre6sNuE1bCm--