| 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.28 2007/06/06 22:42:25 nightmorph Exp $ --> |
2 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.34 2007/09/15 16:47:56 swift 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 |
17 | Setup, install and configure a Samba Server under Gentoo that shares files, |
| 15 | files, printers without the need to install drivers and provides |
18 | printers without the need to install drivers and provides automatic virus |
| 16 | automatic virus scanning. |
19 | scanning. |
| 17 | </abstract> |
20 | </abstract> |
| 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.21</version> |
| 24 | <date>2007-06-06</date> |
27 | <date>2007-09-15</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> |
| 30 | <body> |
33 | <body> |
| 31 | |
34 | |
| 32 | <p> |
35 | <p> |
| 33 | This HOWTO is designed to help you move a network from many different |
36 | This HOWTO is designed to help you move a network from many different clients |
| 34 | clients speaking different languages, to many different machines that |
37 | speaking different languages, to many different machines that speak a common |
| 35 | speak a common language. The ultimate goal is to help differing |
38 | language. The ultimate goal is to help differing architectures and technologies, |
| 36 | architectures and technologies, come together in a productive, |
39 | come together in a productive, happily coexisting environment. |
| 37 | happily coexisting environment. |
|
|
| 38 | </p> |
|
|
| 39 | |
|
|
| 40 | <p> |
40 | </p> |
|
|
41 | |
|
|
42 | <p> |
| 41 | Following the directions outlined in this HOWTO should give you an |
43 | Following the directions outlined in this HOWTO should give you an excellent |
| 42 | excellent step towards a peaceful cohabitation between Windows, and |
44 | step towards a peaceful cohabitation between Windows, and virtually all known |
| 43 | virtually all known variations of *nix. |
45 | variations of *nix. |
| 44 | </p> |
|
|
| 45 | |
|
|
| 46 | <p> |
46 | </p> |
|
|
47 | |
|
|
48 | <p> |
| 47 | This HOWTO originally started not as a HOWTO, but as a FAQ. It was |
49 | This HOWTO originally started not as a HOWTO, but as a FAQ. It was intended to |
| 48 | intended to explore the functionality and power of the Gentoo system, |
50 | explore the functionality and power of the Gentoo system, portage and the |
| 49 | portage and the flexibility of USE flags. Like so many other projects, |
51 | flexibility of USE flags. Like so many other projects, it was quickly discovered |
| 50 | it was quickly discovered what was missing in the Gentoo realm: there |
52 | what was missing in the Gentoo realm: there weren't any Samba HOWTO's catered |
| 51 | weren't any Samba HOWTO's catered for Gentoo users. These users are |
53 | for Gentoo users. These users are more demanding than most; they require |
| 52 | more demanding than most; they require performance, flexibility and |
54 | performance, flexibility and customization. This does not however imply that |
| 53 | customization. This does not however imply that this HOWTO was not |
|
|
| 54 | intended for other distributions; rather that it was designed to work |
55 | this HOWTO was not intended for other distributions; rather that it was designed |
| 55 | with a highly customized version of Samba. |
56 | to work with a highly customized version of Samba. |
| 56 | </p> |
|
|
| 57 | |
|
|
| 58 | <p> |
57 | </p> |
|
|
58 | |
|
|
59 | <p> |
| 59 | This HOWTO will describe how to share files and printers between Windows |
60 | This HOWTO will describe how to share files and printers between Windows PCs and |
| 60 | PCs and *nix PCs. It will also demonstrate the use of the VFS (Virtual |
61 | *nix PCs. It will also demonstrate the use of the VFS (Virtual File System) |
| 61 | File System) feature of Samba to incorporate automatic virus protection. |
62 | feature of Samba to incorporate automatic virus protection. As a finale, it will |
| 62 | As a finale, it will show you how to mount and manipulate shares. |
63 | show you how to mount and manipulate shares. |
| 63 | </p> |
|
|
| 64 | |
|
|
| 65 | <p> |
64 | </p> |
|
|
65 | |
|
|
66 | <p> |
| 66 | There are a few topics that will be mentioned, but are out of the |
67 | There are a few topics that will be mentioned, but are out of the scope of this |
| 67 | scope of this HOWTO. These will be noted as they are presented. |
68 | HOWTO. These will be noted as they are presented. |
| 68 | </p> |
|
|
| 69 | |
|
|
| 70 | <p> |
69 | </p> |
|
|
70 | |
|
|
71 | <p> |
| 71 | This HOWTO is based on a compilation and merge of an excellent HOWTO |
72 | This HOWTO is based on a compilation and merge of an excellent HOWTO provided in |
| 72 | provided in the <uri link="http://forums.gentoo.org">Gentoo forums</uri> |
73 | the <uri link="http://forums.gentoo.org">Gentoo forums</uri> by Andreas "daff" |
| 73 | by Andreas "daff" Ntaflos and the collected knowledge of Joshua Preston. |
74 | Ntaflos and the collected knowledge of Joshua Preston. The link to this |
| 74 | The link to this discussion is provided below for your reference: |
75 | discussion is provided below for your reference: |
| 75 | </p> |
76 | </p> |
| 76 | |
77 | |
| 77 | <ul> |
78 | <ul> |
| 78 | <li> |
79 | <li> |
| 79 | <uri link="http://forums.gentoo.org/viewtopic.php?t=110931">HOWTO |
80 | <uri link="http://forums.gentoo.org/viewtopic.php?t=110931">HOWTO |
| … | |
… | |
| 87 | <title>Before you use this guide</title> |
88 | <title>Before you use this guide</title> |
| 88 | <body> |
89 | <body> |
| 89 | |
90 | |
| 90 | <p> |
91 | <p> |
| 91 | There are a several other guides for setting up CUPS and/or Samba, please read |
92 | There are a several other guides for setting up CUPS and/or Samba, please read |
| 92 | them as well, as they may tell you things left out of this HOWTO (intentional |
93 | them as well, as they may tell you things left out of this HOWTO (intentional or |
| 93 | or otherwise). One such document is the very useful and well written <uri |
94 | otherwise). One such document is the very useful and well written <uri |
| 94 | link="/doc/en/printing-howto.xml">Gentoo Printing Guide</uri>, as configuration |
95 | link="/doc/en/printing-howto.xml">Gentoo Printing Guide</uri>, as configuration |
| 95 | issues and specific printer setup is not discussed here. |
96 | issues and specific printer setup is not discussed here. |
| 96 | </p> |
97 | </p> |
| 97 | |
98 | |
| 98 | </body> |
99 | </body> |
| … | |
… | |
| 100 | <section> |
101 | <section> |
| 101 | <title>Brief Overview</title> |
102 | <title>Brief Overview</title> |
| 102 | <body> |
103 | <body> |
| 103 | |
104 | |
| 104 | <p> |
105 | <p> |
| 105 | After presenting the various USE flags, the following list will outline |
106 | After presenting the various USE flags, the following list will outline all of |
| 106 | all of the topics covered as they are presented: |
107 | the topics covered as they are presented: |
| 107 | </p> |
108 | </p> |
| 108 | |
109 | |
| 109 | <ul> |
110 | <ul> |
| 110 | <li>On the Samba server: |
111 | <li>On the Samba server: |
| 111 | <ul> |
112 | <ul> |
| … | |
… | |
| 153 | A working network (home/office/etc) consisting of more than one machine) |
154 | A working network (home/office/etc) consisting of more than one machine) |
| 154 | </li> |
155 | </li> |
| 155 | </ul> |
156 | </ul> |
| 156 | |
157 | |
| 157 | <p> |
158 | <p> |
| 158 | The main package we use here is net-fs/samba, however, you will need |
159 | The main package we use here is net-fs/samba, however, you will need a kernel |
| 159 | a kernel with smbfs support enabled in order to mount a samba or windows |
160 | with cifs support enabled in order to mount a samba or windows share from |
| 160 | share from another computer. CUPS will be emerged if it is not already. |
161 | another computer. CUPS will be emerged if it is not already. |
| 161 | app-antivirus/clamav will be used also, but others should be easily adapted |
162 | app-antivirus/clamav will be used also, but others should be easily adapted to |
| 162 | to 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 |
| 163 | technologies, such as Sophos, FProt, Fsav, Trend, Icap, Nai, ... |
164 | technologies, such as Sophos, FProt, Fsav, Trend, Icap, Nai, ... |
| 164 | </p> |
165 | </p> |
| 165 | |
166 | |
| 166 | </body> |
167 | </body> |
| 167 | </section> |
168 | </section> |
| … | |
… | |
| 181 | <pre caption="Samba uses the following USE Variables:"> |
182 | <pre caption="Samba uses the following USE Variables:"> |
| 182 | kerberos acl cups ldap pam readline python oav |
183 | kerberos acl cups ldap pam readline python oav |
| 183 | </pre> |
184 | </pre> |
| 184 | |
185 | |
| 185 | <p> |
186 | <p> |
| 186 | Depending on the network topology and the specific requirements of |
187 | Depending on the network topology and the specific requirements of the server, |
| 187 | the server, the USE flags outlined below will define what to include or |
188 | the USE flags outlined below will define what to include or exclude from the |
| 188 | exclude from the emerging of Samba. |
189 | emerging of Samba. |
| 189 | </p> |
190 | </p> |
| 190 | |
191 | |
| 191 | <table> |
192 | <table> |
| 192 | <tr> |
193 | <tr> |
| 193 | <th><b>USE flag</b></th> |
194 | <th><b>USE flag</b></th> |
| … | |
… | |
| 211 | </ti> |
212 | </ti> |
| 212 | </tr> |
213 | </tr> |
| 213 | <tr> |
214 | <tr> |
| 214 | <th><b>cups</b></th> |
215 | <th><b>cups</b></th> |
| 215 | <ti> |
216 | <ti> |
| 216 | This enables support for the Common Unix Printing System. This |
217 | This enables support for the Common Unix Printing System. This provides an |
| 217 | provides an interface allowing local CUPS printers to be shared to |
218 | interface allowing local CUPS printers to be shared to other systems in the |
| 218 | other systems in the network. |
219 | network. |
| 219 | </ti> |
220 | </ti> |
| 220 | </tr> |
221 | </tr> |
| 221 | <tr> |
222 | <tr> |
| 222 | <th><b>ldap</b></th> |
223 | <th><b>ldap</b></th> |
| 223 | <ti> |
224 | <ti> |
| 224 | Enables the Lightweight Directory Access Protocol (LDAP). If Samba is |
225 | Enables the Lightweight Directory Access Protocol (LDAP). If Samba is |
| 225 | expected to use Active Directory, this option must be used. This would |
226 | expected to use Active Directory, this option must be used. This would be |
| 226 | be used in the event Samba needs to login to or provide login to |
227 | used in the event Samba needs to login to or provide login to a |
| 227 | a Domain/Active Directory Server. The kerberos USE flag is needed for |
228 | Domain/Active Directory Server. The kerberos USE flag is needed for proper |
| 228 | proper functioning of this option. |
229 | functioning of this option. |
| 229 | </ti> |
230 | </ti> |
| 230 | </tr> |
231 | </tr> |
| 231 | <tr> |
232 | <tr> |
| 232 | <th><b>pam</b></th> |
233 | <th><b>pam</b></th> |
| 233 | <ti> |
234 | <ti> |
| 234 | Include support for pluggable authentication modules (PAM). This |
235 | Include support for pluggable authentication modules (PAM). This provides |
| 235 | provides the ability to authenticate users on the Samba Server, which is |
236 | the ability to authenticate users on the Samba Server, which is required if |
| 236 | required if users have to login to your server. The kerberos USE flag |
237 | users have to login to your server. The kerberos USE flag is recommended |
| 237 | is recommended along with this option. |
238 | along with this option. |
| 238 | </ti> |
239 | </ti> |
| 239 | </tr> |
240 | </tr> |
| 240 | <tr> |
241 | <tr> |
| 241 | <th><b>readline</b></th> |
242 | <th><b>readline</b></th> |
| 242 | <ti> |
243 | <ti> |
| 243 | Link Samba against libreadline. This is highly recommended and should |
244 | Link Samba against libreadline. This is highly recommended and should |
| 244 | probably not be disabled |
245 | probably not be disabled. |
| 245 | </ti> |
246 | </ti> |
| 246 | </tr> |
247 | </tr> |
| 247 | <tr> |
248 | <tr> |
| 248 | <th><b>python</b></th> |
249 | <th><b>python</b></th> |
| 249 | <ti> |
250 | <ti> |
| 250 | Python bindings API. Provides an API that will allow Python to |
251 | Python bindings API. Provides an API that will allow Python to interface |
| 251 | interface with Samba. |
252 | with Samba. |
| 252 | </ti> |
253 | </ti> |
| 253 | </tr> |
254 | </tr> |
| 254 | <tr> |
255 | <tr> |
| 255 | <th><b>oav</b></th> |
256 | <th><b>oav</b></th> |
| 256 | <ti> |
257 | <ti> |
| 257 | Provides on-access scanning of Samba shares with FRISK F-Prot |
258 | Provides on-access scanning of Samba shares with FRISK F-Prot Daemon, |
| 258 | Daemon, Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep |
259 | Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep (SAVI), |
| 259 | (SAVI), Symantec CarrierScan, and Trend Micro (VSAPI). |
260 | Symantec CarrierScan, and Trend Micro (VSAPI). |
| 260 | </ti> |
261 | </ti> |
| 261 | </tr> |
262 | </tr> |
| 262 | </table> |
263 | </table> |
| 263 | |
264 | |
| 264 | <p> |
265 | <p> |
| … | |
… | |
| 291 | <section> |
292 | <section> |
| 292 | <title>Emerging Samba</title> |
293 | <title>Emerging Samba</title> |
| 293 | <body> |
294 | <body> |
| 294 | |
295 | |
| 295 | <p> |
296 | <p> |
| 296 | First of all: be sure that all your hostnames resolve correctly. |
297 | First of all: be sure that all your hostnames resolve correctly. Either have a |
| 297 | Either have a working domain name system running on your network |
298 | working domain name system running on your network or appropriate entries in |
| 298 | or appropriate entries in your <path>/etc/hosts</path> file. |
299 | your <path>/etc/hosts</path> file. <c>cupsaddsmb</c> often borks if hostnames |
| 299 | <c>cupsaddsmb</c> often borks if hostnames don't point to the correct |
300 | don't point to the correct machines. |
| 300 | machines. |
|
|
| 301 | </p> |
|
|
| 302 | |
|
|
| 303 | <p> |
301 | </p> |
|
|
302 | |
|
|
303 | <p> |
| 304 | Hopefully now you can make an assessment of what you'll actually need in |
304 | Hopefully now you can make an assessment of what you'll actually need in order |
| 305 | order to use Samba with your particular setup. The setup used for this |
305 | to use Samba with your particular setup. The setup used for this HOWTO is: |
| 306 | HOWTO is: |
|
|
| 307 | </p> |
306 | </p> |
| 308 | |
307 | |
| 309 | <ul> |
308 | <ul> |
| 310 | <li>oav</li> |
309 | <li>oav</li> |
| 311 | <li>cups</li> |
310 | <li>cups</li> |
| 312 | <li>readline</li> |
311 | <li>readline</li> |
| 313 | <li>pam</li> |
312 | <li>pam</li> |
| 314 | </ul> |
313 | </ul> |
| 315 | |
314 | |
| 316 | <p> |
315 | <p> |
| 317 | To optimize performance, size and the time of the build, the |
316 | To optimize performance, size and the time of the build, the USE flags are |
| 318 | USE flags are specifically included or excluded. |
317 | specifically included or excluded. |
| 319 | </p> |
318 | </p> |
| 320 | |
319 | |
| 321 | <pre caption="Emerge Samba"> |
320 | <pre caption="Emerge Samba"> |
| 322 | # <i>echo "net-fs/samba oav readline cups pam" >> /etc/portage/package.use</i> |
321 | # <i>echo "net-fs/samba oav readline cups pam" >> /etc/portage/package.use</i> |
| 323 | # <i>emerge net-fs/samba</i> |
322 | # <i>emerge net-fs/samba</i> |
| 324 | </pre> |
323 | </pre> |
| 325 | |
324 | |
| 326 | <note> |
325 | <note> |
| 327 | The following archs will need to add <e>~</e> to their <e>KEYWORDS</e>: x86, |
326 | The following arches will need to add <e>~</e> to their <e>KEYWORDS</e>: x86, |
| 328 | ppc, sparc, hppa, ia64 and alpha |
327 | ppc, sparc, hppa, ia64 and alpha |
| 329 | </note> |
328 | </note> |
| 330 | |
329 | |
| 331 | <p> |
330 | <p> |
| 332 | This will emerge Samba and CUPS (if CUPS is not already emerged). |
331 | This will emerge Samba and CUPS (if CUPS is not already emerged). |
| … | |
… | |
| 337 | <section> |
336 | <section> |
| 338 | <title>Emerging ClamAV</title> |
337 | <title>Emerging ClamAV</title> |
| 339 | <body> |
338 | <body> |
| 340 | |
339 | |
| 341 | <p> |
340 | <p> |
| 342 | Because the <e>oav</e> USE flag only provides an interface to allow on access |
341 | Because the <e>oav</e> USE flag only provides an interface to allow on access |
| 343 | virus scanning, the actual virus scanner must be emerged. The scanner |
342 | virus scanning, the actual virus scanner must be emerged. The scanner used in |
| 344 | used in this HOWTO is ClamAV. |
343 | this HOWTO is ClamAV. |
| 345 | </p> |
344 | </p> |
| 346 | |
345 | |
| 347 | <pre caption="Emerge Clamav"> |
346 | <pre caption="Emerge Clamav"> |
| 348 | # <i>emerge app-antivirus/clamav</i> |
347 | # <i>emerge app-antivirus/clamav</i> |
| 349 | </pre> |
348 | </pre> |
| … | |
… | |
| 381 | <section> |
380 | <section> |
| 382 | <title>Configuring Samba</title> |
381 | <title>Configuring Samba</title> |
| 383 | <body> |
382 | <body> |
| 384 | |
383 | |
| 385 | <p> |
384 | <p> |
| 386 | The main Samba configuration file is <path>/etc/samba/smb.conf</path>. |
385 | The main Samba configuration file is <path>/etc/samba/smb.conf</path>. It is |
| 387 | It is divided in sections indicated by [sectionname]. Comments are either |
386 | divided in sections indicated by [sectionname]. Comments are either |
| 388 | # or ;. A sample <path>smb.conf</path> is included below with comments and |
387 | # or ;. A sample <path>smb.conf</path> is included below with comments and |
| 389 | suggestions for modifications. If more details are required, see the |
388 | suggestions for modifications. If more details are required, see the man page |
| 390 | man page for <path>smb.conf</path>, the installed |
389 | for <path>smb.conf</path>, the installed <path>smb.conf.example</path>, the |
| 391 | <path>smb.conf.example</path>, the Samba Web site or any of the |
390 | Samba Web site or any of the numerous Samba books available. |
| 392 | numerous Samba books available. |
|
|
| 393 | </p> |
391 | </p> |
| 394 | |
392 | |
| 395 | <pre caption="A Sample /etc/samba/smb.conf"> |
393 | <pre caption="A Sample /etc/samba/smb.conf"> |
| 396 | [global] |
394 | [global] |
| 397 | <comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment> |
395 | <comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment> |
| … | |
… | |
| 421 | hosts deny = 0.0.0.0/0 |
419 | hosts deny = 0.0.0.0/0 |
| 422 | <comment># Other options for this are USER, DOMAIN, ADS, and SERVER |
420 | <comment># Other options for this are USER, DOMAIN, ADS, and SERVER |
| 423 | # The default is user</comment> |
421 | # The default is user</comment> |
| 424 | security = share |
422 | security = share |
| 425 | <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> |
| 426 | guest account = samba |
|
|
| 427 | guest ok = yes |
424 | guest ok = yes |
| 428 | <comment># We now will implement the on access virus scanner. |
425 | <comment># We now will implement the on access virus scanner. |
| 429 | # NOTE: By putting this in our [Global] section, we enable |
426 | # NOTE: By putting this in our [Global] section, we enable |
| 430 | # scanning of ALL shares, you could optionally move |
427 | # scanning of ALL shares, you could optionally move |
| 431 | # these to a specific share and only scan it.</comment> |
428 | # these to a specific share and only scan it.</comment> |
| … | |
… | |
| 482 | guest ok = yes |
479 | guest ok = yes |
| 483 | path = /home/samba/public |
480 | path = /home/samba/public |
| 484 | </pre> |
481 | </pre> |
| 485 | |
482 | |
| 486 | <warn> |
483 | <warn> |
| 487 | If you like to use Samba's guest account to do anything concerning |
484 | If you like to use Samba's guest account to do anything concerning printing from |
| 488 | printing from Windows clients: don't set <c>guest only = yes</c> in |
485 | Windows clients: don't set <c>guest only = yes</c> in the <c>[global]</c> |
| 489 | the <c>[global]</c> section. The guest account seems to cause |
486 | section. The guest account seems to cause problems when running |
| 490 | problems when running <c>cupsaddsmb</c> sometimes when trying to |
487 | <c>cupsaddsmb</c> sometimes when trying to connect from Windows machines. See |
| 491 | connect from Windows machines. See below, too, when we talk about |
488 | below, too, when we talk about <c>cupsaddsmb</c> and the problems that can |
| 492 | <c>cupsaddsmb</c> and the problems that can arise. Use a dedicated |
|
|
| 493 | printer user, like <c>printeruser</c> or <c>printer</c> or |
489 | arise. Use a dedicated printer user, like <c>printeruser</c> or <c>printer</c> |
| 494 | <c>printme</c> or whatever. It doesn't hurt and it will certainly |
490 | or <c>printme</c> or whatever. It doesn't hurt and it will certainly protect you |
| 495 | protect you from a lot of problems. |
491 | from a lot of problems. |
| 496 | </warn> |
492 | </warn> |
| 497 | |
493 | |
| 498 | <warn> |
494 | <warn> |
| 499 | Turning on ClamAV on access scanning in the <c>[global]</c> section will slow |
495 | Turning on ClamAV on access scanning in the <c>[global]</c> section will slow |
| 500 | down the performance of your Samba server dramatically. |
496 | down the performance of your Samba server dramatically. |
| 501 | </warn> |
497 | </warn> |
| 502 | |
498 | |
| 503 | <p> |
499 | <p> |
| 504 | Now create the directories required for the minimum configuration of |
500 | Now create the directories required for the minimum configuration of Samba to |
| 505 | Samba to share the installed printer throughout the network. |
501 | share the installed printer throughout the network. |
| 506 | </p> |
502 | </p> |
| 507 | |
503 | |
| 508 | <pre caption="Create the directories"> |
504 | <pre caption="Create the directories"> |
| 509 | # <i>mkdir /etc/samba/printer</i> |
505 | # <i>mkdir /etc/samba/printer</i> |
| 510 | # <i>mkdir /var/spool/samba</i> |
506 | # <i>mkdir /var/spool/samba</i> |
| 511 | # <i>mkdir /home/samba/public</i> |
507 | # <i>mkdir /home/samba/public</i> |
| 512 | </pre> |
508 | </pre> |
| 513 | |
509 | |
| 514 | <p> |
510 | <p> |
| 515 | At least one Samba user is required in order to install the printer |
511 | At least one Samba user is required in order to install the printer drivers and |
| 516 | drivers and to allow users to connect to the printer. Users must |
512 | to allow users to connect to the printer. Users must exist in the system's |
| 517 | exist in the system's <path>/etc/passwd</path> file. |
513 | <path>/etc/passwd</path> file. |
| 518 | </p> |
514 | </p> |
| 519 | |
515 | |
| 520 | <pre caption="Creating the users"> |
516 | <pre caption="Creating the users"> |
| 521 | # <i>smbpasswd -a root</i> |
517 | # <i>smbpasswd -a root</i> |
| 522 | |
518 | |
| … | |
… | |
| 545 | <section> |
541 | <section> |
| 546 | <title>Configuring ClamAV</title> |
542 | <title>Configuring ClamAV</title> |
| 547 | <body> |
543 | <body> |
| 548 | |
544 | |
| 549 | <p> |
545 | <p> |
| 550 | The configuration file specified to be used in <path>smb.conf</path> is |
546 | The configuration file specified to be used in <path>smb.conf</path> is |
| 551 | <path>/etc/samba/vscan-clamav.conf</path>. While these options are set |
547 | <path>/etc/samba/vscan-clamav.conf</path>. While these options are set to the |
| 552 | to the defaults, the infected file action may need to be changed. |
548 | defaults, the infected file action may need to be changed. |
| 553 | </p> |
549 | </p> |
| 554 | |
550 | |
| 555 | <pre caption="/etc/samba/vscan-clamav.conf"> |
551 | <pre caption="/etc/samba/vscan-clamav.conf"> |
| 556 | [samba-vscan] |
552 | [samba-vscan] |
| 557 | <comment>; run-time configuration for vscan-samba using |
553 | <comment>; run-time configuration for vscan-samba using |
| … | |
… | |
| 614 | <comment>; port number the ScannerDaemon listens on</comment> |
610 | <comment>; port number the ScannerDaemon listens on</comment> |
| 615 | oav port = 8127 |
611 | oav port = 8127 |
| 616 | </pre> |
612 | </pre> |
| 617 | |
613 | |
| 618 | <p> |
614 | <p> |
| 619 | It is generally a good idea to start the virus scanner immediately. Add |
615 | It is generally a good idea to start the virus scanner immediately. Add it to |
| 620 | it to the <e>default</e> runlevel and then start the <c>clamd</c> service |
616 | the <e>default</e> runlevel and then start the <c>clamd</c> service immediately. |
| 621 | immediately. The service has two processes: freshclam keeps the virus definition |
617 | The service has two processes: freshclam keeps the virus definition database up |
| 622 | database up to date while clamd is the actual anti-virus daemon. First you may |
618 | to date while clamd is the actual anti-virus daemon. First you may want to set |
| 623 | want to set the paths of the logfiles so that it fits your needs. |
619 | the paths of the logfiles so that it fits your needs. |
| 624 | </p> |
620 | </p> |
| 625 | |
621 | |
| 626 | <pre caption="Checking the location of the logfiles"> |
622 | <pre caption="Checking the location of the logfiles"> |
| 627 | # <i>vim /etc/clamd.conf</i> |
623 | # <i>vim /etc/clamd.conf</i> |
| 628 | <comment>(Check the line "LogFile /var/log/clamd.log")</comment> |
624 | <comment>(Check the line "LogFile /var/log/clamd.log")</comment> |
| … | |
… | |
| 646 | <section> |
642 | <section> |
| 647 | <title>Configuring CUPS</title> |
643 | <title>Configuring CUPS</title> |
| 648 | <body> |
644 | <body> |
| 649 | |
645 | |
| 650 | <p> |
646 | <p> |
| 651 | This is a little more complicated. CUPS' main config file is |
647 | This is a little more complicated. CUPS' main config file is |
| 652 | <path>/etc/cups/cupsd.conf</path>. It's structure is similar to Apache's |
648 | <path>/etc/cups/cupsd.conf</path>. It's structure is similar to Apache's |
| 653 | <path>httpd.conf</path> file, so many you may find it familiar. Outlined |
649 | <path>httpd.conf</path> file, so many you may find it familiar. Outlined in the |
| 654 | in the example are the directives that need to be changed: |
650 | example are the directives that need to be changed: |
| 655 | </p> |
651 | </p> |
| 656 | |
652 | |
| 657 | <pre caption="/etc/cups/cupsd.conf"> |
653 | <pre caption="/etc/cups/cupsd.conf"> |
| 658 | ServerName <i>PrintServer</i> <comment># your printserver name</comment> |
654 | ServerName <i>PrintServer</i> <comment># your printserver name</comment> |
| 659 | ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, e.g. you</comment> |
655 | ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, e.g. you</comment> |
| … | |
… | |
| 730 | <p> |
726 | <p> |
| 731 | First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to |
727 | First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to |
| 732 | find and download the correct PPD file for your printer and CUPS. To do so, |
728 | find and download the correct PPD file for your printer and CUPS. To do so, |
| 733 | click the link Printer Listings to the left. Select your printers manufacturer |
729 | click the link Printer Listings to the left. Select your printers manufacturer |
| 734 | and the model in the pulldown menu, e.g. HP and DeskJet 930C. Click "Show". On |
730 | and the model in the pulldown menu, e.g. HP and DeskJet 930C. Click "Show". On |
| 735 | the page coming up click the "recommended driver" link after reading the |
731 | the page coming up click the "recommended driver" link after reading the various |
| 736 | various notes and information. Then fetch the PPD file from the next page, |
732 | notes and information. Then fetch the PPD file from the next page, again after |
| 737 | again after reading the notes and introductions there. You may have to select |
733 | reading the notes and introductions there. You may have to select your printers |
| 738 | your printers manufacturer and model again. Reading the <uri |
734 | manufacturer and model again. Reading the <uri |
| 739 | link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri> |
735 | link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri> is |
| 740 | is also very helpful when working with CUPS. |
736 | also very helpful when working with CUPS. |
| 741 | </p> |
|
|
| 742 | |
|
|
| 743 | <p> |
737 | </p> |
|
|
738 | |
|
|
739 | <p> |
| 744 | Now you have a PPD file for your printer to work with CUPS. Place it in |
740 | Now you have a PPD file for your printer to work with CUPS. Place it in |
| 745 | <path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was |
741 | <path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was named |
| 746 | named <path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer. |
742 | <path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer. |
| 747 | This can be done via the CUPS web interface or via command line. The web |
743 | This can be done via the CUPS web interface or via command line. The web |
| 748 | interface is found at <path>http://PrintServer:631</path> once CUPS is running. |
744 | interface is found at <path>http://PrintServer:631</path> once CUPS is running. |
| 749 | </p> |
745 | </p> |
| 750 | |
746 | |
| 751 | <pre caption="Install the printer via command line"> |
747 | <pre caption="Install the printer via command line"> |
| 752 | # <i>lpadmin -p HPDeskJet930C -E -v usb:/dev/ultp0 -m HP-DeskJet_930C-hpijs.ppd</i> |
748 | # <i>lpadmin -p HPDeskJet930C -E -v usb:/dev/ultp0 -m HP-DeskJet_930C-hpijs.ppd</i> |
| 753 | # <i>/etc/init.d/cupsd restart</i> |
749 | # <i>/etc/init.d/cupsd restart</i> |
| 754 | </pre> |
750 | </pre> |
| 755 | |
751 | |
| 756 | <p> |
752 | <p> |
| 757 | Remember to adjust to what you have. Be sure to have the name |
753 | Remember to adjust to what you have. Be sure to have the name (<c>-p</c> |
| 758 | (<c>-p</c> argument) right (the name you set above during the Samba |
754 | argument) right (the name you set above during the Samba configuration!) and to |
| 759 | configuration!) and to put in the correct <c>usb:/dev/usb/blah</c>, |
755 | put in the correct <c>usb:/dev/usb/blah</c>, <c>parallel:/dev/blah</c> or |
| 760 | <c>parallel:/dev/blah</c> or whatever device you are using for your |
756 | whatever device you are using for your printer. |
| 761 | printer. |
|
|
| 762 | </p> |
|
|
| 763 | |
|
|
| 764 | <p> |
757 | </p> |
|
|
758 | |
|
|
759 | <p> |
| 765 | You should now be able to access the printer from the web interface |
760 | You should now be able to access the printer from the web interface and be able |
| 766 | and be able to print a test page. |
761 | to print a test page. |
| 767 | </p> |
762 | </p> |
| 768 | |
763 | |
| 769 | </body> |
764 | </body> |
| 770 | </section> |
765 | </section> |
| 771 | <section> |
766 | <section> |
| 772 | <title>Installing the Windows printer drivers</title> |
767 | <title>Installing the Windows printer drivers</title> |
| 773 | <body> |
768 | <body> |
| 774 | |
769 | |
| 775 | <p> |
770 | <p> |
| 776 | Now that the printer should be working it is time to install the drivers |
771 | Now that the printer should be working it is time to install the drivers for the |
| 777 | for the Windows clients to work. Samba 2.2 introduced this functionality. |
772 | Windows clients to work. Samba 2.2 introduced this functionality. Browsing to |
| 778 | Browsing to the print server in the Network Neighbourhood, right-clicking |
773 | the print server in the Network Neighbourhood, right-clicking on the |
| 779 | on the printershare and selecting "connect" downloads the appropriate |
774 | printershare and selecting "connect" downloads the appropriate drivers |
| 780 | drivers automagically to the connecting client, avoiding the hassle of |
775 | automagically to the connecting client, avoiding the hassle of manually |
| 781 | manually installing printer drivers locally. |
776 | installing printer drivers locally. |
| 782 | </p> |
777 | </p> |
| 783 | |
778 | |
| 784 | <p> |
779 | <p> |
| 785 | There are two sets of printer drivers for this. First, the Adobe PS drivers |
780 | There are two sets of printer drivers for this. First, the Adobe PS drivers |
| 786 | which can be obtained from <uri |
781 | which can be obtained from <uri |
| 787 | link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript |
782 | link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript |
| 788 | printer drivers). Second, there are the CUPS PS drivers, to be obtained <uri |
783 | printer drivers). Second, there are the CUPS PS drivers, to be obtained by |
| 789 | link="http://dev.gentoo.org/~nightmorph/misc/cups-samba-5.0rc2.tar.gz">here</uri>. |
784 | emerging <c>net-print/cups-windows</c>. Note that it may still be marked ~arch, |
|
|
785 | so you may need to add it to <path>/etc/portage/package.keywords</path>. There |
| 790 | There doesn't seem to be a difference between the functionality of the two, but |
786 | doesn't seem to be a difference between the functionality of the two, but the |
| 791 | the Adobe PS drivers need to be extracted on a Windows System since it's a |
787 | Adobe PS drivers need to be extracted on a Windows System since it's a Windows |
| 792 | Windows binary. Also the whole procedure of finding and copying the correct |
788 | binary. Also the whole procedure of finding and copying the correct files is a |
| 793 | files is a bit more hassle. The CUPS drivers seem to support some options the |
789 | bit more hassle. The CUPS drivers seem to support some options the Adobe drivers |
| 794 | Adobe drivers don't. |
790 | don't. |
| 795 | </p> |
|
|
| 796 | <!-- |
|
|
| 797 | used to be available at www.cups.org/articles.php?L142+p4, but only 6.0 is |
|
|
| 798 | available. at some point, we should update this for 6.0. |
|
|
| 799 | --> |
|
|
| 800 | |
|
|
| 801 | <p> |
791 | </p> |
| 802 | This HOWTO uses the CUPS drivers for Windows. The downloaded file is |
792 | |
| 803 | called <path>cups-samba-5.0rc2.tar.gz</path>. Extract the files |
|
|
| 804 | contained into a directory. |
|
|
| 805 | </p> |
793 | <p> |
| 806 | |
794 | This HOWTO uses the CUPS drivers for Windows. Install them as shown: |
| 807 | <pre caption="Extract the drivers and run the install"> |
|
|
| 808 | # <i>tar -xzf cups-samba-5.0rc2.tar.gz</i> |
|
|
| 809 | # <i>cd cups-samba-5.0rc2</i> |
|
|
| 810 | <comment>(Only use this script if CUPS resides in /usr/share/cups)</comment> |
|
|
| 811 | # <i>./cups-samba.install</i> |
|
|
| 812 | </pre> |
|
|
| 813 | |
|
|
| 814 | <p> |
795 | </p> |
| 815 | <path>cups-samba.ss</path> is a TAR archive containing three files: |
|
|
| 816 | <path>cups5.hlp</path>, <path>cupsdrvr5.dll</path> and |
|
|
| 817 | <path>cupsui5.dll</path>. These are the actual driver files. |
|
|
| 818 | </p> |
|
|
| 819 | |
796 | |
| 820 | <warn> |
797 | <pre caption="Install the drivers and restart CUPS"> |
| 821 | The script <c>cups-samba.install</c> may not work for all *nixes (i.e. FreeBSD) |
798 | # <i>emerge -av cups-windows</i> |
| 822 | because almost everything which is not part of the base system is |
|
|
| 823 | installed somewhere under the prefix <path>/usr/local/</path>. This |
|
|
| 824 | seems not to be the case for most things you install under GNU/Linux. |
|
|
| 825 | However, if your CUPS installation is somewhere other than |
|
|
| 826 | <path>/usr/share/cups/</path> see the example below. |
|
|
| 827 | </warn> |
|
|
| 828 | |
|
|
| 829 | <p> |
|
|
| 830 | Suppose your CUPS installation resides under |
|
|
| 831 | <path>/usr/local/share/cups/</path>, and you want to install the drivers there. |
|
|
| 832 | Do the following: |
|
|
| 833 | </p> |
|
|
| 834 | |
|
|
| 835 | <pre caption="Manually installing the drivers"> |
|
|
| 836 | # <i>cd /path/you/extracted/the/CUPS-driver/tarball/into</i> |
|
|
| 837 | # <i>tar -xf cups-samba.ss</i> |
|
|
| 838 | <comment>(This extracts the files to usr/share/cups/drivers under the CURRENT WORKING DIRECTORY)</comment> |
|
|
| 839 | # <i>cd usr/share/cups/drivers</i> |
|
|
| 840 | <comment>(no leading / !)</comment> |
|
|
| 841 | # <i>cp cups* /usr/local/share/cups/drivers</i> |
|
|
| 842 | # <i>/etc/init.d/cupsd restart</i> |
799 | # <i>/etc/init.d/cupsd restart</i> |
| 843 | </pre> |
800 | </pre> |
| 844 | |
801 | |
| 845 | <p> |
802 | <p> |
| 846 | Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS distribution. |
803 | Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS distribution. |
| … | |
… | |
| 865 | </p> |
822 | </p> |
| 866 | |
823 | |
| 867 | <ul> |
824 | <ul> |
| 868 | <li> |
825 | <li> |
| 869 | The hostname given as a parameter for <c>-h</c> and <c>-H</c> |
826 | The hostname given as a parameter for <c>-h</c> and <c>-H</c> |
| 870 | (<c>PrintServer</c>) often does not resolve correctly and doesn't |
827 | (<c>PrintServer</c>) often does not resolve correctly and doesn't identify |
| 871 | identify the print server for CUPS/Samba interaction. If an error |
828 | the print server for CUPS/Samba interaction. If an error like: <b>Warning: |
| 872 | like: <b>Warning: No PPD file for printer "CUPS_PRINTER_NAME" - |
829 | No PPD file for printer "CUPS_PRINTER_NAME" - skipping!</b> occurs, the |
| 873 | skipping!</b> occurs, the first thing you should do is substitute |
830 | first thing you should do is substitute <c>PrintServer</c> with |
| 874 | <c>PrintServer</c> with <c>localhost</c> and try it again. |
831 | <c>localhost</c> and try it again. |
| 875 | </li> |
832 | </li> |
| 876 | <li> |
833 | <li> |
| 877 | The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message |
834 | The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message |
| 878 | is quite common, but can be triggered by many problems. It's unfortunately |
835 | is quite common, but can be triggered by many problems. It's unfortunately |
| 879 | not very helpful. One thing to try is to temporarily set <c>security = |
836 | not very helpful. One thing to try is to temporarily set <c>security = |
| 880 | user</c> in your <path>smb.conf</path>. After/if the installation completes |
837 | user</c> in your <path>smb.conf</path>. After/if the installation completes |
| 881 | successfully, you should set it back to share, or whatever it was set to |
838 | successfully, you should set it back to share, or whatever it was set to |
| 882 | before. |
839 | before. |
| 883 | </li> |
840 | </li> |
| 884 | </ul> |
841 | </ul> |
| 885 | |
842 | |
| 886 | <p> |
843 | <p> |
| 887 | This should install the correct driver directory structure under |
844 | This should install the correct driver directory structure under |
| 888 | <path>/etc/samba/printer</path>. That would be |
845 | <path>/etc/samba/printer</path>. That would be |
| 889 | <path>/etc/samba/printer/W32X86/2/</path>. The files contained should |
846 | <path>/etc/samba/printer/W32X86/2/</path>. The files contained should be the 3 |
| 890 | be the 3 driver files and the PPD file, renamed to YourPrinterName.ppd |
847 | driver files and the PPD file, renamed to <path>YourPrinterName.ppd</path> (the |
| 891 | (the name which you gave the printer when installing it (see above). |
848 | name which you gave the printer when installing it (see above). |
| 892 | </p> |
|
|
| 893 | |
|
|
| 894 | <p> |
849 | </p> |
|
|
850 | |
|
|
851 | <p> |
| 895 | Pending no errors or other complications, your drivers are now |
852 | Pending no errors or other complications, your drivers are now installed. |
| 896 | installed. |
|
|
| 897 | </p> |
853 | </p> |
| 898 | |
854 | |
| 899 | </body> |
855 | </body> |
| 900 | </section> |
856 | </section> |
| 901 | <section> |
857 | <section> |
| … | |
… | |
| 919 | <title>Testing our Samba configuration</title> |
875 | <title>Testing our Samba configuration</title> |
| 920 | <body> |
876 | <body> |
| 921 | |
877 | |
| 922 | <p> |
878 | <p> |
| 923 | We will want to test our configuration file to ensure that it is formatted |
879 | We will want to test our configuration file to ensure that it is formatted |
| 924 | properly and all of our options have at least the correct syntax. To do |
880 | properly and all of our options have at least the correct syntax. To do this we |
| 925 | this we run <c>testparm</c>. |
881 | run <c>testparm</c>. |
| 926 | </p> |
882 | </p> |
| 927 | |
883 | |
| 928 | <pre caption="Running the testparm"> |
884 | <pre caption="Running the testparm"> |
| 929 | <comment>(By default, testparm checks /etc/samba/smb.conf)</comment> |
885 | <comment>(By default, testparm checks /etc/samba/smb.conf)</comment> |
| 930 | # <i>/usr/bin/testparm</i> |
886 | # <i>/usr/bin/testparm</i> |
| … | |
… | |
| 960 | <section> |
916 | <section> |
| 961 | <title>Checking our services</title> |
917 | <title>Checking our services</title> |
| 962 | <body> |
918 | <body> |
| 963 | |
919 | |
| 964 | <p> |
920 | <p> |
| 965 | It would probably be prudent to check our logs at this time also. |
921 | It would probably be prudent to check our logs at this time also. We will also |
| 966 | We will also want to take a peak at our Samba shares using |
922 | want to take a peak at our Samba shares using <c>smbclient</c>. |
| 967 | <c>smbclient</c>. |
|
|
| 968 | </p> |
923 | </p> |
| 969 | |
924 | |
| 970 | <pre caption="Checking the shares with smbclient"> |
925 | <pre caption="Checking the shares with smbclient"> |
| 971 | # <i>smbclient -L localhost</i> |
926 | # <i>smbclient -L localhost</i> |
| 972 | Password: |
927 | Password: |
| … | |
… | |
| 982 | <section> |
937 | <section> |
| 983 | <title>Printer configuration of *nix based clients</title> |
938 | <title>Printer configuration of *nix based clients</title> |
| 984 | <body> |
939 | <body> |
| 985 | |
940 | |
| 986 | <p> |
941 | <p> |
| 987 | Despite the variation or distribution, the only thing needed is CUPS. Do the |
942 | Despite the variation or distribution, the only thing needed is CUPS. Do the |
| 988 | equivalent on any other UNIX/Linux/BSD client. |
943 | equivalent on any other UNIX/Linux/BSD client. |
| 989 | </p> |
944 | </p> |
| 990 | |
945 | |
| 991 | <pre caption="Configuring a Gentoo system"> |
946 | <pre caption="Configuring a Gentoo system"> |
| 992 | # <i>emerge cups</i> |
947 | # <i>emerge cups</i> |
| … | |
… | |
| 1023 | </pre> |
978 | </pre> |
| 1024 | |
979 | |
| 1025 | <p> |
980 | <p> |
| 1026 | Just point your web browser to <c>http://printserver:631</c> on the client if |
981 | Just point your web browser to <c>http://printserver:631</c> on the client if |
| 1027 | you want to manage your printers and their jobs with a nice web interface. |
982 | you want to manage your printers and their jobs with a nice web interface. |
| 1028 | Replace <c>printserver</c> with the name of the <e>machine</e> that acts as |
983 | Replace <c>printserver</c> with the name of the <e>machine</e> that acts as your |
| 1029 | your print server, not the name you gave to the cups print server if you used |
984 | print server, not the name you gave to the cups print server if you used |
| 1030 | different names. |
985 | different names. |
| 1031 | </p> |
986 | </p> |
| 1032 | |
987 | |
| 1033 | </body> |
988 | </body> |
| 1034 | </section> |
989 | </section> |
| 1035 | <section> |
990 | <section> |
| 1036 | <title>Mounting a Windows or Samba share in GNU/Linux</title> |
991 | <title>Mounting a Windows or Samba share in GNU/Linux</title> |
| 1037 | <body> |
992 | <body> |
| 1038 | |
993 | |
|
|
994 | <note> |
|
|
995 | Don't forget to first <c>emerge samba</c> on the client(s) that will be |
|
|
996 | accessing the shares. |
|
|
997 | </note> |
|
|
998 | |
| 1039 | <p> |
999 | <p> |
| 1040 | Now is time to configure our kernel to support smbfs. Since I'm assumming we've |
1000 | Now is time to configure our kernel to support cifs. Since I'm assuming |
| 1041 | all compiled at least one kernel, we'll need to make sure we have all the right |
1001 | we've all compiled at least one kernel, we'll need to make sure we have all the |
| 1042 | options selected in our kernel. For simplicity sake, make it a module for ease |
1002 | right options selected in our kernel. For simplicity's sake, make it a module |
| 1043 | of use. It is the author's opinion that kernel modules are a good thing and |
1003 | for ease of use. It is the author's opinion that kernel modules are a good thing |
| 1044 | should be used whenever possible. |
1004 | and should be used whenever possible. |
| 1045 | </p> |
|
|
| 1046 | |
|
|
| 1047 | <pre caption="Relevant kernel options" > |
|
|
| 1048 | CONFIG_SMB_FS=m |
|
|
| 1049 | CONFIG_SMB_UNIX=y |
|
|
| 1050 | </pre> |
|
|
| 1051 | |
|
|
| 1052 | <p> |
1005 | </p> |
|
|
1006 | |
|
|
1007 | <pre caption="Kernel support" > |
|
|
1008 | CONFIG_CIFS=m |
|
|
1009 | </pre> |
|
|
1010 | |
|
|
1011 | <p> |
| 1053 | Then make the module/install it; insert them with: |
1012 | Then make the module/install it; insert it with: |
| 1054 | </p> |
1013 | </p> |
| 1055 | |
1014 | |
| 1056 | <pre caption="Loading the kernel module"> |
1015 | <pre caption="Loading the kernel module"> |
| 1057 | # <i>modprobe smbfs</i> |
1016 | # <i>modprobe cifs</i> |
| 1058 | </pre> |
1017 | </pre> |
| 1059 | |
1018 | |
| 1060 | <p> |
1019 | <p> |
| 1061 | Once the modules is loaded, mounting a Windows or Samba share is |
1020 | Once the module is loaded, mounting a Windows or Samba share is possible. Use |
| 1062 | possible. Use <c>mount</c> to accomplish this, as detailed below: |
1021 | <c>mount</c> to accomplish this, as detailed below: |
| 1063 | </p> |
1022 | </p> |
| 1064 | |
1023 | |
| 1065 | <pre caption="Mounting a Windows/Samba share"> |
1024 | <pre caption="Mounting a Windows/Samba share"> |
| 1066 | <comment>(The syntax for mounting a Windows/Samba share is: |
1025 | <comment>(The syntax for mounting a Windows/Samba share is: |
| 1067 | mount -t smbfs [-o username=xxx,password=xxx] //server/share /mnt/point |
1026 | mount -t cifs [-o username=xxx,password=xxx] //server/share /mnt/point |
| 1068 | If we are not using passwords or a password is not needed)</comment> |
1027 | If we are not using passwords or a password is not needed)</comment> |
| 1069 | |
1028 | |
| 1070 | # <i>mount -t smbfs //PrintServer/public /mnt/public</i> |
1029 | # <i>mount -t cifs //PrintServer/public /mnt/public</i> |
| 1071 | |
1030 | |
| 1072 | <comment>(If a password is needed)</comment> |
1031 | <comment>(If a password is needed)</comment> |
| 1073 | # <i>mount -t smbfs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i> |
1032 | # <i>mount -t cifs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i> |
| 1074 | </pre> |
1033 | </pre> |
| 1075 | |
1034 | |
| 1076 | <p> |
1035 | <p> |
| 1077 | After you mount the share, you would access it as if it were a local |
1036 | After you mount the share, you would access it as if it were a local drive. |
| 1078 | drive. |
|
|
| 1079 | </p> |
1037 | </p> |
| 1080 | |
1038 | |
| 1081 | </body> |
1039 | </body> |
| 1082 | </section> |
1040 | </section> |
| 1083 | <section> |
1041 | <section> |
| 1084 | <title>Printer Configuration for Windows NT/2000/XP clients</title> |
1042 | <title>Printer Configuration for Windows NT/2000/XP clients</title> |
| 1085 | <body> |
1043 | <body> |
| 1086 | |
1044 | |
| 1087 | <p> |
1045 | <p> |
| 1088 | That's just a bit of point-and-click. Browse to |
1046 | That's just a bit of point-and-click. Browse to <path>\\PrintServer</path> and |
| 1089 | <path>\\PrintServer</path> and right click on the printer |
1047 | right click on the printer (HPDeskJet930C) and click connect. This will download |
| 1090 | (HPDeskJet930C) and click connect. This will download the drivers to |
|
|
| 1091 | the Windows client and now every application (such as Word or Acrobat) |
1048 | the drivers to the Windows client and now every application (such as Word or |
| 1092 | will offer HPDeskJet930C as an available printer to print to. :-) |
1049 | Acrobat) will offer HPDeskJet930C as an available printer to print to. :-) |
| 1093 | </p> |
1050 | </p> |
| 1094 | |
1051 | |
| 1095 | </body> |
1052 | </body> |
| 1096 | </section> |
1053 | </section> |
| 1097 | </chapter> |
1054 | </chapter> |
| … | |
… | |
| 1101 | <section> |
1058 | <section> |
| 1102 | <title>A Fond Farewell</title> |
1059 | <title>A Fond Farewell</title> |
| 1103 | <body> |
1060 | <body> |
| 1104 | |
1061 | |
| 1105 | <p> |
1062 | <p> |
| 1106 | Well that should be it. You should now have a successful printing enviroment |
1063 | That should be it. You should now have a successful printing enviroment that is |
| 1107 | that is friendly to both Windows and *nix as well as a fully virus-free working |
1064 | friendly to both Windows and *nix as well as a fully virus-free working share! |
| 1108 | share! |
|
|
| 1109 | </p> |
1065 | </p> |
| 1110 | |
1066 | |
| 1111 | </body> |
1067 | </body> |
| 1112 | </section> |
1068 | </section> |
| 1113 | </chapter> |
1069 | </chapter> |
| … | |
… | |
| 1131 | on Samba/CUPS configuration</uri> |
1087 | on Samba/CUPS configuration</uri> |
| 1132 | </li> |
1088 | </li> |
| 1133 | <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li> |
1089 | <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li> |
| 1134 | <li> |
1090 | <li> |
| 1135 | <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt |
1091 | <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt |
| 1136 | Pfeifle's Samba Print HOWTO</uri> ( |
1092 | Pfeifle's Samba Print HOWTO</uri> ( This HOWTO really covers <e>ANYTHING</e> |
| 1137 | This HOWTO really covers <e>ANYTHING</e> and <e>EVERYTHING</e> |
|
|
| 1138 | I've written here, plus a LOT more concerning CUPS and Samba, and |
1093 | and <e>EVERYTHING</e> I've written here, plus a LOT more concerning CUPS and |
| 1139 | generally printing support on networks. A really interesting read, |
1094 | Samba, and generally printing support on networks. A really interesting |
| 1140 | with lots and lots of details) |
1095 | read, with lots and lots of details.) |
| 1141 | </li> |
1096 | </li> |
| 1142 | <li><uri link="http://www.freebsddiary.org/cups.php">FreeBSD Diary's CUPS Topic</uri></li> |
1097 | <li><uri link="http://www.freebsddiary.org/cups.php">FreeBSD Diary's CUPS Topic</uri></li> |
| 1143 | </ul> |
1098 | </ul> |
| 1144 | |
1099 | |
| 1145 | </body> |
1100 | </body> |
| … | |
… | |
| 1147 | <section> |
1102 | <section> |
| 1148 | <title>Troubleshooting</title> |
1103 | <title>Troubleshooting</title> |
| 1149 | <body> |
1104 | <body> |
| 1150 | |
1105 | |
| 1151 | <p> |
1106 | <p> |
|
|
1107 | See <uri |
| 1152 | See <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37">this |
1108 | link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37">this |
| 1153 | page</uri> from Kurt Pfeifle's "Printing Support in Samba 3.0" |
1109 | page</uri> from Kurt Pfeifle's "Printing Support in Samba 3.0" manual. Lots of |
| 1154 | manual. Lots of useful tips there! Be sure to look this one up |
1110 | useful tips there! Be sure to look this one up first, before posting questions |
| 1155 | first, before posting questions and problems! Maybe the solution |
1111 | and problems! Maybe the solution you're looking for is right there. |
| 1156 | you're looking for is right there. |
|
|
| 1157 | </p> |
1112 | </p> |
| 1158 | |
1113 | |
| 1159 | </body> |
1114 | </body> |
| 1160 | </section> |
1115 | </section> |
| 1161 | </chapter> |
1116 | </chapter> |
Parent Directory
| 
Revision Log
| 
Patch