what's the best basic attitude to adopt as a newbie?
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.
what's the best basic attitude to adopt as a newbie?
Hi all. Here's a general question. I'm wondering what you've found the basic general attitude to adopt was when you are a linux newbie.
I still put myself in that catagory, as I've been at it for less than a year now. Not sure when I would or should take myself out of that category.
My situation is that I'm new to linux, but took an intro course in it. I use it every day, as I'm setting up new servers and the like, but when I go home, as I'm married and with a child, I don't find myself in front of the computer much, (unless absolutely needed). I do however, have Fedora 4 set up at home.
I'm responsible for 1 web development server and 1 production server here at work, and since aquiring books is not a problem for me AT ALL, I get books and read up as I deem needed. Right now, I'm reading all about securing apache in the Oreilly title of the same name.
Here's what I'm trying to get at : some understanding of when and where, and how to be cautious with my linux boxes , and more to the point (in the interest of learning deeply), when where and how to be bold and experimental - even occasionally (and temporarily) destructive at times. Case in point, when I just start renaming files and directories at will until the process that I'm targeting breaks. Granted, I have 2 boxes to play with, but I feel like I should have a 3rd box that could actually handle being non-funtional for a while. However, I don't relish the daily duty of manually replicating tasks on both systems just in the name of keeping 2 servers as closely alike as possible. What's good about these 2 systems is that they are both RHEL4, with an update subscription. That makes the updating and synchronization of the servers a breeze from the standpoint of software installs.
I don't want to take forever to learn what might be considered a more advanced level of linux, but at the same time, I don't want to always break things, or comprimise security or functionality in order to do it, either. and on saturday, I'm obligated to clean my house with the rest of the family, rather than spending too much time in front of a moniter and keyboard.
So, I'm looking for a proper balance and order.
Maybe I can learn from your personal experience, and how you found your balance?
Not being an expert on the subject, but having several opinions, and having made some observations in your post i believe you have the basic skills not just for Linux but for anything, you are not afraid to do research, read up on something, test it out etc. these i think are necessary to succeed past an install in Linux.
In terms of your experimenting with it, this is a great thing, but not for production servers, the purpose of your production server and web server is to provide a service with as little downtime as possible. A bleeding edge install for experimentation is a direct conflict with these goals and should be avoided. Your idea of a 3rd box (if feasible?) is the way to go, with a system in place that allows a quick reinstall back to a working state (something like norton ghost etc.).
My attitude as a newbie (and I still am- I only started about half a year ago) was to throw myself into it. Install as many different distros as you can, and play with them, learn your way around, try to read information and find solutions to problems either from documentation or forums. Enjoy it! (If possible/applicable ) Boot LiveCDs, try to install Linux on a tea-cosy, break your system, fix it, then try another and start all over again try to find a distro- or indeeed two or more distros, that suit you best and get to know your way around them.
It helps if you have a spare computer or can dual boot though- a constantly changing environment doesn't lend itself to serious work I'm still about here in the process- I'm unable to have a proper dedicated Linux machine of any real power, but I'm lucky in that I have got a spare old computer that my parents have essentially given me to play around with.
I think that as far as breaking things go it is not a bad thing on a home PC. Granted, anyone can break things but it is how you go forward from there that counts.
I have learned more from fixing things I have broke than anything else. As long as you have averything backed up you shouldn't worry too much.
The first time I installed a distro I was worried about formatting and partitioning my hard drive. I had only ever bought PC's with Windows preinstalled and it was a big thing for me.
Reading is great, but unless you get your hands dirty and use what you learned you forget a lot of it and sometimes didn't understand it correctly to start with.
I consider myself a newbie but I have learned a lot. I think I have gained an understanding of the filesystem, which was alien at first. I now have an idea where most thing are.
I have also recently learned a great deal of shell scripting which I think it is great and I am now starting to automate a lot of stuff. It is great when you realise the opportunities and power this gives you.
Linux now, is cool in that the instalation and GUI makes it possible to achieve desired results with greater ease but still has the power to utilize the more advanced features such as the shell as and when you learn or need them.
My basic attitude when I started was, first, to keep in mind at all times:
"This is not Windows. Don't expect it to be like Windows in any way. This has to be learned completely from beginning to end."
And to learn I attempted one thing at a time and didn't quit until I either solved it or found evidence that it won't work (yet). Don't give up even if it's taking weeks to find an answer. I also didn't use the forums until I exhausted every other resource available. The best way to learn is by discovering the answer on your own.
And finally, from the beginning I've kept a notebook to log how I solved each issue.
Sorry i'm still a newby...and will be for another 15 years..
damm is it that long ago...hmm, must get some memory pills...
nah stuff it, cant remember how to boot it still so maybe after 20 years i might not call myself a newby, then again its probably going to change a bit by then and i'll probably update to the latest so i'll be a newby again...
Well thats linux, never stops changing and you never stop learning...
Not sure when I would or should take myself out of that category.
You get to pass GO and collect $200 when you are answering more questions then you are asking! Making it to this plateau moves you from newbie to the next level IMHO.
Note that I didn't say "You know all the answers", my thought process is more along the lines "You don't always have to ask the questions". i.e., You've developed the skills to help yourself conquer many obstacles you run into (through research, testing, trial and error, etc.) You will always need to ask some questions - that is, if you want to continue learning - but you will start answering more than you ask.
Also remember, you can become a real guru in one area of Linux, and still be a drooling newbie in a different area. e.g., I've been doing some thermal testing on my box and I needed to load down the cpu. I found a big source package and repetitively ran "make; make dist-clean; make; make dist-clean..." While this indeed loaded down the cpu as I required, I just saw a MUCH easier way in some other person's post: "dd if=/dev/urandom of=/dev/null". Duh. Now why didn't I think of that! Always learning...
want to load up a cpu...
install boinc and crunch a heavy project like seti or the likes...
optimize the app to use all available instruction sets...SSE, SSE2, SSE3(pni)...
can crank some of my pc's up by as much as 20 degrees celsius...
and yes they are clean and all have artic silver and larger heatsinks than standard...
intel run hottest tho...
good leg warmers...lol...
Distribution: Ubuntu and whatever is new kid on the block
keep notes, backup, break things, keep notes, backup, break things... ad nauseum.
Get a separate box and a kvm switch so you don't have to move about much but you can play in the sandpit and work your magic on the stable systems.