Date: Fri, 3 Apr 2026 11:53:28 -0700 From: Mark Millard <marklmi@yahoo.com> To: void <void@f-m.fm>, freebsd-pkgbase@freebsd.org Subject: Re: pkgbase on armv7 (rpi2b v1.1) questions Message-ID: <3468c201-6efc-45e2-81d1-3f414da6d35f@yahoo.com> In-Reply-To: <ac-c3zvDsDw7r_Gj@int21h>
index | next in thread | previous in thread | raw e-mail
On 4/3/26 03:56, void wrote: > Hi, > > On systems like these, a bootable image is provided for convenience > with default logins. I'm guessing these images aren't pkgbasified. Reminder: These armv7 images are normally UFS, not ZFS based. For reference for others that might read: https://github.com/FreeBSDFoundation/pkgbasify is being implicitly referenced here. > > [] is pkgbase expected to work on armv7? if so, are there instructions > somewhere showing how? I converted to having pkgbase boot kernels and boot worlds as my context long ago, not in modern times relative to pkgbase being involved in an official release and other such tooling (as far as I knew at the time). So I'm not going to comment for this, at least for now. > > [] if yes, can one follow -current-nodebug with pkgbase? In general for main (a.k.a, CURRENT) [so: 16 as stands], not just for armv7: Kernel: pkgbase provides both debug and non-debug kernels under different names. (There can be more kernels as well.) World : pkgbase only provides a debug world for main and non-debug for the rest. main's pkgbase kernel (path) names: /boot/kernel/ /boot/kernel.GENERIC-NODEBUG/ /boot/kernel.GENERIC-MMCCAM/ The first is the debug kernel. I use /boot/loader.conf to control which I'm using. (I've never used the MMCCAM one.) I normally use the non-debug kernel. For non-main: /boot/kernel/ /boot/kernel.GENERIC-DEBUG/ /boot/kernel.GENERIC-MMCCAM/ So, here the first is the non-debug kernel, whichis what I nonnormally use for non-main as well. For at least amd64 for main there is also: /boot/kernel.MINIMAL/ As for a debug main world's overhead: the asserts and jemalloc internal check overheads and such can take more time than a debug kernel. But I'm not going to try any sort of general workload breakdown analysis for tradeoffs. One thing that can be done is to have the likes of: # ls -l /etc/malloc.conf lrwxr-xr-x 1 root wheel 10 Mar 29 10:38 /etc/malloc.conf -> junk:false Notably, if you build port-packages via poudriere(-devel), it is the poudriere jail's world that matters for the bulk build activity, not the boot world. Similarly for chroot use and jail use in general. Thus bulk builds of port-packages need not suffer the performance tradeoffs of a debug world even on systems that boot a debug world. But, so far as I know, there are no pre-built non-debug main worlds that are officially distributed, even as a non-RELEASE-status build. Also, as far as I know, there are no pre-built debug non-main worlds that are officially distributed, even as a non-RELEASE-status build. > > I'm not at all keen to pkgbase all the things, but think it'd be ideally > suited to very low powered machines > It is my understanding that FreeBSD 15.1 is intended to add more normal types of RELEASE builds for armv7, like other platforms have in 15.0. -- === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3468c201-6efc-45e2-81d1-3f414da6d35f>