Sun Certified System Administrator for Solaris 10 Study Guide (Exams 310-XXX & 310-XXX)
Author: Paul Sanghera
Primarily Written for those who want to earn the Sun Certified System Administrator (SCSA) certification for Solaris 10, this guide presents full coverage of the official objectives for both the required exams: CX-310-200 and CX-310-202. In spite of the laser sharp focus on the exam objectives, this is not a cram style book. Written in a classroom-based teaching style, this book presents material in a sequential fashion: topics and chapters build upon the previously covered topics and chapters. There is no hopping from topic to topic. An introductory chapter for beginners and a cohesive, concise, yet comprehensive presentation of the material makes it a self contained book that requires no prior experience in Solaris or UNIX. Even after passing the exam, you will find yourself coming back to use this book as an on-the-job reference.
Full coverage of exam topics includes:
- Basic and advanced Solaris 10 installation
- Managing file systems and core dumps
- Performing user and security administration
- Managing network printers and system processes
- Performing system backups and restores and managing storage volumes
- Managing naming services
- Managing role based access control and system messaging
- Understanding fundamentals of TCP/IP networking and managing network services
The book features complete details on all exam objectives, 250+ practice questions, step-by-step exercises, on-the-job elements, a two-minute drill at the end of each chapter that reviews the key points in the chapter, and chapter self-tests. The CD contains MasterExam practice exam software with all new questions, a Searchable electronic book, and a second practice exam (withfree online registration).
Dr. Paul Sanghera (San Jose, CA) Linux+, Network+, CAN, SCP, SCSA, is a technologist, educator, and entrepreneur based in the Silicon Valley, California. With a Ph.D. in Physics, and a Master’s in Computer Science from Cornell University, Dr. Sanghera is an expert in Computer Networking, TCP/IP protocols, Java Technologies, and peer to peer distributed communication systems. He has more than 15 years experience working with the UNIX system environment, including work at research laboratories such as CERN and the Wilson Nuclear Synchrotron Laboratory at Cornell University, and in the computer industry. He has taught technology courses in the Bay Area at CSU Hayward, San Jose State University, Golden Gate University, and Brooks College.
Paul was a founding member and Director of Engineering at an e-commerce company, weborder, that was sold to Netopia. He has also been at the ground floor of several other technology startups such as Dream Logic, and MP3.com. DR. Sanghera has also worked as Senior Software Engineer at Novell, and Netscape, and have contributed to technologies such as Netscape Communicator, NDS, and sellerXpert. Author and co-author of more than 150 research papers published in American and European research journals, Dr. Sanghera has made professional presentations by invitation at several International conferences.
Book about: Cooking Vegetarian or Kitchen
Perl Best Practices
Author: Damian Conway
Many programmers code by instinct, relying on convenient habits or a "style" they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good.
But if you're serious about your profession, intuition isn't enough. "Perl Best Practices" author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects.
With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging.
They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, "Perl Best Practices"offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how
software ought to be created.
Most of all, "Perl Best Practices" offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way.
Praise for "Perl Best Practices" from Perl community members:
"As a manager of a large Perl project, I'd ensure that every member of my team has a copy of "Perl Best Practices" on their desk, and use it as the basis for an in-house style guide."
-- Randal Schwartz
"There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book."
-- Peter Scott
"Perl Best Practices" will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of "scripting languages." Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too."
-- Andy Lester
"Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years."
-- Bill Odom
"Finally, a means to bring lasting order to the process and product of real Perl development teams."
-- Andrew Sundstrom
"Perl Best Practices" provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers."
-- Bennett Todd
"I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer."
-- Paul Fenwick
"At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues."
-- Jacinta Richardson
"If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it."
-- Steven Lembark
"The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until "Perl Best Practices," This book fills a large gap in every Perl bookshelf."
-- Uri Guttman
Table of Contents:
1 | Best practices | 1 |
2 | Code layout | 8 |
3 | Naming conventions | 36 |
4 | Values and expressions | 51 |
5 | Variables | 73 |
6 | Control structures | 93 |
7 | Documentation | 132 |
8 | Built-in functions | 149 |
9 | Subroutines | 175 |
10 | I/O | 202 |
11 | References | 227 |
12 | Regular expressions | 235 |
13 | Error handling | 273 |
14 | Command-line processing | 299 |
15 | Objects | 318 |
16 | Class hierarchies | 359 |
17 | Modules | 397 |
18 | Testing and debugging | 420 |
19 | Miscellanea | 441 |
No comments:
Post a Comment