The NetBSD project is pleased to announce the eighteenth major release of the NetBSD operating system NetBSD 10.0!
See the release announcement for details.
The netbsd-10 release branch is more than a year old now, so it is high time the 10.0 release makes it to the front stage. This matches the long time it took for the development branch to get ready for branching, a lot of development went into this new release.
This also caused the release announcement to be one of the longest we ever did.
If you want to try NetBSD 10.0 please check the installation notes for your architecture and download the preferred install image from the CDN or if you are using an ARM based device from the netbsd-10 builds from the bootable ARM images page.
If you have any issues with installation or run into issues with the system during use, please contact us on one of the mailing lists or file a problem report.
Are any of our community NetBSD users? What are the brickbats or bouquets for the OS?
(Score: 5, Interesting) by tangomargarine on Tuesday April 02 2024, @02:22PM (1 child)
And they called them all "NetBSD 10.0"? Sounds confusing.
Comma, please.
"Is that really true?" "I just spent the last hour telling you to think for yourself! Didn't you hear anything I said?"
(Score: 2) by Gaaark on Tuesday April 02 2024, @04:32PM
Modded you informative, 'cos Off-topic seemed a bit .... off-topic? :/
--- Please remind me if I haven't been civil to you: I'm channeling MDC. ---Gaaark 2.0 ---
(Score: 3, Insightful) by epitaxial on Tuesday April 02 2024, @03:05PM (1 child)
Porting an OS to many architectures is no easy task. From Alpha to VAX, NetBSD has you covered.
(Score: 1, Funny) by Anonymous Coward on Tuesday April 02 2024, @06:33PM
Yep, if you're using NetBSD you'll be kinda hosed if you're running anything by Xerox, a Yamaha workstation or anything built for zOS.
(Score: 4, Informative) by Mojibake Tengu on Tuesday April 02 2024, @05:50PM
Sure.
The smallest handheld I had NetBSD on was HP Jornada. Good old wardriving times...
++ NetBSD is the thinnest and fastest network kernel out there. For building headless or pocket network appliances, no rival in that.
-- Autoloaded Nouveau driver panics kernel often, if not immediately. That one is overall shit on all other kernels too so no big deal. Absolutely not acceptable on a pure platform which otherwise exhibits uptime in years.
If in true need of graphics on a BSD/NVIDIA contraption, use FreeBSD and NVIDIA's official FreeBSD driver instead. Yes, dear ATI/AMD, NVIDIA supports FreeBSD directly, for ages.
Rust programming language offends both my Intelligence and my Spirit.
(Score: 3, Interesting) by recourse on Wednesday April 03 2024, @02:31AM (2 children)
NetBSD is my first nix love. I used it to set up my first publically accessible web server. It was a joy to work with and if I could I would switch to it for work. Its configuration system was simple and easy to use for a teen in the late 90s and I just really loved using it. NetBSD and the other BSDs will always have a place in my technical heart.
(Score: 2) by Cyrix6x86 on Wednesday April 03 2024, @06:45PM (1 child)
NetBSD is the only BSD that I have never used.
I think I followed the traditional FreeBSD (1998) -> DragonFly BSD (2004?) -> OpenBSD desktop (2010) journey.
I've used pkgsrc on OpenSolaris I believe. But never actually used NetBSD.
Are there any scenarios where it makes sense to use NetBSD over one of the other BSD systems?
(Score: 1, Informative) by Anonymous Coward on Thursday April 04 2024, @06:43AM
When hardware or drivers make it difficult to run the others. Installing OpenBSD on ARM devices is often a hassle, for example, while NetBSD can usually be installed quite simply on nearly anything. If you want to use features like bluetooth, it can make sense on laptops over OpenBSD. It also has ZFS support and a linux compatibility layer like FreeBSD, but doesn't have jails. It does have it's own hypervisor nvmm, but I haven't used enough to know how it compares to bhyve or OpenBSD's vmm. In many ways it feels like the best of both Free- and Open- BSD, but I find myself missing rcctl and the nicely curated OpenBSD base system, so I only use it where it's the path of least of resistance.
(Score: 1) by namefags_are_jerks on Thursday April 04 2024, @04:21AM
My primary home computer has been NetBSD since May 1994 (I have untouched files from its installation still on it..) - It's definitely a Ship of Theseus/Grandfathers Axe for the hardware, but since I switched from the formal releases (0.8, 0.9, 1.0) to the NetBSD-current in 1997, I've had the 'same' operating system ever since -- updating it from source continuously for 27 years...
NetBSD is /still/ BSD - unlike just about everything else. It still admins like a early 1990s BSD system that Nemeth/Snyder/Seebass wrote about, using the same utilities as back then-- no proprietary utilities exclusive to a platform, and where just about everything is managed with /bin/sh scripts (init...pkgsrc...) pkg_comp used for building packages from source rely on /bin/sh and chroot() like it was 1990 .. No fads like Jails or Zones or Wayland or Java or Python or Rust. LLVM was brought into the base for building just the AMD firmware on x86/amd64, but otherwise GCC is the primary compiler no matter what the trendoids want to believe is 'better', thanks to the multiple architectures NetBSD supports.
I always make a mess of FreeBSD and OpenBSD systems I look after, as I keep admin'ing them like a NBSD box, rather than with the tools you're 'supposed' to use..
There also hasn't the major dramas from the SJW culture war a few years ago which hacked up FreeBSD and Linux- someone freaked out over Hilter quotes in fortune, and a clique of superheroes erasing 'blacklist' was about it. Self-professed leadership hoping to divide the dev community and keep the 'good' part ain't a good strategy when the community isn't that big.