Replying to
@team@manitu.social Hübsch! Ist FreeBSD Support geplant bzw gehen eigene ISOs?
Remote
not Evander Sinque
@FiLiS@mastodon.social
mastodon 4.8.0-nightly.2026-10-06FreeBSD and death metal. #RUNBSD
580 Followers
956 Following
23 Posts
Joined April 02, 2017
Getting woken up to clean up teenager barf. It's been a while. #parenting
Family gatherings at home. So nice, so exhausting.
Waking up to a bunch of #FreeBSD security advisories. Ugh.
I should stop giving people the shittier options that also involve more work. They tend to always pick them.
Replying to
@h3artbl33d @jpmens yeah, but that is for a planned maintenance next week. Can't see any details on the current issue
Replying to
@stefano@mastodon.bsd.cafe same. Taking regular breaks might help. Have a great day anyway! 🤞
Replying to
Replying to
It's a very weird setting causing the controller to - duh - expose only n drives to the host. You can't choose which, it seems to just expose the first n drives. FreeBSD wouldn't boot with 36 drives exposed, but does with 4 or 16. MBR bootloader that is.
Replying to
@bagder@mastodon.social the AI talk at #EuroBSDcon was hilarious, though. But I'm sure you'll always have something to talk about. Hope, this will calm BS submissions down a bit.
Replying to
@Larvitz thank you so much for your post. Do you run this in a jail? I ran into an issue where nginx would return this error: sendmsg() failed (22: Invalid argument) while handling initial packet .... Looks like it is fixed by using the v4/v6 IPs with the listen directive, since FreeBSD too picky about the originating IP address.
Replying to
@Larvitz ah, I'm running in a non-VNET jail, could be that this is what caused my issue.
Replying to
Replying to
@darth@silversword.online using FreeBSD on servers since about 2000, daily driving it on laptop and desktop since about 2017