GeoBarRod: base generally isn't on the bleeding edge of OpenSSL for a lot of reasons.

One such is that it'd mean a lot of more churn of the tree, since OpenSSL is a big thing to pull in, but another is that it's a lot of work to integrate properly, with things like ossl(4) further complicating things.

Also, 3.1 has an EOL _before_ 3.0.. So, you know, that's probably not unimportant too. :D

Everything in base that'll benefit from OpenSSL probably won't benefit too much from the things noted in the release notes of OpenSSL 3.1, and everything in ports can sumably be custom-built if you're willing to put in the effort using security/openssl31.

presumably*

@debdrup Thanks for the quick reply. Certainly stability is the most important thing. So I'll keep the ports with security/openssl31. Have a great day! :D

GeoBarRod: So, you're already using OpenSSL 3.1 then? I'm just curious about your question, honestly.

I'd assume if you're using the port version of OpenSSL, all your other ports will also be linked to that (provided pkgconf hasn't broken it.)

Is this ask specifically about base OpenSSL?

heya how's 14 running?

no jc

sometimes major versions can be kinda rough launch

im sort of mixing oss and pulse randomly and none of the mixers are pikcing up on applications themselves (i can only adjust volume for the whole system), is there a big picture thing im missing (i3 with startx, dbus enabled)

Seems like 14 is not swapping out firefox processes, causing my system to be practically unusable with more than a handful of firefox tabs open

kernel+userland is 14 but firefox packages are built for 13 - not that this should matter

ek: Funny you mention that. pkgconf is currently breaking it, pending bugs.freebsd.org/bugzilla/show_bug.cgi?id=273961

Title: 273961 – devel/pkgconf: unconditionally prioritises base system libraries

vkarlsen: Yep. That's exactly why I mentioned it.

:)

what is the correct way to automatically decrypt and mount a geli partition on a software raid1 at boottime? i asked in the forum but i am too impatient to wait for answers so i ask here too

@ek So, you're already using OpenSSL 3.1 then? I'm just curious about your question, honestly. Yes it's. I use OpenSSL 3.1 right now via port.

uno.m2m.pm/freebsdbug.jpg looks like i just stumbled upon a bug in the installer.

any pointer? known? good to report?

armin: which version exactly?

yuripv: ^

armin: nice yamaha mixer;)

plasma: oh that's my mx-16gu, the only reason is that after over 10 years i got tired of re-plugging things. :D

bootonly does not contain any distributions, but it should not report failure like *that*

armin: ;)

yuripv: that's a dialog usage error. it expects 3 arguments, and gets 7. that should definitely not happen, no matter the installation image.

yuripv: admittedly, my hardware is very likely questionable or even broken, so i assume nobody hit that bug before.

yuripv: this is a thinclient i got for free, i don't expect that thing to work. :)

I mean it tried to report legitimate error, but did it wrong, yes; probably something not updated when switching over to bsddialog

oh!

yuripv: any pointer what the filename of that script that utilizes dialog is? i'm trying to find it through the github web interface so i don't have to clone hundreds of megabytes just to check.

usr.sbin/bsdinstall/distextract/distextract.c

search for "Error while extracting"

perfect! thanks!

i'm on a ryzen 9 with 32gb of ram, the web interface is basically completely useless

it's so slow that when i click on something i have to wait several seconds for the browser to update the content

ok that makes absolutely zero sense, i'll have to use a plain terminal window for that.

does our RPi image come with UFS or ZFS?

antranigv: with ufs by default, zfs as a module

otis I wonder if I can use ZFS on Root for the RPi, now that mkimg supports it

antranigv: i can't answer that question (i'm not sure whether loader on rpi supports it, but i'd say yes)

last resort would be using something like truncate

antranigv: I have ZFS Root on a RPi 4 with /bootfs as UFS, and /boot as a symlink to /bootfs/boot. Or were you thinking of ZFS Root without a separate /bootfs?

tmp_ I'm okay with separate bootfs, as long as I can have ZFS without truncate on UFS

tmp_ can you point me to a guide to setup? :)

I adapted a lot from setting up 9.x and 10.x on PowerPC way back when.

I'm not sure I have anything specific.

tmp_ lemme ask it in a different way. did you build the setup yourself or was it possible to do with bsdinstall and base tools?

Oh, wait, my notes refer to pages in the Wiki: wiki.freebsd.org/RootOnZFS/UFSBoot

Title: RootOnZFS/UFSBoot - FreeBSD Wiki

I'm pretty sure I booted from a default image written to one SD card, then used an adapter to prepare the actual SD card I made into the system.

Next week I'll have the parts to start setting up another RPi 4, I may try booting bsdinstall from a USB stick, if that works.

do we know what are the very minimum options for llvm to build mesa successfuly?

plz dont tell me i need MLIR or openmp