#netBSD

RT: https://mstdn.jp/users/landley/statuses/116409848816616141

@justine
Looks quite simple port without patch.
But reading the description, it seems to be a wrapper for specific syscall with the same name as the port.
So it would depend if the syscall exists on #OpenBSD and compatible with the one on #FreeBSD.
If #OpenBSD matched above prerequisite, and #OpenBSD ports infrastructure is enough alike with #FreeBSD #ports (IIRC, #NetBSD, the direct origin of #OpenBSD, once introduced #FreeBSD #ports framework far before when it was still quite simple and switched to their own #pkgsrc later), the conversion would be trivial.

On #FreeBSD, porters (including myself) first create a port under specific category directory such as graphics, test, hook on category Makefile, generate diff and file a PR on Bugzilla and/or open review on Phabricator.

For any #ports that are not intended to be included in official #ports, no need to hook to category Makefile and no need to file PRs / opening reviews. Ports framework allows it. Hooking on category Makefile is needed to be picked for official #pkg building. Maybe #OpenBSD #ports, too, as without the allowance, how porters attempt to make new ports?

By searching Internet, found this.
https://www.openbsd.org/faq/ports/guide.html

And FreeBSD has a (large) document "Porter's Handbook".
https://docs.freebsd.org/en/books/porters-handbook/

An example how I've added new FreeBSD port.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293719
https://reviews.freebsd.org/D55798

And its relevant commit.
https://cgit.freebsd.org/ports/commit/?id=b23b14c3bfc0d930f7757226b06a88008e95909c

Maybe #OpenBSD would have its own workflow, though.

Looks like not only backups but also my obsession^Wpassion to write detailed entries to my "selfhosting journal" pays back. Any change, I made in my main home server, has a date and a detailed description of changes made. Also, the process of #NetBSD installation and service installation is documented too, alongside with documented list of running services, opened ports, cronjobs, etc.

At one bad day, my main server started to hangup at near 18:00 and at nea 08:00. There weren't any cron (or any another) jobs at this time. In the logs and monitoring the problems with mosquitto (MQTT server) were visible — somehow it eats at near 100% of CPU, then monit restart it, then things become working, then (after some time) the server hangs completely. Investigation showed that write to my second ZFS disk (where the PostgreSQL DB lives) were extremely slowed, so ZFS panicked, crashed and crashes the kernel

[ 204836.661198] wd0d: device timeout writing fsbn 123148477 of 123148477-123148478 (wd0 bn 123148477; cn 122171 tn 1 sn 46), xfer 38, retry 1
[ 204863.837664] wd0: soft error (corrected) xfer 38
[ 206810.672323] wd0: autoconfiguration error: wd_flushcache: status=0x5128<TIMEOU>
[ 212327.420695] SLOW IO: zio timestamp 211326864412007ns, delta 1000556283358ns, last io 211280726737075ns
[ 212327.420695] panic: I/O to pool 'zfs' appears to be hung on vdev guid 1299234741086050345 at '/dev/wd0'.
[ 212327.420695] cpu0: Begin traceback...
[ 212327.420695] vpanic() at netbsd:vpanic+0x183
[ 212327.420695] panic() at netbsd:panic+0x3c
[ 212327.420695] vdev_deadman() at zfs:vdev_deadman+0x15e
[ 212327.420695] vdev_deadman() at zfs:vdev_deadman+0x31
[ 212327.420695] spa_deadman_wq() at zfs:spa_deadman_wq+0xe0
[ 212327.430704] workqueue_worker() at netbsd:workqueue_worker+0xef
[ 212327.430704] cpu0: End traceback...

At the same time, I hear a strange metal noises from server at near 08:00 too, so the destiny of second drive was specified.

The server restoration will take some time, but since anything were written in the log file, I'm able just to replay some actions and get all systems up as soon as possible

#selfhosting #HomeServer

Alt...

Emacs buffer with journal entries (in OrgMode) related to the administrative actions in the server.

Alt...

Emacs buffer with description of NetBSD installation process on the main server and with lists of TODO items, services, opened ports, etc.

Alt...

EGA colored photo of a 2.5 inches HDD

@darth My main laptop, where I doing almost all computing now, running #FreeBSD for (checks notes) 6 years.

For homelab server(s) I'm using #NetBSD because it runs everywhere

For *BSD fans, I wish to understand something that truly bothers me.

You are a fan of one or more BSD os. Is that BSD (doesn't matter which one) your daily driver, your primary OS on your main computer?

#BSD #FreeBSD #OpenBSD #NetBSD

The BSDCan 2026 schedule has been published, https://www.bsdcan.org/2026/timetable/timetable-all.html

You can register for the conference, which runs June 17 - 20, 2026 at https://www.bsdcan.org/2026/registration.html @bsdcan #bsdcan #ottawa #freebsd #netbsd #openbsd #development #sysadmin #devops #libresoftware #freesoftware

Do you want to come to Brussels, mingle with BSD people, perhaps do a talk, a tutorial or a BOF session?

The Call for papers https://2026.eurobsdcon.org/cfp/ is open until June 20th, for the conference in Brussels September 9-13, 2026.

We also offer pre-submission guidance/mentoring, as described in the CFP document.

Wonder what BSD and the conferences are about? See https://nxdomain.no/~peter/what_is_bsd_come_to_a_conference_to_find_out.html

@EuroBSDCon #freebsd #netbsd #openbsd #freesoftware #libresoftware #brussels #bruxelles

The BSDCan 2026 schedule has been posted. 30 regular talks, one set of lightning talks, and one Audio BoF: https://www.bsdcan.org/2026/timetable/timetable-all.html

Both FreeBSD and NetBSD will be holding two day Dev Summits across the hall from each other in DMS.
https://wiki.freebsd.org/DevSummit/202606
https://www.netbsd.org/gallery/events.html#bsdcan2026

Just like last year, the reception on Saturday night is free if you register early. This year you must register before May 1, 2026: https://www.bsdcan.org/2026/registration.html
#bsdcan @bsdcan #freebsd #openbsd #netbsd #conference #ottawa

Third system with #NetBSD 11.0 RC3, a little pi slice.

Alt...

neofetch NetBSD 11.0 RC3 output; NetBSD burgee in dark on light blue. text: OS: NetBSD 11.0_RC3 evbarm Uptime: 8 hours, 12 mins Packages: 23 (pkg_info) Shell: sh Terminal: /dev/pts/0 CPU: raspberrypi,3-model-a-plus (4) Memory: 319MiB / 430MiB

Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟲/𝟬𝟰/𝟭𝟯 (Valuable News - 2026/04/13) available.

https://vermaden.wordpress.com/2026/04/13/valuable-news-2026-04-13/

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/04/13) available.

https://vermaden.wordpress.com/2026/04/13/valuable-news-2026-04-13/

Past releases: https://vermaden.wordpress.com/news/

#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday

@astraleureka @atax1a If Linux is not a hard requirement, #NetBSD has support to this day:
https://wiki.netbsd.org/ports/mac68k/

This weekend is the perfect time to get your #eurobsdcon submissions done!

The Call for papers https://2026.eurobsdcon.org/cfp/ is open until June 20th, for the conference in Brussels September 9-13, 2026.

We also offer pre-submission guidance/mentoring, see towards the end of the CFP document.

Wonder what BSD and the conferences are about? See https://nxdomain.no/~peter/what_is_bsd_come_to_a_conference_to_find_out.html

@EuroBSDCon #freebsd #netbsd #openbsd #freesoftware #libresoftware #brussels #bruxelles #development #sysadmin #hacking #networking

@jschauma We get dh@ emails monthly with gnats stats about the #NetBSD bugs. The oldest one is always listed, either it's a doozy or so obscure no-one cares

In the world of BSD conferendes, BSDCan 2026 https://bsdcan.org is next, on June 17-20 in Ottawa, Canada.

Read more about the BSD conferences in "What is BSD? Come to a conference to find out!" https://nxdomain.no/~peter/what_is_bsd_come_to_a_conference_to_find_out.html #netbsd #openbsd #freebsd #conference #freesoftware #libresoftware #development #networking #sysadmin

Well, well, well... it's Friday, so let's have a little bit of fun, shall we?

#NetBSD 11, take two!

$ qemu-img create -f qcow2 ~/Documents/VM/netbsd11.img 20G

$ sudo qemu-system-x86_64 -accel kvm -m 2G -cpu host -smp 2 -boot d -hda /home/gil/Documents/VM/netbsd11.img -name NetBSD11 -cdrom Downloads/ISO/NetBSD/NetBSD-11.0_RC3-amd64-dvd.iso -display curses -net user,hostfwd=tcp::22222-:22 -net nic

Second system for #NetBSD 11.0 RC3, an Atom PC, upgraded with the i386 CD image.
TIL how to skip sets that are not in the distribution sets. Apparently the 700 MB ISO file *just* fits, by leaving out manhtml and tests. I guess I can back-fill them?

> 710453248 Apr 4 12:22 NetBSD-11.0_RC3-i386.iso

Alt...

neofetch core dump on a fresh 11.0 RC3 NetBSD upgrade to an i386 minion.

First system upgraded to #NetBSD 11.0 RC3. Not the last.

Alt...

$ time neofetch jim@ ---- OS: NetBSD 11.0_RC3 amd64 Uptime: 5 mins Packages: 453 (pkg_info) Shell: sh Terminal: /dev/pts/2 CPU: Intel 686-class (2) Memory: 723MiB / 3987MiB real 0m0.497s user 0m0.176s sys 0m0.145s

Here are some things that one can add to the analysis of the MacOS TCP timeout clock freeze bug.

The code for calculate_tcp_clock() in XNU was changed in May 2025. Older versions of this function (e.g. in xnu-11417) worked quite differently and wouldn't have stopped ticking the clock at 32-bit unsigned integer wraparound.

None of #NetBSD, #FreeBSD, nor #OpenBSD share this exact way of doing TCP timeout processing with #XNU.

FreeBSD does not have a tcp_now and works off the global 32-bit ticks variable. OpenBSD effectively works off the kernel's system clock, too, but with a randomized offset, and does 64-bit unsigned modular arithmetic. NetBSD uses a distinct 32-bit unsigned tcp_now counter that it simply increments by 1 at regular intervals, and does modular arithmetic subtraction.

https://photon.codes/blog/we-found-a-ticking-time-bomb-in-macos-tcp-networking

#TCP #MacOS

What is considered state of the art for Endpoint management, and specifically security controls (EDR, SIEM, RMM, etc.) for BSD? There usually exists clients and agents for Linux in this space. There is an abandoned(?) Wazuh port for FreeBSD.

Essentially how does one manage and monitor the security of 100’s or 1,000’s of BSD endpoints like a Windows or Linux or even Mac environment would?

#askfedi #freebsd #openbsd #netbsd #infosec

Have you been wondering about ZFS AnyRAID? Allan Jude will be giving a talk about Flexible Disk Layout @ BSDCan

If you register before May 1, the closing reception is free!

Register at https://www.bsdcan.org/2026/registration.html

#bsdcan #conference #bsd #unix #development #freebsd #netbsd #openbsd
#sysadmin #devops

Can anyone recommend a decent 2 port PCI network card?

Not PCIe or PCI-X!!!!

Bonus if its compatible with #NetBSD and has 1Gb ports

#Networking #oldcomputing

The new way of selling 'AI' seems to be to push it as a bugfinder. The latest example being waved around as of yesterday includes, as one of its non-embargoed examples, what is patched by this #OpenBSD patch.

https://ftp.openbsd.org/pub/OpenBSD/patches/7.8/common/025_sack.patch.sig

The problematic thing is that this sort of bugfixing hasn't changed the commentary in the code, which stated that p points to the last linked list entry at the point of the added null check and can never be null. But it actually can be, if there was a sole linked list entry that ended up being fully encompassed and thus deleted.

So this kind of 'AI' use is going to give us a lot more comments-do-not-match-code maintenance headaches down the road.

(Both #NetBSD and #FreeBSD factor this out into a separate tcp_sack.c and do the linked list handling slightly differently without a 'previous' pointer.)

#AI

https://red.anthropic.com/2026/mythos-preview/

I wonder why they didn't check #NetBSD ! 🤔
#FreeBSD #OpenBSD #runbsd