Question on learning Linux or on subject of interest.
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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 would say an important point is missing: you should be interested. You will never know linux, it is nonsense, You will know parts of the system, you will be familiar with some tools, techniques (and so on...). You need to understand how they work, how to use them ... But without real interest and willing to know it and master it you will never be an expert.
I've been using Linux for about 10 years (8 of them as my primary operating system). In that time, I've learned by a lot of repetition, if I do it enough times it just kind of sticks. Otherwise, I've gotten pretty good at searching through various help forums- you'll find the ones that are best for you. I tend to like this one best, it's written in a very "newbie friendly" way.
In my day job, I'm an academic and I play with some fancy stats (mostly in R, some Stata) and have recently started programming to manipulate data. I find the best way to learn that is to find a tutorial, download the tutorial data and work through the examples while typing all the code (no copy and paste) and documenting it in my own words. It's a great reference and forces me to learn it.
I'm also a big fan of saving bash scripts of particularly difficult command line problems- that way I can go back and rerun it when I need to do it again six months down the line.
If we need to explore more than one subject of interest , let say Shell scripting, Python , Network security and SSH. (This is my example, and you may have your own curriculum of research/study)
Here we have four subjects. Would you all suggest to complete a topic first before going for the next. Or we could have a go on all the 4 topics? ( I would like to know what's individual take. )
If we go for the 4 topics at a time.. how would you plan to tackle the challenges along the way. ?
I believe there would be stop/pause along the study journey, or you might hit a stubborn hurdle. How would you decide to skip it and ignore it altogether? Or you might try to find a way to encounter it.
Any good strategy in studying of any subject of interest?
If you need a quick n dirty soln right now for some job, the just learn what you can from eg google or LQ and then update when time permits.
Ideally you'd want to do one thing at a time, but that can get tedious.
You could reserve say x hrs per week per subject; enough time per subject to get somewhere, short enough to allow time for the next.
You may need to prioritise to get a needed soln.
Note also that there will be some overlap eg N/W security & ssh go hand-in-hand; its a bash env so you need basics regardless of eg learning Python.
Similarly if you want to automate ssh as opposed to just manual logins...
Thanks Chris, your advise sound great especially on " You could reserve say x hrs per week per subject; enough time per subject to get somewhere, short enough to allow time for the next. You may need to prioritise to get a needed soln."
What i really need right now is the motivation and planning.
Based on my past, even though i plan i didn't carry it out to the full..( i think it's due to lack of faith)
Plan and Do is like a quantum leap. (Leap of Faith).
Anyway, appreciate for all the kind folks here for their time in giving your suggestion and input.