Octal Number System (Base-8) Explained: Why Linux File Permissions Use It

This article serves as a comprehensive guide and decision-support content for the Base Converter tool.

Table of Contents

• 1. The Foundation of Security in Unix and Linux Systems
• 2. The Tripartite Structure of File Permissions: Read, Write, Execute
• 3. Why is Base-8 (The Octal System) Used?
• 4. Conversion Logic from Octal to Binary and Decimal Systems
• 5. Common Chmod Usage and Permission Calculation Scenarios

---

1. The Foundation of Security in Unix and Linux Systems

A massive portion of the world's web servers, smartphones (Android), and cloud infrastructures run on Unix/Linux-based operating systems. The multi-user architecture of these systems demands high security. The rules determining "who can read, modify, or execute" every file and folder on the system are strictly enforced.

When a new Linux user or web developer sees commands like chmod 755 file.txt or chmod 644 index.html in the terminal, they often act by rote memorization. The numbers "755" or "644" here are actually not decimal (base-10), but octal (base-8) numbers. The Linux file permissions mechanism is the most common and well-known example of the octal number system actively used in the IT world today.

2. The Tripartite Structure of File Permissions: Read, Write, Execute

In the Linux operating system, permissions are built upon three fundamental actions:

• Read (r): Viewing the file contents.
• Write (w): Modifying or deleting the file contents.
• Execute (x): Running the file as a program or script.

The system defines these three actions separately for three different user groups:

1. User (u - Owner): The primary user who created the file.
2. Group (g): Members of the user group the file belongs to.
3. Others (o): Everyone else connected to the system (public access).

When you check a file's permissions using the ls -l command, you'll see a character string resembling this:
-rwxr-xr--

Breaking down this sequence:

• The first character (-) indicates that this is a regular file (if it were a directory, it would be d).
• The next 3 characters (rwx): The owner (User) can read, write, and execute.
• The next 3 characters (r-x): The Group can read and execute, but cannot write.
• The final 3 characters (r--): Others can only read.

3. Why is Base-8 (The Octal System) Used?

The underlying logic of these permissions is actually based on the binary system. To the operating system, each permission (r, w, x) is a single bit. If the permission is granted, it holds a "1"; if denied (represented by -), it holds a "0".

Converting the owner permissions (rwx) to binary: 1, 1, 1 -> 111
Converting group permissions (r-x) to binary: 1, 0, 1 -> 101
Converting others permissions (r--) to binary: 1, 0, 0 -> 100

Now, let's look at the resulting 9-bit string: 111101100. Memorizing this string is very difficult for humans. This is precisely why system administrators use the Octal (base-8) number system.

The octal system operates in base-8 (digits 0-7). The greatest advantage of the octal system is that exactly 3 binary bits (representing 8 states from 000 to 111) map perfectly to a single octal digit!

4. Conversion Logic from Octal to Binary and Decimal Systems

The math for converting from binary to octal (base-2 to base-8), in groups of 3 bits, works as follows:
The bit values are $ 2^2=4 $, $ 2^1=2 $, and $ 2^0=1 $ respectively.

• Read (r): 100 (Binary) = 4 (Octal)
• Write (w): 010 (Binary) = 2 (Octal)
• Execute (x): 001 (Binary) = 1 (Octal)

If you want to grant a user read, write, and execute permissions, the corresponding bits are set to 1:
111 (Binary) = 4 + 2 + 1 = 7 (Octal)

If you want to grant a user only read and execute permissions:
101 (Binary) = 4 + 0 + 1 = 5 (Octal)

The command equivalent of our previous rwxr-xr-- example is calculated like this:

• User (rwx) -> 4+2+1 = 7
• Group (r-x) -> 4+0+1 = 5
• Others (r--) -> 4+0+0 = 4

Conclusion: The command to assign these permissions is chmod 754 filename.

5. Common Chmod Usage and Permission Calculation Scenarios

Standard permission templates are frequently used on Linux systems and web servers (e.g., Apache, Nginx). Understanding their octal logic is essential to prevent security vulnerabilities.

Why is chmod 777 Dangerous?

7 (4+2+1) means full permissions. 777 means anyone on the system can read, modify, and execute the file. On a web server, this is a massive security flaw, allowing an external attacker to upload a malicious script (write) and run it on the server (execute).

chmod 644 - Standard File Permissions

This is typically used for HTML, CSS, or image files on web servers.

• 6 (4+2) = Owner can read and write (update the file).
• 4 = Group can only read.
• 4 = Others (site visitors) can only read (they can view the file, but cannot change it).

chmod 755 - Standard Directory and Script Permissions

To enter folders (directories) on your website, "execute (x)" permission is required.

• 7 = Owner reads, writes, and enters the directory.
• 5 (4+1) = Group and others read the contents and enter the directory, but cannot create files inside it.

For secure system administration, rather than rote memorization, mastering the foundational principles of number bases and bit operations puts any SysAdmin a step ahead.

---

Convert System Permissions Quickly

To clearly see or calculate the base-2 (Binary) and base-10 (Decimal) equivalents behind the octal permission codes you use in terminal commands, you can rely on our Base Converter tool.