Linux · File Permissions & Ownership

A directory is chmod 000 but root reads and deletes files in it anyway. Why do the permission bits not stop root?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in File Permissions & Ownership

You own a file and want to give it away to another user by changing its owner. Why does chown fail for you?

In the first column of ls -l output you see a leading character like d, l, or c before the rwx bits. What does that character encode, and what are the main codes?

In a line like -rw-r--r-- 1 kofler kofler ..., there is a number right after the ten type-and-permission characters. What does that number mean?

Every Linux file carries an owner, a group, and permission bits. How many permission bits are there, and how are they grouped?

A user has no write bit on a file, yet they delete it anyway. How is that possible?

A file is rw-r--r-- and you want every user on the system to be able to read it too. Using symbolic chmod, what command does that?

Start learning today

Free to start — download the app or use it in your browser.