The NetBSD Foundation will participate to Google Summer of Code 2026!

Google Summer of Code is a great opportunity to contribute to NetBSD and/or pkgsrc!

To learn more please give a look to NetBSD Blog post: https://blog.NetBSD.org/tnf/entry/gsoc2026_tnf

#netbsd #pkgsrc

I think 2026 is the right time to bring back BSDmag

https://archive.org/details/BSD_Magazine_11_2014/page/16/mode/1up

#DragonflyBSD #FreeBSD #OpenBSD #NetBSD #MidnightBSD #RunBSD

What's the most popular wiki software for BSDs? What do y'all use? #freebsd #openbsd #netbsd

(Edit to add: for a small team of mostly non-technical editors.)

Oh, nice, #NetBSD 11 on the horizon!

https://netbsd.org/releases/formal-11/NetBSD-11.0.html

A little late for me to announce, but RC1 at this stage. I wonder if I should install this instead of the stable release?

#RunBSD

#NetBSD Fun Facts
#Linux #unix #runbsd

@FreeBSDFoundation I think that was in 1998 because #NetBSD lacked drivers for a network interface that I had to use. They fixed that shortly afterwards.

The moebius #Ants continue to crawl on the Pi 0W, 2 weeks later. #NetBSD

Alt...

Mesh onscreen with 3d ants, escher like.

#TIL that there is a command "units" for units conversion exists. In the #BSD world it was appeared in the #NetBSD then ported to the #FreeBSD 2.2.0, according to the "History" section in the manpage.

https://jlsksr.de/notes/24100102/

At least, for now I known that 19 liters equals to 30.89 vodka bottles, or 154.47 charkas (чарок, от «чарка»), or 308.94 shkalikoff (шкаликов, от «шкалик»), or 1.55 vёder (вёдер, от «ведро»).

Conversion rules lives in the simple text file in the /usr/share/misc/definitions.units and the own rules could be written in some text file in the same manner.

@rf

Alt...

Screenshot of Xterm window with some examples of units conversion with "units" command. Commands issued: "units -t '19 liters' vodkabottle", "units -t '19 liters' charka", "units -t '19 liters' shkalik", "units -t '19 liters' vedro". Their output already described in the main toot.

Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟲/𝟬𝟮/𝟮𝟯 (Valuable News - 2026/02/23) available.

https://vermaden.wordpress.com/2026/02/23/valuable-news-2026-02-23/

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

https://vermaden.wordpress.com/2026/02/23/valuable-news-2026-02-23/

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

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

Mid February #NetBSD #pkgsrc package counts for 2025Q4:

10.0: earmv4 12805 (didn’t have it listed before) 10.0: m68k 9622 (+1394) 10.0: powerpc 20711 (+2833) 10.0: sparc64 16866 (+1635) 10.0: vax 7495 (+748)

11.0: aarch64eb 24042 (+4001) 11.0: earmv4 4362 (+612) 11.0: m68k 8132 (+1271) 11.0: mips64eb 3852 (+363) 11.0: mipsel 440 (+449 - needs a new power supply) 11.0: powerpc 4552 (unchanged - needs space and power) 11.0: riscv64 18616 (+3233) 11.0: sh3el 7809 (+2239) 11.0: vax 5245 (+1879)

@EF Hmm... where exactly? If it's on nanopi r2s (the one in the picture), then #FreeBSD works there, but if it's on OrangePi Zero, then #netbsd runs there, but it can't communicate with the network card, which basically kills the whole idea😉

My old friend, a Raspberry Pi A+, has been running my home heating system for months, just like it did back in 2014.

It has not missed a single moment.
It has sailed through every so called cloud outage.
It kept working flawlessly even when the Internet connection was down, because it simply does not need it.

This is the kind of technology I love.
Of course, it runs NetBSD!

rpicaldaia# uptime
6:23PM up 78 days, 20:16, 4 users, load averages: 0.33, 0.17, 0.13
rpicaldaia# uname -a
NetBSD rpicaldaia 10.1 NetBSD 10.1 (RPI) #0: Mon Dec 16 13:08:11 UTC 2024 mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/evbarm/compile/RPI evbarm

#NetBSD #RunBSD #OwnYourData

@wfk @gmc @freedosproject

IIRC, current #Linux, #FreeBSD and I think #OpenBSD no longer supports 486 systems. But I did see an article that #NetBSD can still be put on a 486. But I lost the link

With that said, if I had that system, I would put some form of DOS on it. Maybe sone day I will find one :)

Happy to see NetBSD is in Google‘s Summer of Code again for 2o26:

https://summerofcode.withgoogle.com/programs/2026/organizations/the-netbsd-foundation

#netbsd #google #summerofcode #gsoc

If you are in tech or interested and have not yet been to a regional #BSD conference, I would recommend you consider going to one.

A short description of the three major ones can be found in my recent piece "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 (G-tracked https://bsdly.blogspot.com/2025/11/what-is-bsd-come-to-conference-to-find.html). Fun fact: I'll be at all three this year

#openbsd #netbsd #freebsd #asiabsdcon #bsdcan #eurobsdcon @bsdcan @EuroBSDCon

Now: Martin Husemann explaining about the #NetBSD Wi-Fi driver renewal #EuroBSDCon

@philpem See if you can get #NetBSD/acorn26 running on it (an old release as port has been removed). My A5000 seems to be dead and I lost my A540 with 16MB.

While writing my article, it became clear to me how much responsibility — and especially experience — is required to touch areas like UVM or NPF inside NetBSD.

I’ve learned a lot over the past weeks. But I’m also honest enough to say: I don’t yet have the depth of experience needed to modify those subsystems responsibly.

So I made a conscious decision.

I’ve created a new experimental branch for secmodel_jail / jailctl / jailmgr that is strictly additive:

- No changes to existing kernel code paths

- No UVM hooks

- No NPF integration

- No hidden coupling between subsystems

It adds new code only.

The reason is simple: even without deep UVM or NPF integration, the security model already delivers significant practical value for me. And in this reduced, explicit form, the attack surface is clear and the audit scope sharply defined.

This feels like the right first alpha candidate: understandable, bounded, and reversible.

https://github.com/MatthiasPetermann/netbsd-src/tree/feature/jails-v1-ga

#netbsd

Just added another sensor to #sysinspect — "procnotify".

In this very short demo: as long as a new process is "bash" (use "zsh", LOL), #sysinspect SIGKILLs it.

Key points:
1. procnotify detects a new process
2. a model is getting triggered (in this case just a process killer)

Currently:
Native: #linux, #netbsd
Others: external fallback path.

@kaveman Thank you so much for mentioning my little experiment with bringing Jails to NetBSD here - I really appreciate it.

In the meantime I’ve brought it to a somewhat usable state (at least in its core) and experimented with some interesting - though highly experimental - integration paths with UVM and NPF.

I’m currently thinking about what the best next step would be. One idea is a stripped-down version that complements the kernel code - essentially just secmodel_jail+kauth+jailctl+jailmgr, but without UVM and without NPF integration - possibly as a pkgsrc package?

The current experimental state is described here:
https://www.petermann-digital.de/blog/netbsd-secmodel_jail-update/

(Sorry - at the moment it’s available in German only.)

#netbsd

Alt...

A visualization of a atom with the core (secmodel_jail) and orbits of jailctl and jailmgr.

@osnews

Well, learn something new every day :)

I just tried this on #NetBSD and it worked as described. Since #slackware now has nvi, it will be interesting for people there too.

#unix