@grillchen >afaik openbsd has no proprietary blobs at all
They say that and then I look and find proprietary software;
https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/sysutils/acx-firmware/
https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/sysutils/arm-trusted-firmware/ (there may be a free version of this, but I have no doubt that they the proprietary version only)
https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/sysutils/bwi-firmware/
https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/sysutils/firmware/

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.

When you install "Open"BSD, this script is run *with no driver specified* without the user being asked; https://cvsweb.openbsd.org/src/usr.sbin/fw_update/

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.