neysx 07/12/01 11:30:40 Modified: quick-samba-howto.xml Log: Minor formatting fixes, no content change
Revision Changes Path 1.37 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.37&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml?rev=1.37&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml?r1=1.36&r2=1.37 Index: quick-samba-howto.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v retrieving revision 1.36 retrieving revision 1.37 diff -u -r1.36 -r1.37 --- quick-samba-howto.xml 1 Dec 2007 11:25:01 -0000 1.36 +++ quick-samba-howto.xml 1 Dec 2007 11:30:40 -0000 1.37 @@ -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.36 2007/12/01 11:25:01 neysx Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.37 2007/12/01 11:30:40 neysx Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> <guide link="/doc/en/quick-samba-howto.xml"> @@ -72,15 +72,15 @@ </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 +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> <li> - <uri link="http://forums.gentoo.org/viewtopic.php?t=110931";>HOWTO + <uri link="http://forums.gentoo.org/viewtopic.php?t=110931";>HOWTO CUPS+Samba: printing from Windows & Linux</uri> </li> </ul> @@ -200,17 +200,17 @@ <tr> <th><b>kerberos</b></th> <ti> - Include support for Kerberos. The server will need this if it is - intended to join an existing domain or Active Directory. See the note - below for more information. + Include support for Kerberos. The server will need this if it is intended + to join an existing domain or Active Directory. See the note below for more + information. </ti> </tr> <tr> <th><b>acl</b></th> <ti> Enables Access Control Lists. The ACL support in Samba uses a patched - ext2/ext3, or SGI's XFS in order to function properly as it extends more - detailed access to files or directories; much more so than typical *nix + ext2/ext3, or SGI's XFS in order to function properly as it extends more + detailed access to files or directories; much more so than typical *nix GID/UID schemas. </ti> </tr> @@ -235,7 +235,7 @@ <tr> <th><b>pam</b></th> <ti> - Include support for pluggable authentication modules (PAM). This provides + 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. @@ -272,9 +272,9 @@ <ul> <li> - ACLs on ext2/3 are implemented through extended attributes (EAs). EA and - ACL kernel options for ext2 and/or ext3 will need to be enabled - (depending on which file system is being used - both can be enabled). + ACLs on ext2/3 are implemented through extended attributes (EAs). EA and + ACL kernel options for ext2 and/or ext3 will need to be enabled (depending + on which file system is being used - both can be enabled). </li> <li> While Active Directory, ACL, and PDC functions are out of the intended @@ -300,7 +300,7 @@ 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. +don't point to the correct machines. </p> <p> @@ -380,12 +380,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 +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. +Samba Web site or any of the numerous Samba books available. </p> <pre caption="A Sample /etc/samba/smb.conf"> @@ -452,14 +452,14 @@ # be the only printer admin)</comment> printer admin = <i>root</i> -<comment># Now we setup our printers share. This should be +<comment># Now we setup our printers share. This should be # browseable, printable, public.</comment> -[printers] +[printers] comment = All Printers -browseable = no -printable = yes +browseable = no +printable = yes writable = no -public = yes +public = yes guest ok = yes path = /var/spool/samba <comment># Modify this to "username,root" if you don't want root to @@ -512,14 +512,14 @@ </p> <pre caption="Creating the users"> -# <i>smbpasswd -a root</i> +# <i>smbpasswd -a root</i> <comment>(If another user is to be a printer admin)</comment> # <i>smbpasswd -a username</i> </pre> <p> -The Samba passwords need not be the same as the system passwords +The Samba passwords need not be the same as the system passwords in <path>/etc/passwd</path>. </p> @@ -655,7 +655,7 @@ AccessLog /var/log/cups/access_log <comment># probably doesn't need changing</comment> ErrorLog /var/log/cups/error_log <comment># doesn't really need changing either</comment> -LogLevel debug <comment># only while isntalling and testing, should later be +LogLevel debug <comment># only while installing and testing, should later be # changed to 'info'</comment> MaxClients 100 <comment># I've had to set this to 1000000000 or so because some time back, @@ -663,7 +663,7 @@ # making CUPS think a denial of service attack was in progress when # I tried to configure a printer with the web interface. weird.</comment> -BrowseAddress @IF(<i>eth0</i>) <comment># Change this to your internal net interface</comment> +BrowseAddress @IF(<i>eth0</i>) <comment># Change this to your internal net interface</comment> <Location /> Order Deny,Allow @@ -677,7 +677,7 @@ AuthType Basic AuthClass System Allow From <i>192.168.1.*</i> <comment># same as above, allow any host on the - # 192.168.1.0 network to connect and do + # 192.168.1.0 network to connect and do # administrative tasks after authenticating</comment> Order Deny,Allow Deny From All @@ -685,14 +685,14 @@ </pre> <p> -Edit <path>/etc/cups/mime.convs</path> to uncomment some lines. -The changes to <path>mime.convs</path> and <path>mime.types</path> are -needed to make CUPS print Microsoft Office document files. +Edit <path>/etc/cups/mime.convs</path> to uncomment some lines. The changes to +<path>mime.convs</path> and <path>mime.types</path> are needed to make CUPS +print Microsoft Office document files. </p> <pre caption="/etc/cups/mime.convs"> <comment>(The following line is found near the end of the file. Uncomment it)</comment> -application/octet-stream application/vnd.cups-raw 0 +application/octet-stream application/vnd.cups-raw 0 </pre> <p> @@ -701,11 +701,11 @@ <pre caption="/etc/cups/mime.types"> <comment>(The following line is found near the end of the file. Uncomment it)</comment> -application/octet-stream +application/octet-stream </pre> <p> -CUPS needs to be started on boot, and started immediately. +CUPS needs to be started on boot, and started immediately. </p> <pre caption="Setting up the CUPS service" > @@ -766,9 +766,9 @@ <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 +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. -- [EMAIL PROTECTED] mailing list
