I don't think syscalls are strictly part of Computer Science. They're an implementation detail of how we have collectively decided to write operating systems. A

I don't think syscalls are strictly part of Computer Science. They're an implementation detail of how we have collectively decided to write operating systems. As such, they're far more relevant to software engineering or computer engineering than computer science. As Dijkstra once (supposedly) said, Computer Science is no more about computers than astronomy is about telescopes. You can be a computer scientist without ever even touching a computer (although I imagine these days most of us do anyway as a hobby). For example, my Computer Science PhD dissertation involves precisely zero lines of code. Following the astronomy analogy, I would place syscalls firmly within the telescope operating manual. That said, almost every undergraduate CS program that I've seen contains a dose or two of software engineering. I learned about syscalls in my OS undergrad class, which was an elective to the major. I also learned about how to use version control such as GIT and Subversion in a non-elective CS class... also not CS in the strict sense, but hard to avoid I guess?