Izzo wrote:Y'know....the funny thing my instructor in class suggests that I need to learn to do things manually in order to truly understand how things work ...which I can see but in a nutshell he contradicts your statement ...and to be honest I believe you more than I do him.
Not constradictory really - I would agree in general. I was just pointing out that learning how package managers work is not a waste of time. I was suggesting RPM for your web browser as that is a critical piece for learning - getting updates, reading articles, etc. If you are planning on managing webservers, I would suggest you learn how to roll your own first.
Learn how it works nuts n bolts first, then learn how to automate. Makes perfect sense to me.
To clarify, if you are applying for a job as a linux admin and you don't know server mgmt tools (mgmt, deployment, automation in general), they may pass you over. Can you do all those tasks through scripting? Of course, but it would take all your time to write and maintain those scripts. You can't deploy FF manually to 100 desktops...when it comes to troubleshooting, you need to know how to do things manually.
Hackers (classic definition) tend to use bubble gum (trial n error) which can leave a system less than clean - analogy is having a bunch of unused crap in the windows registry.
In the business world you want consistency, in reasearch/dev you want creativity. All depends on where you want to go with your experience.
Stick with what your instructor says - s/he is writing your report card
