I don't think we need to get into the implementation details, but it's a very old command. It stands for "tape archive" and was intended for writing files and folders onto reels of magnetic tape for archiving and backup, or to transport to another machine. It predates networks!
It can represent directory entries, meaning both folders and files, and get the parent/child relationships correct.
I'm not sure what you mean by "priority". They all go in there, in the correct place, so that the data can be reconstructed.
You can do them in the other order, but you'd need to have a second terminal, on your laptop, to do the SCP.
Think of it this way: you can PUSH your file from your laptop to Tempest, but you can't PULL your file onto Tempest from your laptop.
tar turns a directory structure into a single file, which is convenient for saving/archiving/sending.
Gzip compresses a file.
I've listed the commands that are most important. You'll get them by practice.
Gdome, Georgia Dome, is just an example user, like "Wendy Wellesley". Not important to remember.
The ability to "ls" a directory is separate from being able to "cd" into it. They usually go together, but not always.
Great point! The mv
command does double-duty: moving
files to other places that already exist or to other names. I was
puzzled by this when I first learned unix, back when dinosaurs roamed the earth.
The cp
command will allow you to name the copy. So
cp file1 file2
names the copy. Same for folders:
cp -r dir1 dir2
Now, as a feature, if dir2
already exists, CP copies into it, keeping the original name. So you get:
dir1 dir2
It will "beep" and wait for you to choose. You can get a list of the possible continuations by pressing TAB again.
Let's look at that together. If you're still confused, come visit me in office hours!
Historically, the source code was small and open. Thanks to UC Berkeley, many, many people copied unix. But then they wanted to enhance it, so there were variations, and different opinions about how things should work.
Then, Linus Torvalds wanted Unix on his PC, so he created Linux. (Linus=Linus + Unix). Again, open source, so many, many people contributed.
Now there are lots of distributions of Linux, that have different, say, user interfaces (Desktop environments).
No! It's very weird to be able to transfer a file, including its *ownership* to another user. I implemented the "drop" command on our server, using some advanced Unix skills, which I would be happy to describe outside of class.
Yes, though it's not often done. Just separate them with a semicolon. The following does two commands in one:
cd ~/cs304; ls
Yes, for the first assignment, but then, maybe not often. But if you want to drop some code to a partner, a tar file is invaluable.
Great!