Panic after updating from source

[Kevin Oberman]

On Mon, Mar 1, 2021 at 6:31 PM Michael Sierchio <kudzu at tenebras.com> wrote:

> Anyone can repeat what's in the handbook.  It may not be applicable in all
> circumstances, as I noted before – as when you don't have console access.
>
> It turns out that the formula I describe above works flawlessly for
> 12-STABLE to 13-STABLE upgrade:
>
>
>    1. userland and kernel are on
>
>    FreeBSD test-1.dbm.q2w.spin.pm 12.2-STABLE FreeBSD 12.2-STABLE
>    stable/12-n232782-39e2c45679a GRAVITON  arm64
>
>
>    1. Clear /usr/src and /usr/obj
>    2. Make sure you have a working kernconf for the new OS (e.g., device
>    random disappears in 13)
>    3.
>
>    git clone -b stable/13 --depth 1 https://git.freebsd.org/src.git
> /usr/src
>    4.
>
>    cp ~/GRAVITON /usr/src/sys/arm64/conf # my kernconf, mentioned in
>    /etc/make.conf
>    5.
>
>    cd /usr/src
>    6.
>
>    ( make -j8 buildworld && make -j8 kernel && make installworld && reboot
>    ) >& make.out &
>    7.
>
>    [ time passes ]
>    8.
>
>    ssh <machine>
>    9.
>
>    uname -a
>
> FreeBSD test-1.dbm.q2w.spin.pm 13.0-STABLE FreeBSD 13.0-STABLE #0
> stable/13-05e4a34e4 GRAVITON  arm64
>
> --
>
> "Well," Brahmā said, "even after ten thousand explanations, a fool is no
> wiser, but an intelligent person requires only two thousand five hundred."
>
> - The Mahābhārata
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscribe at freebsd.org"
>
You need to be aware that the shallow clone hash will not include the
commit count which will be used in future security updates to make it easy
to check whether your system needs to be updated or not. A full clone does
require more space, but I was surprised at how little extra space it
requires. Warner  is updating his git mini-guide to point out this issue.
If you run STABLE, it's a really significant concern. You can convert the
shallow clone to a full one with "git fetch --unshallow". This will take
some time to run.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman at gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683