Build 10MB #NetBSD VMs That Boot in 10ms Using #smolBSD
https://ostechnix.com/build-10mb-netbsd-vms-boot-10ms-smolbsd/
Build 10MB #NetBSD VMs That Boot in 10ms Using #smolBSD
https://ostechnix.com/build-10mb-netbsd-vms-boot-10ms-smolbsd/
📢 The Call for Papers is open for BSD-NL Conference – Spring 2026 📢
We are looking for talks on any *BSD 🐡😈⛳ topic!
Whether you’re a seasoned speaker or just starting out, we’d love to hear from you.
Share your ideas and join us in Utrecht!
🔗 https://events.bsdnl.nl/early2026/
📆 2026-05-09 / May 9th 2025
🕐 10:00-23:00 CET
📍 Brouwerij Maximus (Utrecht)
🌐 https://bsdnl.nl
#BSDNL #RUNBSD #BSD #OpenBSD #FreeBSD #NetBSD #HardenedBSD #SecBSD #DragonflyBSD
It is nice they looked at #rust and found it good for #Linux, but may limit what platforms #Linux can run on. Curious what that means for #IOT, which I think tends to have little resources when compared to amd64.
I saw this post here on sdf/mastodon from a #NetBSD developer and it nicely explains why #rust as it is now is not really good for use on some systems:
📢 The Call for Papers is open for BSD-NL Conference – Spring 2026 📢
We are looking for talks on any *BSD 🐡😈⛳ topic!
Whether you’re a seasoned speaker or just starting out, we’d love to hear from you.
Share your ideas and join us in Utrecht!
🔗 https://events.bsdnl.nl/early2026/
📆 2026-05-09 / May 9th 2025
🕐 10:00-23:00 CET
📍 Brouwerij Maximus (Utrecht)
🌐 https://bsdnl.nl
#BSDNL #RUNBSD #BSD #OpenBSD #FreeBSD #NetBSD #HardenedBSD #SecBSD #DragonflyBSD
Linux 7.0 Officially Concluding The Rust Experiment - Phoronix
｢ formally concluding the "Rust experiment" with upstream kernel developers now in acceptance that Rust for the Linux kernel is here to stay ｣
It is nice they looked at #rust and found it good for #Linux, but may limit what platforms #Linux can run on. Curious what that means for #IOT, which I think tends to have little resources when compared to amd64.
I saw this post here on sdf/mastodon from a #NetBSD developer and it nicely explains why #rust as it is now is not really good for use on some systems:
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟲/𝟬𝟮/𝟬𝟵 (Valuable News - 2026/02/09) available.
https://vermaden.wordpress.com/2026/02/09/valuable-news-2026-02-09/
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/09) available.
https://vermaden.wordpress.com/2026/02/09/valuable-news-2026-02-09/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
Registration for BSDCan 2026 is open at https://www.bsdcan.org/2026/registration.html + tutorial schedule published.
#bsdcan #freebsd #openbsd #netbsd #development #networking #devops #sysadmin #conferences
For more on BSD and the BSD conferences, see https://nxdomain.no/~peter/what_is_bsd_come_to_a_conference_to_find_out.html (or tracked https://bsdly.blogspot.com/2025/11/what-is-bsd-come-to-conference-to-find.html +
https://medium.com/@peter.hansteen/what-is-bsd-come-to-a-conference-to-find-out-06acd7d77fd8 )
Registration for BSDCan 2026 is open at https://www.bsdcan.org/2026/registration.html + tutorial schedule published.
#bsdcan #freebsd #openbsd #netbsd #development #networking #devops #sysadmin #conferences
For more on BSD and the BSD conferences, see https://nxdomain.no/~peter/what_is_bsd_come_to_a_conference_to_find_out.html (or tracked https://bsdly.blogspot.com/2025/11/what-is-bsd-come-to-conference-to-find.html +
https://medium.com/@peter.hansteen/what-is-bsd-come-to-a-conference-to-find-out-06acd7d77fd8 )
🚨 Spring is upon us! 🚨
To celebrate this we want to announce, with a little more time this time, the next edition of the BSD-NL Conference.
BSD-NL Conference - Spring 2026 🐡😈⛳
📆 2026-05-09 / May 9th 2026
🕐 10:00-23:00 CET
📍 Brouwerij Maximus (Utrecht)
🌐 https://bsdnl.nl
If you have a talk prepared already we want to hear from you! You can submit your abstract at https://events.bsdnl.nl/
Hack! You can even register for the event already... the price we charge is to cover lunch. https://tickets.bsdnl.nl/bsdnl/early-26/
#BSDNL #RUNBSD #BSD #OpenBSD #FreeBSD #NetBSD #HardenedBSD #SecBSD #DragonflyBSD
🚨 Spring is upon us! 🚨
To celebrate this we want to announce, with a little more time this time, the next edition of the BSD-NL Conference.
BSD-NL Conference - Spring 2026 🐡😈⛳
📆 2026-05-09 / May 9th 2026
🕐 10:00-23:00 CET
📍 Brouwerij Maximus (Utrecht)
🌐 https://bsdnl.nl
If you have a talk prepared already we want to hear from you! You can submit your abstract at https://events.bsdnl.nl/
Hack! You can even register for the event already... the price we charge is to cover lunch. https://tickets.bsdnl.nl/bsdnl/early-26/
#BSDNL #RUNBSD #BSD #OpenBSD #FreeBSD #NetBSD #HardenedBSD #SecBSD #DragonflyBSD
Few days ago I successfully configured #coturn to have a TURN/STUN server for in-family calls. But … looks like bots or some bad guys constantly trying to connect to my TURN server to use it for something 😒
Of course, it is impossible, since anonymous access or any other access without right key is impossible. But, there are no IPs of attackers in the log file, even wth "Verbose" directive — only my local and public IPs and my server's hostname 
Maybe, there is some way to force coturn to display IP addresses of connected clients, so I could ban them all with fail2ban?
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.
Few days ago I successfully configured #coturn to have a TURN/STUN server for in-family calls. But … looks like bots or some bad guys constantly trying to connect to my TURN server to use it for something 😒
Of course, it is impossible, since anonymous access or any other access without right key is impossible. But, there are no IPs of attackers in the log file, even wth "Verbose" directive — only my local and public IPs and my server's hostname
Maybe, there is some way to force coturn to display IP addresses of connected clients, so I could ban them all with fail2ban?
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.
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 been a couple of years now since I migrated from Linux and really enjoying it.
be safe and keep up the excellent work,
#appreciation #bsd #kiss #unix #freebsd #openbsd #netbsd #dragonfly #runbsd #illumos
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
Newsflash: we have a date for BSD-NL, for the Early 2026 day-conference. Go follow @bsd_nl to get the announcement straight into your timeline 
#BSDNL #BSD #OpenBSD #HardenedBSD #FreeBSD #SecBSD #NetBSD #RUNBSD #MyMotherRunsBSD
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
