does anybody know of an ELI5 (explain like im 5 years old) for understanding whats using swap?

I've got 128GB RAM, only 1/2 used, and something is swapping out 6G which makes no sense to me

I'm not concerned about the swap per se, I'm assuming that the swap usage means my builds are running through disk and not in tmpfs as expected

ps wwauxd | less -pW ?

not good tho

I came up with this

doas ps auxwwd | awk 'NR==1{print};$8 ~ /W/'

which shows no processes using significant swap at all

is the swap currently being used or WAS it used?

its still showing up as used in top

not familiar with top's internals, but it may just be reporting how much was used (and is therefore still there even if there's nothing being written to it)

dch: what does swapinfo say?

I'm pretty sure top just reads sysctls for most things

8% used which matches what top says too

and yet top ... -w (show approx swap usage per process) shows nothing

I guess it is probably tmpfs that are swapping out, but there shouldn't be any need to here

lovely 128g ram

yeah I make heavy use of tmpfs stuff for work, everything is faster

tdd: saw your email, do you need me to reply to it or would you be okay with joining #freebsd-irc ?

Hiya! Just started playing with FreeBSD recently. I was poking at PkgBase, and I tested it by upgrading from 14.0-RELEASE to 14.1-RELEASE and it worked well! Now that that's completed, `pkg update` is still updating from the default pkg repo as well as the FreeBSD-base one I added. I'm trying to understand what my update workflow would look like, would I routinely check for outdated packages on the `FreeBSD-base` repo, or would the

defaut repo on 14.1 give me the same results?

adammo: i'm not sure what your question is. what do you mean by the default repo giving you the same results? i haven't tried pkgbase on non-CURRENT, but have a few CURRENT boxes that are managed via pkgbase. there i just pkg update && pkg upgrade and things handle itself. i'm not sure if it's any different on 14.x, but does that help?

yeah I think that helps. I think I'm just a bit confused conceptually if now I effectively have two repos with the same packages? With freebsd-update and pkg, as a noob, the distinction was clear to me. I used pkg to upgrade whatever I have installed and freebsd-update to do release updates.

the default pkg repo is whatever is built from the ports tree, so things like nginx, apache, your browser, etc. pkgbase is basically the same thing, except instead of building ports, it builds freebsd's base as a collection of fine-grained packages, so you wouldn't be using freebsd-update anymore to update the base system, instead it would all be handled by a single tool, which is pkg

so one repository are the ports, and one is your base system

unless you need to specify which software you want to upgrade, a pkg upgrade should handle both gracefully (or at least, that's the idea)

ah okay, so the base system packages don't exist in the default ports then?

yeah

sweet, I get it now, thanks!

I decided to upgrade to 14.2 with freebsd-update. how avoid problem with drm-kmod driver?

disable in /etc/rc.conf?

does system boot with disabled driver to console?

boots yes

and after kernel install make a driver from ports and voila

drm-kmod driver for 14.1 and 14.2 is the same if you install it from official repository

it will change within 3 months