-
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?
-
skered
I always just recreate the jail
-
mason
markmcb: Maybe a good opportunity to use Ansible or similar.
-
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.
-
markmcb
thanks!
-
lw
does anyone know if ROCm (AMD's Linux GPGPU API) works on FreeBSD? or if it could be ported (is it open source)?
-
lw
i found a few old forum threads but not real details
-
V-T60
Hello. Can someone tell me about MTK7601?
-
V-T60
Mediatek
-
V-T60
1. Can I host AP with it?
-
V-T60
2. Does FreeBSD at all support it good?
-
V-T60
^these are the most crucial for the moment
-
lw
i don't know the answer but my suggestion would be to boot from the installer image and see whether the card works
-
lw
that'll give you a definitive answer, i suppose
-
concussious
it doesn't work yet, but it is being worked on
-
concussious
you can follow/contribute to the discussion at bugs.freebsd.org/bugzilla/show_bug.cgi?id=264300
-
kyonsalt
FreeBSD 14 bootonly iso can't boot to rescue mode? I had to use FreeBSD 13 boot iso.
-
V-T60
concussious: but there are nothing about MTK7601?
-
V-T60
ugen1.3: <MediaTek802.11 n WLAN1.0 802.11 n WLAN> at usbus1
-
V-T60
Doesn't this mean that the thing will work fine?
-
lw
ugen is a generic USB device, it means the device won't work at all unless a more specific driver attaches
-
rwp
V-T60, I don't know but I might guess that wifibox would have it working.
github.com/pgj/freebsd-wifibox
-
VimDiesel
Title: GitHub - pgj/freebsd-wifibox: wifibox: Use Linux to drive your wireless card on FreeBSD
-
rwp
-
VimDiesel
Title: JRG Systems - 802.11ac on FreeBSD with wifibox
-
rwp
Another wifibox writeup specifically on the framework laptop:
xyinn.org/md/freebsd/wifibox
-
VimDiesel
Title: Fast & Stable WiFi with wifibox on FreeBSD | @fearedbliss
-
concussious
V-T60: that's why you should help him. his driver is called mt76. I'm sure he wants it tested on mt7601.
-
concussious
V-T60: everyone currently helping him has other chips in mt76 family
-
crb
how do I get the git hash for whatever is checked out in my /usr/src?
-
lw
crb: cd /usr/src; git log; the first entry is your git hash
-
crb
thank you
-
V-T60
concussious: ok, i will join, if it is about me being vital there
-
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
-
V-T60
oh, what does it mean for me?
-
concussious
that wifi is not the one
-
V-T60
oh, sad
-
V-T60
>USB wireless adapters are not supported.
-
V-T60
Plus my CPU isn't supported by bhyve...
-
concussious
to see what usb network options are available you can use "apropos usb | grep network"
-
V-T60
concussious: I can't find there anything about MTK7601
-
V-T60
So I will not able to run this Mediatek without bhyve/the device being not USB?
-
concussious
sorry, i meant, to see what supported usb networking hardware you could use, try "apropos usb|grep network"
-
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.
-
V-T60
these are all options for FreeBSd on my platform, right?
-
concussious
yeah, "apropos usb|grep network" on a freebsd console shows what usb network drivers are currently available on that system
-
V-T60
okay, sad that my device isn't in the list
-
ly2en
brace yourselves, kubernetes on freebsd is coming!
-
lw
ly2en: ugh terrible news
-
ly2en
for freebsd? Or k8s?
-
lw
kinda both but mostly for freebsd
-
lw
i hoped we'd avoid that crap
-
crb
how can I show the last snapshot on a zfs filesystem?
-
crb
or the dates of snapshots?
-
lw
i don't think zfs records the date of snapshots
-
lw
if you use something like sanoid it names the snapshots after the current date/time though
-
torindel
just use date+time in names of snapshots ^^
-
torindel
that will solve your problem of "whats last snapshot" too
-
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)
-
rtprio
there is the creation property in a snapshot
-
torindel
that will solve your problem of "whats last snapshot" too
-
torindel
not the last snapshot or that files where modified and snapshot is not "current data"?
-
torindel
missclick with up arrow ;p
-
rtprio
zfs list -t snapshot -o name,creation
-
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
-
torindel
so if you have @20240601, @test, @20240602 it would be fine if you do -I @20240601 name@20240602
-
torindel
as it will copy the snapshots in beetween anyway
-
torindel
(and dont forget you can always do fresh snapshot if you dont know whats latest)
-
torindel
fun part starts when you have "too much" snapshots, and it wont allow you to send/recv it all at once
-
crb
thanks
-
rtprio
what, why won't "it" allow you to send all at once?
-
torindel
rtprio: i'm snapshoting like every 15min on production systems
-
rtprio
that's... sounds excessive. but also doesn't answer my question
-
crb
cannot receive incremental stream: most recent snapshot of rz2_pool does not
-
crb
match incremental source
-
torindel
if i need to send/recv whole volume i have to limit myself to about 15000-20000 snapshots at once
-
crb
that's why I wanted to list the creation dates of snapshot if they didn't have a date in the name
-
torindel
rtprio: if you want to copy too much at a time it copies first X snapshots and dies with some dumb error
-
torindel
its problem if you try to recursive send volumes
-
torindel
as it will copy X snapshots from first one, and other ones will still be at the original one
-
torindel
crb: did you independently snap on source and destination?
-
torindel
crb: try deleting latest snapshot on destination maybe?
-
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
-
crb
but I think I fixed it using the -F flap
-
crb
but I think I fixed it using the -F flag
-
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