RhodiumToad, someone said you might know about FreeBSD and slow SD write speeds.

I got a 512GB SDXC that's writing <1MBps right now. Tried two different readers, two different adapters, and no adapter

ExclamationPoint: It's only on FBSD that it's that slow?

SDXC on a usb-attached reader?

is it a new card or an old one?

hi! im an architect currently working on a proposal for a future freebsd headquarters

any suggestions to what the design concept should be?

a building based on beastie would have too much of a religious connotation i'm afraid

I'm… so confused.

meena: he's building a building but doesn't want beastie on the front of it because it looks satanic

TommyC: yep

i could use beastie's three pronged spear

Church of Satanic Temple does have some problematic people associated; it does serves its purpose to challenge christian-religion propagandist US governments

yep

you know my godfather shared jailcell with the famous church burner

An opensource project probably isn't going to have a headquarter..

but maybe a bunker?

Woosh.

or foundation

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.

what is the status of ath10k / ath11k and ath12k?

they seem to be in kernel sources but for some reason not connected to build system

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

i thought the wiki had that

man.freebsd.org/cgi/man.cgi?query=l…+and+Ports&arch=default&format=html && wiki.freebsd.org/RootOnZFS/GPTZFSBoot different way rtprio

Title: loader.efi

is there any way I can compute the hashes in the master.passwd file by hand?

I need to feed this file to dovecot as an authentication backend, and need the hashes but these accounts don't actually exist

signalblue: In the master.passwd file, the password field is the encrypted form of

the password, see crypt(3).

rtprio: I know that

I want to take a plain-text password and convert it to the encrypted form that is in that file

openssl passwd -salt blah -6

thanks

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

I might have done both of those things- externally generate a hashed password; create an account to harvest the hashed password

it is just salted sha, you could do it by hand if you had the patience

or didnt know a few openssl verbs

How does "pkg" determines "__FreeBSD_verision" (short of running it & getting the message about mismatched versions)?

Is that recorded some where for the explicit purpose of getting the value after installing the world?

Alternatively, is there some knob that I could set to insert "__FreeBSD_version" in "uname" output?

i think it's uname -K

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.

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

i dont run release, whats yours say?

1302506 (stable/13)

... well outout is only the number; added "(stable/13)" to indicate the source

freebsd-version prints that, but it means something else

Right

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.

i don't understand how freebsd-version works tbh

the manpage seems clear enough

-k tries to find the default kernel path by parsing loader.conf, then finds the version number within that

when you only run current, it's always the same

always the same as what?

parv: pkg actually determines the __FreeBSD_version by reading it from the ELF headers of some binary

and that binary is the first to be found of $ABI_FILE, /usr/bin/uname, or /bin/sh

it's always 14.0-CURRENT. never patch level. which makes sense, but also makes it not useful, unlike uname -K

readelf -n /usr/bin/uname

freebsd-version is returning the release name (like uname -r), not the __FreeBSD_version

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.

RhodiumToad, Thanks

there's nothing really greppable in the pkg code that does that part

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)'"

Tried running stat, fstat, fuser, & lsof on /dev/klog to see what might have that open...but to no avail.

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?

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?

ktrace or some similar tool should tell you how it's trying to open it.