but the non-string keys part is new to me

I used to do aliasing and mapping and referencing of partial strings or "objects" in YAML, because we put huge blocks of bullshit into our hieradata… and it wasn't until we actually started to use a standard pattern of roles and profiles, where a) a huge chunk of that was put into profiles, and b) we introduced a pattern of making two queries:

one for defaults, and one for the actual config data and then merged them, that our hiera data became actually manageable.

bad times.

anyway: Anyone else got FreeBSD running on Hetzner? I'm getting facter is_virtual => false ; facter virtual ⇒ physical; while doing the calls that facter supposedly does produces: sysctl kern.vm_guest => kvm

On my local virtual machine, this works.

Hrm… but that's 14-CURRENT… the one that doesn't work is 13.1

message has been deleted

that's one thing I dislike about the slack bridge: you can't open those files

and threads

I don't miss those

fun…

found the issue: [1] pry(Facter:ResolversFreebsd:Virtual)> require_relative 'ffi/ffi_helper'

LoadError: Could not open library 'c': Shared object "c" not found, required by "ruby30".

Could not open library 'libc.so': Shared object "libc.so" not found, required by "ruby30"

from /usr/local/lib/ruby/gems/3.0/gems/ffi-1.15.5/lib/ffi/library.rb145in `block in ffi_lib'

now to track down why it's happening.

binford2k: do you know if you can disable threads in one room?

bastelfreak: is it that the threads just don't show up at all?

yeah and you cannot determine in irc if a message comes from a thread

like the one from CVQuesty. that's in a thread

I think the answer to disabling threads is no... slack rarely lets that sort of thing happen

I know discord has that capability

okay, so, turns out: facter requires libc.so — not /lib/libc.so.7, but /usr/lib/libc.so

which Facter version are you using? 3 or 4?

ewoud: 4

ewoud: contrast: https://github.com/puppetlabs/facter/blob/main/lib/facter/resolvers/freebsd/ffi/ffi_helper.rb#L8-L15 with: https://github.com/gronke/py-freebsd_sysctl/blob/master/freebsd_sysctl/libc.py

anyway, back to stealing, i mean, borrowing, code.

isn't that something the linker should end up doing? I don't know what I'm talking about with compilers so I may be wrong :P