other than modifying /usr/local/etc/rc.d/nginx to require named, is there a cleaner way of doing that? maybe in rc.conf? either adding a delay for a specific service or something like nginx_depend="named" ?

if not, then adding that seems kinda rudimentary, and I feel like a patch is required :)

antranigv, Why does your nginx require named? That's not a normal requirement. Certainly my nginx installs do not require named.

rwp by default it doesn't, but I have some proxy_pass which has DNS entries in it, and because I use IPv6 + DNS I ended up using both internal and external domain names.

rwp but I did just hit the issue again. WriteFreely didn't start automatically, it needed MySQL.

now I could move MySQL into another jail, and then use the depend= feature in jails.

If you need it then you need it, and should modify your rc script to require it. But that would not be a patch forced upon the rest of us.

rwp what I did mean is a patch for rc.subr, for a feature like <name>_depend, not patching nginx itself :P

otherwise having named as a dep for nginx would be a nightmare yes :D

Ah... Gotcha.

Pretty sure it is rcorder(8) which handles the dependencies.

has anyone here been able to successfully get the signal-desktop ports package to build?

rwp turns out there's a better way to do things: antranigv.am/posts/2025/01/changing-freebsds-rcorder-without-patching

Hello

When Poudriere finishes compiling

do I need to do anything else to update packages?

because when I run "pkg version -v" it still shows that my packages are out of date

i have been using Poudriere for a little while and i never had that issue before

after Poudriere finished compiling, my packages were automatically updated

"pkg upgrade" also does not do anything

is there a way to set the MAC address on an interface in Bhyve

crb yes

crb according to the man page it should be tapN[,mac=xx:xx:xx:xx:xx:xx][,mtu=N]

here's a dumb questions: if I want to upgrade from 13.1 to 14.2, should I do 13.1 -> 13.2 -> 13.3 -> 13.4 -> 14.2 OR should I do 13.1 -> 13.2 -> 14.0 -> 14.1 -> 14.2 ?

antranigv: You can skip steps

0fg

sigh.

Is there a freebsd `watch` command available for macos?

no, macos doesn't have this, at least no man page and it's not in the PATH

alas

antranigv, I would think you can go 13.1 to 13.4 to 14.2.

ghoti: there might be one in ports, I usually write my own though. Something like: while x=$(pgrep svnlite); do clear; ps auxd -p $x; sleep 2; done

function watch() { while true; do clear; $@; sleep 2; done }

ghoti gwatch is a thing, I guess.

but I do what pertho does.

vkarlsen you *can*, but I don't think its recommended. I once upgraded from FreeBSD 7 to 10 directly, but in that case the rollback might not work, other things might be broken, etc.

so (I feel like I'm repeating what I said in Discord, btw :P) I'm not looking for the "possible" way to upgrade a system, but rather the recommended way!.

I don't think 13.1 -> 14.2 is as big a leap as 7 -> 10 :D

antranigv: are you using root on ZFS? Make a snapshot.. try upgrading to 14.2.. if anything breaks, you can always go back to the snapshot/boot environment

pertho I know, I know, but again, this is not for that case :D

we (as very advanced users) know all of this

but newcomers don't

it would be nice if the FreeBSD docs mentioned the best practice in it

and most of them don't even check the installation page e.g. freebsd.org/releases/14.2R/installation

it says: The freebsd-update(8) utility supports binary upgrades of amd64, arm64, and i386 systems running earlier FreeBSD releases. Systems running 13.4-RELEASE or 14.1-RELEASE can upgrade as follows

but no one reads this, so, I'm making a web app where you input which version you're on, which version you wanna go to, and it tells you the recommended path.

hell I don't even update servers at all. I just reboot and iPXE boots the newest image. but we also need to take care of newcomers :D

I do always read the doc but with 14.2 I forgot to check the errata

Which explained the main issue I had

I love the way that with FreeBSD I can always find a reason for things that break

"It's not working, but I know why!"

can anyone here recommend a replacement for tinydns (that supports DNS views)?

antranigv: Yeah, I just yolo those things and deal with fallout if things go awry, but I understand this is not appropriate in all situations :)

if anyone interested...

jim brown on qemu streaming for NYC*BG

NYC*BUG