Linux Programming by Example

Simon P. Chappell writes "Linux programming is the C Programming Language. Elaborating a little, Linux programming is C, with the GLIBC library and the POSIX standard API. Even a language as powerful as C needs libraries and to get the Holy Grail of cross-platform portability, it's necessary to have them standardised. The POSIX API is that standardisation and Linux adheres to it very well (opinions from those litigious folks in Utah aside). For those of us who already know C, Linux Programming by Example sets out to teach you the rest in a step by step, helpful, relaxed and incremental manner." Linux Programming by Example author Arnold Robbins pages 687 (21 page index) publisher Prentice Hall rating 10 reviewer Simon P. Chappell ISBN 0131429647 summary An exellent tutorial for real-world Linux software development

What's To Like There are many things to like about this book (over and above the fact that page 118 has my all-time favourite UserFriendly cartoon on it :-). Linux Programming by Example (LinuxPbE hereafter) takes a steady, incremental path through the concepts required to write software that can effectively interact with the Linux environment.

It is a truism many of us have proven multiple times in our lives that one of the finest learning tools available to programmers is to read and grok good, working code, written in the language that we are learning. LinuxPbE takes this philosophy and walks you through actual example code from various Unixes and Linux. The first part of the book, specifically chapters one through six, covers all of the aspects of Linux programming necessary to understand the Unix V7 ls program in its full glory in chapter seven. I feel that this approach works very well.

Part two dives into processes, walking us through creating them, managing them, communicating with them by using pipes and sending them signals. A few other general topics are included for completeness. Part three then covers the art and tools of debugging in fairly substantial detail.

All the code in the book is very well laid out, with line numbers provided to the left, and comments (in a small sans-serif font) on the right-hand side of the code. This is a very readable combination that is enhanced further by the fact that at each logical division, an explanation is given of the design and implementation used by that section.

I can't resist admiring the addition of the essay "Teach Yourself Programming in Ten Years" by Peter Norvig. This is a classic exploration of the effort needed to attain mastery of any skill, concluding that the minimum length of time required is ten years. The inclusion of this article, to me, speaks well of the author and his understanding of the learning process. One can only hope that those learning from this book will come to the same understanding and realise that the book is the start of their journey to mastering Linux programming.

What's To Consider

Nothing notable.

Summary If you want to learn how to do this stuff for real, then this book will get you started. As "Teach Yourself Programming in Ten Years" explains, no book is going to cause you to become an expert in 24 hours, 24 days or even, perhaps, 24 months. That said, this book will be useful for many of those ten years, so run or surf to your favourite bookstore and purchase it now.

You can purchase Linux Programming by Example from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Comments

Bookpool!

[jargoone]

This particular book is currently out of stock there, but I just thought I'd mention one of my favorite sites, bookpool.com. This particular book costs 15% of the list ($6) less than Barnes and Noble. They have great service and fast shipping (often free if you purchase enough).

No affiliation whatsoever, just thought I'd share.

Re:Bookpool!

[fingusernames]

Yeah, I started using Bookpool when I was in college, around 92 I believe. Whenever it was, it was before it was a web site or had a domain or was even a company. "It" was just a mailing list, you'd say what book you wanted, and when enough wanted it, they'd go for a group deal from the publisher. It has always had the best prices. For technical books, there is simply no need to look anywhere else.

Larry

Re:automake, autoconf, .src.rpm, ...

[tcopeland]

There's a good book on the auto[blah] part of that - it's GNU Autoconf, Automake, and LibTool.

It gives a good overview, as well as some extras - i.e., chapter 21 - "Writing Portable Bourne Shell".

re "Teach Yourself Programming in Ten Years"

[kclittle]

I've been programming for 30 years. I recently discovered Python. I'm ass-deep in the uglyness of XML. I'm getting comfortable with Linux, beginning to understand where it's like *nix and where it's not. I'm reading up on .NET; some of it's new, some of it's borrowed, some of it's ugly, some of it's pretty neat. I'd like to get a chance to play with Erlang or ML.

In short, I am *still* learning, and there are areas I've not even scratched. And I'm having a ball! Ten years? Heck, it may take me fifty!

Re:Umm, whats with that user friendly comic.

[Spoing]

DOS didn't have inodes. The comic is multi-platform. :)

Re:example code

[aridhol]

Read that site again. You'll find that int main(void) is legit, it's void main(void) that they don't like. And, according to the C standard, it's one of the two legal signatures for main (the other is int main(int argc, char **argv)).