Why use './' in front of filenames?

Sun, 23 Apr 2023 00:00:00 +0000

In Linux (and MS-DOS I guess) the period signifies the current directory, so if I have a file in the current directory called test.txt, I can refer to it as test.txt or ./test.txt

ian@enrico-rider:~$ cat test.txt
test
ian@enrico-rider:~$ cat ./test.txt
test

I mostly see this in references to files in HTML and have often wondered why. Here it is being used in a Udemy course I’m following.

It’s one of those things that’s difficult to Google, so these days my reflex is to ask ChatGPT such questions.

Okay. That makes sense for executable files. If you just type in the name, Linux will look in the current directory, then if not found, in each of the directories in your $PATH variable. But if you add the ./ to the front, it will only look in your current directory. This claim of ChatGPT’s is easily tested, lets try with cat.

ian@enrico-rider:~$ cat test.txt
test
ian@enrico-rider:~$ ./cat test.txt
-bash: ./cat: No such file or directory
ian@enrico-rider:~$ cp /usr/bin/cat cat
ian@enrico-rider:~$ ./cat test.txt
test

So that checks out, but it doesn’t explain the main place I see it - in HTML.

Again, that makes sense. But it still doesn’t answer why the instructor in my course is using it for:

cp /etc/passwd ./users.txt

Lol - I feel this is a real edge case. I can see it being more a problem with the first file rather than the second one. eg.

So, TL:DR; using ‘./’ in front of a filename can be useful when:

executing a shell script in the current directory (to avoid ambiguity with other executable files in your PATH);
when running a command that takes filenames as arguments, and the filename might be confused with an argument;
in HTML to avoid confusion between the directory the current file is in and the root directory of the web server.

Recursively Deleting Files in Linux

Fri, 14 Apr 2023 00:00:00 +0000

I’ve been using this rsync command to backup files from my NAS to a USB drive. The –excludes are to avoid copying over some junk hidden files - some created by MacOS and some by Synology.

sudo rsync -rvit --exclude '*@eaDir*' --exclude '.DS_Store' /volume1/media/ /volumeUSB1/usbshare1-2/media --del

The .DS_Store files seem to be dropped by MacOS every time I view a directory on the NAS from my MacBook. They’re not doing any harm, and they presumably do something handy for the Mac - remembering the view settings for that folder or some such. Nevertheless, they annoy me. It makes sense to not back them up - they don’t serve any useful purpose in that context.

If I wanted to delete them anyway, how would I go about it? They are scattered randomly around, including in sub-directories of sub-directories. Is there some recursive flag I can add to rm to accomplish this?

I found a better solution on AskUbuntu, we can use the find command. This way it’s easy to safely test your filename matching first before you destroy any files.

find . -name ".DS_Store" -type f

-name is clear enough, and the -type f option is just saying to look for files (rather than directories etc). The period at the start is the location, ie, start in the directory above so the current working directory is included. Once you’ve tuned this, you can add -delete to go nuclear.

find . -name ".DS_Store" -type f -delete

Command-Line on blog.iankulin.com

Why use './' in front of filenames?

Recursively Deleting Files in Linux