00:00:25 ant-x, Firewalls are a big umbrella protection. I always install a local caching nameserver such as bind or unbound but I don't want it to be publicly available as a resolver. Does it bind to the loopback or to the public network? With a firewall in place it does not matter. 00:00:53 Also I use fail2ban to reduce the log file size and noise and that works with the local firewall. 01:51:27 I'm still dealing with this weird pkgbase issue. for some reason, pkg fails to ever upgrade FreeBSD-src and FreeBSD-src-sys 01:53:17 I can remove the packages and completely nuke /usr/src, reinstall the packages which successfully brings that directory tree up-to-date, but as soon as I upgrade the base system, /usr/src falls out of date and fails pkg check 02:27:24 tm512: what's the error 02:31:51 pkg check gives an abundance of "checksum mismatch" and "missing file" errors, because what's in /usr/src and /usr/src/sys is from an older version of the packages 02:59:36 mostly unrelated to that, but I am curious to try something on stable/15, whereas I'm still on stable/14. wondering if the less painful route of migration is to go from my latest 14 boot environment up to 15, or dust off this 15 boot environment from early september and upgrade that to the latest 03:04:27 not sure if the 14 -> 15 migration via pkgbase is any less annoying than it was back in september, and I don't think I'm losing any configuration changes by rolling back 5 months. I guess upgrading my 15 BE is best as long as upgrading from ~15-ALPHA1 through pkgsrc isn't too big of a jump 03:04:41 er, s/pkgsrc/pkgbase 03:17:35 If Synth aborts while regenerating the flavor index because it encountered an error in a Makefile, is there anything I can do to resolve the issue, or is that an upstream issue that needs to be resolved? I just updated the ports tree before trying to install a port, and I got that error about lang/python-doc-pdf-a4 03:31:17 Not sure without seeing more of the actual error output, but was the port very recently updated? This smells like it may be someone forgetting about https://docs.freebsd.org/en/books/porters-handbook/testing/#make-describe 03:43:48 Regenerating flavor index: this may take a while ... 03:43:49 Scanning entire ports tree. 03:43:51 progress: 47.64% 03:43:52 culprit: lang/python-doc-pdf-a4 03:43:54 Scan aborted because 'make' encounted an error in the Makefile. 03:43:55 lang/python-doc-pdf-a4 (check /tmp/synth.scanner.35.out) 03:43:57 Flavor index generation failed: ports scan 03:44:29 That was the entire thing. But the .out file it mentioned doesn't exist, 03:58:26 Looks like that port was removed in https://cgit.freebsd.org/ports/commit?id=5e61a90f3a2307b70e48a2aab08c021b417eedd0 (less than 2 days ago). You may want tor trtry after refreshing your ports tree. 03:59:38 s/tor trtry/to retry/ 04:21:02 I don't get it. I do not have that port installed, and that directory does not exist in my ports tree. But Synth still aborts when it reaches that port in its scan. No idea where it is getting that from. 04:21:19 I'm using the git ports tree. 04:26:27 Ah. Apparently even if the port was deleted, python-doc-pdf-a4 still exists in the /usr/ports/lang/Makefile 04:33:06 Getting chrome for linux/widevine running on freebsd is so easy now 04:33:14 A few years ago you'd have to jump through hoops 04:50:16 fnix It is pretty awesome. 04:50:17 PaddyMac, that might be it, then. If you have a FreeBSD Bugzilla account, you should file a ports bug about that. 04:50:42 s/might be/probably is/ 04:51:55 I even reset my git tree. So yeah, I guess this does wrrant abug report. 04:52:18 (If you don't have a Bugzilla account, ask in #freebsd-ports for a committer to fix that, linking to the removal URL. 04:52:24 ) 04:57:14 wondering if my /usr/src pkgbase issue has anything to do with boot environments. is /usr/src excluded from boot environments created with bectl? 04:58:09 my current method for upgrading my system is to create and mount a new BE, then upgrade the BE using pkg -c, activate the BE, then reboot 04:58:12 Even if a commiter fixes the issue, it seems like Synth itself should be able to not choke on something like that. 04:59:02 though I think this issue with /usr/src never getting updated was happening even back when my upgrade strategy was to reboot into a new BE before running any upgrades 05:00:08 since when I first noticed that /usr/src was out of date, I think the files in there were from back in 2024 not long after I first installed FreeBSD on this machine 05:07:08 /usr/src has to be included because it's different between each release 05:14:30 it does seem to be a boot environment issue. /usr/src gets updated files inside the BE's root, but then when I actually boot into the new BE, zroot/usr/src, containing outdated sources, gets mounted over the updated /usr/src on the root 05:15:12 set zroot/usr/src legacy mounted? 05:16:08 what does that mean exactly? 05:18:00 wondering why I shouldn't just destroy zroot/usr/src 05:18:49 there doesn't seem to be a benefit in having one copy of the source tree shared between all of my BEs 05:45:48 for trying 15 I guess I'm best off just upgrading from my BE of stable/15 from around the release of ALPHA1. my only chance of trying the latest DRM drivers is if I jump over to 15 05:46:32 though last I heard, from this other person who's getting GPU hangs similar to what I'm getting, the 6.9 drivers don't fix the issue 05:49:46 I'm curious about the 6.10 drivers that got merged into drm-kmod master about a week ago 05:51:21 these GPU hangs significantly affect how I'm able to use my computer and if I were reasonable I probably should've abandoned FreeBSD by now with how long it's been with zero attention from the drm-kmod devs 05:54:36 tm512, legacy mounted refers to setting mountpoint=legacy. that stops zfs from automounting the dataset letting it be mounted in /etc/fstab instead if you should want 05:54:54 destroying it is valid but not preferable (what if you e.g. need to extract etcupdate from it) 06:00:31 well the zroot/usr/src dataset isn't being kept up to date properly. I have to remove the packages, nuke /usr/src, and reinstall the packages while zroot/usr/src is mounted 06:02:10 if I try extracting anything from it, unless I go through that hassle every time I update, I'm not going to get stuff that matches the running system 06:02:52 ah 06:02:58 then, nevermind i suppose, just destroy it 06:04:28 I could keep it up to date if I mount the dataset under the BE's mountpoint while I'm upgrading 06:05:53 but then I'm sharing a source tree between all BE's and if I have to roll back an upgrade for some reason I'm going to have to manually intervene to downgrade /usr/src 06:11:40 You could use git and switch between branches when upgrading/downgrading the system 06:13:10 then again I didn't follow the discussion 06:13:47 How come the pkg list is not publically viewable anymore? 06:13:54 Like this: http://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/ 06:55:34 it's huge 06:55:52 and also: why 07:31:40 for great justice /s 07:47:24 i am stuck on a "bhyve exited with status 4" on a host that i swear was running 09:49:17 well, I gave iwlwifi another shot here, now on 14.4-STABLE. it's just as busted as the last time I tried, unfortunately 09:53:02 does iwlwifi even support 802.11ac on the Wireless-AC 9260 card? I just noticed on the man page that ac is only supported on the 22000 generation and later, I'm guessing the 9260 is part of the 9000 series generation and not supported? 09:54:16 and is it the same situation on 15.0? I noticed the stable/15 branch has work that was never backported to 14 10:02:27 considering the state of FreeBSD's wifi support, maybe I just need to resort to wifibox again 10:16:44 I wonder if there are even any plans for iwlwifi to support the full capabilities of this card, and even if so, if it's just gonna be pushed off while 802.11ax support is prioritized 10:29:33 Ok, so my VM is still crashing without any clue of what's going on 10:29:35 in less than 24h it just stops working 10:29:37 console is a black screen, unreachable from the network 10:29:39 no kernel crash, nothing in logs, i checked netdata searching for any spike before crash and NOTHING 10:29:41 ram is available, not any cpu spike, no swap 10:30:15 lately i had some problems with syncthing amount of files open 10:34:14 i fixed the syncthing issue with : kern.maxfiles=500000 and kern.maxfilesperproc=131072 in /etc/sysctl.conf 10:34:36 if it makes my os not stable, shouldn't it trigger a kernel crash instead of a black screen ? 10:35:04 i enabled watchdogd, so if it crashes it should reboot : it does not 10:35:15 and /var/crash/ remains empty 10:35:37 (i tested a crash following the documentation and it worked with the simulation) 10:35:41 did anyone mention my nick? 10:36:03 (sysctl debug.kdb.panic=1) 10:36:11 i did 10:36:15 "black screen" 10:36:31 now you're here, help me figure it out :) 10:36:33 do you have a swap partitioen 10:36:46 yes i do, but as said it's not swaping 10:36:51 let me paste netdata graph 10:36:57 it swaps but very very light 10:37:17 was it set as dumpdev when you crashed the bus 10:37:33 the swap ? 10:37:35 yes 10:37:48 eoli3n: what's your VM environment? vBox or qemu? 10:37:48 i don't think so, how do i do this ? 10:38:05 you should `sysrc dumpdev=AUTO` and then reboot normally; in my case I have a network dump device which requires more complex setup and another server running freebsd at least 13 10:38:11 black i'm running a VM in "freebox os 4.9" this is a french isp router which allow to run vms 10:38:20 SarahMalik: yes, i did that 10:38:25 this is configured 10:38:39 well 10:38:53 do you have console access to the host platform (freebox os)? 10:39:17 i don't 10:39:21 no logs nothing 10:39:40 this is netdata swap usage : https://0x0.st/PcRE.png 10:39:47 each hole is a "crash" 10:39:55 that with netdata is of no use to us 10:40:11 (for the record: I have *@*/scottpedia on ignore because of unbelievable rudeness) 10:40:12 SarahMalik: i didn't get what you mean 10:40:49 netdata i'm assuming is coming from the freebox os, its "swap usage" is not of concern to us, we want to know if a swap partition is configured in the VM's "hard drive" 10:41:02 no, netdata is installed on freebsd 10:41:12 this is freebsd swap usage 10:41:14 uh, huh. weird. continue. 10:41:28 what's weird ? i don't get your point 10:41:39 nothing, i just didn't know that was a thing 10:41:44 what output have you for `dumpon -l`? 10:41:55 > vtbd0p2 10:43:38 and that partition exists? it's how big? i've found that my netdump server usually needs around 3 gigabytes each time any of its clients (both with over 8gb of ram by a long shot) crashes 10:44:36 534528 4194304 2 freebsd-swap (2.0G) 10:45:06 so your guess is that it is a kernel crash but no sufficient swap space to write ? 10:45:15 why do I found nothing after a reboot ? 10:45:19 not even a single file 10:45:34 ... might be. You'd need to video the VGA screen or serial console from during the crash 10:45:42 i do have one 10:45:50 but as said, it remains black after the "crash" 10:45:50 did it show it dumping and doing all that? 10:45:54 nop 10:45:58 nothing, black screen 10:45:58 oh what the blast 10:46:43 i tried to enable video output and select "video" in 5. from freebsd bootloader but i can't get something outside the console 10:46:48 maybe i miss something 10:46:59 "enable video output on the vm" 10:47:01 edit /etc/ttys, make one of the serial consoles a console, and have the thing boot to the serial console primarily 10:47:16 if freebox supports serial consoles; idk if it does 10:47:30 sorry, what does it try to do ? 10:47:39 i have console working before the crash 10:47:44 after the crash console is out 10:47:53 you have video console working before crash and then out after? 10:48:01 this is why i am recommending serial 10:48:09 nop sorry let's restart 10:48:15 i only have console output working 10:48:18 until it crashed 10:48:21 define console 10:48:25 let me paste 10:48:27 is this video console or serial console 10:49:03 serial 10:49:11 https://0x0.st/PcRk.png 10:49:12 this 10:49:43 I don't know, then, how you are configuring it that it becomes unusable when FreeBSD crashes 10:50:08 but since this isn't a PC that means everything I actually know goes out the window; do we have an arm64 expert on the party line? 10:50:14 i tried to enable checkbox "Ecran virtuel" which means "virtual display" and then boot freebsd with "video" from the bootloader, but when i open "display" button (the currently grey one) it says that i don't have any display 10:50:56 SarahMalik: i don't get what you mean, i just login to the console i pasted 10:51:03 right yes, I see that 10:51:13 but after the crash i don't even see anything in that console 10:51:48 you boot in the bootloader with serial console? which is what it should be for this to work 10:51:52 yes 10:52:00 and it works 10:52:01 until the crash 10:52:02 very weird 10:52:06 what's weird ? 10:52:21 what's weird is that something's happening that shouldn't be 10:52:27 which part N 10:52:28 ? 10:52:36 you mean the crash 10:52:41 the serial console not being written to when you crash? 10:52:53 yes, that's why i thing that this is not a kernel crash 10:52:57 think 10:53:17 but it is, you're literally flipping the crash the kernel sysctl, that crashes the kernel 10:53:33 yes that was to test that this is working 10:53:39 but it is, you're literally flipping the crash the kernel sysctl, that crashes the kernel... oh 10:53:44 ... sory about the repeat 10:54:02 the kernel crash test was just to see that i see files in /var/crash 10:54:09 so you're having a different crash, but it's not a normal panic 10:54:10 and i did, when i flip the crash myself 10:54:17 yes 10:54:18 i think 10:54:48 maybe what's crashing is the VM itself 10:54:57 then freebsd doesn't even know that it's crashing 10:54:59 okay; this is really offtopic for here then is there some way to set some debug options in the hypervisor, like can it save core when the VM dies, assuming the VM dies with this crash and not that it's stopping? 10:55:02 like unplugging the cable 10:55:33 problem is that i don't have anything on the freebox os, not log, no console, nothing 10:55:43 just that web interface with some buttons 10:56:10 ah... 10:56:21 then you'll need to speak to that vendor to try to figure out what's up 10:56:49 so we are absollutly sure now that this is not related to my freebsd install ? 10:57:49 not really, but it's gone outside our abilities to know what's happening. I know there are bugs in freebsd that can cause what I call "hard crashes", i experienced one with my GPU 10:58:06 but here you have a hypervisor that could conceivably be misbehaving 10:58:29 you'd need to have a word with freebox about what they do under circumstances like this 10:58:32 strange thing is that it worked for many weeks without problem 10:58:44 you changed nothing, this started happening? 10:58:45 yep, i'm creating an account on the forum to get help 10:58:47 thanks for your time 10:58:59 SarahMalik: i changed the sysctl part 10:59:03 let's try to revert this 10:59:08 ah 10:59:20 i had freebsd crashing because of syncthing 10:59:37 syncthing migrating to inotify will fix it 10:59:53 but for now i need to set higher maxfiles and mexfilesperproc 10:59:57 max 11:00:14 and that shouldn't be crashing the system, but it is 11:02:11 let's revert / reboot and see what happens 11:02:22 see you in a min 11:06:49 wait and see 11:07:17 i found someone which has the exact same problem as me since last freebox os upgrade : https://dev.freebox.fr/bugs/task/40675?string=VM&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=open&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto= 12:28:25 silly question but what's the practical difference between using `pkg -j`, `pkg -r` and `pkg -c`? 12:33:11 -j/-c will enter the jail/chroot, so configs of that jail/chroot apply (you can't use -j to update a jail that has no internet access), -r will work on the host (not sure if it looks for configs in that given root) 12:37:42 mm. so do they all cache packages internally? 12:38:08 or would -r allow pkg to do all of that on the host? 12:43:42 no idea on -r, maybe it behaves like -c just without doing the chroot, maybe it uses more stuff (like the cache dir) from the host 12:43:44 (in any case, thanks for the answer) 12:59:20 polarian re bouncer/vpn - "the number of people who tell me this" - not me :P took just an extra hour to figure out sasl and soju 13:45:26 The kids and their bouncers. What's wrong with just shelling in? 14:03:20 V_PauAmma_V Holy cow. I filed a bug before I went to bed. It was marked complete when I got up this morning. 14:03:42 I figured it would be at least Monday. 14:18:33 I read on Phoronix that there is a planned KDE Plasma desktop installer option planned for 15.1 to improve the laptop experience. Has there been any discussion of putting a wifibox installer option? Because honestly making sure wifi works on a laptop would make the laptop experience great. 16:05:11 i am stuck on a "bhyve exited with status 4" on a host that i swear was running 16:05:22 other efi vms are running 16:05:25 not sure what else to check 16:12:01 vkarlsen how's that? 17:01:18 Who is current head honcho for fuse filesystems in FreeBSD? Commit history is a bit too sparse to tell. 17:06:53 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293028 17:21:21 Have a ports tree? 17:26:01 A what? 17:26:50 anyone else use doas here? the conf file doesnt seem to work 17:27:16 seti: i do 17:27:27 i just have the rule permit nopass :wheel 17:27:36 yet my user in wheel still gets prompted everytime 17:28:16 permit keepenv nopass :wheel 17:28:21 is mine 17:30:35 didnt work either :( 17:30:51 manything in the logs? 17:31:06 is doas setuid properly? 17:33:30 looked in /var/log/auth.log didnt show anything strange 17:34:54 does it work after a password? 17:36:25 oh i should have specified, it works its just that i cant disable password 17:52:19 a bit dumbfounded, vidoas doesnt report syntax errors in the file when i write exit 17:53:58 oh now it worked 17:54:28 had to have at the top ONLY permit nopass user 17:57:34 but adding permit keepenv user as root somehow defeats the option above? 17:58:04 oh adding it under that one fixes it 19:52:59 lessless: Logging into a shell on the remote machine and running the client there 19:58:33 vkarlsen, I do that! In my IRC setup I pretty much have a Rube Goldberg of parts though and for almost anything I could say, I do that. :-) tmux+irssi+znc+irssi+perl+emacs+erc here. The advantage of a local client is that I can have it make a beep in certain conditions, my nick highlighted by certain people in certain channels. That's harder to do when only using a remote ssh client IRC. 20:00:49 That is a good point 20:01:41 seti, I think it is dangerous to be running X (or Wayland) programs as root. It's just a big attack surface. Therefore I think having "keepenv" is a bad thing. And also it often results in root owned files in the home directory which is not good. 20:02:35 tbh I always come back to https://xkcd.com/1200/ 20:05:17 I have a weekly cronjob to look for such files: 25 16 1 * * test -d $HOME && find $HOME -user root -ls 20:06:35 Not liking what I realized I was doing I contemplated changing that on the fly before posting to test ! -d $HOME || find ... but decided to leave it. The difference is whether cron itself ever sees the non-zero exit code or not. 20:07:21 A few years ago on the Debian side of things the maintainer there decided to patch cron so that it would complain if any command exited non-zero. It created quite a large kerfuffle since that is not traditional behavior. 20:09:42 It's not truly a critical cronjob and if there is ever any possibility that the required mount point is not present then I always add a protection to skip that job because otherwise the deluge of email from a system after some problem or maintenance task can be quite large. 20:10:29 dTal, I love that Randal says he switches to his brother's account in that case. That's very funny! 20:12:07 vkarlsen I'll wait until Apple drives Darwin fully into the ground before switching to a terminal client :) 20:15:26 lessless, (pedantically) I don't see how those two things are related. I don't see why they would be related! I think if you are using Darwin and it is broken then even command line programs will be broken too. (Just rhetorical musing...) 20:25:25 rwp this is going to be controversial, and I hope I won't get banned. I think macOS is the best desktop experience out there (for now). So I'm going to try to make the most out of it. Maybe this belongs to #freebsd-social :) 20:45:15 lessless, Definitely #freebsd-social is the place. You should join back in there! I don't think it will get you banned here. Because looking at almost every conference presentation on FreeBSD the presenter will almost always be running MacOS. That always feels wrong to me. If I were presenting at an Apple conference I would run Apple. If presenting at a BSD conference I would be using BSD. 20:47:22 I've got a 1000Gbps usb 3.0 j5Create adapter but freebsd only shows it at 100Gbps.... anyone else have issues like this? 20:54:25 sig`: you mean mbit 20:54:36 yeah sorry 20:54:36 heh 20:54:37 Do you perhaps mean 1000 Mbps rather than 1000 Gbps? If I were getting 100 Gbps on USB then I think I would be doing very well indeed. 20:56:03 I think a better question is what the driver supports and how to debug this and how to improve it. What does dmesg say when the driver loads? 20:57:29 I would also test this with alternative live-boot operating systems to see how the Linux driver for it reacts to it and how the OpenBSD driver reacts to it and gather data. 20:57:51 it works as 1000 on linux 20:58:02 need to download a live openbsd to try that 21:03:38 rwp: AX88179 + FreeBSD (axge) seems to be known issues 21:03:50 don't think I'll waste my time playing with this adapter anymore 21:04:06 https://forums.freebsd.org/threads/interface-flapping-on-ethernet-usb-adapter.96631/?utm_source=chatgpt.com 21:41:48 sig`, Bummer! Hopefully the situation will improve. (Not that I can help in any way other than hoping.) 21:43:36 rwp: yeah, I just need to pull the trigger on a new mini pc for what I'm doing. 21:44:06 this old machine just needs to be snapshotted over to something new... :) 21:45:54 The new generation of mini-pc systems are really nice! I have been enjoying the small handful of systems I am using. My desktop is now an old HP t740 with 4x displays but I still consider that a mini-pc but driving 4x displays which I am loving. I have 2x gen 2 ZimaBoard systems for random testing and they are nice. 21:46:53 An HP Elitedesk is one of the machines in my home lab setup. 21:54:20 I'm already running this as my main desktop: Beelink SER9 PRO AMD Ryzen AI 9 HX 370 21:54:38 would like another one for my server