/[gentoo]/xml/htdocs/doc/en/quick-samba-howto.xml
Gentoo

Diff of /xml/htdocs/doc/en/quick-samba-howto.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.29 Revision 1.35
1<?xml version='1.0' encoding='UTF-8'?> 1<?xml version='1.0' encoding='UTF-8'?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.29 2007/06/06 23:23:35 nightmorph Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.35 2007/10/14 19:10:05 nightmorph Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4<guide link="/doc/en/quick-samba-howto.xml"> 4<guide link="/doc/en/quick-samba-howto.xml">
5<title>Gentoo Samba3/CUPS/ClamAV HOWTO</title> 5<title>Gentoo Samba3/CUPS/ClamAV HOWTO</title>
6<author title="Author"> 6<author title="Author">
7 <mail link="daff at dword dot org">Andreas "daff" Ntaflos</mail> 7 <mail link="daff at dword dot org">Andreas "daff" Ntaflos</mail>
8</author> 8</author>
9<author title="Author"> 9<author title="Author">
10 <mail link="joshua@sungentoo.homeunix.com">Joshua Preston</mail> 10 <mail link="joshua@sungentoo.homeunix.com">Joshua Preston</mail>
11</author> 11</author>
12<author title="Editor">
13 <mail link="nightmorph@gentoo.org">Joshua Saddler</mail>
14</author>
12 15
13<abstract> 16<abstract>
14Setup, install and configure a Samba Server under Gentoo that shares files, 17Setup, install and configure a Samba Server under Gentoo that shares files,
15printers without the need to install drivers and provides automatic virus 18printers without the need to install drivers and provides automatic virus
16scanning. 19scanning.
18 21
19<!-- The content of this document is licensed under the CC-BY-SA license --> 22<!-- The content of this document is licensed under the CC-BY-SA license -->
20<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 23<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
21<license/> 24<license/>
22 25
23<version>1.17</version> 26<version>1.22</version>
24<date>2007-06-06</date> 27<date>2007-10-14</date>
25 28
26<chapter> 29<chapter>
27<title>Introduction to this HOWTO</title> 30<title>Introduction to this HOWTO</title>
28<section> 31<section>
29<title>Purpose</title> 32<title>Purpose</title>
152 </li> 155 </li>
153</ul> 156</ul>
154 157
155<p> 158<p>
156The main package we use here is net-fs/samba, however, you will need a kernel 159The main package we use here is net-fs/samba, however, you will need a kernel
157with smbfs support enabled in order to mount a samba or windows share from 160with cifs support enabled in order to mount a samba or windows share from
158another computer. CUPS will be emerged if it is not already. 161another computer. CUPS will be emerged if it is not already.
159app-antivirus/clamav will be used also, but others should be easily adapted to 162app-antivirus/clamav will be used also, but others should be easily adapted to
160work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning 163work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning
161technologies, such as Sophos, FProt, Fsav, Trend, Icap, Nai, ... 164technologies, such as Sophos, FProt, Fsav, Trend, Icap, Nai, ...
162</p> 165</p>
416hosts deny = 0.0.0.0/0 419hosts deny = 0.0.0.0/0
417<comment># Other options for this are USER, DOMAIN, ADS, and SERVER 420<comment># Other options for this are USER, DOMAIN, ADS, and SERVER
418# The default is user</comment> 421# The default is user</comment>
419security = share 422security = share
420<comment># No passwords, so we're going to use a guest account!</comment> 423<comment># No passwords, so we're going to use a guest account!</comment>
421guest account = samba
422guest ok = yes 424guest ok = yes
423<comment># We now will implement the on access virus scanner. 425<comment># We now will implement the on access virus scanner.
424# NOTE: By putting this in our [Global] section, we enable 426# NOTE: By putting this in our [Global] section, we enable
425# scanning of ALL shares, you could optionally move 427# scanning of ALL shares, you could optionally move
426# these to a specific share and only scan it.</comment> 428# these to a specific share and only scan it.</comment>
776 778
777<p> 779<p>
778There are two sets of printer drivers for this. First, the Adobe PS drivers 780There are two sets of printer drivers for this. First, the Adobe PS drivers
779which can be obtained from <uri 781which can be obtained from <uri
780link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript 782link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript
781printer drivers). Second, there are the CUPS PS drivers, to be obtained <uri 783printer drivers). Second, there are the CUPS PS drivers, to be obtained by
782link="http://dev.gentoo.org/~nightmorph/misc/cups-samba-5.0rc2.tar.gz">here</uri>. 784emerging <c>net-print/cups-windows</c>. Note that it may still be marked ~arch,
785so you may need to add it to <path>/etc/portage/package.keywords</path>. There
783There doesn't seem to be a difference between the functionality of the two, but 786doesn't seem to be a difference between the functionality of the two, but the
784the Adobe PS drivers need to be extracted on a Windows System since it's a 787Adobe PS drivers need to be extracted on a Windows System since it's a Windows
785Windows binary. Also the whole procedure of finding and copying the correct 788binary. Also the whole procedure of finding and copying the correct files is a
786files is a bit more hassle. The CUPS drivers seem to support some options the 789bit more hassle. The CUPS drivers support some options the Adobe drivers
787Adobe drivers don't. 790don't.
788</p>
789<!--
790used to be available at www.cups.org/articles.php?L142+p4, but only 6.0 is
791available. at some point, we should update this for 6.0.
792-->
793
794<p> 791</p>
795This HOWTO uses the CUPS drivers for Windows. The downloaded file is 792
796called <path>cups-samba-5.0rc2.tar.gz</path>. Extract the files
797contained into a directory.
798</p> 793<p>
799 794This HOWTO uses the CUPS drivers for Windows. Install them as shown:
800<pre caption="Extract the drivers and run the install">
801# <i>tar -xzf cups-samba-5.0rc2.tar.gz</i>
802# <i>cd cups-samba-5.0rc2</i>
803<comment>(Only use this script if CUPS resides in /usr/share/cups)</comment>
804# <i>./cups-samba.install</i>
805</pre>
806
807<p> 795</p>
808<path>cups-samba.ss</path> is a TAR archive containing three files:
809<path>cups5.hlp</path>, <path>cupsdrvr5.dll</path> and
810<path>cupsui5.dll</path>. These are the actual driver files.
811</p>
812 796
813<warn>
814The script <c>cups-samba.install</c> may not work for all *nixes (i.e. FreeBSD)
815because almost everything which is not part of the base system is installed
816somewhere under the prefix <path>/usr/local/</path>. This seems not to be the
817case for most things you install under GNU/Linux. However, if your CUPS
818installation is somewhere other than <path>/usr/share/cups/</path> see the
819example below.
820</warn>
821
822<p>
823Suppose your CUPS installation resides under
824<path>/usr/local/share/cups/</path>, and you want to install the drivers there.
825Do the following:
826</p>
827
828<pre caption="Manually installing the drivers"> 797<pre caption="Install the drivers">
829# <i>cd /path/you/extracted/the/CUPS-driver/tarball/into</i> 798# <i>emerge -av cups-windows</i>
830# <i>tar -xf cups-samba.ss</i>
831<comment>(This extracts the files to usr/share/cups/drivers under the CURRENT WORKING DIRECTORY)</comment>
832# <i>cd usr/share/cups/drivers</i>
833<comment>(no leading / !)</comment>
834# <i>cp cups* /usr/local/share/cups/drivers</i>
835# <i>/etc/init.d/cupsd restart</i>
836</pre> 799</pre>
837 800
838<p> 801<p>
839Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS distribution. 802Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS distribution.
840Its man page is an interesting read. 803Be sure to read its manpage (<c>man cupsaddsmb</c>), as it will tell you which
804Windows drivers you'll need to copy to the proper CUPS directory. Once you've
805copied the drivers, restart CUPS by running <c>/etc/init.d/cupsd restart</c>.
806Next, run <c>cupsaddsmb</c> as shown:
841</p> 807</p>
842 808
843<pre caption="Run cupsaddsmb"> 809<pre caption="Run cupsaddsmb">
844# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -v HPDeskJet930C</i> 810# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -v HPDeskJet930C</i>
845<comment>(Instead of HPDeskJet930C you could also specify "-a", which will 811<comment>(Instead of HPDeskJet930C you could also specify "-a", which will
1025</section> 991</section>
1026<section> 992<section>
1027<title>Mounting a Windows or Samba share in GNU/Linux</title> 993<title>Mounting a Windows or Samba share in GNU/Linux</title>
1028<body> 994<body>
1029 995
996<note>
997Don't forget to first <c>emerge samba</c> on the client(s) that will be
998accessing the shares.
999</note>
1000
1030<p> 1001<p>
1031Now is time to configure our kernel to support smbfs. Since I'm assumming we've 1002Now is time to configure our kernel to support cifs. Since I'm assuming
1032all compiled at least one kernel, we'll need to make sure we have all the right 1003we've all compiled at least one kernel, we'll need to make sure we have all the
1033options selected in our kernel. For simplicity's sake, make it a module for ease 1004right options selected in our kernel. For simplicity's sake, make it a module
1034of use. It is the author's opinion that kernel modules are a good thing and 1005for ease of use. It is the author's opinion that kernel modules are a good thing
1035should be used whenever possible. 1006and should be used whenever possible.
1036</p>
1037
1038<pre caption="Relevant kernel options" >
1039CONFIG_SMB_FS=m
1040CONFIG_SMB_UNIX=y
1041</pre>
1042
1043<p> 1007</p>
1008
1009<pre caption="Kernel support" >
1010CONFIG_CIFS=m
1011</pre>
1012
1013<p>
1044Then make the module/install it; insert them with: 1014Then make the module/install it; insert it with:
1045</p> 1015</p>
1046 1016
1047<pre caption="Loading the kernel module"> 1017<pre caption="Loading the kernel module">
1048# <i>modprobe smbfs</i> 1018# <i>modprobe cifs</i>
1049</pre> 1019</pre>
1050 1020
1051<p> 1021<p>
1052Once the module is loaded, mounting a Windows or Samba share is possible. Use 1022Once the module is loaded, mounting a Windows or Samba share is possible. Use
1053<c>mount</c> to accomplish this, as detailed below: 1023<c>mount</c> to accomplish this, as detailed below:
1054</p> 1024</p>
1055 1025
1056<pre caption="Mounting a Windows/Samba share"> 1026<pre caption="Mounting a Windows/Samba share">
1057<comment>(The syntax for mounting a Windows/Samba share is: 1027<comment>(The syntax for mounting a Windows/Samba share is:
1058 mount -t smbfs [-o username=xxx,password=xxx] //server/share /mnt/point 1028 mount -t cifs [-o username=xxx,password=xxx] //server/share /mnt/point
1059If we are not using passwords or a password is not needed)</comment> 1029If we are not using passwords or a password is not needed)</comment>
1060 1030
1061# <i>mount -t smbfs //PrintServer/public /mnt/public</i> 1031# <i>mount -t cifs //PrintServer/public /mnt/public</i>
1062 1032
1063<comment>(If a password is needed)</comment> 1033<comment>(If a password is needed)</comment>
1064# <i>mount -t smbfs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i> 1034# <i>mount -t cifs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i>
1065</pre> 1035</pre>
1066 1036
1067<p> 1037<p>
1068After you mount the share, you would access it as if it were a local drive. 1038After you mount the share, you would access it as if it were a local drive.
1069</p> 1039</p>

Legend:
Removed from v.1.29  
changed lines
  Added in v.1.35

  ViewVC Help
Powered by ViewVC 1.1.20