ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
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 read a white paper a few years back that explained at the time why batch programming should be done in sh (bash). Because in tcsh and ksh, while having perhaps richer instruction sets than plain old sh (bourne shell) the behaviour of some constructs tended to differ slightly between the batch and interactive execution of some scripts. Sh was simple, but considered very safe for batch. Just in case, and while your assembled audience awaits you posting the awk version info.
Many people think that shell scripts should be written for sh, for portability.
OTOH, I learned shell scripting in bash & am not about to give up its richness.
If it ever (doubtful) gets to a point that someone really needs to run something of mine on a system that doesn't have bash,
they have 3 choices:
Many people think that shell scripts should be written for sh, for portability. OTOH, I learned shell scripting in bash & am not about to give up its richness.
ROTFL, that was my stance as well. Then I stepped into this project and I had to unlearn a lot of things to stay compatible... For testing Bourne compatibility on GNU/Linux I use the Heirloom shell. Strict as hell.