Link to Original Source
Slashdot videos: Now with more Slashdot!
Link to Original Source
The book opens with a gentle introduction to Unix concepts, explaining case sensitivity, manpages, the root user, and so forth. Although users with even a slight amount of experience can skip this part entirely, it would serve as a reasonable introduction for a newcomer.
As one might expect, there is an introduction to both Vi and Emacs; curiously, there is also a section on the older line editors. The remainder of the book covers almost all topics relevant to system administration, including process management, devices, printing, and networking. The style is similar (though not always identical) to the "Cookbook" line of O'Reilly products. Other than the introductory parts for each topic, most of the book follows a simple "problem -> solution" format, allowing readers to quickly identify which part is of interest to them.
In addition to the obligatory section on shell programming, there are sections on programming in Perl and Python. These are in no way replacements for books devoted solely to these languages; it simply can't compete with books that cover a small topic in complete detail. However, they are quite acceptable as both tutorials and lightweight references.
The real value in this book comes from the collection of somewhat- obscure tricks and techniques found throughout. Reading it cover-to-cover would be difficult, but skipping past the introductory sections allows you to discover some real gems. Flipping through it will uncover a wealth of Unix arcana whose very existence may be unknown to even relatively-experienced admins. For example:
- What command would you issue to find out which virtual console (or pseudo
terminal) you are using?
- What is the easiest way to add line numbers to the front of each line of text in a file?
- What does ':' mean to Bash, and how can it be used effectively?
Overall, the book is a solid addition to any admin's library, and would make an excellent purchase for someone interested in learning system administration from the basics.
- Dalhousie University ACM Chapter"
There's a few sites which aim to free you of this process by providing anonymous accounts for different sites. For example, bugmenot.com gives you a long list of accounts to log into each website.
But it would be much better if I could just assume that a particular account would be available on all sites. Imagine if you could just log into every site as 'John Hendrix' and enter the password 'foobar01'.
Is there any reason why we can't all log into the New York Times using the same username and password? I was thinking we could make a community effort to create the same account on all of those sites which ask you to login. So whether you were visiting the Sacramento Bee, the New York Times or the New York Post, you could be sure that 'John Hendrix' had the same password. And if you visit a site where John Hendrix doesn't exist, or has been deleted by the administrator, just make a new account for him."