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.
If you edit your file (remove the hash-bang) and make it like this:
if [ `jobs|wc -l` = 0 ]
echo 'There are no jobs'
echo 'There are some jobs'
And parse it:
$ ls -l example
-rw-r----- 1 druuna internet 137 May 2 16:07 example
$ . example
There are no jobs
As you can see the file doesn't even need execute permissions. Do mind the space between the dot and the filename.
The major difference between parsing and executing a file is the way the shell is used. Parsing is done in the shell you are in, while executing will start a new shell and runs the program in the new shell.
If I remove the #!/bin/bash from my code, will that allow it to run in the current shell?
No, the prefix is unrelated, it's the way you launch the script that matters.
I tried it with it and without, with same results.
Indeed, the #! prefix is only used when the script is executed by the O/S as an executable program to tell what command interpreter to use.
When you run it with the shell "." command, the whole first line is ignored as it starts with "#" which is the comment prefix.