02:24:56 <PaddyMac> Has Steam been tested with FreeBSD 14-current? I'm having errors preventing it from running, and I'm wondering if there is a problem with my configuration or it's just incompatible with 14.
02:26:10 <PaddyMac> These are my errors: https://pastebin.com/yjh49Lnd
02:26:12 <VimDiesel> Title: $ steam-installDownloading Steam...fetch: http://repo.steampowered.com/steam - Pastebin.com
04:47:04 <rtprio> PaddyMac: have you checked out games/linux-steam-utils ?
05:21:32 <grahamperrin> Where is the charter for the freebsd-doc mailing list?
06:19:15 <jonusenet> where can i talk about freebsd dev talk? including kernel and userland apps
06:19:48 <RhodiumToad> here or in #freebsd-dev
06:19:54 <jonusenet> ty
06:32:01 <grahamperrin> jonusenet: also <https://discord.com/channels/727023752348434432/783418678279929896>
06:32:02 <VimDiesel> Title: Discord
06:33:07 <grahamperrin> – that is, #devguide, with #kernel nearby.
06:35:11 <RhodiumToad> any autofs users around?
06:37:39 <rtprio> i got it working not too long ago
06:38:41 <RhodiumToad> which features are you using?
06:41:25 <rtprio> let me boot that up and see
06:42:37 <rtprio> not much, apparently: "/home   auto_home       -nobrowse"
06:45:57 <RhodiumToad> I found a fairly nasty bug that happens most obviously if you try and use both -media and -noauto maps
06:50:24 <RhodiumToad> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272446
06:50:27 <VimDiesel> Title: 272446 – automount -c clobbers flags of mounted direct map entries
07:53:42 <debdrup> Speaking of autofs, https://www.freshports.org/sysutils/devd-mount/ landed not too long ago.
07:53:43 <VimDiesel> Title: FreshPorts -- sysutils/devd-mount: Automount tool utilizing devd notifications
07:54:15 <debdrup> I'm only using autofs for /net so I don't suspect I can be a lot of help.
11:30:19 <mikoto-chan> where is libclang.so on freeBSD?
11:30:48 <parv> Somewhere in /usr/lib*?
11:31:23 <RhodiumToad> for the base system? I don't think there is one
11:31:43 <RhodiumToad> applications that use libclang need to use one of the llvm ports
11:33:08 <parv> Sorry. As RhodiumToad mentioned, for llvm15 found in /usr/local/llvm15/lib
11:34:46 <RhodiumToad> (applications have to link to a specific llvm version because they're not generally compatible)
11:39:52 <mikoto-chan> RhodiumToad: so I _need_ to get libclang from ports?
11:40:23 <RhodiumToad> if you're building an application that needs libclang, then yes, you need to install one of the devel/llvm* ports
11:41:13 <debdrup> llvm in the base system isn't the complete llvm collection, it's basically just enough for the base system
11:41:36 <debdrup> there are good reasons for this (though right now they escape me)
11:42:01 <parv> Is it not possible to build whole & everything llvm+clang by twiddling some knobs?
11:42:05 <RhodiumToad> the main reason is to not make the llvm ABI part of the base system ABI
11:42:27 <RhodiumToad> parv: that's what the ports are for
11:42:27 <meena> base clang/llvm is stripped of everything non essential for a compiler, because if it wasn't, we'd have to think about ABI compatibility
11:42:45 * debdrup nods at RhodiumToad and meena
11:43:19 <debdrup> i seem to recall a few other reasons, but they're "minor" reasons compared to that major one
11:53:07 <PaddyMac> rtprio Yes. That is what's failing to start. As t turns out, I emailed the maintainer last night. I had a reply this morning saying that a fix is in the repo and should y in ports in a couple of weeks. So it's a known issue.
13:32:28 <yuripv> AllanJude: hi, do you know if user vdev properties on FreeBSD are not settable (returning EROFS) by choice, or is it a bug?
14:00:53 <CmdLnKid> yuripv, how are you trying to set these ?
14:01:46 <CmdLnKid> assuming via zfs set ...
14:02:08 <yuripv> no, using zpool set, of course
14:02:25 <CmdLnKid> one of the two ;-)
14:02:51 <yuripv> e.g. zpool set com.example:spare=foo data nda1p1
14:03:01 <CmdLnKid> k
14:03:09 <yuripv> ioctl(4,0xc0185a56 { IORW 0x5a('Z'), 86, 24 },0xeef7c98f928) ERR#30 'Read-only file system'
14:03:15 <yuripv> it shouldn't be :)
14:03:24 <CmdLnKid> interesting
14:04:37 <CmdLnKid> have you also tried setting debugflags=16 "allow shooting yourself in the foot mode", have plenty of backups just in case
14:04:42 <yuripv> pre-defined properties (e.g. zpool set comment=foo pool vdev) are ok, it's only the problem with user properties
14:05:20 <yuripv> that sysctl is completely unrelated, this is zfs thing and properties are stored in per-vdev zaps
14:05:54 <yuripv> i was just too lazy to look in the code and thought a quick answer would do :D
14:05:54 <CmdLnKid> yeah was thinking maybe it had something to do with it being a raw vdev
14:06:32 <CmdLnKid> maybe detach the vdev first ? then set ?
14:06:45 <yuripv> it's not how it works...
14:06:52 <CmdLnKid> i know i know shouldn't be that way
14:07:20 <CmdLnKid> just making a few initial guesess
14:07:23 <yuripv> you can't set properties on something that does not exist :)
14:08:09 <yuripv> as i said, predefined properties are ok, the problem is only with user-defined properties, so anything outside of this scope is unrelated
14:08:23 <CmdLnKid> k