Operation Manual

FolderFileAccess
Permis-
sion
have execute permission for the
directory, they can nevertheless
access certain les in this directo-
ry if they know of their existence.
Users can create, rename or delete
les in the directory.
Users can change the le: They can
add or drop data and can even delete
Write
(w)
the contents of the le. However, this
does not include the permission to
remove the le completely from the
directory as long as they do not have
write permissions for the directory
where the le is located.
Users can change into the directo-
ry and execute les there. If they
Users can execute the le. This per-
mission is only relevant for les like
Execute
(x)
do not have read access to that di-programs or shell scripts, not for text
rectory they cannot list the lesles. If the operating system can ex-
but can access them nevertheless
if they know of their existence.
ecute the le directly, users do not
need read permission to execute the
le. However, if the le must me in-
terpreted like a shell script or a perl
program, additional read permission
is needed.
Note that access to a certain le is always dependent on the correct combination of access
permissions for the le itself and the directory it is located in.
21.5.3 Modifying File Permissions
In Linux, objects such as les or folder or processes generally belong to the user who
created or initiated them. The group which is associated with a le or a folder depends
on the primary group the user belongs to when creating the object. When you create a
new le or directory, initial access permissions for this object are set according to a
Shell Basics 313