The execute permission makes sense for files (which include scripts etc.), but when it comes to directories, the write (w) permission works the same way as execute (x), right?
In the first terminal A, I create a directory, enter the directory, and create a file:
Simple question, but I’m not sure where to look and google doesn’t respond to periods and slashes.
Is there a Unix command to get the absolute (and canonicalized) path from a relative path which may contain symbolic links?
In Bash, suppose I visit a directory, and then another directory. I would like to copy a file from the first directory to the second directory, but without specifying the long pathnames of them. Is it possible?
What would be a good way to move a file type from a directory and all of its sub-directories?
Suppose you have an alias go, but want it to do different things in different directories?
I’ve seen many explanations for why the link count for an empty directory in Unix based OSes is 2 instead of 1. They all say that it’s because of the ‘.’ directory, which every directory has pointing back to itself. I understand why having some concept of ‘.’ is useful for specifying relative paths, but what is gained by implementing it at the filesystem level? Why not just have shells or the system calls that take paths know how to interpret it?
Let’s say user has Directory1 and it contains File1 File2 CantBeDeletedFile
How to make so the user would never be allowed to delete the CantBeDeletedFile?