From owner-freebsd-stable@freebsd.org Thu Jan 12 04:24:33 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 DA431CAC487 for ; Thu, 12 Jan 2017 04:24:33 +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 A10FB1AD8 for ; Thu, 12 Jan 2017 04:24:33 +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 v0C4OPhP063106; Wed, 11 Jan 2017 23:24:30 -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 23:24:18 -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="OHEtRfvVVKAFpfg7fwKC6sFuL7ANEAOJ3" 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 23:24:32 -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: Thu, 12 Jan 2017 04:24:33 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --OHEtRfvVVKAFpfg7fwKC6sFuL7ANEAOJ3 Content-Type: multipart/mixed; boundary="fCgx93EaAJdMrXcmTHgpkMxrv0CQs3EmM"; 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: --fCgx93EaAJdMrXcmTHgpkMxrv0CQs3EmM Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 01/11/17 17:46, George Mitchell wrote: > On 01/11/17 17:20, Kevin Oberman wrote: >> [...] >> >> While I have no suggestions about the error building libc, your statem= ent >> that you can't use freebsd-update due to your use of a custom kernel i= s >> incorrect. This is a common misconception and, in cases of very limite= d >> 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.) >> >> All you need is a GENERIC kernel in /boot/GENERIC. You can either buil= d it >> or download it. See the FreeBSD Handbook Section 23.2.3.1, =E2=80=9CCu= stom 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. >> >> Once the GENERIC kernel is in /boot, you may use freebsd-update and, i= f the >> GENERIC kernel is not updated, you're good to go. If it is, you will n= eed >> to build and install a new custom kernel and reboot. Since most securi= ty >> patches don't touch the kernel, this is usually not needed. I believe = that >> 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.o= rg" >> > 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 >=20 Just to refresh my memory of what happened a few months ago, I tried the following experiment. I copied my current modified kernel: rsync -av /boot/kernel/ /boot/my.kernel/ Then with my modified kernel still in place, I said: freebsd-update fetch freebsd-update install With not a qualm in the world, freebsd-update installed a fresh SCHED_ULE kernel in /boot. (Happily, it did save my current kernel in /boot/kernel.old.) That's what happened last year, too. Why didn't freebsd-update notice that I had a modified kernel and at least notify me that something funky was going on? -- George --fCgx93EaAJdMrXcmTHgpkMxrv0CQs3EmM-- --OHEtRfvVVKAFpfg7fwKC6sFuL7ANEAOJ3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlh3BPkACgkQwRES3m+p 4flmiA/+LaZs3cktQtS6WxkZFeK/nw51YARZ7JxmB6qw8A1mBERgTgr6bjJ7G21t GoID3dwm6q4I1hC86pd/JGSjVpmf8MDpz3BxgbzTJ+1L6okIHarIhLtlHo7d6Ozv ll/Yex6Biw54HZcA4hM0xuFWSlBZ5G79MY1UMsb66c869fiv7sf2frezYw/GC7tw ZPZ3PLb/sCyfvqFKrwDo2L0X65pzAb9STHXadCuTaTMk6S+daecNzmQAIJw2DbSG wLKHVg40KLks7bGF51WudDWniudCqo7h401nqSUWHPdHaxOa1wslLCZiRBDLsFiR 5OLNeFeDnag4Xv4R9tFRSoLmlMiuKczYLhxXLLOnfENYDLPidcPIo4sZMcz1wWea sywDmtMRZn0U2KLnGG6G8flrQcgAZPfeOfg7wrAj9waPnYwBzNFfivAj52uhdTME HP4kpyoGkNO6m8hgHDJbYetdSkwO0cyM8ygLhyyCcTOhSRwOMGDc1WfMEB6OS/b7 SVw5bnCbO7Lr8nv6rqfsDTd8ke6CLLO50IByikmW1uPQTif3KR+erHZYqsiO7Qml kEhjYREI1V8X5ERwRBFwmij1ZndUN0OlBdxrzDuZFRD9Kg/ErKOdqJCObumk2vol XeJ+Il+60ATvaqXib6zYQsviwmlCl3b9sfG3zCYFeNq+vzIUzIs= =N5e+ -----END PGP SIGNATURE----- --OHEtRfvVVKAFpfg7fwKC6sFuL7ANEAOJ3--