03:10:20 my pc sound is very small, the same soundbar on other OS , the sound is common, https://paste.centos.org/view/3cd207f9, my OS is freebsd 14.2 03:11:25 FreeBSD is becoming more appealing everyday I learn new stuff… pkg-status is awesome 03:41:15 I agree this FreeBSD stuff is a lot of fun 04:11:18 sent xxy a memo 04:12:00 oxbar, i don't see a pkg-status where i am; do you mean stats or something? 05:09:32 https://pkg-status.freebsd.org/ 05:28:23 aha 10:29:04 https://bsky.app/profile/theregister.com/post/3lmvcbjjusd2f 10:35:39 also https://virginiabusiness.com/nova-govcon-firm-mitre-to-lay-off-442-employees-after-doge-cuts-contracts/ and https://www.thecvefoundation.org/ 10:51:05 hm, my feed reader says the atom feed of the ports repo is broken 12:08:33 Hi all, my machine rebooted at 3:11am this morning. /var/log/messages snippet: https://x0.at/WH-5.txt . Thoughts, directions to debug that?.. 12:10:18 exhausted due to intense IO operations run by standard cron jobs, check hardware 12:16:28 mzar: failing hardware? such as bad drives or bad memory? 12:16:52 because while I can understand jobs crashing, I can't really understand the OS giving up and rebooting 12:29:20 the only job vaguely running at 3:11am would be a daily nextcloud routine (www) CMD (cd /usr/local/www/nextcloud && /usr/bin/nice -n 19 /usr/local/bin/php console.php preview:pre-generate) -- which I just tried and that didn't crash 12:33:14 periodic runs scripts at that time 12:56:00 f451 Agent Orange is following Vlad's orders 13:10:08 xxy: the mixer levels can be changed. try mixer vol=1 pcm=1 speaker=1 line=1 ... until you find the option needed to increase the sound output. 13:25:19 jpb, they're not here. 13:27:25 MelMalik: yeah, but they might be back with an irc client that grabs previous convos 13:29:17 uh? 13:29:24 i don't think libera can send those. 14:04:40 jbp, that's not how irc protocol works 15:05:13 so I had audio working on my previous freebsd install, but I can't quite figure out why i do not now 15:06:46 pulseaudio is installed, I can start it with --start but beep(1) still does nothing 15:07:13 the correct sound device is selected, and it is unmuted, pavucontrol can connect to the pulseaudio daemon 15:07:31 do you need pulse? 15:10:21 * polarian shrugs 15:11:10 haven't messed with audio for AGES... used to use pipewire on Linux, but as pulse has the best support on freebsd I assumed it would just be the easiest solution for now 15:11:34 it used to work on my previous install... I just never setup audio after reinstalling freebsd on my laptop, and now I cant remember what I did to get it to work :P 15:14:41 sorry i cant help. But if you can get it to work without pulse audio, ive noticed most programs now can change their volume without changing system volume 15:16:54 you can test if freebsds native audio support works by doing cat /dev/random >/dev/dsp which sends random noise to your default audio device 15:17:46 Speaking of audio, which driver do I want for this?: https://termbin.com/k3qt 15:19:30 That just hda(4)? 15:22:18 it looks like HDMI audio CrtxReavr, is it ? 15:29:00 Shouldn't be. 15:33:14 OK, but it should show up in /dev/sndstat, I have '8 Series/C220 Series Chipset High Definition Audio Controller' as hdac1 and it works 15:38:46 nimaje: nothing 15:52:33 is it true 4chan has been hacked through vulnerabilities in freebsd? 15:52:56 i've heard no evidence to support that theory 16:04:34 dkjds: what were the vulnerabilities ? 16:07:51 pdf thumbnailer vulnerability 16:08:13 thet word on the street was they were running 10.1 (and 10.1-era software), and a ghostscript exploit was used to get shell access 16:08:15 pdf thumbnailer is not part of FreeBSD 16:09:36 dkjds: it was an exploit in a 10+ year old ghostscript release 16:10:10 but fun to know that freebsd has been the os serving 4chan all this time 16:10:33 interesting, they probably avoided maintenance downtimes till now 16:11:15 mzar: like a downtime savings account, you put all your downtime aside and get to take it all at once 16:12:35 a collateralized technical debt obligation 16:12:56 nice writeup about this hack (in Polish, but you can traslate) https://sekurak.pl/4chan-z-problemami-czyli-o-ataku-na-popularny-imageboard/ 16:14:16 polarian: i just went through setting up audio on my system. you can dm if you want. 16:16:02 freebsd 10.1 is from 2019, it is just 5 years 16:17:59 it looks like they were running custom kernel 16:18:00 no it's not 16:18:07 10.1 is like 11 years old 16:18:50 then probably sysadmin retired or left, but moderators wanted to keep it running 16:19:15 the kernel build date is september 2019 16:19:37 you can build a kernel when ever you want 16:19:42 10.1 went EOL end 2016 16:21:55 https://www.freebsd.org/security/unsupported/ is reference 16:22:08 anybody here familiar with resolvconf ? 16:22:14 FreeBSD 10.1-RELEASE will be supported until January 1, 2017. - from 10.1 RELNOTES 16:22:17 anyway, someone rebuit custom kernel in 2019 - perhaps they have own, not upstreamed patches in the source 16:22:36 apparently not enough ;-) 16:22:54 anyway I have a dhcp laptop, and I want to use the same dns server every single time 16:23:34 I have tried `resolvconf_enable=NO` and `resolv_enable=NO` but I still get ISP supplied garbage DNS here 16:23:53 if necessary I will force it via dhclient.conf instead but this feels wrong 16:24:24 dch: i am not familiar with resolvconf, but generally i would prefer to fix this in dhclient.conf using the supersede option 16:24:36 yeah exactly 16:24:43 only because it seems better to fix the problem at the source 16:25:05 (well, not quite at the source, unless perhaps your ISP's DHCP server runs FreeBSD 10.1 and you can break into it and change the DNS servers it gives you) 16:25:09 resolv_enable="NO" works for me, but i guess dhclient would then be responsible for updating it 16:26:01 so i'd be inclined to agre about supercede 16:28:44 we're all out here regularly updating our stuff like dummies while 4chan's rocking a 13yr old garbage stack and it still took them this long to see consequences. 16:29:15 you can add resolv_conf="/dev/null" to /etc/resolvconf.conf 16:29:17 so dhclient-script has `resolvconf_enable` check 16:29:32 but supersede and messing with dhclient-scripts resolv conf functions are also options 16:30:09 the resolvconf.conf edit is what local-unbound does, though. so that's prolly the best option 16:32:40 I'm going with resolconf.conf then thanks zi 16:37:06 np 16:47:52 would it be correct to say freebsd has quarterly security updates, i.e. every 3 months? 16:48:18 isley: yes i feel quite stupid as well 16:48:50 that gave me a good laugh 16:49:08 johnjaye: a new ports tree is branched every quarter; however, security patches for the system are released in near real time and updates to the ports tree (on the non-quarterly branch) is also near real time 16:50:35 so if you install security updates as soon as they are available and you are using the main branch of the ports tree, you can easily bring security fixes in way faster than 'every 3 months' 16:51:18 security fixes are also sometimes backported to the ports quarterly branch, but not always 17:06:39 well, the should is that they are backported to quarterly, as about the only thing that should go into a quarterly branch, the is is something else 17:10:04 nimaje: it isnt always that easy. sometimes bringing in a security fix, involves pulling in other updates as a side effect 17:10:23 i wouldnt say it is super often that someone is hand-crafting a backport of a specific fix to merge into the quarterly branch, even when it happens 17:12:05 in theory upstream should be providing a patch for whatever version is in quarterly (it shouldn't be that old) but yes, the is is something else 17:12:19 pfft, who would want to sign up for that? 17:12:29 "we released a new versin with the patch to address the issue. update." 17:12:33 s/versin/version/ 17:13:08 i think this is a bit harder for debian or rhel as they release so frequently that half their software isn't supported upstream anymore :-) 17:13:23 so *infrequently* 17:13:32 that's also by design/choice though 17:13:47 they intentionally stick os release foo to apache 2.4.11 (or whatever) 17:15:54 they look at final solution of the problem and backport it, picking each commit one by one 17:16:44 on sponsor some open source project asking for longer support 17:18:34 CentOS was nightmare, CentOS users: "-Pleae don't use this option in program XY since we are running CentOS 4.x and our version of program XY is (very low number here)" 17:19:57 i think that's almost all flavors of linux, no? 17:21:24 I don't know, luckily CentoOS is no problem anymore 17:21:42 as an example: ubuntu 18.x is locked to apache 2.4.29 17:22:10 ubuntu 22.x is stuck with 2.4.52 17:22:38 FreeBSD admin had to respond to CentOS lobby this way: "-We are running the most recent version of XY, and disputed opion increases security" 17:23:18 zi: AFAIR Debian/Ubuntu have "bacports" repositories, and you can upgrade using them 17:23:31 CentOS didn't have it 17:23:31 i do not miss administering centos, for sure 17:24:07 i haven't used debian for a while, but i thought backports was more for "this version is so old it no longer works at all", whereas Ubuntu PPAs are more for just getting a newer version of something 17:24:53 zi: pretty much, except for certain exceptions with backports as mentioned. but in general any distro you'd wanna run on a server will have this issue. rolling release distros like arch not so much 17:25:22 but I would never put arch on a server, and I'm saying that as someone who ran it on desktop for close to a decade 17:25:36 there is such a thing as too up to date 17:31:10 arch will give you every new security patch pretty damn quickly. but it will do the same for every new bug too. and they'll happily push updates that break stuff, and just make an announcement of it on their site with a tip on how to fix it