nightmorph 07/07/29 06:48:12 Modified: quick-samba-howto.xml Log: updated cifs stuff for bug 186776
Revision Changes Path 1.31 xml/htdocs/doc/en/quick-samba-howto.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml?rev=1.31&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml?rev=1.31&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml?r1=1.30&r2=1.31 Index: quick-samba-howto.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v retrieving revision 1.30 retrieving revision 1.31 diff -u -r1.30 -r1.31 --- quick-samba-howto.xml 8 Jul 2007 02:22:04 -0000 1.30 +++ quick-samba-howto.xml 29 Jul 2007 06:48:12 -0000 1.31 @@ -1,5 +1,5 @@ <?xml version='1.0' encoding='UTF-8'?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.30 2007/07/08 02:22:04 nightmorph Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.31 2007/07/29 06:48:12 nightmorph Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> <guide link="/doc/en/quick-samba-howto.xml"> <title>Gentoo Samba3/CUPS/ClamAV HOWTO</title> @@ -23,8 +23,8 @@ <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> <license/> -<version>1.18</version> -<date>2007-07-07</date> +<version>1.19</version> +<date>2007-07-28</date> <chapter> <title>Introduction to this HOWTO</title> @@ -157,7 +157,7 @@ <p> The main package we use here is net-fs/samba, however, you will need a kernel -with smbfs support enabled in order to mount a samba or windows share from +with cifs support enabled in order to mount a samba or windows share from another computer. CUPS will be emerged if it is not already. app-antivirus/clamav will be used also, but others should be easily adapted to work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning @@ -993,24 +993,23 @@ <body> <p> -Now is time to configure our kernel to support smbfs. Since I'm assumming we've -all compiled at least one kernel, we'll need to make sure we have all the right -options selected in our kernel. For simplicity's sake, make it a module for ease -of use. It is the author's opinion that kernel modules are a good thing and -should be used whenever possible. +Now is time to configure our kernel to support cifs. Since I'm assuming +we've all compiled at least one kernel, we'll need to make sure we have all the +right options selected in our kernel. For simplicity's sake, make it a module +for ease of use. It is the author's opinion that kernel modules are a good thing +and should be used whenever possible. </p> -<pre caption="Relevant kernel options" > -CONFIG_SMB_FS=m -CONFIG_SMB_UNIX=y +<pre caption="Kernel support" > +CONFIG_CIFS=m </pre> <p> -Then make the module/install it; insert them with: +Then make the module/install it; insert it with: </p> <pre caption="Loading the kernel module"> -# <i>modprobe smbfs</i> +# <i>modprobe cifs</i> </pre> <p> @@ -1020,13 +1019,13 @@ <pre caption="Mounting a Windows/Samba share"> <comment>(The syntax for mounting a Windows/Samba share is: - mount -t smbfs [-o username=xxx,password=xxx] //server/share /mnt/point + mount -t cifs [-o username=xxx,password=xxx] //server/share /mnt/point If we are not using passwords or a password is not needed)</comment> -# <i>mount -t smbfs //PrintServer/public /mnt/public</i> +# <i>mount -t cifs //PrintServer/public /mnt/public</i> <comment>(If a password is needed)</comment> -# <i>mount -t smbfs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i> +# <i>mount -t cifs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i> </pre> <p> -- [EMAIL PROTECTED] mailing list
