1
<?xml version="1.0" encoding="utf-8"?>
2
<page xmlns="http://projectmallard.org/1.0/" type="topic" style="tip" id="user-admin-explain" xml:lang="cs">
5
<link type="guide" xref="user-accounts#privileges"/>
7
<desc>You need admin privileges to change important parts of your system.</desc>
9
<revision pkgversion="3.4.0" date="2012-02-19" status="review"/>
11
<credit type="author">
12
<name>GNOME Documentation Project</name>
13
<email>gnome-doc-list@gnome.org</email>
16
<include xmlns="http://www.w3.org/2001/XInclude" href="legal.xml"/>
18
<mal:credit xmlns:mal="http://projectmallard.org/1.0/" type="translator copyright">
19
<mal:name>Adam Matoušek</mal:name>
20
<mal:email>adamatousek@gmail.com</mal:email>
21
<mal:years>2012</mal:years>
25
<title>How do administrative privileges work?</title>
27
<p>As well as the files that <em>you</em> create, your computer has a number
28
of files which are needed by the system for it to work properly. If these
29
important <em>system files</em> are changed improperly they can cause various
30
things to break, so they are protected from changes by default. Certain
31
applications also modify important parts of the system, and so are also
34
<p>The way that they are protected is by only allowing users with
35
<em>administrative privileges</em> to change the files or use the applications.
36
In day-to-day use, you won't need to change any system files or use these
37
applications, so by default you do not have admin privileges.</p>
39
<p>Sometimes you need to use these applications, so you may be able to
40
temporarily get admin privileges to allow you to make the changes. If an
41
application needs admin privileges, it will ask for your password. For example,
42
if you want to install some new software, the software installer (package
43
manager) will ask for your admin password so it can add the new application to
44
the system. Once it has finished, your admin privileges will be taken away
47
<p>Admin privileges are associated with your user account. Some users are
48
allowed to have admin privileges and some are not. Without admin privileges you
49
will not be able to install software. Some user accounts (for example, the
50
"root" account) have permanent admin privileges. You shouldn't use admin
51
privileges all of the time, because you might accidentally change something
52
you did not intend to (like delete a needed system file, for example).</p>
54
<p>In summary, admin privileges allow you to change important parts of your
55
system when needed, but prevent you from doing it accidentally.</p>
58
<title>What does "super user" mean?</title>
59
<p>A user with admin privileges is sometimes called a <em>super user</em>.
60
This is simply because that user has more privileges than normal users. You
61
might see people discussing things like <cmd>su</cmd> and <cmd>sudo</cmd>;
62
these are programs for temporarily giving you "super user" (admin) privileges.</p>
65
<section id="advantages">
66
<title>Why are admin privileges useful?</title>
67
<p>Requiring users to have admin privileges before important system changes
68
are made is useful because it helps to prevent your system from being broken,
69
intentionally or unintentionally.</p>
70
<p>If you had admin privileges all of the time, you might accidentally change
71
an important file, or run an application which changes something important by
72
mistake. Only getting admin privileges temporarily, when you need them, reduces
73
the risk of these mistakes happening.</p>
74
<p>Only certain trusted users should be allowed to have admin privileges.
75
This prevents other users from messing with the computer and doing things like
76
uninstalling applications that you need, installing applications that you don't
77
want, or changing important files. This is useful from a security standpoint.</p>
added
removed
gnome-help/cs/user-admin-explain.page
