00:54:41 <markmcb> for poudriere jails, when an upgrade (e.g., 14.0 to 14.1) occurs, is it best to create a new jail and rebuild everything, or ok to just upgrade the existing jail and incrementally build?
01:32:11 <skered> I always just recreate the jail
02:25:30 <mason> markmcb: Maybe a good opportunity to use Ansible or similar.
02:31:44 <rwp> markmcb, In theory the result should be the same. If one were to experiment and upgrade copy A and create new B and then compared the files in them I expect any differences to be unintended differences.
02:33:48 <markmcb> thanks!
12:19:26 <lw> does anyone know if ROCm (AMD's Linux GPGPU API) works on FreeBSD?  or if it could be ported (is it open source)?
12:19:33 <lw> i found a few old forum threads but not real details
14:30:50 <V-T60> Hello. Can someone tell me about MTK7601?
14:30:58 <V-T60> Mediatek
14:31:05 <V-T60> 1. Can I host AP with it?
14:31:15 <V-T60> 2. Does FreeBSD at all support it good?
14:33:27 <V-T60> ^these are the most crucial for the moment
14:35:26 <lw> i don't know the answer but my suggestion would be to boot from the installer image and see whether the card works
14:35:33 <lw> that'll give you a definitive answer, i suppose
14:48:55 <concussious> it doesn't work yet, but it is being worked on
14:52:59 <concussious> you can follow/contribute to the discussion at bugs.freebsd.org/bugzilla/show_bug.cgi?id=264300
16:12:03 <kyonsalt> FreeBSD 14 bootonly iso can't boot to rescue mode? I had to use FreeBSD 13 boot iso.
16:38:57 <V-T60> concussious: but there are nothing about MTK7601?
16:45:55 <V-T60> ugen1.3: <MediaTek802.11 n WLAN1.0 802.11 n WLAN> at usbus1
16:46:03 <V-T60> Doesn't this mean that the thing will work fine?
16:46:39 <lw> ugen is a generic USB device, it means the device won't work at all unless a more specific driver attaches
17:05:38 <rwp> V-T60, I don't know but I might guess that wifibox would have it working.  https://github.com/pgj/freebsd-wifibox
17:05:39 <VimDiesel> Title: GitHub - pgj/freebsd-wifibox: wifibox: Use Linux to drive your wireless card on FreeBSD
17:05:59 <rwp> Good reference to wifibox: https://jrgsystems.com/posts/2022-04-20-802.11ac-on-freebsd-with-wifibox/
17:06:00 <VimDiesel> Title: JRG Systems - 802.11ac on FreeBSD with wifibox
17:06:35 <rwp> Another wifibox writeup specifically on the framework laptop: https://xyinn.org/md/freebsd/wifibox
17:06:36 <VimDiesel> Title: Fast & Stable WiFi with wifibox on FreeBSD | @fearedbliss
17:45:52 <concussious> V-T60: that's why you should help him. his driver is called mt76. I'm sure he wants it tested on mt7601.
17:46:55 <concussious> V-T60: everyone currently helping him has other chips in mt76 family
17:52:55 <crb> how do I get the git hash for whatever is checked out in my /usr/src?
17:53:12 <lw> crb: cd /usr/src; git log;  the first entry is your git hash
17:53:49 <crb> thank you
17:59:31 <V-T60> concussious: ok, i will join, if it is about me being vital there
17:59:47 <concussious> V-T60: wow, so it turns out, bz is porting the mt76 driver from linux, where they have a mt76 driver for everything the mtk76?? family *except* mtk7601, which has it's own driver
18:00:25 <V-T60> oh, what does it mean for me?
18:01:00 <concussious> that wifi is not the one
18:04:04 <V-T60> oh, sad
18:04:06 <V-T60> >USB wireless adapters are not supported.
18:04:16 <V-T60> Plus my CPU isn't supported by bhyve...
18:04:32 <concussious> to see what usb network options are available you can use "apropos usb | grep network"
18:17:46 <V-T60> concussious: I can't find there anything about MTK7601
18:18:05 <V-T60> So I will not able to run this Mediatek without bhyve/the device being not USB?
18:20:22 <concussious> sorry, i meant, to see what supported usb networking hardware you could use, try "apropos usb|grep network"
18:21:29 <concussious> as in, im saying, we have some options you can probably find for <$10, but mtk7601 is not nor is likely to become one of them.
18:25:16 <V-T60> these are all options for FreeBSd on my platform, right?
18:34:34 <concussious> yeah, "apropos usb|grep network" on a freebsd console shows what usb network drivers are currently available on that system
18:35:27 <V-T60> okay, sad that my device isn't in the list
19:30:58 <ly2en> brace yourselves, kubernetes on freebsd is coming!
20:01:59 <lw> ly2en: ugh terrible news
20:06:14 <ly2en> for freebsd? Or k8s?
20:14:25 <lw> kinda both but mostly for freebsd
20:14:29 <lw> i hoped we'd avoid that crap
21:33:20 <crb> how can I show the last snapshot on a zfs filesystem?
21:35:23 <crb> or the dates of snapshots?
21:35:50 <lw> i don't think zfs records the date of snapshots
21:36:09 <lw> if you use something like sanoid it names the snapshots after the current date/time though
21:42:38 <torindel> just use date+time in names of snapshots ^^
21:43:20 <torindel> that will solve your problem of "whats last snapshot" too
21:44:00 <crb> I do that most of the time but there are a few times where I didn't and when doing a send/recieve zfs reports and issue with not the last snapshot (I think)
21:45:16 <rtprio> there is the creation property in a snapshot
21:45:29 <torindel> that will solve your problem of "whats last snapshot" too
21:45:36 <torindel> not the last snapshot or that files where modified and snapshot is not "current data"?
21:45:45 <torindel> missclick with up arrow ;p
21:45:56 <rtprio> zfs list -t snapshot -o name,creation
21:48:25 <torindel> crb: even if you branch snapshots in a tree (instead of single line) you shouldnt have problems with send/recv as long as you -I @ from shared snapshot to anything newer than what you have
21:49:31 <torindel> so if you have @20240601, @test, @20240602 it would be fine if you do -I @20240601 name@20240602
21:49:47 <torindel> as it will copy the snapshots in beetween anyway
21:51:07 <torindel> (and dont forget you can always do fresh snapshot if you dont know whats latest)
21:52:58 <torindel> fun part starts when you have "too much" snapshots, and it wont allow you to send/recv it all at once
21:53:10 <crb> thanks
21:55:42 <rtprio> what, why won't "it" allow you to send all at once?
21:56:19 <torindel> rtprio: i'm snapshoting like every 15min on production systems
21:56:53 <rtprio> that's... sounds excessive. but also doesn't answer my question
21:56:53 <crb> cannot receive incremental stream: most recent snapshot of rz2_pool does not
21:56:53 <crb> match incremental source
21:56:55 <torindel> if i need to send/recv whole volume i have to limit myself to about 15000-20000 snapshots at once
21:57:11 <crb> that's why I wanted to list the creation dates of snapshot if they didn't have a date in the name
21:57:56 <torindel> rtprio: if you want to copy too much at a time it copies first X snapshots and dies with some dumb error
21:58:13 <torindel> its problem if you try to recursive send volumes
21:58:51 <torindel> as it will copy X snapshots from first one, and other ones will still be at the original one
21:59:37 <torindel> crb: did you independently snap on source and destination?
22:00:33 <torindel> crb: try deleting latest snapshot on destination maybe?
22:10:04 <crb> torindel and there in lies the problem how do you determine the latest snapshot if you didn't use the date in the name
22:10:15 <crb> but I think I fixed it using the -F flap
22:10:17 <crb> but I think I fixed it using the -F flag
22:31:12 <torindel> sidenote if anyone is interested: there arent any slowdowns/hickups during work/snapshoting when you have excessive ammount of snapshots, only downside is that it gets a WHILE to get list of all snapshots (esp if filesystem system is under higer i/o), althroo if you know snapshot name cd .zfs/snapshot/name is fine