Results 1 to 3 of 3
I have a couple years of experience with Linux, Primarily with Fedora 12 and Ubuntu 9.10-10.04.
I am currently a student working for a degree in Computer Network Security, but ...
- 07-06-2010 #1Just Joined!
- Join Date
- Jul 2010
- Posts
- 0
Top 10 Things I should learn
I have a couple years of experience with Linux, Primarily with Fedora 12 and Ubuntu 9.10-10.04.
I am currently a student working for a degree in Computer Network Security, but have been considering leaving window$ behind all together and work towards being a Linux Admin. If there are any Admins on here, could you give me your top 10 lists of things to know inside and out? i just want to get myself as good as i can get before it comes time to find a job.
Thanks
- 07-06-2010 #2
first thing you have to learn is that windows is here to stay, you had better know it. You need to know how Linux interacts with Windows.
second, learn to use the command line. Most things you do will be done remotely, where a GUI won't be accessible. This means learning common commands, how to use man pages, info pages, and `$command --help`.
third, Learn vi. You may prefer emacs, nano, pico, whatever, but whever you go, unix or linux, vi is ALWAYS available.
fourth, learn shell scripting. You'll need to learn sed, awk, how functions work in the shell, how arguments are passed, and general feel for conventions that are common. You don't need to be a guru, but you need to learn how to at least read other people's scripts.
fifth, learn how to use google. I don't just mean learn how to put something in the box and hit search, learn how to find the information you need, what search terms are good, and what are effectively useless.
six, and this goes with 5, learn to read log files. Logs tell you (almost) everything, they just don't tell you in english. Learn how to find useful information in logs, and how to throw them into google.
seven, learn to install applications from source. Learn how to customize instalations, so that you can install them to nonstandard locations, and you can include only the functions you need. Less functions means less possible vulnerabilities, only include what you are going to use or need.
eight, learn to document. Most large linux shops don't have their admins there 24/7, they have an operations team that monitors the apps, and does most of the application restarts, server reboots, stuff like that. Unless you want to be called at 2 AM every night, learn what information is important to them, and how to get it to them. This will probably be learned durring the time that you're in operations ( don't expect your first job to be an admin, it aint gonna happen.)
nine, Learn Redhat Enterprise Linux, and Suse enterprise linux. If you work for a company that uses linux, you're GOING to run into one of these 2. Ubuntu is great for desktop usage, but it's not what companies use. Is it capable? I'm sure it is, but it's not redhat or novell, and names matter.
ten, you may know 20 times what your boss does, but it doesn't matter, he's your boss. You're not at the job to make things work better, you're there for a paycheck. Do whatever he says, and when it blows up, oh well, you were told to do it. (make sure you keep record of everything BTW)
I'm sure there's more, and probably better things to learn, but they are the 10 I thought of.New to the internet, technical forums, or the hacker / open source community??
Read this to learn good posting habits http://www.catb.org/~esr/faqs/smart-questions.html
RHCE for RHEL version 5
RHCT for RHEL version 4
- 07-08-2010 #3
" . . . you're there for a paycheck."
-- meton_magis
Couldn't live with that one! (Which is why I'm self-employed and living off the grid)
For some of us, the question is, "Would you rather be rich or happy," which parallels the question, "Would you rather be happy or right?" (Which is the way it is in this world of pairs of opposites).
In any case, Vaya con Dios! Best wishes in your studies.


Reply With Quote
