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.
But according to the rules [a-z] and [A-Z] are completely different. Moreover as I said file names ending in 'a' are not shown but those ending in 'b-z' are shown. If A-Z is expanded as aAbB...zZ then it should show file names ending with 'a' also.
I know this is not a bug ....but then why does this happen?
I cannot reproduce that behaviour; the only valid explanation
for this is my directory-theory. I really can't imagine that they
would have introduced a bug like this in recent versions of
ls and/or bash w/o a major repercussion.
I guess there might be some issue with my system settings.
I tried setting LC_ALL to 'C' and I was even unable to create files having uppercase characters in their names.
My LANG variable is set to en_IN.
It will be interesting for me to get into this as a newbie
Well, I am not an expert in this fields, but recent linux distributions follow table 1 of the standard ISO 14651 "International string ordering and comparison". The collating sequence is defined following this standard and it affects not only sorting but character ranges in some regular expressions.
Apart language settings and collating sequences, a more simple explanation of this behaviour is given by the Advanced Bash Scripting Guide:
As of version 2.05 of Bash, filename globbing no longer distinguishes between
lowercase and uppercase letters in a character range between brackets. For example, ls
[A−M]* would match both File1.txt and file1.txt. To revert to the
customary behavior of bracket matching, set LC_COLLATE to C by an export
LC_COLLATE=C in /etc/profile and/or ~/.bashrc.