00:01:40 <dkeav> i used to a good while ago
00:01:41 <dkeav> had an atheros based card for hostap
00:02:21 <rwp> ketas, Things are improving in that area: https://freebsdfoundation.org/blog/how-to-unlock-high-speed-wi-fi-on-freebsd-14/
00:03:11 <rwp> That's all about improving kernel driver performance and not user interface.  But kernel wifi driver performance has been really very slow so that's not a bad place to improve things.
00:07:07 <ketas> yes it is
00:07:30 <ketas> anyone using that wants to use current
00:09:21 <rwp> For the kernel driver wifi performance improvements listed there the changes in CURRENT has been merged into 14.3-RELEASE.
00:10:03 <ketas> it somewhat improves laptop sta
00:10:17 <ketas> but it's still being worked on
00:10:30 <ketas> and nevermind exotic setups
00:11:11 <ketas> to be honest, there's not much hw one could use to create ap's too
00:11:33 <ketas> there'a good support with pcie
00:11:51 <ketas> but there's no hw to stick pcie card into
00:12:16 <ketas> there's ton of hw where you can stick usb into but that's massive shitshow
00:12:29 <ketas> it does work almost
00:13:57 <ketas> usb does add latency and has no dma but that's only part of issue
00:20:33 <ketas> only benefit is that doorstop hw is available at doorstop price
00:24:21 <ketas> there's also invisible stuff going on but public reports involve someone's intel wifi card in laptop is having trouble having 5ghz connection to already overheating comcast router
00:24:27 <ketas> also important but
00:41:25 <futune> after upgrading from 14.2 to 14.3, and also pkg, the fish shell has stopped working for me
00:41:58 <futune> it dumps core, with "Bad system call (core dumped)"
00:42:47 <futune> immediately on trying to start
00:42:58 <futune> does anyone know what is going on with it?
00:43:02 <kevans> the question is, which system call?
00:43:35 <kevans> running it under `truss` may be enlightening
00:46:03 <futune> that is a very good idea but the output is long and I don't know what it means
00:46:22 <futune> This looks suspicious: compat11.kevent(0,0x0,0,0x0,0,0x0)		 ERR#78 'Function not implemented'
00:47:44 <futune> could it be related to freebsd 11 binary compatibillity? That's what compat11 makes me think of
00:47:48 <kevans> yeah
00:48:00 <kevans> iirc we smack ENOSYS with a SIGSYS by default
00:48:38 <kevans> but we do build COMPAT_FREEBSD11 (and pretty much every other compat option) into GENERIC; are you just running stock packages/configs, or custom stuff?
00:48:59 <futune> I see. Does GENERIC have compat11? I've been compiling my own kernel for years, and fish has been running fine until this update
00:49:05 <futune> ah, sorry, I was too slow
00:49:12 <futune> yes, it's my own kernel config
00:49:42 <kevans> yeah, it has all of the compat options
00:49:47 <futune> I find it strange that it would start needing compat11 now, since that's several years out of date
00:50:02 <kevans> yeah, that's quite odd
00:50:13 <kevans> ohhh
00:50:28 <kevans> > The biggest change is that the entire shell has been rewritten in Rust.
00:50:32 <kevans> there's your answer
00:50:40 <futune> flipping fantastic ...
00:50:53 <futune> thanks for the help
00:51:08 <kevans> yep, sorry to be the bearer of bad news
00:52:51 <futune> at least I gained some knowledge :)
00:55:22 <ketas> why is iron oxide so popular anyway
02:59:00 <wavefunction> Why is rust leveraging compat11? That's gotta be a mistake somewher
03:00:41 <wavefunction> Just installed fish shell via pkg -- works great.
03:01:23 <wavefunction> rust is popular because it generally makes doing the dumb things harder than doing the right thing.
03:14:45 <kevans> wavefunction: not a mistake, hysterical raisins
03:15:03 <kevans> trying to get them to move on is a whole thing
03:15:30 <kevans> https://github.com/rust-lang/rust/issues/89058
03:15:40 <kevans> I believe this is the one
03:16:16 <kevans> you know it's a good one because it's been ongoing from 2021
06:23:33 <polarian> ivy: I thought it was generally agreed upon that gnu coreutils are shit :)
13:54:29 <remiliascarlet> polarian: Rather, most non-Linux Unix-like OS users agree that GNU coreutils are shit, as well as GNU in general.
13:56:27 <remiliascarlet> But at least they're not the ones sabotaging Linux from the inside, that's IBM and all the products they own (Red Hat, Fedora, Gnome, Wayland, SystemD, DBUS, Avahi, and more).
13:57:06 <remiliascarlet> Microsoft sabotages Linux too, but at least they also add some kind of value back in return.
13:57:43 <remiliascarlet> So they at least kill Linux with respect.
14:12:40 <antranigv> anyone here runs Forgejo on FreeBSD? I'm getting some weird issues about "Command error: stat /usr/local/sbin/custom/conf/app.ini: no such file or directory"
14:16:00 <rtprio> antranigv: hah, the gitea package had that problem too
14:17:22 <rtprio> but i don't remember what fixed it
14:21:05 <kevans> antranigv: sounds like FORGEJO_CUSTOM is broken
14:21:21 <kevans> it should be set in the forgejo rc sript to /usr/local/etc/${name}
14:21:44 <antranigv> rtprio I remember that too. I'll check an older machine archive now.
14:21:51 <antranigv> kevans indeed. and it is set btw
14:22:10 <kevans> odd
14:22:28 <kevans> well that's the extent of my knowledge :-D
14:22:44 <rtprio> i do remember the port overwrote my custom decorations, but i never bothered to set up a pr for it
14:26:54 <antranigv> kevans good enough!
14:27:05 <antranigv> it helped! ok I think I know what the issue is
14:37:53 <kevans> oh?
14:55:38 <wavefunction> kevans: "hysterical raisins" - I'm keeping that in my witticism booklet.
15:04:52 <rtprio> ugh, might be time to protect my gitea
15:11:28 <wavefunction> rtprio: I had to starting a couple weeks ago. And that was just for cgit. https://www.gluecode.net/blog/posts/2025/anubis-installed.html
15:14:00 <wavefunction> Looking at that linked rust issue, it really seems like a lot of developers *lately* don't actually care about finishing discussions/documentation/updates.
15:14:24 <wavefunction> I will always appreciate the BSDs for having at least some intention of polishing a release.
15:35:38 <rtprio> yeah, i was eyeing anubis. but i could move it behind wireguard / lan only and no one else would care
15:47:02 <rwp> If it is for your own personal use only you can always put it behind http basic auth too which is even simpler.
15:56:58 <rtprio> that would break all my shit
15:57:04 <rtprio> but yes, it would be simpler
16:00:17 <wavefunction> But... but... catgirls
18:23:42 <CrtxReavr> Is seemingly excessive inode usage a symptom of ZFS usage?
18:24:26 <rtprio> not that i've observed
18:24:48 <ivy> where are you seeing "excessive inode usage"?
18:25:32 <CrtxReavr> I'm not. . . trying to help someone on EFnet.
18:26:29 <rwp> Start with each file consuming at least one inode.  An excessive number of inodes used would mean an excessive number of files.  Lots of small files?
18:29:03 <CrtxReavr> That doesnt' seem to be the case.
18:29:27 <rtprio> i didn't know people still hung out on efnet
18:29:38 <CrtxReavr> I'm wondering if inodes are not being released when files are deleted.
18:30:40 <ivy> CrtxReavr: well, can you ask the person you're helping where they're seeing excessive inodes (and what that means)?
18:31:15 <CrtxReavr> df -i
18:31:34 <CrtxReavr> The chief complaint is disappearing space.
18:31:51 <rtprio> do they have a ton of snapshots and then deleted files?
18:31:59 <rtprio> they would also take up space
18:32:08 <rtprio> depending on what happened since
18:33:49 <CrtxReavr> https://bpa.st/TFQA
18:34:26 <rtprio> so he's out of space, inodes are a symptom, not the problem
18:36:21 <CrtxReavr> Well, a file shouldn't use more than one inode.
18:36:49 <rtprio> what about a file in a snapshot
18:37:47 <CrtxReavr> Where I've traditionally seen inode problems is when people ran out and bought multi-TB drive, made it one volume, newfs'd it, but then the default inode density was too low, so little files would eat up all the inodes.
18:38:04 <rtprio> yeah, for ufs maybe
18:38:23 <rtprio> i haven't seen or heard of an out of inode situation in like, more than a decade
18:39:57 <rtprio> zfs list -o space   how much does he have in snapshots
18:49:29 <rtprio> ?
18:51:59 <rwp> I thought that inodes were dynamically allocated on zfs.  Pretty sure.
19:04:49 <rwp> Yes.  Since our cgit server is suffering network abuse stress: https://bpa.st/6EEQ
19:05:49 <rwp> Our poor https://cgit.freebsd.org/src/ is giving me sporadic success with mostly 503 failures.  As are most source servers on the Internet.  Due to AI Scraper Crawlers endlessly hammering on them.
19:08:52 <rtprio> so it ... makes it up for df -i ?
19:08:55 <rtprio> more or less?
19:18:27 <rwp> This would be something good to have an interpretation from someone who would know but...  It appears to me that it reports based upon the currently dynamically allocated values.  Which means as values change you can get wild fluctuations in results for percentages and such.
19:19:08 <rwp> Note that I am far from knowledgeable about this code base.  But I think it is dynamic and so the mapping to df values is not going to be like it is on UFS.
19:19:15 * rwp must run afk...
19:26:26 <rtprio> CrtxReavr: so ... an update?
23:47:07 <joako_> It is no longer possible to update iocage jail if the release is no longer in the updates server?