~ / recent activity
statusRecent activity
Status
Maintenance
A static snapshot rather than a live feed. The notebook is a set of plain files, so there is no running service counting edits. Consider this the short tour: the notes that answer the most questions, and the references worth bookmarking.
Notes that answer the most questions
| Note | Area | What it covers |
|---|---|---|
| Debugging an Apache segfault | Troubleshooting | Core dumps, a backtrace and a null pointer behind a reverse proxy |
| A PHP bus error under load | Troubleshooting | Concurrency and why a file write has to be atomic |
| A home ADSL router running NetBSD | Sysadmin | A Soekris board, PPPoE and the need for MSS clamping |
| Booting a NetBSD guest with PVGrub | Sysadmin | Running paravirtualised guests on a Ganeti cluster |
| Powering two disks from one board | Hardware | A small electric modification for a tiny file server |
References worth bookmarking
- A short gdb field guide
- Git notes on patches and branches
- Building pkgsrc packages on a build machine
- Reading a running kernel with SystemTap
- Links worth keeping
How the notes are kept
Each note lives in a version control repository, so its history is stored with the file itself. When a note is revised, the message attached to that change explains why. Nothing here is wired to a live counter; the repository is the record. If a note has gone stale, the quickest fix is to send the details.