How to Compare Sorted Files Line-by-Line Using the comm Command in Linux

When you are managing a massive Linux database migration and you have two giant text files containing thousands of email addresses, you often need to execute a highly specific data intersection. You do not just want to know if the files are different; you need to mathematically extract exactly which email addresses exist in both files simultaneously, or which addresses exist only in file one. To force the Linux kernel to execute this complex structural comparison and output a perfectly formatted three-column report, you must use the comm command.

Executing a Three-Column Intersection

The comm (Compare) command is a highly aggressive forensic engine. It loads two text files into memory and executes a strict, line-by-line mathematical comparison.

CRITICAL WARNING: The comm engine is mathematically flawed by design: it absolutely requires both files to be perfectly alphabetically sorted before it can execute the comparison. If the files are chaotic, the engine will violently crash and output corrupted data. You must use the sort command on both files first.

Assume you have two perfectly sorted files: list_A.txt and list_B.txt.

comm list_A.txt list_B.txt

The exact millisecond you press Enter, the engine rips through the code and outputs a highly structured, three-column matrix directly to your screen:

• Column 1 (Far Left): Lines that exist strictly and uniquely in File A.
• Column 2 (Middle): Lines that exist strictly and uniquely in File B.
• Column 3 (Far Right): Lines that exist perfectly in BOTH File A and File B.

Suppressing Specific Columns

The raw three-column output is visually chaotic if the files contain 10,000 lines. The true power of the comm engine is its ability to mathematically suppress specific columns, allowing you to extract exact data sets.

You achieve this by injecting numerical flags (1, 2, or 3) into the command. The numbers instruct the engine which columns to hide.

If you only want to see the lines that are common to BOTH files (Column 3), you must instruct the engine to suppress Column 1 and Column 2.

comm -12 list_A.txt list_B.txt

The engine instantly executes the massive comparison, violently deletes the unique data from both lists, and outputs a perfectly clean, single-column list containing only the data points that perfectly overlap.

If you want to see exactly which email addresses are missing from the second list, you suppress Column 2 and Column 3:

comm -23 list_A.txt list_B.txt

The engine instantly outputs only the unique data from File A.