src

For me, when I learned more than 20 years ago, reading source and manpages from Linux and other Unix like projects was a source of inspiration. I'd recommend OpenBSD libc. https://github.com/openbsd/src/tree/master/lib/libc String functions especially are a good way to get into the C way of thinking. Since C's approach to strings is unique. I also learned a lot by reading manpages of libc functions or Unix utilities and thinking about how they were implemented, and writing my own little versions.

True. The author might enjoy studying something like OpenBSD (https://github.com/openbsd/src)

I'm not sure I follow - you want a smart, small webserver that takes in a http request and updates an analytic store based on headers? Sounds like something nginx might handle via lua scripting? Otherwise, maybe you want: https://github.com/lammertb/libhttp Or you might want to look at either of: https://www.acme.com/software/thttpd/ https://github.com/openbsd/src/tree/master/usr.sbin/httpd If you really want to build (another) web server in C. Not entirely clear why want to use C for this, though?

Is this even a bug? An invalid length is already being checked by the kernel. https://github.com/openbsd/src/blob/4628c0e6cf9bd4a6d679c314... Sure his fix made it more robust, but the problem only showed up because he had his fuzzer bypass validation that was being done outside of the function.

[BSD systems do](https://github.com/openbsd/src/tree/master/regress/sys)

I believe the Samsung Galaxy Book Go was tested with OpenBSD during the initial development for the ThinkPad x13s, keyboard support was added in this commit. https://github.com/openbsd/src/commit/74edc71ccae4051eda11fa... Many of these older generation "Windows on Snapdragon" laptops unfortunately did not use fast NVMe storage however, only slow eMMC and eUFS (Universal Flash Storage), the latter currently being unsupported by OpenBSD.

Reminder, there are many different netcats, here are some of the most commons: - netcat-traditional http://www.stearns.org/nc/ - netcat-openbsd : https://github.com/openbsd/src/blob/master/usr.bin/nc/netcat... (also packaged in Debian) - ncat https://nmap.org/ncat/ - netcat GNU: https://netcat.sourceforge.net/ (quite rare) To prevent any confusion, I like to recommend socat: http://www.dest-unreach.org/socat/

This will be a MAJOR problem when trying to incorporate the DHCP Vendor OPTION message fields … programmatically. It is easily done in ISC DHCP but not available in systemd, udhcpcd, nor dnsmasq. Looking at you ISPs who use Juniper Network concentrators and routers. Also I use ISC DHCP to help compensate for Nintendo DS handhelds who have brokenly incorporated a space into its DHCP hostname.[2] Now going to look at OpenBSD fork of ISC.[3] 2] https://github.com/egberts/isc-dhcp-server-nintendo 3] https://github.com/openbsd/src/blob/master/usr.sbin/dhcpd/dh...

Here are a few implementations that did not get the memo: coreutils ls: https://git.savannah.gnu.org/cgit/coreutils.git/log/src/ls.c freebsd ls: https://github.com/freebsd/freebsd-src/commits/927f8d8bbbed7... busybox ls: https://git.busybox.net/busybox/log/coreutils/ls.c openbsd ls: https://github.com/openbsd/src/commits/master/bin/ls/ls.c The latter seems to be the most stable, yet has been updated two years ago, many years after its first introduction.

Loading data from random memory locations became too expensive compared to computations. For log, exp, trigonometry, and similar, I think people rarely use any lookup tables. Instead, they use some high-poly approximations, and for log/exp abuse IEEE binary floats representation. Here's a log() function from the standard library in OpenBSD: https://github.com/openbsd/src/blob/master/lib/libm/src/e_lo...

> Our policy is to stick with stable supported interfaces whenever possible Except you're not doing that consistently though. On OpenBSD, mincore(2) was removed 3 years ago, and it's UNIMPL syscall 78 was eventually recycled by a different system call: mquery(2), which your library calls expecting mincore and passes bogus arguments to. I would be very surprised if there aren't more serious mistakes lurking in your library, in fact I know there are. https://github.com/openbsd/src/commit/54e4f6b9a1dc183e1dc7c4... https://github.com/openbsd/src/commit/1d60349d0b961891264d42...

A cleaner example without bit masking: https://github.com/openbsd/src/blob/master/lib/libc/crypt/ar...

> I think he's absolutely right. The str* functions are just worse versions of the mem* functions. Per Todd C. Miller (creator of strlcpy and maintainer of sudo) and Theo de Raadt (OpenBSD) in these 1999 (PostScript) slides, the simplest implementation of strlcpy() uses (can use) memcpy(): size_t strlcpy(char *dst, const char *src, size_t siz) { size_t n; size_t slen = strlen(src); if (siz) { if ((n = MIN(slen, siz - 1))) memcpy(dst, src, n); dst[n] = ’\0’; } return(slen); } * https://www.openbsd.org/papers/strlcpy-slides.ps The current OpenBSD is currently different: * https://github.com/openbsd/src/blob/master/lib/libc/string/s... * https://cvsweb.openbsd.org/src/lib/libc/string/strlcpy.c One problem with memcpy() is that it returns (void *

i havent used C in quite a while but I did not remember strlcpy using strlen, and it seems the linux kernel's implementation differs quite a bit from the openbsd one: https://elixir.bootlin.com/linux/v5.19.3/source/lib/string.c... https://github.com/openbsd/src/blob/master/lib/libc/string/s...

The original strlcpy() was written for OpenBSD (2.4) by Todd C. Miller (who has also been the maintainer of sudo since 1994): * https://github.com/openbsd/src/blob/master/lib/libc/string/s... * https://cvsweb.openbsd.org/src/lib/libc/string/strlcpy.c