nightmorph 07/06/06 23:23:35 Modified: quick-samba-howto.xml Log: 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.
Revision Changes Path 1.29 xml/htdocs/doc/en/quick-samba-howto.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml?rev=1.29&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml?rev=1.29&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml?r1=1.28&r2=1.29 Index: quick-samba-howto.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v retrieving revision 1.28 retrieving revision 1.29 diff -u -r1.28 -r1.29 --- quick-samba-howto.xml 6 Jun 2007 22:42:25 -0000 1.28 +++ quick-samba-howto.xml 6 Jun 2007 23:23:35 -0000 1.29 @@ -1,5 +1,5 @@ <?xml version='1.0' encoding='UTF-8'?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.28 2007/06/06 22:42:25 nightmorph Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.29 2007/06/06 23:23:35 nightmorph Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> <guide link="/doc/en/quick-samba-howto.xml"> <title>Gentoo Samba3/CUPS/ClamAV HOWTO</title> @@ -11,9 +11,9 @@ </author> <abstract> -Setup, install and configure a Samba Server under Gentoo that shares -files, printers without the need to install drivers and provides -automatic virus scanning. +Setup, install and configure a Samba Server under Gentoo that shares files, +printers without the need to install drivers and provides automatic virus +scanning. </abstract> <!-- The content of this document is licensed under the CC-BY-SA license --> @@ -30,48 +30,46 @@ <body> <p> -This HOWTO is designed to help you move a network from many different -clients speaking different languages, to many different machines that -speak a common language. The ultimate goal is to help differing -architectures and technologies, come together in a productive, -happily coexisting environment. +This HOWTO is designed to help you move a network from many different clients +speaking different languages, to many different machines that speak a common +language. The ultimate goal is to help differing architectures and technologies, +come together in a productive, happily coexisting environment. </p> <p> -Following the directions outlined in this HOWTO should give you an -excellent step towards a peaceful cohabitation between Windows, and -virtually all known variations of *nix. +Following the directions outlined in this HOWTO should give you an excellent +step towards a peaceful cohabitation between Windows, and virtually all known +variations of *nix. </p> <p> -This HOWTO originally started not as a HOWTO, but as a FAQ. It was -intended to explore the functionality and power of the Gentoo system, -portage and the flexibility of USE flags. Like so many other projects, -it was quickly discovered what was missing in the Gentoo realm: there -weren't any Samba HOWTO's catered for Gentoo users. These users are -more demanding than most; they require performance, flexibility and -customization. This does not however imply that this HOWTO was not -intended for other distributions; rather that it was designed to work -with a highly customized version of Samba. +This HOWTO originally started not as a HOWTO, but as a FAQ. It was intended to +explore the functionality and power of the Gentoo system, portage and the +flexibility of USE flags. Like so many other projects, it was quickly discovered +what was missing in the Gentoo realm: there weren't any Samba HOWTO's catered +for Gentoo users. These users are more demanding than most; they require +performance, flexibility and customization. This does not however imply that +this HOWTO was not intended for other distributions; rather that it was designed +to work with a highly customized version of Samba. </p> <p> -This HOWTO will describe how to share files and printers between Windows -PCs and *nix PCs. It will also demonstrate the use of the VFS (Virtual -File System) feature of Samba to incorporate automatic virus protection. -As a finale, it will show you how to mount and manipulate shares. +This HOWTO will describe how to share files and printers between Windows PCs and +*nix PCs. It will also demonstrate the use of the VFS (Virtual File System) +feature of Samba to incorporate automatic virus protection. As a finale, it will +show you how to mount and manipulate shares. </p> <p> -There are a few topics that will be mentioned, but are out of the -scope of this HOWTO. These will be noted as they are presented. +There are a few topics that will be mentioned, but are out of the scope of this +HOWTO. These will be noted as they are presented. </p> <p> -This HOWTO is based on a compilation and merge of an excellent HOWTO -provided in the <uri link="http://forums.gentoo.org";>Gentoo forums</uri> -by Andreas "daff" Ntaflos and the collected knowledge of Joshua Preston. -The link to this discussion is provided below for your reference: +This HOWTO is based on a compilation and merge of an excellent HOWTO provided in +the <uri link="http://forums.gentoo.org";>Gentoo forums</uri> by Andreas "daff" +Ntaflos and the collected knowledge of Joshua Preston. The link to this +discussion is provided below for your reference: </p> <ul> @@ -89,8 +87,8 @@ <p> There are a several other guides for setting up CUPS and/or Samba, please read -them as well, as they may tell you things left out of this HOWTO (intentional -or otherwise). One such document is the very useful and well written <uri +them as well, as they may tell you things left out of this HOWTO (intentional or +otherwise). One such document is the very useful and well written <uri link="/doc/en/printing-howto.xml">Gentoo Printing Guide</uri>, as configuration issues and specific printer setup is not discussed here. </p> @@ -102,8 +100,8 @@ <body> <p> -After presenting the various USE flags, the following list will outline -all of the topics covered as they are presented: +After presenting the various USE flags, the following list will outline all of +the topics covered as they are presented: </p> <ul> @@ -155,11 +153,11 @@ </ul> <p> -The main package we use here is net-fs/samba, however, you will need -a kernel with smbfs support enabled in order to mount a samba or windows -share from another computer. CUPS will be emerged if it is not already. -app-antivirus/clamav will be used also, but others should be easily adapted -to work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning +The main package we use here is net-fs/samba, however, you will need a kernel +with smbfs support enabled in order to mount a samba or windows share from +another computer. CUPS will be emerged if it is not already. +app-antivirus/clamav will be used also, but others should be easily adapted to +work with Samba. Gentoo's samba ebuild supports all kinds of virus scanning technologies, such as Sophos, FProt, Fsav, Trend, Icap, Nai, ... </p> @@ -183,9 +181,9 @@ </pre> <p> -Depending on the network topology and the specific requirements of -the server, the USE flags outlined below will define what to include or -exclude from the emerging of Samba. +Depending on the network topology and the specific requirements of the server, +the USE flags outlined below will define what to include or exclude from the +emerging of Samba. </p> <table> @@ -213,50 +211,50 @@ <tr> <th><b>cups</b></th> <ti> - This enables support for the Common Unix Printing System. This - provides an interface allowing local CUPS printers to be shared to - other systems in the network. + This enables support for the Common Unix Printing System. This provides an + interface allowing local CUPS printers to be shared to other systems in the + network. </ti> </tr> <tr> <th><b>ldap</b></th> <ti> - Enables the Lightweight Directory Access Protocol (LDAP). If Samba is - expected to use Active Directory, this option must be used. This would - be used in the event Samba needs to login to or provide login to - a Domain/Active Directory Server. The kerberos USE flag is needed for - proper functioning of this option. + Enables the Lightweight Directory Access Protocol (LDAP). If Samba is + expected to use Active Directory, this option must be used. This would be + used in the event Samba needs to login to or provide login to a + Domain/Active Directory Server. The kerberos USE flag is needed for proper + functioning of this option. </ti> </tr> <tr> <th><b>pam</b></th> <ti> - Include support for pluggable authentication modules (PAM). This - provides the ability to authenticate users on the Samba Server, which is - required if users have to login to your server. The kerberos USE flag - is recommended along with this option. + Include support for pluggable authentication modules (PAM). This provides + the ability to authenticate users on the Samba Server, which is required if + users have to login to your server. The kerberos USE flag is recommended + along with this option. </ti> </tr> <tr> <th><b>readline</b></th> <ti> - Link Samba against libreadline. This is highly recommended and should - probably not be disabled + Link Samba against libreadline. This is highly recommended and should + probably not be disabled. </ti> </tr> <tr> <th><b>python</b></th> <ti> - Python bindings API. Provides an API that will allow Python to - interface with Samba. + Python bindings API. Provides an API that will allow Python to interface + with Samba. </ti> </tr> <tr> <th><b>oav</b></th> <ti> - Provides on-access scanning of Samba shares with FRISK F-Prot - Daemon, Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep - (SAVI), Symantec CarrierScan, and Trend Micro (VSAPI). + Provides on-access scanning of Samba shares with FRISK F-Prot Daemon, + Kaspersky AntiVirus, OpenAntiVirus.org ScannerDaemon, Sophos Sweep (SAVI), + Symantec CarrierScan, and Trend Micro (VSAPI). </ti> </tr> </table> @@ -293,17 +291,15 @@ <body> <p> -First of all: be sure that all your hostnames resolve correctly. -Either have a working domain name system running on your network -or appropriate entries in your <path>/etc/hosts</path> file. -<c>cupsaddsmb</c> often borks if hostnames don't point to the correct -machines. +First of all: be sure that all your hostnames resolve correctly. Either have a +working domain name system running on your network or appropriate entries in +your <path>/etc/hosts</path> file. <c>cupsaddsmb</c> often borks if hostnames +don't point to the correct machines. </p> <p> -Hopefully now you can make an assessment of what you'll actually need in -order to use Samba with your particular setup. The setup used for this -HOWTO is: +Hopefully now you can make an assessment of what you'll actually need in order +to use Samba with your particular setup. The setup used for this HOWTO is: </p> <ul> @@ -314,8 +310,8 @@ </ul> <p> -To optimize performance, size and the time of the build, the -USE flags are specifically included or excluded. +To optimize performance, size and the time of the build, the USE flags are +specifically included or excluded. </p> <pre caption="Emerge Samba"> @@ -324,7 +320,7 @@ </pre> <note> -The following archs will need to add <e>~</e> to their <e>KEYWORDS</e>: x86, +The following arches will need to add <e>~</e> to their <e>KEYWORDS</e>: x86, ppc, sparc, hppa, ia64 and alpha </note> @@ -339,9 +335,9 @@ <body> <p> -Because the <e>oav</e> USE flag only provides an interface to allow on access -virus scanning, the actual virus scanner must be emerged. The scanner -used in this HOWTO is ClamAV. +Because the <e>oav</e> USE flag only provides an interface to allow on access +virus scanning, the actual virus scanner must be emerged. The scanner used in +this HOWTO is ClamAV. </p> <pre caption="Emerge Clamav"> @@ -383,13 +379,12 @@ <body> <p> -The main Samba configuration file is <path>/etc/samba/smb.conf</path>. -It is divided in sections indicated by [sectionname]. Comments are either -# or ;. A sample <path>smb.conf</path> is included below with comments and -suggestions for modifications. If more details are required, see the -man page for <path>smb.conf</path>, the installed -<path>smb.conf.example</path>, the Samba Web site or any of the -numerous Samba books available. +The main Samba configuration file is <path>/etc/samba/smb.conf</path>. It is +divided in sections indicated by [sectionname]. Comments are either +# or ;. A sample <path>smb.conf</path> is included below with comments and +suggestions for modifications. If more details are required, see the man page +for <path>smb.conf</path>, the installed <path>smb.conf.example</path>, the +Samba Web site or any of the numerous Samba books available. </p> <pre caption="A Sample /etc/samba/smb.conf"> @@ -484,15 +479,14 @@ </pre> <warn> -If you like to use Samba's guest account to do anything concerning -printing from Windows clients: don't set <c>guest only = yes</c> in -the <c>[global]</c> section. The guest account seems to cause -problems when running <c>cupsaddsmb</c> sometimes when trying to -connect from Windows machines. See below, too, when we talk about -<c>cupsaddsmb</c> and the problems that can arise. Use a dedicated -printer user, like <c>printeruser</c> or <c>printer</c> or -<c>printme</c> or whatever. It doesn't hurt and it will certainly -protect you from a lot of problems. +If you like to use Samba's guest account to do anything concerning printing from +Windows clients: don't set <c>guest only = yes</c> in the <c>[global]</c> +section. The guest account seems to cause problems when running +<c>cupsaddsmb</c> sometimes when trying to connect from Windows machines. See +below, too, when we talk about <c>cupsaddsmb</c> and the problems that can +arise. Use a dedicated printer user, like <c>printeruser</c> or <c>printer</c> +or <c>printme</c> or whatever. It doesn't hurt and it will certainly protect you +from a lot of problems. </warn> <warn> @@ -501,8 +495,8 @@ </warn> <p> -Now create the directories required for the minimum configuration of -Samba to share the installed printer throughout the network. +Now create the directories required for the minimum configuration of Samba to +share the installed printer throughout the network. </p> <pre caption="Create the directories"> @@ -512,9 +506,9 @@ </pre> <p> -At least one Samba user is required in order to install the printer -drivers and to allow users to connect to the printer. Users must -exist in the system's <path>/etc/passwd</path> file. +At least one Samba user is required in order to install the printer drivers and +to allow users to connect to the printer. Users must exist in the system's +<path>/etc/passwd</path> file. </p> <pre caption="Creating the users"> @@ -547,9 +541,9 @@ <body> <p> -The configuration file specified to be used in <path>smb.conf</path> is -<path>/etc/samba/vscan-clamav.conf</path>. While these options are set -to the defaults, the infected file action may need to be changed. +The configuration file specified to be used in <path>smb.conf</path> is +<path>/etc/samba/vscan-clamav.conf</path>. While these options are set to the +defaults, the infected file action may need to be changed. </p> <pre caption="/etc/samba/vscan-clamav.conf"> @@ -616,11 +610,11 @@ </pre> <p> -It is generally a good idea to start the virus scanner immediately. Add -it to the <e>default</e> runlevel and then start the <c>clamd</c> service -immediately. The service has two processes: freshclam keeps the virus definition -database up to date while clamd is the actual anti-virus daemon. First you may -want to set the paths of the logfiles so that it fits your needs. +It is generally a good idea to start the virus scanner immediately. Add it to +the <e>default</e> runlevel and then start the <c>clamd</c> service immediately. +The service has two processes: freshclam keeps the virus definition database up +to date while clamd is the actual anti-virus daemon. First you may want to set +the paths of the logfiles so that it fits your needs. </p> <pre caption="Checking the location of the logfiles"> @@ -648,10 +642,10 @@ <body> <p> -This is a little more complicated. CUPS' main config file is -<path>/etc/cups/cupsd.conf</path>. It's structure is similar to Apache's -<path>httpd.conf</path> file, so many you may find it familiar. Outlined -in the example are the directives that need to be changed: +This is a little more complicated. CUPS' main config file is +<path>/etc/cups/cupsd.conf</path>. It's structure is similar to Apache's +<path>httpd.conf</path> file, so many you may find it familiar. Outlined in the +example are the directives that need to be changed: </p> <pre caption="/etc/cups/cupsd.conf"> @@ -732,19 +726,19 @@ find and download the correct PPD file for your printer and CUPS. To do so, click the link Printer Listings to the left. Select your printers manufacturer and the model in the pulldown menu, e.g. HP and DeskJet 930C. Click "Show". On -the page coming up click the "recommended driver" link after reading the -various notes and information. Then fetch the PPD file from the next page, -again after reading the notes and introductions there. You may have to select -your printers manufacturer and model again. Reading the <uri -link="http://www.linuxprinting.org/cups-doc.html";>CUPS quickstart guide</uri> -is also very helpful when working with CUPS. +the page coming up click the "recommended driver" link after reading the various +notes and information. Then fetch the PPD file from the next page, again after +reading the notes and introductions there. You may have to select your printers +manufacturer and model again. Reading the <uri +link="http://www.linuxprinting.org/cups-doc.html";>CUPS quickstart guide</uri> is +also very helpful when working with CUPS. </p> <p> -Now you have a PPD file for your printer to work with CUPS. Place it in -<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was -named <path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer. -This can be done via the CUPS web interface or via command line. The web +Now you have a PPD file for your printer to work with CUPS. Place it in +<path>/usr/share/cups/model</path>. The PPD for the HP DeskJet 930C was named +<path>HP-DeskJet_930C-hpijs.ppd</path>. You should now install the printer. +This can be done via the CUPS web interface or via command line. The web interface is found at <path>http://PrintServer:631</path> once CUPS is running. </p> @@ -754,16 +748,15 @@ </pre> <p> -Remember to adjust to what you have. Be sure to have the name -(<c>-p</c> argument) right (the name you set above during the Samba -configuration!) and to put in the correct <c>usb:/dev/usb/blah</c>, -<c>parallel:/dev/blah</c> or whatever device you are using for your -printer. +Remember to adjust to what you have. Be sure to have the name (<c>-p</c> +argument) right (the name you set above during the Samba configuration!) and to +put in the correct <c>usb:/dev/usb/blah</c>, <c>parallel:/dev/blah</c> or +whatever device you are using for your printer. </p> <p> -You should now be able to access the printer from the web interface -and be able to print a test page. +You should now be able to access the printer from the web interface and be able +to print a test page. </p> </body> @@ -773,12 +766,12 @@ <body> <p> -Now that the printer should be working it is time to install the drivers -for the Windows clients to work. Samba 2.2 introduced this functionality. -Browsing to the print server in the Network Neighbourhood, right-clicking -on the printershare and selecting "connect" downloads the appropriate -drivers automagically to the connecting client, avoiding the hassle of -manually installing printer drivers locally. +Now that the printer should be working it is time to install the drivers for the +Windows clients to work. Samba 2.2 introduced this functionality. Browsing to +the print server in the Network Neighbourhood, right-clicking on the +printershare and selecting "connect" downloads the appropriate drivers +automagically to the connecting client, avoiding the hassle of manually +installing printer drivers locally. </p> <p> @@ -819,16 +812,16 @@ <warn> The script <c>cups-samba.install</c> may not work for all *nixes (i.e. FreeBSD) -because almost everything which is not part of the base system is -installed somewhere under the prefix <path>/usr/local/</path>. This -seems not to be the case for most things you install under GNU/Linux. -However, if your CUPS installation is somewhere other than -<path>/usr/share/cups/</path> see the example below. +because almost everything which is not part of the base system is installed +somewhere under the prefix <path>/usr/local/</path>. This seems not to be the +case for most things you install under GNU/Linux. However, if your CUPS +installation is somewhere other than <path>/usr/share/cups/</path> see the +example below. </warn> <p> -Suppose your CUPS installation resides under -<path>/usr/local/share/cups/</path>, and you want to install the drivers there. +Suppose your CUPS installation resides under +<path>/usr/local/share/cups/</path>, and you want to install the drivers there. Do the following: </p> @@ -867,33 +860,32 @@ <ul> <li> The hostname given as a parameter for <c>-h</c> and <c>-H</c> - (<c>PrintServer</c>) often does not resolve correctly and doesn't - identify the print server for CUPS/Samba interaction. If an error - like: <b>Warning: No PPD file for printer "CUPS_PRINTER_NAME" - - skipping!</b> occurs, the first thing you should do is substitute - <c>PrintServer</c> with <c>localhost</c> and try it again. + (<c>PrintServer</c>) often does not resolve correctly and doesn't identify + the print server for CUPS/Samba interaction. If an error like: <b>Warning: + No PPD file for printer "CUPS_PRINTER_NAME" - skipping!</b> occurs, the + first thing you should do is substitute <c>PrintServer</c> with + <c>localhost</c> and try it again. </li> <li> - The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message - is quite common, but can be triggered by many problems. It's unfortunately - not very helpful. One thing to try is to temporarily set <c>security = - user</c> in your <path>smb.conf</path>. After/if the installation completes - successfully, you should set it back to share, or whatever it was set to + The command fails with an <b>NT_STATUS_UNSUCCESSFUL</b>. This error message + is quite common, but can be triggered by many problems. It's unfortunately + not very helpful. One thing to try is to temporarily set <c>security = + user</c> in your <path>smb.conf</path>. After/if the installation completes + successfully, you should set it back to share, or whatever it was set to before. </li> </ul> <p> -This should install the correct driver directory structure under -<path>/etc/samba/printer</path>. That would be -<path>/etc/samba/printer/W32X86/2/</path>. The files contained should -be the 3 driver files and the PPD file, renamed to YourPrinterName.ppd -(the name which you gave the printer when installing it (see above). +This should install the correct driver directory structure under +<path>/etc/samba/printer</path>. That would be +<path>/etc/samba/printer/W32X86/2/</path>. The files contained should be the 3 +driver files and the PPD file, renamed to <path>YourPrinterName.ppd</path> (the +name which you gave the printer when installing it (see above). </p> <p> -Pending no errors or other complications, your drivers are now -installed. +Pending no errors or other complications, your drivers are now installed. </p> </body> @@ -921,8 +913,8 @@ <p> We will want to test our configuration file to ensure that it is formatted -properly and all of our options have at least the correct syntax. To do -this we run <c>testparm</c>. +properly and all of our options have at least the correct syntax. To do this we +run <c>testparm</c>. </p> <pre caption="Running the testparm"> @@ -962,9 +954,8 @@ <body> <p> -It would probably be prudent to check our logs at this time also. -We will also want to take a peak at our Samba shares using -<c>smbclient</c>. +It would probably be prudent to check our logs at this time also. We will also +want to take a peak at our Samba shares using <c>smbclient</c>. </p> <pre caption="Checking the shares with smbclient"> @@ -984,7 +975,7 @@ <body> <p> -Despite the variation or distribution, the only thing needed is CUPS. Do the +Despite the variation or distribution, the only thing needed is CUPS. Do the equivalent on any other UNIX/Linux/BSD client. </p> @@ -1025,8 +1016,8 @@ <p> Just point your web browser to <c>http://printserver:631</c> on the client if you want to manage your printers and their jobs with a nice web interface. -Replace <c>printserver</c> with the name of the <e>machine</e> that acts as -your print server, not the name you gave to the cups print server if you used +Replace <c>printserver</c> with the name of the <e>machine</e> that acts as your +print server, not the name you gave to the cups print server if you used different names. </p> @@ -1039,8 +1030,8 @@ <p> Now is time to configure our kernel to support smbfs. Since I'm assumming we've all compiled at least one kernel, we'll need to make sure we have all the right -options selected in our kernel. For simplicity sake, make it a module for ease -of use. It is the author's opinion that kernel modules are a good thing and +options selected in our kernel. For simplicity's sake, make it a module for ease +of use. It is the author's opinion that kernel modules are a good thing and should be used whenever possible. </p> @@ -1058,8 +1049,8 @@ </pre> <p> -Once the modules is loaded, mounting a Windows or Samba share is -possible. Use <c>mount</c> to accomplish this, as detailed below: +Once the module is loaded, mounting a Windows or Samba share is possible. Use +<c>mount</c> to accomplish this, as detailed below: </p> <pre caption="Mounting a Windows/Samba share"> @@ -1074,8 +1065,7 @@ </pre> <p> -After you mount the share, you would access it as if it were a local -drive. +After you mount the share, you would access it as if it were a local drive. </p> </body> @@ -1085,11 +1075,10 @@ <body> <p> -That's just a bit of point-and-click. Browse to -<path>\\PrintServer</path> and right click on the printer -(HPDeskJet930C) and click connect. This will download the drivers to -the Windows client and now every application (such as Word or Acrobat) -will offer HPDeskJet930C as an available printer to print to. :-) +That's just a bit of point-and-click. Browse to <path>\\PrintServer</path> and +right click on the printer (HPDeskJet930C) and click connect. This will download +the drivers to the Windows client and now every application (such as Word or +Acrobat) will offer HPDeskJet930C as an available printer to print to. :-) </p> </body> @@ -1103,9 +1092,8 @@ <body> <p> -Well that should be it. You should now have a successful printing enviroment -that is friendly to both Windows and *nix as well as a fully virus-free working -share! +That should be it. You should now have a successful printing enviroment that is +friendly to both Windows and *nix as well as a fully virus-free working share! </p> </body> @@ -1133,11 +1121,10 @@ <li><uri link="http://linuxprinting.org/";>LinuxPrinting dot Org</uri></li> <li> <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/";>Kurt - Pfeifle's Samba Print HOWTO</uri> ( - This HOWTO really covers <e>ANYTHING</e> and <e>EVERYTHING</e> - I've written here, plus a LOT more concerning CUPS and Samba, and - generally printing support on networks. A really interesting read, - with lots and lots of details) + Pfeifle's Samba Print HOWTO</uri> ( This HOWTO really covers <e>ANYTHING</e> + and <e>EVERYTHING</e> I've written here, plus a LOT more concerning CUPS and + Samba, and generally printing support on networks. A really interesting + read, with lots and lots of details.) </li> <li><uri link="http://www.freebsddiary.org/cups.php";>FreeBSD Diary's CUPS Topic</uri></li> </ul> @@ -1149,11 +1136,11 @@ <body> <p> -See <uri link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37";>this -page</uri> from Kurt Pfeifle's "Printing Support in Samba 3.0" -manual. Lots of useful tips there! Be sure to look this one up -first, before posting questions and problems! Maybe the solution -you're looking for is right there. +See <uri +link="http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/Samba-HOWTO-Collection-3.0-PrintingChapter-11th-draft.html#37";>this +page</uri> from Kurt Pfeifle's "Printing Support in Samba 3.0" manual. Lots of +useful tips there! Be sure to look this one up first, before posting questions +and problems! Maybe the solution you're looking for is right there. </p> </body> -- [EMAIL PROTECTED] mailing list
