Re: What happened to 16?
- Reply: Chris : "Re: What happened to 16?"
- In reply to: S. Ross Gohlke: "Re: What happened to 16?"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 08 Dec 2025 20:48:39 UTC
On 12/8/25 13:03, S. Ross Gohlke wrote:
>
> On 12/8/25 01:37, Chris wrote:
>> I just got a new laptop and tried to boot 13.5,14 and 15
>> but it hangs at the video -- something about loosing contact
>> with sc. So I went to get a copy of 16. But download.freebsd.org
>> doesn't know where it is. All the links to it from FreeBSD.org
>> return 404.
>>
>> So where is it?
>>
>> Thanks! :-)
> You can generate your own artifacts from pkgbase packages installed in
> an alternate root.
>
> Add the package repository configuration:
>
> FreeBSD-base: {
> url: "pkg+https://pkg.FreeBSD.org/${ABI}/base_latest",
> mirror_type: "srv",
> signature_type: "fingerprints",
> fingerprints: "/usr/share/keys/pkg",
> enabled: yes
> }
>
> To generate src.txz:
>
> # env ABI=FreeBSD:16:amd64 pkg -r /mnt/src install FreeBSD-set-src
> # tar -acof /var/tmp/src.txz -C /mnt/src usr/src
>
> To generate base.txz:
>
> # env ABI=FreeBSD:16:amd64 pkg -r /mnt/base install FreeBSD-set-base
> # mtree -deiU -f /etc/mtree/BSD.root.dist -p /mnt/base
> # mtree -deiU -f /etc/mtree/BSD.usr.dist -p /mnt/base/usr
> # tar -acof /var/tmp/base.txz -C /mnt/base .
>
> The mtree commands may or may not be necessary, but in my case I
> expect /usr/obj to exist.
>
> If you want to pretend like this never happened, remove the package
> repository configuration and database ($PKG_DBDIR/repos/FreeBSD-base)
> once you have the artifacts.
On second thought, the local pkg database will still be "polluted". You
probably want to delete the packages first.
# env ABI=FreeBSD:16:amd64 pkg -r /mnt/src delete FreeBSD-set-src
# env ABI=FreeBSD:16:amd64 pkg -r /mnt/src autoremove
# env ABI=FreeBSD:16:amd64 pkg -r /mnt/base delete FreeBSD-set-base
# env ABI=FreeBSD:16:amd64 pkg -r /mnt/base autoremove
This might have consequences for your regular installation, so use with
caution.
Honestly, you want a dedicated PKG_DBDIR too, but that entails extra
complications.
> You will still have the packages, which you could exclude from your
> normal cache by setting PKG_CACHEDIR in the above pkg commands.