Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderI remember learning about ELF files first because that’s how you’d run pirated PS2 games. Funny how my insatiable appetite for games in my teens resulted in learning so much about Linux executable files and eventually it seemed inevitable that I should just learn to code.
One of my favourite explorations of the ELF format is linked in the comments. Just how small can you make an ELF executable? [0]. Spoiler: 45 bytes, when you go far enough that standard assemblers start getting in the way. When the ELF header becomes part of the program itself. > Of course, half of the values in this file violate some part of the ELF standard, and it's a wonder that Linux will even consent to sneeze on it…
Great read! Thanks for sharing. Would be great if lsm hooks existed for execve and create_elf_table(). Tangential to that,wonder why loading multiple lsm isn't a thing? I can see myself writing complimentary lsm to an existing selinux or apparmor lsm that adds or enhances functionality and security controls.
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 277
- Total comments
- 19
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2017-12-02 | How programs get run: ELF binaries | mgdo | 3 | 0 |
| 2017-12-03 | How programs get run: ELF binaries | jrepinc | 4 | 1 |
| 2018-05-20 | How programs get run: ELF binaries (2015)First breakout | ingve | 129 | 7 |
| 2025-10-25 | How programs get run: ELF binaries (2015)Best thread · Latest 20+ point return | st_goliath | 141 | 11 |