File exists (ls) but no such file or directory (cd)
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.
I found out that when the subdirectory is only one word such as Ruby instead of Ruby Code, then I can cd to the sub directory. When there is a space in the name apparently I can't, and I get back for cd Ruby Code
-bash: cd: Ruby: No such file or directory
Note that only Ruby is recognized. However when I use ls I get back Ruby Code.
Spaces (in file/dir names etc) are technically legal in *nix, BUT given that nearly all cmds default to assuming params are space separated, you can see that this will cause issues. I always use underscores instead and highly recommend you do something like that.
(BTW, in case you don't already know, *nix is case sensitive, so Ruby != ruby etc)