/[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.28 Revision 1.43
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 $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4<guide link="/doc/en/quick-samba-howto.xml"> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.43 2012/07/27 02:25:41 nightmorph Exp $ -->
4
5<guide>
5<title>Gentoo Samba3/CUPS/ClamAV HOWTO</title> 6<title>Gentoo Samba3/CUPS HOWTO</title>
7
6<author title="Author"> 8<author title="Author">
7 <mail link="daff at dword dot org">Andreas "daff" Ntaflos</mail> 9 Andreas "daff" Ntaflos <!--daff at dword dot org-->
8</author> 10</author>
9<author title="Author"> 11<author title="Author">
10 <mail link="joshua@sungentoo.homeunix.com">Joshua Preston</mail> 12 <mail link="joshua@sungentoo.homeunix.com">Joshua Preston</mail>
11</author> 13</author>
14<author title="Editor">
15 <mail link="nightmorph@gentoo.org">Joshua Saddler</mail>
16</author>
12 17
13<abstract> 18<abstract>
14Setup, install and configure a Samba Server under Gentoo that shares 19Setup, install and configure a Samba server under Gentoo that shares files and
15files, printers without the need to install drivers and provides 20printers without the need to install drivers.
16automatic virus scanning.
17</abstract> 21</abstract>
18 22
19<!-- The content of this document is licensed under the CC-BY-SA license --> 23<!-- The content of this document is licensed under the CC-BY-SA license -->
20<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 24<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
21<license/> 25<license/>
22 26
23<version>1.17</version> 27<version>3</version>
24<date>2007-06-06</date> 28<date>2012-07-26</date>
25 29
26<chapter> 30<chapter>
27<title>Introduction to this HOWTO</title> 31<title>Introduction to this HOWTO</title>
28<section> 32<section>
29<title>Purpose</title> 33<title>Purpose</title>
30<body> 34<body>
31 35
32<p> 36<p>
33This HOWTO is designed to help you move a network from many different 37This HOWTO is designed to help you move a network from many different clients
34clients speaking different languages, to many different machines that 38speaking different languages, to many different machines that speak a common
35speak a common language. The ultimate goal is to help differing 39language. The ultimate goal is to help differing architectures and technologies,
36architectures and technologies, come together in a productive, 40come together in a productive, happily coexisting environment.
37happily coexisting environment.
38</p>
39
40<p> 41</p>
42
43<p>
41Following the directions outlined in this HOWTO should give you an 44Following the directions outlined in this HOWTO should give you an excellent
42excellent step towards a peaceful cohabitation between Windows, and 45step towards a peaceful cohabitation between Windows, and virtually all known
43virtually all known variations of *nix. 46variations of *nix.
44</p>
45
46<p> 47</p>
48
49<p>
47This HOWTO originally started not as a HOWTO, but as a FAQ. It was 50This HOWTO originally started not as a HOWTO, but as a FAQ. It was intended to
48intended to explore the functionality and power of the Gentoo system, 51explore the functionality and power of the Gentoo system, portage and the
49portage and the flexibility of USE flags. Like so many other projects, 52flexibility of USE flags. Like so many other projects, it was quickly discovered
50it was quickly discovered what was missing in the Gentoo realm: there 53what was missing in the Gentoo realm: there weren't any Samba HOWTOs catered
51weren't any Samba HOWTO's catered for Gentoo users. These users are 54for Gentoo users. These users are more demanding than most; they require
52more demanding than most; they require performance, flexibility and 55performance, flexibility and customization. This does not however imply that
53customization. This does not however imply that this HOWTO was not
54intended for other distributions; rather that it was designed to work 56this HOWTO was not intended for other distributions; rather that it was designed
55with a highly customized version of Samba. 57to work with a highly customized version of Samba.
56</p>
57
58<p> 58</p>
59
60<p>
59This HOWTO will describe how to share files and printers between Windows 61This HOWTO will describe how to share files and printers between Windows PCs and
60PCs and *nix PCs. It will also demonstrate the use of the VFS (Virtual
61File System) feature of Samba to incorporate automatic virus protection.
62As a finale, it will show you how to mount and manipulate shares. 62*nix PCs. It will also show you how to mount and manipulate shares.
63</p>
64
65<p> 63</p>
64
65<p>
66There are a few topics that will be mentioned, but are out of the 66There are a few topics that will be mentioned, but are out of the scope of this
67scope of this HOWTO. These will be noted as they are presented. 67HOWTO. These will be noted as they are presented.
68</p>
69
70<p> 68</p>
69
70<p>
71This HOWTO is based on a compilation and merge of an excellent HOWTO 71This HOWTO is based on a compilation and merge of an excellent HOWTO provided
72provided in the <uri link="http://forums.gentoo.org">Gentoo forums</uri> 72in the <uri link="http://forums.gentoo.org">Gentoo forums</uri> by Andreas
73by Andreas "daff" Ntaflos and the collected knowledge of Joshua Preston. 73"daff" Ntaflos and the collected knowledge of Joshua Preston. The link to this
74The link to this discussion is provided below for your reference: 74discussion is provided below for your reference:
75</p> 75</p>
76 76
77<ul> 77<ul>
78 <li> 78 <li>
79 <uri link="http://forums.gentoo.org/viewtopic.php?t=110931">HOWTO 79 <uri link="http://forums.gentoo.org/viewtopic.php?t=110931">HOWTO
80 CUPS+Samba: printing from Windows &amp; Linux</uri> 80 CUPS+Samba: printing from Windows &amp; Linux</uri>
81 </li> 81 </li>
82</ul> 82</ul>
83 83
84</body> 84</body>
87<title>Before you use this guide</title> 87<title>Before you use this guide</title>
88<body> 88<body>
89 89
90<p> 90<p>
91There are a several other guides for setting up CUPS and/or Samba, please read 91There are a several other guides for setting up CUPS and/or Samba, please read
92them as well, as they may tell you things left out of this HOWTO (intentional 92them as well, as they may tell you things left out of this HOWTO (intentional or
93or otherwise). One such document is the very useful and well written <uri 93otherwise). One such document is the very useful and well written <uri
94link="/doc/en/printing-howto.xml">Gentoo Printing Guide</uri>, as configuration 94link="/doc/en/printing-howto.xml">Gentoo Printing Guide</uri>, as configuration
95issues and specific printer setup is not discussed here. 95issues and specific printer setup is not discussed here.
96</p> 96</p>
97 97
98</body> 98</body>
100<section> 100<section>
101<title>Brief Overview</title> 101<title>Brief Overview</title>
102<body> 102<body>
103 103
104<p> 104<p>
105After presenting the various USE flags, the following list will outline 105After presenting the various USE flags, the following list will outline all of
106all of the topics covered as they are presented: 106the topics covered as they are presented:
107</p> 107</p>
108 108
109<ul> 109<ul>
110 <li>On the Samba server: 110 <li>On the Samba server:
111 <ul> 111 <ul>
112 <li>Install and configure ClamAV</li>
113 <li>Install and configure Samba</li> 112 <li>Install and configure Samba</li>
114 <li>Install and configure CUPS</li> 113 <li>Install and configure CUPS</li>
115 <li>Adding the printer to CUPS</li> 114 <li>Adding the printer to CUPS</li>
116 <li>Adding the PS drivers for the Windows clients</li> 115 <li>Adding the PS drivers for the Windows clients</li>
117 </ul> 116 </ul>
141We will need the following: 140We will need the following:
142</p> 141</p>
143 142
144<ul> 143<ul>
145 <li>net-fs/samba</li> 144 <li>net-fs/samba</li>
146 <li>app-antivirus/clamav</li> 145 <li>net-print/cups (built with the <c>ppds</c> USE flag)</li>
147 <li>net-print/cups</li>
148 <li>net-print/foomatic</li>
149 <li>net-print/hplip (if you have an HP printer)</li> 146 <li>net-print/hplip (if you have an HP printer)</li>
150 <li>A kernel of sorts (2.6)</li> 147 <li>A kernel of sorts (2.6)</li>
151 <li>A printer (PS or non-PS, maybe not TOO new or fancy)</li> 148 <li>A printer (PS or non-PS)</li>
152 <li> 149 <li>
153 A working network (home/office/etc) consisting of more than one machine) 150 A working network (home/office/etc) consisting of more than one machine)
154 </li> 151 </li>
155</ul> 152</ul>
156 153
157<p> 154<p>
158The main package we use here is net-fs/samba, however, you will need 155The main package we use here is <c>net-fs/samba</c>, however, you will need a
159a kernel with smbfs support enabled in order to mount a samba or windows 156kernel with CIFS support enabled in order to mount a Samba or Windows share from
160share from another computer. CUPS will be emerged if it is not already. 157another computer. CUPS will be emerged if it is not already.
161app-antivirus/clamav will be used also, but others should be easily adapted
162to work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning
163technologies, such as Sophos, FProt, Fsav, Trend, Icap, Nai, ...
164</p> 158</p>
165 159
166</body> 160</body>
167</section> 161</section>
168</chapter> 162</chapter>
177Before emerging anything, take a look at some of the various USE flags available 171Before emerging anything, take a look at some of the various USE flags available
178to Samba. 172to Samba.
179</p> 173</p>
180 174
181<pre caption="Samba uses the following USE Variables:"> 175<pre caption="Samba uses the following USE Variables:">
182kerberos acl cups ldap pam readline python oav 176kerberos acl cups ldap pam readline python winbind
183</pre> 177</pre>
184 178
185<p> 179<p>
186Depending on the network topology and the specific requirements of 180Depending on the network topology and the specific requirements of the server,
187the server, the USE flags outlined below will define what to include or 181the USE flags outlined below will define what to include or exclude from the
188exclude from the emerging of Samba. 182emerging of Samba.
189</p> 183</p>
190 184
191<table> 185<table>
192<tr> 186<tr>
193 <th><b>USE flag</b></th> 187 <th><b>USE flag</b></th>
194 <th>Description</th> 188 <th>Description</th>
195</tr> 189</tr>
196<tr> 190<tr>
197 <th><b>kerberos</b></th> 191 <th><b>kerberos</b></th>
198 <ti> 192 <ti>
199 Include support for Kerberos. The server will need this if it is 193 Include support for Kerberos. The server will need this if it is intended
200 intended to join an existing domain or Active Directory. See the note 194 to join an existing domain or Active Directory. See the note below for more
201 below for more information. 195 information.
202 </ti> 196 </ti>
203</tr> 197</tr>
204<tr> 198<tr>
205 <th><b>acl</b></th> 199 <th><b>acl</b></th>
206 <ti> 200 <ti>
207 Enables Access Control Lists. The ACL support in Samba uses a patched 201 Enables Access Control Lists. The ACL support in Samba uses a patched
208 ext2/ext3, or SGI's XFS in order to function properly as it extends more 202 ext2/ext3, or SGI's XFS in order to function properly as it extends more
209 detailed access to files or directories; much more so than typical *nix 203 detailed access to files or directories; much more so than typical *nix
210 GID/UID schemas. 204 GID/UID schemas.
211 </ti> 205 </ti>
212</tr> 206</tr>
213<tr> 207<tr>
214 <th><b>cups</b></th> 208 <th><b>cups</b></th>
215 <ti> 209 <ti>
216 This enables support for the Common Unix Printing System. This 210 This enables support for the Common Unix Printing System. This provides an
217 provides an interface allowing local CUPS printers to be shared to 211 interface allowing local CUPS printers to be shared to other systems in the
218 other systems in the network. 212 network.
219 </ti> 213 </ti>
220</tr> 214</tr>
221<tr> 215<tr>
222 <th><b>ldap</b></th> 216 <th><b>ldap</b></th>
223 <ti> 217 <ti>
224 Enables the Lightweight Directory Access Protocol (LDAP). If Samba is 218 Enables the Lightweight Directory Access Protocol (LDAP). If Samba is
225 expected to use Active Directory, this option must be used. This would 219 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 220 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 221 Domain/Active Directory Server. The kerberos USE flag is needed for proper
228 proper functioning of this option. 222 functioning of this option.
229 </ti> 223 </ti>
230</tr> 224</tr>
231<tr> 225<tr>
232 <th><b>pam</b></th> 226 <th><b>pam</b></th>
233 <ti> 227 <ti>
234 Include support for pluggable authentication modules (PAM). This 228 Include support for pluggable authentication modules (PAM). This provides
235 provides the ability to authenticate users on the Samba Server, which is 229 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 230 users have to login to your server. The kerberos USE flag is recommended
237 is recommended along with this option. 231 along with this option.
238 </ti> 232 </ti>
239</tr> 233</tr>
240<tr> 234<tr>
241 <th><b>readline</b></th> 235 <th><b>readline</b></th>
242 <ti> 236 <ti>
243 Link Samba against libreadline. This is highly recommended and should 237 Link Samba against libreadline. This is highly recommended and should
244 probably not be disabled 238 probably not be disabled.
245 </ti> 239 </ti>
246</tr> 240</tr>
247<tr> 241<tr>
248 <th><b>python</b></th> 242 <th><b>python</b></th>
249 <ti> 243 <ti>
250 Python bindings API. Provides an API that will allow Python to 244 Python bindings API. Provides an API that will allow Python to interface
251 interface with Samba. 245 with Samba.
252 </ti> 246 </ti>
253</tr> 247</tr>
254<tr> 248<tr>
255 <th><b>oav</b></th> 249 <th><b>winbind</b></th>
256 <ti> 250 <ti>
257 Provides on-access scanning of Samba shares with FRISK F-Prot 251 Winbind allows for a unified logon within a Samba environment. It uses a
258 Daemon, Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep 252 Unix implementation of Windows RPC calls, PAM and the name service switch
259 (SAVI), Symantec CarrierScan, and Trend Micro (VSAPI). 253 (supported by the c library) to enable Windows NT domain users to appear and
254 work as Unix users on a Unix system.
260 </ti> 255 </ti>
261</tr> 256</tr>
262</table> 257</table>
263 258
264<p> 259<p>
266Samba functions include: 261Samba functions include:
267</p> 262</p>
268 263
269<ul> 264<ul>
270 <li> 265 <li>
271 ACLs on ext2/3 are implemented through extended attributes (EAs). EA and 266 ACLs on ext2/3 are implemented through extended attributes (EAs). EA and
272 ACL kernel options for ext2 and/or ext3 will need to be enabled 267 ACL kernel options for ext2 and/or ext3 will need to be enabled (depending
273 (depending on which file system is being used - both can be enabled). 268 on which file system is being used - both can be enabled).
274 </li> 269 </li>
275 <li> 270 <li>
276 While Active Directory, ACL, and PDC functions are out of the intended 271 While Active Directory, ACL, and PDC functions are out of the intended
277 scope of this HOWTO, you may find these links as helpful to your cause: 272 scope of this HOWTO, you may find these links as helpful to your cause:
278 <ul> 273 <ul>
291<section> 286<section>
292<title>Emerging Samba</title> 287<title>Emerging Samba</title>
293<body> 288<body>
294 289
295<p> 290<p>
296First of all: be sure that all your hostnames resolve correctly. 291First of all: be sure that all your hostnames resolve correctly. Either have a
297Either have a working domain name system running on your network 292working domain name system running on your network or appropriate entries in
298or appropriate entries in your <path>/etc/hosts</path> file. 293your <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 294don't point to the correct machines.
300machines.
301</p>
302
303<p> 295</p>
296
297<p>
304Hopefully now you can make an assessment of what you'll actually need in 298Hopefully now you can make an assessment of what you'll actually need in order
305order to use Samba with your particular setup. The setup used for this 299to use Samba with your particular setup. The setup used for this HOWTO is:
306HOWTO is:
307</p> 300</p>
308 301
309<ul> 302<ul>
310 <li>oav</li>
311 <li>cups</li> 303 <li>cups</li>
312 <li>readline</li> 304 <li>readline</li>
313 <li>pam</li> 305 <li>pam</li>
314</ul> 306</ul>
315 307
316<p> 308<p>
317To optimize performance, size and the time of the build, the 309To optimize performance, size and the time of the build, the USE flags are
318USE flags are specifically included or excluded. 310specifically included or excluded.
311</p>
312
313<p>
314First, add <c>ppds</c> to your USE flags to make sure that when CUPS is built,
315it has proper foomatic support:
316</p>
317
318<pre caption="Adding ppds">
319# <i>echo "net-print/cups ppds" &gt;&gt; /etc/portage/package.use</i>
320</pre>
321
322<p>
323Now, emerge Samba:
319</p> 324</p>
320 325
321<pre caption="Emerge Samba"> 326<pre caption="Emerge Samba">
322# <i>echo "net-fs/samba oav readline cups pam" &gt;&gt; /etc/portage/package.use</i> 327# <i>echo "net-fs/samba readline cups pam" &gt;&gt; /etc/portage/package.use</i>
323# <i>emerge net-fs/samba</i> 328# <i>emerge net-fs/samba</i>
324</pre> 329</pre>
325 330
326<note>
327The following archs will need to add <e>~</e> to their <e>KEYWORDS</e>: x86,
328ppc, sparc, hppa, ia64 and alpha
329</note>
330
331<p>
332This will emerge Samba and CUPS (if CUPS is not already emerged).
333</p> 331<p>
334 332This will emerge Samba and CUPS.
335</body>
336</section>
337<section>
338<title>Emerging ClamAV</title>
339<body>
340
341<p> 333</p>
342Because the <e>oav</e> USE flag only provides an interface to allow on access
343virus scanning, the actual virus scanner must be emerged. The scanner
344used in this HOWTO is ClamAV.
345</p>
346
347<pre caption="Emerge Clamav">
348# <i>emerge app-antivirus/clamav</i>
349</pre>
350
351</body>
352</section>
353<section>
354<title>Emerging foomatic</title>
355<body>
356
357<pre caption="Emerge foomatic">
358# <i>emerge net-print/foomatic</i>
359</pre>
360 334
361</body> 335</body>
362</section> 336</section>
363<section> 337<section>
364<title>Emerging net-print/hplip</title> 338<title>Emerging net-print/hplip</title>
381<section> 355<section>
382<title>Configuring Samba</title> 356<title>Configuring Samba</title>
383<body> 357<body>
384 358
385<p> 359<p>
386The main Samba configuration file is <path>/etc/samba/smb.conf</path>. 360The main Samba configuration file is <path>/etc/samba/smb.conf</path>. It is
387It is divided in sections indicated by [sectionname]. Comments are either 361divided in sections indicated by [sectionname]. Comments are either
388# or ;. A sample <path>smb.conf</path> is included below with comments and 362# or ;. A sample <path>smb.conf</path> is included below with comments and
389suggestions for modifications. If more details are required, see the 363suggestions for modifications. If more details are required, see the man page
390man page for <path>smb.conf</path>, the installed 364for <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 365Samba Web site or any of the numerous Samba books available.
392numerous Samba books available.
393</p> 366</p>
394 367
395<pre caption="A Sample /etc/samba/smb.conf"> 368<pre caption="A Sample /etc/samba/smb.conf">
396[global] 369[global]
397<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment> 370<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment>
421hosts deny = 0.0.0.0/0 394hosts deny = 0.0.0.0/0
422<comment># Other options for this are USER, DOMAIN, ADS, and SERVER 395<comment># Other options for this are USER, DOMAIN, ADS, and SERVER
423# The default is user</comment> 396# The default is user</comment>
424security = share 397security = share
425<comment># No passwords, so we're going to use a guest account!</comment> 398<comment># No passwords, so we're going to use a guest account!</comment>
426guest account = samba
427guest ok = yes 399guest ok = yes
428<comment># We now will implement the on access virus scanner.
429# NOTE: By putting this in our [Global] section, we enable
430# scanning of ALL shares, you could optionally move
431# these to a specific share and only scan it.</comment>
432
433<comment># For Samba 3.x. This enables ClamAV on access scanning.</comment>
434vfs object = vscan-clamav
435vscan-clamav: config-file = /etc/samba/vscan-clamav.conf
436 400
437<comment># Now we setup our print drivers information!</comment> 401<comment># Now we setup our print drivers information!</comment>
438[print$] 402[print$]
439comment = Printer Drivers 403comment = Printer Drivers
440path = /etc/samba/printer <comment># this path holds the driver structure</comment> 404path = /etc/samba/printer <comment># this path holds the driver structure</comment>
455guest ok = yes 419guest ok = yes
456<comment># Modify this to "username,root" if you don't want root to 420<comment># Modify this to "username,root" if you don't want root to
457# be the only printer admin)</comment> 421# be the only printer admin)</comment>
458printer admin = <i>root</i> 422printer admin = <i>root</i>
459 423
460<comment># Now we setup our printers share. This should be 424<comment># Now we setup our printers share. This should be
461# browseable, printable, public.</comment> 425# browseable, printable, public.</comment>
462[printers] 426[printers]
463comment = All Printers 427comment = All Printers
464browseable = no 428browseable = no
465printable = yes 429printable = yes
466writable = no 430writable = no
467public = yes 431public = yes
468guest ok = yes 432guest ok = yes
469path = /var/spool/samba 433path = /var/spool/samba
470<comment># Modify this to "username,root" if you don't want root to 434<comment># Modify this to "username,root" if you don't want root to
471# be the only printer admin)</comment> 435# be the only printer admin)</comment>
472printer admin = <i>root</i> 436printer admin = <i>root</i>
482guest ok = yes 446guest ok = yes
483path = /home/samba/public 447path = /home/samba/public
484</pre> 448</pre>
485 449
486<warn> 450<warn>
487If you like to use Samba's guest account to do anything concerning 451If you like to use Samba's guest account to do anything concerning printing from
488printing from Windows clients: don't set <c>guest only = yes</c> in 452Windows clients: don't set <c>guest only = yes</c> in the <c>[global]</c>
489the <c>[global]</c> section. The guest account seems to cause 453section. The guest account seems to cause problems when running
490problems when running <c>cupsaddsmb</c> sometimes when trying to 454<c>cupsaddsmb</c> sometimes when trying to connect from Windows machines. See
491connect from Windows machines. See below, too, when we talk about 455below, 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
493printer user, like <c>printeruser</c> or <c>printer</c> or 456arise. 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 457or <c>printme</c> or whatever. It doesn't hurt and it will certainly protect you
495protect you from a lot of problems. 458from a lot of problems.
496</warn> 459</warn>
497 460
498<warn>
499Turning on ClamAV on access scanning in the <c>[global]</c> section will slow
500down the performance of your Samba server dramatically.
501</warn>
502
503<p> 461<p>
504Now create the directories required for the minimum configuration of 462Now create the directories required for the minimum configuration of Samba to
505Samba to share the installed printer throughout the network. 463share the installed printer throughout the network.
506</p> 464</p>
507 465
508<pre caption="Create the directories"> 466<pre caption="Create the directories">
509# <i>mkdir /etc/samba/printer</i> 467# <i>mkdir /etc/samba/printer</i>
510# <i>mkdir /var/spool/samba</i> 468# <i>mkdir /var/spool/samba</i>
511# <i>mkdir /home/samba/public</i> 469# <i>mkdir /home/samba/public</i>
512</pre> 470</pre>
513 471
514<p> 472<p>
515At least one Samba user is required in order to install the printer 473At least one Samba user is required in order to install the printer drivers and
516drivers and to allow users to connect to the printer. Users must 474to allow users to connect to the printer. Users must exist in the system's
517exist in the system's <path>/etc/passwd</path> file. 475<path>/etc/passwd</path> file.
518</p> 476</p>
519 477
520<pre caption="Creating the users"> 478<pre caption="Creating the users">
521# <i>smbpasswd -a root</i> 479# <i>smbpasswd -a root</i>
522 480
523<comment>(If another user is to be a printer admin)</comment> 481<comment>(If another user is to be a printer admin)</comment>
524# <i>smbpasswd -a username</i> 482# <i>smbpasswd -a username</i>
525</pre> 483</pre>
526 484
527<p> 485<p>
528The Samba passwords need not be the same as the system passwords 486The Samba passwords need not be the same as the system passwords
529in <path>/etc/passwd</path>. 487in <path>/etc/passwd</path>.
530</p> 488</p>
531 489
532<p> 490<p>
533You will also need to update <path>/etc/nsswitch.conf</path> so that Windows 491You will also need to update <path>/etc/nsswitch.conf</path> so that Windows
541</pre> 499</pre>
542 500
543</body> 501</body>
544</section> 502</section>
545<section> 503<section>
546<title>Configuring ClamAV</title>
547<body>
548
549<p>
550The 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
552to the defaults, the infected file action may need to be changed.
553</p>
554
555<pre caption="/etc/samba/vscan-clamav.conf">
556[samba-vscan]
557<comment>; run-time configuration for vscan-samba using
558; clamd
559; all options are set to default values</comment>
560
561<comment>; do not scan files larger than X bytes. If set to 0 (default),
562; this feature is disable (i.e. all files are scanned)</comment>
563max file size = 0
564
565<comment>; log all file access (yes/no). If set to yes, every access will
566; be logged. If set to no (default), only access to infected files
567; will be logged</comment>
568verbose file logging = no
569
570<comment>; if set to yes (default), a file will be scanned while opening</comment>
571scan on open = yes
572<comment>; if set to yes, a file will be scanned while closing (default is yes)</comment>
573scan on close = yes
574
575<comment>; if communication to clamd fails, should access to file denied?
576; (default: yes)</comment>
577deny access on error = yes
578
579<comment>; if daemon fails with a minor error (corruption, etc.),
580; should access to file denied?
581; (default: yes)</comment>
582deny access on minor error = yes
583
584<comment>; send a warning message via Windows Messenger service
585; when virus is found?
586; (default: yes)</comment>
587send warning message = yes
588
589<comment>; what to do with an infected file
590; quarantine: try to move to quantine directory; delete it if moving fails
591; delete: delete infected file
592; nothing: do nothing</comment>
593infected file action = <comment>delete</comment>
594
595<comment>; where to put infected files - you really want to change this!
596; it has to be on the same physical device as the share!</comment>
597quarantine directory = /tmp
598<comment>; prefix for files in quarantine</comment>
599quarantine prefix = vir-
600
601<comment>; as Windows tries to open a file multiple time in a (very) short time
602; of period, samba-vscan use a last recently used file mechanism to avoid
603; multiple scans of a file. This setting specified the maximum number of
604; elements of the last recently used file list. (default: 100)</comment>
605max lru files entries = 100
606
607<comment>; an entry is invalidated after lru file entry lifetime (in seconds).
608; (Default: 5)</comment>
609lru file entry lifetime = 5
610
611<comment>; socket name of clamd (default: /var/run/clamd)</comment>
612clamd socket name = /tmp/clamd
613
614<comment>; port number the ScannerDaemon listens on</comment>
615oav port = 8127
616</pre>
617
618<p>
619It is generally a good idea to start the virus scanner immediately. Add
620it to the <e>default</e> runlevel and then start the <c>clamd</c> service
621immediately. The service has two processes: freshclam keeps the virus definition
622database up to date while clamd is the actual anti-virus daemon. First you may
623want to set the paths of the logfiles so that it fits your needs.
624</p>
625
626<pre caption="Checking the location of the logfiles">
627# <i>vim /etc/clamd.conf</i>
628<comment>(Check the line "LogFile /var/log/clamd.log")</comment>
629# <i>vim /etc/freshclam.conf</i>
630<comment>(Check the line "UpdateLogFile /var/log/freshclam.log")</comment>
631# <i>vim /etc/conf.d/clamd</i>
632<comment>(Set "START_CLAMD=yes" and "START_FRESHCLAM=yes")</comment>
633</pre>
634
635<p>
636Now fire up the virus scanner.
637</p>
638
639<pre caption="Add clamd to bootup and start it">
640# <i>rc-update add clamd default</i>
641# <i>/etc/init.d/clamd start</i>
642</pre>
643
644</body>
645</section>
646<section>
647<title>Configuring CUPS</title> 504<title>Configuring CUPS</title>
648<body> 505<body>
649 506
650<p> 507<p>
651This is a little more complicated. CUPS' main config file is 508This 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 509<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 510<path>httpd.conf</path> file, so many you may find it familiar. Outlined in the
654in the example are the directives that need to be changed: 511example are the directives that need to be changed:
655</p> 512</p>
656 513
657<pre caption="/etc/cups/cupsd.conf"> 514<pre caption="/etc/cups/cupsd.conf">
658ServerName <i>PrintServer</i> <comment># your printserver name</comment> 515ServerName <i>PrintServer</i> <comment># your printserver name</comment>
659ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, e.g. you</comment> 516ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, e.g. you</comment>
660 517
661AccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment> 518AccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment>
662ErrorLog /var/log/cups/error_log <comment># doesn't really need changing either</comment> 519ErrorLog /var/log/cups/error_log <comment># doesn't really need changing either</comment>
663 520
664LogLevel debug <comment># only while isntalling and testing, should later be 521LogLevel debug <comment># only while installing and testing, should later be
665 # changed to 'info'</comment> 522 # changed to 'info'</comment>
666 523
667MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back, 524MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back,
668 # there seemed to be a bug in CUPS' controlling of the web interface, 525 # there seemed to be a bug in CUPS' controlling of the web interface,
669 # making CUPS think a denial of service attack was in progress when 526 # making CUPS think a denial of service attack was in progress when
670 # I tried to configure a printer with the web interface. weird.</comment> 527 # I tried to configure a printer with the web interface. weird.</comment>
671 528
672BrowseAddress @IF(<i>eth0</i>) <comment># Change this to your internal net interface</comment> 529BrowseAddress @IF(<i>eth0</i>) <comment># Change this to your internal net interface</comment>
673 530
674&lt;Location /&gt; 531&lt;Location /&gt;
675Order Deny,Allow 532Order Deny,Allow
676Deny From All 533Deny From All
677Allow From <i>192.168.1.*</i> <comment># the addresses of your internel network 534Allow From <i>192.168.1.*</i> <comment># the addresses of your internel network
681 538
682&lt;Location /admin&gt; 539&lt;Location /admin&gt;
683AuthType Basic 540AuthType Basic
684AuthClass System 541AuthClass System
685Allow From <i>192.168.1.*</i> <comment># same as above, allow any host on the 542Allow From <i>192.168.1.*</i> <comment># same as above, allow any host on the
686 # 192.168.1.0 network to connect and do 543 # 192.168.1.0 network to connect and do
687 # administrative tasks after authenticating</comment> 544 # administrative tasks after authenticating</comment>
688Order Deny,Allow 545Order Deny,Allow
689Deny From All 546Deny From All
690&lt;/Location&gt; 547&lt;/Location&gt;
691</pre> 548</pre>
692 549
693<p> 550<p>
694Edit <path>/etc/cups/mime.convs</path> to uncomment some lines. 551Edit <path>/etc/cups/mime.convs</path> to uncomment some lines. The changes to
695The changes to <path>mime.convs</path> and <path>mime.types</path> are 552<path>mime.convs</path> and <path>mime.types</path> are needed to make CUPS
696needed to make CUPS print Microsoft Office document files. 553print Microsoft Office document files.
697</p> 554</p>
698 555
699<pre caption="/etc/cups/mime.convs"> 556<pre caption="/etc/cups/mime.convs">
700<comment>(The following line is found near the end of the file. Uncomment it)</comment> 557<comment>(The following line is found near the end of the file. Uncomment it)</comment>
701application/octet-stream application/vnd.cups-raw 0 558application/octet-stream application/vnd.cups-raw 0
702</pre> 559</pre>
703 560
704<p> 561<p>
705Edit <path>/etc/cups/mime.types</path> to uncomment some lines. 562Edit <path>/etc/cups/mime.types</path> to uncomment some lines.
706</p> 563</p>
707 564
708<pre caption="/etc/cups/mime.types"> 565<pre caption="/etc/cups/mime.types">
709<comment>(The following line is found near the end of the file. Uncomment it)</comment> 566<comment>(The following line is found near the end of the file. Uncomment it)</comment>
710application/octet-stream 567application/octet-stream
711</pre> 568</pre>
712 569
713<p> 570<p>
714CUPS needs to be started on boot, and started immediately. 571CUPS needs to be started on boot, and started immediately.
715</p> 572</p>
716 573
717<pre caption="Setting up the CUPS service" > 574<pre caption="Setting up the CUPS service" >
718<comment>(To start CUPS on boot)</comment> 575<comment>(To start CUPS on boot)</comment>
719# <i>rc-update add cupsd default</i> 576# <i>rc-update add cupsd default</i>
730<p> 587<p>
731First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to 588First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to
732find and download the correct PPD file for your printer and CUPS. To do so, 589find and download the correct PPD file for your printer and CUPS. To do so,
733click the link Printer Listings to the left. Select your printers manufacturer 590click the link Printer Listings to the left. Select your printers manufacturer
734and the model in the pulldown menu, e.g. HP and DeskJet 930C. Click "Show". On 591and the model in the pulldown menu, e.g. HP and DeskJet 930C. Click "Show". On
735the page coming up click the "recommended driver" link after reading the 592the page coming up click the "recommended driver" link after reading the various
736various notes and information. Then fetch the PPD file from the next page, 593notes and information. Then fetch the PPD file from the next page, again after
737again after reading the notes and introductions there. You may have to select 594reading the notes and introductions there. You may have to select your printers
738your printers manufacturer and model again. Reading the <uri 595manufacturer and model again. Reading the <uri
739link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri> 596link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri> is
740is also very helpful when working with CUPS. 597also very helpful when working with CUPS.
741</p>
742
743<p> 598</p>
599
600<p>
744Now you have a PPD file for your printer to work with CUPS. Place it in 601Now 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 602<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was named
746named <path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer. 603<path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer.
747This can be done via the CUPS web interface or via command line. The web 604This can be done via the CUPS web interface or via command line. The web
748interface is found at <path>http://PrintServer:631</path> once CUPS is running. 605interface is found at <path>http://PrintServer:631</path> once CUPS is running.
749</p> 606</p>
750 607
751<pre caption="Install the printer via command line"> 608<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> 609# <i>lpadmin -p HPDeskJet930C -E -v usb:/dev/ultp0 -m HP-DeskJet_930C-hpijs.ppd</i>
753# <i>/etc/init.d/cupsd restart</i> 610# <i>/etc/init.d/cupsd restart</i>
754</pre> 611</pre>
755 612
756<p> 613<p>
757Remember to adjust to what you have. Be sure to have the name 614Remember 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 615argument) right (the name you set above during the Samba configuration!) and to
759configuration!) and to put in the correct <c>usb:/dev/usb/blah</c>, 616put 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 617whatever device you are using for your printer.
761printer.
762</p>
763
764<p> 618</p>
619
620<p>
765You should now be able to access the printer from the web interface 621You should now be able to access the printer from the web interface and be able
766and be able to print a test page. 622to print a test page.
767</p> 623</p>
768 624
769</body> 625</body>
770</section> 626</section>
771<section> 627<section>
772<title>Installing the Windows printer drivers</title> 628<title>Installing the Windows printer drivers</title>
773<body> 629<body>
774 630
775<p> 631<p>
776Now that the printer should be working it is time to install the drivers 632Now that the printer should be working it is time to install the drivers for
777for the Windows clients to work. Samba 2.2 introduced this functionality. 633the Windows clients to work. Samba 2.2 introduced this functionality. Browsing
778Browsing to the print server in the Network Neighbourhood, right-clicking 634to the print server in the Network Neighbourhood, right-clicking on the
779on the printershare and selecting "connect" downloads the appropriate 635printershare and selecting "connect" downloads the appropriate drivers
780drivers automagically to the connecting client, avoiding the hassle of 636automagically to the connecting client, avoiding the hassle of manually
781manually installing printer drivers locally. 637installing printer drivers locally.
782</p> 638</p>
783 639
784<p> 640<p>
785There are two sets of printer drivers for this. First, the Adobe PS drivers 641There are two sets of printer drivers for this. First, the Adobe PS drivers
786which can be obtained from <uri 642which can be obtained from <uri
787link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript 643link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript
788printer drivers). Second, there are the CUPS PS drivers, to be obtained <uri 644printer drivers). Second, there are the CUPS PS drivers, to be obtained by
789link="http://dev.gentoo.org/~nightmorph/misc/cups-samba-5.0rc2.tar.gz">here</uri>. 645emerging <c>net-print/cups-windows</c>. There doesn't seem to be a difference
790There doesn't seem to be a difference between the functionality of the two, but 646between the functionality of the two, but the Adobe PS drivers need to be
791the Adobe PS drivers need to be extracted on a Windows System since it's a 647extracted on a Windows System since it's a Windows binary. Also the whole
792Windows binary. Also the whole procedure of finding and copying the correct 648procedure of finding and copying the correct files is a bit more hassle. The
793files is a bit more hassle. The CUPS drivers seem to support some options the 649CUPS drivers support some options the Adobe drivers don't.
794Adobe drivers don't.
795</p>
796<!--
797used to be available at www.cups.org/articles.php?L142+p4, but only 6.0 is
798available. at some point, we should update this for 6.0.
799-->
800
801<p> 650</p>
802This HOWTO uses the CUPS drivers for Windows. The downloaded file is 651
803called <path>cups-samba-5.0rc2.tar.gz</path>. Extract the files
804contained into a directory.
805</p> 652<p>
806 653This 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> 654</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 655
820<warn>
821The script <c>cups-samba.install</c> may not work for all *nixes (i.e. FreeBSD)
822because almost everything which is not part of the base system is
823installed somewhere under the prefix <path>/usr/local/</path>. This
824seems not to be the case for most things you install under GNU/Linux.
825However, if your CUPS installation is somewhere other than
826<path>/usr/share/cups/</path> see the example below.
827</warn>
828
829<p>
830Suppose your CUPS installation resides under
831<path>/usr/local/share/cups/</path>, and you want to install the drivers there.
832Do the following:
833</p>
834
835<pre caption="Manually installing the drivers"> 656<pre caption="Install the drivers">
836# <i>cd /path/you/extracted/the/CUPS-driver/tarball/into</i> 657# <i>emerge -av cups-windows</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>
843</pre> 658</pre>
844 659
845<p> 660<p>
846Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS distribution. 661Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS distribution.
847Its man page is an interesting read. 662Be sure to read its manpage (<c>man cupsaddsmb</c>), as it will tell you which
663Windows drivers you'll need to copy to the proper CUPS directory. Once you've
664copied the drivers, restart CUPS by running <c>/etc/init.d/cupsd restart</c>.
665Next, run <c>cupsaddsmb</c> as shown:
848</p> 666</p>
849 667
850<pre caption="Run cupsaddsmb"> 668<pre caption="Run cupsaddsmb">
851# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -v HPDeskJet930C</i> 669# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -v HPDeskJet930C</i>
852<comment>(Instead of HPDeskJet930C you could also specify "-a", which will 670<comment>(Instead of HPDeskJet930C you could also specify "-a", which will
865</p> 683</p>
866 684
867<ul> 685<ul>
868 <li> 686 <li>
869 The hostname given as a parameter for <c>-h</c> and <c>-H</c> 687 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 688 (<c>PrintServer</c>) often does not resolve correctly and doesn't identify
871 identify the print server for CUPS/Samba interaction. If an error 689 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" - 690 No PPD file for printer "CUPS_PRINTER_NAME" - skipping!</b> occurs, the
873 skipping!</b> occurs, the first thing you should do is substitute 691 first thing you should do is substitute <c>PrintServer</c> with
874 <c>PrintServer</c> with <c>localhost</c> and try it again. 692 <c>localhost</c> and try it again.
875 </li> 693 </li>
876 <li> 694 <li>
877 The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message 695 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 696 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 = 697 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 698 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 699 successfully, you should set it back to share, or whatever it was set to
882 before. 700 before.
883 </li> 701 </li>
884</ul> 702</ul>
885 703
886<p> 704<p>
887This should install the correct driver directory structure under 705This should install the correct driver directory structure under
888<path>/etc/samba/printer</path>. That would be 706<path>/etc/samba/printer</path>. That would be
889<path>/etc/samba/printer/W32X86/2/</path>. The files contained should 707<path>/etc/samba/printer/W32X86/2/</path>. The files contained should be the 3
890be the 3 driver files and the PPD file, renamed to YourPrinterName.ppd 708driver 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). 709name which you gave the printer when installing it (see above).
892</p>
893
894<p> 710</p>
711
712<p>
895Pending no errors or other complications, your drivers are now 713Pending no errors or other complications, your drivers are now installed.
896installed.
897</p> 714</p>
898 715
899</body> 716</body>
900</section> 717</section>
901<section> 718<section>
919<title>Testing our Samba configuration</title> 736<title>Testing our Samba configuration</title>
920<body> 737<body>
921 738
922<p> 739<p>
923We will want to test our configuration file to ensure that it is formatted 740We will want to test our configuration file to ensure that it is formatted
924properly and all of our options have at least the correct syntax. To do 741properly and all of our options have at least the correct syntax. To do this we
925this we run <c>testparm</c>. 742run <c>testparm</c>.
926</p> 743</p>
927 744
928<pre caption="Running the testparm"> 745<pre caption="Running the testparm">
929<comment>(By default, testparm checks /etc/samba/smb.conf)</comment> 746<comment>(By default, testparm checks /etc/samba/smb.conf)</comment>
930# <i>/usr/bin/testparm</i> 747# <i>/usr/bin/testparm</i>
960<section> 777<section>
961<title>Checking our services</title> 778<title>Checking our services</title>
962<body> 779<body>
963 780
964<p> 781<p>
965It would probably be prudent to check our logs at this time also. 782It would probably be prudent to check our logs at this time also. We will also
966We will also want to take a peak at our Samba shares using 783want to take a peak at our Samba shares using <c>smbclient</c>.
967<c>smbclient</c>.
968</p> 784</p>
969 785
970<pre caption="Checking the shares with smbclient"> 786<pre caption="Checking the shares with smbclient">
971# <i>smbclient -L localhost</i> 787# <i>smbclient -L localhost</i>
972Password: 788Password:
982<section> 798<section>
983<title>Printer configuration of *nix based clients</title> 799<title>Printer configuration of *nix based clients</title>
984<body> 800<body>
985 801
986<p> 802<p>
987Despite the variation or distribution, the only thing needed is CUPS. Do the 803Despite the variation or distribution, the only thing needed is CUPS. Do the
988equivalent on any other UNIX/Linux/BSD client. 804equivalent on any other UNIX/Linux/BSD client.
989</p> 805</p>
990 806
991<pre caption="Configuring a Gentoo system"> 807<pre caption="Configuring a Gentoo system">
992# <i>emerge cups</i> 808# <i>emerge cups</i>
1023</pre> 839</pre>
1024 840
1025<p> 841<p>
1026Just point your web browser to <c>http://printserver:631</c> on the client if 842Just point your web browser to <c>http://printserver:631</c> on the client if
1027you want to manage your printers and their jobs with a nice web interface. 843you want to manage your printers and their jobs with a nice web interface.
1028Replace <c>printserver</c> with the name of the <e>machine</e> that acts as 844Replace <c>printserver</c> with the name of the <e>machine</e> that acts as your
1029your print server, not the name you gave to the cups print server if you used 845print server, not the name you gave to the cups print server if you used
1030different names. 846different names.
1031</p> 847</p>
1032 848
1033</body> 849</body>
1034</section> 850</section>
1035<section> 851<section>
1036<title>Mounting a Windows or Samba share in GNU/Linux</title> 852<title>Mounting a Windows or Samba share in GNU/Linux</title>
1037<body> 853<body>
1038 854
855<note>
856Don't forget to install <c>net-fs/samba</c> on the client(s) that will be
857accessing the shares.
858</note>
859
1039<p> 860<p>
1040Now is time to configure our kernel to support smbfs. Since I'm assumming we've 861Now is time to configure our kernel to support CIFS. Since I'm assuming
1041all compiled at least one kernel, we'll need to make sure we have all the right 862we've all compiled at least one kernel, we'll need to make sure we have all the
1042options selected in our kernel. For simplicity sake, make it a module for ease 863right options selected in our kernel. For simplicity's sake, make it a module
1043of use. It is the author's opinion that kernel modules are a good thing and 864for ease of use. It is the author's opinion that kernel modules are a good thing
1044should be used whenever possible. 865and should be used whenever possible.
1045</p>
1046
1047<pre caption="Relevant kernel options" >
1048CONFIG_SMB_FS=m
1049CONFIG_SMB_UNIX=y
1050</pre>
1051
1052<p> 866</p>
867
868<pre caption="Kernel support" >
869CONFIG_CIFS=m
870</pre>
871
872<p>
1053Then make the module/install it; insert them with: 873Then make the module/install it; insert it with:
1054</p> 874</p>
1055 875
1056<pre caption="Loading the kernel module"> 876<pre caption="Loading the kernel module">
1057# <i>modprobe smbfs</i> 877# <i>modprobe cifs</i>
1058</pre> 878</pre>
1059 879
1060<p> 880<p>
1061Once the modules is loaded, mounting a Windows or Samba share is 881Once the module is loaded, mounting a Windows or Samba share is possible. Use
1062possible. Use <c>mount</c> to accomplish this, as detailed below: 882<c>mount</c> to accomplish this, as detailed below:
1063</p> 883</p>
1064 884
1065<pre caption="Mounting a Windows/Samba share"> 885<pre caption="Mounting a Windows/Samba share">
1066<comment>(The syntax for mounting a Windows/Samba share is: 886<comment>(The syntax for mounting a Windows/Samba share is:
1067 mount -t smbfs [-o username=xxx,password=xxx] //server/share /mnt/point 887 mount -t cifs [-o username=xxx,password=xxx] //server/share /mnt/point
1068If we are not using passwords or a password is not needed)</comment> 888If we are not using passwords or a password is not needed)</comment>
1069 889
1070# <i>mount -t smbfs //PrintServer/public /mnt/public</i> 890# <i>mount -t cifs //PrintServer/public /mnt/public</i>
1071 891
1072<comment>(If a password is needed)</comment> 892<comment>(If a password is needed)</comment>
1073# <i>mount -t smbfs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i> 893# <i>mount -t cifs -o username=USERNAME,password=PASSWORD //PrintServer/public /mnt/public</i>
1074</pre> 894</pre>
1075 895
1076<p> 896<p>
1077After you mount the share, you would access it as if it were a local 897After you mount the share, you would access it as if it were a local drive.
1078drive.
1079</p> 898</p>
1080 899
1081</body> 900</body>
1082</section> 901</section>
1083<section> 902<section>
1084<title>Printer Configuration for Windows NT/2000/XP clients</title> 903<title>Printer Configuration for Windows NT/2000/XP clients</title>
1085<body> 904<body>
1086 905
1087<p> 906<p>
1088That's just a bit of point-and-click. Browse to 907That's just a bit of point-and-click. Browse to <path>\\PrintServer</path> and
1089<path>\\PrintServer</path> and right click on the printer 908right click on the printer (HPDeskJet930C) and click connect. This will download
1090(HPDeskJet930C) and click connect. This will download the drivers to
1091the Windows client and now every application (such as Word or Acrobat) 909the drivers to the Windows client and now every application (such as Word or
1092will offer HPDeskJet930C as an available printer to print to. :-) 910Acrobat) will offer HPDeskJet930C as an available printer to print to. :-)
1093</p> 911</p>
1094 912
1095</body> 913</body>
1096</section> 914</section>
1097</chapter> 915</chapter>
1101<section> 919<section>
1102<title>A Fond Farewell</title> 920<title>A Fond Farewell</title>
1103<body> 921<body>
1104 922
1105<p> 923<p>
1106Well that should be it. You should now have a successful printing enviroment 924That should be it. You should now have a successful printing enviroment that is
1107that is friendly to both Windows and *nix as well as a fully virus-free working 925friendly to both Windows and *nix as well as a working share!
1108share!
1109</p> 926</p>
1110 927
1111</body> 928</body>
1112</section> 929</section>
1113</chapter> 930</chapter>
1131 on Samba/CUPS configuration</uri> 948 on Samba/CUPS configuration</uri>
1132 </li> 949 </li>
1133 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li> 950 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li>
1134 <li> 951 <li>
1135 <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt 952 <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt
1136 Pfeifle's Samba Print HOWTO</uri> ( 953 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 954 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, 955 Samba, and generally printing support on networks. A really interesting
1140 with lots and lots of details) 956 read, with lots and lots of details.)
1141 </li> 957 </li>
1142 <li><uri link="http://www.freebsddiary.org/cups.php">FreeBSD Diary's CUPS Topic</uri></li> 958 <li><uri link="http://www.freebsddiary.org/cups.php">FreeBSD Diary's CUPS Topic</uri></li>
1143</ul> 959</ul>
1144 960
1145</body> 961</body>
1147<section> 963<section>
1148<title>Troubleshooting</title> 964<title>Troubleshooting</title>
1149<body> 965<body>
1150 966
1151<p> 967<p>
968See <uri
1152See <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37">this 969link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37">this
1153page</uri> from Kurt Pfeifle's "Printing Support in Samba 3.0" 970page</uri> from Kurt Pfeifle's "Printing Support in Samba 3.0" manual. Lots of
1154manual. Lots of useful tips there! Be sure to look this one up 971useful tips there! Be sure to look this one up first, before posting questions
1155first, before posting questions and problems! Maybe the solution 972and problems! Maybe the solution you're looking for is right there.
1156you're looking for is right there.
1157</p> 973</p>
1158 974
1159</body> 975</body>
1160</section> 976</section>
1161</chapter> 977</chapter>

Legend:
Removed from v.1.28  
changed lines
  Added in v.1.43

  ViewVC Help
Powered by ViewVC 1.1.20