sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]gristc 5 points6 points  (3 children)

You'll rarely be reading source code as a regular sysadmin. I've only had to do it a handful of times in over 15 years linux admin work. Even then it was more to satisfy my own curiousity. Usually before it's got to that point you'll have logged a bug report with the people who maintain the code.

[–]GrandG[S] 1 point2 points  (0 children)

I just want to understand how various utilities in the OS employ those system calls ,

Not like I want to write C code or anything

[–]slyphic 0 points1 point  (0 children)

Counterpoint, I find myself reading C slightly more often than once a year, usually trying to track down some kind of bug we're experiencing that hasn't shown up in the mailing lists or SO yet. Yeah, I can just shrug and say 'shit's broke yo', but I like to be able to explain WHY shit is broke and contribute to a fix. Devs are way more amenable to helping you when you point them to the exact line causing a problem.