- Shopping Bag ( 0 items )
1 Introduction 1
2 IPython 21
3 Text 71
4 Documentation and Reporting 123
5 Networking 147
6 Data 177
7 SNMP 205
8 OS Soup 227
9 Package Management 257
10 Processes and Concurrency 289
11 Building GUIs 323
12 Data Persistence 357
13 Command Line 387
14 Pragmatic Examples 405
Appendix Callbacks 419
Posted March 12, 2009
I recently got my hands on a copy of "Python for Unix and Linux System Administration". After reading it, I felt the time I've invested in reading it was well spent. The author introduced the reader to many different situations where python would help make their lives as system administrators easier, without confusing the reader with some complex forms or statements. My feeling is that this book is aimed at people who want to use Python to solve their problems quickly and efficiently, but only have a limited experience with the language - and the books fits that purpose well with its rather superficial approach that the reader can later extend later on with various available resources. It would only be fair that I too mention some of the shortcomings that I noticed while reading this book.
1) The author introduces the reader to ways that Python can be used.
2) Most of the time there will be more than one way to accomplish a task. The author at times presents a scenario and showed the reader how to do the same task with different modules. This places the choice of which to use back where it belongs, with the reader.
3) The book has a website (most do these days) where the code examples can be downloaded. http://py4sa.appspot.com/
1) More time was spent on iPython than was really needed.
2) The case of a word is important in Python. For instance "import Sys" and "import sys" are two completely different things. There were quite a few occasions where a module name was used as the first word in the sentence and because of that it was capitalized.
3) There was once instance that I saw where a script example had no indentation at all. Trying to run it would have resulted in complete failure.
4) It would have been nice if the script examples were named instead of leaving it to the reader to figure it out based on the imports used in another example.
When all is said and done I think I would recommend the book to others if I knew that they had at least some background with Python. And I would highly recommend that they check the addendum and errata pages.