cant believe im actually fixing stuff and not just begging others for help

it's like a whole new world

asking for help is a sign of strength

It's being fully human, as we are communal beings.

ya but i gotta be able to admin a box myself and till now i needed mostly begging to do it

so i got caddy running again and it has http/3 quic now. starts up fine, runs fine. but i see in caddy log message that failed to increase receive buffer size

so github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size#bsd says to increase it. that advice safe?

Title: UDP Receive Buffer Size · lucas-clemente/quic-go Wiki · GitHub

i dont trust non-bsd ppl

polyex27, I've been here (since I returned) 3.5 years, and I happily do both - sometimes alternating, sometimes together, as in "help! I started fixing this document and I don't understand what it should say!"

well im sure ill still ask for help, like i am now with the maxsockbuf advice. it's just amazing to actually be fixing shit on my own box myself. never thought i'd see the day

i just doubled the default maxsockbuf

Can I get a hand making fusefs go? Or if someone else can tell me a good way to read an exfat filesystem....

I haven't used fuse, and I'm not sure about .. the daemon, where it is or how to start it.. or how to tell fuse to use exfat, even?

So, I bought this 16TB m.2 SSD which I do not trust. `file -s /dev/da1p2` tells me it is. a `DOS/MBR boot sector".  I can `od -c /dev/da1p2` and I see the word "EXFAT"  in the output. Am I on the right track?

gh00p: How much did you pay for the ssd? Too good to be true? I would expect a disk like that to show up as an NVMe...

gh00p: and if you bought it, aren't you going to wipe it and put your own FS on there?

koobs: I don't disagree at all, but it's also a proper _good_ feeling when you do figure something out on your own

gh00p: I can almost guarentee you got scammed.

There's no way 16TB fits on any M.2 form factor; the 16TB SSDs that you can buy take up either 2.5" via U.2 or the "Ruler" form factor that Intel is pushing.

Actually, I think the 16TB SSD I saw was 3.5"

<debdrup> "Graham Perrin: the project isn't..." <- The conversation began in a FreeBSD area where GitHub is primary.

polyex27: why is caddy opening a UDP port??

oh, probably because QUIC…

debdrup: they make legit 2.5" 16TB ssd

but tehy're also thousands of bucks new

heh, what do you know

you can get a 16TB m.2 nvme

but its not exactly 2280...

oh pardon, thats ngsff being compared to m2, <-- learning

Measuring only 30.5mm x 110mm x 4.38mm, the NGSFF

form factor offers three times the capacity of a 2.5 inch while maintaining

serviceability in an M.2 size.

(I do imagine you're right about it being a scam fwiw)

how can I change my pkg server?

plasma, it's in /etc/installurl.

oh, i meant the other guy.

my bad.

nvm ;)

V_PauAmma_V: now I realise, the example screenshot in GitHub-provided documentation is misleading (as a result of dimming parts of the shot).

oh, also i'm in the wrong channel. so i'm guessing you also have /etc/installurl?

Now I see, edits from maintainers allowed by default, and not only with drafts:

anyone here using doas to give out privileges to accounts, rather than sudo?

No. I didn't even know that was a thing.

Well, it almost isn't a thing. I don't know what, but something from OpenBSD is missing in FreeBSD which makes doas work nice. I think it's about remembering you for a while like sudo does, so you don't have to type password every single time

But take it with a huge grain of salt, as I didn't do the research

i used it previously until they decided to make it "secure" and it stopped doing something sudo can (i don't remember what exactly, didn't look back)

As far as I know, it's just that the OpenDOAS port has the persistence flag disabled by default on compilation, but it can be built with it and added to doas.conf as `permit persist :wheel`

They mention it follows the same method sudo does of relying on timestamps, and supposedly OpenBSD has a kernel API for this kind of auth

but yeah, it can be made to persist though not (supposedly) as securely as OpenBSD

is there a known problem with pkg right now on arm64 -current ?

f451: much easier to tell us what you're experiencing

w3m -dump -cols 2147483647 freebsd.org/status/report-2022-01-2022-03 > /tmp/test.txt && less /tmp/test.txt

Title: FreeBSD Quarterly Status Report First Quarter 2022 | The FreeBSD Project

meena: lol, point taken ;)

steew: FreeBSD doesn't package OpenDoas: it packages github.com/slicer69/doas

Title: GitHub - slicer69/doas: A port of OpenBSD's doas which runs on FreeBSD, Linux, NetBSD, and illumos

in fairness, there was a ton of output

ok in summary

The package management tool is not yet installed on your system.

Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:14:aarch64/latest, please wait...

Verifying signature with trusted certificate pkg.freebsd.org.2013102301... done

Child process pid=97234 terminated abnormally: Segmentation fault

it's "not installed" rn because i tried to fix the issue by deinstalling and reinstalling it

unfortunately gdb isn't installed either

f451: so, summary-summary: "pkg on CURRENT / aarch64 is segfaulting"

yes

maybe it's cos ive got retpoline enabled

make: "/usr/src/share/mk/bsd.prog.mk" line 68: warning: Retpoline requested but not supported by compiler or linker

i thought retpoline was all good?

maybe not

nah, same error

I've got a port I just upgraded... did a make reinstall, says it is installing v 1.59 but whenever I check the version of the bin it shows an older version. I did a find to see if there were two bins and there are not

Any ideas how to resolve that?

I guess I can copy from /u/s/p/net/rclone/work/bin/rclone to /usr/bin

Hi. In rsync, is there a way to preserve permissions *except* group? I am trying to back up a zfs volume to exFAT. I don't care about keeping the group, but I would like to be free of the error messages.

gh00p: -a, --archive archive mode; equals -rlptgoD (no -H,-A,-X)

gh00p: so if you expand that yourself, and drop the -g, you'll get what you want

meena, ah, tysm. I guess I have more options to remove to make this happy with exFAT though. :/

exFAT sucks. Is it likely that I can get away with formatting a 16TB SSD with ufs instead?

gh00p, Since FAT stores only to the 2-second level you will also need --modify-window=1 too.

rwp, oh, that makes sense. Thank you, I would not have figured that error out.

SpaceBass_laptop: what's the port?

rclone?

gh00p, It doesn't actually produce an error message. It just can never make the target "up to date". Because the timestamp on odd second files can't be equal.

And therefore rsync will always try to update the file thinking that the timestamp does not match.

Yes, errors without error messages are some of the worst. :)

My digital audio player uses FAT and I run into that issue rsync'ing files there.

But FAT is not exFAT. Does exFAT have the same time limitation?

gh00p, I guess not! en.wikipedia.org/wiki/ExFAT "Timestamp granularity of 10 ms for creation and modified times (down from 2 s of FAT ..."

Title: exFAT - Wikipedia

how can I sort files found by find ?

I tried find ./ -type f -print0 | sort -z

but it prints them all in one line, whereas I need them one per line

last1: remove -print0

genius - thank you! so find already outputs the null char ?

if you tell it to

last1, the sort -z reads zero terminated strings on input and *writes zero terminated strings on output*.

That's why they appeared to you as being all on one line. They were zero terminated not newline terminated.

last1: I guess, you're also aware of option -s in find(1)?

find -s ./ -type f -print

Results may differ, as mentioned in the manual page

Alternatively, with sysutils/bfs:

bfs -s ./ -type f -print

If it is me and I know there are no whitespace problems with files then I just use traditional newline terminated strings. Like: find . -type f -print | sort

Because it seems silly to use zstrings and then convert at the end. Ex: find . -type f -print0 | sort -z | xargs -0rL1

do you seriously need to use -print still?

even openbsd's find dropped that years ago

nacelle: that's for print0

(and some people never get used to not using certain parameters…)

I see a raw -print on the line above it :-)

(the only reason I got better at unix commands is after peers poked fun at me for using arcane syntax, maybe this helps, maybe its doesnt)