[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.

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 revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
slackbook:working_with_filesystems [2012/09/09 22:58 (UTC)] – [NFS] Added original text with formatting mfillpotslackbook:working_with_filesystems [2012/10/14 15:58 (UTC)] – removed all bash flags mfillpot
Line 248: Line 248:
  
  
-<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 254:
  
 /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 276:
 ==== 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 297:
 </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 [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.+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 318:
 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}}

Trace:

slackbook:working_with_filesystems ()