what's the right word for how much of a comp is in use? cpu, ram, etc

demido: "utilization", maybe? That's the word I tend to see in AWS docs about metrics, at least.

dango ya that's prolly right

demido: you into aws?

no i don't support centralization

you?

neither. but I used to do stuff on aws.

it's a very inefficient and thus expensive platform

you agree utilization is right term for how much of a comp is in use?

doesn't surprise me

well i'd say "resource utilization" is a more accurate one if you are refering to physical hardware

as in windows's resource monitor

not just physical but vm too ya?

yeah

"Resource Utilization", I like that. I'm gonna use that now. :3

shit you are the guy who called me a monkey last time demido

awesome ty for the help guys!

nvm we are cool

anyone using input-leap used to be known as synergy? KVM software?

thought it was in ports but it is not

why does it take so long from powering off a linux guest until the bhyve process exits back to the command line?

has anyone booted an arch based iso on a bhyve vm more recently than 2016, using vm-bhyve

also, how do I get some more information than "bhyve exited with status 4"

mornings y'all

Hello, when I'm running freebsd-update -r XY.Z-RELEASE upgrade is there a way to skip the merge process and always install the new file?

and also answer "yes" to all questions

I'm asking this because I have all my configuration in Saltstack and I'd like to upgrade multiple jails automatically

mtll: " 4 exited due to an error"

well, I found that in the manpage

I was hoping there was some way to ascertain what the error actually was. more verbose logging, or something

there are 12 places it errors out, most have a preceeding print

hmm, I couldn't find anything printed anywhere

is "add logging to bhyve" an option?

I'll look into it some more later

I guess my more pressing question is, is vm-bhyve still being maintained? because it seems like some of the example configs are rather out of date

the arch one at least references the 2016 ISO

it's structured differently now, it seems based on poking around the iso FS

you could try applying that, building and running

or is there some other bhyve wrapper which is more hands off?

most VM software, like virtualbox, I can just give it an ISO and it'll boot, for the most part

i just prefer to run bhyve under s6 supervision managed by s6-rc for dependencies e.g. create the bridge before the tap/vmnet device

Alver secure_level? Maybe that's why you can't assign an IP... maybe. I had to temporarily change a jail's security level sometime in the past, but I can't remember why

does zfs handle async writes on its own so there is little benefit from mounting zfs with async flag?

scoobybejesus_tl: it turned out to be a combination of devfs rules and (afterwards) me using a Linux ifconfig syntax on BSD

mage: never tried it myself but I think you can do that with the ALWAYS_INSTALL option in /etc/etcupdate.conf

holy shiiit

FUSE exfat 1.4.0 (libfuse3)

ERROR: 'VIDEO' directory size 32768 is not divisible by 131072.

how to even deal with that

Hi all, quick question, what's the reason that the /var/cache partition is not on its own zfs volume by default? The way it is, it's part of a snapshot of the ROOT partition

hc: Unsure. But, you can always make it a separate dataset.

ek: I just did -- for all my freebsd machines

Just want to make sure I didn't miss an important point

Not that I'm aware of. As long as /var/cache is accessible, it shouldn't make a difference how it's segregated or mounted.

kk, thanks! :-)

So far, it is working fine

cool!

How does capsicum compare to pledge? As I understand it they're both ways for an application to basically limit what they can do

I need to mirror 14.3-RELEASE FreeBSD-base packages locally, so I don't keep fetching them again & again & again

I'm on 15.0-CURRENT

something like this should work: `doas env IGNORE_OSVERSION=yes ABI=FreeBSD:14:amd64 OSVERSION=1403000 pkg fetch -r FreeBSD-base -Uyao .`

15.0's not out yet is it? Due 11th July

septemberish

Reading here freebsd.org/releases/15.0R/schedule ahh ok stable 15 Sept 5th

erm decemberish freebsd.org/releases/15.0R/schedule

but `pkg fetch` really doesn't want to fetch 14 bits

I'm a newbie so I'll take your word for it.

problem worked around by slinging it in a jail