Carla Schroder - Linux Cookbook
Here you can read online Carla Schroder - Linux Cookbook full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. year: 2009, publisher: OReilly Media, genre: Romance novel. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:
Romance novel
Science fiction
Adventure
Detective
Science
History
Home and family
Prose
Art
Politics
Computer
Non-fiction
Religion
Business
Children
Humor
Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.
- Book:Linux Cookbook
- Author:
- Publisher:OReilly Media
- Genre:
- Year:2009
- Rating:4 / 5
- Favourites:Add to favourites
- Your mark:
Linux Cookbook: summary, description and annotation
We offer to read an annotation, description, summary or preface (depends on what the author of the book "Linux Cookbook" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.
Linux information can be found scattered in man pages, texinfo files, and source code comments, but the best source is the experts who have built up a working knowledge of managing Linux systems. The Linux Cookbooks tested techniques distill years of hard-won experience into practical cut-and-paste solutions to everyday Linux dilemmas. Use just one recipe from this collection of real-world solutions, and the hours of tedious trial-and-error saved will more than pay for the cost of the book. Its more than a time-saver; its a sanity saver.
Carla Schroder: author's other books
Who wrote Linux Cookbook? Find out the surname, the name of the author of the book and a list of all author's works by series.
Linux Cookbook — read online for free the complete book (whole text) full work
Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Linux Cookbook" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.
Font size:
Interval:
Bookmark:
Copyright 2009 O'Reilly Media, Inc.
To Dawn Marie.
During the writing of this book, she tilled the fields, trained the horses, cooked the meals, cleaned the ditches, and graciously fended off generous neighbors bearing large zucchinis. No author could ask for more. Thank you for 14 great years; may we have many more.
So: you're a relatively new Linux user. You've got Linux installed, you've managed to log in, do some web browsing, send and receive email, andnow what? Although you can handle some of the basics, you feel like you're flying blind: you know you've got lots of really powerful stuff at your fingertips, or at least so your Linux guru friend told you, but how do you make it do tricks? What's there, and how does it work? What's this thing called grep that they're always talking about? How do you Samba? And where's the #$%^ documentation?
The Linux-Unix world is abundantly documented. No, really! You can always find an answer, if you know where to look. The problem, of course, is knowing where to look. There are man pages, info pages, READMEs, HTML manuals, and the code itself. You don't have to be a programmer to unearth useful bits in source code, because the comments often tell you what you need to know.
There are thousands upon thousands of online communities, one (or more) surrounding nearly every bit of software in the Linux universe. Nearly every program, no matter how small, has its own user mailing list. Every Linux distribution has its own mailing lists and user forums. There are forums and lists and Usenet groups for every computing subject under the sun.
And of course there are books and magazines of every description. So the real problem with Linux documentation is not the lack of it, but finding the bits you need without having to embark on a lengthy, heroic quest.
This book is aimed at folks who want to know what button to push. Understanding the underlying theory is useful, but if you can't make the darn thing work, not very helpful. So it's light on theory and heavy on how-to-make-this-go, with detailed, step-by-step instructions. I've included many references to additional resources.
Readers should have a bit of Linux experience. You don't need to be a guru, but you should have some familiarity with the basics of booting up and shutting down, starting applications, Web surfing, and poking around the filesystem. You should know how to find and use the command line, as well as work in a graphical environment. You should understand that Linux is a true multi-user system, and that you use an ordinary unprivileged user account as much as possible, and that you only invoke root when you really need to.
This book assumes that you are in charge of a PC or LAN, and can acquire rootly powers when the occasion calls for them. You might be a power user who wants complete control of your Linux box, or a home user who wants to run a personal web or mail server, or set up a small LAN. Perhaps you are a Windows system admininstrator who has suddenly been ordered to "do Linux," and you need to know how to set up Linux servers for Windows clients. Maybe you want to add Linux servers to an existing network. You might need to integrate Linux and Windows desktop users on a LAN.
Or you have no need for Windows at all, and just want to learn Linux system administration.
Given that there are thousands of software packages to choose from, almost all of which do something useful, it was a foregone conclusion that I couldn't cover everything. Or even most of everything. I decided what to include, and what to leave out, based on my opinion of what a fundamental Linux skill set should include. (You may have different ideas.) I included programs that I consider to be the best-of-breed, such djbdns, GRUB, Apache 2, vim, and Postfix. And I didn't neglect old standbys like LILO and BIND.
You'll find some excellent, innovative scripts for:
Adding users in batches
Changing passwords in batches
Finding all the installed documentation for a program
Finding orphaned libraries on RPM-based systems, and adding them to the RPM database
I decided not to include productivity and desktop applications, like Open Office, KMail, Firefox, Konqueror, the Gimp, GnuCash, and so forth. This book is about building infrastructure. Once you master the fundamentals of running and maintaining a Linux system, it will take you anywhere you want to go.
There are more Linux distributions than can be counted; there are literally thousands of distributions, many of which are peculiar to a company, a campus, or even a circle of friends who like to roll their own. However, the world of distributions breaks (not very cleanly) into two large camps: RPM-based systems, represented in this book by Red Hat and Fedora, and apt-based systems, represented by Debian. Debian-based distributions are spreading like weeds, such as Knoppix, Xandros, Libranet, Unbuntu, and Linspire.
Even if you are using a distribution that does not fall into one of these two categories, such as Slackware or Gentoo, the fundamentals are pretty much the same. The kernel is the same; the programs and utilities available are the same; the window managers are the same; the only substantial difference is the way you install software.
That's not to say there aren't other differences between Linux distributions. A chronic bugaboo with Linux is differing file locations on different distributions. Get used to it; it's not going to go away. This book provides several excellent methods for finding out where your particular distribution puts configuration files, executables, and program documentation.
The following typographical conventions are used in this book:
Used for filenames and pathnames, hostnames, domain names, commands, URLs, and email addresses. Italic is also used for new terms where they are defined.
Constant widthUsed for code examples and fragments.
Constant width boldUsed for user input.
Constant width italicUsed to indicate text that is replaceable.
Indicates a tip, suggestion, or general note.
Indicates a warning or caution.
One particularly important convention in this book involves the use of command line prompts. I can't say it too often: don't get into the habit of su'ing to root whenever you have to do anything remotely administrative. Even worse, don't say "It's my machine, I can do anything as root." Use root privileges only when you really need them. You'll be safer that way; you'll have some protection against your own mistakes, and against attacks made by outsiders.
To show you when you need root privileges, commands requiring root privileges are preceded by the root prompt, #. Commands that don't require root privileges are preceded by the default bash shell prompt, $.
Don't be confusedthere are many file listings in the book, and in many of these files, comments are preceded by #. Yes, it can be confusing, but you'll get used to it.
Doubtless this book, despite the heroic efforts of me and the fabulous O'Reilly team, contains flaws, errors, and omissions. Please email your feedback and suggestions to for errata, updates, and to download the scripts and configuration files used in the book.
Font size:
Interval:
Bookmark:
Similar books «Linux Cookbook»
Look at similar books to Linux Cookbook. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.
Discussion, reviews of the book Linux Cookbook and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.