Attachment 31592 Details for Bug 51294 – Fix for bug

[patch] Fix for bug

quick-samba-howto.diff (text/plain), 12.00 KB, created by Sune Kloppenborg Jeppesen (RETIRED) on 2004-05-17 10:19:11 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Sune Kloppenborg Jeppesen (RETIRED)

Created: 2004-05-17 10:19:11 UTC

Size: 12.00 KB

patch

obsolete

>--- en/quick-samba-howto.xml	2004-05-13 09:03:31.000000000 +0200
>+++ quick-samba-howto.xml	2004-05-17 19:15:09.803358596 +0200
>@@ -1,7 +1,7 @@
> <?xml version = '1.0' encoding = 'UTF-8'?>
> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
> <guide link="quick-samba-howto.xml">
>-<title>Gentoo Samba3/CUPS/clamav HOWTO</title>
>+<title>Gentoo Samba3/CUPS/Clam AV HOWTO</title>
> <author title="Author">
> <mail link="daff at dword dot org">Andreas "daff" Ntaflos</mail>
> </author>
>@@ -10,8 +10,8 @@
> </author>
> 
> <abstract>
>-Setup, install and configure a Samba Server under Gentoo that shares 
>-files, printers without the need to install drivers and provides 
>+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>
> 
>@@ -32,8 +32,8 @@
> This HOWTO is designed to help you move a network from many different 
> clients speaking different languages, to many different manchines that 
> speak a common language. The ultimate goal is to help differing
>-architechures and technologies, come together in a productive, 
>-happily coexistant environment.
>+architectures and technologies, come together in a productive, 
>+happily coexisting environment.
> 
> 
> 
>@@ -311,8 +311,9 @@
> 
> 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 /etc/hosts file. cupsaddsmb often
>-borks if hostnames don't point to the correct machines.
>+or appropriate entries in your <path>/etc/hosts</path> file.
>+<c>cupsaddsmb</c> often borks if hostnames don't point to the correct
>+machines. 
> 
> 
> 
>@@ -350,13 +351,13 @@
> </body>
> </section>
> <section>
>-<title>Emerging clam-av</title>
>+<title>Emerging Clam AV</title>
> <body>
> 
> 
>-Because the oav USE flag only provides an interface to allow on access 
>+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 <e>net-mail/clamav</e>.
>+used in this HOWTO is Clam AV.
> 
> 
> <pre caption="Emerge clam-av">
>@@ -401,8 +402,9 @@
> 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 smb.conf.example, the Samba 
>-Web site or any of the numerous Samba books available. 
>+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. 
> 
> 
> <pre caption="A Sample /etc/samba/smb.conf">
>@@ -493,24 +495,18 @@
> path = /home/samba/public
> </pre>
> 
>-
>-There are several warnings that we should put here:
>-
>+<warn>
> 
>-<ul>
>- <li>
>- If you like to use Samba's guest account to do anything concerning 
>- printing from Windows clients: don't
>- </li>
>- <li>Don't set guest only = yes in the global section</li>
>- <li>
>- The guest account seems to cause problems when running cupsaddsmb sometimes
>- when trying to connect from Windows machines. See below, too, when we talk
>- about cupsaddsmb and the problems that can arise. Use a dedicated printer 
>- user, like "printeruser" or "printer" or "printme" or whatever. It doesn't
>- hurt and it will certainly protect you from a lot of problems.
>- </li>
>-</ul>
>+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>
> 
> 
> Now create the directories required for the minimum configuration of 
>@@ -544,7 +540,7 @@
> </body>
> </section>
> <section>
>-<title>Configuring clam-av</title>
>+<title>Configuring Clam AV</title>
> <body>
> 
> 
>@@ -615,7 +611,7 @@
> 
> 
> It is generally a good idea to start the virus scanner immediately. Add 
>-it to the default runlevel and then start the clamd service immediately.
>+it to the <e>default</e> runlevel and then start the <c>clamd</c> service immediately.
> 
> 
> <pre caption="Add clamd to bootup and start it">
>@@ -630,7 +626,7 @@
> <body>
> 
> 
>-This is a little more complicated). CUPS' main config file is 
>+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:
>@@ -674,7 +670,8 @@
> 
> 
> Edit <path>/etc/cups/mime.convs</path> to uncomment some lines.
>-The changes to mime.convs and mime.types are needed to make CUPSprint Microsoft Office document files.
>+The changes to <path>mime.convs</path> and <path>mime.types</path> are
>+needed to make CUPS print Microsoft Office document files. 
> 
> 
> <pre caption="/etc/cups/mime.convs">
>@@ -726,9 +723,9 @@
> 
> 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 HP-DeskJet_930C-hpijs.ppd. You should now install the printer. 
>+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 http://PrintServer:631 once CUPS is running.
>+interface is found at <path>http://PrintServer:631</path> once CUPS is running.
> 
> 
> <pre caption="Install the printer via command line">
>@@ -736,15 +733,16 @@
> </pre>
> 
> 
>-Remember to adjust to what you have. Be sure to have the name (-p) right (the 
>-name you set above during the Samba configuration!) and to put in the 
>-correct usb:/dev/usb/blah, parallel:/dev/blah 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.
> 
> 
> 
>-You should now be able to access the printer from the web interface. You 
>-should now 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.
> 
> 
> </body>
>@@ -790,18 +788,18 @@
> </pre>
> 
> 
>-cups-samba.ss is a TAR archive containing three files:
>-cups5.hlp, cupsdrvr5.dll and cupsui5.dll. These are the actual driver 
>-files.
>+<path>cups-samba.ss</path> is a TAR archive containing three files:
>+<path>cups5.hlp</path>, <path>cupsdrvr5.dll</path> and
>+<path>cupsui5.dll</path>. These are the actual driver files.
> 
> 
> <warn>
>-The script cups-samba.install may not work for all *nixes (ie FreeBSD)
>+The script <c>cups-samba.install</c> may not work for all *nixes (ie 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.
>+<path>/usr/share/cups/</path> see the example below.
> </warn> 
> 
> 
>@@ -844,18 +842,18 @@
> 
> <ul>
> <li>
>- The hostname given as a parameter for -h and -H (PrintServer) often does
>- not resolve correctly and doesn't identify the print server for CUPS/Samba 
>- interaction.
>- If an error like: Warning: No PPD file for printer "CUPS_PRINTER_NAME" - 
>- skipping! occurs, the first thing you should do is substitute 
>- PrintServer with localhost and try it again.
>+ 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: Warning: No PPD file for printer "CUPS_PRINTER_NAME" -
>+ skipping! 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 NT_STATUS_UNSUCCESSFUL. 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 security = 
>- user in your <path>smb.conf</path>. After/if the installation completes 
>+ 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>
>@@ -973,7 +971,7 @@
> 
> 
> That should be it. Nothing else will be needed. Just point your web 
>-browser to http://localhost:631 (on the CLIENT) and you'll see that 
>+browser to <c>http://localhost:631</c> on the client and you'll see that 
> PrintServer broadcasts all available printers to all CUPS clients.
> 
> 
>@@ -987,10 +985,10 @@
> </pre>
> 
> 
>-In order to setup a default printer, you have to edit 
>-<path>/etc/cups/client.conf</path> and set the directive ServerName to 
>-your printserver. In the case of this guide that would be the 
>-following example.
>+In order to setup a default printer, you have to edit
>+<path>/etc/cups/client.conf</path> and set the directive
>+<c>ServerName</c> to your printserver. In the case of this guide that
>+would be the following example.
> 
> 
> <pre caption="/etc/cups/client.conf">
>@@ -998,7 +996,7 @@
> </pre>
> 
> 
>-The following will print foorbar.whatever.ps directly to the print 
>+The following will print <path>foorbar.whatever.ps</path> directly to the print 
> server.
> 
> 
>@@ -1013,14 +1011,15 @@
> 
> <ul>
> <li>
>- Setting the ServerName in client.conf seems to work well for only one 
>- printer, there may be yet another way to set a client's default remote 
>- printer.
>+ Setting the <c>ServerName</c> in <path>client.conf</path> seems to
>+ work well for only one printer, there may be yet another way to
>+ set a client's default remote printer.
> </li>
> <li>
>- Also, when accessing http://localhost:631 on the client now, no printers 
>- seem to be "found" by the client-CUPS. This is to be expected when setting
>- ServerName in <path>client.conf</path>.
>+ Also, when accessing <c>http://localhost:631</c> on the client
>+ now, no printers seem to be "found" by the client-CUPS. This is to
>+ be expected when setting <c>ServerName</c> in
>+ <path>client.conf</path>.
> </li>
> </ul>
> 
>@@ -1031,10 +1030,10 @@
> <body>
> 
> 
>-Now is time to configure our kernel to support it the smbfs. Since I'm 
>+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 as a module for ease of use. It is the
>+For simplicity sake, make it a module for ease of use. It is the
> authors opinion that kernel modules are a good thing and should be used 
> whenever possible.
> 
>@@ -1080,11 +1079,11 @@
> <body>
> 
> 
>-That's just a bit of point-and-click. Browse to \\PrintServer 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. :-)
> 
> 
> </body>

Actions: View | Diff

Attachments on bug 51294: 31592