so to update my question about p9fs the other day, i've been using it in one VM and have not had any problems so far, seems to work pretty well

just ran into another ZFS panic but couldn't get a vmcore since i think it dropped into ddb

seems like some recent change broke zfs a lot

now it's hung (no disk activity) trying to copy a file

can't read the file with rsync either, it starts at 300MB/s, then gradually drops to 0 around 3.5GB

guess i need to restore from backup send open a new PR

ok, now went to reproduce it and the problem is magically fixed

i'm pretty sure some recent change in main has broken zfs though

maybe i'll wait to upgrade to this latest pkg set

kevans: i am unsure because no one on fs@ has reported any problems

and i am using zfs native encryption which we know has been completely broken since it was introduced, but it's disabled on nearly all my filesystems

(i only can't disable it on the root filesystem because i'd have to recreate the pool)

sadly i can't reproduce the panic i had early when starting a bhyve vm and because system was configured to drop into ddb instead of writing a vmcore i don't have a dump

couldn't get a local console to dump it from ddb?

kevans: i didn't even noticed it panicked until i rebooted and noticed the ddb trace in dmesg from the previous boot

and apparently i forgot to save it

oof =(

i've fixed the sysctl config to not drop to ddb now though so at least if it happens again i should have a core

should probably reboot and get a vmcore for 282281 at least

need to upgrade my rpis first though, this is always exciting due no serial console

1!fuchsia /home/lexi# pkg upgrade

ld-elf.so.1: Shared object "libmd.so.6" not found, required by "pkg"

fuck sake

someone remind me why i use freebsd

(yes, i know, the answer is linux is worse)

Because pkg-static exists for such occasions.

rwp: i know about pkg-static, but this libmd issue has been haunting me for weeks

and the annoying part is that simply upgrading does not fix it

you have to know the magic incantaiton, 'pkg(-static) upgrade -f'

But, but, but... ldd: /usr/local/sbin/pkg-static: not a dynamic ELF executable

yes, but my point is, 'pkg-static upgrade' does not fix the problem

you have to use 'pkg-static upgrade -f'

because pkg for some reason does not realise some packages have to be upgraded due to sovers changes

In FreeBSD the upgrade with the -f option is pretty well known though. Always use it after a major release upgrade for example.

in other news

Checking for out of date packages:

FreeBSD-dtb-15.snap20240917032829 orphaned: base

FreeBSD-syscons-15.snap20240917032829 orphaned: base

what happened to these packages, did they get removed?

Saying would be knowing, not knowing, cannot say.

i mailed freebsd-pkgbase@

possiblle!

i have a survey

1) do you have 'pkg orphans' comamnds on your freebsd system?

2) what freebsd version do you use?

ivy: yes—all my systems currently running 15.0-CURRENT.

thanks, seems like this question was prompted by someone who had a custom pkg.conf

and 'pkg orphans' is an alias rather than a builtin command

Aye, 'tis an alias.

what photo viewer is best in gnome enviroment?

ristretto, xxy

does freebsd have a SIIT-DC?

remember back in the 1980s when every minicomputer had a microcomputer on top of it to act as system console? i.imgur.com/o3aKWY2.jpeg

that is a funny analogy. but apt

ivy: linux iirc has such feature of plug and play functioning as a console. something to do with usb hub originally...

that is really a console. It reminds me I named one of projects wrong. it may be confusing that I used the word, "console" in it.

does freebsd have an API for looking up the SIIT-DC prefix?