src

On GitHub, appears at [0] with comments coming in today at [1]. 0 - https://github.com/openbsd/src/commit/2e40dd69ac29d6a858309b... 1 - https://github.com/openbsd/src/commit/cc66e8f557d6f3d4dea5ea...

No. All that it is is common heritage in the BIND DNS client library whose doco this is. It is a widely used DNS client library that has made it into numerous operating system's C libraries, from Solaris through GNU libc to OS/2. The manual pages for that library have spread along with it. * https://www.isc.org/downloads/libbind/ * http://wiki.netbsd.org/individual-software-releases/netresol... * https://sourceware.org/git/?p=glibc.git;a=blob;f=resolv/READ... One can even trace its spread from, say, 386BSD through NetBSD to OpenBSD. * https://github.com/NetBSD/src/blob/516da8a02fc8bc10555ed9acd... * https://github.com/openbsd/src/blob/df930be708d50e9715f173ca... Manual pages are not standards, not specifications, but implementation documentation. As Chuck McManis said in this very discussion, to misuse them as standards or specificati

The BSDs and Solaris/Illumos have had DRM for years (where available), but it tends to lag the Linux version significantly because it's not trivial to port the code from Linux. I'm not sure where the compatibility breaks relative to the code given on the page, but most of them have some derivative of the original drm.h header that defines most of the structs and ioctls mentioned (e.g. [1] [2] [3]) [1] https://github.com/freebsd/freebsd/blob/master/sys/dev/drm/d... [2] https://github.com/openbsd/src/blob/master/sys/dev/pci/drm/d... [3] https://github.com/illumos/illumos-gate/blob/master/usr/src/...

https://github.com/openbsd/src/blob/master/sys/dev/acpi/dsdt... https://github.com/openbsd/src/blob/master/sys/dev/acpi/dsdt...

In case someone is interested, here is relevant code [0]. Notice that mutexp is read without any synchronization, and _spinlock further down uses different lock than one in initialization code (former is specific to this mutex and latter a global one). There is no happens before relationship between mutex initialization and mutex locking. Thus, if different thread reads non-null value of *mutexp, there is no guarantee that writes done to the mutext structure itself will be visible. Given strong memory model of amd64 and i386, compiler would have to reorder pointer publication and structure initialization in pthread_mutex_init, unlikely but certainly a valid change given lack of synchronization. [0] https://github.com/openbsd/src/blob/0ecb71b5ec9e4b22a484606f...

OpenBSD has had a github mirror for awhile now. The commit is here: https://github.com/openbsd/src/commit/bc04e837fd81a3001f68f1... As for clang version, it looks to be 4.0.0 per https://github.com/openbsd/src/commit/53d771aafdbe5b919f264f...

The design djb talks about of pre-generating batches of random numbers, deleting the cipher key and erasing the numbers as they are extracted is exactly what OpenBSD has done since Markus Friedl switched arc4random() to use ChaCha20 in 2013: https://github.com/openbsd/src/commit/90c1fad70a3483c2c72c3c... The design was inspired by Nick Mathewson's libottery: https://github.com/nmathewson/libottery I think he misses the point his criticism of getrandom() - that is intended to be the interface by which the libc PRNG gets its seed; userspace programs should just use the libc PRNG instead of going off to the kernel (i.e. arc4random())

For something somewhat related, see parts of this thread: https://news.ycombinator.com/item?id=14414610 Note that cat+gnu awk was faster than just gnu awk - but mawk was faster still (reading a not entirely small file). And in a similar vein of gp comparing Gnu and Openbsd, note that openbsd cat is a little more convoluted than the simplest possible implementation (at least to my eyes): https://github.com/openbsd/src/blob/master/bin/cat/cat.c https://github.com/coreutils/coreutils/blob/master/src/cat.c (That is, Gnu "cat" and OpenBSD "cat" are less different than Gnu "yes" and OpenBSD "yes").

Is it really "easier, cleaner and shorter to write it in python"? Did you look at the OpenBSD implementation? https://github.com/openbsd/src/blob/master/usr.bin/yes/yes.c It's essentially line for line identical to your python code...

Speed vs readability: https://github.com/coreutils/coreutils/blob/master/src/yes.c https://github.com/openbsd/src/blob/master/usr.bin/yes/yes.c

Completely agree. But the tools don't make this very easy. Back in college I was working on patches to OpenSSL, Chrome, Firefox, Apache, etc., to add support for TLS-SRP, and it was a huge pain to jump into these massive codebases and try to understand them. I was using Emacs and had all of the various language support modes configured, but go-to-definition and cross-references barely worked. Searching was slow, and if I wanted to discuss a piece of code with my CS lab partners, I couldn't just share a link. A friend felt the same pain but then went to work at Google for a bit. At Google, they have some pretty amazing code reading/searching tools (see https://static.googleusercontent.com/media/research.google.c...), and these tools helped Google build a culture of thoroughly reading and reviewing code. The causality is bidirectional, but