What additional privileges does the root user have over a standard user in Linux?

closed as too broad by muru, jimmij, Jakuje, taliezin, roaima Jan 9 '16 at 23:28

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 3
    Clearly: "All of them" – Sobrique Jan 9 '16 at 19:52
  • 1
    Sounds like homework to me. – Kira Jan 9 '16 at 20:35
  • 1
    I will add to @Sobrique's excellent answer. None at all, as a normal user can be given every single permission that root has, or just some of them: see unix.stackexchange.com/questions/101263/… – ctrl-alt-delor Jan 9 '16 at 23:16
  • @richard I would counter that such a normal user would no longer (by definition) be a normal user – roaima Jan 9 '16 at 23:27
  • They are not root (therefore by definition normal), and have some extra privileges e.g. open privileged ports. (Unix, traditionally, defines two types of user, root and what we are calling normal ( I do not remember the name ). On a modern system, we can also give some or all of the privileges to a non-root user. ) – ctrl-alt-delor Jan 9 '16 at 23:30

The root user can do pretty much anything that the hardware allows. The root user can write directly to hard drives without going through the filesystem. Root can modify the kernel via modules. The root user can also circumvent any security policy of the system software: he can change ownership of any files, set up privileged ports, write to privileged filesystem locations, gain extra scheduling priority levels, etc. The root user can also spy on any other user in the system.

Regular users can generally only manipulate their own processes and their own filesystem subtrees. They tend to be forbidden from manipulating the system's hardware, security policies, and from meddling with other users' files and processes.

  • 1
    Hello, root can't get around an enforcing sepolicy is some situations, without setenforce 0 – moonbutt74 Jan 9 '16 at 17:30
  • 1
    @moonbutt74 depends if the root is running unconfined. – Jakuje Jan 9 '16 at 22:02
  • @Jakuje , Hi thanks for clarification, I was thinking in terms on Samsung devices Android 5- and on. – moonbutt74 Jan 9 '16 at 23:11

On Unix, users are represented by a number (User ID, or UID). Any user with UID 0 is privileged, normally there is only one called root.

Unix system permissions are more or less represented as permissions (the typical rwx) on files (devices, like disks, are also files for Unix). One of the differences is that root can override any read and write permission.

Another permission area is the manipulating of processes, something usually only the owner of the process (typically whoever started it, unless it is a SUID executable) is allowed to signal a process or attach to it for debugging. Again, root can override this.

Some operations (like powering off or rebooting) explicitly check for root.

Note too that modern security frameworks can be used to limit and grant privileges in a separate, fine-grained form. See this thread for some details on machines with root with no password, open to the whole 'net.


root is the system administrator, and they can do whatever they want to the system, which can lead to data corruption if the account is not used wisely. Since it appears you are new to Linux, I would recommend you not use root until you get more experience with Linux. To access an administrator/root command prompt from a standard users command prompt, type su (I believe most distros support this) and then hit enter.

Beware when using root, as you can really mess up your computer.

  • 1
    I would recomend sudo over su and not doing it until you know what you are doing over both. May be also a virtual machine to play with and brake. – ctrl-alt-delor Jan 9 '16 at 23:18

Not the answer you're looking for? Browse other questions tagged or ask your own question.