schmonz.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
#NetBSD 11 RC1 released!
No official announcement yet but Phoronix has the deets: https://www.phoronix.com/news/NetBSD-11.0-RC1
boostedI believe 'man 7 entropy' will explain what #NetBSD uses that for. On my machine, file "/var/db/entropy-file" gets recreated on every boot.
Victory is mine! #NetBSD 11 RC1 is working!
Overall, pretty uneventful...
Now, I will let it rest for a little while, until qemu 9.2.4 has finished compiling.
As I wrote before (https://mastodon.bsd.cafe/@evgandr/115912395421390028) I tried to use TURN server for communication with my relatives, but failed to setup secure enough solution. So, I decided to try an old and reliable solutionย โ Asterisk. With the help of a book "Asterisk: The Definitive Guide" from J.V. Meggelen & R. Bryant & L. Madsen, of course.
First, I was forced to build the asterisk package by myself (from ports, ofc), since the binary version from NetBSD repository compiled with the all DB support, except my favourite PostgreSQL database.
By the way, adding users and writing dialplan with the help of aforementioned book was not so hard as I expected
. Same for network setup. Since, I'm using PJSIP I just opened SIPS port and a range of UDP ports for RTP protocol on the my firewall. Despite, my home network hidden behind NAT on the router, there are no big problems with networkingย โ end-user devices and an Asterisk server connected with use of simple star topology.
Surpisingly, the quality of the voice call is excellent comparing with service, provided by local cellular network operators. I suppose, that the secret in used codecs, or it is because there are not so much users (only 2) of my service.
[3348/9317] Compiling C object libqemu-mipsn32el-linux-user.a.p/linux-user_signal.c.o
So, roughly 30% done. I think the #NetBSD VM will be done first!
The good side of this, is that I can keep an eye on both the #NetBSD 11 VM and the compilation of qemu on my #Slackware server! ๐
It works, but it is going to be painful: since the qemu network emulation provides the VM with an IPv6 address through DHCP, #NetBSD sysinst tries IPv6 first, times out, then tries IPv4... all of this to be redirected by the web server and go through IPv6 - timeout - IPv4 again.
In other words: it downloads, but really really slowly. โน๏ธ
Any help getting out of that painful loop is greatly appreciated (I know how to do it on an installed machine, just not in sysinst) 
It seems #NetBSD 'sysinst' still has issues with the 'curses' qemu console, but it remains readable, so onward!
From:
The following features are to be removed from #NetBSD in the future:
- groff(1). Man pages are now handled with mandoc(1), and groff(1) can still be found in pkgsrc as textproc/groff.
- pf(4). This packet filter is obsolete and unmaintained in NetBSD. It will be eventually removed due to possible long-standing security issues and lack of multiprocessor support. New installations should use npf(7).
No 'npf mastery' book so I really need to read that man page...
$ /usr/local/bin/qemu-img create -f qcow2 /opt/qemu/netbsd11.img 20G
20GB should be enough for most installations I suppose... #netbsd 
~/files/download/ISO/NetBSD$ curl -O https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-11/20260206082425Z/amd64/installation/cdrom/boot.iso
Yeah, going to test #NetBSD 11-RC1 like a savage as usual... ๐ค

boostedI had to use a breadboard to set up a serial console, but I got #NetBSD working on the VisionFive 2! ๐ฅณ
Ethernet works great, so I will mostly talk to it over SSH, I suppose.
Registration for BSDCan 2026 is now open https://www.bsdcan.org/2026/registration.html and tutorials schedule is published.
#bsdcan #openbsd #netbsd #freebsd #libresoftware #freesoftware #conference #development #networking #sysadmin #devops
Just a shout out to everyone directly or loosly involved in *BSD world here on fedi and elsewhere.
Thanks for having me here. It's now a couple of years now since I mograted from Linux and really enjoying it.
be safe and keep up the excellent work,
#appreciation #bsd #unix #freebsd #openbsd #netbsd #dragonfly #runbsd #illumos
boostedWe got #CentOS Mascot before #GTA6
https://blog.centos.org/2025/05/release-the-quokka/
Let's go #NetBSD we should get Mascot other than logo

In the majority of cases there actually is no separate inet_pton() manual page.
https://man.freebsd.org/cgi/man.cgi?query=inet_pton&sektion=3
https://man.netbsd.org/inet_pton.3
http://tribblix.org/man/man3c/inet_pton.html
https://man.omnios.org/man3c/inet.3c
http://uw714doc.xinuos.com/en/man/html.3N/inet.3N.html
Although most of those call out inet_pton(), SCO #UnixWare in fact documented the four human-readable IPv4 formats for inet_pton(), and did not even have an inet_aton().
In #NetBSD, the internal inet_pton4() function was indeed updated by Christos Zoulas from the old Paul Vixie code to support the four human-readable formats of inet_aton(), 22 years ago; although it's not clear where this additional IPv4 conversion functionality is actually used.
The old Paul Vixie code from 1996 is retained in GNU libc, #FreeBSD, & #OpenBSD; this being code from the BIND DNS client library.
It was superseded by a from-scratch reimplementation based around a str2inet_addr() function in #Solaris/ #Illumos/ #Tribblix/ #OmniOS. musl libc also has its own from-scratch version.
Everything that can accept human-readable IPv4 addresses in place of hostnames, and that does so by using the conventional C library inet_aton() or inet_pton() functions.
A single (32-bit) number has been an accepted human-readable form from the start, back in the 4.3BSD days. It's a thing that gets regularly rediscovered.
(Bernstein's networking tools use a ip4_scan() function that only supports strict 4-decimal-numbers form. But several of them special case and re-map the string "0" before calling this function. libowfat's scan_ip4() is similar to ip4_scan(). As is ip4_scan() in @ska's libstddjb.)
This and three other accepted formats are explained in all of the #FreeBSD, #OpenBSD, #NetBSD, and Linux GNU libc manual pages. They also explain why 0x00000000 and 0x7F000001 and 0177.1 will work as IPv4 addresses with such programs.
Just added short ๐๐ผ๐ผ๐ธ ๐ผ๐ณ ๐ฃ๐ (๐ฐ๐๐ต ๐๐ฑ๐ถ๐๐ถ๐ผ๐ป) [Book of PF] review/update to ๐๐ผ๐ผ๐ธ๐ ๐๐ฏ๐ผ๐๐ ๐๐ฟ๐ฒ๐ฒ๐๐ฆ๐ [Books About FreeBSD] article.
https://vermaden.wordpress.com/2022/02/04/books-about-freebsd#book-pf-4th
Just added short ๐๐ผ๐ผ๐ธ ๐ผ๐ณ ๐ฃ๐ (๐ฐ๐๐ต ๐๐ฑ๐ถ๐๐ถ๐ผ๐ป) [Book of PF] review/update to ๐๐ผ๐ผ๐ธ๐ ๐๐ฏ๐ผ๐๐ ๐๐ฟ๐ฒ๐ฒ๐๐ฆ๐ [Books About FreeBSD] article.
https://vermaden.wordpress.com/2022/02/04/books-about-freebsd#book-pf-4th
https://bentsukun.ch/posts/netbsd-rust-kernel/
#rust #netbsd
RT: https://bsd.network/users/jaypatelani/statuses/116004550797346180
Rust in the NetBSD kernel seems unlikely
Rust is everywhere, and it's no surprise it's also made its way into the lowest levels of certain operating systems and kernels, so it shouldn't be surprising that various operating system developers have to field questions and inquiries about Rust. NetBSD developer Benny Siegert wrote a blog post about this very subject, and in it, details why it's unlike
https://www.osnews.com/story/144326/rust-in-the-netbsd-kernel-seems-unlikely/
Since my home server not intended for use by any people outside of my city (plus some VPN endpoints in other countries) โ it is ok to ban some unwanted countries and cities from which I don't expect anything good, except attempts to hack my box to use my resources or set me up
.
So I added some GeoIP blocking to the npf with script to update GeoIP list โ I blocked China, Iran, North Korea, etc and Moscow (because there are a lot of government and commercial backed bots coming from here). Results are good โ the bots don't disappeared completely but the speed of adding new IPs to the blacklist is decreased
Sadly, I was unable to add USA and UK to the list, because looks like there are some limits (not found how to increase them
), which disallows to load a lot of CIDRs for these countries to the blacklist.
Latest ๐ฉ๐ฎ๐น๐๐ฎ๐ฏ๐น๐ฒ ๐ก๐ฒ๐๐ - ๐ฎ๐ฌ๐ฎ๐ฒ/๐ฌ๐ฎ/๐ฌ๐ฎ (Valuable News - 2026/02/02) available.
https://vermaden.wordpress.com/2026/02/02/valuable-news-2026-02-02/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
Latest ๐ฉ๐ฎ๐น๐๐ฎ๐ฏ๐น๐ฒ ๐ก๐ฒ๐๐ - ๐ฎ๐ฌ๐ฎ๐ฒ/๐ฌ๐ฎ/๐ฌ๐ฎ (Valuable News - 2026/02/02) available.
https://vermaden.wordpress.com/2026/02/02/valuable-news-2026-02-02/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
boosted#NetBSD peeps! There is a (mostly) working #Valgrind implementation for NetBSD at https://github.com/paulfloyd/valgrind-netbsd. It would be great if we could get a (binary) package for it!