diff options
author | Gerald Carter <jerry@samba.org> | 2001-06-01 11:50:38 +0000 |
---|---|---|
committer | Gerald Carter <jerry@samba.org> | 2001-06-01 11:50:38 +0000 |
commit | 05b2b2cdd4895b6d2a4d345192bfd4fed1e0ec25 (patch) | |
tree | 0c08619346abcac14ae3eb579b60e8c58bf84822 /docs | |
parent | e07b85ab195509cd1bd83e813ecf464f5629c566 (diff) | |
download | samba-05b2b2cdd4895b6d2a4d345192bfd4fed1e0ec25.tar.gz samba-05b2b2cdd4895b6d2a4d345192bfd4fed1e0ec25.tar.bz2 samba-05b2b2cdd4895b6d2a4d345192bfd4fed1e0ec25.zip |
syncing up with SAMBA_2_2
(This used to be commit 1bc58c21b15fcdb0a504d051f60e20c4e24441e6)
Diffstat (limited to 'docs')
39 files changed, 10056 insertions, 4585 deletions
diff --git a/docs/Samba-HOWTO-Collection.pdf b/docs/Samba-HOWTO-Collection.pdf index b41513ed06..251416d1cd 100644 --- a/docs/Samba-HOWTO-Collection.pdf +++ b/docs/Samba-HOWTO-Collection.pdf @@ -1,6 +1,6 @@ %PDF-1.2 %âãÏÓ -1 0 obj<</Producer(htmldoc 1.8.11 Copyright 1997-2001 Easy Software Products, All Rights Reserved.)/CreationDate(D:20010424184435Z)/Title(SAMBA Project Documentation)/Creator(Modular DocBook HTML Stylesheet Version 1.57)>>endobj +1 0 obj<</Producer(htmldoc 1.8.11 Copyright 1997-2001 Easy Software Products, All Rights Reserved.)/CreationDate(D:20010601114858Z)/Title(SAMBA Project Documentation)/Creator(Modular DocBook HTML Stylesheet Version 1.57)>>endobj 2 0 obj<</Type/Encoding/Differences[ 32/space/exclam/quotedbl/numbersign/dollar/percent/ampersand/quotesingle/parenleft/parenright/asterisk/plus/comma/minus/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/asciicircum/underscore/grave/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde 128/Euro 130/quotesinglbase/florin/quotedblbase/ellipsis/dagger/daggerdbl/circumflex/perthousand/Scaron/guilsinglleft/OE 145/quoteleft/quoteright/quotedblleft/quotedblright/bullet/endash/emdash/tilde/trademark/scaron/guilsinglright/oe 159/Ydieresis/space/exclamdown/cent/sterling/currency/yen/brokenbar/section/dieresis/copyright/ordfeminine/guillemotleft/logicalnot/hyphen/registered/macron/degree/plusminus/twosuperior/threesuperior/acute/mu/paragraph/periodcentered/cedilla/onesuperior/ordmasculine/guillemotright/onequarter/onehalf/threequarters/questiondown/Agrave/Aacute/Acircumflex/Atilde/Adieresis/Aring/AE/Ccedilla/Egrave/Eacute/Ecircumflex/Edieresis/Igrave/Iacute/Icircumflex/Idieresis/Eth/Ntilde/Ograve/Oacute/Ocircumflex/Otilde/Odieresis/multiply/Oslash/Ugrave/Uacute/Ucircumflex/Udieresis/Yacute/Thorn/germandbls/agrave/aacute/acircumflex/atilde/adieresis/aring/ae/ccedilla/egrave/eacute/ecircumflex/edieresis/igrave/iacute/icircumflex/idieresis/eth/ntilde/ograve/oacute/ocircumflex/otilde/odieresis/divide/oslash/ugrave/uacute/ucircumflex/udieresis/yacute/thorn/ydieresis]>>endobj 3 0 obj<</Type/Font/Subtype/Type1/BaseFont/Courier/Encoding 2 0 R>>endobj 4 0 obj<</Type/Font/Subtype/Type1/BaseFont/Courier-Bold/Encoding 2 0 R>>endobj @@ -13,7 +13,7 @@ 11 0 obj<</Type/Font/Subtype/Type1/BaseFont/Helvetica-Bold/Encoding 2 0 R>>endobj 12 0 obj<</Type/Font/Subtype/Type1/BaseFont/Symbol>>endobj 13 0 obj<</S/URI/URI(http://www.samba.org/)>>endobj -14 0 obj<</Subtype/Link/Rect[188.7 476.2 290.2 489.2]/Border[0 0 0]/A 13 0 R>>endobj +14 0 obj<</Subtype/Link/Rect[188.4 476.2 289.8 489.2]/Border[0 0 0]/A 13 0 R>>endobj 15 0 obj<</S/URI/URI(mailto:jerry@samba.org)>>endobj 16 0 obj<</Subtype/Link/Rect[72.0 463.0 148.4 476.0]/Border[0 0 0]/A 15 0 R>>endobj 17 0 obj[14 0 R @@ -23,7 +23,7 @@ 19 0 obj<</Subtype/Link/Rect[369.9 587.8 471.0 600.8]/Border[0 0 0]/A 18 0 R>>endobj 20 0 obj[19 0 R ]endobj -21 0 obj<</Subtype/Link/Rect[295.1 319.4 385.6 332.4]/Border[0 0 0]/Dest[440 0 R/XYZ null 656 0]>>endobj +21 0 obj<</Subtype/Link/Rect[295.1 319.4 385.6 332.4]/Border[0 0 0]/Dest[481 0 R/XYZ null 656 0]>>endobj 22 0 obj[21 0 R ]endobj 23 0 obj<</S/URI/URI(http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp)>>endobj @@ -40,23 +40,23 @@ 31 0 obj<</Subtype/Link/Rect[146.5 548.2 280.3 561.2]/Border[0 0 0]/A 30 0 R>>endobj 32 0 obj<</S/URI/URI(http://msdn.microsoft.com/)>>endobj 33 0 obj<</Subtype/Link/Rect[221.4 521.8 341.1 534.8]/Border[0 0 0]/A 32 0 R>>endobj -34 0 obj<</Subtype/Link/Rect[460.9 252.2 541.6 265.2]/Border[0 0 0]/Dest[470 0 R/XYZ null 528 0]>>endobj -35 0 obj[31 0 R +34 0 obj<</S/URI/URI(http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP)>>endobj +35 0 obj<</Subtype/Link/Rect[72.0 297.4 355.9 310.4]/Border[0 0 0]/A 34 0 R>>endobj +36 0 obj[31 0 R 33 0 R -34 0 R +35 0 R ]endobj -36 0 obj<</S/URI/URI(#WRITELIST)>>endobj -37 0 obj<</Subtype/Link/Rect[91.9 663.4 157.9 676.4]/Border[0 0 0]/A 36 0 R>>endobj -38 0 obj<</S/URI/URI(conf.5.html)>>endobj -39 0 obj<</Subtype/Link/Rect[192.7 650.2 291.3 663.2]/Border[0 0 0]/A 38 0 R>>endobj -40 0 obj<</S/URI/URI(#GUESTOK)>>endobj -41 0 obj<</Subtype/Link/Rect[163.3 623.8 228.6 636.8]/Border[0 0 0]/A 40 0 R>>endobj -42 0 obj<</S/URI/URI(#MAPTOGUEST)>>endobj -43 0 obj<</Subtype/Link/Rect[401.4 518.2 492.0 531.2]/Border[0 0 0]/A 42 0 R>>endobj +37 0 obj<</Subtype/Link/Rect[462.9 705.8 540.9 718.8]/Border[0 0 0]/Dest[511 0 R/XYZ null 191 0]>>endobj +38 0 obj<</S/URI/URI(#WRITELIST)>>endobj +39 0 obj<</Subtype/Link/Rect[91.9 391.4 157.9 404.4]/Border[0 0 0]/A 38 0 R>>endobj +40 0 obj<</S/URI/URI(conf.5.html)>>endobj +41 0 obj<</Subtype/Link/Rect[192.7 378.2 294.1 391.2]/Border[0 0 0]/A 40 0 R>>endobj +42 0 obj<</S/URI/URI(#GUESTOK)>>endobj +43 0 obj<</Subtype/Link/Rect[163.3 351.8 231.3 364.8]/Border[0 0 0]/A 42 0 R>>endobj 44 0 obj<</S/URI/URI(#MAPTOGUEST)>>endobj -45 0 obj<</Subtype/Link/Rect[108.0 505.0 130.0 518.0]/Border[0 0 0]/A 44 0 R>>endobj -46 0 obj<</S/URI/URI(#PRINTERADMIN)>>endobj -47 0 obj<</Subtype/Link/Rect[433.8 233.0 526.2 246.0]/Border[0 0 0]/A 46 0 R>>endobj +45 0 obj<</Subtype/Link/Rect[401.4 246.2 492.0 259.2]/Border[0 0 0]/A 44 0 R>>endobj +46 0 obj<</S/URI/URI(#MAPTOGUEST)>>endobj +47 0 obj<</Subtype/Link/Rect[108.0 233.0 130.0 246.0]/Border[0 0 0]/A 46 0 R>>endobj 48 0 obj[37 0 R 39 0 R 41 0 R @@ -64,311 +64,318 @@ 45 0 R 47 0 R ]endobj -49 0 obj<</S/URI/URI(rpcclient.1.html)>>endobj -50 0 obj<</Subtype/Link/Rect[239.1 342.2 382.1 355.2]/Border[0 0 0]/A 49 0 R>>endobj +49 0 obj<</S/URI/URI(#PRINTERADMIN)>>endobj +50 0 obj<</Subtype/Link/Rect[433.8 647.0 526.2 660.0]/Border[0 0 0]/A 49 0 R>>endobj 51 0 obj[50 0 R ]endobj -52 0 obj<</S/URI/URI(#SHOWADDPRINTERWIZARD)>>endobj -53 0 obj<</Subtype/Link/Rect[108.0 584.6 306.0 597.6]/Border[0 0 0]/A 52 0 R>>endobj -54 0 obj<</S/URI/URI(#ADDPRINTERCOMMAND)>>endobj -55 0 obj<</Subtype/Link/Rect[456.6 558.2 522.6 571.2]/Border[0 0 0]/A 54 0 R>>endobj +52 0 obj<</S/URI/URI(rpcclient.1.html)>>endobj +53 0 obj<</Subtype/Link/Rect[239.1 664.6 382.1 677.6]/Border[0 0 0]/A 52 0 R>>endobj +54 0 obj<</S/URI/URI(#SHOWADDPRINTERWIZARD)>>endobj +55 0 obj<</Subtype/Link/Rect[108.0 240.2 306.0 253.2]/Border[0 0 0]/A 54 0 R>>endobj 56 0 obj<</S/URI/URI(#ADDPRINTERCOMMAND)>>endobj -57 0 obj<</Subtype/Link/Rect[72.0 545.0 118.2 558.0]/Border[0 0 0]/A 56 0 R>>endobj -58 0 obj<</S/URI/URI(#DELETEPRINTERCOMMAND)>>endobj -59 0 obj<</Subtype/Link/Rect[189.3 439.4 334.5 452.4]/Border[0 0 0]/A 58 0 R>>endobj -60 0 obj<</S/URI/URI(#ENUMPORTSCOMMAND)>>endobj -61 0 obj<</Subtype/Link/Rect[451.4 262.2 510.8 275.2]/Border[0 0 0]/A 60 0 R>>endobj -62 0 obj<</S/URI/URI(#ENUMPORTSCOMMAND)>>endobj -63 0 obj<</Subtype/Link/Rect[72.0 249.0 118.2 262.0]/Border[0 0 0]/A 62 0 R>>endobj -64 0 obj<</S/URI/URI(http://imprints.sourceforge.net/)>>endobj -65 0 obj<</Subtype/Link/Rect[303.3 164.2 442.9 177.2]/Border[0 0 0]/A 64 0 R>>endobj -66 0 obj[53 0 R +57 0 obj<</Subtype/Link/Rect[456.6 213.8 535.8 226.8]/Border[0 0 0]/A 56 0 R>>endobj +58 0 obj<</S/URI/URI(#ADDPRINTERCOMMAND)>>endobj +59 0 obj<</Subtype/Link/Rect[72.0 200.6 118.2 213.6]/Border[0 0 0]/A 58 0 R>>endobj +60 0 obj<</S/URI/URI(#DELETEPRINTERCOMMAND)>>endobj +61 0 obj<</Subtype/Link/Rect[189.3 95.0 334.5 108.0]/Border[0 0 0]/A 60 0 R>>endobj +62 0 obj[53 0 R 55 0 R 57 0 R 59 0 R 61 0 R -63 0 R -65 0 R ]endobj +63 0 obj<</S/URI/URI(#ENUMPORTSCOMMAND)>>endobj +64 0 obj<</Subtype/Link/Rect[451.4 585.4 510.8 598.4]/Border[0 0 0]/A 63 0 R>>endobj +65 0 obj<</S/URI/URI(#ENUMPORTSCOMMAND)>>endobj +66 0 obj<</Subtype/Link/Rect[72.0 572.2 118.2 585.2]/Border[0 0 0]/A 65 0 R>>endobj 67 0 obj<</S/URI/URI(http://imprints.sourceforge.net/)>>endobj -68 0 obj<</Subtype/Link/Rect[108.0 83.0 244.9 96.0]/Border[0 0 0]/A 67 0 R>>endobj -69 0 obj[68 0 R +68 0 obj<</Subtype/Link/Rect[303.3 487.4 442.9 500.4]/Border[0 0 0]/A 67 0 R>>endobj +69 0 obj[64 0 R +66 0 R +68 0 R ]endobj -70 0 obj<</S/URI/URI(smbpasswd.8.html)>>endobj -71 0 obj<</Subtype/Link/Rect[221.4 416.2 287.7 429.2]/Border[0 0 0]/A 70 0 R>>endobj -72 0 obj<</S/URI/URI(smb.conf.5.html)>>endobj -73 0 obj<</Subtype/Link/Rect[353.1 99.4 425.7 112.4]/Border[0 0 0]/A 72 0 R>>endobj -74 0 obj<</S/URI/URI(#SECURITY)>>endobj -75 0 obj<</Subtype/Link/Rect[169.1 59.8 241.7 72.8]/Border[0 0 0]/A 74 0 R>>endobj -76 0 obj[71 0 R -73 0 R -75 0 R +70 0 obj<</S/URI/URI(http://imprints.sourceforge.net/)>>endobj +71 0 obj<</Subtype/Link/Rect[108.0 154.6 244.9 167.6]/Border[0 0 0]/A 70 0 R>>endobj +72 0 obj[71 0 R ]endobj -77 0 obj<</S/URI/URI(#WORKGROUP)>>endobj -78 0 obj<</Subtype/Link/Rect[146.2 694.6 225.4 707.6]/Border[0 0 0]/A 77 0 R>>endobj -79 0 obj<</S/URI/URI(#ENCRYPTPASSWORDS)>>endobj -80 0 obj<</Subtype/Link/Rect[224.7 615.4 343.5 628.4]/Border[0 0 0]/A 79 0 R>>endobj -81 0 obj<</S/URI/URI(#PASSWORDSERVER)>>endobj -82 0 obj<</Subtype/Link/Rect[188.7 575.8 307.5 588.8]/Border[0 0 0]/A 81 0 R>>endobj -83 0 obj[78 0 R -80 0 R -82 0 R +73 0 obj<</S/URI/URI(smbpasswd.8.html)>>endobj +74 0 obj<</Subtype/Link/Rect[221.4 416.2 287.7 429.2]/Border[0 0 0]/A 73 0 R>>endobj +75 0 obj<</S/URI/URI(smb.conf.5.html)>>endobj +76 0 obj<</Subtype/Link/Rect[353.1 99.4 425.7 112.4]/Border[0 0 0]/A 75 0 R>>endobj +77 0 obj<</S/URI/URI(#SECURITY)>>endobj +78 0 obj<</Subtype/Link/Rect[169.1 59.8 241.7 72.8]/Border[0 0 0]/A 77 0 R>>endobj +79 0 obj[74 0 R +76 0 R +78 0 R ]endobj -84 0 obj<</S/URI/URI(#SECURITYEQUALSSERVER)>>endobj -85 0 obj<</Subtype/Link/Rect[277.9 651.4 354.1 664.4]/Border[0 0 0]/A 84 0 R>>endobj -86 0 obj<</S/URI/URI(winbind.html)>>endobj -87 0 obj<</Subtype/Link/Rect[153.9 598.6 222.3 611.6]/Border[0 0 0]/A 86 0 R>>endobj -88 0 obj<</S/URI/URI(http://www.linuxworld.com)>>endobj -89 0 obj<</Subtype/Link/Rect[443.5 281.8 500.6 294.8]/Border[0 0 0]/A 88 0 R>>endobj -90 0 obj<</S/URI/URI(http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html)>>endobj -91 0 obj<</Subtype/Link/Rect[72.0 268.6 189.3 281.6]/Border[0 0 0]/A 90 0 R>>endobj -92 0 obj[85 0 R -87 0 R -89 0 R -91 0 R +80 0 obj<</S/URI/URI(#WORKGROUP)>>endobj +81 0 obj<</Subtype/Link/Rect[146.2 694.6 225.4 707.6]/Border[0 0 0]/A 80 0 R>>endobj +82 0 obj<</S/URI/URI(#ENCRYPTPASSWORDS)>>endobj +83 0 obj<</Subtype/Link/Rect[224.7 615.4 343.5 628.4]/Border[0 0 0]/A 82 0 R>>endobj +84 0 obj<</S/URI/URI(#PASSWORDSERVER)>>endobj +85 0 obj<</Subtype/Link/Rect[188.7 575.8 307.5 588.8]/Border[0 0 0]/A 84 0 R>>endobj +86 0 obj[81 0 R +83 0 R +85 0 R ]endobj -93 0 obj<</S/URI/URI(UNIX_INSTALL.html)>>endobj -94 0 obj<</Subtype/Link/Rect[446.0 273.4 547.7 286.4]/Border[0 0 0]/A 93 0 R>>endobj -95 0 obj<</S/URI/URI(smb.conf.5.html)>>endobj -96 0 obj<</Subtype/Link/Rect[72.0 247.0 173.4 260.0]/Border[0 0 0]/A 95 0 R>>endobj -97 0 obj[94 0 R -96 0 R +87 0 obj<</S/URI/URI(#SECURITYEQUALSSERVER)>>endobj +88 0 obj<</Subtype/Link/Rect[277.9 651.4 354.1 664.4]/Border[0 0 0]/A 87 0 R>>endobj +89 0 obj<</S/URI/URI(winbind.html)>>endobj +90 0 obj<</Subtype/Link/Rect[153.9 598.6 222.3 611.6]/Border[0 0 0]/A 89 0 R>>endobj +91 0 obj<</S/URI/URI(http://www.linuxworld.com)>>endobj +92 0 obj<</Subtype/Link/Rect[443.5 281.8 500.6 294.8]/Border[0 0 0]/A 91 0 R>>endobj +93 0 obj<</S/URI/URI(http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html)>>endobj +94 0 obj<</Subtype/Link/Rect[72.0 268.6 189.3 281.6]/Border[0 0 0]/A 93 0 R>>endobj +95 0 obj[88 0 R +90 0 R +92 0 R +94 0 R ]endobj -98 0 obj<</S/URI/URI(smb.conf.5.html)>>endobj -99 0 obj<</Subtype/Link/Rect[468.3 677.8 549.6 690.8]/Border[0 0 0]/A 98 0 R>>endobj -100 0 obj<</S/URI/URI(smb.conf.5.html)>>endobj -101 0 obj<</Subtype/Link/Rect[72.0 664.6 92.8 677.6]/Border[0 0 0]/A 100 0 R>>endobj -102 0 obj<</S/URI/URI(#NETBIOSNAME)>>endobj -103 0 obj<</Subtype/Link/Rect[94.6 591.2 159.4 602.2]/Border[0 0 0]/A 102 0 R>>endobj -104 0 obj<</S/URI/URI(#WORKGROUP)>>endobj -105 0 obj<</Subtype/Link/Rect[94.6 580.4 143.2 591.4]/Border[0 0 0]/A 104 0 R>>endobj -106 0 obj<</S/URI/URI(#OSLEVEL)>>endobj -107 0 obj<</Subtype/Link/Rect[94.6 548.0 137.8 559.0]/Border[0 0 0]/A 106 0 R>>endobj -108 0 obj<</S/URI/URI(#PERFERREDMASTER)>>endobj -109 0 obj<</Subtype/Link/Rect[94.6 537.2 181.0 548.2]/Border[0 0 0]/A 108 0 R>>endobj -110 0 obj<</S/URI/URI(#DOMAINMASTER)>>endobj -111 0 obj<</Subtype/Link/Rect[94.6 526.4 164.8 537.4]/Border[0 0 0]/A 110 0 R>>endobj -112 0 obj<</S/URI/URI(#LOCALMASTER)>>endobj -113 0 obj<</Subtype/Link/Rect[94.6 515.6 159.4 526.6]/Border[0 0 0]/A 112 0 R>>endobj -114 0 obj<</S/URI/URI(#SECURITYEQUALSUSER)>>endobj -115 0 obj<</Subtype/Link/Rect[94.6 483.2 137.8 494.2]/Border[0 0 0]/A 114 0 R>>endobj -116 0 obj<</S/URI/URI(#ENCRYPTPASSWORDS)>>endobj -117 0 obj<</Subtype/Link/Rect[94.6 450.8 186.4 461.8]/Border[0 0 0]/A 116 0 R>>endobj -118 0 obj<</S/URI/URI(#DOMAINLOGONS)>>endobj -119 0 obj<</Subtype/Link/Rect[94.6 418.4 164.8 429.4]/Border[0 0 0]/A 118 0 R>>endobj -120 0 obj<</S/URI/URI(#LOGONPATH)>>endobj -121 0 obj<</Subtype/Link/Rect[94.6 386.0 148.6 397.0]/Border[0 0 0]/A 120 0 R>>endobj -122 0 obj<</S/URI/URI(#LOGONDRIVE)>>endobj -123 0 obj<</Subtype/Link/Rect[94.6 342.8 154.0 353.8]/Border[0 0 0]/A 122 0 R>>endobj -124 0 obj<</S/URI/URI(#LOGONHOME)>>endobj -125 0 obj<</Subtype/Link/Rect[94.6 332.0 148.6 343.0]/Border[0 0 0]/A 124 0 R>>endobj -126 0 obj<</S/URI/URI(#LOGONSCRIPT)>>endobj -127 0 obj<</Subtype/Link/Rect[94.6 288.8 159.4 299.8]/Border[0 0 0]/A 126 0 R>>endobj -128 0 obj<</S/URI/URI(#PATH)>>endobj -129 0 obj<</Subtype/Link/Rect[94.6 245.6 116.2 256.6]/Border[0 0 0]/A 128 0 R>>endobj -130 0 obj<</S/URI/URI(#WRITEABLE)>>endobj -131 0 obj<</Subtype/Link/Rect[94.6 234.8 143.2 245.8]/Border[0 0 0]/A 130 0 R>>endobj -132 0 obj<</S/URI/URI(#WRITELIST)>>endobj -133 0 obj<</Subtype/Link/Rect[94.6 224.0 148.6 235.0]/Border[0 0 0]/A 132 0 R>>endobj -134 0 obj<</S/URI/URI(#PATH)>>endobj -135 0 obj<</Subtype/Link/Rect[94.6 180.8 116.2 191.8]/Border[0 0 0]/A 134 0 R>>endobj -136 0 obj<</S/URI/URI(#WRITEABLE)>>endobj -137 0 obj<</Subtype/Link/Rect[94.6 170.0 143.2 181.0]/Border[0 0 0]/A 136 0 R>>endobj -138 0 obj<</S/URI/URI(#CREATEMASK)>>endobj -139 0 obj<</Subtype/Link/Rect[94.6 159.2 154.0 170.2]/Border[0 0 0]/A 138 0 R>>endobj -140 0 obj<</S/URI/URI(#DIRECTORYMASK)>>endobj -141 0 obj<</Subtype/Link/Rect[94.6 148.4 170.2 159.4]/Border[0 0 0]/A 140 0 R>>endobj -142 0 obj<</S/URI/URI(ENCRYPTION.html)>>endobj -143 0 obj<</Subtype/Link/Rect[108.0 82.6 200.6 95.6]/Border[0 0 0]/A 142 0 R>>endobj -144 0 obj[99 0 R +96 0 obj<</S/URI/URI(smb.conf.5.html)>>endobj +97 0 obj<</Subtype/Link/Rect[182.3 603.4 254.9 616.4]/Border[0 0 0]/A 96 0 R>>endobj +98 0 obj<</S/URI/URI(EMCRYPTION.html)>>endobj +99 0 obj<</Subtype/Link/Rect[334.9 603.4 418.9 616.4]/Border[0 0 0]/A 98 0 R>>endobj +100 0 obj<</S/URI/URI(UNIX_INSTALL.html)>>endobj +101 0 obj<</Subtype/Link/Rect[72.0 426.2 173.7 439.2]/Border[0 0 0]/A 100 0 R>>endobj +102 0 obj<</S/URI/URI(smb.conf.5.html)>>endobj +103 0 obj<</Subtype/Link/Rect[167.0 413.0 268.4 426.0]/Border[0 0 0]/A 102 0 R>>endobj +104 0 obj[97 0 R +99 0 R 101 0 R 103 0 R -105 0 R -107 0 R -109 0 R -111 0 R -113 0 R -115 0 R -117 0 R -119 0 R -121 0 R -123 0 R -125 0 R -127 0 R -129 0 R -131 0 R -133 0 R -135 0 R -137 0 R -139 0 R -141 0 R -143 0 R ]endobj -145 0 obj<</S/URI/URI(#DOMAINADMONUSERS)>>endobj -146 0 obj<</Subtype/Link/Rect[505.2 668.2 538.2 681.2]/Border[0 0 0]/A 145 0 R>>endobj -147 0 obj<</S/URI/URI(#DOMAINADMONUSERS)>>endobj -148 0 obj<</Subtype/Link/Rect[72.0 655.0 124.9 668.0]/Border[0 0 0]/A 147 0 R>>endobj -149 0 obj<</S/URI/URI(#DOMAINADMINGROUP)>>endobj -150 0 obj<</Subtype/Link/Rect[146.2 655.0 240.7 668.0]/Border[0 0 0]/A 149 0 R>>endobj -151 0 obj[146 0 R -148 0 R -150 0 R +105 0 obj<</S/URI/URI(smb.conf.5.html)>>endobj +106 0 obj<</Subtype/Link/Rect[468.3 570.2 549.6 583.2]/Border[0 0 0]/A 105 0 R>>endobj +107 0 obj<</S/URI/URI(smb.conf.5.html)>>endobj +108 0 obj<</Subtype/Link/Rect[72.0 557.0 92.8 570.0]/Border[0 0 0]/A 107 0 R>>endobj +109 0 obj<</S/URI/URI(#NETBIOSNAME)>>endobj +110 0 obj<</Subtype/Link/Rect[94.6 483.6 159.4 494.6]/Border[0 0 0]/A 109 0 R>>endobj +111 0 obj<</S/URI/URI(#WORKGROUP)>>endobj +112 0 obj<</Subtype/Link/Rect[94.6 472.8 143.2 483.8]/Border[0 0 0]/A 111 0 R>>endobj +113 0 obj<</S/URI/URI(#OSLEVEL)>>endobj +114 0 obj<</Subtype/Link/Rect[94.6 440.4 137.8 451.4]/Border[0 0 0]/A 113 0 R>>endobj +115 0 obj<</S/URI/URI(#PERFERREDMASTER)>>endobj +116 0 obj<</Subtype/Link/Rect[94.6 429.6 181.0 440.6]/Border[0 0 0]/A 115 0 R>>endobj +117 0 obj<</S/URI/URI(#DOMAINMASTER)>>endobj +118 0 obj<</Subtype/Link/Rect[94.6 418.8 164.8 429.8]/Border[0 0 0]/A 117 0 R>>endobj +119 0 obj<</S/URI/URI(#LOCALMASTER)>>endobj +120 0 obj<</Subtype/Link/Rect[94.6 408.0 159.4 419.0]/Border[0 0 0]/A 119 0 R>>endobj +121 0 obj<</S/URI/URI(#SECURITYEQUALSUSER)>>endobj +122 0 obj<</Subtype/Link/Rect[94.6 375.6 137.8 386.6]/Border[0 0 0]/A 121 0 R>>endobj +123 0 obj<</S/URI/URI(#ENCRYPTPASSWORDS)>>endobj +124 0 obj<</Subtype/Link/Rect[94.6 343.2 186.4 354.2]/Border[0 0 0]/A 123 0 R>>endobj +125 0 obj<</S/URI/URI(#DOMAINLOGONS)>>endobj +126 0 obj<</Subtype/Link/Rect[94.6 310.8 164.8 321.8]/Border[0 0 0]/A 125 0 R>>endobj +127 0 obj<</S/URI/URI(#LOGONPATH)>>endobj +128 0 obj<</Subtype/Link/Rect[94.6 278.4 148.6 289.4]/Border[0 0 0]/A 127 0 R>>endobj +129 0 obj<</S/URI/URI(#LOGONDRIVE)>>endobj +130 0 obj<</Subtype/Link/Rect[94.6 235.2 154.0 246.2]/Border[0 0 0]/A 129 0 R>>endobj +131 0 obj<</S/URI/URI(#LOGONHOME)>>endobj +132 0 obj<</Subtype/Link/Rect[94.6 224.4 148.6 235.4]/Border[0 0 0]/A 131 0 R>>endobj +133 0 obj<</S/URI/URI(#LOGONSCRIPT)>>endobj +134 0 obj<</Subtype/Link/Rect[94.6 181.2 159.4 192.2]/Border[0 0 0]/A 133 0 R>>endobj +135 0 obj<</S/URI/URI(#PATH)>>endobj +136 0 obj<</Subtype/Link/Rect[94.6 138.0 116.2 149.0]/Border[0 0 0]/A 135 0 R>>endobj +137 0 obj<</S/URI/URI(#WRITEABLE)>>endobj +138 0 obj<</Subtype/Link/Rect[94.6 127.2 143.2 138.2]/Border[0 0 0]/A 137 0 R>>endobj +139 0 obj<</S/URI/URI(#WRITELIST)>>endobj +140 0 obj<</Subtype/Link/Rect[94.6 116.4 148.6 127.4]/Border[0 0 0]/A 139 0 R>>endobj +141 0 obj<</S/URI/URI(#PATH)>>endobj +142 0 obj<</Subtype/Link/Rect[94.6 73.2 116.2 84.2]/Border[0 0 0]/A 141 0 R>>endobj +143 0 obj<</S/URI/URI(#WRITEABLE)>>endobj +144 0 obj<</Subtype/Link/Rect[94.6 62.4 143.2 73.4]/Border[0 0 0]/A 143 0 R>>endobj +145 0 obj[106 0 R +108 0 R +110 0 R +112 0 R +114 0 R +116 0 R +118 0 R +120 0 R +122 0 R +124 0 R +126 0 R +128 0 R +130 0 R +132 0 R +134 0 R +136 0 R +138 0 R +140 0 R +142 0 R +144 0 R ]endobj -152 0 obj<</S/URI/URI(#ADDUSERSCRIPT)>>endobj -153 0 obj<</Subtype/Link/Rect[304.2 707.8 371.1 720.8]/Border[0 0 0]/A 152 0 R>>endobj -154 0 obj[153 0 R +146 0 obj<</S/URI/URI(#CREATEMASK)>>endobj +147 0 obj<</Subtype/Link/Rect[94.6 722.0 154.0 733.0]/Border[0 0 0]/A 146 0 R>>endobj +148 0 obj<</S/URI/URI(#DIRECTORYMASK)>>endobj +149 0 obj<</Subtype/Link/Rect[94.6 711.2 170.2 722.2]/Border[0 0 0]/A 148 0 R>>endobj +150 0 obj<</S/URI/URI(ENCRYPTION.html)>>endobj +151 0 obj<</Subtype/Link/Rect[108.0 645.4 200.6 658.4]/Border[0 0 0]/A 150 0 R>>endobj +152 0 obj<</S/URI/URI(#DOMAINADMINUSERS)>>endobj +153 0 obj<</Subtype/Link/Rect[505.2 553.0 538.2 566.0]/Border[0 0 0]/A 152 0 R>>endobj +154 0 obj<</S/URI/URI(#DOMAINADMINUSERS)>>endobj +155 0 obj<</Subtype/Link/Rect[72.0 539.8 124.9 552.8]/Border[0 0 0]/A 154 0 R>>endobj +156 0 obj<</S/URI/URI(#DOMAINADMINGROUP)>>endobj +157 0 obj<</Subtype/Link/Rect[146.2 539.8 240.7 552.8]/Border[0 0 0]/A 156 0 R>>endobj +158 0 obj[147 0 R +149 0 R +151 0 R +153 0 R +155 0 R +157 0 R ]endobj -155 0 obj<</S/URI/URI(http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp)>>endobj -156 0 obj<</Subtype/Link/Rect[164.2 464.6 409.3 477.6]/Border[0 0 0]/A 155 0 R>>endobj -157 0 obj[156 0 R +159 0 obj<</S/URI/URI(smbpasswd.6.html)>>endobj +160 0 obj<</Subtype/Link/Rect[72.0 524.2 138.6 537.2]/Border[0 0 0]/A 159 0 R>>endobj +161 0 obj<</S/URI/URI(#ADDUSERSCRIPT)>>endobj +162 0 obj<</Subtype/Link/Rect[427.0 269.0 491.2 282.0]/Border[0 0 0]/A 161 0 R>>endobj +163 0 obj[160 0 R +162 0 R ]endobj -158 0 obj<</S/URI/URI(ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE)>>endobj -159 0 obj<</Subtype/Link/Rect[251.9 562.6 504.0 575.6]/Border[0 0 0]/A 158 0 R>>endobj -160 0 obj<</S/URI/URI(ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE)>>endobj -161 0 obj<</Subtype/Link/Rect[176.2 523.0 448.5 536.0]/Border[0 0 0]/A 160 0 R>>endobj -162 0 obj<</S/URI/URI(http://www.tcpdump.org/)>>endobj -163 0 obj<</Subtype/Link/Rect[316.1 121.4 422.1 134.4]/Border[0 0 0]/A 162 0 R>>endobj -164 0 obj<</S/URI/URI(http://www.ethereal.com/)>>endobj -165 0 obj<</Subtype/Link/Rect[343.3 108.2 452.6 121.2]/Border[0 0 0]/A 164 0 R>>endobj -166 0 obj[159 0 R -161 0 R -163 0 R -165 0 R +164 0 obj<</S/URI/URI(http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp)>>endobj +165 0 obj<</Subtype/Link/Rect[164.2 441.8 409.3 454.8]/Border[0 0 0]/A 164 0 R>>endobj +166 0 obj[165 0 R ]endobj -167 0 obj<</S/URI/URI(http://samba.org)>>endobj -168 0 obj<</Subtype/Link/Rect[200.3 161.0 274.8 174.0]/Border[0 0 0]/A 167 0 R>>endobj -169 0 obj<</S/URI/URI(http://www.skippy.net/linux/smb-howto.html)>>endobj -170 0 obj<</Subtype/Link/Rect[336.8 121.4 541.7 134.4]/Border[0 0 0]/A 169 0 R>>endobj -171 0 obj<</S/URI/URI(http://bioserve.latrobe.edu.au/samba)>>endobj -172 0 obj<</Subtype/Link/Rect[108.0 95.0 267.8 108.0]/Border[0 0 0]/A 171 0 R>>endobj -173 0 obj<</S/URI/URI(http://samba.org/cifs/)>>endobj -174 0 obj<</Subtype/Link/Rect[248.9 81.8 345.4 94.8]/Border[0 0 0]/A 173 0 R>>endobj -175 0 obj<</S/URI/URI(http://mailhost.cb1.com/~lkcl/ntdom/)>>endobj -176 0 obj<</Subtype/Link/Rect[208.2 68.6 375.2 81.6]/Border[0 0 0]/A 175 0 R>>endobj -177 0 obj[168 0 R +167 0 obj<</S/URI/URI(ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE)>>endobj +168 0 obj<</Subtype/Link/Rect[287.9 523.0 540.0 536.0]/Border[0 0 0]/A 167 0 R>>endobj +169 0 obj<</S/URI/URI(ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE)>>endobj +170 0 obj<</Subtype/Link/Rect[236.3 483.4 508.6 496.4]/Border[0 0 0]/A 169 0 R>>endobj +171 0 obj<</S/URI/URI(http://www.tcpdump.org/)>>endobj +172 0 obj<</Subtype/Link/Rect[352.1 68.6 458.1 81.6]/Border[0 0 0]/A 171 0 R>>endobj +173 0 obj[168 0 R 170 0 R 172 0 R -174 0 R -176 0 R ]endobj -178 0 obj<</S/URI/URI(ftp://ftp.microsoft.com/developr/drg/CIFS/)>>endobj -179 0 obj<</Subtype/Link/Rect[244.3 721.0 435.9 734.0]/Border[0 0 0]/A 178 0 R>>endobj -180 0 obj<</S/URI/URI(http://samba.org)>>endobj -181 0 obj<</Subtype/Link/Rect[325.0 623.0 396.8 636.0]/Border[0 0 0]/A 180 0 R>>endobj -182 0 obj<</S/URI/URI(http://www.samba-tng.org/)>>endobj -183 0 obj<</Subtype/Link/Rect[265.1 583.4 386.8 596.4]/Border[0 0 0]/A 182 0 R>>endobj -184 0 obj<</S/URI/URI(http://lists.samba.org/)>>endobj -185 0 obj<</Subtype/Link/Rect[72.0 161.0 164.3 174.0]/Border[0 0 0]/A 184 0 R>>endobj -186 0 obj<</S/URI/URI(http://lists.samba.org/mailman/roster/samba-ntdom)>>endobj -187 0 obj<</Subtype/Link/Rect[237.9 147.8 259.6 160.8]/Border[0 0 0]/A 186 0 R>>endobj -188 0 obj[179 0 R -181 0 R -183 0 R -185 0 R -187 0 R +174 0 obj<</S/URI/URI(http://www.ethereal.com/)>>endobj +175 0 obj<</Subtype/Link/Rect[435.5 721.0 544.9 734.0]/Border[0 0 0]/A 174 0 R>>endobj +176 0 obj<</S/URI/URI(http://samba.org)>>endobj +177 0 obj<</Subtype/Link/Rect[236.3 127.0 310.8 140.0]/Border[0 0 0]/A 176 0 R>>endobj +178 0 obj<</S/URI/URI(http://www.skippy.net/linux/smb-howto.html)>>endobj +179 0 obj<</Subtype/Link/Rect[144.0 74.2 346.1 87.2]/Border[0 0 0]/A 178 0 R>>endobj +180 0 obj[175 0 R +177 0 R +179 0 R ]endobj -189 0 obj<</S/URI/URI(#NTACLSUPPORT)>>endobj -190 0 obj<</Subtype/Link/Rect[342.7 533.8 441.7 546.8]/Border[0 0 0]/A 189 0 R>>endobj -191 0 obj[190 0 R +181 0 obj<</S/URI/URI(http://bioserve.latrobe.edu.au/samba)>>endobj +182 0 obj<</Subtype/Link/Rect[182.5 707.8 345.0 720.8]/Border[0 0 0]/A 181 0 R>>endobj +183 0 obj<</S/URI/URI(http://samba.org/cifs/)>>endobj +184 0 obj<</Subtype/Link/Rect[284.9 694.6 381.4 707.6]/Border[0 0 0]/A 183 0 R>>endobj +185 0 obj<</S/URI/URI(http://mailhost.cb1.com/~lkcl/ntdom/)>>endobj +186 0 obj<</Subtype/Link/Rect[244.2 681.4 411.2 694.4]/Border[0 0 0]/A 185 0 R>>endobj +187 0 obj<</S/URI/URI(ftp://ftp.microsoft.com/developr/drg/CIFS/)>>endobj +188 0 obj<</Subtype/Link/Rect[280.3 668.2 471.9 681.2]/Border[0 0 0]/A 187 0 R>>endobj +189 0 obj<</S/URI/URI(http://samba.org)>>endobj +190 0 obj<</Subtype/Link/Rect[361.0 615.4 432.8 628.4]/Border[0 0 0]/A 189 0 R>>endobj +191 0 obj<</S/URI/URI(http://www.samba-tng.org/)>>endobj +192 0 obj<</Subtype/Link/Rect[301.1 575.8 425.6 588.8]/Border[0 0 0]/A 191 0 R>>endobj +193 0 obj<</S/URI/URI(http://lists.samba.org/)>>endobj +194 0 obj<</Subtype/Link/Rect[135.5 140.2 227.8 153.2]/Border[0 0 0]/A 193 0 R>>endobj +195 0 obj<</S/URI/URI(http://lists.samba.org/mailman/roster/samba-ntdom)>>endobj +196 0 obj<</Subtype/Link/Rect[309.0 127.0 330.7 140.0]/Border[0 0 0]/A 195 0 R>>endobj +197 0 obj[182 0 R +184 0 R +186 0 R +188 0 R +190 0 R +192 0 R +194 0 R +196 0 R ]endobj -192 0 obj<</S/URI/URI(#SECURITYMASK)>>endobj -193 0 obj<</Subtype/Link/Rect[88.2 668.2 180.6 681.2]/Border[0 0 0]/A 192 0 R>>endobj -194 0 obj<</S/URI/URI(#CREATEMASK)>>endobj -195 0 obj<</Subtype/Link/Rect[358.9 589.0 438.1 602.0]/Border[0 0 0]/A 194 0 R>>endobj -196 0 obj<</S/URI/URI(#FORCESECURITYMODE)>>endobj -197 0 obj<</Subtype/Link/Rect[427.0 536.2 526.0 549.2]/Border[0 0 0]/A 196 0 R>>endobj -198 0 obj<</S/URI/URI(#FORCESECURITYMODE)>>endobj -199 0 obj<</Subtype/Link/Rect[72.0 523.0 98.4 536.0]/Border[0 0 0]/A 198 0 R>>endobj -200 0 obj<</S/URI/URI(#FORCECREATEMODE)>>endobj -201 0 obj<</Subtype/Link/Rect[358.9 443.8 477.7 456.8]/Border[0 0 0]/A 200 0 R>>endobj -202 0 obj<</S/URI/URI(smb.conf.5.html)>>endobj -203 0 obj<</Subtype/Link/Rect[72.0 166.6 151.2 179.6]/Border[0 0 0]/A 202 0 R>>endobj -204 0 obj[193 0 R -195 0 R -197 0 R -199 0 R -201 0 R -203 0 R +198 0 obj<</S/URI/URI(#NTACLSUPPORT)>>endobj +199 0 obj<</Subtype/Link/Rect[342.7 533.8 441.7 546.8]/Border[0 0 0]/A 198 0 R>>endobj +200 0 obj[199 0 R ]endobj -205 0 obj<</S/URI/URI(http://carol.wins.uva.nl/~leeuw/samba/warp.html)>>endobj -206 0 obj<</Subtype/Link/Rect[331.1 607.0 550.0 620.0]/Border[0 0 0]/A 205 0 R>>endobj -207 0 obj<</S/URI/URI(ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/)>>endobj -208 0 obj<</Subtype/Link/Rect[72.0 241.4 319.2 254.4]/Border[0 0 0]/A 207 0 R>>endobj -209 0 obj<</S/URI/URI(http://carol.wins.uva.nl/~leeuw/lanman.html)>>endobj -210 0 obj<</Subtype/Link/Rect[346.1 241.4 544.2 254.4]/Border[0 0 0]/A 209 0 R>>endobj -211 0 obj<</S/URI/URI(ftp://ftp.cdrom.com/pub/os2/network/ndis/)>>endobj -212 0 obj<</Subtype/Link/Rect[175.9 117.8 366.2 130.8]/Border[0 0 0]/A 211 0 R>>endobj -213 0 obj[206 0 R +201 0 obj<</S/URI/URI(#SECURITYMASK)>>endobj +202 0 obj<</Subtype/Link/Rect[88.2 668.2 180.6 681.2]/Border[0 0 0]/A 201 0 R>>endobj +203 0 obj<</S/URI/URI(#CREATEMASK)>>endobj +204 0 obj<</Subtype/Link/Rect[358.9 589.0 438.1 602.0]/Border[0 0 0]/A 203 0 R>>endobj +205 0 obj<</S/URI/URI(#FORCESECURITYMODE)>>endobj +206 0 obj<</Subtype/Link/Rect[427.0 536.2 526.0 549.2]/Border[0 0 0]/A 205 0 R>>endobj +207 0 obj<</S/URI/URI(#FORCESECURITYMODE)>>endobj +208 0 obj<</Subtype/Link/Rect[72.0 523.0 98.4 536.0]/Border[0 0 0]/A 207 0 R>>endobj +209 0 obj<</S/URI/URI(#FORCECREATEMODE)>>endobj +210 0 obj<</Subtype/Link/Rect[358.9 443.8 477.7 456.8]/Border[0 0 0]/A 209 0 R>>endobj +211 0 obj<</S/URI/URI(smb.conf.5.html)>>endobj +212 0 obj<</Subtype/Link/Rect[72.0 166.6 151.2 179.6]/Border[0 0 0]/A 211 0 R>>endobj +213 0 obj[202 0 R +204 0 R +206 0 R 208 0 R 210 0 R 212 0 R ]endobj -214 0 obj<</S/URI/URI(http://carol.wins.uva.nl/~leeuw/samba/fix.html)>>endobj -215 0 obj<</Subtype/Link/Rect[225.7 661.0 434.8 674.0]/Border[0 0 0]/A 214 0 R>>endobj -216 0 obj[215 0 R -]endobj -217 0 obj<</Subtype/Link/Rect[72.0 684.0 277.3 697.0]/Border[0 0 0]/Dest[413 0 R/XYZ null 798 0]>>endobj -218 0 obj<</Subtype/Link/Rect[108.0 670.8 249.2 683.8]/Border[0 0 0]/Dest[413 0 R/XYZ null 730 0]>>endobj -219 0 obj<</Subtype/Link/Rect[108.0 657.6 255.0 670.6]/Border[0 0 0]/Dest[413 0 R/XYZ null 593 0]>>endobj -220 0 obj<</Subtype/Link/Rect[108.0 644.4 257.7 657.4]/Border[0 0 0]/Dest[413 0 R/XYZ null 178 0]>>endobj -221 0 obj<</Subtype/Link/Rect[108.0 631.2 309.0 644.2]/Border[0 0 0]/Dest[416 0 R/XYZ null 739 0]>>endobj -222 0 obj<</Subtype/Link/Rect[108.0 618.0 316.7 631.0]/Border[0 0 0]/Dest[416 0 R/XYZ null 379 0]>>endobj -223 0 obj<</Subtype/Link/Rect[108.0 604.8 284.9 617.8]/Border[0 0 0]/Dest[416 0 R/XYZ null 268 0]>>endobj -224 0 obj<</Subtype/Link/Rect[108.0 591.6 280.0 604.6]/Border[0 0 0]/Dest[419 0 R/XYZ null 768 0]>>endobj -225 0 obj<</Subtype/Link/Rect[108.0 578.4 328.6 591.4]/Border[0 0 0]/Dest[419 0 R/XYZ null 266 0]>>endobj -226 0 obj<</Subtype/Link/Rect[108.0 565.2 364.9 578.2]/Border[0 0 0]/Dest[422 0 R/XYZ null 686 0]>>endobj -227 0 obj<</Subtype/Link/Rect[108.0 552.0 315.8 565.0]/Border[0 0 0]/Dest[422 0 R/XYZ null 509 0]>>endobj -228 0 obj<</Subtype/Link/Rect[108.0 538.8 514.3 551.8]/Border[0 0 0]/Dest[422 0 R/XYZ null 332 0]>>endobj -229 0 obj<</Subtype/Link/Rect[108.0 525.6 259.4 538.6]/Border[0 0 0]/Dest[425 0 R/XYZ null 768 0]>>endobj -230 0 obj<</Subtype/Link/Rect[108.0 512.4 236.0 525.4]/Border[0 0 0]/Dest[425 0 R/XYZ null 577 0]>>endobj -231 0 obj<</Subtype/Link/Rect[108.0 499.2 186.5 512.2]/Border[0 0 0]/Dest[425 0 R/XYZ null 505 0]>>endobj -232 0 obj<</Subtype/Link/Rect[108.0 486.0 267.2 499.0]/Border[0 0 0]/Dest[425 0 R/XYZ null 394 0]>>endobj -233 0 obj<</Subtype/Link/Rect[108.0 472.8 295.6 485.8]/Border[0 0 0]/Dest[428 0 R/XYZ null 739 0]>>endobj -234 0 obj<</Subtype/Link/Rect[108.0 459.6 177.7 472.6]/Border[0 0 0]/Dest[428 0 R/XYZ null 615 0]>>endobj -235 0 obj<</Subtype/Link/Rect[108.0 446.4 232.3 459.4]/Border[0 0 0]/Dest[431 0 R/XYZ null 768 0]>>endobj -236 0 obj<</Subtype/Link/Rect[108.0 433.2 232.6 446.2]/Border[0 0 0]/Dest[431 0 R/XYZ null 683 0]>>endobj -237 0 obj<</Subtype/Link/Rect[72.0 406.8 371.8 419.8]/Border[0 0 0]/Dest[434 0 R/XYZ null 798 0]>>endobj -238 0 obj<</Subtype/Link/Rect[108.0 393.6 181.6 406.6]/Border[0 0 0]/Dest[434 0 R/XYZ null 706 0]>>endobj -239 0 obj<</Subtype/Link/Rect[108.0 380.4 210.7 393.4]/Border[0 0 0]/Dest[434 0 R/XYZ null 569 0]>>endobj -240 0 obj<</Subtype/Link/Rect[108.0 367.2 268.7 380.2]/Border[0 0 0]/Dest[437 0 R/XYZ null 699 0]>>endobj -241 0 obj<</Subtype/Link/Rect[108.0 354.0 277.0 367.0]/Border[0 0 0]/Dest[437 0 R/XYZ null 220 0]>>endobj -242 0 obj<</Subtype/Link/Rect[108.0 340.8 316.7 353.8]/Border[0 0 0]/Dest[440 0 R/XYZ null 768 0]>>endobj -243 0 obj<</Subtype/Link/Rect[108.0 327.6 215.2 340.6]/Border[0 0 0]/Dest[440 0 R/XYZ null 656 0]>>endobj -244 0 obj<</Subtype/Link/Rect[108.0 314.4 246.4 327.4]/Border[0 0 0]/Dest[443 0 R/XYZ null 399 0]>>endobj -245 0 obj<</Subtype/Link/Rect[108.0 301.2 362.5 314.2]/Border[0 0 0]/Dest[446 0 R/XYZ null 475 0]>>endobj -246 0 obj<</Subtype/Link/Rect[72.0 274.8 402.3 287.8]/Border[0 0 0]/Dest[449 0 R/XYZ null 798 0]>>endobj -247 0 obj<</Subtype/Link/Rect[108.0 261.6 179.2 274.6]/Border[0 0 0]/Dest[449 0 R/XYZ null 706 0]>>endobj -248 0 obj<</Subtype/Link/Rect[108.0 248.4 161.2 261.4]/Border[0 0 0]/Dest[452 0 R/XYZ null 673 0]>>endobj -249 0 obj<</Subtype/Link/Rect[72.0 222.0 277.1 235.0]/Border[0 0 0]/Dest[455 0 R/XYZ null 798 0]>>endobj -250 0 obj<</Subtype/Link/Rect[108.0 208.8 181.6 221.8]/Border[0 0 0]/Dest[455 0 R/XYZ null 730 0]>>endobj -251 0 obj<</Subtype/Link/Rect[108.0 195.6 189.0 208.6]/Border[0 0 0]/Dest[455 0 R/XYZ null 474 0]>>endobj -252 0 obj<</Subtype/Link/Rect[108.0 182.4 209.7 195.4]/Border[0 0 0]/Dest[455 0 R/XYZ null 244 0]>>endobj -253 0 obj<</Subtype/Link/Rect[108.0 169.2 294.4 182.2]/Border[0 0 0]/Dest[461 0 R/XYZ null 768 0]>>endobj -254 0 obj<</Subtype/Link/Rect[108.0 156.0 287.3 169.0]/Border[0 0 0]/Dest[461 0 R/XYZ null 445 0]>>endobj -255 0 obj<</Subtype/Link/Rect[108.0 142.8 350.9 155.8]/Border[0 0 0]/Dest[464 0 R/XYZ null 727 0]>>endobj -256 0 obj<</Subtype/Link/Rect[108.0 129.6 242.1 142.6]/Border[0 0 0]/Dest[464 0 R/XYZ null 444 0]>>endobj -257 0 obj<</Subtype/Link/Rect[108.0 116.4 220.1 129.4]/Border[0 0 0]/Dest[464 0 R/XYZ null 254 0]>>endobj -258 0 obj<</Subtype/Link/Rect[108.0 103.2 214.3 116.2]/Border[0 0 0]/Dest[467 0 R/XYZ null 768 0]>>endobj -259 0 obj<</Subtype/Link/Rect[108.0 90.0 281.2 103.0]/Border[0 0 0]/Dest[467 0 R/XYZ null 630 0]>>endobj -260 0 obj<</Subtype/Link/Rect[108.0 76.8 222.3 89.8]/Border[0 0 0]/Dest[467 0 R/XYZ null 532 0]>>endobj -261 0 obj<</Subtype/Link/Rect[108.0 63.6 234.5 76.6]/Border[0 0 0]/Dest[467 0 R/XYZ null 421 0]>>endobj -262 0 obj[217 0 R -218 0 R +214 0 obj<</S/URI/URI(http://carol.wins.uva.nl/~leeuw/samba/warp.html)>>endobj +215 0 obj<</Subtype/Link/Rect[331.1 607.0 550.0 620.0]/Border[0 0 0]/A 214 0 R>>endobj +216 0 obj<</S/URI/URI(ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/)>>endobj +217 0 obj<</Subtype/Link/Rect[72.0 241.4 319.2 254.4]/Border[0 0 0]/A 216 0 R>>endobj +218 0 obj<</S/URI/URI(http://carol.wins.uva.nl/~leeuw/lanman.html)>>endobj +219 0 obj<</Subtype/Link/Rect[346.1 241.4 544.2 254.4]/Border[0 0 0]/A 218 0 R>>endobj +220 0 obj<</S/URI/URI(ftp://ftp.cdrom.com/pub/os2/network/ndis/)>>endobj +221 0 obj<</Subtype/Link/Rect[175.9 117.8 366.2 130.8]/Border[0 0 0]/A 220 0 R>>endobj +222 0 obj[215 0 R +217 0 R 219 0 R -220 0 R 221 0 R -222 0 R -223 0 R -224 0 R -225 0 R -226 0 R -227 0 R -228 0 R +]endobj +223 0 obj<</S/URI/URI(http://carol.wins.uva.nl/~leeuw/samba/fix.html)>>endobj +224 0 obj<</Subtype/Link/Rect[225.7 661.0 434.8 674.0]/Border[0 0 0]/A 223 0 R>>endobj +225 0 obj[224 0 R +]endobj +226 0 obj<</S/URI/URI(http://samba.org/samba/cvs.html)>>endobj +227 0 obj<</Subtype/Link/Rect[357.1 577.0 500.7 590.0]/Border[0 0 0]/A 226 0 R>>endobj +228 0 obj<</S/URI/URI(http://samba.org/cgi-bin/cvsweb)>>endobj +229 0 obj<</Subtype/Link/Rect[138.6 354.6 283.2 367.6]/Border[0 0 0]/A 228 0 R>>endobj +230 0 obj<</S/URI/URI(http://www.cyclic.com/)>>endobj +231 0 obj<</Subtype/Link/Rect[394.3 230.2 498.2 243.2]/Border[0 0 0]/A 230 0 R>>endobj +232 0 obj[227 0 R 229 0 R -230 0 R 231 0 R -232 0 R -233 0 R +]endobj +233 0 obj<</Subtype/Link/Rect[72.0 684.0 277.3 697.0]/Border[0 0 0]/Dest[454 0 R/XYZ null 798 0]>>endobj +234 0 obj<</Subtype/Link/Rect[108.0 670.8 249.2 683.8]/Border[0 0 0]/Dest[454 0 R/XYZ null 730 0]>>endobj +235 0 obj<</Subtype/Link/Rect[108.0 657.6 255.0 670.6]/Border[0 0 0]/Dest[454 0 R/XYZ null 593 0]>>endobj +236 0 obj<</Subtype/Link/Rect[108.0 644.4 257.7 657.4]/Border[0 0 0]/Dest[454 0 R/XYZ null 178 0]>>endobj +237 0 obj<</Subtype/Link/Rect[108.0 631.2 309.0 644.2]/Border[0 0 0]/Dest[457 0 R/XYZ null 739 0]>>endobj +238 0 obj<</Subtype/Link/Rect[108.0 618.0 316.7 631.0]/Border[0 0 0]/Dest[457 0 R/XYZ null 379 0]>>endobj +239 0 obj<</Subtype/Link/Rect[108.0 604.8 284.9 617.8]/Border[0 0 0]/Dest[457 0 R/XYZ null 268 0]>>endobj +240 0 obj<</Subtype/Link/Rect[108.0 591.6 280.0 604.6]/Border[0 0 0]/Dest[460 0 R/XYZ null 768 0]>>endobj +241 0 obj<</Subtype/Link/Rect[108.0 578.4 328.6 591.4]/Border[0 0 0]/Dest[460 0 R/XYZ null 266 0]>>endobj +242 0 obj<</Subtype/Link/Rect[108.0 565.2 364.9 578.2]/Border[0 0 0]/Dest[463 0 R/XYZ null 686 0]>>endobj +243 0 obj<</Subtype/Link/Rect[108.0 552.0 315.8 565.0]/Border[0 0 0]/Dest[463 0 R/XYZ null 509 0]>>endobj +244 0 obj<</Subtype/Link/Rect[108.0 538.8 514.3 551.8]/Border[0 0 0]/Dest[463 0 R/XYZ null 332 0]>>endobj +245 0 obj<</Subtype/Link/Rect[108.0 525.6 259.4 538.6]/Border[0 0 0]/Dest[466 0 R/XYZ null 768 0]>>endobj +246 0 obj<</Subtype/Link/Rect[108.0 512.4 236.0 525.4]/Border[0 0 0]/Dest[466 0 R/XYZ null 577 0]>>endobj +247 0 obj<</Subtype/Link/Rect[108.0 499.2 186.5 512.2]/Border[0 0 0]/Dest[466 0 R/XYZ null 505 0]>>endobj +248 0 obj<</Subtype/Link/Rect[108.0 486.0 267.2 499.0]/Border[0 0 0]/Dest[466 0 R/XYZ null 394 0]>>endobj +249 0 obj<</Subtype/Link/Rect[108.0 472.8 295.6 485.8]/Border[0 0 0]/Dest[469 0 R/XYZ null 739 0]>>endobj +250 0 obj<</Subtype/Link/Rect[108.0 459.6 177.7 472.6]/Border[0 0 0]/Dest[469 0 R/XYZ null 615 0]>>endobj +251 0 obj<</Subtype/Link/Rect[108.0 446.4 232.3 459.4]/Border[0 0 0]/Dest[472 0 R/XYZ null 768 0]>>endobj +252 0 obj<</Subtype/Link/Rect[108.0 433.2 232.6 446.2]/Border[0 0 0]/Dest[472 0 R/XYZ null 683 0]>>endobj +253 0 obj<</Subtype/Link/Rect[72.0 406.8 371.8 419.8]/Border[0 0 0]/Dest[475 0 R/XYZ null 798 0]>>endobj +254 0 obj<</Subtype/Link/Rect[108.0 393.6 181.6 406.6]/Border[0 0 0]/Dest[475 0 R/XYZ null 706 0]>>endobj +255 0 obj<</Subtype/Link/Rect[108.0 380.4 210.7 393.4]/Border[0 0 0]/Dest[475 0 R/XYZ null 569 0]>>endobj +256 0 obj<</Subtype/Link/Rect[108.0 367.2 268.7 380.2]/Border[0 0 0]/Dest[478 0 R/XYZ null 699 0]>>endobj +257 0 obj<</Subtype/Link/Rect[108.0 354.0 277.0 367.0]/Border[0 0 0]/Dest[478 0 R/XYZ null 220 0]>>endobj +258 0 obj<</Subtype/Link/Rect[108.0 340.8 316.7 353.8]/Border[0 0 0]/Dest[481 0 R/XYZ null 768 0]>>endobj +259 0 obj<</Subtype/Link/Rect[108.0 327.6 215.2 340.6]/Border[0 0 0]/Dest[481 0 R/XYZ null 656 0]>>endobj +260 0 obj<</Subtype/Link/Rect[108.0 314.4 246.4 327.4]/Border[0 0 0]/Dest[484 0 R/XYZ null 399 0]>>endobj +261 0 obj<</Subtype/Link/Rect[108.0 301.2 362.5 314.2]/Border[0 0 0]/Dest[487 0 R/XYZ null 475 0]>>endobj +262 0 obj<</Subtype/Link/Rect[72.0 274.8 402.3 287.8]/Border[0 0 0]/Dest[490 0 R/XYZ null 798 0]>>endobj +263 0 obj<</Subtype/Link/Rect[108.0 261.6 179.2 274.6]/Border[0 0 0]/Dest[490 0 R/XYZ null 706 0]>>endobj +264 0 obj<</Subtype/Link/Rect[108.0 248.4 161.2 261.4]/Border[0 0 0]/Dest[493 0 R/XYZ null 673 0]>>endobj +265 0 obj<</Subtype/Link/Rect[72.0 222.0 277.1 235.0]/Border[0 0 0]/Dest[496 0 R/XYZ null 798 0]>>endobj +266 0 obj<</Subtype/Link/Rect[108.0 208.8 181.6 221.8]/Border[0 0 0]/Dest[496 0 R/XYZ null 730 0]>>endobj +267 0 obj<</Subtype/Link/Rect[108.0 195.6 189.0 208.6]/Border[0 0 0]/Dest[496 0 R/XYZ null 302 0]>>endobj +268 0 obj<</Subtype/Link/Rect[108.0 182.4 209.7 195.4]/Border[0 0 0]/Dest[499 0 R/XYZ null 693 0]>>endobj +269 0 obj<</Subtype/Link/Rect[108.0 169.2 294.4 182.2]/Border[0 0 0]/Dest[502 0 R/XYZ null 542 0]>>endobj +270 0 obj<</Subtype/Link/Rect[108.0 156.0 287.3 169.0]/Border[0 0 0]/Dest[505 0 R/XYZ null 768 0]>>endobj +271 0 obj<</Subtype/Link/Rect[108.0 142.8 350.9 155.8]/Border[0 0 0]/Dest[505 0 R/XYZ null 383 0]>>endobj +272 0 obj<</Subtype/Link/Rect[108.0 129.6 242.1 142.6]/Border[0 0 0]/Dest[508 0 R/XYZ null 768 0]>>endobj +273 0 obj<</Subtype/Link/Rect[108.0 116.4 220.1 129.4]/Border[0 0 0]/Dest[508 0 R/XYZ null 577 0]>>endobj +274 0 obj<</Subtype/Link/Rect[108.0 103.2 214.3 116.2]/Border[0 0 0]/Dest[508 0 R/XYZ null 466 0]>>endobj +275 0 obj<</Subtype/Link/Rect[108.0 90.0 281.2 103.0]/Border[0 0 0]/Dest[508 0 R/XYZ null 328 0]>>endobj +276 0 obj<</Subtype/Link/Rect[108.0 76.8 222.3 89.8]/Border[0 0 0]/Dest[508 0 R/XYZ null 230 0]>>endobj +277 0 obj<</Subtype/Link/Rect[108.0 63.6 234.5 76.6]/Border[0 0 0]/Dest[511 0 R/XYZ null 768 0]>>endobj +278 0 obj[233 0 R 234 0 R 235 0 R 236 0 R @@ -397,51 +404,8 @@ 259 0 R 260 0 R 261 0 R -]endobj -263 0 obj<</Subtype/Link/Rect[108.0 684.0 302.9 697.0]/Border[0 0 0]/Dest[470 0 R/XYZ null 528 0]>>endobj -264 0 obj<</Subtype/Link/Rect[72.0 657.6 272.9 670.6]/Border[0 0 0]/Dest[473 0 R/XYZ null 798 0]>>endobj -265 0 obj<</Subtype/Link/Rect[108.0 644.4 299.9 657.4]/Border[0 0 0]/Dest[473 0 R/XYZ null 730 0]>>endobj -266 0 obj<</Subtype/Link/Rect[108.0 631.2 288.0 644.2]/Border[0 0 0]/Dest[476 0 R/XYZ null 356 0]>>endobj -267 0 obj<</Subtype/Link/Rect[108.0 618.0 307.9 631.0]/Border[0 0 0]/Dest[479 0 R/XYZ null 768 0]>>endobj -268 0 obj<</Subtype/Link/Rect[72.0 591.6 424.6 604.6]/Border[0 0 0]/Dest[482 0 R/XYZ null 798 0]>>endobj -269 0 obj<</Subtype/Link/Rect[108.0 578.4 181.0 591.4]/Border[0 0 0]/Dest[482 0 R/XYZ null 706 0]>>endobj -270 0 obj<</Subtype/Link/Rect[108.0 565.2 316.1 578.2]/Border[0 0 0]/Dest[485 0 R/XYZ null 768 0]>>endobj -271 0 obj<</Subtype/Link/Rect[108.0 552.0 432.8 565.0]/Border[0 0 0]/Dest[488 0 R/XYZ null 647 0]>>endobj -272 0 obj<</Subtype/Link/Rect[108.0 538.8 261.4 551.8]/Border[0 0 0]/Dest[491 0 R/XYZ null 621 0]>>endobj -273 0 obj<</Subtype/Link/Rect[108.0 525.6 252.8 538.6]/Border[0 0 0]/Dest[494 0 R/XYZ null 567 0]>>endobj -274 0 obj<</Subtype/Link/Rect[108.0 512.4 246.4 525.4]/Border[0 0 0]/Dest[497 0 R/XYZ null 528 0]>>endobj -275 0 obj<</Subtype/Link/Rect[108.0 499.2 213.7 512.2]/Border[0 0 0]/Dest[500 0 R/XYZ null 237 0]>>endobj -276 0 obj<</Subtype/Link/Rect[108.0 486.0 194.5 499.0]/Border[0 0 0]/Dest[503 0 R/XYZ null 726 0]>>endobj -277 0 obj<</Subtype/Link/Rect[108.0 472.8 431.0 485.8]/Border[0 0 0]/Dest[506 0 R/XYZ null 768 0]>>endobj -278 0 obj<</Subtype/Link/Rect[72.0 446.4 423.1 459.4]/Border[0 0 0]/Dest[512 0 R/XYZ null 798 0]>>endobj -279 0 obj<</Subtype/Link/Rect[108.0 433.2 164.5 446.2]/Border[0 0 0]/Dest[512 0 R/XYZ null 706 0]>>endobj -280 0 obj<</Subtype/Link/Rect[108.0 420.0 181.6 433.0]/Border[0 0 0]/Dest[512 0 R/XYZ null 569 0]>>endobj -281 0 obj<</Subtype/Link/Rect[108.0 406.8 233.6 419.8]/Border[0 0 0]/Dest[512 0 R/XYZ null 246 0]>>endobj -282 0 obj<</Subtype/Link/Rect[108.0 393.6 188.3 406.6]/Border[0 0 0]/Dest[515 0 R/XYZ null 581 0]>>endobj -283 0 obj<</Subtype/Link/Rect[108.0 380.4 222.0 393.4]/Border[0 0 0]/Dest[515 0 R/XYZ null 417 0]>>endobj -284 0 obj<</Subtype/Link/Rect[108.0 367.2 288.6 380.2]/Border[0 0 0]/Dest[515 0 R/XYZ null 292 0]>>endobj -285 0 obj<</Subtype/Link/Rect[108.0 354.0 230.8 367.0]/Border[0 0 0]/Dest[518 0 R/XYZ null 768 0]>>endobj -286 0 obj<</Subtype/Link/Rect[108.0 340.8 288.9 353.8]/Border[0 0 0]/Dest[518 0 R/XYZ null 326 0]>>endobj -287 0 obj<</Subtype/Link/Rect[108.0 327.6 269.3 340.6]/Border[0 0 0]/Dest[521 0 R/XYZ null 686 0]>>endobj -288 0 obj<</Subtype/Link/Rect[108.0 314.4 203.0 327.4]/Border[0 0 0]/Dest[521 0 R/XYZ null 496 0]>>endobj -289 0 obj<</Subtype/Link/Rect[108.0 301.2 259.9 314.2]/Border[0 0 0]/Dest[521 0 R/XYZ null 345 0]>>endobj -290 0 obj<</Subtype/Link/Rect[108.0 288.0 178.0 301.0]/Border[0 0 0]/Dest[521 0 R/XYZ null 155 0]>>endobj -291 0 obj<</Subtype/Link/Rect[108.0 274.8 177.4 287.8]/Border[0 0 0]/Dest[524 0 R/XYZ null 581 0]>>endobj -292 0 obj<</Subtype/Link/Rect[72.0 248.4 413.9 261.4]/Border[0 0 0]/Dest[527 0 R/XYZ null 798 0]>>endobj -293 0 obj<</Subtype/Link/Rect[108.0 235.2 447.4 248.2]/Border[0 0 0]/Dest[527 0 R/XYZ null 706 0]>>endobj -294 0 obj<</Subtype/Link/Rect[108.0 222.0 319.1 235.0]/Border[0 0 0]/Dest[527 0 R/XYZ null 525 0]>>endobj -295 0 obj<</Subtype/Link/Rect[108.0 208.8 231.1 221.8]/Border[0 0 0]/Dest[527 0 R/XYZ null 348 0]>>endobj -296 0 obj<</Subtype/Link/Rect[108.0 195.6 292.2 208.6]/Border[0 0 0]/Dest[530 0 R/XYZ null 686 0]>>endobj -297 0 obj<</Subtype/Link/Rect[108.0 182.4 208.5 195.4]/Border[0 0 0]/Dest[530 0 R/XYZ null 443 0]>>endobj -298 0 obj<</Subtype/Link/Rect[108.0 169.2 233.6 182.2]/Border[0 0 0]/Dest[530 0 R/XYZ null 187 0]>>endobj -299 0 obj<</Subtype/Link/Rect[108.0 156.0 301.4 169.0]/Border[0 0 0]/Dest[533 0 R/XYZ null 673 0]>>endobj -300 0 obj<</Subtype/Link/Rect[108.0 142.8 394.8 155.8]/Border[0 0 0]/Dest[533 0 R/XYZ null 232 0]>>endobj -301 0 obj<</Subtype/Link/Rect[108.0 129.6 386.9 142.6]/Border[0 0 0]/Dest[539 0 R/XYZ null 594 0]>>endobj -302 0 obj<</Subtype/Link/Rect[72.0 103.2 223.3 116.2]/Border[0 0 0]/Dest[542 0 R/XYZ null 798 0]>>endobj -303 0 obj<</Subtype/Link/Rect[108.0 90.0 153.5 103.0]/Border[0 0 0]/Dest[542 0 R/XYZ null 730 0]>>endobj -304 0 obj<</Subtype/Link/Rect[108.0 76.8 493.5 89.8]/Border[0 0 0]/Dest[542 0 R/XYZ null 700 0]>>endobj -305 0 obj<</Subtype/Link/Rect[108.0 63.6 498.7 76.6]/Border[0 0 0]/Dest[542 0 R/XYZ null 348 0]>>endobj -306 0 obj[263 0 R +262 0 R +263 0 R 264 0 R 265 0 R 266 0 R @@ -456,8 +420,51 @@ 275 0 R 276 0 R 277 0 R -278 0 R -279 0 R +]endobj +279 0 obj<</Subtype/Link/Rect[108.0 684.0 300.2 697.0]/Border[0 0 0]/Dest[511 0 R/XYZ null 191 0]>>endobj +280 0 obj<</Subtype/Link/Rect[72.0 657.6 272.9 670.6]/Border[0 0 0]/Dest[517 0 R/XYZ null 798 0]>>endobj +281 0 obj<</Subtype/Link/Rect[108.0 644.4 299.9 657.4]/Border[0 0 0]/Dest[517 0 R/XYZ null 730 0]>>endobj +282 0 obj<</Subtype/Link/Rect[108.0 631.2 288.0 644.2]/Border[0 0 0]/Dest[520 0 R/XYZ null 356 0]>>endobj +283 0 obj<</Subtype/Link/Rect[108.0 618.0 307.9 631.0]/Border[0 0 0]/Dest[523 0 R/XYZ null 768 0]>>endobj +284 0 obj<</Subtype/Link/Rect[72.0 591.6 416.3 604.6]/Border[0 0 0]/Dest[526 0 R/XYZ null 798 0]>>endobj +285 0 obj<</Subtype/Link/Rect[108.0 578.4 219.2 591.4]/Border[0 0 0]/Dest[526 0 R/XYZ null 706 0]>>endobj +286 0 obj<</Subtype/Link/Rect[108.0 565.2 181.0 578.2]/Border[0 0 0]/Dest[526 0 R/XYZ null 608 0]>>endobj +287 0 obj<</Subtype/Link/Rect[108.0 552.0 316.1 565.0]/Border[0 0 0]/Dest[529 0 R/XYZ null 660 0]>>endobj +288 0 obj<</Subtype/Link/Rect[108.0 538.8 432.8 551.8]/Border[0 0 0]/Dest[532 0 R/XYZ null 531 0]>>endobj +289 0 obj<</Subtype/Link/Rect[108.0 525.6 319.4 538.6]/Border[0 0 0]/Dest[532 0 R/XYZ null 196 0]>>endobj +290 0 obj<</Subtype/Link/Rect[108.0 512.4 330.8 525.4]/Border[0 0 0]/Dest[535 0 R/XYZ null 359 0]>>endobj +291 0 obj<</Subtype/Link/Rect[108.0 499.2 261.4 512.2]/Border[0 0 0]/Dest[535 0 R/XYZ null 183 0]>>endobj +292 0 obj<</Subtype/Link/Rect[108.0 486.0 252.8 499.0]/Border[0 0 0]/Dest[541 0 R/XYZ null 545 0]>>endobj +293 0 obj<</Subtype/Link/Rect[108.0 472.8 246.4 485.8]/Border[0 0 0]/Dest[544 0 R/XYZ null 488 0]>>endobj +294 0 obj<</Subtype/Link/Rect[108.0 459.6 292.9 472.6]/Border[0 0 0]/Dest[553 0 R/XYZ null 768 0]>>endobj +295 0 obj<</Subtype/Link/Rect[108.0 446.4 332.0 459.4]/Border[0 0 0]/Dest[556 0 R/XYZ null 435 0]>>endobj +296 0 obj<</Subtype/Link/Rect[108.0 433.2 406.2 446.2]/Border[0 0 0]/Dest[559 0 R/XYZ null 189 0]>>endobj +297 0 obj<</Subtype/Link/Rect[108.0 420.0 431.0 433.0]/Border[0 0 0]/Dest[574 0 R/XYZ null 686 0]>>endobj +298 0 obj<</Subtype/Link/Rect[72.0 393.6 423.1 406.6]/Border[0 0 0]/Dest[580 0 R/XYZ null 798 0]>>endobj +299 0 obj<</Subtype/Link/Rect[108.0 380.4 164.5 393.4]/Border[0 0 0]/Dest[580 0 R/XYZ null 706 0]>>endobj +300 0 obj<</Subtype/Link/Rect[108.0 367.2 181.6 380.2]/Border[0 0 0]/Dest[580 0 R/XYZ null 569 0]>>endobj +301 0 obj<</Subtype/Link/Rect[108.0 354.0 233.6 367.0]/Border[0 0 0]/Dest[580 0 R/XYZ null 246 0]>>endobj +302 0 obj<</Subtype/Link/Rect[108.0 340.8 188.3 353.8]/Border[0 0 0]/Dest[583 0 R/XYZ null 581 0]>>endobj +303 0 obj<</Subtype/Link/Rect[108.0 327.6 222.0 340.6]/Border[0 0 0]/Dest[583 0 R/XYZ null 417 0]>>endobj +304 0 obj<</Subtype/Link/Rect[108.0 314.4 288.6 327.4]/Border[0 0 0]/Dest[583 0 R/XYZ null 292 0]>>endobj +305 0 obj<</Subtype/Link/Rect[108.0 301.2 230.8 314.2]/Border[0 0 0]/Dest[586 0 R/XYZ null 768 0]>>endobj +306 0 obj<</Subtype/Link/Rect[108.0 288.0 288.9 301.0]/Border[0 0 0]/Dest[586 0 R/XYZ null 326 0]>>endobj +307 0 obj<</Subtype/Link/Rect[108.0 274.8 269.3 287.8]/Border[0 0 0]/Dest[589 0 R/XYZ null 686 0]>>endobj +308 0 obj<</Subtype/Link/Rect[108.0 261.6 203.0 274.6]/Border[0 0 0]/Dest[589 0 R/XYZ null 496 0]>>endobj +309 0 obj<</Subtype/Link/Rect[108.0 248.4 259.9 261.4]/Border[0 0 0]/Dest[589 0 R/XYZ null 345 0]>>endobj +310 0 obj<</Subtype/Link/Rect[108.0 235.2 178.0 248.2]/Border[0 0 0]/Dest[589 0 R/XYZ null 155 0]>>endobj +311 0 obj<</Subtype/Link/Rect[108.0 222.0 177.4 235.0]/Border[0 0 0]/Dest[592 0 R/XYZ null 581 0]>>endobj +312 0 obj<</Subtype/Link/Rect[72.0 195.6 413.9 208.6]/Border[0 0 0]/Dest[595 0 R/XYZ null 798 0]>>endobj +313 0 obj<</Subtype/Link/Rect[108.0 182.4 447.4 195.4]/Border[0 0 0]/Dest[595 0 R/XYZ null 706 0]>>endobj +314 0 obj<</Subtype/Link/Rect[108.0 169.2 319.1 182.2]/Border[0 0 0]/Dest[595 0 R/XYZ null 525 0]>>endobj +315 0 obj<</Subtype/Link/Rect[108.0 156.0 231.1 169.0]/Border[0 0 0]/Dest[595 0 R/XYZ null 348 0]>>endobj +316 0 obj<</Subtype/Link/Rect[108.0 142.8 292.2 155.8]/Border[0 0 0]/Dest[598 0 R/XYZ null 686 0]>>endobj +317 0 obj<</Subtype/Link/Rect[108.0 129.6 208.5 142.6]/Border[0 0 0]/Dest[598 0 R/XYZ null 443 0]>>endobj +318 0 obj<</Subtype/Link/Rect[108.0 116.4 233.6 129.4]/Border[0 0 0]/Dest[598 0 R/XYZ null 187 0]>>endobj +319 0 obj<</Subtype/Link/Rect[108.0 103.2 301.4 116.2]/Border[0 0 0]/Dest[601 0 R/XYZ null 673 0]>>endobj +320 0 obj<</Subtype/Link/Rect[108.0 90.0 394.8 103.0]/Border[0 0 0]/Dest[601 0 R/XYZ null 232 0]>>endobj +321 0 obj<</Subtype/Link/Rect[108.0 76.8 386.9 89.8]/Border[0 0 0]/Dest[607 0 R/XYZ null 594 0]>>endobj +322 0 obj[279 0 R 280 0 R 281 0 R 282 0 R @@ -484,184 +491,245 @@ 303 0 R 304 0 R 305 0 R -]endobj -307 0 obj<</Subtype/Link/Rect[108.0 684.0 450.2 697.0]/Border[0 0 0]/Dest[545 0 R/XYZ null 768 0]>>endobj -308 0 obj<</Subtype/Link/Rect[108.0 670.8 419.9 683.8]/Border[0 0 0]/Dest[545 0 R/XYZ null 639 0]>>endobj -309 0 obj[307 0 R +306 0 R +307 0 R 308 0 R +309 0 R +310 0 R +311 0 R +312 0 R +313 0 R +314 0 R +315 0 R +316 0 R +317 0 R +318 0 R +319 0 R +320 0 R +321 0 R ]endobj -310 0 obj<</Dests 311 0 R>>endobj -311 0 obj<</Kids[312 0 R]>>endobj -312 0 obj<</Limits[(aen1011)(smbpasswdfileformat)]/Names[(aen1011)313 0 R(aen1050)314 0 R(aen1074)315 0 R(aen1092)316 0 R(aen1096)317 0 R(aen1109)318 0 R(aen1116)319 0 R(aen1120)320 0 R(aen1125)321 0 R(aen1129)322 0 R(aen1145)323 0 R(aen1153)324 0 R(aen1157)325 0 R(aen116)326 0 R(aen1160)327 0 R(aen1166)328 0 R(aen1178)329 0 R(aen1181)330 0 R(aen1192)331 0 R(aen1201)332 0 R(aen1212)333 0 R(aen1232)334 0 R(aen1247)335 0 R(aen1261)336 0 R(aen1268)337 0 R(aen1290)338 0 R(aen132)339 0 R(aen1354)340 0 R(aen1364)341 0 R(aen1375)342 0 R(aen1377)343 0 R(aen1392)344 0 R(aen1401)345 0 R(aen1405)346 0 R(aen141)347 0 R(aen15)348 0 R(aen157)349 0 R(aen17)350 0 R(aen171)351 0 R(aen176)352 0 R(aen180)353 0 R(aen183)354 0 R(aen192)355 0 R(aen196)356 0 R(aen206)357 0 R(aen209)358 0 R(aen212)359 0 R(aen223)360 0 R(aen227)361 0 R(aen238)362 0 R(aen25)363 0 R(aen257)364 0 R(aen264)365 0 R(aen273)366 0 R(aen325)367 0 R(aen364)368 0 R(aen379)369 0 R(aen390)370 0 R(aen4)371 0 R(aen425)372 0 R(aen434)373 0 R(aen445)374 0 R(aen462)375 0 R(aen472)376 0 R(aen507)377 0 R(aen520)378 0 R(aen53)379 0 R(aen531)380 0 R(aen556)381 0 R(aen564)382 0 R(aen568)383 0 R(aen57)384 0 R(aen578)385 0 R(aen581)386 0 R(aen585)387 0 R(aen607)388 0 R(aen639)389 0 R(aen657)390 0 R(aen71)391 0 R(aen721)392 0 R(aen726)393 0 R(aen742)394 0 R(aen753)395 0 R(aen77)396 0 R(aen790)397 0 R(aen833)398 0 R(aen87)399 0 R(aen872)400 0 R(aen9)401 0 R(aen900)402 0 R(aen940)403 0 R(aen987)404 0 R(body.html)405 0 R(migration)406 0 R(samba-project-documentation)407 0 R(smbpasswdfileformat)408 0 R]>>endobj -313 0 obj<</D[500 0 R/XYZ null 726 null]>>endobj -314 0 obj<</D[503 0 R/XYZ null 768 null]>>endobj -315 0 obj<</D[509 0 R/XYZ null 798 null]>>endobj -316 0 obj<</D[509 0 R/XYZ null 706 null]>>endobj -317 0 obj<</D[509 0 R/XYZ null 569 null]>>endobj -318 0 obj<</D[509 0 R/XYZ null 246 null]>>endobj -319 0 obj<</D[512 0 R/XYZ null 581 null]>>endobj -320 0 obj<</D[512 0 R/XYZ null 417 null]>>endobj -321 0 obj<</D[512 0 R/XYZ null 292 null]>>endobj -322 0 obj<</D[515 0 R/XYZ null 768 null]>>endobj -323 0 obj<</D[515 0 R/XYZ null 326 null]>>endobj -324 0 obj<</D[518 0 R/XYZ null 686 null]>>endobj -325 0 obj<</D[518 0 R/XYZ null 496 null]>>endobj -326 0 obj<</D[416 0 R/XYZ null 266 null]>>endobj -327 0 obj<</D[518 0 R/XYZ null 345 null]>>endobj -328 0 obj<</D[518 0 R/XYZ null 155 null]>>endobj -329 0 obj<</D[521 0 R/XYZ null 581 null]>>endobj -330 0 obj<</D[524 0 R/XYZ null 798 null]>>endobj -331 0 obj<</D[524 0 R/XYZ null 706 null]>>endobj -332 0 obj<</D[524 0 R/XYZ null 525 null]>>endobj -333 0 obj<</D[524 0 R/XYZ null 348 null]>>endobj -334 0 obj<</D[527 0 R/XYZ null 686 null]>>endobj -335 0 obj<</D[527 0 R/XYZ null 443 null]>>endobj -336 0 obj<</D[527 0 R/XYZ null 187 null]>>endobj -337 0 obj<</D[530 0 R/XYZ null 673 null]>>endobj -338 0 obj<</D[530 0 R/XYZ null 232 null]>>endobj -339 0 obj<</D[419 0 R/XYZ null 686 null]>>endobj -340 0 obj<</D[536 0 R/XYZ null 594 null]>>endobj -341 0 obj<</D[539 0 R/XYZ null 798 null]>>endobj -342 0 obj<</D[539 0 R/XYZ null 730 null]>>endobj -343 0 obj<</D[539 0 R/XYZ null 700 null]>>endobj -344 0 obj<</D[539 0 R/XYZ null 348 null]>>endobj -345 0 obj<</D[542 0 R/XYZ null 768 null]>>endobj -346 0 obj<</D[542 0 R/XYZ null 639 null]>>endobj -347 0 obj<</D[419 0 R/XYZ null 509 null]>>endobj -348 0 obj<</D[410 0 R/XYZ null 798 null]>>endobj -349 0 obj<</D[419 0 R/XYZ null 332 null]>>endobj -350 0 obj<</D[410 0 R/XYZ null 730 null]>>endobj -351 0 obj<</D[422 0 R/XYZ null 768 null]>>endobj -352 0 obj<</D[422 0 R/XYZ null 577 null]>>endobj -353 0 obj<</D[422 0 R/XYZ null 505 null]>>endobj -354 0 obj<</D[422 0 R/XYZ null 394 null]>>endobj -355 0 obj<</D[425 0 R/XYZ null 739 null]>>endobj -356 0 obj<</D[425 0 R/XYZ null 615 null]>>endobj -357 0 obj<</D[428 0 R/XYZ null 768 null]>>endobj -358 0 obj<</D[428 0 R/XYZ null 683 null]>>endobj -359 0 obj<</D[431 0 R/XYZ null 798 null]>>endobj -360 0 obj<</D[431 0 R/XYZ null 706 null]>>endobj -361 0 obj<</D[431 0 R/XYZ null 569 null]>>endobj -362 0 obj<</D[434 0 R/XYZ null 699 null]>>endobj -363 0 obj<</D[410 0 R/XYZ null 593 null]>>endobj -364 0 obj<</D[434 0 R/XYZ null 220 null]>>endobj -365 0 obj<</D[437 0 R/XYZ null 768 null]>>endobj -366 0 obj<</D[437 0 R/XYZ null 656 null]>>endobj -367 0 obj<</D[440 0 R/XYZ null 399 null]>>endobj -368 0 obj<</D[443 0 R/XYZ null 475 null]>>endobj -369 0 obj<</D[446 0 R/XYZ null 798 null]>>endobj -370 0 obj<</D[446 0 R/XYZ null 706 null]>>endobj -371 0 obj<</D[407 0 R/XYZ null 647 null]>>endobj -372 0 obj<</D[449 0 R/XYZ null 673 null]>>endobj -373 0 obj<</D[452 0 R/XYZ null 798 null]>>endobj -374 0 obj<</D[452 0 R/XYZ null 730 null]>>endobj -375 0 obj<</D[452 0 R/XYZ null 474 null]>>endobj -376 0 obj<</D[452 0 R/XYZ null 244 null]>>endobj -377 0 obj<</D[458 0 R/XYZ null 768 null]>>endobj -378 0 obj<</D[458 0 R/XYZ null 445 null]>>endobj -379 0 obj<</D[410 0 R/XYZ null 178 null]>>endobj -380 0 obj<</D[461 0 R/XYZ null 727 null]>>endobj -381 0 obj<</D[461 0 R/XYZ null 444 null]>>endobj -382 0 obj<</D[461 0 R/XYZ null 254 null]>>endobj -383 0 obj<</D[464 0 R/XYZ null 768 null]>>endobj -384 0 obj<</D[413 0 R/XYZ null 739 null]>>endobj -385 0 obj<</D[464 0 R/XYZ null 630 null]>>endobj -386 0 obj<</D[464 0 R/XYZ null 532 null]>>endobj -387 0 obj<</D[464 0 R/XYZ null 421 null]>>endobj -388 0 obj<</D[467 0 R/XYZ null 528 null]>>endobj -389 0 obj<</D[470 0 R/XYZ null 798 null]>>endobj -390 0 obj<</D[470 0 R/XYZ null 730 null]>>endobj -391 0 obj<</D[413 0 R/XYZ null 379 null]>>endobj -392 0 obj<</D[473 0 R/XYZ null 356 null]>>endobj -393 0 obj<</D[476 0 R/XYZ null 768 null]>>endobj -394 0 obj<</D[479 0 R/XYZ null 798 null]>>endobj -395 0 obj<</D[479 0 R/XYZ null 706 null]>>endobj -396 0 obj<</D[413 0 R/XYZ null 268 null]>>endobj -397 0 obj<</D[482 0 R/XYZ null 768 null]>>endobj -398 0 obj<</D[485 0 R/XYZ null 647 null]>>endobj -399 0 obj<</D[416 0 R/XYZ null 768 null]>>endobj -400 0 obj<</D[488 0 R/XYZ null 621 null]>>endobj -401 0 obj<</D[407 0 R/XYZ null 616 null]>>endobj -402 0 obj<</D[491 0 R/XYZ null 567 null]>>endobj -403 0 obj<</D[494 0 R/XYZ null 528 null]>>endobj -404 0 obj<</D[497 0 R/XYZ null 237 null]>>endobj -405 0 obj<</D[413 0 R/XYZ null 698 null]>>endobj -406 0 obj<</D[467 0 R/XYZ null 528 null]>>endobj -407 0 obj<</D[407 0 R/XYZ null 753 null]>>endobj -408 0 obj<</D[437 0 R/XYZ null 656 null]>>endobj -409 0 obj<</Type/Pages/MediaBox[0 0 595 792]/Count 49/Kids[410 0 R -548 0 R -551 0 R -554 0 R -413 0 R -416 0 R -419 0 R -422 0 R -425 0 R -428 0 R -431 0 R -434 0 R -437 0 R -440 0 R -443 0 R -446 0 R -449 0 R -452 0 R -455 0 R -458 0 R -461 0 R -464 0 R -467 0 R -470 0 R -473 0 R -476 0 R -479 0 R -482 0 R -485 0 R -488 0 R -491 0 R -494 0 R -497 0 R -500 0 R -503 0 R -506 0 R -509 0 R -512 0 R -515 0 R -518 0 R -521 0 R -524 0 R -527 0 R -530 0 R -533 0 R -536 0 R -539 0 R -542 0 R -545 0 R +323 0 obj<</Subtype/Link/Rect[72.0 684.0 223.3 697.0]/Border[0 0 0]/Dest[610 0 R/XYZ null 798 0]>>endobj +324 0 obj<</Subtype/Link/Rect[108.0 670.8 153.5 683.8]/Border[0 0 0]/Dest[610 0 R/XYZ null 730 0]>>endobj +325 0 obj<</Subtype/Link/Rect[108.0 657.6 493.5 670.6]/Border[0 0 0]/Dest[610 0 R/XYZ null 700 0]>>endobj +326 0 obj<</Subtype/Link/Rect[108.0 644.4 498.7 657.4]/Border[0 0 0]/Dest[610 0 R/XYZ null 348 0]>>endobj +327 0 obj<</Subtype/Link/Rect[108.0 631.2 450.2 644.2]/Border[0 0 0]/Dest[613 0 R/XYZ null 768 0]>>endobj +328 0 obj<</Subtype/Link/Rect[108.0 618.0 419.9 631.0]/Border[0 0 0]/Dest[613 0 R/XYZ null 639 0]>>endobj +329 0 obj<</Subtype/Link/Rect[72.0 591.6 342.4 604.6]/Border[0 0 0]/Dest[616 0 R/XYZ null 798 0]>>endobj +330 0 obj<</Subtype/Link/Rect[108.0 578.4 187.1 591.4]/Border[0 0 0]/Dest[616 0 R/XYZ null 706 0]>>endobj +331 0 obj<</Subtype/Link/Rect[108.0 565.2 247.6 578.2]/Border[0 0 0]/Dest[616 0 R/XYZ null 582 0]>>endobj +332 0 obj<</Subtype/Link/Rect[108.0 552.0 230.8 565.0]/Border[0 0 0]/Dest[616 0 R/XYZ null 484 0]>>endobj +333 0 obj<</Subtype/Link/Rect[108.0 538.8 205.8 551.8]/Border[0 0 0]/Dest[616 0 R/XYZ null 359 0]>>endobj +334 0 obj[323 0 R +324 0 R +325 0 R +326 0 R +327 0 R +328 0 R +329 0 R +330 0 R +331 0 R +332 0 R +333 0 R +]endobj +335 0 obj<</Dests 336 0 R>>endobj +336 0 obj<</Kids[337 0 R]>>endobj +337 0 obj<</Limits[(aen1015)(smbpasswdfileformat)]/Names[(aen1015)338 0 R(aen1129)339 0 R(aen1159)340 0 R(aen116)341 0 R(aen1193)342 0 R(aen1201)343 0 R(aen1209)344 0 R(aen1217)345 0 R(aen1224)346 0 R(aen1260)347 0 R(aen1273)348 0 R(aen1276)349 0 R(aen1286)350 0 R(aen1311)351 0 R(aen132)352 0 R(aen1329)353 0 R(aen1333)354 0 R(aen1346)355 0 R(aen1353)356 0 R(aen1357)357 0 R(aen1362)358 0 R(aen1366)359 0 R(aen1382)360 0 R(aen1390)361 0 R(aen1394)362 0 R(aen1397)363 0 R(aen1403)364 0 R(aen141)365 0 R(aen1415)366 0 R(aen1418)367 0 R(aen1429)368 0 R(aen1438)369 0 R(aen1449)370 0 R(aen1469)371 0 R(aen1484)372 0 R(aen1498)373 0 R(aen15)374 0 R(aen1505)375 0 R(aen1527)376 0 R(aen157)377 0 R(aen1591)378 0 R(aen1601)379 0 R(aen1612)380 0 R(aen1614)381 0 R(aen1629)382 0 R(aen1638)383 0 R(aen1642)384 0 R(aen1651)385 0 R(aen1658)386 0 R(aen1663)387 0 R(aen1666)388 0 R(aen1671)389 0 R(aen17)390 0 R(aen171)391 0 R(aen176)392 0 R(aen180)393 0 R(aen183)394 0 R(aen192)395 0 R(aen196)396 0 R(aen206)397 0 R(aen209)398 0 R(aen212)399 0 R(aen223)400 0 R(aen227)401 0 R(aen238)402 0 R(aen25)403 0 R(aen257)404 0 R(aen264)405 0 R(aen273)406 0 R(aen325)407 0 R(aen364)408 0 R(aen379)409 0 R(aen390)410 0 R(aen4)411 0 R(aen425)412 0 R(aen434)413 0 R(aen445)414 0 R(aen467)415 0 R(aen478)416 0 R(aen513)417 0 R(aen53)418 0 R(aen530)419 0 R(aen541)420 0 R(aen566)421 0 R(aen57)422 0 R(aen574)423 0 R(aen578)424 0 R(aen588)425 0 R(aen591)426 0 R(aen595)427 0 R(aen617)428 0 R(aen661)429 0 R(aen679)430 0 R(aen71)431 0 R(aen743)432 0 R(aen748)433 0 R(aen764)434 0 R(aen77)435 0 R(aen781)436 0 R(aen787)437 0 R(aen827)438 0 R(aen87)439 0 R(aen870)440 0 R(aen884)441 0 R(aen9)442 0 R(aen912)443 0 R(aen923)444 0 R(aen971)445 0 R(body.html)446 0 R(migration)447 0 R(samba-project-documentation)448 0 R(smbpasswdfileformat)449 0 R]>>endobj +338 0 obj<</D[541 0 R/XYZ null 488 null]>>endobj +339 0 obj<</D[550 0 R/XYZ null 768 null]>>endobj +340 0 obj<</D[553 0 R/XYZ null 435 null]>>endobj +341 0 obj<</D[457 0 R/XYZ null 266 null]>>endobj +342 0 obj<</D[556 0 R/XYZ null 189 null]>>endobj +343 0 obj<</D[559 0 R/XYZ null 605 null]>>endobj +344 0 obj<</D[559 0 R/XYZ null 406 null]>>endobj +345 0 obj<</D[559 0 R/XYZ null 168 null]>>endobj +346 0 obj<</D[562 0 R/XYZ null 698 null]>>endobj +347 0 obj<</D[565 0 R/XYZ null 341 null]>>endobj +348 0 obj<</D[568 0 R/XYZ null 434 null]>>endobj +349 0 obj<</D[568 0 R/XYZ null 339 null]>>endobj +350 0 obj<</D[571 0 R/XYZ null 686 null]>>endobj +351 0 obj<</D[577 0 R/XYZ null 798 null]>>endobj +352 0 obj<</D[460 0 R/XYZ null 686 null]>>endobj +353 0 obj<</D[577 0 R/XYZ null 706 null]>>endobj +354 0 obj<</D[577 0 R/XYZ null 569 null]>>endobj +355 0 obj<</D[577 0 R/XYZ null 246 null]>>endobj +356 0 obj<</D[580 0 R/XYZ null 581 null]>>endobj +357 0 obj<</D[580 0 R/XYZ null 417 null]>>endobj +358 0 obj<</D[580 0 R/XYZ null 292 null]>>endobj +359 0 obj<</D[583 0 R/XYZ null 768 null]>>endobj +360 0 obj<</D[583 0 R/XYZ null 326 null]>>endobj +361 0 obj<</D[586 0 R/XYZ null 686 null]>>endobj +362 0 obj<</D[586 0 R/XYZ null 496 null]>>endobj +363 0 obj<</D[586 0 R/XYZ null 345 null]>>endobj +364 0 obj<</D[586 0 R/XYZ null 155 null]>>endobj +365 0 obj<</D[460 0 R/XYZ null 509 null]>>endobj +366 0 obj<</D[589 0 R/XYZ null 581 null]>>endobj +367 0 obj<</D[592 0 R/XYZ null 798 null]>>endobj +368 0 obj<</D[592 0 R/XYZ null 706 null]>>endobj +369 0 obj<</D[592 0 R/XYZ null 525 null]>>endobj +370 0 obj<</D[592 0 R/XYZ null 348 null]>>endobj +371 0 obj<</D[595 0 R/XYZ null 686 null]>>endobj +372 0 obj<</D[595 0 R/XYZ null 443 null]>>endobj +373 0 obj<</D[595 0 R/XYZ null 187 null]>>endobj +374 0 obj<</D[451 0 R/XYZ null 798 null]>>endobj +375 0 obj<</D[598 0 R/XYZ null 673 null]>>endobj +376 0 obj<</D[598 0 R/XYZ null 232 null]>>endobj +377 0 obj<</D[460 0 R/XYZ null 332 null]>>endobj +378 0 obj<</D[604 0 R/XYZ null 594 null]>>endobj +379 0 obj<</D[607 0 R/XYZ null 798 null]>>endobj +380 0 obj<</D[607 0 R/XYZ null 730 null]>>endobj +381 0 obj<</D[607 0 R/XYZ null 700 null]>>endobj +382 0 obj<</D[607 0 R/XYZ null 348 null]>>endobj +383 0 obj<</D[610 0 R/XYZ null 768 null]>>endobj +384 0 obj<</D[610 0 R/XYZ null 639 null]>>endobj +385 0 obj<</D[613 0 R/XYZ null 798 null]>>endobj +386 0 obj<</D[613 0 R/XYZ null 706 null]>>endobj +387 0 obj<</D[613 0 R/XYZ null 582 null]>>endobj +388 0 obj<</D[613 0 R/XYZ null 484 null]>>endobj +389 0 obj<</D[613 0 R/XYZ null 359 null]>>endobj +390 0 obj<</D[451 0 R/XYZ null 730 null]>>endobj +391 0 obj<</D[463 0 R/XYZ null 768 null]>>endobj +392 0 obj<</D[463 0 R/XYZ null 577 null]>>endobj +393 0 obj<</D[463 0 R/XYZ null 505 null]>>endobj +394 0 obj<</D[463 0 R/XYZ null 394 null]>>endobj +395 0 obj<</D[466 0 R/XYZ null 739 null]>>endobj +396 0 obj<</D[466 0 R/XYZ null 615 null]>>endobj +397 0 obj<</D[469 0 R/XYZ null 768 null]>>endobj +398 0 obj<</D[469 0 R/XYZ null 683 null]>>endobj +399 0 obj<</D[472 0 R/XYZ null 798 null]>>endobj +400 0 obj<</D[472 0 R/XYZ null 706 null]>>endobj +401 0 obj<</D[472 0 R/XYZ null 569 null]>>endobj +402 0 obj<</D[475 0 R/XYZ null 699 null]>>endobj +403 0 obj<</D[451 0 R/XYZ null 593 null]>>endobj +404 0 obj<</D[475 0 R/XYZ null 220 null]>>endobj +405 0 obj<</D[478 0 R/XYZ null 768 null]>>endobj +406 0 obj<</D[478 0 R/XYZ null 656 null]>>endobj +407 0 obj<</D[481 0 R/XYZ null 399 null]>>endobj +408 0 obj<</D[484 0 R/XYZ null 475 null]>>endobj +409 0 obj<</D[487 0 R/XYZ null 798 null]>>endobj +410 0 obj<</D[487 0 R/XYZ null 706 null]>>endobj +411 0 obj<</D[448 0 R/XYZ null 647 null]>>endobj +412 0 obj<</D[490 0 R/XYZ null 673 null]>>endobj +413 0 obj<</D[493 0 R/XYZ null 798 null]>>endobj +414 0 obj<</D[493 0 R/XYZ null 730 null]>>endobj +415 0 obj<</D[493 0 R/XYZ null 302 null]>>endobj +416 0 obj<</D[496 0 R/XYZ null 693 null]>>endobj +417 0 obj<</D[499 0 R/XYZ null 542 null]>>endobj +418 0 obj<</D[451 0 R/XYZ null 178 null]>>endobj +419 0 obj<</D[502 0 R/XYZ null 768 null]>>endobj +420 0 obj<</D[502 0 R/XYZ null 383 null]>>endobj +421 0 obj<</D[505 0 R/XYZ null 768 null]>>endobj +422 0 obj<</D[454 0 R/XYZ null 739 null]>>endobj +423 0 obj<</D[505 0 R/XYZ null 577 null]>>endobj +424 0 obj<</D[505 0 R/XYZ null 466 null]>>endobj +425 0 obj<</D[505 0 R/XYZ null 328 null]>>endobj +426 0 obj<</D[505 0 R/XYZ null 230 null]>>endobj +427 0 obj<</D[508 0 R/XYZ null 768 null]>>endobj +428 0 obj<</D[508 0 R/XYZ null 191 null]>>endobj +429 0 obj<</D[514 0 R/XYZ null 798 null]>>endobj +430 0 obj<</D[514 0 R/XYZ null 730 null]>>endobj +431 0 obj<</D[454 0 R/XYZ null 379 null]>>endobj +432 0 obj<</D[517 0 R/XYZ null 356 null]>>endobj +433 0 obj<</D[520 0 R/XYZ null 768 null]>>endobj +434 0 obj<</D[523 0 R/XYZ null 798 null]>>endobj +435 0 obj<</D[454 0 R/XYZ null 268 null]>>endobj +436 0 obj<</D[523 0 R/XYZ null 706 null]>>endobj +437 0 obj<</D[523 0 R/XYZ null 608 null]>>endobj +438 0 obj<</D[526 0 R/XYZ null 660 null]>>endobj +439 0 obj<</D[457 0 R/XYZ null 768 null]>>endobj +440 0 obj<</D[529 0 R/XYZ null 531 null]>>endobj +441 0 obj<</D[529 0 R/XYZ null 196 null]>>endobj +442 0 obj<</D[448 0 R/XYZ null 616 null]>>endobj +443 0 obj<</D[532 0 R/XYZ null 359 null]>>endobj +444 0 obj<</D[532 0 R/XYZ null 183 null]>>endobj +445 0 obj<</D[538 0 R/XYZ null 545 null]>>endobj +446 0 obj<</D[454 0 R/XYZ null 698 null]>>endobj +447 0 obj<</D[508 0 R/XYZ null 191 null]>>endobj +448 0 obj<</D[448 0 R/XYZ null 753 null]>>endobj +449 0 obj<</D[478 0 R/XYZ null 656 null]>>endobj +450 0 obj<</Type/Pages/MediaBox[0 0 595 792]/Count 60/Kids[451 0 R +622 0 R +625 0 R +628 0 R +454 0 R +457 0 R +460 0 R +463 0 R +466 0 R +469 0 R +472 0 R +475 0 R +478 0 R +481 0 R +484 0 R +487 0 R +490 0 R +493 0 R +496 0 R +499 0 R +502 0 R +505 0 R +508 0 R +511 0 R +514 0 R +517 0 R +520 0 R +523 0 R +526 0 R +529 0 R +532 0 R +535 0 R +538 0 R +541 0 R +544 0 R +547 0 R +550 0 R +553 0 R +556 0 R +559 0 R +562 0 R +565 0 R +568 0 R +571 0 R +574 0 R +577 0 R +580 0 R +583 0 R +586 0 R +589 0 R +592 0 R +595 0 R +598 0 R +601 0 R +604 0 R +607 0 R +610 0 R +613 0 R +616 0 R +619 0 R ]>>endobj -410 0 obj<</Type/Page/Parent 409 0 R/Contents 411 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 17 0 R>>endobj -411 0 obj<</Length 412 0 R/Filter/FlateDecode>>stream -xu’AsÓ0…ïþoz*3b9®“p"¥80
gŽ²½‰l+H2™ü{VŠ!MÆ;«Õî~ïI?#‰˜‰Y‚i†²‹îóhò¸@#ßp&›¦È+Ä"Žy¥¼^/¿Ü/±2zG¥Ãƒ.‡Žz§\£û7ù.”J®ð¥·³X̹x¬ÉIu~ˇ<ân¸»“œMç3þŸðÏ6§Ä4ÙëÄ+ªt‘…Ög®eaQ¥;A¤r„Hæ"ñyÝXZÿ -NcºB¡z©ú¸šp$e>Ù£ßK½ÞÕÊAµ`írz«8UÆ°I7(«;rMG6ô -,2[î½Ó…ïÂ@=aOÆ2[Éa§v¸éð]aIµu´Ø4=ã2R«™³¹|¤|^þõü1’23¤©d¤‰ôŽœ¢kà1‡Ià=ÊjíèŽóÖy^K`™A£o~c¶¸®Û¿L‡ƒ°Þ@¡Ívr¹7ø½,2_]\¡+ìÕ–Xèª%e –Xà°¯Xû¥Ï -‘ò¹Æ¬f–‰tþˆùŒå%‹‹[¼#cŽïþBþ‡Q„uÜ&~_¡÷5±)7Õ#Ë×è7öæ˜endstream -endobj -412 0 obj -468 -endobj -413 0 obj<</Type/Page/Parent 409 0 R/Contents 414 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 20 0 R>>endobj -414 0 obj<</Length 415 0 R/Filter/FlateDecode>>stream +451 0 obj<</Type/Page/Parent 450 0 R/Contents 452 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 17 0 R>>endobj +452 0 obj<</Length 453 0 R/Filter/FlateDecode>>stream +xu’OsÚ0ÅïþorJgcÇ@O%ýè$-žéY¶6µ-*Éeøö}¤”d2l¤ÕîþÞ[ýŽ>³ÓUÝÑäÓi‚bÍH>ÍPÔHâ$áNu½Z~»_âÑèª>èjìÕà¤kõð¦Ø†TÁŸz;Kâ9“O9…’½?ò±ˆX
ww‚Ñl>ãÿ”?£°>¦yœ?<£Êy(}æZ–ÖY¹#D!Né<N=DÑ´¥Ö¿À¯D¥»Ž +ˆ
½Æ—‡ŸÅ·ëZÕp+Ù—õÿê ÿ(×(”46ÆW8sð‡Õ`GÒ»F:È®ó/¦Ç¾’¡j4†.Ý ¬î•k{eC± +;e,á*.{ÙÒâvˆ‚ý{míªXd²'
ŽÏþrª„ýø ‘DzLªG*fÞû°ê°ò3O¸LñÙÓ'ý¢ä|ô8Ô Ê ÑW>÷0\7ÎíÞN&ûý>¶ÞÀX›ÍäòlHðg©1迺¸BWØÉ¢ÎÇNI«`Ž»Z:o—>ËCƹ&”2ºÂâIÉ0jK·x«Œ9¼ûù +cöq›ú¼BïE»o²O,ߣ¿"çRendstream +endobj +453 0 obj +461 +endobj +454 0 obj<</Type/Page/Parent 450 0 R/Contents 455 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 20 0 R>>endobj +455 0 obj<</Length 456 0 R/Filter/FlateDecode>>stream xV]sÛ6|ׯ¸¦‰:cS¢>,Éov§NóÐfë¥ Š¨H€À(šéïÞ‘´å4êÔeK{»{þ5JiŠŸ”V3šßPVî·£ÉÆfSÚøæfµ¦mNÓd:Å'Ùø§R5Q{JúÅ):zoCTUEÊæ´Õ!Òãݯ÷w?nÿ”:颫s=O“*Ó[£nhzKµÊ)–šje©Q{º}JÓ~ßlÅ»¶çk(7!z³k£ÎéhbÙI™³QKT¹ÈÔ]´[8œ¢"h©«†ïu¤“k ð=*%Dïþ€!Lé:w€sgßF:Xt[v{Fý„˜ñ[ŠþD\ciìž*sз]/`÷©—›täã¨û*í¿[®¹f¨wy²¦¿©v^˺Ÿ·#¦_4 &ê+¡é%.¿§1•16·“ÉñxLïHœßóÚmHCXŽ¿´\ÌñºX¯ð:Ã/N/öYN7¢Æ³a§ÞGé-Ý·¦Ê™wöÒ½±Ê›ËVr”³L¸¢ÂxÖ·Ðïö^Õ½8ËAœdcfßözLfÇ°–ì숄/½Î¢ó§„¶¨O¡tm•“j£cj3Œ \òTM|6ZÇ/d`zröØ„¦Â)D]'½=©TŸ4µ¶
ªˆ¬Öy`VÌ\«\J}u>ûŠ½sñû/mxÞéõµÌIW`hc1ë=ÜQ‡S‚Ötäá Î ¹†]NGk«v•Æxm¤þŠZîëuØjuÐÁÈ\g˜Ë¨E]o„>ØL“‰o!F›ÁëЉP7¦‚Á9%²¢§ãÿ²Åˆ` #©?×ú¤}àlâXï……«Í¾Œ¶ìwÉhÉyžf‡ÉëwÉré¨ñR
ñÏN#z¬ª‡KEÑ›EÞÀ²Q[>½Iì²w´SÙí¢ãœ|-}qhWûx™´žªÂà²å:U¸rÂÇÇvaKélØüïhÝ,äR:OÖyŸ¬³[žYâÛÝÔóQYŒ9îî‹*·ô]ì@a$öº‹£ùZ蘕üÖ]€Š, Ä$v`ÏSî=Èé,DS·•„_Bït”dš=?_°ð†1œi:ŒŠKðDËmljÜoPÏÙát…圇l:Iˆ"%’¾æqÝó@¸}}˜Cn5Ô„C%mºà•¦agqôƒ%)7yXŸ= endobj -415 0 obj +456 0 obj 1092 endobj -416 0 obj<</Type/Page/Parent 409 0 R/Contents 417 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj -417 0 obj<</Length 418 0 R/Filter/FlateDecode>>stream +457 0 obj<</Type/Page/Parent 450 0 R/Contents 458 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +458 0 obj<</Length 459 0 R/Filter/FlateDecode>>stream xWÛnÛ8}ÏWÌö¥.ÐÈ—ØŽ`Ún[E/Û8Ø
šÅ‚’(‰Dº$•Ô¿gH)vÕ¤› Žc
çræÌæÛÑ”&øžÒéŒN–”5G/7G¯7G“dµ¢ý‹-ñÇ„æëe²¢ùêïOù•TÀv÷/írµNæíöÁÎÇoÖ4Ó¦@Øåb‘,i“‡ÓÚd£i2OèÂË-œÑ++…—ä+I®I)3ºPek…WFS¡j™<Û|…Ã9M§ÑáñìîF›J"œÀͶ–u¤tð,¿GäÚ4WVfÞØ]ÿ4WÎ[•¶2¡sØ”¥tžv¦EE"g
g1¡ãéI2ãèm]ïÈ™`˜ MNJªÌ]i¶ìÎQiÈ›RÂ…åx´µ"ó*“@ ç‹èœº¯/emRQÿÓ—Špìþ1~ß{SZÓnéwzõöóÇËOñlš}hü¥BîÞà°l¹ sÚ<–¡!FøÞtÏcsÈqW©¬ê` /D“ @@ -670,22 +738,22 @@ R¼°È©ˆdyùùã_çÞ&þ»fê䲪v×ÏúVtœÙGåã7‹n’F Dc鳱͒ B?v
oQOréyOP¿ëÃ2ê.1 mXy©¬¦UÛ8p%—£ŠÝ1‹q7‰Õ÷; Í¡¢/æ(Àª[ÛÓåiÂÿ à&~p%¿xñþåúdÍWÜ‘0lq•„ÝÄÀÇSÇñØÿ¹ÀÏW“dÿpœ±G(ÖŸGÿ@FË*endstream endobj -418 0 obj +459 0 obj 1451 endobj -419 0 obj<</Type/Page/Parent 409 0 R/Contents 420 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj -420 0 obj<</Length 421 0 R/Filter/FlateDecode>>stream +460 0 obj<</Type/Page/Parent 450 0 R/Contents 461 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +461 0 obj<</Length 462 0 R/Filter/FlateDecode>>stream x•WïOÛHýÎ_1p.U‰'! Ü'ª–;¤+å §ªR¥ÓÆ^'¶7·»&Éovã$¸ä( ™ ïüØ7oÞLþ=Š©‹ß˜F=ê))Ž>LŽ>MŽºÑxL»‡™áŸ.{јã>Ñ€Œ¤Gñßp÷¦ß†á
\á%üoðÓ¹:§x@“a‡c|Hýû.M’V
£8¢{'t&.ðA§ÊeF¤JéÒ(ÑeönòpÔ¹P?íÞ~Z7_&Ÿ~£ÉYé<×K¶\ª<§©¤Te™4²t¤2¢µ®¨²’n®ïIþóžœÆ!댚VN¦d¥yR‰´Tˆ…8b—Ú½!nHjýH±C!€è³iu¤K:µõóL[Ñ×9씥Tf¸PÊ^Ú8Šûç—,"ºÎ¨ÔnÎÉï#7—%‰”ÃG¹É*îG=Î Fö"DŒ÷°Ùäô¦JÛ¶µ%ÕÑž§·wA« •“¯¥ÁéQ§J6;×UžÒ\<I%Q³öɼ¹´µ§ƒqoäÊ‘LÕÿ@{ˆ-¤t€[j‘%« d¸€á .3wbÔô,Ô”?ûxR„ú 6KôŒÖŽ:•5\'"ïXQLEgªÊŽ-¦`?êò ¸<
ÿT ô(¨<‰YeÌ¥"pà@+ë5ΪíjO¹vöÞXMŒZ¸SüÆ°ƒ‡Fèpðò¤%ëÝò·h”¹Ù"w¨{þ ÓSZH3ÇT§îv+Ÿ§ýñ÷Ÿ¿|?àT ¯yÎc£óPAöž€?·ÔVX·‰zen$Êw-=&u¯ò=ƒ©¼¤xUGŸ,ežûÛù5¬K½xˆ…*l]=ìZ~éÂjµ¿HÅ~3k®R½z•šFt™ƒ6¥pêI^‡ÊÓìB
)²ÐåóÌyrQWͯEÀ`Ïj¿Þ äÊ›z¾0€Ámt`]ÌN¬33.@_k÷B>:Ôëy~,¼>É9ƒy^#` çížXœÓ[l}I7¶»}u7«=5ü 1ðŽ·G=|Hßô
`0îFçø³>§€~ùëè?åÆendstream endobj -421 0 obj +462 0 obj 1365 endobj -422 0 obj<</Type/Page/Parent 409 0 R/Contents 423 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F2 5 0 R/F3 6 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj -423 0 obj<</Length 424 0 R/Filter/FlateDecode>>stream +463 0 obj<</Type/Page/Parent 450 0 R/Contents 464 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F2 5 0 R/F3 6 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +464 0 obj<</Length 465 0 R/Filter/FlateDecode>>stream xV]OëF}çWL¥V
q’‡J÷SºÒ½Ð6iQÕôaco’%ö®ïîÈ¿¿gvíKH€>´ ÀÁöÌ™3çÌìדõñ= qJç#ÊÊ“·ó“ÞÇ!
4_áÎh2¦yNý¤ßïÓ<ëÌ
mUQòä¤ÎIÄNµ(ÈòI•5™tN::ß"ÜE®Cº\æñmŠ „9xÎ?–ð#}ꦣdD«ëù‡)}ZÑÎÔT;Ïþü}HÎï IJ3Äó²ä[šÂƒ¥ØQ¡¶xÚPaÌ–„ç»1=xhªîΓ”³ÈQV…t=wg‡]ç…õuuX€Ë¬ªÇP)z&Ê¥ Ò+AŽ$Ôða~6it>JF4œŒqâÇJZEò/i€ ùý4™<¡ŒšyYÑhJsËÅ8¯ô:Tï6‚sq'T!–àÀh.ÚZeï¤=ª2åÞv~lØ´]ûY¡¤öÔýÜÜ;oï…€ã¼eC[ÛɽæüÅYÝÆÔENkéi)2PÀ’YáÎ1Ј4MÚ¾æFÿ¤É™Rú
—ªˆÍŒµ2óÅ®‘EÛ0'Ñ „èÊx–Dh/^àwMN™Ð$ @@ -693,11 +761,11 @@ gh)Y39÷ÌII÷ü`ƒŠ€í)‡ ±ôYè/B‹5.#;î õ¢ãêlCÂÑÍêf½8=Tl£ÕlcäŠô– y' Èj«ü.ê”õÌ2])ø"–eå×Z:S%œ»76G+¸ÐÚ=»’ÕÀQÅÊÀʵâö3v‹%E…´
í endobj -424 0 obj +465 0 obj 1189 endobj -425 0 obj<</Type/Page/Parent 409 0 R/Contents 426 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj -426 0 obj<</Length 427 0 R/Filter/FlateDecode>>stream +466 0 obj<</Type/Page/Parent 450 0 R/Contents 467 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +467 0 obj<</Length 468 0 R/Filter/FlateDecode>>stream xWÙnã8|ÏW4ò²`+¶ã\ƒ=à\‰'3öÂX /´DÙœP¤G¤âøï·š”r(³‚ŠE²««««é{êãg@§C::¡´Ø»˜ïÞœÓ`DóoNÎðQ?é÷û4O;ƒdÐOh±ž&9Í×ʬ]Y󋧅-ÿ8˜Çþ
qoxŠý¬5ÖójÚb™#a2ÚÙŠœ¥'o‰_>Òþvmi[Z/‰?q´QZ’ÍÉ—Â÷ñ™44!WVÒùpBfqˆÜÐÄJ(CœÍ0úÔ%CÞ<WZ‡M©Ðevk’zåð$áD;sÀÀ µZ{*¥È8(åŒãj2þ<ý2›ÌÿìC üŠnÆ_fƒ·‰R‡q¾J#`_îÂ!…Pš)Ð @@ -710,32 +778,32 @@ i¼ðʲ\À«³U™J ™¤Öäïsî„¡ÂÚ•/"GÁG=[+øÁ†–<û¸ÄLë“À?…ønKåw/ßÎdbÈêL–³vð½`³q†°haúÑ@r[ÕŽf$Ï
€eÌ”2™±V…ŠÊ”Y÷¶¥æ Á ÑÂ:®XVpm™A‘!=c·Øë¦â£ÄŠpcŠ:ÛxaÞ›¦œŠ5z׊[JÌZà ²'´®XÁ»0þš"¯@Í,†)a—.`Ñèwv÷E¾X¡ÄÒÉò æ˜NXÀ!áz*kÏÑ0¯Q°F»]FòyNA}£AªŸ†¸„jc€@Á˜¢ I[v\’Œ(ÃVùu#8˜Ãœ•«O¯–ÖnÄEíÕÓ9êTþ=?ækNps=›Éxh:ꡃU€k*Á¤¡ÊŒ¦`Æê»R;½)î–ŸhþÚ³›RÁÚT²ââ³4TrS„ÿªÉè¶ÑÖç—÷‡“{By¹
›1Õ¿U©¨€ «„n€1 ›ŠwG-y„O¥_ÊJµÏå[ZbO¸VBf?nM+räv¸#ðκéXÙU!–è7µ¾¬VªÃ›³úv089Mø.ð³ñÝŘ-ü;<þ7W(Ž×‹‹{§C|KÈþ×·„ÑY?9Ç7,?æ#p›øº÷7¾8ñ5endstream endobj -427 0 obj +468 0 obj 1513 endobj -428 0 obj<</Type/Page/Parent 409 0 R/Contents 429 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj -429 0 obj<</Length 430 0 R/Filter/FlateDecode>>stream +469 0 obj<</Type/Page/Parent 450 0 R/Contents 470 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +470 0 obj<</Length 471 0 R/Filter/FlateDecode>>stream x•W]oÛ6}ϯ¸ðËR Ñl'qÒ‡>8‰‹Kâ,v·Pб‘H•¤âêßï\Rr\µ0‹¼çž{îÕ׃ ñoBçS:™QZ\®ëƒq2¦ÙÅÛä”N/Îñ<Å+)ç׿¾K“SZç¸8;;Kf´ÎÆcZ§‡“d2NNº·J{¥Ÿ(·¦¢wþ&oHÐU©¤ötõfý¦Ni2‰¦Ž§ç0t¸6Ô8‰ƒ5–|!<)GâE¨RlJI/Jཫ6ÇádFä¤}ÁÉàIP£Õ7*ŒóÔš†¶ª,IKƒûÔTµ‚_Hv?¦ãÉI2e·°–ÆÈjkž¬¨ú„Û8¨w·•v^À~$—ZU{¢.†HG =H/xÉm“ze4ž9Òp„rc©2vè;“©¹„º˜¦3àÎP˜sê¥cèVŸV’ó-èÜl2#UMZPŒLTœ CŸ"Z$ÞûO\ë^úàƒ†Kíö#u »ïj6;CÅÿ»ög'“€Ý ög ݘôþÿ¥ÂKòZ)h[(íL%½ªC*PyGÞš†ËŒÄËh(D†b}lßòm[&ïOwvûšo$Q--°¯€Å¦e o/;Î$)Wl¿‘•©±Yoi4 I š-ŠBaÀ+Ž?X¡Ÿ$G²i=BBé™ÊAº„‚/:cgÌ”Q&uNdÒð˜ÎY¹Z¦*W2ûÁ?l‰`ØÛb³ÕÍÑÔµ±þÇŒÐ\Ìö§Ú—‡obÇ€^VHðÀ>»È=|ªª.e…¾‚Ñ€ÓpÒ
B=Ž— C’¡‰M*#²ÖìÁ¾;g!c³C@@)¾Hè£FÁ|£…—% xì/ÌB¾6 ±»&e®æM9,ÚÊ[•z$¿/ä Ó”¥…Dó3˜òöð.È@Aè\Æ1ÑÖ²Æ{ 6ñ|jP¸@«h÷ºuk,Ü@áY15Çï HÁI…ƒHjf¹ë¾çdOä8MÊ@Q¶´äÜ…mþU”9ôp&º@NéLB aŒM%že/œQz(¾Þ£€Õ-ç¤^5[
Iƒ¦† ð„Dª„.[Êd.šì‰T1ºs¼çÐåòsX…¹ç¾Ü\ŘÒóž0H›:Š(û.§wÔF•fAôq±xÍ:ò€Û—káÔ?eÀCž·.c¨J¦\ØpУq–t0,.¥ZØ ð¨õÊ„å£l´"ÜI*š¢nÌ1Ô¯Ìè_ü®z{ r|(}<Dgܯi†]Î=¾“4·a` \Äbä @䜕¾±Ac¬í
æÆ'T—W¹£Y˜ ¡yà endobj -430 0 obj +471 0 obj 1666 endobj -431 0 obj<</Type/Page/Parent 409 0 R/Contents 432 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj -432 0 obj<</Length 433 0 R/Filter/FlateDecode>>stream +472 0 obj<</Type/Page/Parent 450 0 R/Contents 473 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +473 0 obj<</Length 474 0 R/Filter/FlateDecode>>stream x“_o›0Åßó)Žò”J‹!ä±íÖ©Õ:…½õÅ5—âlf;Yûíw
ÍÖE[U!,[Ü?¾¿sø1I‘ð“¢X Ë¡ºÉE9ùxµAºDYó—|Í› ‰H’¥š¥"MD.p#û^›|÷äŒìÈŸ•œ¸DšŽ‰óEÁ‰³ëÏvF•®krdöÇ,XƒÐn/=¤©0öF?#äâ™#äŽ ÑZ»ƒCÌôX짱y‚yš‰Eljû À–hˆöݽPÖÔlÐËBm* R·^ÄìÏå„gDže¼.ׯ~Gž"Ym6C›(…ÀW¾Ãe#Tw[ ïáÒ;{ßRçKDZë–¤ø©C©##f£Ž…=ô€ÃݬÕÌ&"üBŽ§û€+&¬Xwe«°6ò ™ÁŸZ:ø»³ô5¬l×uÄZDÝþB~®†L?FÈñ&¿éFeëíIçÈ7”Šóx°j%g=É®oɳ]ø2ÁºçײÕZ¿X/ÍýÌv}åÛíùÍÅ9n}äšødÕžg2ú$Þv>fÍÇ´·]¾\'bÿx±Î·É/ŠçûŒendstream endobj -433 0 obj +474 0 obj 451 endobj -434 0 obj<</Type/Page/Parent 409 0 R/Contents 435 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj -435 0 obj<</Length 436 0 R/Filter/FlateDecode>>stream +475 0 obj<</Type/Page/Parent 450 0 R/Contents 476 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +476 0 obj<</Length 477 0 R/Filter/FlateDecode>>stream x•WMoÛ8½çWri 8ŽíæÃ9-Ðìئ݋v\hŠ¶¸‘H•¤âúßï’’l¥—EÛ ‘HÎÌ{oÞP?Næ4ß9Ý,èÍ5Éúäíêäâî–3ZmðæúfI«‚fÓÙOäÙ»R4A9ZLéOa> CÂt¿¢/Âûu}0Òí› y½ú÷dFç‹Kœp¦
=ˆz-°ó'¿à s¼á çoæÓ/ZLçSúh‚³E+»#.î.i>Ï+7¼î›%…RQ¡žUe›Z™@v“S[$Èi}Ó¦°;Ïé‘´u#‚^WŠš.UÕ§JëR~ҴϹÏߤČݑà½,=‹J"(j=IkŒŠÉzB‘ꧡÚÇ켨íÄž„'‡Ù!ÚAr8æY¹i‡×õ4"¶*µ§ÂÊ6VW(/^+O%ráÚ>½ýe)$ªu@¨&òä#»RpY¾ÅØì üÓG]²´Ök³¥]©xÑÞ¶(ð¢pÔt¦ôžùÒ¶UAN‰‚“8nÓVÕ~BÊ7Jjÿ-äÙ þJ@°x
‰'æ,¢Íšä
bõ3ô['à¨ÑÚë0Ç' @@ -747,11 +815,11 @@ dhh…;îF‡U¶¦ÌÍy:²ž1i˜í£bÓ™§œx5ÆX9~é•ÌKN!¾ªRf«Nc¿¾¨¼{Í]TèÍ3g1³ÄÚØw +e…0@D4ŒZ‚}ÔC µ“cì: ØM; bKâ“é
…€©Ü ùsÀQ^½©´F‚EFO58VI\D¹Ñ<úR'þŽPN—ÈÄ=l¢›’0ŽÖb÷tâh´z—aö1sc`Ìì31JweÂO¶š•ýdTºjcŒ8‡në§jšD/ëíeŽ2í›×XñݲËÈ£·BÙòÆ3ô—N endobj -436 0 obj +477 0 obj 1599 endobj -437 0 obj<</Type/Page/Parent 409 0 R/Contents 438 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>>>endobj -438 0 obj<</Length 439 0 R/Filter/FlateDecode>>stream +478 0 obj<</Type/Page/Parent 450 0 R/Contents 479 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>>>endobj +479 0 obj<</Length 480 0 R/Filter/FlateDecode>>stream xWÛnÛF}÷Wò°h]]úRعyˆÓF*Œ¢éÊ\Š“»ÌîÒ²þ¾gvI]·Ð"Ž`‹äÎÌ™3g¿]Œi„cšOh:£´º¸]_\½¿¦ñ˜Ö9®ÌsZg4JF£ÓÁñ’|!<>$Dµä¤}”–´äÏmvŽŒ%ç•.Ü––RX/Ÿ<‘ÉÃ7
žyé¨ÎíŒÍhH_ÏÏh³÷òÕúëň†ãi2AƒB¸Bfô(ʇfÒªGü™[S)ŸÐMéé³äŽQaV{<HÂÊX@/®·B»Jyh†ëã²µôÈúYû¢q¤tj¥pJoEÚXå÷ ón}Ühv½Lt½˜ã÷ þ#Ra^Òøº…iÂ<I¦ }¨jc½ÐžuG7ÓxZµ!8Âi§†îÔ`üžHèŒVoK¤¹¯½2š¼L¾1”NÊŠœªT),Úƒk8À56©Lh](ܯ¢,Rî’ ³ãN_ö2ºÜ“{PÝ‘5?Ú&B.-dÖìk•Š’ï’:súƒT@‹®A Îã§ò®š¨4Û-¬t€ö„!Ed¹YÊEŸÔÚF쌑¹Äþ,úið{¼•§ÌH׫6°;`ÕªÇ( ™)÷ÐBˆü34$y_ì¦[™ LÁÙ-';–3'E/î‹*’ß…qÚ¿HèÓP*4 pn;exã¼ úê’¸4ü¶§Ô4eF5¦½ @@ -762,11 +830,11 @@ a-Ô'tÂÕ%7îlPT ÿî`DÏæ(˜ØgWS°èX1,7@RðøbñœPŠa*i4ûW¸ï´Êsl¿Ö#ñËÇžøHÌ ¿‰ÅlkøèG›)¼çtûæl8»×”šÏNz‚d?©_z ÓuÖ‰‹ÂVQŽoŠ¥püƒþ“dËIÁÌÙN"ßG6›)êh4f¤â;X÷WkMAv1TÂÜ—Á¯„7¶|`lŠùfc endobj -439 0 obj +480 0 obj 1780 endobj -440 0 obj<</Type/Page/Parent 409 0 R/Contents 441 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>>>endobj -441 0 obj<</Length 442 0 R/Filter/FlateDecode>>stream +481 0 obj<</Type/Page/Parent 450 0 R/Contents 482 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>>>endobj +482 0 obj<</Length 483 0 R/Filter/FlateDecode>>stream xWÛn7}÷WÌCË€u—%Ç(Ømp‚VZQ¨]Jb¼KnI®”úñ=ýHZÛuz‘CZ’3gfÎÎþq2¤þ†4ÑxJQzr3?ùi~2è]^ÒþŸ]ã¶M½ M.gø>÷¦d%øa¦ù‡íýwo°æ+XŸ^âKÖ4:£Þ¸7êÑu¼Ú‹µtdV¤îJÙ"ó2¦L8·36vgó/'ýwÙ vG3ëd‰Pš¼üê÷{I 9ìÃ6[„†øVÎÉ™p’]âYJ+céþý
)§O‘äÒ)-Õšb)’g“]ç³Éw x1˜‚C%F TͦCî\ÌF(É1{&¥—Î]º\A®Qšc¶ ¦’,·šÀ%DÀ‹t)ÈÄo½ŠT&¼$欉%‚'dÜ›È$DÊSš;OK^Båq*1æ‘ò,lNiYàôF¸
H»I.ÛÙ\«P5ø× S裟kxNŠs¦;ÿøáö¡)JiYFÙQ6KÚ‰"ø"Zå:ò _t,§j;VifœSl+½UÁ±§(‘ˆ{ÇÜ©£½÷uƒŠä½Ê/΀Œ@ò8ouŸ6Ù?àQdÐÝJ—ÌA u¶Bšš¼r¯öhn(ÅÖT¹~€Ní”ßãÃC¿ã‚•¢œ¹sZKïC+äžàP]¡£ó}^Kf@‚Žt¨/}Ô/™sLšNhŽ¼u¤aZ{?Ä^%Ê£ 压ÚYúØœí¹Mëø9׌۪ò†—"YK-C¦9ëG\§•5)žÚ”F›ðþ&:F[ö·Çz¥CúGúsž G¶“?ÕR-¤R*A¬Pƒ•I³ãbE&MY¯Ž!€ù®25¬ó X/ú“Ž3Jô–ú¹³ýÄD"éC±—¢ŸYµCûM(Çy?ðw»¢Zkm®_ÑXHwá<Ïoà>\nïÏùÛ·#/2Æ^ Ôÿ{ÞPôÛˆÆ$[[‘2ßV&G z¡8÷AêI\™VFÞØ¢G74}%ò×À3¬x¢8ÇÀa˜}¹¸ÿ¡N°Ù¡jÕ:®CçEÓÇ•ïìC$·1y³¼;ܘPwk‚e~rÀ™´P$m‹+ÍŽœ\`ZtJM]¢Mjb⥗0¶ .Ξ´èz”;Èãó¥ÐòQb.yÿ4HFÉéC¸Eˆó¹0yhzZ×v–S„òR˜¼öBÓuGzÐ|\T\†)Ú¤º‹š³¥‚€‹pÓ' @@ -777,11 +845,11 @@ c¦SkV*Âû.nXã‡<ÙP`b5
–º™X¶Yº—¥‹iÏ_oç×ww¿·óf={ «s(OÿÝeU‰átÖâsÌ]uýþæš~¶æ@?š(O! ‚‡g6Ö-7wg£ðJøO_M'³Iý69°=¼Úürò T©wendstream endobj -442 0 obj +483 0 obj 1546 endobj -443 0 obj<</Type/Page/Parent 409 0 R/Contents 444 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>>>endobj -444 0 obj<</Length 445 0 R/Filter/FlateDecode>>stream +484 0 obj<</Type/Page/Parent 450 0 R/Contents 485 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>>>endobj +485 0 obj<</Length 486 0 R/Filter/FlateDecode>>stream x}W]O;}çWŒª+‘JÉ惄H÷Z*Ú{IÕJ¥Î®“¸ìÚ©í%Í¿¿gìÝMXè ¶Ç3gÎœÿ:Ò X¢¢—P9؃xi™¾¦àókÖ³¶áLÈBôJøHÚPEGe›ÐµŽ²ß Y°A¹Ò
oë@ ‘µ&hfQ“£¿i/ƒœ‹z³9bMß×¹YŠüH‘ËÐIð*jüCÔ_x´Û ͧXH¼K¥Vî/ä&¡ÏV®¤E<ûn+œœMƒ“e©"®¨Å¿‰‚q_ʵÒAnºL0Îî1¿xœIbÌ€p° IxBCˆI˜4]àŠCó*q*-ØDG· ‚€è°ZK ¥Ðy®Ø}B—zo“Ū`k#)ÚÁC',KmÊõ¦Ã£6»\fè>hW¾Ì¤&‡ÒZ ðƒÙÖýírBã®Óô`¿A]Ëè²¥ƒÜŽ‹ÎÕººÔêw[°ûÒ§ý¨·—pO @@ -789,22 +857,22 @@ X¢¢—P9؃xi™¾¦àókÖ³¶áLÈBôJøHÚPEGe›ÐµŽ²ß …^:4(ÔlÜo_ßYi
¤®:ªà›áu<ßtÒ~élŸ+&ï;Q,E©tÿ9hÜPmÅ«‹£{>G8'ÀáLa0ðÆî_¶ÜP †Óª:7L.’ál;œàv-‘уº¸:·_ît÷iAtuMîî—?^¿o»‰öS*L‚…EÖjß¿©ñ:üšÔµÍ¤&“(|>ÆÀèÆ-šQÇ @õDz„"¶%S¾ïÐß «\W*Cgªxvy¨¼e‹Â>:ΕÀX¢`©ëUÏ ”5Á>°5ÅÈÈ¡†2C'®&O^à¾úÇéE‡N²ùŠ‹‘ðxU±·Ô¥ÔrÅ{zœ·• sr(X<Ñk‚&ÀŒ½6˜ 2˃A“™Òó6ŒÈ ÃZ¨¹ßsÇ(ò{fÔ· õ¨gŠ‡ÑdÚª^~éu›œFLÅV,UÎqÉVÐÖŠúÂW¥3~=Ü-* å1>ÂhŒ/!¡|EïˆaB Xù«Á¸ÕñT_ëŒ}¶x ªÞ›Piïp‹ endobj -445 0 obj +486 0 obj 1752 endobj -446 0 obj<</Type/Page/Parent 409 0 R/Contents 447 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 22 0 R>>endobj -447 0 obj<</Length 448 0 R/Filter/FlateDecode>>stream +487 0 obj<</Type/Page/Parent 450 0 R/Contents 488 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 22 0 R>>endobj +488 0 obj<</Length 489 0 R/Filter/FlateDecode>>stream xVaoÛ6ýî_qU V,Ùqœ¢
Ð`ÍP`ɺƬû@K´ÍF"5’Šë¿w%;n²CÃywïÞ½»ËߣŒ&øÉè2§éœŠzt³ßâMFË5Næ‹KZ–4I'“ -‹äת¤‡»j„s;cË·ôfù
Y´HÞù}#ÉàÚ“¨ZI[i%‰Œ¥òd¥o&µ&Nv‘6ìcBãlšæˆ–°uàºó@4ÎçéŒoÝË]€òùß¡h\P®#Ô\}‘žþÛ£•ãßà4úœ
„
ð>…˜(ä\=ÕÂ[ΟŠÖZ©}¤ÊyceIkP…Sài´gÌßõ;CCXG%ž_RÛS™ß3¶ÔÁ| ”vªª‚í §Uev!Ãr½¢Þ.”oÍNÓƒ¨Wb€ñBHÛjÇÉZƒÜ‚?W¯‚JІ3ñ(žÆ+£EE$ì¦Áá¹Fj½Wzs@£E-i·5N²TN(ê%F{Ó"!‡šŠàS¢{ãÁ:×aÇ$2:ˆ5 ;€ŠÚXS7¾+*Vleñp@̯Å
²äµ®£‘±‡ ¬ìávàöüöâGQÀÒùm/Û„PªR:µÑ(9‚£µ!€‚|= ®¨U¥diè÷ûO„Bu¸€0Øtî{ h#g¥)ÂöàYÊàÇöH—qœtue÷uÆWù/òtÁº>,^(FØñ ŠäF`am endobj -448 0 obj +489 0 obj 1146 endobj -449 0 obj<</Type/Page/Parent 409 0 R/Contents 450 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F2 5 0 R/F4 7 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 29 0 R>>endobj -450 0 obj<</Length 451 0 R/Filter/FlateDecode>>stream +490 0 obj<</Type/Page/Parent 450 0 R/Contents 491 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F2 5 0 R/F4 7 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 29 0 R>>endobj +491 0 obj<</Length 492 0 R/Filter/FlateDecode>>stream x¥WÛnÛF}÷WЇ*€D‹º;@ ØIÕä!(Z«ŠªKr%nBrU.)Eß3C.))M‹ à˜ÜÙ¹ž93üë.¤1þ…´œÐtAq~÷´¹ûqs7V+ê•{<Œi2›3š–øûa…?KM;¾C¨é~Aü~ý@“1mvоX®h“È9Þăש:Tº¤i@o«L±'EïM\Zgw½1®*MTW:¡µÉô‹ÍÇ»1&3(<Ÿ]¥sªJÉô¬òH± ó™(Wqj @@ -814,113 +882,118 @@ P½¢çÇ÷O_•ÁÑ4AôÜmî6•ìÜ×ìXýÝcÙ²º‡$sÀW,õÝÙÛéÑ9B¦²½køìFi·³œé„äh0Í°nŒú ¡ÆèšO¤ïœKØæÆ2va]2›hv,v™ÉM³‚JðÑõœ“ª#,þ® u´&Ÿ%H°GÏ °gå‘ÁD–,áÒ½pE ó¦%›Und~Ú²Í7~ùoOjâ7[ÎÀMø¨Já”_`ëøåîoL½!rendstream endobj -451 0 obj +492 0 obj 1534 endobj -452 0 obj<</Type/Page/Parent 409 0 R/Contents 453 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>>>endobj -453 0 obj<</Length 454 0 R/Filter/FlateDecode>>stream +493 0 obj<</Type/Page/Parent 450 0 R/Contents 494 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>>>endobj +494 0 obj<</Length 495 0 R/Filter/FlateDecode>>stream xuT]oÚ0}çWœ·Q©dX€Çv]ß6mÓ^x1¶iÜ;³¢üû'¡ÕPG„ž>÷|\ÿ™ä˜óɱ^`Y@V“ûÝäãã yŽÝ‘+ÅfÂ<›ÏçØÉ飱âtêtDS#–¡«îd$NƾD‡ÚÓKZ†Õ±uþ¡^t®A+l¼…° ! ñST‘Ýìž'sÌE¶"æôWÐ>ÀY<ÃL´,†<mc€Öµ8x×ÝÃp¢×ÄcEÂíÏdŸþ¬=DÄž¿pö{uî¤Ô!û„¡ñ=_f‹„žÈ8ß/°Ÿ¶¥‘%D]kÁó”ñZFç
9T‡öö7@/üÜô†ÔlÜÅ#¼«½‘Ú
š-_u0êÖËòe7¡(Kj³Ú¬ù¾àŸ’ǶÈ)ZrìÓf›ÿx¶Ìr>øæ¢ ãÍ_Z>[$ƒ§¿UÔòUa«µJ
4AŽ¥ 0GÔ^Ÿk U®±iÁ:;£¦˜€J(Íé<‹©ã¹³‘t&:A”éR+ºTMXæÇ;ÕpHjÇ£Sb*JÃxÑãÎÏ0ð’cngëlƒ‹“ûE±×/¹N˯9ûÜxÏT%ƒJíõ‡@L5z#£éazªÐ“aÖS0`EECéš“"étröRýn7œ5ý_+—V™· eãMìP7¾vA‡Ûê·ì‹±e“ƒ¾Çþýá2cg¥8k¸ÖRçÒÔ¬´êʇZûÊpœ%ÎtHCK¾ÎR¥ƒy²Ì©£œæŽ®+sìź}3LÞe2ºw…¸p}ÕbÌöj»e¢ßË6ìo£¼Xgé¦JR¾ÝH?ï¾Þßá»wÏG<8ÙTtS$ë×ÙP5ʦ׳°Z¯˜…Þœ|•ö³›“¿¦endstream endobj -454 0 obj +495 0 obj 686 endobj -455 0 obj<</Type/Page/Parent 409 0 R/Contents 456 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 35 0 R>>endobj -456 0 obj<</Length 457 0 R/Filter/FlateDecode>>stream -x•WÛnÛF}÷WL€ -€ø8 -Ok '›,ëÀÑdEÂдUýN'w©¬Žé}Ñä¿é…™#žc’uEàü¼3•Èìz,ãÁ|Œ‡H& N¢Ø?m¡cáy¬$7Ów· ^Òp¢hA Qÿ -ô8P®mË^²«RË?ÆBTè¾<}¸\¸¼ö|â;{ž3ìÐc›}HõÂ*×N²Àþ”KÁºË7¨ìbµ)e¢–®É£¶Í³”ømº6 ”t¢lVýÈEóa!mç…Æ'Õp?µ+·åífÚ! -êr€{¨0r¼©…‹šoyÙ^L®G m¼ætàñ‚]ýw.ìñ$öÎcâúZH¶“Ê%è0Ä0\è&KAš|Ú ýñ8ˆ 9
úgÑÈ?ù†ƒi7ïµj›cð·Àœ¤ -Scà²ü0ÈÌå³Íà¡ñÓ&=è&ÄÓv}†˜7†¨vã@ThƒÃ½¨žLa#û±Þ¨{§mH’ù¬s‚^²óg§¤jÖ¥ÐZm½äÆ“Kn<<$¹Ù/X°8GN_~yœP”“›Û¯¶Ñ¶"†©y~¼ósæ±…8oL
ÂT¸&^ç1[ -ùÒÜ•b1DZSÌ3ø²4G?³H¸z$Ðñ6YÛÃYåÎ<ì áA`]1¸¯±úôÀš„Ã@Ìļ$¼â
y%ßsoyQoU:AìzVeÔœ¯ÛŸÝVFï ˜½‹0ü¹%b®Ó MNô±!“/0K¼¹Vcc†–²¨rY³< ó°J0™ò©ÊhH„Ån_ÚÒ§µÈ £ã«RÔ«W¶ŽEµPu%€ÜNýBn*Yf"ôVE MKo̪<Jú«jœ®ì‘¥{yJ>Æ`×™;íÒÓŽ“.]„ýBÝÆT]–ê¬kø@Úõ"h{t÷rN&0¥?w®à°à5ñ'õõûÑ¿Ò+ºáendstream -endobj -457 0 obj -1716 -endobj -458 0 obj<</Type/Page/Parent 409 0 R/Contents 459 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/Fc 12 0 R>>>>/Annots 48 0 R>>endobj -459 0 obj<</Length 460 0 R/Filter/FlateDecode>>stream -xXmoÛ8þž_1W°.P;–,Ëöú!mÓ½ -hŠŸ€!ÍbJÊ«w›«ÛÍÕt²\Rÿ¦÷XL)\-&!EË>Ç1Þ´¤žÅj>›Än'Š&Q»YØ„‚î
‚®?NiE›”ÆP²Iíö”6ɈðÚ7ÒÔ¤¾Ò[:IózóåjJã -ð¦(7Ô™RH…:’uТΟ%Q!ŸeÁÏhI¢šª6üp&°Ù*Â×ÒÊ+R:ÅcØm©¨¥s0§“ÅÁYRR°ˆÙE»ò.bcs ]^HC¸.ª*“ -'DRÚµ—<É«%²—<\—"X³ÁîYúÐzS/1åv’¨j÷4š?½¦RTt{ë_=>º#Ú)M¥ -ò -Knà—XD¾ot^í‰lý2çÎ*€…óåY
o‚%Rª]uqš/W6å{pp"iùG“kYʪ¶º}t o"î½¼á»Qp¾;Xcw#²ýÙ?ÝõǹKKçÇ¥©‚áS3•Y¥ÈÏb—!5OªÑd¢ÈZK™"/îv6C
ó¢ _-ªZÚÌæxŒQã`fóldÓ—p.§}¢=Šr+ ÌÔo8Ñ8û ¿‚*Usci¯«÷9c‹ïÑMSgJÿ`è^ÕòG‹ðžF|WZg¢¦|ÇÈkû5¯RðÝoœ?Hûs_à»Ãìç\Љ›Ï .¥íɤõ } ŸF¦I2ìEªJ¤–²ÜbÇ= * -Q{ó†ë’¢i0 »Ã5vÁîóÿƒ|\.=/Åó·ôN¤>ÜQDV‚2»ìƒ0.PfýÂ/Èj›Z/²2†Sþ÷}ÿâ[´<
”eQ ÈŸÄW0t28©©PÜLÍ7~dÜZf8€fJY#áSÕ÷%3[ ú—@çOŽäá”Úg¿H¤9ÒÇ/¡\AõHqIéàŠ8™æpPÚŠ”P}¬ -%RV£v”jnmŒa>(›¢Î¨6I‘ƒ(lhô¡“”šÔpÔ -8‹“¿ràôsž ÈrL¼Hƶ-…ø -&!Òj Ö*C;&ÔØdÂ|hc]ªˆ¿'Ï3ï½üÖÍ÷êj4
[ɽ½ðÎnî)ÈÂËš94À^ø17ç¤3ÕÑ~צŽÃyKú¿;‰c~y7)÷¯ÿÿ:[ÆüÙ½þF¯üm¿úþÙ»ûhêÏñßÁÙÕüzµ|áè,¼ùÇúï7ÝéÁQÐýMqÈÄ¿o~[¿(áÓÝú±0T Ñt:}ñôzý¾?|qzŽR¯ßÛó}I
f„vŒÞš›ÂÑÍfs{¿¹û|ÿ¢‡ÛŸ¹{¸ý@ëÛ‡Owøö‘ãvÖ¢ÛV-:“Fæ[‚½x:AòrÑ ‡Î¸u’HE$ -"D¨]9êí;›?‡ém@Âÿ?\„}gÒ’†·n¨¶Ì¹zœÙraþÙ”ä97Ђ4Ù<z/Öž -'—¡œÍŒ6çÁìÃÒ&p×~îÛ¾Nw»`@ï–xMÍ-ìAÃCU[ñQ90ž!÷Ú©pÁÍ[Y²3òt䧊>4ö“ƒE€I=r°ÀÛÑÜÂ(‰Â‹¶äs~ç<·ms[ÚŽÑi§µ+\'AÖF%¹íÏ}ƒFª< -endobj -460 0 obj -2035 -endobj -461 0 obj<</Type/Page/Parent 409 0 R/Contents 462 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 51 0 R>>endobj -462 0 obj<</Length 463 0 R/Filter/FlateDecode>>stream -xµWaoâFýž_1BšJÁ±.ÒU"—äŽ6!È]%r{ßÙ»®×„ðïûf×vI+tM¼»³oÞ̼ÿ}߀z-jw)LÎgG—³#ßë÷éé#_á‹O>:ýÿû¦çu)—´äX„™úÛO¯ÞRСÙÖ»}üÙuŸfáqÇká—¦²(bµ¢‹<~¹¡¥Îéò16öá8U§¿Î¾^u(œf«[dzµ¤XÅE,JÊ#zIYy -kT`ËT¤AkmŠ_Qe7%‘Ìi' Ń$¥«£Y4$Œ‰WJFTh¶”zħfÐöZ€Ø•ûHTç°]Ô¶bÃÇb¹µhƹÎd^ÄX -“Xª„ƒzaSËìL!SCšé:¡¨ñ9V‘ÞÍè±ßmœ”æÁª’2:ˆ=8ßTQ™®rnÕ B,ƒš=Å;B¢êU•DUlÆlR.vÆ&b¨•å`r‹l -Üg}0þÌ×Ê-ãD½}CÅÙmЊ™gn38þj[‡w°ÎŽ;ŠË1%àYeòá(èö¼€Ú~.¤Ô -ú^¯ü–ÐÔN6øÊgŸï’N[é•TB׌H‘Sv|pêQÞºowtÛŸ»‘ïØÿžR;ðk<‚z¬² ílõ¦”Œ -þ!Â<]µ€Y¨zÖh¶¾j£vj³FkÁáÚçÞ¡päÊÂ¥@=é0hRl©é0Ô3ƒë[êÅLPÖ”:Ñ[N*„R>Š4CK@ðךg$<ƒ($‘ílhzXE‹—ÑßtzåÓ[ž$.× &˜Ÿ¬†×þ¢Í¬45ïlßü-(öfH
‰j(‡“†% -ÏC«ß ²¿ý¥´Ñrµx<ß“<Õru…Ôâ…cp¨–šë‹M‰ƒø§Ü1B.Ñü㘮Qjùïð¢ã#eˆÇÇñ´º¡ð#nh¡ÿß:Óø7½âÁw…²R´ËgqX&beÎæþc´û~E÷³=Šƒ4¿ÇÏøöÃíýý:kZ\¯nŽ¤ ó8ã‘èlîöž;ÝÒÅdøérBƒOƒáõàüú’®n'4û8œÒx2Í.''¯Z/ǯ³yµZåųŠyLüá!1ïïŠâ7WX¶vž¤òûÿž›Xüaq9½ê×Z×…4vñ^ŠšnÎx¡Ó_ùåB‡˜ Tù^Û©¥¥^˾ç|ïg§×©^‘‚ƒÞñçÑ?ð:©æendstream -endobj -463 0 obj -1656 -endobj -464 0 obj<</Type/Page/Parent 409 0 R/Contents 465 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 66 0 R>>endobj -465 0 obj<</Length 466 0 R/Filter/FlateDecode>>stream -x•XÛrÛ6}÷WìøI™±)ñ¢[fúà4qëN⸵:éƒ_`²˜„JVܯïÙAQ²=M“ övÎÙEþ> i‚ß!Í#Šg”–'ïV'V'“`± ý£~ÀË„f‹žÉbŽgáQkZóXÄ1ýÛÇ—ZÒj£g8j•Éò„Véè¶MSmíº-Š'²º¡Íö|[çUC¡¬ÎuM¿ÞÐGeuý–“ ¿Õu®-ÝÜoV_‡ðg>’Ο¡;ãË%… [Çž$fö“ -’€.²,¯èZïè†ëÚÒc®¨Ùhú’W™ÙYº^ÑÅͶ8¾L(Ý‘çÑŽÞ=Q¦×ª-š3ºUå½"³^ó)ª(HB v£jøy¥3Ê+r§!rÚÈ–÷Ajªõ¡‘ïdON½oAœÒÚ™®¢‹ÂÒßsÛpyÅ_Oè<Œƒˆ]k6¹í6þu‡îcF¨ÿ¨ŽÁœ»‚IDL»1Ük¸ovd**‘óh†¤ÃïÅW•NDÖ¢ZlKÝši‡U†«:mMª¢Ï[]uA}ø~7ºÃ/|Š¢ß½ÙfC*+ó -‘Õª8²óAhHìc^èìY½å¨6¦!Sw™|f} ä¼£ôÝæ´Û|>ä³wÍæ².DðÈÞür3¦É¨*i¶ì_ -º=¼–N“n'/ß±:M`r°:x/)šÀÜ`uøŽÕ®Þ±'ßðS¢~ú<¡¤Óéäˆ#RwT"ë¼s8ù‰ž´´õlÞË‘ž"#T†1×ÑãîÍ‹é†d£a®ãE7¦ƒ¸¤Dœroœ>„1$á4âuåª@F ë` -ÖǸä -"!ŠyÖy4õB‡$õ{xœ -a8bŒ úKë2˜wo=!“ÉTšÚ~JYm4¦nhp¢ÜºÌ(><‡Î¢`zth/ÏÃ{tl4Ó…n´/)þ1YX£|µ.Í#;?eV‚p_œ!º0X£â%ë®ë^£â¦ÁÍâ1jtzÉà¾qSݘºÜíùÄL–™i?X#ë$ÔNl‘jkM*úQÆ)nÐ*Ýx˜;™ƒ*S—˜³ž¨Q߃’qòñf¾=;ÝÏŸ?á‡tyõñþ‚aœ¢Îw‘IÅ•m·b¶C^ªÁ8œÈ?8—ucÊÀ§á(ÈÓÒ‘uSí%—pE¦NÝØ8LÜ)¼ã±Îbêôœ2÷®Š’1{k-Áwi¬è;ß‘eÉïa”œ)o kýw›/@ -Çç‹â¨m]³ˆïžéÎßÞ‹Wòåñ$˜ˆ„Žðx]‰Ë¤1ãÉ»â!v¬íŠ -ó§ªx)€n²´6蔨ÄÔƒ”}m'xFet¯ -U¥Ìpcò‚úq_Z>™é”„@r gGgc”ðÓ;ÓÌšRsú©|#yQÀ!ñ| Q‰¢¹›gâäÞžÍ31¦™‹‹£™ñY‹–ˆ¦Dyd(ÇsUéª-¬œÄnáY±CÜK¯zQ8= ôëÍn“ƒ“)Z²ƒKºƒË’ô“ï®Ü`ˆG\bt¥D‰¥è®.=½†pºÕŽþC›ÂùäH¼“ dº*…–V€"îš|ò²´‚Jö[l•{)¼Ì3q÷Ïë«¿ˆA‚a«c
‹DOk\Ÿ]ª@ÛK ƵFn2Ü8âÝ(Œ–‚Š¾ã²*o}]Âxr„ƒ¼bpãBĨîq7& ×Mß—{÷wúžlÎwæÄŒhÓ4Û·ãqÞe'°¦S
:¨t3öýË¢#4í4üðe×~¶ÈLÚ²¤ˆ—ΧE›r©ãlysà›£Œ/yù}ËQ‰°C,n“xuó—»yve -|( -endobj -466 0 obj -1898 -endobj -467 0 obj<</Type/Page/Parent 409 0 R/Contents 468 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>>>endobj -468 0 obj<</Length 469 0 R/Filter/FlateDecode>>stream -xWÛrÚH}÷Wô#®
2Ì%/[¹Ùqí&aRyáe
0‰¤Qf$vkÿ}OF2(8©J]e3êËéÓ§›¯1
ðÓtH£ ÉìâùòâÕòbÍfôðÇnñf@Ãi4¤ñlŠ—ñ`Ž×VцŸÀ!Ì´pýêfNñ˜–XŸÌð"ñçZÊÞ8EqDŸv¢$íè.+¬ÎK÷ûåòóÅÕ͘â¸~®?œâ¹^sÎwI“¦J–Úäd6T“:ÚK®* -cKo©Ü)Ú\a£È¬?œDEoaͽNøl©¼´"E…qº4ö@:‡±Lxûø|+¬¿ûIç‰Ù;z»$‘'4¿¾šÏȇ,%Vßã_!ä±UŽê<dÈ£? -q3qO£Mê?¤\)Îd}ðiœc_ÄQ„rgß–{<žùÞ?-÷("®[ÛD5Ù~PáÎMÆtIÓ2HD)Ö©@Y„m£LPhúZ)«‘Ò½„Vʈ -½^.”)¹¹v8N¯„ÜuðmD,T,N“ÖÙN@ÑyΩ=´ßÿé…‚DȲ‚¸Pû<5ÂëK&“µæspÚ¼í8g.êæÞ?ÓÛ)ønójq$@Â?R¬AT´«Þpå~pÒúçÇa³&9“«ŽWÏy‹»!Ùõ&kæ«Ÿu©&Af{”ߤ‡úH“¡™˜P>¦’;Ì)YY]Hî”üB?úD¬S•Sk4¡õ¸{LIF#‰Ýá6Ô:Î^8ë˜õG×#îM§+x3y¥ƒsRì1½:åjµLéf’6jÙXê×áô_¿û´|î4®^݉ª´¢¢Ã¨&g*+xÄs2aÆ.3ª‚9ÉÞæ+øÏ&Žç4ZE•^MQA–‰TçŠÊ¦ä¤ÕEùësVÐíò߈û5¡†Å+þF -Ù³“ÉÓº.~Ñu8EN°9WÆUp¬
ÔÛ㱺䉂M8 è„Èý6ãµäÐèkSÍï䇕^„¢4¥ÇR#w~wH1Ù/9”¡Õ™ITJ¹àÊ@Wö -zÎúœ3&’œÌz&h½ÍùŽïz1”Í”çMÊ«[;äÏpÒu9Ú?š1‹6^Ð’ª -ÄÉÓÔ×H"nŠ=*ËÃIXSáí_Ý\7rá²u½ËÔŸ7-Ùó†:wm!ÏÞõ¤½ºÐœÖE¾®—L௠æáa-õa -endobj -469 0 obj -1439 -endobj -470 0 obj<</Type/Page/Parent 409 0 R/Contents 471 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 69 0 R>>endobj -471 0 obj<</Length 472 0 R/Filter/FlateDecode>>stream -xXÙnÛF}÷WÜæIlZ’e-y)œ6NŒ&Ý,À} PŒÈ‘41Éag†–ý÷=wI¦] Š$¶¨!ïrιó×Ɉ†ø3¢Ù˜.§TÔ'–'7h¹ÆÉt>£eIÃl8Ò²üÒHÒkr[IÑ«JÖ–dSè®qÒÈ’v[Ùª[ÈÆ©fCþÞÛº5ªq–œÖYéh'p+¨%ÙV’”µ´§Ëo'C:]fcx¬¤ÛIؤGa”î,Ù®mµqðUT ->H˜b«œ,\g¤Íˆn´!ù$8†3ºWM©w–èç%©¦¨ºRZTõ(w^Ò»ë÷öü~Vš{Ænoñøôx5ÊæïˆDSîí.®¨UerƒE«tðQ69 æ‰^[|}Ž§Ù„s]P´Õ;àE
~ï¶Â¥„Cð8’hÅètm¥E LÖH^€€-
À¸F¶ÖuN’‘¸ÁÐNUU/U®êÎ@¼0+ 6 ök°…ߺ•Æ)àW*Qé
é¦z>€Iä -VÂß[eÀàþQŠ*às„¨vâÙRg -ø¢²¼´0S -*‘ôþúI# -hrõX…*u²m¹¸-2ªTœp\]¸BQÄH£daö-¦§<´–±AÞ±üi¥Ý–£îå~‹Š©èG¨óÅÕÅbÞ3J -'¾V„#,xˆ¹ÑZë2öðqy‚æI“Ùýl2ŸáóÿŒ¤u赡ø¹×N&ßÝ×™Wæà«Ú˜?’_]GFa+{b@`uœ=±Çãö}>æö=ø„nÇåIõЩEp<á[ðUlE³A¡|°“ º…zѺõ#¾{ŸŸþ¢NÙÕð¥as(x#Y©Òžõ0÷Qû¡ù„2fZ1º–ÆXQk]UŽ`ÕÖ -·µÄ‹›«Xîãñ(»¢óñ<tÌëbëºfóÝiŒ3̪ðã÷OûËé"›FìGÐ -‰>_øÇ–ìc•åaW„Î«Õ -Ól'TTè
RT¥f+¨ñ ±µ#ìC׉¼óãÔÛçA -lt…æn©9gå°ã¶ù׋îq5F›xÙ@RÜ^gÓ)ŸF•ÅŽRì%â³Ùoª„‘+Ìı¶ÕØ{òAäËÅ¡¸ü”µ£ú¯ ª:uè+¯lîÄ²Ä -tâg6ËÍÈõÞ쯨”§Ú4XwJ¿6Àý+šY©FRWcÆ߀-•ß?•ç%¨pýò:žœÁzÚQE^žá(ñ1ðõƒòvõaAk<Y]u¼_±‰#ñ„m+íy‰Eôˆë_ï¹Lì¤ý2„U(¡
¾SOð• -ÄØÌBô¯Ö™5Ò]p2;þì€J~±ãýɿؾ©±¤¡½Æâè¼ü§ÕsׂÑt–ñðfpˆôîúë‡k~íû†wk¬+EÇk¢GŠƒ<O‡Ç~Uý[êd6I»ÈxÈöìo'ûZÌendstream -endobj -472 0 obj -1840 -endobj -473 0 obj<</Type/Page/Parent 409 0 R/Contents 474 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F2 5 0 R/F4 7 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 76 0 R>>endobj -474 0 obj<</Length 475 0 R/Filter/FlateDecode>>stream +496 0 obj<</Type/Page/Parent 450 0 R/Contents 497 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F2 5 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 36 0 R>>endobj +497 0 obj<</Length 498 0 R/Filter/FlateDecode>>stream +x•WËvÚHÝû+j‘9Ç$†ìœ‡g2c;N '‹qÔ@g$µ¢–ÀÎ×Ï~ð2™™ÛÇ GwÕ[÷V?‹©Ÿ˜.ºQZœ½žõ®'”ôi¶ÀÑå˜fõ£~WÒΛ•¨YÓ ¢ûZ•*—4m«J×
©’¦¢˜J¢$z|9ûfWŠn¥îE%X«3ˆâˆÞ—M³6m”.Ý“ŠcÿdrÉϽ–KU–¼ÁF5+jVÒ.ܧZæRyîw3n{Cö‘R4j-é‹*3½1t7£*ÄYÈt%Je +Cª¨rYȲ‘ïÞ§n|á¢[+At;í~ºCÉÈ.;½ÿðáf:¥R2£JUòáeDÀ@®•n
emŠ!½ —.ó'òÁáQÞŠrÍѶ©Èsù‹É(hYg†”E–)Iä´hK‹—ÈUó„…ôZeXxþä—ììÃôÛ¢$iÞfÒ¼â•QànX:Ôl¡kPe®EÆP[°P߬Š5ÑBåÒP£·€N†½É¸w7ë%̈4W +lh"e¨ÚõÁu‰ÍšJ
OÂ/nÀ3¾·ª¶’ÏéXÖì”' äTÏêÝW¥i° åm½¬¯´±V§ëÌ5~€Û.Âmµ¨u±•© ‘hœ+š·Ë£å#ø€
¼³,z²Ù¾“JnH +1¡°ôQº¹†ä$ÚrÊã˘"—QIvý€:¤iÁy6íEÊñ¸28³0ãšäãJÍÕsk‡Q†±`ò¸«Ëƒd`¥L˜íT‘iŸäA:!FÔJ”O´0^ˆ´mpòâ,3Xy ÿl%ŸH€Ým£rõ™@õ@HŒÞ¿½•†ƒÚàE`•çzÃ0ÝNéÏ×X§QiŽP„ + +endobj +498 0 obj +1754 +endobj +499 0 obj<</Type/Page/Parent 450 0 R/Contents 500 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 48 0 R>>endobj +500 0 obj<</Length 501 0 R/Filter/FlateDecode>>stream +x…XmoÛÈþî_18°D²H½_pœ\ÝhR÷ìâ®8Š¹’˜\Ý.iE@|Ÿ™]¾X‘]DïÛÌ3ÏÌ<«?/"ã/¢EL“9%Å҇‹¿<\ŒGË%uov‹‡1ųQLÓå_çs¼YMLÓdæa$Šù?2„½ð´oØèêfJQDŠi¾œÑC*ãczH;í4í•U…®´uï(+“¼N³rKo¾\\ÝÄaí`o³S(µÙ>6Y®ýŒf÷A·Ï;R°gy›TïN2Ué”T™’Û™:O©4ao!î7VGlú/½˜¬Æ£ÍÀ„ +šN£ExÊéžAƒ3‹ƒ}wj‡C²’J}À‡«Tž«*3¥ÝK…YY¹1¶ÿ“)©ÚeŽ’*·úÑÑÔ…Voàge0C°³o¬š/[ƒUòâào9µõS¶µÞ§6’¡è–Ë7,ÙðÈp²äÆєxHbvj’ºÐe5úFYñIóY<š +Ÿ¦3°Ü_RéVÀAO=™ÅÊØtÔýHÜ#ÞÕÍŠ¢)Ó'F`WfÓQ<ŠFôÑjxNü.dzó›ÝÑsLÃxÁ¾Ý–dlêÁwõ~ol%A¨÷¹QÂM³¡> +!Á_`Q» +Ïï‰)7Ù¶†ÏJf ¸LÍ|O[3>œÞ`‹¬€ÞÓÃ/O°8Åž©§Ù½*ÖêÒQHŒR厜!±”÷'ÌG¦)+ØUVôè³è
1«œ¶OY"IÐ;^X¼>ýš•©98úüཕùÈR&åÞš§,Åpú;H°¸dÄß6Æs0ÿ»£yaÒlslÍѹb=bä<d8-áÈi™D“çæÀaä +õµ
i5Ç)&¶©4 +5?Ž"©zÈçUx +ÙÚÄQ|RöZRK8|‹gE°ÀðXÀsh·Kpêg
³*M›¾Ò?²À=súÌ€þ3FW¬â½±l^ÿ7 +Ìß3 8Xñâ–)ÒÄ'¸ÑTÞÏúôfwEi¬F9´P
kÍâFÞÚ-·@é˜bfß +endobj +501 0 obj +2125 +endobj +502 0 obj<</Type/Page/Parent 450 0 R/Contents 503 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 51 0 R>>endobj +503 0 obj<</Length 504 0 R/Filter/FlateDecode>>stream +xX]oâX}ϯ¨E+5#%&Òó2"²ƒ”& g´šÞ‡‹};mûÒ¾vhö×ï©ûÆéiVQçÃØ·ªN:uÜ_/bêá+¦QŸn†”ä÷Ë‹ëÇ[ŠcZ®)¾¹‹4¼»¥eJ½¨×ëÑ2鎗ËÉl9}žýƒh>ùåÓt>y —Éüãt±ÀÕÅË?.&˾ß>ä¾ÍÿÅWh8º‹îhp7Âïñû¨O¥¤…‹:ðQû4¼íGó˜Ó‚t™Ê’*MI]–²¨²‰4%A…ÜSZªW÷éA×´ùJÐV›ê’H’ôšª=žÔEª*¥Cym*Ü‘¥T•µü‘s +^¦ÝåV’H]ÕFâ.ût!“Šðñ)ùÓÄ+¢Z¥¯GŸ»*’®”ZWá´Ï?Ǻ~L|µW#à\Óîçþpd?</fÞÍ0ÆøàrÄ äþÊÚ +1ø42[Qâi|##-ÕÞ•R€PEvxG«¥r-ꬲÇñÄ‚ä‡ìv8B?dq¦„)ëÑíàøç"‘ÄC³eú&ˆÆpE¥üZ£¢ôXR*_nEŠF£eï>¯ý’ŒÊwÏLoxs\Z ðyèymT±ÁnP>wué(Ó
ì8’ãÔÕ.&*tl]êÇü¦ŠTï
Í–4À´$™‚\DD3ñª6H8LpçÅ‘ÎtZy¡Lú¢1è.Wœòo`e¶º†tÉX* *"³œäJ0,>a°ƒÛ›‹*Ù2U€j(ÅwýT…L[ 2ZR64¦Ñp¼gytíe9@s×NBßSùbñܲÎ6eCŠ/ZȪâ$¬bZíÉ7L_€p:'ˆ{š“v‰üÿªXÕŒå÷¡ã™ˆdQÝó@Y²©· +„ÛØY¦÷–Ø.¸àä5Ó àCZ|#@åÿŠ’Ç¿ÄlyÝçuì¸m"W•Ìw¶‰ˆ÷ª°›lÛ•z'ËŠ•‰.Ž˜ï·*Ù¢LNFÎÉK@0´¢Ý¶:!büm$Y–88‡<ŠÛ§×j&_¬Ò*Äs5”ˆ¢ÀvÄ®I•Ùeâ S4˜‰æÙ`óåRÌN&j€jàòågUa*¨L/LâF3Y¶rn `ÓoE|ÐV÷ +ÙÇÜëË'Ë»úlñÛ„aávh·p|Æ’ìMüܾxSpÜWV!Ù‘±ØصÍå쪡¨|=_x¤XBí.µiâ6·ªìÒä´™çìåZÀñ"»ãqœØshþWa£bŸÓ9 "¯8gQƒ“(¼]ÙW¸®ÉW¼íÚ]^¸ûxÁ̵.\:7`Tj‹ÆÒ÷F¦Áh¿y(Õ¶þÀÝÅÇû£XØœ.YTS§Cí¿W90c猱æV‰âp<‚Ûê3kÄfká]ãÇÅÕü僕H$ øœ§g¥¬±Œx!è[ù½°<$~’ÝDµ’
¾(m¯päœÁŠˆ¾•2×06¸u¼ÊqÝ7Ï怵å7(”!Wk¼l¶b‡¥Êv¾QW΢
^g9yˆåc‡ç1Hö£ Çï·ÚË,»ú‚
UЦÔõζ׽ÐmŒwÚï¹Å;Ï‘¯ü_ +endobj +504 0 obj +1872 +endobj +505 0 obj<</Type/Page/Parent 450 0 R/Contents 506 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 62 0 R>>endobj +506 0 obj<</Length 507 0 R/Filter/FlateDecode>>stream +xµXkOãHýί¸B»Ú´DŒí' õJiAÏ°ê–¤§WJúCaWˆgl—×åØ_¿çÖ#q2Aš‘fh5J¥ªîûžs‹ÿžDâ_D£˜ ¥åɧÙÉÍì$ÆcÚýjž±i0Œ‚„†ã>ÇI©‘´ä+Ø…œí/œ?ÿ|IÑfKˆOÆø™ýfioÄÁ 麮UÓ’ B4Ï’ªuù$RKª›¼je£?Ì~99ÿ<¤(²‚úñ‚z÷•¤\뵤v%ZZ M¢Éµ¬([ãæ3¾–”ÉY¨º”UK5ŽH<å“ 8ˆqßœª¤Ì¨U¤-Y“¿À†LmªB‰ÌXR?à +4/UCQþCwˆ¾j¯ö[^Ღ»M¾±J¹a;Il~݈ÆêoF‘ë÷o—T*þT¤*ÉŽ›4ø°FÛÇN¢dD”Ä—HDIq4FnUÐÔd‚’AˆÍn¼]8$I륤E‰0‡ÏŒ1NkW*t$ˆ³YGw]Ò +·öx¶e`Œ6µpáRèÌÿ…M¦EŽT!²Z¶.©*KQelÖ®¶Ì'#Ô×ERDí‰}sÉ”ñljZ«44’úÖ†mJ7y»"ÜÏ+ÝŠ¢€{
Y™¡Œ–ª(Ô†³‹TÊWQÖ…©¤•Ú@¾KÕºÈX»Hao„®dve+7¤K.܈úñºô7âÞÖ_ªÕ³¢þWj”jÿ®eÚÀö~J§Ý`
ѧ& + +•r„Ù¦ +TçÕWQx_™”2M¾Œ½€8ŽÀÎÁeÓ x4žNÆÓµ¬r™2ücJ_7ÌtÎfo(ºSÆ +¼öŽ„§‹<&¸µ¾ï6æÍa8ÔS€‡ £V¾¶lkÙg§3㈯™œ&,uðûd]µ~²ˆ¢Q0 ¼âC4d„¶¿°‹mC&`îΣ}¶’&v\]üΑ<¿1-³ÍèòÄgy%ö’øP×t‹0ÎÌ}[2YHÄÙg¹S[;°:†ßü|od©^Øn˜oÞ&¦e8ŽG‡ç‡é"jà +endobj +507 0 obj +1828 +endobj +508 0 obj<</Type/Page/Parent 450 0 R/Contents 509 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 69 0 R>>endobj +509 0 obj<</Length 510 0 R/Filter/FlateDecode>>stream +x¥WMsÛ6½ûWìø¤ÌØ”HÉ’œK'_N=“¸n¢LzÈ"! (hGùõ}ÍÚig:–-“°»oß¾]~?Ii‚Ÿ”Mç”W'/W'ã«KJg´ÚàÉ|‰ +š$“É„Vùh–dÉEBEµ$tA·µÒNÖtkjgŸ¾b÷ŒÒ4ì>ÏØ=ú¬taî-ݬƟ³ç=de}'kKÂZ“+á$ ÚãºWnGRä»°PÖ Ñj'$mêJ”åœø&Éí$mp‡Ì†ÞÝ®ÒçglBçé4ÉØî«?Þã&]]¿{ƒ/éò$ÁQÁ÷ª±ŽDi
ÙfïÍòq¹Ñ¹Ü;>‘ïõœ+‚[p1Œƒ^¨Ñ”.ëF˸ØvFZT² Óà@¸Sx÷CYØ3(؃u²ê\-Œ´ÝQ-}ð-LJ“©@ïÌÀ²wñŒjjRŽÁîïªe%=â‹IÉK…;6¡ölžpÊG7q;áZÀ:/žÀëô)•Þž’'†ö.“DNÛDÂ|îw’C-ÍVå¢|, +ÕýÐ’Ì[ŠîŽF…:Í…& Öا€ä¬†6€(³EEìÔìôÑ”à½OX,¹~ ôÈ +ìùÖ 9!n%ZóyÔå[ÏE^&(È5ª«–ÐåL} +q䜜/ WhþÅèK6_´£ð³®ß]ãBhZæÐ-ÏàåÐP_í™êK =i|õ<)mºP`chwnr™µh¦ŒK»t€ŒoËèœÜCóæÅŒÒy=ˆgá€8â<GR:P[Jf‹%4ì×”Ìf3à>¤d–ЫˆolƯCjoÛÔ>ÁÐÒãLq¥tYz"/Läµ< +X#¥úìë+PºœükºS4í¦{ØØÂ<ý‹Ç$´´d<º‰²N¬¹—„Sà:´*qà¾þ½‘ÐÛ‚îfS‡!*ôûjuK•ÌwB+[a~¤7ÙøF‹“Ǥ3¶Cû@º7€‚>}xçÓÌЉÜ57ê^ótÇYñ$YŸ[£ñr`œ¹¨¶Škÿ€Fè§HÃ[Ýܾ}|tª
gá·F:û@ÀsÈ»Å/!ðCþÀªç|µm°ê1jæ«ï!Uó8µñˆnEq!?<‰IÍ„ò>ù +Ckljå”ïdþ8E¨±.eѧ֜ÇÎÇ„dÙšLçL›‹ŒÅý8û}|ñþå¼×™¯hSôºßËÙ½ó°ë<lû/„³‹•o é%Ÿ +endobj +510 0 obj +1600 +endobj +511 0 obj<</Type/Page/Parent 450 0 R/Contents 512 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>>>endobj +512 0 obj<</Length 513 0 R/Filter/FlateDecode>>stream +xWMoÛ8½çWzr±±b;Žíô²HÓ¦
Úl»Ýƒ.´DÛl$Q%);F±ÿ}ß”í(Øp순7oÞŒži€ß!MGt>¡¬<y;?y??$³^Ì +t>ãu<›âu8¸LFd$-ù +žÂÎþçÏn.i8¦ùæ'3¼ÉýóͳÞ89OÆ Í×’n+ëDQ§tE×…’•{=ÿqrv3¦á0ÜݻÓp¦ª¥6e8mäJ˜\U+rl¨¬ªœÅ‘#‹™·H¤,‰P…Xl„o7H¤u3<GBpÔZê‡pú¿|ŸIjû4®-•·•M.sÚ*·ö¨6«“IªEö V2áëê& ƒÑóÉ·G_Š9Ó¥älÈm5qÖÖ›@•ö6YéH/ gKQåT¨JÒWi +²™Q5ÐAg1Ëþ4AYÙ}:šLãÃi~ÖoAôaþé7Z‹ÜVFÔk•‰á8i–i9M>Ý'®ëÿéº?šû}^ŒÍK¤=À±Ð +n|âTê\T ®Œ°´•EÁ[çŒIŽó…9q=b¨Ü(¸µžYjç B´¾ïE¹þÖwUÁ +rùc<Ç:BJ*k…Æ +¨UÀK_·õ‚41‹u>ÿ¢}4oèZ„‰B +'©©}‰reàK›Oœkíz;ü‚bñÝP°X†—|ŽàsÖúìóÕ¹¯ ]/çO£½µ¶arUt•ç_íÞyæ¤=ðýî¾ÿ××ëNÿÄÏ£a2aT Ç +¶EWñn5²Pf+#Óµz!ÝVÂ&m„Qº±tàR”~a”² +øbÑ=¯‘ð|Í™ðÀcäùU#yÆzïµ($ªÆðÑÝ'D{5¼Õ°ˆ¤àÿ£Þ"tsJaøä‘VÚî äN=b8?+ÖŸÚµEK1-3È×N7œy'qßÏjéù‹ŒÙ‰‚É·TSæ¿¿À~ÀÉícyâc ÕaÆ#£B•Ê…á‡OèŠiä,¢<hL‡zq=ãQé©ö‹ç¹ßB +zR#ÌË‹³ËY‡ÍaÎú*Ž°Ú!Í}¨Œu~2ú]l÷›õïÚ½úx‹¦^e÷hH=ãÔ»SØÑüä—F—±¢°•<2 £d”<òуp3‹ýfýÁXp,•X]}½×(W¶Õ +᧽D¡kˆ26X½‘9F:”½>Fn$3TÚS*Ûø:Œò¡‚-òýËå„ø7uØóšUà”e¢¢ÉjáÖÏ¡–ýA£ö r²Ê1~vQÆ/xÖK!šÒ' ŸX哧£$ÇÕ>,7<ÁãøaP„sXc€ +PØã²pJ +Ó,ˆÄ>€ýÊסüÕ h¡ë)šê[šúï7ÜD¡v³¸š
'ÓdH“ËQ˜ø÷Wwo¯Xƒ`Ÿ¡w:k¸fž|¯Ž÷§#¿ûÿ÷ׯ1¾èÅ/ +£[ +endobj +513 0 obj +1629 +endobj +514 0 obj<</Type/Page/Parent 450 0 R/Contents 515 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/Fc 12 0 R>>>>/Annots 72 0 R>>endobj +515 0 obj<</Length 516 0 R/Filter/FlateDecode>>stream +xW]oã6|ϯØæÉbÅr;¹‡Iî+èåž
EU´DÛ¼H¢JÒñåßw–[wô¡8¢HîÎÌήÿ9Ji„Ÿ”fc:ŸR^Ý,ŽÎÞO(Mi±ÂÊôrF‹‚FÉh4¢E>˜‹j)h£#§iœŒ©OÒ’Ý66ŽVÚÐýüËÃ-5FÕNÕkj´µjYÊSZn‘ÛHú¼ ¼T²v´SeIÖño#+Y-¥á7N_F4LÏqÁ¢4F>+½Å5Òñ™I»>ž&^¿«I›‚·jZ«gI¢Þ»£‹äXTÒ*qLÙ@×åÕ2—Ö +óBjE/zK´ˆ ‡lôÖr‡SêŶÚÖ¹Sº¥r8¨&QvrJ…,¥“!c#×Ê:Üô$_, ku®„“ +'Er Ñdm´.q)ßrIºöµÙÞ–E/é¥iºi âçÀ¬Ð̶Û(ûæ»#Q·o²ìñîóçE–ѯá´Ml +t öPf)4ª%Ñ}ÊLoø® +ËõÅBѵ„Øå7ô¬÷”°'µ6O> ñ%-u¼Æ6»Gm4OmÔJ›Il’ŸDñŒž)Öh+þ^¾÷·Äý² +‰†ÕÈ× +endobj +516 0 obj +1661 +endobj +517 0 obj<</Type/Page/Parent 450 0 R/Contents 518 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F2 5 0 R/F4 7 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 79 0 R>>endobj +518 0 obj<</Length 519 0 R/Filter/FlateDecode>>stream x•WMoÛF½ûWÒH”HYþÒv.`9…æPõ°"W&c’«î’–õïûfwII”}(bÄ&¹œ7oÞÿ=‰hŒÇ49£¤<¹žŸŒn/)Ó|…'gç4OiŽÇ¸“_2±®¥¦iHF&Îë-ýJ©*E^~E¹‡¯ç?¡èÔN¢0†©`F!ý¡ò*¯žHT4›Ó{}“×Yg vN)Š¼øœ_¿«H鬔&áŽc£_p³Vô¦½]Ö€h«*SÓ*×ø_¤)Õ™¤™¬¯ï©¥$µ²÷lì{LÃhâBÞç·8bŸ°ªì;ßn¾Pc8ŸGƽ¨Ä“Ñ%gB¢y–J´µ4d_,E’å•$‘$ª©j ½…%ZŠä¹Y·ñ&ªªµ* ©Cï#>A†4¸2¦à\”L¼ û~-ÄQyœ°Õ2" ǯßÿŠŽ‚ªRZZìæ1LâIíìÕùæá¾gn@›,O2ÄÉ(rߊ¹sh4€)œîY-A¼z)ÐÂÚ÷Ää×÷Âcšš7]ß|y†ãp2öve엧밶™v$ø2µZ°ôÝš @@ -928,13 +1001,13 @@ Yª Ás~ºqM‘¨²Äõ§Ã(NKTý‹&j‹jÊåZ³Iiø“ ÛX¯±óa¹¡;ìm®Ížå–U†;ÂM—aÁ*ÅñÀýn›ô{3·—UW³5µ,Ö£ßåе݂Äpsã–.“ ¨p¯°ì3 †ÖGtv Ù/i2@ðí…×{¬ôS»†íD~¦6¯oHLÒVa9
Çáv¾wk4É4·«§vØ
€Ñm×èÿ»àjLß»¦
3DÙpåPéY” Õûö{Ä6"€¸<ñix¢³I{ÑáOñ¨÷mÃ2ºP|"`ŽÛêx\÷L°½Kàj·öÞÀ ÕIßÝÞ”M¬3ÐÎÇ}X -þL@ÛrQþ~*ÔRÿ°»Åóþéˆä±f2e}ç^x1Ú@†>ñÿ÷-wzÎHâ0
b»má?Oþsõ<‹endstream +þL@ÛrQþ~*ÔRÿ°»Åóþéˆä±f2e}ç^x1Ú@†>ñÿ÷-wzÎHâ0
bûm„ÿ<ùsÿ<Œendstream endobj -475 0 obj +519 0 obj 1558 endobj -476 0 obj<</Type/Page/Parent 409 0 R/Contents 477 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 83 0 R>>endobj -477 0 obj<</Length 478 0 R/Filter/FlateDecode>>stream +520 0 obj<</Type/Page/Parent 450 0 R/Contents 521 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 86 0 R>>endobj +521 0 obj<</Length 522 0 R/Filter/FlateDecode>>stream xW]oÛF|ׯØê¥ja3"/ȃ?ê"@夵Š húp"OÒÅ$¹;ZÖ¿ïì)Q²‘…
H”ÈÝÙÙÙ¹Õ×^LCüÅ4MèbBiÑ»^ôÞÜ)Ži±Â7“Ù”
£ápH‹t`eZåvôŽ2]Uþ´øÒûeÑãü]ó»?~íMGQB“ñe4¡‚âÑ$š5W9=„,£C–É·uóÜËgGéF”kIn#©IÓƒ¨ã‹htõ‡YÓ›»¤É½HE[m×F×½ã4‡þÑBP®JIªô þ^çz)ò¬8¥ñ¡&#EöÖÃ=Ðxî3Ÿ' ]dƒN>ºý0çœoîÚCÚß',²(Køg JQHÒ+ÿ>pO[IÂHú¢U©Êu´giœDSφÈWP'QÜ\5Üq{0‡Îþ¥k*jëHäVÓF<â+a×IÓï†CðiO‚Ká¨qƒì49É25»ÊQ%¬?™ý~'¬tLx öŠì¤m>jp»%¬´¡®
ÕV°ªùáó gžmuàwãË®¢ïT)ò|wF"Ëèó @@ -942,300 +1015,464 @@ gžmuàwãË®¢ïT)ò|wF"Ëèó
^Ç&¯rÌw)œz’,Pµòà<0[,3.ña÷<Ð0el;¡Oî¡Â™ný‰àÙl Ç£`‹ï¤„cÀg{:@Wä @|<¿”ô6ˆàp,}CE?‡{_¢ÂË6:;£íF¡E[x¬bydu*3¦;($‰p Á<×ÛV6M-òR L»eO.$TÊøH¸“:á™–6¢×Ô¤'©ð´¡¥AŸRa…A1Q^ðéýýe‰¥ C`¤½fZ‰:w8k5Ñ#€á°Ž[W•6/FWºë÷<÷‹ßæO±Ÿ€Îl1Õhfe¥»ýdXîÚÞªæòÙ‡ XÁ¾BÇlü~'OªôŽÒô§ðƒæÔÆ 1ŽõôŠ(È:YÙ -8VÖ[È:u§ñŸ@‰Ñƒ’éFUËöi>¿Áò5W©ÑV¯…ŒL4î*Î%ö±*¯alžÖÆÂf—p§×lÖìñdŠ%{šàGRç×ÒÃÕüúŠ>ý àZ˜Cd„ë’k8O‡ÇÿÑñFø51ÃO38]â·#`ü½÷/ž}uendstream +8VÖ[È:u§ñŸ@‰Ñƒ’éFUËöi>¿Áò5W©ÑV¯…ŒL4î*Î%ö±*¯alžÖÆÂf—p§×lÖìñdŠ%{šàGRç×ÒÃÕüúŠ>ý àZ˜Cd„ë’k8O‡ÇÿÑñFø51ÃO38]rÁa€ñ÷Þ¿ž‡vendstream endobj -478 0 obj +522 0 obj 1533 endobj -479 0 obj<</Type/Page/Parent 409 0 R/Contents 480 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 92 0 R>>endobj -480 0 obj<</Length 481 0 R/Filter/FlateDecode>>stream +523 0 obj<</Type/Page/Parent 450 0 R/Contents 524 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 95 0 R>>endobj +524 0 obj<</Length 525 0 R/Filter/FlateDecode>>stream xW]oÛ6}ϯ¸oó QlB!é3'’_< y[àAS.Ÿdaª’«É¶:; ¥¤§Xixo<ˆÏ¶qô¬Šo<µ‰8ïî±Æè$žœrÆ¡@mp§ÈŸ„vb/ÙýP7Îr’²/À
ôÇ°½«?8ÄrHR ³3½‹ð}¼KJ»†e\*_D†ªíÝîÄë‹$ªÿIÞ!orCÊÅzë©O«ÕPñ,ió‘Ôˆ²ª¸®w>«äR-/{P•åÝ£éPX¸HŸG*‘ÉØ÷EžÌ‡LoA(
¾¡=t´„LF½ÂÐyŽ×q²GB±òªw¸=}ý6J³×‡M–™²Š¯
µpã!+.*cÈÉb—Y´íç»–Ëî:îˆ ”æà%åB–ÀÒËwhôSß ¾JYÁïÌ Ô™¯a¦’h!¾,(ëi„hàÎç0î*þÄwrëŒö a’Ì7VŽB^sË÷\ö¶œsvÊÊjcÍÎ
¬wöAÉ’:c¤uƒK
òÎìz)|² Màtb‹z¯÷œc’.Kè eÛXß”¯î`u+`…÷(öòÅI£xFþvk0ÊÅÊ2°îÇ!ö+vž_1)…ᘸߑ¨ªB¡ípÉeB( ?!âÚÇBÛõN^^EÓ³wb/\®¹~ŠôT_Ôbß÷Xó¶"ûª¿ÀbÃøÄÉãä§Ì~Í;I2S)¾²jÄëX£Ü£ÅTEƒÈ²*0 1™Ay±VJý¤j£¹ó"«…CÔ9¿<3ÜÆÎv}öâý²÷1;î݇ͻ_ø†ÒÙ*M~ì]c”šOטšxP]S¥NÅu–â¯Óù -¿ý¹ŠnYƒAîä ‡°†zr“5~ŽÀÐg‘o5Y5[ópÒˣ܂˜½ø[é0)FtžS饛—GS¡uÓX7ɶ)àjáéÓ>MgaJœñPسÞ#ܾÄ(~Úë=–´æéú´×{Ĥˆƒþ¥üµÐak'Å NÇÄkÃBð)xwóp¤ôòôQì.èœóÕ«uÃîšæ€{ñ©¶±ëèt¹Â8¼šâûµ÷!ûpuûæŠîkóýƒaˆŒŸ0Øêy8uŽýŸÏÞùj`lt4Eqýyöw_Âcendstream +¿ý¹ŠnYƒAîä ‡°†zr“5~ŽÀÐg‘o5Y5[ópÒˣ܂˜½ø[é0)FtžS饛—GS¡uÓX7ɶ)àjáéÓ>MgaJœñPسÞ#ܾÄ(~Úë=–´æéú´×{Ĥˆƒþ¥üµÐak'Å NÇÄkÃBð)xwóp¤ôòôQì.èœóÕ«uÃîšæ€{ñ©¶±ëèt¹Â8¼šâûµ÷!ûpuûæŠîkóýƒaˆŒŸ0Øêy8uŽýŸÏÞùj`lt4GqýyöwiÂdendstream endobj -481 0 obj +525 0 obj 1671 endobj -482 0 obj<</Type/Page/Parent 409 0 R/Contents 483 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 97 0 R>>endobj -483 0 obj<</Length 484 0 R/Filter/FlateDecode>>stream -xWÛrÛ6}×Wì[‹)YRúæKÓxš*NÍ4}ðL! H° (Eß³àE'I;™ŒMÄîž={öèŸAL#ü‹i–ÐxJ2ܤƒ—¯_Q2¢t…O¦³9¥¢Ñ‘·QzåhÑ»#oéÖ+½®¢G‘/%Q}!Q‘x‘~Œh˜LpÃŃӹp{º³¹Ð¿å5F9>ÅcãˆÃq%üÆ4Š#ºòóÚٺȚsSŠãö\2ãS×µßX÷SEëýÜœš´§.(ÝèŠ2+ë\žð» ió¥.„׶ »¢;±Õâ…-pM_=ÜÝÒ›wÓw$ŠŒü¦-°*7Y.Ò®¤××õ›>¢–ª.•“Je*£å![¨¨½(™F ?•«Ú”šJ§c„2JTŠ‘¥È8®Q€!)J±ÔF{*>(¤ÀÓG]dvLRšD#:Åþ¬€C'èé5?½ˆ°)Z¡=v§‹5Ѫ.$ã%kOÕÆÖ&£uŸ ä†ð`а+'kúlìÚîrgI½L˜QÒhô¥¢¦m²mÛpÍÁt÷)™ÎÚ»žògÃýÒÉŠþöW_ÚK9µºUÚ*C•’µãì4”SÞiµm¢]y&@—Á&i‰BÍ‘MÓAfÚr”ÛËEúÿîlÈ$X:»ÒøÑÒÎèRù½m÷•W9•ÖhÉüúŽË‡ÉTí©pJ¦R+‰ë -‹-¤©yVÐ?:f};ÏHvœ8¦.(‹wuõ…Î!\‰¢…ØiôqÌÓ3
«³£#´žiq æ"e‡¸Ž¼7 æb«¥¢-x$ž^|
åîø·f¡›¸ë,cr6”ÜjÐûÀð»(Ä?y -›Ü¿«'w
!àc%í` £ü”’ß”[*gÂïoÝi§¤·nÿõš¿5ügÌzh„´Q¨Vø>£^ f^Šr•#—À>цQqXÖ)[{£‹Ž|¼.œ×ÒôbÝõ”v -/rXE@o¥5`È}iÝI*Í@µülwc•Fyeö”éÕ -7bEY¤&ËWN_f 7hÁR)Þa+L¨0¸¦ü¹¨ÊæŠÈë¼O¿£ÊÂ)¸Þý΋F—´Sak¡¦[K‹ò¯ú8Ô…ùŠªÓq©g%t«€²cN» ¸žîOL˜¦ œâãC’´›"ì¦C_¨ëöÅ*«³°ËMÅÖƒ1‘[ ¿˜¥Žh¤ƒU8¼ 6¬aéÞÅpapÑÿfSsä_Ò›¥à˜(æßþøu0žñNÆs¬úœ&³«hÖ>zdËž ->à`µ4³ƒmÇãêxœh&À¸_ÑÞÖMvÌrÉ[èñè -ŠÀ9ÍÏéâÃâþ¯¿ïéõÛ·ÑÆçæô\¨ˆÏ]ž‹Ù™äâ3ûœ0˜Bdö5Ø°çê@GVÒ:|puÙÌxÆÞ5¢šk”€É¢µµa(+\æ5›à€.%1,¼šb94äÑcN³YògG9Å£`>ä<=‰Ç0!‡ŽTù2âZž.®ÀÈ\D%„õX¼ûã~[‰‹–¢ÂÆá^*¨,i!/¡¥³p}ÛáÎc›÷ÜwÇ‘f”Ÿk1ç8„u -_ÍÏxìwÑ-0-rd¹„ÅRbø±Nƒv²:ˆFçÚ³¬Õ¦“Ib˜\ø -¾~ÀعKNììC7´ÚìC_%V¥’RDíÈ¡!fÞÆÆUûp‡ð<D¶×%HU¡<›^Æ4ªôIù¥6;¦^?ƒáçÖÂ@®ð“—Gèd#4ƒ“ùŒ5ÿЪù6ï¿ípßDüžoagîÿì›×ÊÔzí$ì¤ô~ð/þö?ëendstream -endobj -484 0 obj -1508 -endobj -485 0 obj<</Type/Page/Parent 409 0 R/Contents 486 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 144 0 R>>endobj -486 0 obj<</Length 487 0 R/Filter/FlateDecode>>stream -x•XK“ÚF¾ï¯èK*¸*$„q¹R~íCÖ{/)¯ƒ4€l½,
‹7¿>_÷0 ›bÕÌL?¾î釾]¹4ÆŸK3&EÙÕ‹»«×wWc'éðU@`›ë9>ùáÏþ,Às¥iÉG° ->û/ì]ÏÉõén öAˆ‡XÖÇt
Çsèe‘/“Õ¦Jò™µ¦*[(zUd*ÉyÑTEšêêÉÝ—«ÑµÙ–×Л×à'–IUª. G¢J+ÃÌm‹ê+?Y–·¯^RR“)ˆ6y¬qF屈,U¥2mðå:ÒuªGfUg'‚zÑ;Ú&iÊJ*;+]6õÛ«É<p&øžRF¾;u¼†Jé£ -‡›ÎJﱘrÖ¤SOˆ,¦þIXeÏã! -8Qó–£x{Úê˜EC±¹¹}hÕZÝ{ËöƒYƒ{\|Y ÷¸>\¾C£M]¤„Œjž2Fi²ínkâÎçt=–èÑdl»»V³ƒ"£Õ"½gyÑ‘r/Є¶+Äe™îCT« Ù²D4¾µ½Ê?ÑìåFÅY"Íú¹ë©;ñ*çAî|;™Mh{v—Ÿ¤íÝ…ª‹ÆQ#ö¬%zlCóؽ¸=žÅä„’2Â2ÊM£CÝÉÔ¢Ë}¬+Dƒ@÷²?ú,×ckq?9CZ¢G$&¯#TfY¤`UœOútŒÇSÑÀrË>çnÅ¢G®´mc…¢GôÌŠ>æCéy–bKx<çöDZ”?f©bIe‘äF&q̾kLBÿaà²S¯Z`ŠåOÞ !6ó¼±ÐNuAÒ¡Zéœ}7³¢Ìɱ6*Ik*rTÁ-gÖ˜“kRÿ® -4~ià›ð”Ïs0ú$§e!΢¥ÐvãäõÍËÿÞÞ½{ã¬Mvn"pš±+jÞg¹˜ÂUڽ̚õÝû^ÞÛPw“£˜}²Ÿ"©ñªáÃïlx<t3ïÁoƒæž3£ëŽZœe- ¨ðr'¡3çw:‚Ààãó¿_<§Ûªø‚ïo¢
7£âAf:tƒ™ƒéxæ ¿_}õãϸvÉQoڸ럫ÿÃêÒéendstream -endobj -487 0 obj -1670 -endobj -488 0 obj<</Type/Page/Parent 409 0 R/Contents 489 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 151 0 R>>endobj -489 0 obj<</Length 490 0 R/Filter/FlateDecode>>stream -xXkOãFýί¸RW"H$!œÀ·,”.U¡Û’ªý€TMì ñ®íIgÆ„üûž;Û‰€îJÕ²!~Ýǹçž{Í?#:Á¿MÆtšPZ|œü8?8L§Ô~è'à¶Ét0¥³é„¿ñ¡%-ù \„™æ·oÎh4¢ù’Í&Ó Í3wà ÍÓÞ|%ÉHý,5•µ±´dq*S¥È+*…±¸²Ðjƒ›ˆpJéß–JÓŸy•á<¥E.+KVQ¡Ra½`SGó/'ÔÆpÝ»¾ŸÞ¤!¬þ©ÄËãd®Ç°ûã)íŸ^603ô Ê… 1ÎfJª”%µ\".A©*×…D9ÿ.™°¹BÜKzÒª^#§õ:¯ž©ÝHYQ“ÇýÜß«Œ#tàG4Géï?œr‰û,é,Iš£‚\pñ'»(ÿqûW4þس«Ü~´E±¥êẸsÆ/c(å˺à -0ä‚ÌJiKf-RùxtL[Uó©ºÈ`ƒÓÆ\5‡tSz1êßóÅl3¢dÌ*éô„ƒw|ç°¤óñà¢s™…CШC‘•¯FM°>áÌ£ùшݴö_egð³k˜+à²A ºVJîØìãj2LÞòñ1îz„'Ÿ’cÊ.š®¥M2åbªjIk¡E ªiãú!¯ÐeöåµL4A×¾›f—CªïbhZÂØm!I¤©ª+kJ_pƒû6ïvùðæPpOŸÐyâ;«mêdp: «èÿN¤«¼’4×Üà³àÅAü³Ê+ñʵ°¡H$0ÇÑŠZxÌÚÑ»É5ì0bÔÁX®Øf%,Ò-ƒC놴˜ðÍ=”[>s2†ÎeÌö“rB‡¿cÂÑ-bEjSÁÄb¿F1D,jÑíZ³há„EÆ5ŠY -]w„ÉH”̺Râk
Aå¦,늻’%d“Û•{<ÔóJUV«¢p>?É*õÒÜ
¨’/´RÀ-wè¸$‹¯ %©”åG+5x!S ²FìÖÊèÞ[P3ÎvUZ!ßJA+ÞN·Mêj¿¿²ôÄø¡ŽŸ¯¯Ž9óz‰#Öˆè« -%Œ,©ŒWÁõ²€ Þt ò®E$‰V’ô%ô4ƒFslk/r¨À-×
˜ -#]I[äpÖ 0Q}Ð_{%zxÚﻢ€F;+œ -¸0ÀÎs»øpÞ¥—¦'X IÐÛµÓöÆK°uCOìÛp×A¯ÁhU’CûUô"™ÞÞ—0Y§¬¦ƒ€ø¥IKì½YÖ´üFrKCž5ÂجòtÅuÔàáö•gÚí%ò$+ èdvLØoÆÝ~Þä8½-cQàg+Û¦?‡Ò¦ÃW;Ô5{Ó¾`óMmYµ, ¼ÈŒíïÅ„@äs—ÓJú%Ëuœ_›:žé×m.}/vÖõÿöø}Ê…4ëöëò“FЮ*1_åFU‡6 滕O¶Hî%\ÕÀˆOÖFŒ4J†Ú§fèð
è(_¯ÉI’2Tfj½ÞÂ-o™±X{9þRÛ½ Šü+HHÌe´tÁ;ÌÍ~îG¿sûáòåòüäÿG—÷ó;¿N\3ù<ä¼.‡‹¼.EaõZñî³!^ÈÁúÛ¥[QXeK'”éFa¹_÷ù–’J¦PRr#f<I¿§¸=Àzûj´‡ -ïs¿ü¬c&Dendstream -endobj -490 0 obj -1755 -endobj -491 0 obj<</Type/Page/Parent 409 0 R/Contents 492 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 154 0 R>>endobj -492 0 obj<</Length 493 0 R/Filter/FlateDecode>>stream -x•WkoÛ6ýž_qlˆ -Øò#‰|†<š6X»t‰‹b€¿Pm³“D•”âúßï\R’e¥Ýºpl‰ä}sîå—£ ñBó)Î(ÎŽ®G¯Gãðâ‚öfcšž†S:»˜ãûdŠ#iÅ;ðÇ´X>º;£É„+œ>»˜Ó"qïÇ´ˆƒÅF’•±ÎÚŠéÅFŠRåkÊD¼Q¹¤ÒT¶$ǺÊKKÊR©I$ •™‘Îù/Ò‰Ò}-U†Mx§Jæ%oø¬q6èW‹Ï>¤ÆÇ ;úøæhz:E8³ù4¼ Œ¦ç§á¬þ•Ò“?Oñ²ë<It&TÒ_º¢JSÊ¥³D*Ó*‘$èY¤<ÔÆyU»Ð5ƒó³ƒÝßx{yNzî´ v ËM}']ª*+
Ùب¢dûûò¸oØP!ŒÈd)MHt-S½åĉœäW‘©¤{Â!H7ïzcà c`‘‚eòùŸá÷;•W_Éîl)³WîÆtÉåŸÐpzž¹¨_Ç)ú•F•5#©_¤áú%òy”WHëpM”jhiÄkV"…7Ã÷ôKEÞFƒ±![a?à×}NO"‹¡¸áxP¯œÕhtÔpÖ-ÂO(F"ÉÎ2€<<eΖ¦êo ²Èäb#Déå€Ï…ÿMÊ”¦‘_*eNæ”ç¥Ù@d³¨Ön‡ïYë=;Ýs6d{¨$¶h“ôÃ}zûðñÝmoÇf%˜£ÉR¢V+øÒ4gô¼.75É`BÇJ”pÝpF²ŒGÞë¾)”¯Œ*wP
aunNœÖŒé|>ϼ²t…etwI€‡eäüô‰³ð,¤e(ã£TfÞ„^£õŽ4™C¦¬BÁ=7Gé÷\=ùù„/Úç Eâa¼ù„+:idŠº½Ë Ü*iº[¾úÙö1»çAQÊ
œa¯DQÈ<‘IHwFÊë§[Zˆ°W #ñÛš–~ƒ[Ÿ”
v…g^çlDŒ}ÊPm'F)ŸS–G¿ -£×P–™pÈ—Á¬%!¢D€(ÿ¶TH³’q™îBzjùä}êÃêÊ«ºK -ʶꤞ7{VŶ5àY&°É)u¸°r_á'8-¤ÓdÄ=Ûn4dÎcÔå†%µ¢¤9ݧ°‹ÖVh|¼‚ýp/W_ ö•J觗°«asOkG¹4¡cn"’mÄ3‚v˜#CŠ5E;ßn}— Ãð˜h»‘ù¾Mî¡ZkÑ÷Ѻ€&Á }ÔÆJ³—µ‡ÑÊè̹ÐS•V¦+Ç.3>=r°òhi ¬êÅd™ý[,“ÏØTÓ -$áæf
#®j&k‰Žs³ùÚÇÉép.x{,ñ-SÕš$ú§#å÷ꕉÀ«Õ -5Sè%\’Uªbh…S>?”uã šÐÏééΓ;l#œQ—âHX³Bq3à\glMó("ýŒà¨÷’{L6oî/ØŽ›qÜ„À]$ÕkWÐvÜŒñory½|…sšƒ¾ÑAîÛát[Å1ê¹Âܳ£+.EU@l„1c&Í-ž‚G–•¢fŸwbɳVœ[££/`Ý þ+Š}HÑ«,.?1KTF½l•–7è\'D$PkK#JmŽ^õ`ÍØÊ -WW„‚ÄéœsÕ1æë¯Ã•§û[²8µ„¾Hí -endobj -493 0 obj -1834 -endobj -494 0 obj<</Type/Page/Parent 409 0 R/Contents 495 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 157 0 R>>endobj -495 0 obj<</Length 496 0 R/Filter/FlateDecode>>stream -xXýoÛFýÝÅ (`¥°)ëÃ’ (Ü$nƒkÒ\"¸ƒ€bE®¤É]wiYÿ}ßÌ’E÷‡ A$.çãÍ›7³úÏňnðgDó1Mf”?./†Sh¹Á“ÙÝœ–Ý$777´L®"ãɺ@*Mµ÷fëoúºSÁí+g·ôÛåŸ7t=ž%S¼<XîðJY9-øíTÕ^g´>PØiúòþØÛ©gƒ—ùÚ…³T¨tg¬fO®¶!!ú¸¡ƒ«IUšjϧ٠-e,Œe…±½P8:ò"ü6rIšS-j÷yЕUÁ<ëü@改Ä)PE\HÛPí—UŽÃMàú@ñY¼kdbŠ¥®ªtòCBŸÔ“îÅ×$l±À)±XlÞ¥
¨À_÷ª”ÈëRy¿ÏhcPGÇ(jzTÅZq¹…ìùEå@>ÚT¼)²²¤3à¯RxÊnñÕ‰ -
öœó‰6«ÃÚ8Ô–OÒÞ„hyùí%©²ÔV‚t\ÿÕ€ŒN€HQÖ(Ö|þ[Z½Ih‰0a¯öÖH Dð -l‡,˜Çßyø͉jýÎ-ÝzãP‘î½”U€¢0Ý<Ó"õãv:ùj´
˜Ê!©ðÑìW¨Û{B™¦€'ZDAþ…Võ;Ö)öÁ„´C·iÄÿüöÓÅb)œŽÉŒ -ÝÎ’yó)§G†ÀNnð°-41òq¿CTª‰6º&`p193Øý\Ðx4N&wÝÏx:]$‹îÓÎg<Žs¨ÝÏMnfɨón÷3žŽ'Ém÷iç3žNægQ1Ö ¶jK¶WÈ|lyÁµ:–^X×R<8/—Ðáè@¼ÀÁ€Ô³2¹Ì¼Må -údÒÊy· Ò×ÀqšþÌÊÂæY ™†9«rÊt€ÿ–fÇ~|“‡4©µ«C7,i˜}ˆ -+³û¼UÚ)~œ`*ëq3xÁ/Ù6 ÷7f›”.1œ¦,QCÌ>,Íü}ŒÂsÀUœÃ;Kô‹¨×)´’è_Þ( ~y
]|éºù¢Ü'Gk$~΀øŠìƒ4/rtVÔrxÁðâʱ‚R(¼f$6
Dpˆ-7nêv\Ÿ{ÆzÔFù>® -bÂõ:€‡ºbÕ©»J½Ý €-³·Ô‹+żÁÔ1)å@0¾ú¼dÓǬ‡±WœÄÞ乤Á‹Iœ~€uˆººÖ2$†Jo1q “OØ5DÆ„˜=Ír'oz~!feŽ=ÊÜŸÝ^cú\‰9Ñj’8§ˆ„TÕ©,
6m‡6±=›b´:’`øÐÒ²“/‚i©tÅC»p6Á~Ö\Gü®µ1Ø‹ýóõÙ„>JÑAügmefbb`tÂÞÑwü–¬AÌÒs³ÐÒ·«•8Y0ˆúE¢ƒ\{Y+›µ±<Ÿ˜Ü¹§v+¨¶x*+f¯®öÆcøì ß*÷.Ö‰‹Ån:1d†wB«ðt¹3ØÆìe+]Âw˼–(Gîöжc$‡+½nRlû*}¢ 6'J&Aµz#±wŒb®µnÛùð*•FX#Kâú‘:îþ²OÀM /²¼
_zX‚áq÷}¡ù¦¾œ)ÃJCôêE ’×΂íÓLEqˆÑ‚puRßýzAw/lÞ¥°`è6]Òg5*8å¹ÃuD‡±Eìuž# HH)Céâý\`‡P°AØÜ©vÝŽ]zòظdõúu³A‹¹„¸Ec+tNyh·¦æÍXx¿‡ür€$ºîùÍîO¼a1—yfnü[WŽîùžÄZŸÿ:ÔŠ¤
9ÊÃù„üÛi÷’RA3’·Âÿ>ß>F¹”¶•«Ë¶®¸ld9rb8Øào…¥p&ž<ª# ø…»)rj|üŽÞ½ÿ_¿Zçr¿ZUÚ?™°Zas‡f»Z5Œé±…‹ÜÄÚ‰““c9lBl6xÈpæj\¦¯ñEÊ×Ìh¬U¶'Ä<&¯(AR[”|#,`/[¾Ü2j¾`…¦`Šféö³gÓäÎ8ùP„Úïïßyû5®»|Ù•»K9&+°Ó3‡ßà˜gÅ¡I±½ÉÜÁ^á›b}$I립Sã÷ƒd0|‰‘Ç“Ž]ÄK•ÇßnµÇO |h–qd‘IgB½x-~+¯á!zò^†Ù‰Tz¼oÅmñ"WÃ&ˆ|çNØVj½æ‹œL>¹Š=‰~øp×,X£Ù‹îlÎ[<./÷Ÿ~¼çÅóO¨6½wiÍ—”ãs_ÏÇøÝ&ü_W¤é|Š»—œßq -¸Füóâ/ñ¤¬endstream -endobj -496 0 obj -2051 -endobj -497 0 obj<</Type/Page/Parent 409 0 R/Contents 498 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 166 0 R>>endobj -498 0 obj<</Length 499 0 R/Filter/FlateDecode>>stream -x¥WÛnÛF}÷WÌ›d@¢.–%9/…ãØÛi#åRÀ/+rImLîªÜ¥£í¿÷Ì.)JJš-¢–œ93sæÌð·“
ñ7¢Ù˜Î¦'¯—'ƒ›)F´Lq2Ïh™Ð0‡´Œ»?™-%†n)“Ž:ï,é^h‘ɲCB'ÔYÈòyïÇÓågØ›ììõÇÓh‹Ý…Ò±„ÄèŽ#-eBÎЪzzXRmçê
i³íÑzß/¹µ<tN©)é)„Ò¶ÓçÁRtÙíìõAƒç^Å¥±&u”(ëJµªœ´$ÁXe4™”ج•€irK±Ès`ÖòKe½wxvøM8·¦J'fkéâœì‹u²°ÑÀƒ#\éDFò*‘–PŒ6U)%>ÜÄuJû³hŽ:!´ÇñtV6ùæ³]èûÅÚÏ×6xý,µ£JnQðDu½<ay*ш¿½ûñd4»ˆ.è|<‹¦TÐäl
ë«œ‹M,|0Çmûl¼ÊUüDkYrU@¥Î -¥*—Ý‘÷2£nê6¯|FESþ(6Å`äj5¸_ÜÝÜÞ]/ןÞ/¢ëO×¾l»0¼IÁq…›ÒƒÆ´G!FvÐ5¾;æ~³… -Ây*+„’–¦`Èçh8«'ó9œt6›FçõU½!./2ÖÒüY Bää
þï-Þ}X¾}{·ËÑAµwiÎÉlî1Ïð«ØÒPèAXt&“‰‰Vv¦Ñ4¢káÈ …%JžoЂº"ß̇2òÕE18wø/„~!kª2FW£—•†b¡YÛÜ*í¹ÃGÄwAOr¥3Ê! ¶Gïn®:ÐÈ\b⪠-y,>ÊRè,´?æõc—q$2UîOâhxäú±;‚ÊeSX»5ebO£Ðôt]궹Ò*§Bº5¸ˆZµQ¸¥7,«ËóÍç%pî¼M]Êâ˜úY=!ïRš‹Ì7
¬mUž7“/ø9Šb?]u®”¥âñ²aæb7x -î
ìˆÏi
› -Òù„ÑϼëaÚ” 4/Gì|ïˆâ)ð‡;^˘‰èç„GŽcWæ}‘»~"sé bˆ53 Ϲ&¼º+WæqƒØ*MU¬x.?vÁß\ -ëzÌR†À9…¶ç|}†5ÿ{0òxz„ -Ÿž+ÿ¨ -R·ÛÛüúÉ _·ÛmäøáMdÊlੱ»»Y_ºÐ‹kôó‰kÔÒÏ눟¤ãÇ8¶Ù(:£¿q ¶ùK«¿Ø-e3^Ûö÷X«UšB„XTÞ?Ü~â¾à-òlLxóñ»ómÐ츼Ø~'®½° â1/¶—?h'Á
p¸RÄ¡©ðéKH»?¶KnÐ)PAº7Z9<Ëâó$"¼¹Âh´ÔAA‚Õ.w/fÍNoxúB)ÊÙ«7l_^ªZ¯ÍbýÞExSä¬1ÈÅý—f’¶û7ûÜÌëù4šÎ@»éüÜ󫻸¼} 56Ÿ¡ÌXÉ÷6<~®nïÏÆþmëßl¤º~9_°
ã—“¿ -endobj -499 0 obj -1781 -endobj -500 0 obj<</Type/Page/Parent 409 0 R/Contents 501 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 177 0 R>>endobj -501 0 obj<</Length 502 0 R/Filter/FlateDecode>>stream -xÕXMsÚH½ûWôR&)#°÷²eCœ¸6N²l*U\i@Ke4sÙß¾¯g„ø0Ù|Ôv+ÛÀhúëõë×|9 ©!
:ÔíS”\MNZ×= -CšÌñIÿ|@“˜ÚA»Ý¦IÔÈ¥ÍtN6–ÊD%”Mh|;&‘¦zUÒ\Š—Y¡ò"º“¶¤™´+)sùšìJE:+–Vš’¦
%*Rñ6‘+mîžN>Ÿ´©vƒ<h¨Çç"’¤r*ŒÎT-õ²¤LÇrú4 šàÙ{\©àŸsQÒ› ¥Á›x¨´p†#8Œß:O×Þc\+«
›'=?0[9CÖˆù\E+##+c²Ú9›êH¤lg¦^L3£E‰QWN?S.g¸~^I+a¤Oâ„l$îˆD~`oÇîΕQÖå…SÏ Î„eæ*•e@üXëº_׬Ùé=ÎÙ+½¢XÓMýéŸ[ºõ1Ÿ²"gÿ?"åH‘åìJ(è£Êc.èÅ÷›·²EFmåƧ–ó‡ -5w©eþ8p@å^‹VŠ;^Ÿj惧‡GÀ#ˆãeú¬TÐ&NzúŒ¾˜œ`á ðœ'w?ÛÔÁ…~?¹ —÷“ð9+Ýí~ÒúAЇ÷¯½<©D;îoźÍH!ÿxÿò$Ä4ëR-Ô¦Œ:í,úW)÷—!ð[ØÙ߆^An²Š‹l&¨Ü¬q¶fÌ‚”X[üÚj•|2ÐfáRÉNló¹€>JJà'(SÆ -endobj -502 0 obj -1855 -endobj -503 0 obj<</Type/Page/Parent 409 0 R/Contents 504 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 188 0 R>>endobj -504 0 obj<</Length 505 0 R/Filter/FlateDecode>>stream -xX]sã¸|÷¯˜<Y›’hK–%y_®¼Þóž«nsN¬Jê*ÎH‚$vA‚€V”_Ÿ€´,´µuå²l~ -£µÙ0Be§r~±‘ŽÞs ¯gÜêØ2œµ´
Þñú>Û¥u×/Fw—¸óöÛp“ã©*H²_@þ²Vðë°–O|‹5y—q¢´Âz•uZX*¤ðg§ý^Õ2¡ÛfKü_ïçÙyÊD/ÁwN‡){[‹‘x{:4„èUŠvÒÉ2uˆH-fm8ÜðÉñ@Ô qa3:ÇgrŠ„÷È´Ò -Ï÷ÜÖyY“‚ÄØ®iøV×@‡ æü&¹Êt:§ÖšT¤z‚‚È4—/@’œÌ"ñaBÈuW§På¦ Bi9fä˜>,3m|—TCÿ.5vÕÿaD&oâ-ŠûÒãÇ;r1ûB7òtW7É‚åå¡!‘ç*àÖS½GnL*’Ù¤^€‰yÏû%ˆîþùvG¸õ —ÀYÇi¦Ù«¬’ÙW¬R‡ ‡ü:jò -êz¨,1¢q¨Ê^á>êÉF=ÍÍp'ô/cQG!Ö›Je))ˆK,«nˆþJ8h[HùJ´l Š -š¹‹ÞK¡H‡YOãsô"L»¾É¬jT&tBhn v4à ä<ä rZD©w]ê2«ÒPXìÁ® üÆAØùnDÓ˜mÀ¼‰g£ªÊeÂBjLùðÈAgjÉ›o”Öaí®aóC9æ_Yì ªKSé=â—K¡AÐòû$X²¥Ç‘*a9Ãù7¬Hþ£AèxŠ®×3È9Ôˆ•µVeå!ƒ™îPÙØ]¯8 -Hèxw×ðhSQs‚á°øÁú´+!²h‚C`šƒº[ðwv ÀcŽ4pÐÃÁƒ€°Î!h|H -ºÉÆteÅô*9Ôgdƒ—ÿ±Â“ÍÜ G!ùQÞ?Ay…óüŽúö¢8W¼Ê*¸¯™qV J?cúfÔ¶PÆ`W°³Um !ÛmĦ¬Ø§§,è¯ÉÝíc@—AÛH
ÊGüÿTî¤Ã±V†žöÂ+¼Yh -=“u\cid‹d-AÄîÐK¢;²hFÐX‚¶ìÌkÑe‚ê¨j°¿•š|;ĨNBk<ˆÂ¾Zõ© ªC·b¢yTÁž(E:ÐñMn$²–ÃÓ†Ó€¯…ÆÅëÊTð•rp+óEí§c¸QúaršÌV˜&CòìÍO¦ˆTÜà89효7ëÚ q«‚±
ËúKóG™DÑÛíÆ=BŒ,?–Ôj& óiÓÇ“‰r*ý0@1wú‘r -çxt»á‰9^ÓÄþXvw£r?qãÁÌ]lJôñ›Á‹Ãò‘éô¨õý…±m:È®£fÌtq¯¦SÖÄš¦¸9à|õÍXƒ”°zîIè7¤‡´(t.è8ýHG˜²m»×gÃ7“°õk‡½'“¡ªâÆÙÉ%W¸PHp%¤'Ð8‚KÑ—e9>* ?±¶ñb]¬hyŽYø0{ŸG]£q§@ÔÑpg|Q@°ÉÄŎС$I1{Ã.|ó2?ú}ŪŸ§‹%fÚ匿îØ÷tûùÃ-=Zó…[µ½aB0A"'qÕ$.ú~c¾ä 9|‘r5íúûÙÿ ×|endstream -endobj -505 0 obj -2019 -endobj -506 0 obj<</Type/Page/Parent 409 0 R/Contents 507 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj -507 0 obj<</Length 508 0 R/Filter/FlateDecode>>stream -x¥WïOãFýÎ_1ªt=BŽW>Tâ×õh¸#T)Rµ±×x{×·»&¸}ßì:Á1TTñÄ?vÞ¼yófò}kB{ø›ÐÑ”ö)¶N“Ÿ~¢É%9î~ćŒöÆ{{{”¤Û‡ã£1ß\\^ÿyvsÜÞ|ûgOÇt¯tf–Ž®:7•PšÎŒöÖ”ô#ÍDµ;É7}@“I<zwz„£·“B9u-u¦ži)«”eÙ’h|a¬ÌhÑÒ¯¦Ðô™ikç ““/d<WEEBg„ÔNË&ÃK…´’rc9òíNöÇSŽXç¥U¾GH‡=H‡cÎwûú&¹ ãMÄÛ” Þ¬è‡ÍKiÁÖI²²á½!åñ-—–?-ÉÕ2U¹J©’x6ã8E©½J…WF úBxJ…¦FgÒ2!šfW§”†Q‰
¦ÃQm• ñz™Iûûã -™gÊ@é“ÀÃMMU$ÊBÂ!£‰O~Bb$Ÿ½Ô`§Å5ørrMWB‹™"Hm7©)Ç}U(VCÖ¤2Ä»R©5Îä~wMÏR´ÐAN™B©Õ¢ñJ?„HCˆMÊ(^0Ê1ͤìÄD‰Ò¬¨ê¹˜|¶0ËN<Lp-,j jNÚÅ›©•üå…n÷Â…+«ò€KYqL3TJªC*}nf'WAŒPé´“àëò1Ì£sÍÁáIÅ!HP]rË媔¡j¨•ö²¸îóíû›Ûß~¹½¹ûJKcñ>k
I(‰ÏÏw8}.VöâhA¢-@ÚÕBÚ}µª¶]=—F7€F_Ç=écS¿~r¾3d%Úœ¨ÀÄg›ÐÞt3û0¥{ak€Ñ9$ÑWá‹q %”ƒœªT),‹jônD`“Ŷ,TZp·
Xé%þFÞ¢4ÐæuètLŸÍR2÷F£k£/Dv]§O’J•¢•^uD¯ö©É‚ Qæ*8€jorÛ9-s;ß–= kFN²'¡Ñ{Ý…AŠÜ)wZ=ç;Ý•C•Ð-ÕÒ X¸p86A·BƒÂæCƒŽà+TJÿžKƒ¤
¥¥Ñx‡„²ÃR^€ž¶Õµðå -lj´!TYMZùÀ®ÐöúžU±¾ÌBC/ 7`8ìb¬ÞA¾™t)|%䃚*¯D©þŠ]¡4بâgæ…ÕÁ¥C©Àq6ò{+,€uÃÄѹ(C³ØFM Oð z¯¼R?)kt…£Æa¾¬Ó%Ø|3ÐH™PO„É湄#AZlï`>Ç4DÍZ-*¼Ásµ4"Ô³T‹!бÄXÁ«äaLMmô˜.a*"õ#¾õ/ãÅÈêp p#´¾ˆŽ=Åo•hIKˆˆ5üÿá[Ò"bl©ÕžùsÔÈPJI{àZœ¥E -D’7ƒ|œ -®–p¾n˜«)"‘ÿŒuˆT¦…Ù@ú.ÔDÁ²Ø
ÃlÞD}k˜E‹%R¢¿rH®T0`,Q~mU"žbÇM.š‹Å
t»7îw;ž“i³Þßz#ZÝjÔgqDë
£/€¸C…Öw§Í%ÀÊ—CŸ3rê<ÖÈìâìîö2ù£Kø`çà^ÏDCX¡C -Rl)0 -endobj -508 0 obj -1625 -endobj -509 0 obj<</Type/Page/Parent 409 0 R/Contents 510 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F8 10 0 R>>>>>>endobj -510 0 obj<</Length 511 0 R/Filter/FlateDecode>>stream -xmU]oâ:}çWÌÓ]*-)Pº}£Wªt½Û¬V+Uºrî&qÖvÊòïï;|4(¡`{æÌ™3Ç¿{#â5¢Ù˜.¦$ËÞuÚ;ÿ{B£¥+¬L/g”æ4L†Ã!¥²÷ªìŽ~è*7[G‹”ÜÎyUÒskì/ç…צ"áh«Š‚?²8ò|F[6âU‘öŽÌ¶"«ÖÚy»KNã=…ýî,}é
i0ºHÆÈß÷á©Ök©kᣢ[S -|<)ÙXíw$MåisÊ…™pŠÂY¿Q;raÃQiÊ0XkXË
-–i'-£’åªVxTžV
ÊØ#?&1+£-ö™ëF¼GFÂäT03â’6×xšL¸Ät£è;Ø:ÆÔŽ¤( -•shzš?€åCµs)•sô *±üêåL8Ú8\KÁ_l§6Ñ jBßµ,z»Šòtå•PmMHÜ9þÜ×ꊼ!U¹$ïIý×Ru“˨“ -endobj -511 0 obj -915 -endobj -512 0 obj<</Type/Page/Parent 409 0 R/Contents 513 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>>>endobj -513 0 obj<</Length 514 0 R/Filter/FlateDecode>>stream +526 0 obj<</Type/Page/Parent 450 0 R/Contents 527 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 104 0 R>>endobj +527 0 obj<</Length 528 0 R/Filter/FlateDecode>>stream +xWÛnÛF}÷WÌ[e ¢DêfåÍ—¨1Ú8N¬4}P¬È•¸
Ée–¤Uý}Ïìr%JNŠ40`“&w.gÎœ~½iˆŸf¦ç7Ë‹ÁbNÑ–<™Î®h™Ð0ñŸ¸w›Š²–†¦½Õ;ª5Ýêb£¶‘ô$òµ (ˆHT$.—_©q¾÷hT.Ìžît.TÁgj£³L~‹ý…xýõG!ÎãÄ4z4ÒȯªT-飉*¶îĘ°=Íøý¹Ñˆa¯Ša]$ãNÀaªŠbû+*3)*I¹ø"©âÈñ\Ôö¬À]¬sتÅ:“´SuÊmŠðNkQ©¸Í-¹X7*“UÒ<«ðWåë€O‘(JP²°ù?"ÉU¡ªÚäUŠªÚi“É"6û²Vº`΀h™Ê +Vëf·o–\[ +ùêã¯a8F4™^cÊ)¼Š‚y{—Ñ—tˆÛ9vKYëRÅ(”Íø@'ìµN%ÙôN˜-
Š½çÓ[õ&«Ë6ªhzôšÓ(“³mÖ¢/£ù<FÔ¨(ÅVZ}h€ kÎÆÓ œYŒàÌÇwîâÍô– §éû`{¤7ŽGoß^¾‡Áߘ‹ëB“ÉU0¥ñÕ,¢† m|OyŽO¢qpÚUÓ +èFÄ_¶F7EÂö‹I‹6ú²ï8þ kùÚVg°˜úZ\7uªÍ/ñSzíÎz\{`˜Ÿè¸ÉeQ®ó{ +ayÆI݉g•À}QèvŽmüxwk± ¾gºK)ÌÅpo>,}[/®?€¯7-ã=:~UM)M,eŽ÷E]H\ßæ7µäìý!MÅôGTÎxi”6,3Fº¦eyIEb˜-’È(¥X«LÕŠ›D“ˆk«?ôY‰Þ—%Q‰S :Ëë(H´ê!íÕ%'"á¡à¦·*p&¾¢8‰â–(À€[ ×±Dè+†¤KÈAK:±œ9æȨª÷šÄic¦·º¨hctÞ9fSXõêþ¶)==NW—¶)|–ôñ¼â8S({eUDUg¾…©UǺ©3U0z¨iU˲¢BBÈ*VlŽ¾«®,a +ªd¯?™C$[9k¤“öã>Ø^9´2XÄžögÐf¬:IoMgØz9åg-,3s„âЦóÚ†ãÐ0œ2ù,¡2nÜZûÿ®Œ¬’ÏÎ[†Å’@^¡Å<5дV2D+SÜ=èÄNlƒ‡åIæ?¶‘¬zFì1[èŒM´u›ÐÏ"구Ul'‹Õ’”S©3È*DêŒûÉF3,!ýˆ×"Ô›·årÛ=bêRD·N(Ù¸SŒvòdž…¿Ø &h77ÛÃ9.¡ÿv»,<A"ŠF§íçô<
Bn{»ÎòªÅºúBáh—Jfú$ZÈytóc”p“.&\Ž1!Ü!¯"]
;í¬R±È3“NTÖŽ5ÖVUÄYÃ»Ý +YÛ)l{®;·}°\9?ÈjÓTõÕË£wÒ^O×ïà®DÕݦbgp×*òâs¢"Ì@È +endobj +528 0 obj +1735 +endobj +529 0 obj<</Type/Page/Parent 450 0 R/Contents 530 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 145 0 R>>endobj +530 0 obj<</Length 531 0 R/Filter/FlateDecode>>stream +x•XÛrÓH}ÏWôËÖ†±u³e/Em²,qÕ>ÆòØH!É1þû=Ý#Y²ñBa{,Ít÷9§/ò÷—üs)ôÈR”^¼š\ü3¹pz£µ/Ň</Á(ä×Á¸çQ¡iÎ;pÇl_p{ÿ. ץɜŽBšÌä‡&Ñåk“ÍãŪˆ³UKM**úxûšžM¾^\cn›]º=Ycyíú°†¯^ZU¼-UÑ2Î4UŪ¬HE‘YeUI*›ÑWg|K”Äš¿£Êˆ•™IUœíšð¬‰ko@×Þ°°ÉR#.…ÿΔƙ)h¦+'%•«hIª¤U‰Kyaæq¢ËçTnÊJ§”›$ŽbþBWQ¯×#zkÖúIÏÙ…Ò›™Š2é²TEœl8f§
±ÌuÏãˆÝVh`3mã¨8XèDUzÆ·þg3³.é~‚³«µ)¾ &‹t^•pamh' MõžÉ8Å&ÃA&K64-b=Ç;ãÐã[E
],XþY
ûý»1¹€nÚ¡E±%{Øó{t˜ñ[Ë.V…I]°±V9 +ûgúû +Dƒ“È@L ª2˜éú¯£Þ°ãUw«a¸su'u%L¤næ~$âpƒ0k¢”†”<ÔŒzÑbâù ±E$W+Àm½ÊË—àà¹:žt†ì´äM—»¥zÒP°Î(‰³o@bWKqMEÕJ%[>‘±eTÄ9+[TÌrªSü-g8d¢2Ò?Tš'ºÝ6‡8Š³)'eé/«K‡Æ,r”#o`KÅçEb¦*ùÂ×9…9zè•ð÷‚^©YŒ2ÆðVñ‘eàR0W)¡ õ¢mMCJ½aŒ
],‘êÓØ@Ѷ8±Ý¸Å”^JÉëßyÖýËÞ|ØqÃávJ¡ËÙ-‹£nôïj¬?þHn¹åd\f•ÿª3÷7ŸîßÝðÝÛ£¯=QÚ×-˜k0´4«dÆÜ01œ=uEçOLîS…Q €¡Új‚±®:LYJÃ<dq4ÈzÃ~!Ì Jyr<´aÐÅÕB¯ëŒQ,íê´M<Øã7/ô\œð6´ã¶7zG[þÈRÇÞìâŒíQ°Çeîï}D[‹Ú—ÅÃ!wÝVB]&φ{P+¥Ž0[T›mÒÑãeÊc‚ôìíÕ—²~|¶ÃYàg"_g¼X¬]ÿ›óûÎnðՃΣ蛜›z®Êù4CBµRhßWq¡¹Y“)ž˜vœwFÒ™\7€Ö}YñÒ乪E¿6ß?F¸ƒQ”«<7EÕdhb&Ûѧr"¦$ú´‹Ó®z,¸¸¶®ÖúlÏnÐnñ;åæZš.ÚrYq³Ý™éþîBë¾”81$»8ãnÀtÝ?kµ<é#þþ¸|læJ¬V|÷AŒóÜÅÄñ?KZšE‰&DÔE{S]:ãJLï7ª©¦”ÇghNU»a;<ñ!™yÜódq&l‡›ÈÏaÏŠøéDƒz+¶©ÕîhÜ‚m§ºcç ØŒÇi°ùÛ¡OBmgr Jémݲi›¬Y?¢òŸfj ž„*Ù]]Ý~x¸ºEðdÈ
í3ú¹œüÝYÏÎoQ x ««+‹3¨áA.¬ÓÇqzQ:ã[ö”÷¢3;‹‡{‰Û:s|ƒ6¬€Û))¹²8³›Q§s©¿*‹¾4“~ÉÏ—ý$žö|»~ 1®2þÈçÓ^Œí£h[‡Öè5ZM“RËL×àÈmå-ŸODòíÆ-1þ–6aäË*5Ãc,;qlÌza'|r5äùw§òæ.§M’á·)By6bJåóéÐüýös†R<:¡«ôñÒϪÚ.²OÒ5•òù´yotÙÓTÖí¤7ªßp¡ß
Çv¸|¸yÿê†>æ+ª0ÝšhÅ
?ZÿÚ†=<A„žüÄñ»ÇAÈSšlõ†uäÿ^ü¬endstream +endobj +531 0 obj +1632 +endobj +532 0 obj<</Type/Page/Parent 450 0 R/Contents 533 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 158 0 R>>endobj +533 0 obj<</Length 534 0 R/Filter/FlateDecode>>stream +xXMsÛ6½ûWì-ÊŒ%‹²,ÉéÁ±ã&ÄIuÚNÝDBcP@ÒŠúëûvP+§—NSÇüÀ~¼}ûv™¯'
ñ_BÓO(-O^ÍO^ÏO†ƒÙŒv?Ü.†4™^F4žMñûh4˜‘Ó´lOai€ ÿøôÓ Þ˜ÐD^.i6âórQÐg>#ïîÀÅÙí.i¾dÛ|rFóLLižöR§U©TÕãËù—½ãbÇ{ô#
'Ã!?E +ÞÈt‚ˆKºœá¯‰\<ë>˜âÍ}¿YîtZ[·ý/×SïúìvLIÂiôÅbÄ!̳Þ|¥—âÿ)µÍºÐd—´¶¹©+ª-ér½RUþ·¦ÜP½Âkû¤ñªYæSunÍ€“C¡Ø蘾6©Û®kÑZUÕƺ¬¢²©jZhÒF- +
ˆn£ÒÂs¦k•YC+»!v›Y8Ë«Ss©îüÎ'\±d?%%£—D®žqM’DâÚ•íõÝõ§?>Îß~¸¬ê²x¦tâg·i„n +v%ç¸ûÑdžGhùq‹€¥J»'D/©WÍzm]ÌJ(û`MEÊd +<b.Vk•êû—§´µ
ßjŠì°J-+ç$ö<aBôxDÃ1`+é|ȡˇ¾wY½Ü{Æb‹Ë{×™*+`FUÁþtÜÚDË£Ù£»N_ÔÜà©kZš-Ý·«ãó«û×x:™
¦È[Ÿ2W ó!Ê®ÏÐZäÓnbcFk—‹Ë*4Ó©är•´^nÀñÒwø%‡©¥èÆKÉC&hõ%Š¶ùªz9W)tj.*-Stˆi™ +ÅõsÐiŒ‡ #¸- +景fëHö¨•Âú‰ã@
Û/Ê×îL×éÙQè$ùWTú¶‘.uZö“ +m^øUp§D?åqÏ1ÚÏÒ°õw<Ów\s´¹®üR¢6åy»~cB‡)ì„û"Á>h/åû78Ö¨"ÌÐo¡13ôZì7®½—`ð–ùNO±¡Bªñ¬e)nWÐEÔWÑ£ârÂ{ËÝ“* ý¾œ*@C'fBå(2åëÈNÉŽ.f‘ÌG³ƒÚÏdèÙ»ÂDèu¥Ä£Ë¤Ou?W~ÊTq»>êm°ØIQæ6+óÎÏ9n!YªØí¼íäºÊ'QtÆ;5°•QŠ@:^Û +ôMí÷hßã‹ÍÏŽTÚð‚Œ•ae3èñσȷ߰$c^6¿¿$ɨóùÄ«@2ÀÀ¬ƒºH?ðü9NWß'QÂÚ‘?GËÜaÒà»cÍÜÚyfZð¼_±„@ãßßSF•a‰aÀä^OF}‹\ ½¡°Ë ¬œ„÷"*ñS¾ÞfÐÇÄdK/T&rêÜÙ84/yÐðÖÆè´l ²aôFd²Sô(s`ª ƒýÂn8Øb}Sü![Š¢w¹i¾-еY˜Wþ#ì*¾Så[2™L M&¸ÈzŸ¯Þ¿º¢Î~Á¿`ÛûÎâS}ÿr:’Éÿqßc/Å¿Üp£)»û~9ùÓ¢bbendstream +endobj +534 0 obj +1935 +endobj +535 0 obj<</Type/Page/Parent 450 0 R/Contents 536 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 163 0 R>>endobj +536 0 obj<</Length 537 0 R/Filter/FlateDecode>>stream +xWko·ýî_1u]X¢ÇêmE'q›¢ÉíU´Ô.e1Ù%Ur׊gøX=œ¶iDðî’3Ù3gÿ8Ëh€Í†4šR^Ý,Î^/νùœö?öXv5îi<ŸñßCüXI+¬ÐäjÔ›>ù[øíõo±9£Å +~§ó- +ÿ}@‹¼c©¿¤g‹÷gýÛq\Õé7ÎöÝRiü!( +ê>P³Ý‚ú…|ìë¦,©›Ç}ô¯ùZiù»Vù-*yb–ºuõÙðJ”.~OÛa>õ†¯Ózjä‚bépŠÄ`éb-c龬óþF8·-N#º¶;Ú*„_*WSÝÑqÄ„oõš]Øl¤.dñœ¶F_Ö´‚]¼dá]Œ(ï“ãÖß….H¢µéBY™×Æîztk,É¢Ú”l2‹²”]f³Ù]ÂmSÑ…>=#ýÝ!O‚*Õ‰Ó*G×!'ºbDdÈä$dÒ»½¸þx=Lð?‹‡aá¾&GÅf:×-.®Oë›`Õe_ÓPàKó(ŸÿSüäBÓÓ;*¤ËÚÔ +Eñ…[!¥\ÍMNª'{t#œ¬Pî—¦Ú4µ´=RÂÑÿàH,)a¢ÜQÕ +àöW†q@'ª¥ÐÓ¦äæA«ÿÅÊ +w +ÈÛ6¶ðiƒ÷XüÂhI‹v؉'ÏÄyßOßzŠÏ¯€¶Š¦SÏ”üPÒóížýzÏ‘“–#ÇWÒ=K¶G½ïÌïŸù“µëmy èÊMUqï’êÖ|ȵ´²í¼DÆ-‰}’…©õJ]ÁÜÉ~û· ½û†|B’ô¸eÇŸ¿³ãëŒÂÇ"^Þ0ïEK)WÙxÚ¡«çA¾7Jûêæ¥&ŽáOªªd¡€r÷¤l>‰©lƒaož&
ðUÛO(ŒÎõp’½ºîF{f=FVB@UÉzmŠth’4êQ”;ÚƒýØÐqW%Æ7¾~Qº0[Gïôã«—¢>çwÒ>JKˆP<H{DßZSùoµÂd@?n×*_û7 ÿùЊèÏ#wû!é·¦}Sþ%@§¶¤ãGP¾úA†×©žíLc#7q›RcÚ/1“àT«0,›Bڿ삳r¸=¤T +endobj +537 0 obj +1766 +endobj +538 0 obj<</Type/Page/Parent 450 0 R/Contents 539 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/Fc 12 0 R>>>>>>endobj +539 0 obj<</Length 540 0 R/Filter/FlateDecode>>stream +xWaoÛ6ýž_q +Ô9v²d݇
iÒlÁÐ4[=”DÛl$Ñ%©¸þ÷{w¤UmW`-В»{÷޻㇃)ãï”ÎgtrFE}ðj~0¹>¥é”æK~töã9ÍK:ÎŽi^ŒækMgóJ×d<Ù¦Ú‘i(ÄÇ+§jj½.)XªÕƒ–º n7Æ·…&<-õ˜L už6Ú-uª]Fï,N« _ÌßÓÑô$›!øHñ‘Ž¶&¬mäÈçÏž“jJâ7ÄßO®HIÍfuuŒ8]"(ç™ÒQeišUwZFo] +Oòl»¶UúV"󉽜8™%ílK•y@IR®o–gœ—BzùÐjjMIߥ<ÏRž8lv–r7´ÒÈÍV%þUÊÕ#ŸRئFÆg+É]ÙZ™&ßC"ëèðR5
ôÞ¢¥¼Ë‡ +m\Œ€ìÍÝå3<gèAwªÎÝ]]fD¬„¥*»eP +[×BÈ©ªAT§kˬ*jt`ÞÇx½ÆúŸH£H¯ÇŽËŸ‹û›ÛÛùbñsDzOu>O$ð=MÊø®C¹wÀu뼃ê–RE×> ¯ö\Sô¼ÖuY +`±l+øj³SK.£ÝÀYÅ®"A½ÅÓGí<›ÆGDr¶Ô”eý™•& ÇtØ«ñ[EŽé®Ò +†&؃Ǧ1ù¶ +‹£„× %ª¬A +Ö%áÆÔ±´¸ÚÔ +¶ü±[óÑ}z½»¹"ó€‰èw²a8™GÌÉýÛ?ÿõÏ·Ýeø>~ÔIcÄd¦B˜V‚s×(FTõ¦úŒSÌÕ$_Î`i0˜EñÀ½}ä7"Õq0t¿C8m¬84~Âdë„S¬¿…1³sU<Hˆ¥…jxæ°
/îZïi–gçcšßþÙ${}qE¹SM±FÀ†Åˆì4{”nJ]‚·Ñ¿âüÞ*öÛA¨Â:üFœ˜½–9-èç¬3+Ó¨ªã/qs +Rq
’ÅÒ`þ`hEôˆ){ä/«'™³~c¼z‰È°ýzû³,“R$ÛœÀUÈþ +CIÔÿ¬Iì°¥ò~[Fãê/1ƒxq¥éºZÂ#¤£¼b1 +y‰fy+$Šã§þ?…£6˜Ê,ýûxPÊâjº²S
ü¬“¶›ÜX4—÷´ž’¬þ¼/J’– °€£ÃO;íÿÃß?#¸íß$æÈÇ·žû +7>R9_éêÝ€+rÍ+g*¿dÔ¾¿¶m}rÑø¢÷a¡¿xƒ±SÁSJ,]+–NlÈ,ãùʳ̔7ðÖ¥ùW~;å1˜Ý +endobj +540 0 obj +1867 +endobj +541 0 obj<</Type/Page/Parent 450 0 R/Contents 542 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 166 0 R>>endobj +542 0 obj<</Length 543 0 R/Filter/FlateDecode>>stream +xWÛnÛF}÷WÌK¶°¨«uñKá4qk¤qR[AЂ@±"WÒÖ$WÙ]FÖß÷Ì.)QtÍEµä\Îœ93ür1¤þi6¢ñ”ÒââõòâíòbÏçtú0œÆººšÆš®âFñœŒ¤5?2ˆ°süÀýýÛ
‡´\³Ýé|FËÌß0 eIc´!UÒAW†l±Êâ\o®‰vÂÚlÕ߉‚¿Åé5¾ý-ÒTW¥K¢ÑtžüHoÞ_Ó§ûw÷>ßÓÛ‡‡´†µOVšë—ÿ\¨7Ç#8Œ~¨ðãTÿ:âàñ룵2ÖÑJ’,m…$œÆ7±Êñm+‰ŸªZÚ+·õú·WuF"æøöõ$QðÂNNIG—°¤,á_©M!òeº”— +Çà‡/dؾt)W)ÎúV+ѵ³V€RX&ÏõÞ^×þ´`F‘ÔU¨Õê¬A¨/•22k~çúï¤)”‹>÷Òƒ™1ó*º[3‘h/JÇàYà°éÓ^˜IMNT®Üoð!§Aü̵>ÒŒÀÂï:E]•{eIä!.Pö¶Vyéï›Ýg«™D1-·4øou!iUmÀ–3>èo™ä@«R=¿´ˆ0ÃÓ¥”ãÖŠ“‰yyN~FÁS¿Ðè#S (¿Jc•ëÖc\Ô@K¯š,® +“ùŸ@ó¨ýÛ
ÑjkHËd:ô½xjþi<éñ`èúQç*Ux‚Èfö¼ÌܾÊï«tb‘ &Z¾@Q^‰h%UìÐý·<<诪Üx©8zã–ôØ°¸…S¦=ÐÂ, + §´Û +臎¾Ø&n†þ&…ÌP=6ûY•øO÷Kš +Ê¢¿10ù Õ…ªLó*ÃDðƒøäh\‚¼¨ÔŽ;í3†£u^:NÐyAhÑÓâ<T‚’<f…ú:¨|˜ÝŽM´UÞVÊ…â9?¶™RHÞéhäíe·•AŸšKØl}Û6ü[\Q'º›ÁÊcv
Ǫ̀¾ìäÞáìò‹ˆ£°94P¢A~W2\LÖ#7ÊòÐy’¼åÐkŸRÛÆn÷6ðU¢Ã°ÂX`ü›ÞKpW ì‡,éä;…/Oô1™ª¤Øí$Y2—\ÎlφY6y uÉÚ¢/>E¡ËXdEvßîá·f¥‰öª,Ý7îéÎ +o»Êóá ¶×ô©“…’tܤ×Iâ]% FW7®@}pë 6 +Vš=s‰*5DDµêúrÛ‚ðÜ8lõ¼+¹°Ì6•Júˆµ‹Æ”D<Ò‰)a°´óÀ<e +{¦+¼¸ôpœ>š® + +ùÀoüR½b¤¶MÖž9ìkÃo_LŸ +»8ˆœ*êßJ,ïë¼YÀÕ©òyøÈëoû®*Ñ/þ½š§ +?{åÃh³!‡Ž+Ok.þÔ”š×»Ôp<Ħ:ýŽ=Þ¼}Ûã?Pz£ÓŠß2ŽKFo8áöÞläׯÿôŽ3™Mšum<àÀ°¥ÿqñ/à1:,endstream +endobj +543 0 obj +1958 +endobj +544 0 obj<</Type/Page/Parent 450 0 R/Contents 545 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 173 0 R>>endobj +545 0 obj<</Length 546 0 R/Filter/FlateDecode>>stream +xW]oÛF|÷¯Ø7)€D}Z’ó$©Ü°“6R> +øåH)&ä{w´l´ýï=RE§@Z¶%‘Ú›]þq1¡1~&´œÒlAQqñf{1ºžÓdBÛ„?Z¬–´iŒÇcÚFý›„R£«’JgQ&-ÅZõíµùFZI2²ÔÆY²UšJ‹©t.S)¹¤ªŒ…“1Ñ}ßH¿ô_ÃÅûuT
â<§D›Û¯cNfÁ +š/øý.§Í³~›¯®Îúí-ºìí¤a!¢½Êµ€„À¨0Ñ.{@m’,—[çp“R?qåËуâP÷ ÒÅhäY8ºÛÜ^ßÜ®7£wë/7ÁúËÚ×‰@-q55‡€çÈç\;çíT‹æ ÙïöRA:"ËE˜{EƒÉÉbÌh>_¡_ÁÛl,šw
oÎ|~å»ùäOÞ +vQÔz¤Ÿzùð%â»`&94›©Ð‡ë·=ø,0ÖQU@þ>@@컞ÁS³á‹`@MI¢}æv>¸E(NÃNiDÂÙÐÊ¥ZÇ$Ë–Ë>âን4å½{µ—‚Û*Ú‘°sCƒY +n$Ì A~Tb‚¢˜Êð‰Cõ@‚?ÀÅ×aD*ñöPhªV8åZ£·µ›Z‘Gãó4B¥è/žü“NŠ÷}ÆËDT¹Ã’È“1– ¬¹Ã§°;Llï_ÔKCËð^«S?&UN…t;ÈÕ:aD]P²×ò¯X¢ž†5º¾l–‡>¥QDô3Åú”ä"õY"Ú>ÃÔŒÊNVu9Îøjz:Ì”0¼”qûbFc™x‚€L8'P³4ù³ÂÅSЗD¾6àâ¦+Oz +5÷Ž½Â¼Ö«
ï„XXz)Uó²Å‡·.qÈB|óê$ +}(ñ÷úÕ näL>¹Æ2—ƇTSÍWx:²kú8ÔÄ-b«$áu³ü¾çRX7`MçÔ©Ë`LÞWÄö˜ëµŠ«âã©wkÅZUÅÖTØ~âäó{*¶ÜÄIã7µvÒ#yŸcsä¡Y¥wË&õÏ0µž&üõò9ûý‡ª"Mk«¢V p9±ÀnƒÕw2½`zì°½7!³RftÅÍC=àáJ·—€X¶+µÁ³|EjÀ"rGäƒÛàžJÆ„8À`àuß
<×ì®,ÑF\Z™ªä³®Ü°¯Ã¿¹#ë~C÷Á‚bôrØáˆi–B€*}é›= °õºRQÐ_äý‡‘Ž®æýl»;=µ÷Mˆ?ʽ°†·4ý©¤3mI ÀƒEàÁïïÙ§«q0¡Ù¡ Ùjqxó½=q6÷cã´ø¼V~lJÅ+T|¶‘Ee\%·Ái ðvéEq\õŽûíœß÷û}àøËe M::¿û°îôák¯N‘så½UÖTbøùÇÈÉl‚T«ËúÉkóúîÍkô³þŠÞÆÃLkÉàï
'‹%n.§~Ýÿ‘¥h¾äUÊß>ó# +endobj +546 0 obj +1734 +endobj +547 0 obj<</Type/Page/Parent 450 0 R/Contents 548 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F6 9 0 R/F8 10 0 R/Fc 12 0 R>>>>/Annots 180 0 R>>endobj +548 0 obj<</Length 549 0 R/Filter/FlateDecode>>stream +xÕXÛnÛF}÷WL9EëÉÎKaK¹4RêÐËŠ\Y“\f¹²ì¿ï™Ý%%Sê}hÀˆdr®çœ™ñƒ.uð¯K£õ‡g糃·³ƒNÔÁ÷ü£Ë?¾¼?èûÑkž£e4õ¢Óð)¥)¿uün@Ý.Í–lhx2¢Yâ,thÞhP!â[i©ÌÕr)
-µ¡¯W’ȺVy¿G´Ò¥-(9-$%z“§Z$2¡¥Ñ½œ}oFfnèpemñæøx³ÙDÒ®¤‘"b=~Ú%ÃOGÞµ{Ãh€ ß!kD¬ò²+ü,IçøŸ¤K]ê¥åðLIW³#º’v£Í-]ê\Y¼KóCq+"Ê¥Ít>Iª$q'T*©¦\,Ôîö£»ÜžÈ;™êå¨ÌŽ'-TÀùßz¥©4wxHå¥iJ㉫9½œâc«Œˆf+Ùp„wJ…lô’B|0,Ѓ•*JÚ(»rïÃ$gÇIÖYÁ•ðÍ*Ñ»‘2‡»BÞD¨l±¶°‹¼•Œ‹´*¤d‡®P*ÇãKK„O©Êx×%e:‘ó—>pªCõµ¿š=‘óF¥iáÎÓrñÃœkGÏ WîÑÛåRÅ”(#c,Yíª›êX¤è(-ô½«æ +v-Ž4Aü×@#`a¹Ñ„Š®§÷œÜ¯ÞK¼´GÑ 8Î{ÃQ¡â.ÿ®fÆ…GsµOnlåÓÈkÔ¨8Ö@Ïå/,(‘7Œíp¹fÈøªQ]¤ÉŽþ@w¢þàôˆ6+¯vðà!»¥Ï>CðÞ‡¹÷LÓÏŒï ¡±,KpD¯Ó„u¨TØìKs›·`¯vb8f#|Xú¦×
^ÔÍ_Àˆƒà^Äý\GD:°Ë÷Ýn?~dOÙ.Àn<Ѓ^£t• ’&¬h¦uŠNB’Ïndn[èeƒ\&Íà„X–>ü3ï5¬O0–ÚÈÄZ´¸ÄÇ:·F§ôYä2ÅçZïø)s§Pr|{–$5Z1SX_w`ůjIÊìvUýûœ8=ŠSßrvO¿µ**þ¬Û±3Âê:Õ{”ð?5þKT’u~f; +üÍz†±Q±ÚíSV;B^«ÂxâÃþ¯;HÓÙ³ùI禢WœfÕÿw8}…m"Ö68 +âÍ2ÆÅ]të)o“n‘Aðö”¤}…—Ìj.LjÙðË…v"‚Lünꎅw؆õ)y(ôø ôâ„Y7+ñ +Èu«¨/)KzuhÍ|õ&è²IÝYÒJ¦ÅrÒ×/ýòá׬Tå·å›æF°¿¿âbíQŸN{î<íõO°Çº{×).ÝÓþ£ãôVKÞX§"[(ç±qóíHáÔ,ùÉH¿¼Ö·òÎy-i% +endobj +549 0 obj +1795 +endobj +550 0 obj<</Type/Page/Parent 450 0 R/Contents 551 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/Fc 12 0 R>>>>/Annots 197 0 R>>endobj +551 0 obj<</Length 552 0 R/Filter/FlateDecode>>stream +x¥XM“Ûƽï¯èœ–J‘à7¹ë‹k%e•=ÈÞdi§\ÙÀ€-€1Òô!¿=¯{ +"nRiá´B9l)¶·ºnéx¸nTøc6¾ªmÚ$œ0•ª½Iš\Õ”iåÎ"¶ž>ð¦ÐÝ•{â_¼õu2À7 rÍÛòžeö¾°5à7N´ +)¼5ŠèÝÏO`z +õ‚ˆeµËdè&VƵÑYŸr‹ +ðs[®ûD€žóƒÕ¾ûÆIJ1ܽv¬Ñà º4BÉD{`CRú¡£8èÉÆ9é2±)–oUÀÑs¯E1QÐlƒÈ%6‡Ù›A83Î ¼ÿ®…¼àó›×ê øR]R´Â&¥}'•&ó{º~¸.¸2mlnÐ9»k8 +»ÆC²($V?€í8õÑh_X΄6k<ƒêZ‘UºJìEEåÏΓû+#@æÆʼnÊFô/[£ªB´Ñ'2hJAB‘VZÑ/ÖxØ#tpÐ4Éõª*]B
8{ˆ[v*Lø,†.ÙH»–á†aàu²)M¢òˆè£‚äUÚ‚¤ì[¨{)ÆÅwMì’ÚÄ,©°±â^/¸PˆÝÌkn˜xhÙ<Ùtv¦;Z‘ß¡º +×.Àf ?âÍ&·ºH@áÚ…¢oðÿdèC]B\¸æ´À¤‘ÙÞ `¼IâéRfQ0eÍAç!¼þ
òJ>iéê:%x
Ž¯äÿsïÔ7(2Ïo¨Mê® +{IB=÷3¯V¨ÙϽc·âÆuŒ++S1åw°ðù
û|ÊÖð WóÞÝ= +¸ŒÙNçà~€ÿ‹sçyt;ÕjÑîa›ZgMImÕVy¯i :›4\eØ^¤‰fAA¸Þ¡·D¯T£A£ ßý®è^Ĺâ@¤Öãئû.@md"Z…ôÂ,p.Ym§ªhÓ ¡;Î
!ßû—¨aÜ!(N8j(5²—ÃSÉvR¦èPýQÒñ¦A©g)³oQؾַµ?¹:¹?¹lXx¦Á_1lCƃءý\Y4Ù`œ8R²¡µ[8)cj;¬ÓÝú-|œ ^UÎädríÚ "*,w ®ñÒVcðXLqð2ÍeBÏç0#\çŽñhq1Í´&Š† +(„(‡sŸ“™í8~oÃÐI’|²ùmCGý8݅ꆻ“A%ôY¯Î¥ü
gÓ%æá[œ„a6›Ìop&˜†Ç@sF·Ó³“ˆ~DîèÅÐAƒ¾ + +[&å3…°¶†“9ý˜-g ¹zL§ÿ¸úÛß7#endstream +endobj +552 0 obj +2310 +endobj +553 0 obj<</Type/Page/Parent 450 0 R/Contents 554 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +554 0 obj<</Length 555 0 R/Filter/FlateDecode>>stream +xW]O9}çW\õeA‚” +NSÁåöú£´nu¿3*þJ•Y’›«K©¬!¥Ðš‘g ªB9Ì"}ýŽÅ\‡T9Ö}ˆ)D–9s'Ì]gëAŽÄuÁ€µ$îl€Å3-ÚÔÇç‘\X$Ó®M}¨¬‰p=-žZ©')Ê^MYdÓI°ÙXµ?.¿~¾»ùtý‘;’OQrä¬xm¨w3U{2'Öôs–XªìÀq)ÐùO!t(”×6— @ßê½Ì¾…Wk„
2£5ª.P Øj¨8Ò¯º™Í¹ÔÅ¡‚I†Á“Þtv*o‘ôˆ¤5dËQ¾B꤫›'¥¢n Ìó¿ž}¸Ë´ +ÃÜïÐÑ$ÔóØ£=kV&ÌáºÇSL¤Š¨º"¡½þ ÜÐEeÄKlj™s®…*¹A<^/Ð3ëDû‡›äœ— ”N
~Z@X$¡`3PqÉti44³5¡I—3ܪn¾Š^EăFxdç+kuX…‚-\†Âv¿
‰“ÔA!vSßï0åÊk¸Û +¸¿šs8â+Œ
– :bš…ÕlÕ>4@×ÖÚÛ5eÛµ¥}…nWsLl:àÅ ûSáæâŠRP†{„¾æ$/~MòKÉ„V¡…-´pà4÷Ø´‹œ¤*$‡egZÖˆr¸Ÿ%½VM)!p"½P~™‚ce +±~0–¯èÚÛAÔY»¹Ò,N……”RÈÃ#[bs€ÀBQ’ý¬©À«¤5
$ôÅäväQ<¬Ôzæõ÷Û,%vg*Á®ø®mÉ¿Wß`S®T«fø—GÞ¥Ñ^ám +ŽN1n¡n!AKF4êAó?¾,Å3íNz_²4*Ñ¥ì\ Øó|µì<,ÍDEˆxz®¸ÁäºXŸˆ}¿˜‘Qx·¶‹âOÉòtB‡Ô:<D‡×Ρoð +endobj +555 0 obj +1853 +endobj +556 0 obj<</Type/Page/Parent 450 0 R/Contents 557 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +557 0 obj<</Length 558 0 R/Filter/FlateDecode>>stream +xWÛnÛF}÷WÌC‹º€Dë.Ùh +ØIˆ/•&@œŠ\šŒ©]e—´¢¿ï™YR¤-ê ALîåÌ™3g†ß†4ÀŸ!ÍG4žQ´9ºX½]
‚Å‚šìÞƒMÓàÔÿ×*JŽäÍpzzx5™’W8lpÃáœtr9¡áV .ž-æ´Šåý€VÑñ…Jvæa©£4Ó”éÂP‘*ŠŒN²‡Ò†Ef4»Â–ÿßõ(+(s´3¶Hwi–c¿1¼;,(5; +éS¦O?S”gJ´U·lÜï«oGêÇÁ ŽCl{0úŒƒ‹þh†0ð|Å·ûkkÂ8 +]áèþ¸¶¼¥Ãc +ãØ*çÈ$Ú•k +øYc¬Õ%Øs±¼¹;œÿææê|yýÇ`ð'ÇÈüð±²$÷Ê„C°£Ô§œ¬K2ë +±ß +˜·`R1R«"•=)Ð +.£”˜ù"á²½¾E‡UG)´‘SöIY\òAÚßžÐ$®ïñs÷öÃßo?$` ˆ1+|ý#<éOGÁ¢“Ī’V² ôày3ò5²jº»º@èNåö3øuLŒ¬{†ê +–XPZù‚ŽýÐ’˜<7;4Ÿ†Š×ˆ¿Pµ¶ Ä<ÇÎ/ZhaFåŠ-¹Í:@‚’jJð†ìRSæhdkÂ8\cæƒâ©xf•³VÎ5î‘TÙÌ>ý;›Š¨.¨r¾ËpVjp‰ +\é§ÌÍy“"j)ú°ÏÛös]£Ì%Åíucbvx86æó*Å,D–SHª²ÆÈl¶˜F,>%¸¼ðJ×´UßP–Îñ
@&fH¬Ø³ +endobj +558 0 obj +1624 +endobj +559 0 obj<</Type/Page/Parent 450 0 R/Contents 560 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +560 0 obj<</Length 561 0 R/Filter/FlateDecode>>stream +xWÛnÛF}÷WL]U +¦Vû⇒ôãK~ZP3»·0j +'‘¤Õišz
Ã-Üé§Ñ˜#½aìíy¦:‘KªœÎªœKŠ`éúá Û‚[‰;Ï3 +å(7Ö½PŠ,&Lo(ßéxðÛyúåêñ¦å.Ô¹qýg¤×¯îîÛ‡¹ïŽtùÛ/ +›/¢ÄÜ£ÏDNÑ«r³‚?OßKÏR®_u¾Ab;£«¤¬ØK†Râ‚'%ú¼@ÅMÐmTbÇ™6Rš¦Ú¡®+/ï†òês.5«AÔ΀£\……³ ¤L1»ÖظQ> Ÿ¤¿A*–ú]¥>ÜvD5Õr“Mzfõ¼£2nJä:S¢iˆ\&5° +›™|î„Îd]ÕDåµ= 꾶ÌJ@UË3zt'¿Að¤×ÂZBýÑ„¿"e LyyåÙ-ûI{~³Ÿ°£à|_žßNqŒ¿v0¤{ü%°_NÆÑ$D<êe
cê®ð¥«‚|¾£']Šâc<ZµâÜŸ¹[~sV¶jFa¿q
ä+·;À×UÚù¤\÷ù:üK|{…×V¨Qkƒº˜Ý|Üì6‰],ØÃrï«õÚ:‘ƒý$Á¹éŸ²Fãê~vçpæ?ÏLYé&Í +9¾Ä +y9À·÷nOWß_1Ÿ!X˜’Šw:íöåT7ëüO(.yå@:Ãq
êï'ÿC†3êendstream +endobj +561 0 obj +1953 +endobj +562 0 obj<</Type/Page/Parent 450 0 R/Contents 563 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +563 0 obj<</Length 564 0 R/Filter/FlateDecode>>stream +x¥WïoÛ6ýž¿âV h +ØŠe;¶S`šnYtY׺؆º(h‰²ÙH¢+Ruóßï)JŠÒbÃÖ%’ÇûñÞ»Ó瓘&øÓrJ³%ÅÉÕúäçõÉ$Z¨ûSíð0¡é<ZÑ|µäŸSü¬$eØŠ§Ù<š7+ñ/Ú•ùjG¦[Á%8†›Û?¸áüzNqLë-VKZ§n}BëäìJf6Se’ÚUîh¯d5%ºÌÔ®ÆZ¥EÁ‡Jg*—fDÊ’2T™Õ9ï5Rºc¨òòOeJøu³¦$W²´æÉúÓÉ„Æñ,šâî3UrY`ì^D*…Å=&jöMû¼µÆî€YA7Ò¾3²úEÚ—e¦‘ŽÏµ4°¤Ù6U_dÅO;é̳“ÕcÓúN¹N„UºŒè…>JlñÁ‡pæ K¸–ji¨Ô–öâ'B„tÁ
#¢VÒCË”)™§#Òe~çœbòSÀ¿½¨dDë=ÒWHQlvp»»3Œ#ˆÓØJ%V¦ÜVr=TÙšG„Î~ª*™X]Ý}#—]=z¹|ûì×Wz§KzóúyH戎{•ìV(øXˆòÎG…ÚãÚ$¯Sv —3çf%¤œtÖw8À)¢a>ÈÔ‡ƒ®¬ËuØƈKU–ÉŠ‘ÃU Í…ì6¡‹å$ZBÖ€ç×—-.f—`ZŸ‹hM£8bË©>BÊž74p áàúd¨®ÁÆgœí2
ª”¾Jïw¹ÞŠürŸ0þ8¦ØFL3¼ó`Ítžë#§vsÆʯ‚¹²yòÔß<¡KfqLãé…çHîŠwvO?ÒÿBººGÆ]ûÄÛ7›Ów›Mî7'øåýøÆ|ÏÂsv:¦2uîsoÁúà"Á/¾ùôÆÛl쨅x͈b+<97毵þ8H·ñæ”@ÄU"I± +BûP†;Áu½ÆÕ×éwŸ'ý žÍÚɹœ#@<™bLx(/3'/÷FÙ§1¡Û0êÃ0àç<ÝjtiÏ·#2·0ÐÃQÒíã´õCsYõ/UaYí©$ûºþ'eXÒñ±ÂÓx¯Áuñ…¦}~½jZ]¼XD1-.›™sæÕ3z]éOh?ô“Njþ +'i¾äÏ*gq¶äè;¿Ÿü
s5S«endstream +endobj +564 0 obj +1501 +endobj +565 0 obj<</Type/Page/Parent 450 0 R/Contents 566 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +566 0 obj<</Length 567 0 R/Filter/FlateDecode>>stream +xXïoÛÈýî¿b /r +#Å©ºªÔ>Ðè>*银íh2(yôA‡‡èšÑ„FÈqëUF¤lI£[wΕ£Ñr§mi¼.¢óÐòHÂx*œÚÆ@O¦ªh©Ö~Ëm1q'yV®PÕ ì#ò2΢87£Ââíjõ” +˜hž>Â'ÿå˜[þ +ošØkê05Œ©Ï'Þ³Fù¬™IÝ,ÿa¦4Î8H§¾›NVô!(¢èy +j0=‡á‘}7ItTxÀæÈUä.B»S´Áv8í%{˜sÐɵ{–¥$z÷kÑ„šN
&h2ó÷+5DJÎé[â †Ác_™îûF³sÛƒª×¬Š<T4I¢‡«S›H5nôùÒò—ÒÏ&Ĥk<D†´ÉÙ÷$P-Ž´Ñ¼å +DN@ ^2È:Á˜¬BÛG’‡ÏJ¦Øm6´:íÊ2gÇšT1ÃS5ö*§Î"ÈZ¬‡¥·ÓÕ«{Ãijƒ¶ÈˆtKÕÀ’´ÇÀ“wŽ#.ÖlÊÞŒ…¼Ã3¥>hšT+¦XÊËÞïôÑœöŒé/&ä¡î-øëkêAûžÉÎ@yd«Ÿ4D9×Á³q(äàšÙð
[ø1é´,†YŠÉ½×Žpîšy¬”ÝÆK«pW©½wðºý¾}zs9€¯óyÌŽ$Pœ4ÿ¯…žAZx×À0×
´ +Ãt +PRHQ¿‚¸´Apò.E¯YA×Ä B¦yNÒ»¨ÄiyN¯föµ é5‡³À€ß™†¼ÙîmQGˆAäèg.LòǘþY—p0¦î^Ù²ŠpvñÀ[îD¡,°aƒŸÇž ëd·`Lkpkláisàì7äÕUü»Áa–¬~îß`¥ùû~—EL"¦¹›a¿Xº9IÚÒ-ù¤—`ö# øú§›îÅ{~u=›ã;ƒy²v÷ï>½ÇvîÛü®hk¬JÅorì4Ý>½^à«…ò4½¡ó;ÃÆl[/·ÑG8ßòò÷–_Ô£@ÖÐ?;Ãÿ…—1BðŠ|upq}èrâù
‡Á×ÿ8ùY–‘endstream +endobj +567 0 obj +1902 +endobj +568 0 obj<</Type/Page/Parent 450 0 R/Contents 569 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +569 0 obj<</Length 570 0 R/Filter/FlateDecode>>stream +x•WaOãFýίEª +Rb’ +»(ô’L«œ‹Ý «ð[SP&óŒïpÑ®¹)y¢ð0ÆIÐTD‹rÉIrjN)ÒçÕ +,€o.e,ãðÈSÄýtrŒXõ'M#ŒÜƒ Îé×ÕÍ„ÈÙøs#3½ªyJu$RèÒ ß{:‡4ÇÐÙ
hÊ\6á‘—Ñç« ÓæPh%Xɵ¡‹$Zß941‡êT +ã±Dl¥0èDnI¾ŸÛägKÁÓóýÖ™zzUrLv•;íôÙŽ.½ÓTt„ö½æ´¸nW8àtúÖÎcè⌢T¡ï[ÇÏ>Gb‘é‡^©±\ÂS@•’:‰ò“K42j +Õ’˜ê•3vÉ)2Ó¥M‹(÷—‡«GÈ.xp—fm$MAuý£êÑðŒzµï dP.S•Ú.@ .ünE6`(–Ór΃…R¹Â'½k Õ8ò}OÆ17!Ê£…„emgC«2[B
,¶h—Ù’ÏB`™ÎyžøÝᚹݤ1|½d?°AuY= +9{ò<ü.á›ÉÖ:é`A§çcü<ÄNÏüzq± ÃñYp›jö‹QpôD5š9×gm0“™Nƒ>§ØL™Ý)Ä ×íöÀÕºÖ?ÿq£ãªfѶí›dubÁÊ'(¹b®…[—Ë,‚¦°b½&»”‘š)À]$F—óĹÐ^£.“ÚøN9¾=kv®íªÁ+ƒ_lšz_ÒE”Ò /ÊùÅ#Vzµu;{€(Cüs½ÕóÂÃDg¼8Tµ8þ[ÅÊFpž|…p
‹ò"|€%O§9Jƒµà*×¼æøò–Ž—c¨0eÈŠá(½yùâ2y%›8]% +kÈì-×ŬR#–³œù›JïLÛ¢€”m"wc«Åÿt¿Sù:A^,(5Í·ó6UóN3£3÷—½d_Ê{XŽ·DA¸×psVÄzôðŒ!Vp<1E_²Å0†u#>UËÜemä±Q+ÙqšÃa›è2YXì#(´“\vZ…V¦¥Q–>^õõö,º +¬¼—¹§eÛʹ\×±™“NSBí?µó¡L¿ín'+ºY·†Gàm»Ü¼¡ö˜ð„š™Â1±ªÊy]b¡0 0!Ñ, +:ßÔê-=®±þù,+5ïîUæ²WãÙÁT/*]ÊJX²³îµQX”—ÒdÊòA×7<SÞ +=+1ºª„¾<WñÉj i¬q?,H;væ:§j¯JoœBµæñ
¶˜ºV”x±âð ÞÄöÒ†°2‘—´ÇÑÎI…–ü)ñ–°Ä&Âxb£4i˺™–žVxæ±¼œ³_úQAAqèB«Sƒ·*éôþ΀côâ¥ü±ú×gx-,1®œ1pÂ9„‹6]p`ºi…öÍ¥ÓCÑÇø—.Gh_#0³O‡€c,ÒØïshí—šçýǾ¯oÏ+'ŒÆÁ +endobj +570 0 obj +1858 +endobj +571 0 obj<</Type/Page/Parent 450 0 R/Contents 572 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +572 0 obj<</Length 573 0 R/Filter/FlateDecode>>stream +x…WkoÛ8üž_±0P\Ī‰è‡´iï\|¹ØEQœ-Ѷj‰TI*ŽÿýÍ’’jÓkPçaš»;;3»ú~Ò¥¾º4ìQ@q~ò~zòöÓu»4]àÁÕ¦ u¢N§CÓøôN‘[I*Œ^¤™¤$52vÚlÏi<¥ØHᤥ\I%ÒXŠF—ÑÛhÝE–ÆÂ¥ZÑp¢EB%¤q·±ç$,md–áûÙôÛI‡ÚÝ~ÔC§[i×Nsj¥[ið'Œ£{©ÊpOëÁ襹m!ìô ßÔY™-(µd‘µL(U$È—2ž–Všèöf5‚Ž‘Vª–$ŠB +®HÓ\\À€D·“C4¸£¢4…¶’#Æ¥1R¹lK¥Z+½QuœÞ ºàâ¾ê’b€…<<È“u2§Z9£3zJf<ÖÅYg:Ù®8¤ñG+ò9^¥y–†f§VJnÌ2+HWm³×ÈQ$™Åå¢stV/ +ž-Ž +'8:gèS + Tÿ[£¦\8Çù{Yiuö,“›ìðövðŠ(ð5I—Ò˜b¶Ðh¢Š¹lÄcQÂKJ• ˆJ )Œ–¯Üä29odã»Uõ„°^¹3|Ý€C”*“ÖRËJh4u[zçÃV^"Ul¶ES/…°v£Mbqx+m«£æIþqüáñëÃôî¯qä^ÜìŒ{x H´ +Q_Ö(¥’ñ;J‹H$ °±„AYf<ÝÝ +æ~xf·àuÙ–,˜Tеݟ¢P¾;L k0: +Sª°0âëÙl“*åÀ@ÿÐïíyê§ÐÝ—¡ÖóçT—Ö?^ì—/)+¶ÏFñ£Ë¶V8¿ÒÖý0J«žx%ûª-ïEØÑb<Å€¾ÀÈý{h˜ñüUy›Ÿqü+K +endobj +573 0 obj +1793 +endobj +574 0 obj<</Type/Page/Parent 450 0 R/Contents 575 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +575 0 obj<</Length 576 0 R/Filter/FlateDecode>>stream +x¥WïOãFýÎ_1:éZN‚@BH€•øuWÚ#P⪚괱×dÛëÛ]“sÿú¾ÙuÇGÕJÕ‰#ÄöÎÌ{oÞŒ¿îôéÿú4Ðшâ|ç"Ú9xLý>E)5:S”Ðaïðð¢xw¢<£wÑÜ6lnÛý#{Ž3‹êétLûäÒHø±:—¤¬¤%§ÉH«³IKå”èe‘i‘¨â‰tJ“ˆJ£S•I»ÇçÒ~ÿ¨7@ô]|?ó¬æ#žv*—‰pˆáD^Ú‘¢…Àá©®Š9‡3++Mïê<BTÈi¨*ù©„tÁyv"-µyÆyNáªHnÇ=”*cqÄp¬r|\¬K…sß“éXdÔ~¾©†edì´©‘¢[(Ë!÷[Õá(Uà´ÂÁaPàéñ-=ˆõ9ÑÒ~&\-lŠŒšÖpáYÃ!²úÏ~í€/z#žŒñy€Ð‘~O©?d~qÏá w²Eð¨wÚ£«»Ûó›ÉçË»Iôp÷±ç¾9:£GU€2ËD]é\ çKÎYgôME>{#žþø¤1N™Á{mbï*à¿ F‰l“0”•…ÿ>øŽGãu ýSˆ5LC
+ñ
èxØï¡œ–H# L¢,e‘¨o´–´QOª2•[hâæ5ý¢ýL‘4¥¾,CO¦/_‹œ´äŠ³*ÁSž•TλEb©-×ã@ò¦":0ð‚á1JÙä?jš—OÇ&wÑ58WuîR•!FNo¶áϤyãÓD]V"Dæõ
A<F²dðYè”RÆ*U1å÷¢R†,œŠ½æ;EùŠEAh(i»‚¦·èA¦2Ù’ò°Ð¤Ò>^K-Si¸ñŽz}Z²1À<ú/7W¾ZHÆ:/E¡`ý\ØЫ|ò +#ùÍÉ¢A½£pë}<ŸÐ(Ä‚çt¬³^[²Š¥šT±L:EÞªØh«S·¿†g)jH&EçBj^9¶(ŽÄnÒŒ gÁYöh*eÓ9¾c $o‚£á´NØ…^†®!¸¨’DcáÉØHþc·Ý`aðÖäŸ!/dÎ1‘rW§ Ôûµ±™žßzã +*ÆY³] @òkÉ€ñþT`6\ ™ÃI 9/2SYht¢oÐFŽ/Êè"ÇQA"ë2D4_ð#%L¥¬1[àžº%oIaÔù#¶5©‘ã ]¼-a²¡ææ٠ĹWÉó»†3ß EìöøÒ¿`Œª]#æm©ÆÂâ½ËôþÊE] +€ŒŸø~£ß¥AÄf9óQ±Ì +ÖÈôúòÓÃMô{S×ãÁÎÁŒÍÖ¯4ŒA0„U–þ56ŠéÎ[7©$¬Pü\ a¦$!Ó×äþjI@Þ2a˜ ÷&*Á +endobj +576 0 obj +1763 +endobj +577 0 obj<</Type/Page/Parent 450 0 R/Contents 578 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F8 10 0 R>>>>>>endobj +578 0 obj<</Length 579 0 R/Filter/FlateDecode>>stream +xmVkOÛJýž_1ŸÚ “„4¾…Ç•JÂ-¾ª*!]íI¼ÅÞuwפù÷=»v^¦~ìÌ™3gÎð«7¢!¾F4Óå”Ò²w÷.þ™ÐhDñ +O¦W3Š3FÃáâ´¿É…#—ó–,;Ò5.4e::‹ö†4O£ ÞïÇ9Ów©2½±´ˆé?ˆ2áD",“(¬&ÃVfli#].•‰[kiÙFçÒR%2¬NQª•RÙp·FØ϶M=ºŒÆ>µå´6Òm á•“+Éæœr]2eÒpê´ÙžÓÚ躢’Ë„ÍeeÏ `Þœ®¨2z%>'¡2PºÅ=¼³Ù—g·ÖqI¯ý6oÖ 'µ"Ú¸(üoÀÄ‘×3‹¹xg’Î’Þ¨£šèz ïwsžzOŠLe%b(º×%Ø —]Íž£Ûâ@y8Û´-&MuYæ +É2®ÊѪF»n’4½’Æú¬÷ýÀˆ
ŒVEØ3b»ÌzÙœj:HEQpþ2ËûjçiÊÖÒ“Pbø=H½ÃQ$£•6\á/L§6Qƒˆ$ýвpèô)ʓʱx‰„Äã¯}É7~XÙ$ïHý—)w“§N0¨Â‚Ò_5CJ{Ŧ”Î_H!qÊñS54 +\ë´£tMdˤÖn«¥p7¨[×ÃâîÛçøq¹ˆÜoˆôK…O¼îç߇(~Æ.ª:¹°âEµ éñÊV׆C«ÖQƒ¿”Æèn}tïmuÐJ¤M] XJàU(PiG +‹m#&˪àÒkÛKÌpUì4‡!}§yÍÈðŽ4ËK?øÌewÿúKã+»kx㇠i§ßƒíŽ»è hÇoy…fúÉiÜÀOOrjXÁ4]~”0+¼o¼C‚œ\É5DœE4w¬¥FO8˜`ÖøÏÁ×–‹z6²pÈÝÝ…Áì>ßßA£ôèüxÂr¥IÑŽ +‹4‡gGó;iNˆ¾@ï°ÓHß`ãËsò´Ž· +endobj +579 0 obj +1017 +endobj +580 0 obj<</Type/Page/Parent 450 0 R/Contents 581 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>>>endobj +581 0 obj<</Length 582 0 R/Filter/FlateDecode>>stream x¥WMoÛF½ûWzrP›¶dGrzK‚0Ð8n =ä²"—âÖ$—á’bÔ_ß÷v—’B‚ °-Àäî|¼yófôõl&×ø™Ér.7I«³w«³«û72¿–UŽ7‹å¬2¹N®¯ñ$=_¨¦Ó,ùT›\gò‡ÝØÚÉZwƒÖµ|6uf'«W«Î®år~çªÎäÓãÃßÒ;Soxjƒ<Bo3œ¡·Ë›Y2çñe2KäíÚuJ»pêVf³xj¾ä™‡ºÓ›VuÆÖbó`n>˜´µÎæÝQ,Òí7…ˆ’q^2p)cGà)²0™nñFÉ/…-wë¦ü%æ1» ¡ÜÑ€Àntmï7«¦ï˜–®·¦µu¥ëÎIn[X*-žw¦Ò‰|ÖÒ´Ú᥄”1¥ó!À™žËкy Iv…–gUÕ$(×›Nó@ƒ¸ZU9AZJÄÙ‘!ÍÎú»È}Ÿ9Ž®K]!®è½wš—|™LÕà¼|azâñ€ò_Oï%Ueé.ä©ì7«ò¶G¨ugÒpÿƒÍúRãÄ$U¥Ežu»5)RL—vì0nâòq%™ €H[ç7V€Vm£AEæ‘i<„ÜcJ•JS£«Â8iÎK¦]Úš5òfP±·nç:]]ˆþÖ”pÎ:ópÞ×)¡U¥évb:B¿dð Â]¦v}ÓV{‚žü(Ô z±ISÛS`lm;0Dòd=E
]é…tØÓ‡˜ñŽ× ‚Ò°Õ W£RÓóõ̓|ÈÅ@ƒå
“k‚o½Õ-šÖT–±@tRh/ƒ¡=ÇfÂ9àõýG¹ž”šI±Ò‚ëÞ”¯T¼×(çÐ/.àu«¿ö†"íñƒÙ¡0Žð ª¥Ô ÃJ×)T¿6ÿÒE½s¯ÇpŒ¥ê›®‘›ãy‘Ÿ>ɼ‘,øÌP|•8i¦rëïz?{<P+¸Ðj-®‚ ‹Æ`c´˜Ì:®»(B#A ‹ŒÅ‡xÚj¼uŸÆIs¹Lî0g1=¿ÌËɼá»Ë‘ÇŽúNœ¹xõçí>ÅjJZ¨zCêÌÿcþr~-Üôi**G'@t
k _{Fk2ÿû- Â-2ؾ̢.ì8üaµ¶0±ŸÄ“¢+lï7HňYÖ7å8ñÀÌï$¬Ù7û¾òdU4¤Ã·:*B9Ì "ÄËŒþª¬ÂPâ¦C`•áŒYz‘Ž°Î@‡½öh„Æ{ÔÕýì‹ÏFá>à¼O½Â Ú}£(-GKF@ŒL>BX0üïÚadøñ䛽Y$‹L¾Ùbš¯¤Ëä;§XÄRžâ$Ü?ã±@¸-¡#ª Ôœ jã!YcD =;ø"Ù^Ûo”š hÀ*ïËr‚T¥«5° -KqÜ`ùXcï,Xð›aÃ;ðƒVî9àÛ;HP,!„×€_ +KqÜ`ùXcï,Xð›aÃ;ðƒVî9àÛ;HP,!„×€_ endobj -514 0 obj +582 0 obj 1674 endobj -515 0 obj<</Type/Page/Parent 409 0 R/Contents 516 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj -516 0 obj<</Length 517 0 R/Filter/FlateDecode>>stream -x…WMsÔ8½çWtqª3_dÂ1ÝZ Y2r‘m-bKF²ÇëýõûZ²Kf,u÷ë÷^·œh‰_+ÚisIIyö~öæÏ-V´?à›Ë«íSZFËå’öÉâ‹“Ö‘ÑTç’¾Ü}üF¥Hr¥%%¨©q’îöü—%¡Sʬi*"-JéH8>ÙQkš"õ¾Ò¢VGù*Ü柊^ï¿Ÿ-ébµ‰Öˆ¾Øó ¾?ÉM«é +583 0 obj<</Type/Page/Parent 450 0 R/Contents 584 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +584 0 obj<</Length 585 0 R/Filter/FlateDecode>>stream +x…WMsÔ8½çWtqª3_dÂq »µ²d(8ä"Û[Ä–Œd×ûë÷µd;ŽKf,u÷ë÷^·œh‰_+ÚisIIyöþpöæÏ-Vt8â›Ë«RZFËå’Éâ‹“Ö‘ÑTç’¾Ü~üF¥Hr¥%%¨©q’nü—%¡Sʬi*"-JéH8>ÙQkš"õ¾Ò¢V'ù*Ü柊^¾Ÿ-ébµ‰Öˆ¾8ð ¾?ÉM«é¨ ÜDÎà*Q‡û„•„ïdJqÇÑSS -åsát-É£ÔT˜ŸÕ|NÒiöœ¨mô,°}»øªtjZrÒ9…âQ…˜†^_FÛ>a`Ttdâ£2#W êôÀ!gÜã3RŽb©tÆHøÿ…’fØèjñ$}æcËY¢7Ÿn¯?Þ=>ŽiøÄ£Ñ>G(üÖ2A
Âv\ƒªI…iݘ°Ie-mÉ
¹X™*+“»!1‹Ü][Sè9¢´Bר‰§JØZ%M!,¡æ d`´Û\%9Õ¶qüh͈‡•i¥Nd:Çö:M'ƒÌ»ó1ñÊš£J™`$´W#dÀ4<ªd¨&GÜŽž÷E“e".$]ŸœšykÒ†9÷¸¸¿¾}|M®CÒ% -Uw {qDL\DÄù’Ìyè$·F«™C@Ú¹ÖØ”IU·Œ‰zٯɬW4`¼hªÃuÀíêA|\ô’ÑîÇ×¾AìÏàôv³ÂÏíÕ?×øƒ(‡`)ïhi°¥lßí¼¬ŸMem¢6“5}ʈ©
]¬Ù†ÙÔþa¤5› `àûÍá£\%'’ÿ(W3:0…X°ÊªéƒüKêizJôœ„ÝÌ:Ñ*—‡v7Hm8?¹º ž3Í`ÑÈÈVp//î<qž&K*Lçï›Ç›ÞÞª:7ˆ‹š¸P ¦‹|ÙàC`¢FµIb]£’ia½ô3+E
CrªéØ>‘Ô,¨H!{ …Û`ÈdPO.EÊD™rô—Å{äÙÀÓv¼P¯6“€AX:ÓŠŽIÀo%ZVÁoF ¹ÞXŽé½7À`B[´ÿ²òÑç5±Æ|¹ÿÝ[Û ](Þ“*‹¼|+á`’¡[•XãÌ¡îÉ£!,î
‘ï/òòî'a½³Ø[ñåÉIQÂH¼ÉŒ†®¿¶÷Î5‘µ¸:UØæ’µõÿ -ÛlÂàœ*lÑ_˜`CN_¹Î÷'*Û#pÛ¨ÞéàË0W•ñ€˜çðoA ˆ¤ë7ù°3‹E Fç '€
ó -ÐPjŸàdÀ7ýDî5ìLòÇh&‚ð¼±òG^1Áa¹Ö‚É,àø›_&µdÙø…¡¾{xð€EÏúꄉ¢j4’(Ž9„1ÃshÎrFHäÚðÊ&)'Äê“%Ž -P“yÚùõv]þ¦óëåUtu²°í¢-{ë3?a¸Å=’²ó}@¿¢Â'x€çf«$PŸ:)¬;'y -)ý}öOE×`endstream -endobj -517 0 obj +åsát-É“ÔT˜ŸÕ|NÒóì9QÛèY`úvñUéÔ´ä¤s +Å£ +1
1$¼¾Œ¶}ÂÀ¨èÈÄ'eG8®ÔéCθ/Æg¤ÅR錑ðÿ%Í°ÐÕâQúÌÆ–³D¯?Ýì?Þ><ŒiøÄ£Ñ!G(üÖ2A
Âv\ƒªI…iݘ°Ie-mÉ
¹X™*+“»!1‹Ü][Sè9¢´Bר‰§JØZ%M!,¡æd`´Û\%9Õ¶qüh͈‡•Gi¥Nd:ÇvŸ¦Š“AæÝù˜xeÍI¥L0
Ú«2à
žT2T“#nGO‚»¢É2’öÏNÍŠ¼1iÃœ{XÜío^“ët €õçQO +‰Lˆˆ'…îÇIj˜‰ª*ú,]èÐ,l"*«BÕÈ^œ +Óùûæñ¦··ªÎ
â¢&.T‚é"_68À˜¨Qm’˜FרdZX/ýÌJQÃœ*A:¶O$5*RÈhá62Ô“K‘2ÑB¦ýeñ¹@ö +Û\²¶þ_a›MœS…m#úlÈé+ÁùþDenûÕ;|æª2°óþ-(‘tý&0vf±Ôèä°a fªfÚ„Poû½bÑ_Ÿ>Ï`A©%¡4”Ú'8ÙðM?‘{
;“<Â1Z‰€ <o¬üÑ€WLpX®µ`2K€8~Åæ—I-Y6~a`¨oïï=`ѳ>†:a¢¨äŠcŽaÌ𚳜¹6¼r€I GÊ ±úd‰c#Àœ M¬Šñë +žEµ²ðd0³ª|š¡¬,Ž'H¿ì²~“¢I™t6àY +-2ßÚsˆÅçÙByhÏö {·©Œ)p$S°Ïg9.Ÿ™W€ž·)h‡ßÊÀk6c#F#¹³ªäíîÚ￳"?<-iØd®3:6Úïv¯ ŸoÙ9ï†9[m5»S²HÁNA±I±ÔÉ÷/¶_Ìf”½ÁÏ"Wæú\(ƒ17ð|?q-hÉl‘º)½T‡ÉÍðBß,G¿ÝeâIû™„|1 ±*{lfùˆ˜*oåØß3ÿ¦®Œè +;6:S±ó +hÄC«¼·^
eOË;ý¤ÕÜ6™)œßdA`Á[ +*ñ3}vùÓ‹X¿ÚmÞýbî\õ¦¾ÂdâÉå3ÿ¹ß߼߳Û|ç™~m4«KŒÁ¹§.±ÅÏ7ÁínWã{Û-ŸBJŸýOF×`endstream +endobj +585 0 obj 1683 endobj -518 0 obj<</Type/Page/Parent 409 0 R/Contents 519 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj -519 0 obj<</Length 520 0 R/Filter/FlateDecode>>stream -x…XÁrÛ6½û+v|rglÚ’]ËÉÍqê™ìº•2é‘ Ä˜$ -&4›Òõ-åÍɇÅÉåã;šÜТÄ7·wø¡ «ìêêŠùÙ,»É¦=«FÓ\Û·*Ç¿›Êçë__qò†&“pòb:ÃɳÅZÿèés2–žçósª)*µò½Õä×Êó'ÔYít‹Ÿ[jT»¥ÏÏŸþ"Ói«|Õ®Èm×Ëè“'U×fã8ü]L®³)‡
ΗÆ68dZr}¾&åhmœoQ€;ÇÝU*å4Òh궇ÈZjB:¦~Ó•Ö4TTÚrvÎô6×.K‚?¢6ýjºZŸ£8çq³ªM«)Ô±1öJRڗǪÂK8\¡m…MITÖ€¨¬j}T²7 ¢PÌk“«šð” •Ñ=µÚs`<2Ž¶¸Î: -¡s«uÁ•'ƒÖ…ø¤€KºÞ§L‰‰z{ÜÏis+°d/ -½¯Ã£ÞN~ÀØê{°Gäu¾nMmVÐL¬"LîF˜A_*ñßq®âê -F‹£ìk±ŠIÈÝt ã½éke©3p‰aæ@Éèc¸3ì{¬UY1Ö°Öb”MAáÌ&‰Ê~× oŠ!¶—6¾<ŠVðʲ°odAÐ(ìoâŽJîBRc#DtÌ£kØ@óE·ŸŠÓ 6È-èZ¼l©•,PÑä]ž¨~÷…ôag›Ý,L·×IZ6xÕ€…(›ŠŽrx3½LÝØ݆ûÊðSôLÈ%XIîetT¯÷Œ"¿Ûàí¯ÂKZô
ÝÇ`"é!»šwÿBhB³½®åkÕ®„’HÄžF
DÆ¢À~r4œ¥#sé¹=ØßÏ’,ÆID‡}i†ðŠ,Û;˜{&8>W*;Ÿ À½±
_5²§$rÜ©&+ŽWÑhK¦Yr$ѼHQO¢ƒ³l‡¢4Ú»Â; wôÚÆis¡¹Á÷±Œ‡„NXCò -¼.<° } -endobj -520 0 obj +586 0 obj<</Type/Page/Parent 450 0 R/Contents 587 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +587 0 obj<</Length 588 0 R/Filter/FlateDecode>>stream +x…XÁrÛ6½û+vrrglÚRËÉÍqê™ìº•2é‘ Ä˜$ +åÕ +šq +1>SôéiÁU¾~yjhÒçéMƬÜZ,Hu]]åÏΚµUMÃ,©Z¯m©@ÑÀÚVíªB—¹Ä=üÓuɼ +О–\½ãø‹?žï‰Ðô1¸<óZ¨}ߎ +SynzPW·}#ÓdÚÖav¾È…µ`Iiuµ²ÊîB +µ3‘\Ш|ƒBÈöm‹„“2‡Î0NKÃNoƒà6T^nK]Ýs´yÛCŠásôÒoL¿ÞpR;ÚbXã<„;“Ø3ö*~3&Xg«F +7·†GJø íb¡âWPPQ½ó+íó«Ö9QÄCPÆ']<§Œ¾2u"*cê6ê…U¤úÞkÌ£7I¢…Á·µ1/}'cF÷4´…?eZý<¡ñ!IÜÊÙn*($Ô2ßQµPŒ%Þï:
<í[ÌU‚Ê {†7Å›ã[ +¡s«uÁ•'ƒÖ…ø¤€KºÞ§L‰‰z{ÚÏis+°ä +/!hÑs4tŸ‚‰¤û`ìjÞýK¡]ÍöV¸–oT»JV {t<<5‹ûÉÑp–Ž´Î=¦äö`O|?K²'QöI¤=¶Æ+²lï`î™àøT\©ì|& +ï$l@ÜÑk§Í…æßÇ2î:a
É+HðºðÀ‚ô,"…Æ[—ý,\ÝÈ%ˆá'ÂzMÓ„ëÍ_„öH€Ïôn£½›Ü̳ ~!òž_=wï@%ó›ûÉäx›Š¦“O]†‡/çSüÖ¤øÉoMfó–Œ<8{ǧ± ~?ûqŸÍQendstream +endobj +588 0 obj 1868 endobj -521 0 obj<</Type/Page/Parent 409 0 R/Contents 522 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj -522 0 obj<</Length 523 0 R/Filter/FlateDecode>>stream -xWïo9ýÞ¿b¾]*•4IӤܷBTé8âNª„œµ“5õÚ‹½›4ÿý½±½Ív[¡B‚¬=?Þ¼y3þy2¥ þLi9£‹ÕÉ›ÕÉù»9M§´ÚàËâjI+I“ñd2¡U1r^*?¦U©iÛ(¿…¢JÜ«@BJm·D‚¬Ú“h›RÙF¢ÑÎRP~§qtã<}Óv¤òR"ÎHCM)\U25ŽÖêtõãdB¯¦ã‚IgÁo<ãÄßÏß!üì¨Õ÷}2=.}ì2Qådk±ÂÕZIö1°pnôú<¨¢õº9œ-„Ìná‡`Ã6ÞÚhƒÔ‘Ÿîë•Q;a›.qÀãµµMrŒÝ`=…i§u9Ð¥¢ÃOבtE[Ï„f„±rþDªÚ„1óÇêe£ÅÅb¼ ùÕÿžá/¢Ø¤*¿¦é<Wy2_=©ór<ÇúŠ²çýÞ»¶¦ÛºFØ©¤OáAê3¦Êèª -´|µÞÆ‹ºW1õÖ‚ALéö>¬bEtÃ`à -A^Ø"·aGkåCþÈâÀ#5’ÃÍ!fÀÐ\ý *•<k›ÍÀããå”ÓmÃÌË¥ý-зæÐ@#tACÈ ÄΡjù{¥Ø88ĘˆñxÎVµí¶õÈ -3GÅ‚ÕÞ* ¤º6:5l?š.Ê@Ø÷Àk‡ñ^C©JFV°ÅlÅÿyõ3RAOCÜaMR«ró,ÆhF9âˆIkšJŒØ++ó3B-©¾:4 8¨æ\4gw"#Ö"(*•¸¹¦îç®{)*@¬¯‰‘ì1çÙ‘“‰-‚º9Ú‹C_ræóû×’3ŸÎbÂÇÑÂ’s9¦Ï1yz+Š9sˆýy”Eæ)QÂ(TTK[e•‡‚ [ã"á#äG¸ÉrïçîÛ”\9 -[4@"R³wþ ö¥f CyÍW»6ŽbzÂ{–BQ*x`è%aè±Ý/ï ~¶ÊÂQÒ -m¤!Z{}` ”®ÏÚ+OƒJ£í¿>ÕS‹n©Ò,ðªi½…C6&èÓÍÛ( ¿á§Ž¹Â8ph¯›§ºˆÈñ ÐÕ†a„3嬺Ýí.pT[<¨ä´ß{(–âÆ6©éÀéqJô²bÚ;h¸ŒÒ‘1†mxÀÒÀ2®júÅØ^ˆÈ3è GOŽ*fGá*H$Š-ÊÀâò1¨YÖO.uÊY{áp@EÉ‚ƒ(QQ¥5²-ÝK›K'u(ö,ăà0vÑz¼6 -±{sý}õá}½±ö‘Õð§Ñ™©€O -Ïßu‹hµ4ÉSõ/»%?ç ïFWw§é[oÇGö58”±8«;Àa| -endobj -523 0 obj -1744 -endobj -524 0 obj<</Type/Page/Parent 409 0 R/Contents 525 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>>>endobj -525 0 obj<</Length 526 0 R/Filter/FlateDecode>>stream -x}UMoÛ8¼ûW¼cˆUÛqí䘤 À&È6.º‡^h’’ÙH¤Ê»þ÷;’¯ë.âȆ$òÍ›™7ü1šÒSZÎèjA²ÝFæ4Òªä[‹ë%MŠÉdB+yñÕص±ŠL ™¼×6Ö{r±¦ëZSé<QÜhúËØô“\«½ˆÆVö!êæ’D7.Uj¢#‡×ýû›¬¾&4ž^3T¿èÖ^“Ô> -Ã[‚A½‚P0$y´ß(´È/‰vš¼þ‘–3¬{ªÍÚàe¾…¯t<)z -›a¢J˘óªgÑhzÕ~k$¾w&€ -õÝ´Ú€U|ÖZº†ùj7ìš‹E ç××\€^nŸ¨ 8oTôåùñÚj«œq•²—r¼,®éê¦X0Ÿßf‹eÿ|š?ÎpÅóHjDÛC`Ž ºr; -Úc§Ê»ÔvÒ-÷´ë<XÐ#—݃/R¦,Lu„ñÄ–n‹}wÜ•7Š_î;&Óy¢4p2È·ì6#fu,ÌÝtrò8ïSH•Ñ»½Vg¹Ÿ-Šùÿq?hs˜* ZÍŠ7Ù=¤œîâ
EBJ—l<Œíœ±ÃÉ"Ô®bþMs*€gÐF²?¡e܈¥kf;è˜ÇùÈY™³-ãú;{
Ü%S+¦´’Jï -.y³z €0´C«•q &ÀxÄa”™ýYÄõk¥ƒy3vÙø(@âÎÑ«hÖ‚ƒoåFc@¾‚#.—,<¸ƒ@dpõ–C·a´Ö»ÉHáæ.Ò¬–:ÎŽ2ÙL›¨MÜC†g³z
ÏhW7CëjŸånàæÀÝŸ«B—>^Mq_/qáPv!}CSªD|Ïo–9'ßSzY,ºwVÖ)@Ù. -†Q/3õ<æƒC4Ç
æ
ÉÌð¡ôÿɺ>ì.Ÿt}Ð!é:áãí]뀮ôd¤wÁ•‘>¿ÜgF €øåv9X•N
7ŠùÉ¡c£®øT«Pïû¼õ¤®rY>W§ÔM~×8‡/#âäŽÆ,xRV™3Š9 -Él03¨
œð`ˆŒÀ'›(¨1?õiÓ9cx‘ VÃþ`|½Èóé
‚÷œÈ×}|OË‚OiœÁG‡ñëíÓÝ-½x÷]ËHŸœL
Ž›Ì -ï>îV»egL1_ÎQ˜7½¸ºîý=ú1x’Tendstream -endobj -526 0 obj +589 0 obj<</Type/Page/Parent 450 0 R/Contents 590 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +590 0 obj<</Length 591 0 R/Filter/FlateDecode>>stream +xWïo9ýÞ¿b¾]*•4 iRî[¡ªtq'UBÎÚÉšzíÅÞMÈolo³ÙVè„ kÏ7oÞŒœMi‚?SZÎèå‚Šêìõêìò휦SZmðeq½¤•¤Éx2™Ðª9/•ÓªÔ´m”߈BQ%T !¥¶["AVíI´M©l£Ñhg)(¿Ó8ºqž¾j»ÖVÒNù)$Œ¡¦
®*ˆGku¾ú~6¡Ó—ã‚IgÁo<ãÄß/ß"üì¨Õ·}2=.}ì2Qådk±ÂÕZIö1°piôú2¨¢õº9\-„Ìná‡`Ã6ÞÚhƒÔ‘Ÿîë•Q;a›.qÀãµµMrŒÝ`´ӂºè³RÑáÇ›¿Hº¢€gB3ÂX9ÿ"Õm˜ƒùcu†²Ñâåb¼ ùõÿžá/¢Ø¤*¿¢é<Wy2_ŸÔy9žã}AÙˆó~ç][ÓÝ-Ý ìTÒSxúŒ©2úŠªƒ-ßD·ñ"ƒîUL½µ`S@º} ÷«XÝ0Ø0Àªs¢5Èx‡ºK&nÞ>ÝÝÞŸw܃ÑÛ²1’8Œ+\å/ïïþ¡}©‹’JBv«ÈmØÑZù?r…8ðHäpsˆ™04W?ˆJ%ÏÚf3ðøx9åÆt×0óriôÝ94Ð]Ðr±s¨Z>Æ^)6Ž1&b|ž³ÕDm»m=2 +
¨Ø¯)W@Ãn4Âùoà¢WõÈDˆ +gvˆ˜•#ÜhP6]©‹”Å Û#Qø´U?›”ÒÙx‡ÖäŸc…™#ŠbÁjï +R]¶Må ì{àµÃx¯¡T¥ +Ü\S÷s×=ƒ•
NÖ×ÄHö˜óìÈÉDAÝíÅ¡/9óùŠýkÉ™Og1áãhaɹӧ˜<½E‰œ9Äþ<Ê"sƒ”Š¨á +BÂoø©c®0Úë¦Ä©.¢r|Âtõ£aáL`9«nw»ËÕÏ*9í·ÄŠ¥¸±„Mj:pzœ½¬˜ö.£tdŒa°4°Œ«ŸµFý.blÏDät£'dz£p$Åe`ñaÙÔ,ë'—ºe¬=s8 ¢dÁA”¨(‡R‚‰Ù–î¥Í¥“:{âAp»h=^€ñ±ê8wLPˆ‚• )`W,N7o³WWh·_·äl1ŦÐßö–Üw@"—Èƽqv£1eâ/ìã™]AlvÚ†ÕS`dY,;>"«
¬l1FуØBb½ÃÊ…/ÉE·æõv¬ºÅ¶&ªµ¸Œ².ÐaO–¶gÐ×zLÔaÑg¾J•öÞÅ•VA0ƒÈ1P°¢¥‹j< lØEwƒH2MS¬·Âóœk<€MM*dg—/oZÀ±i-”ÌYa°s+Oè±×ø&À÷8ß`¡å-02بŸÀ:ˆý‰ÅÁäàhÝjLtL‡|Ú±!8dHT®ÅžÇ§¡Äa:t*ÑÈÆÕÜè)Û5&-ö*ìjƒØ½¾ù¶zÿ.ŽƒÞXûÀêøÓèÌTÀ…“Âów`Ý"ZF-MòTý«nÉÏ9ÈûÑõýyúÖÛñ‘}
åE,Îêp +œÌôÇötr…÷Á¯5b9o±þÔ^ŒéO]éô2‰ëø3zð5?ùÒþÇ(gŽ7?ö=<Z÷.ÄøNü†L+ük«1´9Lˆ7+#È‹18Ø9Ëð{bÊufÑt±Oñ¶}ÅWä,}ôî;4”nûï,¾õ"~±œá,Gÿóa4_Îñ¢Š7æ6þûì?±£÷ãendstream +endobj +591 0 obj +1743 +endobj +592 0 obj<</Type/Page/Parent 450 0 R/Contents 593 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>>>endobj +593 0 obj<</Length 594 0 R/Filter/FlateDecode>>stream +x}UMoÛ8¼ûW¼cˆUÛq䘤 À&È6.º‡^h’’ÙH¤Ê»þ÷;’œ¬›.âȆ$òÍ›™7ü1™Ós*t±"ÙNnÖ“wKšÏi]ñÕeIkE³b6›ÑZž}5vc¬"H&ïµÍœÅEì„iĦÑT9O·šþ26ý$×i/¢±5…Cˆº='ÑÄKõ–:çc èÈáuÿúæëï“MçÅÕÏúu„×$µÂpÁÎ…`P¯ ;I¾ÙoZäÇçD{M^ÿHËÖ-5fã…ð*߈Â×:ž=…Í0Q¥cÌyÕ£h5=k¿3ß{@€š§&Õu&â:¡œF¢}g‰œJ'…†î +ZoÁ*>-]Ë|µŽvm‹Å"Ðãós.@O×Tƒ„#7júòxÿí´U·‚¸Ê‡;9H9-‹Kº¸*VÌç·ÅªžRóãéÇ®x¾Iè:`ÌDWn +Ž¸\²ðà>‘Á5; ܆Ñ:ïv&#…›ûH³Zê8;ªd3m¢1ñ +ñ½¼*sN¾¦tY”Ý:+› l㨃—‡zóQ‚1šãó†dføPzLÈÿdÝvç¿Oº!èôVð‚ñö®óF@Wz0Ò»àªHŸŸn‰3#ÐV@ürû¬J¯ƒ†E‹üäбQ×|ªÀÕ¨×}^zRW¹¬Æ+ÈSê'¿oœÃ—‰ÀñrGc¼V)«ÌÅœ…d6˜ÔNx0DFà“ÍNÔšŸú´éœ1<‡HP«áFÿR0¾Aäåü +ÁûžÈ—C|ÏWeÁ§4Îà7‡ñóõÃÍ5=y÷]ËHŸœL-Ž›Ì +ï>íWMûegï˜bY.Q˜7=[– ¿'ÿ1y’Tendstream +endobj +594 0 obj 1010 endobj -527 0 obj<</Type/Page/Parent 409 0 R/Contents 528 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 191 0 R>>endobj -528 0 obj<</Length 529 0 R/Filter/FlateDecode>>stream -x•XÁnÛF½û+91€MK²"Ù½9†Ý(’4v›|Y‘+sr—]’Võ÷}3Ë¥(ÚAQ0D‘œ™7óæͬþ>™ÓsZ/èbEYuòññäüîŠ3zÜâÎj}I9ÍÒÙßdÉM¡êV{ºLé÷O÷Òí+Ó4ÆYúhÚ†”ÍéÛ½ÍÝ®¡Oïÿ:™ÑÙb Éu–馡g[ïJúÕ4mð»9ž`wgótÁ_¦ó”þ0zgì³Í -eŸùBÜÖƒÛ†º†¿n
‡DÎ:oÚ}ïz¾J@’UºçÞß’æóÞßbÍw?é+6TµQ´Hgé’¼.µj4™Fn©)a™¶ÎÓ70²Ï¬4Ú{ë‹æG'«Zó¢‡pð¡m§D -%a¹dA8Tó2]¤ô‹Û1¥]„fÛ\MÒƒc1’Ž¿Cj@cnß%‡&0¼Ôg¸Ì¾Óδ…pÄ›ç¢XÇí½éÚ–ÁÂ…0ÇÁÜÜxÂ{Ö‘Èn¼`[=m•Ü³0”ÐЯþþé|k‹”¾(“²Ò¶£ÚÕÍYWŸrpˆ†=ò½ - p$îxß;ìfÉëlÜÅ0‹u•»1Ä׬äí½*Ž÷C“ºJ/¨Tè× -{%„$껦ÏowxTÆëR#iH ‹¥”[G\¨ 2!¨ðš×7ºÜÒS"›KŠ /
˜Ñ V]*¬)qz°ðé¤T8µú
FøÅ€¥ŽFz9ˆ?\K¯ÅŸ&ÂFvÀQö„™L-ÎŽÇ +„êdk‘–…ÏáÀÉFÐÆ)„“N?_1u1Ty›0v@&ôé´zQ¦TÞyrô‡úwNvý1Ï{J×8ÆñÊ -°µçºl|▊ͲªÃ9OÍýïÃ$´X<ÛÏ¢ÐÑ}z1ˇôöÛr`` -·_™ƒ°IÙ8™˜˜BËó»Ë~ -]ñ‰õæýž@?ú
a¹æ©†_(òä⊡áÈöÛÉ¿ŒJ#þendstream -endobj -529 0 obj -1802 -endobj -530 0 obj<</Type/Page/Parent 409 0 R/Contents 531 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj -531 0 obj<</Length 532 0 R/Filter/FlateDecode>>stream -x•XÁnÛ8½ç+ºD\Åv\'ÝË"I“EmÚm¼ír¡%*f#‰Z’Žã~ý¾!%[’Û‹…ÒäÌ›7oóïÑ„Æø7¡³)Î)-.G'73šLh‘ce~~F‹ŒÆÉx<¦E/VÒHR–DEwJWzSQªËRT¹•p´QEAmžðÉè^”KAØž‘( -½!Ak+MX¼ÈJU)ëŒpÚPmÔ3¾,å«Å·£1½žœ&SܧºªdêdFä4gN“q2#œõŒã„%£µãõt%ªG‰`$!8iìJÕ¤s¢\Ò’®h©˜ B§¢@7÷aik,I›ÁíF–ÚI*õºâü~ìj¢È´Lh±&˳P…X’#ª…q|3‡Â‡žÜÌ`ã{™jÙü¶…;fHL×F¹-aݳ¥
~rQoý‰R”[º( -e‘§È7tR”£N8¹Ñ¥_.…ªš=¹«É*'>øzq„*ÓütžÌiv~†Ï@˜Pí<â-Mf
)ÆÓä¼G‹ód–Ð%7ªzô`2@™2¨šF -µ4¥²VéÊÚŒQä)Œy…è”Éh¹vÙ -•>q 8gZZüdi]£è™…~^°ºZ0;˜|á -µ°‚–Q&œX -‹*øŽé`š
-ÙËoœ‹ÂzJî%9æ¬yÚ±ÄÑ¥%Pð‚íáÜ¡&û‚uhÖêjt
éÜêJHï¸ÞíÜpI÷œÝ¬!÷WºrFÑ–‚è¶PÀ¶×™ÊsèXå|mL#Ò>€V?”´#²šnqU&¹äˆ‚Ü”Qè\2(ª€€íÛ/Wƺ®Ü¾=EËýZîNß¼…$v§ ËÝ$¡¾º£Hýº2=vÚf(.À¡]Sœ<½®O@,Ð
Üyf€š>±T#mªŒy)²hDÉä¦>þ"ñp$& -FÇcýﻲ¿¿« þ›Ì\ˆ¡ï¥&§nÚµA¹z‘wP`¤vTõ1ù¼‡
~Át¨¶aëþ,˜%ÓÕ±cº@nÙ—Á%"?¦ 5LaÃl£•mQãÀöƒBŒ‚Ï;.”p°5Ê¡Qƒ¼´W¬Á5Ì„¸¶k?,…}Vv§€µ‘¹z Å{x:äAÑ=Ê»Ai*=ˆ´ñÀ£(ÏÍ!Ä—kxjv*+nbLMf×½à«t/Fï²™ïLfá=¨J×…h˜í硯%;ÏóhÊ3Šð;ÝÂVš†ucà£þ…/ñT@Ž¤ÔÐt…<–ÿט4…@‰ñº[ôKÔi¥h!ž$}lûh,QÂAÜà%ÑC¼Y)Ш¢”¢ò. ò”|xå#2’§.:‘9Øäæ'Àn|·ÚÀv%ž[#2õƒŽ£ÑA ™ûÞÿaÌmpžHÈÀ§zm,—FO Gl-´~BÑñƒ ïÒè5 ¢âµn‘ú Yf¤ÃkÃ?iÕlcj¬09€4‡ÀÏ1®Ï#t— †Ý89e§ÿë8‡‡ØþÈpšÐ»Ãÿ´÷å¥VÕvS°Ý‹iÎÆ<HÜîñE6¼¾ -[dÔôr°™}žtÉýùëeÀ+ë¶Eû†üiNˆ+…à'hgŽÉ‘²yâ-Ûo6E^Øñz{4À¢‹Rí<DC,Ñ©aàãÂ= -Ï—û‹—ôÉèoGôN§k6›Êë°ýõÙRÈâÿ÷vœÍðöô_œù4¼[ÿ:ú¶±7endstream -endobj -532 0 obj +595 0 obj<</Type/Page/Parent 450 0 R/Contents 596 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 200 0 R>>endobj +596 0 obj<</Length 597 0 R/Filter/FlateDecode>>stream +x•XÁnÛH½û+ +91€MK²"É{s{ÖÀ ÉÆžÉ|i‘-³7d7§IZ£¿ßWÕlŠ¢,Q$«êU½zU¿Îæ4ÃߜֺZQV}~:»¼¿¦ÅŒžv¸³Zoè)§Y:›á›,¹-TÝjO›”þøòðoú¦}ešÆ8KŸMÛ²9ýx°¹Û7ôåéãÓÎft±XÂFr“eºièÖÙÖ»’~7MÛðìnŽ'ØÝÅÕ<]ðÛtžÒŸFï}£Y¡ì_ˆÛzpÛP×ð×m¡á¨ÑYçM{è]ÏW)Hr£J÷Òû[Ò|Þû[¬ùî½'cÅÆ£ª¶Šé,]’×¥V&ÓÈ-µ5%,ÓÎyúaFö™•F[`obÑü¨ñdUk^õ>´-─s~p†¸hëþæ×éˆnår³;ˆÛÎæÚ—‡÷°§1Á+DË8\ËþU‹:Œ™òzוdî9Ê\U{‡Êi1kävr-I.\ÓRÈ,øÎZŽÁÙsŽ0æ·ÇÑ´¦,Émõnñ‰Ë±3¥¦c¥`¡ÔœI„§z»¤òÊX0Á«YÍ”åD ¬»§3fPæüéûog‹õ,]ÓòzƒªV´¸^§óþª¤Gæî—×Rò#glï-T•)ª¶Åá s½S]ÙÒ«*;áS¼ª4q"”±«Š®W駑ãñ5î®®‡ cX§Hü]Þ/zFLÓ°É"OYIMW×η’ðÁŒ¤FÌD2'T¨†¶Z[’^Ñ9íPb~íò-.Œ¿ÎúíTÙèðÈÑøqúVÒúnúÔ95àk¥¬©»\‡ +þ‹‘tü=Rsû.á8´00᥾Àeö“ö¦-„#Þ¼-À:nïm׶~,´€9ææÆë>°ŽDvãÛêi«äž…¡„€^xõ/·à[[¤ô£@ñ˜”•¶Õ®n.ºúœƒC4ì‘ï@«¾ É7ïôÖ艶%MB8¢ˆÚ!êŠK48ˆâ¥è‰%cëY¤¨«å1ë|¥Ê¾‘G +°Š,tU[hƒbÍ0F:غšÙä‚.„#E¿¼hšÒäEÒ‚ÈÅ:Zûà:B@pÝhnqÿ¡fÍùÔô·ã9åIòæQºérà +þæAÖ“IÈ_÷Vû¦0õäá·)SÏ_¸‰´`™b"jÐbkïA¤ +ãU½hºAýÕéÔ£dEñ-RÄâ_è2GåÂh ´G'qœ£j¨ºÖÊ“ à +Tìãâi+Œ/Af €á4À”„Ü=oRa/vÍX¸T9/›XT$´^lM¥1ÿ‚gËq<YÇÎÅ(û§Ø£7ሼ'åä²`iñ@ÉöúTQ‰±ˆ†ÄƘáÝAé™àv,§ÌÅÕÿÓÅj9›ôê¸j={Ÿ¾ƒxJã…]à=¸ú‰z6ÂÉÌ@YtY²]îá}áÈímÈô$ÓJñ¹” îh?IÅÈÜô‹vµŠþqZÆÑ/Lï¾ÿy÷ýùY¨ôœüÎêÄvž?Nb½™Æ +6ãO‚¡)^fóQ·Ÿ¾>ŠåAƒƒ^¢œ¯ÚG¹Ìq<¿0&¡ +Ö¨æ²É×H¿5jå!…\YÙܦ‘Ÿ þ…ÏÜ4™7uXi[ždrð;*fŒ}ÃÈ +"‚ +¡y}£Ë='²¹¡˜PÀðÒ€
bեš§Ë +ݧ³|Ho¿-‡ +endobj +597 0 obj +1804 +endobj +598 0 obj<</Type/Page/Parent 450 0 R/Contents 599 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +599 0 obj<</Length 600 0 R/Filter/FlateDecode>>stream +x•XÁrÛ6½û+vx13£Ð’¬Èv/Û±;î$N«I¾@$h¡& €,«_ß· +sHÞßý˜ÕÖ–‰ÕK8!¢¡g’)[bö +;ÒüNK£3C;ðò0ˆ¼—õQµCT„k®2Y9•où3#Ý XpèÏȯqW(à ¦ßn®F®d‘µ•õ)ÔÂZZF™pb),ªà;¦ƒý]hr4< ++d/¿q. +ë)¹—䘳jHäiÇD—–@Á2´‡s‡šìÖ¡Y««Ñ
¤s«+9 U¼ãz·sÃ%Ý;p~t»†Ü_ëÊ]DCX¢ÛBÛ^Cd*Ï¡c•óµ1Hû +Np#PPF¡sÉ ¨¶o¿\ëºrwzqŠ–û¹Ü¾»€$v§ ËÝ$¡[¾º£Hýº2=vÚf(.À¡]Sœ<½®O@,Ð
Üyf€š>±T#mªŒy)²hDÉä+¦>þ$ñp$& +FÇcýݯ»²¿¿« þ›Ì\ˆ¡ï¥&§nÚµA¹z‘wP`¤vTõ1ù¼‡
~Ét¨¶aëþ,˜%ÓÕ±cº@nÙ—Á%"?¦ 5LaÃl£•mQãÀöƒBŒ‚Ï;.”p°5Ê¡Qƒ¼´W¬Á5Ì„¸¶k?,…}Vv§€µ‘¹z
Å{x:äAÑÊ»A—i*=ˆ´ñÀ£(ÏÍ!ÄWkxjv*+nbLMf×½à«t/Fï²™ïLfá=¨J×…h˜í硯%;ÏóhÊ3Šð+ÝÁVš†ucà£þ…/ñT@Ž¤ÔÐt…<–ÿט4…@‰ñº_ôKÔi¥h!ž%}jûh,QÂAÜà%Ñc¼Y)Ш¢”¢ò. ò”||ã#2’§.:‘9Øäæ'Àn|·ÚÀv%^Z#2õƒŽ£OÑA ™ûÞÿaÌmpžHÈÀ§zm,—FO Gl-´~FÑñƒ ¥Ñ#jDÅkÝ"'ôQ³ÌH‡×†Ò0ªØÆÕXar +ÀOÐÎ'’¯"eóÄZ¶ßlŠ¼,°ãõöh€E)¤0Úy*ˆ†X¢SÃÀÇ…{ +endobj +600 0 obj 1789 endobj -533 0 obj<</Type/Page/Parent 409 0 R/Contents 534 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj -534 0 obj<</Length 535 0 R/Filter/FlateDecode>>stream -x•WÁrÛ6½û+vtRfÙRIéÍ©›i&MÜ6ê´_ ”“¦õ÷}»€$ -r:ÓñØÖˆÀâí¾·ËïSºÆÏ”3z3§¬ºx¿º¸úpCÓ) -<™/´Êézr}}M«l¼Újò:³uŽ-Ù‚rãtÖZ·£F»Êxolíi«<Õ–œV%UZÕ¦Þ™šZìÿëËÇN÷Ö•9)ÄtºqÚëºõ¯Vß.®éõôÍd -ø-Ë=h™{ã¤îbQŠÎÍ™šj‘¢¨EûۚͶį\ #Ç<¢H -?(!·×YUÂ]y çv¢®Ì1$Rá+'4(?òÎp[œ´Âp“ -˜L„áõE¦A¢Ãˆ&Npœ«s÷äî“é8g¼åØÐ;Da;^ûA8X€Eýaà¶ÄJtÌ`^<wÝþŠµcÔÁ·xr¤ìG,è¦{\·œdÅ¡q«bœ«Ë8SNç‹É”æ‹Åd)¯g·ŸßßÒïÎ~ƒãÑͺ -F"“:G–¿^Ìð&›ÿïkÍÍâÇÈÖ›)Çá\üW³Óeendstream -endobj -535 0 obj +601 0 obj<</Type/Page/Parent 450 0 R/Contents 602 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +602 0 obj<</Length 603 0 R/Filter/FlateDecode>>stream +x•WÁrÛ6½û+vtRfÙRlIéÍ©›i&MÜ6ê´_ ”¦õ÷}»€$ +r:ÓñØÖˆÀâí¾·ËïSºÆÏ”3z3§¬ºx·º¸zCÓ) +<™/´Êézr}}M«l¼Újò:³uŽ-Ù‚rãtÖZ·£F»Êxolíi«<Õ–œV%UZÕ¦Þ™šZìÿëó‡N÷Ö•9)ÄtºqÚëºõ¯V_/®éõôÍd +SjÊ +0JzøxŠ{Lë®mm=¡_m¯Ÿ´»äãQ-®.•¦2jEæ‘šÎk~tEXZcaÏKmW¥· 0S·Ú©,D1J†¾Em”Ë#¯G9Q¥ü7ÖNŽOMÉ ÷î¾ Jmë +FŪ¾ÜÕÙV³Z€=éŸãG–ިÔP +F"“:G–¿^Ìð&›ÿïkÍÍâÇÈÖÛkŽÂÿ¸øW´Óeendstream +endobj +603 0 obj 1614 endobj -536 0 obj<</Type/Page/Parent 409 0 R/Contents 537 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R>>>>/Annots 204 0 R>>endobj -537 0 obj<</Length 538 0 R/Filter/FlateDecode>>stream +604 0 obj<</Type/Page/Parent 450 0 R/Contents 605 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F6 9 0 R/F8 10 0 R>>>>/Annots 213 0 R>>endobj +605 0 obj<</Length 606 0 R/Filter/FlateDecode>>stream x¥XMÛ6½ï¯ä²°«•ü½zHФŠ4mãc.\™^3+‰Ž$¯×ùõ}3¤$Jv¢E€$’Èá|¼yóèoW Åø“ÐbL“9¥ùÕÛÕÕÝû1% 6ø2_.hµ¦8Šã˜VéhcËTÓÚ”:my¤J§ûÒÔGÊíZ¿^}Åæi»ùv<¦Ø>úT`“¢}¥KJ3“>UäÖÎüÚÑ«O¿½êoQmIívÙ‘ê&Úé27UelQÑg•?(ÊÕ®’oæY½¦àÍl0¦ÛdÙ>þî±´ûÝÝÁ–Ùš¨¼;ܽP]š]¦J}CªX³É‚&Ë(ÝêôIŽH·ªxÔëÞ!È‚¢Áfõ¨LQÕ²öÁÔ[#S°ïVWœ>É!%ü¿¿~½Jæði>aÏrZŽÛ‡Œ>s øÉT¼îRÏYðö‚
9%ñ2š{[Íöþyå#u5õ'•TÕ“d®5"î‹‘¦¶#Ú©RåºÖeDoŠ#IÌõVÕD]jdÎåK^)¼(l-9A]®“k¤©2Ug†xQ¦75}+N¶…S™-€ IYká"*Ù×]iŸc¥[g¼ETjóªÍƒÉ˜»¦ÞzNG1(‹[±ChË;>Û´Q©ß‡ðÁ4¥]ïS½ŽhÎáú6TwRd¤ÙyQ[Ð!¨&[ÀsËË}¿[8¾x±Xø9ó³j>‹!”©ü랺ÊÇL3!™ÿ®_j·0cÓ¦uCgÕõ˜N"¨.ÄAx~NSÁcß›¶Š§8@(dè+¹ÉÓô«0@ÓåRà.ÃÆ=´1O—÷½ˆ›)ÕòE܆ð@n§Ü–Ú²ÔÕÎòÜðLã[å<Í ÏI,gH Kh!¨°´u'ýÓ§;f»86ÆÊ+¢
9tàbƒªTv¢ÑZ&xÓÉ–^£C_°ùM;~ðwÌ+¯Št!î»îÑ•»õ(ȵun "S¸SŠ7Ìd2]gW[ðÏS“UC‚¨j¾pŠ|ä¾å»*kë–Z)"8'r2 \óòh÷¾ ÏNíw|‹awÀØ-çVþÔÍž¯¾–…m&·.ÇîžNN¼@€pΔ"VÁNÅzP‘ÑFËW—ÕUq]{I§p}DçÔ&Ýgªô—*H)ÑB¢nø -Ž*ˆÍ—ÑìËké°ËÃZh¸)ŒËrµÓ©Ù˜”Yœ~â$u}‚QÑÀ°c+¾~þ,2€Ôs´†…ƒUMÞÃ_i~`òÜæ^oüîýÒ§)™/p·›ßO¨Ñç7ß¾¡?JûÁÑ/6Ýç¸Ë´b—p›çÅ·‹1~BZ–Ñ,¢râJ²Ð/ÝÑÌ+Þ>]L! +Ž*ˆÍ—ÑìËké°ËÃZh¸)ŒËrµÓ©Ù˜”Yœ~â$u}‚QÑÀ°c+¾~þ,2€Ôs´†…ƒUMÞÃ_i~`òÜæ^oüîýÒ§)™/p·›ßO¨Ñç7ß¾¡?JûÁÑ/6Ýç¸Ë´b—p›çÅ·‹1~BZ–Ñ,¢râJ²Ð/ÝÑÌ+Þ>]L! endobj -538 0 obj +606 0 obj 1656 endobj -539 0 obj<</Type/Page/Parent 409 0 R/Contents 540 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F2 5 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj -540 0 obj<</Length 541 0 R/Filter/FlateDecode>>stream +607 0 obj<</Type/Page/Parent 450 0 R/Contents 608 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F2 5 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>>>endobj +608 0 obj<</Length 609 0 R/Filter/FlateDecode>>stream x•MSÛ0†ïù;œÂqãHÚôc¦Óii3í‹"+X`K©$“É¿ï»ò®n.1’vß}ö]é÷$¥9þRZ-èü’d5¹Î&o>-)M)Ûbår½¢,§y2ŸÏ)“Ó+O¹òÒéÊÏHºÕFÐ"™'K …¢p¢RA9OïN³G[ôÁf‹KìÊò©tJE•ðO¼gNýÊÖ:©¨[·¹çÚ)¬;¼~x°¥=?,¨Ï´WNQíUŽ*|P"'»Wk/kÏ{ ìNXËÇlt±\&Z®Wøâ ±¶
»·”¢Ffw‘2”!½u²Jè³!ƒ¶†ö:1©ÂäÂå-Ï.‰À¹(»ÛióÐ -C´n’ÖlK-¾Â^)ÓpíƒRÔâU g-šò•¬¢\‹Ò>h;4ÊÎ!6‡¸qD¬–P{¢sÞQ´|Dû(ØvOõŽð©»J© +C´n’ÖlK-¾Â^)ÓpíƒRÔâU g-šò•¬¢\‹Ò>h;4ÊÎ!6‡¸qD¬–P{¢sÞQ´|Dû(ØvOõŽð©»J© endobj -541 0 obj +609 0 obj 853 endobj -542 0 obj<</Type/Page/Parent 409 0 R/Contents 543 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 213 0 R>>endobj -543 0 obj<</Length 544 0 R/Filter/FlateDecode>>stream -x¥W]oâF}ϯ¸â%‰6'•VU%]Ô|íB»ÄËØÀ{†‡å¥¿½çŽmHP»«¶‰DbÏ×sÏ=çòõh@}ühÑðœÒòèjvt3;êã1í?̘
‚ˆâñÿÇq“‘´àÄ6»Lo/(êÓlÝÏGcše~oÒ“ë•X;iè" ÇiD×E.•£Ÿg§³/G¼t×K{C>q–\ƒ€n/?ZžÑ§Þ;ÕoñþƒÞP*M(Õj‘/+Äõ8
#ú,Ìš®µR2u¤
½z“°$(õ‡7›ÎŽôd©SQ&â'ðp´÷ð%?ý|!":E€¢¤x4Æßú© )CÞÆ4Ô·8
ß -'OÄ»)°HIG¶Z¯µqÿkW„Ýyîjò8%ý‚lÔçt(39?â<¼¹ºùuò/éEc¾Ãg¢¬¦¹ZK”On¬#·AêõRâ¡MîV~,V’^K#O'»µN–ÌAI!Ôsûœ‘ßÖ…È2”+¿˜©ßä³E®ªE@“E]´â(ŒÙ–)ÖúàdÖ¥¤ruÖQ[,‚Í°ßt@Ôæ™#kðïR…€q‡ƒs;SY -l~b! -M® -ÇP¡¡? W²Õ"ä5Q¯~V&YFP%J .CrðÂHkñ¤ý!ö0…õq–8d¢óà×ÞåÖuºlv-Ó|‰>O¦M|, -endobj -544 0 obj +610 0 obj<</Type/Page/Parent 450 0 R/Contents 611 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 7 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>>>/Annots 222 0 R>>endobj +611 0 obj<</Length 612 0 R/Filter/FlateDecode>>stream +x¥W]oâF}ϯ¸â%‰6ÈJ«*‰’.j¾v¡ÝVâelà=ã‡å¥¿½çŽmHP»«¶‰DbÏ×sÏ=çòõh@}ühÑðœ’âèj~t3?ê“ í?Ì +˜
‚ˆF“1þ‚IK^Al³ûÀôðö‚¢>Í—Øý|<¡yêÇñ&9¹^‹ÒIC=Î"ºÎ3©}xü<<9⥃Q½´7äçéÉE0èöò£å}ê
±Sýï?è
%BÑ”–ÙªB\³0¢Ï”t•’‰#mèÕÛ K‚x³éà<àHO–˜:E,~âG{¿_òÓÏGÑ"¢³q( +'ø[?å4cHÂÛ
õ-ÎÆÃ7 +hæ„qD÷OóYpóûM—å$yæ=þòê¡ jdéîòiÖñGÖSyn‡Ë‚õê +Ãöo<‰u• +±mÄUSª7*×÷PT•©€;pì•“ÃŽ!«+8ù;@߯™Ë™³ÇùóFœq_›´‘q)P¦1PODºøꪎ¢–¬ÚçÙàZ›íÌÑ97 +÷6QÒz’ßØ· +Ìc>¸… Ï&XP4ŠÈ?5ξïsZîcÂø +@ô¡J3ëëc_{-÷O<£ÐžçMùŽ‡üÅQy+`“]SÎÍæ>æ|'¡(›þôlØ +endobj +612 0 obj 1594 endobj -545 0 obj<</Type/Page/Parent 409 0 R/Contents 546 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F2 5 0 R/F4 7 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 216 0 R>>endobj -546 0 obj<</Length 547 0 R/Filter/FlateDecode>>stream -xV]oã6|÷¯XäÉ8´åø+A.Erg÷rHsil\PôŠ‚–(›WJTE*®_úÛ;KɉíàÞŠ †l’³³³³KýÝŠ¨‡¿ˆÆ}:Qœµnî윢-R¬Œ&xH¨'z½-âö¹ˆÄ™ ëR‘_+|Ê|K–I;W)G›µÊé˼ۧom^|V¥Ó6ÿöŽ°ƒ*§’Žä»Å÷VN£‘˜ @;6Zåþ'þµ;PÕáOûc^}bÌ(±$é~º ¯·Ó'²%ã1:™iÃdz(uî‰>@zTÎVe¬è¦´§Ê“å–æ2[JÂW&Gnm7T‚ƒO-Î5$L?=þÜŠ†gbL£þHô(ƒN}p®¿š³bÐ)}Õi±F²±Ì‰–ŠRý²^nÁ½>^SZÚŒ‚‡±Êµií}qÑíƲ´FltîDõ,Enºÿ¥ªM×1ù.0ÅÚgæ%pgA´€,u¸6†yè<6U¢’pÚŸ‰>««s3Ò£†M±È¦µF‚n=Iã,…$P7ŠmU@jì¨Ë^”viTæ:ä*¤†Ú¥biu¾"cñ£Få2kÌqÝ.¿«ØfJJ¹ZAª —õÉ–F¢~óµBäm(÷~EP².
'ç(Î`2F©úøhzìéápôÆÓAŸàøë–VÊ#¸‚$¥†&ø}“+Ú€'F)Ì\^;×ýȺ3]:ß¡¸Tò¹5'Kcçï·÷‹_ÿ@VÒsƒp“œb{"¡+êøÁ[6¯aÄšºº±çÞ<`©Ë"ŠéõŸ¡Ž²Êyr¾ñƒS…,A¥³¡½‚Qrf,ô®·l©W:—þqÄk¬Nè¶Üz8aõfù¿vŒÙôØTs[çUZS -Úˆv¡× ‹1˜lͶ’—˜{[¯è=]î‰b_‰ËD=k4£]uH‰•¸ úô@wü}0¼ÃÉ»ëùôñót!WŽBþ†ùÌo-ŸŒf¼æ9Q“€ódQ@§ lÎ꼩~Lhs³m”Ým‚aö’yu^q/‡NSö‹ô0XáÙ/ÝËûk #UƒñIƾ‚¿·‡˜*¦Û²Îï5=…c>&¾^ṓ¹5ä³Ô¦éã/µsœ‚?GpC¶CWW@åAL¤ _!NgèñM’$<†BÄ×¾ÌGVëP*å)¶YkŒf`¿@åow®ÞS®ž«ÝÙ¤é’h4MιSç׿Ü\㮵<¼é£«÷·ô¸é÷:o>÷ñÖüo
´÷ž00êþ`ÈAqüÚúÛ™¹Èendstream -endobj -547 0 obj -1109 -endobj -548 0 obj<</Type/Page/Parent 409 0 R/Contents 549 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 262 0 R>>endobj -549 0 obj<</Length 550 0 R/Filter/FlateDecode>>stream +613 0 obj<</Type/Page/Parent 450 0 R/Contents 614 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F2 5 0 R/F4 7 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 225 0 R>>endobj +614 0 obj<</Length 615 0 R/Filter/FlateDecode>>stream +xV]oÛ6}÷¯¸È“8ôGü‘i†´uÖYšÅBƒaZ¢,v”¨ŠT<¿ì·ï\JNlg}‚²EÞ{î¹ç\ò{gHü
i6¢“)Åyç]Ôé_ŸÑpLQŠ7ÓS<$4ƒÁ€¢¸{&†âDÐU¥Èg +Ÿ²ØåGÒÎÕÊÑ:S}^ôGôµË/ŸTå´-¾¾!¬ Ú©„¤#ù&úÖÐñp*N‘ +ÿÿÚ¿Ópؤ?Íøí#ÇÜØšK’îæ}¹™?’8¡£kmLB÷•.<Ñû”³u+zWÙµSÕQ +K™/%á+ƒ#—Ù5Õ¥àäó¨Ãµ†‚iÈO?w†“1£éh*”ƒ§07ß-˜1ð€¾ðe(6–ÑRQªÿFÕË
°—ÒÇ¥•Í)0°Ÿ«ZQ—2ïËó~?–•5b'ê') +ÓÿÇ(U¯ûŽÁ÷Sd>7ûQvŽ"ˆ"ÐÒ¤[kc‡.bS'* {Àý‰1»º +endobj +615 0 obj +1116 +endobj +616 0 obj<</Type/Page/Parent 450 0 R/Contents 617 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 232 0 R>>endobj +617 0 obj<</Length 618 0 R/Filter/FlateDecode>>stream +xWQoÛ6~ϯ8ä¥)ÐÈ–ìÄIž¶uK[ h·Æm0 /4EÙ¬%R#)kþ÷ûŽ’lÅéТhmYGÞÝwßwwýç,¥)þ¤´ÈhvM²:ûmy6¹¿¥lJËo®7´ÌišL§øE^¼Þˆ:(Gé4¡·—éW)•÷ô ª• o'I›«—ËogSºÌæ8±Ó‚^yàßøö?òí—³4Éø=®Kzg‚³y#ƒ¶¦3Sšö¦Ù‚
;7ÚS®vª´µÊI†ðÕ2;í¬1•2!!ú½·qž¯8 +Aè²!l +ëú× WDi¤Îƒ¦NÄ|!‰wµ[±Vþ¡ä²lr&@ö9¿7¬Ïé›ãªY'„@‚ÀßÐZ„]´bïÙÃ^O!‚W^ÉD¤}¬ÐÑ÷Æú0¢Ígó£=~mȺǺïZýÒÛ& +£SÅ3¤øüý…¨;|ê èññ‘VζȆ`n–%ÙÑ]% à/ãq’6¹Þé¼%“çŽÂJÕ¡ŽâÇ¥µ[fug²ÓÜBˆà;V›-»¶ +>üQi^Qm5† +TªšÀÔÂE'iùò‰-ñ¨Ç™Áa$F”Іà¹V8[Q?³Ÿâ<440!n{¨õšÇOϵ(·~Tœ·1Žµ°Üã`ª}éÃ’©EUëî6ï±}0s +;1øf…FšXÇÓâI•É@ýÌ&#ªh‚•úr +endobj +618 0 obj +1480 +endobj +619 0 obj<</Type/Page/Parent 450 0 R/Contents 620 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F1 4 0 R/F2 5 0 R/F4 7 0 R/F5 8 0 R/F8 10 0 R>>>>>>endobj +620 0 obj<</Length 621 0 R/Filter/FlateDecode>>stream +xTMsÚ0½ó+Þääì؆@Ê©äkré$-žæ’™ŒeìÔ–ˆ$Ãðï»’€í¡ÃKë·û>ÖŸƒ)ý2LrÇàÝà¶\=Že(*w4¾™ (‘&iš¢àÑk-$f~lUJi0¬˜1¥KØíJà²ø ”l‡ñµ '{Ü(ñ%)â|œŒ?úÑKØZ€«®c²ô×1
A=Ëhʯ¯wˆtqx“À—˜®ŒÐk¡§ôüÕ°nÁ¥—Ó+zÔJY†?=$>¡¨ƒMÓ¶àZ0+ˆUÙhÁÒ[pÖ¶¢„%-kd#—~f´TmìîÒ¨^sG¤x‹šD$¾èéavïzSÃl˜äŽ–eË%a:Í$¯ß.ø)À{…´-5VôϬ”,
¬òPÃ$E)Ö¢U«ŽŠ`µ &ü˜ÎÝÏùV(ÒVÃÍ@L$já(PûŽÙS êä{ãb}*WçM)ª@ž(@²ŽÚc†¶!TuÆ2P;Tšý +¸U~IÆ.ÐN~UºÝ¡Œ_BxnöK;Ì’ù$
Å^¼hõA+†{Å{ff›àlœ'TOrÿ ¸«ÙÊ’YšàéùµxÆŒsaænÕq¼të†Âïš&£ä&|C®Çîà¡|üŒÍ€¡endstream +endobj +621 0 obj +642 +endobj +622 0 obj<</Type/Page/Parent 450 0 R/Contents 623 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 278 0 R>>endobj +623 0 obj<</Length 624 0 R/Filter/FlateDecode>>stream xÍœ]oDZ†ïõ+æ"Àq€x½³³3»{n}؉ Œe'Ö1¬@d<Ûî×Çmò¸àüñLöïÓê^?´ÒÛ¼?tÁLŸlÇúä¡ö#$ã1!1+Â,øƒéÛéR$d8§È@"˜ÄXÉ£VŒ0ÖeÃR\Á1¶blw7‡ãi½§«hÅ©úø@€7CŹEÄ–Á£PûG¯Ìœ7õ«aѼ)]oêW3½7ͽ7e½ZÞéÕ›jBåM™ ¦wcÆ:tÞ›²¾MÀðü¸YŸÊPC:˜ãsï)1[HF/ùŸ«IÆFÆíîÝãH…ܧ]U+‡ýÕöýÝq}ÚÆÁõ u¸¸«Q.iWÛëÍD}sñЃߌó§^rvD½ G\Æ Ö74urV'7úÚ MŸ<†õFô\ÐÔ-::Ïrz¹KyI#î׉û1!C=âÓánœ¹°ˆa.ýÀ!ŒêÉoF÷# Ë‘ÌC¬€‡ˆ»ŒIö>Ÿsõ°ñËöô!#XÄ|k`z@sÂâf}܉?a 0{ÈêvX•¤¿×rÚÅ´Jõ‡à¶¦ONÆú䶡v\#$?cBbV„>¸®éÛ™Æ=$d8;'ÎÍH ÇÁ$]€9†®@?I%¼‚
=#¨ˆŸeÞA2ñà&?’ @@ -1250,158 +1487,157 @@ qvq¸—’I“`–Œ†e‚ÝÕxùBåïáëÒ7l³LcÃê5lO³–ýÛd´m‡”lÎi×@xþáà”ThYÖ32ÖW„ B<¥&ólÿhÕ5–œ,µ¸^§ñ¥1c‰¶$ÍÈ»!Ÿ5¤ÕÅIfȪ>•)3É:r
‡HîQ!ö‡ý·›”ËlJNDz˜UOxzšˆÏvcÉUZ&•ú³k;åÞ([úcz‘.Š!g8ñ“Š²Î£Ñ3ë’ˆ:½ÝŽ„óò¶ià8&0x‚Ý‹Ôæ*NR€°ÿ;ó ÌŽ$9ß+QñA÷ËÈöÙŸ‚U4_°1o¦d,õÄT¦¬x¤f7}jAÖ§Û¡²Š¬å˜˜ásVÉ …,[»G1vEz~ØáE7=pŠô5Óº·HfØ~tAÆâ;èO>Éz¼¨ ¿T˜é“1*¦à¼J:x7²D¼oÌ»ëq7¾6É0gDGcB.n~Ä:éeC¬G.)´J" tcÝWÄ DÄíݼ›4Žž¤”0+뺞c"'ÍÆ‘Œë-,–YŸ,Í:T.QÕPüåVKÚ|øY2D™X«é¼‡W?ä,×o¯~d–®U8–®~ÔJ¥Õí¬.3:«Xöd½]UâÏwPtâÉÚÖŠ4Jº_QÆ):KÄåu{÷V "¼Ú^·‡«âA¤Mù<ˆ«bðŠôGÛww§2èKö–Õ`áÔ_¨•¨X?Ðë%,dåRW!+PAÎ>Ýž6ãánƒ%¸3?—¨0§ãfÜŸd ØGÄqÄ tøD8²*8ŒQ+„†“1¥ùô¨Ö³•¶+IŽ^Œ}ˆÖPf8èâÓž|¤`m¤´û”¸¹È&_/ÓJJîäû–Ü}6¿øìÐRØAÕ³ê8za‡59zíiŸ0=›!JLд¾fèY,Ž}™ÇØ]úlKÜ£Íçr$Ëù™»j¸L£#•oq´ËßÅ™¤¡Ø‘Œí”uK¤ÍjœYZØEöÂtÛ«ãæ*ÉFõ® -vßCÎÂL2‰Å$\üÂ3Êš- G@iƒÜˆà3R!N!G†ðYøÓ5[¼ûhóçÖm°·:š.F?¢€Ô"iöuÇÑ7Ÿ\fRZÔu(
X5â¿|Q74V»ÆÈ-KfCÞJïÒw^.±žÐ<¦O{-š§B<çŽ%,ð_°Cã ‹ŒÁZ:Ôœ{ª>XKãïÑhœDè8<‰¾Ã»!úz9ïÿ’Rb‰,I9NFGÐßoäÄÇïþ¡c½lù|í11´mgGÄd lõ¢„2Óñ«ÎÒ¶ÅõRÛA;:‚ÝŽŒ0í#4¬,j8ŠÝ”G¼v,k$Nûðãdrä\Æ9«ÀÀáàP•\ 2¾ÿ5¼¨CRlFD°s•±¤žÊÃGøR›w Ó0‡WÆÆ5ëV/Èfµ/”‰S2¶éeŸ -¬ W9†ˆ>êI*¸F.ä÷Ža"/'\~#,+ÁÁ{„jÌAü"Rʉ– -Ô×!Æ¥¢‚A`¼‡ÆˆtÛ#ÒÔ`ŒlE„QgÂä$T‰tÛÞ¬/~Îß|èo‘õ¼Ý°@6æRús±›~”Ä/`/ÝgR&ÇÒÞ”ÉÕp€ÂYQ ÅqtÞËÓÝxÂ0÷€±Ñ‹K”ÓÒ¥†z—þ«|¢±˜Â[B÷Ý-5П‹%p”É»Ž³Óš\[Žåj‰ --ajÛu”Ãö×/þ}û"°ûŽi¥Én\»Ié• -ͼdôKf^¥¡ë§d¬IÛ7¤õ'ý&42{ý&´¤m⺌îßœÉG„¼¦ôO| -endobj -550 0 obj -4978 -endobj -551 0 obj<</Type/Page/Parent 409 0 R/Contents 552 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 306 0 R>>endobj -552 0 obj<</Length 553 0 R/Filter/FlateDecode>>stream -xÍœ[7…ßý+úi‘ -¡VI)9eRŽÂ¿öý®ß]&Ÿ øT;ê,%ÞP–ÅHBšë¡ÐâÙYª‹Ä¡Âpd‘:@<´~IBqªÚ[DÉÌ»þt•ëB2xU=‘Pmê Æ7YJ3“ˆÁ-0 PŠŸÀ7§wí›Ö#»…ê‘ñB=ct·jý°±~˜ôès”X -nâ¦C‚±©Ä§xzÃÐû¾ËÝyn7‰ÕpdƒHTÏxÝïÎ÷CJpfò –£<hœ!$'’ ’…h‰¦ZíOð ÂS»˜ºy[¦qñ‚Ü`îƒQëœ@Õ3‰nF‚Qçô¯¯òÐFŠm5_Hã–~¹Þ¶_ßçF#¸Ï}ÖÈõ¾•Ÿ® -€5 ´81W °ˆ7ëMX&.8/6åZÈ銂)‰€X„®cZÀ"üD…24J³5Q²Åä‰+ š#°úãúðÓúðÏ0Ï[À‚wé½MK³¼®“ˆ¡³¼x¡ŽÃ³¼.ØŽ£ØM³¼Ä -³<à -³¼!dZú€Lã’~š?T,Âx[þΕøfÿ.Å
Ò¤^À -xŽé°¸ª{ TÀcd-Øo6ëƒô¬@›ÛwÒf¢=/“
’æ
á"w=šÉv¬ëÛOýL¶SRy†KFÅÑc€ør¹úñò°¿ÞK`…xš¢ÿ¾™°T.Ó«p¡f’éU[ã&ÇÌ:JT ƒ€êkÌÑ‹3@¤NMs}£C6s±3£R_ÓU
¤c:Í£‘úy‚
¤’À0—8eê¡<Åö¢SÂ=ЙFÉãz8ð
UMgzK=£éU¸ 7¨çÎ üôJÕ¼a0VGpú‡5ò`´Ô+2X))˜‹!Šµ•xº\]õ»Òü$“æŒ!‰k)g‡ëã)SV¡ÝÆ’P3I,ãþj…®~*Q„ÕÃ$›«’ÈCkÖHT?1AüÁêÝú™U`À†Îª©€¥<Øô’SM&aŒ˜mMl)UúYBÓ!Ïf©€%PÏf
è‚èÈlÏTÀbŸ'Ç4ñ¶¸™šÞñpžÇ’pA½³XûÍSŸ)îTëcÿì·Û’'&\ã,È:Ý -¶t|›”UI`ìmÕU¤)@ï[ÄÓe¿¡ .Ë -XÊ“þw·‘¸íÆZãw»jÍnÑ“î</ŠdV$Šý¼hfI/ ™qe -nÊÃ&VÈÃVÈÃ!äô’hMzlahÓº(Q&U\‰ïvýÅ:ï'‘LBI¢÷=äÉþr¿ËÃë@Á°„ù#SRÁÆ»õz—–•ðÔ`?ËQ´çøNCJp+q¦IhÏ¡NC" :Ùî5UIT ±U±ã¡Ç°YRÏøîÙãÿ$›H¯J28;–Ìζ©€‡\iÈ`t™0îpUROeß`çPºMȳß~nMµE®*'ãEî:”Gm±Hµ£Ò86Ú'R˜ƒRöCÂý7ÇÓa¹:…gé0˜ÜþY~·ïF³Ô\F1]Z¶áB-…Tj;·K¬œuT-Yf).¬dªå%a~~½’eb ?Y–Ù™f&Ë«dšpA¦™5n¢0¹c«ú° ŠÆ6Â`•–5ÎîÔ•A(ÔWB;RêÖ,”)ëbƒI<æŸús]0Oo?ÝèyñG×"Ý 3â6\P‹`„öî -³e‡
sÞ(Â:E<Õô¶gœ-´Ð#̉“…,º0Q°Õøîíˆ ñŸ&´&‘ÞN$Á•<=\]±‚¶c;æ -ª>,ˆ0ãéïÒJ>.U@Î.ÁC¹Êôu8z¢e0¢y“ÈÎþðcÌñÉ9‡?0V»ieÿ-yz¸ ie~γ-iïéJÐÐ̈èêÈÓ~uØ÷eu£z¡Ñ6Jl_—ëíþTv9Hˆ¶Y´˜äXŒð¡ÕúœwÒI+3·a…´€'=Xn6±•?QtYËâ!µf¸ Ö”sãtd[Ú²³±T'!¬·áÙr›OØkD,Äûð -GOúUf°L:—,™Dx -N®®>v)ôƒÅÍ’Ö슴c™“¥¦Ô8öfWÿÒeXÖVBã†0&#ô¾‡¼Ø\_^† -xÆ×8gQòओî%‹@ó$ ì)æy‰€ÀÓÖ!´€GÜßlöÑ™Ä5±éçe©“¶f“« #½öÌxA¾€<ÖpR¶¹bc+ïeL*Cˆ·Œ—ëãõ&w$“Æ”ä«Äûȃ°§)öÞí:‡PÛ:»Né,r.È®Shv6*V
“»(E°U÷f€Þ÷ˆÇ»ã ®Q¤çjËJxãîF*0Ð{ÑQ¸> ëéôN¨‘4BŸ¸¡\›`O)¯º›pAmÒyOwÛQ -"§4Œ<¶ˆ<Á&Ç)<{˜á Ú'9M=ýW?:Ó ”WÝM¸ Óà]?@S¦RRQ"Æ‘5DãðŽÕy¬˜’øÓY'íË’¦ÁËq9%/Ô8œ–×!¬Ý”N¬À5¬BæeÑ')á¤Çj“¡bZ%úJp¾‘Dh*$ÑÑTŒÐûñb}ØöGiª<ò‘$ä -“°pÖÁVd.POxýؼ0Á:P°0r5A(”Q& +vßCÎÂL2‰Å$\üÂ3Êš- G@iƒÜˆà3R!N!G†ðYøÓ5[¼ûhóçÖm°·:š.F?¢€Ô"iöuÇÑ7Ÿ\fRZÔu(
X5â¿|Q74V»ÆÈ-KfCÞJïÒw^.±žÐ<¦O{-š§B<çŽ%,ð_°Cã ‹ŒÁZ:Ôœ{ª>XKãïÑhœDè8<‰¾Ã»!úz9ïÿ’Rb‰,I9NFGÐßoäÄÇïþ¡c½lù|í1±u;ëmgGÄd Le ”™Ž_u–¶-®—ÚÎzØÑìvd„ié¤aeQÃQì~¤¼8âí°cYë$!0p +ØGkf“É‘suçH¬‡ƒCUrÈøþ×ð¢I°qÁÎUÆ +D`x*Ká3HmÞNÃ^׬[½ o˜Õ¾P&NÉئ—}ô3Ø}ˆc-É` +¬ W9†ˆ>êI*¸F.ä÷Ža"/'\~#,+ÁÁ{„jÌAü"Rʉ– +øï˜ÓéÏÅ}kÕöµ‰Óì†ÕׂþþISF Ôo’ 2Vƒú:ĸTT0l÷Бn{DšŒ‘ˆ0êàL˜|„*‘n{›õÅÏùû‘ý-"²ž·ÈÆ\J.vÓ’øì¥ûLÊäX›`‚2¹®P8+ +´8ŽÎ{yºOæ06zÑ‚c‰rZºÔÁ°‘BïÒ•O4SxKè¾»¥ús±Ž2yב`rZ“k˱\-Q¢%Lm»ŽrxÀþzâÅ¿o_vß‘#t"yÃëa·#)½R¡™—ì~ÉÌ«4ôoý4ÓSX“¶oHëOúMhdöúMhIÛÄuÝ¿9“7xMéŸø +endobj +624 0 obj +4982 +endobj +625 0 obj<</Type/Page/Parent 450 0 R/Contents 626 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 322 0 R>>endobj +626 0 obj<</Length 627 0 R/Filter/FlateDecode>>stream +xÍœ[Ç…ßõ+yœ‡Ðœ/‚@–lG%+Ò:Î[@q¹»có¢\Ëþ÷9Õ]Ý}ªf}‘œ]ÛŒNŸ=ÕÕÕÕ—áÕÕÿêjÞTí¬Zï}rñèãÏ–U3.®ªº_Nêj6懲Ëj:™Nñéú£‹Õ›í¦:\UOûóf>ýéâ›GŸ^<’¡TUË_¯>ÔÎ&ÓjÖ-ñÿ]Õ÷“F/¶Õkù"'8^WÖUu-_ÚÌz|}o7é&•~ÁvU=mò÷(:Þw€çÃõquûDa!0u;im
Q`Tó!ËI +xÂåa·J"!00‡XP으Yx!HÄb.~d½|à¶CJœyê[%a=%ùb^xϾXœ¼iÔ+c´œ.ER´Ù-96ÖSc¿ì'uqªj•´”’3&Åà8"üã0ì‡ýuò Ò‰Oµ“ÞRâýeU¼4 4¡¸ +!^\¤:°H*G©#ÄSë—$§ª½E”<¼Î7¹.$ƒWÕ„jS—X`1¾É:‰“sñM¦h‘2ÄÉúâ¤ñÈ~)ƒzd¼PÄÝ/¥ƒZ?l¬&=:åå–‚›¸é˜`ìE*ñžÞ0ô¾¯Åj™ÛDâC5Ù Õ3¾ö—‡w§Ì!%8syËÑžƒ +xÊãõýLãe‘Ô„É?Ub{ÍÆXÆLB”© +àOpk¬ÖtöM<çÉvëdVbÀDôµQ´çT%µbM/ƒ.[%ðêç¬]ÝÚ0뱟êÈô¾¡¸™sŸé° #©2¼¬¯âEé3]ȶìX‚(GÁQ1Ïê,BïK¢Çç«ýíj»Íy+Áé$y7UI<híúKZŒAÊö 뤔¾#áÓVHxΙ{ ë@AæáÌ“ +xÊJ{`h`¤E÷?+`>!™[lµpA®0—ÖåV”ðY‰+ÈXÑ1Bï{ˆ ¬WÀWXN*àA¾I Îl&ÞÍõIhÏ1-È:ñƒ9bKQ°§¤Ì‡¤ +xÊÍfû6Eqñ¡$‹¾®ôaRYÓŠ.ü!©ÀèCp1Ñžñ,ׂ4 ÌdqÜ>Šð„ëM6)«À˜ËÚ‡e(Ö3ÂbîÃ{#ü±6DÓ…¬5zO¸ D̳ çl²pþ¨ú¥ÌN;Ö+Ñì̘d°Ö¶áÔÑû¢3ãÜ$¦“Hm0‰ì9W‡âפ!
cW%a=Ãos‘RÙµµ-à9Ëï?~þiHTåHѽ䀤Eþ”°FSòÕpAN–`íà‚} ì1U‚ŒÐûz’Ö{ì¢8F$Ø¢—4‘aaŒUèÙþ„ls-G“NÉNAjiY̲,-àköbs~w8~›8¬sKÇA€=å‹Ã5jÚSBõ=´hkV‹[,!I¦Ì/J¶HÄì°(ÙÍ9!¶¡A(ÔC~¢
3,ÙÀ¤
Çú‰6L¬&r²,Åûš½Æþ!-'±mØJ°2œTÀsnóÅ" °ÍÜ;„R=âÕaµãªR–LÄlU´€ç|…MÀä“,¤•$ß@P +Xʳ’z!òúf‰g³ê°ö.AÁü}´K™MèS˜’çë6\¨_ñεTËÖà®ë(Ç,Zö™
+ì\!”´ 6žeYÈè•è+ñÕ~¸Úä8$“$IRLÑûG Ô¬³î™¥¤ƒ£ï6›}æÆ=S›„ößUH ¶ÎÜS%´çPg!½¤Z¦*‰ê4«dUìpè+ì-©€g|õâÙ¿“M¤?%\Ëàζ©€‡Üžhd`t9Eiª’ x -Þc•ì†È©[ÅzFé‡,×A’&ðˆÊ¿~ÂZ°cŒXiH -÷¤ó~¹Ù_Æ3O’ûàÕí<ÒÄy®/RïÂmìpŒmÛa’:LÍ:t¯÷‰Á$dzYðѼ¿ @ûõå' bG›[¹Þ·òŸÐYóÀ‚~–4 „´—©¿ô3)`rÌ,#H:Õ€‰jÞX(UÖp¶&J¶#I -t)lF,œ^X½9¥Î* r^Ú<D*`Ç«åa-3öæ.gìÎágtp¶äð8Üe«ˆ”šsyÕ‡XnôÑ儛ƈ¨CkaØmq¤Lª¤µP®¯‡ñ<R^å5Œ„õý»Ýúp¼ê߆t€Ž¿:Ç¿ýM×&8@OÀÊ{ùõxlSÆ}-Ρb>éÚDõÑv¬mvƘpc›(DÇåús§7´Ibà¬z!3ÖCö9_U“ÍŠµ;‚¢Ah8ïëÕi_^bti™Y’Â=‰Æíà"ÓîÞE&æ`\è!« Õ‰ÔA'þ¥8C™Æ‘oÊ\Ôô¶g<¢°N"4BHÞ„Þ÷ˆ²v C2GÜbH¾}ÿù …³kKÇ@ëpAv
/$p»–Ñ>N ò‚/˽/^χÏ$©ø¸˜É€Û“†öýÃŽs:³bì*¨pAfm¬=𞺋\ª–|†L–ÇÐå -—ðKú¸` - -ƒJt_óƒ$CCbà -Ÿ‹ïbÚcwèpæÕ†/GßbupÜþ½~›8Áÿ˜£d_‘¡Ó&Bp/C€Ë*2ðØ$Neäè+p³»*%:•¡D®§Üà« ÚVŒP¨Gp oŠH¼Tæ÷†o{Âòt:ôo®ÉÛ‹~ŠuðÂbâm©¶Ë·o10…y£üZÖoœ7NZ!ÅÑ«¦ñÀgH1†ÏꤜÇ2ÙŽ7¥ÅrØŠdOXo—œ¸Š‘£™ÇÏZ‹Hóâ篚Ôõ‹1]¿©'¤òx×Ëã[¯‰@* 0ÄY„ÞöŒož¿>{D~âç76ÈM9ßShbÎï"8äSøœ[ã}úÃΆüÎUi™*'%ñû7þdª?ºÿm8šþ)Ö3ï1¯üÙÚΘ±„Ïj,†'þ(§Ø¥X&LÃUŽÄžœò.ãK¼é”“+ -qÓð¶ Éã]/ç·õŠzŸÇkI¤W¢”WõŠB\\Ò’Fo{ùjð{,E Ì\~CÑ`:„÷篾È}•$¢8#‡Wtø)"Ñ^/ùĉdÎ^ƒ$‚Þöl®ì°ŠOžt€ €WA±Ræä$¯E[kêm¯¯Ø¤’q@öôMæx›ÁØ$‘ùŽ,+X¯·=a’,@ -ȱ·
©·½¼ü’
I G]^¾(½Aoôùë‹rLùìÓ+ÐËWá· -2£ÈÀ˜ËIkS…xÛ3.J+’o -aIeQo{@˜V„—OÈÿ¾¸oƒ¦^嬖|.A±a0v¹•‡ >«<ÀUÇÁòÈóß?:Ibë•è.è$yF^þž “0!D‚ÎÀÜÕbÐQ}F‰¾ÜÙH„þŽë°ÝG¨·=¡MžJ -ȱ뎣,@/ÿþ³Ý¾D¬¢’ˆ#¿0cñ¶GhØûþó¿æª):
ÀU%Þö¹HÎzaOžFo{6Nr%H2’ØfdBd Ù ¤ -endobj -553 0 obj -5199 -endobj -554 0 obj<</Type/Page/Parent 409 0 R/Contents 555 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 309 0 R>>endobj -555 0 obj<</Length 556 0 R/Filter/FlateDecode>>stream -x–M““@†ïüŠ>f;aøædeÕU–ḗ˜,k`Sþ{»™šÆ*ÝTm%á}ŸéžámòÓÓàãKC@˜À¾ö -oý˜CàCqçJC’FPÀW¾ßîWÅîÛ¹s„צ¹”Í¥»+^¼·…G‚^šÞ}}ç…‰ò!‰rü_CªØ}8Ö†öëÇ´¦¥±š$ÆåغX‹ -¸Õ®†,Péœm/¦-;sÔ ýTÖf¯ÿ幜܄ˆ ¡ê{uí9`ìšßC
܃„XË"œ@•12˜™¿`X`T]w-»Âl5ž}ºhÅ -äö\6‚›*šï†Ä§í:Ì„ˆ8’gê¨ñ´b[Ê]ÈÈ÷œÆ¯²í*Ó<ݵ0g
¡Ÿ,Ú±ÁjÜSîAB«p¾!N ×®<Ep""°TØM502• €HÀX -G;2“)YLóaFq`É9´Fk,†iFô÷ó㌹5g³ƒÁJ}y¾ƒ@‚n¦ý^5§¡ îDNFªY_ƒ@ràhÆ®¸
C¢# -:ï -Ùb>ù¸‰rš*r°ûuÈ:lÒº>jýôüߨ±0ÚÔMÏâþ]ÿ,Îܳø^§9Îâ,Ä,c’·›øÜš—r7f1î»PÊo¨<Žû”~BVUU¹Pñþ -endobj -556 0 obj -661 -endobj -557 0 obj<</Count 10/First 558 0 R/Last 643 0 R>>endobj -558 0 obj<</Parent 557 0 R/Title(Table of Contents)/Dest[548 0 R/XYZ null 756 null]/Next 559 0 R>>endobj -559 0 obj<</Parent 557 0 R/Count -19/First 560 0 R/Last 578 0 R/Title(Chapter 1. How to Install and Test SAMBA)/Dest[413 0 R/XYZ null 750 null]/Prev 558 0 R/Next 579 0 R>>endobj -560 0 obj<</Parent 559 0 R/Title(1.1. Step 0: Read the man pages)/Dest[413 0 R/XYZ null 726 null]/Next 561 0 R>>endobj -561 0 obj<</Parent 559 0 R/Title(1.2. Step 1: Building the Binaries)/Dest[413 0 R/XYZ null 589 null]/Prev 560 0 R/Next 562 0 R>>endobj -562 0 obj<</Parent 559 0 R/Title(1.3. Step 2: The all important step)/Dest[413 0 R/XYZ null 174 null]/Prev 561 0 R/Next 563 0 R>>endobj -563 0 obj<</Parent 559 0 R/Title(1.4. Step 3: Create the smb configuration file.)/Dest[416 0 R/XYZ null 735 null]/Prev 562 0 R/Next 564 0 R>>endobj -564 0 obj<</Parent 559 0 R/Title(1.5. Step 4: Test your config file with testparm)/Dest[416 0 R/XYZ null 375 null]/Prev 563 0 R/Next 565 0 R>>endobj -565 0 obj<</Parent 559 0 R/Title(1.6. Step 5: Starting the smbd and nmbd)/Dest[416 0 R/XYZ null 264 null]/Prev 564 0 R/Next 566 0 R>>endobj -566 0 obj<</Parent 559 0 R/Title(1.6.1. Step 5a: Starting from inetd.conf)/Dest[419 0 R/XYZ null 750 null]/Prev 565 0 R/Next 567 0 R>>endobj -567 0 obj<</Parent 559 0 R/Title(1.6.2. Step 5b. Alternative: starting it as a daemon)/Dest[419 0 R/XYZ null 262 null]/Prev 566 0 R/Next 568 0 R>>endobj -568 0 obj<</Parent 559 0 R/Title(1.7. Step 6: Try listing the shares available on your server)/Dest[422 0 R/XYZ null 682 null]/Prev 567 0 R/Next 569 0 R>>endobj -569 0 obj<</Parent 559 0 R/Title(1.8. Step 7: Try connecting with the unix client)/Dest[422 0 R/XYZ null 505 null]/Prev 568 0 R/Next 570 0 R>>endobj -570 0 obj<</Parent 559 0 R/Title(1.9. Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client)/Dest[422 0 R/XYZ null 328 null]/Prev 569 0 R/Next 571 0 R>>endobj -571 0 obj<</Parent 559 0 R/Title(1.10. What If Things Don't Work?)/Dest[425 0 R/XYZ null 750 null]/Prev 570 0 R/Next 572 0 R>>endobj -572 0 obj<</Parent 559 0 R/Title(1.10.1. Diagnosing Problems)/Dest[425 0 R/XYZ null 573 null]/Prev 571 0 R/Next 573 0 R>>endobj -573 0 obj<</Parent 559 0 R/Title(1.10.2. Scope IDs)/Dest[425 0 R/XYZ null 501 null]/Prev 572 0 R/Next 574 0 R>>endobj -574 0 obj<</Parent 559 0 R/Title(1.10.3. Choosing the Protocol Level)/Dest[425 0 R/XYZ null 390 null]/Prev 573 0 R/Next 575 0 R>>endobj -575 0 obj<</Parent 559 0 R/Title(1.10.4. Printing from UNIX to a Client PC)/Dest[428 0 R/XYZ null 735 null]/Prev 574 0 R/Next 576 0 R>>endobj -576 0 obj<</Parent 559 0 R/Title(1.10.5. Locking)/Dest[428 0 R/XYZ null 611 null]/Prev 575 0 R/Next 577 0 R>>endobj -577 0 obj<</Parent 559 0 R/Title(1.10.6. Mapping Usernames)/Dest[431 0 R/XYZ null 750 null]/Prev 576 0 R/Next 578 0 R>>endobj -578 0 obj<</Parent 559 0 R/Title(1.10.7. Other Character Sets)/Dest[431 0 R/XYZ null 679 null]/Prev 577 0 R>>endobj -579 0 obj<</Parent 557 0 R/Count -8/First 580 0 R/Last 587 0 R/Title(Chapter 2. LanMan and NT Password Encryption in Samba 2.x)/Dest[434 0 R/XYZ null 750 null]/Prev 559 0 R/Next 588 0 R>>endobj -580 0 obj<</Parent 579 0 R/Title(2.1. Introduction)/Dest[434 0 R/XYZ null 702 null]/Next 581 0 R>>endobj -581 0 obj<</Parent 579 0 R/Title(2.2. How does it work?)/Dest[434 0 R/XYZ null 565 null]/Prev 580 0 R/Next 582 0 R>>endobj -582 0 obj<</Parent 579 0 R/Title(2.3. Important Notes About Security)/Dest[437 0 R/XYZ null 695 null]/Prev 581 0 R/Next 583 0 R>>endobj -583 0 obj<</Parent 579 0 R/Title(2.3.1. Advantages of SMB Encryption)/Dest[437 0 R/XYZ null 216 null]/Prev 582 0 R/Next 584 0 R>>endobj -584 0 obj<</Parent 579 0 R/Title(2.3.2. Advantages of non-encrypted passwords)/Dest[440 0 R/XYZ null 750 null]/Prev 583 0 R/Next 585 0 R>>endobj -585 0 obj<</Parent 579 0 R/Title(2.4. The smbpasswd file)/Dest[440 0 R/XYZ null 652 null]/Prev 584 0 R/Next 586 0 R>>endobj -586 0 obj<</Parent 579 0 R/Title(2.5. The smbpasswd Command)/Dest[443 0 R/XYZ null 395 null]/Prev 585 0 R/Next 587 0 R>>endobj -587 0 obj<</Parent 579 0 R/Title(2.6. Setting up Samba to support LanManager Encryption)/Dest[446 0 R/XYZ null 471 null]/Prev 586 0 R>>endobj -588 0 obj<</Parent 557 0 R/Count -2/First 589 0 R/Last 590 0 R/Title(Chapter 3. Hosting a Microsoft Distributed File System tree on Samba)/Dest[449 0 R/XYZ null 750 null]/Prev 579 0 R/Next 591 0 R>>endobj -589 0 obj<</Parent 588 0 R/Title(3.1. Instructions)/Dest[449 0 R/XYZ null 702 null]/Next 590 0 R>>endobj -590 0 obj<</Parent 588 0 R/Title(3.1.1. Notes)/Dest[452 0 R/XYZ null 669 null]/Prev 589 0 R>>endobj -591 0 obj<</Parent 557 0 R/Count -13/First 592 0 R/Last 604 0 R/Title(Chapter 4. Printing Support in Samba 2.2.x)/Dest[455 0 R/XYZ null 750 null]/Prev 588 0 R/Next 605 0 R>>endobj -592 0 obj<</Parent 591 0 R/Title(4.1. Introduction)/Dest[455 0 R/XYZ null 726 null]/Next 593 0 R>>endobj -593 0 obj<</Parent 591 0 R/Title(4.2. Configuration)/Dest[455 0 R/XYZ null 470 null]/Prev 592 0 R/Next 594 0 R>>endobj -594 0 obj<</Parent 591 0 R/Title(4.2.1. Creating [print$])/Dest[455 0 R/XYZ null 240 null]/Prev 593 0 R/Next 595 0 R>>endobj -595 0 obj<</Parent 591 0 R/Title(4.2.2. Setting Drivers for Existing Printers)/Dest[461 0 R/XYZ null 750 null]/Prev 594 0 R/Next 596 0 R>>endobj -596 0 obj<</Parent 591 0 R/Title(4.2.3. Support a large number of printers)/Dest[461 0 R/XYZ null 441 null]/Prev 595 0 R/Next 597 0 R>>endobj -597 0 obj<</Parent 591 0 R/Title(4.2.4. Adding New Printers via the Windows NT APW)/Dest[464 0 R/XYZ null 723 null]/Prev 596 0 R/Next 598 0 R>>endobj -598 0 obj<</Parent 591 0 R/Title(4.2.5. Samba and Printer Ports)/Dest[464 0 R/XYZ null 440 null]/Prev 597 0 R/Next 599 0 R>>endobj -599 0 obj<</Parent 591 0 R/Title(4.3. The Imprints Toolset)/Dest[464 0 R/XYZ null 250 null]/Prev 598 0 R/Next 600 0 R>>endobj -600 0 obj<</Parent 591 0 R/Title(4.3.1. What is Imprints?)/Dest[467 0 R/XYZ null 750 null]/Prev 599 0 R/Next 601 0 R>>endobj -601 0 obj<</Parent 591 0 R/Title(4.3.2. Creating Printer Driver Packages)/Dest[467 0 R/XYZ null 626 null]/Prev 600 0 R/Next 602 0 R>>endobj -602 0 obj<</Parent 591 0 R/Title(4.3.3. The Imprints server)/Dest[467 0 R/XYZ null 528 null]/Prev 601 0 R/Next 603 0 R>>endobj -603 0 obj<</Parent 591 0 R/Title(4.3.4. The Installation Client)/Dest[467 0 R/XYZ null 417 null]/Prev 602 0 R/Next 604 0 R>>endobj -604 0 obj<</Parent 591 0 R/Title(4.4. Migration to from Samba 2.0.x to 2.2.x)/Dest[470 0 R/XYZ null 524 null]/Prev 603 0 R>>endobj -605 0 obj<</Parent 557 0 R/Count -3/First 606 0 R/Last 608 0 R/Title(Chapter 5. security = domain in Samba 2.x)/Dest[473 0 R/XYZ null 750 null]/Prev 591 0 R/Next 609 0 R>>endobj -606 0 obj<</Parent 605 0 R/Title(5.1. Joining an NT Domain with Samba 2.2)/Dest[473 0 R/XYZ null 726 null]/Next 607 0 R>>endobj -607 0 obj<</Parent 605 0 R/Title(5.2. Samba and Windows 2000 Domains)/Dest[476 0 R/XYZ null 352 null]/Prev 606 0 R/Next 608 0 R>>endobj -608 0 obj<</Parent 605 0 R/Title(5.3. Why is this better than security = server?)/Dest[479 0 R/XYZ null 750 null]/Prev 607 0 R>>endobj -609 0 obj<</Parent 557 0 R/Count -9/First 610 0 R/Last 618 0 R/Title(Chapter 6. How to Configure Samba 2.2.x as a Primary Domain Controller)/Dest[482 0 R/XYZ null 750 null]/Prev 605 0 R/Next 619 0 R>>endobj -610 0 obj<</Parent 609 0 R/Title(6.1. Background)/Dest[482 0 R/XYZ null 702 null]/Next 611 0 R>>endobj -611 0 obj<</Parent 609 0 R/Title(6.2. Configuring the Samba Domain Controller)/Dest[485 0 R/XYZ null 750 null]/Prev 610 0 R/Next 612 0 R>>endobj -612 0 obj<</Parent 609 0 R/Title(6.3. Creating Machine Trust Accounts and Joining Clients to the Domain)/Dest[488 0 R/XYZ null 643 null]/Prev 611 0 R/Next 613 0 R>>endobj -613 0 obj<</Parent 609 0 R/Title(6.4. Common Problems and Errors)/Dest[491 0 R/XYZ null 617 null]/Prev 612 0 R/Next 614 0 R>>endobj -614 0 obj<</Parent 609 0 R/Title(6.5. System Policies and Profiles)/Dest[494 0 R/XYZ null 563 null]/Prev 613 0 R/Next 615 0 R>>endobj -615 0 obj<</Parent 609 0 R/Title(6.6. What other help can I get ?)/Dest[497 0 R/XYZ null 524 null]/Prev 614 0 R/Next 616 0 R>>endobj -616 0 obj<</Parent 609 0 R/Title(6.6.1. URLs and similar)/Dest[500 0 R/XYZ null 233 null]/Prev 615 0 R/Next 617 0 R>>endobj -617 0 obj<</Parent 609 0 R/Title(6.6.2. Mailing Lists)/Dest[503 0 R/XYZ null 722 null]/Prev 616 0 R/Next 618 0 R>>endobj -618 0 obj<</Parent 609 0 R/Title(6.7. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba)/Dest[506 0 R/XYZ null 750 null]/Prev 617 0 R>>endobj -619 0 obj<</Parent 557 0 R/Count -13/First 620 0 R/Last 632 0 R/Title(Chapter 7. Unifed Logons between Windows NT and UNIX using Winbind)/Dest[512 0 R/XYZ null 750 null]/Prev 609 0 R/Next 633 0 R>>endobj -620 0 obj<</Parent 619 0 R/Title(7.1. Abstract)/Dest[512 0 R/XYZ null 702 null]/Next 621 0 R>>endobj -621 0 obj<</Parent 619 0 R/Title(7.2. Introduction)/Dest[512 0 R/XYZ null 565 null]/Prev 620 0 R/Next 622 0 R>>endobj -622 0 obj<</Parent 619 0 R/Title(7.3. What Winbind Provides)/Dest[512 0 R/XYZ null 242 null]/Prev 621 0 R/Next 623 0 R>>endobj -623 0 obj<</Parent 619 0 R/Title(7.3.1. Target Uses)/Dest[515 0 R/XYZ null 577 null]/Prev 622 0 R/Next 624 0 R>>endobj -624 0 obj<</Parent 619 0 R/Title(7.4. How Winbind Works)/Dest[515 0 R/XYZ null 413 null]/Prev 623 0 R/Next 625 0 R>>endobj -625 0 obj<</Parent 619 0 R/Title(7.4.1. Microsoft Remote Procedure Calls)/Dest[515 0 R/XYZ null 288 null]/Prev 624 0 R/Next 626 0 R>>endobj -626 0 obj<</Parent 619 0 R/Title(7.4.2. Name Service Switch)/Dest[518 0 R/XYZ null 750 null]/Prev 625 0 R/Next 627 0 R>>endobj -627 0 obj<</Parent 619 0 R/Title(7.4.3. Pluggable Authentication Modules)/Dest[518 0 R/XYZ null 322 null]/Prev 626 0 R/Next 628 0 R>>endobj -628 0 obj<</Parent 619 0 R/Title(7.4.4. User and Group ID Allocation)/Dest[521 0 R/XYZ null 682 null]/Prev 627 0 R/Next 629 0 R>>endobj -629 0 obj<</Parent 619 0 R/Title(7.4.5. Result Caching)/Dest[521 0 R/XYZ null 492 null]/Prev 628 0 R/Next 630 0 R>>endobj -630 0 obj<</Parent 619 0 R/Title(7.5. Installation and Configuration)/Dest[521 0 R/XYZ null 341 null]/Prev 629 0 R/Next 631 0 R>>endobj -631 0 obj<</Parent 619 0 R/Title(7.6. Limitations)/Dest[521 0 R/XYZ null 151 null]/Prev 630 0 R/Next 632 0 R>>endobj -632 0 obj<</Parent 619 0 R/Title(7.7. Conclusion)/Dest[524 0 R/XYZ null 577 null]/Prev 631 0 R>>endobj -633 0 obj<</Parent 557 0 R/Count -9/First 634 0 R/Last 642 0 R/Title(Chapter 8. UNIX Permission Bits and WIndows NT Access Control Lists)/Dest[527 0 R/XYZ null 750 null]/Prev 619 0 R/Next 643 0 R>>endobj -634 0 obj<</Parent 633 0 R/Title(8.1. Viewing and changing UNIX permissions using the NT security dialogs)/Dest[527 0 R/XYZ null 702 null]/Next 635 0 R>>endobj -635 0 obj<</Parent 633 0 R/Title(8.2. How to view file security on a Samba share)/Dest[527 0 R/XYZ null 521 null]/Prev 634 0 R/Next 636 0 R>>endobj -636 0 obj<</Parent 633 0 R/Title(8.3. Viewing file ownership)/Dest[527 0 R/XYZ null 344 null]/Prev 635 0 R/Next 637 0 R>>endobj -637 0 obj<</Parent 633 0 R/Title(8.4. Viewing file or directory permissions)/Dest[530 0 R/XYZ null 682 null]/Prev 636 0 R/Next 638 0 R>>endobj -638 0 obj<</Parent 633 0 R/Title(8.4.1. File Permissions)/Dest[530 0 R/XYZ null 439 null]/Prev 637 0 R/Next 639 0 R>>endobj -639 0 obj<</Parent 633 0 R/Title(8.4.2. Directory Permissions)/Dest[530 0 R/XYZ null 183 null]/Prev 638 0 R/Next 640 0 R>>endobj -640 0 obj<</Parent 633 0 R/Title(8.5. Modifying file or directory permissions)/Dest[533 0 R/XYZ null 669 null]/Prev 639 0 R/Next 641 0 R>>endobj -641 0 obj<</Parent 633 0 R/Title(8.6. Interaction with the standard Samba create mask parameters)/Dest[533 0 R/XYZ null 228 null]/Prev 640 0 R/Next 642 0 R>>endobj -642 0 obj<</Parent 633 0 R/Title(8.7. Interaction with the standard Samba file attribute mapping)/Dest[539 0 R/XYZ null 590 null]/Prev 641 0 R>>endobj -643 0 obj<</Parent 557 0 R/Count -5/First 644 0 R/Last 648 0 R/Title(Chapter 9. OS2 Client HOWTO)/Dest[542 0 R/XYZ null 750 null]/Prev 633 0 R>>endobj -644 0 obj<</Parent 643 0 R/Title(9.1. FAQs)/Dest[542 0 R/XYZ null 726 null]/Next 645 0 R>>endobj -645 0 obj<</Parent 643 0 R/Title(9.1.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?)/Dest[542 0 R/XYZ null 696 null]/Prev 644 0 R/Next 646 0 R>>endobj -646 0 obj<</Parent 643 0 R/Title(9.1.2. How can I configure OS/2 Warp 3 \(not Connect\), OS/2 1.2, 1.3 or 2.x for Samba?)/Dest[542 0 R/XYZ null 344 null]/Prev 645 0 R/Next 647 0 R>>endobj -647 0 obj<</Parent 643 0 R/Title(9.1.3. Are there any other issues when OS/2 \(any version\) is used as a client?)/Dest[545 0 R/XYZ null 750 null]/Prev 646 0 R/Next 648 0 R>>endobj -648 0 obj<</Parent 643 0 R/Title(9.1.4. How do I get printer driver download working for OS/2 clients?)/Dest[545 0 R/XYZ null 635 null]/Prev 647 0 R>>endobj -649 0 obj<</Type/Catalog/Pages 409 0 R/Names 310 0 R/PageLayout/SinglePage/Outlines 557 0 R/OpenAction[410 0 R/XYZ null null null]/PageMode/UseOutlines/PageLabels<</Nums[0<</P(title)>>1<</S/r>>4<</S/D>>]>>>>endobj +,ûgB®ña§C:sT©
©°.Å‹Üuhã¹ÅüÊætئqÑ]I8?‹Ø.Lp¿A&·ZŸÃ³ô÷“7ýÈ<ý—}ì,ÕÊn²T¸ÐçÃþq‹„À&]˜p;û¨^öE 4c â™4¸Œ¹®éw¶ƒì̃„¤á‚Ì#ïHÐë ó‰ÛAnUV%â…±Ó:’¾Æigô$þúˆô€ØR§f™LÙ[0-à(ȱ¾.u½iöþƒØ/sß/åZb*)͵NxÚe'i‹Ò•cö¯lèag‚ÞöŒ‹Õ‘ÖIHcbñy
C–ˆ£j åK¯’›ÝÃêç8.Ñ™™sƒÈ&YFÈUãE±kƒÕ›\`ü· éÃ1L£W¢'ð™6YÄN +Å#Òl/?ht‰mÁ¼ªÑ„jÍ™?å-ý«±±µ”RCÐÛžñbµËHHûcNÒbˆNàë}xãºÃ:SXLØ+4˜T`ÄÁûë›c×~Ò™…¦‹â2¨Gó…j’~ܽʰNØÇ aNè}‹x¹½½¾¯LŠ!𞤶Ó
&°œÇ·ØÆØŸ‡µ]q$yìèb\§Ä·°çÈÁÒ¦’dÁþ\+àrЛpA€×Äü€ŽYcz¢•€Ù#">âíƒ H„&À@>·ˆ®G +¿8:¦AÜP®M°`žgÜòjjž0cÆÝàÍ]?ãvç ¢6Àd^Ê€Ø&#ÄÃn8‡ y÷ÿ¶'Ø]H°æ‘¦Í3îxQ\¶^øAÖ)åHRKðÅBO`©<Çàë-Ö°ûo–IÇ3eJ#g¿órp¼Ð'ãåà8ËçU‰»–ƒ+,ÞVXChÏ\–ƒ“¯ŸÍõ"Y9ÞöÇy‘Dkåx™©‚Þ÷ˆ—›ãn8ISå‘´ a!¯í+ieÜ£>Ê`–I`)¦Nåz'R![À¶"i?Oøú™y½”u `b”]k‚wPh5™$ +˜Ÿ©;Ì‘OÄØ¡$,Á®áBIzÛþ5lÞÑê8éàh|áLÑûžÂ~F"qxIG"Q=c÷H¯©*,§—]¤lâ~Ì2ñWY£´åzÈÛÜ“‹×‘,œ8B\aã$¼g™ýÖ‚mK×P©€§ð±XRÉNˆÊ²5ÑžQú!‹ÄõCä‡I<¢ò/ë²$ì#V’Â=érXm×a¸ÇÓ{$öí<a_^ëp‘z/<¯ÂÙ\…dÄ>¡ú°âcôzÛüâ`Ôàô®¼÷d +÷$Ãuæôû[ÝR¾+¨áÐ'eò¢Qø»tK´ƒ]2Opû*GHì*–‡£à3 +éE뇕?ÖÇ»¾eúFeœxQùΞñë?´æÄ–r>Bþ.æ\ø³¡bN·M¡òø~ëƒ=G„§#Wï&J˜,1E¹¾"c³~ø©À_iPkÍY<ÌÂJø»Xô¶ø9¦T,«ø‰)!©:â¼kùÃÕœß!<?ž†_î"Šr=ÆD©"—U5Cˆ·=BT‘@¡«·½~ŸŠR“ì›jÄÛã‚úÚ}_½yE”†ðwiûÞ‡%·º§Ò¸yÀZü7“Gi6rÖˆ×DÂNF¢„•¦(×bÌoœ Ú-¼9iôòkVMs'*ñBÎôqÄY9–‹÷—«c>*H2´8¶yåwj`N5¡Þ¶›[¤–á5|(ÒÂËÃ9c'óðëLˆLKØNå¼}‘`Ò†ž›±>Þ¶úêíêˆm[´gd þ5)—uH¬¾ä¬)ü]/yúœÉ©ª8º«ñPxýÊëÔ)'xs”ìAc·L„øB¯<Sò +yñÎëGŽ™äÁ1M"ÐîvM¥D?2”Èõ”;œ3!ñŠ=‡B=‚sSD✒šB¼í «óù8¼¹-3H Å4ïøpE"ØcªÝêí[Œ3!å“Ÿý5.Šá¶¿3ˆ%WýÙàðWø`̑ï +endobj +627 0 obj +5013 +endobj +628 0 obj<</Type/Page/Parent 450 0 R/Contents 629 0 R/Resources<</ProcSet[/PDF/Text]/Font<</F4 7 0 R/F5 8 0 R/F8 10 0 R/F9 11 0 R>>>>/Annots 334 0 R>>endobj +629 0 obj<</Length 630 0 R/Filter/FlateDecode>>stream +xÍ™ÍoÛFÅïþ+öè +f¤ŠbÒ`¤šR®ÏÄë“ñ)JœäY/ã3Œ‰0B-b!ž¶ŒWÝcšu¤‘‰[OZMˆç-a¹Ø%‹€È1¾Œ`¯{idæ·2!X²ÛÝnîöëžDZ¦…ô"Õr}–su}Öw2‹¶p½™J +°·‹ýÇ”Ë +°èn½ì=•à4™ø’âD´åt½-²ˆ©x¯FDªE8Öm]™7¶Èxb`yLXº³Ò‰¤ +°ŒNRé)¤“EU6¢Ä +°›S\Ö2“å»N%‚-åÓzØt»›i€Y‹æÊšÑEE¸%¹M?º¬£˜á¾®²I–ñpX¯R",O”…D®…ЋD‚˜Â¯t1`„è“
ÜQ!@-!,°ü²¦ÑsËû\VWüàZOK¿;ºÜsLÇ‹œÊøFÔûI€E}$j‚]⤟Ï3¹å(}$jýªKãÆŠà:yÎ?hÀ°ºAG&…N…a0ú õwëþ.αoY*ƒB.Ië?î7Ø3"³Tb6µ¸„bD¬¦¬ö´U?$—ðóXAb€t»ûnÑ·i3<^«\R€Æ<vû¿6»»”ë@ñ`šÁšâèÎÉ"´D.‹vÀÓ—Xv<–HWÊJDR€Î!tÔ!<)ˆÕ~iKQ‹õÝ%[5Š'{ð +³"ÝB°®H5!´ŠŸdLˆç-Áïµ%Ë +S,,8#XÊ¡{Ø/û݆¶Á|gL +°˜e· è¶$fnª#M#òi³H×Ã*0Ж±–qñçµx9ž„Ÿª¥¹ù5ëZÝ%ðï†eG¦öýD¦íͺ’]^ibÒîÝ Fés?
™åwfƌ׻ã¾[=,XEHRØœþò»Ý×\ó·Äšq*3ä†u¸¿R@wSoÌfthÏ`Ð`o³Ç`@DŠ·3S M#ÒÈðúUâyK0ýI:isÔOç‘ÀsîÌ$’¯eþs"‰jÙ§™tû;©²Ÿß`ÀßRDÒ˜zâi^ÞÝ4ÞíüÕ3×[ù˜ëØîM—4…LÞÐÔLhäXL)H#•WQŠ BÆÂ`óè^Î!hæÔãú¡”;ç_„PSŠ¬Dö©þ€J‘ÉËî_j._ÀˆˆãÆ)ƈñd9#”ƒ kS$1J¹¤Z1"Ö2–Ÿü;ž¼ü?X_(ÌðöÒòo/§˜¦òöû¬Sì¯Éû,¼ »>ÿíå¹û}ß}½þŸ»åÃ/ÉÏeo©q?¶òÊuuºÙlâçÍÉgG@+endstream +endobj +630 0 obj +1798 +endobj +631 0 obj<</Count 11/First 632 0 R/Last 727 0 R>>endobj +632 0 obj<</Parent 631 0 R/Title(Table of Contents)/Dest[622 0 R/XYZ null 756 null]/Next 633 0 R>>endobj +633 0 obj<</Parent 631 0 R/Count -19/First 634 0 R/Last 652 0 R/Title(Chapter 1. How to Install and Test SAMBA)/Dest[454 0 R/XYZ null 750 null]/Prev 632 0 R/Next 653 0 R>>endobj +634 0 obj<</Parent 633 0 R/Title(1.1. Step 0: Read the man pages)/Dest[454 0 R/XYZ null 726 null]/Next 635 0 R>>endobj +635 0 obj<</Parent 633 0 R/Title(1.2. Step 1: Building the Binaries)/Dest[454 0 R/XYZ null 589 null]/Prev 634 0 R/Next 636 0 R>>endobj +636 0 obj<</Parent 633 0 R/Title(1.3. Step 2: The all important step)/Dest[454 0 R/XYZ null 174 null]/Prev 635 0 R/Next 637 0 R>>endobj +637 0 obj<</Parent 633 0 R/Title(1.4. Step 3: Create the smb configuration file.)/Dest[457 0 R/XYZ null 735 null]/Prev 636 0 R/Next 638 0 R>>endobj +638 0 obj<</Parent 633 0 R/Title(1.5. Step 4: Test your config file with testparm)/Dest[457 0 R/XYZ null 375 null]/Prev 637 0 R/Next 639 0 R>>endobj +639 0 obj<</Parent 633 0 R/Title(1.6. Step 5: Starting the smbd and nmbd)/Dest[457 0 R/XYZ null 264 null]/Prev 638 0 R/Next 640 0 R>>endobj +640 0 obj<</Parent 633 0 R/Title(1.6.1. Step 5a: Starting from inetd.conf)/Dest[460 0 R/XYZ null 750 null]/Prev 639 0 R/Next 641 0 R>>endobj +641 0 obj<</Parent 633 0 R/Title(1.6.2. Step 5b. Alternative: starting it as a daemon)/Dest[460 0 R/XYZ null 262 null]/Prev 640 0 R/Next 642 0 R>>endobj +642 0 obj<</Parent 633 0 R/Title(1.7. Step 6: Try listing the shares available on your server)/Dest[463 0 R/XYZ null 682 null]/Prev 641 0 R/Next 643 0 R>>endobj +643 0 obj<</Parent 633 0 R/Title(1.8. Step 7: Try connecting with the unix client)/Dest[463 0 R/XYZ null 505 null]/Prev 642 0 R/Next 644 0 R>>endobj +644 0 obj<</Parent 633 0 R/Title(1.9. Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client)/Dest[463 0 R/XYZ null 328 null]/Prev 643 0 R/Next 645 0 R>>endobj +645 0 obj<</Parent 633 0 R/Title(1.10. What If Things Don't Work?)/Dest[466 0 R/XYZ null 750 null]/Prev 644 0 R/Next 646 0 R>>endobj +646 0 obj<</Parent 633 0 R/Title(1.10.1. Diagnosing Problems)/Dest[466 0 R/XYZ null 573 null]/Prev 645 0 R/Next 647 0 R>>endobj +647 0 obj<</Parent 633 0 R/Title(1.10.2. Scope IDs)/Dest[466 0 R/XYZ null 501 null]/Prev 646 0 R/Next 648 0 R>>endobj +648 0 obj<</Parent 633 0 R/Title(1.10.3. Choosing the Protocol Level)/Dest[466 0 R/XYZ null 390 null]/Prev 647 0 R/Next 649 0 R>>endobj +649 0 obj<</Parent 633 0 R/Title(1.10.4. Printing from UNIX to a Client PC)/Dest[469 0 R/XYZ null 735 null]/Prev 648 0 R/Next 650 0 R>>endobj +650 0 obj<</Parent 633 0 R/Title(1.10.5. Locking)/Dest[469 0 R/XYZ null 611 null]/Prev 649 0 R/Next 651 0 R>>endobj +651 0 obj<</Parent 633 0 R/Title(1.10.6. Mapping Usernames)/Dest[472 0 R/XYZ null 750 null]/Prev 650 0 R/Next 652 0 R>>endobj +652 0 obj<</Parent 633 0 R/Title(1.10.7. Other Character Sets)/Dest[472 0 R/XYZ null 679 null]/Prev 651 0 R>>endobj +653 0 obj<</Parent 631 0 R/Count -8/First 654 0 R/Last 661 0 R/Title(Chapter 2. LanMan and NT Password Encryption in Samba 2.x)/Dest[475 0 R/XYZ null 750 null]/Prev 633 0 R/Next 662 0 R>>endobj +654 0 obj<</Parent 653 0 R/Title(2.1. Introduction)/Dest[475 0 R/XYZ null 702 null]/Next 655 0 R>>endobj +655 0 obj<</Parent 653 0 R/Title(2.2. How does it work?)/Dest[475 0 R/XYZ null 565 null]/Prev 654 0 R/Next 656 0 R>>endobj +656 0 obj<</Parent 653 0 R/Title(2.3. Important Notes About Security)/Dest[478 0 R/XYZ null 695 null]/Prev 655 0 R/Next 657 0 R>>endobj +657 0 obj<</Parent 653 0 R/Title(2.3.1. Advantages of SMB Encryption)/Dest[478 0 R/XYZ null 216 null]/Prev 656 0 R/Next 658 0 R>>endobj +658 0 obj<</Parent 653 0 R/Title(2.3.2. Advantages of non-encrypted passwords)/Dest[481 0 R/XYZ null 750 null]/Prev 657 0 R/Next 659 0 R>>endobj +659 0 obj<</Parent 653 0 R/Title(2.4. The smbpasswd file)/Dest[481 0 R/XYZ null 652 null]/Prev 658 0 R/Next 660 0 R>>endobj +660 0 obj<</Parent 653 0 R/Title(2.5. The smbpasswd Command)/Dest[484 0 R/XYZ null 395 null]/Prev 659 0 R/Next 661 0 R>>endobj +661 0 obj<</Parent 653 0 R/Title(2.6. Setting up Samba to support LanManager Encryption)/Dest[487 0 R/XYZ null 471 null]/Prev 660 0 R>>endobj +662 0 obj<</Parent 631 0 R/Count -2/First 663 0 R/Last 664 0 R/Title(Chapter 3. Hosting a Microsoft Distributed File System tree on Samba)/Dest[490 0 R/XYZ null 750 null]/Prev 653 0 R/Next 665 0 R>>endobj +663 0 obj<</Parent 662 0 R/Title(3.1. Instructions)/Dest[490 0 R/XYZ null 702 null]/Next 664 0 R>>endobj +664 0 obj<</Parent 662 0 R/Title(3.1.1. Notes)/Dest[493 0 R/XYZ null 669 null]/Prev 663 0 R>>endobj +665 0 obj<</Parent 631 0 R/Count -13/First 666 0 R/Last 678 0 R/Title(Chapter 4. Printing Support in Samba 2.2.x)/Dest[496 0 R/XYZ null 750 null]/Prev 662 0 R/Next 679 0 R>>endobj +666 0 obj<</Parent 665 0 R/Title(4.1. Introduction)/Dest[496 0 R/XYZ null 726 null]/Next 667 0 R>>endobj +667 0 obj<</Parent 665 0 R/Title(4.2. Configuration)/Dest[496 0 R/XYZ null 298 null]/Prev 666 0 R/Next 668 0 R>>endobj +668 0 obj<</Parent 665 0 R/Title(4.2.1. Creating [print$])/Dest[499 0 R/XYZ null 689 null]/Prev 667 0 R/Next 669 0 R>>endobj +669 0 obj<</Parent 665 0 R/Title(4.2.2. Setting Drivers for Existing Printers)/Dest[502 0 R/XYZ null 538 null]/Prev 668 0 R/Next 670 0 R>>endobj +670 0 obj<</Parent 665 0 R/Title(4.2.3. Support a large number of printers)/Dest[505 0 R/XYZ null 750 null]/Prev 669 0 R/Next 671 0 R>>endobj +671 0 obj<</Parent 665 0 R/Title(4.2.4. Adding New Printers via the Windows NT APW)/Dest[505 0 R/XYZ null 379 null]/Prev 670 0 R/Next 672 0 R>>endobj +672 0 obj<</Parent 665 0 R/Title(4.2.5. Samba and Printer Ports)/Dest[508 0 R/XYZ null 750 null]/Prev 671 0 R/Next 673 0 R>>endobj +673 0 obj<</Parent 665 0 R/Title(4.3. The Imprints Toolset)/Dest[508 0 R/XYZ null 573 null]/Prev 672 0 R/Next 674 0 R>>endobj +674 0 obj<</Parent 665 0 R/Title(4.3.1. What is Imprints?)/Dest[508 0 R/XYZ null 462 null]/Prev 673 0 R/Next 675 0 R>>endobj +675 0 obj<</Parent 665 0 R/Title(4.3.2. Creating Printer Driver Packages)/Dest[508 0 R/XYZ null 324 null]/Prev 674 0 R/Next 676 0 R>>endobj +676 0 obj<</Parent 665 0 R/Title(4.3.3. The Imprints server)/Dest[508 0 R/XYZ null 226 null]/Prev 675 0 R/Next 677 0 R>>endobj +677 0 obj<</Parent 665 0 R/Title(4.3.4. The Installation Client)/Dest[511 0 R/XYZ null 750 null]/Prev 676 0 R/Next 678 0 R>>endobj +678 0 obj<</Parent 665 0 R/Title(4.4. Migration to from Samba 2.0.x to 2.2.x)/Dest[511 0 R/XYZ null 187 null]/Prev 677 0 R>>endobj +679 0 obj<</Parent 631 0 R/Count -3/First 680 0 R/Last 682 0 R/Title(Chapter 5. security = domain in Samba 2.x)/Dest[517 0 R/XYZ null 750 null]/Prev 665 0 R/Next 683 0 R>>endobj +680 0 obj<</Parent 679 0 R/Title(5.1. Joining an NT Domain with Samba 2.2)/Dest[517 0 R/XYZ null 726 null]/Next 681 0 R>>endobj +681 0 obj<</Parent 679 0 R/Title(5.2. Samba and Windows 2000 Domains)/Dest[520 0 R/XYZ null 352 null]/Prev 680 0 R/Next 682 0 R>>endobj +682 0 obj<</Parent 679 0 R/Title(5.3. Why is this better than security = server?)/Dest[523 0 R/XYZ null 750 null]/Prev 681 0 R>>endobj +683 0 obj<</Parent 631 0 R/Count -13/First 684 0 R/Last 696 0 R/Title(Chapter 6. How to Configure Samba 2.2 as a Primary Domain Controller)/Dest[526 0 R/XYZ null 750 null]/Prev 679 0 R/Next 697 0 R>>endobj +684 0 obj<</Parent 683 0 R/Title(6.1. Prerequisite Reading)/Dest[526 0 R/XYZ null 702 null]/Next 685 0 R>>endobj +685 0 obj<</Parent 683 0 R/Title(6.2. Background)/Dest[526 0 R/XYZ null 604 null]/Prev 684 0 R/Next 686 0 R>>endobj +686 0 obj<</Parent 683 0 R/Title(6.3. Configuring the Samba Domain Controller)/Dest[529 0 R/XYZ null 656 null]/Prev 685 0 R/Next 687 0 R>>endobj +687 0 obj<</Parent 683 0 R/Title(6.4. Creating Machine Trust Accounts and Joining Clients to the Domain)/Dest[532 0 R/XYZ null 527 null]/Prev 686 0 R/Next 688 0 R>>endobj +688 0 obj<</Parent 683 0 R/Title(6.4.1. Manually creating machine trust accounts)/Dest[532 0 R/XYZ null 192 null]/Prev 687 0 R/Next 689 0 R>>endobj +689 0 obj<</Parent 683 0 R/Title(6.4.2. Creating machine trust accounts "on the fly")/Dest[535 0 R/XYZ null 355 null]/Prev 688 0 R/Next 690 0 R>>endobj +690 0 obj<</Parent 683 0 R/Title(6.5. Common Problems and Errors)/Dest[535 0 R/XYZ null 179 null]/Prev 689 0 R/Next 691 0 R>>endobj +691 0 obj<</Parent 683 0 R/Title(6.6. System Policies and Profiles)/Dest[541 0 R/XYZ null 541 null]/Prev 690 0 R/Next 692 0 R>>endobj +692 0 obj<</Parent 683 0 R/Title(6.7. What other help can I get ?)/Dest[544 0 R/XYZ null 484 null]/Prev 691 0 R/Next 693 0 R>>endobj +693 0 obj<</Parent 683 0 R/Title(6.8. Domain Control for Windows 9x/ME)/Dest[553 0 R/XYZ null 750 null]/Prev 692 0 R/Next 694 0 R>>endobj +694 0 obj<</Parent 683 0 R/Title(6.8.1. Configuration Instructions: Network Logons)/Dest[556 0 R/XYZ null 431 null]/Prev 693 0 R/Next 695 0 R>>endobj +695 0 obj<</Parent 683 0 R/Title(6.8.2. Configuration Instructions: Setting up Roaming User Profiles)/Dest[559 0 R/XYZ null 185 null]/Prev 694 0 R/Next 696 0 R>>endobj +696 0 obj<</Parent 683 0 R/Title(6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba)/Dest[574 0 R/XYZ null 682 null]/Prev 695 0 R>>endobj +697 0 obj<</Parent 631 0 R/Count -13/First 698 0 R/Last 710 0 R/Title(Chapter 7. Unifed Logons between Windows NT and UNIX using Winbind)/Dest[580 0 R/XYZ null 750 null]/Prev 683 0 R/Next 711 0 R>>endobj +698 0 obj<</Parent 697 0 R/Title(7.1. Abstract)/Dest[580 0 R/XYZ null 702 null]/Next 699 0 R>>endobj +699 0 obj<</Parent 697 0 R/Title(7.2. Introduction)/Dest[580 0 R/XYZ null 565 null]/Prev 698 0 R/Next 700 0 R>>endobj +700 0 obj<</Parent 697 0 R/Title(7.3. What Winbind Provides)/Dest[580 0 R/XYZ null 242 null]/Prev 699 0 R/Next 701 0 R>>endobj +701 0 obj<</Parent 697 0 R/Title(7.3.1. Target Uses)/Dest[583 0 R/XYZ null 577 null]/Prev 700 0 R/Next 702 0 R>>endobj +702 0 obj<</Parent 697 0 R/Title(7.4. How Winbind Works)/Dest[583 0 R/XYZ null 413 null]/Prev 701 0 R/Next 703 0 R>>endobj +703 0 obj<</Parent 697 0 R/Title(7.4.1. Microsoft Remote Procedure Calls)/Dest[583 0 R/XYZ null 288 null]/Prev 702 0 R/Next 704 0 R>>endobj +704 0 obj<</Parent 697 0 R/Title(7.4.2. Name Service Switch)/Dest[586 0 R/XYZ null 750 null]/Prev 703 0 R/Next 705 0 R>>endobj +705 0 obj<</Parent 697 0 R/Title(7.4.3. Pluggable Authentication Modules)/Dest[586 0 R/XYZ null 322 null]/Prev 704 0 R/Next 706 0 R>>endobj +706 0 obj<</Parent 697 0 R/Title(7.4.4. User and Group ID Allocation)/Dest[589 0 R/XYZ null 682 null]/Prev 705 0 R/Next 707 0 R>>endobj +707 0 obj<</Parent 697 0 R/Title(7.4.5. Result Caching)/Dest[589 0 R/XYZ null 492 null]/Prev 706 0 R/Next 708 0 R>>endobj +708 0 obj<</Parent 697 0 R/Title(7.5. Installation and Configuration)/Dest[589 0 R/XYZ null 341 null]/Prev 707 0 R/Next 709 0 R>>endobj +709 0 obj<</Parent 697 0 R/Title(7.6. Limitations)/Dest[589 0 R/XYZ null 151 null]/Prev 708 0 R/Next 710 0 R>>endobj +710 0 obj<</Parent 697 0 R/Title(7.7. Conclusion)/Dest[592 0 R/XYZ null 577 null]/Prev 709 0 R>>endobj +711 0 obj<</Parent 631 0 R/Count -9/First 712 0 R/Last 720 0 R/Title(Chapter 8. UNIX Permission Bits and WIndows NT Access Control Lists)/Dest[595 0 R/XYZ null 750 null]/Prev 697 0 R/Next 721 0 R>>endobj +712 0 obj<</Parent 711 0 R/Title(8.1. Viewing and changing UNIX permissions using the NT security dialogs)/Dest[595 0 R/XYZ null 702 null]/Next 713 0 R>>endobj +713 0 obj<</Parent 711 0 R/Title(8.2. How to view file security on a Samba share)/Dest[595 0 R/XYZ null 521 null]/Prev 712 0 R/Next 714 0 R>>endobj +714 0 obj<</Parent 711 0 R/Title(8.3. Viewing file ownership)/Dest[595 0 R/XYZ null 344 null]/Prev 713 0 R/Next 715 0 R>>endobj +715 0 obj<</Parent 711 0 R/Title(8.4. Viewing file or directory permissions)/Dest[598 0 R/XYZ null 682 null]/Prev 714 0 R/Next 716 0 R>>endobj +716 0 obj<</Parent 711 0 R/Title(8.4.1. File Permissions)/Dest[598 0 R/XYZ null 439 null]/Prev 715 0 R/Next 717 0 R>>endobj +717 0 obj<</Parent 711 0 R/Title(8.4.2. Directory Permissions)/Dest[598 0 R/XYZ null 183 null]/Prev 716 0 R/Next 718 0 R>>endobj +718 0 obj<</Parent 711 0 R/Title(8.5. Modifying file or directory permissions)/Dest[601 0 R/XYZ null 669 null]/Prev 717 0 R/Next 719 0 R>>endobj +719 0 obj<</Parent 711 0 R/Title(8.6. Interaction with the standard Samba create mask parameters)/Dest[601 0 R/XYZ null 228 null]/Prev 718 0 R/Next 720 0 R>>endobj +720 0 obj<</Parent 711 0 R/Title(8.7. Interaction with the standard Samba file attribute mapping)/Dest[607 0 R/XYZ null 590 null]/Prev 719 0 R>>endobj +721 0 obj<</Parent 631 0 R/Count -5/First 722 0 R/Last 726 0 R/Title(Chapter 9. OS2 Client HOWTO)/Dest[610 0 R/XYZ null 750 null]/Prev 711 0 R/Next 727 0 R>>endobj +722 0 obj<</Parent 721 0 R/Title(9.1. FAQs)/Dest[610 0 R/XYZ null 726 null]/Next 723 0 R>>endobj +723 0 obj<</Parent 721 0 R/Title(9.1.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?)/Dest[610 0 R/XYZ null 696 null]/Prev 722 0 R/Next 724 0 R>>endobj +724 0 obj<</Parent 721 0 R/Title(9.1.2. How can I configure OS/2 Warp 3 \(not Connect\), OS/2 1.2, 1.3 or 2.x for Samba?)/Dest[610 0 R/XYZ null 344 null]/Prev 723 0 R/Next 725 0 R>>endobj +725 0 obj<</Parent 721 0 R/Title(9.1.3. Are there any other issues when OS/2 \(any version\) is used as a client?)/Dest[613 0 R/XYZ null 750 null]/Prev 724 0 R/Next 726 0 R>>endobj +726 0 obj<</Parent 721 0 R/Title(9.1.4. How do I get printer driver download working for OS/2 clients?)/Dest[613 0 R/XYZ null 635 null]/Prev 725 0 R>>endobj +727 0 obj<</Parent 631 0 R/Count -4/First 728 0 R/Last 731 0 R/Title(Chapter 10. HOWTO Access Samba source code via CVS)/Dest[616 0 R/XYZ null 750 null]/Prev 721 0 R>>endobj +728 0 obj<</Parent 727 0 R/Title(10.1. Introduction)/Dest[616 0 R/XYZ null 702 null]/Next 729 0 R>>endobj +729 0 obj<</Parent 727 0 R/Title(10.2. CVS Access to samba.org)/Dest[616 0 R/XYZ null 578 null]/Prev 728 0 R/Next 730 0 R>>endobj +730 0 obj<</Parent 727 0 R/Title(10.2.1. Access via CVSweb)/Dest[616 0 R/XYZ null 480 null]/Prev 729 0 R/Next 731 0 R>>endobj +731 0 obj<</Parent 727 0 R/Title(10.2.2. Access via cvs)/Dest[616 0 R/XYZ null 355 null]/Prev 730 0 R>>endobj +732 0 obj<</Type/Catalog/Pages 450 0 R/Names 335 0 R/PageLayout/SinglePage/Outlines 631 0 R/OpenAction[451 0 R/XYZ null null null]/PageMode/UseOutlines/PageLabels<</Nums[0<</P(title)>>1<</S/r>>4<</S/D>>]>>>>endobj xref -0 650 +0 733 0000000000 65535 f 0000000015 00000 n 0000000244 00000 n @@ -1437,623 +1673,706 @@ xref 0000003817 00000 n 0000003874 00000 n 0000003959 00000 n -0000004064 00000 n -0000004102 00000 n -0000004143 00000 n -0000004227 00000 n -0000004269 00000 n -0000004354 00000 n -0000004393 00000 n -0000004478 00000 n -0000004520 00000 n -0000004605 00000 n -0000004647 00000 n -0000004732 00000 n -0000004776 00000 n -0000004861 00000 n -0000004920 00000 n -0000004967 00000 n -0000005052 00000 n -0000005076 00000 n -0000005128 00000 n -0000005213 00000 n -0000005262 00000 n -0000005347 00000 n -0000005396 00000 n -0000005480 00000 n -0000005532 00000 n -0000005617 00000 n -0000005665 00000 n -0000005750 00000 n -0000005798 00000 n -0000005882 00000 n -0000005945 00000 n -0000006030 00000 n -0000006096 00000 n -0000006159 00000 n -0000006242 00000 n -0000006266 00000 n -0000006313 00000 n -0000006398 00000 n +0000004052 00000 n +0000004136 00000 n +0000004174 00000 n +0000004279 00000 n +0000004320 00000 n +0000004404 00000 n +0000004446 00000 n +0000004531 00000 n +0000004570 00000 n +0000004655 00000 n +0000004697 00000 n +0000004782 00000 n +0000004824 00000 n +0000004909 00000 n +0000004968 00000 n +0000005012 00000 n +0000005097 00000 n +0000005121 00000 n +0000005168 00000 n +0000005253 00000 n +0000005305 00000 n +0000005390 00000 n +0000005439 00000 n +0000005524 00000 n +0000005573 00000 n +0000005657 00000 n +0000005709 00000 n +0000005793 00000 n +0000005845 00000 n +0000005893 00000 n +0000005978 00000 n +0000006026 00000 n +0000006110 00000 n +0000006173 00000 n +0000006258 00000 n +0000006296 00000 n +0000006359 00000 n 0000006444 00000 n -0000006528 00000 n -0000006568 00000 n -0000006651 00000 n -0000006689 00000 n +0000006468 00000 n +0000006515 00000 n +0000006600 00000 n +0000006646 00000 n 0000006730 00000 n -0000006815 00000 n -0000006863 00000 n -0000006948 00000 n -0000006994 00000 n -0000007079 00000 n -0000007117 00000 n -0000007169 00000 n -0000007254 00000 n -0000007297 00000 n -0000007382 00000 n -0000007438 00000 n -0000007523 00000 n -0000007618 00000 n -0000007702 00000 n -0000007747 00000 n -0000007795 00000 n -0000007880 00000 n -0000007926 00000 n -0000008010 00000 n -0000008041 00000 n -0000008087 00000 n -0000008172 00000 n -0000008219 00000 n -0000008304 00000 n -0000008348 00000 n -0000008434 00000 n -0000008476 00000 n -0000008562 00000 n -0000008602 00000 n -0000008688 00000 n -0000008736 00000 n -0000008822 00000 n -0000008867 00000 n -0000008953 00000 n -0000008997 00000 n -0000009083 00000 n -0000009134 00000 n -0000009220 00000 n -0000009269 00000 n -0000009355 00000 n -0000009400 00000 n -0000009486 00000 n -0000009528 00000 n -0000009614 00000 n -0000009657 00000 n -0000009743 00000 n -0000009785 00000 n -0000009871 00000 n -0000009915 00000 n -0000010001 00000 n -0000010038 00000 n -0000010124 00000 n -0000010166 00000 n -0000010252 00000 n -0000010294 00000 n -0000010380 00000 n -0000010417 00000 n -0000010503 00000 n -0000010545 00000 n -0000010631 00000 n -0000010674 00000 n -0000010760 00000 n -0000010806 00000 n -0000010892 00000 n -0000010939 00000 n -0000011024 00000 n -0000011225 00000 n -0000011274 00000 n -0000011361 00000 n -0000011410 00000 n -0000011496 00000 n -0000011545 00000 n -0000011632 00000 n -0000011674 00000 n -0000011720 00000 n -0000011807 00000 n -0000011833 00000 n -0000011948 00000 n -0000012035 00000 n -0000012061 00000 n -0000012143 00000 n -0000012230 00000 n -0000012315 00000 n -0000012402 00000 n -0000012457 00000 n -0000012544 00000 n -0000012600 00000 n -0000012687 00000 n -0000012737 00000 n -0000012785 00000 n -0000012872 00000 n +0000006770 00000 n +0000006853 00000 n +0000006891 00000 n +0000006932 00000 n +0000007017 00000 n +0000007065 00000 n +0000007150 00000 n +0000007196 00000 n +0000007281 00000 n +0000007319 00000 n +0000007371 00000 n +0000007456 00000 n +0000007499 00000 n +0000007584 00000 n +0000007640 00000 n +0000007725 00000 n +0000007820 00000 n +0000007904 00000 n +0000007949 00000 n +0000007995 00000 n +0000008080 00000 n +0000008126 00000 n +0000008211 00000 n +0000008260 00000 n +0000008346 00000 n +0000008393 00000 n +0000008480 00000 n +0000008528 00000 n +0000008575 00000 n +0000008662 00000 n +0000008709 00000 n +0000008794 00000 n +0000008838 00000 n +0000008924 00000 n +0000008966 00000 n +0000009052 00000 n +0000009092 00000 n +0000009178 00000 n +0000009226 00000 n +0000009312 00000 n +0000009357 00000 n +0000009443 00000 n +0000009487 00000 n +0000009573 00000 n +0000009624 00000 n +0000009710 00000 n +0000009759 00000 n +0000009845 00000 n +0000009890 00000 n +0000009976 00000 n +0000010018 00000 n +0000010104 00000 n +0000010147 00000 n +0000010233 00000 n +0000010275 00000 n +0000010361 00000 n +0000010405 00000 n +0000010491 00000 n +0000010528 00000 n +0000010614 00000 n +0000010656 00000 n +0000010742 00000 n +0000010784 00000 n +0000010870 00000 n +0000010907 00000 n +0000010991 00000 n +0000011033 00000 n +0000011117 00000 n +0000011295 00000 n +0000011338 00000 n +0000011424 00000 n +0000011470 00000 n +0000011556 00000 n +0000011603 00000 n +0000011690 00000 n +0000011739 00000 n +0000011826 00000 n +0000011875 00000 n +0000011961 00000 n +0000012010 00000 n +0000012097 00000 n +0000012163 00000 n +0000012211 00000 n +0000012297 00000 n +0000012343 00000 n +0000012430 00000 n +0000012464 00000 n +0000012579 00000 n +0000012666 00000 n +0000012692 00000 n +0000012774 00000 n +0000012861 00000 n 0000012946 00000 n 0000013033 00000 n -0000013101 00000 n -0000013187 00000 n -0000013241 00000 n -0000013326 00000 n -0000013394 00000 n -0000013479 00000 n -0000013537 00000 n -0000013611 00000 n -0000013698 00000 n -0000013746 00000 n -0000013833 00000 n -0000013890 00000 n -0000013977 00000 n -0000014032 00000 n -0000014118 00000 n -0000014199 00000 n -0000014286 00000 n -0000014344 00000 n -0000014389 00000 n -0000014476 00000 n -0000014502 00000 n -0000014547 00000 n -0000014633 00000 n -0000014676 00000 n -0000014763 00000 n -0000014813 00000 n -0000014900 00000 n -0000014950 00000 n -0000015035 00000 n -0000015083 00000 n -0000015170 00000 n -0000015217 00000 n -0000015303 00000 n -0000015369 00000 n -0000015448 00000 n -0000015535 00000 n -0000015617 00000 n -0000015703 00000 n -0000015778 00000 n -0000015865 00000 n -0000015938 00000 n -0000016025 00000 n -0000016075 00000 n -0000016153 00000 n -0000016240 00000 n -0000016266 00000 n -0000016371 00000 n -0000016477 00000 n -0000016583 00000 n -0000016689 00000 n -0000016795 00000 n -0000016901 00000 n -0000017007 00000 n -0000017113 00000 n -0000017219 00000 n -0000017325 00000 n -0000017431 00000 n -0000017537 00000 n -0000017643 00000 n -0000017749 00000 n -0000017855 00000 n -0000017961 00000 n -0000018067 00000 n -0000018173 00000 n -0000018279 00000 n -0000018385 00000 n -0000018490 00000 n -0000018596 00000 n -0000018702 00000 n -0000018808 00000 n -0000018914 00000 n -0000019020 00000 n -0000019126 00000 n -0000019232 00000 n -0000019338 00000 n -0000019443 00000 n -0000019549 00000 n -0000019655 00000 n -0000019760 00000 n -0000019866 00000 n -0000019972 00000 n -0000020078 00000 n -0000020184 00000 n -0000020290 00000 n -0000020396 00000 n -0000020502 00000 n -0000020608 00000 n -0000020714 00000 n -0000020819 00000 n -0000020923 00000 n -0000021027 00000 n -0000021405 00000 n -0000021511 00000 n -0000021616 00000 n -0000021722 00000 n -0000021828 00000 n -0000021934 00000 n +0000013088 00000 n +0000013173 00000 n +0000013215 00000 n +0000013271 00000 n +0000013358 00000 n +0000013406 00000 n +0000013493 00000 n +0000013567 00000 n +0000013652 00000 n +0000013694 00000 n +0000013762 00000 n +0000013849 00000 n +0000013903 00000 n +0000013990 00000 n +0000014058 00000 n +0000014145 00000 n +0000014219 00000 n +0000014306 00000 n +0000014354 00000 n +0000014441 00000 n +0000014498 00000 n +0000014585 00000 n +0000014640 00000 n +0000014727 00000 n +0000014808 00000 n +0000014895 00000 n +0000014977 00000 n +0000015022 00000 n +0000015109 00000 n +0000015135 00000 n +0000015180 00000 n +0000015266 00000 n +0000015309 00000 n +0000015396 00000 n +0000015446 00000 n +0000015533 00000 n +0000015583 00000 n +0000015668 00000 n +0000015716 00000 n +0000015803 00000 n +0000015850 00000 n +0000015936 00000 n +0000016002 00000 n +0000016081 00000 n +0000016168 00000 n +0000016250 00000 n +0000016336 00000 n +0000016411 00000 n +0000016498 00000 n +0000016571 00000 n +0000016658 00000 n +0000016708 00000 n +0000016786 00000 n +0000016873 00000 n +0000016899 00000 n +0000016962 00000 n +0000017049 00000 n +0000017112 00000 n +0000017199 00000 n +0000017253 00000 n +0000017340 00000 n +0000017382 00000 n +0000017487 00000 n +0000017593 00000 n +0000017699 00000 n +0000017805 00000 n +0000017911 00000 n +0000018017 00000 n +0000018123 00000 n +0000018229 00000 n +0000018335 00000 n +0000018441 00000 n +0000018547 00000 n +0000018653 00000 n +0000018759 00000 n +0000018865 00000 n +0000018971 00000 n +0000019077 00000 n +0000019183 00000 n +0000019289 00000 n +0000019395 00000 n +0000019501 00000 n +0000019606 00000 n +0000019712 00000 n +0000019818 00000 n +0000019924 00000 n +0000020030 00000 n +0000020136 00000 n +0000020242 00000 n +0000020348 00000 n +0000020454 00000 n +0000020559 00000 n +0000020665 00000 n +0000020771 00000 n +0000020876 00000 n +0000020982 00000 n +0000021088 00000 n +0000021194 00000 n +0000021300 00000 n +0000021406 00000 n +0000021512 00000 n +0000021618 00000 n +0000021724 00000 n +0000021830 00000 n +0000021935 00000 n 0000022039 00000 n -0000022145 00000 n -0000022251 00000 n -0000022357 00000 n -0000022463 00000 n -0000022569 00000 n -0000022675 00000 n -0000022781 00000 n -0000022887 00000 n -0000022993 00000 n -0000023098 00000 n -0000023204 00000 n -0000023310 00000 n -0000023416 00000 n -0000023522 00000 n -0000023628 00000 n -0000023734 00000 n -0000023840 00000 n -0000023946 00000 n -0000024052 00000 n -0000024158 00000 n -0000024264 00000 n -0000024370 00000 n -0000024476 00000 n -0000024581 00000 n -0000024687 00000 n -0000024793 00000 n -0000024899 00000 n -0000025005 00000 n -0000025111 00000 n -0000025217 00000 n -0000025323 00000 n -0000025429 00000 n -0000025535 00000 n -0000025640 00000 n -0000025745 00000 n -0000025849 00000 n -0000025953 00000 n -0000026315 00000 n -0000026421 00000 n -0000026527 00000 n -0000026561 00000 n -0000026595 00000 n -0000026629 00000 n -0000028196 00000 n -0000028245 00000 n -0000028294 00000 n -0000028343 00000 n -0000028392 00000 n -0000028441 00000 n -0000028490 00000 n -0000028539 00000 n -0000028588 00000 n -0000028637 00000 n -0000028686 00000 n -0000028735 00000 n -0000028784 00000 n -0000028833 00000 n -0000028882 00000 n -0000028931 00000 n -0000028980 00000 n -0000029029 00000 n -0000029078 00000 n -0000029127 00000 n -0000029176 00000 n -0000029225 00000 n -0000029274 00000 n -0000029323 00000 n -0000029372 00000 n -0000029421 00000 n -0000029470 00000 n -0000029519 00000 n -0000029568 00000 n -0000029617 00000 n -0000029666 00000 n -0000029715 00000 n -0000029764 00000 n -0000029813 00000 n -0000029862 00000 n -0000029911 00000 n -0000029960 00000 n -0000030009 00000 n -0000030058 00000 n -0000030107 00000 n -0000030156 00000 n -0000030205 00000 n -0000030254 00000 n -0000030303 00000 n -0000030352 00000 n -0000030401 00000 n -0000030450 00000 n -0000030499 00000 n -0000030548 00000 n -0000030597 00000 n -0000030646 00000 n -0000030695 00000 n -0000030744 00000 n -0000030793 00000 n -0000030842 00000 n -0000030891 00000 n -0000030940 00000 n -0000030989 00000 n -0000031038 00000 n -0000031087 00000 n -0000031136 00000 n -0000031185 00000 n -0000031234 00000 n -0000031283 00000 n -0000031332 00000 n -0000031381 00000 n -0000031430 00000 n -0000031479 00000 n -0000031528 00000 n -0000031577 00000 n -0000031626 00000 n -0000031675 00000 n -0000031724 00000 n -0000031773 00000 n -0000031822 00000 n -0000031871 00000 n -0000031920 00000 n -0000031969 00000 n -0000032018 00000 n -0000032067 00000 n -0000032116 00000 n -0000032165 00000 n -0000032214 00000 n -0000032263 00000 n -0000032312 00000 n -0000032361 00000 n -0000032410 00000 n -0000032459 00000 n -0000032508 00000 n -0000032557 00000 n -0000032606 00000 n -0000032655 00000 n -0000032704 00000 n -0000032753 00000 n -0000032802 00000 n -0000032851 00000 n -0000032900 00000 n -0000033361 00000 n -0000033508 00000 n -0000034047 00000 n -0000034068 00000 n -0000034242 00000 n -0000035405 00000 n -0000035427 00000 n -0000035578 00000 n -0000037100 00000 n -0000037122 00000 n -0000037282 00000 n -0000038718 00000 n -0000038740 00000 n -0000038918 00000 n -0000040178 00000 n -0000040200 00000 n -0000040342 00000 n -0000041926 00000 n -0000041948 00000 n -0000042081 00000 n -0000043818 00000 n -0000043840 00000 n -0000043973 00000 n -0000044495 00000 n -0000044516 00000 n -0000044658 00000 n -0000046328 00000 n -0000046350 00000 n -0000046511 00000 n -0000048362 00000 n -0000048384 00000 n -0000048572 00000 n -0000050189 00000 n -0000050211 00000 n -0000050390 00000 n -0000052213 00000 n -0000052235 00000 n -0000052409 00000 n -0000053626 00000 n -0000053648 00000 n -0000053822 00000 n -0000055427 00000 n -0000055449 00000 n -0000055592 00000 n -0000056349 00000 n -0000056370 00000 n -0000056554 00000 n -0000058341 00000 n -0000058363 00000 n -0000058537 00000 n -0000060643 00000 n -0000060665 00000 n -0000060840 00000 n -0000062567 00000 n -0000062589 00000 n -0000062773 00000 n -0000064742 00000 n -0000064764 00000 n -0000064934 00000 n -0000066444 00000 n -0000066466 00000 n -0000066650 00000 n -0000068561 00000 n -0000068583 00000 n -0000068766 00000 n -0000070395 00000 n -0000070417 00000 n -0000070591 00000 n -0000072195 00000 n -0000072217 00000 n -0000072391 00000 n -0000074133 00000 n -0000074155 00000 n -0000074321 00000 n -0000075900 00000 n -0000075922 00000 n -0000076098 00000 n -0000077839 00000 n -0000077861 00000 n -0000078046 00000 n -0000079872 00000 n -0000079894 00000 n -0000080069 00000 n -0000081974 00000 n -0000081996 00000 n -0000082171 00000 n -0000084293 00000 n -0000084315 00000 n -0000084491 00000 n -0000086343 00000 n -0000086365 00000 n -0000086541 00000 n -0000088467 00000 n -0000088489 00000 n -0000088665 00000 n -0000090755 00000 n -0000090777 00000 n -0000090928 00000 n -0000092624 00000 n -0000092646 00000 n -0000092769 00000 n -0000093755 00000 n -0000093776 00000 n -0000093928 00000 n -0000095673 00000 n -0000095695 00000 n -0000095837 00000 n -0000097591 00000 n -0000097613 00000 n -0000097764 00000 n -0000099703 00000 n -0000099725 00000 n -0000099876 00000 n -0000101691 00000 n -0000101713 00000 n -0000101856 00000 n -0000102937 00000 n -0000102959 00000 n -0000103143 00000 n -0000105016 00000 n -0000105038 00000 n -0000105207 00000 n -0000107067 00000 n -0000107089 00000 n -0000107249 00000 n -0000108934 00000 n -0000108956 00000 n -0000109130 00000 n -0000110857 00000 n -0000110879 00000 n -0000111030 00000 n -0000111954 00000 n -0000111975 00000 n -0000112142 00000 n -0000113807 00000 n -0000113829 00000 n -0000113986 00000 n -0000115166 00000 n -0000115188 00000 n -0000115345 00000 n -0000120394 00000 n -0000120416 00000 n -0000120573 00000 n -0000125843 00000 n -0000125865 00000 n -0000126013 00000 n -0000126745 00000 n -0000126766 00000 n -0000126822 00000 n -0000126927 00000 n -0000127105 00000 n -0000127224 00000 n -0000127359 00000 n -0000127495 00000 n -0000127643 00000 n -0000127793 00000 n -0000127933 00000 n -0000128074 00000 n -0000128227 00000 n -0000128389 00000 n -0000128538 00000 n -0000128726 00000 n -0000128859 00000 n -0000128987 00000 n -0000129105 00000 n -0000129241 00000 n -0000129383 00000 n -0000129499 00000 n -0000129625 00000 n -0000129741 00000 n -0000129935 00000 n -0000130040 00000 n -0000130163 00000 n -0000130299 00000 n -0000130435 00000 n -0000130580 00000 n -0000130704 00000 n -0000130831 00000 n -0000130973 00000 n -0000131178 00000 n -0000131283 00000 n -0000131383 00000 n -0000131563 00000 n -0000131668 00000 n -0000131787 00000 n -0000131912 00000 n -0000132057 00000 n -0000132199 00000 n -0000132349 00000 n -0000132480 00000 n -0000132606 00000 n -0000132731 00000 n -0000132871 00000 n -0000132998 00000 n -0000133129 00000 n -0000133261 00000 n -0000133439 00000 n -0000133567 00000 n -0000133703 00000 n -0000133838 00000 n -0000134045 00000 n -0000134148 00000 n -0000134293 00000 n -0000134465 00000 n -0000134597 00000 n -0000134731 00000 n -0000134864 00000 n -0000134988 00000 n -0000135109 00000 n -0000135256 00000 n -0000135460 00000 n -0000135561 00000 n -0000135679 00000 n -0000135806 00000 n -0000135925 00000 n -0000136048 00000 n -0000136188 00000 n -0000136315 00000 n -0000136455 00000 n -0000136591 00000 n -0000136713 00000 n -0000136849 00000 n -0000136966 00000 n -0000137069 00000 n -0000137273 00000 n -0000137434 00000 n -0000137582 00000 n -0000137710 00000 n -0000137853 00000 n -0000137977 00000 n -0000138106 00000 n -0000138251 00000 n -0000138416 00000 n -0000138568 00000 n -0000138719 00000 n -0000138816 00000 n -0000139000 00000 n -0000139189 00000 n -0000139371 00000 n -0000139529 00000 n +0000022143 00000 n +0000022521 00000 n +0000022627 00000 n +0000022732 00000 n +0000022838 00000 n +0000022944 00000 n +0000023050 00000 n +0000023155 00000 n +0000023261 00000 n +0000023367 00000 n +0000023473 00000 n +0000023579 00000 n +0000023685 00000 n +0000023791 00000 n +0000023897 00000 n +0000024003 00000 n +0000024109 00000 n +0000024215 00000 n +0000024321 00000 n +0000024427 00000 n +0000024533 00000 n +0000024638 00000 n +0000024744 00000 n +0000024850 00000 n +0000024956 00000 n +0000025062 00000 n +0000025168 00000 n +0000025274 00000 n +0000025380 00000 n +0000025486 00000 n +0000025592 00000 n +0000025698 00000 n +0000025804 00000 n +0000025910 00000 n +0000026016 00000 n +0000026121 00000 n +0000026227 00000 n +0000026333 00000 n +0000026439 00000 n +0000026545 00000 n +0000026651 00000 n +0000026757 00000 n +0000026863 00000 n +0000026968 00000 n +0000027072 00000 n +0000027434 00000 n +0000027539 00000 n +0000027645 00000 n +0000027751 00000 n +0000027857 00000 n +0000027963 00000 n +0000028069 00000 n +0000028174 00000 n +0000028280 00000 n +0000028386 00000 n +0000028492 00000 n +0000028598 00000 n +0000028704 00000 n +0000028738 00000 n +0000028772 00000 n +0000030594 00000 n +0000030643 00000 n +0000030692 00000 n +0000030741 00000 n +0000030790 00000 n +0000030839 00000 n +0000030888 00000 n +0000030937 00000 n +0000030986 00000 n +0000031035 00000 n +0000031084 00000 n +0000031133 00000 n +0000031182 00000 n +0000031231 00000 n +0000031280 00000 n +0000031329 00000 n +0000031378 00000 n +0000031427 00000 n +0000031476 00000 n +0000031525 00000 n +0000031574 00000 n +0000031623 00000 n +0000031672 00000 n +0000031721 00000 n +0000031770 00000 n +0000031819 00000 n +0000031868 00000 n +0000031917 00000 n +0000031966 00000 n +0000032015 00000 n +0000032064 00000 n +0000032113 00000 n +0000032162 00000 n +0000032211 00000 n +0000032260 00000 n +0000032309 00000 n +0000032358 00000 n +0000032407 00000 n +0000032456 00000 n +0000032505 00000 n +0000032554 00000 n +0000032603 00000 n +0000032652 00000 n +0000032701 00000 n +0000032750 00000 n +0000032799 00000 n +0000032848 00000 n +0000032897 00000 n +0000032946 00000 n +0000032995 00000 n +0000033044 00000 n +0000033093 00000 n +0000033142 00000 n +0000033191 00000 n +0000033240 00000 n +0000033289 00000 n +0000033338 00000 n +0000033387 00000 n +0000033436 00000 n +0000033485 00000 n +0000033534 00000 n +0000033583 00000 n +0000033632 00000 n +0000033681 00000 n +0000033730 00000 n +0000033779 00000 n +0000033828 00000 n +0000033877 00000 n +0000033926 00000 n +0000033975 00000 n +0000034024 00000 n +0000034073 00000 n +0000034122 00000 n +0000034171 00000 n +0000034220 00000 n +0000034269 00000 n +0000034318 00000 n +0000034367 00000 n +0000034416 00000 n +0000034465 00000 n +0000034514 00000 n +0000034563 00000 n +0000034612 00000 n +0000034661 00000 n +0000034710 00000 n +0000034759 00000 n +0000034808 00000 n +0000034857 00000 n +0000034906 00000 n +0000034955 00000 n +0000035004 00000 n +0000035053 00000 n +0000035102 00000 n +0000035151 00000 n +0000035200 00000 n +0000035249 00000 n +0000035298 00000 n +0000035347 00000 n +0000035396 00000 n +0000035445 00000 n +0000035494 00000 n +0000035543 00000 n +0000035592 00000 n +0000035641 00000 n +0000035690 00000 n +0000035739 00000 n +0000035788 00000 n +0000035837 00000 n +0000035886 00000 n +0000035935 00000 n +0000035984 00000 n +0000036033 00000 n +0000036082 00000 n +0000036631 00000 n +0000036778 00000 n +0000037310 00000 n +0000037331 00000 n +0000037505 00000 n +0000038668 00000 n +0000038690 00000 n +0000038841 00000 n +0000040363 00000 n +0000040385 00000 n +0000040545 00000 n +0000041981 00000 n +0000042003 00000 n +0000042181 00000 n +0000043441 00000 n +0000043463 00000 n +0000043605 00000 n +0000045189 00000 n +0000045211 00000 n +0000045344 00000 n +0000047081 00000 n +0000047103 00000 n +0000047236 00000 n +0000047758 00000 n +0000047779 00000 n +0000047921 00000 n +0000049591 00000 n +0000049613 00000 n +0000049774 00000 n +0000051625 00000 n +0000051647 00000 n +0000051835 00000 n +0000053452 00000 n +0000053474 00000 n +0000053653 00000 n +0000055476 00000 n +0000055498 00000 n +0000055672 00000 n +0000056889 00000 n +0000056911 00000 n +0000057085 00000 n +0000058690 00000 n +0000058712 00000 n +0000058855 00000 n +0000059612 00000 n +0000059633 00000 n +0000059817 00000 n +0000061642 00000 n +0000061664 00000 n +0000061838 00000 n +0000064034 00000 n +0000064056 00000 n +0000064249 00000 n +0000066192 00000 n +0000066214 00000 n +0000066398 00000 n +0000068297 00000 n +0000068319 00000 n +0000068503 00000 n +0000070174 00000 n +0000070196 00000 n +0000070357 00000 n +0000072057 00000 n +0000072079 00000 n +0000072271 00000 n +0000074003 00000 n +0000074025 00000 n +0000074208 00000 n +0000075837 00000 n +0000075859 00000 n +0000076033 00000 n +0000077637 00000 n +0000077659 00000 n +0000077833 00000 n +0000079575 00000 n +0000079597 00000 n +0000079782 00000 n +0000081588 00000 n +0000081610 00000 n +0000081776 00000 n +0000083479 00000 n +0000083501 00000 n +0000083677 00000 n +0000085683 00000 n +0000085705 00000 n +0000085899 00000 n +0000087736 00000 n +0000087758 00000 n +0000087927 00000 n +0000089865 00000 n +0000089887 00000 n +0000090081 00000 n +0000092110 00000 n +0000092132 00000 n +0000092308 00000 n +0000094113 00000 n +0000094135 00000 n +0000094301 00000 n +0000096167 00000 n +0000096189 00000 n +0000096355 00000 n +0000098736 00000 n +0000098758 00000 n +0000098900 00000 n +0000100824 00000 n +0000100846 00000 n +0000100988 00000 n +0000102683 00000 n +0000102705 00000 n +0000102865 00000 n +0000104889 00000 n +0000104911 00000 n +0000105062 00000 n +0000106634 00000 n +0000106656 00000 n +0000106798 00000 n +0000108771 00000 n +0000108793 00000 n +0000108944 00000 n +0000110873 00000 n +0000110895 00000 n +0000111037 00000 n +0000112901 00000 n +0000112923 00000 n +0000113083 00000 n +0000114917 00000 n +0000114939 00000 n +0000115062 00000 n +0000116150 00000 n +0000116172 00000 n +0000116324 00000 n +0000118069 00000 n +0000118091 00000 n +0000118233 00000 n +0000119987 00000 n +0000120009 00000 n +0000120160 00000 n +0000122099 00000 n +0000122121 00000 n +0000122272 00000 n +0000124086 00000 n +0000124108 00000 n +0000124251 00000 n +0000125332 00000 n +0000125354 00000 n +0000125538 00000 n +0000127413 00000 n +0000127435 00000 n +0000127604 00000 n +0000129464 00000 n +0000129486 00000 n +0000129646 00000 n +0000131331 00000 n +0000131353 00000 n +0000131527 00000 n +0000133254 00000 n +0000133276 00000 n +0000133427 00000 n +0000134351 00000 n +0000134372 00000 n +0000134539 00000 n +0000136204 00000 n +0000136226 00000 n +0000136383 00000 n +0000137570 00000 n +0000137592 00000 n +0000137749 00000 n +0000139300 00000 n +0000139322 00000 n +0000139472 00000 n +0000140185 00000 n +0000140206 00000 n +0000140363 00000 n +0000145416 00000 n +0000145438 00000 n +0000145595 00000 n +0000150679 00000 n +0000150701 00000 n +0000150858 00000 n +0000152727 00000 n +0000152749 00000 n +0000152805 00000 n +0000152910 00000 n +0000153088 00000 n +0000153207 00000 n +0000153342 00000 n +0000153478 00000 n +0000153626 00000 n +0000153776 00000 n +0000153916 00000 n +0000154057 00000 n +0000154210 00000 n +0000154372 00000 n +0000154521 00000 n +0000154709 00000 n +0000154842 00000 n +0000154970 00000 n +0000155088 00000 n +0000155224 00000 n +0000155366 00000 n +0000155482 00000 n +0000155608 00000 n +0000155724 00000 n +0000155918 00000 n +0000156023 00000 n +0000156146 00000 n +0000156282 00000 n +0000156418 00000 n +0000156563 00000 n +0000156687 00000 n +0000156814 00000 n +0000156956 00000 n +0000157161 00000 n +0000157266 00000 n +0000157366 00000 n +0000157546 00000 n +0000157651 00000 n +0000157770 00000 n +0000157895 00000 n +0000158040 00000 n +0000158182 00000 n +0000158332 00000 n +0000158463 00000 n +0000158589 00000 n +0000158714 00000 n +0000158854 00000 n +0000158981 00000 n +0000159112 00000 n +0000159243 00000 n +0000159421 00000 n +0000159549 00000 n +0000159685 00000 n +0000159820 00000 n +0000160026 00000 n +0000160139 00000 n +0000160255 00000 n +0000160400 00000 n +0000160572 00000 n +0000160720 00000 n +0000160872 00000 n +0000161004 00000 n +0000161138 00000 n +0000161271 00000 n +0000161409 00000 n +0000161559 00000 n +0000161727 00000 n +0000161874 00000 n +0000162078 00000 n +0000162179 00000 n +0000162297 00000 n +0000162424 00000 n +0000162543 00000 n +0000162666 00000 n +0000162806 00000 n +0000162933 00000 n +0000163073 00000 n +0000163209 00000 n +0000163331 00000 n +0000163467 00000 n +0000163584 00000 n +0000163687 00000 n +0000163891 00000 n +0000164052 00000 n +0000164200 00000 n +0000164328 00000 n +0000164471 00000 n +0000164595 00000 n +0000164724 00000 n +0000164869 00000 n +0000165034 00000 n +0000165186 00000 n +0000165350 00000 n +0000165447 00000 n +0000165631 00000 n +0000165820 00000 n +0000166002 00000 n +0000166160 00000 n +0000166334 00000 n +0000166440 00000 n +0000166570 00000 n +0000166696 00000 n +0000166806 00000 n trailer -<</Size 650/Root 649 0 R/Info 1 0 R/ID[<4c0cb111c71223d1abdea98e47b3a13f><4c0cb111c71223d1abdea98e47b3a13f>]>> +<</Size 733/Root 732 0 R/Info 1 0 R/ID[<379319e715cf855d9f261ba14b5e3b6b><379319e715cf855d9f261ba14b5e3b6b>]>> startxref -139743 +167020 %%EOF diff --git a/docs/docbook/Makefile.in b/docs/docbook/Makefile.in index e3694896f2..0c043d77e3 100644 --- a/docs/docbook/Makefile.in +++ b/docs/docbook/Makefile.in @@ -36,7 +36,8 @@ MANPAGES=$(MANDIR)/findsmb.1 $(MANDIR)/smbclient.1 \ $(MANDIR)/smbpasswd.5 $(MANDIR)/testparm.1 $(MANDIR)/samba.7 \ $(MANDIR)/smbpasswd.8 $(MANDIR)/testprns.1 \ $(MANDIR)/smb.conf.5 $(MANDIR)/wbinfo.1 \ - $(MANDIR)/smbcacls.1 $(MANDIR)/smbsh.1 $(MANDIR)/winbindd.8 + $(MANDIR)/smbcacls.1 $(MANDIR)/smbsh.1 $(MANDIR)/winbindd.8 \ + $(MANDIR)/make_unicodemap.1 SGMLMANSRC=manpages/findsmb.1.sgml manpages/smbclient.1.sgml \ manpages/smbspool.8.sgml manpages/lmhosts.5.sgml \ @@ -50,12 +51,14 @@ SGMLMANSRC=manpages/findsmb.1.sgml manpages/smbclient.1.sgml \ manpages/smbpasswd.8.sgml manpages/testprns.1.sgml \ manpages/smb.conf.5.sgml \ manpages/wbinfo.1.sgml manpages/smbcacls.1.sgml \ - manpages/smbsh.1.sgml manpages/winbindd.8.sgml + manpages/smbsh.1.sgml manpages/winbindd.8.sgml \ + manpages/make_unicodemap.1.sgml HOWTOSRC=projdoc/DOMAIN_MEMBER.sgml projdoc/NT_Security.sgml \ projdoc/msdfs_setup.sgml projdoc/printer_driver2.sgml \ projdoc/UNIX_INSTALL.sgml projdoc/winbind.sgml projdoc/OS2-Client-HOWTO.sgml \ - projdoc/Samba-PDC-HOWTO.sgml projdoc/ENCRYPTION.sgml + projdoc/Samba-PDC-HOWTO.sgml projdoc/ENCRYPTION.sgml \ + projdoc/CVS-Access.sgml FAQSRC=faq/samba-pdc-faq.sgml @@ -71,7 +74,7 @@ man: $(MANPAGES) FAQ: $(FAQSRC) @echo Building SAMBA PDC FAQ... @(for i in $?; do \ - htmlfile=`basename $$i | sed "s/\.sgml/\.html/g"`; \ + htmlfile=`echo $$i | sed 's,.*/,,' | sed "s/\.sgml/\.html/g"`; \ echo "Making $$htmlfile"; \ $(JADE) -t sgml -V nochunks -d $(SGML_SHARE)/dsssl/docbook/html/docbook.dsl \ -f /tmp/jade.log $$i > ../htmldocs/$$htmlfile; \ @@ -82,13 +85,13 @@ FAQ: $(FAQSRC) HOWTO: $(HOWTOSRC) @echo Building HOWTO pages... @(for i in $?; do \ - htmlfile=`basename $$i | sed "s/\.sgml/\.html/g"`; \ + htmlfile=`echo $$i | sed 's,.*/,,' | sed "s/\.sgml/\.html/g"`; \ echo "Making $$htmlfile"; \ - cat $$i | $(PERL) scripts/make-article.pl > /tmp/`basename $$i`; \ + cat $$i | $(PERL) scripts/make-article.pl > /tmp/`echo $$i | sed 's,.*/,,'`; \ $(JADE) -t sgml -V nochunks -d $(SGML_SHARE)/dsssl/docbook/html/docbook.dsl \ - -f /tmp/jade.log /tmp/`basename $$i` > ../htmldocs/$$htmlfile; \ + -f /tmp/jade.log /tmp/`echo $$i | sed 's,.*/,,'` > ../htmldocs/$$htmlfile; \ cat /tmp/jade.log | grep -v DTDDECL; \ - /bin/rm -f /tmp/jade.log /tmp/`basename $$i`; \ + /bin/rm -f /tmp/jade.log /tmp/`echo $$i | sed 's,.*/,,'`; \ done) @@ -102,7 +105,6 @@ proj-doc: @(cd projdoc; $(JADE) -t sgml -i html -V nochunks -d ../stylesheets/ldp.dsl\#html samba-doc.sgml > ../samba-doc.html) @(cd scripts; ./ldp_print ../samba-doc.html) @mv -f samba-doc.pdf ../Samba-HOWTO-Collection.pdf - #@$(HTMLDOC) -f ../Samba-HOWTO-Collection.pdf samba-doc.html @/bin/mv -f samba-doc.html ../htmldocs/Samba-HOWTO-Collection.html @@ -113,7 +115,7 @@ proj-doc: man-html-all: $(SGMLMANSRC) @echo Building HTML formatted man pages... @(for i in $?; do \ - htmlfile=`basename $$i | sed "s/\.sgml/\.html/g"`; \ + htmlfile=`echo $$i | sed 's,.*/,,' | sed "s/\.sgml/\.html/g"`; \ echo "Making $$htmlfile"; \ $(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html -f /tmp/jade.log $$i > ../htmldocs/$$htmlfile; \ cat /tmp/jade.log | grep -v DTDDECL; \ @@ -124,7 +126,7 @@ man-html-all: $(SGMLMANSRC) man-all: $(SGMLMANSRC) @echo Building man pages... @(for i in $?; do \ - manfile=`basename $$i | sed "s/\.sgml//g"`; \ + manfile=`echo $$i | sed 's,.*/,,' | sed "s/\.sgml//g"`; \ echo "Making $$manfile"; \ $(ONSGMLS) -f /tmp/docbook2x.log $$i | $(SGMLSPL) \ $(SGML_SHARE)/docbook2X/docbook2man-spec.pl; \ @@ -143,210 +145,218 @@ man-all: $(SGMLMANSRC) $(MANDIR)/findsmb.1: manpages/findsmb.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbclient.1: manpages/smbclient.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbspool.8: manpages/smbspool.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/lmhosts.5: manpages/lmhosts.5.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbcontrol.1: manpages/smbcontrol.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbstatus.1: manpages/smbstatus.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/make_smbcodepage.1: manpages/make_smbcodepage.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` + +$(MANDIR)/make_unicodemap.1: manpages/make_unicodemap.1.sgml + @echo "Making $@" + @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` + @echo "Making HTML version of $@" + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbd.8: manpages/smbd.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbtar.1: manpages/smbtar.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/nmbd.8: manpages/nmbd.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbmnt.8: manpages/smbmnt.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbumount.8: manpages/smbumount.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/nmblookup.1: manpages/nmblookup.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbmount.8: manpages/smbmount.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/swat.8: manpages/swat.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/rpcclient.1: manpages/rpcclient.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbpasswd.5: manpages/smbpasswd.5.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/testparm.1: manpages/testparm.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/samba.7: manpages/samba.7.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbpasswd.8: manpages/smbpasswd.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/testprns.1: manpages/testprns.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smb.conf.5: manpages/smb.conf.5.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/wbinfo.1: manpages/wbinfo.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbcacls.1: manpages/smbcacls.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/smbsh.1 : manpages/smbsh.1.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` $(MANDIR)/winbindd.8: manpages/winbindd.8.sgml @echo "Making $@" @$(ONSGMLS) $< | $(SGMLSPL) $(SGML_SHARE)/docbook2X/docbook2man-spec.pl - @cat `basename $@` | $(PERL) scripts/strip-links.pl > $@ - @/bin/rm -f `basename $@` + @cat `echo $@ | sed 's,.*/,,'` | $(PERL) scripts/strip-links.pl > $@ + @/bin/rm -f `echo $@ | sed 's,.*/,,'` @echo "Making HTML version of $@" - @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`basename $< | sed "s/\.sgml/\.html/g"` + @$(JADE) -t sgml -i html -V nochunks -d ./stylesheets/ldp.dsl\#html $< > $(HTMLDIR)/`echo $< | sed 's,.*/,,'| sed "s/\.sgml/\.html/g"` ## Clean Rule diff --git a/docs/docbook/manpages/make_smbcodepage.1.sgml b/docs/docbook/manpages/make_smbcodepage.1.sgml index 8a58b8614d..a36f9b968c 100644 --- a/docs/docbook/manpages/make_smbcodepage.1.sgml +++ b/docs/docbook/manpages/make_smbcodepage.1.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="findsmb"> +<refentry id="make-smbcodepage"> <refmeta> <refentrytitle>make_smbcodepage</refentrytitle> @@ -56,11 +56,11 @@ <varlistentry> <term>inputfile</term> - <listitem><para>This is the input file to process. In t - he '<parameter>c</parameter>' case this will be a text + <listitem><para>This is the input file to process. In + the <parameter>c</parameter> case this will be a text codepage definition file such as the ones found in the Samba <filename>source/codepages</filename> directory. In - the '<parameter>d</parameter>' case this will be the + the <parameter>d</parameter> case this will be the binary format codepage definition file normally found in the <filename>lib/codepages</filename> directory in the Samba install directory path.</para></listitem> diff --git a/docs/docbook/manpages/make_unicodemap.1.sgml b/docs/docbook/manpages/make_unicodemap.1.sgml new file mode 100644 index 0000000000..50a5446d60 --- /dev/null +++ b/docs/docbook/manpages/make_unicodemap.1.sgml @@ -0,0 +1,172 @@ +<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> +<refentry id="make-unicodemap"> + +<refmeta> + <refentrytitle>make_unicodemap</refentrytitle> + <manvolnum>1</manvolnum> +</refmeta> + + +<refnamediv> + <refname>make_unicodemap</refname> + <refpurpose>construct a unicode map file for Samba</refpurpose> +</refnamediv> + +<refsynopsisdiv> + <cmdsynopsis> + <command>make_unicodemap</command> + <arg choice="req">codepage</arg> + <arg choice="req">inputfile</arg> + <arg choice="req">outputfile</arg> + </cmdsynopsis> +</refsynopsisdiv> + + + +<refsect1> + <title>DESCRIPTION</title> + + <para> + This tool is part of the <ulink url="samba.7.html">Samba</ulink> + suite. + </para> + + <para> + <command>make_unicodemap</command> compiles text unicode map + files into binary unicodef map files for use with the + internationalization features of Samba 2.2. + </para> +</refsect1> + + + +<refsect1> + <title>OPTIONS</title> + + <variablelist> + <varlistentry> + <term>codepage</term> + <listitem><para>This is the codepage or UNIX character + set we are processing (a number, e.g. 850). + </para></listitem> + </varlistentry> + + <varlistentry> + <term>inputfile</term> + <listitem><para>This is the input file to process. This is a + text unicode map file such as the ones found in the Samba + <filename>source/codepages</filename> directory. + </para></listitem> + </varlistentry> + + <varlistentry> + <term>outputfile</term> + <listitem><para>This is the binary output file to produce. + </para></listitem> + </varlistentry> + </variablelist> +</refsect1> + + +<refsect1> + <title>Samba Unicode Map Files</title> + + <para> + A text Samba unicode map file is a description that tells Samba + how to map characters from a specified DOS code page or UNIX character + set to 16 bit unicode. + </para> + + <para>A binary Samba unicode map file is a binary representation + of the same information, including a value that specifies what + codepage or UNIX character set this file is describing. + </para> +</refsect1> + +<refsect1> + <title>Files</title> + + <para><filename>CP<codepage>.TXT</filename></para> + + <para> + These are the input (text) unicode map files provided + in the Samba <filename>source/codepages</filename> + directory. + </para> + + <para> + A text unicode map file consists of multiple lines + containing two fields. These fields are : + </para> + + <itemizedlist> + <listitem><para><parameter>character</parameter> - which is + the (hex) character mapped on this line. + </para></listitem> + + <listitem><para><parameter>unicode</parameter> - which + is the (hex) 16 bit unicode character that the character + will map to. + </para></listitem> + </itemizedlist> + + <para> + <filename>unicode_map.<codepage></filename> - These are + the output (binary) unicode map files produced and placed in + the Samba destination <filename>lib/codepage</filename> + directory. + </para> +</refsect1> + + +<refsect1> + <title>Installation</title> + + <para> + The location of the server and its support files is a matter + for individual system administrators. The following are thus + suggestions only. + </para> + + <para> + It is recommended that the <command>make_unicodemap</command> + program be installed under the + <filename>$prefix/samba</filename> hierarchy, + in a directory readable by all, writeable only by root. The + program itself should be executable by all. The program + should NOT be setuid or setgid! + </para> +</refsect1> + +<refsect1> + <title>VERSION</title> + + <para>This man page is correct for version 2.2 of + the Samba suite.</para> +</refsect1> + +<refsect1> + <title>SEE ALSO</title> + <para><ulink url="smbd.8.html"><command>smbd(8)</command></ulink>, + <ulink url="smb.conf.5.html">smb.conf(5)</ulink> + </para> +</refsect1> + +<refsect1> + <title>AUTHOR</title> + + <para>The original Samba software and related utilities + were created by Andrew Tridgell. Samba is now developed + by the Samba Team as an Open Source project similar + to the way the Linux kernel is developed.</para> + + <para>The original Samba man pages were written by Karl Auer. + The man page sources were converted to YODL format (another + excellent piece of Open Source software, available at + <ulink url="ftp://ftp.icce.rug.nl/pub/unix/"> + ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0 + release by Jeremy Allison. The conversion to DocBook for + Samba 2.2 was done by Gerald Carter</para> +</refsect1> + +</refentry> diff --git a/docs/docbook/manpages/nmbd.8.sgml b/docs/docbook/manpages/nmbd.8.sgml index 5194b1072b..8db2749bfa 100644 --- a/docs/docbook/manpages/nmbd.8.sgml +++ b/docs/docbook/manpages/nmbd.8.sgml @@ -37,7 +37,7 @@ <para><command>nmbd</command> is a server that understands and can reply to NetBIOS over IP name service requests, like - those produced by SMBD/CIFS clients such as Windows 95/98/ME, + those produced by SMB/CIFS clients such as Windows 95/98/ME, Windows NT, Windows 2000, and LanManager clients. It also participates in the browsing protocols which make up the Windows "Network Neighborhood" view.</para> diff --git a/docs/docbook/manpages/rpcclient.1.sgml b/docs/docbook/manpages/rpcclient.1.sgml index c02f935d82..0d45a5dc20 100644 --- a/docs/docbook/manpages/rpcclient.1.sgml +++ b/docs/docbook/manpages/rpcclient.1.sgml @@ -107,8 +107,9 @@ <varlistentry> <term>-l logbasename</term> - <listitem><para>File name for log/debug files. .client will be - appended. The log file is never removed by the client. + <listitem><para>File name for log/debug files. The extension + '.client' will be appended. The log file is never removed + by the client. </para></listitem> </varlistentry> @@ -161,9 +162,8 @@ <varlistentry> <term>-W domain</term> <listitem><para>Set the SMB domain of the username. This - overrides the default domain which is the domain of the - server specified with the <parameter>-S</parameter> option. - If the domain specified is the same as the server's NetBIOS name, + overrides the default domain which is the domain defined in + smb.conf. If the domain specified is the same as the server's NetBIOS name, it causes the client to log on using the server's local SAM (as opposed to the Domain SAM). </para></listitem> </varlistentry> @@ -179,8 +179,15 @@ <para><emphasis>LSARPC</emphasis></para> <itemizedlist> <listitem><para><command>lsaquery</command></para></listitem> - <listitem><para><command>lookupsids</command></para></listitem> - <listitem><para><command>lookupnames</command></para></listitem> + + <listitem><para><command>lookupsids</command> - Resolve a list + of SIDs to usernames. + </para></listitem> + + <listitem><para><command>lookupnames</command> - Resolve s list + of usernames to SIDs. + </para></listitem> + <listitem><para><command>enumtrusts</command></para></listitem> </itemizedlist> <para> </para> @@ -193,6 +200,10 @@ <listitem><para><command>querygroup</command></para></listitem> <listitem><para><command>queryusergroups</command></para></listitem> <listitem><para><command>querygroupmem</command></para></listitem> + <listitem><para><command>queryaliasmem</command></para></listitem> + <listitem><para><command>querydispinfo</command></para></listitem> + <listitem><para><command>querydominfo</command></para></listitem> + <listitem><para><command>enumdomgroups</command></para></listitem> </itemizedlist> <para> </para> @@ -244,6 +255,12 @@ </listitem> + <listitem><para><command>deldriver</command> - Delete the + specified printer driver for all architectures. This + does not delete the actual driver files from the server, + only the entry from the server's list of drivers. + </para></listitem> + <listitem><para><command>enumdata</command> - Enumerate all printer setting data stored on the server. On Windows NT clients, these values are stored in the registry, while Samba servers diff --git a/docs/docbook/manpages/smb.conf.5.sgml b/docs/docbook/manpages/smb.conf.5.sgml index e5357d24f3..70b4cc1c8e 100644 --- a/docs/docbook/manpages/smb.conf.5.sgml +++ b/docs/docbook/manpages/smb.conf.5.sgml @@ -325,7 +325,7 @@ <para>Many of the strings that are settable in the config file can take substitutions. For example the option "path = - /tmp/%U" would be interpreted as "path = + /tmp/%u" would be interpreted as "path = /tmp/john" if the user connected with the username john.</para> <para>These substitutions are mostly noted in the descriptions below, @@ -586,8 +586,9 @@ each parameter for details. Note that some are synonyms.</para> <itemizedlist> + <listitem><para><link linkend="ADDPRINTERCOMMAND"><parameter>add printer command</parameter></link></para></listitem> + <listitem><para><link linkend="ADDSHARECOMMAND"><parameter>add share command</parameter></link></para></listitem> <listitem><para><link linkend="ADDUSERSCRIPT"><parameter>add user script</parameter></link></para></listitem> - <listitem><para><link linkend="ADDPRINTERCOMMAND"><parameter>addprinter command</parameter></link></para></listitem> <listitem><para><link linkend="ALLOWTRUSTEDDOMAINS"><parameter>allow trusted domains</parameter></link></para></listitem> <listitem><para><link linkend="ANNOUNCEAS"><parameter>announce as</parameter></link></para></listitem> <listitem><para><link linkend="ANNOUNCEVERSION"><parameter>announce version</parameter></link></para></listitem> @@ -595,6 +596,7 @@ <listitem><para><link linkend="BINDINTERFACESONLY"><parameter>bind interfaces only</parameter></link></para></listitem> <listitem><para><link linkend="BROWSELIST"><parameter>browse list</parameter></link></para></listitem> <listitem><para><link linkend="CHANGENOTIFYTIMEOUT"><parameter>change notify timeout</parameter></link></para></listitem> + <listitem><para><link linkend="CHANGESHARECOMMAND"><parameter>change share command</parameter></link></para></listitem> <listitem><para><link linkend="CHARACTERSET"><parameter>character set</parameter></link></para></listitem> <listitem><para><link linkend="CLIENTCODEPAGE"><parameter>client code page</parameter></link></para></listitem> <listitem><para><link linkend="CODEPAGEDIRECTORY"><parameter>code page directory</parameter></link></para></listitem> @@ -608,15 +610,13 @@ <listitem><para><link linkend="DEBUGLEVEL"><parameter>debuglevel</parameter></link></para></listitem> <listitem><para><link linkend="DEFAULT"><parameter>default</parameter></link></para></listitem> <listitem><para><link linkend="DEFAULTSERVICE"><parameter>default service</parameter></link></para></listitem> + <listitem><para><link linkend="DELETEPRINTERCOMMAND"><parameter>delete printer command</parameter></link></para></listitem> + <listitem><para><link linkend="DELETESHARECOMMAND"><parameter>delete share command</parameter></link></para></listitem> <listitem><para><link linkend="DELETEUSERSCRIPT"><parameter>delete user script</parameter></link></para></listitem> - <listitem><para><link linkend="DELETEPRINTERCOMMAND"><parameter>deleteprinter command</parameter></link></para></listitem> <listitem><para><link linkend="DFREECOMMAND"><parameter>dfree command</parameter></link></para></listitem> <listitem><para><link linkend="DNSPROXY"><parameter>dns proxy</parameter></link></para></listitem> <listitem><para><link linkend="DOMAINADMINGROUP"><parameter>domain admin group</parameter></link></para></listitem> - <listitem><para><link linkend="DOMAINADMINUSERS"><parameter>domain admin users</parameter></link></para></listitem> - <listitem><para><link linkend="DOMAINGROUPS"><parameter>domain groups</parameter></link></para></listitem> <listitem><para><link linkend="DOMAINGUESTGROUP"><parameter>domain guest group</parameter></link></para></listitem> - <listitem><para><link linkend="DOMAINGUESTUSERS"><parameter>domain guest users</parameter></link></para></listitem> <listitem><para><link linkend="DOMAINLOGONS"><parameter>domain logons</parameter></link></para></listitem> <listitem><para><link linkend="DOMAINMASTER"><parameter>domain master</parameter></link></para></listitem> <listitem><para><link linkend="ENCRYPTPASSWORDS"><parameter>encrypt passwords</parameter></link></para></listitem> @@ -670,9 +670,11 @@ <listitem><para><link linkend="NTPIPESUPPORT"><parameter>nt pipe support</parameter></link></para></listitem> <listitem><para><link linkend="NTSMBSUPPORT"><parameter>nt smb support</parameter></link></para></listitem> <listitem><para><link linkend="NULLPASSWORDS"><parameter>null passwords</parameter></link></para></listitem> + <listitem><para><link linkend="OBEYPAMRESTRICTIONS"><parameter>obey pam restrictions</parameter></link></para></listitem> <listitem><para><link linkend="OPLOCKBREAKWAITTIME"><parameter>oplock break wait time</parameter></link></para></listitem> <listitem><para><link linkend="OSLEVEL"><parameter>os level</parameter></link></para></listitem> <listitem><para><link linkend="OS2DRIVERMAP"><parameter>os2 driver map</parameter></link></para></listitem> + <listitem><para><link linkend="PAMPASSWORDCHANGE"><parameter>pam password change</parameter></link></para></listitem> <listitem><para><link linkend="PANICACTION"><parameter>panic action</parameter></link></para></listitem> <listitem><para><link linkend="PASSWDCHAT"><parameter>passwd chat</parameter></link></para></listitem> <listitem><para><link linkend="PASSWDCHATDEBUG"><parameter>passwd chat debug</parameter></link></para></listitem> @@ -881,6 +883,119 @@ <variablelist> + + <varlistentry> + <term><anchor id="ADDPRINTERCOMMAND">add printer command (G)</term> + <listitem><para>With the introduction of MS-RPC based printing + support for Windows NT/2000 clients in Samba 2.2, The MS Add + Printer Wizard (APW) icon is now also available in the + "Printers..." folder displayed a share listing. The APW + allows for printers to be add remotely to a Samba or Windows + NT/2000 print server.</para> + + <para>For a Samba host this means that the printer must be + physically added to underlying printing system. The <parameter>add + printer command</parameter> defines a script to be run which + will perform the necessary operations for adding the printer + to the print system and to add the appropriate service definition + to the <filename>smb.conf</filename> file in order that it can be + shared by <ulink url="smbd.8.html"><command>smbd(8)</command> + </ulink>.</para> + + <para>The <parameter>add printer command</parameter> is + automatically invoked with the following parameter (in + order:</para> + + <itemizedlist> + <listitem><para><parameter>printer name</parameter></para></listitem> + <listitem><para><parameter>share name</parameter></para></listitem> + <listitem><para><parameter>port name</parameter></para></listitem> + <listitem><para><parameter>driver name</parameter></para></listitem> + <listitem><para><parameter>location</parameter></para></listitem> + <listitem><para><parameter>Windows 9x driver location</parameter> + </para></listitem> + </itemizedlist> + + <para>All parameters are filled in from the PRINTER_INFO_2 structure sent + by the Windows NT/2000 client with one exception. The "Windows 9x + driver location" parameter is included for backwards compatibility + only. The remaining fields in the structure are generated from answers + to the APW questions.</para> + + <para>Once the <parameter>add printer command</parameter> has + been executed, <command>smbd</command> will reparse the <filename> + smb.conf</filename> to determine if the share defined by the APW + exists. If the sharename is still invalid, then <command>smbd + </command> will return an ACCESS_DENIED error to the client.</para> + + <para>See also <link linkend="DELETEPRINTERCOMMAND"><parameter> + delete printer command</parameter></link>, <link + linkend="printing"><parameter>printing</parameter></link>, + <link linkend="SHOWADDPRINTERWIZARD"><parameter>show add + printer wizard</parameter></link></para> + + <para>Default: <emphasis>none</emphasis></para> + <para>Example: <command>addprinter command = /usr/bin/addprinter + </command></para> + </listitem> + </varlistentry> + + + + <varlistentry> + <term><anchor id="ADDSHARECOMMAND">add share command (G)</term> + <listitem><para>Samba 2.2.0 introduced the ability to dynamically + add and delete shares via the Windows NT 4.0 Server Manager. The + <parameter>add share command</parameter> is used to define an + external program or script which will add a new service definition + to <filename>smb.conf</filename>. In order to successfully + execute the <parameter>add share command</parameter>, <command>smbd</command> + requires that the administrator be connected using a root account (i.e. + uid == 0). + </para> + + <para> + When executed, <command>smbd</command> will automatically invoke the + <parameter>add share command</parameter> with four parameters. + </para> + + <itemizedlist> + <listitem><para><parameter>configFile</parameter> - the location + of the global <filename>smb.conf</filename> file. + </para></listitem> + + <listitem><para><parameter>shareName</parameter> - the name of the new + share. + </para></listitem> + + <listitem><para><parameter>pathName</parameter> - path to an **existing** + directory on disk. + </para></listitem> + + <listitem><para><parameter>comment</parameter> - comment string to associate + with the new share. + </para></listitem> + </itemizedlist> + + <para> + This parameter is only used for add file shares. To add printer shares, + see the <link linkend="ADDPRINTERCOMMAND"><parameter>add printer + command</parameter></link>. + </para> + + <para> + See also <link linkend="CHANGESHARECOMMAND"><parameter>change share + command</parameter></link>, <link linkend="DELETESHARECOMMAND"><parameter>delete share + command</parameter></link>. + </para> + + <para>Default: <emphasis>none</emphasis></para> + <para>Example: <command>add share command = /usr/local/bin/addshare</command></para> + </listitem> + </varlistentry> + + + <varlistentry> <term><anchor id="ADDUSERSCRIPT">add user script (G)</term> <listitem><para>This is the full pathname to a script that will @@ -935,63 +1050,6 @@ <varlistentry> - <term><anchor id="ADDPRINTERCOMMAND">addprinter command (G)</term> - <listitem><para>With the introduction of MS-RPC based printing - support for Windows NT/2000 clients in Samba 2.2, The MS Add - Printer Wizard (APW) icon is now also available in the - "Printers..." folder displayed a share listing. The APW - allows for printers to be add remotely to a Samba or Windows - NT/2000 print server.</para> - - <para>For a Samba host this means that the printer must be - physically added to underlying printing system. The <parameter> - addprinter command</parameter> defines a script to be run which - will perform the necessary operations for adding the printer - to the print system and to add the appropriate service definition - to the <filename>smb.conf</filename> file in order that it can be - shared by <ulink url="smbd.8.html"><command>smbd(8)</command> - </ulink>.</para> - - <para>The <parameter>addprinter command</parameter> is - automatically invoked with the following parameter (in - order:</para> - - <itemizedlist> - <listitem><para><parameter>printer name</parameter></para></listitem> - <listitem><para><parameter>share name</parameter></para></listitem> - <listitem><para><parameter>port name</parameter></para></listitem> - <listitem><para><parameter>driver name</parameter></para></listitem> - <listitem><para><parameter>location</parameter></para></listitem> - <listitem><para><parameter>Windows 9x driver location</parameter> - </para></listitem> - </itemizedlist> - - <para>All parameters are filled in from the PRINTER_INFO_2 structure sent - by the Windows NT/2000 client with one exception. The "Windows 9x - driver location" parameter is included for backwards compatibility - only. The remaining fields in the structure are generated from answers - to the APW questions.</para> - - <para>Once the <parameter>addprinter command</parameter> has - been executed, <command>smbd</command> will reparse the <filename> - smb.conf</filename> to determine if the share defined by the APW - exists. If the sharename is still invalid, then <command>smbd - </command> will return an ACCESS_DENIED error to the client.</para> - - <para>See also <link linkend="DELETEPRINTERCOMMAND"><parameter> - deleteprinter command</parameter></link>, <link - linkend="printing"><parameter>printing</parameter></link>, - <link linkend="SHOWADDPRINTERWIZARD"><parameter>show add - printer wizard</parameter></link></para> - - <para>Default: <emphasis>none</emphasis></para> - <para>Example: <command>addprinter command = /usr/bin/addprinter - </command></para> - </listitem> - </varlistentry> - - - <varlistentry> <term><anchor id="ADMINUSERS">admin users (S)</term> <listitem><para>This is a list of users who will be granted administrative privileges on the share. This means that they @@ -1264,7 +1322,60 @@ <para>Would change the scan time to every 5 minutes.</para></listitem> </varlistentry> + + + <varlistentry> + <term><anchor id="CHANGESHARECOMMAND">change share command (G)</term> + <listitem><para>Samba 2.2.0 introduced the ability to dynamically + add and delete shares via the Windows NT 4.0 Server Manager. The + <parameter>change share command</parameter> is used to define an + external program or script which will modify an existing service definition + in <filename>smb.conf</filename>. In order to successfully + execute the <parameter>change share command</parameter>, <command>smbd</command> + requires that the administrator be connected using a root account (i.e. + uid == 0). + </para> + <para> + When executed, <command>smbd</command> will automatically invoke the + <parameter>change share command</parameter> with four parameters. + </para> + + <itemizedlist> + <listitem><para><parameter>configFile</parameter> - the location + of the global <filename>smb.conf</filename> file. + </para></listitem> + + <listitem><para><parameter>shareName</parameter> - the name of the new + share. + </para></listitem> + + <listitem><para><parameter>pathName</parameter> - path to an **existing** + directory on disk. + </para></listitem> + + <listitem><para><parameter>comment</parameter> - comment string to associate + with the new share. + </para></listitem> + </itemizedlist> + + <para> + This parameter is only used modify existing file shares definitions. To modify + printer shares, use the "Printers..." folder as seen when browsing the Samba host. + </para> + + <para> + See also <link linkend="ADDSHARECOMMAND"><parameter>add share + command</parameter></link>, <link linkend="DELETESHARECOMMAND"><parameter>delete + share command</parameter></link>. + </para> + + <para>Default: <emphasis>none</emphasis></para> + <para>Example: <command>change share command = /usr/local/bin/addshare</command></para> + </listitem> + </varlistentry> + + <varlistentry> <term><anchor id="CHARACTERSET">character set (G)</term> @@ -1545,6 +1656,11 @@ mode bits on created directories. See also the <link linkend="INHERITPERMISSIONS"> <parameter>inherit permissions</parameter></link> parameter.</para> + <para>Note that this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + a mask on access control lists also, they need to set the <link + linkend="SECURITYMASK"><parameter>security mask</parameter></link>.</para> + <para>Default: <command>create mask = 0744</command></para> <para>Example: <command>create mask = 0775</command></para></listitem> </varlistentry> @@ -1648,15 +1764,9 @@ <varlistentry> <term><anchor id="DEBUGLEVEL">debuglevel (G)</term> - <listitem><para>The value of the parameter (an integer) allows - the debug level (logging level) to be specified in the - <filename>smb.conf</filename> file. This is to give greater - flexibility in the configuration of the system.</para> - - <para>The default will be the debug level specified on - the command line or level zero if none was specified.</para> - - <para>Example: <command>debug level = 3</command></para></listitem> + <listitem><para>Synonym for <link linkend="LOGLEVEL"><parameter> + log level</parameter></link>.</para> + </listitem> </varlistentry> @@ -1721,6 +1831,48 @@ <varlistentry> + <term><anchor id="DELETEPRINTERCOMMAND">delete printer command (G)</term> + <listitem><para>With the introduction of MS-RPC based printer + support for Windows NT/2000 clients in Samba 2.2, it is now + possible to delete printer at run time by issuing the + DeletePrinter() RPC call.</para> + + <para>For a Samba host this means that the printer must be + physically deleted from underlying printing system. The <parameter> + deleteprinter command</parameter> defines a script to be run which + will perform the necessary operations for removing the printer + from the print system and from <filename>smb.conf</filename>. + </para> + + <para>The <parameter>delete printer command</parameter> is + automatically called with only one parameter: <parameter> + "printer name"</parameter>.</para> + + + <para>Once the <parameter>delete printer command</parameter> has + been executed, <command>smbd</command> will reparse the <filename> + smb.conf</filename> to associated printer no longer exists. + If the sharename is still valid, then <command>smbd + </command> will return an ACCESS_DENIED error to the client.</para> + + <para>See also <link linkend="ADDPRINTERCOMMAND"><parameter> + add printer command</parameter></link>, <link + linkend="printing"><parameter>printing</parameter></link>, + <link linkend="SHOWADDPRINTERWIZARD"><parameter>show add + printer wizard</parameter></link></para> + + <para>Default: <emphasis>none</emphasis></para> + <para>Example: <command>deleteprinter command = /usr/bin/removeprinter + </command></para> + </listitem> + </varlistentry> + + + + + + + <varlistentry> <term><anchor id="DELETEREADONLY">delete readonly (S)</term> <listitem><para>This parameter allows readonly files to be deleted. This is not normal DOS semantics, but is allowed by UNIX.</para> @@ -1733,6 +1885,53 @@ </varlistentry> + + <varlistentry> + <term><anchor id="DELETESHARECOMMAND">delete share command (G)</term> + <listitem><para>Samba 2.2.0 introduced the ability to dynamically + add and delete shares via the Windows NT 4.0 Server Manager. The + <parameter>delete share command</parameter> is used to define an + external program or script which will remove an existing service + definition from <filename>smb.conf</filename>. In order to successfully + execute the <parameter>delete share command</parameter>, <command>smbd</command> + requires that the administrator be connected using a root account (i.e. + uid == 0). + </para> + + <para> + When executed, <command>smbd</command> will automatically invoke the + <parameter>delete share command</parameter> with two parameters. + </para> + + <itemizedlist> + <listitem><para><parameter>configFile</parameter> - the location + of the global <filename>smb.conf</filename> file. + </para></listitem> + + <listitem><para><parameter>shareName</parameter> - the name of + the existing service. + </para></listitem> + </itemizedlist> + + <para> + This parameter is only used to remove file shares. To delete printer shares, + see the <link linkend="DELETEPRINTERCOMMAND"><parameter>delete printer + command</parameter></link>. + </para> + + <para> + See also <link linkend="ADDSHARECOMMAND"><parameter>delete share + command</parameter></link>, <link linkend="CHANGESHARECOMMAND"><parameter>change + share</parameter></link>. + </para> + + <para>Default: <emphasis>none</emphasis></para> + <para>Example: <command>delete share command = /usr/local/bin/delshare</command></para> + + </listitem> + </varlistentry> + + <varlistentry> @@ -1797,46 +1996,6 @@ - <varlistentry> - <term><anchor id="DELETEPRINTERCOMMAND">deleteprinter command (G)</term> - <listitem><para>With the introduction of MS-RPC based printer - support for Windows NT/2000 clients in Samba 2.2, it is now - possible to delete printer at run time by issuing the - DeletePrinter() RPC call.</para> - - <para>For a Samba host this means that the printer must be - physically deleted from underlying printing system. The <parameter> - deleteprinter command</parameter> defines a script to be run which - will perform the necessary operations for removing the printer - from the print system and from <filename>smb.conf</filename>. - </para> - - <para>The <parameter>deleteprinter command</parameter> is - automatically called with only one parameter: <parameter> - "printer name"</parameter>.</para> - - - <para>Once the <parameter>deleteprinter command</parameter> has - been executed, <command>smbd</command> will reparse the <filename> - smb.conf</filename> to associated printer no longer exists. - If the sharename is still valid, then <command>smbd - </command> will return an ACCESS_DENIED error to the client.</para> - - <para>See also <link linkend="ADDPRINTERCOMMAND"><parameter> - addprinter command</parameter></link>, <link - linkend="printing"><parameter>printing</parameter></link>, - <link linkend="SHOWADDPRINTERWIZARD"><parameter>show add - printer wizard</parameter></link></para> - - <para>Default: <emphasis>none</emphasis></para> - <para>Example: <command>deleteprinter command = /usr/bin/removeprinter - </command></para> - </listitem> - </varlistentry> - - - - <varlistentry> <term><anchor id="DELETEVETOFILES">delete veto files (S)</term> @@ -1962,6 +2121,11 @@ </parameter></link> parameter. This parameter is set to 000 by default (i.e. no extra mode bits are added).</para> + <para>Note that this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + a mask on access control lists also, they need to set the <link + linkend="DIRECTORYSECURITYMASK"><parameter>directory security mask</parameter></link>.</para> + <para>See the <link linkend="FORCEDIRECTORYMODE"><parameter>force directory mode</parameter></link> parameter to cause particular mode bits to always be set on created directories.</para> @@ -2002,17 +2166,15 @@ mask may be treated as a set of bits the user is not allowed to change.</para> - <para>If not set explicitly this parameter is set to the same - value as the <link linkend="DIRECTORYMASK"><parameter>directory - mask</parameter></link> parameter. To allow a user to - modify all the user/group/world permissions on a directory, set - this parameter to 0777.</para> + <para>If not set explicitly this parameter is set to 0777 + meaning a user is allowed to modify all the user/group/world + permissions on a directory.</para> <para><emphasis>Note</emphasis> that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. - Administrators of most normal systems will probably want to set - it to 0777.</para> + Administrators of most normal systems will probably want to leave + it as the default of 0777.</para> <para>See also the <link linkend="FORCEDIRECTORYSECURITYMODE"><parameter> force directory security mode</parameter></link>, <link @@ -2020,9 +2182,8 @@ <link linkend="FORCESECURITYMODE"><parameter>force security mode </parameter></link> parameters.</para> - <para>Default: <command>directory security mask = <same as - directory mask></command></para> - <para>Example: <command>directory security mask = 0777</command></para> + <para>Default: <command>directory security mask = 0777</command></para> + <para>Example: <command>directory security mask = 0700</command></para> </listitem> </varlistentry> @@ -2054,67 +2215,47 @@ <varlistentry> <term><anchor id="DOMAINADMINGROUP">domain admin group (G)</term> - <listitem><para>This is an <emphasis>EXPERIMENTAL</emphasis> parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list <ulink - url="mailto:samba-ntdom@samba.org">samba-ntdom</ulink> available by - visiting the web page at <ulink url="http://lists.samba.org/"> - http://lists.samba.org/</ulink>.</para></listitem> - </varlistentry> - - - <varlistentry> - <term><anchor id="DOMAINADMINUSERS">domain admin users (G)</term> - <listitem><para>This is an <emphasis>EXPERIMENTAL</emphasis> parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list <ulink - url="mailto:samba-ntdom@samba.org">samba-ntdom</ulink> available by - visiting the web page at <ulink url="http://lists.samba.org/"> - http://lists.samba.org/</ulink>.</para></listitem> + <listitem><para>This parameter is intended as a temporary solution + to enable users to be a member of the "Domain Admins" group when + a Samba host is acting as a PDC. A complete solution will be provided + by a system for mapping Windows NT/2000 groups onto UNIX groups. + Please note that this parameter has a somewhat confusing name. It + accepts a list of usernames and of group names in standard + <filename>smb.conf</filename> notation. + </para> + + <para>See also <link linkend="DOMAINGUESTGROUP"><parameter>domain + guest group</parameter></link>, <link linkend="DOMAINLOGONS"><parameter>domain + logons</parameter></link> + </para> + + <para>Default: <emphasis>no domain administrators</emphasis></para> + <para>Example: <command>domain admin group = root @wheel</command></para> + </listitem> </varlistentry> - <varlistentry> - <term><anchor id="DOMAINGROUPS">domain groups (G)</term> - <listitem><para>This is an <emphasis>EXPERIMENTAL</emphasis> parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list <ulink - url="mailto:samba-ntdom@samba.org">samba-ntdom</ulink> available by - visiting the web page at <ulink url="http://lists.samba.org/"> - http://lists.samba.org/</ulink>.</para></listitem> - </varlistentry> - <varlistentry> <term><anchor id="DOMAINGUESTGROUP">domain guest group (G)</term> - <listitem><para>This is an <emphasis>EXPERIMENTAL</emphasis> parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list <ulink - url="mailto:samba-ntdom@samba.org">samba-ntdom</ulink> available by - visiting the web page at <ulink url="http://lists.samba.org/"> - http://lists.samba.org/</ulink>.</para></listitem> - </varlistentry> - - - <varlistentry> - <term><anchor id="DOMAINGUESTUSERS">domain guest users (G)</term> - <listitem><para>This is an <emphasis>EXPERIMENTAL</emphasis> parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list <ulink - url="mailto:samba-ntdom@samba.org">samba-ntdom</ulink> available by - visiting the web page at <ulink url="http://lists.samba.org/"> - http://lists.samba.org/</ulink>.</para></listitem> + <listitem><para>This parameter is intended as a temporary solution + to enable users to be a member of the "Domain Guests" group when + a Samba host is acting as a PDC. A complete solution will be provided + by a system for mapping Windows NT/2000 groups onto UNIX groups. + Please note that this parameter has a somewhat confusing name. It + accepts a list of usernames and of group names in standard + <filename>smb.conf</filename> notation. + </para> + + <para>See also <link linkend="DOMAINADMINGROUP"><parameter>domain + admin group</parameter></link>, <link linkend="DOMAINLOGONS"><parameter>domain + logons</parameter></link> + </para> + + <para>Default: <emphasis>no domain guests</emphasis></para> + <para>Example: <command>domain guest group = nobody @guest</command></para> + </listitem> </varlistentry> @@ -2431,6 +2572,12 @@ mode after the mask set in the <parameter>create mask</parameter> parameter is applied.</para> + <para>Note that by default this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + this mask on access control lists also, they need to set the <link + linkend="RESTRICTACLWITHMASK"><parameter>restrict acl with + mask</parameter></link> to true.</para> + <para>See also the parameter <link linkend="CREATEMASK"><parameter>create mask</parameter></link> for details on masking mode bits on files.</para> @@ -2459,6 +2606,12 @@ mask in the parameter <parameter>directory mask</parameter> is applied.</para> + <para>Note that by default this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + this mask on access control lists also, they need to set the <link + linkend="RESTRICTACLWITHMASK"><parameter>restrict acl with + mask</parameter></link> to true.</para> + <para>See also the parameter <link linkend="DIRECTORYMASK"><parameter> directory mask</parameter></link> for details on masking mode bits on created directories.</para> @@ -2490,17 +2643,15 @@ mask may be treated as a set of bits that, when modifying security on a directory, the user has always set to be 'on'.</para> - <para>If not set explicitly this parameter is set to the same - value as the <link linkend="FORCEDIRECTORYMODE"><parameter>force - directory mode</parameter></link> parameter. To allow - a user to modify all the user/group/world permissions on a - directory without restrictions, set this parameter to 000.</para> + <para>If not set explicitly this parameter is 000, which + allows a user to modify all the user/group/world permissions on a + directory without restrictions.</para> <para><emphasis>Note</emphasis> that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. - Administrators of most normal systems will probably want to set - it to 0000.</para> + Administrators of most normal systems will probably want to leave + it set as 0000.</para> <para>See also the <link linkend="DIRECTORYSECURITYMASK"><parameter> directory security mask</parameter></link>, <link linkend="SECURITYMASK"> @@ -2508,9 +2659,8 @@ <link linkend="FORCESECURITYMODE"><parameter>force security mode </parameter></link> parameters.</para> - <para>Default: <command>force directory security mode = <same as - force directory mode></command></para> - <para>Example: <command>force directory security mode = 0</command></para> + <para>Default: <command>force directory security mode = 0</command></para> + <para>Example: <command>force directory security mode = 700</command></para> </listitem> </varlistentry> @@ -2568,17 +2718,15 @@ mask may be treated as a set of bits that, when modifying security on a file, the user has always set to be 'on'.</para> - <para>If not set explicitly this parameter is set to the same - value as the <link linkend="FORCECREATEMODE"><parameter>force - create mode</parameter></link> parameter. To allow a user to - modify all the user/group/world permissions on a file, with no - restrictions set this parameter to 000.</para> + <para>If not set explicitly this parameter is set to 0, + and allows a user to modify all the user/group/world permissions on a file, + with no restrictions.</para> <para><emphasis>Note</emphasis> that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. - Administrators of most normal systems will probably want to set - it to 0000.</para> + Administrators of most normal systems will probably want to leave + this set to 0000.</para> <para>See also the <link linkend="FORCEDIRECTORYSECURITYMODE"><parameter> force directory security mode</parameter></link>, @@ -2586,9 +2734,8 @@ mask</parameter></link>, <link linkend="SECURITYMASK"><parameter> security mask</parameter></link> parameters.</para> - <para>Default: <command>force security mode = <same as force - create mode></command></para> - <para>Example: <command>force security mode = 0</command></para> + <para>Default: <command>force security mode = 0</command></para> + <para>Example: <command>force security mode = 700</command></para> </listitem> </varlistentry> @@ -3340,9 +3487,15 @@ <varlistentry> <term><anchor id="LOGLEVEL">log level (G)</term> - <listitem><para>Synonym for <link linkend="DEBUGLEVEL"><parameter> - debug level</parameter></link>.</para> - </listitem> + <listitem><para>The value of the parameter (an integer) allows + the debug level (logging level) to be specified in the + <filename>smb.conf</filename> file. This is to give greater + flexibility in the configuration of the system.</para> + + <para>The default will be the log level specified on + the command line or level zero if none was specified.</para> + + <para>Example: <command>log level = 3</command></para></listitem> </varlistentry> @@ -4580,6 +4733,28 @@ + + <varlistentry> + <term><anchor id="OBEYPAMRESTRICTIONS">obey pam restrictions (G)</term> + <listitem><para>When Samba 2.2 is configure to enable PAM support + (i.e. --with-pam), this parameter will control whether or not Samba + should obey PAM's account and session management directives. The + default behavior is to use PAM for clear text authentication only + and to ignore any account or session management. Note that Samba + always ignores PAM for authentication in the case of <link + linkend="ENCRYPTPASSWORDS"><parameter>encrypt passwords = yes</parameter> + </link>. The reason is that PAM modules cannot support the challenge/response + authentication mechanism needed in the presence of SMB password encryption. + </para> + + <para>Default: <command>obey pam restrictions = no</command></para> + </listitem> + </varlistentry> + + + + + <varlistentry> <term><anchor id="ONLYUSER">only user (S)</term> <listitem><para>This is a boolean option that controls whether @@ -4608,24 +4783,6 @@ - - <varlistentry> - <term><anchor id="OLELOCKINGCOMPATIBILITY">ole locking compatibility (G)</term> - <listitem><para>This parameter allows an administrator to turn - off the byte range lock manipulation that is done within Samba to - give compatibility for OLE applications. Windows OLE applications - use byte range locking as a form of inter-process communication, by - locking ranges of bytes around the 2^32 region of a file range. This - can cause certain UNIX lock managers to crash or otherwise cause - problems. Setting this parameter to <constant>no</constant> means you - trust your UNIX lock manager to handle such cases correctly.</para> - - <para>Default: <command>ole locking compatibility = yes</command></para> - </listitem> - </varlistentry> - - - <varlistentry> <term><anchor id="ONLYGUEST">only guest (S)</term> <listitem><para>A synonym for <link linkend="GUESTONLY"><parameter> @@ -4755,6 +4912,21 @@ </varlistentry> + <varlistentry> + <term><anchor id="PAMPASSWORDCHANGE">pam password change (G)</term> + <listitem><para>With the addition of better PAM support in Samba 2.2, + this parameter, it is possible to use PAM's password change control + flag for Samba. If enabled, then PAM will be used for password + changes when requested by an SMB client, and the <link + linkend="PASSWDCHAT"><parameter>passwd chat</parameter></link> must be + be changed to work with the pam prompts. + </para> + + <para>Default: <command>pam password change = no</command></para> + + </listitem> + </varlistentry> + <varlistentry> <term><anchor id="PANICACTION">panic action (G)</term> @@ -4810,10 +4982,21 @@ password cleartext. In this case the old password cleartext is set to "" (the empty string).</para> + <para>Also, if the <link linkend="PAMPASSWORDCHANGE"><parameter>pam + password change</parameter></link> parameter is set to true, then the + chat sequence should consist of three elements. The first element should + match the pam prompt for the old password, the second element should match + the pam prompt for the first request for the new password, and the final + element should match the pam prompt for the second request for the new password. + These matches are done case insentively. Under most conditions this change + is done as root so the prompt for the old password will never be matched. + </para> + <para>See also <link linkend="UNIXPASSWORDSYNC"><parameter>unix password sync</parameter></link>, <link linkend="PASSWDPROGRAM"><parameter> - passwd program</parameter></link> and <link linkend="PASSWDCHATDEBUG"> - <parameter>passwd chat debug</parameter></link>.</para> + passwd program</parameter></link> ,<link linkend="PASSWDCHATDEBUG"> + <parameter>passwd chat debug</parameter></link> and <link linkend="PAMPASSWORDCHANGE"> + <parameter>pam password change</parameter></link>.</para> <para>Default: <command>passwd chat = *new*password* %n\n *new*password* %n\n *changed*</command></para> @@ -5799,6 +5982,35 @@ <varlistentry> + <term><anchor id="RESTRICTACLWITHMASK">restrict acl with mask (S)</term> + <listitem><para>This is a boolean parameter. If set to false (default), then + Creation of files with access control lists (ACLS) and modification of ACLs + using the Windows NT/2000 ACL editor will be applied directly to the file + or directory.</para> + + <para>If set to True, then all requests to set an ACL on a file will have the + parameters <link linkend="CREATEMASK"><parameter>create mask</parameter></link>, + <link linkend="FORCECREATEMODE"><parameter>force create mode</parameter></link> + applied before setting the ACL, and all requests to set an ACL on a directory will + have the parameters <link linkend="DIRECTORYMASK"><parameter>directory + mask</parameter></link>, <link linkend="FORCEDIRECTORYMODE"><parameter>force + directory mode</parameter></link> applied before setting the ACL. + </para> + + <para>See also <link linkend="CREATEMASK"><parameter>create mask</parameter></link>, + <link linkend="FORCECREATEMODE"><parameter>force create mode</parameter></link>, + <link linkend="DIRECTORYMASK"><parameter>directory mask</parameter></link>, + <link linkend="FORCEDIRECTORYMODE"><parameter>force directory mode</parameter></link> + </para> + + <para>Default: <command>restrict acl with mask = no</command></para> + </listitem> + </varlistentry> + + + + + <varlistentry> <term><anchor id="RESTRICTANONYMOUS">restrict anonymous (G)</term> <listitem><para>This is a boolean parameter. If it is true, then anonymous access to the server will be restricted, namely in the @@ -6176,17 +6388,15 @@ mask may be treated as a set of bits the user is not allowed to change.</para> - <para>If not set explicitly this parameter is set to the same - value as the <link linkend="CREATEMASK"><parameter>create mask - </parameter></link> parameter. To allow a user to modify all the - user/group/world permissions on a file, set this parameter to - 0777.</para> + <para>If not set explicitly this parameter is 0777, allowing + a user to modify all the user/group/world permissions on a file. + </para> <para><emphasis>Note</emphasis> that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will - probably want to set it to 0777.</para> + probably want to leave it set to 0777.</para> <para>See also the <link linkend="FORCEDIRECTORYSECURITYMODE"> <parameter>force directory security mode</parameter></link>, @@ -6194,9 +6404,8 @@ security mask</parameter></link>, <link linkend="FORCESECURITYMODE"> <parameter>force security mode</parameter></link> parameters.</para> - <para>Default: <command>security mask = <same as create mask> - </command></para> - <para>Example: <command>security mask = 0777</command></para> + <para>Default: <command>security mask = 0777</command></para> + <para>Example: <command>security mask = 0770</command></para> </listitem> </varlistentry> diff --git a/docs/docbook/manpages/smbcontrol.1.sgml b/docs/docbook/manpages/smbcontrol.1.sgml index 44418ea85f..8e529d8b71 100644 --- a/docs/docbook/manpages/smbcontrol.1.sgml +++ b/docs/docbook/manpages/smbcontrol.1.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="findsmb"> +<refentry id="smbcontrol"> <refmeta> <refentrytitle>smbcontrol</refentrytitle> diff --git a/docs/docbook/manpages/smbspool.8.sgml b/docs/docbook/manpages/smbspool.8.sgml index b847aadd05..5b409bb9de 100644 --- a/docs/docbook/manpages/smbspool.8.sgml +++ b/docs/docbook/manpages/smbspool.8.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="findsmb"> +<refentry id="smbspool"> <refmeta> <refentrytitle>smbspool</refentrytitle> @@ -8,7 +8,7 @@ <refnamediv> - <refname>nmblookup</refname> + <refname>smbspool</refname> <refpurpose>send print file to an SMB printer</refpurpose> </refnamediv> diff --git a/docs/docbook/manpages/smbstatus.1.sgml b/docs/docbook/manpages/smbstatus.1.sgml index 6f2361d021..c2f638b88e 100644 --- a/docs/docbook/manpages/smbstatus.1.sgml +++ b/docs/docbook/manpages/smbstatus.1.sgml @@ -1,5 +1,5 @@ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -<refentry id="findsmb"> +<refentry id="smbstatus"> <refmeta> <refentrytitle>smbstatus</refentrytitle> diff --git a/docs/docbook/projdoc/CVS-Access.sgml b/docs/docbook/projdoc/CVS-Access.sgml new file mode 100644 index 0000000000..aea146b66a --- /dev/null +++ b/docs/docbook/projdoc/CVS-Access.sgml @@ -0,0 +1,157 @@ +<chapter> + + +<chapterinfo> + <author> + <affiliation> + <orgname>Samba Team</orgname> + </affiliation> + </author> + + + <pubdate> (22 May 2001) </pubdate> +</chapterinfo> + +<title>HOWTO Access Samba source code via CVS</title> + +<sect1> +<title>Introduction</title> + +<para> +Samba is developed in an open environnment. Developers use CVS +(Concurrent Versioning System) to "checkin" (also known as +"commit") new source code. Samba's various CVS branches can +be accessed via anonymouns CVS using the instructions +detailed in this chapter. +</para> + +<para> +This document is a modified version of the instructions found at +<ulink url="http://samba.org/samba/cvs.html">http://samba.org/samba/cvs.html</ulink> +</para> + +</sect1> + + +<sect1> +<title>CVS Access to samba.org</title> + +<para> +The machine samba.org runs a publicly accessible CVS +repository for access to the source code of several packages, +including samba, rsync and jitterbug. There are two main ways of +accessing the CVS server on this host. +</para> + +<sect2> +<title>Access via CVSweb</title> + +<para> +You can access the source code via your +favourite WWW browser. This allows you to access the contents of +individual files in the repository and also to look at the revision +history and commit logs of individual files. You can also ask for a diff +listing between any two versions on the repository. +</para> + +<para> +Use the URL : <ulink +url="http://samba.org/cgi-bin/cvsweb">http://samba.org/cgi-bin/cvsweb</ulink> +</para> +</sect2> + +<sect2> +<title>Access via cvs</title> + +<para> +You can also access the source code via a +normal cvs client. This gives you much more control over you can +do with the repository and allows you to checkout whole source trees +and keep them uptodate via normal cvs commands. This is the +preferred method of access if you are a developer and not +just a casual browser. +</para> + +<para> +To download the latest cvs source code, point your +browser at the URL : <ulink url="http://www.cyclic.com/">http://www.cyclic.com/</ulink>. +and click on the 'How to get cvs' link. CVS is free software under +the GNU GPL (as is Samba). Note that there are several graphical CVS clients +which provide a graphical interface to the sometimes mundane CVS commands. +Links to theses clients are also available from http://www.cyclic.com. +</para> + +<para> +To gain access via anonymous cvs use the following steps. +For this example it is assumed that you want a copy of the +samba source code. For the other source code repositories +on this system just substitute the correct package name +</para> + +<orderedlist> +<listitem> + <para> + Install a recent copy of cvs. All you really need is a + copy of the cvs client binary. + </para> +</listitem> + + +<listitem> + <para> + Run the command + </para> + + <para> + <command>cvs -d :pserver:cvs@samba.org:/cvsroot login</command> + </para> + + <para> + When it asks you for a password type <userinput>cvs</userinput>. + </para> +</listitem> + + +<listitem> + <para> + Run the command + </para> + + <para> + <command>cvs -d :pserver:cvs@samba.org:/cvsroot co samba</command> + </para> + + <para> + This will create a directory called samba containing the + latest samba source code (i.e. the HEAD tagged cvs branch). This + currently corresponds to the 3.0 development tree. + </para> + + <para> + CVS branches other HEAD can be obtained by using the <parameter>-r</parameter> + and defining a tag name. A list of branch tag names can be found on the + "Development" page of the samba web site. A common request is to obtain the + latest 2.2 release code. This could be done by using the following command. + </para> + + <para> + <command>cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba</command> + </para> +</listitem> + +<listitem> + <para> + Whenever you want to merge in the latest code changes use + the following command from within the samba directory: + </para> + + <para> + <command>cvs update -d -P</command> + </para> +</listitem> +</orderedlist> + +</sect2> +</sect1> + +</chapter> diff --git a/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml b/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml index 699ba54a09..0b86bcba63 100644 --- a/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml +++ b/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml @@ -8,17 +8,46 @@ <orgname>VA Linux Systems/Samba Team</orgname> <address><email>jerry@samba.org</email></address> </affiliation> + <firstname>David</firstname><surname>Bannon</surname> + <affiliation> + <orgname>Samba Team</orgname> + <address><email>dbannon@samba.org</email></address> + </affiliation> + </author> - <pubdate> (15 Apr 2001) </pubdate> + <pubdate> (26 Apr 2001) </pubdate> </chapterinfo> <title> -How to Configure Samba 2.2.x as a Primary Domain Controller +How to Configure Samba 2.2 as a Primary Domain Controller </title> <!-- ********************************************************** + Prerequisite Reading + +*************************************************************** --> +<sect1> +<title>Prerequisite Reading</title> + +<para> +Before you continue readingin this chapter, please make sure +that you are comfortable with configuring basic files services +in smb.conf and how to enable and administrate password +encryption in Samba. Theses two topics are covered in the +<ulink url="smb.conf.5.html"><filename>smb.conf(5)</filename></ulink> +manpage and the <ulink url="EMCRYPTION.html">Encryption chapter</ulink> +of this HOWTO Collection. +</para> + + +</sect1> + + + +<!-- ********************************************************** + Background Information *************************************************************** --> @@ -27,44 +56,82 @@ How to Configure Samba 2.2.x as a Primary Domain Controller Background </title> -<para><emphasis>Author's Note :</emphasis> This document -is a combination of David Bannon's Samba 2.2 PDC HOWTO -and the Samba NT Domain FAQ. Both documents are superceeded by this one. +<note> +<para> +<emphasis>Author's Note :</emphasis> This document is a combination +of David Bannon's Samba 2.2 PDC HOWTO and the Samba NT Domain FAQ. +Both documents are superceeded by this one. </para> +</note> <para> Version of Samba prior to release 2.2 had marginal capabilities to -act as a Windows NT 4.0 Primary Domain Controller (PDC). The following -functionality should work in 2.2.0: +act as a Windows NT 4.0 Primary Domain Controller (PDC). Beginning with +Samba 2.2.0, we are proud to announce official support for Windows NT 4.0 +style domain logons from Windows NT 4.0 (through SP6) and Windows 2000 (through +SP1) clients. This article outlines the steps necessary for configuring Samba +as a PDC. It is necessary to have a working Samba server prior to implementing the +PDC functionality. If you have not followed the steps outlined in +<ulink url="UNIX_INSTALL.html"> UNIX_INSTALL.html</ulink>, please make sure +that your server is configured correctly before proceeding. Another good +resource in the <ulink url="smb.conf.5.html">smb.conf(5) man +page</ulink>. The following functionality should work in 2.2: </para> <itemizedlist> - <listitem><para>domain logons for Windows NT 4.0/2000 clients</para></listitem> + <listitem><para> + domain logons for Windows NT 4.0/2000 clients. + </para></listitem> - <listitem><para>placing a Windows 9x client in user level security</para></listitem> + <listitem><para> + placing a Windows 9x client in user level security + </para></listitem> - <listitem><para>retrieving a list of users and groups from a Samba PDC to - Windows 9x/NT/2000 clients </para></listitem> + <listitem><para> + retrieving a list of users and groups from a Samba PDC to + Windows 9x/NT/2000 clients + </para></listitem> - <listitem><para>roving user profiles</para></listitem> + <listitem><para> + roving (roaming) user profiles + </para></listitem> - <listitem><para>Windows NT 4.0 style system policies</para></listitem> + <listitem><para> + Windows NT 4.0 style system policies + </para></listitem> </itemizedlist> +<warning> + <title>Windows 2000 Service Pack 2 Clients</title> + <para> + Samba 2.2.1 is required for PDC functionality when using Windows 2000 + SP2 clients. + </para> +</warning> + + <para> The following pieces of functionality are not included in the 2.2 release: </para> <itemizedlist> - <listitem><para>Windows NT 4 domain trusts</para></listitem> + <listitem><para> + Windows NT 4 domain trusts + </para></listitem> - <listitem><para>Sam replication with Windows NT 4.0 Domain Controllers - (i.e. a Samba PDC and a Windows NT BDC or vice versa) </para></listitem> + <listitem><para> + SAM replication with Windows NT 4.0 Domain Controllers + (i.e. a Samba PDC and a Windows NT BDC or vice versa) + </para></listitem> - <listitem><para>Adding users via the User Manager for Domains</para></listitem> + <listitem><para> + Adding users via the User Manager for Domains + </para></listitem> - <listitem><para>Acting as a Windows 2000 Domain Controller (i.e. Kerberos - and Active Directory)</para></listitem> + <listitem><para> + Acting as a Windows 2000 Domain Controller (i.e. Kerberos and + Active Directory) + </para></listitem> </itemizedlist> <para> @@ -75,19 +142,6 @@ from NT4 domain logons and has been officially supported for some time. </para> -<para> -Beginning with Samba 2.2.0, we are proud to announce official -support for Windows NT 4.0 style domain logons from Windows NT -4.0 and Windows 2000 (including SP1) clients. This article -outlines the steps necessary for configuring Samba as a PDC. -Note that it is necessary to have a working Samba server -prior to implementing the PDC functionality. If you have not -followed the steps outlined in <ulink url="UNIX_INSTALL.html"> -UNIX_INSTALL.html</ulink>, please make sure that your server -is configured correctly before proceeding. Another good -resource in the <ulink url="smb.conf.5.html">smb.conf(5) man -page</ulink>. -</para> <para> Implementing a Samba PDC can basically be divided into 2 broad @@ -95,11 +149,14 @@ steps. </para> <orderedlist numeration="Arabic"> - <listitem><para>Configuring the Samba Domain Controller + <listitem><para> + Configuring the Samba PDC </para></listitem> - <listitem><para>Creating machine trust accounts - and joining clients to the domain</para></listitem> + <listitem><para> + Creating machine trust accounts and joining clients + to the domain + </para></listitem> </orderedlist> <para> @@ -164,7 +221,7 @@ Here is an example smb.conf for acting as a PDC: <ulink url="smb.conf.5.html#LOGONHOME">logon home</ulink> = \\homeserver\%u ; specify a generic logon script for all users - ; this is a relative path to the [netlogon] share + ; this is a relative **DOS** path to the [netlogon] share <ulink url="smb.conf.5.html#LOGONSCRIPT">logon script</ulink> = logon.cmd ; necessary share for domain controller @@ -182,28 +239,32 @@ Here is an example smb.conf for acting as a PDC: </programlisting></para> <para> -There are a couple of points to emphasize in the above -configuration. +There are a couple of points to emphasize in the above configuration. </para> <itemizedlist> - <listitem><para>encrypted passwords must be enabled. - For more details on how to do this, refer to - <ulink url="ENCRYPTION.html">ENCRYPTION.html</ulink>. + <listitem><para> + Encrypted passwords must be enabled. For more details on how + to do this, refer to <ulink url="ENCRYPTION.html">ENCRYPTION.html</ulink>. </para></listitem> - <listitem><para>The server must support domain logons - and a <filename>[netlogon]</filename> share</para></listitem> + <listitem><para> + The server must support domain logons and a + <filename>[netlogon]</filename> share + </para></listitem> - <listitem><para>The server must be the domain master browser - in order for Windows client to locate the server as a DC.</para> - </listitem> + <listitem><para> + The server must be the domain master browser in order for Windows + client to locate the server as a DC. Please refer to the various + Network Browsing documentation included with this distribution for + details. + </para></listitem> </itemizedlist> <para> As Samba 2.2 does not offer a complete implementation of group mapping between Windows NT groups and UNIX groups (this is really quite complicated to explain -in a short space), you should refer to the <ulink url="smb.conf.5.html#DOMAINADMONUSERS">domain +in a short space), you should refer to the <ulink url="smb.conf.5.html#DOMAINADMINUSERS">domain admin users</ulink> and <ulink url="smb.conf.5.html#DOMAINADMINGROUP">domain admin group</ulink> smb.conf parameters for information of creating a Domain Admins style accounts. @@ -217,24 +278,28 @@ style accounts. to the Domain</title> <para> -First you must understand what a machine trust account is and what -it is used for. -</para> - -<para> -A machine trust account is a user account owned by a computer. +A machine trust account is a samba user account owned by a computer. The account password acts as the shared secret for secure -communication with the Domain Controller. Hence the reason that -a Windows 9x host is never a true member of a domain because -it does not posses a machine trust account and thus has no shared -secret with the DC. +communication with the Domain Controller. This is a security feature +to prevent an unauthorized machine with the same netbios name from +joining the domain and gaining access to domain user/group accounts. +Hence a Windows 9x host is never a true member of a domain because it does +not posses a machine trust account, and thus has no shared secret with the DC. </para> <para> On a Windows NT PDC, these machine trust account passwords are stored -in the registry. A Samba PDC stores these accounts in he same location +in the registry. A Samba PDC stores these accounts in the same location as user LanMan and NT password hashes (currently <filename>smbpasswd</filename>). -However, machine trust accounts only possess the NT password hash. +However, machine trust accounts only possess and use the NT password hash. +</para> + +<para> +Because Samba requires machine accounts to possess a UNIX uid from +which an Windows NT SID can be generated, all of these accounts +must have an entry in <filename>/etc/passwd</filename> and smbpasswd. +Future releases will alleviate the need to create +<filename>/etc/passwd</filename> entries. </para> <para> @@ -242,25 +307,35 @@ There are two means of creating machine trust accounts. </para> <itemizedlist> - <listitem><para>Manual creation before joining the client - to the domain. In this case, the password is set to a known - value -- the lower case of the machine's netbios name.</para></listitem> + <listitem><para> + Manual creation before joining the client to the domain. In this case, + the password is set to a known value -- the lower case of the + machine's netbios name. + </para></listitem> - <listitem><para>Creation of the account at the time of - joining the domain. In this case, the session key of the - administrative account used to join the client to the domain acts - as an encryption key for setting the password to a random value.</para> - </listitem> + <listitem><para> + Creation of the account at the time of joining the domain. In + this case, the session key of the administrative account used to join + the client to the domain acts as an encryption key for setting the + password to a random value (This is the recommended method). + </para></listitem> </itemizedlist> +<sect2> +<title>Manually creating machine trust accounts</title> + <para> -Because Samba requires machine accounts to possess a UNIX uid from -which an Windows NT SID can be generated, all of these accounts -will have an entry in <filename>/etc/passwd</filename> and smbpasswd. -Future releases will alleviate the need to create -<filename>/etc/passwd</filename> entries. +The first step in creating a machine trust account by hand is to +create an entry for the machine in /etc/passwd. This can be done +using <command>vipw</command> or any 'add userr' command which is normally +used to create new UNIX accounts. The following is an example for a Linux +based Samba server: </para> +<para> +<prompt>root# </prompt>/usr/sbin/useradd -g 100 -d /dev/null -c <replaceable> +machine_nickname</replaceable> -m -s /bin/false <replaceable>machine_name</replaceable>$ +</para> <para> The <filename>/etc/passwd</filename> entry will list the machine name @@ -270,39 +345,60 @@ home directory. For example a machine called 'doppy' would have an </para> <para><programlisting> -doppy$:x:505:501:NTMachine:/dev/null:/bin/false +doppy$:x:505:501:<replaceable>machine_nickname</replaceable>:/dev/null:/bin/false </programlisting></para> <para> -If you are manually creating the machine accounts, it is necessary -to add the <filename>/etc/passwd</filename> (or NIS passwd -map) entry prior to adding the <filename>smbpasswd</filename> -entry. The following command will create a new machine account -ready for use. +Above, <replaceable>machine_nickname</replaceable> can be any descriptive name for the +pc i.e. BasementComputer. The <replaceable>machine_name</replaceable> absolutely must be +the netbios name of the pc to be added to the domain. The "$" must append the netbios +name of the pc or samba will not recognize this as a machine account </para> + <para> -<prompt>root# </prompt> smbpasswd -a -m <replaceable>machine_name</replaceable> +Now that the UNIX account has been created, the next step is to create +the smbpasswd entry for the machine containing the well known initial +trust account password. This can be done using the <ulink +url="smbpasswd.6.html"><command>smbpasswd(8)</command></ulink> command +as shown here: </para> <para> -where <replaceable>machine_name</replaceable> is the machine's netbios -name. +<prompt>root# </prompt> smbpasswd -a -m <replaceable>machine_name</replaceable> </para> <para> -<emphasis>If you manually create a machine account, immediately join -the client to the domain.</emphasis> An open account like this -can allow intruders to gain access to user account information -in your domain. +where <replaceable>machine_name</replaceable> is the machine's netbios +name. </para> +<warning> + <title>Join the client to the domain immediately</title> + + <para> + Manually creating a machine trust account using this method is the + equivalent of creating a machine account on a Windows NT PDC using + the "Server Manager". From the time at which the account is created + to the time which th client joins the domain and changes the password, + your domain is vulnerable to an intruder joining your domain using a + a machine with the same netbios name. A PDC inherently trusts + members of the domain and will serve out a large degree of user + information to such clients. You have been warned! + </para> +</warning> +</sect2> + + +<sect2> +<title>Creating machine trust accounts "on the fly"</title> + <para> -The second way of creating machine trust accounts is to add -them on the fly at the time the client is joined to the domain. -You will need to include a value for the -<ulink url="smb.conf.5.html#ADDUSERSCRIPT">add user script</ulink> -parameter. Below is an example I use on a RedHat 6.2 Linux system. +The second, and most recommended way of creating machine trust accounts +is to create them as needed at the time the client is joined to +the domain. You will need to include a value for the <ulink +url="smb.conf.5.html#ADDUSERSCRIPT">add user script</ulink> +parameter. Below is an example from a RedHat 6.2 Linux system. </para> <para><programlisting> @@ -310,13 +406,13 @@ add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u </programlisting></para> <para> -In Samba 2.2.0, <emphasis>only the root account</emphasis> can be used to create -machine accounts on the fly like this. Therefore, it is required -to create an entry in smbpasswd for <emphasis>root</emphasis>. -The password <emphasis>SHOULD</emphasis> be set to s different -password that the associated <filename>/etc/passwd</filename> -entry for security reasons. +In Samba 2.2.1, <emphasis>only the root account</emphasis> can be used to create +machine accounts like this. Therefore, it is required to create +an entry in smbpasswd for <emphasis>root</emphasis>. The password +<emphasis>SHOULD</emphasis> be set to s different password that the +associated <filename>/etc/passwd</filename> entry for security reasons. </para> +</sect2> </sect1> <!-- ********************************************************** @@ -330,108 +426,145 @@ entry for security reasons. <para> </para> +<itemizedlist> +<listitem> + <para> + <emphasis>I cannot include a '$' in a machine name.</emphasis> + </para> + + <para> + A 'machine name' in (typically) <filename>/etc/passwd</> + of the machine name with a '$' appended. FreeBSD (and other BSD + systems ?) won't create a user with a '$' in their name. + </para> -<para> -<emphasis>I cannot include a '$' in a machine name.</emphasis> -</para> - -<para> -A 'machine name' in (typically) <filename>/etc/passwd</> -of the machine name with a '$' appended. FreeBSD (and other BSD -systems ?) won't create a user with a '$' in their name. -</para> + <para> + The problem is only in the program used to make the entry, once + made, it works perfectly. So create a user without the '$' and + use <command>vipw</> to edit the entry, adding the '$'. Or create + the whole entry with vipw if you like, make sure you use a + unique uid ! + </para> +</listitem> + +<listitem> + <para> + <emphasis>I get told "You already have a connection to the Domain...." + or "Cannot join domain, the credentials supplied conflict with an + existing set.." when creating a machine account.</emphasis> + </para> -<para> -The problem is only in the program used to make the entry, once -made, it works perfectly. So create a user without the '$' and -use <command>vipw</> to edit the entry, adding the '$'. Or create -the whole entry with vipw if you like, make sure you use a -unique uid ! -</para> + <para> + This happens if you try to create a machine account from the + machine itself and already have a connection (e.g. mapped drive) + to a share (or IPC$) on the Samba PDC. The following command + will remove all network drive connections: + </para> + <para> + <prompt>C:\WINNT\></prompt> <command>net use * /d</command> + </para> -<para> -<emphasis>I get told "You already have a connection to the Domain...." -when creating a machine account.</emphasis> -</para> + <para> + Further, if the machine is a already a 'member of a workgroup' that + is the same name as the domain you are joining (bad idea) you will + get this message. Change the workgroup name to something else, it + does not matter what, reboot, and try again. + </para> +</listitem> -<para> -This happens if you try to create a machine account from the -machine itself and use a user name that does not work (for whatever -reason) and then try another (possibly valid) user name. -Exit out of the network applet to close the initial connection -and try again. -</para> +<listitem> + <para> + <emphasis>The system can not log you on (C000019B)....</emphasis> + </para> -<para> -Further, if the machine is a already a 'member of a workgroup' that -is the same name as the domain you are joining (bad idea) you will -get this message. Change the workgroup name to something else, it -does not matter what, reboot, and try again. -</para> + <para>I joined the domain successfully but after upgrading + to a newer version of the Samba code I get the message, "The system + can not log you on (C000019B), Please try a gain or consult your + system administrator" when attempting to logon. + </para> -<para> -<emphasis>I get told "Cannot join domain, the credentials supplied -conflict with an existing set.."</emphasis> -</para> + <para> + This occurs when the domain SID stored in + <filename>private/WORKGROUP.SID</filename> is + changed. For example, you remove the file and <command>smbd</command> automatically + creates a new one. Or you are swapping back and forth between + versions 2.0.7, TNG and the HEAD branch code (not recommended). The + only way to correct the problem is to restore the original domain + SID or remove the domain client from the domain and rejoin. + </para> +</listitem> -<para> -This is the same basic problem as mentioned above, "You already -have a connection..." -</para> +<listitem> + <para> + <emphasis>The machine account for this computer either does not + exist or is not accessible.</emphasis> + </para> -<para> -<emphasis> -"The system can not log you on (C000019B)...."</emphasis> -</para> + <para> + When I try to join the domain I get the message "The machine account + for this computer either does not exist or is not accessible". Whats + wrong? + </para> -<para>I joined the domain successfully but after upgrading -to a newer version of the Samba code I get the message, "The system -can not log you on (C000019B), Please try a gain or consult your -system administrator" when attempting to logon. -</para> + <para> + This problem is caused by the PDC not having a suitable machine account. + If you are using the <parameter>add user script</parameter> method to create + accounts then this would indicate that it has not worked. Ensure the domain + admin user system is working. + </para> -<para> -This occurs when the domain SID stored in -<filename>private/WORKGROUP.SID</filename> is -changed. For example, you remove the file and <command>smbd</command> automatically -creates a new one. Or you are swapping back and forth between -versions 2.0.7, TNG and the HEAD branch code (not recommended). The -only way to correct the problem is to restore the original domain -SID or remove the domain client from the domain and rejoin. -</para> + <para> + Alternatively if you are creating account entries manually then they + have not been created correctly. Make sure that you have the entry + correct for the machine account in smbpasswd file on the Samba PDC. + If you added the account using an editor rather than using the smbpasswd + utility, make sure that the account name is the machine netbios name + with a '$' appended to it ( ie. computer_name$ ). There must be an entry + in both /etc/passwd and the smbpasswd file. Some people have reported + that inconsistent subnet masks between the Samba server and the NT + client have caused this problem. Make sure that these are consistent + for both client and server. + </para> +</listitem> +<listitem> + <para> + <emphasis>When I attempt to login to a Samba Domain from a NT4/W2K workstation, + I get a message about my account being disabled.</emphasis> + </para> -<para> -<emphasis>"The machine account for this computer either does not -exist or is not accessible."</emphasis> -</para> + <para> + This problem is caused by a PAM related bug in Samba 2.2.0. This bug is + fixed in 2.2.1. Other symptoms could be unaccessible shares on + NT/W2K member servers in the domain or the following error in your smbd.log: + passdb/pampass.c:pam_account(268) PAM: UNKNOWN ERROR for User: %user% + </para> + + <para> + At first be ensure to enable the useraccounts with <command>smbpasswd -e + %user%</command>, this is normaly done, when you create an account. + </para> -<para> -When I try to join the domain I get the message "The machine account -for this computer either does not exist or is not accessible". Whats -wrong ? -</para> + <para> + In order to work around this problem in 2.2.0, configure the + <parameter>account</parameter> control flag in + <filename>/etc/pam.d/samba</filename> file as follows: + </para> -<para> -This problem is caused by the PDC not having a suitable machine account. -If you are using the <command>add user script =</> method to create -accounts then this would indicate that it has not worked. Ensure the domain -admin user system is working. -</para> + <para><programlisting> + account required pam_permit.so + </programlisting></para> -<para> -Alternatively if you are creating account entries manually then they -have not been created correctly. Make sure that you have the entry -correct for the machine account in smbpasswd file on the Samba PDC. -If you added the account using an editor rather than using the smbpasswd -utility, make sure that the account name is the machine netbios name -with a '$' appended to it ( ie. computer_name$ ). There must be an entry -in both /etc/passwd and the smbpasswd file. Some people have reported -that inconsistent subnet masks between the Samba server and the NT -client have caused this problem. Make sure that these are consistent -for both client and server. -</para> + <para> + If you want to remain backward compatibility to samba 2.0.x use + <filename>pam_permit.so</filename>, it's also possible to use + <filename>pam_pwdb.so</filename>. There are some bugs if you try to + use <filename>pam_unix.so</filename>, if you need this, be ensure to use + the most recent version of this file. + </para> +</listitem> +</itemizedlist> </sect1> @@ -460,89 +593,98 @@ Profiles and Policies in Windows NT 4.0</ulink> available from Microsoft. Here are some additional details: </para> -<para> -<emphasis>What about Windows NT Policy Editor ?</emphasis> -</para> +<itemizedlist> -<para> -To create or edit <filename>ntconfig.pol</filename> you must use -the NT Server Policy Editor, <command>poledit.exe</command> which -is included with NT Server but <emphasis>not NT Workstation</emphasis>. -There is a Policy Editor on a NTws -but it is not suitable for creating <emphasis>Domain Policies</emphasis>. -Further, although the Windows 95 -Policy Editor can be installed on an NT Workstation/Server, it will not -work with NT policies because the registry key that are set by the policy templates. -However, the files from the NT Server will run happily enough on an NTws. -You need <filename>poledit.exe, common.adm</> and <filename>winnt.adm</>. It is convenient -to put the two *.adm files in <filename>c:\winnt\inf</> which is where -the binary will look for them unless told otherwise. Note also that that -directory is 'hidden'. -</para> +<listitem> + <para> + <emphasis>What about Windows NT Policy Editor ?</emphasis> + </para> -<para>The Windows NT policy editor is also included with the -Service Pack 3 (and later) for Windows NT 4.0. Extract the files using -<command>servicepackname /x</command>, ie thats <command>Nt4sp6ai.exe -/x</command> for service pack 6a. The policy editor, <command>poledit.exe</command> and the -associated template files (*.adm) should -be extracted as well. It is also possible to downloaded the policy template -files for Office97 and get a copy of the policy editor. Another possible -location is with the Zero Administration Kit available for download from Microsoft. -</para> + <para> + To create or edit <filename>ntconfig.pol</filename> you must use + the NT Server Policy Editor, <command>poledit.exe</command> which + is included with NT Server but <emphasis>not NT Workstation</emphasis>. + There is a Policy Editor on a NTws + but it is not suitable for creating <emphasis>Domain Policies</emphasis>. + Further, although the Windows 95 + Policy Editor can be installed on an NT Workstation/Server, it will not + work with NT policies because the registry key that are set by the policy templates. + However, the files from the NT Server will run happily enough on an NTws. + You need <filename>poledit.exe, common.adm</> and <filename>winnt.adm</>. It is convenient + to put the two *.adm files in <filename>c:\winnt\inf</> which is where + the binary will look for them unless told otherwise. Note also that that + directory is 'hidden'. + </para> + <para> + The Windows NT policy editor is also included with the Service Pack 3 (and + later) for Windows NT 4.0. Extract the files using <command>servicepackname /x</command>, + ie thats <command>Nt4sp6ai.exe /x</command> for service pack 6a. The policy editor, + <command>poledit.exe</command> and the associated template files (*.adm) should + be extracted as well. It is also possible to downloaded the policy template + files for Office97 and get a copy of the policy editor. Another possible + location is with the Zero Administration Kit available for download from Microsoft. + </para> +</listitem> -<para> -<emphasis>Can Win95 do Policies ?</emphasis> -</para> -<para> -Install the group policy handler for Win9x to pick up group -policies. Look on the Win98 CD in <filename>\tools\reskit\netadmin\poledit</filename>. -Install group policies on a Win9x client by double-clicking -<filename>grouppol.inf</filename>. Log off and on again a couple of -times and see if Win98 picks up group policies. Unfortunately this needs -to be done on every Win9x machine that uses group policies.... -</para> +<listitem> + <para> + <emphasis>Can Win95 do Policies ?</emphasis> + </para> -<para> -If group policies don't work one reports suggests getting the updated -(read: working) grouppol.dll for Windows 9x. The group list is grabbed -from /etc/group. -</para> + <para> + Install the group policy handler for Win9x to pick up group + policies. Look on the Win98 CD in <filename>\tools\reskit\netadmin\poledit</filename>. + Install group policies on a Win9x client by double-clicking + <filename>grouppol.inf</filename>. Log off and on again a couple of + times and see if Win98 picks up group policies. Unfortunately this needs + to be done on every Win9x machine that uses group policies.... + </para> -<para> -<emphasis>How do I get 'User Manager' and 'Server Manager'</emphasis> -</para> + <para> + If group policies don't work one reports suggests getting the updated + (read: working) grouppol.dll for Windows 9x. The group list is grabbed + from /etc/group. + </para> +</listitem> -<para> -Since I don't need to buy an NT Server CD now, how do I get -the 'User Manager for Domains', the 'Server Manager' ? -</para> -<para> -Microsoft distributes a version of -these tools called nexus for installation on Windows 95 systems. The -tools set includes -</para> +<listitem> + <para> + <emphasis>How do I get 'User Manager' and 'Server Manager'</emphasis> + </para> + + <para> + Since I don't need to buy an NT Server CD now, how do I get + the 'User Manager for Domains', the 'Server Manager' ? + </para> + + <para> + Microsoft distributes a version of these tools called nexus for + installation on Windows 95 systems. The tools set includes + </para> -<itemizedlist> - <listitem><para>Server Manager</para></listitem> + <itemizedlist> + <listitem><para>Server Manager</para></listitem> - <listitem><para>User Manager for Domains</para></listitem> + <listitem><para>User Manager for Domains</para></listitem> - <listitem><para>Event Viewer</para></listitem> -</itemizedlist> + <listitem><para>Event Viewer</para></listitem> + </itemizedlist> -<para> -Click here to download the archived file <ulink -url="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE">ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE</ulink> -</para> + <para> + Click here to download the archived file <ulink + url="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE">ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE</ulink> + </para> -<para> -The Windows NT 4.0 version of the 'User Manager for -Domains' and 'Server Manager' are available from Microsoft via ftp -from <ulink url="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE">ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</ulink> -</para> + <para> + The Windows NT 4.0 version of the 'User Manager for + Domains' and 'Server Manager' are available from Microsoft via ftp + from <ulink url="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE">ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</ulink> + </para> +</listitem> +</itemizedlist> </sect1> @@ -564,12 +706,14 @@ of mailing lists, RFC's and documentation. The docs that come with the samba distribution contain very good explanations of general SMB topics such as browsing.</para> -<para> -<emphasis>What are some diagnostics tools I can use to debug the domain logon -process and where can I find them?</emphasis> -</para> +<itemizedlist> +<listitem> + <para> + <emphasis>What are some diagnostics tools I can use to debug the domain logon + process and where can I find them?</emphasis> + </para> - <para> + <para> One of the best diagnostic tools for debugging problems is Samba itself. You can use the -d option for both smbd and nmbd to specifiy what 'debug level' at which to run. See the man pages on smbd, nmbd and @@ -601,9 +745,9 @@ process and where can I find them?</emphasis> <listitem><para>smbclient -L //{netbios name of server}</para></listitem> </itemizedlist> - <para> + <para> An SMB enabled version of tcpdump is available from - <ulink url="http://www.tcpdump.org/">http://www.tcpdup.org/</ulink>. + <ulink url="http://www.tcpdump.org/">http://www.tcpdup.org/</ulink>. Ethereal, another good packet sniffer for UNIX and Win32 hosts, can be downloaded from <ulink url="http://www.ethereal.com/">http://www.ethereal.com</ulink>. @@ -620,11 +764,15 @@ process and where can I find them?</emphasis> local subnet. Be aware that Ethereal can read and write netmon formatted files. </para> +</listitem> + + +<listitem> + <para> + <emphasis>How do I install 'Network Monitor' on an NT Workstation + or a Windows 9x box?</emphasis> + </para> -<para> -<emphasis>How do I install 'Network Monitor' on an NT Workstation -or a Windows 9x box?</emphasis> -</para> <para> Installing netmon on an NT workstation requires a couple of steps. The following are for installing Netmon V4.00.349, which comes @@ -696,12 +844,17 @@ or a Windows 9x box?</emphasis> information on how to do this. Copy the files from a working Netmon installation. </para> +</listitem> -<sect2> -<title>URLs and similar</title> -<itemizedlist> + +<listitem> + <para> + The following is a list if helpful URLs and other links: + </para> + + <itemizedlist> <listitem><para>Home of Samba site <ulink url="http://samba.org"> http://samba.org</ulink>. We have a mirror near you !</para></listitem> @@ -728,36 +881,35 @@ or a Windows 9x box?</emphasis> <ulink url="ftp://ftp.microsoft.com/developr/drg/CIFS/"> ftp://ftp.microsoft.com/developr/drg/CIFS/</ulink></para></listitem> + </itemizedlist> +</listitem> </itemizedlist> -</sect2> - - -<sect2> -<title>Mailing Lists</title> -<para> -<emphasis>How do I get help from the mailing lists ?</emphasis> -</para> +<itemizedlist> +<listitem> + <para> + <emphasis>How do I get help from the mailing lists ?</emphasis> + </para> -<para> -There are a number of Samba related mailing lists. Go to <ulink -url="http://samba.org">http://samba.org</ulink>, click on your nearest mirror -and then click on <command>Support</> and then click on <command> -Samba related mailing lists</>. -</para> + <para> + There are a number of Samba related mailing lists. Go to <ulink + url="http://samba.org">http://samba.org</ulink>, click on your nearest mirror + and then click on <command>Support</> and then click on <command> + Samba related mailing lists</>. + </para> -<para> -For questions relating to Samba TNG go to -<ulink url="http://www.samba-tng.org/">http://www.samba-tng.org/</ulink> -It has been requested that you don't post questions about Samba-TNG to the -main stream Samba lists.</para> + <para> + For questions relating to Samba TNG go to + <ulink url="http://www.samba-tng.org/">http://www.samba-tng.org/</ulink> + It has been requested that you don't post questions about Samba-TNG to the + main stream Samba lists.</para> -<para> -If you post a message to one of the lists please observe the following guide lines : -</para> + <para> + If you post a message to one of the lists please observe the following guide lines : + </para> -<itemizedlist> + <itemizedlist> <listitem><para> Always remember that the developers are volunteers, they are not paid and they never guarantee to produce a particular feature at @@ -801,28 +953,787 @@ If you post a message to one of the lists please observe the following guide lin mailing lists go to a huge number of people, do they all need a copy of your smb.conf in their attach directory ?</para></listitem> + </itemizedlist> +</listitem> + + +<listitem> + <para> + <emphasis>How do I get off the mailing lists ?</emphasis> + </para> + + <para>To have your name removed from a samba mailing list, go to the + same place you went to to get on it. Go to <ulink + url="http://lists.samba.org/">http://lists.samba.org</ulink>, + click on your nearest mirror and then click on <command>Support</> and + then click on <command> Samba related mailing lists</>. Or perhaps see + <ulink url="http://lists.samba.org/mailman/roster/samba-ntdom">here</ulink> + </para> + + <para> + Please don't post messages to the list asking to be removed, you will just + be referred to the above address (unless that process failed in some way...) + </para> +</listitem> </itemizedlist> +</sect1> + + +<!-- ********************************************************** + + Windows 9x domain control + +*************************************************************** --> +<sect1> +<title>Domain Control for Windows 9x/ME</title> +<note> <para> -<emphasis>How do I get off the mailing lists ?</emphasis> +The following section contains much of the original +DOMAIN.txt file previously included with Samba. Much of +the material is based on what went into the book Special +Edition, Using Samba. (Richard Sharpe) </para> +</note> - <para>To have your name removed from a samba mailing list, go to the - same place you went to to get on it. Go to <ulink url= - "http://lists.samba.org/">http://lists.samba.org</ulink>, click - on your nearest mirror and then click on <command>Support</> and - then click on <command> Samba related mailing lists</>. Or perhaps see - <ulink url="http://lists.samba.org/mailman/roster/samba-ntdom">here</ulink></para> +<para> +A domain and a workgroup are exactly the same thing in terms of network +browsing. The difference is that a distributable authentication +database is associated with a domain, for secure login access to a +network. Also, different access rights can be granted to users if they +successfully authenticate against a domain logon server (NT server and +other systems based on NT server support this, as does at least Samba TNG now). +</para> - <para> - Please don't post messages to the list asking to be removed, you will just - be referred to the above address (unless that process failed in some way...) - </para> -</sect2> -</sect1> +<para> +The SMB client logging on to a domain has an expectation that every other +server in the domain should accept the same authentication information. +Network browsing functionality of domains and workgroups is +identical and is explained in BROWSING.txt. It should be noted, that browsing +is total orthogonal to logon support. +</para> + +<para> +Issues related to the single-logon network model are discussed in this +document. Samba supports domain logons, network logon scripts, and user +profiles for MS Windows for workgroups and MS Windows 9X clients. +</para> + + +<para> +When an SMB client in a domain wishes to logon it broadcast requests for a +logon server. The first one to reply gets the job, and validates its +password using whatever mechanism the Samba administrator has installed. +It is possible (but very stupid) to create a domain where the user +database is not shared between servers, ie they are effectively workgroup +servers advertising themselves as participating in a domain. This +demonstrates how authentication is quite different from but closely +involved with domains. +</para> + +<para> +Another thing commonly associated with single-logon domains is remote +administration over the SMB protocol. Again, there is no reason why this +cannot be implemented with an underlying username database which is +different from the Windows NT SAM. Support for the Remote Administration +Protocol is planned for a future release of Samba. +</para> + +<para> +Network logon support as discussed in this section is aimed at Window for +Workgroups, and Windows 9X clients. +</para> + +<para> +Support for profiles is confirmed as working for Win95, NT 4.0 and NT 3.51. +It is possible to specify: the profile location; script file to be loaded +on login; the user's home directory; and for NT a kick-off time could also +now easily be supported. However, there are some differences between Win9X +profile support and WinNT profile support. These are discussed below. +</para> + +<para> +With NT Workstations, all this does not require the use or intervention of +an NT 4.0 or NT 3.51 server: Samba can now replace the logon services +provided by an NT server, to a limited and experimental degree (for example, +running "User Manager for Domains" will not provide you with access to +a domain created by a Samba Server). +</para> + +<para> +With Win95, the help of an NT server can be enlisted, both for profile storage +and for user authentication. For details on user authentication, see +security_level.txt. For details on profile storage, see below. +</para> + +<para> +Using these features you can make your clients verify their logon via +the Samba server; make clients run a batch file when they logon to +the network and download their preferences, desktop and start menu. +</para> + +<para> +Before launching into the configuration instructions, it is worthwhile looking +at how a Win9X client performs a logon: +</para> + +<orderedlist> +<listitem> + <para> + The client broadcasts (to the IP broadcast address of the subnet it is in) + a NetLogon request. This is sent to the NetBIOS address DOMAIN<00> at the + NetBIOS layer. The client chooses the first response it receives, which + contains the NetBIOS name of the logon server to use in the format of + \\SERVER. + </para> +</listitem> + +<listitem> + <para> + The client then connects to that server, logs on (does an SMBsessetupX) and + then connects to the IPC$ share (using an SMBtconX). + </para> +</listitem> + +<listitem> + <para> + The client then does a NetWkstaUserLogon request, which retrieves the name + of the user's logon script. + </para> +</listitem> + +<listitem> + <para> + The client then connects to the NetLogon share and searches for this + and if it is found and can be read, is retrieved and executed by the client. + After this, the client disconnects from the NetLogon share. + </para> +</listitem> + +<listitem> + <para> + The client then sends a NetUserGetInfo request to the server, to retrieve + the user's home share, which is used to search for profiles. Since the + response to the NetUserGetInfo request does not contain much more + the user's home share, profiles for Win9X clients MUST reside in the user + home directory. + </para> +</listitem> + +<listitem> + <para> + The client then connects to the user's home share and searches for the + user's profile. As it turns out, you can specify the users home share as + a sharename and path. For example, \\server\fred\.profile. + If the profiles are found, they are implemented. + </para> +</listitem> + +<listitem> + <para> + The client then disconnects from the user's home share, and reconnects to + the NetLogon share and looks for CONFIG.POL, the policies file. If this is + found, it is read and implemented. + </para> +</listitem> +</orderedlist> + + +<sect2> +<title>Configuration Instructions: Network Logons</title> + +<para> +To use domain logons and profiles you need to do the following: +</para> + + +<orderedlist> +<listitem> + <para> + Create a share called [netlogon] in your smb.conf. This share should + be readable by all users, and probably should not be writeable. This + share will hold your network logon scripts, and the CONFIG.POL file + (Note: for details on the CONFIG.POL file, how to use it, what it is, + refer to the Microsoft Windows NT Administration documentation. + The format of these files is not known, so you will need to use + Microsoft tools). + </para> + + <para> + For example I have used: + </para> + + <para><programlisting> +[netlogon] + path = /data/dos/netlogon + writeable = no + guest ok = no +</programlisting></para> + + <para> + Note that it is important that this share is not writeable by ordinary + users, in a secure environment: ordinary users should not be allowed + to modify or add files that another user's computer would then download + when they log in. + </para> +</listitem> + + + +<listitem> + <para> + in the [global] section of smb.conf set the following: + </para> + + <para><programlisting> +domain logons = yes +logon script = %U.bat + </programlisting></para> + + <para> + The choice of batch file is, of course, up to you. The above would + give each user a separate batch file as the %U will be changed to + their username automatically. The other standard % macros may also be + used. You can make the batch files come from a subdirectory by using + something like: + </para> + + <para><programlisting> +logon script = scripts\%U.bat + </programlisting></para> +</listitem> + +<listitem> + <para> + create the batch files to be run when the user logs in. If the batch + file doesn't exist then no batch file will be run. + </para> + + <para> + In the batch files you need to be careful to use DOS style cr/lf line + endings. If you don't then DOS may get confused. I suggest you use a + DOS editor to remotely edit the files if you don't know how to produce + DOS style files under unix. + </para> +</listitem> + + +<listitem> + <para> + Use smbclient with the -U option for some users to make sure that + the \\server\NETLOGON share is available, the batch files are + visible and they are readable by the users. + </para> +</listitem> + +<listitem> + <para> + you will probabaly find that your clients automatically mount the + \\SERVER\NETLOGON share as drive z: while logging in. You can put + some useful programs there to execute from the batch files. + </para> +</listitem> +</orderedlist> +<warning> +<title>security mode and master browsers</title> +<para> +There are a few comments to make in order to tie up some +loose ends. There has been much debate over the issue of whether +or not it is ok to configure Samba as a Domain Controller in security +modes other than <constant>USER</constant>. The only security mode +which will not work due to technical reasons is <constant>SHARE</constant> +mode security. <constant>DOMAIN</constant> and <constant>SERVER</constant> +mode security is really just a variation on SMB user level security. +</para> + +<para> +Actually, this issue is also closer tied to the debate on whether +or not Samba must be the domain master browser for its workgroup +when operating as a DC. While it may technically be possible +to configure a server as such (after all, browsing and domain logons +are two distinctly different functions), it is not a good idea to +so. You should remember that the DC must register the DOMAIN#1b netbios +name. This is the name used by Windows clients to locate the DC. +Windows clients do not distinguish between the DC and the DMB. +For this reason, it is very wise to configure the Samba DC as the DMB. +</para> + +<para> +Now back to the issue of configuring a Samba DC to use a mode other +than "security = user". If a Samba host is configured to use +another SMB server or DC in order to validate user connection +requests, then it is a fact that some other machine on the network +(the "password server") knows more about user than the Samba host. +99% of the time, this other host is a domain controller. Now +in order to operate in domain mode security, the "workgroup" parameter +must be set to the name of the Windows NT domain (which already +has a domain controller, right?) +</para> + +<para> +Therefore configuring a Samba box as a DC for a domain that +already by definition has a PDC is asking for trouble. +Therefore, you should always configure the Samba DC to be the DMB +for its domain. +</para> +</warning> + +</sect2> + + +<sect2> +<title>Configuration Instructions: Setting up Roaming User Profiles</title> + +<warning> +<para> +<emphasis>NOTE!</emphasis> Roaming profiles support is different +for Win9X and WinNT. +</para> +</warning> + +<para> +Before discussing how to configure roaming profiles, it is useful to see how +Win9X and WinNT clients implement these features. +</para> + +<para> +Win9X clients send a NetUserGetInfo request to the server to get the user's +profiles location. However, the response does not have room for a separate +profiles location field, only the users home share. This means that Win9X +profiles are restricted to being in the user's home directory. +</para> + + +<para> +WinNT clients send a NetSAMLogon RPC request, which contains many fields, +including a separate field for the location of the user's profiles. +This means that support for profiles is different for Win9X and WinNT. +</para> + + + +<sect3> +<title>Windows NT Configuration</title> + +<para> +To support WinNT clients, inn the [global] section of smb.conf set the +following (for example): +</para> + +<para><programlisting> +logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath +</programlisting></para> + +<para> +The default for this option is \\%N\%U\profile, namely +\\sambaserver\username\profile. The \\N%\%U service is created +automatically by the [homes] service. +If you are using a samba server for the profiles, you _must_ make the +share specified in the logon path browseable. +</para> + +<note> +<para> +[lkcl 26aug96 - we have discovered a problem where Windows clients can +maintain a connection to the [homes] share in between logins. The +[homes] share must NOT therefore be used in a profile path.] +</para> +</note> + +</sect3> + + +<sect3> +<title>Windows 9X Configuration</title> + +<para> +To support Win9X clients, you must use the "logon home" parameter. Samba has +now been fixed so that "net use/home" now works as well, and it, too, relies +on the "logon home" parameter. +</para> + +<para> +By using the logon home parameter, you are restricted to putting Win9X +profiles in the user's home directory. But wait! There is a trick you +can use. If you set the following in the [global] section of your +smb.conf file: +</para> + +<para><programlisting> +logon home = \\%L\%U\.profiles +</programlisting></para> + +<para> +then your Win9X clients will dutifully put their clients in a subdirectory +of your home directory called .profiles (thus making them hidden). +</para> + +<para> +Not only that, but 'net use/home' will also work, because of a feature in +Win9X. It removes any directory stuff off the end of the home directory area +and only uses the server and share portion. That is, it looks like you +specified \\%L\%U for "logon home". +</para> + + +</sect3> + + +<sect3> +<title>Win9X and WinNT Configuration</title> + +<para> +You can support profiles for both Win9X and WinNT clients by setting both the +"logon home" and "logon path" parameters. For example: +</para> + +<para><programlisting> +logon home = \\%L\%U\.profiles +logon path = \\%L\profiles\%U +</programlisting></para> + +<note> +<para> +I have not checked what 'net use /home' does on NT when "logon home" is +set as above. +</para> +</note> +</sect3> + + + +<sect3> +<title>Windows 9X Profile Setup</title> + +<para> +When a user first logs in on Windows 9X, the file user.DAT is created, +as are folders "Start Menu", "Desktop", "Programs" and "Nethood". +These directories and their contents will be merged with the local +versions stored in c:\windows\profiles\username on subsequent logins, +taking the most recent from each. You will need to use the [global] +options "preserve case = yes", "short case preserve = yes" and +"case sensitive = no" in order to maintain capital letters in shortcuts +in any of the profile folders. +</para> + + +<para> +The user.DAT file contains all the user's preferences. If you wish to +enforce a set of preferences, rename their user.DAT file to user.MAN, +and deny them write access to this file. +</para> + +<orderedlist> +<listitem> + <para> + On the Windows 95 machine, go to Control Panel | Passwords and + select the User Profiles tab. Select the required level of + roaming preferences. Press OK, but do _not_ allow the computer + to reboot. + </para> +</listitem> + + +<listitem> + <para> + On the Windows 95 machine, go to Control Panel | Network | + Client for Microsoft Networks | Preferences. Select 'Log on to + NT Domain'. Then, ensure that the Primary Logon is 'Client for + Microsoft Networks'. Press OK, and this time allow the computer + to reboot. + </para> +</listitem> + +</orderedlist> + +<para> +Under Windows 95, Profiles are downloaded from the Primary Logon. +If you have the Primary Logon as 'Client for Novell Networks', then +the profiles and logon script will be downloaded from your Novell +Server. If you have the Primary Logon as 'Windows Logon', then the +profiles will be loaded from the local machine - a bit against the +concept of roaming profiles, if you ask me. +</para> + +<para> +You will now find that the Microsoft Networks Login box contains +[user, password, domain] instead of just [user, password]. Type in +the samba server's domain name (or any other domain known to exist, +but bear in mind that the user will be authenticated against this +domain and profiles downloaded from it, if that domain logon server +supports it), user name and user's password. +</para> + +<para> +Once the user has been successfully validated, the Windows 95 machine +will inform you that 'The user has not logged on before' and asks you +if you wish to save the user's preferences? Select 'yes'. +</para> + +<para> +Once the Windows 95 client comes up with the desktop, you should be able +to examine the contents of the directory specified in the "logon path" +on the samba server and verify that the "Desktop", "Start Menu", +"Programs" and "Nethood" folders have been created. +</para> + +<para> +These folders will be cached locally on the client, and updated when +the user logs off (if you haven't made them read-only by then :-). +You will find that if the user creates further folders or short-cuts, +that the client will merge the profile contents downloaded with the +contents of the profile directory already on the local client, taking +the newest folders and short-cuts from each set. +</para> + +<para> +If you have made the folders / files read-only on the samba server, +then you will get errors from the w95 machine on logon and logout, as +it attempts to merge the local and the remote profile. Basically, if +you have any errors reported by the w95 machine, check the unix file +permissions and ownership rights on the profile directory contents, +on the samba server. +</para> + +<para> +If you have problems creating user profiles, you can reset the user's +local desktop cache, as shown below. When this user then next logs in, +they will be told that they are logging in "for the first time". +</para> + +<orderedlist> +<listitem> + <para> + instead of logging in under the [user, password, domain] dialog, + press escape. + </para> +</listitem> + +<listitem> + <para> + run the regedit.exe program, and look in: + </para> + + <para> + HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList + </para> + + <para> + you will find an entry, for each user, of ProfilePath. Note the + contents of this key (likely to be c:\windows\profiles\username), + then delete the key ProfilePath for the required user. + </para> + + <para> + [Exit the registry editor]. + </para> +</listitem> + +<listitem> + <para> + <emphasis>WARNING</emphasis> - before deleting the contents of the + directory listed in + the ProfilePath (this is likely to be c:\windows\profiles\username), + ask them if they have any important files stored on their desktop + or in their start menu. delete the contents of the directory + ProfilePath (making a backup if any of the files are needed). + </para> + + <para> + This will have the effect of removing the local (read-only hidden + system file) user.DAT in their profile directory, as well as the + local "desktop", "nethood", "start menu" and "programs" folders. + </para> +</listitem> + +<listitem> + <para> + search for the user's .PWL password-cacheing file in the c:\windows + directory, and delete it. + </para> +</listitem> + + +<listitem> + <para> + log off the windows 95 client. + </para> +</listitem> + +<listitem> + <para> + check the contents of the profile path (see "logon path" described + above), and delete the user.DAT or user.MAN file for the user, + making a backup if required. + </para> +</listitem> + +</orderedlist> + +<para> +If all else fails, increase samba's debug log levels to between 3 and 10, +and / or run a packet trace program such as tcpdump or netmon.exe, and +look for any error reports. +</para> + +<para> +If you have access to an NT server, then first set up roaming profiles +and / or netlogons on the NT server. Make a packet trace, or examine +the example packet traces provided with NT server, and see what the +differences are with the equivalent samba trace. +</para> + +</sect3> + + +<sect3> +<title>Windows NT Workstation 4.0</title> + +<para> +When a user first logs in to a Windows NT Workstation, the profile +NTuser.DAT is created. The profile location can be now specified +through the "logon path" parameter. +</para> + +<note> +<para> +[lkcl 10aug97 - i tried setting the path to +\\samba-server\homes\profile, and discovered that this fails because +a background process maintains the connection to the [homes] share +which does _not_ close down in between user logins. you have to +have \\samba-server\%L\profile, where user is the username created +from the [homes] share]. +</para> +</note> + +<para> +There is a parameter that is now available for use with NT Profiles: +"logon drive". This should be set to "h:" or any other drive, and +should be used in conjunction with the new "logon home" parameter. +</para> + +<para> +The entry for the NT 4.0 profile is a _directory_ not a file. The NT +help on profiles mentions that a directory is also created with a .PDS +extension. The user, while logging in, must have write permission to +create the full profile path (and the folder with the .PDS extension) +[lkcl 10aug97 - i found that the creation of the .PDS directory failed, +and had to create these manually for each user, with a shell script. +also, i presume, but have not tested, that the full profile path must +be browseable just as it is for w95, due to the manner in which they +attempt to create the full profile path: test existence of each path +component; create path component]. +</para> + +<para> +In the profile directory, NT creates more folders than 95. It creates +"Application Data" and others, as well as "Desktop", "Nethood", +"Start Menu" and "Programs". The profile itself is stored in a file +NTuser.DAT. Nothing appears to be stored in the .PDS directory, and +its purpose is currently unknown. +</para> + +<para> +You can use the System Control Panel to copy a local profile onto +a samba server (see NT Help on profiles: it is also capable of firing +up the correct location in the System Control Panel for you). The +NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN +turns a profile into a mandatory one. +</para> + +<note> +<para> +[lkcl 10aug97 - i notice that NT Workstation tells me that it is +downloading a profile from a slow link. whether this is actually the +case, or whether there is some configuration issue, as yet unknown, +that makes NT Workstation _think_ that the link is a slow one is a +matter to be resolved]. +</para> + +<para> +[lkcl 20aug97 - after samba digest correspondance, one user found, and +another confirmed, that profiles cannot be loaded from a samba server +unless "security = user" and "encrypt passwords = yes" (see the file +ENCRYPTION.txt) or "security = server" and "password server = ip.address. +of.yourNTserver" are used. either of these options will allow the NT +workstation to access the samba server using LAN manager encrypted +passwords, without the user intervention normally required by NT +workstation for clear-text passwords]. +</para> + +<para> +[lkcl 25aug97 - more comments received about NT profiles: the case of +the profile _matters_. the file _must_ be called NTuser.DAT or, for +a mandatory profile, NTuser.MAN]. +</para> +</note> + +</sect3> + + +<sect3> +<title>Windows NT Server</title> + +<para> +There is nothing to stop you specifying any path that you like for the +location of users' profiles. Therefore, you could specify that the +profile be stored on a samba server, or any other SMB server, as long as +that SMB server supports encrypted passwords. +</para> + +</sect3> + + +<sect3> +<title>Sharing Profiles between W95 and NT Workstation 4.0</title> + +<warning> +<title>Potentially outdated or incorrect material follows</title> +<para> +I think this is all bogus, but have not deleted it. (Richard Sharpe) +</para> +</warning> + +<para> +The default logon path is \\%N\U%. NT Workstation will attempt to create +a directory "\\samba-server\username.PDS" if you specify the logon path +as "\\samba-server\username" with the NT User Manager. Therefore, you +will need to specify (for example) "\\samba-server\username\profile". +NT 4.0 will attempt to create "\\samba-server\username\profile.PDS", which +is more likely to succeed. +</para> + +<para> +If you then want to share the same Start Menu / Desktop with W95, you will +need to specify "logon path = \\samba-server\username\profile" [lkcl 10aug97 +this has its drawbacks: i created a shortcut to telnet.exe, which attempts +to run from the c:\winnt\system32 directory. this directory is obviously +unlikely to exist on a Win95-only host]. +</para> + +<para> + +If you have this set up correctly, you will find separate user.DAT and +NTuser.DAT files in the same profile directory. +</para> + +<note> +<para> +[lkcl 25aug97 - there are some issues to resolve with downloading of +NT profiles, probably to do with time/date stamps. i have found that +NTuser.DAT is never updated on the workstation after the first time that +it is copied to the local workstation profile directory. this is in +contrast to w95, where it _does_ transfer / update profiles correctly]. +</para> +</note> + +</sect3> + +</sect2> +</sect1> <!-- ********************************************************** @@ -836,10 +1747,14 @@ If you post a message to one of the lists please observe the following guide lin DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba </title> -<para> -This appendix was originally authored by John H Terpstra of the Samba Team -and is included here for posterity. -</para> +<warning> + <title>Possibly Outdated Material</title> + + <para> + This appendix was originally authored by John H Terpstra of + the Samba Team and is included here for posterity. + </para> +</warning> <para> @@ -858,13 +1773,8 @@ Windows NT SAM. Windows NT Server can be installed as either a plain file and print server (WORKGROUP workstation or server) or as a server that participates in Domain Control (DOMAIN member, Primary Domain controller or Backup Domain controller). -</para> - -<para> The same is true for OS/2 Warp Server, Digital Pathworks and other similar products, all of which can participate in Domain Control along with Windows NT. -However only those servers which have licensed Windows NT code in them can be -a primary Domain Controller (eg Windows NT Server, Advanced Server for Unix.) </para> <para> diff --git a/docs/docbook/projdoc/printer_driver2.sgml b/docs/docbook/projdoc/printer_driver2.sgml index 7f0aebc45f..51471ae690 100644 --- a/docs/docbook/projdoc/printer_driver2.sgml +++ b/docs/docbook/projdoc/printer_driver2.sgml @@ -13,7 +13,7 @@ </author> - <pubdate> (20 Apr 2001) </pubdate> + <pubdate> (3 May 2001) </pubdate> </chapterinfo> <title>Printing Support in Samba 2.2.x</title> @@ -55,17 +55,42 @@ SPOOLSS support includes:</para> information</para></listitem> </itemizedlist> +<para> +There has been some initial confusion about what all this means +and whether or not it is a requirement for printer drivers to be +installed on a Samba host in order to support printing from Windows +clients. A bug existed in Samba 2.2.0 which made Windows NT/2000 clients +require that the Samba server possess a valid driver for the printer. +This is fixed in Samba 2.2.1 and once again, Windows NT/2000 clients +can use the local APW for installing drivers to be used with a Samba +served printer. This is the same behavior exhibited by Windows 9x clients. +As a side note, Samba does not use these drivers in any way to process +spooled files. They are utilized entirely by the clients. +</para> + +<para> +The following MS KB article, may be of some help if you are dealing with +Windows 2000 clients: <emphasis>How to Add Printers with No User +Interaction in Windows 2000</emphasis> +</para> + +<para> +<ulink url="http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP">http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP</ulink> +</para> + </sect1> <sect1> <title>Configuration</title> +<warning> +<title>[print$] vs. [printer$]</title> + <para> -<emphasis>WARNING!!!</emphasis> Previous versions of Samba -recommended using a share named [printer$]. This name was taken from the -printer$ service created by Windows 9x clients when a -printer was shared. Windows 9x printer servers always have +Previous versions of Samba recommended using a share named [printer$]. +This name was taken from the printer$ service created by Windows 9x +clients when a printer was shared. Windows 9x printer servers always have a printer$ service which provides read-only access via no password in order to support printer driver downloads. </para> @@ -81,13 +106,13 @@ the client. </para> <para> -These parameters, including <parameter>printer driver +These parameters, including <parameter>printer driver file</parameter> parameter, are being depreciated and should not be used in new installations. For more information on this change, -you should refer to the <link linkend="MIGRATION">Migration section -</link>of this document. +you should refer to the <link linkend="MIGRATION">Migration section</link> +of this document. </para> - +</warning> <sect2> <title>Creating [print$]</title> @@ -112,18 +137,22 @@ appropriate values for your site):</para> guest ok = yes browseable = yes read only = yes + ; since this share is configured as read only, then we need + ; a 'write list'. Check the file system permissions to make + ; sure this account can copy files to the share. If this + ; is setup to a non-root account, then it should also exist + ; as a 'printer admin' write list = ntadmin </programlisting></para> <para>The <ulink url="smb.conf.5.html#WRITELIST"><parameter> write list</parameter></ulink> is used to allow administrative level user accounts to have write access in order to update files -on the share. See the <ulink url="smb./conf.5.html"> -smb.conf(5) man page</ulink> for more information on -configuring file shares.</para> +on the share. See the <ulink url="smb./conf.5.html">smb.conf(5) +man page</ulink> for more information on configuring file shares.</para> -<para>The requirement for <ulink url="smb.conf.5.html#GUESTOK"><command> -guest ok = yes</command></ulink> depends upon how your +<para>The requirement for <ulink url="smb.conf.5.html#GUESTOK"><command>guest +ok = yes</command></ulink> depends upon how your site is configured. If users will be guaranteed to have an account on the Samba host, then this is a non-issue.</para> @@ -165,27 +194,33 @@ for each architecture you wish to support.</para> </programlisting></para> <warning> - <title>ATTENTION! REQUIRED PERMISSIONS</title> +<title>ATTENTION! REQUIRED PERMISSIONS</title> - <para>In order to currently add a new driver to you Samba host, - one of two conditions must hold true:</para> +<para> +In order to currently add a new driver to you Samba host, +one of two conditions must hold true: +</para> - <itemizedlist> - <listitem><para>The account used to connect to the Samba host - must have a uid of 0 (i.e. a root account)</para></listitem> +<itemizedlist> + <listitem><para>The account used to connect to the Samba host + must have a uid of 0 (i.e. a root account)</para></listitem> - <listitem><para>The account used to connect to the Samba host - must be a member of the <ulink - url="smb.conf.5.html#PRINTERADMIN"><parameter>printer - admin</parameter></ulink> list.</para></listitem> - </itemizedlist> - - <para>Of course, the connected account must still possess access - to add files to the subdirectories beneath [print$].</para> + <listitem><para>The account used to connect to the Samba host + must be a member of the <ulink + url="smb.conf.5.html#PRINTERADMIN"><parameter>printer + admin</parameter></ulink> list.</para></listitem> +</itemizedlist> + +<para> +Of course, the connected account must still possess access +to add files to the subdirectories beneath [print$]. Remember +that all file shares are set to 'read only' by default. +</para> </warning> -<para>Once you have created the required [print$] service and +<para> +Once you have created the required [print$] service and associated subdirectories, simply log onto the Samba server using a root (or <parameter>printer admin</parameter>) account from a Windows NT 4.0 client. Navigate to the "Printers" folder @@ -198,9 +233,27 @@ that matches the printer shares defined on your Samba host. <title>Setting Drivers for Existing Printers</title> <para>The initial listing of printers in the Samba host's -Printers folder will have no printer driver assigned to them. -The way assign a driver to a printer is to view the Properties -of the printer and either</para> +Printers folder will have no real printer driver assigned +to them. By default, in Samba 2.2.0 this driver name was set to +<emphasis>NO PRINTER DRIVER AVAILABLE FOR THIS PRINTER</emphasis>. +Later versions changed this to a NULL string to allow the use +tof the local Add Printer Wizard on NT/2000 clients. +Attempting to view the printer properties for a printer +which has this default driver assigned will result in +the error message:</para> + +<para> +<emphasis>Device settings cannot be displayed. The driver +for the specified printer is not installed, only spooler +properties will be displayed. Do you want to install the +driver now?</emphasis> +</para> + +<para> +Click "No" in the error dialog and you will be presented with +the printer properties window. The way assign a driver to a +printer is to either +</para> <itemizedlist> <listitem><para>Use the "New Driver..." button to install @@ -271,7 +324,7 @@ Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,] comment:[] -<prompt>$ </prompt>rpcclient pogo -U root%bleaK.er \ +<prompt>$ </prompt>rpcclient pogo -U root%secret \ <prompt>> </prompt> -c "setdriver hp-print \"HP LaserJet 4000 Series PS\"" Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] Successfully set hp-print to driver HP LaserJet 4000 Series PS. @@ -292,7 +345,7 @@ Add Printer Wizard icon. The APW will be show only if <itemizedlist> <listitem><para>The connected user is able to successfully execute an OpenPrinterEx(\\server) with administrative - priviledges (i.e. root or <parameter>printer admin</parameter>. + priviledges (i.e. root or <parameter>printer admin</parameter>). </para></listitem> <listitem><para><ulink url="smb.conf.5.html#SHOWADDPRINTERWIZARD"><parameter>show @@ -302,8 +355,8 @@ Add Printer Wizard icon. The APW will be show only if <para> In order to be able to use the APW to successfully add a printer to a Samba -server, the <ulink url="smb.conf.5.html#ADDPRINTERCOMMAND"><parameter>addprinter -command</parameter></ulink> must have a defined value. The program +server, the <ulink url="smb.conf.5.html#ADDPRINTERCOMMAND"><parameter>add +printer command</parameter></ulink> must have a defined value. The program hook must successfully add the printer to the system (i.e. <filename>/etc/printcap</filename> or appropriate files) and <filename>smb.conf</filename> if necessary. @@ -312,16 +365,16 @@ hook must successfully add the printer to the system (i.e. <para> When using the APW from a client, if the named printer share does not exist, <command>smbd</command> will execute the <parameter>add printer -program</parameter> and reparse to the <filename>smb.conf</filename> +command</parameter> and reparse to the <filename>smb.conf</filename> to attempt to locate the new printer share. If the share is still not defined, an error of "Access Denied" is returned to the client. Note that the -<parameter>add printer program</parameter> is executed undet the context +<parameter>add printer program</parameter> is executed under the context of the connected user, not necessarily a root account. </para> <para> -There is a complementing <ulink url="smb.conf.5.html#DELETEPRINTERCOMMAND"><parameter>deleteprinter -command</parameter></ulink> for removing entries from the "Printers..." +There is a complementing <ulink url="smb.conf.5.html#DELETEPRINTERCOMMAND"><parameter>delete +printer command</parameter></ulink> for removing entries from the "Printers..." folder. </para> @@ -473,7 +526,7 @@ foreach (supported architecture for a given driver) </filename></para> <para>will reveal that Windows NT always uses the NT driver - name. The is ok as Windows NT always requires that at least + name. This is ok as Windows NT always requires that at least the Windows NT version of the printer driver is present. However, Samba does not have the requirement internally. Therefore, how can you use the NT driver name if is has not @@ -489,67 +542,167 @@ foreach (supported architecture for a given driver) <sect1> - <title><anchor id="MIGRATION">Migration to from Samba 2.0.x to - 2.2.x</title> - - <para>Given that printer driver management has changed - (we hope improved :) ) in 2.2.0 over prior releases, - migration from an existing setup to 2.2.0 can follow - several paths.</para> +<title><anchor id="MIGRATION">Migration to from Samba 2.0.x to 2.2.x</title> + +<para> +Given that printer driver management has changed (we hope improved) in +2.2 over prior releases, migration from an existing setup to 2.2 can +follow several paths. +</para> + +<para> +Windows clients have a tendency to remember things for quite a while. +For example, if a Windows NT client has attached to a Samba 2.0 server, +it will remember the server as a LanMan printer server. Upgrading +the Samba host to 2.2 makes support for MSRPC printing possible, but +the NT client will still remember the previous setting. +</para> + +<para> +In order to give an NT client printing "amesia" (only necessary if you +want to use the newer MSRPC printing functionality in Samba), delete +the registry keys associated with the print server contained in +<constant>[HKLM\SYSTEM\CurrentControlSet\Control\Print]</constant>. The +spooler service on the client should be stopped prior to doing this: +</para> + +<para> +<prompt>C:\WINNT\ ></prompt> <userinput>net stop spooler</userinput> +</para> + +<para> +<emphasis>All the normal disclaimers about editing the registry go +here.</emphasis> Be careful, and know what you are doing. +</para> + +<para> +The spooler service should be restarted after you have finished +removing the appropriate registry entries by replacing the +<command>stop</command> command above with <command>start</command>. +</para> + +<para> +Windows 9x clients will continue to use LanMan printing calls +with a 2.2 Samba server so there is no need to perform any of these +modifications on non-NT clients. +</para> - <warning> - <title>Achtung!</title> - <para>The following smb.conf parameters are considered to be - depreciated and will be removed soon. Do not use them - in new installations</para> +<warning> +<title>Achtung!</title> + +<para> +The following smb.conf parameters are considered to be depreciated and will +be removed soon. Do not use them in new installations +</para> - <itemizedlist> - <listitem><para><parameter>printer driver file (G)</parameter> - </para></listitem> +<itemizedlist> + <listitem><para><parameter>printer driver file (G)</parameter> + </para></listitem> - <listitem><para><parameter>printer driver (S)</parameter> - </para></listitem> + <listitem><para><parameter>printer driver (S)</parameter> + </para></listitem> - <listitem><para><parameter>printer driver location (S)</parameter> - </para></listitem> - </itemizedlist> - </warning> + <listitem><para><parameter>printer driver location (S)</parameter> + </para></listitem> +</itemizedlist> +</warning> - <para>Here are the possible scenarios for supporting migration:</para> +<para> +Here are the possible scenarios for supporting migration: +</para> - <itemizedlist> - <listitem><para>If you do not desire the new Windows NT - print driver support, nothing needs to be done. - All existing parameters work the same.</para></listitem> - - <listitem><para>If you want to take advantage of NT printer - driver support but do not want to migrate the - 9x drivers to the new setup, the leave the existing - printers.def file. When smbd attempts to locate a - 9x driver for the printer in the TDB and fails it - will drop down to using the printers.def (and all - associated parameters). The <command>make_printerdef</command> - tool will also remain for backwards compatibility but will - be moved to the "this tool is the old way of doing it" - pile.</para></listitem> - - <listitem><para>If you install a Windows 9x driver for a printer - on your Samba host (in the printing TDB), this information will - take precedence and the three old printing parameters - will be ignored (including print driver location).</para></listitem> - - <listitem><para>If you want to migrate an existing <filename>printers.def</filename> - file into the new setup, the current only - solution is to use the Windows NT APW to install the NT drivers - and the 9x drivers. This can be scripted using <command>smbclient</command> - and <command>rpcclient</command>. See the - Imprints installation client at <ulink - url="http://imprints.sourceforge.net/">http://imprints.sourceforge.net/</ulink> - for an example. - </para></listitem> - </itemizedlist> +<itemizedlist> + <listitem><para>If you do not desire the new Windows NT + print driver support, nothing needs to be done. + All existing parameters work the same.</para></listitem> + + <listitem><para>If you want to take advantage of NT printer + driver support but do not want to migrate the + 9x drivers to the new setup, the leave the existing + printers.def file. When smbd attempts to locate a + 9x driver for the printer in the TDB and fails it + will drop down to using the printers.def (and all + associated parameters). The <command>make_printerdef</command> + tool will also remain for backwards compatibility but will + be moved to the "this tool is the old way of doing it" + pile.</para></listitem> + + <listitem><para>If you install a Windows 9x driver for a printer + on your Samba host (in the printing TDB), this information will + take precedence and the three old printing parameters + will be ignored (including print driver location).</para></listitem> + + <listitem><para>If you want to migrate an existing <filename>printers.def</filename> + file into the new setup, the current only solution is to use the Windows + NT APW to install the NT drivers and the 9x drivers. This can be scripted + using <command>smbclient</command> and <command>rpcclient</command>. See the + Imprints installation client at <ulink + url="http://imprints.sourceforge.net/">http://imprints.sourceforge.net/</ulink> + for an example. + </para></listitem> +</itemizedlist> </sect1> + +<!-- + + This comment from rpc_server/srv_spoolss_nt.c:_spoolss_open_printer_ex() + needs to be added into a section probably. This is to remind me it needs + to be done. -jerry + + /* + * If the openprinterex rpc call contains a devmode, + * it's a per-user one. This per-user devmode is derivated + * from the global devmode. Openprinterex() contains a per-user + * devmode for when you do EMF printing and spooling. + * In the EMF case, the NT workstation is only doing half the job + * of rendering the page. The other half is done by running the printer + * driver on the server. + * The EMF file doesn't contain the page description (paper size, orientation, ...). + * The EMF file only contains what is to be printed on the page. + * So in order for the server to know how to print, the NT client sends + * a devicemode attached to the openprinterex call. + * But this devicemode is short lived, it's only valid for the current print job. + * + * If Samba would have supported EMF spooling, this devicemode would + * have been attached to the handle, to sent it to the driver to correctly + * rasterize the EMF file. + * + * As Samba only supports RAW spooling, we only receive a ready-to-print file, + * we just act as a pass-thru between windows and the printer. + * + * In order to know that Samba supports only RAW spooling, NT has to call + * getprinter() at level 2 (attribute field) or NT has to call startdoc() + * and until NT sends a RAW job, we refuse it. + * + * But to call getprinter() or startdoc(), you first need a valid handle, + * and to get an handle you have to call openprintex(). Hence why you have + * a devicemode in the openprinterex() call. + * + * + * Differences between NT4 and NT 2000. + * NT4: + * + * On NT4, you only have a global devicemode. This global devicemode can be changed + * by the administrator (or by a user with enough privs). Everytime a user + * wants to print, the devicemode is resetted to the default. In Word, everytime + * you print, the printer's characteristics are always reset to the global devicemode. + * + * NT 2000: + * + * In W2K, there is the notion of per-user devicemode. The first time you use + * a printer, a per-user devicemode is build from the global devicemode. + * If you change your per-user devicemode, it is saved in the registry, under the + * H_KEY_CURRENT_KEY sub_tree. So that everytime you print, you have your default + * printer preferences available. + * + * To change the per-user devicemode: it's the "Printing Preferences ..." button + * on the General Tab of the printer properties windows. + * + * To change the global devicemode: it's the "Printing Defaults..." button + * on the Advanced Tab of the printer properties window. +--> + </chapter> diff --git a/docs/docbook/projdoc/samba-doc.sgml b/docs/docbook/projdoc/samba-doc.sgml index b055477db7..fa58399bf1 100644 --- a/docs/docbook/projdoc/samba-doc.sgml +++ b/docs/docbook/projdoc/samba-doc.sgml @@ -8,6 +8,7 @@ <!ENTITY NT-Security SYSTEM "NT_Security.sgml"> <!ENTITY OS2-Client SYSTEM "OS2-Client-HOWTO.sgml"> <!ENTITY Samba-PDC-HOWTO SYSTEM "Samba-PDC-HOWTO.sgml"> +<!ENTITY CVS-Access SYSTEM "CVS-Access.sgml"> ]> <book id="Samba-Project-Documentation"> @@ -26,10 +27,10 @@ <title>Abstract</title> <para> -This book is a collection of HOWTOs added to Samba documentation over the year. +This book is a collection of HOWTOs added to Samba documentation over the years. I try to ensure that all are current, but sometimes the is a larger job -than one person can maintain. You can always find the later version of this -PDF file at <ulink url="http://www.samba.org/">http://www.samba.org/</ulink> +than one person can maintain. The most recent version of this document +can be found at <ulink url="http://www.samba.org/">http://www.samba.org/</ulink> on the "Documentation" page. Please send updates to <ulink url="mailto:jerry@samba.org">jerry@samba.org</ulink>. </para> @@ -49,5 +50,6 @@ Cheers, jerry &WINBIND; &NT-Security; &OS2-Client; +&CVS-Access; </book> diff --git a/docs/htmldocs/CVS-Access.html b/docs/htmldocs/CVS-Access.html new file mode 100644 index 0000000000..ea47cede04 --- /dev/null +++ b/docs/htmldocs/CVS-Access.html @@ -0,0 +1,193 @@ +<HTML +><HEAD +><TITLE +>HOWTO Access Samba source code via CVS</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD +><BODY +CLASS="ARTICLE" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="ARTICLE" +><DIV +CLASS="TITLEPAGE" +><H1 +CLASS="TITLE" +><A +NAME="AEN1" +>HOWTO Access Samba source code via CVS</A +></H1 +><HR></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN3" +>Introduction</A +></H1 +><P +>Samba is developed in an open environnment. Developers use CVS +(Concurrent Versioning System) to "checkin" (also known as +"commit") new source code. Samba's various CVS branches can +be accessed via anonymouns CVS using the instructions +detailed in this chapter.</P +><P +>This document is a modified version of the instructions found at +<A +HREF="http://samba.org/samba/cvs.html" +TARGET="_top" +>http://samba.org/samba/cvs.html</A +></P +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A +NAME="AEN8" +>CVS Access to samba.org</A +></H1 +><P +>The machine samba.org runs a publicly accessible CVS +repository for access to the source code of several packages, +including samba, rsync and jitterbug. There are two main ways of +accessing the CVS server on this host.</P +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN11" +>Access via CVSweb</A +></H2 +><P +>You can access the source code via your +favourite WWW browser. This allows you to access the contents of +individual files in the repository and also to look at the revision +history and commit logs of individual files. You can also ask for a diff +listing between any two versions on the repository.</P +><P +>Use the URL : <A +HREF="http://samba.org/cgi-bin/cvsweb" +TARGET="_top" +>http://samba.org/cgi-bin/cvsweb</A +></P +></DIV +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN16" +>Access via cvs</A +></H2 +><P +>You can also access the source code via a +normal cvs client. This gives you much more control over you can +do with the repository and allows you to checkout whole source trees +and keep them uptodate via normal cvs commands. This is the +preferred method of access if you are a developer and not +just a casual browser.</P +><P +>To download the latest cvs source code, point your +browser at the URL : <A +HREF="http://www.cyclic.com/" +TARGET="_top" +>http://www.cyclic.com/</A +>. +and click on the 'How to get cvs' link. CVS is free software under +the GNU GPL (as is Samba). Note that there are several graphical CVS clients +which provide a graphical interface to the sometimes mundane CVS commands. +Links to theses clients are also available from http://www.cyclic.com.</P +><P +>To gain access via anonymous cvs use the following steps. +For this example it is assumed that you want a copy of the +samba source code. For the other source code repositories +on this system just substitute the correct package name</P +><P +></P +><OL +TYPE="1" +><LI +><P +> Install a recent copy of cvs. All you really need is a + copy of the cvs client binary. + </P +></LI +><LI +><P +> Run the command + </P +><P +> <B +CLASS="COMMAND" +>cvs -d :pserver:cvs@samba.org:/cvsroot login</B +> + </P +><P +> When it asks you for a password type <TT +CLASS="USERINPUT" +><B +>cvs</B +></TT +>. + </P +></LI +><LI +><P +> Run the command + </P +><P +> <B +CLASS="COMMAND" +>cvs -d :pserver:cvs@samba.org:/cvsroot co samba</B +> + </P +><P +> This will create a directory called samba containing the + latest samba source code (i.e. the HEAD tagged cvs branch). This + currently corresponds to the 3.0 development tree. + </P +><P +> CVS branches other HEAD can be obtained by using the <TT +CLASS="PARAMETER" +><I +>-r</I +></TT +> + and defining a tag name. A list of branch tag names can be found on the + "Development" page of the samba web site. A common request is to obtain the + latest 2.2 release code. This could be done by using the following command. + </P +><P +> <B +CLASS="COMMAND" +>cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba</B +> + </P +></LI +><LI +><P +> Whenever you want to merge in the latest code changes use + the following command from within the samba directory: + </P +><P +> <B +CLASS="COMMAND" +>cvs update -d -P</B +> + </P +></LI +></OL +></DIV +></DIV +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html index 85ef2feb70..acfb1a7a3c 100644 --- a/docs/htmldocs/Samba-HOWTO-Collection.html +++ b/docs/htmldocs/Samba-HOWTO-Collection.html @@ -38,10 +38,10 @@ NAME="AEN9" >Abstract</A ></H1 ><P ->This book is a collection of HOWTOs added to Samba documentation over the year. +>This book is a collection of HOWTOs added to Samba documentation over the years. I try to ensure that all are current, but sometimes the is a larger job -than one person can maintain. You can always find the later version of this -PDF file at <A +than one person can maintain. The most recent version of this document +can be found at <A HREF="http://www.samba.org/" TARGET="_top" >http://www.samba.org/</A @@ -271,299 +271,361 @@ HREF="#AEN445" ></DT ><DT >4.2. <A -HREF="#AEN462" +HREF="#AEN467" >Configuration</A ></DT ><DD ><DL ><DT >4.2.1. <A -HREF="#AEN472" +HREF="#AEN478" >Creating [print$]</A ></DT ><DT >4.2.2. <A -HREF="#AEN507" +HREF="#AEN513" >Setting Drivers for Existing Printers</A ></DT ><DT >4.2.3. <A -HREF="#AEN520" +HREF="#AEN530" >Support a large number of printers</A ></DT ><DT >4.2.4. <A -HREF="#AEN531" +HREF="#AEN541" >Adding New Printers via the Windows NT APW</A ></DT ><DT >4.2.5. <A -HREF="#AEN556" +HREF="#AEN566" >Samba and Printer Ports</A ></DT ></DL ></DD ><DT >4.3. <A -HREF="#AEN564" +HREF="#AEN574" >The Imprints Toolset</A ></DT ><DD ><DL ><DT >4.3.1. <A -HREF="#AEN568" +HREF="#AEN578" >What is Imprints?</A ></DT ><DT >4.3.2. <A -HREF="#AEN578" +HREF="#AEN588" >Creating Printer Driver Packages</A ></DT ><DT >4.3.3. <A -HREF="#AEN581" +HREF="#AEN591" >The Imprints server</A ></DT ><DT >4.3.4. <A -HREF="#AEN585" +HREF="#AEN595" >The Installation Client</A ></DT ></DL ></DD ><DT >4.4. <A -HREF="#AEN607" +HREF="#AEN617" ><A NAME="MIGRATION" ></A ->Migration to from Samba 2.0.x to - 2.2.x</A +>Migration to from Samba 2.0.x to 2.2.x</A ></DT ></DL ></DD ><DT >5. <A -HREF="#AEN639" +HREF="#AEN661" >security = domain in Samba 2.x</A ></DT ><DD ><DL ><DT >5.1. <A -HREF="#AEN657" +HREF="#AEN679" >Joining an NT Domain with Samba 2.2</A ></DT ><DT >5.2. <A -HREF="#AEN721" +HREF="#AEN743" >Samba and Windows 2000 Domains</A ></DT ><DT >5.3. <A -HREF="#AEN726" +HREF="#AEN748" >Why is this better than security = server?</A ></DT ></DL ></DD ><DT >6. <A -HREF="#AEN742" ->How to Configure Samba 2.2.x as a Primary Domain Controller</A +HREF="#AEN764" +>How to Configure Samba 2.2 as a Primary Domain Controller</A ></DT ><DD ><DL ><DT >6.1. <A -HREF="#AEN753" ->Background</A +HREF="#AEN781" +>Prerequisite Reading</A ></DT ><DT >6.2. <A -HREF="#AEN790" ->Configuring the Samba Domain Controller</A +HREF="#AEN787" +>Background</A ></DT ><DT >6.3. <A -HREF="#AEN833" +HREF="#AEN827" +>Configuring the Samba Domain Controller</A +></DT +><DT +>6.4. <A +HREF="#AEN870" >Creating Machine Trust Accounts and Joining Clients to the Domain</A ></DT +><DD +><DL ><DT ->6.4. <A -HREF="#AEN872" ->Common Problems and Errors</A +>6.4.1. <A +HREF="#AEN884" +>Manually creating machine trust accounts</A +></DT +><DT +>6.4.2. <A +HREF="#AEN912" +>Creating machine trust accounts "on the fly"</A ></DT +></DL +></DD ><DT >6.5. <A -HREF="#AEN900" ->System Policies and Profiles</A +HREF="#AEN923" +>Common Problems and Errors</A ></DT ><DT >6.6. <A -HREF="#AEN940" +HREF="#AEN971" +>System Policies and Profiles</A +></DT +><DT +>6.7. <A +HREF="#AEN1015" >What other help can I get ?</A ></DT +><DT +>6.8. <A +HREF="#AEN1129" +>Domain Control for Windows 9x/ME</A +></DT +><DD +><DL +><DT +>6.8.1. <A +HREF="#AEN1159" +>Configuration Instructions: Network Logons</A +></DT +><DT +>6.8.2. <A +HREF="#AEN1193" +>Configuration Instructions: Setting up Roaming User Profiles</A +></DT ><DD ><DL ><DT ->6.6.1. <A -HREF="#AEN987" ->URLs and similar</A +>6.8.2.1. <A +HREF="#AEN1201" +>Windows NT Configuration</A +></DT +><DT +>6.8.2.2. <A +HREF="#AEN1209" +>Windows 9X Configuration</A +></DT +><DT +>6.8.2.3. <A +HREF="#AEN1217" +>Win9X and WinNT Configuration</A +></DT +><DT +>6.8.2.4. <A +HREF="#AEN1224" +>Windows 9X Profile Setup</A +></DT +><DT +>6.8.2.5. <A +HREF="#AEN1260" +>Windows NT Workstation 4.0</A +></DT +><DT +>6.8.2.6. <A +HREF="#AEN1273" +>Windows NT Server</A ></DT ><DT ->6.6.2. <A -HREF="#AEN1011" ->Mailing Lists</A +>6.8.2.7. <A +HREF="#AEN1276" +>Sharing Profiles between W95 and NT Workstation 4.0</A ></DT ></DL ></DD +></DL +></DD ><DT ->6.7. <A -HREF="#AEN1050" +>6.9. <A +HREF="#AEN1286" >DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A ></DT ></DL ></DD ><DT >7. <A -HREF="#AEN1074" +HREF="#AEN1311" >Unifed Logons between Windows NT and UNIX using Winbind</A ></DT ><DD ><DL ><DT >7.1. <A -HREF="#AEN1092" +HREF="#AEN1329" >Abstract</A ></DT ><DT >7.2. <A -HREF="#AEN1096" +HREF="#AEN1333" >Introduction</A ></DT ><DT >7.3. <A -HREF="#AEN1109" +HREF="#AEN1346" >What Winbind Provides</A ></DT ><DD ><DL ><DT >7.3.1. <A -HREF="#AEN1116" +HREF="#AEN1353" >Target Uses</A ></DT ></DL ></DD ><DT >7.4. <A -HREF="#AEN1120" +HREF="#AEN1357" >How Winbind Works</A ></DT ><DD ><DL ><DT >7.4.1. <A -HREF="#AEN1125" +HREF="#AEN1362" >Microsoft Remote Procedure Calls</A ></DT ><DT >7.4.2. <A -HREF="#AEN1129" +HREF="#AEN1366" >Name Service Switch</A ></DT ><DT >7.4.3. <A -HREF="#AEN1145" +HREF="#AEN1382" >Pluggable Authentication Modules</A ></DT ><DT >7.4.4. <A -HREF="#AEN1153" +HREF="#AEN1390" >User and Group ID Allocation</A ></DT ><DT >7.4.5. <A -HREF="#AEN1157" +HREF="#AEN1394" >Result Caching</A ></DT ></DL ></DD ><DT >7.5. <A -HREF="#AEN1160" +HREF="#AEN1397" >Installation and Configuration</A ></DT ><DT >7.6. <A -HREF="#AEN1166" +HREF="#AEN1403" >Limitations</A ></DT ><DT >7.7. <A -HREF="#AEN1178" +HREF="#AEN1415" >Conclusion</A ></DT ></DL ></DD ><DT >8. <A -HREF="#AEN1181" +HREF="#AEN1418" >UNIX Permission Bits and WIndows NT Access Control Lists</A ></DT ><DD ><DL ><DT >8.1. <A -HREF="#AEN1192" +HREF="#AEN1429" >Viewing and changing UNIX permissions using the NT security dialogs</A ></DT ><DT >8.2. <A -HREF="#AEN1201" +HREF="#AEN1438" >How to view file security on a Samba share</A ></DT ><DT >8.3. <A -HREF="#AEN1212" +HREF="#AEN1449" >Viewing file ownership</A ></DT ><DT >8.4. <A -HREF="#AEN1232" +HREF="#AEN1469" >Viewing file or directory permissions</A ></DT ><DD ><DL ><DT >8.4.1. <A -HREF="#AEN1247" +HREF="#AEN1484" >File Permissions</A ></DT ><DT >8.4.2. <A -HREF="#AEN1261" +HREF="#AEN1498" >Directory Permissions</A ></DT ></DL ></DD ><DT >8.5. <A -HREF="#AEN1268" +HREF="#AEN1505" >Modifying file or directory permissions</A ></DT ><DT >8.6. <A -HREF="#AEN1290" +HREF="#AEN1527" >Interaction with the standard Samba create mask parameters</A ></DT ><DT >8.7. <A -HREF="#AEN1354" +HREF="#AEN1591" >Interaction with the standard Samba file attribute mapping</A ></DT @@ -571,39 +633,39 @@ HREF="#AEN1354" ></DD ><DT >9. <A -HREF="#AEN1364" +HREF="#AEN1601" >OS2 Client HOWTO</A ></DT ><DD ><DL ><DT >9.1. <A -HREF="#AEN1375" +HREF="#AEN1612" >FAQs</A ></DT ><DD ><DL ><DT >9.1.1. <A -HREF="#AEN1377" +HREF="#AEN1614" >How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?</A ></DT ><DT >9.1.2. <A -HREF="#AEN1392" +HREF="#AEN1629" >How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?</A ></DT ><DT >9.1.3. <A -HREF="#AEN1401" +HREF="#AEN1638" >Are there any other issues when OS/2 (any version) is used as a client?</A ></DT ><DT >9.1.4. <A -HREF="#AEN1405" +HREF="#AEN1642" >How do I get printer driver download working for OS/2 clients?</A ></DT @@ -611,6 +673,39 @@ HREF="#AEN1405" ></DD ></DL ></DD +><DT +>10. <A +HREF="#AEN1651" +>HOWTO Access Samba source code via CVS</A +></DT +><DD +><DL +><DT +>10.1. <A +HREF="#AEN1658" +>Introduction</A +></DT +><DT +>10.2. <A +HREF="#AEN1663" +>CVS Access to samba.org</A +></DT +><DD +><DL +><DT +>10.2.1. <A +HREF="#AEN1666" +>Access via CVSweb</A +></DT +><DT +>10.2.2. <A +HREF="#AEN1671" +>Access via cvs</A +></DT +></DL +></DD +></DL +></DD ></DL ></DIV ><DIV @@ -2347,22 +2442,60 @@ TARGET="_top" information</P ></LI ></UL +><P +>There has been some initial confusion about what all this means +and whether or not it is a requirement for printer drivers to be +installed on a Samba host in order to support printing from Windows +clients. A bug existed in Samba 2.2.0 which made Windows NT/2000 clients +require that the Samba server possess a valid driver for the printer. +This is fixed in Samba 2.2.1 and once again, Windows NT/2000 clients +can use the local APW for installing drivers to be used with a Samba +served printer. This is the same behavior exhibited by Windows 9x clients. +As a side note, Samba does not use these drivers in any way to process +spooled files. They are utilized entirely by the clients.</P +><P +>The following MS KB article, may be of some help if you are dealing with +Windows 2000 clients: <EM +>How to Add Printers with No User +Interaction in Windows 2000</EM +></P +><P +><A +HREF="http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP" +TARGET="_top" +>http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP</A +></P ></DIV ><DIV CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN462" +NAME="AEN467" >4.2. Configuration</A ></H1 +><DIV +CLASS="WARNING" ><P -><EM ->WARNING!!!</EM -> Previous versions of Samba -recommended using a share named [printer$]. This name was taken from the -printer$ service created by Windows 9x clients when a -printer was shared. Windows 9x printer servers always have +></P +><TABLE +CLASS="WARNING" +BORDER="1" +WIDTH="100%" +><TR +><TD +ALIGN="CENTER" +><B +>[print$] vs. [printer$]</B +></TD +></TR +><TR +><TD +ALIGN="LEFT" +><P +>Previous versions of Samba recommended using a share named [printer$]. +This name was taken from the printer$ service created by Windows 9x +clients when a printer was shared. Windows 9x printer servers always have a printer$ service which provides read-only access via no password in order to support printer driver downloads.</P ><P @@ -2387,21 +2520,26 @@ the client.</P >These parameters, including <TT CLASS="PARAMETER" ><I ->printer driver +>printer driver file</I ></TT > parameter, are being depreciated and should not be used in new installations. For more information on this change, you should refer to the <A HREF="#MIGRATION" ->Migration section </A ->of this document.</P +>Migration section</A +> +of this document.</P +></TD +></TR +></TABLE +></DIV ><DIV CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN472" +NAME="AEN478" >4.2.1. Creating [print$]</A ></H2 ><P @@ -2430,6 +2568,11 @@ CLASS="PROGRAMLISTING" guest ok = yes browseable = yes read only = yes + ; since this share is configured as read only, then we need + ; a 'write list'. Check the file system permissions to make + ; sure this account can copy files to the share. If this + ; is setup to a non-root account, then it should also exist + ; as a 'printer admin' write list = ntadmin</PRE ></TD ></TR @@ -2450,16 +2593,17 @@ level user accounts to have write access in order to update files on the share. See the <A HREF="smb./conf.5.html" TARGET="_top" ->smb.conf(5) man page</A -> for more information on -configuring file shares.</P +>smb.conf(5) +man page</A +> for more information on configuring file shares.</P ><P >The requirement for <A HREF="smb.conf.5.html#GUESTOK" TARGET="_top" ><B CLASS="COMMAND" ->guest ok = yes</B +>guest +ok = yes</B ></A > depends upon how your site is configured. If users will be guaranteed to have @@ -2538,26 +2682,26 @@ ALIGN="CENTER" ALIGN="LEFT" ><P >In order to currently add a new driver to you Samba host, - one of two conditions must hold true:</P +one of two conditions must hold true:</P ><P ></P ><UL ><LI ><P >The account used to connect to the Samba host - must have a uid of 0 (i.e. a root account)</P + must have a uid of 0 (i.e. a root account)</P ></LI ><LI ><P >The account used to connect to the Samba host - must be a member of the <A + must be a member of the <A HREF="smb.conf.5.html#PRINTERADMIN" TARGET="_top" ><TT CLASS="PARAMETER" ><I >printer - admin</I + admin</I ></TT ></A > list.</P @@ -2565,7 +2709,8 @@ CLASS="PARAMETER" ></UL ><P >Of course, the connected account must still possess access - to add files to the subdirectories beneath [print$].</P +to add files to the subdirectories beneath [print$]. Remember +that all file shares are set to 'read only' by default.</P ></TD ></TR ></TABLE @@ -2588,14 +2733,32 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN507" +NAME="AEN513" >4.2.2. Setting Drivers for Existing Printers</A ></H2 ><P >The initial listing of printers in the Samba host's -Printers folder will have no printer driver assigned to them. -The way assign a driver to a printer is to view the Properties -of the printer and either</P +Printers folder will have no real printer driver assigned +to them. By default, in Samba 2.2.0 this driver name was set to +<EM +>NO PRINTER DRIVER AVAILABLE FOR THIS PRINTER</EM +>. +Later versions changed this to a NULL string to allow the use +tof the local Add Printer Wizard on NT/2000 clients. +Attempting to view the printer properties for a printer +which has this default driver assigned will result in +the error message:</P +><P +><EM +>Device settings cannot be displayed. The driver +for the specified printer is not installed, only spooler +properties will be displayed. Do you want to install the +driver now?</EM +></P +><P +>Click "No" in the error dialog and you will be presented with +the printer properties window. The way assign a driver to a +printer is to either</P ><P ></P ><UL @@ -2642,7 +2805,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN520" +NAME="AEN530" >4.2.3. Support a large number of printers</A ></H2 ><P @@ -2700,7 +2863,7 @@ Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] <TT CLASS="PROMPT" >$ </TT ->rpcclient pogo -U root%bleaK.er \ +>rpcclient pogo -U root%secret \ <TT CLASS="PROMPT" >> </TT @@ -2717,7 +2880,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN531" +NAME="AEN541" >4.2.4. Adding New Printers via the Windows NT APW</A ></H2 ><P @@ -2739,7 +2902,7 @@ CLASS="PARAMETER" ><I >printer admin</I ></TT ->. +>). </P ></LI ><LI @@ -2766,8 +2929,8 @@ TARGET="_top" ><TT CLASS="PARAMETER" ><I ->addprinter -command</I +>add +printer command</I ></TT ></A > must have a defined value. The program @@ -2789,7 +2952,7 @@ CLASS="COMMAND" CLASS="PARAMETER" ><I >add printer -program</I +command</I ></TT > and reparse to the <TT CLASS="FILENAME" @@ -2802,7 +2965,7 @@ CLASS="PARAMETER" ><I >add printer program</I ></TT -> is executed undet the context +> is executed under the context of the connected user, not necessarily a root account.</P ><P >There is a complementing <A @@ -2811,8 +2974,8 @@ TARGET="_top" ><TT CLASS="PARAMETER" ><I ->deleteprinter -command</I +>delete +printer command</I ></TT ></A > for removing entries from the "Printers..." @@ -2823,7 +2986,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN556" +NAME="AEN566" >4.2.5. Samba and Printer Ports</A ></H2 ><P @@ -2860,7 +3023,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN564" +NAME="AEN574" >4.3. The Imprints Toolset</A ></H1 ><P @@ -2878,7 +3041,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN568" +NAME="AEN578" >4.3.1. What is Imprints?</A ></H2 ><P @@ -2910,7 +3073,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN578" +NAME="AEN588" >4.3.2. Creating Printer Driver Packages</A ></H2 ><P @@ -2926,7 +3089,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN581" +NAME="AEN591" >4.3.3. The Imprints server</A ></H2 ><P @@ -2946,7 +3109,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN585" +NAME="AEN595" >4.3.4. The Installation Client</A ></H2 ><P @@ -3032,7 +3195,7 @@ CLASS="FILENAME" ></P ><P >will reveal that Windows NT always uses the NT driver - name. The is ok as Windows NT always requires that at least + name. This is ok as Windows NT always requires that at least the Windows NT version of the printer driver is present. However, Samba does not have the requirement internally. Therefore, how can you use the NT driver name if is has not @@ -3049,18 +3212,60 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN607" +NAME="AEN617" >4.4. <A NAME="MIGRATION" ></A ->Migration to from Samba 2.0.x to - 2.2.x</A +>Migration to from Samba 2.0.x to 2.2.x</A ></H1 ><P ->Given that printer driver management has changed - (we hope improved :) ) in 2.2.0 over prior releases, - migration from an existing setup to 2.2.0 can follow - several paths.</P +>Given that printer driver management has changed (we hope improved) in +2.2 over prior releases, migration from an existing setup to 2.2 can +follow several paths.</P +><P +>Windows clients have a tendency to remember things for quite a while. +For example, if a Windows NT client has attached to a Samba 2.0 server, +it will remember the server as a LanMan printer server. Upgrading +the Samba host to 2.2 makes support for MSRPC printing possible, but +the NT client will still remember the previous setting.</P +><P +>In order to give an NT client printing "amesia" (only necessary if you +want to use the newer MSRPC printing functionality in Samba), delete +the registry keys associated with the print server contained in +<TT +CLASS="CONSTANT" +>[HKLM\SYSTEM\CurrentControlSet\Control\Print]</TT +>. The +spooler service on the client should be stopped prior to doing this:</P +><P +><TT +CLASS="PROMPT" +>C:\WINNT\ ></TT +> <TT +CLASS="USERINPUT" +><B +>net stop spooler</B +></TT +></P +><P +><EM +>All the normal disclaimers about editing the registry go +here.</EM +> Be careful, and know what you are doing.</P +><P +>The spooler service should be restarted after you have finished +removing the appropriate registry entries by replacing the +<B +CLASS="COMMAND" +>stop</B +> command above with <B +CLASS="COMMAND" +>start</B +>.</P +><P +>Windows 9x clients will continue to use LanMan printing calls +with a 2.2 Samba server so there is no need to perform any of these +modifications on non-NT clients.</P ><DIV CLASS="WARNING" ><P @@ -3080,9 +3285,8 @@ ALIGN="CENTER" ><TD ALIGN="LEFT" ><P ->The following smb.conf parameters are considered to be - depreciated and will be removed soon. Do not use them - in new installations</P +>The following smb.conf parameters are considered to be depreciated and will +be removed soon. Do not use them in new installations</P ><P ></P ><UL @@ -3094,7 +3298,7 @@ CLASS="PARAMETER" >printer driver file (G)</I ></TT > - </P + </P ></LI ><LI ><P @@ -3104,7 +3308,7 @@ CLASS="PARAMETER" >printer driver (S)</I ></TT > - </P + </P ></LI ><LI ><P @@ -3114,7 +3318,7 @@ CLASS="PARAMETER" >printer driver location (S)</I ></TT > - </P + </P ></LI ></UL ></TD @@ -3129,31 +3333,31 @@ CLASS="PARAMETER" ><LI ><P >If you do not desire the new Windows NT - print driver support, nothing needs to be done. - All existing parameters work the same.</P + print driver support, nothing needs to be done. + All existing parameters work the same.</P ></LI ><LI ><P >If you want to take advantage of NT printer - driver support but do not want to migrate the - 9x drivers to the new setup, the leave the existing - printers.def file. When smbd attempts to locate a - 9x driver for the printer in the TDB and fails it - will drop down to using the printers.def (and all - associated parameters). The <B + driver support but do not want to migrate the + 9x drivers to the new setup, the leave the existing + printers.def file. When smbd attempts to locate a + 9x driver for the printer in the TDB and fails it + will drop down to using the printers.def (and all + associated parameters). The <B CLASS="COMMAND" >make_printerdef</B > - tool will also remain for backwards compatibility but will - be moved to the "this tool is the old way of doing it" - pile.</P + tool will also remain for backwards compatibility but will + be moved to the "this tool is the old way of doing it" + pile.</P ></LI ><LI ><P >If you install a Windows 9x driver for a printer - on your Samba host (in the printing TDB), this information will - take precedence and the three old printing parameters - will be ignored (including print driver location).</P + on your Samba host (in the printing TDB), this information will + take precedence and the three old printing parameters + will be ignored (including print driver location).</P ></LI ><LI ><P @@ -3161,23 +3365,22 @@ CLASS="COMMAND" CLASS="FILENAME" >printers.def</TT > - file into the new setup, the current only - solution is to use the Windows NT APW to install the NT drivers - and the 9x drivers. This can be scripted using <B + file into the new setup, the current only solution is to use the Windows + NT APW to install the NT drivers and the 9x drivers. This can be scripted + using <B CLASS="COMMAND" >smbclient</B -> - and <B +> and <B CLASS="COMMAND" >rpcclient</B >. See the - Imprints installation client at <A + Imprints installation client at <A HREF="http://imprints.sourceforge.net/" TARGET="_top" >http://imprints.sourceforge.net/</A > - for an example. - </P + for an example. + </P ></LI ></UL ></DIV @@ -3186,7 +3389,7 @@ TARGET="_top" CLASS="CHAPTER" ><HR><H1 ><A -NAME="AEN639" +NAME="AEN661" >Chapter 5. security = domain in Samba 2.x</A ></H1 ><DIV @@ -3194,7 +3397,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN657" +NAME="AEN679" >5.1. Joining an NT Domain with Samba 2.2</A ></H1 ><P @@ -3421,7 +3624,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN721" +NAME="AEN743" >5.2. Samba and Windows 2000 Domains</A ></H1 ><P @@ -3446,7 +3649,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN726" +NAME="AEN748" >5.3. Why is this better than security = server?</A ></H1 ><P @@ -3532,52 +3735,135 @@ TARGET="_top" CLASS="CHAPTER" ><HR><H1 ><A -NAME="AEN742" ->Chapter 6. How to Configure Samba 2.2.x as a Primary Domain Controller</A +NAME="AEN764" +>Chapter 6. How to Configure Samba 2.2 as a Primary Domain Controller</A ></H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN753" ->6.1. Background</A +NAME="AEN781" +>6.1. Prerequisite Reading</A +></H1 +><P +>Before you continue readingin this chapter, please make sure +that you are comfortable with configuring basic files services +in smb.conf and how to enable and administrate password +encryption in Samba. Theses two topics are covered in the +<A +HREF="smb.conf.5.html" +TARGET="_top" +><TT +CLASS="FILENAME" +>smb.conf(5)</TT +></A +> +manpage and the <A +HREF="EMCRYPTION.html" +TARGET="_top" +>Encryption chapter</A +> +of this HOWTO Collection.</P +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A +NAME="AEN787" +>6.2. Background</A ></H1 +><DIV +CLASS="NOTE" +><BLOCKQUOTE +CLASS="NOTE" ><P +><B +>Note: </B ><EM >Author's Note :</EM -> This document -is a combination of David Bannon's Samba 2.2 PDC HOWTO -and the Samba NT Domain FAQ. Both documents are superceeded by this one.</P +> This document is a combination +of David Bannon's Samba 2.2 PDC HOWTO and the Samba NT Domain FAQ. +Both documents are superceeded by this one.</P +></BLOCKQUOTE +></DIV ><P >Version of Samba prior to release 2.2 had marginal capabilities to -act as a Windows NT 4.0 Primary Domain Controller (PDC). The following -functionality should work in 2.2.0:</P +act as a Windows NT 4.0 Primary Domain Controller (PDC). Beginning with +Samba 2.2.0, we are proud to announce official support for Windows NT 4.0 +style domain logons from Windows NT 4.0 (through SP6) and Windows 2000 (through +SP1) clients. This article outlines the steps necessary for configuring Samba +as a PDC. It is necessary to have a working Samba server prior to implementing the +PDC functionality. If you have not followed the steps outlined in +<A +HREF="UNIX_INSTALL.html" +TARGET="_top" +> UNIX_INSTALL.html</A +>, please make sure +that your server is configured correctly before proceeding. Another good +resource in the <A +HREF="smb.conf.5.html" +TARGET="_top" +>smb.conf(5) man +page</A +>. The following functionality should work in 2.2:</P ><P ></P ><UL ><LI ><P ->domain logons for Windows NT 4.0/2000 clients</P +> domain logons for Windows NT 4.0/2000 clients. + </P ></LI ><LI ><P ->placing a Windows 9x client in user level security</P +> placing a Windows 9x client in user level security + </P ></LI ><LI ><P ->retrieving a list of users and groups from a Samba PDC to - Windows 9x/NT/2000 clients </P +> retrieving a list of users and groups from a Samba PDC to + Windows 9x/NT/2000 clients + </P ></LI ><LI ><P ->roving user profiles</P +> roving (roaming) user profiles + </P ></LI ><LI ><P ->Windows NT 4.0 style system policies</P +> Windows NT 4.0 style system policies + </P ></LI ></UL +><DIV +CLASS="WARNING" +><P +></P +><TABLE +CLASS="WARNING" +BORDER="1" +WIDTH="100%" +><TR +><TD +ALIGN="CENTER" +><B +>Windows 2000 Service Pack 2 Clients</B +></TD +></TR +><TR +><TD +ALIGN="LEFT" +><P +> Samba 2.2.1 is required for PDC functionality when using Windows 2000 + SP2 clients. + </P +></TD +></TR +></TABLE +></DIV ><P >The following pieces of functionality are not included in the 2.2 release:</P ><P @@ -3585,21 +3871,25 @@ functionality should work in 2.2.0:</P ><UL ><LI ><P ->Windows NT 4 domain trusts</P +> Windows NT 4 domain trusts + </P ></LI ><LI ><P ->Sam replication with Windows NT 4.0 Domain Controllers - (i.e. a Samba PDC and a Windows NT BDC or vice versa) </P +> SAM replication with Windows NT 4.0 Domain Controllers + (i.e. a Samba PDC and a Windows NT BDC or vice versa) + </P ></LI ><LI ><P ->Adding users via the User Manager for Domains</P +> Adding users via the User Manager for Domains + </P ></LI ><LI ><P ->Acting as a Windows 2000 Domain Controller (i.e. Kerberos - and Active Directory)</P +> Acting as a Windows 2000 Domain Controller (i.e. Kerberos and + Active Directory) + </P ></LI ></UL ><P @@ -3609,25 +3899,6 @@ support Windows 9x style domain logons is completely different from NT4 domain logons and has been officially supported for some time.</P ><P ->Beginning with Samba 2.2.0, we are proud to announce official -support for Windows NT 4.0 style domain logons from Windows NT -4.0 and Windows 2000 (including SP1) clients. This article -outlines the steps necessary for configuring Samba as a PDC. -Note that it is necessary to have a working Samba server -prior to implementing the PDC functionality. If you have not -followed the steps outlined in <A -HREF="UNIX_INSTALL.html" -TARGET="_top" ->UNIX_INSTALL.html</A ->, please make sure that your server -is configured correctly before proceeding. Another good -resource in the <A -HREF="smb.conf.5.html" -TARGET="_top" ->smb.conf(5) man -page</A ->.</P -><P >Implementing a Samba PDC can basically be divided into 2 broad steps.</P ><P @@ -3636,13 +3907,14 @@ steps.</P TYPE="1" ><LI ><P ->Configuring the Samba Domain Controller +> Configuring the Samba PDC </P ></LI ><LI ><P ->Creating machine trust accounts - and joining clients to the domain</P +> Creating machine trust accounts and joining clients + to the domain + </P ></LI ></OL ><P @@ -3656,8 +3928,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN790" ->6.2. Configuring the Samba Domain Controller</A +NAME="AEN827" +>6.3. Configuring the Samba Domain Controller</A ></H1 ><P >The first step in creating a working Samba PDC is to @@ -3768,7 +4040,7 @@ TARGET="_top" > = \\homeserver\%u ; specify a generic logon script for all users - ; this is a relative path to the [netlogon] share + ; this is a relative **DOS** path to the [netlogon] share <A HREF="smb.conf.5.html#LOGONSCRIPT" TARGET="_top" @@ -3825,16 +4097,14 @@ TARGET="_top" ></TABLE ></P ><P ->There are a couple of points to emphasize in the above -configuration.</P +>There are a couple of points to emphasize in the above configuration.</P ><P ></P ><UL ><LI ><P ->encrypted passwords must be enabled. - For more details on how to do this, refer to - <A +> Encrypted passwords must be enabled. For more details on how + to do this, refer to <A HREF="ENCRYPTION.html" TARGET="_top" >ENCRYPTION.html</A @@ -3843,23 +4113,27 @@ TARGET="_top" ></LI ><LI ><P ->The server must support domain logons - and a <TT +> The server must support domain logons and a + <TT CLASS="FILENAME" >[netlogon]</TT -> share</P +> share + </P ></LI ><LI ><P ->The server must be the domain master browser - in order for Windows client to locate the server as a DC.</P +> The server must be the domain master browser in order for Windows + client to locate the server as a DC. Please refer to the various + Network Browsing documentation included with this distribution for + details. + </P ></LI ></UL ><P >As Samba 2.2 does not offer a complete implementation of group mapping between Windows NT groups and UNIX groups (this is really quite complicated to explain in a short space), you should refer to the <A -HREF="smb.conf.5.html#DOMAINADMONUSERS" +HREF="smb.conf.5.html#DOMAINADMINUSERS" TARGET="_top" >domain admin users</A @@ -3876,28 +4150,38 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN833" ->6.3. Creating Machine Trust Accounts and Joining Clients +NAME="AEN870" +>6.4. Creating Machine Trust Accounts and Joining Clients to the Domain</A ></H1 ><P ->First you must understand what a machine trust account is and what -it is used for.</P -><P ->A machine trust account is a user account owned by a computer. +>A machine trust account is a samba user account owned by a computer. The account password acts as the shared secret for secure -communication with the Domain Controller. Hence the reason that -a Windows 9x host is never a true member of a domain because -it does not posses a machine trust account and thus has no shared -secret with the DC.</P +communication with the Domain Controller. This is a security feature +to prevent an unauthorized machine with the same netbios name from +joining the domain and gaining access to domain user/group accounts. +Hence a Windows 9x host is never a true member of a domain because it does +not posses a machine trust account, and thus has no shared secret with the DC.</P ><P >On a Windows NT PDC, these machine trust account passwords are stored -in the registry. A Samba PDC stores these accounts in he same location +in the registry. A Samba PDC stores these accounts in the same location as user LanMan and NT password hashes (currently <TT CLASS="FILENAME" >smbpasswd</TT >). -However, machine trust accounts only possess the NT password hash.</P +However, machine trust accounts only possess and use the NT password hash.</P +><P +>Because Samba requires machine accounts to possess a UNIX uid from +which an Windows NT SID can be generated, all of these accounts +must have an entry in <TT +CLASS="FILENAME" +>/etc/passwd</TT +> and smbpasswd. +Future releases will alleviate the need to create +<TT +CLASS="FILENAME" +>/etc/passwd</TT +> entries. </P ><P >There are two means of creating machine trust accounts.</P ><P @@ -3905,30 +4189,52 @@ However, machine trust accounts only possess the NT password hash.</P ><UL ><LI ><P ->Manual creation before joining the client - to the domain. In this case, the password is set to a known - value -- the lower case of the machine's netbios name.</P +> Manual creation before joining the client to the domain. In this case, + the password is set to a known value -- the lower case of the + machine's netbios name. + </P ></LI ><LI ><P ->Creation of the account at the time of - joining the domain. In this case, the session key of the - administrative account used to join the client to the domain acts - as an encryption key for setting the password to a random value.</P +> Creation of the account at the time of joining the domain. In + this case, the session key of the administrative account used to join + the client to the domain acts as an encryption key for setting the + password to a random value (This is the recommended method). + </P ></LI ></UL +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN884" +>6.4.1. Manually creating machine trust accounts</A +></H2 ><P ->Because Samba requires machine accounts to possess a UNIX uid from -which an Windows NT SID can be generated, all of these accounts -will have an entry in <TT -CLASS="FILENAME" ->/etc/passwd</TT -> and smbpasswd. -Future releases will alleviate the need to create -<TT -CLASS="FILENAME" ->/etc/passwd</TT -> entries.</P +>The first step in creating a machine trust account by hand is to +create an entry for the machine in /etc/passwd. This can be done +using <B +CLASS="COMMAND" +>vipw</B +> or any 'add userr' command which is normally +used to create new UNIX accounts. The following is an example for a Linux +based Samba server:</P +><P +><TT +CLASS="PROMPT" +>root# </TT +>/usr/sbin/useradd -g 100 -d /dev/null -c <TT +CLASS="REPLACEABLE" +><I +>machine_nickname</I +></TT +> -m -s /bin/false <TT +CLASS="REPLACEABLE" +><I +>machine_name</I +></TT +>$</P ><P >The <TT CLASS="FILENAME" @@ -3949,23 +4255,43 @@ WIDTH="100%" ><TD ><PRE CLASS="PROGRAMLISTING" ->doppy$:x:505:501:NTMachine:/dev/null:/bin/false</PRE +>doppy$:x:505:501:<TT +CLASS="REPLACEABLE" +><I +>machine_nickname</I +></TT +>:/dev/null:/bin/false</PRE ></TD ></TR ></TABLE ></P ><P ->If you are manually creating the machine accounts, it is necessary -to add the <TT -CLASS="FILENAME" ->/etc/passwd</TT -> (or NIS passwd -map) entry prior to adding the <TT -CLASS="FILENAME" ->smbpasswd</TT -> -entry. The following command will create a new machine account -ready for use.</P +>Above, <TT +CLASS="REPLACEABLE" +><I +>machine_nickname</I +></TT +> can be any descriptive name for the +pc i.e. BasementComputer. The <TT +CLASS="REPLACEABLE" +><I +>machine_name</I +></TT +> absolutely must be +the netbios name of the pc to be added to the domain. The "$" must append the netbios +name of the pc or samba will not recognize this as a machine account</P +><P +>Now that the UNIX account has been created, the next step is to create +the smbpasswd entry for the machine containing the well known initial +trust account password. This can be done using the <A +HREF="smbpasswd.6.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbpasswd(8)</B +></A +> command +as shown here:</P ><P ><TT CLASS="PROMPT" @@ -3983,24 +4309,57 @@ CLASS="REPLACEABLE" >machine_name</I ></TT > is the machine's netbios -name.</P +name. </P +><DIV +CLASS="WARNING" ><P -><EM ->If you manually create a machine account, immediately join -the client to the domain.</EM -> An open account like this -can allow intruders to gain access to user account information -in your domain.</P -><P ->The second way of creating machine trust accounts is to add -them on the fly at the time the client is joined to the domain. -You will need to include a value for the -<A +></P +><TABLE +CLASS="WARNING" +BORDER="1" +WIDTH="100%" +><TR +><TD +ALIGN="CENTER" +><B +>Join the client to the domain immediately</B +></TD +></TR +><TR +><TD +ALIGN="LEFT" +><P +> Manually creating a machine trust account using this method is the + equivalent of creating a machine account on a Windows NT PDC using + the "Server Manager". From the time at which the account is created + to the time which th client joins the domain and changes the password, + your domain is vulnerable to an intruder joining your domain using a + a machine with the same netbios name. A PDC inherently trusts + members of the domain and will serve out a large degree of user + information to such clients. You have been warned! + </P +></TD +></TR +></TABLE +></DIV +></DIV +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN912" +>6.4.2. Creating machine trust accounts "on the fly"</A +></H2 +><P +>The second, and most recommended way of creating machine trust accounts +is to create them as needed at the time the client is joined to +the domain. You will need to include a value for the <A HREF="smb.conf.5.html#ADDUSERSCRIPT" TARGET="_top" >add user script</A > -parameter. Below is an example I use on a RedHat 6.2 Linux system.</P +parameter. Below is an example from a RedHat 6.2 Linux system.</P ><P ><TABLE BORDER="0" @@ -4016,135 +4375,228 @@ CLASS="PROGRAMLISTING" ></TABLE ></P ><P ->In Samba 2.2.0, <EM +>In Samba 2.2.1, <EM >only the root account</EM > can be used to create -machine accounts on the fly like this. Therefore, it is required -to create an entry in smbpasswd for <EM +machine accounts like this. Therefore, it is required to create +an entry in smbpasswd for <EM >root</EM ->. -The password <EM +>. The password +<EM >SHOULD</EM -> be set to s different -password that the associated <TT +> be set to s different password that the +associated <TT CLASS="FILENAME" >/etc/passwd</TT -> -entry for security reasons.</P +> entry for security reasons.</P +></DIV ></DIV ><DIV CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN872" ->6.4. Common Problems and Errors</A +NAME="AEN923" +>6.5. Common Problems and Errors</A ></H1 ><P ></P ><P -><EM ->I cannot include a '$' in a machine name.</EM ></P +><UL +><LI +><P +> <EM +>I cannot include a '$' in a machine name.</EM +> + </P ><P ->A 'machine name' in (typically) <TT +> A 'machine name' in (typically) <TT CLASS="FILENAME" >/etc/passwd</TT > -of the machine name with a '$' appended. FreeBSD (and other BSD -systems ?) won't create a user with a '$' in their name.</P + of the machine name with a '$' appended. FreeBSD (and other BSD + systems ?) won't create a user with a '$' in their name. + </P ><P ->The problem is only in the program used to make the entry, once -made, it works perfectly. So create a user without the '$' and -use <B +> The problem is only in the program used to make the entry, once + made, it works perfectly. So create a user without the '$' and + use <B CLASS="COMMAND" >vipw</B > to edit the entry, adding the '$'. Or create -the whole entry with vipw if you like, make sure you use a -unique uid !</P + the whole entry with vipw if you like, make sure you use a + unique uid ! + </P +></LI +><LI ><P -><EM +> <EM >I get told "You already have a connection to the Domain...." -when creating a machine account.</EM -></P -><P ->This happens if you try to create a machine account from the -machine itself and use a user name that does not work (for whatever -reason) and then try another (possibly valid) user name. -Exit out of the network applet to close the initial connection -and try again.</P + or "Cannot join domain, the credentials supplied conflict with an + existing set.." when creating a machine account.</EM +> + </P ><P ->Further, if the machine is a already a 'member of a workgroup' that -is the same name as the domain you are joining (bad idea) you will -get this message. Change the workgroup name to something else, it -does not matter what, reboot, and try again.</P +> This happens if you try to create a machine account from the + machine itself and already have a connection (e.g. mapped drive) + to a share (or IPC$) on the Samba PDC. The following command + will remove all network drive connections: + </P ><P -><EM ->I get told "Cannot join domain, the credentials supplied -conflict with an existing set.."</EM -></P +> <TT +CLASS="PROMPT" +>C:\WINNT\></TT +> <B +CLASS="COMMAND" +>net use * /d</B +> + </P ><P ->This is the same basic problem as mentioned above, "You already -have a connection..."</P +> Further, if the machine is a already a 'member of a workgroup' that + is the same name as the domain you are joining (bad idea) you will + get this message. Change the workgroup name to something else, it + does not matter what, reboot, and try again. + </P +></LI +><LI ><P -><EM ->"The system can not log you on (C000019B)...."</EM -></P +> <EM +>The system can not log you on (C000019B)....</EM +> + </P ><P >I joined the domain successfully but after upgrading -to a newer version of the Samba code I get the message, "The system -can not log you on (C000019B), Please try a gain or consult your -system administrator" when attempting to logon.</P + to a newer version of the Samba code I get the message, "The system + can not log you on (C000019B), Please try a gain or consult your + system administrator" when attempting to logon. + </P ><P ->This occurs when the domain SID stored in -<TT +> This occurs when the domain SID stored in + <TT CLASS="FILENAME" >private/WORKGROUP.SID</TT > is -changed. For example, you remove the file and <B + changed. For example, you remove the file and <B CLASS="COMMAND" >smbd</B > automatically -creates a new one. Or you are swapping back and forth between -versions 2.0.7, TNG and the HEAD branch code (not recommended). The -only way to correct the problem is to restore the original domain -SID or remove the domain client from the domain and rejoin.</P + creates a new one. Or you are swapping back and forth between + versions 2.0.7, TNG and the HEAD branch code (not recommended). The + only way to correct the problem is to restore the original domain + SID or remove the domain client from the domain and rejoin. + </P +></LI +><LI ><P -><EM ->"The machine account for this computer either does not -exist or is not accessible."</EM -></P +> <EM +>The machine account for this computer either does not + exist or is not accessible.</EM +> + </P ><P ->When I try to join the domain I get the message "The machine account -for this computer either does not exist or is not accessible". Whats -wrong ?</P +> When I try to join the domain I get the message "The machine account + for this computer either does not exist or is not accessible". Whats + wrong? + </P ><P ->This problem is caused by the PDC not having a suitable machine account. -If you are using the <B -CLASS="COMMAND" ->add user script =</B +> This problem is caused by the PDC not having a suitable machine account. + If you are using the <TT +CLASS="PARAMETER" +><I +>add user script</I +></TT > method to create -accounts then this would indicate that it has not worked. Ensure the domain -admin user system is working.</P -><P ->Alternatively if you are creating account entries manually then they -have not been created correctly. Make sure that you have the entry -correct for the machine account in smbpasswd file on the Samba PDC. -If you added the account using an editor rather than using the smbpasswd -utility, make sure that the account name is the machine netbios name -with a '$' appended to it ( ie. computer_name$ ). There must be an entry -in both /etc/passwd and the smbpasswd file. Some people have reported -that inconsistent subnet masks between the Samba server and the NT -client have caused this problem. Make sure that these are consistent -for both client and server.</P + accounts then this would indicate that it has not worked. Ensure the domain + admin user system is working. + </P +><P +> Alternatively if you are creating account entries manually then they + have not been created correctly. Make sure that you have the entry + correct for the machine account in smbpasswd file on the Samba PDC. + If you added the account using an editor rather than using the smbpasswd + utility, make sure that the account name is the machine netbios name + with a '$' appended to it ( ie. computer_name$ ). There must be an entry + in both /etc/passwd and the smbpasswd file. Some people have reported + that inconsistent subnet masks between the Samba server and the NT + client have caused this problem. Make sure that these are consistent + for both client and server. + </P +></LI +><LI +><P +> <EM +>When I attempt to login to a Samba Domain from a NT4/W2K workstation, + I get a message about my account being disabled.</EM +> + </P +><P +> This problem is caused by a PAM related bug in Samba 2.2.0. This bug is + fixed in 2.2.1. Other symptoms could be unaccessible shares on + NT/W2K member servers in the domain or the following error in your smbd.log: + passdb/pampass.c:pam_account(268) PAM: UNKNOWN ERROR for User: %user% + </P +><P +> At first be ensure to enable the useraccounts with <B +CLASS="COMMAND" +>smbpasswd -e + %user%</B +>, this is normaly done, when you create an account. + </P +><P +> In order to work around this problem in 2.2.0, configure the + <TT +CLASS="PARAMETER" +><I +>account</I +></TT +> control flag in + <TT +CLASS="FILENAME" +>/etc/pam.d/samba</TT +> file as follows: + </P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +> account required pam_permit.so + </PRE +></TD +></TR +></TABLE +></P +><P +> If you want to remain backward compatibility to samba 2.0.x use + <TT +CLASS="FILENAME" +>pam_permit.so</TT +>, it's also possible to use + <TT +CLASS="FILENAME" +>pam_pwdb.so</TT +>. There are some bugs if you try to + use <TT +CLASS="FILENAME" +>pam_unix.so</TT +>, if you need this, be ensure to use + the most recent version of this file. + </P +></LI +></UL ></DIV ><DIV CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN900" ->6.5. System Policies and Profiles</A +NAME="AEN971" +>6.6. System Policies and Profiles</A ></H1 ><P >Much of the information necessary to implement System Policies and @@ -4159,92 +4611,107 @@ Profiles and Policies in Windows NT 4.0</A ><P >Here are some additional details:</P ><P -><EM ->What about Windows NT Policy Editor ?</EM ></P +><UL +><LI +><P +> <EM +>What about Windows NT Policy Editor ?</EM +> + </P ><P ->To create or edit <TT +> To create or edit <TT CLASS="FILENAME" >ntconfig.pol</TT > you must use -the NT Server Policy Editor, <B + the NT Server Policy Editor, <B CLASS="COMMAND" >poledit.exe</B > which -is included with NT Server but <EM + is included with NT Server but <EM >not NT Workstation</EM >. -There is a Policy Editor on a NTws -but it is not suitable for creating <EM + There is a Policy Editor on a NTws + but it is not suitable for creating <EM >Domain Policies</EM >. -Further, although the Windows 95 -Policy Editor can be installed on an NT Workstation/Server, it will not -work with NT policies because the registry key that are set by the policy templates. -However, the files from the NT Server will run happily enough on an NTws. -You need <TT + Further, although the Windows 95 + Policy Editor can be installed on an NT Workstation/Server, it will not + work with NT policies because the registry key that are set by the policy templates. + However, the files from the NT Server will run happily enough on an NTws. + You need <TT CLASS="FILENAME" >poledit.exe, common.adm</TT > and <TT CLASS="FILENAME" >winnt.adm</TT >. It is convenient -to put the two *.adm files in <TT + to put the two *.adm files in <TT CLASS="FILENAME" >c:\winnt\inf</TT > which is where -the binary will look for them unless told otherwise. Note also that that -directory is 'hidden'.</P + the binary will look for them unless told otherwise. Note also that that + directory is 'hidden'. + </P ><P ->The Windows NT policy editor is also included with the -Service Pack 3 (and later) for Windows NT 4.0. Extract the files using -<B +> The Windows NT policy editor is also included with the Service Pack 3 (and + later) for Windows NT 4.0. Extract the files using <B CLASS="COMMAND" >servicepackname /x</B ->, ie thats <B +>, + ie thats <B CLASS="COMMAND" ->Nt4sp6ai.exe -/x</B -> for service pack 6a. The policy editor, <B +>Nt4sp6ai.exe /x</B +> for service pack 6a. The policy editor, + <B CLASS="COMMAND" >poledit.exe</B -> and the -associated template files (*.adm) should -be extracted as well. It is also possible to downloaded the policy template -files for Office97 and get a copy of the policy editor. Another possible -location is with the Zero Administration Kit available for download from Microsoft.</P +> and the associated template files (*.adm) should + be extracted as well. It is also possible to downloaded the policy template + files for Office97 and get a copy of the policy editor. Another possible + location is with the Zero Administration Kit available for download from Microsoft. + </P +></LI +><LI ><P -><EM +> <EM >Can Win95 do Policies ?</EM -></P +> + </P ><P ->Install the group policy handler for Win9x to pick up group -policies. Look on the Win98 CD in <TT +> Install the group policy handler for Win9x to pick up group + policies. Look on the Win98 CD in <TT CLASS="FILENAME" >\tools\reskit\netadmin\poledit</TT >. -Install group policies on a Win9x client by double-clicking -<TT + Install group policies on a Win9x client by double-clicking + <TT CLASS="FILENAME" >grouppol.inf</TT >. Log off and on again a couple of -times and see if Win98 picks up group policies. Unfortunately this needs -to be done on every Win9x machine that uses group policies....</P + times and see if Win98 picks up group policies. Unfortunately this needs + to be done on every Win9x machine that uses group policies.... + </P ><P ->If group policies don't work one reports suggests getting the updated -(read: working) grouppol.dll for Windows 9x. The group list is grabbed -from /etc/group.</P +> If group policies don't work one reports suggests getting the updated + (read: working) grouppol.dll for Windows 9x. The group list is grabbed + from /etc/group. + </P +></LI +><LI ><P -><EM +> <EM >How do I get 'User Manager' and 'Server Manager'</EM -></P +> + </P ><P ->Since I don't need to buy an NT Server CD now, how do I get -the 'User Manager for Domains', the 'Server Manager' ?</P +> Since I don't need to buy an NT Server CD now, how do I get + the 'User Manager for Domains', the 'Server Manager' ? + </P ><P ->Microsoft distributes a version of -these tools called nexus for installation on Windows 95 systems. The -tools set includes</P +> Microsoft distributes a version of these tools called nexus for + installation on Windows 95 systems. The tools set includes + </P ><P ></P ><UL @@ -4262,27 +4729,31 @@ tools set includes</P ></LI ></UL ><P ->Click here to download the archived file <A +> Click here to download the archived file <A HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE" TARGET="_top" >ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE</A -></P +> + </P ><P ->The Windows NT 4.0 version of the 'User Manager for -Domains' and 'Server Manager' are available from Microsoft via ftp -from <A +> The Windows NT 4.0 version of the 'User Manager for + Domains' and 'Server Manager' are available from Microsoft via ftp + from <A HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE" TARGET="_top" >ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</A -></P +> + </P +></LI +></UL ></DIV ><DIV CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN940" ->6.6. What other help can I get ?</A +NAME="AEN1015" +>6.7. What other help can I get ?</A ></H1 ><P >There are many sources of information available in the form @@ -4290,10 +4761,15 @@ of mailing lists, RFC's and documentation. The docs that come with the samba distribution contain very good explanations of general SMB topics such as browsing.</P ><P -><EM ->What are some diagnostics tools I can use to debug the domain logon -process and where can I find them?</EM ></P +><UL +><LI +><P +> <EM +>What are some diagnostics tools I can use to debug the domain logon + process and where can I find them?</EM +> + </P ><P > One of the best diagnostic tools for debugging problems is Samba itself. You can use the -d option for both smbd and nmbd to specifiy what @@ -4335,7 +4811,7 @@ CLASS="COMMAND" ></UL ><P > An SMB enabled version of tcpdump is available from - <A + <A HREF="http://www.tcpdump.org/" TARGET="_top" >http://www.tcpdup.org/</A @@ -4358,11 +4834,14 @@ TARGET="_top" local subnet. Be aware that Ethereal can read and write netmon formatted files. </P +></LI +><LI ><P -><EM +> <EM >How do I install 'Network Monitor' on an NT Workstation -or a Windows 9x box?</EM -></P + or a Windows 9x box?</EM +> + </P ><P > Installing netmon on an NT workstation requires a couple of steps. The following are for installing Netmon V4.00.349, which comes @@ -4457,14 +4936,11 @@ CLASS="FILENAME" information on how to do this. Copy the files from a working Netmon installation. </P -><DIV -CLASS="SECT2" -><HR><H2 -CLASS="SECT2" -><A -NAME="AEN987" ->6.6.1. URLs and similar</A -></H2 +></LI +><LI +><P +> The following is a list if helpful URLs and other links: + </P ><P ></P ><UL @@ -4529,43 +5005,43 @@ TARGET="_top" ></P ></LI ></UL -></DIV -><DIV -CLASS="SECT2" -><HR><H2 -CLASS="SECT2" -><A -NAME="AEN1011" ->6.6.2. Mailing Lists</A -></H2 +></LI +></UL ><P -><EM ->How do I get help from the mailing lists ?</EM ></P +><UL +><LI +><P +> <EM +>How do I get help from the mailing lists ?</EM +> + </P ><P ->There are a number of Samba related mailing lists. Go to <A +> There are a number of Samba related mailing lists. Go to <A HREF="http://samba.org" TARGET="_top" >http://samba.org</A >, click on your nearest mirror -and then click on <B + and then click on <B CLASS="COMMAND" >Support</B > and then click on <B CLASS="COMMAND" ->Samba related mailing lists</B ->.</P +> Samba related mailing lists</B +>. + </P ><P ->For questions relating to Samba TNG go to -<A +> For questions relating to Samba TNG go to + <A HREF="http://www.samba-tng.org/" TARGET="_top" >http://www.samba-tng.org/</A > -It has been requested that you don't post questions about Samba-TNG to the -main stream Samba lists.</P + It has been requested that you don't post questions about Samba-TNG to the + main stream Samba lists.</P ><P ->If you post a message to one of the lists please observe the following guide lines :</P +> If you post a message to one of the lists please observe the following guide lines : + </P ><P ></P ><UL @@ -4632,34 +5108,850 @@ main stream Samba lists.</P smb.conf in their attach directory ?</P ></LI ></UL +></LI +><LI ><P -><EM +> <EM >How do I get off the mailing lists ?</EM -></P +> + </P ><P >To have your name removed from a samba mailing list, go to the - same place you went to to get on it. Go to <A + same place you went to to get on it. Go to <A HREF="http://lists.samba.org/" TARGET="_top" >http://lists.samba.org</A ->, click - on your nearest mirror and then click on <B +>, + click on your nearest mirror and then click on <B CLASS="COMMAND" >Support</B > and - then click on <B + then click on <B CLASS="COMMAND" > Samba related mailing lists</B >. Or perhaps see - <A + <A HREF="http://lists.samba.org/mailman/roster/samba-ntdom" TARGET="_top" >here</A -></P +> + </P ><P > Please don't post messages to the list asking to be removed, you will just - be referred to the above address (unless that process failed in some way...) - </P + be referred to the above address (unless that process failed in some way...) + </P +></LI +></UL +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A +NAME="AEN1129" +>6.8. Domain Control for Windows 9x/ME</A +></H1 +><DIV +CLASS="NOTE" +><BLOCKQUOTE +CLASS="NOTE" +><P +><B +>Note: </B +>The following section contains much of the original +DOMAIN.txt file previously included with Samba. Much of +the material is based on what went into the book Special +Edition, Using Samba. (Richard Sharpe)</P +></BLOCKQUOTE +></DIV +><P +>A domain and a workgroup are exactly the same thing in terms of network +browsing. The difference is that a distributable authentication +database is associated with a domain, for secure login access to a +network. Also, different access rights can be granted to users if they +successfully authenticate against a domain logon server (NT server and +other systems based on NT server support this, as does at least Samba TNG now).</P +><P +>The SMB client logging on to a domain has an expectation that every other +server in the domain should accept the same authentication information. +Network browsing functionality of domains and workgroups is +identical and is explained in BROWSING.txt. It should be noted, that browsing +is total orthogonal to logon support.</P +><P +>Issues related to the single-logon network model are discussed in this +document. Samba supports domain logons, network logon scripts, and user +profiles for MS Windows for workgroups and MS Windows 9X clients.</P +><P +>When an SMB client in a domain wishes to logon it broadcast requests for a +logon server. The first one to reply gets the job, and validates its +password using whatever mechanism the Samba administrator has installed. +It is possible (but very stupid) to create a domain where the user +database is not shared between servers, ie they are effectively workgroup +servers advertising themselves as participating in a domain. This +demonstrates how authentication is quite different from but closely +involved with domains.</P +><P +>Another thing commonly associated with single-logon domains is remote +administration over the SMB protocol. Again, there is no reason why this +cannot be implemented with an underlying username database which is +different from the Windows NT SAM. Support for the Remote Administration +Protocol is planned for a future release of Samba.</P +><P +>Network logon support as discussed in this section is aimed at Window for +Workgroups, and Windows 9X clients. </P +><P +>Support for profiles is confirmed as working for Win95, NT 4.0 and NT 3.51. +It is possible to specify: the profile location; script file to be loaded +on login; the user's home directory; and for NT a kick-off time could also +now easily be supported. However, there are some differences between Win9X +profile support and WinNT profile support. These are discussed below.</P +><P +>With NT Workstations, all this does not require the use or intervention of +an NT 4.0 or NT 3.51 server: Samba can now replace the logon services +provided by an NT server, to a limited and experimental degree (for example, +running "User Manager for Domains" will not provide you with access to +a domain created by a Samba Server).</P +><P +>With Win95, the help of an NT server can be enlisted, both for profile storage +and for user authentication. For details on user authentication, see +security_level.txt. For details on profile storage, see below.</P +><P +>Using these features you can make your clients verify their logon via +the Samba server; make clients run a batch file when they logon to +the network and download their preferences, desktop and start menu.</P +><P +>Before launching into the configuration instructions, it is worthwhile looking +at how a Win9X client performs a logon:</P +><P +></P +><OL +TYPE="1" +><LI +><P +> The client broadcasts (to the IP broadcast address of the subnet it is in) + a NetLogon request. This is sent to the NetBIOS address DOMAIN<00> at the + NetBIOS layer. The client chooses the first response it receives, which + contains the NetBIOS name of the logon server to use in the format of + \\SERVER. + </P +></LI +><LI +><P +> The client then connects to that server, logs on (does an SMBsessetupX) and + then connects to the IPC$ share (using an SMBtconX). + </P +></LI +><LI +><P +> The client then does a NetWkstaUserLogon request, which retrieves the name + of the user's logon script. + </P +></LI +><LI +><P +> The client then connects to the NetLogon share and searches for this + and if it is found and can be read, is retrieved and executed by the client. + After this, the client disconnects from the NetLogon share. + </P +></LI +><LI +><P +> The client then sends a NetUserGetInfo request to the server, to retrieve + the user's home share, which is used to search for profiles. Since the + response to the NetUserGetInfo request does not contain much more + the user's home share, profiles for Win9X clients MUST reside in the user + home directory. + </P +></LI +><LI +><P +> The client then connects to the user's home share and searches for the + user's profile. As it turns out, you can specify the users home share as + a sharename and path. For example, \\server\fred\.profile. + If the profiles are found, they are implemented. + </P +></LI +><LI +><P +> The client then disconnects from the user's home share, and reconnects to + the NetLogon share and looks for CONFIG.POL, the policies file. If this is + found, it is read and implemented. + </P +></LI +></OL +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN1159" +>6.8.1. Configuration Instructions: Network Logons</A +></H2 +><P +>To use domain logons and profiles you need to do the following:</P +><P +></P +><OL +TYPE="1" +><LI +><P +> Create a share called [netlogon] in your smb.conf. This share should + be readable by all users, and probably should not be writeable. This + share will hold your network logon scripts, and the CONFIG.POL file + (Note: for details on the CONFIG.POL file, how to use it, what it is, + refer to the Microsoft Windows NT Administration documentation. + The format of these files is not known, so you will need to use + Microsoft tools). + </P +><P +> For example I have used: + </P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>[netlogon] + path = /data/dos/netlogon + writeable = no + guest ok = no</PRE +></TD +></TR +></TABLE +></P +><P +> Note that it is important that this share is not writeable by ordinary + users, in a secure environment: ordinary users should not be allowed + to modify or add files that another user's computer would then download + when they log in. + </P +></LI +><LI +><P +> in the [global] section of smb.conf set the following: + </P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>domain logons = yes +logon script = %U.bat + </PRE +></TD +></TR +></TABLE +></P +><P +> The choice of batch file is, of course, up to you. The above would + give each user a separate batch file as the %U will be changed to + their username automatically. The other standard % macros may also be + used. You can make the batch files come from a subdirectory by using + something like: + </P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>logon script = scripts\%U.bat + </PRE +></TD +></TR +></TABLE +></P +></LI +><LI +><P +> create the batch files to be run when the user logs in. If the batch + file doesn't exist then no batch file will be run. + </P +><P +> In the batch files you need to be careful to use DOS style cr/lf line + endings. If you don't then DOS may get confused. I suggest you use a + DOS editor to remotely edit the files if you don't know how to produce + DOS style files under unix. + </P +></LI +><LI +><P +> Use smbclient with the -U option for some users to make sure that + the \\server\NETLOGON share is available, the batch files are + visible and they are readable by the users. + </P +></LI +><LI +><P +> you will probabaly find that your clients automatically mount the + \\SERVER\NETLOGON share as drive z: while logging in. You can put + some useful programs there to execute from the batch files. + </P +></LI +></OL +><DIV +CLASS="WARNING" +><P +></P +><TABLE +CLASS="WARNING" +BORDER="1" +WIDTH="100%" +><TR +><TD +ALIGN="CENTER" +><B +>security mode and master browsers</B +></TD +></TR +><TR +><TD +ALIGN="LEFT" +><P +>There are a few comments to make in order to tie up some +loose ends. There has been much debate over the issue of whether +or not it is ok to configure Samba as a Domain Controller in security +modes other than <TT +CLASS="CONSTANT" +>USER</TT +>. The only security mode +which will not work due to technical reasons is <TT +CLASS="CONSTANT" +>SHARE</TT +> +mode security. <TT +CLASS="CONSTANT" +>DOMAIN</TT +> and <TT +CLASS="CONSTANT" +>SERVER</TT +> +mode security is really just a variation on SMB user level security.</P +><P +>Actually, this issue is also closer tied to the debate on whether +or not Samba must be the domain master browser for its workgroup +when operating as a DC. While it may technically be possible +to configure a server as such (after all, browsing and domain logons +are two distinctly different functions), it is not a good idea to +so. You should remember that the DC must register the DOMAIN#1b netbios +name. This is the name used by Windows clients to locate the DC. +Windows clients do not distinguish between the DC and the DMB. +For this reason, it is very wise to configure the Samba DC as the DMB.</P +><P +>Now back to the issue of configuring a Samba DC to use a mode other +than "security = user". If a Samba host is configured to use +another SMB server or DC in order to validate user connection +requests, then it is a fact that some other machine on the network +(the "password server") knows more about user than the Samba host. +99% of the time, this other host is a domain controller. Now +in order to operate in domain mode security, the "workgroup" parameter +must be set to the name of the Windows NT domain (which already +has a domain controller, right?)</P +><P +>Therefore configuring a Samba box as a DC for a domain that +already by definition has a PDC is asking for trouble. +Therefore, you should always configure the Samba DC to be the DMB +for its domain.</P +></TD +></TR +></TABLE +></DIV +></DIV +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN1193" +>6.8.2. Configuration Instructions: Setting up Roaming User Profiles</A +></H2 +><DIV +CLASS="WARNING" +><P +></P +><TABLE +CLASS="WARNING" +BORDER="1" +WIDTH="100%" +><TR +><TD +ALIGN="CENTER" +><B +>Warning</B +></TD +></TR +><TR +><TD +ALIGN="LEFT" +><P +><EM +>NOTE!</EM +> Roaming profiles support is different +for Win9X and WinNT.</P +></TD +></TR +></TABLE +></DIV +><P +>Before discussing how to configure roaming profiles, it is useful to see how +Win9X and WinNT clients implement these features.</P +><P +>Win9X clients send a NetUserGetInfo request to the server to get the user's +profiles location. However, the response does not have room for a separate +profiles location field, only the users home share. This means that Win9X +profiles are restricted to being in the user's home directory.</P +><P +>WinNT clients send a NetSAMLogon RPC request, which contains many fields, +including a separate field for the location of the user's profiles. +This means that support for profiles is different for Win9X and WinNT.</P +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN1201" +>6.8.2.1. Windows NT Configuration</A +></H3 +><P +>To support WinNT clients, inn the [global] section of smb.conf set the +following (for example):</P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath</PRE +></TD +></TR +></TABLE +></P +><P +>The default for this option is \\%N\%U\profile, namely +\\sambaserver\username\profile. The \\N%\%U service is created +automatically by the [homes] service. +If you are using a samba server for the profiles, you _must_ make the +share specified in the logon path browseable. </P +><DIV +CLASS="NOTE" +><BLOCKQUOTE +CLASS="NOTE" +><P +><B +>Note: </B +>[lkcl 26aug96 - we have discovered a problem where Windows clients can +maintain a connection to the [homes] share in between logins. The +[homes] share must NOT therefore be used in a profile path.]</P +></BLOCKQUOTE +></DIV +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN1209" +>6.8.2.2. Windows 9X Configuration</A +></H3 +><P +>To support Win9X clients, you must use the "logon home" parameter. Samba has +now been fixed so that "net use/home" now works as well, and it, too, relies +on the "logon home" parameter.</P +><P +>By using the logon home parameter, you are restricted to putting Win9X +profiles in the user's home directory. But wait! There is a trick you +can use. If you set the following in the [global] section of your +smb.conf file:</P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>logon home = \\%L\%U\.profiles</PRE +></TD +></TR +></TABLE +></P +><P +>then your Win9X clients will dutifully put their clients in a subdirectory +of your home directory called .profiles (thus making them hidden).</P +><P +>Not only that, but 'net use/home' will also work, because of a feature in +Win9X. It removes any directory stuff off the end of the home directory area +and only uses the server and share portion. That is, it looks like you +specified \\%L\%U for "logon home".</P +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN1217" +>6.8.2.3. Win9X and WinNT Configuration</A +></H3 +><P +>You can support profiles for both Win9X and WinNT clients by setting both the +"logon home" and "logon path" parameters. For example:</P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>logon home = \\%L\%U\.profiles +logon path = \\%L\profiles\%U</PRE +></TD +></TR +></TABLE +></P +><DIV +CLASS="NOTE" +><BLOCKQUOTE +CLASS="NOTE" +><P +><B +>Note: </B +>I have not checked what 'net use /home' does on NT when "logon home" is +set as above.</P +></BLOCKQUOTE +></DIV +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN1224" +>6.8.2.4. Windows 9X Profile Setup</A +></H3 +><P +>When a user first logs in on Windows 9X, the file user.DAT is created, +as are folders "Start Menu", "Desktop", "Programs" and "Nethood". +These directories and their contents will be merged with the local +versions stored in c:\windows\profiles\username on subsequent logins, +taking the most recent from each. You will need to use the [global] +options "preserve case = yes", "short case preserve = yes" and +"case sensitive = no" in order to maintain capital letters in shortcuts +in any of the profile folders.</P +><P +>The user.DAT file contains all the user's preferences. If you wish to +enforce a set of preferences, rename their user.DAT file to user.MAN, +and deny them write access to this file.</P +><P +></P +><OL +TYPE="1" +><LI +><P +> On the Windows 95 machine, go to Control Panel | Passwords and + select the User Profiles tab. Select the required level of + roaming preferences. Press OK, but do _not_ allow the computer + to reboot. + </P +></LI +><LI +><P +> On the Windows 95 machine, go to Control Panel | Network | + Client for Microsoft Networks | Preferences. Select 'Log on to + NT Domain'. Then, ensure that the Primary Logon is 'Client for + Microsoft Networks'. Press OK, and this time allow the computer + to reboot. + </P +></LI +></OL +><P +>Under Windows 95, Profiles are downloaded from the Primary Logon. +If you have the Primary Logon as 'Client for Novell Networks', then +the profiles and logon script will be downloaded from your Novell +Server. If you have the Primary Logon as 'Windows Logon', then the +profiles will be loaded from the local machine - a bit against the +concept of roaming profiles, if you ask me.</P +><P +>You will now find that the Microsoft Networks Login box contains +[user, password, domain] instead of just [user, password]. Type in +the samba server's domain name (or any other domain known to exist, +but bear in mind that the user will be authenticated against this +domain and profiles downloaded from it, if that domain logon server +supports it), user name and user's password.</P +><P +>Once the user has been successfully validated, the Windows 95 machine +will inform you that 'The user has not logged on before' and asks you +if you wish to save the user's preferences? Select 'yes'.</P +><P +>Once the Windows 95 client comes up with the desktop, you should be able +to examine the contents of the directory specified in the "logon path" +on the samba server and verify that the "Desktop", "Start Menu", +"Programs" and "Nethood" folders have been created.</P +><P +>These folders will be cached locally on the client, and updated when +the user logs off (if you haven't made them read-only by then :-). +You will find that if the user creates further folders or short-cuts, +that the client will merge the profile contents downloaded with the +contents of the profile directory already on the local client, taking +the newest folders and short-cuts from each set.</P +><P +>If you have made the folders / files read-only on the samba server, +then you will get errors from the w95 machine on logon and logout, as +it attempts to merge the local and the remote profile. Basically, if +you have any errors reported by the w95 machine, check the unix file +permissions and ownership rights on the profile directory contents, +on the samba server.</P +><P +>If you have problems creating user profiles, you can reset the user's +local desktop cache, as shown below. When this user then next logs in, +they will be told that they are logging in "for the first time".</P +><P +></P +><OL +TYPE="1" +><LI +><P +> instead of logging in under the [user, password, domain] dialog, + press escape. + </P +></LI +><LI +><P +> run the regedit.exe program, and look in: + </P +><P +> HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList + </P +><P +> you will find an entry, for each user, of ProfilePath. Note the + contents of this key (likely to be c:\windows\profiles\username), + then delete the key ProfilePath for the required user. + </P +><P +> [Exit the registry editor]. + </P +></LI +><LI +><P +> <EM +>WARNING</EM +> - before deleting the contents of the + directory listed in + the ProfilePath (this is likely to be c:\windows\profiles\username), + ask them if they have any important files stored on their desktop + or in their start menu. delete the contents of the directory + ProfilePath (making a backup if any of the files are needed). + </P +><P +> This will have the effect of removing the local (read-only hidden + system file) user.DAT in their profile directory, as well as the + local "desktop", "nethood", "start menu" and "programs" folders. + </P +></LI +><LI +><P +> search for the user's .PWL password-cacheing file in the c:\windows + directory, and delete it. + </P +></LI +><LI +><P +> log off the windows 95 client. + </P +></LI +><LI +><P +> check the contents of the profile path (see "logon path" described + above), and delete the user.DAT or user.MAN file for the user, + making a backup if required. + </P +></LI +></OL +><P +>If all else fails, increase samba's debug log levels to between 3 and 10, +and / or run a packet trace program such as tcpdump or netmon.exe, and +look for any error reports.</P +><P +>If you have access to an NT server, then first set up roaming profiles +and / or netlogons on the NT server. Make a packet trace, or examine +the example packet traces provided with NT server, and see what the +differences are with the equivalent samba trace.</P +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN1260" +>6.8.2.5. Windows NT Workstation 4.0</A +></H3 +><P +>When a user first logs in to a Windows NT Workstation, the profile +NTuser.DAT is created. The profile location can be now specified +through the "logon path" parameter. </P +><DIV +CLASS="NOTE" +><BLOCKQUOTE +CLASS="NOTE" +><P +><B +>Note: </B +>[lkcl 10aug97 - i tried setting the path to +\\samba-server\homes\profile, and discovered that this fails because +a background process maintains the connection to the [homes] share +which does _not_ close down in between user logins. you have to +have \\samba-server\%L\profile, where user is the username created +from the [homes] share].</P +></BLOCKQUOTE +></DIV +><P +>There is a parameter that is now available for use with NT Profiles: +"logon drive". This should be set to "h:" or any other drive, and +should be used in conjunction with the new "logon home" parameter.</P +><P +>The entry for the NT 4.0 profile is a _directory_ not a file. The NT +help on profiles mentions that a directory is also created with a .PDS +extension. The user, while logging in, must have write permission to +create the full profile path (and the folder with the .PDS extension) +[lkcl 10aug97 - i found that the creation of the .PDS directory failed, +and had to create these manually for each user, with a shell script. +also, i presume, but have not tested, that the full profile path must +be browseable just as it is for w95, due to the manner in which they +attempt to create the full profile path: test existence of each path +component; create path component].</P +><P +>In the profile directory, NT creates more folders than 95. It creates +"Application Data" and others, as well as "Desktop", "Nethood", +"Start Menu" and "Programs". The profile itself is stored in a file +NTuser.DAT. Nothing appears to be stored in the .PDS directory, and +its purpose is currently unknown.</P +><P +>You can use the System Control Panel to copy a local profile onto +a samba server (see NT Help on profiles: it is also capable of firing +up the correct location in the System Control Panel for you). The +NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN +turns a profile into a mandatory one.</P +><DIV +CLASS="NOTE" +><BLOCKQUOTE +CLASS="NOTE" +><P +><B +>Note: </B +>[lkcl 10aug97 - i notice that NT Workstation tells me that it is +downloading a profile from a slow link. whether this is actually the +case, or whether there is some configuration issue, as yet unknown, +that makes NT Workstation _think_ that the link is a slow one is a +matter to be resolved].</P +><P +>[lkcl 20aug97 - after samba digest correspondance, one user found, and +another confirmed, that profiles cannot be loaded from a samba server +unless "security = user" and "encrypt passwords = yes" (see the file +ENCRYPTION.txt) or "security = server" and "password server = ip.address. +of.yourNTserver" are used. either of these options will allow the NT +workstation to access the samba server using LAN manager encrypted +passwords, without the user intervention normally required by NT +workstation for clear-text passwords].</P +><P +>[lkcl 25aug97 - more comments received about NT profiles: the case of +the profile _matters_. the file _must_ be called NTuser.DAT or, for +a mandatory profile, NTuser.MAN].</P +></BLOCKQUOTE +></DIV +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN1273" +>6.8.2.6. Windows NT Server</A +></H3 +><P +>There is nothing to stop you specifying any path that you like for the +location of users' profiles. Therefore, you could specify that the +profile be stored on a samba server, or any other SMB server, as long as +that SMB server supports encrypted passwords.</P +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN1276" +>6.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</A +></H3 +><DIV +CLASS="WARNING" +><P +></P +><TABLE +CLASS="WARNING" +BORDER="1" +WIDTH="100%" +><TR +><TD +ALIGN="CENTER" +><B +>Potentially outdated or incorrect material follows</B +></TD +></TR +><TR +><TD +ALIGN="LEFT" +><P +>I think this is all bogus, but have not deleted it. (Richard Sharpe)</P +></TD +></TR +></TABLE +></DIV +><P +>The default logon path is \\%N\U%. NT Workstation will attempt to create +a directory "\\samba-server\username.PDS" if you specify the logon path +as "\\samba-server\username" with the NT User Manager. Therefore, you +will need to specify (for example) "\\samba-server\username\profile". +NT 4.0 will attempt to create "\\samba-server\username\profile.PDS", which +is more likely to succeed.</P +><P +>If you then want to share the same Start Menu / Desktop with W95, you will +need to specify "logon path = \\samba-server\username\profile" [lkcl 10aug97 +this has its drawbacks: i created a shortcut to telnet.exe, which attempts +to run from the c:\winnt\system32 directory. this directory is obviously +unlikely to exist on a Win95-only host].</P +><P +> If you have this set up correctly, you will find separate user.DAT and +NTuser.DAT files in the same profile directory.</P +><DIV +CLASS="NOTE" +><BLOCKQUOTE +CLASS="NOTE" +><P +><B +>Note: </B +>[lkcl 25aug97 - there are some issues to resolve with downloading of +NT profiles, probably to do with time/date stamps. i have found that +NTuser.DAT is never updated on the workstation after the first time that +it is copied to the local workstation profile directory. this is in +contrast to w95, where it _does_ transfer / update profiles correctly].</P +></BLOCKQUOTE +></DIV +></DIV ></DIV ></DIV ><DIV @@ -4667,12 +5959,35 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1050" ->6.7. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +NAME="AEN1286" +>6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A ></H1 +><DIV +CLASS="WARNING" +><P +></P +><TABLE +CLASS="WARNING" +BORDER="1" +WIDTH="100%" +><TR +><TD +ALIGN="CENTER" +><B +>Possibly Outdated Material</B +></TD +></TR +><TR +><TD +ALIGN="LEFT" ><P ->This appendix was originally authored by John H Terpstra of the Samba Team -and is included here for posterity.</P +> This appendix was originally authored by John H Terpstra of + the Samba Team and is included here for posterity. + </P +></TD +></TR +></TABLE +></DIV ><P ><EM >NOTE :</EM @@ -4688,12 +6003,9 @@ Windows NT SAM.</P ><P >Windows NT Server can be installed as either a plain file and print server (WORKGROUP workstation or server) or as a server that participates in Domain -Control (DOMAIN member, Primary Domain controller or Backup Domain controller).</P -><P ->The same is true for OS/2 Warp Server, Digital Pathworks and other similar -products, all of which can participate in Domain Control along with Windows NT. -However only those servers which have licensed Windows NT code in them can be -a primary Domain Controller (eg Windows NT Server, Advanced Server for Unix.)</P +Control (DOMAIN member, Primary Domain controller or Backup Domain controller). +The same is true for OS/2 Warp Server, Digital Pathworks and other similar +products, all of which can participate in Domain Control along with Windows NT.</P ><P >To many people these terms can be confusing, so let's try to clear the air.</P ><P @@ -4768,7 +6080,7 @@ within its registry.</P CLASS="CHAPTER" ><HR><H1 ><A -NAME="AEN1074" +NAME="AEN1311" >Chapter 7. Unifed Logons between Windows NT and UNIX using Winbind</A ></H1 ><DIV @@ -4776,7 +6088,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1092" +NAME="AEN1329" >7.1. Abstract</A ></H1 ><P @@ -4798,7 +6110,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1096" +NAME="AEN1333" >7.2. Introduction</A ></H1 ><P @@ -4852,7 +6164,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1109" +NAME="AEN1346" >7.3. What Winbind Provides</A ></H1 ><P @@ -4894,7 +6206,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1116" +NAME="AEN1353" >7.3.1. Target Uses</A ></H2 ><P @@ -4918,7 +6230,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1120" +NAME="AEN1357" >7.4. How Winbind Works</A ></H1 ><P @@ -4938,7 +6250,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1125" +NAME="AEN1362" >7.4.1. Microsoft Remote Procedure Calls</A ></H2 ><P @@ -4964,7 +6276,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1129" +NAME="AEN1366" >7.4.2. Name Service Switch</A ></H2 ><P @@ -5043,7 +6355,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1145" +NAME="AEN1382" >7.4.3. Pluggable Authentication Modules</A ></H2 ><P @@ -5092,7 +6404,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1153" +NAME="AEN1390" >7.4.4. User and Group ID Allocation</A ></H2 ><P @@ -5118,7 +6430,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1157" +NAME="AEN1394" >7.4.5. Result Caching</A ></H2 ><P @@ -5141,7 +6453,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1160" +NAME="AEN1397" >7.5. Installation and Configuration</A ></H1 ><P @@ -5172,7 +6484,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1166" +NAME="AEN1403" >7.6. Limitations</A ></H1 ><P @@ -5220,7 +6532,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1178" +NAME="AEN1415" >7.7. Conclusion</A ></H1 ><P @@ -5236,7 +6548,7 @@ NAME="AEN1178" CLASS="CHAPTER" ><HR><H1 ><A -NAME="AEN1181" +NAME="AEN1418" >Chapter 8. UNIX Permission Bits and WIndows NT Access Control Lists</A ></H1 ><DIV @@ -5244,7 +6556,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1192" +NAME="AEN1429" >8.1. Viewing and changing UNIX permissions using the NT security dialogs</A ></H1 @@ -5283,7 +6595,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1201" +NAME="AEN1438" >8.2. How to view file security on a Samba share</A ></H1 ><P @@ -5329,7 +6641,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1212" +NAME="AEN1449" >8.3. Viewing file ownership</A ></H1 ><P @@ -5415,7 +6727,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1232" +NAME="AEN1469" >8.4. Viewing file or directory permissions</A ></H1 ><P @@ -5477,7 +6789,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1247" +NAME="AEN1484" >8.4.1. File Permissions</A ></H2 ><P @@ -5539,7 +6851,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1261" +NAME="AEN1498" >8.4.2. Directory Permissions</A ></H2 ><P @@ -5571,7 +6883,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1268" +NAME="AEN1505" >8.5. Modifying file or directory permissions</A ></H1 ><P @@ -5669,7 +6981,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1290" +NAME="AEN1527" >8.6. Interaction with the standard Samba create mask parameters</A ></H1 @@ -5942,7 +7254,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1354" +NAME="AEN1591" >8.7. Interaction with the standard Samba file attribute mapping</A ></H1 @@ -5989,7 +7301,7 @@ CLASS="COMMAND" CLASS="CHAPTER" ><HR><H1 ><A -NAME="AEN1364" +NAME="AEN1601" >Chapter 9. OS2 Client HOWTO</A ></H1 ><DIV @@ -5997,7 +7309,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1375" +NAME="AEN1612" >9.1. FAQs</A ></H1 ><DIV @@ -6005,7 +7317,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1377" +NAME="AEN1614" >9.1.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?</A ></H2 @@ -6064,7 +7376,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1392" +NAME="AEN1629" >9.1.2. How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?</A ></H2 @@ -6117,7 +7429,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1401" +NAME="AEN1638" >9.1.3. Are there any other issues when OS/2 (any version) is used as a client?</A ></H2 @@ -6139,7 +7451,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1405" +NAME="AEN1642" >9.1.4. How do I get printer driver download working for OS/2 clients?</A ></H2 @@ -6183,6 +7495,178 @@ CLASS="REPLACEABLE" ></DIV ></DIV ></DIV +><DIV +CLASS="CHAPTER" +><HR><H1 +><A +NAME="AEN1651" +>Chapter 10. HOWTO Access Samba source code via CVS</A +></H1 +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN1658" +>10.1. Introduction</A +></H1 +><P +>Samba is developed in an open environnment. Developers use CVS +(Concurrent Versioning System) to "checkin" (also known as +"commit") new source code. Samba's various CVS branches can +be accessed via anonymouns CVS using the instructions +detailed in this chapter.</P +><P +>This document is a modified version of the instructions found at +<A +HREF="http://samba.org/samba/cvs.html" +TARGET="_top" +>http://samba.org/samba/cvs.html</A +></P +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A +NAME="AEN1663" +>10.2. CVS Access to samba.org</A +></H1 +><P +>The machine samba.org runs a publicly accessible CVS +repository for access to the source code of several packages, +including samba, rsync and jitterbug. There are two main ways of +accessing the CVS server on this host.</P +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN1666" +>10.2.1. Access via CVSweb</A +></H2 +><P +>You can access the source code via your +favourite WWW browser. This allows you to access the contents of +individual files in the repository and also to look at the revision +history and commit logs of individual files. You can also ask for a diff +listing between any two versions on the repository.</P +><P +>Use the URL : <A +HREF="http://samba.org/cgi-bin/cvsweb" +TARGET="_top" +>http://samba.org/cgi-bin/cvsweb</A +></P +></DIV +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN1671" +>10.2.2. Access via cvs</A +></H2 +><P +>You can also access the source code via a +normal cvs client. This gives you much more control over you can +do with the repository and allows you to checkout whole source trees +and keep them uptodate via normal cvs commands. This is the +preferred method of access if you are a developer and not +just a casual browser.</P +><P +>To download the latest cvs source code, point your +browser at the URL : <A +HREF="http://www.cyclic.com/" +TARGET="_top" +>http://www.cyclic.com/</A +>. +and click on the 'How to get cvs' link. CVS is free software under +the GNU GPL (as is Samba). Note that there are several graphical CVS clients +which provide a graphical interface to the sometimes mundane CVS commands. +Links to theses clients are also available from http://www.cyclic.com.</P +><P +>To gain access via anonymous cvs use the following steps. +For this example it is assumed that you want a copy of the +samba source code. For the other source code repositories +on this system just substitute the correct package name</P +><P +></P +><OL +TYPE="1" +><LI +><P +> Install a recent copy of cvs. All you really need is a + copy of the cvs client binary. + </P +></LI +><LI +><P +> Run the command + </P +><P +> <B +CLASS="COMMAND" +>cvs -d :pserver:cvs@samba.org:/cvsroot login</B +> + </P +><P +> When it asks you for a password type <TT +CLASS="USERINPUT" +><B +>cvs</B +></TT +>. + </P +></LI +><LI +><P +> Run the command + </P +><P +> <B +CLASS="COMMAND" +>cvs -d :pserver:cvs@samba.org:/cvsroot co samba</B +> + </P +><P +> This will create a directory called samba containing the + latest samba source code (i.e. the HEAD tagged cvs branch). This + currently corresponds to the 3.0 development tree. + </P +><P +> CVS branches other HEAD can be obtained by using the <TT +CLASS="PARAMETER" +><I +>-r</I +></TT +> + and defining a tag name. A list of branch tag names can be found on the + "Development" page of the samba web site. A common request is to obtain the + latest 2.2 release code. This could be done by using the following command. + </P +><P +> <B +CLASS="COMMAND" +>cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba</B +> + </P +></LI +><LI +><P +> Whenever you want to merge in the latest code changes use + the following command from within the samba directory: + </P +><P +> <B +CLASS="COMMAND" +>cvs update -d -P</B +> + </P +></LI +></OL +></DIV +></DIV +></DIV ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/Samba-PDC-HOWTO.html b/docs/htmldocs/Samba-PDC-HOWTO.html index 668f7f9aff..883de3a0ab 100644 --- a/docs/htmldocs/Samba-PDC-HOWTO.html +++ b/docs/htmldocs/Samba-PDC-HOWTO.html @@ -1,7 +1,7 @@ <HTML ><HEAD ><TITLE ->How to Configure Samba 2.2.x as a Primary Domain Controller</TITLE +>How to Configure Samba 2.2 as a Primary Domain Controller</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD @@ -20,7 +20,7 @@ CLASS="TITLEPAGE" CLASS="TITLE" ><A NAME="AEN1" ->How to Configure Samba 2.2.x as a Primary Domain Controller</A +>How to Configure Samba 2.2 as a Primary Domain Controller</A ></H1 ><HR></DIV ><DIV @@ -29,44 +29,127 @@ CLASS="SECT1" CLASS="SECT1" ><A NAME="AEN3" +>Prerequisite Reading</A +></H1 +><P +>Before you continue readingin this chapter, please make sure +that you are comfortable with configuring basic files services +in smb.conf and how to enable and administrate password +encryption in Samba. Theses two topics are covered in the +<A +HREF="smb.conf.5.html" +TARGET="_top" +><TT +CLASS="FILENAME" +>smb.conf(5)</TT +></A +> +manpage and the <A +HREF="EMCRYPTION.html" +TARGET="_top" +>Encryption chapter</A +> +of this HOWTO Collection.</P +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A +NAME="AEN9" >Background</A ></H1 +><DIV +CLASS="NOTE" +><BLOCKQUOTE +CLASS="NOTE" ><P +><B +>Note: </B ><I CLASS="EMPHASIS" >Author's Note :</I -> This document -is a combination of David Bannon's Samba 2.2 PDC HOWTO -and the Samba NT Domain FAQ. Both documents are superceeded by this one.</P +> This document is a combination +of David Bannon's Samba 2.2 PDC HOWTO and the Samba NT Domain FAQ. +Both documents are superceeded by this one.</P +></BLOCKQUOTE +></DIV ><P >Version of Samba prior to release 2.2 had marginal capabilities to -act as a Windows NT 4.0 Primary Domain Controller (PDC). The following -functionality should work in 2.2.0:</P +act as a Windows NT 4.0 Primary Domain Controller (PDC). Beginning with +Samba 2.2.0, we are proud to announce official support for Windows NT 4.0 +style domain logons from Windows NT 4.0 (through SP6) and Windows 2000 (through +SP1) clients. This article outlines the steps necessary for configuring Samba +as a PDC. It is necessary to have a working Samba server prior to implementing the +PDC functionality. If you have not followed the steps outlined in +<A +HREF="UNIX_INSTALL.html" +TARGET="_top" +> UNIX_INSTALL.html</A +>, please make sure +that your server is configured correctly before proceeding. Another good +resource in the <A +HREF="smb.conf.5.html" +TARGET="_top" +>smb.conf(5) man +page</A +>. The following functionality should work in 2.2:</P ><P ></P ><UL ><LI ><P ->domain logons for Windows NT 4.0/2000 clients</P +> domain logons for Windows NT 4.0/2000 clients. + </P ></LI ><LI ><P ->placing a Windows 9x client in user level security</P +> placing a Windows 9x client in user level security + </P ></LI ><LI ><P ->retrieving a list of users and groups from a Samba PDC to - Windows 9x/NT/2000 clients </P +> retrieving a list of users and groups from a Samba PDC to + Windows 9x/NT/2000 clients + </P ></LI ><LI ><P ->roving user profiles</P +> roving (roaming) user profiles + </P ></LI ><LI ><P ->Windows NT 4.0 style system policies</P +> Windows NT 4.0 style system policies + </P ></LI ></UL +><DIV +CLASS="WARNING" +><P +></P +><TABLE +CLASS="WARNING" +BORDER="1" +WIDTH="100%" +><TR +><TD +ALIGN="CENTER" +><B +>Windows 2000 Service Pack 2 Clients</B +></TD +></TR +><TR +><TD +ALIGN="LEFT" +><P +> Samba 2.2.1 is required for PDC functionality when using Windows 2000 + SP2 clients. + </P +></TD +></TR +></TABLE +></DIV ><P >The following pieces of functionality are not included in the 2.2 release:</P ><P @@ -74,21 +157,25 @@ functionality should work in 2.2.0:</P ><UL ><LI ><P ->Windows NT 4 domain trusts</P +> Windows NT 4 domain trusts + </P ></LI ><LI ><P ->Sam replication with Windows NT 4.0 Domain Controllers - (i.e. a Samba PDC and a Windows NT BDC or vice versa) </P +> SAM replication with Windows NT 4.0 Domain Controllers + (i.e. a Samba PDC and a Windows NT BDC or vice versa) + </P ></LI ><LI ><P ->Adding users via the User Manager for Domains</P +> Adding users via the User Manager for Domains + </P ></LI ><LI ><P ->Acting as a Windows 2000 Domain Controller (i.e. Kerberos - and Active Directory)</P +> Acting as a Windows 2000 Domain Controller (i.e. Kerberos and + Active Directory) + </P ></LI ></UL ><P @@ -98,25 +185,6 @@ support Windows 9x style domain logons is completely different from NT4 domain logons and has been officially supported for some time.</P ><P ->Beginning with Samba 2.2.0, we are proud to announce official -support for Windows NT 4.0 style domain logons from Windows NT -4.0 and Windows 2000 (including SP1) clients. This article -outlines the steps necessary for configuring Samba as a PDC. -Note that it is necessary to have a working Samba server -prior to implementing the PDC functionality. If you have not -followed the steps outlined in <A -HREF="UNIX_INSTALL.html" -TARGET="_top" ->UNIX_INSTALL.html</A ->, please make sure that your server -is configured correctly before proceeding. Another good -resource in the <A -HREF="smb.conf.5.html" -TARGET="_top" ->smb.conf(5) man -page</A ->.</P -><P >Implementing a Samba PDC can basically be divided into 2 broad steps.</P ><P @@ -125,13 +193,14 @@ steps.</P TYPE="1" ><LI ><P ->Configuring the Samba Domain Controller +> Configuring the Samba PDC </P ></LI ><LI ><P ->Creating machine trust accounts - and joining clients to the domain</P +> Creating machine trust accounts and joining clients + to the domain + </P ></LI ></OL ><P @@ -145,7 +214,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN40" +NAME="AEN49" >Configuring the Samba Domain Controller</A ></H1 ><P @@ -251,7 +320,7 @@ TARGET="_top" > = \\homeserver\%u ; specify a generic logon script for all users - ; this is a relative path to the [netlogon] share + ; this is a relative **DOS** path to the [netlogon] share <A HREF="smb.conf.5.html#LOGONSCRIPT" TARGET="_top" @@ -305,16 +374,14 @@ TARGET="_top" > = 0700</PRE ></P ><P ->There are a couple of points to emphasize in the above -configuration.</P +>There are a couple of points to emphasize in the above configuration.</P ><P ></P ><UL ><LI ><P ->encrypted passwords must be enabled. - For more details on how to do this, refer to - <A +> Encrypted passwords must be enabled. For more details on how + to do this, refer to <A HREF="ENCRYPTION.html" TARGET="_top" >ENCRYPTION.html</A @@ -323,23 +390,27 @@ TARGET="_top" ></LI ><LI ><P ->The server must support domain logons - and a <TT +> The server must support domain logons and a + <TT CLASS="FILENAME" >[netlogon]</TT -> share</P +> share + </P ></LI ><LI ><P ->The server must be the domain master browser - in order for Windows client to locate the server as a DC.</P +> The server must be the domain master browser in order for Windows + client to locate the server as a DC. Please refer to the various + Network Browsing documentation included with this distribution for + details. + </P ></LI ></UL ><P >As Samba 2.2 does not offer a complete implementation of group mapping between Windows NT groups and UNIX groups (this is really quite complicated to explain in a short space), you should refer to the <A -HREF="smb.conf.5.html#DOMAINADMONUSERS" +HREF="smb.conf.5.html#DOMAINADMINUSERS" TARGET="_top" >domain admin users</A @@ -356,28 +427,38 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN83" +NAME="AEN92" >Creating Machine Trust Accounts and Joining Clients to the Domain</A ></H1 ><P ->First you must understand what a machine trust account is and what -it is used for.</P -><P ->A machine trust account is a user account owned by a computer. +>A machine trust account is a samba user account owned by a computer. The account password acts as the shared secret for secure -communication with the Domain Controller. Hence the reason that -a Windows 9x host is never a true member of a domain because -it does not posses a machine trust account and thus has no shared -secret with the DC.</P +communication with the Domain Controller. This is a security feature +to prevent an unauthorized machine with the same netbios name from +joining the domain and gaining access to domain user/group accounts. +Hence a Windows 9x host is never a true member of a domain because it does +not posses a machine trust account, and thus has no shared secret with the DC.</P ><P >On a Windows NT PDC, these machine trust account passwords are stored -in the registry. A Samba PDC stores these accounts in he same location +in the registry. A Samba PDC stores these accounts in the same location as user LanMan and NT password hashes (currently <TT CLASS="FILENAME" >smbpasswd</TT >). -However, machine trust accounts only possess the NT password hash.</P +However, machine trust accounts only possess and use the NT password hash.</P +><P +>Because Samba requires machine accounts to possess a UNIX uid from +which an Windows NT SID can be generated, all of these accounts +must have an entry in <TT +CLASS="FILENAME" +>/etc/passwd</TT +> and smbpasswd. +Future releases will alleviate the need to create +<TT +CLASS="FILENAME" +>/etc/passwd</TT +> entries. </P ><P >There are two means of creating machine trust accounts.</P ><P @@ -385,30 +466,52 @@ However, machine trust accounts only possess the NT password hash.</P ><UL ><LI ><P ->Manual creation before joining the client - to the domain. In this case, the password is set to a known - value -- the lower case of the machine's netbios name.</P +> Manual creation before joining the client to the domain. In this case, + the password is set to a known value -- the lower case of the + machine's netbios name. + </P ></LI ><LI ><P ->Creation of the account at the time of - joining the domain. In this case, the session key of the - administrative account used to join the client to the domain acts - as an encryption key for setting the password to a random value.</P +> Creation of the account at the time of joining the domain. In + this case, the session key of the administrative account used to join + the client to the domain acts as an encryption key for setting the + password to a random value (This is the recommended method). + </P ></LI ></UL +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN106" +>Manually creating machine trust accounts</A +></H2 ><P ->Because Samba requires machine accounts to possess a UNIX uid from -which an Windows NT SID can be generated, all of these accounts -will have an entry in <TT -CLASS="FILENAME" ->/etc/passwd</TT -> and smbpasswd. -Future releases will alleviate the need to create -<TT -CLASS="FILENAME" ->/etc/passwd</TT -> entries.</P +>The first step in creating a machine trust account by hand is to +create an entry for the machine in /etc/passwd. This can be done +using <B +CLASS="COMMAND" +>vipw</B +> or any 'add userr' command which is normally +used to create new UNIX accounts. The following is an example for a Linux +based Samba server:</P +><P +><TT +CLASS="PROMPT" +>root# </TT +>/usr/sbin/useradd -g 100 -d /dev/null -c <TT +CLASS="REPLACEABLE" +><I +>machine_nickname</I +></TT +> -m -s /bin/false <TT +CLASS="REPLACEABLE" +><I +>machine_name</I +></TT +>$</P ><P >The <TT CLASS="FILENAME" @@ -423,20 +526,40 @@ CLASS="FILENAME" ><P ><PRE CLASS="PROGRAMLISTING" ->doppy$:x:505:501:NTMachine:/dev/null:/bin/false</PRE +>doppy$:x:505:501:<TT +CLASS="REPLACEABLE" +><I +>machine_nickname</I +></TT +>:/dev/null:/bin/false</PRE ></P ><P ->If you are manually creating the machine accounts, it is necessary -to add the <TT -CLASS="FILENAME" ->/etc/passwd</TT -> (or NIS passwd -map) entry prior to adding the <TT -CLASS="FILENAME" ->smbpasswd</TT -> -entry. The following command will create a new machine account -ready for use.</P +>Above, <TT +CLASS="REPLACEABLE" +><I +>machine_nickname</I +></TT +> can be any descriptive name for the +pc i.e. BasementComputer. The <TT +CLASS="REPLACEABLE" +><I +>machine_name</I +></TT +> absolutely must be +the netbios name of the pc to be added to the domain. The "$" must append the netbios +name of the pc or samba will not recognize this as a machine account</P +><P +>Now that the UNIX account has been created, the next step is to create +the smbpasswd entry for the machine containing the well known initial +trust account password. This can be done using the <A +HREF="smbpasswd.6.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbpasswd(8)</B +></A +> command +as shown here:</P ><P ><TT CLASS="PROMPT" @@ -454,167 +577,283 @@ CLASS="REPLACEABLE" >machine_name</I ></TT > is the machine's netbios -name.</P +name. </P +><DIV +CLASS="WARNING" ><P -><I -CLASS="EMPHASIS" ->If you manually create a machine account, immediately join -the client to the domain.</I -> An open account like this -can allow intruders to gain access to user account information -in your domain.</P -><P ->The second way of creating machine trust accounts is to add -them on the fly at the time the client is joined to the domain. -You will need to include a value for the -<A +></P +><TABLE +CLASS="WARNING" +BORDER="1" +WIDTH="100%" +><TR +><TD +ALIGN="CENTER" +><B +>Join the client to the domain immediately</B +></TD +></TR +><TR +><TD +ALIGN="LEFT" +><P +> Manually creating a machine trust account using this method is the + equivalent of creating a machine account on a Windows NT PDC using + the "Server Manager". From the time at which the account is created + to the time which th client joins the domain and changes the password, + your domain is vulnerable to an intruder joining your domain using a + a machine with the same netbios name. A PDC inherently trusts + members of the domain and will serve out a large degree of user + information to such clients. You have been warned! + </P +></TD +></TR +></TABLE +></DIV +></DIV +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN134" +>Creating machine trust accounts "on the fly"</A +></H2 +><P +>The second, and most recommended way of creating machine trust accounts +is to create them as needed at the time the client is joined to +the domain. You will need to include a value for the <A HREF="smb.conf.5.html#ADDUSERSCRIPT" TARGET="_top" >add user script</A > -parameter. Below is an example I use on a RedHat 6.2 Linux system.</P +parameter. Below is an example from a RedHat 6.2 Linux system.</P ><P ><PRE CLASS="PROGRAMLISTING" >add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u </PRE ></P ><P ->In Samba 2.2.0, <I +>In Samba 2.2.1, <I CLASS="EMPHASIS" >only the root account</I > can be used to create -machine accounts on the fly like this. Therefore, it is required -to create an entry in smbpasswd for <I +machine accounts like this. Therefore, it is required to create +an entry in smbpasswd for <I CLASS="EMPHASIS" >root</I ->. -The password <I +>. The password +<I CLASS="EMPHASIS" >SHOULD</I -> be set to s different -password that the associated <TT +> be set to s different password that the +associated <TT CLASS="FILENAME" >/etc/passwd</TT -> -entry for security reasons.</P +> entry for security reasons.</P +></DIV ></DIV ><DIV CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN122" +NAME="AEN145" >Common Problems and Errors</A ></H1 ><P ></P ><P -><I +></P +><UL +><LI +><P +> <I CLASS="EMPHASIS" >I cannot include a '$' in a machine name.</I -></P +> + </P ><P ->A 'machine name' in (typically) <TT +> A 'machine name' in (typically) <TT CLASS="FILENAME" >/etc/passwd</TT > -of the machine name with a '$' appended. FreeBSD (and other BSD -systems ?) won't create a user with a '$' in their name.</P + of the machine name with a '$' appended. FreeBSD (and other BSD + systems ?) won't create a user with a '$' in their name. + </P ><P ->The problem is only in the program used to make the entry, once -made, it works perfectly. So create a user without the '$' and -use <B +> The problem is only in the program used to make the entry, once + made, it works perfectly. So create a user without the '$' and + use <B CLASS="COMMAND" >vipw</B > to edit the entry, adding the '$'. Or create -the whole entry with vipw if you like, make sure you use a -unique uid !</P + the whole entry with vipw if you like, make sure you use a + unique uid ! + </P +></LI +><LI ><P -><I +> <I CLASS="EMPHASIS" >I get told "You already have a connection to the Domain...." -when creating a machine account.</I -></P -><P ->This happens if you try to create a machine account from the -machine itself and use a user name that does not work (for whatever -reason) and then try another (possibly valid) user name. -Exit out of the network applet to close the initial connection -and try again.</P + or "Cannot join domain, the credentials supplied conflict with an + existing set.." when creating a machine account.</I +> + </P ><P ->Further, if the machine is a already a 'member of a workgroup' that -is the same name as the domain you are joining (bad idea) you will -get this message. Change the workgroup name to something else, it -does not matter what, reboot, and try again.</P +> This happens if you try to create a machine account from the + machine itself and already have a connection (e.g. mapped drive) + to a share (or IPC$) on the Samba PDC. The following command + will remove all network drive connections: + </P ><P -><I -CLASS="EMPHASIS" ->I get told "Cannot join domain, the credentials supplied -conflict with an existing set.."</I -></P +> <TT +CLASS="PROMPT" +>C:\WINNT\></TT +> <B +CLASS="COMMAND" +>net use * /d</B +> + </P ><P ->This is the same basic problem as mentioned above, "You already -have a connection..."</P +> Further, if the machine is a already a 'member of a workgroup' that + is the same name as the domain you are joining (bad idea) you will + get this message. Change the workgroup name to something else, it + does not matter what, reboot, and try again. + </P +></LI +><LI ><P -><I +> <I CLASS="EMPHASIS" ->"The system can not log you on (C000019B)...."</I -></P +>The system can not log you on (C000019B)....</I +> + </P ><P >I joined the domain successfully but after upgrading -to a newer version of the Samba code I get the message, "The system -can not log you on (C000019B), Please try a gain or consult your -system administrator" when attempting to logon.</P + to a newer version of the Samba code I get the message, "The system + can not log you on (C000019B), Please try a gain or consult your + system administrator" when attempting to logon. + </P ><P ->This occurs when the domain SID stored in -<TT +> This occurs when the domain SID stored in + <TT CLASS="FILENAME" >private/WORKGROUP.SID</TT > is -changed. For example, you remove the file and <B + changed. For example, you remove the file and <B CLASS="COMMAND" >smbd</B > automatically -creates a new one. Or you are swapping back and forth between -versions 2.0.7, TNG and the HEAD branch code (not recommended). The -only way to correct the problem is to restore the original domain -SID or remove the domain client from the domain and rejoin.</P + creates a new one. Or you are swapping back and forth between + versions 2.0.7, TNG and the HEAD branch code (not recommended). The + only way to correct the problem is to restore the original domain + SID or remove the domain client from the domain and rejoin. + </P +></LI +><LI +><P +> <I +CLASS="EMPHASIS" +>The machine account for this computer either does not + exist or is not accessible.</I +> + </P ><P +> When I try to join the domain I get the message "The machine account + for this computer either does not exist or is not accessible". Whats + wrong? + </P +><P +> This problem is caused by the PDC not having a suitable machine account. + If you are using the <TT +CLASS="PARAMETER" ><I +>add user script</I +></TT +> method to create + accounts then this would indicate that it has not worked. Ensure the domain + admin user system is working. + </P +><P +> Alternatively if you are creating account entries manually then they + have not been created correctly. Make sure that you have the entry + correct for the machine account in smbpasswd file on the Samba PDC. + If you added the account using an editor rather than using the smbpasswd + utility, make sure that the account name is the machine netbios name + with a '$' appended to it ( ie. computer_name$ ). There must be an entry + in both /etc/passwd and the smbpasswd file. Some people have reported + that inconsistent subnet masks between the Samba server and the NT + client have caused this problem. Make sure that these are consistent + for both client and server. + </P +></LI +><LI +><P +> <I CLASS="EMPHASIS" ->"The machine account for this computer either does not -exist or is not accessible."</I -></P +>When I attempt to login to a Samba Domain from a NT4/W2K workstation, + I get a message about my account being disabled.</I +> + </P ><P ->When I try to join the domain I get the message "The machine account -for this computer either does not exist or is not accessible". Whats -wrong ?</P +> This problem is caused by a PAM related bug in Samba 2.2.0. This bug is + fixed in 2.2.1. Other symptoms could be unaccessible shares on + NT/W2K member servers in the domain or the following error in your smbd.log: + passdb/pampass.c:pam_account(268) PAM: UNKNOWN ERROR for User: %user% + </P ><P ->This problem is caused by the PDC not having a suitable machine account. -If you are using the <B +> At first be ensure to enable the useraccounts with <B CLASS="COMMAND" ->add user script =</B -> method to create -accounts then this would indicate that it has not worked. Ensure the domain -admin user system is working.</P -><P ->Alternatively if you are creating account entries manually then they -have not been created correctly. Make sure that you have the entry -correct for the machine account in smbpasswd file on the Samba PDC. -If you added the account using an editor rather than using the smbpasswd -utility, make sure that the account name is the machine netbios name -with a '$' appended to it ( ie. computer_name$ ). There must be an entry -in both /etc/passwd and the smbpasswd file. Some people have reported -that inconsistent subnet masks between the Samba server and the NT -client have caused this problem. Make sure that these are consistent -for both client and server.</P +>smbpasswd -e + %user%</B +>, this is normaly done, when you create an account. + </P +><P +> In order to work around this problem in 2.2.0, configure the + <TT +CLASS="PARAMETER" +><I +>account</I +></TT +> control flag in + <TT +CLASS="FILENAME" +>/etc/pam.d/samba</TT +> file as follows: + </P +><P +><PRE +CLASS="PROGRAMLISTING" +> account required pam_permit.so + </PRE +></P +><P +> If you want to remain backward compatibility to samba 2.0.x use + <TT +CLASS="FILENAME" +>pam_permit.so</TT +>, it's also possible to use + <TT +CLASS="FILENAME" +>pam_pwdb.so</TT +>. There are some bugs if you try to + use <TT +CLASS="FILENAME" +>pam_unix.so</TT +>, if you need this, be ensure to use + the most recent version of this file. + </P +></LI +></UL ></DIV ><DIV CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN150" +NAME="AEN193" >System Policies and Profiles</A ></H1 ><P @@ -630,97 +869,112 @@ Profiles and Policies in Windows NT 4.0</A ><P >Here are some additional details:</P ><P -><I +></P +><UL +><LI +><P +> <I CLASS="EMPHASIS" >What about Windows NT Policy Editor ?</I -></P +> + </P ><P ->To create or edit <TT +> To create or edit <TT CLASS="FILENAME" >ntconfig.pol</TT > you must use -the NT Server Policy Editor, <B + the NT Server Policy Editor, <B CLASS="COMMAND" >poledit.exe</B > which -is included with NT Server but <I + is included with NT Server but <I CLASS="EMPHASIS" >not NT Workstation</I >. -There is a Policy Editor on a NTws -but it is not suitable for creating <I + There is a Policy Editor on a NTws + but it is not suitable for creating <I CLASS="EMPHASIS" >Domain Policies</I >. -Further, although the Windows 95 -Policy Editor can be installed on an NT Workstation/Server, it will not -work with NT policies because the registry key that are set by the policy templates. -However, the files from the NT Server will run happily enough on an NTws. -You need <TT + Further, although the Windows 95 + Policy Editor can be installed on an NT Workstation/Server, it will not + work with NT policies because the registry key that are set by the policy templates. + However, the files from the NT Server will run happily enough on an NTws. + You need <TT CLASS="FILENAME" >poledit.exe, common.adm</TT > and <TT CLASS="FILENAME" >winnt.adm</TT >. It is convenient -to put the two *.adm files in <TT + to put the two *.adm files in <TT CLASS="FILENAME" >c:\winnt\inf</TT > which is where -the binary will look for them unless told otherwise. Note also that that -directory is 'hidden'.</P + the binary will look for them unless told otherwise. Note also that that + directory is 'hidden'. + </P ><P ->The Windows NT policy editor is also included with the -Service Pack 3 (and later) for Windows NT 4.0. Extract the files using -<B +> The Windows NT policy editor is also included with the Service Pack 3 (and + later) for Windows NT 4.0. Extract the files using <B CLASS="COMMAND" >servicepackname /x</B ->, ie thats <B +>, + ie thats <B CLASS="COMMAND" ->Nt4sp6ai.exe -/x</B -> for service pack 6a. The policy editor, <B +>Nt4sp6ai.exe /x</B +> for service pack 6a. The policy editor, + <B CLASS="COMMAND" >poledit.exe</B -> and the -associated template files (*.adm) should -be extracted as well. It is also possible to downloaded the policy template -files for Office97 and get a copy of the policy editor. Another possible -location is with the Zero Administration Kit available for download from Microsoft.</P +> and the associated template files (*.adm) should + be extracted as well. It is also possible to downloaded the policy template + files for Office97 and get a copy of the policy editor. Another possible + location is with the Zero Administration Kit available for download from Microsoft. + </P +></LI +><LI ><P -><I +> <I CLASS="EMPHASIS" >Can Win95 do Policies ?</I -></P +> + </P ><P ->Install the group policy handler for Win9x to pick up group -policies. Look on the Win98 CD in <TT +> Install the group policy handler for Win9x to pick up group + policies. Look on the Win98 CD in <TT CLASS="FILENAME" >\tools\reskit\netadmin\poledit</TT >. -Install group policies on a Win9x client by double-clicking -<TT + Install group policies on a Win9x client by double-clicking + <TT CLASS="FILENAME" >grouppol.inf</TT >. Log off and on again a couple of -times and see if Win98 picks up group policies. Unfortunately this needs -to be done on every Win9x machine that uses group policies....</P + times and see if Win98 picks up group policies. Unfortunately this needs + to be done on every Win9x machine that uses group policies.... + </P ><P ->If group policies don't work one reports suggests getting the updated -(read: working) grouppol.dll for Windows 9x. The group list is grabbed -from /etc/group.</P +> If group policies don't work one reports suggests getting the updated + (read: working) grouppol.dll for Windows 9x. The group list is grabbed + from /etc/group. + </P +></LI +><LI ><P -><I +> <I CLASS="EMPHASIS" >How do I get 'User Manager' and 'Server Manager'</I -></P +> + </P ><P ->Since I don't need to buy an NT Server CD now, how do I get -the 'User Manager for Domains', the 'Server Manager' ?</P +> Since I don't need to buy an NT Server CD now, how do I get + the 'User Manager for Domains', the 'Server Manager' ? + </P ><P ->Microsoft distributes a version of -these tools called nexus for installation on Windows 95 systems. The -tools set includes</P +> Microsoft distributes a version of these tools called nexus for + installation on Windows 95 systems. The tools set includes + </P ><P ></P ><UL @@ -738,26 +992,30 @@ tools set includes</P ></LI ></UL ><P ->Click here to download the archived file <A +> Click here to download the archived file <A HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE" TARGET="_top" >ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE</A -></P +> + </P ><P ->The Windows NT 4.0 version of the 'User Manager for -Domains' and 'Server Manager' are available from Microsoft via ftp -from <A +> The Windows NT 4.0 version of the 'User Manager for + Domains' and 'Server Manager' are available from Microsoft via ftp + from <A HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE" TARGET="_top" >ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</A -></P +> + </P +></LI +></UL ></DIV ><DIV CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN190" +NAME="AEN237" >What other help can I get ?</A ></H1 ><P @@ -766,11 +1024,16 @@ of mailing lists, RFC's and documentation. The docs that come with the samba distribution contain very good explanations of general SMB topics such as browsing.</P ><P -><I +></P +><UL +><LI +><P +> <I CLASS="EMPHASIS" >What are some diagnostics tools I can use to debug the domain logon -process and where can I find them?</I -></P + process and where can I find them?</I +> + </P ><P > One of the best diagnostic tools for debugging problems is Samba itself. You can use the -d option for both smbd and nmbd to specifiy what @@ -812,7 +1075,7 @@ CLASS="COMMAND" ></UL ><P > An SMB enabled version of tcpdump is available from - <A + <A HREF="http://www.tcpdump.org/" TARGET="_top" >http://www.tcpdup.org/</A @@ -835,12 +1098,15 @@ TARGET="_top" local subnet. Be aware that Ethereal can read and write netmon formatted files. </P +></LI +><LI ><P -><I +> <I CLASS="EMPHASIS" >How do I install 'Network Monitor' on an NT Workstation -or a Windows 9x box?</I -></P + or a Windows 9x box?</I +> + </P ><P > Installing netmon on an NT workstation requires a couple of steps. The following are for installing Netmon V4.00.349, which comes @@ -935,14 +1201,11 @@ CLASS="FILENAME" information on how to do this. Copy the files from a working Netmon installation. </P -><DIV -CLASS="SECT2" -><HR><H2 -CLASS="SECT2" -><A -NAME="AEN237" ->URLs and similar</A -></H2 +></LI +><LI +><P +> The following is a list if helpful URLs and other links: + </P ><P ></P ><UL @@ -1008,44 +1271,44 @@ TARGET="_top" ></P ></LI ></UL -></DIV -><DIV -CLASS="SECT2" -><HR><H2 -CLASS="SECT2" -><A -NAME="AEN261" ->Mailing Lists</A -></H2 +></LI +></UL ><P -><I +></P +><UL +><LI +><P +> <I CLASS="EMPHASIS" >How do I get help from the mailing lists ?</I -></P +> + </P ><P ->There are a number of Samba related mailing lists. Go to <A +> There are a number of Samba related mailing lists. Go to <A HREF="http://samba.org" TARGET="_top" >http://samba.org</A >, click on your nearest mirror -and then click on <B + and then click on <B CLASS="COMMAND" >Support</B > and then click on <B CLASS="COMMAND" ->Samba related mailing lists</B ->.</P +> Samba related mailing lists</B +>. + </P ><P ->For questions relating to Samba TNG go to -<A +> For questions relating to Samba TNG go to + <A HREF="http://www.samba-tng.org/" TARGET="_top" >http://www.samba-tng.org/</A > -It has been requested that you don't post questions about Samba-TNG to the -main stream Samba lists.</P + It has been requested that you don't post questions about Samba-TNG to the + main stream Samba lists.</P ><P ->If you post a message to one of the lists please observe the following guide lines :</P +> If you post a message to one of the lists please observe the following guide lines : + </P ><P ></P ><UL @@ -1113,35 +1376,799 @@ CLASS="EMPHASIS" smb.conf in their attach directory ?</P ></LI ></UL +></LI +><LI ><P -><I +> <I CLASS="EMPHASIS" >How do I get off the mailing lists ?</I -></P +> + </P ><P >To have your name removed from a samba mailing list, go to the - same place you went to to get on it. Go to <A + same place you went to to get on it. Go to <A HREF="http://lists.samba.org/" TARGET="_top" >http://lists.samba.org</A ->, click - on your nearest mirror and then click on <B +>, + click on your nearest mirror and then click on <B CLASS="COMMAND" >Support</B > and - then click on <B + then click on <B CLASS="COMMAND" > Samba related mailing lists</B >. Or perhaps see - <A + <A HREF="http://lists.samba.org/mailman/roster/samba-ntdom" TARGET="_top" >here</A -></P +> + </P ><P > Please don't post messages to the list asking to be removed, you will just - be referred to the above address (unless that process failed in some way...) - </P + be referred to the above address (unless that process failed in some way...) + </P +></LI +></UL +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A +NAME="AEN351" +>Domain Control for Windows 9x/ME</A +></H1 +><DIV +CLASS="NOTE" +><BLOCKQUOTE +CLASS="NOTE" +><P +><B +>Note: </B +>The following section contains much of the original +DOMAIN.txt file previously included with Samba. Much of +the material is based on what went into the book Special +Edition, Using Samba. (Richard Sharpe)</P +></BLOCKQUOTE +></DIV +><P +>A domain and a workgroup are exactly the same thing in terms of network +browsing. The difference is that a distributable authentication +database is associated with a domain, for secure login access to a +network. Also, different access rights can be granted to users if they +successfully authenticate against a domain logon server (NT server and +other systems based on NT server support this, as does at least Samba TNG now).</P +><P +>The SMB client logging on to a domain has an expectation that every other +server in the domain should accept the same authentication information. +Network browsing functionality of domains and workgroups is +identical and is explained in BROWSING.txt. It should be noted, that browsing +is total orthogonal to logon support.</P +><P +>Issues related to the single-logon network model are discussed in this +document. Samba supports domain logons, network logon scripts, and user +profiles for MS Windows for workgroups and MS Windows 9X clients.</P +><P +>When an SMB client in a domain wishes to logon it broadcast requests for a +logon server. The first one to reply gets the job, and validates its +password using whatever mechanism the Samba administrator has installed. +It is possible (but very stupid) to create a domain where the user +database is not shared between servers, ie they are effectively workgroup +servers advertising themselves as participating in a domain. This +demonstrates how authentication is quite different from but closely +involved with domains.</P +><P +>Another thing commonly associated with single-logon domains is remote +administration over the SMB protocol. Again, there is no reason why this +cannot be implemented with an underlying username database which is +different from the Windows NT SAM. Support for the Remote Administration +Protocol is planned for a future release of Samba.</P +><P +>Network logon support as discussed in this section is aimed at Window for +Workgroups, and Windows 9X clients. </P +><P +>Support for profiles is confirmed as working for Win95, NT 4.0 and NT 3.51. +It is possible to specify: the profile location; script file to be loaded +on login; the user's home directory; and for NT a kick-off time could also +now easily be supported. However, there are some differences between Win9X +profile support and WinNT profile support. These are discussed below.</P +><P +>With NT Workstations, all this does not require the use or intervention of +an NT 4.0 or NT 3.51 server: Samba can now replace the logon services +provided by an NT server, to a limited and experimental degree (for example, +running "User Manager for Domains" will not provide you with access to +a domain created by a Samba Server).</P +><P +>With Win95, the help of an NT server can be enlisted, both for profile storage +and for user authentication. For details on user authentication, see +security_level.txt. For details on profile storage, see below.</P +><P +>Using these features you can make your clients verify their logon via +the Samba server; make clients run a batch file when they logon to +the network and download their preferences, desktop and start menu.</P +><P +>Before launching into the configuration instructions, it is worthwhile looking +at how a Win9X client performs a logon:</P +><P +></P +><OL +TYPE="1" +><LI +><P +> The client broadcasts (to the IP broadcast address of the subnet it is in) + a NetLogon request. This is sent to the NetBIOS address DOMAIN<00> at the + NetBIOS layer. The client chooses the first response it receives, which + contains the NetBIOS name of the logon server to use in the format of + \\SERVER. + </P +></LI +><LI +><P +> The client then connects to that server, logs on (does an SMBsessetupX) and + then connects to the IPC$ share (using an SMBtconX). + </P +></LI +><LI +><P +> The client then does a NetWkstaUserLogon request, which retrieves the name + of the user's logon script. + </P +></LI +><LI +><P +> The client then connects to the NetLogon share and searches for this + and if it is found and can be read, is retrieved and executed by the client. + After this, the client disconnects from the NetLogon share. + </P +></LI +><LI +><P +> The client then sends a NetUserGetInfo request to the server, to retrieve + the user's home share, which is used to search for profiles. Since the + response to the NetUserGetInfo request does not contain much more + the user's home share, profiles for Win9X clients MUST reside in the user + home directory. + </P +></LI +><LI +><P +> The client then connects to the user's home share and searches for the + user's profile. As it turns out, you can specify the users home share as + a sharename and path. For example, \\server\fred\.profile. + If the profiles are found, they are implemented. + </P +></LI +><LI +><P +> The client then disconnects from the user's home share, and reconnects to + the NetLogon share and looks for CONFIG.POL, the policies file. If this is + found, it is read and implemented. + </P +></LI +></OL +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN381" +>Configuration Instructions: Network Logons</A +></H2 +><P +>To use domain logons and profiles you need to do the following:</P +><P +></P +><OL +TYPE="1" +><LI +><P +> Create a share called [netlogon] in your smb.conf. This share should + be readable by all users, and probably should not be writeable. This + share will hold your network logon scripts, and the CONFIG.POL file + (Note: for details on the CONFIG.POL file, how to use it, what it is, + refer to the Microsoft Windows NT Administration documentation. + The format of these files is not known, so you will need to use + Microsoft tools). + </P +><P +> For example I have used: + </P +><P +><PRE +CLASS="PROGRAMLISTING" +>[netlogon] + path = /data/dos/netlogon + writeable = no + guest ok = no</PRE +></P +><P +> Note that it is important that this share is not writeable by ordinary + users, in a secure environment: ordinary users should not be allowed + to modify or add files that another user's computer would then download + when they log in. + </P +></LI +><LI +><P +> in the [global] section of smb.conf set the following: + </P +><P +><PRE +CLASS="PROGRAMLISTING" +>domain logons = yes +logon script = %U.bat + </PRE +></P +><P +> The choice of batch file is, of course, up to you. The above would + give each user a separate batch file as the %U will be changed to + their username automatically. The other standard % macros may also be + used. You can make the batch files come from a subdirectory by using + something like: + </P +><P +><PRE +CLASS="PROGRAMLISTING" +>logon script = scripts\%U.bat + </PRE +></P +></LI +><LI +><P +> create the batch files to be run when the user logs in. If the batch + file doesn't exist then no batch file will be run. + </P +><P +> In the batch files you need to be careful to use DOS style cr/lf line + endings. If you don't then DOS may get confused. I suggest you use a + DOS editor to remotely edit the files if you don't know how to produce + DOS style files under unix. + </P +></LI +><LI +><P +> Use smbclient with the -U option for some users to make sure that + the \\server\NETLOGON share is available, the batch files are + visible and they are readable by the users. + </P +></LI +><LI +><P +> you will probabaly find that your clients automatically mount the + \\SERVER\NETLOGON share as drive z: while logging in. You can put + some useful programs there to execute from the batch files. + </P +></LI +></OL +><DIV +CLASS="WARNING" +><P +></P +><TABLE +CLASS="WARNING" +BORDER="1" +WIDTH="100%" +><TR +><TD +ALIGN="CENTER" +><B +>security mode and master browsers</B +></TD +></TR +><TR +><TD +ALIGN="LEFT" +><P +>There are a few comments to make in order to tie up some +loose ends. There has been much debate over the issue of whether +or not it is ok to configure Samba as a Domain Controller in security +modes other than <TT +CLASS="CONSTANT" +>USER</TT +>. The only security mode +which will not work due to technical reasons is <TT +CLASS="CONSTANT" +>SHARE</TT +> +mode security. <TT +CLASS="CONSTANT" +>DOMAIN</TT +> and <TT +CLASS="CONSTANT" +>SERVER</TT +> +mode security is really just a variation on SMB user level security.</P +><P +>Actually, this issue is also closer tied to the debate on whether +or not Samba must be the domain master browser for its workgroup +when operating as a DC. While it may technically be possible +to configure a server as such (after all, browsing and domain logons +are two distinctly different functions), it is not a good idea to +so. You should remember that the DC must register the DOMAIN#1b netbios +name. This is the name used by Windows clients to locate the DC. +Windows clients do not distinguish between the DC and the DMB. +For this reason, it is very wise to configure the Samba DC as the DMB.</P +><P +>Now back to the issue of configuring a Samba DC to use a mode other +than "security = user". If a Samba host is configured to use +another SMB server or DC in order to validate user connection +requests, then it is a fact that some other machine on the network +(the "password server") knows more about user than the Samba host. +99% of the time, this other host is a domain controller. Now +in order to operate in domain mode security, the "workgroup" parameter +must be set to the name of the Windows NT domain (which already +has a domain controller, right?)</P +><P +>Therefore configuring a Samba box as a DC for a domain that +already by definition has a PDC is asking for trouble. +Therefore, you should always configure the Samba DC to be the DMB +for its domain.</P +></TD +></TR +></TABLE +></DIV +></DIV +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN415" +>Configuration Instructions: Setting up Roaming User Profiles</A +></H2 +><DIV +CLASS="WARNING" +><P +></P +><TABLE +CLASS="WARNING" +BORDER="1" +WIDTH="100%" +><TR +><TD +ALIGN="CENTER" +><B +>Warning</B +></TD +></TR +><TR +><TD +ALIGN="LEFT" +><P +><I +CLASS="EMPHASIS" +>NOTE!</I +> Roaming profiles support is different +for Win9X and WinNT.</P +></TD +></TR +></TABLE +></DIV +><P +>Before discussing how to configure roaming profiles, it is useful to see how +Win9X and WinNT clients implement these features.</P +><P +>Win9X clients send a NetUserGetInfo request to the server to get the user's +profiles location. However, the response does not have room for a separate +profiles location field, only the users home share. This means that Win9X +profiles are restricted to being in the user's home directory.</P +><P +>WinNT clients send a NetSAMLogon RPC request, which contains many fields, +including a separate field for the location of the user's profiles. +This means that support for profiles is different for Win9X and WinNT.</P +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN423" +>Windows NT Configuration</A +></H3 +><P +>To support WinNT clients, inn the [global] section of smb.conf set the +following (for example):</P +><P +><PRE +CLASS="PROGRAMLISTING" +>logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath</PRE +></P +><P +>The default for this option is \\%N\%U\profile, namely +\\sambaserver\username\profile. The \\N%\%U service is created +automatically by the [homes] service. +If you are using a samba server for the profiles, you _must_ make the +share specified in the logon path browseable. </P +><DIV +CLASS="NOTE" +><BLOCKQUOTE +CLASS="NOTE" +><P +><B +>Note: </B +>[lkcl 26aug96 - we have discovered a problem where Windows clients can +maintain a connection to the [homes] share in between logins. The +[homes] share must NOT therefore be used in a profile path.]</P +></BLOCKQUOTE +></DIV +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN431" +>Windows 9X Configuration</A +></H3 +><P +>To support Win9X clients, you must use the "logon home" parameter. Samba has +now been fixed so that "net use/home" now works as well, and it, too, relies +on the "logon home" parameter.</P +><P +>By using the logon home parameter, you are restricted to putting Win9X +profiles in the user's home directory. But wait! There is a trick you +can use. If you set the following in the [global] section of your +smb.conf file:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>logon home = \\%L\%U\.profiles</PRE +></P +><P +>then your Win9X clients will dutifully put their clients in a subdirectory +of your home directory called .profiles (thus making them hidden).</P +><P +>Not only that, but 'net use/home' will also work, because of a feature in +Win9X. It removes any directory stuff off the end of the home directory area +and only uses the server and share portion. That is, it looks like you +specified \\%L\%U for "logon home".</P +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN439" +>Win9X and WinNT Configuration</A +></H3 +><P +>You can support profiles for both Win9X and WinNT clients by setting both the +"logon home" and "logon path" parameters. For example:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>logon home = \\%L\%U\.profiles +logon path = \\%L\profiles\%U</PRE +></P +><DIV +CLASS="NOTE" +><BLOCKQUOTE +CLASS="NOTE" +><P +><B +>Note: </B +>I have not checked what 'net use /home' does on NT when "logon home" is +set as above.</P +></BLOCKQUOTE +></DIV +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN446" +>Windows 9X Profile Setup</A +></H3 +><P +>When a user first logs in on Windows 9X, the file user.DAT is created, +as are folders "Start Menu", "Desktop", "Programs" and "Nethood". +These directories and their contents will be merged with the local +versions stored in c:\windows\profiles\username on subsequent logins, +taking the most recent from each. You will need to use the [global] +options "preserve case = yes", "short case preserve = yes" and +"case sensitive = no" in order to maintain capital letters in shortcuts +in any of the profile folders.</P +><P +>The user.DAT file contains all the user's preferences. If you wish to +enforce a set of preferences, rename their user.DAT file to user.MAN, +and deny them write access to this file.</P +><P +></P +><OL +TYPE="1" +><LI +><P +> On the Windows 95 machine, go to Control Panel | Passwords and + select the User Profiles tab. Select the required level of + roaming preferences. Press OK, but do _not_ allow the computer + to reboot. + </P +></LI +><LI +><P +> On the Windows 95 machine, go to Control Panel | Network | + Client for Microsoft Networks | Preferences. Select 'Log on to + NT Domain'. Then, ensure that the Primary Logon is 'Client for + Microsoft Networks'. Press OK, and this time allow the computer + to reboot. + </P +></LI +></OL +><P +>Under Windows 95, Profiles are downloaded from the Primary Logon. +If you have the Primary Logon as 'Client for Novell Networks', then +the profiles and logon script will be downloaded from your Novell +Server. If you have the Primary Logon as 'Windows Logon', then the +profiles will be loaded from the local machine - a bit against the +concept of roaming profiles, if you ask me.</P +><P +>You will now find that the Microsoft Networks Login box contains +[user, password, domain] instead of just [user, password]. Type in +the samba server's domain name (or any other domain known to exist, +but bear in mind that the user will be authenticated against this +domain and profiles downloaded from it, if that domain logon server +supports it), user name and user's password.</P +><P +>Once the user has been successfully validated, the Windows 95 machine +will inform you that 'The user has not logged on before' and asks you +if you wish to save the user's preferences? Select 'yes'.</P +><P +>Once the Windows 95 client comes up with the desktop, you should be able +to examine the contents of the directory specified in the "logon path" +on the samba server and verify that the "Desktop", "Start Menu", +"Programs" and "Nethood" folders have been created.</P +><P +>These folders will be cached locally on the client, and updated when +the user logs off (if you haven't made them read-only by then :-). +You will find that if the user creates further folders or short-cuts, +that the client will merge the profile contents downloaded with the +contents of the profile directory already on the local client, taking +the newest folders and short-cuts from each set.</P +><P +>If you have made the folders / files read-only on the samba server, +then you will get errors from the w95 machine on logon and logout, as +it attempts to merge the local and the remote profile. Basically, if +you have any errors reported by the w95 machine, check the unix file +permissions and ownership rights on the profile directory contents, +on the samba server.</P +><P +>If you have problems creating user profiles, you can reset the user's +local desktop cache, as shown below. When this user then next logs in, +they will be told that they are logging in "for the first time".</P +><P +></P +><OL +TYPE="1" +><LI +><P +> instead of logging in under the [user, password, domain] dialog, + press escape. + </P +></LI +><LI +><P +> run the regedit.exe program, and look in: + </P +><P +> HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList + </P +><P +> you will find an entry, for each user, of ProfilePath. Note the + contents of this key (likely to be c:\windows\profiles\username), + then delete the key ProfilePath for the required user. + </P +><P +> [Exit the registry editor]. + </P +></LI +><LI +><P +> <I +CLASS="EMPHASIS" +>WARNING</I +> - before deleting the contents of the + directory listed in + the ProfilePath (this is likely to be c:\windows\profiles\username), + ask them if they have any important files stored on their desktop + or in their start menu. delete the contents of the directory + ProfilePath (making a backup if any of the files are needed). + </P +><P +> This will have the effect of removing the local (read-only hidden + system file) user.DAT in their profile directory, as well as the + local "desktop", "nethood", "start menu" and "programs" folders. + </P +></LI +><LI +><P +> search for the user's .PWL password-cacheing file in the c:\windows + directory, and delete it. + </P +></LI +><LI +><P +> log off the windows 95 client. + </P +></LI +><LI +><P +> check the contents of the profile path (see "logon path" described + above), and delete the user.DAT or user.MAN file for the user, + making a backup if required. + </P +></LI +></OL +><P +>If all else fails, increase samba's debug log levels to between 3 and 10, +and / or run a packet trace program such as tcpdump or netmon.exe, and +look for any error reports.</P +><P +>If you have access to an NT server, then first set up roaming profiles +and / or netlogons on the NT server. Make a packet trace, or examine +the example packet traces provided with NT server, and see what the +differences are with the equivalent samba trace.</P +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN482" +>Windows NT Workstation 4.0</A +></H3 +><P +>When a user first logs in to a Windows NT Workstation, the profile +NTuser.DAT is created. The profile location can be now specified +through the "logon path" parameter. </P +><DIV +CLASS="NOTE" +><BLOCKQUOTE +CLASS="NOTE" +><P +><B +>Note: </B +>[lkcl 10aug97 - i tried setting the path to +\\samba-server\homes\profile, and discovered that this fails because +a background process maintains the connection to the [homes] share +which does _not_ close down in between user logins. you have to +have \\samba-server\%L\profile, where user is the username created +from the [homes] share].</P +></BLOCKQUOTE +></DIV +><P +>There is a parameter that is now available for use with NT Profiles: +"logon drive". This should be set to "h:" or any other drive, and +should be used in conjunction with the new "logon home" parameter.</P +><P +>The entry for the NT 4.0 profile is a _directory_ not a file. The NT +help on profiles mentions that a directory is also created with a .PDS +extension. The user, while logging in, must have write permission to +create the full profile path (and the folder with the .PDS extension) +[lkcl 10aug97 - i found that the creation of the .PDS directory failed, +and had to create these manually for each user, with a shell script. +also, i presume, but have not tested, that the full profile path must +be browseable just as it is for w95, due to the manner in which they +attempt to create the full profile path: test existence of each path +component; create path component].</P +><P +>In the profile directory, NT creates more folders than 95. It creates +"Application Data" and others, as well as "Desktop", "Nethood", +"Start Menu" and "Programs". The profile itself is stored in a file +NTuser.DAT. Nothing appears to be stored in the .PDS directory, and +its purpose is currently unknown.</P +><P +>You can use the System Control Panel to copy a local profile onto +a samba server (see NT Help on profiles: it is also capable of firing +up the correct location in the System Control Panel for you). The +NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN +turns a profile into a mandatory one.</P +><DIV +CLASS="NOTE" +><BLOCKQUOTE +CLASS="NOTE" +><P +><B +>Note: </B +>[lkcl 10aug97 - i notice that NT Workstation tells me that it is +downloading a profile from a slow link. whether this is actually the +case, or whether there is some configuration issue, as yet unknown, +that makes NT Workstation _think_ that the link is a slow one is a +matter to be resolved].</P +><P +>[lkcl 20aug97 - after samba digest correspondance, one user found, and +another confirmed, that profiles cannot be loaded from a samba server +unless "security = user" and "encrypt passwords = yes" (see the file +ENCRYPTION.txt) or "security = server" and "password server = ip.address. +of.yourNTserver" are used. either of these options will allow the NT +workstation to access the samba server using LAN manager encrypted +passwords, without the user intervention normally required by NT +workstation for clear-text passwords].</P +><P +>[lkcl 25aug97 - more comments received about NT profiles: the case of +the profile _matters_. the file _must_ be called NTuser.DAT or, for +a mandatory profile, NTuser.MAN].</P +></BLOCKQUOTE +></DIV +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN495" +>Windows NT Server</A +></H3 +><P +>There is nothing to stop you specifying any path that you like for the +location of users' profiles. Therefore, you could specify that the +profile be stored on a samba server, or any other SMB server, as long as +that SMB server supports encrypted passwords.</P +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN498" +>Sharing Profiles between W95 and NT Workstation 4.0</A +></H3 +><DIV +CLASS="WARNING" +><P +></P +><TABLE +CLASS="WARNING" +BORDER="1" +WIDTH="100%" +><TR +><TD +ALIGN="CENTER" +><B +>Potentially outdated or incorrect material follows</B +></TD +></TR +><TR +><TD +ALIGN="LEFT" +><P +>I think this is all bogus, but have not deleted it. (Richard Sharpe)</P +></TD +></TR +></TABLE +></DIV +><P +>The default logon path is \\%N\U%. NT Workstation will attempt to create +a directory "\\samba-server\username.PDS" if you specify the logon path +as "\\samba-server\username" with the NT User Manager. Therefore, you +will need to specify (for example) "\\samba-server\username\profile". +NT 4.0 will attempt to create "\\samba-server\username\profile.PDS", which +is more likely to succeed.</P +><P +>If you then want to share the same Start Menu / Desktop with W95, you will +need to specify "logon path = \\samba-server\username\profile" [lkcl 10aug97 +this has its drawbacks: i created a shortcut to telnet.exe, which attempts +to run from the c:\winnt\system32 directory. this directory is obviously +unlikely to exist on a Win95-only host].</P +><P +> If you have this set up correctly, you will find separate user.DAT and +NTuser.DAT files in the same profile directory.</P +><DIV +CLASS="NOTE" +><BLOCKQUOTE +CLASS="NOTE" +><P +><B +>Note: </B +>[lkcl 25aug97 - there are some issues to resolve with downloading of +NT profiles, probably to do with time/date stamps. i have found that +NTuser.DAT is never updated on the workstation after the first time that +it is copied to the local workstation profile directory. this is in +contrast to w95, where it _does_ transfer / update profiles correctly].</P +></BLOCKQUOTE +></DIV +></DIV ></DIV ></DIV ><DIV @@ -1149,12 +2176,35 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN300" +NAME="AEN508" >DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A ></H1 +><DIV +CLASS="WARNING" ><P ->This appendix was originally authored by John H Terpstra of the Samba Team -and is included here for posterity.</P +></P +><TABLE +CLASS="WARNING" +BORDER="1" +WIDTH="100%" +><TR +><TD +ALIGN="CENTER" +><B +>Possibly Outdated Material</B +></TD +></TR +><TR +><TD +ALIGN="LEFT" +><P +> This appendix was originally authored by John H Terpstra of + the Samba Team and is included here for posterity. + </P +></TD +></TR +></TABLE +></DIV ><P ><I CLASS="EMPHASIS" @@ -1171,12 +2221,9 @@ Windows NT SAM.</P ><P >Windows NT Server can be installed as either a plain file and print server (WORKGROUP workstation or server) or as a server that participates in Domain -Control (DOMAIN member, Primary Domain controller or Backup Domain controller).</P -><P ->The same is true for OS/2 Warp Server, Digital Pathworks and other similar -products, all of which can participate in Domain Control along with Windows NT. -However only those servers which have licensed Windows NT code in them can be -a primary Domain Controller (eg Windows NT Server, Advanced Server for Unix.)</P +Control (DOMAIN member, Primary Domain controller or Backup Domain controller). +The same is true for OS/2 Warp Server, Digital Pathworks and other similar +products, all of which can participate in Domain Control along with Windows NT.</P ><P >To many people these terms can be confusing, so let's try to clear the air.</P ><P diff --git a/docs/htmldocs/make_smbcodepage.1.html b/docs/htmldocs/make_smbcodepage.1.html index 52eb12e527..8e792e3122 100644 --- a/docs/htmldocs/make_smbcodepage.1.html +++ b/docs/htmldocs/make_smbcodepage.1.html @@ -14,7 +14,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="FINDSMB" +NAME="MAKE-SMBCODEPAGE" >make_smbcodepage</A ></H1 ><DIV @@ -104,24 +104,24 @@ CLASS="PARAMETER" >inputfile</DT ><DD ><P ->This is the input file to process. In t - he '<TT +>This is the input file to process. In + the <TT CLASS="PARAMETER" ><I >c</I ></TT ->' case this will be a text +> case this will be a text codepage definition file such as the ones found in the Samba <TT CLASS="FILENAME" >source/codepages</TT > directory. In - the '<TT + the <TT CLASS="PARAMETER" ><I >d</I ></TT ->' case this will be the +> case this will be the binary format codepage definition file normally found in the <TT CLASS="FILENAME" diff --git a/docs/htmldocs/make_unicodemap.1.html b/docs/htmldocs/make_unicodemap.1.html new file mode 100644 index 0000000000..a0b8740693 --- /dev/null +++ b/docs/htmldocs/make_unicodemap.1.html @@ -0,0 +1,276 @@ +<HTML +><HEAD +><TITLE +>make_unicodemap</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD +><BODY +CLASS="REFENTRY" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><H1 +><A +NAME="MAKE-UNICODEMAP" +>make_unicodemap</A +></H1 +><DIV +CLASS="REFNAMEDIV" +><A +NAME="AEN5" +></A +><H2 +>Name</H2 +>make_unicodemap -- construct a unicode map file for Samba</DIV +><DIV +CLASS="REFSYNOPSISDIV" +><A +NAME="AEN8" +></A +><H2 +>Synopsis</H2 +><P +><B +CLASS="COMMAND" +>make_unicodemap</B +> {codepage} {inputfile} {outputfile}</P +></DIV +><DIV +CLASS="REFSECT1" +><A +NAME="AEN14" +></A +><H2 +>DESCRIPTION</H2 +><P +> This tool is part of the <A +HREF="samba.7.html" +TARGET="_top" +>Samba</A +> + suite. + </P +><P +> <B +CLASS="COMMAND" +>make_unicodemap</B +> compiles text unicode map + files into binary unicodef map files for use with the + internationalization features of Samba 2.2. + </P +></DIV +><DIV +CLASS="REFSECT1" +><A +NAME="AEN20" +></A +><H2 +>OPTIONS</H2 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +>codepage</DT +><DD +><P +>This is the codepage or UNIX character + set we are processing (a number, e.g. 850). + </P +></DD +><DT +>inputfile</DT +><DD +><P +>This is the input file to process. This is a + text unicode map file such as the ones found in the Samba + <TT +CLASS="FILENAME" +>source/codepages</TT +> directory. + </P +></DD +><DT +>outputfile</DT +><DD +><P +>This is the binary output file to produce. + </P +></DD +></DL +></DIV +></DIV +><DIV +CLASS="REFSECT1" +><A +NAME="AEN36" +></A +><H2 +>Samba Unicode Map Files</H2 +><P +> A text Samba unicode map file is a description that tells Samba + how to map characters from a specified DOS code page or UNIX character + set to 16 bit unicode. + </P +><P +>A binary Samba unicode map file is a binary representation + of the same information, including a value that specifies what + codepage or UNIX character set this file is describing. + </P +></DIV +><DIV +CLASS="REFSECT1" +><A +NAME="AEN40" +></A +><H2 +>Files</H2 +><P +><TT +CLASS="FILENAME" +>CP<codepage>.TXT</TT +></P +><P +> These are the input (text) unicode map files provided + in the Samba <TT +CLASS="FILENAME" +>source/codepages</TT +> + directory. + </P +><P +> A text unicode map file consists of multiple lines + containing two fields. These fields are : + </P +><P +></P +><UL +><LI +><P +><TT +CLASS="PARAMETER" +><I +>character</I +></TT +> - which is + the (hex) character mapped on this line. + </P +></LI +><LI +><P +><TT +CLASS="PARAMETER" +><I +>unicode</I +></TT +> - which + is the (hex) 16 bit unicode character that the character + will map to. + </P +></LI +></UL +><P +> <TT +CLASS="FILENAME" +>unicode_map.<codepage></TT +> - These are + the output (binary) unicode map files produced and placed in + the Samba destination <TT +CLASS="FILENAME" +>lib/codepage</TT +> + directory. + </P +></DIV +><DIV +CLASS="REFSECT1" +><A +NAME="AEN57" +></A +><H2 +>Installation</H2 +><P +> The location of the server and its support files is a matter + for individual system administrators. The following are thus + suggestions only. + </P +><P +> It is recommended that the <B +CLASS="COMMAND" +>make_unicodemap</B +> + program be installed under the + <TT +CLASS="FILENAME" +>$prefix/samba</TT +> hierarchy, + in a directory readable by all, writeable only by root. The + program itself should be executable by all. The program + should NOT be setuid or setgid! + </P +></DIV +><DIV +CLASS="REFSECT1" +><A +NAME="AEN63" +></A +><H2 +>VERSION</H2 +><P +>This man page is correct for version 2.2 of + the Samba suite.</P +></DIV +><DIV +CLASS="REFSECT1" +><A +NAME="AEN66" +></A +><H2 +>SEE ALSO</H2 +><P +><A +HREF="smbd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbd(8)</B +></A +>, + <A +HREF="smb.conf.5.html" +TARGET="_top" +>smb.conf(5)</A +> + </P +></DIV +><DIV +CLASS="REFSECT1" +><A +NAME="AEN72" +></A +><H2 +>AUTHOR</H2 +><P +>The original Samba software and related utilities + were created by Andrew Tridgell. Samba is now developed + by the Samba Team as an Open Source project similar + to the way the Linux kernel is developed.</P +><P +>The original Samba man pages were written by Karl Auer. + The man page sources were converted to YODL format (another + excellent piece of Open Source software, available at + <A +HREF="ftp://ftp.icce.rug.nl/pub/unix/" +TARGET="_top" +> ftp://ftp.icce.rug.nl/pub/unix/</A +>) and updated for the Samba 2.0 + release by Jeremy Allison. The conversion to DocBook for + Samba 2.2 was done by Gerald Carter</P +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/htmldocs/printer_driver2.html b/docs/htmldocs/printer_driver2.html index ac845b8433..c44d9c5bf8 100644 --- a/docs/htmldocs/printer_driver2.html +++ b/docs/htmldocs/printer_driver2.html @@ -83,23 +83,61 @@ TARGET="_top" information</P ></LI ></UL +><P +>There has been some initial confusion about what all this means +and whether or not it is a requirement for printer drivers to be +installed on a Samba host in order to support printing from Windows +clients. A bug existed in Samba 2.2.0 which made Windows NT/2000 clients +require that the Samba server possess a valid driver for the printer. +This is fixed in Samba 2.2.1 and once again, Windows NT/2000 clients +can use the local APW for installing drivers to be used with a Samba +served printer. This is the same behavior exhibited by Windows 9x clients. +As a side note, Samba does not use these drivers in any way to process +spooled files. They are utilized entirely by the clients.</P +><P +>The following MS KB article, may be of some help if you are dealing with +Windows 2000 clients: <I +CLASS="EMPHASIS" +>How to Add Printers with No User +Interaction in Windows 2000</I +></P +><P +><A +HREF="http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP" +TARGET="_top" +>http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP</A +></P ></DIV ><DIV CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN20" +NAME="AEN25" >Configuration</A ></H1 +><DIV +CLASS="WARNING" ><P -><I -CLASS="EMPHASIS" ->WARNING!!!</I -> Previous versions of Samba -recommended using a share named [printer$]. This name was taken from the -printer$ service created by Windows 9x clients when a -printer was shared. Windows 9x printer servers always have +></P +><TABLE +CLASS="WARNING" +BORDER="1" +WIDTH="100%" +><TR +><TD +ALIGN="CENTER" +><B +>[print$] vs. [printer$]</B +></TD +></TR +><TR +><TD +ALIGN="LEFT" +><P +>Previous versions of Samba recommended using a share named [printer$]. +This name was taken from the printer$ service created by Windows 9x +clients when a printer was shared. Windows 9x printer servers always have a printer$ service which provides read-only access via no password in order to support printer driver downloads.</P ><P @@ -124,21 +162,26 @@ the client.</P >These parameters, including <TT CLASS="PARAMETER" ><I ->printer driver +>printer driver file</I ></TT > parameter, are being depreciated and should not be used in new installations. For more information on this change, you should refer to the <A HREF="#MIGRATION" ->Migration section </A ->of this document.</P +>Migration section</A +> +of this document.</P +></TD +></TR +></TABLE +></DIV ><DIV CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN30" +NAME="AEN36" >Creating [print$]</A ></H2 ><P @@ -161,6 +204,11 @@ CLASS="PROGRAMLISTING" guest ok = yes browseable = yes read only = yes + ; since this share is configured as read only, then we need + ; a 'write list'. Check the file system permissions to make + ; sure this account can copy files to the share. If this + ; is setup to a non-root account, then it should also exist + ; as a 'printer admin' write list = ntadmin</PRE ></P ><P @@ -178,16 +226,17 @@ level user accounts to have write access in order to update files on the share. See the <A HREF="smb./conf.5.html" TARGET="_top" ->smb.conf(5) man page</A -> for more information on -configuring file shares.</P +>smb.conf(5) +man page</A +> for more information on configuring file shares.</P ><P >The requirement for <A HREF="smb.conf.5.html#GUESTOK" TARGET="_top" ><B CLASS="COMMAND" ->guest ok = yes</B +>guest +ok = yes</B ></A > depends upon how your site is configured. If users will be guaranteed to have @@ -257,26 +306,26 @@ ALIGN="CENTER" ALIGN="LEFT" ><P >In order to currently add a new driver to you Samba host, - one of two conditions must hold true:</P +one of two conditions must hold true:</P ><P ></P ><UL ><LI ><P >The account used to connect to the Samba host - must have a uid of 0 (i.e. a root account)</P + must have a uid of 0 (i.e. a root account)</P ></LI ><LI ><P >The account used to connect to the Samba host - must be a member of the <A + must be a member of the <A HREF="smb.conf.5.html#PRINTERADMIN" TARGET="_top" ><TT CLASS="PARAMETER" ><I >printer - admin</I + admin</I ></TT ></A > list.</P @@ -284,7 +333,8 @@ CLASS="PARAMETER" ></UL ><P >Of course, the connected account must still possess access - to add files to the subdirectories beneath [print$].</P +to add files to the subdirectories beneath [print$]. Remember +that all file shares are set to 'read only' by default.</P ></TD ></TR ></TABLE @@ -307,14 +357,34 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN65" +NAME="AEN71" >Setting Drivers for Existing Printers</A ></H2 ><P >The initial listing of printers in the Samba host's -Printers folder will have no printer driver assigned to them. -The way assign a driver to a printer is to view the Properties -of the printer and either</P +Printers folder will have no real printer driver assigned +to them. By default, in Samba 2.2.0 this driver name was set to +<I +CLASS="EMPHASIS" +>NO PRINTER DRIVER AVAILABLE FOR THIS PRINTER</I +>. +Later versions changed this to a NULL string to allow the use +tof the local Add Printer Wizard on NT/2000 clients. +Attempting to view the printer properties for a printer +which has this default driver assigned will result in +the error message:</P +><P +><I +CLASS="EMPHASIS" +>Device settings cannot be displayed. The driver +for the specified printer is not installed, only spooler +properties will be displayed. Do you want to install the +driver now?</I +></P +><P +>Click "No" in the error dialog and you will be presented with +the printer properties window. The way assign a driver to a +printer is to either</P ><P ></P ><UL @@ -361,7 +431,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN78" +NAME="AEN88" >Support a large number of printers</A ></H2 ><P @@ -413,7 +483,7 @@ Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] <TT CLASS="PROMPT" >$ </TT ->rpcclient pogo -U root%bleaK.er \ +>rpcclient pogo -U root%secret \ <TT CLASS="PROMPT" >> </TT @@ -427,7 +497,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN89" +NAME="AEN99" >Adding New Printers via the Windows NT APW</A ></H2 ><P @@ -449,7 +519,7 @@ CLASS="PARAMETER" ><I >printer admin</I ></TT ->. +>). </P ></LI ><LI @@ -476,8 +546,8 @@ TARGET="_top" ><TT CLASS="PARAMETER" ><I ->addprinter -command</I +>add +printer command</I ></TT ></A > must have a defined value. The program @@ -499,7 +569,7 @@ CLASS="COMMAND" CLASS="PARAMETER" ><I >add printer -program</I +command</I ></TT > and reparse to the <TT CLASS="FILENAME" @@ -512,7 +582,7 @@ CLASS="PARAMETER" ><I >add printer program</I ></TT -> is executed undet the context +> is executed under the context of the connected user, not necessarily a root account.</P ><P >There is a complementing <A @@ -521,8 +591,8 @@ TARGET="_top" ><TT CLASS="PARAMETER" ><I ->deleteprinter -command</I +>delete +printer command</I ></TT ></A > for removing entries from the "Printers..." @@ -533,7 +603,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN114" +NAME="AEN124" >Samba and Printer Ports</A ></H2 ><P @@ -570,7 +640,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN122" +NAME="AEN132" >The Imprints Toolset</A ></H1 ><P @@ -588,7 +658,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN126" +NAME="AEN136" >What is Imprints?</A ></H2 ><P @@ -620,7 +690,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN136" +NAME="AEN146" >Creating Printer Driver Packages</A ></H2 ><P @@ -636,7 +706,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN139" +NAME="AEN149" >The Imprints server</A ></H2 ><P @@ -657,7 +727,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN143" +NAME="AEN153" >The Installation Client</A ></H2 ><P @@ -734,7 +804,7 @@ CLASS="FILENAME" ></P ><P >will reveal that Windows NT always uses the NT driver - name. The is ok as Windows NT always requires that at least + name. This is ok as Windows NT always requires that at least the Windows NT version of the printer driver is present. However, Samba does not have the requirement internally. Therefore, how can you use the NT driver name if is has not @@ -751,18 +821,61 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN165" +NAME="AEN175" ><A NAME="MIGRATION" ></A ->Migration to from Samba 2.0.x to - 2.2.x</A +>Migration to from Samba 2.0.x to 2.2.x</A ></H1 ><P ->Given that printer driver management has changed - (we hope improved :) ) in 2.2.0 over prior releases, - migration from an existing setup to 2.2.0 can follow - several paths.</P +>Given that printer driver management has changed (we hope improved) in +2.2 over prior releases, migration from an existing setup to 2.2 can +follow several paths.</P +><P +>Windows clients have a tendency to remember things for quite a while. +For example, if a Windows NT client has attached to a Samba 2.0 server, +it will remember the server as a LanMan printer server. Upgrading +the Samba host to 2.2 makes support for MSRPC printing possible, but +the NT client will still remember the previous setting.</P +><P +>In order to give an NT client printing "amesia" (only necessary if you +want to use the newer MSRPC printing functionality in Samba), delete +the registry keys associated with the print server contained in +<TT +CLASS="CONSTANT" +>[HKLM\SYSTEM\CurrentControlSet\Control\Print]</TT +>. The +spooler service on the client should be stopped prior to doing this:</P +><P +><TT +CLASS="PROMPT" +>C:\WINNT\ ></TT +> <TT +CLASS="USERINPUT" +><B +>net stop spooler</B +></TT +></P +><P +><I +CLASS="EMPHASIS" +>All the normal disclaimers about editing the registry go +here.</I +> Be careful, and know what you are doing.</P +><P +>The spooler service should be restarted after you have finished +removing the appropriate registry entries by replacing the +<B +CLASS="COMMAND" +>stop</B +> command above with <B +CLASS="COMMAND" +>start</B +>.</P +><P +>Windows 9x clients will continue to use LanMan printing calls +with a 2.2 Samba server so there is no need to perform any of these +modifications on non-NT clients.</P ><DIV CLASS="WARNING" ><P @@ -782,9 +895,8 @@ ALIGN="CENTER" ><TD ALIGN="LEFT" ><P ->The following smb.conf parameters are considered to be - depreciated and will be removed soon. Do not use them - in new installations</P +>The following smb.conf parameters are considered to be depreciated and will +be removed soon. Do not use them in new installations</P ><P ></P ><UL @@ -796,7 +908,7 @@ CLASS="PARAMETER" >printer driver file (G)</I ></TT > - </P + </P ></LI ><LI ><P @@ -806,7 +918,7 @@ CLASS="PARAMETER" >printer driver (S)</I ></TT > - </P + </P ></LI ><LI ><P @@ -816,7 +928,7 @@ CLASS="PARAMETER" >printer driver location (S)</I ></TT > - </P + </P ></LI ></UL ></TD @@ -831,31 +943,31 @@ CLASS="PARAMETER" ><LI ><P >If you do not desire the new Windows NT - print driver support, nothing needs to be done. - All existing parameters work the same.</P + print driver support, nothing needs to be done. + All existing parameters work the same.</P ></LI ><LI ><P >If you want to take advantage of NT printer - driver support but do not want to migrate the - 9x drivers to the new setup, the leave the existing - printers.def file. When smbd attempts to locate a - 9x driver for the printer in the TDB and fails it - will drop down to using the printers.def (and all - associated parameters). The <B + driver support but do not want to migrate the + 9x drivers to the new setup, the leave the existing + printers.def file. When smbd attempts to locate a + 9x driver for the printer in the TDB and fails it + will drop down to using the printers.def (and all + associated parameters). The <B CLASS="COMMAND" >make_printerdef</B > - tool will also remain for backwards compatibility but will - be moved to the "this tool is the old way of doing it" - pile.</P + tool will also remain for backwards compatibility but will + be moved to the "this tool is the old way of doing it" + pile.</P ></LI ><LI ><P >If you install a Windows 9x driver for a printer - on your Samba host (in the printing TDB), this information will - take precedence and the three old printing parameters - will be ignored (including print driver location).</P + on your Samba host (in the printing TDB), this information will + take precedence and the three old printing parameters + will be ignored (including print driver location).</P ></LI ><LI ><P @@ -863,23 +975,22 @@ CLASS="COMMAND" CLASS="FILENAME" >printers.def</TT > - file into the new setup, the current only - solution is to use the Windows NT APW to install the NT drivers - and the 9x drivers. This can be scripted using <B + file into the new setup, the current only solution is to use the Windows + NT APW to install the NT drivers and the 9x drivers. This can be scripted + using <B CLASS="COMMAND" >smbclient</B -> - and <B +> and <B CLASS="COMMAND" >rpcclient</B >. See the - Imprints installation client at <A + Imprints installation client at <A HREF="http://imprints.sourceforge.net/" TARGET="_top" >http://imprints.sourceforge.net/</A > - for an example. - </P + for an example. + </P ></LI ></UL ></DIV diff --git a/docs/htmldocs/rpcclient.1.html b/docs/htmldocs/rpcclient.1.html index 786dd6c866..9c19660a46 100644 --- a/docs/htmldocs/rpcclient.1.html +++ b/docs/htmldocs/rpcclient.1.html @@ -151,8 +151,9 @@ CLASS="PROGRAMLISTING" >-l logbasename</DT ><DD ><P ->File name for log/debug files. .client will be - appended. The log file is never removed by the client. +>File name for log/debug files. The extension + '.client' will be appended. The log file is never removed + by the client. </P ></DD ><DT @@ -235,14 +236,8 @@ CLASS="COMMAND" ><DD ><P >Set the SMB domain of the username. This - overrides the default domain which is the domain of the - server specified with the <TT -CLASS="PARAMETER" -><I ->-S</I -></TT -> option. - If the domain specified is the same as the server's NetBIOS name, + overrides the default domain which is the domain defined in + smb.conf. If the domain specified is the same as the server's NetBIOS name, it causes the client to log on using the server's local SAM (as opposed to the Domain SAM). </P ></DD @@ -252,7 +247,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN91" +NAME="AEN90" ></A ><H2 >COMMANDS</H2 @@ -275,14 +270,18 @@ CLASS="COMMAND" ><B CLASS="COMMAND" >lookupsids</B -></P +> - Resolve a list + of SIDs to usernames. + </P ></LI ><LI ><P ><B CLASS="COMMAND" >lookupnames</B -></P +> - Resolve s list + of usernames to SIDs. + </P ></LI ><LI ><P @@ -329,6 +328,34 @@ CLASS="COMMAND" >querygroupmem</B ></P ></LI +><LI +><P +><B +CLASS="COMMAND" +>queryaliasmem</B +></P +></LI +><LI +><P +><B +CLASS="COMMAND" +>querydispinfo</B +></P +></LI +><LI +><P +><B +CLASS="COMMAND" +>querydominfo</B +></P +></LI +><LI +><P +><B +CLASS="COMMAND" +>enumdomgroups</B +></P +></LI ></UL ><P > </P @@ -429,6 +456,17 @@ CLASS="COMMAND" ><P ><B CLASS="COMMAND" +>deldriver</B +> - Delete the + specified printer driver for all architectures. This + does not delete the actual driver files from the server, + only the entry from the server's list of drivers. + </P +></LI +><LI +><P +><B +CLASS="COMMAND" >enumdata</B > - Enumerate all printer setting data stored on the server. On Windows NT clients, @@ -603,7 +641,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN196" +NAME="AEN210" ></A ><H2 >BUGS</H2 @@ -644,7 +682,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN206" +NAME="AEN220" ></A ><H2 >VERSION</H2 @@ -655,7 +693,7 @@ NAME="AEN206" ><DIV CLASS="REFSECT1" ><A -NAME="AEN209" +NAME="AEN223" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html index 0f8a83a939..75e2587689 100644 --- a/docs/htmldocs/smb.conf.5.html +++ b/docs/htmldocs/smb.conf.5.html @@ -859,11 +859,11 @@ NAME="AEN253" ><LI ><P ><A -HREF="#ADDUSERSCRIPT" +HREF="#ADDPRINTERCOMMAND" ><TT CLASS="PARAMETER" ><I ->add user script</I +>add printer command</I ></TT ></A ></P @@ -871,11 +871,23 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#ADDPRINTERCOMMAND" +HREF="#ADDSHARECOMMAND" ><TT CLASS="PARAMETER" ><I ->addprinter command</I +>add share command</I +></TT +></A +></P +></LI +><LI +><P +><A +HREF="#ADDUSERSCRIPT" +><TT +CLASS="PARAMETER" +><I +>add user script</I ></TT ></A ></P @@ -967,6 +979,18 @@ CLASS="PARAMETER" ><LI ><P ><A +HREF="#CHANGESHARECOMMAND" +><TT +CLASS="PARAMETER" +><I +>change share command</I +></TT +></A +></P +></LI +><LI +><P +><A HREF="#CHARACTERSET" ><TT CLASS="PARAMETER" @@ -1123,23 +1147,11 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#DELETEUSERSCRIPT" -><TT -CLASS="PARAMETER" -><I ->delete user script</I -></TT -></A -></P -></LI -><LI -><P -><A HREF="#DELETEPRINTERCOMMAND" ><TT CLASS="PARAMETER" ><I ->deleteprinter command</I +>delete printer command</I ></TT ></A ></P @@ -1147,11 +1159,11 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#DFREECOMMAND" +HREF="#DELETESHARECOMMAND" ><TT CLASS="PARAMETER" ><I ->dfree command</I +>delete share command</I ></TT ></A ></P @@ -1159,11 +1171,11 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#DNSPROXY" +HREF="#DELETEUSERSCRIPT" ><TT CLASS="PARAMETER" ><I ->dns proxy</I +>delete user script</I ></TT ></A ></P @@ -1171,11 +1183,11 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#DOMAINADMINGROUP" +HREF="#DFREECOMMAND" ><TT CLASS="PARAMETER" ><I ->domain admin group</I +>dfree command</I ></TT ></A ></P @@ -1183,11 +1195,11 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#DOMAINADMINUSERS" +HREF="#DNSPROXY" ><TT CLASS="PARAMETER" ><I ->domain admin users</I +>dns proxy</I ></TT ></A ></P @@ -1195,11 +1207,11 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#DOMAINGROUPS" +HREF="#DOMAINADMINGROUP" ><TT CLASS="PARAMETER" ><I ->domain groups</I +>domain admin group</I ></TT ></A ></P @@ -1219,18 +1231,6 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#DOMAINGUESTUSERS" -><TT -CLASS="PARAMETER" -><I ->domain guest users</I -></TT -></A -></P -></LI -><LI -><P -><A HREF="#DOMAINLOGONS" ><TT CLASS="PARAMETER" @@ -1867,6 +1867,18 @@ CLASS="PARAMETER" ><LI ><P ><A +HREF="#OBEYPAMRESTRICTIONS" +><TT +CLASS="PARAMETER" +><I +>obey pam restrictions</I +></TT +></A +></P +></LI +><LI +><P +><A HREF="#OPLOCKBREAKWAITTIME" ><TT CLASS="PARAMETER" @@ -1903,6 +1915,18 @@ CLASS="PARAMETER" ><LI ><P ><A +HREF="#PAMPASSWORDCHANGE" +><TT +CLASS="PARAMETER" +><I +>pam password change</I +></TT +></A +></P +></LI +><LI +><P +><A HREF="#PANICACTION" ><TT CLASS="PARAMETER" @@ -2757,7 +2781,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN889" +NAME="AEN897" ></A ><H2 >COMPLETE LIST OF SERVICE PARAMETERS</H2 @@ -4176,7 +4200,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN1361" +NAME="AEN1369" ></A ><H2 >EXPLANATION OF EACH PARAMETER</H2 @@ -4187,154 +4211,9 @@ CLASS="VARIABLELIST" ><DL ><DT ><A -NAME="ADDUSERSCRIPT" -></A ->add user script (G)</DT -><DD -><P ->This is the full pathname to a script that will - be run <EM ->AS ROOT</EM -> by <A -HREF="smbd.8.html" -TARGET="_top" ->smbd(8) - </A -> under special circumstances described below.</P -><P ->Normally, a Samba server requires that UNIX users are - created for all users accessing files on this server. For sites - that use Windows NT account databases as their primary user database - creating these users and keeping the user list in sync with the - Windows NT PDC is an onerous task. This option allows <A -HREF="smbd.8.html" -TARGET="_top" ->smbd</A -> to create the required UNIX users - <EM ->ON DEMAND</EM -> when a user accesses the Samba server.</P -><P ->In order to use this option, <A -HREF="smbd.8.html" -TARGET="_top" ->smbd</A -> - must be set to <TT -CLASS="PARAMETER" -><I ->security=server</I -></TT -> or <TT -CLASS="PARAMETER" -><I -> security=domain</I -></TT -> and <TT -CLASS="PARAMETER" -><I ->add user script</I -></TT -> - must be set to a full pathname for a script that will create a UNIX - user given one argument of <TT -CLASS="PARAMETER" -><I ->%u</I -></TT ->, which expands into - the UNIX user name to create.</P -><P ->When the Windows user attempts to access the Samba server, - at login (session setup in the SMB protocol) time, <A -HREF="smbd.8.html" -TARGET="_top" -> smbd</A -> contacts the <TT -CLASS="PARAMETER" -><I ->password server</I -></TT -> and - attempts to authenticate the given user with the given password. If the - authentication succeeds then <B -CLASS="COMMAND" ->smbd</B -> - attempts to find a UNIX user in the UNIX password database to map the - Windows user into. If this lookup fails, and <TT -CLASS="PARAMETER" -><I ->add user script - </I -></TT -> is set then <B -CLASS="COMMAND" ->smbd</B -> will - call the specified script <EM ->AS ROOT</EM ->, expanding - any <TT -CLASS="PARAMETER" -><I ->%u</I -></TT -> argument to be the user name to create.</P -><P ->If this script successfully creates the user then <B -CLASS="COMMAND" ->smbd - </B -> will continue on as though the UNIX user - already existed. In this way, UNIX users are dynamically created to - match existing Windows NT accounts.</P -><P ->See also <A -HREF="#SECURITY" -><TT -CLASS="PARAMETER" -><I -> security</I -></TT -></A ->, <A -HREF="#PASSWORDSERVER" -> <TT -CLASS="PARAMETER" -><I ->password server</I -></TT -></A ->, - <A -HREF="#DELETEUSERSCRIPT" -><TT -CLASS="PARAMETER" -><I ->delete user - script</I -></TT -></A ->.</P -><P ->Default: <B -CLASS="COMMAND" ->add user script = <empty string> - </B -></P -><P ->Example: <B -CLASS="COMMAND" ->add user script = /usr/local/samba/bin/add_user - %u</B -></P -></DD -><DT -><A NAME="ADDPRINTERCOMMAND" ></A ->addprinter command (G)</DT +>add printer command (G)</DT ><DD ><P >With the introduction of MS-RPC based printing @@ -4348,7 +4227,8 @@ NAME="ADDPRINTERCOMMAND" physically added to underlying printing system. The <TT CLASS="PARAMETER" ><I -> addprinter command</I +>add + printer command</I ></TT > defines a script to be run which will perform the necessary operations for adding the printer @@ -4370,7 +4250,7 @@ CLASS="COMMAND" >The <TT CLASS="PARAMETER" ><I ->addprinter command</I +>add printer command</I ></TT > is automatically invoked with the following parameter (in @@ -4444,7 +4324,7 @@ CLASS="PARAMETER" >Once the <TT CLASS="PARAMETER" ><I ->addprinter command</I +>add printer command</I ></TT > has been executed, <B @@ -4465,7 +4345,7 @@ HREF="#DELETEPRINTERCOMMAND" ><TT CLASS="PARAMETER" ><I -> deleteprinter command</I +> delete printer command</I ></TT ></A >, <A @@ -4500,6 +4380,290 @@ CLASS="COMMAND" ></DD ><DT ><A +NAME="ADDSHARECOMMAND" +></A +>add share command (G)</DT +><DD +><P +>Samba 2.2.0 introduced the ability to dynamically + add and delete shares via the Windows NT 4.0 Server Manager. The + <TT +CLASS="PARAMETER" +><I +>add share command</I +></TT +> is used to define an + external program or script which will add a new service definition + to <TT +CLASS="FILENAME" +>smb.conf</TT +>. In order to successfully + execute the <TT +CLASS="PARAMETER" +><I +>add share command</I +></TT +>, <B +CLASS="COMMAND" +>smbd</B +> + requires that the administrator be connected using a root account (i.e. + uid == 0). + </P +><P +> When executed, <B +CLASS="COMMAND" +>smbd</B +> will automatically invoke the + <TT +CLASS="PARAMETER" +><I +>add share command</I +></TT +> with four parameters. + </P +><P +></P +><UL +><LI +><P +><TT +CLASS="PARAMETER" +><I +>configFile</I +></TT +> - the location + of the global <TT +CLASS="FILENAME" +>smb.conf</TT +> file. + </P +></LI +><LI +><P +><TT +CLASS="PARAMETER" +><I +>shareName</I +></TT +> - the name of the new + share. + </P +></LI +><LI +><P +><TT +CLASS="PARAMETER" +><I +>pathName</I +></TT +> - path to an **existing** + directory on disk. + </P +></LI +><LI +><P +><TT +CLASS="PARAMETER" +><I +>comment</I +></TT +> - comment string to associate + with the new share. + </P +></LI +></UL +><P +> This parameter is only used for add file shares. To add printer shares, + see the <A +HREF="#ADDPRINTERCOMMAND" +><TT +CLASS="PARAMETER" +><I +>add printer + command</I +></TT +></A +>. + </P +><P +> See also <A +HREF="#CHANGESHARECOMMAND" +><TT +CLASS="PARAMETER" +><I +>change share + command</I +></TT +></A +>, <A +HREF="#DELETESHARECOMMAND" +><TT +CLASS="PARAMETER" +><I +>delete share + command</I +></TT +></A +>. + </P +><P +>Default: <EM +>none</EM +></P +><P +>Example: <B +CLASS="COMMAND" +>add share command = /usr/local/bin/addshare</B +></P +></DD +><DT +><A +NAME="ADDUSERSCRIPT" +></A +>add user script (G)</DT +><DD +><P +>This is the full pathname to a script that will + be run <EM +>AS ROOT</EM +> by <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8) + </A +> under special circumstances described below.</P +><P +>Normally, a Samba server requires that UNIX users are + created for all users accessing files on this server. For sites + that use Windows NT account databases as their primary user database + creating these users and keeping the user list in sync with the + Windows NT PDC is an onerous task. This option allows <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> to create the required UNIX users + <EM +>ON DEMAND</EM +> when a user accesses the Samba server.</P +><P +>In order to use this option, <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> + must be set to <TT +CLASS="PARAMETER" +><I +>security=server</I +></TT +> or <TT +CLASS="PARAMETER" +><I +> security=domain</I +></TT +> and <TT +CLASS="PARAMETER" +><I +>add user script</I +></TT +> + must be set to a full pathname for a script that will create a UNIX + user given one argument of <TT +CLASS="PARAMETER" +><I +>%u</I +></TT +>, which expands into + the UNIX user name to create.</P +><P +>When the Windows user attempts to access the Samba server, + at login (session setup in the SMB protocol) time, <A +HREF="smbd.8.html" +TARGET="_top" +> smbd</A +> contacts the <TT +CLASS="PARAMETER" +><I +>password server</I +></TT +> and + attempts to authenticate the given user with the given password. If the + authentication succeeds then <B +CLASS="COMMAND" +>smbd</B +> + attempts to find a UNIX user in the UNIX password database to map the + Windows user into. If this lookup fails, and <TT +CLASS="PARAMETER" +><I +>add user script + </I +></TT +> is set then <B +CLASS="COMMAND" +>smbd</B +> will + call the specified script <EM +>AS ROOT</EM +>, expanding + any <TT +CLASS="PARAMETER" +><I +>%u</I +></TT +> argument to be the user name to create.</P +><P +>If this script successfully creates the user then <B +CLASS="COMMAND" +>smbd + </B +> will continue on as though the UNIX user + already existed. In this way, UNIX users are dynamically created to + match existing Windows NT accounts.</P +><P +>See also <A +HREF="#SECURITY" +><TT +CLASS="PARAMETER" +><I +> security</I +></TT +></A +>, <A +HREF="#PASSWORDSERVER" +> <TT +CLASS="PARAMETER" +><I +>password server</I +></TT +></A +>, + <A +HREF="#DELETEUSERSCRIPT" +><TT +CLASS="PARAMETER" +><I +>delete user + script</I +></TT +></A +>.</P +><P +>Default: <B +CLASS="COMMAND" +>add user script = <empty string> + </B +></P +><P +>Example: <B +CLASS="COMMAND" +>add user script = /usr/local/samba/bin/add_user + %u</B +></P +></DD +><DT +><A NAME="ADMINUSERS" ></A >admin users (S)</DT @@ -5061,6 +5225,136 @@ CLASS="COMMAND" ></DD ><DT ><A +NAME="CHANGESHARECOMMAND" +></A +>change share command (G)</DT +><DD +><P +>Samba 2.2.0 introduced the ability to dynamically + add and delete shares via the Windows NT 4.0 Server Manager. The + <TT +CLASS="PARAMETER" +><I +>change share command</I +></TT +> is used to define an + external program or script which will modify an existing service definition + in <TT +CLASS="FILENAME" +>smb.conf</TT +>. In order to successfully + execute the <TT +CLASS="PARAMETER" +><I +>change share command</I +></TT +>, <B +CLASS="COMMAND" +>smbd</B +> + requires that the administrator be connected using a root account (i.e. + uid == 0). + </P +><P +> When executed, <B +CLASS="COMMAND" +>smbd</B +> will automatically invoke the + <TT +CLASS="PARAMETER" +><I +>change share command</I +></TT +> with four parameters. + </P +><P +></P +><UL +><LI +><P +><TT +CLASS="PARAMETER" +><I +>configFile</I +></TT +> - the location + of the global <TT +CLASS="FILENAME" +>smb.conf</TT +> file. + </P +></LI +><LI +><P +><TT +CLASS="PARAMETER" +><I +>shareName</I +></TT +> - the name of the new + share. + </P +></LI +><LI +><P +><TT +CLASS="PARAMETER" +><I +>pathName</I +></TT +> - path to an **existing** + directory on disk. + </P +></LI +><LI +><P +><TT +CLASS="PARAMETER" +><I +>comment</I +></TT +> - comment string to associate + with the new share. + </P +></LI +></UL +><P +> This parameter is only used modify existing file shares definitions. To modify + printer shares, use the "Printers..." folder as seen when browsing the Samba host. + </P +><P +> See also <A +HREF="#ADDSHARECOMMAND" +><TT +CLASS="PARAMETER" +><I +>add share + command</I +></TT +></A +>, <A +HREF="#DELETESHARECOMMAND" +><TT +CLASS="PARAMETER" +><I +>delete + share command</I +></TT +></A +>. + </P +><P +>Default: <EM +>none</EM +></P +><P +>Example: <B +CLASS="COMMAND" +>change share command = /usr/local/bin/addshare</B +></P +></DD +><DT +><A NAME="CHARACTERSET" ></A >character set (G)</DT @@ -5731,6 +6025,18 @@ CLASS="PARAMETER" ></A > parameter.</P ><P +>Note that this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + a mask on access control lists also, they need to set the <A +HREF="#SECURITYMASK" +><TT +CLASS="PARAMETER" +><I +>security mask</I +></TT +></A +>.</P +><P >Default: <B CLASS="COMMAND" >create mask = 0744</B @@ -5909,21 +6215,15 @@ NAME="DEBUGLEVEL" >debuglevel (G)</DT ><DD ><P ->The value of the parameter (an integer) allows - the debug level (logging level) to be specified in the - <TT -CLASS="FILENAME" ->smb.conf</TT -> file. This is to give greater - flexibility in the configuration of the system.</P -><P ->The default will be the debug level specified on - the command line or level zero if none was specified.</P -><P ->Example: <B -CLASS="COMMAND" ->debug level = 3</B -></P +>Synonym for <A +HREF="#LOGLEVEL" +><TT +CLASS="PARAMETER" +><I +> log level</I +></TT +></A +>.</P ></DD ><DT ><A @@ -6040,6 +6340,102 @@ CLASS="PROGRAMLISTING" ></DD ><DT ><A +NAME="DELETEPRINTERCOMMAND" +></A +>delete printer command (G)</DT +><DD +><P +>With the introduction of MS-RPC based printer + support for Windows NT/2000 clients in Samba 2.2, it is now + possible to delete printer at run time by issuing the + DeletePrinter() RPC call.</P +><P +>For a Samba host this means that the printer must be + physically deleted from underlying printing system. The <TT +CLASS="PARAMETER" +><I +> deleteprinter command</I +></TT +> defines a script to be run which + will perform the necessary operations for removing the printer + from the print system and from <TT +CLASS="FILENAME" +>smb.conf</TT +>. + </P +><P +>The <TT +CLASS="PARAMETER" +><I +>delete printer command</I +></TT +> is + automatically called with only one parameter: <TT +CLASS="PARAMETER" +><I +> "printer name"</I +></TT +>.</P +><P +>Once the <TT +CLASS="PARAMETER" +><I +>delete printer command</I +></TT +> has + been executed, <B +CLASS="COMMAND" +>smbd</B +> will reparse the <TT +CLASS="FILENAME" +> smb.conf</TT +> to associated printer no longer exists. + If the sharename is still valid, then <B +CLASS="COMMAND" +>smbd + </B +> will return an ACCESS_DENIED error to the client.</P +><P +>See also <A +HREF="#ADDPRINTERCOMMAND" +><TT +CLASS="PARAMETER" +><I +> add printer command</I +></TT +></A +>, <A +HREF="#PRINTING" +><TT +CLASS="PARAMETER" +><I +>printing</I +></TT +></A +>, + <A +HREF="#SHOWADDPRINTERWIZARD" +><TT +CLASS="PARAMETER" +><I +>show add + printer wizard</I +></TT +></A +></P +><P +>Default: <EM +>none</EM +></P +><P +>Example: <B +CLASS="COMMAND" +>deleteprinter command = /usr/bin/removeprinter + </B +></P +></DD +><DT +><A NAME="DELETEREADONLY" ></A >delete readonly (S)</DT @@ -6059,6 +6455,123 @@ CLASS="COMMAND" ></DD ><DT ><A +NAME="DELETESHARECOMMAND" +></A +>delete share command (G)</DT +><DD +><P +>Samba 2.2.0 introduced the ability to dynamically + add and delete shares via the Windows NT 4.0 Server Manager. The + <TT +CLASS="PARAMETER" +><I +>delete share command</I +></TT +> is used to define an + external program or script which will remove an existing service + definition from <TT +CLASS="FILENAME" +>smb.conf</TT +>. In order to successfully + execute the <TT +CLASS="PARAMETER" +><I +>delete share command</I +></TT +>, <B +CLASS="COMMAND" +>smbd</B +> + requires that the administrator be connected using a root account (i.e. + uid == 0). + </P +><P +> When executed, <B +CLASS="COMMAND" +>smbd</B +> will automatically invoke the + <TT +CLASS="PARAMETER" +><I +>delete share command</I +></TT +> with two parameters. + </P +><P +></P +><UL +><LI +><P +><TT +CLASS="PARAMETER" +><I +>configFile</I +></TT +> - the location + of the global <TT +CLASS="FILENAME" +>smb.conf</TT +> file. + </P +></LI +><LI +><P +><TT +CLASS="PARAMETER" +><I +>shareName</I +></TT +> - the name of + the existing service. + </P +></LI +></UL +><P +> This parameter is only used to remove file shares. To delete printer shares, + see the <A +HREF="#DELETEPRINTERCOMMAND" +><TT +CLASS="PARAMETER" +><I +>delete printer + command</I +></TT +></A +>. + </P +><P +> See also <A +HREF="#ADDSHARECOMMAND" +><TT +CLASS="PARAMETER" +><I +>delete share + command</I +></TT +></A +>, <A +HREF="#CHANGESHARECOMMAND" +><TT +CLASS="PARAMETER" +><I +>change + share</I +></TT +></A +>. + </P +><P +>Default: <EM +>none</EM +></P +><P +>Example: <B +CLASS="COMMAND" +>delete share command = /usr/local/bin/delshare</B +></P +></DD +><DT +><A NAME="DELETEUSERSCRIPT" ></A >delete user script (G)</DT @@ -6232,102 +6745,6 @@ CLASS="COMMAND" ></DD ><DT ><A -NAME="DELETEPRINTERCOMMAND" -></A ->deleteprinter command (G)</DT -><DD -><P ->With the introduction of MS-RPC based printer - support for Windows NT/2000 clients in Samba 2.2, it is now - possible to delete printer at run time by issuing the - DeletePrinter() RPC call.</P -><P ->For a Samba host this means that the printer must be - physically deleted from underlying printing system. The <TT -CLASS="PARAMETER" -><I -> deleteprinter command</I -></TT -> defines a script to be run which - will perform the necessary operations for removing the printer - from the print system and from <TT -CLASS="FILENAME" ->smb.conf</TT ->. - </P -><P ->The <TT -CLASS="PARAMETER" -><I ->deleteprinter command</I -></TT -> is - automatically called with only one parameter: <TT -CLASS="PARAMETER" -><I -> "printer name"</I -></TT ->.</P -><P ->Once the <TT -CLASS="PARAMETER" -><I ->deleteprinter command</I -></TT -> has - been executed, <B -CLASS="COMMAND" ->smbd</B -> will reparse the <TT -CLASS="FILENAME" -> smb.conf</TT -> to associated printer no longer exists. - If the sharename is still valid, then <B -CLASS="COMMAND" ->smbd - </B -> will return an ACCESS_DENIED error to the client.</P -><P ->See also <A -HREF="#ADDPRINTERCOMMAND" -><TT -CLASS="PARAMETER" -><I -> addprinter command</I -></TT -></A ->, <A -HREF="#PRINTING" -><TT -CLASS="PARAMETER" -><I ->printing</I -></TT -></A ->, - <A -HREF="#SHOWADDPRINTERWIZARD" -><TT -CLASS="PARAMETER" -><I ->show add - printer wizard</I -></TT -></A -></P -><P ->Default: <EM ->none</EM -></P -><P ->Example: <B -CLASS="COMMAND" ->deleteprinter command = /usr/bin/removeprinter - </B -></P -></DD -><DT -><A NAME="DELETEVETOFILES" ></A >delete veto files (S)</DT @@ -6551,6 +6968,18 @@ CLASS="PARAMETER" > parameter. This parameter is set to 000 by default (i.e. no extra mode bits are added).</P ><P +>Note that this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + a mask on access control lists also, they need to set the <A +HREF="#DIRECTORYSECURITYMASK" +><TT +CLASS="PARAMETER" +><I +>directory security mask</I +></TT +></A +>.</P +><P >See the <A HREF="#FORCEDIRECTORYMODE" ><TT @@ -6639,27 +7068,17 @@ NAME="DIRECTORYSECURITYMASK" mask may be treated as a set of bits the user is not allowed to change.</P ><P ->If not set explicitly this parameter is set to the same - value as the <A -HREF="#DIRECTORYMASK" -><TT -CLASS="PARAMETER" -><I ->directory - mask</I -></TT -></A -> parameter. To allow a user to - modify all the user/group/world permissions on a directory, set - this parameter to 0777.</P +>If not set explicitly this parameter is set to 0777 + meaning a user is allowed to modify all the user/group/world + permissions on a directory.</P ><P ><EM >Note</EM > that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. - Administrators of most normal systems will probably want to set - it to 0777.</P + Administrators of most normal systems will probably want to leave + it as the default of 0777.</P ><P >See also the <A HREF="#FORCEDIRECTORYSECURITYMODE" @@ -6691,13 +7110,12 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->directory security mask = <same as - directory mask></B +>directory security mask = 0777</B ></P ><P >Example: <B CLASS="COMMAND" ->directory security mask = 0777</B +>directory security mask = 0700</B ></P ></DD ><DT @@ -6750,70 +7168,47 @@ NAME="DOMAINADMINGROUP" >domain admin group (G)</DT ><DD ><P ->This is an <EM ->EXPERIMENTAL</EM -> parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list <A -HREF="mailto:samba-ntdom@samba.org" -TARGET="_top" ->samba-ntdom</A -> available by - visiting the web page at <A -HREF="http://lists.samba.org/" -TARGET="_top" -> http://lists.samba.org/</A ->.</P -></DD -><DT -><A -NAME="DOMAINADMINUSERS" -></A ->domain admin users (G)</DT -><DD +>This parameter is intended as a temporary solution + to enable users to be a member of the "Domain Admins" group when + a Samba host is acting as a PDC. A complete solution will be provided + by a system for mapping Windows NT/2000 groups onto UNIX groups. + Please note that this parameter has a somewhat confusing name. It + accepts a list of usernames and of group names in standard + <TT +CLASS="FILENAME" +>smb.conf</TT +> notation. + </P ><P ->This is an <EM ->EXPERIMENTAL</EM -> parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list <A -HREF="mailto:samba-ntdom@samba.org" -TARGET="_top" ->samba-ntdom</A -> available by - visiting the web page at <A -HREF="http://lists.samba.org/" -TARGET="_top" -> http://lists.samba.org/</A ->.</P -></DD -><DT -><A -NAME="DOMAINGROUPS" +>See also <A +HREF="#DOMAINGUESTGROUP" +><TT +CLASS="PARAMETER" +><I +>domain + guest group</I +></TT ></A ->domain groups (G)</DT -><DD +>, <A +HREF="#DOMAINLOGONS" +><TT +CLASS="PARAMETER" +><I +>domain + logons</I +></TT +></A +> + </P ><P ->This is an <EM ->EXPERIMENTAL</EM -> parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list <A -HREF="mailto:samba-ntdom@samba.org" -TARGET="_top" ->samba-ntdom</A -> available by - visiting the web page at <A -HREF="http://lists.samba.org/" -TARGET="_top" -> http://lists.samba.org/</A ->.</P +>Default: <EM +>no domain administrators</EM +></P +><P +>Example: <B +CLASS="COMMAND" +>domain admin group = root @wheel</B +></P ></DD ><DT ><A @@ -6822,46 +7217,47 @@ NAME="DOMAINGUESTGROUP" >domain guest group (G)</DT ><DD ><P ->This is an <EM ->EXPERIMENTAL</EM -> parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list <A -HREF="mailto:samba-ntdom@samba.org" -TARGET="_top" ->samba-ntdom</A -> available by - visiting the web page at <A -HREF="http://lists.samba.org/" -TARGET="_top" -> http://lists.samba.org/</A ->.</P -></DD -><DT -><A -NAME="DOMAINGUESTUSERS" +>This parameter is intended as a temporary solution + to enable users to be a member of the "Domain Guests" group when + a Samba host is acting as a PDC. A complete solution will be provided + by a system for mapping Windows NT/2000 groups onto UNIX groups. + Please note that this parameter has a somewhat confusing name. It + accepts a list of usernames and of group names in standard + <TT +CLASS="FILENAME" +>smb.conf</TT +> notation. + </P +><P +>See also <A +HREF="#DOMAINADMINGROUP" +><TT +CLASS="PARAMETER" +><I +>domain + admin group</I +></TT ></A ->domain guest users (G)</DT -><DD +>, <A +HREF="#DOMAINLOGONS" +><TT +CLASS="PARAMETER" +><I +>domain + logons</I +></TT +></A +> + </P ><P ->This is an <EM ->EXPERIMENTAL</EM -> parameter - that is part of the unfinished Samba NT Domain Controller Code. It may - be removed in a later release. To work with the latest code builds - that may have more support for Samba NT Domain Controller functionality - please subscribe to the mailing list <A -HREF="mailto:samba-ntdom@samba.org" -TARGET="_top" ->samba-ntdom</A -> available by - visiting the web page at <A -HREF="http://lists.samba.org/" -TARGET="_top" -> http://lists.samba.org/</A ->.</P +>Default: <EM +>no domain guests</EM +></P +><P +>Example: <B +CLASS="COMMAND" +>domain guest group = nobody @guest</B +></P ></DD ><DT ><A @@ -7436,6 +7832,19 @@ CLASS="PARAMETER" > parameter is applied.</P ><P +>Note that by default this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + this mask on access control lists also, they need to set the <A +HREF="#RESTRICTACLWITHMASK" +><TT +CLASS="PARAMETER" +><I +>restrict acl with + mask</I +></TT +></A +> to true.</P +><P >See also the parameter <A HREF="#CREATEMASK" ><TT @@ -7495,6 +7904,19 @@ CLASS="PARAMETER" > is applied.</P ><P +>Note that by default this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + this mask on access control lists also, they need to set the <A +HREF="#RESTRICTACLWITHMASK" +><TT +CLASS="PARAMETER" +><I +>restrict acl with + mask</I +></TT +></A +> to true.</P +><P >See also the parameter <A HREF="#DIRECTORYMASK" ><TT @@ -7548,27 +7970,17 @@ NAME="FORCEDIRECTORYSECURITYMODE" mask may be treated as a set of bits that, when modifying security on a directory, the user has always set to be 'on'.</P ><P ->If not set explicitly this parameter is set to the same - value as the <A -HREF="#FORCEDIRECTORYMODE" -><TT -CLASS="PARAMETER" -><I ->force - directory mode</I -></TT -></A -> parameter. To allow - a user to modify all the user/group/world permissions on a - directory without restrictions, set this parameter to 000.</P +>If not set explicitly this parameter is 000, which + allows a user to modify all the user/group/world permissions on a + directory without restrictions.</P ><P ><EM >Note</EM > that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. - Administrators of most normal systems will probably want to set - it to 0000.</P + Administrators of most normal systems will probably want to leave + it set as 0000.</P ><P >See also the <A HREF="#DIRECTORYSECURITYMASK" @@ -7600,13 +8012,12 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->force directory security mode = <same as - force directory mode></B +>force directory security mode = 0</B ></P ><P >Example: <B CLASS="COMMAND" ->force directory security mode = 0</B +>force directory security mode = 700</B ></P ></DD ><DT @@ -7701,27 +8112,17 @@ NAME="FORCESECURITYMODE" mask may be treated as a set of bits that, when modifying security on a file, the user has always set to be 'on'.</P ><P ->If not set explicitly this parameter is set to the same - value as the <A -HREF="#FORCECREATEMODE" -><TT -CLASS="PARAMETER" -><I ->force - create mode</I -></TT -></A -> parameter. To allow a user to - modify all the user/group/world permissions on a file, with no - restrictions set this parameter to 000.</P +>If not set explicitly this parameter is set to 0, + and allows a user to modify all the user/group/world permissions on a file, + with no restrictions.</P ><P ><EM >Note</EM > that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. - Administrators of most normal systems will probably want to set - it to 0000.</P + Administrators of most normal systems will probably want to leave + this set to 0000.</P ><P >See also the <A HREF="#FORCEDIRECTORYSECURITYMODE" @@ -7753,13 +8154,12 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->force security mode = <same as force - create mode></B +>force security mode = 0</B ></P ><P >Example: <B CLASS="COMMAND" ->force security mode = 0</B +>force security mode = 700</B ></P ></DD ><DT @@ -9292,15 +9692,21 @@ NAME="LOGLEVEL" >log level (G)</DT ><DD ><P ->Synonym for <A -HREF="#DEBUGLEVEL" -><TT -CLASS="PARAMETER" -><I -> debug level</I -></TT -></A ->.</P +>The value of the parameter (an integer) allows + the debug level (logging level) to be specified in the + <TT +CLASS="FILENAME" +>smb.conf</TT +> file. This is to give greater + flexibility in the configuration of the system.</P +><P +>The default will be the log level specified on + the command line or level zero if none was specified.</P +><P +>Example: <B +CLASS="COMMAND" +>log level = 3</B +></P ></DD ><DT ><A @@ -11634,6 +12040,36 @@ CLASS="COMMAND" ></DD ><DT ><A +NAME="OBEYPAMRESTRICTIONS" +></A +>obey pam restrictions (G)</DT +><DD +><P +>When Samba 2.2 is configure to enable PAM support + (i.e. --with-pam), this parameter will control whether or not Samba + should obey PAM's account and session management directives. The + default behavior is to use PAM for clear text authentication only + and to ignore any account or session management. Note that Samba + always ignores PAM for authentication in the case of <A +HREF="#ENCRYPTPASSWORDS" +><TT +CLASS="PARAMETER" +><I +>encrypt passwords = yes</I +></TT +> + </A +>. The reason is that PAM modules cannot support the challenge/response + authentication mechanism needed in the presence of SMB password encryption. + </P +><P +>Default: <B +CLASS="COMMAND" +>obey pam restrictions = no</B +></P +></DD +><DT +><A NAME="ONLYUSER" ></A >only user (S)</DT @@ -11694,30 +12130,6 @@ CLASS="COMMAND" ></DD ><DT ><A -NAME="OLELOCKINGCOMPATIBILITY" -></A ->ole locking compatibility (G)</DT -><DD -><P ->This parameter allows an administrator to turn - off the byte range lock manipulation that is done within Samba to - give compatibility for OLE applications. Windows OLE applications - use byte range locking as a form of inter-process communication, by - locking ranges of bytes around the 2^32 region of a file range. This - can cause certain UNIX lock managers to crash or otherwise cause - problems. Setting this parameter to <TT -CLASS="CONSTANT" ->no</TT -> means you - trust your UNIX lock manager to handle such cases correctly.</P -><P ->Default: <B -CLASS="COMMAND" ->ole locking compatibility = yes</B -></P -></DD -><DT -><A NAME="ONLYGUEST" ></A >only guest (S)</DT @@ -11952,6 +12364,33 @@ CLASS="COMMAND" ></DD ><DT ><A +NAME="PAMPASSWORDCHANGE" +></A +>pam password change (G)</DT +><DD +><P +>With the addition of better PAM support in Samba 2.2, + this parameter, it is possible to use PAM's password change control + flag for Samba. If enabled, then PAM will be used for password + changes when requested by an SMB client, and the <A +HREF="#PASSWDCHAT" +><TT +CLASS="PARAMETER" +><I +>passwd chat</I +></TT +></A +> must be + be changed to work with the pam prompts. + </P +><P +>Default: <B +CLASS="COMMAND" +>pam password change = no</B +></P +></DD +><DT +><A NAME="PANICACTION" ></A >panic action (G)</DT @@ -12072,6 +12511,24 @@ CLASS="PARAMETER" password cleartext. In this case the old password cleartext is set to "" (the empty string).</P ><P +>Also, if the <A +HREF="#PAMPASSWORDCHANGE" +><TT +CLASS="PARAMETER" +><I +>pam + password change</I +></TT +></A +> parameter is set to true, then the + chat sequence should consist of three elements. The first element should + match the pam prompt for the old password, the second element should match + the pam prompt for the first request for the new password, and the final + element should match the pam prompt for the second request for the new password. + These matches are done case insentively. Under most conditions this change + is done as root so the prompt for the old password will never be matched. + </P +><P >See also <A HREF="#UNIXPASSWORDSYNC" ><TT @@ -12089,7 +12546,7 @@ CLASS="PARAMETER" > passwd program</I ></TT ></A -> and <A +> ,<A HREF="#PASSWDCHATDEBUG" > <TT CLASS="PARAMETER" @@ -12097,6 +12554,14 @@ CLASS="PARAMETER" >passwd chat debug</I ></TT ></A +> and <A +HREF="#PAMPASSWORDCHANGE" +> <TT +CLASS="PARAMETER" +><I +>pam password change</I +></TT +></A >.</P ><P >Default: <B @@ -13990,6 +14455,102 @@ CLASS="COMMAND" ></DD ><DT ><A +NAME="RESTRICTACLWITHMASK" +></A +>restrict acl with mask (S)</DT +><DD +><P +>This is a boolean parameter. If set to false (default), then + Creation of files with access control lists (ACLS) and modification of ACLs + using the Windows NT/2000 ACL editor will be applied directly to the file + or directory.</P +><P +>If set to True, then all requests to set an ACL on a file will have the + parameters <A +HREF="#CREATEMASK" +><TT +CLASS="PARAMETER" +><I +>create mask</I +></TT +></A +>, + <A +HREF="#FORCECREATEMODE" +><TT +CLASS="PARAMETER" +><I +>force create mode</I +></TT +></A +> + applied before setting the ACL, and all requests to set an ACL on a directory will + have the parameters <A +HREF="#DIRECTORYMASK" +><TT +CLASS="PARAMETER" +><I +>directory + mask</I +></TT +></A +>, <A +HREF="#FORCEDIRECTORYMODE" +><TT +CLASS="PARAMETER" +><I +>force + directory mode</I +></TT +></A +> applied before setting the ACL. + </P +><P +>See also <A +HREF="#CREATEMASK" +><TT +CLASS="PARAMETER" +><I +>create mask</I +></TT +></A +>, + <A +HREF="#FORCECREATEMODE" +><TT +CLASS="PARAMETER" +><I +>force create mode</I +></TT +></A +>, + <A +HREF="#DIRECTORYMASK" +><TT +CLASS="PARAMETER" +><I +>directory mask</I +></TT +></A +>, + <A +HREF="#FORCEDIRECTORYMODE" +><TT +CLASS="PARAMETER" +><I +>force directory mode</I +></TT +></A +> + </P +><P +>Default: <B +CLASS="COMMAND" +>restrict acl with mask = no</B +></P +></DD +><DT +><A NAME="RESTRICTANONYMOUS" ></A >restrict anonymous (G)</DT @@ -14819,19 +15380,9 @@ NAME="SECURITYMASK" mask may be treated as a set of bits the user is not allowed to change.</P ><P ->If not set explicitly this parameter is set to the same - value as the <A -HREF="#CREATEMASK" -><TT -CLASS="PARAMETER" -><I ->create mask - </I -></TT -></A -> parameter. To allow a user to modify all the - user/group/world permissions on a file, set this parameter to - 0777.</P +>If not set explicitly this parameter is 0777, allowing + a user to modify all the user/group/world permissions on a file. + </P ><P ><EM >Note</EM @@ -14839,7 +15390,7 @@ CLASS="PARAMETER" Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will - probably want to set it to 0777.</P + probably want to leave it set to 0777.</P ><P >See also the <A HREF="#FORCEDIRECTORYSECURITYMODE" @@ -14871,13 +15422,12 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->security mask = <same as create mask> - </B +>security mask = 0777</B ></P ><P >Example: <B CLASS="COMMAND" ->security mask = 0777</B +>security mask = 0770</B ></P ></DD ><DT @@ -17781,7 +18331,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN5643" +NAME="AEN5791" ></A ><H2 >WARNINGS</H2 @@ -17811,7 +18361,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN5649" +NAME="AEN5797" ></A ><H2 >VERSION</H2 @@ -17822,7 +18372,7 @@ NAME="AEN5649" ><DIV CLASS="REFSECT1" ><A -NAME="AEN5652" +NAME="AEN5800" ></A ><H2 >SEE ALSO</H2 @@ -17901,7 +18451,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN5672" +NAME="AEN5820" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbcontrol.1.html b/docs/htmldocs/smbcontrol.1.html index c8cb14ccd3..7136d3e981 100644 --- a/docs/htmldocs/smbcontrol.1.html +++ b/docs/htmldocs/smbcontrol.1.html @@ -14,7 +14,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="FINDSMB" +NAME="SMBCONTROL" >smbcontrol</A ></H1 ><DIV diff --git a/docs/htmldocs/smbspool.8.html b/docs/htmldocs/smbspool.8.html index d29db41716..f689b4a0bc 100644 --- a/docs/htmldocs/smbspool.8.html +++ b/docs/htmldocs/smbspool.8.html @@ -14,7 +14,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="FINDSMB" +NAME="SMBSPOOL" >smbspool</A ></H1 ><DIV @@ -24,7 +24,7 @@ NAME="AEN5" ></A ><H2 >Name</H2 ->nmblookup -- send print file to an SMB printer</DIV +>smbspool -- send print file to an SMB printer</DIV ><DIV CLASS="REFSYNOPSISDIV" ><A diff --git a/docs/htmldocs/smbstatus.1.html b/docs/htmldocs/smbstatus.1.html index cc366638df..1d3dc9f952 100644 --- a/docs/htmldocs/smbstatus.1.html +++ b/docs/htmldocs/smbstatus.1.html @@ -14,7 +14,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="FINDSMB" +NAME="SMBSTATUS" >smbstatus</A ></H1 ><DIV diff --git a/docs/htmldocs/swat.8.html b/docs/htmldocs/swat.8.html index e2977f3286..be16272bb6 100644 --- a/docs/htmldocs/swat.8.html +++ b/docs/htmldocs/swat.8.html @@ -35,7 +35,7 @@ NAME="AEN8" ><P ><B CLASS="COMMAND" ->nmblookup</B +>swat</B > [-s <smb config file>] [-a]</P ></DIV ><DIV diff --git a/docs/manpages/make_smbcodepage.1 b/docs/manpages/make_smbcodepage.1 index eb1fe84a74..fec52adee5 100644 --- a/docs/manpages/make_smbcodepage.1 +++ b/docs/manpages/make_smbcodepage.1 @@ -3,7 +3,7 @@ .\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/> .\" Please send any bug reports, improvements, comments, patches, .\" etc. to Steve Cheng <steve@ggi-project.org>. -.TH "MAKE_SMBCODEPAGE" "1" "24 April 2001" "" "" +.TH "MAKE_SMBCODEPAGE" "1" "01 June 2001" "" "" .SH NAME make_smbcodepage \- construct a codepage file for Samba .SH SYNOPSIS @@ -29,11 +29,11 @@ This is the codepage we are processing (a number, e.g. 850). .TP \fBinputfile\fR -This is the input file to process. In t -he '\fIc\fR' case this will be a text +This is the input file to process. In +the \fIc\fR case this will be a text codepage definition file such as the ones found in the Samba \fIsource/codepages\fR directory. In -the '\fId\fR' case this will be the +the \fId\fR case this will be the binary format codepage definition file normally found in the \fIlib/codepages\fR directory in the Samba install directory path. diff --git a/docs/manpages/make_unicodemap.1 b/docs/manpages/make_unicodemap.1 index 6ecd538cbe..805bc2d6c7 100644 --- a/docs/manpages/make_unicodemap.1 +++ b/docs/manpages/make_unicodemap.1 @@ -1,100 +1,97 @@ -.TH MAKE_UNICODEMAP 1 "24 Mar 2001" "make_unicodemap 2.2.0-alpha3" -.PP -.SH "NAME" -make_unicodemap \- Construct a unicode map file for Samba -.PP -.SH "SYNOPSIS" -.PP -\fBmake_unicodemap\fP codepage inputfile outputfile -.PP -.SH "DESCRIPTION" -.PP -This program is part of the \fBSamba\fP suite\&. -.PP -\fBmake_unicodemap\fP compiles text unicode map files into binary unicode -map files for use with the internationalization features of Samba 2\&.0 -.PP -.SH "OPTIONS" -.PP -.IP -.IP "codepage" -This is the codepage or UNIX character set we are processing (a number, e\&.g\&. 850)\&. -.IP -.IP "inputfile" -This is the input file to process\&. This is a text unicode map file -such as the ones found in the Samba \fIsource/codepages\fP directory\&. -.IP -.IP "outputfile" -This is the binary output file to produce\&. -.IP -.PP -.SH "Samba Unicode Map Files" -.PP -A text Samba unicode map file is a description that tells -Samba how to map characters from a specified DOS code page or UNIX character -set to 16 bit unicode\&. -.PP -A binary Samba unicode map file is a binary representation of -the same information, including a value that specifies what codepage -or UNIX character set this file is describing\&. -.PP -.SH "FILES" -.PP -\fBCP<codepage>\&.TXT\fP -.PP -These are the input (text) unicode map files provided in the Samba -\fIsource/codepages\fP directory\&. -.PP -A text unicode map file consists of multiple lines -containing two fields\&. These fields are : -.PP -.IP -.IP o -\fBcharacter\fP: which is the (hex) character mapped on this -line\&. -.IP -.IP o -\fBunicode\fP: which is the (hex) 16 bit unicode character that the -character will map to\&. -.IP -.PP -\fBunicode_map\&.<codepage>\fP These are the output (binary) unicode map files -produced and placed in the Samba destination \fIlib/codepage\fP -directory\&. -.PP -.SH "INSTALLATION" -.PP -The location of the server and its support files is a matter for -individual system administrators\&. The following are thus suggestions -only\&. -.PP -It is recommended that the \fBmake_unicodemap\fP program be installed -under the \fI/usr/local/samba\fP hierarchy, in a directory readable by -all, writeable only by root\&. The program itself should be executable -by all\&. The program should NOT be setuid or setgid! -.PP -.SH "VERSION" -.PP -This man page is correct for version 2\&.0 of the Samba suite\&. -.PP -.SH "SEE ALSO" -.PP -\fBsmb\&.conf(5)\fP, \fBsmbd (8)\fP -.PP -.SH "AUTHOR" -.PP -The original Samba software and related utilities were created by -Andrew Tridgell samba@samba\&.org\&. Samba is now developed -by the Samba Team as an Open Source project similar to the way the -Linux kernel is developed\&. -.PP -The original Samba man pages were written by Karl Auer\&. The man page -sources were converted to YODL format (another excellent piece of Open -Source software, available at -\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP) -and updated for the Samba2\&.0 release by Jeremy Allison\&. -samba@samba\&.org\&. -.PP -See \fBsamba (7)\fP to find out how to get a full -list of contributors and details on how to submit bug reports, -comments etc\&. +.\" This manpage has been automatically generated by docbook2man-spec +.\" from a DocBook document. docbook2man-spec can be found at: +.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/> +.\" Please send any bug reports, improvements, comments, patches, +.\" etc. to Steve Cheng <steve@ggi-project.org>. +.TH "MAKE_UNICODEMAP" "1" "01 June 2001" "" "" +.SH NAME +make_unicodemap \- construct a unicode map file for Samba +.SH SYNOPSIS +.sp +\fBmake_unicodemap\fR \fBcodepage\fR \fBinputfile\fR \fBoutputfile\fR +.SH "DESCRIPTION" +.PP +This tool is part of the Sambasuite. +.PP +\fBmake_unicodemap\fR compiles text unicode map +files into binary unicodef map files for use with the +internationalization features of Samba 2.2. +.SH "OPTIONS" +.TP +\fBcodepage\fR +This is the codepage or UNIX character +set we are processing (a number, e.g. 850). +.TP +\fBinputfile\fR +This is the input file to process. This is a +text unicode map file such as the ones found in the Samba +\fIsource/codepages\fR directory. +.TP +\fBoutputfile\fR +This is the binary output file to produce. +.SH "SAMBA UNICODE MAP FILES" +.PP +A text Samba unicode map file is a description that tells Samba +how to map characters from a specified DOS code page or UNIX character +set to 16 bit unicode. +.PP +A binary Samba unicode map file is a binary representation +of the same information, including a value that specifies what +codepage or UNIX character set this file is describing. +.SH "FILES" +.PP +\fICP<codepage>.TXT\fR +.PP +These are the input (text) unicode map files provided +in the Samba \fIsource/codepages\fR +directory. +.PP +A text unicode map file consists of multiple lines +containing two fields. These fields are : +.TP 0.2i +\(bu +\fIcharacter\fR - which is +the (hex) character mapped on this line. +.TP 0.2i +\(bu +\fIunicode\fR - which +is the (hex) 16 bit unicode character that the character +will map to. +.PP +\fIunicode_map.<codepage>\fR - These are +the output (binary) unicode map files produced and placed in +the Samba destination \fIlib/codepage\fR +directory. +.PP +.SH "INSTALLATION" +.PP +The location of the server and its support files is a matter +for individual system administrators. The following are thus +suggestions only. +.PP +It is recommended that the \fBmake_unicodemap\fR +program be installed under the +\fI$prefix/samba\fR hierarchy, +in a directory readable by all, writeable only by root. The +program itself should be executable by all. The program +should NOT be setuid or setgid! +.SH "VERSION" +.PP +This man page is correct for version 2.2 of +the Samba suite. +.SH "SEE ALSO" +.PP +\fBsmbd(8)\fR, +smb.conf(5).SH "AUTHOR" +.PP +The original Samba software and related utilities +were created by Andrew Tridgell. Samba is now developed +by the Samba Team as an Open Source project similar +to the way the Linux kernel is developed. +.PP +The original Samba man pages were written by Karl Auer. +The man page sources were converted to YODL format (another +excellent piece of Open Source software, available at +ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0 +release by Jeremy Allison. The conversion to DocBook for +Samba 2.2 was done by Gerald Carter diff --git a/docs/manpages/rpcclient.1 b/docs/manpages/rpcclient.1 index f45ebdee50..d046ec3709 100644 --- a/docs/manpages/rpcclient.1 +++ b/docs/manpages/rpcclient.1 @@ -3,7 +3,7 @@ .\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/> .\" Please send any bug reports, improvements, comments, patches, .\" etc. to Steve Cheng <steve@ggi-project.org>. -.TH "RPCCLIENT" "1" "24 April 2001" "" "" +.TH "RPCCLIENT" "1" "01 June 2001" "" "" .SH NAME rpcclient \- tool for executing client side MS-RPC functions .SH SYNOPSIS @@ -56,8 +56,9 @@ planning on submitting a bug report to the Samba team (see BUGS.txt). Print a summary of command line options. .TP \fB-l logbasename\fR -File name for log/debug files. .client will be -appended. The log file is never removed by the client. +File name for log/debug files. The extension +\&'.client' will be appended. The log file is never removed +by the client. .TP \fB-N\fR instruct \fBrpcclient\fR not to ask @@ -93,9 +94,8 @@ it in directly. .TP \fB-W domain\fR Set the SMB domain of the username. This -overrides the default domain which is the domain of the -server specified with the \fI-S\fR option. -If the domain specified is the same as the server's NetBIOS name, +overrides the default domain which is the domain defined in +smb.conf. If the domain specified is the same as the server's NetBIOS name, it causes the client to log on using the server's local SAM (as opposed to the Domain SAM). .SH "COMMANDS" @@ -106,10 +106,12 @@ opposed to the Domain SAM). \fBlsaquery\fR .TP 0.2i \(bu -\fBlookupsids\fR +\fBlookupsids\fR - Resolve a list +of SIDs to usernames. .TP 0.2i \(bu -\fBlookupnames\fR +\fBlookupnames\fR - Resolve s list +of usernames to SIDs. .TP 0.2i \(bu \fBenumtrusts\fR @@ -130,6 +132,18 @@ opposed to the Domain SAM). .TP 0.2i \(bu \fBquerygroupmem\fR +.TP 0.2i +\(bu +\fBqueryaliasmem\fR +.TP 0.2i +\(bu +\fBquerydispinfo\fR +.TP 0.2i +\(bu +\fBquerydominfo\fR +.TP 0.2i +\(bu +\fBenumdomgroups\fR .PP .PP .PP @@ -180,6 +194,12 @@ and the \fIport\fRmust be a valid port name (see \fBenumports\fR. .TP 0.2i \(bu +\fBdeldriver\fR - Delete the +specified printer driver for all architectures. This +does not delete the actual driver files from the server, +only the entry from the server's list of drivers. +.TP 0.2i +\(bu \fBenumdata\fR - Enumerate all printer setting data stored on the server. On Windows NT clients, these values are stored in the registry, while Samba servers diff --git a/docs/manpages/smb.conf.5 b/docs/manpages/smb.conf.5 index 56c04c035c..efd36946ab 100644 --- a/docs/manpages/smb.conf.5 +++ b/docs/manpages/smb.conf.5 @@ -3,7 +3,7 @@ .\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/> .\" Please send any bug reports, improvements, comments, patches, .\" etc. to Steve Cheng <steve@ggi-project.org>. -.TH "SMB.CONF" "5" "24 April 2001" "" "" +.TH "SMB.CONF" "5" "01 June 2001" "" "" .SH NAME smb.conf \- The configuration file for the Samba suite .SH "SYNOPSIS" @@ -503,10 +503,13 @@ Here is a list of all global parameters. See the section of each parameter for details. Note that some are synonyms. .TP 0.2i \(bu -\fIadd user script\fR +\fIadd printer command\fR +.TP 0.2i +\(bu +\fIadd share command\fR .TP 0.2i \(bu -\fIaddprinter command\fR +\fIadd user script\fR .TP 0.2i \(bu \fIallow trusted domains\fR @@ -530,6 +533,9 @@ each parameter for details. Note that some are synonyms. \fIchange notify timeout\fR .TP 0.2i \(bu +\fIchange share command\fR +.TP 0.2i +\(bu \fIcharacter set\fR .TP 0.2i \(bu @@ -569,10 +575,13 @@ each parameter for details. Note that some are synonyms. \fIdefault service\fR .TP 0.2i \(bu -\fIdelete user script\fR +\fIdelete printer command\fR +.TP 0.2i +\(bu +\fIdelete share command\fR .TP 0.2i \(bu -\fIdeleteprinter command\fR +\fIdelete user script\fR .TP 0.2i \(bu \fIdfree command\fR @@ -584,18 +593,9 @@ each parameter for details. Note that some are synonyms. \fIdomain admin group\fR .TP 0.2i \(bu -\fIdomain admin users\fR -.TP 0.2i -\(bu -\fIdomain groups\fR -.TP 0.2i -\(bu \fIdomain guest group\fR .TP 0.2i \(bu -\fIdomain guest users\fR -.TP 0.2i -\(bu \fIdomain logons\fR .TP 0.2i \(bu @@ -755,6 +755,9 @@ each parameter for details. Note that some are synonyms. \fInull passwords\fR .TP 0.2i \(bu +\fIobey pam restrictions\fR +.TP 0.2i +\(bu \fIoplock break wait time\fR .TP 0.2i \(bu @@ -764,6 +767,9 @@ each parameter for details. Note that some are synonyms. \fIos2 driver map\fR .TP 0.2i \(bu +\fIpam password change\fR +.TP 0.2i +\(bu \fIpanic action\fR .TP 0.2i \(bu @@ -1332,48 +1338,7 @@ each parameter for details. Note that some are synonyms. \fIwriteable\fR .SH "EXPLANATION OF EACH PARAMETER" .TP -\fBadd user script (G)\fR -This is the full pathname to a script that will -be run \fBAS ROOT\fR by smbd(8) -under special circumstances described below. - -Normally, a Samba server requires that UNIX users are -created for all users accessing files on this server. For sites -that use Windows NT account databases as their primary user database -creating these users and keeping the user list in sync with the -Windows NT PDC is an onerous task. This option allows smbdto create the required UNIX users -\fBON DEMAND\fR when a user accesses the Samba server. - -In order to use this option, smbdmust be set to \fIsecurity=server\fR or \fI security=domain\fR and \fIadd user script\fR -must be set to a full pathname for a script that will create a UNIX -user given one argument of \fI%u\fR, which expands into -the UNIX user name to create. - -When the Windows user attempts to access the Samba server, -at login (session setup in the SMB protocol) time, smbdcontacts the \fIpassword server\fR and -attempts to authenticate the given user with the given password. If the -authentication succeeds then \fBsmbd\fR -attempts to find a UNIX user in the UNIX password database to map the -Windows user into. If this lookup fails, and \fIadd user script -\fRis set then \fBsmbd\fR will -call the specified script \fBAS ROOT\fR, expanding -any \fI%u\fR argument to be the user name to create. - -If this script successfully creates the user then \fBsmbd -\fRwill continue on as though the UNIX user -already existed. In this way, UNIX users are dynamically created to -match existing Windows NT accounts. - -See also \fI security\fR, \fIpassword server\fR, -\fIdelete user -script\fR. - -Default: \fBadd user script = <empty string> -\fR -Example: \fBadd user script = /usr/local/samba/bin/add_user -%u\fR -.TP -\fBaddprinter command (G)\fR +\fBadd printer command (G)\fR With the introduction of MS-RPC based printing support for Windows NT/2000 clients in Samba 2.2, The MS Add Printer Wizard (APW) icon is now also available in the @@ -1382,14 +1347,15 @@ allows for printers to be add remotely to a Samba or Windows NT/2000 print server. For a Samba host this means that the printer must be -physically added to underlying printing system. The \fI addprinter command\fR defines a script to be run which +physically added to underlying printing system. The \fIadd +printer command\fR defines a script to be run which will perform the necessary operations for adding the printer to the print system and to add the appropriate service definition to the \fIsmb.conf\fR file in order that it can be shared by \fBsmbd(8)\fR . -The \fIaddprinter command\fR is +The \fIadd printer command\fR is automatically invoked with the following parameter (in order: .RS @@ -1420,13 +1386,13 @@ only. The remaining fields in the structure are generated from answers to the APW questions. .PP .PP -Once the \fIaddprinter command\fR has +Once the \fIadd printer command\fR has been executed, \fBsmbd\fR will reparse the \fI smb.conf\fR to determine if the share defined by the APW exists. If the sharename is still invalid, then \fBsmbd \fRwill return an ACCESS_DENIED error to the client. .PP .PP -See also \fI deleteprinter command\fR, \fIprinting\fR, +See also \fI delete printer command\fR, \fIprinting\fR, \fIshow add printer wizard\fR .PP @@ -1437,6 +1403,94 @@ Default: \fBnone\fR Example: \fBaddprinter command = /usr/bin/addprinter \fR.PP .TP +\fBadd share command (G)\fR +Samba 2.2.0 introduced the ability to dynamically +add and delete shares via the Windows NT 4.0 Server Manager. The +\fIadd share command\fR is used to define an +external program or script which will add a new service definition +to \fIsmb.conf\fR. In order to successfully +execute the \fIadd share command\fR, \fBsmbd\fR +requires that the administrator be connected using a root account (i.e. +uid == 0). + +When executed, \fBsmbd\fR will automatically invoke the +\fIadd share command\fR with four parameters. +.RS +.TP 0.2i +\(bu +\fIconfigFile\fR - the location +of the global \fIsmb.conf\fR file. +.TP 0.2i +\(bu +\fIshareName\fR - the name of the new +share. +.TP 0.2i +\(bu +\fIpathName\fR - path to an **existing** +directory on disk. +.TP 0.2i +\(bu +\fIcomment\fR - comment string to associate +with the new share. +.RE +.PP +This parameter is only used for add file shares. To add printer shares, +see the \fIadd printer +command\fR. +.PP +.PP +See also \fIchange share +command\fR, \fIdelete share +command\fR. +.PP +.PP +Default: \fBnone\fR +.PP +.PP +Example: \fBadd share command = /usr/local/bin/addshare\fR +.PP +.TP +\fBadd user script (G)\fR +This is the full pathname to a script that will +be run \fBAS ROOT\fR by smbd(8) +under special circumstances described below. + +Normally, a Samba server requires that UNIX users are +created for all users accessing files on this server. For sites +that use Windows NT account databases as their primary user database +creating these users and keeping the user list in sync with the +Windows NT PDC is an onerous task. This option allows smbdto create the required UNIX users +\fBON DEMAND\fR when a user accesses the Samba server. + +In order to use this option, smbdmust be set to \fIsecurity=server\fR or \fI security=domain\fR and \fIadd user script\fR +must be set to a full pathname for a script that will create a UNIX +user given one argument of \fI%u\fR, which expands into +the UNIX user name to create. + +When the Windows user attempts to access the Samba server, +at login (session setup in the SMB protocol) time, smbdcontacts the \fIpassword server\fR and +attempts to authenticate the given user with the given password. If the +authentication succeeds then \fBsmbd\fR +attempts to find a UNIX user in the UNIX password database to map the +Windows user into. If this lookup fails, and \fIadd user script +\fRis set then \fBsmbd\fR will +call the specified script \fBAS ROOT\fR, expanding +any \fI%u\fR argument to be the user name to create. + +If this script successfully creates the user then \fBsmbd +\fRwill continue on as though the UNIX user +already existed. In this way, UNIX users are dynamically created to +match existing Windows NT accounts. + +See also \fI security\fR, \fIpassword server\fR, +\fIdelete user +script\fR. + +Default: \fBadd user script = <empty string> +\fR +Example: \fBadd user script = /usr/local/samba/bin/add_user +%u\fR +.TP \fBadmin users (S)\fR This is a list of users who will be granted administrative privileges on the share. This means that they @@ -1621,6 +1675,52 @@ Example: \fBchange notify timeout = 300\fR Would change the scan time to every 5 minutes. .TP +\fBchange share command (G)\fR +Samba 2.2.0 introduced the ability to dynamically +add and delete shares via the Windows NT 4.0 Server Manager. The +\fIchange share command\fR is used to define an +external program or script which will modify an existing service definition +in \fIsmb.conf\fR. In order to successfully +execute the \fIchange share command\fR, \fBsmbd\fR +requires that the administrator be connected using a root account (i.e. +uid == 0). + +When executed, \fBsmbd\fR will automatically invoke the +\fIchange share command\fR with four parameters. +.RS +.TP 0.2i +\(bu +\fIconfigFile\fR - the location +of the global \fIsmb.conf\fR file. +.TP 0.2i +\(bu +\fIshareName\fR - the name of the new +share. +.TP 0.2i +\(bu +\fIpathName\fR - path to an **existing** +directory on disk. +.TP 0.2i +\(bu +\fIcomment\fR - comment string to associate +with the new share. +.RE +.PP +This parameter is only used modify existing file shares definitions. To modify +printer shares, use the "Printers..." folder as seen when browsing the Samba host. +.PP +.PP +See also \fIadd share +command\fR, \fIdelete +share command\fR. +.PP +.PP +Default: \fBnone\fR +.PP +.PP +Example: \fBchange share command = /usr/local/bin/addshare\fR +.PP +.TP \fBcharacter set (G)\fR This allows a smbd to map incoming filenames from a DOS Code page (see the client @@ -1898,6 +1998,10 @@ create mode\fR parameter for forcing particular mode bits to be set on created files. See also the \fIdirectory mode"\fR parameter for masking mode bits on created directories. See also the \fIinherit permissions\fR parameter. +Note that this parameter does not apply to permissions +set by Windows NT/2000 ACL editors. If the administrator wishes to enforce +a mask on access control lists also, they need to set the \fIsecurity mask\fR. + Default: \fBcreate mask = 0744\fR Example: \fBcreate mask = 0775\fR @@ -1970,15 +2074,7 @@ effect. Default: \fBdebug uid = no\fR .TP \fBdebuglevel (G)\fR -The value of the parameter (an integer) allows -the debug level (logging level) to be specified in the -\fIsmb.conf\fR file. This is to give greater -flexibility in the configuration of the system. - -The default will be the debug level specified on -the command line or level zero if none was specified. - -Example: \fBdebug level = 3\fR +Synonym for \fI log level\fR. .TP \fBdefault (G)\fR A synonym for \fI default service\fR. @@ -2022,6 +2118,33 @@ Example: .sp .fi .TP +\fBdelete printer command (G)\fR +With the introduction of MS-RPC based printer +support for Windows NT/2000 clients in Samba 2.2, it is now +possible to delete printer at run time by issuing the +DeletePrinter() RPC call. + +For a Samba host this means that the printer must be +physically deleted from underlying printing system. The \fI deleteprinter command\fR defines a script to be run which +will perform the necessary operations for removing the printer +from the print system and from \fIsmb.conf\fR. + +The \fIdelete printer command\fR is +automatically called with only one parameter: \fI "printer name"\fR. + +Once the \fIdelete printer command\fR has +been executed, \fBsmbd\fR will reparse the \fI smb.conf\fR to associated printer no longer exists. +If the sharename is still valid, then \fBsmbd +\fRwill return an ACCESS_DENIED error to the client. + +See also \fI add printer command\fR, \fIprinting\fR, +\fIshow add +printer wizard\fR + +Default: \fBnone\fR + +Example: \fBdeleteprinter command = /usr/bin/removeprinter +\fR.TP \fBdelete readonly (S)\fR This parameter allows readonly files to be deleted. This is not normal DOS semantics, but is allowed by UNIX. @@ -2032,6 +2155,45 @@ permissions, and DOS semantics prevent deletion of a read only file. Default: \fBdelete readonly = no\fR .TP +\fBdelete share command (G)\fR +Samba 2.2.0 introduced the ability to dynamically +add and delete shares via the Windows NT 4.0 Server Manager. The +\fIdelete share command\fR is used to define an +external program or script which will remove an existing service +definition from \fIsmb.conf\fR. In order to successfully +execute the \fIdelete share command\fR, \fBsmbd\fR +requires that the administrator be connected using a root account (i.e. +uid == 0). + +When executed, \fBsmbd\fR will automatically invoke the +\fIdelete share command\fR with two parameters. +.RS +.TP 0.2i +\(bu +\fIconfigFile\fR - the location +of the global \fIsmb.conf\fR file. +.TP 0.2i +\(bu +\fIshareName\fR - the name of +the existing service. +.RE +.PP +This parameter is only used to remove file shares. To delete printer shares, +see the \fIdelete printer +command\fR. +.PP +.PP +See also \fIdelete share +command\fR, \fIchange +share\fR. +.PP +.PP +Default: \fBnone\fR +.PP +.PP +Example: \fBdelete share command = /usr/local/bin/delshare\fR +.PP +.TP \fBdelete user script (G)\fR This is the full pathname to a script that will be run \fBAS ROOT\fR by \fBsmbd(8)\fRunder special circumstances @@ -2085,33 +2247,6 @@ Default: \fBdelete user script = <empty string> Example: \fBdelete user script = /usr/local/samba/bin/del_user %u\fR .TP -\fBdeleteprinter command (G)\fR -With the introduction of MS-RPC based printer -support for Windows NT/2000 clients in Samba 2.2, it is now -possible to delete printer at run time by issuing the -DeletePrinter() RPC call. - -For a Samba host this means that the printer must be -physically deleted from underlying printing system. The \fI deleteprinter command\fR defines a script to be run which -will perform the necessary operations for removing the printer -from the print system and from \fIsmb.conf\fR. - -The \fIdeleteprinter command\fR is -automatically called with only one parameter: \fI "printer name"\fR. - -Once the \fIdeleteprinter command\fR has -been executed, \fBsmbd\fR will reparse the \fI smb.conf\fR to associated printer no longer exists. -If the sharename is still valid, then \fBsmbd -\fRwill return an ACCESS_DENIED error to the client. - -See also \fI addprinter command\fR, \fIprinting\fR, -\fIshow add -printer wizard\fR - -Default: \fBnone\fR - -Example: \fBdeleteprinter command = /usr/bin/removeprinter -\fR.TP \fBdelete veto files (S)\fR This option is used when Samba is attempting to delete a directory that contains one or more vetoed directories @@ -2220,6 +2355,10 @@ created from this parameter with the value of the \fIforce directory mode \fRparameter. This parameter is set to 000 by default (i.e. no extra mode bits are added). +Note that this parameter does not apply to permissions +set by Windows NT/2000 ACL editors. If the administrator wishes to enforce +a mask on access control lists also, they need to set the \fIdirectory security mask\fR. + See the \fIforce directory mode\fR parameter to cause particular mode bits to always be set on created directories. @@ -2250,26 +2389,23 @@ this mask from being modified. Essentially, zero bits in this mask may be treated as a set of bits the user is not allowed to change. -If not set explicitly this parameter is set to the same -value as the \fIdirectory -mask\fR parameter. To allow a user to -modify all the user/group/world permissions on a directory, set -this parameter to 0777. +If not set explicitly this parameter is set to 0777 +meaning a user is allowed to modify all the user/group/world +permissions on a directory. \fBNote\fR that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. -Administrators of most normal systems will probably want to set -it to 0777. +Administrators of most normal systems will probably want to leave +it as the default of 0777. See also the \fI force directory security mode\fR, \fIsecurity mask\fR, \fIforce security mode \fRparameters. -Default: \fBdirectory security mask = <same as -directory mask>\fR +Default: \fBdirectory security mask = 0777\fR -Example: \fBdirectory security mask = 0777\fR +Example: \fBdirectory security mask = 0700\fR .TP \fBdns proxy (G)\fR Specifies that nmbd(8)when acting as a WINS server and finding that a NetBIOS name has not @@ -2290,44 +2426,38 @@ See also the parameter \fI wins support\fR. Default: \fBdns proxy = yes\fR .TP \fBdomain admin group (G)\fR -This is an \fBEXPERIMENTAL\fR parameter -that is part of the unfinished Samba NT Domain Controller Code. It may -be removed in a later release. To work with the latest code builds -that may have more support for Samba NT Domain Controller functionality -please subscribe to the mailing list samba-ntdom <URL:mailto:samba-ntdom@samba.org> available by -visiting the web page at http://lists.samba.org/ <URL:http://lists.samba.org/>. -.TP -\fBdomain admin users (G)\fR -This is an \fBEXPERIMENTAL\fR parameter -that is part of the unfinished Samba NT Domain Controller Code. It may -be removed in a later release. To work with the latest code builds -that may have more support for Samba NT Domain Controller functionality -please subscribe to the mailing list samba-ntdom <URL:mailto:samba-ntdom@samba.org> available by -visiting the web page at http://lists.samba.org/ <URL:http://lists.samba.org/>. -.TP -\fBdomain groups (G)\fR -This is an \fBEXPERIMENTAL\fR parameter -that is part of the unfinished Samba NT Domain Controller Code. It may -be removed in a later release. To work with the latest code builds -that may have more support for Samba NT Domain Controller functionality -please subscribe to the mailing list samba-ntdom <URL:mailto:samba-ntdom@samba.org> available by -visiting the web page at http://lists.samba.org/ <URL:http://lists.samba.org/>. +This parameter is intended as a temporary solution +to enable users to be a member of the "Domain Admins" group when +a Samba host is acting as a PDC. A complete solution will be provided +by a system for mapping Windows NT/2000 groups onto UNIX groups. +Please note that this parameter has a somewhat confusing name. It +accepts a list of usernames and of group names in standard +\fIsmb.conf\fR notation. + +See also \fIdomain +guest group\fR, \fIdomain +logons\fR + +Default: \fBno domain administrators\fR + +Example: \fBdomain admin group = root @wheel\fR .TP \fBdomain guest group (G)\fR -This is an \fBEXPERIMENTAL\fR parameter -that is part of the unfinished Samba NT Domain Controller Code. It may -be removed in a later release. To work with the latest code builds -that may have more support for Samba NT Domain Controller functionality -please subscribe to the mailing list samba-ntdom <URL:mailto:samba-ntdom@samba.org> available by -visiting the web page at http://lists.samba.org/ <URL:http://lists.samba.org/>. -.TP -\fBdomain guest users (G)\fR -This is an \fBEXPERIMENTAL\fR parameter -that is part of the unfinished Samba NT Domain Controller Code. It may -be removed in a later release. To work with the latest code builds -that may have more support for Samba NT Domain Controller functionality -please subscribe to the mailing list samba-ntdom <URL:mailto:samba-ntdom@samba.org> available by -visiting the web page at http://lists.samba.org/ <URL:http://lists.samba.org/>. +This parameter is intended as a temporary solution +to enable users to be a member of the "Domain Guests" group when +a Samba host is acting as a PDC. A complete solution will be provided +by a system for mapping Windows NT/2000 groups onto UNIX groups. +Please note that this parameter has a somewhat confusing name. It +accepts a list of usernames and of group names in standard +\fIsmb.conf\fR notation. + +See also \fIdomain +admin group\fR, \fIdomain +logons\fR + +Default: \fBno domain guests\fR + +Example: \fBdomain guest group = nobody @guest\fR .TP \fBdomain logons (G)\fR If set to true, the Samba server will serve @@ -2574,6 +2704,11 @@ permissions changed. The default for this parameter is (in octal) mode after the mask set in the \fIcreate mask\fR parameter is applied. +Note that by default this parameter does not apply to permissions +set by Windows NT/2000 ACL editors. If the administrator wishes to enforce +this mask on access control lists also, they need to set the \fIrestrict acl with +mask\fR to true. + See also the parameter \fIcreate mask\fR for details on masking mode bits on files. @@ -2598,6 +2733,11 @@ bits to a created directory. This operation is done after the mode mask in the parameter \fIdirectory mask\fR is applied. +Note that by default this parameter does not apply to permissions +set by Windows NT/2000 ACL editors. If the administrator wishes to enforce +this mask on access control lists also, they need to set the \fIrestrict acl with +mask\fR to true. + See also the parameter \fI directory mask\fR for details on masking mode bits on created directories. @@ -2622,26 +2762,23 @@ the user may have modified to be on. Essentially, one bits in this mask may be treated as a set of bits that, when modifying security on a directory, the user has always set to be 'on'. -If not set explicitly this parameter is set to the same -value as the \fIforce -directory mode\fR parameter. To allow -a user to modify all the user/group/world permissions on a -directory without restrictions, set this parameter to 000. +If not set explicitly this parameter is 000, which +allows a user to modify all the user/group/world permissions on a +directory without restrictions. \fBNote\fR that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. -Administrators of most normal systems will probably want to set -it to 0000. +Administrators of most normal systems will probably want to leave +it set as 0000. See also the \fI directory security mask\fR, \fIsecurity mask\fR, \fIforce security mode \fRparameters. -Default: \fBforce directory security mode = <same as -force directory mode>\fR +Default: \fBforce directory security mode = 0\fR -Example: \fBforce directory security mode = 0\fR +Example: \fBforce directory security mode = 700\fR .TP \fBforce group (S)\fR This specifies a UNIX group name that will be @@ -2689,26 +2826,23 @@ the user may have modified to be on. Essentially, one bits in this mask may be treated as a set of bits that, when modifying security on a file, the user has always set to be 'on'. -If not set explicitly this parameter is set to the same -value as the \fIforce -create mode\fR parameter. To allow a user to -modify all the user/group/world permissions on a file, with no -restrictions set this parameter to 000. +If not set explicitly this parameter is set to 0, +and allows a user to modify all the user/group/world permissions on a file, +with no restrictions. \fBNote\fR that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. -Administrators of most normal systems will probably want to set -it to 0000. +Administrators of most normal systems will probably want to leave +this set to 0000. See also the \fI force directory security mode\fR, \fIdirectory security mask\fR, \fI security mask\fR parameters. -Default: \fBforce security mode = <same as force -create mode>\fR +Default: \fBforce security mode = 0\fR -Example: \fBforce security mode = 0\fR +Example: \fBforce security mode = 700\fR .TP \fBforce user (S)\fR This specifies a UNIX user name that will be @@ -3287,7 +3421,15 @@ you to have separate log files for each user or machine. Example: \fBlog file = /usr/local/samba/var/log.%m \fR.TP \fBlog level (G)\fR -Synonym for \fI debug level\fR. +The value of the parameter (an integer) allows +the debug level (logging level) to be specified in the +\fIsmb.conf\fR file. This is to give greater +flexibility in the configuration of the system. + +The default will be the log level specified on +the command line or level zero if none was specified. + +Example: \fBlog level = 3\fR .TP \fBlogon drive (G)\fR This parameter specifies the local path to @@ -4295,6 +4437,18 @@ See also smbpasswd (5). Default: \fBnull passwords = no\fR .TP +\fBobey pam restrictions (G)\fR +When Samba 2.2 is configure to enable PAM support +(i.e. --with-pam), this parameter will control whether or not Samba +should obey PAM's account and session management directives. The +default behavior is to use PAM for clear text authentication only +and to ignore any account or session management. Note that Samba +always ignores PAM for authentication in the case of \fIencrypt passwords = yes\fR +\&. The reason is that PAM modules cannot support the challenge/response +authentication mechanism needed in the presence of SMB password encryption. + +Default: \fBobey pam restrictions = no\fR +.TP \fBonly user (S)\fR This is a boolean option that controls whether connections with usernames not in the \fIuser\fR @@ -4317,18 +4471,6 @@ parameter. Default: \fBonly user = no\fR .TP -\fBole locking compatibility (G)\fR -This parameter allows an administrator to turn -off the byte range lock manipulation that is done within Samba to -give compatibility for OLE applications. Windows OLE applications -use byte range locking as a form of inter-process communication, by -locking ranges of bytes around the 2^32 region of a file range. This -can cause certain UNIX lock managers to crash or otherwise cause -problems. Setting this parameter to no means you -trust your UNIX lock manager to handle such cases correctly. - -Default: \fBole locking compatibility = yes\fR -.TP \fBonly guest (S)\fR A synonym for \fI guest only\fR. .TP @@ -4423,6 +4565,15 @@ containing in the Samba documentation. Default: \fBos2 driver map = <empty string> \fR.TP +\fBpam password change (G)\fR +With the addition of better PAM support in Samba 2.2, +this parameter, it is possible to use PAM's password change control +flag for Samba. If enabled, then PAM will be used for password +changes when requested by an SMB client, and the \fIpasswd chat\fR must be +be changed to work with the pam prompts. + +Default: \fBpam password change = no\fR +.TP \fBpanic action (G)\fR This is a Samba developer option that allows a system command to be called when either smbd(8)crashes. This is usually used to draw attention to the fact that @@ -4468,8 +4619,17 @@ in the smbpasswd file is being changed, without access to the old password cleartext. In this case the old password cleartext is set to "" (the empty string). +Also, if the \fIpam +password change\fR parameter is set to true, then the +chat sequence should consist of three elements. The first element should +match the pam prompt for the old password, the second element should match +the pam prompt for the first request for the new password, and the final +element should match the pam prompt for the second request for the new password. +These matches are done case insentively. Under most conditions this change +is done as root so the prompt for the old password will never be matched. + See also \fIunix password -sync\fR, \fI passwd program\fR and \fIpasswd chat debug\fR. +sync\fR, \fI passwd program\fR , \fIpasswd chat debug\fR and \fIpam password change\fR. Default: \fBpasswd chat = *new*password* %n\\n *new*password* %n\\n *changed*\fR @@ -5230,6 +5390,27 @@ is in fact the browse master on it's segment. Default: \fBremote browse sync = <empty string> \fR.TP +\fBrestrict acl with mask (S)\fR +This is a boolean parameter. If set to false (default), then +Creation of files with access control lists (ACLS) and modification of ACLs +using the Windows NT/2000 ACL editor will be applied directly to the file +or directory. + +If set to True, then all requests to set an ACL on a file will have the +parameters \fIcreate mask\fR, +\fIforce create mode\fR +applied before setting the ACL, and all requests to set an ACL on a directory will +have the parameters \fIdirectory +mask\fR, \fIforce +directory mode\fR applied before setting the ACL. + +See also \fIcreate mask\fR, +\fIforce create mode\fR, +\fIdirectory mask\fR, +\fIforce directory mode\fR + +Default: \fBrestrict acl with mask = no\fR +.TP \fBrestrict anonymous (G)\fR This is a boolean parameter. If it is true, then anonymous access to the server will be restricted, namely in the @@ -5562,25 +5743,22 @@ this mask from being modified. Essentially, zero bits in this mask may be treated as a set of bits the user is not allowed to change. -If not set explicitly this parameter is set to the same -value as the \fIcreate mask -\fRparameter. To allow a user to modify all the -user/group/world permissions on a file, set this parameter to -0777. +If not set explicitly this parameter is 0777, allowing +a user to modify all the user/group/world permissions on a file. \fBNote\fR that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will -probably want to set it to 0777. +probably want to leave it set to 0777. See also the \fIforce directory security mode\fR, \fIdirectory security mask\fR, \fIforce security mode\fR parameters. -Default: \fBsecurity mask = <same as create mask> -\fR -Example: \fBsecurity mask = 0777\fR +Default: \fBsecurity mask = 0777\fR + +Example: \fBsecurity mask = 0770\fR .TP \fBserver string (G)\fR This controls what string will show up in the diff --git a/docs/manpages/smbcontrol.1 b/docs/manpages/smbcontrol.1 index 20e08dd832..0c894aa959 100644 --- a/docs/manpages/smbcontrol.1 +++ b/docs/manpages/smbcontrol.1 @@ -3,7 +3,7 @@ .\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/> .\" Please send any bug reports, improvements, comments, patches, .\" etc. to Steve Cheng <steve@ggi-project.org>. -.TH "SMBCONTROL" "1" "24 April 2001" "" "" +.TH "SMBCONTROL" "1" "01 June 2001" "" "" .SH NAME smbcontrol \- send messages to smbd or nmbd processes .SH SYNOPSIS diff --git a/docs/manpages/smbspool.8 b/docs/manpages/smbspool.8 index 6bdfeb6adb..e30755c4b2 100644 --- a/docs/manpages/smbspool.8 +++ b/docs/manpages/smbspool.8 @@ -3,9 +3,9 @@ .\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/> .\" Please send any bug reports, improvements, comments, patches, .\" etc. to Steve Cheng <steve@ggi-project.org>. -.TH "SMBSPOOL" "8" "24 April 2001" "" "" +.TH "SMBSPOOL" "8" "01 June 2001" "" "" .SH NAME -nmblookup \- send print file to an SMB printer +smbspool \- send print file to an SMB printer .SH SYNOPSIS .sp \fBsmbspool\fR [ \fBjob\fR ] [ \fBuser\fR ] [ \fBtitle\fR ] [ \fBcopies\fR ] [ \fBoptions\fR ] [ \fBfilename\fR ] diff --git a/docs/manpages/smbstatus.1 b/docs/manpages/smbstatus.1 index 21ece4b02a..d2e3c97e79 100644 --- a/docs/manpages/smbstatus.1 +++ b/docs/manpages/smbstatus.1 @@ -3,7 +3,7 @@ .\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/> .\" Please send any bug reports, improvements, comments, patches, .\" etc. to Steve Cheng <steve@ggi-project.org>. -.TH "SMBSTATUS" "1" "24 April 2001" "" "" +.TH "SMBSTATUS" "1" "01 June 2001" "" "" .SH NAME smbstatus \- report on current Samba connections .SH SYNOPSIS diff --git a/docs/manpages/swat.8 b/docs/manpages/swat.8 index 4ec6bfba5d..b53e057430 100644 --- a/docs/manpages/swat.8 +++ b/docs/manpages/swat.8 @@ -3,12 +3,12 @@ .\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/> .\" Please send any bug reports, improvements, comments, patches, .\" etc. to Steve Cheng <steve@ggi-project.org>. -.TH "SWAT" "8" "24 April 2001" "" "" +.TH "SWAT" "8" "01 June 2001" "" "" .SH NAME swat \- Samba Web Administration Tool .SH SYNOPSIS .sp -\fBnmblookup\fR [ \fB-s <smb config file>\fR ] [ \fB-a\fR ] +\fBswat\fR [ \fB-s <smb config file>\fR ] [ \fB-a\fR ] .SH "DESCRIPTION" .PP This tool is part of the Sambasuite. diff --git a/docs/textdocs/CVS_ACCESS.txt b/docs/textdocs/CVS_ACCESS.txt deleted file mode 100644 index c854d3fe33..0000000000 --- a/docs/textdocs/CVS_ACCESS.txt +++ /dev/null @@ -1,124 +0,0 @@ -!== -!== CVS_ACCESS.txt for Samba release 2.0.4 18 May 1999 -!== -Contributor: Modified from the Web pages by Jeremy Allison. -Date: 23 Dec 1997 -Status: Current - -How to get access to Samba source code via cvs. -=============================================== - -CVS Access to samba.org ------------------------------- - -The machine samba.org runs a publicly accessible CVS -repository for access to the source code of several packages, -including samba, rsync and jitterbug. This document describes -how to get anonymous read-only access to this source code. - -Access via cvsweb ------------------ - -You can access the source code via your favourite WWW browser. -This allows you to access the contents of individual files in -the repository and also to look at the revision history and -commit logs of individual files. You can also ask for a diff -listing between any two versions on the repository. - -Use the URL : http://samba.org/cgi-bin/cvsweb - -Access via cvs --------------- - -You can also access the source code via a normal cvs client. -This gives you much more control over you can do with the -repository and allows you to checkout whole source trees -and keep them uptodate via normal cvs commands. This is the -preferred method of access if you are a developer and not -just a casual browser. - -To download the latest cvs source code, point your -browser at the URL : - -http://www.cyclic.com/ - -and click on the 'How to get cvs' link. CVS is free -software under the GNU GPL (as is Samba). - -To gain access via anonymous cvs use the following steps. -For this example it is assumed that you want a copy of the -samba source code. For the other source code repositories -on this system just substitute the correct package name - -1. Install a recent copy of cvs. All you really need is a - copy of the cvs client binary. - -2. Run the command - - cvs -d :pserver:cvs@samba.org:/cvsroot login - -When it asks you for a password type 'cvs' (not including -the quotes). - -3. Run the command - - cvs -d :pserver:cvs@samba.org:/cvsroot co samba - -This will create a directory called samba containing the -latest samba source code. This currently corresponds to the -1.9.18alpha development tree. - -4. Whenever you want to merge in the latest code changes use -the following command from within the samba directory: - - cvs update -d -P - -NOTE: If you instead want the latest source code for the -1.9.17 stable tree then replace step 4 with the command: - - cvs -d :pserver:cvs@samba.org:/cvsroot co -r BRANCH_1_9_17 samba - -Access to the NT DOMAIN Controller code ---------------------------------------- - -The Samba PDC code is being separately developed on a -branch named BRANCH_NTDOM. To gain access to the latest -source code (this changes daily) do the following: - -1). Log onto cvs - - cvs -d :pserver:cvs@samba.org:/cvsroot login - -When it asks you for a password type 'cvs' (not including -the quotes). - -2). Check out the BRANCH_NTDOM by typing : - - cvs -d :pserver:cvs@samba.org:/cvsroot co -r BRANCH_NTDOM samba - -This will create a directory called samba containing the -latest snapshot of the domain controller code. - -3). To keep this code up to date after it has been -changed in the cvs repository, cd into the samba -directory you created above and type : - - cvs update -d -P - -How it's done. --------------- - -If you are interested in how anonymous cvs access is set up and -want to set it up on your own system then you might like to checkout -the pserver source code using the the command : - - cvs -d :pserver:cvs@samba.org:/cvsroot co pserver - -You really have to know what you are doing to do this. Please don't -email samba-bugs with basic cvs or unix security questions. - -Reporting problems. -------------------- - -If you have any problems with this system please email -samba-bugs@samba.org. diff --git a/docs/textdocs/DOMAIN.txt b/docs/textdocs/DOMAIN.txt deleted file mode 100644 index d16f3aa55d..0000000000 --- a/docs/textdocs/DOMAIN.txt +++ /dev/null @@ -1,381 +0,0 @@ -!== -!== DOMAIN.txt for Samba release 2.0.4 18 May 1999 -!== -Contributor: Samba Team -Updated: December 4, 1998 (John H Terpstra) - -Subject: Network Logons and Roaming (Roving) Profiles -=========================================================================== - -A domain and a workgroup are exactly the same thing in terms of network -browsing. The difference is that a distributable authentication -database is associated with a domain, for secure login access to a -network. Also, different access rights can be granted to users if they -successfully authenticate against a domain logon server (samba does not -support this, but NT server and other systems based on NT server do). - -As of samba-2.0.0 this is now a work in progress that is expected to -mature rapidly. Since this document pre-dates samba-2.0.0 it should be -read from the perspective of it's origins but the reader should understand -that the following details may NOT be up to date with current development. - -The SMB client logging on to a domain has an expectation that every other -server in the domain should accept the same authentication information. -However the network browsing functionality of domains and workgroups is -identical and is explained in BROWSING.txt. - -Issues related to the single-logon network model are discussed in this -document. Samba supports domain logons, network logon scripts, and user -profiles for MS Windows for workgroups and MS Windows 9X clients. - -Work is underway to support domain logon for MS Windows NT clients - this -is mostly working but will undergo much change as the the behaviour of the -new code matures and becomes easier to manage. - -Support is also not complete. Samba does not yet support the sharing -of the Windows NT-style SAM database with other systems. However this is -only one way of having a shared user database: exactly the same effect can -be achieved by having all servers in a domain share a distributed NIS or -Kerberos authentication database. - -When an SMB client in a domain wishes to logon it broadcast requests for a -logon server. The first one to reply gets the job, and validates its -password using whatever mechanism the Samba administrator has installed. -It is possible (but very stupid) to create a domain where the user -database is not shared between servers, ie they are effectively workgroup -servers advertising themselves as participating in a domain. This -demonstrates how authentication is quite different from but closely -involved with domains. - -Another thing commonly associated with single-logon domains is remote -administration over the SMB protocol. Again, there is no reason why this -cannot be implemented with an underlying username database which is -different from the Windows NT SAM. Support for the Remote Administration -Protocol is planned for a future release of Samba. - -The domain support works for WfWg, and Win95 clients and NT 4.0 and 3.51. -Domain support is currently at an early experimental stage for NT 4.0 and -NT 3.51. Support for Windows OS/2 clients is still being worked on and is -still experimental. - -Support for profiles is confirmed as working for Win95, NT 4.0 and NT 3.51. -It is possible to specify: the profile location; script file to be loaded -on login; the user's home directory; and for NT a kick-off time could also -now easily be supported. - -With NT Workstations, all this does not require the use or intervention of -an NT 4.0 or NT 3.51 server: Samba can now replace the logon services -provided by an NT server, to a limited and experimental degree (for example, -running "User Manager for Domains" will not provide you with access to -a domain created by a Samba Server). - -With Win95, the help of an NT server can be enlisted, both for profile storage -and for user authentication. For details on user authentication, see -security_level.txt. For details on profile storage, see below. - - -Using these features you can make your clients verify their logon via -the Samba server; make clients run a batch file when they logon to -the network and download their preferences, desktop and start menu. - - -Configuration Instructions: Network Logons -============================================== - -To use domain logons and profiles you need to do the following: - - -1) Setup nmbd and smbd by configuring smb.conf so that Samba is - acting as the master browser. See <your OS>_INSTALL.txt and BROWSING.txt - for details. - -2) Setup a WINS server (see NetBIOS.txt) and configure all your clients - to use that WINS service. - -3) Create a share called [netlogon] in your smb.conf. This share should - be readable by all users, and probably should not be writeable. This - share will hold your network logon scripts, and the CONFIG.POL file - (Note: for details on the CONFIG.POL file, how to use it, what it is, - refer to the Microsoft Windows NT Administration documentation. - The format of these files is not known, so you will need to use - Microsoft tools). - -For example I have used: - - [netlogon] - path = /data/dos/netlogon - writeable = no - guest ok = no - -Note that it is important that this share is not writeable by ordinary -users, in a secure environment: ordinary users should not be allowed -to modify or add files that another user's computer would then download -when they log in. - -4) in the [global] section of smb.conf set the following: - - domain logons = yes - logon script = %U.bat - -The choice of batch file is, of course, up to you. The above would -give each user a separate batch file as the %U will be changed to -their username automatically. The other standard % macros may also be -used. You can make the batch files come from a subdirectory by using -something like: - - logon script = scripts\%U.bat - -5) create the batch files to be run when the user logs in. If the batch - file doesn't exist then no batch file will be run. - -In the batch files you need to be careful to use DOS style cr/lf line -endings. If you don't then DOS may get confused. I suggest you use a -DOS editor to remotely edit the files if you don't know how to produce -DOS style files under unix. - -6) Use smbclient with the -U option for some users to make sure that - the \\server\NETLOGON share is available, the batch files are - visible and they are readable by the users. - -7) you will probabaly find that your clients automatically mount the - \\SERVER\NETLOGON share as drive z: while logging in. You can put - some useful programs there to execute from the batch files. - -NOTE: You must be using "security = user" or "security = server" for -domain logons to work correctly. Share level security won't work -correctly. - - - -Configuration Instructions: Setting up Roaming User Profiles -================================================================ - -In the [global] section of smb.conf set the following (for example): - - logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath - -The default for this option is \\%N\%U\profile, namely -\\sambaserver\username\profile. The \\N%\%U service is created -automatically by the [homes] service. - -If you are using a samba server for the profiles, you _must_ make the -share specified in the logon path browseable. Windows 95 appears to -check that it can see the share and any subdirectories within that share -specified by the logon path option, rather than just connecting straight -away. It also attempts to create the components of the full path for -you. If the creation of any component fails, or if it cannot see any -component of the path, the profile creation / reading fails. - -[lkcl 26aug96 - we have discovered a problem where Windows clients can -maintain a connection to the [homes] share in between logins. The -[homes] share must NOT therefore be used in a profile path.] - - -Windows 95 ----------- - -When a user first logs in on Windows 95, the file user.DAT is created, -as are folders "Start Menu", "Desktop", "Programs" and "Nethood". -These directories and their contents will be merged with the local -versions stored in c:\windows\profiles\username on subsequent logins, -taking the most recent from each. You will need to use the [global] -options "preserve case = yes", "short case preserve = yes" and -"case sensitive = no" in order to maintain capital letters in shortcuts -in any of the profile folders. - -The user.DAT file contains all the user's preferences. If you wish to -enforce a set of preferences, rename their user.DAT file to user.MAN, -and deny them write access to this file. - -2) On the Windows 95 machine, go to Control Panel | Passwords and - select the User Profiles tab. Select the required level of - roaming preferences. Press OK, but do _not_ allow the computer - to reboot. - -3) On the Windows 95 machine, go to Control Panel | Network | - Client for Microsoft Networks | Preferences. Select 'Log on to - NT Domain'. Then, ensure that the Primary Logon is 'Client for - Microsoft Networks'. Press OK, and this time allow the computer - to reboot. - -Under Windows 95, Profiles are downloaded from the Primary Logon. -If you have the Primary Logon as 'Client for Novell Networks', then -the profiles and logon script will be downloaded from your Novell -Server. If you have the Primary Logon as 'Windows Logon', then the -profiles will be loaded from the local machine - a bit against the -concept of roaming profiles, if you ask me. - -You will now find that the Microsoft Networks Login box contains -[user, password, domain] instead of just [user, password]. Type in -the samba server's domain name (or any other domain known to exist, -but bear in mind that the user will be authenticated against this -domain and profiles downloaded from it, if that domain logon server -supports it), user name and user's password. - -Once the user has been successfully validated, the Windows 95 machine -will inform you that 'The user has not logged on before' and asks you -if you wish to save the user's preferences? Select 'yes'. - -Once the Windows 95 client comes up with the desktop, you should be able -to examine the contents of the directory specified in the "logon path" -on the samba server and verify that the "Desktop", "Start Menu", -"Programs" and "Nethood" folders have been created. - -These folders will be cached locally on the client, and updated when -the user logs off (if you haven't made them read-only by then :-). -You will find that if the user creates further folders or short-cuts, -that the client will merge the profile contents downloaded with the -contents of the profile directory already on the local client, taking -the newest folders and short-cuts from each set. - -If you have made the folders / files read-only on the samba server, -then you will get errors from the w95 machine on logon and logout, as -it attempts to merge the local and the remote profile. Basically, if -you have any errors reported by the w95 machine, check the unix file -permissions and ownership rights on the profile directory contents, -on the samba server. - - -If you have problems creating user profiles, you can reset the user's -local desktop cache, as shown below. When this user then next logs in, -they will be told that they are logging in "for the first time". - - -1) instead of logging in under the [user, password, domain] dialog], - press escape. - -2) run the regedit.exe program, and look in: - - HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList - - you will find an entry, for each user, of ProfilePath. Note the - contents of this key (likely to be c:\windows\profiles\username), - then delete the key ProfilePath for the required user. - - [Exit the registry editor]. - -3) WARNING - before deleting the contents of the directory listed in - the ProfilePath (this is likely to be c:\windows\profiles\username), - ask them if they have any important files stored on their desktop - or in their start menu. delete the contents of the directory - ProfilePath (making a backup if any of the files are needed). - - This will have the effect of removing the local (read-only hidden - system file) user.DAT in their profile directory, as well as the - local "desktop", "nethood", "start menu" and "programs" folders. - -4) search for the user's .PWL password-cacheing file in the c:\windows - directory, and delete it. - -5) log off the windows 95 client. - -6) check the contents of the profile path (see "logon path" described - above), and delete the user.DAT or user.MAN file for the user, - making a backup if required. - - -If all else fails, increase samba's debug log levels to between 3 and 10, -and / or run a packet trace program such as tcpdump or netmon.exe, and -look for any error reports. - -If you have access to an NT server, then first set up roaming profiles -and / or netlogons on the NT server. Make a packet trace, or examine -the example packet traces provided with NT server, and see what the -differences are with the equivalent samba trace. - - -Windows NT Workstation 4.0 --------------------------- - -When a user first logs in to a Windows NT Workstation, the profile -NTuser.DAT is created. The profile location can be now specified -through the "logon path" parameter, in exactly the same way as it -can for Win95. [lkcl 10aug97 - i tried setting the path to -\\samba-server\homes\profile, and discovered that this fails because -a background process maintains the connection to the [homes] share -which does _not_ close down in between user logins. you have to -have \\samba-server\%L\profile, where user is the username created -from the [homes] share]. - -There is a parameter that is now available for use with NT Profiles: -"logon drive". This should be set to "h:" or any other drive, and -should be used in conjunction with the new "logon home" parameter. - -The entry for the NT 4.0 profile is a _directory_ not a file. The NT -help on profiles mentions that a directory is also created with a .PDS -extension. The user, while logging in, must have write permission to -create the full profile path (and the folder with the .PDS extension) -[lkcl 10aug97 - i found that the creation of the .PDS directory failed, -and had to create these manually for each user, with a shell script. -also, i presume, but have not tested, that the full profile path must -be browseable just as it is for w95, due to the manner in which they -attempt to create the full profile path: test existence of each path -component; create path component]. - -In the profile directory, NT creates more folders than 95. It creates -"Application Data" and others, as well as "Desktop", "Nethood", -"Start Menu" and "Programs". The profile itself is stored in a file -NTuser.DAT. Nothing appears to be stored in the .PDS directory, and -its purpose is currently unknown. - -You can use the System Control Panel to copy a local profile onto -a samba server (see NT Help on profiles: it is also capable of firing -up the correct location in the System Control Panel for you). The -NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN -turns a profile into a mandatory one. - -[lkcl 10aug97 - i notice that NT Workstation tells me that it is -downloading a profile from a slow link. whether this is actually the -case, or whether there is some configuration issue, as yet unknown, -that makes NT Workstation _think_ that the link is a slow one is a -matter to be resolved]. - -[lkcl 20aug97 - after samba digest correspondance, one user found, and -another confirmed, that profiles cannot be loaded from a samba server -unless "security = user" and "encrypt passwords = yes" (see the file -ENCRYPTION.txt) or "security = server" and "password server = ip.address. -of.yourNTserver" are used. either of these options will allow the NT -workstation to access the samba server using LAN manager encrypted -passwords, without the user intervention normally required by NT -workstation for clear-text passwords]. - -[lkcl 25aug97 - more comments received about NT profiles: the case of -the profile _matters_. the file _must_ be called NTuser.DAT or, for -a mandatory profile, NTuser.MAN]. - - -Windows NT Server ------------------ - -There is nothing to stop you specifying any path that you like for the -location of users' profiles. Therefore, you could specify that the -profile be stored on a samba server, or any other SMB server, as long as -that SMB server supports encrypted passwords. - - - -Sharing Profiles between W95 and NT Workstation 4.0 ---------------------------------------------------- - -The default logon path is \\%N\U%. NT Workstation will attempt to create -a directory "\\samba-server\username.PDS" if you specify the logon path -as "\\samba-server\username" with the NT User Manager. Therefore, you -will need to specify (for example) "\\samba-server\username\profile". -NT 4.0 will attempt to create "\\samba-server\username\profile.PDS", which -is more likely to succeed. - -If you then want to share the same Start Menu / Desktop with W95, you will -need to specify "logon path = \\samba-server\username\profile" [lkcl 10aug97 -this has its drawbacks: i created a shortcut to telnet.exe, which attempts -to run from the c:\winnt\system32 directory. this directory is obviously -unlikely to exist on a Win95-only host]. - -If you have this set up correctly, you will find separate user.DAT and -NTuser.DAT files in the same profile directory. - -[lkcl 25aug97 - there are some issues to resolve with downloading of -NT profiles, probably to do with time/date stamps. i have found that -NTuser.DAT is never updated on the workstation after the first time that -it is copied to the local workstation profile directory. this is in -contrast to w95, where it _does_ transfer / update profiles correctly]. - diff --git a/docs/textdocs/MIRRORS.txt b/docs/textdocs/MIRRORS.txt deleted file mode 100755 index a133f261c5..0000000000 --- a/docs/textdocs/MIRRORS.txt +++ /dev/null @@ -1,6 +0,0 @@ -!== -!== MIRRORS.txt for Samba release 2.0.4 18 May 1999 -!== - -For a list of web and ftp mirrors please see -http://samba.org/samba/ diff --git a/docs/textdocs/outdated/NTDOMAIN.txt b/docs/textdocs/outdated/NTDOMAIN.txt new file mode 100644 index 0000000000..8408acb979 --- /dev/null +++ b/docs/textdocs/outdated/NTDOMAIN.txt @@ -0,0 +1,51 @@ +!== +!== NTDOMAIN.txt for Samba release 2.0.4 18 May 1999 +!== +Contributor: Luke Kenneth Casson Leighton (samba-bugs@samba.org) + Copyright (C) 1997 Luke Kenneth Casson Leighton +Created: October 20, 1997 +Updated: February 25, 1999 (Jerry Carter) + +Subject: NT Domain Logons +=========================================================================== + +As of 1.9.18alpha1, Samba supports logins for NT 3.51 and 4.0 Workstations, +without the need, use or intervention of NT Server. This document describes +how to set this up. Over the continued development of the 1.9.18alpha +series, this process (and therefore this document) should become simpler. + +One useful thing to do is to get this version of Samba up and running +with Win95 profiles, as you would for the current stable version of +Samba (currently at 1.9.17p4), and is fully documented. You will need +to set up encrypted passwords. Even if you don't have any Win95 machines, +using your Samba Server to store the profile for one of your NT Workstation +users is a good test that you have 1.9.18alpha1 correctly configured *prior* +to attempting NT Domain Logons. + +The support is still experimental, so should be used at your own risk. + +NT is not as robust as you might have been led to believe: during the +development of the Domain Logon Support, one person reported having to +reinstall NT from scratch: their workstation had become totally unuseable. + +[further reports on ntsec@iss.net by independent administrators showing + similar symptoms lead us to believe that the SAM database file may be + corruptible. this _is_ recoverable (or, at least the machine is accessible), + by deleting the SAM file, under which circumstances all user account details + are lost, but at least the Administrator can log in with a blank password. + this is *not* possible except if the NT system is installed in a FAT + partition.] + +This *has* been reported to the NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM digest. + +========================================================================== +Please note that Samba 2.0 does not **officially** support domain logons +for Windows NT clients. Of course, domain logon support for Windows 9x +clients is complete and official. These are two different issues. + +Samba's capability to act as a Primary Domain Controller for Windows NT +domains is not advertised as it is not completed yet. For more information +regarding how to obtain the latest development (HEAD branch) source code +and what features are available, please refer to the NT Domain FAQ on-line +at the Samba web site under the documentation page. + diff --git a/docs/textdocs/outdated/PROJECTS b/docs/textdocs/outdated/PROJECTS new file mode 100644 index 0000000000..3008bea430 --- /dev/null +++ b/docs/textdocs/outdated/PROJECTS @@ -0,0 +1,88 @@ + Samba Projects Directory + ======================== + + +>>>>> NOTE: THIS FILE IS NOW VERY OUT OF DATE <<<<< + + +This is a list of who's working on what in Samba. It's not guaranteed +to be uptodate or accurate but I hope it will help us getting +coordinated. + +If you are working on something to do with Samba and you aren't here +then please let me know! Also, if you are listed below and you have +any corrections or updates then please let me know. + +Email contact: +samba-bugs@samba.org + +======================================================================== +Documentation and FAQ + +Docs and FAQ files for the Samba suite of software. + +Contact samba-bugs@samba.org with the diffs. These are urgently +required. + +The FAQ is being added to on an ad hoc basis, see the web pages for info. + +Mark Preston was working on a set of formatted docs for Samba. Is this +still happening? Contact mpreston@sghms.ac.uk + +Status last updated 2nd October 1996 +======================================================================== + +======================================================================== +Netbeui support + +This aimed to produce patches so that Samba can be used with clients +that do not have TCP/IP. It will try to remain as portable as possible. +Contact Brian.Onn@Canada.Sun.COM (Brian Onn) Unfortunately it died, and +although a lot of people have expressed interest nobody has come forward +to do it. The Novell port (see Samba web pages) includes NetBEUI +functionality in a proprietrary library which should still be helpful as +we have the interfaces. Alan Cox (a.cox@li.org) has the information +required to write the state machine if someone is going to do the work. + +Status last updated 2nd October 1996 +======================================================================== + +======================================================================== +Smbfs + +A mountable smb filesystem for Linux using the userfs userspace filesystem + +Contact lendecke@namu01.gwdg.de (Volker Lendecke) + +This works really well, and is measurably more efficient than commercial +client software. It is now part of the Linux kernel. Long filename support +is in use. + +Status last updated June 1997 +======================================================================== + +======================================================================== +Admin Tool + +Aims to produce a nice smb.conf editor and other useful tools for +administering a Samba system. + +Contact: Steve Brown (steve@unicorn.dungeon.com) + +In the design phase. + +Status last updated 4th September 1994 +======================================================================== + + +======================================================================== +Lanman Client. + +Contact: john@amanda.xs4all.nl (John Stewart) + +Aims to produce a reliable LANMAN Client implementation for LINUX, +and possibly other variations of UNIX. Project ably started by +Tor Lillqvist; tml@hemuli.tte.vtt.fi + +Status last updated 17th January 1995 +======================================================================== |