@grillchen Since GNU is really the project where it has been carefully ensured that everything is free software, meanwhile all BSD's currently contain many proprietary files.
GNU is also functionally superior to every single BSD.
The game those "Open"BSD developers play is not shipping the proprietary software directly, instead they include a makefile with a download link to the proprietary malware.
As per https://man.openbsd.org/fw_update "The fw_update utility installs, updates, or deletes firmware packages for driver from the Internet. *If no driver is specified*, the fw_update utility tries to determine which firmware is needed on the system."
The end result is proprietary malware being installed by "Open"BSD, without the user being asked, or even the license noted (sometimes they copy the license file after it has been installed), even if the hardware works just fine without proprietary software.
There isn't any meaningful difference between proprietary software in the repo and proprietary software linked in the repo, with those links being automatically followed later - therefore "Open"BSD is a proprietary OS.
GNU meanwhile respects the users freedom and never installs proprietary malware, or recommends it - but still doesn't do anything to prevent the user from installing any software they want all the same.
@dcc >you do not need to install open bsd with proprietary drivers... Too bad, fw_update will install whatever proprietary software it possible can.
For example, fw_update will install the proprietary software known as intel microcode updates if you run openbsd in a VT-d VM, even though clearly that software is useless (the proprietary OS known as Debian does this too).
Sure you can patch openbsd to remove the malware installing script, but why on earth would you use an OS that has freedom sabotage built in?