| 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.32 2007/07/29 22:14:39 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> |
| 14 | Setup, install and configure a Samba Server under Gentoo that shares files, |
17 | Setup, install and configure a Samba Server under Gentoo that shares files, |
| 15 | printers without the need to install drivers and provides automatic virus |
18 | printers without the need to install drivers and provides automatic virus |
| 16 | scanning. |
19 | scanning. |
| … | |
… | |
| 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.20</version> |
| 24 | <date>2007-06-06</date> |
27 | <date>2007-07-29</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> |
| 156 | The main package we use here is net-fs/samba, however, you will need a kernel |
159 | The main package we use here is net-fs/samba, however, you will need a kernel |
| 157 | with smbfs support enabled in order to mount a samba or windows share from |
160 | with cifs support enabled in order to mount a samba or windows share from |
| 158 | another computer. CUPS will be emerged if it is not already. |
161 | another computer. CUPS will be emerged if it is not already. |
| 159 | app-antivirus/clamav will be used also, but others should be easily adapted to |
162 | app-antivirus/clamav will be used also, but others should be easily adapted to |
| 160 | work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning |
163 | work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning |
| 161 | technologies, such as Sophos, FProt, Fsav, Trend, Icap, Nai, ... |
164 | technologies, such as Sophos, FProt, Fsav, Trend, Icap, Nai, ... |
| 162 | </p> |
165 | </p> |
| … | |
… | |
| 776 | |
779 | |
| 777 | <p> |
780 | <p> |
| 778 | There are two sets of printer drivers for this. First, the Adobe PS drivers |
781 | There are two sets of printer drivers for this. First, the Adobe PS drivers |
| 779 | which can be obtained from <uri |
782 | which can be obtained from <uri |
| 780 | link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript |
783 | link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript |
| 781 | printer drivers). Second, there are the CUPS PS drivers, to be obtained <uri |
784 | printer drivers). Second, there are the CUPS PS drivers, to be obtained by |
| 782 | link="http://dev.gentoo.org/~nightmorph/misc/cups-samba-5.0rc2.tar.gz">here</uri>. |
785 | emerging <c>net-print/cups-windows</c>. Note that it may still be marked ~arch, |
|
|
786 | so you may need to add it to <path>/etc/portage/package.keywords</path>. There |
| 783 | There doesn't seem to be a difference between the functionality of the two, but |
787 | doesn't seem to be a difference between the functionality of the two, but the |
| 784 | the Adobe PS drivers need to be extracted on a Windows System since it's a |
788 | Adobe PS drivers need to be extracted on a Windows System since it's a Windows |
| 785 | Windows binary. Also the whole procedure of finding and copying the correct |
789 | binary. Also the whole procedure of finding and copying the correct files is a |
| 786 | files is a bit more hassle. The CUPS drivers seem to support some options the |
790 | bit more hassle. The CUPS drivers seem to support some options the Adobe drivers |
| 787 | Adobe drivers don't. |
791 | don't. |
| 788 | </p> |
|
|
| 789 | <!-- |
|
|
| 790 | used to be available at www.cups.org/articles.php?L142+p4, but only 6.0 is |
|
|
| 791 | available. at some point, we should update this for 6.0. |
|
|
| 792 | --> |
|
|
| 793 | |
|
|
| 794 | <p> |
792 | </p> |
| 795 | This HOWTO uses the CUPS drivers for Windows. The downloaded file is |
793 | |
| 796 | called <path>cups-samba-5.0rc2.tar.gz</path>. Extract the files |
|
|
| 797 | contained into a directory. |
|
|
| 798 | </p> |
794 | <p> |
| 799 | |
795 | This 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> |
796 | </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 | |
797 | |
| 813 | <warn> |
798 | <pre caption="Install the drivers and restart CUPS"> |
| 814 | The script <c>cups-samba.install</c> may not work for all *nixes (i.e. FreeBSD) |
799 | # <i>emerge -av cups-windows</i> |
| 815 | because almost everything which is not part of the base system is installed |
|
|
| 816 | somewhere under the prefix <path>/usr/local/</path>. This seems not to be the |
|
|
| 817 | case for most things you install under GNU/Linux. However, if your CUPS |
|
|
| 818 | installation is somewhere other than <path>/usr/share/cups/</path> see the |
|
|
| 819 | example below. |
|
|
| 820 | </warn> |
|
|
| 821 | |
|
|
| 822 | <p> |
|
|
| 823 | Suppose your CUPS installation resides under |
|
|
| 824 | <path>/usr/local/share/cups/</path>, and you want to install the drivers there. |
|
|
| 825 | Do the following: |
|
|
| 826 | </p> |
|
|
| 827 | |
|
|
| 828 | <pre caption="Manually installing the drivers"> |
|
|
| 829 | # <i>cd /path/you/extracted/the/CUPS-driver/tarball/into</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> |
800 | # <i>/etc/init.d/cupsd restart</i> |
| 836 | </pre> |
801 | </pre> |
| 837 | |
802 | |
| 838 | <p> |
803 | <p> |
| 839 | Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS distribution. |
804 | Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS distribution. |
| … | |
… | |
| 1025 | </section> |
990 | </section> |
| 1026 | <section> |
991 | <section> |
| 1027 | <title>Mounting a Windows or Samba share in GNU/Linux</title> |
992 | <title>Mounting a Windows or Samba share in GNU/Linux</title> |
| 1028 | <body> |
993 | <body> |
| 1029 | |
994 | |
|
|
995 | <note> |
|
|
996 | Don't forget to first <c>emerge samba</c> on the client(s) that that will be |
|
|
997 | accessing the shares. |
|
|
998 | </note> |
|
|
999 | |
| 1030 | <p> |
1000 | <p> |
| 1031 | Now is time to configure our kernel to support smbfs. Since I'm assumming we've |
1001 | Now is time to configure our kernel to support cifs. Since I'm assuming |
| 1032 | all compiled at least one kernel, we'll need to make sure we have all the right |
1002 | we've all compiled at least one kernel, we'll need to make sure we have all the |
| 1033 | options selected in our kernel. For simplicity's sake, make it a module for ease |
1003 | right options selected in our kernel. For simplicity's sake, make it a module |
| 1034 | of use. It is the author's opinion that kernel modules are a good thing and |
1004 | for ease of use. It is the author's opinion that kernel modules are a good thing |
| 1035 | should be used whenever possible. |
1005 | and should be used whenever possible. |
| 1036 | </p> |
|
|
| 1037 | |
|
|
| 1038 | <pre caption="Relevant kernel options" > |
|
|
| 1039 | CONFIG_SMB_FS=m |
|
|
| 1040 | CONFIG_SMB_UNIX=y |
|
|
| 1041 | </pre> |
|
|
| 1042 | |
|
|
| 1043 | <p> |
1006 | </p> |
|
|
1007 | |
|
|
1008 | <pre caption="Kernel support" > |
|
|
1009 | CONFIG_CIFS=m |
|
|
1010 | </pre> |
|
|
1011 | |
|
|
1012 | <p> |
| 1044 | Then make the module/install it; insert them with: |
1013 | Then make the module/install it; insert it with: |
| 1045 | </p> |
1014 | </p> |
| 1046 | |
1015 | |
| 1047 | <pre caption="Loading the kernel module"> |
1016 | <pre caption="Loading the kernel module"> |
| 1048 | # <i>modprobe smbfs</i> |
1017 | # <i>modprobe cifs</i> |
| 1049 | </pre> |
1018 | </pre> |
| 1050 | |
1019 | |
| 1051 | <p> |
1020 | <p> |
| 1052 | Once the module is loaded, mounting a Windows or Samba share is possible. Use |
1021 | Once the module is loaded, mounting a Windows or Samba share is possible. Use |
| 1053 | <c>mount</c> to accomplish this, as detailed below: |
1022 | <c>mount</c> to accomplish this, as detailed below: |
| 1054 | </p> |
1023 | </p> |
| 1055 | |
1024 | |
| 1056 | <pre caption="Mounting a Windows/Samba share"> |
1025 | <pre caption="Mounting a Windows/Samba share"> |
| 1057 | <comment>(The syntax for mounting a Windows/Samba share is: |
1026 | <comment>(The syntax for mounting a Windows/Samba share is: |
| 1058 | mount -t smbfs [-o username=xxx,password=xxx] //server/share /mnt/point |
1027 | mount -t cifs [-o username=xxx,password=xxx] //server/share /mnt/point |
| 1059 | If we are not using passwords or a password is not needed)</comment> |
1028 | If we are not using passwords or a password is not needed)</comment> |
| 1060 | |
1029 | |
| 1061 | # <i>mount -t smbfs //PrintServer/public /mnt/public</i> |
1030 | # <i>mount -t cifs //PrintServer/public /mnt/public</i> |
| 1062 | |
1031 | |
| 1063 | <comment>(If a password is needed)</comment> |
1032 | <comment>(If a password is needed)</comment> |
| 1064 | # <i>mount -t smbfs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i> |
1033 | # <i>mount -t cifs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i> |
| 1065 | </pre> |
1034 | </pre> |
| 1066 | |
1035 | |
| 1067 | <p> |
1036 | <p> |
| 1068 | After you mount the share, you would access it as if it were a local drive. |
1037 | After you mount the share, you would access it as if it were a local drive. |
| 1069 | </p> |
1038 | </p> |
Parent Directory
| 
Revision Log
| 
Patch