| 1 |
nightmorph 07/06/06 23:23:35 |
| 2 |
|
| 3 |
Modified: quick-samba-howto.xml |
| 4 |
Log: |
| 5 |
proper guidexml coding style, linewrapping, typo fixes for correct english, and spacing fixes. no content change. just lots of little stuff all throughout the doc. |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.29 xml/htdocs/doc/en/quick-samba-howto.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml?rev=1.29&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml?rev=1.29&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml?r1=1.28&r2=1.29 |
| 13 |
|
| 14 |
Index: quick-samba-howto.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v |
| 17 |
retrieving revision 1.28 |
| 18 |
retrieving revision 1.29 |
| 19 |
diff -u -r1.28 -r1.29 |
| 20 |
--- quick-samba-howto.xml 6 Jun 2007 22:42:25 -0000 1.28 |
| 21 |
+++ quick-samba-howto.xml 6 Jun 2007 23:23:35 -0000 1.29 |
| 22 |
@@ -1,5 +1,5 @@ |
| 23 |
<?xml version='1.0' encoding='UTF-8'?> |
| 24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.28 2007/06/06 22:42:25 nightmorph Exp $ --> |
| 25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.29 2007/06/06 23:23:35 nightmorph Exp $ --> |
| 26 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 27 |
<guide link="/doc/en/quick-samba-howto.xml"> |
| 28 |
<title>Gentoo Samba3/CUPS/ClamAV HOWTO</title> |
| 29 |
@@ -11,9 +11,9 @@ |
| 30 |
</author> |
| 31 |
|
| 32 |
<abstract> |
| 33 |
-Setup, install and configure a Samba Server under Gentoo that shares |
| 34 |
-files, printers without the need to install drivers and provides |
| 35 |
-automatic virus scanning. |
| 36 |
+Setup, install and configure a Samba Server under Gentoo that shares files, |
| 37 |
+printers without the need to install drivers and provides automatic virus |
| 38 |
+scanning. |
| 39 |
</abstract> |
| 40 |
|
| 41 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 42 |
@@ -30,48 +30,46 @@ |
| 43 |
<body> |
| 44 |
|
| 45 |
<p> |
| 46 |
-This HOWTO is designed to help you move a network from many different |
| 47 |
-clients speaking different languages, to many different machines that |
| 48 |
-speak a common language. The ultimate goal is to help differing |
| 49 |
-architectures and technologies, come together in a productive, |
| 50 |
-happily coexisting environment. |
| 51 |
+This HOWTO is designed to help you move a network from many different clients |
| 52 |
+speaking different languages, to many different machines that speak a common |
| 53 |
+language. The ultimate goal is to help differing architectures and technologies, |
| 54 |
+come together in a productive, happily coexisting environment. |
| 55 |
</p> |
| 56 |
|
| 57 |
<p> |
| 58 |
-Following the directions outlined in this HOWTO should give you an |
| 59 |
-excellent step towards a peaceful cohabitation between Windows, and |
| 60 |
-virtually all known variations of *nix. |
| 61 |
+Following the directions outlined in this HOWTO should give you an excellent |
| 62 |
+step towards a peaceful cohabitation between Windows, and virtually all known |
| 63 |
+variations of *nix. |
| 64 |
</p> |
| 65 |
|
| 66 |
<p> |
| 67 |
-This HOWTO originally started not as a HOWTO, but as a FAQ. It was |
| 68 |
-intended to explore the functionality and power of the Gentoo system, |
| 69 |
-portage and the flexibility of USE flags. Like so many other projects, |
| 70 |
-it was quickly discovered what was missing in the Gentoo realm: there |
| 71 |
-weren't any Samba HOWTO's catered for Gentoo users. These users are |
| 72 |
-more demanding than most; they require performance, flexibility and |
| 73 |
-customization. This does not however imply that this HOWTO was not |
| 74 |
-intended for other distributions; rather that it was designed to work |
| 75 |
-with a highly customized version of Samba. |
| 76 |
+This HOWTO originally started not as a HOWTO, but as a FAQ. It was intended to |
| 77 |
+explore the functionality and power of the Gentoo system, portage and the |
| 78 |
+flexibility of USE flags. Like so many other projects, it was quickly discovered |
| 79 |
+what was missing in the Gentoo realm: there weren't any Samba HOWTO's catered |
| 80 |
+for Gentoo users. These users are more demanding than most; they require |
| 81 |
+performance, flexibility and customization. This does not however imply that |
| 82 |
+this HOWTO was not intended for other distributions; rather that it was designed |
| 83 |
+to work with a highly customized version of Samba. |
| 84 |
</p> |
| 85 |
|
| 86 |
<p> |
| 87 |
-This HOWTO will describe how to share files and printers between Windows |
| 88 |
-PCs and *nix PCs. It will also demonstrate the use of the VFS (Virtual |
| 89 |
-File System) feature of Samba to incorporate automatic virus protection. |
| 90 |
-As a finale, it will show you how to mount and manipulate shares. |
| 91 |
+This HOWTO will describe how to share files and printers between Windows PCs and |
| 92 |
+*nix PCs. It will also demonstrate the use of the VFS (Virtual File System) |
| 93 |
+feature of Samba to incorporate automatic virus protection. As a finale, it will |
| 94 |
+show you how to mount and manipulate shares. |
| 95 |
</p> |
| 96 |
|
| 97 |
<p> |
| 98 |
-There are a few topics that will be mentioned, but are out of the |
| 99 |
-scope of this HOWTO. These will be noted as they are presented. |
| 100 |
+There are a few topics that will be mentioned, but are out of the scope of this |
| 101 |
+HOWTO. These will be noted as they are presented. |
| 102 |
</p> |
| 103 |
|
| 104 |
<p> |
| 105 |
-This HOWTO is based on a compilation and merge of an excellent HOWTO |
| 106 |
-provided in the <uri link="http://forums.gentoo.org">Gentoo forums</uri> |
| 107 |
-by Andreas "daff" Ntaflos and the collected knowledge of Joshua Preston. |
| 108 |
-The link to this discussion is provided below for your reference: |
| 109 |
+This HOWTO is based on a compilation and merge of an excellent HOWTO provided in |
| 110 |
+the <uri link="http://forums.gentoo.org">Gentoo forums</uri> by Andreas "daff" |
| 111 |
+Ntaflos and the collected knowledge of Joshua Preston. The link to this |
| 112 |
+discussion is provided below for your reference: |
| 113 |
</p> |
| 114 |
|
| 115 |
<ul> |
| 116 |
@@ -89,8 +87,8 @@ |
| 117 |
|
| 118 |
<p> |
| 119 |
There are a several other guides for setting up CUPS and/or Samba, please read |
| 120 |
-them as well, as they may tell you things left out of this HOWTO (intentional |
| 121 |
-or otherwise). One such document is the very useful and well written <uri |
| 122 |
+them as well, as they may tell you things left out of this HOWTO (intentional or |
| 123 |
+otherwise). One such document is the very useful and well written <uri |
| 124 |
link="/doc/en/printing-howto.xml">Gentoo Printing Guide</uri>, as configuration |
| 125 |
issues and specific printer setup is not discussed here. |
| 126 |
</p> |
| 127 |
@@ -102,8 +100,8 @@ |
| 128 |
<body> |
| 129 |
|
| 130 |
<p> |
| 131 |
-After presenting the various USE flags, the following list will outline |
| 132 |
-all of the topics covered as they are presented: |
| 133 |
+After presenting the various USE flags, the following list will outline all of |
| 134 |
+the topics covered as they are presented: |
| 135 |
</p> |
| 136 |
|
| 137 |
<ul> |
| 138 |
@@ -155,11 +153,11 @@ |
| 139 |
</ul> |
| 140 |
|
| 141 |
<p> |
| 142 |
-The main package we use here is net-fs/samba, however, you will need |
| 143 |
-a kernel with smbfs support enabled in order to mount a samba or windows |
| 144 |
-share from another computer. CUPS will be emerged if it is not already. |
| 145 |
-app-antivirus/clamav will be used also, but others should be easily adapted |
| 146 |
-to work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning |
| 147 |
+The main package we use here is net-fs/samba, however, you will need a kernel |
| 148 |
+with smbfs support enabled in order to mount a samba or windows share from |
| 149 |
+another computer. CUPS will be emerged if it is not already. |
| 150 |
+app-antivirus/clamav will be used also, but others should be easily adapted to |
| 151 |
+work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning |
| 152 |
technologies, such as Sophos, FProt, Fsav, Trend, Icap, Nai, ... |
| 153 |
</p> |
| 154 |
|
| 155 |
@@ -183,9 +181,9 @@ |
| 156 |
</pre> |
| 157 |
|
| 158 |
<p> |
| 159 |
-Depending on the network topology and the specific requirements of |
| 160 |
-the server, the USE flags outlined below will define what to include or |
| 161 |
-exclude from the emerging of Samba. |
| 162 |
+Depending on the network topology and the specific requirements of the server, |
| 163 |
+the USE flags outlined below will define what to include or exclude from the |
| 164 |
+emerging of Samba. |
| 165 |
</p> |
| 166 |
|
| 167 |
<table> |
| 168 |
@@ -213,50 +211,50 @@ |
| 169 |
<tr> |
| 170 |
<th><b>cups</b></th> |
| 171 |
<ti> |
| 172 |
- This enables support for the Common Unix Printing System. This |
| 173 |
- provides an interface allowing local CUPS printers to be shared to |
| 174 |
- other systems in the network. |
| 175 |
+ This enables support for the Common Unix Printing System. This provides an |
| 176 |
+ interface allowing local CUPS printers to be shared to other systems in the |
| 177 |
+ network. |
| 178 |
</ti> |
| 179 |
</tr> |
| 180 |
<tr> |
| 181 |
<th><b>ldap</b></th> |
| 182 |
<ti> |
| 183 |
- Enables the Lightweight Directory Access Protocol (LDAP). If Samba is |
| 184 |
- expected to use Active Directory, this option must be used. This would |
| 185 |
- be used in the event Samba needs to login to or provide login to |
| 186 |
- a Domain/Active Directory Server. The kerberos USE flag is needed for |
| 187 |
- proper functioning of this option. |
| 188 |
+ Enables the Lightweight Directory Access Protocol (LDAP). If Samba is |
| 189 |
+ expected to use Active Directory, this option must be used. This would be |
| 190 |
+ used in the event Samba needs to login to or provide login to a |
| 191 |
+ Domain/Active Directory Server. The kerberos USE flag is needed for proper |
| 192 |
+ functioning of this option. |
| 193 |
</ti> |
| 194 |
</tr> |
| 195 |
<tr> |
| 196 |
<th><b>pam</b></th> |
| 197 |
<ti> |
| 198 |
- Include support for pluggable authentication modules (PAM). This |
| 199 |
- provides the ability to authenticate users on the Samba Server, which is |
| 200 |
- required if users have to login to your server. The kerberos USE flag |
| 201 |
- is recommended along with this option. |
| 202 |
+ Include support for pluggable authentication modules (PAM). This provides |
| 203 |
+ the ability to authenticate users on the Samba Server, which is required if |
| 204 |
+ users have to login to your server. The kerberos USE flag is recommended |
| 205 |
+ along with this option. |
| 206 |
</ti> |
| 207 |
</tr> |
| 208 |
<tr> |
| 209 |
<th><b>readline</b></th> |
| 210 |
<ti> |
| 211 |
- Link Samba against libreadline. This is highly recommended and should |
| 212 |
- probably not be disabled |
| 213 |
+ Link Samba against libreadline. This is highly recommended and should |
| 214 |
+ probably not be disabled. |
| 215 |
</ti> |
| 216 |
</tr> |
| 217 |
<tr> |
| 218 |
<th><b>python</b></th> |
| 219 |
<ti> |
| 220 |
- Python bindings API. Provides an API that will allow Python to |
| 221 |
- interface with Samba. |
| 222 |
+ Python bindings API. Provides an API that will allow Python to interface |
| 223 |
+ with Samba. |
| 224 |
</ti> |
| 225 |
</tr> |
| 226 |
<tr> |
| 227 |
<th><b>oav</b></th> |
| 228 |
<ti> |
| 229 |
- Provides on-access scanning of Samba shares with FRISK F-Prot |
| 230 |
- Daemon, Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep |
| 231 |
- (SAVI), Symantec CarrierScan, and Trend Micro (VSAPI). |
| 232 |
+ Provides on-access scanning of Samba shares with FRISK F-Prot Daemon, |
| 233 |
+ Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep (SAVI), |
| 234 |
+ Symantec CarrierScan, and Trend Micro (VSAPI). |
| 235 |
</ti> |
| 236 |
</tr> |
| 237 |
</table> |
| 238 |
@@ -293,17 +291,15 @@ |
| 239 |
<body> |
| 240 |
|
| 241 |
<p> |
| 242 |
-First of all: be sure that all your hostnames resolve correctly. |
| 243 |
-Either have a working domain name system running on your network |
| 244 |
-or appropriate entries in your <path>/etc/hosts</path> file. |
| 245 |
-<c>cupsaddsmb</c> often borks if hostnames don't point to the correct |
| 246 |
-machines. |
| 247 |
+First of all: be sure that all your hostnames resolve correctly. Either have a |
| 248 |
+working domain name system running on your network or appropriate entries in |
| 249 |
+your <path>/etc/hosts</path> file. <c>cupsaddsmb</c> often borks if hostnames |
| 250 |
+don't point to the correct machines. |
| 251 |
</p> |
| 252 |
|
| 253 |
<p> |
| 254 |
-Hopefully now you can make an assessment of what you'll actually need in |
| 255 |
-order to use Samba with your particular setup. The setup used for this |
| 256 |
-HOWTO is: |
| 257 |
+Hopefully now you can make an assessment of what you'll actually need in order |
| 258 |
+to use Samba with your particular setup. The setup used for this HOWTO is: |
| 259 |
</p> |
| 260 |
|
| 261 |
<ul> |
| 262 |
@@ -314,8 +310,8 @@ |
| 263 |
</ul> |
| 264 |
|
| 265 |
<p> |
| 266 |
-To optimize performance, size and the time of the build, the |
| 267 |
-USE flags are specifically included or excluded. |
| 268 |
+To optimize performance, size and the time of the build, the USE flags are |
| 269 |
+specifically included or excluded. |
| 270 |
</p> |
| 271 |
|
| 272 |
<pre caption="Emerge Samba"> |
| 273 |
@@ -324,7 +320,7 @@ |
| 274 |
</pre> |
| 275 |
|
| 276 |
<note> |
| 277 |
-The following archs will need to add <e>~</e> to their <e>KEYWORDS</e>: x86, |
| 278 |
+The following arches will need to add <e>~</e> to their <e>KEYWORDS</e>: x86, |
| 279 |
ppc, sparc, hppa, ia64 and alpha |
| 280 |
</note> |
| 281 |
|
| 282 |
@@ -339,9 +335,9 @@ |
| 283 |
<body> |
| 284 |
|
| 285 |
<p> |
| 286 |
-Because the <e>oav</e> USE flag only provides an interface to allow on access |
| 287 |
-virus scanning, the actual virus scanner must be emerged. The scanner |
| 288 |
-used in this HOWTO is ClamAV. |
| 289 |
+Because the <e>oav</e> USE flag only provides an interface to allow on access |
| 290 |
+virus scanning, the actual virus scanner must be emerged. The scanner used in |
| 291 |
+this HOWTO is ClamAV. |
| 292 |
</p> |
| 293 |
|
| 294 |
<pre caption="Emerge Clamav"> |
| 295 |
@@ -383,13 +379,12 @@ |
| 296 |
<body> |
| 297 |
|
| 298 |
<p> |
| 299 |
-The main Samba configuration file is <path>/etc/samba/smb.conf</path>. |
| 300 |
-It is divided in sections indicated by [sectionname]. Comments are either |
| 301 |
-# or ;. A sample <path>smb.conf</path> is included below with comments and |
| 302 |
-suggestions for modifications. If more details are required, see the |
| 303 |
-man page for <path>smb.conf</path>, the installed |
| 304 |
-<path>smb.conf.example</path>, the Samba Web site or any of the |
| 305 |
-numerous Samba books available. |
| 306 |
+The main Samba configuration file is <path>/etc/samba/smb.conf</path>. It is |
| 307 |
+divided in sections indicated by [sectionname]. Comments are either |
| 308 |
+# or ;. A sample <path>smb.conf</path> is included below with comments and |
| 309 |
+suggestions for modifications. If more details are required, see the man page |
| 310 |
+for <path>smb.conf</path>, the installed <path>smb.conf.example</path>, the |
| 311 |
+Samba Web site or any of the numerous Samba books available. |
| 312 |
</p> |
| 313 |
|
| 314 |
<pre caption="A Sample /etc/samba/smb.conf"> |
| 315 |
@@ -484,15 +479,14 @@ |
| 316 |
</pre> |
| 317 |
|
| 318 |
<warn> |
| 319 |
-If you like to use Samba's guest account to do anything concerning |
| 320 |
-printing from Windows clients: don't set <c>guest only = yes</c> in |
| 321 |
-the <c>[global]</c> section. The guest account seems to cause |
| 322 |
-problems when running <c>cupsaddsmb</c> sometimes when trying to |
| 323 |
-connect from Windows machines. See below, too, when we talk about |
| 324 |
-<c>cupsaddsmb</c> and the problems that can arise. Use a dedicated |
| 325 |
-printer user, like <c>printeruser</c> or <c>printer</c> or |
| 326 |
-<c>printme</c> or whatever. It doesn't hurt and it will certainly |
| 327 |
-protect you from a lot of problems. |
| 328 |
+If you like to use Samba's guest account to do anything concerning printing from |
| 329 |
+Windows clients: don't set <c>guest only = yes</c> in the <c>[global]</c> |
| 330 |
+section. The guest account seems to cause problems when running |
| 331 |
+<c>cupsaddsmb</c> sometimes when trying to connect from Windows machines. See |
| 332 |
+below, too, when we talk about <c>cupsaddsmb</c> and the problems that can |
| 333 |
+arise. Use a dedicated printer user, like <c>printeruser</c> or <c>printer</c> |
| 334 |
+or <c>printme</c> or whatever. It doesn't hurt and it will certainly protect you |
| 335 |
+from a lot of problems. |
| 336 |
</warn> |
| 337 |
|
| 338 |
<warn> |
| 339 |
@@ -501,8 +495,8 @@ |
| 340 |
</warn> |
| 341 |
|
| 342 |
<p> |
| 343 |
-Now create the directories required for the minimum configuration of |
| 344 |
-Samba to share the installed printer throughout the network. |
| 345 |
+Now create the directories required for the minimum configuration of Samba to |
| 346 |
+share the installed printer throughout the network. |
| 347 |
</p> |
| 348 |
|
| 349 |
<pre caption="Create the directories"> |
| 350 |
@@ -512,9 +506,9 @@ |
| 351 |
</pre> |
| 352 |
|
| 353 |
<p> |
| 354 |
-At least one Samba user is required in order to install the printer |
| 355 |
-drivers and to allow users to connect to the printer. Users must |
| 356 |
-exist in the system's <path>/etc/passwd</path> file. |
| 357 |
+At least one Samba user is required in order to install the printer drivers and |
| 358 |
+to allow users to connect to the printer. Users must exist in the system's |
| 359 |
+<path>/etc/passwd</path> file. |
| 360 |
</p> |
| 361 |
|
| 362 |
<pre caption="Creating the users"> |
| 363 |
@@ -547,9 +541,9 @@ |
| 364 |
<body> |
| 365 |
|
| 366 |
<p> |
| 367 |
-The configuration file specified to be used in <path>smb.conf</path> is |
| 368 |
-<path>/etc/samba/vscan-clamav.conf</path>. While these options are set |
| 369 |
-to the defaults, the infected file action may need to be changed. |
| 370 |
+The configuration file specified to be used in <path>smb.conf</path> is |
| 371 |
+<path>/etc/samba/vscan-clamav.conf</path>. While these options are set to the |
| 372 |
+defaults, the infected file action may need to be changed. |
| 373 |
</p> |
| 374 |
|
| 375 |
<pre caption="/etc/samba/vscan-clamav.conf"> |
| 376 |
@@ -616,11 +610,11 @@ |
| 377 |
</pre> |
| 378 |
|
| 379 |
<p> |
| 380 |
-It is generally a good idea to start the virus scanner immediately. Add |
| 381 |
-it to the <e>default</e> runlevel and then start the <c>clamd</c> service |
| 382 |
-immediately. The service has two processes: freshclam keeps the virus definition |
| 383 |
-database up to date while clamd is the actual anti-virus daemon. First you may |
| 384 |
-want to set the paths of the logfiles so that it fits your needs. |
| 385 |
+It is generally a good idea to start the virus scanner immediately. Add it to |
| 386 |
+the <e>default</e> runlevel and then start the <c>clamd</c> service immediately. |
| 387 |
+The service has two processes: freshclam keeps the virus definition database up |
| 388 |
+to date while clamd is the actual anti-virus daemon. First you may want to set |
| 389 |
+the paths of the logfiles so that it fits your needs. |
| 390 |
</p> |
| 391 |
|
| 392 |
<pre caption="Checking the location of the logfiles"> |
| 393 |
@@ -648,10 +642,10 @@ |
| 394 |
<body> |
| 395 |
|
| 396 |
<p> |
| 397 |
-This is a little more complicated. CUPS' main config file is |
| 398 |
-<path>/etc/cups/cupsd.conf</path>. It's structure is similar to Apache's |
| 399 |
-<path>httpd.conf</path> file, so many you may find it familiar. Outlined |
| 400 |
-in the example are the directives that need to be changed: |
| 401 |
+This is a little more complicated. CUPS' main config file is |
| 402 |
+<path>/etc/cups/cupsd.conf</path>. It's structure is similar to Apache's |
| 403 |
+<path>httpd.conf</path> file, so many you may find it familiar. Outlined in the |
| 404 |
+example are the directives that need to be changed: |
| 405 |
</p> |
| 406 |
|
| 407 |
<pre caption="/etc/cups/cupsd.conf"> |
| 408 |
@@ -732,19 +726,19 @@ |
| 409 |
find and download the correct PPD file for your printer and CUPS. To do so, |
| 410 |
click the link Printer Listings to the left. Select your printers manufacturer |
| 411 |
and the model in the pulldown menu, e.g. HP and DeskJet 930C. Click "Show". On |
| 412 |
-the page coming up click the "recommended driver" link after reading the |
| 413 |
-various notes and information. Then fetch the PPD file from the next page, |
| 414 |
-again after reading the notes and introductions there. You may have to select |
| 415 |
-your printers manufacturer and model again. Reading the <uri |
| 416 |
-link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri> |
| 417 |
-is also very helpful when working with CUPS. |
| 418 |
+the page coming up click the "recommended driver" link after reading the various |
| 419 |
+notes and information. Then fetch the PPD file from the next page, again after |
| 420 |
+reading the notes and introductions there. You may have to select your printers |
| 421 |
+manufacturer and model again. Reading the <uri |
| 422 |
+link="http://www.linuxprinting.org/cups-doc.html">CUPS quickstart guide</uri> is |
| 423 |
+also very helpful when working with CUPS. |
| 424 |
</p> |
| 425 |
|
| 426 |
<p> |
| 427 |
-Now you have a PPD file for your printer to work with CUPS. Place it in |
| 428 |
-<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was |
| 429 |
-named <path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer. |
| 430 |
-This can be done via the CUPS web interface or via command line. The web |
| 431 |
+Now you have a PPD file for your printer to work with CUPS. Place it in |
| 432 |
+<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was named |
| 433 |
+<path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer. |
| 434 |
+This can be done via the CUPS web interface or via command line. The web |
| 435 |
interface is found at <path>http://PrintServer:631</path> once CUPS is running. |
| 436 |
</p> |
| 437 |
|
| 438 |
@@ -754,16 +748,15 @@ |
| 439 |
</pre> |
| 440 |
|
| 441 |
<p> |
| 442 |
-Remember to adjust to what you have. Be sure to have the name |
| 443 |
-(<c>-p</c> argument) right (the name you set above during the Samba |
| 444 |
-configuration!) and to put in the correct <c>usb:/dev/usb/blah</c>, |
| 445 |
-<c>parallel:/dev/blah</c> or whatever device you are using for your |
| 446 |
-printer. |
| 447 |
+Remember to adjust to what you have. Be sure to have the name (<c>-p</c> |
| 448 |
+argument) right (the name you set above during the Samba configuration!) and to |
| 449 |
+put in the correct <c>usb:/dev/usb/blah</c>, <c>parallel:/dev/blah</c> or |
| 450 |
+whatever device you are using for your printer. |
| 451 |
</p> |
| 452 |
|
| 453 |
<p> |
| 454 |
-You should now be able to access the printer from the web interface |
| 455 |
-and be able to print a test page. |
| 456 |
+You should now be able to access the printer from the web interface and be able |
| 457 |
+to print a test page. |
| 458 |
</p> |
| 459 |
|
| 460 |
</body> |
| 461 |
@@ -773,12 +766,12 @@ |
| 462 |
<body> |
| 463 |
|
| 464 |
<p> |
| 465 |
-Now that the printer should be working it is time to install the drivers |
| 466 |
-for the Windows clients to work. Samba 2.2 introduced this functionality. |
| 467 |
-Browsing to the print server in the Network Neighbourhood, right-clicking |
| 468 |
-on the printershare and selecting "connect" downloads the appropriate |
| 469 |
-drivers automagically to the connecting client, avoiding the hassle of |
| 470 |
-manually installing printer drivers locally. |
| 471 |
+Now that the printer should be working it is time to install the drivers for the |
| 472 |
+Windows clients to work. Samba 2.2 introduced this functionality. Browsing to |
| 473 |
+the print server in the Network Neighbourhood, right-clicking on the |
| 474 |
+printershare and selecting "connect" downloads the appropriate drivers |
| 475 |
+automagically to the connecting client, avoiding the hassle of manually |
| 476 |
+installing printer drivers locally. |
| 477 |
</p> |
| 478 |
|
| 479 |
<p> |
| 480 |
@@ -819,16 +812,16 @@ |
| 481 |
|
| 482 |
<warn> |
| 483 |
The script <c>cups-samba.install</c> may not work for all *nixes (i.e. FreeBSD) |
| 484 |
-because almost everything which is not part of the base system is |
| 485 |
-installed somewhere under the prefix <path>/usr/local/</path>. This |
| 486 |
-seems not to be the case for most things you install under GNU/Linux. |
| 487 |
-However, if your CUPS installation is somewhere other than |
| 488 |
-<path>/usr/share/cups/</path> see the example below. |
| 489 |
+because almost everything which is not part of the base system is installed |
| 490 |
+somewhere under the prefix <path>/usr/local/</path>. This seems not to be the |
| 491 |
+case for most things you install under GNU/Linux. However, if your CUPS |
| 492 |
+installation is somewhere other than <path>/usr/share/cups/</path> see the |
| 493 |
+example below. |
| 494 |
</warn> |
| 495 |
|
| 496 |
<p> |
| 497 |
-Suppose your CUPS installation resides under |
| 498 |
-<path>/usr/local/share/cups/</path>, and you want to install the drivers there. |
| 499 |
+Suppose your CUPS installation resides under |
| 500 |
+<path>/usr/local/share/cups/</path>, and you want to install the drivers there. |
| 501 |
Do the following: |
| 502 |
</p> |
| 503 |
|
| 504 |
@@ -867,33 +860,32 @@ |
| 505 |
<ul> |
| 506 |
<li> |
| 507 |
The hostname given as a parameter for <c>-h</c> and <c>-H</c> |
| 508 |
- (<c>PrintServer</c>) often does not resolve correctly and doesn't |
| 509 |
- identify the print server for CUPS/Samba interaction. If an error |
| 510 |
- like: <b>Warning: No PPD file for printer "CUPS_PRINTER_NAME" - |
| 511 |
- skipping!</b> occurs, the first thing you should do is substitute |
| 512 |
- <c>PrintServer</c> with <c>localhost</c> and try it again. |
| 513 |
+ (<c>PrintServer</c>) often does not resolve correctly and doesn't identify |
| 514 |
+ the print server for CUPS/Samba interaction. If an error like: <b>Warning: |
| 515 |
+ No PPD file for printer "CUPS_PRINTER_NAME" - skipping!</b> occurs, the |
| 516 |
+ first thing you should do is substitute <c>PrintServer</c> with |
| 517 |
+ <c>localhost</c> and try it again. |
| 518 |
</li> |
| 519 |
<li> |
| 520 |
- The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message |
| 521 |
- is quite common, but can be triggered by many problems. It's unfortunately |
| 522 |
- not very helpful. One thing to try is to temporarily set <c>security = |
| 523 |
- user</c> in your <path>smb.conf</path>. After/if the installation completes |
| 524 |
- successfully, you should set it back to share, or whatever it was set to |
| 525 |
+ The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message |
| 526 |
+ is quite common, but can be triggered by many problems. It's unfortunately |
| 527 |
+ not very helpful. One thing to try is to temporarily set <c>security = |
| 528 |
+ user</c> in your <path>smb.conf</path>. After/if the installation completes |
| 529 |
+ successfully, you should set it back to share, or whatever it was set to |
| 530 |
before. |
| 531 |
</li> |
| 532 |
</ul> |
| 533 |
|
| 534 |
<p> |
| 535 |
-This should install the correct driver directory structure under |
| 536 |
-<path>/etc/samba/printer</path>. That would be |
| 537 |
-<path>/etc/samba/printer/W32X86/2/</path>. The files contained should |
| 538 |
-be the 3 driver files and the PPD file, renamed to YourPrinterName.ppd |
| 539 |
-(the name which you gave the printer when installing it (see above). |
| 540 |
+This should install the correct driver directory structure under |
| 541 |
+<path>/etc/samba/printer</path>. That would be |
| 542 |
+<path>/etc/samba/printer/W32X86/2/</path>. The files contained should be the 3 |
| 543 |
+driver files and the PPD file, renamed to <path>YourPrinterName.ppd</path> (the |
| 544 |
+name which you gave the printer when installing it (see above). |
| 545 |
</p> |
| 546 |
|
| 547 |
<p> |
| 548 |
-Pending no errors or other complications, your drivers are now |
| 549 |
-installed. |
| 550 |
+Pending no errors or other complications, your drivers are now installed. |
| 551 |
</p> |
| 552 |
|
| 553 |
</body> |
| 554 |
@@ -921,8 +913,8 @@ |
| 555 |
|
| 556 |
<p> |
| 557 |
We will want to test our configuration file to ensure that it is formatted |
| 558 |
-properly and all of our options have at least the correct syntax. To do |
| 559 |
-this we run <c>testparm</c>. |
| 560 |
+properly and all of our options have at least the correct syntax. To do this we |
| 561 |
+run <c>testparm</c>. |
| 562 |
</p> |
| 563 |
|
| 564 |
<pre caption="Running the testparm"> |
| 565 |
@@ -962,9 +954,8 @@ |
| 566 |
<body> |
| 567 |
|
| 568 |
<p> |
| 569 |
-It would probably be prudent to check our logs at this time also. |
| 570 |
-We will also want to take a peak at our Samba shares using |
| 571 |
-<c>smbclient</c>. |
| 572 |
+It would probably be prudent to check our logs at this time also. We will also |
| 573 |
+want to take a peak at our Samba shares using <c>smbclient</c>. |
| 574 |
</p> |
| 575 |
|
| 576 |
<pre caption="Checking the shares with smbclient"> |
| 577 |
@@ -984,7 +975,7 @@ |
| 578 |
<body> |
| 579 |
|
| 580 |
<p> |
| 581 |
-Despite the variation or distribution, the only thing needed is CUPS. Do the |
| 582 |
+Despite the variation or distribution, the only thing needed is CUPS. Do the |
| 583 |
equivalent on any other UNIX/Linux/BSD client. |
| 584 |
</p> |
| 585 |
|
| 586 |
@@ -1025,8 +1016,8 @@ |
| 587 |
<p> |
| 588 |
Just point your web browser to <c>http://printserver:631</c> on the client if |
| 589 |
you want to manage your printers and their jobs with a nice web interface. |
| 590 |
-Replace <c>printserver</c> with the name of the <e>machine</e> that acts as |
| 591 |
-your print server, not the name you gave to the cups print server if you used |
| 592 |
+Replace <c>printserver</c> with the name of the <e>machine</e> that acts as your |
| 593 |
+print server, not the name you gave to the cups print server if you used |
| 594 |
different names. |
| 595 |
</p> |
| 596 |
|
| 597 |
@@ -1039,8 +1030,8 @@ |
| 598 |
<p> |
| 599 |
Now is time to configure our kernel to support smbfs. Since I'm assumming we've |
| 600 |
all compiled at least one kernel, we'll need to make sure we have all the right |
| 601 |
-options selected in our kernel. For simplicity sake, make it a module for ease |
| 602 |
-of use. It is the author's opinion that kernel modules are a good thing and |
| 603 |
+options selected in our kernel. For simplicity's sake, make it a module for ease |
| 604 |
+of use. It is the author's opinion that kernel modules are a good thing and |
| 605 |
should be used whenever possible. |
| 606 |
</p> |
| 607 |
|
| 608 |
@@ -1058,8 +1049,8 @@ |
| 609 |
</pre> |
| 610 |
|
| 611 |
<p> |
| 612 |
-Once the modules is loaded, mounting a Windows or Samba share is |
| 613 |
-possible. Use <c>mount</c> to accomplish this, as detailed below: |
| 614 |
+Once the module is loaded, mounting a Windows or Samba share is possible. Use |
| 615 |
+<c>mount</c> to accomplish this, as detailed below: |
| 616 |
</p> |
| 617 |
|
| 618 |
<pre caption="Mounting a Windows/Samba share"> |
| 619 |
@@ -1074,8 +1065,7 @@ |
| 620 |
</pre> |
| 621 |
|
| 622 |
<p> |
| 623 |
-After you mount the share, you would access it as if it were a local |
| 624 |
-drive. |
| 625 |
+After you mount the share, you would access it as if it were a local drive. |
| 626 |
</p> |
| 627 |
|
| 628 |
</body> |
| 629 |
@@ -1085,11 +1075,10 @@ |
| 630 |
<body> |
| 631 |
|
| 632 |
<p> |
| 633 |
-That's just a bit of point-and-click. Browse to |
| 634 |
-<path>\\PrintServer</path> and right click on the printer |
| 635 |
-(HPDeskJet930C) and click connect. This will download the drivers to |
| 636 |
-the Windows client and now every application (such as Word or Acrobat) |
| 637 |
-will offer HPDeskJet930C as an available printer to print to. :-) |
| 638 |
+That's just a bit of point-and-click. Browse to <path>\\PrintServer</path> and |
| 639 |
+right click on the printer (HPDeskJet930C) and click connect. This will download |
| 640 |
+the drivers to the Windows client and now every application (such as Word or |
| 641 |
+Acrobat) will offer HPDeskJet930C as an available printer to print to. :-) |
| 642 |
</p> |
| 643 |
|
| 644 |
</body> |
| 645 |
@@ -1103,9 +1092,8 @@ |
| 646 |
<body> |
| 647 |
|
| 648 |
<p> |
| 649 |
-Well that should be it. You should now have a successful printing enviroment |
| 650 |
-that is friendly to both Windows and *nix as well as a fully virus-free working |
| 651 |
-share! |
| 652 |
+That should be it. You should now have a successful printing enviroment that is |
| 653 |
+friendly to both Windows and *nix as well as a fully virus-free working share! |
| 654 |
</p> |
| 655 |
|
| 656 |
</body> |
| 657 |
@@ -1133,11 +1121,10 @@ |
| 658 |
<li><uri link="http://linuxprinting.org/">LinuxPrinting dot Org</uri></li> |
| 659 |
<li> |
| 660 |
<uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/">Kurt |
| 661 |
- Pfeifle's Samba Print HOWTO</uri> ( |
| 662 |
- This HOWTO really covers <e>ANYTHING</e> and <e>EVERYTHING</e> |
| 663 |
- I've written here, plus a LOT more concerning CUPS and Samba, and |
| 664 |
- generally printing support on networks. A really interesting read, |
| 665 |
- with lots and lots of details) |
| 666 |
+ Pfeifle's Samba Print HOWTO</uri> ( This HOWTO really covers <e>ANYTHING</e> |
| 667 |
+ and <e>EVERYTHING</e> I've written here, plus a LOT more concerning CUPS and |
| 668 |
+ Samba, and generally printing support on networks. A really interesting |
| 669 |
+ read, with lots and lots of details.) |
| 670 |
</li> |
| 671 |
<li><uri link="http://www.freebsddiary.org/cups.php">FreeBSD Diary's CUPS Topic</uri></li> |
| 672 |
</ul> |
| 673 |
@@ -1149,11 +1136,11 @@ |
| 674 |
<body> |
| 675 |
|
| 676 |
<p> |
| 677 |
-See <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37">this |
| 678 |
-page</uri> from Kurt Pfeifle's "Printing Support in Samba 3.0" |
| 679 |
-manual. Lots of useful tips there! Be sure to look this one up |
| 680 |
-first, before posting questions and problems! Maybe the solution |
| 681 |
-you're looking for is right there. |
| 682 |
+See <uri |
| 683 |
+link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37">this |
| 684 |
+page</uri> from Kurt Pfeifle's "Printing Support in Samba 3.0" manual. Lots of |
| 685 |
+useful tips there! Be sure to look this one up first, before posting questions |
| 686 |
+and problems! Maybe the solution you're looking for is right there. |
| 687 |
</p> |
| 688 |
|
| 689 |
</body> |
| 690 |
|
| 691 |
|
| 692 |
|
| 693 |
-- |
| 694 |
gentoo-doc-cvs@g.o mailing list |
Archives