07:15:44 <vkarlsen> anth: Happy to help
16:30:33 <polarian> I wonder if I should take the serial thing to the ML
19:45:37 <vkarlsen> polarian: I don't know if this will help your exact issue, but some EFI serial problems can be solved by setting hint.uart.X.at="isa" in loader.conf (where X is the number of your serial port)
23:16:37 <mjp> the CVEs start coming and they don't stop coming
23:17:13 <mason> Hm. I wonder if I've opened a bug about this before. FreeBSD 15, I edit .shrc to say .... I did open a bug. Or at least I mentioned it in here. And it was even debugged. I'm surprised it wasn't fixed in FreeBSD 15.
23:17:55 <mason> Yeah, in the stock .shrc, if you turn on "set -o vi" by uncommenting, it doesn't actually work until you set -o, unless you remove the binds.
23:18:10 <mason> Now to see if I actually opened a bug.
23:19:45 <mason> Hey, look at that! Year-ago me reported it against FreeBSD 14.2
23:19:47 <mason> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286429
23:27:34 <spork_css> any idea why ansible's "ansible.builtin.service" works to reload many services, but not pf?
23:27:57 <spork_css> the "restart" state works, but that also nukes all existing states, which is not good.
23:29:04 <spork_css> I see others tend to just set a handler and have it use "ansible.builtin.command" to run "pfctl -f /etc/pf.conf", which is fine, but I'm curious why the "reload" action seems to get lost in translation in that ansible service module.
23:51:48 <mason> spork_css: It might be worth an upstream patch to address the behaviour with Ansible. It's also worth understanding if it tries and fails for some reason, and what exactly it's trying to do. I imagine there's a bunch of special-casing for these things.