From 39366733c3fe943363566756e2e152c45a1b3cb2 Mon Sep 17 00:00:00 2001 From: Patrick J Volkerding Date: Fri, 25 May 2018 23:29:36 +0000 Subject: Fri May 25 23:29:36 UTC 2018 patches/packages/glibc-zoneinfo-2018e-noarch-2_slack14.2.txz: Rebuilt. Handle removal of US/Pacific-New timezone. If we see that the machine is using this, it will be automatically switched to US/Pacific. --- slackbook/html/filesystem-structure.html | 168 ------------------------------- 1 file changed, 168 deletions(-) delete mode 100644 slackbook/html/filesystem-structure.html (limited to 'slackbook/html/filesystem-structure.html') diff --git a/slackbook/html/filesystem-structure.html b/slackbook/html/filesystem-structure.html deleted file mode 100644 index 843c07c5d..000000000 --- a/slackbook/html/filesystem-structure.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - -Filesystem Structure - - - - - - - - - - -
-

Chapter 9 Filesystem -Structure

- -
-
-
Table of Contents
- -
9.1 Ownership
- -
9.2 Permissions
- -
9.3 Links
- -
9.4 Mounting Devices
- -
9.5 NFS Mounts
-
-
- -

We have already discussed the directory structure in Slackware Linux. By this point, -you should be able to find files and directories that you need. But there is more to the -filesystem than just the directory structure.

- -

Linux is a multiuser operating system. Every aspect of the system is multiuser, even -the filesystem. The system stores information like who owns a file and who can read it. -There are other unique parts about the filesystems, such as links and NFS mounts. This -section explains these, as well as the multiuser aspects of the filesystem.

- -
-

9.1 Ownership

- -

The filesystem stores ownership information for each file and directory on the system. -This includes what user and group own a particular file. The easiest way to see this -information is with the ls command:

- - - - - -
-
-% ls -l /usr/bin/wc
--rwxr-xr-x   1 root     bin    7368 Jul 30  1999 /usr/bin/wc
-
-
- -

We are interested in the third and fourth columns. These contain the username and -group name that owns this file. We see that the user “root” and the group “bin” own this file.

- -

We can easily change the file owners with the chown(1) (which -means “change owner”) and chgrp(1) (which means -“change group”) commands. To change the file owner to daemon, we would use chown:

- - - - - -
-
-# chown daemon /usr/bin/wc
-
-
- -

To change the group owner to “root”, we would -use chgrp:

- - - - - -
-
-# chgrp root /usr/bin/wc
-
-
- -

We can also use chown to specify the user and group owners -for a file:

- - - - - -
-
-# chown daemon:root /usr/bin/wc
-
-
- -

In the above example, the user could have used a period instead of a colon. The result -would have been the same; however, the colon is considered better form. Use of the period -is deprecated and may be removed from future versions of chown -to allow usernames with periods in them. These usernames tend to be very popular with -Windows Exchange Servers and are encountered most commonly in email addresses such as: -mr.jones@example.com. In slackware, administrators are advised -to stay away from such usernames because some scripts still use the period to indicate -the user and group of a file or directory. In our example, chmod -would interpret mr.jones as user “mr” and group -“jones”.

- -

File ownership is a very important part of using a Linux system, even if you are the -only user. You sometimes need to fix ownerships on files and device nodes.

-
-
- - - - - -- cgit v1.2.3