00:28:45 no OS is good, but FreeBSD is among the lesat crap 00:40:02 The OS is the least important part of what you do daily on a machine. :) 00:40:27 is there a specific channel for pkgbase stuff? 00:46:48 I'm attempting to pkgbasify on 15 b5 on aarch and I'm getting segfaults when installing /some/ packages - https://gist.github.com/nreilly/a43b6b7eb94ece81800faf6b39e89eca 00:49:42 entrop: There's a mailing list: https://lists.freebsd.org/subscription/freebsd-pkgbase 00:52:35 i installed FreeBSD UNIX 14.3 on a 2020s ThinkPad and tried to boot it with Slackware 15's GRUB2 which worked on previous. This doesn't. Is that because of 'soft journalling' I need to opt-out manually in the installation (older GRUB2 from 2022)? 00:55:24 darwin: https://wiki.freebsd.org/MasonLoringBliss/BootingFreeBSDfromUEFIGRUB 00:55:44 Multibooting is easier with UEFI, so might as well embrace it. 00:56:52 i've rarely had problems multi-booting since 1997... not going to use UEFI until it's the only option 00:57:21 the problem appears to be some update to FFS/UFS2 GRUB2 didn't have three years ago 00:57:52 Hmm, I compiled pkg manially from ports, getting me to 2.4.2 (vs 2.3.1_1) and it seems to be working now 01:44:49 Reinhilde: you aren't wrong! 02:10:53 yeah 04:42:33 A question. If I use en EFI partitiom and boot with UEFO, do I also need a partition of type freebsd-boot? Or if the kernel and all necessary stufff inside the EFI image? 04:46:02 OK, I googled a bit and it seems that I don't need a freebsd-boot partition when using EFI. 04:46:55 You can try that in a VM to be sure, if your hypervisor can emulate (U)EFI. 04:49:32 But this guide, https://www.c0ffee.net/blog/freebsd-full-disk-encryption-uefi/, seems to suggest having a separate freebsd-boot-partition containg kernel and kernel modules and copy /boot/boot1.efi to the efi partition, so I'm a little bit confused. 04:49:50 andreas303: freebsd-boot is an extra partition for when you're on GPT to accomodate the fact that GPT doesn't have reserved space after the MBR. It's not a terrible practise to include them AND an ESP so that you can boot either way. 04:50:16 andreas303: It's the FreeBSD equivalent of https://en.wikipedia.org/wiki/BIOS_boot_partition 04:50:42 andreas303: I talk about partitioning some here: https://wiki.freebsd.org/MasonLoringBliss/ZFSandGELIbyHAND 04:51:21 afk a bit, but I'll check back before bed in case there are questions 04:51:40 mason: Thx! I will check out the wiki. 08:42:40 good morning folks! does brave browser and widevine work together in freebsd or must I run chromium to get widevine to work? 09:03:17 nwe: works out of the box with just the www/linux-brave port 09:06:44 kenrap: today I have installed chrome with pkg install chromium and foreign-cdm 09:07:30 kenrap: will install it from linux-brave then :) thanks! 09:08:09 Sure thing. Amazon prime video works fine on it. 09:08:32 Just make sure it's enabled in the settings. 09:35:41 so this might be a little nutty, but theres something I want to solve. I have sshd set up to essentially only serve sftp, this is so I can offer basic file access to a couple of users. I have it set up to chroot the user into their own directory. However, I also want to give each user access to the same read-only filesystem. 09:35:59 would it be crazy to use nullfs mounts in each user directory? 09:37:07 crazier than that, would it be stupid to write a script that automatically mounts nullfs for each user directory on startup. 12:39:52 specialbomb: sounds like you'd want to install filesystems/sshfs and use that remotely mount each respective user directory 14:01:12 nullfs mounts sounds ideal for this 14:01:49 nullfs? 14:01:50 entrop: pkg 2.4.1 or newer should address your segfault. 14:02:21 man.freebsd.org/nullfs 14:02:48 use it like `mount_nullfs /usr/ports /some/where/else/ports` or put it in fstab so its always available 14:16:43 ugh, i'm running Home Assistant on FreeBSD and i was able to fix it only today. they started requiring PyNaCl 1.6.0 and it wasn't building on FreeBSD. today they released 1.6.1 and with MAKE=gmake i was able to build it... 14:18:04 i hate that project. they are worse than linux monoculture. they target a specific OS (their own OS) and they have versionitis too. every package is always bleeding edge, latest version only 14:26:47 hjf: hah, I'm literally doing this right now 14:27:14 I did it in a venv with pip and didn't run into this PyNaCl issue somehow 14:27:26 but I know the 'official' way is to just use their Docker container at this point, not the Python package 14:28:28 I seem to have things running okay in the venv, but it complains about a few things: Python 3.11 is deprecated, webrtc-noise-gain doesn't like FreeBSD, they're overly permissive with josepy versions and it has a breaking change in 2.0.0 14:57:31 specialbomb, why not just set those users' shell to scponly and add them to the same group for the shared filesystem? 14:58:40 People make shit too hard. 15:07:17 hodapp: no, the container isn't supported either AFAIK. ONLY the "HA OS" version on a raspberry pi for now. 15:07:32 you can check my blog, i've documented some stuff on how to make it work 15:07:33 hjf: the container isn't supported? wtf. 15:07:55 I'm gonna keep trying to use the Python package but we'll see how that goes 15:08:03 hodapp: https://blog.hjf.com.ar/en/2025/01/10/home-assistant-issues-on-freebsd/ 15:08:05 thanks 15:08:42 also this one for py 3.12: https://blog.hjf.com.ar/en/2024/10/19/fixing-home-assistant-2024-10-on-freebsd/ 15:09:04 also this one for today's fix: https://blog.hjf.com.ar/en/2025/11/11/fixing-home-assistant-and-pynacl-on-freebsd/ 15:09:56 i can't believe how fast Wordpress runs now 15:09:58 I wonder why you ran into PyNaCl issues and I didn't 15:10:09 hodapp: are you in the latest version? 15:10:20 i'm running 2025.11.1 now 15:10:26 and you need py 3.12 for that one 15:10:56 oh, no, pip install homeassistant got me 2024.3.3 it turns out 15:11:22 yes, it's the newest you can use in py 3.11 15:11:34 that must be why 15:11:53 hodapp: create yourself a new venv with py312 and start using uv, follow my guide here https://blog.hjf.com.ar/en/2024/10/19/fixing-home-assistant-2024-10-on-freebsd/ 15:12:05 you can keep your old HA venv 15:12:25 uv was gonna be my next attempt. it's not a big real to recreate the venv though 15:12:33 real? deal. whatever. 15:12:50 yeah but you need to do things in a specific way for it to make HA happy 15:19:03 anyways after tuning mysql and installing memcached, my blog now renders in 80ms 15:19:51 i run woocommerce for my shop too. the admin page was doing like 250 queries for every page load. 15:20:09 after installing memcached, it's down to 40-60 queries 15:26:42 CrtxReavr: this is what im currently doing. the problem I want to solve really is to transparently give access to a filesystem for everyone, while simultaniously having separate chroots. 15:30:40 in the curren set up, lets say this share dir is called share, and each user A B and C has a directory of the same name. A, B, C and share all have to be in the same root dir if I dont use nullfs. I think this is a problem because now each user that logs in can see dir entries for other users, and that is not ideal. I can set up permissions obviously amd I have, but I wouldnt want an individual user aware of anyone else being on the system at all 15:32:33 if I nullfs mount media into A/media, B/media C/media, then each user gets their own chroot and has no idea anyone else is present on the system 15:37:41 hjf: okay that's a pro for you man 15:54:13 hello, I know there is an sql lite database por ports... I can't see any log file tough. I wonder if I can query that database to know when pkg was used to upgrade packages, the previous version and the version installed. Is that possible? 15:56:05 I think the whole point of sqlite is that it's a user application, not a client/server setup with a daemon writing logs. 15:57:28 If you want the daemon with logs, then you probably want MySQL or PostgreSQL. 15:58:33 Otherwise, then I guess you need to do the logging in your application. 15:59:58 I thought he was asking if FreeBSD uses an sqlite database for tracking package/port update dates/times that he can query. 16:00:34 'pkg info ' will show the install date of the current version at least. 16:00:48 * CrtxReavr shrugs. 16:00:49 Maybe. 16:02:15 With my logging setup, I can just search 'pkg-static' in /var/log/messages to see dates. 16:05:18 I just noticed that he ping-timed-out anyway 16:07:12 * Capio|Yaazkal oof, internet went down. Can't see if anyone answered my question 16:08:18 Capio|Yaazkal: Are you sure you checked /var/log/messages? Did you grep for 'pkg', for example? In my default syslogd setup, (un)install events are logged there. 16:08:58 I think 'pkg info ' will at least show you the install date of the current version. 16:09:14 psychonate: oh, didn't check there, was specting something like /var/log/pkg.log for whatever reason 16:10:05 If those events are getting to your syslog daemon, I imagine you could check your syslog daemon's config to write those events into a different log file if you want. 16:10:20 s/check/update/ 16:10:45 psychonate: /var/log/messages has the date when the package version changed. It is what I'm looking for, thanks ! 17:56:09 Is 15 release released once builds begin or after the announcement? 18:03:46 zfs(8): OpenZFS has been updated to zfs-2.2-release(2.2.7)(2ec8b6948070). 18:03:58 I thought it was updated to 2.4.x 18:04:23 https://www.freebsd.org/releases/15.0R/relnotes/ 20:17:53 what i do wrong? pkg install firstboot-freebsd-update, add firstboot_freebsd_update_enable="YES" to /etc/rc.conf, finish install and first boot... nothing happens 20:20:45 kerneldove_: firstboot means firstboot ever 20:21:00 ya that's what it was 20:21:10 there's a sentinel involved that, iirc, the rc framework wipes after it executes anything marked for firstboot 20:21:22 it was the first boot 20:21:30 (so if you `pkg install` this on the running system and reboot, it's by definition not the first boot) 20:21:48 it's not on a running system it's during the manual steps part of a new install 20:22:00 installer-installed things also don't go through a firstboot 20:22:06 generally VM or embedded images 20:22:10 huh 20:36:58 Is there an official freebsd.org guide on how to setup Wireguard (with examples) for FreeBSD 14.2? I understand that 14 has it in base, no ports needed. However I don't see anything in the handbook. 20:50:29 tuaris: it's all the same as other platforms 20:50:39 but perhaps wg-quick is the package that may help you 22:41:38 anyone else seeing crashes on freebsd 14.3p>3 ? 22:44:56 back when I was running it, no 22:45:52 kerneldove_ how? 22:46:17 im getting regular OS crashes on 14.3. fatal error mutex xxx own xxx is on list xxx xxx at line 151 in file freebsd-src/lib/libthr/thraed/thr_mutex.c errno 35 22:46:26 it's p5. haven't seen the problem on p3 or earlier 14.3 versions 22:46:44 trying to search bugzilla for any other reports but its' hard to use 22:47:10 what platform are you running on? im guessing its some kind of multithreading issue 22:47:34 ryzen 5700 22:47:59 ryzen 7 5700G specifically 22:48:16 and ya prolly multithreading related 22:52:04 thats definitely weird, Im gonna go on a limb and say it could be worth booting into a different OS and updating your microcode, but I dont know enough about how freebsd's kernel works :( 22:53:42 i wonder if it's related to https://lists.freebsd.org/pipermail/freebsd-current/2016-March/060264.html 22:53:49 that's old but similar part of the code 22:54:52 shrug 22:55:19 is this just freebsd without any extras installed? 22:55:33 or are you attempting to run specific software 22:55:54 freebsd + a rust server app i made 22:56:12 running on a bunch of boxes with basically identical versions and configs, no others having prob 22:56:29 exact same setup huh. weird 22:56:51 bios + microcode update would be a good start, should be able to use the cpu-microcode-amd to test new microcode without having to flash the CPU from another OS? 22:56:56 are they also running your app? 22:56:57 ya i use scripted bsdinstall so i can say it's identical 22:56:59 hm 22:57:01 ya 22:57:05 cpu-microcode-amd package* 22:57:20 will that tell me if an update is needed? 22:57:27 i would boot into a diff OS personally, if its gonna be unstable 22:58:08 I beleive it just loads the microcode into the CPU on each boot? 23:05:06 I dunno, I just wouldnt trust it :D 23:05:14 ok if it happens again i'll try updating the bios/bmc then try again 23:05:27 sucks because it was working reliably until i changed from p3 to p5 23:05:42 any way to see if there were changes to that file post p3? 23:05:53 freebsd-src/lib/libthr/thraed/thr_mutex.c 23:06:57 https://github.com/freebsd/freebsd-src/blob/master/lib/libthr/thread/thr_mutex.c looks like 5 years ago so can't be that 23:06:59 hmm 23:08:53 difference between -pX and -pY should be very minimal, literally only he source files mentioned in the errata notice 23:09:19 maybe SO_REUSEPORT_LB breaks connect(2) for UDP sockets. [SA-25:09.netinet]? my server app does lots of udp 23:19:56 im very curious about this, I hope you sort it :( 23:24:15 ty me too hehe 23:27:12 cpu-microcode-* are necessary evil imo, not all hardware (motherboard) vendors provide BIOS updates for long so the microcode updates cannot be loaded from an updated BIOS on boot, the OS must take over that duty 23:39:57 is it recommended to run cpu-microcode-amd for any server using amd procs? 23:47:34 the cpu vendors recommend it 23:48:08 ok i'll set all of my boxes up to use it ty 23:49:18 hm just got the crash again! 23:49:59 this time it was rust tokio libp2p error "expected some established connection to peer before closing" think https://github.com/freebsd/freebsd-src/commit/058bcb57cd4b7e855cd596316541aff0adc5ddcf looks related? 23:54:21 i rebooted after setting up cpu-microcode-amd in /boot/loader.conf.d/. any way i can check and see if it was applied? 23:54:42 dmesg | grep micro 23:54:49 i put its config in /boot/loader.conf.d/cpu_microcode_amd.conf 23:55:12 nothing 23:55:37 service microcode_update start 23:55:56 pkg install cpu-microcode 23:56:00 first 23:56:16 i already ran pkg install cpu-microcode-amd, is that not enough? 23:56:50 i get this on my intel systems (with an up-to-date bios!) 23:56:51 dmesg | grep micro 23:56:51 CPU microcode: updated from 0xf0 to 0xfa 23:57:27 you either use /boot/loaders.conf* OR rc.conf, the first being preferred as its loaded before the kernel 23:57:41 ya that's what i did 23:57:43 the first method 23:58:40 i installed cpu-microcode-amd, then to /boot/loader.conf.d/cpu_microcode_amd.conf i added cpu_microcode_load="YES" \n cpu_microcode_name="/boot/firmware/amd-ucode.bin" 23:58:45 need i do more? 23:59:21 that looks correct to me 23:59:31 i wonder why not working then? 23:59:36 there is nothing you can do more