Novell LINUX ENTERPRISE DESKTOP 10 SP2 - DEPLOYMENT GUIDE 08-05-2008 Deployment Manual page 381

Table of Contents

Advertisement

to this file. Other permissions can be assigned by means of ACLs (access control
lists).
Directory Permissions
Access permissions for directories have the type d. For directories, the individual
permissions have a slightly different meaning.
Example 15.2 Sample Output Showing Directory Permissions
drwxrwxr-x 1 tux project3 35 Jun 21 15:15
In
Example 15.2, "Sample Output Showing Directory Permissions"
owner (tux) and the owning group (project3) of the directory ProjectData
are easy to recognize. In contrast to the file access permissions from
(page 364), the set reading permission (r) means that the contents of the directory
can be shown. The write permission (w) means that new files can be created. The
executable permission (x) means that the user can change to this directory. In the
above example, the user tux as well as the members of the group project3 can
change to the ProjectData directory (x), view the contents (r), and add or
delete files (w). The rest of the users, on the other hand, are given less access. They
may enter the directory (x) and browse through it (r), but not insert any new files
(w).
15.2.2 Modifying File Permissions
Changing Access Permissions
The access permissions of a file or directory can be changed by the owner and, of
course, by root with the command chmod followed by the parameters changing
the permissions and one or more filenames. The parameters form different cate-
gories:
1. Users concerned
• u (user)—owner of the file
• g (group)—group that owns the file
• o (others)—additional users (if no parameter is given, the changes apply to all
categories)
ProjectData
(page 365), the
File Access
Working with the Shell
365

Advertisement

Table of Contents
loading

This manual is also suitable for:

Linux enterprise desktop 10 sp2

Table of Contents