find by name, type, and size in Linux CLI - Step-by-Step Execution

Concept Flow - find by name, type, and size

Start: User runs find command

↓

Parse options: name, type, size

↓

Search directory tree

↓

Check each file/directory

↓

Match name?

↓

All conditions met?

Yes↓

Print file path

↓

Continue until all files checked

↓

End

The find command checks each file in the directory tree against name, type, and size filters, printing paths that match all conditions.

Execution Sample

Linux CLI

find . -name "*.txt" -type f -size +1k

Find all regular files ending with .txt larger than 1 kilobyte in the current directory and subdirectories.

Execution Table

Step	File Checked	Name Matches	Type Matches	Size Matches	Print Path?
1	./notes.txt	Yes (*.txt)	Yes (file)	No (500 bytes)	No
2	./report.txt	Yes (*.txt)	Yes (file)	Yes (2k)	Yes
3	./image.png	No (*.txt)	Yes (file)	Yes (5k)	No
4	./docs	No (*.txt)	No (directory)	N/A	No
5	./docs/manual.txt	Yes (*.txt)	Yes (file)	Yes (3k)	Yes
6	./script.sh	No (*.txt)	Yes (file)	Yes (1.5k)	No
7	./archive.zip	No (*.txt)	Yes (file)	Yes (10k)	No
Exit	All files checked	-	-	-	Stop searching

💡 All files in the directory tree have been checked against the conditions.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	After 6	After 7	Final
Current File	None	./notes.txt	./report.txt	./image.png	./docs	./docs/manual.txt	./script.sh	./archive.zip	All checked
Name Match	N/A	Yes	Yes	No	No	Yes	No	No	N/A
Type Match	N/A	Yes	Yes	Yes	No	Yes	Yes	Yes	N/A
Size Match	N/A	No	Yes	Yes	N/A	Yes	Yes	Yes	N/A
Print Path	N/A	No	Yes	No	No	Yes	No	No	N/A

Key Moments - 3 Insights

Why does the file './notes.txt' not get printed even though its name and type match?

Because its size is 500 bytes, which does not meet the condition '-size +1k' (greater than 1 kilobyte), as shown in execution_table row 1.

Why is the directory './docs' not printed even if it contains matching files?

Because the '-type f' option filters only regular files, so directories like './docs' are skipped, as seen in execution_table row 4.

What happens if a file matches name and size but not type?

It will not be printed because all conditions must be met; type mismatch causes rejection, as shown in execution_table row 3.

Visual Quiz - 3 Questions

Look at the execution table, which file is the first to be printed?

A ./notes.txt

B ./image.png

C ./report.txt

D ./docs/manual.txt

💡 Hint

Check the 'Print Path?' column for the first 'Yes' value.

At which step does the condition '-size +1k' first become true?

A Step 1

B Step 2

C Step 4

D Step 6

💡 Hint

Look at the 'Size Matches' column in the execution_table.

If the '-type f' option was removed, which file would then be printed at step 4?

A ./docs

B ./image.png

C ./script.sh

D ./archive.zip

💡 Hint

Step 4 is './docs' which is a directory; without '-type f', directories can match.

Concept Snapshot

find [path] -name "pattern" -type [f/d] -size [+/-]size
- Searches files/directories recursively
- Filters by name (wildcards), type (file or directory), and size
- Prints paths matching all conditions
- Size +1k means larger than 1 kilobyte
- Use '.' for current directory

Full Transcript

The 'find' command searches through directories and files starting from a given path. It checks each item against conditions like name pattern, type (file or directory), and size. Only items matching all conditions are printed. For example, 'find . -name "*.txt" -type f -size +1k' finds all regular files ending with .txt larger than 1 kilobyte in the current directory and its subdirectories. The execution table shows step-by-step how each file is checked and whether it matches each condition. Variables track the current file and match results. Key moments clarify why some files are not printed despite partial matches. The visual quiz tests understanding of the matching process and conditions. This helps beginners see how 'find' works in practice.