Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
slackbook:working_with_filesystems [2012/09/09 22:58 (UTC)]
mfillpot [NFS] Added original text with formatting
slackbook:working_with_filesystems [2012/10/24 09:40 (UTC)] (current)
alienbob [Using mount] Fixed a paragraph which was erroneously copied from the previous chapter
Line 138: Line 138:
 ===== Using mount =====  ===== Using mount ===== 
  
-Unlike other filesystems ​which hold files and directoriesswap +Now that we've learned what (some of) the different ​filesystems 
-partitions hold virtual memoryThis is very useful as it prevents ​the +available in Linux areit's time we looked at how to use them. 
-system from crashing should all your RAM be consumed. Instead, ​the +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 mountedTo do this, we (naturally) use mount(8). 
-applications ​to use. Think of it as adding virtual memory ​to your +The first thing we must do is decide where we want the filesystem 
-computervery slow virtual memoryswap is typically a fail-safe and +located. Recall that there are no such things are drive letters 
-shouldn'be relied upon for continual ​use. Add more RAM to your system +denoting filesystems in Linux. Instead, ​all filesystems are mounted 
-if you find yourself using lots of swap+on directories. The base filesystem on which you install Slackware 
 +is always located at ''/'' ​and others are always located in 
 +subdirectories of ''/''​. ''/​mnt/​hd''​ is a common place to temporarily 
 +locate a partition, so we'​ll ​use that in our first example. 
 +In order to mount a filesystem'​s contents, we must tell mount what 
 +kind of filesystem we havewhere to mount it, and any special 
 +options to use. 
 + 
 +<​code>​ 
 +darkstar:~# mount -t ext3 /dev/hda3 /mnt/hd -o ro 
 +</​code>​ 
 + 
 +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,​ we have mounted it 
 +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'​s contents. Here we've chosen ''/​mnt/​hd''​. Finally, 
 +we must decide what options to use if any. These are declared with 
 +the [-o] argument. A short-list ​of the most common options follows
  
 **Table 11.2. Common mount options** **Table 11.2. Common mount options**
Line 248: Line 270:
  
  
-<code>+<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 254: Line 276:
  
 /​home/​backup 192.168.1.0/​24(sync,​rw,​no_root_squash) /​home/​backup 192.168.1.0/​24(sync,​rw,​no_root_squash)
-</code>+</file>
  
  
Line 276: Line 298:
 ==== SMB ====  ==== SMB ==== 
  
-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 //smb.conf(5)//. Unfortunately configuring samba as a service is beyond the scope of this book. Check online for additional documentation,​ and as always refer to the man page.+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 ''​smb.conf''​(5). Unfortunately configuring samba as a 
 +service is beyond the scope of this book. Check online for additional 
 +documentation,​ and as always refer to the man page.  
 + 
 + 
 +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,​ you 
 +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,​ you must specify a username and password. 
  
 <​code>​ <​code>​
Line 284: Line 319:
 </​code>​ </​code>​
  
-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 [usernameand [passwordarguments. This can create a security problem if you wish to place your samba share in fstab. You may avoid this problem by using the [credentialsargument. ​[credentialspoints to a file 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.+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. ​//credentials// points to a file 
 +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. ​ 
  
 <​code>​ <​code>​
Line 293: Line 340:
 darkstar:~# mount -t cifs //​darkstar/​home -o credentials=/​etc/​creds-home darkstar:~# mount -t cifs //​darkstar/​home -o credentials=/​etc/​creds-home
 </​code>​ </​code>​
 +
 +====== Chapter Navigation ======
 +
 +**Previous Chapter: [[slackbook:​filesystem_permissions|Filesystem Permissions]]**
 +
 +**Next Chapter: [[slackbook:​vi|vi]]**
 ====== Sources ====== ====== Sources ======
- * Original source: [[http://​www.slackbook.org/​beta/]] +<!-- If you copy information from another source, then specify that source --> 
 +  * Original source: [[http://​www.slackbook.org/​beta]] ​\\ 
 +<!-- Authors are allowed to give credit to themselves! --> 
 +  * Originally written by Alan Hicks, Chris Lumens, David Cantrell, Logan Johnson 
 +<!-- * Contrbutions by [[wiki:​user:​yyy | User Y]] -->
  
 <!-- Please do not modify anything below, except adding new tags.--> <!-- Please do not modify anything below, except adding new tags.-->
-{{tag>​slackbook filesystem mount}}+<!-- You must also remove the tag-word "​template"​ below. Otherwise your page will not show up in the Table of Contents --> 
 +{{tag>​slackbook filesystem ​network_filesystems nfs smb mount}}

In Other Languages
QR Code
QR Code slackbook:working_with_filesystems (generated for current page)