src

> tend to have more features and better help output Just a random opinion. Others disagree and prefer the BSD way. Concrete reasons include code-base simplicity. https://github.com/coreutils/coreutils/blob/master/src/yes.c https://github.com/openbsd/src/blob/master/usr.bin/yes/yes.c

And here is the commit https://github.com/openbsd/src/commit/21b3e8786537fe05ba6f42...

The code change on GitHub: https://github.com/openbsd/src/commit/56bc0efbd80da2ff595e44...

OpenBSD has a WIP driver for the NVMe controller on the M1 chip, but AFAIK it's not working 100% reliably yet. https://github.com/openbsd/src/commit/1c31dbaaf6000562ff37f7... https://github.com/openbsd/src/commit/0ccab0b00204b8c23f121d... Patrick Wildt posted an early video of OpenBSD booting on the M1 Mac Mini back in January. A lot of the internal hardware is supported now as of 7.0-beta, such as the Broadcom Gigabit, Wi-Fi and USB. https://twitter.com/bluerise/status/1354216838406823936

Likely because the author doesn't care about that and are productivity focused. Besides, OpenBSD uses the same drivers as Linux, ported to the OpenBSD kernel. https://github.com/openbsd/src/commit/ad8b1aafbcc34f7eb86e4e...

This is OpenBSD's sshd init script: https://github.com/openbsd/src/blob/master/etc/rc.d/sshd On an archlinux system running systemd I see that the equivalent of the rc_reload function is "ExecReload=/bin/kill -HUP $MAINPID" (which is actually less safe...) I'm not sure if you think that's declarative but to me it's basically as declarative as you can make a shell script. > By default every popular distro before systemd/upstart did. Many services still use them anyways (systemd just generates a shim to run the start/stop/status operations on them) I mean is anyone CURRENTLY using them? Because as far as I'm aware the linux sysvinit situation was a gigantic mess which nobody wanted to bother fixing despite the fact that OpenBSD and other BSDs had already fixed it by that point. I think most linux distros can be taken as an example of how no

OpenBSD has no equivalent to FreeBSD's support tiers, but arm64/aarch64 is supported with binary packages and syspatches today. https://www.openbsd.org/arm64.html Amusing seeing people reacting here on HN to the Apple M1 SoC Linux kernel upstreaming, meanwhile in OpenBSD.. FreeBSD hasn't made any public progress yet on M1 support. https://marc.info/?l=openbsd-arm&m=161386122115249&w=2 https://github.com/openbsd/src/search?q=m1&type=commits

In this case you can just read the previous paper, which explains the caveat that PIE daemons utilizing ASLR must be so-called fork-only services--i.e. forked from a supervisor process. If they're not fork-only than you can't leak the address space layout. The suggested counter measure is to re-exec child processes so their address space is re-randomized. OpenSSH began doing this by default 10 years before the above paper: https://github.com/openbsd/src/commit/5541d005bde289515d9734... Presumably (hopefully) some other common, multi-process network daemons have been refactored to exec child processes. As explained in the paper, nginx, which utilizes an M:N process model, was susceptible. Anybody know if nginx was refactored to fork+exec its worker processes rather than just fork? (EDIT: AFAICT via a cursory examination of ngx_master_proc

From looking at the implementation of yes [0], I would say it follows closely the GNU coreutils implementation [1]. It allocates and re-uses a buffer to speed things up [2] and does not implement the old simple version [3] (or the even simpler OpenBSD [4]) [0]: https://github.com/uutils/coreutils/blob/master/src/uu/yes/s... [1]: https://github.com/coreutils/coreutils/blob/master/src/yes.c [2]: http://github.com//coreutils/coreutils/commit/35217221c211f3... [3]: https://github.com/coreutils/coreutils/blob/ccbd1d7dc5189f46... [4]: https://github.com/openbsd/src/blob/master/usr.bin/yes/yes.c

OpenBSD doesn’t send NTP queries to those sources - with the exception of Cloudflare’s NTP pool. It uses TLS timestamps to constrain the possible time values. This prevents spoofed NTP packets from changing the time. https://man.openbsd.org/ntpd.conf.5 https://github.com/openbsd/src/blob/master/etc/ntpd.conf

> For example, OpenBSD at some point changed how mmap() was defined so that it takes seven arguments: It seems like that was the case from day one, when a copy of the NetBSD code was imported to later become OpenBSD[1]. And if my reasoning is correct, saying that OpenBSD “changed it at some point” is not quite correct. https://github.com/openbsd/src/blob/df930be708d50e9715f173ca...

It's not really philosophical, they just weren't happy with the Bluetooth stack they had (originally from netbsd I think) and no-one has written a new one yet. https://github.com/openbsd/src/commit/b8042ed98e3e7a691133b4...