Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #19546

M

Manu's Public Articles and Projects

Personal blog · articles.manugarg.comsystemsprogramming

Manu's Public Articles and Projects is a personal blog at articles.manugarg.com about systems and programming. Since 2011, 4 different Hacker News readers have linked it 5 times. No feed was found, so read it on the site itself.

No feed foundVisit the blog
5mentions?
4HN people?
2011–2017first – last linked?
Links on Hacker News per year · peak 1 in 2011

Too few sampled comments (4) to say how often HN recommends it.?

Why HN links it

HN readers link this blog for articles on Linux system calls, statically linked programs and assembly 'Hello World' programs. Commenters cite these articles when discussing how syscalls work.

Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Articles : Manu's public articles

Most-linked posts?

  1. /systemcallinlinux2_6.html
    2 people · 3 mentions · first linked 2011-05-23

What Hacker News says?

  1. Sounds complicated, if AMD and Intel both use different instructions for system calls: http://wiki.osdev.org/Sysenter http://articles.manugarg.com/systemcallinlinux2_6.html

    Comment linking /systemcallinlinux2_6.html

    on ““Hello World” in assembly language on Linux”
  2. Submitted About ELF auxiliary vectors as a story · 1 points

    HN discussion
  3. The diagram showing the stack on program entry misses the auxiliary vector[0]. As a sidenote, I find stack diagrams more intuitive (for typical descending stacks) when the low address is drawn at the top. This way it looks like a real-world stack and if you need to represent some data or executable code in the same address space it will appear in natural order, from top to bottom. [0] http://articles.manugarg.com/ab…

    Comment linking /aboutelfauxiliaryvectors.html

    on “How statically linked programs run on Linux (2012)”
  4. This focuses on int 0x80, which is the old method; it's been replaced by the sysenter opcode, which is faster on newer chips. (This has been the case since Linux 2.5, and Pentium II+ processors; it was apparently first noticed on the Pentium IV.) Would this basic method work with sysenter? http://articles.manugarg.com/systemcallinlinux2_6.html http://kerneltrap.org/node/531 (From 2002) http://lwn.net/Articles/18412/…

    Comment linking /systemcallinlinux2_6.html

    on “Linux on Windows (Wine in reverse)”
  5. > (e)glibc and friends are fairly critical since they are the one exposing kernel features. By default. Unlike in Windows (from what I understand), in Unix-like OSes (Linux, the BSDs, probably others) it's entirely possible for user programs to talk directly to the kernel via a published API. In Linux, C programs can use the syscall(2) function and x86 and x86-64 assembly language programs can use either the sysente…

    Comment linking /systemcallinlinux2_6.html

    on “Apache Kills Off Its C++ Standard Library”

Search all of HN for articles.manugarg.com