Let's Help Netbsd Cross the Finish Line Before 2025 Ends
Posted2 months agoActive2 months ago
mail-index.netbsd.orgTechstoryHigh profile
supportivepositive
Debate
20/100
NetbsdOpen SourceBsdOperating Systems
Key topics
Netbsd
Open Source
Bsd
Operating Systems
The NetBSD community is rallying around a donation call to help the project stay afloat, with many users expressing gratitude and donating to the cause, while also discussing the project's strengths and weaknesses.
Snapshot generated from the HN discussion
Discussion Activity
Very active discussionFirst comment
53m
Peak period
124
0-6h
Avg / period
20
Comment distribution160 data points
Loading chart...
Based on 160 loaded comments
Key moments
- 01Story posted
Oct 26, 2025 at 8:34 AM EDT
2 months ago
Step 01 - 02First comment
Oct 26, 2025 at 9:27 AM EDT
53m after posting
Step 02 - 03Peak activity
124 comments in 0-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 30, 2025 at 4:33 AM EDT
2 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45711279Type: storyLast synced: 11/20/2025, 8:23:06 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
If Linux never happened, we would still be using big iron UNIXes, each taking whatever they felt like from BSD variants.
Notice how all the new FOSS operating systems for IoT devices none of them use GPL, NutXX, FreeRTOS, Zephyr, Arduino libs, IDF,...
Linux came around at the right time when the Internet was going public and regular people had access to hardware that could run a decent UNIX. People latched onto it because it was free and an interesting project. The free BSDs were just late enough to the party that they missed out on the momentum.
All the proprietary UNIX vendors (other than SCO) relied on expensive proprietary hardware sales. Intel ate their lunch while they were too busy stabbing each other in the back to notice. Linux killed SCO because SCO was, quite frankly, overpriced crap.
None of this had anything to do with the license, other that the fact you could use it for free. It was all about hardware availability, the rise of the Internet, the wave of new IT people who had experienced Linux at home, and the fact that Linux on Intel was good enough to replace those pricy proprietary machines.
Now, you wanna talk Apple, there's where your code "theft" kicks in. But that's a whole different thing.
> 1998: Many major companies such as IBM, Compaq and Oracle announce their support for Linux.
From https://en.wikipedia.org/wiki/History_of_Linux
Without big money from UNIX vendors like those, cutting down their R&D costs, Linux would not have climbed anything.
GPL was the reason why they collaborated instead of being able to assimilate the code as they were doing with BSD, like anything sockets related.
Ironically IBM has recouped its investment, now as Red-Hat owners.
That is where everything on GNU/Linux that is mainly done by Red-Hat like GNOME, Gtk, GCC, Java is being paid for.
The three companies you list are horrible examples. IBM is kind of a UNIX vendor, sort of, but not like Sun or DEC. They sell solutions, and the solutions that use AIX don't overlap with what Linux was capable of in 1998. I'd argue that, given their complete disregard for Tru-64 and pretty much all things DEC, Compaq was never a UNIX vendor - they just inherited a bunch of legacy systems they needed to support. They certainly didn't push for new Tru-64 based systems. Oracle wasn't a UNIX vendor at all and wouldn't become one for quite some time.
BSD sockets are also a bad example. They were the reference implementation, paid for by DARPA. The entire purpose of BSD sockets was to be copied into other operating systems. You'll notice that Linux copied them as well.
IBM and Compaq invested in Linux because they wanted something that ran on their lower-end server hardware and could handle web traffic. Oracle invested in Linux because they wanted to be the backend to all these new websites that were cropping up.
IBM, Oracle, and Compaq didn't give a rat's ass about the operating system code - they wanted the platform. If Linux had never happened and FreeBSD became the new hot thing all the online hackers were talking about, the result would have been exactly the same. They'd have poured money into the projects rather than trying to make their own thing because that's the financially sensible thing to do. The UNIX wars were over, and proprietary software lost.
Meanwhile, the last major UNIX vendor - Sun Microsystems - was giving away its own source code under the CDDL. FreeBSD ended up adopting a lot of it. That's the complete opposite effect from what you're talking about.
Sun got involved in the GNOME project and even deprecated their own CDE desktop in favor of it. Was it because it was GPL? No. It was because they saw that all the new desktop software was coming out of the Linux community, who didn't have access to CDE. Even if GNOME had been BSD licensed they would still have switched to it, because they were still trying to keep the workstation market alive at that point and CDE was quickly becoming irrelevant.
As far as I can see, the only companies interested in taking operating system code were the network appliance vendors and Apple. It only worked for them because they didn't care about compatibility.
You mean any free software license, BSD or otherwise.
Notice how NetBSD isn’t asking for code contributions, but for monetary contributions. The GPL doesn’t cover that either. Observe the current rugpulling fad to relicense free software (both permissive and copyleft) to nonfree protectionist licenses like BUSL and SSPL in order to monetize.
More than fine if you ask me, giving away your work for megacorps and oligarchs to steamroll your business or otherwise society at large isn’t much of a public service in the end
So if some company/product was open source and then used source available license, the backlash would be so much that they go to something like AGPl most of the time
but that happens because people feel betrayed because some might have contributed thinking its foss forever so its a rug pull
I think a good idea could be to have a source available license from the start so that everybody who ever contributes knows this as a fact.
What are your thoughts? What should I or anyone else pick? As a "foss" advocate, I would prefer AGPL but I don't want to get screwed by Big Tech ever with all the loopholes that they can have (like AWS), Honestly I don't know which is why I am asking really.
My personal (non-mainstream) thought on this topic is: work on open source projects that serve a purpose that is very antithetical to the interests of bigtech companies. This way, such companies will be a lot less interested in "using" your project (without contributing back).
I know in the past things like the network stack had been repurposed to other mainstream products.
https://www.nas.nasa.gov/hecc/support/kb/using-software-pack...
But don't you dare switch to a proprietary license or you will be dragged across social media as an evil selfish person. Even if it's only postponing source releases for a couple of years.
FWIW, this is the first time I have ever seen any mention of donations on any major tech WEB site.
Seems fitting that NetBSD's internal mailing lists still use ossified address syntax from a time before DNS.
Having NetBSD around is a net win, and the cost of doing business for them is extremely low for the product they provide.
One of the running jokes is that you can "run it on a toaster" — see https://news.ycombinator.com/item?id=45712368
Years ago I had to get a very old document off of a DOS diskette. So I tried:
* On Linux: accessing the diskette would cause a panic or a reboot or massive read failures.
* FreeBSD: panics all the time
* NetBSD: panics. But then I remembered it had rump. So I said, why not try that. Started up rump, got a few code dumps, but after a some tries I got a bit over 90% of the document off of the diskette. The main system had no issues with the rump kernel crashing.
So that alone is worth the "price of admission" :)
NetBSD has been a labor of love for a long, long time.
In the mid-90's I was a teenager with a 486-25 on a desk in a closet running NetBSD 0.9-1.0, connected to 10base2 going to my dad's office where there was a computer that dual booted to Linux. I learned so much from those systems; systems programming, how to really use the C programming language, sysadmin skills, reading network traces. A whole part of who I am today derives from those early experiences trying to figure out what the $## was going on while tracking -CURRENT.
Here something you might like : CS631 -- Advanced Programming in the UNIX Environment - NetBSD https://stevens.netmeister.org/631/netbsd.html
I'm retired from tech and a high school teacher these days and allowed to teach wack/out of level things.
I would love to teach operating systems with NetBSD, but between the space hardware stuff I do and the Verilog/digital logic/microprocessor architecture class I teach, I soak up all the interested students' elective slots.
I suppose after 30+ years, any chance of consolidation is hopeless and undesirable?
For hardware, can a single device driver be made for all variants of BSD? If so, then I agree.
From what I've seen, the BSD community swaps code around on a regular basis. But they pick and choose what code to use based on their own goals. It seems to work pretty well.
FreeBSD: I always got the impression this was trying to be full modern UNIX but non-linux
NetBSD: I guess this is for older/less powerful computers based on comments here?
OpenBSD: ???Security???
Dragonfly: a schism over threading, but FreeBSD?
The Linux codebase, on the other hand, is licensed under a copyleft license that only allows its use in open-source projects that themselves only allow their codebase to be used in open-source projects, and so on. Because of this, Linux can incorporate BSD codebases, but not the other way around.
OpenBSD/FreeBSD/NetBSD are open source continuations of the source-available 4.4-BSDlite code (removing AT&T proprietary extensions iirc).
OpenBSD follows BSD principles but focuses on code clarity and security.
FreeBSD tries to be very flexible, putting user-experience over security. (it has to be noted that OpenBSD is very usable, but lacks a lot of nice features like ZFS and DTrace that FreeBSD supports).
NetBSD is all about being incredibly lean and portable. NetBSD will run on basically anything, even things that Linux and other *BSD's have no hope of running on.
So, leaning in to how SSD's behave instead of how HDD's behave- ensuring that the kernel can make effective use of multiple cores etc;
However it goes, the main issue is one no operating system can solve which is modern life relying on the Web and beefier browsers. Unless you want to rebel against that you're probably better off getting a laptop from the past 10 years for < £100 on eBay.
I remember it used to be expensive as heck to do TLS back in 2014~, so much so that we bought accelerator cards and segmented "secure" servers so that load wouldn't hit the ordinary browsing of our sites...
I use a TLS forward proxy. With today's overpowered hardware, I can even run the proxy on an old "phone" (but I cant run NetBSD^1)
This allows the older computers I own to use plaintext HTTP like the good old days
1. Despite https://en.wikipedia.org/wiki/T-Mobile_Sidekick
Imagine this, a system which can watch movies, edit texts, create disks, have curl/wget, send and recieve files using piping server (which is a curl thing) , view pdfs, mpv and what not, a desktop manager, file manager etc.
As someone hacking around with the legendary tiny core linux, I am more and more mind blown each day with just how much can happen in 14-21 MB, you can definitely build a mini self hosting rack with just some remastering as tinycore can actually run podman as well (combine this with alpine containers to create a super duper minimalist self hosting things too)
the possibilities are endless. When I ran tiny core linux on my pc and ran nothing else, It took 21 mb in ram for a whole gui with editors and file managers etc. all running in ram so super fast filesystem with a package manager
I personally wanted to build my own operating system to limit myself to the most minimal system so taht I just study and do nothing else, I thought tiny core was it but then I tried to hack around it and there are sooooo many things in 21 mb, makes me appreciate minimalism
I have to say, the sheer fucking irony of this statement made me do a double-take.
I might be showing my age a bit, but I'm still remembering when web-browsing was considered a "light" activity (without extensions like Web Java), and watching a video was "very computationally expensive".
I guess some shift happened in the early 2010's where video playback was hardware accelerated more frequently; and complicated javascript started taking off as Google unveiled v8.
This is their attempt of everything app, where the whole internet would be behind the UI of their chatbot and it would go through an LLM before being changed by it and then it would pass to us.
Your single comment explains a lot really and this is something that I agree. Everything App is the browser/internet, combining it with things like wasm, you can even run whole iso files in browser wasm itself (Its fresh on my mind because I shared it to somebody on HN right now but try out copy.sh/v86 [1])
[1]: https://copy.sh/v86/
Linux (the kernel) may have been ported to more machines and architectures than NetBSD’s kernel, yes. But is all the code present in the same source tree or do you have to go find patch sets or unofficial branches?
More importantly: is there a modern distribution that builds an installable system for that platform?
The special thing about NetBSD is that you get the portability out of a single and modern tree for many more platforms than any single Linux distribution offers.
In any case, NetBSD is not well known and “why bother because Linux also runs everywhere too” so I thought it was worth explaining.
I asked a major employer why they're using Linux + Apache for an RP when OpenBSD + HAProxy + CARP is a significantly better option. Crickets.
I want a good laptop for OpenBSD (or FreeBSD, at the least) that isn't 10 years old or weighs 5+ lbs.
Some architectures are no longer practical with Linux. The kernel might still support it, but distribution support is sketchy.
For a SPARC64 server refurb project, the choices were pretty much OpenBSD or NetBSD in my case.
Its also one of few OSes where 32-bit 386 is still tier 1 release.
All from single code source code tree.
Once, after accident.
Emotionally I like this - but thinking more dispassionately, these systems use, by modern standards, a huge amount of power. I wonder if, for many (most?) of them, it whould not be more environmentally responsible to replace them with modern, less power-hungry devices.
The cost of creating new computers has got to be pretty high to the environment (I've heard 85% of lifetime carbon emissions from computers are from the manufacturing process), and I strongly suspect that we don't take that into consideration since we greenwash ourselves by forcing China to do our dirty work, chastising them for it, and then patting ourselves on the back for buying "more energy efficient chips".
But if the cost of a new machine is the same as a year or two of the old operating the new is probably the way to go.
They aren't; among other things, most environmental harm is externalized. When you buy things that produce climate change or microplastics, the cost of the impact is paid by society generally.
But aren't those made regardless if the people with old computers upgrade to them or not? I guess over time, they'll make less if people buy less, but the ones we'd purchase today has already been made, and might as well replace less energy efficient devices than just being added to the global count.
I'm surprised someone like the Sierra Club, Consumer Reports, a scientific group, a government group, etc. doesn't undertake it. Yes, it's a bunch of work, there would be uncertainty, but it's essential and better than nothing.
There are such things for food:
* Klimato: https://klimato.com/
* The Big Climate Database: http://thebigclimatedatabase.com/
I hope you understand how unique netbsd is, it is one of the only systems which can be compiled so easily with just a single script even from linux or other systems and its rump kernel etc. drivers from what I know are (modular?) so they could be used with other kernels as well if any kernel wants ie.
You never know where the innovation can be, I feel like that each kernel/operating system can bring a new idea, as an example, templeOS uses Holy C which basically is Just in time C (iirc) and that means that you can just edit files of templeOS and restart and those changes would occur
I know TempleOS is niche and a meme OS but I feel like that there are a lot of ideas and unique operating systems and I have heard that netbsd can be good in giving driver support to.
This is just one of many things, and I feel like the main point of NetBSD and the likes are fundamental hackability, they can run on things like routers as well although most run openbsd/freebsd but still. I don't see a reason not to unless you are speaking monetary (ie. it may take some extra funds developing/hosting but that is chump change) but I feel like NETBSD is a novel project with respectable goals and they aren't going to change just for this.
More Options are a good thing. if I can have a project run on Netbsd, then its very easy to port it over to any other vast array of hardware as well, and that hardware includes extremely embedded hardware as well I guess
Aren't competing kernels already shipping support for this hardware? Surely the project has to have more selling points than "can be compiled with a single script."
I meant in the sense that since NetBSD supports soooo many devices, it can also help innovation in other kernels if need be as well by being able to take driver support via its rumpkernel as well if need be
And to be honest, I feel like there is this sense of freedom knowing that you can have a system which is portable, if some script can run on my pc on netbsd, chances are if its not too specific, it could run on your pc or even your toaster lol!
https://laughingsquid.com/netbsd-toaster/
Netbsd can run on any device possible and I really appreciate it.
>Surely the project has to have more selling points than "can be compiled with a single script."
Personally I have only heard good things about netbsd but I don't have much expertise in it (sorry), I can recommend you to take a look at smolbsd which looks really cool for uni-kernel purposes as well
https://news.ycombinator.com/item?id=45582758
I feel like that there is a lot more things that can be done with netbsd as well or other open source projects in general as well
That's more of a meme than reality and I wish people would actually look into it before mindlessly repeating the trope. I did, when I wanted to run a new OS on a niche device, and the reality is very different. Nowadays Linux works on a lot more hardware than NetBSD does. Yes, NetBSD nominally supports a few more architectures than Linux (very few, especially that μClinux is now upstreamed), but the driver situation for the rest of the system means that it can't run on most devices from those architecture anyway.
Linus hast this with User Mode Linux (upstream) and Linux Kernel Library (out of tree).
> You never know where the innovation can be, I feel like that each kernel/operating system can bring a new idea, as an example, templeOS uses Holy C which basically is Just in time C (iirc) and that means that you can just edit files of templeOS and restart and those changes would occur
That's a while ago, but Fabrice Bellard did a demo with his tiny c compiler where it would would compile the Linux Kernel at boot time and then boot the compiled Kernel.
> This is just one of many things, and I feel like the main point of NetBSD and the likes are fundamental hackability, they can run on things like routers as well although most run openbsd/freebsd but still.
Most consumer grade routers run Linux out of the box.
> More Options are a good thing. if I can have a project run on Netbsd, then its very easy to port it over to any other vast array of hardware as well, and that hardware includes extremely embedded hardware as well I guess
uCLinux (upstream) doesn't even need a MMU. It can run on a Cortex-M4 with 8mb ram.
That’s interesting. Do you have a link you can share? Or remember any more details?
I’m curious how long it took to fully start
https://lwn.net/Articles/108341/
So in my other comment I mentioned some specific(s) to (or rather, originated from) NetBSD, just as much as for example pledge() (fine-grained system call restriction), unveil() (filesystem visibility restriction), arc4random family[1] (ChaCha20-based CSPRNG), reallocarray() (integer overflow-safe realloc), OpenBGPD (BGP daemon), OpenOSPFD (OSPF daemon), httpd (web server), acme-client (Let's Encrypt client), signify (cryptographic signing tool), etc. are specific to OpenBSD.
DragonflyBSD has some goodies too while we are at it! For example varsym (Variable Symbol System - per-process environment-like variable substitution), nlookup (namecache-based path lookup replacing the vnode-based namei()), objcache (per-CPU object caching allocator), LWKT (Light Weight Kernel Threads - message-passing based threading), HAMMER2 (clustered COW filesystem with multi-master replication, successor to HAMMER), and so forth.
All popular BSDs have their own rich history. I know more about DragonflyBSD than NetBSD, so as an example: DragonflyBSD's core design philosophy centers on SMP scalability (cache-coherent token-based synchronization and LWKT message passing, avoiding fine-grained locking), OpenBSD's gist is security, and so forth.
[1] The ChaCha20-based CSPRNG (originally arc4random was RC4-based), which has been ported to other BSDs and some Linux systems.
(Sorry, I was really tempted to elaborate on these unique features and I felt like your comment was the perfect place for it!).
I always had the same question about cleaning recycling as it went through a recycling plant -- is the water usage environmentally "friendly" versus what is ultimately recycled (which is often not much, sadly).
Come on, look at all the businesses and what's really happening in the space you're commenting on. That laptop literally means nothing.
The comparison probably needs to be: Running that old NetBSD machine for a few hours a day, worst case about 40 while I work vs. producing an running a brand new laptop.
If we're talking desktops, then many older machines have 2-300W PSUs, not even enough to power a modern graphics card (I know, an Nvidia card isn't running 600W all the time).
And on a larger scale, you could use your dismissal against almost everything. Every part of society (and businesses are part of society) can think ‘that thing I do means literally nothing when so much else is going on!’ about almost anything.
It uses just 1.5W.
Any more recent alternative would consume much more power.
I’ve just replaced an old Cubieboard (RPi1 alternative - about 2W) running Pi-hole and an old temperamental gigabit router (~10W) with a 2014 Mac mini (plus second Gigabit adapter) - which uses about 11W (a really efficient computer for its age!)
It’s less than the old combo drew - but I wonder if I could be accomplishing the same with an (or even a couple of) SBCs - and if that would ‘pay for itself’ (environmentally well as financially) after a couple of years.
At 11W, the financial costs of running are quite low. I think it's about 90 kWh per year. Depends on your rates, but I've seen $0.60 quoted in comments lately as a high rate for PG&E customers in California, which is about $55. You might well be able to invest in something that can run your load for fewer watts, but I don't know if it's worth the effort.
You're likely to get a lot more savings by looking at things that use more energy.
It is running Gitea, Prometheus and a bunch of small tools I wrote (weather monitoring, home automation, family data sharing and tools for my Kids)
I believe that this is true for just about all widely popular distributions. It's probably possible to set up Arch to have power draw similar to NetBSD, but you're going to have to know what you're doing and it's probably going to require more administration/attention to keep running smoothly than NetBSD does.
By coincidence I installed NetBSD last weekend on a Raspberry Pi. Never used it before, but it seemed very nice. I had some issues with sshd (most likely just me doing something stupid) and never got as far as experimenting with WiFi, but supposedly there is some support (unlike FreeBSD and OpenBSD that do not support WiFi on any Raspberry Pis?).
If you really need wireless you can buy a USB WiFi dongle, and since there is a lot of support a compatible one is restively easy to find.
With a bit less performance? Sure. But for my use-case it works. And more people realizing that might actually be a good thing.
I did replace the screen with a low power screen, which easily had the biggest impact on battery life.
I haven't tested the T480 under OpenBSD in a while, but my guess is that if I ran it with "apm -L", it would get close to the same numbers.
This argument misses the forest for the trees for non-commercial users.
78 more comments available on Hacker News