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'm not an expert, so I can only guess: the same way you become an expert in anything. Practice, read about it and use it. Common sense, really. There's loads of online docs about Linux. Websearch: learning linux.
i learned and practiced linux basic commands..so now what should i do after basic commands?
A big part of being an expert in Linux (and a part I haven't mastered myself) is being an expert in bash scripting.
A lot of bash scripts implement key parts of the system, especially startup. Those parts are among the least documented and the most important to understand on the way to becoming a Linux expert.
Programs coded in C often have detailed documentation of their behavior, because those writing the documentation expect non programmers to need to know that behavior.
But important programs coded in bash typically have no real documentation of their behavior. If you need to understand their behavior you need to be a good enough bash programmer to read the script as if it were "self documenting".
So go through some advanced tutorial in bash scripting, then try to understand some of the scripts involved in startup of your distribution.
Is this just disagreement?
Also the only thing I can find on lemming is rodent.
Anyway I believe that everyone would like to understand what you actually mean as anything stated in forum should be helpful to the OP & others!
Hey, was just kidding. The idea to try commands in a virtual box is good of course. But then you don't have the pressure, the stress than working in a real system where damages are real and lessons taken by heart
What are you interested in? Linux is really good at all sorts of networking related things. You may want to set up a server at home for backup purposes. Or maybe a webserver. Or play around with home automation. A Raspberry Pi is a very affordable option do do any of these things.
If you are more interested in the desktop experience go ahead and try out different distros and / or desktop environments. Customize your distro to a point where it behaves exactly the way you want. Play around with things, break your installation, and repair it again. Once you are comfortable with all the installation and set up tasks, start installing Linux on other people's computers.
Or set up a custom router using e.g. OpenWrt. It's quite interesting to have a Linux install running on your router which you can access through ssh, and it gives you a maximum of flexibility and configurability.
Play around with Debian Live-build to build your own custom iso image and put it on a flash drive for your key ring.
I'm not an expert either, but here are memorable parts of my journey:
Back in the old days of ubuntu, you still had to edit config files via the terminal, in my case specifically it was to add mirrors. I remember how freaked out I was at the terminal following it closely, getting worried when I made a mistake and hit backspace and vi didn't delete the character (or so I thought) so I'd exit and try again. After that incident I learned more about vi/vim and I was more comfortable working with them and using them.
I was afraid of the command line in general, so along with learning vi/vim I got myself a copy of a beginner's guide at TLDP and followed it all the way through. I learned about the filesystem, package managers and just got more comfortable with the command line in general
I also started playing around with distros and a lot of them at the time involved partitioning the filesystem yourself so I eventually got over my fear of cfdisk and was able to partition my drive fine. When I started installing more software I had to follow all sorts of guides and these guides eventually got me use to grep/sed/awk. Lastly, when I started getting interesting in hosting stuff online and having a wordpress blog I got more familiar with logs to find problems.
I'm at the point now that I can get by in most distros, if instructions aren't holding my way all the way through I'm not terribly worried most of the time. With the help on Google I am mostly self sufficient, but every now and again I still need help and I'm sure most people here do too.
as a measurement you can try to solve problems here, at LQ.
This is an excellent suggestion. Trying to help others is a great way to learn. Testing out your proposed answers before you post them will force you to try new stuff.
My suggestion is to pick something you want to do and learn how to do it with Linux. You will learn as you go along. With me, it was self-hosting my website, which I did with Slackware and a lampp stack--I self-hosted for almost five years, until I moved to these parts, where my new ISP is actively hostile to public-facing servers and blocks port 80 (I know there are workarounds, but it wasn't worth the trouble).
In the process of doing that, I learned how to use text editors, simple file and directory navigation commands, and lots of other stuff. It really doesn't matter what it is, as long as it has you using a Linux computer; you will have to learn Linux stuff along the way. Then pick another something, then another something, and so on.