/[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.36 Revision 1.37
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.36 2007/12/01 11:25:01 neysx Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.37 2007/12/01 11:30:40 neysx Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link="/doc/en/quick-samba-howto.xml"> 5<guide link="/doc/en/quick-samba-howto.xml">
6 6
7<title>Gentoo Samba3/CUPS/ClamAV HOWTO</title> 7<title>Gentoo Samba3/CUPS/ClamAV HOWTO</title>
8 8
9<author title="Author"> 9<author title="Author">
10 <mail>Andreas "daff" Ntaflos</mail><!--daff at dword dot org--> 10 <mail>Andreas "daff" Ntaflos</mail><!--daff at dword dot org-->
11</author> 11</author>
12<author title="Author"> 12<author title="Author">
13 <mail link="joshua@sungentoo.homeunix.com">Joshua Preston</mail> 13 <mail link="joshua@sungentoo.homeunix.com">Joshua Preston</mail>
14</author> 14</author>
15<author title="Editor"> 15<author title="Editor">
16 <mail link="nightmorph@gentoo.org">Joshua Saddler</mail> 16 <mail link="nightmorph@gentoo.org">Joshua Saddler</mail>
17</author> 17</author>
60</p> 60</p>
61 61
62<p> 62<p>
63This HOWTO will describe how to share files and printers between Windows PCs and 63This HOWTO will describe how to share files and printers between Windows PCs and
64*nix PCs. It will also demonstrate the use of the VFS (Virtual File System) 64*nix PCs. It will also demonstrate the use of the VFS (Virtual File System)
65feature of Samba to incorporate automatic virus protection. As a finale, it will 65feature of Samba to incorporate automatic virus protection. As a finale, it will
66show you how to mount and manipulate shares. 66show you how to mount and manipulate shares.
67</p> 67</p>
68 68
69<p> 69<p>
70There are a few topics that will be mentioned, but are out of the scope of this 70There are a few topics that will be mentioned, but are out of the scope of this
71HOWTO. These will be noted as they are presented. 71HOWTO. These will be noted as they are presented.
72</p> 72</p>
73 73
74<p> 74<p>
75This HOWTO is based on a compilation and merge of an excellent HOWTO provided in 75This HOWTO is based on a compilation and merge of an excellent HOWTO provided
76the <uri link="http://forums.gentoo.org">Gentoo forums</uri> by Andreas "daff" 76in the <uri link="http://forums.gentoo.org">Gentoo forums</uri> by Andreas
77Ntaflos and the collected knowledge of Joshua Preston. The link to this 77"daff" Ntaflos and the collected knowledge of Joshua Preston. The link to this
78discussion is provided below for your reference: 78discussion is provided below for your reference:
79</p> 79</p>
80 80
81<ul> 81<ul>
82 <li> 82 <li>
83 <uri link="http://forums.gentoo.org/viewtopic.php?t=110931">HOWTO 83 <uri link="http://forums.gentoo.org/viewtopic.php?t=110931">HOWTO
84 CUPS+Samba: printing from Windows &amp; Linux</uri> 84 CUPS+Samba: printing from Windows &amp; Linux</uri>
85 </li> 85 </li>
86</ul> 86</ul>
87 87
88</body> 88</body>
89</section> 89</section>
90<section> 90<section>
91<title>Before you use this guide</title> 91<title>Before you use this guide</title>
92<body> 92<body>
93 93
94<p> 94<p>
95There are a several other guides for setting up CUPS and/or Samba, please read 95There are a several other guides for setting up CUPS and/or Samba, please read
96them as well, as they may tell you things left out of this HOWTO (intentional or 96them as well, as they may tell you things left out of this HOWTO (intentional or
97otherwise). One such document is the very useful and well written <uri 97otherwise). One such document is the very useful and well written <uri
98link="/doc/en/printing-howto.xml">Gentoo Printing Guide</uri>, as configuration 98link="/doc/en/printing-howto.xml">Gentoo Printing Guide</uri>, as configuration
188 188
189<p> 189<p>
190Depending on the network topology and the specific requirements of the server, 190Depending on the network topology and the specific requirements of the server,
191the USE flags outlined below will define what to include or exclude from the 191the USE flags outlined below will define what to include or exclude from the
192emerging of Samba. 192emerging of Samba.
193</p> 193</p>
194 194
195<table> 195<table>
196<tr> 196<tr>
197 <th><b>USE flag</b></th> 197 <th><b>USE flag</b></th>
198 <th>Description</th> 198 <th>Description</th>
199</tr> 199</tr>
200<tr> 200<tr>
201 <th><b>kerberos</b></th> 201 <th><b>kerberos</b></th>
202 <ti> 202 <ti>
203 Include support for Kerberos. The server will need this if it is 203 Include support for Kerberos. The server will need this if it is intended
204 intended to join an existing domain or Active Directory. See the note 204 to join an existing domain or Active Directory. See the note below for more
205 below for more information. 205 information.
206 </ti> 206 </ti>
207</tr> 207</tr>
208<tr> 208<tr>
209 <th><b>acl</b></th> 209 <th><b>acl</b></th>
210 <ti> 210 <ti>
211 Enables Access Control Lists. The ACL support in Samba uses a patched 211 Enables Access Control Lists. The ACL support in Samba uses a patched
212 ext2/ext3, or SGI's XFS in order to function properly as it extends more 212 ext2/ext3, or SGI's XFS in order to function properly as it extends more
213 detailed access to files or directories; much more so than typical *nix 213 detailed access to files or directories; much more so than typical *nix
214 GID/UID schemas. 214 GID/UID schemas.
215 </ti> 215 </ti>
216</tr> 216</tr>
217<tr> 217<tr>
218 <th><b>cups</b></th> 218 <th><b>cups</b></th>
219 <ti> 219 <ti>
220 This enables support for the Common Unix Printing System. This provides an 220 This enables support for the Common Unix Printing System. This provides an
221 interface allowing local CUPS printers to be shared to other systems in the 221 interface allowing local CUPS printers to be shared to other systems in the
222 network. 222 network.
223 </ti> 223 </ti>
224</tr> 224</tr>
225<tr> 225<tr>
226 <th><b>ldap</b></th> 226 <th><b>ldap</b></th>
227 <ti> 227 <ti>
228 Enables the Lightweight Directory Access Protocol (LDAP). If Samba is 228 Enables the Lightweight Directory Access Protocol (LDAP). If Samba is
229 expected to use Active Directory, this option must be used. This would be 229 expected to use Active Directory, this option must be used. This would be
230 used in the event Samba needs to login to or provide login to a 230 used in the event Samba needs to login to or provide login to a
231 Domain/Active Directory Server. The kerberos USE flag is needed for proper 231 Domain/Active Directory Server. The kerberos USE flag is needed for proper
232 functioning of this option. 232 functioning of this option.
233 </ti> 233 </ti>
234</tr> 234</tr>
235<tr> 235<tr>
236 <th><b>pam</b></th> 236 <th><b>pam</b></th>
237 <ti> 237 <ti>
238 Include support for pluggable authentication modules (PAM). This provides 238 Include support for pluggable authentication modules (PAM). This provides
239 the ability to authenticate users on the Samba Server, which is required if 239 the ability to authenticate users on the Samba Server, which is required if
240 users have to login to your server. The kerberos USE flag is recommended 240 users have to login to your server. The kerberos USE flag is recommended
241 along with this option. 241 along with this option.
242 </ti> 242 </ti>
243</tr> 243</tr>
244<tr> 244<tr>
245 <th><b>readline</b></th> 245 <th><b>readline</b></th>
246 <ti> 246 <ti>
247 Link Samba against libreadline. This is highly recommended and should 247 Link Samba against libreadline. This is highly recommended and should
248 probably not be disabled. 248 probably not be disabled.
249 </ti> 249 </ti>
250</tr> 250</tr>
251<tr> 251<tr>
252 <th><b>python</b></th> 252 <th><b>python</b></th>
253 <ti> 253 <ti>
260 <ti> 260 <ti>
261 Provides on-access scanning of Samba shares with FRISK F-Prot Daemon, 261 Provides on-access scanning of Samba shares with FRISK F-Prot Daemon,
262 Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep (SAVI), 262 Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep (SAVI),
263 Symantec CarrierScan, and Trend Micro (VSAPI). 263 Symantec CarrierScan, and Trend Micro (VSAPI).
264 </ti> 264 </ti>
265</tr> 265</tr>
266</table> 266</table>
267 267
268<p> 268<p>
269A couple of things worth mentioning about the USE flags and different 269A couple of things worth mentioning about the USE flags and different
270Samba functions include: 270Samba functions include:
271</p> 271</p>
272 272
273<ul> 273<ul>
274 <li> 274 <li>
275 ACLs on ext2/3 are implemented through extended attributes (EAs). EA and 275 ACLs on ext2/3 are implemented through extended attributes (EAs). EA and
276 ACL kernel options for ext2 and/or ext3 will need to be enabled 276 ACL kernel options for ext2 and/or ext3 will need to be enabled (depending
277 (depending on which file system is being used - both can be enabled). 277 on which file system is being used - both can be enabled).
278 </li> 278 </li>
279 <li> 279 <li>
280 While Active Directory, ACL, and PDC functions are out of the intended 280 While Active Directory, ACL, and PDC functions are out of the intended
281 scope of this HOWTO, you may find these links as helpful to your cause: 281 scope of this HOWTO, you may find these links as helpful to your cause:
282 <ul> 282 <ul>
283 <li><uri>http://www.bluelightning.org/linux/samba_acl_howto/</uri></li> 283 <li><uri>http://www.bluelightning.org/linux/samba_acl_howto/</uri></li>
284 <li><uri>http://www.wlug.org.nz/HowtoSamba3AndActiveDirectory</uri></li> 284 <li><uri>http://www.wlug.org.nz/HowtoSamba3AndActiveDirectory</uri></li>
285 </ul> 285 </ul>
286 </li> 286 </li>
287</ul> 287</ul>
288 288
289</body> 289</body>
290</section> 290</section>
291</chapter> 291</chapter>
292 292
293<chapter> 293<chapter>
294<title>Server Software Installation</title> 294<title>Server Software Installation</title>
295<section> 295<section>
296<title>Emerging Samba</title> 296<title>Emerging Samba</title>
297<body> 297<body>
298 298
299<p> 299<p>
300First of all: be sure that all your hostnames resolve correctly. Either have a 300First of all: be sure that all your hostnames resolve correctly. Either have a
301working domain name system running on your network or appropriate entries in 301working domain name system running on your network or appropriate entries in
302your <path>/etc/hosts</path> file. <c>cupsaddsmb</c> often borks if hostnames 302your <path>/etc/hosts</path> file. <c>cupsaddsmb</c> often borks if hostnames
303don't point to the correct machines. 303don't point to the correct machines.
304</p> 304</p>
305 305
306<p> 306<p>
307Hopefully now you can make an assessment of what you'll actually need in order 307Hopefully now you can make an assessment of what you'll actually need in order
308to use Samba with your particular setup. The setup used for this HOWTO is: 308to use Samba with your particular setup. The setup used for this HOWTO is:
309</p> 309</p>
310 310
311<ul> 311<ul>
312 <li>oav</li> 312 <li>oav</li>
313 <li>cups</li> 313 <li>cups</li>
314 <li>readline</li> 314 <li>readline</li>
315 <li>pam</li> 315 <li>pam</li>
316</ul> 316</ul>
317 317
318<p> 318<p>
368<pre caption="Emerge hplip"> 368<pre caption="Emerge hplip">
369# <i>emerge net-print/hplip</i> 369# <i>emerge net-print/hplip</i>
370</pre> 370</pre>
371 371
372</body> 372</body>
373</section> 373</section>
374</chapter> 374</chapter>
375 375
376<chapter> 376<chapter>
377<title>Server Configuration</title> 377<title>Server Configuration</title>
378<section> 378<section>
379<title>Configuring Samba</title> 379<title>Configuring Samba</title>
380<body> 380<body>
381 381
382<p> 382<p>
383The main Samba configuration file is <path>/etc/samba/smb.conf</path>. It is 383The main Samba configuration file is <path>/etc/samba/smb.conf</path>. It is
384divided in sections indicated by [sectionname]. Comments are either 384divided in sections indicated by [sectionname]. Comments are either
385# or ;. A sample <path>smb.conf</path> is included below with comments and 385# or ;. A sample <path>smb.conf</path> is included below with comments and
386suggestions for modifications. If more details are required, see the man page 386suggestions for modifications. If more details are required, see the man page
387for <path>smb.conf</path>, the installed <path>smb.conf.example</path>, the 387for <path>smb.conf</path>, the installed <path>smb.conf.example</path>, the
388Samba Web site or any of the numerous Samba books available. 388Samba Web site or any of the numerous Samba books available.
389</p> 389</p>
390 390
391<pre caption="A Sample /etc/samba/smb.conf"> 391<pre caption="A Sample /etc/samba/smb.conf">
392[global] 392[global]
393<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment> 393<comment># Replace MYWORKGROUPNAME with your workgroup/domain</comment>
394workgroup = <comment>MYWORKGROUPNAME</comment> 394workgroup = <comment>MYWORKGROUPNAME</comment>
395<comment># Of course this has no REAL purpose other than letting 395<comment># Of course this has no REAL purpose other than letting
396# everyone knows it's not Windows! 396# everyone knows it's not Windows!
397# %v prints the version of Samba we are using.</comment> 397# %v prints the version of Samba we are using.</comment>
398server string = Samba Server %v 398server string = Samba Server %v
399<comment># We are going to use cups, so we are going to put it in here ;-)</comment> 399<comment># We are going to use cups, so we are going to put it in here ;-)</comment>
400printcap name = cups 400printcap name = cups
401printing = cups 401printing = cups
402load printers = yes 402load printers = yes
403<comment># We want a log file and we do not want it to get bigger than 50kb.</comment> 403<comment># We want a log file and we do not want it to get bigger than 50kb.</comment>
440# be the only printer admin)</comment> 440# be the only printer admin)</comment>
441write list = <i>root</i> 441write list = <i>root</i>
442 442
443<comment># Now we'll setup a printer to share, while the name is arbitrary 443<comment># Now we'll setup a printer to share, while the name is arbitrary
444# it should be consistent throughout Samba and CUPS!</comment> 444# it should be consistent throughout Samba and CUPS!</comment>
445[HPDeskJet930C] 445[HPDeskJet930C]
446comment = HP DeskJet 930C Network Printer 446comment = HP DeskJet 930C Network Printer
447printable = yes 447printable = yes
448path = /var/spool/samba 448path = /var/spool/samba
449public = yes 449public = yes
450guest ok = yes 450guest ok = yes
451<comment># Modify this to "username,root" if you don't want root to 451<comment># Modify this to "username,root" if you don't want root to
452# be the only printer admin)</comment> 452# be the only printer admin)</comment>
453printer admin = <i>root</i> 453printer admin = <i>root</i>
454 454
455<comment># Now we setup our printers share. This should be 455<comment># Now we setup our printers share. This should be
456# browseable, printable, public.</comment> 456# browseable, printable, public.</comment>
457[printers] 457[printers]
458comment = All Printers 458comment = All Printers
459browseable = no 459browseable = no
460printable = yes 460printable = yes
461writable = no 461writable = no
462public = yes 462public = yes
463guest ok = yes 463guest ok = yes
464path = /var/spool/samba 464path = /var/spool/samba
465<comment># Modify this to "username,root" if you don't want root to 465<comment># Modify this to "username,root" if you don't want root to
466# be the only printer admin)</comment> 466# be the only printer admin)</comment>
467printer admin = <i>root</i> 467printer admin = <i>root</i>
468 468
469<comment># We create a new share that we can read/write to from anywhere 469<comment># We create a new share that we can read/write to from anywhere
470# This is kind of like a public temp share, anyone can do what 470# This is kind of like a public temp share, anyone can do what
471# they want here.</comment> 471# they want here.</comment>
472[public] 472[public]
473comment = Public Files 473comment = Public Files
474browseable = yes 474browseable = yes
475public = yes 475public = yes
476create mode = 0766 476create mode = 0766
477guest ok = yes 477guest ok = yes
500</p> 500</p>
501 501
502<pre caption="Create the directories"> 502<pre caption="Create the directories">
503# <i>mkdir /etc/samba/printer</i> 503# <i>mkdir /etc/samba/printer</i>
504# <i>mkdir /var/spool/samba</i> 504# <i>mkdir /var/spool/samba</i>
505# <i>mkdir /home/samba/public</i> 505# <i>mkdir /home/samba/public</i>
506</pre> 506</pre>
507 507
508<p> 508<p>
509At least one Samba user is required in order to install the printer drivers and 509At least one Samba user is required in order to install the printer drivers and
510to allow users to connect to the printer. Users must exist in the system's 510to allow users to connect to the printer. Users must exist in the system's
511<path>/etc/passwd</path> file. 511<path>/etc/passwd</path> file.
512</p> 512</p>
513 513
514<pre caption="Creating the users"> 514<pre caption="Creating the users">
515# <i>smbpasswd -a root</i> 515# <i>smbpasswd -a root</i>
516 516
517<comment>(If another user is to be a printer admin)</comment> 517<comment>(If another user is to be a printer admin)</comment>
518# <i>smbpasswd -a username</i> 518# <i>smbpasswd -a username</i>
519</pre> 519</pre>
520 520
521<p> 521<p>
522The Samba passwords need not be the same as the system passwords 522The Samba passwords need not be the same as the system passwords
523in <path>/etc/passwd</path>. 523in <path>/etc/passwd</path>.
524</p> 524</p>
525 525
526<p> 526<p>
527You will also need to update <path>/etc/nsswitch.conf</path> so that Windows 527You will also need to update <path>/etc/nsswitch.conf</path> so that Windows
528systems can be found easily using NetBIOS: 528systems can be found easily using NetBIOS:
529</p> 529</p>
530 530
531<pre caption="Editing /etc/nsswitch.conf"> 531<pre caption="Editing /etc/nsswitch.conf">
532# <i>nano -w /etc/nsswitch.conf</i> 532# <i>nano -w /etc/nsswitch.conf</i>
533<comment>(Edit the hosts: line)</comment> 533<comment>(Edit the hosts: line)</comment>
534hosts: files dns <i>wins</i> 534hosts: files dns <i>wins</i>
535</pre> 535</pre>
536 536
537</body> 537</body>
643 643
644<p> 644<p>
645This is a little more complicated. CUPS' main config file is 645This is a little more complicated. CUPS' main config file is
646<path>/etc/cups/cupsd.conf</path>. It's structure is similar to Apache's 646<path>/etc/cups/cupsd.conf</path>. It's structure is similar to Apache's
647<path>httpd.conf</path> file, so many you may find it familiar. Outlined in the 647<path>httpd.conf</path> file, so many you may find it familiar. Outlined in the
648example are the directives that need to be changed: 648example are the directives that need to be changed:
649</p> 649</p>
650 650
651<pre caption="/etc/cups/cupsd.conf"> 651<pre caption="/etc/cups/cupsd.conf">
652ServerName <i>PrintServer</i> <comment># your printserver name</comment> 652ServerName <i>PrintServer</i> <comment># your printserver name</comment>
653ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, e.g. you</comment> 653ServerAdmin <i>root@PrintServer</i> <comment># the person for printer-related hate-mail, e.g. you</comment>
654 654
655AccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment> 655AccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment>
656ErrorLog /var/log/cups/error_log <comment># doesn't really need changing either</comment> 656ErrorLog /var/log/cups/error_log <comment># doesn't really need changing either</comment>
657 657
658LogLevel debug <comment># only while isntalling and testing, should later be 658LogLevel debug <comment># only while installing and testing, should later be
659 # changed to 'info'</comment> 659 # changed to 'info'</comment>
660 660
661MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back, 661MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back,
662 # there seemed to be a bug in CUPS' controlling of the web interface, 662 # there seemed to be a bug in CUPS' controlling of the web interface,
663 # making CUPS think a denial of service attack was in progress when 663 # making CUPS think a denial of service attack was in progress when
664 # I tried to configure a printer with the web interface. weird.</comment> 664 # I tried to configure a printer with the web interface. weird.</comment>
665 665
666BrowseAddress @IF(<i>eth0</i>) <comment># Change this to your internal net interface</comment> 666BrowseAddress @IF(<i>eth0</i>) <comment># Change this to your internal net interface</comment>
667 667
668&lt;Location /&gt; 668&lt;Location /&gt;
669Order Deny,Allow 669Order Deny,Allow
670Deny From All 670Deny From All
671Allow From <i>192.168.1.*</i> <comment># the addresses of your internel network 671Allow From <i>192.168.1.*</i> <comment># the addresses of your internel network
672 # e.g. 192.168.1.* will allow connections from any host on 672 # e.g. 192.168.1.* will allow connections from any host on
673 # the 192.168.1.0 network. change to whatever suits you</comment> 673 # the 192.168.1.0 network. change to whatever suits you</comment>
674&lt;/Location&gt; 674&lt;/Location&gt;
675 675
676&lt;Location /admin&gt; 676&lt;Location /admin&gt;
677AuthType Basic 677AuthType Basic
678AuthClass System 678AuthClass System
679Allow From <i>192.168.1.*</i> <comment># same as above, allow any host on the 679Allow From <i>192.168.1.*</i> <comment># same as above, allow any host on the
680 # 192.168.1.0 network to connect and do 680 # 192.168.1.0 network to connect and do
681 # administrative tasks after authenticating</comment> 681 # administrative tasks after authenticating</comment>
682Order Deny,Allow 682Order Deny,Allow
683Deny From All 683Deny From All
684&lt;/Location&gt; 684&lt;/Location&gt;
685</pre> 685</pre>
686 686
687<p> 687<p>
688Edit <path>/etc/cups/mime.convs</path> to uncomment some lines. 688Edit <path>/etc/cups/mime.convs</path> to uncomment some lines. The changes to
689The changes to <path>mime.convs</path> and <path>mime.types</path> are 689<path>mime.convs</path> and <path>mime.types</path> are needed to make CUPS
690needed to make CUPS print Microsoft Office document files. 690print Microsoft Office document files.
691</p> 691</p>
692 692
693<pre caption="/etc/cups/mime.convs"> 693<pre caption="/etc/cups/mime.convs">
694<comment>(The following line is found near the end of the file. Uncomment it)</comment> 694<comment>(The following line is found near the end of the file. Uncomment it)</comment>
695application/octet-stream application/vnd.cups-raw 0 695application/octet-stream application/vnd.cups-raw 0
696</pre> 696</pre>
697 697
698<p> 698<p>
699Edit <path>/etc/cups/mime.types</path> to uncomment some lines. 699Edit <path>/etc/cups/mime.types</path> to uncomment some lines.
700</p> 700</p>
701 701
702<pre caption="/etc/cups/mime.types"> 702<pre caption="/etc/cups/mime.types">
703<comment>(The following line is found near the end of the file. Uncomment it)</comment> 703<comment>(The following line is found near the end of the file. Uncomment it)</comment>
704application/octet-stream 704application/octet-stream
705</pre> 705</pre>
706 706
707<p> 707<p>
708CUPS needs to be started on boot, and started immediately. 708CUPS needs to be started on boot, and started immediately.
709</p> 709</p>
710 710
711<pre caption="Setting up the CUPS service" > 711<pre caption="Setting up the CUPS service" >
712<comment>(To start CUPS on boot)</comment> 712<comment>(To start CUPS on boot)</comment>
713# <i>rc-update add cupsd default</i> 713# <i>rc-update add cupsd default</i>
714<comment>(To start or restart CUPS now)</comment> 714<comment>(To start or restart CUPS now)</comment>
715# <i>/etc/init.d/cupsd restart</i> 715# <i>/etc/init.d/cupsd restart</i>
716</pre> 716</pre>
717 717
718</body> 718</body>
719</section> 719</section>
720<section> 720<section>
721<title>Installing a printer for and with CUPS</title> 721<title>Installing a printer for and with CUPS</title>
722<body> 722<body>
723 723
754whatever device you are using for your printer. 754whatever device you are using for your printer.
755</p> 755</p>
756 756
757<p> 757<p>
758You should now be able to access the printer from the web interface and be able 758You should now be able to access the printer from the web interface and be able
759to print a test page. 759to print a test page.
760</p> 760</p>
761 761
762</body> 762</body>
763</section> 763</section>
764<section> 764<section>
765<title>Installing the Windows printer drivers</title> 765<title>Installing the Windows printer drivers</title>
766<body> 766<body>
767 767
768<p> 768<p>
769Now that the printer should be working it is time to install the drivers for the 769Now that the printer should be working it is time to install the drivers for
770Windows clients to work. Samba 2.2 introduced this functionality. Browsing to 770the Windows clients to work. Samba 2.2 introduced this functionality. Browsing
771the print server in the Network Neighbourhood, right-clicking on the 771to the print server in the Network Neighbourhood, right-clicking on the
772printershare and selecting "connect" downloads the appropriate drivers 772printershare and selecting "connect" downloads the appropriate drivers
773automagically to the connecting client, avoiding the hassle of manually 773automagically to the connecting client, avoiding the hassle of manually
774installing printer drivers locally. 774installing printer drivers locally.
775</p> 775</p>
776 776
777<p> 777<p>
778There are two sets of printer drivers for this. First, the Adobe PS drivers 778There are two sets of printer drivers for this. First, the Adobe PS drivers
779which can be obtained from <uri 779which can be obtained from <uri
780link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript 780link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript
781printer drivers). Second, there are the CUPS PS drivers, to be obtained by 781printer drivers). Second, there are the CUPS PS drivers, to be obtained by
782emerging <c>net-print/cups-windows</c>. Note that it may still be marked ~arch, 782emerging <c>net-print/cups-windows</c>. Note that it may still be marked ~arch,
783so you may need to add it to <path>/etc/portage/package.keywords</path>. There 783so you may need to add it to <path>/etc/portage/package.keywords</path>. There
784doesn't seem to be a difference between the functionality of the two, but the 784doesn't seem to be a difference between the functionality of the two, but the
785Adobe PS drivers need to be extracted on a Windows System since it's a Windows 785Adobe PS drivers need to be extracted on a Windows System since it's a Windows
786binary. Also the whole procedure of finding and copying the correct files is a 786binary. Also the whole procedure of finding and copying the correct files is a

Legend:
Removed from v.1.36  
changed lines
  Added in v.1.37

  ViewVC Help
Powered by ViewVC 1.1.20