| |||||||||||||||
![]() Sell Back Your Copy for $2.43
Whether you buy it used on Amazon for $8.09 or somewhere else, you can sell it back through our Book Trade-In Program at the current price of $2.43.
Used Price$8.09
Trade-in Price$2.43
Price after
Trade-in$5.66 |
Solaris Systems Programming
Rich Teer
The first definitive guide to programming in the Solaris Operating Environment
In the tradition of W. Richard Stevens' Advanced Programming in the UNIX Environment, this book offers comprehensive, practical guidance for systems programmers. It covers all versions of the Solaris OS, from 2.5 through 9 and is relevant to both SPARC™ and x86 platforms. From I/O to IPC, pseudo terminals to localization, and processes to doors, Rich Teer illuminates the unique features and subtleties of this environment as never before.
As a former Sun Microsystems, Inc. consultant, long-time C programmer, and tech reviewer for Stevens' UNIX Network Programming, Teer is singularly well qualified to write this book. Using real-world case studies, code examples, and diagrams, he explains both the "how" and "why" of Solaris systems programminghelping any C programmer write efficient, reliable code. Coverage includes:
$59.99 U.S./$86.99 Canada
PRENTICE HALL PTR
Upper Saddle River, NJ 07458
www.phptr.com
© Copyright Pearson Education. All rights reserved.
About the Author
RICH TEER is a UNIX consultant based in Kelowna, BC, Canada. A long-time respected member of the UNIX community, Rich is an acknowledged Solaris system administration and programming expert, holding SCSA, SCNA, and SCSA certifications. He has fourteen years' C programming experience, and more than nine years' experience working with Sun systems, including two years as a technical support consultant for Sun Microsystems, Inc. He was a technical reviewer for W. Richard Stevens' highly acclaimed UNIX Network Programming, 2nd Edition.
© Copyright Pearson Education. All rights reserved.
Product Details
Would you like to update product info or give feedback on images?
|
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
34 of 43 people found the following review helpful:
1.0 out of 5 stars
Plagiarism is bad,
By ERP DBA "erp_dba" (Des Moines, IA) - See all my reviews
This review is from: Solaris Systems Programming (Hardcover)
I would recommend Thomas E. Dickey's web page to anybody with open mind to decide on this issue.
http://invisible-island.net/critique/APUE-SSP.html I would certainly not pass my English Composition classes if I would be paraphrasing that much from somebody's work without proper references.
30 of 41 people found the following review helpful:
1.0 out of 5 stars
Cannot recommend this book.,
This review is from: Solaris Systems Programming (Hardcover)
At first sight, the book appeared to be typical/average.
However, when checking for specific details to post an opinion of the book I noticed something strange - paraphrasing of material from Stevens' "Advanced Programming in the Unix Environment". Teer does not credit the material which is borrowed. Read more details here - http://invisible-island.net/critique/APUE-SSP.html
28 of 40 people found the following review helpful:
2.0 out of 5 stars
Not a substitute for Stevens' APUE,
By
This review is from: Solaris Systems Programming (Hardcover)
Despite the claim on the back cover, the book is far away from the tradition of Richard Stevens' "Advanced Programming in the UNIX Environment". In contrast to APUE, which truly enlightens the reader with all sorts of historical, portability, and background information, Teer's book is not much more than a Solaris API description.
Many of the examples in it will not work unmodified on Linux, BSD, or other platforms. It will thus not be of much help to a novice Unix programmer unless he actually wants to write Solaris-only programs - not a common scenario in the Unix/POSIX world. But a more experienced programmer can just use the Solaris manual pages to get most of the information contained in the book. Also the book contains one of the most stupid code examples I have ever seen: an snprintf() emulation that works by calling vsprintf() first, then checking its return value to see if the buffer size was large enough, possibly exiting with an error message: int snprintf (char *buf, size_t n, const char *fmt, ...) { [...] len = vsprintf (buf, fmt, ap); [...] if (len >= n) err_quit ("snprintf: \"%s\" caused a buffer overflow", fmt); But when such an overflow is actually exploited on the stack by an attacker, vsprintf() may not return at all, rendering the check useless. The code thus gives a false impression of security. This might be regarded even more dangerous than code that does not perform overflow checks at all, especially in the context of a book. I have to admit that I did not look at too many examples, but I would recommend to be cautious with the book until somebody has verified that this is the only fundamental security error in its code.
Share your thoughts with other customers: Create your own review
|
|
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
|
This product's forum
Active discussions in related forums
Search Customer Discussions
|
Related forums
|