renzume.
2025-02-12

you don't link all of libc

A technical exploration of how linking with libc works on OpenBSD, demonstrating that programs don't actually link with 'all of libc' but rather specific object files as needed. The article explains the mechanics of ar archives and linking processes, debunking common misconceptions about libc linking.

Original archive.is archive.ph web.archive.org

Log in to get one-click access to archived versions of this article.

read comments on news aggregators:

Related articles

Let's code a TCP/IP stack, 1: Ethernet & ARP

A detailed guide explains how to build a TCP/IP stack from scratch, focusing on implementing Ethernet and ARP protocols in userspace Linux. The implementation uses TUN/TAP devices for intercepting network traffic and demonstrates successful ARP request handling, serving as an educational resource for deep network programming.

How Copyover MUD Servers Worked | Blog

An exploration of MUD (Multi-User Dungeons) server architecture reveals a clever technique called 'copyover' that allows stateful servers to update their code while maintaining connections and state. The method utilizes Unix primitives like pipes, fork(), and file descriptor persistence to achieve seamless server updates without disconnecting users.