title: Linux for Developers: Jumpstart Your Linux Programming Skills (Developer's Library)
author:  William Rothwell 
description: At the impressionable age of 14, <b>William &ldquo;Bo&rdquo; Rothwell</b> crossed paths with a TRS-80 Micro Computer System (affectionately known as a &ldquo;Trash 80&rdquo;). Soon after, the adults responsible for Bo made the mistake of leaving him alone with the TSR-80. He immediately dismantled it and held his first computer class, showing his friends what made this &ldquo;computer thing&rdquo; work. Since this experience, Bo&rsquo;s passion for understanding how computers work and sharing this knowledge with others has resulted in a rewarding career in IT training. His experience includes Linux, Unix, and programming languages such as Perl, Python, Tcl, and BASH. <br> <br>Rothwell is the founder and lead instructor of One Course Source, an IT training organization. He is author of <i>LPIC-2 Certification Guide</i>, contributing author of <i>CompTIA Linux+/LPIC-1 Cert Guide</i>, and technical editor of <i>Red Hat RHCSA/RHCE 7 Cert Guide</i>.<br> <br>
zlib_text: Overview  
  This book is about writing software that makes the most effective use of the system you're 
  running on -- code that interfaces directly with the kernel and core system libraries, including 
  the shell, text editor, compiler, debugger, core utilities, and system daemons. The majority of 
  both Unix and Linux code is still written at the system level, and Linux System Programming 
  focuses on everything above the kernel, where applications such as Apache, bash, cp, vim, 
  Emacs, gcc, gdb, glibc, ls, mv, and X exist.  
  Written primarily for engineers looking to program (better) at the low level, this book is an 
  ideal teaching tool for any programmer. Even with the trend toward high-level development, 
  either through web software (such as PHP) or managed code (C#), someone still has to write 
  the PHP interpreter and the C# virtual machine. Linux System Programming gives you an 
  understanding of core internals that makes for better code, no matter where it appears in the 
  stack. Deb