03:36:08 <ExclamationPoint> RhodiumToad, someone said you might know about FreeBSD and slow SD write speeds.
03:36:40 <ExclamationPoint> I got a 512GB SDXC that's writing <1MBps right now. Tried two different readers, two different adapters, and no adapter
04:01:54 <TommyC> ExclamationPoint: It's only on FBSD that it's that slow?
06:49:41 <RhodiumToad> SDXC on a usb-attached reader?
06:50:18 <RhodiumToad> is it a new card or an old one?
08:17:16 <myappie> hi! im an architect currently working on a proposal for a future freebsd headquarters
08:17:26 <myappie> any suggestions to what the design concept should be?
08:18:50 <myappie> a building based on beastie would have too much of a religious connotation i'm afraid
08:40:08 <meena> I'm… so confused.
08:42:26 <TommyC> meena: he's building a building but doesn't want beastie on the front of it because it looks satanic
08:51:59 <myappie> TommyC: yep
09:00:11 <myappie> i could use beastie's three pronged spear
09:03:42 <parv> Church of Satanic Temple does have some problematic people associated; it does serves its purpose to challenge christian-religion propagandist US governments
09:04:23 <myappie> yep
09:04:40 <myappie> you know my godfather shared jailcell with the famous church burner
12:02:46 <debdrup> An opensource project probably isn't going to have a headquarter..
12:06:01 <la_mettrie> but maybe a bunker?
12:06:50 <debdrup> Woosh.
12:20:11 <pstef_> or foundation
14:43:35 <debdrup> I'm pretty sure the foundation has to have a registered address to exist, but it's a 501c3 so it's unlikely to be much more than an office and a mailbox.
19:13:22 <pkubaj> what is the status of ath10k / ath11k and ath12k?
19:13:59 <pkubaj> they seem to be in kernel sources but for some reason not connected to build system
19:51:26 <vxwarlock> which one is true > newfs_msdos -A -F 32 -b 4096 -L EFI /dev/gpt/efi or newfs_msdos -F 32 -c 1 /dev/ada0p1 | I have create one partition for efi [gpart add -a 4k -s 1G -t efi ada0
20:00:35 <rtprio> i thought the wiki had that
20:13:07 <vxwarlock> https://man.freebsd.org/cgi/man.cgi?query=loader.efi&apropos=0&sektion=0&manpath=FreeBSD+13.2-RELEASE+and+Ports&arch=default&format=html && https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot different way rtprio
20:13:09 <VimDiesel> Title: loader.efi
20:13:54 <signalblue> is there any way I can compute the hashes in the master.passwd file by hand?
20:14:40 <signalblue> I need to feed this file to dovecot as an authentication backend, and need the hashes but these accounts don't actually exist
20:16:21 <rtprio> signalblue:     In the master.passwd file, the password field is the encrypted form of
20:16:24 <rtprio>      the password, see crypt(3).
20:16:49 <signalblue> rtprio: I know that
20:17:13 <signalblue> I want to take a plain-text password and convert it to the encrypted form that is in that file
20:21:35 <rtprio> openssl passwd -salt blah -6
20:23:27 <signalblue> thanks
20:24:03 <signalblue> i've just resorted to creating a dummy account with the password, copying it to where I need I need it from the master.passwd file, and then deleting that account
20:37:29 <parv> I might have done both of those things- externally generate a hashed password; create an account to harvest the hashed password
20:38:35 <rtprio> it is just salted sha, you could do it by hand if you had the patience
20:38:51 <rtprio> or didnt know a few openssl verbs
20:58:04 <parv> How does "pkg" determines "__FreeBSD_verision" (short of running it & getting the message about mismatched versions)?
20:59:26 <parv> Is that recorded some where for the explicit purpose of getting the value after installing the world?
21:00:40 <parv> Alternatively, is there some knob that I could set to insert "__FreeBSD_version" in "uname" output?
21:11:31 <rtprio> i think it's uname -K
21:13:38 <Ronis_BR> Hi! I am trying to set a file sharing through a VPN. The host is FreeBSD. I setup NFS and SMB. It turns out that SMB is almost 50% faster than NFS. I am not using encryption for this test in neither case. Is it expected or am I doing something wrong? The biggest problem is that I can get 3 MB/s of transfer rate in SMB, whereas scp gives more than 10 MB/s.
21:13:55 <parv> rtprio, Nice! Thank you. The manual page does not make that clear enough. From "-K  Write the FreeBSD version of the kernel", I would have thought that be "13.2-RELEASE-p9" & such
21:14:18 <rtprio> i dont run release, whats yours say?
21:14:39 <parv> 1302506 (stable/13)
21:15:31 <parv> ... well outout is only the number; added "(stable/13)" to indicate the source
21:17:19 <rtprio> freebsd-version prints that, but it means something else
21:18:29 <parv> Right
21:28:03 <parv> From "freebsd-version(8)" manual page: -k  Print the version and patch level of the installed kernel ... -- fail to see anything between the options that would indicate differing values.
22:41:52 <rtprio> i don't understand how freebsd-version works tbh
22:43:22 <RhodiumToad> the manpage seems clear enough
22:44:17 <RhodiumToad> -k tries to find the default kernel path by parsing loader.conf, then finds the version number within that
22:51:48 <rtprio> when you only run current, it's always the same
22:57:23 <RhodiumToad> always the same as what?
22:58:06 <RhodiumToad> parv: pkg actually determines the __FreeBSD_version by reading it from the ELF headers of some binary
22:59:23 <RhodiumToad> and that binary is the first to be found of $ABI_FILE, /usr/bin/uname, or /bin/sh
23:00:48 <rtprio> it's always 14.0-CURRENT. never patch level. which makes sense, but also makes it not useful, unlike uname -K
23:00:54 <RhodiumToad> readelf -n /usr/bin/uname
23:01:50 <RhodiumToad> freebsd-version is returning the release name (like uname -r), not the __FreeBSD_version
23:02:20 <parv> RhodiumToad, Ah. I had tried earlier to search in "pkg" source for literal "__FreeBSD_version" string to find if that would mention some file but did not find that.
23:02:30 <parv> RhodiumToad, Thanks
23:06:49 <RhodiumToad> there's nothing really greppable in the pkg code that does that part
23:07:29 * RhodiumToad found it by looking for where FreeBSD_version was set in annotations, seeing that it came from ctx.osversion, and then searching for that
23:53:03 <_xor> Hmm, I don't know much about /dev/klog, but I do use syslog-ng. Trying to restart syslog-ng just now and it's giving me: "Error opening file for reading; filename='/dev/klog', error='Device busy (16)'"
23:53:25 <_xor> Tried running stat, fstat, fuser, & lsof on /dev/klog to see what might have that open...but to no avail.
23:55:22 <_xor> I know rebooting will probably fix it, but wondering why it would have trouble being able to open a read fd for that. I guess something grabbed it exclusively?
23:57:07 <_xor> Oooooh, wait a second. Could it be that syslog-ng is trying to gain exclusive access to it for itself (since it's a logging daemon and prefers full control?), but is failing because existing stuff is already reading from it and it's crying because it doesn't want to share the playground with the other kids?
23:59:26 <V_PauAmma_V> ktrace or some similar tool should tell you how it's trying to open it.