Date: Sat, 20 Jan 2024 12:43:08 -0800 From: Mark Millard <marklmi@yahoo.com> To: FreeBSD-pkgbase@freebsd.org Subject: Re: https://wiki.freebsd.org/PkgBase and -r base vs. -rFreeBSD-base on the page; more Message-ID: <34E7E369-3FA8-4CA6-8EF7-00A28A2DCC05@yahoo.com> In-Reply-To: <C3C893F6-E095-4D69-AC9D-E25798D1E00C@yahoo.com> References: <C3C893F6-E095-4D69-AC9D-E25798D1E00C@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 19, 2024, at 22:07, Mark Millard <marklmi@yahoo.com> wrote: > I've just done my first Initial setup. I've some notes. >=20 > https://wiki.freebsd.org/PkgBase has an odd mix of -r base vs. -r = FreeBSD-base . >=20 > Since the notes use: >=20 > QUOTE > # mkdir -p /usr/local/etc/pkg/repos/ > # cat <<EOF >/usr/local/etc/pkg/repos/base.conf >=20 >> base: { > END QUOTE >=20 > I expect that -r base is the intent. When I cross checked by > trying a -r FreeBSD-base the result was: >=20 > # pkg upgrade -r FreeBSD-base > No repositories are enabled. >=20 > I set this up via a RPi5 from a prior snapshot (2023-Jan-11's) > based media for main. >=20 >=20 > I ended up with: >=20 > # ls -Tlodt /boot/kernel*/kernel > -r--r--r-- 1 root wheel - 18194200 Jan 19 18:22:51 2024 = /boot/kernel.GENERIC-NODEBUG/kernel > -r--r--r-- 1 root wheel uarch 17731376 Jan 11 06:27:12 2024 = /boot/kernel/kernel >=20 > so the default kernel directory was not actually updated. I'll note that when I set up stable/14 pkg base on the stable/14 media /boot/kernel/* updated in the more normal way, with *.pkgsave files. My guess is that /boot/kernel.GENERIC-NODEBUG/ is normal for main [so: 15 now] and that /boot/kernel/ was odd by not ending up with updated files and *.pkgsave files for the 15 DEBUG kernel. > https://wiki.freebsd.org/PkgBase does not make the intent > for this clear. Two mv's? mv and a cp -aRx ? I did: >=20 > # mv /boot/kernel /boot/kernel.old > # cp -aRx /boot/kernel.GENERIC-NODEBUG /boot/kernel >=20 > and rebooted yet again to get the new kernel. That got > me to: >=20 > # uname -apKU > FreeBSD generic 15.0-CURRENT FreeBSD 15.0-CURRENT = main-n267654-dfe30e41967f GENERIC-NODEBUG arm64 aarch64 1500011 1500011 >=20 > But I'm unsure what is expected for /boot/kernel.GENERIC-NODEBUG . >=20 >=20 > pkg would not initially bootstrap. I added a: >=20 > /usr/local/etc/pkg/repos/FreeBSD.conf >=20 > in order for pkg to bootstrap and removed it after the > bootstrap. pkg then continued to work based on > /etc/pkg/FreeBSD.conf and /usr/local/etc/pkg/repos/base.conf . >=20 >=20 > Other notes: >=20 > The intent is to have a "test official build" media for > main. I prefer to submit problems based on official builds > instead of my personal ones that are not fully standard. > Also, I learn if it is "just my build" for any oddities > that I can not replicate for an official build. >=20 > I'll likely do similarly for a stable/14 snapshot media, > also created via the RPi5. >=20 > Now that armv7 base_latest has shown up, I may do similarly > for that type of context as well. >=20 Other notes: The base naming patterns were: For main: FreeBSD-*-15.snap* with Version 15.snap* For stable/14: FreeBSD-*-14.snap* with Version 14.snap* I do not know if 14.*-STABLE should lead to: FreeBSD-*-14.*.snap* with Version 14.*.snap* or not. Nor if 15.0-CURRENT should lead to: FreeBSD-*-15.0.snap* with Version 15.0.snap* or not. May be 15 gets the .0 only once it is past CURRENT (and past PRERELEASE?)? (The above is not an objection to what is now present.) It does appear messy to figure out what specific commit a base was built based on without installation and use of the likes of uname -KU or fetching and examining files. The likes of: https://pkg.freebsd.org/FreeBSD:14:aarch64/base_latest/?C=3DM&O=3DD does not list a plain text file with such information. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34E7E369-3FA8-4CA6-8EF7-00A28A2DCC05>