- Working directory:
~/lecture1 - When the
cdcommand is run with no arguments, the directory is changed to the home directory (~), as seen in the prompt on the next line. - This is not an error.
- Working directory:
~/lecture1 - When the
cdcommand is run with a file as an argument, it does not change directory and outputs that the file is not a directory. - This is an error because
cdrequires a directory to change to, not a file.
- Working directory:
~ - When the
cdcommand is run with a directory as an argument, it changes the directory to the given directory. - This is not an error.
- Working directory:
~ - When the
lscommand is run with no arguments, it outputs the contents of the current working directory. - This is not an error.
- Working directory:
~ - When the
lscommand is run with a file as an argument, it outputs the path of the file. - This is not an error.
- Working directory:
~ - When the
lscommand is run with a directory as an argument, it outputs the contents of the given directory. - This is not an error.
- Working directory:
~ - When the
catcommand is run with no args, it seems like it does nothing. But the prompt is gone.
- We notice that we can actually type in the command, and when we give some input, it echoes it back! We see that the command has not completed and allows us to keep giving input and receiving output.
- We can return to the prompt by aborting the command using
^C(control C).
- In summary, the
catcommand, when run with no arguments, just outputs the input until it is aborted. - This is an error because the user most likely does not want to output the input.
- Working directory:
~ - When the
catcommand is run with a file as an argument, it outputs the contents of the given file. - This is not an error.
- Working directory:
~ - When the
catcommand is run with a directory as an argument, it outputs that the path is a directory. - This is an error because this command is used to output the contents of one or multiple files concatenated together and not directories.
