/[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.20
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.20 2006/01/01 11:51:43 neysx 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="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.12</version>
23<date>May 18, 2004</date> 24<date>2005-03-26</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/hpijs (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 (preferably 2.4.24+ or 2.6.x)</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>
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>
175Before emerging anything, take a look at the various USE flags 177Before emerging anything, take a look at the various USE flags
176available to Samba. 178available to 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 mysql xml acl cups ldap pam readline python oav libclamav
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
254 </ti> 256 </ti>
255</tr> 257</tr>
256<tr> 258<tr>
257 <th><b>readline</b></th> 259 <th><b>readline</b></th>
258 <ti> 260 <ti>
259 Link Samba again libreadline. This is highly recommended and should 261 Link Samba against libreadline. This is highly recommended and should
260 probably not be disabled 262 probably not be disabled
261 </ti> 263 </ti>
262</tr> 264</tr>
263<tr> 265<tr>
264 <th><b>python</b></th> 266 <th><b>python</b></th>
273 Provides on-access scanning of Samba shares with FRISK F-Prot 275 Provides on-access scanning of Samba shares with FRISK F-Prot
274 Daemon, Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep 276 Daemon, Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep
275 (SAVI), Symantec CarrierScan, and Trend Micro (VSAPI). 277 (SAVI), Symantec CarrierScan, and Trend Micro (VSAPI).
276 </ti> 278 </ti>
277</tr> 279</tr>
280<tr>
281 <th><b>libclamav</b></th>
282 <ti>
283 Use the ClamAV library instead of the clamd daemon
284 </ti>
285</tr>
278</table> 286</table>
279 287
280<p> 288<p>
281A couple of things worth mentioning about the USE flags and different 289A couple of things worth mentioning about the USE flags and different
282Samba functions include: 290Samba functions include:
300</ul> 308</ul>
301 309
302</body> 310</body>
303</section> 311</section>
304</chapter> 312</chapter>
313
305<chapter> 314<chapter>
306<title>Server Software Installation</title> 315<title>Server Software Installation</title>
307<section> 316<section>
308<title>Emerging Samba</title> 317<title>Emerging Samba</title>
309<body> 318<body>
333To optimize performance, size and the time of the build, the 342To optimize performance, size and the time of the build, the
334USE flags are specifically included or excluded. 343USE flags are specifically included or excluded.
335</p> 344</p>
336 345
337<pre caption="Emerge Samba"> 346<pre caption="Emerge Samba">
338<comment>(Note the USE flags!)</comment> 347# <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> 348# <i>emerge net-fs/samba</i>
340</pre> 349</pre>
341 350
342<note> 351<note>
343The following archs will need to add <e>~</e> to their <e>KEYWORDS</e>: x86, 352The following archs will need to add <e>~</e> to their <e>KEYWORDS</e>: x86,
344ppc, sparc, hppa, ia64 and alpha 353ppc, sparc, hppa, ia64 and alpha
349</p> 358</p>
350 359
351</body> 360</body>
352</section> 361</section>
353<section> 362<section>
354<title>Emerging Clam AV</title> 363<title>Emerging ClamAV</title>
355<body> 364<body>
356 365
357<p> 366<p>
358Because the <e>oav</e> USE flag only provides an interface to allow on access 367Because 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 368virus scanning, the actual virus scanner must be emerged. The scanner
360used in this HOWTO is Clam AV. 369used in this HOWTO is ClamAV.
361</p> 370</p>
362 371
363<pre caption="Emerge clam-av"> 372<pre caption="Emerge Clamav">
364# <i>emerge net-mail/clamav</i> 373# <i>emerge app-antivirus/clamav</i>
365</pre> 374</pre>
366 375
367</body> 376</body>
368</section> 377</section>
369<section> 378<section>
389</pre> 398</pre>
390 399
391</body> 400</body>
392</section> 401</section>
393</chapter> 402</chapter>
403
394<chapter> 404<chapter>
395<title>Server Configuration</title> 405<title>Server Configuration</title>
396<section> 406<section>
397<title>Configuring Samba</title> 407<title>Configuring Samba</title>
398<body> 408<body>
410<pre caption="A Sample /etc/samba/smb.conf"> 420<pre caption="A Sample /etc/samba/smb.conf">
411[global] 421[global]
412<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment> 422<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment>
413workgroup = <comment>MYWORKGROUPNAME</comment> 423workgroup = <comment>MYWORKGROUPNAME</comment>
414<comment># Of course this has no REAL purpose other than letting 424<comment># Of course this has no REAL purpose other than letting
415# everyone know its not Windows! 425# everyone knows it's not Windows!
416# %v prints the version of Samba we are using.</comment> 426# %v prints the version of Samba we are using.</comment>
417server string = Samba Server %v 427server string = Samba Server %v
418<comment># We are going to use cups, so we are going to put it in here ;-)</comment> 428<comment># We are going to use cups, so we are going to put it in here ;-)</comment>
419printcap name = cups 429printcap name = cups
420printing = cups 430printing = cups
442guest ok = yes 452guest ok = yes
443<comment># We now will implement the on access virus scanner. 453<comment># We now will implement the on access virus scanner.
444# NOTE: By putting this in our [Global] section, we enable 454# NOTE: By putting this in our [Global] section, we enable
445# scanning of ALL shares, you could optionally move 455# scanning of ALL shares, you could optionally move
446# these to a specific share and only scan it.</comment> 456# these to a specific share and only scan it.</comment>
447vfs object = /usr/lib/samba/vfs/vscan-clamav.so 457
458<comment># For Samba 3.x. This enables ClamAV on access scanning.</comment>
459vfs object = vscan-clamav
448vfs options = config-file = /etc/samba/vscan-clamav.conf 460vscan-clamav: config-file = /etc/samba/vscan-clamav.conf
449 461
450<comment># Now we setup our print drivers information!</comment> 462<comment># Now we setup our print drivers information!</comment>
451[print$] 463[print$]
452comment = Printer Drivers 464comment = Printer Drivers
453path = /etc/samba/printer <comment># this path holds the driver structure</comment> 465path = /etc/samba/printer <comment># this path holds the driver structure</comment>
454guest ok = no 466guest ok = yes
455browseable = yes 467browseable = yes
456read only = yes 468read only = yes
457<comment># Modify this to "username,root" if you don't want root to 469<comment># Modify this to "username,root" if you don't want root to
458# be the only printer admin)</comment> 470# be the only printer admin)</comment>
459write list = <i>root</i> 471write list = <i>root</i>
472 484
473<comment># Now we setup our printers share. This should be 485<comment># Now we setup our printers share. This should be
474# browseable, printable, public.</comment> 486# browseable, printable, public.</comment>
475[printers] 487[printers]
476comment = All Printers 488comment = All Printers
477browseable = yes 489browseable = no
478printable = yes 490printable = yes
491writable = no
479public = yes 492public = yes
480guest ok = yes 493guest ok = yes
481path = /var/spool/samba 494path = /var/spool/samba
482<comment># Modify this to "username,root" if you don't want root to 495<comment># Modify this to "username,root" if you don't want root to
483# be the only printer admin)</comment> 496# be the only printer admin)</comment>
494guest ok = yes 507guest ok = yes
495path = /home/samba/public 508path = /home/samba/public
496</pre> 509</pre>
497 510
498<warn> 511<warn>
499
500If you like to use Samba's guest account to do anything concerning 512If 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 513printing from Windows clients: don't set <c>guest only = yes</c> in
502the <c>[global]</c> section. The guest account seems to cause 514the <c>[global]</c> section. The guest account seems to cause
503problems when running <c>cupsaddsmb</c> sometimes when trying to 515problems when running <c>cupsaddsmb</c> sometimes when trying to
504connect from Windows machines. See below, too, when we talk about 516connect from Windows machines. See below, too, when we talk about
506printer user, like <c>printeruser</c> or <c>printer</c> or 518printer user, like <c>printeruser</c> or <c>printer</c> or
507<c>printme</c> or whatever. It doesn't hurt and it will certainly 519<c>printme</c> or whatever. It doesn't hurt and it will certainly
508protect you from a lot of problems. 520protect you from a lot of problems.
509</warn> 521</warn>
510 522
523<warn>
524Turning on ClamAV on access scanning in the <c>[global]</c> section will slow
525down the performance of your Samba server dramatically.
526</warn>
527
511<p> 528<p>
512Now create the directories required for the minimum configuration of 529Now create the directories required for the minimum configuration of
513Samba to share the installed printer throughout the network. 530Samba to share the installed printer throughout the network.
514</p> 531</p>
515 532
535<p> 552<p>
536The Samba passwords need not be the same as the system passwords 553The Samba passwords need not be the same as the system passwords
537in <path>/etc/passwd</path>. 554in <path>/etc/passwd</path>.
538</p> 555</p>
539 556
557<p>
558You will also need to update <path>/etc/nsswitch.conf</path> so that Windows
559systems can be found easily using NetBIOS:
560</p>
561
562<pre caption="Editing /etc/nsswitch.conf">
563# <i>nano -w /etc/nsswitch.conf</i>
564<comment>(Edit the hosts: line)</comment>
565hosts: files dns <i>wins</i>
566</pre>
567
540</body> 568</body>
541</section>
542<section> 569</section>
570<section>
543<title>Configuring Clam AV</title> 571<title>Configuring ClamAV</title>
544<body> 572<body>
545 573
546<p> 574<p>
547The configuration file specified to be used in <path>smb.conf</path> is 575The 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 576<path>/etc/samba/vscan-clamav.conf</path>. While these options are set
571 599
572<comment>; if communication to clamd fails, should access to file denied? 600<comment>; if communication to clamd fails, should access to file denied?
573; (default: yes)</comment> 601; (default: yes)</comment>
574deny access on error = yes 602deny access on error = yes
575 603
576<comment>; if daemon files with a minor error (corruption, etc.), 604<comment>; if daemon fails with a minor error (corruption, etc.),
577; should access to file denied? 605; should access to file denied?
578; (default: yes)</comment> 606; (default: yes)</comment>
579deny access on minor error = yes 607deny access on minor error = yes
580 608
581<comment>; send a warning message via Windows Messenger service 609<comment>; send a warning message via Windows Messenger service
599; of period, samba-vscan use a last recently used file mechanism to avoid 627; 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 628; multiple scans of a file. This setting specified the maximum number of
601; elements of the last recently used file list. (default: 100)</comment> 629; elements of the last recently used file list. (default: 100)</comment>
602max lru files entries = 100 630max lru files entries = 100
603 631
604<comment>; an entry is invalidad after lru file entry lifetime (in seconds). 632<comment>; an entry is invalidated after lru file entry lifetime (in seconds).
605; (Default: 5)</comment> 633; (Default: 5)</comment>
606lru file entry lifetime = 5 634lru file entry lifetime = 5
607 635
608<comment>; socket name of clamd (default: /var/run/clamd)</comment> 636<comment>; socket name of clamd (default: /var/run/clamd)</comment>
609clamd socket name = /var/run/clamd 637clamd socket name = /tmp/clamd
638
639<comment>; port number the ScannerDaemon listens on</comment>
640oav port = 8127
610</pre> 641</pre>
611 642
612<p> 643<p>
613It is generally a good idea to start the virus scanner immediately. Add 644It 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. 645it to the <e>default</e> runlevel and then start the <c>clamd</c> service
646immediately. The service has two processes: freshclam keeps the virus definition
647database up to date while clamd is the actual anti-virus daemon. First you may
648want to set the paths of the logfiles so that it fits your needs.
649</p>
650
651<pre caption="Checking the location of the logfiles">
652# <i>vim /etc/clamd.conf</i>
653<comment>(Check the line "LogFile /var/log/clamd.log")</comment>
654# <i>vim /etc/freshclam.conf</i>
655<comment>(Check the line "UpdateLogFile /var/log/freshclam.log")</comment>
656# <i>vim /etc/conf.d/clamd</i>
657<comment>(Set "START_CLAMD=yes" and "START_FRESHCLAM=yes")</comment>
658</pre>
659
660<p>
661Now fire up the virus scanner.
615</p> 662</p>
616 663
617<pre caption="Add clamd to bootup and start it"> 664<pre caption="Add clamd to bootup and start it">
618# <i>rc-update add clamd default</i> 665# <i>rc-update add clamd default</i>
619# <i>/etc/init.d/clamd start</i> 666# <i>/etc/init.d/clamd start</i>
638 685
639AccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment> 686AccessLog /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> 687ErrorLog /var/log/cups/error_log <comment># doesn't really need changing either</comment>
641 688
642LogLevel debug <comment># only while isntalling and testing, should later be 689LogLevel debug <comment># only while isntalling and testing, should later be
643 # changed to 'info'</comment> 690 # changed to 'info'</comment>
644 691
645MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back, 692MaxClients 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, 693 # 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 694 # 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> 695 # I tried to configure a printer with the web interface. weird.</comment>
678<comment>(The following line is found near the end of the file. Uncomment it)</comment> 725<comment>(The following line is found near the end of the file. Uncomment it)</comment>
679application/octet-stream application/vnd.cups-raw 0 726application/octet-stream application/vnd.cups-raw 0
680</pre> 727</pre>
681 728
682<p> 729<p>
683Edit <path>/etc/cups/mime.convs</path> to uncomment some lines. 730Edit <path>/etc/cups/mime.types</path> to uncomment some lines.
684</p> 731</p>
685 732
686<pre caption="/etc/cups/mime.types"> 733<pre caption="/etc/cups/mime.types">
687<comment>(The following line is found near the end of the file. Uncomment it)</comment> 734<comment>(The following line is found near the end of the file. Uncomment it)</comment>
688application/octet-stream 735application/octet-stream
693</p> 740</p>
694 741
695<pre caption="Setting up the CUPS service" > 742<pre caption="Setting up the CUPS service" >
696<comment>(To start CUPS on boot)</comment> 743<comment>(To start CUPS on boot)</comment>
697# <i>rc-update add cupsd default</i> 744# <i>rc-update add cupsd default</i>
698<comment>(To start CUPS if it isn't started)</comment> 745<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> 746# <i>/etc/init.d/cupsd restart</i>
702</pre> 747</pre>
703 748
704</body> 749</body>
705</section> 750</section>
706<section> 751<section>
707<title>Installing a printer for and with CUPS</title> 752<title>Installing a printer for and with CUPS</title>
708<body> 753<body>
709 754
710<p> 755<p>
711First, go to <uri link="http://linuxprinting.org">LinuxPrinting.Org</uri> 756First, 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 757find 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 758click the link Printer Listings to the left. Select your printers manufacturer
714printers manufacturer and the model in the pulldown menu, eg HP and 759and the model in the pulldown menu, eg HP and DeskJet 930C. Click "Show". On
715DeskJet 930C. Click "Show". On the page coming up click the "recommended 760the page coming up click the "recommended driver" link after reading the
716driver" link after reading the various notes and information. Then fetch 761various 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 762again after reading the notes and introductions there. You may have to select
718introductions there. You may have to select your printers manufacturer 763your printers manufacturer and model again. Reading the <uri
719and model again. Reading the <uri link="http://www.linuxprinting.org/cups-doc.html">CUPS 764link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri>
720quickstart guide</uri> is also very helpful when working with CUPS. 765is also very helpful when working with CUPS.
721</p> 766</p>
722 767
723<p> 768<p>
724Now you have a PPD file for your printer to work with CUPS. Place it in 769Now 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 770<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was
950</pre> 995</pre>
951 996
952</body> 997</body>
953</section> 998</section>
954</chapter> 999</chapter>
1000
955<chapter> 1001<chapter>
956<title>Configuration of the Clients</title> 1002<title>Configuration of the Clients</title>
957<section> 1003<section>
958<title>Printer configuration of *nix based clients</title> 1004<title>Printer configuration of *nix based clients</title>
959<body> 1005<body>
960 1006
961<p> 1007<p>
962Despite the variation or distribution, the only thing needed is CUPS. 1008Despite the variation or distribution, the only thing needed is CUPS. Do the
963Do the equivalent on any other UNIX/Linux/BSD client. 1009equivalent on any other UNIX/Linux/BSD client.
964</p> 1010</p>
965 1011
966<pre caption="Configuring a Gentoo system."> 1012<pre caption="Configuring a Gentoo system">
967# <i>emerge cups</i> 1013# <i>emerge cups</i>
968# <i>/etc/init.d/cupsd start</i> 1014# <i>nano -w /etc/cups/client.conf</i>
969# <i>rc-update add cupsd default</i> 1015ServerName <i>PrintServer</i> <comment># your printserver name</comment>
970</pre> 1016</pre>
971 1017
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> 1018<p>
977 1019That should be it. Nothing else will be needed.
978<p> 1020</p>
979To print, use for example 1021
980</p> 1022<p>
1023If you use only one printer, it will be your default printer. If your print
1024server manages several printers, your administrator will have defined a default
1025printer on the server. If you want to define a different default printer for
1026yourself, use the <c>lpoptions</c> command.
1027</p>
1028
1029<pre caption="Setting your default printer">
1030<comment>(List available printers)</comment>
1031# <i>lpstat -a</i>
1032<comment>(Sample output, yours will differ)</comment>
1033HPDeskJet930C accepting requests since Jan 01 00:00
1034laser accepting requests since Jan 01 00:00
1035<comment>(Define HPDeskJet930C as your default printer)</comment>
1036# <i>lpoptions -d HPDeskJet930C</i>
1037</pre>
981 1038
982<pre caption="Printing in *nix"> 1039<pre caption="Printing in *nix">
1040<comment>(Specify the printer to be used)</comment>
983# <i>lpr -pHPDeskJet930C anything.txt</i> 1041# <i>lp -d HPDeskJet930C anything.txt</i>
984# <i>lpr -PHPDeskJet930C foobar.whatever.ps</i> 1042<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> 1043# <i>lp foobar.whatever.ps</i>
1005</pre> 1044</pre>
1006 1045
1007<p>
1008Some common observations when setting a default printer in this manner
1009include the following:
1010</p> 1046<p>
1011 1047Just point your web browser to <c>http://printserver:631</c> on the client if
1012<ul> 1048you want to manage your printers and their jobs with a nice web interface.
1013 <li> 1049Replace <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 1050your 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 1051different names.
1016 set a client's default remote printer. 1052</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 1053
1026</body> 1054</body>
1027</section> 1055</section>
1028<section> 1056<section>
1029<title>Mounting a Windows or Samba share in GNU/Linux</title> 1057<title>Mounting a Windows or Samba share in GNU/Linux</title>
1030<body> 1058<body>
1031 1059
1032<p> 1060<p>
1033Now is time to configure our kernel to support smbfs. Since I'm 1061Now 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 1062all 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. 1063options 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 1064of use. It is the author's opinion that kernel modules are a good thing and
1038whenever possible. 1065should be used whenever possible.
1039</p> 1066</p>
1040 1067
1041<pre caption="Relevant kernel options" > 1068<pre caption="Relevant kernel options" >
1042CONFIG_SMB_FS=m 1069CONFIG_SMB_FS=m
1043CONFIG_SMB_UNIX=y 1070CONFIG_SMB_UNIX=y
1087</p> 1114</p>
1088 1115
1089</body> 1116</body>
1090</section> 1117</section>
1091</chapter> 1118</chapter>
1119
1092<chapter> 1120<chapter>
1093<title>Final Notes</title> 1121<title>Final Notes</title>
1094<section> 1122<section>
1095<title>A Fond Farewell</title> 1123<title>A Fond Farewell</title>
1096<body> 1124<body>
1102</p> 1130</p>
1103 1131
1104</body> 1132</body>
1105</section> 1133</section>
1106</chapter> 1134</chapter>
1135
1107<chapter> 1136<chapter>
1108<title>Links and Resources</title> 1137<title>Links and Resources</title>
1109<section> 1138<section>
1110<title>Links</title> 1139<title>Links</title>
1111<body> 1140<body>

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

  ViewVC Help
Powered by ViewVC 1.1.20