Welcome to Google Summer of Code 2025 contributors https://lobste.rs/s/cvabc7 #netbsd
https://blog.netbsd.org/tnf/entry/gsoc2025_welcome_contributors

Congratulations to the @Google #SummerOfCode students who will work on Enhancing Support for NAT64 Protocol Translation, Asynchronous I/O Framework and Using bubblewrap to add sandboxing for @netbsd this summer.

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

#NetBSD #Google #SummerOfCode #gsoc

@netbsd Google Summer of Code 2025 projects announced!:

- Enhancing Support for NAT64 Protocol Translation in NetBSD - Dennis O.I
- Asynchronous I/O Framework - Ethan Miller
- Using bubblewrap to add sandboxing to NetBSD - Vasyl Lanko

To learn more please give a look to the blog post https://blog.netbsd.org/tnf/entry/gsoc2025_welcome_contributors

Welcome Dennis, Ethan and Vasyl!

#netbsd

What's the general opinion on doing scheduled zfs scrubs? Likely to be more useful on the older #zfs that #NetBSD uses?

Snapshots are taken daily and periodically cleaned up. On a system used for backing up files, does it perform a useful integrity test?

The latest version of Pale Moon on a 550MHz NetBSD/sparc64 machine. The last portable web browser capable of opening YouTube - slowly, but stable.

#NetBSD #sparc

Alt...

A screenshot of a 550MHz NetBSD/sparc64 desktop running ctwm running Pale Moon (here titled New Moon) open to the NetBSD page on English Wikipedia. It is using 516M/2048 memory.

One thing that has come from the reading done so far is that the slogan is wrong.

#NetBSD does not work on the Raspberry Pi 5; only up to the Raspberry Pi 4.

https://wiki.netbsd.org/ports/evbarm/raspberry_pi/

But a cheap second-hand #RaspberryPi 4 might be an option. No RTC. But running sntpclock I hope would not be a problem any more than it is on my other machines.

Of course, one of the unknowns here is what of the tools that I have, that build and run on FreeBSD, will build and run on NetBSD. This is one of the reasons for wanting a NetBSD machine. I don't even know whether I can build and run publicfile.

@wolf480pl So yeah, I think that everything has compromises to some extent.

• I'm shure #OpenBSD could even up their #security if they were willing to break #POSIX and #compatibility in general for their distro, but that'll only introduce more headaches and pain along the way.

I chose #Linux as basis for @OS1337 because it solves the #driver problem for me and I know it. I'm just complete shit with #NetBSD which may arguably be the better option targeting low-end systems, but that'll again result in more pain and frustration getting other #apps ported over when I can't just say: "Target linux-#i486 and statically compile in all your dependencies" to any 3rd party as starting point.

@NostalgicKitsune damn...

And I guess there is no #NetBSD #LiveDVD / #BootCD you can plop in on a #BlueBomb'd #WiiMini?

• Or am I too optimistic?

Sorry, I'm too used to #Linux on #Xbox360…

I'm considering running a #NetBSD machine. As physically small and low-power as possible whilst still having Ethernet, USB, and HDMI. The plan is to occasionally compile stuff on it but mainly also stick it in a corner and have it be a minor HTTP/FTP/GOPHER server.

I know that the slogan of long-standing is "Of course it runs NetBSD.", so I know what I'll be told by reflex if I ask whether NetBSD runs on Raspberry Pi-based stuff. (-:

I'm not sure whether I'm better or worse off, power wise, getting a cheap mini-PC instead. They seem over-specced, and fan noise is a problem. Plus, I don't need multiple HDMI ports. I'll barely need one. On the other hand, installation will be less complex and there'll be EFI ab initio.

I have some reading to do.

How to use Post-Quantum Cryptography on NetBSD using Open Quantum Safe - Blog post by Jan Schaumann @jschauma #Cryptography #PQC #NetBSD https://www.netmeister.org/blog/netbsd-pqc.html

Yesterday, I told you about incus - today I tell you how you can easily run #FreeBSD, #OpenBSD & #NetBSD with #incus!

#RUNBSD! #opensource #homelab #virtualization #proxmox

https://gyptazy.com/run-freebsd-openbsd-netbsd-vms-in-incus/

Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟱/𝟬𝟱/𝟬𝟱 (Valuable News - 2025/05/05) available.

https://vermaden.wordpress.com/2025/05/05/valuable-news-2025-05-05/

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

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

Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟱/𝟬𝟱/𝟬𝟱 (Valuable News - 2025/05/05) available.

https://vermaden.wordpress.com/2025/05/05/valuable-news-2025-05-05/

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

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

Great article from @gyptazy :

Run FreeBSD, OpenBSD & NetBSD VMs in Incus

https://gyptazy.com/run-freebsd-openbsd-netbsd-vms-in-incus/?utm_source=discoverbsd

#FreeBSD #NetBSD #OpenBSD #Incus #VM #Virtualization

I've been reading an interesting article by Liguo Yu et. al., "Maintainability of the kernels of open-source operating systems: A comparison of Linux with FreeBSD, NetBSD, and OpenBSD" (DOI: 10.1016/j.jss.2005.08.014). Keep in mind, the article is from 2005 (published in 2006), so it would be interesting to know how things have changed since then. We are talking here about #Linux 2,4,20, #FreeBSD 5.1, #NetBSD 1.6 and #OpenBSD 3.3.
The article basically explores maintainability of said OSes judging mainly by usage of global variables.
Here's some interesting takeouts.
"Unsafe definition" is in their terms a usage of global variables between kernel modules and non-kernel modules.

Alt...

Two graphs showing number of global variables and unsafe definitions in Linux and three BSDs. Linux has significantly more of both.

Better the *daemon* you know than the *daemon* you don't

#runbsd #netbsd #freebsd #openbsd

#FreeBSD - I had to use 15-CURRENT as the video card isn't supported. Even in 15-CURRENT, trackpad doesn't seem to be working and the video performance is poor. I'll have to investigate.

#OpenBSD - better video performance, the wifi card is recognised but it seems to have some performance issues (packets lost, etc). Trackpad is not working

#NetBSD - video card is not supported, trackpad isn't working

I'll test the whole system with a Fedora, just to be sure that the hardware is ok (but a small test, yesterday, was successful).

#aceBSD

I recently move my #GoToSocial from #NetBSD to #FreeBSD; to have a look at memory consumption when using sqlite and the wasm thing. And… well, memory usage is about the same.

NetBSD on the left. FreeBSD on the right.

Post-Quantum Cryptography on NetBSD https://lobste.rs/s/j03wkv #netbsd
https://www.netmeister.org/blog/netbsd-pqc.html

@jschauma published a nice little primer on post quantum cryptography on #NetBSD :

https://www.netmeister.org/blog/netbsd-pqc.html

I put together some notes on using post-quantum cryptography on NetBSD using Open Quantum Safe as well as using BoringSSL. It's really simple, but instructions aren't always easy to find, so here you go:

https://www.netmeister.org/blog/netbsd-pqc.html

#NetBSD #pqc

@darrenmoffat #illumos does not yet (https://www.illumos.org/issues/5386) so it doesn't even build. The issues I've heard about from #NetBSD land are problems running inside xterm and reverse characters not working anymore.

I use tmux too, this is just about providing a version of screen for my users who still wish to use it.

Yet to hear anything positive about GNU screen 5.x.

Drops support for #Solaris / #illumos (now has a hard requirement on openpty()), and breaks various use-cases on #NetBSD.

Switching all my builds back over to misc/screen4.

#pkgsrc

Congratulations to #DragonFlyBSD from #NetBSD community for 6.4.1 release!🎉 #RunBSD
https://www.dragonflybsd.org/release64/

@jfparis @stefano A full ./build.sh -D ../dest-evbarm -O ../obj-evbarm -T ../tools -R ../sets -m evbarm -a earmv6hf -x tools distribution sets takes about 4 days and 22 hours at 1 GHz on a microSD card.

The same takes 12.25 minutes on a Ryzen 7900, less time than it takes to run install=/ on the Pi Zero (17.25 minutes) :P

I just had to know!

#NetBSD