This is the second blog post in a series of articles about using the CCEB cluster. An overview of the series is available here. This post focuses on basics of command line.
Most people use the terms folder and directory interchangeably. From a programmers point of view though there is a slight distinction. A directory is file organization system while a folder is the graphical user interface that is used to represent a directory. For example, on both Mac and Windows operating systems the visual representation of a directory that most users interact with is a folder.
When working through the command line, there is not a visual interface and the user manually codes functions and paths rather than navigating through directories. In this case, you are working with directories. Since we are discussing the command line in this post, I’ll use the terminology directory rather than folder but in reality both are commonly accepted terms.
The command line is a text interface to pass certain functions to the computer’s operating system. Nowadays, users rarely use the command line and instead interact with the computer using a graphical interface and menu-driven interactions or commands. Anything that can be done with the typical point and click graphical interface has a manual function that can be passed through the command line to execute the same task. The command line can be intimidating at first especially for users that are used to doing everything with a graphical interface but it is not different than any other programming language. There is a learning curve but luckily the command line is a very intuitive language.
You can use command line on your computer and on the cluster. As a Mac user, the Terminal app comes standard and can be used to pass the commands. I’ve been using Mac for 10+ years so I’ve actually never used the command line on a Windows. If you’re a Windows users you should Google the Terminal equivalent for your PC.
To use the cluster, you’ll need to be somewhat familiar with command line both on your machine and on the cluster. The command line is how you will request nodes and submit jobs. The cluster is a Unix machine so file paths should use ‘/’.
The most important commands, in my opinion, are shown below:
cdis used to change the current working directory. You can use .. to move back a directory. Adding backslashes will move you back multiple directories (i.e. ../..).
lslists computer files in a directory.
pwdreports the full path name to the current working directory.
mvmoves files or directories from one location to another.
cpcopies files or directories from one location to another.
mansummons the manual for almost all command line commands.
mkdircreates a directory.
rmdirremoves a directory.
rmremoves files or a directory.
clearclears the screen/command board in Terminal.
*pattern*uses all files with the pattern indicated in the command applied.
touchcreates an empty text file.
Warning: Be very careful using the rm command. Using the rm command can wipe out entire directories full of files. For example,
rm -rf/ remove (rm) - recursive (r) force (f) home (/). That is, the
rm -rf/ command will delete every directory, file, and sub-directory within your operating system. It is the equivalent of wiping your entire hard drive clean. The cluster will not let you remove directories that you do not have permissions for. For example, I cannot wipe out another students dissertation directory because I do not have permissions to their directory.
See what working directory you’re currently in:
Change the working directory from the current ‘/Users/alval’ to ‘/Users/alval/Box’:
See what working directory you are currently in:
List the objects in the current working directory:
Make a directory ‘test’ inside of ‘Box’ then list the objects in ‘Box’:
notice that ‘test’ is now a directory in ‘Box’.
Move the ‘test’ directory to ‘/Users/alval/Box/Teaching’ then list the objects in the ‘Box’ and ‘Teaching’ directories:
notice ‘test’ is no longer in ‘Box’ and has been moved to ‘Teaching’. Because we moved the object rather than copy (
cp) the original will no longer be in ‘Box’.
Let’s change the working directory to ‘test’ and list the files:
Notice the ‘test’ directory is empty so nothing is returned.
The next set of code creates three empty text files (‘file1.txt’, ‘file2.txt’, ‘dummy.txt’), and then lists the newly created objects in ‘test’.
Notice ‘file1.txt’, ‘file2.txt’, ‘dummy.txt’ are now listed as files in ‘test’.
Remove the files with ‘file’ in their name and then list the remaining objects in ‘test’:
notice in the next screenshot that ‘file1.txt’ and ‘file2.txt’ were removed but ‘dummy.txt’ remains. This is because only objects with ‘file’ are removed.
Now we set the working directory back to ‘Teaching’ and remove the ‘test’ directory:
notice that ‘test’ is no longer in ‘Teaching’ since it was deleted.
For more information here is a very basic youtube video.
The commands and examples provided here just scratch the surface of what the command line can do. The command line is a computing language so you can write functions and loops or download packages. For example, though GitHub now has a visual studio I personally prefer to use the command line functionality. I find it faster to execute and easier to manage. Like any language, the more you use it the more comfortable you’ll get. It amazes me how much time I save myself organizing files and directories using the command line rather than the graphical folder interface.
At the minimum you’ll need to be comfortable with the command line to get onto the cluster, move around directories, submit jobs, and check jobs.