/[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.4 Revision 1.28
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<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<guide link="quick-samba-howto.xml"> 4<guide link="/doc/en/quick-samba-howto.xml">
4<title>Gentoo Samba3/CUPS/Clam AV HOWTO</title> 5<title>Gentoo Samba3/CUPS/ClamAV HOWTO</title>
5<author title="Author"> 6<author title="Author">
6 <mail link="daff at dword dot org">Andreas "daff" Ntaflos</mail> 7 <mail link="daff at dword dot org">Andreas "daff" Ntaflos</mail>
7</author> 8</author>
8<author title="Author"> 9<author title="Author">
9 <mail link="joshua@sungentoo.homeunix.com">Joshua Preston</mail> 10 <mail link="joshua@sungentoo.homeunix.com">Joshua Preston</mail>
17 18
18<!-- The content of this document is licensed under the CC-BY-SA license --> 19<!-- The content of this document is licensed under the CC-BY-SA license -->
19<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 20<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
20<license/> 21<license/>
21 22
22<version>1.3</version> 23<version>1.17</version>
23<date>May 18, 2004</date> 24<date>2007-06-06</date>
24 25
25<chapter> 26<chapter>
26<title>Introduction to this HOWTO</title> 27<title>Introduction to this HOWTO</title>
27<section> 28<section>
28<title>Purpose</title> 29<title>Purpose</title>
29<body> 30<body>
30 31
31<p> 32<p>
32This HOWTO is designed to help you move a network from many different 33This HOWTO is designed to help you move a network from many different
33clients speaking different languages, to many different manchines that 34clients speaking different languages, to many different machines that
34speak a common language. The ultimate goal is to help differing 35speak a common language. The ultimate goal is to help differing
35architectures and technologies, come together in a productive, 36architectures and technologies, come together in a productive,
36happily coexisting environment. 37happily coexisting environment.
37</p> 38</p>
38 39
85<section> 86<section>
86<title>Before you use this guide</title> 87<title>Before you use this guide</title>
87<body> 88<body>
88 89
89<p> 90<p>
90There are a several other guides for setting up CUPS and/or Samba, 91There are a several other guides for setting up CUPS and/or Samba, please read
91please read them as well, as they may tell you things left out of this 92them as well, as they may tell you things left out of this HOWTO (intentional
92HOWTO (intentional or otherwise). One such document is the very useful 93or otherwise). One such document is the very useful and well written <uri
93and well written <uri link="http://www.gentoo.org/doc/en/printing-howto.xml">Gentoo 94link="/doc/en/printing-howto.xml">Gentoo Printing Guide</uri>, as configuration
94Printing Guide</uri>, as configuration issues and specific printer setup 95issues and specific printer setup is not discussed here.
95is not discussed here.
96</p> 96</p>
97 97
98</body> 98</body>
99</section> 99</section>
100<section> 100<section>
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 CLAM-AV</li> 112 <li>Install and configure ClamAV</li>
113 <li>Install and configure Samba</li> 113 <li>Install and configure Samba</li>
114 <li>Install and configure CUPS</li> 114 <li>Install and configure CUPS</li>
115 <li>Adding the printer to CUPS</li> 115 <li>Adding the printer to CUPS</li>
116 <li>Adding the PS drivers for the Windows clients</li> 116 <li>Adding the PS drivers for the Windows clients</li>
117 </ul> 117 </ul>
141We will need the following: 141We will need the following:
142</p> 142</p>
143 143
144<ul> 144<ul>
145 <li>net-fs/samba</li> 145 <li>net-fs/samba</li>
146 <li>net-mail/clamav</li> 146 <li>app-antivirus/clamav</li>
147 <li>net-print/cups</li> 147 <li>net-print/cups</li>
148 <li>net-print/foomatic</li> 148 <li>net-print/foomatic</li>
149 <li>net-print/hpijs (if you have an HP printer)</li> 149 <li>net-print/hplip (if you have an HP printer)</li>
150 <li>A kernel of sorts (preferably 2.4.24+ or 2.6.x)</li> 150 <li>A kernel of sorts (2.6)</li>
151 <li>A printer (PS or non-PS, maybe not TOO new or fancy)</li> 151 <li>A printer (PS or non-PS, maybe not TOO new or fancy)</li>
152 <li> 152 <li>
153 A working network (home/office/etc) consisting of more than one machine) 153 A working network (home/office/etc) consisting of more than one machine)
154 </li> 154 </li>
155</ul> 155</ul>
156 156
157<p> 157<p>
158The main package we use here is net-fs/samba, however, you will need 158The main package we use here is net-fs/samba, however, you will need
159a kernel with smbfs support enabled in order to mount a samba or windows 159a kernel with smbfs support enabled in order to mount a samba or windows
160share from another computer. CUPS will be emerged if it is not already. 160share from another computer. CUPS will be emerged if it is not already.
161net-mail/clamav will be used also, but others should be easily adapted 161app-antivirus/clamav will be used also, but others should be easily adapted
162to work with Samba. 162to work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning
163technologies, such as Sophos, FProt, Fsav, Trend, Icap, Nai, ...
163</p> 164</p>
164 165
165</body> 166</body>
166</section> 167</section>
167</chapter> 168</chapter>
169
168<chapter> 170<chapter>
169<title>Getting acquainted with Samba</title> 171<title>Getting acquainted with Samba</title>
170<section> 172<section>
171<title>The USE Flags</title> 173<title>The USE Flags</title>
172<body> 174<body>
173 175
174<p> 176<p>
175Before emerging anything, take a look at the various USE flags 177Before emerging anything, take a look at some of the various USE flags available
176available to Samba. 178to Samba.
177</p> 179</p>
178 180
179<pre caption="Samba uses the following USE Variables:"> 181<pre caption="Samba uses the following USE Variables:">
180kerberos mysql xml acl cups ldap pam readline python oav 182kerberos acl cups ldap pam readline python oav
181</pre> 183</pre>
182 184
183<p> 185<p>
184Depending on the network topology and the specific requirements of 186Depending on the network topology and the specific requirements of
185the server, the USE flags outlined below will define what to include or 187the server, the USE flags outlined below will define what to include or
195 <th><b>kerberos</b></th> 197 <th><b>kerberos</b></th>
196 <ti> 198 <ti>
197 Include support for Kerberos. The server will need this if it is 199 Include support for Kerberos. The server will need this if it is
198 intended to join an existing domain or Active Directory. See the note 200 intended to join an existing domain or Active Directory. See the note
199 below for more information. 201 below for more information.
200 </ti>
201</tr>
202<tr>
203 <th><b>mysql</b></th>
204 <ti>
205 This will allow Samba to use MySQL in order to do password authentication.
206 It will store ACLs, usernames, passwords, etc in a database versus a
207 flat file. If Samba is needed to do password authentication, such as
208 acting as a password validation server or a Primary Domain Controller
209 (PDC).
210 </ti>
211</tr>
212<tr>
213 <th><b>xml</b></th>
214 <ti>
215 The xml USE option for Samba provides a password database backend allowing
216 Samba to store account details in XML files, for the same reasons listed in
217 the mysql USE flag description.
218 </ti> 202 </ti>
219</tr> 203</tr>
220<tr> 204<tr>
221 <th><b>acl</b></th> 205 <th><b>acl</b></th>
222 <ti> 206 <ti>
254 </ti> 238 </ti>
255</tr> 239</tr>
256<tr> 240<tr>
257 <th><b>readline</b></th> 241 <th><b>readline</b></th>
258 <ti> 242 <ti>
259 Link Samba again libreadline. This is highly recommended and should 243 Link Samba against libreadline. This is highly recommended and should
260 probably not be disabled 244 probably not be disabled
261 </ti> 245 </ti>
262</tr> 246</tr>
263<tr> 247<tr>
264 <th><b>python</b></th> 248 <th><b>python</b></th>
291 <li> 275 <li>
292 While Active Directory, ACL, and PDC functions are out of the intended 276 While Active Directory, ACL, and PDC functions are out of the intended
293 scope of this HOWTO, you may find these links as helpful to your cause: 277 scope of this HOWTO, you may find these links as helpful to your cause:
294 <ul> 278 <ul>
295 <li><uri>http://www.bluelightning.org/linux/samba_acl_howto/</uri></li> 279 <li><uri>http://www.bluelightning.org/linux/samba_acl_howto/</uri></li>
296 <li><uri>http://open-projects.linuxcare.com/research-papers/winbind-08162000.html</uri></li>
297 <li><uri>http://www.wlug.org.nz/HowtoSamba3AndActiveDirectory</uri></li> 280 <li><uri>http://www.wlug.org.nz/HowtoSamba3AndActiveDirectory</uri></li>
298 </ul> 281 </ul>
299 </li> 282 </li>
300</ul> 283</ul>
301 284
302</body> 285</body>
303</section> 286</section>
304</chapter> 287</chapter>
288
305<chapter> 289<chapter>
306<title>Server Software Installation</title> 290<title>Server Software Installation</title>
307<section> 291<section>
308<title>Emerging Samba</title> 292<title>Emerging Samba</title>
309<body> 293<body>
333To optimize performance, size and the time of the build, the 317To optimize performance, size and the time of the build, the
334USE flags are specifically included or excluded. 318USE flags are specifically included or excluded.
335</p> 319</p>
336 320
337<pre caption="Emerge Samba"> 321<pre caption="Emerge Samba">
338<comment>(Note the USE flags!)</comment> 322# <i>echo "net-fs/samba oav readline cups pam" &gt;&gt; /etc/portage/package.use</i>
339# <i>USE=&quot;oav readline cups pam -python -ldap -kerberos -xml -acl -mysql&quot; emerge net-fs/samba</i> 323# <i>emerge net-fs/samba</i>
340</pre> 324</pre>
341 325
342<note> 326<note>
343The following archs will need to add <e>~</e> to their <e>KEYWORDS</e>: x86, 327The following archs will need to add <e>~</e> to their <e>KEYWORDS</e>: x86,
344ppc, sparc, hppa, ia64 and alpha 328ppc, sparc, hppa, ia64 and alpha
349</p> 333</p>
350 334
351</body> 335</body>
352</section> 336</section>
353<section> 337<section>
354<title>Emerging Clam AV</title> 338<title>Emerging ClamAV</title>
355<body> 339<body>
356 340
357<p> 341<p>
358Because the <e>oav</e> USE flag only provides an interface to allow on access 342Because the <e>oav</e> USE flag only provides an interface to allow on access
359virus scanning, the actual virus scanner must be emerged. The scanner 343virus scanning, the actual virus scanner must be emerged. The scanner
360used in this HOWTO is Clam AV. 344used in this HOWTO is ClamAV.
361</p> 345</p>
362 346
363<pre caption="Emerge clam-av"> 347<pre caption="Emerge Clamav">
364# <i>emerge net-mail/clamav</i> 348# <i>emerge app-antivirus/clamav</i>
365</pre> 349</pre>
366 350
367</body> 351</body>
368</section> 352</section>
369<section> 353<section>
375</pre> 359</pre>
376 360
377</body> 361</body>
378</section> 362</section>
379<section> 363<section>
380<title>Emerging net-print/hpijs</title> 364<title>Emerging net-print/hplip</title>
381<body> 365<body>
382 366
383<p> 367<p>
384You only need to emerge this if you use an HP printer. 368You only need to emerge this if you use an HP printer.
385</p> 369</p>
386 370
387<pre caption="Emerge hpijs"> 371<pre caption="Emerge hplip">
388# <i>emerge net-print/hpijs</i> 372# <i>emerge net-print/hplip</i>
389</pre> 373</pre>
390 374
391</body> 375</body>
392</section> 376</section>
393</chapter> 377</chapter>
378
394<chapter> 379<chapter>
395<title>Server Configuration</title> 380<title>Server Configuration</title>
396<section> 381<section>
397<title>Configuring Samba</title> 382<title>Configuring Samba</title>
398<body> 383<body>
410<pre caption="A Sample /etc/samba/smb.conf"> 395<pre caption="A Sample /etc/samba/smb.conf">
411[global] 396[global]
412<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment> 397<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment>
413workgroup = <comment>MYWORKGROUPNAME</comment> 398workgroup = <comment>MYWORKGROUPNAME</comment>
414<comment># Of course this has no REAL purpose other than letting 399<comment># Of course this has no REAL purpose other than letting
415# everyone know its not Windows! 400# everyone knows it's not Windows!
416# %v prints the version of Samba we are using.</comment> 401# %v prints the version of Samba we are using.</comment>
417server string = Samba Server %v 402server string = Samba Server %v
418<comment># We are going to use cups, so we are going to put it in here ;-)</comment> 403<comment># We are going to use cups, so we are going to put it in here ;-)</comment>
419printcap name = cups 404printcap name = cups
420printing = cups 405printing = cups
442guest ok = yes 427guest ok = yes
443<comment># We now will implement the on access virus scanner. 428<comment># We now will implement the on access virus scanner.
444# NOTE: By putting this in our [Global] section, we enable 429# NOTE: By putting this in our [Global] section, we enable
445# scanning of ALL shares, you could optionally move 430# scanning of ALL shares, you could optionally move
446# these to a specific share and only scan it.</comment> 431# these to a specific share and only scan it.</comment>
447vfs object = /usr/lib/samba/vfs/vscan-clamav.so 432
433<comment># For Samba 3.x. This enables ClamAV on access scanning.</comment>
434vfs object = vscan-clamav
448vfs options = config-file = /etc/samba/vscan-clamav.conf 435vscan-clamav: config-file = /etc/samba/vscan-clamav.conf
449 436
450<comment># Now we setup our print drivers information!</comment> 437<comment># Now we setup our print drivers information!</comment>
451[print$] 438[print$]
452comment = Printer Drivers 439comment = Printer Drivers
453path = /etc/samba/printer <comment># this path holds the driver structure</comment> 440path = /etc/samba/printer <comment># this path holds the driver structure</comment>
454guest ok = no 441guest ok = yes
455browseable = yes 442browseable = yes
456read only = yes 443read only = yes
457<comment># Modify this to "username,root" if you don't want root to 444<comment># Modify this to "username,root" if you don't want root to
458# be the only printer admin)</comment> 445# be the only printer admin)</comment>
459write list = <i>root</i> 446write list = <i>root</i>
472 459
473<comment># Now we setup our printers share. This should be 460<comment># Now we setup our printers share. This should be
474# browseable, printable, public.</comment> 461# browseable, printable, public.</comment>
475[printers] 462[printers]
476comment = All Printers 463comment = All Printers
477browseable = yes 464browseable = no
478printable = yes 465printable = yes
466writable = no
479public = yes 467public = yes
480guest ok = yes 468guest ok = yes
481path = /var/spool/samba 469path = /var/spool/samba
482<comment># Modify this to "username,root" if you don't want root to 470<comment># Modify this to "username,root" if you don't want root to
483# be the only printer admin)</comment> 471# be the only printer admin)</comment>
494guest ok = yes 482guest ok = yes
495path = /home/samba/public 483path = /home/samba/public
496</pre> 484</pre>
497 485
498<warn> 486<warn>
499
500If you like to use Samba's guest account to do anything concerning 487If you like to use Samba's guest account to do anything concerning
501printing from Windows clients: don't set <c>guest only = yes</c> in 488printing from Windows clients: don't set <c>guest only = yes</c> in
502the <c>[global]</c> section. The guest account seems to cause 489the <c>[global]</c> section. The guest account seems to cause
503problems when running <c>cupsaddsmb</c> sometimes when trying to 490problems when running <c>cupsaddsmb</c> sometimes when trying to
504connect from Windows machines. See below, too, when we talk about 491connect from Windows machines. See below, too, when we talk about
506printer user, like <c>printeruser</c> or <c>printer</c> or 493printer user, like <c>printeruser</c> or <c>printer</c> or
507<c>printme</c> or whatever. It doesn't hurt and it will certainly 494<c>printme</c> or whatever. It doesn't hurt and it will certainly
508protect you from a lot of problems. 495protect you from a lot of problems.
509</warn> 496</warn>
510 497
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
511<p> 503<p>
512Now create the directories required for the minimum configuration of 504Now create the directories required for the minimum configuration of
513Samba to share the installed printer throughout the network. 505Samba to share the installed printer throughout the network.
514</p> 506</p>
515 507
535<p> 527<p>
536The Samba passwords need not be the same as the system passwords 528The Samba passwords need not be the same as the system passwords
537in <path>/etc/passwd</path>. 529in <path>/etc/passwd</path>.
538</p> 530</p>
539 531
532<p>
533You will also need to update <path>/etc/nsswitch.conf</path> so that Windows
534systems can be found easily using NetBIOS:
535</p>
536
537<pre caption="Editing /etc/nsswitch.conf">
538# <i>nano -w /etc/nsswitch.conf</i>
539<comment>(Edit the hosts: line)</comment>
540hosts: files dns <i>wins</i>
541</pre>
542
540</body> 543</body>
541</section>
542<section> 544</section>
545<section>
543<title>Configuring Clam AV</title> 546<title>Configuring ClamAV</title>
544<body> 547<body>
545 548
546<p> 549<p>
547The configuration file specified to be used in <path>smb.conf</path> is 550The configuration file specified to be used in <path>smb.conf</path> is
548<path>/etc/samba/vscan-clamav.conf</path>. While these options are set 551<path>/etc/samba/vscan-clamav.conf</path>. While these options are set
571 574
572<comment>; if communication to clamd fails, should access to file denied? 575<comment>; if communication to clamd fails, should access to file denied?
573; (default: yes)</comment> 576; (default: yes)</comment>
574deny access on error = yes 577deny access on error = yes
575 578
576<comment>; if daemon files with a minor error (corruption, etc.), 579<comment>; if daemon fails with a minor error (corruption, etc.),
577; should access to file denied? 580; should access to file denied?
578; (default: yes)</comment> 581; (default: yes)</comment>
579deny access on minor error = yes 582deny access on minor error = yes
580 583
581<comment>; send a warning message via Windows Messenger service 584<comment>; send a warning message via Windows Messenger service
599; of period, samba-vscan use a last recently used file mechanism to avoid 602; of period, samba-vscan use a last recently used file mechanism to avoid
600; multiple scans of a file. This setting specified the maximum number of 603; multiple scans of a file. This setting specified the maximum number of
601; elements of the last recently used file list. (default: 100)</comment> 604; elements of the last recently used file list. (default: 100)</comment>
602max lru files entries = 100 605max lru files entries = 100
603 606
604<comment>; an entry is invalidad after lru file entry lifetime (in seconds). 607<comment>; an entry is invalidated after lru file entry lifetime (in seconds).
605; (Default: 5)</comment> 608; (Default: 5)</comment>
606lru file entry lifetime = 5 609lru file entry lifetime = 5
607 610
608<comment>; socket name of clamd (default: /var/run/clamd)</comment> 611<comment>; socket name of clamd (default: /var/run/clamd)</comment>
609clamd socket name = /var/run/clamd 612clamd socket name = /tmp/clamd
613
614<comment>; port number the ScannerDaemon listens on</comment>
615oav port = 8127
610</pre> 616</pre>
611 617
612<p> 618<p>
613It is generally a good idea to start the virus scanner immediately. Add 619It is generally a good idea to start the virus scanner immediately. Add
614it to the <e>default</e> runlevel and then start the <c>clamd</c> service immediately. 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.
615</p> 637</p>
616 638
617<pre caption="Add clamd to bootup and start it"> 639<pre caption="Add clamd to bootup and start it">
618# <i>rc-update add clamd default</i> 640# <i>rc-update add clamd default</i>
619# <i>/etc/init.d/clamd start</i> 641# <i>/etc/init.d/clamd start</i>
632in the example are the directives that need to be changed: 654in the example are the directives that need to be changed:
633</p> 655</p>
634 656
635<pre caption="/etc/cups/cupsd.conf"> 657<pre caption="/etc/cups/cupsd.conf">
636ServerName <i>PrintServer</i> <comment># your printserver name</comment> 658ServerName <i>PrintServer</i> <comment># your printserver name</comment>
637ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, eg you</comment> 659ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, e.g. you</comment>
638 660
639AccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment> 661AccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment>
640ErrorLog /var/log/cups/error_log <comment># doesn't really need changing either</comment> 662ErrorLog /var/log/cups/error_log <comment># doesn't really need changing either</comment>
641 663
642LogLevel debug <comment># only while isntalling and testing, should later be 664LogLevel debug <comment># only while isntalling and testing, should later be
643 # changed to 'info'</comment> 665 # changed to 'info'</comment>
644 666
645MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back, 667MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back,
646 # there seemed to be a bug in CUPS' controlling of the web interface, 668 # there seemed to be a bug in CUPS' controlling of the web interface,
647 # making CUPS think a denial of service attack was in progress when 669 # making CUPS think a denial of service attack was in progress when
648 # I tried to configure a printer with the web interface. weird.</comment> 670 # I tried to configure a printer with the web interface. weird.</comment>
651 673
652&lt;Location /&gt; 674&lt;Location /&gt;
653Order Deny,Allow 675Order Deny,Allow
654Deny From All 676Deny From All
655Allow From <i>192.168.1.*</i> <comment># the addresses of your internel network 677Allow From <i>192.168.1.*</i> <comment># the addresses of your internel network
656 # eg 192.168.1.* will allow connections from any host on 678 # e.g. 192.168.1.* will allow connections from any host on
657 # the 192.168.1.0 network. change to whatever suits you</comment> 679 # the 192.168.1.0 network. change to whatever suits you</comment>
658&lt;/Location&gt; 680&lt;/Location&gt;
659 681
660&lt;Location /admin&gt; 682&lt;Location /admin&gt;
661AuthType Basic 683AuthType Basic
678<comment>(The following line is found near the end of the file. Uncomment it)</comment> 700<comment>(The following line is found near the end of the file. Uncomment it)</comment>
679application/octet-stream application/vnd.cups-raw 0 701application/octet-stream application/vnd.cups-raw 0
680</pre> 702</pre>
681 703
682<p> 704<p>
683Edit <path>/etc/cups/mime.convs</path> to uncomment some lines. 705Edit <path>/etc/cups/mime.types</path> to uncomment some lines.
684</p> 706</p>
685 707
686<pre caption="/etc/cups/mime.types"> 708<pre caption="/etc/cups/mime.types">
687<comment>(The following line is found near the end of the file. Uncomment it)</comment> 709<comment>(The following line is found near the end of the file. Uncomment it)</comment>
688application/octet-stream 710application/octet-stream
693</p> 715</p>
694 716
695<pre caption="Setting up the CUPS service" > 717<pre caption="Setting up the CUPS service" >
696<comment>(To start CUPS on boot)</comment> 718<comment>(To start CUPS on boot)</comment>
697# <i>rc-update add cupsd default</i> 719# <i>rc-update add cupsd default</i>
698<comment>(To start CUPS if it isn't started)</comment> 720<comment>(To start or restart CUPS now)</comment>
699# <i>/etc/init.d/cupsd start</i>
700<comment>(If CUPS is already started we'll need to restart it!)</comment>
701# <i>/etc/init.d/cupsd restart</i> 721# <i>/etc/init.d/cupsd restart</i>
702</pre> 722</pre>
703 723
704</body> 724</body>
705</section> 725</section>
706<section> 726<section>
707<title>Installing a printer for and with CUPS</title> 727<title>Installing a printer for and with CUPS</title>
708<body> 728<body>
709 729
710<p> 730<p>
711First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> 731First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> to
712to find and download the correct PPD file for your printer and CUPS. To 732find and download the correct PPD file for your printer and CUPS. To do so,
713do so, click the link Printer Listings to the left. Select your 733click the link Printer Listings to the left. Select your printers manufacturer
714printers manufacturer and the model in the pulldown menu, eg HP and 734and the model in the pulldown menu, e.g. HP and DeskJet 930C. Click "Show". On
715DeskJet 930C. Click "Show". On the page coming up click the "recommended 735the page coming up click the "recommended driver" link after reading the
716driver" link after reading the various notes and information. Then fetch 736various notes and information. Then fetch the PPD file from the next page,
717the PPD file from the next page, again after reading the notes and 737again after reading the notes and introductions there. You may have to select
718introductions there. You may have to select your printers manufacturer 738your printers manufacturer and model again. Reading the <uri
719and model again. Reading the <uri link="http://www.linuxprinting.org/cups-doc.html">CUPS 739link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri>
720quickstart guide</uri> is also very helpful when working with CUPS. 740is also very helpful when working with CUPS.
721</p> 741</p>
722 742
723<p> 743<p>
724Now you have a PPD file for your printer to work with CUPS. Place it in 744Now you have a PPD file for your printer to work with CUPS. Place it in
725<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was 745<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was
728interface is found at <path>http://PrintServer:631</path> once CUPS is running. 748interface is found at <path>http://PrintServer:631</path> once CUPS is running.
729</p> 749</p>
730 750
731<pre caption="Install the printer via command line"> 751<pre caption="Install the printer via command line">
732# <i>lpadmin -p HPDeskJet930C -E -v usb:/dev/ultp0 -m HP-DeskJet_930C-hpijs.ppd</i> 752# <i>lpadmin -p HPDeskJet930C -E -v usb:/dev/ultp0 -m HP-DeskJet_930C-hpijs.ppd</i>
753# <i>/etc/init.d/cupsd restart</i>
733</pre> 754</pre>
734 755
735<p> 756<p>
736Remember to adjust to what you have. Be sure to have the name 757Remember to adjust to what you have. Be sure to have the name
737(<c>-p</c> argument) right (the name you set above during the Samba 758(<c>-p</c> argument) right (the name you set above during the Samba
759drivers automagically to the connecting client, avoiding the hassle of 780drivers automagically to the connecting client, avoiding the hassle of
760manually installing printer drivers locally. 781manually installing printer drivers locally.
761</p> 782</p>
762 783
763<p> 784<p>
764There are two sets of printer drivers for this. First, the Adobe PS 785There are two sets of printer drivers for this. First, the Adobe PS drivers
765drivers which can be obtained from <uri 786which can be obtained from <uri
766link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> 787link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript
767(PostScript printer drivers). Second, there are the CUPS PS drivers, 788printer drivers). Second, there are the CUPS PS drivers, to be obtained <uri
768to be obtained from <uri link="http://www.cups.org/software.php">the 789link="http://dev.gentoo.org/~nightmorph/misc/cups-samba-5.0rc2.tar.gz">here</uri>.
769CUPS homepage</uri> and selecting "CUPS Driver for Windows" from the 790There doesn't seem to be a difference between the functionality of the two, but
770pull down menu. There doesn't seem to be a difference between the 791the Adobe PS drivers need to be extracted on a Windows System since it's a
771functionality of the two, but the Adobe PS drivers need to be extracted 792Windows binary. Also the whole procedure of finding and copying the correct
772on a Windows System since it's a Windows binary. Also the whole procedure 793files is a bit more hassle. The CUPS drivers seem to support some options the
773of finding and copying the correct files is a bit more hassle. The CUPS 794Adobe drivers don't.
774drivers seem to support some options the Adobe drivers don't.
775</p> 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-->
776 800
777<p> 801<p>
778This HOWTO uses the CUPS drivers for Windows. The downloaded file is 802This HOWTO uses the CUPS drivers for Windows. The downloaded file is
779called <path>cups-samba-5.0rc2.tar.gz</path>. Extract the files 803called <path>cups-samba-5.0rc2.tar.gz</path>. Extract the files
780contained into a directory. 804contained into a directory.
792<path>cups5.hlp</path>, <path>cupsdrvr5.dll</path> and 816<path>cups5.hlp</path>, <path>cupsdrvr5.dll</path> and
793<path>cupsui5.dll</path>. These are the actual driver files. 817<path>cupsui5.dll</path>. These are the actual driver files.
794</p> 818</p>
795 819
796<warn> 820<warn>
797The script <c>cups-samba.install</c> may not work for all *nixes (ie FreeBSD) 821The script <c>cups-samba.install</c> may not work for all *nixes (i.e. FreeBSD)
798because almost everything which is not part of the base system is 822because almost everything which is not part of the base system is
799installed somewhere under the prefix <path>/usr/local/</path>. This 823installed somewhere under the prefix <path>/usr/local/</path>. This
800seems not to be the case for most things you install under GNU/Linux. 824seems not to be the case for most things you install under GNU/Linux.
801However, if your CUPS installation is somewhere other than 825However, if your CUPS installation is somewhere other than
802<path>/usr/share/cups/</path> see the example below. 826<path>/usr/share/cups/</path> see the example below.
813# <i>tar -xf cups-samba.ss</i> 837# <i>tar -xf cups-samba.ss</i>
814<comment>(This extracts the files to usr/share/cups/drivers under the CURRENT WORKING DIRECTORY)</comment> 838<comment>(This extracts the files to usr/share/cups/drivers under the CURRENT WORKING DIRECTORY)</comment>
815# <i>cd usr/share/cups/drivers</i> 839# <i>cd usr/share/cups/drivers</i>
816<comment>(no leading / !)</comment> 840<comment>(no leading / !)</comment>
817# <i>cp cups* /usr/local/share/cups/drivers</i> 841# <i>cp cups* /usr/local/share/cups/drivers</i>
842# <i>/etc/init.d/cupsd restart</i>
818</pre> 843</pre>
819 844
820<p> 845<p>
821Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS 846Now we'll use the script <c>cupsaddsmb</c> provided by the CUPS distribution.
822distribution. It's man page is an interesting read. 847Its man page is an interesting read.
823</p> 848</p>
824 849
825<pre caption="Run cupsaddsmb"> 850<pre caption="Run cupsaddsmb">
826# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -v HPDeskJet930C</i> 851# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -v HPDeskJet930C</i>
827<comment>(Instead of HPDeskJet930C you could also specify "-a", which will 852<comment>(Instead of HPDeskJet930C you could also specify "-a", which will
828"export all known printers".)</comment> 853"export all known printers".)</comment>
829# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -a</i> 854# <i>cupsaddsmb -H PrintServer -U root -h PrintServer -a</i>
830</pre> 855</pre>
831 856
832<warn> 857<warn>
833The execution of this command often causes the most trouble. 858The execution of this command often causes the most trouble. Read through the
834Reading through the <uri
835link="http://forums.gentoo.org/viewtopic.php?t=110931">posts in this 859<uri link="http://forums.gentoo.org/viewtopic.php?t=110931">posts in this
836thread</uri>. 860thread</uri> for some troubleshooting tips.
837</warn> 861</warn>
838 862
839<p> 863<p>
840Here are common errors that may happen: 864Here are common errors that may happen:
841</p> 865</p>
950</pre> 974</pre>
951 975
952</body> 976</body>
953</section> 977</section>
954</chapter> 978</chapter>
979
955<chapter> 980<chapter>
956<title>Configuration of the Clients</title> 981<title>Configuration of the Clients</title>
957<section> 982<section>
958<title>Printer configuration of *nix based clients</title> 983<title>Printer configuration of *nix based clients</title>
959<body> 984<body>
960 985
961<p> 986<p>
962Despite the variation or distribution, the only thing needed is CUPS. 987Despite the variation or distribution, the only thing needed is CUPS. Do the
963Do the equivalent on any other UNIX/Linux/BSD client. 988equivalent on any other UNIX/Linux/BSD client.
964</p> 989</p>
965 990
966<pre caption="Configuring a Gentoo system."> 991<pre caption="Configuring a Gentoo system">
967# <i>emerge cups</i> 992# <i>emerge cups</i>
968# <i>/etc/init.d/cupsd start</i> 993# <i>nano -w /etc/cups/client.conf</i>
969# <i>rc-update add cupsd default</i> 994ServerName <i>PrintServer</i> <comment># your printserver name</comment>
970</pre> 995</pre>
971 996
972<p>
973That should be it. Nothing else will be needed. Just point your web
974browser to <c>http://localhost:631</c> on the client and you'll see that
975PrintServer broadcasts all available printers to all CUPS clients.
976</p> 997<p>
977 998That should be it. Nothing else will be needed.
978<p> 999</p>
979To print, use for example 1000
980</p> 1001<p>
1002If you use only one printer, it will be your default printer. If your print
1003server manages several printers, your administrator will have defined a default
1004printer on the server. If you want to define a different default printer for
1005yourself, use the <c>lpoptions</c> command.
1006</p>
1007
1008<pre caption="Setting your default printer">
1009<comment>(List available printers)</comment>
1010# <i>lpstat -a</i>
1011<comment>(Sample output, yours will differ)</comment>
1012HPDeskJet930C accepting requests since Jan 01 00:00
1013laser accepting requests since Jan 01 00:00
1014<comment>(Define HPDeskJet930C as your default printer)</comment>
1015# <i>lpoptions -d HPDeskJet930C</i>
1016</pre>
981 1017
982<pre caption="Printing in *nix"> 1018<pre caption="Printing in *nix">
1019<comment>(Specify the printer to be used)</comment>
983# <i>lpr -pHPDeskJet930C anything.txt</i> 1020# <i>lp -d HPDeskJet930C anything.txt</i>
984# <i>lpr -PHPDeskJet930C foobar.whatever.ps</i> 1021<comment>(Use your default printer)</comment>
985</pre>
986
987<p>
988In order to setup a default printer, you have to edit
989<path>/etc/cups/client.conf</path> and set the directive
990<c>ServerName</c> to your printserver. In the case of this guide that
991would be the following example.
992</p>
993
994<pre caption="/etc/cups/client.conf">
995ServerName PrintServer
996</pre>
997
998<p>
999The following will print <path>foorbar.whatever.ps</path> directly to the print
1000server.
1001</p>
1002
1003<pre caption="Printing to the default printer">
1004$ <i>lpr foobar.whatever.ps</i> 1022# <i>lp foobar.whatever.ps</i>
1005</pre> 1023</pre>
1006 1024
1007<p>
1008Some common observations when setting a default printer in this manner
1009include the following:
1010</p> 1025<p>
1011 1026Just point your web browser to <c>http://printserver:631</c> on the client if
1012<ul> 1027you want to manage your printers and their jobs with a nice web interface.
1013 <li> 1028Replace <c>printserver</c> with the name of the <e>machine</e> that acts as
1014 Setting the <c>ServerName</c> in <path>client.conf</path> seems to 1029your print server, not the name you gave to the cups print server if you used
1015 work well for only one printer, there may be yet another way to 1030different names.
1016 set a client's default remote printer. 1031</p>
1017 </li>
1018 <li>
1019 Also, when accessing <c>http://localhost:631</c> on the client
1020 now, no printers seem to be "found" by the client-CUPS. This is to
1021 be expected when setting <c>ServerName</c> in
1022 <path>client.conf</path>.
1023 </li>
1024</ul>
1025 1032
1026</body> 1033</body>
1027</section> 1034</section>
1028<section> 1035<section>
1029<title>Mounting a Windows or Samba share in GNU/Linux</title> 1036<title>Mounting a Windows or Samba share in GNU/Linux</title>
1030<body> 1037<body>
1031 1038
1032<p> 1039<p>
1033Now is time to configure our kernel to support smbfs. Since I'm 1040Now is time to configure our kernel to support smbfs. Since I'm assumming we've
1034assumming we've all compiled at least one kernel, we'll need to make 1041all compiled at least one kernel, we'll need to make sure we have all the right
1035sure we have all the right options selected in our kernel. 1042options selected in our kernel. For simplicity sake, make it a module for ease
1036For simplicity sake, make it a module for ease of use. It is the
1037authors opinion that kernel modules are a good thing and should be used 1043of use. It is the author's opinion that kernel modules are a good thing and
1038whenever possible. 1044should be used whenever possible.
1039</p> 1045</p>
1040 1046
1041<pre caption="Relevant kernel options" > 1047<pre caption="Relevant kernel options" >
1042CONFIG_SMB_FS=m 1048CONFIG_SMB_FS=m
1043CONFIG_SMB_UNIX=y 1049CONFIG_SMB_UNIX=y
1087</p> 1093</p>
1088 1094
1089</body> 1095</body>
1090</section> 1096</section>
1091</chapter> 1097</chapter>
1098
1092<chapter> 1099<chapter>
1093<title>Final Notes</title> 1100<title>Final Notes</title>
1094<section> 1101<section>
1095<title>A Fond Farewell</title> 1102<title>A Fond Farewell</title>
1096<body> 1103<body>
1102</p> 1109</p>
1103 1110
1104</body> 1111</body>
1105</section> 1112</section>
1106</chapter> 1113</chapter>
1114
1107<chapter> 1115<chapter>
1108<title>Links and Resources</title> 1116<title>Links and Resources</title>
1109<section> 1117<section>
1110<title>Links</title> 1118<title>Links</title>
1111<body> 1119<body>
1115troubleshooting your installation: 1123troubleshooting your installation:
1116</p> 1124</p>
1117 1125
1118<ul> 1126<ul>
1119 <li><uri link="http://www.cups.org/">CUPS Homepage</uri></li> 1127 <li><uri link="http://www.cups.org/">CUPS Homepage</uri></li>
1128 <li>
1120 <li><uri link="http://www.samba.org/">Samba Homepage</uri></li> 1129 <uri link="http://www.samba.org/">Samba Homepage</uri>, especially the <uri
1130 link="http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/CUPS-printing.html">chapter
1131 on Samba/CUPS configuration</uri>
1132 </li>
1121 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li> 1133 <li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li>
1122 <li> 1134 <li>
1123 <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt 1135 <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt
1124 Pfeifle's Samba Print HOWTO</uri> ( 1136 Pfeifle's Samba Print HOWTO</uri> (
1125 This HOWTO really covers <e>ANYTHING</e> and <e>EVERYTHING</e> 1137 This HOWTO really covers <e>ANYTHING</e> and <e>EVERYTHING</e>

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

  ViewVC Help
Powered by ViewVC 1.1.20