Today was a OSes update day . First, I updated the laptop of one of my relatives, which I gave him at near 2021. The OS on the laptop (some kind of Dell Inspiron) wasn't updated since these times, so it was a Linux Mint version 18.2 (and now it is ver. 22.3). But, suddenly for me, minor update from 18.2 to 18.3 and the major update from 18.3 to 19, with the help of this instruction: https://linuxmint-user-guide.readthedocs.io/en/latest/upgrade.html

From my previous experience with Oracle Linux and it's repositories, I thought, that Linux Mint update will fail, because all repositories shut down and update files were removed, because the installation from 2021 is too old. But, all necessary infrastructure is still up and I managed to perform updates

The second update, the update of my main server with NetBSD. It just works: I installed sysupgrade, update the system, merge some configuration in /etc/, update binary packages, update to packages from pkgsrc and that's all. It just works, without any surprises and problems

#NetBSD #LinuxMint

The #eurobsdcon 2026 Call for Papers is still open!

https://2026.eurobsdcon.org/cfp/

Submit by June 20th, come to Brussels September 9-13 and mingle with #BSD people!

We also offer pre-submission guidance/mentoring, see the CFP text.

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

@AFresh1 on #NetBSD :

#sysupgrade auto https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-X/latest/amd64

For packages :

#pkgin update
#pkgin full-upgrade

Edit:

For packages only #pkgin upgrade
as pointed by @jperkin Thanks :)

The system was previously softhacked through other means but I managed to get Wiibrand working in the end, the Homebrew Channel installed and NetBSD started up.

Unfortunately the "UGREEN USB 2.0 Ethernet Adapter" doesn't work in the Wii Menu, despite having the right chipset, and also not in #NetBSD - the axen driver repeatedly prints messages about a wrong buffer. I've ordered a Realtek-based dongle instead.

@cienmilojos

I don't know of any OS that has an iron-clad #NoAI policy.

#NetBSD comes the closest, but they even have a provision for AI being included "with permission," IIRC.

#OpenBSD already has slop in base, via tmux. :/

Boo to #Apple, but hooray for #NetBSD! ​

https://www.osnews.com/story/144845/apple-wants-to-kill-your-time-capsule-but-they-run-netbsd-so-they-cant/

https://www.osnews.com/story/144845/apple-wants-to-kill-your-time-capsule-but-they-run-netbsd-so-they-cant/

#apple #timecapsule #netbsd

Petit hors-série aujourd'hui, sur de la compilation de noyau #NetBSD en CI #Gitlab ! Rendez-vous sur https://www.twitch.tv/ahp_nils

I created a support page (in lieu of a blog) about SR-IOV on XenServer and XCP-ng with various Intel NICs and different operating systems including #FreeBSD, #OpenBSD and #NetBSD

I think the #NetBSD ixv(4) driver needs resyncing to #FreeBSD from whence it came (or get hints from #OpenBSD). I couldn't get it to work on #NetBSD
https://www.precedence.co.uk/wiki/Support-KB-Citrix/XenServer-SRIOV

The #eurobsdcon 2026 Call for Papers is still open!

https://2026.eurobsdcon.org/cfp/

Submit by June 20th, come to Brussels September 9-13 and mingle with #BSD people!

We also offer pre-submission guidance/mentoring, see within.

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

Yes, it's the same with @xcpng as #XenServer. XenCenter and XCP-ng Center don't offer the SR-IOV network as an option for VMs. Luckily, #XenOrchestra gets that right.

While there I tested various #BSD OSes with SR-IOV and Intel i350 NICs:

#NetBSD - NIC is described (as defined in pcidevs), but no driver
#OpenBSD - NIC entirely unknown as not in pcidevs
#FreeBSD - virtual function works straight off as igb0

The #NetBSD and slightly-newer #OpenBSD iavf(8) drivers only support much newer NICs.

Mit #NetBSD wäre das nicht passiert!

https://www.golem.de/news/seit-2017-ausnutzbar-gefaehrliche-root-luecke-im-linux-kernel-entdeckt-2604-208181.html

A little know fact about #NetBSD is that a a machine that can run it is known as a TareBSD and the two together are called a GrossBSD.

#BSD #humor #humour #silly

@rl_dane @anselmschueler

Lemme rephrase that:

I miss the days when distros used the 2.6.x kernel. Maybe someone around here will just call me a cranky old curmudgeon, but things did seem simpler back then.

The opaque undocumented userland sprawl is a problem, with the operative word being "undocumented."

RE: Arch Wiki

Yes, as good as it is it's still not proper HOWTO or understandable, (vetted) documentation. The *one* thing that has me gravitating towards #FreeBSD is documentation is a first class feature. It makes the OS a lot more transparent and understandable. I'm sure that's also the case for #NetBSD and #OpenBSD but I don't use them.

This laptop runs #Ubuntu. While it is a #Debian derivative, it's opaque. While there is more documentation available on Ubuntu's website, it's nowhere near as thorough and empathetic as it needs to be. I shouldn't have to visit another distro's wiki just to research info about a different distro on an OEM laptop. That, to me, is unacceptable.

#netbsd

https://www.osnews.com/story/144845/apple-wants-to-kill-your-time-capsule-but-they-run-netbsd-so-they-cant/

Has anyone tried #NetBSD/aarch64 11 RC3 on the #RaspberryPi Zero 2W?

@drj Not really. I used and consulted on UNIX in the 80's when I worked with Siemens, we called it SINIX. In 2001 after starting teaching, I started with Linux and used vim from early on for sysadm work and gui editors for extensive editing. I converted from Linux to #OpenBSD and #NetBSD to observe KISS including using only vi for all editing. On those two vi is actually nvi. I never really needed the book more than what's in the first 7 chapters. The clone chapters treats every clone systematically alike. But back in 1998, the clones were not really that different.
This book, UNIX POWER TOOLS, and UNIX in a Nutshell, have been with me for about 25 years or more.

I think #NetBSD #pkgsrc foundation can take this initiative : @netbsd

https://www.sovereign.tech/news/join-sovereign-tech-standards-network

@projectanchorage I would look at multiple options.
- If you're strictly stuck with i386 (not even i486) that means #NetBSD is propably the only choice.
- Depending on your goals, you may want to consider #OpenBSD or #386BSD (today's #FreeBSD).
- Not shure if #OpenSolaris / #illumos supported anything beyond #SPARC(v9 / SPARC64) & #amd64.

The question to me is whether or not old #BSD versions emcan even be built with midern toolchains and if choosing them isn't going to bite one in the ass down the line.
- The reason I choose #Linux for @OS1337 is because it's mature toolchain, drivers and hardware support.
- Tho you may rightfully argue that #OS1337 is just taking the #toybox / #musl + linux "distro" #mkroot and basically tries to make something out of it.

The #eurobsdcon 2026 Call for Papers is open through June 20th!

https://2026.eurobsdcon.org/cfp/

Submit by June 20th, come to Brussels September 9-13 and mingle with #BSD people!

We also offer pre-submission guidance/mentoring, see within.

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

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

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

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

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

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

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

And my new homeserver! #NetBSD

Alt...

Picture of a Nintendo Wii

took the week off, celebrate me and my wife's wedding day.

Soon my brave #parisc #hppa machine celebrate 40days uptime.
31 year old machine running 33 year old #NetBSD

@ObsidianUrbex #netbsd candidate 🤔

Only four days left!

Register for BSDCan 2026 https://www.bsdcan.org/2026/ *before May 1st* to get the Saturday reception for free!

Schedule https://www.bsdcan.org/2026/timetable/timetable-all.html

To register https://www.bsdcan.org/2026/registration.html @bsdcan #openbsd #freebsd #netbsd

BSDCan https://www.bsdcan.org/2026/ Talk Saturday 2026-06-20: 14:30 - 15:20 DMS 1130
Bringing memory safety to BSD with CHERI
Brooks Davis
https://www.bsdcan.org/2026/timetable/timetable-Bringing-memory-safety.html
To register https://www.bsdcan.org/2026/registration.html @bsdcan #openbsd #freebsd #netbsd #cheri

BSDCan https://www.bsdcan.org/2026/ Talk Saturday 2026-06-20: 14:30 - 15:20 DMS 1120
Community Event Organizing
Michael Dexter
https://www.bsdcan.org/2026/timetable/timetable-Community-Event-Organizing.html
To register https://www.bsdcan.org/2026/registration.html @bsdcan #openbsd #freebsd #netbsd #events #organizing

BSDCan https://www.bsdcan.org/2026/ Talk Saturday 2026-06-20: 12:30 - 13:00 DMS 1130
Lightning talks
https://www.bsdcan.org/2026/timetable/timetable-Lightning-talks.html
To register https://www.bsdcan.org/2026/registration.html @bsdcan #freebsd #netbsd #openbsd #lightningtalks

BSDCan https://www.bsdcan.org/2026/ Talk Saturday 2026-06-20: 11:00 - 11:50 DMS 1130
NetManager - Building products with NetBSD round 2
Stephen Borrill
https://www.bsdcan.org/2026/timetable/timetable-NetManager---Building.html
To register https://www.bsdcan.org/2026/registration.html @bsdcan #netbsd #netmanager

BSDCan https://www.bsdcan.org/2026/ Talk Friday 2026-06-19: 14:30 - 15:20 DMS 1130
What has (can) the EU Cyber Resilience Act done (do) for you?
Peter Hansteen
https://www.bsdcan.org/2026/timetable/timetable-What-has-can.html
To register https://www.bsdcan.org/2026/registration.html @bsdcan #cra #cyberresilience #freebsd #openbsd #netbsd

BSDCan https://www.bsdcan.org/2026/ BoF Friday 2026-06-19: 12:00 - 13:00 DMS 1130
Audio BoF
Michael Williams
https://www.bsdcan.org/2026/timetable/timetable-Audio-BoF.html
To register https://www.bsdcan.org/2026/registration.html @bsdcan #freebsd #netbsd #openbsd #audio

BSDCan https://www.bsdcan.org/2026/ Talk Friday 2026-06-19: 09:45 - 10:35 DMS 1110
Using Coverity Scan for static code analysis in NetBSD
Emmanuel Nyarko
https://www.bsdcan.org/2026/timetable/timetable-Using-Coverity-Scan.html
To register https://www.bsdcan.org/2026/registration.html @bsdcan #netbsd #coverity #deveopment

BSDCan https://www.bsdcan.org/2026/ Tutorial Thursday 2026-06-18: 09:00 - 12:00 DMS 1120
Shell Scripting Tutorial for Beginners and Sysadmins
Mathias Eggers
https://www.bsdcan.org/2026/timetable/timetable-Shell-Scripting-Tutorial.html
To register https://www.bsdcan.org/2026/registration.html @bsdcan #freebsd #netbsd #openbsd #shell

@tfb @jrsharp
#FreeBSD had proceeded some parts of "abstraction" in this several decades.
For example, separation of buses (like ISA, PCI, USB, ...) and devices connected to any of the buses called "newbus" when it was introduced, GEOM for disks, NETGRAPH for networks. But the appoaches would be different with #NetBSD.
Putting newbus (current implementation) aside, others were for "flexibilities" over "abstraction for compatibilities".

My understanding in difference between aproaches of FreeBSD and of NetBSD would be...
FreeBSD: Make it work and stable, fast for running platform in production first. Then, consider making it portable.

NetBSD: Make it elegant and portable by separating machine independent (MI) parts and machine dependent (MD) parts. Then, making it stable would be easier to achieve. So the next would be performance tunings.

Link to document about newbus (already not "new" bus but "current" bus, though):
https://docs.freebsd.org/en/books/arch-handbook/newbus/