“UbuntuHelp:MountWindowsSharesPermanently”的版本间的差异

2010年5月19日 (三) 23:27的最新版本

文章出处:

https://help.ubuntu.com/community/MountWindowsSharesPermanently

点击翻译:

English

请不要直接编辑翻译本页，本页将定期与来源同步。

This page is being developed to fix a dead link on the InternetAndNetworking page.

Introduction

This guide will show you how to setup a mount of a remote windows share, and have it always there when you startup.

Two methods, depending on share host

cifs
smbfs

smbfs is the "original" method. However, smbfs is not compatible with security signatures, which are enabled by default and not recommended to disable on Windows Server 2003 and later. If a share is served by Windows Server 2003 or later, you should use cifs.

Prerequisites

You must have a windows machine (or other machine running Samba) with an accessible share. The 'samba' package itself is not necessary if you only need a smb client. The "smbfs" package provides the tools needed to mount "smbfs" and "cifs" filesytems. You may have smbfs installed on your machine. If not, run

sudo apt-get install smbfs

Update the unmount order to prevent CIFS from hanging during shutdown.

sudo update-rc.d -f umountnfs.sh remove
sudo update-rc.d umountnfs.sh stop 15 0 6 .

Setup

Single User

Note the UID of the single user which is to have access to the share. For a user named $username, the following command outputs the UID

grep $USERNAME /etc/passwd | cut -d: -f3

Multiple Users

If multiple users are to have the same level of access to the share, then create a new user group, presumably named after the share. Navigate to "System" -> "Administration" -> "Users and Groups" -> "Manage Groups". -> "Add Group" and select a name, Group ID (GID), and group members. Note the GID -- you will need it later.

Credentials File

Warning- this method is not completely secure, any user with root access could see your password in plain text. Create a file called .smbcredentials, probably in the home directory of the primary user of the share. In this file put username an equals sign and the windows username (and domain if loging into a domain) on the first line, put password an equals sign and the password for that user account on the second line of the file. The file should look like:

username=MyUsername
password=MyPassword

# OR:
# username=MyUsername@MyDomain
# password=MyPassword

On the command line, in the directory of .smbcredentials type

sudo chown root .smbcredentials
sudo chmod 600 .smbcredentials

this will ensure that only root can access this file. Note: Regretfully as from version 3.3.2-1ubuntu3.2 (October 2009) this approach is no longer possible together with the "user" option. A security fix prevents reading the credentials file if you don't have read access to it. You will have to pin the packages at version 3.3.2-1ubuntu3 or 3.3.2-1ubuntu3.1 to continue using this approach as non-root.

Editing fstab

Warning- editing the fstab file can be dangerous, please back it up before continuing. Note: if servername or sharename has a literal space (i.e. ' '), substitute \040 instead, so that 'server name' becomes 'server\040name' Add a line at the bottom of your /etc/fstab file that specifies: //$SERVER/$SHARE $MOUNTPOINT $FS_TYPE credentials=$SMB_CREDENTIALS,uid=$UID,gid=$GID

# e.g.
SERVER=apollo
SHARE=install_files
MOUNTPOINT=/path/to/mnt
FS_TYPE=smbfs
SMB_CREDENTIALS=/path/to/.smbcredentials
UID=1000
GID=1000

smbfs, group perms

FS_TYPE=smbfs
GID=1234 # the newly created group's ID
don't include uid=$UID, which defaults to that of root

//apollo/install_files /path/to/mnt smbfs iocharset=utf8,credentials=/path/to/.smbcredentials,gid=1234 0 0

Note: many directories are set so that only the user can write to the directory and that the group can only read (permissions 755), if this is the case then when it is mounted the group will still not be able to write to the directory regardless of their permission on the share. To give the group write permissions on the mount then use the following.

//apollo/install_files /path/to/mnt smbfs iocharset=utf8,credentials=/path/to/.smbcredentials,dmask=775,gid=1234 0 0

smbfs, user perms

FS_TYPE=smbfs
UID=1000 # particular user's uid
don't include gid=$GID, which defaults to $UID

//apollo/install_files /path/to/mnt smbfs iocharset=utf8,credentials=/path/to/.smbcredentials,uid=1000 0 0

cifs, group perms

FS_TYPE=cifs
GID=1234 # the newly created group's ID
don't include uid=$UID

//apollo/install_files /path/to/mnt cifs iocharset=utf8,credentials=/path/to/.smbcredentials,gid=1234 0 0

Note: many directories are set so that only the user can write to the directory and that the group can only read (permissions 755), if this is the case then when it is mounted the group will still not be able to write to the directory regardless of their permission on the share. To give the group write permissions on the mount then use the following.

//apollo/install_files /path/to/mnt smbfs iocharset=utf8,credentials=/path/to/.smbcredentials,dir_mode=0775,gid=1234 0 0

cifs, user perms

FS_TYPE=cifs
UID=1000 # the user's uid
don't include gid=$GID

//apollo/install_files /path/to/mnt cifs iocharset=utf8,credentials=/path/to/.smbcredentials,uid=1000 0 0

Ensure

The entire expression MUST all be on one line in your fstab file
use "//" and "/" instead of "\\" and "\" when specifying the share location
/path/to/mnt is a directory that exists (and is empty)

Completing Setup

Reload fstab:

sudo mount -a

Troubleshooting

cifs will not mount

Note:- cifs by default does not resolve netbios names so you may get an error message when you try to mount that the name could not be resolved into an address and "could not find target server". In order to enable netbios resolution you need to edit /etc/nsswitch.conf and add the winbind package:

edit /etc/nsswitch.conf

sudo gedit /etc/nsswitch.conf

change the line from

hosts: files dns

to

hosts: files wins dns

next install winbind

sudo aptitude install winbind

Now you should be able to mount the directory

Server is down, filesystem is hung

If the client somehow loses contact with the Samba server, then the filesystem will probably get hung. Basically, it becomes a blackhole, eating things that try to read to/write from it (e.g. ls) and refusing to go away (e.g., umount says that the "device is busy"). Sometimes, all you need to do is restart the Samba daemon on the server machine.

sudo /etc/init.d/samba restart

If that doesn't work, or for some reason you can't do anything on the server side, then try

sudo umount -lf /mount/point

The -f option forces (possibly unclean) unmounting, and the -l option is for "lazy unmounting", and seems to work around "device is busy" errors that occur with just -f.

CIFS remote ownership enforcement

When you connect using CIFS to a server which supports Unix permissions (e.g. Samba), CIFS will by default try to enforce remote Unix ownership UIDs and Unix permissions when you try to access the share. i.e. if a file is owned by UID 502 on the remote server, then the local kernel will try to enforce the same permissions if it were owned by UID 502 on the local machine. Note: This has nothing to do with the remote server's security settings. This is an extra local ownership enforcement by the filesystem driver. It is a feature to allow use of remote share as a local drive with full Unix permissions enforcement if users match. But if this is a public share, then chances are, the remote UIDs will not make sense locally. A remote UID might be a completely different user or might not exist at all on the local machine. If remote UIDs and local UIDs do not match, then local users will have trouble using the share. To disable this, use the "noperm" mount option. Remote permissions and UIDs will still be visible, but they will not be enforced locally.

System Hangs on Shutdown

Sometimes during shutdown, networking will be turned off before the network share is unmounted. This will cause the computer to display the below code for a few minuets before shutting down (the numbers seem to change after each boot).

CIFS VFS: server not responding
CIFS VFS: no response for cmd ## mid ###

To fix this problem, and allow the computer to shut down smoothly, just change when the network share is unmounted by the file system. This can be done by running the following commands:

sudo update-rc.d -f umountnfs.sh remove
sudo update-rc.d umountnfs.sh stop 15 0 6 .

Login without Credentials

If you want to mount the share without the credentials file you can use the entry below. I believe that by adding the _netdev in the entry below, it will not mount the share if you are not connected to the same network that the share is on or if you are not connected to a network at all.

/etc/fstab: static file system information.
<file system> <mount point> <type> <options> <dump> <pass>

//<server>/<share> <mount point> cifs rw,_netdev,user=<username>,password=<password>,uid=<uid>,gid=<gid> 0 0 Here is an example of the last line //gurnee/projects /home/jcrow/GurneeServer cifs rw,_netdev,user=DOMAIN/user,password=password,uid=1000,gid=100 0 0 The server being connected to is Gurnee, the shared folder is projects, the mount point is /home/jcrow/GurneeServer

Connect when network available

The _netdev option is also used for systems that only have networking started at user login (as when using the Gnome Network Manager package). For having network connections enabled at boot up (without requiring a user login) then tools that write to the /etc/network/interfaces file may have to be used. It is probably good policy to always use _netdev for all automatic network mounts.

@@ 第1行： / 第1行： @@
 {{From|https://help.ubuntu.com/community/MountWindowsSharesPermanently}}
-{{Languages|php5}}
+{{Languages|UbuntuHelp:MountWindowsSharesPermanently}}
+This page is being developed to fix a dead link on the [[UbuntuHelp:InternetAndNetworking|InternetAndNetworking]] page.
-This page is being developed to fix a dead link on the InternetAndNetworking page.
 == Introduction ==
+This guide will show you how to setup a mount of a remote windows share, and have it always there when you startup.
-This guide will show you how to setup a mount of a remote windows share, and have it always there when you startup.
+=== Two methods, depending on share host ===
+* cifs
+* smbfs
+smbfs is the "original" method.
+However, smbfs is not compatible with security signatures, which are enabled by default and not recommended to disable on Windows Server 2003 and later.  If a share is served by Windows Server 2003 or later, you should use cifs.
 == Prerequisites ==
+You must have a windows machine (or other machine running Samba) with an accessible share.
-You must have smbfs installed on your machine.  This should occur by default.  If you don't have it, run
+The 'samba' package itself is not necessary if you only need a smb client.
+The "smbfs" package provides the tools needed to mount "smbfs" and "cifs" filesytems.
+You may have smbfs installed on your machine.  If not, run
 <pre><nowiki>
 sudo apt-get install smbfs
-</nowiki></code>
+</nowiki></pre>
+Update the unmount order to prevent CIFS from hanging during shutdown.
-You must have a windows machine (or other machine running Samba) with an accessable share.
+<pre><nowiki>
+sudo update-rc.d -f umountnfs.sh remove
-The 'samba' package itself is not necessary if you only need a smb client.
+sudo update-rc.d umountnfs.sh stop 15 0 6 .
+</nowiki></pre>
 == Setup ==
+=== Single User ===
-=== Read/Write Group ===
+Note the UID of the single user which is to have access to the share.  For a user named $username, the following command outputs the UID
-The first step is to create a group of users that you want to have read/write access to this share (by default only root can r/w).  If there is only one user you want to give read/write access, then don't worry about this.  If you have multiple users, and each user also has a windows account with individual permissions, do not add them to this group.  Instead, repeat this set of instructions for each user, I would recommend making the mount point in this example somewhere in their home directory.
+<pre><nowiki>
+grep $USERNAME /etc/passwd | cut -d: -f3
-To create the group, go to the "System" menu, then to the "Administration" menu, then select "Users and Groups".  Under the groups tab, create a new group.  Then add the users you want to have read/write access to this group.  Write down the GID for the group, you will need it later.
+</nowiki></pre>
+=== Multiple Users ===
+If multiple users are to have the same level of access to the share, then create a new user group, presumably named after the share.
+Navigate to "System" -> "Administration" -> "Users and Groups" -> "Manage Groups". -> "Add Group" and select a name, Group ID (GID), and group members.  Note the GID -- you will need it later.
 === Credentials File ===
 Warning- this method is not completely secure, any user with root access could see your password in plain text.
+Create a file called .smbcredentials, probably in the home directory of the primary user of the share.  In this file put username an equals sign and the windows username (and domain if loging into a domain) on the first line, put password an equals sign and the password for that user account on the second line of the file.  The file should look like:
-Create a file called .smbpassword, probably in the home directory of the primary user of the share.  In this file put username an equals sign and the windows username (and domain if loging into a domain) on the first line, put password an equals sign and the password for that user account on the second line of the file.  The file should look like:
 <pre><nowiki>
-username=MyUserName
+username=MyUsername
 password=MyPassword
-</nowiki></code>
-On the command line, in the directory of .smbpassword type
+# OR:
+# username=MyUsername@MyDomain
+# password=MyPassword
+</nowiki></pre>
+On the command line, in the directory of .smbcredentials type
 <pre><nowiki>
-sudo chown root .smbpassword
+sudo chown root .smbcredentials
-sudo chmod 600 .smbpassword
+sudo chmod 600 .smbcredentials
-</nowiki></code>
+</nowiki></pre>
 this will ensure that only root can access this file.
+'''''Note:''' Regretfully as from version 3.3.2-1ubuntu3.2 (October 2009) this approach is no longer possible together with the "user" option. A security fix prevents reading the credentials file if you don't have read access to it. You will have to pin the packages at version 3.3.2-1ubuntu3 or 3.3.2-1ubuntu3.1 to continue using this approach as non-root.''
 === Editing fstab ===
 Warning- editing the fstab file can be dangerous, please back it up before continuing.
+Note: if servername or sharename has a literal space (i.e. ' '), substitute \040 instead, so that 'server name' becomes 'server\040name'
-Add a line at the bottom of your \etc\fstab file that specifies:
+Add a line at the bottom of your /etc/fstab file that specifies:
+//$SERVER/$SHARE $MOUNTPOINT $FS_TYPE credentials=$SMB_CREDENTIALS,uid=$UID,gid=$GID
 <pre><nowiki>
-//servername/sharename /mountdirectory smbfs credentials=/home/myhomedirectory/.smbpassword,gid=GIDFromAbove 0 0
+# e.g.
-</nowiki></code>
+SERVER=apollo
-''I can't make the above show up on one line, but it MUST all be on one line in your fstab file''
+SHARE=install_files
+MOUNTPOINT=/path/to/mnt
-If you only want one user to have read/write access, use uid=UsersID instead of the gid.  If you don't want anyone except root to have read/write access, leave that string out entirely.
+FS_TYPE=smbfs
-You can find the UsersID in /etc/passwd
+SMB_CREDENTIALS=/path/to/.smbcredentials
+UID=1000
+GID=1000
+</nowiki></pre>
+==== smbfs, group perms ====
+* FS_TYPE=smbfs
+* GID=1234 # the newly created group's ID
+* don't include uid=$UID, which defaults to that of root
+<pre><nowiki>
+//apollo/install_files /path/to/mnt smbfs iocharset=utf8,credentials=/path/to/.smbcredentials,gid=1234 0 0
+</nowiki></pre>
+Note: many directories are set so that only the user can write to the directory and that the group can only read (permissions 755), if this is the case then when it is mounted the group will still not be able to write to the directory regardless of their permission on the share. To give the group write permissions on the mount then use the following.
+<pre><nowiki>
+//apollo/install_files /path/to/mnt smbfs iocharset=utf8,credentials=/path/to/.smbcredentials,dmask=775,gid=1234 0 0
+</nowiki></pre>
+==== smbfs, user perms ====
+* FS_TYPE=smbfs
+* UID=1000 # particular user's uid
+* don't include gid=$GID, which defaults to $UID
+<pre><nowiki>
+//apollo/install_files /path/to/mnt smbfs iocharset=utf8,credentials=/path/to/.smbcredentials,uid=1000 0 0
+</nowiki></pre>
+==== cifs, group perms ====
+* FS_TYPE=cifs
+* GID=1234 # the newly created group's ID
+* don't include uid=$UID
 <pre><nowiki>
-less /etc/passwd
+//apollo/install_files /path/to/mnt cifs iocharset=utf8,credentials=/path/to/.smbcredentials,gid=1234 0 0
+</nowiki></pre>
-and then type / -followed by the username you are looking for-
+Note: many directories are set so that only the user can write to the directory and that the group can only read (permissions 755), if this is the case then when it is mounted the group will still not be able to write to the directory regardless of their permission on the share. To give the group write permissions on the mount then use the following.
-</nowiki></code>
+<pre><nowiki>
+//apollo/install_files /path/to/mnt smbfs iocharset=utf8,credentials=/path/to/.smbcredentials,dir_mode=0775,gid=1234 0 0
-Be sure to use unix "//" and "/" instead of windows "\\" and "\" in the windows share, otherwise it won't parse correctly.
+</nowiki></pre>
+==== cifs, user perms ====
-Make sure the /mountdirector is a directory that exists (and is empty)
+* FS_TYPE=cifs
+* UID=1000 # the user's uid
+* don't include gid=$GID
+<pre><nowiki>
+//apollo/install_files /path/to/mnt cifs iocharset=utf8,credentials=/path/to/.smbcredentials,uid=1000 0 0
+</nowiki></pre>
+=== Ensure ===
+* The entire expression MUST all be on one line in your fstab file
+* use "//" and "/" instead of "\\" and "\" when specifying the share location
+* /path/to/mnt is a directory that exists (and is empty)
 === Completing Setup ===
-Reload fstab or restart
+Reload fstab:
-Reloading fstab can be done by typing:
 <pre><nowiki>
 sudo mount -a
-</nowiki></code>
+</nowiki></pre>
 == Troubleshooting ==
+=== cifs will not mount ===
+Note:- cifs by default does not resolve netbios names so you may get an error message when you try to mount that the name could not be resolved into an address and "could not find target server".
+In order to enable netbios resolution you need to edit /etc/nsswitch.conf and add the winbind package:
+* edit /etc/nsswitch.conf
+<pre><nowiki>
+sudo gedit /etc/nsswitch.conf
+</nowiki></pre>
+change the line from
+<pre><nowiki>
+hosts: files dns
+</nowiki></pre>
+to
+<pre><nowiki>
+hosts: files wins dns
+</nowiki></pre>
+* next install winbind
+<pre><nowiki>
+sudo aptitude install winbind
+</nowiki></pre>
+Now you should be able to mount the directory
 === Server is down, filesystem is hung ===
 If the client somehow loses contact with the Samba server, then the filesystem will probably get hung.  Basically, it becomes a blackhole, eating things that try to read to/write from it (e.g. <code><nowiki>ls</nowiki></code>) and refusing to go away (e.g., <code><nowiki>umount</nowiki></code> says that the "device is busy").
 Sometimes, all you need to do is restart the Samba daemon on the server machine.
 <pre><nowiki>
 sudo /etc/init.d/samba restart
-</nowiki></code>
+</nowiki></pre>
 If that doesn't work, or for some reason you can't do anything on the server side, then try
 <pre><nowiki>
 sudo umount -lf /mount/point
-</nowiki></code>
+</nowiki></pre>
 The <code><nowiki>-f</nowiki></code> option forces (possibly unclean) unmounting, and the <code><nowiki>-l</nowiki></code> option is for "lazy unmounting", and seems to work around "device is busy" errors that occur with just <code><nowiki>-f</nowiki></code>.
+=== CIFS remote ownership enforcement ===
+When you connect using CIFS to a server which supports Unix permissions (e.g. Samba), CIFS will by default try to enforce remote Unix ownership UIDs and Unix permissions when you try to access the share. i.e. if a file is owned by UID 502 on the remote server, then the local kernel will try to enforce the same permissions if it were owned by UID 502 on the local machine. Note: This has nothing to do with the remote server's security settings. This is an extra local ownership enforcement by the filesystem driver. It is a feature to allow use of remote share as a local drive with full Unix permissions enforcement if users match.
+But if this is a public share, then chances are, the remote UIDs will not make sense locally. A remote UID might be a completely different user or might not exist at all on the local machine. If remote UIDs and local UIDs do not match, then local users will have trouble using the share. To disable this, use the "noperm" mount option. Remote permissions and UIDs will still be visible, but they will not be enforced locally.
+=== System Hangs on Shutdown ===
+Sometimes during shutdown, networking will be turned off before the network share is unmounted.  This will cause the computer to display the below code for a few minuets before shutting down (the numbers seem to change after each boot).
+<pre><nowiki>
+CIFS VFS: server not responding
+CIFS VFS: no response for cmd ## mid ###
+</nowiki></pre>
+To fix this problem, and allow the computer to shut down smoothly, just change when the network share is unmounted by the file system.  This can be done by running the following commands:
+<pre><nowiki>
+sudo update-rc.d -f umountnfs.sh remove
+sudo update-rc.d umountnfs.sh stop 15 0 6 .
+</nowiki></pre>
+=== Login without Credentials ===
+If you want to mount the share without the credentials file you can use the entry below. I believe that by adding the '''_netdev''' in the entry below, it will not mount the share if you are not connected to the same network that the share is on or if you are not connected to a network at all.
+# /etc/fstab: static file system information.
+#
+# <file system> <mount point> <type> <options> <dump> <pass>
+//<server>/<share> <mount point> cifs rw,_netdev,user=<username>,password=<password>,uid=<uid>,gid=<gid> 0 0
+Here is an example of the last line
+//gurnee/projects /home/jcrow/GurneeServer cifs rw,_netdev,user=DOMAIN/user,password=password,uid=1000,gid=100 0 0
+The server being connected to is Gurnee, the shared folder is projects, the mount point is /home/jcrow/GurneeServer
+=== Connect when network available  ===
+The '''_netdev''' option is also used for systems that only have networking started at user login (as when using the Gnome Network Manager package). For having network connections enabled at boot up (without requiring a user login) then tools that write to the /etc/network/interfaces file may have to be used. It is probably good policy to always use '''_netdev''' for all automatic network mounts.
 ----
-CategoryDocumentation
 [[category:UbuntuHelp]]

个人工具

“UbuntuHelp:MountWindowsSharesPermanently”的版本间的差异 - Ubuntu中文

搜索

导航

编辑

工具