[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
slackbook:working_with_filesystems [2012/09/09 22:55 (UTC)] – [Using mount] Added original text with formatting mfillpot | slackbook:working_with_filesystems [2012/10/24 09:40 (UTC)] (current) – [Using mount] Fixed a paragraph which was erroneously copied from the previous chapter alienbob | ||
---|---|---|---|
Line 138: | Line 138: | ||
===== Using mount ===== | ===== Using mount ===== | ||
- | Unlike other filesystems | + | Now that we've learned what (some of) the different |
- | partitions hold virtual memory. This is very useful as it prevents | + | available in Linux are, it's time we looked at how to use them. |
- | system from crashing should all your RAM be consumed. Instead, | + | In order to read or write data on a filesystem, that filesystem |
- | kernel copies portions of the RAM into swap and frees them up for other | + | must first be mounted. To do this, we (naturally) use mount(8). |
- | applications | + | The first thing we must do is decide where we want the filesystem |
- | computer, very slow virtual memory. swap is typically a fail-safe and | + | located. Recall that there are no such things are drive letters |
- | shouldn't be relied upon for continual | + | denoting filesystems in Linux. Instead, |
- | if you find yourself using lots of swap. | + | on directories. The base filesystem on which you install Slackware |
+ | is always located at ''/'' | ||
+ | subdirectories of ''/'' | ||
+ | locate a partition, so we' | ||
+ | In order to mount a filesystem' | ||
+ | kind of filesystem we have, where to mount it, and any special | ||
+ | options to use. | ||
+ | |||
+ | < | ||
+ | darkstar:~# mount -t ext3 /dev/hda3 /mnt/hd -o ro | ||
+ | </ | ||
+ | |||
+ | Let's disect this. We have an ext3 filesystem located on the third | ||
+ | partition of the first IDE device, and we've decided to mount its | ||
+ | contents on the directory /mnt/hd. Additionally, | ||
+ | read-only so no changes can be made to these contents. The [-t ext3] | ||
+ | argument tells mount what type of filesystem we are using, in this | ||
+ | case it is ext3. This lets the kernel know which driver to use. | ||
+ | Often mount can determine this for itself, but it never hurts to | ||
+ | explicitly declare it. Second, we tell mount where to locate the | ||
+ | filesystem' | ||
+ | we must decide what options to use if any. These are declared with | ||
+ | the [-o] argument. A short-list | ||
**Table 11.2. Common mount options** | **Table 11.2. Common mount options** | ||
Line 209: | Line 231: | ||
===== Network Filesystems ===== | ===== Network Filesystems ===== | ||
- | In addition to local filesystems, | + | In addition to local filesystems, |
+ | filesystems as both client and server. This allows you to share data | ||
+ | between multiple computers transparently. We'll discuss the two most | ||
+ | common: NFS and SMB. | ||
==== NFS ==== | ==== NFS ==== | ||
- | NFS is the Network File System for Linux as well as several other common operating systems. It has modest performance but supports the full range of permissions for Slackware. In order to use NFS as either a client or a server, you must run the remote procedure call daemon. This is easily accomplished by setting the /// | + | NFS is the Network File System for Linux as well as several other common |
+ | operating systems. It has modest performance but supports the full range of | ||
+ | permissions for Slackware. In order to use NFS as either a client or a | ||
+ | server, you must run the remote procedure call daemon. This is easily | ||
+ | accomplished by setting the '' | ||
+ | executable and telling it to start. Once it has been set executable, it | ||
+ | will run automatically every time you boot into Slackware. | ||
< | < | ||
Line 220: | Line 251: | ||
</ | </ | ||
- | Mounting an NFS share is little different than mounting a local filesystem. Rather than specifying a local device, you must tell mount the domain name or IP address of the NFS server and the directory to mount with a colon between them. | + | |
+ | Mounting an NFS share is little different than mounting a local filesystem. | ||
+ | Rather than specifying a local device, you must tell mount the domain name | ||
+ | or IP address of the NFS server and the directory to mount with a colon | ||
+ | between them. | ||
< | < | ||
Line 226: | Line 262: | ||
</ | </ | ||
- | Running an NFS server is a little bit different. First, you must configure each directory to be exported in the /// | ||
- | <code> | + | Running an NFS server is a little bit different. First, you must configure |
+ | each directory to be exported in the ''/ | ||
+ | file. '' | ||
+ | directories will be shared, who they will be shared with, and what special | ||
+ | permissions to grant or deny. | ||
+ | |||
+ | |||
+ | <file> | ||
# See exports(5) for a description. | # See exports(5) for a description. | ||
# This file contains a list of all directories exported to other computers. | # This file contains a list of all directories exported to other computers. | ||
Line 234: | Line 276: | ||
/ | / | ||
- | </code> | + | </file> |
- | The first column in exports is a list of the files to be exported via NFS. The second column is a list of what systems may access the export along with special permissions. You can specify hosts via domain name, IP address, or netblock address (as I have here). Special permissions are always a parenthetical list. For a complete list, you'll need to read the man page. For now, the only special option that matters is [no_root_squash]. Usually the root user on an NFS client cannot read or write an exported share. Instead, the root user is " | + | The first column in |
+ | '' | ||
+ | is a list of the files to be exported via NFS. The second column is a list | ||
+ | of what systems may access the export along with special permissions. You | ||
+ | can specify hosts via domain name, IP address, or netblock address (as I | ||
+ | have here). Special permissions are always a parenthetical list. For a | ||
+ | complete list, you'll need to read the man page. For now, the only special | ||
+ | option that matters is //no_root_squash//. Usually the root user on | ||
+ | an NFS client cannot read or write an exported share. Instead, the root | ||
+ | user is //" | ||
+ | //no_root_squash// prevents this. | ||
- | You'll also need to run the NFS daemon. Starting and stopping NFS server support is done with the /// | ||
+ | You'll also need to run the NFS daemon. Starting and stopping NFS server | ||
+ | support is done with the ''/ | ||
+ | Set it executable and run it just like we did for | ||
+ | '' | ||
==== SMB ==== | ==== SMB ==== | ||
- | SMB is the Windows network file-sharing protocol. Connecting to SMB shares (commonly called samba shares) is fairly straight forward. Unfortuantely, | + | SMB is the Windows network file-sharing protocol. Connecting to SMB shares |
+ | (commonly called samba shares) is fairly straight forward. Unfortuantely, | ||
+ | SMB isn't as strongly supported as NFS. Still, it offers higher performance | ||
+ | and connectivity with Windows computers. For these reasons, SMB is the most | ||
+ | common network file-sharing protocol deployed on local networks. Exporting | ||
+ | SMB shares from Slackware is done through the samba daemon and configured | ||
+ | in '' | ||
+ | service is beyond the scope of this book. Check online for additional | ||
+ | documentation, | ||
+ | |||
+ | |||
+ | Thankfully mounting an SMB share is easy and works almost exactly like | ||
+ | mounting an NFS share. You must tell mount where to find the server and | ||
+ | what share you wish to access in exactly the same way. Additionally, | ||
+ | must specify a username and password. | ||
- | Thankfully mounting an SMB share is easy and works almost exactly like mounting an NFS share. You must tell mount where to find the server and what share you wish to access in exactly the same way. Additionally, | ||
< | < | ||
Line 250: | Line 319: | ||
</ | </ | ||
- | You may be wondering why the filesystem type is cifs instead of smbfs. In older versions of the Linux kernel, smbfs was used. This has been deprecated in favor of the better performing and more secure general purpose cifs driver. | ||
- | All SMB shares require the [username] and [password] arguments. This can create a security problem if you wish to place your samba share in fstab. You may avoid this problem by using the [credentials] argument. | + | You may be wondering why the filesystem type is cifs instead of smbfs. In |
+ | older versions of the Linux kernel, smbfs was used. This has been | ||
+ | deprecated in favor of the better performing and more secure general | ||
+ | purpose cifs driver. | ||
+ | |||
+ | |||
+ | All SMB shares require the //username// and //password// | ||
+ | arguments. This can create a security problem if you wish to place your | ||
+ | samba share in fstab. You may avoid this problem by using the | ||
+ | //credentials// argument. | ||
+ | which contains the username and password information. As long as this file | ||
+ | is safely guarded and readable only by root, the likelyhood that your | ||
+ | authentication credentials will be compromised is lessened. | ||
< | < | ||
Line 259: | Line 340: | ||
darkstar:~# mount -t cifs // | darkstar:~# mount -t cifs // | ||
</ | </ | ||
+ | |||
+ | ====== Chapter Navigation ====== | ||
+ | |||
+ | **Previous Chapter: [[slackbook: | ||
+ | |||
+ | **Next Chapter: [[slackbook: | ||
====== Sources ====== | ====== Sources ====== | ||
- | * Original source: [[http:// | + | <!-- If you copy information from another source, then specify that source --> |
+ | * Original source: [[http:// | ||
+ | <!-- Authors are allowed to give credit to themselves! --> | ||
+ | * Originally written by Alan Hicks, Chris Lumens, David Cantrell, Logan Johnson | ||
+ | <!-- * Contrbutions by [[wiki: | ||
<!-- Please do not modify anything below, except adding new tags.--> | <!-- Please do not modify anything below, except adding new tags.--> | ||
- | {{tag> | + | <!-- You must also remove the tag-word " |
+ | {{tag> |