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.
When Linux was first written, ksh (ksh88 ?) was still a closed src program, so they went with bash; highly ksh compatible (work-alike), but open src & free.
You could get pdksh (public domain ksh rewrite) but it wasn't that popular for obvious reasons.
Later on, ksh (ksh93 iirc) became open, but by that pt the default was bash.
Your choice as to which you use, but getting used to bash is prob a good idea. As I say, the 2 are very close in functionality. The main problem in porting scripts is external cmds/progs like find, which the GNU team have extended with extra options and in some cases altered. See the -maxdepth/-prune options between old school find and the gnu version.
If you are using Centos, just the std install, the ksh should be the one from the repos and should work. It's possible that your login entry in /etc/passwd still says bash, not ksh.
Just FYI, as with ksh = .profile & .kshrc, the equiv files for bash are .bash_profile & .bashrc, although bash would (should ?) run .profile if no .bash_profile exists, iirc.