Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
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 wondered the same thing when I first started using linux. Consider the possibility of two commands spelled the same way, with different case. Like run_command and Run_Command. In dos, or dos box in windows, they'd be the same command, but in linux they're not. I could immediately see the freedom it gives the programmer or the casual user, you have a lot more choices for script names, etc.
Linux is case sensitive because 'a' and 'A' are different as far as the OS is concerned. Historically, MS-DOS only used uppercase to represent filenames. In an attempt to allow lowercase while retaining backward compatibility, Windows 95 introduced LFNs (Long File Name) into the FAT filesystem. LFN allowed filenames longer than the MS-DOS 8.3, and in an effort to keep things uncomplicated, made no distinction between upper and lower case letters.
Well, I'll give you a different answer: because case sensitive is simpler and faster to sort. Case insensitive sorting is much slower. I don't know about it being simpler for the user, but luckily the tab key does most of the typing for me.
What I like about case sensitivity is that it enforces consistency. For example, filenames will always be refered to the same way in scripts etc. You will not have ls, LS, lS, Ls, etc.
Also, about the sorting ls will sort case sensitive. This why we usually write README, Makefile instead of readme, makefile in source directories, they all go to the beginning...
LINUX is and was and will be developed using the C Language.
C is case sensitive and case sensitiveness also gives a lot of freedom and extra options.
Hence Linux is and must be case sensitive forever!
Distribution: openSuSE 42.1_64+Tumbleweed-KDE, Mint 17.3
Posts: 4,071
Rep:
Small and capital letters have different ASCII-representations, thus for the system they are not the same. And Unix being a byte stream oriented OS ... DOS/Win has consistently to "to_upper()" any file name related input as their problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.