@armando @stuartl OK, the problem you will have with older versions of Receiver (as it was) is that they won't know new enough TLS, etc. to be able to speak to anything modern.

I never got 11.6 to work with modern--ish NetScaler even when forcing on SSL v2 and SHA1 cert signatures.

However, I now have a graphical #NetBSD environment to play with thanks to @lproven and his query about CDE to the NetBSD mailing lists, so I'll see how well modern Linux emulation works.

Reject it

#NetBSD #antiai #noai #runbsd

@nivex If you have a few hours to spare, this makes for an interesting read - https://www.theos.com/deraadt/coremail.html

"This mail archive is the complete (as far as I know) communication between myself and the NetBSD core between December 15 (when they removed all my NetBSD access) and the day OpenBSD was formed. It
actually goes a little further beyond that time, and includes mail from a few other people involved in the negotiations."

#openbsd #netbsd

I've been delving into the history of the BSDs lately and found a very interesting tidbit. Theo de Raadt, who most people know today from OpenBSD, was one of the founding members of NetBSD. He was asked to resign from that project for behavior that is distressingly common today on LKML: https://mail-index.netbsd.org/netbsd-users/1994/12/23/0000.html

So basically they took "fire brilliant assholes" to heart before it was really a thing. Between this and their swiftness to denounce "AI" (in 2024 when it was still early days of the current hype), they have risen much in my estimation.

#BSD #NetBSD

why is #NetBSD PUFFS /dev/putter and not /dev/puffs ? #lang_en

@armando How new do you need? Even the ancient one in pkgsrc speaks to CVAD 2507 CU1 just fine. Some of us have made and sold #NetBSD products with the ICA client in...

https://docs.google.com/presentation/d/1lrtnPlm6LA_ae2TXjqBxhaHj75VzQJRzQ-V3SOsdxqQ/edit?usp=sharing

At least I will be able to play with my #NetBSD Lenovo IdeaPad Netbook during those long and boring Teams meetings! 😋

Has anyone tried running CDE on NetBSD 11? Either it doesn't work or I'm doing something wrong, but I'm unsure which it is.

Maybe it's not the best desktop, but I liked it when I used it on Solaris at an old job. I would like to try it again if it's possible, but I lack the knowledge beyond calling it in ~/.xsession.

#BSD #NetBSD #Unix

Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟲/𝟬𝟴/𝟭𝟳 (Valuable News - 2026/08/17) available.

https://vermaden.wordpress.com/2026/08/17/valuable-news-2026-08-17/

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

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

With recent commits, hdaudio(4) of #NetBSD/amd64-current becomes stable.

Whew, I successfully updated my kitchen-server from NetBSD 10.1 to NetBSD 11.0 via the sysupgrade.

Now, I'm thinking about transforming this system, having a lot of binary packages from remote repository — to the system where each package is built locally via pkgsrc.

Since it is just a server, I don't see any problems with > 24h compile time of something like Rust of Librewolf
BTW, I didn't find an easy way (just launch one script and go to sleep) to convert the system from using remote built packages to the locally built packages
So, looks like I'll use some one-liner to get list of packages where build host != my server hostname. And then rebuild and update these packages with the help of pkgsrc.

#NetBSD #pkgsrc

Hmm... #pkgsrc/lang/nodejs24 under #NetBSD/i386 has another problem...

It’s time to start on my work again, currently in progress… #FreeBSD #NetBSD #OpenBSD

@argv_minus_one @giacomo @lispi314 @niconiconi With #NetBSD rump, it's the SAME implementation, just running in userspace. The same likely isn't true for a FUSE reimplementation, so harder to compare. On NetBSD, just add -o rump to your mount command

Would it be wrong to build a Cedar Mill #Pentium4 computer just to try #NetBSD/amd64 on it?

@stefano @dch

This being said, I'd love to compile it under #Slackware and #NetBSD

If I remember corectly, #NetBSD allows running its filesystem drivers in userspace for easier debugging.
(also, obviously, #GNU/#Hurd does that).

As for performance, I keep reading this about microkernel penality, but I can't find any actual measure. How slow is "slow" in this context? I'd bet a coffee the tradeoff might be acceptable in several usage contexts.

@lispi314@udongein.xyz @niconiconi@mk.absturztau.be

Also obligatory desktop screenshot.

[1] https://shop.rabbitholecomputing.com/products/sata-pci-hard-card

#NetBSD #486 #NSFW #RetroComputing

Alt...

Screenshot of NetBSD X desktop using the default CTWM window manager. Hot-Babe (lightly clad; the CPU is running hot) in the lower-left corner, next to conky system monitor. Lower right corner has small terminal windows tailing the snac log and showing 'pfetch' output, respectively; both next to the virtual-desktop switcher in CTWM. Two main terminal windows: One running mrxvt showing 'lspci' output, another running irssi. Plain blue background.

#Retrocomputing #486

Alt...

pfetch output showing the NetBSD flag, OS release and hardware (AMD 486-class, 127MB RAM)

@Statler_waldorf @Gammitin Lovely. In about ~2003/2005 I used one of those, with a UPA Creator3D video card and 20" Sun Trinitron CRT, as my home workstation. Running #NetBSD -current rather than Solaris though.

Toot from #pkgsrc/www/firefox-154.0b10 under #NetBSD/amd64 11.99.7.

And this will not support 32-bit architectures of #NetBSD. I will fix this.

I was thinking today about my diversity of hardware and systems I maintain.

Sure, I've got a few standard VPS cloud systems (vultr, hetzner) running #FreeBSD. These do the heavy lifting for my web, DNS and other services.

My least standard setup is an RPI4 installed in an RV. The electronics are 100% solar powered and connected to the internet via Starlink. Starlink was also converted to 12v and the router replaced with an openWrt powered system.

What's your most unique setup?

#NetBSD #Linux

stefano@MBPProM1 ~/s/smolBSD (main)> ./startnb.sh -i images/rescue-evbarm-aarch64.img

➡️ using QEMU version 11.1.0

➡️ using kernel kernels/netbsd-SMOL-aarch64.img

➡️ using console: com

➡️ using disk image images/rescue-evbarm-aarch64.img

🔚 ^D to stop the vm, ^A-X to kill it

qemu-system-aarch64: warning: driftfix 'slew' is not available with this machine

boot NetBSD/aarch64

initarm

[ 1.0000000] NetBSD/evbarm (fdt) booting ...

main

[ 1.0000000] smolBSD 11.0_STABLE (MICROVM) Notice: this software is protected by copyright

[ 1.0000000] Detecting hardware...[ 1.0000030] WARNING: system needs entropy for security; see entropy(7)

[ 1.0000030] done.

[ 1.0080588] kernel boot time: 121ms

Created tmpfs /dev (1359872 byte, 2624 inodes)

Impressive!

#smolBSD #NetBSD #RunBSD

If you're not aware of it, you should have a look here:
https://nycdn.netbsd.org/pub/arm/

Ready to go NetBSD images for SBC!

#NetBSD #RunBSD

Hello from the other side!

Yes, it's true. This instance is now running from the Orange PI PC (NetBSD, armv7). It's currently using the SD Card. The performance is...you judge! And it's not set to low_power mode!

#littleOne #littleFedi #SBC #NetBSD

Alt...

The Orange PI PC currently running this instance, dust included

@stefano
But this won't be the only method, I hope? :)
#netbsd isn't on friendly terms with ethernet on my Orange Pi Zeros :(

smolBSD by @imil could be a nice docker alternative for #littleFedi
I'll perform more tests and will consider to make it an "official deployment method".

#NetBSD #smolBSD

@tsutsuii #NetBSD

I found this is misleading, but I read this protest a lot around, and while I understand it, I think it is a misunderstanding.
Linux never got has goal to make run forever all kind of hardware. It is a misconception because the hardware support is longer and many used it for old machines, but this is coincidental, not a stated goal.

If you need a OS that runs "forever" on everything, that's NetBSD: running everywhere is their goal.

https://invidious.tiekoetter.com/watch?v=8vDSSxaQ7ZU

#foss #linux #netbsd

Perhaps what is really needed around is more awareness to alternatives to Linux too, not just for Windows/MacOsX.

A lot of these drivers that are getting removed from Linux, along the 32bit, are niches that can fall into retrocomputing at this point.
If you fall in it, I could suggest you to pick NetBSD, that has the 32 bit support along many things.
You could even run it on an Amiga68k (the CLASSIC hardware!) even if is a low priority port.

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

#foss #linux #netbsd

@claudiom one more reason to use #NetBSD 🚩

The plan is to run a littleFedi instance, once the dust settles.

1) First time running NetBSD on anything, and I only started using *BSD a year ago. Do I need to compile go from source?

2) My ISP needs to provide me with a modem that can run in bridge mode with a static IP. It seems they can only do one, or the other, but not both. Using LTE modem as backup.

3) littleFedi is not yet available (not complaining!)

#NetBSD #littleFedi