{"id":204,"date":"2018-09-28T02:38:00","date_gmt":"2018-09-27T18:38:00","guid":{"rendered":"https:\/\/yeslq.com\/201809204.html"},"modified":"2019-05-07T10:40:51","modified_gmt":"2019-05-07T02:40:51","slug":"the-linux-command-line-navigation-2","status":"publish","type":"post","link":"https:\/\/yeslq.com\/?p=204","title":{"rendered":"The Linux Command Line—Navigation"},"content":{"rendered":"

\nThe Linux Command Line <\/a><\/i>by William Shotts<\/span><\/h1>\n

\nNavigation<\/span><\/h1>\n
\nIn this lesson, I will introduce your first three commands: pwd<\/a> (print working directory), cd<\/a> (change directory), and ls<\/a> (list files and directories).<\/div>\n
\nIf you have not worked with a command line interface before, you will need to pay close attention to this lesson, since the concepts will take some getting used to.<\/div>\n

\nFile System Organization<\/span><\/h2>\n
\nLike that legacy operating system, the files on a Linux system are arranged in what is called a hierarchical directory structure<\/i>. This means that they are organized in a tree-like pattern of directories<\/i> (called folders in other systems), which may contain files and other directories. The first directory in the file system is called the root directory<\/i>. The root directory contains files and subdirectories, which contain more files and subdirectories and so on and so on.<\/div>\n
\n<\/div>\n
\nMost graphical environments today include a file manager program to view and manipulate the contents of the file system. Often you will see the file system represented like this:
<\/a><\/div>\n
\nOne important difference between the legacy operating system and Unix-like operating systems such as Linux is that Linux does not employ the concept of drive letters. While drive letters split the file system into a series of different trees (one for each drive), Linux always has a single tree. Different storage devices may contain different branches of the tree, but there is always a single tree.<\/div>\n

\npwd<\/span><\/h2>\n
\nSince a command line interface cannot provide graphic pictures of the file system structure, it must have a different way of representing it. Think of the file system tree as a maze, and you are standing in it. At any given moment, you are located in a single directory. Inside that directory, you can see its files and the pathway to its parent directory<\/i> and the pathways to the subdirectories of the directory in which you are standing.<\/div>\n
\nThe directory you are standing in is called the working directory<\/i>. To find the name of the working directory, use the pwd command.<\/div>\n
\n[me@linuxbox me]$ pwd
\/home\/me<\/div>\n
\nWhen you first log on to a Linux system, the working directory is set to your home directory<\/i>. This is where you put your files. On most systems, your home directory will be called \/home\/your_user_name, but it can be anything according to the whims of the system administrator.<\/div>\n
\nTo list the files in the working directory, use the ls command.<\/div>\n
\n
[me@linuxbox me]$ ls\nDesktop     Xrootenv.0    linuxcmd\nGNUstep     bin           nedit.rpm\nGUILG00.GZ  hitni123.jpg  nsmail\n<\/pre>\n<\/div>\n
\nI will come back to ls in the next lesson. There are a lot of fun things you can do with it, but I have to talk about pathnames and directories a bit first.<\/div>\n
\ncd<\/span><\/h2>\n
\nTo change your working directory (where you are standing in the maze) you use the cd command. To do this, type cd followed by the pathname<\/i> of the desired working directory. A pathname is the route you take along the branches of the tree to get to the directory you want. Pathnames can be specified in one of two different ways; absolute pathnames<\/i> or relative pathnames<\/i>. Let’s look with absolute pathnames first.<\/div>\n
\nAn absolute pathname begins with the root directory and follows the tree branch by branch until the path to the desired directory or file is completed. For example, there is a directory on your system in which most programs are installed. The pathname of the directory is \/usr\/bin. This means from the root directory (represented by the leading slash in the pathname) there is a directory called “usr” which contains a directory called “bin”.<\/div>\n
\nLet’s try this out:<\/div>\n
\n
[me@linuxbox me]$ cd \/usr\/bin\n[me@linuxbox bin]$ pwd\n\/usr\/bin\n[me@linuxbox bin]$ ls\n[                     lwp-request\n2to3                  lwp-rget\n2to3-2.6              lxterm\na2p                   lz\naalib-config          lzcat\naconnect              lzma\nacpi_fakekey          lzmadec\nacpi_listen           lzmainfo\nadd-apt-repository    m17n-db\naddpart               magnifier\n\nand many more...\n<\/pre>\n<\/div>\n
\nNow we can see that we have changed the current working directory to \/usr\/bin and that it is full of files. Notice how your prompt has changed? As a convenience, it is usually set up to display the name of the working directory.<\/div>\n
\nWhere an absolute pathname starts from the root directory and leads to its destination, a relative pathname starts from the working directory. To do this, it uses a couple of special notations to represent relative positions in the file system tree. These special notations are “.” (dot) and “..” (dot dot).<\/div>\n
\nThe “.” notation refers to the working directory itself and the “..” notation refers to the working directory’s parent directory. Here is how it works. Let’s change the working directory to \/usr\/bin again:<\/div>\n
\n[me@linuxbox me]$ cd \/usr\/bin
[me@linuxbox bin]$ pwd
\/usr\/bin<\/div>\n
\nO.K., now let’s say that we wanted to change the working directory to the parent of \/usr\/bin which is \/usr. We could do that two different ways. First, with an absolute pathname:<\/div>\n
\n[me@linuxbox bin]$ cd \/usr
[me@linuxbox usr]$ pwd
\/usr<\/div>\n
\nOr, with a relative pathname:<\/div>\n
\n[me@linuxbox bin]$ cd ..
[me@linuxbox usr]$ pwd
\/usr<\/div>\n
\nTwo different methods with identical results. Which one should you use? The one that requires the least typing!<\/div>\n
\nLikewise, we can change the working directory from \/usr to \/usr\/bin in two different ways. First using an absolute pathname:<\/div>\n
\n[me@linuxbox usr]$ cd \/usr\/bin
[me@linuxbox bin]$ pwd
\/usr\/bin<\/div>\n
\nOr, with a relative pathname:<\/div>\n
\n[me@linuxbox usr]$ cd .\/bin
[me@linuxbox bin]$ pwd
\/usr\/bin<\/div>\n
\nNow, there is something important that I must point out here. In almost all cases, you can omit the “.\/”. It is implied. Typing:<\/div>\n
\n[me@linuxbox usr]$ cd bin<\/div>\n
\nwould do the same thing. In general, if you do not specify a pathname to something, the working directory will be assumed. There is one important exception to this, but we won’t get to that for a while.<\/div>\n
\nA Few Shortcuts<\/span><\/h2>\n
\nIf you type cd followed by nothing, cd will change the working directory to your home directory.<\/div>\n
\nA related shortcut is to type cd ~user_name<\/i>. In this case, cd will change the working directory to the home directory of the specified user.<\/div>\n
\nTyping cd – changes the working directory to the previous one.<\/div>\n
\n
\nImportant facts about file names<\/span><\/h2>\n
    \n
  1. File names that begin with a period character are hidden. This only means that ls will not list them unless you say ls -a. When your account was created, several hidden files were placed in your home directory to configure things for your account. Later on we will take a closer look at some of these files to see how you can customize your environment<\/i>. In addition, some applications will place their configuration and settings files in your home directory as hidden files.<\/li>\n
  2. File names in Linux, like Unix, are case sensitive. The file names “File1” and “file1” refer to different files.<\/li>\n
  3. Linux has no concept of a “file extension” like legacy operating systems. You may name files any way you like. However, while Linux itself does not care about file extensions, many application programs do.<\/li>\n
  4. Though Linux supports long file names which may contain embedded spaces and punctuation characters, limit the punctuation characters to period, dash, and underscore. Most importantly, do not embed spaces in file names.<\/strong> If you want to represent spaces between words in a file name, use underscore characters. You will thank yourself later.<\/li>\n<\/ol>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
    The Linux Command Line by William Shotts Navigatio … \u9605\u8bfb\u66f4\u591a<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[51,52,53],"class_list":["post-204","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-linux","tag-shell","tag-the-linux-command-line"],"_links":{"self":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts\/204","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=204"}],"version-history":[{"count":1,"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts\/204\/revisions"}],"predecessor-version":[{"id":299,"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts\/204\/revisions\/299"}],"wp:attachment":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=204"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=204"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=204"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}