My first Unix was a BSD as it turns out. Ultrix 4.2. I did get a chance to play with a Linux system around the same time - fast and crashy. Pretty sure it was before there were formal GNU/Linux distributions.

and it's still fast & crashy. I'd prefer FreeBSD desktop if had driver for my multi-function hub / media dashboard with Alcor Micro Corporation chips, and RAM huge-pages

of course, I have it dual-boot, just not used as much due to using those more often

but when I can use *BSD for a server, I prefer that firstly

darwin: Way less crashy nowadays.

I had no idea about Wallnut Creek back then. I would have got a much earlier start. We only had 264bps at the time. I was finally able to find a boxed copy of Redhat 9. I still have the disks and manual. It took many years to realize unix-like was really a thing still happening. It's wild that Wallnut Creek > iXsystems

rtj: Don't forget BSDi.

You are right.

bbiab, snagging diner

dinner*

Heh Ultrix... I ran Remedy on that...

this may sound like a repeat and i am just being an idiot.. nvidia drivers are just updated on my server.. do i HAVE to reboot to gake it?

'gake'?

voy4g3r2: yes

i set zfsboot_swap_size to 4g and i have 8 disks for zfs obviously. shows my swap as 32gb because i guess it used 4gb on each disk. is that right/expected?

sounds reasonable

also sounds like way more swap than is needed

ya srsly

i'm gonna change it to 1g so it only ends up as 8gb ram

what doesn't feel right is why put swap on every drive? doesn't that mean if any of the drives fail, the box crashes because now swap is broken?

i thought swap only went on 1 drive or smth

depends on your requirements, but i'd usually mirror it because almost nothing should be using swap anyway

also, kernel dump size is limited to a single swap device, so you lose one of the main reasons to add swap nowadays

I think more typically the installer creates swap as a mirror across all of the drives.

sig`: ah ok thanks. yeah i was just wondering if they were pushing dev code into CURRENT or just keeping 2.3 until 15.0-RELEASE so that answers my question.

to have full disk encryption for zfs using geli, does that mean every time i reboot a server i gotta get an ipmi connection to type the geli pw in before it'll boot?

kerneldove_: unless you have a local console, yes.

hm dang. do many ppl use it then? seems bad for uptime. like if a server crashes doesn't it normally automatically reboot? that would prevent it

kerneldove_: I believe what most people would do on a server is to only encrypt some additional "data" disk, and then boot normally, having to SSH in to un-lock the additional disk.

ah ok ty

kerneldove_: But still, your approach is not wrong, you could totally use some IPMI or out-of-band channel.

Macer: -CURRENT has dev code, not the 2.3 release

Hey folks. I work on a security product which my organization is investigating FreeBSD support for. This product works on Linux using eBPF kprobes. For FreeBSD, my preference would be to use dtrace; however, as far as I can tell (maybe I am searching for the wrong thing), there is not a stable API for loading and interacting with dtrace scripts (there are the utilities, obviously) in the vein of libdtrace on Illumos/macOS. If there is, I have not encountered a manpage

for it - is such a thing available? Would there be an appetite for such a thing if not?

im trying to find openssl3 package for freebsd15, but i get 403 here: pkg.freebsd.org/FreeBSD:15:amd64/latest/All

do you know where i can find it?

dogg0: install it using the "pkg" tool, or if you insist on downloading it manually, fetch the packagesite file from the latest/ directory and examine the manifest to find the package filename

it's in /usr/ports/security/openssl3..

forgive me, noob here trying to fix issue with pkg thanks

31, 32, 33, 34, 35

thanks

dogg0: you don't want the openssl3 package to fix the pkg issue, you want the current version of misc/compat14x. you'll probably need to rebuild it from ports, at which point you may as well just rebuild pkg from there as well

yay! got it

if i really want to test 15, am i best to wait until the 5th when stable branch is created?

dogg0: the current issues are caused by pkg.f.o being behind the release itself (combined with some recent breaking changes in src) which will work itself out once the rebuild finishes... it's hard to say when that will be but probably a week or two. in general i don't recommend using pkg.f.o with -CURRENT anyway

appreciate the advice thanks again