Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i am looking for a book with the most basic info for linux using. i have read several books about different aspects of different distros, and even the book about linus torvalds(very interesting-i instantly identified with him, he sounds a lot like me in many ways). all of the books i find for beginners are lacking in one important area-they offer no examples of how to actually perform the functions they speak about. i know how to download a tarball, for example, but when i try to compile it to install using the mke command, it tells me that i haven't specified the target. i used the -h to get a list of command options, but nowhere do i find out how to actually decide where to put the target or how to use it. i am looking for a book listing the commands i need including the function and syntax used. it took me almost a week to figure out how to pull up a command line. admittedly, i haven't tried the 'for dummies' type of book, maybe the info is there? i am a beginner with experience programming basic, pascal, and cobal from the late '80s, and windows from '98. i used to be a tacfire repairman(ibm mainframe which is obsolete now), so i know the mechanics of computing, but without some sort of guide, i feel like an idiot sometimes when my wife says 'why can't i download pictures?' and i tell her that i need to figure out how to use the program i just downloaded.
Most of the O'Reilley books are good. Start with something basic. And read it in small doses.
When learning a system, I strongly suggest keeping a diary. Write down what you learn, and write down your questions. Once you've written a question down, you won't forget it, and you can choose when to explore it.
I also suggest that you "get acquainted with the forest before you start studying trees." Always try to "get the big picture" first. The Linux system consists of many, loosely-connected parts.
If you have the linux or IT general "mindset", then you'll get on with most of the stuff suggested.
If you're like me, i.e. don't have the "mindset", or don't come from an IT background of some sort, then you might find the learning curve a little steeper than you might have been led to believe.
I've been doing this "linux thing" for about 3 years or so, and documentation still annoys the hell out of me. I found a few things that seem to start well, but then disappear off into the clouds over my head. The authors seem to forget just how much prior knowledge they have or have forgotten.
The nature of the linux world is such, that they don't even entertain the idea of using a professional proof reader and the author often seems to be blinkered by the constraints of their specific project.
It's not a criticism per se, but programmers and developer aren't professional writers. They tend to write for people with the same or similar levels of knowledge as they themselves have.
"Proper" basic stuff is rare as rocking horse shite!