src

You're welcome. And you might like to see ''sys/queue.h'': https://github.com/openbsd/src/blob/master/sys/sys/queue.h

I think they meant to draw attention to the implementation of `yes` to showcase crustiness the C stdlib imposes on even a trivial program. But of course GNU is kind of notorious in this regard. Compare their `yes` to OpenBSD's. It's night and day. https://github.com/openbsd/src/blob/master/usr.bin/yes/yes.c

No because in the case of the "ls" command, it replaces non-printable characters with a question mark '?', including newline characters. I believe the actual source code for this behavior can be seen here: https://github.com/openbsd/src/blob/master/bin/ls/utf8.c

> If you want to have fun, try calling revoke(2) on character devices that are not TTYs. I remember fixing a bug in FreeBSD once, where you could make the system panic by calling that function on /dev/bpf. IIRC there's a lot of problems with revoke(2) on anything that's not a tty device, so on OpenBSD revoke(2) returns ENOTTY in those cases. https://github.com/openbsd/src/commit/0aefaaaa63aa6de2ea734f... https://github.com/openbsd/src/commit/205dd0b22f2c32de7bacbd... This was discovered earlier on during pledge(2) development.

It turns out the ifconfig command does not provide any default subnet mask parameters. That is done inside the kernel. Changing the kernel would break backwards compatibility. https://github.com/openbsd/src/blob/0970cb57551e0e8df6688f8a... https://github.com/torvalds/linux/blob/cb8e59cc87201af93dfbb...

Which BSDs did you try and what is the precise behavior of subnet mask parameters that you had a problem with? It would be best if you could include the exact ifconfig command, the output from running the command and what was the expected outcome. 1) Yes, there is active development. BSDs don't have net-tools as a separately developed package. https://github.com/openbsd/src/commits/master/sbin/ifconfig https://github.com/freebsd/freebsd/commits/master/sbin/ifcon...

My guess is that it's because Perl is very comfortable for a team that mostly writes C on a Unix like platform. The general syntax, operators, etc, are close, and familiar things like stat(), gethostbyname(), etc, work almost the same. Edit: One of their Perl scripts for reference: https://github.com/openbsd/src/blob/b66614995ab119f75167daaa... And pkg_add, which has quite a lot of Perl: https://github.com/openbsd/src/tree/master/usr.sbin/pkg_add

This would not have wholly worked with Linux. As I've noted elsewhere in this discussion, Linux does not support all of the Unix mechanisms. It does not implement the XCASE line discipline flag; so, unlike on Unix, on Linux one cannot use the xcase mechanism to get lowercase on an uppercase-only terminal. FreeBSD doesn't support the Unix mechanism, either. Nor does NetBSD. Xe could have connected it to an OpenBSD system. OpenBSD still supports the whole mechanism. * https://github.com/openbsd/src/blob/57d747eef2b80ca9ffb95407...

In 2012, first release 5.3 in 2013. Added by Matthew Dempsky. It was used for the per-shared object stack protector cookie extended for the per-function cookies required for RETGUARD. https://github.com/openbsd/src/blob/master/libexec/ld.so/SPE... https://www.openbsd.org/innovations.html No other OS has this.