Date: Wed, 11 Jan 2017 23:24:18 -0500 From: George Mitchell <george+freebsd@m5p.com> To: Kevin Oberman <rkoberman@gmail.com> Cc: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org> Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" Message-ID: <fcdaaa0c-4a7a-e21c-58e8-f4576ef637e3@m5p.com> In-Reply-To: <d9be6315-d19e-a97e-7828-6278f475329e@m5p.com> References: <c0725ed3-0345-321e-ce05-e324bac89717@m5p.com> <CAN6yY1s1m0=_1%2B38n8me-4%2BLHN6bbiaii2q6diCLGF_SMxugtg@mail.gmail.com> <d9be6315-d19e-a97e-7828-6278f475329e@m5p.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --OHEtRfvVVKAFpfg7fwKC6sFuL7ANEAOJ3 Content-Type: multipart/mixed; boundary="fCgx93EaAJdMrXcmTHgpkMxrv0CQs3EmM"; protected-headers="v1" From: George Mitchell <george+freebsd@m5p.com> To: Kevin Oberman <rkoberman@gmail.com> Cc: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org> Message-ID: <fcdaaa0c-4a7a-e21c-58e8-f4576ef637e3@m5p.com> Subject: Re: 10.3-RELEASE-p13 "unsupported file layout" References: <c0725ed3-0345-321e-ce05-e324bac89717@m5p.com> <CAN6yY1s1m0=_1+38n8me-4+LHN6bbiaii2q6diCLGF_SMxugtg@mail.gmail.com> <d9be6315-d19e-a97e-7828-6278f475329e@m5p.com> In-Reply-To: <d9be6315-d19e-a97e-7828-6278f475329e@m5p.com> --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 >> <https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-u= pgrading-freebsdupdate.html#freebsd-update-custom-kernel-9x> >> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fcdaaa0c-4a7a-e21c-58e8-f4576ef637e3>