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 would not agree with the opinion regarding "bash."
Linux/Unix environments give you many scripting tools to choose from: Perl, PHP, Python, Ruby, awk, and many more. All of them can be used to create scripts, because when you execute any command, the shell looks for "#!commandprocessor" (called 'shebang') in the first few characters of the command file. It then invokes the appropriate command-processor.
Realistically speaking, you're going to encounter many different scripting tools in-use, and you're simply going to have to surf the Internet to find out more about each of them. You won't be able to "become an expert" on all of them, but you will need to acquire an awareness of what's going on.
I don't think that you can simply expect to "go to school on it," nor to find "training." The subject is too broad. You need to master self-education. You are going to constantly be confronted with "things that you have never exactly seen before," and you need to master the survival-skill of "always landing on your feet, no matter what."
Guys, bash (bourne again shell). If you are going to script in 'bash' then you had better learn the shell.
Generally speaking a GNU/Linux distribution uses scripting in some form to configure, install or just plain maintain the install. Most admins find the use of scripting initially to perform a required task(s) then if speed becomes a factor then a higher level language is then used to formulate the task(s). Yes, assembly is still used by some but the portability isn't what a 'C/C+' or the like would be.
So for the OP to learn scripting with 'bash' would open doors to most modern GNU/Linux distributions.