01:24:03 V_PauAmma_V: if I try to pass ipv6_static_routes I get the following: 01:24:05 ifconfig: ipv6_static_routes: bad value 01:24:59 currently following one of the solutions earlier, I have the following: 01:25:01 ifconfig_wlan0="WPA DHCP inet6 2001:8b0:57a:2385::b prefixlen 64" 01:25:12 ah shite I probably should have filtered the IPv6 address but meh 01:25:34 I am starting to think the other solution was a better one 01:25:38 oh I forgot to add the ssid 01:26:40 oh wait ipv6_static_routes would be well static... and therefore break when moving network... 01:28:30 I will try the DHCLIENT-SCRIPT(8) method which was recommended, this seems simpler than messing with rc.conf 01:29:37 You don't pass it to ifconfig. You define it in rc.conf and let rc parse it and deal with components accordingly. 01:30:02 I realised that, but the issue is that would not be per ssid 01:30:06 it would be global 01:30:12 which isn't what I wanted 01:30:15 Fair enough. 01:30:35 so yeah dhclient-script(8) seems like the best bet 01:31:25 unless someone else has any ideas? 01:34:15 polarian: have you tried doing dd tasks with pv instead? I believe it will often be a dropin with better defaults 01:35:39 scoobybejesus: no... but after reading the linked docs, just specifying 1M block sizes and setting the conv=sync flag seems to give the expected performance... 01:36:35 pv will throw in the progress bar capability as well, but true true 01:49:42 scoobybejesus: status=progress gives enough information for me :) 01:49:50 sometimes more is less :P 01:49:57 sorry... less is more... geez 01:55:04 are you really running dd often enough to be made aware of the status? 08:11:02 SIGINFO is nice, because it works in a lot more utilities than dd. 08:47:24 <|cos|> tsoome: do you have suspend-resume working with freebsd on a macbook? arm or intel? 09:04:27 debdrup: yes, i lament that ^T doesn't work everywhere 09:28:36 On the BSDs, it'll at least print what the kernel thinks is going on. 16:20:51 |cos| sorry, I do not have fbsd installed directly on hardware 17:15:51 Good afternoon all. A quick preface, I'm pretty new to BSD as a daily driver and though I'd pick up a distro to save myself a little bit of sanity. So, I'm running on NomadBSD which is based on FreeBSD 14 p4. I'm here today to ask about setting up Bluetooth audio, as I've just been going in circles over the last day or two trying to get it to work. So far I've followed along with a method I've seen a few times, 17:15:51 so I'm just going to link the one post that I've actually been using following this. The part I'm getting stuck at is the actual point where I set up audio. I can't seem to connect to the DSP device properly? I think? I'll grab the error in a second, will follow with the link 17:16:07 This is what I'm following along with: https://forums.freebsd.org/threads/bluetooth-audio-how-to-connect-and-use-bluetooth-headphones-on-freebsd.82671/ 17:16:08 Title: [Bluetooth-audio] How to connect and use Bluetooth headphones on FreeBSD | The FreeBSD Forums 17:16:20 This is where I'm getting stuck virtual_oss -T /dev/sndstat -S -a o,-4 -C 2 -c 2 -r 44100 -b 16 -s 1024 -R /dev/dsp0 -P /dev/bluetooth/headphones -d dsp -t vdsp.ctl 17:16:27 And this is the error: virtual_oss: Could not open DSP device '/dev/dsp0': Operation not supported 17:16:35 I'm guessing that /dev/dspX are audio devices, however I'm not sure what is what, and I can't seem to figure out how to figure that out 17:32:01 <|cos|> tsoome: ok. i can kinda see why, after myself attempting running it on a macbook... thanks for answering! 19:09:04 ls 19:09:07 ... 19:09:17 alright, I've just tried to upgrade to 14.0 and encountered a problem 19:10:39 libcrypto and libssl need to rebuilt, seemingly. I was not aware this had to be done, and probably did it wrong. Now I'm in a situation where I cannot run "make install clean" in /usr/ports/ports-mgmt/pkg. It fails with ld_error:duplicate symbol: nbactions and many more similar errors on attempt to build pkg 19:10:54 I cannot upgrade pkg because of the crypto and ssl library issues here 19:11:43 how can I proceed? 19:19:23 https://forums.freebsd.org/threads/pkg-not-working-ld-elf-so-1-shared-object-libssl-so-111-not-found-required-by-pkg.68078/ starting from this 19:19:24 Title: Solved - pkg not working - ld-elf.so.1: Shared object "libssl.so.111" not found, required by "pkg" | The FreeBSD Forums 19:25:07 the problem is that random packages still seem to want openssl111 19:25:14 and yet I've upgraded everything 19:28:42 ldd does not show this version if I run it on /usr/sbin/pkg 19:34:32 /usr/sbin/pkg is just a small wrapper to install and call the real pkg /usr/local/sbin/pkg 19:35:29 so why does it look for libssl.so.111 19:35:37 that shouldn't be part of this release 19:36:56 you upgraded via freebsd-update ? and try to rebuild your ports after the first restart as it should have told you 19:37:02 ? 19:37:24 I tried to upgrade ports one step too late I believe 19:37:54 pkg-static shows pkg's version as 1.21.3 if I check it 19:39:32 /usr/local/sbin/pkg shows a dependency on .111 even after upgrading pkg via pkg-static 19:39:54 I think pkg-static install -f pkg should work 19:39:58 it did not 19:40:04 this is the result *after doing this* 19:40:22 "FreeBSD_version: 1302001 " shows as in the info for pkg, which doesn't make sense to me 19:40:25 could this be relevant? 19:41:04 freebsd-version yields 14.0-RELEASE-p6 19:41:24 ah, pkg-static is detecting ABI wrong, because of that mishap 19:41:36 right that is what that sounded like 19:41:53 is there a way to force it to use correct ABI and re-upgrade everything? 19:45:46 everything in freebsd-version -kru shows 14.0 19:46:29 aha 19:46:47 now I've got the ABI change made, let's see if things will fix 19:48:27 pkg seems to have shaken off its ailment now, so that's promising... 19:56:46 Yep ok, I just set the correct ABI in pkg.conf manually and it appears it's happy now. lmk if that's a bad idea or incomplete I guess 20:27:06 now that it is fixed pkg should detect ABI corrctly again, so you should change it back to the variable and when upgrade to 15.0 remember to update your packages before the last freebsd-update call removes the old libs and in case it you have that problem again, I think you can set ABI via the environment