2015 LinuxQuestions.org Members Choice AwardsThis forum is for the 2015 LinuxQuestions.org Members Choice Awards.
You can now vote for your favorite products of 2015. This is your chance to be heard! Voting ends on February 10th.
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.
Well, granted, that was a bad bit of code (hardly qualifies as a bug since it was a feature!). In fact, it was more like a well implemented but stupid idea!
But the bash bashing I refer to is not related really to shellshock, but more the frequent references to bash-isms and a kind of shell-snobbery that seems less good humored than say, vi vs emacs snobbery, or Slackware vs everything-else snobbery.
Features unique to bash are called bash-isms with a sneer, whereas features unique to other software are called... unique features.
I like bash. But I've only used anything else for mere MOMENTS, so really have no great amount of experience to go with anything else. But then, since every distro I like defaults to bash, I've never had a HUGE reason to try something else (I figure if it's THAT much better, ONE of the distro's I liked would default to it).
I have tried others many times, but I don't really like the default behaviour of most alternatives. I have many bash scripts and bashisms are really good too, but if I had to go back in time and learn a shell, I'd go probably with ksh, because bash is really too slow.
But still, bash is the best compromise if you want to run the same shell in the terminal and on scripts. zsh is great for interactive mode, but I heard it is not so great for scripts. On the other hand, ksh is a good shell for scripts and way faster than bash, and has some nice features like floating point arithmetic that bash has not, but I tried setting it up for interactive use, and I found it to be really bad!