From 07e38f7a9d7f188dfa565abb186eaf08c6f93dd9 Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Thu, 17 Apr 2003 12:07:32 +0000 Subject: Adding Mimir's edits. (This used to be commit c77c4e57dcecd6eeaadffe1b1f78483eaaa79217) --- docs/docbook/devdoc/gencache.sgml | 119 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 119 insertions(+) create mode 100644 docs/docbook/devdoc/gencache.sgml diff --git a/docs/docbook/devdoc/gencache.sgml b/docs/docbook/devdoc/gencache.sgml new file mode 100644 index 0000000000..1ba2f77c9d --- /dev/null +++ b/docs/docbook/devdoc/gencache.sgml @@ -0,0 +1,119 @@ + + + + RafalSzczesniak + + April 2003 + + +General cache mechanism and API + + +Abstract + +General cache (gencache) was designed to combine various kinds of caching +mechanisms into one, defined by a simple API. This way, anyone can use it +to create their own caching layer on top of gencache. An example of +such approach is the netbios name cache. + + + + +The mechanism + +Gencache utilises tdb database, like many other +parts of Samba. As its origins are in Berkeley DB implementation, it +uses key/value pairs stored in binary file. The values gencache +operates on are string-based, however. This makes very easy to use it +in command line environment eg. to quickly take a look at what's in +the cache or set some value. + + + +All the data is stored in gencache.tdb +file. Records put there are in key/value format as mentioned below, +but as it's a cache, the timeout plays also important role and has a +special place in the key/value pair, as well as API. + + + + + +The data structure + +The record stored in gencache.tdb file consists +of the key, the value and the expiration timeout. While the first part +is stored completely independent from the others, the last two are +kept together. The form the record has is: + + + +key: <string&bt; +value: <12-digit timeout&bt;/<string> + + +The timeout part is the ASCII representation of +time_t value of the time when the cache entry +expires. Obviously the API, the programmer is provided with, hides this detail, +so that you don't have to care about checking it. Simply watch +carefully the return status of the function. + + + + +The API + + +BOOL gencache_init() + + +This is used to initialise to whole caching mechanism. It means +opening the file or creating it if non-existing. If it's already been +opened earlier, then the routine just does nothing and returns +true. If something goes wrong, say the user +doesn't have necessary rights, the function returns +false. + + +BOOL gencache_shutdown() + + +This is the proper way to close the cache file. It simply +returns true after successful closing file and +false upon a failure. + + +BOOL gencache_set(const char* keystr, const char* value, time_t timeout) + + +This is one of the most basic functions. What it allows you to +do is to set some particular cache entry. If the entry haven't +existed yet, the function will act just as it was "gencache_add" +function. If it's already been in the cache, the entry will be set to +the new value. In either case, the cache entry will be set with given +key, value and timeout. Thus it is comfortable way to just set the +entry and not care about the details. + + +BOOL gencache_set_only(const char* keystr, const char* value, time_t timeout) + + + +BOOL gencache_del(const char* keystr) + + + +BOOL gencache_get(const char* keystr, char** valstr, time_t* timeout) + + + +void gencache_iterate(void (*fn)(const char* key, const char *value, time_t timeout, void* dptr), + void* data, const char* keystr_pattern) + + + + +Writing your own caching layer + + + -- cgit From 800f68d2fbba2cc1727329c5c026e5a8165b9fd0 Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Thu, 17 Apr 2003 12:08:03 +0000 Subject: Small edits. (This used to be commit f75624dad4183748fcf31390e249b945716c333a) --- docs/docbook/projdoc/NT4Migration.sgml | 4 +++- docs/docbook/projdoc/passdb.sgml | 4 +--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/docbook/projdoc/NT4Migration.sgml b/docs/docbook/projdoc/NT4Migration.sgml index 3ff2fa1e7e..1f7371de36 100644 --- a/docs/docbook/projdoc/NT4Migration.sgml +++ b/docs/docbook/projdoc/NT4Migration.sgml @@ -14,7 +14,9 @@ Samba-3 based domain control. Planning and Getting Started -You must use at least the following ... + +You must use at least the following ... + Objectives diff --git a/docs/docbook/projdoc/passdb.sgml b/docs/docbook/projdoc/passdb.sgml index 762d77cd46..0de0376df8 100644 --- a/docs/docbook/projdoc/passdb.sgml +++ b/docs/docbook/projdoc/passdb.sgml @@ -450,9 +450,7 @@ include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/samba.schema - -## uncomment this line if you want to support the RFC2307 (NIS) schema -## include /etc/openldap/schema/nis.schema +include /etc/openldap/schema/nis.schema .... -- cgit From 491aa2bfde1010709e61807a62d5a77b54a6179f Mon Sep 17 00:00:00 2001 From: Simo Sorce Date: Thu, 17 Apr 2003 14:25:52 +0000 Subject: seem that someone changed the semanthic of unix_strlower without fixing all places where it was used, this caused me segfaults in the last week :( add more debugging in idmap to chase down a problem (This used to be commit 6393105bda12fb3f6211e4f0128aabf588431b49) --- source3/passdb/pdb_tdb.c | 10 +++++++--- source3/sam/gumm_tdb.c | 9 ++++++--- source3/sam/idmap_tdb.c | 4 ++-- 3 files changed, 15 insertions(+), 8 deletions(-) diff --git a/source3/passdb/pdb_tdb.c b/source3/passdb/pdb_tdb.c index 7e2f4b832f..3a1702a4e0 100644 --- a/source3/passdb/pdb_tdb.c +++ b/source3/passdb/pdb_tdb.c @@ -585,8 +585,10 @@ static NTSTATUS tdbsam_getsampwnam (struct pdb_methods *my_methods, SAM_ACCOUNT return nt_status; } + /* Data is stored in all lower-case */ - unix_strlower(sname, -1, name, sizeof(name)); + fstrcpy(name, sname); + strlower(name); /* set search key */ slprintf(keystr, sizeof(keystr)-1, "%s%s", USERPREFIX, name); @@ -692,7 +694,8 @@ static NTSTATUS tdbsam_delete_sam_account(struct pdb_methods *my_methods, SAM_AC uint32 rid; fstring name; - unix_strlower(pdb_get_username(sam_pass), -1, name, sizeof(name)); + fstrcpy(name, pdb_get_username(sam_pass)); + strlower(name); /* open the TDB */ if (!(pwd_tdb = tdb_open_log(tdb_state->tdbsam_location, 0, TDB_DEFAULT, O_RDWR, 0600))) { @@ -826,7 +829,8 @@ static BOOL tdb_update_sam(struct pdb_methods *my_methods, SAM_ACCOUNT* newpwd, } data.dptr = buf; - unix_strlower(pdb_get_username(newpwd), -1, name, sizeof(name)); + fstrcpy(name, pdb_get_username(newpwd)); + strlower(name); DEBUG(5, ("Storing %saccount %s with RID %d\n", flag == TDB_INSERT ? "(new) " : "", name, user_rid)); diff --git a/source3/sam/gumm_tdb.c b/source3/sam/gumm_tdb.c index 5e390490cf..5da2407faa 100644 --- a/source3/sam/gumm_tdb.c +++ b/source3/sam/gumm_tdb.c @@ -264,7 +264,8 @@ static NTSTATUS get_object_by_name(TALLOC_CTX *mem_ctx, struct tdbsam2_object *o return ret; } - unix_strlower(name, -1, objname, sizeof(objname)); + fstrcpy(objname, name); + strlower(objname); slprintf(keystr, sizeof(keystr)-1, "%s%s", NAMEPREFIX, objname); key.dptr = keystr; @@ -603,7 +604,8 @@ static NTSTATUS tdbsam2_get_domain_sid(DOM_SID *sid, const char* name) goto done; } - unix_strlower(name, -1, domname, sizeof(domname)); + fstrcpy(domname, name); + strlower(domname); ret = get_object_by_name(mem_ctx, &obj, domname); @@ -650,7 +652,8 @@ static NTSTATUS tdbsam2_set_domain_sid (const DOM_SID *sid, const char *name) } } - unix_strlower(name, -1, domname, sizeof(domname)); + fstrcpy(domname, name); + strlower(domname); /* TODO: we need to lock this entry until updated! */ diff --git a/source3/sam/idmap_tdb.c b/source3/sam/idmap_tdb.c index 7080ac56e6..c494cf595f 100644 --- a/source3/sam/idmap_tdb.c +++ b/source3/sam/idmap_tdb.c @@ -236,11 +236,11 @@ static NTSTATUS db_set_mapping(DOM_SID *sid, unid_t id, int id_type) kid.dsize = strlen(kidstr) + 1; if (tdb_store(idmap_tdb, ksid, kid, TDB_INSERT) == -1) { - DEBUG(0, ("idb_set_mapping: tdb_store 1 error: %s", tdb_errorstr(idmap_tdb))); + DEBUG(0, ("idb_set_mapping: tdb_store 1 error: %s\n", tdb_errorstr(idmap_tdb))); return NT_STATUS_UNSUCCESSFUL; } if (tdb_store(idmap_tdb, kid, ksid, TDB_INSERT) == -1) { - DEBUG(0, ("idb_set_mapping: tdb_store 2 error: %s", tdb_errorstr(idmap_tdb))); + DEBUG(0, ("idb_set_mapping: tdb_store 2 error: %s\n", tdb_errorstr(idmap_tdb))); return NT_STATUS_UNSUCCESSFUL; } return NT_STATUS_OK; -- cgit From 30f3314a0f70bff6c447164a60463f10731c4805 Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Thu, 17 Apr 2003 16:08:22 +0000 Subject: Edits in progress. (This used to be commit c1dea19852d8eedf590323ac464f863eb3b92c83) --- docs/docbook/projdoc/Browsing-Quickguide.sgml | 26 +++++++++++ docs/docbook/projdoc/NT4Migration.sgml | 64 ++++++++++++++++++++++++++- 2 files changed, 88 insertions(+), 2 deletions(-) diff --git a/docs/docbook/projdoc/Browsing-Quickguide.sgml b/docs/docbook/projdoc/Browsing-Quickguide.sgml index ed5b9a61af..d8df57dcb9 100644 --- a/docs/docbook/projdoc/Browsing-Quickguide.sgml +++ b/docs/docbook/projdoc/Browsing-Quickguide.sgml @@ -301,6 +301,32 @@ particularly not using it's own IP address. Specifying both will cause &nmbd; to refuse to start! + +WINS Replication + + +Samba-3 permits WINS replication through the use of the wrepld utility. +This tool is not currently capable of being used as it is still in active development. +As soon as this tool becomes moderately functional we will prepare man pages and enhance this +section of the documentation to provide usage and technical details. + + + + +Static WINS Entries + + +New to Samba-3 is a tool called winsedit that may be used to add +static WINS entries to the WINS database. This tool can be used also to modify entries +existing in the WINS database. + + + +The development of the winsedit tool was made necessary due to the migration +of the older style wins.dat file into a new tdb binary backend data store. + + + diff --git a/docs/docbook/projdoc/NT4Migration.sgml b/docs/docbook/projdoc/NT4Migration.sgml index 1f7371de36..3640c78942 100644 --- a/docs/docbook/projdoc/NT4Migration.sgml +++ b/docs/docbook/projdoc/NT4Migration.sgml @@ -15,16 +15,76 @@ Samba-3 based domain control. Planning and Getting Started -You must use at least the following ... +In the IT world there is often a saying that all problems are encountered because of +poor planning. The corrollary to this saying is that not all problems can be anticpated +and planned for. Then again, good planning will anticpate most show stopper type situations. + + + +Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control +environment would do well to develop a detailed migration plan. So here are a few pointers to +help migration get under way. Objectives -Blah blah objectives here. +The key objective for most organisations will be to make the migration from MS Windows NT4 +to Samba-3 domain control as painless as possible. One of the challenges you may experience +in your migration process may well be one of convincing management that the new environment +should remain in place. Many who have introduced open source technologies have experienced +pressure to return to a Microsoft based platform solution at the first sign of trouble. + + + +It is strongly advised that before attempting a migration to a Samba-3 controlled network +that every possible effort be made to gain all-round commitment to the change. Firstly, you +should know precisely why the change is important for the organisation. +Possible motivations to make a change include: + + + + + Improve network manageability + + + Obtain better user level functionality + + + Reduce network operating costs + + + Reduce exposure caused by Microsoft withdrawal of NT4 support + + + Avoid MS License 6 implications + + + Reduce organisation's dependency on Microsoft + + + + +It is vital that oit be well recognised that Samba-3 is NOT MS Windows NT4. Samba-3 offers +an alternative solution that is both different from MS Windows NT4 and that offers some +advantages compared with it. It should also be recognised that Samba-3 lacks many of the +features that Microsoft has promoted as core values in migration from MS Windows NT4 to +MS Windows 2000 and beyond (with or without Active Directory services). + +What are the features the Samba-3 can NOT provide? + + + + Active Directory Server + Group Policy Objects (in Active Direcrtory) + Machine Policy objects + Logon Scripts in Active Directorty + Software Application and Access Controls in Active Directory + + Steps In Migration Process -- cgit From 683bba2e8b0de88751622160a504a181b525812a Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Thu, 17 Apr 2003 17:25:24 +0000 Subject: Fix syntax errors (This used to be commit 0a55ff6738f9a8bdc480cb71c43e7372e45af216) --- docs/docbook/projdoc/PolicyMgmt.sgml | 2 +- docs/docbook/projdoc/samba-doc.sgml | 1 - 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/docbook/projdoc/PolicyMgmt.sgml b/docs/docbook/projdoc/PolicyMgmt.sgml index a6c5ffa8e4..7557d496a4 100644 --- a/docs/docbook/projdoc/PolicyMgmt.sgml +++ b/docs/docbook/projdoc/PolicyMgmt.sgml @@ -195,12 +195,12 @@ exists with NT4 style policy files. Administration of Win2K / XP Policies + Instructions Instead of using the tool called "The System Policy Editor", commonly called Poledit (from the executable name poledit.exe), GPOs are created and managed using a Microsoft Management Console (MMC) snap-in as follows: - diff --git a/docs/docbook/projdoc/samba-doc.sgml b/docs/docbook/projdoc/samba-doc.sgml index c56255d13a..328287ee04 100644 --- a/docs/docbook/projdoc/samba-doc.sgml +++ b/docs/docbook/projdoc/samba-doc.sgml @@ -106,6 +106,5 @@ for various environments. &Diagnosis; &problems; &BUGS; -&MANUALPAGES; -- cgit From 1ac5abe51637c5a1150c19cdeba128ece5fd67f1 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Thu, 17 Apr 2003 18:58:53 +0000 Subject: Update SGML layout. (This used to be commit 934dbcb1ae47811cae69c3b0677ba89e4f8eabee) --- docs/docbook/samba.dsl | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/docbook/samba.dsl b/docs/docbook/samba.dsl index 7c530ce424..5a424a551f 100644 --- a/docs/docbook/samba.dsl +++ b/docs/docbook/samba.dsl @@ -68,7 +68,11 @@ ; === Books only === (define %generate-book-titlepage% #t) (define %generate-book-toc% #t) -(define ($generate-chapter-toc$) #f) ;; never generate a chapter TOC in books +(define %generate-part-toc% #f) +(define %generate-part-titlepage% #t) +(define %generate-chapter-toc% #f) +(define %number-screen-lines% #t) +(define %generate-partintro-on-titlepage% #f) ; === Articles only === (define %generate-article-titlepage% #t) -- cgit From c85cb325aa8e18ecf4685a271bb124768d25c7eb Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Thu, 17 Apr 2003 19:12:05 +0000 Subject: Fix syntax errors (This used to be commit c7f18b38e683bf3b341504e02af448ce13fad248) --- docs/docbook/manpages/net.8.sgml | 3 ++- docs/docbook/manpages/ntlm_auth.1.sgml | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/docbook/manpages/net.8.sgml b/docs/docbook/manpages/net.8.sgml index a22797845b..8ee965e3ed 100644 --- a/docs/docbook/manpages/net.8.sgml +++ b/docs/docbook/manpages/net.8.sgml @@ -208,7 +208,7 @@ Join a domain. If the account already exists on the server, and [TYPE] is MEMBER, the machine will attempt to join automatically. (Assuming that the machine has been created in server manager) Otherwise, a password will be prompted for, and a new account may -be created. +be created. [TYPE] may be PDC, BDC or MEMBER to specify the type of server @@ -224,6 +224,7 @@ using the old style of domain joining - you need to create a trust account in server manager first. + [RPC|ADS] USER diff --git a/docs/docbook/manpages/ntlm_auth.1.sgml b/docs/docbook/manpages/ntlm_auth.1.sgml index 08a7d4aa88..42a362cd41 100644 --- a/docs/docbook/manpages/ntlm_auth.1.sgml +++ b/docs/docbook/manpages/ntlm_auth.1.sgml @@ -1,7 +1,7 @@ %globalentities; ]> - + ntlm_auth @@ -41,6 +41,7 @@ OPTIONS + --helper-protocol=PROTO -- cgit From 3706db02165c555d37f566d26ea9d0984d5c2b59 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Thu, 17 Apr 2003 19:12:40 +0000 Subject: Always use DSSSL stylesheet (This used to be commit aee2c48c729c4c9d7187556a9fabc4becb4045dd) --- docs/docbook/Makefile.in | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/docbook/Makefile.in b/docs/docbook/Makefile.in index d594764c2c..e44108401d 100644 --- a/docs/docbook/Makefile.in +++ b/docs/docbook/Makefile.in @@ -82,21 +82,21 @@ html: # Text files $(TXTDIR)/Samba-HOWTO-Collection.txt: $(PROJDOC)/samba-doc.sgml - $(DOCBOOK2TXT) -o . $< + $(DOCBOOK2TXT) -d samba.dsl -o . $< mv ./samba-doc.txt $@ $(TXTDIR)/Samba-Developers-Guide.txt: $(DEVDOC)/dev-doc.sgml - $(DOCBOOK2TXT) -o . $< + $(DOCBOOK2TXT) -d samba.dsl -o . $< mv ./dev-doc.txt $@ # PostScript $(PSDIR)/Samba-HOWTO-Collection.ps: $(PROJDOC)/samba-doc.sgml - $(DOCBOOK2PS) -o . $< + $(DOCBOOK2PS) -d samba.dsl -o . $< mv ./samba-doc.ps $@ $(PSDIR)/Samba-Developers-Guide.ps: $(DEVDOC)/dev-doc.sgml - $(DOCBOOK2PS) -o . $< + $(DOCBOOK2PS) -d samba.dsl -o . $< mv ./dev-doc.ps $@ # Adobe PDF files @@ -110,19 +110,19 @@ $(PDFDIR)/Samba-Developers-Guide.pdf: $(HTMLDIR)/Samba-Developers-Guide.html # Single large HTML files $(HTMLDIR)/Samba-HOWTO-Collection.html: $(PROJDOC)/samba-doc.sgml - $(DOCBOOK2HTML) -u -o . $< + $(DOCBOOK2HTML) -d samba.dsl -u -o . $< mv ./samba-doc.html $@ $(HTMLDIR)/Samba-Developers-Guide.html: $(DEVDOC)/dev-doc.sgml - $(DOCBOOK2HTML) -u -o . $< + $(DOCBOOK2HTML) -d samba.dsl -u -o . $< mv ./dev-doc.html $@ $(HTMLDIR)/%.html: $(MANPROJDOC)/%.sgml - $(DOCBOOK2HTML) -u -o $(HTMLDIR) $< + $(DOCBOOK2HTML) -d samba.dsl -u -o $(HTMLDIR) $< $(MANDIR)/%: $(MANPROJDOC)/%.sgml - $(DOCBOOK2MAN) -o $(MANDIR) $< + $(DOCBOOK2MAN) -d samba.dsl -o $(MANDIR) $< $(PERL) scripts/strip-links.pl < $@ > $@.temp mv $@.temp $@ -- cgit From cdd3fa410a6b9f0ddc778149175f3ba7e8a7095d Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Thu, 17 Apr 2003 19:15:22 +0000 Subject: Regenerate docs (This used to be commit 13a4cd540a1c193e77d973b9dac5bc2d9e7a5353) --- docs/Samba-Developers-Guide.pdf | 4 +- docs/Samba-HOWTO-Collection.pdf | 12338 ++++++----- docs/faq/faq-clientapp.html | 24 + docs/faq/faq-config.html | 19 + docs/faq/faq-errors.html | 44 + docs/faq/faq-features.html | 63 + docs/faq/faq-general.html | 34 + docs/faq/faq-install.html | 59 + docs/htmldocs/Samba-HOWTO-Collection.html | 31094 ++++++++++++++-------------- docs/htmldocs/ads.html | 78 +- docs/htmldocs/appendixes.html | 442 +- docs/htmldocs/browsing-quick.html | 131 +- docs/htmldocs/bugreport.html | 92 +- docs/htmldocs/compiling.html | 198 +- docs/htmldocs/diagnosis.html | 81 +- docs/htmldocs/findsmb.1.html | 24 +- docs/htmldocs/groupmapping.html | 2 +- docs/htmldocs/improved-browsing.html | 112 +- docs/htmldocs/install.html | 151 +- docs/htmldocs/integrate-ms-networks.html | 130 +- docs/htmldocs/introduction.html | 282 +- docs/htmldocs/msdfs.html | 10 +- docs/htmldocs/net.8.html | 1576 +- docs/htmldocs/optional.html | 949 +- docs/htmldocs/other-clients.html | 136 +- docs/htmldocs/pam.html | 38 +- docs/htmldocs/passdb.html | 345 +- docs/htmldocs/pdbedit.8.html | 44 +- docs/htmldocs/portability.html | 63 +- docs/htmldocs/printing.html | 221 +- docs/htmldocs/samba-bdc.html | 100 +- docs/htmldocs/samba-howto-collection.html | 836 +- docs/htmldocs/samba-pdc.html | 867 +- docs/htmldocs/samba.7.html | 352 +- docs/htmldocs/securing-samba.html | 67 +- docs/htmldocs/securitylevels.html | 38 +- docs/htmldocs/smb.conf.5.html | 24 +- docs/htmldocs/speed.html | 121 +- docs/htmldocs/type.html | 299 +- docs/htmldocs/unix-permissions.html | 99 +- docs/htmldocs/vfs.html | 100 +- docs/htmldocs/winbind.html | 258 +- docs/manpages/findsmb.1 | 2 +- docs/manpages/lmhosts.5 | 2 +- docs/manpages/net.8 | 462 +- docs/manpages/nmbd.8 | 2 +- docs/manpages/nmblookup.1 | 2 +- docs/manpages/pdbedit.8 | 2 +- docs/manpages/rpcclient.1 | 2 +- docs/manpages/samba.7 | 85 +- 50 files changed, 26067 insertions(+), 26437 deletions(-) diff --git a/docs/Samba-Developers-Guide.pdf b/docs/Samba-Developers-Guide.pdf index 0b0851c11c..bdf1740d06 100644 --- a/docs/Samba-Developers-Guide.pdf +++ b/docs/Samba-Developers-Guide.pdf @@ -1,6 +1,6 @@ %PDF-1.3 % -1 0 obj<>endobj +1 0 obj<>endobj 2 0 obj<>endobj 3 0 obj<>endobj 4 0 obj<>endobj @@ -2728,7 +2728,7 @@ xref 0000186776 00000 n 0000186871 00000 n trailer -<]>> +<]>> startxref 187413 %%EOF diff --git a/docs/Samba-HOWTO-Collection.pdf b/docs/Samba-HOWTO-Collection.pdf index 9fb7bf58a6..d06d23377a 100644 --- a/docs/Samba-HOWTO-Collection.pdf +++ b/docs/Samba-HOWTO-Collection.pdf @@ -1,6 +1,6 @@ %PDF-1.3 % -1 0 obj<>endobj +1 0 obj<>endobj 2 0 obj<>endobj 3 0 obj<>endobj 4 0 obj<>endobj @@ -20,50 +20,49 @@ endobj 16 0 obj<]/Interpolate true/Filter/FlateDecode/Width 24/Height 24/BitsPerComponent 8/Length 223 >>stream xUQ0 58@4wo%wR+8C+N"]ׂ*W ,D1|Ši"%~0)܁1lN!31T4HԆ<<~Z>yn.H>LKb؎џ'4Y}-?f&tA{27L}On4KI" PBhïG]z$>.mcoendstream endobj -17 0 obj<>endobj -18 0 obj<>endobj -19 0 obj<>endobj -20 0 obj<>endobj -21 0 obj<>endobj -22 0 obj<>endobj -23 0 obj<>endobj -24 0 obj<>endobj -25 0 obj<>endobj -26 0 obj<>endobj -27 0 obj<>endobj -28 0 obj<>endobj -29 0 obj<>endobj -30 0 obj<>endobj -31 0 obj<>endobj -32 0 obj<>endobj -33 0 obj<>endobj -34 0 obj<>endobj -35 0 obj<>endobj -36 0 obj<>endobj -37 0 obj<>endobj -38 0 obj<>endobj -39 0 obj<>endobj -40 0 obj<>endobj -41 0 obj<>endobj -42 0 obj<>endobj -43 0 obj<>endobj -44 0 obj<>endobj -45 0 obj<>endobj -46 0 obj<>endobj -47 0 obj<>endobj -48 0 obj<>endobj -49 0 obj<>endobj -50 0 obj<>endobj -51 0 obj<>endobj -52 0 obj<>endobj -53 0 obj<>endobj -54 0 obj<>endobj -55 0 obj<>endobj -56 0 obj<>endobj -57 0 obj<>endobj -58 0 obj<>endobj -59 0 obj<>endobj -60 0 obj[17 0 R +17 0 obj<>endobj +18 0 obj<>endobj +19 0 obj<>endobj +20 0 obj<>endobj +21 0 obj<>endobj +22 0 obj<>endobj +23 0 obj<>endobj +24 0 obj<>endobj +25 0 obj<>endobj +26 0 obj<>endobj +27 0 obj<>endobj +28 0 obj<>endobj +29 0 obj<>endobj +30 0 obj<>endobj +31 0 obj<>endobj +32 0 obj<>endobj +33 0 obj<>endobj +34 0 obj<>endobj +35 0 obj<>endobj +36 0 obj<>endobj +37 0 obj<>endobj +38 0 obj<>endobj +39 0 obj<>endobj +40 0 obj<>endobj +41 0 obj<>endobj +42 0 obj<>endobj +43 0 obj<>endobj +44 0 obj<>endobj +45 0 obj<>endobj +46 0 obj<>endobj +47 0 obj<>endobj +48 0 obj<>endobj +49 0 obj<>endobj +50 0 obj<>endobj +51 0 obj<>endobj +52 0 obj<>endobj +53 0 obj<>endobj +54 0 obj<>endobj +55 0 obj<>endobj +56 0 obj<>endobj +57 0 obj<>endobj +58 0 obj<>endobj +59 0 obj[17 0 R 18 0 R 19 0 R 20 0 R @@ -104,51 +103,52 @@ endobj 55 0 R 56 0 R 57 0 R -58 0 R -59 0 R]endobj -61 0 obj<>endobj -62 0 obj<>endobj -63 0 obj<>endobj -64 0 obj<>endobj -65 0 obj<>endobj -66 0 obj<>endobj -67 0 obj<>endobj -68 0 obj<>endobj -69 0 obj<>endobj -70 0 obj<>endobj -71 0 obj<>endobj -72 0 obj<>endobj -73 0 obj<>endobj -74 0 obj<>endobj -75 0 obj<>endobj -76 0 obj<>endobj -77 0 obj<>endobj -78 0 obj<>endobj -79 0 obj<>endobj -80 0 obj<>endobj -81 0 obj<>endobj -82 0 obj<>endobj -83 0 obj<>endobj -84 0 obj<>endobj -85 0 obj<>endobj -86 0 obj<>endobj -87 0 obj<>endobj -88 0 obj<>endobj -89 0 obj<>endobj -90 0 obj<>endobj -91 0 obj<>endobj -92 0 obj<>endobj -93 0 obj<>endobj -94 0 obj<>endobj -95 0 obj<>endobj -96 0 obj<>endobj -97 0 obj<>endobj -98 0 obj<>endobj -99 0 obj<>endobj -100 0 obj<>endobj -101 0 obj<>endobj -102 0 obj<>endobj -103 0 obj[61 0 R +58 0 R]endobj +60 0 obj<>endobj +61 0 obj<>endobj +62 0 obj<>endobj +63 0 obj<>endobj +64 0 obj<>endobj +65 0 obj<>endobj +66 0 obj<>endobj +67 0 obj<>endobj +68 0 obj<>endobj +69 0 obj<>endobj +70 0 obj<>endobj +71 0 obj<>endobj +72 0 obj<>endobj +73 0 obj<>endobj +74 0 obj<>endobj +75 0 obj<>endobj +76 0 obj<>endobj +77 0 obj<>endobj +78 0 obj<>endobj +79 0 obj<>endobj +80 0 obj<>endobj +81 0 obj<>endobj +82 0 obj<>endobj +83 0 obj<>endobj +84 0 obj<>endobj +85 0 obj<>endobj +86 0 obj<>endobj +87 0 obj<>endobj +88 0 obj<>endobj +89 0 obj<>endobj +90 0 obj<>endobj +91 0 obj<>endobj +92 0 obj<>endobj +93 0 obj<>endobj +94 0 obj<>endobj +95 0 obj<>endobj +96 0 obj<>endobj +97 0 obj<>endobj +98 0 obj<>endobj +99 0 obj<>endobj +100 0 obj<>endobj +101 0 obj<>endobj +102 0 obj<>endobj +103 0 obj[60 0 R +61 0 R 62 0 R 63 0 R 64 0 R @@ -190,48 +190,49 @@ endobj 100 0 R 101 0 R 102 0 R]endobj -104 0 obj<>endobj -105 0 obj<>endobj -106 0 obj<>endobj -107 0 obj<>endobj -108 0 obj<>endobj -109 0 obj<>endobj -110 0 obj<>endobj -111 0 obj<>endobj -112 0 obj<>endobj -113 0 obj<>endobj -114 0 obj<>endobj -115 0 obj<>endobj -116 0 obj<>endobj -117 0 obj<>endobj -118 0 obj<>endobj -119 0 obj<>endobj -120 0 obj<>endobj -121 0 obj<>endobj -122 0 obj<>endobj -123 0 obj<>endobj -124 0 obj<>endobj -125 0 obj<>endobj -126 0 obj<>endobj -127 0 obj<>endobj -128 0 obj<>endobj -129 0 obj<>endobj -130 0 obj<>endobj -131 0 obj<>endobj -132 0 obj<>endobj -133 0 obj<>endobj -134 0 obj<>endobj -135 0 obj<>endobj -136 0 obj<>endobj -137 0 obj<>endobj -138 0 obj<>endobj -139 0 obj<>endobj -140 0 obj<>endobj -141 0 obj<>endobj -142 0 obj<>endobj -143 0 obj<>endobj -144 0 obj<>endobj -145 0 obj[104 0 R +104 0 obj<>endobj +105 0 obj<>endobj +106 0 obj<>endobj +107 0 obj<>endobj +108 0 obj<>endobj +109 0 obj<>endobj +110 0 obj<>endobj +111 0 obj<>endobj +112 0 obj<>endobj +113 0 obj<>endobj +114 0 obj<>endobj +115 0 obj<>endobj +116 0 obj<>endobj +117 0 obj<>endobj +118 0 obj<>endobj +119 0 obj<>endobj +120 0 obj<>endobj +121 0 obj<>endobj +122 0 obj<>endobj +123 0 obj<>endobj +124 0 obj<>endobj +125 0 obj<>endobj +126 0 obj<>endobj +127 0 obj<>endobj +128 0 obj<>endobj +129 0 obj<>endobj +130 0 obj<>endobj +131 0 obj<>endobj +132 0 obj<>endobj +133 0 obj<>endobj +134 0 obj<>endobj +135 0 obj<>endobj +136 0 obj<>endobj +137 0 obj<>endobj +138 0 obj<>endobj +139 0 obj<>endobj +140 0 obj<>endobj +141 0 obj<>endobj +142 0 obj<>endobj +143 0 obj<>endobj +144 0 obj<>endobj +145 0 obj<>endobj +146 0 obj[104 0 R 105 0 R 106 0 R 107 0 R @@ -271,53 +272,51 @@ endobj 141 0 R 142 0 R 143 0 R -144 0 R]endobj -146 0 obj<>endobj -147 0 obj<>endobj -148 0 obj<>endobj -149 0 obj<>endobj -150 0 obj<>endobj -151 0 obj<>endobj -152 0 obj<>endobj -153 0 obj<>endobj -154 0 obj<>endobj -155 0 obj<>endobj -156 0 obj<>endobj -157 0 obj<>endobj -158 0 obj<>endobj -159 0 obj<>endobj -160 0 obj<>endobj -161 0 obj<>endobj -162 0 obj<>endobj -163 0 obj<>endobj -164 0 obj<>endobj -165 0 obj<>endobj -166 0 obj<>endobj -167 0 obj<>endobj -168 0 obj<>endobj -169 0 obj<>endobj -170 0 obj<>endobj -171 0 obj<>endobj -172 0 obj<>endobj -173 0 obj<>endobj -174 0 obj<>endobj -175 0 obj<>endobj -176 0 obj<>endobj -177 0 obj<>endobj -178 0 obj<>endobj -179 0 obj<>endobj -180 0 obj<>endobj -181 0 obj<>endobj -182 0 obj<>endobj -183 0 obj<>endobj -184 0 obj<>endobj -185 0 obj<>endobj -186 0 obj<>endobj -187 0 obj<>endobj -188 0 obj<>endobj -189 0 obj<>endobj -190 0 obj[146 0 R -147 0 R +144 0 R +145 0 R]endobj +147 0 obj<>endobj +148 0 obj<>endobj +149 0 obj<>endobj +150 0 obj<>endobj +151 0 obj<>endobj +152 0 obj<>endobj +153 0 obj<>endobj +154 0 obj<>endobj +155 0 obj<>endobj +156 0 obj<>endobj +157 0 obj<>endobj +158 0 obj<>endobj +159 0 obj<>endobj +160 0 obj<>endobj +161 0 obj<>endobj +162 0 obj<>endobj +163 0 obj<>endobj +164 0 obj<>endobj +165 0 obj<>endobj +166 0 obj<>endobj +167 0 obj<>endobj +168 0 obj<>endobj +169 0 obj<>endobj +170 0 obj<>endobj +171 0 obj<>endobj +172 0 obj<>endobj +173 0 obj<>endobj +174 0 obj<>endobj +175 0 obj<>endobj +176 0 obj<>endobj +177 0 obj<>endobj +178 0 obj<>endobj +179 0 obj<>endobj +180 0 obj<>endobj +181 0 obj<>endobj +182 0 obj<>endobj +183 0 obj<>endobj +184 0 obj<>endobj +185 0 obj<>endobj +186 0 obj<>endobj +187 0 obj<>endobj +188 0 obj<>endobj +189 0 obj[147 0 R 148 0 R 149 0 R 150 0 R @@ -358,52 +357,53 @@ endobj 185 0 R 186 0 R 187 0 R -188 0 R -189 0 R]endobj -191 0 obj<>endobj -192 0 obj<>endobj -193 0 obj<>endobj -194 0 obj<>endobj -195 0 obj<>endobj -196 0 obj<>endobj -197 0 obj<>endobj -198 0 obj<>endobj -199 0 obj<>endobj -200 0 obj<>endobj -201 0 obj<>endobj -202 0 obj<>endobj -203 0 obj<>endobj -204 0 obj<>endobj -205 0 obj<>endobj -206 0 obj<>endobj -207 0 obj<>endobj -208 0 obj<>endobj -209 0 obj<>endobj -210 0 obj<>endobj -211 0 obj<>endobj -212 0 obj<>endobj -213 0 obj<>endobj -214 0 obj<>endobj -215 0 obj<>endobj -216 0 obj<>endobj -217 0 obj<>endobj -218 0 obj<>endobj -219 0 obj<>endobj -220 0 obj<>endobj -221 0 obj<>endobj -222 0 obj<>endobj -223 0 obj<>endobj -224 0 obj<>endobj -225 0 obj<>endobj -226 0 obj<>endobj -227 0 obj<>endobj -228 0 obj<>endobj -229 0 obj<>endobj -230 0 obj<>endobj -231 0 obj<>endobj -232 0 obj<>endobj -233 0 obj<>endobj -234 0 obj[191 0 R +188 0 R]endobj +190 0 obj<>endobj +191 0 obj<>endobj +192 0 obj<>endobj +193 0 obj<>endobj +194 0 obj<>endobj +195 0 obj<>endobj +196 0 obj<>endobj +197 0 obj<>endobj +198 0 obj<>endobj +199 0 obj<>endobj +200 0 obj<>endobj +201 0 obj<>endobj +202 0 obj<>endobj +203 0 obj<>endobj +204 0 obj<>endobj +205 0 obj<>endobj +206 0 obj<>endobj +207 0 obj<>endobj +208 0 obj<>endobj +209 0 obj<>endobj +210 0 obj<>endobj +211 0 obj<>endobj +212 0 obj<>endobj +213 0 obj<>endobj +214 0 obj<>endobj +215 0 obj<>endobj +216 0 obj<>endobj +217 0 obj<>endobj +218 0 obj<>endobj +219 0 obj<>endobj +220 0 obj<>endobj +221 0 obj<>endobj +222 0 obj<>endobj +223 0 obj<>endobj +224 0 obj<>endobj +225 0 obj<>endobj +226 0 obj<>endobj +227 0 obj<>endobj +228 0 obj<>endobj +229 0 obj<>endobj +230 0 obj<>endobj +231 0 obj<>endobj +232 0 obj<>endobj +233 0 obj<>endobj +234 0 obj[190 0 R +191 0 R 192 0 R 193 0 R 194 0 R @@ -446,49 +446,49 @@ endobj 231 0 R 232 0 R 233 0 R]endobj -235 0 obj<>endobj -236 0 obj<>endobj -237 0 obj<>endobj -238 0 obj<>endobj -239 0 obj<>endobj -240 0 obj<>endobj -241 0 obj<>endobj -242 0 obj<>endobj -243 0 obj<>endobj -244 0 obj<>endobj -245 0 obj<>endobj -246 0 obj<>endobj -247 0 obj<>endobj -248 0 obj<>endobj -249 0 obj<>endobj -250 0 obj<>endobj -251 0 obj<>endobj -252 0 obj<>endobj -253 0 obj<>endobj -254 0 obj<>endobj -255 0 obj<>endobj -256 0 obj<>endobj -257 0 obj<>endobj -258 0 obj<>endobj -259 0 obj<>endobj -260 0 obj<>endobj -261 0 obj<>endobj -262 0 obj<>endobj -263 0 obj<>endobj -264 0 obj<>endobj -265 0 obj<>endobj -266 0 obj<>endobj -267 0 obj<>endobj -268 0 obj<>endobj -269 0 obj<>endobj -270 0 obj<>endobj -271 0 obj<>endobj -272 0 obj<>endobj -273 0 obj<>endobj -274 0 obj<>endobj -275 0 obj<>endobj -276 0 obj<>endobj -277 0 obj<>endobj +235 0 obj<>endobj +236 0 obj<>endobj +237 0 obj<>endobj +238 0 obj<>endobj +239 0 obj<>endobj +240 0 obj<>endobj +241 0 obj<>endobj +242 0 obj<>endobj +243 0 obj<>endobj +244 0 obj<>endobj +245 0 obj<>endobj +246 0 obj<>endobj +247 0 obj<>endobj +248 0 obj<>endobj +249 0 obj<>endobj +250 0 obj<>endobj +251 0 obj<>endobj +252 0 obj<>endobj +253 0 obj<>endobj +254 0 obj<>endobj +255 0 obj<>endobj +256 0 obj<>endobj +257 0 obj<>endobj +258 0 obj<>endobj +259 0 obj<>endobj +260 0 obj<>endobj +261 0 obj<>endobj +262 0 obj<>endobj +263 0 obj<>endobj +264 0 obj<>endobj +265 0 obj<>endobj +266 0 obj<>endobj +267 0 obj<>endobj +268 0 obj<>endobj +269 0 obj<>endobj +270 0 obj<>endobj +271 0 obj<>endobj +272 0 obj<>endobj +273 0 obj<>endobj +274 0 obj<>endobj +275 0 obj<>endobj +276 0 obj<>endobj +277 0 obj<>endobj 278 0 obj[235 0 R 236 0 R 237 0 R @@ -532,50 +532,49 @@ endobj 275 0 R 276 0 R 277 0 R]endobj -279 0 obj<>endobj -280 0 obj<>endobj -281 0 obj<>endobj -282 0 obj<>endobj -283 0 obj<>endobj -284 0 obj<>endobj -285 0 obj<>endobj -286 0 obj<>endobj -287 0 obj<>endobj -288 0 obj<>endobj -289 0 obj<>endobj -290 0 obj<>endobj -291 0 obj<>endobj -292 0 obj<>endobj -293 0 obj<>endobj -294 0 obj<>endobj -295 0 obj<>endobj -296 0 obj<>endobj -297 0 obj<>endobj -298 0 obj<>endobj -299 0 obj<>endobj -300 0 obj<>endobj -301 0 obj<>endobj -302 0 obj<>endobj -303 0 obj<>endobj -304 0 obj<>endobj -305 0 obj<>endobj -306 0 obj<>endobj -307 0 obj<>endobj -308 0 obj<>endobj -309 0 obj<>endobj -310 0 obj<>endobj -311 0 obj<>endobj -312 0 obj<>endobj -313 0 obj<>endobj -314 0 obj<>endobj -315 0 obj<>endobj -316 0 obj<>endobj -317 0 obj<>endobj -318 0 obj<>endobj -319 0 obj<>endobj -320 0 obj<>endobj -321 0 obj<>endobj -322 0 obj[279 0 R +279 0 obj<>endobj +280 0 obj<>endobj +281 0 obj<>endobj +282 0 obj<>endobj +283 0 obj<>endobj +284 0 obj<>endobj +285 0 obj<>endobj +286 0 obj<>endobj +287 0 obj<>endobj +288 0 obj<>endobj +289 0 obj<>endobj +290 0 obj<>endobj +291 0 obj<>endobj +292 0 obj<>endobj +293 0 obj<>endobj +294 0 obj<>endobj +295 0 obj<>endobj +296 0 obj<>endobj +297 0 obj<>endobj +298 0 obj<>endobj +299 0 obj<>endobj +300 0 obj<>endobj +301 0 obj<>endobj +302 0 obj<>endobj +303 0 obj<>endobj +304 0 obj<>endobj +305 0 obj<>endobj +306 0 obj<>endobj +307 0 obj<>endobj +308 0 obj<>endobj +309 0 obj<>endobj +310 0 obj<>endobj +311 0 obj<>endobj +312 0 obj<>endobj +313 0 obj<>endobj +314 0 obj<>endobj +315 0 obj<>endobj +316 0 obj<>endobj +317 0 obj<>endobj +318 0 obj<>endobj +319 0 obj<>endobj +320 0 obj<>endobj +321 0 obj[279 0 R 280 0 R 281 0 R 282 0 R @@ -616,38 +615,53 @@ endobj 317 0 R 318 0 R 319 0 R -320 0 R -321 0 R]endobj -323 0 obj<>endobj -324 0 obj<>endobj -325 0 obj<>endobj -326 0 obj<>endobj -327 0 obj<>endobj -328 0 obj<>endobj -329 0 obj<>endobj -330 0 obj<>endobj -331 0 obj<>endobj -332 0 obj<>endobj -333 0 obj<>endobj -334 0 obj<>endobj -335 0 obj<>endobj -336 0 obj<>endobj -337 0 obj<>endobj -338 0 obj<>endobj -339 0 obj<>endobj -340 0 obj<>endobj -341 0 obj<>endobj -342 0 obj<>endobj -343 0 obj<>endobj -344 0 obj<>endobj -345 0 obj<>endobj -346 0 obj<>endobj -347 0 obj<>endobj -348 0 obj<>endobj -349 0 obj<>endobj -350 0 obj<>endobj -351 0 obj<>endobj -352 0 obj[323 0 R +320 0 R]endobj +322 0 obj<>endobj +323 0 obj<>endobj +324 0 obj<>endobj +325 0 obj<>endobj +326 0 obj<>endobj +327 0 obj<>endobj +328 0 obj<>endobj +329 0 obj<>endobj +330 0 obj<>endobj +331 0 obj<>endobj +332 0 obj<>endobj +333 0 obj<>endobj +334 0 obj<>endobj +335 0 obj<>endobj +336 0 obj<>endobj +337 0 obj<>endobj +338 0 obj<>endobj +339 0 obj<>endobj +340 0 obj<>endobj +341 0 obj<>endobj +342 0 obj<>endobj +343 0 obj<>endobj +344 0 obj<>endobj +345 0 obj<>endobj +346 0 obj<>endobj +347 0 obj<>endobj +348 0 obj<>endobj +349 0 obj<>endobj +350 0 obj<>endobj +351 0 obj<>endobj +352 0 obj<>endobj +353 0 obj<>endobj +354 0 obj<>endobj +355 0 obj<>endobj +356 0 obj<>endobj +357 0 obj<>endobj +358 0 obj<>endobj +359 0 obj<>endobj +360 0 obj<>endobj +361 0 obj<>endobj +362 0 obj<>endobj +363 0 obj<>endobj +364 0 obj<>endobj +365 0 obj<>endobj +366 0 obj[322 0 R +323 0 R 324 0 R 325 0 R 326 0 R @@ -675,49 +689,35 @@ endobj 348 0 R 349 0 R 350 0 R -351 0 R]endobj -353 0 obj<>endobj -354 0 obj<>endobj -355 0 obj<>endobj -356 0 obj<>endobj -357 0 obj<>endobj -358 0 obj<>endobj -359 0 obj<>endobj -360 0 obj<>endobj -361 0 obj<>endobj -362 0 obj<>endobj -363 0 obj<>endobj -364 0 obj<>endobj -365 0 obj<>endobj -366 0 obj<>endobj -367 0 obj<>endobj -368 0 obj<>endobj -369 0 obj<>endobj -370 0 obj<>endobj -371 0 obj<>endobj -372 0 obj<>endobj -373 0 obj<>endobj -374 0 obj<>endobj -375 0 obj<>endobj -376 0 obj<>endobj -377 0 obj<>endobj -378 0 obj<>endobj -379 0 obj<>endobj -380 0 obj<>endobj -381 0 obj<>endobj -382 0 obj<>endobj -383 0 obj<>endobj -384 0 obj<>endobj -385 0 obj[354 0 R +351 0 R +352 0 R +353 0 R +354 0 R +355 0 R 356 0 R +357 0 R 358 0 R +359 0 R 360 0 R +361 0 R 362 0 R 363 0 R 364 0 R -365 0 R -366 0 R -367 0 R +365 0 R]endobj +367 0 obj<>endobj +368 0 obj<>endobj +369 0 obj<>endobj +370 0 obj<>endobj +371 0 obj<>endobj +372 0 obj<>endobj +373 0 obj<>endobj +374 0 obj<>endobj +375 0 obj<>endobj +376 0 obj<>endobj +377 0 obj<>endobj +378 0 obj<>endobj +379 0 obj<>endobj +380 0 obj[367 0 R 368 0 R 369 0 R 370 0 R @@ -729,69 +729,43 @@ endobj 376 0 R 377 0 R 378 0 R -379 0 R -380 0 R -381 0 R -382 0 R -383 0 R -384 0 R]endobj -386 0 obj<>endobj -387 0 obj<>endobj -388 0 obj<>endobj -389 0 obj<>endobj -390 0 obj<>endobj -391 0 obj<>endobj -392 0 obj<>endobj -393 0 obj<>endobj -394 0 obj<>endobj -395 0 obj<>endobj -396 0 obj<>endobj -397 0 obj<>endobj -398 0 obj<>endobj -399 0 obj<>endobj -400 0 obj<>endobj -401 0 obj<>endobj -402 0 obj<>endobj -403 0 obj<>endobj -404 0 obj<>endobj -405 0 obj<>endobj -406 0 obj<>endobj -407 0 obj<>endobj -408 0 obj<>endobj -409 0 obj<>endobj -410 0 obj<>endobj -411 0 obj<>endobj -412 0 obj<>endobj -413 0 obj<>endobj -414 0 obj<>endobj -415 0 obj<>endobj -416 0 obj<>endobj -417 0 obj<>endobj -418 0 obj<>endobj -419 0 obj<>endobj -420 0 obj<>endobj -421 0 obj<>endobj -422 0 obj<>endobj -423 0 obj<>endobj -424 0 obj<>endobj -425 0 obj<>endobj -426 0 obj<>endobj -427 0 obj<>endobj -428 0 obj<>endobj -429 0 obj<>endobj -430 0 obj<>endobj -431 0 obj<>endobj -432 0 obj<>endobj -433 0 obj<>endobj -434 0 obj<>endobj -435 0 obj<>endobj -436 0 obj<>endobj -437 0 obj<>endobj -438 0 obj<>endobj -439 0 obj[386 0 R -387 0 R +379 0 R]endobj +381 0 obj<>endobj +382 0 obj<>endobj +383 0 obj<>endobj +384 0 obj<>endobj +385 0 obj<>endobj +386 0 obj<>endobj +387 0 obj<>endobj +388 0 obj<>endobj +389 0 obj<>endobj +390 0 obj<>endobj +391 0 obj<>endobj +392 0 obj<>endobj +393 0 obj<>endobj +394 0 obj<>endobj +395 0 obj<>endobj +396 0 obj<>endobj +397 0 obj<>endobj +398 0 obj<>endobj +399 0 obj<>endobj +400 0 obj<>endobj +401 0 obj<>endobj +402 0 obj<>endobj +403 0 obj<>endobj +404 0 obj<>endobj +405 0 obj<>endobj +406 0 obj<>endobj +407 0 obj<>endobj +408 0 obj<>endobj +409 0 obj<>endobj +410 0 obj<>endobj +411 0 obj<>endobj +412 0 obj<>endobj +413 0 obj[382 0 R +384 0 R +386 0 R 388 0 R -389 0 R 390 0 R 391 0 R 392 0 R @@ -814,9 +788,61 @@ endobj 409 0 R 410 0 R 411 0 R -412 0 R -413 0 R -414 0 R +412 0 R]endobj +414 0 obj<>endobj +415 0 obj<>endobj +416 0 obj<>endobj +417 0 obj<>endobj +418 0 obj<>endobj +419 0 obj<>endobj +420 0 obj<>endobj +421 0 obj<>endobj +422 0 obj<>endobj +423 0 obj<>endobj +424 0 obj<>endobj +425 0 obj<>endobj +426 0 obj<>endobj +427 0 obj<>endobj +428 0 obj<>endobj +429 0 obj<>endobj +430 0 obj<>endobj +431 0 obj<>endobj +432 0 obj<>endobj +433 0 obj<>endobj +434 0 obj<>endobj +435 0 obj<>endobj +436 0 obj<>endobj +437 0 obj<>endobj +438 0 obj<>endobj +439 0 obj<>endobj +440 0 obj<>endobj +441 0 obj<>endobj +442 0 obj<>endobj +443 0 obj<>endobj +444 0 obj<>endobj +445 0 obj<>endobj +446 0 obj<>endobj +447 0 obj<>endobj +448 0 obj<>endobj +449 0 obj<>endobj +450 0 obj<>endobj +451 0 obj<>endobj +452 0 obj<>endobj +453 0 obj<>endobj +454 0 obj<>endobj +455 0 obj<>endobj +456 0 obj<>endobj +457 0 obj<>endobj +458 0 obj<>endobj +459 0 obj<>endobj +460 0 obj<>endobj +461 0 obj<>endobj +462 0 obj<>endobj +463 0 obj<>endobj +464 0 obj<>endobj +465 0 obj<>endobj +466 0 obj<>endobj +467 0 obj[414 0 R 415 0 R 416 0 R 417 0 R @@ -840,60 +866,9 @@ endobj 435 0 R 436 0 R 437 0 R -438 0 R]endobj -440 0 obj<>endobj -441 0 obj<>endobj -442 0 obj<>endobj -443 0 obj<>endobj -444 0 obj<>endobj -445 0 obj<>endobj -446 0 obj<>endobj -447 0 obj<>endobj -448 0 obj<>endobj -449 0 obj<>endobj -450 0 obj<>endobj -451 0 obj<>endobj -452 0 obj<>endobj -453 0 obj<>endobj -454 0 obj<>endobj -455 0 obj<>endobj -456 0 obj<>endobj -457 0 obj<>endobj -458 0 obj<>endobj -459 0 obj<>endobj -460 0 obj<>endobj -461 0 obj<>endobj -462 0 obj<>endobj -463 0 obj<>endobj -464 0 obj<>endobj -465 0 obj<>endobj -466 0 obj<>endobj -467 0 obj<>endobj -468 0 obj<>endobj -469 0 obj<>endobj -470 0 obj<>endobj -471 0 obj<>endobj -472 0 obj<>endobj -473 0 obj<>endobj -474 0 obj<>endobj -475 0 obj<>endobj -476 0 obj<>endobj -477 0 obj<>endobj -478 0 obj<>endobj -479 0 obj<>endobj -480 0 obj<>endobj -481 0 obj<>endobj -482 0 obj<>endobj -483 0 obj<>endobj -484 0 obj<>endobj -485 0 obj<>endobj -486 0 obj<>endobj -487 0 obj<>endobj -488 0 obj<>endobj -489 0 obj<>endobj -490 0 obj<>endobj -491 0 obj<>endobj -492 0 obj[440 0 R +438 0 R +439 0 R +440 0 R 441 0 R 442 0 R 443 0 R @@ -919,9 +894,60 @@ endobj 463 0 R 464 0 R 465 0 R -466 0 R -467 0 R -468 0 R +466 0 R]endobj +468 0 obj<>endobj +469 0 obj<>endobj +470 0 obj<>endobj +471 0 obj<>endobj +472 0 obj<>endobj +473 0 obj<>endobj +474 0 obj<>endobj +475 0 obj<>endobj +476 0 obj<>endobj +477 0 obj<>endobj +478 0 obj<>endobj +479 0 obj<>endobj +480 0 obj<>endobj +481 0 obj<>endobj +482 0 obj<>endobj +483 0 obj<>endobj +484 0 obj<>endobj +485 0 obj<>endobj +486 0 obj<>endobj +487 0 obj<>endobj +488 0 obj<>endobj +489 0 obj<>endobj +490 0 obj<>endobj +491 0 obj<>endobj +492 0 obj<>endobj +493 0 obj<>endobj +494 0 obj<>endobj +495 0 obj<>endobj +496 0 obj<>endobj +497 0 obj<>endobj +498 0 obj<>endobj +499 0 obj<>endobj +500 0 obj<>endobj +501 0 obj<>endobj +502 0 obj<>endobj +503 0 obj<>endobj +504 0 obj<>endobj +505 0 obj<>endobj +506 0 obj<>endobj +507 0 obj<>endobj +508 0 obj<>endobj +509 0 obj<>endobj +510 0 obj<>endobj +511 0 obj<>endobj +512 0 obj<>endobj +513 0 obj<>endobj +514 0 obj<>endobj +515 0 obj<>endobj +516 0 obj<>endobj +517 0 obj<>endobj +518 0 obj<>endobj +519 0 obj<>endobj +520 0 obj[468 0 R 469 0 R 470 0 R 471 0 R @@ -944,59 +970,9 @@ endobj 488 0 R 489 0 R 490 0 R -491 0 R]endobj -493 0 obj<>endobj -494 0 obj<>endobj -495 0 obj<>endobj -496 0 obj<>endobj -497 0 obj<>endobj -498 0 obj<>endobj -499 0 obj<>endobj -500 0 obj<>endobj -501 0 obj<>endobj -502 0 obj<>endobj -503 0 obj<>endobj -504 0 obj<>endobj -505 0 obj<>endobj -506 0 obj<>endobj -507 0 obj<>endobj -508 0 obj<>endobj -509 0 obj<>endobj -510 0 obj<>endobj -511 0 obj<>endobj -512 0 obj<>endobj -513 0 obj<>endobj -514 0 obj<>endobj -515 0 obj<>endobj -516 0 obj<>endobj -517 0 obj<>endobj -518 0 obj<>endobj -519 0 obj<>endobj -520 0 obj<>endobj -521 0 obj<>endobj -522 0 obj<>endobj -523 0 obj<>endobj -524 0 obj<>endobj -525 0 obj<>endobj -526 0 obj<>endobj -527 0 obj<>endobj -528 0 obj<>endobj -529 0 obj<>endobj -530 0 obj<>endobj -531 0 obj<>endobj -532 0 obj<>endobj -533 0 obj<>endobj -534 0 obj<>endobj -535 0 obj<>endobj -536 0 obj<>endobj -537 0 obj<>endobj -538 0 obj<>endobj -539 0 obj<>endobj -540 0 obj<>endobj -541 0 obj<>endobj -542 0 obj<>endobj -543 0 obj<>endobj -544 0 obj[493 0 R +491 0 R +492 0 R +493 0 R 494 0 R 495 0 R 496 0 R @@ -1022,9 +998,59 @@ endobj 516 0 R 517 0 R 518 0 R -519 0 R -520 0 R -521 0 R +519 0 R]endobj +521 0 obj<>endobj +522 0 obj<>endobj +523 0 obj<>endobj +524 0 obj<>endobj +525 0 obj<>endobj +526 0 obj<>endobj +527 0 obj<>endobj +528 0 obj<>endobj +529 0 obj<>endobj +530 0 obj<>endobj +531 0 obj<>endobj +532 0 obj<>endobj +533 0 obj<>endobj +534 0 obj<>endobj +535 0 obj<>endobj +536 0 obj<>endobj +537 0 obj<>endobj +538 0 obj<>endobj +539 0 obj<>endobj +540 0 obj<>endobj +541 0 obj<>endobj +542 0 obj<>endobj +543 0 obj<>endobj +544 0 obj<>endobj +545 0 obj<>endobj +546 0 obj<>endobj +547 0 obj<>endobj +548 0 obj<>endobj +549 0 obj<>endobj +550 0 obj<>endobj +551 0 obj<>endobj +552 0 obj<>endobj +553 0 obj<>endobj +554 0 obj<>endobj +555 0 obj<>endobj +556 0 obj<>endobj +557 0 obj<>endobj +558 0 obj<>endobj +559 0 obj<>endobj +560 0 obj<>endobj +561 0 obj<>endobj +562 0 obj<>endobj +563 0 obj<>endobj +564 0 obj<>endobj +565 0 obj<>endobj +566 0 obj<>endobj +567 0 obj<>endobj +568 0 obj<>endobj +569 0 obj<>endobj +570 0 obj<>endobj +571 0 obj<>endobj +572 0 obj[521 0 R 522 0 R 523 0 R 524 0 R @@ -1046,25 +1072,9 @@ endobj 540 0 R 541 0 R 542 0 R -543 0 R]endobj -545 0 obj<>endobj -546 0 obj<>endobj -547 0 obj<>endobj -548 0 obj<>endobj -549 0 obj<>endobj -550 0 obj<>endobj -551 0 obj<>endobj -552 0 obj<>endobj -553 0 obj<>endobj -554 0 obj<>endobj -555 0 obj<>endobj -556 0 obj<>endobj -557 0 obj<>endobj -558 0 obj<>endobj -559 0 obj<>endobj -560 0 obj<>endobj -561 0 obj<>endobj -562 0 obj[545 0 R +543 0 R +544 0 R +545 0 R 546 0 R 547 0 R 548 0 R @@ -1080,52 +1090,9 @@ endobj 558 0 R 559 0 R 560 0 R -561 0 R]endobj -563 0 obj<>endobj -564 0 obj<>endobj -565 0 obj<>endobj -566 0 obj<>endobj -567 0 obj<>endobj -568 0 obj<>endobj -569 0 obj<>endobj -570 0 obj<>endobj -571 0 obj<>endobj -572 0 obj<>endobj -573 0 obj<>endobj -574 0 obj<>endobj -575 0 obj<>endobj -576 0 obj<>endobj -577 0 obj<>endobj -578 0 obj<>endobj -579 0 obj<>endobj -580 0 obj<>endobj -581 0 obj<>endobj -582 0 obj<>endobj -583 0 obj<>endobj -584 0 obj<>endobj -585 0 obj<>endobj -586 0 obj<>endobj -587 0 obj<>endobj -588 0 obj<>endobj -589 0 obj<>endobj -590 0 obj<>endobj -591 0 obj<>endobj -592 0 obj<>endobj -593 0 obj<>endobj -594 0 obj<>endobj -595 0 obj<>endobj -596 0 obj<>endobj -597 0 obj<>endobj -598 0 obj<>endobj -599 0 obj<>endobj -600 0 obj<>endobj -601 0 obj<>endobj -602 0 obj<>endobj -603 0 obj<>endobj -604 0 obj<>endobj -605 0 obj<>endobj -606 0 obj<>endobj -607 0 obj[563 0 R +561 0 R +562 0 R +563 0 R 564 0 R 565 0 R 566 0 R @@ -1133,9 +1100,42 @@ endobj 568 0 R 569 0 R 570 0 R -571 0 R -572 0 R -573 0 R +571 0 R]endobj +573 0 obj<>endobj +574 0 obj<>endobj +575 0 obj<>endobj +576 0 obj<>endobj +577 0 obj<>endobj +578 0 obj<>endobj +579 0 obj<>endobj +580 0 obj<>endobj +581 0 obj<>endobj +582 0 obj<>endobj +583 0 obj<>endobj +584 0 obj<>endobj +585 0 obj<>endobj +586 0 obj<>endobj +587 0 obj<>endobj +588 0 obj<>endobj +589 0 obj<>endobj +590 0 obj<>endobj +591 0 obj<>endobj +592 0 obj<>endobj +593 0 obj<>endobj +594 0 obj<>endobj +595 0 obj<>endobj +596 0 obj<>endobj +597 0 obj<>endobj +598 0 obj<>endobj +599 0 obj<>endobj +600 0 obj<>endobj +601 0 obj<>endobj +602 0 obj<>endobj +603 0 obj<>endobj +604 0 obj<>endobj +605 0 obj<>endobj +606 0 obj<>endobj +607 0 obj[573 0 R 574 0 R 575 0 R 576 0 R @@ -1171,1412 +1171,1022 @@ endobj 606 0 R]endobj 608 0 obj<>endobj 609 0 obj<>endobj -610 0 obj<>endobj -611 0 obj<>endobj -612 0 obj<>endobj +610 0 obj<>endobj +611 0 obj<>endobj +612 0 obj<>endobj 613 0 obj[609 0 R 610 0 R 611 0 R 612 0 R]endobj -614 0 obj<>endobj -615 0 obj[614 0 R]endobj -616 0 obj<>endobj -617 0 obj<>endobj -618 0 obj<>endobj -619 0 obj<>endobj -620 0 obj<>endobj -621 0 obj<>endobj -622 0 obj<>endobj -623 0 obj<>endobj -624 0 obj<>endobj -625 0 obj<>endobj -626 0 obj<>endobj -627 0 obj<>endobj -628 0 obj<>endobj -629 0 obj<>endobj -630 0 obj[617 0 R -619 0 R -621 0 R -623 0 R -625 0 R -627 0 R -629 0 R]endobj +614 0 obj<>endobj +615 0 obj<>endobj +616 0 obj[614 0 R +615 0 R]endobj +617 0 obj<>endobj +618 0 obj<>endobj +619 0 obj<>endobj +620 0 obj<>endobj +621 0 obj<>endobj +622 0 obj<>endobj +623 0 obj<>endobj +624 0 obj<>endobj +625 0 obj<>endobj +626 0 obj<>endobj +627 0 obj<>endobj +628 0 obj<>endobj +629 0 obj<>endobj +630 0 obj<>endobj 631 0 obj<>endobj -632 0 obj<>endobj -633 0 obj<>endobj -634 0 obj<>endobj -635 0 obj<>endobj -636 0 obj<>endobj -637 0 obj[632 0 R -634 0 R -636 0 R]endobj -638 0 obj<>endobj -639 0 obj<>endobj -640 0 obj<>endobj -641 0 obj<>endobj -642 0 obj<>endobj -643 0 obj<>endobj -644 0 obj<>endobj -645 0 obj<>endobj -646 0 obj<>endobj -647 0 obj<>endobj -648 0 obj<>endobj -649 0 obj<>endobj -650 0 obj<>endobj -651 0 obj<>endobj -652 0 obj[639 0 R -641 0 R -643 0 R -645 0 R -647 0 R -649 0 R -651 0 R]endobj -653 0 obj<>endobj -654 0 obj<>endobj -655 0 obj[654 0 R]endobj -656 0 obj<>endobj -657 0 obj<>endobj -658 0 obj[657 0 R]endobj -659 0 obj<>endobj -660 0 obj<>endobj -661 0 obj<>endobj -662 0 obj<>endobj -663 0 obj<>endobj -664 0 obj<>endobj -665 0 obj<>endobj -666 0 obj<>endobj -667 0 obj<>endobj -668 0 obj<>endobj -669 0 obj<>endobj -670 0 obj<>endobj -671 0 obj<>endobj -672 0 obj<>endobj -673 0 obj<>endobj -674 0 obj<>endobj -675 0 obj<>endobj -676 0 obj<>endobj -677 0 obj<>endobj -678 0 obj<>endobj -679 0 obj<>endobj -680 0 obj<>endobj -681 0 obj<>endobj -682 0 obj<>endobj -683 0 obj<>endobj -684 0 obj<>endobj -685 0 obj<>endobj -686 0 obj<>endobj -687 0 obj<>endobj -688 0 obj<>endobj -689 0 obj<>endobj -690 0 obj<>endobj -691 0 obj<>endobj -692 0 obj<>endobj -693 0 obj<>endobj -694 0 obj<>endobj -695 0 obj<>endobj -696 0 obj<>endobj -697 0 obj<>endobj -698 0 obj<>endobj -699 0 obj<>endobj -700 0 obj<>endobj -701 0 obj<>endobj -702 0 obj<>endobj -703 0 obj<>endobj -704 0 obj<>endobj -705 0 obj[659 0 R -660 0 R -661 0 R -662 0 R -663 0 R -664 0 R -665 0 R -666 0 R -667 0 R -668 0 R -669 0 R -670 0 R -671 0 R -672 0 R +632 0 obj<>endobj +633 0 obj[618 0 R +620 0 R +622 0 R +624 0 R +626 0 R +628 0 R +630 0 R +632 0 R]endobj +634 0 obj<>endobj +635 0 obj<>endobj +636 0 obj<>endobj +637 0 obj<>endobj +638 0 obj[635 0 R +637 0 R]endobj +639 0 obj<>endobj +640 0 obj<>endobj +641 0 obj<>endobj +642 0 obj<>endobj +643 0 obj<>endobj +644 0 obj<>endobj +645 0 obj<>endobj +646 0 obj<>endobj +647 0 obj<>endobj +648 0 obj<>endobj +649 0 obj<>endobj +650 0 obj<>endobj +651 0 obj<>endobj +652 0 obj<>endobj +653 0 obj[640 0 R +642 0 R +644 0 R +646 0 R +648 0 R +650 0 R +652 0 R]endobj +654 0 obj<>endobj +655 0 obj<>endobj +656 0 obj[654 0 R +655 0 R]endobj +657 0 obj<>endobj +658 0 obj<>endobj +659 0 obj[658 0 R]endobj +660 0 obj<>endobj +661 0 obj<>endobj +662 0 obj<>endobj +663 0 obj<>endobj +664 0 obj[661 0 R +663 0 R]endobj +665 0 obj<>endobj +666 0 obj<>endobj +667 0 obj<>endobj +668 0 obj<>endobj +669 0 obj[666 0 R +668 0 R]endobj +670 0 obj<>endobj +671 0 obj<>endobj +672 0 obj<>endobj +673 0 obj<>endobj +674 0 obj<>endobj +675 0 obj<>endobj +676 0 obj<>endobj +677 0 obj<>endobj +678 0 obj<>endobj +679 0 obj<>endobj +680 0 obj<>endobj +681 0 obj<>endobj +682 0 obj<>endobj +683 0 obj<>endobj +684 0 obj<>endobj +685 0 obj<>endobj +686 0 obj<>endobj +687 0 obj<>endobj +688 0 obj<>endobj +689 0 obj<>endobj +690 0 obj<>endobj +691 0 obj<>endobj +692 0 obj<>endobj +693 0 obj<>endobj +694 0 obj<>endobj +695 0 obj<>endobj +696 0 obj<>endobj +697 0 obj<>endobj +698 0 obj<>endobj +699 0 obj<>endobj +700 0 obj<>endobj +701 0 obj<>endobj +702 0 obj<>endobj +703 0 obj<>endobj +704 0 obj<>endobj +705 0 obj<>endobj +706 0 obj<>endobj +707 0 obj<>endobj +708 0 obj<>endobj +709 0 obj<>endobj +710 0 obj<>endobj +711 0 obj<>endobj +712 0 obj[671 0 R 673 0 R -674 0 R 675 0 R -676 0 R 677 0 R -678 0 R 679 0 R -680 0 R 681 0 R -682 0 R 683 0 R -684 0 R 685 0 R -686 0 R 687 0 R -688 0 R 689 0 R -690 0 R 691 0 R -692 0 R 693 0 R -694 0 R 695 0 R -696 0 R 697 0 R -698 0 R 699 0 R -700 0 R 701 0 R -702 0 R 703 0 R -704 0 R]endobj -706 0 obj<>endobj -707 0 obj[706 0 R]endobj -708 0 obj<>endobj -709 0 obj<>endobj -710 0 obj<>endobj -711 0 obj<>endobj -712 0 obj[709 0 R +705 0 R +707 0 R +709 0 R +710 0 R 711 0 R]endobj -713 0 obj<>endobj -714 0 obj<>endobj -715 0 obj<>endobj -716 0 obj<>endobj -717 0 obj[714 0 R -716 0 R]endobj -718 0 obj<>endobj -719 0 obj<>endobj -720 0 obj[719 0 R]endobj -721 0 obj<>endobj -722 0 obj<>endobj -723 0 obj<>endobj -724 0 obj<>endobj -725 0 obj<>endobj -726 0 obj<>endobj -727 0 obj<>endobj -728 0 obj<>endobj -729 0 obj<>endobj -730 0 obj<>endobj -731 0 obj<>endobj -732 0 obj<>endobj -733 0 obj<>endobj -734 0 obj<>endobj -735 0 obj<>endobj -736 0 obj<>endobj -737 0 obj<>endobj -738 0 obj<>endobj -739 0 obj<>endobj -740 0 obj<>endobj -741 0 obj<>endobj -742 0 obj<>endobj -743 0 obj<>endobj -744 0 obj<>endobj -745 0 obj<>endobj -746 0 obj<>endobj -747 0 obj<>endobj -748 0 obj<>endobj -749 0 obj<>endobj -750 0 obj<>endobj -751 0 obj<>endobj -752 0 obj<>endobj -753 0 obj<>endobj -754 0 obj<>endobj -755 0 obj<>endobj -756 0 obj<>endobj -757 0 obj<>endobj -758 0 obj<>endobj -759 0 obj<>endobj -760 0 obj<>endobj -761 0 obj<>endobj -762 0 obj<>endobj -763 0 obj<>endobj -764 0 obj[722 0 R -724 0 R +713 0 obj<>endobj +714 0 obj[713 0 R]endobj +715 0 obj<>endobj +716 0 obj<>endobj +717 0 obj[716 0 R]endobj +718 0 obj<>endobj +719 0 obj<>endobj +720 0 obj<>endobj +721 0 obj[719 0 R +720 0 R]endobj +722 0 obj<>endobj +723 0 obj<>endobj +724 0 obj[723 0 R]endobj +725 0 obj<>endobj +726 0 obj<>endobj +727 0 obj<>endobj +728 0 obj[725 0 R 726 0 R -728 0 R -730 0 R +727 0 R]endobj +729 0 obj<>endobj +730 0 obj<>endobj +731 0 obj<>endobj +732 0 obj<>endobj +733 0 obj<>endobj +734 0 obj<>endobj +735 0 obj<>endobj +736 0 obj<>endobj +737 0 obj[730 0 R 732 0 R 734 0 R -736 0 R -738 0 R -740 0 R -742 0 R -744 0 R -746 0 R -748 0 R -750 0 R +736 0 R]endobj +738 0 obj<>endobj +739 0 obj<>endobj +740 0 obj<>endobj +741 0 obj<>endobj +742 0 obj<>endobj +743 0 obj<>endobj +744 0 obj<>endobj +745 0 obj<>endobj +746 0 obj<>endobj +747 0 obj<>endobj +748 0 obj[739 0 R +741 0 R +743 0 R +745 0 R +747 0 R]endobj +749 0 obj<>endobj +750 0 obj<>endobj +751 0 obj<>endobj +752 0 obj<>endobj +753 0 obj<>endobj +754 0 obj<>endobj +755 0 obj<>endobj +756 0 obj<>endobj +757 0 obj<>endobj +758 0 obj<>endobj +759 0 obj[750 0 R 752 0 R 754 0 R 756 0 R -758 0 R -760 0 R -762 0 R -763 0 R]endobj -765 0 obj<>endobj -766 0 obj<>endobj -767 0 obj[766 0 R]endobj -768 0 obj<>endobj -769 0 obj<>endobj -770 0 obj[769 0 R]endobj -771 0 obj<>endobj -772 0 obj<>endobj -773 0 obj<>endobj -774 0 obj<>endobj -775 0 obj[772 0 R -774 0 R]endobj -776 0 obj<>endobj -777 0 obj<>endobj -778 0 obj<>endobj -779 0 obj<>endobj -780 0 obj<>endobj -781 0 obj<>endobj -782 0 obj<>endobj -783 0 obj<>endobj -784 0 obj<>endobj -785 0 obj<>endobj -786 0 obj<>endobj -787 0 obj<>endobj -788 0 obj<>endobj -789 0 obj<>endobj -790 0 obj<>endobj -791 0 obj<>endobj -792 0 obj[777 0 R -779 0 R -781 0 R -783 0 R -785 0 R -787 0 R -789 0 R -791 0 R]endobj -793 0 obj<>endobj -794 0 obj<>endobj -795 0 obj<>endobj -796 0 obj<>endobj -797 0 obj[794 0 R -796 0 R]endobj -798 0 obj<>endobj -799 0 obj<>endobj +758 0 R]endobj +760 0 obj<>endobj +761 0 obj<>endobj +762 0 obj<>endobj +763 0 obj<>endobj +764 0 obj<>endobj +765 0 obj<>endobj +766 0 obj[761 0 R +763 0 R +765 0 R]endobj +767 0 obj<>endobj +768 0 obj<>endobj +769 0 obj<>endobj +770 0 obj<>endobj +771 0 obj<>endobj +772 0 obj<>endobj +773 0 obj<>endobj +774 0 obj<>endobj +775 0 obj<>endobj +776 0 obj<>endobj +777 0 obj[768 0 R +770 0 R +772 0 R +774 0 R +776 0 R]endobj +778 0 obj<>endobj +779 0 obj<>endobj +780 0 obj<>endobj +781 0 obj<>endobj +782 0 obj[779 0 R +781 0 R]endobj +783 0 obj<>endobj +784 0 obj<>endobj +785 0 obj<>endobj +786 0 obj<>endobj +787 0 obj<>endobj +788 0 obj<>endobj +789 0 obj<>endobj +790 0 obj<>endobj +791 0 obj[784 0 R +786 0 R +788 0 R +790 0 R]endobj +792 0 obj<>endobj +793 0 obj<>endobj +794 0 obj[793 0 R]endobj +795 0 obj<>endobj +796 0 obj<>endobj +797 0 obj[796 0 R]endobj +798 0 obj<>endobj +799 0 obj<>endobj 800 0 obj[799 0 R]endobj -801 0 obj<>endobj -802 0 obj<>endobj -803 0 obj<>endobj -804 0 obj[801 0 R -802 0 R -803 0 R]endobj -805 0 obj<>endobj -806 0 obj<>endobj -807 0 obj<>endobj -808 0 obj<>endobj -809 0 obj<>endobj -810 0 obj<>endobj -811 0 obj<>endobj -812 0 obj<>endobj -813 0 obj[806 0 R +801 0 obj<>endobj +802 0 obj<>endobj +803 0 obj<>endobj +804 0 obj<>endobj +805 0 obj<>endobj +806 0 obj<>endobj +807 0 obj<>endobj +808 0 obj<>endobj +809 0 obj<>endobj +810 0 obj<>endobj +811 0 obj<>endobj +812 0 obj<>endobj +813 0 obj[802 0 R +804 0 R +806 0 R 808 0 R 810 0 R 812 0 R]endobj -814 0 obj<>endobj -815 0 obj<>endobj -816 0 obj<>endobj -817 0 obj<>endobj -818 0 obj<>endobj -819 0 obj<>endobj -820 0 obj<>endobj -821 0 obj<>endobj -822 0 obj<>endobj -823 0 obj<>endobj -824 0 obj[815 0 R -817 0 R -819 0 R -821 0 R -823 0 R]endobj -825 0 obj<>endobj -826 0 obj<>endobj -827 0 obj<>endobj -828 0 obj<>endobj -829 0 obj<>endobj -830 0 obj<>endobj -831 0 obj<>endobj -832 0 obj<>endobj -833 0 obj<>endobj -834 0 obj<>endobj -835 0 obj<>endobj -836 0 obj<>endobj -837 0 obj<>endobj -838 0 obj<>endobj -839 0 obj<>endobj -840 0 obj<>endobj -841 0 obj<>endobj -842 0 obj<>endobj -843 0 obj<>endobj -844 0 obj<>endobj -845 0 obj<>endobj -846 0 obj<>endobj -847 0 obj<>endobj -848 0 obj<>endobj -849 0 obj<>endobj -850 0 obj<>endobj -851 0 obj<>endobj -852 0 obj<>endobj -853 0 obj<>endobj -854 0 obj<>endobj -855 0 obj<>endobj -856 0 obj<>endobj -857 0 obj<>endobj -858 0 obj<>endobj -859 0 obj<>endobj -860 0 obj<>endobj -861 0 obj<>endobj -862 0 obj<>endobj -863 0 obj<>endobj -864 0 obj<>endobj -865 0 obj<>endobj -866 0 obj<>endobj -867 0 obj<>endobj -868 0 obj<>endobj -869 0 obj<>endobj -870 0 obj[825 0 R -826 0 R -827 0 R -828 0 R +814 0 obj<>endobj +815 0 obj<>endobj +816 0 obj[815 0 R]endobj +817 0 obj<>endobj +818 0 obj<>endobj +819 0 obj<>endobj +820 0 obj<>endobj +821 0 obj<>endobj +822 0 obj<>endobj +823 0 obj<>endobj +824 0 obj<>endobj +825 0 obj[818 0 R +820 0 R +822 0 R +824 0 R]endobj +826 0 obj<>endobj +827 0 obj<>endobj +828 0 obj<>endobj +829 0 obj<>endobj +830 0 obj<>endobj +831 0 obj<>endobj +832 0 obj[827 0 R 829 0 R -830 0 R -831 0 R -832 0 R -833 0 R -834 0 R -835 0 R -836 0 R -837 0 R -838 0 R -839 0 R -840 0 R -841 0 R -842 0 R -843 0 R -844 0 R +831 0 R]endobj +833 0 obj<>endobj +834 0 obj<>endobj +835 0 obj[834 0 R]endobj +836 0 obj<>endobj +837 0 obj<>endobj +838 0 obj[837 0 R]endobj +839 0 obj<>endobj +840 0 obj<>endobj +841 0 obj[840 0 R]endobj +842 0 obj<>endobj +843 0 obj<>endobj +844 0 obj<>endobj +845 0 obj<>endobj +846 0 obj<>endobj +847 0 obj<>endobj +848 0 obj[843 0 R 845 0 R -846 0 R -847 0 R -848 0 R -849 0 R -850 0 R -851 0 R +847 0 R]endobj +849 0 obj<>endobj +850 0 obj<>endobj +851 0 obj<>endobj +852 0 obj<>endobj +853 0 obj<>endobj +854 0 obj<>endobj +855 0 obj<>endobj +856 0 obj<>endobj +857 0 obj<>endobj +858 0 obj<>endobj +859 0 obj[850 0 R 852 0 R -853 0 R 854 0 R -855 0 R 856 0 R -857 0 R -858 0 R -859 0 R -860 0 R -861 0 R -862 0 R +858 0 R]endobj +860 0 obj<>endobj +861 0 obj<>endobj +862 0 obj<>endobj +863 0 obj<>endobj +864 0 obj<>endobj +865 0 obj<>endobj +866 0 obj<>endobj +867 0 obj<>endobj +868 0 obj[861 0 R 863 0 R -864 0 R 865 0 R -866 0 R -867 0 R -868 0 R -869 0 R]endobj -871 0 obj<>endobj -872 0 obj<>endobj -873 0 obj<>endobj -874 0 obj<>endobj -875 0 obj<>endobj -876 0 obj<>endobj -877 0 obj<>endobj -878 0 obj<>endobj -879 0 obj<>endobj -880 0 obj<>endobj -881 0 obj<>endobj -882 0 obj<>endobj -883 0 obj<>endobj -884 0 obj<>endobj -885 0 obj<>endobj -886 0 obj<>endobj -887 0 obj<>endobj -888 0 obj<>endobj -889 0 obj<>endobj -890 0 obj<>endobj -891 0 obj<>endobj -892 0 obj<>endobj -893 0 obj<>endobj -894 0 obj<>endobj -895 0 obj<>endobj -896 0 obj<>endobj -897 0 obj<>endobj -898 0 obj<>endobj -899 0 obj<>endobj -900 0 obj<>endobj -901 0 obj<>endobj -902 0 obj<>endobj -903 0 obj<>endobj -904 0 obj<>endobj -905 0 obj<>endobj -906 0 obj<>endobj -907 0 obj<>endobj -908 0 obj<>endobj -909 0 obj<>endobj -910 0 obj<>endobj -911 0 obj<>endobj -912 0 obj<>endobj -913 0 obj<>endobj -914 0 obj<>endobj -915 0 obj<>endobj -916 0 obj<>endobj -917 0 obj<>endobj -918 0 obj<>endobj -919 0 obj<>endobj -920 0 obj<>endobj -921 0 obj<>endobj -922 0 obj[871 0 R -872 0 R -873 0 R -874 0 R -875 0 R -876 0 R -877 0 R -878 0 R -879 0 R -880 0 R -881 0 R -882 0 R -883 0 R -884 0 R -885 0 R -886 0 R -887 0 R -888 0 R -889 0 R +867 0 R]endobj +869 0 obj<>endobj +870 0 obj<>endobj +871 0 obj<>endobj +872 0 obj<>endobj +873 0 obj[870 0 R +872 0 R]endobj +874 0 obj<>endobj +875 0 obj<>endobj +876 0 obj<>endobj +877 0 obj<>endobj +878 0 obj[875 0 R +877 0 R]endobj +879 0 obj<>endobj +880 0 obj<>endobj +881 0 obj<>endobj +882 0 obj<>endobj +883 0 obj[880 0 R +882 0 R]endobj +884 0 obj<>endobj +885 0 obj<>endobj +886 0 obj[885 0 R]endobj +887 0 obj<>endobj +888 0 obj<>endobj +889 0 obj<>endobj +890 0 obj<>endobj +891 0 obj<>endobj +892 0 obj<>endobj +893 0 obj[888 0 R 890 0 R -891 0 R -892 0 R -893 0 R -894 0 R -895 0 R -896 0 R -897 0 R -898 0 R -899 0 R -900 0 R -901 0 R -902 0 R -903 0 R -904 0 R -905 0 R +892 0 R]endobj +894 0 obj<>endobj +895 0 obj<>endobj +896 0 obj[894 0 R +895 0 R]endobj +897 0 obj<>endobj +898 0 obj<>endobj +899 0 obj[898 0 R]endobj +900 0 obj<>endobj +901 0 obj<>endobj +902 0 obj[901 0 R]endobj +903 0 obj<>endobj +904 0 obj<>endobj +905 0 obj<>endobj +906 0 obj<>endobj +907 0 obj<>endobj +908 0 obj<>endobj +909 0 obj<>endobj +910 0 obj<>endobj +911 0 obj[904 0 R 906 0 R -907 0 R 908 0 R -909 0 R -910 0 R -911 0 R -912 0 R -913 0 R -914 0 R -915 0 R -916 0 R -917 0 R -918 0 R -919 0 R +910 0 R]endobj +912 0 obj<>endobj +913 0 obj<>endobj +914 0 obj<>endobj +915 0 obj<>endobj +916 0 obj[913 0 R +915 0 R]endobj +917 0 obj<>endobj +918 0 obj<>endobj +919 0 obj<>endobj +920 0 obj<>endobj +921 0 obj<>endobj +922 0 obj<>endobj +923 0 obj<>endobj +924 0 obj<>endobj +925 0 obj<>endobj +926 0 obj<>endobj +927 0 obj[918 0 R 920 0 R -921 0 R]endobj -923 0 obj<>endobj -924 0 obj<>endobj -925 0 obj<>endobj -926 0 obj<>endobj -927 0 obj<>endobj -928 0 obj<>endobj -929 0 obj<>endobj -930 0 obj<>endobj -931 0 obj<>endobj -932 0 obj<>endobj -933 0 obj<>endobj -934 0 obj<>endobj -935 0 obj<>endobj -936 0 obj<>endobj -937 0 obj<>endobj -938 0 obj<>endobj -939 0 obj<>endobj -940 0 obj<>endobj -941 0 obj<>endobj -942 0 obj<>endobj -943 0 obj<>endobj -944 0 obj<>endobj -945 0 obj<>endobj -946 0 obj<>endobj -947 0 obj<>endobj -948 0 obj<>endobj -949 0 obj<>endobj -950 0 obj<>endobj -951 0 obj<>endobj -952 0 obj<>endobj -953 0 obj<>endobj -954 0 obj<>endobj -955 0 obj<>endobj -956 0 obj<>endobj -957 0 obj<>endobj -958 0 obj<>endobj -959 0 obj<>endobj -960 0 obj<>endobj -961 0 obj<>endobj -962 0 obj<>endobj -963 0 obj<>endobj -964 0 obj<>endobj -965 0 obj<>endobj -966 0 obj<>endobj -967 0 obj<>endobj -968 0 obj<>endobj -969 0 obj<>endobj -970 0 obj<>endobj -971 0 obj<>endobj -972 0 obj<>endobj -973 0 obj<>endobj -974 0 obj[923 0 R +922 0 R 924 0 R -925 0 R -926 0 R -927 0 R -928 0 R -929 0 R -930 0 R +926 0 R]endobj +928 0 obj<>endobj +929 0 obj<>endobj +930 0 obj<>endobj +931 0 obj<>endobj +932 0 obj<>endobj +933 0 obj<>endobj +934 0 obj<>endobj +935 0 obj<>endobj +936 0 obj[929 0 R 931 0 R -932 0 R 933 0 R -934 0 R -935 0 R -936 0 R -937 0 R -938 0 R -939 0 R -940 0 R -941 0 R -942 0 R +935 0 R]endobj +937 0 obj<>endobj +938 0 obj<>endobj +939 0 obj[938 0 R]endobj +940 0 obj<>endobj +941 0 obj<>endobj +942 0 obj<>endobj +943 0 obj<>endobj +944 0 obj<>endobj +945 0 obj<>endobj +946 0 obj[941 0 R 943 0 R -944 0 R -945 0 R -946 0 R -947 0 R -948 0 R -949 0 R -950 0 R -951 0 R -952 0 R -953 0 R -954 0 R -955 0 R -956 0 R +945 0 R]endobj +947 0 obj<>endobj +948 0 obj[947 0 R]endobj +949 0 obj<>endobj +950 0 obj<>endobj +951 0 obj<>endobj +952 0 obj<>endobj +953 0 obj[950 0 R +952 0 R]endobj +954 0 obj<>endobj +955 0 obj<>endobj +956 0 obj<>endobj +957 0 obj<>endobj +958 0 obj<>endobj +959 0 obj<>endobj +960 0 obj<>endobj +961 0 obj<>endobj +962 0 obj<>endobj +963 0 obj<>endobj +964 0 obj<>endobj +965 0 obj<>endobj +966 0 obj<>endobj +967 0 obj<>endobj +968 0 obj<>endobj +969 0 obj<>endobj +970 0 obj[955 0 R 957 0 R -958 0 R 959 0 R -960 0 R 961 0 R -962 0 R 963 0 R -964 0 R 965 0 R -966 0 R 967 0 R -968 0 R -969 0 R -970 0 R -971 0 R -972 0 R -973 0 R]endobj -975 0 obj<>endobj -976 0 obj<>endobj -977 0 obj<>endobj -978 0 obj<>endobj -979 0 obj<>endobj -980 0 obj<>endobj -981 0 obj<>endobj -982 0 obj[975 0 R -976 0 R -977 0 R -978 0 R +969 0 R]endobj +971 0 obj<>endobj +972 0 obj<>endobj +973 0 obj<>endobj +974 0 obj<>endobj +975 0 obj[972 0 R +974 0 R]endobj +976 0 obj<>endobj +977 0 obj<>endobj +978 0 obj<>endobj +979 0 obj<>endobj +980 0 obj<>endobj +981 0 obj<>endobj +982 0 obj<>endobj +983 0 obj[977 0 R 979 0 R -980 0 R -981 0 R]endobj -983 0 obj<>endobj -984 0 obj<>endobj -985 0 obj<>endobj -986 0 obj<>endobj -987 0 obj<>endobj -988 0 obj<>endobj -989 0 obj<>endobj -990 0 obj<>endobj -991 0 obj<>endobj -992 0 obj<>endobj -993 0 obj[984 0 R -986 0 R -988 0 R -990 0 R -992 0 R]endobj -994 0 obj<>endobj -995 0 obj<>endobj -996 0 obj<>endobj -997 0 obj<>endobj -998 0 obj<>endobj -999 0 obj<>endobj -1000 0 obj[995 0 R -997 0 R -999 0 R]endobj -1001 0 obj<>endobj -1002 0 obj<>endobj -1003 0 obj<>endobj -1004 0 obj<>endobj -1005 0 obj<>endobj -1006 0 obj<>endobj -1007 0 obj<>endobj -1008 0 obj<>endobj -1009 0 obj<>endobj -1010 0 obj<>endobj -1011 0 obj[1002 0 R -1004 0 R -1006 0 R -1008 0 R -1010 0 R]endobj -1012 0 obj<>endobj -1013 0 obj<>endobj -1014 0 obj<>endobj -1015 0 obj<>endobj -1016 0 obj[1013 0 R -1015 0 R]endobj -1017 0 obj<>endobj -1018 0 obj<>endobj -1019 0 obj<>endobj -1020 0 obj<>endobj -1021 0 obj<>endobj -1022 0 obj<>endobj -1023 0 obj<>endobj -1024 0 obj<>endobj -1025 0 obj[1018 0 R -1020 0 R -1022 0 R -1024 0 R]endobj -1026 0 obj<>endobj -1027 0 obj<>endobj -1028 0 obj[1027 0 R]endobj -1029 0 obj<>endobj -1030 0 obj<>endobj -1031 0 obj[1030 0 R]endobj -1032 0 obj<>endobj -1033 0 obj<>endobj -1034 0 obj[1033 0 R]endobj -1035 0 obj<>endobj -1036 0 obj<>endobj -1037 0 obj<>endobj -1038 0 obj<>endobj -1039 0 obj<>endobj -1040 0 obj<>endobj -1041 0 obj<>endobj -1042 0 obj<>endobj -1043 0 obj<>endobj -1044 0 obj<>endobj -1045 0 obj<>endobj -1046 0 obj<>endobj -1047 0 obj[1036 0 R -1038 0 R -1040 0 R -1042 0 R -1044 0 R -1046 0 R]endobj -1048 0 obj<>endobj -1049 0 obj<>endobj -1050 0 obj[1049 0 R]endobj -1051 0 obj<>endobj -1052 0 obj<>endobj -1053 0 obj<>endobj -1054 0 obj<>endobj -1055 0 obj<>endobj -1056 0 obj<>endobj -1057 0 obj<>endobj -1058 0 obj<>endobj -1059 0 obj[1052 0 R -1054 0 R -1056 0 R -1058 0 R]endobj -1060 0 obj<>endobj -1061 0 obj<>endobj -1062 0 obj<>endobj -1063 0 obj<>endobj -1064 0 obj<>endobj -1065 0 obj<>endobj -1066 0 obj[1061 0 R -1063 0 R -1065 0 R]endobj -1067 0 obj<>endobj -1068 0 obj<>endobj -1069 0 obj[1068 0 R]endobj -1070 0 obj<>endobj -1071 0 obj<>endobj -1072 0 obj[1071 0 R]endobj -1073 0 obj<>endobj -1074 0 obj<>endobj -1075 0 obj[1074 0 R]endobj -1076 0 obj<>endobj -1077 0 obj<>endobj -1078 0 obj<>endobj -1079 0 obj<>endobj -1080 0 obj<>endobj -1081 0 obj<>endobj -1082 0 obj[1077 0 R -1079 0 R -1081 0 R]endobj -1083 0 obj<>endobj -1084 0 obj<>endobj -1085 0 obj<>endobj -1086 0 obj<>endobj -1087 0 obj<>endobj -1088 0 obj<>endobj -1089 0 obj<>endobj -1090 0 obj<>endobj -1091 0 obj<>endobj -1092 0 obj<>endobj -1093 0 obj[1084 0 R -1086 0 R -1088 0 R -1090 0 R -1092 0 R]endobj -1094 0 obj<>endobj -1095 0 obj<>endobj -1096 0 obj<>endobj -1097 0 obj<>endobj -1098 0 obj<>endobj -1099 0 obj<>endobj -1100 0 obj<>endobj -1101 0 obj<>endobj -1102 0 obj[1095 0 R -1097 0 R -1099 0 R -1101 0 R]endobj -1103 0 obj<>endobj -1104 0 obj<>endobj -1105 0 obj<>endobj -1106 0 obj<>endobj -1107 0 obj[1104 0 R -1106 0 R]endobj -1108 0 obj<>endobj -1109 0 obj<>endobj -1110 0 obj<>endobj -1111 0 obj<>endobj -1112 0 obj[1109 0 R -1111 0 R]endobj -1113 0 obj<>endobj -1114 0 obj<>endobj -1115 0 obj<>endobj -1116 0 obj<>endobj -1117 0 obj[1114 0 R -1116 0 R]endobj -1118 0 obj<>endobj -1119 0 obj<>endobj -1120 0 obj[1119 0 R]endobj -1121 0 obj<>endobj -1122 0 obj<>endobj -1123 0 obj<>endobj -1124 0 obj<>endobj -1125 0 obj<>endobj -1126 0 obj<>endobj -1127 0 obj[1122 0 R -1124 0 R -1126 0 R]endobj -1128 0 obj<>endobj -1129 0 obj<>endobj -1130 0 obj[1128 0 R -1129 0 R]endobj -1131 0 obj<>endobj -1132 0 obj<>endobj -1133 0 obj[1132 0 R]endobj -1134 0 obj<>endobj -1135 0 obj<>endobj -1136 0 obj[1135 0 R]endobj -1137 0 obj<>endobj -1138 0 obj<>endobj -1139 0 obj<>endobj -1140 0 obj<>endobj -1141 0 obj<>endobj -1142 0 obj<>endobj -1143 0 obj<>endobj -1144 0 obj<>endobj -1145 0 obj<>endobj -1146 0 obj<>endobj -1147 0 obj<>endobj -1148 0 obj<>endobj -1149 0 obj<>endobj -1150 0 obj<>endobj -1151 0 obj<>endobj -1152 0 obj<>endobj -1153 0 obj<>endobj -1154 0 obj<>endobj -1155 0 obj<>endobj -1156 0 obj<>endobj -1157 0 obj<>endobj -1158 0 obj<>endobj -1159 0 obj<>endobj -1160 0 obj<>endobj -1161 0 obj<>endobj -1162 0 obj<>endobj -1163 0 obj<>endobj -1164 0 obj<>endobj -1165 0 obj<>endobj -1166 0 obj<>endobj -1167 0 obj<>endobj -1168 0 obj<>endobj -1169 0 obj<>endobj -1170 0 obj<>endobj -1171 0 obj<>endobj -1172 0 obj<>endobj -1173 0 obj<>endobj -1174 0 obj<>endobj -1175 0 obj<>endobj -1176 0 obj<>endobj -1177 0 obj<>endobj -1178 0 obj<>endobj -1179 0 obj<>endobj -1180 0 obj<>endobj -1181 0 obj<>endobj -1182 0 obj<>endobj -1183 0 obj<>endobj -1184 0 obj[1137 0 R -1138 0 R -1139 0 R -1140 0 R -1141 0 R -1142 0 R -1143 0 R -1144 0 R -1145 0 R -1146 0 R -1147 0 R -1148 0 R -1149 0 R -1150 0 R -1151 0 R -1152 0 R -1153 0 R -1154 0 R -1155 0 R -1156 0 R -1157 0 R -1158 0 R -1159 0 R -1160 0 R -1161 0 R -1162 0 R -1163 0 R -1164 0 R -1165 0 R -1166 0 R -1167 0 R -1168 0 R -1169 0 R -1170 0 R -1171 0 R -1172 0 R -1173 0 R -1174 0 R -1175 0 R -1176 0 R -1177 0 R -1178 0 R -1179 0 R -1180 0 R -1181 0 R -1182 0 R -1183 0 R]endobj -1185 0 obj<>endobj -1186 0 obj<>endobj -1187 0 obj<>endobj -1188 0 obj<>endobj -1189 0 obj<>endobj -1190 0 obj<>endobj -1191 0 obj<>endobj -1192 0 obj<>endobj -1193 0 obj<>endobj -1194 0 obj<>endobj -1195 0 obj<>endobj -1196 0 obj<>endobj -1197 0 obj<>endobj -1198 0 obj<>endobj -1199 0 obj<>endobj -1200 0 obj<>endobj -1201 0 obj<>endobj -1202 0 obj<>endobj -1203 0 obj<>endobj -1204 0 obj<>endobj -1205 0 obj<>endobj -1206 0 obj<>endobj -1207 0 obj<>endobj -1208 0 obj[1185 0 R -1186 0 R -1187 0 R -1188 0 R -1189 0 R -1190 0 R -1191 0 R -1192 0 R -1193 0 R -1194 0 R -1195 0 R -1196 0 R -1197 0 R -1198 0 R -1199 0 R -1200 0 R -1201 0 R -1202 0 R -1203 0 R -1204 0 R -1205 0 R -1206 0 R -1207 0 R]endobj -1209 0 obj<>endobj -1210 0 obj<>endobj -1211 0 obj<>endobj -1212 0 obj<>endobj -1213 0 obj<>endobj -1214 0 obj<>endobj -1215 0 obj<>endobj -1216 0 obj<>endobj -1217 0 obj<>endobj -1218 0 obj<>endobj -1219 0 obj[1210 0 R -1212 0 R -1214 0 R -1216 0 R -1218 0 R]endobj -1220 0 obj<>endobj -1221 0 obj<>endobj -1222 0 obj<>endobj -1223 0 obj<>endobj -1224 0 obj<>endobj -1225 0 obj<>endobj -1226 0 obj<>endobj -1227 0 obj<>endobj -1228 0 obj[1221 0 R -1223 0 R -1225 0 R -1227 0 R]endobj -1229 0 obj<>endobj -1230 0 obj<>endobj -1231 0 obj[1230 0 R]endobj -1232 0 obj<>endobj -1233 0 obj<>endobj -1234 0 obj<>endobj -1235 0 obj<>endobj -1236 0 obj<>endobj -1237 0 obj<>endobj -1238 0 obj[1233 0 R -1235 0 R -1237 0 R]endobj -1239 0 obj<>endobj -1240 0 obj<>endobj -1241 0 obj<>endobj -1242 0 obj<>endobj -1243 0 obj<>endobj -1244 0 obj<>endobj -1245 0 obj<>endobj -1246 0 obj<>endobj -1247 0 obj[1240 0 R -1242 0 R -1244 0 R -1246 0 R]endobj -1248 0 obj<>endobj -1249 0 obj<>endobj -1250 0 obj<>endobj -1251 0 obj<>endobj -1252 0 obj[1249 0 R -1251 0 R]endobj -1253 0 obj<>endobj -1254 0 obj<>endobj -1255 0 obj<>endobj -1256 0 obj<>endobj -1257 0 obj<>endobj -1258 0 obj<>endobj -1259 0 obj<>endobj -1260 0 obj[1254 0 R -1256 0 R -1258 0 R -1259 0 R]endobj -1261 0 obj<>endobj -1262 0 obj<>endobj -1263 0 obj<>endobj -1264 0 obj<>endobj -1265 0 obj[1262 0 R -1264 0 R]endobj -1266 0 obj<>endobj -1267 0 obj<>endobj -1268 0 obj<>endobj -1269 0 obj<>endobj -1270 0 obj<>endobj -1271 0 obj<>endobj -1272 0 obj<>endobj -1273 0 obj<>endobj -1274 0 obj<>endobj -1275 0 obj<>endobj -1276 0 obj<>endobj -1277 0 obj<>endobj -1278 0 obj<>endobj -1279 0 obj<>endobj -1280 0 obj<>endobj -1281 0 obj<>endobj -1282 0 obj<>endobj -1283 0 obj<>endobj -1284 0 obj<>endobj -1285 0 obj<>endobj -1286 0 obj<>endobj -1287 0 obj<>endobj -1288 0 obj<>endobj -1289 0 obj<>endobj -1290 0 obj<>endobj -1291 0 obj<>endobj -1292 0 obj<>endobj -1293 0 obj<>endobj -1294 0 obj<>endobj -1295 0 obj<>endobj -1296 0 obj<>endobj -1297 0 obj<>endobj -1298 0 obj<>endobj -1299 0 obj<>endobj -1300 0 obj<>endobj -1301 0 obj<>endobj -1302 0 obj<>endobj -1303 0 obj<>endobj -1304 0 obj<>endobj -1305 0 obj<>endobj -1306 0 obj<>endobj -1307 0 obj<>endobj -1308 0 obj<>endobj -1309 0 obj<>endobj -1310 0 obj<>endobj -1311 0 obj<>endobj -1312 0 obj<>endobj -1313 0 obj<>endobj -1314 0 obj<>endobj -1315 0 obj<>endobj -1316 0 obj<>endobj -1317 0 obj<>endobj -1318 0 obj<>endobj -1319 0 obj<>endobj -1320 0 obj<>endobj -1321 0 obj<>endobj -1322 0 obj<>endobj -1323 0 obj<>endobj -1324 0 obj<>endobj -1325 0 obj<>endobj -1326 0 obj<>endobj -1327 0 obj<>endobj -1328 0 obj<>endobj -1329 0 obj<>endobj -1330 0 obj<>endobj -1331 0 obj<>endobj -1332 0 obj<>endobj -1333 0 obj<>endobj -1334 0 obj<>endobj -1335 0 obj<>endobj -1336 0 obj<>endobj -1337 0 obj<>endobj -1338 0 obj<>endobj -1339 0 obj<>endobj -1340 0 obj<>endobj -1341 0 obj<>endobj -1342 0 obj<>endobj -1343 0 obj<>endobj -1344 0 obj<>endobj -1345 0 obj<>endobj -1346 0 obj<>endobj -1347 0 obj<>endobj -1348 0 obj<>endobj -1349 0 obj<>endobj -1350 0 obj<>endobj -1351 0 obj<>endobj -1352 0 obj<>endobj -1353 0 obj<>endobj -1354 0 obj<>endobj -1355 0 obj<>endobj -1356 0 obj<>endobj -1357 0 obj<>endobj -1358 0 obj<>endobj -1359 0 obj<>endobj -1360 0 obj<>endobj -1361 0 obj<>endobj -1362 0 obj<>endobj -1363 0 obj<>endobj -1364 0 obj<>endobj -1365 0 obj<>endobj -1366 0 obj<>endobj -1367 0 obj<>endobj -1368 0 obj<>endobj -1369 0 obj<>endobj -1370 0 obj<>endobj -1371 0 obj<>endobj -1372 0 obj<>endobj -1373 0 obj<>endobj -1374 0 obj<>endobj -1375 0 obj<>endobj -1376 0 obj<>endobj -1377 0 obj<>endobj -1378 0 obj<>endobj -1379 0 obj<>endobj -1380 0 obj<>endobj -1381 0 obj<>endobj -1382 0 obj<>endobj -1383 0 obj<>endobj -1384 0 obj<>endobj -1385 0 obj<>endobj -1386 0 obj<>endobj -1387 0 obj<>endobj -1388 0 obj<>endobj -1389 0 obj<>endobj -1390 0 obj<>endobj -1391 0 obj<>endobj -1392 0 obj<>endobj -1393 0 obj<>endobj -1394 0 obj<>endobj -1395 0 obj<>endobj -1396 0 obj<>endobj -1397 0 obj<>endobj -1398 0 obj<>endobj -1399 0 obj<>endobj -1400 0 obj<>endobj -1401 0 obj<>endobj -1402 0 obj<>endobj -1403 0 obj<>endobj -1404 0 obj<>endobj -1405 0 obj<>endobj -1406 0 obj<>endobj -1407 0 obj<>endobj -1408 0 obj<>endobj -1409 0 obj<>endobj -1410 0 obj<>endobj -1411 0 obj<>endobj -1412 0 obj<>endobj -1413 0 obj<>endobj -1414 0 obj<>endobj -1415 0 obj<>endobj -1416 0 obj<>endobj -1417 0 obj<>endobj -1418 0 obj<>endobj -1419 0 obj<>endobj -1420 0 obj<>endobj -1421 0 obj<>endobj -1422 0 obj<>endobj -1423 0 obj<>endobj -1424 0 obj<>endobj -1425 0 obj<>endobj -1426 0 obj<>endobj -1427 0 obj<>endobj -1428 0 obj<>endobj -1429 0 obj<>endobj -1430 0 obj<>endobj -1431 0 obj<>endobj -1432 0 obj<>endobj -1433 0 obj<>endobj -1434 0 obj<>endobj -1435 0 obj<>endobj -1436 0 obj<>endobj -1437 0 obj<>endobj -1438 0 obj<>endobj -1439 0 obj<>endobj -1440 0 obj<>endobj -1441 0 obj<>endobj -1442 0 obj<>endobj -1443 0 obj<>endobj -1444 0 obj<>endobj -1445 0 obj<>endobj -1446 0 obj<>endobj -1447 0 obj<>endobj -1448 0 obj<>endobj -1449 0 obj<>endobj -1450 0 obj<>endobj -1451 0 obj<>endobj -1452 0 obj<>endobj -1453 0 obj<>endobj -1454 0 obj<>endobj -1455 0 obj<>endobj -1456 0 obj<>endobj -1457 0 obj<>endobj -1458 0 obj<>endobj -1459 0 obj<>endobj -1460 0 obj<>endobj -1461 0 obj<>endobj -1462 0 obj<>endobj -1463 0 obj<>endobj -1464 0 obj<>endobj -1465 0 obj<>endobj -1466 0 obj<>endobj -1467 0 obj<>endobj -1468 0 obj<>endobj -1469 0 obj<>endobj -1470 0 obj<>endobj -1471 0 obj<>endobj -1472 0 obj<>endobj -1473 0 obj<>endobj -1474 0 obj<>endobj -1475 0 obj<>endobj -1476 0 obj<>endobj -1477 0 obj<>endobj -1478 0 obj<>endobj -1479 0 obj<>endobj -1480 0 obj<>endobj -1481 0 obj<>endobj -1482 0 obj<>endobj -1483 0 obj<>endobj -1484 0 obj<>endobj -1485 0 obj<>endobj -1486 0 obj<>endobj -1487 0 obj<>endobj -1488 0 obj<>endobj -1489 0 obj<>endobj -1490 0 obj<>endobj -1491 0 obj<>endobj -1492 0 obj<>endobj -1493 0 obj<>endobj -1494 0 obj<>endobj -1495 0 obj<>endobj -1496 0 obj<>endobj -1497 0 obj<>endobj -1498 0 obj<>endobj -1499 0 obj<>endobj -1500 0 obj<>endobj -1501 0 obj<>endobj -1502 0 obj<>endobj -1503 0 obj<>endobj -1504 0 obj<>endobj -1505 0 obj<>endobj -1506 0 obj<>endobj -1507 0 obj<>endobj -1508 0 obj<>endobj -1509 0 obj<>endobj -1510 0 obj<>endobj -1511 0 obj<>endobj -1512 0 obj<>endobj -1513 0 obj<>endobj -1514 0 obj<>endobj -1515 0 obj<>endobj -1516 0 obj<>endobj -1517 0 obj<>endobj -1518 0 obj<>endobj -1519 0 obj<>endobj -1520 0 obj<>endobj -1521 0 obj<>endobj -1522 0 obj<>endobj -1523 0 obj<>endobj -1524 0 obj<>endobj -1525 0 obj<>endobj -1526 0 obj<>endobj -1527 0 obj<>endobj -1528 0 obj<>endobj -1529 0 obj<>endobj -1530 0 obj<>endobj -1531 0 obj<>endobj -1532 0 obj<>endobj -1533 0 obj<>endobj -1534 0 obj<>endobj -1535 0 obj<>endobj -1536 0 obj<>endobj -1537 0 obj<>endobj -1538 0 obj<>endobj -1539 0 obj<>endobj -1540 0 obj<>endobj -1541 0 obj<>endobj -1542 0 obj<>endobj -1543 0 obj<>endobj -1544 0 obj<>endobj -1545 0 obj<>endobj -1546 0 obj<>endobj -1547 0 obj<>endobj -1548 0 obj<>endobj -1549 0 obj<>endobj -1550 0 obj<>endobj -1551 0 obj<>endobj -1552 0 obj<>endobj -1553 0 obj<>endobj -1554 0 obj<>endobj -1555 0 obj<>endobj -1556 0 obj<>endobj -1557 0 obj<>endobj -1558 0 obj<>endobj -1559 0 obj<>endobj -1560 0 obj<>endobj -1561 0 obj<>endobj -1562 0 obj<>endobj -1563 0 obj<>endobj -1564 0 obj<>endobj -1565 0 obj<>endobj -1566 0 obj<>endobj -1567 0 obj<>endobj -1568 0 obj<>endobj -1569 0 obj<>endobj -1570 0 obj<>endobj -1571 0 obj<>endobj -1572 0 obj<>endobj -1573 0 obj<>endobj -1574 0 obj<>endobj -1575 0 obj<>endobj -1576 0 obj<>endobj -1577 0 obj<>endobj -1578 0 obj<>endobj -1579 0 obj<>endobj -1580 0 obj<>endobj -1581 0 obj<>endobj -1582 0 obj<>endobj -1583 0 obj<>endobj -1584 0 obj<>endobj -1585 0 obj<>endobj -1586 0 obj<>endobj -1587 0 obj<>endobj -1588 0 obj<>endobj -1589 0 obj<>endobj -1590 0 obj<>endobj -1591 0 obj<>endobj -1592 0 obj<>endobj -1593 0 obj<>endobj -1594 0 obj<>endobj -1595 0 obj<>endobj -1596 0 obj<>endobj -1597 0 obj<>endobj -1598 0 obj<>endobj -1599 0 obj<>endobj -1600 0 obj<>endobj -1601 0 obj<>endobj -1602 0 obj<>endobj -1603 0 obj<>endobj -1604 0 obj<>endobj -1605 0 obj<>endobj -1606 0 obj<>endobj -1607 0 obj<>endobj -1608 0 obj<>endobj -1609 0 obj<>endobj -1610 0 obj<>endobj -1611 0 obj<>endobj -1612 0 obj<>endobj -1613 0 obj<>endobj -1614 0 obj<>endobj -1615 0 obj<>endobj -1616 0 obj<>endobj -1617 0 obj<>endobj -1618 0 obj<>endobj -1619 0 obj<>endobj -1620 0 obj<>endobj -1621 0 obj<>endobj -1622 0 obj<>endobj -1623 0 obj<>endobj -1624 0 obj<>endobj -1625 0 obj<>endobj -1626 0 obj<>endobj -1627 0 obj<>endobj -1628 0 obj<>endobj -1629 0 obj<>endobj -1630 0 obj<>endobj -1631 0 obj<>endobj -1632 0 obj<>endobj -1633 0 obj<>endobj -1634 0 obj<>endobj -1635 0 obj<>endobj -1636 0 obj<>endobj -1637 0 obj<>endobj -1638 0 obj<>endobj +985 0 obj<>endobj +986 0 obj<>endobj +987 0 obj<>endobj +988 0 obj<>endobj +989 0 obj<>endobj +990 0 obj<>endobj +991 0 obj<>endobj +992 0 obj<>endobj +993 0 obj<>endobj +994 0 obj<>endobj +995 0 obj<>endobj +996 0 obj<>endobj +997 0 obj<>endobj +998 0 obj<>endobj +999 0 obj<>endobj +1000 0 obj<>endobj +1001 0 obj<>endobj +1002 0 obj<>endobj +1003 0 obj<>endobj +1004 0 obj<>endobj +1005 0 obj<>endobj +1006 0 obj<>endobj +1007 0 obj<>endobj +1008 0 obj<>endobj +1009 0 obj<>endobj +1010 0 obj<>endobj +1011 0 obj<>endobj +1012 0 obj<>endobj +1013 0 obj<>endobj +1014 0 obj<>endobj +1015 0 obj<>endobj +1016 0 obj<>endobj +1017 0 obj<>endobj +1018 0 obj<>endobj +1019 0 obj<>endobj +1020 0 obj<>endobj +1021 0 obj<>endobj +1022 0 obj<>endobj +1023 0 obj<>endobj +1024 0 obj<>endobj +1025 0 obj<>endobj +1026 0 obj<>endobj +1027 0 obj<>endobj +1028 0 obj<>endobj +1029 0 obj<>endobj +1030 0 obj<>endobj +1031 0 obj<>endobj +1032 0 obj<>endobj +1033 0 obj<>endobj +1034 0 obj<>endobj +1035 0 obj<>endobj +1036 0 obj<>endobj +1037 0 obj<>endobj +1038 0 obj<>endobj +1039 0 obj<>endobj +1040 0 obj<>endobj +1041 0 obj<>endobj +1042 0 obj<>endobj +1043 0 obj<>endobj +1044 0 obj<>endobj +1045 0 obj<>endobj +1046 0 obj<>endobj +1047 0 obj<>endobj +1048 0 obj<>endobj +1049 0 obj<>endobj +1050 0 obj<>endobj +1051 0 obj<>endobj +1052 0 obj<>endobj +1053 0 obj<>endobj +1054 0 obj<>endobj +1055 0 obj<>endobj +1056 0 obj<>endobj +1057 0 obj<>endobj +1058 0 obj<>endobj +1059 0 obj<>endobj +1060 0 obj<>endobj +1061 0 obj<>endobj +1062 0 obj<>endobj +1063 0 obj<>endobj +1064 0 obj<>endobj +1065 0 obj<>endobj +1066 0 obj<>endobj +1067 0 obj<>endobj +1068 0 obj<>endobj +1069 0 obj<>endobj +1070 0 obj<>endobj +1071 0 obj<>endobj +1072 0 obj<>endobj +1073 0 obj<>endobj +1074 0 obj<>endobj +1075 0 obj<>endobj +1076 0 obj<>endobj +1077 0 obj<>endobj +1078 0 obj<>endobj +1079 0 obj<>endobj +1080 0 obj<>endobj +1081 0 obj<>endobj +1082 0 obj<>endobj +1083 0 obj<>endobj +1084 0 obj<>endobj +1085 0 obj<>endobj +1086 0 obj<>endobj +1087 0 obj<>endobj +1088 0 obj<>endobj +1089 0 obj<>endobj +1090 0 obj<>endobj +1091 0 obj<>endobj +1092 0 obj<>endobj +1093 0 obj<>endobj +1094 0 obj<>endobj +1095 0 obj<>endobj +1096 0 obj<>endobj +1097 0 obj<>endobj +1098 0 obj<>endobj +1099 0 obj<>endobj +1100 0 obj<>endobj +1101 0 obj<>endobj +1102 0 obj<>endobj +1103 0 obj<>endobj +1104 0 obj<>endobj +1105 0 obj<>endobj +1106 0 obj<>endobj +1107 0 obj<>endobj +1108 0 obj<>endobj +1109 0 obj<>endobj +1110 0 obj<>endobj +1111 0 obj<>endobj +1112 0 obj<>endobj +1113 0 obj<>endobj +1114 0 obj<>endobj +1115 0 obj<>endobj +1116 0 obj<>endobj +1117 0 obj<>endobj +1118 0 obj<>endobj +1119 0 obj<>endobj +1120 0 obj<>endobj +1121 0 obj<>endobj +1122 0 obj<>endobj +1123 0 obj<>endobj +1124 0 obj<>endobj +1125 0 obj<>endobj +1126 0 obj<>endobj +1127 0 obj<>endobj +1128 0 obj<>endobj +1129 0 obj<>endobj +1130 0 obj<>endobj +1131 0 obj<>endobj +1132 0 obj<>endobj +1133 0 obj<>endobj +1134 0 obj<>endobj +1135 0 obj<>endobj +1136 0 obj<>endobj +1137 0 obj<>endobj +1138 0 obj<>endobj +1139 0 obj<>endobj +1140 0 obj<>endobj +1141 0 obj<>endobj +1142 0 obj<>endobj +1143 0 obj<>endobj +1144 0 obj<>endobj +1145 0 obj<>endobj +1146 0 obj<>endobj +1147 0 obj<>endobj +1148 0 obj<>endobj +1149 0 obj<>endobj +1150 0 obj<>endobj +1151 0 obj<>endobj +1152 0 obj<>endobj +1153 0 obj<>endobj +1154 0 obj<>endobj +1155 0 obj<>endobj +1156 0 obj<>endobj +1157 0 obj<>endobj +1158 0 obj<>endobj +1159 0 obj<>endobj +1160 0 obj<>endobj +1161 0 obj<>endobj +1162 0 obj<>endobj +1163 0 obj<>endobj +1164 0 obj<>endobj +1165 0 obj<>endobj +1166 0 obj<>endobj +1167 0 obj<>endobj +1168 0 obj<>endobj +1169 0 obj<>endobj +1170 0 obj<>endobj +1171 0 obj<>endobj +1172 0 obj<>endobj +1173 0 obj<>endobj +1174 0 obj<>endobj +1175 0 obj<>endobj +1176 0 obj<>endobj +1177 0 obj<>endobj +1178 0 obj<>endobj +1179 0 obj<>endobj +1180 0 obj<>endobj +1181 0 obj<>endobj +1182 0 obj<>endobj +1183 0 obj<>endobj +1184 0 obj<>endobj +1185 0 obj<>endobj +1186 0 obj<>endobj +1187 0 obj<>endobj +1188 0 obj<>endobj +1189 0 obj<>endobj +1190 0 obj<>endobj +1191 0 obj<>endobj +1192 0 obj<>endobj +1193 0 obj<>endobj +1194 0 obj<>endobj +1195 0 obj<>endobj +1196 0 obj<>endobj +1197 0 obj<>endobj +1198 0 obj<>endobj +1199 0 obj<>endobj +1200 0 obj<>endobj +1201 0 obj<>endobj +1202 0 obj<>endobj +1203 0 obj<>endobj +1204 0 obj<>endobj +1205 0 obj<>endobj +1206 0 obj<>endobj +1207 0 obj<>endobj +1208 0 obj<>endobj +1209 0 obj<>endobj +1210 0 obj<>endobj +1211 0 obj<>endobj +1212 0 obj<>endobj +1213 0 obj<>endobj +1214 0 obj<>endobj +1215 0 obj<>endobj +1216 0 obj<>endobj +1217 0 obj<>endobj +1218 0 obj<>endobj +1219 0 obj<>endobj +1220 0 obj<>endobj +1221 0 obj<>endobj +1222 0 obj<>endobj +1223 0 obj<>endobj +1224 0 obj<>endobj +1225 0 obj<>endobj +1226 0 obj<>endobj +1227 0 obj<>endobj +1228 0 obj<>endobj +1229 0 obj<>endobj +1230 0 obj<>endobj +1231 0 obj<>endobj +1232 0 obj<>endobj +1233 0 obj<>endobj +1234 0 obj<>endobj +1235 0 obj<>endobj +1236 0 obj<>endobj +1237 0 obj<>endobj +1238 0 obj<>endobj +1239 0 obj<>endobj +1240 0 obj<>endobj +1241 0 obj<>endobj +1242 0 obj<>endobj +1243 0 obj<>endobj +1244 0 obj<>endobj +1245 0 obj<>endobj +1246 0 obj<>endobj +1247 0 obj<>endobj +1248 0 obj<>endobj +1249 0 obj<>endobj +1250 0 obj<>endobj +1251 0 obj<>endobj +1252 0 obj<>endobj +1253 0 obj<>endobj +1254 0 obj<>endobj +1255 0 obj<>endobj +1256 0 obj<>endobj +1257 0 obj<>endobj +1258 0 obj<>endobj +1259 0 obj<>endobj +1260 0 obj<>endobj +1261 0 obj<>endobj +1262 0 obj<>endobj +1263 0 obj<>endobj +1264 0 obj<>endobj +1265 0 obj<>endobj +1266 0 obj<>endobj +1267 0 obj<>endobj +1268 0 obj<>endobj +1269 0 obj<>endobj +1270 0 obj<>endobj +1271 0 obj<>endobj +1272 0 obj<>endobj +1273 0 obj<>endobj +1274 0 obj<>endobj +1275 0 obj<>endobj +1276 0 obj<>endobj +1277 0 obj<>endobj +1278 0 obj<>endobj +1279 0 obj<>endobj +1280 0 obj<>endobj +1281 0 obj<>endobj +1282 0 obj<>endobj +1283 0 obj<>endobj +1284 0 obj<>endobj +1285 0 obj<>endobj +1286 0 obj<>endobj +1287 0 obj<>endobj +1288 0 obj<>endobj +1289 0 obj<>endobj +1290 0 obj<>endobj +1291 0 obj<>endobj +1292 0 obj<>endobj +1293 0 obj<>endobj +1294 0 obj<>endobj +1295 0 obj<>endobj +1296 0 obj<>endobj +1297 0 obj<>endobj +1298 0 obj<>endobj +1299 0 obj<>endobj +1300 0 obj<>endobj +1301 0 obj<>endobj +1302 0 obj<>endobj +1303 0 obj<>endobj +1304 0 obj<>endobj +1305 0 obj<>endobj +1306 0 obj<>endobj +1307 0 obj<>endobj +1308 0 obj<>endobj +1309 0 obj<>endobj +1310 0 obj<>endobj +1311 0 obj<>endobj +1312 0 obj<>endobj +1313 0 obj<>endobj +1314 0 obj<>endobj +1315 0 obj<>endobj +1316 0 obj<>endobj +1317 0 obj<>endobj +1318 0 obj<>endobj +1319 0 obj<>endobj +1320 0 obj<>endobj +1321 0 obj<>endobj +1322 0 obj<>endobj +1323 0 obj<>endobj +1324 0 obj<>endobj +1325 0 obj<>endobj +1326 0 obj<>endobj +1327 0 obj<>endobj +1328 0 obj<>endobj +1329 0 obj<>endobj +1330 0 obj<>endobj +1331 0 obj<>endobj +1332 0 obj<>endobj +1333 0 obj<>endobj +1334 0 obj<>endobj +1335 0 obj<>endobj +1336 0 obj<>endobj +1337 0 obj<>endobj +1338 0 obj<>endobj +1339 0 obj<>endobj +1340 0 obj<>endobj +1341 0 obj<>endobj +1342 0 obj<>endobj +1343 0 obj<>endobj +1344 0 obj<>endobj +1345 0 obj<>endobj +1346 0 obj<>endobj +1347 0 obj<>endobj +1348 0 obj<>endobj +1349 0 obj<>endobj +1350 0 obj<>endobj +1351 0 obj<>endobj +1352 0 obj<>endobj +1353 0 obj<>endobj +1354 0 obj<>endobj +1355 0 obj<>endobj +1356 0 obj<>endobj +1357 0 obj<>endobj +1358 0 obj<>endobj +1359 0 obj<>endobj +1360 0 obj<>endobj +1361 0 obj<>endobj +1362 0 obj<>endobj +1363 0 obj<>endobj +1364 0 obj<>endobj +1365 0 obj<>endobj +1366 0 obj<>endobj +1367 0 obj<>endobj +1368 0 obj<>endobj +1369 0 obj<>endobj +1370 0 obj<>endobj +1371 0 obj<>endobj +1372 0 obj<>endobj +1373 0 obj<>endobj +1374 0 obj<>endobj +1375 0 obj<>endobj +1376 0 obj<>endobj +1377 0 obj<>endobj +1378 0 obj<>endobj +1379 0 obj<>endobj +1380 0 obj<>endobj -1639 0 obj<>/XObject<<>>>>>>endobj -1640 0 obj<>stream +1381 0 obj<>/XObject<<>>>>>>endobj +1382 0 obj<>stream x+2T0BCs#c3\..}7K#4K=3cS`g`NvurT(JM.QpO.M+I, r endstream endobj -1641 0 obj<>/XObject<<>>>>/Annots 60 0 R>>endobj -1642 0 obj<>stream -x[rG}W:U+syڒQjc'&w,$G;$c0KVR̙h4z'i2ƿiRgI^%h'IR-NvTJ&O\'u5\'iJ߰NrԠӺP8̹a*4,+PCIUӀ9HVԩ*GyR1N(s$7, -a #\'mysf I.VTY3IQCQ4s}HY%qӤd@!T=V@_A]j;IC&2AL3ma##=[[V$;A+neF2`Q N-S RLC*1M(O:am*ڱ1@N(r)qH-l:,fK @:iN M"=nڎulб`뜤 2$3d`\fBIQ -9.[`` - \(9ٌShHޕgjg!wl'm1،1XD9?+QDN``H.BaJzLdRc[2: PX!L:+d[ LsPQ2ZEE0a-y]0 b$ MYn`\Þ=F`G״g%Xʪ2a" m4M is(s1qqKڐ1XǢ~, m#^J/%& d4%nRj얁u4s%iˆ7OA蕢qBw & -1@z )Ϭ`: :4c%#ulZYy CWhYϼ4@pe8dؘM0pJ_$G m`1Xmhrm&uX堭`f0+BzvlKt>zյ``cFz [۠g6=ݭsfՔ& P9Á1%=w1dm -!"V/u(+`E9% SWcX-Eo0aEurfcY y+(J PA#ǒ`84KTN{O \` xZ9?!v1iVc6h0Xzv,'qt0k+'XҺJE +ֳ`Y+9r= c* )Ej;6 [#-%!Ј 80c;6a59H``#hTT) pt8M+E '*s\0pXoh g!Fz Isc@r#{x`T9RH[cH1%̌~cyJi#N"'S08%c,beh,ۛД#81v#=&Я2$V- "2p-/DXcO${} g -/20 -q 39y%%"J F aBC%!"9)om/*sv@g\K9H<⬗S.zvB `$vrCm:p/g|i ".' TS[ (FQU N8$\ -)3l։&3d b"J2 A[W raN]b0NP V':X`R.( IMK8cӦy"i"DApHi\'^b'k,*E2+GGp RpQH&|XnHlD|ޥfj `)hJ5C)2NRbJ_胳7ՒlHr~1$xz*fLe;J9gfF>${ qP7h沎 c}4 -CD#cBpE" M(C6i* QKs&nSXR9N` =??ȄH{=,[nulj?TC/=~m-[l`r`uxwAAΨg/jOwwKs{~_^'/qCԔFbGVDA# L )o+\$t} ` z xۮPR槗^G֏'9d;I p|~B;HJkN~w"*U~s^T@s7m\HDi(yчMBtLM9YP .Xld1mJb*ReIiPijj[}:J5 D;ʣgE;R 6|9[|}8 -8.yƟ~]Vа^KI&C-~}og RTz^_RO endstream -endobj -1643 0 obj<>/XObject<<>>>>/Annots 103 0 R>>endobj -1644 0 obj<>stream -x\rG}+:}ޗ eؒ}F#{.x42dVU!vMuɬ̬<*+ͦG(뗟I=^fU?*"Xd.&pYWԎ2+j@2ۍ2At; -d:ѰG-ݠ)cbq[`nT1Kxy=e lV`Yb`9j"2 S_TNՐԠwZ#CJr0خ62hèlIU|fیEP7\˲7dK8,Km, ˲Pe =KlcI zh{FeP#zE!qTޖ0T -ޖ1تƢKXfU 6M6d^ -1t"ht=}Q8 +6 47p}'u\\EWD)Tu $d%Ns1zVz'0V X`2i:%Qx֪9#ƹ/ -G {"uT׸n - L>dkAtub1ض@4 ; cGPːFe> GU40[k+Upq @UcKs ;G]tAi1 LǛ+tnhBie$ct,,aT⟳aJ2I\pHVsp0ذƆAIm+^#KX$8]هJ2`PSL`eD?S(a}N29?% +'0XD{[` XˆaHx5JL( 陓ENt%mHC? -֕MHCC0r1q0Fb -XP/| -akՕ -|‘+igA I")cLXb+jI֖1X qÒŰo뙱ؙhX`1Vj(ːj @H($/t1X#M!KX8b,a{X R9 п1aD",aEСe’8&CA.㰝0+I`A+B򋐂$ĭL!џo!մY5^zvw42!0JJhn"k#L[cE"!8$v qe$Ŷ> * $V^S;Hs9m8릠؎0IPׂ p:*è]Z;+P4Ρ.cA\9U%p2C6#ӰcnG&Q!@e1BPڟq!mB8ЌSD!ȲR]F-.2-Pt -p($ 8!92kD!*6OQ'3!8Gs!FCs!(-D$*# -pyKUiG08cHT,EPT,~Cp}iEz04!pIӳG_H&]hfrsgwYȎ׫lohVGСQ)~<0m@j$$_/;pͮbYNJ^]jp>NM.gaplapqK$CIiMVVI_={B:,/,L17ҵD -tZmѣntW|T^wA4(ϯ]⳻S*Fa!Vx3M]HU|NPQa;ͻBt& -+* -0.k=8ALq1#V.Ke'֛s.D{\9l5|F09ׅ"S7JXǁoB,;5II0e -*86-OmJ%[WGj&My(٭z[9dو!y[N -@ҏUvY?'VAhB\T/_Pc|>xwqcBovX>QwG.2#) .]hloy_U -&uEN.^X(1dVt3, A<%1|:sIUy4R"M?YW{8I^TXrЮDO'oPat?3S'3Je0ڇgSJ806*K|Jȑ#vmd204)Y=lsu%4T=9e$q|(zJ!)";^S)_ܩJm0,rh=HݫpOO&fxW޳pU0( 8%(mEGd7J?{uX|A&ǭyoqZ+G%.Uwd?jbdN 5\lWx+26i_l(/{?l}v-xIP\e}a٩o6>G]jm,_ع˨ۻ?%>$on#u֕O(ʦ:Rݍ+&H $ҷd'^z|\{@U#u3uL3A?x+RK7z}w_Hmq`}~^uM%L [`H+5w7"]u|)ƹnPqVlP+}j͔(y E2 eAaK]ޣߐp0`m~?c{I})oGbiBLC*a~yKQ7+c2?ןY|Pq7S[0. \Ž-328P'~MBSF -')$!gRNо0[zvzhu<;NJ,o5U|aq6Q𝛹Ű㐟d_6|} -YK[= ]OC)LmYLxgt|"R!Հn Y.n)r%J`M¦dOˇi'{-i5=~Owo|ݝ>9yDͦzzp#9M^UQOe|.{~Gendstream -endobj -1645 0 obj<>/XObject<<>>>>/Annots 145 0 R>>endobj -1646 0 obj<>stream -x[MsW!@R)Jl1QR9 HuL[>!ۮ03===ݽ>˳!ͳ:. C|cMVZw `yFpUGpAA.2[ﰄY׃&f Y$غx,ah:쳌V#1RYE֌S F"uŠ%1XS3KX U*21c1T9hx,aM_0LQb(1تI- -|UFm@CH`VY`˱Y`\,aj>+_5Ԉ~ٝ#}94m s!鰶u r^}bAK^ԅ]8Š**A28GP-a&'26mT.}l:q -(p"$0 dd(FHl*c@HREn,24 h$K:K8zĨx4$.%9XU<24 WzFGpsbFbIf8yCʼnX}e \3 2,YƆ%z -|ZyC$R)Joihp`iH448G:hdpa0XhT0KXH}}frm4gղ#\[e7nD^pEU {N2N,ajk3Ubg re h UqX@)pU#s ANs jy1X\5g F"(,a(:T3,Y; ph@@pժqEl2gF&SF.xKB D+`!(Dz>1غ賄X?#2;j,az3̌aB΋"Fe5`j"Axs*biI$c1>1Vb5_2HB,a1ob 9LZX`(`D3T0"D XM1rpiAXnvH6P 0XB웳("cwl% Rq̌fg6#Z@("cIcÒ($4(s+%#0-id\2Q`B g cl#~8 Dp<.@%iR8Xaцe'6q61-X5nҜ>3nLr] + dq5Lyׯ6ltKzTEj>)DmWaAO2WA)PY8 -7 Wp6I@|W\M:`wM~M'ۙP.;QM8fqu?l_˯qGM2M7YEM+S e\U}{y9C|p)߷S__LsՍ,wH`8dz 1 -F VQ }U>y:jIn{;zVSQK7^A&P O-fppjEͶU.ё4 tz3ۆ^Ճ)L 卬kkeOpg϶翬*Uq]zҎtgW×Y k%u}lVG]c_](6v|6)ƙbcSqDny_ -DĜCZ$FdF:OLl@*ֻ*^mg~O[PAKG۠gJgq~kWz m,~Q7ALT/e_U}WHCku-=[Oח27 -LOY={<(hq[$AoSg 0XDEj2ޝWd8J3ԫ6``ۻs ̦n[Z5r,6yU!O:蕺?>t?B 5[^,3GP'y2}XOj)js>+WH7@wH\iF>NVj)Mjprt+<-.fE&~\_td.8׫zyBSVÜNoC4CU:$Qfm hU|N>QkС0)u)Iv1JJanU}\ -Tns~~fGl퍊{Z#/a6qxCihd&mw9L:XDbluaWL*{ ҺPKQM⎲ Ma m3_:Z>U>Es9rB}T$=\z7w6pF7jm'W/^ȱr*+l];pV?Ekm`SoKЊ8$T{32L tY,|/2x!?{6,T*Gߊy.xwPݙ;n~M  ֱ'oPHhf3^ۺ+fe7Y9p78;bA3`8L bz ]d1{p~բQ+g]:d]wW{%;}UwF?ջy}3ǽ1eQ:'֫ x邼(9'H?c$ԥ\Ly"Xwgn<߯[:VXM%9 wިѝOBTgQI}z/rF/1nǯ)*[1^rH9v[n^G0MG^lq-ޤS#՝ufqB0=]6tp(QLYg2͂"m>X,\!AZ:Il8Oַ Ag,|HDL}<pWH#c;ns=Y@ޏkUR~6u1꠿5ڪ)g;iN- ;2n5 +FX5xuS>R$!dNIdfr{F VS}=T]d uUfχTQ<: mBeoaV'|o&*Ծڶ̲<=*#~B(*Go3DsFz{y&1 -w4B>Y!݌OJʟ#zOOr޳otI;ճ~=5|n90z/&^ @?%vtXzMnM8iW䩰PWx?Uߙ%z_ho9)hhegύm?J䄕Ͱ˺峿=?endstream -endobj -1647 0 obj<>/XObject<<>>>>/Annots 190 0 R>>endobj -1648 0 obj<>stream -x[r}W]@{tϥLLN\<8;3===__eIgI'ELq_>_eRt́EreRUp.W3pdE;n Y\-lq4l\R9ā0yԁ-$2JX]4 _T@\qYB:SF`RL6b]EXj,V\x&c"H5lbQ k0-flYÌq4"i1D+xa M&X "]tJ@qN@ZD$NLc;:LdUGEr\#i1ša`E"J@\q:ŘV4N[ƁidԥV̗i*@"'aN!SCqbb8 {`Yb*$@ ̸%ԁM#F'ā˲_bNbوV t1ԥl0Ǫ5T@qmKgp/BڐEfk-k0X@iYXUʰ[^Qǩ3K2ma#2<5ʔC`*#fl Z q`b() -&8bfl/R2nd-a-WМˤxp CC!793i%Pf5Ord 5*n& T7X=FlbǰS`Rk1ؼk1XD *5,N]WE"K:%e 2) HZ VjB 뇉-!k®+) (9n5*n>H@*CwTnlX6P5,ͲCpfXIEKGpդ -,՘XZ+ɖqg R@ZL+p VȪ@$B@q#g &EZ&, ZLX`6HD;.Xla V{dFtݚYZ@ HIa*Ra&E5jk0Xd~Yyewk1ؒ>,j -ؖ H@ZBȪݼA ; XZmglˬǪ:1~:`,HNYY6,1X!Rt-,k -(- 3U#YbI sa rs`ak`q-iEQY`CHV*(3˖2!) `^!y eWzqӫ>bwBāC8Þ@X|kHV$+R%%hz8$I :jLojQAHM8>bPD.&b@Z0t\f8b&,"e<"DbCSEQ蔆" Y Ml0/ObQ1`iXbX]dlfQDZfk -ƴ'5X;581XDcQx<`%`zk0cU`` 7ӰM )sHd(jHVNwkRz$؝1``0VuE@qZE"ac. J,t01&2FG.Bp ߁{4IAٙ&  1R?\zOn!!*)ؔՍ&׋Y&ovnGܰQa߽^mglܘ>XW?-B[C2r]}&r,0#q&L[mn+΀T&$WXg׻;gxtfyeqxs={lRv;}6( *D62F"9ܷ&;_ɬpָ<$F~ŦMzz_ζ \^pF85Nwdu#V<f~՜(zY۠?Ձ_;S#j'~'C`a~8_8cTt׿Cv=Y83rlFats\ޓTkhaYp"/r?Ȇ 'čqu ITԺ8=qDZhQڄpU;_X9p@`nli"]VejNUc7/.@JC1ٗ )iNKiJmr1pNArP11TQ 'ȏv~C%#e -Ntht64 KnuTh!5*17"HF1FhKF 7Ǔg -Xֈʯ(nK_\ݯi7CrUFϫlMKFI o`" n-1gL8]c6{5~σ"7ˇw|-x2?1InP1!928Etۣw -[j% OnkV1*|mZSC9^.<[XFs1+]xZMb -cEVf.ZM(Oњ1Χ -R\G_&4\Ҕ .$?ŗãaq\m$Ѫ2GU8;\ -e^xFO©n=G%j$A@9j/paBv/Z[my`t ]F[P/a% 2Pz;_F\;{שB -v-|ZA;dcBIMz 1WJFu Ηsaמ \jvVͭ#Qar KZ2d%+["*^",Ý\ -wF_?A *'_(thǍT{AI6#VF%ʧKTt~:5w_qvT2U {%pհ >NA_ ?º'u8q)n%w ZT0A_Mw324]T>5/>AMypd: m.OyƧ$y~>w+|?M+ۅ/c0[[1b0K{[ 3h`,ZPW"hoR - --*h(l،A#;@f[T]]7O0h8I9 >r=KtzA7)O׋9A-֡;wrbW:@6GEAh)ͧSEEr*tzŠO<|U(f|fa? {gw ogEOOaC (Lj2|'ndzj6}Vy?:s{w.\ϢGE2" 7/jluv?} W"kIXT?eiq_Z~¯fgNu^.뽲t~r*W5!/J"'D1!;{aW8W<'L obL*Xr&9; -6ttի?tendstream -endobj -1649 0 obj<>/XObject<<>>>>/Annots 234 0 R>>endobj -1650 0 obj<>stream -x[r7}WcA/ΦjZ;m%3KQI9tTؒT%=9eͯ>}|gy^Mڞ4t=]Wl\m&*-MT@oL!Nt+(( u.7lYS>Li};9r ]|l6ߊ1C^z\cE .nƹ)R/n=/5 Eh#E,R7S}㲃:b E_x30y+Ӊ\4OyK9ee2 -HfI%Qw͝;wb׏{~㢔Yn;iҳ7Rڨ5wz0υL2VM oX3H5HSWeU -X}O(uEH.'1+Ec~dŕׯ5&q@A~3徖H!iA gt]{TWtf-}<ϗa$ `UDR+Ao+Zn\zLTh5 -'fV~A 53VvSueGN -h=b+K]>zlEP{;= BTهNR(g0x);?u7!_։9.BתBA5u:qjK{nOLN}>\DpR%)z#fI+zOи̥U)~1 4cƍsߢM;qY;9ܶ윓?0zỺ1JOqNK9nhLfĪIjR| n^ (ڛ?o/w5Xmw&?j)[YނDܳHtl]rNy D#H Yr~=[]ś8Z'l %)W"$K%wg -T)X9Q&qqFJ>KO -񇽾蓢%]\5 >g|lfwqߦ]>/"|Wf!endstream -endobj -1651 0 obj<>/XObject<<>>>>/Annots 278 0 R>>endobj -1652 0 obj<>stream -x[v7+z1B^cLdg,enQTX$5|PUM*&cs|x6zPZ}gcgmM6]x|O"+QuvEVףq.|\ -Gz hGgtÎ+ -T֣ H(6;Maâ@ovt<ҩi$I5x dPdܡID *E.Qfúk`0myO=iy{g8ª.>[.v׳8vF9d(*`R* eEj9HG=X)6_Eg ``Kg LڨjQ fכ:G$FHJ@Ko~3 G\Jci}THK hE>@~⪃@fwvYf6=&Mtڬ.|Y$|]w9lmv4[b8m-dD\ԩz&qZ;_QܕM -~q.ұމls_8;o5ѐtƾ[Bt;_-%]'Y~>[Q#X0#|چ[t51欋wX~^)w"Kﲟˋgq)ʟIaj)(Gc+:X,*Ix!<:g?Tq0U@JP}/T -GYze_dY#qz[fJf\]Z\=~*}M{Z6O/0۷sĘ^?mWtL/x_rїl./Cf\kv4]-/idϦU PP^v^%c$yWRKl0էW*9. yU{\̗љ$^&w,A6aVMcӖ1'$<N^JR"2DKwNi[n6Pܙ?_Lf|98ƾ]*~݇3QW/ce-MwΘyܠXL n* նNǑ ESp[߼"Xgէ DܑljI7~^.(Ġi{>u.~KDWwJ! -}UYnCrn|1&6$WvL#ZV\ !cmxxg^_D~olG6Ȉnb*ܫNrS2ʻvfM.:;Փ+3$ݪY=N~Xp'{^Ec+bܕ0PPJYk.鹞R0;|q;G#բON˫5A:n%Km8/VqK2U+;D Җ_#w|{?~=.6-_ 3|:ۦ;>wH <ب޹ m5iIBDAg5$vG:҇_`N'u))xYt &:wD׻;XkoWi:mFb3+ꀅVbl7>XµdY8 9} jnh`;4X-cu@1N$hOip_'|/)q$؍ q:<a໰*N[rc<4UOvM&glFl^SyuN~j-D(]t6ݭNwiiu \bӍnunJeK k\m#wn"Gm;o3cڼ4KWYR^G%d p=Ǿp;SÚ!_adzsܘȔ`Z|Onz8nyrwWR$z9Upp%S/fM|ч/?~?2ٟCEJ8󷫟>:Շ^Ekެ7qo&xTܿ<燏>jq1?tOW}H8M -snNU|feD?cl#Uo4oXug!f Y 5G] TǗ\'c1*xv?ɒeGd|q K`ެ!Ý{^.y<Ȩo_^<{«endstream -endobj -1653 0 obj<>/XObject<<>>>>/Annots 322 0 R>>endobj -1654 0 obj<>stream -x[MsGWѩZќiKױXk)=2F$"G!);_@7![[l\͛F7n4=YL/M,ɫdx6LDzT _$i&9}"&ux8ne -$M*D9H"M'7s1l:il3EUŨ[6ͨߜ;&P6+2P&v9ccRfJӦF嬚dPSh8-2#=!.ulUc&8aR - [ؐT*1b`ʊ؊fE.hǪil[ԩ)Mz'4pitgEH20K1ˤTceElN}20 &Qc2QN5aҥ&)+s74p%=XHmJʱcbJږHJ#U84 zR7c9۱ҳ.\[2߱CSv([[VE][@h9^_$A (mH%=&UIY,`RQĝRh(qu - A޴eaf aҔc -&@$ )@۵qa} =v!g[9H -Lrߟ={ -49u]%ϟndL[nߝVHRju@D=?ׄxYMxvˋY3&PC_JAvӭڊbY -6'gE|x@O`,tvJ:6lڝ~q& -;XK[oVcL(|nl[92Rq{FUlGl[l,'4{յ̄s ʣ.wT5_}$!TTt&:&xuϜ'<ĺ.iYm93cwz>QXeaqۮȇG~bi:6$ht⓵?eS4IuսZݸFg8Ok oqc3vқw#mltzQ l$ǁh|_YhIEe(N':I:z/8IRLU|ovOwӬ| 3@B8֤Z !HU&>óO<^/t57G:l\Yus|v LS`l7]t26Ƨ쑲ϨjhT.KB /7ԭ3&,=ϠFZY/b -\ZӫDGg]]-]t3â+.^ΏNC7"[|X98>&U1p58Vl+I: ysнOk| -G)Tvakovotxrx_5})(ClFu!|7(m~\}xcM99:~uXKd2Z*i`\Gs4wa>AA_|/kF>6o&q -{e'(Œn/$n\av+C:MoDsݜJ̇e[Vv2zX˧TOxguL !d[QB uH"[.ex.Fe^E_&(V3|KQֱ[&0ޢF Bn21}R[z|9He̓7ze_l+&.Ut}0لlIWgQ?"MjoD/^oK.wJ "3y98'f9}mz:>= ٳ>/Znendstream -endobj -1655 0 obj<>/XObject<<>>>>/Annots 352 0 R>>endobj -1656 0 obj<>stream -xZKsW΁o%%ƇiK -ʵ>_Lg^(4hHOBO2o6ʚ8.FESp5I\+NmdSEj kiIdb6M\ - FuN2yE H5-*(M2Q`5qX+Rb9/q&<*1D -- AX!IHZyH3IN1ٰ*L64dC0غά0NsR'JhJQX@+i"7ԘJv:|~Z24ӦM+` vV` -*Va EV3 $p-U,VP䤄К<@8d ـ'q -"s$L$Y 6h k͓%*Ly)HɱфlQ"n0 DT - jLvMZsl?q&7d\F)9*@ dlRcH_]1!#MU$lcrʁ=gBjER*lEHkDYa8,Ь` ʮj`KJtZSTo'k -b -ǡeQ8)H@jL`eˑ3.[s!+.W9l$dߊ|#°VcɦXs@Z 3 :ۭS,HIHfT0؂6b&C䓙Jc@8H3UlñX(g2r㨆#1 -r -[M6a9KYL"QTp9rc1X4.@\s, mt p\8JfiX%kghJBY@Z3MX+]@q8 - 1|!aݐ?-I a MZBIB2Q@&uD- &M1N -cN-c :ζBjLXU. -5$`Ka k5 -$f ;I)zǠ4LAqHqU= dY&,jZ6I h9Bځ8c d(zRdjzM@ǡ 5EH4 ~a dRASL/rԘ,GUL'#|uF:wcQQ37lҰ7h0&Y}@r~]{!حzN~3ѢӛϟUvND̃&묂,q M^NCu0DU25)J{?8A{(vxzt"ǯT-2ZLO[Y5t;N --*O0FNɎ4}1d %ljʼnJ"YϷ"Jk2qծȯ"ZS~ j;DAz֭_ݪn=|SS\$n^q_TCP.|Q4IV~_޵cƍT5.Roݻ)=sNlC:-IrtqxoY{~:RzA=GNJ!3ߎ=в>tn`\_H`qA ^8o8*ꗟ4nbrpryfY$~;KUDw0(uG|ٯl: -qQiM~;6.p ~qƘ߱ ϻqW;WJ;۞^_S"%<oZT<YhW53ӒS):Z 2񱇖5 3ֆ¿RzmH)@}r=!z2t-ׇy=똪gizV`>MׇnA|)\wе gg -d.Ai׫ʧi{".QC_a?ԍۆ܏.~T?<<ĒW)ugh҅ N={7.78qFOyvj-Sa/Ru8w"`*nΒtg_=OݮW'!` [j8vtXĥ3߈^;EːxON\w+Vvk3 >& >Lbfͣڰ_[r.q/-LW^d75TDžK`:i4v>oʬY }PVuĤ .&׳c~ow 6hꚻpΧ-ţ|Bw|V;4@3Q}-o% - wx|o8EaO,h]kͪ#6qCendstream -endobj -1657 0 obj<>/XObject<<>>>>/Annots 385 0 R>>endobj -1658 0 obj<>stream -xXrF}WK* -553J%2 (B 96})dR><}yQ"ǔ(/ 77`Fh,(:TъOŜT1$ 4CgE2N)d:*FAB9.c)%a,SZ2 -ִ\RK16c-`9k/!9`c֮XNCX"ȥb`J|s )_Y=`KJ -'fkv@> 10 \tMhDTah$߳ -&lֳ -]lֳ -#YGd5;KϼRdmn"$\A*ܑEe*a* fQ>* 0kױs)wc˧Q)al0XV1;{J*'g5;㵯X|wxVcfgOUdR’qķN$cسȔggY9ZS^Vcp -r5.{Va3VaL31XlZdSͫs1iHI"T[l)+'&_t}+/Hj0Wh5`T`|)Va1cYc+X6>G\\Ygv.{ֺAV`R(gf3nG$@(g\xVacr`C --ƜetYax4iK՘svII]IHKɡcׄ(Sop-1T8N|.PR=,&|qyCpF/5a{_A6%yzʼnʘ].cɬGӑxe& LOʝFɟe_list'FcxՑ?}Ci]o3>U緗?U]m)ϸͪ-}¡=~em_~$ mP}ƘτόrSU@fGzG[-2_J/Xdmΰ%;v44[kD2-9pPl3lεt=Ys'XN YC?%eÏK3!DɞwV==TE7Y_tgΫ1ɭ -YOc}ՓnKqe.7L}G((۹R-4 'Ը MDξoخ55 =l_n-7to sf=nwSa6ht~߆2LZu6Mּt= ?f8xi(Pe/) f4YlH;&zo[c[*s$tw/Љ|kg7%^Ԧ/ir iaK6ӶV*,hulrv)F}[ -H5 6cLК]늛iRB,y@wL5Esߞn+]_jgI,l~E/6}kU v; -Eŋ=F'{b ª$\ -[boxږu_b~Ɔ?)~*Y,R>/XObject<<>>>>/Annots 439 0 R>>endobj -1660 0 obj<>stream -xZ]sF|ׯ܃hIJ*r9s+DBbP@Ўu ɕsJVw>wvfϋ,L/ <aN$Njâ\La,vL.Iid9_M$b - C,$g<, ̦,,fpf9C1s359bj2 Cn0a: -;] ҥzs4kf C(&Ke].(k9 :2y],౰БXW0lg\!Q<96uY8bi}(WHRŸ9M'R12C*΋XŐ7gh;Qb3IS썰=I#Y$m]=67p< )I`< +l'Y`%CM`3]",O`9+-;9 favG0r=Lf!4DQ'440*aB8IV0™'V1X"eͩ?XŎ)0̐ -a)&LX܁)'î 3NW'͊ه#͊ΗH - ;3a=U»"4 -fYIV1XTV0E^)fوD`Ipy+dܿ! W0*? -f̩8 -d!p v -F@bK\Ҭ,آhW1kW*fƲ9'rg!֩crbt㽟LV0؂mJX`q;B@IV0YT6a - lIzl\c;e.5a(L Y'R1XڢbY?q $ YIlh]12YWldf uʼnug6J"!>_xW2Ÿ/abm&V0v՚jbݬp!ߐL9[ab -S5ɑG0DѮg - ʺbԣo<rCTl%[: '\‰f' 5-X$"aSeEJe3NVh̳z0B4SSS' +,.Z H0Y,5* 7z,R:狈 % jȳ0X+)y$+,j Hveq+`=QV1%o W{p 0Z \,V -/ - -dXT Gb*ab#LBTjd3K +,۪Y1Xm+D5Oᨕgd%#rZcp$+$Y`q++.%UDTbhgCH14h"*Ϗ_Yd, /a3|)$`xPV0RɈvE']bn/nɮbW UѮ'xdF@8n(<Ⱥb\"!Q<(G+ -FfUF֝`'#!,}R3`ҘX`'5a%V1Z%֝;dL f.4X`k9aͳV1XjԮb <*׾ꕇ_-xx$܁+8X,{/cYK`U rME-Zezѐ+,OI 8ɚb\Axpe˃N w5e,V֮ Pʨ.l ݯxI`>&csc Gά6bm;d|'EM*[@{x+ ;~(aafo_c4\ZD->^LOo>|9 O7?('kv]hǾi`q]1 }}؀>uԝI_.&᦯pku\v)q`bOv_5p]o.-uoCߵ]ݙ6uUnj6C5S_ z4Pu.SigUcuWyjM__jiNƷ[|aEJ`䮹LJ? 9cFo j`؇?ms7g}kV\%gѵzZu]YV#=T}hxc }EqX3mW!M4d=+͎f18ӑ Ay iTy#^䃧 ԇf'.G,Gu nhPwLJƪE kQY]6][L TumnYއp{2;maW} W)zD=˪-G8o'C܏wKiZfaݜۮƑB<]=YfszkwF>imCx5nb65=6/O7lͯnGi?)s\~}1j#bsݫ^i/w/p=-9#xGSendstream -endobj -1661 0 obj<>/XObject<<>>>>/Annots 492 0 R>>endobj -1662 0 obj<>stream -x[sF+ѩZQ$ DUQJ>"! Ihyg6U}.FaFaVr`/韏?^ǃaVS]d4z -=9+Qp0 SC"GrPxt0rǰh0ð;642[eƐ=-ǃgsœe&r9ɉrĻ,]Oq&lȹ|d˩gad$Rga*|8fd1t4ga\ϬPXa91ga9Ya cCa:aX<;6*GH ƆLðt -guXT$6*.50XؐD#Yh{I!vʒ8WE`">OzSHLOYRh}D"㪟X[20G*Cf=k{wðD&s90,ƞ5a:NmStKC&IcUNX1˥W9Y]9/Wd dA2 HS"=DZ2lծAH;IİQuh9UevCsPc=hgi5 K0<,qm46m<,manK=P }>lsWMq?M O6\_>p>^w(݇mwx~ ݲ9.av?]/>|p./lwAnv͖ڝ(Suyww ff]Xfߝ8톇wٮMME.oܷ^n^Jc<- ]4=*(sIoվ\/uyyX>fn/-F-,ܮ[ fa {@UvaQo«N?TKYzim^(EOnny a]4F;eguԮzb>OsمG\l/Aÿ DPG/'ѥ0wm8 O|||\~ڥ.H9{ }MO~Ίu*}ZՖqloJ"ܗb3lB,V"˓`2{oMyntYXcLa9/ if{>6nmڱUޚolpr[? ;U'ѨI훵 n.XoW0e[? jok^'i)Mc߽Gogȑ&AR{/Ծ{U -G{ !NMTVwX38LIjn -ÎkgzҾI!*z`^񌓱y} < ~+ۆ {\}#"i+KҮ\jcH$й-o[U%Þ1w=-ȻO -p'#'_Ú[[Xh‘"t 6Ny -PەӬvחfk8wjmn=Oml#`mo#,6w󲳒A~V;m&mIU[lS:b^njZg^|RfUT,5 [ Eѭǯi+ދ9 -vw׷_o$[t)_x㗳x~_{joݥ,׋XMendstream -endobj -1663 0 obj<>/XObject<<>>>>/Annots 544 0 R>>endobj -1664 0 obj<>stream -xYrV+z,M`JIHBL4smJR~M?,(|<|J?wDhK &Z`y4Uų˜bAF/ԱC1K-k ê$ 50+9U8b |Jk0|SidUq!{8XA`q5|*k0̛YY٩5S!9%85c Y)Ա%\N%^BNbee$WJJ&ȸi2Ŭ> }D/K0 \A0CĨ+Աj5G?TiM/0$zeU k0c>ZŝhEppcIrΥl@ , k0˵kd af_.8! 48r|k#'b˒ۀw]" vGTc%|eI!BDg Tl|95D88!9.m9QB@\\8\$AЬqyEI-7]O?/UJ\q%` >z'=uQحӑGMږ;jʶޟbm ݫ}ٵge9:݂Z^6q8 /|r\lbow,s9LMݬ1u5J^Jm{G7#zW?+Xǎ/ج)nKIىkömbݟė~qr}lإp''kzs\w<=C/5ZmC芦+7 -=/ǻO#5ס398fWר=:G]׻CTm?8x^+;;GP_bCm4<DaZ?Ӷ^j$v`57,ᱩ0 e9 U?:?{QQaPL3 xU:}c-燯g֯﹫N#7}>p>6?~7ݪAu;F+U3+3͂.W6G {W/ñv1Duq=V ^WBac|{nlj,B'~̳s}o8͂pCFypnIxȇ_刟/<ۏWэ[w($z|rKcƬ_ˋ_Mendstream -endobj -1665 0 obj<>/XObject<<>>>>/Annots 562 0 R>>endobj -1666 0 obj<>stream -xrF|>:,!UG,4G4%\b?3PPjwq]VE%F1TQ v -{**MaO&IDUT( eQcjVP+*)1UPS)oq5C(WO-ŜU)ۨҪbe)[dB40G*U1glCEKQlPc6 -ڶ>),wR.I[i+6`M!b1Wf3Tq1<\zEBJK 'bMsTaPɓ7 x*vܽd:[OؼCO/-#5cn;GۿpF>N6g:]MNS[lu_Y%vxѬg1D˙]\{H#گmw8طC=n~#XartNx?r&͝G~>'P2Yqx>MuGp?, PGw>P\'AtX".4grqYQji4T^ǵ}UW!6 iya/QNKyܞWY'yyC]GT6]OVx<;Q:?\DZY{7,6!g q 3<_2ï%9߻=endstream -endobj -1667 0 obj<>/XObject<<>>>>>>endobj -1668 0 obj<>stream +1383 0 obj<>/XObject<<>>>>/Annots 59 0 R>>endobj +1384 0 obj<>stream +x[ے}W-rUn劤Xd_%H`9=3 lk/I3螾LO'..$+t2/~_2oM5ʃurMR#M +7)&͊IIb@4 \ +auŤ^Ni-[ʊB~r"C +IGV%y`Lix80p$]()JV^3ЁkrJʤeΎ!0I= #g &ͧ#R&EdR:($Ŵ+f.y@\Sq.@yιs$w4dhc PMRSt+g w TIeŃl$Y `%)3MN)S)˓մf~y \8~8@i?!lHZL9,a ۤieEʩ3*$FIDEn3i @HZLR1RbUFFՙ `[y/2P='", $!ezkU"g :J$- {â Y'IY0'Y%i@$k3Ѕh9!.f8z$-&Us2-5lM۟a 26xeEoq2DWƏtyIP`-8.5aQ`RYn{-یg_3[ fXJTXQL3c HVq  + DΧbdC-oXN)^Me$%55QbeeR +IN9K!m$iJyy@ {rqOB DZ  (Y69ό578Tb)dX53elIfXv?x҇E@pEERN!8 SrsꃟŠ i @L ,3ǧr +x)w計f)r9s⿣ 7G r,: 3"ajzHo 30|9 2#1 {1{{ldv0q'%l~n*ywmQG==sz_ƏɿvqX~`nwRdBNNˣzح +h|9Wz=f|CPuktVOz,0^iÄ~FrVy]߯~%},o_D-:?7F(*8ُHF{ 0' l&!W~hzmd!~yS; _~UI'Ӳ:;od#J^=2Ŀ8acM~h;R{`yEU:<&x(I3nEHyE|8+bF#zߢ*y'|́<s$ڳu@@N6E*/>^-w/W9uf -6(}[! +-C=> +-ڤF +Ynv n +>u=Nh3=tBqSVȡ52TqrEigwt^CâecU;/*ѽHP׷+о%@W}DDyU$MJ5y.Zl] (!.ݟ| ӏg'|Rĉ]$Z4VsI(5vˇ\nm-P@$JNonV5{/WfyeGXx[d\mq~27nظ {jUJp-^Q9<2hO[ޟ5B%WG -Gg{ +ߟ?KW 9kw KvwlEs4Б" l37f\T!6p +').&lW臏 P^"^}Fl!jvE˩7o^E(Nhj$۸/> [Q6\AD?WZ܉Uˡ߲FV<_v-;'bNj kh͋+OOKM[~ܸH3_WK2dO5g[è~~wUQiԁG?TBO#/I} Dv|H̩JtQ!t4-ue 2>6/(l5zfhex_Iy}~W}NF~ 7aVuWq7pQJ%2Cw<M +![0xj&r;wEqWw\D5pgGԷ_6`;-(zm~ 9D8iUF K|/'ͻs'iAWgx〠1Z BڠNU(l2FtG,΅mܳN+8BNx;ˠE R;{{~ƞ/bTBG%G!Zfh7yސc{;~ѯi +ˎo9>hg@DA66Jj΅ӹ?P~I3|o=xGwHż!k7ɂK5u&$kF/G{^l ~h7{\,G {*[Sc팳a0`ӝx(tpБ~ͥ-ޡP^/>̝To*bO:wDNJϗZå}Y=Qz-/!-sk3Q<ޭ]ߝZQvSqW/N2FIf)lA2}ZvZQ0VXC"$ᓮZrIZ+$\+X^Ϟq1endstream +endobj +1385 0 obj<>/XObject<<>>>>/Annots 103 0 R>>endobj +1386 0 obj<>stream +x[rG}WL*2sᐏegK1E[LxQH*> (gXUt7Fh(PtUQOA9.KK1if纨g8yhԍsp]i ũ[ ո8%qY9eQC欪$)&ITr6n86.rӆBG& rNsi ֲ80:p2@60rͤǐBf: vVS6M \/L&sӘn tؖ-#c=ۊXf846Vթ\:LȅpLzL/0Ց-6a$1flXt `P(TdQ=e:tO k\$`ss-d:;R zBՕ)jUqR) +<)Fz }0 cbHj,Gˉd'nʔf ,br"A0h.ؒCd +Ĥdd5sudd S,i=K +8j&٣)<SVA1XֱawV+qN9.pN8 9(q[ RҐ0%miMġgU*orhCdOs4S&! D8c ++C=lYK9VD b`Y1Xxeqբ[4rp`&= E2a?hJ-9v\UhzRA^4qzTӢwC=+{j.*󩶰E#P+P2ԔĆzLMӱeLw81|qr s0O|q!T=<6c ܱ6B#Wz g: x b$6嘑S6piNM92 R0#F.̤ǐ&<: eYXJv0/ g'2,ndp7jRACLmC.ytqpjg2gC8T:y=a8 R.\#˿L92 8499PqT6N@!w@d)"SBH489 9skqs3' +ht}W4c! +31w,ܼaaġYM_MZ=`qx{upu!փԫUd=,D"n򿪢h#8@jOA1jh䈚VU&WUy+Є'e_ǿ&8:7t D a=gOFk+5G\^\lwGkA$;ʙYN;j"vzWR9Vȼ[^NI7nh{BdJ|y.m~eT8KdE%̪"_?{P1@"fˍDTy MB=;mps'Gz%b9TX̗J7hpa\;EQDegAF2owK+9 + ͎T}__$Joŋ'ϟQ +S$ǥWϳש)o{93)gU ⏺.BdR凓^YnQ󻇍8ڽǻrPܴ%_j&;ė>Wv踘9_C) + k>ڛqcʜ.xI7slwgDH1$wpY: J7MC+cz|t;\ze0|CJ6fӡl7vup.6ruBMfk]Fl/5aNۅT.WF@9Tf8x'$me?5 Ixf,,7CU&ߟkez׫'Sk3kM׵N{ .7 oAm + pEV{2/7e< Mݎ/*o k>gR=6HTcԹrx['im+|Ao*T|k+1[s݉;n>|r"5|oˌ ,WK y!wGr㩤nv}=^IIg~̃wv*^~'11bg-@j2\җpuqX]TN#^o 0[? ~ |"(nk2Q?Z%53$_Q|1ؔJex]ê)np]꯻M{FG1r>~~ke{^އ+?u˿Mrp+S ^yS8՛;yCz/x_uyײQ!x|>է endstream +endobj +1387 0 obj<>/XObject<<>>>>/Annots 146 0 R>>endobj +1388 0 obj<>stream +x͜[Gr+zFCtG8lڒ^Ѧ/ i02뒧8E]Kfefeeh5Y;LG1˿/i7zQ?p7yJ;bv6Nf4SŰl&MvANJa瓳m?hvz`}g +ds8990 +,J\RRn׌.b #Lۘ~kSŦٰ`SD{k[:۸a-@Wagwz h)F]qnQuV̈́ +ތf:b=؁iJ J&HŰlJ(a'3:bX V0,s,ObX|=+L +ŴuVQ2bXW{NK0^E6L wn%`^ k0 `ة K[ 5*Pb[ItoA5状a!+*6ð+j6c`<JÞ7c\,񙥯*e ڳbX=Im뱯lԈlQUa}V- i+5AϊarwX{bXKglҶ9 T9R)}wNS9&P } hobSGڭbX\ K +V-ka1NuM:FRLR1ݲM9[?T1lkF*`5 KX^(+G􉰊a 謒l5 a8< r' TtZ*:ez)mV0̒i+Q x:%.)[L%[9q 3! d^ +RTXenH]QՅnnA%86]s Wa| P.tnM]sP *'NyBe֦aL0ŠiB|RPwYL &d9yaΆM-n|;āM(`l{bJ*A]u9nYkZ/xNS0FQȀ3!âZetU0[1Qهy3A:ŧB*!-G4$%jz2sڂm>4"EKLАQ1 { Dq d"֩b!V0,_daI$X`RZgIL$ *ә`n.;"\Q[9L+MA*eOdbX7D V1,ET*65O+E`KmdaEX(1Z*ؚ+ءDؚ98qڎX`R0J)`X{U(%o 8ѳ`Xf=r]uK[䓹]Ub.ci$j4:)rP+ U4TnP HP9fFX%M1r3[̗.lѯr!ػ3vga@:BٴpD%8nokfh'J Cd;pAB8 +:v.\@8:. j$Q)O%]'vB X?pK. \@&IROW #R. Yr9(S'/<ǣ촜?u0Ͽ~|}m/GO7a?ҊX֚}j7w\|=O4I?Zvo卷&iFm}Dv٫Mѝf~ޕ.m7˵upxNpjGs9߭.MzBo^WryV_pec#T-OMjycjyj:dﻫkUg֘vy ]j} arzn. 0ܪۛ"{EU{|}993:cɑkU?6{z j(;]o} [,%c,OCE5+'%tRmehJ\HRL21jul85Po7oos]Eq%Wiv0=̦u*kxɓ-wXkv0עAyٲ;ނUf g%#}b Z 1'b,B!{rn'>< + {׍$61?֝Ql^iKܻ̃î+HS$t<ڰ07mz{ÂB{͡^=h[s̀s:o]oyhI M}T&_=K,Q)$ؾsë{ݟ*p/!e8P :ˑ! fɑ$ebmՃ_gwʃ9vf{z6Ήޝ9~46dDeK|wHOomnd9~dw6z29RͫP"\ʗtL:l[z^$X#y=&%|aKmb'ک}iQjfAUOmVKe;{l5G{1nP8} +Um_)GpS{JZax'%آ>哓Qۿ! >6U=i<)Sz?rbk6[#]gv+"˴ZSθ߼~ߥMk̓cu'&^Qq9Gvr\bJ'뻚4WS2c'b97~*~U }K'H㮈okoP~k~,9hydGje[\cg_B}k{؉r*E/=ΰ;sUb)EQЗLo$吴^$E'=(<${y!&zrʇPn}Hw8bS  R/SpM -kdC $ˈv/˛|˵`ףṱ?BխLLd*(\*}竤SyY~885 ʒ^v5L~mz]&2b@ri9bwcY ȵH[+Bzc>HQ""gzC䰮$-~Zs .t`\]Zto]&Q nS%F dlhA54] D' +]R[Aʅ8(vW=H{^|vjf '+(>:nK)uAc(^~qgbbYM]UڗԽߠ=>սQFcևT[{y-p ?ny6X5T 5R uPdPNwۋ%>kr> 9un~pJLB-i;bxcrsG{ѥkqy~YE x-7+\'i-)7uDyˣ=^,Nx <m$mo7듇=p] {;^mSb+ endstream +endobj +1389 0 obj<>/XObject<<>>>>/Annots 189 0 R>>endobj +1390 0 obj<>stream +x[]s[}}Hf*XqƝ:Zʸ3M(?gw$OII;vbY T+ˋBqRM>!AZTp 'md:[kX? +H&1KY2,`b Z-cUcM`L \^䘝:J*E5vCLLXщKm#TΰTG2u:d }ӈo{[8/e nEg mkg cPjJmf@2E\_,aSZE!ހDpH +Gd +⦦fF/ZA[!py.{WHA% Z羨*>h,8XtiEԔ1ؑ$!)&,luaT +\ +Ic mey[T  \$V;H9Y.yJ*29YdH5bUR{ՆڧT 'k˜d Ev @jXG uVm[ +|#ۗB2ƠH䦦E$q{b b3,r +z61J.pl+t1-s)5e dX`D0qޖXXB"qk`77S.:aD2HEX¢l'm 9&;)pAD2N"9k"Ŷpx lX ytJ/J.Ra"[dY`1ڠC;X(A'`/dn5uV-@6r&EfΊ9FF!6 A2r\;GxN2Rѳ&*8P3q'!$NB7 \Wx'KCu ;"tI3]$k#0MΚ +.pF8GP9^jCN!1XFu'I3H%YJn%JLĐCD2VRXǢX¢deRό`m;oK,OLg`f=e +H)$t1XL6yjED+NLA](qXH$cB3gE:f V?Ϊ9O@ɦ!6˗B26AY;b(3Jޖ1X,1XD㚲Նhh)+NB/T4C89!"-a1D-a3k`NI $n9GPE +\e,KnƒˀXYY4pzGP0’qX OM4Y_P +\i'k'":@\g @KX -5n^ˑA$EB2ƠXwg X뿥WGha.Q94YJRD 8s(O&$G\%sA9U\kAqwR<0vKASn9v BL_ApQᮡv<^[+wR 09bԟ3uP%k%wv!0' 8jq.= 07K*4&Ssߤk9'!A~X?[P.GۅQx꽻}i\71n'of6fiq$*#J/rlJDC6ߨ* UnmʑjLI /n8B~TO:EPfr6,Wr|jA?H xRw_ ˷9OqGkg[xjwsx}X2b0LizNgEnlZG#{H%GȓJƹ*:bJ~a:e!gq13=l"}w< vg q;|z~,&/xf̉S#n]?mG`:AA`W. {ذ |zC +nU:!`NFE>u(/?:R[_zM,h iJ?:q{*bLpܹfq5-AMc4ר T琽L4&pyOmCm3%Y9]M֊]Ű8⹯x)wKg~"ʏ75^~ē{:El:X3m BQ{\, SZx5#ȫ޽pw|ڭqq:}7":.&$ɶ{׾9dwO.U?Ay ouZNJgG6Bp[ҼўG8YT=2i ^.0fq!\r +?51iE_wR-8]10n|lf;Kꕽ w:]Zc+S{fW>]}c,,SCnaVKx#{5P]rdk?4pBq~F`?Ƃ]VFkzZb)`&uI.RlWxxlxґlv;KO& +>wO{(!#LEL/j^ODp?<8})folVtRJ/&k|^t?.Ǔendstream +endobj +1391 0 obj<>/XObject<<>>>>/Annots 234 0 R>>endobj +1392 0 obj<>stream +x[]w7}ϯxtMs4'}UdQkI,$VN{N;w8@AgE"ʬjY>D>zY5Lng.sp դtˬ1خԮˬ,Q[VulN:eݤðCьl3naª0a+ \hWkj'E8%C|k) ,_R`#=vR65j|;eA4#= +4}%' +@5I\_B&,a`ᩍc&-H0M"GGgFtܚVжsjl JG`"E.:NsXY)Ҙ "4lI&U(1DXb}Щċԩ4rEUp0>NۆNN\0_u*1:-[m:jj`[: |o8 0#F(+SrF23W9t1v'gvRw8.+jF-Qj(F{8CdhRC0r̞gzt{: cP76ضĀ] 0F( + a0 + JR + #xl U8EUHb*uN[pH7bvqTMf촃Juf0Dz̰0"De"r%WIcrͷsjs Vyt+f rKe͑V .# +QsE4h+1Xɗ0b1V<ޣh%@d\pUD%CVcZc^;a`jðNc#v.B9 9bȌs"1XY֬6qɛ$=f' +/znl)-qt"Q>0>ۋ.:L]hEa +3+c=Л #h͸TG.D[#=H c +̬յu"a u[Yj)F+‘+!H# +$,p +jSq c:E~(`na_B݌P}D.CK0XLJSrc=;k1Ǯe)4 Wڊ;.DaM#pȅplPVrPc% n$ QQ)E23 ̃Jat&S9 zw2V(sZm 8ADםx$mQ-2!QA +Bw2 8gqz"3㤳ԮogZcQAPAнVA"zV$q"Hj˔K%yvy .dz.o:{^mݿ.C+LNb;{aq;.>r>>3,-/b~%ow͟7t2>~?9:G-VW?}]cvRt,ӫӕbI_E$buçH{t& obOG34l{;BBv.f*gﶛl+"v/N(ZZm7vL>x~ԠFPa*#t92Λj38#dG_Jټ!AXVNR_N77eH=p#5&CIp¤wgq'D}z{)L6m]>/UNďl[_ˀ!Ꙟov.KN9_ozP0ϧbϿ8}([hx()hb϶_Խ'CB|i1smB]pQ, ! Oӥ(R^D( &us}Ȁh +<0I/nw.L>ڛ& 2XS9~@MB|Km':VGI $4XdF62L>x~Winof+uPc7oÒc|:#&xIw $}xbOC͢^sv(;wh^/n7'^n(L#zKdIޡ5owl˴he̕Ef/w4!S, _)s+ZI~D0qw+4?-͙'󳝠h"Ãƹ f۹y? u;iNda^t FAWw{]3r\y^M>%tu#:?~[0>< @ q~b|? /Ӑ2[RUl0MGKYجCP)N(S +o⎾&d32xpNŲű|YUbEi<;$Lvcm9ϮՂE!GV 5Zj)_WB-݁]6 Oo3yS?ծ4g{Bu⯻|):NSC6L*ZQw߬oEܢa ͏4 Z*(JMV}\. I93QP*)3̆NiyPawGS*G%_i ==r#EP[8vnl b?~Z/kj_ŅdݠfEMpЮ)U!+y_1a=\$,7=ܜG8]cb5aW Kw=Ư@1;+҃2ӴOKe#T>j̔UX X] G}'V +E(V䡱EQ0OG0~J/SCs_!IXKUÙi9|*jՂWւt%4դ:s8됺/faX|iק\J娗r.(qm ^l߷kOWJDDX[an +J"n=Y"zQ?mQ)7/tfiIh>eRt j' Q@3rVz-eV)[IpV)QRŵ;zbA-ʎڇtu^`nx EPE( hpfOp'24a=MEB iX@YİFiG;A9 i/nl)4]oֲ!=ԋ +Iy拼5仩~hPcࢃe(4/M$T(Uߤ-Jx>ԧ=עcgS?뒄_lO?J;g/tjO +9BC"bi5J6R1:7_[+' ڪԎs<>nUn7IGVM36;4P`>|q&Oj덴K\N Wp V _Ɯ7\C^g<պo]`7>s|g9Bendstream +endobj +1393 0 obj<>/XObject<<>>>>/Annots 278 0 R>>endobj +1394 0 obj<>stream +x[ےG}+m 0˚3zf/h#3fu9YUْ»uɬUvGy6l\deMF~O5U.d\du=l"ql nNjK݁,ņV9Y[8d1,,1خv-eɢ iIdtRJ%=[Ԑ7ڳCCʰUgE-nXA(Anx#=-P|S=pV[(c۴Tmkøa8 e= 뮁P5&.H+jձ6:L5Pcu`&nc=kcۍ3; EU9lc=28UtZk%.+XCmձDQ +'E)1UAù7]{(17L3v`kzc8{0l*uÆ18x-6A%= 6OlX:4anX&^Mǒ `L8IIpUD4Hܫ@cPX\FYi+%" xVJc/{D8SAl^)1X\ٰ k%##N$1+UV/͏贉5qb1rGzcaI1/[1&T5mф~Ą'6c,1؂±s4"cj*9cڒ'Xv iQh于* })Ѥ*x1I%$C'eEU[ I ҁ%*2M9sRR|j60rys Tg88L@"RTnnj296qJg5d&IxZ* ڔ^ +UTѢ?Jxq.2cp2@c/tvFc=z  ::`ۦ+HF p6cFwzcYؔ#wM HMU?O +IG)p +В 4gV4 C +y894.q+"ﵞux0υіkuۚnHNA2 ÌlE3r`Q:LE: aJz aƊ8?-70kH*@8ؐ60L.)g:`aR^ɋ[eA*4q2iǫ#W00L +_0'g;S<EPIEx0Jthhm+"RA%N!2O=rb|9*T2e'4Ur163Yq]2Lg1 qH2 +5ܳGO^t`k,a\eW@˛Yz}Zng滋1 +==zr &z ?7o%f[_ fTtnkٯn&j.P 8~E8e4|6}^WBa\^@4Q[oHV,`E_3݌;D 8dzSuZs0Eg̷Q 07:0$zb/z8Ucq0ע#{lb|CIy4~NPgiP_#M3#d\ǖҏfbP8FL0oߥtq:Q:(-L!EնN@Jnt;lޭWQw襶=TV=*L>0AA|P뽣<loge\ +2WCgy;;COxi? Uul13<,W`-E@1 +̊\~"C]o{>8˓FxY)($ۺO(!^|ٮ痻xpGӌ~twR׀/}AqR=̵qVJ Pʢ(1ep +DǸ=!F1\I/ J-jS^D֩?/,dNx3N+! %^t 5=#qicu{/y4Ʃ<4J(/WB=w|b [JƝ +׹S)$޻;)a0] Y G=I4 +R}ay8F@n[Ϧ!$8l9_Tvܼ刓>yTixw{)]\w͜?Fw1 avCXk(! ɷ/Rzsd3 Fǩ`bq +6Ӊ$"j6[OcS\ej|(T #6_ͧfZB6CM*E}1XX~v=;Q-U;);o;bWg?S鋾]9?L8=Uƾ1|O"b/<^i+9 A0y"s994`GV"7{39|Qjvw9]\e9lѯ/0 XNiDY\>C zup^@oka]*o+T[h[=j*nqrF^܈/ISmyOΪ9Q@KQNd%xt=GVfw{Z%RwIj$:݇Qb*{ru~^vW}}&tMJ3M؟pf}ov(=0?[t ֟*]^+/S~X!5؅jo+"+Z7Z矾 O&;x xo6u +/Οz4>nn׼da7u|nέѿendstream +endobj +1395 0 obj<>/XObject<<>>>>/Annots 321 0 R>>endobj +1396 0 obj<>stream +x[Ms W!Uq#,Ŷ*+[do#f#r!)}n4kQIծ i1"45lY6$5c +,j$IhV!qŤ2`lY`yN22"nt^\A\lj|*u#"!k0še &qc0E欌LLrUAPq"r2J:eHL`Eϊ5X (ƦIM*]ng2k +8Y Ē)9b -UXҰEd5lYbX6eꌃà`qHTQbyJv` XHeEܒ., +ETW%9l k0 &T$`r%6lxQe)YtUʩsKg X<8 xRJER7`@x㒄*)>` 41EX -Y%= A0(Ms,A ĤiIi1؊ʒ[n9d n0@@B @Y=gt~AdA7.IäCŰudlLeR $LHiX0`t3Y9BbE+ 9SI5IF2:us ĤqLj(i1ج`-L֙Y ]@9DC +~H$nW` + +,Y63ct\)1PI ++5b k0XM29$ d!q<,KC#OVF}?x g;4VmM#e'ӗ'F#][J * _n!#l0!p;b#k&ɳ͆j5L*:UˊlntKճeu,)߼n*N'{?@;bD3͜f'1MO^if 2zg4pu,c)rXU#ӱ}- CȢrHtծBVۧeznߢl‘Cknx-1?sUoxM[{P\wK{{Ka""Z-6q! OϏD%uJU7 lʿD9r|O /ZE:ҭ硝䉾&OoS;GqNMDž(ln/qeVsס}Q7Z-?5m9轾Zc{sF(ԾНU& D{(Iᦷ +rIMLpH j:pƚsXjK?㖿`Se}kʟhzWl%.ϲ]H7s-͆'P|>cGww]{jw(Co4S9VcmɅ䠷0#zlli뤔GS)Gg8<;KvT$%w]l*!8`x͉Ozǫ~3LH{'6Jl4/;.C(i8ĝ*7}hw@d1}wAQ͛Qwn^ZnIKҵ{"U& -N4vz%wֱ"j]{= 9{$+[C滇uX}]N٥G3z-ZΎG8nIC\O.vhşCwU!Em|T B4v"|QJzgec7غtZ# J.7x-ۡ3 ?`2#}&6*oG*:o&^䑾n}Ί^8^R5n:Z*8]߁F]lIj+V|wn} vjqu:Rᇻj̥v.~P|!;4hMQwrM {ƂfwZ0s$_I\L&n{a/ͤk9j]Y;_HCZOW|"M̕3.0YKVu +o`ûc ŧ!g!8L}dN"9;mKPCk/gWt1/Mp4I2kw)Rm|uQ]o*6Hz~A9J§KQ|_ǏI'kmc_ZKmPs;Gnsw*;#i5>ϭ `\/1 6:駛>Ӫ+g}*nۓ~yσendstream +endobj +1397 0 obj<>/XObject<<>>>>/Annots 366 0 R>>endobj +1398 0 obj<>stream +x[r}WwR4٪l`/zYKPr9= RŋT%<{0Y"MoYW|b:/?Г*Z*I2ppr$ IM1 b`O +Gz l APIؼf6 +hMi82@Vd0cs"qbi +FzL ;aU51Yn,[lr \:iJK"="'ʊتeo%K&6p 98!4e;@ +[H8m"Fz 6Ƭ`oa=[דڳl#l`sU%{ jzmRh$;oeh͋Ѭ<[d#kx i =[ֳm(XWI1-Fz P"ȊX\͈'YqDZjcV+\W+lCXÐ\r0 3"\,ރ5a(Hc[\c Gulacc&׷#5<0 K}0S7d +c[T4%cc&sֱP:LG=[#53}Q&fxd:(3mI3,:871Xl`bHPz &%5sfcraǤǤ )6c0TUyQZ@U)rFzLSc[Q`;ań2%Z{i9RҔN#=XbLT]D5&6pA3%=VMMؚJz 쥁KSꅌt,6kub#G_V~IUvi ILDc&]jxXy)`uw^%=X>QŲP W-lRJRdIZ@TdRǕ*KEg~akoPҮb-F"1Unm0 'ΈJU-Ke/d`! sB3Z:L)lA X\9!OHJK PC)nyJ90(BGP$)v$:FPpJ"I.6@o*TPl"HL9HBKHNEEm4p25Plr$t(B3iBE +iDr +*)B#G3PST\sBA}H9c>(,M VC0ZC4{Mp ᆱbloŦ p @?n| ӒhAh| )~S!7+b AR,G< N~C4;zR +qw/^&,gQ-JϬ"[gXi 77s1^|D(ưyJTUAeV ]bSD]=G%5WV_B K3Hg=L㣾LDp_GE8%8h^`V?=S{8(=/osl,W/IU'2y}Mta\z9g7/M5oCTRUFWnk8 +_]Ae}EozN+(MG ex6י v1}KPV YPml"rePՙYhWN ދݎ6As\"~` }74C6 ؊D] A&Z.ج + j[ElDOsBJjtXCv [I^BN =N#"yMAX{6.]rn-GgޜpS*utכav1 e-87O?/) p|/ۀX_'0^,Cin(v-bb*[wڶ!CdVa%w 8~x~) : o,(Vvl1֥r&GJX۩(!ZZ{Jt_wwKNIZn08 p>FB_btdqf}|MpԶ<MO@ԇ>!q5+o |Z̥ +ktt=uNnJHƟ.8 qdK--~]=q&aEC/V)k::8!=w-4jyOc}^kwt;4Jiw$7w%ȝ[dtc!?P[zw;r~26z!8㬚/ǝO(Z(\ ~V|[y'-ZpЪ9ye39a9S\Z4w; S)zD2t>F]vyH'R_،_a4¦۟9O7STs 4h̓Jh?FuZ@Y$Aۡ4ra]QVBϳNv^cNO;Untn'i | :雀W n-}nJ,3.+1ғ-hG16hnφ-= kX܍?|o"]N18L6?!h)n,Ε)*5.&:z]uU8g )Ŀl:mj}|z7_KQ쩴+'es)\1n'GMt|nuLf!LJdө-W/c\q>͖z_%ūw;lr9ǃ/#"xʵN+&Y\:G_ٓRn9N7g d4>_{'|0hY6<%Ht9Am2q9}$||~X DXc[.ۿFiԋ fR -qsq}%ß ޖ/E[xӦDz=>oA[ş˖N+>oIw+|ǟ z҇0 ŋ/Ҭendstream +endobj +1399 0 obj<>/XObject<<>>>>/Annots 380 0 R>>endobj +1400 0 obj<>stream +xXMs8ϯa˶,또MbP'ce=vIUT==? d+'Ew,p*5%N]a.2.LKFr 6,`+*2 Vˠ.ݢ 0FM!VҊe,Ԍ9Z:NdyZ$U 9R ]aiQhd"90"Ż " z2|Lg|`+.`k9k?4̇i1炜HW+N .cB~$980XT1XC]&a9cd'cMviA4q8w ,-cox0EQe, + ˆ%IY5$ % "dԒ" iKIW>,sEr)dA8] V@NBb +un8IhMN $4L&Z:v\8!4 H+Ļ3N J-TCexztvJx taw kN ++]Zv.Im8YmPLVvx}j61Ƕ>㖄ytk-svہ<>J23?9sLZhm_Ye龸o1TE+7ƾVEVӻ@U,SGӟGԒ?>/Cr䑄_hxAEX.lf?nVAYhLgO1A=?_[j='ߏMPQջv76pH[oG3Dڇt)(?Ene?B}+PcNJۜQiD~gLPP+3!KwX<3'?͡WSRi:7bGz.1h&MGV>mwG fgQ2!0mKgCv֧Zv,wmS'Y= ,X9a%Xܴ#[fcϰLx'h+vU.Z|0`H!5 +#0M >i$@T~4mzBdsX-y5`~a o)sgR)}_};4SR|5oMfl_?AOyL4ݳ`Y/q +M ]$Z;`âDԾC`m\_O:&-xMd_30xJ ~!o޺e)B{i^}3o[_^@z™q|^ Xa/ +4Nޞ$]əYvV3*Qi[^ZP,endstream +endobj +1401 0 obj<>/XObject<<>>>>/Annots 413 0 R>>endobj +1402 0 obj<>stream +xXrF}Wt%JFLk"GD/~! XTT*tO@%!E ["H Utǫ)^,\okG6xpX20:P<"h7JlQDak(e4Lv3å 6 FAP0xqfޜ„drΤ vlEh5E:X*ȑ2%$$.bib߱A 1UIkMO K(*1LkM((TM˅Mu"&cV?@97)d9NA({9Rc!V +P +E-+/MDs& +9GX.X(n;i@l0؜2Ki|!0E@*DX1olF>!9j 68Vcp`|MY% +R,4BȎUuq`-X&ҝX9]>!DN 0 m0KVs >$1̃\ +Ms[@u'\* 6呢X|k8Vc2kec{tiWA" +c!;Vas0a4*Vay!O +!-|`"O?ωR\9ApYRAǓsPS܂Y9ȥzgSv*EKP8s#JX> e 8 Dq%*AΎSAp%Tp3 8 “q U 8\j%3.{i)xOW/.?4y2쌼1mViU{}jWvnGwFySUPRPw[\osB+FW Mvi ;cGC]?&Yj, ꂺ/sHM#rn)CU& uCc XWWgjD[܃Tϭ'aKqER[C$n~nL5Oú*sͧ_PQУ(ȅCVu^ \ѧ6]3q@発M}U*o in=T^M2{;{jD,K {T-B67iR]UtvN=5Yob>/XObject<<>>>>/Annots 467 0 R>>endobj +1404 0 obj<>stream +xZrF+8>C백yΆ%˖/ !G;JR^o8b"zWW5 ~1<YX5g~b1b6&dŨ8M9S 6[ +[,FQ<-LqAQCQc <%`*& vf + +nB >y,@@ +;[$/bȮbQD0)r!U L4OHf4k,DTh6E,8+yJb>N&P?È!d%94d^`˜>9+F١UlFCfvf YP)bq)"S9f([348L G%S>~G+afcn\M]ޣM}::? [paz.cMCFY5wP=t{۲P7jܔ]]4~~j\}>ݼy(PΰVsWEdm|u[c_uW7em7uWuzWlr]o? \}ܵ8zj{_Fn?`!7u${U(4.Q ~ׇ +]`N[>vSWoJZK\ PH^wݦj]v'{N+pPXcLeⷒ@MZlUhb§M}_c. +)ayUv_yRhۑ9S +:/\{kA >u>$CMr(L.@Ԏcc4oKw|xi7Z'2+Uz/-}60IVm1<ؽ4iwGL +mNBz|?[<ɶK`[hRsјB]43A&ېC^?=<U=b6 %8c쁋rX&[D/z +~S&ưn9Iݎ8& [WO7G +׃f1Yn(O!r~>.|Ӊ+ԇz#.bǹN}-mU{a` +5ºUbH/.u}OYt,UWڍ%6+]6-U<&Mw'XNn;˲GG8^*_9n..\p%`8Gyo<_/E? s~{ٟbendstream +endobj +1405 0 obj<>/XObject<<>>>>/Annots 520 0 R>>endobj +1406 0 obj<>stream +xZKsFWQZQēQYWE^E DBbВ\iLv+UvZ^$n7K]Vb:'O\IʪL%r h.fYcTdY + PR Ӓj9KY'%=*(ɼF'+ E2` . 7c ` jQq4D>Pd3rң9³!bI<$4L'+ yq)%*&"sa-E9 Ns#3 d9V0e +lUecb$.3cQֻ\ػlH\>kXDV0d:Lm +S8}Q`Y?bi`9kYQ*S 7.G/k60)T%\#Y33d+,ˑ4#Y`u^Pb;2Ab& +XU' Ր,(`8 ,VRY`14p9}Hdd# 9XP™1B Í`d,+(ndt1)"iB1 +7k1]Ni6rƀ"+fˑULǚEjȠ\q2#sY0]ΐ ae*V0].z܏ܐ/.׶4sWX`m+8 7)r^f[Ty2Aqȗ/bE +A"7.ì24rJAV1]>V0]dDYp㧚{ N;ΐ,&av:SÙ8 +f@\%OyZYP}pA` ŮDLyDV1ؤb;Y -`8 ++Y%`(N[#lۻbTֲ· `^%23< "csz{Sq4 ++,Fe +YzZҿ\!kp'*%>VTЦΚ"5dI QGh*fbb8KaSZ +CfV0(blw%pl-nv`_ ! ,z.GV0h~?Ŀ`N`]!\HtزXD2?,=b:^vKH pH=>ZŽ + !5dCSX`FW\ X~v%2ł +f#+V?a־DDV14[0#1pSa+,69d}vҎF6Ǔ Xs fMYW UC^qP1hdKa/3ULf#͊9܌Qwٶ̢H!sY0` %V1ؒ{FX`}UW~?=)[x2~P\R 84I. tZ֝9s|*D.Bp8Sή&Le^gbpL,BXÆDh\P~8rœuT:xcqoA!n)pU#g#vصր!Đ-ø#[\\"Jj+L>u%Ns}jv~uWwWj}|z>L2q[}mhXZ4nu}cwn?^9Z-gƮc-dD3~鞺!D}=DVͩ1zjmor׾Ӈ{wu嵮v[;>ru[ovͪ{Qh[ۿ۽[u߶^5+wnnb⾴[<5Mѡfw~x'-?URN [Yqp 3 vfﺧq8ufF޷A^v{ѹ6\oWykaG(_Mkap~TeY:e%R2} >{8hݛC]6\v=8?}ja#ziGS1?PGԟNa<].sGB|koa/6}^xΗb>u52||&Ȫw̻=O!S!Kd|9#ăykapK󸍙/; gu[u,=8G?d~Aw3/?Z}[GXlkKù9Q[4Dָp1X]qI2C"CnVD'-}>/XObject<<>>>>/Annots 572 0 R>>endobj +1408 0 obj<>stream +xY]s|ׯ؇T%yL|O)YmUHW,ܑ{IRWuޙ홝; .\l:'eEo\AGkpf1< rêiMÔ 15le ;/qQa9 öE{] ܸy%2 )H\)HY!(L(hb-|GQ- ޸⬦}UT͙ AV8O$ZsYfP+r"T Y+- V`9ͳ**܏2ƂT[b8Fdz͂Udzh i=fRP5,Bg f"˳+@.%F߹0퉚8sPHI2~!tg2A 3r24o!8$+f 0HYMb!0qdK @NDB<Eh? fEW-wPjݪZMڭ9,rø/e.Uz}J[+uھ}܇z.~CqCWUmCYv,PC6*` 4^5C+enVkjxm{ZϿsNnM]︉H}i]7+ +)B7/{&SEiıv ,30L ~^յOɱ„ +ߏvvÁ_~kqC:u +Ӓgܻ~@]{9vuzHSi9ot,W79(o}l%-YvC+)QoțX`ݔ+<*W.*WKwjo<.z-J~AKr޾CmrE:\sD}z{uՋR_GIٟ.G=]Zקȸ/.qWUШx+: 3\vU~_Gko%-\٬Nmq4c$Ӳl9]$] gOyڍk+נhCg]lU(}}e}.V nz\,Q)^c%BCK]˯'Ĝ>Z1j܋alӰ==TT]s:ӝM9ڰ"7}_7eWq0 CI}J4tZ17pDŽ<2De0}s[BS~pCJ&p ~pw_+n8@7WbvhTW(t}͢Cx oawn8Ӈ-sWj]Ab=.~7,Cķ?G1Fv]ۊw1z1Vp×78rHm#.?gsCg}Q(:&dz/glendstream +endobj +1409 0 obj<>/XObject<<>>>>/Annots 607 0 R>>endobj +1410 0 obj<>stream +xXnF+ sUIHV5-l|${\YZ 9=UD!Ed2ڶ0ӪL"ߖ"ьYi 6+LNA᥂fVeU˜-q՘2(J9%A*PY]ya3H 5U2 b)a ") 6CX9X0H`5\XW%c) G,H*n3ʳ +-Rʳ +ssL*0⡆1+H =YdI 37D$ + D" \s!VyI\nyqRA"U)XNQAK9N*ISޗ`SAN1Ksia4 ]!\T֔-]X'LD-xDu҈.z 6 l} +RrZ–%:+NhF.`a} +c䉔 8T0d' 1Xrdlr|9vH(CB Ot.oD8`8b8%x9/b[FGZW"s$^!Rt!5* *y||V%WSr E\Y'#$6kIFHv1gsL1^X %V`{Y`=*ܒ\i5+j 6b,1k -+ ȯ-%`eܽ‡CRf9|4Z/MsAFzao%U[r^0X9Y9ņՖPᒖP$RApF2Ul"!{Vax ]* 顎U-jy ɮv@:Er+R:Ly9܌ ߻p~N.$P9^XaGv15,ϳN> :x=`H3>p=(Ub1rR+;UYh41XT8׬ ^Mb]P0/%6|HPWջ[=9m-f€nL]ů.ԯC| g>Q|>n/DŽ7ts%m-T]Em8 TmaAV~#U=]i2F@dF퓝 ,1]_@T)j?d~yCrQ,e /mtl}.(DeDLmz84玎R>5h&;*2"?i[\p,F%W44%ꦡ'%x5v4d,]wUxƾKy!lO%>C׏Si¬ʲ;SiW;}z ˜Wag–fJw%\~d蓝&hg }KVD9Izz1hihs?is]?*^qgosN9n?ɲzJvĺj(ѣþ&{k3loՄb>W VS yroCn'o-v4Uf/' .|E-YFendstream +endobj +1411 0 obj<>/XObject<<>>>>>>endobj +1412 0 obj<>stream x+2T0BCs#c3\..}7K#4BHP$YSO=5/(1G!3$1''$3?O3$ BMr = !)f \CT&lendstream endobj -1669 0 obj<>/XObject<<>>>>/Annots 607 0 R>>endobj -1670 0 obj<>stream -xYr+.*&UJlGU~Ml smBt}tpߏn@ebY$沭/f ?|}h&qג$3eY'dAѬ 'E\ -zIƪ6h"]%5#ٜyŌuɼ`s-g]10 {$j6 H` l` fˉfV{tXApĝtxN5k8585 ;ѳ`1l5'g U\{Ԝb(mǑ7m@ܝ"KAhXw4W`(qʓ!Ul0X\ -*k04 `fް8<5,'`upXzw V.3ƀFp(g5fglZ̀86ufuQ1˼503`cXaY\\/nnxfy~b b S[&ǽ; Ÿ'ٳC1zbްT"/ke^m2qR#N95bkl` ˼b{a |.v\.3 -ʫuc吢4ȩJVm}YVb -75jM_Fo3ȼp 8|f[.@ 0^WF"pxfߺx)y@p\| 21i]3wy`7ׯ4Jxxn"{|K&~iC6mgcK2ӗǪC m^ʦ슽T}+m#Z~({ٍ難#\KK{z=ʏ -bub&/}?ISH~j;ȹ. ݾ7l=b|r4Gy)AW__Q_CH>1 U1&&`T/nSUaXre_E4K%Ҥ6au}{Qjj)d=ɾ꽭^Ewku/eG%STã}lWHLkk)>ϪYԿ>m ~rFQdOc#},lum۶w2MHѶ=rs2 K'4i;7yӵ}/]SkLƫik@=:OhCbMFF% S+I0~Izѣz>Hɾz7Nץ|-v(iZX?H]rΚUSW:E1ͧY4V>}Aխ*еCmal*(uE:,"(6ss1utCvuO -TϪ_E|^|}hh*ru'>5-uc?Ͷ{:J4mtmsyN’ҧvxu|Vf {|)Cj_ ~?RgN<(iy{pPkm{78g 9}jŸG-cA'ҭ1Iyqؿfa6p}o.vzBw.mUagȎoqpmNL+a? 'b"Mg_?>|8/3>p Y8egi&iLz$\\6"0 rP8%X"Ǻ%zt"Pd_5Wv",/5Ç2 n.\ <endstream -endobj -1671 0 obj<>/XObject<<>>>>/Annots 613 0 R>>endobj -1672 0 obj<>stream -xVn6}֮߯}$5mA}$JZURzgHI{iҋ ȹ3s?G!M*ْr4 2n ZN`J%MVݏN؝Ondl7͂9-V` zD݊mO%͢M0;=]cw9<-ri^H|ውy8E:tU/\ yn ŰX#0[=hvCє_ִM_DHCa@?=5n+ۈ QWo^+z6|t0*UJyEag?loT%́j<\Zҙ7 Tm*SC(52Ձ~RULЧJ=SlcT6JWmwl, -Rr)]3J< Uц`R# ft-UD+2KkM"(yumtmhe"3/xHaZW[3Zd-#Aʒm8#!+[ۂ:ժg15&'spDۜ`=i:EP&"!*p ȘTZJr#'^ɍw - 3]X_k+m#{2ua(2h:Д{?R xĮgopBUtj>Gn#^:=bj@se-7 ƋRҎNug)׀ܝXK}rJ jhD,gK`WXy\g]$my檛n2TUnOnKsce* sZs)b{:cѪA™ow~x4M]'4ĝS؇^/8-.nк}ʃPn@0_E=Z&*S^x<|Ø;;hkl>)4+!/E#J\pϥD .#,%(,#It`N:ؐc;VP #wG ǍEvwf#T9;b\.Oʦq˔0|4me/fn0P?rѱQ \={TZɱa {vt$=b 7`^{qXܣ= -Rߠ[s~΢[tRnafo_F(9\endstream -endobj -1673 0 obj<>/XObject<<>>>>>>endobj -1674 0 obj<>stream -xVo6Pl IJe;u -0-Q6TI*#%Qa bwwӗNjBKʪq2U2 -XIEX^,$^/F7 Jg,p9 Mp&ۻW˗:4[+l)Gvr=\ 'sRK[L -O[Y֎Bm`uZ*zZxR" -;1 )2FR] -_[Ӻ|PKj&@B<[%tFLUR9"8/J~],t~H8FaME82'h. 6>7ΓmZԅx0V"*GkkvNZj -/ףQi2Qn׋q:zYg2Ema_\8WWP-*Ϝ|6 4(uȐŅVkrUJ"*ViK/)M^r2 Zf\Ei~ʰf4$Ab.BR\Z v4>tSeɄut !-ԑS62"H ra ȍ4&{*>}CMt766fparD!"^.,j1=WX;L)&B\2 v4eN B~fƜH]r+"p<(lj2#Hܟ#<0- -$m0'rݭ^,0jgs"5Z}m'ģGFra3Yk::ixYe@l.ߩO\pXmpvP|ε}2tfM*Ap7q=\}*6N2#d0C|G~ DπK_EU+F0&dƄҪͱMk(V0CjcnOV8vky$aF'PA09bdzq,]H./zݾz}3tAoLT%8Oix5^[@=~6's7uy7= endstream -endobj -1675 0 obj<>/XObject<<>>>>/Annots 615 0 R>>endobj -1676 0 obj<>stream -xWo6/MXNlC4Cuo-Q1Dj;RNP4Hl~{ф7ŔGlL4px_݉ |./=] -K5\вcZ'[W^\ݭ?^~I:}9\β8iZcV:{C*iύgg'@s8hj +&6jyÎe1KO-b< У(sjxpy$$DRpJX.Jd|! -yN?OY䦟S*YpBC["; fWp,wM:A{G,@V84{8l%71X) ԂsP=y -~=k9@[Cƪ1ux9NL f&I2#tL4՞|B0c5 B7(hcDŜN#F\ Z @Hwv;~=5l+.I <F{ |!P,\]~[{&>P E1 -MС [}zOf:3zhHsK~w<צ2L)m:! l m:!ig,e2BRJSPQX5b~<8{TNjrb1Ph -yw$];/d# 6-Ay&+-K(XcSKRiXnʓ<7-=D6G!dKBy@G'ߚ"B<\03J-TA>/XObject<<>>>>>>endobj -1678 0 obj<>stream -x5PN0+Fk7 'TTZ8:4%K=kdj3;#1 AO"#P0 \@rGERfRBDQq}6,_7.O<:뮋d'KG u_5bޫ~иo Le71E])EюMs-ѣT?_9Mٚ3ߍms'NH>/XObject<>>>>>endobj -1680 0 obj<>stream +1413 0 obj<>/XObject<<>>>>>>endobj +1414 0 obj<>stream +x]N <\Vݤ&&4-n Zh6Nfgt +B;1-=;vp0=YTa:\P=" )Lَ#,l~ di!<^ ]る'S^)EٍW:lG}|CVjeX׺/b^p_lendstream +endobj +1415 0 obj<>/XObject<<>>>>>>endobj +1416 0 obj<>stream +xXn9}W Ŏ-g˞H~TndKQ~OjGI V_rԩ<Ft9 0Wل'}N:EdpwE!-װuq9eN3vuPFLp6odPJ[/h4JǓl oOgkۆ+096"7(J%Ef6%;~56>y:?tiOֺTx?i+Ek6Jx,2Sr8=6*\Fpں{6XiˌRtZ zIa7u|9f0-ʈU5Ȯ~o8eG8-6^`;ayMG)ӦBR-rsacNh`R-5q4_ ""#V{Z)+|5]a(J8BbgCdxQ-*4Nڈ^6S;Z:Lea.4<;Oe`υ"-= Ha{Lt_wmCn ?N?>=N3ZnP4#n5WMS[M2>vT`,tV)cWZU&)؍Ε@C0xmY5:zHOo* oҵiE +%f8ōZv 8=xh~blKTrUYԙʐ_x1RCF(;~sF2pqow^(,*}oJj#&giG߸8~3ULry~u}>f5Izx.etf3΃@CK)ǥmUaضE}&Ue,ȷ {z+-LlwpϊE +\{x\RWx%i(+J5R >E3_#+-I [ H }⓳JiY!q@טqȩPqi3=M𤾠$3d:BrKYc^yS^)} fqN@#)D੸Wp0sc'L2,E##z6y['r?MJ*eQ.FwKV ,`wܥ( vؘܕ@'7Lw",N + ,q=r)@C9$2 _wql9CR]sawH1 I ŋ0KZ&o +]0LΓ\M'oendstream +endobj +1417 0 obj<>/XObject<<>>>>>>endobj +1418 0 obj<>stream +xXr۸+NDKJVWnE$@˚ARR'IO cD1M(.Άѐ& ~M4]ElpwISq5:!i_bSVh5Α$ߔJoƛ3?9/t"lBL#cVi{JM)JqR4Axb͞V{/_Hig6p([i3Dn{8(#)FTK_(BAL(U9M8巕?o+A5 sR{%rJ+s1S>NLe{'PveJ8o/HSӫ!0-ؗB^12quM%7.3U4˄'TK$j[J}DOkYƢˌr;<$v|iѿ#5+&3gcU+]JSI)R3vgrR?$~1f% Sm3IKz{Ubrm cOt)7(qFG'--9T{=#QPՐAz6iC0LM18qDƪAnuI03;@2lyށ=CA׉;@Wa=c(իg3 Vhf WE;fe*E`v*M +h94xqw<)Y:Ym$%IZn 1dM)i".np7ޟF]]1>ľ}y& +ei}3h>5sN ̦tb䘴^ sHM`xXޞШ S@QwI'8"e+J$GۥQ|O hP8=@I1\ yUm {D2 qX%>R@G+i_U,Bo2m=&cn[NO%_Ozm5\+ǩ)ԟ5PĐbh4y3aሟ'^6ֈ$λ>!MB=1qUup8BunfqQ!ACgnhwBa8」0O_O +!N}`L_{}OM ^\lBꖐ!yM!>OSf;Ȇ+QX Jh/ bE51v\giո(5bNUql͍dԋ.8f uEI  ,ɍ@>O@~Q+^ +lp9`5Īya +.Hrgͅ0Ip4a ^YmU`)CN7(-W0>J8WOR]&eD\ EWM}t˼&Nu{7 A%`cp| -p_UT퀳*p @S߹ xQ@K¹vЊ3"g#";bV6WJq1 +6c xA.9zS +:!jeFB送Ą;CFಣ,^;௝w+d6Q⺥om$C귬9F%6/Ƭ}endstream +endobj +1419 0 obj<>/XObject<<>>>>>>endobj +1420 0 obj<>stream +xXO޿ +=T"vBB+E (Ii5'{ y;wl' ]VJs_终ѰGwݠK`@!{g%-_wO߅#4]4iB4>~@s.5rakU^ 49Z(Y>˪R +cECJw~uBZJiU,X͕);}8zt7ǖq-Ҋ|d!7F[cXUwuYهhmf̃K\*2Vʥ$hiLBRBZ<2KLTڑYbP1-V82_ӏt;{Bj޻*Q V J7t% Ā,gLaXiM efŶM!:AgrZlqg%֔2ƛ7gș?ˀ /&~:1`Kgmto3iMp0FV1;:#-B کXpj/UUڵs;뛝uJl I/8e |YifuUН(K4i3;Bl8 > Rec{ #PfSg55YX-rGTY´@Oш:ǣm.'d* $raOdZ{x5uR^Z5d &u*hyé1مŸ$\OL.Ѓ!̪Jd(IT˔KNNlR,Z$X7ɶ;;Yp3,=sܯU['!$,hi47F.y piR,Be4m< ϕ;8@&UG,բ ܓz^eϻ0m_|.ttsúTZ%Tru<XXL^ n؍^\ޛ/{mUWyIv*gV)HThd5W?cp]JQtB]!oڢ M@l0y t^ DUCA +;UކkgH +dJmu/B,}VzԜ=S'Kh4u'?U-gϤKR[re~ut!!,)?:U0ooS/,ۋ8$6cQB=xLe8Šہ›e$g/ȧ~qn|s6(Y'x-2Y{qf)G}VLaA!-T!>a&qK*ttGD@`;¥_l ]&Wu'3>X+m&|. /O }?x_&g7g>/XObject<<>>>>>>endobj +1422 0 obj<>stream +xmUn6|W,eN_r) +8q[J\YL$%)+P. rwvvv bZNiL ?ъ%OLYbOEf0[P&CjII3&p\FFE4G6Ii$ӽJq&MMʟ;IfVxw!%r^Fmd2+} FcxMCلSQ92B{vGΤӁS8j*OF$PGIsM _Yv!c*^"L֖ @I +.V>G7< W%YSc*j!hle$ |2u@Ȧz0.r^LwRm/ \~6琇e0Ҝ]2 MO\7 +}A!%lPReӪ SBsw{@h`91ƃk۽E +ةTRB͙A$tӒrS2JRB8c˶Q2s`GC &!v h4RflP +-Zu =DWd!bX[ƿ̐4~fˢ$AF=G +F%ӊQ$v +|ك\AQJvOЧT~'izݯgz Xi@\qݾUle1`JB͇ެf45,؃(RfMg{PXvn~н؉ꐞx)Z:^sUj,AI["귗+aGygq0B-:  emv*Qa`CԊc=k+9 9'[iFTc䕮 oX v/ _?}c.~i:6AkNsX8GKNpqj!eDlKZE-4a}*|wc,yi=0||3;L@*e0G^]% 4tK쫤P.$.n;mnN@ .B2ӿ::*2v7>tLAdlw.Ռf[<]\ӣ5Ϝw 9_Σb 81s!endstream +endobj +1423 0 obj<>/XObject<<>>>>/Annots 613 0 R>>endobj +1424 0 obj<>stream +xVn6}֮߯}$5mA}$JZURzgHI{iҋ ȹ3s?G!M*ْr4 2n ZN`J%MVݏN؝Ondl7͂9-V` zD݊mO%͢M0;=]cw9<-ri^H|ውy8E:tU/\ yn ŰX#0[=hvCє_ִM_DHFmeQ$6tͫ?p\o .nT;+=Ҋ2mBQ0E(riIgހSURLDTIU3iC*LQq(]I(&Kɱt|C($T!Gjv I\.ZdzATI] +<ʌ.5d'GQԵѵQAUϼ"ExLwo-2 e6x\ueʐCխmjU +g +OdL\98r "mNL +Qk~ xQTאLB8cXYdL| {ept%k`]rF;./۵G6ّ=I{_:0H@^4`Hfh=~09DܜX_b^k9/TM{)8!FB=r8ehNiK+8-/t,BPP|gcnt[w~NF,%~>o9gJ%[W?4y{"OiNuE0+p<3HVAoċM7 /Iu"l-AS/a̝LE56CtAU"ˑy w%.8 +"@K w:0M'}l1+(B#ÄF" 3cc9$K`ܓں4G,sbmw!BF]w1ylr|p1.w'eӸeʀB>q37P]KЂ9X`|h s*0xsp½ ; cu?vJ8Xz,Pxў btA|)oP~㏭9?g-:_̓ra>lG7endstream +endobj +1425 0 obj<>/XObject<<>>>>>>endobj +1426 0 obj<>stream +xV]o6|ϯXZIJe;C\quhHNYR%) (&ݝ׳i6l b4&4ea3]pfS(=16BR\Z +kwJj$A=|hi k9醫 BVdQGNU^b K?nqDjO{oQ|頂† "LJܬ,‚-Iccس>pÔb".}OhnM)1ng}Iqj)C6lJ'|jl2H G tɭ&l;處:{N L~RK+('{4ҪgkMX.ĉewQ[&dk ,WG@RC&3{{s˩_kiek ,_\ y8h:8t*X&.T:t5| (b{u[D6 _=iRؔeGl ?E`-AyW[>`I~(O] Y`<=$hD_5Oz Gb N2(U뿯f/l>ԧemZ|>raލA)@xhlmc;*zD<ӻ3smdЇϢ"~"=2-ݍ]yV)‰R_ӕ5 W oLȌU^cPa6rܞ*vOT]/lZ>@mA爩UDZtLZ4}[7aalX=ӗ蜤K(z"ǖ|dS0s0U$7W_nWCڔqhư9SzI+|_f gsa^m+t Jc'2o}~1MMn>C$u/X"\~:$M !_g}Aendstream +endobj +1427 0 obj<>/XObject<<>>>>/Annots 616 0 R>>endobj +1428 0 obj<>stream +xWko6_q/MXvtCR'C6icoA-Q5TEνG)h`}sCǿMt2<'}OɐF >֔`0'GxaoͣA?lt +{cG{_K$g{g{_K8wN)'v?IN'8~1~J/oڀ9O'>-ңw<<_n^Arv;쨪 B[U `+^|w2xv_@9-V~4sU{W?/vD{q *GQXMxtk:o<)?%o*) +mGn) +rWn?q} N3[Ul<sW|k,tw\*Z)OK IS}ņAYk̴P2 +Kҩɍ^){ .0wG%dgROYF +瀑{^J)},ҵNTk a,P#}[ &Om(^bt WHϔ:AusBo1t7,T h:pcD鲒(5F߭Xg;%;z9ZLjDT\~{#9]d <]au 1c-B$x64_|mŠs䃀J'78'M@56b&VD2bUQ:0j^EU];|>.,*DlGFD1]'Pig:(zhHqkye?¤F(1bN1cZ6@Cvt.3QC2sMpEPߕg,#̟k (OȆy=y{vaH ]5ĉiPF*]o<Ɏ, J30*ƒYr@ +Vh!{ CFo%A`}@ t![+#>-ǰ?Bɬ2be!' +Ra;(׉8C?KjKn!Rop;)+o`NA ժtono.I>]ڏw׋Knrp-y^p0r#ͥ)Lhנ!]Hʗ#?jھe x;stߵ.36Y|Л;h2J&i|_~-endstream +endobj +1429 0 obj<>/XObject<>>>>>endobj +1430 0 obj<>stream xW]o6}ϯoMF8v4 `MC^BKņ"Us)Җ݆#s/4٤{?قf ~~<[K_.KM'GZ{Mxqf7G\j -K59Zk#=4vҨ{~.&WqdmcٶUFwW4w./& dR9*lVxrmuAkEAPn^YC;ˣ]a -Ğ?Y|k68v>UUk8uJG!KtGdw)3G񸰕P}{Ò{_Knm~nC*vCYYK$B:'×b J -nJĨ9W.kO=~;uPƱMco-#L& B C. W-٨m lk×CZ'VG-ES5,ں:-$!>e؎猡t"dn[p=bn]3T 5\Qv7hR6gPl%h?{Bk_R w`) fo# -$CmKO\XXXЭ^ĉkRgzpŇهGB10PBF `80ذ/2i6 {k;S)_"`XP޼!>12lRG-?MZxƟ G![2oTiaqӭt[VaPA–bێߢMʌؿ36jVmo$0yO{2;&a+prj?B@(FpUAֱ>/XObject<<>>>>>>endobj -1682 0 obj<>stream -xXnF}ẈHŎ$JA"X+qcrWᒖ=h$;s bJ|Mi19$I2o%isq{E62*#Lhf,fO[4:і(ǣP&w9źńFIr{<:s[C3Z+9G1-9߻lyCJgJJK<ֲ:$-J<D&YT$a"D:DmQNdv 2jjv  Id?I5MFs@YA -p<ȫDL"ODMR#-ԴUW׻K{>EU!<LJ%<4;Gjna6Ԇ"[qtÚኝܐuŝv)Jv 8rv.om(-%nvhɵs/]PdpZ'( iIEAYkYjE6Xtg Գ;Zڄm ̒*2#!u$2_B}֥8܈TC/[˔ tiqf/,M-B{S=<({(:Gh'*toW@2R󘦽Bq(e^L0EMjD kK\4N\duXhc}qH+\6zT M?p/ 4icQZI@+/8; B -OpB 2w$i-[#@9\HTK 3FC\8<+V-()*T;g<5L@"Ok>Pk6f.l_'>Y'дMerHqE8ɧ4zwba܉Crx8Y\_] ZlW݇EĄ:h0>Sȁo,l#&.&z~;uálO-StXVJt~tXm.AfWSZ)hT<-8c IqƪGQ96,ݍSLe#tC\TȒiFYYVn-FX|bģPXA0ZU^g]Bv>S$D Vs`4Pe xx.numIi*8ъ׊Tp - Bw($ϱVn -L֓뙔hToA$S+6@8F+*׹CP=݈ Tas2c/qoL=gVolN'{U qIeY;'aCځ1{:,UG$×jkbti]l B:uJc,n6VN%2E7 al=gz)Ent 6]lOm׳N{A9J#9"B(CȎ3W_vI(w7Gh1AhX?Wd1O/şϕendstream -endobj -1683 0 obj<>/XObject<<>>>>>>endobj -1684 0 obj<>stream -xWmOHίoM$!t@-=tz%:jco-nk'Ϳgf][(yygf iC:Ʉh tps>—4'd}p5=:M059`@ӴGKWiRֺڦ~o8dӬY&?>|iD%ܲ2΂Iz,GpukKLw2Tpq 9m\MuΊU%|򝮮nQ p&bhX -瞍]Pa`- 8l.*a\Q3*y8 -yKlr&Y DqQ2N L6}66-{X4:קӭd4<`tog]LJP_^(!|λgҗ~۪'R?/*S@΀O QYL*P[10:U.|PLnb%} _Cv>scP$+[0e]TjWb#VXQ> $>mŭf`0VGSC܄flgUuS;t؍qL8!+>QfΨ`O{Uhmkm;<=96oZ߁7IDRg_Jhl)=Dc =䑛E"@]s{N-M[azjg {+k ]RjԴRE01y/𸀂_";ujL3 !x RA&T[~z\- dcp9\i*U!Oa._[ eKe2ԁRCSbm5帴 |Brnh2,/Sq+! e$c -glZY70t.X:HKV*,4 -Tc߼$ -EH6ٖ;Z&PV&Np H5~te&E=2)0!2XZjqMqD -7 -]j>70}eGOK -!1 -lz{kg$vyab=8Rw[An$^dcs1amVFED8P/]9,jS_(y ||z47[Ƀk - p hYdQpN#EBYv -۸۽E^?0**sBpF|Pb<2s>/XObject<<>>>>>>endobj -1686 0 obj<>stream +KqQbut6 X髞9.w), *2,94`0BwNh@D&+Er:cZQ)u-+c5 !rr۽zQ *EéB2 +41ڋ]s{w&Vv/1gz!A +nuMKcTѮsA[n2a]GW/XmFqVcj]đÁqr K 9cLpa9Rp{V\ðE5td^4Sk9ÞY;Gvb}PKh6 \x-yz|q,AA RSxԛX5m r&6Tkg )xděUګȬC;OWWv~%?ӣK 9Of?Wda2rod<$K7=L pnsL@.Dr[U{Y|Gzl#e-v4Q$m#  B}Ջ8qM +Lo0v@bSh^h4fXJ#[9 G& SE4 4a|Upu50K  +7'"uSM2I~σ(qK*"l<Cw.t+* >(TؒQC,XBw165^[T7~FͪՃ$85yOF3;~V0>lN2PNGH@n0*: nd5-Ԭ76SJ7Bi\.h]$&;V018؍,wZc[HI|{*| ~PIe`gk\{4[k DPՑĐ БWݵ7*D\0{LpM@/6`I~e uƮ(]Tnq>fpowdzJp/_e.;q2ξ 5(endstream +endobj +1431 0 obj<>/XObject<<>>>>>>endobj +1432 0 obj<>stream +xXnF}ẈHŎ$JA"X+qcrWᒖ=h$;s bJ|Mi19$I2o%isq{E62*#Lh.YB֕͞[itZ+- QGL +s [u! f +x.ugn)ʵwW4sb4[$swcf-3k(aI_ "͕yleEu.UEe}{iIZxx?PL^x=HDtL٣գJ%Շ$d%8d4GS)~Hk*e*޵؛!x&W,D\ڥԩGZ(1'39"[Ki񯠯w|,Cyb?-WK*yhvl E.c5E;!4 ~gs;RHp\t%Q+ZK<(~#ђk^Nh-Qk{ӆ\s7 lֲR Ԋbmpag]w( !{VՍ%UQeGB< He>Kq@Z^J)H鐏# p^*YZvLzydH[$Grwxjt]|EY=N|0 l 2^]g+y?N\}N&iʔHpOi.tn! =)LJ^|DEq q9(zٶe u.%a|䧐rY8jGLS]L!쥏ۃw.CٸZt谬"6W\ͮV%<G= +SШ6)yZp]@Ucrm<@YD0F>%Ӗɥi0+[G +Va DX1%}0IljDFmi @R\܀1ڒeU ?pv<ş PHc;7 `'3)6 ߂6HWlp`:͍V֍Us{V2d0^8ڙz9rnrpO6A0\i*˘vNz=btX䏆I)/U* 74ҺRꁅ 6uNϹs(DPx#Ƒ չ75|Dԣ2(}s}C( PAƫ^'R-^2$$$t?/ϛendstream +endobj +1433 0 obj<>/XObject<<>>>>>>endobj +1434 0 obj<>stream +xWmOHίoMb T&:jco-nk'Ϳgf][(yygf tDiyOtk˃E2>钦s]`ߧiڣץ4)k]mSM7T84dIv|u2OIxqڣ$I'g4pbx8b\{u_&g{QcH#=j8t؎L m*#|wRUН +>nzMHe!ϼSYs1 guvYE[ܫd0Hɠ5J]]d4Ӵ0+mIׇ$XA+Ux&8=*U hfDqc8L݈HQR c]peV ; +W&}lOnچ{v8߶0`α|2I"B>WУZ4dz#7DR%N,[\",VnïfiK ab_q70u2ELw0Jg@Bz2L*$';>ZHGsTECh\Փ ʖʪ-UexB5kŢTx+HH+n3c` > )x;pi3l{֑@X%1wpN)bSiBER;LA J?NxPJJMהn' ʝG8_ +@t|Aƭ 6؏)`P"ЧiQg-ޜ[DXйD:b -[A0*P}( !f[Z+J k@VX8- A`ɖoH C> ʤȀfl`Ik5a[`0LަߠV(vmʫܤ=,uf*D+MhH„zq,RﰹH, I#齊,bچe+ +poBq_(rȋY8p5kCQ+䦽hn +&(3/"VZt5 @\%%eȢK j2aG;%q/{4`TzUJ pMᮍn p12FKx leXyJB]3=7Ȋ)唛Bš=prdcµb!<\)$u#Hh5303] Q3 L8&sh[>y ޹<^ Gz8[,.-0fG @endstream +endobj +1435 0 obj<>/XObject<<>>>>>>endobj +1436 0 obj<>stream xls0([Rڤ5eib-J/ 80{L7ӧD|1BEA B I(4'$%QXQ )R0ȆU+N R2$*+RY5ڢrQcBB4Qr#?#@V=7Q$"a8diV)')!w) Ak5G+AJT<"Ao A2z߶ Y8R[$($!tT i[(~R0Q#GWbݲj7,9|Hg*z{Btl>%a)|ø6*Mo R,yu^wlŤiבkYv~΢·}&G1~1ͣݘCst>8# (N{R=FJ*GuQJrkIoa6ƒI%Re_sm(1zk%uT(<+"]*v24e#>.-ʒ< 12uߡ"o>|,R6F;꒬#DJpbU1;F;l1:>r! 8[hR"bF(ї\zy)̰ya;@5nm͊ @9=Syue^+?T#Uyl Xl{NT{~Qm8&} wm/ -8|.qFX?E'JMm`Ͻ_.99qzEU>%~"uqiJ>1.9BQ`j4&%{AZa kz=W\ĉkXVX?L~e>{hҙil_q7O ƒ<[9 oy/f_ {phE.)M }s]5UֺF} /7>s313/aYD ގ?H/<1fyF6>S Ny)3ED$ -΂%dCOTGNrP?|yf*MJu03o -o8Dɐ31[^]_у0Ȥ5͚ _lp dzq4 O~;' endstream -endobj -1687 0 obj<>/XObject<<>>>>>>endobj -1688 0 obj<>stream -xTMo0 W9@p;C\Pd9V+$7Ϳ%7];,C"Gꥐ7 &GU 'PTƓ|O-IE8i:$K)!4LjGO|R<YdSB. 3Ρ]LFGIXT4kqaNFhgKn09%I )ro -8h$jgv1kξӐbɆn]AW7I ֈ%%jtZ*I2'5Ιށ2<Ę3;P Gg%P *c(j}OqM)L6̐ qO`j6gDcw$o=1N3TGG[IUMh׃dCw?>H(HR1E z˓Oz:KQV9by-+7$R [>/XObject<>>>>>endobj -1690 0 obj<>stream -xWn8}W pjE/liBKŵD*$WgHɱU/(93gΌ.&4ƿ -4[PZ]1ͧdA%~OJ/hL8$7xGpdA }}G1s^,oh$XKK;U:7^Mb#|'ؘ,,$Y{k&+&tqhtfRI93K4yS-92ψWLATAД2'oZJm[{& NV$&5U-,劼 +W]o6|.a>$h46->PX"ΐVq8ٽI1 A|0g=]̾=zypDSYd"3Yւ8,Cmw6vm-aͻȷҾ7R9k|\9/wNKc V8슟_&r4['Hy;^t+tu}#[4uUhv񌘕\q/CH_>_}wU.N֪RkK8+s{]g @?΋Ƅw֐zlKWA8u1僩Fy5wB?Ǽ8-EGiLU4xx4c{ch:5& On- z}PcLc®Zh U=|+Q7GRܽfwR5j߸ Vn>_+;ZWk8FUo<moopnike+Z.VÓU=A&c8]-jt%c8~+̧it3TK!3n}-k |*t  6kaX<ϴ2:R@pIa:^raGUP^VAk +bVĶȲ5uIj@BPNC[s;LBp< +$Ηx.4K j 1`0DEq9. +y2T1Hh|8 +AO=2 (OTwQłJ1׶&[{ L{m7EMB%2~@'x\F0:z_'zhllb8u6 W,iىXm'STAsA[ha*ERg$ + +fwp@fX@eslxR&*1t,y]/գ'JEi:7#hqWm*>Trug8k"u1,Ku| bE}x3evq&sqE?hRksm#jDGoXYfrskKj+N,1ijiy8F*`^F%ty>(.}"_O$Q΃nMa|=|DF-1 ~Ħ8DA;=H+ͺ7eq1#'?V4C#yɒʹy>~eqzQ,quy+&ģ|lrgs4ޛසaendstream +endobj +1437 0 obj<>/XObject<<>>>>>>endobj +1438 0 obj<>stream +xVN#9}+jyHIJ.H;;$JHv{pYM)w!a4$v9Uſ']K'Cg1?{xYIY8莺ۃ}=n )OCqVԬMΚ4&Jpke&)yCK-ԆKDq.I=8o;:7OIJLYM+kIr >qMu|uiL( iҢTxrTJ 81K]89M\+iQ5iHrυ䋗FsL)1—BYRZd@GjD3kJPxD'5iÎ9iHGYLZN#c\RԳCHg]( XǑv.`Vo :IVJɈef2k煣ϯh6+:gn~=O qZA"RW錪<@M=Nf 9WT/9i@UijsxM^zwAG(72e:?g @QV0 _y{yxL"saC+u`xiH9D ĵs 0tY#%kÇ W.K(@( =c?ӚB'J{I;7λW5mYP,zr!/tуz?3IҘ;6gh_Q@[7 +B3;\HPyV MoEI=O]AİOi%,k /tɥZaem >f%{nh_whm޶~V!rUf hc}SzhHU 1G}A\GD0k}X!6(=oK A?m)[Fzh}K!m5l/x!q ER[,.y80NVY0Jx2~4ޯὤTn@Np-;ѤnkօO,X6 jg(F/ɸOg+^, >3I 9A1k֨  X0ڝuנendstream +endobj +1439 0 obj<>/XObject<>>>>>endobj +1440 0 obj<>stream +xWn8}W pjE/liBKŵD*$WgHɱU/(93gΌ.&4ƿ -4[PZ]1ͧdA%~OJ/hL8$7xGpdA }}G1s^,oh$XKK;U:7^Mb#|'ؘ,<$Y{k&+&tqhtfRI93K4yS-92ψWLATAД2'oZJm[{& NV$&5U-,劼 rX!'5D}ٜ.9{=!X{ǥ3W(K<"t,8՚ػt?ޜ;B$K R1YZ'? WeIFm\X92e0>$3F9FJY*mK ORd6 E|i#Q"{tRҙX S_Oi/C<6O9 賁B<ܹCTr_HVL\d (SyS3I5Bi#Ai~dM ܔ\h%Z*[SB֥Ic, 宑. -AC`ا}}ִ[%Ӫ҉4O+SHwW }4U**nhq3p#k} hq ъ{j#=;3iS`1{1 Jt}Ӱf{ϯo{VTb=V &fU^{Z2mU0QnPsAhzαn{Z=50\+r +AC`ا}}ִ[%Ӫ҉4O+SHwW }4U**nhq3p#k} hq ъ{j#=;3iS`1{1 Jt}Ӱf{ϯo{VTb=V OfU^{Z2mU0QnPsAhzαn{Z=50\+r  u/Qa( bcJYGщ] Ig[+8KֵO4qP:F47"9᮷8O}k8HXdz}Ea{Zy c 3&2tFϢdD7SnסB?VItwW(/Gc ȤU,XL yi0rkpK{ 0*R»8Yж,K"Mڳ'`cE2r_hH>pv1m /DCr>{LYHk㜂D$\A A;DC*3cgs -(#e&U{*1S4ۂقx0NxdfVUVYlXCͱ,?*uͰa *\4T$#ѡqΆ0OT0ˮoċc@U5~9S6a3G wE fWG;سJg~Y?^jx,Jd=TŬh̐ҝJq&(F5S"8YMHYid2On}0FB=rG8ajjД7hT0C7Ԕ-X(aEV~Vh^=畖u(ҟX=Zݯuu5&$#;|U7f;UpT - @am䯕>E2^贃3+ב[|o«,Yt5_|Of t' aqiX_|% endstream -endobj -1691 0 obj<>/XObject<<>>>>>>endobj -1692 0 obj<>stream -xW]S6}Wܷ/7BLXN-'Zd˕d v:0Ėt?9W`H i6` h<G#g<Ÿdp<Gi'p|L˔i0e<::ӟNq`@4LynJ-fFY4_n=6_ +>mNYW ->O7Na>$pO{էSw{n*Ǡw@H68qpMfh6 lj<|sendstream -endobj -1693 0 obj<>/XObject<<>>>>>>endobj -1694 0 obj<>stream -xV]oF|X-ZdEn6 -ȓy1uwv%I`Hُ/'9M✦s*6'lBg =ǯ״Y6C>f^/O\Pr -KBɄ(lV[®|*(V -U+SRtTTk@'cK tF2niC]-08F^itA!8(\zQkQҟFZ{2kj]C -cIY6" ^f]9Aԥ#Xr':Q55}n*[M%bPq%\e  Cӱ%}xz,.H Uh4rTa[XGxǝvCQnNݲ0P"0dG>ؽVH? 0ϳOd?H{xVh;JH*iՖ y]t -XL.+1 Jb4{zv\Sťk1]u*G, IDJյ @ԙv4v>J (}hwL gF,:DfN)lua-w {c6`fӋO:xgn\\ RXOrnl **]<N{EJ: d(QAr:<#.TY CvP#wޢ؈3AB6 -rtrl3~}3Н?|GP1)fX7o@M2l& {k(lVvAUSmEƚhPԶWcjOgiOYF5xwĜ~_ Fkh To#J#6#ZCtk\V -zj)8sp6233As] Z}gg зPuyʋ$Oi&(&NyhF/8%<hsjh y04mRe +]KUw|z҇n/06D$.JW?be?I%jq$N<3zwN 4WP( -]!CH -KX<9` 4yKqp VȏX^YkntqX@9{kjG+B)Z{+6bp|*l$vbt%êad%k_TYR9uǢᔶn?`k\iXyy治 9n)4>z.\QpJ8u4`\qh,[/__˓N.!,endstream -endobj -1695 0 obj<>/XObject<<>>>>/Annots 630 0 R>>endobj -1696 0 obj<>stream -xXn+ -ތ H M<1$psڴȦct7T7)r2@ S9zbZi2E#|r"|9FT8DSNW,8ZbuO:EsOQ4nxXPAx6q|أY4ix/MX.{#)͒lΗ.cO3.bj3V#9 >MFK?N _\ R&̗ ڤ.#$O,VkxQ!T#Sڝ~_DizJ{?nP{d AM~_=?u!JT[̊2/pA,xNs,ptF92S:8XZPvP{K1!u; 38{=}y!=f6FO}CgW\ײL̩rT k$5G6xzl e*}-I]$Hnєg(pEj` |Dj8U\ -e[vRTtoA 8 8ݍ[L{E +!@HwaEicn(w 9Q.3YY;X0xnoefM/>5p!Qm;iQbF׹Od[*c,J!Ee$fN6cJGL#)b11#VfpQ`n3XKȓ,p( HgʰUF>+@,?]+6{!1gV< ţYMܣM)Yхh<,8$U xa>xɓN=3ns=p>yߥ۷7DĺЪ}'mlҢKx#g>H*II;+jyh ]q/hl{[qc -#~26Ԁ P g8F\9/((~^ -79ۑRd G@|Ko]]ӏUE屉> u8x~c3I]~\,eS&Tioӵ~TR<^;2@2]&6c׫0046o4]1 -枥%Tr%v_]F¤żkݖ^í+*;5.&SW ul̋Ĩ䡍[d4Cz9Fzx~`Xu5Us3YeVy\QgȓyۮD_?SS+062鹀waV+l},F4]L|.^ oNendstream -endobj -1697 0 obj<>/XObject<<>>>>/Annots 637 0 R>>endobj -1698 0 obj<>stream -xWr6}WL3cyƦudI-y$! 1IhE߳)SƑlJٳπCM(ɏQ?hJ$SNSFs^O()/ WW#|6b/#iu4i8Ēlew+i%H=>-(DUYjdJf_i.͓4d 4g)6Y1%: - F#ZDR&4KIfI˾*59R{p @)8N2% G0Jڈ -PntpH"$9M[mi܆(履22q8=|GQoޜRZyHI|jZ |8pPXWf$K0mwW|\havP[L -؁'[5NeT -l发X"m/W|9t6{8&䁋\%N^nTNlpԟR~$Ȏ{ZsI##RL'f$ vQ=]Ȑ=grCĊEt I2a-)KkVڸjdޱu6.5L.P/c+W|qpx^(qCΚ/0_0R)!ɋ!^X_+ -PnOºtLuP(7/8ɯZ2zTɣ?ڍ(n6XseY${T2;7dmkfpVibT8 pc4s(<8跁UAXX `tUAs".OBsgټJ:Kw_ng1P5h"!öJ6LEƵ ɀ َ*Δt/3Έ²{uх=Az(47:dl[ŹrFSRڮ`APGwj[C``adr"E,*`($OmQܢe2G`|!{8s`7|taٝB;³òuBko@m6ڈP7@lCuxfZ@]8Jn.S -=b,mbDN O- ˞ z~HL)ӕqWp`#rQj]4 H4χB|yݰO9Mplpx0k fX^2Z:~ױc\~v~ =)wA;M="pYf?t<9%"N6WYzRf (+|w -2Pӳmxv_&Bիvs8V](v>3S+W'٧39ZdB@`'4JS%程ntRpB@~reSҏ`8`7wwX`94իc6X;^93G-HQ -oT:UrMַc!T 1^:Ⱦ?nfX'K7uKEl$BhIuʵίeͮM&0zϯ?Ff:xYlǕ ܒ~zOtr<0w?W@endstream -endobj -1699 0 obj<>/XObject<<>>>>/Annots 652 0 R>>endobj -1700 0 obj<>stream -xVMo8W IJ%;|H`7&z$aK(GIf8ސ#f) h$ͼ" -9_ig ͗\zKrBhh[ޢ٢f -x͢km%2U<{[vc:[4G~gk:?-\y>\5slo~T27ՌV١R۫mMyLUsb%+R/Q|m4I#MjvgvBrMqJkQ#|jYmH'N9 ~Ni䜧S%il$ΫW"oJ T*w%y%=sA-7=p␳l;~A@EwXp+6fš/awLD#9u!547$S -Q&ŠJsl[uRгmżvo۶$o)ZM?]+LN[vν̣b_ۢ6Üa3S d0ԕ`BXZ],DЀ2Ř&\ cL#Sk;SN:U &SKZ7qQ'W  !=jߩA^hon' {#$<74$ gRdV'7%`{1G0sUQ1 -*x>p<#:pꂘ&A2{63ns"J3Ǯ^:v}w{nN9Kԣ9-ð׿_R>6 V e >i&<͘y477 Q 0_}ڌ HJjendstream -endobj -1701 0 obj<>/XObject<<>>>>/Annots 655 0 R>>endobj -1702 0 obj<>stream -xWn8}W Rb@K.BKT"U3|m&)Μs8vң.~z4`DiqM4N 'c㿕 $Y@[><:bcAdLuNӓza2/tntI%Ɯh]-(D <2RXQH/;=t,>ɥҒZ;*'iJgJ3^͔7Ox. h)XUC6BEL> d|DbyBu!QF ΍i9ZMX댏󁎧 -1K|%~\Phx2ӧ$Jn8Bz%E,Ǯ@% -h88cr ڋ\tEb!VhTW4e./0vuZkt\)S|gn왣q^64oʽcI/0rZ,"7~"Szet$Ac;z9?r ?@0DQ25[::'yỸu$ > ʐۺ`"7t:TP`ҹjTߙr˰Ҋ<)`Acj3yyRZ2G$͡H45CK a=6A2O::T"H:QfH=lamǼڱ?ZlyAk[5 =TyFX}s}[A0VXɃ3)r(V-*/AgZ.;D -VǦq#;p`6Q#@|@@@7wr)-NJIf6- Rڡ DLEv2J?`;󖇝cxKxB|}U -@'ƺu*K#}auqb7{Q4=nvɲ$]Nd<w=;/ V?#XQi4ЌB - :k>/XObject<<>>>>/Annots 658 0 R>>endobj -1704 0 obj<>stream -xX[oF~8pV)$ZIŎU$@#r(1!gؙ )ɔݦ"kօswnh@}h<Q?Y43RGO|AY4&!׳3 hBh2Yo,L+̓4]eJmm%9MJn_0n]MH~sR%2!]J#\eʟ/sKҩ?wэz1rԧ̒ P,FW$uFe$XB6G Z<+dnC<~YQ9]@s.6w/ڄ(:cncCTts!p^AEdT[J\=3}Ib6`,o0a!P-,gD#[Fo8ōӳ_6Zm+0v2t4x>O[<Y~4[V0 h]K)yޖIFx79tg4WEaxoǃ}$o4 3fv(^endstream -endobj -1705 0 obj<>/XObject<<>>>>>>endobj -1706 0 obj<>stream -xVo6_qUiO*! ! H϶R^2mӺ&16vJٴ}6)mھi {l7$N ٺ{>tȋ!J|'),Y= `%q,0˚ Qb@l^jr(-$a -"9d(ʵ[ؑ{R\VN,4Om!ZĚiGJ$7aVB l^X -}!VXe -S/Ș'L4 wT8 %Aۜ!ȃŚrV;|4UƳTL==T.+淘~V`ZmO}Û>,тux ϔU`VXx*v}/5(9R,C؏GA؋dE t;QR[日#{IQ8z1O5S)AP {~wd}|^dzE99Qr%%+ W>/XObject<>>>>>endobj -1708 0 obj<>stream -xWnF}WL$%n}p5 (XKi%Wq=K*D%F!ș333g! 'ِFSҳA0lLikzZ)i)yN82L36O2N SZ(uMq8"hiwV .~]LVKE&eTx\\8"Λw&ϥe콱}Lr:IJ~YGt9{([-ZvHh]6߫$W(H;CdZ9C:b,mtRi=Y&2&De*QB삖eA$h8!6yA*K8N8&h4oa9c0-x.}r,w^`G8.(9ЫpڷFg _;OZ=  -XڬSZ^.o?,U"g?L"4 4v}S"E'+iCBĮא~:N]hHeR"5lcU˞ d̆lJ}itׅc>f)Lˆ_2ʷ>70}ƼO977;DBN -j}~xܴ@}ˮi)G mÝ6 R{ףH3s酫%-鱾 XM -vuwW%TaxET٣3WE'>buBt'vd 33%*/` !c͏-)sis=> | qy|wa1 NPRZ@8Q-OϵYS^,r:o -'=x 3;OR{ - i  ^qV (tN&8wGT:]ؤ8_`{96CĸeX?qwبN{ZH ^I(V8}crxnĩf-Vcils,V&+-FڶRbp:]u~zߎg`6vOCw sq?:endstream -endobj -1709 0 obj<>/XObject<<>>>>>>endobj -1710 0 obj<>stream -xWo8_1ߠIUrnS{Rݝ2Culj;7$m@Ownh7o޼Vz e^؃" >(7_ڽ_Y.a`b@^QG\9n\x `"-LAOD)3bqv6ASc"n-:I7-7p{\^q)lO ü x{s~  | -U21kfm \EfvX֍6qçBQnݜ@_K&&Є78V:MEC]3;C1szVz`ؠ6iQ3t8+^JuR @Ӽ*,`Ft -c$^q(Lm:;`-:W8:XphbgQZ&ɢL2H~uIiXt^j(&EIV~cKCd¤J-9W1gA΂Y6BJ{$|v QͰp“MaAvUJ=![#j%hH؊{iC.z_-|2zn|xU(;.nAv"&UY60TfwHh퇧6zf#^r%y^&usi!08Jn=uHÂ.o3I0OatKwm~QJ~־I(@V`'){Ŷ{eP*Lƞ)m:\{_ek? o$ҏ7?|љ cOZmC;W;~Hgd/~ z\ȋv>XGyѣBg(׋dُb/[c9?!urJ -s/0|䀊CJP-ŘYz-Q/&_|Ұab:da&FgjZ]Хp.c hWCks Y)r⓷cBJ;zX(ٿ'v(7` -t;qNbYΊ?jU.(Pe1~-a<xr 5) -TI-g40 ~Oendstream -endobj -1711 0 obj<>/XObject<<>>>>>>endobj -1712 0 obj<>stream -x+2T0BCs#c3\..}7K#4BHP$YSO! U!?M!3$1''$3?O3$ BOzs=s3 -!)F #\C&endstream -endobj -1713 0 obj<>/XObject<<>>>>/Annots 705 0 R>>endobj -1714 0 obj<>stream -xIss 6_Zm9$Yҡ36EXj4ѿ,93\*3++S+¢ }XTjpq>,qCQ'#=̱RpYN\NeҀL:t9Y8c$W$ HVSyHa6بv6Ivj5YY&lpVW8)HChQfއ(Qb-cA#5 8Xl(3E-c$Y[tNDiY+Չ{Qa3dWV뢴 :,:,s9XS\S.vQH^DQqưsð96*^,b5am(*XkvXXlT<bYՆL]Ĉc|ʬÔTG1QljI/6k;zdaX7uZX`kRPp -d,9/S A21lU*uva Ϭ -vgֺJ͉:C:z%6E$BjȈFӐXn:ق8aXlQ96:EOSXiϕ jȤǰ֙_Sd㘝Y5bX;qN}5{ [ -T1,vTbU!˞ð UfTfV0r*+밂l y>!saD 2K"z,tD0,fYltPrıXs9:˙uX5{ DlQlLa̒wbXYTaXYa]×q41b&CuX۵CYaJvrXpÇ8V '>GکDz K9: KL): ;NeaF 91lz1!ɬðNYa'+ٳQ=zTÀQ]b不sV3YAXWR&=V40,#܉ -dŋ±VąUF8c4Xaj: ʉfaҘyYUٮʺ qY* -C!1KTcff0,4s: P|"0,ٮl:rfu Acݺh;߹Q Dr/r+} T> zh"l<4V\v%#"8ST&  R˖ I4fTk Am"#'ب ]L4 [Dz tF30괏UJŀl:S4s2~Y-YYLFZdA8;LR-( !ĜSeA) ]34>j1ĜWJEd4>hzeLF%cFCsH)De%qr\ox9-'X݇Y?nR (p,2c9M#͂t%gO_ 7<pymof͡Mm7k9E\{O.uجku߄!|]w.=vpy=uׇM{Ñ7m_B~tmC4u۵}s菓g3ɔU]ڛZWґƕz޷h}g2MH2Ϸ$\uxkMyɭ3 /= “uUZ'Wvk:i;5Z/.w -kR!W3 :6uq&fC6a|mvݑ(V [\nwZH_$C REx$ds2jeC9|u}0.]V7]~{r&~o03N󧮽?\?b F҉o2x$J`^t nR6GAK^:oDeEn}_:7bp׻J跜?v7ץ)c^u]vʼ7 o}hЅfwg=MyE*á(Us~;O߽z̅doloǾ >vœRhUTH~T/]1Gre.Ir 1Bylo S$@YOuk*>cniRױnR|ݏ!p䇗/0\7׶>xs!W Uo f=j8ݱu޸cDn&xvn.fo uۅo6}C -˱n`~zXL4=wALv> Yʜ3MyJ:Z ˦b;{쵕чxjh1?I;SsIC[q'iwWk\viekZ|4Kqh8:$`^أ+h4fOK%&\odcL*W|uyϳJendstream -endobj -1715 0 obj<>/XObject<<>>>>/Annots 707 0 R>>endobj -1716 0 obj<>stream -xUQMO!+ޱ{0`s4ݍ5wАyyo/&!HJLpA/57Vs>bak\{HQ]VBZbb¸ĶPBQ%&2,hV[Cqƀ-[:v!%6J[+iGGH)DOKGPCr{'[a+(EyK'܍~Ð֩,KMQ܈6? )'Դ-mJdͽcD\qendstream -endobj -1717 0 obj<>/XObject<<>>>>>>endobj -1718 0 obj<>stream -xWn8}W 8)i4[_hH/IRl%-$b9sfـdHKʳ~OQW?ğ -5 4_9NdҸK:+`Ѭh&'V03 ^u0ԙ[uԝʬqfIK7R#yC~#`)^+%j3=y8c+.vo/2^vniZ-S|1,Ev -ppu1ib0ߘR(Mw\"hoMQHR%{MA?9rHMEXmoӛٿ3y1v' /\:Qf - &JlƐr*W~qS/÷LRD2*ܜr)p(>5u Gm"t)AdVȑkLR/ƑK?cqL\&f ^& -w@FmCNQn Y֚%& -Yi2A*2q6 *P(:V:SY\NV*IJXS]i-p74,~ *לYe?&7Y2J眠rY -zkasH]+W U \vˊYu.3j[aE)QF ݉ -=}8~Gn^J7j72SL,p9R4o(- -bJ{zU/i8B+2:3ᜊH;/-]qyhrYy`9QޣCx)#.e&bUTn@TsҘk;nM񺠨o28Վh{D) kȬ2V#J7TAZ,MOU!BstbQ+9*])5==M^l/jZ<=BS-'^4ๆ]g[yո|t;'^DZwB_aކ^lm&;faeɠS+3.ֺ8~&,릉Z+ 9UbϟG ^1MQo E;JaqJ42>_i(G7B v(Zt求=R!vx6^ʎ bb <+$vf%kU.q6jkT^9[ M oh)lsvk,? gi2dANe+5N}6o TFmWw{7 -'*njl쏳endstream -endobj -1719 0 obj<>/XObject<<>>>>>>endobj -1720 0 obj<>stream -xV]OH}W\ƍe]iKYū 8bϸ3=wlC0܏s=w~4OL9-VUghFxiY9"ܸj-7_VǔHڬ) f3JɭB(+3olK[i~ "OoO+dH])!@Mq13PѷJ GܘJ(M֔%Sa,UJNEYÅ*_> b[|bjG"繽 -w PYhb@ '#Ul7,wЩ<(Ӹ91T?g[!y~|@u8TN>/XObject<<>>>>>>endobj -1722 0 obj<>stream -xWMo8W |N;Y`v vBKF"U7CI6ie͛яόsZ()wZQ%I #g!<9MgĀ&cCkQm^,1ڃ:8jQ -T$*sγ)}:1pc〞liWi {ȝDbǁRvoh[@""c`¾mcZeTDeq+C#<WX M ryǭ덜U,9 P"E*mreH>-]8YNm wpeΣ!!D3Sl(s] PN05rQLs﹡M\Qp=-'dq``pA7(۪""W*Jyz7ItU)m[5(XA{fT+{l!Z 5 Tq y  Up7 G(PI1#&U$ -_}$@4ggHr7FA-L(K^ue椵mj[eN(̒ @=0v3a,{BOW=oA>\/Cb\\w (endstream -endobj -1723 0 obj<>/XObject<<>>>>>>endobj -1724 0 obj<>stream -xXn8}W b;,Ї,tw}%f#*I~!)ٖ[m"r̙Q~\icOfFyu1F4-Ms|JZ_[^\k\- h_f&'i_"K7Vwܝx'sܽ(= \Tt+?5~ £ $'h[Yy奒ߑG2&pf3ZnwWj*t$8@h|SH8*˭Zɂf哠xuʁhQZ83rRɹc]^Vu̬4Rt#DZ.ސ| H$ 1T|32c4pY] (Ctr(7Zo@ @HJx5h]Co9C,K&|imMS]3 ̚·]$HeYF;fbK[ f/Tg#ץ8Dx0t{< C-l,S\gN4b WH-daml/àUʶUwpyHVp-e*kdJ{ 'kaU_ȴyu~|@  ު,L Р([%1*L=ǩObVVF/[#< svBCB>/S k֞s]Ju7lQg`2lh] kYs`$Xe1D/0 O]k9R}PQ.5*J4Zn5JY͚~J -TكۥȞ3Ǘ7$Di4-1WtT TOmJ8Ω i\m,zCR&7<$K=_͈鄬>+N]hdU#̡&_ccgxM<:](d $/aTߢT+n8aՑډ:9l'뽦S6e/|ׇ\XY;1HB9g c1¿MfsbƷc@U|<(GJq8Q ,6xkjKƨYNZf5l9_J)-XA.!P"ՇOP}P: 4U[i|t2?fLl>[ęs3e?./p+endstream -endobj -1725 0 obj<>/XObject<<>>>>/Annots 712 0 R>>endobj -1726 0 obj<>stream -xW]o6}ϯԊ3lִtDl$%)';d[mR[ǹ{lHtDʫA6g٘* /%i67 _[A6lFVl'n\]e혆CZd6EB"-ְj<+HaE%ri)v o'_rdVE<;zTR{7icxjtog/Ӣ `Av -*=?';fg;[}^K |"/'Q*^]Ŝ1Sv=r+K>֣xvm 6迚cM -ui.gU -DԀRn$lDd z$Bx.ԥ4vVH9]F2Dwl]FoNEYh5/ | `kޠkZy^V¡E%Mb L<cvH%J`6fdX[%A:/<6 -`c'jaWASe"51_z3:QĮNu2xgTEUuEH=)[PIXIR"^lh#~F+ѢѝTBJӜc|C{*n et?9 @]wHX.q_\|J;B6$,jk0$(7KhGn=}c;`HRmK[>h5feucv*NҒF_D%|p{g,_;IZ*|*λ=@q,29\3[gŲDE!c=7.kcess&4`,_[4zkBqN-U*SN'rg-dM60l2G[p0ݎFbl4א@xX)@)֢n+yr2Ms4!㞫G+UʔُSҟA _AUsɼ0boOh\SЦҫ;?|9լ~q'-5g, bPQOՎy %m09zBTE:'$(Mir48`ouf~V59" ξrCJkwn -y龃p2ǹf'>@A͛X)H: [ad܂V<֡Bn.9bO8[eSG[(BG_rmOOԪėN5nB8=Q zH҆d?8ZHib5^9S'Xvǝ*_&-"?"%!O8UC^I1_+E<4Cy\y1)a @~o=kux9x!fi iUЎ+!դR?/n"nǃ) [1q#hH4.i27_0j;lMPԁ75< /?v<g <7lkendstream -endobj -1727 0 obj<>/XObject<<>>>>/Annots 717 0 R>>endobj -1728 0 obj<>stream + @am䯕>E2^贃3+ב[|o«,Yt5_|Of t' aqi:X_|Kendstream +endobj +1441 0 obj<>/XObject<>>>>>endobj +1442 0 obj<>stream +xW]S8}WܷvH#QYADŶ\I{awZے9犟!/iD' jCh|r',/c:`(1gS6_ +k蔥6yo0h sY[p f1`+Y^}:: glqo 0q00# +|yڥNendstream +endobj +1443 0 obj<>/XObject<<>>>>>>endobj +1444 0 obj<>stream +xVoGbTUHg;vRU)R i1e}w^}3{wM!̼yǗF|L۳Q6dӫ9~kZɇt͞Ϯ׋7X!jN`4E1N/_.>}8 +7 +SKSPtTl]k@'cKtqcc@ÌhO1p R CpPf|C7n?UdVԸ8ƮIYiր" _fm ‘-rUdߪؚ>1(Ok_%P^㮝>{lu|]$5m4r1ˆL Ç=[G=]8Ft ca?Efa N|;V~`gyCɾ`wBqٷdN3*{V[b3DuI+7@8grYqzWZFsg%8gKQ{_\ڛeZ]ȍ}tlXѠX$*-NTUoO)m]@no.U♈Ʃz]/`poA ]4΢C_[wNa jك[7.h ?&PE%i e/λ.JPb(}P7WF3 \Eб'*[N'0|u~bL5z8d{1E;yW`Fl(xWB@XUo,d伛웁PI[y·hd dGNLM6xJB;1ڒaR?+A*_mepNJsM.ӴM,Ӽxs^ 7ՄfQP^{ +(ZS%EY:nd0 |gW?g;9+endstream +endobj +1445 0 obj<>/XObject<<>>>>/Annots 633 0 R>>endobj +1446 0 obj<>stream +xX]s۶}Kܙm꩓F>"A 5IhYgRe3d:"^4ğ#()oN}xu34[̢!4M*<E W'hF,`q1Fu 0Y77Sxyi:흫~ C6OEi_3^? P^d/JTé_s9+bgJS1PO〃t7o1oEX048"}R UܞH0;τge]lZ`aئvumݼQu,^HDSc]Y*j,4ti埵,WLj>'@oCZ| +%wlǡzBmzDcB܂Jqs2׀iܣ1F 6HX2R 'V uH3g K j%LڃrKc e])(lqҘ,_ =yLi$EL9C:f\`$,C;Vdi \b+tҙ2lzO +ˏ͞%@s ۙUwBdFVS9#e+ˈM7iŔ2yJ f4Ilu.tm !_h0=[W6ES^B=$S#ov幘FHש!/'&4T,ϋCZBMYKvz؄H [wJԊ0t)y(;Y[6ϫ8=vr (+)dqm3L>,oi3wb\q*~ӯGTh5*+,0+<#7FME>ӠLvq9h|OiE aY`eqlG\87v_,>ݐP[27ᦣ5 #)IrtJ}@a',zNy枇 w9{uۥJLgA0!lB C3A;lŸq<]Tz/?%SϸdtuV5 qB >X5(z@!V F߼K6{v, Z c\=WO?-?0!o?χ7s'|ј_Y uendstream +endobj +1447 0 obj<>/XObject<<>>>>/Annots 638 0 R>>endobj +1448 0 obj<>stream +xW]SF}Wܙd3'6BB'ʹe- V]]v8s>M4Sl}'4>gFq4>4 ³N&80럞 :§ڰ7kf{4[ ɄfGMՊl."mΟR 3K:0"+ yBw2NܮTAN[I<7B[,u`9ЙS"?iHM2 +!|-T̿\zLTN.u]> )t|=:(!p] +kIYZ'JKBg0 +4o8fu ]CN1Le޿fIbѣ|%%l>^m?8vXڟO-RlYυAilT<܊ +~8证ӸUZiѺroHe '  `lx[Q+ai.A*:#bZ~ط$ z|{$`&EƝXTm\{stCE9O]$mtIΈܢ7] +(HgcQHLXrkyD-6sFX +t5`-+XRP XU&E6FDz`ޖ"d%V,`7խò>"?}j6lWv@]uxfZgG& >'D=)r2P8m6}k$!?5@0Ml AT)l;ҥ80+xT0ё9hAkpI#7qyyFFA&|6( m{o%7*$FBO=w,UgiH%gI  'z}N1@Hޗg)]Ey88$"ipPl_[kPU|'J@Y9`?oӭc#4EUEǼ| 0 ,|U/ZN]G1uP ?wHU@>{і7L\Ma.>2YP:7$, AiؕF|:\ , 2˦8JU+[.W6<­Z u aꤍsۡvXaCv +D qQ0X~ wFڐ@wmHPFFk._myhr=C".B;/~%݅(\bs#8HACKϮN5^>ۈsm]xsfak9@`09PYp!b6؇8?b&rQn+z.+[!~ܘEm? G:B7\rJp B +aUjo>/XObject<<>>>>/Annots 653 0 R>>endobj +1450 0 obj<>stream +xV[s8~W %3`C-;;-m¿OoLwBb}I?>M2ق|04C/ys3?_f fު^dt?-sZYOSon_- 瀞2oo=ղ*V[ +b9"1ݢld v2/za.}l| +Z۷Xv9 W˖^+}`oP|LMiEZMi"ΪS3:Yʉdf( A qz+#iz&*'jf;^ +tQ%Bh8LcKq(1Ƞm9r6 &Xp#g $& iR)9D2wDN44jF{e3x'1~XE,O%QDAĭsPmϪ\GPrڬ?l޾a }C_n׵!q<)&y҂͝9>mgܥA|M4 hdx Np-4~M;Jw=Ԥ#`ARj[O+Qݔ\[P`"f_45N-5߯?^)̅ވN3 +˃fx957ґ;~>܈4˹\ƒkf?3endstream +endobj +1451 0 obj<>/XObject<<>>>>/Annots 656 0 R>>endobj +1452 0 obj<>stream +xW]s6|q]&фƳ)^k$h8G.`_]`vsOe._h0uq(K/Nzw}E +T^$~>-"[X6ooJF[W\ҲTT4e:|iy~tҧͰtX1KDY/A$6bYDͺ8oV~t.hź(dTa >oLY'#Yцtqr  BХ4UV*yO g;4(4]xX֕Jagh 4U_A̩KL^$-@yO#YBeAb TeNRau٩TrKRvDg&uU@swowZEBoJK(Zp w7auS~r  +LK Syxn =FWYBN},k`c7#1֙a"EF;6j#QI5D8{y\p~%ث^TYG,[ǏI)> d=x;M䌔S$![XvڈȚ,3O @Pi.:?/p)u s/P?k+X +1ѓ.#^ί y sdm=^mH%lUEp8|D RFz\|nZYkx5R;T`BՈ^N֙^AǨDUn3Yej64+ܳP¼/6iR9穀J " _!|^&[FQv(qLڻɂ0]Fz j% I5nno}ڊ@U,b\:Ƞ70FwxAV,) H;S(L[PC ~ +Z,\peFX|5H~xBp A6䓗"^>nu(Fmk-jZ= +፛m0I S*`Fw{Z 2v\P@ZSj ~cԉzhdZJ#ȣeX?`OD&anjg>Vf=.D1isq?dp䖘||׮%I;#zC, [Z KoA/)Mo8mQ{ţ! =P*v:38lpȥb7oGg["^F߼WS ++#37ߪU xl:0Mke$t*@n'D쭍a`j-&6ro~'yܤ[W<$Mxn@wZ??cdw8\}pendstream +endobj +1453 0 obj<>/XObject<<>>>>/Annots 659 0 R>>endobj +1454 0 obj<>stream +xX[oH~ϯ8JBT M)I U#-0cpb{gʿؘ[ETMws׃5E6uO^ͮץNm$|GW>G[סZ͎#-WgjhBAߣQ`oȯfU<̒En"R( SCJ"H4&&zki +3LdR(\hPYkz&&5ZG^ 4-=͠)MpY,PűZE)WgTӱ\ݍڛ"~˴@ɺEAzHu. gK6IZ^4>Kr#aLOp3?%ɍH& k]'s汬<QzgMilP +co:;h7QPx]ppMz.HIHWyj&f8#5C>3U|̕p+rS +hw]X*6XiUŭV1Yi9F4bod|u5 0K(h8ߢ$" ,rW[Tvg|،zyW~ *xf/"H.Qj(/EЄd%{MZdj@:k-$ +#Hh`!Y,[)9tC`bp=2$M!\ x/H% 9(,uys L:}PHc0_RokJ&C9ׂHI,_C#VS2Dxq. #CKSX)v͟2Xc>ȿnHSD:}>l2晵T"fVFh@v3KÅ u1=WlY9ue`]ny(U\X8Z`Boeg\MnAEGsœQ}6ԲC;N!D"ٳBN&vd^_G Jp-y7˞hBcrDi?ElF)OeB^UM5h!~}W'mE{;QŒG<-f1*㽙q4pL1?N-m:Պa\CmI>jN-!' bø^_[Vc)8!p_ŮQJb<^6sqNg*+ң%u-U/гÆUC޺)$%m)ݽd㪆aHMFat>|d{I ;J|Ys~>GqIB +MYLyfD{jqLĝo\вyT!ovCpk/r +ysQ,-+Z,ÿc+G>~} H#",Xf+iMs4 ځICT&[ Dr2[9Vo b}& [RbKV O d(ؐlsBUu$›2l Ϙaw5~_Dؽ[G}|DnU]g_; z~={huD^|~G7h>^@Bǂߍ:K endstream +endobj +1455 0 obj<>/XObject<<>>>>>>endobj +1456 0 obj<>stream +xV]oF}W\EJ dd7[ڪ`f3ΌЪw<8!NvmA x=ss>&Ǐ޺>Z<+ %1,20 XSEh-ٲTh{PZH55E6K2LSQr kVfoGRb8ZL/?š(bKJ9X^xd gh;jC!ra-0k6j@AcƁiv2^Vc`4XAu( JdQΖ4}؟Y8 +Ć0~n~@B"<LHК*($-GDY)hrV +s.ʋ-F,7?LLYu)?sJ*ϭ'sL9@ B:M["y +Jn FsZ4qQXW$Ӵ"lj˘)6¾v<3*@^H,uܵ;R7GT{1;Ϭ:w`j{'g0vcJH4q'0QKik(Κw|0O]xZaXa+{\,>L.xor</*0~/*yjv]'1(,@'ȍƓߏx zl7nwM|/$WI!r)E}?^#TyF}wo4L}8 Fa VDqMS]|}7UgӂmX+~_j@;Kp#KjezV\ _~g#AX`5v#ckER'OǏv>]bGUvlj|͢DaC.~S<pI%)2W}/ltNŋimw]{nSF'??fjĵ6^PnTϘo+rkZ..Z72de5 z3=5Qs>/XObject<>>>>>endobj +1458 0 obj<>stream +xXko6_q˖IaH3-bb%L(5Ϳ߹ȎMVy}NBOH1Mf'`D,b1~sI`C\,5\31d)-]!&F`ͥ(Tb+)X +OAvJae9d"{z0eN>#jI"e(cD*-iZSbrw82L3V?A8sPdW3PR^e@K؞((#.ҽvCe?tO +2X 乌#KJ+GqT56ϕISǕWu^E>ҿ_]ln-ZVN="&Y:mVA k{QlZ1}"`!m ,Q2K8*K{]nTFZD;K֤6L%T(Ѻ,\ wnM^"3:Ix: 9~qkX5TMʱ9{GtGɡs#i:F5_=ST *)?>pyhq4|63 +XڬWZQ.nOhLB*Ox QL" $ ?E]"E%+i5]!ҽ0Μ8IyLn4nJ#!glB1&:bQ$Z6/ub}M$lY 0bgy,Lm?rqaQ컜=m"^>r qi]PkS!ڞ+m2ͺR{73sWCKc}F.5Qa;qVN,vAUsUbPbئXb5ݨ]+2Ƥu kDAy .x ,v,p6ǔWZsHwwjm#\P/zpP{PVpr[N;{el )do&y[UruZy0BķCa]7k1qIjnVdW#%lhx U[&#?>?72SQY;CI~Xbz9Mĸa̳9 0^0v-OJ;"z̍ +۷[s g5Kq|"1Z.7Xx#Jpyrw{'MMaވ"6F(H+~QθgNszY[Tdxy">/XObject<<>>>>>>endobj +1460 0 obj<>stream +xV]o8|7;N^i9H+-QItH*}gi+\rD.S}h8(oWF)3b8c/>0o] bLfx ͣeTDZtV5~z&JYtEdk'cjlh_z{ 1 +w +CQmݜA_gBLˎy"t)١>-:W^P-4 'NkQ48\(1:о QYFؼ|)+Rqo.o?1a@pNaH-=l +K4'D+o2gbmaHSb%=O4kz$@RҼV#g0qn|2UZ}vȵI@暷C'|k3`{*My5^7Mϕx`U> }$C_S=uX\vp|蕥 \\|XGeQ)AUG"2rsLQ=?f!}$7\%jeSA/y6aH)EݘjXzO숗?@[6BRab8SvkmwAg5u@ЮC9_Mpz*V-g~ǹRYJG+?JcP)ۡNstEbwG2?t61ypCS{S87_@lj3ⴚ`? {ixxendstream +endobj +1461 0 obj<>/XObject<<>>>>>>endobj +1462 0 obj<>stream +x+2T0BCs#c3\..}7K#4BHP$YSO! U!?M!3$1''$3?O3$ BOzs=s3 -!)Ɔ #\C&endstream +endobj +1463 0 obj<>/XObject<<>>>>>>endobj +1464 0 obj<>stream +x]N0 y8 IZphyХ#:#IR!$d[O4b +I 10 +~;8W\wOJ>-cKn;=ؽq0;5` |%DRq|>bJTq aB `KItFYmÑd#*7yOOC/]nvf|E|ȇZTendstream +endobj +1465 0 obj<>/XObject<<>>>>>>endobj +1466 0 obj<>stream +xW]o9}ϯ;Tmm&bf x3cʿsmIZi?D +sιG]hܧfоg%-Ao4~y~vֹ~fKitM/-]Rg,%MdHw1fE3vZTy+W5,=iw>^j5oȯ%,+o\-q&'gl-EQ{^&2#Rd WјNA ֔BilF{kBfV)=ع;d뵻AUC:>d^dO:;~{<UT|N.7B5SH0Tbֆ(Uk&Ɩ +|iejj&ܐTT ExtP`zf+LRHhߎ8`yg =q{ĵc&(QE.\F7j-p:uKȒ6lU.0(HTJ{ RADI爳QiBձҙbt"аb+T!ƚo'M+#Ta;:%Kb! ϗ2^fkaa~WǖCCBȎJ 8 |g)Pd:>J7mk8r<{&^TT.CTo%lk$y~0E,ZU2VHhНPҳwL{΁;rk{j8 +hfxH4=!mc+I` E#@ +~'?XD9UdsFעm5 RvD_x>/XObject<<>>>>>>endobj +1468 0 obj<>stream +xVNH|+x +1}aG*^ ҪmNo r.Uuϓ)M3ՌKJ˓I4th^<ܸMG7E޸O..i:8GzEqFH0P!VYzcHOo/^ϖgB +'QS.-yC~'!29bjt5oD[U +5P) +:X*xB ҸQʭ[ڙN^"tֆ,ESڇ7e MrEY8")dv݆K@u]2<%.'`.fyQҐW4gLxhG=[hɏF +먪BTIʊ1udr:5rD^<@$8OeJEAZx*>FV )B;R |S2'J>ˎ \yJZռ˓6[ `-vWG1G!^h<[Ogy\F%c~#ҧ +{vS>*Z +Čwa0^y8mdD/TjRee1otfyɻxח e7$,c!sJjO>`)⃸!|mH>Wx:"jrRf-oM2E$~ H_1A9oP}$ \']~{ukF 3SZ\=J pxg$pE'lZ:9f7a{0E`<&$$)]?Cef2Tde2:) +6:5 _Yl97޿*eO'og-w}% +@ka8{onpMqr[b;D2&̤ eONXzz؊Aۆ|W wU }`" q׫782ԮvVEs{o'P>= $:$7ĀDNF?nX=٣SYWv.Ds8xcPQ ~kΆBVv=pI $ 'xt_I/$%9]*07؞-Y/?_&W>q-Vh\x =_0'5endstream +endobj +1469 0 obj<>/XObject<<>>>>>>endobj +1470 0 obj<>stream +xWMo8W |N$v(b/zɅhD$o,+>m&͛73-t=Ǐ״/w/7g.|X]\z 6pX>*'8'ғ*׊Tl>y_8IW/Wafde2@h|Rܙ@Ag8~@MBU+4M.$[֘é1.ׁ7kOәG-8nwb:ӧ_k S_uqj&tWӗ8yRE$0FRBT>wxZ}m)v};rpK"@F nS3َ 1MD^gڼ24 POաQ op*:R5?GM LsuXDV_Ѻ6^F׍iUUީVʇ +<-WX ͅ ѻZXsJs*S ̉^(^)Ժ@QN2T?) +d.Ύm wpeΣ!!H#7Ƈl +sr(yACf,9SXC] +z0]0ʠmUT{sij02]ErB+-ԕ{#k%xO N+"4 ! .y*gsno @@ b8YV4GHh(dcDsS:<H7c?~,byUUJB0ϗw9i- +ݾ{EI+zy ~ I4JaR4< +Ԓ;yJ#F贻L8eiCuTiDȚPj  q0L5@{eA~qGA#Z^@>2< +8#l#/n)QDuų==V`තc8NGH>Hœe[@Iĉjk~6d;]+NkiPz͹ ͊QKVҾR'nK dN&A,Υ,rw_mlL!bܾ`_h]w~&F߇QO[Sb MxSqV^Wt8wL,n-͌6uj1cJ.[H޺ė?wU|LSxo[,IGڗ1rhqfB `]x囓fu-oy_::0K" +7X䁱k_05 fz^z8.y ٻtxHXs..)endstream +endobj +1471 0 obj<>/XObject<<>>>>>>endobj +1472 0 obj<>stream +xXMo8W |JXv!mZ`(腖hD$ Iɶܢh89o޼ŘF7nfWlD"t1 ~[Oiƕ +ш,g7=I"-=Y◼,xw8'EYi⥒/ ȥ[KuOo%9QDXț,/'8 7ل#85vRSa#: Gz@Q!]nJ$7/3#֞WDJ^¹E JΝ낄cf ⠻!jt==e@'񴶦)aL8Iŀ\xm@';GZx3]@P«EKOzx\bY:7eMCnkʘ9hl`dUvp'AHW/2:M1[b'1{*}ń ό5?sM.unu %£@Ws iog fz=v*Bm!CW(kcĭxjUC +$Xk).W\#P8Y +P,WBpGEϫ{<<HVATUH" ]C4ZGFY+o\*=(2}@"gУk,:3VBX\Cx"]IzFRLn>!lQ]* zH[#SiYraF)$Ĩs`Dl^XBazTƬHcñÒ2aeaZE؂(PI`9N}n 6za_m6;L_ypt % `08^sP0a'8Fe%FbX˪Ĝ;#*)%zLNyǧZˑJAA$hTb-ze#9DfkJ-?==¥![DONo'ق?ҁ۷h9dT9?NkG7kH?}ASv]e_xL2vM l_^50Ԇ +vO9jsυ\ `o#VI\hUXS\V)*p(hXjJW+Uy6Qteo1q ͂1<-,gREQiE11x`Ӈ95F*SI@zKʭqfgP~ox (,j!/k '3Pe}]/涒"lQy(4}͠qe12Ww.@x!.`M9ye +^Uc, Ⱦ6MZH&QATαS@)>w*T~cLB +١4ڶ-a쾩]?-@ ft;^, J3l/ [1c:f"Μqy5$0endstream +endobj +1473 0 obj<>/XObject<<>>>>/Annots 664 0 R>>endobj +1474 0 obj<>stream +xW]o6}ϯԊx3lִtDl$%)'=d[mR[ǹ{lHtDʫA6ןg٘* /%i6Oo4ƗlDc%3Oܸf׋1 X!lJ"8E[aՔyV6ŠJziBRRdAгO$5\-ɬ҅yvtByTo6yհ_^"En?+U{~N*v v0FD^JaO1U.2:c_9Gc0z,V|Go(xOi/-l4 5Ǿ?r%\TKAϪ, ܺIe6O=HJυb)\Kir2<sѻe.պD2Fܑk^AtA12ך1Y"+C-e!PK<>-y‹}J<zHIm~Jt_xFlDN"î ƃG3cE*kb쿐$vMgt8]U;ϝdċt]-h{R7ױf=dQEжGFVE=;㙩 [99.T$ݼ@1/=4rA5>0]dB%vR;m"H!XfeM֖ۯaHhOQ:nFC# z +vb; >28}*k@yU%7"(,QJ|EFCXBvMT:Z U>w{j,%Xd 0(sgReCzn\ +&l L8iXptu'4iJ=6HZU N92pZ$f6ݣ?-TnC#16k 8ޖ3 jǼMDɒ6ooFP[Q"#w@&QXPAo07lzccu +u}ǚ_ ag_Yb!;7>/XObject<<>>>>/Annots 669 0 R>>endobj +1476 0 obj<>stream x}UMsF+|"[A ! HU$Z&k/J fXmdׯ_B7IDㄲ7 Fxr[/ALqZR<+)fAgc6t7pϦETgO7\hF)̈ҬO폕YSLRnJOKoDpi~;2wZ̖?Zxdeu|߱pSz`(<^Rc]_ݑvM)uMNSn^IeYQn"Pa2QKPʌ+S4 :sW-(Eav=ar@Vꉾ('K&)jȽ8*TA$JL$ybk*䜓Yw\-ZAz1I춧 \"oQ/| ݢ!G]cy+жC="j)20$IdiL_}}2k=C -ۖ%b7 GZLctJlkY|/tuob)AE~>א0Gyx4go<>whJ;mӵ&FZFaqWɀ?[ гV,8zAlڱkH742 k\Ni00Zuޙc1P#O/OF3 `B,,&YY׬-+}j{=6IWPзZ)}B|;s0PԲh18ZGnY^fKYnPU;h1Hᆩ5Qe{q@ro _5ShaF!{@{A4_<'pD;U#VX0JcK:1 +zUUPHVr] Da օt e?{jBnJ_ smy7Lvi|?[iz?ϕyANZ̽P;xd -a9N8ǴGTendstream -endobj -1729 0 obj<>/XObject<>>>/Annots 720 0 R>>endobj -1730 0 obj<>stream -xVMs"7+ -3|:7ĉ+ekJgF4{+\Fݭ믝Ii`L>>ٿ<ڙIF0RIh]AO8F#fNp.DR HIz鈮 }\:s4[dJ<'j%j,z\p$* XKW =X] -4S7"ٵ)TޚPD$&<9N!U_iQ\WxbHiڜ&ɘO\wfMuVr8CWڑuDuSTEnc~%|8+Fگ8B/i.ͭAv ) + ,9̖!UK]i¹9vW{m*pMhR B;C!%(4Z7F5#(cm%j -f:3qz7vFeI:BL0?eGendstream -endobj -1731 0 obj<>/XObject<<>>>>/Annots 764 0 R>>endobj -1732 0 obj<>stream -xW[sV~WK']@f2'D&By)GTRK]yL[PS7Dd36†p(UjY]J/](aRHZߤuZ*G{pY)XJ}cY)#uvZ+jDZT?(A ؄<]$8 BSjUqP0iyNoYLJB/SqJ JaYaIàFrgq5%wv{؃4g_:0k-:+a銈\,-6jEju%u -(1EKfN ­vw3.֟1MRg[[ ;_K)nk8MYendstream -endobj -1733 0 obj<>/XObject<<>>>>>>endobj -1734 0 obj<>stream -xXے6}\%Q<+ٲDT&I09i\(%WmyݧOn)MgJ7dB-yIۛ[Ni嵋Ւ69adBlK tk{ylSU;%,F -.dE˜c+{x3F&0-/4%+^(SAsZo6Lu!O>-nk*E]s)b ~dR/=vK b4Rő~o9=R3"Cw4`h~F Ԇ$$m reߴxɽ˲lOܽsGl,5g@xy\f/~Zhq~ո`qϵx|]HrLS2@RUuzBS8|u4\U gka-xWd *0zW9 3q[[t,?u]$RpTs-G#\TmqtcE)~OT/[=?Rp A)Xv`!sɔ伌}ID4L^=^.Q{G | ݹw/4O8[H J7 }+L(egr8 vI,S2He&5)VwZ[˸|ÞeFCL{ f'*sݓm?yEkGc}=&54$ -k"j `r+sHXH IȞF!c)w p F*ۢQf*ʋk^;8QȖ)Q4rHxu6S -:rQXȒ!0kPnUz%=ujH;'GGU/dh%? -B7jM+MKAZ@/ο* -<dD=qv; -$dZ31d%Bp_PEOFv*p<2T\GCy)D;_AB7:y\xsgIQB]1xɓs>gFXŝ d Zrƈ\.5*Pڙ+t6 -hWu|L3W3P /KT! d;|$$qG{)Y$J<}8nitXc{dm1d]So<9 KXX4gE.e>hl'?2x27ħ{k@C +0:)[S-FGS!k,] ʏĘ.N FޮPs1L -d>_-+Q ctijѐ+ǭta QMn\KnHB1;/Bf9>DgI\:K -F=GFF;^+4̸<$\4TʵwEț5nJֺY(xdtd|j%! F/|hH‚u{ WZi?q[wȟdXC;~s-xendstream -endobj -1735 0 obj<>/XObject<>>>/Annots 767 0 R>>endobj -1736 0 obj<>stream -xWkoH_q7[ ZoI]um UR`0=Ca;36IJI=uvQ?t:8;}:N>'8=:e4?GJG(D'8ш }< )h`ɘfҧYR&Ts)JI/g_qݞ,Z&qojM]̕,›&`0 -Pޝ$C-Z2ƫ*Jql*]SVNJ-etH\Qt- Mbmt>ku_]H ͷE؂q8ߛh#/tH-ѠH$dTHӭz(9$vOReTeV2'~@$77&BU dpL.ceR'd2 2Eƞ0[ ˌ l\ha{NO&atN@ft0 -g5C,qefrXg - :Z*J&}gςf0Mcm'1SbVaxMP-%s.Ra͇F P't6W6ٺ*e'QmQc)]1/L -q wd6^o?\;F;CyQ: djg b`-)L_jK3 {Ł{5ÃlM+K} Lm/ro1n08s[Llt -?ݠh[m6S -ff&ksLf+E6w;qnDŊ='ic;j9OZ85Zٰ]'YSd<`bnz{CsƶV -ZJ[Jٷ0[&rw*% A?`ĽVf=K -;jEu&a 'հ^B![`zkJ݉ib7 q+'6*҉uj/b)ctB J2Gg{G{[=RT80$wUٟc=ly -3JVF-`S@C-Z8Ch)%rhds5I[~gJ2l^*%\R8o݇oZ"**0Z|m#r\~a74۫n4~8X^_it\iv >9`ܷ,?xGw٧fGhendstream -endobj -1737 0 obj<>/XObject<<>>>>/Annots 770 0 R>>endobj -1738 0 obj<>stream -xWkoGίr[HfaaCC>b|a$;dfטs VUE0;yιKi2ј3H4Β7|Gw/o쌲)ϧZ8O%v?&{+,rdLA(Ow3J3/xnvMcR54ʶ`0~}Tq1RkYt{mkA=+P;3G%kR'tm}uJ{ktNNd\קM\ ݴ[^c44U:Bf#g^n/\^pc+PCD:/z4"$K&)~LAHendstream -endobj -1739 0 obj<>/XObject<<>>>>>>endobj -1740 0 obj<>stream -xXn8}W]]$%ia4Q46. Dl$Q%=CR&m֡乜9sf{CgHRV]7'4lG1r$fYoT$eIWņTE./(2'?3CI򐔣6ji2s&{MIogt4?Loogg>Ӝ~i "7h6d` :(e(\p͜ j'_f>ǔchTr)#?dV,eBW+Q-*0HX]Jr-IVDZZb9}HFZ_. SK,9VYhL4:SxGݤ-XKh2]Aó[n`L=B6 I2h -hg -E NA\4c %EXytvg\!}*ɞcYA٦pvJ"M -LY{AIeA_:C*-8WR8<\8r U湔.-5ԈTW;AfS>|R3X׉!п@(D鼇L$`֭\ x7ٙHZJGT_L%WY517ܦN%J%C˴֮tšY8U(}ݎ~vV -ėbnMdI -b%RL$4‚zW>Lz|?69SgZ 0mF'%;/ouK/9ƜycY -b5 -= x фaoan,VcFg8@:5 _\T+_|ccݩG^wc<EK'8?:ٶhPȰl)mE<a -GOx UY-sjQK% -g-n {%@G* ]їѿ7[Q tB@Kk_*eA\`_E2yxxa& /8QFo7N|[ĆNh7qىs[pMx~UxGa؃ƙ{16p0W;?>ۛC0"-DrvKTrʲJ;*˚a=U@Q͒1JFɀ9RMo ~6]K.yа\gM( @ܤCp RVK󪊛U `?'p%Js|QFl~{?}/~Yg=x|>/XObject<<>>>>/Annots 775 0 R>>endobj -1742 0 obj<>stream -xW]o}/ )D}Zp IkAňR3ܙisgHIw6Iޏs=׫VJy2unK/?_-dMUV[IWerMVެq*~W{ܼ}Ξ7-`Nt|)Wy:H5|'HShUn &1ph*>C<{O`H9ml%2儏M4]%G4Z)$Q\n$N~dl&-EYS[+R Fe N\ b{5%(`*^FCAϤOglDuC;QnҴ SZǔׅ.(+wg-m|k'ڀH Ll ~o͐TU T{3W#G\@RTCmvx8Q/g*IobNކ FcYKqnQ2''i϶ACXJ$S|#ZrFdףd`Q5'*ӛ-WTy% ol*U:x r|Υy Z"3iS!px8B` -,Gjdgա ޹'O -c2u)tb-\@x>jӮIh׃E3 JHVP& )QhԅMzcJ@P3CWBܙ /M@1"yb)rAVSNqeH)s8]4(D 2tDed'ַ>np@l -f?p2U \QLO~h -xs7:1kQ0tF|u& %,L-t $ nC1pXU B5-=ESwbN&G,z.0ȭ>7XޔTI# 1r`UU82a1S8AV)MivaUe 0Ҳbp TןU3mhD%T8F[BE:'iH|mg<ۗ}.Pghw@A --SjB?[z[NE駙,edFԺ>,'g Bs9nRͥ -prJv&qyqcϳ~E 543X{:f䈧 -Z}=+>=n9n;Nө)]J.ݬh]n?T4.].ݡR w+nxczN]T|_78&endstream -endobj -1743 0 obj<>/XObject<<>>>>/Annots 792 0 R>>endobj -1744 0 obj<>stream -xXMsFWRRR"HH%Z̺R  en|R7=],3u4?fce'#o7ϧ'~{4ޜ2OoRZވ)~8`'Y\Q ^^^ orDVdD..LS(W.39MET_*]*K!E*REfK֩zJmM=K K~*Iw_z2?}07<}r3kнJcgfoٜ*UI8v6sfE{XmiQHYK61UFՙNR6.5|0t~1ՑNSPA D6Dnw,G m}i.N#ol*Lx:B7،I@کܝr.ॶ2h5tahT8\[ycrW>J*MF*Y6j -qh2Rz|1z-fJU?v=R=v*oD "Dߨ\NHEOTN(p*7@f+V-F["{ Nԓ64 -}eӇ38!\P^2gw=N&D(S lXe]w<#=,iݩyf*um5E=(Gq炗ZQs5Jɔ1KA\MN"DZH``xoPEeգÆA>b9wߛ=l,P_gT`Pls"-V2Ӗ;.ړҏʎ(uDvJqqsUQQwuСe7?D*dv|$"Z54"ڐ,un 'oGnkX8S(ced@z1a|-Sj"!ǥQ\e2BM0zY8Eֲzu4CfB A4!>PIl)QiRӻz./  ۧ0@ M(yĹphgʝG%!rR3O0gxQ G RSdt/g_Tjk,LCA)eޤ*S9'-"{ޞApIX6Pn.@N -dj'ixn;|KXqUYYJQy\׋ψFc{>xkm4fxo*uw ;W ̠o&ahXg>.nicAB]~4@d]um0<*@ iaj'В0b )F$`.b~[;,L&_~SMDً6CsozXcug5BE m(Dø 9:_e`2f3\է| 3ocd=?;ڡ}1¹g@R^e8ؑ[b1[Lwf>/XObject<<>>>>/Annots 797 0 R>>endobj -1746 0 obj<>stream -xXr}Wt$HFFX٤< 9`;3=0m֦l`.ݧOgSϔ3/l&o?bR|(l~Ui>3|]/I_qͱfɿ_T_]~V5߽YҪ{'*/^"6Y@i~h~C$^m]x烼t>N[]لS6uU]lZi|Ֆ6d֪@V%d]Н;F89_h:mP.x姲`<f 3{]O(/aVłt5%"UVt`FuJ*b [U:OVk{p/.٘@Yw5CiʻN8 -o5Ǐ(鷃wHUvnDFl'N -I|1>z*ilةSV_pI۷)3Ay -8ب/:#&n@6u0*aیQlI0iRj= Z`iNδ7;^*}mj,iW -7 %/:$K A,-NQH61?j"J0 Fə:{zk*9"Bʞ+H(Y*'X1 7Q{V a#W?#^^>|abbSnDaPNNHf1k"Nv; UӘ,&c*8%I[gJe zPÝ)h vb Xf=A+Ͷ25sQe9 k'p'-Nڝ}V@P#*t/;:%pH0N@UȩFЯg?/ yl+m[iӢ+^)_9#0X-E8d^DjZpGEM -zd}F)1(aQ V bw=|26w2"jP}e>*w9^E&╌XANhn gsN; ff!F*svrU -8JV&RUqXұS,Mu+Kד0Ku,>hJ <BѨY hEs~ [w˸5%$_:H{c$ò!UZ<)IoO Vh} S57SkPmrEO\3P0w2[@ _j(M Z#Pl]t}@YEZL%?AF._EփA,nt;;uP-~KS15sSLo1jD"bY_Z4o@|o\n^>|>i5 l*Te|^ELɖG N'wArjWmu@ӆCA`Utf >l"08k.حbFHdbG%P.`*hQ0R6]C[(:Xodx<ׄ}t,܅z0>ru}V -\pC}5q$^ggV !H7ͪ2 X4w ?5<:CA ƏPt2I7<*d^%D%^覫fNUֳwg>v툄w _W˫bIa5g?endstream -endobj -1747 0 obj<>/XObject<>>>>>endobj -1748 0 obj<>stream -xXko_1@%ٖ䶸:qci}Y+scpVY,.R4@cg̙33z0>h<A?It2!ך_i0Nq0H&48;mu<S hãɘf~f\W*z0dp2[*|XkGRamEӢ*Kpkw5^ O8]?:Y'Mlqٗ>'puzUlQm'Y&S6 nsk[g8S=:NNsUW\(RYipÝ\ES9Bg M$ΙEi~h< 9߬L6,r AT 4UYO.WhZc<$:36I/:Y XfEÈ>y#(SRaIngܮI58 xkcjfOXֶ$F%-,n`zFeK(䔓) -TapcJR=iRA7$s̈́H| -i±̮$n-j-Qɴ{v%ρ/ת5TgKj+S+!\i͟ 4#qOGM gy9[_qtqV>?Pt{EIKk:[X -k[>SnOֺ ~Bhy .bt+M5UȘs=>O T*TH|1'[7Kƻ3i1[`y萺!r +F -x# Ҵ'Ra;|*/BltPM mrax#Ψ9 0,OϨwzt~^oPe;uNr -SLGcv ](Z L.,/}80,V4ٿ~6# X?1 لrܵJ].:yg-caSM?7 s˃2mFi.),VkFVm'8=? -I&!~&h 'Z6JBP~7 }Oǧx4 t~??$endstream -endobj -1749 0 obj<>/XObject<<>>>>>>endobj -1750 0 obj<>stream -xmTj0|W Rv=8BZzp/yQl9VK%7c%`9ّٙ!G̐U@ơ NS+E:H Dd*i BִЎPf AwUN[dzP.{Jq "}f"n'Jf.\`6kO$P+洏J4:5P+DDܴ~bK*;\s|y\@HH5)І^rnf.:^}Q֐1orލY![031mwۍx0M|O]d۵5Qy,te9 >O}Yendstream -endobj -1751 0 obj<>/XObject<<>>>>/Annots 800 0 R>>endobj -1752 0 obj<>stream -xWn8}W Зql@Q x$DH"Rq{lGIX *˙3g&O3ɐƔ~ǛtgdDiҧdry:O!0'>L0Һp5^аObO4|(x\oDdEfX -c]ҍ)tmL3t`$~y$8띍OAB?*YɧZY$"Sznh07WreԔ"k B\n,!.VR!%F8W!5l9%m۰ZI B!7$,eҦZ,OJأ3Ir]ZgMs"O%~*DQ:fŇ9gHhEar6<:K5գu)-Nstfͣ3 m0W_,w3 =`dLj!*(3hiFh_B>r29` -^p{DJ6@8GfAchM/$ o\HgRY e[S8|n%zN􂁆~/M&f0> -gsO˯ܲch - !pn -5XFui2LwO lrD+BT[ߟW:0hֿK'W|#ԓېJJ,V)w7l39~ z^5@;.*JɩzXw#JY3RRtZɢ !F=b-Jr^zFWI;RA%&0wlK|ՈZ -p#Ꜳt98B,3 dZ: pfXie)K0;>X.ϥz6d)^Y &0N8ZTâ,1ay )ǐw vяi^710uဣG@6 dLK"=P(Eh /lnzȹV23ލ[=E3GA-Xy~1ָc̀bS~S~ƣGdfK@tA! yd7L4[e1HOz>/XObject<<>>>>>>endobj -1754 0 obj<>stream -xWnH+C$ >eD$Y~V͐2Mۻ"0"in:H2h"iyOr:'CϦ<_eg/g2| '>dd jwYD[;|n,sIJI- +ۖ%b7 GZLctJlkY|/tuob)AE~>א0Gyx4go<>whJ;mӵ&FZFaqWɀ?[ гV,8zAlڱkH742 k\Ni00Zuޙc1P#O/OF3 `B,,&YY׬-+}j{=6IWPзZ)}B|;s0PԲh18ZGnY^fKYnPU;h1Hᆩ5Qe{q@ro _5ShaF!{@{IO \5u&%ҫNlL^cnծssp<R@rDa,Qlg·u!]merϞEC+\[޴ ݦcߏzse^&s:do'%$DXcTendstream +endobj +1477 0 obj<>/XObject<>>>>>endobj +1478 0 obj<>stream +xVr6+譊(z:7?+eGk+|@Hš$$~{Rdoe˶̠{zvR'IF1ɲO4w8o_hJ$"M82+ݦ#6s9n)|Ǔ)sB>>gWkQ{eiУ(#Q|Hߺʞifu)KOlgצ+SykBY;R$IPV}h%r]!is"$c>qWܙ IF !_kG2 ՅNQ) iJbQ(z~zO lnbK](GN٭xt\$| +6/ *DOD^J;ưνkiwצׄkѿDt'c[[*cp+Ϗ[z$t)ʚM6Yal|+x dU +8PܡUBy`[Es|dnavj]b +BMM%ZQh wP89eaVrLp87/!ӃXiPFezwLYS64-iI_bVɕ9H#sW7"j +pL>Ȫw_=(orJA8Hf2sfiKkJ|fi=FfAw)춛?D҃P*4^^APEKBKQr>=*:-/3T7:ߊJBU,g?S +>hUT-p@8 eIO+Pɋ¼0J" SW.P=-/X+FG.r /Z!:Ɩ *~4lܷFs 9ZؽNj;XN 28D @GOg:QɑڂGw??%anC}N<}zO ? Fh>);նBYgǘVIoj~$ӎ̢7WlEa +nzU5ґˀXT0qq`HS޹M]cAcuװ18 QPgKtOF-N=Ha@{JUJP|S7tek-hXYQ:.p;P=(_ Ӂa-5,&ލvǫBКEb{ UQoB)ZX#O1olu`.@<o{FޗB0}`BJ;>RQ`inj8GQ,K !a+ ,tgn2;ʒt0aÙa2O#,sys;Bendstream +endobj +1479 0 obj<>/XObject<<>>>>/Annots 712 0 R>>endobj +1480 0 obj<>stream +xWsF~_/ %K2L'}hĝ>9H:;cҿI&G۟D7lLqJE}!i$9_i n?޿>GAJ`L5itDE/J,ȅ[^$aE3 +sNi(J'b%91LzBlyq^E1t{j`^oB 卑?q&'^A97bX-/xbe>xv$K^$COSqbN!^H9 Mؿ&ryfN<ɃP4&Pv ID;vxqFXf/'%OspHtԀŸqxlLKsTYYbIڂj͢}J:]TeQ 诺}JPe8jtUmY=<~: ÍSE( rݪzK6YwAku_e37K7Sv~.{*LS蕳]O(BysY4~(^Z 3]kJ^ɐs.LqfQ"*ZS2RZx5Jy`McT, y_9֨*@[*'* *tu">Tppڏj{-9D<4ClMիJԸTӃ\_>>+3SG3JE`^( ,)w+ @J"=睫黷zЛݷf:~o{ϽyR٥YWsU{1*S +Z~(B?U/iO;Yz[W >hI̎dgv:Pv4N 4{փN5ZCƖ\'r?^75ÊgJYR(^_ek81[ {]ŽZʴ/_eMsw]6Gz72y7b}(n;}n jͼQxkbgKKSZ[:iͺ+]mujowfc~3[^^7E{uhKA)uUIDC-D-۳3I%Rn#^>9H֟ vQ)v 2;xnGkێYG*g>>iNw;"85 =@38p^}Q+~(E=aa:(HȆB {nQ})/C6YjT6N6?oO /+r 4mcn_t2WёQJfyt5Ӡ79úLD?qt)+gt7b0YTt,#eiҼp''1*鸽%k'2ŚD> 1g!%Ydi['RWӓ?Nendstream +endobj +1481 0 obj<>/XObject<<>>>>/Annots 714 0 R>>endobj +1482 0 obj<>stream +xXrF}Wt"kHole'ZM*Jm !9AQܯs),]q%[)Lw>}_MiSZh$zŚ?go$mvv59ɚJ.&+MٲzE=M6%524kn#0tY+}Qoigt[S)CHU'J=|v70p"F#EQVѓuQM-2:|MSq F *Y$t]-Ad{UIM鶲޹kU[߉sw4*Y2t7΀q Kv/,_ohe]Za`C{)c$9x^&) x*:=`E[.L*Bسh6;Lte"cP!ֻ!l!HHnV0=ZՕ5(Ihåu){-[#O\TmqtӈRr OTe)8Z;dʆor^ƾ$B4L=ų]=>/m~1}iDw5U&29D#=6`+i$T27G*3IKזj41YfDe*cL`0;Q!  ((p^#&Ѝќx#Q4ڹ)B6&+>QɁDAi!)H"\X\f/"xW0 +<`-04xZo<5e=~ET^]E)E[_wר, dmPgv- +Kz^պwN n j9\S,.w|B9#Zo(2W KAZ@/ο* +<%dȈzB )cwrHɸm̘7,ƐT $z~A +X?u&f7g"Z73NL=Kg t?\`Cgd%R5L#ڦFuv^Ueوj'_ŧвg8]/?QQ*v^z|LSϓJ(\) ׽Pa^.W B:N'׵\~GD%q+$u:yru: X},50AKk(+ϘT#IjPaxUT?o:yu0e> p`I@,1gM"Jw4zB%Q0Q@D?>чS O+S'?S!C +6))gOxt; KLjC+rQ_ܣx/1 +J _@뮂1eo2/؅(1y`uCiE2Oܭr>?90z5>9Y_s J {wbn~/P4TqN@Wb8^=_zb]ě>v|x{Q4/ss&׼/l]JNGjke1ek6W/_endstream +endobj +1483 0 obj<>/XObject<>>>/Annots 717 0 R>>endobj +1484 0 obj<>stream +xXrH}WtySedxդ⪭A Ř=='e 9}z(~" lLI~4t~> G4'x?ī/hϧ?QCi<E|nm() jR`L!SR\H>^_VI`!n̤*\ HK %'~I]JKw&i@ &an84F=0 +.$ YU Ŧēd4*@Sv oEPFte%Dx|tjfbI{R)l +`RPOuerQ55Љɢ vTn$S|5̲0(IHPR&u mG21y.uc&\ t3bCsQ +疢lsXc @r~L0 +a5-'GVfV.]:}!!>W-T*+F69>;P~4|wͽ!gLU"4C]bxGZf#NΪ#WRrѦ( ZwUFdY(CP>|[x1ҦKY<6v$3+M'Tg֯ˢ_ΕYp&=E ~*Ɯ wn"r*y"lw!{f{97;pl?ŸVn{MnܠvivId'TW*CGi +5е<4Dx ~⡬lܼR>/XObject<<>>>>/Annots 721 0 R>>endobj +1486 0 obj<>stream +xWao6_q0bYmAml)vk<òHl%%8{GJ0A+xw{G%'iJG1eY%4M9ůUlko4aq2ES*zeSA׽gsIdrIMHg)6Ni4xouSf0>u-Y̊Avq?NNTr$ȉyV]lB-}1ns[cUgc.*(?;\U'u"Vr O_ onk }D%*ԐijE ߀;^~J,.H/(PW;BKծ|ŒUpc֦)$gT^. %쏃9gr-jZYI|^O>Wjw>LzTVۖ&SΓcyKgr ^o3_PdJ訖=D`9yO.Y~oj跟ŚYl ՘;X׉+o5F0olb݉/$\:tv׊gJ|v1`Ũ R}zy^`M0cwl*|G:9Uc0wtPC 3pE't x.N|]~Qx;< N}=M}#p+f~/?2 bZ! ;wwtz#'%ʡ/Y0u , {C~9|h'yH_Wendstream +endobj +1487 0 obj<>/XObject<<>>>>>>endobj +1488 0 obj<>stream +xW]o8|ϯ +=$Ӈ+yh/PZm6T|7KJ(XrvvvvhL#9]L)/FوMٔ&K|N*>\<_ͲƗ4_lLsI`4y>etkztvYғ0>:g;O@e<7ra M^R7' ?"hȈR8vqvHjJa=YoLbT>/XObject<<>>>>>>endobj +1490 0 obj<>stream +xX]oF|ׯ-J; %6 $R|Yr;ɡgZ￿ኢζUM;~ObF%YvF<[i*ݸY~ZtJg-//hU9;U~&ku4R )ux=~Vy+ 2aBz)0<MlUk2^U5{nn} 3aK޿{Omu#)Z2d:m??dBZ6 -?!?M&RRi*xHն4mճحuAB}m׍?Qȵ;AkE^g ǽ_Q^>Eή+]gt[Q Һqh.5b:tEEd>Иޒ +A-i (%dk+5ݯ_f?ї%mNp(j׶^֚iWPqr|d=T[H6NK0sɞG$q'~OpǟƺZU՞ +1.M_gs +¸`›=ˌv?ZVvE⑇νTnZ!TE,0@m՞lI`(CkX)e 4y$F+uf!FL.Bh=H^L +TJet]y{&xiWl7N5I w}+=$)7p3:w>;6Cu J>͎% N1go^ +UmEY[^[G5*|{`ʁ3qˈ"9<_ߤ|hN9͈*o+RGWzY |±r6z qݷ|G>q!lt_87 /#Wv#7"'cZQZr #XKlx iy\;l[r; +}4A4Of圖˳p}wsM +:bX1]&gW<=Ӈb],/eO9'quWԞhendstream +endobj +1491 0 obj<>/XObject<>>>>>endobj +1492 0 obj<>stream +xWko_1pQ,Ze= +۷Xm}YKscq{fvIL.ֱ<ф7ŔVGdLdIs4Y$:+s|©ɜ-&'y2Zh2uξ3ɺДF 5:A7v-bjw,7NM⩰)ӧRxr4q of|k҂rhlnJz4u :w jOm(uLMUʢO\KzXOHқL wBq:m'UΓx*ԈiC\,q:q 9KOi]ɶ{R؝NM?4&RsX;vSM-ڕ?Mt$}wl_X`uzO|mj{2V?OTA~OaK•>p{KïV7J=cj;,?DgAB#bxaiLoUb + hì7޷xC5ADuұlRk+(g'7ƱEv*Ɖ< 2N>?|zˇIl]Z Sm0*C\IUɄs;]=4lgK˻ nͧWGg>/XObject<<>>>>/Annots 724 0 R>>endobj +1494 0 obj<>stream +xWn8}W Зql@Q x$DH"Rq{lGIX *˙3g&O3ɐƔ~ǛtgdDiҧdry:O!0'>L0Һp5^аObO4|(x\oDdEӄfX +c]ҍ)tmL3t`$~y$8띍OAB?*YɧZY$"Sznh07WreԔ"k B\n,!.VR!%F8W!5l9%m۰ZI B!7$,eҦZ,OJأ%uej6Tk?їFL!hTK,*ST |;ͅҙZ6Zlϰ',_e?tt|q΀2E|K0΀򣥍B kL- +OZ_P怩*xLh{E+YJr= +5{% +0̿-s"e9RKeeV +'m$NsskBx9} Z4`ؚ^*Тe=/zrˎ5*)#H`ץa09F=%aʅc +Q^_l^h`Yp[Nd,ݟ\POnC~((²XqjvȲI|6e0z(%a ߙ(idC4WCKIi%&dm_4+mQx^% VHq-UV#>hi* s4B< $ttQh:T7zais, $cI6h>9Xbo}4zf8jR; h҇qACZC\5C;E?y̯ktrǸgLNĂ1.q޿ڋ|@QBTn-гun"Y(#[˄gh0z7VlO `eU[㾏5jSMvrO'"A<0- +]yڇ0/NK >0Dn a@"< v? MT&8!pcfUL6.Bn 8zRELj_{S-rior> +פ`[ ka#Y% +CM/g*l対bm+À%QA]0d2sbNkBrXkf1A +n ʆ1m_IlրHcP%&D H;ޅw!YTإe\02֬\M";),&~sF/:bmy}jxeNob@i\h2J&)΀<&W_4endstream +endobj +1495 0 obj<>/XObject<<>>>>>>endobj +1496 0 obj<>stream +xWnH+C$ >eD$Y~V͐2Mۻ"0"in:H2h"iyOr:'CϦ<_eg/g2| '>dd jwYD[;|n,sIJI- ]}0 c p f. <׺1p{9~P^v¦ӕx+ -jSu&k{7!ax}K%ksb/YnŨR˯)Z_Uvov:s` $Tol@=L^mfu Fdv6$am sدR`ɣeL9Io?k8de菣־endstream +Z1 gh8-nW8oTbp("PX̠r Vͮ2dmML²@D9,2m3HA E]'J{y;> $Tol@=L^mfu Fdv6$am sدR`ɣeL9Io?k8degty~?־endstream endobj -1755 0 obj<>/XObject<<>>>>>>endobj -1756 0 obj<>stream -xV]o6|Xb8p(hӴ6PMQPeN"7KIN( N3{-GTj^.knAJRe%$꩕&| 2pU[~eV7s!ޠӸ<:~2^.9 +1497 0 obj<>/XObject<<>>>>>>endobj +1498 0 obj<>stream +xV]o6|Xb8p(hӴ6PMQPeN"7KIN( N3{-GTj^.knAJRe%$꩕&| 2pU[~eV7s!ޠӸ":~2^.9 U[(8VAIWϠοB睫CpC # =ʆ`K-(8rll z} ``Ψ"`C)\]Ka!8.:!i<5Fo8c7/`v=IoGA|(zU)7szFN=Yvz={+kQNV=&Y&O9-7E,رLXo@o7$]wB{;~xYꦒPNyhɉ\4{ۆ p*wpq>NZ7 - D5Yްb=l/ 4U`TKr(jmrUfp*^g;!tB,e,k-]OQOY4 }H>dG5P(|0?5Ol&|j+Iendstream -endobj -1757 0 obj<>/XObject<>>>/Annots 804 0 R>>endobj -1758 0 obj<>stream -xV]o6}ܢQ,Y6tmP{%V#H3KJyι2 -iߐUI0q3#i5BaD8 8ܭpFW޻qM'GDe484O*.-J,A7,+8{e: fl1%_W;êt;ê08 -q+=Irh`YQ49%Pu(\-VhE"wēlj#j+JR0$r]BQ%l->LLa͜E)NjMaݮ7n\dZS[w( ,jiF*[dZXß0{r5HwB^P#AnT j0pHJ)@Tet!ME zth!ʊ~>o_^߾ n/}×&tNx')kp%-UjK0fNdneyL-u  0se!+Q(1>qWo@6zSh'73Fg4T$( ⩃%76\i9P0\!sTDB84gYH7BC=:r] Di7 d=,놫 ĄW0Ҷmԕeoy7zqx{̢1YT3p0 B\P%˓`Y9tbƛz)F7yQsj`3xN 9rQ׺qbGp}Qpekl۾;xX;Uuu8-"`Zm?t^Z>/XObject<<>>>>>>endobj -1760 0 obj<>stream -xU]oH}W\eiUTIh>UXVBOg˿3H!ܹsν5JhWB)2hO(KqFrS=4[[UO:ިq}dAeBi2 /YLwF0'ȕ!ƹʽ<~J t>6#oJdF"K#L-ZCV5F>*4;mN{YUhxI_q#[zRuGh&P0$uw a6 αw7iqk{IwB(m\뺨uЏkUȽ7Q^-挗0uӦߎkv@P%"z3DsGyzf'TGR\|"_iuY:ƴ}${F-+o.=Sw4xWR(Gu.mץg 1=R*$Vzoit% [g3!T{rJac^dG5P(|0?5Ol|j+kTendstream +endobj +1499 0 obj<>/XObject<>>>/Annots 728 0 R>>endobj +1500 0 obj<>stream +xV]o6}ܢQ$Y6tmP{%V#*E3KJyι2(oDiL ʪQt13o$F_(J/Q0$Iw&ҕ~A_Ǔ0ף(_FICYREFTJ.K&ki*-M4ED(+>p}y}. _ +, +x')kMaw8?ؖ*3R-fMN6q(h\3*-x[ $`+:6+YJp@i1 8~c$xE;D o1: |Ǧ8È4H&\ssRR@pQ +.s"+ <˒@Lwq9O/xͽj Jq),m5 0 E0Ζ_%:%w4LM02c].5- q6B mACJZK-l9.fV|[6'|r +UT(Әb{pMjKzߏ$@=R`e n'`Z[Ұj9L HkDB^:z`z{{  ڕ4WQWYXuUbˆ+i[iJʲ>/XObject<<>>>>>>endobj +1502 0 obj<>stream +xU]oH}W\eiUTIh>UXVBOg˿3H!ܹsν5JhWB)2hO(KqFrS=4[[UO:ިq}dAeBi2 YLwF0'ȕ!ƹʽ<~J t>6#oJdF"K#L-ZCV5F>*4;mN{YUhxI_q#[zRuGh&P0$uw a6 αw7iqk{IwB(m\뺨uЏkUȽ7Q^-挗0uӦߎkv@P%"z3DsGyzf'TGR\|"_iuY:ƴ}${F-+o.=Sw4xWR(Gu.mץg 1=R*$Vzoit% [g3!T{rJac^XᏴ@\@76 1EFƤV@Rkd*A?BĕYL?WRN,/C -0 >5jgq}7L4r_K[n֍qzP! Cϛ*gMxAi(󕳴5{vvn&%,Av[$=ynooOXp25Xo9iBOtƋl||݌ E"|endstream -endobj -1761 0 obj<>/XObject<<>>>>/Annots 813 0 R>>endobj -1762 0 obj<>stream -xWao6_q0ղe;i tòDl%#{GRX Rݽ{3Hi?)4Q^ F_~yȒ8QEdL⪤堻n%yL).1"igg)@cbqm;pf#,c[5vdy4iAf Z>]_ICZ ݮ2҆>z -] UX}||Xj- b<>dۈ<_U%Q]y'tPn/$ 4d.m*IGNK -`CV{TW7T  -.r|5C *HIO]iNB,!zEYʢ۞3:TlW(gS.H)Wg*Juuj#Y(+ӿV7}UJr,vBx;ݔ@mVQ؇[IwCTR $Z6;~c(U-Ivږz-ʿSf^}K<HQvsviF'ogGy 5a1=!9@\ۅ8teI#JC^3tss; Q2T -v\>'QkCH6`.Xf&CT.}uAЭ`U @+.2~ m{➫j:SNrFU}QbX8'+ d - e^_vy_wHyEGiFgT#D!Z*Tkл=w/u ƞ4&[;Nrge ©{ɼP^G,aɆdu`WE|P>[*Í\VJ/+SF+u P,F*D38$s,iV$wSM$^ -εAsa]ԡknnT'i(LUi?c]z7]G$=r#fNsw!ixΧxa֐0Ηm,4,@PmųygD j_>}endstream -endobj -1763 0 obj<>/XObject<>>>/Annots 824 0 R>>endobj -1764 0 obj<>stream +0 >5jgq}7L4r_K[n֍qzP! Cϛ*gMxAi(󕳴5{vvn&%,Av[$=ynooOXp25Xo9iBOtƋl< ynF"endstream +endobj +1503 0 obj<>/XObject<<>>>>/Annots 737 0 R>>endobj +1504 0 obj<>stream +xWo6a;$eq2`2V{+ehHGRqIŊb)04HKw|w 4j0JFσ,hUN$JkfYrٝɔY2f49+oYYww +49==KҸuEcm8wӌm$c[5vfɬYhۋ>bNiQtK>܈QBsQ- KniCT=BWBo#:gVZJßy: Ώ'6 U5{rx$i0%'ڦ mă6dyd P0Z^Qp xOQAH|@O#t S.R}Wn `s"|%Px34-E~lc)(׵3xIľŔSD89CJVƺrU5֑,me쫾˕*%9MN໧!<؍nʂj6v+(뵤!*)Gn-`M?1jrIK|)]3%b(~ wL;9;tn#ē<hxvܯ5-DqLH:n,3v!;6{~D{҈l e,7!sC1#A I4P; Ǽd_A`|4tk?kUC% + ``b ڃH@+gs*N߽vh:Q0{G_բغ;. +uB6YDB{WFޗ?R@^ёaG('UbO;Q{Fc>x +*EvK-jakA'*֎q^õpA2/ב bXDa42@*k_"8<;ϖ o/p,#1U|) +??Q n/K +#8$K> Thix"si\XuZ$짛9‰@FںrV +yb=.xXׯMk|# ~;s4\亪ƈmE\Fk]g)^h5$lsI膕Q6>USzeoYȐ a2G?Lc>/XObject<>>>/Annots 748 0 R>>endobj +1506 0 obj<>stream xWr6}Wl֙Nlj;qJ"! (hYH>t2 ={o>O '^ÛohLi2'*?V9yM;wVҪ3 oAQ⊯5׼;o؝Γa.}zɈqłk쎦ɸ:˻߀xOf3{ӥOx8c6Q`  sw@<W@4Vc {v^!8}Zy2" "=(-3L!?n7/1n_B;'쟐7 :Ň"zt>͋*-9.{)o$iOgob @a@Lzr5D.6֚T:G_` O *voLi#^^ >j.D+yijJ }f",YJJM 2Zx)כ VS+ vfB̅%ޤ&?ӚvV ]S x|ӂC>.RPa%!&y' XYzcvQW,,\hiޙ2h &6y#j4-&yz :xl/SN@sW-Vx8p!C zP O!E(_fҡ>>aJgiBM2LKU)Zv[2޴p*cSsXͪK-U;ns)38/6*"VdglFL]֚>JȅoZpj2ՊഭbǑf -(6c{rn@3z£YKmKqajD'8ctQ x_dOB{Tr~GBPAhEQCs0xϴP7̹Pgj"'3Cʿ<Bl\ `A'FmH`JdrY -"bִle@)HF00ĩNʙx -Rp{xqJnǍJYp+X<&%нW!)4Gt96h~0[L5(ŠQHǢBBVne2!*}pbdZ./ }8F8-LOr chY521 --؇A|9utUN#DEZ;Z@loGFqi mxla-gct%fL h<^0J/@U= n'f /һEPh⸲! y yGC幄9,q[-%\Sqe+t9j>l>1nXQ4 Lϕyhf2`mv|}K8t-oJb2[;b<F&}լ(4Lp RR"P@Yy$ |ڛ1gd: #~=+endstream -endobj -1765 0 obj<>/XObject<<>>>>>>endobj -1766 0 obj<>stream -x+2T0BCs#c3\..}7K#4BHP$YSO1,1/95E9?/-3($3?O3$ BUs=s3 ]!) S\C[)endstream -endobj -1767 0 obj<>/XObject<<>>>>/Annots 870 0 R>>endobj -1768 0 obj<>stream -xY]s}ׯ؇>(3oOǎSwj1Ug>@$D&KJm:{wUbEmWq?]%YtŪbwpyػ+nG <$ɣ̐Ͳ`eTZ`4G,>4-4[ LY.%ْ - g -Đ-Vg].bKk1E|XB4[ 6GI,(& TBn0 Jg X0Ll&53YH U-R))J\1b&.A@Z PT`ZB -P7 PJ*k07]qSe q@ZE`u24ZLFY v!e^MJ#,HXo,s$>1XVW -(e Xr)k0¸U,iObG(65,|/,k0 -;Y!ֱE}-X!#k0Vyw8+ȸ;=e *ݝe{ $fK|twE51DY92J`A[ay:u Z1Gx*w MDPH,$X|jسy58ਲҳيYJ v 5Y5i-- جlZrF* obL }cXG1q -f͊ada]-ge Q`-U v_e FD5}ϬbhHMf -*LY⪄8+k0@WbcxS98iuP,((+$iRP(|eD6U YLhV` `X9Ybvf!)P`"fk1B7SQhOA#`KE vhdţ*?(j,e ͸r#bm_0I;J*ȰH ڕK'p)0 -=s&d)Hv k0XxwU`ZE k0/TYo?S5s*}/X"ZXhXlAe}I8y%8gA>i3a [pF`zĉbXx>̾3Q`hFư3GlPʾ̫$NR<դSݯ fx3׌5R8rPh&Ne?}9JMS=cZ;a9xe|s@ s'rB)fOp蕫GIAPy^$H2=|7`˂!TYUo3( @ -MNp4pQ W -.Lsy14(+ʗZw0vbߑ)~xĖ 2AVx)A](O[+y$4nCEO!A@pi BNAol17iEHl mNZ&4.pR'tǻ&q|5HSxcSN!8y))ݐN!8υCʉ @rb>MHtg  N!8 >*N!%)s%j;pbd|8Ȁhde \Yu* -_)qoomzruXj8.?ube5}p#X9h@~\61-V\xw:~||YZ\ [VsلoO^8r?2\ew( vpCwPV ~%DINnxU]{:<=V/Ϸ-B'[/*ɬ׬FAfaO񔄟q 6 nu~-Gl^Gy\2-tK_-AlLA- -}LwP8Vo] ݲ-]?v2$VH08?Ln۹8]֯ -6tHmYƫ{!wmx>/XObject<<>>>>/Annots 922 0 R>>endobj -1770 0 obj<>stream -x}Z]sF|ׯǻSlWE>]D -Q$=v RJ;߳:]!?igaZ*$/ÿ~j$X.]HdHNgg[,G<,`t‡IHvP<`tP|r9K -Xf$SEbYB4-[^@IDulOg: vVLR: S#Y.g 7,;z YpSdfp#f@s/e̱,Rt`JƠc 4rfi~Րu|J"0& ;a`= UGԥ/))@QA8MÁlQz v &ccSe8:GaKujX̖.,9 0Ʃp8eτ"kNDZ (@AfiLz,P(jb6 iv1D3ǚO|)9!]b7DcPVj̲rsAH.9 'cfXz-F)io9=;W"04Qz X=MR2h.,d%^|Fdf*9!J I*e#*ws>8 I t`ܤu -x-mE!+dv#"f?Y!:L,5eȱV!\dQN,dai; ] PDFa%nvd*Si1DFbB")dVT;Ë-rZdN( E! Pg:,0$:Avɪ66;!U B^X3<0'cDcKȚԖ3=.SUO\-XjXb,)6?7C4.}FA(MfhHz {UVɮ9 jX+|bN@0? ɮ`Փu+9V]aU5MBNs" ϊuv1<3: :QcX^ּb3~&3oc5T,:L;axe=m5FE\3K$3 ~P9a:XK2F#BJԬ"04c'5j:$4,V;Fa-: Vcyl#NVĞesJQ r@Xe˒_6/MӪdiYzl.<,^5{ |W+ˑ:r,FVd=ܳ1玵A ? B;ٱ.;z vEaDa{`SD~]!(bD5 -cPu`K!QaVOMd=fr`^VMMUIR1vtbiơWHRY-Pbfo?SkDЩ, :QAVrғQDN#_cI@Fz"!88I'VsەAsR" .B6rR؋rrZ 9\ЉE _%-~m&JǧXn`NNTo|A&PSA_)X7U:q]`J#?1v 1=m/\H RV0LF05( -` ˿p!ڴßWyx~fH'z'NO.=3ꃌۑq±BA)׺aQe)5+cpsK8wo÷yM|{ՔM|ΙmM˅_Q-);]Q>lkAjw{jP&m|5\x -zb Ϯ:UrJTaϩ"i4UK6x*5_M C>9sAV%'p1߻nT;{ny칊xw$Z. _$\Y$1L}jvex3j/᥶iԗ0?;ޗowd5ÿD / gsdendstream -endobj -1771 0 obj<>/XObject<<>>>>/Annots 974 0 R>>endobj -1772 0 obj<>stream -xY]SJ}W?HPnl,.Ț6Rp{t_`Dvg7_?Kr7i/֬ܙ ȽD}/Ԭ`t*3axCB/ PEi 6Jʱ -MB/Ӭ`7T{K*AJՁ*ʱV6/x^* Ua̬8Žq3D`c1u`s{*mt FA =A`r`ӂr_ ZU!ܩTX± -ϪkUM031UE8S Pԏ -Y)axXc1gfE#gVr*)"Ia, -RpCGj 6JP֎ns -OJ8 6^ZӔ3yDN-a&Hlr* 4;{Kv -BP%S[" &im*d0LZa[dgkCTjTnsLR4 Z܋"Բz4<=3-RlJSq଀& )H@ML8SyArY"5"%qM,HXqrV"AɕTs|1vZ#^06(U,q8jYcxc*Ulg,֝=`NAc0X?Ӭ¼VMg1Xo2{AƾehllǮ :5 ņ`Rl`'Dֆѷ r -2b83)R-r`%U,z *@A*8Mǔmm? WZ$RoUYъUPf3 ż UUb4k=CLx?|ĄH<+ [tXkL~TYU3+Z>l%0mzF %d-!6 -M5([s4F8*YDLǜ0$[؊c932acVU,sXmn'"UD|ΜIk"+H=ݳa8~(Bb8$, -S] -sdFqaƾ=k 6X"lk[H(pܝ,#5Dզ3;;֘LX+IA4qn[pX!ر -e֬Ì?K߱V0Pg p'n8ςkl@*< Vl4V0.QpT[ --qt&5F0#X)8g0"_{zOZ%3ZR& _q˲P8;<,g(?SCpn;JApTq R6KI<>pA_!f6bç4L+w ;O|, F!1!h@)N~rд1 ->.н~\o2WYW!Cܬfi_{sͺ|l͏+mіB8v' j?̧vW6bq^@[mfțeݗr_BXA,;6Rxu!(<,Pd|CWnM/퇦:L| 67~C<23~q8q;M*,78f5SyͿVfnm}a,k|tH&wr4ÛWOǞC9ۧS:)_f+}XwM$>}Wm%^#47Mյ}0,e~C3CWіN -d{ -lyRb䂆TK@^7rq6_ݎH<]m훟_vs_\~E=T52ZS==w?W}U'<, #0n6vhcZa%qEF7w+cY=cc.rn^d.zrn܊ve|E׋׻};DLB+JݽKSa6y߇~|~naW37fעe;qg%7xB9:|#;ܾM[Fe*߹270-׃z(8yJgRw86MxMrGfh}-D:M,z{&aƫTpoOly܌ۡyFlPVEWu5vtm 3$[. ߁A"\qOQV7.pb1jaJg/8uo߳4߄A&9_gUВendstream -endobj -1773 0 obj<>/XObject<<>>>>/Annots 982 0 R>>endobj -1774 0 obj<>stream -xeTMo0+ޡ^aSICKlB@²ah%a ־e88&>r8kف-"8.K`BZ%)F0ٶFVۅs9S`"@4U9掙hjpKH{&D2jt&TP<; LƂ)fbVw=5\!6)fl5䟰 @rDΑ qZ%@hH"9 -Y;u:\6wl`]ƀP[@YˡJc?AO͸U05%oY\gQn﮾c}Ծ> ;=zl0:f{Vf:F0xxЬjk8g3Av>C]ZJ0nU$ů ~ թkɟl -~ԅfdhuendstream -endobj -1775 0 obj<>/XObject<>>>>>endobj -1776 0 obj<>stream -xWMSH+rr@ LFXKU|5Fɒ8lQlin<ZLivIiy&dIrEd7&'c\%3\NZnLɻ˓h:/WvƸnrUh2NzЮ4[{<*1M02NS=*8[Gofsdp0I;Smjj?o}iru8^[gž2 -ii2iM%b0B*`ZaRw~;eznܤ9s=г4|Q@^Ȍ`% L⨢ QAepS¶yi(bD:[o4`"H?RcfD/B;2<"N;\tc aE)FGZ``; - )&@6W.=GuۃH˾L><Ԯ2}9́omS}l(ج(1H"xJ) - SRG"f+Dl oo|$}}pv"=y6quw0[LwrY3(ӳvMq8ؒH%&EX.Hq]e{V;OG92>uK]VL$a_e1S29|ۛOֆH?Zy.Lo+][Zazď>`1dw[ʡzClP`[8Xٸ;xMyVqFW}:m~,׶7 Vz@0e;(Z##Z .RĕYdz)pgŚF4vEf|](vpP،W͒ 8RRendstream -endobj -1777 0 obj<>/XObject<<>>>>>>endobj -1778 0 obj<>stream -xX]sF} dc]p鸓nIH+XҪ1=wWI8M;I<ǹ{7h?#Řd8x4HJd<u0\'gKhjB`8EKT*irkI;Xi(իIT[+K[kG[mͭi. Q>T&Ntz>F\XKdENlo9E:D,^fLTޒyw8S F ,].\F:e e) -KF#DkP@Lص*H'X9-52@%)b:6-FfI&gyЂad,^Je@<0"6y6\emUh% -܎plߜD̻VXlG4U9?eT )~- $ \=@&fe08{9/JnUA 4B+ɔJ継 dZ21-7!N=ǃNX|s@79]|)PX }gG*]CTjLWIRa۩1׹+[b˛H~[c:_n??=|}%|zʹWn`R -8h^뻇\Z߶|ǖC yok/PEz~y;.ci# -"[Ő*3/ܐ%hMV7üYd7R(bRXԠ-pws :)(qodcpUԖ=t> -αj\Nq(Wc;ÝeQ= -]wFn! hX% 8;_S.Y%J>YMw]x -FVZ:K% )Hب&aAcvI3 CSle8]@"0`y/U#y)N:ڒ?W:>KB"fDQ@ORHI2liz1ik}nvilUCc3p!tìL*K?JC}9`^ Bf #PP[-V?=(j0Z0Ͱ{F;4]F(ZL OH7snթv FiC~2]x` {'a3 ف aM*g{U^Iv uv$Ca:%V@O kDl35BRX珳hEڣ8i0Jl{ƚO5l b|sXQETsͳz( -mBgb -^iz h, 6+0@c^Zx9BBuI8(=IOZC%繧;<>т|yik&JЮK/~8 ȴ/-,b VHow L~FE>UV45fu7`/(ZсYMOPL}دߏ?gճ3C6\x#2jAK#㖏)$5?vjiV}e5aBkNyVڪ~mۥե)a6I7b+ot^Fo</~alQW -9.h<>\2~ң0\胎6'14 {~^.' -WC;'[Pgendstream -endobj -1779 0 obj<>/XObject<<>>>>>>endobj -1780 0 obj<>stream -xWr6+vtRflYͩi&6_ }%tf۷g3gF9]-()Φ)-WkYy_)M5f`kqUJ3*Nl_M68Ү0*OY*BҔ2%çNSR0te߭Mbv51٘Fjgj§xU5l)3v -;l $B/=@"/=;uFgÊ{T7NGHTooHPaSqqOޝ: UHl Ehr2//d{Όitae,8"7 wo -)SUe:W yLG>-MGz<~>=uS׶Яv_;2[n -SZCa)liu;^isaʽ!2eJ&k U.:r -埙)@5=~%UP g ޱz%X 6egLTʩBc:TR %9acna>|63Uy,=Ĵrdof4(Sؙ؋3x0j=TɁ5t" R.0< 5lI8Dy窳PE,8OcbD5sI9'8~+@h3u7 sE?xs?KQ>aͩ|gv$*Q&B#=TŠkFEys; hX }jDg>鴇I$ynwĥmtgyFeeV eҨzF:$l a4: h7hmj|θ"z먹o-59d!W *0'y'̦_d-A"⌢[߽f%0:>!mw%-}}Iu&RZS!cf۔V3M(?5f2{ -:չCc̃01dXr'%,x\fBO2$Z|rDD)l9~}ǝ9c@("*(s? -WMN0 ³ҫ]N5c Ǚ1Tɽq<C 8 1c\G=Oh}̻Wܼ:̝mw0pykc?^g6:qn!kI;Y*ڹl+-7r~wl vrKzYŜ:_V_endstream -endobj -1781 0 obj<>/XObject<<>>>>/Annots 993 0 R>>endobj -1782 0 obj<>stream ++W%{ `#y<&gG?t1mb 3! ~h]Jjk FKD_#)zv*k9IHOAB]U<3 jhMQޑJk h)gbUf 5􉧕EÑx0 ,Z=/PqkŇ +x9dyR( R:!U oK +#f/M=pj-T}!QдY+e'%cM[7R68X٦\K7*T.H&`lbta2q;g(p]PZEhR*JИ*c10Ucn@լRPs6Ih_1C#`AK@m񒋣-"P`Ezt`Kfuj뿨T\?~ /ccXNۺ*V){i&BBh3:f[043G %&z=6)CretbQ7 + Yt\H[ ^L&D/C,X奡gܨgVܐ@a Ԗt3F/F3ژ042nihv"HpQkxY ?c8 0.Mqx -;匣uP- q@Wd6߭xĬQEz7Wc*MW<%! 7#h<0'֘;b3n`5+y,nr.gV-ׁG/QጤOC*ɠǷ4 7 +&2LZк-ЎOڣr ?QAXx "|RǗ~|xP׽U?%ـ&I2y޻y{A|AJCJ +(k:ߤ!O{s>tL'3|Bxr/::t=zendstream +endobj +1507 0 obj<>/XObject<<>>>>>>endobj +1508 0 obj<>stream +x+2T0BCs#c3\..}7K#4BHP$YSO1,1/95E9?/-3($3?O3$ BUs=s3 ]!)& S\CQ)endstream +endobj +1509 0 obj<>/XObject<<>>>>>>endobj +1510 0 obj<>stream +x]OAN0 s\Ҵ+H@Ȧ$+${\u,{:Df&'1jIY<&voHF s!ZյӍw@ܣ\bW`+žcW`9/rv)_Va viTDX po.]ɣ.)߳|w^qY0|T>  {f?]endstream +endobj +1511 0 obj<>/XObject<>>>>>endobj +1512 0 obj<>stream +xWMSH+rr@ LFXKU|5Fɒ8lQlin<ZLivIiy&dIrEd7&'c\%3\NZnLɻ˓h:/WvƸnrUh2IzЮ4[{<*1M02NS=*8[Gofsdpߌޙj#V\U!~_O[ϗC{lj::UMoEr)-J*l8T0Ϛn}cVKψX-mf{j[e{nbL ^|`2炯rz-g)e, +!vAڵ ~r=r؀VfS SJ(:a>F*+M:$5&LX$W3)5̪$2?j]{6i9 ",AYFjss:[ 红( l݆踱PW.==4P.J7Җ:@"@[UTkvZ[ @)#ƔВ\iTt)Ӑ$5X0̘-źCbKM:ݝ] mwRK Cmi|2/" ]CSb K d&TZj\ja2t +0Pq4sbx *-M-ٶ> e-FqAhZ,._;kJrHݫzm%^Ljc压0aBl^sspc3=2#w2XI|q08(ATfY(ܔ{m|G^ +ƩQ* 䪈b<x$7Ԙы ϢHN8ݘhXvQA.z-DF ++ ՠfl2ѽf Ҳ/+A_m#zs:Ah [. +6+J-!jvTQHkJ#y4[Û/n<= cF-{aM\]44̖9ݧGF ]*:k+$RIIQ6~\W^Qί̴ORS;;gWnk̔G >OV(Sʣ\endstream +endobj +1513 0 obj<>/XObject<<>>>>>>endobj +1514 0 obj<>stream +xXMsHWtqTa ^c&{eF0kI_g$I%qGׯ_䟓 gDsS Cs9I?FlvI-8_Mh zJ%9Mn-)#sG+ z1<_P*>vkeiҔrh35E$!"-Ym[mN20W#8i$Bl4T3iCQ/He%K s9dA 0q~?pUb.jp|Arpu,Ï[>fjX[plmVI< [ua îE:yX[9nVVqW8&*"l8?ˋ1,y奿xp^؆+%+r4#\]x|>e>|=Gp: МV/N[_.' +WCz?a?NuPpendstream +endobj +1515 0 obj<>/XObject<<>>>>>>endobj +1516 0 obj<>stream +xWMs6Wز$;қSLmi@$(!&  M-RPf۷ gA%ݬ(.97[ݬįf &ڬi納ۃ$+#WN(VFF6G*ɔJRqH)"WTN%Z4&FFZŜ7%Οb~xMi4j@O{˃(aHJ%ET(qaBv1쌕rhC[SY?B"r~{o"A=>; {H U:>9d^z_}ѱJ >~tae8"UY):|2beT \Hv2a*z v<=>qOiWg4|:BaKUJQ:zPeAespB]o涊^eVo +,^E>/XObject<<>>>>/Annots 759 0 R>>endobj +1518 0 obj<>stream xWn6}W %.(-_RYtS,It -;1"93g.>ic(-h/퟿$",E Loql23>5^ĸ2&8R$_nnnDSƉS:[&p7\c7Y:ԙ<-+'9XUc v5v(vb;o%)|\1-3=[irh3]V՞L{*JI{ '>Z⒠J?:?^$6|Ov-i#Bti^ 1nQ=*wXz| Ft3`Uu~![M.ሽ$QXbI;甮e4kQ>Ձ ](Ti;aaJ^{<-^=S aoD% iem''خDN/Ժ{-]Gs^/N>>&%/.o&y`eGJ [GDq68H39֭aSBPPz$W#Z -לdN["/ty GQpsu]tGekd0AOk()0AY^O/J? *T)n5>-|u]AW+^޹&յk9]wC”P_YIVꁫ~dе;ʍEafX3eT@_[\u_X{Ľ`.h%wR?'sʲ3adb#msn1Szk~{Yy<{ZasC {,xͺ.vX"*TP;_JEn>9Zƍ(uqdږ2dߵWnB5ȫz J7vpAnxbk0n;Vmyեt%@#gUiEW]J]Zii U'`U6U=ڡ%PL4ꩈW`@iyS$8k.y^ōE5#'Jj -LgD:[(3<x3~~xKVܣ_u-0F]5ǯ>iD_Ș7 HdDCܞMX?>$endstream -endobj -1783 0 obj<>/XObject<<>>>>>>endobj -1784 0 obj<>stream -xMo@Oc)8Ǥj*D!eY&K,,K(ݙwygz!Be ?(^+V ^#nRo0+*4<iwʊq+%RLBVZ+./"#7v+Ն.2`t-@.1$dx LrЪO/@*ݝ?M-Abu|HKize_8eip "kUT[|;! |)1›dmC.Y7d>3M;xNz^10>(;F7qjMwnP&Gip #ƹ0 -ݸ\zDb+ -DHY"?e"Ia.*fEիPQ[2K-]`@9J/1$BEt~SK\\CiyFtBMg ()֠Hڠ/8zmқ} -y)ܐ ߤ0VYBe,;ﭥ>(dw - T$ N"Zk`ױ?8 }{|э%PxuF24'h݀fY/2E :iʘ+_(qQH;E~M#\(z;*qXFvxqs ?"puj67.̒Va;Q($^.ǀqD/"endstream -endobj -1785 0 obj<>/XObject<<>>>>>>endobj -1786 0 obj<>stream -xW]o6|ϯދVlmrWw ZC-1DwϲW Nݝ}~t%e"b¿SIۓ'gS[.i/&ޖurЭnj -讥DtCVXΧ_0+鋨7YTm)(F0vMnHYBUbSɄ֥3F6jJôROړӜ‚8+ESȇS|Z4`85攉9zW\?1LV\ -*c$y"FgB&GtpDkJ¼_)mx#Ndde `uc+lr',sޅzW:{cȨtKAp;mLMWPYmtTtr7G$=Kh /dZ;d |i+D -9N~}54JC!%'X쫊%vyFEr2ÉA@F2IK *-{`'?1E^.(4JgQϪb*((߿Y|S@ ¢s=pW(5 QTAY&^BjYofn\D54M،""6yB &l$h Q|c'Zo\ϥE?Q4;֬*d5(Y0< YO=&Az¬xUD=Σ0}<yb;AK'e 3zA4a"hǍYnT'tGVn^y&@@D{k0!%t뵍j#He ĂQ/m-r1Ntkp:Jr8)uyu>?3Ƚ\ 6PV6K#F# s=fR pà1G}J'?n".61ۤ웗Ezq"aK0(W%pXcpkP(Ἀ 7ُ=go)NIƷSU,u1e"Fc%*r$^='a>;t?)0a̢^v\j0F!#g;lTsqm;UyHd)(ʤqa`sƿ+ -4\FN"`*Q@%%c蠴UW>Ἱ9m䇯pQYǍ_tnb[7շ9dp}%d ~3VW: >䏓`(kendstream -endobj -1787 0 obj<>/XObject<>>>/Annots 1000 0 R>>endobj -1788 0 obj<>stream -xWMSHW5UXrn]vة9Dd/z4ccFc/!~"t: !l?>G·`D%$8u -%AwG r.PZR{h k6.' - >^x蝦6L+8,8Yf3•FתjT@vus!'R{JᮆK҄dFބe*9yW δȤ|xir2-Vj-"!yI̷ CQ8O iU-pMl3y~KCȪK$;-uJsVPYUHS鷮\~jnc "Ӟ\ \F2ldD9owHgEΆՠdy$I[F^"ED,l\Nw7@ \A{I^2{ ~P#NdkL%sBԘT6s| |pGEG{l+rY|yU@3Z:4RhsE 8(?s)hyf}M06EbF4jwIG_߹䐬qD,"pY -F|~D`YҠ -R:1X˘Q#ULZxNZ{=< *ŎuMC,:jΜJ.>שDaÅ?oXPGӉz!cYagWC 7XcK531U$[QxQ d q {?FYz JFCSUC э ϟAn-K,YJiBw@idC9ڵ:4t\7Nћ^l[%$e~ufNVE>53cea/B$Ө MT$.o]3=yo +#Y=4?Z-T8>0Ŗ:k6 Ȩr:~+VT?40\ h{[4C~ȵK%+Iڏ -}=r.o[:;iY,-3GM]@CL왐3J([ -C]pQ@XW'so1Sm+W1[c'xOah>s<>/XObject<<>>>>/Annots 1016 0 R>>endobj -1792 0 obj<>stream +LgD:[(3<x3~~xKVܣ_u-0F]5ǯ>4/nzdݛwtsx2Ol!nOoX??E*endstream +endobj +1519 0 obj<>/XObject<<>>>>>>endobj +1520 0 obj<>stream +xMo0 DN)8v]n -+Z[,AHW{Pm|%"/d +D5,X|)Vt0Y^A@+"4:QIwSFV\!:99m@CS%9X0<+ʿAyF,tfo`)l5j?K }ZYhj™#T}ڹ԰ +c8D2档I$˴t-l[G&y_oﱵ/ڱWWn1c\_&{4ghh&2'7аY(Gw˯,F \RۆVHBj݉Mֵs'E(Et6okYIֈ4XqaWwۉΓy 0շtk| endstream +endobj +1521 0 obj<>/XObject<<>>>>>>endobj +1522 0 obj<>stream +xW]o6}ϯVlh^-i]y%Zb"I߹XBuby?9#,i%]t~IY}HuHRZ]_F.hŕ˫kZ <ɦh4LVQMAݵh[|;]?Ȋ`d^:~q8>S/:gQtF1vMnHYBUbSɄ֥3F6jJôROړ‚8+ESȇSZ4p;ްwosDUɜl'd\[L/XGq@8 Eفx v])Rkp09% O`8扈 _n(kK(tT[g;}}]}z&]vx8Q%)nu<3102+Ҫ;s &qC_EquaR pc@ J'n".ycڤ0C7/7&3@•0(W%ソ_2.`[ +@ "6jߜξEiq%~XfvpˠyFGUmѼ{pIE!yz҄W)`2Ĝy1`ʗ ^ zq Md؀a6 + y9*g:@DeCQ>çc' wc;}"8 J/T;N5\dNwUO~?e80WFf~)p2b7T") $-1L9ƁJ^u]Ρŕo^}Fg_t `, Dj\b YCj\]^wd{'mD(iendstream +endobj +1523 0 obj<>/XObject<>>>/Annots 766 0 R>>endobj +1524 0 obj<>stream +xWRH}WUkdK !SyXa,$h${ӣc\XӭND}D4i0>>>E.`Hq0prv!Aw r.P<|g&xl9UE#Xq?Q087ѐihm4{Y'>24KmFtbUˊA@*kU>ҴYtUξgQlopQ@7e]Ij9E; ,FKRyFSQ,֥'JQ/LV>B&KQ*SR*,k>oM{hU Ç))JO9iV1A&tbe[QމrʁD x#i"S֔-z CzR^l۬|Re74o0](2"e-PgZ2K`wXN.8qNr 5+]R* Q6:q썂17q/G_xQ^Q/Ӵ~*E.O Yš tNFZJzޭdಮWo`J$yA)k eb1v oQԱd- dIдUN'}녙wg$$ѮI"+ӭ2 j{u˵u=7F9&^|p?jS#I Z5yFtPc$:ZV4X@Ҭ^|,v_#bhzR`Ke!eIF\>It5I$iD!3(2THBDfEI70=UYtAjjĂ]({u:&KO^`hUu.9 +;p wjQs5>}D(-mQrUߖ lj͂ܭ˞0\o[XU#pŖg)S =۾ZNR д^g1he%2`r e 99t:P +w5]&'a/Ckvyہ3Tڳ.ӽQЏ4iYr&NǢ>VɕAyn7;(dcs}!\|GYg~on8*TR``y'%:Aimb8p)r0۠L=Y* #4H{v!<-˜ XC [|>/XObject<>>>/Annots 777 0 R>>endobj +1526 0 obj<>stream +xWo8ߟb8 )P/پbKt/5^6-1[ITI)d(Ù7oF_c +;ń B=</1xG9ͦd9W7 +MWQľ,¤21fWxpڻt!5m\6q$ i_V&;oHÖJ4/X4^HuYjSѳ6~4eEE:x<i86ɦuT0_Y.uL*|HbȨFbODMRXyYػ)TIOb]+ߐչ$yog^DVK:NIX*E^f*#ބddT+J IovdU%^w>w2VZ A?DByKw CQ$W퍮a&v_GʪHvZJI{qѺ"eIebUeH1UpΕ [@?1R|8e:Ȋ|'FKq/v΀꒑,!] y,b&"`dsYknJ7̹ +) @e8L* Mesm%s%Z r-|GFǢ{%2sZKp{U@3::44Ȭ& a\?sW VamShN6s!9XD<2"3^r{b"! +&2X˄Q#]t< h#t=zM9.{59ޯ7gKga^4^ߞ]4[R-O=ly =}=?o6xaO;= B ǽ)"P>*fYFc`JejٴNƳY\N($r=||wCk?k=W8ZrJEm*Jn]h96ˊ7ThʯO=Tendstream +endobj +1527 0 obj<>/XObject<<>>>>/Annots 782 0 R>>endobj +1528 0 obj<>stream xX]oF|X/KJ_ 'N -É{vh%7Oh.+Z'pפyE Ub: -˷*([WQV^=MBv &&>)?_8@-NwŒjPG9nLFlKRQªJ2>Ը*z -y #NK^"q s/ jEW4:%U֤Z.~WoS"41ލε_}ҁj ۫{9-}Vj m譪Sh:`4"1ǚُlbR/i1v#fll@əHPt֋Cjg]-}Ww[Ͱ&O輊cs\`kmv 6-iH^I87%vGf鱈p [.}Cs`v)ײhD丽 `2*%5sUq:2U{V6Cq)9kF&svHsƦ2@C[]WA0[DwiL+ -}2C3B 5D,Q* d5K?OBvRijq%9 Vx~1x9qNU_V -a u`߼]e72Uao=b>b~vw/n]mGR;"8)f3|' Q^Wf\c5``I -s%rB _"9=ʊM [Jr~^o!שQv!OFBQ 6P6 *ۘN`x.мJ"v#k=Z|PՁf1M]U(rEMꔧ0`Zhs?O6!! -8 ݗ?rRRnPz, tpAS|[-ȵNz$'(UjӸB/(.14ABv:ouPY.BAlb:B}\~YZOz%w_;贅JǎmDX WMl9M»{rY#*W4+oّ`ekeA)h@4N~PP!Vs*`#DJY QrܼyPThU~ &8Bf0ؼv\ nFc)1Ez@{4v 틷6U͠ݺ(lr'#_mH1g1=0qp)41Jj?5^ລP΋ɖ o(Kh^huyjU'd<ƈD#,.tؼOq6y9ܣqF0JiS:lʚD -WESpTb qͨ:`Exxvex!Czy^1R$9˜P&U: *2YjqWG[QdygG# >/XObject<<>>>>/Annots 1025 0 R>>endobj -1794 0 obj<>stream -xWnF}WLQ ADE"&W%{f/2%8H46,k13gΜ%o@=·ߡΠ! -I 6`QnPFEJ2Aj2 횱aE^lm 2!+ :ߵ+װ;|VAo牭A'v٫;~h=ikO Cmί]ݚ ^2:'|bzt -5h@{>Mc]Mo/!NvqXEQȼW佧BRFȋX,.YKN9xNxTHxx; ?|>Oh" >MDv'=j)ڟaKIMI)m=gX0I^ɂ.5 E6c3H h1Dt3q#BIrw BMV|ey%+"٬:ޞk9|\y䳛cYFEs5]ގ>\pvx^]hB7HeZl{c|jLKC m<^;Uc~r6uHbO@+E!ާ9L5kcjō'Cǧa'=l;jax8즞k\ ]eRڽoű- -ti ; jC*K]o{q(Q֘zIܥP^9Ѻ$r^&t7pS{Q%8KrU -WI*A輑׷'l;f/2"XV׷5r}fECWey 0|+oDd-QLQ~&q\{]a! S*R M>x]=5@"$[J4;?tʰ@V/DFK޻' 8"cYV؄vR }"Dj`>/XObject<<>>>>/Annots 1028 0 R>>endobj -1796 0 obj<>stream -xWmOH_1 -;! HA-蠗KJ!ڻM@Ϯ9-pywg晗yMB):7t!ޚ.`}g8cp(0&EJםKM6ڵ7Q?!E O^HQt(v:"/P$ F(B\~ݭ^b} h?xShi_S/诵H>' KN 7ΰdW>%C<pvJӅ!(}>%d=-5vk'bX)'pjH}Z yxUo $d_9 +'EwYG; 2:=|^|w>'l7{{b>Kֽ*uQJ.FiMtm{Nsb?9̏ںC'I[kf/u__Ϩ􂣿zgd1\G4^(g,ŇY> K/]-e7!w\ˣ|Ges$ -UK>KPY^4Kףu$}%w1?6(д-әJh~s;w\ BTKJz*WINWwޡzB¿)_mm:]}GNVیZ9ekLh@ l5w!N@y -rfpHr@2H+hIH -YK8/EP6( -}tGBv-Z:RXՒ[7Su+6g:1Vi3Y`iMZI}XB7,e2iLP[!h:_TÖKiڵ,(0SXX p}W{рYJ* HYB ǧڰq`:@L90TpP0U|QcV lrɑxkRTGS˛Uָ1ZCO! Nީo'<+&#o2'`ĵӨg_jendstream -endobj -1797 0 obj<>/XObject<<>>>>/Annots 1031 0 R>>endobj -1798 0 obj<>stream -xWMs6WQFD˒K'_vg[ K4 EuSJo\#¸x9rQҠ®xAٴG -38\&OR(r)үb#kD2rD|A)~DiʺsL+2`y"Ѐ"=\q*ݶYY41.TA€El8z/+Z"\q4ͼ8 -Ѕ~vwPGchp]){0ujJ/BӅPc 5`Ȏ{эzxĻ.C|We)UZh9(ҁxk* j@snn}\FeCR0^S'r1ώnb{KN !o2aŊ}gY -G[#!z=(A 6IVhUuDoDT*05u%yBQQ&UOtc6! $=OL-Qܤ{̕nÿu۪)#;6:KHuyn!Bq'xa -[56=BY0P1Ę. ێRvOV_9vP^r)vQSS'n9(>evLr{26 Vᢱf}T~y*l>(h[65mg3_џ`>v%;9WZҝD*/ 9A_FJ$ks;p]Oa9V{,o2X aQ,NYAC5;19-ڢc+L|2~hnN&9i{îHP1Z0N,Kg 1P& R!dU'E;De?Ϯ.:!8~VezԶU ];`/6#T'6Xt i@lt|&mh5ڃGtjJṋ>etas|)X?x_/EOÁb4ۭ@,Z̗~\L7_'nendstream -endobj -1799 0 obj<>/XObject<<>>>>>>endobj -1800 0 obj<>stream +É=^f4/Hj}zKo:bu],VN$1zIűj,6u\oUQƏz3TH M#|RZ[5=hu2.Weq$ie:蒃BRQªJ2>Ը*z*&'q_hUD@.>YPtIS*s9^_@\% mMw&1%aK։ws=)WDt+TgnĞANKiZyz|F#%z'?NA)(l*I屦}c<[1Y_ֈ/ic*Gͧ3Y);DZ/Gw e_=oߖ66<GkG{S*ip-{\koPݽɀlIG +MPƁ$);d[G,SXT{pO#粋hD⸽`2*%&5ca\̎LU񞙆}x"9Lۜ9PvUxI9; 9cӄ X1[]WA [v.y5,Lf XgYYGj"1E͎l/mEK?OBv4q%"Vx~1x9q/Jg]<7o.J[貂M7rEc~rw/o]mGR;"8)f+|EQ^WFF б d`I +s%rw/weŦ + -8!~o!ש~;А#`Tli`i 60k<uhp"v#k=Z|PՁf1M]UkE9ni?ҦouSB `a-E ɹyc OٟZD'[ MmhnJPGG,'%rsG9 6:j18$@uғdܢBԦq&;<htƤľ ՉJβ}?C>OxKq=fp=I7a.^i ũ,D<m@Nf ñ'}Y•ika \  ی8XɉǙ±qJw #z%t!硩R" ݱ:]aaY&y`ޜe[eߞz;ԑV\;3.=-C|(~C|L7!wGTV4+oё:G˄҇ѧסp'1F gq |>{*S w˫3+҂U˧xڲʚDu"BnB^ldDs3Y춐߮v ?ȼf!zLp))I 2g3><^ޱj^'aT[D& a5{4Z-.xhp뾲1DW}Vd=j-/h/cfsog@vendstream +endobj +1529 0 obj<>/XObject<<>>>>/Annots 791 0 R>>endobj +1530 0 obj<>stream +xWnF}WLQ& ADE"&W%{f/2%8H46,k13gΜ%7~HEّ:=_!il}ܾ>je ]49-3f-3 +׮kXVDְ 3Rʾr˨^׮Z_YW[kkX'A8Ow+m*W[5Jw6lzְq,_4n5eFa;tNjt}ƺ>Mo/!NvqXEQȼWzOR樓 +YQ+cHdQ/>rtӥDh'yDYl";A}- +1ڔ4vsM,RáQPYn1<ٛz+JY %gGLeP/}+T`WWr-Rq_}W=9r6|jineɪJT~635ty;puK+zu}K7 ܎ӫ#eh2F.EϏ5̪xA{T-c"Yu>>Yxz3S3 VS+np^ǣa'=l;jax8^+׸xX.:dfZ,0H)YaSF6&)xs3Qfw^~d$yǴPi, `OKEr| +Uˤ{ 3c1[M&AwՆT <ԗP. +i18K%8err+u%ItMj;op$%VKqHNU >$FIO" +CjʈVƲꞇ5+o (˃X[|# kaZ N(gQ5R0(*հ䃇S $x?ZAu@Hר dUBdT {HL#xY>lMh-'NH6.DSBbH_߂mLQ'uCB6d{4Vgr4.ä][eXu!=Jn+FOKy)`QyuR⭈%eT-5Djos +#GNGFa <|[joB!Bphy"B+} V8^o{2WOE7Y|\xEPm0)n_.ދK؜DKo]fpA5<t U|}9`x~.OʥIk`[:MxЦ^db X}I*Z3$lw~o`޾z]|5=['endstream +endobj +1531 0 obj<>/XObject<<>>>>/Annots 794 0 R>>endobj +1532 0 obj<>stream +xWkO8_qUʊՖIK[̠ V#1K=; c)U;,3<{þ[/QH!Yq?4woifuc?b[ (A?FCJ7G@qqzO R8EZ4\HZȂkЏXº{KU_=o ĝ3u +Ew4UdL*p4+yrN$l;}}y1yMttMh%4OӦ`h7#9o8qN_^ǒklݢ$Yqc3m_@v:z;D&L&W*M-äwa/iz hOhoXvsl~g˵3VELWo:' ̭g n5YM4QĚȗ)N y +fHv@2X/d.H +Y5K8.E6h~ +GB޵Z:JXŜ0Su'2m:ƈ; ϐfCe@]TnYd H ͘HICPu>Ge2зV΄kUQPHڱ:w֏SU +/*XeOafK $HC  S=4nW;.9 +o=Sr{y*%`O-> a!'[}qA'*.m8m-wkQHt+ Fo4NœF?[mqendstream +endobj +1533 0 obj<>/XObject<<>>>>/Annots 797 0 R>>endobj +1534 0 obj<>stream +xWMsHWѩŊ8e.! C.cilH3BkU ) z_~v2~4dhL4]kI+~'Ed +/p*裻W,\DQt>_$c'&/ӓK)]!BXP0GfyrPtSVҶԘ4Sd|glaL6* t{7ozԖ̊,|V:7ۆnSztdE'tejLYJ=!GW.UF?#F[b%5J6VT+iL[g7e=#V|&kKD２Y22^KZUckl9HT5%O8'F0ZJ\?2[IaĘeKNCi r'yA_}SU^h9(ґx႕*d 597W1QY) +,L˝ǔ\ʿg~7O&P@Š%sxgYJC[+!z9=(A!6M﨔FhՔMBoD9Tdk +K|iL^> +<mC<0Iks{<3Zq0W:ۻЪ#;6:KH<7p!Gaq'ya +͂H=@Y0P1Ę. R[+l#;(/”iX{T ;us2; ԃP^ō$Uh}9}T</^'Ȍ@8ҟ 1l[+ܡ0̅Ғd%*Uea NrZע$(]瞣ܞàα2cy?e͏b)vҰ"> iK0Uջ9Y\ H"Q,kqoxnqR7`Y:ÂBuT`E|<װ9|_{/"'p>Bak~;t>M泅4gsMznendstream +endobj +1535 0 obj<>/XObject<<>>>>>>endobj +1536 0 obj<>stream xWn7}W IP#Fĭ@jhsk+Y!wmis;sptҧ4pLi~Kz4^$#M'x=|{=~?_ IfY4 -sGHM5ȌkYK<HX7yꐅ@V "H%BE0pa,$aӵY6*2ueFHu1T7#gtzYh+g|pkm?[J#NH =9oZ-wZژ;`*,Qh%JuBS l֭:x/snb5/ΚRZ]6+2޽ QAF.OJI7#L9/sdR x>Wݕ)5^z|_硠cQL)c)tfbr!lŁ?Z %]?`%>-Ҷt/n0>0h^@pfCTL!U;SqGj& EJhf.Så~#@8,\r; Bg 4(JpPGB5*`/v/- -Lȣ5FR/A ^_PRp$J +Lȣ5FR/A ^_PRp&J T9=Ja/ z8OYU)WY,82K*^L.U-m-[D=jF@۷lvhPgKkrq(hjūƢYaZ#i|^B3y +߱s+mBոq -6had+_1a'jdb)XS%+ ı:i.m~rAЃYMG,TbT̺oؾJU4Z-wRa SAb`BL)QM4axX=Ya|Ů$|u:+K^ Gp^ě4I8;r&d2*ɀ>N~?zendstream -endobj -1801 0 obj<>/XObject<<>>>>>>endobj -1802 0 obj<>stream -xWmo6_qK-jv-R:`hx(HBRqa}ϑVlMwsѷ{cgL M{hD,h<ޛcZ`2?Z2%h,*/87f8xHͿʨQB)аfrW=? ƣh:n;[zh}fm{Eg}m-kYG†o a\`dT\"d3])YPau)\R*WΝ62PSY2UtI[]An[ɗ׎~m eV..BK.L8H47 ,D -NF:l7bkUۖV2Q+%SJQHeES!fG0F&ϖ?ҝkid{&= *tc p'$/Tdz6*ρs#qUEfՖtlG^B|2x7"HT#FT`%H5j<6+ O0DgG FIJ=ӁB3G+@sr07xKK\:P"Nk E@ݖGeRp U"A$υ+"fj9݃ 7ֹ4}m0t~!> 5z.BMerv\FpmXlvqb,{ˮ;N5:>fOz&`89S쫇6"rM!WFc * TMc^8xaDVzө `w &o?ܬ)k5䩅OJ>n_-ItMAki$̺.ds-mο'(;"3"ɰC 7@LBOaqZހ5'ȯ -ވϾ۵;&XFfk݋w=dkַJiP鐣#Q=bLe{ `B9B'򀤬X.[DvW{$.|L'49=˄lI e]'- PatOnX;àRKCF +Dqʖ͡Yu]滧3{Y6;?gdiTSL(T)E -ҧoL[77HS<& -#Tu(NuɫWTޜY>F=wpLBby}8T?х4R'aN2->1]]QB_$i渄dj0^o7^ @|?n| -x4{KSbw'LdNl;ηT<4x zcLa OƭLXQb<),΍[[1,Ð`[GzueELSnߓ endstream -endobj -1803 0 obj<>/XObject<<>>>>>>endobj -1804 0 obj<>stream +6had+_1a'jdb)XS%+ ı:i.m~rAЃYMG,TbT̺oؾJU4Z-wRa SAb`BL)QM4axX=Ya|Ů$|uƓA"=@IἈ7gi :qv2MFd>/XObject<<>>>>>>endobj +1538 0 obj<>stream +xWkOFί%%RfЂDDRZ*lYU=w6mcsϝۙ?ZL`Nq3i6 4;\#)y}dB&-Ϣryjyscz j*ź(D1jkF*Gyeh,`2n[]gK8Yq좳y&]-kYG†:]o¸霡E$fҡ;RDDΝTrDdrE ٍu kjG +]Ʌ2z#J7.8'.yp2#e^R6a9\"V.퐖YmKZllpyikJ*U2JIXCH"*Ćlt/Zat:l=  +WœH'L^34b%hgo}~rٞB^E["; / zJ]'" vWZ&t˫h'02H]@_AJ-3[ʶfErwu hw4{Y6;?gӿhdiTLQ|Q+PF#3m(_z&"I|PI:ƍfº* aol>=wP5p8g< ?{|s xO~wJFL^{85,֑r-f[ &s/; endstream +endobj +1539 0 obj<>/XObject<<>>>>>>endobj +1540 0 obj<>stream xWkoF_ 6*y&yiEE~|gHaM$۝]=icZLh:8#OfW \O4e2z(><h4&^آeMU~`<)Z -sRSɖxlD9.lC*ɮvOZq\UdjjKPEnI ⟸rf&zK^kv;훼F>Ncc|aO2Q9ulMmV\Z1HҶu*dnIC]'C*mZ;-=;c޼,`:q','.Z~  00zpuJqk -F4䡃GkG*4CStbץG̎/XSoP -v!::mY(K+|^䜋ek r =̬+T )soFȭmacj3vIsM6IJj@rU;P 1Mpzpe!4Wh]\[SKD$:TQQSsoyO'H*Ot+.kg5|bI9"S;ppvO&_Ŷ*Ψcdv{! s@x-yThB.*Al/s?hÂr8q|m+'70Eznn/Zc ҏxoTm[@zWU6v&aLQD AQA>fJ ;[*Ow {Chsn#poA? -vq,iɥ(hS/3&6PHQ Ԗ9Z6_>[G~Q^%0rۉ9 B`;,]Ƭ3I3NGW2?Pq Hf`P_]!C{ϠhxvYT1Ǘ>X0}߰9[‹s,fogendstream -endobj -1805 0 obj<>/XObject<<>>>>>>endobj -1806 0 obj<>stream -xW]OJ}WLiByHj)z++m5b{4?k^UǙ3g&;3wFC:ZPZL)^I4?^!9Mλ4M+cǧSIf~1A`Yș"D,խNcN `wgd(OW 'Hn"7SUSUcrܐ?RSO|SW lhFktD%K'||Jo{2#FDee`8/캋Y(I +sRSɖxlD9.lC*ɮvOZq\UdjjKPEnI ⟸rf&zK^kv;훼F>Ncc|aO2Q9ulMmV\Z1HҶu*dnIC]'C*mZ;-=;c޼,`:qY@ʕ>2NhCm0׎JUh34ĮKN_TRߠdUB0 uHuDo'P"_^W"A9) zMYWSl +[{Sg6m9>9lZ;Ԁ`v^/b(5ѷʔCh< +X1,/ꗈ9H Zu9= +RV8ނ)NT8'~V\ΖkhfrD8wvGL%&7} /iM6sqcUQ<1$4BpZ^= K? + #\:T?nـ_ІMFq3VwO*o5 4dD΃|̔@8w-'cUΣAtVyLb<| g*js Pz>'W+h])笠MJۋHСㆶf'8 +C ;ٟܔ{-Eߞ!x\n7);?jf,zk%`B!֕{>JɿuvNrCzLL|۾}W.phIyq} G$ނ~y>~s |QINZSYnE½2L.wΡRD 8CÀf" ATk9}XӒK9P7i*^7gLm| A-s,6 mRA|@.J`3-ɵs"34%vX Y1~5lgg +<Tߏ\d~!jd2y(ah~c>/XObject<<>>>>>>endobj +1542 0 obj<>stream +xW]OJ}WLiByHj)z++m5b{4?k^UǙ3g&;3wFC:ZPZL)^I4?^!9Mλ4M+cǧSIfG~1A`Yș"D,խNcN `wgd(OW 'Hn"7SUSUcrܐ?RSO|SW lhFktD%K'||Jo{2#FDee`8/캋Y(I ]Me󰵶#gMl5?Fq^ }&juBn3f~w{\ W9V>kP';T=pjN%IfB!(Nuo<0Keq8k\y2-5)ps7v@GU5;[۶HltSF&}ժI%G漿^|v9]jS7Avh9Tih8@S4G&;IK*ve!6*&13SzWJ\SAt:U:g~[i./ݑA6r_yR@M z%*8;ݍPQ "ےIm -b av7UG/y4:"h1D4}7xC{$y"un#^M͸o@UvE+τX ~|k 5%g;! Cx>!N!Cc3@>X]\xHyႫm592Hq[:lZ#+lVzw_nf |g:>rw0alVZkb!k|9Oc|٥;dnDendstream -endobj -1807 0 obj<>/XObject<<>>>>>>endobj -1808 0 obj<>stream -xTn@|W*UIM?:J#UЇ>am喤;wrV%ݏYD!> Z&T40)VALqi;8H^*\˅xy |fEQLI%; )/ΣEi@_+wEWBmWi]~1EѸH;UBvitrB|4(獵F }! -Nٺ(ƷC,\/#L:dG ܺ<+|6£5E(Aa]*u{1'={ -4Joȴ;PI뚬еq#* -{.Vvp^K ݹ& -#Ў2 -endstream -endobj -1809 0 obj<>/XObject<<>>>>/Annots 1034 0 R>>endobj -1810 0 obj<>stream -xWrF}WtPUx-ʮJdzu5u!0 0@~O˫%4ӍN4)-ftqIiy2I&89_|B"QIE<i>]߿لV9^.h;w;UhzлϷKu -Ҳk.9Ze#1M -fM9MU~WW;MlYڊ>W!]z~קS6:{Tۺ);M(X*U'xRF &U"a:G\uZ4nڜ*.(t[2NWWUF;۲ֺ;o -뵮T<|(0UQ|X<v=)<|XSeTs9Cu -&Uc;w,qu=}ݜ]&X@ѱ6`;@-⌃ -uv0Pf5+SZv!|Q(NڟꉲׅOԈ ^V[o`S[  -mŞBnԒ3Drd9]u|VGFW`;*XK~Ch^J -T hVpi5xy8< -9q8֧ƱZG;skaMzS}2UڀсdC KElgdrۆWe6UAk"U[z"?p,b J~iĽVum+qV68lt`R΂{4€^fŨ6,V%α0d#V@Ju۝Iw"\Bb}jm&(in-8YS{f[ i3(%U@X;H&Z9;[E0[ܩ 5 -د^s<:D{8<(G;Ց/7 %F\2?3in%uGKH2m7i 3XYotD^2IE/@(Fu71W, M WYϾ:Jˎ#.rQ q \3!YtsȘʎ~̹Q!~HCEP1 Z* RgC:෧XW@/vKӞ;H54ΐk 1#Be3~lPY'!eB|X,M|q&yyHIiϝ@MA۽䴼Cᩈ,1k@lRiP=πf׷71Pæ -_Ɵ PG!UÄ薾r$ -tTJW:GZ&+2:ny5APQTю9hs#⣟.N N&Q_/ ╎UG>#@Tjу#fG%Eˍ j d}5ل^k3wz-y~weUMis:Y -l Q>H{%Fu0;=#fxRWEl߿?_̓?'z>/XObject<>>>>>endobj -1812 0 obj<>stream -xWMs6W(%93=8NA[)dh]XnNt|r3f{3#ɜK+:bf(Ρ"q6׍ DT@y+u!ev[)Ӏ@lNra:4B9VkʋLFJ1P]&uhe uzڸsi|-(ZoaB77pčbF+'1'g<ܨWT5WN)$أ[bܯha\6jh:f߼fC8O>!Yf>lFWc|;s9q|5C7o| -oLR#SFY>/XObject<>>>>>endobj -1814 0 obj<>stream -xXko_1] cxW?mM+PxEnH3õ$opfΙ3C#Mqߌ3:>9)pp1:?䲣Wӽch:ӳ M+ᐦ~6AB 7Mhn|p:P\4eM R{-TFclE|V{CGGiZ7*󂦰X{S49]^\np쮏w*ʶ FrskUq mLsVؠ} }>o35@F#Wג+Ά.!նԇsrx gq3״TwPkXt=-Egg|Zsed')&.XVC(#/a |nt4c?3\*J %D@;+`e~Ng} -xLFe;+{߾W $tfVV7rET1Qoy|I)јfa"r#'cdB۠t>̥th|Lѫߞ2.jz}H+0+B[Y+ RzkGOaJ E}6 e({ + uƾ,n@~$阔ae-F[Cj0EDHeL82]Ў0^4A|KE+τX ~|k 5%g;! Cx>!N!Cc3@>X]\xHyႫm592Hq[:lZ#+lVzw_nf |g:>rw0alVZkb!k|9Oc|M|{?xCendstream +endobj +1543 0 obj<>/XObject<<>>>>>>endobj +1544 0 obj<>stream +xTn@|W*UIM?:J#UЇ>am喤;wrV%ݏYD!> Z&T40)VALqi;8H^*\˅xy |fEQLI%; )/Σei@_+wEWBmWi]~1EѸHy^ď0ft* C˘&2`ɯ"_,7^_uhS0K?pXwp>n81<.&Zm/am;8,뵽8,Tz@w'SIp vdSVtW6(-iLnj4Xa-~aa f?]876endstream +endobj +1545 0 obj<>/XObject<<>>>>/Annots 800 0 R>>endobj +1546 0 obj<>stream +xWr}WnBUIeWmd'UUVL:v ȱ vf =Erd>}Ɍ;..)-O)N|Oh1[T|9~RJ]\4 ߯O&7oi>u+Zg'NA;-݊jںp&fhbot[g& Vf*b띦,mE_*}j.i3bS)ONmA=նn +(iKdO*(aS[g1>80ry +iܴ95U]PHse$ve/u~LӾ)į׺"S?j2x6-Q$`2Q|X<v=)<|\WSeTs9Cu +&U#Q;Uփ2/b%Hڌ؀B8sE*T3bX .ՀENiq7\$APFy8Q+~~"]:>MR#2{F{I~[$ۻ;iMmnGrF3ԱA{z0 +:dT3Drd9]u|VGzP#u0Sf\|̓F?Qn +u%RC+_ @_}<VsAYLm8gcBƎQSnT#5&v) X>pZ%qj Y`EesS"6329mC +課gM ܪkh@D4O C6ȄҡKZ-ZDerJ#iܷUn N%[3p)}N>ʹ0 :Ň&*ݲ9R]!vgҝ @XZ[ 55JF @Tem|V@ +h1En =B6yDΖd(w*CmB =+`x  9Ýf Ywudeǽ0/̗~fI"BL&at8덎\&Ũsv.Fw~wՁԼ*:WGccy\Tkzeי,9dQeG?uUh~-g،b +3!_sDFC o6_}'-bQ@MM3d~ZsLDHп)D"gsa'-U01T>rsx tz i#dxv:dRs1bfӆ'Dv?knsZ]|͡TD[l3 za.Tz($A3-;*E 3@Mu"ϊ/X>Ln7 LJҩ@GexաέSm<|be,Zy%)NȑSF::">d rlbߌ^-^X5y3iE5j(KXM=8bF-TRYLlfPb$er]Io _bs,cD9 Fk0u6Ğ`I0Tt@uM&#'fƋTB:FPKYk!/̝^K^GYeS\j֨B/^IQD9N刽m)&7WO_ԋel}\WG//?':/rIendstream +endobj +1547 0 obj<>/XObject<>>>>>endobj +1548 0 obj<>stream +xWMs6W(%93=8N]{~ٙ^kga#=@'@hՐ\ bOMX{'8ݙv7?8\A\_*iÔ3dTcz7BӅvL8DSǍԼ 0-uI + dOʣp\Y!wϽ竦_8%7'$:N!+p.huX"]PW"%U(0bgqxn/\jp#PmP`vǟ={Wu` /m/̲ǖv, -qiV{{+$Tv5)K~4CXP5t7$;(}2PSgq=lEGH&qECÅVb?kӡnB+zÚZ:t<7+Ѣx  n[7_=Ɏ89F5GZFwJ|'%5]~@CrPP[F#|י4հ7yj B7df3;dϯ'4 zyx}pUxc1R4|Blx2M%z<{7> endstream +endobj +1549 0 obj<>/XObject<>>>>>endobj +1550 0 obj<>stream +xXko_1] cxW?mM+PxEnH3õ$opfΙ3C#Mqߌ3:>9)pp1:?䲣Wӽch:ӳ M+ᐦ~6AB 7Mhn|p:P\4eM R{-TFclE|V{CGGiZ7*󂦰X{S49]^\np쮏w*ʶ FrskUq mLsVؠ} }>o35@F#Wג+Ά.!նԇsrx gq3״TwPkXt=-Egg|Zsed')&.XVC(#/a |nt4c?3\*J %D@;+`e~Ng} +xLFe;+{߾W $tfVV7rET1Qoy|I)јfa"r#'cdB۠t>̥th|Lѫ_2.jz}H+0+B[Y+ RzkGOaJ E}6 e({ 0:5P%V&*xeLq͝Y:sppdT|}|@ uT WOLI]˫&zr8󎕉u_F*q\i@xV=0an-"!*W"Zֲaheq1(O#ѿsz0hYP0b\ $33*>)t]^Ppl\ s5$FtX՝)bDu9jT*k5C 4.4*eպ*(HH?Ǿf/^v$+%z J^nL,50S-0А2;kꆍRQ1wܼG2;Ⱥ>}Ⱥ(@|Mr08$`{czɫiy]Ƙ4ݺK^keq cH[ءKD'Fdz&hjj4M"Rł$+#WUΥ,ډDzolU( "C[.;/E3ohy9^qIr[AF>X(LV˕vXgؒ2\RX;$(>]a @@ -3786,177 +3185,170 @@ x 4!-"ğ! ~%Pn 4e^g.;2C~x65؂ 95F b5US"A`"iF/ѢQ'P zL +'n٭9><_盪YdCK37:M7Cz||-":߈lAʒه雽r !B/c][{yZ{(R0o17%41n)@쿜d3R'mQdA>&0$&rsLڑ.w#5eziǕf0%2Kih6ƠȄ-t1kok < tl!7=TH(vn,O/g?FbxvD>|uNW}Ƭ. - GaG>B }\:E_؊BK' ž tϽZendstream -endobj -1815 0 obj<>/XObject<<>>>>>>endobj -1816 0 obj<>stream -xW]o9|h@_v7=x‡x{Vpw,pBr_ɑ w(nVWU7NTޜK9Orv~1= |>_euhv}&''Xa,j\ձjjٺ֢W+]ENׯeeĵĵ뢬:U:erzTݍe:Rz鰕mGt-wήctrzնT*̞zZum.Py,j+lvSX"')jA?tkFz(}眑<-,9W*"C9i@_:y3=eh7,욭j"2@SYM(uӪ\r~ }gp)u0 R(y+ -+ݪE~j;Q}[NL=.&h[Z8oײ6!q`,}Ij*71_a&D U'ꪋji+8uϬYXYmRT/SC Y`K!Aۛ۟%Z-hHyYX$9zp4^ ->ifZ+A;XJH@RrkcNYj z)"Η蠐/Ѡ9&v2t\w ,FcB$JoQSYܸ_u^3iAi|^AC6"1GTQTEי P-cEkw MU_jHH0-'([^%#z:Pz40"@s牳K)şM3Ix\#hys'I^S{(؇<#w0: rU;ɰI 6)\Y"_4c">j0@$RHXZ4{fAKH"YβRjl!ϐQ.@H}6BRU< A*NQ2F`dߠ՛3)U;֫rȏ_ܳW^)Ks{/-x -L˭{ ;Pim!8 *&?A˶ͥPuHr,w>0tA@\ A= ,:ZFj{yPзLVv7VbDٟj;!4}|Z1I /) Q8K|৬۠wy8uAL9F>6H K/ $,=O/c-RP;Y :lf7'R0KH7RF0GP/H2 4ƙ,8L+ٜ :J:]PcZض\C1;8l-Oj]v!w`<9H7` 珿]Tk   Jb3T*VX6sq[ZhNDM; xtpoFw=pi/r@?-'oߢZ)y݁ @&]`Γ1ͳp#J 롱mP.8ΒU9>%Ϯ(WЃFh?ߒwz׾ ]h߂ tMe;d:J+:<Ic(8Al4H.1*ը _(ܞ y6-AJյȔBSq@'禇mTD˖ST$C5(CB0K4 Bzn̮18{kxAD>lyٺr+R+4 TDe8]e_q@P1c%;ޡIH.0wiq)x -W)B~B |/зR:, [`e\3myYJvPF۟`38'Xy0Y]s'dˤC1Һ3۟GǙendstream -endobj -1817 0 obj<>/XObject<<>>>>>>endobj -1818 0 obj<>stream + GaG>B qq)rNVl_"~w<9.&g`LNӽ?|endstream +endobj +1551 0 obj<>/XObject<<>>>>>>endobj +1552 0 obj<>stream +xW]o9|h@o^z +0P3ŘNH"9w6A["旣g!'L|:ӳ驜^ZG?-fWXr-g粬sYVǪe:[^u͓{ V־:Ht7ZVzW;7<>zWL0}|4RYTv?Jq6IZM9ˏ9i>BDTZSh\3{jiյaҺCMʲLJO!bmxp}w93 ӝVk^|MԢdsFrⲰ_*J| @I}kfz^oSY5;DdԧܘPԧUfx{BRR`U!^WUVU!1Vcw@% [ML=.$h]Z8oײ6!q` +,}Ivj*1_a&D U'ꪋje-8uϬYXYmRT/SCV Y`K!A뛟%[-hHyX$9zp4^ +>jfZ+A;XJH@JrkcNYj z)"Η蠐/Ѡ9&2t\w ,FcA$Zq n-Ϥ~h$-r5PmL67´Y>jܠ*d_jm+Y) p7Ti ܲFZ,Ӂ[u},:VSP'ή~L;yS^hX*v \pR(R|0j2=ߠ՛3)S{֫r[ȏ_ܳW^)Kss'xLˍ; {Pim!/]_8 *&?A˶ͥ7 +Xn}`.,pZ{BG4X.)u,FYW 0o 0 >~|ňb?HwB:5hi$k$1 't6Fn,񁟲nޱ.Kz (`5Af]:O%9NdQzh D 61og36 ޞYJM,u@z$Jl`@`#ɠ3lH,޿g0fsnL*pvC#ibr]n8 ^rtݶ?kQ_t[ۅ-jSp ITi?zovSm04 0(wORrȾRo0[%cjamEbhOv9f50?gAi9ykth%D +Liͣol2vܤ i=/WFo @,n#tqĨʩ -|vD4ZFx6;Piڅv+-@TCV`믵cJ>4CiFdAp +R )`7aR>=T]L/4}rnzVEtl9NAxȃ{vB!:\fi:aߣcXHύٕz~ N37^Edt^iÊԊ'MB+6`@(}WyPzс vP]OH X Vzaaɻa< +Gǔq!?H| }P>p[\\Lrr 26e(%[?x#g?Ky:N V>7LxV'2ilyz~:=?PϘˣߏ endstream +endobj +1553 0 obj<>/XObject<<>>>>>>endobj +1554 0 obj<>stream xWr6}Wl3~h21Q?ӫ(h:k%‹A?_F4| 39>uw6{(D -%UNfd4}V:3[׽̕ޝ3oJ2+43_V2E+G~#"3Ky<9SwpYh8Nq2 v2Z,sÕܸ[V!-ҘrygTPz{[coAG >&( iJ:*_AdpFQT*iDMsi A%|_/;H#P$뤯Jc߀/R -B/H!"Yo6$eɖ@Q-Sh8wt~QK`fVTTW½ -Xl^ҝ@D~Ǒk.md2GT!*J ylJC$Enpoj`Ņ Ow @U^pQDh ^8h/ZDro$$ u="© 0[<>}X6DEn߽4lK.p'`Xڜn`ׅ&SE{'Tm ; vkӎ'<6*oڱ9jPAgBu]q -J;@ -1U.%*0۞dܳ'={|b3ڡ>.  ,ښ %+@aP\jW mK!7  k6[m %0:E"YtsUK-a246!#)#RΎՋXèE; ɪ=Yz2P1#+OJDٲyc^mKic]óoSۆV~y9n# -8 5EI{P '34u+Rs_)3IhutPR -q9QF(A*]'*\<:T(FLjm{6Nҧ^'7>@Nw5 -c|NOZÛ XqޚQ w I:MFd<ŷ3w󣿏#endstream -endobj -1819 0 obj<>/XObject<<>>>>/Annots 1047 0 R>>endobj -1820 0 obj<>stream +r0xRRV b"C7f n7*q8HҨ B%rJiŨ1:=@ٚ hgr /Y:AtNH!#d!2Z!> >&( iJ:*_AdpFQT`JQ\BiP:pA ׋cN0u8:A7 ¡ pHȦD #IA5yT .5"_pGUp6B!Vf![z*E4t'qKۺ0UH;Ơ8xsIQܛZ)Xq!S]Bu7+P=\V' $2 ; z÷|+jp*bCϣOV }#Q>wj).˲5 y=6)عuɔC s΂}c?xa*OF +[|@*­,3EMfyCtlkvҷ*8 3@7M$`q +<@F.W +L4Z%x6 +O] }1-86 <Z!tAP7VYZ`gV11 b>Qڙ +${,2l +l`9Hqt'_ֹY&~2N_\ANG[B9g=۟.OEIZ MP_=v@8p<(<wN=^{NKT/29eUu D[`pgEW?Uy$֘ӯ z>񞍓iDɍ]M믂_S|ּ?n$f&xf+endstream +endobj +1555 0 obj<>/XObject<<>>>>/Annots 813 0 R>>endobj +1556 0 obj<>stream xXmSH* nQёܗ*Iw;?v'q/soA@]4QHQv4w #_-h qyb!A1x̨ {4{ݞ4V?~ß{G ݢ;Zc>h`qc x#[n]F=>(8: pnlqЙv+Tn8/KQKa RO;Iuz%ΌqZ1)`0?۾I!(M`wJ|3P8l Ld$H<:`M@ $*e]RZ[P8{FqXVi0E%^Fw&ԢMyȧs4py-9{y.O62̄isbMbV*MZ;S1Adze1o0w:;n}n?ևL.}ϟ&?qYm0σt" |*2jUl &@ tH02SyseN&*Z8: -F5#  vvC nйs$@8BKQ0-WA-ed8҄pa%-K}gT%֥z>M"6]zj=32/7Wi_^{S4I F2y&QpIǫVR >q3*ͤNw y @R2!7Hs[,ERM; EeVvꊡ':Өuo:~ G2ή{Civ2r+$5YƲ5[ wݴR9v$*ePZHR=[sd6'POQQn/e貥A S%6P{)TaQꥲe D erٚs7d 1)T`2)d5hrfHV9fH)c̻0:/o"dYI*V'QtR&'"_e2q.+p8GHga,M7'fKEHַ*7V+vZ7xS,@De=Ƀwz?غ9R`G,YA -,k9:3QZ*yx,A٫] 6y"}'cP + 1w9/|[WDYuSY"sfw kqލp*EvFt"gYxYÇ.[w[F3~>dADvcؽy'813S5-.V^ ~p/wjtպeՀ'*;x 0efrqZ ͺPӂGqOo"e6*'׮BFNuF2}@`N/ . ܖ4r=^i/6ވ)ec7ڐ~$AQmn w@؂B݋C$/ kYKL֊K ? -+֚5IC=ϝ F=lϱ!RD2UkeoB5 !dܧᨚl槷g>/XObject<<>>>>>>endobj -1822 0 obj<>stream +F5u9cB :wGh) +e*1, gU.eT2Qqy% ś=!\ҏ$w{ ʺ4[01]#~{1WsvD[⥀|2v]}w>/XObject<<>>>>>>endobj +1558 0 obj<>stream xXmoH_1*T@JhsJ phx]{~=ADN*"wy晙u~dM *urGaQau6Oizt1<2;UmNql#l,dH>/|Hd~$ɂI_391 X(J0b> 3?OC6 Eeb80_*ZZ8QFlMq_[e 1tg$}HE(ՈO쑏?E88A|p{Bh99(spX0"=ĦDbB,Xb[=:1bxTHM᤹"hVOc[:u.XhY$9TiU@X0+BV1Qsz zLx Ȳz͊OhUԔ d`- -B ÉEDÚZ&Βy^2(/-'3A+660aQ#&֋}@ SD!uny} G`&Bk-BۨD>TKZQEuN,Y4u',\*l3W..ODb>G[( 8vVΨqvhwEQ9>/XObject<<>>>>>>endobj -1824 0 obj<>stream -xXmoF_1I)H*U4Ez];k -לU!3o-rF'a6p|#,Osx4u?̇ NX H.mXaaV_6K|2ʏ|bB2.Т<"A|>6F78S&^|hAmRhڦݦȑ.Qw1ٸyʦ`,YPE$/@$S9% )4FИ -_%РpDW,k #vA.\lڋ5-Lgfh'{vz@|Ts@!6o@rYb*6IH`H A^(L9;&!3%! V, ggmX 0YE隱mS!$ 1]4:`GVв?v}$`_D/Oe̱!'>'H{ x&}s4CaA`4 -ѩlK.>0D#΃1`d$(Ƈ%C{&tO(;|=LEAkiK -f3r -: xC0a1֮y> k ^M9]hij@l>Q`t䶟bA*,yI.DS4Է -g EnT́81{7Jbs.V.@8h\P"J1Z€, |//,ʧ/ -L<: 19%Hl9iec1:H2 ևmӼH2JAzJ` $*Kpp^wiQ jS=<#:oJEe=2!cܵ2{f%cٶrKybyb!kg(7 bd, 4S) -YLH]A -p[Ҋ>]`"gUD}NGaMʨFy1u^j9]}tu;/hendstream -endobj -1825 0 obj<>/XObject<<>>>>>>endobj -1826 0 obj<>stream -xV[o0~W/ 5!)h=PH&/&1]g)Bڏq\jIdɎ;5|]Cq^j%]s!Jǁ(-gCR BLQB6Gm$:se|Ŋ$,%DI)_f))J(+< K.7v[s<=֣c*{+u>$ *e- ٴsF~GU"( ;NG(.`䙓?`$Z*% -Х?iɺU}g:O"u\.RYdZUK$V@Z[f, +c(DK1U(aܣIֽ -6 #mC >`.ɻy89=Ynk;t3u;;/s,U.6V*ywkwvÁ/.4/voendstream -endobj -1827 0 obj<>/XObject<<>>>>>>endobj -1828 0 obj<>stream -xWs8~q_sLnH=|y-$J+4s2%kWO~+耍]'~%۲m -m6`/i`@_R Յaٱ>@se = <{7ͱs7Ogd8 "#C e \/x~ԪVn-!QXreĩy̙^jÄIB)C6G~& -rGJ篔QQ"z CHRw>/XObject<<>>>>>>endobj -1830 0 obj<>stream +B ÉEDÚZ&Βy^2(/-'3A+660aQ#&֋}@ SD!uny} G`&>/XObject<<>>>>>>endobj +1560 0 obj<>stream +xXmoF_1I $*HsR"^.>l/ٵM kNתz晷gfrd65bi䴌&5;m<ĜGӣzߤS.G8l4eUŸy#?Jxp'unmr 4 ̕Iyn( +]<ǓQ|G&,@GӻFHaspm*ٴ۴[E>9>Mitiؽz]_&ѐBwG`{(Nsf*M8_ܸ.WBud= W,vI,dh%i01hV2Z \~R pn3p^Cw{p:1n7exYղe8UqYVDzÇ߉ktq54J@8MȚNh[~Eֵ:#; |ֻoΦRmϪftc96 F2uj۠êra9Fwk< wQ-SqA18Ve3mE,C7(^1}F(Y0u_ p .DFȑI nblÜ6i'Ne =%pO17"(K0ɥv]&7EOXu=1MX쯒pF"DZD|"1<@b++cUL,SdX30 Ҽ,X4S*iH]~' o 9 uiEO7]*`iQXӇ2VPkꇇ4ȇjttjz_mendstream +endobj +1561 0 obj<>/XObject<<>>>>>>endobj +1562 0 obj<>stream +xV[o0~W/TjB2@i"H'^Lb$lStjIdɎ;5|]h_e v+pOBc;Q\wvdž(gz)a< .hZmx%+02$ 3%|iH2*Pȧ6,ZslMXݩnf 4AJ$I素d30b u?p̨B$A{V4t?@J*ρշ c-*7%bQ˵ջ} (Bo/ POήރ>hE= Μxni=;?:~{ۈ\+"yNbnך(^tAp?6QD{5=[뫌Dp +N2eeIX2VAzHhIqr0<$\]ʥ1++'YHE( s + +'pR T דǻ;xa8F%23pҪk +l1aAATX9 ch*?nYa<$~8Mzh.FO>䙓W?`$Z2% +Х?kɺkUm GwTVu)+ B,3膕' +BLyJ%(luocH[P؟ hiG&.>Fi;/sjNZ햙ঋ?X-9ЪjZkX;5M@;E⏌mendstream +endobj +1563 0 obj<>/XObject<<>>>>>>endobj +1564 0 obj<>stream +xW]s:}W/df&ĤIM~I,g z4-N}6Ȏ˃l&wi|Bo#Mwd8 "(]@x#8έ=dv&3w6Ο[mR3kATI?uTI =j5nqAM\/L,|O/`޼-\p?ʄZ2FWwALBljqZǶ?yGXF1E $R|ǹH`ZӪ05_[кZ y>\!|{ql쵎$t=,E/&_P;,zB?О eQg~W){|g5GK+Jݪr\٬á&q+i~csmSAZ(eȦqM\PbyK(|EUjԮ:\x+;2^%wR[U%pԋ[XNM'ia@ cM[(9c<%MJ\̼s1 ӧ.IR Wwq1x Xf01s>Vpa Mzϔ׭fxrLazwa5^ɂfƿ.Bendstream +endobj +1565 0 obj<>/XObject<<>>>>>>endobj +1566 0 obj<>stream xV͏@WϠqyl_QE0GЕԕ5 daQ@fv1"KUPX!*0,Ծ3lG |\8gai\VPa8"1r!S 40PAǪroNu@|`OPDM,"O `m.2AcJx:Scz0&H::H anc<w2G7Pntf4] C.FFf#Ck -G WB#}m74YJ;˅J1ښYҢ"{&~^wz5q×͞ڷo}@endstream -endobj -1831 0 obj<>/XObject<<>>>>>>endobj -1832 0 obj<>stream -xWo0~_qJ_UhU4%)RB+`f;*m?ls|w}>~L02s 6qܯ5|/v`a6WN;ay;n=|/PUD5d%W%Mn^|c 9G_Ё;o?ds7fotmpysNa֦zo6lSL5@xol͂$sZ2Y9CE⨧a_!AyUy Ño€ƩrdN@N$r C57^G`xG3/A-i!mυ\ hupH* axĵcٴj'yAemcw@F-[­ b0u>n-?{U+//!XE١+?_w^VR$ Tmn]mk'M LIvq+ٷ4rlwtjaoYy.AB ,\$X;$s@oBl>W9Le@?蝶(lY׾~endstream -endobj -1833 0 obj<>/XObject<<>>>>>>endobj -1834 0 obj<>stream -xWQo8~W҇cw^aԓX -S_Lb!NR\Br RU;7|3j_:gp~ =h>|`7.O>a/Sm^ѫ@_`sd(XLVmJx< -b 暩xpA+w*3+nHQ+p265**2AoQeNu@?D|rЩlcu7?gs7gQS5TCfz<֐ئД|EU+.IX{6R3Oo_ȵgx8{9 h 4|Ґ.OwЩJ\4r@2xLJ 6rCz0i)> %*iW1IjSe -ALM0vc1YX8n $:؁WZ2k3 }f!#6R|`$IPhH#1;;JRCd4]TG@pT$P+pDB04k3:falYX o+cAmM1utjLN8C +G WB#}m74YJ;˅J1:YҢ"{&~^wz5q×Ͷڷo}@endstream +endobj +1567 0 obj<>/XObject<<>>>>>>endobj +1568 0 obj<>stream +xWmo0ί8/tUL2`:@#O| IfU]м0͉"9?=e@Ns%hw8m_YkGM{Nbf褋(WMOˤcx,~۔ێ \;P#3vgdJ0_ǒb~57RxOYTb+ >2\Xc.YEXP|gۛWЋh%}! +Ԋ’;3ܧR+W`㚓25뚼0VmLb3l)M5@xol=F 3tX凊). C{bc],5[ sr" SgNB= 0q$wn)k1,5$G_ +i:6ҶEp;Px]F2  %|P{=n͏I+~,Ko K.2. x}>-,?{U/Ϗ!Y١ +s0\^ٖS$ 7ݦ+k'MKf225% +ŭ. FC 9N]+:ڑGsZGO~Ft X_|1WiN(m%[V endstream +endobj +1569 0 obj<>/XObject<<>>>>>>endobj +1570 0 obj<>stream +xWQo8~W҇cwnԓX +S_Lb!NR\Br RU;7|3j_:gp~ =h>o\v|} ]_ܽyogg˧.W(RPL홬x9(Xsy^A5SڝPW^UgҹT W8-@Wd&m:k,UTd2`˜~V+@SǸ Inrmo nϢjB]e"1y뛭!M)vW]40 lPi f6 Ɠk ĝp? +`s:Q >4*xk i0!]2BWЩJ\4r@2xLJ 6rCz0i)> %*iW1IjSe -ALM0vc1YX8n $:؁WZ2k3 }f!#6R|`$IPhH#1;;JRCd4]TG@pT$P+pDB04k3:falYX o+cAmM1utjLN8C 5p:)W wk MN1 ^͗V{%%TF hMX@Ee\ZhjV<8kIs@A4Lդ>#Q/^.*{V;ӤQp."wFڸC,}l {b鵵mT!ugC.F R bR4zӵw]Ww=)'ʹ'tXf_$,Ŷ|Uta\궥6lI;]eNö?M/;o:yxٮD~SL~ 헟tgvFˎwi}{7{X -yifz`w6n{cR͋΅׹>1A?EFendstream +yifz`w6n{cR͋΅׹>1A?TFendstream endobj -1835 0 obj<>/XObject<<>>>>/Annots 1050 0 R>>endobj -1836 0 obj<>stream +1571 0 obj<>/XObject<<>>>>/Annots 816 0 R>>endobj +1572 0 obj<>stream xWmo8ίn7J{Bn+J'!L06sc'iy Ӧ*$yf<]tlCWz}%}}3/P7vk# }$M+;C9mwffew`Rǫ./outFW9;8ߌ1Tn\:w>V;OGK %Oui,R k! ^f>LLjkPuvt>H-1@[ ;yk%ɗ ԪPJkyǕNj4MfTάq_T0y>B>A5}" O4d|}k+Am}?lpwӛJ_7q0_qOLz yP329V[iΘmEJl36*cn_ -Hlh+Hf3{m[܇rÓlk 0܅%`+2 +Hlh+Hf3{m[܇rÓlk 0܅%`+2 F;%OY`!=KS!5̅/>|ߘI&; BO"<Tp:3qtmbY1wR;[ R*Q[Qa?n$ij!]3I݁]NKޓI-@N\p%FxEP-2ƪ0"I|Zȍ 04Q`HSB}0V4qFKl1T0QDbNTsuz2E\i.xRMD$CM-0V/źjkDCU3S$!pM &fQZk@n!2x/>gNdS ò1Ex*s..Sh24UB |,`-ac NQ}lBfRLR£[["v75*Wendstream -endobj -1837 0 obj<>/XObject<>>>/Annots 1059 0 R>>endobj -1838 0 obj<>stream -xWOH_1*:GA+:Ut؛d7vJM?\ 쏙ytDʃA27?^749H&Th:YXLs^;;O.h?uk?7<`-|FQ2ƹtL)|ⵯ4&? qpv^z3UPw -k>$hmeϺVS:5N[$鲄VFީ\Kaq hh_<\Bw;b$IS')p*!osojF d!3eBe]wP -mdŇɊk 7nnG+>\Wγ,wXºG(&@{kmZIij5@X -Adfp4a_ЖFhag0J.eZ Iu2.){o_ܱc\R(ϝuW=D^/ -Հ.ţq2OT"/~\S"֞h,[0Wi.iQCbх2Ƣ:S?Cnnu]i]2cF -gE'$2CmPjqDPHgyByp huͶ(Q+zϻSjȳBoX),R -;95i)lBH98vwȓו"]ENA`XhY>U_Íܢ؝"7 TwS .\2hN]=w<Rj+IGVwmThΒ/GeEń?| ArZou63 - -/6X&R%K۝6^#'Y9\?mju}WݺpoHar`jΧC YϼZ}+ 4[@ 5Ut4x@zҫvS#:%~X ./섙Ebekv6neh^1V5ӜU`4Bkk,:`~籌Ͼ)aՋJ9ד׋z3k8Hm$W4dwٛoЭw>/XObject<>>>/Annots 1066 0 R>>endobj -1840 0 obj<>stream -xW]o}+R (Z;J$7(& ~,Y)n2|9sfG]hاY7O|Bs]ep./>}7}?ECvәi1{~4Wls{E-װ4 i𺴌[i]:neh~*jUl"]m:qS0qyv|:R eҺӕT7HkMxnRYw'/_Zu&;p@bSIcnn:'u-T eSҭֹULI2)S˄tA>xN[ޑ(J8DcarIڤjW"FaZW-ӔUs1lV)ePUVK8t[mSMmJu9qHyTJ䲨XMBK7THB>*9FD" -_DVx´%|w'R+|J]dMJvS0_USCrF5|!Zcp-QJxȁsYeЁNcNV|9A^})=ϒ>j: &cAE.JՋвyJ",H/إϓ̲TVIdFn>$rEޘM,e0@{ -gcm=OYKaADp$rb UaȤzW 6Qizr]_E}G VTO&9oNq7EvSJC`9D0k`OBuOF[6ds(i,aif -չlؿr:Id?ON?ϦW\y,yy>yXPh7>޼G㞎]=ğ̞BVpb#ҝ0[p8mLxiwg0GpxrvbMp1ZvXZ_YSoww2Qb'͊߾lN L)tGn$%?2v?p@&2k Yh.f}_j}vβP\Ǣ>VL2?I ^zyAF3aO\V:c/+QQy5W^;L6a>+)4?OgvǤ*8aP, [vv +WcO͔tՒJIŌEj"V,| #Ȕ9ҩQ;S쯱Rtp-]SgE.j6bdCa4T0QDbNTsuz2E\i.xRMD$CM-0V/źjkDCU3S$!pM &fQZk@n!2x/>gNdS ò1Ex*s..Sh24UB |,`-ac NQ}lBfRLR£[["v7ݶ5*Wendstream +endobj +1573 0 obj<>/XObject<>>>/Annots 825 0 R>>endobj +1574 0 obj<>stream +xWOH_1Tl'!$SujеWzIu鴱7ɂuw7vJM?\ 쏙ylL'Sʃa27?^74==OTx6yXN3^;=Ki?uk'?7:b-|q2l(|ⵯ4%?phv^z=: M. Vhٌ|Hlâ aF:Z )Oavկt%ڨʩjhIVHdYՔgwb+ ˺,e˜r6iHY[&QB׎’ X#L-6~gwiscͅ;qL-ZkUZ'*Gr*֚J7E8J%\N + tc[ۣ{\%V$[k]HcDEYI#F77>btLWH+c-u.B RtebN;Ѐ+yBІCLWX$ Vk+{֍h1qڪ$I%6N*^ k'!JzCW[d!0J&IR?I?SY86yxS1Lh. 9ސǵ-*˨'8:k++>LV8Zc1:teQָE!"jU '6rXubeGǴ\@ ~hB[CQ{`S(i-6Uʸ}N~qⓖq%JcX&2ցoʏ-ZR60;큡 JzIᢍŠqL[U +́x0=1`VPm]-|Hb"3ș9h֢YHu$c7}S,/ ū]wrޯ'g0qHz5GY2<;oRS7޾oyܺG#lq &yBްt_Bs!U&=[ /L8t6-> ڐendstream +endobj +1575 0 obj<>/XObject<>>>/Annots 832 0 R>>endobj +1576 0 obj<>stream +xWmOJί8$R6a+!&$j{\8)}̄p[*sрxH#Jˣ~Ǖ_>MF]wz qoxqȝ4ㆳ ϓJף9# g" 4_h2yAr?8|7~SBaT8(ՓB,]ۡρVK\9!r`We|i !Ba~Y(TFrK(i"cjkpE-03wӧ ϳ$Oqzο>^q2|]Slu=&p1$?dws!|@XəWC8jBzi 'b8; ǃѡUM]=~m;Sm>ﶪ[;+}A Z\2/= E-%,H|ǧLtWN :F?%Q q=?z_Qendstream +endobj +1577 0 obj<>/XObject<<>>>>>>endobj +1578 0 obj<>stream +xWao6_qӗ&A$[8ikm@hD$߾wfBeM&2ɻ{ANc|t>8lg3`t5< +[fsZ1-n#KzGfE[ZCt.5V^55Vi,ˣ׃3l.@U<\t[e;^`cF^p:*z;{B8o:2Dw wl1z ]҆)d%rga'l%uI*)و>Q?D- +\A+kEG.LnXwGY\ڦ1-|k.s!е5K7 sgd33,ߜXۮZs"BoC{HL'|XقP|u6(PXtdܜ$zYjX;1*NQ3--jY*pЂ:FWc^N>%NBah,%sW}ZqӼǓ)gs?Z1/o"d5@&da)G9P%7l)؃vƚAYt#vS aӌ t~R:C`\c+iXhX' &HZJƹYؘ4Λm+ Ahv +̈́FD %e[dn zE?o~c0tw(/Iՠ pXvc$ ±k:eXc[@0XƒD RhwH/@V2:1aאNUw[t'iqUpQ?Jkk 3؆KPdFÚVM[ldyBON "XEf)`xo/!g` yl9 pdač0|} T i`Eț (ÊCփu$ZmJYe^ʒ?% ďAp+ŝVn9G%yqѢw4 ;S5oD&\x1fiv> g/8nydendstream +endobj +1579 0 obj<>/XObject<<>>>>>>endobj +1580 0 obj<>stream +xWnF}W ؇nHSw/E4hPkEQŒ\Ik\YR}( "wr朙їh1ɜF#ZiL'cϒVIʏMZU{yKΛVT]ƶ.?~m㍭ժVSњ;rvoxGvWSUNV7GqJh? kSjXSo`h8oK6JU"[eeR6:mW{mܗ{qѴ[b Er矶\ʶTf;/W]Cv/lZ14&/mKQ5Nm MFD ؐ$"8u|!<ɉQ$鯏ɔ^ma+.v"<P=98w]g,;0go>ڌ> 92fR$"]}>b3m= fz\GZ'ٳd@uWߪܳjp <|$>4bNҕ+SeW>{X䊘br^|v4_8MǗ2(MFwjodOcp'/mpg/mp}{~PrB4^U,h/FcE U4E("ЏeAd=5@7Q<,luvh--:8ev3:m ]h)m ~ %$Gf6͵s.L g~et}BP-DOUSlq Vw# =Ѝhiv8fbx~Tg9[n5E(n_i9LmTd'fӡ Qb;@g + +C>/XObject<>>>/Annots 835 0 R>>endobj +1582 0 obj<>stream +xSA!5?_vc~f1h՘Lmxɳ|*FȖsf-/r +Wr۶}Wt&%Y%viӸc険 I@wmTh:mϙ8/k}4s_c&Vt>Kʪ5]Kfk8[Qzٌ[rE뜦b::;nM'_(h˒6\4zKS֑7[K-%2L[{d$L;dk8_;S)2NLHZFFglusr'9"ZkUy{??QTi +grSXzyJ7d ]s:p˜2S;++S2D]]Y(ʭ~Bv[]*G[k**oޤnY8aCUU)'/ɩFZ52{ԂRH<$\ [']#JG߯c-Z]{yՅ ~xϳ$F]-A%r$j#!{~ccjmn&H(D d$4$|(t =@ӃOT }DKenE}  X/B%-GNzJyϔ%׷:@OKTéCT0qjJ_(2=8 ZK9ǐuϵ$;6+ HNMXq,{2jo^?J$mM]S,wsȎYN16OV>)yb> 846TҦ} S+ +aUrB Ԏ9֏ +㻃&oy(M/kC;cM 454j!Ҷm]3̮+/D[Ƅ 2Ԕ2SW/aC_rx*º8M<jn ԍOL]@7U +G6C\q|B+Q{OB;ЪpPinQM?>n}_l| 3WW2LՀg3?i.η6'*2Șhਛ:}x: ==x,r6@=8"oл~l709S}~T/6za6?_~wxRoLVC%=q=$@cv%&4;tÆS*TXjx Jl04IUP,\qC;HɠRUCrH<*2CNJ]+G4<ſi[=H(d+$U>KÄ>$}nnrl})$|zbn}:Zb7<1 $,Apx+\\ '35>#ff4ҹ]Q%#"tr$ee֐ qk])+8FNWxqcteCB aQuJ<6e|oGtG"\%8Lk!,"0ycgAB@wקYX`ӦueLqVaqCNw$н#51F__Y{,CH4qsE/$zS_3q -6Đ{&Tz9V##33Q=؛m Xd~=V2  FF}ڊBe}pl0^cʁ<)¸R=-*D%D:}K@_UXت.`EYq:hr`Bғ^ac}B+2^>Y( Carn8:UF~d~ۛC%3qԹZuz|܋k0(^}>/XObject<<>>>>>>endobj -1842 0 obj<>stream -xW]o6}ϯK ?Ihl)b%Zf#*IYqw.)AsGgB))-ɘɔf ⿑>Zh2[ Zf1-uCș9Mt$ؚI'T!3X5yTִڑZr+&‚/ȇҺ| 5-t(mjeIuXw|cq 3U[iʅcVQVgD66?Ӿv#+8KzM;SUnmBXU/ze_pI2;R<]$ڍpii9Eq:vDTJWnT!-yHF;TՃ寅1jȮ.}Į$TJVξꛚ'9#*h -'MDb Ū<ȳLSH5bF(fJdn'G.i٭~Vp3USaVjJcJ=󡤙9޵AZQ9F52EB"_EYٝuϰ?;Q3 -FfhilNaxO_6߉6'T^uTEM 9k尯2ΓǚR(J&eQCR܆D/ȦF\5 zQ}#y'amZPN(k%i%,zFI˵0̓Ee̐z|ns1bmZTC"*G4Jg{‡-H&"(c1{[2Z;j=np5x_X M"lU٠G"xL8}DE-2D&k&šŗ}<4/' ¿n-~8@Lpv -<𙠎0`W6N@x;cuP:bXr;%:B 7h%$C/qƵR>@pݎ^8fcSm0؝rP(#UR"w~cT[k-oI* r/DCQ֔.hߡ7zB2? R%(Va t,R[v08L'!QXM=Ef RpZ ew>#Wit܉9<$u폡m5εC/ah#P!?Ű9ݤRY `wEQƒ -ha0v 3>O@S> `a20|}S~4DnnkWARg8W^%ʌ?% 1փX9V3-q%.$Oǻi٩XL0S5Xud-@|V67xƹhԶm4>&.OӕDà ~ WNA-T40י ?f[u33C {, 3sVqw`CamL,Ov#eU&iJ 7ƥ 4] *$WO^;$s xt{&lG& TFQOA(@Ipn41|i -DÝڽU{z;5e}?_aN^k`|U?6 &ҳ :cQ)}9~usMxPIinB ``Dt*^\LQğĖo] |8ɿE0!H\ R&ʾ|ݼMjuWAk2C٥{}s76%5{zoc\Ky-fb~GKĸ |l4endstream -endobj -1843 0 obj<>/XObject<<>>>>>>endobj -1844 0 obj<>stream -xWnF}W ؇nHK4 -ZAQE$W$]Z̮(_@a;3̌e,єKʒ($LiQQiJX9ZˆIiijQNhicdq{RMt:Ë֩&ӸYNGٌҭV4"Ւ[KwQnMYқ)Z. KUKZiծ`hY;K:Z4 + wJXɸ}[3uЍYr͟y0me{Z_٦P`hLѲ_ZjCQwVTmnu V""lHax"Xe|#y'IO1X2 ˵.ze"3_D(, -BSNNЭ..8sea" Y w|)'їa\p 聀h -s}>4'm ݶ~ }"hI -z=.6L n<9!(p ^yxZU)I /@j)+G2t'*%1)C{[flM0mπjS_>r).Dyy0@0FE6Rz=ʛ\{5O/v03,z emQzU:!(M+L}iV7.kiP-VFcF-E??܃t֡|0/."w=UEFPaS -Bwx?u"8 \dZл&x@HgҶIL -X 47 7nXq\3KCUVX%b1Ʀw(BBW|| ߷~+l,ud3maE (!sjcR d{/xԷXFYE?@_j 9ǒxs;UjX9_`L|Vfim 5! b] AP{Pw 42;,_CFa8{>I2d4]$ш7}Cso;]4X,IG > }TczXO͛Ogd1Q_OߎSendstream -endobj -1845 0 obj<>/XObject<>>>/Annots 1069 0 R>>endobj -1846 0 obj<>stream -xs0۴`+H˘.J*b'1bH -D4ԛ$Zk,Dc$'cۜ\v=֧L1H :tNYʬ˪TLJWcΤSW5ĪuM3LiJTu[߿@Dg e NfAw!za8}R$ | !y= iǓ $MG&2|9f w|oMÛ%t=?_vc~f1h՘Lmxɳ|*FȖsf-/r -W]sD}ϯaN&,'q$0HZuwc~=J&/{f?xIgi_PV% ї,c%{:Jn)Mi4>?by_,if3ZeOvV%%KSM)Trwh:ig |>i^ !WH쿶mhh VKN? -pTDv6 3}+IÉ.- 9(vۨ̇2/%*?O(GDYkY'ao~=YQWj%Q:F|7uzl}-TVN}Ngh "2LV">緿2Dm]jYHʍzFvUJK+*k^'v6Fƅʘ9BlNR#'NQ\>յ@PG 4߂>QZa̟_Ψ!.\oa℉:LOQL+$R#ZQ4x5|Sk&mjIDƉK8r+&`g`7cj<*U&kiTyv;x࡬7wTI'We'Ae::'XU5%_Hk3=W\BNbkݩA<.,%0Y>#95e;NVHZ1&\$&%0&qBz<8ڪϸ(Cy<^4[PAt-3R2s|\&' -㳃!o|f:KҴi(hSK> ѐaҭ-w[V-kÎr#'k$R{\2sp};liCe<Gί(^ƅ$"XK.y\H+o>  <8>tqϖg4]y,Rn5Bra_aM\3?Yx7 ,endstream -endobj -1847 0 obj<>/XObject<>>>>>endobj -1848 0 obj<>stream -xXkoG_ѷ@! -숁8CrjfV_<(j#aNOWWUhHtDg*vG43g4^3ӵ\6e|@I>ᯑ>Z>k`H8Of( (ﶺJz֭RvQ⟒VƊ۫OV$+Ism]aT4QKNT,OOߎ!Ey4vmJᔮI}Z>?wݙڟ[Xmӓ*Z UpwpuyF:2L_11)F'F[VewNG?N:?|Ե3ewZp!zqOX0)C0Dqmhnpr㔴YN4(gdL9:P 7E=};&?qBaR:a:LXl_z]'mQ[^ )d`%)qkGO[Ul `Z G WE[ xYHV`o=1{J%zX.d̚ #{۶('H~B$U>)C``]KSct8K(B|YYމJ/_Qs -BSS"V'pxh4y(5C\+8%{0A-8BPPd뺃N(\[a-ȵl/yq" pBɔ˽9C+ԕKM7ޑSW am?}7Y.j>VJ8`-O6شL[)TG;  3(AGcw>mCk $:E5?􆣳iïKC?f?c~:8**rD{nH0>?pÀ"Ȣ^T>5o*f Bh U -%F{1NZ:%p"Fn)Q}7Q}pxDMdž>ch\vJ0 Gm'W;mcǺl-.63jկ!nͻIaeg!CB]+ -|Eiy-_*6/).Akb u d]ۄ&еQw8Y4O -5 {_SWz6Ձ|etaRS?𤓗EQZGW[کcꅝ5@BQx` U)e(&\ 6󦾒+1}o{"xv;mCbv܏i)c'?`ݴ` shuxﱆeu{px$xc"0jcx sYy%qyh~2m\ *޳&Q C Q=^%]9+B]$T2s%j^=$f3*E gdOɆ?%$"d3  -"NO(ٔ1Jdu`QUk rL[le㌗ǩQ,!Ę1|΁qs[~୑6cT]VGj4ٛ;| UCC.Vw!2vFAk%!Zz8E?T&]*dHH6(W >a2O~GM 8Jfmo%4İrCÅ(ko:YF ˪] Q(蛵Jb2T+!/2Ņ;fuz>/XObject<>>>>>endobj -1850 0 obj<>stream +:a5^\H+./^Bvwe f=6 ^': BHܠeYbӛUn\,jBX"7m*`0-/tuN%ߟ-l*;]imTͻu/L~6vx*?]~8 endstream +endobj +1583 0 obj<>/XObject<>>>>>endobj +1584 0 obj<>stream +xXkO#ί;R$X1H7eG8|@3mK~}NØ^E𸧫ԩSU~8Ft6)ۃ3NFń\t׃a1yqF'39#iup8xB-V4Ngbz:EExm8Ey6*ZT$TcknH464uT( Ϫ~Y VB$A>|4Apu?iq)Kv$ݭ74e5q0ww(̫Z`:t/+k%g}dF杕p'uG ٻ%ytdT41l1V'=V[eNGy_ΩfmqF4MwGpnq9[(FwH<'4ܹ)i.< *%jy6@,N,du/n$ IΤVJ8`A/d56R橆]/8 1H^MyBpmg41c1נ~Ɠi_./ZO>7fg~uTqX[':sCQaKE(zg}4Sh'(Ohe$ BknǨ:PTm-cdiT)cR 3bZ +wr3Oן>Ѷh8~l9eNy{0 r/|uSٵxl|JnqA(hV[V,ۼgv(lF||" i`WK~)|[$m^TLQSl$ ,Rq>3j1'ǫir[ Oll^f֝^y҅wG R0*U@O̠=HH1 +̵jq,d)+L\3E})]#(| W)M'/6tX,IniM%`6 O~2dpg_=5,V<#V"}(<1{U1<8,Rq_i JT۵-YgEsAz\^7c,Dl !,~= &endstream +endobj +1585 0 obj<>/XObject<>>>>>endobj +1586 0 obj<>stream xWnF}W >؅EY";±h* >ȕ1evV=3K -!ڝ˙3g_tc:r+OI|_)O ?.3q(1OOO}?ino5VfcǏ.'qBgٓRSg@sg`-->*kp&4%69$3\w0 -Ih9sI; -2]ښ_t: s[Rtn\&>Dy+ѫ78+l^>+b}m8!JT= (!^ë]Ycvk?"͊l0,|}ՀB{p_twM?ɉ}4bxi&>s=`z/Apt t uykϚ˫ 4Q2*y8ls/ZXb&=""ޟuJwzi -gWoX xL *## O^7=&'S6n!ɂendstream -endobj -1851 0 obj<>/XObject<>>>>>endobj -1852 0 obj<>stream -xWko6_qhDeǎbX}@PHD"e~Υ8QۡMqxW_F1Mٔf JϢi_hIp2 CFhBi _Ԋ6g=MiGŒ֒pj2uz9W= "3=^exUVaPxy40^Dv~uGWn6pz- |3L>.Sds$M~ -)O#Er{cj ;|2<-MI)Ueyjߨq%[#zS J0c0 ܴ;oXY7`;b3p94S\=))N᫡Rܨ`jG OD/7S /h-ݹZRZGElmf;ޗ(g0XɞJqWm{=rH=FÁѢ\#h0'(,Fʼӟ>C-UkuϪW[U)@;S0˄+yhq%x T/ֻlmt)DLdxȑe&I\\ A',?ty\u=Ս{_]/9*OO]w9DM]7#P ]Ч}2PPrHzռ0י 껞lqN<}qkU݊U -rc -kUnC)lR7h~Gm'(/֪.Dـ7)۠'W^rkmj%2F+6&5ߓ|Ğ by!К̈́=OїY8FI n9$y74@UV:@T-Jbbeߛav R8+@0 W'6@P=O?DE1d`pf\C!ַRy2kP-}|@c ScDOzv/1Ƀ㓀OF;\ )+24 H/XL]B%Nuq=> *+Yml=W(@fMp6uh|5xYh1[|ƳϞҪ6ڒBua4Hx69М8 -PLV}KSWӳSl/oѻ?7endstream -endobj -1853 0 obj<>/XObject<<>>>>>>endobj -1854 0 obj<>stream -xWMoFW rrP[dŲ{K08n =".%(M-6l͛ד\k.\^IR\.l)^֒jY\:յS Yʯn묗n:|66u'rXĩ|CZo얧68#7_Eق`>7*iⱥ -حmVqV\λ#M^v`+FaR]#)%/rWMd~3j]qچyi30T8Sx :m;+Lɵh ~3zݥmXTd~F -(&EdJ\1fb1i+;v,;vo[@| dab\-x\ !"+[Kר8?0}! {,xW* ɤU`X K -d'kr1b|2&yL -:` D G= &< Sw(|RCA;⇕~Dt`1ՉBp8lq~aht!_NwF¶$al]\YVFN -Uw G Ȱ;9b+Y15j „MߛOO3~w{IrD_'endstream -endobj -1855 0 obj<>/XObject<<>>>>>>endobj -1856 0 obj<>stream +gWoX xL *## O^7=&'Sc6n3Ɂendstream +endobj +1587 0 obj<>/XObject<>>>>>endobj +1588 0 obj<>stream +xWko6_qhDWǂuE\ Hj$R)w.%ʼn0lsϽ2i4SZ P|UG f×^z7E#s|S) )168;iEVpj4Uzu|<&Xx>Vev\fσ<gϬ3?x-µw69h\{UT㶊r.זi%JTt0uE/H +U}Fmn)5u.)WB3Ur8$TIG. .n;vy<M>(PҍR%k +rKfî,eҺ"Ӓ'{甹x2gHy@ʥQ5-IfJ.uiH͊,WX2͌Ϯ^/z.S]iDm$r dSAL7ݿ9C?^~V;O!%_i(^noL@-V ~aZFc\CS ǰ_.HE[Zp7tzVw/19nڝu7ڙB k=XP!nTqe ]i'')Άo\exV*-Q\"u 6e3L=K3dGī住GD9V$\MhgQN4zW;#r2ktp|85* nU*}rvy!6H{ɳ[C\kYlUǛѓZJImIdubOynZ0px((;L8~۶ÁKxPHN1jiIP:R_3*1zLڵF*Brw2| jQhajȚI/P7A/s"?y4||~'mnFQdQI0wKh .ӔLJUE4!?k3EU1e9@{r:`ABz=+^.w9CO0l| qP0pA}9.x<8r'7C=0Yv'OLf_Sl\Lo?67endstream +endobj +1589 0 obj<>/XObject<<>>>>>>endobj +1590 0 obj<>stream +xWMoFW rrP[drzK08n =".%(M-6l͛ד\k.\^KR\.j~5[fdb1x>y,.dF֩$rU5ؔOdF:eNk+M]nrɅ/0ql*n Wrq87Jxl)ylB8vkUcE$.kFH׮梤C/#yTHJɋ{qS3_ hjz\,a^Llm%s5 S|ReT1CgN +lr-ܨID5 +Aժ􂜔xW ,ظpi8)tsFV()+܉#¿߿D?nʛ$ IܩzgL f\7iJg +è4xwO3A}>JrcQunT +%>I3Q ڡ~]VpڄȪ4{1 ߁;H1Gx/Sf-t~b@,iA,f/GN;]h]NKj J"=O/&ƓblMXeG&֡ @f;h dЈJ5cX&iu8&rlz*tNb)I`HF"?rӅt ]un`IlA r;8QG36(God+DHTv]b07}?*v4ˆU?Й]R6,* uv]?j}D +Y[K]n"SY%3h4b;F;FyԷ- >2jX{0Z1.H܉іr +sbOLrȕ-%RkTq>Ĉyr]=wSlNd*g0,%Gݓ]59X 1I@x>{ +})JA"tV0LD!esDVG?K +s0v/;Bwa[ae|0.,+#x'Ԫy;#dXi1G٬X_aڦ͛㧧Ռݧ@oRf\-g8^_/Nendstream +endobj +1591 0 obj<>/XObject<<>>>>>>endobj +1592 0 obj<>stream xWrH+8ı1GCZ Yb -4D3ޯ3(Țn>ftsIW JdJW3/oMj9\z2듋shA!tJWΓ5I6R ^Zr&ٶ&Õ^m7nV&׿Nt>Bzt-'.qx|2Jv;됉$HmxȹQ꒥k(,ǔ~&yF威# ^.rL;VUԐ2KDi 7qkY7U -wt=: dQp8n -(H@U#,4 *MSۚeWՋ9wё!A -_ɢBq&J׵#eR杊mx'Ċw -a!{Qn4d G:9A* !0V"I GejBa;:yci "`xFz!W\\@RHuvd<$=H쏒%3П3$~Hn|$b2]?GzSu.c1saLiE3cV72t`p!')P S*{)e*ZZʄF5>fJogX@ǰnĒd =a@NHjT).?>KG=E&eᘗ82/hP+[gBQpl{ʧN'xƔd]s7(AĢ>!:, -.4ڨv?#/a"nF+'eVG58JP\REX"'oLĻo3ʢ^lNöVCA`b)RK6eņЮ3 v\1Bmm{R8/p7*T@}`-$eeX'^NWUƥ~q+xmZv* -:C,*3Ѝ)6 EWUx0Q8pݺbҎ> C);5()VAl00mU@j9!'/ֳD }E&Dž fork(hZxqgBw7YtvB! C[1C7ޡT\=/xxb5e;=_WMWwWd~-š *χoXdq}LޙN듿Nǟendstream -endobj -1857 0 obj<>/XObject<<>>>>>>endobj -1858 0 obj<>stream -xX]o6}ϯK3 QlqҾ -[lv Dl(Q%xޯ߹$rv($x?=~=t3(l4f4XIex1]g˓ˏoi\_`jJq4u1sIZxIh|N QmP,o$RV䞶ozTuau^Gt1& 5x -%pȥ3LzH.iW9T*Yٶ}q"dV)5mFۉJVpB'ʵ57.6qDq>Q -R_(PU\8Sgn/&0*9ǘL T%|Kdd,sRe)o'jIcaQ_dveɓ ?*D|QETPNƂpi{+vqF?5 -YD7iZ g )3y`.eLck1Ј`YOI`AZMI%fT$SH\h -oRQ-={GJepn)W"fh~$~T -1^,oн< ᮃ :"RxAF!C9w\I8 H{dEAi ;~cB-oʍX|`!Lnm ()Yi=v+4]}C<]{05lǻi Vqy PU |SmP@^/p?S i@ e$blzvabsn#9}T T& 9G`k5+[ݑ˽liy 9^ b T 4vy O^^ fX!abVAq RV@p^vN< @/=q6 +] =Z;79nF>.7܏_䧳lv=Ep4f?/O~?$jendstream -endobj -1859 0 obj<>/XObject<<>>>>/Annots 1072 0 R>>endobj -1860 0 obj<>stream -xXMs6W-LB[-;:vm>(2ӁHBB -@Zֿ(33xX$}"&t OdFu{p\7Zʋɬ>WzA)mizrQM>䴚:ɄKx;8i^ZNSMnmHtUgV92-²q?LXP*<987lKms6"/ۛ)bgڊkI5 /a7~}l&olUýEirѤVʺH(S`[vt[+D=SSVn(Ɔ=p"صefآ2˥;6fG@A:ekҮ;gu+~6H'ÄÓ1 WtF>Jo2R@l-Q]i0zS0[Qz$Viͦ8'TUaykdG3E-[fv:jҲK|#0뵩 -`Q!-2 *hI"geFw;0gL{xG1Z#Xe T>H?TUCZ # {M~Czdc -i̝pɣ~ bY*FJ=P%&hCYHMRPKT s$:칹KhNQ)kaJ62HD)ƚؤsY~!7@"f]Zl|Ӥ8+6vf*X>ڢV - PE lr I5i{i-~+R){_:HB&Vb,)UQ%(3]H -90,dW" "~\37;;0lԶ}KXDo&*W^g[Yaca&ڙ.,o I4&\AH:'m|||Bxa8ʰpK -BMkGt1% !XK`188t]e9,jBC^Fk?)"d"Q e{m?DdV dY1Q+%NӈC?Exbk5Ve $f6gĚH9Ê:Q.>¨6_ Qrc%0T?Fm2X}K`[Axٴg(7'F'F3%$T=| |n+֠)g"_&3 fxfȕSM1sO_ C|endstream -endobj -1861 0 obj<>/XObject<<>>>>/Annots 1075 0 R>>endobj -1862 0 obj<>stream -xXMs8WTIԗ-ٵ-'Rr$!cAT*eׯ_7ŒJEe-~^i Mzbݴr~1˫h;\|f]WzփUpן=mt9KzKTBY.2ʔXkKMi -+Hѻo:]UD۪4;:uR=%jR@HYWex8;}bA ( h.5c5;aM*޳7 ԸG|nVd'> -+lŧ-R\}0ȒKCgJ4+S"Zyރ}>0tLR?Μ¥]C`>B #12T'뎰x{QhTXW,{Ո>F|cO\S l$L{T}'9p lu-oh&,/h7gmJR K%fҦHبd+JݛC t@8C@p|,I]$!BErЇۏ_{'-'^)3 O#P49zՉ *y(E,:ȕҰЉWB]y WR]E*xKQ;WL>O#~?FWߝk/ۘ -䆚70(zV G99%,))$D~΃Ïs~{rXAG=$ijEn0~oN>J*1>TY)=(z=0l#~.ot )ICT8P,Yq Pb:kΎM]csɼF4v>@oŹQMթۺ3X$qktJ30 +p$Zhͱt/&EBv\>My}8aGq7ZBj=SA!`̗[qL_,A2 ia%j%d%] jYg5:\¹KU TC20}ԣmϯf -Zapw}"^V\&f: -ČӐsiI9<)T}30pBʕZz>iXk(rXPWѰJ}R%hC 48z6Lm % tV$m%TŤE_ŀ0$|}Gm{{zƶ:19}ѡ|5"`).kMf<;>k`gG0ځMUJ d ,E5I2\wA7$H " aj}`ΫNY0%Y=B Ql* Wͼ>'΁orP"O 6'(Mκ$ DOkcItuAQN7yed"P(N^S˜:$Rqj<"I;>ƒ@yWRAYbDZwP<[XFZ|,hE}lL gxK$S+!i/Eޔ -J^xa## -${q4Gm V!=MEy#*qqg]2q˨I[]zMux=L'!wlg^0ZOißv?qendstream -endobj -1863 0 obj<>/XObject<<>>>>/Annots 1082 0 R>>endobj -1864 0 obj<>stream -xW[o6~8@1u%j H׵Cm: Dl(w/lqlwnߡ%oW)LPԣ0:ˮ5ſV@e,yr1X_~0J36$MY56܍R$p[&,cOv9]dFcXVܓ=OZ9} TnCL$:5P("5b/0,r(}lmdc:&tA\TG(E{]?w׷ob. s~haNjJM;<0IXCf˛:}dZlZ(#t1pe4T5M.U}s%7%(0M3,;؜!?cμlj+)ȕVJ# -ck% dsh&91K2nJj[7twJy7c2?%Zba ΆiCw׎|:KX2;,2;2>C)ϮEDvq$bWŃ:Da[hm7FR{AI2T>mAr^|| 0 Z3 ZzA%6*ItUHjTXYbs@d"Lqz5*wl -.ſ  /ǖl/^x`rӷpG0$XJjSoeibmѿ3>Xendstream -endobj -1865 0 obj<>/XObject<<>>>>/Annots 1093 0 R>>endobj -1866 0 obj<>stream +4D13ޯ3(Țn>ftsIW JdJW3/oMj9\z2듋shA!tJWΓ5TI6R 5^Zr&fK+剽Sk2 o3\z/ oMޯL|vZNia[C]&oq:He%vf+!I֑)Cs%KטQX)#REoƫDLJAtIUއ\|@3^0\Mf]jHǾr~)rz$:,ԐlΨ.Qǣw(Ő[Z pzcZuC;?Fڃb೯ pN7xj$#݀ōrlK׍_꺰 $!^U_1B3\4QqUsx]J2 + p,)gŸD]{-08{\+E ,{hީؖB|Я-,d&j0`)$X8M)RaO"=z9p.u*Yөn7jPh- +vaG`y!Xd(ًT# Q$A2`||Bb!Il&~ȴL  +ԹA̅2xY]PȄV98g꺛@%Le +Pj j)<*Ma-úKS%9"1\%R3] | zMʘ1/q0 d^90V=τ$(UX_?0CON +)ɺ1> }}nP$E}BfouXr \*iQ-;Fj ^DVNdg.\%Lkp*U%L6SK#ًP.EOޘw> 3ʢNlNv+3 2 SM&)n.-~)Z5AT"UL?to擛O:Mdžendstream +endobj +1593 0 obj<>/XObject<<>>>>>>endobj +1594 0 obj<>stream +xX]o6}ϯK3 QlǵӾ +[lv Dl(Q%xޯ߹$rv($x?=~=4lh6e3?VR^goǷ4Ҫ ~)vF#Zc&ݫgJOWO7vOKiT.O/058a|\^d4_RTkA[h#T- [Ib{T۞?U]c+#j7 ] {7|M5F n,|:8\r)>> EڵD$0BJVxDkxxܩz)Yr@-`ocM8dGd+v{rdM xMrQzEO~T*j˲Ty0g +%"TUeY3.Ǡ 0 h1*Uɷߨ +KgYJ[ĉZx~X8aFX{"r}$p4 +9c08_#|T8 \CZ]OeiME| }ւ}Dj((CLq mjg 4"wSRG?XV!BSR-;C0&›TFTKϞ0RY= m<[HMDPSnjjŧ%‹5`Qx&n +G]{ ,EOfi%*6VTUPR@y"eGy'u;υz2MߎvqD=2zq;I[RA884k1-VnQ,b NZLRNJib0u}S(ii죋cycHx)J[HwUPScjIp[^m! El%C&Ǩ/񪱪 +Y[[+zƮ>bAw~%}~U;1C+nLIxd1m 6mB$0LMF.!聡Gq7jx:pR;7I_U#BC DARDŽRh}( !Fb( J'tE7Lw<ё!@Ɋ^%Sb@l@nySn4 10evkKPGIJ;AXn[6>ݷ2;?f=ާ7Lv7YBN\<`C(L`͋mtv`Pkb+'yj5 +  g' ozφrPwo܌z'7i،g\<^po/ѝqL7:q.s?~Χ|vEM:?_iendstream +endobj +1595 0 obj<>/XObject<<>>>>/Annots 838 0 R>>endobj +1596 0 obj<>stream +xXMs6W-LL[,+:vm>(2ӁHBL +@Zѿ)13xX$}"ߎFt]|Je}tV%> ⼘=b<'^h4(^h:5gŨV'0Mi~Ы F4_ZN>yy|g:Mm4!5TjxB +6*ƭz[1aJC/|NFoٖHl.D^IwS6*^hW~}lXrm{ IuPlm*xG5W 쉉TNEOZ\ha`ꁗ!~7dKS6m?Վ0s/Sb +8һ]1-v jVݧN 'cAaAY!iӍ }49d,t=R(,`'cNAwɞ I2҆EMsNJ]י.>R۵je`FJ +/ x¬/צFH?TE! _{Dv)=lmvxEvHϐl`LR0yP=yXn4A,K=XE}H^eJ} WE + +ra;*K.IqQg8% ~v~ll_0Wڼ`Vؘ=ЄW;IE0k9CR+$W~h2 a[_zd9iX5b<=:SqtMkG[51% !XK`188t]e/jBC^Jkj?)"dWBE6EW31g;hv!"ӂ>JPt-ȊZl\RJ=8ij8V^(,PEk[A=-WB3=c.^JY*Et8`@u?|Fnvx`NjɘM˔:03\utd; Ӈkk\T-YcUNfX NofsA$o1.ȌAHc5F'08Y f#BtB!W9C"dvK_Cb9N +^cOH&9p)⟌PT /ZLl]7a~y04Ԧ'6&}aRÖWYFs0±=(]#pO x˕-ǀ!E?2 1ɠ@L|mw%BGʍj#8a dwc.nqffӞ\hj+)/ P C1𡮛 FH[.R6?f4R%ǛN.^r2;fclz9~u/<@|endstream +endobj +1597 0 obj<>/XObject<<>>>>/Annots 841 0 R>>endobj +1598 0 obj<>stream +xXMs8WTIԗÖwR)D[1 hZ} iqf*2FׯjN3zA%,:Zf_jv_j\4-m)WXgVѦ,ZV_z5#fMTB.2ʔXkKTKWwt&Uiwtԥ?2/zLޑդT=tI8וqv~Ռ&%ۥ#>Q3n}T9*\jg92jw~Ox6p//+}LVMHd*Gv&:O3[W|swrXJUd#lQ5INN2ͅo7|M2񷏴gsm`)u2l{D`d:eQ +Njj҃]%mչ‚]6% vuzO՚.ju-**e"0 7X~"ğ}>+Lq5 C8_,D > zt2>cF{eJP+o{i:\BǙsV48Eȁ|D;&W&d~Voq= + +keo'֨֒Oq >qi*S+$Rh`Lh( X0nED)vH/!Q"aBE(qvo5 @|$uY"HI yDn?~;?.5xL,<BxFWU'Fah`4U2="JB+.#\ t#dV^IQw/ES\2?_> |>\~ +wT 7NDAP3l(?t)aI9'yX) <)+*W OEU[Wyv]jDu8z2ђ.o.d \iƪ|E_qh:AWhv:tO + cDOp'khKWmaURtDOs= 6Kt 1YCT8P5,Yq PbhM殕y>] *il}Ёq#B+ sbU+qgP :H1vyߏ+$:/e/hQ6ҽ q!`p,"4: ^0h pOY3_n0]| 48Qf<ۗ\3eE0p &.UiPAD2;Q~.& (*\hÙu%'h}=Y,JWsᚘ B(3LCΥ%<.bC8Ssw &Ϡ| +Wkya-\p cC]]F**mJ| $gЀ 3%@.̃ЁZZɗP}i=X릕U%}1kB&w0i9‘ݦhE6KZ6]HX?0 ÇMlς_ z(i峟vW?.qendstream +endobj +1599 0 obj<>/XObject<<>>>>/Annots 848 0 R>>endobj +1600 0 obj<>stream +xW[o6~8@1u%J H׵Cm2 Dl(w/lqlwnߡ%o)LPԣ0:.5ſV@e,yr1X_~0J36$MY5W O +nG)Zd~-Ml{ZyEce|)Ÿպ{j$n4ӸVyB7[>Ib{|Jm D@Xx. J>|yy٘+00 3]P(ki`+JQ^uǷ  1zFJ\E9?0fp+tk5E_ +uOb$S!dM>2ot-ke- n:2^Қ&MY*[Jacyv &s6gȁ63q7c+l_hl͐a\"FRھ!gܹy0C1\n~@\7a#lah hxJ%\ʌ-A`UAdt" +4" =ˇaѡJ6١0-h +rXZ#ܿ>ڪtΰ<}ҳ̯a]-hgOkXr)v_:m}26th=Og [p'cSfGg^7@1 ٵ(6DWxABT(z PHj|=H#IVקm=迠]ތob%ѲgbGJϫ?czΜ8pDh4)Mbqoּ3m>84UKWCRHd5j(Hi`WUa}{f iZP)(D5^r.мH0Ǖ4Jݼ$eroOܽW\͛h828 +LXb3Qp0B8:Ke,F5mQ/Qߜ 6uD &ƭx-W-FKg^-5⁹Zl^sRνd = V2\dɣ\ Dhenkjmt0Eq>slrCRSRVF Bj0?VJ\ FtGUlP~` ulXIB`F5|‰ػo>^-@j{ÏvN[f C$:*$o*, O,H19 |2d&8=g;W6}q_[ +cK6Y/<0SRo,%|5𹷲4[dl1I/oA|Wendstream +endobj +1601 0 obj<>/XObject<<>>>>/Annots 859 0 R>>endobj +1602 0 obj<>stream xVko6_qעŲ؎`&)2M( -ѶRTI)KR$.8`H1~t b~ 9bD 4DP]X ֆ{&i8ESxM[Lͺ0K>x$>hʡ%7na`p)Hv2ŗ,JZ晥?TkJܗ6R䊖F7}=Gp7z\s^oDߝW( &RQZ^Pk -K~% =o?ݙTxAvԢ EA{ZRRf2|AJnh%p54~~݅eUZJ2Mـ@@ՃWWya/9̅]) \jR3E"N;wqNA.4p&[K aWؼ\\-)euR|A]ӝ#Zޏ~zty{[gS`@qэO ^ۖk<+sDus ڳL%QHowP!/RZ0p|D7ta=uү9kNE1`߹?w2s10VZCy:ٕn^0@^.ۓyuvkjyL=oT. eBP G>ik_|mizn 9# -vYx.rNMM^!u2s;t}i@lY*ڏѼЙ敶6d}/\ +K~% =o?ݙTxAvԢ EA{ZRRf2|AJnh%p54~~݅eUZJ2Mـ@@ՃWWya/9̅]) \jR3G"N;wqNA.4p&[K aWؼ\\-)euR|A]ӝ#Zޏ~zty{[gS`@qэO ^ۖk<+sDus ڳL%QHowP!/RZ0p|D7ta=uү9kNE1`߹?w2s10VZCy:ٕn^0@^.ۓyuvkjyL=oT. eBP G>ik_|mizn 9# -vYx.rNMM^!u2s;t}i@lY*ڏѼЙ敶6d}/\ SEnlLxO{enRt}w&虇ۂl5>2J"[@Vi7a:-u& 9\!'LwYiyQ[ke p1HW07Uuȁ '_STSe[KG'`и{L"4)RsNqnH+Iߺ8gL.4,('+,1nKpa-6hayR+rp2A hLB!(A,1lȪmp>/XObject<<>>>>>>endobj -1868 0 obj<>stream -xV[oF~WHZVUnM۪Ҿ1Lbϰ3㰨gfl JU=g{ t!DYuxCw%vI!Hp?b@Nyw?}$~<:v -/2 } P\SɩMQi]g \ kJo47㪈j$*}Nd;+µiz\b2gy2<.14#p2{CddљEk^X<¶NrY(0aB -B% 1 5B`tDy쓥 Ï3'*l]@$ ɼ^=rKt*Rk[vVKe/7DE %Ds>ՑL{pc2B]Y.5ü`LJ9U {)b&iH1ӄdJjl}4U0ł#:Aݷa*+2ku{mjrx^z0a?l`i{&RcPd+WU۞ g!bd_*7!&4Ö)!`,';M*  1g !q!sΑHv$BFLA5Q/-8q21K*3%f6J /35|c*4;Fo>6ycVWF-fd.ӐPhH0*L&JxpamJ{(=<2d|Bu"E[Sɶoo/Z/Oۋ4ZP*6n.B!_YD8u(ܔx: O|XĹqđ  hvS/#rɨhD!nӣ>.fZc7endstream -endobj -1869 0 obj<>/XObject<<>>>>>>endobj -1870 0 obj<>stream -xVmo6_6g^ncH[ct%b#H ))u(+b6"^;=Ͻ>LC#$Ew}؝`2)ֽE;5iD3}dŒL.>|8Hv÷/> 'noV{<~ -$w^.KOU+uڱ@_?ut%nIAa* 8{I3G+!CUO[rn*Oܱs%W=F@GciH.֤F5iTX6yL'\iML Vu0q TRvqQ)"RЗݷp"RP[!WR՚$q0Ys -wG{לx4)tL)aәzt8@H x4ք8ͪNgMGݖfcDY=Ώ_R~bsT LA -7WQӭX0eԖ›ʞ$ѓMFԟ/?zޕendstream -endobj -1871 0 obj<>/XObject<<>>>>>>endobj -1872 0 obj<>stream +͉+wBSQnwE 7LqE`b[t>/XObject<<>>>>>>endobj +1604 0 obj<>stream +xV[oF~WHZ1BVZUIQ7.nJ2cĞagaQ|@E6({ΜZpՅ:WBR k&xc01taԼm kho>rT4ALa2e"W$8h bơ@y甐BI֌("hQu^S@/)(JH "/@ XP )0D^>8wYkcb~)..`*㦟+""v5~%ڋ7֛d\NnqUDFqn~SN>s~'UНZ4=.tG1|2<.14#p2{CddљE&k^X<¶NrY(0ar+9K>bZj̅^`䥲O*ʃPn ?Jlz^נ`u2$;{p@-ѝ"JmVZ-EƖĺn/6"P͙oTG1Mɘtcf8]W"YZK3I#DQ&$O5 STUK fեZ)D]ֱ8쾍VY{y\ݼkSCһz1a;L{{4$[e'/?Eބ [4V@WHS4l~X5ȏ9c s\F 2ze + m(xziY/YHTɜ)1MQf}I7֞9C;Wq1x193 +3j1&Әu^q9 KdGX)玢s#B$NY[U#LUSڎ9wa#ˉLvY8mͧ)4,]'.R*hU>/XObject<<>>>>>>endobj +1606 0 obj<>stream +xVmoH_D4=կI݀ZAhtcoR{7x Օ.i.!Ż3wI]a4v'L ɼx4)IAҾy2BbI&z>w$su> 'nxZVI*.\&ZyXE?BT%U)Z;Bͳw:A!;ad9[ZV*OKFPV.\)@Z9ҘR);8!጑`|:RF٫:=#^!7^اX R^1B?)Ys :9SZD9%#b$,ZKrLdQeF*75~+0h)/UHh0UճYICT0944hA=E%u)P}>ޱ@_[ُO,]Ii*pR}@~^zJPՓ +CwFn\qɕ}P%7Xj5kM GӉnZk:wt\j |]iT1e-,s:c74h:v)A,TfVMld,&4IL.-?N6'M,D +uJXtf``n`PڝF< \;s +x'L3ow,vo +tЬ'wljd +dJ-FL-w춊k޵ykEC7VV=S8 TP)_7kwN/>ͨ5ao#6NjtiADѴ~/Og)?DL]ltZ7WQӭ3eԖʞ$aH&#ꏍ_/Еendstream +endobj +1607 0 obj<>/XObject<<>>>>>>endobj +1608 0 obj<>stream xV]o6}HlJmdn=dÀ-6cTIFlζt8"׹ܫϝb$4pLiщYLGӉdFNt[/j<ŗ&iv?tb6AUTtIѩVX\K#2ZjC NV0').K.H9~}yl#O2YQpK&[٣ QJjEݒWkۣ6u٣FZRZ$ "jk\<|B3[?30bV~ $~~yM"$UrU -d4m{6>Wks޿? 9Ay#ܑ\Ǯ9r | u+"QTbY 3_yF[婻݌(ITȫGryYlSUF(yN :=y*FKZLBqM,+ C`RMɈ]!C -*82K1\lRˎCM靖`w+ϪJGw-q7RKU|n!YۇDM8%TB a衶@!8qE5ZL|7N$W5,[mTtu AygFKnBw(9rr Jd5Nw\y,E1kتJa7$V6B-yAn;c(־7/xrWsa5endstream -endobj -1873 0 obj<>/XObject<<>>>>>>endobj -1874 0 obj<>stream -xX]o9}ϯҾP) IIRZuU+Uf7ڞRkaL~@(:{׳)M3KQYM .kugogw4|#W'5/x6ャ{۸RU2X-hZԟ7, -ogJK+JV`cږ"(k.i dc^{e8T۪Pd>6CٍZ~ ajg{P6Aѽ$)ӯg~GFI_'vֆ_ҧ/3>T1BH^%>LUqSL C Z>~R=6.BuX1; %UT)Ó#̨dl #-#+aeU=}i| -!AG - xSDV_0uPX0D҂_*]"[`Iq '0ڕ&Ջρ0{pHZMd%KU$-MPڔh#ƺZV+.mA[(BF֑ ]{ (Bj# @h9l@c.X,#6 Zl3 bPH)d@]L -TEȰY1f(22=Ϝ bU>הqËݧHHEDƩĽ҇t:d+54~6L (rxl'~0VlTv:$-m{k<l&\:PqG+ksfV,aal-@s}ԄvRT[xLHA׶D;+[Xw{"xFN`- a'\,182A -EoCRz 5Īctqi簯?Q ~4!8h"EQN6?ǚĖ>nrеAȫZa U_S*nxw">VOwp0&|ၘ -ecX򮒆;wz?bI|Z([N5v:oI94aG7n1+ownX?M ⟏v|!cX+@si1->=-)>$,LiRN VqOƨ~A5y-?8w068P=Wc!M.5.!+3z: uFǨ]=Ӎ_ϛp ~coUKes_h} A0oKߢ ic;ε]wPEO[?ۭyZz7(D7٦On to n@r>~5}t .֖Mɴ]/n&X Q{{7 -=}h~y7+@;nendstream -endobj -1875 0 obj<>/XObject<<>>>>>>endobj -1876 0 obj<>stream -xWێF}+JKioaQ&  iԴ۸Wv/;|}mf2 SN]\B!LG0 x̦xbޯ{CX'%Ma.XӁ/Hli V+m Ljd\0 a -L6VŖa.3v̀1b۬ -`2JѐHȋTs"oV{SoJfDq=< YE E`2N -mX)oД=X6_{x53)1 NBI[iRJI@*M<}aYOL09&2b`0Q,.ryK[V+[*r[`JiȬb-W,g5OmƤRln%g -FB4 9*#KmX>/XObject<<>>>>>>endobj -1878 0 obj<>stream -xV]o6}@lَ-M@da@@KV"Us))NT؀&Iޏs9ALc|ǴtNI9Gc̣ ͖ Jt|-O-LƳO| FcM%^1mn>4I>JLѢ QPۑIm?~YF(ELLY*\?r="B]"kOSkG'r9p`'5Q7Ni*S3T(-Id@iVmV\z -e$6sJM-$U֔w>ܐkE;{lԖ֢ -DN2J2﬩]KTUÂgysڢ/ˇ"4d^RhΚ,GIʇhAoQ[D(h'`uF8 -CVVR8,mF(u/ig*I`!1YQz6?aM]5%[q G< UPt֦oKZ4 lyYsPʕş!rA?$MBq PAD(!E] PXV8u7,ʼ 09+ Y%W燢s -Fiut3i]HafU֔%2ܯM;@WL/R6Z&BhNk&q#pظ%Tz>fb6 HT* k=rڕh`TV(ahzeÅst)Yk -J&7,+ -8)5m/A+z*TRf>OuKl2ܶuK!Cph)OIec xkʣZԙe9ȴ5wWا \7tL/q 6Z5_yx|U`k -h4fFe"50slm84-0ndy+,:NQ|IYkEDF'ExjXpsY K -iL 5UKS5d,xV 0%1y/kjJ6VpM&y Gb0eV!RXU&2lTop - .g^񬼜2ܾ뫻W`g\tcna}Cr6_F yG7?k%Aendstream -endobj -1879 0 obj<>/XObject<<>>>>>>endobj -1880 0 obj<>stream -xW[o6~ϯ8oN[If P`ɺ@7@KE5+.(X"sRY՚b,h.5nopu{\?щ[Z.hC-mrB>. 8i(N.u&sz =Z{Yڽ{V6YM,Y9kɪq\g-F҈B8Tho$PU|E^ZYgr - W!tpWy:hխe"ˤ]N]:] @֢vY*kNvJJ7-+*T*JIRX%Mқ؞UiBީ}kTgQm=\]H9=_7ɹrɢ<d}alB˝hKG'e%FWQC!sYYܻ8%?~|/f5_.|EWATz<ߗz d3֑#յ wܹ,y(l[(~Tͼf7sUD*jeQ۪uZ G*VJtޫ m6`+xM$4[V]. B~=;*I??4.i{`VΜJnY"iyN@S -Uq@8L*G*ݪzNݪR*L/Xo<ǜq>aĄPJ'~T_7`Щ!0ڏ-+nzڌNzbk1PMEDEmɳ&WmB (:Mk =hwfpDv\GJxJuoъd ~m1N)+UYد/8%%/@js:&Oz ޭQy -vQB[eO EJ/Bq?ˤcT.&dkW6Hwխַz +钫_uαendstream -endobj -1881 0 obj<>/XObject<>>>/Annots 1102 0 R>>endobj -1882 0 obj<>stream -xW]sF}W7%DZ[;I3SaD*sWd:Bs/ZuиGEicW`8|عFNV/ݩߧd~ I+>ß1?}Z}J(lM'&{ДR?|Cz`8@t`^VX -sswEs7Zh2E"F,D&2Hzn(CV?ё2垢DE_U&ћXBPtO" y?q-8U2Vm%-LyieqN ¯>!y?`UpT?ܺ^DYaF¤;.D첊e1$$eeJkg}y,&iՑ}_^$e8Dk mu*T.TRR^@K`=TBqVWraNq]][p ׸"<@+G٦wT‘$Bxx.y*QZB1XsSqzC.t)m9J]F0ώU%]K>>ͭL֝ZO U$W(\N㯟L="M>o.]tt﬚pN',L7k:@5WMر:ZojK\&sn:ڰ ࠑ\K"1 -ҹ,Re r?2;DKBWQ{[mG>x=O-rOZ%\yV.M>qA+͕lbm(tbUQu\Fdky 4,jγH6MU-?N}L޷"H_G gxo{ - .]ZmcCACme &U6.51@S&PryĻLy82bOJ^qGG܆!S,f&Э!rQ8Sɺe~pfqF`~ r p+rָFɗJY:z-׹b^z=*Z0H71(xih0+ 5c#q5m#vy y<+T*:k[,6ڱK D>Lx*@ . -1mĔ@S2i<#1Y%w|9?U띡 uhsiD2oSEu!?]{8I_#'%w2;w?כX Z&-H-&EW - U~v>vN%/Q,| ;Cm*4zZﶳ[lVQ Zm_kG@~8ç!W j=si|FQr7}_m9C§O:)pn0&PL  -|J.څ5hecrsw9 Y"LO#|G5= otT"ay7N`4GC"AU.Z[Mendstream -endobj -1883 0 obj<>/XObject<<>>>>/Annots 1107 0 R>>endobj -1884 0 obj<>stream -xXobp_6eɲ,C\áhb\J[\Ҋ%)=Mv~yfϦt?Stuv]/fe64[PE׳l>t6|t2M;OKB2[½lުzc`4fcCQM'[[ֽ#5[\Is=lYHM0>\\okvr/0,.otxـ w&+.AFՄeЈe˓(Յd?: z:Սn98WO sgcf E/פRu;5_r0a ;^mH\S%xumo޿&RnCP@ HG{Rft-Nx~=_YWۦaیF*a[aa:7@ʮUR`R>hUq1:"צ ߁}M㟌E)ˆٻm+hrM]FUFt[&${_wG;b_ VD 2p?|'_(7I2=p݀3G3tf2,+ $o'Zݷ¥!\F͎ jpEϸ3K U⣻@r#T}6! [b]n@ttÌJիH:Q03 s?1|Хb*qJ[QƭyN7 /o(1g~:ϖjKWҎ3|t&:^&xg~ߊ:6E!L)pN0QvԜ)?J>L2;`[Ǩ޹~gBF*C0QZf:~@ID5 =);W j">+v16nwK ׺>rcH7o ->h~^1ڗ1zQ[B7dpB;y),Jۮ__8o%O4_vsF엳Mendstream -endobj -1885 0 obj<>/XObject<<>>>>>>endobj -1886 0 obj<>stream -xXr6}W5[cfvޜ;3vITHHBL -ZtvDO>_Gcߘ'4QZ]L :8/5(}d:s?Ϗ74| sg]E#)l4f %=yGnc/_wv&)Y4aNzm|ReO?Ft2&$1l&{:cמV+dR'ՖR}ؓC*tiX7mS,]*oUygLҍkF'8ctiR<%|l&K̷.7鞰[VY[Fn{3q) X0.fbb,MX,*+],^g&ĥ  5 AU_m-`G ^H?!{!`b]['VVc(Sê>9c?ȆʪQJГ: RAiU#[<ÛK?'q,xIIfn~~JOa<Ƃߘ\(`o0w塷lH]u41~-*/ -CKg;RH?92`&rDA3cӼV xhYՌ~ |F 4U/HBNGfY&Ā*㼵LP`!ozPvn'eWW0ǤhwT%L*W7MIA/zI2LpYl^N|惈Qv  =XcEniTYYvk}/rbоTs&ўEl1'_k nmY~VTe ;GUԘEJZ,$b^k(3N{jyNK7s+ge -ፂ* Y0r;1AT͐o]5!hv#(xXy?“,uKS}TqURZ% ؚ?!:'v*Yy' -a]a1zNU:u'(8cn#`"CWa|PjT^܋W qƼhz{>|˷ćjHeU`rSCs~قT,Q -8䉷:5h`> {]*F#F^b19sB)LĖİX0qXu@"Papi{ukU'.Rn6X]=plQT|>QV =eQºy|ajKKֶ* 2BttEZOBsDF^Q0Q>Ts0vmr l)iK`xYCFwec_ZgOX;Xiˣ6]gr}^TJ\C5ߥ>q/qkn%-K4~6 ȗfh(j HbMwicpS ncO픋4P<0w{Ҋ+hn֔->qO&7cD+I&E Q{;i?9]=Ğ.7`^6>4G> endstream -endobj -1887 0 obj<>/XObject<>>>>>endobj -1888 0 obj<>stream -xXnH+ -99DkYle'V2ْ:&LwӲUB3aXf/z_'}O)NzQFA4u'? Mш}{K_"h~;;9QOO.hz4OK''gٲϓucؘ%_uvi:QaSohaRsp0WNϜ]! s:,R)>X& dyavJ~ ;!b;ڟLhll"./'vSt$@)*k\:qbK땉W-Kx6iJ*ԣ"U}L\8k_YS(S\DZ&s(oDuJTD*q]2A8ͩU -K۴,>1##*:M&M*Z@qH_DH3:a;;T 2Tۭ^y/y8T%P;;gUNy t -:yxIO6-3Mm -H?~M8lNN{*#t`Ė`C2V*yȰ4|;-?^߽{xin.)Ucu6`1k]>7R|3p +i󪛪ȉS%E:.Q)* d) 4:Pmcnbėvx1丯We 40ݵA/W89P |ˢea -_K:m? -d|pgHUD1h}ؤ(}c6!#J64w:&Ho(/y[A|1H"\v*VsؓkDĵ}z }S<*LdE-3Z 4%w"WY* U&5aCF"["E 9Fr%l?-*iD?Cpm<Y.0wLc?q/JD zr:u2_¹Yd s2.y|#cJł{ҲKDgVM=D,*vdt' {$Tik7)Xc¹&Cy1N6р01, vf fxUH:!z5g7~5Pv*Cp43x)` }_v^)#bN6-"+OٵR,\CW}DfR<|mEW!Z 69dIդ(L4>Cf˛ $>_LԽhUV.FZ=i1O9W|ɗɠiendstream -endobj -1889 0 obj<>/XObject<<>>>>>>endobj -1890 0 obj<>stream -xWn8}W .(:iҴm7. 䅖(D$g(]"X\Μ93q0 ~t2$l&{C_ɯ,fѧ4=e )- Ʉhf])Ʈ,]kї=ݺFo1)IQreХF490[c@SK|h]ې+xh#^Kp [*M9 8g3v;Alz6!xU%%IقrW7mԞHV'!G4;(ޙ@VFuƜog]L:!(ͺfl)}.iZʽ?@xjU4-VNһTe -ɮA7V;jGmo<ޣ7p"2:wux JL-PkPwıu l!LvMd;SJGE>MRgڔf*1eTȮ."`?#EˀK@ OWƴK+`޿]]C аީƛ`Us/cN{h"9 -i<7 - -`| bpiXTRt_؇4Qh.~̤iuh,N#bןQBj6Ŋ:&|'0&ijvo$4dm(~bΉ`دAmN4gX-/Xc+n8ѱitcZum&u;zF@.oD;H >/XObject<>>>>>endobj -1892 0 obj<>stream -xWo6V ز%;3lv]5^ڸ؀z(hH*Ru)ʮ`R%ޯw1B_HMg) "?E`_߄sz$l>.hkI{aŷi0p|qpf׫+&JrAO9{z)Q*rI7yz /tWfa@(jw|Faǣ(&!`2V|iMUP)TֈI鏬z1He_Ӵ\dp0B&k c _:nԶjGFQ4ons9 )-&ZJk~#?Q8uh(3T)+Hf+5,Apma4fo?E ZJAWiޔ|n6#" :o5kQba2U>j'a:FHR%LT*C[qRm@JSǔf2O|Vo+jڢׅyal]0BYldm$wR6< dv=߻oު{U!Y1"C(Tq)I8#'@*=Nlf lÒ 4FЋvmGۖA }M?36X5$q֧pa}7wDxrLPrFv!Z+gNɎmScIɑm.Q6$ [7:DV ;8&a?ͪҁm\Ih<߀uRo2X~$ 8[yrD(]"UYrV?axյf'e kΛ+a~<~vU@@+s(h(⻇21bW}`ٶ-t -o̶n=VIIb;褎WKܤpϸ78(egÀ٣Lz(PKs~Ý -\bp4YUvƇv({~u$onqbhw1#nGΣ;\ 1r]?X` tqk܆cV _w^ V= <|_o`[d\_20 Geuz zendstream -endobj -1893 0 obj<>/XObject<<>>>>>>endobj -1894 0 obj<>stream -xWo6?f`p -؊$SuŊ-i膹hHGRM(Ɏq$~{є&ŌN甖GdBy2qrq8M7~X%-s/%#LhSS؍hkKM/hojM':4Zt[;`yҔFWӝ) -`(hWCuLE|ΌilMJ=R/ϷfﱾbJ'kt7)Eo^^':lZ(V< M#\,;X>/XObject<<>>>>>>endobj -1896 0 obj<>stream +d4m{6>Wks޿? 9Ay#ܑ\Ǯ9r | u+"QTbY 3_yF[婻݌(ITȫGryYlSUF(yN :=y*FKZLBqM,+ C`RM%dC6Ƈ~Up)d=bxڥ;-WU16[nIKٵBܷ#A7u.&q2dם)K)@(CmC` pjP4 }o`03IjXFmQB܄27JPh1r54F^ t0jX {Ɠ +c`+װUL"p{I;o~/Im(!98[v57v2ǂQ y^ K'Vd:3t(<ԥ%و\IaD˽~z 0}.&J9'paOqn:`NbcT~8:SJec潁.J$ՠ'{^e,ЩҨK!JGZ<ӭD@gˬEɽ4WA6V4l¬w /K!^+dLu6yN8~kПh/I,}}oF)_~#üK+==endstream +endobj +1609 0 obj<>/XObject<<>>>>>>endobj +1610 0 obj<>stream +xXn8}W /.v.N@Zt E[?(hPKRu{mYQAvΙٔ&%]ͨ&ńfW5]K:I˳kNiđ-+ ٚJҋ<QQm\)*d4~l-eTK%mtE I]+YQ1mK5dk˱ ]LK=}l +[mh zo_][d}FZ-N?N0jg{P6Aѽ$)ӯg~GFI_'vֆ_ҧ7*z!Z +j| x}I/vN7MqUӂP>~|ͅ_R-UI^ff:\X*EfTVz26̑0*聾4>ː#@W\]Zשv +ɯ [:I,|i/M>-ufᤸEYƄJPE@S 8&r%ӪPa&VRmJ Ldc]-tN-Oho!O#HPVFh=T!A T 6 1WI +F,` n?S-`ԙ1(H2.&wxJdCz3kgN|zQ~Ej{* ek8yS +$I h"T^p\l:2敃o @?M? 9jB;)-PpKv&tkpa,;н^k@b A@L23xy_IÝKX=1ŤsA-d-I;7KXŤNKհ#ѕڷ^7vD&Gw;1k\IqNhY  DL|?)+C yDcw^q~׿ t;qNAԞG&N=: cԮƯML[dYα7ye2빯CF o7 oф.;(_׉XX^wvmMħM<-=|yRܛR"}l'wr:÷wW~ ^9?z}p .ƖMɴ]/n'X Q{{7 +=oK|Nng 9;lendstream +endobj +1611 0 obj<>/XObject<<>>>>>>endobj +1612 0 obj<>stream +xWێH}+J!4[FBQfZi%QnCGvӗLo1dFca}ԩtB/ЬxDW U00U[V1 )Q9ɞ<-jpSN[}FQӃ $1Lٱï>/XObject<<>>>>>>endobj +1614 0 obj<>stream +xVn6|W`,_b;}& ``@@K]ԒTCIquj̙`L1ǴtNI9.&hB'0/婅I<`t%m2/"%ďc$g~|4I>JLѢ QPۑIm?~YF(EL4&oO?U¹~&{DN}j7~'Dמ$tWOsOɱ76Nkt;!p2gHΐHS蝡BiI"%J{J o ғU(-#9(Sjm!)䆤]C.j/ܛ=d뼰V rʕQb~gM] +D8˛3}A\>!Ƌ?}R!Z[Q + t]n@(g9Bп)];)~vM[wp^rev\pPIziP\Be T-JpuG-oQ@sV~N{M 2/$L~v3m}V GzecZLZuD4l%Fh5e urK#=?ԩFI"Zq5?8đa}8l*@=RG1z\C*ڵ؞BEnp9J[0[L*+0A4B95gkNƛCXLנg=Se* ` 3%6ln%Ր!S`8͔k쁧MuQ-L2dښ[;]+m:dٗ8B -tA/`_<\ *x5Z43ek2j`~96UVPr7R2R<Ÿ+,:NaN-a4i72_;"GPw'=?N֥@Tk*tk<=>\sɟY>3,8 'E `FyKb>1^Ԕl> M+#Tqgaʬ4C#5Ledk.Td \@K,kl=f<dzrJp>^у5qҍIN宆"ⳓl<:x' |tIendstream +endobj +1615 0 obj<>/XObject<<>>>>>>endobj +1616 0 obj<>stream +xW[o6~ϯ8oN[If P`I@7@KE5+.(X"{R^՚b,h.5npu{\?щwZ.hC mrB>. +8i(]'t:9=JwD-꽬d^m=+Jply,qP̜5 d8KNSOR#j +iDIVi! Tw7qt>Z"T3ic9ҫPh:܏8n<42eZt.hCBRkQ_5';%QV%ʌ–*s$)& yCul*Yq{4;]Ծ5ӓ +6ǜpkLz\A +}dQ^q>~ T~V6wGN#듲!ov,w }]{ DM[?<U`q/o??H+"͑nxüR"Q㹟uH4!m1FfjQA\C9 *Kn=KHȑKzZ;\}[ 9}TmCqg)<:`2 : }!qF6'p5#|`@8n|B`܋L4"SĂS?NirJ]f +|6 eƓy'iy^{DÍ|/tմ,uA |rIֳCPB)C@P^=/=VN'.߆'x0%:^RUj9t̑=Z.e#`xh}Up{SƅyO= +9U3oM_1 +>pr|jF) +$)jB[ p?^7+( U7s{|K1°9<z;J{,$MK؆3a l[ְHZn9Дa`U6<Sh +6<rr + 89CO1a=W tf7yJ7#"أ9n-T ~Q ya,9e_U_(2NgS2~igtE*3ꝣѷh~ g GeΊX +*{,zuYNu{4ؘF>o6j6%춝@2xSo;(v;!ɩG2/H [YY\OFp:QU}@B6CCKoQA~qj>/XObject<>>>/Annots 868 0 R>>endobj +1618 0 obj<>stream +xW]sF}o8S#Ўح[;I3SaZ*sW&t #<[HZ4|,^ZӠWOgq04??![ ^0<2!]/6էFl2 +BA7i@xD{ۥYrXp XʵԎ&|p.JYrdI)wd*yQzIFӻ?罥sp.>3KϯҵʺB84n[0K'w*MAy݋W&Nc!yj3QdŮ$I[Vw\ EVe1$$ZWl$L+38j!! d JH[-hgJ&"%6f-*h.)/ %p{!hhiN8S :ŕ\X5EZW%\5.8ʇQ>HY!Ek]Qq\Pt)d̹8nX@Q F'Au \x\+ +-ve`K:7|].[Z%{ 't!t#YJ)/Qĩw_?MZ"]W}ު]I5[ +=ҭRYVo&לU[cu: +\Ւ(j9dch^Ar$֢c+HX+kf#N̩ +D]U-H<=dEnEZ4- Wax梣еE Dq+.wGiXRΓHHVݾMU-ڽ`4P;ܽ%%37"'^Gfxo;eg)|]McCACmd &U6>51@[fPyĻ0O,Lnw"7q  Džy6()dY2k819k%0?S]ScNk\"rM5ǼR^un'<(۽^p`\- n+9bcs QE`;~l}f:mdܪ5/8~x +Y@mi:Ԏ]H$',1`ƒVlV!omQHyl94wOQ,9ø˚T:5[KWZlrRJ#TKq8ԏҗԅh1|s/ՋJOZrX$h~lT_V_8My"?iAHΌҊ^(0嗝f ktb,ywۻ39nn,͠tF,E^n;Fl<0&m6JpYC?}=>y2:?C<[ ݛ%0N +3,URո n~̟`Yb}1Y p#1XG[!L +J]X +KV0X)V-?~7):E+',Bpׂ +sSRWSѝ`9 :]Gj>/Բ qIQѼ{sV(gM [Zh?2Y^ *Zr>/XObject<<>>>>>>endobj +1620 0 obj<>stream +xWmSF_uajf7lN2%`CN?TpNSNOݓ@t2aO>k iB.q;l4i?qN}pLLs!0e#d"w2Dj,R xʾS2K#<3\M+ԛ]=A`9EXq}`IcfO>Dd7rtzU_qf8yi#cB$"= $@(wp#e:4.')c#zNyD)fC-3s/@08ere"ˤΙ WusLNrEdqnSY@(VwH@ o(fI߿wl^` Z]SD(KA$(AM\V44PDp /а~iEbMFh8T޵ͮ]=e0F@X rV7nm=Sxa:%U"5풗&L09 I |8F E̱X Is/YXgpxikRX :'%K+) 2B:͋ X(" +H07ujKBj:֊ռuv)j67y'9TJ$Јj-\${,WW[.Er|mVx vaeBxGO.*CfG`2E1޽w2-dkIpm`i9%N+ +gj|#"׋Ϟba?LX3ShܰGΘPBsXp8lT-u̔穪68h8<sqf +&24K:/##xR@D + +T'b +߾mi/4C;*wzq$&~n07nOx*()vIRІeG ~rs?I ?? `Vp`O[zaxF0mNBt!jϞz%|o8E5|&I~mn鞴p[ ZL+TrQͱendstream +endobj +1621 0 obj<>/XObject<<>>>>>>endobj +1622 0 obj<>stream +xUmS1ίbgЙr '2S &Adj{7zvMgsWM:.i@=jاBR>c#]b x ݷˣO_k;(ώex|^fýxZrND?q?ř+ 7:myán=;G/='%pe l9!a(E. D!B 0H1)#1̤wp! +% 8΍)3ay!l6Ao{-KS*& })FQ'h9 aS^"Ԛ9U +-;{\LvRN:q'NAl\ĶrT딖66u$3|Rȅ/ EEqgQ=犎:Ēߪm&IiA`T b$G^i3Љ\# [YLS̭AݲzCo:SLjrpĄD#դQըذֽjmax0LfjhS6ADߴnW6u-9PŌ %twDT'v)%$mU.xh@hCqz.g:q7Vendstream +endobj +1623 0 obj<>/XObject<<>>>>/Annots 873 0 R>>endobj +1624 0 obj<>stream +xXoFb/qdYԉsUNZ.=\uwiE%%mAbSo޼揳1]Ϙn't=#]]eWϧgsicC(I׭5`B2HSnEWUXyi8%]# jKh f.|m[6YbSC'۸6AGݜzXt3kL:&4]N\fsRsKؿbV%z,i׆0XZ/)b5#o³#(LHrs9bJPkMZ87y>d*Hq(J[QǍyN=^e ϯ(Ր9agKoӦ5|t O{2^5K|m+E& 09$GY~Rwg|d2}wA1sk{ Xt \iu%0 V^`.dÚH/b@شݭ&\f[ #ˍ!txWzA׾ 9x|S! +}!u^I<Խf^wL;0gnOendstream +endobj +1625 0 obj<>/XObject<<>>>>>>endobj +1626 0 obj<>stream +xXr6}W5[6uvޜ;3vITHHBL +ZtvDO>_Gcߘ'4QZ}&tvq'_jZӳQ2tz+~ oh< +Af4F#+ڻ2G +YSh*z'%=yGnc/_wv&)Y4aNzm|ReO?Ft:&$1l&{:cמV+dRϧՖR}ؓC*tiX7mS}ҋG.M7Ϊ<3&K +F5~#Nt1x4w̒3>w6ץC[tO-uI+W,y˭xI}B=}Jr REr~&,V.3҆D߆株/͍{Z/@Ӑ01v.[+DY+ñR`ka)PI~kaU1_ dCeU(%jjyyq [4*P-R%Q]8z|IIfn~~FOa<Ƃߘ\(`o0w塷lH]u41~-*/ +CKg;RH?\eLX~=wfƦy61в5kwg@&?\h^͝"4pg"nj0fxzq4ŀ2OTiqRp3'^?X*Y#L(Š[D8`f/+a#w*]lV `y4;J^<ӥ+lBmԋ29 $%Τ0rBo\o +p=V[Qx ͺ>* SrVG[l͟`TUÓI;J.ΰ =aE'*K00>(lt| B/j{FE vc^4==}?n\qwkCn5²ɪl09Щ ء9mlllAABN(DUmbav,Ѫ*bDRxYpMjWKq*2?%\Q>4VӄZo5^iH=cVhq0ؙb8=2E$!46gVזrJ[40 ڊ=.# HԜ9_[!ى@ ͔g +B{bdbX +fn8:A FV0i84]HֵJU)7,®Nc6(*T>C(K+UHa(aryX0w}B|a%k fY!::"-اnYq銉"pk(KY9 ;vL96J۴%0@;h2/r|3a',4YQ3>/*ji%WuYWqzRiڗX5d +%?]K34@ņAFH41eE1MT'ivEu(=}uiŕ|a47Ak@8'ޤQبEVBVKOA]k+2XH++*Pd;OW.l0*x"4%C(N{vFf]׮ ]L|tu$6._bf7`^6r ( endstream +endobj +1627 0 obj<>/XObject<>>>>>endobj +1628 0 obj<>stream +xXNJ}+Rbr>T%ВJLI23cBן\ +!ok_G}OSh@>4͏~QOe;Gc:?Et>nztz=~sq>iB04>.vTZG gG'ӟG=acՙfڽtDMMI5\e:!>szdzeYDwƅc6&}'MNaY݄jwCwl?4E]_&Oʋ!@VR>6M[2z\h:?{Cfw $.98{{k]ѪK&㍴;bt> ??L Ҁiendstream +endobj +1629 0 obj<>/XObject<<>>>>>>endobj +1630 0 obj<>stream +xWn8}W .(8in\t -Q6[TI*~ %QEıȹ9sf`JLtF I6$;)ƯTʃYv:nyp MOiYlJ˂`2e>f.Ukct箵kОn\erwؘW4[ʨ?@TXMBsSZ-P1v )n%Pmȕru-^|]tM4rdǴ\׮0?XJc*׹deځ Na<ʶlTd7cuHF.|4ۑ G&xnW?0a= K}-sNQPI9F¥ڨ@&}ll#6$JMpg{j0C;`$ݫ9<"oM̐>H({Er(zh6:R0(Zٜ|r†82ŹԃZ5P ms)Ŏ" տ@b!{l1s,jqH'o{=C ]a"7J{gu{au[o"4wݤ +?[\iS⸁7I;+u{B$iOp!8beuU&= ńR;@|Kn\`u㢛>#8q*H%Om7(w-B{'^dAsYW]-$-.w' K%`0GP^lQ:o׽ GxF8B,;+[ 8 Lvj78Q?h Vo{ x!LхkĻdWdZ^l4 +晓y: l~}}mbdEfm=/ ̱Uvܙ6*Fܣ*Rξ2g4M6/loXJr:e]NM3 ;` qKT=R]4ZFf#{%w=g *8v-$ɮ ygJ\'IDL屵7 Z +E,{wd(~Иz (3q_ܻʘbiLw (;x|;|jz1洇6.I N/ Vu^V+E7/ OOvb +ꇎ-\/LzO!6h.X$on8"vI) (ԫ;aScw"{?, cMf@F2JCv5LvN~ jsZե)8j }[wuϺ k3s*wy$AIWO'ovu/aY8==a?,8E`endstream +endobj +1631 0 obj<>/XObject<<>>>>>>endobj +1632 0 obj<>stream +xVr8+(WIHzI6E-%@)گ!EӖe[Ӄb+yBeq4&4]w|Wwi]l:'i y4ѓK&/zl&S慾eWpS#y4Cz|Vk{#byK4<*قSl8upZeJ!yIpJPpTΩB ͍ 5Jfє/=H+9n rglkw'3Iǻu^ZҳQ }Q݃1w쁀j0+`386]WqD>kiyd{UHʑ2{2`V. <ҷ'9!9n`/jg2DYj%r'd%q`'|8$b@yGVm&`g'2`W^h<9Q̐NG[ 0/[(Xgꥮ.%4X4}e"UZm(N)/d'a?T$}5d]vKm(O/B@3K 耈H-ݵPx-AIq<dVw!@*ųlU#23&VQzD?0Ͳ딸WyL hPQQ#]3LJVڏ=}G=$jJhG + rX +L';88űe֛YWo$$ +jFz!$1,螋Dn!g\:`iu)[|vXD:]*+v$08j-Nإ2+I#R-s6ZNd ,5D"d=a^ś1 ,mވ07g  ;ʉ0ue$aO͒e +Eݽk=I9fK~YƖfYvS <0s?I 4\5l离֚V +mwYplA)qjFKE"6/r[v;EHN'L&s A DlD`Utc[dGg^Obñh +mc6Ѽ*Q0evVӽ:%cM>.P<Żk1!h|3a%>_.Jl^Ba4Ṇ+8(=ȦE4IC8q뫿;^endstream +endobj +1633 0 obj<>/XObject<>>>>>endobj +1634 0 obj<>stream +xWo6V ز%;3`v]6^ں؀z(hH*Ru)ʮbR%ޯw1/B_Hs.=adؗW᜞+z{1 &4σ+--)u/p>p> f}1~qMф)қ/NyL$<ۉȚe@ϥ~0ZY.V^4O[/yMgq `N"+｡vg|f>7SOX޳}uJzw<.w<4Fdȴ1.e7 g$zcdQqW|HmL#TatXfEaQKP$GB_ӏ Mr 0 hr093\fqn"}w(f 54ƨrol}d؅xvhdA :%;m%'6GwDِ$lEUX6|7k87>J)r5$i/BaKqaEt+DVq[yrD(]"UYrV?axյf/e kΛ+a~<~vU@@ks(j(⻇21bW}`ٶ-t +o̮n=VIIb;褎WKOܤpO78v(egˀ٣Lz(PKs~ý +\bp4YUvv=&oNM˜ֱZdz+BJ;#_ɄtڋC8.,c~:}8_5nABk_9޷z%G+\'ˈwY.8ү닷E Cendstream +endobj +1635 0 obj<>/XObject<<>>>>>>endobj +1636 0 obj<>stream +xWkoF_P$ZmE.y4hIamQʼn 'zm6D䩪L9mز?eG=yF*{NC\ȽSN:hz*wykI1;$ 9A +3Ja%c), +R>V^*7)u);s<=07r֗uw_[w#lws}$#i59z)EHYVm4 +U=J ^in0bܠn~ $\鰵6pki(@a#q , +{\k*ۀ.,-쁨XH0am4xW%"SCTZ ۹%inBWne$ʿ6]#ؠpk m}_lP^WWv t />3ATUh$C@SRBH5k¨=4D*72P7Y(3Ȟjm#,E +2dHq@W%#'׭3Sx[\!I ft#*kvD(6xrg z*]G|C,ご!Y }@Z-(ў2_`H8JVD4 ߕ 3V U!Ā= f ჸ2>Hd]@y3&и4qٞ!CZPocʼLᡈD5m;ك^kI^M!I\Dq[7%*{g|r G〪a +&/T[R2~ |uKfnNz2$>8,'-zhPm dZy +5 #ק-=Lvy~lGZ/e7tZCPJyoKOXd %͓׋5`:"/_: 跣endstream +endobj +1637 0 obj<>/XObject<<>>>>>>endobj +1638 0 obj<>stream xX]sF|ׯK*")&uJXkXf =@P|WNʔ t꯳MgFs\PVM8%7tusso$/.>]lF5^Y\2'<>2;$[IO3]ЃP)ӥ{0vWN!MJXI>RU>fA,)Mf229LIUQ7#~܊r%JsDVl4/05ʨxp#J;rQFjh\K[qHV)j'!|\q˭6<~TEd"ۢBg(N1ksG-bsI hMZ;P9꧚JAxD_E>YqJ$RYkOXZ7fz5~8Hfۻ7z PUhd#]/&u_\P0?]-vڸ*yn`Bt$:}`vx5? = podM 0Pxȍ=׹ %UkY1=t?͇YZR5*ǿ1qۢ:lܣgRLUlOFT*]YRpӴU{2jeMHq|?y)Tfp%gL˞) e~tб4VA yl*\VrPCצ 1ڻ$!r5V,U)G@$ꌪlɀ8_m*{wNd M>\BU@Y7ےK}糄]dxRz߅>,?o~w<~L4o &&iKWeAv~gx͜p ,Bo0 d$Uoѥa+D˘ S0!%ĉ9uzJ"˯t-1/K/Zl~l9LWR`q* 'L^cڇ(/y[p{BJGݲ7)۪% xKꃏxa-B%g|NC"Cō' b|{ڪԄ$ݭ=&(.8;<"~c_g^x:DrCDxy%X)Œ T3VXt0 7PbcGoŭ<=Z>^lr" _d&ɂQBpEU6ϢA\5*Oz_u6p쉝BَM [ f'28WGtD',:֊6hu&} VC˫tnAc&nKnie'yՠЃ ,10%?%AEypx1ʓ+h - x ݺ!Q /SMԋOo̮Y2ǟ~Pú9tzqk;GHCL?ph;h];x%c7rvJ{wzkt3efH.) $&poqF!{]ygLu>/XObject<>>>>>endobj -1898 0 obj<>stream +1639 0 obj<>/XObject<>>>>>endobj +1640 0 obj<>stream xW]oH}ﯸK)/д-d MIbj{gLȿsgl'1 -TH{9z|:tBq~0F41o%iqs/psoJk'7}9w?;O{\)\ dzNaBHr40> Wda -TE?݇c*+H3I&AQ37G}H+M9KUq৻qܫS&G"ӊJ #Zfǽ#F0Ր+)SeZ,)-J|R#Uj~L{-jQgY/v[c)6:ETY"+ c?KJKҩ+tpj(O+COɋ^5Q oNmwiw-A+#fdYtO]|nLL`VYۤz΅WzHBZf?KlT9^R |42QC !5Zf ƊHd  bPћBOQS6wFkd[!N'q]U[B UM(ymdN - P=Bf9 L"f~Ee 0,xckdˉd.J Tqf+Y2]7^uD)Xr^}Rg"ۑpOw{2uc Ee gd"]q<-}-" ;(Н+mثl`X;:п^H -ĮVe\1/N -ոTb,^ e KtإVճ6`c:?*_ct)ݪ%.˧ݾA jSMcxxmA`rN|neŐg6`L^FVtn A{vBM*;Ob^E1A!'?4w A 6: -"NO_\Sm xx -t$y(aГ>;˕(\a6J=C sE e$nu@K<`R< -EĘْLn-9`D5 lB!].’y"52j^8v}w3} FQR)9הo`^R%5'So:9c -VY[z.O.ʞΊ 4c$qqkjaM W?|qoPZ 6uBA^V8yjgWM&GZs9kO=8mfdV{T ~*؜އ';{:l[^ʮLޞCX9Wc+hen!wP2,5% 4[oqHh0gPX\Zab"~*g7}87}74>/XObject<<>>>>>>endobj -1900 0 obj<>stream + P=Bf9 L"f~Ee 0,xckdˉd.J Tqf+Y2]7^uD)Xr^}Rg"ۑpOw{2uc Ee gd"]q<-}-" ;(Н+mثl`XO= SO;灀酴!@jqKZĪ^J? %Q[4Ow]*kU=kcY 63k5KҭZ肽|-`6OiL4( +&go_v +*Z YyxnemduH7th'4ؤRS$^O_O~Ks^``*bt<Ơ0zAM2xgxn=C*#\b)Ʌgs3T +;:\ĐxI[,XMb\A 4$=V,ɣ P4|A-Zaqڒ F>HZ̶)5q.,.MP#C<_0cNw7mUJ!Bk3yMܟ&l._Rs23fo n$rѨ @;^A/@wNYt{saW&@`Sh+toÿت휷1X*ܮF {vd2qT53vk.?jFf%GLe맂}x%Zn >s=B`X6a r!YRS b/PAoV޸ +۞s +Q5uX|.6h*W|xgswSMÓfзT RБRal>bv0oo0sm.A.e DGlNPeT(r,T&w%W;;L4V|9u\6E&Ruj3aF +J>W`!3OrX˿o!i8qE`լ0%+rJ >pŵ7lzMF?|af3r S:>]؟,ɻ_` +>Kendstream +endobj +1641 0 obj<>/XObject<<>>>>>>endobj +1642 0 obj<>stream xW]OH}W\T"NoYU.q]=N3gLȿc;/ծHUUs9w~?N(^ϧl_H݁9/޴}p#} bϼAߧl'3 "~cL{]R(Җ.tS$LDJ\H>ĞV*dʞR4ݓV$Ey|?Sz8>DIj;,Su]t~]EZUzӂLٍܦ]{r-leG߾kEbC T.,QJ.Ro]NULT6=r2G勉 ܕzs>e F>:-FǖB$&VFcFiD"ϥ(Ni -6ahpe%:җ֢"D1TP`s_qA 1Ȳa!2"_5KLk\RחFLq^ɫ?|or# 2ko[Etz~\LBK(`5&14[$x b{0t9 Dȣm UwN!ڡqQ|3j'omoua@ZQDΫ/0Úlu1@W.2E2:<%ϩB]v.>겒f>JjL2Bx"cǦjߴ㌜]fV5o`v,_./[_oc_c==Bzs*\uw'eQ,<}p3d+@zN\%%'zxGErNu@7@F_Q?^ᇺ,m?B 9z+\wW'6 -uF ;ޅԛ7O~EzFHlw P-ea]yB+05oMaP{WjJ0Mz{h6搓7o:Ȼ2-TY?~>/XObject<>>>>>endobj -1902 0 obj<>stream -xWkOJί%TJL^MBQhI/ZۛxuwפNL*0zgΜ:P?i4(;Ei0hhO\ӗ~Чd hD8.\~uT$[7}q>Yd2 ^{-ΔցpJ6QKv??/#qŜ'&g^r猡s:߷ivGomHt{CEIo拃U:\S!\%P{(X8RPxVEUNl%"_hB~~x"*j,t=U>}=3"4>Qk[b띣-@{Y08)% -8<jtRS/:ikOf"B8$n M eY.ӘtXA9sn*c%UD$v]w+S6RBP)JX[ {'HD@# Bw[,u(elKr`7y=pM7y"fkHO*+b@0oD}P0|9~^ -Kk!O"RY {R8ozi"jJƋ4K3DtWLe#HS+k5 <.cp?@،ބ -͝ZnL 7ua[GAڠy] ܾGJuJ4P915#W:4g`,}}0t}绳?nN>]^,wӯQV/bb8+JX,j uIu 6Cj.&WscyǰC^pŞ -,GsMKTy <ִ{xx %pӼ݂J]oxu^*wfYVGJRtFxGWe=sFddà{<55W#xXhy[i,ߠWyLxK8mT+qi@ۻyU?-B?WX5dBtw*0.wʠ`ORiݽX' 2:.ۨ#Pone`\Ƶ j1CjԼR팋.[}njznQ:ft UGl}PMS0Y[E" -|EŞsxű?dvpzPqa¹Wz ׼kЍrxxn$#m'`?p._Tendstream -endobj -1903 0 obj<>/XObject<>>>>>endobj -1904 0 obj<>stream +6ahpe%:җ֢"D1TP`s_qA 1Ȳa!2"_5KLk\RחFLq^ɫ?|or# 2ko[Etz~\LBK(`5&14[$x b{0t9 Dȣm UwN!ڡqQ|3j'omoua@ZQDΫ/0Úlu1@W.2E2:<%ϩB]v.>겒f>JjL2Bx"cǦjߴ㌜]fV5o`v,_./[_oc_c==Bzs*\uw'eQ,<}p3d+@zN\%%'zxGErNu@7@F_Q?^ᇺ,m?B 9z+\wW'6 +uF ;ޅԛ7O~EzFHlw P-ea]yB+05oMaP{WjJ0Mz{h6搓7o:Ȼ2-TY?~>/XObject<>>>>>endobj +1644 0 obj<>stream +xWkoJ_1R 0Hyܢ4zJH^6]C%ꕪ(cq̙3O1/L<É7qK<= ӥ/G}O h4ǯr7yvqqtz=+D4Nh<O>I8T U֥wGH珽gեBet3ktH%ֱ0a:ӼtdcQ!Z&+JD nDo4Oۃ+Ȣ밎ԜZ U]ʥ.(rBєVȢ}: ѡ kF"-4I6qL.֣pBokB#7Z]I3^.ճ4[Nv>\%u ˅_>I# +eUBMWdϴELW$8^˰5eaADX"V9my8,#QŜ'^r炡]:;hvG'omH4ݢ3P*Ln(6\ɇwu~X.Lru RE'qUb4!??~U5AcB: b +܂߮7-q!@x\0Ƶ-JWkj= +v -O҆$ԋjnų|YFI(7i+6i$euD +ʱgTJ\ۋIE(6u=UxU +WJ5XKk#7᜻7x҈$4:{*͵A'^wC]fh ^&-AmBleM7ekBC1r F8D}Q0z|~o\eQ@D*6IYma +]U.dXeNwY B+͆ +g(AzSYm|uyH1f?(&,LEP nfjcb 0'<,4C#kM=7_0p-VCTaЌVEsYO u0O'uJ O7W|8j_/ϿVFze}Ei WrYKgxK4]3nAmWw15Q;,7MQy k:GYy+ zhyдBcMk\C:٢a 7[,-u\Groekq*Agxw4 +:Wan=LNQ#uP+$$0(A")ee ,=` -oh'͐[v4O1o õj%nв34X|wǷE +KLH.!X~% C)4ɱC idRpk+.*`b[@-qm==7|(SSqa'Y+6 VS^ '-JG63-y +>F>+]bEz8Cި ɟ:,&){y7qoݺO.LN~w#yls4z|]-Tendstream +endobj +1645 0 obj<>/XObject<>>>>>endobj +1646 0 obj<>stream xWnF}W R(QuCŖ۠ 6&w.iI3KR&(45;3g,?}(H~?[~ So?v?WtcYhi8㹏?={~0yyvܿO<iQ{>&WhBːpףepE2 T-%1eR&RP2(LՅIY ..%"(W= YGE.]cV9:NM-.ҡZ_^oѥ))bcB J+QIɒHh _d^Gƹ)JÛx눬J3q]/VlI>d I5"# E*h+4BN{ -9 Bc.- q؈ K!QQJNڥҽb$\Hj0Œ {CQPv4|قQ_xd:ZXe/WI:`ŵi 5T•V?H\.2UiʈWtS%Iq@@!]kH|uP2LjB$AHWca5-4 el =`L{d]}3^R 8 9<&V)=}M[E›nOr,85SA30v3u`#Ի53V1e ~3MlЌ)`/?=X8|rTS$Z/@<2>bЎ{v)Y%fKk5YR;t -ي5LǶ S/Xb^d+_`#bi_ل5X-|,4uUkY:T4i -.W3 =')=lw90PGWоꂕ]UL_zI(5$EUpT-_:p5 -{n{ OB&x(\.`&t3MyNn ˂E -blES {n ? {yri;q75W\pwvow׳oս$ϫ՝Wn^xt!&|}|C><וpDwW̸ߙK7_9bFuqo8My͗g=[endstream -endobj -1905 0 obj<>/XObject<<>>>>>>endobj -1906 0 obj<>stream -xX]OH}WT"&_$/ҥZ`ZRe1vq~Jn^2rhWa"oYˍg:G``-fc|T$ OZhFiVҩQ:UyVwC$W]bv}> ;MX gQ)>A1.e) -(U& Δͣc)R=D$q*+ T6 `k8 iqs -Kk0kvqw SBCH?mB$ʹx̆65UNQ*+ iV"ʒ ^ug ! r -<TMx8 ^ť}͂ k&Θ,#v:G׺̳7$a c/ddכViʅcWZՆy RȎݐe6͋˅mpF99 -w{|(f kUMMHZ'Z^UYܢ_Xq SU*{>?,|gY;_(?L]Ju}P+^]o/u850u;Y7[ĵAo*M/ijY;N5IR Hɵj[M݁]JSDe}s=849>/XObject<<>>>>>>endobj -1908 0 obj<>stream -xW[OJ~W*!qZ)* Ĵd -&qfv}!.. 9ܿfso]ӽ޻1 /{|~g0Fep||%5%u3̀喺z"V}esMG3FcY$ -f2 eKlo >c&`TV`' (-$ 0 fd3"?< fE›&SoVXd֡],Q$Oʼn'K9lYqypOX$[ 5be3ͣ֟|ꢺfdry;_̼ X|_bL ơ -SRLRaA$bE,9?p)o7<ᚗ9aᚿm>"&&睕o ב|C*wzе%ʝ!1q'r,^NzwNV)oFr{=*iVG\bYL'_*?蛭:aJ#CJ4O7>/XObject<>>>>>endobj -1910 0 obj<>stream -xXRH}+ -7區IR 粵J=q4#FTm*ƞ>}tw:u78iGmQGxO))N#NtL'| CcvtثeNh/6=<]HExhneoMSI3e}0NZ6'Mǰ"7kpl~Ίҕ,3e( -NUi,gb|0)Fp? -f5|vq~ -!q;wZ ' wL\'*]![E1s50A6a{e<'07s~4~}="3nvCTTxBƁbJb; 8 /vwۏ[p)ϪRѵ(h1!G -΅`2[ -o5U fa a!r٨H !!XáPd*y'`)t(>O#$prnMT )*K е&J,Ҁם47>| -yi*%W@?sG -1tLD$k@h$#Y My]2u./V D5B*UE -eE91|ut @Rhƴy0z5H.t5w!0ݝ`A+}za&BisA]e-^KPm4xr¦/)i0:>)8 %b # W5TF+L)L83~cxRR.$支9%䊇„EQ1NbK!/OFmB;ME1@BuеXVXqyt(H;89h|y&د7bf;^we2nfp3 m⥦7]dE]*ŧ!%k>z㱂Ib P"hϭmksBI4b Pn#pOD[EMU0Rajqn~ʭn|jR0]a]%k! 7֣mQx|/nopW5cNr+\Vq,Imϫ<8qݔO8a0wgW"_bɦ`:jy"!CGGb8y=dendstream -endobj -1911 0 obj<>/XObject<<>>>>>>endobj -1912 0 obj<>stream +9 Bc.- q؈ K!QQJNڥҽb$\Hj0'kF[鸻Zx?,{}&4F\ ?B+ F?B͡LEʬC6XVDqZA`>*pd(E]"GAiX(A|6>&#eB4F"{Si[xSC~f!?2Q 8fo.!h?~CBLՅ [ӒNSQvУ vZ1;gp7N հКc\`23؇ڴY$$wʂS<]= c7[Q F;2Y- M[?c\?tQ͈ܣs ̧(G5Orq#3#0H +xw}m1UkZ*UI/X#tlk0U%E"6"MXgrK]w\ /!]PK5M-/! r!1p9z0zңvp 3Xqlx9(.Xޕk^?4URIRTQ 7Ax{ m\>熰w$tmҬ,5o`l@7n?&axM,X VV49zk jh'wC wSs{w>jvp=]~ZKHbZݙ8i}Gbmׇ7T3s]) Gtw6'ja5xIM>zjpwJOWݤ.No2?Ìtc% /fT9l/]|y_[ +endstream +endobj +1647 0 obj<>/XObject<<>>>>>>endobj +1648 0 obj<>stream +xX]OH}WT"&_ЗUJӥZ]0[d28vq4+%GxrN~Lx#?'㇮(k),0pq.b +(xS6wl, E -eaf8! +9sZ:=g|?Dp׷7˫/YDoRMRcTr]Re*L<:kj_(@HdIaAbA0X: I[iŗ$gHCeST] Lƽ-L E! 4~*&B3JT;E\ +RDZ"% +TZ(K2x9;ץB26' (7ȁ+<jaMb>"'eiS Ȥ:3Jo$ap[HK:z\k%_Hm_q1[UrD h"a Po$ Զʘqy"zsۧ\'\o(2SOW& '\LJ4AҺ7mrSDl1:1kKjl4I,\ TӅ7Es8wjfvl1na@᠔6; mHk__N6~gtLx6lMqWaxAs;:]a;+:D;_U@N_s87;P/oh{b,>TMx8 ^̿vNN5Fgt#kҀVY\бQ\HlZr:Vyah+-T-0c`7F}n6ss ('Gnt{x6c̵>!{ @+] ۫*+[t +nv17rrBe/a,kK)jū˴p5%Rq0V5`v;< Qx6kɹF"Iɟ ?3VmQ|˰;Ki*HV0oG&'͙ i>/XObject<<>>>>>>endobj +1650 0 obj<>stream +xWmOHίUBJ%&!}H$pӪ%؛kB|ɱwg?ÿ>xAz;p1~O z=8lX wZ@XbmL~Qi!lmߗ6:=wTw0rh3]8 VlZ,i!悥/ IJ C3 0Y29A Ni΅Їk|pp=l:fuh0KSqiR[;~]'?˥ʥ}=IĚ~Yr)ow<9cAn ?!'< QD0ŏLف액ڪy +Bf" +(er ؆|DHt0MQJ2 +Mtws)裪_6@a,xX *’Rƫ*ʴD,[s〙džxn4knE;pCwBkR&F dO Hdn+'3B91nBЄ~ԌxGT7%)ud{y T&{hVf^bpX*m}1-&ߴ\Ae &kZc%#9S(3SŵFk.C }?rF-{ BM0Y4Hi 2-R0 "Q GC$r>wgQciA%-TZb7JԒE,(WTSs6 +c-)*^qPt\T g^ dE +; Br-Rbȶ +!=*!z$3hϮ_YWldw=LiVyalf~krՃ6-r{2gjP-ϸ"l],8{.ް]-di94hʳMs t rg'Zerlɯ#|ZZr7r'GD]w3_5&QߋT 7 %2ͅm2w_X e.//`BE;͎o鍏a4:_,K}'LCid[ +tO{vcgGۏO3:gm;_<*endstream +endobj +1651 0 obj<>/XObject<>>>>>endobj +1652 0 obj<>stream +xXrH}WKP+ŹjɅ\[XhF1==%@Z cOt>};joPﴣ6 K#⧔|uE':Ó>!]hza;:|xxM'4Nrp vu.f"K;Z+;dr[TeL&gYF,y9ӦVhI1,g3_{YQZEU~3|߀vx͐d.| u^GՈ>"KCv[oЧΥFvZ]ur-ѹaB)- UFR"SQeKZUܧie)FBh댌R*3҅/ンp yeZ82lEisR,W~plB8cT )\Nt4'Δ,`du#Ɲ>vBnh)Kы$W2VR2pflàI.clWy9!xgA:Sn_e&{oo䥃&Qt i. DQȥuJc9˴IM1EjUWp.4#!*UxԯZ]d5 -  FEjtǚ]&P}ϑȧСTL> 5Q%HF f,@bS(UFWhӏd=P44MR:纘hXճ7 7ȯC2 T-037+U8ĄQIvӂ4 T"u?h܅[Sww酙})9Kwu&/T#{a;`,[@ѷ- +`>?3p)NI(-Ke0e0Aݦ0*]aJaj%ەr$1|%W~ι. &Wq&M4fLKŢ4OuS~xD S +'7W*.o\dRv,G=vspy\7eg{x?z=.aS>[,ٴ,ZGm~7Oq48o(hw.;=eendstream +endobj +1653 0 obj<>/XObject<<>>>>>>endobj +1654 0 obj<>stream xWmOHί!UG}H!)HkO$[t&3~#1u.I;3<3%]:qdlh4c/yh/ >bc};aA/+ TZ2idH4X脺^/-%{(iAn(4 SԑȜIS %Bh^+\d#UV/:tN=DVVE㓈3ق"-Յp6͝?ތo1vhs-ZE WC˵rK^ 3vCWIeڦݘƴZ vLYU.[GXv%j5ě[] ve MU2[԰ &buEDKc Ivn4\?MUzۀi*nV$u6}'YLmqEӭ Yȋ-̴m|?Z+GA4[dˆEk,$^SCB< K'"%miR^2U1JWwPC&Nt0\t/ÕCyBlƢsخCIΰ~JW6Q F%kDŸ75s&SRh\IUDLI,fHF،A9)?}QZF'RGx)Gk&7384evkO\ ?#6 sU7͍%XPAM &\HrD0 =[1zzG O~ wl |H,ڪ\|5~ޢ-%1EV]5^`5hunFNr`9|4 "ee7L {~j٧/ |W | ?uNK$ζ-NRKU u5R'ȑ2 KNj"y(*TA퀶ٽ-eRޕiL-Gj^\GK>tdiQk TJMul_+=i,O7I3dA.uNڥDZW$_Ne}Su((UUJ3vJ!IKG-o{tyL.ؠw>|\h[z4zmWLVٞ -%%3ei2 ,m+ <ӣJ _-˿_^ߜW!J?inX֤UBLfApYP -|c_rK'K@1zlnYYi;;W 0057KVtO;'v*'Nh g{+endstream -endobj -1913 0 obj<>/XObject<<>>>>>>endobj -1914 0 obj<>stream -x5Ak1h$MQB@{]V#Ne$Qh4 . -54+k[<Dm \…󳗄i#"f?01ЇJ1^;sm(bvX+|&%ҕ1*s#6>O7(!r胊em{exFendstream -endobj -1915 0 obj<>/XObject<<>>>>>>endobj -1916 0 obj<>stream -xWMs6WÑޜؙfmN.@$H!킔d*L'ɌB巳9gN Z(kfYMtus -y1}5]śWbF>V7 gxMUfJ,~Qw!g]h i<\ u>yTF].)tm| wZkڔ֕ VCrRewLԁil L3zqrLSzqH]C槁e6mͳ;uߑ@nۨsRBdmT6h -rC 7ץ% L#w/@*d35ݠtxӺAdɧ$ -OӳA=_h+)~q%4q ͯ{.,WhNCoPJ>=5h鋱2ﯮk5ΛH7mvYd3WDSm##Q1 1XWSsP[rZR<&a]X<7U׻ qU*^Z„Ve.]Xp)-RZS yWs]YÓU=P D#{Րb -dWD] Q{OFÀ0U'Thğu3+usRay 5]"!>F,)s4x`>WhP5@Ǒt=[Unʆ]~8RAR}X^sSfpd6/zE -ML[G2#=OYA8 kY,H mѸXkc [k4@VcQ ȊjIa~4jGM%kIe()+Hz e뻊tta2f#ƙj@:@WWĜ8)=: K 8ʆψ(0УA\nEz<7ge0B=DZ1ł29}& 8 -Zp -0V=%Y)4!UZ% 0>XrF_v{8j'N0v6>BY4rq1\ hqސhajBo-"j`BE/h)\b'Ieܥ?@h-U}w 9͂kPS[Qd*/G :a7X^}ۏ#٭2>rs1],.ThL2HH1Tk^&m05эsQdbx34/=Ľ>hV/Bewt9Ԇ+􉜮ީR[w K.+b}[؀.%;E,H$zōqaC%G/46Yi,cdX%QF}.yw栰|7ScT/zbra|9[uY6RNuj<D >ϧO;l>[~]n |⾜_gOendstream -endobj -1917 0 obj<>/XObject<<>>>>>>endobj -1918 0 obj<>stream -xWmO9ίqh%歐}AC+Rݝ/ήC{4{UZA֞24'4=> Gt8OkZɃl2<{d>N/^_+$9㗒`4Er-,fŵoC4>Zjf49"t>_Ɩnx)R6Q R8֦ pٕk. 3D5hTVi?#82Jō>L$BVRbݕXWOZФԲ%h嶟ޒ;Ww(&nqZܨ~:S: ܼ;(]F6bgye/wmKK\vdۖ)*56Ytgr+A'R/]W.{YM -[SJx Ʋ EYc[ݽ>NyZFU)jU/Y`f.AIͤxT!1L@ 'oQlN6+a!0Y$y#.40+S7ZР$ى5,5;nL܊C! 6tXh≂(Vmm`uCrrf$wPM]3&G̸!%LqXռ+5-x`C -j-Xґ0z9}5'鴖UK&7I&rgg{eXT-@I fߪ@z)e3@ԝ藔Jb7=`<'َx!}ȶ͎} 7#0@[RFXʊ\iyXЕ0 -RvmpAGjO!{05# V}jֆ"rc~4(M*˙^?J -V0`[Oႎ8$8kMVAȚ@IJW`.]T<A[))?hjrăNhH ]b"N1)px+5c|86B8QO29\rގ M+L=2\H`e~ݵ;^bw윙i `@4d%:n>W`۠ l⡶;@oZ=+V>oݲq_Y)Z&E1>#L6jw뢕O)o+S(B* i ؝es%xzx*NBz)SPM+'DL]a+05b(酜C|֐h%ك4K^.^|~.ԏ-e7_lH"5&vx>PRETagU59hdЯxn #ĪRwϜf]՝rN'|š<+p(;d% 9g ?r~\.WwP KqYnwOD ӎ W 8[_8w]26Zc!ԈwbߨNDes|/(bkVﶳw2sO?2endstream -endobj -1919 0 obj<>/XObject<>>>>>endobj -1920 0 obj<>stream -xV]oH}Wծd* %thҮm! Jagơ=w|ۇm q9?J:mg hrFҪ%q^$PSWw[şO8iu>(I([!xrMYAH7Pw+' z@FWey.]UuAה E?H8ݐ{yk"KR9snm$Ł -(՚Gd;'CԞ\UpVOo[)q)ΑJ*-J(?_.m.U%gKRVEL3ܑWi2֗Lm-$˪.yVFok -4h!͋4q3#h)zPb+m0(|>V{]y)񁕕E + lQLz¤-v#,8AݎvhZsZ XT"9}1y,E9ma9)ZL1a0nῧKua?Irars&{@I 倴8#A%}%fvz+ڷ!DB+p%`?L)I Ǵۥ\$I u)~"f +t [g4]c=PjJD\wFW"i9,=qEʶ21 6̅;$8\Ͽ `+(U ѥz -zezu\R`=8OT[BKgbuxE^Qz˾`'XIpKEo 2fY:#L 76PRzñ  q#ԚP ,aL9VlԽP4l։TFЍÀ:/DI >Z룭 6Q q)+J`0'2ZښE O5MGA+d(yAen{It=f׷v5f0bq!r0[[kaJ‹n0ȔBy \yMli||7>uܬW7RV;Ƀq:H# k!@,55Yg@[R{qa|AOMXHdcW,qM+f2œIk$,FiI9ù~2ƍw2B,weH|hrYK_PZendstream -endobj -1921 0 obj<>/XObject<>>>>>endobj -1922 0 obj<>stream -xW]o8}W\ZF&H0_FJ3*VkL2~ϵ T]P0ν{1h4*U~%4$S2]'Kf#|yuMFh|q)V^֔$}T^YC4Zo|܏vh(ش3~rR˺G"1R%64vljD7FwSb۷(4{4#(B>F\4λNq rVkBϢZ"=[Ϸ;G2t/IPBLTpYCĪ6s!FCzǛZ_J6 ޞ6h,uF`4v9CdtCiWp0?T=&%4'ǔ~RdH_؀t0:mD,ڬ^#}1J(}:k&*.N JynA^/{(=CSx^Jr3㘨G){ 刂z䄰ݕAqqC wI?\i2li/ m{T&M!VoXtߘNzutLza؊gt‹J]״63=a!/N]ʗ-p Z9ϗdm;6Z~ߑhvh4}riAxd׻jqM.xP_t:M?wendstream -endobj -1923 0 obj<>/XObject<>>>>>endobj -1924 0 obj<>stream -xX]o6}ϯ@14j#v -,@zo:Z,6RKKsdJ.(-O2U0M93d|;kZdzq&d2EzJݟZ_jeK$/8V5fRuŮW'M'u!wI-,k - }nJ%Gk9rU_~ܮ>"}3:b -[+!!Gsx/[ '&5c.:eɵUop9m;67t03]pqYjEQu+|jkVVdU]T9| 4PMC]ew/=׹Nso*z#q*QzXIR4b)pӽƪI!_{|[].Y+kzoWMC-)p=^OD0CrRS5BW!w:ƙwsRUj7ud#`p{.G.E.>XCIQIZgDžIE1vԸA4jŲ{>poaˮDU%%i˄f4 -lZ};]W#qԾ'ǫaiE%Ss(SٶؒOKƮ@p -saߚKnv ` 2U]&4i-GK}9*7Bk$k^$Ml̇/nFd/<` 2ϗ>9S~nuXE2 _ -9d,MM[5,1qH86:m a)!H@PZ;(_›gퟀt0΢RZH5 -D|x;s@;h ȑVѶA/dbI07>a`:ZC۹DNɗ0栓b:Ч !^.$,a -.ȣ^‰Jn_$8غN\T+pPDHwwDxd^E e2/L4,&EzWJ0Ѯ {l%#ĸKֻ+Y@*x'|)n|WU걉o "<{P(~>XAv'v=ɽe`6tgTpp RϩRx>j?GXً 9}fQ0ŵy_M.XFT(ľ?q) 簆>jr#=Y:/I`:}&KDpPk: Yj yG7xCkQ T2c?e(/CH[{~g52Y b t3kUg%Qg<t]O7won5_!k@,{N/..'\]hiz ÃyUlNTfu*8矠`rz6'Ogendstream -endobj -1925 0 obj<>/XObject<<>>>>/Annots 1112 0 R>>endobj -1926 0 obj<>stream -xVn6+VKe{KSlk{ PPmqW"UVP1L͛7D4_Dz2sJWHh^{m,k0|I&bAy -"êz]S|ѕ5mdFz/>a2*9 O8JDWjqU$e2LqOKCU!YU1V>ȬҾ sÉ3ȣ(q{' -*$ФW"4$+o)Sseg+}:~ߴiܑ0 W7#|8|c4ùN9c 283!{[ CQxfF9l ީ w[6G̬FQG4|טtqH;Yg. \%eEUۦ.@g-Ol ӗA*af'8[ѩTS7j*06 |ijNmH<љ  *6'`5+ )n-b liƢ@'yUV'yfXw0O|)l"DY-ڊO.AN?5H7bRk̑*`ZG)/D/// O}>pǷCzpe+:Jb_'$H%OnO~AO6o!lfjoE2 ~%K~_枒endstream -endobj -1927 0 obj<>/XObject<<>>>>>>endobj -1928 0 obj<>stream -xVn6}Ẉ%Kv@ҋy)]MQ6w%RKRq=CʗxM7XDs9s挾\4OA%M$۫I6M%;Eu<(l߯ZՈ1]Ъ"]P=!?uZ[V69OgY #(2z4Pm S֛ ~.Ϩ(m6OHE^kAlr=< y*G hh~|wG?^yRBn՗^@r -ӔRyOa7jGt}#Tn}.7LOp,3oOo ;`>ITvv/_6' p* Ox;%uUue`䨲gtplM5(L -"E~c9d:Q=^W*d]?(eY6=kإÆx:IB͡ kD 1myσY2k!u>MdmL'%D0tH"MKcA,QqFc4`D\g5'ef_i-x*+M<݌wC .5X k١ R>5R$y,re2KV$8Edб v 1k='Q#m]lI Uv.+fߗl7%&7iu?''Gendstream -endobj -1929 0 obj<>/XObject<<>>>>/Annots 1117 0 R>>endobj -1930 0 obj<>stream +%%3ei2 ,m+ <ӣJ _-˿_^ߜW!J?inX֤UBLfApYP -|c_rK'K@1zlnYYi;;W 0057KVt:'v*'Nh g{Wendstream +endobj +1655 0 obj<>/XObject<<>>>>>>endobj +1656 0 obj<>stream +x5OK1XIvc + +fSwKOwa`f3TFG&6+Ь/{vlBJ=I5p=a|w (C@̾{}>bcW@b(GN|[@]jJ nYCߎ!9UNύx f1yB VՖ륢*l8xFendstream +endobj +1657 0 obj<>/XObject<<>>>>>>endobj +1658 0 obj<>stream +xWMs6WLX"۽934qX\|HHDC Jֿ)QN${gğ ]OjNYuv9w7f7=?i%/&xڋgo?+_"'ؿēlPuԞ&cd+w2 REl(LԌ&dbzIUKuqEkcŌBܕZkQ1- +WZBEQ0Qښ&h2+|w%]Lʬ8 d]E槁e:]Fӽ:yXw-U9h2*NmVF闺|A ƮYƮI`;M*ܖ>s>剾-Sjv] 6]K@K#EaW>+Pi@34 +1V+?0`]-MaH/X\BHT~&$\w; +ftrF\J/gBP'ס)[u0k Y!y +Gڐs]\BE8Wye`x^CF4> >QVBpe:Ob2[EFNNtPytwKzX~~a@HZ*NόϚj"dW ď\u[#1=HO4~EzĪі% + FQ;8=i{ʫܬ+vA# ,՗V 5e}&zm-zAP-,uK;C9~тZʂB+ٶNkm˛ lM,x\hzYG 4(͑Q +f1+8VgMvԴc-,5`&l Tcڶ"b0bl%̼YJq.9k(Piqy;3G/&hLODz09 aCG :dMfi&[t΢Sq(V!h!1WiLIcRRBR]kSQ$/<}cSN@2fV "ΦFݪ Q/n 5`%YƄksy-[4,XdUhL0CDL(G B:'IHeآ?Aa ꊦ!QˀŐhND'$Vh2^=<*unׇ7O`?dRoK#4c:YY!5(0.c:wbL4Zbk|/8tnx2&=Zda c( VeS^1v8Ԇ[ah9]S%v*R,:t]\bZ찕 ыqaCvАZXfHJ.p栰|7D{ !7,5+ CK"U÷b︒/Ǖt)lX&NdyqўJ>ړsPgWf.,{|kBt&\>!^mpLyowS\h1g & endstream +endobj +1659 0 obj<>/XObject<<>>>>>>endobj +1660 0 obj<>stream +xW]O9}W\B%}VC+R>8=k{HkO Th~sO&4.4[PQGch~uߧ5Ѽki~) cZgt4їTѴm>W+c^+yG"%p_/͜&f8{m;9'UUT&bUlؘ&BkzxhG>s4_Meգ#Z:ӛc[靮ݓ>J<L\5n zf.[\ٞ͠_U D'%stхY"yT!̓z]nM1DRB#xHOsvAcBB]ؿԁ2N-Fjv9>/XObject<>>>>>endobj +1662 0 obj<>stream +xW]o9}WծD*BѤ]Em! *Ě7MmO(~|@GyX5UPlsν44P ]ѐk|⿕ CM)^Ec~uy_ѭo}cm&Rgl©^MaC4OPrb:b'@ zxaWZpRC?CI@65ZY쎕? e%؀ CC"Cu'5(Kߕ'Gpm@mG_Dmȩ)3XcM&Џi V^A`(|DάC->]Kl9m&ial$8o^|fW[a5'w#RR#˩!de9P0D: EfX+Vr̩410Z3(EQa([y=oV  Fye+AVl6@5 + +e*Fk5.?aE~-TgyWa4X-}JI,a˗<%Ţ<<5c5S +u4Tm]E$xh8)p05_,wn<<.q`šl+OR΃fބ⍭O vxbaSZr] uy!fZyȞ.T ˅X/]9R^o=][iЍKE5Q3l {QJBm+:FAL.tйI1(>ͱWpE$ +02C08u9Q? \\9?/WtHWA4aH֤tڇ ?LGԿ{'hr_5(fkηZ endstream +endobj +1663 0 obj<>/XObject<>>>>>endobj +1664 0 obj<>stream +xWn8}W ] 4e;؇-} %"]~!)[v <Ħș9g?r/1M~P~*ȳNdS~9_GKΆohXSE6A7fb<aBKlPE8[[~]L a>NsA”*R#sd+ۨ're~ o5tghԚ#z#UVz|L]SV?%LhI n 1}e%;G` !oiGUJ;$@\n3ɘl ~&'GUH<4 +>Rl0(`JY()¶!(HGh%[ۦ<\ +/1WH`(}1 ™mXV3j ႀ0hroyshpy׎Xl`&9Vj@ u +n +6 eMGe[5b>r|̹ڒ0ֲX +\)*0,|5ԑU5wKjM)Qf|tnE9פ2U#o# -Cƶ%Y#R(ӡZꌏw= +/ +:O*Ph,DNx(Gn&}U>+T +Gh+2Iy#M3`RV>.RD'$展Ia7r)cGY 3J_ +GTQjZG a' `:@^H u3N6ZI +1,j9bWʶFkӨnJs>QƯ 0 ʜ݇qetrcFgZuȐ|c|zxF%-Тad()l]c\Wb`xt+(yQ|w`l1@4ifIƂZ] *M}1%$ җ16DzyLxFl*KۈEcM㩅ҧ-J79Uuyy^@* +zW|&IHnsK!cjR45,r,Ak@/d7?''t/ue\Í; En.%1~ҢM+6dE /@ mh*S趔kݥ73ͻ{pe;6XÐ:*U״6yD|} z s~Cl ܟѱT d۶m$~߁ekvk4}|R9צ yD"3fCm2%7Nb^dWS&ɘ~};wendstream +endobj +1665 0 obj<>/XObject<>>>>>endobj +1666 0 obj<>stream +xX]o6}ϯ@14j#G P`R{+"eD\Re'vWذ(\{o'S.gtvAiy򍦗,irEo|70=>]o&^\ფI2LhRZR73 NUM5TɄF n]kR' ¬|CyRImkZ.wN\뗼m+Ga(xL#XB6V.kJ%Eik\"ɶɻ~XGN>s|r-l:rN͍o4̌f\E(3EaֺZze]ߠښ%YU"Udc0 {ӧPWKO4uӜ`m\Jy0VX +tjqE=C:V ikʚuC pt1p +\=;{'Q.6̐TUNq&kTM(/ܞ KhkϮ1PR@}qaRQ;5~w^(f $9x2kt{2/&jUI|I|2ͥB*tƴ@ߎUHn,*vXFZZ"MWe%dAȩMCCh(5e`*ن#CBr#i4b OTE*҅+2\طR&]=(ȡ 2kW}k!g)k&Mn,?CR{kwt4'{hLx3 v!uPƞ>>gϭPƵA"+#U!6i&cT9z0;ЛFm!,=%2hSC+bC~KxYTjU pFahU>=`gvh-t<9*6aA2څ$Q0LQyK8QIZM:;[7cIxjj]7 "."ԃhq4_uV«ALe2?✩ԃŤH@CR&ڕ9a1|WZbzWy9@"SDWC ōJ=6mD|aBwUowbGxpУ;^&fC*yFPJ +a e**Z,uLAsdp-ޯښZ/n H GjS_\'䢉eD5M(A?*Y+ + {kCި&7ғp{1T_:og@t ֨᜗{t Ȁ7 <@ +1/3Sf2dϱ*~P#e"0J@Z H+~<&\yZ lX¯uo:m?ϓ~Aׅnt} +Y~bcvzqLht9NBK PJSd]W[Q &e8xdHendstream +endobj +1667 0 obj<>/XObject<<>>>>/Annots 878 0 R>>endobj +1668 0 obj<>stream +xVMo6W̭3e{KSlk{ PmqW"U}#ɍb"͛7o(=)_L˄Ҍze*R):tJ,  :Tie@)N6*N5%{nn:y1l-VêZה+;˻kX^Ų*i6_nqNqL%HB,NvTu q5K Qt!ViiDГ}TA6w=%kVR!$ZF::BeA/)C|(mצ'{>|ѕ5md^x{}z߯eUs$MAqH/We{m^ +%ȪA+0gI998S-<*@\^xBMz+KCp>me7mo/w$O8{t}MS }vyY:'Qu9S)_!Vҁ~c%Wi +eW?xq:wCM4S9Z~e*s-kC( + 0IBF":MpSgk„ 9ٽ έ( el3} v ީ w[6G̬FQG4|טtϛݏIH[Y%s \KطMc]Z(1ٌ8[/w%6UP"OpS0nTalXҶ $s۲0x^y=G3_Y+AUaI l!,O(-kW + RZؘ"^EKb;|O`(N8߉$FBaݹ tO?R0<ٖEF)k[4]9~knĤVy)qט#U(>?R^^_^<">}ȇow^ WtžJ)MSe qC˃l޲C{.!eoy" $9e7c/גendstream +endobj +1669 0 obj<>/XObject<<>>>>>>endobj +1670 0 obj<>stream +xVn6}Wc%K)E^ +q-EAS]ԒT}ϐ%m Q9&8ʠ!a*z;'yJE18ٜhׂ&fx}Y^.FqO{TݡBt{I V_z%iTLRBJ=9qR9 +ړВY9OiEۋ̜25m=T(ɒgWy4;D͆8<2t؞ZxV9y;:xߐ[ON8\d*hPXR('05Ш=ޡ 20N`-G%|VzPQS" yF8MQVRH!au‰V11;XrKr6kdl6_SVXmF:}Ȯ^Taklkz~a¢u4JF%ΘkBߟts 1}_A==9ƕW"u7q8G7LOp;#s(8 +=TUNQNj* OwJZQeeF1k9g7ՠDR0) ]͏XtR1!,Gy,,˲Y.U6FqhS`_#ѯC0m4OyPt!LZHO7 n'-D0tH"NJaA,Y FNn}4CL 50a)VFC9 `tLa?يdiiytln6nLq ==pO)|HsRCսtwS| Uk:_dY b2Z]rÍ'Lendstream +endobj +1671 0 obj<>/XObject<<>>>>/Annots 883 0 R>>endobj +1672 0 obj<>stream xVMo8WmS -)ܒM.@@KtD"$e{߾o(q\ -mJ$ͼG3JhOBf4SHd>8)Zʼn4[I60.ϗ?F)bF FI*攧P~3/O ޸g.%'X!|A=NiQS{ۢVX~BI/3,?͏P5j}ΫRgjmuM"mrjC\SJc# ,J̳) mVn >(Y]JU+Ö4]׶ֱ'm?SRW~Hi;ZkP':uǯZ\+91خ\#3VEݕo~i/Tf=Y7o$ ~zcncpHoJzEg ʘB1gl,$$_Idʭu6G3P\KZئ3֋ARRTF@U -PINhZ]nYCD{@O=doMY!r1Oyd,Xe7KQXzqh=&^yA5%qVhb݉,K. AW4;eAIđZZrZjS)wƱxനG! -V-$cdPkTv@^9Z<.ti#sʄz {Nh]l߿k #%Å1kDrTcD,qvc{OK4P -!6 ;uزUg"^2DР|4mE)HX "3 9cc&AWqq:~dو{䶶&) uܤLDR=j(wk o9D4҇s hS颊 4èJj3yRck*[I#6 Xez3(ǝ"z>;N+[t - &rsc<7'9.5).#ǥ]/F`jendstream -endobj -1931 0 obj<>/XObject<<>>>>/Annots 1120 0 R>>endobj -1932 0 obj<>stream -xeTn0+9%M[%m nC.4HŪ}Tpa̼e/f$t|Ey3-.1.8x,S}xwt-gؑ y1Xw3:[}gl'Br{&tm[+T~@·"M=۞X:U6qȆ b@M>n:8ATU#ALCJBFW;uo˽q ZR+T=VԙP0'i\\Sn"1D @JW7YK`UkcLe^Fv?Za=v 6;Ӱ<2)ы2Р J+J(dKg%hrc⟤>]S}{=v]'ZK'PxŜlr2K SN jh[:nBy)_k1z !c82\C, 3eVo%,Bk6CEZT@G_ Y]h[ccIwo/Bܨ8(!QaH=DYS`GvenlNipC߭yBGX]åLL.gWѠL\2Z0<>mF?Fɮendstream -endobj -1933 0 obj<>/XObject<<>>>>/Annots 1127 0 R>>endobj -1934 0 obj<>stream -xVM6W CZ\HݤnrXlD[L$);}CJdQh$97f4ߘVS-)-h_"T|͛W%q-I4j+%Mh|f%[z4_q-{_|zӹӝo75M'ruKC/M.NV4#zgSzOTZkv**NfQ|4x::Y$Q`B㽆:uhL(Uc:]6L&05;9LZ$\J-Yy0fRQQ:LU2uRL,$rᨶ&iW@/zI81 JZSW)B|GKw2gv$œ,ZqQB$P<"[Y$)0"DF(NK#mi*IJ#B3#o#3gzA//.vfԘKoseT -<7'8N "͕4d0@i -憒 -UxL/=R$cHjljͷG_YaD;Nf#~x'f^/i#MZn]_ ʦBS"8CR4m于/G1zw.%SU -WV=C[&?o v_&FpM߰B=N yϦ3Ỵ#8owfZ";zB϶̝Y~.S©g(g('^dvD!jjabK6Ad@ej(o6pUo)"4N|FL A CSPg+>l;γX t GJ=Jg,9L&d%b TVmGOCM0}l&n< rExnjO"Ï~=Qƒ5===cz2s7h0 sqn r7dV>BKM2{絛g::?!j˰_Fy3884nNgh*b^mqz~ޏz-MFL4y7T[K+Q ɛ. 5jGM]dmdU*KIXPMB誳~3Ny6c2菃nFe>C6$8$djwbNa i#U.Ȇ\1+ƞ&+z,T^1B Xz $FAoG}!e0e}pir+w4ju{!lռݐ[M얕6Z.rlh~ endstream -endobj -1935 0 obj<>/XObject<<>>>>>>endobj -1936 0 obj<>stream -xuOo0 -jvR=r۰vEZm,y~OmY a㏏H)7MFdHli]lgmnq]S\y]Iȓ$˭tɱ!_1>tRՑ7}xǚ}g+JXvԛ:5 ]zzAWEBQC\~wlMG$Ow$&m::X9yB!%T3[Pf/.{)9GSt :dpxH4 sT*(nE^m;t iF R VH'K/Ƴ GY%qePr``Z:YAhmZk#UrTq5 tJrA،_;чhT')[h5c09Ժm">7wy>*|Ŗ?8ԄUҫ8>/XObject<>>>>>endobj -1938 0 obj<>stream +mJ$ͼG3JhOBf4SHd>8)Zʼn4[I60.ϗ?F)bF FI*攧P~3/O ޸g.%'X!|A=NiQ=mQG,?$闏]KmO[vWPUIl36OTȺR6AB!)ixBvIh+X ,ɮ`Pi@ aK Nk[ؓmƟ){) K+?}Νj5 +ψnntxBN຿W-lWTg^7xz *cd,7DQAY?رq``18$C7%ŽճeL3^6K ~?MGc2yֺ#(rQ t-lJX[ R d)G*#u*o~ P\Cd`׈N\ml!=cz| f'k㷦Ƭ|Ga\v1+pq Vĸ8~xNUdlDr[[ UvQnRV~ME[ҵ}rctQńah%Cљ|\r)˱5x-ڤtLṗ2qgNd|tyA}Dҕ-:vX1Mx'YFs=nendstream +endobj +1673 0 obj<>/XObject<<>>>>/Annots 886 0 R>>endobj +1674 0 obj<>stream +xeTKO@W8lb 7PKUTJҪ.{/ػfq_oM@Qěx3cf_ MIhtAY= /g8x,Scx2H"l%fTSHugi`|;$MԋՒ6yxB\Zze4$)^ncousMJ6y%sڱf2jeGސ*R-k-_l%Sypӹj4vS;Y@"cwRJa(-[<ΰ#2b<^9gt6+WTZJBzmvf?OmiU)eAAbG)ƷQ,4y#&%h2c>]Q}s5m+ZK'PxŜrԇK S jh[:nBy)_k1z몧 !c82ʼn\}, 3eՔ,B[6*}EȔCG_Y]hccIwo/Bܨ8(!Qa]K=DvYS`p$ d)IfyF'X]h&+0tO} ~  ֮endstream +endobj +1675 0 obj<>/XObject<<>>>>/Annots 893 0 R>>endobj +1676 0 obj<>stream +xVM6W CZnM&hEPt{$b".IR%"@ ̼7(ƴNh͢~8ZQEyh?Jz]}Vq:LֳhNu+%w(iwEd֟.;Z,p-{_|zӅӟ>lG7;Jfj}KC/u!NJjT'AUf;GouF9mT)_l?f4M2~<['+rFJ5=*lu83R#Bѻ)]`@Zd 0{kCov>\Z$\IQ[; 0z2QQuN22s(xupXi,I %2ա8[;dՍ;t'm>#Qdi /ikGJRl5<HR%`D PRQ:.h6TόDNΜt7 _z[(KR +>%q^G>S%BՒ SqH2+B\SjPl, -U2d-Ri*,zW_P7\G' +~ }mi:ieݠǤZgFn}_ fTpNh3/5^RK0%_o&m]I +B<{ƶJ#F~H5?uCq7L$~C {8(Mg iGtqޑWDw?3wgJu2 +j ? ĐEu(%?m"# +%^?y|/[&OO$k0^=D TΪvn#PHW"Ac -QW`¾ďhd JӏNE(:A!gEA0}/t:cQY~Pubx4l6V#K5?^P@жj7zZjiLFf3n,@[HKύYēqW ߃AOT??cz2s?h8T9h+jn`ɬ|&҅~87N]U.Hk? tBu$ 1BԎaZ 'vpp?Ӹ=/*Bxq4 ӮQkksZ/geMSK_ʽg+/zIu59лPixdB7e5kAJY^JRcm*ǯDWEMƳ8gTc>/XObject<<>>>>>>endobj +1678 0 obj<>stream +xuAs01GҔ[;N/\JJ2>&mi +Ì-?g -MhRgxAyKZ+tRՑ7}xǚ}g+JXvԛ:- ]zzA7ق4]9:2.IkH +Mtts>/XObject<>>>>>endobj +1680 0 obj<>stream xWoH~_1D - poihtHr=xYbvM;]+T|ӰG+Jg)FhD=<4 p_7F]ǣhL=|?~i~ֹSKh̻xn6bKK^DS˵k7SHG*ߜ>R7-.(vo|9hJ O=ot_HEZr&+0"[%:weLq?qN+.LԔB5InEl )7wkE[qv>a0eUԦsg2[{׍Qa4*|F7\hH/43k~iDqctnMFS쇽*F&-B'. s + poihtHr=xYbvM;]+T|ӰG+Jg)FhD=<4 p_7F]ǣhL=|?~i~ֹSKh̻xn6bKK~DS˵k7SHG*ߜ>R7-.(vo|9hJ O=ot_HEZr&+0"[%:weLq?qN+.LԔB5InEl )7wkE[qv>a0eUԦsg2[ՍQa4*|F7\hH/43k~iDqctnMFS쇽*F&-B'. s 0'V:4 -h EI z lvHyv2Xnߏz -Ehm^5ӟ/nA:=@9Mf:$ I^`0,MJIvs尜<̘&a~ aNc$OŭK&7)+;ɮяe=Tp" Ј`~/`hr@K8.nʼ Kh':6{-t+ 8eڭe韷09,`?CfRf9UaĕuSlF?=8W|[54>/XObject<<>>>>>>endobj -1940 0 obj<>stream +1681 0 obj<>/XObject<<>>>>>>endobj +1682 0 obj<>stream xWn8}W )P˖:)(m} -Q6tI*gH%6MD&vΜi9]i2e#ٜ+>ƏT8dvJyN >f+Z-KK[UJ'x2k*eQnFpɭ/$47ʔ3y_<_/^h0eSr=ݔ%:uJy`KjY~gTki#D/k>A,FtH,b2](ힴ3@ up,%%NJĤ2q*hE:{ZI2?kcp]2(2\R|1jب-lc8ވ;6@4Ωneb (2r(MZJ$9 j *NTGYRiVd!Thok\^|Tf]i4"yĜO!?) qD^@W,251%f@:Ƹ?U%PS%ЄD1DGذIІ((bµ9]Y#BDcUB%DLJ; ̹‹ %9[ -)F>Dڠ6urz7HS(7r@:渚PX $K\ь;ivhS5>mU-ο`J[Q<KN -}J'1)eu%,ٻEvZ|Ρ@kсC?JO!pEgm6K `rskWTڞv*`8;9sYofNfK dpQbwȐOGD 3:-`sBbrj?&yƼʍ޼;. -oR?1Ǵ8jed-ȴ -̕¨VuE'ȃl;7"Ϯ$RAZKA Y7dmL[cj/[H{萰9 %4VԪR0!@-qĚ璢c:iftx^M! 컴XxL%UlJ&l$Vh;fpB`/4N7y|\/zY|r(!1}PF"&cw ѣ` ]XEUaݓeFjsU#e"E`F 7faϘ:,1G,m[ m|ݵx[2-oVJH:k)@Hǚ -35221,'M-˱cҮ]-h++^XHc\`_Ukq$cva o]35'47E=zF(F/[`><ŋ8G>ˋ/~>endstream -endobj -1941 0 obj<>/XObject<<>>>>>>endobj -1942 0 obj<>stream -xWn6}W ܇zDd-iKa} Pmq#*I IɎ66Ab[Μ99Cs1)~gt3%4|7V~}1f Zody7|:u>ϳYfn<>he ͢ ץrU$yk*G$rߊ%`8S^M^؝.5l*hT.@pIZ2o2- x#ŔfٜoMU{M]mqcJ?? iv´ 1|N9O*k`ު]kQvn}z>ex)<֍]$Ip%A[h3Vv^4.c! GZ3\) -wִeC^J;1j -ݗw{t]5'7/9PVGO9tZ}RLqLuHlWPُ֜ortabq6 ?bw_|8P_`N^yIf$2/ -"o *"W\BzkޭRT. ]cʢk2jGJiڪ$m,bV>\Ib-jkֿ~|c8ԨIh'zZxGL$s@2TO<*#{3٬ mG%A:kXB>{@z-E'V8o[ȹÎUy^)%LkB! ?/ ->K*4gR$ -3co>LV<@^ RDjIMa -wFrcQb0VQ3']7ri7'I7q! -sM -j!71|c4-{g<o103PBGjDQpǍEF2P 18=~슣1ΩT WЇӢ fsE=Z$`ex1 V -܇+pCTФA/D뫰$ V8 :;pgpr֥rcO@%-/7p\ ȼ[Y ؘ6i ]n>>Q'aiw0fJS P݇7}I#n66gtI.{ǼBhLWeE%ƴ; u`_\6 Gis@WEvԾA8X/<05+azQhQ+ )Qs|04<%hrEjr 37p(9p9f/#җ1`JsWp 4t $IL'Q>:*ud8`>M"b;..12CG@vq)b\DpƓb0q|MBv8d0WU-=> Š&A-qEe,}&z~3yO;~-So5m|;"tf/%\kIendstream -endobj -1943 0 obj<>/XObject<<>>>>>>endobj -1944 0 obj<>stream +}J'1)eu%,ٻEvZ|Ρ@kсC?JO!pEgm6K `rskWTڞv*`8;9sYofNfK dpQbwȐOGD 3:-`sBbrj?&yr㬃7D›TF`1m/:΢~>ZYp 612餄>/XObject<<>>>>>>endobj +1684 0 obj<>stream +xWn6}W ܇zDd-iKa} Pmq#*I IɎ66Ab[Μ99Cs1)~gt3%4|7V~}1f Zody7|:u>_glћ7͒x"}>,7z 4EGW8Kh*I0T|)IiQKpj2;]Fk؄UШ\TՁJ铴d6d52W[jG1)]ͮ9Gߚ2{>һ"4ǔ~~bWib>s2+iT 'U!|>˖Rx9KIJ~c)1 тg$ 켖i\ǎC4*DC{7JgRf?iTywba/=jOn^Ə9r~e +*6)s{cLۯ=95\㌽mܿ3p*ʿlNk$)̖Ie^ +iDգAUC%D*΅.&(6[ ]IƔEאeԄҴUAIxYF!} +[8%:3:qQ34i5buO̵HV突d!xTzGFChg= YAR=BJt:yDAWP}&6>|R-h7Չ[OJop޶s+99^RGU1KbfҧC~Z_H7}Uh΀Ifu|:y.ǁV!Y-e6Ԉ6^`_afN>=nn2N*!.s oC.m6  +5s3PCn2Mc 0li8MZ&3< x1$blafԈಏ?R7d,b#q70t1J{RK]GcS@^EQC+?{εzI(b#b P1/V08}I_:/WaIZ1pu:vP5yK4H;7FJZ^9oḶ &y`yA1mA~` Bs}}06{MO*Ӻ$a̔@ A>o"Fnm(4lF]0ΟyF?>8,JiQKw&ϹlI"fX )}qRѱ^0y8DajV ;Аh V7 Sa3hx,J!<Kgn:PsrI;_F/1{c.T+<PAh HܓOj}tt +q.87}Dv\\cdO +&+៹\SF7p '"apȮaA5][z|+,AqŋAwAM>[v{Xjݧ;jMf0w [pu3omjlvEl1g/8 kKendstream +endobj +1685 0 obj<>/XObject<<>>>>>>endobj +1686 0 obj<>stream xX]S}WtlmXnnu] \l*yFf鞑m&U{|8}t4!xLYy0B'gx=iyp1?84ič^ӃͳCj}.8揮TiɅwxhc }H?{WW? 4+tNWREA.rK?@m}f{\:+ vL) @@ -4430,35 +3858,39 @@ S %d%uV7$Bu3xkE}v {m) t\%"n jd-T+}]Kw^)YkoE ?+>DV 쎚=CE4 UJ ی7<U/^I:amQRհ]>sj&80^@ aIKM77޽u&-]wb:mLvfT BbQ]d1>Q! F4 -LC4T]DVdq0#ڋ%B&u ReX桊X@ذp=6aܩ KVv+сRk  DQ vQKxy@.`"4o!~Y_oȿld3@d@e11hTcStqdJ`,09 k;Q=Y$O+"?fIhM'ox_b9.xshk0,6eQ/Ȗ0`UF*O'1~rvLӓƳ9y'? ˮ2f/]+?@YÓ6s5?Nendstream -endobj -1945 0 obj<>/XObject<<>>>>>>endobj -1946 0 obj<>stream -xXko6_q|Iص4Ma@f qX[Q@@KTE"5JKʎAڠ@+qι 3c::t2>G{VRw콿>шGNN?R>)d4rY'zGZT#/%e"[CrD|e3eTʒ\eR懴U>Xl@KRt4#mg?k -d#`,cY xmBVA+t6KtuLnizu?cr?OIr6:?3 ]fzGyH#JMC*"˩B NP-CʵKh!!8*Q׬1c8jPVL8hQ~Zuֲ5>lQg.Ma)=w4:;;[YLkg^<DUmEp`MCOP˒C(-2̓\޽!h;{ iɮ1@1;WB$bLU7m봽/DtBvEniHz5*PCwyTZvٖY&FR=-J*n%:όmo;(>u_ht|+j@+@-KދEvN܃҆::MDAn -mTUԚ|?j7 wdt1Jh Ƴ˭"9ѭ^ZSY-alc2E(8f䋗qb!`-COO?B;Ng7_M'{.&Lg$yH&m_FFkt䛁黮|WmI1wfiQa$Pou>[䍶Q[R_I6]PhJ)6d܏9m4f(P支;MpfBNjd6 Nm"R9)tNZ*ڌTbZ .TRriiya ny@Tr)uKwxk0k;f&#›T7!mSKu32%yNmoǟ0e4Y#:P %JqdaZ:65=/e_u֟qq+nndapnחe ".i\ -z. R^V<c!2l>Fud }v_3F0g7[j'E\-f)m'RqL7_οB-(YHX|a|x#T͖Fl+om݊!(5W5 MbpԫE"?aSohK\x%͚0]'HF-ymt@J/o 7V -\X=h44u+eYN{^u)xն4-L)hDwil+I@"ܹG:ZA̎쾿>m/x08 j+5QÅ1?qu7=>9|*G$m_5endstream -endobj -1947 0 obj<>/XObject<<>>>>>>endobj -1948 0 obj<>stream +LC4T]DVdq0#ڋ%B&u ReX桊X@ذp=6aܩ KVv+сRk  DQ vQKxy@.`"4o!~Y_oȿld3@d@e11hTcStqdJ`,09 k;Q=Y$O+"?fI6@~ʗQߦ̲O<8E\#["€UJ.9ஜu +ӮbI-4X뱉'/I_P֖kN)W7TՑIw{DHA^bs]G[D,}nEi"KһRe{$GXAh֋Z{¬0cO ը]'E&0FAȜwل8-4lkn^lt#*rp GKeP>(ڲn3JxVj&n#mYjTO&$$&ԋ};;=t> 1OOΧt2,6 盽tw:߯Ogo# +O?XOendstream +endobj +1687 0 obj<>/XObject<<>>>>>>endobj +1688 0 obj<>stream +xXko6_q|Iص,Ma@f qX[Q@@KTE"UJKʎAڠ@+qιވч1PV C: =_+ػH_hDI#'( d^UoO, H #M#-*Iʑ䗒2-!9C"ҙh*yljzVeI2)CZ*pPi6% ?:Ł6A|@ -m+@8iI9(ARXyi*#Sg5d'r;J._$ʒQ) H6bi dN= %E; ʯz>Zd4W\/DFibܠtOdN*%;?f^&{ӸN&<[:H&drp1M?Og$M_hW?'4$oc8 3Pjwt44!j,Ȱb:\K TiۉBu3V#f +jń3QuPg-[+҃,}GSU5mv6NuȻcXANT5HVIN 4;,9?"wwk7NEpqZlhTޚ+ܭxY RseQ)yq`/IY*q)SAZ9?*FhyeWެ)9juξ\pbl$,nݒNANTpcuUգ\1[NiںOSr^Vi5XUךIWmJRJTVI{]6 ۽H[,+@~?Y$7:/ +N+'|^ӝ5C te;j3!.>'Ƹ1${ /endstream +endobj +1689 0 obj<>/XObject<<>>>>>>endobj +1690 0 obj<>stream xWmOHί$E#U'Y6lwͮ 3k;o{wggyA:yC҃NCAkHs|JZtطw:8hv蒂^CLPSSCN6,%]L1WwqzYތ$1oIG&ӛq]\RrCsIOIKi[tW~9WDtnQ$tl4"Q8I0S+ 6ӭnuB*'Š(2t.(M2r4_5](re&;ˌH%[z) RF~`Hc0k w˃>LFj"AKN")&cA>J|_&'E4@. [3̂=Gj{.>7ѴNNs_TT129!:— 8|8aHO1G a39i_ >LV$n+cYp öD"qu˖g;C#Ld*1J&м aDEXIc}|5]ѴNs$ua"΅=Uh.xEdUf+rz=Z;qmVězvlr &87j]ƍCXT] >%2/LVIbY2@pC` --^JࡴƿA πD 4s ~q/5y,g3lmP]Qw#X3;jhg&^2sF*y)OOj7b_iq}H1?ʭ8k^<=q 4Ԕ <TXNbY[nQϧqԝr$딌䗂 BaPT+5tRwo(kP)^YK%W'0Hfr'Ew> ^fWW`'DKv~z6^g=T&tC>:> ^endstream +NVʶK_zo)]#ܖy^6Mdh-MgtWtD&*Qj7.g+~'"cM-D!? Ƶ#{y H9Rm~)$ꎝ)Gg? O{[*reCXI5]<51R`b*Y%w҉ŐK}ChࡴƿA πD 4s ~q/5y,g3lmP]Qw#X3;jhg&^2sF*y)OOj7b_iq}H1?ʭ8k^<=q 4Ԕ <TXNbY[nQϧqԝr$딌䗂 BaPT+5tRwo(kP)^YK%W'0Hfr'Ew> ^fWW`'DKv~z6^g=T&tg|t}aendstream endobj -1949 0 obj<>/XObject<<>>>>>>endobj -1950 0 obj<>stream -xRMO@+,P@ڨq.-Ma+Km$5~ċl6 ͼ73oO# (jg>FqbDiBnP:ܹ9(q #/\MY-wD4 -/ywբ[Q.},UGF)iJڷ_kKu]S/Ӈ9.jU/ "Hjvc*9/-{3;G7`-osmmx߾cvv_Vߩ.*j!e.ɳ>gzcZ4CZ5jy6yN*:bW]4^ Xpq)G'Axm<;Mendstream +1691 0 obj<>/XObject<<>>>>>>endobj +1692 0 obj<>stream +xRN0+1y H=DP"!n촩 n˒ٝ7'O'8DđW|x8dLnP8̹ +dLྏ,w3\Ej)j,^F5A\z^a'QR )o 6T$뺦Z2[r\V]ث^,&.N40n*9/э&XK䣬B[$>Yo ;?X߯UbhT%MF5Q@Y39 8-W!"Z5jy:}M[輫T݊Եez4^ YpfqQHI 6v9 Mendstream endobj -1951 0 obj<>/XObject<>>>>>endobj -1952 0 obj<>stream -xWn8}W[SK.[l[7E ([TI^J(-kQ3gΜ8%LfJkJYrK|הM2GD?MWyjL/ƏhzI\2#D7BՍ4%TmtF+5KAU+~2\@$/7Fow+sLW7W^>ߓCLRTPքV;&-(-MTYRi+Mh8TX +1693 0 obj<>/XObject<>>>>>endobj +1694 0 obj<>stream +xWn8}W[SK.[l[7E ([TI^J(-kQ3gΜ8%LfJkJYrK|הM2GD?MWyjL/ƏhzI\2#D7BՍ4'TmtF+5KAU+~2\@$/7Fow+sLW7W^>ߓCLRTPքV;&-(-MTYRi+Mh8TX sD.&1T"yS - bFB5PULsSjR6;m(0/@-gB{sm4Hpσ!Hm@"G@b5rGj@9d C2D0tp6 pSY׫+CBͺ1r ^. @@ -4467,173 +3899,179 @@ pSY׫+CB = JYab|sdK[AQε~M /GpmItA%)Ce-<`($e%V"GBjl oi#Z$,H (svW k峒74;RQ-}o7|4 [%4^N+La'}wd#Zp]<JyYbBSޕd.Mh6/s䊵#ٻl0ڳ+?g^h':GVE.],|!3D @QۍΊCõ;; -Ja>Ի2c0'R;mHQO,V-y+5:lLpVY|[KqRdߪ2G,?ӱQƏza6TnJ`K#+'0 (UDdܱꙷe7At.Bƽ4A3ƂBqve5{3'v$7v*ຂLnZaխֲb622y.;B{񋃠Uwhn|JmDHtZ_ -PqoK409M7]62?g__endstream -endobj -1953 0 obj<>/XObject<<>>>>>>endobj -1954 0 obj<>stream -xW]oF|X2mJlg;n6yPȣt1cxT -ŤM;ȻIHS&U0%>WjJFxk -/iUHp9-hz)*r6+c77y2b`6&_SlhgW6:-tR鞿RjA(1IS贠*Uv,<zU.N&4"[Ҙ`!X].SZ4$!kXlo7bT5DsNA* -HQPS?9C`<'`!FG@GnX[SRMXiRZPmt(fr3E6u8q>%b(6}|Y{\0=N;(iN)HF\F]T;ZTlo(R9YՈLAv6goY"ܠ4ɉЬIIR٧3S"8rDeU}͟nfsRe*>ш bMj+k_XZRkGg^i_J+pA-Y<k>ͺDٰ~ x%Jc*^c*So^fJ.БI{@85?DOd 6|=e/ ot<&2 UHJ ݸzN'<]TCIl c - bBH_@>+ k 8׶n`VP–K]&R`:ϗ$Vw(|œ/ij<9-upEYirdP>ѪB"4n=I-M rqݞDP Q3B՞J[Cfo}B@NnbrpGG49n/cg]ϥݰH1/VVwgSӍ;@f[%rZ)K4_ FS FwɅKFe9?zW]'N+t}B_8%g~7frP,s)5]}3tkH'9ڏ#6-b4|ublc%R̲[Ȁo`YQ}ۀ pz}1<|~^Uּ yU;x">wmp-/@ )1dKEWJ{Yi;Wr*4Vh.C*er;ܙ-VhЊzCO٤?9{RkNiA2-Aʤi\4HO^5Zs4$oųT! rDkB+}z^l @M g<:zr|ݾ5~? w.?x8WDN{5 l3Qono3 ӣ aq?Kkendstream -endobj -1955 0 obj<>/XObject<<>>>>>>endobj -1956 0 obj<>stream -xX[OH~W7@M8V+hWhK U{B8:ceŏq5̹|; R:hL`rӀ~9^p  tk]RuIoOd۱WM\}z{S[ל꺒fRn?h391_um1v_~\fܰXet;_@n.׾t++^<-K׫1/}ԧa8挹ХUR#9ȃl(ѰGctYʬ9^Zi2wnXӧj!\S+zhgV62Q2d a-EPKRU/AC'Ũ"sk륤6l-R.EE(mՍRa$8W$U:AV@JG YUBeR0ي'pе #5%e;[ޥ^ -(LH+߇#%`A+3]"T hpZٶ (|NQ,@46DF>Beh*j\%ppmw61ӚV?H GK-@υ$.f2Z);v~7q }V -Z,i1b9(t%]an]66y AD";ތrKs036dQ%CQW mT%*D(ʨcO%ݛ0ȡc&3Q#"ҵ}tay[;ʗ552U-j}A:,ium2OC n5O_cAOIaPAfZgB&gr_Ŕ;We";jfd?M_,Br-Mg#z_OQ`E J%C σuendstream -endobj -1957 0 obj<>/XObject<<>>>>>>endobj -1958 0 obj<>stream -xMo6s [(MX0dɬH9CR#xtO)y9<~4H73JfpuwMaH=7hLSڤe*>. ճ& JZ۵:&chW~ CF<1TJy`J0"z'v/ -H }>RBzJ:&\'U -Я IEydMhz.Lv/=r,ne}ˀ69OΊ'DO(+cK$#\ eqS ƛgZT'X.ߏ|4Y]k"1TЈbe⳹ۯxXv[TR^o[v:}wj\X\7mN9ؿv{xέ'݇UwGŘK{]^oԳv>bx0$S\u͵mzQ̺xDQ-c0j3ڮ>̶Q)wV_u`?~_ji!J,=34!vI%'ImrUk$\jlfp@>! FM9.-<1ߩ*W*#d2U=i-W J!9M=ǜނa;JL77֐Svbc4sIAkcLhd8 $JӺvij  >ڛÐ?(Lsg+ 16b#9p.=ϘVUcpL0BiLE ˱%I̜*x^"M&NsٴZ-@&~Y(h t4/6aP[Lo`e74s YmU*wo"gy ֻiWP]!elxLvgEȋ)yܖUcM>jbU yr@^*M,Ums@ac,cӼ\XQ?$|~WZM5"\^WWws g7t|rA*EG=qO)(08U(οĝg`!!?  <3endstream -endobj -1959 0 obj<>/XObject<<>>>>>>endobj -1960 0 obj<>stream -xW]oF|X%Na"mv'+n-(8GwDm$LKϽ&iJGSI<4N)~bjwx7sxbzpdBlov|yW卿07(M)R?Fm|<~8e_M%ge^ϒ-d/yK>OoΒn,6Ke ͋4^+INpҐ+eM=jt֕('z;6Pwǔ$wQ]7YitͺUʆRk _-~&Jg}28մ&e9Ez0S+%[ʑ %$\x</Hv0eL?'R!Te=BW~U2>rz&Ќ9!]mH!)sɟ0Y&U -<mRaIJ|fGTj+ 4²jP=@hH,5֠WYZ_IGZ;:. -P@6odP%7&t#F1`fw7 [F1Y@3{pϞmkkSpgPqSworoCk5$)+ hgyIwu+E Ȣ֋ΪZU*ԣλRp5ЋOաdtO97@9%,(=hڹXz$dvXOzB`f!n|\ OgBd`Bsw}Q}E>IkR݂d[ͱy9m1nT( ?XY528{BT<= -Ԅ 'C .sy6~KzgXYb+@9I-_ m兌1A,V)`Yrś`'ZpFP{/.ji|OOpGh@,r :=JH["p+`m_6.w W)Y -l8N:ԯL( 0/#Ue;߉2H14ٙ>n;^N1h}}&f+ ;rco -*vo$2I>af\g-oI=Ď03q;>p0TgRof Xl(k ?c -+Wg$)0Ę.-=h EYEnz{DP(h3H >*q*S+.'l~dc{}twEo8(]AD1At*|B'RᤃIiw7eic7(뀗p({x/C;9]1x/Cv`a% /p D-Alp?dcL>/XObject<<>>>>>>endobj -1962 0 obj<>stream -xWnF}W[@u$qq -#rW%{fDFJQ -7rw.gΜ}=S_} h8Ev z4#M'{o#)>Oޏߧ0ƕtBaD8QD6dyGQdc~V+,i7ZR(IvOXz.?qz'Zψ1Qtl6Z@d$~wc{pl.$mBӴأJCW($@qxQbig=vs9~,ohvRv> -BSQ;Qa!U#`ƴPi!Txw\tI[i]ڕY(NJ=. xWy0@ -9I0yTFZ[SIv!0JҡSiapl1W ؜"N`/`saDqA ]wѪއTp"Jl!NJ ͼ=6y-3 !QkAl:d:k%9> 6f<7=5u+[,\XA&ɄV6 $V.4_br(Yh݌>rth9W= K1 ^一w'e!vz!E T8Erfu _$]ў"Y נr-.((Dh9`+r/i[%UotFD!<.J8mg -aQXcJeKQAg AiI ؅[v FR$FL*> R>+ yD`t;Um%K\YN bTMg|rSr.@%o- |6kG3e\Q£[Ÿ22ƀm[.z MCoԎtXLsB&s;1lxrh/71;Pb-!)XSՖ&ђd!/S]Jd"1݄[/3C@; *R Mg@nFJ 3} -:u7~<zYFVR" n \|kGsRzKMKsic?Y7me:$/lM@hoeqs_Wu쟖c|i<mvuw}}Cg4'v{iutC3GЍ`|>>!&>/XObject<<>>>>/Annots 1130 0 R>>endobj -1964 0 obj<>stream +PqoK409M7]60?g_Ebendstream +endobj +1695 0 obj<>/XObject<<>>>>>>endobj +1696 0 obj<>stream +xW]oF|X2mJ,g;n6yPȣt1cxT +ͤM;ȻIHS&,dv#^|KZ&8k: i9?e4Mq@ϥ]:QΦuelf&b9;]Sr6v/mBV紵N4=WJ&ȳ5%&մ7iJ[t5U^p>Gв8/@ k}~gbUN hM tDf2 rD͐Q%u nI&,Ut%*Mׇßz^.\mpg5|Uy, PqE9FI*ҡBa0wf0F#U# 8 7P7]r&6ƣU:'ف,SU-6:Zn3":b`8tcwA1LU wY `}A.k󸠏K#.Zf.|o--TV7uԬjZ^2 o7N,@CnPDX hޤ$RNZЎ)S9B"2ા7gE2hD a1Q/X^-}5S/N4/s,\ +n5VTf]"Y ]lX\hWm%Hֱ VVH/p1wCu)7n/EjWW$FǽHE s'H>^uX7^r:xSCt*$Gn\dN'Y<]TCIl c + bBH_B>k k 8׶n`VP–K]&R`:ϗ5$V(|œ/ij<9-upEYkrdP>ѪB"4n=I-M rq%ݞDP Q3BJ[Cfo}GB@NnbrpGG4yu_*n{O_Hab^*^+ww0"J'S4CiD@39qLč Ǘˬsh>%z0v:Yg-fl?r}6t├ƚPԛidAiqLהwiT"cӭy"~@Fe)h竓c;E{(b=B|b4ds8׫ӲBmȫyǓk~7f@nQRCt\|{e,WI/eV?BlH4(HFTP|{nH!cb'0ʻ80w>~u._ʘFb~o}-_ vμBc29R& ϝwX`0hM3*V씖_$LE0DU w/LC/Q<{(` 1H I&AGΰT =p˳-W+_?㍟=σsjS׵O7-|m>]3k&p/D~7w63LR&pzy|ӝLgb\, '3>~y?nendstream +endobj +1697 0 obj<>/XObject<<>>>>>>endobj +1698 0 obj<>stream +xX[OH~W7@M8J+K U{B8eŏq5̹|; R:hL`r>/gi ώhx[ߵ.uݺ꧃ B[+&zVJ wz}56AeGx3ԷOp,L~?BNLohh[]l)>$7l.6lY:~;'y˵o4 +~>EO/ivpjzpK>4i9c.ti|$=y ==hpL.KYJSxNjnv5} i$JmYCJ<ƚBDGɐ/BҐ.I^0įO͋QEBKIs]KYZ\ +K(mՍRQIvq +>ZM3Itԕ3f F- )`O8kMoG`kJttKPv ʓJ ~LtQ+E+@Loc%SG2mOAP#XbOU` Nn^FEWM“89П lc5~,@<:W$Az8=" D0Q$h[)hk糴x,Qt}|*$DЙ(,>ʪ.xr(frjH_Di#3fXhRׁpAoq@@ƭd9hdbc*sBl 7^;N23q"ێ(!I*I j439=I @:CWyd\d0ڑR1OD2^ T(3-M賮:&X+AG_5/Z6ecA$(gd>zn>9cJvѨ\r>]JYaC*lǞAC/J7a CLfFEDQkm$v/ks kѳe .j}A:,TdD< -<}َ>iv>'E +2C7>2 E>-g ^-^=qvC8.4}qzʵH +4 )}ֳVz5:w]ls1Fľ~ cgt42[TTZf,&ntK1Բz 1=q|0ɂtM[}ۛN~ u>Z8oT?Bttm;a*)ܘKxFVĐpg&&O=ϯ'Q`E J>/XObject<<>>>>>>endobj +1700 0 obj<>stream +xMo6s [Gq{G[^DGdVd}!)hMȔDμq" +uLɌh]^Qf75mr +0 i].3AwvIR=k24k5]CZJ:ڈv54dDUi(RC\,oBFICnvRiBZȼGc!j 4{DTOjCQ2/B +!IȬ, Mϥ)Xe7Wӝ0E}l1AsЦIYqĝ(Zeu B<`dzk<8Nw1xlTk+р"o*tM@TjQR^!~\|6߀{u605Žw R=\)~7!4 +vߝ?V?W< v[a01S׍ rϹ5Dhpui+{]̈́Nm#?ݏa7W}smr>qobX'+댷m`}m>؏7ߗCH+5R-KEm M:.>]kRiژBե> +Z:41\0OmC Q/Et fK$0Ϫ~oPT](ÁHK %6c[go%+ k)Rϭw;11$ 5`H]&4UCVeYSU4v}L?8LSf+816f#9p.ϘV]chB1BiL-+%H̝*x^2KNtZ@6~ȧY(h!4/6aP;Lo`e4>s ]]U*wo"'y OhP2m)ebxLvgE؋)}ܖUcm>jĶbUJyr@^*M-Ums@cc,c\XA?$|~W:m5!\^VsfA8OpAcqO"2\qҞ8u3J~Jp]*_U5||Wy0чlF<3endstream +endobj +1701 0 obj<>/XObject<<>>>>>>endobj +1702 0 obj<>stream +xW]oF|X%Na"-v'(n-(8GwDm$LKσ&YJ'3I<4S:ŏT\/'tAOqLhҷO>zwy_&I#a0umm *}nTuxhԾ7"eu<- 3Os?|z +#eĴ(V +\ Su(/nS΍$v|A5JO)u.NӘVԮk@Yл A^ +lVbbY>x^59M2ۏkiL(w Lhp:ρz0i[[,ܷy[f9#;'ס1&د +A++F}/W^'2St`.0vя~I 8U@}m(#I|1kaB6\;&*\4UxU .*au0cJus]42 E U]緶GmrKn#um0Ͷ!tUJ['+k!>% +H,F@7ohL:hvOSL=k_b YklyJ:F,x"(5+sCeh$B#ʸ[ LROdb%Y[qc.#+\c{g;T YV:;31r:صoJ=YA + 1+KUfՅCŬ"B_C7="nvmә $tyc856?2 ʽ>׺;mt烢um7r.CJ " :op>Kp$㴿FֱjdpuK~8Vok}p +wy Ws:Jo|y0 ;龹jA4.a|.A.7^\J,c}qۣk'Qn&3|>/XObject<<>>>>>>endobj +1704 0 obj<>stream +xWnF}W[@%Y"`7Na4buVRbB*}쒔H) +@aF935ɐƴ:OA0t6u9}?W xO;\EWnID֒ݓYuܳX$jIi$=cHEhD +?#[p28 ky* '|7#?܃c[EtIo$i>WWB%;$ B&+N> {Vwf!?t}CW 0 rլ 46.bNs»Kb&KJO +׮B9VuIoͷG,"#8UȱHRͅE7dJ IUBbM #d̍X̀v_p{UlmH # NG`V>L\7Q:g q,PҖ5`p7Ng4M&u{yE/^+ p[99yiG8b湠~$C9V80..ss +u,-'%9!μaĂ3\EEݿ_ˍ hLmeǠJCWX\2"8; U;ZbkqYW-ʳt 8&#ċ.\D{Y4Ri"*BW++9Y$kZ6Cb>BT6[~O+*-]~4b~t5'SQ><?:&Y0(1F%܍(KPy@w5Z72 o zIVT<}d}V1 uZV59Ԁ9 +*֢j: +8hɢ\vG9JZ@z݄:5endstream +endobj +1705 0 obj<>/XObject<<>>>>/Annots 896 0 R>>endobj +1706 0 obj<>stream xWrFW*üJReYvJ N4)-,hj KZfj8jU Ubj|\,)<^Kv -/wKvCĤbFxzR %,הJ5HUnE Ҳ&k )tUdG( jS,Ǚ\}"\ d(ؐBŢRZ`.pkĉݻLV.]qNi/jQJO.tq*e*Z&űXZ(!CFc k.,݈i$*l}To;Ŧe#{dR-\MP^u"A*INS-eBf YX{;8UW&QaJӂ.UbU8wCrs5!3P(VꤧS`cXUx~ogrbNT)` @> ™1ͬ#o( å"t^28i 04o5;@!"IT_#4_]^%L;@F},{ƈFyMüyˎ ,~RԝNUM \@ XB@0c]CY27riuK䳺V ZqhY#@? -udF6ןnɸejk"+/]ܢ)RݘdMVJ^iqar) C,@h %*QIy$v -)}`_=2ح1'2/90ߝ3:["O_VۇNKlR4v'S&k(5~jl8k]YlGùGCR3⦌gⶎXb0CQ"…/}Ƙ]ff:AKiH"1#Ƿapd)ˈő)%ꃱsڪO?&HN)QD}ynbs#8d$7#QHL1쎝|d,{}e̞GhcCzP3m:=zk Ee>/XObject<<>>>>>>endobj -1966 0 obj<>stream -xW]oF|ׯI,Zl胍րFi!Fȣx yޑV;{w)Z $E3)Vq2r7w9?+)ɚ y+\Z+.( ߿nW((, *Q }U!B"fr5)$BAV DG[ Hu8 :%QtmJo'u +*|RtE‘ -Cqᡐ> 8k9 n3GFҤ5[ 4!8.mY#{iN/SϽ| -f - d=}^>/r 8?-,:.f.V@R;_p -k8MON4L:4/3+A|5/С0%cwu`WHe(43^d)z0Qwbsj`5hr 4 cH=T D"Crea8qI8%[hv,q:K }_Ťwwv4Mlanot`>!T,耪)kKO}+OASyy\yw쀏H8h{d5Beޔ,s`FaImHuN^aBGd.-tG0`igW,+xZX[u cם5h-_"<>N G~8~8ׂ ˼=ksf܁GWMS YA~WB@R8fnMuQA0PѠ]IAPAzrGh2_oW UG$I]L ?$Q1!TgV:bpaZ03G$Z~a CdNo$Ƅ,/CӲNDDR*ψxqFjs с+Y?<}^dCPx*FSP`\oxЃ戡P\hcM?xk9j/ BqEt^o/=hg0gF!cki v/8:vFw뾓ďxr -cBĉ`cNXFS#@k„4G⨘vz)b1:YEZP"AL1LF9 n<)B m~ u)qbu]|,>z7|nYz?*HgڰfFx{K)&fendstream -endobj -1967 0 obj<>/XObject<<>>>>>>endobj -1968 0 obj<>stream -xUMo@+r b6`1Q)@%^{.Kpi/}3ofsRWJӌF9 $h<:çTIƳS qnLiJ)-JBТmG)DMNvN5F;Q8rkIOs+$aU׊f)hN%6 G -o{x$#(J{t>%cBW([R-EpeIkr4v7A,1oN4[KMZIШE}hJ׏jt-D#lZ;C(<Z ytP*lQOFz35`6'-I -%>tuuT}KlIJ%03諜)E2+ EyClУq\l+I%LgI6 vW!:Z6luRXb1}m|?ՆZq;k?lk|*Üx6;]F{>*{w Gј=ǃ+kUK/-~ iC2SFaC,c !mb+8oLsLوIR7yy_Lm0-r}C4M+| <&9W'sendstream -endobj -1969 0 obj<>/XObject<<>>>>>>endobj -1970 0 obj<>stream -xWn7}W̛Yk%yH0\ -BRZ\rKr{f+jFb]3}V?%h~MU{6-tjVhq{3 z^,~E9og^lJ5\Ҳ&]m^+bM,o/ ܾq,ΥJƻ|tAe9|t٘H'M[IFה$EI3hml4r3nC8+ UY#' 5q1)k0b:hŏ_ -32NVH.s*;C*&h4.M B-E9Mi,Z]$ևktFsk%UUX]NWݝrAT Z9` z'=pG"ûO0Gmp%j!@H!q*4zINW}co!+%v [ [9,F/11*&~=^d@sloW#Qnӵvþc b3(]a}z f6}]=y$C_rQah! dkSQPn#pbAoG jͦ}cF.2tq%nSL/glx;c)d>0n/il?2G|;GNR'\p[} Ȍ3jT#39Ơ/f&OJ7. O,٠ Y;X, V -NE@NU:;H F!(K*YvlEu` u!G31 3gVhr -ʅX&\6\'Q`>z_|9~/{kM`K5de -t4bYr:[ hLs6%47ݽL0ycdz Ϩqatj~!GŶ`kSEjk83;JdkR04$&|8A= -7 S^h -w+ad5t>ɢP=y׺1!Ci{/pIpgV֩o[!xLJ2T-˒qq9Lf6AUhEe!/{8Nt]7p<.CUi6tgw^4504 -whG/![8Ă:u 1lWbX*xm=^> j^["=8y GN{L?pf2x+S Y{7Ir P71|ooLM# -;aQ.h=Yku@5;Ha9@bfz'KeBj$Iә`K)֏hJ^1 qG -!Lu)Q;3 f[ÿ޼_q-nendstream -endobj -1971 0 obj<>/XObject<<>>>>/Annots 1133 0 R>>endobj -1972 0 obj<>stream -xVn8+@S %]443qWYmH IEϹ\?NcX8#;('eNz&)K\g+:Ex#_d7#I_,O$l_=DrhqFYFZ)b6ӎ%n -A= i:QUJebQ`؎R?0}@um})GQośͷQJl7MK `9UrcJq>(EI6]Ƅs{ Soc4YVCȷ/ql6q9|7>5']3$jadBmƱD4pK{ Jl!58(q6Xi+ -p>^Sb@=Og}zEV -ebqIrbk*QG2M?#/9GvƠ` q)"d֜1%lAm[V"DQ,1"(Fo?ɤ^[AW^/U$t{ϙ <4l/ڰ Eote͡Gl>m GPϪ!@!8{V9#j5i𴎥"q5:N=#Rgd -hUR5 tp_/ :o]+D hC:!$k65l&gܫ=Ny$:x0 [ʰkbk( ek{4A1 fvmNߟ[68CtT J8pk,ChN&]%uIB"@u={`HYaBYJᱞlSW}Kb~kQđ238 *Frb+v>~jJ|޿3<=V<`YewO\r1$Dt6_q6?G#Uendstream -endobj -1973 0 obj<>/XObject<<>>>>/Annots 1136 0 R>>endobj -1974 0 obj<>stream -xVn6}W e‘mQٴ٦vۍ_hHV IͶ@$phsΙ33?#Zi2 !V>xFl9=~\K.S9m$J(LJV-U%MUV{t=xЅwX^&vx8"TR4w@(rEAuDX_]|PmdMU8FPLHHвb, |/zFB #(c'#mu E&靬 -\Ԝ_D)č|Qd}P,/n7 9X]qM^a'QXE,$mV<ÐGFԕ% ۢ$tuھ5@3RjJHgoPdv4oX%ĩ5kKiG8삌FfÜRќJt>S#2-fIu6:" `S҉{ttChJ3Ɨѝ};AlQO"]ap 7MM]Lo3&}P@AK -k0\;R:8AS6pՋ5 -ӟLx;H=nʷs5̹qL7Bk -P̘v`Xl$Gn눧#ϝA×釙}%%AJc<2qCwD<:M- 'hQ'!'endstream -endobj -1975 0 obj<>/XObject<<>>>>/Annots 1184 0 R>>endobj -1976 0 obj<>stream -x}XrF+z*&R䱭8Xh@$H!&,%_sn&*OGW7i-w$//.x2sYN2sI2 zuw\L"sx lbH❋t25e"(ٌܹ -V 8K#i1$K v6 " -rvBhbi`+k05Ǭ Qeng3d%]"!3EV|N k0Y6a,rb\.R ٌ)2M3_$CvӮ^6MRAfG L2hX;8X 26bߩ3k1X24$Ex,V D֑3A L#i1X`65,*LRY4}UbV`(`qNY#.ys鴯VG>!pb`2 k0G$㨅(28S˙el(YicXTr`гfYS|*k_e}~YOe ;}~{>l 5#2,n,f^dY5}e FpҢbGb7;l1E/v?|~eG kV`//=F,֮`qZYAѮ`qi6qYe-kbߑ`Jk4 vr^]_^{sKh2=88YYAe fy13`Y.ZiXGfLgbX,fQs8,[y3.mH`Fi(+wHA>E!į`($Ae F *lwd-,ve f4F֗\`KN&fh80/#)Tgp6d*gw) -w !}aRS詩r$MqÈ6x>#=N!8xS{4}V(}hk5{+KP+_b_g%^ˮNKk~m6n[(m"Dq[<"mՕUA6f[ z;|ڦp®{bЃ@CżiVݟg58?|7׺z9'o"v,P~)WZO/=W^{-G)ǁO? -@b|'P=}WSD7aٿN2D]ԇy2,jwM6}551qeoء⁝rgnԷ?{Sh]Sˉ51^sF0IX^7$-=ʕ@apڠUHժ$smС9JcF$!{ݴ^&Zdtۢ+[̯nNj6f-C$x,Cɗ>/XObject<<>>>>/Annots 1208 0 R>>endobj -1978 0 obj<>stream -xmWrF+ 0ŎI99C (!=KbU[33 $ğHX\n!~qA(yg'Q ae1ب 6IҲ -$Hk`'i/@Wl8Q0Nn':Y.05$1,[z`0bM]gY;Wf04G= 918K5lV0g fu=k0U,1)}TDyLQaHk0زx`B]bI -‹3:kEܭLs*سl4F;6L+blְ;+rҊ3c-[ha ơkϪ.s@VlR^Ө򵊳cZA l9`Ӑ6*X)fְÊH.3ڦsUȬꌑy^A>|ŬAKff 6FR3lW* (T@59ؘFc3,H 7/!tr20]II@=d`A RSw:sbqQ̫ѓ. +l$UHY k0Xe  /  v]@DSd+Uذ/ 8 D39`3Ìr@W0aAj7SE8vS?E yvRL -&Mq4C4xbxIm( -JzJc#fCl%/ l%M. <~;|ύ?mn$wx#̃Cwh\Bܧ~ۡB}N-+tM0V;!m$sVLe~TVvAs\L;9]WcLW6נNjU&"vlyt<q9 a\p?TMYu؍C'm۠_#LWLj,$lsC4Miwǧ7VXs7Vpy<>ɾyiZ2B n`/8569U6x{8p4\Cf,ٷbu^ߊYi:vN wJs3^n{y^tkp|7/G8a_8zT8|P1FGxpSk:߶9CR|Yr ~۬Z}kendstream -endobj -1979 0 obj<>/XObject<<>>>>>>endobj -1980 0 obj<>stream -xMo0 n!%96ݲvAJ,I2 -׏v@fP`S"E1-\ pxJ,rV^ i r-YIDȐ9+f2dE,p.kkeMgyӟmpSbثp}c%$y]TC7r*ߙ1|z+e9У`Դhfᰳ<rK$ՁH ҲOVSF{˩xg& 󘜆赢OԦc76`L"z.w3hTU㼵 ÷U~1iУvM% *O^(?tސxS|IW*R2l7΅(urʽw{S=[fklKyxqi^ʬ`Y*) _g;W;endstream -endobj -1981 0 obj<>/XObject<<>>>>>>endobj -1982 0 obj<>stream -xSn0t16mfRN6]zNm~aҌڪ!k/?.R +ЌIR)g򪤱)M]/gڎ\dmN)* -u LsSPdםA[#9Ńr]tK8;u=I*I -tq~)֎R4g 8JZ, -lѵ/Ϻ$]3iL$GB?jZ*Y~ƉO\ JFH1{&&BM_ +Tq {^^9lȃzd.NlFe3׻EHLnm -bmI M^8^)+BiWvyQFPo?ɷ#endstream -endobj -1983 0 obj<>/XObject<<>>>>>>endobj -1984 0 obj<>stream -xV]o6}ϯS -N6k`-J$6钔]KuAs9\~9?S傊dMh>d __ ^S%PtU(RmcFd*ڹ*~glo \GhV ےN2Z -wY{W{4i~]Zs!bU6ʴ*o奴\QeMʆJXkeNA.dE6g[e{Ԁje,07yԤh?Va7 -=[XG R ȡzm$ Hg[XN Hh JS{ >hHZ|zN%[rH#Q),V{9$+@[&;P0.XAF -kˌ@jo7қGLU$}8'F|eAu\uږFwX؍ zXZ0W: )u؈[ }Sy`n~8gc+a*Tk!=`h|8as2Ħ'0#h Y"EJp6L{ Uٰptz|JoPz,$>gqUAQIG3O'G T2:]LAD=N?J Gɭl尉@b 0O7hXJuCrH.ƶZ`fA({@&C ,P9d>7tyV8[IV~SH8`J&>)TGVơuy8)I2LݧD1wZs$O$iCaXxs1{mώ!!HRc2}9⃤EC`/I0pI -0d ?+|&?;Ooy/)#nĴ!鐾#v娲:}yvłUY2# ЏNt=&oё %B4_׭">L25Z/)- Wt@!I -- g"JSe?\RЩo0h -g\VcJjā6( b<5\jM5- W4Й|or!`=j9@P>.m﹔Cߌ;SO47Uۋ .5.@'D8rqzPAg4R ʹm wYg(dd2?G1"n'{׫6F۸v~H{Y/ūדa Rendstream -endobj -1985 0 obj<>/XObject<<>>>>>>endobj -1986 0 obj<>stream -xVMo6W |iC v@Q J,n$R+Rq_7udoz($@ 3o޼yW3gF9-bJi4x6ܬܿXo&K'V۫46xmF@46ʒyM)ZMd)Ѿ\!Rf,L':#-I"M$PU*E3B7ZTmZЮD@a!2t,֟ŋrLIg ^j٨Jj'28PԘqN:rRxکJ!xyPICE 8{UqP W 㬶NVNw{Etݠxv6JAk/$SZ7-eiRF rZKnhTy4b,&ZFIK|N53+}:ѸU^V6Z˝q UEUmE" -[!+P>?k)TRShr@![ Dgֲ(#ҏ4-$UFjPP[tgi1_[! -Ej -0+sqѻ@PK5joe3h1C`"aiϰlAh6\ ;2FIK'<ބRpZ|YT$tf27McW 1f1%{A/%Z9thx=pMrs:9:T7*{Vʠ%̥ﺟlvUDHWr1c plzf .5dF7Taj-wߘ\=B@Ws^`tBE}Cl{ay.\Wn*$*)2ja|U0=4H=MHqQ2؎Xaڌ{D~-Z`ziY< -1tVG~OF]`ɢƁ7źF6W'(GnWB`4v`+֩`G'lТ5]˿ôMho{e P -yeΛ~ػ7 aytG5 Rɤq/xÁzz˫mXz۫߯endstream -endobj -1987 0 obj<>/XObject<<>>>>>>endobj -1988 0 obj<>stream -xV]sF}KXAeܙ>8yh%L?Z=a86k|OMH@YUʄy5f%TJ3<=#~BH)r} q:>׈+1]T7tV+{֑ȬJo-Ά2FJϐ`\[QOam.;ˀl)X'aZ"^dr'ʲ7ɴ 蓮Fbe!V2{'CzK@_U7s$*?D%2UBrNcd|ނ |jd4$^jȯ^%TEk9(ڇUe1Bkdœ\IS&URJ:t:i YR߁[V -4T9l!CV?~ܴ{|d$8{\zr|zG n -dpЫpŴ.>9(ygk]A^/ӵ\*sɮA_%R:CMGH/?-<ΈiC}및)Q;ɜ\MGT\<8R]qT`C@Q/p"v[>mJ]jʝȠϧa4*W<3Py/a\ sF^ , -( -0fx|Gq!$]2h>rah0V - C xRY"m ` Bטe<7PJi|ehv*鸩 p&:$xi!9 `UEOy/$v`uM$,HjiQ84\*ꁫ:UbG#~I .9ʩL9%]on)vTmsRȰQ֙M;91U/hw ,r1^{ BB18W [j:\j_)6RFb;8 -]vWq7|lH\G\>Zcgᾖw|}'cv8> -W&^U0|C3y-_^}ocS;9K鹞؜w% /rDFK|Esq{ G91㺼_|u:xnV= #\apvѿߛG8m'[*endstream -endobj -1989 0 obj<>/XObject<<>>>>>>endobj -1990 0 obj<>stream -xmUMs6WlOq ~sciQ: D"m`Њ}߂*FjEL 9BD$6mmU>8}#fM.틋-yۨ^ٶ2ZQUS7F#!\b I]8 :MQS'KEʦUP P>q%pq.vxVLϗ`:3xʂVEԯ3&y1k`^j\ 5Y8}bR^mVT r.I_eS"n) p9ɳB -+KXt͡Ǵ%mo勤͋o*r{T|:ϼJQU-2bA>/]\&X6Tq -LoZbb9OQ!m0D,L<\d%rO \}P $H$C`5@nf܈Iұt-H"zc$^:\{L& 2Ьe(VW?|M C~kה6839G'tewԠ)F_x;%q6qX{$z䨲ճc1avS郵0 ]V-i)WUƐ l SO,| )?镭`Շ)/)`@Ďʟ˘gSzr#D;(Tʧėth4Z =zT:- f ܙ@д]no7i_@!؀ޡ;&4(9HSQle:ɛؾ\5fq-I)YOv<=t;hl"Y|`XE6=B 2=NMQ G8v_endstream -endobj -1991 0 obj<>/XObject<<>>>>>>endobj -1992 0 obj<>stream +/wKvCĤbFxzR %,הJ5HUnE Ҳ&k )tUdG( jS,Ǚ\}"\ d(ؐBŢRZ`.pkĉݻLV.]qNi/jQJO.tq*e*Z&űXZ(!CFc k.,݈i$*l}To;Ŧe#{dR-\MP^u"A*INS-eBf YX{;8UW&QaJӂ.UbU8wCrs5!3P(VꤧS`cXUx~ogrbNT)` @> ™1ͬ#o( % ֥ dqtah8;kvҁB@%DFh.Jv̕XՍԍ>-N)yA%2m%X\票;o!@Q,A! a tdn0Ӱ %guFjy!Gڍl.?ݒqDx "q0Ӂ!e> N񣏆f01-MmmŘaD ^hi1tj#DcFooR #SJcU)N-~LS8NsvGڡF#;0;V;ܺxL6_yxj[ue=q Jw1mQ2.\x˔mPi#6kAv@#,?L14wyc"a}9e|1;7@CGbo[F 1>LCYx[\1$m)10'/ u2}0\oj1Ղo{6endstream +endobj +1707 0 obj<>/XObject<<>>>>>>endobj +1708 0 obj<>stream +xW]oF}W+PHQl+Jy1]{ء;3&aWl`{=`BcLvJ7 J8r-^fp8Ʉ69,niǴIjY^>~|i4]$3y9$㨔 <)LSfTTM[)jzΟw$tFJ/WmjҦOk~z;}6G1M2` )3PRkkRZj4%)$OUMuʁ|[4t&'Pnl*R2B❬P̥"[vيޟj | j>G{Pe"*+b&W]Q^I2(4jiojkBtDZySEަv;Q׽ȗ.(IW$P]Z}0TW;z +_{XXpw3yp^>2o%&E.jE!qiKLpzg& S(g 56CUpV!s!j|[,viaщv1+t)H%uzؙt?T]izre*С|yY|)A\OKܯPFg<BJ|@\-sFw栙"Kћ()E"koS[Ը/ծA0Xy^C +gX_' +$&fCÃLCT"4y~[vz\#ͩB#%H!{3NVa|7]*JUƚW JAљ\ 6`(ٽ{Qg׏K)2G7`YL.&;뷣m` Ws{) x>8DEbDTMY=X}/])|ʤȸ#}΋c|DaeD#G*g/3 +KNjCJ'u z8R&sl;K;mvfYBEX"V7 +֭_lcAk(ܐ_@:y6I<_ ƾ/,͙qfY\!6N%[g%~!] + +KLKᘹ5E]@Dv $^abvMIquZX$~5b\3TMOc'g}~k0-0D8P%[yk Ý;i|#}hyk1$4o:'D N&;I<#"AAOu5FBdyCm@A< + NCqpMOPC"#Bs6[髆 wq>ZDӁvv sf 2ư`rcwj@0|;IH'P1fX*~/A6攌Umt?u;"JhM´AXHN/E,W'9>/XObject<<>>>>>>endobj +1710 0 obj<>stream +xUMO@W=ە$@ 0 A,*'Ww#%ɔ,B!x8h3cuE#$zSqtz>:ZiluJXb<.MKW%Wa Ss>{ֵj+ +6A I([5@Ʊ6רkӢ'ZoTtOuʘ->wn>jCI睵F)߼!.0'^C͎l߀Ł7J=ػhH=ǃ+=hUK/-zídf;=~4m +1f ·պTWpg %ӸOEbn~1yWcZ`]Wlf>/XObject<<>>>>>>endobj +1712 0 obj<>stream +xWMo7WMNᬵ,;rH0|Vrv)-]rKrpijFb}p93o{3)~J|IUw6-tjVhqs36|9/?h6A7 :ר>jOt5xctz&Oɗn_8ZtkwPEl:ή%]5&uQNR15EG) j7*h9L٨ʒz磲1 Z5Oe9OqS[' 5!Èii-~Tb~VПqj\F5U>ƭNILSaD^qil-!7`jM{7x`$YwvOި'h:wmIUVRu@w/\Ю1UCV5Hl8"J`A>&B68@!@H{!q*4zI^W}rC֭>[r īPnxW#Qϥjm.}9|rݟv=m<;(2?C.l1-Rv,P Aч$mLE^٭ +53տL_e.tq%r )3`6f +YO >-_,2]Xso3}luj }=\܎u72aLZ U4Gɓ K,$Kp HV?6KդS}mkv;hxPWսkN&$S lZlEu` ;ͳVFUgFph+4$K`r8ȼG% IdD!Ge'jO-/_Zt#X&KVXP@G#v%@ʇ1ȪF(VHܰw29a^ &N>G tc .Qlkz@?[nېh:\2}F١cGLl&ad'pBa@afz9Qx}; X!s8DȬ'IJg:6Z"&d( |'=R= Aj:u];$PFeYt7v~4.i30~t +WӘ̧IΝ''b*Z{"lS^ힷ8>/XObject<<>>>>/Annots 899 0 R>>endobj +1714 0 obj<>stream +xVn8+@S %]443qWYmH IEϹ\?Nc؀8C;(+eNz&)K|V|%<@$>}ey<]'9Քgd=|1&ʖӗoF32bM37vt- tUmHN;ՉP*CRKOvԕ")ˇj  󿷕O =z+lRgS4)nZ\#&SZ}@A(O7&Cz[SeFef 4Q=!&T s [ʝmÏ0 U$:H[gP"g8EQ0J[6ИTࠄI2(0d p|ɭR.80>+U(mᣎx ^?ҶUyxKM%$NRmYvzebֳ&"_ ~@8l*m0Q>BR*k{[WHrl v֨pЁcE/ꍥ¢wC~DF zVg_aػw$[,'$pe&)G^r:"AfSD$5Fɠ9 !b>"J؂ +ڶjE*&Yzc-EPym +_$tVI 1F^l5H3A8xh*^a "E'.FCʚCm[~O}U+[cCb/BI9-Uqȃ(`sFj!,iKEjk0u{귓G4$+ B*z=ZЪxj0;ްa_@wu 6V:E1HuCHK)<֓m +~Top- +8RJ/9|஍cb('b7~'[ ?U2Sx;zp>XTg)~C7fp>/XObject<<>>>>/Annots 902 0 R>>endobj +1716 0 obj<>stream +xW]o6|X%,]Zi"I+҇{IkTEʊΒ}(N F G";_cgL Md'_^_LdN%RI(tshZ Ւrb<[&W뻗4:GrĖētp5M Uj2yg^{˰j:K&=qB‘@4'3j!߇32Y[SV BZJMYr$)M)xMN~rvHRZUjm=9CԵљ;* 3x.мqaZӇd!d%uf p"x"efI\xRceM/RRĶXN6nf[0`qo +@lA9wE U$喪8@L^Fޮ4eHGnzNUus eн(϶hmq0v Ͷ hds x:Rjxd00S4iApR8ᡔ-9,Jr=4XX.=Zdb7L\O߾yszplUAt~(iN3TxC퀛 0擵W|mRhT 9 <g.fEFq|"ja؞ysu zb+06?kxw5KH& ꁋv̼TҧmzU7t<C}O'D]#MZVUv$spCB_|(GÝiBFh¾67-/[ƫ8^Z>*hKՎ26v =y\҇ne8G7`"$AÀ)) ]@(SI's5( ڎ9r{D +V>DPx,#|ĥʚjj>/XObject<<>>>>>>endobj +1718 0 obj<>stream +x]O0O4<Z6MM<g'g2VJ`ZhK{y0P,2 +CVIcdG)E&׷Z;KT~W孼0F_R`wh?nl+EAܛoAA lq-: )6Ӝ a6E]dُ uTRpFG62zV,='roWXϟsZNσT&7VyӤU"<*@!}4]oF܋^,Lz>s^-kendstream +endobj +1719 0 obj<>/XObject<<>>>>>>endobj +1720 0 obj<>stream +xm1 +A >Z8&lf,,vfAaeVB |ϓ#[0jR~GWHiȰ+ 9{2tk~ۣ>EG%-Avk.$endstream +endobj +1721 0 obj<>/XObject<<>>>>/Annots 911 0 R>>endobj +1722 0 obj<>stream +xW]o6}KS V,ٱ<-n@Wlb@_hXKFRw.)يbC$2u9^IL3i|Ii5E3|s$^/-hM%2Jz qz;S8er z||byx'vfu>12Jsdܭ1wrl5egf7:M5m2 IqPW}$)UJI~xq&kdWRQ:jr$+ [GɈ67Ƀ,uSAt}MhCLR ⽿HPkU#cOut(^u颾840TgJܝahM3@ۛo3:kSTCUpl_0RIet%Gs ׫7N[c.dA#d^L~[QZMXLVʽU-=1\o xi ҭFpf=[I£(u}zK@֙i~W4ͳpTfpFxMP3+ {-=qH8*kon"mvᯛ`UsR&)?YPuxI9ݖ*-Ovj>bZl4͉rH6 &t" +P>A4"݋8-یES҇2ygČFQ,#Yi4# mݥsXɠVB?#= <;LC8}F(")KCi[GBĜ,lKE-~ke_fai;%B\qcd.13+tv4R/PGou8Hei2nY9\4apF+l>^Oq<"D>~Cjz9r>K(އщs4rw1Q[7[__EAdWbX*0>/XObject<<>>>>/Annots 916 0 R>>endobj +1724 0 obj<>stream +xWnF|W-&u$/uun,$/$7&RK mX0̙|=&lAIu64_\j)~o;tvu/b(\t6[l;w{t]|:ép_rrr հ9M&θjIԗX2mHP#i7^ ʤrlm{,"&WHJtU:=}禌!E)]7V4׸݊j#bm.a{(κPv,)1R8RedS"R!BNZչ/a{V&SIU,c779oӋ|Ik]Fש%}ʭ,uS9#.:Շ.!mԴ7\?oڮD90BբB7T* .NAtP:n49|~^4YJa\zu[I oY҂TnZ!~^|~6_b/|M.W,4evfEOucW(3] ?h:СWIY3btfe<45z{ExH_R:.)$<єdN<3ל&⊖!OHVhH݈ŧ +ɨS#n>ףѓ݌Y,>)W-j]+ھaH"!([P'>H7 bW t>BWK )׽a3eG N8vDW Җ ҃VYvO;?58gMNQBOyҏߨv2g>/XObject<<>>>>>>endobj +1726 0 obj<>stream +xV]oF|:Uo WIkiXP @q"WE{GZѿ쑴lq?bÐ%qvgfgϓ;!'}էpf4]!<:~1W˓Wc hF삖!OO˴w#esˤ)7;>ӟ(U-yWЍ.V&Tެ8K؛Iu|JSlI9@{s|O`(2n镫+|*TLak@bB shn?̙ܚ[]3BNL#|O_A%XJ"ٔt5_<_4~dpQL2GM8Lmch낚AnOήL=L#W)3 rh<]W)H;Ѓ\hkPX;/{r%{ĠpZMm5U::'˜FBhoVhBSMPzd8mUv9 [$r^>l;iր)CJN s(7D!U΂$̟9Y#>7Գ8j]i\ 7Eir +C{QhE?:hPqqi%n!ƫ,zPe|L^M,؝<=>>3[ŎrG ocbe*wejY4cA*+f n<z'Y%h\~|lLYO:J%.RwT%_w_\I H (mXʹ(wmY(:AqG0DNv~5aq.5zG 8i:cuUt [YˋE`ܪzy1?^Р9n7 !77Wsz',uZ&]Dr}']d>/XObject<<>>>>>>endobj +1728 0 obj<>stream +xV]o6}ϯblCvNm-ƆJlT2KId0(&yy瞫o)Ii1iFE}1NƔMɄf'qʸ0Bt~dJN8%}ܟ8Z̦ 01Cdy-.4^Y }.LW%ߋoɵ;T+a|omSIڊ{E"P/g?XA[C_Nz9Q0}(nA?ma\E+lױ5yHPm#qG3!Q@)xR^;k9J "pkAX8^PGhQ,Z٨&[v5yQps<O{U:Y+#QVJ`,}U$D0NE}7PV]R&ZT>/XObject<>>>>>endobj +1730 0 obj<>stream +xVn6}WLчzXk-4h6X%:f"ZrR/q&F"r8IOJcʫN,4h</{W. }=-% gIpkhip6p: V⨛dn|:$g?NzCJS-x:YA,|Od3] +b%Y?n»[uBŚb,Zvm9Z;x&+up4Q'J#Iij].TT1;a} A U"RVF;<8q@YGߟ;%Ŏʱ:&-%nq` .^.a`Qqe5 ³ҹ BԪd #^,_uGE! +eQ"Viǟrh>%Qȼ"”[*yJB!xόxd?ky.keG17TsW *)oıR-MSW\gXwMS$S%gܪڟJ9/lTt\=(šzBϭ72odpLR-RԎ!Ir(r mAi-K_h– +h"0ASAfȃ*˸4|e]araـf5JK[ V#ay*އU#3~`%!Se6:6GPyoՎ\oh{?Nrޚ?r+CؽczPyޅJ6:'7^KI1-wee +)\q7&u4CKIs].c utheI?e'&Iө;-J,q|}"1^ +a;n!\n90"hwxDśndCanťKznerSf[-sA잶04pL*o?:kk%.L&:ն?Pw҇B{p>/XObject<<>>>>>>endobj +1732 0 obj<>stream +xWMoFW̭1 +RI/+rEnLK)}$%I $Eə73Y}5)h5EJY}5MNgɚ4e:M7W/n^|Jb5mrB)ɮߔ |Н) +-aOoP`WVM6_4/7KͺD˽MipӀ5h&6>6^v鳱9|ڷWiؠ8a[&g:h@Gr7O2ZqMh.MI)RhYrj.^)tڍvhm]`On4=#̫;BYFC:(SG|s]QEɧ*D3Ԁ`.FJ-#@p$|094a[> !ިeZ.876ʪBˈ;K^\^(v:zb)%j/`(y@P:謴\qaPT|\?EC`038fzWBգĞ6**u%Š O+_s]<ڢ:F/~l AM/u!؅.`*xGQH:[,\36RЍVGfz 0CQrIqA_ Zr/1ulp I}) {XRD(n ddY5 + h2'd- }+7'>na>˘#Jv#U/_Z(}B f&2xv6? -p\Xa L(s6˩̨kϤ}gɴŮLeɺq|ྞK9 kϕH9^](wo%&)|UǍ}*ȢNNV"CIWKax-{{c ݎn/tUyaϏ^j;E짥9`WU!^yEGr𕊷xUa'^- +֠LhwVgc~%OLX<'$ 9'̤Ox>p4})Ͻ7;->/XObject<<>>>>>>endobj +1734 0 obj<>stream +xUQoF|WL*]x KEµ:pW{b/x9]ovJPp{g&_G`b:G^bb*-=U8e*||~c1/|cd9$Ǫm+KMXrOT៼~VXkroDLf#Ii*$ˊwRLD*u`gdM*HE8(A7:R;%EC<:m++*3b3UyA;pURRlB%LE,}i:њ54L+b5]T vd +B YQ2G6l zV\`*p57H'<R`kFts6.Pod#|+E~̂5M8mWZX5<[kϭt\rk[؆݇5'wI bKI@tG.^xXlWJ907lH@Ⅰ28tgʿ͗_Z5zv&L=V?A'o8B=˺}oe-mWfT;JO:q kLl#:Ä0G:Ѓ7|7z5G*mRdG=m\۽R͠EF5gg|;V^q/K/1 +ƺc(2Ld:ǘ gaTXZr<9Tv D12dʪ+r9i,H ùj +qbfcm\z$YU̞͗b~R)gG+Aendstream +endobj +1735 0 obj<>/XObject<<>>>>>>endobj +1736 0 obj<>stream x}Vo6} 8vO].C,<D\$R%D"%w޽{ד! H'd@E2|#YIy0]FI2~}urFZH2i &]D奥eBKcبBÛտ60n;zD7ёф*dJ29U𹱥M$)H%ok*kxrǂ88N=8&LMY 6LhʴA9癫dr"'c.F1@QPޒՎ9.%^pT:$ Y?|O,#UV,%| UhkM]a듴}Ϝ a3ZvT* 4Y8 +r?7RBLU!\?<{ l<*,<7˳f`*+Ӣ@(zq19s'gjhT8ƩX6H< #h C`g2%(m#7\QG΀2[cfY"\ yWth^fѕ̤5O-!&Yf*[F'g5OX%gj2Hڦ)AMHG<8+dέϯ"O' B/[J0PKf/')OMn-kv蚮h2EFOh+X8`gQb2ʊ \]-K0' @@ -4643,19 +4081,21 @@ M' {O 7/ຂoqXywއdlԲ9P&sQhT]t⺝5]&];0K6'T-6j.~y#i7ǖU۝2÷W v~NG,96:@yTѵ]DJ)1:ұ:U`>^Lu7ށ[l1U%:wޯb\l %D_-.ørC}4O+~٠"d`?YC 0žO'tL/Fup:V'`endstream endobj -1993 0 obj<>/XObject<<>>>>>>endobj -1994 0 obj<>stream +1737 0 obj<>/XObject<<>>>>>>endobj +1738 0 obj<>stream xV]o6}H"ɪlC6@AKTĄ"]CJrg< %܏sMq$HiSLeS\iyIN+WstΧ=Iw" HW5[FƉ/u>/XObject<<>>>>>>endobj -1996 0 obj<>stream -xmKk0stV%?dz(*(J -"VvY^NG HT]1HUNjh !D*]CWa\||'/L0J8+^δFyS)QLsp&o]2=^y-mםj'L cgbr52m>/XObject<<>>>>>>endobj +1740 0 obj<>stream +xuTn0 }Wחquv6(6kLw$%Ems!_R|2ZTԌ4IE *O7튲%jUFuKT7*Nhg \yncDІM}aҺwZP<N{q+REw19;%_F7)y [b +ڳj)F C(v^, "JHЃ0>HG=2ԋӖYdxxt?6oQnc3)c#YF܄=8 $GRQ':gBI;QXRڑ@X =R;#Z&r t'1qi{K#g<~8jIZ C=@ky +N?NHd GxI'z-yCn\ =['p/ы`Ö ڭc12뻯@yϙ N0M0GvO- c0 <55=fϓ[^RWѸ,h Uq +<>|`8$|(a뼚gǮqE1Oq= ZwMT£ y3eqdztWur7Soa?m|"A$$yv8F|iyd%aUPYYӝ?qt T9|LW;e9g M=<nendstream endobj -1997 0 obj<>/XObject<<>>>>/Annots 1219 0 R>>endobj -1998 0 obj<>stream +1741 0 obj<>/XObject<<>>>>/Annots 927 0 R>>endobj +1742 0 obj<>stream xWn7}W bVź䥰]_)q (+Jb%7K{\I òKrϜ9C=~:4Ro@Y~tѠ7g4gLJߎ:dLA2I~4 #,Ω7īGɰ~i;wus~mȺ=,xnr^?mw繜o= #1\DeI"O 3'WL)JNg_O:O;JdRz/@XrBe–ʚ$n5ΰުO0t2޺6/,Kft醌]JHU@mɄrN^|9)y3ju1l%7<%ӣ2sv4>oG.cQfGKV~Cʹq]xU..h]*̲YG"}Z8ҁ $ @@ -4665,16 +4105,16 @@ _ $R} yp]o ~ᒩ7ц}U40YX3i5zK*2R!)\C9>/XObject<<>>>>/Annots 1228 0 R>>endobj -2000 0 obj<>stream +1743 0 obj<>/XObject<<>>>>/Annots 936 0 R>>endobj +1744 0 obj<>stream xWQo6~8e)PI`HZgMѤY5a%V+(~#qQtkZɻx?1M)-{1/ϒD$[A^2>x,&; 1؃8, N&_hًG'p2,ix<;6^$p1EhD|\ÁHC̆RR({YW4CmzcVic)BS (#yv45d?bt98( oݴik5kD_+EyZk }8kJ'IM+8۲6ew`rTOQvvDj袵8K"A3x]7`*kSMhEOT Kź) 4+X(eM[Ȣ 3qR+Mtص*>,o<y>M`½ifytzKf8ZHaa2zke_t H*iO28i+wo'aV vk,0hh@-Tұ*;/SfOM`sm2&rVPB`ѮV[Asq{35Zgu;eU"268|StV2;ƞkWxCA(ih[eiV!/" q= jIviU=dB3Ljz}bǚsSִu6>i㫛𕡑eC-@|͊GoY󯀽y%t?*>M$YWorvysʑTP\OB5$!! <B6BORp]Պc TiYT6ϨMFjZVE˚RB>7 ~> ꝳ83х&07c@r׶SZ+VH€ۻۻOtEvݙ[WDeo3eX{1bzRچl2l: !)إ^+y b|kY<5 X OT˪6GYN՘\ }A;ڗ̞C_-hz*>tJYË.w\ݬpgpd+KO޳'vϱ9N6֑c+<nfi]#;tdݑ3ΫqAJwABߣ?&t.^n YGM}{ eU:G(3NF@YvquwT{j04PnvE ӦE}n__~ة}r;|<{D>ʼVAZu&װa1Žeh^]c 6=w^䘰 Ξ[&Kvam>נXݬ;"a!w(&DP7-Ln4$|3xS)2^YHC|'1~s8;sۆozkҶļ&RF8 0?_$Iޯ7Xendstream endobj -2001 0 obj<>/XObject<<>>>>/Annots 1231 0 R>>endobj -2002 0 obj<>stream +1745 0 obj<>/XObject<<>>>>/Annots 939 0 R>>endobj +1746 0 obj<>stream xWn8}W R/K Cb;Ej,(H+Rq{DȢ#\Ϝ:R4QDaz:4w0b1G :×.7yJy*x⍚WIz@.1MGNeo%I'͒ᓡ(֐)(6yҡG;⤁FF$2RYTfV$T6$YMv+U^+ί/3r,s[+Qq4w4Ǻ"Y%1;2J쥵a^3BfޙiUi Qaۆ;k<"-H2 0EhS >/XObject<>>>/Annots 1238 0 R>>endobj -2004 0 obj<>stream +1747 0 obj<>/XObject<>>>/Annots 946 0 R>>endobj +1748 0 obj<>stream xWS8~_ӗ 3O: RR[!*Zv)߷[ !o|E7iL %y/ BN>{W)i87`Bq(t̚UFWAhrrin蓳 ko fޠ|S`Oaw؁488UNn9r1,\8fx҉w~DQD-Gn2*u ioHE%>߮>/_G/cHPk,l̏V^G? T2LyLz쥏1$v2kT[zI7u{R)KLReHi[,j'ec{@Nle z4uUSZmir }6$WR2BʤPU|)uFNT*$Ȫ;*"[HEǨS(DZ窖Ճ)IKuۘrg`ـeOޟ˜h\}8ҩy(H)-D OQ-DA &Kkm=zPծut%-b=( @@ -4694,77 +4134,47 @@ x {F`..3uBr8P2s[\ EOFa 1x$b6#S:5ȼkq>/-܏jF>M-qlZs OYaCmLaNx%esRkkppg@ډ7LvheT ׊eͶ$wm2{1avd_ِ&#| ;Wr(ڈLAͦY9gdL] tĚ.WOMendstream endobj -2005 0 obj<>/XObject<<>>>>/Annots 1247 0 R>>endobj -2006 0 obj<>stream -xW]o6}KS V,۱<-n@Wlb@_hXKFRw.)يbC$2u9^IL3i=Ŋr2fIYE3Z-7цJǫ{*q2|"Z NV[X.7k=H&uw3tuNl'f|[EY6Իo6jleg1g^o'7ouF ڦ|\EEѯ%)e -I~x%q7pM %"sBUrIV;AV7&:Fo[Ɉ7ʣ,t]QtuMh/BTUE|~$mړ*BwtKtQ*|Hi-=Mt*6t19V9&qH94^ɔ#UˊduTFW\rD?Q9}z110O+4BE䠪t K/d XUzKKGan33yI-tFAESXxH$Al% zn3kJLqkL7UJQ\}si$G,41|2 EHrUud]av#ZCڜ(dloBx!P U4@-K{ IY> }(,oʡw}K(k5[qd8:gALʎεúKcյ9a1=` -06˗/3E\(`xJt<\UFA &B+rT<=bh/2GعjnRaA gT-:y:8{D0@8OHjS7řxS -6ƘOA6%3J -'r~$9Ze.H*fDfU.>CiGmэ]bHDeR쥤5z/ B3ﰴ!F62):tx^z(Wѷ:$²4{wA{~Ȭ߁@0c8X_S6oS'h6JN "PM6ý.{cbC?H#s-׈݇Om* >/XObject<<>>>>/Annots 1252 0 R>>endobj -2008 0 obj<>stream -xVێ6}߯uJ,vM<MFZl&7!%$EAH93x2ZN)_P\M s]-;+ =9ͯ5-⪦|5|HgͯnXݓuCiS,v97Vޭ/ge8jI2%|BX6Qp 52Wޢ!U/)i@y/5p0(-Y3b:YˠYLj2 -*S :γt -*t%4hYwE`bsG2{Az$jgH~j@D3bT۳5"/3یY,)G-чtndHFht+P'a>J7"bEPG WRz@>42H "` -)]d8=tîaTN{PD\&ԸN *躮kr7teeڠ@Z}q J#]:BЇR+a`il*<:v/ځl H>J Nl*ֆXT) ~Dlh.g\:Fv6$4CG\iqXߚ.#hHg-2u^K'B؉; -%<q@p;'H*BK'JI]@>Ost|)Ivh'w.q,~%Ԙ`"dqf#"ўq+ѦFJi ww`v c4FFzy>#^L\f>/XObject<<>>>>>>endobj -2010 0 obj<>stream -xV[o6~ϯ8kb ؃Shvc-R6kt)*iCJvn!K]o' ,єdi2sg?ǯSTl^z(ѪD|F+I(<Ҫ8kWe]e']A-viZ7t[o']ҽmI`vqBj:wV۶[m ْED7[OFUoig]L跊l%C Nq/CJQsqXk#V 骢*gEW)r"+õS ]Z;.ʉ5 Mbh[ZD!AR73S3(Q{]񺛰0VR;Uxi{d˙Kr"S-ohFaň -Ȃ'$pܣn͎r.Cvʭ I,ZE.F`?Z P XQ-.;u*|gBp-fNoN_h(Ɓ݄{ƒs!~ -V ң`ZѰb~ȶ >A>/XObject<>>>>>endobj -2012 0 obj<>stream -xWnF}WL6)Al@.NXKi#K.-{feZndzw.gΜޟ$4OB!'h@ x>!I=%3FJZa%NUBNz)Bl$,iS Mlȼr$hnQcQ&μ@&}qDT; O 0Z=5Fc(E *Ikf3!Frֲ]ҭuF"dwU0FZƶP+vTj@qߨt_VrJ(_Uɔ!P!|Aw '['9h'Zobr]z r x\Y9RU7wglURԶ{7pPo &͘L2Q"vi T]9c@6ܱɁ,,V1YJr%h7Y큳kG})4cchTkU#^r[!d5SA=>twXGpR2[)nĖ7^*}? 0Ϟ}A`VGK17Q;#@{/瞟 m%8TQB:ƃzB|d3FteըL n>sEj(XFw^y_ַSGPel -8諍Tt~k4YE&)M`ڃ=N"N'̝Oa.8Q@3 VI7&а0Ύ@Yer(;ps@CaذHW -a6~ -#/ Ȓ*VFjE9K-F';Z-2 @edi(tE#˸D%'Wugi,[O$+hHSYÜMx 0qWڄ+oıR2.t\i[sI 0뉇_U~jE -Q;Gfz޶O2|D J.frw% ^RെwWgvK/ B2Uc$endstream -endobj -2013 0 obj<>/XObject<>>>>>endobj -2014 0 obj<>stream -xTn0SBb0Di*5UHM1d!yy -<I% -7t Wn55K|]rIPT .ZE.(A,Vs?<{8\*?l++kJ7&$8i}38 ^"{pFI߅LC(w`{i;w 0D"19JsLN:=ecHPz -gw׹B@-P?Gg q1Jm[ȮbYUdzjP>)FϷYDL _b+~*Xl:tK箾"EOcg.5j>>&ͥd-oxma9<^촷FH礋0,x) m(eIʂ(5invQGl(aׁyhЊfyϘD4Tpݳe$?`>Xu0}'A0I$2O#MSBp>/XObject<<>>>>/Annots 1260 0 R>>endobj -2016 0 obj<>stream -x}Wێ6}W ڦi}hEbUZgHUA.̙3g'sߜnP^Of O?LlK:[PM&[w>M֫lE"|x'/ٚVUzyt'/ -oWZ\8r2/ݰlѲ--f+fK"'կj;$Gn 9_ƕRW0gG-a<2<{ҞYw$'ki+u^"v`Wѹ2NU(J+nOA1tMTsȁd;ݾցEFb69̤KQ/J%\5'ܷO(1a%cPEȅMxryvk[K?!P r |yAGSGS=XоNϺ1fQK--p22;}M4+n-/J5JeNYS`I/! -bp,d35&1Xk?""sE \؇VZ"OCA[AOq~a]Zhuh'ډ=ZjԾMt`΅g4dJ1>jp-HDT^dJKrQz_"l -.JapF:(hKG -S3P q]-3z3<W,e -0]b6{J@+GBT ֱ;xB#yhQxqXAH:V\6h.bR~2n>#XփA\Z>/XObject<<>>>>>>endobj -2018 0 obj<>stream -xW]o7| -胃؀M@x'FwJ,wvyg9EQhO$wvvvvɔ&gJ3/)oN& -VJa6/0 'g Ni]"ruAx2u>jT1V߮LtDu1Zo4kd2}_,ծZ?~7:{h\ho"Lz坸Q6*P6肌%WsH$3g̃8ȕE5"eqo[@AA|WfLmD: `Aխf^+ZU;_`*kJ+CSJX'c^\#ƅi/gmԁd5p ܘj=2ScD s)zp"Aet:y[/)D_Ww_V\ X\ήfIx1&!U/ bdܔhܮn/PCP -^KD-cRWzkNpT=H~RȷւK \wʘE\5 -)UXKrY8+& BRA܍z{/ wPѕ!ꆂ+#7pĝړ+W,!}JT5 "@@G-*8@Ӈ 69FZtvP5!cn~VKqu[(HWot>9 \lhhs41;2%\0Y0P| -ip;+"H⥨ܓ4POx|nvWA ~9xQh€@"ڌa?Zdn@4F{L6 -$&u,Gu W8痄5φVUdI=;~y"\M&<$XDZnЧ) -g^CHv蘞G2bj; WV9uiSze)mΡB{D_2{~I7@#bkC {Wlղ_"|_Ck1^4G!y<0TjyJ$%R?b,Y)X,L~T9OAԙ,?X?Nk綢( `ٵVDV?epVtu`K9ѠbݼM%zm02B \ř~ :r+lNkDl-ZĢ|4yi~cǶjcGb:d~6;?xaF SĪQT)0 >[lFz2fGsmwVứ<ޑdGO'}z7ӧ~u:b7ҏC=ې Da!B6XL%B\s3rRHPGk&^"8:'E-N~2UmAȯץFLcMKylp Ui ;h8`/XvHfڟѸPG[ -ȁ"7sV}zI7)Z'2q}<NUXۃ<}|@5[t=|$0zթr_9-ϗO.w߰+Gc-VUq_8.j>/XObject<>>>>>endobj -2020 0 obj<>stream +1749 0 obj<>/XObject<<>>>>>>endobj +1750 0 obj<>stream +xMo0 n!%96[vJ, J2 +׏N@fP`S"#G.d8 Qbd<]9^Q i r)YIDȐ9+d2dE,p.knKeMgyӟV=xmpeU^a(BH򺺭nU3#JcZa! +RA˶sGiL]͑NnK-Tr#%bң;^r*90yLNCyZчlj0vmȂg0ϥjjt9WjV[}!`^jIK(9s=z8l״dA `/=ZEASƹ0Ȟ 䩩{7ܓhD*StK7gTfRAOaxqWFߣWendstream +endobj +1751 0 obj<>/XObject<<>>>>>>endobj +1752 0 obj<>stream +xV]O8}W\Haf݁٥J#I<$qv=-%B@{Li)]lNEw0&t>ds:~JLyNizsvxs贽n=->QT(R݇T)T55pUdn[y7vhK;YDj ktv >h(¶ BSg}Ū4CiUKq=T+Fb*, kToqruIߣ8f'K{9wyX^ HVo;5-x:ƕBڀFRiTr(62wIlmԩM")m[i*0awҗ#? )Ow:z0_ހvQ4Tk1K7Nc8 +/ɛR: lz'#eFX\}L#rR{ twpL X[7xR/u_z `a7.Acjq]`"\i{Hq`#5A+1#'n:z +o*H'9LvL')uyK~;/fCV0d"x?J1No+\B Jܗ%笐1u;i}<9iVh'P9$`v2EnZzt?+~xԁ2@6_2a8mhޏeT{"Dp1dvp$NqzDlEi %6XT1dwyVؾ| sH8`J&>c)TGpVƢuy8)I2MݧD1T-%IMSp.0,q>/XObject<<>>>>>>endobj +1754 0 obj<>stream +xVMo6W |iC v@Q J,n$R+Rq_7udoz($@ 3o޼yW3gF9-bJi4x6ܬܿXo&K'V۫46xmF@46ʒyM)ZMd)Ѿ\!Rf,L':#-I"M$PU*E3B7ZTmZЮD@a!2t,֟ŋrLIg ^j٨Jj'28PԘqN:rRxکJ!xyPICE 8{UqP W 㬶NVNw{Etݠxv6JAk/$SZ7-eiRF rZKnhTy4b,?k)TRShr@![ Dgֲ(#ҏ4-$UFjPP[tgi1_[! +Ej +0+sqѻ@PK5joe3h1C`"aiϰlAh6\ ;2FIK'<ބRpZ|YT$tf27McW 1f1%{A/%Z9thx=pMrs:9:T7*{Vʠ%̥ﺟlvUDHWr1c plzf .5dF7Taj-wߘ\=B@Ws^`tBE}Cl{ay.\Wn*$*)2ja|U0=4H=MHqQ2؎Xaڌ{D~-Z`ziY< +1tVG~OF]`ɢƁ7źF6W'(GnWB`4v`+֩`G'lТ5]˿ôMho{e P +yeΛ~ػ7 aytG5 Rɤq/xÁzz˫mXz^󱟷W_۰endstream +endobj +1755 0 obj<>/XObject<<>>>>>>endobj +1756 0 obj<>stream +xV]oH}ϯ⥩Ը!%t68}==wl Ͷʇu9ד iԣt|4 4?#i]Ň +Gk8)J~]~/LuETٷX (A8.JNosI4Va mLm#+S_phc4.d^>G$(1"N~x2 {s6h,{Cֱs*K xhV-U ĩL{"Eu&oe7ςT*̫Y6+ ZFT;C"O=3;HAF\om n(=Tǰ_١LmDj5meZxpԐ 5? ,(sD`/+Z& ,d"2YύJRA q0NԂ9 5%x߲`R` æؓ;%#rsO?ӛ?botS&^KuGx@i;[z1Zw5-/?)j:BzyMfFLwF_]LIJmZZ͘HW9z1cIҏ6h#eemNT)ضPD +M>xpT6t _xZ(3JaQ@V6=8 qH+肑F>@ AW_j@>/zvF0BI35^^[,{dvBrx(~O+s Ckk|5TTOM]k4 K$5Q&AL/b~{!f>7cS@obiiAR[jˡze=nLV\UUAb-F< 6NyvpVON)yj@fSLզh\-@ƌrF乍[, QϿ~o ״j4$ɟ'ɓendstream +endobj +1757 0 obj<>/XObject<<>>>>>>endobj +1758 0 obj<>stream +xmUMSHWBjc1lr[]92F@QfF8}=X։)(i=u}WLҜn!"AYG6k*7}FqL +5KB/.mJzid۾~׊:GҾ1MI2sS5uT$lJY Ei!hQ +'ʓ%.'?X~sQXkJe}L  G$55zA u/28[8L`p=F)89,&4zp,Ftj}s^k4%4eZ>\ "8@:(ј_ +aP}r!~D9ѿyf?'rL~||I} lcF}ܒp`j& + 0M'хxSܛ + 8c€š4V|)Oˊǐi7%s\MJz:|7״ D6/kQ^INЗq[o|Zendstream +endobj +1759 0 obj<>/XObject<>>>>>endobj +1760 0 obj<>stream xWMo8W z,P˖N6) #M({%*UoH)p EDg޼y3qRZd4S^M NO%͖ ῕TtdќHa-Nq[UzB } ">w7w)eZxlXҺ D5}%Z/-M +INAy%[}o.tP1ӄVrLMgiHlRiIiP#ALI^:hg:EC5yCwBBxgCXN;i'em%"E+%0c F$0,a0a@ 2PJU">[Pt\_۾[2}=hcb -پ0<꦳"NX QRP_;/t6mr,Bռ9z.hW}q5jH,M&QҰ!GeOQvBi`͗L}endstream +پ0<꦳"NX QRP_;/t6mr,Bռ9z.hW}q5jH,M&QҰ!GeOQvBi`͗L}ѷxendstream endobj -2021 0 obj<>/XObject<<>>>>>>endobj -2022 0 obj<>stream +1761 0 obj<>/XObject<<>>>>>>endobj +1762 0 obj<>stream xW]oF|% `Ӓ?yW B~9Gb-wvdIhyܛkgDC!RV\Lv>hDh04_TSfJ9|ÆQa03]p/em@쾿m>|wkSvMAK!폎C$:m.ГE&'^khrypsOa&㩶grNg\}Pe#irlH*p$Z뜂%lqzᨳund#j87:`@I@m^=ijɘNea:%țʔma}*(R[R{`f{"ǫ*U8m&T fE;{VݣKozU7tsKS\lEtRAmk9;*G!ӥOy*)DFHQ/salB_wTA̮) *AH90T _ R{4nf%sy"eAl7ip[>ykf$4 ^ͬb^>9U%y>1:>s_ht2tI*}Ku2~D)m;zAiOѦ@Fe[ks[;@ AHn t%rJ^z["֠{4(0($ZIp|t-= Yļc~AN..:{FDs0͔Ãf)g'ԢUwFR"_v[(mM .N(yUwBXy2!RY~kr#KqM`;ju^ڛI+Iݣ3“6ٽ yCf~{8Ո{0c}FD®&l巴Uw=1.J*rK[ wڪsJW,zڅ.Ue='BM]\3Al?jH3u'i^t@o$zsiW2Ba**u%f+ǁ243vCޜym,gyÎe_BX$jD^?ӏ~^͂`]幆gx@w0^z &8EuSqNgdS"Xs JQœˊk.YM-!mll;iė@llvfS8OюAD緷]dCe2L`bH6,}m)*-hY(8T}=s1&6*Aբ :0SV*BAqП#j0e{Iڗ[ *T@*W3 ?sȮYKK2B11Kd0bɦx Rx|^ҋEt|X^Y}⢵eUׁmZUiss<&CE 0 KQsWCXX{i'U4,+4ԠmK]d: -`i5]'y^\ZQX.XDZެ7n<jVLrcك'P0:X\I`""mx!9v(&X.op#p2B5alA'hZ2 ӓC4֏Gzߝ@~endstream -endobj -2023 0 obj<>/XObject<>>>>>endobj -2024 0 obj<>stream -xWn8|W,jٲ;I\4q(P %b#*I,)ي<$QLcĴtNIqE4 tR/FfǴ\邖)xLdpVD]& UZ%%Z6\,9i6%V$zUD!=4"Z-DXzh8ar8{wX ʄS##Spk0xhDe --Z\F`n`!Ex3qk Vr늆t~Ϳ7tww{"o&:Oi*X+.*xlX+a-FHL*3F~c|:ї endstream -endobj -2025 0 obj<>/XObject<<>>>>>>endobj -2026 0 obj<>stream -xXQs6~KlKv:ӇMn2snXss  (wi~is%ɻW4*˛kZe4Kfҳܛ7,ZEg2kë~s-SiRN[^yc`5;H2G8 -IQ]R55u)QВ6j]aU[{ÞJ?jm5⠢~wCm -˽{/{mA?MJ3R z0fc-tDeK[F ^}ezLI.@ZʌLVf0#v";J\/{~5f +`i5]'y^\ZQX.XDZެ7n<jVLrcك'P0:X\I`""mx!9v(&X.op#p2B5alA'hZ2 ӓC4֏#~v=co,~endstream +endobj +1763 0 obj<>/XObject<>>>>>endobj +1764 0 obj<>stream +xWaO8ί!JOfvi?-I*!oݸ$qj;l;Ɇcό߼y3y?1-4SRxM*1[DϏ#u|{M_ΗǴ\邖)MdBLi'RLjKJDm%Pym$5LYr:m&KHB{IiL82ZhBx0HS#%+SƒmU&s)9dryp4kHԘ[o{9m#uG݊b%(OL9D­=&*UXm?e4]W8`%htNW^{yCwwg."k68N׆%4HJ$mytiZ6RWdI+w.NL# C4 +KD>=H'(Gk 7`B*dqΕO]?N+08Qۋ}.A. ѠzudhI t *9vUˆB`A@ns\DӗwĵLII0"GlbTň @{ɨM~ASH=h<96 Ǒ'Fq| +Z8p?F]suiI|Ŷd ?C ۧ3`_5'n dбnp^?^Ӡv +FP i o.7C 5KnCY)9GUW4!VGY?'Os}NoLH4}^.^3;2 +P:2Aj4f'_YuPg|,kQOdV":.VtOҭ5P˴um!Q+JHDn^QZ.ɰ5os[ɺ08 +a'ۡr +I+Z@W8g%Uj!ݽj>YU\6 +H['{-nzDrYy Ӷ>I 0QEtKp$1jyi"UBTiC'My: [QWkX=.8oXjs ߴWzoze-x2y.$5giǗG3xJ:M(pѶpt.#>3 ^,T 3P\>kzk_npPoE{FOC\~1q`Ǡ5kПYyHc\۫kGV,Ak0Rg0+\:Wy U3 + :UJ]B{^"?1>/XObject<<>>>>>>endobj +1766 0 obj<>stream +xXQs6~K,[v:ӇMn2snXss  (wi~isŒKi52%ٌVv]Eg2kë~s-SiRN[^yc`5;H|\#Dz֤._tFֺɨ_b~hI-ԽaOu56jqPQn +~?ۻ6 [er^z|[Och!ag^'tn >QҶVQ={zwmR 2c4SULz]W{~5f _خh"_ZںFV#JGR g<#ݦ vQ ]5u,Sds+|4u]ʴ {NKUU;J%m0Hi;"(DxBH{ڰ(dW#1X k ϥ#שyv[Vd) B7pVM8ͬ kLfq UT^`RϪPN{:0Аg$s ԗ՗\Æ"hUk2gd]G9EHu e5U׋eKL]q]HO@nku Zp CMj*4zu^pp* |66A=-E]7׏o~ P|nWZ^:X T&RI_ d yxVB}LQx}a<8L=+>Hwe - m#߆TDu -ъ:Ns_P:7dJ QUַh_OQɢ!{Kӵ 0dGQ+i@%̚'"h*5tq" }1yזiJzKzB]vN3 9 fhq+ Fv :ϋGDhF7t\*o߲qrU>d7W)k/bE\(IvI0[!jD+Vm5w1DLn2-+ـ`wBp^4gZ_{%&M!H~f@ч3@X7t#T:\^" :v,>f6]>s= X!;N ͑)+w&pmbL5:or&Ӧ m댑\`֡ 0{ eQïɑ2F8yRXBgm5!PeaferϾvq(@a~|\=BFWt8*O@{5Nbp+ӚRS{(!:fa6ohY}"'.e?2džWXxYw`0zJw;d7dR@ra4Иb͡kOVup\ QP?H[J7z&S UdO:*u^f= -]d.~0`; }ߣo=XY@Y p^'蒓r !׎n6etgW;0Ƹ21WH1w֐BBw*'#| v8c"FxB#c2(t5dA@woXͯ%-g?| 6j;:a=B5%n+ O|wajy,Kf>N~; ԃQendstream -endobj -2027 0 obj<>/XObject<<>>>>/Annots 1265 0 R>>endobj -2028 0 obj<>stream -xT]6|XܓԲY.W!&'  (bN"U:CRw} ݙ?3F+״IUau[uԄ ,ٚvY1u0c9 Hȶ]燰rcT6!q^쩬#J1FuzQZLPeI$'퓴}1%Oȵfj %ctSΓiޔg+Z J(9`tFN>:7ȋLFKBA -(YLW0&RxNZIxkm$:%q2k((=q[2$OS5 9PoHZ VW{58LvZ#}Vٕ'y3{j#mHjaσGO:|?'x7B= mM-Qf R+}@]&_OTOϞ3 /&#Ѓv_~Eh <uxp/UzÎv|-s TeW!Y,/XhHff,rX [ vσ7lуW]̰<~1=ڴާCe@HŁB%p4"KPVM2{_'0^MBh ?)f\ xfhpo`a(8W1Aj)r+']i[&0!0AdQ~u|ad:-6ĊCw5ߥވsUMӁ~uѶy5s(̊<} gendstream -endobj -2029 0 obj<>endobj -2030 0 obj<>endobj -2031 0 obj<>endobj -2032 0 obj<>endobj -2033 0 obj<>endobj -2034 0 obj<>endobj -2035 0 obj<>endobj -2036 0 obj<>endobj -2037 0 obj<>endobj -2038 0 obj<>endobj -2039 0 obj<>endobj -2040 0 obj<>endobj -2041 0 obj<>endobj -2042 0 obj<>endobj -2043 0 obj<>endobj -2044 0 obj<>endobj -2045 0 obj<>endobj -2046 0 obj<>endobj -2047 0 obj<>endobj -2048 0 obj<>endobj -2049 0 obj<>endobj -2050 0 obj<>endobj -2051 0 obj<>endobj -2052 0 obj<>endobj -2053 0 obj<>endobj -2054 0 obj<>endobj -2055 0 obj<>endobj -2056 0 obj<>endobj -2057 0 obj<>endobj -2058 0 obj<>endobj -2059 0 obj<>endobj -2060 0 obj<>endobj -2061 0 obj<>endobj -2062 0 obj<>endobj -2063 0 obj<>endobj -2064 0 obj<>endobj -2065 0 obj<>endobj -2066 0 obj<>endobj -2067 0 obj<>endobj -2068 0 obj<>endobj -2069 0 obj<>endobj -2070 0 obj<>endobj -2071 0 obj<>endobj -2072 0 obj<>endobj -2073 0 obj<>endobj -2074 0 obj<>endobj -2075 0 obj<>endobj -2076 0 obj<>endobj -2077 0 obj<>endobj -2078 0 obj<>endobj -2079 0 obj<>endobj -2080 0 obj<>endobj -2081 0 obj<>endobj -2082 0 obj<>endobj -2083 0 obj<>endobj -2084 0 obj<>endobj -2085 0 obj<>endobj -2086 0 obj<>endobj -2087 0 obj<>endobj -2088 0 obj<>endobj -2089 0 obj<>endobj -2090 0 obj<>endobj -2091 0 obj<>endobj -2092 0 obj<>endobj -2093 0 obj<>endobj -2094 0 obj<>endobj -2095 0 obj<>endobj -2096 0 obj<>endobj -2097 0 obj<>endobj -2098 0 obj<>endobj -2099 0 obj<>endobj -2100 0 obj<>endobj -2101 0 obj<>endobj -2102 0 obj<>endobj -2103 0 obj<>endobj -2104 0 obj<>endobj -2105 0 obj<>endobj -2106 0 obj<>endobj -2107 0 obj<>endobj -2108 0 obj<>endobj -2109 0 obj<>endobj -2110 0 obj<>endobj -2111 0 obj<>endobj -2112 0 obj<>endobj -2113 0 obj<>endobj -2114 0 obj<>endobj -2115 0 obj<>endobj -2116 0 obj<>endobj -2117 0 obj<>endobj -2118 0 obj<>endobj -2119 0 obj<>endobj -2120 0 obj<>endobj -2121 0 obj<>endobj -2122 0 obj<>endobj -2123 0 obj<>endobj -2124 0 obj<>endobj -2125 0 obj<>endobj -2126 0 obj<>endobj -2127 0 obj<>endobj -2128 0 obj<>endobj -2129 0 obj<>endobj -2130 0 obj<>endobj -2131 0 obj<>endobj -2132 0 obj<>endobj -2133 0 obj<>endobj -2134 0 obj<>endobj -2135 0 obj<>endobj -2136 0 obj<>endobj -2137 0 obj<>endobj -2138 0 obj<>endobj -2139 0 obj<>endobj -2140 0 obj<>endobj -2141 0 obj<>endobj -2142 0 obj<>endobj -2143 0 obj<>endobj -2144 0 obj<>endobj -2145 0 obj<>endobj -2146 0 obj<>endobj -2147 0 obj<>endobj -2148 0 obj<>endobj -2149 0 obj<>endobj -2150 0 obj<>endobj -2151 0 obj<>endobj -2152 0 obj<>endobj -2153 0 obj<>endobj -2154 0 obj<>endobj -2155 0 obj<>endobj -2156 0 obj<>endobj -2157 0 obj<>endobj -2158 0 obj<>endobj -2159 0 obj<>endobj -2160 0 obj<>endobj -2161 0 obj<>endobj -2162 0 obj<>endobj -2163 0 obj<>endobj -2164 0 obj<>endobj -2165 0 obj<>endobj -2166 0 obj<>endobj -2167 0 obj<>endobj -2168 0 obj<>endobj -2169 0 obj<>endobj -2170 0 obj<>endobj -2171 0 obj<>endobj -2172 0 obj<>endobj -2173 0 obj<>endobj -2174 0 obj<>endobj -2175 0 obj<>endobj -2176 0 obj<>endobj -2177 0 obj<>endobj -2178 0 obj<>endobj -2179 0 obj<>endobj -2180 0 obj<>endobj -2181 0 obj<>endobj -2182 0 obj<>endobj -2183 0 obj<>endobj -2184 0 obj<>endobj -2185 0 obj<>endobj -2186 0 obj<>endobj -2187 0 obj<>endobj -2188 0 obj<>endobj -2189 0 obj<>endobj -2190 0 obj<>endobj -2191 0 obj<>endobj -2192 0 obj<>endobj -2193 0 obj<>endobj -2194 0 obj<>endobj -2195 0 obj<>endobj -2196 0 obj<>endobj -2197 0 obj<>endobj -2198 0 obj<>endobj -2199 0 obj<>endobj -2200 0 obj<>endobj -2201 0 obj<>endobj -2202 0 obj<>endobj -2203 0 obj<>endobj -2204 0 obj<>endobj -2205 0 obj<>endobj -2206 0 obj<>endobj -2207 0 obj<>endobj -2208 0 obj<>endobj -2209 0 obj<>endobj -2210 0 obj<>endobj -2211 0 obj<>endobj -2212 0 obj<>endobj -2213 0 obj<>endobj -2214 0 obj<>endobj -2215 0 obj<>endobj -2216 0 obj<>endobj -2217 0 obj<>endobj -2218 0 obj<>endobj -2219 0 obj<>endobj -2220 0 obj<>endobj -2221 0 obj<>endobj -2222 0 obj<>endobj -2223 0 obj<>endobj -2224 0 obj<>endobj -2225 0 obj<>endobj -2226 0 obj<>endobj -2227 0 obj<>endobj -2228 0 obj<>endobj -2229 0 obj<>endobj -2230 0 obj<>endobj -2231 0 obj<>endobj -2232 0 obj<>endobj -2233 0 obj<>endobj -2234 0 obj<>endobj -2235 0 obj<>endobj -2236 0 obj<>endobj -2237 0 obj<>endobj -2238 0 obj<>endobj -2239 0 obj<>endobj -2240 0 obj<>endobj -2241 0 obj<>endobj -2242 0 obj<>endobj -2243 0 obj<>endobj -2244 0 obj<>endobj -2245 0 obj<>endobj -2246 0 obj<>endobj -2247 0 obj<>endobj -2248 0 obj<>endobj -2249 0 obj<>endobj -2250 0 obj<>endobj -2251 0 obj<>endobj -2252 0 obj<>endobj -2253 0 obj<>endobj -2254 0 obj<>endobj -2255 0 obj<>endobj -2256 0 obj<>endobj -2257 0 obj<>endobj -2258 0 obj<>endobj -2259 0 obj<>endobj -2260 0 obj<>endobj -2261 0 obj<>endobj -2262 0 obj<>endobj -2263 0 obj<>endobj -2264 0 obj<>endobj -2265 0 obj<>endobj -2266 0 obj<>endobj -2267 0 obj<>endobj -2268 0 obj<>endobj -2269 0 obj<>endobj -2270 0 obj<>endobj -2271 0 obj<>endobj -2272 0 obj<>endobj -2273 0 obj<>endobj -2274 0 obj<>endobj -2275 0 obj<>endobj -2276 0 obj<>endobj -2277 0 obj<>endobj -2278 0 obj<>endobj -2279 0 obj<>endobj -2280 0 obj<>endobj -2281 0 obj<>endobj -2282 0 obj<>endobj -2283 0 obj<>endobj -2284 0 obj<>endobj -2285 0 obj<>endobj -2286 0 obj<>endobj -2287 0 obj<>endobj -2288 0 obj<>endobj -2289 0 obj<>endobj -2290 0 obj<>endobj -2291 0 obj<>endobj -2292 0 obj<>endobj -2293 0 obj<>endobj -2294 0 obj<>endobj -2295 0 obj<>endobj -2296 0 obj<>endobj -2297 0 obj<>endobj -2298 0 obj<>endobj -2299 0 obj<>endobj -2300 0 obj<>endobj -2301 0 obj<>endobj -2302 0 obj<>endobj -2303 0 obj<>endobj -2304 0 obj<>endobj -2305 0 obj<>endobj -2306 0 obj<>endobj -2307 0 obj<>endobj -2308 0 obj<>endobj -2309 0 obj<>endobj -2310 0 obj<>endobj -2311 0 obj<>endobj -2312 0 obj<>endobj -2313 0 obj<>endobj -2314 0 obj<>endobj -2315 0 obj<>endobj -2316 0 obj<>endobj -2317 0 obj<>endobj -2318 0 obj<>endobj -2319 0 obj<>endobj -2320 0 obj<>endobj -2321 0 obj<>endobj -2322 0 obj<>endobj -2323 0 obj<>endobj -2324 0 obj<>endobj -2325 0 obj<>endobj -2326 0 obj<>endobj -2327 0 obj<>endobj -2328 0 obj<>endobj -2329 0 obj<>endobj -2330 0 obj<>endobj -2331 0 obj<>endobj -2332 0 obj<>endobj -2333 0 obj<>endobj -2334 0 obj<>endobj -2335 0 obj<>endobj -2336 0 obj<>endobj -2337 0 obj<>endobj -2338 0 obj<>endobj -2339 0 obj<>endobj -2340 0 obj<>endobj -2341 0 obj<>endobj -2342 0 obj<>endobj -2343 0 obj<>endobj -2344 0 obj<>endobj -2345 0 obj<>endobj -2346 0 obj<>endobj -2347 0 obj<>endobj -2348 0 obj<>endobj -2349 0 obj<>endobj -2350 0 obj<>endobj -2351 0 obj<>endobj -2352 0 obj<>endobj -2353 0 obj<>1<>9<>14<>15<>16<>20<>25<>36<>37<>39<>41<>45<>56<>59<>61<>63<>64<>68<>73<>74<>85<>107<>120<>122<>126<>138<>141<>144<>147<>149<>156<>165<>167<>168<>170<>171<>172<>176<>179<>183<>188<>190<>]>>>>endobj +ъ:Ns_P:7dJ QUַh_OQɢ!{Kӵ 0dGQ+i@%̚'"h*5tq" }1yזiJzKzB]vN3 9 fhq+ Fv :ϋGDhF7t\*o߲qrU>d7W)k/bE\(IvI0[!jD+Vm5w1DLn2-+ـ`wBp^4gZ_{%&M!H~f@ч3@X7t#T:\^" :v,>f6]>s= X!;N ͑)+w&pmbL5:or&Ӧ m댑\`֡ 0{ eQïɑ2F8yRXBgm5!Pl,ybLn.p5N#9^~>̹ې\.VWE&J!;kHd!; S;{Ik1wA]P`1D @|PbHerE@woX/-g?| 6j;:a=B5 |>0yIWKf>N~; oOendstream +endobj +1767 0 obj<>/XObject<<>>>>/Annots 948 0 R>>endobj +1768 0 obj<>stream +xTn0}WDcCD&U[섊uJJ_&D^{D/|i^prNx[(=8(Mgaҭ6AMYNޚc.0@n'ipEHsM#c|@.@4 Qlys^ {6S[8VlY7R0 ɯҗ`Q4 'TxxpfΚP]de\cbr󧫆©Vm7qL߸0.Jz` +B{ ;QcJ +GސhL %s(gk^&/3oPZ%GZkw-CT##V{Vaˊ491}zrVT:ΫWA(&Ԧ,$@G^: ϧn 'O z3Z\*>Ó.ӽRW2lm;ss E_U( ( g/[3GQdUN>_R|o4Cl*Ќ,Onu_?'&У`YTg4pKJ3ull}1IRp )J+"J[Y߮@/W3.X%B]Fh"LfJR"|K_?endstream +endobj +1769 0 obj<>/XObject<<>>>>/Annots 953 0 R>>endobj +1770 0 obj<>stream +xWMs6WMDIlɹ9vLLg|IBL Z} PN&ՏтULgVy4:zco$~|e/ђ9^l:|*~_̣3W1N)YQf +HJC\ c'[w/5ޚxYB-NYVeb=: 0f OLU@u>óZ4muty~Cғjft2@+L>+G<#3T&υڪfvCԋֹl"RE e"%#t8Z9z%wM鳘^\>0{4"CpCGR_ kx i`(~1xX;vJ2 ԄVwAG?_zQo'9X## L0ǀ_q7 >b"zylO^ ]p:+FA;\@Ql=y ~k/y2sjϯ69#oDpJ<ž=Ϝ%z56#_]\ndB 5 'x3JܩW9ZXFttKo-gS|#Lp-pm`ڴ%*HU- g]"a|5孕v;^#}(|zP>5}, ^$ԡ WK[d Eu_w8|_oa-|a3m/gQendstream +endobj +1771 0 obj<>/XObject<<>>>>/Annots 970 0 R>>endobj +1772 0 obj<>stream +xX]o8}ϯ0Hf˶%̤.BKʼnDjH*_﹔8j;vbQԑL~{<4i48DhJ 1[I[^LJ7gxMh1ѰyiyOcA4x:7^MYd&Tp6a 5oau48CBA#m߇v4ƫ]<]<@pb>^Wp8 +WoVg׼L-Gq:* *xcS{wF{krz/Va}TMi(HY4笭ҋutJ7ZycieLH蔮wR*y /+ rX cN wIER:5{GoW}H΋<3(L#=lxEx#׬Q9*ҵrUŭʑ.*OI>)a@Wߗ?{a^(^u^21ڤ"*謕 G{][;d +qsh玶@ \j);FUQ^Պ>'[i26EP,mp}+DB ^}IS^![ex-eڕ҅H gGcnd?4٣C|]G #_= 9AXh< #ܲ7N.:/`q@GܘI&c0)7 |vJ\˶&jW,p2I *A+3f&AHzha>:r˦*z CQ(6"$2Wo"cw} $XP"Zw}xv4ZG@J_Z|8%ߢ6, xЮ +@orYDt%g.Ia%4K?i>uMkH m!S&/]mgOmCZJ)_&{rqrAwD {4=⎊/Bᵊudv},YЦ04d޾Ax(z^t' X9oSϻYr?SZc5"3 _1'dH|Iath7,*2M ck]Rި'8lu +54y_x0 !.ky@O~v`V 07|#a~Wƥk9O |X!%Ò}-_d/.<_h:F~}sMꋦiy f>lpQa>/XObject<<>>>>/Annots 975 0 R>>endobj +1774 0 obj<>stream +xWMs6WlO;/Kr/ǩ2ukM;E T-H*괙d}[`JjF%e`Lh1%3ZW '/obY2C`'S/;f6M)8zE<:M6qTI5t(Et?lA^TmH +#avY +\c 5&.ܼLh<#M>6:THZ@D˽08jG|=@Y }&5E;'7Bi9"$δu{2NFYH3E; 1sJS--W]Pq~<;X֐s! 6fׁ:""1BW~}<"H -M$@sNY)'lR, ۼrgCsڸcdOEC#} .NNbDڂhٍTnx@9TAJdzYTj^)8)r^[sȷ &i2Jz/vv؁ h.b5dz W5q*‘.^Tj.0znDk+%v)سH?HMJsq3b[3gp'uO-!Z|n +!tuj[^ j/Y(RԵ4NdBG0tƟA ڃAfQ H @Le̩T^pʊc7EHd, + +jS[B?m%:n=86&)R1Le`/BcTൔnԞ*9s:|g>[3p++)&R Jv7!*{u +#Tʓ{(!4R$^XWT 韲KRhMJ>l<3+ \\sLKW/BŢwֳm-b9I :@bwU1Ft& 6}2f!E{, /LW 26 ff 7H!N:B`Xɜz1DU*#' &g3@.T6;xeS05>Bp|$z +Hy^SLN// Y6ʂu[Io)^DgdzC夭"NG{mj*󲁿V`caT ְ8Y='JIШCTkVБ‘XDBo3!]]!X=Z _B&Jźbwĭ洪Mdyh],B( 4Op]Q:tM`ό&z{`D%CQ *[kLi;)7p:va\S;6`?Ƚߓ$^;(Kׁ|}}/]yIm{5X `t(~ ~dqendstream +endobj +1775 0 obj<>/XObject<<>>>>/Annots 983 0 R>>endobj +1776 0 obj<>stream +x}Wێ6}W ڦi}hEbUZgHUA.̙3g'sߜnP^Of O?LlK:[PM&[w>M֫lE"|x'/ٚVUzyt'/ -oWZ\8r2/ݰlѲ--f+fK"'կj;Z3ȭuA7z׸r~VZJP +hEmd7]d1UL\+mHc充)^7GgOړW^?3Dd2mK$B1B_tlr*p^5:Wi +[I);a*Qa90lG:(_>I0Ŕ GEC#SNL(#tFRѾ&[ 1gV]^ɷ䐫FgSJSͰkF$RԳ DNH.FU88۵dKj:V D1TS@7B} h@2Z as~s(,8 ufD!@zQ=۲mY: #szqQ"0ad|W蝥ƂGwRCYL$TxTG.s[Yl5>>lDJbt\GaGnv3|y6DZ6BsRco +(Ҕ9%p6D siBAPjfGHBYR!x+}} zlв2c= =޷d?0 OQU.N bk' +D/ϡx!hzJ{jY4,*~Qŋ>pNMF&JUR%ڃ2'bCO)1ik HYkؘO[vxAԂ"nC\-e! HɭC 'HøƿKc䰂.u-:4kD݉t-I5tj&MW0 +BԎ3hPZ8Ԉ$A"A/A2%~Pp(/BxaaD%ʍL8#d4#y(8.cو+2TsJCZ.1=Co%d#M!*ho΋<@Y!ÑWrml>/XObject<<>>>>>>endobj +1778 0 obj<>stream +xWnF|WlRiɲe@4iH;hY=rhEHMgF4_PM)/ْΖ)zM8ϲ^N/~utrsF*Y,/hUL*&*єOzUNVkMIhpJ'm|8K_M[ڙh/^S꼫_'U +km $c5)'s}0r}UmHY/AlTyU)_*\U1qϟD4: +`^5f^+n:4\8_`jk*S(pSJX#c^ օj/gm՞d5p \z=2S}D q)zpER l_E`V F{tbJrrsI3~Q@`8mۈ¢/eY]Jt=X$jsxOÅ:[\Fmj.k<@s5g1(06~̓9'hF@g̓\Nuzǎm#5v$MpQ7k-**lxUF:S"` 2}J208e +͎O9&Sy'ɼ%%=Oz@_>~Hc!`H/տ,z:v!B1lK +'嬥 +RuXOFh4 ˫oӯKo8ƚ:22 <4v 8`/XnLfڟѸ#PG[`ȁ"3sV}Q7)Zq6 +'2q}<NXۃ<}|@ [t|$0f٫r ĺ+w +XUA_L/b-Oly__8U6endstream +endobj +1779 0 obj<>endobj +1780 0 obj<>endobj +1781 0 obj<>endobj +1782 0 obj<>endobj +1783 0 obj<>endobj +1784 0 obj<>endobj +1785 0 obj<>endobj +1786 0 obj<>endobj +1787 0 obj<>endobj +1788 0 obj<>endobj +1789 0 obj<>endobj +1790 0 obj<>endobj +1791 0 obj<>endobj +1792 0 obj<>endobj +1793 0 obj<>endobj +1794 0 obj<>endobj +1795 0 obj<>endobj +1796 0 obj<>endobj +1797 0 obj<>endobj +1798 0 obj<>endobj +1799 0 obj<>endobj +1800 0 obj<>endobj +1801 0 obj<>endobj +1802 0 obj<>endobj +1803 0 obj<>endobj +1804 0 obj<>endobj +1805 0 obj<>endobj +1806 0 obj<>endobj +1807 0 obj<>endobj +1808 0 obj<>endobj +1809 0 obj<>endobj +1810 0 obj<>endobj +1811 0 obj<>endobj +1812 0 obj<>endobj +1813 0 obj<>endobj +1814 0 obj<>endobj +1815 0 obj<>endobj +1816 0 obj<>endobj +1817 0 obj<>endobj +1818 0 obj<>endobj +1819 0 obj<>endobj +1820 0 obj<>endobj +1821 0 obj<>endobj +1822 0 obj<>endobj +1823 0 obj<>endobj +1824 0 obj<>endobj +1825 0 obj<>endobj +1826 0 obj<>endobj +1827 0 obj<>endobj +1828 0 obj<>endobj +1829 0 obj<>endobj +1830 0 obj<>endobj +1831 0 obj<>endobj +1832 0 obj<>endobj +1833 0 obj<>endobj +1834 0 obj<>endobj +1835 0 obj<>endobj +1836 0 obj<>endobj +1837 0 obj<>endobj +1838 0 obj<>endobj +1839 0 obj<>endobj +1840 0 obj<>endobj +1841 0 obj<>endobj +1842 0 obj<>endobj +1843 0 obj<>endobj +1844 0 obj<>endobj +1845 0 obj<>endobj +1846 0 obj<>endobj +1847 0 obj<>endobj +1848 0 obj<>endobj +1849 0 obj<>endobj +1850 0 obj<>endobj +1851 0 obj<>endobj +1852 0 obj<>endobj +1853 0 obj<>endobj +1854 0 obj<>endobj +1855 0 obj<>endobj +1856 0 obj<>endobj +1857 0 obj<>endobj +1858 0 obj<>endobj +1859 0 obj<>endobj +1860 0 obj<>endobj +1861 0 obj<>endobj +1862 0 obj<>endobj +1863 0 obj<>endobj +1864 0 obj<>endobj +1865 0 obj<>endobj +1866 0 obj<>endobj +1867 0 obj<>endobj +1868 0 obj<>endobj +1869 0 obj<>endobj +1870 0 obj<>endobj +1871 0 obj<>endobj +1872 0 obj<>endobj +1873 0 obj<>endobj +1874 0 obj<>endobj +1875 0 obj<>endobj +1876 0 obj<>endobj +1877 0 obj<>endobj +1878 0 obj<>endobj +1879 0 obj<>endobj +1880 0 obj<>endobj +1881 0 obj<>endobj +1882 0 obj<>endobj +1883 0 obj<>endobj +1884 0 obj<>endobj +1885 0 obj<>endobj +1886 0 obj<>endobj +1887 0 obj<>endobj +1888 0 obj<>endobj +1889 0 obj<>endobj +1890 0 obj<>endobj +1891 0 obj<>endobj +1892 0 obj<>endobj +1893 0 obj<>endobj +1894 0 obj<>endobj +1895 0 obj<>endobj +1896 0 obj<>endobj +1897 0 obj<>endobj +1898 0 obj<>endobj +1899 0 obj<>endobj +1900 0 obj<>endobj +1901 0 obj<>endobj +1902 0 obj<>endobj +1903 0 obj<>endobj +1904 0 obj<>endobj +1905 0 obj<>endobj +1906 0 obj<>endobj +1907 0 obj<>endobj +1908 0 obj<>endobj +1909 0 obj<>endobj +1910 0 obj<>endobj +1911 0 obj<>endobj +1912 0 obj<>endobj +1913 0 obj<>endobj +1914 0 obj<>endobj +1915 0 obj<>endobj +1916 0 obj<>endobj +1917 0 obj<>endobj +1918 0 obj<>endobj +1919 0 obj<>endobj +1920 0 obj<>endobj +1921 0 obj<>endobj +1922 0 obj<>endobj +1923 0 obj<>endobj +1924 0 obj<>endobj +1925 0 obj<>endobj +1926 0 obj<>endobj +1927 0 obj<>endobj +1928 0 obj<>endobj +1929 0 obj<>endobj +1930 0 obj<>endobj +1931 0 obj<>endobj +1932 0 obj<>endobj +1933 0 obj<>endobj +1934 0 obj<>endobj +1935 0 obj<>endobj +1936 0 obj<>endobj +1937 0 obj<>endobj +1938 0 obj<>endobj +1939 0 obj<>endobj +1940 0 obj<>endobj +1941 0 obj<>endobj +1942 0 obj<>endobj +1943 0 obj<>endobj +1944 0 obj<>endobj +1945 0 obj<>endobj +1946 0 obj<>endobj +1947 0 obj<>endobj +1948 0 obj<>endobj +1949 0 obj<>endobj +1950 0 obj<>endobj +1951 0 obj<>endobj +1952 0 obj<>endobj +1953 0 obj<>endobj +1954 0 obj<>endobj +1955 0 obj<>endobj +1956 0 obj<>endobj +1957 0 obj<>endobj +1958 0 obj<>endobj +1959 0 obj<>endobj +1960 0 obj<>endobj +1961 0 obj<>endobj +1962 0 obj<>endobj +1963 0 obj<>endobj +1964 0 obj<>endobj +1965 0 obj<>endobj +1966 0 obj<>endobj +1967 0 obj<>endobj +1968 0 obj<>endobj +1969 0 obj<>endobj +1970 0 obj<>endobj +1971 0 obj<>endobj +1972 0 obj<>endobj +1973 0 obj<>endobj +1974 0 obj<>endobj +1975 0 obj<>endobj +1976 0 obj<>endobj +1977 0 obj<>endobj +1978 0 obj<>endobj +1979 0 obj<>endobj +1980 0 obj<>endobj +1981 0 obj<>endobj +1982 0 obj<>endobj +1983 0 obj<>endobj +1984 0 obj<>endobj +1985 0 obj<>endobj +1986 0 obj<>endobj +1987 0 obj<>endobj +1988 0 obj<>endobj +1989 0 obj<>endobj +1990 0 obj<>endobj +1991 0 obj<>endobj +1992 0 obj<>endobj +1993 0 obj<>endobj +1994 0 obj<>endobj +1995 0 obj<>endobj +1996 0 obj<>endobj +1997 0 obj<>endobj +1998 0 obj<>endobj +1999 0 obj<>endobj +2000 0 obj<>endobj +2001 0 obj<>endobj +2002 0 obj<>endobj +2003 0 obj<>endobj +2004 0 obj<>endobj +2005 0 obj<>endobj +2006 0 obj<>endobj +2007 0 obj<>endobj +2008 0 obj<>endobj +2009 0 obj<>endobj +2010 0 obj<>endobj +2011 0 obj<>endobj +2012 0 obj<>endobj +2013 0 obj<>endobj +2014 0 obj<>endobj +2015 0 obj<>endobj +2016 0 obj<>endobj +2017 0 obj<>endobj +2018 0 obj<>endobj +2019 0 obj<>endobj +2020 0 obj<>endobj +2021 0 obj<>endobj +2022 0 obj<>endobj +2023 0 obj<>endobj +2024 0 obj<>endobj +2025 0 obj<>endobj +2026 0 obj<>endobj +2027 0 obj<>endobj +2028 0 obj<>endobj +2029 0 obj<>endobj +2030 0 obj<>endobj +2031 0 obj<>endobj +2032 0 obj<>endobj +2033 0 obj<>endobj +2034 0 obj<>endobj +2035 0 obj<>endobj +2036 0 obj<>endobj +2037 0 obj<>endobj +2038 0 obj<>endobj +2039 0 obj<>endobj +2040 0 obj<>endobj +2041 0 obj<>endobj +2042 0 obj<>endobj +2043 0 obj<>endobj +2044 0 obj<>endobj +2045 0 obj<>endobj +2046 0 obj<>endobj +2047 0 obj<>endobj +2048 0 obj<>endobj +2049 0 obj<>endobj +2050 0 obj<>endobj +2051 0 obj<>endobj +2052 0 obj<>endobj +2053 0 obj<>endobj +2054 0 obj<>endobj +2055 0 obj<>endobj +2056 0 obj<>endobj +2057 0 obj<>endobj +2058 0 obj<>endobj +2059 0 obj<>endobj +2060 0 obj<>endobj +2061 0 obj<>endobj +2062 0 obj<>endobj +2063 0 obj<>endobj +2064 0 obj<>endobj +2065 0 obj<>endobj +2066 0 obj<>endobj +2067 0 obj<>endobj +2068 0 obj<>endobj +2069 0 obj<>endobj +2070 0 obj<>endobj +2071 0 obj<>endobj +2072 0 obj<>endobj +2073 0 obj<>endobj +2074 0 obj<>endobj +2075 0 obj<>endobj +2076 0 obj<>endobj +2077 0 obj<>endobj +2078 0 obj<>endobj +2079 0 obj<>endobj +2080 0 obj<>endobj +2081 0 obj<>endobj +2082 0 obj<>endobj +2083 0 obj<>endobj +2084 0 obj<>endobj +2085 0 obj<>endobj +2086 0 obj<>endobj +2087 0 obj<>endobj +2088 0 obj<>endobj +2089 0 obj<>endobj +2090 0 obj<>endobj +2091 0 obj<>endobj +2092 0 obj<>endobj +2093 0 obj<>endobj +2094 0 obj<>endobj +2095 0 obj<>endobj +2096 0 obj<>endobj +2097 0 obj<>endobj +2098 0 obj<>endobj +2099 0 obj<>endobj +2100 0 obj<>endobj +2101 0 obj<>endobj +2102 0 obj<>endobj +2103 0 obj<>endobj +2104 0 obj<>endobj +2105 0 obj<>endobj +2106 0 obj<>endobj +2107 0 obj<>endobj +2108 0 obj<>endobj +2109 0 obj<>endobj +2110 0 obj<>endobj +2111 0 obj<>endobj +2112 0 obj<>endobj +2113 0 obj<>endobj +2114 0 obj<>endobj +2115 0 obj<>endobj +2116 0 obj<>endobj +2117 0 obj<>endobj +2118 0 obj<>endobj +2119 0 obj<>endobj +2120 0 obj<>endobj +2121 0 obj<>endobj +2122 0 obj<>endobj +2123 0 obj<>endobj +2124 0 obj<>endobj +2125 0 obj<>endobj +2126 0 obj<>endobj +2127 0 obj<>1<>10<>15<>16<>17<>21<>24<>29<>40<>41<>42<>44<>48<>56<>59<>61<>63<>64<>65<>70<>71<>82<>104<>117<>121<>126<>138<>141<>144<>147<>149<>156<>165<>167<>169<>170<>175<>177<>180<>184<>185<>189<>194<>197<>]>>>>endobj xref -0 2354 +0 2128 0000000000 65535 f 0000000015 00000 n 0000000247 00000 n @@ -5171,9 +4665,9 @@ xref 0000005257 00000 n 0000005360 00000 n 0000005463 00000 n -0000005566 00000 n -0000005669 00000 n -0000005772 00000 n +0000005565 00000 n +0000005668 00000 n +0000005771 00000 n 0000005874 00000 n 0000005977 00000 n 0000006080 00000 n @@ -5192,2308 +4686,2082 @@ xref 0000007418 00000 n 0000007521 00000 n 0000007624 00000 n -0000007727 00000 n -0000007830 00000 n -0000007933 00000 n -0000008036 00000 n -0000008138 00000 n -0000008239 00000 n -0000008340 00000 n -0000008657 00000 n -0000008759 00000 n -0000008862 00000 n -0000008965 00000 n -0000009068 00000 n -0000009171 00000 n -0000009274 00000 n -0000009377 00000 n -0000009480 00000 n -0000009582 00000 n -0000009684 00000 n -0000009786 00000 n -0000009889 00000 n -0000009992 00000 n -0000010095 00000 n -0000010198 00000 n -0000010300 00000 n -0000010403 00000 n -0000010506 00000 n -0000010609 00000 n -0000010712 00000 n -0000010815 00000 n -0000010918 00000 n -0000011020 00000 n -0000011123 00000 n -0000011226 00000 n -0000011329 00000 n -0000011432 00000 n -0000011535 00000 n -0000011638 00000 n -0000011741 00000 n -0000011844 00000 n -0000011947 00000 n -0000012050 00000 n -0000012153 00000 n -0000012255 00000 n -0000012358 00000 n -0000012461 00000 n -0000012564 00000 n -0000012667 00000 n -0000012770 00000 n -0000012872 00000 n -0000012974 00000 n +0000007726 00000 n +0000007829 00000 n +0000007932 00000 n +0000008034 00000 n +0000008135 00000 n +0000008236 00000 n +0000008546 00000 n +0000008648 00000 n +0000008751 00000 n +0000008854 00000 n +0000008957 00000 n +0000009060 00000 n +0000009163 00000 n +0000009266 00000 n +0000009369 00000 n +0000009472 00000 n +0000009575 00000 n +0000009678 00000 n +0000009781 00000 n +0000009884 00000 n +0000009987 00000 n +0000010090 00000 n +0000010193 00000 n +0000010296 00000 n +0000010399 00000 n +0000010502 00000 n +0000010604 00000 n +0000010706 00000 n +0000010808 00000 n +0000010911 00000 n +0000011014 00000 n +0000011117 00000 n +0000011220 00000 n +0000011322 00000 n +0000011425 00000 n +0000011528 00000 n +0000011631 00000 n +0000011734 00000 n +0000011837 00000 n +0000011940 00000 n +0000012042 00000 n +0000012145 00000 n +0000012248 00000 n +0000012351 00000 n +0000012454 00000 n +0000012557 00000 n +0000012660 00000 n +0000012763 00000 n +0000012865 00000 n +0000012967 00000 n 0000013288 00000 n 0000013391 00000 n 0000013495 00000 n 0000013599 00000 n -0000013702 00000 n -0000013806 00000 n -0000013910 00000 n -0000014014 00000 n -0000014118 00000 n -0000014222 00000 n -0000014326 00000 n +0000013703 00000 n +0000013807 00000 n +0000013911 00000 n +0000014015 00000 n +0000014119 00000 n +0000014223 00000 n +0000014327 00000 n 0000014430 00000 n -0000014533 00000 n -0000014637 00000 n -0000014741 00000 n -0000014844 00000 n -0000014947 00000 n -0000015050 00000 n -0000015154 00000 n -0000015258 00000 n -0000015362 00000 n -0000015466 00000 n -0000015570 00000 n -0000015674 00000 n -0000015778 00000 n -0000015882 00000 n -0000015986 00000 n -0000016089 00000 n -0000016192 00000 n -0000016296 00000 n -0000016400 00000 n -0000016504 00000 n -0000016608 00000 n -0000016712 00000 n -0000016816 00000 n -0000016920 00000 n -0000017024 00000 n -0000017128 00000 n -0000017232 00000 n -0000017335 00000 n -0000017437 00000 n -0000017539 00000 n -0000017884 00000 n -0000017987 00000 n -0000018091 00000 n -0000018195 00000 n -0000018299 00000 n -0000018403 00000 n -0000018507 00000 n -0000018611 00000 n -0000018715 00000 n -0000018819 00000 n -0000018923 00000 n -0000019026 00000 n -0000019130 00000 n -0000019234 00000 n -0000019338 00000 n -0000019442 00000 n -0000019546 00000 n -0000019650 00000 n -0000019754 00000 n -0000019858 00000 n -0000019962 00000 n -0000020066 00000 n -0000020170 00000 n -0000020274 00000 n -0000020378 00000 n -0000020482 00000 n -0000020586 00000 n -0000020689 00000 n -0000020793 00000 n -0000020897 00000 n -0000021001 00000 n -0000021105 00000 n -0000021209 00000 n -0000021313 00000 n -0000021417 00000 n -0000021521 00000 n -0000021625 00000 n -0000021729 00000 n -0000021833 00000 n -0000021937 00000 n -0000022041 00000 n -0000022145 00000 n -0000022249 00000 n -0000022353 00000 n -0000022456 00000 n -0000022825 00000 n -0000022928 00000 n -0000023032 00000 n -0000023136 00000 n -0000023240 00000 n -0000023344 00000 n -0000023447 00000 n -0000023551 00000 n -0000023655 00000 n -0000023759 00000 n -0000023863 00000 n -0000023967 00000 n -0000024071 00000 n -0000024175 00000 n -0000024278 00000 n -0000024382 00000 n -0000024486 00000 n -0000024590 00000 n -0000024694 00000 n -0000024798 00000 n -0000024902 00000 n -0000025006 00000 n -0000025110 00000 n -0000025214 00000 n -0000025318 00000 n -0000025422 00000 n -0000025525 00000 n -0000025629 00000 n -0000025733 00000 n -0000025837 00000 n -0000025941 00000 n -0000026045 00000 n -0000026149 00000 n -0000026253 00000 n -0000026356 00000 n -0000026460 00000 n -0000026564 00000 n -0000026668 00000 n -0000026771 00000 n -0000026875 00000 n -0000026979 00000 n -0000027082 00000 n -0000027184 00000 n -0000027286 00000 n -0000027647 00000 n -0000027750 00000 n -0000027854 00000 n -0000027958 00000 n -0000028062 00000 n -0000028166 00000 n -0000028269 00000 n -0000028373 00000 n -0000028477 00000 n -0000028580 00000 n -0000028684 00000 n -0000028788 00000 n -0000028892 00000 n -0000028996 00000 n -0000029100 00000 n -0000029204 00000 n -0000029308 00000 n -0000029412 00000 n -0000029516 00000 n -0000029620 00000 n -0000029724 00000 n -0000029827 00000 n -0000029931 00000 n -0000030035 00000 n -0000030139 00000 n -0000030243 00000 n -0000030347 00000 n -0000030451 00000 n -0000030555 00000 n -0000030659 00000 n -0000030763 00000 n -0000030867 00000 n -0000030971 00000 n -0000031075 00000 n -0000031178 00000 n -0000031282 00000 n -0000031386 00000 n -0000031490 00000 n -0000031594 00000 n -0000031698 00000 n -0000031802 00000 n -0000031904 00000 n -0000032006 00000 n -0000032108 00000 n -0000032469 00000 n -0000032572 00000 n -0000032675 00000 n -0000032779 00000 n -0000032883 00000 n -0000032987 00000 n -0000033091 00000 n -0000033195 00000 n -0000033299 00000 n -0000033403 00000 n -0000033507 00000 n -0000033610 00000 n -0000033714 00000 n -0000033818 00000 n -0000033922 00000 n -0000034026 00000 n -0000034129 00000 n -0000034233 00000 n -0000034337 00000 n -0000034441 00000 n -0000034545 00000 n -0000034649 00000 n -0000034753 00000 n -0000034857 00000 n -0000034961 00000 n -0000035065 00000 n -0000035169 00000 n -0000035272 00000 n -0000035376 00000 n -0000035480 00000 n -0000035584 00000 n -0000035688 00000 n -0000035792 00000 n -0000035896 00000 n -0000035999 00000 n -0000036103 00000 n -0000036207 00000 n -0000036311 00000 n -0000036415 00000 n -0000036519 00000 n -0000036623 00000 n -0000036726 00000 n -0000036828 00000 n -0000036930 00000 n -0000037291 00000 n -0000037394 00000 n -0000037498 00000 n -0000037602 00000 n -0000037706 00000 n -0000037810 00000 n -0000037914 00000 n -0000038018 00000 n -0000038121 00000 n -0000038225 00000 n -0000038329 00000 n -0000038433 00000 n -0000038537 00000 n -0000038641 00000 n -0000038745 00000 n -0000038849 00000 n -0000038953 00000 n -0000039057 00000 n -0000039160 00000 n -0000039264 00000 n -0000039368 00000 n -0000039472 00000 n -0000039576 00000 n -0000039680 00000 n -0000039784 00000 n -0000039887 00000 n -0000039991 00000 n -0000040095 00000 n -0000040199 00000 n -0000040303 00000 n -0000040552 00000 n -0000040606 00000 n -0000040692 00000 n -0000040745 00000 n -0000040831 00000 n -0000040885 00000 n -0000040972 00000 n +0000014534 00000 n +0000014638 00000 n +0000014742 00000 n +0000014846 00000 n +0000014950 00000 n +0000015054 00000 n +0000015158 00000 n +0000015262 00000 n +0000015366 00000 n +0000015469 00000 n +0000015573 00000 n +0000015677 00000 n +0000015781 00000 n +0000015885 00000 n +0000015989 00000 n +0000016093 00000 n +0000016197 00000 n +0000016300 00000 n +0000016404 00000 n +0000016508 00000 n +0000016611 00000 n +0000016714 00000 n +0000016817 00000 n +0000016921 00000 n +0000017025 00000 n +0000017129 00000 n +0000017233 00000 n +0000017337 00000 n +0000017440 00000 n +0000017542 00000 n +0000017644 00000 n +0000017997 00000 n +0000018100 00000 n +0000018204 00000 n +0000018307 00000 n +0000018410 00000 n +0000018514 00000 n +0000018618 00000 n +0000018722 00000 n +0000018826 00000 n +0000018930 00000 n +0000019034 00000 n +0000019138 00000 n +0000019242 00000 n +0000019346 00000 n +0000019450 00000 n +0000019554 00000 n +0000019658 00000 n +0000019762 00000 n +0000019866 00000 n +0000019970 00000 n +0000020074 00000 n +0000020178 00000 n +0000020282 00000 n +0000020386 00000 n +0000020490 00000 n +0000020594 00000 n +0000020698 00000 n +0000020801 00000 n +0000020905 00000 n +0000021009 00000 n +0000021113 00000 n +0000021217 00000 n +0000021321 00000 n +0000021425 00000 n +0000021529 00000 n +0000021633 00000 n +0000021737 00000 n +0000021841 00000 n +0000021945 00000 n +0000022049 00000 n +0000022153 00000 n +0000022257 00000 n +0000022361 00000 n +0000022714 00000 n +0000022817 00000 n +0000022921 00000 n +0000023025 00000 n +0000023129 00000 n +0000023233 00000 n +0000023337 00000 n +0000023441 00000 n +0000023545 00000 n +0000023649 00000 n +0000023753 00000 n +0000023857 00000 n +0000023961 00000 n +0000024065 00000 n +0000024169 00000 n +0000024273 00000 n +0000024377 00000 n +0000024481 00000 n +0000024585 00000 n +0000024688 00000 n +0000024792 00000 n +0000024896 00000 n +0000025000 00000 n +0000025104 00000 n +0000025207 00000 n +0000025311 00000 n +0000025415 00000 n +0000025519 00000 n +0000025623 00000 n +0000025727 00000 n +0000025831 00000 n +0000025935 00000 n +0000026039 00000 n +0000026142 00000 n +0000026246 00000 n +0000026350 00000 n +0000026454 00000 n +0000026558 00000 n +0000026662 00000 n +0000026766 00000 n +0000026870 00000 n +0000026974 00000 n +0000027078 00000 n +0000027181 00000 n +0000027283 00000 n +0000027652 00000 n +0000027755 00000 n +0000027859 00000 n +0000027963 00000 n +0000028067 00000 n +0000028171 00000 n +0000028275 00000 n +0000028379 00000 n +0000028483 00000 n +0000028586 00000 n +0000028690 00000 n +0000028794 00000 n +0000028898 00000 n +0000029001 00000 n +0000029105 00000 n +0000029209 00000 n +0000029313 00000 n +0000029417 00000 n +0000029521 00000 n +0000029625 00000 n +0000029729 00000 n +0000029833 00000 n +0000029937 00000 n +0000030040 00000 n +0000030144 00000 n +0000030248 00000 n +0000030351 00000 n +0000030455 00000 n +0000030559 00000 n +0000030663 00000 n +0000030767 00000 n +0000030871 00000 n +0000030975 00000 n +0000031079 00000 n +0000031183 00000 n +0000031287 00000 n +0000031391 00000 n +0000031495 00000 n +0000031598 00000 n +0000031702 00000 n +0000031806 00000 n +0000031909 00000 n +0000032011 00000 n +0000032113 00000 n +0000032474 00000 n +0000032577 00000 n +0000032681 00000 n +0000032785 00000 n +0000032889 00000 n +0000032993 00000 n +0000033097 00000 n +0000033201 00000 n +0000033305 00000 n +0000033408 00000 n +0000033512 00000 n +0000033616 00000 n +0000033720 00000 n +0000033824 00000 n +0000033928 00000 n +0000034032 00000 n +0000034135 00000 n +0000034239 00000 n +0000034343 00000 n +0000034447 00000 n +0000034550 00000 n +0000034653 00000 n +0000034757 00000 n +0000034861 00000 n +0000034965 00000 n +0000035069 00000 n +0000035173 00000 n +0000035277 00000 n +0000035381 00000 n +0000035485 00000 n +0000035589 00000 n +0000035693 00000 n +0000035796 00000 n +0000035900 00000 n +0000036004 00000 n +0000036108 00000 n +0000036212 00000 n +0000036315 00000 n +0000036419 00000 n +0000036523 00000 n +0000036626 00000 n +0000036728 00000 n +0000036830 00000 n +0000037183 00000 n +0000037286 00000 n +0000037390 00000 n +0000037494 00000 n +0000037597 00000 n +0000037701 00000 n +0000037805 00000 n +0000037909 00000 n +0000038013 00000 n +0000038117 00000 n +0000038221 00000 n +0000038325 00000 n +0000038429 00000 n +0000038533 00000 n +0000038637 00000 n +0000038741 00000 n +0000038845 00000 n +0000038949 00000 n +0000039053 00000 n +0000039157 00000 n +0000039260 00000 n +0000039364 00000 n +0000039468 00000 n +0000039572 00000 n +0000039676 00000 n +0000039780 00000 n +0000039884 00000 n +0000039988 00000 n +0000040092 00000 n +0000040195 00000 n +0000040299 00000 n +0000040403 00000 n +0000040507 00000 n +0000040611 00000 n +0000040715 00000 n +0000040819 00000 n +0000040923 00000 n 0000041027 00000 n -0000041113 00000 n -0000041180 00000 n -0000041266 00000 n -0000041369 00000 n -0000041473 00000 n -0000041577 00000 n -0000041681 00000 n -0000041785 00000 n -0000041889 00000 n -0000041993 00000 n -0000042097 00000 n -0000042201 00000 n -0000042305 00000 n -0000042409 00000 n -0000042513 00000 n -0000042617 00000 n -0000042721 00000 n -0000042825 00000 n -0000042929 00000 n -0000043033 00000 n -0000043137 00000 n -0000043240 00000 n -0000043342 00000 n -0000043444 00000 n -0000043546 00000 n -0000043779 00000 n -0000043883 00000 n -0000043987 00000 n -0000044091 00000 n -0000044195 00000 n -0000044297 00000 n -0000044401 00000 n -0000044505 00000 n -0000044609 00000 n -0000044713 00000 n -0000044817 00000 n -0000044921 00000 n -0000045025 00000 n -0000045129 00000 n -0000045233 00000 n -0000045337 00000 n -0000045441 00000 n -0000045545 00000 n -0000045649 00000 n -0000045753 00000 n -0000045857 00000 n -0000045961 00000 n -0000046065 00000 n -0000046169 00000 n -0000046273 00000 n -0000046377 00000 n +0000041131 00000 n +0000041235 00000 n +0000041338 00000 n +0000041442 00000 n +0000041545 00000 n +0000041647 00000 n +0000041749 00000 n +0000042118 00000 n +0000042221 00000 n +0000042325 00000 n +0000042429 00000 n +0000042533 00000 n +0000042637 00000 n +0000042741 00000 n +0000042844 00000 n +0000042948 00000 n +0000043052 00000 n +0000043156 00000 n +0000043260 00000 n +0000043364 00000 n +0000043468 00000 n +0000043589 00000 n +0000043643 00000 n +0000043729 00000 n +0000043782 00000 n +0000043868 00000 n +0000043922 00000 n +0000044009 00000 n +0000044064 00000 n +0000044150 00000 n +0000044217 00000 n +0000044303 00000 n +0000044406 00000 n +0000044510 00000 n +0000044614 00000 n +0000044718 00000 n +0000044822 00000 n +0000044926 00000 n +0000045030 00000 n +0000045134 00000 n +0000045238 00000 n +0000045342 00000 n +0000045446 00000 n +0000045550 00000 n +0000045654 00000 n +0000045758 00000 n +0000045862 00000 n +0000045966 00000 n +0000046070 00000 n +0000046174 00000 n +0000046277 00000 n +0000046379 00000 n 0000046481 00000 n -0000046585 00000 n -0000046689 00000 n -0000046793 00000 n -0000046897 00000 n -0000047001 00000 n -0000047105 00000 n -0000047209 00000 n -0000047313 00000 n -0000047417 00000 n -0000047521 00000 n -0000047625 00000 n -0000047727 00000 n -0000047831 00000 n -0000047935 00000 n -0000048039 00000 n -0000048143 00000 n -0000048247 00000 n -0000048351 00000 n -0000048455 00000 n -0000048559 00000 n -0000048663 00000 n -0000048767 00000 n -0000048871 00000 n -0000048975 00000 n -0000049078 00000 n -0000049180 00000 n -0000049282 00000 n -0000049723 00000 n -0000049827 00000 n -0000049931 00000 n -0000050035 00000 n -0000050139 00000 n -0000050243 00000 n -0000050347 00000 n -0000050451 00000 n -0000050555 00000 n -0000050659 00000 n -0000050763 00000 n -0000050867 00000 n -0000050971 00000 n -0000051075 00000 n -0000051179 00000 n -0000051283 00000 n -0000051387 00000 n -0000051491 00000 n -0000051595 00000 n -0000051699 00000 n -0000051803 00000 n -0000051907 00000 n -0000052011 00000 n -0000052115 00000 n -0000052219 00000 n -0000052323 00000 n -0000052427 00000 n -0000052531 00000 n -0000052635 00000 n -0000052739 00000 n -0000052843 00000 n -0000052947 00000 n -0000053051 00000 n -0000053155 00000 n -0000053259 00000 n -0000053363 00000 n -0000053467 00000 n -0000053571 00000 n -0000053675 00000 n -0000053779 00000 n -0000053883 00000 n -0000053987 00000 n -0000054091 00000 n -0000054195 00000 n -0000054299 00000 n -0000054403 00000 n -0000054507 00000 n -0000054611 00000 n -0000054715 00000 n -0000054819 00000 n -0000054922 00000 n -0000055024 00000 n -0000055126 00000 n -0000055559 00000 n -0000055663 00000 n -0000055767 00000 n -0000055871 00000 n -0000055975 00000 n -0000056079 00000 n -0000056183 00000 n -0000056287 00000 n -0000056391 00000 n -0000056495 00000 n -0000056599 00000 n -0000056703 00000 n -0000056807 00000 n -0000056911 00000 n -0000057015 00000 n -0000057119 00000 n -0000057223 00000 n -0000057327 00000 n -0000057431 00000 n -0000057535 00000 n -0000057639 00000 n -0000057743 00000 n -0000057846 00000 n -0000057950 00000 n -0000058054 00000 n -0000058158 00000 n -0000058262 00000 n -0000058366 00000 n -0000058470 00000 n -0000058574 00000 n -0000058678 00000 n -0000058782 00000 n -0000058886 00000 n -0000058990 00000 n -0000059094 00000 n -0000059198 00000 n -0000059302 00000 n -0000059406 00000 n -0000059510 00000 n -0000059614 00000 n -0000059718 00000 n -0000059822 00000 n -0000059926 00000 n -0000060030 00000 n -0000060134 00000 n -0000060238 00000 n -0000060342 00000 n -0000060446 00000 n -0000060550 00000 n -0000060653 00000 n -0000060755 00000 n -0000060857 00000 n -0000061282 00000 n -0000061386 00000 n -0000061490 00000 n -0000061594 00000 n -0000061698 00000 n -0000061802 00000 n -0000061906 00000 n -0000062010 00000 n -0000062114 00000 n -0000062218 00000 n -0000062322 00000 n -0000062426 00000 n -0000062530 00000 n -0000062634 00000 n -0000062738 00000 n -0000062842 00000 n -0000062946 00000 n -0000063050 00000 n -0000063203 00000 n -0000063306 00000 n -0000063410 00000 n -0000063514 00000 n -0000063618 00000 n -0000063722 00000 n -0000063826 00000 n -0000063930 00000 n -0000064034 00000 n -0000064138 00000 n -0000064242 00000 n -0000064346 00000 n -0000064450 00000 n -0000064553 00000 n -0000064657 00000 n -0000064761 00000 n -0000064865 00000 n -0000064969 00000 n -0000065073 00000 n -0000065177 00000 n -0000065281 00000 n -0000065384 00000 n -0000065488 00000 n -0000065592 00000 n -0000065696 00000 n -0000065800 00000 n -0000065904 00000 n -0000066008 00000 n -0000066112 00000 n -0000066216 00000 n -0000066320 00000 n -0000066424 00000 n -0000066528 00000 n -0000066632 00000 n -0000066736 00000 n -0000066840 00000 n -0000066944 00000 n -0000067048 00000 n -0000067152 00000 n -0000067256 00000 n -0000067360 00000 n -0000067464 00000 n -0000067568 00000 n -0000067671 00000 n -0000067773 00000 n -0000068142 00000 n -0000068191 00000 n -0000068278 00000 n -0000068382 00000 n -0000068486 00000 n -0000068589 00000 n -0000068638 00000 n -0000068742 00000 n -0000068767 00000 n -0000068823 00000 n -0000068910 00000 n -0000068979 00000 n -0000069066 00000 n -0000069117 00000 n -0000069204 00000 n -0000069289 00000 n -0000069376 00000 n -0000069432 00000 n -0000069519 00000 n -0000069569 00000 n -0000069656 00000 n -0000069708 00000 n -0000069794 00000 n -0000069867 00000 n -0000069929 00000 n -0000070016 00000 n -0000070070 00000 n -0000070156 00000 n -0000070210 00000 n -0000070297 00000 n -0000070338 00000 n -0000070379 00000 n -0000070466 00000 n -0000070510 00000 n -0000070597 00000 n -0000070642 00000 n -0000070729 00000 n -0000070773 00000 n -0000070860 00000 n -0000070904 00000 n -0000070991 00000 n -0000071033 00000 n -0000071120 00000 n -0000071168 00000 n -0000071255 00000 n -0000071328 00000 n -0000071376 00000 n -0000071461 00000 n -0000071486 00000 n -0000071539 00000 n -0000071623 00000 n +0000046583 00000 n +0000046816 00000 n +0000046920 00000 n +0000047024 00000 n +0000047128 00000 n +0000047232 00000 n +0000047336 00000 n +0000047440 00000 n +0000047544 00000 n +0000047648 00000 n +0000047752 00000 n +0000047856 00000 n +0000047960 00000 n +0000048064 00000 n +0000048167 00000 n +0000048271 00000 n +0000048375 00000 n +0000048479 00000 n +0000048583 00000 n +0000048687 00000 n +0000048791 00000 n +0000048895 00000 n +0000048999 00000 n +0000049103 00000 n +0000049207 00000 n +0000049311 00000 n +0000049415 00000 n +0000049519 00000 n +0000049623 00000 n +0000049727 00000 n +0000049831 00000 n +0000049935 00000 n +0000050039 00000 n +0000050143 00000 n +0000050247 00000 n +0000050351 00000 n +0000050455 00000 n +0000050559 00000 n +0000050663 00000 n +0000050767 00000 n +0000050871 00000 n +0000050975 00000 n +0000051079 00000 n +0000051183 00000 n +0000051287 00000 n +0000051391 00000 n +0000051493 00000 n +0000051597 00000 n +0000051701 00000 n +0000051805 00000 n +0000051909 00000 n +0000052013 00000 n +0000052116 00000 n +0000052218 00000 n +0000052320 00000 n +0000052761 00000 n +0000052865 00000 n +0000052969 00000 n +0000053073 00000 n +0000053177 00000 n +0000053281 00000 n +0000053385 00000 n +0000053489 00000 n +0000053593 00000 n +0000053697 00000 n +0000053801 00000 n +0000053905 00000 n +0000054009 00000 n +0000054113 00000 n +0000054217 00000 n +0000054321 00000 n +0000054425 00000 n +0000054529 00000 n +0000054633 00000 n +0000054737 00000 n +0000054841 00000 n +0000054945 00000 n +0000055049 00000 n +0000055153 00000 n +0000055257 00000 n +0000055361 00000 n +0000055465 00000 n +0000055569 00000 n +0000055673 00000 n +0000055777 00000 n +0000055881 00000 n +0000055985 00000 n +0000056089 00000 n +0000056193 00000 n +0000056297 00000 n +0000056401 00000 n +0000056505 00000 n +0000056609 00000 n +0000056713 00000 n +0000056817 00000 n +0000056921 00000 n +0000057025 00000 n +0000057129 00000 n +0000057233 00000 n +0000057337 00000 n +0000057441 00000 n +0000057545 00000 n +0000057649 00000 n +0000057753 00000 n +0000057857 00000 n +0000057960 00000 n +0000058062 00000 n +0000058164 00000 n +0000058597 00000 n +0000058701 00000 n +0000058805 00000 n +0000058909 00000 n +0000059013 00000 n +0000059117 00000 n +0000059221 00000 n +0000059325 00000 n +0000059429 00000 n +0000059533 00000 n +0000059637 00000 n +0000059741 00000 n +0000059845 00000 n +0000059949 00000 n +0000060053 00000 n +0000060157 00000 n +0000060261 00000 n +0000060365 00000 n +0000060469 00000 n +0000060573 00000 n +0000060677 00000 n +0000060781 00000 n +0000060885 00000 n +0000060989 00000 n +0000061093 00000 n +0000061197 00000 n +0000061301 00000 n +0000061405 00000 n +0000061509 00000 n +0000061613 00000 n +0000061717 00000 n +0000061820 00000 n +0000061924 00000 n +0000062028 00000 n +0000062132 00000 n +0000062236 00000 n +0000062340 00000 n +0000062444 00000 n +0000062548 00000 n +0000062652 00000 n +0000062756 00000 n +0000062860 00000 n +0000062964 00000 n +0000063068 00000 n +0000063172 00000 n +0000063276 00000 n +0000063380 00000 n +0000063484 00000 n +0000063588 00000 n +0000063691 00000 n +0000063793 00000 n +0000063895 00000 n +0000064320 00000 n +0000064424 00000 n +0000064528 00000 n +0000064632 00000 n +0000064736 00000 n +0000064840 00000 n +0000064944 00000 n +0000065048 00000 n +0000065152 00000 n +0000065256 00000 n +0000065360 00000 n +0000065464 00000 n +0000065568 00000 n +0000065672 00000 n +0000065776 00000 n +0000065880 00000 n +0000065984 00000 n +0000066088 00000 n +0000066192 00000 n +0000066296 00000 n +0000066400 00000 n +0000066504 00000 n +0000066608 00000 n +0000066712 00000 n +0000066816 00000 n +0000066920 00000 n +0000067024 00000 n +0000067128 00000 n +0000067232 00000 n +0000067336 00000 n +0000067440 00000 n +0000067544 00000 n +0000067648 00000 n +0000067752 00000 n +0000067856 00000 n +0000068145 00000 n +0000068194 00000 n +0000068281 00000 n +0000068385 00000 n +0000068489 00000 n +0000068592 00000 n +0000068641 00000 n +0000068745 00000 n +0000068848 00000 n +0000068881 00000 n +0000068937 00000 n +0000069024 00000 n +0000069093 00000 n +0000069180 00000 n +0000069231 00000 n +0000069318 00000 n +0000069403 00000 n +0000069490 00000 n +0000069546 00000 n +0000069633 00000 n +0000069683 00000 n +0000069770 00000 n +0000069822 00000 n +0000069909 00000 n +0000069971 00000 n +0000070056 00000 n +0000070137 00000 n +0000070191 00000 n +0000070277 00000 n +0000070331 00000 n +0000070418 00000 n +0000070451 00000 n +0000070492 00000 n +0000070579 00000 n +0000070623 00000 n +0000070710 00000 n +0000070755 00000 n +0000070842 00000 n +0000070886 00000 n +0000070973 00000 n +0000071017 00000 n +0000071104 00000 n +0000071146 00000 n +0000071233 00000 n +0000071281 00000 n +0000071368 00000 n +0000071441 00000 n +0000071545 00000 n 0000071648 00000 n -0000071751 00000 n -0000071855 00000 n -0000071959 00000 n -0000072063 00000 n -0000072167 00000 n -0000072270 00000 n -0000072374 00000 n -0000072478 00000 n -0000072582 00000 n -0000072686 00000 n -0000072790 00000 n -0000072894 00000 n -0000072997 00000 n -0000073101 00000 n -0000073205 00000 n -0000073309 00000 n +0000071681 00000 n +0000071734 00000 n +0000071820 00000 n +0000071845 00000 n +0000071892 00000 n +0000071978 00000 n +0000072025 00000 n +0000072111 00000 n +0000072144 00000 n +0000072189 00000 n +0000072276 00000 n +0000072321 00000 n +0000072407 00000 n +0000072440 00000 n +0000072485 00000 n +0000072571 00000 n +0000072614 00000 n +0000072700 00000 n +0000072741 00000 n +0000072827 00000 n +0000072876 00000 n +0000072962 00000 n +0000073008 00000 n +0000073094 00000 n +0000073139 00000 n +0000073225 00000 n +0000073277 00000 n +0000073363 00000 n 0000073413 00000 n -0000073517 00000 n -0000073621 00000 n -0000073725 00000 n -0000073829 00000 n +0000073499 00000 n +0000073545 00000 n +0000073631 00000 n +0000073674 00000 n +0000073760 00000 n +0000073804 00000 n +0000073890 00000 n 0000073933 00000 n -0000074037 00000 n -0000074141 00000 n -0000074244 00000 n -0000074348 00000 n -0000074452 00000 n -0000074556 00000 n -0000074660 00000 n -0000074764 00000 n -0000074868 00000 n -0000074972 00000 n -0000075076 00000 n -0000075180 00000 n -0000075283 00000 n -0000075387 00000 n -0000075491 00000 n -0000075595 00000 n -0000075699 00000 n -0000075803 00000 n -0000075907 00000 n -0000076011 00000 n -0000076115 00000 n -0000076218 00000 n -0000076319 00000 n -0000076421 00000 n -0000076806 00000 n -0000076910 00000 n -0000076935 00000 n -0000076982 00000 n -0000077068 00000 n -0000077115 00000 n -0000077201 00000 n -0000077234 00000 n -0000077279 00000 n -0000077366 00000 n -0000077411 00000 n -0000077497 00000 n -0000077530 00000 n -0000077578 00000 n -0000077665 00000 n -0000077690 00000 n -0000077738 00000 n -0000077825 00000 n -0000077870 00000 n -0000077956 00000 n -0000077999 00000 n -0000078085 00000 n -0000078126 00000 n -0000078212 00000 n -0000078261 00000 n -0000078347 00000 n -0000078393 00000 n -0000078479 00000 n -0000078524 00000 n +0000074019 00000 n +0000074064 00000 n +0000074150 00000 n +0000074188 00000 n +0000074274 00000 n +0000074316 00000 n +0000074402 00000 n +0000074445 00000 n +0000074531 00000 n +0000074569 00000 n +0000074655 00000 n +0000074697 00000 n +0000074783 00000 n +0000074827 00000 n +0000074913 00000 n +0000074960 00000 n +0000075046 00000 n +0000075148 00000 n +0000075250 00000 n +0000075443 00000 n +0000075547 00000 n +0000075572 00000 n +0000075621 00000 n +0000075707 00000 n +0000075732 00000 n +0000075779 00000 n +0000075866 00000 n +0000075970 00000 n +0000076003 00000 n +0000076056 00000 n +0000076143 00000 n +0000076168 00000 n +0000076272 00000 n +0000076375 00000 n +0000076479 00000 n +0000076520 00000 n +0000076562 00000 n +0000076649 00000 n +0000076692 00000 n +0000076779 00000 n +0000076829 00000 n +0000076916 00000 n +0000076964 00000 n +0000077051 00000 n +0000077100 00000 n +0000077143 00000 n +0000077230 00000 n +0000077284 00000 n +0000077371 00000 n +0000077416 00000 n +0000077503 00000 n +0000077560 00000 n +0000077646 00000 n +0000077742 00000 n +0000077827 00000 n +0000077884 00000 n +0000077930 00000 n +0000078017 00000 n +0000078063 00000 n +0000078148 00000 n +0000078192 00000 n +0000078279 00000 n +0000078330 00000 n +0000078417 00000 n +0000078466 00000 n +0000078553 00000 n 0000078610 00000 n -0000078662 00000 n -0000078748 00000 n -0000078798 00000 n -0000078884 00000 n -0000078930 00000 n -0000079016 00000 n -0000079059 00000 n -0000079145 00000 n -0000079189 00000 n -0000079275 00000 n -0000079318 00000 n -0000079404 00000 n -0000079449 00000 n -0000079535 00000 n -0000079573 00000 n -0000079659 00000 n -0000079701 00000 n -0000079787 00000 n -0000079830 00000 n -0000079916 00000 n -0000079954 00000 n -0000080040 00000 n -0000080082 00000 n -0000080168 00000 n -0000080212 00000 n -0000080298 00000 n -0000080345 00000 n -0000080431 00000 n -0000080533 00000 n -0000080726 00000 n -0000080775 00000 n -0000080861 00000 n -0000080886 00000 n -0000080933 00000 n -0000081020 00000 n -0000081045 00000 n -0000081100 00000 n -0000081187 00000 n -0000081243 00000 n -0000081330 00000 n -0000081363 00000 n -0000081411 00000 n -0000081498 00000 n -0000081572 00000 n -0000081659 00000 n -0000081727 00000 n -0000081814 00000 n -0000081868 00000 n -0000081955 00000 n -0000082023 00000 n -0000082110 00000 n -0000082184 00000 n -0000082271 00000 n -0000082319 00000 n -0000082406 00000 n -0000082463 00000 n -0000082550 00000 n -0000082631 00000 n -0000082686 00000 n +0000078673 00000 n +0000078760 00000 n +0000078818 00000 n +0000078905 00000 n +0000078999 00000 n +0000079085 00000 n +0000079126 00000 n +0000079169 00000 n +0000079255 00000 n +0000079303 00000 n +0000079390 00000 n +0000079431 00000 n +0000079518 00000 n +0000079562 00000 n +0000079649 00000 n +0000079693 00000 n +0000079779 00000 n +0000079836 00000 n +0000079882 00000 n +0000079969 00000 n +0000080018 00000 n +0000080103 00000 n +0000080136 00000 n +0000080190 00000 n +0000080277 00000 n +0000080328 00000 n +0000080415 00000 n +0000080469 00000 n +0000080556 00000 n +0000080606 00000 n +0000080693 00000 n +0000080742 00000 n +0000080792 00000 n +0000080877 00000 n +0000080902 00000 n +0000080966 00000 n +0000081053 00000 n +0000081078 00000 n +0000081130 00000 n +0000081215 00000 n +0000081240 00000 n +0000081304 00000 n +0000081391 00000 n +0000081457 00000 n +0000081544 00000 n +0000081602 00000 n +0000081689 00000 n +0000081783 00000 n +0000081870 00000 n +0000081934 00000 n +0000082021 00000 n +0000082082 00000 n +0000082169 00000 n +0000082234 00000 n +0000082311 00000 n +0000082397 00000 n +0000082422 00000 n +0000082512 00000 n +0000082598 00000 n +0000082687 00000 n 0000082773 00000 n -0000082854 00000 n -0000082941 00000 n -0000082974 00000 n -0000083027 00000 n -0000083114 00000 n -0000083139 00000 n -0000083243 00000 n -0000083346 00000 n -0000083450 00000 n -0000083491 00000 n -0000083533 00000 n -0000083620 00000 n -0000083663 00000 n -0000083750 00000 n -0000083800 00000 n -0000083887 00000 n -0000083935 00000 n -0000084022 00000 n -0000084071 00000 n -0000084114 00000 n -0000084201 00000 n -0000084255 00000 n -0000084342 00000 n -0000084387 00000 n -0000084474 00000 n -0000084531 00000 n -0000084617 00000 n -0000084713 00000 n -0000084798 00000 n -0000084855 00000 n -0000084958 00000 n -0000085062 00000 n -0000085166 00000 n -0000085270 00000 n -0000085374 00000 n -0000085478 00000 n -0000085582 00000 n -0000085686 00000 n -0000085790 00000 n -0000085894 00000 n -0000085997 00000 n -0000086100 00000 n -0000086204 00000 n -0000086308 00000 n -0000086412 00000 n -0000086516 00000 n -0000086620 00000 n -0000086724 00000 n -0000086828 00000 n -0000086932 00000 n -0000087036 00000 n -0000087140 00000 n -0000087244 00000 n -0000087348 00000 n -0000087452 00000 n +0000082844 00000 n +0000082930 00000 n +0000083062 00000 n +0000083148 00000 n +0000083197 00000 n +0000083271 00000 n +0000083357 00000 n +0000083454 00000 n +0000083540 00000 n +0000083605 00000 n +0000083692 00000 n +0000083733 00000 n +0000083798 00000 n +0000083885 00000 n +0000083910 00000 n +0000083972 00000 n +0000084059 00000 n +0000084084 00000 n +0000084133 00000 n +0000084220 00000 n +0000084245 00000 n +0000084293 00000 n +0000084380 00000 n +0000084430 00000 n +0000084514 00000 n +0000084558 00000 n +0000084642 00000 n +0000084683 00000 n +0000084727 00000 n +0000084813 00000 n +0000084863 00000 n +0000084949 00000 n +0000084999 00000 n +0000085085 00000 n +0000085134 00000 n +0000085220 00000 n +0000085267 00000 n +0000085353 00000 n +0000085410 00000 n +0000085492 00000 n +0000085579 00000 n +0000085664 00000 n +0000085751 00000 n +0000085803 00000 n +0000085890 00000 n +0000085942 00000 n +0000086028 00000 n +0000086077 00000 n +0000086192 00000 n +0000086279 00000 n +0000086394 00000 n +0000086480 00000 n +0000086513 00000 n +0000086566 00000 n +0000086653 00000 n +0000086703 00000 n +0000086790 00000 n +0000086823 00000 n +0000086912 00000 n +0000086998 00000 n +0000087061 00000 n +0000087146 00000 n +0000087179 00000 n +0000087240 00000 n +0000087326 00000 n +0000087351 00000 n +0000087470 00000 n 0000087556 00000 n -0000087660 00000 n -0000087764 00000 n -0000087868 00000 n -0000087972 00000 n -0000088076 00000 n -0000088180 00000 n -0000088284 00000 n -0000088388 00000 n -0000088491 00000 n -0000088595 00000 n -0000088699 00000 n -0000088803 00000 n -0000088907 00000 n -0000089011 00000 n -0000089115 00000 n -0000089219 00000 n -0000089322 00000 n -0000089424 00000 n -0000089526 00000 n -0000089903 00000 n -0000090007 00000 n -0000090111 00000 n -0000090215 00000 n -0000090319 00000 n -0000090423 00000 n -0000090527 00000 n -0000090630 00000 n -0000090734 00000 n -0000090838 00000 n -0000090942 00000 n -0000091046 00000 n -0000091150 00000 n -0000091254 00000 n -0000091358 00000 n -0000091462 00000 n -0000091566 00000 n -0000091670 00000 n -0000091774 00000 n -0000091878 00000 n -0000091982 00000 n -0000092086 00000 n -0000092190 00000 n -0000092294 00000 n -0000092398 00000 n -0000092501 00000 n -0000092605 00000 n -0000092709 00000 n -0000092813 00000 n -0000092917 00000 n -0000093020 00000 n -0000093124 00000 n -0000093228 00000 n -0000093332 00000 n -0000093436 00000 n -0000093540 00000 n -0000093644 00000 n -0000093748 00000 n -0000093851 00000 n -0000093955 00000 n -0000094059 00000 n -0000094163 00000 n -0000094267 00000 n -0000094371 00000 n -0000094475 00000 n -0000094579 00000 n -0000094683 00000 n -0000094787 00000 n -0000094891 00000 n -0000094994 00000 n -0000095095 00000 n -0000095197 00000 n -0000095622 00000 n -0000095726 00000 n -0000095830 00000 n -0000095934 00000 n -0000096038 00000 n -0000096142 00000 n -0000096246 00000 n -0000096349 00000 n -0000096453 00000 n -0000096557 00000 n -0000096661 00000 n -0000096764 00000 n -0000096868 00000 n -0000096972 00000 n -0000097076 00000 n -0000097180 00000 n -0000097284 00000 n -0000097388 00000 n -0000097492 00000 n -0000097596 00000 n -0000097700 00000 n -0000097803 00000 n -0000097907 00000 n -0000098011 00000 n -0000098114 00000 n -0000098218 00000 n -0000098322 00000 n -0000098426 00000 n -0000098530 00000 n -0000098634 00000 n -0000098738 00000 n -0000098842 00000 n -0000098946 00000 n -0000099050 00000 n -0000099154 00000 n -0000099258 00000 n -0000099361 00000 n -0000099465 00000 n -0000099569 00000 n -0000099673 00000 n -0000099777 00000 n -0000099881 00000 n -0000099985 00000 n -0000100089 00000 n -0000100193 00000 n -0000100297 00000 n -0000100401 00000 n -0000100505 00000 n -0000100609 00000 n -0000100711 00000 n -0000100813 00000 n -0000100915 00000 n -0000101340 00000 n +0000087599 00000 n +0000087686 00000 n +0000087729 00000 n +0000087816 00000 n +0000087857 00000 n +0000087961 00000 n +0000088064 00000 n +0000088097 00000 n +0000088150 00000 n +0000088237 00000 n +0000088262 00000 n +0000088317 00000 n +0000088404 00000 n +0000088429 00000 n +0000088478 00000 n +0000088565 00000 n +0000088628 00000 n +0000088715 00000 n +0000088778 00000 n +0000088865 00000 n +0000088919 00000 n +0000089006 00000 n +0000089055 00000 n +0000089123 00000 n +0000089209 00000 n +0000089264 00000 n +0000089351 00000 n +0000089384 00000 n +0000089439 00000 n +0000089525 00000 n +0000089593 00000 n +0000089679 00000 n +0000089754 00000 n +0000089841 00000 n +0000089911 00000 n +0000089997 00000 n +0000090076 00000 n +0000090163 00000 n +0000090220 00000 n +0000090302 00000 n +0000090388 00000 n +0000090463 00000 n +0000090550 00000 n +0000090623 00000 n +0000090710 00000 n +0000090788 00000 n +0000090875 00000 n +0000090924 00000 n +0000090972 00000 n +0000091059 00000 n +0000091084 00000 n +0000091132 00000 n +0000091219 00000 n +0000091313 00000 n +0000091400 00000 n +0000091494 00000 n +0000091580 00000 n +0000091621 00000 n +0000091725 00000 n +0000091750 00000 n +0000091805 00000 n +0000091892 00000 n +0000091948 00000 n +0000092035 00000 n +0000092068 00000 n +0000092116 00000 n +0000092203 00000 n +0000092277 00000 n +0000092364 00000 n +0000092432 00000 n +0000092519 00000 n +0000092573 00000 n +0000092660 00000 n +0000092728 00000 n +0000092815 00000 n +0000092889 00000 n +0000092976 00000 n +0000093024 00000 n +0000093111 00000 n +0000093168 00000 n +0000093255 00000 n +0000093336 00000 n +0000093391 00000 n +0000093477 00000 n +0000093558 00000 n +0000093645 00000 n +0000093678 00000 n +0000093732 00000 n +0000093819 00000 n +0000093883 00000 n +0000093970 00000 n +0000094025 00000 n +0000094112 00000 n +0000094216 00000 n +0000094265 00000 n +0000094299 00000 n +0000094333 00000 n +0000101136 00000 n +0000101180 00000 n +0000101224 00000 n +0000101268 00000 n +0000101312 00000 n +0000101356 00000 n +0000101400 00000 n 0000101444 00000 n -0000101548 00000 n -0000101652 00000 n -0000101756 00000 n -0000101859 00000 n -0000101963 00000 n -0000102067 00000 n -0000102140 00000 n -0000102186 00000 n -0000102273 00000 n -0000102319 00000 n -0000102404 00000 n -0000102448 00000 n -0000102535 00000 n -0000102586 00000 n -0000102673 00000 n -0000102722 00000 n -0000102809 00000 n -0000102866 00000 n -0000102929 00000 n -0000103016 00000 n -0000103074 00000 n -0000103161 00000 n -0000103255 00000 n -0000103341 00000 n -0000103383 00000 n -0000103427 00000 n -0000103515 00000 n -0000103564 00000 n -0000103653 00000 n -0000103695 00000 n -0000103784 00000 n -0000103829 00000 n -0000103918 00000 n -0000103963 00000 n -0000104051 00000 n -0000104114 00000 n -0000104161 00000 n -0000104250 00000 n -0000104300 00000 n -0000104387 00000 n -0000104423 00000 n -0000104478 00000 n -0000104567 00000 n -0000104619 00000 n -0000104708 00000 n -0000104763 00000 n -0000104852 00000 n +0000101488 00000 n +0000101532 00000 n +0000101576 00000 n +0000101620 00000 n +0000101664 00000 n +0000101708 00000 n +0000101753 00000 n +0000101798 00000 n +0000101843 00000 n +0000101888 00000 n +0000101933 00000 n +0000101978 00000 n +0000102023 00000 n +0000102068 00000 n +0000102113 00000 n +0000102158 00000 n +0000102203 00000 n +0000102248 00000 n +0000102293 00000 n +0000102338 00000 n +0000102383 00000 n +0000102428 00000 n +0000102473 00000 n +0000102518 00000 n +0000102563 00000 n +0000102608 00000 n +0000102653 00000 n +0000102698 00000 n +0000102743 00000 n +0000102788 00000 n +0000102833 00000 n +0000102878 00000 n +0000102923 00000 n +0000102968 00000 n +0000103013 00000 n +0000103058 00000 n +0000103103 00000 n +0000103148 00000 n +0000103193 00000 n +0000103238 00000 n +0000103283 00000 n +0000103328 00000 n +0000103373 00000 n +0000103418 00000 n +0000103463 00000 n +0000103508 00000 n +0000103553 00000 n +0000103598 00000 n +0000103643 00000 n +0000103688 00000 n +0000103733 00000 n +0000103778 00000 n +0000103823 00000 n +0000103868 00000 n +0000103913 00000 n +0000103958 00000 n +0000104003 00000 n +0000104048 00000 n +0000104093 00000 n +0000104138 00000 n +0000104183 00000 n +0000104228 00000 n +0000104273 00000 n +0000104318 00000 n +0000104363 00000 n +0000104408 00000 n +0000104453 00000 n +0000104498 00000 n +0000104543 00000 n +0000104588 00000 n +0000104633 00000 n +0000104678 00000 n +0000104723 00000 n +0000104768 00000 n +0000104813 00000 n +0000104858 00000 n 0000104903 00000 n -0000104992 00000 n -0000105046 00000 n -0000105097 00000 n -0000105184 00000 n -0000105211 00000 n -0000105276 00000 n -0000105365 00000 n -0000105392 00000 n -0000105445 00000 n -0000105532 00000 n -0000105559 00000 n -0000105624 00000 n +0000104948 00000 n +0000104993 00000 n +0000105038 00000 n +0000105083 00000 n +0000105128 00000 n +0000105173 00000 n +0000105218 00000 n +0000105263 00000 n +0000105308 00000 n +0000105353 00000 n +0000105398 00000 n +0000105443 00000 n +0000105488 00000 n +0000105533 00000 n +0000105578 00000 n +0000105623 00000 n +0000105668 00000 n 0000105713 00000 n -0000105780 00000 n -0000105869 00000 n -0000105928 00000 n -0000106017 00000 n -0000106112 00000 n -0000106201 00000 n -0000106266 00000 n -0000106355 00000 n -0000106417 00000 n -0000106506 00000 n -0000106578 00000 n -0000106656 00000 n -0000106744 00000 n -0000106771 00000 n -0000106862 00000 n -0000106950 00000 n -0000107040 00000 n -0000107128 00000 n -0000107200 00000 n +0000105758 00000 n +0000105803 00000 n +0000105848 00000 n +0000105893 00000 n +0000105938 00000 n +0000105983 00000 n +0000106028 00000 n +0000106073 00000 n +0000106118 00000 n +0000106163 00000 n +0000106208 00000 n +0000106253 00000 n +0000106298 00000 n +0000106343 00000 n +0000106388 00000 n +0000106433 00000 n +0000106478 00000 n +0000106523 00000 n +0000106568 00000 n +0000106613 00000 n +0000106658 00000 n +0000106703 00000 n +0000106748 00000 n +0000106793 00000 n +0000106838 00000 n +0000106883 00000 n +0000106928 00000 n +0000106973 00000 n +0000107018 00000 n +0000107063 00000 n +0000107108 00000 n +0000107153 00000 n +0000107198 00000 n +0000107243 00000 n 0000107288 00000 n -0000107421 00000 n -0000107509 00000 n -0000107563 00000 n -0000107638 00000 n -0000107726 00000 n -0000107824 00000 n -0000107912 00000 n -0000107978 00000 n -0000108067 00000 n -0000108112 00000 n -0000108178 00000 n -0000108267 00000 n -0000108294 00000 n -0000108357 00000 n -0000108446 00000 n -0000108473 00000 n -0000108523 00000 n -0000108612 00000 n -0000108639 00000 n -0000108688 00000 n -0000108777 00000 n -0000108828 00000 n -0000108914 00000 n -0000108959 00000 n -0000109045 00000 n -0000109090 00000 n -0000109135 00000 n +0000107333 00000 n +0000107378 00000 n +0000107423 00000 n +0000107468 00000 n +0000107513 00000 n +0000107558 00000 n +0000107603 00000 n +0000107648 00000 n +0000107693 00000 n +0000107738 00000 n +0000107783 00000 n +0000107828 00000 n +0000107873 00000 n +0000107918 00000 n +0000107963 00000 n +0000108008 00000 n +0000108053 00000 n +0000108098 00000 n +0000108143 00000 n +0000108188 00000 n +0000108233 00000 n +0000108278 00000 n +0000108323 00000 n +0000108368 00000 n +0000108413 00000 n +0000108458 00000 n +0000108503 00000 n +0000108548 00000 n +0000108593 00000 n +0000108638 00000 n +0000108683 00000 n +0000108728 00000 n +0000108773 00000 n +0000108818 00000 n +0000108863 00000 n +0000108908 00000 n +0000108953 00000 n +0000108998 00000 n +0000109043 00000 n +0000109088 00000 n +0000109133 00000 n +0000109178 00000 n 0000109223 00000 n -0000109274 00000 n -0000109362 00000 n -0000109413 00000 n -0000109501 00000 n -0000109551 00000 n -0000109639 00000 n -0000109687 00000 n -0000109775 00000 n -0000109838 00000 n -0000109921 00000 n -0000110010 00000 n -0000110096 00000 n -0000110185 00000 n -0000110238 00000 n -0000110327 00000 n -0000110380 00000 n -0000110468 00000 n -0000110522 00000 n -0000110638 00000 n -0000110727 00000 n +0000109268 00000 n +0000109313 00000 n +0000109358 00000 n +0000109403 00000 n +0000109448 00000 n +0000109493 00000 n +0000109538 00000 n +0000109583 00000 n +0000109628 00000 n +0000109673 00000 n +0000109718 00000 n +0000109763 00000 n +0000109808 00000 n +0000109853 00000 n +0000109898 00000 n +0000109943 00000 n +0000109988 00000 n +0000110033 00000 n +0000110078 00000 n +0000110123 00000 n +0000110168 00000 n +0000110213 00000 n +0000110258 00000 n +0000110303 00000 n +0000110348 00000 n +0000110393 00000 n +0000110438 00000 n +0000110483 00000 n +0000110528 00000 n +0000110573 00000 n +0000110618 00000 n +0000110663 00000 n +0000110708 00000 n +0000110753 00000 n +0000110798 00000 n 0000110843 00000 n -0000110931 00000 n -0000110967 00000 n -0000111021 00000 n -0000111110 00000 n -0000111161 00000 n -0000111250 00000 n -0000111286 00000 n -0000111376 00000 n -0000111464 00000 n -0000111528 00000 n -0000111615 00000 n -0000111651 00000 n -0000111713 00000 n -0000111801 00000 n -0000111828 00000 n -0000111948 00000 n -0000112036 00000 n -0000112080 00000 n -0000112169 00000 n -0000112213 00000 n -0000112302 00000 n -0000112347 00000 n -0000112452 00000 n -0000112556 00000 n -0000112592 00000 n -0000112646 00000 n -0000112735 00000 n -0000112762 00000 n -0000112818 00000 n -0000112907 00000 n -0000112934 00000 n -0000113038 00000 n -0000113143 00000 n -0000113248 00000 n -0000113353 00000 n -0000113458 00000 n -0000113563 00000 n -0000113668 00000 n -0000113773 00000 n -0000113878 00000 n -0000113982 00000 n -0000114087 00000 n -0000114192 00000 n -0000114297 00000 n -0000114402 00000 n -0000114506 00000 n -0000114611 00000 n -0000114716 00000 n -0000114821 00000 n -0000114926 00000 n -0000115031 00000 n -0000115136 00000 n -0000115241 00000 n -0000115346 00000 n -0000115451 00000 n -0000115556 00000 n -0000115660 00000 n -0000115765 00000 n -0000115870 00000 n -0000115975 00000 n -0000116080 00000 n -0000116185 00000 n -0000116290 00000 n -0000116394 00000 n -0000116499 00000 n -0000116604 00000 n -0000116709 00000 n -0000116814 00000 n -0000116919 00000 n -0000117024 00000 n -0000117129 00000 n -0000117234 00000 n -0000117339 00000 n -0000117444 00000 n -0000117549 00000 n -0000117653 00000 n -0000117756 00000 n -0000117859 00000 n -0000118300 00000 n -0000118405 00000 n -0000118509 00000 n -0000118614 00000 n -0000118719 00000 n -0000118824 00000 n -0000118929 00000 n -0000119034 00000 n -0000119139 00000 n -0000119244 00000 n -0000119349 00000 n -0000119454 00000 n -0000119558 00000 n -0000119663 00000 n -0000119768 00000 n -0000119873 00000 n -0000119978 00000 n -0000120083 00000 n -0000120188 00000 n -0000120292 00000 n -0000120397 00000 n -0000120502 00000 n -0000120607 00000 n -0000120712 00000 n -0000120937 00000 n -0000120993 00000 n -0000121081 00000 n -0000121150 00000 n -0000121238 00000 n -0000121314 00000 n -0000121403 00000 n -0000121474 00000 n -0000121562 00000 n -0000121642 00000 n -0000121731 00000 n -0000121794 00000 n -0000121877 00000 n -0000121965 00000 n -0000122041 00000 n -0000122130 00000 n -0000122204 00000 n -0000122293 00000 n -0000122372 00000 n -0000122461 00000 n -0000122515 00000 n -0000122564 00000 n -0000122653 00000 n -0000122680 00000 n -0000122729 00000 n -0000122818 00000 n -0000122913 00000 n -0000123002 00000 n -0000123097 00000 n -0000123185 00000 n -0000123230 00000 n -0000123280 00000 n -0000123369 00000 n -0000123433 00000 n -0000123522 00000 n -0000123586 00000 n -0000123675 00000 n -0000123730 00000 n -0000123819 00000 n -0000123873 00000 n -0000123942 00000 n -0000124030 00000 n -0000124086 00000 n -0000124175 00000 n -0000124211 00000 n -0000124266 00000 n -0000124355 00000 n -0000124420 00000 n -0000124509 00000 n -0000124565 00000 n -0000124654 00000 n -0000124759 00000 n -0000124813 00000 n -0000124868 00000 n -0000124957 00000 n -0000125012 00000 n -0000125101 00000 n -0000125137 00000 n -0000125173 00000 n -0000125209 00000 n -0000131622 00000 n -0000131667 00000 n -0000131712 00000 n -0000131757 00000 n -0000131802 00000 n -0000131847 00000 n -0000131892 00000 n -0000131937 00000 n -0000131982 00000 n -0000132027 00000 n -0000132072 00000 n -0000132117 00000 n -0000132162 00000 n -0000132207 00000 n -0000132252 00000 n -0000132297 00000 n -0000132342 00000 n -0000132387 00000 n -0000132432 00000 n -0000132477 00000 n -0000132522 00000 n -0000132567 00000 n -0000132612 00000 n -0000132657 00000 n -0000132702 00000 n -0000132747 00000 n -0000132792 00000 n -0000132837 00000 n -0000132882 00000 n -0000132927 00000 n -0000132972 00000 n -0000133017 00000 n -0000133062 00000 n -0000133107 00000 n -0000133152 00000 n -0000133197 00000 n -0000133242 00000 n -0000133287 00000 n -0000133332 00000 n -0000133377 00000 n -0000133422 00000 n -0000133467 00000 n -0000133512 00000 n -0000133557 00000 n -0000133602 00000 n -0000133647 00000 n -0000133692 00000 n -0000133737 00000 n -0000133782 00000 n -0000133827 00000 n -0000133872 00000 n -0000133917 00000 n -0000133962 00000 n -0000134007 00000 n -0000134052 00000 n -0000134097 00000 n -0000134142 00000 n -0000134187 00000 n -0000134232 00000 n -0000134277 00000 n -0000134322 00000 n -0000134367 00000 n -0000134412 00000 n -0000134457 00000 n -0000134502 00000 n -0000134547 00000 n -0000134592 00000 n -0000134637 00000 n -0000134682 00000 n -0000134727 00000 n -0000134772 00000 n -0000134817 00000 n -0000134862 00000 n -0000134907 00000 n -0000134952 00000 n -0000134997 00000 n -0000135042 00000 n -0000135087 00000 n -0000135132 00000 n -0000135177 00000 n -0000135222 00000 n -0000135267 00000 n -0000135312 00000 n -0000135357 00000 n -0000135402 00000 n -0000135447 00000 n -0000135492 00000 n -0000135537 00000 n -0000135582 00000 n -0000135627 00000 n -0000135672 00000 n -0000135717 00000 n -0000135762 00000 n -0000135807 00000 n -0000135852 00000 n -0000135897 00000 n -0000135942 00000 n -0000135987 00000 n -0000136032 00000 n -0000136077 00000 n -0000136122 00000 n -0000136167 00000 n -0000136212 00000 n -0000136257 00000 n -0000136302 00000 n -0000136347 00000 n -0000136392 00000 n -0000136437 00000 n -0000136482 00000 n -0000136527 00000 n -0000136572 00000 n -0000136617 00000 n -0000136662 00000 n -0000136707 00000 n -0000136752 00000 n -0000136797 00000 n -0000136842 00000 n -0000136887 00000 n -0000136932 00000 n -0000136977 00000 n -0000137022 00000 n -0000137067 00000 n -0000137112 00000 n -0000137157 00000 n -0000137202 00000 n -0000137247 00000 n -0000137292 00000 n -0000137337 00000 n -0000137382 00000 n -0000137427 00000 n -0000137472 00000 n -0000137517 00000 n -0000137562 00000 n -0000137607 00000 n -0000137652 00000 n -0000137697 00000 n -0000137742 00000 n -0000137787 00000 n -0000137832 00000 n -0000137877 00000 n -0000137922 00000 n -0000137967 00000 n -0000138012 00000 n -0000138057 00000 n -0000138102 00000 n -0000138147 00000 n -0000138192 00000 n -0000138237 00000 n -0000138282 00000 n -0000138327 00000 n -0000138372 00000 n -0000138417 00000 n -0000138462 00000 n -0000138507 00000 n -0000138552 00000 n -0000138597 00000 n -0000138642 00000 n -0000138687 00000 n -0000138732 00000 n -0000138777 00000 n -0000138822 00000 n -0000138867 00000 n -0000138912 00000 n -0000138957 00000 n -0000139002 00000 n -0000139047 00000 n -0000139092 00000 n -0000139137 00000 n -0000139182 00000 n -0000139227 00000 n -0000139272 00000 n -0000139317 00000 n -0000139362 00000 n -0000139407 00000 n -0000139452 00000 n -0000139497 00000 n -0000139542 00000 n -0000139587 00000 n -0000139632 00000 n -0000139677 00000 n -0000139722 00000 n -0000139767 00000 n -0000139812 00000 n -0000139857 00000 n -0000139902 00000 n -0000139947 00000 n -0000139992 00000 n -0000140037 00000 n -0000140082 00000 n -0000140127 00000 n -0000140172 00000 n -0000140217 00000 n -0000140262 00000 n -0000140307 00000 n -0000140352 00000 n -0000140397 00000 n -0000140442 00000 n -0000140487 00000 n -0000140532 00000 n -0000140577 00000 n -0000140622 00000 n -0000140667 00000 n -0000140712 00000 n -0000140757 00000 n -0000140802 00000 n -0000140847 00000 n -0000140892 00000 n -0000140937 00000 n -0000140982 00000 n -0000141027 00000 n -0000141072 00000 n -0000141117 00000 n -0000141162 00000 n -0000141207 00000 n -0000141252 00000 n -0000141297 00000 n -0000141342 00000 n -0000141387 00000 n -0000141432 00000 n -0000141477 00000 n -0000141522 00000 n -0000141567 00000 n -0000141612 00000 n -0000141657 00000 n -0000141702 00000 n -0000141747 00000 n -0000141792 00000 n -0000141837 00000 n -0000141882 00000 n -0000141927 00000 n -0000141972 00000 n -0000142017 00000 n -0000142062 00000 n -0000142107 00000 n -0000142152 00000 n -0000142197 00000 n -0000142242 00000 n -0000142287 00000 n -0000142332 00000 n -0000142377 00000 n -0000142422 00000 n -0000142467 00000 n -0000142512 00000 n -0000142557 00000 n -0000142602 00000 n -0000142647 00000 n -0000142692 00000 n -0000142737 00000 n -0000142782 00000 n -0000142827 00000 n -0000142872 00000 n -0000142917 00000 n -0000142962 00000 n -0000143007 00000 n -0000143052 00000 n -0000143097 00000 n -0000143142 00000 n -0000143187 00000 n -0000143232 00000 n -0000143277 00000 n -0000143322 00000 n -0000143367 00000 n -0000143412 00000 n -0000143457 00000 n -0000143502 00000 n -0000143547 00000 n -0000143592 00000 n -0000143637 00000 n -0000143682 00000 n -0000143727 00000 n -0000143772 00000 n -0000143817 00000 n -0000143862 00000 n -0000143907 00000 n -0000143952 00000 n -0000143997 00000 n -0000144042 00000 n -0000144087 00000 n -0000144132 00000 n -0000144177 00000 n -0000144222 00000 n -0000144267 00000 n -0000144312 00000 n -0000144357 00000 n -0000144402 00000 n -0000144447 00000 n -0000144492 00000 n -0000144537 00000 n -0000144582 00000 n -0000144627 00000 n -0000144672 00000 n -0000144717 00000 n -0000144762 00000 n -0000144807 00000 n -0000144852 00000 n -0000144897 00000 n -0000144942 00000 n -0000144987 00000 n -0000145032 00000 n -0000145077 00000 n -0000145122 00000 n -0000145167 00000 n -0000145212 00000 n -0000145257 00000 n -0000145302 00000 n -0000145347 00000 n -0000145392 00000 n -0000145437 00000 n -0000145482 00000 n -0000145527 00000 n -0000145572 00000 n -0000145617 00000 n -0000145662 00000 n -0000145707 00000 n -0000145752 00000 n -0000145797 00000 n -0000145842 00000 n -0000145887 00000 n -0000145932 00000 n -0000145977 00000 n -0000146022 00000 n -0000146067 00000 n -0000146112 00000 n -0000146157 00000 n -0000146202 00000 n -0000146247 00000 n -0000146292 00000 n -0000146337 00000 n -0000146382 00000 n -0000146427 00000 n -0000146472 00000 n -0000146517 00000 n -0000146562 00000 n -0000146607 00000 n -0000146652 00000 n -0000146697 00000 n -0000146742 00000 n -0000146787 00000 n -0000146832 00000 n -0000146877 00000 n -0000146922 00000 n -0000146967 00000 n -0000147012 00000 n -0000147057 00000 n -0000147102 00000 n -0000147147 00000 n -0000147192 00000 n -0000147237 00000 n -0000147281 00000 n -0000147326 00000 n -0000147371 00000 n -0000147416 00000 n -0000147461 00000 n -0000147506 00000 n -0000147551 00000 n -0000147596 00000 n -0000147641 00000 n -0000147686 00000 n -0000147731 00000 n -0000147776 00000 n -0000147821 00000 n -0000147866 00000 n -0000147911 00000 n -0000147956 00000 n -0000148001 00000 n -0000148045 00000 n -0000148090 00000 n -0000148135 00000 n -0000148180 00000 n -0000148225 00000 n -0000150029 00000 n -0000150190 00000 n -0000150359 00000 n -0000150552 00000 n -0000154620 00000 n -0000154814 00000 n -0000158925 00000 n -0000159119 00000 n -0000163276 00000 n -0000163470 00000 n -0000167507 00000 n -0000167701 00000 n -0000171582 00000 n -0000171776 00000 n -0000175525 00000 n -0000175719 00000 n -0000179713 00000 n -0000179907 00000 n -0000182575 00000 n -0000182787 00000 n -0000184960 00000 n -0000185144 00000 n -0000188235 00000 n -0000188419 00000 n -0000191537 00000 n -0000191712 00000 n -0000194089 00000 n -0000194264 00000 n -0000195221 00000 n -0000195382 00000 n -0000195570 00000 n -0000195782 00000 n -0000198529 00000 n -0000198741 00000 n -0000200250 00000 n -0000200467 00000 n -0000201900 00000 n -0000202112 00000 n -0000204045 00000 n -0000204205 00000 n -0000204540 00000 n -0000204760 00000 n -0000206585 00000 n -0000206783 00000 n -0000208712 00000 n -0000208919 00000 n -0000210838 00000 n -0000211056 00000 n -0000213367 00000 n -0000213536 00000 n -0000214339 00000 n -0000214568 00000 n -0000216437 00000 n -0000216634 00000 n -0000218173 00000 n -0000218370 00000 n -0000219866 00000 n -0000220089 00000 n -0000222258 00000 n -0000222461 00000 n -0000224365 00000 n -0000224579 00000 n -0000225880 00000 n -0000226112 00000 n -0000227785 00000 n -0000227998 00000 n -0000229902 00000 n -0000230110 00000 n -0000231388 00000 n -0000231627 00000 n -0000233223 00000 n -0000233420 00000 n -0000234678 00000 n -0000234839 00000 n -0000235029 00000 n -0000235241 00000 n -0000238097 00000 n -0000238272 00000 n -0000238620 00000 n -0000238809 00000 n -0000240495 00000 n -0000240683 00000 n -0000242119 00000 n -0000242316 00000 n -0000244077 00000 n -0000244257 00000 n -0000246221 00000 n -0000246434 00000 n -0000248232 00000 n -0000248454 00000 n -0000249511 00000 n -0000249756 00000 n -0000251176 00000 n -0000251390 00000 n -0000252927 00000 n -0000253125 00000 n -0000255156 00000 n -0000255421 00000 n -0000257177 00000 n -0000257390 00000 n -0000258967 00000 n -0000259174 00000 n -0000261169 00000 n -0000261401 00000 n -0000263430 00000 n -0000263642 00000 n -0000265623 00000 n -0000265836 00000 n -0000268040 00000 n -0000268270 00000 n -0000270457 00000 n -0000270617 00000 n -0000271354 00000 n -0000271548 00000 n -0000273104 00000 n -0000273284 00000 n -0000275025 00000 n -0000275214 00000 n -0000276415 00000 n -0000276680 00000 n -0000278146 00000 n -0000278344 00000 n -0000279324 00000 n -0000279556 00000 n -0000280958 00000 n -0000281193 00000 n -0000283109 00000 n -0000283270 00000 n -0000283463 00000 n -0000283675 00000 n -0000286495 00000 n -0000286670 00000 n -0000289488 00000 n -0000289672 00000 n -0000292249 00000 n -0000292424 00000 n -0000292986 00000 n -0000293225 00000 n -0000294981 00000 n -0000295188 00000 n -0000297028 00000 n -0000297226 00000 n -0000298870 00000 n -0000299082 00000 n -0000300498 00000 n -0000300677 00000 n -0000301494 00000 n -0000301691 00000 n -0000303183 00000 n -0000303448 00000 n -0000305172 00000 n -0000305419 00000 n -0000307345 00000 n -0000307578 00000 n -0000309589 00000 n -0000309822 00000 n -0000311475 00000 n -0000311680 00000 n -0000313024 00000 n -0000313247 00000 n -0000314812 00000 n -0000314991 00000 n -0000316561 00000 n -0000316740 00000 n -0000318262 00000 n -0000318441 00000 n -0000319945 00000 n -0000320124 00000 n -0000321791 00000 n -0000321961 00000 n -0000322707 00000 n -0000322930 00000 n -0000324855 00000 n -0000325096 00000 n -0000326825 00000 n -0000327037 00000 n -0000329096 00000 n -0000329294 00000 n -0000331348 00000 n -0000331555 00000 n -0000333372 00000 n -0000333586 00000 n -0000335691 00000 n -0000335898 00000 n -0000337646 00000 n -0000337833 00000 n -0000339513 00000 n -0000339702 00000 n -0000340595 00000 n -0000340765 00000 n -0000341863 00000 n -0000342033 00000 n -0000342724 00000 n -0000342894 00000 n -0000343755 00000 n -0000343925 00000 n -0000345026 00000 n -0000345250 00000 n -0000346632 00000 n -0000346849 00000 n -0000348630 00000 n -0000348866 00000 n -0000350741 00000 n -0000350920 00000 n -0000352805 00000 n -0000352974 00000 n -0000354481 00000 n -0000354729 00000 n -0000357062 00000 n -0000357294 00000 n -0000359488 00000 n -0000359708 00000 n -0000361577 00000 n -0000361796 00000 n -0000363454 00000 n -0000363643 00000 n -0000365336 00000 n -0000365515 00000 n -0000367260 00000 n -0000367448 00000 n -0000369283 00000 n -0000369478 00000 n -0000371394 00000 n -0000371626 00000 n -0000373730 00000 n -0000373943 00000 n -0000375379 00000 n -0000375593 00000 n -0000377042 00000 n -0000377249 00000 n -0000378486 00000 n -0000378665 00000 n -0000379653 00000 n -0000379841 00000 n -0000380973 00000 n -0000381161 00000 n -0000382662 00000 n -0000382850 00000 n -0000383933 00000 n -0000384122 00000 n -0000385455 00000 n -0000385661 00000 n -0000387311 00000 n -0000387566 00000 n -0000389244 00000 n -0000389448 00000 n -0000391400 00000 n -0000391597 00000 n -0000393797 00000 n -0000394017 00000 n -0000395994 00000 n -0000396182 00000 n -0000397919 00000 n -0000398159 00000 n -0000399676 00000 n -0000399873 00000 n -0000401698 00000 n -0000401886 00000 n -0000403885 00000 n -0000404128 00000 n -0000405952 00000 n -0000406141 00000 n -0000407775 00000 n -0000407996 00000 n -0000409695 00000 n -0000409917 00000 n -0000411573 00000 n -0000411752 00000 n -0000413642 00000 n -0000413820 00000 n -0000415161 00000 n -0000415393 00000 n +0000110888 00000 n +0000110933 00000 n +0000110978 00000 n +0000111023 00000 n +0000111068 00000 n +0000111113 00000 n +0000111158 00000 n +0000111203 00000 n +0000111248 00000 n +0000111293 00000 n +0000111338 00000 n +0000111383 00000 n +0000111428 00000 n +0000111473 00000 n +0000111518 00000 n +0000111563 00000 n +0000111608 00000 n +0000111653 00000 n +0000111698 00000 n +0000111743 00000 n +0000111788 00000 n +0000111833 00000 n +0000111878 00000 n +0000111923 00000 n +0000111968 00000 n +0000112013 00000 n +0000112058 00000 n +0000112103 00000 n +0000112148 00000 n +0000112193 00000 n +0000112238 00000 n +0000112283 00000 n +0000112328 00000 n +0000112373 00000 n +0000112418 00000 n +0000112463 00000 n +0000112508 00000 n +0000112553 00000 n +0000112598 00000 n +0000112643 00000 n +0000112688 00000 n +0000112733 00000 n +0000112778 00000 n +0000112823 00000 n +0000112868 00000 n +0000112913 00000 n +0000112958 00000 n +0000113003 00000 n +0000113048 00000 n +0000113093 00000 n +0000113138 00000 n +0000113183 00000 n +0000113228 00000 n +0000113273 00000 n +0000113318 00000 n +0000113363 00000 n +0000113408 00000 n +0000113453 00000 n +0000113498 00000 n +0000113543 00000 n +0000113588 00000 n +0000113633 00000 n +0000113678 00000 n +0000113723 00000 n +0000113768 00000 n +0000113813 00000 n +0000113858 00000 n +0000113903 00000 n +0000113948 00000 n +0000113993 00000 n +0000114038 00000 n +0000114083 00000 n +0000114128 00000 n +0000114173 00000 n +0000114218 00000 n +0000114263 00000 n +0000114308 00000 n +0000114353 00000 n +0000114398 00000 n +0000114443 00000 n +0000114488 00000 n +0000114533 00000 n +0000114578 00000 n +0000114623 00000 n +0000114668 00000 n +0000114713 00000 n +0000114758 00000 n +0000114803 00000 n +0000114848 00000 n +0000114893 00000 n +0000114938 00000 n +0000114983 00000 n +0000115028 00000 n +0000115073 00000 n +0000115118 00000 n +0000115163 00000 n +0000115208 00000 n +0000115253 00000 n +0000115298 00000 n +0000115343 00000 n +0000115388 00000 n +0000115433 00000 n +0000115478 00000 n +0000115523 00000 n +0000115568 00000 n +0000115613 00000 n +0000115658 00000 n +0000115703 00000 n +0000115748 00000 n +0000115793 00000 n +0000115838 00000 n +0000115883 00000 n +0000115928 00000 n +0000115973 00000 n +0000116018 00000 n +0000116063 00000 n +0000116108 00000 n +0000116153 00000 n +0000116198 00000 n +0000116243 00000 n +0000116288 00000 n +0000116333 00000 n +0000116378 00000 n +0000116423 00000 n +0000116468 00000 n +0000116513 00000 n +0000116558 00000 n +0000116603 00000 n +0000116648 00000 n +0000116693 00000 n +0000116738 00000 n +0000116783 00000 n +0000116828 00000 n +0000116873 00000 n +0000116918 00000 n +0000116963 00000 n +0000117008 00000 n +0000117053 00000 n +0000117098 00000 n +0000117143 00000 n +0000117188 00000 n +0000117233 00000 n +0000117278 00000 n +0000117323 00000 n +0000117368 00000 n +0000117413 00000 n +0000117458 00000 n +0000117503 00000 n +0000117548 00000 n +0000117593 00000 n +0000117638 00000 n +0000117683 00000 n +0000117728 00000 n +0000117773 00000 n +0000117817 00000 n +0000117862 00000 n +0000117907 00000 n +0000117952 00000 n +0000117997 00000 n +0000118042 00000 n +0000118087 00000 n +0000118132 00000 n +0000118177 00000 n +0000118222 00000 n +0000118267 00000 n +0000118312 00000 n +0000118357 00000 n +0000118402 00000 n +0000118447 00000 n +0000118492 00000 n +0000118537 00000 n +0000118582 00000 n +0000118627 00000 n +0000118672 00000 n +0000118717 00000 n +0000118762 00000 n +0000118807 00000 n +0000120647 00000 n +0000120808 00000 n +0000120977 00000 n +0000121170 00000 n +0000125071 00000 n +0000125265 00000 n +0000129072 00000 n +0000129266 00000 n +0000134424 00000 n +0000134618 00000 n +0000138781 00000 n +0000138975 00000 n +0000142887 00000 n +0000143081 00000 n +0000146904 00000 n +0000147098 00000 n +0000150869 00000 n +0000151063 00000 n +0000155066 00000 n +0000155260 00000 n +0000156680 00000 n +0000156892 00000 n +0000158867 00000 n +0000159051 00000 n +0000162262 00000 n +0000162446 00000 n +0000165347 00000 n +0000165522 00000 n +0000168280 00000 n +0000168455 00000 n +0000170117 00000 n +0000170278 00000 n +0000170466 00000 n +0000170636 00000 n +0000170948 00000 n +0000171137 00000 n +0000173323 00000 n +0000173503 00000 n +0000175677 00000 n +0000175866 00000 n +0000178037 00000 n +0000178216 00000 n +0000179409 00000 n +0000179621 00000 n +0000181131 00000 n +0000181348 00000 n +0000182781 00000 n +0000182984 00000 n +0000184908 00000 n +0000185128 00000 n +0000186954 00000 n +0000187152 00000 n +0000189080 00000 n +0000189287 00000 n +0000191205 00000 n +0000191414 00000 n +0000193726 00000 n +0000193914 00000 n +0000195105 00000 n +0000195334 00000 n +0000197203 00000 n +0000197432 00000 n +0000198999 00000 n +0000199196 00000 n +0000200691 00000 n +0000200904 00000 n +0000203089 00000 n +0000203292 00000 n +0000205041 00000 n +0000205255 00000 n +0000206667 00000 n +0000206889 00000 n +0000208588 00000 n +0000208792 00000 n +0000210540 00000 n +0000210738 00000 n +0000211964 00000 n +0000212203 00000 n +0000213822 00000 n +0000214019 00000 n +0000215192 00000 n +0000215353 00000 n +0000215543 00000 n +0000215713 00000 n +0000216011 00000 n +0000216200 00000 n +0000217886 00000 n +0000218074 00000 n +0000219505 00000 n +0000219702 00000 n +0000221463 00000 n +0000221643 00000 n +0000223607 00000 n +0000223820 00000 n +0000225617 00000 n +0000225839 00000 n +0000226896 00000 n +0000227126 00000 n +0000228519 00000 n +0000228733 00000 n +0000230256 00000 n +0000230469 00000 n +0000232473 00000 n +0000232747 00000 n +0000234532 00000 n +0000234745 00000 n +0000236356 00000 n +0000236554 00000 n +0000238221 00000 n +0000238400 00000 n +0000240432 00000 n +0000240662 00000 n +0000242482 00000 n +0000242676 00000 n +0000244231 00000 n +0000244411 00000 n +0000246151 00000 n +0000246340 00000 n +0000247541 00000 n +0000247806 00000 n +0000249273 00000 n +0000249471 00000 n +0000250451 00000 n +0000250683 00000 n +0000252086 00000 n +0000252321 00000 n +0000254238 00000 n +0000254399 00000 n +0000254592 00000 n +0000254762 00000 n +0000255062 00000 n +0000255301 00000 n +0000257056 00000 n +0000257263 00000 n +0000259107 00000 n +0000259305 00000 n +0000260950 00000 n +0000261162 00000 n +0000262578 00000 n +0000262757 00000 n +0000263574 00000 n +0000263771 00000 n +0000265266 00000 n +0000265530 00000 n +0000267253 00000 n +0000267499 00000 n +0000269427 00000 n +0000269659 00000 n +0000271669 00000 n +0000271901 00000 n +0000273553 00000 n +0000273757 00000 n +0000275102 00000 n +0000275324 00000 n +0000276887 00000 n +0000277066 00000 n +0000278635 00000 n +0000278814 00000 n +0000280334 00000 n +0000280513 00000 n +0000282016 00000 n +0000282195 00000 n +0000283861 00000 n +0000284031 00000 n +0000284776 00000 n +0000284998 00000 n +0000286916 00000 n +0000287157 00000 n +0000288886 00000 n +0000289098 00000 n +0000291157 00000 n +0000291355 00000 n +0000293409 00000 n +0000293616 00000 n +0000295434 00000 n +0000295647 00000 n +0000297750 00000 n +0000297957 00000 n +0000299706 00000 n +0000299893 00000 n +0000301572 00000 n +0000301761 00000 n +0000302653 00000 n +0000302823 00000 n +0000303921 00000 n +0000304091 00000 n +0000304782 00000 n +0000304952 00000 n +0000305813 00000 n +0000305983 00000 n +0000307084 00000 n +0000307307 00000 n +0000308689 00000 n +0000308905 00000 n +0000310685 00000 n +0000310920 00000 n +0000312904 00000 n +0000313083 00000 n +0000314886 00000 n +0000315055 00000 n +0000316566 00000 n +0000316824 00000 n +0000319173 00000 n +0000319394 00000 n +0000321537 00000 n +0000321757 00000 n +0000323626 00000 n +0000323845 00000 n +0000325503 00000 n +0000325692 00000 n +0000327384 00000 n +0000327563 00000 n +0000329308 00000 n +0000329496 00000 n +0000331330 00000 n +0000331524 00000 n +0000333439 00000 n +0000333670 00000 n +0000335775 00000 n +0000335987 00000 n +0000337423 00000 n +0000337636 00000 n +0000339085 00000 n +0000339292 00000 n +0000340529 00000 n +0000340708 00000 n +0000341695 00000 n +0000341883 00000 n +0000343015 00000 n +0000343203 00000 n +0000344704 00000 n +0000344892 00000 n +0000345974 00000 n +0000346163 00000 n +0000347496 00000 n +0000347702 00000 n +0000349352 00000 n +0000349606 00000 n +0000351387 00000 n +0000351556 00000 n +0000352952 00000 n +0000353121 00000 n +0000353889 00000 n +0000354092 00000 n +0000356047 00000 n +0000356244 00000 n +0000358444 00000 n +0000358664 00000 n +0000360640 00000 n +0000360828 00000 n +0000362565 00000 n +0000362744 00000 n +0000364069 00000 n +0000364309 00000 n +0000365825 00000 n +0000366022 00000 n +0000367847 00000 n +0000368035 00000 n +0000370034 00000 n +0000370277 00000 n +0000372102 00000 n +0000372291 00000 n +0000373924 00000 n +0000374145 00000 n +0000375844 00000 n +0000376066 00000 n +0000377722 00000 n +0000377901 00000 n +0000379790 00000 n +0000379968 00000 n +0000381309 00000 n +0000381541 00000 n +0000383367 00000 n +0000383545 00000 n +0000384954 00000 n +0000385114 00000 n +0000385404 00000 n +0000385583 00000 n +0000387362 00000 n +0000387560 00000 n +0000389288 00000 n +0000389508 00000 n +0000391116 00000 n +0000391345 00000 n +0000392904 00000 n +0000393114 00000 n +0000394806 00000 n +0000395009 00000 n +0000396130 00000 n +0000396327 00000 n +0000397604 00000 n +0000397807 00000 n +0000398920 00000 n +0000399105 00000 n +0000399957 00000 n +0000400170 00000 n +0000401657 00000 n +0000401837 00000 n +0000402601 00000 n +0000402842 00000 n +0000404449 00000 n +0000404647 00000 n +0000406497 00000 n +0000406694 00000 n +0000408317 00000 n +0000408496 00000 n +0000410549 00000 n +0000410728 00000 n +0000412566 00000 n +0000412745 00000 n +0000414455 00000 n +0000414634 00000 n +0000415065 00000 n +0000415285 00000 n +0000417022 00000 n 0000417219 00000 n -0000417397 00000 n -0000418806 00000 n -0000418966 00000 n -0000419255 00000 n -0000419434 00000 n -0000421151 00000 n -0000421330 00000 n -0000423110 00000 n -0000423321 00000 n -0000424805 00000 n -0000425034 00000 n -0000426593 00000 n -0000426803 00000 n -0000428495 00000 n -0000428699 00000 n -0000429820 00000 n -0000430017 00000 n -0000431295 00000 n -0000431499 00000 n -0000432612 00000 n -0000432798 00000 n -0000433651 00000 n -0000433865 00000 n -0000435352 00000 n -0000435532 00000 n -0000436296 00000 n -0000436537 00000 n -0000438143 00000 n -0000438341 00000 n -0000440190 00000 n -0000440387 00000 n -0000442010 00000 n -0000442189 00000 n -0000444243 00000 n -0000444422 00000 n -0000446260 00000 n -0000446439 00000 n -0000448150 00000 n -0000448329 00000 n -0000448760 00000 n -0000448980 00000 n -0000450717 00000 n -0000450914 00000 n -0000452768 00000 n -0000452937 00000 n -0000454635 00000 n -0000454804 00000 n -0000456013 00000 n -0000456201 00000 n -0000457899 00000 n -0000458087 00000 n -0000459541 00000 n -0000459755 00000 n -0000461358 00000 n -0000461546 00000 n -0000463206 00000 n -0000463394 00000 n -0000464223 00000 n -0000464411 00000 n -0000465983 00000 n -0000466178 00000 n -0000467443 00000 n -0000467647 00000 n -0000469058 00000 n -0000469253 00000 n -0000471911 00000 n -0000472087 00000 n -0000473391 00000 n -0000473561 00000 n -0000474090 00000 n -0000474260 00000 n -0000474772 00000 n -0000474942 00000 n -0000476450 00000 n -0000476620 00000 n -0000478019 00000 n -0000478189 00000 n -0000479739 00000 n -0000479908 00000 n -0000480871 00000 n -0000481050 00000 n -0000482578 00000 n -0000482766 00000 n -0000483735 00000 n -0000483914 00000 n -0000484251 00000 n -0000484447 00000 n -0000486178 00000 n -0000486392 00000 n -0000488075 00000 n -0000488270 00000 n -0000489977 00000 n -0000490213 00000 n -0000491898 00000 n -0000492093 00000 n -0000493675 00000 n -0000493889 00000 n -0000495259 00000 n -0000495447 00000 n -0000496614 00000 n -0000496865 00000 n +0000419073 00000 n +0000419242 00000 n +0000420939 00000 n +0000421108 00000 n +0000422317 00000 n +0000422505 00000 n +0000424203 00000 n +0000424391 00000 n +0000425847 00000 n +0000426060 00000 n +0000427662 00000 n +0000427850 00000 n +0000429511 00000 n +0000429699 00000 n +0000430528 00000 n +0000430716 00000 n +0000432287 00000 n +0000432481 00000 n +0000433747 00000 n +0000433959 00000 n +0000435553 00000 n +0000435732 00000 n +0000436103 00000 n +0000436264 00000 n +0000436464 00000 n +0000436658 00000 n +0000438241 00000 n +0000438454 00000 n +0000439982 00000 n +0000440170 00000 n +0000441432 00000 n +0000441620 00000 n +0000442889 00000 n +0000443142 00000 n +0000444479 00000 n +0000444677 00000 n +0000446207 00000 n +0000446386 00000 n +0000447319 00000 n +0000447498 00000 n +0000449026 00000 n +0000449214 00000 n +0000450183 00000 n +0000450362 00000 n +0000451195 00000 n +0000451390 00000 n +0000453121 00000 n +0000453334 00000 n +0000455017 00000 n +0000455211 00000 n +0000456918 00000 n +0000457153 00000 n +0000458838 00000 n +0000459008 00000 n +0000459535 00000 n +0000459705 00000 n +0000461212 00000 n +0000461382 00000 n +0000462781 00000 n +0000462951 00000 n +0000464501 00000 n +0000464670 00000 n +0000465634 00000 n +0000465884 00000 n +0000467353 00000 n +0000467540 00000 n +0000469484 00000 n +0000469713 00000 n +0000471573 00000 n +0000471780 00000 n +0000473912 00000 n +0000474115 00000 n +0000474870 00000 n +0000475074 00000 n +0000476876 00000 n +0000477098 00000 n +0000478962 00000 n +0000479184 00000 n +0000480738 00000 n +0000480951 00000 n +0000482697 00000 n +0000482914 00000 n +0000484698 00000 n +0000484757 00000 n +0000484860 00000 n +0000485025 00000 n +0000485121 00000 n +0000485239 00000 n +0000485355 00000 n +0000485464 00000 n +0000485587 00000 n +0000485699 00000 n +0000485869 00000 n +0000485970 00000 n +0000486086 00000 n +0000486207 00000 n +0000486327 00000 n +0000486452 00000 n +0000486565 00000 n +0000486669 00000 n +0000486847 00000 n +0000486968 00000 n +0000487128 00000 n +0000487246 00000 n +0000487343 00000 n +0000487495 00000 n +0000487635 00000 n +0000487813 00000 n +0000487968 00000 n +0000488070 00000 n +0000488170 00000 n +0000488379 00000 n +0000488480 00000 n +0000488668 00000 n +0000488809 00000 n +0000488953 00000 n +0000489107 00000 n +0000489216 00000 n +0000489328 00000 n +0000489495 00000 n +0000489607 00000 n +0000489781 00000 n +0000489884 00000 n +0000490057 00000 n +0000490178 00000 n +0000490308 00000 n +0000490434 00000 n +0000490549 00000 n +0000490657 00000 n +0000490804 00000 n +0000490909 00000 n +0000491028 00000 n +0000491157 00000 n +0000491316 00000 n +0000491450 00000 n +0000491587 00000 n +0000491719 00000 n +0000491868 00000 n +0000492000 00000 n +0000492148 00000 n +0000492262 00000 n +0000492380 00000 n +0000492534 00000 n +0000492665 00000 n +0000492759 00000 n +0000492883 00000 n +0000492995 00000 n +0000493172 00000 n +0000493281 00000 n +0000493406 00000 n +0000493552 00000 n +0000493654 00000 n +0000493830 00000 n +0000493974 00000 n +0000494086 00000 n +0000494213 00000 n +0000494341 00000 n +0000494469 00000 n +0000494580 00000 n +0000494779 00000 n +0000494890 00000 n +0000495005 00000 n +0000495149 00000 n +0000495357 00000 n +0000495491 00000 n +0000495645 00000 n +0000495770 00000 n +0000495939 00000 n +0000496072 00000 n +0000496360 00000 n +0000496513 00000 n +0000496707 00000 n +0000496918 00000 n +0000497079 00000 n +0000497200 00000 n +0000497403 00000 n +0000497514 00000 n +0000497629 00000 n +0000497822 00000 n +0000497965 00000 n +0000498081 00000 n +0000498239 00000 n 0000498396 00000 n -0000498616 00000 n -0000499294 00000 n -0000499508 00000 n -0000501253 00000 n -0000501470 00000 n -0000503257 00000 n -0000503507 00000 n -0000504975 00000 n -0000505162 00000 n -0000507106 00000 n -0000507335 00000 n -0000509196 00000 n -0000509403 00000 n -0000511535 00000 n -0000511739 00000 n -0000512599 00000 n -0000512658 00000 n -0000512761 00000 n -0000512926 00000 n -0000513022 00000 n -0000513137 00000 n -0000513252 00000 n -0000513361 00000 n -0000513484 00000 n -0000513596 00000 n -0000513774 00000 n -0000513895 00000 n +0000498527 00000 n +0000498648 00000 n +0000498825 00000 n +0000498935 00000 n +0000499065 00000 n +0000499235 00000 n +0000499329 00000 n +0000499456 00000 n +0000499583 00000 n +0000499679 00000 n +0000499866 00000 n +0000499993 00000 n +0000500127 00000 n +0000500254 00000 n +0000500366 00000 n +0000500572 00000 n +0000500731 00000 n +0000500879 00000 n +0000501007 00000 n +0000501188 00000 n +0000501298 00000 n +0000501413 00000 n +0000501558 00000 n +0000501722 00000 n +0000501872 00000 n +0000502009 00000 n +0000502175 00000 n +0000502279 00000 n +0000502436 00000 n +0000502547 00000 n +0000502692 00000 n +0000502834 00000 n +0000502984 00000 n +0000503101 00000 n +0000503265 00000 n +0000503376 00000 n +0000503516 00000 n +0000503643 00000 n +0000503760 00000 n +0000503899 00000 n +0000504005 00000 n +0000504139 00000 n +0000504271 00000 n +0000504416 00000 n +0000504543 00000 n +0000504675 00000 n +0000504805 00000 n +0000504930 00000 n +0000505038 00000 n +0000505210 00000 n +0000505314 00000 n +0000505449 00000 n +0000505584 00000 n +0000505818 00000 n +0000505972 00000 n +0000506113 00000 n +0000506287 00000 n +0000506377 00000 n +0000506505 00000 n +0000506679 00000 n +0000506781 00000 n +0000506932 00000 n +0000507083 00000 n +0000507209 00000 n +0000507415 00000 n +0000507515 00000 n +0000507633 00000 n +0000507798 00000 n +0000507889 00000 n +0000508050 00000 n +0000508176 00000 n +0000508319 00000 n +0000508446 00000 n +0000508586 00000 n +0000508722 00000 n +0000508830 00000 n +0000509004 00000 n +0000509110 00000 n +0000509230 00000 n +0000509342 00000 n +0000509459 00000 n +0000509561 00000 n +0000509739 00000 n +0000509908 00000 n +0000510016 00000 n +0000510150 00000 n +0000510268 00000 n +0000510445 00000 n +0000510612 00000 n +0000510728 00000 n +0000510866 00000 n +0000511002 00000 n +0000511176 00000 n +0000511291 00000 n +0000511401 00000 n +0000511537 00000 n +0000511713 00000 n +0000511859 00000 n +0000511993 00000 n +0000512149 00000 n +0000512317 00000 n +0000512466 00000 n +0000512590 00000 n +0000512728 00000 n +0000512891 00000 n +0000513001 00000 n +0000513135 00000 n +0000513247 00000 n +0000513428 00000 n +0000513549 00000 n +0000513735 00000 n +0000513892 00000 n 0000514055 00000 n -0000514173 00000 n -0000514270 00000 n -0000514422 00000 n -0000514562 00000 n -0000514740 00000 n -0000514895 00000 n -0000514997 00000 n -0000515097 00000 n -0000515306 00000 n -0000515407 00000 n -0000515595 00000 n -0000515736 00000 n -0000515880 00000 n -0000515996 00000 n -0000516163 00000 n -0000516275 00000 n -0000516449 00000 n -0000516552 00000 n -0000516725 00000 n -0000516846 00000 n -0000516976 00000 n -0000517102 00000 n -0000517217 00000 n -0000517325 00000 n -0000517472 00000 n -0000517577 00000 n -0000517696 00000 n -0000517825 00000 n -0000517984 00000 n -0000518118 00000 n -0000518255 00000 n -0000518387 00000 n -0000518536 00000 n -0000518668 00000 n -0000518816 00000 n -0000518930 00000 n -0000519048 00000 n -0000519202 00000 n -0000519333 00000 n -0000519427 00000 n -0000519551 00000 n -0000519663 00000 n -0000519840 00000 n -0000519949 00000 n -0000520074 00000 n -0000520220 00000 n -0000520322 00000 n -0000520498 00000 n -0000520642 00000 n -0000520754 00000 n -0000520881 00000 n -0000521009 00000 n -0000521137 00000 n -0000521248 00000 n -0000521447 00000 n -0000521558 00000 n -0000521673 00000 n -0000521817 00000 n -0000522025 00000 n -0000522159 00000 n -0000522313 00000 n -0000522438 00000 n -0000522569 00000 n -0000522700 00000 n -0000522861 00000 n -0000522982 00000 n -0000523185 00000 n -0000523296 00000 n -0000523411 00000 n -0000523604 00000 n -0000523747 00000 n -0000523863 00000 n -0000524021 00000 n -0000524178 00000 n -0000524309 00000 n -0000524430 00000 n -0000524607 00000 n -0000524717 00000 n -0000524847 00000 n -0000525017 00000 n -0000525111 00000 n -0000525238 00000 n -0000525365 00000 n -0000525461 00000 n -0000525647 00000 n -0000525773 00000 n -0000525906 00000 n -0000526033 00000 n -0000526145 00000 n -0000526351 00000 n -0000526510 00000 n -0000526658 00000 n -0000526786 00000 n -0000526967 00000 n -0000527077 00000 n -0000527192 00000 n -0000527337 00000 n -0000527501 00000 n -0000527651 00000 n -0000527788 00000 n -0000527954 00000 n -0000528058 00000 n -0000528215 00000 n -0000528326 00000 n -0000528471 00000 n -0000528613 00000 n -0000528763 00000 n -0000528880 00000 n -0000529044 00000 n -0000529155 00000 n -0000529295 00000 n -0000529422 00000 n -0000529539 00000 n -0000529678 00000 n -0000529784 00000 n -0000529918 00000 n -0000530050 00000 n -0000530195 00000 n -0000530322 00000 n -0000530454 00000 n -0000530584 00000 n -0000530709 00000 n -0000530817 00000 n -0000530989 00000 n -0000531093 00000 n -0000531228 00000 n -0000531363 00000 n -0000531597 00000 n -0000531751 00000 n -0000531892 00000 n -0000532066 00000 n -0000532156 00000 n -0000532284 00000 n -0000532458 00000 n -0000532560 00000 n -0000532711 00000 n -0000532862 00000 n -0000532988 00000 n -0000533194 00000 n -0000533294 00000 n -0000533412 00000 n -0000533577 00000 n -0000533668 00000 n -0000533829 00000 n -0000533955 00000 n -0000534098 00000 n -0000534225 00000 n -0000534365 00000 n -0000534501 00000 n -0000534609 00000 n -0000534783 00000 n -0000534889 00000 n -0000535009 00000 n -0000535121 00000 n -0000535238 00000 n -0000535340 00000 n -0000535518 00000 n -0000535687 00000 n -0000535795 00000 n -0000535929 00000 n -0000536047 00000 n -0000536224 00000 n -0000536391 00000 n -0000536507 00000 n -0000536645 00000 n -0000536781 00000 n -0000536941 00000 n -0000537056 00000 n -0000537166 00000 n -0000537342 00000 n -0000537488 00000 n -0000537622 00000 n -0000537778 00000 n -0000537946 00000 n -0000538095 00000 n -0000538219 00000 n -0000538357 00000 n -0000538520 00000 n -0000538630 00000 n -0000538764 00000 n -0000538876 00000 n -0000539057 00000 n -0000539178 00000 n -0000539356 00000 n -0000539476 00000 n -0000539595 00000 n -0000539756 00000 n -0000539879 00000 n -0000540001 00000 n -0000540205 00000 n -0000540310 00000 n -0000540442 00000 n -0000540563 00000 n -0000540734 00000 n -0000540856 00000 n -0000541016 00000 n -0000541115 00000 n -0000541233 00000 n -0000541348 00000 n -0000541450 00000 n -0000541611 00000 n -0000541715 00000 n -0000541814 00000 n -0000542021 00000 n -0000542149 00000 n -0000542234 00000 n -0000542426 00000 n -0000542598 00000 n -0000542702 00000 n -0000542826 00000 n -0000542948 00000 n -0000543060 00000 n -0000543242 00000 n -0000543358 00000 n -0000543482 00000 n -0000543600 00000 n -0000543718 00000 n -0000543823 00000 n -0000544000 00000 n -0000544112 00000 n -0000544243 00000 n -0000544367 00000 n -0000544534 00000 n -0000544651 00000 n -0000544781 00000 n -0000544921 00000 n -0000545058 00000 n -0000545194 00000 n -0000545330 00000 n -0000545467 00000 n -0000545579 00000 n -0000545743 00000 n -0000545847 00000 n -0000545980 00000 n -0000546112 00000 n -0000546234 00000 n -0000546363 00000 n -0000546470 00000 n -0000546636 00000 n -0000546758 00000 n -0000546868 00000 n -0000546982 00000 n -0000547174 00000 n -0000547316 00000 n -0000547428 00000 n -0000547551 00000 n -0000547674 00000 n -0000547796 00000 n -0000547921 00000 n -0000548044 00000 n -0000548162 00000 n -0000548349 00000 n -0000548507 00000 n -0000548611 00000 n -0000548731 00000 n -0000548854 00000 n -0000549029 00000 n -0000549132 00000 n -0000549252 00000 n -0000549367 00000 n -0000549481 00000 n -0000549596 00000 n -0000549710 00000 n -0000549825 00000 n -0000549943 00000 n -0000550060 00000 n -0000550166 00000 n -0000550327 00000 n -0000550423 00000 n -0000550537 00000 n -0000550647 00000 n -0000550778 00000 n -0000550911 00000 n -0000551012 00000 n -0000551190 00000 n -0000551300 00000 n -0000551454 00000 n -0000551623 00000 n -0000551811 00000 n -0000551992 00000 n -0000552148 00000 n -0000552314 00000 n -0000552446 00000 n -0000552593 00000 n -0000552732 00000 n -0000552866 00000 n -0000552990 00000 n -0000553111 00000 n -0000553244 00000 n -0000553350 00000 n -0000553520 00000 n -0000553682 00000 n -0000553788 00000 n -0000553905 00000 n -0000554056 00000 n -0000554221 00000 n -0000554346 00000 n -0000554502 00000 n -0000554620 00000 n -0000554750 00000 n -0000554914 00000 n -0000555018 00000 n -0000555136 00000 n -0000555254 00000 n -0000555375 00000 n -0000555511 00000 n -0000555610 00000 n -0000555765 00000 n -0000555869 00000 n -0000555986 00000 n -0000556101 00000 n -0000556215 00000 n +0000514225 00000 n +0000514349 00000 n +0000514472 00000 n +0000514676 00000 n +0000514781 00000 n +0000514913 00000 n +0000515034 00000 n +0000515205 00000 n +0000515327 00000 n +0000515487 00000 n +0000515586 00000 n +0000515704 00000 n +0000515819 00000 n +0000515921 00000 n +0000516082 00000 n +0000516186 00000 n +0000516285 00000 n +0000516492 00000 n +0000516620 00000 n +0000516705 00000 n +0000516897 00000 n +0000517069 00000 n +0000517173 00000 n +0000517297 00000 n +0000517419 00000 n +0000517531 00000 n +0000517713 00000 n +0000517829 00000 n +0000517953 00000 n +0000518071 00000 n +0000518189 00000 n +0000518294 00000 n +0000518471 00000 n +0000518583 00000 n +0000518714 00000 n +0000518838 00000 n +0000519005 00000 n +0000519122 00000 n +0000519252 00000 n +0000519392 00000 n +0000519529 00000 n +0000519665 00000 n +0000519801 00000 n +0000519938 00000 n +0000520050 00000 n +0000520214 00000 n +0000520318 00000 n +0000520451 00000 n +0000520583 00000 n +0000520705 00000 n +0000520834 00000 n +0000520941 00000 n +0000521107 00000 n +0000521229 00000 n +0000521353 00000 n +0000521470 00000 n +0000521584 00000 n +0000521754 00000 n +0000521916 00000 n +0000522022 00000 n +0000522139 00000 n +0000522290 00000 n +0000522427 00000 n +0000522592 00000 n +0000522717 00000 n +0000522873 00000 n +0000522991 00000 n +0000523121 00000 n +0000523308 00000 n +0000523466 00000 n +0000523570 00000 n +0000523690 00000 n +0000523813 00000 n +0000523974 00000 n +0000524070 00000 n +0000524184 00000 n +0000524294 00000 n +0000524425 00000 n +0000524572 00000 n +0000524673 00000 n +0000524772 00000 n +0000524950 00000 n +0000525060 00000 n +0000525214 00000 n +0000525383 00000 n +0000525571 00000 n +0000525752 00000 n +0000525908 00000 n +0000526074 00000 n +0000526206 00000 n +0000526353 00000 n +0000526492 00000 n +0000526626 00000 n +0000526750 00000 n +0000526871 00000 n +0000527004 00000 n +0000527110 00000 n +0000527302 00000 n +0000527444 00000 n +0000527556 00000 n +0000527679 00000 n +0000527802 00000 n +0000527924 00000 n +0000528049 00000 n +0000528172 00000 n +0000528290 00000 n +0000528465 00000 n +0000528568 00000 n +0000528688 00000 n +0000528803 00000 n +0000528917 00000 n +0000529032 00000 n +0000529146 00000 n +0000529261 00000 n +0000529379 00000 n +0000529496 00000 n +0000529602 00000 n +0000529771 00000 n +0000529875 00000 n +0000529992 00000 n +0000530107 00000 n +0000530221 00000 n +0000530407 00000 n +0000530516 00000 n +0000530691 00000 n +0000530809 00000 n +0000530950 00000 n +0000531073 00000 n +0000531223 00000 n +0000531327 00000 n +0000531445 00000 n +0000531563 00000 n +0000531684 00000 n +0000531820 00000 n +0000531919 00000 n trailer -<<0cac33df34592dc0adc9962ab28d84f6>]>> +<<715f41d6c6f228bafa2b807ede00788a>]>> startxref -557263 +533010 %%EOF diff --git a/docs/faq/faq-clientapp.html b/docs/faq/faq-clientapp.html index 3a85fb4f5a..4aa8a50c4b 100644 --- a/docs/faq/faq-clientapp.html +++ b/docs/faq/faq-clientapp.html @@ -73,6 +73,30 @@ NAME="FAQ-CLIENTAPP" >Chapter 4. Specific client application problems

Chapter 3. Configuration problems

Chapter 5. Common errors

Chapter 6. Features

Chapter 1. General Information

Chapter 2. Compiling and installing Samba on a Unix host

Edited by

John H Terpstra

Jelmer R. Vernooij

Jelmer Vernooij

John H. Terpstra

Gerald (Jerry) Carter

This book is a collection of HOWTOs added to Samba documentation over the years. @@ -95,7 +95,7 @@ CLASS="LEGALNOTICE" >

This documentation is distributed under the GNU General Public License (GPL) @@ -125,141 +125,185 @@ HREF="#INTRODUCTION" >

1. Introduction to Samba
1.1. Background
1.2. Terminology
1.3. Related Projects
1.4. SMB Methodology
1.5. Additional Resources
1.6. Epilogue
1.7. Miscellaneous
2. How to Install and Test SAMBA
1.1. 2.1. Obtaining and installing samba
1.2. 2.2. Configuring samba
1.3. 2.3. Try listing the shares available on your server
1.4. 2.4. Try connecting with the unix client
1.5. 2.5. Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client
1.6. 2.6. What If Things Don't Work?
2. 3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide
2.1. 3.1. Discussion
2.2. 3.2. How browsing functions and how to deploy stable and dependable browsing using Samba
2.3. 3.3. Use of the Remote Announce parameter
2.4. 3.4. Use of the Remote Browse Sync parameter
2.5. 3.5. Use of WINS
2.6. 3.6. Do NOT use more than one (1) protocol on MS Windows machines
2.7. 3.7. Name Resolution Order
3. 4. User information database
3.1. 4.1. Introduction
3.2. 4.2. Important Notes About Security
3.3. 4.3. The smbpasswd Command
3.4. 4.4. Plain text
3.5. 4.5. TDB
3.6. 4.6. LDAP
3.7. 4.7. MySQL
3.8. 4.8. XML
4. 5. Nomenclature of Server Types
4.1. 5.1. Stand Alone Server
4.2. 5.2. Domain Member Server
4.3. 5.3. Domain Controller
5. 6. Samba as Stand-Alone Server
5.1. 6.1. User and Share security level
6. 7. Samba as an NT4 or Win2k Primary Domain Controller
6.1. 7.1. Prerequisite Reading
6.2. 7.2. Background
6.3. 7.3. Configuring the Samba Domain Controller
6.4. 7.4. Creating Machine Trust Accounts and Joining Clients to the Domain
6.5. 7.5. Common Problems and Errors
6.6. What other help can I get?
6.7. 7.6. Domain Control for Windows 9x/ME
7. 8. Samba Backup Domain Controller to Samba Domain Control
7.1. 8.1. Prerequisite Reading
7.2. 8.2. Background
7.3. 8.3. What qualifies a Domain Controller on the network?
7.4. 8.4. Can Samba be a Backup Domain Controller to an NT PDC?
7.5. 8.5. How do I set up a Samba BDC?
8. 9. Samba as a ADS domain member
8.1. 9.1. Setup your smb.conf
8.2. 9.2. Setup your /etc/krb5.conf
8.3. 9.3. Create the computer account
8.4. 9.4. Test your server setup
8.5. 9.5. Testing with
8.6. 9.6. Notes
9. 10. Samba as a NT4 or Win2k domain member
9.1. 10.1. Joining an NT Domain with Samba 3.0
9.2. 10.2. Why is this better than security = server?
10. 11. UNIX Permission Bits and Windows NT Access Control Lists
10.1. 11.1. Viewing and changing UNIX permissions using the NT security dialogs
10.2. 11.2. How to view file security on a Samba share
10.3. 11.3. Viewing file ownership
10.4. 11.4. Viewing file or directory permissions
10.5. 11.5. Modifying file or directory permissions
10.6. 11.6. Interaction with the standard Samba create mask parameters
10.7. 11.7. Interaction with the standard Samba file attribute mapping
11. 12. Configuring Group Mapping
12. 13. Printing Support
12.1. 13.1. Introduction
12.2. 13.2. Configuration
12.3. 13.3. The Imprints Toolset
12.4. 13.4. Diagnosis
13. 14. CUPS Printing Support
13.1. 14.1. Introduction
13.2. 14.2. Configuring smb.conf for CUPS
13.3. 14.3. CUPS - RAW Print Through Mode
13.4. 14.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe PostScript driver with CUPS-PPDs downloaded to clients
13.5. 14.5. Windows Terminal Servers (WTS) as CUPS clients
13.6. 14.6. Setting up CUPS for driver download
13.7. 14.7. Sources of CUPS drivers / PPDs
13.8. 14.8. The CUPS Filter Chains
13.9. 14.9. CUPS Print Drivers and Devices
13.10. 14.10. Limiting the number of pages users can print
13.11. 14.11. Advanced Postscript Printing from MS Windows
13.12. 14.12. Auto-Deletion of CUPS spool files
14. 15. Unified Logons between Windows NT and UNIX using Winbind
14.1. 15.1. Abstract
14.2. 15.2. Introduction
14.3. 15.3. What Winbind Provides
14.4. 15.4. How Winbind Works
14.5. 15.5. Installation and Configuration
14.6. 15.6. Limitations
14.7. 15.7. Conclusion
15. 16. Advanced Network Manangement
15.1. 16.1. Configuring Samba Share Access Controls
15.2. 16.2. Remote Server Administration
15.3. 16.3. Network Logon Script Magic
16. 17. System and Account Policies
16.1. 17.1. Creating and Managing System Policies
16.2. 17.2. Managing Account/User Policies
17.3. System Startup and Logon Processing Overview
17. 18. Desktop Profile Management
17.1. 18.1. Roaming Profiles
17.2. 18.2. Mandatory profiles
17.3. 18.3. Creating/Managing Group Profiles
17.4. 18.4. Default Profile for Windows Users
18. 19. Interdomain Trust Relationships
18.1. 19.1. Trust Relationship Background
18.2. MS Windows NT4 Trust Configuration19.2. Native MS Windows NT4 Trusts Configuration
18.3. Configuring Samba Domain Trusts19.3. Configuring Samba NT-style Domain Trusts
19. 20. PAM Configuration for Centrally Managed Authentication
19.1. 20.1. Samba and PAM
19.2. 20.2. Distributed Authentication
19.3. 20.3. PAM Configuration in smb.conf
20. 21. Stackable VFS modules
20.1. 21.1. Introduction and configuration
20.2. 21.2. Included modules
20.3. 21.3. VFS modules available elsewhere
21. 22. Hosting a Microsoft Distributed File System tree on Samba
21.1. 22.1. Instructions
22. 23. Integrating MS Windows networks with Samba
22.1. 23.1. Name Resolution in a pure Unix/Linux world
22.2. 23.2. Name resolution as used within MS Windows networking
23. 24. Improved browsing in samba
23.1. 24.1. Overview of browsing
23.2. 24.2. Browsing support in samba
23.3. 24.3. Problem resolution
23.4. 24.4. Browsing across subnets
23.5. 24.5. Setting up a WINS server
23.6. 24.6. Setting up Browsing in a WORKGROUP
23.7. 24.7. Setting up Browsing in a DOMAIN
23.8. 24.8. Forcing samba to be the master
23.9. 24.9. Making samba the domain master
23.10. 24.10. Note about broadcast addresses
23.11. 24.11. Multiple interfaces
24. 25. Securing Samba
24.1. 25.1. Introduction
24.2. 25.2. Using host based protection
24.3. 25.3. Using interface protection
24.4. 25.4. Using a firewall
24.5. 25.5. Using a IPC$ share deny
24.6. 25.6. Upgrading Samba
25. 26. Unicode/Charsets
25.1. 26.1. What are charsets and unicode?
25.2. 26.2. Samba and charsets
26.3. Conversion from old names
26. SWAT - The Samba Web Admininistration Tool27. How to compile SAMBA
26.1. SWAT Features and Benefits27.1. Access Samba source code via CVS
27. Migration from NT4 PDC to Samba-3 PDC
27.2. Accessing the samba sources via rsync and ftp
27.1. Planning and Getting Started27.3. Verifying Samba's PGP signature
27.2. Managing Samba-3 Domain Control27.4. Building the Binaries
27.5. Starting the smbd and nmbd
28. Samba performance issuesMigration from NT4 PDC to Samba-3 PDC
28.1. ComparisonsPlanning and Getting Started
28.2. Socket options
28.3. Read size
28.4. Max xmit
28.5. Log level
28.6. Read raw
28.7. Write raw
28.8. Slow Clients
28.9. Slow Logins
28.10. Client tuningManaging Samba-3 Domain Control
29.1. HPUX
29.2. SCO Unix
29.3. DNIX
29.4. RedHat Linux Rembrandt-II
29.5. AIX
29.6. Solaris
30.1. Macintosh clients?
30.2. OS2 Client
30.3. Windows for Workgroups
30.4. Windows '95/'98
30.5. Windows 2000 Service Pack 2
30.6. Windows NT 3.1
31. How to compile SAMBASWAT - The Samba Web Admininistration Tool
31.1. Access Samba source code via CVS
31.2. Accessing the samba sources via rsync and ftp
31.3. Building the Binaries
31.4. Starting the smbd and nmbdSWAT Features and Benefits
32. Reporting BugsSamba performance issues
32.1. IntroductionComparisons
32.2. General infoSocket options
32.3. Debug levelsRead size
32.4. Internal errorsMax xmit
32.5. Attaching to a running processLog level
32.6. PatchesRead raw
32.7. Write raw
32.8. Slow Clients
32.9. Slow Logins
32.10. Client tuning
33.1. Introduction
33.2. Assumptions
33.3. The tests
33.4. Still having troubles?

I. General installation

Introduction

This part contains general info on how to install samba -and how to configure the parts of samba you will most likely need. -PLEASE read this.

Table of Contents
1. How to Install and Test SAMBA
1.1. Obtaining and installing samba
1.2. Configuring samba34. Analysing and solving samba problems
1.2.1. Editing the smb.conf file
1.2.2. SWAT
1.3. Try listing the shares available on your - server
1.4. Try connecting with the unix client34.1. Diagnostics tools
1.5. Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client34.2. Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
1.6. What If Things Don't Work?34.3. Useful URL's
1.6.1. Scope IDs34.4. Getting help from the mailing lists
1.6.2. Locking34.5. How to get off the mailinglists
2. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide35. Reporting Bugs
2.1. Discussion
2.2. How browsing functions and how to deploy stable and -dependable browsing using Samba35.1. Introduction
2.3. Use of the Remote Announce parameter35.2. General info
2.4. Use of the Remote Browse Sync parameter35.3. Debug levels
2.5. Use of WINS35.4. Internal errors
2.6. Do NOT use more than one (1) protocol on MS Windows machines35.5. Attaching to a running process
2.7. Name Resolution Order35.6. Patches
3. User information database
3.1. Introduction
3.2. Important Notes About Security
3.2.1. Advantages of SMB Encryption
3.2.2. Advantages of non-encrypted passwords
3.3. The smbpasswd Command
3.4. Plain text
3.5. TDB
3.6. LDAP
3.6.1. Introduction
3.6.2. Introduction
3.6.3. Supported LDAP Servers
3.6.4. Schema and Relationship to the RFC 2307 posixAccount
3.6.5. Configuring Samba with LDAP
3.6.6. Accounts and Groups management
3.6.7. Security and sambaAccount
3.6.8. LDAP specials attributes for sambaAccounts
3.6.9. Example LDIF Entries for a sambaAccount
3.7. MySQL
3.7.1. Creating the database
3.7.2. Configuring
3.7.3. Using plaintext passwords or encrypted password
3.7.4. Getting non-column data from the table
3.8. XML

I. General installation

Introduction

This part contains general info on how to install samba +and how to configure the parts of samba you will most likely need. +PLEASE read this.

Chapter 1. How to Install and Test SAMBA

Chapter 1. Introduction to Samba

"If you understand what you're doing, you're not learning anything." +-- Anonymous

Samba is a file and print server for Windows-based clients using TCP/IP as the underlying +transport protocol. In fact, it can support any SMB/CIFS-enabled client. One of Samba's big +strengths is that you can use it to blend your mix of Windows and Linux machines together +without requiring a separate Windows NT/2000/2003 Server. Samba is actively being developed +by a global team of about 30 active programmers and was originally developed by Andrew Tridgell.

1.1. Obtaining and installing samba1.1. Background

Binary packages of samba are included in almost any Linux or - Unix distribution. There are also some packages available at - the samba homepage. -

Once long ago, there was a buzzword referred to as DCE/RPC. This stood for Distributed +Computing Environment/Remote Procedure Calls and conceptually was a good idea. It was +originally developed by Apollo/HP as NCA 1.0 (Network Computing Architecture) and only +ran over UDP. When there was a need to run it over TCP so that it would be compatible +with DECnet 3.0, it was redesigned, submitted to The Open Group, and officially became +known as DCE/RPC. Microsoft came along and decided, rather than pay $20 per seat to +license this technology, to reimplement DCE/RPC themselves as MSRPC. From this, the +concept continued in the form of SMB (Server Message Block, or the "what") using the +NetBIOS (Network Basic Input/Output System, or the "how") compatibility layer. You can +run SMB (i.e., transport) over several different protocols; many different implementations +arose as a result, including NBIPX (NetBIOS over IPX, NwLnkNb, or NWNBLink) and NBT +(NetBIOS over TCP/IP, or NetBT). As the years passed, NBT became the most common form +of implementation until the advance of "Direct-Hosted TCP" -- the Microsoft marketing +term for eliminating NetBIOS entirely and running SMB by itself across TCP port 445 +only. As of yet, direct-hosted TCP has yet to catch on.

Perhaps the best summary of the origins of SMB are voiced in the 1997 article titled, CIFS: +Common Insecurities Fail Scrutiny:

If you need to compile samba from source, check the - appropriate appendix chapter.

Several megabytes of NT-security archives, random whitepapers, RFCs, the CIFS spec, the Samba +stuff, a few MS knowledge-base articles, strings extracted from binaries, and packet dumps have +been dutifully waded through during the information-gathering stages of this project, and there +are *still* many missing pieces... While often tedious, at least the way has been generously +littered with occurrences of clapping hand to forehead and muttering 'crikey, what are they +thinking?

1.2. Configuring samba1.2. Terminology

Samba's configuration is stored in the smb.conf file, - that usually resides in /etc/samba/smb.conf - or /usr/local/samba/lib/smb.conf. You can either - edit this file yourself or do it using one of the many graphical - tools that are available, such as the web-based interface swat, that - is included with samba.

1.2.1. Editing the smb.conf file

There are sample configuration files in the examples - subdirectory in the distribution. I suggest you read them - carefully so you can see how the options go together in - practice. See the man page for all the options.

  • The simplest useful configuration file would be - something like this:

    SMB: Acronym for "Server Message Block". This is Microsoft's file and printer sharing protocol. + 

  • [global]
-	workgroup = MYGROUP
-
-[homes]
-	guest ok = no
-	read only = no
-

    CIFS: Acronym for "Common Internet File System". Around 1996, Microsoft apparently + decided that SMB needed the word "Internet" in it, so they changed it to CIFS. +

  • which would allow connections by anyone with an - account on the server, using either their login name or - "homes" as the service name. (Note that I also set the - workgroup that Samba is part of. See BROWSING.txt for details)

    Direct-Hosted: A method of providing file/printer sharing services over port 445/tcp + only using DNS for name resolution instead of WINS. +

  • Make sure you put the smb.conf file in the same place - you specified in theMakefile (the default is to - look for it in /usr/local/samba/lib/).

    IPC: Acronym for "Inter-Process Communication". A method to communicate specific + information between programs. +

  • For more information about security settings for the - [homes] share please refer to the chapter - Securing Samba.

    1.2.1.1. Test your config file with - testparm

    Marshalling: - A method of serializing (i.e., sequential ordering of) variable data + suitable for transmission via a network connection or storing in a file. The source + data can be re-created using a similar process called unmarshalling. +

  • It's important that you test the validity of your - smb.conf file using the testparm program. - If testparm runs OK then it will list the loaded services. If - not it will give an error message.

    NetBIOS: Acronym for "Network Basic Input/Output System". This is not a protocol; + it is a method of communication across an existing protocol. This is a standard which + was originally developed for IBM by Sytek in 1983. To exaggerate the analogy a bit, + it can help to think of this in comparison your computer's BIOS -- it controls the + essential functions of your input/output hardware -- whereas NetBIOS controls the + essential functions of your input/output traffic via the network. Again, this is a bit + of an exaggeration but it should help that paradigm shift. What is important to realize + is that NetBIOS is a transport standard, not a protocol. Unfortunately, even technically + brilliant people tend to interchange NetBIOS with terms like NetBEUI without a second + thought; this will cause no end (and no doubt) of confusion. +

  • Make sure it runs OK and that the services look - reasonable before proceeding.

    NetBEUI: Acronym for the "NetBIOS Extended User Interface". Unlike NetBIOS, NetBEUI + is a protocol, not a standard. It is also not routable, so traffic on one side of a + router will be unable to communicate with the other side. Understanding NetBEUI is + not essential to deciphering SMB; however it helps to point out that it is not the + same as NetBIOS and to improve your score in trivia at parties. NetBEUI was originally + referred to by Microsoft as "NBF", or "The Windows NT NetBEUI Frame protocol driver". + It is not often heard from these days. +

  • Always run testparm again when you change - smb.conf!

1.2.2. SWAT

NBT: Acronym for "NetBIOS over TCP"; also known as "NetBT". Allows the continued use + of NetBIOS traffic proxied over TCP/IP. As a result, NetBIOS names are made + to IP addresses and NetBIOS name types are conceptually equivalent to TCP/IP ports. + This is how file and printer sharing are accomplished in Windows 95/98/ME. They + traditionally rely on three ports: NetBIOS Name Service (nbname) via UDP port 137, + NetBIOS Datagram Service (nbdatagram) via UDP port 138, and NetBIOS Session Service + (nbsession) via TCP port 139. All name resolution is done via WINS, NetBIOS broadcasts, + and DNS. NetBIOS over TCP is documented in RFC 1001 (Concepts and methods) and RFC 1002 + (Detailed specifications). +

  • SWAT is a web-based interface that helps you configure samba. - SWAT might not be available in the samba package on your platform, - but in a seperate package. Please read the swat manpage - on compiling, installing and configuring swat from source. +> W2K: Acronym for Windows 2000 Professional or Server

  • To launch SWAT just run your favorite web browser and - point it at "http://localhost:901/". Replace localhost with the name of the computer you are running samba on if you - are running samba on a different computer then your browser.

    W3K: Acronym for Windows 2003 Server +

    • Note that you can attach to SWAT from any IP connected - machine but connecting from a remote machine leaves your - connection open to password sniffing as passwords will be sent - in the clear over the wire.

    If you plan on getting help, make sure to subscribe to the Samba Mailing List (available at +http://www.samba.org). Optionally, you could just search mailing.unix.samba at http://groups.google.com

    1.3. Try listing the shares available on your - server1.3. Related Projects

    $ smbclient -L - yourhostnameCurrently, there are two projects that are directly related to Samba: SMBFS and CIFS network +client file systems for Linux, both available in the Linux kernel itself.

    • You should get back a list of shares available on - your server. If you don't then something is incorrectly setup. - Note that this method can also be used to see what shares - are available on other LanManager clients (such as WfWg).

      SMBFS (Server Message Block File System) allows you to mount SMB shares (the protocol + that Microsoft Windows and OS/2 Lan Manager use to share files and printers + over local networks) and access them just like any other Unix directory. This is useful + if you just want to mount such filesystems without being a SMBFS server. +

    • If you choose user level security then you may find - that Samba requests a password before it will list the shares. - See the smbclient man page for details. (you - can force it to list the shares without a password by - adding the option -U% to the command line. This will not work - with non-Samba servers)

      CIFS (Common Internet File System) is the successor to SMB, and is actively being worked + on in the upcoming version of the Linux kernel. The intent of this module is to + provide advanced network file system functionality including support for dfs (heirarchical + name space), secure per-user session establishment, safe distributed caching (oplock), + optional packet signing, Unicode and other internationalization improvements, and optional + Winbind (nsswitch) integration. +

    Again, it's important to note that these are implementations for client filesystems, and have +nothing to do with acting as a file and print server for SMB/CIFS clients.

    1.4. Try connecting with the unix client1.4. SMB Methodology

    $ smbclient //yourhostname/aserviceTraditionally, SMB uses UDP port 137 (NetBIOS name service, or netbios-ns), +UDP port 138 (NetBIOS datagram service, or netbios-dgm), and TCP port 139 (NetBIOS +session service, or netbios-ssn). Anyone looking at their network with a good +packet sniffer will be amazed at the amount of traffic generated by just opening +up a single file. In general, SMB sessions are established in the following order:

    • Typically the yourhostname - would be the name of the host where you installed smbd. - The aservice is - any service you have defined in the smb.conf - file. Try your user name if you just have a [homes] - section - in smb.conf.

      "TCP Connection" - establish 3-way handshake (connection) to port 139/tcp + or 445/tcp. +

    • For example if your unix host is bambi - and your login name is fred you would type:

      "NetBIOS Session Request" - using the following "Calling Names": The local + machine's NetBIOS name plus the 16th character 0x00; The server's NetBIOS + name plus the 16th character 0x20 +

    • $ smbclient //bambi/fred -

      "SMB Negotiate Protocol" - determine the protocol dialect to use, which will + be one of the following: PC Network Program 1.0 (Core) - share level security + mode only; Microsoft Networks 1.03 (Core Plus) - share level security + mode only; Lanman1.0 (LAN Manager 1.0) - uses Challenge/Response + Authentication; Lanman2.1 (LAN Manager 2.1) - uses Challenge/Response + Authentication; NT LM 0.12 (NT LM 0.12) - uses Challenge/Response + Authentication +

    • SMB Session Startup. Passwords are encrypted (or not) according to one of + the following methods: Null (no encryption); Cleartext (no encryption); LM + and NTLM; NTLM; NTLMv2 +

    • SMB Tree Connect: Connect to a share name (e.g., \\servername\share); Connect + to a service type (e.g., IPC$ named pipe) +

    A good way to examine this process in depth is to try out SecurityFriday's SWB program +at http://www.securityfriday.com/ToolDownload/SWB/swb_doc.html. It allows you to +walk through the establishment of a SMB/CIFS session step by step.

    1.5. Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client1.5. Additional Resources

    Try mounting disks. eg:

    C:\WINDOWS\> net use d: \\servername\service -

    • Try printing. eg:

      CIFS: Common Insecurities Fail Scrutiny by "Hobbit", + http://hr.uoregon.edu/davidrl/cifs.txt +

    • C:\WINDOWS\> net use lpt1: - \\servername\spoolservice

      Doing the Samba on Windows by Financial Review, + http://afr.com/it/2002/10/01/FFXDF43AP6D.html +

    • C:\WINDOWS\> print filename -

      Implementing CIFS by Christopher R. Hertel, + http://ubiqx.org/cifs/ +

    • Just What Is SMB? by Richard Sharpe, + http://samba.anu.edu.au/cifs/docs/what-is-smb.html +

    • Opening Windows Everywhere by Mike Warfield, + http://www.linux-mag.com/1999-05/samba_01.html +

    • SMB HOWTO by David Wood, + http://www.tldp.org/HOWTO/SMB-HOWTO.html +

    • SMB/CIFS by The Root by "ledin", + http://www.phrack.org/phrack/60/p60-0x0b.txt +

    • The Story of Samba by Christopher R. Hertel, + http://www.linux-mag.com/1999-09/samba_01.html +

    • The Unofficial Samba HOWTO by David Lechnyr, + http://hr.uoregon.edu/davidrl/samba/ +

    • Understanding the Network Neighborhood by Christopher R. Hertel, + http://www.linux-mag.com/2001-05/smb_01.html +

    • Using Samba as a PDC by Andrew Bartlett, + http://www.linux-mag.com/2002-02/samba_01.html +

    1.6. What If Things Don't Work?1.6. Epilogue

    Then you might read the file chapter - Diagnosis and the - FAQ. If you are still stuck then try the mailing list or - newsgroup (look in the README for details). Samba has been - successfully installed at thousands of sites worldwide, so maybe - someone else has hit your problem and has overcome it. You could - also use the WWW site to scan back issues of the samba-digest.

    "What's fundamentally wrong is that nobody ever had any taste when they +did it. Microsoft has been very much into making the user interface look good, +but internally it's just a complete mess. And even people who program for Microsoft +and who have had years of experience, just don't know how it works internally. +Worse, nobody dares change it. Nobody dares to fix bugs because it's such a +mess that fixing one bug might just break a hundred programs that depend on +that bug. And Microsoft isn't interested in anyone fixing bugs -- they're interested +in making money. They don't have anybody who takes pride in Windows 95 as an +operating system.

    When you fix the problem pleasePeople inside Microsoft know it's a bad operating system and they still +continue obviously working on it because they want to get the next version out +because they want to have all these new features to sell more copies of the +system. send some - updates of the documentation (or source code) to one of - the documentation maintainers or the list. -

    1.6.1. Scope IDs

    By default Samba uses a blank scope ID. This means - all your windows boxes must also have a blank scope ID. - If you really want to use a non-blank scope ID then you will - need to use the 'netbios scope' smb.conf option. - All your PCs will need to have the same setting for - this to work. I do not recommend scope IDs.

    The problem with that is that over time, when you have this kind of approach, +and because nobody understands it, because nobody REALLY fixes bugs (other than +when they're really obvious), the end result is really messy. You can't trust +it because under certain circumstances it just spontaneously reboots or just +halts in the middle of something that shouldn't be strange. Normally it works +fine and then once in a blue moon for some completely unknown reason, it's dead, +and nobody knows why. Not Microsoft, not the experienced user and certainly +not the completely clueless user who probably sits there shivering thinking +"What did I do wrong?" when they didn't do anything wrong at all.

    That's what's really irritating to me."

    -- Linus Torvalds, from an interview with BOOT Magazine, Sept 1998 +(http://hr.uoregon.edu/davidrl/boot.txt)

    1.6.2. Locking

    One area which sometimes causes trouble is locking.

    1.7. Miscellaneous

    There are two types of locking which need to be - performed by a SMB server. The first is "record locking" - which allows a client to lock a range of bytes in a open file. - The second is the "deny modes" that are specified when a file - is open.

    This chapter was lovingly handcrafted on a Dell Latitude C400 laptop running Slackware Linux 9.0, +in case anyone asks.

    Record locking semantics under Unix is very - different from record locking under Windows. Versions - of Samba before 2.2 have tried to use the native - fcntl() unix system call to implement proper record - locking between different Samba clients. This can not - be fully correct due to several reasons. The simplest - is the fact that a Windows client is allowed to lock a - byte range up to 2^32 or 2^64, depending on the client - OS. The unix locking only supports byte ranges up to - 2^31. So it is not possible to correctly satisfy a - lock request above 2^31. There are many more - differences, too many to be listed here.

    Samba 2.2 and above implements record locking - completely independent of the underlying unix - system. If a byte range lock that the client requests - happens to fall into the range 0-2^31, Samba hands - this request down to the Unix system. All other locks - can not be seen by unix anyway.

    Strictly a SMB server should check for locks before - every read and write call on a file. Unfortunately with the - way fcntl() works this can be slow and may overstress the - rpc.lockd. It is also almost always unnecessary as clients - are supposed to independently make locking calls before reads - and writes anyway if locking is important to them. By default - Samba only makes locking calls when explicitly asked - to by a client, but if you set "strict locking = yes" then it will - make lock checking calls on every read and write.

    You can also disable by range locking completely - using "locking = no". This is useful for those shares that - don't support locking or don't need it (such as cdroms). In - this case Samba fakes the return codes of locking calls to - tell clients that everything is OK.

    The second class of locking is the "deny modes". These - are set by an application when it opens a file to determine - what types of access should be allowed simultaneously with - its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE - or DENY_ALL. There are also special compatibility modes called - DENY_FCB and DENY_DOS.

    This chapter is Copyright 2003 David Lechnyr (david at lechnyr dot com). +Permission is granted to copy, distribute and/or modify this document under the terms +of the GNU Free Documentation License, Version 1.2 or any later version published by the Free +Software Foundation. A copy of the license is available at http://www.gnu.org/licenses/fdl.txt.

    Chapter 2. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide

    This document should be read in conjunction with Browsing and may -be taken as the fast track guide to implementing browsing across subnets -and / or across workgroups (or domains). WINS is the best tool for resolution -of NetBIOS names to IP addesses. WINS is NOT involved in browse list handling -except by way of name to address mapping.

    Chapter 2. How to Install and Test SAMBA

    2.1. Obtaining and installing samba

    Binary packages of samba are included in almost any Linux or + Unix distribution. There are also some packages available at + the samba homepage. +

    MS Windows 2000 and later can be configured to operate with NO NetBIOS -over TCP/IP. Samba-3 and later also supports this mode of operation.

    If you need to compile samba from source, check the + appropriate appendix chapter.

    2.1. Discussion2.2. Configuring samba

    Firstly, all MS Windows networking is based on SMB (Server Message -Block) based messaging. SMB messaging may be implemented using NetBIOS or -without NetBIOS. Samba implements NetBIOS by encapsulating it over TCP/IP. -MS Windows products can do likewise. NetBIOS based networking uses broadcast -messaging to affect browse list management. When running NetBIOS over -TCP/IP this uses UDP based messaging. UDP messages can be broadcast or unicast.

    Normally, only unicast UDP messaging can be forwarded by routers. The -remote announce -parameter to smb.conf helps to project browse announcements -to remote network segments via unicast UDP. Similarly, the -remote browse sync parameter of Samba's configuration is stored in the smb.conf file, + that usually resides in /etc/samba/smb.conf + or /usr/local/samba/lib/smb.conf. You can either + edit this file yourself or do it using one of the many graphical + tools that are available, such as the web-based interface swat, that + is included with samba.

    2.2.1. Editing the smb.conf -implements browse list collation using unicast UDP.

    file

    Secondly, in those networks where Samba is the only SMB server technology -wherever possible nmbd should be configured on one (1) machine as the WINS -server. This makes it easy to manage the browsing environment. If each network -segment is configured with it's own Samba WINS server, then the only way to -get cross segment browsing to work is by using the -remote announce and the There are sample configuration files in the examples + subdirectory in the distribution. I suggest you read them + carefully so you can see how the options go together in + practice. See the man page for all the options.

    The simplest useful configuration file would be + something like this:

    [global]
+	workgroup = MYGROUP
+
+[homes]
+	guest ok = no
+	read only = no
+

    which would allow connections by anyone with an + account on the server, using either their login name or + "remote browse sync -parameters to your homes" as the service name. (Note that I also set the + workgroup that Samba is part of. See BROWSING.txt for details)

    Make sure you put the smb.conf file.

    file in the same place + you specified in theMakefile (the default is to + look for it in /usr/local/samba/lib/).

    If only one WINS server is used for an entire multi-segment network then -the use of the For more information about security settings for the + remote announce and the -[homes] share please refer to the chapter + Securing Samba.

    2.2.1.1. Test your config file with + remote browse sync parameters should NOT be necessary.

    As of Samba 3 WINS replication is being worked on. The bulk of the code has -been committed, but it still needs maturation.

    testparm

    Right now samba WINS does not support MS-WINS replication. This means that -when setting up Samba as a WINS server there must only be one It's important that you test the validity of your + smb.conf file using the nmbd configured -as a WINS server on the network. Some sites have used multiple Samba WINS -servers for redundancy (one server per subnet) and then used -remote browse sync and remote announce -to affect browse list collation across all -segments. Note that this means clients will only resolve local names, -and must be configured to use DNS to resolve names on other subnets in -order to resolve the IP addresses of the servers they can see on other -subnets. This setup is not recommended, but is mentioned as a practical -consideration (ie: an 'if all else fails' scenario).

    testparm program. + If testparm runs OK then it will list the loaded services. If + not it will give an error message.

    Lastly, take note that browse lists are a collection of unreliable broadcast -messages that are repeated at intervals of not more than 15 minutes. This means -that it will take time to establish a browse list and it can take up to 45 -minutes to stabilise, particularly across network segments.

    Make sure it runs OK and that the services look + reasonable before proceeding.

    Always run testparm again when you change + smb.conf!

    2.2. How browsing functions and how to deploy stable and -dependable browsing using Samba

    As stated above, MS Windows machines register their NetBIOS names -(i.e.: the machine name for each service type in operation) on start -up. Also, as stated above, the exact method by which this name registration -takes place is determined by whether or not the MS Windows client/server -has been given a WINS server address, whether or not LMHOSTS lookup -is enabled, or if DNS for NetBIOS name resolution is enabled, etc.

    2.2.2. SWAT

    In the case where there is no WINS server all name registrations as -well as name lookups are done by UDP broadcast. This isolates name -resolution to the local subnet, unless LMHOSTS is used to list all -names and IP addresses. In such situations Samba provides a means by -which the samba server name may be forcibly injected into the browse -list of a remote MS Windows network (using the -remote announce parameter).

    SWAT is a web-based interface that helps you configure samba. + SWAT might not be available in the samba package on your platform, + but in a seperate package. Please read the swat manpage + on compiling, installing and configuring swat from source. +

    Where a WINS server is used, the MS Windows client will use UDP -unicast to register with the WINS server. Such packets can be routed -and thus WINS allows name resolution to function across routed networks.

    To launch SWAT just run your favorite web browser and + point it at "http://localhost:901/". Replace localhost with the name of the computer you are running samba on if you + are running samba on a different computer then your browser.

    During the startup process an election will take place to create a -local master browser if one does not already exist. On each NetBIOS network -one machine will be elected to function as the domain master browser. This -domain browsing has nothing to do with MS security domain control. -Instead, the domain master browser serves the role of contacting each local -master browser (found by asking WINS or from LMHOSTS) and exchanging browse -list contents. This way every master browser will eventually obtain a complete -list of all machines that are on the network. Every 11-15 minutes an election -is held to determine which machine will be the master browser. By the nature of -the election criteria used, the machine with the highest uptime, or the -most senior protocol version, or other criteria, will win the election -as domain master browser.

    Note that you can attach to SWAT from any IP connected + machine but connecting from a remote machine leaves your + connection open to password sniffing as passwords will be sent + in the clear over the wire.

    2.3. Try listing the shares available on your + server

    Clients wishing to browse the network make use of this list, but also depend -on the availability of correct name resolution to the respective IP -address/addresses.

    $ smbclient -L + yourhostname

    Any configuration that breaks name resolution and/or browsing intrinsics -will annoy users because they will have to put up with protracted -inability to use the network services.

    You should get back a list of shares available on + your server. If you don't then something is incorrectly setup. + Note that this method can also be used to see what shares + are available on other LanManager clients (such as WfWg).

    Samba supports a feature that allows forced synchonisation -of browse lists across routed networks using the remote -browse sync parameter in the smb.conf file. -This causes Samba to contact the local master browser on a remote network and -to request browse list synchronisation. This effectively bridges -two networks that are separated by routers. The two remote -networks may use either broadcast based name resolution or WINS -based name resolution, but it should be noted that the If you choose user level security then you may find + that Samba requests a password before it will list the shares. + See the remote -browse sync parameter provides browse list synchronisation - and -that is distinct from name to address resolution, in other -words, for cross subnet browsing to function correctly it is -essential that a name to address resolution mechanism be provided. -This mechanism could be via DNS, /etc/hosts, -and so on.

    smbclient man page for details. (you + can force it to list the shares without a password by + adding the option -U% to the command line. This will not work + with non-Samba servers)

    2.3. Use of the Remote Announce parameter2.4. Try connecting with the unix client

    The remote announce parameter of -$ smbclient //yourhostname/aservice

    Typically the yourhostname + would be the name of the host where you installed smbd. + The aservice is + any service you have defined in the smb.conf can be used to forcibly ensure -that all the NetBIOS names on a network get announced to a remote network. -The syntax of the + file. Try your user name if you just have a remote announce parameter is: -

    	remote announce = a.b.c.d [e.f.g.h] ...
    [homes] -_or_ -
    	remote announce = smb.conf.
    For example if your unix host is a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...
    bambi - -where: -

    a.b.c.d and -e.f.g.h
    fred you would type:

    is either the LMB (Local Master Browser) IP address -or the broadcst address of the remote network. -ie: the LMB is at 192.168.1.10, or the address -could be given as 192.168.1.255 where the netmask -is assumed to be 24 bits (255.255.255.0). -When the remote announcement is made to the broadcast -address of the remote network every host will receive -our announcements. This is noisy and therefore -undesirable but may be necessary if we do NOT know -the IP address of the remote LMB.

    $ smbclient //WORKGROUP

    is optional and can be either our own workgroup -or that of the remote network. If you use the -workgroup name of the remote network then our -NetBIOS machine names will end up looking like -they belong to that workgroup, this may cause -name resolution problems and should be avoided.

    bambi/fred +

    2.4. Use of the Remote Browse Sync parameter2.5. Try connecting from a DOS, WfWg, Win9x, WinNT, + Win2k, OS/2, etc... client

    The remote browse sync parameter of -smb.conf is used to announce to -another LMB that it must synchronise it's NetBIOS name list with our -Samba LMB. It works ONLY if the Samba server that has this option is -simultaneously the LMB on it's network segment.

    Try mounting disks. eg:

    The syntax of the remote browse sync parameter is: - -

    remote browse sync = a.b.c.d
    - -where a.b.c.d is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.

    C:\WINDOWS\> net use d: \\servername\service +

    Try printing. eg:

    C:\WINDOWS\> net use lpt1: + \\servername\spoolservice

    C:\WINDOWS\> print filename +

    2.5. Use of WINS2.6. What If Things Don't Work?

    Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly -recommended. Every NetBIOS machine registers it's name together with a -name_type value for each of of several types of service it has available. -eg: It registers it's name directly as a unique (the type 0x03) name. -It also registers it's name if it is running the lanmanager compatible -server service (used to make shares and printers available to other users) -by registering the server (the type 0x20) name.

    Then you might read the file chapter + Diagnosis and the + FAQ. If you are still stuck then try to follow + the Analysing and Solving Problems chapter + Samba has been successfully installed at thousands of sites worldwide, + so maybe someone else has hit your problem and has overcome it.

    2.6.1. Scope IDs

    All NetBIOS names are up to 15 characters in length. The name_type variable -is added to the end of the name - thus creating a 16 character name. Any -name that is shorter than 15 characters is padded with spaces to the 15th -character. ie: All NetBIOS names are 16 characters long (including the -name_type information).

    By default Samba uses a blank scope ID. This means + all your windows boxes must also have a blank scope ID. + If you really want to use a non-blank scope ID then you will + need to use the 'netbios scope' smb.conf option. + All your PCs will need to have the same setting for + this to work. I do not recommend scope IDs.

    2.6.2. Locking

    WINS can store these 16 character names as they get registered. A client -that wants to log onto the network can ask the WINS server for a list -of all names that have registered the NetLogon service name_type. This saves -broadcast traffic and greatly expedites logon processing. Since broadcast -name resolution can not be used across network segments this type of -information can only be provided via WINS _or_ via statically configured -lmhosts files that must reside on all clients in the -absence of WINS.

    One area which sometimes causes trouble is locking.

    WINS also serves the purpose of forcing browse list synchronisation by all -LMB's. LMB's must synchronise their browse list with the DMB (domain master -browser) and WINS helps the LMB to identify it's DMB. By definition this -will work only within a single workgroup. Note that the domain master browser -has NOTHING to do with what is referred to as an MS Windows NT Domain. The -later is a reference to a security environment while the DMB refers to the -master controller for browse list information only.

    There are two types of locking which need to be + performed by a SMB server. The first is "record locking" + which allows a client to lock a range of bytes in a open file. + The second is the "deny modes" that are specified when a file + is open.

    Use of WINS will work correctly only if EVERY client TCP/IP protocol stack -has been configured to use the WINS server/s. Any client that has not been -configured to use the WINS server will continue to use only broadcast based -name registration so that WINS may NEVER get to know about it. In any case, -machines that have not registered with a WINS server will fail name to address -lookup attempts by other clients and will therefore cause workstation access -errors.

    Record locking semantics under Unix is very + different from record locking under Windows. Versions + of Samba before 2.2 have tried to use the native + fcntl() unix system call to implement proper record + locking between different Samba clients. This can not + be fully correct due to several reasons. The simplest + is the fact that a Windows client is allowed to lock a + byte range up to 2^32 or 2^64, depending on the client + OS. The unix locking only supports byte ranges up to + 2^31. So it is not possible to correctly satisfy a + lock request above 2^31. There are many more + differences, too many to be listed here.

    To configure Samba as a WINS server just add -wins support = yes to the smb.conf -file [globals] section.

    Samba 2.2 and above implements record locking + completely independent of the underlying unix + system. If a byte range lock that the client requests + happens to fall into the range 0-2^31, Samba hands + this request down to the Unix system. All other locks + can not be seen by unix anyway.

    To configure Samba to register with a WINS server just add -"wins server = a.b.c.d" to your smb.conf file [globals] section.

    Strictly a SMB server should check for locks before + every read and write call on a file. Unfortunately with the + way fcntl() works this can be slow and may overstress the + rpc.lockd. It is also almost always unnecessary as clients + are supposed to independently make locking calls before reads + and writes anyway if locking is important to them. By default + Samba only makes locking calls when explicitly asked + to by a client, but if you set "strict locking = yes" then it will + make lock checking calls on every read and write.

    You can also disable by range locking completely + using "locking = no". This is useful for those shares that + don't support locking or don't need it (such as cdroms). In + this case Samba fakes the return codes of locking calls to + tell clients that everything is OK.

    The second class of locking is the "deny modes". These + are set by an application when it opens a file to determine + what types of access should be allowed simultaneously with + its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE + or DENY_ALL. There are also special compatibility modes called + DENY_FCB and DENY_DOS.

    Chapter 3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide

    This document should be read in conjunction with Browsing and may +be taken as the fast track guide to implementing browsing across subnets +and / or across workgroups (or domains). WINS is the best tool for resolution +of NetBIOS names to IP addesses. WINS is NOT involved in browse list handling +except by way of name to address mapping.

    Never use both wins support = yes together -with wins server = a.b.c.d -particularly not using it's own IP address. -Specifying both will cause nmbd to refuse to start!

    MS Windows 2000 and later can be configured to operate with NO NetBIOS +over TCP/IP. Samba-3 and later also supports this mode of operation.

    2.6. Do NOT use more than one (1) protocol on MS Windows machines3.1. Discussion

    A very common cause of browsing problems results from installing more than -one protocol on an MS Windows machine.

    Firstly, all MS Windows networking is based on SMB (Server Message +Block) based messaging. SMB messaging may be implemented using NetBIOS or +without NetBIOS. Samba implements NetBIOS by encapsulating it over TCP/IP. +MS Windows products can do likewise. NetBIOS based networking uses broadcast +messaging to affect browse list management. When running NetBIOS over +TCP/IP this uses UDP based messaging. UDP messages can be broadcast or unicast.

    Every NetBIOS machine takes part in a process of electing the LMB (and DMB) -every 15 minutes. A set of election criteria is used to determine the order -of precidence for winning this election process. A machine running Samba or -Windows NT will be biased so that the most suitable machine will predictably -win and thus retain it's role.

    Normally, only unicast UDP messaging can be forwarded by routers. The +remote announce +parameter to smb.conf helps to project browse announcements +to remote network segments via unicast UDP. Similarly, the +remote browse sync parameter of smb.conf +implements browse list collation using unicast UDP.

    The election process is "fought out" so to speak over every NetBIOS network -interface. In the case of a Windows 9x machine that has both TCP/IP and IPX -installed and has NetBIOS enabled over both protocols the election will be -decided over both protocols. As often happens, if the Windows 9x machine is -the only one with both protocols then the LMB may be won on the NetBIOS -interface over the IPX protocol. Samba will then lose the LMB role as Windows -9x will insist it knows who the LMB is. Samba will then cease to function -as an LMB and thus browse list operation on all TCP/IP only machines will -fail.

    Secondly, in those networks where Samba is the only SMB server technology +wherever possible nmbd should be configured on one (1) machine as the WINS +server. This makes it easy to manage the browsing environment. If each network +segment is configured with it's own Samba WINS server, then the only way to +get cross segment browsing to work is by using the +remote announce and the remote browse sync +parameters to your smb.conf file.

    Windows 95, 98, 98se, Me are referred to generically as Windows 9x. -The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly -referred to as the WinNT family, but it should be recognised that 2000 and -XP/2003 introduce new protocol extensions that cause them to behave -differently from MS Windows NT4. Generally, where a server does NOT support -the newer or extended protocol, these will fall back to the NT4 protocols.

    If only one WINS server is used for an entire multi-segment network then +the use of the remote announce and the +remote browse sync parameters should NOT be necessary.

    The safest rule of all to follow it this - USE ONLY ONE PROTOCOL!

    As of Samba 3 WINS replication is being worked on. The bulk of the code has +been committed, but it still needs maturation.

    Right now samba WINS does not support MS-WINS replication. This means that +when setting up Samba as a WINS server there must only be one nmbd configured +as a WINS server on the network. Some sites have used multiple Samba WINS +servers for redundancy (one server per subnet) and then used +remote browse sync and remote announce +to affect browse list collation across all +segments. Note that this means clients will only resolve local names, +and must be configured to use DNS to resolve names on other subnets in +order to resolve the IP addresses of the servers they can see on other +subnets. This setup is not recommended, but is mentioned as a practical +consideration (ie: an 'if all else fails' scenario).

    Lastly, take note that browse lists are a collection of unreliable broadcast +messages that are repeated at intervals of not more than 15 minutes. This means +that it will take time to establish a browse list and it can take up to 45 +minutes to stabilise, particularly across network segments.

    2.7. Name Resolution Order3.2. How browsing functions and how to deploy stable and +dependable browsing using Samba

    Resolution of NetBIOS names to IP addresses can take place using a number -of methods. The only ones that can provide NetBIOS name_type information -are:

    As stated above, MS Windows machines register their NetBIOS names +(i.e.: the machine name for each service type in operation) on start +up. Also, as stated above, the exact method by which this name registration +takes place is determined by whether or not the MS Windows client/server +has been given a WINS server address, whether or not LMHOSTS lookup +is enabled, or if DNS for NetBIOS name resolution is enabled, etc.

    WINS: the best tool!
    LMHOSTS: is static and hard to maintain.
    Broadcast: uses UDP and can not resolve names across remote segments.
    In the case where there is no WINS server all name registrations as +well as name lookups are done by UDP broadcast. This isolates name +resolution to the local subnet, unless LMHOSTS is used to list all +names and IP addresses. In such situations Samba provides a means by +which the samba server name may be forcibly injected into the browse +list of a remote MS Windows network (using the +remote announce parameter).

    Where a WINS server is used, the MS Windows client will use UDP +unicast to register with the WINS server. Such packets can be routed +and thus WINS allows name resolution to function across routed networks.

    Alternative means of name resolution includes:

    During the startup process an election will take place to create a +local master browser if one does not already exist. On each NetBIOS network +one machine will be elected to function as the domain master browser. This +domain browsing has nothing to do with MS security domain control. +Instead, the domain master browser serves the role of contacting each local +master browser (found by asking WINS or from LMHOSTS) and exchanging browse +list contents. This way every master browser will eventually obtain a complete +list of all machines that are on the network. Every 11-15 minutes an election +is held to determine which machine will be the master browser. By the nature of +the election criteria used, the machine with the highest uptime, or the +most senior protocol version, or other criteria, will win the election +as domain master browser.

    /etc/hosts: is static, hard to maintain, and lacks name_type info
    DNS: is a good choice but lacks essential name_type info.
    Clients wishing to browse the network make use of this list, but also depend +on the availability of correct name resolution to the respective IP +address/addresses.

    Any configuration that breaks name resolution and/or browsing intrinsics +will annoy users because they will have to put up with protracted +inability to use the network services.

    Many sites want to restrict DNS lookups and want to avoid broadcast name -resolution traffic. The "name resolve order" parameter is of great help here. -The syntax of the "name resolve order" parameter is: +>Samba supports a feature that allows forced synchonisation +of browse lists across routed networks using the remote +browse sync parameter in the smb.conf file. +This causes Samba to contact the local master browser on a remote network and +to request browse list synchronisation. This effectively bridges +two networks that are separated by routers. The two remote +networks may use either broadcast based name resolution or WINS +based name resolution, but it should be noted that the remote +browse sync parameter provides browse list synchronisation - and +that is distinct from name to address resolution, in other +words, for cross subnet browsing to function correctly it is +essential that a name to address resolution mechanism be provided. +This mechanism could be via DNS, /etc/hosts, +and so on.

    3.3. Use of the Remote Announce parameter

    The remote announce parameter of +smb.conf can be used to forcibly ensure +that all the NetBIOS names on a network get announced to a remote network. +The syntax of the remote announce parameter is: 

    name resolve order = wins lmhosts bcast host
    remote announce = a.b.c.d [e.f.g.h] ... _or_ 
    name resolve order = wins lmhosts  	(eliminates bcast and host)
    remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ... -The default is: -
    name  resolve order = host lmhost wins bcast
    . -where "host" refers the the native methods used by the Unix system -to implement the gethostbyname() function call. This is normally -controlled by /etc/host.conf, /etc/nsswitch.conf and /etc/resolv.conf.

    a.b.c.d and +e.f.g.h

    is either the LMB (Local Master Browser) IP address +or the broadcst address of the remote network. +ie: the LMB is at 192.168.1.10, or the address +could be given as 192.168.1.255 where the netmask +is assumed to be 24 bits (255.255.255.0). +When the remote announcement is made to the broadcast +address of the remote network every host will receive +our announcements. This is noisy and therefore +undesirable but may be necessary if we do NOT know +the IP address of the remote LMB.

    WORKGROUP

    is optional and can be either our own workgroup +or that of the remote network. If you use the +workgroup name of the remote network then our +NetBIOS machine names will end up looking like +they belong to that workgroup, this may cause +name resolution problems and should be avoided.

    Chapter 3. User information database

    3.1. Introduction3.4. Use of the Remote Browse Sync parameter

    Old windows clients send plain text passwords over the wire. - Samba can check these passwords by crypting them and comparing them - to the hash stored in the unix user database. -

    Newer windows clients send encrypted passwords (so-called - Lanman and NT hashes) over - the wire, instead of plain text passwords. The newest clients - will only send encrypted passwords and refuse to send plain text - passwords, unless their registry is tweaked. -

    These passwords can't be converted to unix style encrypted - passwords. Because of that you can't use the standard unix - user database, and you have to store the Lanman and NT hashes - somewhere else.

    The remote browse sync parameter of +smb.conf is used to announce to +another LMB that it must synchronise it's NetBIOS name list with our +Samba LMB. It works ONLY if the Samba server that has this option is +simultaneously the LMB on it's network segment.

    Next to a differently encrypted passwords, - windows also stores certain data for each user - that is not stored in a unix user database, e.g. - workstations the user may logon from, the location where his/her - profile is stored, etc. - Samba retrieves and stores this information using a "passdb backend". - Commonly - available backends are LDAP, plain text file, MySQL and nisplus. - For more information, see the documentation about the - The syntax of the passdb backend = parameter. -

    remote browse sync parameter is: + +
    remote browse sync = a.b.c.d
    + +where a.b.c.d is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.

    3.2. Important Notes About Security3.5. Use of WINS

    The unix and SMB password encryption techniques seem similar - on the surface. This similarity is, however, only skin deep. The unix - scheme typically sends clear text passwords over the network when - logging in. This is bad. The SMB encryption scheme never sends the - cleartext password over the network but it does store the 16 byte - hashed values on disk. This is also bad. Why? Because the 16 byte hashed - values are a "password equivalent". You cannot derive the user's - password from them, but they could potentially be used in a modified - client to gain access to a server. This would require considerable - technical knowledge on behalf of the attacker but is perfectly possible. - You should thus treat the data stored in whatever - passdb backend you use (smbpasswd file, ldap, mysql) as though it contained the - cleartext passwords of all your users. Its contents must be kept - secret, and the file should be protected accordingly.

    Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly +recommended. Every NetBIOS machine registers it's name together with a +name_type value for each of of several types of service it has available. +eg: It registers it's name directly as a unique (the type 0x03) name. +It also registers it's name if it is running the lanmanager compatible +server service (used to make shares and printers available to other users) +by registering the server (the type 0x20) name.

    Ideally we would like a password scheme which neither requires - plain text passwords on the net or on disk. Unfortunately this - is not available as Samba is stuck with being compatible with - other SMB systems (WinNT, WfWg, Win95 etc).

    All NetBIOS names are up to 15 characters in length. The name_type variable +is added to the end of the name - thus creating a 16 character name. Any +name that is shorter than 15 characters is padded with spaces to the 15th +character. ie: All NetBIOS names are 16 characters long (including the +name_type information).

    WINS can store these 16 character names as they get registered. A client +that wants to log onto the network can ask the WINS server for a list +of all names that have registered the NetLogon service name_type. This saves +broadcast traffic and greatly expedites logon processing. Since broadcast +name resolution can not be used across network segments this type of +information can only be provided via WINS _or_ via statically configured +lmhosts files that must reside on all clients in the +absence of WINS.

    WINS also serves the purpose of forcing browse list synchronisation by all +LMB's. LMB's must synchronise their browse list with the DMB (domain master +browser) and WINS helps the LMB to identify it's DMB. By definition this +will work only within a single workgroup. Note that the domain master browser +has NOTHING to do with what is referred to as an MS Windows NT Domain. The +later is a reference to a security environment while the DMB refers to the +master controller for browse list information only.

    Use of WINS will work correctly only if EVERY client TCP/IP protocol stack +has been configured to use the WINS server/s. Any client that has not been +configured to use the WINS server will continue to use only broadcast based +name registration so that WINS may NEVER get to know about it. In any case, +machines that have not registered with a WINS server will fail name to address +lookup attempts by other clients and will therefore cause workstation access +errors.

    To configure Samba as a WINS server just add +wins support = yes to the smb.conf +file [globals] section.

    To configure Samba to register with a WINS server just add +"wins server = a.b.c.d" to your smb.conf file [globals] section.

    Note that Windows NT 4.0 Service pack 3 changed the - default for permissible authentication so that plaintext - passwords are Never use both wins support = yes together +with wins server = a.b.c.d +particularly not using it's own IP address. +Specifying both will cause nmbd to refuse to start!

    3.5.1. WINS Replication

    Samba-3 permits WINS replication through the use of the wrepld utility. +This tool is not currently capable of being used as it is still in active development. +As soon as this tool becomes moderately functional we will prepare man pages and enhance this +section of the documentation to provide usage and technical details.

    3.5.2. Static WINS Entries

    New to Samba-3 is a tool called winsedit that may be used to add +static WINS entries to the WINS database. This tool can be used also to modify entries +existing in the WINS database.

    The development of the winsedit tool was made necessary due to the migration +of the older style wins.dat file into a new tdb binary backend data store.

    3.6. Do NOT use more than one (1) protocol on MS Windows machines

    A very common cause of browsing problems results from installing more than +one protocol on an MS Windows machine.

    Every NetBIOS machine takes part in a process of electing the LMB (and DMB) +every 15 minutes. A set of election criteria is used to determine the order +of precidence for winning this election process. A machine running Samba or +Windows NT will be biased so that the most suitable machine will predictably +win and thus retain it's role.

    The election process is "fought out" so to speak over every NetBIOS network +interface. In the case of a Windows 9x machine that has both TCP/IP and IPX +installed and has NetBIOS enabled over both protocols the election will be +decided over both protocols. As often happens, if the Windows 9x machine is +the only one with both protocols then the LMB may be won on the NetBIOS +interface over the IPX protocol. Samba will then lose the LMB role as Windows +9x will insist it knows who the LMB is. Samba will then cease to function +as an LMB and thus browse list operation on all TCP/IP only machines will +fail.

    neverWindows 95, 98, 98se, Me are referred to generically as Windows 9x. +The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly +referred to as the WinNT family, but it should be recognised that 2000 and +XP/2003 introduce new protocol extensions that cause them to behave +differently from MS Windows NT4. Generally, where a server does NOT support +the newer or extended protocol, these will fall back to the NT4 protocols. sent over the wire. - The solution to this is either to switch to encrypted passwords - with Samba or edit the Windows NT registry to re-enable plaintext - passwords. See the document WinNT.txt for details on how to do - this.

    Other Microsoft operating systems which also exhibit - this behavior includes

    The safest rule of all to follow it this - USE ONLY ONE PROTOCOL!

    3.7. Name Resolution Order

    These versions of MS Windows do not support full domain - security protocols, although they may log onto a domain environment. - Of these Only MS Windows XP Home does NOT support domain logons.

    Resolution of NetBIOS names to IP addresses can take place using a number +of methods. The only ones that can provide NetBIOS name_type information +are:

    WINS: the best tool!LMHOSTS: is static and hard to maintain.Broadcast: uses UDP and can not resolve names across remote segments.
    MS DOS Network client 3.0 with - the basic network redirector installed
    Windows 95 with the network redirector - update installed
    Windows 98 [se]
    Windows Me
    Windows XP Home

    The following versions of MS Windows fully support domain - security protocols.

    Alternative means of name resolution includes:

    /etc/hosts: is static, hard to maintain, and lacks name_type infoDNS: is a good choice but lacks essential name_type info.
    Windows NT 3.5x
    Windows NT 4.0

    Many sites want to restrict DNS lookups and want to avoid broadcast name +resolution traffic. The "name resolve order" parameter is of great help here. +The syntax of the "name resolve order" parameter is: +

    name resolve order = wins lmhosts bcast host
    +_or_ +
    name resolve order = wins lmhosts  	(eliminates bcast and host)
    +The default is: +
    name  resolve order = host lmhost wins bcast
    . +where "host" refers the the native methods used by the Unix system +to implement the gethostbyname() function call. This is normally +controlled by /etc/host.conf, /etc/nsswitch.conf and /etc/resolv.conf.

    Chapter 4. User information database

    4.1. Introduction

    Old windows clients send plain text passwords over the wire. + Samba can check these passwords by crypting them and comparing them + to the hash stored in the unix user database. +

    Newer windows clients send encrypted passwords (so-called + Lanman and NT hashes) over + the wire, instead of plain text passwords. The newest clients + will only send encrypted passwords and refuse to send plain text + passwords, unless their registry is tweaked. +

    These passwords can't be converted to unix style encrypted + passwords. Because of that you can't use the standard unix + user database, and you have to store the Lanman and NT hashes + somewhere else.

    Next to a differently encrypted passwords, + windows also stores certain data for each user + that is not stored in a unix user database, e.g. + workstations the user may logon from, the location where his/her + profile is stored, etc. + Samba retrieves and stores this information using a "passdb backend". + Commonly + available backends are LDAP, plain text file, MySQL and nisplus. + For more information, see the documentation about the + passdb backend = parameter. +

    4.2. Important Notes About Security

    The unix and SMB password encryption techniques seem similar + on the surface. This similarity is, however, only skin deep. The unix + scheme typically sends clear text passwords over the network when + logging in. This is bad. The SMB encryption scheme never sends the + cleartext password over the network but it does store the 16 byte + hashed values on disk. This is also bad. Why? Because the 16 byte hashed + values are a "password equivalent". You cannot derive the user's + password from them, but they could potentially be used in a modified + client to gain access to a server. This would require considerable + technical knowledge on behalf of the attacker but is perfectly possible. + You should thus treat the data stored in whatever + passdb backend you use (smbpasswd file, ldap, mysql) as though it contained the + cleartext passwords of all your users. Its contents must be kept + secret, and the file should be protected accordingly.

    Ideally we would like a password scheme which neither requires + plain text passwords on the net or on disk. Unfortunately this + is not available as Samba is stuck with being compatible with + other SMB systems (WinNT, WfWg, Win95 etc).

    Note that Windows NT 4.0 Service pack 3 changed the + default for permissible authentication so that plaintext + passwords are never sent over the wire. + The solution to this is either to switch to encrypted passwords + with Samba or edit the Windows NT registry to re-enable plaintext + passwords. See the document WinNT.txt for details on how to do + this.

    Other Microsoft operating systems which also exhibit + this behavior includes

    These versions of MS Windows do not support full domain + security protocols, although they may log onto a domain environment. + Of these Only MS Windows XP Home does NOT support domain logons.

    MS DOS Network client 3.0 with + the basic network redirector installed
    Windows 95 with the network redirector + update installed
    Windows 98 [se]
    Windows Me
    Windows XP Home

    The following versions of MS Windows fully support domain + security protocols.

    Windows NT 3.5x
    Windows NT 4.0

    Note :All current release of - Microsoft SMB/CIFS clients support authentication via the - SMB Challenge/Response mechanism described here. Enabling - clear text authentication does not disable the ability - of the client to participate in encrypted authentication.

    MS Windows clients will cache the encrypted password alone. - Even when plain text passwords are re-enabled, through the appropriate - registry change, the plain text password is NEVER cached. This means that - in the event that a network connections should become disconnected (broken) - only the cached (encrypted) password will be sent to the resource server - to affect a auto-reconnect. If the resource server does not support encrypted - passwords the auto-reconnect will fail. USE OF ENCRYPTED PASSWORDS - IS STRONGLY ADVISED.

    3.2.1. Advantages of SMB Encryption4.2.1. Advantages of SMB Encryption

    3.2.2. Advantages of non-encrypted passwords4.2.2. Advantages of non-encrypted passwords

    3.3. The smbpasswd Command4.3. The smbpasswd Command

    The smbpasswd utility is a utility similar to the @@ -2921,8 +3271,8 @@ CLASS="SECT1" >

    3.4. Plain text4.4. Plain text

    Older versions of samba retrieved user information from the unix user database @@ -2941,8 +3291,8 @@ CLASS="SECT1" >

    3.5. TDB4.5. TDB

    Samba can also store the user data in a "TDB" (Trivial Database). Using this backend @@ -2954,16 +3304,16 @@ CLASS="SECT1" >

    3.6. LDAP4.6. LDAP

    3.6.1. Introduction4.6.1. Introduction

    This document describes how to use an LDAP directory for storing Samba user @@ -3030,8 +3380,8 @@ CLASS="SECT2" >

    3.6.2. Introduction4.6.2. Introduction

    Traditionally, when configuring As a result of these defeciencies, a more robust means of storing user attributes used by smbd was developed. The API which defines access to user accounts is commonly referred to as the samdb interface (previously this was called the passdb -API, and is still so named in the CVS trees). In Samba 2.2.3, enabling support -for a samdb backend (e.g. --with-ldapsam or ---with-tdbsam) requires compile time support.

    When compiling Samba to include the --with-ldapsam autoconf -option, smbd (and associated tools) will store and lookup user accounts in -an LDAP directory. In reality, this is very easy to understand. If you are -comfortable with using an smbpasswd file, simply replace "smbpasswd" with -"LDAP directory" in all the documentation.

    There are a few points to stress about what the --with-ldapsam +>There are a few points to stress about what the ldapsam does not provide. The LDAP support referred to in the this documentation does not include:

    3.6.3. Supported LDAP Servers4.6.3. Supported LDAP Servers

    The LDAP samdb code in 2.2.3 (and later) has been developed and tested @@ -3165,8 +3495,8 @@ CLASS="SECT2" >

    3.6.4. Schema and Relationship to the RFC 2307 posixAccount4.6.4. Schema and Relationship to the RFC 2307 posixAccount

    Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in @@ -3222,16 +3552,16 @@ CLASS="SECT2" >

    3.6.5. Configuring Samba with LDAP4.6.5. Configuring Samba with LDAP

    3.6.5.1. OpenLDAP configuration4.6.5.1. OpenLDAP configuration

    To include support for the sambaAccount object in an OpenLDAP directory @@ -3277,9 +3607,7 @@ include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/samba.schema - -## uncomment this line if you want to support the RFC2307 (NIS) schema -## include /etc/openldap/schema/nis.schema +include /etc/openldap/schema/nis.schema ....

    3.6.5.2. Configuring Samba4.6.5.2. Configuring Samba

    The following parameters are available in smb.conf only with

    3.6.6. Accounts and Groups management4.6.6. Accounts and Groups management

    As users accounts are managed thru the sambaAccount objectclass, you should @@ -3453,8 +3781,8 @@ CLASS="SECT2" >

    3.6.7. Security and sambaAccount4.6.7. Security and sambaAccount

    There are two important points to remember when discussing the security @@ -3489,9 +3817,8 @@ CLASS="EMPHASIS" >These password hashes are clear text equivalents and can be used to impersonate the user without deriving the original clear text strings. For more information on the details of LM/NT password hashes, refer to the ENCRYPTION chapterUser Database of the Samba-HOWTO-Collection.

    To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults @@ -3532,8 +3859,8 @@ CLASS="SECT2" >

    3.6.8. LDAP specials attributes for sambaAccounts4.6.8. LDAP specials attributes for sambaAccounts

    The sambaAccount objectclass is composed of the following attributes:

    3.6.9. Example LDIF Entries for a sambaAccount4.6.9. Example LDIF Entries for a sambaAccount

    The following is a working LDIF with the inclusion of the posixAccount objectclass:

    3.7. MySQL4.7. MySQL

    3.7.1. Creating the database4.7.1. Creating the database

    You either can set up your own table and specify the field names to pdb_mysql (see below @@ -3842,8 +4169,8 @@ CLASS="SECT2" >

    3.7.2. Configuring4.7.2. Configuring

    This plugin lacks some good documentation, but here is some short info:

    3.7.3. Using plaintext passwords or encrypted password4.7.3. Using plaintext passwords or encrypted password

    I strongly discourage the use of plaintext passwords, however, you can use them:

    3.7.4. Getting non-column data from the table4.7.4. Getting non-column data from the table

    It is possible to have not all data in the database and making some 'constant'.

    3.8. XML4.8. XML

    This module requires libxml2 to be installed.

    II. Type of installation

    Introduction

    Table of Contents
    4. Nomenclature of Server Types
    4.1. Stand Alone Server
    4.2. Domain Member Server
    4.3. Domain Controller
    4.3.1. Domain Controller Types
    5. Samba as Stand-Alone Server
    5.1. User and Share security level
    5.1.1. User Level Security
    5.1.2. Share Level Security
    5.1.3. Server Level Security
    5.1.4. Domain Level Security
    5.1.5. ADS Level Security
    6. Samba as an NT4 or Win2k Primary Domain Controller
    6.1. Prerequisite Reading
    6.2. Background
    6.3. Configuring the Samba Domain Controller
    6.4. Creating Machine Trust Accounts and Joining Clients to the Domain
    6.4.1. Manual Creation of Machine Trust Accounts
    6.4.2. "On-the-Fly" Creation of Machine Trust Accounts
    6.4.3. Joining the Client to the Domain
    6.5. Common Problems and Errors
    6.6. What other help can I get?
    6.7. Domain Control for Windows 9x/ME
    6.7.1. Configuration Instructions: Network Logons
    7. Samba Backup Domain Controller to Samba Domain Control
    7.1. Prerequisite Reading
    7.2. Background
    7.3. What qualifies a Domain Controller on the network?
    7.3.1. How does a Workstation find its domain controller?
    7.3.2. When is the PDC needed?
    7.4. Can Samba be a Backup Domain Controller to an NT PDC?
    7.5. How do I set up a Samba BDC?
    7.5.1. How do I replicate the smbpasswd file?
    7.5.2. Can I do this all with LDAP?
    8. Samba as a ADS domain member
    8.1. Setup your smb.conf
    8.2. Setup your /etc/krb5.conf
    8.3. Create the computer account
    8.3.1. Possible errors
    8.4. Test your server setup
    8.5. Testing with smbclient
    8.6. Notes
    9. Samba as a NT4 or Win2k domain member
    9.1. Joining an NT Domain with Samba 3.0
    9.2. Why is this better than security = server?

    Chapter 4. Nomenclature of Server Types

    Chapter 5. Nomenclature of Server Types

    Adminstrators of Microsoft networks often refer to there being three different type of servers:

    4.1. Stand Alone Server5.1. Stand Alone Server

    The term

    4.2. Domain Member Server5.2. Domain Member Server

    This mode of server operation involves the samba machine being made a member @@ -4460,8 +4492,8 @@ CLASS="SECT1" >

    4.3. Domain Controller5.3. Domain Controller

    Over the years public perceptions of what Domain Control really is has taken on an @@ -4472,8 +4504,8 @@ CLASS="SECT2" >

    4.3.1. Domain Controller Types5.3.1. Domain Controller Types

    ADS Domain Controller.

    .

    Chapter 5. Samba as Stand-Alone ServerChapter 6. Samba as Stand-Alone Server

    In this section the function and purpose of Samba's

    5.1. User and Share security level6.1. User and Share security level

    A SMB server tells the client at startup what "security level" it is @@ -4584,8 +4616,8 @@ CLASS="SECT2" >

    5.1.1. User Level Security6.1.1. User Level Security

    I'll describe user level security first, as its simpler. In user level @@ -4625,8 +4657,8 @@ CLASS="SECT2" >

    5.1.2. Share Level Security6.1.2. Share Level Security

    Ok, now for share level security. In share level security the client @@ -4662,8 +4694,8 @@ CLASS="SECT2" >

    5.1.3. Server Level Security6.1.3. Server Level Security

    Finally "server level" security. In server level security the samba @@ -4698,8 +4730,8 @@ CLASS="SECT3" >

    5.1.3.1. Configuring Samba for Seemless Windows Network Integration6.1.3.1. Configuring Samba for Seemless Windows Network Integration

    MS Windows clients may use encrypted passwords as part of a challenege/response @@ -4810,8 +4842,8 @@ CLASS="SECT3" >

    5.1.3.2. Use MS Windows NT as an authentication server6.1.3.2. Use MS Windows NT as an authentication server

    This method involves the additions of the following parameters in the

    5.1.4. Domain Level Security6.1.4. Domain Level Security

    When samba is operating in

    5.1.4.1. Samba as a member of an MS Windows NT security domain6.1.4.1. Samba as a member of an MS Windows NT security domain

    This method involves additon of the following paramters in the

    5.1.5. ADS Level Security6.1.5. ADS Level Security

    For information about the configuration option please refer to the entire section entitled @@ -4957,37 +4989,32 @@ CLASS="CHAPTER" >Chapter 6. Samba as an NT4 or Win2k Primary Domain ControllerChapter 7. Samba as an NT4 or Win2k Primary Domain Controller

    6.1. Prerequisite Reading7.1. Prerequisite Reading

    Before you continue reading in this chapter, please make sure that you are comfortable with configuring basic files services in smb.conf and how to enable and administer password encryption in Samba. Theses two topics are covered in the -smb.conf(5) -manpage.

    smb.conf manpage.

    6.2. Background7.2. Background

    This article outlines the steps necessary for configuring Samba as a PDC. @@ -5133,19 +5160,17 @@ CLASS="SECT1" >

    6.3. Configuring the Samba Domain Controller7.3. Configuring the Samba Domain Controller

    The first step in creating a working Samba PDC is to understand the parameters necessary in smb.conf. Here we attempt to explain the parameters that are covered in - the smb.conf -man page.

    smb.conf man page.

    Here is an example Encrypted passwords must be enabled. For more details on how to do this, refer to ENCRYPTION.htmlthe User Database chapter.

    6.4. Creating Machine Trust Accounts and Joining Clients to the Domain7.4. Creating Machine Trust Accounts and Joining Clients to the Domain

    A machine trust account is a Samba account that is used to @@ -5432,7 +5457,10 @@ CLASS="EMPHASIS" file allows the creation of arbitrary user and machine accounts without requiring that account to be added to the system (/etc/passwd) file. It too requires the specification of the "non unix account range" option - in the [globals] section of the smb.conf file. + in the [globals] section of the smb.conf file.

  • Read the chapter about the User Database +for details.

    A Samba PDC, however, stores each machine trust account in two parts, as follows: @@ -5515,8 +5549,8 @@ CLASS="SECT2" >

    6.4.1. Manual Creation of Machine Trust Accounts7.4.1. Manual Creation of Machine Trust Accounts

    The first step in manually creating a machine trust account is to @@ -5621,12 +5655,12 @@ as shown here:

    root# smbpasswd -a -m machine_name

    where

    6.4.2. "On-the-Fly" Creation of Machine Trust Accounts7.4.2. "On-the-Fly" Creation of Machine Trust Accounts

    The second (and recommended) way of creating machine trust accounts is @@ -5722,8 +5756,8 @@ CLASS="SECT2" >

    6.4.3. Joining the Client to the Domain7.4.3. Joining the Client to the Domain

    The procedure for joining a client to the domain varies with the @@ -5782,759 +5816,663 @@ CLASS="EMPHASIS" (i.e., you must supply a Samba administrative account when prompted).

    6.5. Common Problems and Errors

    • I cannot include a '$' in a machine name.Samba -

      Joining a samba client to a domain is documented in + the Domain Member chapter.

    7.5. Common Problems and Errors

    7.5.1. I cannot include a '$' in a machine name

    A 'machine name' in (typically) A 'machine name' in (typically) /etc/passwd - of the machine name with a '$' appended. FreeBSD (and other BSD - systems?) won't create a user with a '$' in their name. -

    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 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 vipw to edit the entry, adding the '$'. Or create - the whole entry with vipw if you like, make sure you use a - unique User ID ! -

  • 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 trust account. -

    • 7.5.2. 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 trust account.

    This happens if you try to create a machine trust 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: -

    This happens if you try to create a machine trust 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:

    C:\WINNT\> net use * /d -

    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. -

  • The system can not log you on (C000019B).... -

    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.

    • 7.5.3. The system can not log you on (C000019B)....

    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 again or consult your - system administrator" when attempting to logon. -

    This occurs when the domain SID stored in the secrets.tdb database - is changed. The most common cause of a change in domain SID is when - the domain name and/or the server name (netbios name) is changed. - The only way to correct the problem is to restore the original domain - SID or remove the domain client from the domain and rejoin. The domain - SID may be reset using either the smbpasswd or rpcclient utilities. -

  • The machine trust account for this computer either does not - exist or is not accessible. -

    This occurs when the domain SID stored in the secrets.tdb database +is changed. The most common cause of a change in domain SID is when +the domain name and/or the server name (netbios name) is changed. +The only way to correct the problem is to restore the original domain +SID or remove the domain client from the domain and rejoin. The domain +SID may be reset using either the smbpasswd or rpcclient utilities.

    • 7.5.4. The machine trust account for this computer either does not +exist or is not accessible.

    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". What's - wrong? -

    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". What's +wrong?

    This problem is caused by the PDC not having a suitable machine trust account. - If you are using the This problem is caused by the PDC not having a suitable machine trust account. +If you are using the add user script method to create - accounts then this would indicate that it has not worked. Ensure the domain - admin user system is working. -

    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 trust 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 ( i.e. 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. -

  • When I attempt to login to a Samba Domain from a NT4/W2K workstation, - I get a message about my account being disabled. -

    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% -

    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 trust 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 ( i.e. 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.

    • 7.5.5. When I attempt to login to a Samba Domain from a NT4/W2K workstation, +I get a message about my account being disabled.

    At first be ensure to enable the useraccounts with At first be ensure to enable the useraccounts with smbpasswd -e - %user%, this is normally done, when you create an account. -

    In order to work around this problem in 2.2.0, configure the - account control flag in - /etc/pam.d/samba file as follows: - 

    	account required        pam_permit.so
-

    If you want to remain backward compatibility to samba 2.0.x use - pam_permit.so, it's also possible to use - pam_pwdb.so. There are some bugs if you try to - use pam_unix.so, if you need this, be ensure to use - the most recent version of this file. -

    , this is normally done, when you create an account.

    6.6. What other help can I get?7.6. Domain Control for Windows 9x/ME

    There are many sources of information available in the form -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.

    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-3 does this +now in the same way that MS Windows NT/2K.

    • 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 this documentation under the browsing discussions. +It should be noted, that browsing is totally orthogonal to logon support.

      What are some diagnostics tools I can use to debug the domain logon - process and where can I find them? -

      Issues related to the single-logon network model are discussed in this +section. Samba supports domain logons, network logon scripts, and user +profiles for MS Windows for workgroups and MS Windows 9X/ME clients +which are the focus of this section.

      One of the best diagnostic tools for debugging problems is Samba itself. - You can use the -d option for both smbd and nmbd to specify what - 'debug level' at which to run. See the man pages on smbd, nmbd and - smb.conf for more information on debugging options. The debug - level can range from 1 (the default) to 10 (100 for debugging passwords). -

      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, i.e. 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 helpful method of debugging is to compile samba using the - gcc -g flag. This will include debug - information in the binaries and allow you to attach gdb to the - running smbd / nmbd process. In order to attach gdb to an smbd - process for an NT workstation, first get the workstation to make the - connection. Pressing ctrl-alt-delete and going down to the domain box - is sufficient (at least, on the first time you join the domain) to - generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation - maintains an open connection, and therefore there will be an smbd - process running (assuming that you haven't set a really short smbd - idle timeout) So, in between pressing ctrl alt delete, and actually - typing in your password, you can gdb attach and continue. -

      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.

      Some useful samba commands worth investigating: -

      Before launching into the configuration instructions, it is +worthwhile lookingat how a Windows 9x/ME client performs a logon:

        1. testparam | more

          The client broadcasts (to the IP broadcast address of the subnet it is in) + a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> 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. +

        2. smbclient -L //{netbios name of server}

          The client then connects to that server, logs on (does an SMBsessetupX) and + then connects to the IPC$ share (using an SMBtconX). +

    • An SMB enabled version of tcpdump is available from - http://www.tcpdup.org/. - Ethereal, another good packet sniffer for Unix and Win32 - hosts, can be downloaded from http://www.ethereal.com. +> The client then does a NetWkstaUserLogon request, which retrieves the name + of the user's logon script.

    • For tracing things on the Microsoft Windows NT, Network Monitor - (aka. netmon) is available on the Microsoft Developer Network CD's, - the Windows NT Server install CD and the SMS CD's. The version of - netmon that ships with SMS allows for dumping packets between any two - computers (i.e. placing the network interface in promiscuous mode). - The version on the NT Server install CD will only allow monitoring - of network traffic directed to the local NT box and broadcasts on the - local subnet. Be aware that Ethereal can read and write netmon - formatted files. +> 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.

    • How do I install 'Network Monitor' on an NT Workstation - or a Windows 9x box? +> 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.

    • Installing netmon on an NT workstation requires a couple - of steps. The following are for installing Netmon V4.00.349, which comes - with Microsoft Windows NT Server 4.0, on Microsoft Windows NT - Workstation 4.0. The process should be similar for other version of - Windows NT / Netmon. You will need both the Microsoft Windows - NT Server 4.0 Install CD and the Workstation 4.0 Install CD. +> 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 user's home share as + a sharename and path. For example, \\server\fred\.profile. + If the profiles are found, they are implemented.

    • Initially you will need to install 'Network Monitor Tools and Agent' - on the NT Server. To do this +> 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.

      • 7.6.1. Configuration Instructions: Network Logons

      The main difference between a PDC and a Windows 9x logon +server configuration is that

      • Goto Start - Settings - Control Panel - - Network - Services - Add

        Password encryption is not required for a Windows 9x logon server.

      • Select the 'Network Monitor Tools and Agent' and - click on 'OK'.

      • Click 'OK' on the Network Control Panel. -

      • Insert the Windows NT Server 4.0 install CD - when prompted.

        Windows 9x/ME clients do not possess machine trust accounts.

      At this point the Netmon files should exist in - %SYSTEMROOT%\System32\netmon\*.*. - Two subdirectories exist as well, parsers\ - which contains the necessary DLL's for parsing the netmon packet - dump, and captures\. -

      In order to install the Netmon tools on an NT Workstation, you will - first need to install the 'Network Monitor Agent' from the Workstation - install CD. -

      Therefore, a Samba PDC will also act as a Windows 9x logon +server.

      • Goto Start - Settings - Control Panel - - Network - Services - Add

      • Select the 'Network Monitor Agent' and click - on 'OK'.

      • Click 'OK' on the Network Control Panel. -

      • Insert the Windows NT Workstation 4.0 install - CD when prompted.

      security mode and master browsers
       

      Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* - to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set - permissions as you deem appropriate for your site. You will need - administrative rights on the NT box to run netmon. -

      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 USER. The only security mode +which will not work due to technical reasons is SHARE +mode security. DOMAIN and SERVER +mode security is really just a variation on SMB user level security.

      To install Netmon on a Windows 9x box install the network monitor agent - from the Windows 9x CD (\admin\nettools\netmon). There is a readme - file located with the netmon driver files on the CD if you need - information on how to do this. Copy the files from a working - Netmon installation. -

    • Actually, this issue is also closely 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.

      The following is a list if helpful URLs and other links: -

      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?)

      • 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.

    Chapter 8. Samba Backup Domain Controller to Samba Domain Control

    8.1. Prerequisite Reading

    Home of Samba site Before you continue reading in this chapter, please make sure +that you are comfortable with configuring a Samba PDC +as described in the http://samba.org. We have a mirror near you !

  • The Development document - on the Samba mirrors might mention your problem. If so, - it might mean that the developers are working on it.

  • Samba-PDC-HOWTO.

    • 8.2. Background

    See how Scott Merrill simulates a BDC behavior at - http://www.skippy.net/linux/smb-howto.html.

  • What is a Domain Controller? It is a machine that is able to answer +logon requests from workstations in a Windows NT Domain. Whenever a +user logs into a Windows NT Workstation, the workstation connects to a +Domain Controller and asks him whether the username and password the +user typed in is correct. The Domain Controller replies with a lot of +information about the user, for example the place where the users +profile is stored, the users full name of the user. All this +information is stored in the NT user database, the so-called SAM.

    Although 2.0.7 has almost had its day as a PDC, David Bannon will - keep the 2.0.7 PDC pages at http://bioserve.latrobe.edu.au/samba going for a while yet.

  • There are two kinds of Domain Controller in a NT 4 compatible Domain: +A Primary Domain Controller (PDC) and one or more Backup Domain +Controllers (BDC). The PDC contains the master copy of the +SAM. Whenever the SAM has to change, for example when a user changes +his password, this change has to be done on the PDC. A Backup Domain +Controller is a machine that maintains a read-only copy of the +SAM. This way it is able to reply to logon requests and authenticate +users in case the PDC is not available. During this time no changes to +the SAM are possible. Whenever changes to the SAM are done on the PDC, +all BDC receive the changes from the PDC.

    Misc links to CIFS information - http://samba.org/cifs/

  • Since version 2.2 Samba officially supports domain logons for all +current Windows Clients, including Windows 2000 and XP. This text +assumes the domain to be named SAMBA. To be able to act as a PDC, some +parameters in the [global]-section of the smb.conf have to be set:

    NT Domains for Unix http://mailhost.cb1.com/~lkcl/ntdom/

    workgroup = SAMBA
+domain master = yes
+domain logons = yes

  • FTP site for older SMB specs: - ftp://ftp.microsoft.com/developr/drg/CIFS/

    • Several other things like a [homes] and a [netlogon] share also may be +set along with settings for the profile path, the users home drive and +others. This will not be covered in this document.

    8.3. What qualifies a Domain Controller on the network?

    • Every machine that is a Domain Controller for the domain SAMBA has to +register the NetBIOS group name SAMBA#1c with the WINS server and/or +by broadcast on the local network. The PDC also registers the unique +NetBIOS name SAMBA#1b with the WINS server. The name type #1b is +normally reserved for the domain master browser, a role that has +nothing to do with anything related to authentication, but the +Microsoft Domain implementation requires the domain master browser to +be on the same machine as the PDC.

      8.3.1. How does a Workstation find its domain controller?

      How do I get help from the mailing lists? -

      A NT workstation in the domain SAMBA that wants a local user to be +authenticated has to find the domain controller for SAMBA. It does +this by doing a NetBIOS name query for the group name SAMBA#1c. It +assumes that each of the machines it gets back from the queries is a +domain controller and can answer logon requests. To not open security +holes both the workstation and the selected (TODO: How is the DC +chosen) domain controller authenticate each other. After that the +workstation sends the user's credentials (his name and password) to +the domain controller, asking for approval.

      8.3.2. When is the PDC needed?

      There are a number of Samba related mailing lists. Go to http://samba.org, click on your nearest mirror - and then click on Support and then click on Samba related mailing lists. -

      Whenever a user wants to change his password, this has to be done on +the PDC. To find the PDC, the workstation does a NetBIOS name query +for SAMBA#1b, assuming this machine maintains the master copy of the +SAM. The workstation contacts the PDC, both mutually authenticate and +the password change is done.

    8.4. Can Samba be a Backup Domain Controller to an NT PDC?

    For questions relating to Samba TNG go to - http://www.samba-tng.org/ - It has been requested that you don't post questions about Samba-TNG to the - main stream Samba lists.

    With version 2.2, no. The native NT SAM replication protocols have +not yet been fully implemented. The Samba Team is working on +understanding and implementing the protocols, but this work has not +been finished for version 2.2.

    If you post a message to one of the lists please observe the following guide lines : -

    With version 3.0, the work on both the replication protocols and a +suitable storage mechanism has progressed, and some form of NT4 BDC +support is expected soon.

    Can I get the benefits of a BDC with Samba? Yes. The main reason for +implementing a BDC is availability. If the PDC is a Samba machine, +a second Samba machine can be set up to +service logon requests whenever the PDC is down.

    8.5. How do I set up a Samba BDC?

    Several things have to be done:

    • Always remember that the developers are volunteers, they are - not paid and they never guarantee to produce a particular feature at - a particular time. Any time lines are 'best guess' and nothing more. -

    • Always mention what version of samba you are using and what - operating system its running under. You should probably list the - relevant sections of your smb.conf file, at least the options - in [global] that affect PDC support.

    • The domain SID has to be the same on the PDC and the BDC. This used to +be stored in the file private/MACHINE.SID. This file is not created +anymore since Samba 2.2.5 or even earlier. Nowadays the domain SID is +stored in the file private/secrets.tdb. Simply copying the secrets.tdb +from the PDC to the BDC does not work, as the BDC would +generate a new SID for itself and override the domain SID with this +new BDC SID.

      In addition to the version, if you obtained Samba via - CVS mention the date when you last checked it out.

      To retrieve the domain SID from the PDC or an existing BDC and store it in the +secrets.tdb, execute 'net rpc getsid' on the BDC.

    • Try and make your question clear and brief, lots of long, - convoluted questions get deleted before they are completely read ! - Don't post html encoded messages (if you can select colour or font - size its html).

      The Unix user database has to be synchronized from the PDC to the +BDC. This means that both the /etc/passwd and /etc/group have to be +replicated from the PDC to the BDC. This can be done manually +whenever changes are made, or the PDC is set up as a NIS master +server and the BDC as a NIS slave server. To set up the BDC as a +mere NIS client would not be enough, as the BDC would not be able to +access its user database in case of a PDC failure.

    • If you run one of those nifty 'I'm on holidays' things when - you are away, make sure its configured to not answer mailing lists. -

      The Samba password database in the file private/smbpasswd has to be +replicated from the PDC to the BDC. This is a bit tricky, see the +next section.

    • Don't cross post. Work out which is the best list to post to - and see what happens, i.e. don't post to both samba-ntdom and samba-technical. - Many people active on the lists subscribe to more - than one list and get annoyed to see the same message two or more times. - Often someone will see a message and thinking it would be better dealt - with on another, will forward it on for you.

      Any netlogon share has to be replicated from the PDC to the +BDC. This can be done manually whenever login scripts are changed, +or it can be done automatically together with the smbpasswd +synchronization.

    You might include partial - log files written at a debug level set to as much as 20. - Please don't send the entire log but enough to give the context of the - error messages.

  • Finally, the BDC has to be found by the workstations. This can be done +by setting

    (Possibly) If you have a complete netmon trace ( from the opening of - the pipe to the error ) you can send the *.CAP file as well.

  • workgroup = samba
+domain master = no
+domain logons = yes

    Please think carefully before attaching a document to an email. - Consider pasting the relevant parts into the body of the message. The samba - mailing lists go to a huge number of people, do they all need a copy of your - smb.conf in their attach directory?

  • in the [global]-section of the smb.conf of the BDC. This makes the BDC +only register the name SAMBA#1c with the WINS server. This is no +problem as the name SAMBA#1c is a NetBIOS group name that is meant to +be registered by more than one machine. The parameter 'domain master = +no' forces the BDC not to register SAMBA#1b which as a unique NetBIOS +name is reserved for the Primary Domain Controller.

    8.5.1. How do I replicate the smbpasswd file?

    How do I get off the mailing lists? -

    Replication of the smbpasswd file is sensitive. It has to be done +whenever changes to the SAM are made. Every user's password change is +done in the smbpasswd file and has to be replicated to the BDC. So +replicating the smbpasswd file very often is necessary.

    To have your name removed from a samba mailing list, go to the - same place you went to to get on it. Go to http://lists.samba.org, - click on your nearest mirror and then click on Support and - then click on Samba related mailing lists. Or perhaps see - here -

    As the smbpasswd file contains plain text password equivalents, it +must not be sent unencrypted over the wire. The best way to set up +smbpasswd replication from the PDC to the BDC is to use the utility +rsync. rsync can use ssh as a transport. ssh itself can be set up to +accept *only* rsync transfer without requiring the user to type a +password.

    8.5.2. Can I do this all with LDAP?

    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...) -

    • The simple answer is YES. Samba's pdb_ldap code supports +binding to a replica LDAP server, and will also follow referrals and +rebind to the master if it ever needs to make a modification to the +database. (Normally BDCs are read only, so this will not occur +often).

    Chapter 9. Samba as a ADS domain member

    This is a rough guide to setting up Samba 3.0 with kerberos authentication against a +Windows2000 KDC.

    6.7. Domain Control for Windows 9x/ME9.1. Setup your smb.conf

    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-3 does this -now in the same way that MS Windows NT/2K.

    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 this documentation under the browsing discussions. -It should be noted, that browsing is totally orthogonal to logon support.

    Issues related to the single-logon network model are discussed in this -section. Samba supports domain logons, network logon scripts, and user -profiles for MS Windows for workgroups and MS Windows 9X/ME clients -which are the focus of this section.

    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, i.e. 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.

    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.

    Before launching into the configuration instructions, it is -worthwhile lookingat how a Windows 9x/ME client performs a logon:

    You must use at least the following 3 options in smb.conf:

      realm = YOUR.KERBEROS.REALM
+  security = ADS
+  encrypt passwords = yes

    1. The client broadcasts (to the IP broadcast address of the subnet it is in) - a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> 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. -

    2. The client then connects to that server, logs on (does an SMBsessetupX) and - then connects to the IPC$ share (using an SMBtconX). -

    3. The client then does a NetWkstaUserLogon request, which retrieves the name - of the user's logon script. -

    4. 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. -

    5. 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. -

    6. 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 user's home share as - a sharename and path. For example, \\server\fred\.profile. - If the profiles are found, they are implemented. -

    7. 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. -

    6.7.1. Configuration Instructions: Network Logons

    The main difference between a PDC and a Windows 9x logon -server configuration is that

    In case samba can't figure out your ads server using your realm name, use the +ads server option in smb.conf: +

      ads server = your.kerberos.server

    • Password encryption is not required for a Windows 9x logon server.

    • Windows 9x/ME clients do not possess machine trust accounts.

    Therefore, a Samba PDC will also act as a Windows 9x logon -server.

    security mode and master browsers
     

    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 USER. The only security mode -which will not work due to technical reasons is SHARE -mode security. DOMAIN and SERVER -mode security is really just a variation on SMB user level security.

    Actually, this issue is also closely 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.

    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?)

    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.

    You do *not* need a smbpasswd file, and older clients will + be authenticated as if security = domain, + although it won't do any harm + and allows you to have local users not in the domain. + I expect that the above required options will change soon when we get better + active directory integration.

    Chapter 7. Samba Backup Domain Controller to Samba Domain Control

    7.1. Prerequisite Reading

    Before you continue reading in this chapter, please make sure -that you are comfortable with configuring a Samba PDC -as described in the Samba-PDC-HOWTO.

    7.2. Background9.2. Setup your /etc/krb5.conf

    What is a Domain Controller? It is a machine that is able to answer -logon requests from workstations in a Windows NT Domain. Whenever a -user logs into a Windows NT Workstation, the workstation connects to a -Domain Controller and asks him whether the username and password the -user typed in is correct. The Domain Controller replies with a lot of -information about the user, for example the place where the users -profile is stored, the users full name of the user. All this -information is stored in the NT user database, the so-called SAM.

    There are two kinds of Domain Controller in a NT 4 compatible Domain: -A Primary Domain Controller (PDC) and one or more Backup Domain -Controllers (BDC). The PDC contains the master copy of the -SAM. Whenever the SAM has to change, for example when a user changes -his password, this change has to be done on the PDC. A Backup Domain -Controller is a machine that maintains a read-only copy of the -SAM. This way it is able to reply to logon requests and authenticate -users in case the PDC is not available. During this time no changes to -the SAM are possible. Whenever changes to the SAM are done on the PDC, -all BDC receive the changes from the PDC.

    Since version 2.2 Samba officially supports domain logons for all -current Windows Clients, including Windows 2000 and XP. This text -assumes the domain to be named SAMBA. To be able to act as a PDC, some -parameters in the [global]-section of the smb.conf have to be set:

    The minimal configuration for krb5.conf is:

    workgroup = SAMBA
-domain master = yes
-domain logons = yes
    [realms] + YOUR.KERBEROS.REALM = { + kdc = your.kerberos.server + }

    Several other things like a [homes] and a [netlogon] share also may be -set along with settings for the profile path, the users home drive and -others. This will not be covered in this document.

    7.3. What qualifies a Domain Controller on the network?

    Every machine that is a Domain Controller for the domain SAMBA has to -register the NetBIOS group name SAMBA#1c with the WINS server and/or -by broadcast on the local network. The PDC also registers the unique -NetBIOS name SAMBA#1b with the WINS server. The name type #1b is -normally reserved for the domain master browser, a role that has -nothing to do with anything related to authentication, but the -Microsoft Domain implementation requires the domain master browser to -be on the same machine as the PDC.

    Test your config by doing a kinit USERNAME@REALM and making sure that + your password is accepted by the Win2000 KDC.

    7.3.1. How does a Workstation find its domain controller?

    A NT workstation in the domain SAMBA that wants a local user to be -authenticated has to find the domain controller for SAMBA. It does -this by doing a NetBIOS name query for the group name SAMBA#1c. It -assumes that each of the machines it gets back from the queries is a -domain controller and can answer logon requests. To not open security -holes both the workstation and the selected (TODO: How is the DC -chosen) domain controller authenticate each other. After that the -workstation sends the user's credentials (his name and password) to -the domain controller, asking for approval.

    7.3.2. When is the PDC needed?

    Whenever a user wants to change his password, this has to be done on -the PDC. To find the PDC, the workstation does a NetBIOS name query -for SAMBA#1b, assuming this machine maintains the master copy of the -SAM. The workstation contacts the PDC, both mutually authenticate and -the password change is done.

    7.4. Can Samba be a Backup Domain Controller to an NT PDC?

    With version 2.2, no. The native NT SAM replication protocols have -not yet been fully implemented. The Samba Team is working on -understanding and implementing the protocols, but this work has not -been finished for version 2.2.

    With version 3.0, the work on both the replication protocols and a -suitable storage mechanism has progressed, and some form of NT4 BDC -support is expected soon.

    Can I get the benefits of a BDC with Samba? Yes. The main reason for -implementing a BDC is availability. If the PDC is a Samba machine, -a second Samba machine can be set up to -service logon requests whenever the PDC is down.

    7.5. How do I set up a Samba BDC?

    Several things have to be done:

    • The domain SID has to be the same on the PDC and the BDC. This used to -be stored in the file private/MACHINE.SID. This file is not created -anymore since Samba 2.2.5 or even earlier. Nowadays the domain SID is -stored in the file private/secrets.tdb. Simply copying the secrets.tdb -from the PDC to the BDC does not work, as the BDC would -generate a new SID for itself and override the domain SID with this -new BDC SID.

      To retrieve the domain SID from the PDC or an existing BDC and store it in the -secrets.tdb, execute 'net rpc getsid' on the BDC.

    • The Unix user database has to be synchronized from the PDC to the -BDC. This means that both the /etc/passwd and /etc/group have to be -replicated from the PDC to the BDC. This can be done manually -whenever changes are made, or the PDC is set up as a NIS master -server and the BDC as a NIS slave server. To set up the BDC as a -mere NIS client would not be enough, as the BDC would not be able to -access its user database in case of a PDC failure.

    • The Samba password database in the file private/smbpasswd has to be -replicated from the PDC to the BDC. This is a bit tricky, see the -next section.

    • Any netlogon share has to be replicated from the PDC to the -BDC. This can be done manually whenever login scripts are changed, -or it can be done automatically together with the smbpasswd -synchronization.

    Finally, the BDC has to be found by the workstations. This can be done -by setting

    workgroup = samba
-domain master = no
-domain logons = yes

    in the [global]-section of the smb.conf of the BDC. This makes the BDC -only register the name SAMBA#1c with the WINS server. This is no -problem as the name SAMBA#1c is a NetBIOS group name that is meant to -be registered by more than one machine. The parameter 'domain master = -no' forces the BDC not to register SAMBA#1b which as a unique NetBIOS -name is reserved for the Primary Domain Controller.

    7.5.1. How do I replicate the smbpasswd file?

    Replication of the smbpasswd file is sensitive. It has to be done -whenever changes to the SAM are made. Every user's password change is -done in the smbpasswd file and has to be replicated to the BDC. So -replicating the smbpasswd file very often is necessary.

    As the smbpasswd file contains plain text password equivalents, it -must not be sent unencrypted over the wire. The best way to set up -smbpasswd replication from the PDC to the BDC is to use the utility -rsync. rsync can use ssh as a transport. ssh itself can be set up to -accept *only* rsync transfer without requiring the user to type a -password.

    7.5.2. Can I do this all with LDAP?

    The simple answer is YES. Samba's pdb_ldap code supports -binding to a replica LDAP server, and will also follow referrals and -rebind to the master if it ever needs to make a modification to the -database. (Normally BDCs are read only, so this will not occur -often).

    Chapter 8. Samba as a ADS domain member

    This is a rough guide to setting up Samba 3.0 with kerberos authentication against a -Windows2000 KDC.

    8.1. Setup your smb.conf

    You must use at least the following 3 options in smb.conf:

      realm = YOUR.KERBEROS.REALM
-  security = ADS
-  encrypt passwords = yes

    In case samba can't figure out your ads server using your realm name, use the -ads server option in smb.conf: -

      ads server = your.kerberos.server

    You do *not* need a smbpasswd file, and older clients will - be authenticated as if security = domain, - although it won't do any harm - and allows you to have local users not in the domain. - I expect that the above required options will change soon when we get better - active directory integration.

    8.2. Setup your /etc/krb5.conf

    The minimal configuration for krb5.conf is:

    [realms]
-    YOUR.KERBEROS.REALM = {
-	kdc = your.kerberos.server
-    }

    Test your config by doing a kinit USERNAME@REALM and making sure that - your password is accepted by the Win2000 KDC.

    8.3. Create the computer account9.3. Create the computer account

    As a user that has write permission on the Samba private directory @@ -7063,8 +6627,8 @@ CLASS="SECT2" >

    8.3.1. Possible errors9.3.1. Possible errors

    8.4. Test your server setup9.4. Test your server setup

    On a Windows 2000 client try 8.5. Testing with 9.5. Testing with smbclient

    8.6. Notes9.6. Notes

    You must change administrator password at least once after DC @@ -7148,16 +6712,16 @@ install, to create the right encoding types

    Chapter 9. Samba as a NT4 or Win2k domain member

    Chapter 10. Samba as a NT4 or Win2k domain member

    9.1. Joining an NT Domain with Samba 3.010.1. Joining an NT Domain with Samba 3.0

    Assume you have a Samba 3.0 server with a NetBIOS name of @@ -7338,8 +6902,8 @@ CLASS="SECT1" >

    9.2. Why is this better than security = server?10.2. Why is this better than security = server?

    Currently, domain security in Samba doesn't free you from @@ -7447,10 +7011,11 @@ CLASS="TITLEPAGE" >

    III. Advanced Configuration

    Introduction

    Samba has several features that you might want or might not want to use. The chapters in this part each cover one specific feature.

    Table of Contents
    10. UNIX Permission Bits and Windows NT Access Control Lists
    10.1. Viewing and changing UNIX permissions using the NT - security dialogs
    10.2. How to view file security on a Samba share
    10.3. Viewing file ownership
    10.4. Viewing file or directory permissions
    10.4.1. File Permissions
    10.4.2. Directory Permissions
    10.5. Modifying file or directory permissions
    10.6. Interaction with the standard Samba create mask - parameters
    10.7. Interaction with the standard Samba file attribute - mapping
    11. Configuring Group Mapping
    12. Printing Support
    12.1. Introduction
    12.2. Configuration
    12.2.1. Creating [print$]
    12.2.2. Setting Drivers for Existing Printers
    12.2.3. Support a large number of printers
    12.2.4. Adding New Printers via the Windows NT APW
    12.2.5. Samba and Printer Ports
    12.3. The Imprints Toolset
    12.3.1. What is Imprints?
    12.3.2. Creating Printer Driver Packages
    12.3.3. The Imprints server
    12.3.4. The Installation Client
    12.4. Diagnosis
    12.4.1. Introduction
    12.4.2. Debugging printer problems
    12.4.3. What printers do I have?
    12.4.4. Setting up printcap and print servers
    12.4.5. Job sent, no output
    12.4.6. Job sent, strange output
    12.4.7. Raw PostScript printed
    12.4.8. Advanced Printing
    12.4.9. Real debugging
    13. CUPS Printing Support
    13.1. Introduction
    13.2. Configuring smb.conf for CUPS
    13.3. CUPS - RAW Print Through Mode
    13.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe -PostScript driver with CUPS-PPDs downloaded to clients
    13.5. Windows Terminal Servers (WTS) as CUPS clients
    13.6. Setting up CUPS for driver download
    13.7. Sources of CUPS drivers / PPDs
    13.7.1. cupsaddsmb

    13.8. The CUPS Filter Chains
    13.9. CUPS Print Drivers and Devices
    13.9.1. Further printing steps
    13.10. Limiting the number of pages users can print
    13.11. Advanced Postscript Printing from MS Windows
    13.12. Auto-Deletion of CUPS spool files
    14. Unified Logons between Windows NT and UNIX using Winbind
    14.1. Abstract
    14.2. Introduction
    14.3. What Winbind Provides
    14.3.1. Target Uses
    14.4. How Winbind Works
    14.4.1. Microsoft Remote Procedure Calls
    14.4.2. Microsoft Active Directory Services
    14.4.3. Name Service Switch
    14.4.4. Pluggable Authentication Modules
    14.4.5. User and Group ID Allocation
    14.4.6. Result Caching
    14.5. Installation and Configuration
    14.5.1. Introduction
    14.5.2. Requirements
    14.5.3. Testing Things Out
    14.6. Limitations
    14.7. Conclusion
    15. Advanced Network Manangement
    15.1. Configuring Samba Share Access Controls
    15.1.1. Share Permissions Management
    15.2. Remote Server Administration
    15.3. Network Logon Script Magic
    16. System and Account Policies
    16.1. Creating and Managing System Policies
    16.1.1. Windows 9x/Me Policies
    16.1.2. Windows NT4 Style Policy Files
    16.1.3. MS Windows 200x / XP Professional Policies
    16.2. Managing Account/User Policies
    16.2.1. With Windows NT4/200x
    16.2.2. With a Samba PDC
    17. Desktop Profile Management
    17.1. Roaming Profiles
    17.1.1. Samba Configuration for Profile Handling
    17.1.2. Windows Client Profile Configuration Information
    17.1.3. Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    17.1.4. Profile Migration from Windows NT4/200x Server to Samba
    17.2. Mandatory profiles
    17.3. Creating/Managing Group Profiles
    17.4. Default Profile for Windows Users
    17.4.1. MS Windows 9x/Me
    17.4.2. MS Windows NT4 Workstation
    17.4.3. MS Windows 200x/XP
    18. Interdomain Trust Relationships
    18.1. Trust Relationship Background
    18.2. MS Windows NT4 Trust Configuration
    18.2.1. NT4 as the Trusting Domain
    18.2.2. NT4 as the Trusted Domain
    18.3. Configuring Samba Domain Trusts
    18.3.1. Samba3 as the Trusting Domain
    18.3.2. Samba3 as the Trusted Domain
    19. PAM Configuration for Centrally Managed Authentication
    19.1. Samba and PAM
    19.2. Distributed Authentication
    19.3. PAM Configuration in smb.conf
    20. Stackable VFS modules
    20.1. Introduction and configuration
    20.2. Included modules
    20.2.1. audit
    20.2.2. extd_audit
    20.2.3. recycle
    20.2.4. netatalk
    20.3. VFS modules available elsewhere
    20.3.1. DatabaseFS
    20.3.2. vscan
    21. Hosting a Microsoft Distributed File System tree on Samba
    21.1. Instructions
    21.1.1. Notes
    22. Integrating MS Windows networks with Samba
    22.1. Name Resolution in a pure Unix/Linux world
    22.1.1. /etc/hosts
    22.1.2. /etc/resolv.conf
    22.1.3. /etc/host.conf
    22.1.4. /etc/nsswitch.conf
    22.2. Name resolution as used within MS Windows networking
    22.2.1. The NetBIOS Name Cache
    22.2.2. The LMHOSTS file
    22.2.3. HOSTS file
    22.2.4. DNS Lookup
    22.2.5. WINS Lookup
    23. Improved browsing in samba
    23.1. Overview of browsing
    23.2. Browsing support in samba
    23.3. Problem resolution
    23.4. Browsing across subnets
    23.4.1. How does cross subnet browsing work ?
    23.5. Setting up a WINS server
    23.6. Setting up Browsing in a WORKGROUP
    23.7. Setting up Browsing in a DOMAIN
    23.8. Forcing samba to be the master
    23.9. Making samba the domain master
    23.10. Note about broadcast addresses
    23.11. Multiple interfaces
    24. Securing Samba
    24.1. Introduction
    24.2. Using host based protection
    24.3. Using interface protection
    24.4. Using a firewall
    24.5. Using a IPC$ share deny
    24.6. Upgrading Samba
    25. Unicode/Charsets
    25.1. What are charsets and unicode?
    25.2. Samba and charsets

    Chapter 10. UNIX Permission Bits and Windows NT Access Control Lists

    10.1. Viewing and changing UNIX permissions using the NT - security dialogs

    Windows NT clients can use their native security settings - dialog box to view and modify the underlying UNIX permissions.

    Note that this ability is careful not to compromise - the security of the UNIX host Samba is running on, and - still obeys all the file permission rules that a Samba - administrator can set.

    All access to Unix/Linux system file via Samba is controlled at - the operating system file access control level. When trying to - figure out file access problems it is vitally important to identify - the identity of the Windows user as it is presented by Samba at - the point of file access. This can best be determined from the - Samba log files. -

    10.2. How to view file security on a Samba share

    From an NT4/2000/XP client, single-click with the right - mouse button on any file or directory in a Samba mounted - drive letter or UNC path. When the menu pops-up, click - on the Properties entry at the bottom of - the menu. This brings up the file properties dialog - box. Click on the tab Security and you - will see three buttons, Permissions, - Auditing, and Ownership. - The Auditing button will cause either - an error message A requested privilege is not held - by the client to appear if the user is not the - NT Administrator, or a dialog which is intended to allow an - Administrator to add auditing requirements to a file if the - user is logged on as the NT Administrator. This dialog is - non-functional with a Samba share at this time, as the only - useful button, the Add button will not currently - allow a list of users to be seen.

    10.3. Viewing file ownership

    Clicking on the "Ownership" button - brings up a dialog box telling you who owns the given file. The - owner name will be of the form :

    "SERVER\user (Long name)"

    Where SERVER is the NetBIOS name of - the Samba server, user is the user name of - the UNIX user who owns the file, and (Long name) - is the descriptive string identifying the user (normally found in the - GECOS field of the UNIX password database). Click on the Close - button to remove this dialog.

    If the parameter nt acl support - is set to false then the file owner will - be shown as the NT user "Everyone".

    The Take Ownership button will not allow - you to change the ownership of this file to yourself (clicking on - it will display a dialog box complaining that the user you are - currently logged onto the NT client cannot be found). The reason - for this is that changing the ownership of a file is a privileged - operation in UNIX, available only to the root - user. As clicking on this button causes NT to attempt to change - the ownership of a file to the current user logged into the NT - client this will not work with Samba at this time.

    There is an NT chown command that will work with Samba - and allow a user with Administrator privilege connected - to a Samba server as root to change the ownership of - files on both a local NTFS filesystem or remote mounted NTFS - or Samba drive. This is available as part of the Seclib - NT security library written by Jeremy Allison of - the Samba Team, available from the main Samba ftp site.

    10.4. Viewing file or directory permissions

    The third button is the "Permissions" - button. Clicking on this brings up a dialog box that shows both - the permissions and the UNIX owner of the file or directory. - The owner is displayed in the form :

    "SERVER\user (Long name)"

    Where SERVER is the NetBIOS name of - the Samba server, user is the user name of - the UNIX user who owns the file, and (Long name) - is the descriptive string identifying the user (normally found in the - GECOS field of the UNIX password database).

    If the parameter nt acl support - is set to false then the file owner will - be shown as the NT user "Everyone" and the - permissions will be shown as NT "Full Control".

    The permissions field is displayed differently for files - and directories, so I'll describe the way file permissions - are displayed first.

    10.4.1. File Permissions

    The standard UNIX user/group/world triple and - the corresponding "read", "write", "execute" permissions - triples are mapped by Samba into a three element NT ACL - with the 'r', 'w', and 'x' bits mapped into the corresponding - NT permissions. The UNIX world permissions are mapped into - the global NT group Everyone, followed - by the list of permissions allowed for UNIX world. The UNIX - owner and group permissions are displayed as an NT - user icon and an NT local - group icon respectively followed by the list - of permissions allowed for the UNIX user and group.

    As many UNIX permission sets don't map into common - NT names such as "read", "change" or "full control" then - usually the permissions will be prefixed by the words "Special Access" in the NT display list.

    But what happens if the file has no permissions allowed - for a particular UNIX user group or world component ? In order - to allow "no permissions" to be seen and modified then Samba - overloads the NT "Take Ownership" ACL attribute - (which has no meaning in UNIX) and reports a component with - no permissions as having the NT "O" bit set. - This was chosen of course to make it look like a zero, meaning - zero permissions. More details on the decision behind this will - be given below.

    10.4.2. Directory Permissions

    Directories on an NT NTFS file system have two - different sets of permissions. The first set of permissions - is the ACL set on the directory itself, this is usually displayed - in the first set of parentheses in the normal "RW" - NT style. This first set of permissions is created by Samba in - exactly the same way as normal file permissions are, described - above, and is displayed in the same way.

    The second set of directory permissions has no real meaning - in the UNIX permissions world and represents the "inherited" permissions that any file created within - this directory would inherit.

    Samba synthesises these inherited permissions for NT by - returning as an NT ACL the UNIX permission mode that a new file - created by Samba on this share would receive.

    10.5. Modifying file or directory permissions

    Modifying file and directory permissions is as simple - as changing the displayed permissions in the dialog box, and - clicking the OK button. However, there are - limitations that a user needs to be aware of, and also interactions - with the standard Samba permission masks and mapping of DOS - attributes that need to also be taken into account.

    If the parameter nt acl support - is set to false then any attempt to set - security permissions will fail with an "Access Denied" - message.

    The first thing to note is that the "Add" - button will not return a list of users in Samba (it will give - an error message of "The remote procedure call failed - and did not execute"). This means that you can only - manipulate the current user/group/world permissions listed in - the dialog box. This actually works quite well as these are the - only permissions that UNIX actually has.

    If a permission triple (either user, group, or world) - is removed from the list of permissions in the NT dialog box, - then when the "OK" button is pressed it will - be applied as "no permissions" on the UNIX side. If you then - view the permissions again the "no permissions" entry will appear - as the NT "O" flag, as described above. This - allows you to add permissions back to a file or directory once - you have removed them from a triple component.

    As UNIX supports only the "r", "w" and "x" bits of - an NT ACL then if other NT security attributes such as "Delete - access" are selected then they will be ignored when applied on - the Samba server.

    When setting permissions on a directory the second - set of permissions (in the second set of parentheses) is - by default applied to all files within that directory. If this - is not what you want you must uncheck the "Replace - permissions on existing files" checkbox in the NT - dialog before clicking "OK".

    If you wish to remove all permissions from a - user/group/world component then you may either highlight the - component and click the "Remove" button, - or set the component to only have the special "Take - Ownership" permission (displayed as "O" - ) highlighted.

    10.6. Interaction with the standard Samba create mask - parameters

    There are four parameters - to control interaction with the standard Samba create mask parameters. - These are :

    security mask

    force security mode

    directory security mask

    force directory security mode

    Once a user clicks "OK" to apply the - permissions Samba maps the given permissions into a user/group/world - r/w/x triple set, and then will check the changed permissions for a - file against the bits set in the - security mask parameter. Any bits that - were changed that are not set to '1' in this parameter are left alone - in the file permissions.

    Essentially, zero bits in the security mask - mask may be treated as a set of bits the user is not - allowed to change, and one bits are those the user is allowed to change. -

    If not set explicitly this parameter is set to the same value as - the create mask - parameter. To allow a user to modify all the - user/group/world permissions on a file, set this parameter - to 0777.

    Next Samba checks the changed permissions for a file against - the bits set in the force security mode parameter. Any bits - that were changed that correspond to bits set to '1' in this parameter - are forced to be set.

    Essentially, bits set in the force security mode - parameter 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 force - create mode parameter. - To allow a user to modify all the user/group/world permissions on a file - with no restrictions set this parameter to 000.

    The security mask and force - security mode parameters are applied to the change - request in that order.

    For a directory Samba will perform the same operations as - described above for a file except using the parameter directory security mask instead of security - mask, and force directory security mode - parameter instead of force security mode - .

    The directory security mask parameter - by default is set to the same value as the directory mask - parameter and the force directory security - mode parameter by default is set to the same value as - the force directory mode parameter.

    In this way Samba enforces the permission restrictions that - an administrator can set on a Samba share, whilst still allowing users - to modify the permission bits within that restriction.

    If you want to set up a share that allows users full control - in modifying the permission bits on their files and directories and - doesn't force any particular bits to be set 'on', then set the following - parameters in the smb.conf file in that share specific section :

    security mask = 0777

    force security mode = 0

    directory security mask = 0777

    force directory security mode = 0

    10.7. Interaction with the standard Samba file attribute - mapping

    Samba maps some of the DOS attribute bits (such as "read - only") into the UNIX permissions of a file. This means there can - be a conflict between the permission bits set via the security - dialog and the permission bits set by the file attribute mapping. -

    One way this can show up is if a file has no UNIX read access - for the owner it will show up as "read only" in the standard - file attributes tabbed dialog. Unfortunately this dialog is - the same one that contains the security info in another tab.

    What this can mean is that if the owner changes the permissions - to allow themselves read access using the security dialog, clicks - "OK" to get back to the standard attributes tab - dialog, and then clicks "OK" on that dialog, then - NT will set the file permissions back to read-only (as that is what - the attributes still say in the dialog). This means that after setting - permissions and clicking "OK" to get back to the - attributes dialog you should always hit "Cancel" - rather than "OK" to ensure that your changes - are not overridden.

    Chapter 11. Configuring Group Mapping

    -Starting with Samba 3.0 alpha 2, a new group mapping function is available. The -current method (likely to change) to manage the groups is a new command called -smbgroupedit.

    The first immediate reason to use the group mapping on a PDC, is that -the domain admin group of smb.conf is -now gone. This parameter was used to give the listed users local admin rights -on their workstations. It was some magic stuff that simply worked but didn't -scale very well for complex setups.

    Let me explain how it works on NT/W2K, to have this magic fade away. -When installing NT/W2K on a computer, the installer program creates some users -and groups. Notably the 'Administrators' group, and gives to that group some -privileges like the ability to change the date and time or to kill any process -(or close too) running on the local machine. The 'Administrator' user is a -member of the 'Administrators' group, and thus 'inherit' the 'Administrators' -group privileges. If a 'joe' user is created and become a member of the -'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.

    When a NT/W2K machine is joined to a domain, during that phase, the "Domain -Administrators' group of the PDC is added to the 'Administrators' group of the -workstation. Every members of the 'Domain Administrators' group 'inherit' the -rights of the 'Administrators' group when logging on the workstation.

    You are now wondering how to make some of your samba PDC users members of the -'Domain Administrators' ? That's really easy.

    1. create a unix group (usually in /etc/group), let's call it domadm

    2. add to this group the users that must be Administrators. For example if you want joe,john and mary, your entry in /etc/group will look like:

      domadm:x:502:joe,john,mary

    3. Map this domadm group to the domain admins group by running the command:

      smbgroupedit -c "Domain Admins" -u domadm

    You're set, joe, john and mary are domain administrators !

    Like the Domain Admins group, you can map any arbitrary Unix group to any NT -group. You can also make any Unix group a domain group. For example, on a domain -member machine (an NT/W2K or a samba server running winbind), you would like to -give access to a certain directory to some users who are member of a group on -your samba PDC. Flag that group as a domain group by running:

    smbgroupedit -a unixgroup -td

    You can list the various groups in the mapping database like this

    smbgroupedit -v

    Chapter 12. Printing Support

    12.1. Introduction

    Beginning with the 2.2.0 release, Samba supports -the native Windows NT printing mechanisms implemented via -MS-RPC (i.e. the SPOOLSS named pipe). Previous versions of -Samba only supported LanMan printing calls.

    The additional functionality provided by the new -SPOOLSS support includes:

    • Support for downloading printer driver - files to Windows 95/98/NT/2000 clients upon demand. -

    • Uploading of printer drivers via the - Windows NT Add Printer Wizard (APW) or the - Imprints tool set (refer to http://imprints.sourceforge.net). -

    • Support for the native MS-RPC printing - calls such as StartDocPrinter, EnumJobs(), etc... (See - the MSDN documentation at http://msdn.microsoft.com/ - for more information on the Win32 printing API) -

    • Support for NT Access Control Lists (ACL) - on printer objects

    • Improved support for printer queue manipulation - through the use of an internal databases for spooled job - information

    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. As a side note, Samba does not use these drivers in any way to process -spooled files. They are utilized entirely by the clients.

    The following MS KB article, may be of some help if you are dealing with -Windows 2000 clients: How to Add Printers with No User -Interaction in Windows 2000

    http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP

    12.2. Configuration

    [print$] vs. [printer$]
     

    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.

    However, the initial implementation allowed for a -parameter named printer driver location -to be used on a per share basis to specify the location of -the driver files associated with that printer. Another -parameter named printer driver provided -a means of defining the printer driver name to be sent to -the client.

    12.2.1. Creating [print$]

    In order to support the uploading of printer driver -files, you must first configure a file share named [print$]. -The name of this share is hard coded in Samba's internals so -the name is very important (print$ is the service used by -Windows NT print servers to provide support for printer driver -download).

    You should modify the server's smb.conf file to add the global -parameters and to create the -following file share (of course, some of the parameter values, -such as 'path' are arbitrary and should be replaced with -appropriate values for your site):

    [global]
-    ; members of the ntadmin group should be able
-    ; to add drivers and set printer properties
-    ; root is implicitly a 'printer admin'
-    printer admin = @ntadmin
-
-[print$]
-    path = /usr/local/samba/printers
-    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,root

    The write list is used to allow administrative -level user accounts to have write access in order to update files -on the share. See the smb.conf(5) -man page for more information on configuring file shares.

    The requirement for guest -ok = yes 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.

    Author's Note
     

    The non-issue is that if all your Windows NT users are guaranteed to be -authenticated by the Samba server (such as a domain member server and the NT -user has already been validated by the Domain Controller in -order to logon to the Windows NT console), then guest access -is not necessary. Of course, in a workgroup environment where -you just want to be able to print without worrying about -silly accounts and security, then configure the share for -guest access. You'll probably want to add map to guest = Bad User in the [global] section as well. Make sure -you understand what this parameter does before using it -though. --jerry

    In order for a Windows NT print server to support -the downloading of driver files by multiple client architectures, -it must create subdirectories within the [print$] service -which correspond to each of the supported client architectures. -Samba follows this model as well.

    Next create the directory tree below the [print$] share -for each architecture you wish to support.

    [print$]----- - |-W32X86 ; "Windows NT x86" - |-WIN40 ; "Windows 95/98" - |-W32ALPHA ; "Windows NT Alpha_AXP" - |-W32MIPS ; "Windows NT R4000" - |-W32PPC ; "Windows NT PowerPC"

    ATTENTION! REQUIRED PERMISSIONS
     

    In order to currently add a new driver to you Samba host, -one of two conditions must hold true:

    • The account used to connect to the Samba host - must have a uid of 0 (i.e. a root account)

    • The account used to connect to the Samba host - must be a member of the printer - admin list.

    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.

    Once you have created the required [print$] service and -associated subdirectories, simply log onto the Samba server using -a root (or printer admin) account -from a Windows NT 4.0/2k client. Open "Network Neighbourhood" or -"My Network Places" and browse for the Samba host. Once you have located -the server, navigate to the "Printers..." folder. -You should see an initial listing of printers -that matches the printer shares defined on your Samba host.

    12.2.2. Setting Drivers for Existing Printers

    The initial listing of printers in the Samba host's -Printers folder will have no real printer driver assigned -to them. This defaults to a NULL string to allow the use -of 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:

    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?

    Click "No" in the error dialog and you will be presented with -the printer properties window. The way to assign a driver to a -printer is to either

    • Use the "New Driver..." button to install - a new printer driver, or

    • Select a driver from the popup list of - installed drivers. Initially this list will be empty.

    If you wish to install printer drivers for client -operating systems other than "Windows NT x86", you will need -to use the "Sharing" tab of the printer properties dialog.

    Assuming you have connected with a root account, you -will also be able modify other printer properties such as -ACLs and device settings using this dialog box.

    A few closing comments for this section, it is possible -on a Windows NT print server to have printers -listed in the Printers folder which are not shared. Samba does -not make this distinction. By definition, the only printers of -which Samba is aware are those which are specified as shares in -smb.conf.

    Another interesting side note is that Windows NT clients do -not use the SMB printer share, but rather can print directly -to any printer on another Windows NT host using MS-RPC. This -of course assumes that the printing client has the necessary -privileges on the remote host serving the printer. The default -permissions assigned by Windows NT to a printer gives the "Print" -permissions to the "Everyone" well-known group.

    12.2.3. Support a large number of printers

    One issue that has arisen during the development -phase of Samba 2.2 is the need to support driver downloads for -100's of printers. Using the Windows NT APW is somewhat -awkward to say the list. If more than one printer are using the -same driver, the rpcclient's -setdriver command can be used to set the driver -associated with an installed driver. The following is example -of how this could be accomplished:

    $ rpcclient pogo -U root%secret -c "enumdrivers" -

     
-Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
- 
-[Windows NT x86]
-Printer Driver Info 1:
-     Driver Name: [HP LaserJet 4000 Series PS]
- 
-Printer Driver Info 1:
-     Driver Name: [HP LaserJet 2100 Series PS]
- 
-Printer Driver Info 1:
-     Driver Name: [HP LaserJet 4Si/4SiMX PS]
    -$ rpcclient pogo -U root%secret -c "enumprinters" -
    Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
-     flags:[0x800000]
-     name:[\\POGO\hp-print]
-     description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,]
-     comment:[]
-
    -$ rpcclient pogo -U root%secret -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.

    12.2.4. Adding New Printers via the Windows NT APW

    By default, Samba offers all printer shares defined in smb.conf -in the "Printers..." folder. Also existing in this folder is the Windows NT -Add Printer Wizard icon. The APW will be show only if

    • The connected user is able to successfully - execute an OpenPrinterEx(\\server) with administrative - privileges (i.e. root or printer admin). -

    • show - add printer wizard = yes (the default). -

    In order to be able to use the APW to successfully add a printer to a Samba -server, the add -printer command must have a defined value. The program -hook must successfully add the printer to the system (i.e. -/etc/printcap or appropriate files) and -smb.conf if necessary.

    When using the APW from a client, if the named printer share does -not exist, smbd will execute the add printer -command and reparse to the smb.conf -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 -add printer program is executed under the context -of the connected user, not necessarily a root account.

    There is a complementary delete -printer command for removing entries from the "Printers..." -folder.

    The following is an example add printer command script. It adds the appropriate entries to /etc/printcap.local (change that to what you need) and returns a line of 'Done' which is needed for the whole process to work.

    #!/bin/sh
-
-# Script to insert a new printer entry into printcap.local
-#
-# $1, printer name, used as the descriptive name
-# $2, share name, used as the printer name for Linux
-# $3, port name
-# $4, driver name
-# $5, location, used for the device file of the printer
-# $6, win9x location
-
-#
-# Make sure we use the location that RedHat uses for local printer defs
-PRINTCAP=/etc/printcap.local
-DATE=`date +%Y%m%d-%H%M%S`
-LP=lp
-RESTART="service lpd restart"
-
-# Keep a copy
-cp $PRINTCAP $PRINTCAP.$DATE
-# Add the printer to $PRINTCAP
-echo ""				 			>> $PRINTCAP
-echo "$2|$1:\\" 					>> $PRINTCAP
-echo "  :sd=/var/spool/lpd/$2:\\" 			>> $PRINTCAP
-echo "  :mx=0:ml=0:sh:\\" 				>> $PRINTCAP
-echo "  :lp=/usr/local/samba/var/print/$5.prn:" 	>> $PRINTCAP
-
-touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1
-chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1
-
-mkdir /var/spool/lpd/$2
-chmod 700 /var/spool/lpd/$2
-chown $LP /var/spool/lpd/$2
-#echo $1 >> "/usr/local/samba/var/print/$5.prn"
-#echo $2 >> "/usr/local/samba/var/print/$5.prn"
-#echo $3 >> "/usr/local/samba/var/print/$5.prn"
-#echo $4 >> "/usr/local/samba/var/print/$5.prn"
-#echo $5 >> "/usr/local/samba/var/print/$5.prn"
-#echo $6 >> "/usr/local/samba/var/print/$5.prn"
-$RESTART >> "/usr/local/samba/var/print/$5.prn"
-# Not sure if this is needed
-touch /usr/local/samba/lib/smb.conf
-#
-# You need to return a value, but I am not sure what it means.
-#
-echo "Done"
-exit 0

    12.2.5. Samba and Printer Ports

    Windows NT/2000 print servers associate a port with each printer. These normally -take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the -concept of ports associated with a printer. By default, only one printer port, -named "Samba Printer Port", exists on a system. Samba does not really a port in -order to print, rather it is a requirement of Windows clients.

    Note that Samba does not support the concept of "Printer Pooling" internally -either. This is when a logical printer is assigned to multiple ports as -a form of load balancing or fail over.

    If you require that multiple ports be defined for some reason, -smb.conf possesses a enumports -command which can be used to define an external program -that generates a listing of ports on a system.

    12.3. The Imprints Toolset

    The Imprints tool set provides a UNIX equivalent of the - Windows NT Add Printer Wizard. For complete information, please - refer to the Imprints web site at http://imprints.sourceforge.net/ as well as the documentation - included with the imprints source distribution. This section will - only provide a brief introduction to the features of Imprints.

    12.3.1. What is Imprints?

    Imprints is a collection of tools for supporting the goals - of

    • Providing a central repository information - regarding Windows NT and 95/98 printer driver packages

    • Providing the tools necessary for creating - the Imprints printer driver packages.

    • Providing an installation client which - will obtain and install printer drivers on remote Samba - and Windows NT 4 print servers.

    12.3.2. Creating Printer Driver Packages

    The process of creating printer driver packages is beyond - the scope of this document (refer to Imprints.txt also included - with the Samba distribution for more information). In short, - an Imprints driver package is a gzipped tarball containing the - driver files, related INF files, and a control file needed by the - installation client.

    12.3.3. The Imprints server

    The Imprints server is really a database server that - may be queried via standard HTTP mechanisms. Each printer - entry in the database has an associated URL for the actual - downloading of the package. Each package is digitally signed - via GnuPG which can be used to verify that package downloaded - is actually the one referred in the Imprints database. It is - not recommended that this security check - be disabled.

    12.3.4. The Installation Client

    More information regarding the Imprints installation client - is available in the Imprints-Client-HOWTO.ps - file included with the imprints source package.

    The Imprints installation client comes in two forms.

    • a set of command line Perl scripts

    • a GTK+ based graphical interface to - the command line perl scripts

    The installation client (in both forms) provides a means - of querying the Imprints database server for a matching - list of known printer model names as well as a means to - download and install the drivers on remote Samba and Windows - NT print servers.

    The basic installation process is in four steps and - perl code is wrapped around smbclient - and rpcclient.

    	
-foreach (supported architecture for a given driver)
-{
-     1.  rpcclient: Get the appropriate upload directory 
-         on the remote server
-     2.  smbclient: Upload the driver files
-     3.  rpcclient: Issues an AddPrinterDriver() MS-RPC
-}
-	
-4.  rpcclient: Issue an AddPrinterEx() MS-RPC to actually
-    create the printer

    One of the problems encountered when implementing - the Imprints tool set was the name space issues between - various supported client architectures. For example, Windows - NT includes a driver named "Apple LaserWriter II NTX v51.8" - and Windows 95 calls its version of this driver "Apple - LaserWriter II NTX"

    The problem is how to know what client drivers have - been uploaded for a printer. As astute reader will remember - that the Windows NT Printer Properties dialog only includes - space for one printer driver name. A quick look in the - Windows NT 4.0 system registry at

    HKLM\System\CurrentControlSet\Control\Print\Environment -

    will reveal that Windows NT always uses the NT driver - 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 - already been installed?

    The way of sidestepping this limitation is to require - that all Imprints printer driver packages include both the Intel - Windows NT and 95/98 printer drivers and that NT driver is - installed first.

    12.4. Diagnosis

    12.4.1. Introduction

    This is a short description of how to debug printing problems with -Samba. This describes how to debug problems with printing from a SMB -client to a Samba server, not the other way around. For the reverse -see the examples/printing directory.

    Ok, so you want to print to a Samba server from your PC. The first -thing you need to understand is that Samba does not actually do any -printing itself, it just acts as a middleman between your PC client -and your Unix printing subsystem. Samba receives the file from the PC -then passes the file to a external "print command". What print command -you use is up to you.

    The whole things is controlled using options in smb.conf. The most -relevant options (which you should look up in the smb.conf man page) -are:

          [global]
-        print command     - send a file to a spooler
-        lpq command       - get spool queue status
-        lprm command      - remove a job
-      [printers]
-        path = /var/spool/lpd/samba

    The following are nice to know about:

            queuepause command   - stop a printer or print queue
-        queueresume command  - start a printer or print queue

    Example:

            print command = /usr/bin/lpr -r -P%p %s
-        lpq command   = /usr/bin/lpq    -P%p %s
-        lprm command  = /usr/bin/lprm   -P%p %j
-        queuepause command = /usr/sbin/lpc -P%p stop
-        queuepause command = /usr/sbin/lpc -P%p start

    Samba should set reasonable defaults for these depending on your -system type, but it isn't clairvoyant. It is not uncommon that you -have to tweak these for local conditions. The commands should -always have fully specified pathnames, as the smdb may not have -the correct PATH values.

    When you send a job to Samba to be printed, it will make a temporary -copy of it in the directory specified in the [printers] section. -and it should be periodically cleaned out. The lpr -r option -requests that the temporary copy be removed after printing; If -printing fails then you might find leftover files in this directory, -and it should be periodically cleaned out. Samba used the lpq -command to determine the "job number" assigned to your print job -by the spooler.

    The %>letter< are "macros" that get dynamically replaced with appropriate -values when they are used. The %s gets replaced with the name of the spool -file that Samba creates and the %p gets replaced with the name of the -printer. The %j gets replaced with the "job number" which comes from -the lpq output.

    12.4.2. Debugging printer problems

    One way to debug printing problems is to start by replacing these -command with shell scripts that record the arguments and the contents -of the print file. A simple example of this kind of things might -be:

    	print command = /tmp/saveprint %p %s
-
-    #!/bin/saveprint
-    # we make sure that we are the right user
-    /usr/bin/id -p >/tmp/tmp.print
-    # we run the command and save the error messages
-    # replace the command with the one appropriate for your system
-    /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print

    Then you print a file and try removing it. You may find that the -print queue needs to be stopped in order to see the queue status -and remove the job:

    
h4: {42} % echo hi >/tmp/hi
-h4: {43} % smbclient //localhost/lw4
-added interface ip=10.0.0.4 bcast=10.0.0.255 nmask=255.255.255.0
-Password: 
-Domain=[ASTART] OS=[Unix] Server=[Samba 2.0.7]
-smb: \> print /tmp/hi
-putting file /tmp/hi as hi-17534 (0.0 kb/s) (average 0.0 kb/s)
-smb: \> queue
-1049     3            hi-17534
-smb: \> cancel 1049
-Error cancelling job 1049 : code 0
-smb: \> cancel 1049
-Job 1049 cancelled
-smb: \> queue
-smb: \> exit

    The 'code 0' indicates that the job was removed. The comment -by the smbclient is a bit misleading on this. -You can observe the command output and then and look at the -/tmp/tmp.print file to see what the results are. You can quickly -find out if the problem is with your printing system. Often people -have problems with their /etc/printcap file or permissions on -various print queues.

    12.4.3. What printers do I have?

    You can use the 'testprns' program to check to see if the printer -name you are using is recognized by Samba. For example, you can -use:

        testprns printer /etc/printcap

    Samba can get its printcap information from a file or from a program. -You can try the following to see the format of the extracted -information:

        testprns -a printer /etc/printcap
-
-    testprns -a printer '|/bin/cat printcap'

    12.4.4. Setting up printcap and print servers

    You may need to set up some printcaps for your Samba system to use. -It is strongly recommended that you use the facilities provided by -the print spooler to set up queues and printcap information.

    Samba requires either a printcap or program to deliver printcap -information. This printcap information has the format:

      name|alias1|alias2...:option=value:...

    For almost all printing systems, the printer 'name' must be composed -only of alphanumeric or underscore '_' characters. Some systems also -allow hyphens ('-') as well. An alias is an alternative name for the -printer, and an alias with a space in it is used as a 'comment' -about the printer. The printcap format optionally uses a \ at the end of lines -to extend the printcap to multiple lines.

    Here are some examples of printcap files:

    1. pr just printer name

    2. pr|alias printer name and alias

    3. pr|My Printer printer name, alias used as comment

    4. pr:sh:\ Same as pr:sh:cm= testing - :cm= \ - testing

    5. pr:sh Same as pr:sh:cm= testing - :cm= testing

    Samba reads the printcap information when first started. If you make -changes in the printcap information, then you must do the following:

    1. make sure that the print spooler is aware of these changes. -The LPRng system uses the 'lpc reread' command to do this.

    2. make sure that the spool queues, etc., exist and have the -correct permissions. The LPRng system uses the 'checkpc -f' -command to do this.

    3. You now should send a SIGHUP signal to the smbd server to have -it reread the printcap information.

    12.4.5. Job sent, no output

    This is the most frustrating part of printing. You may have sent the -job, verified that the job was forwarded, set up a wrapper around -the command to send the file, but there was no output from the printer.

    First, check to make sure that the job REALLY is getting to the -right print queue. If you are using a BSD or LPRng print spooler, -you can temporarily stop the printing of jobs. Jobs can still be -submitted, but they will not be printed. Use:

      lpc -Pprinter stop

    Now submit a print job and then use 'lpq -Pprinter' to see if the -job is in the print queue. If it is not in the print queue then -you will have to find out why it is not being accepted for printing.

    Next, you may want to check to see what the format of the job really -was. With the assistance of the system administrator you can view -the submitted jobs files. You may be surprised to find that these -are not in what you would expect to call a printable format. -You can use the UNIX 'file' utitily to determine what the job -format actually is:

        cd /var/spool/lpd/printer   # spool directory of print jobs
-    ls                          # find job files
-    file dfA001myhost

    You should make sure that your printer supports this format OR that -your system administrator has installed a 'print filter' that will -convert the file to a format appropriate for your printer.

    12.4.6. Job sent, strange output

    Once you have the job printing, you can then start worrying about -making it print nicely.

    The most common problem is extra pages of output: banner pages -OR blank pages at the end.

    If you are getting banner pages, check and make sure that the -printcap option or printer option is configured for no banners. -If you have a printcap, this is the :sh (suppress header or banner -page) option. You should have the following in your printer.

       printer: ... :sh

    If you have this option and are still getting banner pages, there -is a strong chance that your printer is generating them for you -automatically. You should make sure that banner printing is disabled -for the printer. This usually requires using the printer setup software -or procedures supplied by the printer manufacturer.

    If you get an extra page of output, this could be due to problems -with your job format, or if you are generating PostScript jobs, -incorrect setting on your printer driver on the MicroSoft client. -For example, under Win95 there is a option:

      Printers|Printer Name|(Right Click)Properties|Postscript|Advanced|

    that allows you to choose if a Ctrl-D is appended to all jobs. -This is a very bad thing to do, as most spooling systems will -automatically add a ^D to the end of the job if it is detected as -PostScript. The multiple ^D may cause an additional page of output.

    12.4.7. Raw PostScript printed

    This is a problem that is usually caused by either the print spooling -system putting information at the start of the print job that makes -the printer think the job is a text file, or your printer simply -does not support PostScript. You may need to enable 'Automatic -Format Detection' on your printer.

    12.4.8. Advanced Printing

    Note that you can do some pretty magic things by using your -imagination with the "print command" option and some shell scripts. -Doing print accounting is easy by passing the %U option to a print -command shell script. You could even make the print command detect -the type of output and its size and send it to an appropriate -printer.

    12.4.9. Real debugging

    If the above debug tips don't help, then maybe you need to bring in -the bug guns, system tracing. See Tracing.txt in this directory.

    Chapter 13. CUPS Printing Support

    13.1. Introduction

    The Common Unix Print System (CUPS) has become very popular, but to many it is -a very mystical tool. There is a great deal of uncertainty regarding CUPS and how -it works. The result is seen in a large number of posting on the samba mailing lists -expressing frustration when MS Windows printers appear not to work with a CUPS -backr-end. -/para>

    This is a good time to point out how CUPS can be used and what it does. CUPS is more -than just a print spooling system - it is a complete printer management system that -complies with HTTP and IPP protocols. It can be managed remotely via a web browser -and it can print using http and ipp protocols.

    CUPS allows to creation of RAW printers (ie: NO file format translation) as well as -SMART printers (ie: CUPS does file format conversion as required for the printer). In -many ways this gives CUPS similar capabilities to the MS Windows print monitoring -system. Of course, if you are a CUPS advocate, you would agrue that CUPS is better! -In any case, let us now move on to explore how one may configure CUPS for interfacing -with MS Windows print clients via Samba.

    CUPS is a newcomer in the UNIX printing scene, -which has convinced many people upon first trial already. However, it has quite a few -new features, which make it different from other, more traditional printing systems.

    13.2. Configuring smb.conf for CUPS

    Printing with CUPS in the most basic smb.conf -setup in Samba-3 only needs two settings: printing = cups and -printcap = cups. While CUPS itself doesn't need a printcap -anymore, the cupsd.conf configuration file knows two directives -(example: Printcap /etc/printcap and PrintcapFormat -BSD), which control if such a file should be created for the -convenience of third party applications. Make sure it is set! For details see -man cupsd.conf and other CUPS-related documentation.

    If SAMBA is compiled against libcups, then printcap = cups uses the -CUPS API to list printers, submit jobs, etc. Otherwise it maps to the System V commands -with an additional -oraw option for printing. On a Linux system, -you can use the ldd command to find out details (ldd may not be -present on other OS platforms, or its function may be embodied by a different command):

    transmeta:/home/kurt # ldd `which smbd`
-        libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000)
-        libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
-        libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000)
-        libdl.so.2 => /lib/libdl.so.2 (0x401e8000)
-        libnsl.so.1 => /lib/libnsl.so.1 (0x401ec000)
-        libpam.so.0 => /lib/libpam.so.0 (0x40202000)
-        libc.so.6 => /lib/libc.so.6 (0x4020b000)
-        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

    The line "libcups.so.2 => /usr/lib/libcups.so.2 -(0x40123000)" shows there is CUPS support compiled into this version of -Samba. If this is the case, and printing = cups is set, then any -otherwise manually set print command in smb.conf is ignored.

    13.3. CUPS - RAW Print Through Mode

    When used in raw print through mode is will be necessary to use the printer -vendor's drivers in each Windows client PC.

    When CUPS printers are configured for RAW print-through mode operation it is the -responsibility of the Samba client to fully render the print job (file) in a format -that is suitable for direct delivery to the printer. In this case CUPS will NOT -do any print file format conversion work.

    The CUPS files that need to be correctly set for RAW mode printers to work are: - -

    • /etc/cups/mime.types

    • /etc/cups/mime.convs

    - -Both contain entries that must be uncommented to allow RAW mode -operation.

    Firstly, to enable CUPS based printing from Samba the following options must be -enabled in your smb.conf file [globals] section: - -

    • printing = CUPS

    • printcap = CUPS

    - -When these parameters are specified the print directives in smb.conf (as well as in -samba itself) will be ignored because samba will directly interface with CUPS through -it's application program interface (API) - so long as Samba has been compiled with -CUPS library (libcups) support. If samba has NOT been compiled with CUPS support then -printing will use the System V AT&T command set with the -oraw -option automatically passing through.

    Cupsomatic (an enhanced printing utility that is part of some CUPS implementations) -on the Samba/CUPS server does *not* add any features if a file is really -printed "raw". However, if you have loaded the driver for the Windows client from -the CUPS server, using the "cupsaddsmb" utility, and if this driver is one using -a "Foomatic" PPD, the PJL header in question is already added on the Windows client, -at the time when the driver initially generated the PostScript data and CUPS in true -"-oraw" manner doesn't remove this PJL header and passes the file "as is" to its -printer communication backend.

    NOTE: editing in the "mime.convs" and the "mime.types" file does not *enforce* -"raw" printing, it only *allows* it.

    Print files that arrive from MS Windows printing are "auto-typed" by CUPS. This aids -the process of determining proper treatment while in the print queue system. - -

    • Files generated by PCL drivers and directed at PCK printers get auto-typed as - application/octet-stream. Unknown file format types also - get auto-typed with this tag. -

    • Files generated by a Postscript driver and directed at a Postscript printer - are auto-typed depending on the auto-detected most suitable MIME type as: - -

      • * application/postscript

      • * application/vnd.cups-postscript

      -

    "application/postscript" first goes thru the "pstops" filter (where the page counting -and accounting takes place). The outcome will be of MIME type -"application/vnd.cups-postscript". The pstopsfilter reads and uses information from -the PPD and inserts user-provided options into the PostScript file. As a consequence, -the filtered file could possibly have an unwanted PJL header.

    "application/postscript" will be all files with a ".ps", ".ai", ".eps" suffix or which -have as their first character string one of "%!" or "<04>%".

    "application/vnd.cups-postscript" will files which contain the string -"LANGUAGE=POSTSCRIPT" (or similar variations with different capitalization) in the -first 512 bytes, and also contain the "PJL super escape code" in the first 128 bytes -("<1B>%-12345X"). Very likely, most PostScript files generated on Windows using a CUPS -or other PPD, will have to be auto-typed as "vnd.cups-postscript". A file produced -with a "Generic PostScript driver" will just be tagged "application/postscript".

    Once the file is in "application/vnd.cups-postscript" format, either "pstoraster" -or "cupsomatic" will take over (depending on the printer configuration, as -determined by the PPD in use).

    A printer queue with *no* PPD associated to it is a "raw" printer and all files -will go directly there as received by the spooler. The exeptions are file types -"application/octet-stream" which need "passthrough feature" enabled. -"Raw" queues don't do any filtering at all, they hand the file directly to the -CUPS backend. This backend is responsible for the sending of the data to the device -(as in the "device URI" notation as lpd://, socket://, smb://, ipp://, http://, -parallel:/, serial:/, usb:/ etc.)

    "cupsomatic"/Foomatic are *not* native CUPS drivers and they don't ship with CUPS. -They are a Third Party add-on, developed at Linuxprinting.org. As such, they are -a brilliant hack to make all models (driven by Ghostscript drivers/filters in -traditional spoolers) also work via CUPS, with the same (good or bad!) quality -as in these other spoolers. "cupsomatic" is only a vehicle to execute a ghostscript -commandline at that stage in the CUPS filtering chain, where "normally" the native -CUPS "pstoraster" filter would kick in. cupsomatic by-passes pstoraster, "kidnaps" -the printfile from CUPS away and re-directs it to go through Ghostscipt. CUPS accepts this, -because the associated CUPS-O-Matic-/Foomatic-PPD specifies:

       *cupsFilter:  "application/vnd.cups-postscript 0 cupsomatic"

    This line persuades CUPS to hand the file to cupsomatic, once it has successfully -converted it to the MIME type "application/vnd.cups-postscript". This conversion will not -happen for Jobs arriving from Windows which are auto-typed "application/octet-stream", -with the according changes in "/etc/cups/mime.types" in place.

    CUPS is widely configurable and flexible, even regarding its filtering mechanism. -Another workaround in some situations would be to have -in "/etc/cups/mime.types" entries as follows:

       application/postscript           application/vnd.cups-raw  0  -
-   application/vnd.cups-postscript  application/vnd.cups-raw  0  -

    This would prevent all Postscript files from being filtered (rather, they will go -thru the virtual "nullfilter" denoted with "-"). This could only be useful for -PS printers. If you want to print PS code on non-PS printers an entry as follows -could be useful:

       */*           application/vnd.cups-raw  0  -

    and would effectively send *all* files to the backend without further processing.

    Lastly, you could have the following entry:

       application/vnd.cups-postscript  application/vnd.cups-raw  0  my_PJL_stripping_filter

    You will need to write a "my_PJL_stripping_filter" (could be a shellscript) that -parses the PostScript and removes the unwanted PJL. This would need to conform to -CUPS filter design (mainly, receive and pass the parameters printername, job-id, -username, jobtitle, copies, print options and possibly the filename). It would -be installed as world executable into "/usr/lib/cups/filters/" and will be called -by CUPS if it encounters a MIME type "application/vnd.cups-postscript".

    CUPS can handle "-o job-hold-until=indefinite". This keeps the job in the queue -"on hold". It will only be printed upon manual release by the printer operator. -This is a requirement in many "central reproduction departments", where a few -operators manage the jobs of hundreds of users on some big machine, where no -user is allowed to have direct access. (The operators often need to load the -proper paper type before running the 10.000 page job requested by marketing -for the mailing, etc.).

    13.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe -PostScript driver with CUPS-PPDs downloaded to clients

    CUPS is perfectly able to use PPD files (PostScript -Printer Descriptions). PPDs can control all print device options. They -are usually provided by the manufacturer -- if you own a PostSript printer, -that is. PPD files are always a component of PostScript printer drivers on MS -Windows or Apple Mac OS systems. They are ASCII files containing -user-selectable print options, mapped to appropriate PostScript, PCL or PJL -commands for the target printer. Printer driver GUI dialogs translate these -options "on-the-fly" into buttons and drop-down lists for the user to -select.

    CUPS can load, without any conversions, the PPD file from -any Windows (NT is recommended) PostScript driver and handle the options. -There is a web browser interface to the print options (select -http://localhost:631/printers/ and click on one "Configure Printer" button -to see it), a commandline interface (see man lpoptions or -try if you have lphelp on your system) plus some different GUI frontends on Linux -UNIX, which can present PPD options to the users. PPD options are normally -meant to become evaluated by the PostScript RIP on the real PostScript -printer.

    CUPS doesn't stop at "real" PostScript printers in its -usage of PPDs. The CUPS developers have extended the PPD concept, to also -describe available device and driver options for non-PostScript printers -through CUPS-PPDs.

    This is logical, as CUPS includes a fully featured -PostScript interpreter (RIP). This RIP is based on Ghostscript. It can -process all received PostScript (and additionally many other file formats) -from clients. All CUPS-PPDs geared to non-PostScript printers contain an -additional line, starting with the keyword *cupsFilter. -This line -tells the CUPS print system which printer-specific filter to use for the -interpretation of the accompanying PostScript. Thus CUPS lets all its -printers appear as PostScript devices to its clients, because it can act as a -PostScript RIP for those printers, processing the received PostScript code -into a proper raster print format.

    CUPS-PPDs can also be used on Windows-Clients, on top of a -PostScript driver (recommended is the Adobe one).

    This feature enables CUPS to do a few tricks no other -spooler can do:

    • act as a networked PostScript RIP (Raster Image Processor), handling - printfiles from all client platforms in a uniform way;

    • act as a central accounting and billing server, as all files are passed - through the pstops Filter and are therefor logged in - the CUPS page_log. - NOTE: this - can not happen with "raw" print jobs, which always remain unfiltered - per definition;

    • enable clients to consolidate on a single PostScript driver, even for - many different target printers.

    13.5. Windows Terminal Servers (WTS) as CUPS clients

    This setup may be of special interest to people -experiencing major problems in WTS environments. WTS need often a multitude -of non-PostScript drivers installed to run their clients' variety of -different printer models. This often imposes the price of much increased -instability. In many cases, in an attempt to overcome this problem, site -administrators have resorted to restrict the allowed drivers installed on -their WTS to one generic PCL- and one PostScript driver. This however -restricts the clients in the amount of printer options available for them -- -often they can't get out more then simplex prints from one standard paper -tray, while their devices could do much better, if driven by a different -driver!

    Using an Adobe PostScript driver, enabled with a CUPS-PPD, -seems to be a very elegant way to overcome all these shortcomings. The -PostScript driver is not known to cause major stability problems on WTS (even -if used with many different PPDs). The clients will be able to (again) chose -paper trays, duplex printing and other settings. However, there is a certain -price for this too: a CUPS server acting as a PostScript RIP for its clients -requires more CPU and RAM than just to act as a "raw spooling" device. Plus, -this setup is not yet widely tested, although the first feedbacks look very -promising...

    13.6. Setting up CUPS for driver download

    The cupsadsmb utility (shipped with all current -CUPS versions) makes the sharing of any (or all) installed CUPS printers very -easy. Prior to using it, you need the following settings in smb.conf:

    [global]
-		 load printers = yes
-		 printing = cups
-		 printcap name = cups
-
-	[printers]
-		 comment = All Printers
-		 path = /var/spool/samba
-		 browseable = no
-		 public = yes
-		 guest ok = yes
-		 writable = no
-		 printable = yes
-		 printer admin = root
-
-	[print$]
-		 comment = Printer Drivers
-		 path = /etc/samba/drivers
-		 browseable = yes
-		 guest ok = no
-		 read only = yes
-		 write list = root
-

    For licensing reasons the necessary files of the Adobe -Postscript driver can not be distributed with either Samba or CUPS. You need -to download them yourself from the Adobe website. Once extracted, create a -drivers directory in the CUPS data directory (usually -/usr/share/cups/). Copy the Adobe files using -UPPERCASE filenames, to this directory as follows:

    		ADFONTS.MFM
-		ADOBEPS4.DRV
-		ADOBEPS4.HLP
-		ADOBEPS5.DLL
-		ADOBEPSU.DLL
-		ADOBEPSU.HLP
-		DEFPRTR2.PPD
-		ICONLIB.DLL
-

    Users of the ESP Print Pro software are able to install -their "Samba Drivers" package for this purpose with no problem.

    13.7. Sources of CUPS drivers / PPDs

    On the internet you can find now many thousand CUPS-PPD -files (with their companion filters), in many national languages, -supporting more than 1.000 non-PostScript models.

    NOTE: the cupsomatic trick from Linuxprinting.org is -working different from the other drivers. While the other drivers take the -generic CUPS raster (produced by CUPS' own pstoraster PostScript RIP) as -their input, cupsomatic "kidnaps" the PostScript inside CUPS, before -RIP-ping, deviates it to an external Ghostscript installation (which now -becomes the RIP) and gives it back to a CUPS backend once Ghostscript is -finished. -- CUPS versions from 1.1.15 and later will provide their pstoraster -PostScript RIP function again inside a system-wide Ghostscript -installation rather than in "their own" pstoraster filter. (This -CUPS-enabling Ghostscript version may be installed either as a -patch to GNU or AFPL Ghostscript, or as a complete ESP Ghostscript package). -However, this will not change the cupsomatic approach of guiding the printjob -along a different path through the filtering system than the standard CUPS -way...

    Once you installed a printer inside CUPS with one of the -recommended methods (the lpadmin command, the web browser interface or one of -the available GUI wizards), you can use cupsaddsmb to share the -printer via Samba. cupsaddsmb prepares the driver files for -comfortable client download and installation upon their first contact with -this printer share.

    13.7.1. cupsaddsmb

    The cupsaddsmb command copies the needed files -for convenient Windows client installations from the previously prepared CUPS -data directory to your [print$] share. Additionally, the PPD -associated with this printer is copied from /etc/cups/ppd/ to -[print$].

    root#  cupsaddsmb -U root infotec_IS2027
-Password for root required to access localhost via SAMBA: [type in password 'secret']

    To share all printers and drivers, use the -a -parameter instead of a printer name.

    Probably you want to see what's going on. Use the --v parameter to get a more verbose output:

    Probably you want to see what's going on. Use the --v parameter to get a more verbose output:

    Note: The following line shave been wrapped so that information is not lost.
- 
-root#  cupsaddsmb -v -U root infotec_IS2027
-    Password for root required to access localhost via SAMBA:
-    Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put
-       /var/spool/cups/tmp/3cd1cc66376c0 W32X86/infotec_IS2027.PPD;put /usr/share/cups/drivers/
-       ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLLr
-       W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP'
-    added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
-    added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
-    added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
-    Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
-    NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
-    putting file /var/spool/cups/tmp/3cd1cc66376c0 as \W32X86/infotec_IS2027.PPD (17394.6 kb/s)
-      (average 17395.2 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPS5.DLL as \W32X86/ADOBEPS5.DLL (10877.4 kb/s)
-      (average 11343.0 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPSU.DLL as \W32X86/ADOBEPSU.DLL (5095.2 kb/s)
-      (average 9260.4 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPSU.HLP as \W32X86/ADOBEPSU.HLP (8828.7 kb/s)
-      (average 9247.1 kb/s)
-
-    Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put
-      /var/spool/cups/tmp/3cd1cc66376c0 WIN40/infotec_IS2027.PPD;put
-      /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put
-      /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put
-      /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put
-      /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put
-      /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put
-      /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
-    added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
-    added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
-    added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
-    Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
-    NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
-    putting file /var/spool/cups/tmp/3cd1cc66376c0 as \WIN40/infotec_IS2027.PPD (26091.5 kb/s)
-      (average 26092.8 kb/s)
-    putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (11241.6 kb/s)
-      (average 11812.9 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (16640.6 kb/s)
-      (average 14679.3 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (11285.6 kb/s)
-      (average 14281.5 kb/s)
-    putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (823.5 kb/s)
-      (average 12944.0 kb/s)
-    putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (19226.2 kb/s)
-      (average 13169.7 kb/s)
-    putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (18666.1 kb/s)
-      (average 13266.7 kb/s)
-
-    Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows NT x86"
-       "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"'
-    cmd = adddriver "Windows NT x86" "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:
-       ADOBEPSU.HLP:NULL:RAW:NULL"
-    Printer Driver infotec_IS2027 successfully installed.
-
-    Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows 4.0"
-       "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:
-       ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
-    cmd = adddriver "Windows 4.0" "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:
-       ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
-    Printer Driver infotec_IS2027 successfully installed.
-
-    Running command: rpcclient localhost -N -U'root%secret'
-       -c 'setdriver infotec_IS2027 infotec_IS2027'
-    cmd = setdriver infotec_IS2027 infotec_IS2027
-    Succesfully set infotec_IS2027 to driver infotec_IS2027.
-
-    root#

    If you look closely, you'll discover your root password was transfered unencrypted over -the wire, so beware! Also, if you look further her, you'll discover error messages like -NT_STATUS_OBJECT_NAME_COLLISION in between. They occur, because -the directories WIN40 and W32X86 already -existed in the [print$] driver download share (from a previous driver -installation). They are harmless here.

    Now your printer is prepared for the clients to use. From -a client, browse to the CUPS/Samba server, open the "Printers" -share, right-click on this printer and select "Install..." or -"Connect..." (depending on the Windows version you use). Now their -should be a new printer in your client's local "Printers" folder, -named (in my case) "infotec_IS2027 on kdebitshop"

    NOTE: -cupsaddsmb will only reliably work i -with CUPS version 1.1.15 or higher -and Samba from 2.2.4. If it doesn't work, or if the automatic printer -driver download to the clients doesn't succeed, you can still manually -install the CUPS printer PPD on top of the Adobe PostScript driver on -clients and then point the client's printer queue to the Samba printer -share for connection, should you desire to use the CUPS networked -PostScript RIP functions.

    13.8. The CUPS Filter Chains

    The following diagrams reveal how CUPS handles print jobs.

    #########################################################################
-#
-# CUPS in and of itself has this (general) filter chain (CAPITAL
-# letters are FILE-FORMATS or MIME types, other are filters (this is
-# true for pre-1.1.15 of pre-4.3 versions of CUPS and ESP PrintPro):
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      |
-#      V
-#     somethingtops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#     pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT
-#      |
-#      |
-#      V
-#     pstoraster   # as shipped with CUPS, independent from any Ghostscipt
-#      |           # installation on the system
-#      |  (= "postscipt interpreter")
-#      |
-#      V
-# APPLICATION/VND.CUPS-RASTER
-#      |
-#      |
-#      V
-#     rastertosomething  (f.e. Gimp-Print filters may be plugged in here)
-#      |   (= "raster driver")
-#      |
-#      V
-# SOMETHING-DEVICE-SPECIFIC
-#      |
-#      |
-#      V
-#     backend
-#
-#
-# ESP PrintPro has some enhanced "rastertosomething" filters as compared to
-# CUPS, and also a somewhat improved "pstoraster" filter.
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
    #########################################################################
-#
-# This is how "cupsomatic" comes into play:
-# =========================================
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      |
-#      V
-#    somethingtops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#    pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
-#      |                                          |
-#      |                                          V
-#      V                                         cupsomatic
-#    pstoraster                                  (constructs complicated
-#      |  (= "postscipt interpreter")            Ghostscript commandline
-#      |                                         to let the file be
-#      V                                         processed by a
-# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=s.th."
-#      |                                         call...)
-#      |                                          |
-#      V                                          |
-#    rastertosomething                          V
-#      |    (= "raster driver")     +-------------------------+
-#      |                            | Ghostscript at work.... |
-#      V                            |                         |
-# SOMETHING-DEVICE-SPECIFIC         *-------------------------+
-#      |                                          |
-#      |                                          |
-#      V                                          |
-#    backend >------------------------------------+
-#      |
-#      |
-#      V
-#    THE PRINTER
-#
-#
-# Note, that cupsomatic "kidnaps" the printfile after the
-# "APPLICATION/VND.CUPS-POSTSCRPT" stage and deviates it through
-# the CUPS-external, systemwide Ghostscript installation, bypassing the
-# "pstoraster" filter (therefor also bypassing the CUPS-raster-drivers
-# "rastertosomething", and hands the rasterized file directly to the CUPS
-# backend...
-#
-# cupsomatic is not made by the CUPS developers. It is an independent
-# contribution to printing development, made by people from
-# Linuxprinting.org. (see also http://www.cups.org/cups-help.html)
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
    #########################################################################
-#
-# And this is how it works for ESP PrintPro from 4.3:
-# ===================================================
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      |
-#      V
-#     somethingtops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#     pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT
-#      |
-#      |
-#      V
-#     gsrip
-#      |  (= "postscipt interpreter")
-#      |
-#      V
-# APPLICATION/VND.CUPS-RASTER
-#      |
-#      |
-#      V
-#     rastertosomething  (f.e. Gimp-Print filters may be plugged in here)
-#      |   (= "raster driver")
-#      |
-#      V
-# SOMETHING-DEVICE-SPECIFIC
-#      |
-#      |
-#      V
-#     backend
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
    #########################################################################
-#
-# This is how "cupsomatic" would come into play with ESP PrintPro:
-# ================================================================
-#
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      |
-#      V
-#    somethingtops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#    pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
-#      |                                          |
-#      |                                          V
-#      V                                         cupsomatic
-#    gsrip                                       (constructs complicated
-#      |  (= "postscipt interpreter")            Ghostscript commandline
-#      |                                         to let the file be
-#      V                                         processed by a
-# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=s.th."
-#      |                                         call...)
-#      |                                          |
-#      V                                          |
-#    rastertosomething                          V
-#      |   (= "raster driver")      +-------------------------+
-#      |                            | Ghostscript at work.... |
-#      V                            |                         |
-# SOMETHING-DEVICE-SPECIFIC         *-------------------------+
-#      |                                          |
-#      |                                          |
-#      V                                          |
-#    backend >------------------------------------+
-#      |
-#      |
-#      V
-#    THE PRINTER
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
    #########################################################################
-#
-# And this is how it works for CUPS from 1.1.15:
-# ==============================================
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      |
-#      V
-#     somethingtops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#     pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-#                                     |
-#                  +------------------v------------------------------+
-#                  | Ghostscript                                     |
-#                  | at work...                                      |
-#                  | (with                                           |
-#                  | "-sDEVICE=cups")                                |
-#                  |                                                 |
-#                  |         (= "postscipt interpreter")             |
-#                  |                                                 |
-#                  +------------------v------------------------------+
-#                                     |
-#                                     |
-# APPLICATION/VND.CUPS-RASTER >-------+
-#      |
-#      |
-#      V
-#     rastertosomething
-#      |   (= "raster driver")
-#      |
-#      V
-# SOMETHING-DEVICE-SPECIFIC
-#      |
-#      |
-#      V
-#     backend
-#
-#
-# NOTE: since version 1.1.15 CUPS "outsourced" the pstoraster process to
-#       Ghostscript. GNU Ghostscript needs to be patched to handle the
-#       CUPS requirement; ESP Ghostscript has this builtin. In any case,
-#       "gs -h" needs to show up a "cups" device. pstoraster is now a
-#       calling an appropriate "gs -sDEVICE=cups..." commandline to do
-#       the job. It will output "application/vnd.cup-raster", which will
-#       be finally processed by a CUPS raster driver "rastertosomething"
-#       Note the difference to "cupsomatic", which will *not* output
-#       CUPS-raster, but a final version of the printfile, ready to be
-#       sent to the printer. cupsomatic also doesn't use the "cups"
-#       devicemode in Ghostscript, but one of the classical devicemodes....
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
    #########################################################################
-#
-# And this is how it works for CUPS from 1.1.15, with cupsomatic included:
-# ========================================================================
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      |
-#      V
-#     somethingtops
-#      |
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      |
-#      V
-#     pstops
-#      |
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-#                                     |
-#                  +------------------v------------------------------+
-#                  | Ghostscript        . Ghostscript at work....    |
-#                  | at work...         . (with "-sDEVICE=           |
-#                  | (with              .            Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists
    11.1. Viewing and changing UNIX permissions using the NT 
+	security dialogs
    Windows NT clients can use their native security settings 
+	dialog box to view and modify the underlying UNIX permissions.
    Note that this ability is careful not to compromise 
+	the security of the UNIX host Samba is running on, and 
+	still obeys all the file permission rules that a Samba 
+	administrator can set.
    	All access to Unix/Linux system file via Samba is controlled at
+	the operating system file access control level. When trying to
+	figure out file access problems it is vitally important to identify
+	the identity of the Windows user as it is presented by Samba at
+	the point of file access. This can best be determined from the
+	Samba log files.
+	
    11.2. How to view file security on a Samba share
    From an NT4/2000/XP client, single-click with the right 
+	mouse button on any file or directory in a Samba mounted 
+	drive letter or UNC path. When the menu pops-up, click 
+	on the Properties entry at the bottom of 
+	the menu. This brings up the file properties dialog
+	box. Click on the tab Security and you 
+	will see three buttons, Permissions, 	
+	Auditing, and Ownership. 
+	The Auditing button will cause either 
+	an error message A requested privilege is not held 
+	by the client to appear if the user is not the 
+	NT Administrator, or a dialog which is intended to allow an 
+	Administrator to add auditing requirements to a file if the 
+	user is logged on as the NT Administrator. This dialog is 
+	non-functional with a Samba share at this time, as the only 
+	useful button, the Add button will not currently 
+	allow a list of users to be seen.
    11.3. Viewing file ownership
    Clicking on the "Ownership" button 
+	brings up a dialog box telling you who owns the given file. The 
+	owner name will be of the form :
    "SERVER\user (Long name)"
    Where s.th."        |
-#                  | "-sDEVICE=cups")   .                            |
-#                  |                    .                            |
-#                  | (CUPS standard)    .      (cupsomatic)          |
-#                  |                    .                            |
-#                  |          (= "postscript interpreter")           |
-#                  |                    .                            |
-#                  +------------------v--------------v---------------+
-#                                     |              |
-#                                     |              |
-# APPLICATION/VND.CUPS-RASTER >-------+              |
-#      |                                             |
-#      |                                             |
-#      V                                             |
-#     rastertoSERVER is the NetBIOS name of 
+	the Samba server, something                            |
-#      |   (= "raster driver")                       |
-#      |                                             |
-#      V                                             |
-# SOMETHING-DEVICE-SPECIFIC >------------------------+
-#      |
-#      |
-#      V
-#     backend
-#
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertouser is the user name of 
+	the UNIX user who owns the file, and something is noted.
-#
-##########################################################################
    (Long name) + is the descriptive string identifying the user (normally found in the + GECOS field of the UNIX password database). Click on the Close + button to remove this dialog.

    If the parameter nt acl support + is set to false then the file owner will + be shown as the NT user "Everyone".

    The Take Ownership button will not allow + you to change the ownership of this file to yourself (clicking on + it will display a dialog box complaining that the user you are + currently logged onto the NT client cannot be found). The reason + for this is that changing the ownership of a file is a privileged + operation in UNIX, available only to the root + user. As clicking on this button causes NT to attempt to change + the ownership of a file to the current user logged into the NT + client this will not work with Samba at this time.

    There is an NT chown command that will work with Samba + and allow a user with Administrator privilege connected + to a Samba server as root to change the ownership of + files on both a local NTFS filesystem or remote mounted NTFS + or Samba drive. This is available as part of the Seclib + NT security library written by Jeremy Allison of + the Samba Team, available from the main Samba ftp site.

    13.9. CUPS Print Drivers and Devices11.4. Viewing file or directory permissions

    CUPS ships with good support for HP LaserJet type printers. You can install -the driver as follows: - -

    The third button is the "Permissions" + button. Clicking on this brings up a dialog box that shows both + the permissions and the UNIX owner of the file or directory. + The owner is displayed in the form :

    "SERVER\user (Long name)"

    • lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd -

    Where SERVER is the NetBIOS name of + the Samba server, user is the user name of + the UNIX user who owns the file, and (Long name) - -(The "-m" switch will retrieve the "laserjet.ppd" from the standard repository -for not-yet-installed-PPDs, which CUPS typically stores in -/usr/share/cups/model. Alternatively, you may use -"-P /absolute/filesystem/path/to/where/there/is/PPD/your.ppd").

    If the parameter nt acl support + is set to false then the file owner will + be shown as the NT user "Everyone" and the + permissions will be shown as NT "Full Control".

    The permissions field is displayed differently for files + and directories, so I'll describe the way file permissions + are displayed first.

    11.4.1. File Permissions

    The standard UNIX user/group/world triple and + the corresponding "read", "write", "execute" permissions + triples are mapped by Samba into a three element NT ACL + with the 'r', 'w', and 'x' bits mapped into the corresponding + NT permissions. The UNIX world permissions are mapped into + the global NT group Everyone, followed + by the list of permissions allowed for UNIX world. The UNIX + owner and group permissions are displayed as an NT + user icon and an NT local + group icon respectively followed by the list + of permissions allowed for the UNIX user and group.

    As many UNIX permission sets don't map into common + NT names such as "read", "change" or "full control" then + usually the permissions will be prefixed by the words "Special Access" in the NT display list.

    But what happens if the file has no permissions allowed + for a particular UNIX user group or world component ? In order + to allow "no permissions" to be seen and modified then Samba + overloads the NT "Take Ownership" ACL attribute + (which has no meaning in UNIX) and reports a component with + no permissions as having the NT "O" bit set. + This was chosen of course to make it look like a zero, meaning + zero permissions. More details on the decision behind this will + be given below.

    13.9.1. Further printing steps11.4.2. Directory Permissions

    Always also consult the database on linuxprinting.org for all recommendations -about which driver is best used for each printer:

    http://www.linuxprinting.org/printer_list.cgi

    There select your model and click on "Show". You'll arrive at a page listing -all drivers working with your model. There will always be *one* -recommended one. Try this one first. In your case -("HP LaserJet 4 Plus"), you'll arrive here:

    http://www.linuxprinting.org/show_printer.cgi?recnum=75104

    Directories on an NT NTFS file system have two + different sets of permissions. The first set of permissions + is the ACL set on the directory itself, this is usually displayed + in the first set of parentheses in the normal "RW" + NT style. This first set of permissions is created by Samba in + exactly the same way as normal file permissions are, described + above, and is displayed in the same way.

    The recommended driver is "ljet4". It has a link to the page for the ljet4 -driver too:

    The second set of directory permissions has no real meaning + in the UNIX permissions world and represents the "inherited" permissions that any file created within + this directory would inherit.

    Samba synthesises these inherited permissions for NT by + returning as an NT ACL the UNIX permission mode that a new file + created by Samba on this share would receive.

    http://www.linuxprinting.org/show_driver.cgi?driver=ljet4

    On the driver's page, you'll find important and detailed info about how to use -that driver within the various available spoolers. You can generate a PPD for -CUPS. The PPD contains all the info about how to use your model and the driver; -this is, once installed, working transparently for the user -- you'll only -need to choose resolution, paper size etc. from the web-based menu or from -the print dialog GUI or from the commandline...

    On the driver's page, choose to use the "PPD-O-Matic" online PPD generator -program. Select your model and click "Generate PPD file". When you safe the -appearing ASCII text file, don't use "cut'n'past" (as it could possiblly corrupt -line endings and tabs), but use "Save as..." in your browser's menu. Save it -at "/some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"

    Then install the printer:

        "lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E \
-          -P /some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"

    Note, that for all the "Foomatic-PPDs" from Linuxprinting.org, you also need -a special "CUPS filter" named "cupsomatic". Get the latest version of -"cupsomatic" from:

    11.5. Modifying file or directory permissions

    http://www.linuxprinting.org/cupsomatic

    Modifying file and directory permissions is as simple + as changing the displayed permissions in the dialog box, and + clicking the OK button. However, there are + limitations that a user needs to be aware of, and also interactions + with the standard Samba permission masks and mapping of DOS + attributes that need to also be taken into account.

    This needs to be copied to /usr/lib/cups/filter/cupsomaticIf the parameter nt acl support -and be made world executable. This filter is needed to read and act upon the -specially encoded Foomatic comments, embedded in the printfile, which in turn -are used to construct (transparently for you, the user) the complicated -ghostscript command line needed for your printer/driver combo.

    false then any attempt to set + security permissions will fail with an "Access Denied" + message.

    You can have a look at all the options for the Ghostscript commandline supported -by your printer and the ljet4 driver by going to the section "Execution details", -selecting your model (Laserjet 4 Plus) and clicking on "Show execution details". -This will bring up this web page:

    The first thing to note is that the "Add" + button will not return a list of users in Samba (it will give + an error message of "The remote procedure call failed + and did not execute"). This means that you can only + manipulate the current user/group/world permissions listed in + the dialog box. This actually works quite well as these are the + only permissions that UNIX actually has.

    http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details

    If a permission triple (either user, group, or world) + is removed from the list of permissions in the NT dialog box, + then when the "OK" button is pressed it will + be applied as "no permissions" on the UNIX side. If you then + view the permissions again the "no permissions" entry will appear + as the NT "O" flag, as described above. This + allows you to add permissions back to a file or directory once + you have removed them from a triple component.

    The ingenious thing is that the database is kept current. If there -is a bug fix and an improvement somewhere in the database, you will -always get the most current and stable and feature-rich driver by following -the steps described above.

    As UNIX supports only the "r", "w" and "x" bits of + an NT ACL then if other NT security attributes such as "Delete + access" are selected then they will be ignored when applied on + the Samba server.

    When setting permissions on a directory the second + set of permissions (in the second set of parentheses) is + by default applied to all files within that directory. If this + is not what you want you must uncheck the "Replace + permissions on existing files" checkbox in the NT + dialog before clicking "OK".

    Till Kamppeter from MandrakeSoft is doing an excellent job here that too few -people are aware of. (So if you use it often, please send him a note showing -your appreciation).

    If you wish to remove all permissions from a + user/group/world component then you may either highlight the + component and click the "Remove" button, + or set the component to only have the special "Take + Ownership" permission (displayed as "O" + ) highlighted.

    11.6. Interaction with the standard Samba create mask + parameters

    The latest and greatest improvement now is support for "custom page sizes" -for all those printers which support it.

    "cupsomatic" is documented here:

    http://www.linuxprinting.org/cups-doc.html

    More printing tutorial info may be found here:

    http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/

    Note, that *all* the Foomatic drivers listed on Linuxprinting.org (now -approaching the "all-time high" number of 1.000 for the supported models) -are using a special filtering chain involving Ghostscript, as described -in this document.

    Summary - You need:

    There are four parameters + to control interaction with the standard Samba create mask parameters. + These are :

    security mask

    A "foomatic+something" PPD is not enough to print with CUPS (but it is *one* important component)
    The "cupsomatic" filter script (Perl) in /usr/lib/cups/filters/
    Perl to make cupsomatic run
    Ghostscript (because it is called and controlled by the PPD/cupsomatic combo in a way to fit your printermodel/driver combo.
    Ghostscript *must*, depending on the driver/model, contain support for a certain "device" (as shown by "gs -h")

    force security mode

    In the case of the "hpijs" driver, you need a Ghostscript version, which -has "ijs" amongst its supported devices in "gs -h". In the case of -"hpijs+foomatic", a valid ghostscript commandline would be reading like this:

           gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs       \
-             -sIjsServer=hpijsPageSize -dDuplex=Duplex Model        \
-             -rResolution,PS:MediaPosition=InputSlot -dIjsUseOutputFD \
-             -sOutputFile=- -
    directory security mask

    force directory security mode

    Note, that with CUPS and the "hpijs+foomatic" PPD (plus Perl and cupsomatic) -you don't need to remember this. You can choose the available print options -thru a GUI print command (like "glp" from ESP's commercially supported -PrintPro software, or KDE's "kprinter", or GNOME's "gtklp" or the independent -"xpp") or the CUPS web interface via human-readable drop-down selection -menus.

    If you use "ESP Ghostscript" (also under the GPL, provided by Easy Software -Products, the makers of CUPS, downloadable from -Once a user clicks "OK" to apply the + permissions Samba maps the given permissions into a user/group/world + r/w/x triple set, and then will check the changed permissions for a + file against the bits set in the http://www.cups.org/software.html, -co-maintained by the developers of linuxprinting.org), you are guaranteed to -have in use the most uptodate, bug-fixed, enhanced and stable version of a Free -Ghostscript. It contains support for ~300 devices, whereas plain vanilla -GNU Ghostscript 7.05 only has ~200.

    + security mask parameter. Any bits that + were changed that are not set to '1' in this parameter are left alone + in the file permissions.

    If you print only one CUPS test page, from the web interface and when you try to -print a windows test page, it acts like the job was never sent: - -

    Can you print "standard" jobs from the CUPS machine?
    Are the jobs from Windows visible in the Web interface on CUPS (http://localhost:631/)?
    Essentially, zero bits in the security mask + mask may be treated as a set of bits the user is Most important:not What kind of printer driver are you using on the Windows clients?
    + allowed to change, and one bits are those the user is allowed to change. +

    If not set explicitly this parameter is set to the same value as + the create mask + parameter. To allow a user to modify all the + user/group/world permissions on a file, set this parameter + to 0777.

    Next Samba checks the changed permissions for a file against + the bits set in the force security mode parameter. Any bits + that were changed that correspond to bits set to '1' in this parameter + are forced to be set.

    Essentially, bits set in the force security mode + parameter 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 force + create mode parameter. + To allow a user to modify all the user/group/world permissions on a file + with no restrictions set this parameter to 000.

    The security mask and force + security mode parameters are applied to the change + request in that order.

    For a directory Samba will perform the same operations as + described above for a file except using the parameter directory security mask instead of security + mask, and force directory security mode + parameter instead of force security mode + .

    The directory security mask parameter + by default is set to the same value as the directory mask + parameter and the force directory security + mode parameter by default is set to the same value as + the force directory mode parameter.

    In this way Samba enforces the permission restrictions that + an administrator can set on a Samba share, whilst still allowing users + to modify the permission bits within that restriction.

    - -You can try to get a more detailed debugging info by setting "LogLevel debug" in -/etc/cups/cupsd.conf, re-start cupsd and investigate If you want to set up a share that allows users full control + in modifying the permission bits on their files and directories and + doesn't force any particular bits to be set 'on', then set the following + parameters in the /var/log/cups/error_log -for the whereabouts of your Windows-originating printjobs:

    smb.conf     file in that share specific section :

    security mask = 0777

    force security mode = 0

    what does the "auto-typing" line say? which is the "MIME type" CUPS thinks is arriving from the Windows clients?
    are there "filter" available for this MIME type?
    are there "filter rules" defined in "/etc/cups/mime.convs" for this MIME type?

    directory security mask = 0777

    force directory security mode = 0

    13.10. Limiting the number of pages users can print11.7. Interaction with the standard Samba file attribute + mapping

    The feature you want is dependent on the real print subsystem you're using. -Samba's part is always to receive the job files from the clients (filtered -*or* unfiltered) and hand it over to this printing subsystem.

    Samba maps some of the DOS attribute bits (such as "read + only") into the UNIX permissions of a file. This means there can + be a conflict between the permission bits set via the security + dialog and the permission bits set by the file attribute mapping. +

    Of course one could "hack" things with one's own scripts.

    One way this can show up is if a file has no UNIX read access + for the owner it will show up as "read only" in the standard + file attributes tabbed dialog. Unfortunately this dialog is + the same one that contains the security info in another tab.

    But there is CUPS (Common Unix Printing System). CUPS supports "quotas". -Quotas can be based on sizes of jobs or on the number of pages or both, -and are spanning any time period you want.

    What this can mean is that if the owner changes the permissions + to allow themselves read access using the security dialog, clicks + "OK" to get back to the standard attributes tab + dialog, and then clicks "OK" on that dialog, then + NT will set the file permissions back to read-only (as that is what + the attributes still say in the dialog). This means that after setting + permissions and clicking "OK" to get back to the + attributes dialog you should always hit "Cancel" + rather than "OK" to ensure that your changes + are not overridden.

    Chapter 12. Configuring Group Mapping

    This is an example command how root would set a print quota in CUPS, -assuming an existing printer named "quotaprinter":

      lpadmin -p quotaprinter -o job-quota-period=604800 -o job-k-limit=1024 \
-       -o job-page-limit=100
    +Starting with Samba 3.0 alpha 2, a new group mapping function is available. The +current method (likely to change) to manage the groups is a new command called +smbgroupedit.

    This would limit every single user to print 100 pages or 1024 KB of -data (whichever comes first) within the last 604.800 seconds ( = 1 week).

    The first immediate reason to use the group mapping on a PDC, is that +the domain admin group of smb.conf is +now gone. This parameter was used to give the listed users local admin rights +on their workstations. It was some magic stuff that simply worked but didn't +scale very well for complex setups.

    For CUPS to count correctly, the printfile needs to pass the CUPS "pstops" filter, -otherwise it uses a "dummy" count of "1". Some printfiles don't pass it -(eg: image files) but then those are mostly 1 page jobs anyway. This also means, -proprietary drivers for the target printer running on the client computers and -CUPS/Samba then spooling these files as "raw" (i.e. leaving them untouched, not -filtering them), will be counted as "1-pagers" too!

    Let me explain how it works on NT/W2K, to have this magic fade away. +When installing NT/W2K on a computer, the installer program creates some users +and groups. Notably the 'Administrators' group, and gives to that group some +privileges like the ability to change the date and time or to kill any process +(or close too) running on the local machine. The 'Administrator' user is a +member of the 'Administrators' group, and thus 'inherit' the 'Administrators' +group privileges. If a 'joe' user is created and become a member of the +'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.

    When a NT/W2K machine is joined to a domain, during that phase, the "Domain +Administrators' group of the PDC is added to the 'Administrators' group of the +workstation. Every members of the 'Domain Administrators' group 'inherit' the +rights of the 'Administrators' group when logging on the workstation.

    You are now wondering how to make some of your samba PDC users members of the +'Domain Administrators' ? That's really easy.

    1. create a unix group (usually in /etc/group), let's call it domadm

    2. add to this group the users that must be Administrators. For example if you want joe,john and mary, your entry in /etc/group will look like:

      You need to send PostScript from the clients (i.e. run a PostScript driver there) -for having the chance to get accounting done. If the printer is a non-PostScript model, -you need to let CUPS do the job to convert the file to a print-ready format for the -target printer. This will be working for currently ~1.000 different printer models, see

           http://www.linuxprinting.org/printer_list.cgi
      domadm:x:502:joe,john,mary

    3. Before CUPS-1.1.16 your only option was to use the Adobe PostScript -Driver on the Windows clients. The output of this driver was not always -passed thru the "pstops" filter on the CUPS/Samba side, and therefor was -not counted correctly (the reason is that it often --- depending on the -"PPD" being used --- did write a "PJL"-header in front of the real -PostScript which made CUPS to skip the pstops and go directy to -the "pstoraster" stage).

      Map this domadm group to the domain admins group by running the command:

      From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver -for Windows NT/2K/XP clients" (it is tagged in the download area of -http://www.cups.org/ as the "cups-samba-1.1.16.tar.gz" package). -It is *not* working for Win9x/ME clients. But it:

      smbgroupedit -c "Domain Admins" -u domadm

    You're set, joe, john and mary are domain administrators !

    Like the Domain Admins group, you can map any arbitrary Unix group to any NT +group. You can also make any Unix group a domain group. For example, on a domain +member machine (an NT/W2K or a samba server running winbind), you would like to +give access to a certain directory to some users who are member of a group on +your samba PDC. Flag that group as a domain group by running:

    smbgroupedit -a unixgroup -td

    it guarantees to not write an PJL-header
    it guarantees to still read and support all PJL-options named in the driver PPD with its own means
    it guarantees the file going thru the "pstops" filter on the CUPS/Samba server
    it guarantees to page-count correctly the printfile

    You can list the various groups in the mapping database like this

    smbgroupedit -v

    Chapter 13. Printing Support

    13.1. Introduction

    Beginning with the 2.2.0 release, Samba supports +the native Windows NT printing mechanisms implemented via +MS-RPC (i.e. the SPOOLSS named pipe). Previous versions of +Samba only supported LanMan printing calls.

    The additional functionality provided by the new +SPOOLSS support includes:

    • You can read more about the setup of this combination in the -manpage for "cupsaddsmb" (only present with CUPS installed, only -current with CUPS 1.1.16).

      Support for downloading printer driver + files to Windows 95/98/NT/2000 clients upon demand. +

    • These are the items CUPS logs in the "page_log" for every single *page* of a job:

      Uploading of printer drivers via the + Windows NT Add Printer Wizard (APW) or the + Imprints tool set (refer to http://imprints.sourceforge.net). +

    • Support for the native MS-RPC printing + calls such as StartDocPrinter, EnumJobs(), etc... (See + the MSDN documentation at http://msdn.microsoft.com/ + for more information on the Win32 printing API) +

    • Printer name
      User name
      Job ID
      Time of printing
      the page number
      the number of copies
      a billing info string (optional)
      Support for NT Access Control Lists (ACL) + on printer objects

    • Improved support for printer queue manipulation + through the use of an internal databases for spooled job + information

    Here is an extract of my CUPS server's page_log file to illustrate -the format and included items:

    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. As a side note, Samba does not use these drivers in any way to process +spooled files. They are utilized entirely by the clients.

    infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 1 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 2 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 3 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 4 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 5 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 6 2 #marketingThe following MS KB article, may be of some help if you are dealing with +Windows 2000 clients: How to Add Printers with No User +Interaction in Windows 2000

    This was Job ID "40", printed on "infotec_IS2027" by user "kurt", a 6-page job -printed in 2 copies and billed to "#marketing"...

    What flaws or shortcomings are there?

    http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP

    13.2. Configuration

     

    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.

    However, the initial implementation allowed for a +parameter named printer driver location +to be used on a per share basis to specify the location of +the driver files associated with that printer. Another +parameter named printer driver provided +a means of defining the printer driver name to be sent to +the client.

    the ones named above
    CUPS really counts the job pages being *processsed in software* - (going thru the "RIP") rather than the physical sheets successfully - leaving the printing device -- if there is a jam while printing - the 5th sheet out of 1000 and the job is aborted by the printer, - the "page count" will still show the figure of 1000 for that job -
    all quotas are the same for all users (no flexibility to give the - boss a higher quota than the clerk) no support for groups -
    no means to read out the current balance or "used-up" number of current quota - [print$] vs. [printer$]
    a user having used up 99 sheets of 100 quota will still be able to send and print a 1.000 sheet job -
    a user being denied a job because of a filled-up quota doesn't get a meaningful - error message from CUPS other than "client-error-not-possible". -

    13.2.1. Creating [print$]

    In order to support the uploading of printer driver +files, you must first configure a file share named [print$]. +The name of this share is hard coded in Samba's internals so +the name is very important (print$ is the service used by +Windows NT print servers to provide support for printer driver +download).

    You should modify the server's smb.conf file to add the global +parameters and to create the +following file share (of course, some of the parameter values, +such as 'path' are arbitrary and should be replaced with +appropriate values for your site):

    [global]
+    ; members of the ntadmin group should be able
+    ; to add drivers and set printer properties
+    ; root is implicitly a 'printer admin'
+    printer admin = @ntadmin
+
+[print$]
+    path = /usr/local/samba/printers
+    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,root

    But this is the best system out there currently. And there are -huge improvements under development:

    The write list is used to allow administrative +level user accounts to have write access in order to update files +on the share. See the smb.conf(5) +man page for more information on configuring file shares.

    The requirement for guest +ok = yes 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.

     
    page counting will go into the "backends" (these talk - directly to the printer and will increase the count in sync with the - actual printing process -- a jam at the 5th sheet will lead to a stop in the counting)
    quotas will be handled more flexiblyAuthor's Note
    probably there will be support for users to inquire their "accounts" in advance
    probably there will be support for some other tools around this topic

    Other than the current stage of the CUPS development, I don't -know any other ready-to-use tool which you could consider.

    You can download the driver files from -The non-issue is that if all your Windows NT users are guaranteed to be +authenticated by the Samba server (such as a domain member server and the NT +user has already been validated by the Domain Controller in +order to logon to the Windows NT console), then guest access +is not necessary. Of course, in a workgroup environment where +you just want to be able to print without worrying about +silly accounts and security, then configure the share for +guest access. You'll probably want to add http://www.cups.org/software.html. -It is a separate package from the CUPS base software files, tagged as "CUPS 1.1.16 -Windows NT/2k/XP Printer Driver for SAMBA (tar.gz, 192k)". The filename to -download is "cups-samba-1.1.16.tar.gz". Upon untar-/unzip-ping it will reveal -the files:

    map to guest = Bad User in the [global] section as well. Make sure +you understand what this parameter does before using it +though. --jerry

    cups-samba.install - cups-samba.license - cups-samba.readme - cups-samba.remove - cups-samba.ss - -

    In order for a Windows NT print server to support +the downloading of driver files by multiple client architectures, +it must create subdirectories within the [print$] service +which correspond to each of the supported client architectures. +Samba follows this model as well.

    These have been packaged with the ESP meta packager software "EPM". The -*.install and *.remove files are simple shell script, which untars the -*.ss (which is nothing else than a tar-archive) and puts its contents -into /usr/share/cups/drivers/. Its contents are 3 files:

    Next create the directory tree below the [print$] share +for each architecture you wish to support.

    cupsdrvr.dll - cupsui.dll - cups.hlp - -

    [print$]----- + |-W32X86 ; "Windows NT x86" + |-WIN40 ; "Windows 95/98" + |-W32ALPHA ; "Windows NT Alpha_AXP" + |-W32MIPS ; "Windows NT R4000" + |-W32PPC ; "Windows NT PowerPC"

    ATTENTION! REQUIRED PERMISSIONS
     

    Due to a bug one CUPS release puts the cups.hlpIn order to currently add a new driver to you Samba host, +one of two conditions must hold true:

    • The account used to connect to the Samba host + must have a uid of 0 (i.e. a root account)

    • The account used to connect to the Samba host + must be a member of the printer + admin list.

    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.

    Once you have created the required [print$] service and +associated subdirectories, simply log onto the Samba server using +a root (or printer admin) account +from a Windows NT 4.0/2k client. Open "Network Neighbourhood" or +"My Network Places" and browse for the Samba host. Once you have located +the server, navigate to the "Printers..." folder. +You should see an initial listing of printers +that matches the printer shares defined on your Samba host.

    13.2.2. Setting Drivers for Existing Printers

    The initial listing of printers in the Samba host's +Printers folder will have no real printer driver assigned +to them. This defaults to a NULL string to allow the use +of 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:

    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?

    Click "No" in the error dialog and you will be presented with +the printer properties window. The way to assign a driver to a +printer is to either

    • Use the "New Driver..." button to install + a new printer driver, or

    • Select a driver from the popup list of + installed drivers. Initially this list will be empty.

    If you wish to install printer drivers for client +operating systems other than "Windows NT x86", you will need +to use the "Sharing" tab of the printer properties dialog.

    Assuming you have connected with a root account, you +will also be able modify other printer properties such as +ACLs and device settings using this dialog box.

    A few closing comments for this section, it is possible +on a Windows NT print server to have printers +listed in the Printers folder which are not shared. Samba does +not make this distinction. By definition, the only printers of +which Samba is aware are those which are specified as shares in +smb.conf.

    Another interesting side note is that Windows NT clients do +not use the SMB printer share, but rather can print directly +to any printer on another Windows NT host using MS-RPC. This +of course assumes that the printing client has the necessary +privileges on the remote host serving the printer. The default +permissions assigned by Windows NT to a printer gives the "Print" +permissions to the "Everyone" well-known group.

    13.2.3. Support a large number of printers

    One issue that has arisen during the development +phase of Samba 2.2 is the need to support driver downloads for +100's of printers. Using the Windows NT APW is somewhat +awkward to say the list. If more than one printer are using the +same driver, the rpcclient's +setdriver command can be used to set the driver +associated with an installed driver. The following is example +of how this could be accomplished:

    $ rpcclient pogo -U root%secret -c "enumdrivers" -into /usr/share/drivers/ instead of -/usr/share/cups/drivers/. To work around this, copy/move -the file after running the "./cups-samba.install" script manually to the right place:

    +Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] + +[Windows NT x86] +Printer Driver Info 1: + Driver Name: [HP LaserJet 4000 Series PS] + +Printer Driver Info 1: + Driver Name: [HP LaserJet 2100 Series PS] + +Printer Driver Info 1: + Driver Name: [HP LaserJet 4Si/4SiMX PS] +$ cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/ - rpcclient pogo -U root%secret -c "enumprinters" -

    Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3] + flags:[0x800000] + name:[\\POGO\hp-print] + description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,] + comment:[] + +$ rpcclient pogo -U root%secret -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.

    This new CUPS PostScript driver is currently binary-only, but free -no source code is provided (yet). The reason is this: it has -been developed with the help of the Microsoft Driver Developer Kit (DDK) -and compiled with Microsoft Visual Studio 6. It is not clear to the driver -developers if they are allowed to distribute the whole of the source code -as Free Software. However, they will likely release the "diff" in source -code under the GPL, so anybody with a license of Visual Studio and a DDK -will be able to compile for him/herself.

    Once you have run the install script (and possibly manually moved the -"cups.hlp" file to "/usr/share/cups/drivers/"), the driver is ready to be -put into Samba's [print$] share (which often maps to "/etc/samba/drivers/" -and contains a subdir tree with WIN40 and W32X86 branches), by running -"cupsaddsmb" (see also "man cupsaddsmb" for CUPS 1.1.16). [Don't forget to -put root into the smbpasswd file by running "smbpasswd" should you run -this whole procedure for the first time.] Once the driver files are in the -[print$] share, they are ready to be downloaded and installed by the -Win NT/2k/XP clients.

    13.2.4. Adding New Printers via the Windows NT APW

    By default, Samba offers all printer shares defined in smb.conf +in the "Printers..." folder. Also existing in this folder is the Windows NT +Add Printer Wizard icon. The APW will be show only if

    • Win 9x/ME clients won't work with this driver. For these you'd - still need to use the ADOBE*.* drivers as previously. +>The connected user is able to successfully + execute an OpenPrinterEx(\\server) with administrative + privileges (i.e. root or printer admin).

  • It is not harming if you've still the ADOBE*.* driver files from - previous installations in the "/usr/share/cups/drivers/" directory. - The new cupsaddsmb (from 1.1.16) will automatically use the - "newest" installed driver (which here then is the CUPS drivers). +>show + add printer wizard = yes (the default).

    • In order to be able to use the APW to successfully add a printer to a Samba +server, the add +printer command must have a defined value. The program +hook must successfully add the printer to the system (i.e. +/etc/printcap or appropriate files) and +smb.conf if necessary.

    When using the APW from a client, if the named printer share does +not exist, smbd will execute the add printer +command and reparse to the smb.conf +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 +add printer program is executed under the context +of the connected user, not necessarily a root account.

    Should your Win clients have had the old ADOBE*.* files and the - Adobe PostScript drivers installed, the download and installation - of the new CUPS PostScript driver for Windows NT/2k/XP will fail - at first. -

    There is a complementary delete +printer command for removing entries from the "Printers..." +folder.

    It is not enough to "delete" the printer (as the driver files - will still be kept by the clients and re-used if you try to - re-install the printer). To really get rid of the Adobe driver - files on the clients, open the "Printers" folder (possibly via - "Start --> Settings --> Control Panel --> Printers"), right-click - onto the folder background and select "Server Properties". A - new dialog opens; select the "Drivers" tab; on the list select - the driver you want to delete and click on the "Delete" button. - (This will only work if there is no single printer left which - uses that particular driver -- you need to "delete" all printers - using this driver in the "Printers" folder first.) -

    The following is an example add printer command script. It adds the appropriate entries to /etc/printcap.local (change that to what you need) and returns a line of 'Done' which is needed for the whole process to work.

    #!/bin/sh
+
+# Script to insert a new printer entry into printcap.local
+#
+# $1, printer name, used as the descriptive name
+# $2, share name, used as the printer name for Linux
+# $3, port name
+# $4, driver name
+# $5, location, used for the device file of the printer
+# $6, win9x location
+
+#
+# Make sure we use the location that RedHat uses for local printer defs
+PRINTCAP=/etc/printcap.local
+DATE=`date +%Y%m%d-%H%M%S`
+LP=lp
+RESTART="service lpd restart"
+
+# Keep a copy
+cp $PRINTCAP $PRINTCAP.$DATE
+# Add the printer to $PRINTCAP
+echo ""				 			>> $PRINTCAP
+echo "$2|$1:\\" 					>> $PRINTCAP
+echo "  :sd=/var/spool/lpd/$2:\\" 			>> $PRINTCAP
+echo "  :mx=0:ml=0:sh:\\" 				>> $PRINTCAP
+echo "  :lp=/usr/local/samba/var/print/$5.prn:" 	>> $PRINTCAP
+
+touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1
+chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1
+
+mkdir /var/spool/lpd/$2
+chmod 700 /var/spool/lpd/$2
+chown $LP /var/spool/lpd/$2
+#echo $1 >> "/usr/local/samba/var/print/$5.prn"
+#echo $2 >> "/usr/local/samba/var/print/$5.prn"
+#echo $3 >> "/usr/local/samba/var/print/$5.prn"
+#echo $4 >> "/usr/local/samba/var/print/$5.prn"
+#echo $5 >> "/usr/local/samba/var/print/$5.prn"
+#echo $6 >> "/usr/local/samba/var/print/$5.prn"
+$RESTART >> "/usr/local/samba/var/print/$5.prn"
+# Not sure if this is needed
+touch /usr/local/samba/lib/smb.conf
+#
+# You need to return a value, but I am not sure what it means.
+#
+echo "Done"
+exit 0

    13.2.5. Samba and Printer Ports

    Windows NT/2000 print servers associate a port with each printer. These normally +take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the +concept of ports associated with a printer. By default, only one printer port, +named "Samba Printer Port", exists on a system. Samba does not really a port in +order to print, rather it is a requirement of Windows clients.

    Once you have successfully downloaded the CUPS PostScript driver - to a client, you can easily switch all printers to this one - by proceeding as described elsewhere in the "Samba HOWTO - Collection" to change a driver for an existing printer. -

    Note that Samba does not support the concept of "Printer Pooling" internally +either. This is when a logical printer is assigned to multiple ports as +a form of load balancing or fail over.

    If you require that multiple ports be defined for some reason, +smb.conf possesses a enumports +command which can be used to define an external program +that generates a listing of ports on a system.

    13.3. The Imprints Toolset

    What are the benefits with the "CUPS PostScript driver for Windows NT/2k/XP" -as compared to the Adobe drivers?

    The Imprints tool set provides a UNIX equivalent of the + Windows NT Add Printer Wizard. For complete information, please + refer to the Imprints web site at http://imprints.sourceforge.net/ as well as the documentation + included with the imprints source distribution. This section will + only provide a brief introduction to the features of Imprints.

    13.3.1. What is Imprints?

    Imprints is a collection of tools for supporting the goals + of

    • no hassle with the Adobe EULA -

      Providing a central repository information + regarding Windows NT and 95/98 printer driver packages

    • no hassle with the question "where do I get the ADOBE*.* driver files from?" -

      Providing the tools necessary for creating + the Imprints printer driver packages.

    • the Adobe drivers (depending on the printer PPD associated with them) - often put a PJL header in front of the core PostScript part of the print - file (thus the file starts with "1B%-12345X" or "escape%-12345X" - instead of "%!PS"). This leads to the CUPS daemon autotyping the - arriving file as a print-ready file, not requiring a pass thru the - "pstops" filter (to speak more technical, it is not regarded as the - generic MIME type "application/postscript", but as the more special - MIME type "application/cups.vnd-postscript"), which therefore also - leads to the page accounting in "/var/log/cups/page_log" not receiving - the exact mumber of pages; instead the dummy page number of "1" is - logged in a standard setup) -

      Providing an installation client which + will obtain and install printer drivers on remote Samba + and Windows NT 4 print servers.

    13.3.2. Creating Printer Driver Packages

    the Adobe driver has more options to "mis-configure" the PostScript - generated by it (like setting it inadvertedly to "Optimize for Speed", - instead of "Optimize for Portability", which could lead to CUPS being - unable to process it) -

  • The process of creating printer driver packages is beyond + the scope of this document (refer to Imprints.txt also included + with the Samba distribution for more information). In short, + an Imprints driver package is a gzipped tarball containing the + driver files, related INF files, and a control file needed by the + installation client.

    • 13.3.3. The Imprints server

    The Imprints server is really a database server that + may be queried via standard HTTP mechanisms. Each printer + entry in the database has an associated URL for the actual + downloading of the package. Each package is digitally signed + via GnuPG which can be used to verify that package downloaded + is actually the one referred in the Imprints database. It is + not recommended that this security check + be disabled.

    13.3.4. The Installation Client

    More information regarding the Imprints installation client + is available in the Imprints-Client-HOWTO.ps + file included with the imprints source package.

    the CUPS PostScript driver output sent by Windows clients to the CUPS - server will be guaranteed to be auto-typed as generic MIME type - "application/postscript", thusly passing thru the CUPS "pstops" filter - and logging the correct number of pages in the page_log for accounting - and quota purposes -

  • The Imprints installation client comes in two forms.

    the CUPS PostScript driver supports the sending of additional print - options by the Win NT/2k/XP clients, such as naming the CUPS standard - banner pages (or the custom ones, should they be installed at the time - of driver download), using the CUPS "page-label" option, setting a - job-priority and setting the scheduled time of printing (with the option - to support additional useful IPP job attributes in the future). -

    • the CUPS PostScript driver supports the inclusion of the new - "*cupsJobTicket" comments at the beginnig of the PostScript file (which - could be used in the future for all sort of beneficial extensions on - the CUPS side, but which will not disturb any other application as those - will regard it as a comment and simply ignore it). -

      a set of command line Perl scripts

    • the CUPS PostScript driver will be the heart of the fully fledged CUPS - IPP client for Windows NT/2k/XP to be released soon (probably alongside - the first Beta release for CUPS 1.2). -

      a GTK+ based graphical interface to + the command line perl scripts

    13.11. Advanced Postscript Printing from MS Windows

    Let the Windows Clients use a PostScript driver to deliver poistscript to -the samba print server (just like any Linux or Unix Client would also use -PostScript to send to the server)

    Make the Unix printing subsystem to which Samba sends the job convert the -incoming PostScript files to the native print format of the target printers -(would be PCL if you have an HP printer)

    Now if you are afraid that this would just mean using a *Generic* PostScript -driver for the clients that has no Simplex/Duplex selection, and no paper tray -choice, but you need them to be able to set up print jobs, with all the bells -and whistles of your printers:-

    The installation client (in both forms) provides a means + of querying the Imprints database server for a matching + list of known printer model names as well as a means to + download and install the drivers on remote Samba and Windows + NT print servers.

    Not possible with traditional spooling systems
    But perfectly supported by CUPS (which uses "PPD" files to - describe how to control the print options for PostScript and - non-PostScript devices alike... -
    The basic installation process is in four steps and + perl code is wrapped around smbclient + and rpcclient.

    	
+foreach (supported architecture for a given driver)
+{
+     1.  rpcclient: Get the appropriate upload directory 
+         on the remote server
+     2.  smbclient: Upload the driver files
+     3.  rpcclient: Issues an AddPrinterDriver() MS-RPC
+}
+	
+4.  rpcclient: Issue an AddPrinterEx() MS-RPC to actually
+    create the printer

    CUPS PPDs are working perfectly on Windows clients who use Adobe PostScript -drivers (or the new CUPS PostScript driver for Windows NT/2K/XP). Clients can use -them to setup the job to their liking and CUPS will use the received job options -to make the (PCL-, ESC/P- or PostScript-) printer behave as required.

    If you want to have the additional benefit of page count logging and accounting -then the CUPS PostScript driver is the best choice (better than the Adobe one).

    One of the problems encountered when implementing + the Imprints tool set was the name space issues between + various supported client architectures. For example, Windows + NT includes a driver named "Apple LaserWriter II NTX v51.8" + and Windows 95 calls its version of this driver "Apple + LaserWriter II NTX"

    If you want to make the drivers downloadable for the clients then "cupsaddsmb" is -your friend. It will setup the [print$] share on the Samba host to be ready to serve -the clients for a "point and print" driver installation.

    The problem is how to know what client drivers have + been uploaded for a printer. As astute reader will remember + that the Windows NT Printer Properties dialog only includes + space for one printer driver name. A quick look in the + Windows NT 4.0 system registry at

    HKLM\System\CurrentControlSet\Control\Print\Environment +

    What strings are attached?

    There are some. But, given the sheer CPU power you can buy nowadays, -these can be overcome easily. The strings:

    will reveal that Windows NT always uses the NT driver + 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 + already been installed?

    Well, if the CUPS/Samba side will have to print to many printers serving many users, -you probably will need to set up a second server (which can do automatic load balancing -with the first one, plus a degree of fail-over mechanism). Converting the incoming -PostScript jobs, "interpreting" them for non-PostScript printers, amounts to the work -of a "RIP" (Raster Image Processor) done in software. This requires more CPU and RAM -than for the mere "raw spooling" task your current setup is solving. It all depends -on the avarage and peak printing load the server should be able to handle.

    The way of sidestepping this limitation is to require + that all Imprints printer driver packages include both the Intel + Windows NT and 95/98 printer drivers and that NT driver is + installed first.

    13.12. Auto-Deletion of CUPS spool files13.4. Diagnosis

    13.4.1. Introduction

    Samba print files pass thru two "spool" directories. One the incoming directory -managed by Samba, (set eg: in the path = /var/spool/samba directive in the [printers] -section of smb.conf). Second is the spool directory of your UNIX print subsystem. -For CUPS it is normally "/var/spool/cups/", as set by the cupsd.conf directive -"RequestRoot /var/spool/cups".

    I am not sure, which one of your directories keeps the files. From what you say, -it is most likely the Samba part.

    This is a short description of how to debug printing problems with +Samba. This describes how to debug problems with printing from a SMB +client to a Samba server, not the other way around. For the reverse +see the examples/printing directory.

    For the CUPS part, you may want to consult:

    Ok, so you want to print to a Samba server from your PC. The first +thing you need to understand is that Samba does not actually do any +printing itself, it just acts as a middleman between your PC client +and your Unix printing subsystem. Samba receives the file from the PC +then passes the file to a external "print command". What print command +you use is up to you.

    http://localhost:631/sam.html#PreserveJobFiles
    http://localhost:631/sam.html#PreserveJobHistory
    http://localhost:631/sam.html#MaxJobs
    The whole things is controlled using options in smb.conf. The most +relevant options (which you should look up in the smb.conf man page) +are:

          [global]
+        print command     - send a file to a spooler
+        lpq command       - get spool queue status
+        lprm command      - remove a job
+      [printers]
+        path = /var/spool/lpd/samba

    There are the settings described for your CUPS daemon, which could lead to completed -job files not being deleted.

    "PreserveJobHistory Yes" -- keeps some details of jobs in -cupsd's mind (well it keeps the "c12345", "c12346" etc. files -in the CUPS spool directory, which do a similar job as the -old-fashioned BSD-LPD control files). This is set to "Yes" -as a default.

    "PreserveJobFiles Yes" -- keeps the job files themselves in -cupsd's mind (well it keeps the "d12345", "d12346" etc. files -in the CUPS spool directory...). This is set to "No" as the -CUPS default.

    "MaxJobs 500" -- this directive controls the maximum number -of jobs that are kept in memory. Once the number of jobs -reaches the limit, the oldest completed job is automatically -purged from the system to make room for the new one. If all -of the known jobs are still pending or active then the new -job will be rejected. Setting the maximum to 0 disables this -functionality. The default setting is 0.

    (There are also additional settings for "MaxJobsPerUser" and -"MaxJobsPerPrinter"...)

    For everything to work as announced, you need to have three things:

    The following are nice to know about:

            queuepause command   - stop a printer or print queue
+        queueresume command  - start a printer or print queue

    a Samba-smbd which is compiled against "libcups" (Check on Linux by running ldd `which smbd`) -
    a Samba-smb.conf setting of printing = cups -
    another Samba-smb.conf setting of printcap = cups -

    Example:

            print command = /usr/bin/lpr -r -P%p %s
+        lpq command   = /usr/bin/lpq    -P%p %s
+        lprm command  = /usr/bin/lprm   -P%p %j
+        queuepause command = /usr/sbin/lpc -P%p stop
+        queuepause command = /usr/sbin/lpc -P%p start

    Note, that in this case all other manually set printing-related -commands (like "print command", "lpq command", "lprm command", -"lppause command" or "lpresume command") are ignored and they -should normally have no influence what-so-ever on your printing.

    Samba should set reasonable defaults for these depending on your +system type, but it isn't clairvoyant. It is not uncommon that you +have to tweak these for local conditions. The commands should +always have fully specified pathnames, as the smdb may not have +the correct PATH values.

    When you send a job to Samba to be printed, it will make a temporary +copy of it in the directory specified in the [printers] section. +and it should be periodically cleaned out. The lpr -r option +requests that the temporary copy be removed after printing; If +printing fails then you might find leftover files in this directory, +and it should be periodically cleaned out. Samba used the lpq +command to determine the "job number" assigned to your print job +by the spooler.

    The %>letter< are "macros" that get dynamically replaced with appropriate +values when they are used. The %s gets replaced with the name of the spool +file that Samba creates and the %p gets replaced with the name of the +printer. The %j gets replaced with the "job number" which comes from +the lpq output.

    13.4.2. Debugging printer problems

    If you want to do things manually, replace the "printing = cups" -by "printing = bsd". Then your manually set commands may work -(haven't tested this), and a "print command = lp -d %P %s; rm %s" -may do what you need.

    One way to debug printing problems is to start by replacing these +command with shell scripts that record the arguments and the contents +of the print file. A simple example of this kind of things might +be:

    You forgot to mention the CUPS version you're using. If you did -set things up as described in the man pages, then the Samba -spool files should be deleted. Otherwise it may be a bug. On -the CUPS side, you can control the behaviour as described -above.

    	print command = /tmp/saveprint %p %s
+
+    #!/bin/saveprint
+    # we make sure that we are the right user
+    /usr/bin/id -p >/tmp/tmp.print
+    # we run the command and save the error messages
+    # replace the command with the one appropriate for your system
+    /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print

    If you have more problems, post the output of these commands:

    Then you print a file and try removing it. You may find that the +print queue needs to be stopped in order to see the queue status +and remove the job:

    grep -v ^# /etc/cups/cupsd.conf | grep -v ^$ - grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"

    
h4: {42} % echo hi >/tmp/hi
+h4: {43} % smbclient //localhost/lw4
+added interface ip=10.0.0.4 bcast=10.0.0.255 nmask=255.255.255.0
+Password: 
+Domain=[ASTART] OS=[Unix] Server=[Samba 2.0.7]
+smb: \> print /tmp/hi
+putting file /tmp/hi as hi-17534 (0.0 kb/s) (average 0.0 kb/s)
+smb: \> queue
+1049     3            hi-17534
+smb: \> cancel 1049
+Error cancelling job 1049 : code 0
+smb: \> cancel 1049
+Job 1049 cancelled
+smb: \> queue
+smb: \> exit

    (adapt paths as needed). These commands sanitize the files -and cut out the empty lines and lines with comments, providing -the "naked settings" in a compact way.

    The 'code 0' indicates that the job was removed. The comment +by the smbclient is a bit misleading on this. +You can observe the command output and then and look at the +/tmp/tmp.print file to see what the results are. You can quickly +find out if the problem is with your printing system. Often people +have problems with their /etc/printcap file or permissions on +various print queues.

    Chapter 14. Unified Logons between Windows NT and UNIX using Winbind

    14.1. Abstract

    13.4.3. What printers do I have?

    Integration of UNIX and Microsoft Windows NT through - a unified logon has been considered a "holy grail" in heterogeneous - computing environments for a long time. We present - winbind, a component of the Samba suite - of programs as a solution to the unified logon problem. Winbind - uses a UNIX implementation - of Microsoft RPC calls, Pluggable Authentication Modules, and the Name - Service Switch to allow Windows NT domain users to appear and operate - as UNIX users on a UNIX machine. This paper describes the winbind - system, explaining the functionality it provides, how it is configured, - and how it works internally.

    You can use the 'testprns' program to check to see if the printer +name you are using is recognized by Samba. For example, you can +use:

        testprns printer /etc/printcap

    Samba can get its printcap information from a file or from a program. +You can try the following to see the format of the extracted +information:

        testprns -a printer /etc/printcap
+
+    testprns -a printer '|/bin/cat printcap'

    14.2. Introduction

    13.4.4. Setting up printcap and print servers

    It is well known that UNIX and Microsoft Windows NT have - different models for representing user and group information and - use different technologies for implementing them. This fact has - made it difficult to integrate the two systems in a satisfactory - manner.

    You may need to set up some printcaps for your Samba system to use. +It is strongly recommended that you use the facilities provided by +the print spooler to set up queues and printcap information.

    One common solution in use today has been to create - identically named user accounts on both the UNIX and Windows systems - and use the Samba suite of programs to provide file and print services - between the two. This solution is far from perfect however, as - adding and deleting users on both sets of machines becomes a chore - and two sets of passwords are required both of which - can lead to synchronization problems between the UNIX and Windows - systems and confusion for users.

    Samba requires either a printcap or program to deliver printcap +information. This printcap information has the format:

      name|alias1|alias2...:option=value:...

    For almost all printing systems, the printer 'name' must be composed +only of alphanumeric or underscore '_' characters. Some systems also +allow hyphens ('-') as well. An alias is an alternative name for the +printer, and an alias with a space in it is used as a 'comment' +about the printer. The printcap format optionally uses a \ at the end of lines +to extend the printcap to multiple lines.

    Here are some examples of printcap files:

    We divide the unified logon problem for UNIX machines into - three smaller problems:

      1. Obtaining Windows NT user and group information -

        pr just printer name

      2. Authenticating Windows NT users -

        pr|alias printer name and alias

      3. Password changing for Windows NT users -

        pr|My Printer printer name, alias used as comment

    Ideally, a prospective solution to the unified logon problem - would satisfy all the above components without duplication of - information on the UNIX machines and without creating additional - tasks for the system administrator when maintaining users and - groups on either system. The winbind system provides a simple - and elegant solution to all three components of the unified logon - problem.

    14.3. What Winbind Provides

  • Winbind unifies UNIX and Windows NT account management by - allowing a UNIX box to become a full member of a NT domain. Once - this is done the UNIX box will see NT users and groups as if - they were native UNIX users and groups, allowing the NT domain - to be used in much the same manner that NIS+ is used within - UNIX-only environments.

    pr:sh:\ Same as pr:sh:cm= testing + :cm= \ + testing

  • The end result is that whenever any - program on the UNIX machine asks the operating system to lookup - a user or group name, the query will be resolved by asking the - NT domain controller for the specified domain to do the lookup. - Because Winbind hooks into the operating system at a low level - (via the NSS name resolution modules in the C library) this - redirection to the NT domain controller is completely - transparent.

    pr:sh Same as pr:sh:cm= testing + :cm= testing

    • Users on the UNIX machine can then use NT user and group - names as they would use "native" UNIX names. They can chown files - so that they are owned by NT domain users or even login to the - UNIX machine and run a UNIX X-Window session as a domain user.

    Samba reads the printcap information when first started. If you make +changes in the printcap information, then you must do the following:

    The only obvious indication that Winbind is being used is - that user and group names take the form DOMAIN\user and - DOMAIN\group. This is necessary as it allows Winbind to determine - that redirection to a domain controller is wanted for a particular - lookup and which trusted domain is being referenced.

    1. Additionally, Winbind provides an authentication service - that hooks into the Pluggable Authentication Modules (PAM) system - to provide authentication via a NT domain to any PAM enabled - applications. This capability solves the problem of synchronizing - passwords between systems since all passwords are stored in a single - location (on the domain controller).

      14.3.1. Target Uses

      make sure that the print spooler is aware of these changes. +The LPRng system uses the 'lpc reread' command to do this.

    2. Winbind is targeted at organizations that have an - existing NT based domain infrastructure into which they wish - to put UNIX workstations or servers. Winbind will allow these - organizations to deploy UNIX workstations without having to - maintain a separate account infrastructure. This greatly - simplifies the administrative overhead of deploying UNIX - workstations into a NT based organization.

      make sure that the spool queues, etc., exist and have the +correct permissions. The LPRng system uses the 'checkpc -f' +command to do this.

    3. Another interesting way in which we expect Winbind to - be used is as a central part of UNIX based appliances. Appliances - that provide file and print services to Microsoft based networks - will be able to use Winbind to provide seamless integration of - the appliance into the domain.

    You now should send a SIGHUP signal to the smbd server to have +it reread the printcap information.

    14.4. How Winbind Works

    The winbind system is designed around a client/server - architecture. A long running winbindd daemon - listens on a UNIX domain socket waiting for requests - to arrive. These requests are generated by the NSS and PAM - clients and processed sequentially.

    The technologies used to implement winbind are described - in detail below.

    14.4.1. Microsoft Remote Procedure Calls13.4.5. Job sent, no output

    Over the last few years, efforts have been underway - by various Samba Team members to decode various aspects of - the Microsoft Remote Procedure Call (MSRPC) system. This - system is used for most network related operations between - Windows NT machines including remote management, user authentication - and print spooling. Although initially this work was done - to aid the implementation of Primary Domain Controller (PDC) - functionality in Samba, it has also yielded a body of code which - can be used for other purposes.

    Winbind uses various MSRPC calls to enumerate domain users - and groups and to obtain detailed information about individual - users or groups. Other MSRPC calls can be used to authenticate - NT domain users and to change user passwords. By directly querying - a Windows PDC for user and group information, winbind maps the - NT account information onto UNIX user and group names.

    14.4.2. Microsoft Active Directory Services

    This is the most frustrating part of printing. You may have sent the +job, verified that the job was forwarded, set up a wrapper around +the command to send the file, but there was no output from the printer.

    Since late 2001, Samba has gained the ability to - interact with Microsoft Windows 2000 using its 'Native - Mode' protocols, rather than the NT4 RPC services. - Using LDAP and Kerberos, a domain member running - winbind can enumerate users and groups in exactly the - same way as a Win2k client would, and in so doing - provide a much more efficient and - effective winbind implementation. -

    14.4.3. Name Service Switch

    First, check to make sure that the job REALLY is getting to the +right print queue. If you are using a BSD or LPRng print spooler, +you can temporarily stop the printing of jobs. Jobs can still be +submitted, but they will not be printed. Use:

    The Name Service Switch, or NSS, is a feature that is - present in many UNIX operating systems. It allows system - information such as hostnames, mail aliases and user information - to be resolved from different sources. For example, a standalone - UNIX workstation may resolve system information from a series of - flat files stored on the local filesystem. A networked workstation - may first attempt to resolve system information from local files, - and then consult a NIS database for user information or a DNS server - for hostname information.

      lpc -Pprinter stop

    The NSS application programming interface allows winbind - to present itself as a source of system information when - resolving UNIX usernames and groups. Winbind uses this interface, - and information obtained from a Windows NT server using MSRPC - calls to provide a new source of account enumeration. Using standard - UNIX library calls, one can enumerate the users and groups on - a UNIX machine running winbind and see all users and groups in - a NT domain plus any trusted domain as though they were local - users and groups.

    Now submit a print job and then use 'lpq -Pprinter' to see if the +job is in the print queue. If it is not in the print queue then +you will have to find out why it is not being accepted for printing.

    The primary control file for NSS is - /etc/nsswitch.conf. - When a UNIX application makes a request to do a lookup - the C library looks in /etc/nsswitch.conf - for a line which matches the service type being requested, for - example the "passwd" service type is used when user or group names - are looked up. This config line species which implementations - of that service should be tried and in what order. If the passwd - config line is:

    Next, you may want to check to see what the format of the job really +was. With the assistance of the system administrator you can view +the submitted jobs files. You may be surprised to find that these +are not in what you would expect to call a printable format. +You can use the UNIX 'file' utitily to determine what the job +format actually is:

    passwd: files example

        cd /var/spool/lpd/printer   # spool directory of print jobs
+    ls                          # find job files
+    file dfA001myhost

    then the C library will first load a module called - /lib/libnss_files.so followed by - the module /lib/libnss_example.so. The - C library will dynamically load each of these modules in turn - and call resolver functions within the modules to try to resolve - the request. Once the request is resolved the C library returns the - result to the application.

    This NSS interface provides a very easy way for Winbind - to hook into the operating system. All that needs to be done - is to put libnss_winbind.so in /lib/ - then add "winbind" into /etc/nsswitch.conf at - the appropriate place. The C library will then call Winbind to - resolve user and group names.

    You should make sure that your printer supports this format OR that +your system administrator has installed a 'print filter' that will +convert the file to a format appropriate for your printer.

    14.4.4. Pluggable Authentication Modules13.4.6. Job sent, strange output

    Pluggable Authentication Modules, also known as PAM, - is a system for abstracting authentication and authorization - technologies. With a PAM module it is possible to specify different - authentication methods for different system applications without - having to recompile these applications. PAM is also useful - for implementing a particular policy for authorization. For example, - a system administrator may only allow console logins from users - stored in the local password file but only allow users resolved from - a NIS database to log in over the network.

    Once you have the job printing, you can then start worrying about +making it print nicely.

    Winbind uses the authentication management and password - management PAM interface to integrate Windows NT users into a - UNIX system. This allows Windows NT users to log in to a UNIX - machine and be authenticated against a suitable Primary Domain - Controller. These users can also change their passwords and have - this change take effect directly on the Primary Domain Controller. -

    The most common problem is extra pages of output: banner pages +OR blank pages at the end.

    PAM is configured by providing control files in the directory - /etc/pam.d/ for each of the services that - require authentication. When an authentication request is made - by an application the PAM code in the C library looks up this - control file to determine what modules to load to do the - authentication check and in what order. This interface makes adding - a new authentication service for Winbind very easy, all that needs - to be done is that the pam_winbind.so module - is copied to /lib/security/ and the PAM - control files for relevant services are updated to allow - authentication via winbind. See the PAM documentation - for more details.

    If you are getting banner pages, check and make sure that the +printcap option or printer option is configured for no banners. +If you have a printcap, this is the :sh (suppress header or banner +page) option. You should have the following in your printer.

       printer: ... :sh

    If you have this option and are still getting banner pages, there +is a strong chance that your printer is generating them for you +automatically. You should make sure that banner printing is disabled +for the printer. This usually requires using the printer setup software +or procedures supplied by the printer manufacturer.

    If you get an extra page of output, this could be due to problems +with your job format, or if you are generating PostScript jobs, +incorrect setting on your printer driver on the MicroSoft client. +For example, under Win95 there is a option:

      Printers|Printer Name|(Right Click)Properties|Postscript|Advanced|

    that allows you to choose if a Ctrl-D is appended to all jobs. +This is a very bad thing to do, as most spooling systems will +automatically add a ^D to the end of the job if it is detected as +PostScript. The multiple ^D may cause an additional page of output.

    14.4.5. User and Group ID Allocation13.4.7. Raw PostScript printed

    When a user or group is created under Windows NT - is it allocated a numerical relative identifier (RID). This is - slightly different to UNIX which has a range of numbers that are - used to identify users, and the same range in which to identify - groups. It is winbind's job to convert RIDs to UNIX id numbers and - vice versa. When winbind is configured it is given part of the UNIX - user id space and a part of the UNIX group id space in which to - store Windows NT users and groups. If a Windows NT user is - resolved for the first time, it is allocated the next UNIX id from - the range. The same process applies for Windows NT groups. Over - time, winbind will have mapped all Windows NT users and groups - to UNIX user ids and group ids.

    This is a problem that is usually caused by either the print spooling +system putting information at the start of the print job that makes +the printer think the job is a text file, or your printer simply +does not support PostScript. You may need to enable 'Automatic +Format Detection' on your printer.

    13.4.8. Advanced Printing

    The results of this mapping are stored persistently in - an ID mapping database held in a tdb database). This ensures that - RIDs are mapped to UNIX IDs in a consistent way.

    Note that you can do some pretty magic things by using your +imagination with the "print command" option and some shell scripts. +Doing print accounting is easy by passing the %U option to a print +command shell script. You could even make the print command detect +the type of output and its size and send it to an appropriate +printer.

    14.4.6. Result Caching13.4.9. Real debugging

    An active system can generate a lot of user and group - name lookups. To reduce the network cost of these lookups winbind - uses a caching scheme based on the SAM sequence number supplied - by NT domain controllers. User or group information returned - by a PDC is cached by winbind along with a sequence number also - returned by the PDC. This sequence number is incremented by - Windows NT whenever any user or group information is modified. If - a cached entry has expired, the sequence number is requested from - the PDC and compared against the sequence number of the cached entry. - If the sequence numbers do not match, then the cached information - is discarded and up to date information is requested directly - from the PDC.

    If the above debug tips don't help, then maybe you need to bring in +the bug guns, system tracing. See Tracing.txt in this directory.

    Chapter 14. CUPS Printing Support

    14.5. Installation and Configuration14.1. Introduction

    Many thanks to John Trostel The Common Unix Print System (CUPS) has become very popular, but to many it is +a very mystical tool. There is a great deal of uncertainty regarding CUPS and how +it works. The result is seen in a large number of posting on the samba mailing lists +expressing frustration when MS Windows printers appear not to work with a CUPS +backr-end.

    This is a good time to point out how CUPS can be used and what it does. CUPS is more +than just a print spooling system - it is a complete printer management system that +complies with HTTP and IPP protocols. It can be managed remotely via a web browser +and it can print using http and ipp protocols.

    CUPS allows to creation of RAW printers (ie: NO file format translation) as well as +SMART printers (ie: CUPS does file format conversion as required for the printer). In +many ways this gives CUPS similar capabilities to the MS Windows print monitoring +system. Of course, if you are a CUPS advocate, you would agrue that CUPS is better! +In any case, let us now move on to explore how one may configure CUPS for interfacing +with MS Windows print clients via Samba.

    jtrostel@snapserver.comCUPS is a newcomer in the UNIX printing scene, +which has convinced many people upon first trial already. However, it has quite a few +new features, which make it different from other, more traditional printing systems.

    14.2. Configuring smb.conf for CUPS

    Printing with CUPS in the most basic smb.conf -for providing the HOWTO for this section.

    printing = cups and +printcap = cups. While CUPS itself doesn't need a printcap +anymore, the cupsd.conf configuration file knows two directives +(example: Printcap /etc/printcap and PrintcapFormat +BSD), which control if such a file should be created for the +convenience of third party applications. Make sure it is set! For details see +man cupsd.conf and other CUPS-related documentation.

    This HOWTO describes how to get winbind services up and running -to control access and authenticate users on your Linux box using -the winbind services which come with SAMBA 2.2.2.

    If SAMBA is compiled against libcups, then printcap = cups uses the +CUPS API to list printers, submit jobs, etc. Otherwise it maps to the System V commands +with an additional -oraw option for printing. On a Linux system, +you can use the ldd command to find out details (ldd may not be +present on other OS platforms, or its function may be embodied by a different command):

    transmeta:/home/kurt # ldd `which smbd`
+        libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000)
+        libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
+        libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000)
+        libdl.so.2 => /lib/libdl.so.2 (0x401e8000)
+        libnsl.so.1 => /lib/libnsl.so.1 (0x401ec000)
+        libpam.so.0 => /lib/libpam.so.0 (0x40202000)
+        libc.so.6 => /lib/libc.so.6 (0x4020b000)
+        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

    The line "libcups.so.2 => /usr/lib/libcups.so.2 +(0x40123000)" shows there is CUPS support compiled into this version of +Samba. If this is the case, and printing = cups is set, then any +otherwise manually set print command in smb.conf is ignored.

    14.5.1. Introduction

    14.3. CUPS - RAW Print Through Mode

    This HOWTO describes the procedures used to get winbind up and -running on my RedHat 7.1 system. Winbind is capable of providing access -and authentication control for Windows Domain users through an NT -or Win2K PDC for 'regular' services, such as telnet a nd ftp, as -well for SAMBA services.

    When used in raw print through mode is will be necessary to use the printer +vendor's drivers in each Windows client PC.

    This HOWTO has been written from a 'RedHat-centric' perspective, so if -you are using another distribution, you may have to modify the instructions -somewhat to fit the way your distribution works.

    When CUPS printers are configured for RAW print-through mode operation it is the +responsibility of the Samba client to fully render the print job (file) in a format +that is suitable for direct delivery to the printer. In this case CUPS will NOT +do any print file format conversion work.

    The CUPS files that need to be correctly set for RAW mode printers to work are: + +

    • /etc/cups/mime.types

    • /etc/cups/mime.convs

    + +Both contain entries that must be uncommented to allow Why should I to this?RAW     -

    mode +operation.

    This allows the SAMBA administrator to rely on the - authentication mechanisms on the NT/Win2K PDC for the authentication - of domain members. NT/Win2K users no longer need to have separate - accounts on the SAMBA server. -

    Firstly, to enable CUPS based printing from Samba the following options must be +enabled in your smb.conf file [globals] section: + +

    • printing = CUPS

    • printcap = CUPS

    + +When these parameters are specified the print directives in smb.conf (as well as in +samba itself) will be ignored because samba will directly interface with CUPS through +it's application program interface (API) - so long as Samba has been compiled with +CUPS library (libcups) support. If samba has NOT been compiled with CUPS support then +printing will use the System V AT&T command set with the Who should be reading this document?-oraw +> +option automatically passing through.

    Cupsomatic (an enhanced printing utility that is part of some CUPS implementations) +on the Samba/CUPS server does *not* add any features if a file is really +printed "raw". However, if you have loaded the driver for the Windows client from +the CUPS server, using the "cupsaddsmb" utility, and if this driver is one using +a "Foomatic" PPD, the PJL header in question is already added on the Windows client, +at the time when the driver initially generated the PostScript data and CUPS in true +"-oraw" manner doesn't remove this PJL header and passes the file "as is" to its +printer communication backend.

    NOTE: editing in the "mime.convs" and the "mime.types" file does not *enforce* +"raw" printing, it only *allows* it.

    Print files that arrive from MS Windows printing are "auto-typed" by CUPS. This aids +the process of determining proper treatment while in the print queue system. + +

    • Files generated by PCL drivers and directed at PCK printers get auto-typed as + application/octet-stream. Unknown file format types also + get auto-typed with this tag.

    • This HOWTO is designed for system administrators. If you are - implementing SAMBA on a file server and wish to (fairly easily) - integrate existing NT/Win2K users from your PDC onto the - SAMBA server, this HOWTO is for you. That said, I am no NT or PAM - expert, so you may find a better or easier way to accomplish - these tasks. +> Files generated by a Postscript driver and directed at a Postscript printer + are auto-typed depending on the auto-detected most suitable MIME type as: + +

      • * application/postscript

      • * application/vnd.cups-postscript

    "application/postscript" first goes thru the "pstops" filter (where the page counting +and accounting takes place). The outcome will be of MIME type +"application/vnd.cups-postscript". The pstopsfilter reads and uses information from +the PPD and inserts user-provided options into the PostScript file. As a consequence, +the filtered file could possibly have an unwanted PJL header.

    "application/postscript" will be all files with a ".ps", ".ai", ".eps" suffix or which +have as their first character string one of "%!" or ">04<%".

    "application/vnd.cups-postscript" will files which contain the string +"LANGUAGE=POSTSCRIPT" (or similar variations with different capitalization) in the +first 512 bytes, and also contain the "PJL super escape code" in the first 128 bytes +(">1B<%-12345X"). Very likely, most PostScript files generated on Windows using a CUPS +or other PPD, will have to be auto-typed as "vnd.cups-postscript". A file produced +with a "Generic PostScript driver" will just be tagged "application/postscript".

    Once the file is in "application/vnd.cups-postscript" format, either "pstoraster" +or "cupsomatic" will take over (depending on the printer configuration, as +determined by the PPD in use).

    14.5.2. Requirements

    If you have a samba configuration file that you are currently -using... BACK IT UP! If your system already uses PAM, -back up the /etc/pam.d directory -contents! If you haven't already made a boot disk, -MAKE ONE NOW!

    Messing with the pam configuration files can make it nearly impossible -to log in to yourmachine. That's why you want to be able to boot back -into your machine in single user mode and restore your -/etc/pam.d back to the original state they were in if -you get frustrated with the way things are going. ;-)

    A printer queue with *no* PPD associated to it is a "raw" printer and all files +will go directly there as received by the spooler. The exeptions are file types +"application/octet-stream" which need "passthrough feature" enabled. +"Raw" queues don't do any filtering at all, they hand the file directly to the +CUPS backend. This backend is responsible for the sending of the data to the device +(as in the "device URI" notation as lpd://, socket://, smb://, ipp://, http://, +parallel:/, serial:/, usb:/ etc.)

    The latest version of SAMBA (version 3.0 as of this writing), now -includes a functioning winbindd daemon. Please refer to the -main SAMBA web page or, -better yet, your closest SAMBA mirror site for instructions on -downloading the source code.

    "cupsomatic"/Foomatic are *not* native CUPS drivers and they don't ship with CUPS. +They are a Third Party add-on, developed at Linuxprinting.org. As such, they are +a brilliant hack to make all models (driven by Ghostscript drivers/filters in +traditional spoolers) also work via CUPS, with the same (good or bad!) quality +as in these other spoolers. "cupsomatic" is only a vehicle to execute a ghostscript +commandline at that stage in the CUPS filtering chain, where "normally" the native +CUPS "pstoraster" filter would kick in. cupsomatic by-passes pstoraster, "kidnaps" +the printfile from CUPS away and re-directs it to go through Ghostscipt. CUPS accepts this, +because the associated CUPS-O-Matic-/Foomatic-PPD specifies:

       *cupsFilter:  "application/vnd.cups-postscript 0 cupsomatic"

    To allow Domain users the ability to access SAMBA shares and -files, as well as potentially other services provided by your -SAMBA machine, PAM (pluggable authentication modules) must -be setup properly on your machine. In order to compile the -winbind modules, you should have at least the pam libraries resident -on your system. For recent RedHat systems (7.1, for instance), that -means pam-0.74-22. For best results, it is helpful to also -install the development packages in pam-devel-0.74-22.

    This line persuades CUPS to hand the file to cupsomatic, once it has successfully +converted it to the MIME type "application/vnd.cups-postscript". This conversion will not +happen for Jobs arriving from Windows which are auto-typed "application/octet-stream", +with the according changes in "/etc/cups/mime.types" in place.

    14.5.3. Testing Things Out

    Before starting, it is probably best to kill off all the SAMBA -related daemons running on your server. Kill off all smbd, -nmbd, and winbindd processes that may -be running. To use PAM, you will want to make sure that you have the -standard PAM package (for RedHat) which supplies the /etc/pam.d -directory structure, including the pam modules are used by pam-aware -services, several pam libraries, and the /usr/doc -and /usr/man entries for pam. Winbind built better -in SAMBA if the pam-devel package was also installed. This package includes -the header files needed to compile pam-aware applications. For instance, -my RedHat system has both pam-0.74-22 and -pam-devel-0.74-22 RPMs installed.

    14.5.3.1. Configure and compile SAMBA

    CUPS is widely configurable and flexible, even regarding its filtering mechanism. +Another workaround in some situations would be to have +in "/etc/cups/mime.types" entries as follows:

       application/postscript           application/vnd.cups-raw  0  -
+   application/vnd.cups-postscript  application/vnd.cups-raw  0  -

    The configuration and compilation of SAMBA is pretty straightforward. -The first three steps may not be necessary depending upon -whether or not you have previously built the Samba binaries.

    This would prevent all Postscript files from being filtered (rather, they will go +thru the virtual "nullfilter" denoted with "-"). This could only be useful for +PS printers. If you want to print PS code on non-PS printers an entry as follows +could be useful:

       */*           application/vnd.cups-raw  0  -

    and would effectively send *all* files to the backend without further processing.

    Lastly, you could have the following entry:

    root# autoconf
-root# make clean
-root# rm config.cache
-root# ./configure
-root# make
-root# make install

    application/vnd.cups-postscript application/vnd.cups-raw 0 my_PJL_stripping_filter

    This will, by default, install SAMBA in /usr/local/samba. -See the main SAMBA documentation if you want to install SAMBA somewhere else. -It will also build the winbindd executable and libraries.

    You will need to write a "my_PJL_stripping_filter" (could be a shellscript) that +parses the PostScript and removes the unwanted PJL. This would need to conform to +CUPS filter design (mainly, receive and pass the parameters printername, job-id, +username, jobtitle, copies, print options and possibly the filename). It would +be installed as world executable into "/usr/lib/cups/filters/" and will be called +by CUPS if it encounters a MIME type "application/vnd.cups-postscript".

    CUPS can handle "-o job-hold-until=indefinite". This keeps the job in the queue +"on hold". It will only be printed upon manual release by the printer operator. +This is a requirement in many "central reproduction departments", where a few +operators manage the jobs of hundreds of users on some big machine, where no +user is allowed to have direct access. (The operators often need to load the +proper paper type before running the 10.000 page job requested by marketing +for the mailing, etc.).

    14.5.3.2. Configure nsswitch.conf and the -winbind libraries

    14.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe +PostScript driver with CUPS-PPDs downloaded to clients

    The libraries needed to run the winbindd daemon -through nsswitch need to be copied to their proper locations, so

    CUPS is perfectly able to use PPD files (PostScript +Printer Descriptions). PPDs can control all print device options. They +are usually provided by the manufacturer -- if you own a PostSript printer, +that is. PPD files are always a component of PostScript printer drivers on MS +Windows or Apple Mac OS systems. They are ASCII files containing +user-selectable print options, mapped to appropriate PostScript, PCL or PJL +commands for the target printer. Printer driver GUI dialogs translate these +options "on-the-fly" into buttons and drop-down lists for the user to +select.

    root# CUPS can load, without any conversions, the PPD file from +any Windows (NT is recommended) PostScript driver and handle the options. +There is a web browser interface to the print options (select +http://localhost:631/printers/ and click on one "Configure Printer" button +to see it), a commandline interface (see cp ../samba/source/nsswitch/libnss_winbind.so /lib

    man lpoptions or +try if you have lphelp on your system) plus some different GUI frontends on Linux +UNIX, which can present PPD options to the users. PPD options are normally +meant to become evaluated by the PostScript RIP on the real PostScript +printer.

    CUPS doesn't stop at "real" PostScript printers in its +usage of PPDs. The CUPS developers have extended the PPD concept, to also +describe available device and driver options for non-PostScript printers +through CUPS-PPDs.

    This is logical, as CUPS includes a fully featured +PostScript interpreter (RIP). This RIP is based on Ghostscript. It can +process all received PostScript (and additionally many other file formats) +from clients. All CUPS-PPDs geared to non-PostScript printers contain an +additional line, starting with the keyword *cupsFilter. +This line +tells the CUPS print system which printer-specific filter to use for the +interpretation of the accompanying PostScript. Thus CUPS lets all its +printers appear as PostScript devices to its clients, because it can act as a +PostScript RIP for those printers, processing the received PostScript code +into a proper raster print format.

    CUPS-PPDs can also be used on Windows-Clients, on top of a +PostScript driver (recommended is the Adobe one).

    I also found it necessary to make the following symbolic link:

    This feature enables CUPS to do a few tricks no other +spooler can do:

    root# ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2

    • And, in the case of Sun solaris:

      root# ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1 -root# ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1 -root# ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2

      act as a networked PostScript RIP (Raster Image Processor), handling + printfiles from all client platforms in a uniform way;

    • Now, as root you need to edit /etc/nsswitch.conf to -allow user and group entries to be visible from the act as a central accounting and billing server, as all files are passed + through the winbindd -daemon. My pstops Filter and are therefor logged in + the CUPS /etc/nsswitch.conf file look like -this after editing:

      	passwd:     files winbind
-	shadow:     files 
-	group:      files winbind

      page_log. - NOTE: this + can not happen with "raw" print jobs, which always remain unfiltered + per definition;

    • -The libraries needed by the winbind daemon will be automatically -entered into the ldconfig cache the next time -your system reboots, but it -is faster (and you don't need to reboot) if you do it manually:

      enable clients to consolidate on a single PostScript driver, even for + many different target printers.

    14.5. Windows Terminal Servers (WTS) as CUPS clients

    root# /sbin/ldconfig -v | grep winbind

    This setup may be of special interest to people +experiencing major problems in WTS environments. WTS need often a multitude +of non-PostScript drivers installed to run their clients' variety of +different printer models. This often imposes the price of much increased +instability. In many cases, in an attempt to overcome this problem, site +administrators have resorted to restrict the allowed drivers installed on +their WTS to one generic PCL- and one PostScript driver. This however +restricts the clients in the amount of printer options available for them -- +often they can't get out more then simplex prints from one standard paper +tray, while their devices could do much better, if driven by a different +driver!

    This makes libnss_winbind available to winbindd -and echos back a check to you.

    Using an Adobe PostScript driver, enabled with a CUPS-PPD, +seems to be a very elegant way to overcome all these shortcomings. The +PostScript driver is not known to cause major stability problems on WTS (even +if used with many different PPDs). The clients will be able to (again) chose +paper trays, duplex printing and other settings. However, there is a certain +price for this too: a CUPS server acting as a PostScript RIP for its clients +requires more CPU and RAM than just to act as a "raw spooling" device. Plus, +this setup is not yet widely tested, although the first feedbacks look very +promising...

    14.5.3.3. Configure smb.conf

    14.6. Setting up CUPS for driver download

    Several parameters are needed in the smb.conf file to control -the behavior of The winbindd. Configure -smb.conf These are described in more detail in -the winbindd(8) man page. My -cupsadsmb utility (shipped with all current +CUPS versions) makes the sharing of any (or all) installed CUPS printers very +easy. Prior to using it, you need the following settings in smb.conf file was modified to -include the following entries in the [global] section:

    :

    [global]
-     <...>
-     # separate domain and username with '+', like DOMAIN+username
-     winbind separator = +
-     # use uids from 10000 to 20000 for domain users
-     winbind uid = 10000-20000
-     # use gids from 10000 to 20000 for domain groups
-     winbind gid = 10000-20000
-     # allow enumeration of winbind users and groups
-     winbind enum users = yes
-     winbind enum groups = yes
-     # give winbind users a real shell (only needed if they have telnet access)
-     template homedir = /home/winnt/%D/%U
-     template shell = /bin/bash

    14.5.3.4. Join the SAMBA server to the PDC domain

    Enter the following command to make the SAMBA server join the -PDC domain, where DOMAIN is the name of -your Windows domain and Administrator is -a domain user who has administrative privileges in the domain.

    For licensing reasons the necessary files of the Adobe +Postscript driver can not be distributed with either Samba or CUPS. You need +to download them yourself from the Adobe website. Once extracted, create a +drivers directory in the CUPS data directory (usually +/usr/share/cups/). Copy the Adobe files using +UPPERCASE filenames, to this directory as follows:

    root# /usr/local/samba/bin/net join -S PDC -U Administrator

    		ADFONTS.MFM
+		ADOBEPS4.DRV
+		ADOBEPS4.HLP
+		ADOBEPS5.DLL
+		ADOBEPSU.DLL
+		ADOBEPSU.HLP
+		DEFPRTR2.PPD
+		ICONLIB.DLL
+

    The proper response to the command should be: "Joined the domain -DOMAIN" where DOMAIN -is your DOMAIN name.

    Users of the ESP Print Pro software are able to install +their "Samba Drivers" package for this purpose with no problem.

    14.5.3.5. Start up the winbindd daemon and test it!

    14.7. Sources of CUPS drivers / PPDs

    Eventually, you will want to modify your smb startup script to -automatically invoke the winbindd daemon when the other parts of -SAMBA start, but it is possible to test out just the winbind -portion first. To start up winbind services, enter the following -command as root:

    On the internet you can find now many thousand CUPS-PPD +files (with their companion filters), in many national languages, +supporting more than 1.000 non-PostScript models.

    root# /usr/local/samba/bin/winbindd

    • Winbindd can now also run in 'dual daemon mode'. This will make it -run as 2 processes. The first will answer all requests from the cache, -thus making responses to clients faster. The other will -update the cache for the query that the first has just responded. -Advantage of this is that responses stay accurate and are faster. -You can enable dual daemon mode by adding '-B' to the commandline:

      ESP PrintPro + (http://wwwl.easysw.com/printpro/) + (commercial, non-Free) is packaged with more than 3.000 PPDs, ready for + successful usage "out of the box" on Linux, IBM-AIX, HP-UX, Sun-Solaris, + SGI-IRIX, Compaq Tru64, Digital Unix and some more commercial Unices (it + is written by the CUPS developers themselves and its sales help finance + the further development of CUPS, as they feed their creators)

    • root# /usr/local/samba/bin/winbindd -B

      the Gimp-Print-Project + (http://gimp-print.sourceforge.net/) + (GPL, Free Software) provides around 120 PPDs (supporting nearly 300 + printers, many driven to photo quality output), to be used alongside the + Gimp-Print CUPS filters;

    • I'm always paranoid and like to make sure the daemon -is really running...

      TurboPrint + (http://www.turboprint.com/) + (Shareware, non-Freee) supports roughly the same amount of printers in + excellent quality;

    • root# ps -ae | grep winbindd

      OMNI + (http://www-124.ibm.com/developerworks/oss/linux/projects/omni/) + (LPGL, Free) is a package made by IBM, now containing support for more + than 400 printers, stemming from the inheritance of IBM OS/2 KnowHow + ported over to Linux (CUPS support is in a Beta-stage at present);

    • This command should produce output like this, if the daemon is running

      HPIJS + (http://hpinkjet.sourceforge.net/) + (BSD-style licnes, Free) supports around 120 of HP's own printers and is + also providing excellent print quality now;

    • 3025 ? 00:00:00 winbindd

      Foomatic/cupsomatic (http://www.linuxprinting.org/) + (LPGL, Free) from Linuxprinting.org are providing PPDs for practically every + Ghostscript filter known to the world, now usable with CUPS.

    Now... for the real test, try to get some information about the -users on your PDC

    NOTE: the cupsomatic trick from Linuxprinting.org is +working different from the other drivers. While the other drivers take the +generic CUPS raster (produced by CUPS' own pstoraster PostScript RIP) as +their input, cupsomatic "kidnaps" the PostScript inside CUPS, before +RIP-ping, deviates it to an external Ghostscript installation (which now +becomes the RIP) and gives it back to a CUPS backend once Ghostscript is +finished. -- CUPS versions from 1.1.15 and later will provide their pstoraster +PostScript RIP function again inside a system-wide Ghostscript +installation rather than in "their own" pstoraster filter. (This +CUPS-enabling Ghostscript version may be installed either as a +patch to GNU or AFPL Ghostscript, or as a complete ESP Ghostscript package). +However, this will not change the cupsomatic approach of guiding the printjob +along a different path through the filtering system than the standard CUPS +way...

    root# Once you installed a printer inside CUPS with one of the +recommended methods (the lpadmin command, the web browser interface or one of +the available GUI wizards), you can use /usr/local/samba/bin/wbinfo -u

    -This should echo back a list of users on your Windows users on -your PDC. For example, I get the following response:

    CEO+Administrator
-CEO+burdell
-CEO+Guest
-CEO+jt-ad
-CEO+krbtgt
-CEO+TsInternetUser

    Obviously, I have named my domain 'CEO' and my winbind -separator is '+'.

    cupsaddsmb to share the +printer via Samba. cupsaddsmb prepares the driver files for +comfortable client download and installation upon their first contact with +this printer share.

    14.7.1. cupsaddsmb

    You can do the same sort of thing to get group information from -the PDC:

    The cupsaddsmb command copies the needed files +for convenient Windows client installations from the previously prepared CUPS +data directory to your [print$] share. Additionally, the PPD +associated with this printer is copied from /etc/cups/ppd/ to +[print$].

    root#root#  /usr/local/samba/bin/wbinfo -gcupsaddsmb -U root infotec_IS2027
-CEO+Domain Admins
-CEO+Domain Users
-CEO+Domain Guests
-CEO+Domain Computers
-CEO+Domain Controllers
-CEO+Cert Publishers
-CEO+Schema Admins
-CEO+Enterprise Admins
-CEO+Group Policy Creator Owners
    [type in password 'secret']

    The function 'getent' can now be used to get unified -lists of both local and PDC users and groups. -Try the following command:

    To share all printers and drivers, use the -a +parameter instead of a printer name.

    Probably you want to see what's going on. Use the +-v parameter to get a more verbose output:

    Probably you want to see what's going on. Use the +-v parameter to get a more verbose output:

    Note: The following line shave been wrapped so that information is not lost.
+ 
+root#  cupsaddsmb -v -U root infotec_IS2027
+    Password for root required to access localhost via SAMBA:
+    Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put
+       /var/spool/cups/tmp/3cd1cc66376c0 W32X86/infotec_IS2027.PPD;put /usr/share/cups/drivers/
+       ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLLr
+       W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP'
+    added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
+    added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
+    added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
+    Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
+    NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
+    putting file /var/spool/cups/tmp/3cd1cc66376c0 as \W32X86/infotec_IS2027.PPD (17394.6 kb/s)
+      (average 17395.2 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPS5.DLL as \W32X86/ADOBEPS5.DLL (10877.4 kb/s)
+      (average 11343.0 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPSU.DLL as \W32X86/ADOBEPSU.DLL (5095.2 kb/s)
+      (average 9260.4 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPSU.HLP as \W32X86/ADOBEPSU.HLP (8828.7 kb/s)
+      (average 9247.1 kb/s)
+
+    Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put
+      /var/spool/cups/tmp/3cd1cc66376c0 WIN40/infotec_IS2027.PPD;put
+      /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put
+      /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put
+      /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put
+      /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put
+      /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put
+      /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
+    added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
+    added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
+    added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
+    Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
+    NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
+    putting file /var/spool/cups/tmp/3cd1cc66376c0 as \WIN40/infotec_IS2027.PPD (26091.5 kb/s)
+      (average 26092.8 kb/s)
+    putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (11241.6 kb/s)
+      (average 11812.9 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (16640.6 kb/s)
+      (average 14679.3 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (11285.6 kb/s)
+      (average 14281.5 kb/s)
+    putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (823.5 kb/s)
+      (average 12944.0 kb/s)
+    putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (19226.2 kb/s)
+      (average 13169.7 kb/s)
+    putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (18666.1 kb/s)
+      (average 13266.7 kb/s)
+
+    Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows NT x86"
+       "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"'
+    cmd = adddriver "Windows NT x86" "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:
+       ADOBEPSU.HLP:NULL:RAW:NULL"
+    Printer Driver infotec_IS2027 successfully installed.
+
+    Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows 4.0"
+       "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:
+       ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
+    cmd = adddriver "Windows 4.0" "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:
+       ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
+    Printer Driver infotec_IS2027 successfully installed.
+
+    Running command: rpcclient localhost -N -U'root%secret'
+       -c 'setdriver infotec_IS2027 infotec_IS2027'
+    cmd = setdriver infotec_IS2027 infotec_IS2027
+    Succesfully set infotec_IS2027 to driver infotec_IS2027.
+
+    root# getent passwdroot#

    You should get a list that looks like your If you look closely, you'll discover your root password was transfered unencrypted over +the wire, so beware! Also, if you look further her, you'll discover error messages like +NT_STATUS_OBJECT_NAME_COLLISION in between. They occur, because +the directories /etc/passwd -list followed by the domain users with their new uids, gids, home -directories and default shells.

    WIN40 and W32X86 already +existed in the [print$] driver download share (from a previous driver +installation). They are harmless here.

    The same thing can be done for groups with the command

    Now your printer is prepared for the clients to use. From +a client, browse to the CUPS/Samba server, open the "Printers" +share, right-click on this printer and select "Install..." or +"Connect..." (depending on the Windows version you use). Now their +should be a new printer in your client's local "Printers" folder, +named (in my case) "infotec_IS2027 on kdebitshop"

    root# NOTE: +getent group

    cupsaddsmb will only reliably work i +with CUPS version 1.1.15 or higher +and Samba from 2.2.4. If it doesn't work, or if the automatic printer +driver download to the clients doesn't succeed, you can still manually +install the CUPS printer PPD on top of the Adobe PostScript driver on +clients and then point the client's printer queue to the Samba printer +share for connection, should you desire to use the CUPS networked +PostScript RIP functions.

    14.5.3.6. Fix the init.d startup scripts

    14.5.3.6.1. Linux

    The winbindd daemon needs to start up after the -smbd and nmbd daemons are running. -To accomplish this task, you need to modify the startup scripts of your system. They are located at /etc/init.d/smb in RedHat and -/etc/init.d/samba in Debian. -script to add commands to invoke this daemon in the proper sequence. My -startup script starts up smbd, -nmbd, and winbindd from the -/usr/local/samba/bin directory directly. The 'start' -function in the script looks like this:

    14.8. The CUPS Filter Chains

    The following diagrams reveal how CUPS handles print jobs.

    start() {
-        KIND="SMB"
-        echo -n $"Starting $KIND services: "
-        daemon /usr/local/samba/bin/smbd $SMBDOPTIONS
-        RETVAL=$?
-        echo
-        KIND="NMB"
-        echo -n $"Starting $KIND services: "
-        daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS
-        RETVAL2=$?
-        echo
-        KIND="Winbind"
-        echo -n $"Starting $KIND services: "
-        daemon /usr/local/samba/bin/winbindd
-        RETVAL3=$?
-        echo
-        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \
-           RETVAL=1
-        return $RETVAL
-}

    If you would like to run winbindd in dual daemon mode, replace -the line -

    #########################################################################
+#
+# CUPS in and of itself has this (general) filter chain (CAPITAL
+# letters are FILE-FORMATS or MIME types, other are filters (this is
+# true for pre-1.1.15 of pre-4.3 versions of CUPS and ESP PrintPro):
+#
+# SOMETHNG-FILEFORMAT
+#      |
+#      |
+#      V
+#     somethingtops
+#      |
+#      |
+#      V
+# APPLICATION/POSTSCRIPT
+#      |
+#      |
+#      V
+#     pstops
+#      |
+#      |
+#      V
+# APPLICATION/VND.CUPS-POSTSCRIPT
+#      |
+#      |
+#      V
+#     pstoraster   # as shipped with CUPS, independent from any Ghostscipt
+#      |           # installation on the system
+#      |  (= "postscipt interpreter")
+#      |
+#      V
+# APPLICATION/VND.CUPS-RASTER
+#      |
+#      |
+#      V
+#     rastertosomething  (f.e. Gimp-Print filters may be plugged in here)
+#      |   (= "raster driver")
+#      |
+#      V
+# SOMETHING-DEVICE-SPECIFIC
+#      |
+#      |
+#      V
+#     backend
+#
+#
+# ESP PrintPro has some enhanced "rastertosomething" filters as compared to
+# CUPS, and also a somewhat improved "pstoraster" filter.
+#
+# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
+#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
+#
+#########################################################################
            daemon /usr/local/samba/bin/winbindd
    - -in the example above with: - -
    #########################################################################
+#
+# This is how "cupsomatic" comes into play:
+# =========================================
+#
+# SOMETHNG-FILEFORMAT
+#      |
+#      |
+#      V
+#    somethingtops
+#      |
+#      |
+#      V
+# APPLICATION/POSTSCRIPT
+#      |
+#      |
+#      V
+#    pstops
+#      |
+#      |
+#      V
+# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
+#      |                                          |
+#      |                                          V
+#      V                                         cupsomatic
+#    pstoraster                                  (constructs complicated
+#      |  (= "postscipt interpreter")            Ghostscript commandline
+#      |                                         to let the file be
+#      V                                         processed by a
+# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=s.th."
+#      |                                         call...)
+#      |                                          |
+#      V                                          |
+#    rastertosomething                          V
+#      |    (= "raster driver")     +-------------------------+
+#      |                            | Ghostscript at work.... |
+#      V                            |                         |
+# SOMETHING-DEVICE-SPECIFIC         *-------------------------+
+#      |                                          |
+#      |                                          |
+#      V                                          |
+#    backend >------------------------------------+
+#      |
+#      |
+#      V
+#    THE PRINTER
+#
+#
+# Note, that cupsomatic "kidnaps" the printfile after the
+# "APPLICATION/VND.CUPS-POSTSCRPT" stage and deviates it through
+# the CUPS-external, systemwide Ghostscript installation, bypassing the
+# "pstoraster" filter (therefor also bypassing the CUPS-raster-drivers
+# "rastertosomething", and hands the rasterized file directly to the CUPS
+# backend...
+#
+# cupsomatic is not made by the CUPS developers. It is an independent
+# contribution to printing development, made by people from
+# Linuxprinting.org. (see also http://www.cups.org/cups-help.html)
+#
+# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
+#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
+#
+#########################################################################
            daemon /usr/local/samba/bin/winbindd -B
    .

    The 'stop' function has a corresponding entry to shut down the -services and looks like this:

    ######################################################################### +# +# And this is how it works for ESP PrintPro from 4.3: +# =================================================== +# +# SOMETHNG-FILEFORMAT +# | +# | +# V +# somethingtops +# | +# | +# V +# APPLICATION/POSTSCRIPT +# | +# | +# V +# pstops +# | +# | +# V +# APPLICATION/VND.CUPS-POSTSCRIPT +# | +# | +# V +# gsrip +# | (= "postscipt interpreter") +# | +# V +# APPLICATION/VND.CUPS-RASTER +# | +# | +# V +# rastertosomething (f.e. Gimp-Print filters may be plugged in here) +# | (= "raster driver") +# | +# V +# SOMETHING-DEVICE-SPECIFIC +# | +# | +# V +# backend +# +# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to +# CUPS and ESP PrintPro plug-in where rastertosomething is noted. +# +#########################################################################

    stop() {
-        KIND="SMB"
-        echo -n $"Shutting down $KIND services: "
-        killproc smbd
-        RETVAL=$?
-        echo
-        KIND="NMB"
-        echo -n $"Shutting down $KIND services: "
-        killproc nmbd
-        RETVAL2=$?
-        echo
-        KIND="Winbind"
-        echo -n $"Shutting down $KIND services: "
-        killproc winbindd
-        RETVAL3=$?
-        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb
-        echo ""
-        return $RETVAL
-}

    14.5.3.6.2. Solaris

    On solaris, you need to modify the -/etc/init.d/samba.server startup script. It usually -only starts smbd and nmbd but should now start winbindd too. If you -have samba installed in /usr/local/samba/bin, -the file could contains something like this:

    ######################################################################### +# +# This is how "cupsomatic" would come into play with ESP PrintPro: +# ================================================================ +# +# +# SOMETHNG-FILEFORMAT +# | +# | +# V +# somethingtops +# | +# | +# V +# APPLICATION/POSTSCRIPT +# | +# | +# V +# pstops +# | +# | +# V +# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+ +# | | +# | V +# V cupsomatic +# gsrip (constructs complicated +# | (= "postscipt interpreter") Ghostscript commandline +# | to let the file be +# V processed by a +# APPLICATION/VND.CUPS-RASTER "-sDEVICE=s.th." +# | call...) +# | | +# V | +# rastertosomething V +# | (= "raster driver") +-------------------------+ +# | | Ghostscript at work.... | +# V | | +# SOMETHING-DEVICE-SPECIFIC *-------------------------+ +# | | +# | | +# V | +# backend >------------------------------------+ +# | +# | +# V +# THE PRINTER +# +# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to +# CUPS and ESP PrintPro plug-in where rastertosomething is noted. +# +#########################################################################

    ##
-## samba.server
-##
-
-if [ ! -d /usr/bin ]
-then                    # /usr not mounted
-        exit
-fi
-
-killproc() {            # kill the named process(es)
-        pid=`/usr/bin/ps -e |
-             /usr/bin/grep -w $1 |
-             /usr/bin/sed -e 's/^  *//' -e 's/ .*//'`
-        [ "$pid" != "" ] && kill $pid
-}
- 
-# Start/stop processes required for samba server
-
-case "$1" in
-
-'start')
+>#########################################################################
 #
-# Edit these lines to suit your installation (paths, workgroup, host)
+# And this is how it works for CUPS from 1.1.15:
+# ==============================================
 #
-echo Starting SMBD
-   /usr/local/samba/bin/smbd -D -s \
-	/usr/local/samba/smb.conf
-
-echo Starting NMBD
-   /usr/local/samba/bin/nmbd -D -l \
-	/usr/local/samba/var/log -s /usr/local/samba/smb.conf
-
-echo Starting Winbind Daemon
-   /usr/local/samba/bin/winbindd
-   ;;
-
-'stop')
-   killproc nmbd
-   killproc smbd
-   killproc winbindd
-   ;;
-
-*)
-   echo "Usage: /etc/init.d/samba.server { start | stop }"
-   ;;
-esac

    Again, if you would like to run samba in dual daemon mode, replace -

       /usr/local/samba/bin/winbindd
    SOMETHNG-FILEFORMAT +# | +# | +# V +# somethingtops +# | +# | +# V +# APPLICATION/POSTSCRIPT +# | +# | +# V +# pstops +# | +# | +# V +# APPLICATION/VND.CUPS-POSTSCRIPT-----+ +# | +# +------------------v------------------------------+ +# | Ghostscript | +# | at work... | +# | (with | +# | "-sDEVICE=cups") | +# | | +# | (= "postscipt interpreter") | +# | | +# +------------------v------------------------------+ +# | +# | +# APPLICATION/VND.CUPS-RASTER >-------+ +# | +# | +# V +# rastertosomething - -in the script above with: - -
    something"
+#       Note the difference to "cupsomatic", which will *not* output
+#       CUPS-raster, but a final version of the printfile, ready to be
+#       sent to the printer. cupsomatic also doesn't use the "cups"
+#       devicemode in Ghostscript, but one of the classical devicemodes....
+#
+# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
+#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
+#
+#########################################################################
       /usr/local/samba/bin/winbindd -B

    ######################################################################### +# +# And this is how it works for CUPS from 1.1.15, with cupsomatic included: +# ======================================================================== +# +# SOMETHNG-FILEFORMAT +# | +# | +# V +# somethingtops +# | +# | +# V +# APPLICATION/POSTSCRIPT +# | +# | +# V +# pstops +# | +# | +# V +# APPLICATION/VND.CUPS-POSTSCRIPT-----+ +# | +# +------------------v------------------------------+ +# | Ghostscript . Ghostscript at work.... | +# | at work... . (with "-sDEVICE= | +# | (with . s.th." | +# | "-sDEVICE=cups") . | +# | . | +# | (CUPS standard) . (cupsomatic) | +# | . | +# | (= "postscript interpreter") | +# | . | +# +------------------v--------------v---------------+ +# | | +# | | +# APPLICATION/VND.CUPS-RASTER >-------+ | +# | | +# | | +# V | +# rastertosomething | +# | (= "raster driver") | +# | | +# V | +# SOMETHING-DEVICE-SPECIFIC >------------------------+ +# | +# | +# V +# backend +# +# +# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to +# CUPS and ESP PrintPro plug-in where rastertosomething is noted. +# +##########################################################################

    14.5.3.6.3. Restarting

    14.9. CUPS Print Drivers and Devices

    If you restart the smbd, nmbd, -and winbindd daemons at this point, you -should be able to connect to the samba server as a domain member just as -if you were a local user.

    14.5.3.7. Configure Winbind and PAM

    CUPS ships with good support for HP LaserJet type printers. You can install +the driver as follows: + +

    • If you have made it this far, you know that winbindd and samba are working -together. If you want to use winbind to provide authentication for other -services, keep reading. The pam configuration files need to be altered in -this step. (Did you remember to make backups of your original +> lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd +

    + +(The "-m" switch will retrieve the "laserjet.ppd" from the standard repository +for not-yet-installed-PPDs, which CUPS typically stores in /etc/pam.d files? If not, do it now.)

    /usr/share/cups/model    . Alternatively, you may use +"-P /absolute/filesystem/path/to/where/there/is/PPD/your.ppd").

    14.9.1. Further printing steps

    You will need a pam module to use winbindd with these other services. This -module will be compiled in the ../source/nsswitch directory -by invoking the command

    Always also consult the database on linuxprinting.org for all recommendations +about which driver is best used for each printer:

    root# make nsswitch/pam_winbind.sohttp://www.linuxprinting.org/printer_list.cgi

    from the ../source directory. The -pam_winbind.so file should be copied to the location of -your other pam security modules. On my RedHat system, this was the -/lib/security directory. On Solaris, the pam security -modules reside in /usr/lib/security.

    There select your model and click on "Show". You'll arrive at a page listing +all drivers working with your model. There will always be *one* +recommended one. Try this one first. In your case +("HP LaserJet 4 Plus"), you'll arrive here:

    root# cp ../samba/source/nsswitch/pam_winbind.so /lib/securityhttp://www.linuxprinting.org/show_printer.cgi?recnum=75104

    The recommended driver is "ljet4". It has a link to the page for the ljet4 +driver too:

    14.5.3.7.1. Linux/FreeBSD-specific PAM configuration

    http://www.linuxprinting.org/show_driver.cgi?driver=ljet4

    The /etc/pam.d/samba file does not need to be changed. I -just left this fileas it was:

    On the driver's page, you'll find important and detailed info about how to use +that driver within the various available spoolers. You can generate a PPD for +CUPS. The PPD contains all the info about how to use your model and the driver; +this is, once installed, working transparently for the user -- you'll only +need to choose resolution, paper size etc. from the web-based menu or from +the print dialog GUI or from the commandline...

    On the driver's page, choose to use the "PPD-O-Matic" online PPD generator +program. Select your model and click "Generate PPD file". When you safe the +appearing ASCII text file, don't use "cut'n'past" (as it could possiblly corrupt +line endings and tabs), but use "Save as..." in your browser's menu. Save it +at "/some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"

    Then install the printer:

    auth    required        /lib/security/pam_stack.so service=system-auth
-account required        /lib/security/pam_stack.so service=system-auth
    "lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E \ + -P /some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"

    The other services that I modified to allow the use of winbind -as an authentication service were the normal login on the console (or a terminal -session), telnet logins, and ftp service. In order to enable these -services, you may first need to change the entries in -/etc/xinetd.d (or /etc/inetd.conf). -RedHat 7.1 uses the new xinetd.d structure, in this case you need -to change the lines in /etc/xinetd.d/telnet -and Note, that for all the "Foomatic-PPDs" from Linuxprinting.org, you also need +a special "CUPS filter" named "cupsomatic". Get the latest version of +"cupsomatic" from:

    http://www.linuxprinting.org/cupsomatic

    This needs to be copied to /etc/xinetd.d/wu-ftp from

    /usr/lib/cups/filter/cupsomatic +and be made world executable. This filter is needed to read and act upon the +specially encoded Foomatic comments, embedded in the printfile, which in turn +are used to construct (transparently for you, the user) the complicated +ghostscript command line needed for your printer/driver combo.

    enable = no
    You can have a look at all the options for the Ghostscript commandline supported +by your printer and the ljet4 driver by going to the section "Execution details", +selecting your model (Laserjet 4 Plus) and clicking on "Show execution details". +This will bring up this web page:

    http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details

    to

    The ingenious thing is that the database is kept current. If there +is a bug fix and an improvement somewhere in the database, you will +always get the most current and stable and feature-rich driver by following +the steps described above.

    enable = yes

    -For ftp services to work properly, you will also need to either -have individual directories for the domain users already present on -the server, or change the home directory template to a general -directory for all domain users. These can be easily set using -the smb.conf global entry -template homedir.

    Till Kamppeter from MandrakeSoft is doing an excellent job here that too few +people are aware of. (So if you use it often, please send him a note showing +your appreciation).

    The /etc/pam.d/ftp file can be changed -to allow winbind ftp access in a manner similar to the -samba file. My The latest and greatest improvement now is support for "custom page sizes" +for all those printers which support it.

    "cupsomatic" is documented here:

    http://www.linuxprinting.org/cups-doc.html

    More printing tutorial info may be found here:

    http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/

    Note, that *all* the Foomatic drivers listed on Linuxprinting.org (now +approaching the "all-time high" number of 1.000 for the supported models) +are using a special filtering chain involving Ghostscript, as described +in this document.

    Summary - You need:

    A "foomatic+something" PPD is not enough to print with CUPS (but it is *one* important component)
    The "cupsomatic" filter script (Perl) in /etc/pam.d/ftp file was -changed to look like this:

    /usr/lib/cups/filters/
    Perl to make cupsomatic run
    Ghostscript (because it is called and controlled by the PPD/cupsomatic combo in a way to fit your printermodel/driver combo.
    Ghostscript *must*, depending on the driver/model, contain support for a certain "device" (as shown by "gs -h")

    auth       required     /lib/security/pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed
-auth       sufficient   /lib/security/pam_winbind.so
-auth       required     /lib/security/pam_stack.so service=system-auth
-auth       required     /lib/security/pam_shells.so
-account    sufficient   /lib/security/pam_winbind.so
-account    required     /lib/security/pam_stack.so service=system-auth
-session    required     /lib/security/pam_stack.so service=system-auth

    The /etc/pam.d/login file can be changed nearly the -same way. It now looks like this:

    In the case of the "hpijs" driver, you need a Ghostscript version, which +has "ijs" amongst its supported devices in "gs -h". In the case of +"hpijs+foomatic", a valid ghostscript commandline would be reading like this:

    auth       required     /lib/security/pam_securetty.so
-auth       sufficient   /lib/security/pam_winbind.so
-auth       sufficient   /lib/security/pam_unix.so use_first_pass
-auth       required     /lib/security/pam_stack.so service=system-auth
-auth       required     /lib/security/pam_nologin.so
-account    sufficient   /lib/security/pam_winbind.so
-account    required     /lib/security/pam_stack.so service=system-auth
-password   required     /lib/security/pam_stack.so service=system-auth
-session    required     /lib/security/pam_stack.so service=system-auth
-session    optional     /lib/security/pam_console.so
    gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs \ + -sIjsServer=hpijsPageSize -dDuplex=Duplex Model \ + -rResolution,PS:MediaPosition=InputSlot -dIjsUseOutputFD \ + -sOutputFile=- -

    In this case, I added the auth sufficient /lib/security/pam_winbind.so -lines as before, but also added the required pam_securetty.so -above it, to disallow root logins over the network. I also added a -sufficient /lib/security/pam_unix.so use_first_pass -line after the winbind.so line to get rid of annoying -double prompts for passwords.

    Note, that with CUPS and the "hpijs+foomatic" PPD (plus Perl and cupsomatic) +you don't need to remember this. You can choose the available print options +thru a GUI print command (like "glp" from ESP's commercially supported +PrintPro software, or KDE's "kprinter", or GNOME's "gtklp" or the independent +"xpp") or the CUPS web interface via human-readable drop-down selection +menus.

    14.5.3.7.2. Solaris-specific configuration

    The /etc/pam.conf needs to be changed. I changed this file so that my Domain -users can logon both locally as well as telnet.The following are the changes -that I made.You can customize the pam.conf file as per your requirements,but -be sure of those changes because in the worst case it will leave your system -nearly impossible to boot.

    If you use "ESP Ghostscript" (also under the GPL, provided by Easy Software +Products, the makers of CUPS, downloadable from +http://www.cups.org/software.html, +co-maintained by the developers of linuxprinting.org), you are guaranteed to +have in use the most uptodate, bug-fixed, enhanced and stable version of a Free +Ghostscript. It contains support for ~300 devices, whereas plain vanilla +GNU Ghostscript 7.05 only has ~200.

    If you print only one CUPS test page, from the web interface and when you try to +print a windows test page, it acts like the job was never sent: + +

    Can you print "standard" jobs from the CUPS machine?
    Are the jobs from Windows visible in the Web interface on CUPS (http://localhost:631/)?
    Most important: What kind of printer driver are you using on the Windows clients?

    #
-#ident	"@(#)pam.conf	1.14	99/09/16 SMI"
-#
-# Copyright (c) 1996-1999, Sun Microsystems, Inc.
-# All Rights Reserved.
-#
-# PAM configuration
-#
-# Authentication management
-#
-login   auth required   /usr/lib/security/pam_winbind.so
-login	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass 
-login	auth required 	/usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass 
-#
-rlogin  auth sufficient /usr/lib/security/pam_winbind.so
-rlogin  auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1
-rlogin	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
-#
-dtlogin auth sufficient /usr/lib/security/pam_winbind.so
-dtlogin	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
-#
-rsh	auth required	/usr/lib/security/$ISA/pam_rhosts_auth.so.1
-other   auth sufficient /usr/lib/security/pam_winbind.so
-other	auth required	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
-#
-# Account management
-#
-login   account sufficient      /usr/lib/security/pam_winbind.so
-login	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
-login	account required	/usr/lib/security/$ISA/pam_unix.so.1 
-#
-dtlogin account sufficient      /usr/lib/security/pam_winbind.so
-dtlogin	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
-dtlogin	account required	/usr/lib/security/$ISA/pam_unix.so.1 
-#
-other   account sufficient      /usr/lib/security/pam_winbind.so
-other	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
-other	account required	/usr/lib/security/$ISA/pam_unix.so.1 
-#
-# Session management
-#
-other	session required	/usr/lib/security/$ISA/pam_unix.so.1 
-#
-# Password management
-#
-#other   password sufficient     /usr/lib/security/pam_winbind.so
-other	password required	/usr/lib/security/$ISA/pam_unix.so.1 
-dtsession auth required	/usr/lib/security/$ISA/pam_unix.so.1
-#
-# Support for Kerberos V5 authentication (uncomment to use Kerberos)
-#
-#rlogin	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#login	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#dtlogin	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#other	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#dtlogin	account optional /usr/lib/security/$ISA/pam_krb5.so.1
-#other	account optional /usr/lib/security/$ISA/pam_krb5.so.1
-#other	session optional /usr/lib/security/$ISA/pam_krb5.so.1
-#other	password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass

    + +You can try to get a more detailed debugging info by setting "LogLevel debug" in +/etc/cups/cupsd.conf, re-start cupsd and investigate /var/log/cups/error_log +for the whereabouts of your Windows-originating printjobs:

    I also added a try_first_pass line after the winbind.so line to get rid of -annoying double prompts for passwords.

    what does the "auto-typing" line say? which is the "MIME type" CUPS thinks is arriving from the Windows clients?
    are there "filter" available for this MIME type?
    are there "filter rules" defined in "/etc/cups/mime.convs" for this MIME type?

    Now restart your Samba and try connecting through your application that you -configured in the pam.conf.

    14.6. Limitations14.10. Limiting the number of pages users can print

    Winbind has a number of limitations in its current - released version that we hope to overcome in future - releases:

    • Winbind is currently only available for - the Linux, Solaris and IRIX operating systems, although ports to other operating - systems are certainly possible. For such ports to be feasible, - we require the C library of the target operating system to - support the Name Service Switch and Pluggable Authentication - Modules systems. This is becoming more common as NSS and - PAM gain support among UNIX vendors.

    • The feature you want is dependent on the real print subsystem you're using. +Samba's part is always to receive the job files from the clients (filtered +*or* unfiltered) and hand it over to this printing subsystem.

      The mappings of Windows NT RIDs to UNIX ids - is not made algorithmically and depends on the order in which - unmapped users or groups are seen by winbind. It may be difficult - to recover the mappings of rid to UNIX id mapping if the file - containing this information is corrupted or destroyed.

    • Of course one could "hack" things with one's own scripts.

      Currently the winbind PAM module does not take - into account possible workstation and logon time restrictions - that may be been set for Windows NT users, this is - instead up to the PDC to enforce.

    14.7. Conclusion

    But there is CUPS (Common Unix Printing System). CUPS supports "quotas". +Quotas can be based on sizes of jobs or on the number of pages or both, +and are spanning any time period you want.

    The winbind system, through the use of the Name Service - Switch, Pluggable Authentication Modules, and appropriate - Microsoft RPC calls have allowed us to provide seamless - integration of Microsoft Windows NT domain users on a - UNIX system. The result is a great reduction in the administrative - cost of running a mixed UNIX and NT network.

    Chapter 15. Advanced Network Manangement

    This is an example command how root would set a print quota in CUPS, +assuming an existing printer named "quotaprinter":

      lpadmin -p quotaprinter -o job-quota-period=604800 -o job-k-limit=1024 \
+       -o job-page-limit=100

    This section attempts to document peripheral issues that are of great importance to network -administrators who want to improve network resource access control, to automate the user -environment, and to make their lives a little easier.

    15.1. Configuring Samba Share Access Controls

    This would limit every single user to print 100 pages or 1024 KB of +data (whichever comes first) within the last 604.800 seconds ( = 1 week).

    This section deals with how to configure Samba per share access control restrictions. -By default samba sets no restrictions on the share itself. Restrictions on the share itself -can be set on MS Windows NT4/200x/XP shares. This can be a very effective way to limit who can -connect to a share. In the absence of specific restrictions the default setting is to allow -the global user Everyone Full Control (ie: Full control, Change and Read).

    For CUPS to count correctly, the printfile needs to pass the CUPS "pstops" filter, +otherwise it uses a "dummy" count of "1". Some printfiles don't pass it +(eg: image files) but then those are mostly 1 page jobs anyway. This also means, +proprietary drivers for the target printer running on the client computers and +CUPS/Samba then spooling these files as "raw" (i.e. leaving them untouched, not +filtering them), will be counted as "1-pagers" too!

    At this time Samba does NOT provide a tool for configuring access control setting on the Share -itself. Samba does have the capacity to store and act on access control settings, but the only -way to create those settings is to use either the NT4 Server Manager or the Windows 200x MMC for -Computer Management.

    You need to send PostScript from the clients (i.e. run a PostScript driver there) +for having the chance to get accounting done. If the printer is a non-PostScript model, +you need to let CUPS do the job to convert the file to a print-ready format for the +target printer. This will be working for currently ~1.000 different printer models, see

         http://www.linuxprinting.org/printer_list.cgi

    Samba stores the per share access control settings in a file called share_info.tdb. -The location of this file on your system will depend on how samba was compiled. The default location -for samba's tdb files is under /usr/local/samba/var. If the tdbdump -utility has been compiled and installed on your system then you can examine the contents of this file -by: tdbdump share_info.tdb.

    15.1.1. Share Permissions Management

    Before CUPS-1.1.16 your only option was to use the Adobe PostScript +Driver on the Windows clients. The output of this driver was not always +passed thru the "pstops" filter on the CUPS/Samba side, and therefor was +not counted correctly (the reason is that it often --- depending on the +"PPD" being used --- did write a "PJL"-header in front of the real +PostScript which made CUPS to skip the pstops and go directy to +the "pstoraster" stage).

    The best tool for the task is platform dependant. Choose the best tool for your environmemt.

    15.1.1.1. Windows NT4 Workstation/Server

    From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver +for Windows NT/2K/XP clients" (it is tagged in the download area of +http://www.cups.org/ as the "cups-samba-1.1.16.tar.gz" package). +It is *not* working for Win9x/ME clients. But it:

    The tool you need to use to manage share permissions on a Samba server is the NT Server Manager. -Server Manager is shipped with Windows NT4 Server products but not with Windows NT4 Workstation. -You can obtain the NT Server Manager for MS Windows NT4 Workstation from Microsoft - see details below.

    it guarantees to not write an PJL-header
    it guarantees to still read and support all PJL-options named in the driver PPD with its own means
    it guarantees the file going thru the "pstops" filter on the CUPS/Samba server
    it guarantees to page-count correctly the printfile

    Instructions

    1. Launch the NT4 Server Manager, click on the Samba server you want to administer, then from the menu -select Computer, then click on the Shared Directories entry.

    2. You can read more about the setup of this combination in the +manpage for "cupsaddsmb" (only present with CUPS installed, only +current with CUPS 1.1.16).

      Now click on the share that you wish to manage, then click on the Properties tab, next click on - the Permissions tab. Now you can Add or change access control settings as you wish.

    15.1.1.2. Windows 200x/XP

    These are the items CUPS logs in the "page_log" for every single *page* of a job:

    On MS Windows NT4/200x/XP system access control lists on the share itself are set using native -tools, usually from filemanager. For example, in Windows 200x: right click on the shared folder, -then select 'Sharing', then click on 'Permissions'. The default Windows NT4/200x permission allows -Everyone Full Control on the Share.

    MS Windows 200x and later all comes with a tool called the 'Computer Management' snap-in for the -Microsoft Management Console (MMC). This tool is located by clicking on Control Panel -> -Administrative Tools -> Computer Management.

    Printer name
    User name
    Job ID
    Time of printing
    the page number
    the number of copies
    a billing info string (optional)

    Instructions

    1. After launching the MMC with the Computer Management snap-in, click on the menu item 'Action', - select 'Connect to another computer'. If you are not logged onto a domain you will be prompted - to enter a domain login user identifier and a password. This will authenticate you to the domain. - If you where already logged in with administrative privilidge this step is not offered.

    2. Here is an extract of my CUPS server's page_log file to illustrate +the format and included items:

      If the Samba server is not shown in the Select Computer box, then type in the name of the target -Samba server in the field 'Name:'. Now click on the [+] next to 'System Tools', then on the [+] -next to 'Shared Folders' in the left panel.

    3. infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 1 2 #marketing + infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 2 2 #marketing + infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 3 2 #marketing + infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 4 2 #marketing + infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 5 2 #marketing + infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 6 2 #marketing

      Now in the right panel, double-click on the share you wish to set access control permissions on. -Then click on the tab 'Share Permissions'. It is now possible to add access control entities -to the shared folder. Do NOT forget to set what type of access (full control, change, read) you -wish to assign for each entry.

    This was Job ID "40", printed on "infotec_IS2027" by user "kurt", a 6-page job +printed in 2 copies and billed to "#marketing"...

    What flaws or shortcomings are there?

    the ones named above CUPS really counts the job pages being *processsed in software* + (going thru the "RIP") rather than the physical sheets successfully + leaving the printing device -- if there is a jam while printing + the 5th sheet out of 1000 and the job is aborted by the printer, + the "page count" will still show the figure of 1000 for that job +

    Be careful. If you take away all permissions from the Everyone user without removing this user -then effectively no user will be able to access the share. This is a result of what is known as -ACL precidence. ie: Everyone with NO ACCESS means that MaryK who is part of the group Everyone -will have no access even if this user is given explicit full control access.

    all quotas are the same for all users (no flexibility to give the + boss a higher quota than the clerk) no support for groups +
    no means to read out the current balance or "used-up" number of current quota +
    a user having used up 99 sheets of 100 quota will still be able to send and print a 1.000 sheet job +
    a user being denied a job because of a filled-up quota doesn't get a meaningful + error message from CUPS other than "client-error-not-possible". +

    15.2. Remote Server Administration

    How do I get 'User Manager' and 'Server Manager'?

    Since I don't need to buy an NT4 Server, how do I get the 'User Manager for Domains', -the 'Server Manager'?

    Microsoft distributes a version of these tools called nexus for installation on Windows 9x / Me -systems. The tools set includes:

    • Server Manager

    • User Manager for Domains

    • Event Viewer

    But this is the best system out there currently. And there are +huge improvements under development:

    Click here to download the archived file ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE

    page counting will go into the "backends" (these talk + directly to the printer and will increase the count in sync with the + actual printing process -- a jam at the 5th sheet will lead to a stop in the counting)
    quotas will be handled more flexibly
    probably there will be support for users to inquire their "accounts" in advance
    probably there will be support for some other tools around this topic

    The Windows NT 4.0 version of the 'User Manager for -Domains' and 'Server Manager' are available from Microsoft via ftp -from ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE

    15.3. Network Logon Script Magic

    This section needs work. Volunteer contributions most welcome. Please send your patches or updates -to John Terpstra.

    Chapter 16. System and Account Policies

    16.1. Creating and Managing System Policies

    Under MS Windows platforms, particularly those following the release of MS Windows -NT4 and MS Windows 95) it is possible to create a type of file that would be placed -in the NETLOGON share of a domain controller. As the client logs onto the network -this file is read and the contents initiate changes to the registry of the client -machine. This file allows changes to be made to those parts of the registry that -affect users, groups of users, or machines.

    For MS Windows 9x/Me this file must be called Config.POL and may -be generated using a tool called poledit.exe, better known as the -Policy Editor. The policy editor was provided on the Windows 98 installation CD, but -dissappeared again with the introduction of MS Windows Me (Millenium Edition). From -comments from MS Windows network administrators it would appear that this tool became -a part of the MS Windows Me Resource Kit.

    MS Windows NT4 Server products include the System Policy Editor -under the Start -> Programs -> Administrative Tools menu item. -For MS Windows NT4 and later clients this file must be called NTConfig.POL.

    New with the introduction of MS Windows 2000 was the Microsoft Management Console -or MMC. This tool is the new wave in the ever changing landscape of Microsoft -methods for management of network access and security. Every new Microsoft product -or technology seems to obsolete the old rules and to introduce newer and more -complex tools and methods. To Microsoft's credit though, the MMC does appear to -be a step forward, but improved functionality comes at a great price.

    Other than the current stage of the CUPS development, I don't +know any other ready-to-use tool which you could consider.

    Before embarking on the configuration of network and system policies it is highly -advisable to read the documentation available from Microsoft's web site regarding +>You can download the driver files from Implementing Profiles and Policies in Windows NT 4.0 from http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp available from Microsoft. -There are a large number of documents in addition to this old one that should also -be read and understood. Try searching on the Microsoft web site for "Group Policies".

    What follows is a very discussion with some helpful notes. The information provided -here is incomplete - you are warned.

    16.1.1. Windows 9x/Me Policies

    http://www.cups.org/software.html. +It is a separate package from the CUPS base software files, tagged as "CUPS 1.1.16 +Windows NT/2k/XP Printer Driver for SAMBA (tar.gz, 192k)". The filename to +download is "cups-samba-1.1.16.tar.gz". Upon untar-/unzip-ping it will reveal +the files:

    You need the Win98 Group Policy Editor to set Group Profiles up under Windows 9x/Me. -It can be found on the Original full product Win98 installation CD under -tools/reskit/netadmin/poledit. Install this using the -Add/Remove Programs facility and then click on the 'Have Disk' tab.

    cups-samba.install + cups-samba.license + cups-samba.readme + cups-samba.remove + cups-samba.ss + +

    Use the Group Policy Editor to create a policy file that specifies the location of -user profiles and/or the My Documents etc. stuff. Then -save these settings in a file called These have been packaged with the ESP meta packager software "EPM". The +*.install and *.remove files are simple shell script, which untars the +*.ss (which is nothing else than a tar-archive) and puts its contents +into Config.POL that needs to -be placed in the root of the [NETLOGON] share. If Win98 is configured to log onto -the Samba Domain, it will automatically read this file and update the Win9x/Me registry -of the machine as it logs on.

    /usr/share/cups/drivers/. Its contents are 3 files:

    Further details are covered in the Win98 Resource Kit documentation.

    cupsdrvr.dll + cupsui.dll + cups.hlp + +

    If you do not take the right steps, then every so often Win9x/Me will check the -integrity of the registry and will restore it's settings from the back-up -copy of the registry it stores on each Win9x/Me machine. Hence, you will -occasionally notice things changing back to the original settings.

    Install the group policy handler for Win9x to pick up group policies. Look on the -Win98 CD in Due to a bug one CUPS release puts the \tools\reskit\netadmin\poledit. -Install group policies on a Win9x client by double-clicking +>cups.hlp +into /usr/share/drivers/ instead of grouppol.inf. 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/Me machine that uses group policies.

    /usr/share/cups/drivers/. To work around this, copy/move +the file after running the "./cups-samba.install" script manually to the right place:

    cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/ + +

    16.1.2. Windows NT4 Style Policy Files

    To create or edit ntconfig.pol you must use the NT Server -Policy Editor, poledit.exe which is included with NT4 Server -but not NT Workstation. There is a Policy Editor on a NT4 -Workstation but it is not suitable for creating Domain Policies. -Further, although the Windows 95 Policy Editor can be installed on an NT4 -Workstation/Server, it will not work with NT clients. However, the files from -the NT Server will run happily enough on an NT4 Workstation.

    You need poledit.exe, common.adm and winnt.adm. -It is convenient to put the two *.adm files in the c:\winnt\inf -directory which is where the binary will look for them unless told otherwise. Note also that that -directory is normally 'hidden'.

    This new CUPS PostScript driver is currently binary-only, but free +no source code is provided (yet). The reason is this: it has +been developed with the help of the Microsoft Driver Developer Kit (DDK) +and compiled with Microsoft Visual Studio 6. It is not clear to the driver +developers if they are allowed to distribute the whole of the source code +as Free Software. However, they will likely release the "diff" in source +code under the GPL, so anybody with a license of Visual Studio and a DDK +will be able to compile for him/herself.

    The Windows NT policy editor is also included with the Service Pack 3 (and -later) for Windows NT 4.0. Extract the files using servicepackname /x, -i.e. that's Nt4sp6ai.exe /x for service pack 6a. The policy editor, -poledit.exe 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.

    Once you have run the install script (and possibly manually moved the +"cups.hlp" file to "/usr/share/cups/drivers/"), the driver is ready to be +put into Samba's [print$] share (which often maps to "/etc/samba/drivers/" +and contains a subdir tree with WIN40 and W32X86 branches), by running +"cupsaddsmb" (see also "man cupsaddsmb" for CUPS 1.1.16). [Don't forget to +put root into the smbpasswd file by running "smbpasswd" should you run +this whole procedure for the first time.] Once the driver files are in the +[print$] share, they are ready to be downloaded and installed by the +Win NT/2k/XP clients.

    16.1.2.1. Registry Tattoos

    With NT4 style registry based policy changes, a large number of settings are not - automatically reversed as the user logs off. Since the settings that were in the - NTConfig.POL file were applied to the client machine registry and that apply to the - hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known - as tattooing. It can have serious consequences down-stream and the administrator must - be extremely careful not to lock out the ability to manage the machine at a later date. +>

    Win 9x/ME clients won't work with this driver. For these you'd + still need to use the ADOBE*.* drivers as previously. +

    It is not harming if you've still the ADOBE*.* driver files from + previous installations in the "/usr/share/cups/drivers/" directory. + The new cupsaddsmb (from 1.1.16) will automatically use the + "newest" installed driver (which here then is the CUPS drivers).

    16.1.3. MS Windows 200x / XP Professional Policies

    Windows NT4 System policies allows setting of registry parameters specific to -users, groups and computers (client workstations) that are members of the NT4 -style domain. Such policy file will work with MS Windows 2000 / XP clients also.

    New to MS Windows 2000 Microsoft introduced a new style of group policy that confers -a superset of capabilities compared with NT4 style policies. Obviously, the tool used -to create them is different, and the mechanism for implementing them is much changed.

    Should your Win clients have had the old ADOBE*.* files and the + Adobe PostScript drivers installed, the download and installation + of the new CUPS PostScript driver for Windows NT/2k/XP will fail + at first. +

    The older NT4 style registry based policies are known as Administrative Templates -in MS Windows 2000/XP Group Policy Objects (GPOs). The later includes ability to set various security -configurations, enforce Internet Explorer browser settings, change and redirect aspects of the -users' desktop (including: the location of My Documents files (directory), as -well as intrinsics of where menu items will appear in the Start menu). An additional new -feature is the ability to make available particular software Windows applications to particular -users and/or groups.

    It is not enough to "delete" the printer (as the driver files + will still be kept by the clients and re-used if you try to + re-install the printer). To really get rid of the Adobe driver + files on the clients, open the "Printers" folder (possibly via + "Start --> Settings --> Control Panel --> Printers"), right-click + onto the folder background and select "Server Properties". A + new dialog opens; select the "Drivers" tab; on the list select + the driver you want to delete and click on the "Delete" button. + (This will only work if there is no single printer left which + uses that particular driver -- you need to "delete" all printers + using this driver in the "Printers" folder first.) +

    Remember: NT4 policy files are named NTConfig.POL and are stored in the root -of the NETLOGON share on the domain controllers. A Windows NT4 user enters a username, a password -and selects the domain name to which the logon will attempt to take place. During the logon -process the client machine reads the NTConfig.POL file from the NETLOGON share on the authenticating -server, modifies the local registry values according to the settings in this file.

    Windows 2K GPOs are very feature rich. They are NOT stored in the NETLOGON share, rather part of -a Windows 200x policy file is stored in the Active Directory itself and the other part is stored -in a shared (and replicated) volume called the SYSVOL folder. This folder is present on all Active -Directory domain controllers. The part that is stored in the Active Directory itself is called the -group policy container (GPC), and the part that is stored in the replicated share called SYSVOL is -known as the group policy template (GPT).

    Once you have successfully downloaded the CUPS PostScript driver + to a client, you can easily switch all printers to this one + by proceeding as described elsewhere in the "Samba HOWTO + Collection" to change a driver for an existing printer. +

    What are the benefits with the "CUPS PostScript driver for Windows NT/2k/XP" +as compared to the Adobe drivers?

    With NT4 clients the policy file is read and executed upon only aas each user log onto the network. -MS Windows 200x policies are much more complex - GPOs are processed and applied at client machine -startup (machine specific part) and when the user logs onto the network the user specific part -is applied. In MS Windows 200x style policy management each machine and/or user may be subject -to any number of concurently applicable (and applied) policy sets (GPOs). Active Directory allows -the administrator to also set filters over the policy settings. No such equivalent capability -exists with NT4 style policy files.

    16.1.3.1. Administration of Win2K / XP Policies

    Instructions

    • Instead of using the tool called "The System Policy Editor", commonly called Poledit (from the -executable name poledit.exe), GPOs are created and managed using a Microsoft Management Console -(MMC) snap-in as follows:

        no hassle with the Adobe EULA +

      1. Go to the Windows 200x / XP menu Start->Programs->Administrative Tools - and select the MMC snap-in called "Active Directory Users and Computers"

        no hassle with the question "where do I get the ADOBE*.* driver files from?" +

      2. the Adobe drivers (depending on the printer PPD associated with them) + often put a PJL header in front of the core PostScript part of the print + file (thus the file starts with "1B%-12345X" or "escape%-12345X" + instead of "%!PS"). This leads to the CUPS daemon autotyping the + arriving file as a print-ready file, not requiring a pass thru the + "pstops" filter (to speak more technical, it is not regarded as the + generic MIME type "application/postscript", but as the more special + MIME type "application/cups.vnd-postscript"), which therefore also + leads to the page accounting in "/var/log/cups/page_log" not receiving + the exact mumber of pages; instead the dummy page number of "1" is + logged in a standard setup) +

      3. Select the domain or organizational unit (OU) that you wish to manage, then right click -to open the context menu for that object, select the properties item.

        the Adobe driver has more options to "mis-configure" the PostScript + generated by it (like setting it inadvertedly to "Optimize for Speed", + instead of "Optimize for Portability", which could lead to CUPS being + unable to process it) +

      4. the CUPS PostScript driver output sent by Windows clients to the CUPS + server will be guaranteed to be auto-typed as generic MIME type + "application/postscript", thusly passing thru the CUPS "pstops" filter + and logging the correct number of pages in the page_log for accounting + and quota purposes +

      5. the CUPS PostScript driver supports the sending of additional print + options by the Win NT/2k/XP clients, such as naming the CUPS standard + banner pages (or the custom ones, should they be installed at the time + of driver download), using the CUPS "page-label" option, setting a + job-priority and setting the scheduled time of printing (with the option + to support additional useful IPP job attributes in the future). +

      6. the CUPS PostScript driver supports the inclusion of the new + "*cupsJobTicket" comments at the beginnig of the PostScript file (which + could be used in the future for all sort of beneficial extensions on + the CUPS side, but which will not disturb any other application as those + will regard it as a comment and simply ignore it). +

      7. Now left click on the Group Policy tab, then left click on the New tab. Type a name -for the new policy you will create.

      8. the CUPS PostScript driver will be the heart of the fully fledged CUPS + IPP client for Windows NT/2k/XP to be released soon (probably alongside + the first Beta release for CUPS 1.2). +

    14.11. Advanced Postscript Printing from MS Windows

    Let the Windows Clients use a PostScript driver to deliver poistscript to +the samba print server (just like any Linux or Unix Client would also use +PostScript to send to the server)

    Make the Unix printing subsystem to which Samba sends the job convert the +incoming PostScript files to the native print format of the target printers +(would be PCL if you have an HP printer)

    Now if you are afraid that this would just mean using a *Generic* PostScript +driver for the clients that has no Simplex/Duplex selection, and no paper tray +choice, but you need them to be able to set up print jobs, with all the bells +and whistles of your printers:-

    Not possible with traditional spooling systems
    But perfectly supported by CUPS (which uses "PPD" files to + describe how to control the print options for PostScript and + non-PostScript devices alike... +

    Now left click on the Edit tab to commence the steps needed to create the GPO.

    CUPS PPDs are working perfectly on Windows clients who use Adobe PostScript +drivers (or the new CUPS PostScript driver for Windows NT/2K/XP). Clients can use +them to setup the job to their liking and CUPS will use the received job options +to make the (PCL-, ESC/P- or PostScript-) printer behave as required.

    All policy configuration options are controlled through the use of policy administrative -templates. These files have a .adm extension, both in NT4 as well as in Windows 200x / XP. -Beware however, since the .adm files are NOT interchangible across NT4 and Windows 200x. -The later introduces many new features as well as extended definition capabilities. It is -well beyond the scope of this documentation to explain how to program .adm files, for that -the adminsitrator is referred to the Microsoft Windows Resource Kit for your particular -version of MS Windows.

    If you want to have the additional benefit of page count logging and accounting +then the CUPS PostScript driver is the best choice (better than the Adobe one).

    If you want to make the drivers downloadable for the clients then "cupsaddsmb" is +your friend. It will setup the [print$] share on the Samba host to be ready to serve +the clients for a "point and print" driver installation.

    The MS Windows 2000 Resource Kit contains a tool called gpolmig.exe. This tool can be used -to migrate an NT4 NTConfig.POL file into a Windows 200x style GPO. Be VERY careful how you -use this powerful tool. Please refer to the resource kit manuals for specific usage information.

    What strings are attached?

    There are some. But, given the sheer CPU power you can buy nowadays, +these can be overcome easily. The strings:

    Well, if the CUPS/Samba side will have to print to many printers serving many users, +you probably will need to set up a second server (which can do automatic load balancing +with the first one, plus a degree of fail-over mechanism). Converting the incoming +PostScript jobs, "interpreting" them for non-PostScript printers, amounts to the work +of a "RIP" (Raster Image Processor) done in software. This requires more CPU and RAM +than for the mere "raw spooling" task your current setup is solving. It all depends +on the avarage and peak printing load the server should be able to handle.

    16.2. Managing Account/User Policies14.12. Auto-Deletion of CUPS spool files

    Policies can define a specific user's settings or the settings for a group of users. The resulting -policy file contains the registry settings for all users, groups, and computers that will be using -the policy file. Separate policy files for each user, group, or computer are not not necessary.

    If you create a policy that will be automatically downloaded from validating domain controllers, -you should name the file NTconfig.POL. As system administrator, you have the option of renaming the -policy file and, by modifying the Windows NT-based workstation, directing the computer to update -the policy from a manual path. You can do this by either manually changing the registry or by using -the System Policy Editor. This path can even be a local path such that each machine has its own policy file, -but if a change is necessary to all machines, this change must be made individually to each workstation.

    When a Windows NT4/200x/XP machine logs onto the network the NETLOGON share on the authenticating domain -controller for the presence of the NTConfig.POL file. If one exists it is downloaded, parsed and then -applied to the user's part of the registry.

    MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally, -acquire policy settings through Group Policy Objects (GPOs) that are defined and stored in Active Directory -itself. The key benefit of using AS GPOs is that they impose no registry tatooing effect. -This has considerable advanage compared with the use of NTConfig.POL (NT4) style policy updates.

    Samba print files pass thru two "spool" directories. One the incoming directory +managed by Samba, (set eg: in the path = /var/spool/samba directive in the [printers] +section of smb.conf). Second is the spool directory of your UNIX print subsystem. +For CUPS it is normally "/var/spool/cups/", as set by the cupsd.conf directive +"RequestRoot /var/spool/cups".

    Inaddition to user access controls that may be imposed or applied via system and/or group policies -in a manner that works in conjunction with user profiles, the user management environment under -MS Windows NT4/200x/XP allows per domain as well as per user account restrictions to be applied. -Common restrictions that are frequently used includes:

    I am not sure, which one of your directories keeps the files. From what you say, +it is most likely the Samba part.

    For the CUPS part, you may want to consult:

    http://localhost:631/sam.html#PreserveJobFileshttp://localhost:631/sam.html#PreserveJobHistoryhttp://localhost:631/sam.html#MaxJobs
    Logon Hours
    Password Aging
    Permitted Logon from certain machines only
    Account type (Local or Global)
    User Rights

    16.2.1. With Windows NT4/200x

    The tools that may be used to configure these types of controls from the MS Windows environment are: -The NT4 User Manager for domains, the NT4 System and Group Policy Editor, the registry editor (regedt32.exe). -Under MS Windows 200x/XP this is done using the Microsoft Managment Console (MMC) with approapriate -"snap-ins", the registry editor, and potentially also the NT4 System and Group Policy Editor.

    16.2.2. With a Samba PDC

    There are the settings described for your CUPS daemon, which could lead to completed +job files not being deleted.

    With a Samba Domain Controller, the new tools for managing of user account and policy information includes: -smbpasswd, pdbedit, smbgroupedit, net, rpcclient.. The administrator should read the -man pages for these tools and become familiar with their use.

    Chapter 17. Desktop Profile Management

    17.1. Roaming Profiles

    "PreserveJobHistory Yes" -- keeps some details of jobs in +cupsd's mind (well it keeps the "c12345", "c12346" etc. files +in the CUPS spool directory, which do a similar job as the +old-fashioned BSD-LPD control files). This is set to "Yes" +as a default.

    "PreserveJobFiles Yes" -- keeps the job files themselves in +cupsd's mind (well it keeps the "d12345", "d12346" etc. files +in the CUPS spool directory...). This is set to "No" as the +CUPS default.

    "MaxJobs 500" -- this directive controls the maximum number +of jobs that are kept in memory. Once the number of jobs +reaches the limit, the oldest completed job is automatically +purged from the system to make room for the new one. If all +of the known jobs are still pending or active then the new +job will be rejected. Setting the maximum to 0 disables this +functionality. The default setting is 0.

    (There are also additional settings for "MaxJobsPerUser" and +"MaxJobsPerPrinter"...)

    For everything to work as announced, you need to have three things:

    a Samba-smbd which is compiled against "libcups" (Check on Linux by running ldd `which smbd`) +

    Roaming profiles support is different for Win9x / Me and Windows NT4/200x.

    Before discussing how to configure roaming profiles, it is useful to see how -Windows 9x / Me and Windows NT4/200x clients implement these features.

    Windows 9x / Me 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 user's home share. This means that Win9X/Me -profiles are restricted to being stored in the user's home directory.

    Windows NT4/200x clients send a NetSAMLogon RPC request, which contains many fields, -including a separate field for the location of the user's profiles.

    17.1.1. Samba Configuration for Profile Handling

    This section documents how to configure Samba for MS Windows client profile support.

    17.1.1.1. NT4/200x User Profiles

    To support Windowns NT4/200x clients, in the [global] section of smb.conf set the -following (for example):

    	logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath
    a Samba-smb.conf setting of printing = cups - - This is typically implemented like: - -
    		logon path = \\%L\Profiles\%u
    another Samba-smb.conf setting of printcap = cups -where %L translates to the name of the Samba server and %u translates to the user name

    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. Please refer to the man page for smb.conf in respect of the different -symantics of %L and %N, as well as %U and %u.

    MS Windows NT/2K clients at times do not disconnect a connection to a server -between logons. It is recommended to NOT use the homes -meta-service name as part of the profile share path.

    Note, that in this case all other manually set printing-related +commands (like "print command", "lpq command", "lprm command", +"lppause command" or "lpresume command") are ignored and they +should normally have no influence what-so-ever on your printing.

    If you want to do things manually, replace the "printing = cups" +by "printing = bsd". Then your manually set commands may work +(haven't tested this), and a "print command = lp -d %P %s; rm %s" +may do what you need.

    You forgot to mention the CUPS version you're using. If you did +set things up as described in the man pages, then the Samba +spool files should be deleted. Otherwise it may be a bug. On +the CUPS side, you can control the behaviour as described +above.

    If you have more problems, post the output of these commands:

    grep -v ^# /etc/cups/cupsd.conf | grep -v ^$ + grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"

    (adapt paths as needed). These commands sanitize the files +and cut out the empty lines and lines with comments, providing +the "naked settings" in a compact way.

    17.1.1.2. Windows 9x / Me User Profiles

    Chapter 15. Unified Logons between Windows NT and UNIX using Winbind

    15.1. Abstract

    To support Windows 9x / Me 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.

    Integration of UNIX and Microsoft Windows NT through + a unified logon has been considered a "holy grail" in heterogeneous + computing environments for a long time. We present + winbind, a component of the Samba suite + of programs as a solution to the unified logon problem. Winbind + uses a UNIX implementation + of Microsoft RPC calls, Pluggable Authentication Modules, and the Name + Service Switch to allow Windows NT domain users to appear and operate + as UNIX users on a UNIX machine. This paper describes the winbind + system, explaining the functionality it provides, how it is configured, + and how it works internally.

    15.2. Introduction

    By using the logon home parameter, you are restricted to putting Win9x / Me -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:

    It is well known that UNIX and Microsoft Windows NT have + different models for representing user and group information and + use different technologies for implementing them. This fact has + made it difficult to integrate the two systems in a satisfactory + manner.

    One common solution in use today has been to create + identically named user accounts on both the UNIX and Windows systems + and use the Samba suite of programs to provide file and print services + between the two. This solution is far from perfect however, as + adding and deleting users on both sets of machines becomes a chore + and two sets of passwords are required both of which + can lead to synchronization problems between the UNIX and Windows + systems and confusion for users.

    We divide the unified logon problem for UNIX machines into + three smaller problems:

    	logon home = \\%L\%U\.profiles

    • then your Windows 9x / Me clients will dutifully put their clients in a subdirectory -of your home directory called .profiles (thus making them hidden).

      Obtaining Windows NT user and group information +

    • Not only that, but net use/home will also work, because of a feature in -Windows 9x / Me. 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 Authenticating Windows NT users +

    • Password changing for Windows NT users +

    Ideally, a prospective solution to the unified logon problem + would satisfy all the above components without duplication of + information on the UNIX machines and without creating additional + tasks for the system administrator when maintaining users and + groups on either system. The winbind system provides a simple + and elegant solution to all three components of the unified logon + problem.

    15.3. What Winbind Provides

    Winbind unifies UNIX and Windows NT account management by + allowing a UNIX box to become a full member of a NT domain. Once + this is done the UNIX box will see NT users and groups as if + they were native UNIX users and groups, allowing the NT domain + to be used in much the same manner that NIS+ is used within + UNIX-only environments.

    The end result is that whenever any + program on the UNIX machine asks the operating system to lookup + a user or group name, the query will be resolved by asking the + NT domain controller for the specified domain to do the lookup. + Because Winbind hooks into the operating system at a low level + (via the NSS name resolution modules in the C library) this + redirection to the NT domain controller is completely + transparent.

    Users on the UNIX machine can then use NT user and group + names as they would use "native" UNIX names. They can chown files + so that they are owned by NT domain users or even login to the + UNIX machine and run a UNIX X-Window session as a domain user.

    The only obvious indication that Winbind is being used is + that user and group names take the form DOMAIN\user and + DOMAIN\group. This is necessary as it allows Winbind to determine + that redirection to a domain controller is wanted for a particular + lookup and which trusted domain is being referenced.

    Additionally, Winbind provides an authentication service + that hooks into the Pluggable Authentication Modules (PAM) system + to provide authentication via a NT domain to any PAM enabled + applications. This capability solves the problem of synchronizing + passwords between systems since all passwords are stored in a single + location (on the domain controller).

    15.3.1. Target Uses

    Winbind is targeted at organizations that have an + existing NT based domain infrastructure into which they wish + to put UNIX workstations or servers. Winbind will allow these + organizations to deploy UNIX workstations without having to + maintain a separate account infrastructure. This greatly + simplifies the administrative overhead of deploying UNIX + workstations into a NT based organization.

    Another interesting way in which we expect Winbind to + be used is as a central part of UNIX based appliances. Appliances + that provide file and print services to Microsoft based networks + will be able to use Winbind to provide seamless integration of + the appliance into the domain.

    15.4. How Winbind Works

    The winbind system is designed around a client/server + architecture. A long running logon home.

    winbindd daemon + listens on a UNIX domain socket waiting for requests + to arrive. These requests are generated by the NSS and PAM + clients and processed sequentially.

    The technologies used to implement winbind are described + in detail below.

    15.4.1. Microsoft Remote Procedure Calls

    Over the last few years, efforts have been underway + by various Samba Team members to decode various aspects of + the Microsoft Remote Procedure Call (MSRPC) system. This + system is used for most network related operations between + Windows NT machines including remote management, user authentication + and print spooling. Although initially this work was done + to aid the implementation of Primary Domain Controller (PDC) + functionality in Samba, it has also yielded a body of code which + can be used for other purposes.

    Winbind uses various MSRPC calls to enumerate domain users + and groups and to obtain detailed information about individual + users or groups. Other MSRPC calls can be used to authenticate + NT domain users and to change user passwords. By directly querying + a Windows PDC for user and group information, winbind maps the + NT account information onto UNIX user and group names.

    17.1.1.3. Mixed Windows 9x / Me and Windows NT4/200x User Profiles

    You can support profiles for both Win9X and WinNT clients by setting both the -logon home and logon path parameters. For example:

    15.4.2. Microsoft Active Directory Services

    	logon home = \\%L\%u\.profiles
-	logon path = \\%L\profiles\%u

    Since late 2001, Samba has gained the ability to + interact with Microsoft Windows 2000 using its 'Native + Mode' protocols, rather than the NT4 RPC services. + Using LDAP and Kerberos, a domain member running + winbind can enumerate users and groups in exactly the + same way as a Win2k client would, and in so doing + provide a much more efficient and + effective winbind implementation. +

    17.1.2. Windows Client Profile Configuration Information15.4.3. Name Service Switch

    17.1.2.1. Windows 9x / Me Profile Setup

    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 preserve case = yes" and -"case sensitive = no" in order to maintain capital letters in shortcuts -in any of the profile folders.

    The Name Service Switch, or NSS, is a feature that is + present in many UNIX operating systems. It allows system + information such as hostnames, mail aliases and user information + to be resolved from different sources. For example, a standalone + UNIX workstation may resolve system information from a series of + flat files stored on the local filesystem. A networked workstation + may first attempt to resolve system information from local files, + and then consult a NIS database for user information or a DNS server + for hostname information.

    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.

    The NSS application programming interface allows winbind + to present itself as a source of system information when + resolving UNIX usernames and groups. Winbind uses this interface, + and information obtained from a Windows NT server using MSRPC + calls to provide a new source of account enumeration. Using standard + UNIX library calls, one can enumerate the users and groups on + a UNIX machine running winbind and see all users and groups in + a NT domain plus any trusted domain as though they were local + users and groups.

    1. The primary control file for NSS is + /etc/nsswitch.conf. + When a UNIX application makes a request to do a lookup + the C library looks in /etc/nsswitch.conf + for a line which matches the service type being requested, for + example the "passwd" service type is used when user or group names + are looked up. This config line species which implementations + of that service should be tried and in what order. If the passwd + config line is:

      On the Windows 9x / Me 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. -

    2. passwd: files example

      On the Windows 9x / Me 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. -

    then the C library will first load a module called + /lib/libnss_files.so followed by + the module /lib/libnss_example.so. The + C library will dynamically load each of these modules in turn + and call resolver functions within the modules to try to resolve + the request. Once the request is resolved the C library returns the + result to the application.

    Under Windows 9x / Me 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, it would seem!

    This NSS interface provides a very easy way for Winbind + to hook into the operating system. All that needs to be done + is to put libnss_winbind.so in /lib/ + then add "winbind" into /etc/nsswitch.conf at + the appropriate place. The C library will then call Winbind to + resolve user and group names.

    15.4.4. Pluggable Authentication Modules

    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.

    Pluggable Authentication Modules, also known as PAM, + is a system for abstracting authentication and authorization + technologies. With a PAM module it is possible to specify different + authentication methods for different system applications without + having to recompile these applications. PAM is also useful + for implementing a particular policy for authorization. For example, + a system administrator may only allow console logins from users + stored in the local password file but only allow users resolved from + a NIS database to log in over the network.

    Once the user has been successfully validated, the Windows 9x / Me 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'.

    Winbind uses the authentication management and password + management PAM interface to integrate Windows NT users into a + UNIX system. This allows Windows NT users to log in to a UNIX + machine and be authenticated against a suitable Primary Domain + Controller. These users can also change their passwords and have + this change take effect directly on the Primary Domain Controller. +

    Once the Windows 9x / Me 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.

    PAM is configured by providing control files in the directory + /etc/pam.d/ for each of the services that + require authentication. When an authentication request is made + by an application the PAM code in the C library looks up this + control file to determine what modules to load to do the + authentication check and in what order. This interface makes adding + a new authentication service for Winbind very easy, all that needs + to be done is that the pam_winbind.so module + is copied to /lib/security/ and the PAM + control files for relevant services are updated to allow + authentication via winbind. See the PAM documentation + for more details.

    15.4.5. User and Group ID Allocation

    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.

    When a user or group is created under Windows NT + is it allocated a numerical relative identifier (RID). This is + slightly different to UNIX which has a range of numbers that are + used to identify users, and the same range in which to identify + groups. It is winbind's job to convert RIDs to UNIX id numbers and + vice versa. When winbind is configured it is given part of the UNIX + user id space and a part of the UNIX group id space in which to + store Windows NT users and groups. If a Windows NT user is + resolved for the first time, it is allocated the next UNIX id from + the range. The same process applies for Windows NT groups. Over + time, winbind will have mapped all Windows NT users and groups + to UNIX user ids and group ids.

    If you have made the folders / files read-only on the samba server, -then you will get errors from the Windows 9x / Me 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 Windows 9x / Me machine, check the Unix file -permissions and ownership rights on the profile directory contents, -on the samba server.

    The results of this mapping are stored persistently in + an ID mapping database held in a tdb database). This ensures that + RIDs are mapped to UNIX IDs in a consistent way.

    15.4.6. Result Caching

    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".

    An active system can generate a lot of user and group + name lookups. To reduce the network cost of these lookups winbind + uses a caching scheme based on the SAM sequence number supplied + by NT domain controllers. User or group information returned + by a PDC is cached by winbind along with a sequence number also + returned by the PDC. This sequence number is incremented by + Windows NT whenever any user or group information is modified. If + a cached entry has expired, the sequence number is requested from + the PDC and compared against the sequence number of the cached entry. + If the sequence numbers do not match, then the cached information + is discarded and up to date information is requested directly + from the PDC.

    15.5. Installation and Configuration

    1. Many thanks to John Trostel jtrostel@snapserver.com +for providing the HOWTO for this section.

      instead of logging in under the [user, password, domain] dialog, - press escape. -

    2. This HOWTO describes how to get winbind services up and running +to control access and authenticate users on your Linux box using +the winbind services which come with SAMBA 2.2.2.

      15.5.1. Introduction

      run the regedit.exe program, and look in: -

      This HOWTO describes the procedures used to get winbind up and +running on my RedHat 7.1 system. Winbind is capable of providing access +and authentication control for Windows Domain users through an NT +or Win2K PDC for 'regular' services, such as telnet a nd ftp, as +well for SAMBA services.

      HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList -

      This HOWTO has been written from a 'RedHat-centric' perspective, so if +you are using another distribution, you may have to modify the instructions +somewhat to fit the way your distribution works.

      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]. - -

      • WARNINGWhy should I to this? - 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. -

        This allows the SAMBA administrator to rely on the + authentication mechanisms on the NT/Win2K PDC for the authentication + of domain members. NT/Win2K users no longer need to have separate + accounts on the SAMBA server. +

      • search for the user's .PWL password-caching file in the c:\windows - directory, and delete it. -

      • Who should be reading this document? +

        log off the windows 9x / Me client. -

        This HOWTO is designed for system administrators. If you are + implementing SAMBA on a file server and wish to (fairly easily) + integrate existing NT/Win2K users from your PDC onto the + SAMBA server, this HOWTO is for you. That said, I am no NT or PAM + expert, so you may find a better or easier way to accomplish + these tasks. +

    15.5.2. Requirements

    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 you have a samba configuration file that you are currently +using... BACK IT UP! If your system already uses PAM, +back up the /etc/pam.d directory +contents! If you haven't already made a boot disk, +MAKE ONE NOW!

    If all else fails, increase samba's debug log levels to between 3 and 10, -and / or run a packet trace program such as ethereal or netmon.exe, and -look for error messages.

    Messing with the pam configuration files can make it nearly impossible +to log in to yourmachine. That's why you want to be able to boot back +into your machine in single user mode and restore your +/etc/pam.d back to the original state they were in if +you get frustrated with the way things are going. ;-)

    If you have access to an Windows NT4/200x server, then first set up roaming profiles -and / or netlogons on the Windows NT4/200x server. Make a packet trace, or examine -the example packet traces provided with Windows NT4/200x server, and see what the -differences are with the equivalent samba trace.

    The latest version of SAMBA (version 3.0 as of this writing), now +includes a functioning winbindd daemon. Please refer to the +main SAMBA web page or, +better yet, your closest SAMBA mirror site for instructions on +downloading the source code.

    To allow Domain users the ability to access SAMBA shares and +files, as well as potentially other services provided by your +SAMBA machine, PAM (pluggable authentication modules) must +be setup properly on your machine. In order to compile the +winbind modules, you should have at least the pam libraries resident +on your system. For recent RedHat systems (7.1, for instance), that +means pam-0.74-22. For best results, it is helpful to also +install the development packages in pam-devel-0.74-22.

    15.5.3. Testing Things Out

    Before starting, it is probably best to kill off all the SAMBA +related daemons running on your server. Kill off all smbd, +nmbd, and winbindd processes that may +be running. To use PAM, you will want to make sure that you have the +standard PAM package (for RedHat) which supplies the /etc/pam.d +directory structure, including the pam modules are used by pam-aware +services, several pam libraries, and the /usr/doc +and /usr/man entries for pam. Winbind built better +in SAMBA if the pam-devel package was also installed. This package includes +the header files needed to compile pam-aware applications. For instance, +my RedHat system has both pam-0.74-22 and +pam-devel-0.74-22 RPMs installed.

    17.1.2.2. Windows NT4 Workstation15.5.3.1. Configure and compile SAMBA

    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.

    The configuration and compilation of SAMBA is pretty straightforward. +The first three steps may not be necessary depending upon +whether or not you have previously built the Samba binaries.

    root# autoconf
+root# make clean
+root# rm config.cache
+root# ./configure
+root# make
+root# make install

    There is a parameter that is now available for use with NT Profiles: -"logon drive". This should be set to This will, by default, install SAMBA in H: or any other drive, and -should be used in conjunction with the new "logon home" parameter.

    The entry for the NT4 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 -for those situations where it might be created.)

    In the profile directory, Windows NT4 creates more folders than Windows 9x / Me. -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.

    The case of the profile is significant. The file must be called -NTuser.DAT or, for a mandatory profile, NTuser.MAN.

    /usr/local/samba. +See the main SAMBA documentation if you want to install SAMBA somewhere else. +It will also build the winbindd executable and libraries.

    17.1.2.3. Windows 2000/XP Professional15.5.3.2. Configure nsswitch.conf and the +winbind libraries

    You must first convert the profile from a local profile to a domain -profile on the MS Windows workstation as follows:

    The libraries needed to run the winbindd daemon +through nsswitch need to be copied to their proper locations, so

    root# cp ../samba/source/nsswitch/libnss_winbind.so /lib

    • Log on as the LOCAL workstation administrator. -

    • I also found it necessary to make the following symbolic link:

      Right click on the 'My Computer' Icon, select 'Properties' -

    • root# ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2

      Click on the 'User Profiles' tab -

    • And, in the case of Sun solaris:

      Select the profile you wish to convert (click on it once) -

    • root# ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1 +root# ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1 +root# ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2

      Click on the button 'Copy To' -

    • Now, as root you need to edit /etc/nsswitch.conf to +allow user and group entries to be visible from the winbindd +daemon. My /etc/nsswitch.conf file look like +this after editing:

      In the "Permitted to use" box, click on the 'Change' button. - 

    • 	passwd:     files winbind
+	shadow:     files 
+	group:      files winbind

      Click on the 'Look in" area that lists the machine name, when you click - here it will open up a selection box. Click on the domain to which the - profile must be accessible. -

      +The libraries needed by the winbind daemon will be automatically +entered into the ldconfig cache the next time +your system reboots, but it +is faster (and you don't need to reboot) if you do it manually:

      root# /sbin/ldconfig -v | grep winbind

      You will need to log on if a logon box opens up. Eg: In the connect - as: MIDEARTH\root, password: mypassword.

      This makes libnss_winbind available to winbindd +and echos back a check to you.

    • To make the profile capable of being used by anyone select 'Everyone' -

    • Click OK. The Selection box will close. -

    • Now click on the 'Ok' button to create the profile in the path you - nominated. -

    15.5.3.3. Configure smb.conf

    Done. You now have a profile that can be editted using the samba-3.0.0 +>Several parameters are needed in the smb.conf file to control +the behavior of winbindd. Configure profiles tool.

    smb.conf These are described in more detail in +the winbindd(8) man page. My +smb.conf file was modified to +include the following entries in the [global] section:

    [global]
+     <...>
+     # separate domain and username with '+', like DOMAIN+username
+     winbind separator = +
+     # use uids from 10000 to 20000 for domain users
+     winbind uid = 10000-20000
+     # use gids from 10000 to 20000 for domain groups
+     winbind gid = 10000-20000
+     # allow enumeration of winbind users and groups
+     winbind enum users = yes
+     winbind enum groups = yes
+     # give winbind users a real shell (only needed if they have telnet access)
+     template homedir = /home/winnt/%D/%U
+     template shell = /bin/bash

    Under NT/2K the use of mandotory profiles forces the use of MS Exchange -storage of mail data. That keeps desktop profiles usable.

    15.5.3.4. Join the SAMBA server to the PDC domain

    Enter the following command to make the SAMBA server join the +PDC domain, where DOMAIN is the name of +your Windows domain and Administrator is +a domain user who has administrative privileges in the domain.

    root# /usr/local/samba/bin/net join -S PDC -U Administrator

    • This is a security check new to Windows XP (or maybe only -Windows XP service pack 1). It can be disabled via a group policy in -Active Directory. The policy is:

      "Computer Configuration\Administrative Templates\System\User -Profiles\Do not check for user ownership of Roaming Profile Folders"

      ...and it should be set to "Enabled". -Does the new version of samba have an Active Directory analogue? If so, -then you may be able to set the policy through this.

      If you cannot set group policies in samba, then you may be able to set -the policy locally on each machine. If you want to try this, then do -the following (N.B. I don't know for sure that this will work in the -same way as a domain group policy):

    • On the XP workstation log in with an Administrator account.

    • The proper response to the command should be: "Joined the domain +DOMAIN" where DOMAIN +is your DOMAIN name.

    • Eventually, you will want to modify your smb startup script to +automatically invoke the winbindd daemon when the other parts of +SAMBA start, but it is possible to test out just the winbind +portion first. To start up winbind services, enter the following +command as root:

      Type: "mmc"

    • root# /usr/local/samba/bin/winbindd

      Click: "OK"

    • Winbindd can now also run in 'dual daemon mode'. This will make it +run as 2 processes. The first will answer all requests from the cache, +thus making responses to clients faster. The other will +update the cache for the query that the first has just responded. +Advantage of this is that responses stay accurate and are faster. +You can enable dual daemon mode by adding '-B' to the commandline:

      A Microsoft Management Console should appear.

    • root# /usr/local/samba/bin/winbindd -B

      Click: File, "Add/Remove Snap-in...", "Add"

    • I'm always paranoid and like to make sure the daemon +is really running...

      Double-Click: "Group Policy"

    • root# ps -ae | grep winbindd

      Click: "Finish", "Close"

    • This command should produce output like this, if the daemon is running

      Click: "OK"

    • 3025 ? 00:00:00 winbindd

      In the "Console Root" window:

    • Now... for the real test, try to get some information about the +users on your PDC

      Expand: "Local Computer Policy", "Computer Configuration",

    • root# /usr/local/samba/bin/wbinfo -u

      "Administrative Templates", "System", "User Profiles"

    • +This should echo back a list of users on your Windows users on +your PDC. For example, I get the following response:

      Double-Click: "Do not check for user ownership of Roaming Profile

    • CEO+Administrator
+CEO+burdell
+CEO+Guest
+CEO+jt-ad
+CEO+krbtgt
+CEO+TsInternetUser

      Folders"

    • Obviously, I have named my domain 'CEO' and my winbind +separator is '+'.

      Select: "Enabled"

    • You can do the same sort of thing to get group information from +the PDC:

      Click: OK"

    • root# /usr/local/samba/bin/wbinfo -g
+CEO+Domain Admins
+CEO+Domain Users
+CEO+Domain Guests
+CEO+Domain Computers
+CEO+Domain Controllers
+CEO+Cert Publishers
+CEO+Schema Admins
+CEO+Enterprise Admins
+CEO+Group Policy Creator Owners

      Close the whole console. You do not need to save the settings (this - refers to the console settings rather than the policies you have - changed).

    • The function 'getent' can now be used to get unified +lists of both local and PDC users and groups. +Try the following command:

      Reboot

    17.1.3. Sharing Profiles between W9x/Me and NT4/200x/XP workstations

    root# getent passwd

    Sharing of desktop profiles between Windows versions is NOT recommended. -Desktop profiles are an evolving phenomenon and profiles for later versions -of MS Windows clients add features that may interfere with earlier versions -of MS Windows clients. Probably the more salient reason to NOT mix profiles -is that when logging off an earlier version of MS Windows the older format -of profile contents may overwrite information that belongs to the newer -version resulting in loss of profile information content when that user logs -on again with the newer version of MS Windows.

    You should get a list that looks like your /etc/passwd +list followed by the domain users with their new uids, gids, home +directories and default shells.

    If you then want to share the same Start Menu / Desktop with W9x/Me, you will -need to specify a common location for the profiles. The smb.conf parameters -that need to be common are logon path and -logon home.

    The same thing can be done for groups with the command

    If you have this set up correctly, you will find separate user.DAT and -NTuser.DAT files in the same profile directory.

    root# getent group

    17.1.4. Profile Migration from Windows NT4/200x Server to Samba

    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.

    17.1.4.1. Windows NT4 Profile Management Tools15.5.3.6. Fix the init.d startup scripts

    15.5.3.6.1. Linux

    Unfortunately, the Resource Kit information is specific to the version of MS Windows -NT4/200x. The correct resource kit is required for each platform.

    Here is a quick guide:

    The winbindd daemon needs to start up after the +smbd and nmbd daemons are running. +To accomplish this task, you need to modify the startup scripts of your system. They are located at /etc/init.d/smb in RedHat and +/etc/init.d/samba in Debian. +script to add commands to invoke this daemon in the proper sequence. My +startup script starts up smbd, +nmbd, and winbindd from the +/usr/local/samba/bin directory directly. The 'start' +function in the script looks like this:

    start() {
+        KIND="SMB"
+        echo -n $"Starting $KIND services: "
+        daemon /usr/local/samba/bin/smbd $SMBDOPTIONS
+        RETVAL=$?
+        echo
+        KIND="NMB"
+        echo -n $"Starting $KIND services: "
+        daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS
+        RETVAL2=$?
+        echo
+        KIND="Winbind"
+        echo -n $"Starting $KIND services: "
+        daemon /usr/local/samba/bin/winbindd
+        RETVAL3=$?
+        echo
+        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \
+           RETVAL=1
+        return $RETVAL
+}

    • On your NT4 Domain Controller, right click on 'My Computer', then -select the tab labelled 'User Profiles'.

    • If you would like to run winbindd in dual daemon mode, replace +the line +
              daemon /usr/local/samba/bin/winbindd
      + +in the example above with: + +
              daemon /usr/local/samba/bin/winbindd -B
      .

      Select a user profile you want to migrate and click on it.

      The 'stop' function has a corresponding entry to shut down the +services and looks like this:

      stop() {
+        KIND="SMB"
+        echo -n $"Shutting down $KIND services: "
+        killproc smbd
+        RETVAL=$?
+        echo
+        KIND="NMB"
+        echo -n $"Shutting down $KIND services: "
+        killproc nmbd
+        RETVAL2=$?
+        echo
+        KIND="Winbind"
+        echo -n $"Shutting down $KIND services: "
+        killproc winbindd
+        RETVAL3=$?
+        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb
+        echo ""
+        return $RETVAL
+}

    15.5.3.6.2. Solaris

    On solaris, you need to modify the +/etc/init.d/samba.server startup script. It usually +only starts smbd and nmbd but should now start winbindd too. If you +have samba installed in /usr/local/samba/bin, +the file could contains something like this:

    ##
+## samba.server
+##
+
+if [ ! -d /usr/bin ]
+then                    # /usr not mounted
+        exit
+fi
+
+killproc() {            # kill the named process(es)
+        pid=`/usr/bin/ps -e |
+             /usr/bin/grep -w $1 |
+             /usr/bin/sed -e 's/^  *//' -e 's/ .*//'`
+        [ "$pid" != "" ] && kill $pid
+}
+ 
+# Start/stop processes required for samba server
+
+case "$1" in
+
+'start')
+#
+# Edit these lines to suit your installation (paths, workgroup, host)
+#
+echo Starting SMBD
+   /usr/local/samba/bin/smbd -D -s \
+	/usr/local/samba/smb.conf
+
+echo Starting NMBD
+   /usr/local/samba/bin/nmbd -D -l \
+	/usr/local/samba/var/log -s /usr/local/samba/smb.conf
+
+echo Starting Winbind Daemon
+   /usr/local/samba/bin/winbindd
+   ;;
+
+'stop')
+   killproc nmbd
+   killproc smbd
+   killproc winbindd
+   ;;
+
+*)
+   echo "Usage: /etc/init.d/samba.server { start | stop }"
+   ;;
+esac

    I am using the term "migrate" lossely. You can copy a profile to -create a group profile. You can give the user 'Everyone' rights to the -profile you copy this to. That is what you need to do, since your samba -domain is not a member of a trust relationship with your NT4 PDC.

  • Click the 'Copy To' button.

  • In the box labelled 'Copy Profile to' add your new path, eg: - c:\temp\foobarAgain, if you would like to run samba in dual daemon mode, replace +

       /usr/local/samba/bin/winbindd
    + +in the script above with: + +
       /usr/local/samba/bin/winbindd -B

  • Click on the button labelled 'Change' in the "Permitted to use" box.

  • Click on the group 'Everyone' and then click OK. This closes the - 'chose user' box.

  • Now click OK.

    • Follow the above for every profile you need to migrate.

    17.1.4.2. Side bar Notes

    You should obtain the SID of your NT4 domain. You can use smbpasswd to do -this. Read the man page.

    15.5.3.6.3. Restarting

    With Samba-3.0.0 alpha code you can import all you NT4 domain accounts -using the net samsync method. This way you can retain your profile -settings as well as all your users.

    If you restart the smbd, nmbd, +and winbindd daemons at this point, you +should be able to connect to the samba server as a domain member just as +if you were a local user.

    17.1.4.3. moveuser.exe

    The W2K professional resource kit has moveuser.exe. moveuser.exe changes -the security of a profile from one user to another. This allows the account -domain to change, and/or the user name to change.

    17.1.4.4. Get SID15.5.3.7. Configure Winbind and PAM

    You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 -Resource Kit.

    Windows NT 4.0 stores the local profile information in the registry under -the following key: -HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

    Under the ProfileList key, there will be subkeys named with the SIDs of the -users who have logged on to this computer. (To find the profile information -for the user whose locally cached profile you want to move, find the SID for -the user with the GetSID.exe utility.) Inside of the appropriate user's -subkey, you will see a string value named ProfileImagePath.

    17.2. Mandatory profiles

    A Mandatory Profile is a profile that the user does NOT have the ability to overwrite. -During the user's session it may be possible to change the desktop environment, but -as the user logs out all changes made will be lost. If it is desired to NOT allow the -user any ability to change the desktop environment then this must be done through -policy settings. See previous chapter.

    Under NO circumstances should the profile directory (or it's contents) be made read-only -as this may render the profile un-usable.

    For MS Windows NT4/200x/XP the above method can be used to create mandatory profiles -also. To convert a group profile into a mandatory profile simply locate the NTUser.DAT -file in the copied profile and rename it to NTUser.MAN.

    For MS Windows 9x / Me it is the User.DAT file that must be renamed to User.MAN to -affect a mandatory profile.

    17.3. Creating/Managing Group Profiles

    Most organisations are arranged into departments. There is a nice benenfit in -this fact since usually most users in a department will require the same desktop -applications and the same desktop layout. MS Windows NT4/200x/XP will allow the -use of Group Profiles. A Group Profile is a profile that is created firstly using -a template (example) user. Then using the profile migration tool (see above) the -profile is assigned access rights for the user group that needs to be given access -to the group profile.

    If you have made it this far, you know that winbindd and samba are working +together. If you want to use winbind to provide authentication for other +services, keep reading. The pam configuration files need to be altered in +this step. (Did you remember to make backups of your original +/etc/pam.d files? If not, do it now.)

    The next step is rather important. PLEASE NOTE: Instead of assigning a group profile -to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned -the now modified profile.

    You will need a pam module to use winbindd with these other services. This +module will be compiled in the ../source/nsswitch directory +by invoking the command

    root# make nsswitch/pam_winbind.so

    Be careful with group profiles, if the user who is a member of a group also - has a personal profile, then the result will be a fusion (merge) of the two. -

    17.4. Default Profile for Windows Users

    MS Windows 9x / Me and NT4/200x/XP will use a default profile for any user for whom -a profile does not already exist. Armed with a knowledge of where the default profile -is located on the Windows workstation, and knowing which registry keys affect the path -from which the default profile is created, it is possible to modify the default profile -to one that has been optimised for the site. This has significant administrative -advantages.

    from the ../source directory. The +pam_winbind.so file should be copied to the location of +your other pam security modules. On my RedHat system, this was the +/lib/security directory. On Solaris, the pam security +modules reside in /usr/lib/security.

    root# cp ../samba/source/nsswitch/pam_winbind.so /lib/security

    17.4.1. MS Windows 9x/Me
    15.5.3.7.1. Linux/FreeBSD-specific PAM configuration

    To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System -Policy Editor or change the registry directly.

    The /etc/pam.d/samba file does not need to be changed. I +just left this fileas it was:

    To enable default per user profiles in Windows 9x / Me, launch the System Policy Editor, then -select File -> Open Registry, then click on the Local Computer icon, click on Windows 98 System, -select User Profiles, click on the enable box. Do not forget to save the registry changes.

    auth    required        /lib/security/pam_stack.so service=system-auth
+account required        /lib/security/pam_stack.so service=system-auth

    To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive +>The other services that I modified to allow the use of winbind +as an authentication service were the normal login on the console (or a terminal +session), telnet logins, and ftp service. In order to enable these +services, you may first need to change the entries in HKEY_LOCAL_MACHINE\Network\Logon. Now add a DWORD type key with the name -"User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0.

    17.4.1.1. How User Profiles Are Handled in Windows 9x / Me?

    When a user logs on to a Windows 9x / Me machine, the local profile path, -/etc/xinetd.d (or HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList, is checked -for an existing entry for that user:

    /etc/inetd.conf    ). +RedHat 7.1 uses the new xinetd.d structure, in this case you need +to change the lines in /etc/xinetd.d/telnet +and /etc/xinetd.d/wu-ftp from

    If the user has an entry in this registry location, Windows 9x / Me checks for a locally cached -version of the user profile. Windows 9x / Me also checks the user's home directory (or other -specified directory if the location has been modified) on the server for the User Profile. -If a profile exists in both locations, the newer of the two is used. If the User Profile exists -on the server, but does not exist on the local machine, the profile on the server is downloaded -and used. If the User Profile only exists on the local machine, that copy is used.

    enable = no

    If a User Profile is not found in either location, the Default User Profile from the Windows 9x / Me -machine is used and is copied to a newly created folder for the logged on user. At log off, any -changes that the user made are written to the user's local profile. If the user has a roaming -profile, the changes are written to the user's profile on the server.

    17.4.2. MS Windows NT4 Workstation

    to

    On MS Windows NT4 the default user profile is obtained from the location -%SystemRoot%\Profiles which in a default installation will translate to -C:\WinNT\Profiles. Under this directory on a clean install there will be -three (3) directories: 

    enable = yes

    +For ftp services to work properly, you will also need to either +have individual directories for the domain users already present on +the server, or change the home directory template to a general +directory for all domain users. These can be easily set using +the Administrator, All Users, Default Usersmb.conf global entry +template homedir.

    The All Users directory contains menu settings that are common across all -system users. The /etc/pam.d/ftp file can be changed +to allow winbind ftp access in a manner similar to the +samba file. My Default User directory contains menu entries that are -customisable per user depending on the profile settings chosen/created.

    /etc/pam.d/ftp     file was +changed to look like this:

    When a new user first logs onto an MS Windows NT4 machine a new profile is created from:

    auth       required     /lib/security/pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed
+auth       sufficient   /lib/security/pam_winbind.so
+auth       required     /lib/security/pam_stack.so service=system-auth
+auth       required     /lib/security/pam_shells.so
+account    sufficient   /lib/security/pam_winbind.so
+account    required     /lib/security/pam_stack.so service=system-auth
+session    required     /lib/security/pam_stack.so service=system-auth

    The /etc/pam.d/login file can be changed nearly the +same way. It now looks like this:

    auth       required     /lib/security/pam_securetty.so
+auth       sufficient   /lib/security/pam_winbind.so
+auth       sufficient   /lib/security/pam_unix.so use_first_pass
+auth       required     /lib/security/pam_stack.so service=system-auth
+auth       required     /lib/security/pam_nologin.so
+account    sufficient   /lib/security/pam_winbind.so
+account    required     /lib/security/pam_stack.so service=system-auth
+password   required     /lib/security/pam_stack.so service=system-auth
+session    required     /lib/security/pam_stack.so service=system-auth
+session    optional     /lib/security/pam_console.so

    All Users settings
    Default User settings (contains the default NTUser.DAT file)

    In this case, I added the auth sufficient /lib/security/pam_winbind.so +lines as before, but also added the required pam_securetty.so +above it, to disallow root logins over the network. I also added a +sufficient /lib/security/pam_unix.so use_first_pass +line after the winbind.so line to get rid of annoying +double prompts for passwords.

    15.5.3.7.2. Solaris-specific configuration

    The /etc/pam.conf needs to be changed. I changed this file so that my Domain +users can logon both locally as well as telnet.The following are the changes +that I made.You can customize the pam.conf file as per your requirements,but +be sure of those changes because in the worst case it will leave your system +nearly impossible to boot.

    #
+#ident	"@(#)pam.conf	1.14	99/09/16 SMI"
+#
+# Copyright (c) 1996-1999, Sun Microsystems, Inc.
+# All Rights Reserved.
+#
+# PAM configuration
+#
+# Authentication management
+#
+login   auth required   /usr/lib/security/pam_winbind.so
+login	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass 
+login	auth required 	/usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass 
+#
+rlogin  auth sufficient /usr/lib/security/pam_winbind.so
+rlogin  auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1
+rlogin	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+#
+dtlogin auth sufficient /usr/lib/security/pam_winbind.so
+dtlogin	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+#
+rsh	auth required	/usr/lib/security/$ISA/pam_rhosts_auth.so.1
+other   auth sufficient /usr/lib/security/pam_winbind.so
+other	auth required	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+#
+# Account management
+#
+login   account sufficient      /usr/lib/security/pam_winbind.so
+login	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
+login	account required	/usr/lib/security/$ISA/pam_unix.so.1 
+#
+dtlogin account sufficient      /usr/lib/security/pam_winbind.so
+dtlogin	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
+dtlogin	account required	/usr/lib/security/$ISA/pam_unix.so.1 
+#
+other   account sufficient      /usr/lib/security/pam_winbind.so
+other	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
+other	account required	/usr/lib/security/$ISA/pam_unix.so.1 
+#
+# Session management
+#
+other	session required	/usr/lib/security/$ISA/pam_unix.so.1 
+#
+# Password management
+#
+#other   password sufficient     /usr/lib/security/pam_winbind.so
+other	password required	/usr/lib/security/$ISA/pam_unix.so.1 
+dtsession auth required	/usr/lib/security/$ISA/pam_unix.so.1
+#
+# Support for Kerberos V5 authentication (uncomment to use Kerberos)
+#
+#rlogin	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+#login	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+#dtlogin	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+#other	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+#dtlogin	account optional /usr/lib/security/$ISA/pam_krb5.so.1
+#other	account optional /usr/lib/security/$ISA/pam_krb5.so.1
+#other	session optional /usr/lib/security/$ISA/pam_krb5.so.1
+#other	password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass

    When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain -the following steps are followed in respect of profile handling:

    I also added a try_first_pass line after the winbind.so line to get rid of +annoying double prompts for passwords.

    Now restart your Samba and try connecting through your application that you +configured in the pam.conf.

    15.6. Limitations

    Winbind has a number of limitations in its current + released version that we hope to overcome in future + releases:

      • The users' account information which is obtained during the logon process contains - the location of the users' desktop profile. The profile path may be local to the - machine or it may be located on a network share. If there exists a profile at the location - of the path from the user account, then this profile is copied to the location - %SystemRoot%\Profiles\%USERNAME%. This profile then inherits the - settings in the All Users profile in the %SystemRoot%\Profiles - location. -

        Winbind is currently only available for + the Linux, Solaris and IRIX operating systems, although ports to other operating + systems are certainly possible. For such ports to be feasible, + we require the C library of the target operating system to + support the Name Service Switch and Pluggable Authentication + Modules systems. This is becoming more common as NSS and + PAM gain support among UNIX vendors.

      • If the user account has a profile path, but at it's location a profile does not exist, - then a new profile is created in the %SystemRoot%\Profiles\%USERNAME% - directory from reading the Default User profile. -

        The mappings of Windows NT RIDs to UNIX ids + is not made algorithmically and depends on the order in which + unmapped users or groups are seen by winbind. It may be difficult + to recover the mappings of rid to UNIX id mapping if the file + containing this information is corrupted or destroyed.

      • If the NETLOGON share on the authenticating server (logon server) contains a policy file - (NTConfig.POL) then it's contents are applied to the NTUser.DAT - which is applied to the HKEY_CURRENT_USER part of the registry. -

        Currently the winbind PAM module does not take + into account possible workstation and logon time restrictions + that may be been set for Windows NT users, this is + instead up to the PDC to enforce.

    15.7. Conclusion

    When the user logs out, if the profile is set to be a roaming profile it will be written - out to the location of the profile. The NTuser.DAT file is then - re-created from the contents of the HKEY_CURRENT_USER contents. - Thus, should there not exist in the NETLOGON share an NTConfig.POL at the - next logon, the effect of the provious NTConfig.POL will still be held - in the profile. The effect of this is known as tatooing. -

    The winbind system, through the use of the Name Service + Switch, Pluggable Authentication Modules, and appropriate + Microsoft RPC calls have allowed us to provide seamless + integration of Microsoft Windows NT domain users on a + UNIX system. The result is a great reduction in the administrative + cost of running a mixed UNIX and NT network.

    Chapter 16. Advanced Network Manangement

    MS Windows NT4 profiles may be Local or This section attempts to document peripheral issues that are of great importance to network +administrators who want to improve network resource access control, to automate the user +environment, and to make their lives a little easier.

    16.1. Configuring Samba Share Access Controls

    This section deals with how to configure Samba per share access control restrictions. +By default samba sets no restrictions on the share itself. Restrictions on the share itself +can be set on MS Windows NT4/200x/XP shares. This can be a very effective way to limit who can +connect to a share. In the absence of specific restrictions the default setting is to allow +the global user RoamingEveryone. A Local profile -will stored in the %SystemRoot%\Profiles\%USERNAME% location. A roaming profile will -also remain stored in the same way, unless the following registry key is created:

    Full Control (ie: Full control, Change and Read).

    	HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
-	"DeleteRoamingCache"=dword:00000001
    - -In which case, the local copy (in %SystemRoot%\Profiles\%USERNAME%) will be -deleted on logout.

    At this time Samba does NOT provide a tool for configuring access control setting on the Share +itself. Samba does have the capacity to store and act on access control settings, but the only +way to create those settings is to use either the NT4 Server Manager or the Windows 200x MMC for +Computer Management.

    Under MS Windows NT4 default locations for common resources (like Samba stores the per share access control settings in a file called My Documents -may be redirected to a network share by modifying the following registry keys. These changes may be affected -via use of the System Policy Editor (to do so may require that you create your owns template extension -for the policy editor to allow this to be done through the GUI. Another way to do this is by way of first -creating a default user profile, then while logged in as that user, run regedt32 to edit the key settings.

    The Registry Hive key that affects the behaviour of folders that are part of the default user profile -are controlled by entries on Windows NT4 is:

            HKEY_CURRENT_USER
-                \Software
-                        \Microsoft
-                                \Windows
-                                        \CurrentVersion
-                                                \Explorer
-                                                        \User Shell Folders\

    The above hive key contains a list of automatically managed folders. The default entries are:

            Name            Default Value
-        --------------  -----------------------------------------
-        AppData         %USERPROFILE%\Application Data
-        Desktop         %USERPROFILE%\Desktop
-        Favorites       %USERPROFILE%\Favorites
-        NetHood         %USERPROFILE%\NetHood
-        PrintHood       %USERPROFILE%\PrintHood
-        Programs        %USERPROFILE%\Start Menu\Programs
-        Recent          %USERPROFILE%\Recent
-        SendTo          %USERPROFILE%\SendTo
-        Start Menu      %USERPROFILE%\Start Menu
-        Startup         %USERPROFILE%\Start Menu\Programs\Startup
-
    -

    The registry key that contains the location of the default profile settings is: - -

    	HKEY_LOCAL_MACHINE
-		\SOFTWARE
-			\Microsoft
-				\Windows
-					\CurrentVersion
-						\Explorer
-							\User Shell Folders
    - -The default entries are: - -
    	Common Desktop		%SystemRoot%\Profiles\All Users\Desktop
-	Common Programs		%SystemRoot%\Profiles\All Users\Programs
-	Common Start Menu	%SystemRoot%\Profiles\All Users\Start Menu
-	Common Startu	p	%SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup

    share_info.tdb. +The location of this file on your system will depend on how samba was compiled. The default location +for samba's tdb files is under /usr/local/samba/var. If the tdbdump +utility has been compiled and installed on your system then you can examine the contents of this file +by: tdbdump share_info.tdb.

    17.4.3. MS Windows 200x/XP16.1.1. Share Permissions Management

    The best tool for the task is platform dependant. Choose the best tool for your environmemt.

    16.1.1.1. Windows NT4 Workstation/Server

    The tool you need to use to manage share permissions on a Samba server is the NT Server Manager. +Server Manager is shipped with Windows NT4 Server products but not with Windows NT4 Workstation. +You can obtain the NT Server Manager for MS Windows NT4 Workstation from Microsoft - see details below.

    Instructions

    1. MS Windows XP Home Edition does use default per user profiles, but can not participate - in domain security, can not log onto an NT/ADS style domain, and thus can obtain the profile - only from itself. While there are benefits in doing this the beauty of those MS Windows - clients that CAN participate in domain logon processes allows the administrator to create - a global default profile and to enforce it through the use of Group Policy Objects (GPOs). -

    Launch the NT4 Server Manager, click on the Samba server you want to administer, then from the menu +select Computer, then click on the Shared Directories entry.

  • Now click on the share that you wish to manage, then click on the Properties tab, next click on + the Permissions tab. Now you can Add or change access control settings as you wish.

    • 16.1.1.2. Windows 200x/XP

    When a new user first logs onto MS Windows 200x/XP machine the default profile is obtained from -C:\Documents and Settings\Default User. The administrator can modify (or change -the contents of this location and MS Windows 200x/XP will gladly user it. This is far from the optimum -arrangement since it will involve copying a new default profile to every MS Windows 200x/XP client -workstation.

    On MS Windows NT4/200x/XP system access control lists on the share itself are set using native +tools, usually from filemanager. For example, in Windows 200x: right click on the shared folder, +then select 'Sharing', then click on 'Permissions'. The default Windows NT4/200x permission allows +Everyone Full Control on the Share.

    When MS Windows 200x/XP participate in a domain security context, and if the default user -profile is not found, then the client will search for a default profile in the NETLOGON share -of the authenticating server. ie: In MS Windows parlance: -%LOGONSERVER%\NETLOGON\Default User and if one exits there it will copy this -to the workstation to the MS Windows 200x and later all comes with a tool called the 'Computer Management' snap-in for the +Microsoft Management Console (MMC). This tool is located by clicking on C:\Documents and Settings\ under the Windows -login name of the user.

    Control Panel -> +Administrative Tools -> Computer Management.

    Instructions

    1. After launching the MMC with the Computer Management snap-in, click on the menu item 'Action', + select 'Connect to another computer'. If you are not logged onto a domain you will be prompted + to enter a domain login user identifier and a password. This will authenticate you to the domain. + If you where already logged in with administrative privilidge this step is not offered.

    2. If the Samba server is not shown in the Select Computer box, then type in the name of the target +Samba server in the field 'Name:'. Now click on the [+] next to 'System Tools', then on the [+] +next to 'Shared Folders' in the left panel.

    3. Now in the right panel, double-click on the share you wish to set access control permissions on. +Then click on the tab 'Share Permissions'. It is now possible to add access control entities +to the shared folder. Do NOT forget to set what type of access (full control, change, read) you +wish to assign for each entry.

    This path translates, in Samba parlance, to the smb.conf [NETLOGON] share. The directory - should be created at the root of this share and msut be called Default Profile. -

    Be careful. If you take away all permissions from the Everyone user without removing this user +then effectively no user will be able to access the share. This is a result of what is known as +ACL precidence. ie: Everyone with NO ACCESS means that MaryK who is part of the group Everyone +will have no access even if this user is given explicit full control access.

    16.2. Remote Server Administration

    If a default profile does not exist in this location then MS Windows 200x/XP will use the local -default profile.

    How do I get 'User Manager' and 'Server Manager'?

    On loging out, the users' desktop profile will be stored to the location specified in the registry -settings that pertain to the user. If no specific policies have been created, or passed to the client -during the login process (as Samba does automatically), then the user's profile will be written to -the local machine only under the path C:\Documents and Settings\%USERNAME%.

    Since I don't need to buy an NT4 Server, how do I get the 'User Manager for Domains', +the 'Server Manager'?

    Those wishing to modify the default behaviour can do so through up to three methods:

    Microsoft distributes a version of these tools called nexus for installation on Windows 9x / Me +systems. The tools set includes:

    • Modify the registry keys on the local machine manually and place the new default profile in the - NETLOGON share root - NOT recommended as it is maintenance intensive. -

      Server Manager

    • Create an NT4 style NTConfig.POL file that specified this behaviour and locate this file - in the root of the NETLOGON share along with the new default profile. -

      User Manager for Domains

    • Create a GPO that enforces this through Active Directory, and place the new default profile - in the NETLOGON share. -

      Event Viewer

    The Registry Hive key that affects the behaviour of folders that are part of the default user profile -are controlled by entries on Windows 200x/XP is:

    Click here to download the archived file ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE

    	HKEY_CURRENT_USER
-		\Software
-			\Microsoft
-				\Windows
-					\CurrentVersion
-						\Explorer
-							\User Shell Folders\
    The Windows NT 4.0 version of the 'User Manager for +Domains' and 'Server Manager' are available from Microsoft via ftp +from ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE

    16.3. Network Logon Script Magic

    The above hive key contains a list of automatically managed folders. The default entries are:

    This section needs work. Volunteer contributions most welcome. Please send your patches or updates +to John Terpstra.

    	Name		Default Value
-	--------------	-----------------------------------------
-	AppData		%USERPROFILE%\Application Data
-	Cache		%USERPROFILE%\Local Settings\Temporary Internet Files
-	Cookies		%USERPROFILE%\Cookies
-	Desktop		%USERPROFILE%\Desktop
-	Favorites	%USERPROFILE%\Favorites
-	History		%USERPROFILE%\Local Settings\History
-	Local AppData	%USERPROFILE%\Local Settings\Application Data
-	Local Settings	%USERPROFILE%\Local Settings
-	My Pictures	%USERPROFILE%\My Documents\My Pictures
-	NetHood		%USERPROFILE%\NetHood
-	Personal	%USERPROFILE%\My Documents
-	PrintHood	%USERPROFILE%\PrintHood
-	Programs	%USERPROFILE%\Start Menu\Programs
-	Recent		%USERPROFILE%\Recent
-	SendTo		%USERPROFILE%\SendTo
-	Start Menu	%USERPROFILE%\Start Menu
-	Startup		%USERPROFILE%\Start Menu\Programs\Startup
-	Templates	%USERPROFILE%\Templates
-
    -

    There are several opportunities for creating a custom network startup configuration environment.

    No Logon Script
    Simple universal Logon Script that applies to all users
    Use of a conditional Logon Script that applies per user or per group attirbutes
    Use of Samba's Preexec and Postexec functions on access to the NETLOGON share to create + a custom Logon Script and then execute it.
    User of a tool such as KixStart

    There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all -the others are of type REG_EXPAND_SZ.

    It makes a huge difference to the speed of handling roaming user profiles if all the folders are -stored on a dedicated location on a network server. This means that it will NOT be necessary to -write Outlook PST file over the network for every login and logout.

    The Samba source code tree includes two logon script generation/execution tools. See examples directory genlogon and ntlogon subdirectories.

    To set this to a network location you could use the following examples: +>The following listings are from the genlogon directory.

    This is the genlogon.pl file: 

    	%LOGONSERVER%\%USERNAME%\Default Folders
    +> #!/usr/bin/perl + # + # genlogon.pl + # + # Perl script to generate user logon scripts on the fly, when users + # connect from a Windows client. This script should be called from smb.conf + # with the %U, %G and %L parameters. I.e: + # + # root preexec = genlogon.pl %U %G %L + # + # The script generated will perform + # the following: + # + # 1. Log the user connection to /var/log/samba/netlogon.log + # 2. Set the PC's time to the Linux server time (which is maintained + # daily to the National Institute of Standard's Atomic clock on the + # internet. + # 3. Connect the user's home drive to H: (H for Home). + # 4. Connect common drives that everyone uses. + # 5. Connect group-specific drives for certain user groups. + # 6. Connect user-specific drives for certain users. + # 7. Connect network printers. -This would store the folders in the user's home directory under a directory called "Default Folders" + # Log client connection + #($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time); + ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time); + open LOG, ">>/var/log/samba/netlogon.log"; + print LOG "$mon/$mday/$year $hour:$min:$sec - User $ARGV[0] logged into $ARGV[1]\n"; + close LOG; -You could also use: + # Start generating logon script + open LOGON, ">/shared/netlogon/$ARGV[0].bat"; + print LOGON "\@ECHO OFF\r\n"; -
    	\\SambaServer\FolderShare\%USERNAME%
    + # Connect shares just use by Software Development group + if ($ARGV[1] eq "SOFTDEV" || $ARGV[0] eq "softdev") + { + print LOGON "NET USE M: \\\\$ARGV[2]\\SOURCE\r\n"; + } -in which case the default folders will be stored in the server named SambaServer -in the share called FolderShare under a directory that has the name of the MS Windows -user as seen by the Linux/Unix file system.

    Please note that once you have created a default profile share, you MUST migrate a user's profile -(default or custom) to it.

    Those wishing to use more elaborate or capable logon processing system should check out the following sites:

    MS Windows 200x/XP profiles may be Local or Roaming. -A roaming profile will be cached locally unless the following registry key is created:

    http://www.craigelachie.org/rhacer/ntlogon
    http://www.kixtart.org

    	HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
-	"DeleteRoamingCache"=dword:00000001
    - -In which case, the local cache copy will be deleted on logout.

    Chapter 18. Interdomain Trust Relationships

    Samba-3 supports NT4 style domain trust relationships. This is feature that many sites -will want to use if they migrate to Samba-3 from and NT4 style domain and do NOT want to -adopt Active Directory or an LDAP based authentication back end. This section explains -some background information regarding trust relationships and how to create them. It is now -possible for Samba3 to NT4 trust (and vica versa), as well as Samba3 to Samba3 trusts.

    Chapter 17. System and Account Policies

    18.1. Trust Relationship Background17.1. Creating and Managing System Policies

    MS Windows NT3.x/4.0 type security domains employ a non-hierchical security structure. -The limitations of this architecture as it affects the scalability of MS Windows networking -in large organisations is well known. Additionally, the flat-name space that results from -this design significantly impacts the delegation of administrative responsibilities in -large and diverse organisations.

    Under MS Windows platforms, particularly those following the release of MS Windows +NT4 and MS Windows 95) it is possible to create a type of file that would be placed +in the NETLOGON share of a domain controller. As the client logs onto the network +this file is read and the contents initiate changes to the registry of the client +machine. This file allows changes to be made to those parts of the registry that +affect users, groups of users, or machines.

    Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means -of circumventing the limitations of the older technologies. Not every organisation is ready -or willing to embrace ADS. For small companies the older NT4 style domain security paradigm -is quite adequate, there thus remains an entrenched user base for whom there is no direct -desire to go through a disruptive change to adopt ADS.

    For MS Windows 9x/Me this file must be called Config.POL and may +be generated using a tool called poledit.exe, better known as the +Policy Editor. The policy editor was provided on the Windows 98 installation CD, but +dissappeared again with the introduction of MS Windows Me (Millenium Edition). From +comments from MS Windows network administrators it would appear that this tool became +a part of the MS Windows Me Resource Kit.

    Microsoft introduced with MS Windows NT the ability to allow differing security domains -to affect a mechanism so that users from one domain may be given access rights and privilidges -in another domain. The language that describes this capability is couched in terms of -Trusts. Specifically, one domain will MS Windows NT4 Server products include the trustSystem Policy Editor the users -from another domain. The domain from which users are available to another security domain is -said to be a trusted domain. The domain in which those users have assigned rights and privilidges -is the trusting domain. With NT3.x/4.0 all trust relationships are always in one direction only, -thus if users in both domains are to have privilidges and rights in each others' domain, then it is -necessary to establish two (2) relationships, one in each direction.

    +under the Start -> Programs -> Administrative Tools menu item. +For MS Windows NT4 and later clients this file must be called NTConfig.POL.

    In an NT4 style MS security domain, all trusts are non-transitive. This means that if there -are three (3) domains (let's call them RED, WHITE, and BLUE) where RED and WHITE have a trust -relationship, and WHITE and BLUE have a trust relationship, then it holds that there is no -implied trust between the RED and BLUE domains. ie: Relationships are explicit and not -transitive.

    New with the introduction of MS Windows 2000 was the Microsoft Management Console +or MMC. This tool is the new wave in the ever changing landscape of Microsoft +methods for management of network access and security. Every new Microsoft product +or technology seems to obsolete the old rules and to introduce newer and more +complex tools and methods. To Microsoft's credit though, the MMC does appear to +be a step forward, but improved functionality comes at a great price.

    New to MS Windows 2000 ADS security contexts is the fact that trust relationships are two-way -by default. Also, all inter-ADS domain trusts are transitive. In the case of the RED, WHITE and BLUE -domains above, with Windows 2000 and ADS the RED and BLUE domains CAN trust each other. This is -an inherent feature of ADS domains.

    18.2. MS Windows NT4 Trust Configuration

    Before embarking on the configuration of network and system policies it is highly +advisable to read the documentation available from Microsoft's web site regarding +Implementing Profiles and Policies in Windows NT 4.0 from http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp available from Microsoft. +There are a large number of documents in addition to this old one that should also +be read and understood. Try searching on the Microsoft web site for "Group Policies".

    There are two steps to creating an inter-domain trust relationship.

    What follows is a very brief discussion with some helpful notes. The information provided +here is incomplete - you are warned.

    18.2.1. NT4 as the Trusting Domain17.1.1. Windows 9x/Me Policies

    For MS Windows NT4, all domain trust relationships are configured using the Domain User Manager. -To affect a two way trust relationship it is necessary for each domain administrator to make -available (for use by an external domain) it's security resources. This is done from the Domain -User Manager Policies entry on the menu bar. From the Policy menu, select Trust Relationships, then -next to the lower box that is labelled "Permitted to Trust this Domain" are two buttons, "Add" and -"Remove". The "Add" button will open a panel in which needs to be entered the remote domain that -will be able to assign user rights to your domain. In addition it is necessary to enter a password -that is specific to this trust relationship. The password is added twice.

    18.2.2. NT4 as the Trusted Domain

    You need the Win98 Group Policy Editor to set Group Profiles up under Windows 9x/Me. +It can be found on the Original full product Win98 installation CD under +tools/reskit/netadmin/poledit. Install this using the +Add/Remove Programs facility and then click on the 'Have Disk' tab.

    A trust relationship will work only when the other (trusting) domain makes the appropriate connections -with the trusted domain. To consumate the trust relationship the administrator will launch the -Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the -"Add" button that is next to the box that is labelled "Trusted Domains". A panel will open in -which must be entered the name of the remote domain as well as the password assigned to that trust.

    Use the Group Policy Editor to create a policy file that specifies the location of +user profiles and/or the My Documents etc. stuff. Then +save these settings in a file called Config.POL that needs to +be placed in the root of the [NETLOGON] share. If Win98 is configured to log onto +the Samba Domain, it will automatically read this file and update the Win9x/Me registry +of the machine as it logs on.

    18.3. Configuring Samba Domain Trusts

    Further details are covered in the Win98 Resource Kit documentation.

    This descitpion is meant to be a fairly short introduction about how to set up a Samba server so -that it could participate in interdomain trust relationships. Trust relationship support in Samba -is in its early stage, so lot of things don't work yet. Paricularly, the contents of this document -applies to NT4-style trusts.

    If you do not take the right steps, then every so often Win9x/Me will check the +integrity of the registry and will restore it's settings from the back-up +copy of the registry it stores on each Win9x/Me machine. Hence, you will +occasionally notice things changing back to the original settings.

    Each of the procedures described below is treated as they were performed with Windows NT4 Server on -one end. The other end could just as well be another Samba3 domain. It can be clearly seen, after -reading this document, that combining Samba-specific parts of what's written below leads to trust -between domains in purely Samba environment.

    Install the group policy handler for Win9x to pick up group policies. Look on the +Win98 CD in \tools\reskit\netadmin\poledit. +Install group policies on a Win9x client by double-clicking +grouppol.inf. 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/Me machine that uses group policies.

    18.3.1. Samba3 as the Trusting Domain17.1.2. Windows NT4 Style Policy Files

    In order to set Samba PDC to be trusted party of the relationship first you need -to create special account for domain that will be the trusting party. To do that, -you can use 'smbpasswd' utility. Creating the trusted domain account is very -similiar to creating the connection to the trusting machine's account. Suppose, -your domain is called SAMBA, and the remote domain is called RUMBA. Your first -step will be to issue this command from your favourite shell:

    To create or edit ntconfig.pol you must use the NT Server +Policy Editor, poledit.exe which is included with NT4 Server +but not NT Workstation. There is a Policy Editor on a NT4 +Workstation but it is not suitable for creating Domain Policies. +Further, although the Windows 95 Policy Editor can be installed on an NT4 +Workstation/Server, it will not work with NT clients. However, the files from +the NT Server will run happily enough on an NT4 Workstation.

    	deity# smbpasswd -a -i rumba
-	New SMB password: XXXXXXXX
-	Retype SMB password: XXXXXXXX
-	Added user rumba$
-
-	where:
-		-a means to add a new account into the passdb database
-		-i means create this account with the Inter-Domain trust flag
-
-	The account name will be 'rumba$' (the name ofthe remote domain)

    You need poledit.exe, common.adm and winnt.adm. +It is convenient to put the two *.adm files in the c:\winnt\inf +directory which is where the binary will look for them unless told otherwise. Note also that that +directory is normally 'hidden'.

    fter issuing this command you'll be asked for typing account's -password. You can use any password you want, but be aware that Windows NT will -not change this password until 7 days have passed since account creating. -After command returns successfully, you can look at your new account's entry -(in the way depending on your configuration) and see that account's name is -really RUMBA$ and it has 'I' flag in the flags field. Now you're ready to confirm -the trust by establishing it from Windows NT Server.

    The Windows NT policy editor is also included with the Service Pack 3 (and +later) for Windows NT 4.0. Extract the files using servicepackname /x, +i.e. that's Nt4sp6ai.exe /x for service pack 6a. The policy editor, +poledit.exe 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.

    17.1.2.1. Registry Tattoos

    Open 'User Manager for Domains' and from menu 'Policies' select 'Trust Relationships...'. -Right beside 'Trusted domains' list press 'Add...' button. You'll be prompted for -trusted domain name and the relationship's password. Type in SAMBA, as this is -your domain name and the password you've just used during account creation. -Press OK and if everything went fine, you will see 'Trusted domain relationship -successfully established' message. Well done.

    With NT4 style registry based policy changes, a large number of settings are not + automatically reversed as the user logs off. Since the settings that were in the + NTConfig.POL file were applied to the client machine registry and that apply to the + hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known + as tattooing. It can have serious consequences down-stream and the administrator must + be extremely careful not to lock out the ability to manage the machine at a later date. +

    18.3.2. Samba3 as the Trusted Domain17.1.3. MS Windows 200x / XP Professional Policies

    This time activities are somewhat reversed. Again, we'll assume that your domain -controlled by Samba PDC is called SAMBA and NT-controlled domain is called RUMBA.

    Windows NT4 System policies allows setting of registry parameters specific to +users, groups and computers (client workstations) that are members of the NT4 +style domain. Such policy file will work with MS Windows 2000 / XP clients also.

    The very first thing is to add account for SAMBA domain on RUMBA's PDC.

    New to MS Windows 2000 Microsoft introduced a new style of group policy that confers +a superset of capabilities compared with NT4 style policies. Obviously, the tool used +to create them is different, and the mechanism for implementing them is much changed.

    Launch the Domain User Manager, then from the menu select 'Policies', 'Trust Relationships'. -Now, next to 'Trusted Domains' box press the 'Add' button, and type in the name of the trusted -domein (SAMBA) and password securing the relationship.

    The older NT4 style registry based policies are known as Administrative Templates +in MS Windows 2000/XP Group Policy Objects (GPOs). The later includes ability to set various security +configurations, enforce Internet Explorer browser settings, change and redirect aspects of the +users' desktop (including: the location of My Documents files (directory), as +well as intrinsics of where menu items will appear in the Start menu). An additional new +feature is the ability to make available particular software Windows applications to particular +users and/or groups.

    Password can be arbitrarily chosen the more, because it's easy to change it -from Samba server whenever you want. After confirming password your account is -ready and waiting. Now it's Samba's turn.

    Remember: NT4 policy files are named NTConfig.POL and are stored in the root +of the NETLOGON share on the domain controllers. A Windows NT4 user enters a username, a password +and selects the domain name to which the logon will attempt to take place. During the logon +process the client machine reads the NTConfig.POL file from the NETLOGON share on the authenticating +server, modifies the local registry values according to the settings in this file.

    Using your favourite shell while being logged on as root, issue this command:

    Windows 2K GPOs are very feature rich. They are NOT stored in the NETLOGON share, rather part of +a Windows 200x policy file is stored in the Active Directory itself and the other part is stored +in a shared (and replicated) volume called the SYSVOL folder. This folder is present on all Active +Directory domain controllers. The part that is stored in the Active Directory itself is called the +group policy container (GPC), and the part that is stored in the replicated share called SYSVOL is +known as the group policy template (GPT).

    	deity#  net rpc trustdom establish rumba
    With NT4 clients the policy file is read and executed upon only aas each user log onto the network. +MS Windows 200x policies are much more complex - GPOs are processed and applied at client machine +startup (machine specific part) and when the user logs onto the network the user specific part +is applied. In MS Windows 200x style policy management each machine and/or user may be subject +to any number of concurently applicable (and applied) policy sets (GPOs). Active Directory allows +the administrator to also set filters over the policy settings. No such equivalent capability +exists with NT4 style policy files.

    17.1.3.1. Administration of Win2K / XP Policies

    Instructions

    You'll be prompted for password you've just typed on your Windows NT4 Server box. -Don't worry if you will see the error message with returned code of -Instead of using the tool called "The System Policy Editor", commonly called Poledit (from the +executable name poledit.exe), GPOs are created and managed using a Microsoft Management Console +(MMC) snap-in as follows:

    1. Go to the Windows 200x / XP menu NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT. It means the -password you gave is correct and the NT4 Server says the account is ready for trusting your domain -and not for ordinary connection. After that, be patient it can take a while (especially -in large networks), you should see 'Success' message. Contgratulations! Your trust -relationship has just been established.

      Start->Programs->Administrative Tools + and select the MMC snap-in called "Active Directory Users and Computers"

    2. Select the domain or organizational unit (OU) that you wish to manage, then right click +to open the context menu for that object, select the properties item.

    3. Now left click on the Group Policy tab, then left click on the New tab. Type a name +for the new policy you will create.

    4. Now left click on the Edit tab to commence the steps needed to create the GPO.

    All policy configuration options are controlled through the use of policy administrative +templates. These files have a .adm extension, both in NT4 as well as in Windows 200x / XP. +Beware however, since the .adm files are NOT interchangible across NT4 and Windows 200x. +The later introduces many new features as well as extended definition capabilities. It is +well beyond the scope of this documentation to explain how to program .adm files, for that +the adminsitrator is referred to the Microsoft Windows Resource Kit for your particular +version of MS Windows.

    Note that you have to run this command as root, since you need write access to -your secrets.tdb file.

    The MS Windows 2000 Resource Kit contains a tool called gpolmig.exe. This tool can be used +to migrate an NT4 NTConfig.POL file into a Windows 200x style GPO. Be VERY careful how you +use this powerful tool. Please refer to the resource kit manuals for specific usage information.

    17.2. Managing Account/User Policies

    Policies can define a specific user's settings or the settings for a group of users. The resulting +policy file contains the registry settings for all users, groups, and computers that will be using +the policy file. Separate policy files for each user, group, or computer are not not necessary.

    If you create a policy that will be automatically downloaded from validating domain controllers, +you should name the file NTconfig.POL. As system administrator, you have the option of renaming the +policy file and, by modifying the Windows NT-based workstation, directing the computer to update +the policy from a manual path. You can do this by either manually changing the registry or by using +the System Policy Editor. This path can even be a local path such that each machine has its own policy file, +but if a change is necessary to all machines, this change must be made individually to each workstation.

    When a Windows NT4/200x/XP machine logs onto the network the NETLOGON share on the authenticating domain +controller for the presence of the NTConfig.POL file. If one exists it is downloaded, parsed and then +applied to the user's part of the registry.

    MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally, +acquire policy settings through Group Policy Objects (GPOs) that are defined and stored in Active Directory +itself. The key benefit of using AS GPOs is that they impose no registry tatooing effect. +This has considerable advanage compared with the use of NTConfig.POL (NT4) style policy updates.

    Inaddition to user access controls that may be imposed or applied via system and/or group policies +in a manner that works in conjunction with user profiles, the user management environment under +MS Windows NT4/200x/XP allows per domain as well as per user account restrictions to be applied. +Common restrictions that are frequently used includes:

    Logon Hours
    Password Aging
    Permitted Logon from certain machines only
    Account type (Local or Global)
    User Rights

    17.2.1. With Windows NT4/200x

    The tools that may be used to configure these types of controls from the MS Windows environment are: +The NT4 User Manager for domains, the NT4 System and Group Policy Editor, the registry editor (regedt32.exe). +Under MS Windows 200x/XP this is done using the Microsoft Managment Console (MMC) with approapriate +"snap-ins", the registry editor, and potentially also the NT4 System and Group Policy Editor.

    Chapter 19. PAM Configuration for Centrally Managed Authentication

    17.2.2. With a Samba PDC

    With a Samba Domain Controller, the new tools for managing of user account and policy information includes: +smbpasswd, pdbedit, smbgroupedit, net, rpcclient.. The administrator should read the +man pages for these tools and become familiar with their use.

    19.1. Samba and PAM17.3. System Startup and Logon Processing Overview

    A number of Unix systems (eg: Sun Solaris), as well as the -xxxxBSD family and Linux, now utilize the Pluggable Authentication -Modules (PAM) facility to provide all authentication, -authorization and resource control services. Prior to the -introduction of PAM, a decision to use an alternative to -the system password database (/etc/passwd) -would require the provision of alternatives for all programs that provide -security services. Such a choice would involve provision of -alternatives to such programs as: login, -passwd, chown, etc.

    The following attempts to document the order of processing of system and user policies following a system +reboot and as part of the user logon:

    PAM provides a mechanism that disconnects these security programs -from the underlying authentication/authorization infrastructure. -PAM is configured either through one file /etc/pam.conf (Solaris), -or by editing individual files that are located in /etc/pam.d.

    1. Network starts, then Remote Procedure Call System Service (RPCSS) and Multiple Universal Naming + Convention Provider (MUP) start +

    2. Where Active Directory is involved, an ordered list of Group Policy Objects (GPOs) is downloaded + and applied. The list may include GPOs that: +

      Apply to the location of machines in a Directory
      Apply only when settings have changed
      Depend on configuration of scope of applicability: local, site, domain, organizational unit, etc.

      If the PAM authentication module (loadable link library file) is located in the - default location then it is not necessary to specify the path. In the case of - Linux, the default location is /lib/security. If the module - is located other than default then the path may be specified as: - - 

      	auth       required      /other_path/pam_strange_module.so
-

      + No desktop user interface is presented until the above have been processed.

  • The following is an example /etc/pam.d/login configuration file. -This example had all options been uncommented is probably not usable -as it stacks many conditions before allowing successful completion -of the login process. Essentially all conditions can be disabled -by commenting them out except the calls to pam_pwdb.so.

    Execution of start-up scripts (hidden and synchronous by defaut). + 

  • 	#%PAM-1.0
-	# The PAM configuration file for the `login' service
-	#
-	auth 		required	pam_securetty.so
-	auth 		required	pam_nologin.so
-	# auth 		required	pam_dialup.so
-	# auth 		optional	pam_mail.so
-	auth		required	pam_pwdb.so shadow md5
-	# account    	requisite  	pam_time.so
-	account		required	pam_pwdb.so
-	session		required	pam_pwdb.so
-	# session 	optional	pam_lastlog.so
-	# password   	required   	pam_cracklib.so retry=3
-	password	required	pam_pwdb.so shadow md5

    A keyboard action to affect start of logon (Ctrl-Alt-Del). +

  • PAM allows use of replacable modules. Those available on a -sample system include:

    User credentials are validated, User profile is loaded (depends on policy settings). +

  • $/bin/ls /lib/security -

    	pam_access.so    pam_ftp.so          pam_limits.so     
-	pam_ncp_auth.so  pam_rhosts_auth.so  pam_stress.so     
-	pam_cracklib.so  pam_group.so        pam_listfile.so   
-	pam_nologin.so   pam_rootok.so       pam_tally.so      
-	pam_deny.so      pam_issue.so        pam_mail.so       
-	pam_permit.so    pam_securetty.so    pam_time.so       
-	pam_dialup.so    pam_lastlog.so      pam_mkhomedir.so  
-	pam_pwdb.so      pam_shells.so       pam_unix.so       
-	pam_env.so       pam_ldap.so         pam_motd.so       
-	pam_radius.so    pam_smbpass.so      pam_unix_acct.so  
-	pam_wheel.so     pam_unix_auth.so    pam_unix_passwd.so
-	pam_userdb.so    pam_warn.so         pam_unix_session.so
    An ordered list of User GPOs is obtained. The list contents depends on what is configured in respsect of: + +

    Is user a domain member, thus subject to particular policies
    Loopback enablement, and the state of the loopback policy (Merge or Replace)
    Location of the Active Directory itself
    Has the list of GPOs changed. No processing is needed if not changed.

    The following example for the login program replaces the use of -the pam_pwdb.so module which uses the system -password database (/etc/passwd, -/etc/shadow, /etc/group) with -the module pam_smbpass.so which uses the Samba -database which contains the Microsoft MD4 encrypted password -hashes. This database is stored in either -/usr/local/samba/private/smbpasswd, -/etc/samba/smbpasswd, or in -/etc/samba.d/smbpasswd, depending on the -Samba implementation for your Unix/Linux system. The -pam_smbpass.so module is provided by -Samba version 2.2.1 or later. It can be compiled by specifying the ---with-pam_smbpass options when running Samba's -configure script. For more information -on the pam_smbpass module, see the documentation -in the source/pam_smbpass directory of the Samba -source distribution.

    	#%PAM-1.0
-	# The PAM configuration file for the `login' service
-	#
-	auth		required	pam_smbpass.so nodelay
-	account		required	pam_smbpass.so nodelay
-	session		required	pam_smbpass.so nodelay
-	password	required	pam_smbpass.so nodelay

    +

  • The following is the PAM configuration file for a particular -Linux system. The default condition uses pam_pwdb.so.

    User Policies are applied from Active Directory. Note: There are several types. +

  • Logon scripts are run. New to Win2K and Active Directory, logon scripts may be obtained based on Group + Policy objects (hidden and executed synchronously). NT4 style logon scripts are then run in a normal + window. +

  • The User Interface as determined from the GPOs is presented. Note: In a Samba domain (like and NT4 + Domain) machine (system) policies are applied at start-up, User policies are applied at logon. +

    • Chapter 18. Desktop Profile Management

    18.1. Roaming Profiles

    	#%PAM-1.0
-	# The PAM configuration file for the `samba' service
-	#
-	auth       required     pam_pwdb.so nullok nodelay shadow audit
-	account    required     pam_pwdb.so audit nodelay
-	session    required     pam_pwdb.so nodelay
-	password   required     pam_pwdb.so shadow md5

    In the following example the decision has been made to use the -smbpasswd database even for basic samba authentication. Such a -decision could also be made for the passwd program and would -thus allow the smbpasswd passwords to be changed using the passwd -program.

    Roaming profiles support is different for Win9x / Me and Windows NT4/200x.

    Before discussing how to configure roaming profiles, it is useful to see how +Windows 9x / Me and Windows NT4/200x clients implement these features.

    Windows 9x / Me 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 user's home share. This means that Win9X/Me +profiles are restricted to being stored in the user's home directory.

    Windows NT4/200x clients send a NetSAMLogon RPC request, which contains many fields, +including a separate field for the location of the user's profiles.

    18.1.1. Samba Configuration for Profile Handling

    This section documents how to configure Samba for MS Windows client profile support.

    18.1.1.1. NT4/200x User Profiles

    To support Windowns NT4/200x clients, in the [global] section of smb.conf set the +following (for example):

    	#%PAM-1.0
-	# The PAM configuration file for the `samba' service
-	#
-	auth       required     pam_smbpass.so nodelay
-	account    required     pam_pwdb.so audit nodelay
-	session    required     pam_pwdb.so nodelay
-	password   required     pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf

    logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath + + This is typically implemented like: + +
    		logon path = \\%L\Profiles\%u
    +where %L translates to the name of the Samba server and %u translates to the user name

    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. Please refer to the man page for smb.conf in respect of the different +symantics of %L and %N, as well as %U and %u.

    PAM allows stacking of authentication mechanisms. It is -also possible to pass information obtained within one PAM module through -to the next module in the PAM stack. Please refer to the documentation for -your particular system implementation for details regarding the specific -capabilities of PAM in this environment. Some Linux implmentations also -provide the pam_stack.so module that allows all -authentication to be configured in a single central file. The -pam_stack.so method has some very devoted followers -on the basis that it allows for easier administration. As with all issues in -life though, every decision makes trade-offs, so you may want examine the -PAM documentation for further helpful information.

    MS Windows NT/2K clients at times do not disconnect a connection to a server +between logons. It is recommended to NOT use the homes +meta-service name as part of the profile share path.

    19.2. Distributed Authentication

    18.1.1.2. Windows 9x / Me User Profiles

    The astute administrator will realize from this that the -combination of To support Windows 9x / Me 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.

    By using the logon home parameter, you are restricted to putting Win9x / Me +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 pam_smbpass.so, -smb.conf file:

    	logon home = \\%L\%U\.profiles

    then your Windows 9x / Me clients will dutifully put their clients in a subdirectory +of your home directory called .profiles (thus making them hidden).

    Not only that, but net use/home will also work, because of a feature in +Windows 9x / Me. 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 winbindd, and a distributed -passdb backend, such as ldap, will allow the establishment of a -centrally managed, distributed -user/password database that can also be used by all -PAM (eg: Linux) aware programs and applications. This arrangement -can have particularly potent advantages compared with the -use of Microsoft Active Directory Service (ADS) in so far as -reduction of wide area network authentication traffic.

    logon home.

    19.3. PAM Configuration in smb.conf

    There is an option in smb.conf called obey pam restrictions. -The following is from the on-line help for this option in SWAT;

    18.1.1.3. Mixed Windows 9x / Me and Windows NT4/200x User Profiles

    When Samba is configured 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 -encrypt passwords = yes. -The reason is that PAM modules cannot support the challenge/response -authentication mechanism needed in the presence of SMB -password encryption.

    You can support profiles for both Win9X and WinNT clients by setting both the +logon home and logon path parameters. For example:

    Default: obey pam restrictions = no

    	logon home = \\%L\%u\.profiles
+	logon path = \\%L\profiles\%u

    Chapter 20. Stackable VFS modules

    18.1.2. Windows Client Profile Configuration Information

    20.1. Introduction and configuration

    18.1.2.1. Windows 9x / Me Profile Setup

    Since samba 3.0, samba supports stackable VFS(Virtual File System) modules. -Samba passes each request to access the unix file system thru the loaded VFS modules. -This chapter covers all the modules that come with the samba source and references to -some external modules.

    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 preserve case = yes" and +"case sensitive = no" in order to maintain capital letters in shortcuts +in any of the profile folders.

    You may have problems to compile these modules, as shared libraries are -compiled and linked in different ways on different systems. -They currently have been tested against GNU/linux and IRIX.

    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.

    To use the VFS modules, create a share similar to the one below. The -important parameter is the vfs object parameter which must point to -the exact pathname of the shared library objects. For example, to log all access -to files and use a recycle bin: - -

           [audit]
-                comment = Audited /data directory
-                path = /data
-                vfs object = /path/to/audit.so /path/to/recycle.so
-                writeable = yes
-                browseable = yes

    1. The modules are used in the order they are specified.

      On the Windows 9x / Me 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. +

    2. Further documentation on writing VFS modules for Samba can be found in -the Samba Developers Guide.

      On the Windows 9x / Me 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 9x / Me 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, it would seem!

    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 9x / Me 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 9x / Me 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 Windows 9x / Me 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 Windows 9x / Me 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-caching file in the c:\windows + directory, and delete it. +

    5. log off the windows 9x / Me 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 ethereal or netmon.exe, and +look for error messages.

    If you have access to an Windows NT4/200x server, then first set up roaming profiles +and / or netlogons on the Windows NT4/200x server. Make a packet trace, or examine +the example packet traces provided with Windows NT4/200x server, and see what the +differences are with the equivalent samba trace.

    20.2. Included modules

    20.2.1. audit

    18.1.2.2. Windows NT4 Workstation

    A simple module to audit file access to the syslog -facility. The following operations are logged: -

    share
    connect/disconnect
    directory opens/create/remove
    file open/close/rename/unlink/chmod
    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.

    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 NT4 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 +for those situations where it might be created.)

    In the profile directory, Windows NT4 creates more folders than Windows 9x / Me. +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.

    20.2.2. extd_audit

    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.

    This module is identical with the audit module above except -that it sends audit logs to both syslog as well as the smbd log file/s. The -loglevel for this module is set in the smb.conf file. At loglevel = 0, only file -and directory deletions and directory and file creations are logged. At loglevel = 1 -file opens are renames and permission changes are logged , while at loglevel = 2 file -open and close calls are logged also.

    The case of the profile is significant. The file must be called +NTuser.DAT or, for a mandatory profile, NTuser.MAN.

    20.2.3. recycle

    18.1.2.3. Windows 2000/XP Professional

    A recycle-bin like modules. When used any unlink call -will be intercepted and files moved to the recycle -directory instead of beeing deleted.

    You must first convert the profile from a local profile to a domain +profile on the MS Windows workstation as follows:

    Supported options: -

    vfs_recycle_bin:repository

    • FIXME

    vfs_recycle_bin:keeptree
    Log on as the LOCAL workstation administrator. +

  • FIXME

    • vfs_recycle_bin:versions
    Right click on the 'My Computer' Icon, select 'Properties' +

  • FIXME

    • vfs_recycle_bin:touch
    Click on the 'User Profiles' tab +

  • FIXME

    • vfs_recycle_bin:maxsize
    Select the profile you wish to convert (click on it once) +

  • FIXME

    • vfs_recycle_bin:exclude
    Click on the button 'Copy To' +

  • FIXME

    • vfs_recycle_bin:exclude_dir
    In the "Permitted to use" box, click on the 'Change' button. +

  • FIXME

    • vfs_recycle_bin:noversions
    Click on the 'Look in" area that lists the machine name, when you click + here it will open up a selection box. Click on the domain to which the + profile must be accessible. +

    FIXME

    You will need to log on if a logon box opens up. Eg: In the connect + as: MIDEARTH\root, password: mypassword.

    20.2.4. netatalk

  • A netatalk module, that will ease co-existence of samba and -netatalk file sharing services.

    To make the profile capable of being used by anyone select 'Everyone' +

  • Click OK. The Selection box will close. +

  • Now click on the 'Ok' button to create the profile in the path you + nominated. +

    • Done. You now have a profile that can be editted using the samba-3.0.0 +profiles tool.

    Advantages compared to the old netatalk module: -

    Under NT/2K the use of mandotory profiles forces the use of MS Exchange +storage of mail data. That keeps desktop profiles usable.

    it doesn't care about creating of .AppleDouble forks, just keeps ones in sync
    if share in smb.conf doesn't contain .AppleDouble item in hide or veto list, it will be added automatically

    20.3. VFS modules available elsewhere

    • This section contains a listing of various other VFS modules that -have been posted but don't currently reside in the Samba CVS -tree for one reason ot another (e.g. it is easy for the maintainer -to have his or her own CVS tree).

      This is a security check new to Windows XP (or maybe only +Windows XP service pack 1). It can be disabled via a group policy in +Active Directory. The policy is:

      No statemets about the stability or functionality any module -should be implied due to its presence here.

      20.3.1. DatabaseFS

      "Computer Configuration\Administrative Templates\System\User +Profiles\Do not check for user ownership of Roaming Profile Folders"

      ...and it should be set to "Enabled". +Does the new version of samba have an Active Directory analogue? If so, +then you may be able to set the policy through this.

      If you cannot set group policies in samba, then you may be able to set +the policy locally on each machine. If you want to try this, then do +the following (N.B. I don't know for sure that this will work in the +same way as a domain group policy):

    • URL: http://www.css.tayloru.edu/~elorimer/databasefs/index.php

      On the XP workstation log in with an Administrator account.

    • By Eric Lorimer.

      Click: "Start", "Run"

    • I have created a VFS module which implements a fairly complete read-only -filesystem. It presents information from a database as a filesystem in -a modular and generic way to allow different databases to be used -(originally designed for organizing MP3s under directories such as -"Artists," "Song Keywords," etc... I have since applied it to a student -roster database very easily). The directory structure is stored in the -database itself and the module makes no assumptions about the database -structure beyond the table it requires to run.

      Type: "mmc"

    • Any feedback would be appreciated: comments, suggestions, patches, -etc... If nothing else, hopefully it might prove useful for someone -else who wishes to create a virtual filesystem.

    20.3.2. vscan

    Click: "OK"

  • URL: http://www.openantivirus.org/

    A Microsoft Management Console should appear.

  • samba-vscan is a proof-of-concept module for Samba, which -uses the VFS (virtual file system) features of Samba 2.2.x/3.0 -alphaX. Of couse, Samba has to be compiled with VFS support. -samba-vscan supports various virus scanners and is maintained -by Rainer Link.

    • Chapter 21. Hosting a Microsoft Distributed File System tree on Samba

    21.1. Instructions

    Click: File, "Add/Remove Snap-in...", "Add"

  • The Distributed File System (or Dfs) provides a means of - separating the logical view of files and directories that users - see from the actual physical locations of these resources on the - network. It allows for higher availability, smoother storage expansion, - load balancing etc. For more information about Dfs, refer to Microsoft documentation.

    Double-Click: "Group Policy"

  • This document explains how to host a Dfs tree on a Unix - machine (for Dfs-aware clients to browse) using Samba.

    Click: "Finish", "Close"

  • To enable SMB-based DFS for Samba, configure it with the - --with-msdfs option. Once built, a - Samba server can be made a Dfs server by setting the global - boolean host msdfs parameter in the smb.conf - file. You designate a share as a Dfs root using the share - level boolean msdfs root parameter. A Dfs root directory on - Samba hosts Dfs links in the form of symbolic links that point - to other servers. For example, a symbolic link - junction->msdfs:storage1\share1 in - the share directory acts as the Dfs junction. When Dfs-aware - clients attempt to access the junction link, they are redirected - to the storage location (in this case, \\storage1\share1).

    Click: "OK"

  • Dfs trees on Samba work with all Dfs-aware clients ranging - from Windows 95 to 2000.

    In the "Console Root" window:

  • Here's an example of setting up a Dfs tree on a Samba - server.

    Expand: "Local Computer Policy", "Computer Configuration",

  • # The smb.conf file:
-[global]
-	netbios name = SAMBA
-	host msdfs   = yes
-
-[dfs]
-	path = /export/dfsroot
-	msdfs root = yes
-

    "Administrative Templates", "System", "User Profiles"

  • In the /export/dfsroot directory we set up our dfs links to - other servers on the network.

    Double-Click: "Do not check for user ownership of Roaming Profile

  • root# cd /export/dfsroot

    Folders"

  • root# chown root /export/dfsroot

    Select: "Enabled"

  • root# chmod 755 /export/dfsroot

    Click: OK"

  • root# ln -s msdfs:storageA\\shareA linka

    Close the whole console. You do not need to save the settings (this + refers to the console settings rather than the policies you have + changed).

  • root# ln -s msdfs:serverB\\share,serverC\\share linkb

    Reboot

    • 18.1.3. Sharing Profiles between W9x/Me and NT4/200x/XP workstations

    You should set up the permissions and ownership of - the directory acting as the Dfs root such that only designated - users can create, delete or modify the msdfs links. Also note - that symlink names should be all lowercase. This limitation exists - to have Samba avoid trying all the case combinations to get at - the link name. Finally set up the symbolic links to point to the - network shares you want, and start Samba.

    Sharing of desktop profiles between Windows versions is NOT recommended. +Desktop profiles are an evolving phenomenon and profiles for later versions +of MS Windows clients add features that may interfere with earlier versions +of MS Windows clients. Probably the more salient reason to NOT mix profiles +is that when logging off an earlier version of MS Windows the older format +of profile contents may overwrite information that belongs to the newer +version resulting in loss of profile information content when that user logs +on again with the newer version of MS Windows.

    Users on Dfs-aware clients can now browse the Dfs tree - on the Samba server at \\samba\dfs. Accessing - links linka or linkb (which appear as directories to the client) - takes users directly to the appropriate shares on the network.

    If you then want to share the same Start Menu / Desktop with W9x/Me, you will +need to specify a common location for the profiles. The smb.conf parameters +that need to be common are logon path and +logon home.

    If you have this set up correctly, you will find separate user.DAT and +NTuser.DAT files in the same profile directory.

    21.1.1. Notes18.1.4. Profile Migration from Windows NT4/200x Server to Samba

    • Windows clients need to be rebooted - if a previously mounted non-dfs share is made a dfs - root or vice versa. A better way is to introduce a - new share and make it the dfs root.

    • Currently there's a restriction that msdfs - symlink names should all be lowercase.

    • For security purposes, the directory - acting as the root of the Dfs tree should have ownership - and permissions set so that only designated users can - modify the symbolic links in the directory.

    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.

    Chapter 22. Integrating MS Windows networks with Samba

    18.1.4.1. Windows NT4 Profile Management Tools

    This section deals with NetBIOS over TCP/IP name to IP address resolution. If you -your MS Windows clients are NOT configured to use NetBIOS over TCP/IP then this -section does not apply to your installation. If your installation involves use of -NetBIOS over TCP/IP then this section may help you to resolve networking problems.

    Unfortunately, the Resource Kit information is specific to the version of MS Windows +NT4/200x. The correct resource kit is required for each platform.

    Here is a quick guide:

    • NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS - over Logical Link Control (LLC). On modern networks it is highly advised - to NOT run NetBEUI at all. Note also that there is NO such thing as - NetBEUI over TCP/IP - the existence of such a protocol is a complete - and utter mis-apprehension.

    On your NT4 Domain Controller, right click on 'My Computer', then +select the tab labelled 'User Profiles'.

  • Since the introduction of MS Windows 2000 it is possible to run MS Windows networking -without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS -name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over -TCP/IP is disabled on MS Windows 2000 and later clients then only TCP port 445 will be -used and UDP port 137 and TCP port 139 will not.

    Select a user profile you want to migrate and click on it.

    When using Windows 2000 or later clients, if NetBIOS over TCP/IP is NOT disabled, then -the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet -Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print traffic).

    I am using the term "migrate" lossely. You can copy a profile to +create a group profile. You can give the user 'Everyone' rights to the +profile you copy this to. That is what you need to do, since your samba +domain is not a member of a trust relationship with your NT4 PDC.

  • When NetBIOS over TCP/IP is disabled the use of DNS is essential. Most installations that -disable NetBIOS over TCP/IP today use MS Active Directory Service (ADS). ADS requires -Dynamic DNS with Service Resource Records (SRV RR) and with Incremental Zone Transfers (IXFR). -Use of DHCP with ADS is recommended as a further means of maintaining central control -over client workstation network configuration.

    22.1. Name Resolution in a pure Unix/Linux world

    The key configuration files covered in this section are:

      Click the 'Copy To' button.

    • In the box labelled 'Copy Profile to' add your new path, eg: + /etc/hostsc:\temp\foobar

    • /etc/resolv.conf

      Click on the button labelled 'Change' in the "Permitted to use" box.

    • /etc/host.conf

      Click on the group 'Everyone' and then click OK. This closes the + 'chose user' box.

    • /etc/nsswitch.conf

      Now click OK.

    22.1.1. /etc/hosts

    Contains a static list of IP Addresses and names. -eg:

    	127.0.0.1	localhost localhost.localdomain
-	192.168.1.1	bigbox.caldera.com	bigbox	alias4box

    The purpose of /etc/hosts is to provide a -name resolution mechanism so that uses do not need to remember -IP addresses.

    Network packets that are sent over the physical network transport -layer communicate not via IP addresses but rather using the Media -Access Control address, or MAC address. IP Addresses are currently -32 bits in length and are typically presented as four (4) decimal -numbers that are separated by a dot (or period). eg: 168.192.1.1

    MAC Addresses use 48 bits (or 6 bytes) and are typically represented -as two digit hexadecimal numbers separated by colons. eg: -40:8e:0a:12:34:56

    Every network interfrace must have an MAC address. Associated with -a MAC address there may be one or more IP addresses. There is NO -relationship between an IP address and a MAC address, all such assignments -are arbitary or discretionary in nature. At the most basic level all -network communications takes place using MAC addressing. Since MAC -addresses must be globally unique, and generally remains fixed for -any particular interface, the assignment of an IP address makes sense -from a network management perspective. More than one IP address can -be assigned per MAC address. One address must be the primary IP address, -this is the address that will be returned in the ARP reply.

    When a user or a process wants to communicate with another machine -the protocol implementation ensures that the "machine name" or "host -name" is resolved to an IP address in a manner that is controlled -by the TCP/IP configuration control files. The file -/etc/hosts is one such file.

    When the IP address of the destination interface has been -determined a protocol called ARP/RARP is used to identify -the MAC address of the target interface. ARP stands for Address -Resolution Protocol, and is a broadcast oriented method that -uses UDP (User Datagram Protocol) to send a request to all -interfaces on the local network segment using the all 1's MAC -address. Network interfaces are programmed to respond to two -MAC addresses only; their own unique address and the address -ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will -contain the MAC address and the primary IP address for each -interface.

    The /etc/hosts file is foundational to all -Unix/Linux TCP/IP installations and as a minumum will contain -the localhost and local network interface IP addresses and the -primary names by which they are known within the local machine. -This file helps to prime the pump so that a basic level of name -resolution can exist before any other method of name resolution -becomes available.

    Follow the above for every profile you need to migrate.

    22.1.2. /etc/resolv.conf

    This file tells the name resolution libraries:

    • 18.1.4.2. Side bar Notes

      The name of the domain to which the machine - belongs -

    • You should obtain the SID of your NT4 domain. You can use smbpasswd to do +this. Read the man page.

      The name(s) of any domains that should be - automatically searched when trying to resolve unqualified - host names to their IP address -

    • With Samba-3.0.0 alpha code you can import all you NT4 domain accounts +using the net samsync method. This way you can retain your profile +settings as well as all your users.

    18.1.4.3. moveuser.exe

    The name or IP address of available Domain - Name Servers that may be asked to perform name to address - translation lookups -

    • The W2K professional resource kit has moveuser.exe. moveuser.exe changes +the security of a profile from one user to another. This allows the account +domain to change, and/or the user name to change.

    22.1.3. /etc/host.conf

    18.1.4.4. Get SID

    /etc/host.conf is the primary means by -which the setting in /etc/resolv.conf may be affected. It is a -critical configuration file. This file controls the order by -which name resolution may procede. The typical structure is:

    You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 +Resource Kit.

    	order hosts,bind
-	multi on

    Windows NT 4.0 stores the local profile information in the registry under +the following key: +HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

    then both addresses should be returned. Please refer to the -man page for host.conf for further details.

    Under the ProfileList key, there will be subkeys named with the SIDs of the +users who have logged on to this computer. (To find the profile information +for the user whose locally cached profile you want to move, find the SID for +the user with the GetSID.exe utility.) Inside of the appropriate user's +subkey, you will see a string value named ProfileImagePath.

    22.1.4. /etc/nsswitch.conf

    18.2. Mandatory profiles

    This file controls the actual name resolution targets. The -file typically has resolver object specifications as follows:

    A Mandatory Profile is a profile that the user does NOT have the ability to overwrite. +During the user's session it may be possible to change the desktop environment, but +as the user logs out all changes made will be lost. If it is desired to NOT allow the +user any ability to change the desktop environment then this must be done through +policy settings. See previous chapter.

    	# /etc/nsswitch.conf
-	#
-	# Name Service Switch configuration file.
-	#
-
-	passwd:		compat
-	# Alternative entries for password authentication are:
-	# passwd:	compat files nis ldap winbind
-	shadow:		compat
-	group:		compat
-
-	hosts:		files nis dns
-	# Alternative entries for host name resolution are:
-	# hosts:	files dns nis nis+ hesoid db compat ldap wins
-	networks:	nis files dns
-
-	ethers:		nis files
-	protocols:	nis files
-	rpc:		nis files
-	services:	nis files

    Of course, each of these mechanisms requires that the appropriate -facilities and/or services are correctly configured.

    Under NO circumstances should the profile directory (or it's contents) be made read-only +as this may render the profile un-usable.

    It should be noted that unless a network request/message must be -sent, TCP/IP networks are silent. All TCP/IP communications assumes a -principal of speaking only when necessary.

    For MS Windows NT4/200x/XP the above method can be used to create mandatory profiles +also. To convert a group profile into a mandatory profile simply locate the NTUser.DAT +file in the copied profile and rename it to NTUser.MAN.

    Starting with version 2.2.0 samba has Linux support for extensions to -the name service switch infrastructure so that linux clients will -be able to obtain resolution of MS Windows NetBIOS names to IP -Addresses. To gain this functionality Samba needs to be compiled -with appropriate arguments to the make command (ie: make -nsswitch/libnss_wins.so). The resulting library should -then be installed in the /lib directory and -the "wins" parameter needs to be added to the "hosts:" line in -the /etc/nsswitch.conf file. At this point it -will be possible to ping any MS Windows machine by it's NetBIOS -machine name, so long as that machine is within the workgroup to -which both the samba machine and the MS Windows machine belong.

    For MS Windows 9x / Me it is the User.DAT file that must be renamed to User.MAN to +affect a mandatory profile.

    22.2. Name resolution as used within MS Windows networking18.3. Creating/Managing Group Profiles

    MS Windows networking is predicated about the name each machine -is given. This name is known variously (and inconsistently) as -the "computer name", "machine name", "networking name", "netbios name", -"SMB name". All terms mean the same thing with the exception of -"netbios name" which can apply also to the name of the workgroup or the -domain name. The terms "workgroup" and "domain" are really just a -simply name with which the machine is associated. All NetBIOS names -are exactly 16 characters in length. The 16th character is reserved. -It is used to store a one byte value that indicates service level -information for the NetBIOS name that is registered. A NetBIOS machine -name is therefore registered for each service type that is provided by -the client/server.

    Most organisations are arranged into departments. There is a nice benenfit in +this fact since usually most users in a department will require the same desktop +applications and the same desktop layout. MS Windows NT4/200x/XP will allow the +use of Group Profiles. A Group Profile is a profile that is created firstly using +a template (example) user. Then using the profile migration tool (see above) the +profile is assigned access rights for the user group that needs to be given access +to the group profile.

    The following are typical NetBIOS name/service type registrations:

    The next step is rather important. PLEASE NOTE: Instead of assigning a group profile +to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned +the now modified profile.

    	Unique NetBIOS Names:
-		MACHINENAME<00>	= Server Service is running on MACHINENAME
-		MACHINENAME<03> = Generic Machine Name (NetBIOS name)
-		MACHINENAME<20> = LanMan Server service is running on MACHINENAME
-		WORKGROUP<1b> = Domain Master Browser
-
-	Group Names:
-		WORKGROUP<03> = Generic Name registered by all members of WORKGROUP
-		WORKGROUP<1c> = Domain Controllers / Netlogon Servers
-		WORKGROUP<1d> = Local Master Browsers
-		WORKGROUP<1e> = Internet Name Resolvers

    It should be noted that all NetBIOS machines register their own -names as per the above. This is in vast contrast to TCP/IP -installations where traditionally the system administrator will -determine in the /etc/hosts or in the DNS database what names -are associated with each IP address.

    One further point of clarification should be noted, the /etc/hosts -file and the DNS records do not provide the NetBIOS name type information -that MS Windows clients depend on to locate the type of service that may -be needed. An example of this is what happens when an MS Windows client -wants to locate a domain logon server. It find this service and the IP -address of a server that provides it by performing a lookup (via a -NetBIOS broadcast) for enumeration of all machines that have -registered the name type *<1c>. A logon request is then sent to each -IP address that is returned in the enumerated list of IP addresses. Which -ever machine first replies then ends up providing the logon services.

    The name "workgroup" or "domain" really can be confusing since these -have the added significance of indicating what is the security -architecture of the MS Windows network. The term "workgroup" indicates -that the primary nature of the network environment is that of a -peer-to-peer design. In a WORKGROUP all machines are responsible for -their own security, and generally such security is limited to use of -just a password (known as SHARE MODE security). In most situations -with peer-to-peer networking the users who control their own machines -will simply opt to have no security at all. It is possible to have -USER MODE security in a WORKGROUP environment, thus requiring use -of a user name and a matching password.

    MS Windows networking is thus predetermined to use machine names -for all local and remote machine message passing. The protocol used is -called Server Message Block (SMB) and this is implemented using -the NetBIOS protocol (Network Basic Input Output System). NetBIOS can -be encapsulated using LLC (Logical Link Control) protocol - in which case -the resulting protocol is called NetBEUI (Network Basic Extended User -Interface). NetBIOS can also be run over IPX (Internetworking Packet -Exchange) protocol as used by Novell NetWare, and it can be run -over TCP/IP protocols - in which case the resulting protocol is called -NBT or NetBT, the NetBIOS over TCP/IP.

    Be careful with group profiles, if the user who is a member of a group also + has a personal profile, then the result will be a fusion (merge) of the two. +

    18.4. Default Profile for Windows Users

    MS Windows machines use a complex array of name resolution mechanisms. -Since we are primarily concerned with TCP/IP this demonstration is -limited to this area.

    MS Windows 9x / Me and NT4/200x/XP will use a default profile for any user for whom +a profile does not already exist. Armed with a knowledge of where the default profile +is located on the Windows workstation, and knowing which registry keys affect the path +from which the default profile is created, it is possible to modify the default profile +to one that has been optimised for the site. This has significant administrative +advantages.

    22.2.1. The NetBIOS Name Cache18.4.1. MS Windows 9x/Me

    All MS Windows machines employ an in memory buffer in which is -stored the NetBIOS names and IP addresses for all external -machines that that machine has communicated with over the -past 10-15 minutes. It is more efficient to obtain an IP address -for a machine from the local cache than it is to go through all the -configured name resolution mechanisms.

    To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System +Policy Editor or change the registry directly.

    If a machine whose name is in the local name cache has been shut -down before the name had been expired and flushed from the cache, then -an attempt to exchange a message with that machine will be subject -to time-out delays. i.e.: Its name is in the cache, so a name resolution -lookup will succeed, but the machine can not respond. This can be -frustrating for users - but it is a characteristic of the protocol.

    To enable default per user profiles in Windows 9x / Me, launch the System Policy Editor, then +select File -> Open Registry, then click on the Local Computer icon, click on Windows 98 System, +select User Profiles, click on the enable box. Do not forget to save the registry changes.

    The MS Windows utility that allows examination of the NetBIOS -name cache is called "nbtstat". The Samba equivalent of this -is called "nmblookup".

    To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive +HKEY_LOCAL_MACHINE\Network\Logon. Now add a DWORD type key with the name +"User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0.

    22.2.2. The LMHOSTS file

    18.4.1.1. How User Profiles Are Handled in Windows 9x / Me?

    This file is usually located in MS Windows NT 4.0 or -2000 in C:\WINNT\SYSTEM32\DRIVERS\ETC and contains -the IP Address and the machine name in matched pairs. The +>When a user logs on to a Windows 9x / Me machine, the local profile path, LMHOSTS file performs NetBIOS name -to IP address mapping oriented.

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList, is checked +for an existing entry for that user:

    It typically looks like:

    If the user has an entry in this registry location, Windows 9x / Me checks for a locally cached +version of the user profile. Windows 9x / Me also checks the user's home directory (or other +specified directory if the location has been modified) on the server for the User Profile. +If a profile exists in both locations, the newer of the two is used. If the User Profile exists +on the server, but does not exist on the local machine, the profile on the server is downloaded +and used. If the User Profile only exists on the local machine, that copy is used.

    	# Copyright (c) 1998 Microsoft Corp.
-	#
-	# This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
-	# over TCP/IP) stack for Windows98
-	#
-	# This file contains the mappings of IP addresses to NT computernames
-	# (NetBIOS) names.  Each entry should be kept on an individual line.
-	# The IP address should be placed in the first column followed by the
-	# corresponding computername. The address and the comptername
-	# should be separated by at least one space or tab. The "#" character
-	# is generally used to denote the start of a comment (see the exceptions
-	# below).
-	#
-	# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
-	# files and offers the following extensions:
-	#
-	#      #PRE
-	#      #DOM:<domain>
-	#      #INCLUDE <filename>
-	#      #BEGIN_ALTERNATE
-	#      #END_ALTERNATE
-	#      \0xnn (non-printing character support)
-	#
-	# Following any entry in the file with the characters "#PRE" will cause
-	# the entry to be preloaded into the name cache. By default, entries are
-	# not preloaded, but are parsed only after dynamic name resolution fails.
-	#
-	# Following an entry with the "#DOM:<domain>" tag will associate the
-	# entry with the domain specified by <domain>. This affects how the
-	# browser and logon services behave in TCP/IP environments. To preload
-	# the host name associated with #DOM entry, it is necessary to also add a
-	# #PRE to the line. The <domain> is always preloaded although it will not
-	# be shown when the name cache is viewed.
-	#
-	# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
-	# software to seek the specified <filename> and parse it as if it were
-	# local. <filename> is generally a UNC-based name, allowing a
-	# centralized lmhosts file to be maintained on a server.
-	# It is ALWAYS necessary to provide a mapping for the IP address of the
-	# server prior to the #INCLUDE. This mapping must use the #PRE directive.
-	# In addtion the share "public" in the example below must be in the
-	# LanManServer list of "NullSessionShares" in order for client machines to
-	# be able to read the lmhosts file successfully. This key is under
-	# \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
-	# in the registry. Simply add "public" to the list found there.
-	#
-	# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
-	# statements to be grouped together. Any single successful include
-	# will cause the group to succeed.
-	#
-	# Finally, non-printing characters can be embedded in mappings by
-	# first surrounding the NetBIOS name in quotations, then using the
-	# \0xnn notation to specify a hex value for a non-printing character.
-	#
-	# The following example illustrates all of these extensions:
-	#
-	# 102.54.94.97     rhino         #PRE #DOM:networking  #net group's DC
-	# 102.54.94.102    "appname  \0x14"                    #special app server
-	# 102.54.94.123    popular            #PRE             #source server
-	# 102.54.94.117    localsrv           #PRE             #needed for the include
-	#
-	# #BEGIN_ALTERNATE
-	# #INCLUDE \\localsrv\public\lmhosts
-	# #INCLUDE \\rhino\public\lmhosts
-	# #END_ALTERNATE
-	#
-	# In the above example, the "appname" server contains a special
-	# character in its name, the "popular" and "localsrv" server names are
-	# preloaded, and the "rhino" server name is specified so it can be used
-	# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
-	# system is unavailable.
-	#
-	# Note that the whole file is parsed including comments on each lookup,
-	# so keeping the number of comments to a minimum will improve performance.
-	# Therefore it is not advisable to simply add lmhosts file entries onto the
-	# end of this file.

    If a User Profile is not found in either location, the Default User Profile from the Windows 9x / Me +machine is used and is copied to a newly created folder for the logged on user. At log off, any +changes that the user made are written to the user's local profile. If the user has a roaming +profile, the changes are written to the user's profile on the server.

    22.2.3. HOSTS file18.4.2. MS Windows NT4 Workstation

    This file is usually located in MS Windows NT 4.0 or 2000 in +>On MS Windows NT4 the default user profile is obtained from the location C:\WINNT\SYSTEM32\DRIVERS\ETC and contains -the IP Address and the IP hostname in matched pairs. It can be -used by the name resolution infrastructure in MS Windows, depending -on how the TCP/IP environment is configured. This file is in -every way the equivalent of the Unix/Linux %SystemRoot%\Profiles which in a default installation will translate to +C:\WinNT\Profiles. Under this directory on a clean install there will be +three (3) directories: Administrator, All Users, Default User.

    The All Users directory contains menu settings that are common across all +system users. The Default User directory contains menu entries that are +customisable per user depending on the profile settings chosen/created.

    When a new user first logs onto an MS Windows NT4 machine a new profile is created from:

    All Users settings
    Default User settings (contains the default NTUser.DAT file)

    When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain +the following steps are followed in respect of profile handling:

    1. The users' account information which is obtained during the logon process contains + the location of the users' desktop profile. The profile path may be local to the + machine or it may be located on a network share. If there exists a profile at the location + of the path from the user account, then this profile is copied to the location + %SystemRoot%\Profiles\%USERNAME%. This profile then inherits the + settings in the All Users profile in the %SystemRoot%\Profiles + location. +

    2. If the user account has a profile path, but at it's location a profile does not exist, + then a new profile is created in the %SystemRoot%\Profiles\%USERNAME% + directory from reading the Default User profile. +

    3. If the NETLOGON share on the authenticating server (logon server) contains a policy file + (NTConfig.POL) then it's contents are applied to the NTUser.DAT + which is applied to the HKEY_CURRENT_USER part of the registry. +

    4. When the user logs out, if the profile is set to be a roaming profile it will be written + out to the location of the profile. The NTuser.DAT file is then + re-created from the contents of the HKEY_CURRENT_USER contents. + Thus, should there not exist in the NETLOGON share an /etc/hosts file.

    22.2.4. DNS Lookup

    This capability is configured in the TCP/IP setup area in the network -configuration facility. If enabled an elaborate name resolution sequence -is followed the precise nature of which isdependant on what the NetBIOS -Node Type parameter is configured to. A Node Type of 0 means use -NetBIOS broadcast (over UDP broadcast) is first used if the name -that is the subject of a name lookup is not found in the NetBIOS name -cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to -Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the -WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast -lookup is used.

    22.2.5. WINS Lookup

    A WINS (Windows Internet Name Server) service is the equivaent of the -rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores -the names and IP addresses that are registered by a Windows client -if the TCP/IP setup has been given at least one WINS Server IP Address.

    NTConfig.POL at the + next logon, the effect of the provious NTConfig.POL will still be held + in the profile. The effect of this is known as tatooing. +

    To configure Samba to be a WINS server the following parameter needs -to be added to the MS Windows NT4 profiles may be Local or Roaming. A Local profile +will stored in the smb.conf file:

    %SystemRoot%\Profiles\%USERNAME% location. A roaming profile will +also remain stored in the same way, unless the following registry key is created:

    	wins support = Yes

    HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\ + "DeleteRoamingCache"=dword:00000001 + +In which case, the local copy (in %SystemRoot%\Profiles\%USERNAME%) will be +deleted on logout.

    To configure Samba to use a WINS server the following parameters are -needed in the Under MS Windows NT4 default locations for common resources (like smb.conf file:

    My Documents +may be redirected to a network share by modifying the following registry keys. These changes may be affected +via use of the System Policy Editor (to do so may require that you create your owns template extension +for the policy editor to allow this to be done through the GUI. Another way to do this is by way of first +creating a default user profile, then while logged in as that user, run regedt32 to edit the key settings.

    The Registry Hive key that affects the behaviour of folders that are part of the default user profile +are controlled by entries on Windows NT4 is:

    	wins support = No
-	wins server = xxx.xxx.xxx.xxx
    HKEY_CURRENT_USER + \Software + \Microsoft + \Windows + \CurrentVersion + \Explorer + \User Shell Folders\

    where xxx.xxx.xxx.xxx is the IP address -of the WINS server.

    The above hive key contains a list of automatically managed folders. The default entries are:

            Name            Default Value
+        --------------  -----------------------------------------
+        AppData         %USERPROFILE%\Application Data
+        Desktop         %USERPROFILE%\Desktop
+        Favorites       %USERPROFILE%\Favorites
+        NetHood         %USERPROFILE%\NetHood
+        PrintHood       %USERPROFILE%\PrintHood
+        Programs        %USERPROFILE%\Start Menu\Programs
+        Recent          %USERPROFILE%\Recent
+        SendTo          %USERPROFILE%\SendTo
+        Start Menu      %USERPROFILE%\Start Menu
+        Startup         %USERPROFILE%\Start Menu\Programs\Startup
+
    +

    The registry key that contains the location of the default profile settings is: + +

    	HKEY_LOCAL_MACHINE
+		\SOFTWARE
+			\Microsoft
+				\Windows
+					\CurrentVersion
+						\Explorer
+							\User Shell Folders
    + +The default entries are: + +
    	Common Desktop		%SystemRoot%\Profiles\All Users\Desktop
+	Common Programs		%SystemRoot%\Profiles\All Users\Programs
+	Common Start Menu	%SystemRoot%\Profiles\All Users\Start Menu
+	Common Startu	p	%SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup

    Chapter 23. Improved browsing in samba

    18.4.3. MS Windows 200x/XP

    23.1. Overview of browsing

    SMB networking provides a mechanism by which clients can access a list -of machines in a network, a so-called browse list. This list -contains machines that are ready to offer file and/or print services -to other machines within the network. Thus it does not include -machines which aren't currently able to do server tasks. The browse -list is heavily used by all SMB clients. Configuration of SMB -browsing has been problematic for some Samba users, hence this -document.

    MS Windows 2000 and later, as with Samba 3 and later, can be -configured to not use NetBIOS over TCP/IP. When configured this way -it is imperative that name resolution (using DNS/LDAP/ADS) be correctly -configured and operative. Browsing will NOT work if name resolution -from SMB machine names to IP addresses does not function correctly.

    Where NetBIOS over TCP/IP is enabled use of a WINS server is highly -recommended to aid the resolution of NetBIOS (SMB) names to IP addresses. -WINS allows remote segment clients to obtain NetBIOS name_type information -that can NOT be provided by any other means of name resolution.

    MS Windows XP Home Edition does use default per user profiles, but can not participate + in domain security, can not log onto an NT/ADS style domain, and thus can obtain the profile + only from itself. While there are benefits in doing this the beauty of those MS Windows + clients that CAN participate in domain logon processes allows the administrator to create + a global default profile and to enforce it through the use of Group Policy Objects (GPOs). +

    23.2. Browsing support in samba

    Samba facilitates browsing. The browsing is supported by nmbd -and is also controlled by options in the When a new user first logs onto MS Windows 200x/XP machine the default profile is obtained from +smb.conf file. -Samba can act as a local browse master for a workgroup and the ability -for samba to support domain logons and scripts is now available.

    Samba can also act as a domain master browser for a workgroup. This -means that it will collate lists from local browse masters into a -wide area network server list. In order for browse clients to -resolve the names they may find in this list, it is recommended that -both samba and your clients use a WINS server.

    Note that you should NOT set Samba to be the domain master for a -workgroup that has the same name as an NT Domain: on each wide area -network, you must only ever have one domain master browser per workgroup, -regardless of whether it is NT, Samba or any other type of domain master -that is providing this service.

    C:\Documents and Settings\Default User. The administrator can modify (or change +the contents of this location and MS Windows 200x/XP will gladly user it. This is far from the optimum +arrangement since it will involve copying a new default profile to every MS Windows 200x/XP client +workstation.

    When MS Windows 200x/XP participate in a domain security context, and if the default user +profile is not found, then the client will search for a default profile in the NETLOGON share +of the authenticating server. ie: In MS Windows parlance: +%LOGONSERVER%\NETLOGON\Default User and if one exits there it will copy this +to the workstation to the C:\Documents and Settings\ under the Windows +login name of the user.

    Nmbd can be configured as a WINS server, but it is not -necessary to specifically use samba as your WINS server. MS Windows -NT4, Server or Advanced Server 2000 or 2003 can be configured as -your WINS server. In a mixed NT/2000/2003 server and samba environment on -a Wide Area Network, it is recommended that you use the Microsoft -WINS server capabilities. In a samba-only environment, it is -recommended that you use one and only one Samba server as your WINS server.

    This path translates, in Samba parlance, to the smb.conf [NETLOGON] share. The directory + should be created at the root of this share and msut be called Default Profile. +

    To get browsing to work you need to run nmbd as usual, but will need -to use the workgroup option in If a default profile does not exist in this location then MS Windows 200x/XP will use the local +default profile.

    On loging out, the users' desktop profile will be stored to the location specified in the registry +settings that pertain to the user. If no specific policies have been created, or passed to the client +during the login process (as Samba does automatically), then the user's profile will be written to +the local machine only under the path smb.confC:\Documents and Settings\%USERNAME%.

    Those wishing to modify the default behaviour can do so through up to three methods:

    • Modify the registry keys on the local machine manually and place the new default profile in the + NETLOGON share root - NOT recommended as it is maintenance intensive. +

    • Create an NT4 style NTConfig.POL file that specified this behaviour and locate this file + in the root of the NETLOGON share along with the new default profile. +

    • Create a GPO that enforces this through Active Directory, and place the new default profile + in the NETLOGON share. +

    The Registry Hive key that affects the behaviour of folders that are part of the default user profile +are controlled by entries on Windows 200x/XP is:

    	HKEY_CURRENT_USER
+		\Software
+			\Microsoft
+				\Windows
+					\CurrentVersion
+						\Explorer
+							\User Shell Folders\

    The above hive key contains a list of automatically managed folders. The default entries are:

    	Name		Default Value
+	--------------	-----------------------------------------
+	AppData		%USERPROFILE%\Application Data
+	Cache		%USERPROFILE%\Local Settings\Temporary Internet Files
+	Cookies		%USERPROFILE%\Cookies
+	Desktop		%USERPROFILE%\Desktop
+	Favorites	%USERPROFILE%\Favorites
+	History		%USERPROFILE%\Local Settings\History
+	Local AppData	%USERPROFILE%\Local Settings\Application Data
+	Local Settings	%USERPROFILE%\Local Settings
+	My Pictures	%USERPROFILE%\My Documents\My Pictures
+	NetHood		%USERPROFILE%\NetHood
+	Personal	%USERPROFILE%\My Documents
+	PrintHood	%USERPROFILE%\PrintHood
+	Programs	%USERPROFILE%\Start Menu\Programs
+	Recent		%USERPROFILE%\Recent
+	SendTo		%USERPROFILE%\SendTo
+	Start Menu	%USERPROFILE%\Start Menu
+	Startup		%USERPROFILE%\Start Menu\Programs\Startup
+	Templates	%USERPROFILE%\Templates
+
    -to control what workgroup Samba becomes a part of.

    Samba also has a useful option for a Samba server to offer itself for -browsing on another subnet. It is recommended that this option is only -used for 'unusual' purposes: announcements over the internet, for -example. See remote announce in the -smb.conf man page.

    There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all +the others are of type REG_EXPAND_SZ.

    It makes a huge difference to the speed of handling roaming user profiles if all the folders are +stored on a dedicated location on a network server. This means that it will NOT be necessary to +write Outlook PST file over the network for every login and logout.

    To set this to a network location you could use the following examples: + +

    	%LOGONSERVER%\%USERNAME%\Default Folders
    + +This would store the folders in the user's home directory under a directory called "Default Folders" + +You could also use: + +
    	\\SambaServer\FolderShare\%USERNAME%
    + +in which case the default folders will be stored in the server named SambaServer +in the share called FolderShare under a directory that has the name of the MS Windows +user as seen by the Linux/Unix file system.

    Please note that once you have created a default profile share, you MUST migrate a user's profile +(default or custom) to it.

    MS Windows 200x/XP profiles may be Local or Roaming. +A roaming profile will be cached locally unless the following registry key is created:

    	HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
+	"DeleteRoamingCache"=dword:00000001
    + +In which case, the local cache copy will be deleted on logout.

    Chapter 19. Interdomain Trust Relationships

    Samba-3 supports NT4 style domain trust relationships. This is feature that many sites +will want to use if they migrate to Samba-3 from and NT4 style domain and do NOT want to +adopt Active Directory or an LDAP based authentication back end. This section explains +some background information regarding trust relationships and how to create them. It is now +possible for Samba-3 to NT4 trust (and vice versa), as well as Samba3 to Samba3 trusts.

    23.3. Problem resolution19.1. Trust Relationship Background

    If something doesn't work then hopefully the log.nmb file will help -you track down the problem. Try a debug level of 2 or 3 for finding -problems. Also note that the current browse list usually gets stored -in text form in a file called browse.dat.

    Note that if it doesn't work for you, then you should still be able to -type the server name as \\SERVER in filemanager then -hit enter and filemanager should display the list of available shares.

    MS Windows NT3.x/4.0 type security domains employ a non-hierarchical security structure. +The limitations of this architecture as it affects the scalability of MS Windows networking +in large organisations is well known. Additionally, the flat-name space that results from +this design significantly impacts the delegation of administrative responsibilities in +large and diverse organisations.

    Some people find browsing fails because they don't have the global -guest account set to a valid account. Remember that the -IPC$ connection that lists the shares is done as guest, and thus you must -have a valid guest account.

    Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means +of circumventing the limitations of the older technologies. Not every organisation is ready +or willing to embrace ADS. For small companies the older NT4 style domain security paradigm +is quite adequate, there thus remains an entrenched user base for whom there is no direct +desire to go through a disruptive change to adopt ADS.

    Microsoft introduced with MS Windows NT the ability to allow differing security domains +to affect a mechanism so that users from one domain may be given access rights and privileges +in another domain. The language that describes this capability is couched in terms of +MS Windows 2000 and upwards (as with Samba) can be configured to disallow -anonymous (ie: Guest account) access to the IPC$ share. In that case, the -MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the -name of the currently logged in user to query the IPC$ share. MS Windows -9X clients are not able to do this and thus will NOT be able to browse -server resources.Trusts

    . Specifically, one domain will trust the users +from another domain. The domain from which users are available to another security domain is +said to be a trusted domain. The domain in which those users have assigned rights and privileges +is the trusting domain. With NT3.x/4.0 all trust relationships are always in one direction only, +thus if users in both domains are to have privileges and rights in each others' domain, then it is +necessary to establish two (2) relationships, one in each direction.

    The other big problem people have is that their broadcast address, -netmask or IP address is wrong (specified with the "interfaces" option -in smb.conf)

    In an NT4 style MS security domain, all trusts are non-transitive. This means that if there +are three (3) domains (let's call them RED, WHITE, and BLUE) where RED and WHITE have a trust +relationship, and WHITE and BLUE have a trust relationship, then it holds that there is no +implied trust between the RED and BLUE domains. ie: Relationships are explicit and not +transitive.

    New to MS Windows 2000 ADS security contexts is the fact that trust relationships are two-way +by default. Also, all inter-ADS domain trusts are transitive. In the case of the RED, WHITE and BLUE +domains above, with Windows 2000 and ADS the RED and BLUE domains CAN trust each other. This is +an inherent feature of ADS domains. Samba-3 implements MS Windows NT4 +style Interdomain trusts and interoperates with MS Windows 200x ADS +security domains in similar manner to MS Windows NT4 style domains.

    23.4. Browsing across subnets19.2. Native MS Windows NT4 Trusts Configuration

    Since the release of Samba 1.9.17(alpha1) Samba has been -updated to enable it to support the replication of browse lists -across subnet boundaries. New code and options have been added to -achieve this. This section describes how to set this feature up -in different settings.

    To see browse lists that span TCP/IP subnets (ie. networks separated -by routers that don't pass broadcast traffic) you must set up at least -one WINS server. The WINS server acts as a DNS for NetBIOS names, allowing -NetBIOS name to IP address translation to be done by doing a direct -query of the WINS server. This is done via a directed UDP packet on -port 137 to the WINS server machine. The reason for a WINS server is -that by default, all NetBIOS name to IP address translation is done -by broadcasts from the querying machine. This means that machines -on one subnet will not be able to resolve the names of machines on -another subnet without using a WINS server.

    Remember, for browsing across subnets to work correctly, all machines, -be they Windows 95, Windows NT, or Samba servers must have the IP address -of a WINS server given to them by a DHCP server, or by manual configuration -(for Win95 and WinNT, this is in the TCP/IP Properties, under Network -settings) for Samba this is in the smb.conf file.

    There are two steps to creating an interdomain trust relationship.

    23.4.1. How does cross subnet browsing work ?19.2.1. NT4 as the Trusting Domain (ie. creating the trusted account)

    Cross subnet browsing is a complicated dance, containing multiple -moving parts. It has taken Microsoft several years to get the code -that achieves this correct, and Samba lags behind in some areas. -Samba is capable of cross subnet browsing when configured correctly.

    Consider a network set up as follows :

                                       (DMB)
-             N1_A      N1_B        N1_C       N1_D        N1_E
-              |          |           |          |           |
-          -------------------------------------------------------
-            |          subnet 1                       |
-          +---+                                      +---+
-          |R1 | Router 1                  Router 2   |R2 |
-          +---+                                      +---+
-            |                                          |
-            |  subnet 2              subnet 3          |
-  --------------------------       ------------------------------------
-  |     |     |      |               |        |         |           |
- N2_A  N2_B  N2_C   N2_D           N3_A     N3_B      N3_C        N3_D 
-                    (WINS)

    Consisting of 3 subnets (1, 2, 3) connected by two routers -(R1, R2) - these do not pass broadcasts. Subnet 1 has 5 machines -on it, subnet 2 has 4 machines, subnet 3 has 4 machines. Assume -for the moment that all these machines are configured to be in the -same workgroup (for simplicities sake). Machine N1_C on subnet 1 -is configured as Domain Master Browser (ie. it will collate the -browse lists for the workgroup). Machine N2_D is configured as -WINS server and all the other machines are configured to register -their NetBIOS names with it.

    As all these machines are booted up, elections for master browsers -will take place on each of the three subnets. Assume that machine -N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on -subnet 3 - these machines are known as local master browsers for -their particular subnet. N1_C has an advantage in winning as the -local master browser on subnet 1 as it is set up as Domain Master -Browser.

    On each of the three networks, machines that are configured to -offer sharing services will broadcast that they are offering -these services. The local master browser on each subnet will -receive these broadcasts and keep a record of the fact that -the machine is offering a service. This list of records is -the basis of the browse list. For this case, assume that -all the machines are configured to offer services so all machines -will be on the browse list.

    For each network, the local master browser on that network is -considered 'authoritative' for all the names it receives via -local broadcast. This is because a machine seen by the local -master browser via a local broadcast must be on the same -network as the local master browser and thus is a 'trusted' -and 'verifiable' resource. Machines on other networks that -the local master browsers learn about when collating their -browse lists have not been directly seen - these records are -called 'non-authoritative'.

    At this point the browse lists look as follows (these are -the machines you would see in your network neighborhood if -you looked in it on a particular network right now).

    Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D

    Note that at this point all the subnets are separate, no -machine is seen across any of the subnets.

    Now examine subnet 2. As soon as N2_B has become the local -master browser it looks for a Domain master browser to synchronize -its browse list with. It does this by querying the WINS server -(N2_D) for the IP address associated with the NetBIOS name -WORKGROUP>1B<. This name was registerd by the Domain master -browser (N1_C) with the WINS server as soon as it was booted.

    Once N2_B knows the address of the Domain master browser it -tells it that is the local master browser for subnet 2 by -sending a MasterAnnouncement packet as a UDP port 138 packet. -It then synchronizes with it by doing a NetServerEnum2 call. This -tells the Domain Master Browser to send it all the server -names it knows about. Once the domain master browser receives -the MasterAnnouncement packet it schedules a synchronization -request to the sender of that packet. After both synchronizations -are done the browse lists look like :

    Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
-
-Servers with a (*) after them are non-authoritative names.

    At this point users looking in their network neighborhood on -subnets 1 or 2 will see all the servers on both, users on -subnet 3 will still only see the servers on their own subnet.

    For MS Windows NT4, all domain trust relationships are configured using the Domain User Manager. +To affect a two way trust relationship it is necessary for each domain administrator to make +available (for use by an external domain) it's security resources. This is done from the Domain +User Manager Policies entry on the menu bar. From the Policy menu, select Trust Relationships, then +next to the lower box that is labelled "Permitted to Trust this Domain" are two buttons, "Add" and +"Remove". The "Add" button will open a panel in which needs to be entered the remote domain that +will be able to assign user rights to your domain. In addition it is necessary to enter a password +that is specific to this trust relationship. The password needs to be +typed twice (for standard confirmation).

    19.2.2. NT4 as the Trusted Domain (ie. creating trusted account's password)

    The same sequence of events that occured for N2_B now occurs -for the local master browser on subnet 3 (N3_D). When it -synchronizes browse lists with the domain master browser (N1_A) -it gets both the server entries on subnet 1, and those on -subnet 2. After N3_D has synchronized with N1_C and vica-versa -the browse lists look like.

    A trust relationship will work only when the other (trusting) domain makes the appropriate connections +with the trusted domain. To consumate the trust relationship the administrator will launch the +Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the +"Add" button that is next to the box that is labelled "Trusted Domains". A panel will open in +which must be entered the name of the remote domain as well as the password assigned to that trust.

    19.3. Configuring Samba NT-style Domain Trusts

    Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*),
-                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-
-Servers with a (*) after them are non-authoritative names.

    This description is meant to be a fairly short introduction about how to set up a Samba server so +that it could participate in interdomain trust relationships. Trust relationship support in Samba +is in its early stage, so lot of things don't work yet.

    At this point users looking in their network neighborhood on -subnets 1 or 3 will see all the servers on all sunbets, users on -subnet 2 will still only see the servers on subnets 1 and 2, but not 3.

    Each of the procedures described below is treated as they were performed with Windows NT4 Server on +one end. The remote end could just as well be another Samba-3 domain. It can be clearly seen, after +reading this document, that combining Samba-specific parts of what's written below leads to trust +between domains in purely Samba environment.

    19.3.1. Samba-3 as the Trusting Domain

    Finally, the local master browser for subnet 2 (N2_B) will sync again -with the domain master browser (N1_C) and will recieve the missing -server entries. Finally - and as a steady state (if no machines -are removed or shut off) the browse lists will look like :

    In order to set Samba PDC to be trusted party of the relationship first you need +to create special account for the domain that will be the trusting party. To do that, +you can use the 'smbpasswd' utility. Creating the trusted domain account is very +similiar to creating a trusted machine account. Suppose, your domain is +called SAMBA, and the remote domain is called RUMBA. The first step +will be to issue this command from your favourite shell:

    Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*),
-                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
+CLASS="SCREEN"
+>    deity# smbpasswd -a -i rumba
+    	New SMB password: XXXXXXXX
+    	Retype SMB password: XXXXXXXX
+    	Added user rumba$
    -Subnet3 N3_D N3_A, N3_B, N3_C, N3_D - N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), - N2_A(*), N2_B(*), N2_C(*), N2_D(*) - -Servers with a (*) after them are non-authoritative names.

    Synchronizations between the domain master browser and local -master browsers will continue to occur, but this should be a -steady state situation.

    If either router R1 or R2 fails the following will occur:

    1. Names of computers on each side of the inaccessible network fragments - will be maintained for as long as 36 minutes, in the network neighbourhood - lists. -

    2. -a means to add a new account into the +passdb database and -i means: ''create this +account with the InterDomain trust flag''

      Attempts to connect to these inaccessible computers will fail, but the - names will not be removed from the network neighbourhood lists. -

    3. The account name will be 'rumba$' (the name of the remote domain)

      If one of the fragments is cut off from the WINS server, it will only - be able to access servers on its local subnet, by using subnet-isolated - broadcast NetBIOS name resolution. The effects are similar to that of - losing access to a DNS server. -

    After issuing this command you'll be asked to enter the password for +the account. You can use any password you want, but be aware that Windows NT will +not change this password until 7 days following account creation. +After the command returns successfully, you can look at the entry for new account +(in the way depending on your configuration) and see that account's name is +really RUMBA$ and it has 'I' flag in the flags field. Now you're ready to confirm +the trust by establishing it from Windows NT Server.

    Open 'User Manager for Domains' and from menu 'Policies' select 'Trust Relationships...'. +Right beside 'Trusted domains' list box press 'Add...' button. You will be prompted for +the trusted domain name and the relationship password. Type in SAMBA, as this is +your domain name, and the password used at the time of account creation. +Press OK and, if everything went without incident, you will see 'Trusted domain relationship +successfully established' message.

    23.5. Setting up a WINS server

    19.3.2. Samba-3 as the Trusted Domain

    Either a Samba machine or a Windows NT Server machine may be set up -as a WINS server. To set a Samba machine to be a WINS server you must -add the following option to the smb.conf file on the selected machine : -in the [globals] section add the line

    This time activities are somewhat reversed. Again, we'll assume that your domain +controlled by the Samba PDC is called SAMBA and NT-controlled domain is called RUMBA.

    wins support = yes

    The very first thing requirement is to add an account for the SAMBA domain on RUMBA's PDC.

    Versions of Samba prior to 1.9.17 had this parameter default to -yes. If you have any older versions of Samba on your network it is -strongly suggested you upgrade to a recent version, or at the very -least set the parameter to 'no' on all these machines.

    Launch the Domain User Manager, then from the menu select 'Policies', 'Trust Relationships'. +Now, next to 'Trusted Domains' box press the 'Add' button, and type in the name of the trusted +domain (SAMBA) and password securing the relationship.

    Machines with wins support = yes will keep a list of -all NetBIOS names registered with them, acting as a DNS for NetBIOS names.

    The password can be arbitrarily chosen. It is easy to change it the password +from Samba server whenever you want. After confirming the password your account is +ready for use. Now it's Samba's turn.

    You should set up only ONE wins server. Do NOT set the -wins support = yes option on more than one Samba -server.

    Using your favourite shell while being logged in as root, issue this command:

    To set up a Windows NT Server as a WINS server you need to set up -the WINS service - see your NT documentation for details. Note that -Windows NT WINS Servers can replicate to each other, allowing more -than one to be set up in a complex subnet environment. As Microsoft -refuse to document these replication protocols Samba cannot currently -participate in these replications. It is possible in the future that -a Samba->Samba WINS replication protocol may be defined, in which -case more than one Samba machine could be set up as a WINS server -but currently only one Samba server should have the -wins support = yes parameter set.

    deity# net rpc trustdom establish rumba

    After the WINS server has been configured you must ensure that all -machines participating on the network are configured with the address -of this WINS server. If your WINS server is a Samba machine, fill in -the Samba machine IP address in the "Primary WINS Server" field of -the "Control Panel->Network->Protocols->TCP->WINS Server" dialogs -in Windows 95 or Windows NT. To tell a Samba server the IP address -of the WINS server add the following line to the [global] section of -all smb.conf files :

    You will be prompted for the password you just typed on your Windows NT4 Server box. +Don not worry if you see an error message that mentions a returned code of +NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT. It means the +password you gave is correct and the NT4 Server says the account is +ready for interdomain connection and not for ordinary +connection. After that, be patient it can take a while (especially +in large networks), you should see the 'Success' message. Congratulations! Your trust +relationship has just been established.

    wins server = >name or IP address<

    where >name or IP address< is either the DNS name of the WINS server -machine or its IP address.

    Note that this line MUST NOT BE SET in the Note that you have to run this command as root because you must have write access to +the smb.conf file of the Samba -server acting as the WINS server itself. If you set both the -wins support = yes option and the -wins server = <name> option then -nmbd will fail to start.

    There are two possible scenarios for setting up cross subnet browsing. -The first details setting up cross subnet browsing on a network containing -Windows 95, Samba and Windows NT machines that are not configured as -part of a Windows NT Domain. The second details setting up cross subnet -browsing on networks that contain NT Domains.

    secrets.tdb file.

    Chapter 20. PAM Configuration for Centrally Managed Authentication

    23.6. Setting up Browsing in a WORKGROUP20.1. Samba and PAM

    To set up cross subnet browsing on a network containing machines -in up to be in a WORKGROUP, not an NT Domain you need to set up one -Samba server to be the Domain Master Browser (note that this is *NOT* -the same as a Primary Domain Controller, although in an NT Domain the -same machine plays both roles). The role of a Domain master browser is -to collate the browse lists from local master browsers on all the -subnets that have a machine participating in the workgroup. Without -one machine configured as a domain master browser each subnet would -be an isolated workgroup, unable to see any machines on any other -subnet. It is the presense of a domain master browser that makes -cross subnet browsing possible for a workgroup.

    In an WORKGROUP environment the domain master browser must be a -Samba server, and there must only be one domain master browser per -workgroup name. To set up a Samba server as a domain master browser, -set the following option in the [global] section of the A number of Unix systems (eg: Sun Solaris), as well as the +xxxxBSD family and Linux, now utilize the Pluggable Authentication +Modules (PAM) facility to provide all authentication, +authorization and resource control services. Prior to the +introduction of PAM, a decision to use an alternative to +the system password database (smb.conf file :

    /etc/passwd) +would require the provision of alternatives for all programs that provide +security services. Such a choice would involve provision of +alternatives to such programs as: domain master = yes

    login, +passwd, chown, etc.

    The domain master browser should also preferrably be the local master -browser for its own subnet. In order to achieve this set the following -options in the [global] section of the PAM provides a mechanism that disconnects these security programs +from the underlying authentication/authorization infrastructure. +PAM is configured either through one file smb.conf file :

    /etc/pam.conf (Solaris), +or by editing individual files that are located in /etc/pam.d.

    domain master = yes
-local master = yes
-preferred master = yes
-os level = 65

    The domain master browser may be the same machine as the WINS -server, if you require.

    Next, you should ensure that each of the subnets contains a -machine that can act as a local master browser for the -workgroup. Any MS Windows NT/2K/XP/2003 machine should be -able to do this, as will Windows 9x machines (although these -tend to get rebooted more often, so it's not such a good idea -to use these). To make a Samba server a local master browser -set the following options in the [global] section of the - If the PAM authentication module (loadable link library file) is located in the + default location then it is not necessary to specify the path. In the case of + Linux, the default location is /lib/security. If the module + is located other than default then the path may be specified as: + + 

    	auth       required      /other_path/pam_strange_module.so
+
    +

    The following is an example smb.conf file :

    /etc/pam.d/login configuration file. +This example had all options been uncommented is probably not usable +as it stacks many conditions before allowing successful completion +of the login process. Essentially all conditions can be disabled +by commenting them out except the calls to pam_pwdb.so.

    domain master = no
-local master = yes
-preferred master = yes
-os level = 65
    #%PAM-1.0 + # The PAM configuration file for the `login' service + # + auth required pam_securetty.so + auth required pam_nologin.so + # auth required pam_dialup.so + # auth optional pam_mail.so + auth required pam_pwdb.so shadow md5 + # account requisite pam_time.so + account required pam_pwdb.so + session required pam_pwdb.so + # session optional pam_lastlog.so + # password required pam_cracklib.so retry=3 + password required pam_pwdb.so shadow md5

    Do not do this for more than one Samba server on each subnet, -or they will war with each other over which is to be the local -master browser.

    PAM allows use of replacable modules. Those available on a +sample system include:

    The local master parameter allows Samba to act as a -local master browser. The preferred master causes nmbd -to force a browser election on startup and the os level$/bin/ls /lib/security -parameter sets Samba high enough so that it should win any browser elections.

    pam_access.so pam_ftp.so pam_limits.so + pam_ncp_auth.so pam_rhosts_auth.so pam_stress.so + pam_cracklib.so pam_group.so pam_listfile.so + pam_nologin.so pam_rootok.so pam_tally.so + pam_deny.so pam_issue.so pam_mail.so + pam_permit.so pam_securetty.so pam_time.so + pam_dialup.so pam_lastlog.so pam_mkhomedir.so + pam_pwdb.so pam_shells.so pam_unix.so + pam_env.so pam_ldap.so pam_motd.so + pam_radius.so pam_smbpass.so pam_unix_acct.so + pam_wheel.so pam_unix_auth.so pam_unix_passwd.so + pam_userdb.so pam_warn.so pam_unix_session.so

    If you have an NT machine on the subnet that you wish to -be the local master browser then you can disable Samba from -becoming a local master browser by setting the following -options in the The following example for the login program replaces the use of +the pam_pwdb.so module which uses the system +password database (/etc/passwd, +/etc/shadow, /etc/group) with +the module pam_smbpass.so which uses the Samba +database which contains the Microsoft MD4 encrypted password +hashes. This database is stored in either +/usr/local/samba/private/smbpasswd, +/etc/samba/smbpasswd, or in +/etc/samba.d/smbpasswd, depending on the +Samba implementation for your Unix/Linux system. The +pam_smbpass.so module is provided by +Samba version 2.2.1 or later. It can be compiled by specifying the +[global] section of the +>--with-pam_smbpass options when running Samba's smb.conf file :

    configure script. For more information +on the pam_smbpass module, see the documentation +in the source/pam_smbpass directory of the Samba +source distribution.

    domain master = no
-local master = no
-preferred master = no
-os level = 0
    #%PAM-1.0 + # The PAM configuration file for the `login' service + # + auth required pam_smbpass.so nodelay + account required pam_smbpass.so nodelay + session required pam_smbpass.so nodelay + password required pam_smbpass.so nodelay

    23.7. Setting up Browsing in a DOMAIN

    If you are adding Samba servers to a Windows NT Domain then -you must not set up a Samba server as a domain master browser. -By default, a Windows NT Primary Domain Controller for a Domain -name is also the Domain master browser for that name, and many -things will break if a Samba server registers the Domain master -browser NetBIOS name (DOMAIN<1B>) -with WINS instead of the PDC.

    For subnets other than the one containing the Windows NT PDC -you may set up Samba servers as local master browsers as -described. To make a Samba server a local master browser set -the following options in the [global] section -of the The following is the PAM configuration file for a particular +Linux system. The default condition uses smb.conf file :

    pam_pwdb.so.

    domain master = no
-local master = yes
-preferred master = yes
-os level = 65
    #%PAM-1.0 + # The PAM configuration file for the `samba' service + # + auth required pam_pwdb.so nullok nodelay shadow audit + account required pam_pwdb.so audit nodelay + session required pam_pwdb.so nodelay + password required pam_pwdb.so shadow md5

    If you wish to have a Samba server fight the election with machines -on the same subnet you may set the os level parameter -to lower levels. By doing this you can tune the order of machines that -will become local master browsers if they are running. For -more details on this see the section Forcing samba to be the master browser -below.

    In the following example the decision has been made to use the +smbpasswd database even for basic samba authentication. Such a +decision could also be made for the passwd program and would +thus allow the smbpasswd passwords to be changed using the passwd +program.

    If you have Windows NT machines that are members of the domain -on all subnets, and you are sure they will always be running then -you can disable Samba from taking part in browser elections and -ever becoming a local master browser by setting following options -in the [global] section of the smb.conf -file :

    	#%PAM-1.0
+	# The PAM configuration file for the `samba' service
+	#
+	auth       required     pam_smbpass.so nodelay
+	account    required     pam_pwdb.so audit nodelay
+	session    required     pam_pwdb.so nodelay
+	password   required     pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf

    domain master = no - local master = no - preferred master = no - os level = 0

    PAM allows stacking of authentication mechanisms. It is +also possible to pass information obtained within one PAM module through +to the next module in the PAM stack. Please refer to the documentation for +your particular system implementation for details regarding the specific +capabilities of PAM in this environment. Some Linux implmentations also +provide the pam_stack.so module that allows all +authentication to be configured in a single central file. The +pam_stack.so method has some very devoted followers +on the basis that it allows for easier administration. As with all issues in +life though, every decision makes trade-offs, so you may want examine the +PAM documentation for further helpful information.

    23.8. Forcing samba to be the master20.2. Distributed Authentication

    Who becomes the master browser is determined by an election -process using broadcasts. Each election packet contains a number of parameters -which determine what precedence (bias) a host should have in the -election. By default Samba uses a very low precedence and thus loses -elections to just about anyone else.

    If you want Samba to win elections then just set the os level global -option in The astute administrator will realize from this that the +combination of smb.conf to a higher number. It defaults to 0. Using 34 -would make it win all elections over every other system (except other -samba systems!)

    A os level of 2 would make it beat WfWg and Win95, but not MS Windows -NT/2K Server. A MS Windows NT/2K Server domain controller uses level 32.

    The maximum os level is 255

    If you want samba to force an election on startup, then set the +>pam_smbpass.so, preferred master global option in smb.conf to "yes". Samba will -then have a slight advantage over other potential master browsers -that are not preferred master browsers. Use this parameter with -care, as if you have two hosts (whether they are windows 95 or NT or -samba) on the same local subnet both set with preferred master to -"yes", then periodically and continually they will force an election -in order to become the local master browser.

    If you want samba to be a domain master browser, then it is -recommended that you also set preferred master to "yes", because -samba will not become a domain master browser for the whole of your -LAN or WAN if it is not also a local master browser on its own -broadcast isolated subnet.

    It is possible to configure two samba servers to attempt to become -the domain master browser for a domain. The first server that comes -up will be the domain master browser. All other samba servers will -attempt to become the domain master browser every 5 minutes. They -will find that another samba server is already the domain master -browser and will fail. This provides automatic redundancy, should -the current domain master browser fail.

    winbindd    , and a distributed +passdb backend, such as ldap, will allow the establishment of a +centrally managed, distributed +user/password database that can also be used by all +PAM (eg: Linux) aware programs and applications. This arrangement +can have particularly potent advantages compared with the +use of Microsoft Active Directory Service (ADS) in so far as +reduction of wide area network authentication traffic.

    23.9. Making samba the domain master20.3. PAM Configuration in smb.conf

    The domain master is responsible for collating the browse lists of -multiple subnets so that browsing can occur between subnets. You can -make samba act as the domain master by setting domain master = yes -in smb.conf. By default it will not be a domain master.

    Note that you should NOT set Samba to be the domain master for a -workgroup that has the same name as an NT Domain.

    There is an option in smb.conf called obey pam restrictions. +The following is from the on-line help for this option in SWAT;

    When samba is the domain master and the master browser it will listen -for master announcements (made roughly every twelve minutes) from local -master browsers on other subnets and then contact them to synchronise -browse lists.

    When Samba is configured 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 +encrypt passwords = yes. +The reason is that PAM modules cannot support the challenge/response +authentication mechanism needed in the presence of SMB +password encryption.

    If you want samba to be the domain master then I suggest you also set -the os level high enough to make sure it wins elections, and set -Default: preferred master to "yes", to get samba to force an election on -startup.

    Note that all your servers (including samba) and clients should be -using a WINS server to resolve NetBIOS names. If your clients are only -using broadcasting to resolve NetBIOS names, then two things will occur:

    obey pam restrictions = no

    1. your local master browsers will be unable to find a domain master - browser, as it will only be looking on the local subnet. -

    Chapter 21. Stackable VFS modules

    21.1. Introduction and configuration

    if a client happens to get hold of a domain-wide browse list, and - a user attempts to access a host in that list, it will be unable to - resolve the NetBIOS name of that host. -

    Since samba 3.0, samba supports stackable VFS(Virtual File System) modules. +Samba passes each request to access the unix file system thru the loaded VFS modules. +This chapter covers all the modules that come with the samba source and references to +some external modules.

    If, however, both samba and your clients are using a WINS server, then:

    You may have problems to compile these modules, as shared libraries are +compiled and linked in different ways on different systems. +They currently have been tested against GNU/linux and IRIX.

    To use the VFS modules, create a share similar to the one below. The +important parameter is the vfs object parameter which must point to +the exact pathname of the shared library objects. For example, to log all access +to files and use a recycle bin: + +

           [audit]
+                comment = Audited /data directory
+                path = /data
+                vfs object = /path/to/audit.so /path/to/recycle.so
+                writeable = yes
+                browseable = yes

    1. your local master browsers will contact the WINS server and, as long as - samba has registered that it is a domain master browser with the WINS - server, your local master browser will receive samba's ip address - as its domain master browser. -

    2. The modules are used in the order they are specified.

      when a client receives a domain-wide browse list, and a user attempts - to access a host in that list, it will contact the WINS server to - resolve the NetBIOS name of that host. as long as that host has - registered its NetBIOS name with the same WINS server, the user will - be able to see that host. -

    Further documentation on writing VFS modules for Samba can be found in +the Samba Developers Guide.

    23.10. Note about broadcast addresses21.2. Included modules

    If your network uses a "0" based broadcast address (for example if it -ends in a 0) then you will strike problems. Windows for Workgroups -does not seem to support a 0's broadcast and you will probably find -that browsing and name lookups won't work.

    23.11. Multiple interfaces

    21.2.1. audit

    A simple module to audit file access to the syslog +facility. The following operations are logged: +

    share
    connect/disconnect
    directory opens/create/remove
    file open/close/rename/unlink/chmod

    Samba now supports machines with multiple network interfaces. If you -have multiple interfaces then you will need to use the interfaces -option in smb.conf to configure them.

    Chapter 24. Securing Samba

    24.1. Introduction

    21.2.2. extd_audit

    This note was attached to the Samba 2.2.8 release notes as it contained an -important security fix. The information contained here applies to Samba -installations in general.

    This module is identical with the audit module above except +that it sends audit logs to both syslog as well as the smbd log file/s. The +loglevel for this module is set in the smb.conf file. At loglevel = 0, only file +and directory deletions and directory and file creations are logged. At loglevel = 1 +file opens are renames and permission changes are logged , while at loglevel = 2 file +open and close calls are logged also.

    24.2. Using host based protection

    In many installations of Samba the greatest threat comes for outside -your immediate network. By default Samba will accept connections from -any host, which means that if you run an insecure version of Samba on -a host that is directly connected to the Internet you can be -especially vulnerable.

    21.2.3. recycle

    One of the simplest fixes in this case is to use the hosts allow and -hosts deny options in the Samba smb.conf configuration file to only -allow access to your server from a specific range of hosts. An example -might be:

    A recycle-bin like modules. When used any unlink call +will be intercepted and files moved to the recycle +directory instead of beeing deleted.

      hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
-  hosts deny = 0.0.0.0/0
    Supported options: +

    The above will only allow SMB connections from 'localhost' (your own -computer) and from the two private networks 192.168.2 and -192.168.3. All other connections will be refused connections as soon -as the client sends its first packet. The refusal will be marked as a -'not listening on called name' error.

    24.3. Using interface protection

    vfs_recycle_bin:repository

    By default Samba will accept connections on any network interface that -it finds on your system. That means if you have a ISDN line or a PPP -connection to the Internet then Samba will accept connections on those -links. This may not be what you want.

    FIXME

    vfs_recycle_bin:keeptree

    You can change this behaviour using options like the following:

    FIXME

    vfs_recycle_bin:versions

      interfaces = eth* lo
-  bind interfaces only = yes

    FIXME

    vfs_recycle_bin:touch

    FIXME

    vfs_recycle_bin:maxsize

    This tells Samba to only listen for connections on interfaces with a -name starting with 'eth' such as eth0, eth1, plus on the loopback -interface called 'lo'. The name you will need to use depends on what -OS you are using, in the above I used the common name for Ethernet -adapters on Linux.

    FIXME

    vfs_recycle_bin:exclude

    If you use the above and someone tries to make a SMB connection to -your host over a PPP interface called 'ppp0' then they will get a TCP -connection refused reply. In that case no Samba code is run at all as -the operating system has been told not to pass connections from that -interface to any process.

    FIXME

    vfs_recycle_bin:exclude_dir

    FIXME

    vfs_recycle_bin:noversions

    FIXME

    24.4. Using a firewall

    Many people use a firewall to deny access to services that they don't -want exposed outside their network. This can be a very good idea, -although I would recommend using it in conjunction with the above -methods so that you are protected even if your firewall is not active -for some reason.

    21.2.4. netatalk

    If you are setting up a firewall then you need to know what TCP and -UDP ports to allow and block. Samba uses the following:

    A netatalk module, that will ease co-existence of samba and +netatalk file sharing services.

    UDP/137    - used by nmbd
-UDP/138    - used by nmbd
-TCP/139    - used by smbd
-TCP/445    - used by smbd
    Advantages compared to the old netatalk module: +

    it doesn't care about creating of .AppleDouble forks, just keeps ones in sync
    if share in smb.conf doesn't contain .AppleDouble item in hide or veto list, it will be added automatically

    The last one is important as many older firewall setups may not be -aware of it, given that this port was only added to the protocol in -recent years.

    24.5. Using a IPC$ share deny21.3. VFS modules available elsewhere

    If the above methods are not suitable, then you could also place a -more specific deny on the IPC$ share that is used in the recently -discovered security hole. This allows you to offer access to other -shares while denying access to IPC$ from potentially untrustworthy -hosts.

    This section contains a listing of various other VFS modules that +have been posted but don't currently reside in the Samba CVS +tree for one reason ot another (e.g. it is easy for the maintainer +to have his or her own CVS tree).

    To do that you could use:

    No statemets about the stability or functionality any module +should be implied due to its presence here.

    21.3.1. DatabaseFS

      [ipc$]
-     hosts allow = 192.168.115.0/24 127.0.0.1
-     hosts deny = 0.0.0.0/0
    URL: http://www.css.tayloru.edu/~elorimer/databasefs/index.php

    this would tell Samba that IPC$ connections are not allowed from -anywhere but the two listed places (localhost and a local -subnet). Connections to other shares would still be allowed. As the -IPC$ share is the only share that is always accessible anonymously -this provides some level of protection against attackers that do not -know a username/password for your host.

    By Eric Lorimer.

    If you use this method then clients will be given a 'access denied' -reply when they try to access the IPC$ share. That means that those -clients will not be able to browse shares, and may also be unable to -access some other resources.

    I have created a VFS module which implements a fairly complete read-only +filesystem. It presents information from a database as a filesystem in +a modular and generic way to allow different databases to be used +(originally designed for organizing MP3s under directories such as +"Artists," "Song Keywords," etc... I have since applied it to a student +roster database very easily). The directory structure is stored in the +database itself and the module makes no assumptions about the database +structure beyond the table it requires to run.

    This is not recommended unless you cannot use one of the other -methods listed above for some reason.

    Any feedback would be appreciated: comments, suggestions, patches, +etc... If nothing else, hopefully it might prove useful for someone +else who wishes to create a virtual filesystem.

    24.6. Upgrading Samba

    21.3.2. vscan

    Please check regularly on URL: http://www.samba.org/ for updates and -important announcements. Occasionally security releases are made and -it is highly recommended to upgrade Samba when a security vulnerability -is discovered.

    http://www.openantivirus.org/

    samba-vscan is a proof-of-concept module for Samba, which +uses the VFS (virtual file system) features of Samba 2.2.x/3.0 +alphaX. Of couse, Samba has to be compiled with VFS support. +samba-vscan supports various virus scanners and is maintained +by Rainer Link.

    Chapter 25. Unicode/Charsets

    Chapter 22. Hosting a Microsoft Distributed File System tree on Samba

    25.1. What are charsets and unicode?22.1. Instructions

    Computers communicate in numbers. In texts, each number will be -translated to a corresponding letter. The meaning that will be assigned -to a certain number depends on the character set(charset) that is used. -A charset can be seen as a table that is used to translate numbers to -letters. Not all computers use the same charset (there are charsets -with German umlauts, Japanese characters, etc). Usually a charset contains -256 characters, which means that storing a character with it takes -exactly one byte.

    The Distributed File System (or Dfs) provides a means of + separating the logical view of files and directories that users + see from the actual physical locations of these resources on the + network. It allows for higher availability, smoother storage expansion, + load balancing etc. For more information about Dfs, refer to Microsoft documentation.

    There are also charsets that support even more characters, -but those need twice(or even more) as much storage space. These -charsets can contain 256 * 256 = 65536 characters, which -is more then all possible characters one could think of. They are called -multibyte charsets (because they use more then one byte to -store one character).

    This document explains how to host a Dfs tree on a Unix + machine (for Dfs-aware clients to browse) using Samba.

    A standardised multibyte charset is unicode, info available at -To enable SMB-based DFS for Samba, configure it with the + --with-msdfs option. Once built, a + Samba server can be made a Dfs server by setting the global + boolean www.unicode.org. -Big advantage of using a multibyte charset is that you only need one; no -need to make sure two computers use the same charset when they are -communicating.

    host msdfs parameter in the smb.conf + file. You designate a share as a Dfs root using the share + level boolean msdfs root parameter. A Dfs root directory on + Samba hosts Dfs links in the form of symbolic links that point + to other servers. For example, a symbolic link + junction->msdfs:storage1\share1 in + the share directory acts as the Dfs junction. When Dfs-aware + clients attempt to access the junction link, they are redirected + to the storage location (in this case, \\storage1\share1).

    Old windows clients used to use single-byte charsets, named -'codepages' by microsoft. However, there is no support for -negotiating the charset to be used in the smb protocol. Thus, you -have to make sure you are using the same charset when talking to an old client. -Newer clients (Windows NT, 2K, XP) talk unicode over the wire.

    25.2. Samba and charsets

    Dfs trees on Samba work with all Dfs-aware clients ranging + from Windows 95 to 2000.

    As of samba 3.0, samba can (and will) talk unicode over the wire. Internally, -samba knows of three kinds of character sets:

    Here's an example of setting up a Dfs tree on a Samba + server.

    # The smb.conf file:
+[global]
+	netbios name = SAMBA
+	host msdfs   = yes
+
+[dfs]
+	path = /export/dfsroot
+	msdfs root = yes
+

    In the /export/dfsroot directory we set up our dfs links to + other servers on the network.

    root# cd /export/dfsroot

    root# chown root /export/dfsroot

    root# chmod 755 /export/dfsroot

    root# ln -s msdfs:storageA\\shareA linka

    root# ln -s msdfs:serverB\\share,serverC\\share linkb

    You should set up the permissions and ownership of + the directory acting as the Dfs root such that only designated + users can create, delete or modify the msdfs links. Also note + that symlink names should be all lowercase. This limitation exists + to have Samba avoid trying all the case combinations to get at + the link name. Finally set up the symbolic links to point to the + network shares you want, and start Samba.

    Users on Dfs-aware clients can now browse the Dfs tree + on the Samba server at \\samba\dfs. Accessing + links linka or linkb (which appear as directories to the client) + takes users directly to the appropriate shares on the network.

    unix charset

    22.1.1. Notes

    This is the charset used internally by your operating system. - The default is ASCII, which is fine for most - systems. -

    display charset

    • This is the charset samba will use to print messages - on your screen. It should generally be the same as the unix charset. -

    dos charset
    Windows clients need to be rebooted + if a previously mounted non-dfs share is made a dfs + root or vice versa. A better way is to introduce a + new share and make it the dfs root.

  • This is the charset samba uses when communicating with - DOS and Windows 9x clients. It will talk unicode to all newer clients. - The default depends on the charsets you have installed on your system. - Run testparm -v | grep "dos charset" to see - what the default is on your system. -

    • Currently there's a restriction that msdfs + symlink names should all be lowercase.

  • For security purposes, the directory + acting as the root of the Dfs tree should have ownership + and permissions set so that only designated users can + modify the symbolic links in the directory.

    • IV. Appendixes

    Table of Contents
    26. SWAT - The Samba Web Admininistration Tool
    26.1. SWAT Features and Benefits
    26.1.1. The SWAT Home Page
    26.1.2. Global Settings
    26.1.3. The SWAT Wizard
    26.1.4. Share Settings
    26.1.5. Printing Settings
    26.1.6. The Status Page
    26.1.7. The Password Change Page
    27. Migration from NT4 PDC to Samba-3 PDC
    27.1. Planning and Getting Started
    27.1.1. Objectives
    27.1.2. Steps In Migration Process
    27.2. Managing Samba-3 Domain Control
    28. Samba performance issues
    28.1. Comparisons
    28.2. Socket options
    28.3. Read size
    28.4. Max xmit
    28.5. Log level
    28.6. Read raw
    28.7. Write raw
    28.8. Slow Clients
    28.9. Slow Logins
    28.10. Client tuning
    29. Portability
    29.1. HPUX
    29.2. SCO Unix
    29.3. DNIX
    29.4. RedHat Linux Rembrandt-II
    29.5. AIX
    29.5.1. Sequential Read Ahead
    30. Samba and other CIFS clients
    30.1. Macintosh clients?
    30.2. OS2 Client
    30.2.1. How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?
    30.2.2. How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?
    30.2.3. Are there any other issues when OS/2 (any version) - is used as a client?
    30.2.4. How do I get printer driver download working - for OS/2 clients?
    30.3. Windows for Workgroups
    30.3.1. Use latest TCP/IP stack from Microsoft
    30.3.2. Delete .pwl files after password change
    30.3.3. Configure WfW password handling
    30.3.4. Case handling of passwords
    30.3.5. Use TCP/IP as default protocol
    30.4. Windows '95/'98
    30.5. Windows 2000 Service Pack 2
    30.6. Windows NT 3.1
    31. How to compile SAMBA
    31.1. Access Samba source code via CVS
    31.1.1. Introduction
    31.1.2. CVS Access to samba.org
    31.2. Accessing the samba sources via rsync and ftp
    31.3. Building the Binaries
    31.3.1. Compiling samba with Active Directory support
    31.4. Starting the smbd and nmbd

    Chapter 23. Integrating MS Windows networks with Samba

    This section deals with NetBIOS over TCP/IP name to IP address resolution. If you +your MS Windows clients are NOT configured to use NetBIOS over TCP/IP then this +section does not apply to your installation. If your installation involves use of +NetBIOS over TCP/IP then this section may help you to resolve networking problems.

    NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS + over Logical Link Control (LLC). On modern networks it is highly advised + to NOT run NetBEUI at all. Note also that there is NO such thing as + NetBEUI over TCP/IP - the existence of such a protocol is a complete + and utter mis-apprehension.

    Since the introduction of MS Windows 2000 it is possible to run MS Windows networking +without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS +name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over +TCP/IP is disabled on MS Windows 2000 and later clients then only TCP port 445 will be +used and UDP port 137 and TCP port 139 will not.

    When using Windows 2000 or later clients, if NetBIOS over TCP/IP is NOT disabled, then +the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet +Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print traffic).

    When NetBIOS over TCP/IP is disabled the use of DNS is essential. Most installations that +disable NetBIOS over TCP/IP today use MS Active Directory Service (ADS). ADS requires +Dynamic DNS with Service Resource Records (SRV RR) and with Incremental Zone Transfers (IXFR). +Use of DHCP with ADS is recommended as a further means of maintaining central control +over client workstation network configuration.

    23.1. Name Resolution in a pure Unix/Linux world

    The key configuration files covered in this section are:

    • /etc/hosts

    • /etc/resolv.conf

    • /etc/host.conf

    • /etc/nsswitch.conf

    23.1.1. /etc/hosts

    Contains a static list of IP Addresses and names. +eg:

    	127.0.0.1	localhost localhost.localdomain
+	192.168.1.1	bigbox.caldera.com	bigbox	alias4box

    The purpose of /etc/hosts is to provide a +name resolution mechanism so that uses do not need to remember +IP addresses.

    Network packets that are sent over the physical network transport +layer communicate not via IP addresses but rather using the Media +Access Control address, or MAC address. IP Addresses are currently +32 bits in length and are typically presented as four (4) decimal +numbers that are separated by a dot (or period). eg: 168.192.1.1

    MAC Addresses use 48 bits (or 6 bytes) and are typically represented +as two digit hexadecimal numbers separated by colons. eg: +40:8e:0a:12:34:56

    Every network interfrace must have an MAC address. Associated with +a MAC address there may be one or more IP addresses. There is NO +relationship between an IP address and a MAC address, all such assignments +are arbitary or discretionary in nature. At the most basic level all +network communications takes place using MAC addressing. Since MAC +addresses must be globally unique, and generally remains fixed for +any particular interface, the assignment of an IP address makes sense +from a network management perspective. More than one IP address can +be assigned per MAC address. One address must be the primary IP address, +this is the address that will be returned in the ARP reply.

    When a user or a process wants to communicate with another machine +the protocol implementation ensures that the "machine name" or "host +name" is resolved to an IP address in a manner that is controlled +by the TCP/IP configuration control files. The file +/etc/hosts is one such file.

    When the IP address of the destination interface has been +determined a protocol called ARP/RARP is used to identify +the MAC address of the target interface. ARP stands for Address +Resolution Protocol, and is a broadcast oriented method that +uses UDP (User Datagram Protocol) to send a request to all +interfaces on the local network segment using the all 1's MAC +address. Network interfaces are programmed to respond to two +MAC addresses only; their own unique address and the address +ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will +contain the MAC address and the primary IP address for each +interface.

    The /etc/hosts file is foundational to all +Unix/Linux TCP/IP installations and as a minumum will contain +the localhost and local network interface IP addresses and the +primary names by which they are known within the local machine. +This file helps to prime the pump so that a basic level of name +resolution can exist before any other method of name resolution +becomes available.

    23.1.2. /etc/resolv.conf

    This file tells the name resolution libraries:

    • The name of the domain to which the machine + belongs +

    • The name(s) of any domains that should be + automatically searched when trying to resolve unqualified + host names to their IP address +

    • The name or IP address of available Domain + Name Servers that may be asked to perform name to address + translation lookups +

    23.1.3. /etc/host.conf

    /etc/host.conf is the primary means by +which the setting in /etc/resolv.conf may be affected. It is a +critical configuration file. This file controls the order by +which name resolution may procede. The typical structure is:

    	order hosts,bind
+	multi on

    then both addresses should be returned. Please refer to the +man page for host.conf for further details.

    23.1.4. /etc/nsswitch.conf

    This file controls the actual name resolution targets. The +file typically has resolver object specifications as follows:

    	# /etc/nsswitch.conf
+	#
+	# Name Service Switch configuration file.
+	#
+
+	passwd:		compat
+	# Alternative entries for password authentication are:
+	# passwd:	compat files nis ldap winbind
+	shadow:		compat
+	group:		compat
+
+	hosts:		files nis dns
+	# Alternative entries for host name resolution are:
+	# hosts:	files dns nis nis+ hesoid db compat ldap wins
+	networks:	nis files dns
+
+	ethers:		nis files
+	protocols:	nis files
+	rpc:		nis files
+	services:	nis files

    Of course, each of these mechanisms requires that the appropriate +facilities and/or services are correctly configured.

    It should be noted that unless a network request/message must be +sent, TCP/IP networks are silent. All TCP/IP communications assumes a +principal of speaking only when necessary.

    Starting with version 2.2.0 samba has Linux support for extensions to +the name service switch infrastructure so that linux clients will +be able to obtain resolution of MS Windows NetBIOS names to IP +Addresses. To gain this functionality Samba needs to be compiled +with appropriate arguments to the make command (ie: make +nsswitch/libnss_wins.so). The resulting library should +then be installed in the /lib directory and +the "wins" parameter needs to be added to the "hosts:" line in +the /etc/nsswitch.conf file. At this point it +will be possible to ping any MS Windows machine by it's NetBIOS +machine name, so long as that machine is within the workgroup to +which both the samba machine and the MS Windows machine belong.

    23.2. Name resolution as used within MS Windows networking

    MS Windows networking is predicated about the name each machine +is given. This name is known variously (and inconsistently) as +the "computer name", "machine name", "networking name", "netbios name", +"SMB name". All terms mean the same thing with the exception of +"netbios name" which can apply also to the name of the workgroup or the +domain name. The terms "workgroup" and "domain" are really just a +simply name with which the machine is associated. All NetBIOS names +are exactly 16 characters in length. The 16th character is reserved. +It is used to store a one byte value that indicates service level +information for the NetBIOS name that is registered. A NetBIOS machine +name is therefore registered for each service type that is provided by +the client/server.

    The following are typical NetBIOS name/service type registrations:

    	Unique NetBIOS Names:
+		MACHINENAME<00>	= Server Service is running on MACHINENAME
+		MACHINENAME<03> = Generic Machine Name (NetBIOS name)
+		MACHINENAME<20> = LanMan Server service is running on MACHINENAME
+		WORKGROUP<1b> = Domain Master Browser
+
+	Group Names:
+		WORKGROUP<03> = Generic Name registered by all members of WORKGROUP
+		WORKGROUP<1c> = Domain Controllers / Netlogon Servers
+		WORKGROUP<1d> = Local Master Browsers
+		WORKGROUP<1e> = Internet Name Resolvers

    It should be noted that all NetBIOS machines register their own +names as per the above. This is in vast contrast to TCP/IP +installations where traditionally the system administrator will +determine in the /etc/hosts or in the DNS database what names +are associated with each IP address.

    One further point of clarification should be noted, the /etc/hosts +file and the DNS records do not provide the NetBIOS name type information +that MS Windows clients depend on to locate the type of service that may +be needed. An example of this is what happens when an MS Windows client +wants to locate a domain logon server. It find this service and the IP +address of a server that provides it by performing a lookup (via a +NetBIOS broadcast) for enumeration of all machines that have +registered the name type *<1c>. A logon request is then sent to each +IP address that is returned in the enumerated list of IP addresses. Which +ever machine first replies then ends up providing the logon services.

    The name "workgroup" or "domain" really can be confusing since these +have the added significance of indicating what is the security +architecture of the MS Windows network. The term "workgroup" indicates +that the primary nature of the network environment is that of a +peer-to-peer design. In a WORKGROUP all machines are responsible for +their own security, and generally such security is limited to use of +just a password (known as SHARE MODE security). In most situations +with peer-to-peer networking the users who control their own machines +will simply opt to have no security at all. It is possible to have +USER MODE security in a WORKGROUP environment, thus requiring use +of a user name and a matching password.

    MS Windows networking is thus predetermined to use machine names +for all local and remote machine message passing. The protocol used is +called Server Message Block (SMB) and this is implemented using +the NetBIOS protocol (Network Basic Input Output System). NetBIOS can +be encapsulated using LLC (Logical Link Control) protocol - in which case +the resulting protocol is called NetBEUI (Network Basic Extended User +Interface). NetBIOS can also be run over IPX (Internetworking Packet +Exchange) protocol as used by Novell NetWare, and it can be run +over TCP/IP protocols - in which case the resulting protocol is called +NBT or NetBT, the NetBIOS over TCP/IP.

    MS Windows machines use a complex array of name resolution mechanisms. +Since we are primarily concerned with TCP/IP this demonstration is +limited to this area.

    23.2.1. The NetBIOS Name Cache

    All MS Windows machines employ an in memory buffer in which is +stored the NetBIOS names and IP addresses for all external +machines that that machine has communicated with over the +past 10-15 minutes. It is more efficient to obtain an IP address +for a machine from the local cache than it is to go through all the +configured name resolution mechanisms.

    If a machine whose name is in the local name cache has been shut +down before the name had been expired and flushed from the cache, then +an attempt to exchange a message with that machine will be subject +to time-out delays. i.e.: Its name is in the cache, so a name resolution +lookup will succeed, but the machine can not respond. This can be +frustrating for users - but it is a characteristic of the protocol.

    The MS Windows utility that allows examination of the NetBIOS +name cache is called "nbtstat". The Samba equivalent of this +is called "nmblookup".

    23.2.2. The LMHOSTS file

    This file is usually located in MS Windows NT 4.0 or +2000 in C:\WINNT\SYSTEM32\DRIVERS\ETC and contains +the IP Address and the machine name in matched pairs. The +LMHOSTS file performs NetBIOS name +to IP address mapping oriented.

    It typically looks like:

    	# Copyright (c) 1998 Microsoft Corp.
+	#
+	# This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
+	# over TCP/IP) stack for Windows98
+	#
+	# This file contains the mappings of IP addresses to NT computernames
+	# (NetBIOS) names.  Each entry should be kept on an individual line.
+	# The IP address should be placed in the first column followed by the
+	# corresponding computername. The address and the comptername
+	# should be separated by at least one space or tab. The "#" character
+	# is generally used to denote the start of a comment (see the exceptions
+	# below).
+	#
+	# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
+	# files and offers the following extensions:
+	#
+	#      #PRE
+	#      #DOM:<domain>
+	#      #INCLUDE <filename>
+	#      #BEGIN_ALTERNATE
+	#      #END_ALTERNATE
+	#      \0xnn (non-printing character support)
+	#
+	# Following any entry in the file with the characters "#PRE" will cause
+	# the entry to be preloaded into the name cache. By default, entries are
+	# not preloaded, but are parsed only after dynamic name resolution fails.
+	#
+	# Following an entry with the "#DOM:<domain>" tag will associate the
+	# entry with the domain specified by <domain>. This affects how the
+	# browser and logon services behave in TCP/IP environments. To preload
+	# the host name associated with #DOM entry, it is necessary to also add a
+	# #PRE to the line. The <domain> is always preloaded although it will not
+	# be shown when the name cache is viewed.
+	#
+	# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
+	# software to seek the specified <filename> and parse it as if it were
+	# local. <filename> is generally a UNC-based name, allowing a
+	# centralized lmhosts file to be maintained on a server.
+	# It is ALWAYS necessary to provide a mapping for the IP address of the
+	# server prior to the #INCLUDE. This mapping must use the #PRE directive.
+	# In addtion the share "public" in the example below must be in the
+	# LanManServer list of "NullSessionShares" in order for client machines to
+	# be able to read the lmhosts file successfully. This key is under
+	# \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
+	# in the registry. Simply add "public" to the list found there.
+	#
+	# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
+	# statements to be grouped together. Any single successful include
+	# will cause the group to succeed.
+	#
+	# Finally, non-printing characters can be embedded in mappings by
+	# first surrounding the NetBIOS name in quotations, then using the
+	# \0xnn notation to specify a hex value for a non-printing character.
+	#
+	# The following example illustrates all of these extensions:
+	#
+	# 102.54.94.97     rhino         #PRE #DOM:networking  #net group's DC
+	# 102.54.94.102    "appname  \0x14"                    #special app server
+	# 102.54.94.123    popular            #PRE             #source server
+	# 102.54.94.117    localsrv           #PRE             #needed for the include
+	#
+	# #BEGIN_ALTERNATE
+	# #INCLUDE \\localsrv\public\lmhosts
+	# #INCLUDE \\rhino\public\lmhosts
+	# #END_ALTERNATE
+	#
+	# In the above example, the "appname" server contains a special
+	# character in its name, the "popular" and "localsrv" server names are
+	# preloaded, and the "rhino" server name is specified so it can be used
+	# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
+	# system is unavailable.
+	#
+	# Note that the whole file is parsed including comments on each lookup,
+	# so keeping the number of comments to a minimum will improve performance.
+	# Therefore it is not advisable to simply add lmhosts file entries onto the
+	# end of this file.

    23.2.3. HOSTS file

    This file is usually located in MS Windows NT 4.0 or 2000 in +C:\WINNT\SYSTEM32\DRIVERS\ETC and contains +the IP Address and the IP hostname in matched pairs. It can be +used by the name resolution infrastructure in MS Windows, depending +on how the TCP/IP environment is configured. This file is in +every way the equivalent of the Unix/Linux /etc/hosts file.

    23.2.4. DNS Lookup

    This capability is configured in the TCP/IP setup area in the network +configuration facility. If enabled an elaborate name resolution sequence +is followed the precise nature of which isdependant on what the NetBIOS +Node Type parameter is configured to. A Node Type of 0 means use +NetBIOS broadcast (over UDP broadcast) is first used if the name +that is the subject of a name lookup is not found in the NetBIOS name +cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to +Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the +WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast +lookup is used.

    23.2.5. WINS Lookup

    A WINS (Windows Internet Name Server) service is the equivaent of the +rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores +the names and IP addresses that are registered by a Windows client +if the TCP/IP setup has been given at least one WINS Server IP Address.

    To configure Samba to be a WINS server the following parameter needs +to be added to the smb.conf file:

    	wins support = Yes

    To configure Samba to use a WINS server the following parameters are +needed in the smb.conf file:

    	wins support = No
+	wins server = xxx.xxx.xxx.xxx

    where xxx.xxx.xxx.xxx is the IP address +of the WINS server.

    Chapter 24. Improved browsing in samba

    24.1. Overview of browsing

    SMB networking provides a mechanism by which clients can access a list +of machines in a network, a so-called browse list. This list +contains machines that are ready to offer file and/or print services +to other machines within the network. Thus it does not include +machines which aren't currently able to do server tasks. The browse +list is heavily used by all SMB clients. Configuration of SMB +browsing has been problematic for some Samba users, hence this +document.

    MS Windows 2000 and later, as with Samba 3 and later, can be +configured to not use NetBIOS over TCP/IP. When configured this way +it is imperative that name resolution (using DNS/LDAP/ADS) be correctly +configured and operative. Browsing will NOT work if name resolution +from SMB machine names to IP addresses does not function correctly.

    Where NetBIOS over TCP/IP is enabled use of a WINS server is highly +recommended to aid the resolution of NetBIOS (SMB) names to IP addresses. +WINS allows remote segment clients to obtain NetBIOS name_type information +that can NOT be provided by any other means of name resolution.

    24.2. Browsing support in samba

    Samba facilitates browsing. The browsing is supported by nmbd +and is also controlled by options in the smb.conf file. +Samba can act as a local browse master for a workgroup and the ability +for samba to support domain logons and scripts is now available.

    Samba can also act as a domain master browser for a workgroup. This +means that it will collate lists from local browse masters into a +wide area network server list. In order for browse clients to +resolve the names they may find in this list, it is recommended that +both samba and your clients use a WINS server.

    Note that you should NOT set Samba to be the domain master for a +workgroup that has the same name as an NT Domain: on each wide area +network, you must only ever have one domain master browser per workgroup, +regardless of whether it is NT, Samba or any other type of domain master +that is providing this service.

    Nmbd can be configured as a WINS server, but it is not +necessary to specifically use samba as your WINS server. MS Windows +NT4, Server or Advanced Server 2000 or 2003 can be configured as +your WINS server. In a mixed NT/2000/2003 server and samba environment on +a Wide Area Network, it is recommended that you use the Microsoft +WINS server capabilities. In a samba-only environment, it is +recommended that you use one and only one Samba server as your WINS server.

    To get browsing to work you need to run nmbd as usual, but will need +to use the workgroup option in smb.conf +to control what workgroup Samba becomes a part of.

    Samba also has a useful option for a Samba server to offer itself for +browsing on another subnet. It is recommended that this option is only +used for 'unusual' purposes: announcements over the internet, for +example. See remote announce in the +smb.conf man page.

    24.3. Problem resolution

    If something doesn't work then hopefully the log.nmb file will help +you track down the problem. Try a debug level of 2 or 3 for finding +problems. Also note that the current browse list usually gets stored +in text form in a file called browse.dat.

    Note that if it doesn't work for you, then you should still be able to +type the server name as \\SERVER in filemanager then +hit enter and filemanager should display the list of available shares.

    Some people find browsing fails because they don't have the global +guest account set to a valid account. Remember that the +IPC$ connection that lists the shares is done as guest, and thus you must +have a valid guest account.

    MS Windows 2000 and upwards (as with Samba) can be configured to disallow +anonymous (ie: Guest account) access to the IPC$ share. In that case, the +MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the +name of the currently logged in user to query the IPC$ share. MS Windows +9X clients are not able to do this and thus will NOT be able to browse +server resources.

    The other big problem people have is that their broadcast address, +netmask or IP address is wrong (specified with the "interfaces" option +in smb.conf)

    24.4. Browsing across subnets

    Since the release of Samba 1.9.17(alpha1) Samba has been +updated to enable it to support the replication of browse lists +across subnet boundaries. New code and options have been added to +achieve this. This section describes how to set this feature up +in different settings.

    To see browse lists that span TCP/IP subnets (ie. networks separated +by routers that don't pass broadcast traffic) you must set up at least +one WINS server. The WINS server acts as a DNS for NetBIOS names, allowing +NetBIOS name to IP address translation to be done by doing a direct +query of the WINS server. This is done via a directed UDP packet on +port 137 to the WINS server machine. The reason for a WINS server is +that by default, all NetBIOS name to IP address translation is done +by broadcasts from the querying machine. This means that machines +on one subnet will not be able to resolve the names of machines on +another subnet without using a WINS server.

    Remember, for browsing across subnets to work correctly, all machines, +be they Windows 95, Windows NT, or Samba servers must have the IP address +of a WINS server given to them by a DHCP server, or by manual configuration +(for Win95 and WinNT, this is in the TCP/IP Properties, under Network +settings) for Samba this is in the smb.conf file.

    24.4.1. How does cross subnet browsing work ?

    Cross subnet browsing is a complicated dance, containing multiple +moving parts. It has taken Microsoft several years to get the code +that achieves this correct, and Samba lags behind in some areas. +Samba is capable of cross subnet browsing when configured correctly.

    Consider a network set up as follows :

                                       (DMB)
+             N1_A      N1_B        N1_C       N1_D        N1_E
+              |          |           |          |           |
+          -------------------------------------------------------
+            |          subnet 1                       |
+          +---+                                      +---+
+          |R1 | Router 1                  Router 2   |R2 |
+          +---+                                      +---+
+            |                                          |
+            |  subnet 2              subnet 3          |
+  --------------------------       ------------------------------------
+  |     |     |      |               |        |         |           |
+ N2_A  N2_B  N2_C   N2_D           N3_A     N3_B      N3_C        N3_D 
+                    (WINS)

    Consisting of 3 subnets (1, 2, 3) connected by two routers +(R1, R2) - these do not pass broadcasts. Subnet 1 has 5 machines +on it, subnet 2 has 4 machines, subnet 3 has 4 machines. Assume +for the moment that all these machines are configured to be in the +same workgroup (for simplicities sake). Machine N1_C on subnet 1 +is configured as Domain Master Browser (ie. it will collate the +browse lists for the workgroup). Machine N2_D is configured as +WINS server and all the other machines are configured to register +their NetBIOS names with it.

    As all these machines are booted up, elections for master browsers +will take place on each of the three subnets. Assume that machine +N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on +subnet 3 - these machines are known as local master browsers for +their particular subnet. N1_C has an advantage in winning as the +local master browser on subnet 1 as it is set up as Domain Master +Browser.

    On each of the three networks, machines that are configured to +offer sharing services will broadcast that they are offering +these services. The local master browser on each subnet will +receive these broadcasts and keep a record of the fact that +the machine is offering a service. This list of records is +the basis of the browse list. For this case, assume that +all the machines are configured to offer services so all machines +will be on the browse list.

    For each network, the local master browser on that network is +considered 'authoritative' for all the names it receives via +local broadcast. This is because a machine seen by the local +master browser via a local broadcast must be on the same +network as the local master browser and thus is a 'trusted' +and 'verifiable' resource. Machines on other networks that +the local master browsers learn about when collating their +browse lists have not been directly seen - these records are +called 'non-authoritative'.

    At this point the browse lists look as follows (these are +the machines you would see in your network neighborhood if +you looked in it on a particular network right now).

    Subnet           Browse Master   List
+------           -------------   ----
+Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E
+
+Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
+
+Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D

    Note that at this point all the subnets are separate, no +machine is seen across any of the subnets.

    Now examine subnet 2. As soon as N2_B has become the local +master browser it looks for a Domain master browser to synchronize +its browse list with. It does this by querying the WINS server +(N2_D) for the IP address associated with the NetBIOS name +WORKGROUP>1B<. This name was registerd by the Domain master +browser (N1_C) with the WINS server as soon as it was booted.

    Once N2_B knows the address of the Domain master browser it +tells it that is the local master browser for subnet 2 by +sending a MasterAnnouncement packet as a UDP port 138 packet. +It then synchronizes with it by doing a NetServerEnum2 call. This +tells the Domain Master Browser to send it all the server +names it knows about. Once the domain master browser receives +the MasterAnnouncement packet it schedules a synchronization +request to the sender of that packet. After both synchronizations +are done the browse lists look like :

    Subnet           Browse Master   List
+------           -------------   ----
+Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
+
+Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
+
+Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
+
+Servers with a (*) after them are non-authoritative names.

    At this point users looking in their network neighborhood on +subnets 1 or 2 will see all the servers on both, users on +subnet 3 will still only see the servers on their own subnet.

    The same sequence of events that occured for N2_B now occurs +for the local master browser on subnet 3 (N3_D). When it +synchronizes browse lists with the domain master browser (N1_A) +it gets both the server entries on subnet 1, and those on +subnet 2. After N3_D has synchronized with N1_C and vica-versa +the browse lists look like.

    Subnet           Browse Master   List
+------           -------------   ----
+Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*),
+                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
+
+Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
+
+Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
+
+Servers with a (*) after them are non-authoritative names.

    At this point users looking in their network neighborhood on +subnets 1 or 3 will see all the servers on all sunbets, users on +subnet 2 will still only see the servers on subnets 1 and 2, but not 3.

    Finally, the local master browser for subnet 2 (N2_B) will sync again +with the domain master browser (N1_C) and will recieve the missing +server entries. Finally - and as a steady state (if no machines +are removed or shut off) the browse lists will look like :

    Subnet           Browse Master   List
+------           -------------   ----
+Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*),
+                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
+
+Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
+                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
+
+Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
+	
+Servers with a (*) after them are non-authoritative names.

    Synchronizations between the domain master browser and local +master browsers will continue to occur, but this should be a +steady state situation.

    If either router R1 or R2 fails the following will occur:

    1. Names of computers on each side of the inaccessible network fragments + will be maintained for as long as 36 minutes, in the network neighbourhood + lists. +

    2. Attempts to connect to these inaccessible computers will fail, but the + names will not be removed from the network neighbourhood lists. +

    3. If one of the fragments is cut off from the WINS server, it will only + be able to access servers on its local subnet, by using subnet-isolated + broadcast NetBIOS name resolution. The effects are similar to that of + losing access to a DNS server. +

    24.5. Setting up a WINS server

    Either a Samba machine or a Windows NT Server machine may be set up +as a WINS server. To set a Samba machine to be a WINS server you must +add the following option to the smb.conf file on the selected machine : +in the [globals] section add the line

    wins support = yes

    Versions of Samba prior to 1.9.17 had this parameter default to +yes. If you have any older versions of Samba on your network it is +strongly suggested you upgrade to a recent version, or at the very +least set the parameter to 'no' on all these machines.

    Machines with wins support = yes will keep a list of +all NetBIOS names registered with them, acting as a DNS for NetBIOS names.

    You should set up only ONE wins server. Do NOT set the +wins support = yes option on more than one Samba +server.

    To set up a Windows NT Server as a WINS server you need to set up +the WINS service - see your NT documentation for details. Note that +Windows NT WINS Servers can replicate to each other, allowing more +than one to be set up in a complex subnet environment. As Microsoft +refuse to document these replication protocols Samba cannot currently +participate in these replications. It is possible in the future that +a Samba->Samba WINS replication protocol may be defined, in which +case more than one Samba machine could be set up as a WINS server +but currently only one Samba server should have the +wins support = yes parameter set.

    After the WINS server has been configured you must ensure that all +machines participating on the network are configured with the address +of this WINS server. If your WINS server is a Samba machine, fill in +the Samba machine IP address in the "Primary WINS Server" field of +the "Control Panel->Network->Protocols->TCP->WINS Server" dialogs +in Windows 95 or Windows NT. To tell a Samba server the IP address +of the WINS server add the following line to the [global] section of +all smb.conf files :

    wins server = >name or IP address<

    where >name or IP address< is either the DNS name of the WINS server +machine or its IP address.

    Note that this line MUST NOT BE SET in the smb.conf file of the Samba +server acting as the WINS server itself. If you set both the +wins support = yes option and the +wins server = <name> option then +nmbd will fail to start.

    There are two possible scenarios for setting up cross subnet browsing. +The first details setting up cross subnet browsing on a network containing +Windows 95, Samba and Windows NT machines that are not configured as +part of a Windows NT Domain. The second details setting up cross subnet +browsing on networks that contain NT Domains.

    24.6. Setting up Browsing in a WORKGROUP

    To set up cross subnet browsing on a network containing machines +in up to be in a WORKGROUP, not an NT Domain you need to set up one +Samba server to be the Domain Master Browser (note that this is *NOT* +the same as a Primary Domain Controller, although in an NT Domain the +same machine plays both roles). The role of a Domain master browser is +to collate the browse lists from local master browsers on all the +subnets that have a machine participating in the workgroup. Without +one machine configured as a domain master browser each subnet would +be an isolated workgroup, unable to see any machines on any other +subnet. It is the presense of a domain master browser that makes +cross subnet browsing possible for a workgroup.

    In an WORKGROUP environment the domain master browser must be a +Samba server, and there must only be one domain master browser per +workgroup name. To set up a Samba server as a domain master browser, +set the following option in the [global] section of the smb.conf file :

    domain master = yes

    The domain master browser should also preferrably be the local master +browser for its own subnet. In order to achieve this set the following +options in the [global] section of the smb.conf file :

    domain master = yes
+local master = yes
+preferred master = yes
+os level = 65

    The domain master browser may be the same machine as the WINS +server, if you require.

    Next, you should ensure that each of the subnets contains a +machine that can act as a local master browser for the +workgroup. Any MS Windows NT/2K/XP/2003 machine should be +able to do this, as will Windows 9x machines (although these +tend to get rebooted more often, so it's not such a good idea +to use these). To make a Samba server a local master browser +set the following options in the [global] section of the +smb.conf file :

    domain master = no
+local master = yes
+preferred master = yes
+os level = 65

    Do not do this for more than one Samba server on each subnet, +or they will war with each other over which is to be the local +master browser.

    The local master parameter allows Samba to act as a +local master browser. The preferred master causes nmbd +to force a browser election on startup and the os level +parameter sets Samba high enough so that it should win any browser elections.

    If you have an NT machine on the subnet that you wish to +be the local master browser then you can disable Samba from +becoming a local master browser by setting the following +options in the [global] section of the +smb.conf file :

    domain master = no
+local master = no
+preferred master = no
+os level = 0

    24.7. Setting up Browsing in a DOMAIN

    If you are adding Samba servers to a Windows NT Domain then +you must not set up a Samba server as a domain master browser. +By default, a Windows NT Primary Domain Controller for a Domain +name is also the Domain master browser for that name, and many +things will break if a Samba server registers the Domain master +browser NetBIOS name (DOMAIN<1B>) +with WINS instead of the PDC.

    For subnets other than the one containing the Windows NT PDC +you may set up Samba servers as local master browsers as +described. To make a Samba server a local master browser set +the following options in the [global] section +of the smb.conf file :

    domain master = no
+local master = yes
+preferred master = yes
+os level = 65

    If you wish to have a Samba server fight the election with machines +on the same subnet you may set the os level parameter +to lower levels. By doing this you can tune the order of machines that +will become local master browsers if they are running. For +more details on this see the section Forcing samba to be the master browser +below.

    If you have Windows NT machines that are members of the domain +on all subnets, and you are sure they will always be running then +you can disable Samba from taking part in browser elections and +ever becoming a local master browser by setting following options +in the [global] section of the smb.conf +file :

    domain master = no + local master = no + preferred master = no + os level = 0

    24.8. Forcing samba to be the master

    Who becomes the master browser is determined by an election +process using broadcasts. Each election packet contains a number of parameters +which determine what precedence (bias) a host should have in the +election. By default Samba uses a very low precedence and thus loses +elections to just about anyone else.

    If you want Samba to win elections then just set the os level global +option in smb.conf to a higher number. It defaults to 0. Using 34 +would make it win all elections over every other system (except other +samba systems!)

    A os level of 2 would make it beat WfWg and Win95, but not MS Windows +NT/2K Server. A MS Windows NT/2K Server domain controller uses level 32.

    The maximum os level is 255

    If you want samba to force an election on startup, then set the +preferred master global option in smb.conf to "yes". Samba will +then have a slight advantage over other potential master browsers +that are not preferred master browsers. Use this parameter with +care, as if you have two hosts (whether they are windows 95 or NT or +samba) on the same local subnet both set with preferred master to +"yes", then periodically and continually they will force an election +in order to become the local master browser.

    If you want samba to be a domain master browser, then it is +recommended that you also set preferred master to "yes", because +samba will not become a domain master browser for the whole of your +LAN or WAN if it is not also a local master browser on its own +broadcast isolated subnet.

    It is possible to configure two samba servers to attempt to become +the domain master browser for a domain. The first server that comes +up will be the domain master browser. All other samba servers will +attempt to become the domain master browser every 5 minutes. They +will find that another samba server is already the domain master +browser and will fail. This provides automatic redundancy, should +the current domain master browser fail.

    24.9. Making samba the domain master

    The domain master is responsible for collating the browse lists of +multiple subnets so that browsing can occur between subnets. You can +make samba act as the domain master by setting domain master = yes +in smb.conf. By default it will not be a domain master.

    Note that you should NOT set Samba to be the domain master for a +workgroup that has the same name as an NT Domain.

    When samba is the domain master and the master browser it will listen +for master announcements (made roughly every twelve minutes) from local +master browsers on other subnets and then contact them to synchronise +browse lists.

    If you want samba to be the domain master then I suggest you also set +the os level high enough to make sure it wins elections, and set +preferred master to "yes", to get samba to force an election on +startup.

    Note that all your servers (including samba) and clients should be +using a WINS server to resolve NetBIOS names. If your clients are only +using broadcasting to resolve NetBIOS names, then two things will occur:

    1. your local master browsers will be unable to find a domain master + browser, as it will only be looking on the local subnet. +

    2. if a client happens to get hold of a domain-wide browse list, and + a user attempts to access a host in that list, it will be unable to + resolve the NetBIOS name of that host. +

    If, however, both samba and your clients are using a WINS server, then:

    1. your local master browsers will contact the WINS server and, as long as + samba has registered that it is a domain master browser with the WINS + server, your local master browser will receive samba's ip address + as its domain master browser. +

    2. when a client receives a domain-wide browse list, and a user attempts + to access a host in that list, it will contact the WINS server to + resolve the NetBIOS name of that host. as long as that host has + registered its NetBIOS name with the same WINS server, the user will + be able to see that host. +

    24.10. Note about broadcast addresses

    If your network uses a "0" based broadcast address (for example if it +ends in a 0) then you will strike problems. Windows for Workgroups +does not seem to support a 0's broadcast and you will probably find +that browsing and name lookups won't work.

    24.11. Multiple interfaces

    Samba now supports machines with multiple network interfaces. If you +have multiple interfaces then you will need to use the interfaces +option in smb.conf to configure them.

    Chapter 25. Securing Samba

    25.1. Introduction

    This note was attached to the Samba 2.2.8 release notes as it contained an +important security fix. The information contained here applies to Samba +installations in general.

    25.2. Using host based protection

    In many installations of Samba the greatest threat comes for outside +your immediate network. By default Samba will accept connections from +any host, which means that if you run an insecure version of Samba on +a host that is directly connected to the Internet you can be +especially vulnerable.

    One of the simplest fixes in this case is to use the hosts allow and +hosts deny options in the Samba smb.conf configuration file to only +allow access to your server from a specific range of hosts. An example +might be:

      hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
+  hosts deny = 0.0.0.0/0

    The above will only allow SMB connections from 'localhost' (your own +computer) and from the two private networks 192.168.2 and +192.168.3. All other connections will be refused connections as soon +as the client sends its first packet. The refusal will be marked as a +'not listening on called name' error.

    25.3. Using interface protection

    By default Samba will accept connections on any network interface that +it finds on your system. That means if you have a ISDN line or a PPP +connection to the Internet then Samba will accept connections on those +links. This may not be what you want.

    You can change this behaviour using options like the following:

      interfaces = eth* lo
+  bind interfaces only = yes

    This tells Samba to only listen for connections on interfaces with a +name starting with 'eth' such as eth0, eth1, plus on the loopback +interface called 'lo'. The name you will need to use depends on what +OS you are using, in the above I used the common name for Ethernet +adapters on Linux.

    If you use the above and someone tries to make a SMB connection to +your host over a PPP interface called 'ppp0' then they will get a TCP +connection refused reply. In that case no Samba code is run at all as +the operating system has been told not to pass connections from that +interface to any process.

    25.4. Using a firewall

    Many people use a firewall to deny access to services that they don't +want exposed outside their network. This can be a very good idea, +although I would recommend using it in conjunction with the above +methods so that you are protected even if your firewall is not active +for some reason.

    If you are setting up a firewall then you need to know what TCP and +UDP ports to allow and block. Samba uses the following:

    UDP/137    - used by nmbd
+UDP/138    - used by nmbd
+TCP/139    - used by smbd
+TCP/445    - used by smbd

    The last one is important as many older firewall setups may not be +aware of it, given that this port was only added to the protocol in +recent years.

    25.5. Using a IPC$ share deny

    If the above methods are not suitable, then you could also place a +more specific deny on the IPC$ share that is used in the recently +discovered security hole. This allows you to offer access to other +shares while denying access to IPC$ from potentially untrustworthy +hosts.

    To do that you could use:

      [ipc$]
+     hosts allow = 192.168.115.0/24 127.0.0.1
+     hosts deny = 0.0.0.0/0

    this would tell Samba that IPC$ connections are not allowed from +anywhere but the two listed places (localhost and a local +subnet). Connections to other shares would still be allowed. As the +IPC$ share is the only share that is always accessible anonymously +this provides some level of protection against attackers that do not +know a username/password for your host.

    If you use this method then clients will be given a 'access denied' +reply when they try to access the IPC$ share. That means that those +clients will not be able to browse shares, and may also be unable to +access some other resources.

    This is not recommended unless you cannot use one of the other +methods listed above for some reason.

    25.6. Upgrading Samba

    Please check regularly on http://www.samba.org/ for updates and +important announcements. Occasionally security releases are made and +it is highly recommended to upgrade Samba when a security vulnerability +is discovered.

    Chapter 26. Unicode/Charsets

    26.1. What are charsets and unicode?

    Computers communicate in numbers. In texts, each number will be +translated to a corresponding letter. The meaning that will be assigned +to a certain number depends on the character set(charset) that is used. +A charset can be seen as a table that is used to translate numbers to +letters. Not all computers use the same charset (there are charsets +with German umlauts, Japanese characters, etc). Usually a charset contains +256 characters, which means that storing a character with it takes +exactly one byte.

    There are also charsets that support even more characters, +but those need twice(or even more) as much storage space. These +charsets can contain 256 * 256 = 65536 characters, which +is more then all possible characters one could think of. They are called +multibyte charsets (because they use more then one byte to +store one character).

    A standardised multibyte charset is unicode, info available at +www.unicode.org. +Big advantage of using a multibyte charset is that you only need one; no +need to make sure two computers use the same charset when they are +communicating.

    Old windows clients used to use single-byte charsets, named +'codepages' by microsoft. However, there is no support for +negotiating the charset to be used in the smb protocol. Thus, you +have to make sure you are using the same charset when talking to an old client. +Newer clients (Windows NT, 2K, XP) talk unicode over the wire.

    26.2. Samba and charsets

    As of samba 3.0, samba can (and will) talk unicode over the wire. Internally, +samba knows of three kinds of character sets:

    31.4.1. Starting from inetd.conf
    31.4.2. Alternative: starting it as a daemon
    32. Reporting Bugs
    unix charset
    32.1. Introduction
    32.2. General info
    32.3. Debug levels
    32.4. Internal errors
    32.5. Attaching to a running process
    32.6. Patches

    This is the charset used internally by your operating system. + The default is ASCII, which is fine for most + systems. +

    33. The samba checklist
    display charset
    33.1. Introduction
    33.2. Assumptions
    33.3. The tests

    This is the charset samba will use to print messages + on your screen. It should generally be the same as the unix charset. +

    33.4. Still having troubles?
    dos charset

    This is the charset samba uses when communicating with + DOS and Windows 9x clients. It will talk unicode to all newer clients. + The default depends on the charsets you have installed on your system. + Run testparm -v | grep "dos charset" to see + what the default is on your system. +

    26.3. Conversion from old names

    Because previous samba versions did not do any charset conversion, +characters in filenames are usually not correct in the unix charset but only +for the local charset used by the DOS/Windows clients.

    The following script from Steve Langasek converts all +filenames from CP850 to the iso8859-15 charset.

    #find /path/to/share -type f -exec bash -c 'CP="{}"; ISO=`echo -n "$CP" | iconv -f cp850 \ + -t iso8859-15`; if [ "$CP" != "$ISO" ]; then mv "$CP" "$ISO"; fi' \;

    IV. Appendixes

    Chapter 26. SWAT - The Samba Web Admininistration Tool

    Chapter 27. How to compile SAMBA

    You can obtain the samba source from the samba website. To obtain a development version, +you can download samba from CVS or using rsync.

    27.1. Access Samba source code via CVS

    27.1.1. Introduction

    Samba is developed in an open environment. Developers use CVS +(Concurrent Versioning System) to "checkin" (also known as +"commit") new source code. Samba's various CVS branches can +be accessed via anonymous CVS using the instructions +detailed in this chapter.

    This chapter is a modified version of the instructions found at +http://samba.org/samba/cvs.html

    27.1.2. 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. There are two main ways of +accessing the CVS server on this host.

    27.1.2.1. 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

    27.1.2.2. 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 up to date 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). 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.

    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. +

    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 (i.e. the HEAD tagged cvs branch). This + currently corresponds to the 3.0 development tree. +

      CVS branches other HEAD can be obtained by using the -r + 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 userinput. +

      cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba +

    4. Whenever you want to merge in the latest code changes use + the following command from within the samba directory: +

      cvs update -d -P +

    27.2. Accessing the samba sources via rsync and ftp

    pserver.samba.org also exports unpacked copies of most parts of the CVS tree at ftp://pserver.samba.org/pub/unpacked and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp. + See the rsync homepage for more info on rsync. +

    The disadvantage of the unpacked trees + is that they do not support automatic + merging of local changes like CVS does. + rsync access is most convenient for an + initial install. +

    27.3. Verifying Samba's PGP signature

    In these days of insecurity, it's strongly recommended that you verify the PGP signature for any +source file before installing it. According to Jerry Carter of the Samba Team, only about 22% of +all Samba downloads have had a corresponding PGP signature download (a very low percentage, which +should be considered a bad thing). Even if you're not downloading from a mirror site, verifying PGP +signatures should be a standard reflex.

    With that said, go ahead and download the following files:

         $ wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc
+     $ wget http://us1.samba.org/samba/ftp/samba-pubkey.asc

    This is a rough guide to SWAT.

    The first file is the PGP signature for the Samba source file; the other is the Samba public +PGP key itself. Import the public PGP key with:

         $ gpg --import samba-pubkey.asc

    And verify the Samba source code integrity with:

         $ gzip -d samba-2.2.8a.tar.gz
+     $ gpg --verify samba-2.2.8a.tar.asc

    If you receive a message like, "Good signature from Samba Distribution Verification Key..." +then all is well. The warnings about trust relationships can be ignored. An example of what +you would not want to see would be:

         gpg: BAD signature from "Samba Distribution Verification Key"

    26.1. SWAT Features and Benefits27.4. Building the Binaries

    You must use at least the following ...

    26.1.1. The SWAT Home Page

    To do this, first run the program ./configure + in the source directory. This should automatically + configure Samba for your operating system. If you have unusual + needs then you may wish to run

    Blah blah here.

    26.1.2. Global Settings

    root# ./configure --help +

    Document steps right here!

    26.1.3. The SWAT Wizard

    first to see what special options you can enable. + Then executing

    Lots of blah blah here.

    26.1.4. Share Settings

    root# make

    Document steps right here!

    26.1.5. Printing Settings

    will create the binaries. Once it's successfully + compiled you can use

    Document steps right here!

    26.1.6. The Status Page

    root# make install

    Document steps right here!

    to install the binaries and manual pages. You can + separately install the binaries and/or man pages using

    root# make installbin +

    and

    root# make installman +

    Note that if you are upgrading for a previous version + of Samba you might like to know that the old versions of + the binaries will be renamed with a ".old" extension. You + can go back to the previous version with

    root# make revert +

    if you find this version a disaster!

    26.1.7. The Password Change Page27.4.1. Compiling samba with Active Directory support

    Document steps right here!

    Chapter 27. Migration from NT4 PDC to Samba-3 PDC

    In order to compile samba with ADS support, you need to have installed + on your system: +

    the MIT kerberos development libraries (either install from the sources or use a package). The heimdal libraries will not work.
    the OpenLDAP development libraries.

    This is a rough guide to assist those wishing to migrate from NT4 domain control to -Samba-3 based domain control.

    27.1. Planning and Getting Started

    You must use at least the following ...

    If your kerberos libraries are in a non-standard location then + remember to add the configure option --with-krb5=DIR.

    After you run configure make sure that include/config.h it generates contains lines like this:

    #define HAVE_KRB5 1
+#define HAVE_LDAP 1
+

    If it doesn't then configure did not find your krb5 libraries or + your ldap libraries. Look in config.log to figure out why and fix + it.

    27.1.1. Objectives

    27.4.1.1. Installing the required packages for Debian

    On Debian you need to install the following packages:

    libkrb5-dev
    krb5-user

    Blah blah objectives here.

    +

    27.1.2. Steps In Migration Process

    27.4.1.2. Installing the required packages for RedHat

    Document steps right here!

    On RedHat this means you should have at least:

    krb5-workstation (for kinit)
    krb5-libs (for linking with)
    krb5-devel (because you are compiling from source)

    +

    in addition to the standard development environment.

    Note that these are not standard on a RedHat install, and you may need + to get them off CD2.

    27.2. Managing Samba-3 Domain Control27.5. Starting the smbd and nmbd

    Lots of blah blah here.

    Chapter 28. Samba performance issues

    You must choose to start smbd and nmbd either + as daemons or from inetdDon't try + to do both! Either you can put them in inetd.conf and have them started on demand + by inetd, or you can start them as + daemons either from the command line or in /etc/rc.local. See the man pages for details + on the command line options. Take particular care to read + the bit about what user you need to be in order to start + Samba. In many cases you must be root.

    The main advantage of starting smbd + and nmbd using the recommended daemon method + is that they will respond slightly more quickly to an initial connection + request.

    28.1. Comparisons

    27.5.1. Starting from inetd.conf

    The Samba server uses TCP to talk to the client. Thus if you are -trying to see if it performs well you should really compare it to -programs that use the same protocol. The most readily available -programs for file transfer that use TCP are ftp or another TCP based -SMB server.

    NOTE; The following will be different if + you use NIS, NIS+ or LDAP to distribute services maps.

    If you want to test against something like a NT or WfWg server then -you will have to disable all but TCP on either the client or -server. Otherwise you may well be using a totally different protocol -(such as Netbeui) and comparisons may not be valid.

    Look at your /etc/services. + What is defined at port 139/tcp. If nothing is defined + then add a line like this:

    Generally you should find that Samba performs similarly to ftp at raw -transfer speed. It should perform quite a bit faster than NFS, -although this very much depends on your system.

    netbios-ssn 139/tcp

    Several people have done comparisons between Samba and Novell, NFS or -WinNT. In some cases Samba performed the best, in others the worst. I -suspect the biggest factor is not Samba vs some other system but the -hardware and drivers used on the various systems. Given similar -hardware Samba should certainly be competitive in speed with other -systems.

    28.2. Socket options

    similarly for 137/udp you should have an entry like:

    There are a number of socket options that can greatly affect the -performance of a TCP based server like Samba.

    netbios-ns 137/udp

    The socket options that Samba uses are settable both on the command -line with the -O option, or in the smb.conf file.

    Next edit your /etc/inetd.conf + and add two lines something like this:

    The "socket options" section of the smb.conf manual page describes how -to set these and gives recommendations.

    		netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd 
+		netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd 
+

    Getting the socket options right can make a big difference to your -performance, but getting them wrong can degrade it by just as -much. The correct settings are very dependent on your local network.

    The exact syntax of /etc/inetd.conf + varies between unixes. Look at the other entries in inetd.conf + for a guide.

    The socket option TCP_NODELAY is the one that seems to make the -biggest single difference for most networks. Many people report that -adding "socket options = TCP_NODELAY" doubles the read performance of -a Samba drive. The best explanation I have seen for this is that the -Microsoft TCP/IP stack is slow in sending tcp ACKs.

    Some unixes already have entries like netbios_ns + (note the underscore) in /etc/services. + You must either edit /etc/services or + /etc/inetd.conf to make them consistent.

    28.3. Read size

    The option "read size" affects the overlap of disk reads/writes with -network reads/writes. If the amount of data being transferred in -several of the SMB commands (currently SMBwrite, SMBwriteX and -SMBreadbraw) is larger than this value then the server begins writing -the data before it has received the whole packet from the network, or -in the case of SMBreadbraw, it begins writing to the network before -all the data has been read from disk.

    This overlapping works best when the speeds of disk and network access -are similar, having very little effect when the speed of one is much -greater than the other.

    The default value is 16384, but very little experimentation has been -done yet to determine the optimal value, and it is likely that the best -value will vary greatly between systems anyway. A value over 65536 is -pointless and will cause you to allocate memory unnecessarily.

    On many systems you may need to use the + interfaces option in smb.conf to specify the IP address + and netmask of your interfaces. Run ifconfig + as root if you don't know what the broadcast is for your + net. nmbd tries to determine it at run + time, but fails on some unixes. +

    28.4. Max xmit

    At startup the client and server negotiate a "maximum transmit" size, -which limits the size of nearly all SMB commands. You can set the -maximum size that Samba will negotiate using the "max xmit = " option -in smb.conf. Note that this is the maximum size of SMB request that -Samba will accept, but not the maximum size that the *client* will accept. -The client maximum receive size is sent to Samba by the client and Samba -honours this limit.

    It defaults to 65536 bytes (the maximum), but it is possible that some -clients may perform better with a smaller transmit unit. Trying values -of less than 2048 is likely to cause severe problems.

    In most cases the default is the best option.

    Many unixes only accept around 5 + parameters on the command line in inetd.conf. + This means you shouldn't use spaces between the options and + arguments, or you should use a script, and start the script + from inetd.

    28.5. Log level

    If you set the log level (also known as "debug level") higher than 2 -then you may suffer a large drop in performance. This is because the -server flushes the log file after each operation, which can be very -expensive.

    Restart inetd, perhaps just send + it a HUP. If you have installed an earlier version of nmbd then you may need to kill nmbd as well.

    28.6. Read raw

    27.5.2. Alternative: starting it as a daemon

    The "read raw" operation is designed to be an optimised, low-latency -file read operation. A server may choose to not support it, -however. and Samba makes support for "read raw" optional, with it -being enabled by default.

    To start the server as a daemon you should create + a script something like this one, perhaps calling + it startsmb.

    In some cases clients don't handle "read raw" very well and actually -get lower performance using it than they get using the conventional -read operations. 

    		#!/bin/sh
+		/usr/local/samba/bin/smbd -D 
+		/usr/local/samba/bin/nmbd -D 
+

    So you might like to try "read raw = no" and see what happens on your -network. It might lower, raise or not affect your performance. Only -testing can really tell.

    28.7. Write raw

    then make it executable with chmod + +x startsmb

    The "write raw" operation is designed to be an optimised, low-latency -file write operation. A server may choose to not support it, -however. and Samba makes support for "write raw" optional, with it -being enabled by default.

    You can then run startsmb by + hand or execute it from /etc/rc.local +

    Some machines may find "write raw" slower than normal write, in which -case you may wish to change this option.

    To kill it send a kill signal to the processes + nmbd and smbd.

    28.8. Slow Clients

    One person has reported that setting the protocol to COREPLUS rather -than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).

    I suspect that his PC's (386sx16 based) were asking for more data than -they could chew. I suspect a similar speed could be had by setting -"read raw = no" and "max xmit = 2048", instead of changing the -protocol. Lowering the "read size" might also help.

    If you use the SVR4 style init system then + you may like to look at the examples/svr4-startup + script to make Samba fit into that system.

    28.9. Slow Logins

    Chapter 28. Migration from NT4 PDC to Samba-3 PDC

    Slow logins are almost always due to the password checking time. Using -the lowest practical "password level" will improve things a lot. You -could also enable the "UFC crypt" option in the Makefile.

    This is a rough guide to assist those wishing to migrate from NT4 domain control to +Samba-3 based domain control.

    28.10. Client tuning28.1. Planning and Getting Started

    Often a speed problem can be traced to the client. The client (for -example Windows for Workgroups) can often be tuned for better TCP -performance.

    See your client docs for details. In particular, I have heard rumours -that the WfWg options TCPWINDOWSIZE and TCPSEGMENTSIZE can have a -large impact on performance.

    Also note that some people have found that setting DefaultRcvWindow in -the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a -big improvement. I don't know why.

    My own experience wth DefaultRcvWindow is that I get much better -performance with a large value (16384 or larger). Other people have -reported that anything over 3072 slows things down enourmously. One -person even reported a speed drop of a factor of 30 when he went from -3072 to 8192. I don't know why.

    It probably depends a lot on your hardware, and the type of unix box -you have at the other end of the link.

    In the IT world there is often a saying that all problems are encountered because of +poor planning. The corrollary to this saying is that not all problems can be anticpated +and planned for. Then again, good planning will anticpate most show stopper type situations.

    Paul Cochrane has done some testing on client side tuning and come -to the following conclusions:

    Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control +environment would do well to develop a detailed migration plan. So here are a few pointers to +help migration get under way.

    28.1.1. Objectives

    Install the W2setup.exe file from www.microsoft.com. This is an -update for the winsock stack and utilities which improve performance.

    The key objective for most organisations will be to make the migration from MS Windows NT4 +to Samba-3 domain control as painless as possible. One of the challenges you may experience +in your migration process may well be one of convincing management that the new environment +should remain in place. Many who have introduced open source technologies have experienced +pressure to return to a Microsoft based platform solution at the first sign of trouble.

    Configure the win95 TCPIP registry settings to give better -perfomance. I use a program called MTUSPEED.exe which I got off the -net. There are various other utilities of this type freely available. -The setting which give the best performance for me are:

    It is strongly advised that before attempting a migration to a Samba-3 controlled network +that every possible effort be made to gain all-round commitment to the change. Firstly, you +should know precisely why the change is important for the organisation. +Possible motivations to make a change include:

    1. MaxMTU Remove

      • RWIN Remove

        Improve network manageability

      • MTUAutoDiscover Disable

        Obtain better user level functionality

      • MTUBlackHoleDetect Disable

        Reduce network operating costs

      • Time To Live Enabled

        Reduce exposure caused by Microsoft withdrawal of NT4 support

      • Time To Live - HOPS 32

        Avoid MS License 6 implications

      • NDI Cache Size 0

        Reduce organisation's dependency on Microsoft

    I tried virtually all of the items mentioned in the document and -the only one which made a difference to me was the socket options. It -turned out I was better off without any!!!!!

    It is vital that oit be well recognised that Samba-3 is NOT MS Windows NT4. Samba-3 offers +an alternative solution that is both different from MS Windows NT4 and that offers some +advantages compared with it. It should also be recognised that Samba-3 lacks many of the +features that Microsoft has promoted as core values in migration from MS Windows NT4 to +MS Windows 2000 and beyond (with or without Active Directory services).

    In terms of overall speed of transfer, between various win95 clients -and a DX2-66 20MB server with a crappy NE2000 compatible and old IDE -drive (Kernel 2.0.30). The transfer rate was reasonable for 10 baseT.

    What are the features the Samba-3 can NOT provide?

    The figures are:          Put              Get 
-P166 client 3Com card:    420-440kB/s      500-520kB/s
-P100 client 3Com card:    390-410kB/s      490-510kB/s
-DX4-75 client NE2000:     370-380kB/s      330-350kB/s

    Active Directory Server
    Group Policy Objects (in Active Direcrtory)
    Machine Policy objects
    Logon Scripts in Active Directorty
    Software Application and Access Controls in Active Directory

    I based these test on transfer two files a 4.5MB text file and a 15MB -textfile. The results arn't bad considering the hardware Samba is -running on. It's a crap machine!!!!

    The updates mentioned in 1 and 2 brought up the transfer rates from -just over 100kB/s in some clients.

    A new client is a P333 connected via a 100MB/s card and hub. The -transfer rates from this were good: 450-500kB/s on put and 600+kB/s -on get.

    28.1.2. Steps In Migration Process

    Looking at standard FTP throughput, Samba is a bit slower (100kB/s -upwards). I suppose there is more going on in the samba protocol, but -if it could get up to the rate of FTP the perfomance would be quite -staggering.

    This is not a definitive ste-by-step process yet - just a place holder so the info +is not lost. + +1. You will have an NT4 PDC that has the users, groups, policies and profiles to be migrated + +2. Samba-3 set up as a DC with netlogon share, profile share, etc. + +3. Process: + a. Create a BDC account for the samba server using NT Server Manager + - Samba must NOT be running + + b. rpcclient NT4PDC -U Administrator%passwd + lsaquery + + Note the SID returned by step b. + + c. net getsid -S NT4PDC -w DOMNAME -U Administrator%passwd + + Note the SID in step c. + + d. net getlocalsid + + Note the SID, now check that all three SIDS reported are the same! + + e. net rpc join -S NT4PDC -w DOMNAME -U Administrator%passwd + + f. net rpc vampire -S NT4PDC -U administrator%passwd + + g. pdbedit -l + + Note - did the users migrate? + + h. initGrps.sh DOMNAME + + i. smbgroupedit -v + + Now check that all groups are recognised + + j. net rpc campire -S NT4PDC -U administrator%passwd + + k. pdbedit -lv + + Note - check that all group membership has been migrated. + + +Now it is time to migrate all the profiles, then migrate all policy files. + +Moe later.

    29.1. HPUX

    29.2. SCO Unix

    29.3. DNIX

    29.4. RedHat Linux Rembrandt-II

    29.5. AIX

    29.5.1. Sequential Read Ahead

    29.6. Solaris

    Some people have been experiencing problems with F_SETLKW64/fcntl +when running samba on solaris. The built in file locking mechanism was +not scalable. Performance would degrade to the point where processes would +get into loops of trying to lock a file. It woul try a lock, then fail, +then try again. The lock attempt was failing before the grant was +occurring. So the visible manifestation of this would be a handful of +processes stealing all of the CPU, and when they were trussed they would +be stuck if F_SETLKW64 loops.

    Sun released patches for Solaris 2.6, 8, and 9. The patch for Solaris 7 +has not been released yet.

    The patch revision for 2.6 is 105181-34 +for 8 is 108528-19 +and for 9 is 112233-04

    After the install of these patches it is recommended to reconfigure +and rebuild samba.

    Thanks to Joe Meslovich for reporting

    30.1. Macintosh clients?

    30.2. OS2 Client

    30.2.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?

    30.2.2. How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?

    30.2.3. Are there any other issues when OS/2 (any version) is used as a client?

    30.2.4. How do I get printer driver download working for OS/2 clients?

    30.3. Windows for Workgroups

    30.3.1. Use latest TCP/IP stack from Microsoft

    30.3.2. Delete .pwl files after password change

    30.3.3. Configure WfW password handling

    30.3.4. Case handling of passwords

    30.3.5. Use TCP/IP as default protocol

    30.4. Windows '95/'98

    30.5. Windows 2000 Service Pack 2

    By disabling the nt acl support parameter, Samba will send -the Win2k client a response to the QuerySecurityDescriptor -trans2 call which causes the client to set a default ACL -for the profile. This default ACL includes

    DOMAIN\user "Full Control"

    This bug does not occur when using winbind to -create accounts on the Samba host for Domain users.

    30.6. Windows NT 3.1

    If you have problems communicating across routers with Windows -NT 3.1 workstations, read this Microsoft Knowledge Base article.

    Chapter 31. How to compile SAMBA

    You can obtain the samba source from the samba website. To obtain a development version, -you can download samba from CVS or using rsync.

    31.1. Access Samba source code via CVS

    31.1.1. Introduction

    Samba is developed in an open environment. Developers use CVS -(Concurrent Versioning System) to "checkin" (also known as -"commit") new source code. Samba's various CVS branches can -be accessed via anonymous CVS using the instructions -detailed in this chapter.

    This chapter is a modified version of the instructions found at -http://samba.org/samba/cvs.html

    31.1.2. 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. There are two main ways of -accessing the CVS server on this host.

    31.1.2.1. 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

    31.1.2.2. 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 up to date 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). 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.

    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. -

    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 (i.e. the HEAD tagged cvs branch). This - currently corresponds to the 3.0 development tree. -

      CVS branches other HEAD can be obtained by using the -r - 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 userinput. -

      parameter, Samba will send +the Win2k client a response to the QuerySecurityDescriptor +trans2 call which causes the client to set a default ACL +for the profile. This default ACL includes

      cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba -

    4. DOMAIN\user "Full Control"

      Whenever you want to merge in the latest code changes use - the following command from within the samba directory: -

      cvs update -d -P -

      This bug does not occur when using winbind to +create accounts on the Samba host for Domain users.

    31.2. Accessing the samba sources via rsync and ftp30.6. Windows NT 3.1

    pserver.samba.org also exports unpacked copies of most parts of the CVS tree at ftp://pserver.samba.org/pub/unpacked and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp. - See If you have problems communicating across routers with Windows +NT 3.1 workstations, read the rsync homepage for more info on rsync. -

    The disadvantage of the unpacked trees - is that they do not support automatic - merging of local changes like CVS does. - rsync access is most convenient for an - initial install. -

    this Microsoft Knowledge Base article.

    Chapter 31. SWAT - The Samba Web Admininistration Tool

    This is a rough guide to SWAT.

    31.3. Building the Binaries31.1. SWAT Features and Benefits

    To do this, first run the program ./configure - in the source directory. This should automatically - configure Samba for your operating system. If you have unusual - needs then you may wish to run

    root# ./configure --help -

    first to see what special options you can enable. - Then executing

    root# make

    will create the binaries. Once it's successfully - compiled you can use

    root# make install

    to install the binaries and manual pages. You can - separately install the binaries and/or man pages using

    You must use at least the following ...

    31.1.1. The SWAT Home Page

    root# make installbin -

    Blah blah here.

    31.1.2. Global Settings

    and

    Document steps right here!

    31.1.3. The SWAT Wizard

    root# make installman -

    Lots of blah blah here.

    31.1.4. Share Settings

    Note that if you are upgrading for a previous version - of Samba you might like to know that the old versions of - the binaries will be renamed with a ".old" extension. You - can go back to the previous version with

    Document steps right here!

    31.1.5. Printing Settings

    root# make revert -

    Document steps right here!

    31.1.6. The Status Page

    if you find this version a disaster!

    Document steps right here!

    31.3.1. Compiling samba with Active Directory support31.1.7. The Password Change Page

    In order to compile samba with ADS support, you need to have installed - on your system: -

    the MIT kerberos development libraries (either install from the sources or use a package). The heimdal libraries will not work.
    the OpenLDAP development libraries.
    Document steps right here!

    Chapter 32. Samba performance issues

    32.1. Comparisons

    The Samba server uses TCP to talk to the client. Thus if you are +trying to see if it performs well you should really compare it to +programs that use the same protocol. The most readily available +programs for file transfer that use TCP are ftp or another TCP based +SMB server.

    If you want to test against something like a NT or WfWg server then +you will have to disable all but TCP on either the client or +server. Otherwise you may well be using a totally different protocol +(such as Netbeui) and comparisons may not be valid.

    Generally you should find that Samba performs similarly to ftp at raw +transfer speed. It should perform quite a bit faster than NFS, +although this very much depends on your system.

    Several people have done comparisons between Samba and Novell, NFS or +WinNT. In some cases Samba performed the best, in others the worst. I +suspect the biggest factor is not Samba vs some other system but the +hardware and drivers used on the various systems. Given similar +hardware Samba should certainly be competitive in speed with other +systems.

    32.2. Socket options

    - -

    There are a number of socket options that can greatly affect the +performance of a TCP based server like Samba.

    If your kerberos libraries are in a non-standard location then - remember to add the configure option --with-krb5=DIR.

    The socket options that Samba uses are settable both on the command +line with the -O option, or in the smb.conf file.

    After you run configure make sure that include/config.h it generates contains lines like this:

    The "socket options" section of the smb.conf manual page describes how +to set these and gives recommendations.

    #define HAVE_KRB5 1
-#define HAVE_LDAP 1
-

    Getting the socket options right can make a big difference to your +performance, but getting them wrong can degrade it by just as +much. The correct settings are very dependent on your local network.

    If it doesn't then configure did not find your krb5 libraries or - your ldap libraries. Look in config.log to figure out why and fix - it.

    The socket option TCP_NODELAY is the one that seems to make the +biggest single difference for most networks. Many people report that +adding "socket options = TCP_NODELAY" doubles the read performance of +a Samba drive. The best explanation I have seen for this is that the +Microsoft TCP/IP stack is slow in sending tcp ACKs.

    31.3.1.1. Installing the required packages for Debian

    32.3. Read size

    On Debian you need to install the following packages:

    The option "read size" affects the overlap of disk reads/writes with +network reads/writes. If the amount of data being transferred in +several of the SMB commands (currently SMBwrite, SMBwriteX and +SMBreadbraw) is larger than this value then the server begins writing +the data before it has received the whole packet from the network, or +in the case of SMBreadbraw, it begins writing to the network before +all the data has been read from disk.

    libkrb5-dev
    krb5-user
    This overlapping works best when the speeds of disk and network access +are similar, having very little effect when the speed of one is much +greater than the other.

    -

    The default value is 16384, but very little experimentation has been +done yet to determine the optimal value, and it is likely that the best +value will vary greatly between systems anyway. A value over 65536 is +pointless and will cause you to allocate memory unnecessarily.

    31.3.1.2. Installing the required packages for RedHat

    On RedHat this means you should have at least:

    32.4. Max xmit

    krb5-workstation (for kinit)
    krb5-libs (for linking with)
    krb5-devel (because you are compiling from source)
    At startup the client and server negotiate a "maximum transmit" size, +which limits the size of nearly all SMB commands. You can set the +maximum size that Samba will negotiate using the "max xmit = " option +in smb.conf. Note that this is the maximum size of SMB request that +Samba will accept, but not the maximum size that the *client* will accept. +The client maximum receive size is sent to Samba by the client and Samba +honours this limit.

    -

    It defaults to 65536 bytes (the maximum), but it is possible that some +clients may perform better with a smaller transmit unit. Trying values +of less than 2048 is likely to cause severe problems.

    in addition to the standard development environment.

    In most cases the default is the best option.

    32.5. Log level

    Note that these are not standard on a RedHat install, and you may need - to get them off CD2.

    If you set the log level (also known as "debug level") higher than 2 +then you may suffer a large drop in performance. This is because the +server flushes the log file after each operation, which can be very +expensive.

    32.6. Read raw

    The "read raw" operation is designed to be an optimised, low-latency +file read operation. A server may choose to not support it, +however. and Samba makes support for "read raw" optional, with it +being enabled by default.

    In some cases clients don't handle "read raw" very well and actually +get lower performance using it than they get using the conventional +read operations.

    So you might like to try "read raw = no" and see what happens on your +network. It might lower, raise or not affect your performance. Only +testing can really tell.

    32.7. Write raw

    The "write raw" operation is designed to be an optimised, low-latency +file write operation. A server may choose to not support it, +however. and Samba makes support for "write raw" optional, with it +being enabled by default.

    Some machines may find "write raw" slower than normal write, in which +case you may wish to change this option.

    31.4. Starting the smbd and nmbd32.8. Slow Clients

    You must choose to start smbd and nmbd either - as daemons or from inetdDon't try - to do both! Either you can put them in inetd.conf and have them started on demand - by inetd, or you can start them as - daemons either from the command line or in /etc/rc.local. See the man pages for details - on the command line options. Take particular care to read - the bit about what user you need to be in order to start - Samba. In many cases you must be root.

    One person has reported that setting the protocol to COREPLUS rather +than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).

    The main advantage of starting smbd - and nmbd using the recommended daemon method - is that they will respond slightly more quickly to an initial connection - request.

    I suspect that his PC's (386sx16 based) were asking for more data than +they could chew. I suspect a similar speed could be had by setting +"read raw = no" and "max xmit = 2048", instead of changing the +protocol. Lowering the "read size" might also help.

    31.4.1. Starting from inetd.conf

    32.9. Slow Logins

    Slow logins are almost always due to the password checking time. Using +the lowest practical "password level" will improve things a lot. You +could also enable the "UFC crypt" option in the Makefile.

    32.10. Client tuning

    Often a speed problem can be traced to the client. The client (for +example Windows for Workgroups) can often be tuned for better TCP +performance.

    See your client docs for details. In particular, I have heard rumours +that the WfWg options TCPWINDOWSIZE and TCPSEGMENTSIZE can have a +large impact on performance.

    Also note that some people have found that setting DefaultRcvWindow in +the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a +big improvement. I don't know why.

    My own experience wth DefaultRcvWindow is that I get much better +performance with a large value (16384 or larger). Other people have +reported that anything over 3072 slows things down enourmously. One +person even reported a speed drop of a factor of 30 when he went from +3072 to 8192. I don't know why.

    It probably depends a lot on your hardware, and the type of unix box +you have at the other end of the link.

    Paul Cochrane has done some testing on client side tuning and come +to the following conclusions:

    NOTE; The following will be different if - you use NIS, NIS+ or LDAP to distribute services maps.

    Install the W2setup.exe file from www.microsoft.com. This is an +update for the winsock stack and utilities which improve performance.

    Look at your /etc/services. - What is defined at port 139/tcp. If nothing is defined - then add a line like this:

    Configure the win95 TCPIP registry settings to give better +perfomance. I use a program called MTUSPEED.exe which I got off the +net. There are various other utilities of this type freely available. +The setting which give the best performance for me are:

    netbios-ssn 139/tcp

    1. similarly for 137/udp you should have an entry like:

      MaxMTU Remove

    2. netbios-ns 137/udp

      RWIN Remove

    3. Next edit your /etc/inetd.conf - and add two lines something like this:

      MTUAutoDiscover Disable

    4. MTUBlackHoleDetect Disable

    5. Time To Live Enabled

    6. Time To Live - HOPS 32

    7. NDI Cache Size 0

    I tried virtually all of the items mentioned in the document and +the only one which made a difference to me was the socket options. It +turned out I was better off without any!!!!!

    In terms of overall speed of transfer, between various win95 clients +and a DX2-66 20MB server with a crappy NE2000 compatible and old IDE +drive (Kernel 2.0.30). The transfer rate was reasonable for 10 baseT.

    		netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd 
-		netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd 
-
    The figures are: Put Get +P166 client 3Com card: 420-440kB/s 500-520kB/s +P100 client 3Com card: 390-410kB/s 490-510kB/s +DX4-75 client NE2000: 370-380kB/s 330-350kB/s

    The exact syntax of /etc/inetd.conf - varies between unixes. Look at the other entries in inetd.conf - for a guide.

    I based these test on transfer two files a 4.5MB text file and a 15MB +textfile. The results arn't bad considering the hardware Samba is +running on. It's a crap machine!!!!

    Some unixes already have entries like netbios_ns - (note the underscore) in /etc/services. - You must either edit /etc/services or - /etc/inetd.conf to make them consistent.

    The updates mentioned in 1 and 2 brought up the transfer rates from +just over 100kB/s in some clients.

    A new client is a P333 connected via a 100MB/s card and hub. The +transfer rates from this were good: 450-500kB/s on put and 600+kB/s +on get.

    On many systems you may need to use the - interfaces option in smb.conf to specify the IP address - and netmask of your interfaces. Run ifconfig - as root if you don't know what the broadcast is for your - net. nmbd tries to determine it at run - time, but fails on some unixes. -

    Looking at standard FTP throughput, Samba is a bit slower (100kB/s +upwards). I suppose there is more going on in the samba protocol, but +if it could get up to the rate of FTP the perfomance would be quite +staggering.

    Chapter 33. The samba checklist

    33.1. Introduction

    This file contains a list of tests you can perform to validate your +Samba server. It also tells you what the likely cause of the problem +is if it fails any one of these steps. If it passes all these tests +then it is probably working fine.

    Many unixes only accept around 5 - parameters on the command line in inetd.conf. - This means you shouldn't use spaces between the options and - arguments, or you should use a script, and start the script - from inetd.

    You should do ALL the tests, in the order shown. We have tried to +carefully choose them so later tests only use capabilities verified in +the earlier tests.

    Restart inetd, perhaps just send - it a HUP. If you have installed an earlier version of nmbd then you may need to kill nmbd as well.

    If you send one of the samba mailing lists an email saying "it doesn't work" +and you have not followed this test procedure then you should not be surprised +your email is ignored.

    31.4.2. Alternative: starting it as a daemon

    33.2. Assumptions

    To start the server as a daemon you should create - a script something like this one, perhaps calling - it In all of the tests it is assumed you have a Samba server called +BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.

    The procedure is similar for other types of clients.

    It is also assumed you know the name of an available share in your +smb.conf. I will assume this share is called tmp. +You can add a tmp share like by adding the +following to startsmb.

    smb.conf:

    		#!/bin/sh
-		/usr/local/samba/bin/smbd -D 
-		/usr/local/samba/bin/nmbd -D 
-

    then make it executable with chmod - +x startsmb [tmp] + comment = temporary files + path = /tmp + read only = yes

    You can then run startsmb by - hand or execute it from /etc/rc.local -

    To kill it send a kill signal to the processes - nmbd and smbd.

    If you use the SVR4 style init system then - you may like to look at the examples/svr4-startup - script to make Samba fit into that system.

    These tests assume version 3.0 or later of the samba suite. Some commands shown did not exist in earlier versions.

    Chapter 32. Reporting Bugs

    32.1. Introduction

    The email address for bug reports for stable releases is samba@samba.org. -Bug reports for alpha releases should go to samba-technical@samba.org.

    Please take the time to read this file before you submit a bug -report. Also, please see if it has changed between releases, as we -may be changing the bug reporting mechanism at some time.

    Please also do as much as you can yourself to help track down the -bug. Samba is maintained by a dedicated group of people who volunteer -their time, skills and efforts. We receive far more mail about it than -we can possibly answer, so you have a much higher chance of an answer -and a fix if you send us a "developer friendly" bug report that lets -us fix it fast.

    Do not assume that if you post the bug to the comp.protocols.smb -newsgroup or the mailing list that we will read it. If you suspect that your -problem is not a bug but a configuration problem then it is better to send -it to the Samba mailing list, as there are (at last count) 5000 other users on -that list that may be able to help you.

    Please pay attention to the error messages you receive. If any error message +reports that your server is being unfriendly you should first check that you +IP name resolution is correctly set up. eg: Make sure your /etc/resolv.conf +file points to name servers that really do exist.

    You may also like to look though the recent mailing list archives, -which are conveniently accessible on the Samba web pages -at http://samba.org/samba/Also, if you do not have DNS server access for name resolution please check +that the settings for your smb.conf file results in dns proxy = no. The +best way to check this is with testparm smb.conf.

    32.2. General info33.3. The tests

    Before submitting a bug report check your config for silly -errors. Look in your log files for obvious messages that tell you that -you've misconfigured something and run testparm to test your config -file for correct syntax.

    Have you run through the diagnosis? -This is very important.

    If you include part of a log file with your bug report then be sure to -annotate it with exactly what you were doing on the client at the -time, and exactly what the results were.

    32.3. Debug levels

    If the bug has anything to do with Samba behaving incorrectly as a -server (like refusing to open a file) then the log files will probably -be very useful. Depending on the problem a log level of between 3 and -10 showing the problem may be appropriate. A higher level givesmore -detail, but may use too much disk space.

    Diagnosing your samba server

    1. To set the debug level use log level = in your -In the directory in which you store your smb.conf. You may also find it useful to set the log -level higher for just one machine and keep separate logs for each machine. -To do this use:

      file, run the command +testparm smb.conf. If it reports any errors then your smb.conf +configuration file is faulty.

      log level = 10
-log file = /usr/local/samba/lib/log.%m
-include = /usr/local/samba/lib/smb.conf.%m

      then create a file -/usr/local/samba/lib/smb.conf.machine where -machine is the name of the client you wish to debug. In that file -put any Your smb.conf commands you want, for example +> file may be located in: /etc/samba +Or in: /usr/local/samba/lib

    2. Run the command ping BIGSERVER from the PC and +ping ACLIENT from +the unix box. If you don't get a valid response then your TCP/IP +software is not correctly installed.

      Note that you will need to start a "dos prompt" window on the PC to +run ping.

      If you get a message saying "host not found" or similar then your DNS +software or /etc/hosts file is not correctly setup. +It is possible to +run samba without DNS entries for the server and client, but I assume +you do have correct entries for the remainder of these tests.

      Another reason why ping might fail is if your host is running firewall +software. You will need to relax the rules to let in the workstation +in question, perhaps by allowing access from another subnet (on Linux +this is done via the ipfwadm program.)

    3. Run the command smbclient -L BIGSERVER on the unix box. You +should get a list of available shares back.

      If you get a error message containing the string "Bad password" then +you probably have either an incorrect hosts allow, log level= may be useful. This also allows you to -experiment with different security systems, protocol levels etc on just -one machine.

      The hosts deny or valid users line in your +smb.conf entry , or your guest account is not +valid. Check what your guest account is using testparm and +temporarily remove any log level = -is synonymous with the entry hosts allow, debuglevel = that has been -used in older versions of Samba and is being retained for backwards -compatibility of smb.conf files.

      As the hosts deny, log level = value is increased you will record -a significantly increasing level of debugging information. For most -debugging operations you may not need a setting higher than 3. Nearly -all bugs can be tracked at a setting of 10, but be prepared for a VERY -large volume of log data.

    32.4. Internal errors

    If you get a "INTERNAL ERROR" message in your log files it means that -Samba got an unexpected signal while running. It is probably a -segmentation fault and almost certainly means a bug in Samba (unless -you have faulty hardware or system software).

    If the message came from smbd then it will probably be accompanied by -a message which details the last SMB message received by smbd. This -info is often very useful in tracking down the problem so please -include it in your bug report.

    valid users or invalid users lines.

    You should also detail how to reproduce the problem, if -possible. Please make this reasonably detailed.

    If you get a "connection refused" response then the smbd server may +not be running. If you installed it in inetd.conf then you probably edited +that file incorrectly. If you installed it as a daemon then check that +it is running, and check that the netbios-ssn port is in a LISTEN +state using netstat -a.

    You may also find that a core file appeared in a If you get a "session request failed" then the server refused the +connection. If it says "Your server software is being unfriendly" then +its probably because you have invalid command line parameters to smbd, +or a similar fatal problem with the initial startup of smbd. Also +check your config file (corefilessmb.conf) for syntax errors with testparm -subdirectory of the directory where you keep your samba log -files. This file is the most useful tool for tracking down the bug. To -use it you do this:

    gdb smbd coreThere are a number of reasons for which smbd may refuse or decline +a session request. The most common of these involve one or more of +the following smb.conf file entries:

    	hosts deny = ALL
+	hosts allow = xxx.xxx.xxx.xxx/yy
+	bind interfaces only = Yes

    adding appropriate paths to smbd and core so gdb can find them. If you -don't have gdb then try dbx. Then within the debugger use the -command where to give a stack trace of where the problem -occurred. Include this in your mail.

    In the above, no allowance has been made for any session requests that +will automatically translate to the loopback adaptor address 127.0.0.1. +To solve this problem change these lines to:

    If you known any assembly language then do a disass of the routine -where the problem occurred (if its in a library routine then -disassemble the routine that called it) and try to work out exactly -where the problem is by looking at the surrounding code. Even if you -don't know assembly then incuding this info in the bug report can be -useful.

    32.5. Attaching to a running process

    	hosts deny = ALL
+	hosts allow = xxx.xxx.xxx.xxx/yy 127.

    Unfortunately some unixes (in particular some recent linux kernels) -refuse to dump a core file if the task has changed uid (which smbd -does often). To debug with this sort of system you could try to attach -to the running process using gdb smbd PID where you get PID from -Do NOT use the bind interfaces only parameter where you +may wish to +use the samba password change facility, or where smbstatus. Then use c to continue and try to cause the core dump -using the client. The debugger should catch the fault and tell you -where it occurred.

    32.6. Patches

    smbclient may need to +access local service for name resolution or for local resource +connections. (Note: the bind interfaces only parameter deficiency +where it will not allow connections to the loopback address will be +fixed soon).

    The best sort of bug report is one that includes a fix! If you send us -patches please use diff -u format if your version of -diff supports it, otherwise use Another common cause of these two errors is having something already running +on port 139, such as Samba (ie: smbd is running from inetd already) or +something like Digital's Pathworks. Check your inetd.conf file before trying +to start smbd as a daemon, it can avoid a lot of frustration!

    And yet another possible cause for failure of this test is when the subnet mask +and / or broadcast address settings are incorrect. Please check that the +network interface IP Address / Broadcast Address / Subnet Mask settings are +correct and that Samba has correctly noted these in the log.nmb file.

  • Run the command diff -c4. Make sure -your do the diff against a clean version of the source and let me know -exactly what version you used.

    • Chapter 33. The samba checklist

    33.1. Introduction

    nmblookup -B BIGSERVER __SAMBA__. You should get the +IP address of your Samba server back.

    If you don't then nmbd is incorrectly installed. Check your inetd.conf +if you run it from there, or that the daemon is running and listening +to udp port 137.

    This file contains a list of tests you can perform to validate your -Samba server. It also tells you what the likely cause of the problem -is if it fails any one of these steps. If it passes all these tests -then it is probably working fine.

    One common problem is that many inetd implementations can't take many +parameters on the command line. If this is the case then create a +one-line script that contains the right parameters and run that from +inetd.

  • You should do ALL the tests, in the order shown. We have tried to -carefully choose them so later tests only use capabilities verified in -the earlier tests.

    run the command nmblookup -B ACLIENT '*'

    If you send one of the samba mailing lists an email saying "it doesn't work" -and you have not followed this test procedure then you should not be surprised -your email is ignored.

    • 33.2. Assumptions

    You should get the PCs IP address back. If you don't then the client +software on the PC isn't installed correctly, or isn't started, or you +got the name of the PC wrong.

    In all of the tests it is assumed you have a Samba server called -BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.

    If ACLIENT doesn't resolve via DNS then use the IP address of the +client in the above test.

  • The procedure is similar for other types of clients.

    Run the command nmblookup -d 2 '*'

    It is also assumed you know the name of an available share in your -smb.conf. I will assume this share is called tmp. -You can add a tmp share like by adding the -following to This time we are trying the same as the previous test but are trying +it via a broadcast to the default broadcast address. A number of +Netbios/TCPIP hosts on the network should respond, although Samba may +not catch all of the responses in the short time it listens. You +should see "got a positive name query response" messages from several +hosts.

    If this doesn't give a similar result to the previous test then +nmblookup isn't correctly getting your broadcast address through its +automatic mechanism. In this case you should experiment use the +interfaces option in smb.conf:

    to manually configure your IP +address, broadcast and netmask. 

    
[tmp]
- comment = temporary files 
- path = /tmp
- read only = yes
    If your PC and server aren't on the same subnet then you will need to +use the -B option to set the broadcast address to the that of the PCs +subnet.

    This test will probably fail if your subnet mask and broadcast address are +not correct. (Refer to TEST 3 notes above).

  • Run the command smbclient //BIGSERVER/TMP. You should +then be prompted for a password. You should use the password of the account +you are logged into the unix box with. If you want to test with +another account then add the -U accountname option to the end of +the command line. eg: +smbclient //bigserver/tmp -Ujohndoe

    These tests assume version 3.0 or later of the samba suite. Some commands shown did not exist in earlier versions.

    It is possible to specify the password along with the username +as follows: +smbclient //bigserver/tmp -Ujohndoe%secret

    Please pay attention to the error messages you receive. If any error message -reports that your server is being unfriendly you should first check that you -IP name resolution is correctly set up. eg: Make sure your /etc/resolv.conf -file points to name servers that really do exist.

    Also, if you do not have DNS server access for name resolution please check -that the settings for your Once you enter the password you should get the smb> prompt. If you +don't then look at the error message. If it says "invalid network +name" then the service "tmp" is not correctly setup in your smb.conf file results in dns proxy = no. The -best way to check this is with testparm smb.conf.

    • 33.3. The tests

    Diagnosing your samba serverIf it says "bad password" then the likely causes are:

    1. In the directory in which you store your smb.conf file, run the command -testparm smb.conf. If it reports any errors then your you have shadow passords (or some other password system) but didn't + compile in support for them in smbd +

    2. your valid users configuration is incorrect +

    3. you have a mixed case password and you haven't enabled the password + level option at a high enough level +

    4. the path = line in smb.conf is incorrect. Check it with testparm -configuration file is faulty.

    5. you enabled password encryption but didn't create the SMB encrypted + password file +

      Once connected you should be able to use the commands +dir get put etc. +Type help command for instructions. You should +especially check that the amount of free disk space shown is correct +when you type dir.

    6. On the PC type the command net view \\BIGSERVER. You will +need to do this from within a "dos prompt" window. You should get back a +list of available shares on the server.

      If you get a "network name not found" or similar error then netbios +name resolution is not working. This is usually caused by a problem in +nmbd. To overcome it you could do one of the following (you only need +to choose one of them):

      Your smb.conf file may be located in: /etc/samba -Or in: /usr/local/samba/lib

    1. fixup the nmbd installation

    2. Run the command ping BIGSERVER from the PC and - add the IP address of BIGSERVER to the wins server box in the + advanced tcp/ip setup on the PC.

    3. enable windows name resolution via DNS in the advanced section of + the tcp/ip setup

    4. add BIGSERVER to your lmhosts file on the PC.

    If you get a "invalid network name" or "bad password error" then the +same fixes apply as they did for the ping ACLIENT from -the unix box. If you don't get a valid response then your TCP/IP -software is not correctly installed.

    smbclient -L test above. In +particular, make sure your hosts allow line is correct (see the man +pages)

    Note that you will need to start a "dos prompt" window on the PC to -run ping.

    Also, do not overlook that fact that when the workstation requests the +connection to the samba server it will attempt to connect using the +name with which you logged onto your Windows machine. You need to make +sure that an account exists on your Samba server with that exact same +name and password.

    If you get a message saying "host not found" or similar then your DNS -software or If you get "specified computer is not receiving requests" or similar +it probably means that the host is not contactable via tcp services. +Check to see if the host is running tcp wrappers, and if so add an entry in +the /etc/hosts file is not correctly setup. -It is possible to -run samba without DNS entries for the server and client, but I assume -you do have correct entries for the remainder of these tests.

    Another reason why ping might fail is if your host is running firewall -software. You will need to relax the rules to let in the workstation -in question, perhaps by allowing access from another subnet (on Linux -this is done via the ipfwadm program.)

    hosts.allow file for your client (or subnet, etc.)

  • Run the command smbclient -L BIGSERVER on the unix box. You -should get a list of available shares back.

    If you get a error message containing the string "Bad password" then -you probably have either an incorrect net use x: \\BIGSERVER\TMP. You should +be prompted for a password then you should get a "command completed +successfully" message. If not then your PC software is incorrectly +installed or your smb.conf is incorrect. make sure your hosts allow, - +and other config lines in smb.conf are correct.

    It's also possible that the server can't work out what user name to +connect you as. To see if this is the problem add the line hosts deny or user = +username to the valid users line in your +>[tmp] section of smb.conf, or your guest account is not -valid. Check what your guest account is using testparm and -temporarily remove any hosts allow, hosts deny, valid users or where username is the +username corresponding to the password you typed. If you find this +fixes things you may need the username mapping option.

    It might also be the case that your client only sends encrypted passwords +and you have invalid users lines.

    encrypt passwords = no in smb.conf +Turn it back on to fix.

  • If you get a "connection refused" response then the smbd server may -not be running. If you installed it in inetd.conf then you probably edited -that file incorrectly. If you installed it as a daemon then check that -it is running, and check that the netbios-ssn port is in a LISTEN -state using Run the command netstat -a.

    nmblookup -M testgroup where +testgroup is the name of the workgroup that your Samba server and +Windows PCs belong to. You should get back the IP address of the +master browser for that workgroup.

    If you get a "session request failed" then the server refused the -connection. If it says "Your server software is being unfriendly" then -its probably because you have invalid command line parameters to smbd, -or a similar fatal problem with the initial startup of smbd. Also -check your config file (If you don't then the election process has failed. Wait a minute to +see if it is just being slow then try again. If it still fails after +that then look at the browsing options you have set in smb.conf) for syntax errors with testparm -and that the various directories where samba keeps its log and lock -files exist.

    . Make +sure you have preferred master = yes to ensure that +an election is held at startup.

  • There are a number of reasons for which smbd may refuse or decline -a session request. The most common of these involve one or more of -the following From file manager try to browse the server. Your samba server should +appear in the browse list of your local workgroup (or the one you +specified in smb.conf). You should be able to double click on the name +of the server and get a list of shares. If you get a "invalid +password" error when you do then you are probably running WinNT and it +is refusing to browse a server that has no encrypted password +capability and is in user level security mode. In this case either set +security = server AND +password server = Windows_NT_Machine in your +smb.conf file entries:

    file, or make sure encrypted passwords is +set to "yes".

    • 33.4. Still having troubles?

    	hosts deny = ALL
-	hosts allow = xxx.xxx.xxx.xxx/yy
-	bind interfaces only = Yes

    Read the chapter on +Analysing and Solving Problems.

    Chapter 34. Analysing and solving samba problems

    In the above, no allowance has been made for any session requests that -will automatically translate to the loopback adaptor address 127.0.0.1. -To solve this problem change these lines to:

    There are many sources of information available in the form +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.

    34.1. Diagnostics tools

    	hosts deny = ALL
-	hosts allow = xxx.xxx.xxx.xxx/yy 127.

    One of the best diagnostic tools for debugging problems is Samba itself. +You can use the -d option for both smbd and nmbd to specify what +'debug level' at which to run. See the man pages on smbd, nmbd and +smb.conf for more information on debugging options. The debug +level can range from 1 (the default) to 10 (100 for debugging passwords).

    Do NOT use the bind interfaces only parameter where you -may wish to -use the samba password change facility, or where smbclient may need to -access local service for name resolution or for local resource -connections. (Note: the Another helpful method of debugging is to compile samba using the +bind interfaces only parameter deficiency -where it will not allow connections to the loopback address will be -fixed soon).

    gcc -g flag. This will include debug +information in the binaries and allow you to attach gdb to the +running smbd / nmbd process. In order to attach gdb to an smbd +process for an NT workstation, first get the workstation to make the +connection. Pressing ctrl-alt-delete and going down to the domain box +is sufficient (at least, on the first time you join the domain) to +generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation +maintains an open connection, and therefore there will be an smbd +process running (assuming that you haven't set a really short smbd +idle timeout) So, in between pressing ctrl alt delete, and actually +typing in your password, you can gdb attach and continue.

    Another common cause of these two errors is having something already running -on port 139, such as Samba (ie: smbd is running from inetd already) or -something like Digital's Pathworks. Check your inetd.conf file before trying -to start smbd as a daemon, it can avoid a lot of frustration!

    Some useful samba commands worth investigating:

    And yet another possible cause for failure of this test is when the subnet mask -and / or broadcast address settings are incorrect. Please check that the -network interface IP Address / Broadcast Address / Subnet Mask settings are -correct and that Samba has correctly noted these in the log.nmb file.

    • testparam | more

    • Run the command nmblookup -B BIGSERVER __SAMBA__. You should get the -IP address of your Samba server back.

      smbclient -L //{netbios name of server}

    If you don't then nmbd is incorrectly installed. Check your inetd.conf -if you run it from there, or that the daemon is running and listening -to udp port 137.

    An SMB enabled version of tcpdump is available from +http://www.tcpdup.org/. +Ethereal, another good packet sniffer for Unix and Win32 +hosts, can be downloaded from http://www.ethereal.com.

    One common problem is that many inetd implementations can't take many -parameters on the command line. If this is the case then create a -one-line script that contains the right parameters and run that from -inetd.

  • For tracing things on the Microsoft Windows NT, Network Monitor +(aka. netmon) is available on the Microsoft Developer Network CD's, +the Windows NT Server install CD and the SMS CD's. The version of +netmon that ships with SMS allows for dumping packets between any two +computers (i.e. placing the network interface in promiscuous mode). +The version on the NT Server install CD will only allow monitoring +of network traffic directed to the local NT box and broadcasts on the +local subnet. Be aware that Ethereal can read and write netmon +formatted files.

    • 34.2. Installing 'Network Monitor' on an NT Workstation or a Windows 9x box

    Installing netmon on an NT workstation requires a couple +of steps. The following are for installing Netmon V4.00.349, which comes +with Microsoft Windows NT Server 4.0, on Microsoft Windows NT +Workstation 4.0. The process should be similar for other version of +Windows NT / Netmon. You will need both the Microsoft Windows +NT Server 4.0 Install CD and the Workstation 4.0 Install CD.

    Initially you will need to install 'Network Monitor Tools and Agent' +on the NT Server. To do this

    run the command nmblookup -B ACLIENT '*'

    • You should get the PCs IP address back. If you don't then the client -software on the PC isn't installed correctly, or isn't started, or you -got the name of the PC wrong.

      Goto Start - Settings - Control Panel - + Network - Services - Add

    • If ACLIENT doesn't resolve via DNS then use the IP address of the -client in the above test.

      Select the 'Network Monitor Tools and Agent' and + click on 'OK'.

    • Run the command nmblookup -d 2 '*'

      Click 'OK' on the Network Control Panel. +

    • This time we are trying the same as the previous test but are trying -it via a broadcast to the default broadcast address. A number of -Netbios/TCPIP hosts on the network should respond, although Samba may -not catch all of the responses in the short time it listens. You -should see "got a positive name query response" messages from several -hosts.

      Insert the Windows NT Server 4.0 install CD + when prompted.

    If this doesn't give a similar result to the previous test then -nmblookup isn't correctly getting your broadcast address through its -automatic mechanism. In this case you should experiment use the -interfaces option in At this point the Netmon files should exist in +smb.conf to manually configure your IP -address, broadcast and netmask.

    %SYSTEMROOT%\System32\netmon\*.*. +Two subdirectories exist as well, parsers\ +which contains the necessary DLL's for parsing the netmon packet +dump, and captures\.

    If your PC and server aren't on the same subnet then you will need to -use the -B option to set the broadcast address to the that of the PCs -subnet.

    In order to install the Netmon tools on an NT Workstation, you will +first need to install the 'Network Monitor Agent' from the Workstation +install CD.

    This test will probably fail if your subnet mask and broadcast address are -not correct. (Refer to TEST 3 notes above).

    • Goto Start - Settings - Control Panel - + Network - Services - Add

    • Run the command smbclient //BIGSERVER/TMP. You should -then be prompted for a password. You should use the password of the account -you are logged into the unix box with. If you want to test with -another account then add the -U accountname option to the end of -the command line. eg: -smbclient //bigserver/tmp -Ujohndoe

      Select the 'Network Monitor Agent' and click + on 'OK'.

    • Click 'OK' on the Network Control Panel. +

    • Insert the Windows NT Workstation 4.0 install + CD when prompted.

    Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* +to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set +permissions as you deem appropriate for your site. You will need +administrative rights on the NT box to run netmon.

    To install Netmon on a Windows 9x box install the network monitor agent +from the Windows 9x CD (\admin\nettools\netmon). There is a readme +file located with the netmon driver files on the CD if you need +information on how to do this. Copy the files from a working +Netmon installation.

    34.3. Useful URL's

    • It is possible to specify the password along with the username -as follows: -smbclient //bigserver/tmp -Ujohndoe%secret

    Home of Samba site http://samba.org. We have a mirror near you !

  • Once you enter the password you should get the smb> prompt. If you -don't then look at the error message. If it says "invalid network -name" then the service "tmp" is not correctly setup in your smb.conf.

    The Development document +on the Samba mirrors might mention your problem. If so, +it might mean that the developers are working on it.

  • See how Scott Merrill simulates a BDC behavior at + http://www.skippy.net/linux/smb-howto.html.

  • If it says "bad password" then the likely causes are:

    Although 2.0.7 has almost had its day as a PDC, David Bannon will + keep the 2.0.7 PDC pages at http://bioserve.latrobe.edu.au/samba going for a while yet.

  • Misc links to CIFS information + http://samba.org/cifs/

    1. you have shadow passords (or some other password system) but didn't - compile in support for them in smbd -

      NT Domains for Unix http://mailhost.cb1.com/~lkcl/ntdom/

    2. your valid users configuration is incorrect -

      FTP site for older SMB specs: + ftp://ftp.microsoft.com/developr/drg/CIFS/

    • 34.4. Getting help from the mailing lists

    you have a mixed case password and you haven't enabled the There are a number of Samba related mailing lists. Go to http://samba.org, click on your nearest mirror +and then click on password - level option at a high enough level -

    Support and then click on Samba related mailing lists.

    For questions relating to Samba TNG go to +http://www.samba-tng.org/ +It has been requested that you don't post questions about Samba-TNG to the +main stream Samba lists.

    If you post a message to one of the lists please observe the following guide lines :

    • Always remember that the developers are volunteers, they are +not paid and they never guarantee to produce a particular feature at +a particular time. Any time lines are 'best guess' and nothing more.

    • the path = line in Always mention what version of samba you are using and what +operating system its running under. You should probably list the +relevant sections of your smb.conf is incorrect. Check it with testparm -

      file, at least the options +in [global] that affect PDC support.

    • you enabled password encryption but didn't create the SMB encrypted - password file -

      In addition to the version, if you obtained Samba via +CVS mention the date when you last checked it out.

    • Once connected you should be able to use the commands -dir get put etc. -Type help command for instructions. You should -especially check that the amount of free disk space shown is correct -when you type dir.

      Try and make your question clear and brief, lots of long, +convoluted questions get deleted before they are completely read ! +Don't post html encoded messages (if you can select colour or font +size its html).

    • On the PC type the command net view \\BIGSERVER. You will -need to do this from within a "dos prompt" window. You should get back a -list of available shares on the server.

      If you get a "network name not found" or similar error then netbios -name resolution is not working. This is usually caused by a problem in -nmbd. To overcome it you could do one of the following (you only need -to choose one of them):

        If you run one of those nifty 'I'm on holidays' things when +you are away, make sure its configured to not answer mailing lists.

      1. fixup the nmbd installation

        Don't cross post. Work out which is the best list to post to +and see what happens, i.e. don't post to both samba-ntdom and samba-technical. +Many people active on the lists subscribe to more +than one list and get annoyed to see the same message two or more times. +Often someone will see a message and thinking it would be better dealt +with on another, will forward it on for you.

      2. add the IP address of BIGSERVER to the wins server box in the - advanced tcp/ip setup on the PC.

        You might include partial +log files written at a debug level set to as much as 20. +Please don't send the entire log but enough to give the context of the +error messages.

      3. enable windows name resolution via DNS in the advanced section of - the tcp/ip setup

        (Possibly) If you have a complete netmon trace ( from the opening of +the pipe to the error ) you can send the *.CAP file as well.

      4. add BIGSERVER to your lmhosts file on the PC.

        Please think carefully before attaching a document to an email. +Consider pasting the relevant parts into the body of the message. The samba +mailing lists go to a huge number of people, do they all need a copy of your +smb.conf in their attach directory?

    34.5. How to get off the mailinglists

    If you get a "invalid network name" or "bad password error" then the -same fixes apply as they did for the smbclient -L test above. In -particular, make sure your To have your name removed from a samba mailing list, go to the +same place you went to to get on it. Go to http://lists.samba.org, +click on your nearest mirror and then click on hosts allow line is correct (see the man -pages)

    Support and +then click on Samba related mailing lists. Or perhaps see +here

    Also, do not overlook that fact that when the workstation requests the -connection to the samba server it will attempt to connect using the -name with which you logged onto your Windows machine. You need to make -sure that an account exists on your Samba server with that exact same -name and password.

    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...)

    Chapter 35. Reporting Bugs

    35.1. Introduction

    If you get "specified computer is not receiving requests" or similar -it probably means that the host is not contactable via tcp services. -Check to see if the host is running tcp wrappers, and if so add an entry in -the hosts.allow file for your client (or subnet, etc.)

  • The email address for bug reports for stable releases is samba@samba.org. +Bug reports for alpha releases should go to samba-technical@samba.org.

    Please take the time to read this file before you submit a bug +report. Also, please see if it has changed between releases, as we +may be changing the bug reporting mechanism at some time.

    Please also do as much as you can yourself to help track down the +bug. Samba is maintained by a dedicated group of people who volunteer +their time, skills and efforts. We receive far more mail about it than +we can possibly answer, so you have a much higher chance of an answer +and a fix if you send us a "developer friendly" bug report that lets +us fix it fast.

    Do not assume that if you post the bug to the comp.protocols.smb +newsgroup or the mailing list that we will read it. If you suspect that your +problem is not a bug but a configuration problem then it is better to send +it to the Samba mailing list, as there are (at last count) 5000 other users on +that list that may be able to help you.

    You may also like to look though the recent mailing list archives, +which are conveniently accessible on the Samba web pages +at http://samba.org/samba/.

    • 35.2. General info

    Before submitting a bug report check your config for silly +errors. Look in your log files for obvious messages that tell you that +you've misconfigured something and run testparm to test your config +file for correct syntax.

    Run the command net use x: \\BIGSERVER\TMP. You should -be prompted for a password then you should get a "command completed -successfully" message. If not then your PC software is incorrectly -installed or your smb.conf is incorrect. make sure your hosts allow -and other config lines in smb.conf are correct.

    Have you run through the diagnosis? +This is very important.

    It's also possible that the server can't work out what user name to -connect you as. To see if this is the problem add the line user = -username to the If you include part of a log file with your bug report then be sure to +annotate it with exactly what you were doing on the client at the +time, and exactly what the results were.

    35.3. Debug levels

    If the bug has anything to do with Samba behaving incorrectly as a +server (like refusing to open a file) then the log files will probably +be very useful. Depending on the problem a log level of between 3 and +10 showing the problem may be appropriate. A higher level givesmore +detail, but may use too much disk space.

    To set the debug level use [tmp] section of +>log level = in your smb.conf where username is the -username corresponding to the password you typed. If you find this -fixes things you may need the username mapping option.

    . You may also find it useful to set the log +level higher for just one machine and keep separate logs for each machine. +To do this use:

    It might also be the case that your client only sends encrypted passwords -and you have encrypt passwords = no in smb.conf -Turn it back on to fix.

  • log level = 10
+log file = /usr/local/samba/lib/log.%m
+include = /usr/local/samba/lib/smb.conf.%m

    Run the command nmblookup -M then create a file +/usr/local/samba/lib/smb.conf.testgroup where +>machine where testgroup is the name of the workgroup that your Samba server and -Windows PCs belong to. You should get back the IP address of the -master browser for that workgroup.

    If you don't then the election process has failed. Wait a minute to -see if it is just being slow then try again. If it still fails after -that then look at the browsing options you have set in machine is the name of the client you wish to debug. In that file +put any smb.conf. Make -sure you have commands you want, for example +preferred master = yes to ensure that -an election is held at startup.

  • log level= may be useful. This also allows you to +experiment with different security systems, protocol levels etc on just +one machine.

    From file manager try to browse the server. Your samba server should -appear in the browse list of your local workgroup (or the one you -specified in smb.conf). You should be able to double click on the name -of the server and get a list of shares. If you get a "invalid -password" error when you do then you are probably running WinNT and it -is refusing to browse a server that has no encrypted password -capability and is in user level security mode. In this case either set -The smb.conf entry security = server AND -log level = +is synonymous with the entry password server = Windows_NT_Machine in your -debuglevel = that has been +used in older versions of Samba and is being retained for backwards +compatibility of smb.conf file, or make sure files.

    As the encrypted passwords is -set to "yes".

    • log level = value is increased you will record +a significantly increasing level of debugging information. For most +debugging operations you may not need a setting higher than 3. Nearly +all bugs can be tracked at a setting of 10, but be prepared for a VERY +large volume of log data.

    33.4. Still having troubles?35.4. Internal errors

    Try the mailing list or newsgroup, or use the ethereal utility to -sniff the problem. The official samba mailing list can be reached at -samba@samba.org. To find -out more about samba and how to subscribe to the mailing list check -out the samba web page at -http://samba.org/samba/If you get a "INTERNAL ERROR" message in your log files it means that +Samba got an unexpected signal while running. It is probably a +segmentation fault and almost certainly means a bug in Samba (unless +you have faulty hardware or system software).

    If the message came from smbd then it will probably be accompanied by +a message which details the last SMB message received by smbd. This +info is often very useful in tracking down the problem so please +include it in your bug report.

    You should also detail how to reproduce the problem, if +possible. Please make this reasonably detailed.

    You may also find that a core file appeared in a corefiles +subdirectory of the directory where you keep your samba log +files. This file is the most useful tool for tracking down the bug. To +use it you do this:

    gdb smbd core

    adding appropriate paths to smbd and core so gdb can find them. If you +don't have gdb then try dbx. Then within the debugger use the +command where to give a stack trace of where the problem +occurred. Include this in your mail.

    If you known any assembly language then do a disass of the routine +where the problem occurred (if its in a library routine then +disassemble the routine that called it) and try to work out exactly +where the problem is by looking at the surrounding code. Even if you +don't know assembly then incuding this info in the bug report can be +useful.

    35.5. Attaching to a running process

    Unfortunately some unixes (in particular some recent linux kernels) +refuse to dump a core file if the task has changed uid (which smbd +does often). To debug with this sort of system you could try to attach +to the running process using gdb smbd PID where you get PID from +smbstatus. Then use c to continue and try to cause the core dump +using the client. The debugger should catch the fault and tell you +where it occurred.

    35.6. Patches

    The best sort of bug report is one that includes a fix! If you send us +patches please use diff -u format if your version of +diff supports it, otherwise use diff -c4. Make sure +your do the diff against a clean version of the source and let me know +exactly what version you used.

    NextChapter 8. Samba as a ADS domain memberChapter 9. Samba as a ADS domain member

    This is a rough guide to setting up Samba 3.0 with kerberos authentication against a Windows2000 KDC.

    8.1. Setup your 9.1. Setup your smb.conf

    8.2. Setup your 9.2. Setup your /etc/krb5.conf8.3. Create the computer account9.3. Create the computer account

    As a user that has write permission on the Samba private directory @@ -271,8 +319,8 @@ CLASS="SECT2" >

    8.3.1. Possible errors9.3.1. Possible errors

    8.4. Test your server setup9.4. Test your server setup

    On a Windows 2000 client try 8.5. Testing with 9.5. Testing with smbclient

    8.6. Notes9.6. Notes

    You must change administrator password at least once after DC @@ -386,7 +434,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" >NextNext

    IV. Appendixes

    Table of Contents
    26. SWAT - The Samba Web Admininistration Tool
    26.1. SWAT Features and Benefits
    26.1.1. The SWAT Home Page
    26.1.2. Global Settings
    26.1.3. The SWAT Wizard
    26.1.4. Share Settings
    26.1.5. Printing Settings
    26.1.6. The Status Page
    26.1.7. The Password Change Page
    27. Migration from NT4 PDC to Samba-3 PDC
    27.1. Planning and Getting Started
    27.1.1. Objectives
    27.1.2. Steps In Migration Process
    27.2. Managing Samba-3 Domain Control
    28. Samba performance issues
    28.1. Comparisons
    28.2. Socket options
    28.3. Read size
    28.4. Max xmit
    28.5. Log level
    28.6. Read raw
    28.7. Write raw
    28.8. Slow Clients
    28.9. Slow Logins
    28.10. Client tuning
    29. Portability
    29.1. HPUX
    29.2. SCO Unix
    29.3. DNIX
    29.4. RedHat Linux Rembrandt-II
    29.5. AIX
    29.5.1. Sequential Read Ahead
    29.6. Solaris
    30. Samba and other CIFS clients
    30.1. Macintosh clients?
    30.2. OS2 Client
    30.2.1. How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?
    30.2.2. How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?
    30.2.3. Are there any other issues when OS/2 (any version) - is used as a client?
    30.2.4. How do I get printer driver download working - for OS/2 clients?
    30.3. Windows for Workgroups
    30.3.1. Use latest TCP/IP stack from Microsoft
    30.3.2. Delete .pwl files after password change
    30.3.3. Configure WfW password handling
    30.3.4. Case handling of passwords
    30.3.5. Use TCP/IP as default protocol
    30.4. Windows '95/'98
    30.5. Windows 2000 Service Pack 2
    30.6. Windows NT 3.1
    31. How to compile SAMBA
    31.1. Access Samba source code via CVS
    31.1.1. Introduction
    31.1.2. CVS Access to samba.org
    31.2. Accessing the samba sources via rsync and ftp
    31.3. Building the Binaries
    31.3.1. Compiling samba with Active Directory support
    31.4. Starting the smbd and nmbd
    31.4.1. Starting from inetd.conf
    31.4.2. Alternative: starting it as a daemon
    32. Reporting Bugs
    32.1. Introduction
    32.2. General info
    32.3. Debug levels
    32.4. Internal errors
    32.5. Attaching to a running process
    32.6. Patches
    33. The samba checklist
    33.1. Introduction
    33.2. Assumptions
    33.3. The tests
    33.4. Still having troubles?
    NextSWAT - The Samba Web Admininistration ToolHow to compile SAMBA
    Chapter 2. Quick Cross Subnet Browsing / Cross Workgroup Browsing guideChapter 3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide

    This document should be read in conjunction with Browsing and may be taken as the fast track guide to implementing browsing across subnets @@ -113,8 +178,8 @@ CLASS="SECT1" >

    2.1. Discussion3.1. Discussion

    Firstly, all MS Windows networking is based on SMB (Server Message @@ -204,8 +269,8 @@ CLASS="SECT1" >

    2.2. How browsing functions and how to deploy stable and +NAME="AEN327" +>3.2. How browsing functions and how to deploy stable and dependable browsing using Samba

    2.3. Use of the 3.3. Use of the Remote Announce parameter

    2.4. Use of the 3.4. Use of the Remote Browse Sync parameter

    2.5. Use of WINS3.5. Use of WINS

    Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly @@ -509,14 +574,50 @@ CLASS="APPLICATION" >

    3.5.1. WINS Replication

    Samba-3 permits WINS replication through the use of the wrepld utility. +This tool is not currently capable of being used as it is still in active development. +As soon as this tool becomes moderately functional we will prepare man pages and enhance this +section of the documentation to provide usage and technical details.

    3.5.2. Static WINS Entries

    New to Samba-3 is a tool called winsedit that may be used to add +static WINS entries to the WINS database. This tool can be used also to modify entries +existing in the WINS database.

    The development of the winsedit tool was made necessary due to the migration +of the older style wins.dat file into a new tdb binary backend data store.

    2.6. Do NOT use more than one (1) protocol on MS Windows machines3.6. Do NOT use more than one (1) protocol on MS Windows machines

    A very common cause of browsing problems results from installing more than @@ -558,8 +659,8 @@ CLASS="SECT1" >

    2.7. Name Resolution Order3.7. Name Resolution Order

    Resolution of NetBIOS names to IP addresses can take place using a number diff --git a/docs/htmldocs/bugreport.html b/docs/htmldocs/bugreport.html index 516d187e6a..9aa2fcfe2a 100644 --- a/docs/htmldocs/bugreport.html +++ b/docs/htmldocs/bugreport.html @@ -13,11 +13,8 @@ REL="UP" TITLE="Appendixes" HREF="appendixes.html">PrevNext 

    Chapter 32. Reporting Bugs

    Chapter 35. Reporting Bugs

    32.1. Introduction35.1. Introduction

    The email address for bug reports for stable releases is

    32.2. General info35.2. General info

    Before submitting a bug report check your config for silly @@ -149,8 +181,8 @@ CLASS="SECT1" >

    32.3. Debug levels35.3. Debug levels

    If the bug has anything to do with Samba behaving incorrectly as a @@ -231,8 +263,8 @@ CLASS="SECT1" >

    32.4. Internal errors35.4. Internal errors

    If you get a "INTERNAL ERROR" message in your log files it means that @@ -287,8 +319,8 @@ CLASS="SECT1" >

    32.5. Attaching to a running process35.5. Attaching to a running process

    Unfortunately some unixes (in particular some recent linux kernels) @@ -319,8 +351,8 @@ CLASS="SECT1" >

    32.6. Patches35.6. Patches

    The best sort of bug report is one that includes a fix! If you send us @@ -352,7 +384,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" >PrevNext How to compile SAMBAAnalysing and solving samba problemsThe samba checklist 

    PrevNextChapter 31. How to compile SAMBAChapter 27. How to compile SAMBA

    You can obtain the samba source from the samba website. To obtain a development version, -you can download samba from CVS or using rsync.

    31.1. Access Samba source code via CVS27.1. Access Samba source code via CVS

    31.1.1. Introduction27.1.1. Introduction

    Samba is developed in an open environment. Developers use CVS @@ -117,8 +193,8 @@ CLASS="SECT2" >

    31.1.2. CVS Access to samba.org27.1.2. CVS Access to samba.org

    The machine samba.org runs a publicly accessible CVS @@ -130,8 +206,8 @@ CLASS="SECT3" >

    31.1.2.1. Access via CVSweb27.1.2.1. Access via CVSweb

    You can access the source code via your @@ -151,8 +227,8 @@ CLASS="SECT3" >

    31.1.2.2. Access via cvs27.1.2.2. Access via cvs

    You can also access the source code via a @@ -256,8 +332,8 @@ CLASS="SECT1" >

    31.2. Accessing the samba sources via rsync and ftp27.2. Accessing the samba sources via rsync and ftp

    pserver.samba.org also exports unpacked copies of most parts of the CVS tree at

    31.3. Building the Binaries27.3. Verifying Samba's PGP signature

    In these days of insecurity, it's strongly recommended that you verify the PGP signature for any +source file before installing it. According to Jerry Carter of the Samba Team, only about 22% of +all Samba downloads have had a corresponding PGP signature download (a very low percentage, which +should be considered a bad thing). Even if you're not downloading from a mirror site, verifying PGP +signatures should be a standard reflex.

    With that said, go ahead and download the following files:

         $ wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc
+     $ wget http://us1.samba.org/samba/ftp/samba-pubkey.asc

    The first file is the PGP signature for the Samba source file; the other is the Samba public +PGP key itself. Import the public PGP key with:

         $ gpg --import samba-pubkey.asc

    And verify the Samba source code integrity with:

         $ gzip -d samba-2.2.8a.tar.gz
+     $ gpg --verify samba-2.2.8a.tar.asc

    If you receive a message like, "Good signature from Samba Distribution Verification Key..." +then all is well. The warnings about trust relationships can be ignored. An example of what +you would not want to see would be:

         gpg: BAD signature from "Samba Distribution Verification Key"

    27.4. Building the Binaries

    To do this, first run the program

    31.3.1. Compiling samba with Active Directory support27.4.1. Compiling samba with Active Directory support

    In order to compile samba with ADS support, you need to have installed @@ -393,9 +511,7 @@ BORDER="0" >

    - -

    If your kerberos libraries are in a non-standard location then remember to add the configure option --with-krb5=DIR.

    31.3.1.1. Installing the required packages for Debian27.4.1.1. Installing the required packages for Debian

    On Debian you need to install the following packages:

    31.3.1.2. Installing the required packages for RedHat27.4.1.2. Installing the required packages for RedHat

    On RedHat this means you should have at least:

    31.4. Starting the smbd and nmbd27.5. Starting the smbd and nmbd

    You must choose to start smbd and nmbd either @@ -533,8 +649,8 @@ CLASS="SECT2" >

    31.4.1. Starting from inetd.conf27.5.1. Starting from inetd.conf

    NOTE; The following will be different if @@ -711,8 +827,8 @@ CLASS="SECT2" >

    31.4.2. Alternative: starting it as a daemon27.5.2. Alternative: starting it as a daemon

    To start the server as a daemon you should create @@ -804,7 +920,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" >PrevNextSamba and other CIFS clientsAppendixesReporting BugsMigration from NT4 PDC to Samba-3 PDC

    Prev Next
    Chapter 33. The samba checklist
    Table of Contents
    33.1. Introduction
    33.2. Assumptions
    33.3. The tests
    33.4. Still having troubles?

    33.1. Introduction

    33.2. Assumptions

    33.3. The tests

    33.4. Still having troubles?

    Try the mailing list or newsgroup, or use the ethereal utility to -sniff the problem. The official samba mailing list can be reached at +>Read the chapter on samba@samba.org. To find -out more about samba and how to subscribe to the mailing list check -out the samba web page at -http://samba.org/samba/

    Analysing and Solving Problems.

    Prev NextReporting BugsSamba performance issues Analysing and solving samba problems
    IP ADDR         NETBIOS NAME   WORKGROUP/OS/VERSION 
---------------------------------------------------------------------- 
-192.168.35.10   MINESET-TEST1  [DMVENGR]
-192.168.35.55   LINUXBOX      *[MYGROUP] [Unix] [Samba 2.0.6]
-192.168.35.56   HERBNT2        [HERB-NT]
-192.168.35.63   GANDALF        [MVENGR] [Unix] [Samba 2.0.5a for IRIX]
-192.168.35.65   SAUNA          [WORKGROUP] [Unix] [Samba 1.9.18p10]
-192.168.35.71   FROGSTAR       [ENGR] [Unix] [Samba 2.0.0 for IRIX]
-192.168.35.78   HERBDHCP1     +[HERB]
-192.168.35.88   SCNT2         +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0]
-192.168.35.93   FROGSTAR-PC    [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager]
-192.168.35.97   HERBNT1       *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0]
     IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION +  --------------------------------------------------------------------- +  192.168.35.10 MINESET-TEST1 [DMVENGR] +  192.168.35.55 LINUXBOX *[MYGROUP] [Unix] [Samba 2.0.6] + 5 192.168.35.56 HERBNT2 [HERB-NT] +  192.168.35.63 GANDALF [MVENGR] [Unix] [Samba 2.0.5a for IRIX] +  192.168.35.65 SAUNA [WORKGROUP] [Unix] [Samba 1.9.18p10] +  192.168.35.71 FROGSTAR [ENGR] [Unix] [Samba 2.0.0 for IRIX] +  192.168.35.78 HERBDHCP1 +[HERB] + 10 192.168.35.88 SCNT2 +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0] +  192.168.35.93 FROGSTAR-PC [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager] +  192.168.35.97 HERBNT1 *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0]
    Chapter 11. Configuring Group MappingChapter 12. Configuring Group Mapping

    Starting with Samba 3.0 alpha 2, a new group mapping function is available. The diff --git a/docs/htmldocs/improved-browsing.html b/docs/htmldocs/improved-browsing.html index 3817bbece8..6a7aaf6081 100644 --- a/docs/htmldocs/improved-browsing.html +++ b/docs/htmldocs/improved-browsing.html @@ -74,14 +74,78 @@ CLASS="CHAPTER" >Chapter 23. Improved browsing in sambaChapter 24. Improved browsing in samba

    23.1. Overview of browsing24.1. Overview of browsing

    SMB networking provides a mechanism by which clients can access a list @@ -112,8 +176,8 @@ CLASS="SECT1" >

    23.2. Browsing support in samba24.2. Browsing support in samba

    Samba facilitates browsing. The browsing is supported by

    23.3. Problem resolution24.3. Problem resolution

    If something doesn't work then hopefully the log.nmb file will help @@ -250,8 +314,8 @@ CLASS="SECT1" >

    23.4. Browsing across subnets24.4. Browsing across subnets

    Since the release of Samba 1.9.17(alpha1) Samba has been @@ -284,8 +348,8 @@ CLASS="SECT2" >

    23.4.1. How does cross subnet browsing work ?24.4.1. How does cross subnet browsing work ?

    Cross subnet browsing is a complicated dance, containing multiple @@ -495,8 +559,8 @@ CLASS="SECT1" >

    23.5. Setting up a WINS server24.5. Setting up a WINS server

    Either a Samba machine or a Windows NT Server machine may be set up @@ -590,8 +654,8 @@ CLASS="SECT1" >

    23.6. Setting up Browsing in a WORKGROUP24.6. Setting up Browsing in a WORKGROUP

    To set up cross subnet browsing on a network containing machines @@ -700,8 +764,8 @@ CLASS="SECT1" >

    23.7. Setting up Browsing in a DOMAIN24.7. Setting up Browsing in a DOMAIN

    If you are adding Samba servers to a Windows NT Domain then @@ -775,7 +839,7 @@ CLASS="SECT1" CLASS="SECT1" >23.8. Forcing samba to be the master24.8. Forcing samba to be the master

    Who becomes the

    23.9. Making samba the domain master24.9. Making samba the domain master

    The domain master is responsible for collating the browse lists of @@ -934,8 +998,8 @@ CLASS="SECT1" >

    23.10. Note about broadcast addresses24.10. Note about broadcast addresses

    If your network uses a "0" based broadcast address (for example if it @@ -948,8 +1012,8 @@ CLASS="SECT1" >

    23.11. Multiple interfaces24.11. Multiple interfaces

    Samba now supports machines with multiple network interfaces. If you diff --git a/docs/htmldocs/install.html b/docs/htmldocs/install.html index cc2674ea1c..54d10859f5 100644 --- a/docs/htmldocs/install.html +++ b/docs/htmldocs/install.html @@ -13,8 +13,8 @@ REL="UP" TITLE="General installation" HREF="introduction.html">PrevChapter 1. How to Install and Test SAMBAChapter 2. How to Install and Test SAMBA

    1.1. Obtaining and installing samba2.1. Obtaining and installing samba

    Binary packages of samba are included in almost any Linux or @@ -104,8 +176,8 @@ CLASS="SECT1" >

    1.2. Configuring samba2.2. Configuring samba

    Samba's configuration is stored in the smb.conf file, @@ -125,8 +197,8 @@ CLASS="SECT2" >

    1.2.1. Editing the 2.2.1. Editing the smb.conf file

    1.2.1.1. Test your config file with +NAME="AEN215" +>2.2.1.1. Test your config file with testparm

    1.2.2. SWAT2.2.2. SWAT

    SWAT is a web-based interface that helps you configure samba. @@ -248,8 +320,8 @@ CLASS="SECT1" >

    1.3. Try listing the shares available on your +NAME="AEN230" +>2.3. Try listing the shares available on your server

    1.4. Try connecting with the unix client2.4. Try connecting with the unix client

    1.5. Try connecting from a DOS, WfWg, Win9x, WinNT, +NAME="AEN260" +>2.5. Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client

    1.6. What If Things Don't Work?2.6. What If Things Don't Work?

    Then you might read the file chapter @@ -405,29 +477,20 @@ NAME="AEN150" HREF="diagnosis.html" >Diagnosis and the - FAQ. If you are still stuck then try the mailing list or - newsgroup (look in the README for details). Samba has been - successfully installed at thousands of sites worldwide, so maybe - someone else has hit your problem and has overcome it. You could - also use the WWW site to scan back issues of the samba-digest.

    When you fix the problem please send some - updates of the documentation (or source code) to one of - the documentation maintainers or the list. -

    Analysing and Solving Problems chapter + Samba has been successfully installed at thousands of sites worldwide, + so maybe someone else has hit your problem and has overcome it.

    1.6.1. Scope IDs2.6.1. Scope IDs

    By default Samba uses a blank scope ID. This means @@ -442,8 +505,8 @@ CLASS="SECT2" >

    1.6.2. Locking2.6.2. Locking

    One area which sometimes causes trouble is locking.

    PrevGeneral installationIntroduction to SambaChapter 22. Integrating MS Windows networks with Samba

    Chapter 23. Integrating MS Windows networks with Samba

    This section deals with NetBIOS over TCP/IP name to IP address resolution. If you your MS Windows clients are NOT configured to use NetBIOS over TCP/IP then this @@ -155,8 +239,8 @@ CLASS="SECT1" >

    22.1. Name Resolution in a pure Unix/Linux world23.1. Name Resolution in a pure Unix/Linux world

    The key configuration files covered in this section are:

    22.1.1. 23.1.1. /etc/hosts

    22.1.2. 23.1.2. /etc/resolv.conf

    22.1.3. 23.1.3. /etc/host.conf

    22.1.4. 23.1.4. /etc/nsswitch.conf

    22.2. Name resolution as used within MS Windows networking23.2. Name resolution as used within MS Windows networking

    MS Windows networking is predicated about the name each machine @@ -499,8 +583,8 @@ CLASS="SECT2" >

    22.2.1. The NetBIOS Name Cache23.2.1. The NetBIOS Name Cache

    All MS Windows machines employ an in memory buffer in which is @@ -526,8 +610,8 @@ CLASS="SECT2" >

    22.2.2. The LMHOSTS file23.2.2. The LMHOSTS file

    This file is usually located in MS Windows NT 4.0 or @@ -629,8 +713,8 @@ CLASS="SECT2" >

    22.2.3. HOSTS file23.2.3. HOSTS file

    This file is usually located in MS Windows NT 4.0 or 2000 in @@ -651,8 +735,8 @@ CLASS="SECT2" >

    22.2.4. DNS Lookup23.2.4. DNS Lookup

    This capability is configured in the TCP/IP setup area in the network @@ -671,8 +755,8 @@ CLASS="SECT2" >

    22.2.5. WINS Lookup23.2.5. WINS Lookup

    A WINS (Windows Internet Name Server) service is the equivaent of the diff --git a/docs/htmldocs/introduction.html b/docs/htmldocs/introduction.html index e16808e8f3..f45e60b5c5 100644 --- a/docs/htmldocs/introduction.html +++ b/docs/htmldocs/introduction.html @@ -13,8 +13,8 @@ REL="PREVIOUS" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html">Next

    I. General installation

    Introduction

    Table of Contents
    1. How to Install and Test SAMBA
    1.1. Obtaining and installing samba
    1.2. Configuring samba
    1.2.1. Editing the smb.conf file
    1.2.2. SWAT
    1.3. Try listing the shares available on your - server
    1.4. Try connecting with the unix client
    1.5. Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client
    1.6. What If Things Don't Work?
    1.6.1. Scope IDs
    1.6.2. Locking
    2. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide
    2.1. Discussion
    2.2. How browsing functions and how to deploy stable and -dependable browsing using Samba
    2.3. Use of the Remote Announce parameter
    2.4. Use of the Remote Browse Sync parameter
    2.5. Use of WINS
    2.6. Do NOT use more than one (1) protocol on MS Windows machines
    2.7. Name Resolution Order
    3. User information database
    3.1. Introduction
    3.2. Important Notes About Security
    3.2.1. Advantages of SMB Encryption
    3.2.2. Advantages of non-encrypted passwords
    3.3. The smbpasswd Command
    3.4. Plain text
    3.5. TDB
    3.6. LDAP
    3.6.1. Introduction
    3.6.2. Introduction
    3.6.3. Supported LDAP Servers
    3.6.4. Schema and Relationship to the RFC 2307 posixAccount
    3.6.5. Configuring Samba with LDAP
    3.6.6. Accounts and Groups management
    3.6.7. Security and sambaAccount
    3.6.8. LDAP specials attributes for sambaAccounts
    3.6.9. Example LDIF Entries for a sambaAccount
    3.7. MySQL
    3.7.1. Creating the database
    3.7.2. Configuring
    3.7.3. Using plaintext passwords or encrypted password
    3.7.4. Getting non-column data from the table
    3.8. XML
    NextHow to Install and Test SAMBAIntroduction to Samba
    Chapter 21. Hosting a Microsoft Distributed File System tree on SambaChapter 22. Hosting a Microsoft Distributed File System tree on Samba

    21.1. Instructions22.1. Instructions

    The Distributed File System (or Dfs) provides a means of @@ -212,8 +212,8 @@ CLASS="SECT2" >

    21.1.1. Notes22.1.1. Notes

    Name

    net -- Tool for administration of Samba and remote - CIFS servers.
    net {<ads|rap|rpc>} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address] [-p port] [-n myname] [-s conffile] [-S server] [-C comment] [-M maxusers] [-F flags] [-j jobid] [-l] [-r] [-f] [-t timeout] [-P] [-D debuglevel]

    {<ads|rap|rpc>} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address] [-p port] [-n myname] [-s conffile] [-S server] [-l] [-P] [-D debuglevel]

    DESCRIPTION

    suite.

    The samba net utility is meant to work just like the net utility - available for windows and DOS.

    OPTIONS

    -h
    -h|--help

    Display summary of all available options. - -

    Print a summary of command line options.

    -w target-workgroup

    IP address of target server to use. You have to - specify either this option or a target workgroup or a target server. + specify either this option or a target workgroup or + a target server.

    -p port

    Port on the target server to connect to. +> Port on the target server to connect to (usually 139 or 445). + Defaults to trying 445 first, then 139.

    -n myname
    -n <primary NetBIOS name>

    Sets name of the client. -

    This option allows you to override +the NetBIOS name that Samba uses for itself. This is identical +to setting the NetBIOS +name parameter in the smb.conf(5) file. However, a command +line setting will take precedence over settings in +smb.conf(5).

    -s conffile
    -s <configuration file>

    Specify alternative configuration file that should be loaded. -

    The file specified contains the +configuration details required by the server. The +information in this file includes server-specific +information such as what printcap file to use, as well +as descriptions of all the services that the server is +to provide. See smb.conf(5) for more information. +The default configuration file name is determined at +compile time.

    -S server
    -C comment

    FIXME -

    -M maxusers

    FIXME -

    -F flags

    FIXME -

    -j jobid

    FIXME -

    -l

    FIXME +> When listing data, give more information on each item.

    -r
    -P

    FIXME +> Make queries to the external server using the machine account of the local server.

    -f
    -d|--debug=debuglevel

    FIXME -

    -t timeout
    debuglevel is an integer +from 0 to 10. The default value if this parameter is +not specified is zero.

    FIXME -

    -P
    The higher this value, the more detail will be +logged to the log files about the activities of the +server. At level 0, only critical errors and serious +warnings will be logged. Level 1 is a reasonable level for +day to day running - it generates a small amount of +information about operations carried out.

    Make queries to the external server using the machine account of the local server. -

    -D debuglevel
    Levels above 1 will generate considerable +amounts of log data, and should only be used when +investigating a problem. Levels above 3 are designed for +use only by developers and generate HUGE amounts of log +data, most of which is extremely cryptic.

    set the debuglevel. Debug level 0 is the lowest - and 100 being the highest. This should be set to 100 if you are - planning on submitting a bug report to the Samba team (see - Note that specifying this parameter here will +override the log +level parameter in the BUGS.txt). -

    smb.conf(5) file.

    TIME

    COMMANDS

    TIME

    The NET TIME command allows you to view the time on a remote server or synchronise the time on the local server with the time on the remote server.

    TIME

    Without any options, the Without any options, the NET TIME command - displays the time on the remote server. -

    SYSTEM

    TIME SYSTEM

    Displays the time on the remote server in a format ready for Displays the time on the remote server in a format ready for /bin/date -

    SET

    TIME SET

    Tries to set the date and time of the local server to that on - the remote server using Tries to set the date and time of the local server to that on +the remote server using /bin/date. -

    ZONE
    .

    TIME ZONE

    Displays the timezone in hours from GMT on the remote computer. -

    Displays the timezone in hours from GMT on the remote computer.

    RPC

    [RPC|ADS] JOIN [TYPE] [-U username[%password]] [options]

    The NET RPC command allows you to do various - NT4 operations.

    Join a domain. If the account already exists on the server, and +[TYPE] is MEMBER, the machine will attempt to join automatically. +(Assuming that the machine has been created in server manager) +Otherwise, a password will be prompted for, and a new account may +be created.

    [TYPE] may be PDC, BDC or MEMBER to specify the type of server +joining the domain.

    JOIN -U username[%password] [options]

    [RPC] OLDJOIN [options]

    Join a domain with specified username and password. Password - will be prompted if none is specified.

    JOIN [options except -U]
    Join a domain. Use the OLDJOIN option to join the domain +using the old style of domain joining - you need to create a trust +account in server manager first.

    [RPC|ADS] USER

    [RPC|ADS] USER DELETE target

    to join a domain created in server manager -

    USER [misc. options] [targets]
    Delete specified user

    [RPC|ADS] USER LIST

    List users -

    USER DELETE <name> [misc options]
    List all users

    [RPC|ADS] USER INFO target

    delete specified user -

    USER INFO <name> [misc options]
    List the domain groups of a the specified user.

    [RPC|ADS] USER ADD name [password] [-F user flags] [-C comment]

    list the domain groups of the specified user -

    USER ADD <name> [password] [-F user flags] [misc. options]
    Add specified user.

    [RPC|ADS] GROUP

    [RPC|ADS] GROUP [misc options] [targets]

    Add specified user -

    GROUP [misc options] [targets]
    List user groups.

    [RPC|ADS] GROUP DELETE name [misc. options]

    List user groups -

    GROUP DELETE <name> [misc. options] [targets]
    Delete specified group.

    [RPC|ADS] GROUP ADD name [-C comment]

    Delete specified group -

    GROUP ADD <name> [-C comment]
    Create specified group.

    [RAP|RPC] SHARE

    [RAP|RPC] SHARE [misc. options] [targets]

    Create specified group -

    SHARE [misc. options] [targets]
    Enumerates all exported resources (network shares) on target server.

    [RAP|RPC] SHARE ADD name=serverpath [-C comment] [-M maxusers] [targets]

    enumerates all exported resources (network shares) on target server -

    SHARE ADD <name=serverpath> [misc. options] [targets]
    Adds a share from a server (makes the export active). Maxusers +specifies the number of users that can be connected to the +share simultaneously.

    SHARE DELETE sharenam

    Adds a share from a server (makes the export active) -

    SHARE DELETE <sharenam
    Delete specified share.

    [RPC|RAP] FILE

    [RPC|RAP] FILE

    List all open files on remote server.

    [RPC|RAP] FILE CLOSE fileid

    Close file with specified fileid on +remote server.

    [RPC|RAP] FILE INFO fileid

    Print information on specified fileid. +Currently listed are: file-id, username, locks, path, permissions.

    [RAP|RPC] FILE USER

    Currently NOT implemented.

    VERSION

    SESSION

    RAP SESSION

    This man page is incomplete for version 3.0 of the Samba - suite.

    Without any other options, SESSION enumerates all active SMB/CIFS +sessions on the target server.

    RAP SESSION DELETE|CLOSE CLIENT_NAME

    Close the specified sessions.

    RAP SESSION INFO CLIENT_NAME

    Give a list with all the open files in specified session.

    RAP SERVER DOMAIN

    List all servers in specified domain or workgroup. Defaults +to local domain.

    RAP DOMAIN

    Lists all domains and workgroups visible on the +current network.

    RAP PRINTQ

    RAP PRINTQ LIST QUEUE_NAME

    Lists the specified print queue and print jobs on the server. +If the QUEUE_NAME is omitted, all +queues are listed.

    RAP PRINTQ DELETE JOBID

    Delete job with specified id.

    RAP VALIDATE user [password]

    Validate whether the specified user can log in to the +remote server. If the password is not specified on the commandline, it +will be prompted.

    Currently NOT implemented.

    RAP GROUPMEMBER

    RAP GROUPMEMBER LIST GROUP

    List all members of the specified group.

    RAP GROUPMEMBER DELETE GROUP USER

    Delete member from group.

    RAP GROUPMEMBER ADD GROUP USER

    Add member to group.

    RAP ADMIN command

    Execute the specified command on +the remote server. Only works with OS/2 servers.

    Currently NOT implemented.

    RAP SERVICE

    RAP SERVICE START NAME [arguments...]

    Start the specified service on the remote server. Not implemented yet.

    Currently NOT implemented.

    RAP SERVICE STOP

    Stop the specified service on the remote server.

    Currently NOT implemented.

    RAP PASSWORD USER OLDPASS NEWPASS

    Change password of USER from OLDPASS to NEWPASS.

    LOOKUP

    LOOKUP HOST HOSTNAME [TYPE]

    Lookup the IP address of the given host with the specified type (netbios suffix). +The type defaults to 0x20 (workstation).

    LOOKUP LDAP [DOMAIN

    Give IP address of LDAP server of specified DOMAIN. Defaults to local domain.

    LOOKUP KDC [REALM]

    Give IP address of KDC for the specified REALM. +Defaults to local realm.

    LOOKUP DC [DOMAIN]

    Give IP's of Domain Controllers for specified DOMAIN. Defaults to local domain.

    LOOKUP MASTER DOMAIN

    Give IP of master browser for specified DOMAIN +or workgroup. Defaults to local domain.

    CACHE

    Samba uses a general caching interface called 'gencache'. It +can be controlled using 'NET CACHE'.

    All the timeout parameters support the suffixes: + +

    s - Seconds
    m - Minutes
    h - Hours
    d - Days
    w - Weeks

    CACHE ADD key data time-out

    Add specified key+data to the cache with the given timeout.

    CACHE DEL key

    Delete key from the cache.

    CACHE SET key data time-out

    Update data of existing cache entry.

    CACHE SEARCH PATTERN

    Search for the specified pattern in the cache data.

    CACHE LIST

    List all current items in the cache.

    CACHE FLUSH

    Remove all the current items from the cache.

    GETLOCALSID [DOMAIN]

    Print the SID of the specified domain, or if the parameter is +omitted, the SID of the domain the local server is in.

    SETLOCALSID S-1-5-21-x-y-z

    Sets domain sid for the local server to the specified SID.

    MAXRID

    Prints out the highest RID currently in use on the local +server (by the active 'passdb backend').

    RPC INFO

    Print information about the domain of the remote server, +such as domain name, domain sid and number of users and groups.

    [RPC|ADS] TESTJOIN

    Check whether participation in a domain is still valid.

    [RPC|ADS] CHANGETRUSTPW

    Force change of domain trust password.

    RPC TRUSTDOM

    RPC TRUSTDOM ADD DOMAIN

    Add a interdomain trust account for +DOMAIN to the remote server.

    RPC TRUSTDOM DEL DOMAIM

    Remove interdomain trust account for +DOMAIN from the remote server.

    Currently NOT implemented.

    RPC TRUSTDOM ESTABLISH DOMAIN

    Establish a trust relationship to a trusting domain. +Interdomain account must already be created on the remote PDC.

    RPC TRUSTDOM REVOKE DOMAIN

    Abandon relationship to trusted domain

    RPC TRUSTDOM LIST

    List all current interdomain trust relationships.

    RPC ABORTSHUTDOWN

    Abort the shutdown of a remote server.

    SHUTDOWN [-t timeout] [-r] [-f] [-C message]

    Shut down the remote server.

    -r

    Reboot after shutdown.

    -f

    Force shutting down all applications.

    -t timeout

    Timeout before system will be shut down. An interactive +user of the system can use this time to cancel the shutdown.

    -C message

    Display the specified message on the screen to +announce the shutdown.

    SAMDUMP

    Print out sam database of remote server. You need +to run this on either a BDC.

    VAMPIRE

    Export users, aliases and groups from remote server to +local server. Can only be run an a BDC.

    GETSID

    Fetch domain SID and store it in the local secrets.tdb.

    ADS LEAVE

    Make the remote host leave the domain it is part of.

    ADS STATUS

    Print out status of machine account of the local machine in ADS. +Prints out quite some debug info. Aimed at developers, regular +users should use NET ADS TESTJOIN.

    ADS PRINTER

    ADS PRINTER INFO [PRINTER] [SERVER]

    Lookup info for PRINTER on SERVER. The printer name defaults to "*", the +server name defaults to the local host.

    ADS PRINTER PUBLISH PRINTER

    Publish specified printer using ADS.

    ADS PRINTER REMOVE PRINTER

    Remove specified printer from ADS directory.

    ADS SEARCH EXPRESSION ATTRIBUTES...

    Perform a raw LDAP search on a ADS server and dump the results. The +expression is a standard LDAP search expression, and the +attributes are a list of LDAP fields to show in the results.

    Example: net ads search '(objectCategory=group)' sAMAccountName

    ADS DN DN (attributes)

    Perform a raw LDAP search on a ADS server and dump the results. The +DN standard LDAP DN, and the attributes are a list of LDAP fields +to show in the result.

    Example: net ads dn 'CN=administrator,CN=Users,DC=my,DC=domain' SAMAccountName

    WORKGROUP

    Print out workgroup name for specified kerberos realm.

    HELP [COMMAND]

    Gives usage information for the specified command.

    VERSION

    This man page is incomplete for version 3.0 of the Samba + suite.

    AUTHOR

    The original Samba man pages were written by Karl Auer. - The current set of manpages and documentation is maintained - by the Samba Team in the same fashion as the Samba source code.

    The net manpage was written by Jelmer Vernooij.

    Prev

    III. Advanced Configuration

    Introduction

    Samba has several features that you might want or might not want to use. The chapters in this part each cover one specific feature.

    Table of Contents
    10. UNIX Permission Bits and Windows NT Access Control Lists
    10.1. Viewing and changing UNIX permissions using the NT - security dialogs
    10.2. How to view file security on a Samba share
    10.3. Viewing file ownership
    10.4. Viewing file or directory permissions
    10.4.1. File Permissions
    10.4.2. Directory Permissions
    10.5. Modifying file or directory permissions
    10.6. Interaction with the standard Samba create mask - parameters
    10.7. Interaction with the standard Samba file attribute - mapping
    11. Configuring Group Mapping
    12. Printing Support
    12.1. Introduction
    12.2. Configuration
    12.2.1. Creating [print$]
    12.2.2. Setting Drivers for Existing Printers
    12.2.3. Support a large number of printers
    12.2.4. Adding New Printers via the Windows NT APW
    12.2.5. Samba and Printer Ports
    12.3. The Imprints Toolset
    12.3.1. What is Imprints?
    12.3.2. Creating Printer Driver Packages
    12.3.3. The Imprints server
    12.3.4. The Installation Client
    12.4. Diagnosis
    12.4.1. Introduction
    12.4.2. Debugging printer problems
    12.4.3. What printers do I have?
    12.4.4. Setting up printcap and print servers
    12.4.5. Job sent, no output
    12.4.6. Job sent, strange output
    12.4.7. Raw PostScript printed
    12.4.8. Advanced Printing
    12.4.9. Real debugging
    13. CUPS Printing Support
    13.1. Introduction
    13.2. Configuring smb.conf for CUPS
    13.3. CUPS - RAW Print Through Mode
    13.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe -PostScript driver with CUPS-PPDs downloaded to clients
    13.5. Windows Terminal Servers (WTS) as CUPS clients
    13.6. Setting up CUPS for driver download
    13.7. Sources of CUPS drivers / PPDs
    13.7.1. cupsaddsmb
    13.8. The CUPS Filter Chains
    13.9. CUPS Print Drivers and Devices
    13.9.1. Further printing steps
    13.10. Limiting the number of pages users can print
    13.11. Advanced Postscript Printing from MS Windows
    13.12. Auto-Deletion of CUPS spool files
    14. Unified Logons between Windows NT and UNIX using Winbind
    14.1. Abstract
    14.2. Introduction
    14.3. What Winbind Provides
    14.3.1. Target Uses
    14.4. How Winbind Works
    14.4.1. Microsoft Remote Procedure Calls
    14.4.2. Microsoft Active Directory Services
    14.4.3. Name Service Switch
    14.4.4. Pluggable Authentication Modules
    14.4.5. User and Group ID Allocation
    14.4.6. Result Caching
    14.5. Installation and Configuration
    14.5.1. Introduction
    14.5.2. Requirements
    14.5.3. Testing Things Out
    14.6. Limitations
    14.7. Conclusion
    15. Advanced Network Manangement
    15.1. Configuring Samba Share Access Controls
    15.1.1. Share Permissions Management
    15.2. Remote Server Administration
    15.3. Network Logon Script Magic
    16. System and Account Policies
    16.1. Creating and Managing System Policies
    16.1.1. Windows 9x/Me Policies
    16.1.2. Windows NT4 Style Policy Files
    16.1.3. MS Windows 200x / XP Professional Policies
    16.2. Managing Account/User Policies
    16.2.1. With Windows NT4/200x
    16.2.2. With a Samba PDC
    17. Desktop Profile Management
    17.1. Roaming Profiles
    17.1.1. Samba Configuration for Profile Handling
    17.1.2. Windows Client Profile Configuration Information
    17.1.3. Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    17.1.4. Profile Migration from Windows NT4/200x Server to Samba
    17.2. Mandatory profiles
    17.3. Creating/Managing Group Profiles
    17.4. Default Profile for Windows Users
    17.4.1. MS Windows 9x/Me
    17.4.2. MS Windows NT4 Workstation
    17.4.3. MS Windows 200x/XP
    18. Interdomain Trust Relationships
    18.1. Trust Relationship Background
    18.2. MS Windows NT4 Trust Configuration
    18.2.1. NT4 as the Trusting Domain
    18.2.2. NT4 as the Trusted Domain
    18.3. Configuring Samba Domain Trusts
    18.3.1. Samba3 as the Trusting Domain
    18.3.2. Samba3 as the Trusted Domain
    19. PAM Configuration for Centrally Managed Authentication
    19.1. Samba and PAM
    19.2. Distributed Authentication
    19.3. PAM Configuration in smb.conf
    20. Stackable VFS modules
    20.1. Introduction and configuration
    20.2. Included modules
    20.2.1. audit
    20.2.2. extd_audit
    20.2.3. recycle
    20.2.4. netatalk
    20.3. VFS modules available elsewhere
    20.3.1. DatabaseFS
    20.3.2. vscan
    21. Hosting a Microsoft Distributed File System tree on Samba
    21.1. Instructions
    21.1.1. Notes
    22. Integrating MS Windows networks with Samba
    22.1. Name Resolution in a pure Unix/Linux world
    22.1.1. /etc/hosts
    22.1.2. /etc/resolv.conf
    22.1.3. /etc/host.conf
    22.1.4. /etc/nsswitch.conf
    22.2. Name resolution as used within MS Windows networking
    22.2.1. The NetBIOS Name Cache
    22.2.2. The LMHOSTS file
    22.2.3. HOSTS file
    22.2.4. DNS Lookup
    22.2.5. WINS Lookup
    23. Improved browsing in samba
    23.1. Overview of browsing
    23.2. Browsing support in samba
    23.3. Problem resolution
    23.4. Browsing across subnets
    23.4.1. How does cross subnet browsing work ?
    23.5. Setting up a WINS server
    23.6. Setting up Browsing in a WORKGROUP
    23.7. Setting up Browsing in a DOMAIN
    23.8. Forcing samba to be the master
    23.9. Making samba the domain master
    23.10. Note about broadcast addresses
    23.11. Multiple interfaces
    24. Securing Samba
    24.1. Introduction
    24.2. Using host based protection
    24.3. Using interface protection
    24.4. Using a firewall
    24.5. Using a IPC$ share deny
    24.6. Upgrading Samba
    25. Unicode/Charsets
    25.1. What are charsets and unicode?
    25.2. Samba and charsets
    PrevNextChapter 30. Samba and other CIFS clients

    This chapter contains client-specific information.

    30.1. Macintosh clients?

    30.2. OS2 Client

    30.2.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?

    30.2.2. How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?

    30.2.3. Are there any other issues when OS/2 (any version) is used as a client?

    30.2.4. How do I get printer driver download working for OS/2 clients?

    30.3. Windows for Workgroups

    30.3.1. Use latest TCP/IP stack from Microsoft

    30.3.2. Delete .pwl files after password change

    30.3.3. Configure WfW password handling

    30.3.4. Case handling of passwords

    30.3.5. Use TCP/IP as default protocol

    30.4. Windows '95/'98

    30.5. Windows 2000 Service Pack 2

    30.6. Windows NT 3.1

    NextHow to compile SAMBASWAT - The Samba Web Admininistration Tool

    Chapter 19. PAM Configuration for Centrally Managed AuthenticationChapter 20. PAM Configuration for Centrally Managed Authentication

    19.1. Samba and PAM20.1. Samba and PAM

    A number of Unix systems (eg: Sun Solaris), as well as the @@ -363,8 +387,8 @@ CLASS="SECT1" >

    19.2. Distributed Authentication20.2. Distributed Authentication

    The astute administrator will realize from this that the @@ -389,8 +413,8 @@ CLASS="SECT1" >

    19.3. PAM Configuration in smb.conf20.3. PAM Configuration in smb.conf

    There is an option in smb.conf called Chapter 3. User information databaseChapter 4. User information database

    3.1. Introduction4.1. Introduction

    Old windows clients send plain text passwords over the wire. @@ -121,8 +271,8 @@ CLASS="SECT1" >

    3.2. Important Notes About Security4.2. Important Notes About Security

    The unix and SMB password encryption techniques seem similar @@ -248,44 +398,62 @@ BORDER="0" >

    Note :All current release of - Microsoft SMB/CIFS clients support authentication via the - SMB Challenge/Response mechanism described here. Enabling - clear text authentication does not disable the ability - of the client to participate in encrypted authentication.

    MS Windows clients will cache the encrypted password alone. - Even when plain text passwords are re-enabled, through the appropriate - registry change, the plain text password is NEVER cached. This means that - in the event that a network connections should become disconnected (broken) - only the cached (encrypted) password will be sent to the resource server - to affect a auto-reconnect. If the resource server does not support encrypted - passwords the auto-reconnect will fail. USE OF ENCRYPTED PASSWORDS - IS STRONGLY ADVISED.

    3.2.1. Advantages of SMB Encryption4.2.1. Advantages of SMB Encryption

    3.2.2. Advantages of non-encrypted passwords4.2.2. Advantages of non-encrypted passwords

    3.3. The smbpasswd Command4.3. The smbpasswd Command

    The smbpasswd utility is a utility similar to the @@ -461,8 +629,8 @@ CLASS="SECT1" >

    3.4. Plain text4.4. Plain text

    Older versions of samba retrieved user information from the unix user database @@ -481,8 +649,8 @@ CLASS="SECT1" >

    3.5. TDB4.5. TDB

    Samba can also store the user data in a "TDB" (Trivial Database). Using this backend @@ -494,16 +662,16 @@ CLASS="SECT1" >

    3.6. LDAP4.6. LDAP

    3.6.1. Introduction4.6.1. Introduction

    This document describes how to use an LDAP directory for storing Samba user @@ -570,8 +738,8 @@ CLASS="SECT2" >

    3.6.2. Introduction4.6.2. Introduction

    Traditionally, when configuring As a result of these defeciencies, a more robust means of storing user attributes used by smbd was developed. The API which defines access to user accounts is commonly referred to as the samdb interface (previously this was called the passdb -API, and is still so named in the CVS trees). In Samba 2.2.3, enabling support -for a samdb backend (e.g. --with-ldapsam or ---with-tdbsam) requires compile time support.

    When compiling Samba to include the --with-ldapsam autoconf -option, smbd (and associated tools) will store and lookup user accounts in -an LDAP directory. In reality, this is very easy to understand. If you are -comfortable with using an smbpasswd file, simply replace "smbpasswd" with -"LDAP directory" in all the documentation.

    There are a few points to stress about what the --with-ldapsam +>There are a few points to stress about what the ldapsam does not provide. The LDAP support referred to in the this documentation does not include:

    3.6.3. Supported LDAP Servers4.6.3. Supported LDAP Servers

    The LDAP samdb code in 2.2.3 (and later) has been developed and tested @@ -705,8 +853,8 @@ CLASS="SECT2" >

    3.6.4. Schema and Relationship to the RFC 2307 posixAccount4.6.4. Schema and Relationship to the RFC 2307 posixAccount

    Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in @@ -762,16 +910,16 @@ CLASS="SECT2" >

    3.6.5. Configuring Samba with LDAP4.6.5. Configuring Samba with LDAP

    3.6.5.1. OpenLDAP configuration4.6.5.1. OpenLDAP configuration

    To include support for the sambaAccount object in an OpenLDAP directory @@ -817,9 +965,7 @@ include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/samba.schema - -## uncomment this line if you want to support the RFC2307 (NIS) schema -## include /etc/openldap/schema/nis.schema +include /etc/openldap/schema/nis.schema ....

    3.6.5.2. Configuring Samba4.6.5.2. Configuring Samba

    The following parameters are available in smb.conf only with

    3.6.6. Accounts and Groups management4.6.6. Accounts and Groups management

    As users accounts are managed thru the sambaAccount objectclass, you should @@ -993,8 +1139,8 @@ CLASS="SECT2" >

    3.6.7. Security and sambaAccount4.6.7. Security and sambaAccount

    There are two important points to remember when discussing the security @@ -1029,9 +1175,8 @@ CLASS="EMPHASIS" >These password hashes are clear text equivalents and can be used to impersonate the user without deriving the original clear text strings. For more information on the details of LM/NT password hashes, refer to the ENCRYPTION chapterUser Database of the Samba-HOWTO-Collection.

    To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults @@ -1072,8 +1217,8 @@ CLASS="SECT2" >

    3.6.8. LDAP specials attributes for sambaAccounts4.6.8. LDAP specials attributes for sambaAccounts

    The sambaAccount objectclass is composed of the following attributes:

    3.6.9. Example LDIF Entries for a sambaAccount4.6.9. Example LDIF Entries for a sambaAccount

    The following is a working LDIF with the inclusion of the posixAccount objectclass:

    3.7. MySQL4.7. MySQL

    3.7.1. Creating the database4.7.1. Creating the database

    You either can set up your own table and specify the field names to pdb_mysql (see below @@ -1382,8 +1527,8 @@ CLASS="SECT2" >

    3.7.2. Configuring4.7.2. Configuring

    This plugin lacks some good documentation, but here is some short info:

    3.7.3. Using plaintext passwords or encrypted password4.7.3. Using plaintext passwords or encrypted password

    I strongly discourage the use of plaintext passwords, however, you can use them:

    3.7.4. Getting non-column data from the table4.7.4. Getting non-column data from the table

    It is possible to have not all data in the database and making some 'constant'.

    3.8. XML4.8. XML

    This module requires libxml2 to be installed.

    sorce:500:Simo Sorce
-samba:45:Test User
     sorce:500:Simo Sorce +  samba:45:Test User

    ---------------
-username:       sorce
-user ID/Group:  500/500
-user RID/GRID:  2000/2001
-Full Name:      Simo Sorce
-Home Directory: \\BERSERKER\sorce
-HomeDir Drive:  H:
-Logon Script:   \\BERSERKER\netlogon\sorce.bat
-Profile Path:   \\BERSERKER\profile
----------------
-username:       samba
-user ID/Group:  45/45
-user RID/GRID:  1090/1091
-Full Name:      Test User
-Home Directory: \\BERSERKER\samba
-HomeDir Drive:  
-Logon Script:   
-Profile Path:   \\BERSERKER\profile
     --------------- +  username: sorce +  user ID/Group: 500/500 +  user RID/GRID: 2000/2001 + 5 Full Name: Simo Sorce +  Home Directory: \\BERSERKER\sorce +  HomeDir Drive: H: +  Logon Script: \\BERSERKER\netlogon\sorce.bat +  Profile Path: \\BERSERKER\profile + 10 --------------- +  username: samba +  user ID/Group: 45/45 +  user RID/GRID: 1090/1091 +  Full Name: Test User + 15 Home Directory: \\BERSERKER\samba +  HomeDir Drive: +  Logon Script: +  Profile Path: \\BERSERKER\profile

    sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX         ]:LCT-00000000:
-samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX         ]:LCT-3BFA1E8D:
     sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX ]:LCT-00000000: +  samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ]:LCT-3BFA1E8D:
    -u username
    PrevChapter 29. Portability
    Table of Contents
    29.1. HPUX
    29.2. SCO Unix
    29.3. DNIX
    29.4. RedHat Linux Rembrandt-II
    29.5. AIX
    29.6. Solaris

    Samba works on a wide range of platforms but the interface all the platforms provide is not always compatible. This chapter contains @@ -84,7 +123,7 @@ CLASS="SECT1" >

    29.1. HPUX

    29.2. SCO Unix

    29.3. DNIX

    29.4. RedHat Linux Rembrandt-II

    29.5. AIX

    29.5.1. Sequential Read Ahead

    29.6. Solaris

    PrevSamba performance issuesMigration from NT4 PDC to Samba-3 PDCChapter 12. Printing SupportChapter 13. Printing Support

    12.1. Introduction13.1. Introduction

    Beginning with the 2.2.0 release, Samba supports @@ -163,8 +294,8 @@ CLASS="SECT1" >

    12.2. Configuration13.2. Configuration

    12.2.1. Creating [print$]13.2.1. Creating [print$]

    In order to support the uploading of printer driver @@ -442,8 +573,8 @@ CLASS="SECT2" >

    12.2.2. Setting Drivers for Existing Printers13.2.2. Setting Drivers for Existing Printers

    The initial listing of printers in the Samba host's @@ -514,8 +645,8 @@ CLASS="SECT2" >

    12.2.3. Support a large number of printers13.2.3. Support a large number of printers

    One issue that has arisen during the development @@ -590,8 +721,8 @@ CLASS="SECT2" >

    12.2.4. Adding New Printers via the Windows NT APW13.2.4. Adding New Printers via the Windows NT APW

    By default, Samba offers all printer shares defined in

    12.2.5. Samba and Printer Ports13.2.5. Samba and Printer Ports

    Windows NT/2000 print servers associate a port with each printer. These normally @@ -780,8 +911,8 @@ CLASS="SECT1" >

    12.3. The Imprints Toolset13.3. The Imprints Toolset

    The Imprints tool set provides a UNIX equivalent of the @@ -798,8 +929,8 @@ CLASS="SECT2" >

    12.3.1. What is Imprints?13.3.1. What is Imprints?

    Imprints is a collection of tools for supporting the goals @@ -830,8 +961,8 @@ CLASS="SECT2" >

    12.3.2. Creating Printer Driver Packages13.3.2. Creating Printer Driver Packages

    The process of creating printer driver packages is beyond @@ -846,8 +977,8 @@ CLASS="SECT2" >

    12.3.3. The Imprints server13.3.3. The Imprints server

    The Imprints server is really a database server that @@ -870,8 +1001,8 @@ CLASS="SECT2" >

    12.3.4. The Installation Client13.3.4. The Installation Client

    More information regarding the Imprints installation client @@ -964,16 +1095,16 @@ CLASS="SECT1" >

    12.4. Diagnosis13.4. Diagnosis

    12.4.1. Introduction13.4.1. Introduction

    This is a short description of how to debug printing problems with @@ -1047,8 +1178,8 @@ CLASS="SECT2" >

    12.4.2. Debugging printer problems13.4.2. Debugging printer problems

    One way to debug printing problems is to start by replacing these @@ -1104,8 +1235,8 @@ CLASS="SECT2" >

    12.4.3. What printers do I have?13.4.3. What printers do I have?

    You can use the 'testprns' program to check to see if the printer @@ -1133,8 +1264,8 @@ CLASS="SECT2" >

    12.4.4. Setting up printcap and print servers13.4.4. Setting up printcap and print servers

    You may need to set up some printcaps for your Samba system to use. @@ -1217,8 +1348,8 @@ CLASS="SECT2" >

    12.4.5. Job sent, no output13.4.5. Job sent, no output

    This is the most frustrating part of printing. You may have sent the @@ -1262,8 +1393,8 @@ CLASS="SECT2" >

    12.4.6. Job sent, strange output13.4.6. Job sent, strange output

    Once you have the job printing, you can then start worrying about @@ -1308,8 +1439,8 @@ CLASS="SECT2" >

    12.4.7. Raw PostScript printed13.4.7. Raw PostScript printed

    This is a problem that is usually caused by either the print spooling @@ -1323,8 +1454,8 @@ CLASS="SECT2" >

    12.4.8. Advanced Printing13.4.8. Advanced Printing

    Note that you can do some pretty magic things by using your @@ -1339,8 +1470,8 @@ CLASS="SECT2" >

    12.4.9. Real debugging13.4.9. Real debugging

    If the above debug tips don't help, then maybe you need to bring in diff --git a/docs/htmldocs/samba-bdc.html b/docs/htmldocs/samba-bdc.html index 69787dbeaf..618889cab2 100644 --- a/docs/htmldocs/samba-bdc.html +++ b/docs/htmldocs/samba-bdc.html @@ -74,14 +74,76 @@ CLASS="CHAPTER" >Chapter 7. Samba Backup Domain Controller to Samba Domain ControlChapter 8. Samba Backup Domain Controller to Samba Domain Control

    7.1. Prerequisite Reading8.1. Prerequisite Reading

    Before you continue reading in this chapter, please make sure @@ -97,8 +159,8 @@ CLASS="SECT1" >

    7.2. Background8.2. Background

    What is a Domain Controller? It is a machine that is able to answer @@ -142,8 +204,8 @@ CLASS="SECT1" >

    7.3. What qualifies a Domain Controller on the network?8.3. What qualifies a Domain Controller on the network?

    Every machine that is a Domain Controller for the domain SAMBA has to @@ -159,8 +221,8 @@ CLASS="SECT2" >

    7.3.1. How does a Workstation find its domain controller?8.3.1. How does a Workstation find its domain controller?

    A NT workstation in the domain SAMBA that wants a local user to be @@ -178,8 +240,8 @@ CLASS="SECT2" >

    7.3.2. When is the PDC needed?8.3.2. When is the PDC needed?

    Whenever a user wants to change his password, this has to be done on @@ -194,8 +256,8 @@ CLASS="SECT1" >

    7.4. Can Samba be a Backup Domain Controller to an NT PDC?8.4. Can Samba be a Backup Domain Controller to an NT PDC?

    With version 2.2, no. The native NT SAM replication protocols have @@ -217,8 +279,8 @@ CLASS="SECT1" >

    7.5. How do I set up a Samba BDC?8.5. How do I set up a Samba BDC?

    Several things have to be done:

    7.5.1. How do I replicate the smbpasswd file?8.5.1. How do I replicate the smbpasswd file?

    Replication of the smbpasswd file is sensitive. It has to be done @@ -305,8 +367,8 @@ CLASS="SECT2" >

    7.5.2. Can I do this all with LDAP?8.5.2. Can I do this all with LDAP?

    The simple answer is YES. Samba's pdb_ldap code supports diff --git a/docs/htmldocs/samba-howto-collection.html b/docs/htmldocs/samba-howto-collection.html index fae541f90f..1111d86de1 100644 --- a/docs/htmldocs/samba-howto-collection.html +++ b/docs/htmldocs/samba-howto-collection.html @@ -55,10 +55,10 @@ CLASS="EDITEDBY" >Edited by

    John H Terpstra

    Jelmer R. Vernooij

    Jelmer Vernooij

    John H. Terpstra

    Gerald (Jerry) Carter

    This book is a collection of HOWTOs added to Samba documentation over the years. @@ -98,7 +98,7 @@ CLASS="LEGALNOTICE" >

    This documentation is distributed under the GNU General Public License (GPL) @@ -128,141 +128,185 @@ HREF="introduction.html" >

    1. Introduction to Samba
    1.1. Background
    1.2. Terminology
    1.3. Related Projects
    1.4. SMB Methodology
    1.5. Additional Resources
    1.6. Epilogue
    1.7. Miscellaneous
    2. How to Install and Test SAMBA
    1.1. 2.1. Obtaining and installing samba
    1.2. 2.2. Configuring samba
    1.3. 2.3. Try listing the shares available on your server
    1.4. 2.4. Try connecting with the unix client
    1.5. 2.5. Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client
    1.6. 2.6. What If Things Don't Work?
    2. 3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide
    2.1. 3.1. Discussion
    2.2. 3.2. How browsing functions and how to deploy stable and dependable browsing using Samba
    2.3. 3.3. Use of the Remote Announce parameter
    2.4. 3.4. Use of the Remote Browse Sync parameter
    2.5. 3.5. Use of WINS
    2.6. 3.6. Do NOT use more than one (1) protocol on MS Windows machines
    2.7. 3.7. Name Resolution Order
    3. 4. User information database
    3.1. 4.1. Introduction
    3.2. 4.2. Important Notes About Security
    3.3. 4.3. The smbpasswd Command
    3.4. 4.4. Plain text
    3.5. 4.5. TDB
    3.6. 4.6. LDAP
    3.7. 4.7. MySQL
    3.8. 4.8. XML
    4. 5. Nomenclature of Server Types
    4.1. 5.1. Stand Alone Server
    4.2. 5.2. Domain Member Server
    4.3. 5.3. Domain Controller
    5. 6. Samba as Stand-Alone Server
    5.1. 6.1. User and Share security level
    6. 7. Samba as an NT4 or Win2k Primary Domain Controller
    6.1. 7.1. Prerequisite Reading
    6.2. 7.2. Background
    6.3. 7.3. Configuring the Samba Domain Controller
    6.4. 7.4. Creating Machine Trust Accounts and Joining Clients to the Domain
    6.5. 7.5. Common Problems and Errors
    6.6. What other help can I get?
    6.7. 7.6. Domain Control for Windows 9x/ME
    7. 8. Samba Backup Domain Controller to Samba Domain Control
    7.1. 8.1. Prerequisite Reading
    7.2. 8.2. Background
    7.3. 8.3. What qualifies a Domain Controller on the network?
    7.4. 8.4. Can Samba be a Backup Domain Controller to an NT PDC?
    7.5. 8.5. How do I set up a Samba BDC?
    8. 9. Samba as a ADS domain member
    8.1. 9.1. Setup your smb.conf
    8.2. 9.2. Setup your /etc/krb5.conf
    8.3. 9.3. Create the computer account
    8.4. 9.4. Test your server setup
    8.5. 9.5. Testing with
    8.6. 9.6. Notes
    9. 10. Samba as a NT4 or Win2k domain member
    9.1. 10.1. Joining an NT Domain with Samba 3.0
    9.2. 10.2. Why is this better than security = server?
    10. 11. UNIX Permission Bits and Windows NT Access Control Lists
    10.1. 11.1. Viewing and changing UNIX permissions using the NT security dialogs
    10.2. 11.2. How to view file security on a Samba share
    10.3. 11.3. Viewing file ownership
    10.4. 11.4. Viewing file or directory permissions
    10.5. 11.5. Modifying file or directory permissions
    10.6. 11.6. Interaction with the standard Samba create mask parameters
    10.7. 11.7. Interaction with the standard Samba file attribute mapping
    11. 12. Configuring Group Mapping
    12. 13. Printing Support
    12.1. 13.1. Introduction
    12.2. 13.2. Configuration
    12.3. 13.3. The Imprints Toolset
    12.4. 13.4. Diagnosis
    13. 14. CUPS Printing Support
    13.1. 14.1. Introduction
    13.2. 14.2. Configuring smb.conf for CUPS
    13.3. 14.3. CUPS - RAW Print Through Mode
    13.4. 14.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe PostScript driver with CUPS-PPDs downloaded to clients
    13.5. 14.5. Windows Terminal Servers (WTS) as CUPS clients
    13.6. 14.6. Setting up CUPS for driver download
    13.7. 14.7. Sources of CUPS drivers / PPDs
    13.8. 14.8. The CUPS Filter Chains
    13.9. 14.9. CUPS Print Drivers and Devices
    13.10. 14.10. Limiting the number of pages users can print
    13.11. 14.11. Advanced Postscript Printing from MS Windows
    13.12. 14.12. Auto-Deletion of CUPS spool files
    14. 15. Unified Logons between Windows NT and UNIX using Winbind
    14.1. 15.1. Abstract
    14.2. 15.2. Introduction
    14.3. 15.3. What Winbind Provides
    14.4. 15.4. How Winbind Works
    14.5. 15.5. Installation and Configuration
    14.6. 15.6. Limitations
    14.7. 15.7. Conclusion
    15. 16. Advanced Network Manangement
    15.1. 16.1. Configuring Samba Share Access Controls
    15.2. 16.2. Remote Server Administration
    15.3. 16.3. Network Logon Script Magic
    16. 17. System and Account Policies
    16.1. 17.1. Creating and Managing System Policies
    16.2. 17.2. Managing Account/User Policies
    17.3. System Startup and Logon Processing Overview
    17. 18. Desktop Profile Management
    17.1. 18.1. Roaming Profiles
    17.2. 18.2. Mandatory profiles
    17.3. 18.3. Creating/Managing Group Profiles
    17.4. 18.4. Default Profile for Windows Users
    18. 19. Interdomain Trust Relationships
    18.1. 19.1. Trust Relationship Background
    18.2. MS Windows NT4 Trust Configuration19.2. Native MS Windows NT4 Trusts Configuration
    18.3. Configuring Samba Domain Trusts19.3. Configuring Samba NT-style Domain Trusts
    19. 20. PAM Configuration for Centrally Managed Authentication
    19.1. 20.1. Samba and PAM
    19.2. 20.2. Distributed Authentication
    19.3. 20.3. PAM Configuration in smb.conf
    20. 21. Stackable VFS modules
    20.1. 21.1. Introduction and configuration
    20.2. 21.2. Included modules
    20.3. 21.3. VFS modules available elsewhere
    21. 22. Hosting a Microsoft Distributed File System tree on Samba
    21.1. 22.1. Instructions
    22. 23. Integrating MS Windows networks with Samba
    22.1. 23.1. Name Resolution in a pure Unix/Linux world
    22.2. 23.2. Name resolution as used within MS Windows networking
    23. 24. Improved browsing in samba
    23.1. 24.1. Overview of browsing
    23.2. 24.2. Browsing support in samba
    23.3. 24.3. Problem resolution
    23.4. 24.4. Browsing across subnets
    23.5. 24.5. Setting up a WINS server
    23.6. 24.6. Setting up Browsing in a WORKGROUP
    23.7. 24.7. Setting up Browsing in a DOMAIN
    23.8. 24.8. Forcing samba to be the master
    23.9. 24.9. Making samba the domain master
    23.10. 24.10. Note about broadcast addresses
    23.11. 24.11. Multiple interfaces
    24. 25. Securing Samba
    24.1. 25.1. Introduction
    24.2. 25.2. Using host based protection
    24.3. 25.3. Using interface protection
    24.4. 25.4. Using a firewall
    24.5. 25.5. Using a IPC$ share deny
    24.6. 25.6. Upgrading Samba
    25. 26. Unicode/Charsets
    25.1. 26.1. What are charsets and unicode?
    25.2. 26.2. Samba and charsets
    26.3. Conversion from old names
    26. SWAT - The Samba Web Admininistration Tool27. How to compile SAMBA
    26.1. SWAT Features and Benefits27.1. Access Samba source code via CVS
    27. Migration from NT4 PDC to Samba-3 PDC27.2. Accessing the samba sources via rsync and ftp
    27.1. Planning and Getting Started27.3. Verifying Samba's PGP signature
    27.2. Managing Samba-3 Domain Control27.4. Building the Binaries
    27.5. Starting the smbd and nmbd
    28. Samba performance issuesMigration from NT4 PDC to Samba-3 PDC
    28.1. ComparisonsPlanning and Getting Started
    28.2. Socket options
    28.3. Read size
    28.4. Max xmit
    28.5. Log level
    28.6. Read raw
    28.7. Write raw
    28.8. Slow Clients
    28.9. Slow Logins
    28.10. Client tuningManaging Samba-3 Domain Control
    29.1. HPUX
    29.2. SCO Unix
    29.3. DNIX
    29.4. RedHat Linux Rembrandt-II
    29.5. AIX
    29.6. Solaris
    30.1. Macintosh clients?
    30.2. OS2 Client
    30.3. Windows for Workgroups
    30.4. Windows '95/'98
    30.5. Windows 2000 Service Pack 2
    30.6. Windows NT 3.1
    31. How to compile SAMBASWAT - The Samba Web Admininistration Tool
    31.1. Access Samba source code via CVS
    31.2. Accessing the samba sources via rsync and ftp
    31.3. Building the Binaries
    31.4. Starting the smbd and nmbdSWAT Features and Benefits
    32. Reporting BugsSamba performance issues
    32.1. IntroductionComparisons
    32.2. General infoSocket options
    32.3. Debug levelsRead size
    32.4. Internal errorsMax xmit
    32.5. Attaching to a running processLog level
    32.6. PatchesRead raw
    32.7. Write raw
    32.8. Slow Clients
    32.9. Slow Logins
    32.10. Client tuning
    33.1. Introduction
    33.2. Assumptions
    33.3. The tests
    33.4. Still having troubles?
    34. Analysing and solving samba problems
    34.1. Diagnostics tools
    34.2. Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
    34.3. Useful URL's
    34.4. Getting help from the mailing lists
    34.5. How to get off the mailinglists
    35. Reporting Bugs
    35.1. Introduction
    35.2. General info
    35.3. Debug levels
    35.4. Internal errors
    35.5. Attaching to a running process
    35.6. Patches
    Chapter 6. Samba as an NT4 or Win2k Primary Domain ControllerChapter 7. Samba as an NT4 or Win2k Primary Domain Controller
    Table of Contents
    7.1. Prerequisite Reading
    7.2. Background
    7.3. Configuring the Samba Domain Controller
    7.4. Creating Machine Trust Accounts and Joining Clients to the Domain
    7.4.1. Manual Creation of Machine Trust Accounts
    7.4.2. "On-the-Fly" Creation of Machine Trust Accounts
    7.4.3. Joining the Client to the Domain
    7.5. Common Problems and Errors
    7.5.1. I cannot include a '$' in a machine name
    7.5.2. 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 trust account.
    7.5.3. The system can not log you on (C000019B)....
    7.5.4. The machine trust account for this computer either does not +exist or is not accessible.
    7.5.5. When I attempt to login to a Samba Domain from a NT4/W2K workstation, +I get a message about my account being disabled.
    7.6. Domain Control for Windows 9x/ME

    6.1. Prerequisite Reading7.1. Prerequisite Reading

    Before you continue reading in this chapter, please make sure that you are comfortable with configuring basic files services in smb.conf and how to enable and administer password encryption in Samba. Theses two topics are covered in the -smb.conf(5) -manpage.

    smb.conf     manpage.

    6.2. Background7.2. Background

    This article outlines the steps necessary for configuring Samba as a PDC. @@ -250,19 +336,17 @@ CLASS="SECT1" >

    6.3. Configuring the Samba Domain Controller7.3. Configuring the Samba Domain Controller

    The first step in creating a working Samba PDC is to understand the parameters necessary in smb.conf. Here we attempt to explain the parameters that are covered in - the smb.conf -man page.

    smb.conf man page.

    Here is an example Encrypted passwords must be enabled. For more details on how to do this, refer to ENCRYPTION.htmlthe User Database chapter.

    6.4. Creating Machine Trust Accounts and Joining Clients to the Domain7.4. Creating Machine Trust Accounts and Joining Clients to the Domain

    A machine trust account is a Samba account that is used to @@ -549,7 +633,10 @@ CLASS="EMPHASIS" file allows the creation of arbitrary user and machine accounts without requiring that account to be added to the system (/etc/passwd) file. It too requires the specification of the "non unix account range" option - in the [globals] section of the smb.conf file. + in the [globals] section of the smb.conf file.

  • Read the chapter about the User Database +for details.

    A Samba PDC, however, stores each machine trust account in two parts, as follows: @@ -632,8 +725,8 @@ CLASS="SECT2" >

    6.4.1. Manual Creation of Machine Trust Accounts7.4.1. Manual Creation of Machine Trust Accounts

    The first step in manually creating a machine trust account is to @@ -738,12 +831,12 @@ as shown here:

    root# smbpasswd -a -m machine_name

    where

    6.4.2. "On-the-Fly" Creation of Machine Trust Accounts7.4.2. "On-the-Fly" Creation of Machine Trust Accounts

    The second (and recommended) way of creating machine trust accounts is @@ -839,8 +932,8 @@ CLASS="SECT2" >

    6.4.3. Joining the Client to the Domain7.4.3. Joining the Client to the Domain

    The procedure for joining a client to the domain varies with the @@ -899,6 +992,22 @@ CLASS="EMPHASIS" (i.e., you must supply a Samba administrative account when prompted).

  • Samba

    Joining a samba client to a domain is documented in + the Domain Member chapter.

    • 6.5. Common Problems and Errors7.5. Common Problems and Errors

    7.5.1. I cannot include a '$' in a machine name

    • I cannot include a '$' in a machine name. -

      A 'machine name' in (typically) A 'machine name' in (typically) /etc/passwd - of the machine name with a '$' appended. FreeBSD (and other BSD - systems?) won't create a user with a '$' in their name. -

      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 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 vipw to edit the entry, adding the '$'. Or create - the whole entry with vipw if you like, make sure you use a - unique User ID ! -

    • 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 trust account. -

    7.5.2. 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 trust account.

    This happens if you try to create a machine trust 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: -

    This happens if you try to create a machine trust 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:

    C:\WINNT\> net use * /d -

    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. -

  • The system can not log you on (C000019B).... -

    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.

    • 7.5.3. The system can not log you on (C000019B)....

    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 again or consult your - system administrator" when attempting to logon. -

    This occurs when the domain SID stored in the secrets.tdb database - is changed. The most common cause of a change in domain SID is when - the domain name and/or the server name (netbios name) is changed. - The only way to correct the problem is to restore the original domain - SID or remove the domain client from the domain and rejoin. The domain - SID may be reset using either the smbpasswd or rpcclient utilities. -

  • The machine trust account for this computer either does not - exist or is not accessible. -

    This occurs when the domain SID stored in the secrets.tdb database +is changed. The most common cause of a change in domain SID is when +the domain name and/or the server name (netbios name) is changed. +The only way to correct the problem is to restore the original domain +SID or remove the domain client from the domain and rejoin. The domain +SID may be reset using either the smbpasswd or rpcclient utilities.

    • 7.5.4. The machine trust account for this computer either does not +exist or is not accessible.

    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". What's - wrong? -

    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". What's +wrong?

    This problem is caused by the PDC not having a suitable machine trust account. - If you are using the This problem is caused by the PDC not having a suitable machine trust account. +If you are using the add user script method to create - accounts then this would indicate that it has not worked. Ensure the domain - admin user system is working. -

    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 trust 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 ( i.e. 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. -

  • When I attempt to login to a Samba Domain from a NT4/W2K workstation, - I get a message about my account being disabled. -

    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% -

    At first be ensure to enable the useraccounts with smbpasswd -e - %user%, this is normally done, when you create an account. -

    In order to work around this problem in 2.2.0, configure the - account control flag in - /etc/pam.d/samba file as follows: - 

    	account required        pam_permit.so
-

    If you want to remain backward compatibility to samba 2.0.x use - pam_permit.so, it's also possible to use - pam_pwdb.so. There are some bugs if you try to - use pam_unix.so, if you need this, be ensure to use - the most recent version of this file. -

    • 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 trust 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 ( i.e. 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.

    6.6. What other help can I get?

    There are many sources of information available in the form -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.

    • What are some diagnostics tools I can use to debug the domain logon - process and where can I find them? -

      One of the best diagnostic tools for debugging problems is Samba itself. - You can use the -d option for both smbd and nmbd to specify what - 'debug level' at which to run. See the man pages on smbd, nmbd and - smb.conf for more information on debugging options. The debug - level can range from 1 (the default) to 10 (100 for debugging passwords). -

      Another helpful method of debugging is to compile samba using the - gcc -g flag. This will include debug - information in the binaries and allow you to attach gdb to the - running smbd / nmbd process. In order to attach gdb to an smbd - process for an NT workstation, first get the workstation to make the - connection. Pressing ctrl-alt-delete and going down to the domain box - is sufficient (at least, on the first time you join the domain) to - generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation - maintains an open connection, and therefore there will be an smbd - process running (assuming that you haven't set a really short smbd - idle timeout) So, in between pressing ctrl alt delete, and actually - typing in your password, you can gdb attach and continue. -

      Some useful samba commands worth investigating: -

      • testparam | more

      • smbclient -L //{netbios name of server}

      An SMB enabled version of tcpdump is available from - http://www.tcpdup.org/. - Ethereal, another good packet sniffer for Unix and Win32 - hosts, can be downloaded from http://www.ethereal.com. -

      For tracing things on the Microsoft Windows NT, Network Monitor - (aka. netmon) is available on the Microsoft Developer Network CD's, - the Windows NT Server install CD and the SMS CD's. The version of - netmon that ships with SMS allows for dumping packets between any two - computers (i.e. placing the network interface in promiscuous mode). - The version on the NT Server install CD will only allow monitoring - of network traffic directed to the local NT box and broadcasts on the - local subnet. Be aware that Ethereal can read and write netmon - formatted files. -

    • How do I install 'Network Monitor' on an NT Workstation - or a Windows 9x box? -

      Installing netmon on an NT workstation requires a couple - of steps. The following are for installing Netmon V4.00.349, which comes - with Microsoft Windows NT Server 4.0, on Microsoft Windows NT - Workstation 4.0. The process should be similar for other version of - Windows NT / Netmon. You will need both the Microsoft Windows - NT Server 4.0 Install CD and the Workstation 4.0 Install CD. -

      Initially you will need to install 'Network Monitor Tools and Agent' - on the NT Server. To do this -

      • Goto Start - Settings - Control Panel - - Network - Services - Add

      • Select the 'Network Monitor Tools and Agent' and - click on 'OK'.

      • Click 'OK' on the Network Control Panel. -

      • Insert the Windows NT Server 4.0 install CD - when prompted.

      At this point the Netmon files should exist in - %SYSTEMROOT%\System32\netmon\*.*. - Two subdirectories exist as well, parsers\ - which contains the necessary DLL's for parsing the netmon packet - dump, and captures\. -

      In order to install the Netmon tools on an NT Workstation, you will - first need to install the 'Network Monitor Agent' from the Workstation - install CD. -

      • Goto Start - Settings - Control Panel - - Network - Services - Add

      • Select the 'Network Monitor Agent' and click - on 'OK'.

      • Click 'OK' on the Network Control Panel. -

      • Insert the Windows NT Workstation 4.0 install - CD when prompted.

      Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* - to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set - permissions as you deem appropriate for your site. You will need - administrative rights on the NT box to run netmon. -

      To install Netmon on a Windows 9x box install the network monitor agent - from the Windows 9x CD (\admin\nettools\netmon). There is a readme - file located with the netmon driver files on the CD if you need - information on how to do this. Copy the files from a working - Netmon installation. -

    • The following is a list if helpful URLs and other links: -

    • How do I get help from the mailing lists? -

      There are a number of Samba related mailing lists. Go to http://samba.org, click on your nearest mirror - and then click on Support and then click on Samba related mailing lists. -

      For questions relating to Samba TNG go to - http://www.samba-tng.org/ - It has been requested that you don't post questions about Samba-TNG to the - main stream Samba lists.

      If you post a message to one of the lists please observe the following guide lines : -

      • Always remember that the developers are volunteers, they are - not paid and they never guarantee to produce a particular feature at - a particular time. Any time lines are 'best guess' and nothing more. -

      • Always mention what version of samba you are using and what - operating system its running under. You should probably list the - relevant sections of your smb.conf file, at least the options - in [global] that affect PDC support.

      • In addition to the version, if you obtained Samba via - CVS mention the date when you last checked it out.

      • Try and make your question clear and brief, lots of long, - convoluted questions get deleted before they are completely read ! - Don't post html encoded messages (if you can select colour or font - size its html).

      • If you run one of those nifty 'I'm on holidays' things when - you are away, make sure its configured to not answer mailing lists. -

      • Don't cross post. Work out which is the best list to post to - and see what happens, i.e. don't post to both samba-ntdom and samba-technical. - Many people active on the lists subscribe to more - than one list and get annoyed to see the same message two or more times. - Often someone will see a message and thinking it would be better dealt - with on another, will forward it on for you.

      • You might include partial - log files written at a debug level set to as much as 20. - Please don't send the entire log but enough to give the context of the - error messages.

      • (Possibly) If you have a complete netmon trace ( from the opening of - the pipe to the error ) you can send the *.CAP file as well.

      • Please think carefully before attaching a document to an email. - Consider pasting the relevant parts into the body of the message. The samba - mailing lists go to a huge number of people, do they all need a copy of your - smb.conf in their attach directory?

    • How do I get off the mailing lists? -

      7.5.5. When I attempt to login to a Samba Domain from a NT4/W2K workstation, +I get a message about my account being disabled.

      To have your name removed from a samba mailing list, go to the - same place you went to to get on it. Go to http://lists.samba.org, - click on your nearest mirror and then click on Support and - then click on At first be ensure to enable the useraccounts with Samba related mailing lists. Or perhaps see - here -

      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...) -

    smbpasswd -e +%user%, this is normally done, when you create an account.

    6.7. Domain Control for Windows 9x/ME7.6. Domain Control for Windows 9x/ME

    A domain and a workgroup are exactly the same thing in terms of network @@ -1625,8 +1248,8 @@ CLASS="SECT2" >

    6.7.1. Configuration Instructions: Network Logons7.6.1. Configuration Instructions: Network Logons

    The main difference between a PDC and a Windows 9x logon diff --git a/docs/htmldocs/samba.7.html b/docs/htmldocs/samba.7.html index 689fba7cee..728f42f6f9 100644 --- a/docs/htmldocs/samba.7.html +++ b/docs/htmldocs/samba.7.html @@ -246,13 +246,353 @@ CLASS="COMMAND" command is a tool for changing LanMan and Windows NT password hashes on Samba and Windows NT servers.

    smbcacls(1)

    The smbcacls command is + a tool to set ACL's on remote CIFS servers.

    smbsh(1)

    The smbsh command is + a program that allows you to run a unix shell with + with an overloaded VFS.

    smbtree(1)

    The smbtree command + is a text-based network neighborhood tool.

    smbtar(1)

    The smbtar can make + backups of data on CIFS/SMB servers.

    smbspool(8)

    smbspool is a + helper utility for printing on printers connected + to CIFS servers.

    smbcontrol(1)

    smbcontrol is a utility + that can change the behaviour of running samba daemons. +

    rpcclient(1)

    rpcclient is a utility + that can be used to execute RPC commands on remote + CIFS servers.

    pdbedit(8)

    The pdbedit command + can be used to maintain the local user database on + a samba server.

    findsmb(1)

    The findsmb command + can be used to find SMB servers on the local network. +

    net(8)

    The net command + is supposed to work similar to the DOS/Windows + NET.EXE command.

    swat(8)

    swat is a web-based + interface to configuring smb.conf. +

    winbindd(8)

    winbindd is a daemon + that is used for integrating authentication and + the user database into unix.

    wbinfo(1)

    wbinfo is a utility + that retrieves and stores information related to winbind. +

    editreg(1)

    editreg is a command-line + utility that can edit windows registry files. +

    profiles(1)

    profiles is a command-line + utility that can be used to replace all occurences of + a certain SID with another SID. +

    vfstest(1)

    vfstest is a utility + that can be used to test vfs modules.

    ntlm_auth(1)

    ntlm_auth is a helper-utility + for external programs wanting to do NTLM-authentication. +

    smbmount(8), smbumount(8), smbmount(8)

    smbmount,smbmnt and smbmnt are commands that can be used to + mount CIFS/SMB shares on Linux. +

    smbcquotas(1)

    smbcquotas is a tool that + can set remote QUOTA's on server with NTFS 5.

    COMPONENTS

    AVAILABILITY

    VERSION

    CONTRIBUTIONS

    CONTRIBUTORS

    AUTHOR

    Chapter 24. Securing SambaChapter 25. Securing Samba

    24.1. Introduction25.1. Introduction

    This note was attached to the Samba 2.2.8 release notes as it contained an @@ -93,8 +132,8 @@ CLASS="SECT1" >

    24.2. Using host based protection25.2. Using host based protection

    In many installations of Samba the greatest threat comes for outside @@ -134,8 +173,8 @@ CLASS="SECT1" >

    24.3. Using interface protection25.3. Using interface protection

    By default Samba will accept connections on any network interface that @@ -151,8 +190,6 @@ CLASS="PROGRAMLISTING" bind interfaces only = yes

    This tells Samba to only listen for connections on interfaces with a name starting with 'eth' such as eth0, eth1, plus on the loopback interface called 'lo'. The name you will need to use depends on what @@ -170,8 +207,8 @@ CLASS="SECT1" >

    24.4. Using a firewall25.4. Using a firewall

    Many people use a firewall to deny access to services that they don't @@ -200,8 +237,8 @@ CLASS="SECT1" >

    24.5. Using a IPC$ share deny25.5. Using a IPC$ share deny

    If the above methods are not suitable, then you could also place a @@ -239,8 +276,8 @@ CLASS="SECT1" >

    24.6. Upgrading Samba25.6. Upgrading Samba

    Please check regularly on Chapter 5. Samba as Stand-Alone ServerChapter 6. Samba as Stand-Alone Server

    In this section the function and purpose of Samba's

    5.1. User and Share security level6.1. User and Share security level

    A SMB server tells the client at startup what "security level" it is @@ -107,8 +107,8 @@ CLASS="SECT2" >

    5.1.1. User Level Security6.1.1. User Level Security

    I'll describe user level security first, as its simpler. In user level @@ -148,8 +148,8 @@ CLASS="SECT2" >

    5.1.2. Share Level Security6.1.2. Share Level Security

    Ok, now for share level security. In share level security the client @@ -185,8 +185,8 @@ CLASS="SECT2" >

    5.1.3. Server Level Security6.1.3. Server Level Security

    Finally "server level" security. In server level security the samba @@ -221,8 +221,8 @@ CLASS="SECT3" >

    5.1.3.1. Configuring Samba for Seemless Windows Network Integration6.1.3.1. Configuring Samba for Seemless Windows Network Integration

    MS Windows clients may use encrypted passwords as part of a challenege/response @@ -333,8 +333,8 @@ CLASS="SECT3" >

    5.1.3.2. Use MS Windows NT as an authentication server6.1.3.2. Use MS Windows NT as an authentication server

    This method involves the additions of the following parameters in the

    5.1.4. Domain Level Security6.1.4. Domain Level Security

    When samba is operating in

    5.1.4.1. Samba as a member of an MS Windows NT security domain6.1.4.1. Samba as a member of an MS Windows NT security domain

    This method involves additon of the following paramters in the

    5.1.5. ADS Level Security6.1.5. ADS Level Security

    For information about the configuration option please refer to the entire section entitled diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html index 6ebe2fc002..dc4b0c3541 100644 --- a/docs/htmldocs/smb.conf.5.html +++ b/docs/htmldocs/smb.conf.5.html @@ -174,7 +174,7 @@ CLASS="FILENAME" The share is accessed via the share name "foo":

        [foo]
 	path = /home/bar
@@ -195,7 +195,7 @@ CLASS="EMPHASIS"
 	elsewhere):
        [aprinter]
 	path = /usr/spool/public
@@ -294,7 +294,7 @@ CLASS="USERINPUT"
 		section:
        [homes]
 	read only = no
        [printers]
 	path = /usr/spool/public
@@ -410,7 +410,7 @@ CLASS="COMPUTEROUTPUT"
 		more lines like this:
        alias|alias|alias|alias...    
    docs/     shipped with the source code.
    In order for encrypted passwords to work correctly
 		
    WARNINGS
    VERSION
    SEE ALSO
    AUTHOR
    PrevNextChapter 28. Samba performance issuesChapter 32. Samba performance issues
    Table of Contents
    32.1. Comparisons
    32.2. Socket options
    32.3. Read size
    32.4. Max xmit
    32.5. Log level
    32.6. Read raw
    32.7. Write raw
    32.8. Slow Clients
    32.9. Slow Logins
    32.10. Client tuning
    28.1. Comparisons32.1. Comparisons
    The Samba server uses TCP to talk to the client. Thus if you are
@@ -111,8 +170,8 @@ CLASS="SECT1"
 >
    28.2. Socket options32.2. Socket options
    There are a number of socket options that can greatly affect the
@@ -139,8 +198,8 @@ CLASS="SECT1"
 >
    28.3. Read size32.3. Read size
    The option "read size" affects the overlap of disk reads/writes with
@@ -165,8 +224,8 @@ CLASS="SECT1"
 >
    28.4. Max xmit32.4. Max xmit
    At startup the client and server negotiate a "maximum transmit" size,
@@ -188,8 +247,8 @@ CLASS="SECT1"
 >
    28.5. Log level32.5. Log level
    If you set the log level (also known as "debug level") higher than 2
@@ -202,8 +261,8 @@ CLASS="SECT1"
 >
    28.6. Read raw32.6. Read raw
    The "read raw" operation is designed to be an optimised, low-latency
@@ -224,8 +283,8 @@ CLASS="SECT1"
 >
    28.7. Write raw32.7. Write raw
    The "write raw" operation is designed to be an optimised, low-latency
@@ -241,8 +300,8 @@ CLASS="SECT1"
 >
    28.8. Slow Clients32.8. Slow Clients
    One person has reported that setting the protocol to COREPLUS rather
@@ -258,8 +317,8 @@ CLASS="SECT1"
 >
    28.9. Slow Logins32.9. Slow Logins
    Slow logins are almost always due to the password checking time. Using
@@ -271,8 +330,8 @@ CLASS="SECT1"
 >
    28.10. Client tuning32.10. Client tuning
    Often a speed problem can be traced to the client. The client (for
@@ -389,7 +448,7 @@ WIDTH="33%"
 ALIGN="left"
 VALIGN="top"
 >PrevNextMigration from NT4 PDC to Samba-3 PDCSWAT - The Samba Web Admininistration ToolPortabilityThe samba checklist
    II. Type of installation
    Introduction
    Samba can operate in various SMB networks. This part contains information on configuring samba 
 for various environments.
    Table of Contents
    4. Nomenclature of Server Types
    4.1. Stand Alone Server
    4.2. Domain Member Server
    4.3. Domain Controller
    4.3.1. Domain Controller Types
    5. Samba as Stand-Alone Server
    5.1. User and Share security level
    5.1.1. User Level Security
    5.1.2. Share Level Security
    5.1.3. Server Level Security
    5.1.4. Domain Level Security
    5.1.5. ADS Level Security
    6. Samba as an NT4 or Win2k Primary Domain Controller
    6.1. Prerequisite Reading
    6.2. Background
    6.3. Configuring the Samba Domain Controller
    6.4. Creating Machine Trust Accounts and Joining Clients to the Domain
    6.4.1. Manual Creation of Machine Trust Accounts
    6.4.2. "On-the-Fly" Creation of Machine Trust Accounts
    6.4.3. Joining the Client to the Domain
    6.5. Common Problems and Errors
    6.6. What other help can I get?
    6.7. Domain Control for Windows 9x/ME
    6.7.1. Configuration Instructions:	Network Logons
    7. Samba Backup Domain Controller to Samba Domain Control
    7.1. Prerequisite Reading
    7.2. Background
    7.3. What qualifies a Domain Controller on the network?
    7.3.1. How does a Workstation find its domain controller?
    7.3.2. When is the PDC needed?
    7.4. Can Samba be a Backup Domain Controller to an NT PDC?
    7.5. How do I set up a Samba BDC?
    7.5.1. How do I replicate the smbpasswd file?
    7.5.2. Can I do this all with LDAP?
    8. Samba as a ADS domain member
    8.1. Setup your smb.conf
    8.2. Setup your /etc/krb5.conf
    8.3. Create the computer account
    8.3.1. Possible errors
    8.4. Test your server setup
    8.5. Testing with smbclient
    8.6. Notes
    9. Samba as a NT4 or Win2k domain member
    9.1. Joining an NT Domain with Samba 3.0
    9.2. Why is this better than security = server?
    Chapter 10. UNIX Permission Bits and Windows NT Access Control ListsChapter 11. UNIX Permission Bits and Windows NT Access Control Lists
    10.1. Viewing and changing UNIX permissions using the NT 
+NAME="AEN1534"
+>11.1. Viewing and changing UNIX permissions using the NT 
 	security dialogs
    10.2. How to view file security on a Samba share11.2. How to view file security on a Samba share
    From an NT4/2000/XP client, single-click with the right 
@@ -199,8 +260,8 @@ CLASS="SECT1"
 >
    10.3. Viewing file ownership11.3. Viewing file ownership
    Clicking on the 
    10.4. Viewing file or directory permissions11.4. Viewing file or directory permissions
    The third button is the 
    10.4.1. File Permissions11.4.1. File Permissions
    The standard UNIX user/group/world triple and 
@@ -401,8 +462,8 @@ CLASS="SECT2"
 >
    10.4.2. Directory Permissions11.4.2. Directory Permissions
    Directories on an NT NTFS file system have two 
@@ -433,8 +494,8 @@ CLASS="SECT1"
 >
    10.5. Modifying file or directory permissions11.5. Modifying file or directory permissions
    Modifying file and directory permissions is as simple 
@@ -529,8 +590,8 @@ CLASS="SECT1"
 >
    10.6. Interaction with the standard Samba create mask 
+NAME="AEN1629"
+>11.6. Interaction with the standard Samba create mask 
 	parameters
    10.7. Interaction with the standard Samba file attribute 
+NAME="AEN1682"
+>11.7. Interaction with the standard Samba file attribute 
 	mapping
    Chapter 20. Stackable VFS modulesChapter 21. Stackable VFS modules
    Table of Contents
    21.1. Introduction and configuration
    21.2. Included modules
    21.2.1. audit
    21.2.2. extd_audit
    21.2.3. recycle
    21.2.4. netatalk
    21.3. VFS modules available elsewhere
    21.3.1. DatabaseFS
    21.3.2. vscan
    20.1. Introduction and configuration21.1. Introduction and configuration
    Since samba 3.0, samba supports stackable VFS(Virtual File System) modules.  
@@ -121,16 +183,16 @@ CLASS="SECT1"
 >
    20.2. Included modules21.2. Included modules
    20.2.1. audit21.2.1. audit
    A simple module to audit file access to the syslog
@@ -167,8 +229,8 @@ CLASS="SECT2"
 >
    20.2.2. extd_audit21.2.2. extd_audit
    This module is identical with the 
    20.2.3. recycle21.2.3. recycle
    A recycle-bin like modules. When used any unlink call
@@ -260,8 +322,8 @@ CLASS="SECT2"
 >
    20.2.4. netatalk21.2.4. netatalk
    A netatalk module, that will ease co-existence of samba and
@@ -293,8 +355,8 @@ CLASS="SECT1"
 >
    20.3. VFS modules available elsewhere21.3. VFS modules available elsewhere
    This section contains a listing of various other VFS modules that 
@@ -309,8 +371,8 @@ CLASS="SECT2"
 >
    20.3.1. DatabaseFS21.3.1. DatabaseFS
    URL: 
    20.3.2. vscan21.3.2. vscan
    URL: Chapter 14. Unified Logons between Windows NT and UNIX using WinbindChapter 15. Unified Logons between Windows NT and UNIX using Winbind
    14.1. Abstract15.1. Abstract
    Integration of UNIX and Microsoft Windows NT through 
@@ -107,8 +247,8 @@ CLASS="SECT1"
 >
    14.2. Introduction15.2. Introduction
    It is well known that UNIX and Microsoft Windows NT have 
@@ -161,8 +301,8 @@ CLASS="SECT1"
 >
    14.3. What Winbind Provides15.3. What Winbind Provides
    Winbind unifies UNIX and Windows NT account management by 
@@ -203,8 +343,8 @@ CLASS="SECT2"
 >
    14.3.1. Target Uses15.3.1. Target Uses
    Winbind is targeted at organizations that have an 
@@ -227,8 +367,8 @@ CLASS="SECT1"
 >
    14.4. How Winbind Works15.4. How Winbind Works
    The winbind system is designed around a client/server 
@@ -247,8 +387,8 @@ CLASS="SECT2"
 >
    14.4.1. Microsoft Remote Procedure Calls15.4.1. Microsoft Remote Procedure Calls
    Over the last few years, efforts have been underway 
@@ -273,8 +413,8 @@ CLASS="SECT2"
 >
    14.4.2. Microsoft Active Directory Services15.4.2. Microsoft Active Directory Services
                    Since late 2001, Samba has gained the ability to
@@ -292,8 +432,8 @@ CLASS="SECT2"
 >
    14.4.3. Name Service Switch15.4.3. Name Service Switch
    The Name Service Switch, or NSS, is a feature that is 
@@ -372,8 +512,8 @@ CLASS="SECT2"
 >
    14.4.4. Pluggable Authentication Modules15.4.4. Pluggable Authentication Modules
    Pluggable Authentication Modules, also known as PAM, 
@@ -421,8 +561,8 @@ CLASS="SECT2"
 >
    14.4.5. User and Group ID Allocation15.4.5. User and Group ID Allocation
    When a user or group is created under Windows NT 
@@ -447,8 +587,8 @@ CLASS="SECT2"
 >
    14.4.6. Result Caching15.4.6. Result Caching
    An active system can generate a lot of user and group 
@@ -470,8 +610,8 @@ CLASS="SECT1"
 >
    14.5. Installation and Configuration15.5. Installation and Configuration
    Many thanks to John Trostel 
    14.5.1. Introduction15.5.1. Introduction
    This HOWTO describes the procedures used to get winbind up and 
@@ -548,8 +688,8 @@ CLASS="SECT2"
 >
    14.5.2. Requirements15.5.2. Requirements
    If you have a samba configuration file that you are currently 
@@ -618,8 +758,8 @@ CLASS="SECT2"
 >
    14.5.3. Testing Things Out15.5.3. Testing Things Out
    Before starting, it is probably best to kill off all the SAMBA 
@@ -663,8 +803,8 @@ CLASS="SECT3"
 >
    14.5.3.1. Configure and compile SAMBA15.5.3.1. Configure and compile SAMBA
    The configuration and compilation of SAMBA is pretty straightforward.
@@ -729,8 +869,8 @@ CLASS="SECT3"
 >
    14.5.3.2. Configure 15.5.3.2. Configure nsswitch.conf and the 
@@ -834,8 +974,8 @@ CLASS="SECT3"
 >
    14.5.3.3. Configure smb.conf15.5.3.3. Configure smb.conf
    Several parameters are needed in the smb.conf file to control 
@@ -909,8 +1049,8 @@ CLASS="SECT3"
 >
    14.5.3.4. Join the SAMBA server to the PDC domain15.5.3.4. Join the SAMBA server to the PDC domain
    Enter the following command to make the SAMBA server join the 
@@ -947,8 +1087,8 @@ CLASS="SECT3"
 >
    14.5.3.5. Start up the winbindd daemon and test it!15.5.3.5. Start up the winbindd daemon and test it!
    Eventually, you will want to modify your smb startup script to 
@@ -1083,16 +1223,16 @@ CLASS="SECT3"
 >
    14.5.3.6. Fix the init.d startup scripts15.5.3.6. Fix the init.d startup scripts
    14.5.3.6.1. Linux15.5.3.6.1. Linux
    The 
    14.5.3.6.2. Solaris15.5.3.6.2. Solaris
    On solaris, you need to modify the 
@@ -1285,8 +1425,8 @@ CLASS="SECT4"
 >
    14.5.3.6.3. Restarting15.5.3.6.3. Restarting
    If you restart the 
    14.5.3.7. Configure Winbind and PAM15.5.3.7. Configure Winbind and PAM
    If you have made it this far, you know that winbindd and samba are working
@@ -1367,8 +1507,8 @@ CLASS="SECT4"
 >
    14.5.3.7.1. Linux/FreeBSD-specific PAM configuration15.5.3.7.1. Linux/FreeBSD-specific PAM configuration
    The 
    14.5.3.7.2. Solaris-specific configuration15.5.3.7.2. Solaris-specific configuration
    The /etc/pam.conf needs to be changed. I changed this file so that my Domain
@@ -1583,8 +1723,8 @@ CLASS="SECT1"
 >
    14.6. Limitations15.6. Limitations
    Winbind has a number of limitations in its current 
@@ -1625,8 +1765,8 @@ CLASS="SECT1"
 >
    14.7. Conclusion15.7. Conclusion
    The winbind system, through the use of the Name Service 
diff --git a/docs/manpages/findsmb.1 b/docs/manpages/findsmb.1
index 733537fad8..37aa7565b5 100644
--- a/docs/manpages/findsmb.1
+++ b/docs/manpages/findsmb.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "FINDSMB" "1" "07 april 2003" "" ""
+.TH "FINDSMB" "1" "17 April 2003" "" ""
 
 .SH NAME
 findsmb \- list info about machines that respond to SMB  name queries on a subnet
diff --git a/docs/manpages/lmhosts.5 b/docs/manpages/lmhosts.5
index 021d2179d4..84cd3e42fe 100644
--- a/docs/manpages/lmhosts.5
+++ b/docs/manpages/lmhosts.5
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "LMHOSTS" "5" "07 april 2003" "" ""
+.TH "LMHOSTS" "5" "17 April 2003" "" ""
 
 .SH NAME
 lmhosts \- The Samba NetBIOS hosts file
diff --git a/docs/manpages/net.8 b/docs/manpages/net.8
index e80a5d730b..c22ecaadf1 100644
--- a/docs/manpages/net.8
+++ b/docs/manpages/net.8
@@ -3,24 +3,29 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "NET" "8" "07 april 2003" "" ""
+.TH "NET" "8" "17 April 2003" "" ""
 
 .SH NAME
 net \- Tool for administration of Samba and remote CIFS servers.
 .SH SYNOPSIS
 
-\fBnet\fR \fB\fR [ \fB-h\fR ] [ \fB-w workgroup\fR ] [ \fB-W myworkgroup\fR ] [ \fB-U user\fR ] [ \fB-I ip-address\fR ] [ \fB-p port\fR ] [ \fB-n myname\fR ] [ \fB-s conffile\fR ] [ \fB-S server\fR ] [ \fB-C comment\fR ] [ \fB-M maxusers\fR ] [ \fB-F flags\fR ] [ \fB-j jobid\fR ] [ \fB-l\fR ] [ \fB-r\fR ] [ \fB-f\fR ] [ \fB-t timeout\fR ] [ \fB-P\fR ] [ \fB-D debuglevel\fR ]
+\fBnet\fR \fB\fR [ \fB-h\fR ] [ \fB-w workgroup\fR ] [ \fB-W myworkgroup\fR ] [ \fB-U user\fR ] [ \fB-I ip-address\fR ] [ \fB-p port\fR ] [ \fB-n myname\fR ] [ \fB-s conffile\fR ] [ \fB-S server\fR ] [ \fB-l\fR ] [ \fB-P\fR ] [ \fB-D debuglevel\fR ]
 
 .SH "DESCRIPTION"
 .PP
 This tool is part of the \fBSamba\fR(7) suite.
 .PP
 The samba net utility is meant to work just like the net utility 
-available for windows and DOS.
+available for windows and DOS. The first argument should be used 
+to specify the protocol to use when executing a certain command. 
+ADS is used for ActiveDirectory, RAP is using for old (Win9x/NT3) 
+clients and RPC can be used for NT4 and Windows 2000. If this 
+argument is omitted, net will try to determine it automatically. 
+Not all commands are available on all protocols.
 .SH "OPTIONS"
 .TP
-\fB-h\fR
-Display summary of all available options.
+\fB-h|--help\fR
+Print a summary of command line options.
 .TP
 \fB-w target-workgroup\fR
 Sets target workgroup or domain. You have to specify 
@@ -34,111 +39,394 @@ User name to use
 .TP
 \fB-I ip-address\fR
 IP address of target server to use. You have to
-specify either this option or a target workgroup or a target server.
+specify either this option or a target workgroup or
+a target server.
 .TP
 \fB-p port\fR
-Port on the target server to connect to.
-.TP
-\fB-n myname\fR
-Sets name of the client.
-.TP
-\fB-s conffile\fR
-Specify alternative configuration file that should be loaded.
+Port on the target server to connect to (usually 139 or 445). 
+Defaults to trying 445 first, then 139.
+.TP
+\fB-n \fR
+This option allows you to override
+the NetBIOS name that Samba uses for itself. This is identical
+to setting the \fINetBIOS
+name\fR parameter in the \fBsmb.conf\fR(5) file.  However, a command
+line setting will take precedence over settings in
+\fBsmb.conf\fR(5).
+.TP
+\fB-s \fR
+The file specified contains the 
+configuration details required by the server.  The 
+information in this file includes server-specific
+information such as what printcap file to use, as well 
+as descriptions of all the services that the server is 
+to provide. See \fIsmb.conf(5)\fR for more information.
+The default configuration file name is determined at 
+compile time.
 .TP
 \fB-S server\fR
 Name of target server. You should specify either 
 this option or a target workgroup or a target IP address.
 .TP
-\fB-C comment\fR
-FIXME
-.TP
-\fB-M maxusers\fR
-FIXME
-.TP
-\fB-F flags\fR
-FIXME
-.TP
-\fB-j jobid\fR
-FIXME
-.TP
 \fB-l\fR
-FIXME
-.TP
-\fB-r\fR
-FIXME
-.TP
-\fB-f\fR
-FIXME
-.TP
-\fB-t timeout\fR
-FIXME
+When listing data, give more information on each item.
 .TP
 \fB-P\fR
 Make queries to the external server using the machine account of the local server.
 .TP
-\fB-D debuglevel\fR
-set the debuglevel. Debug level 0 is the lowest
-and 100 being the highest. This should be set to 100 if you are
-planning on submitting a bug report to the Samba team (see
-\fIBUGS.txt\fR).
-.SH "TIME"
+\fB-d|--debug=debuglevel\fR
+\fIdebuglevel\fR is an integer 
+from 0 to 10.  The default value if this parameter is 
+not specified is zero.
+
+The higher this value, the more detail will be 
+logged to the log files about the activities of the 
+server. At level 0, only critical errors and serious 
+warnings will be logged. Level 1 is a reasonable level for
+day to day running - it generates a small amount of 
+information about operations carried out.
+
+Levels above 1 will generate considerable 
+amounts of log data, and should only be used when 
+investigating a problem. Levels above 3 are designed for 
+use only by developers and generate HUGE amounts of log
+data, most of which is extremely cryptic.
+
+Note that specifying this parameter here will 
+override the log
+level file.
+.SH "COMMANDS"
+.SS "TIME"
 .PP
 The \fBNET TIME\fR command allows you to view the time on a remote server
 or synchronise the time on the local server with the time on the remote server.
-.TP
-\fB\fR
+.SS "TIME"
+.PP
 Without any options, the \fBNET TIME\fR command 
 displays the time on the remote server.
-.TP
-\fBSYSTEM\fR
+.SS "TIME SYSTEM"
+.PP
 Displays the time on the remote server in a format ready for \fB/bin/date\fR
-.TP
-\fBSET\fR
+.SS "TIME SET"
+.PP
 Tries to set the date and time of the local server to that on 
-the remote server using \fB/bin/date\fR.
-.TP
-\fBZONE\fR
+the remote server using \fB/bin/date\fR. 
+.SS "TIME ZONE"
+.PP
 Displays the timezone in hours from GMT on the remote computer.
-.SH "RPC"
+.SS "[RPC|ADS] JOIN [TYPE] [-U USERNAME[%PASSWORD]] [OPTIONS]"
 .PP
-The \fBNET RPC\fR command allows you to do various 
-NT4 operations.
-.TP
-\fBJOIN -U username[%password] [options]\fR
-Join a domain with specified username and password. Password 
-will be prompted if none is specified.
-.TP
-\fBJOIN [options except -U]\fR
-to join a domain created in server manager
-.TP
-\fBUSER [misc. options] [targets]\fR
-List users
-.TP
-\fBUSER DELETE  [misc options]\fR
-delete specified user
-.TP
-\fBUSER INFO  [misc options]\fR
-list the domain groups of the specified user
-.TP
-\fBUSER ADD  [password] [-F user flags] [misc. options]\fR
-Add specified user
-.TP
-\fBGROUP [misc options] [targets]\fR
-List user groups
-.TP
-\fBGROUP DELETE  [misc. options] [targets]\fR
-Delete specified group
+Join a domain.  If the account already exists on the server, and 
+[TYPE] is MEMBER, the machine will attempt to join automatically. 
+(Assuming that the machine has been created in server manager)
+Otherwise, a password will be prompted for, and a new account may
+be created.
+.PP
+[TYPE] may be PDC, BDC or MEMBER to specify the type of server
+joining the domain.
+.SS "[RPC] OLDJOIN [OPTIONS]"
+.PP
+Join a domain. Use the OLDJOIN option to join the domain 
+using the old style of domain joining - you need to create a trust 
+account in server manager first.
+.SS "[RPC|ADS] USER"
+.SS "[RPC|ADS] USER DELETE TARGET"
+.PP
+Delete specified user
+.SS "[RPC|ADS] USER LIST"
+.PP
+List all users
+.SS "[RPC|ADS] USER INFO TARGET"
+.PP
+List the domain groups of a the specified user.
+.SS "[RPC|ADS] USER ADD NAME [PASSWORD] [-F USER FLAGS] [-C COMMENT]"
+.PP
+Add specified user.
+.SS "[RPC|ADS] GROUP"
+.SS "[RPC|ADS] GROUP [MISC OPTIONS] [TARGETS]"
+.PP
+List user groups.
+.SS "[RPC|ADS] GROUP DELETE NAME [MISC. OPTIONS]"
+.PP
+Delete specified group.
+.SS "[RPC|ADS] GROUP ADD NAME [-C COMMENT]"
+.PP
+Create specified group.
+.SS "[RAP|RPC] SHARE"
+.SS "[RAP|RPC] SHARE [MISC. OPTIONS] [TARGETS]"
+.PP
+Enumerates all exported resources (network shares) on target server.
+.SS "[RAP|RPC] SHARE ADD NAME=SERVERPATH [-C COMMENT] [-M MAXUSERS] [TARGETS]"
+.PP
+Adds a share from a server (makes the export active). Maxusers 
+specifies the number of users that can be connected to the 
+share simultaneously.
+.SS "SHARE DELETE SHARENAM"
+.PP
+Delete specified share.
+.SS "[RPC|RAP] FILE"
+.SS "[RPC|RAP] FILE"
+.PP
+List all open files on remote server.
+.SS "[RPC|RAP] FILE CLOSE FILEID"
+.PP
+Close file with specified \fIfileid\fR on 
+remote server.
+.SS "[RPC|RAP] FILE INFO FILEID"
+.PP
+Print information on specified \fIfileid\fR. 
+Currently listed are: file-id, username, locks, path, permissions.
+.SS "[RAP|RPC] FILE USER"
+.sp
+.RS
+.B "Note:"
+Currently NOT implemented.
+.RE
+.SS "SESSION"
+.SS "RAP SESSION"
+.PP
+Without any other options, SESSION enumerates all active SMB/CIFS 
+sessions on the target server.
+.SS "RAP SESSION DELETE|CLOSE CLIENT_NAME"
+.PP
+Close the specified sessions.
+.SS "RAP SESSION INFO CLIENT_NAME"
+.PP
+Give a list with all the open files in specified session.
+.SS "RAP SERVER DOMAIN"
+.PP
+List all servers in specified domain or workgroup. Defaults
+to local domain.
+.SS "RAP DOMAIN"
+.PP
+Lists all domains and workgroups visible on the 
+current network.
+.SS "RAP PRINTQ"
+.SS "RAP PRINTQ LIST QUEUE_NAME"
+.PP
+Lists the specified print queue and print jobs on the server.
+If the \fIQUEUE_NAME\fR is omitted, all 
+queues are listed.
+.SS "RAP PRINTQ DELETE JOBID"
+.PP
+Delete job with specified id.
+.SS "RAP VALIDATE USER [PASSWORD]"
+.PP
+Validate whether the specified user can log in to the 
+remote server. If the password is not specified on the commandline, it 
+will be prompted. 
+.sp
+.RS
+.B "Note:"
+Currently NOT implemented.
+.RE
+.SS "RAP GROUPMEMBER"
+.SS "RAP GROUPMEMBER LIST GROUP"
+.PP
+List all members of the specified group.
+.SS "RAP GROUPMEMBER DELETE GROUP USER"
+.PP
+Delete member from group.
+.SS "RAP GROUPMEMBER ADD GROUP USER"
+.PP
+Add member to group.
+.SS "RAP ADMIN COMMAND"
+.PP
+Execute the specified \fIcommand\fR on 
+the remote server. Only works with OS/2 servers.
+.sp
+.RS
+.B "Note:"
+Currently NOT implemented.
+.RE
+.SS "RAP SERVICE"
+.SS "RAP SERVICE START NAME [ARGUMENTS...]"
+.PP
+Start the specified service on the remote server. Not implemented yet.
+.sp
+.RS
+.B "Note:"
+Currently NOT implemented.
+.RE
+.SS "RAP SERVICE STOP"
+.PP
+Stop the specified service on the remote server.
+.sp
+.RS
+.B "Note:"
+Currently NOT implemented.
+.RE
+.SS "RAP PASSWORD USER OLDPASS NEWPASS"
+.PP
+Change password of \fIUSER\fR from \fIOLDPASS\fR to \fINEWPASS\fR.
+.SS "LOOKUP"
+.SS "LOOKUP HOST HOSTNAME [TYPE]"
+.PP
+Lookup the IP address of the given host with the specified type (netbios suffix). 
+The type defaults to 0x20 (workstation).
+.SS "LOOKUP LDAP [DOMAIN"
+.PP
+Give IP address of LDAP server of specified \fIDOMAIN\fR. Defaults to local domain.
+.SS "LOOKUP KDC [REALM]"
+.PP
+Give IP address of KDC for the specified \fIREALM\fR.
+Defaults to local realm.
+.SS "LOOKUP DC [DOMAIN]"
+.PP
+Give IP's of Domain Controllers for specified \fIDOMAIN\fR. Defaults to local domain.
+.SS "LOOKUP MASTER DOMAIN"
+.PP
+Give IP of master browser for specified \fIDOMAIN\fR
+or workgroup. Defaults to local domain.
+.SS "CACHE"
+.PP
+Samba uses a general caching interface called 'gencache'. It 
+can be controlled using 'NET CACHE'.
+.PP
+All the timeout parameters support the suffixes:
+
+s - Seconds
+
+m - Minutes
+
+h - Hours
+
+d - Days
+
+w - Weeks
+.SS "CACHE ADD KEY DATA TIME-OUT"
+.PP
+Add specified key+data to the cache with the given timeout.
+.SS "CACHE DEL KEY"
+.PP
+Delete key from the cache.
+.SS "CACHE SET KEY DATA TIME-OUT"
+.PP
+Update data of existing cache entry.
+.SS "CACHE SEARCH PATTERN"
+.PP
+Search for the specified pattern in the cache data.
+.SS "CACHE LIST"
+.PP
+List all current items in the cache.
+.SS "CACHE FLUSH"
+.PP
+Remove all the current items from the cache.
+.SS "GETLOCALSID [DOMAIN]"
+.PP
+Print the SID of the specified domain, or if the parameter is 
+omitted, the SID of the domain the local server is in.
+.SS "SETLOCALSID S-1-5-21-X-Y-Z"
+.PP
+Sets domain sid for the local server to the specified SID.
+.SS "MAXRID"
+.PP
+Prints out the highest RID currently in use on the local 
+server (by the active 'passdb backend').
+.SS "RPC INFO"
+.PP
+Print information about the domain of the remote server, 
+such as domain name, domain sid and number of users and groups.
+.SS "[RPC|ADS] TESTJOIN"
+.PP
+Check whether participation in a domain is still valid.
+.SS "[RPC|ADS] CHANGETRUSTPW"
+.PP
+Force change of domain trust password.
+.SS "RPC TRUSTDOM"
+.SS "RPC TRUSTDOM ADD DOMAIN"
+.PP
+Add a interdomain trust account for 
+\fIDOMAIN\fR to the remote server. 
+.SS "RPC TRUSTDOM DEL DOMAIM"
+.PP
+Remove interdomain trust account for 
+\fIDOMAIN\fR from the remote server. 
+.sp
+.RS
+.B "Note:"
+Currently NOT implemented.
+.RE
+.SS "RPC TRUSTDOM ESTABLISH DOMAIN"
+.PP
+Establish a trust relationship to a trusting domain. 
+Interdomain account must already be created on the remote PDC.
+.SS "RPC TRUSTDOM REVOKE DOMAIN"
+.PP
+Abandon relationship to trusted domain
+.SS "RPC TRUSTDOM LIST"
+.PP
+List all current interdomain trust relationships.
+.SS "RPC ABORTSHUTDOWN"
+.PP
+Abort the shutdown of a remote server.
+.SS "SHUTDOWN [-T TIMEOUT] [-R] [-F] [-C MESSAGE]"
+.PP
+Shut down the remote server.
 .TP
-\fBGROUP ADD  [-C comment]\fR
-Create specified group
+\fB-r\fR
+Reboot after shutdown.
 .TP
-\fBSHARE [misc. options] [targets]\fR
-enumerates all exported resources (network shares) on target server
+\fB-f\fR
+Force shutting down all applications.
 .TP
-\fBSHARE ADD  [misc. options] [targets]\fR
-Adds a share from a server (makes the export active)
+\fB-t timeout\fR
+Timeout before system will be shut down. An interactive 
+user of the system can use this time to cancel the shutdown.
 .TP
-\fBSHARE DELETE  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "NMBD" "8" "07 april 2003" "" ""
+.TH "NMBD" "8" "17 April 2003" "" ""
 
 .SH NAME
 nmbd \- NetBIOS name server to provide NetBIOS  over IP naming services to clients
diff --git a/docs/manpages/nmblookup.1 b/docs/manpages/nmblookup.1
index d57ec24fa3..fc8ae0b9f8 100644
--- a/docs/manpages/nmblookup.1
+++ b/docs/manpages/nmblookup.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "NMBLOOKUP" "1" "07 april 2003" "" ""
+.TH "NMBLOOKUP" "1" "17 April 2003" "" ""
 
 .SH NAME
 nmblookup \- NetBIOS over TCP/IP client used to lookup NetBIOS  names
diff --git a/docs/manpages/pdbedit.8 b/docs/manpages/pdbedit.8
index b0731cdffd..2f25a5479d 100644
--- a/docs/manpages/pdbedit.8
+++ b/docs/manpages/pdbedit.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "PDBEDIT" "8" "07 april 2003" "" ""
+.TH "PDBEDIT" "8" "17 April 2003" "" ""
 
 .SH NAME
 pdbedit \- manage the SAM database
diff --git a/docs/manpages/rpcclient.1 b/docs/manpages/rpcclient.1
index 92b80e02cb..c01c3f92d0 100644
--- a/docs/manpages/rpcclient.1
+++ b/docs/manpages/rpcclient.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "RPCCLIENT" "1" "07 april 2003" "" ""
+.TH "RPCCLIENT" "1" "17 April 2003" "" ""
 
 .SH NAME
 rpcclient \- tool for executing client side  MS-RPC functions
diff --git a/docs/manpages/samba.7 b/docs/manpages/samba.7
index e1ae7d77bf..a0f69baf56 100644
--- a/docs/manpages/samba.7
+++ b/docs/manpages/samba.7
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SAMBA" "7" "07 april 2003" "" ""
+.TH "SAMBA" "7" "17 April 2003" "" ""
 
 .SH NAME
 Samba \- A Windows SMB/CIFS fileserver for UNIX
@@ -70,6 +70,89 @@ priviledges for that group, such as saAddUser, etc.
 The \fBsmbpasswd\fR
 command is a tool for changing LanMan and Windows NT 
 password hashes on Samba and Windows NT servers.
+.TP
+\fBsmbcacls(1)\fR
+The \fBsmbcacls\fR command is 
+a tool to set ACL's on remote CIFS servers. 
+.TP
+\fBsmbsh(1)\fR
+The \fBsmbsh\fR command is 
+a program that allows you to run a unix shell with 
+with an overloaded VFS.
+.TP
+\fBsmbtree(1)\fR
+The \fBsmbtree\fR command 
+is a text-based network neighborhood tool.
+.TP
+\fBsmbtar(1)\fR
+The \fBsmbtar\fR can make 
+backups of data on CIFS/SMB servers.
+.TP
+\fBsmbspool(8)\fR
+\fBsmbspool\fR is a 
+helper utility for printing on printers connected 
+to CIFS servers. 
+.TP
+\fBsmbcontrol(1)\fR
+\fBsmbcontrol\fR is a utility
+that can change the behaviour of running samba daemons.
+.TP
+\fBrpcclient(1)\fR
+\fBrpcclient\fR is a utility
+that can be used to execute RPC commands on remote 
+CIFS servers.
+.TP
+\fBpdbedit(8)\fR
+The \fBpdbedit\fR command 
+can be used to maintain the local user database on 
+a samba server.
+.TP
+\fBfindsmb(1)\fR
+The \fBfindsmb\fR command 
+can be used to find SMB servers on the local network.
+.TP
+\fBnet(8)\fR
+The \fBnet\fR command 
+is supposed to work similar to the DOS/Windows
+NET.EXE command.
+.TP
+\fBswat(8)\fR
+\fBswat\fR is a web-based
+interface to configuring \fIsmb.conf\fR.
+.TP
+\fBwinbindd(8)\fR
+\fBwinbindd\fR is a daemon 
+that is used for integrating authentication and 
+the user database into unix.
+.TP
+\fBwbinfo(1)\fR
+\fBwbinfo\fR is a utility 
+that retrieves and stores information related to winbind.
+.TP
+\fBeditreg(1)\fR
+\fBeditreg\fR is a command-line
+utility that can edit windows registry files.
+.TP
+\fBprofiles(1)\fR
+\fBprofiles\fR is a command-line
+utility that can be used to replace all occurences of 
+a certain SID with another SID.
+.TP
+\fBvfstest(1)\fR
+\fBvfstest\fR is a utility
+that can be used to test vfs modules.
+.TP
+\fBntlm_auth(1)\fR
+\fBntlm_auth\fR is a helper-utility
+for external programs wanting to do NTLM-authentication.
+.TP
+\fBsmbmount(8), smbumount(8), smbmount(8)\fR
+\fBsmbmount\fR,\fBsmbmnt\fR and \fBsmbmnt\fR are commands that can be used to 
+mount CIFS/SMB shares on Linux.
+.TP
+\fBsmbcquotas(1)\fR
+\fBsmbcquotas\fR is a tool that 
+can set remote QUOTA's on server with NTFS 5. 
 .SH "COMPONENTS"
 .PP
 The Samba suite is made up of several components. Each 
-- 
cgit 


From 065cf3eac53da6908f3e5a84b2765e75cd52c516 Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij 
Date: Thu, 17 Apr 2003 19:23:06 +0000
Subject: Regenerate docs (This used to be commit
 381f75134a8d7dd2c3983f64b6598944a63a07b2)

---
 docs/htmldocs/advancednetworkmanagement.html |  555 ++++++
 docs/htmldocs/cups-printing.html             | 2773 ++++++++++++++++++++++++++
 docs/htmldocs/domain-member.html             |  446 +++++
 docs/htmldocs/editreg.1.html                 |  142 ++
 docs/htmldocs/interdomaintrusts.html         |  451 +++++
 docs/htmldocs/introsmb.html                  |  659 ++++++
 docs/htmldocs/nt4migration.html              |  356 ++++
 docs/htmldocs/ntlm_auth.1.html               |  261 +++
 docs/htmldocs/policymgmt.html                |  758 +++++++
 docs/htmldocs/problems.html                  |  560 ++++++
 docs/htmldocs/profilemgmt.html               | 1753 ++++++++++++++++
 docs/htmldocs/profiles.1.html                |  139 ++
 docs/htmldocs/servertype.html                |  368 ++++
 docs/htmldocs/smbcquotas.1.html              |  391 ++++
 docs/htmldocs/smbtree.1.html                 |  304 +++
 docs/htmldocs/swat.html                      |  233 +++
 docs/htmldocs/unicode.html                   |  301 +++
 docs/manpages/editreg.1                      |   45 +
 docs/manpages/manpage.links                  |    0
 docs/manpages/manpage.refs                   |   39 +
 docs/manpages/ntlm_auth.1                    |  109 +
 docs/manpages/profiles.1                     |   45 +
 docs/manpages/smb.conf.5                     |    5 +-
 docs/manpages/smbcacls.1                     |    2 +-
 docs/manpages/smbclient.1                    |    2 +-
 docs/manpages/smbcontrol.1                   |    2 +-
 docs/manpages/smbcquotas.1                   |  183 ++
 docs/manpages/smbd.8                         |    2 +-
 docs/manpages/smbgroupedit.8                 |    2 +-
 docs/manpages/smbmnt.8                       |    2 +-
 docs/manpages/smbmount.8                     |    2 +-
 docs/manpages/smbpasswd.5                    |    2 +-
 docs/manpages/smbpasswd.8                    |    2 +-
 docs/manpages/smbsh.1                        |    2 +-
 docs/manpages/smbspool.8                     |    2 +-
 docs/manpages/smbstatus.1                    |    2 +-
 docs/manpages/smbtar.1                       |    2 +-
 docs/manpages/smbtree.1                      |  144 ++
 docs/manpages/smbumount.8                    |    2 +-
 docs/manpages/swat.8                         |    2 +-
 docs/manpages/testparm.1                     |    2 +-
 docs/manpages/testprns.1                     |    2 +-
 docs/manpages/vfstest.1                      |    2 +-
 docs/manpages/wbinfo.1                       |    2 +-
 docs/manpages/winbindd.8                     |    2 +-
 45 files changed, 11037 insertions(+), 23 deletions(-)
 create mode 100644 docs/htmldocs/advancednetworkmanagement.html
 create mode 100644 docs/htmldocs/cups-printing.html
 create mode 100644 docs/htmldocs/domain-member.html
 create mode 100644 docs/htmldocs/editreg.1.html
 create mode 100644 docs/htmldocs/interdomaintrusts.html
 create mode 100644 docs/htmldocs/introsmb.html
 create mode 100644 docs/htmldocs/nt4migration.html
 create mode 100644 docs/htmldocs/ntlm_auth.1.html
 create mode 100644 docs/htmldocs/policymgmt.html
 create mode 100644 docs/htmldocs/problems.html
 create mode 100644 docs/htmldocs/profilemgmt.html
 create mode 100644 docs/htmldocs/profiles.1.html
 create mode 100644 docs/htmldocs/servertype.html
 create mode 100644 docs/htmldocs/smbcquotas.1.html
 create mode 100644 docs/htmldocs/smbtree.1.html
 create mode 100644 docs/htmldocs/swat.html
 create mode 100644 docs/htmldocs/unicode.html
 create mode 100644 docs/manpages/editreg.1
 create mode 100644 docs/manpages/manpage.links
 create mode 100644 docs/manpages/manpage.refs
 create mode 100644 docs/manpages/ntlm_auth.1
 create mode 100644 docs/manpages/profiles.1
 create mode 100644 docs/manpages/smbcquotas.1
 create mode 100644 docs/manpages/smbtree.1

diff --git a/docs/htmldocs/advancednetworkmanagement.html b/docs/htmldocs/advancednetworkmanagement.html
new file mode 100644
index 0000000000..a57b74f275
--- /dev/null
+++ b/docs/htmldocs/advancednetworkmanagement.html
@@ -0,0 +1,555 @@
+
+Advanced Network Manangement
    SAMBA Project Documentation
    PrevNext
    Chapter 16. Advanced Network Manangement
    This section attempts to document peripheral issues that are of great importance to network
+administrators who want to improve network resource access control, to automate the user
+environment, and to make their lives a little easier.
    16.1. Configuring Samba Share Access Controls
    This section deals with how to configure Samba per share access control restrictions.
+By default samba sets no restrictions on the share itself. Restrictions on the share itself
+can be set on MS Windows NT4/200x/XP shares. This can be a very effective way to limit who can
+connect to a share. In the absence of specific restrictions the default setting is to allow
+the global user Everyone Full Control (ie: Full control, Change and Read).
    At this time Samba does NOT provide a tool for configuring access control setting on the Share
+itself. Samba does have the capacity to store and act on access control settings, but  the only
+way to create those settings is to use either the NT4 Server Manager or the Windows 200x MMC for
+Computer Management.
    Samba stores the per share access control settings in a file called share_info.tdb.
+The location of this file on your system will depend on how samba was compiled. The default location
+for samba's tdb files is under /usr/local/samba/var. If the tdbdump
+utility has been compiled and installed on your system then you can examine the contents of this file
+by: tdbdump share_info.tdb.
    16.1.1. Share Permissions Management
    The best tool for the task is platform dependant. Choose the best tool for your environmemt.
    16.1.1.1. Windows NT4 Workstation/Server
    The tool you need to use to manage share permissions on a Samba server is the NT Server Manager.
+Server Manager is shipped with Windows NT4 Server products but not with Windows NT4 Workstation.
+You can obtain the NT Server Manager for MS Windows NT4 Workstation from Microsoft - see details below.
    Instructions
    1. Launch the NT4 Server Manager, click on the Samba server you want to administer, then from the menu
+select Computer, then click on the Shared Directories entry.
    2. 	Now click on the share that you wish to manage, then click on the Properties tab, next click on
+	the Permissions tab. Now you can Add or change access control settings as you wish.
    16.1.1.2. Windows 200x/XP
    On MS Windows NT4/200x/XP system access control lists on the share itself are set using native
+tools, usually from filemanager. For example, in Windows 200x: right click on the shared folder,
+then select 'Sharing', then click on 'Permissions'. The default Windows NT4/200x permission allows
+Everyone Full Control on the Share.
    MS Windows 200x and later all comes with a tool called the 'Computer Management' snap-in for the
+Microsoft Management Console (MMC). This tool is located by clicking on Control Panel ->
+Administrative Tools -> Computer Management.
    Instructions
    1. 	After launching the MMC with the Computer Management snap-in, click on the menu item 'Action',
+	select 'Connect to another computer'. If you are not logged onto a domain you will be prompted
+	to enter a domain login user identifier and a password. This will authenticate you to the domain.
+	If you where already logged in with administrative privilidge this step is not offered.
    2. If the Samba server is not shown in the Select Computer box, then type in the name of the target
+Samba server in the field 'Name:'. Now click on the [+] next to 'System Tools', then on the [+]
+next to 'Shared Folders' in the left panel.
    3. Now in the right panel, double-click on the share you wish to set access control permissions on.
+Then click on the tab 'Share Permissions'. It is now possible to add access control entities
+to the shared folder. Do NOT forget to set what type of access (full control, change, read) you
+wish to assign for each entry.
    Be careful. If you take away all permissions from the Everyone user without removing this user
+then effectively no user will be able to access the share. This is a result of what is known as
+ACL precidence. ie: Everyone with NO ACCESS means that MaryK who is part of the group Everyone
+will have no access even if this user is given explicit full control access.
    16.2. Remote Server Administration
    How do I get 'User Manager' and 'Server Manager'?
    Since I don't need to buy an NT4 Server, how do I get the 'User Manager for Domains',
+the 'Server Manager'?
    Microsoft distributes a version of these tools called nexus for installation on Windows 9x / Me
+systems.  The tools set includes:
    • Server Manager
    • User Manager for Domains
    • Event Viewer
    Click here to download the archived file ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE
    The Windows NT 4.0 version of the 'User Manager for 
+Domains' and 'Server Manager' are available from Microsoft via ftp 
+from ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE
    16.3. Network Logon Script Magic
    This section needs work. Volunteer contributions most welcome. Please send your patches or updates
+to John Terpstra.
    There are several opportunities for creating a custom network startup configuration environment.
    No Logon Script
    Simple universal Logon Script that applies to all users
    Use of a conditional Logon Script that applies per user or per group attirbutes
    Use of Samba's Preexec and Postexec functions on access to the NETLOGON share to create
+	a custom Logon Script and then execute it.
    User of a tool such as KixStart
    The Samba source code tree includes two logon script generation/execution tools. See examples directory genlogon and ntlogon subdirectories.
    The following listings are from the genlogon directory.
    This is the genlogon.pl file:
+
+
    	#!/usr/bin/perl
+	#
+	# genlogon.pl
+	#
+	# Perl script to generate user logon scripts on the fly, when users
+	# connect from a Windows client.  This script should be called from smb.conf
+	# with the %U, %G and %L parameters. I.e:
+	#
+	#       root preexec = genlogon.pl %U %G %L
+	#
+	# The script generated will perform
+	# the following:
+	#
+	# 1. Log the user connection to /var/log/samba/netlogon.log
+	# 2. Set the PC's time to the Linux server time (which is maintained
+	#    daily to the National Institute of Standard's Atomic clock on the
+	#    internet.
+	# 3. Connect the user's home drive to H: (H for Home).
+	# 4. Connect common drives that everyone uses.
+	# 5. Connect group-specific drives for certain user groups.
+	# 6. Connect user-specific drives for certain users.
+	# 7. Connect network printers.
+
+	# Log client connection
+	#($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
+	($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
+	open LOG, ">>/var/log/samba/netlogon.log";
+	print LOG "$mon/$mday/$year $hour:$min:$sec - User $ARGV[0] logged into $ARGV[1]\n";
+	close LOG;
+
+	# Start generating logon script
+	open LOGON, ">/shared/netlogon/$ARGV[0].bat";
+	print LOGON "\@ECHO OFF\r\n";
+
+	# Connect shares just use by Software Development group
+	if ($ARGV[1] eq "SOFTDEV" || $ARGV[0] eq "softdev")
+	{
+		print LOGON "NET USE M: \\\\$ARGV[2]\\SOURCE\r\n";
+	}
+
+	# Connect shares just use by Technical Support staff
+	if ($ARGV[1] eq "SUPPORT" || $ARGV[0] eq "support")
+	{
+		print LOGON "NET USE S: \\\\$ARGV[2]\\SUPPORT\r\n";
+	}
+
+	# Connect shares just used by Administration staff
+	If ($ARGV[1] eq "ADMIN" || $ARGV[0] eq "admin")
+	{
+		print LOGON "NET USE L: \\\\$ARGV[2]\\ADMIN\r\n";
+		print LOGON "NET USE K: \\\\$ARGV[2]\\MKTING\r\n";
+	}
+
+	# Now connect Printers.  We handle just two or three users a little
+	# differently, because they are the exceptions that have desktop
+	# printers on LPT1: - all other user's go to the LaserJet on the
+	# server.
+	if ($ARGV[0] eq 'jim'
+	    || $ARGV[0] eq 'yvonne')
+	{
+		print LOGON "NET USE LPT2: \\\\$ARGV[2]\\LJET3\r\n";
+		print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
+	}
+	else
+	{
+		print LOGON "NET USE LPT1: \\\\$ARGV[2]\\LJET3\r\n";
+		print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
+	}
+
+	# All done! Close the output file.
+	close LOGON;
    Those wishing to use more elaborate or capable logon processing system should check out the following sites:
    http://www.craigelachie.org/rhacer/ntlogon
    http://www.kixtart.org
    PrevHomeNext
    Unified Logons between Windows NT and UNIX using WinbindUpSystem and Account Policies
    
\ No newline at end of file
diff --git a/docs/htmldocs/cups-printing.html b/docs/htmldocs/cups-printing.html
new file mode 100644
index 0000000000..bc704e575e
--- /dev/null
+++ b/docs/htmldocs/cups-printing.html
@@ -0,0 +1,2773 @@
+
+CUPS Printing Support
    SAMBA Project Documentation
    PrevNext
    Chapter 14. CUPS Printing Support
    14.1. Introduction
    The Common Unix Print System (CUPS) has become very popular, but to many it is
+a very mystical tool. There is a great deal of uncertainty regarding CUPS and how
+it works. The result is seen in a large number of posting on the samba mailing lists
+expressing frustration when MS Windows printers appear not to work with a CUPS
+backr-end.
    This is a good time to point out how CUPS can be used and what it does. CUPS is more
+than just a print spooling system - it is a complete printer management system that
+complies with HTTP and IPP protocols. It can be managed remotely via a web browser
+and it can print using http and ipp protocols.
    CUPS allows to creation of RAW printers (ie: NO file format translation) as well as
+SMART printers (ie: CUPS does file format conversion as required for the printer). In
+many ways this gives CUPS similar capabilities to the MS Windows print monitoring
+system. Of course, if you are a CUPS advocate, you would agrue that CUPS is better!
+In any case, let us now move on to explore how one may configure CUPS for interfacing
+with MS Windows print clients via Samba.
    CUPS is a newcomer in the UNIX printing scene,
+which has convinced many people upon first trial already. However, it has quite a few
+new features, which make it different from other, more traditional printing systems.
    14.2. Configuring smb.conf for CUPS
    Printing with CUPS in the most basic smb.conf
+setup in Samba-3  only needs two settings: printing = cups and
+printcap = cups. While CUPS itself doesn't need a printcap
+anymore, the cupsd.conf configuration file knows two directives
+(example: Printcap /etc/printcap and PrintcapFormat
+BSD), which control if such a file should be created for the
+convenience of third party applications. Make sure it is set! For details see
+man cupsd.conf and other CUPS-related documentation.
    If SAMBA is compiled against libcups, then printcap = cups uses the
+CUPS API to list printers, submit jobs, etc. Otherwise it maps to the System V commands
+with an additional -oraw option for printing. On a Linux system,
+you can use the ldd command to find out details (ldd may not be
+present on other OS platforms, or its function may be embodied by a different command):
    transmeta:/home/kurt # ldd `which smbd`
+        libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000)
+        libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
+        libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000)
+        libdl.so.2 => /lib/libdl.so.2 (0x401e8000)
+        libnsl.so.1 => /lib/libnsl.so.1 (0x401ec000)
+        libpam.so.0 => /lib/libpam.so.0 (0x40202000)
+        libc.so.6 => /lib/libc.so.6 (0x4020b000)
+        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
    The line "libcups.so.2 => /usr/lib/libcups.so.2
+(0x40123000)" shows there is CUPS support compiled into this version of
+Samba. If this is the case, and printing = cups is set, then any
+otherwise manually set print command in smb.conf is ignored.
    14.3. CUPS - RAW Print Through Mode
    When used in raw print through mode is will be necessary to use the printer
+vendor's drivers in each Windows client PC.
    When CUPS printers are configured for RAW print-through mode operation it is the
+responsibility of the Samba client to fully render the print job (file) in a format
+that is suitable for direct delivery to the printer. In this case CUPS will NOT
+do any print file format conversion work.
    The CUPS files that need to be correctly set for RAW mode printers to work are:
+
+
    • /etc/cups/mime.types
    • /etc/cups/mime.convs
    
+
+Both contain entries that must be uncommented to allow RAW mode
+operation.
    Firstly, to enable CUPS based printing from Samba the following options must be
+enabled in your smb.conf file [globals] section:
+
+
    • printing = CUPS
    • printcap = CUPS
    
+
+When these parameters are specified the print directives in smb.conf (as well as in
+samba itself) will be ignored because samba will directly interface with CUPS through
+it's application program interface (API) - so long as Samba has been compiled with
+CUPS library (libcups) support. If samba has NOT been compiled with CUPS support then
+printing will use the System V AT&T command set with the -oraw 
+option automatically passing through.
    Cupsomatic (an enhanced printing utility that is part of some CUPS implementations) 
+on the Samba/CUPS server does *not* add any features if a file is really
+printed "raw".  However, if you have loaded the driver for the Windows client from
+the CUPS server, using the "cupsaddsmb" utility, and if this driver is one using
+a "Foomatic" PPD, the PJL header in question is already added on the Windows client,
+at the time when the driver initially generated the PostScript data and CUPS in true
+"-oraw" manner doesn't remove this PJL header and passes the file "as is" to its
+printer communication backend.
    NOTE: editing in the "mime.convs" and the "mime.types" file does not *enforce*
+"raw" printing, it only *allows* it.
    Print files that arrive from MS Windows printing are "auto-typed" by CUPS. This aids
+the process of determining proper treatment while in the print queue system.
+
+
    • 	Files generated by PCL drivers and directed at PCK printers get auto-typed as
+	application/octet-stream. Unknown file format types also
+	get auto-typed with this tag.
+	
    • 	Files generated by a Postscript driver and directed at a Postscript printer
+	are auto-typed depending on the auto-detected most suitable MIME type as:
+
+	
      • * application/postscript
      • * application/vnd.cups-postscript
      
+	
    "application/postscript" first goes thru the "pstops" filter (where the page counting
+and accounting takes place). The outcome will be of MIME type
+"application/vnd.cups-postscript". The pstopsfilter reads and uses information from
+the PPD and inserts user-provided options into the PostScript file. As a consequence,
+the filtered file could possibly have an unwanted PJL header.
    "application/postscript" will be all files with a ".ps", ".ai", ".eps" suffix or which
+have as their first character string one of "%!" or ">04<%".
    "application/vnd.cups-postscript" will files which contain the string
+"LANGUAGE=POSTSCRIPT" (or similar variations with different capitalization) in the
+first 512 bytes, and also contain the "PJL super escape code" in the first 128 bytes
+(">1B<%-12345X"). Very likely, most PostScript files generated on Windows using a CUPS
+or other PPD, will have to be auto-typed as "vnd.cups-postscript".  A file produced
+with a "Generic PostScript driver" will just be tagged "application/postscript".
    Once the file is in "application/vnd.cups-postscript" format, either "pstoraster"
+or "cupsomatic" will take over (depending on the printer configuration, as
+determined by the PPD in use).
    A printer queue with *no* PPD associated to it is a "raw" printer and all files
+will go directly there as received by the spooler. The exeptions are file types
+"application/octet-stream" which need "passthrough feature" enabled.
+"Raw" queues don't do any filtering at all, they hand the file directly to the
+CUPS backend. This backend is responsible for the sending of the data to the device
+(as in the "device URI" notation as lpd://, socket://, smb://, ipp://, http://,
+parallel:/, serial:/, usb:/ etc.)
    "cupsomatic"/Foomatic are *not* native CUPS drivers and they don't ship with CUPS.
+They are a Third Party add-on, developed at Linuxprinting.org.  As such, they are
+a brilliant hack to make all models (driven by Ghostscript drivers/filters in
+traditional spoolers) also work via CUPS, with the same (good or bad!) quality
+as in these other spoolers. "cupsomatic" is only a vehicle to execute a ghostscript
+commandline at that stage in the CUPS filtering chain, where "normally" the native
+CUPS "pstoraster" filter would kick in.  cupsomatic by-passes pstoraster, "kidnaps"
+the printfile from CUPS away and re-directs it to go through Ghostscipt. CUPS accepts this,
+because the associated CUPS-O-Matic-/Foomatic-PPD specifies:
       *cupsFilter:  "application/vnd.cups-postscript 0 cupsomatic"
    This line persuades CUPS to hand the file to cupsomatic, once it has successfully
+converted it to the MIME type "application/vnd.cups-postscript". This conversion will not
+happen for Jobs arriving from Windows which are auto-typed "application/octet-stream",
+with the according changes in "/etc/cups/mime.types" in place.
    CUPS is widely configurable and flexible, even regarding its filtering mechanism.
+Another workaround in some situations would be to have
+in "/etc/cups/mime.types" entries as follows:
       application/postscript           application/vnd.cups-raw  0  -
+   application/vnd.cups-postscript  application/vnd.cups-raw  0  -
    This would prevent all Postscript files from being filtered (rather, they will go
+thru the virtual "nullfilter" denoted with "-"). This could only be useful for
+PS printers. If you want to print PS code on non-PS printers an entry as follows
+could be useful:
       */*           application/vnd.cups-raw  0  -
    and would effectively send *all* files to the backend without further processing.
    Lastly, you could have the following entry:
       application/vnd.cups-postscript  application/vnd.cups-raw  0  my_PJL_stripping_filter
    You will need to write a "my_PJL_stripping_filter" (could be a shellscript) that
+parses the PostScript and removes the unwanted PJL. This would need to conform to
+CUPS filter design (mainly, receive and pass the parameters printername, job-id,
+username, jobtitle, copies, print options and possibly the filename). It would
+be installed as world executable into "/usr/lib/cups/filters/" and will be called
+by CUPS if it encounters a MIME type "application/vnd.cups-postscript".
    CUPS can handle "-o job-hold-until=indefinite". This keeps the job in the queue
+"on hold". It will only be printed upon manual release by the printer operator.
+This is a requirement in many "central reproduction departments", where a few
+operators manage the jobs of hundreds of users on some big machine, where no
+user is allowed to have direct access. (The operators often need to load the
+proper paper type before running the 10.000 page job requested by marketing
+for the mailing, etc.).
    14.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe
+PostScript driver with CUPS-PPDs downloaded to clients
    CUPS is perfectly able to use PPD files (PostScript
+Printer Descriptions). PPDs can control all print device options. They
+are usually provided by the manufacturer -- if you own a PostSript printer,
+that is. PPD files are always a component of PostScript printer drivers on MS
+Windows or Apple Mac OS systems. They are ASCII files containing
+user-selectable print options, mapped to appropriate PostScript, PCL or PJL
+commands for the target printer. Printer driver GUI dialogs translate these
+options "on-the-fly" into buttons and drop-down lists for the user to
+select.
    CUPS can load, without any conversions, the PPD file from
+any Windows (NT is recommended) PostScript driver and handle the options.
+There is a web browser interface to the print options (select
+http://localhost:631/printers/ and click on one "Configure Printer" button
+to see it), a commandline interface (see man lpoptions or
+try if you have lphelp on your system) plus some different GUI frontends on Linux
+UNIX, which can present PPD options to the users. PPD options are normally
+meant to become evaluated by the PostScript RIP on the real PostScript
+printer.
    CUPS doesn't stop at "real" PostScript printers in its
+usage of PPDs. The CUPS developers have extended the PPD concept, to also
+describe available device and driver options for non-PostScript printers
+through  CUPS-PPDs.
    This is logical, as CUPS includes a fully featured
+PostScript interpreter (RIP). This RIP is based on Ghostscript. It can
+process all received PostScript (and additionally many other file formats)
+from clients. All CUPS-PPDs geared to non-PostScript printers contain an
+additional line, starting with the keyword *cupsFilter.
+This line
+tells the CUPS print system which printer-specific filter to use for the
+interpretation of the accompanying PostScript. Thus CUPS lets all its
+printers appear as PostScript devices to its clients, because it can act as a
+PostScript RIP for those printers, processing the received PostScript code
+into a proper raster print format.
    CUPS-PPDs can also be used on Windows-Clients, on top of a
+PostScript driver (recommended is the Adobe one).
    This feature enables CUPS to do a few tricks no other
+spooler can do:
    • act as a networked PostScript RIP (Raster Image Processor), handling
+    printfiles from all client platforms in a uniform way;
    • act as a central accounting and billing server, as all files are passed
+    through the pstops Filter and are therefor logged in
+    the CUPS page_log. - NOTE: this
+    can not happen with "raw" print jobs, which always remain unfiltered
+    per definition;
    • enable clients to consolidate on a single PostScript driver, even for
+    many different target printers.
    14.5. Windows Terminal Servers (WTS) as CUPS clients
    This setup may be of special interest to people
+experiencing major problems in WTS environments. WTS need often a multitude
+of non-PostScript drivers installed to run their clients' variety of
+different printer models. This often imposes the price of much increased
+instability. In many cases, in an attempt to overcome this problem, site
+administrators have resorted to restrict the allowed drivers installed on
+their WTS to one generic PCL- and one PostScript driver. This however
+restricts the clients in the amount of printer options available for them --
+often they can't get out more then simplex prints from one standard paper
+tray, while their devices could do much better, if driven by a different
+driver!
    Using an Adobe PostScript driver, enabled with a CUPS-PPD,
+seems to be a very elegant way to overcome all these shortcomings. The
+PostScript driver is not known to cause major stability problems on WTS (even
+if used with many different PPDs). The clients will be able to (again) chose
+paper trays, duplex printing and other settings. However, there is a certain
+price for this too: a  CUPS server acting as a PostScript RIP for its clients
+requires more CPU and RAM than just to act as  a "raw spooling" device. Plus,
+this setup is not yet widely tested, although the first feedbacks look very
+promising...
    14.6. Setting up CUPS for driver download
    The cupsadsmb utility (shipped with all current
+CUPS versions) makes the sharing of any (or all) installed CUPS printers very
+easy. Prior to using it, you need the following settings in smb.conf:
    [global]
+		 load printers = yes
+		 printing = cups
+		 printcap name = cups
+
+	[printers]
+		 comment = All Printers
+		 path = /var/spool/samba
+		 browseable = no
+		 public = yes
+		 guest ok = yes
+		 writable = no
+		 printable = yes
+		 printer admin = root
+
+	[print$]
+		 comment = Printer Drivers
+		 path = /etc/samba/drivers
+		 browseable = yes
+		 guest ok = no
+		 read only = yes
+		 write list = root
+	
    For licensing reasons the necessary files of the Adobe
+Postscript driver can not be distributed with either Samba or CUPS. You need
+to download them yourself from the Adobe website. Once extracted, create a
+drivers directory in the CUPS data directory (usually
+/usr/share/cups/). Copy the Adobe files using
+UPPERCASE filenames, to this directory as follows:
    		ADFONTS.MFM
+		ADOBEPS4.DRV
+		ADOBEPS4.HLP
+		ADOBEPS5.DLL
+		ADOBEPSU.DLL
+		ADOBEPSU.HLP
+		DEFPRTR2.PPD
+		ICONLIB.DLL
+	
    Users of the ESP Print Pro software are able to install
+their "Samba Drivers" package for this purpose with no problem.
    14.7. Sources of CUPS drivers / PPDs
    On the internet you can find now many thousand CUPS-PPD
+files (with their companion filters), in many national languages,
+supporting more than 1.000 non-PostScript models.
    NOTE: the cupsomatic trick from Linuxprinting.org is
+working different from the other drivers. While the other drivers take the
+generic CUPS raster (produced by CUPS' own pstoraster PostScript RIP) as
+their input, cupsomatic "kidnaps" the PostScript inside CUPS, before
+RIP-ping, deviates it to an external Ghostscript installation (which now
+becomes the RIP) and gives it back to a CUPS backend once Ghostscript is
+finished. -- CUPS versions from 1.1.15 and later will provide their pstoraster
+PostScript RIP function again inside a system-wide Ghostscript
+installation rather than in "their own" pstoraster filter. (This
+CUPS-enabling Ghostscript version may be installed either as a
+patch to GNU or AFPL Ghostscript, or as a complete ESP Ghostscript package).
+However, this will not change the cupsomatic approach of guiding the printjob
+along a different path through the filtering system than the standard CUPS
+way...
    Once you installed a printer inside CUPS with one of the
+recommended methods (the lpadmin command, the web browser interface or one of
+the available GUI wizards), you can use cupsaddsmb to share the
+printer via Samba. cupsaddsmb prepares the driver files for
+comfortable client download and installation upon their first contact with
+this printer share.
    14.7.1. cupsaddsmb
    The cupsaddsmb command copies the needed files
+for convenient Windows client installations from the previously prepared CUPS
+data directory to your [print$] share. Additionally, the PPD
+associated with this printer is copied from /etc/cups/ppd/ to
+[print$].
    root#  cupsaddsmb -U root infotec_IS2027
+Password for root required to access localhost via SAMBA: [type in password 'secret']
    To share all printers and drivers, use the -a
+parameter instead of a printer name.
    Probably you want to see what's going on. Use the
+-v parameter to get a more verbose output:
    Probably you want to see what's going on. Use the
+-v parameter to get a more verbose output:
    Note: The following line shave been wrapped so that information is not lost.
+ 
+root#  cupsaddsmb -v -U root infotec_IS2027
+    Password for root required to access localhost via SAMBA:
+    Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put
+       /var/spool/cups/tmp/3cd1cc66376c0 W32X86/infotec_IS2027.PPD;put /usr/share/cups/drivers/
+       ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLLr
+       W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP'
+    added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
+    added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
+    added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
+    Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
+    NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
+    putting file /var/spool/cups/tmp/3cd1cc66376c0 as \W32X86/infotec_IS2027.PPD (17394.6 kb/s)
+      (average 17395.2 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPS5.DLL as \W32X86/ADOBEPS5.DLL (10877.4 kb/s)
+      (average 11343.0 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPSU.DLL as \W32X86/ADOBEPSU.DLL (5095.2 kb/s)
+      (average 9260.4 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPSU.HLP as \W32X86/ADOBEPSU.HLP (8828.7 kb/s)
+      (average 9247.1 kb/s)
+
+    Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put
+      /var/spool/cups/tmp/3cd1cc66376c0 WIN40/infotec_IS2027.PPD;put
+      /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put
+      /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put
+      /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put
+      /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put
+      /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put
+      /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
+    added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
+    added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
+    added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
+    Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
+    NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
+    putting file /var/spool/cups/tmp/3cd1cc66376c0 as \WIN40/infotec_IS2027.PPD (26091.5 kb/s)
+      (average 26092.8 kb/s)
+    putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (11241.6 kb/s)
+      (average 11812.9 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (16640.6 kb/s)
+      (average 14679.3 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (11285.6 kb/s)
+      (average 14281.5 kb/s)
+    putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (823.5 kb/s)
+      (average 12944.0 kb/s)
+    putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (19226.2 kb/s)
+      (average 13169.7 kb/s)
+    putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (18666.1 kb/s)
+      (average 13266.7 kb/s)
+
+    Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows NT x86"
+       "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"'
+    cmd = adddriver "Windows NT x86" "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:
+       ADOBEPSU.HLP:NULL:RAW:NULL"
+    Printer Driver infotec_IS2027 successfully installed.
+
+    Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows 4.0"
+       "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:
+       ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
+    cmd = adddriver "Windows 4.0" "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:
+       ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
+    Printer Driver infotec_IS2027 successfully installed.
+
+    Running command: rpcclient localhost -N -U'root%secret'
+       -c 'setdriver infotec_IS2027 infotec_IS2027'
+    cmd = setdriver infotec_IS2027 infotec_IS2027
+    Succesfully set infotec_IS2027 to driver infotec_IS2027.
+
+    root# 
    If you look closely, you'll discover your root password was transfered unencrypted over
+the wire, so beware! Also, if you look further her, you'll discover error messages like
+NT_STATUS_OBJECT_NAME_COLLISION in between. They occur, because
+the directories WIN40 and W32X86 already
+existed in the [print$] driver download share (from a previous driver
+installation). They are harmless here.
    Now your printer is prepared for the clients to use. From
+a client, browse to the CUPS/Samba server, open the "Printers"
+share, right-click on this printer and select "Install..." or
+"Connect..." (depending on the Windows version you use). Now their
+should be a new printer in your client's local "Printers" folder,
+named (in my case) "infotec_IS2027 on kdebitshop"
    NOTE: 
+cupsaddsmb will only reliably work i
+with CUPS version 1.1.15 or higher
+and Samba from 2.2.4. If it doesn't work, or if the automatic printer
+driver download to the clients doesn't succeed, you can still manually
+install the CUPS printer PPD on top of the Adobe PostScript driver on
+clients and then point the client's printer queue to the Samba printer
+share for connection, should you desire to use the CUPS networked
+PostScript RIP functions.
    14.8. The CUPS Filter Chains
    The following diagrams reveal how CUPS handles print jobs.
    #########################################################################
+#
+# CUPS in and of itself has this (general) filter chain (CAPITAL
+# letters are FILE-FORMATS or MIME types, other are filters (this is
+# true for pre-1.1.15 of pre-4.3 versions of CUPS and ESP PrintPro):
+#
+# SOMETHNG-FILEFORMAT
+#      |
+#      |
+#      V
+#     somethingtops
+#      |
+#      |
+#      V
+# APPLICATION/POSTSCRIPT
+#      |
+#      |
+#      V
+#     pstops
+#      |
+#      |
+#      V
+# APPLICATION/VND.CUPS-POSTSCRIPT
+#      |
+#      |
+#      V
+#     pstoraster   # as shipped with CUPS, independent from any Ghostscipt
+#      |           # installation on the system
+#      |  (= "postscipt interpreter")
+#      |
+#      V
+# APPLICATION/VND.CUPS-RASTER
+#      |
+#      |
+#      V
+#     rastertosomething  (f.e. Gimp-Print filters may be plugged in here)
+#      |   (= "raster driver")
+#      |
+#      V
+# SOMETHING-DEVICE-SPECIFIC
+#      |
+#      |
+#      V
+#     backend
+#
+#
+# ESP PrintPro has some enhanced "rastertosomething" filters as compared to
+# CUPS, and also a somewhat improved "pstoraster" filter.
+#
+# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
+#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
+#
+#########################################################################
    #########################################################################
+#
+# This is how "cupsomatic" comes into play:
+# =========================================
+#
+# SOMETHNG-FILEFORMAT
+#      |
+#      |
+#      V
+#    somethingtops
+#      |
+#      |
+#      V
+# APPLICATION/POSTSCRIPT
+#      |
+#      |
+#      V
+#    pstops
+#      |
+#      |
+#      V
+# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
+#      |                                          |
+#      |                                          V
+#      V                                         cupsomatic
+#    pstoraster                                  (constructs complicated
+#      |  (= "postscipt interpreter")            Ghostscript commandline
+#      |                                         to let the file be
+#      V                                         processed by a
+# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=s.th."
+#      |                                         call...)
+#      |                                          |
+#      V                                          |
+#    rastertosomething                          V
+#      |    (= "raster driver")     +-------------------------+
+#      |                            | Ghostscript at work.... |
+#      V                            |                         |
+# SOMETHING-DEVICE-SPECIFIC         *-------------------------+
+#      |                                          |
+#      |                                          |
+#      V                                          |
+#    backend >------------------------------------+
+#      |
+#      |
+#      V
+#    THE PRINTER
+#
+#
+# Note, that cupsomatic "kidnaps" the printfile after the
+# "APPLICATION/VND.CUPS-POSTSCRPT" stage and deviates it through
+# the CUPS-external, systemwide Ghostscript installation, bypassing the
+# "pstoraster" filter (therefor also bypassing the CUPS-raster-drivers
+# "rastertosomething", and hands the rasterized file directly to the CUPS
+# backend...
+#
+# cupsomatic is not made by the CUPS developers. It is an independent
+# contribution to printing development, made by people from
+# Linuxprinting.org. (see also http://www.cups.org/cups-help.html)
+#
+# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
+#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
+#
+#########################################################################
    #########################################################################
+#
+# And this is how it works for ESP PrintPro from 4.3:
+# ===================================================
+#
+# SOMETHNG-FILEFORMAT
+#      |
+#      |
+#      V
+#     somethingtops
+#      |
+#      |
+#      V
+# APPLICATION/POSTSCRIPT
+#      |
+#      |
+#      V
+#     pstops
+#      |
+#      |
+#      V
+# APPLICATION/VND.CUPS-POSTSCRIPT
+#      |
+#      |
+#      V
+#     gsrip
+#      |  (= "postscipt interpreter")
+#      |
+#      V
+# APPLICATION/VND.CUPS-RASTER
+#      |
+#      |
+#      V
+#     rastertosomething  (f.e. Gimp-Print filters may be plugged in here)
+#      |   (= "raster driver")
+#      |
+#      V
+# SOMETHING-DEVICE-SPECIFIC
+#      |
+#      |
+#      V
+#     backend
+#
+# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
+#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
+#
+#########################################################################
    #########################################################################
+#
+# This is how "cupsomatic" would come into play with ESP PrintPro:
+# ================================================================
+#
+#
+# SOMETHNG-FILEFORMAT
+#      |
+#      |
+#      V
+#    somethingtops
+#      |
+#      |
+#      V
+# APPLICATION/POSTSCRIPT
+#      |
+#      |
+#      V
+#    pstops
+#      |
+#      |
+#      V
+# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
+#      |                                          |
+#      |                                          V
+#      V                                         cupsomatic
+#    gsrip                                       (constructs complicated
+#      |  (= "postscipt interpreter")            Ghostscript commandline
+#      |                                         to let the file be
+#      V                                         processed by a
+# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=s.th."
+#      |                                         call...)
+#      |                                          |
+#      V                                          |
+#    rastertosomething                          V
+#      |   (= "raster driver")      +-------------------------+
+#      |                            | Ghostscript at work.... |
+#      V                            |                         |
+# SOMETHING-DEVICE-SPECIFIC         *-------------------------+
+#      |                                          |
+#      |                                          |
+#      V                                          |
+#    backend >------------------------------------+
+#      |
+#      |
+#      V
+#    THE PRINTER
+#
+# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
+#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
+#
+#########################################################################
    #########################################################################
+#
+# And this is how it works for CUPS from 1.1.15:
+# ==============================================
+#
+# SOMETHNG-FILEFORMAT
+#      |
+#      |
+#      V
+#     somethingtops
+#      |
+#      |
+#      V
+# APPLICATION/POSTSCRIPT
+#      |
+#      |
+#      V
+#     pstops
+#      |
+#      |
+#      V
+# APPLICATION/VND.CUPS-POSTSCRIPT-----+
+#                                     |
+#                  +------------------v------------------------------+
+#                  | Ghostscript                                     |
+#                  | at work...                                      |
+#                  | (with                                           |
+#                  | "-sDEVICE=cups")                                |
+#                  |                                                 |
+#                  |         (= "postscipt interpreter")             |
+#                  |                                                 |
+#                  +------------------v------------------------------+
+#                                     |
+#                                     |
+# APPLICATION/VND.CUPS-RASTER >-------+
+#      |
+#      |
+#      V
+#     rastertosomething
+#      |   (= "raster driver")
+#      |
+#      V
+# SOMETHING-DEVICE-SPECIFIC
+#      |
+#      |
+#      V
+#     backend
+#
+#
+# NOTE: since version 1.1.15 CUPS "outsourced" the pstoraster process to
+#       Ghostscript. GNU Ghostscript needs to be patched to handle the
+#       CUPS requirement; ESP Ghostscript has this builtin. In any case,
+#       "gs -h" needs to show up a "cups" device. pstoraster is now a
+#       calling an appropriate "gs -sDEVICE=cups..." commandline to do
+#       the job. It will output "application/vnd.cup-raster", which will
+#       be finally processed by a CUPS raster driver "rastertosomething"
+#       Note the difference to "cupsomatic", which will *not* output
+#       CUPS-raster, but a final version of the printfile, ready to be
+#       sent to the printer. cupsomatic also doesn't use the "cups"
+#       devicemode in Ghostscript, but one of the classical devicemodes....
+#
+# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
+#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
+#
+#########################################################################
    #########################################################################
+#
+# And this is how it works for CUPS from 1.1.15, with cupsomatic included:
+# ========================================================================
+#
+# SOMETHNG-FILEFORMAT
+#      |
+#      |
+#      V
+#     somethingtops
+#      |
+#      |
+#      V
+# APPLICATION/POSTSCRIPT
+#      |
+#      |
+#      V
+#     pstops
+#      |
+#      |
+#      V
+# APPLICATION/VND.CUPS-POSTSCRIPT-----+
+#                                     |
+#                  +------------------v------------------------------+
+#                  | Ghostscript        . Ghostscript at work....    |
+#                  | at work...         . (with "-sDEVICE=           |
+#                  | (with              .            s.th."        |
+#                  | "-sDEVICE=cups")   .                            |
+#                  |                    .                            |
+#                  | (CUPS standard)    .      (cupsomatic)          |
+#                  |                    .                            |
+#                  |          (= "postscript interpreter")           |
+#                  |                    .                            |
+#                  +------------------v--------------v---------------+
+#                                     |              |
+#                                     |              |
+# APPLICATION/VND.CUPS-RASTER >-------+              |
+#      |                                             |
+#      |                                             |
+#      V                                             |
+#     rastertosomething                            |
+#      |   (= "raster driver")                       |
+#      |                                             |
+#      V                                             |
+# SOMETHING-DEVICE-SPECIFIC >------------------------+
+#      |
+#      |
+#      V
+#     backend
+#
+#
+# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
+#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
+#
+##########################################################################
    14.9. CUPS Print Drivers and Devices
    CUPS ships with good support for HP LaserJet type printers. You can install
+the driver as follows:
+
+
    • 	lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd
+	
    
+
+(The "-m" switch will retrieve the "laserjet.ppd" from the standard repository
+for not-yet-installed-PPDs, which CUPS typically stores in 
+/usr/share/cups/model. Alternatively, you may use
+"-P /absolute/filesystem/path/to/where/there/is/PPD/your.ppd").
    14.9.1. Further printing steps
    Always also consult the database on linuxprinting.org for all recommendations
+about which driver is best used for each printer:
    http://www.linuxprinting.org/printer_list.cgi
    There select your model and click on "Show". You'll arrive at a page listing
+all drivers working with your model. There will always be *one* 
+recommended one. Try this one first. In your case
+("HP LaserJet 4 Plus"), you'll arrive here:
    http://www.linuxprinting.org/show_printer.cgi?recnum=75104
    The recommended driver is "ljet4". It has a link to the page for the ljet4
+driver too:
    http://www.linuxprinting.org/show_driver.cgi?driver=ljet4
    On the driver's page, you'll find important and detailed info about how to use
+that driver within the various available spoolers. You can generate a PPD for
+CUPS. The PPD contains all the info about how to use your model and the driver;
+this is, once installed, working transparently for the user -- you'll only
+need to choose resolution, paper size etc. from the web-based menu or from
+the print dialog GUI or from the commandline...
    On the driver's page, choose to use the "PPD-O-Matic" online PPD generator
+program. Select your model and click "Generate PPD file". When you safe the
+appearing ASCII text file, don't use "cut'n'past" (as it could possiblly corrupt
+line endings and tabs), but use "Save as..." in your browser's menu. Save it
+at "/some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"
    Then install the printer:
        "lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E \
+          -P /some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"
    Note, that for all the "Foomatic-PPDs" from Linuxprinting.org, you also need
+a special "CUPS filter" named "cupsomatic". Get the latest version of
+"cupsomatic" from:
    http://www.linuxprinting.org/cupsomatic
    This needs to be copied to /usr/lib/cups/filter/cupsomatic
+and be made world executable. This filter is needed to read and act upon the
+specially encoded Foomatic comments, embedded in the printfile, which in turn
+are used to construct (transparently for you, the user) the complicated
+ghostscript command line needed for your printer/driver combo.
    You can have a look at all the options for the Ghostscript commandline supported
+by your printer and the ljet4 driver by going to the section "Execution details",
+selecting your model (Laserjet 4 Plus) and clicking on "Show execution details".
+This will bring up this web page:
    http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details
    The ingenious thing is that the database is kept current. If there
+is a bug fix and an improvement somewhere in the database, you will
+always get the most current and stable and feature-rich driver by following
+the steps described above.
    Till Kamppeter from MandrakeSoft is doing an excellent job here that too few
+people are aware of. (So if you use it often, please send him a note showing
+your appreciation).
    The latest and greatest improvement now is support for "custom page sizes"
+for all those printers which support it.
    "cupsomatic" is documented here:
    http://www.linuxprinting.org/cups-doc.html
    More printing tutorial info may be found here:
    http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/
    Note, that *all* the Foomatic drivers listed on Linuxprinting.org (now
+approaching the "all-time high" number of 1.000 for the supported models)
+are using a special filtering chain involving Ghostscript, as described
+in this document.
    Summary - You need:
    A "foomatic+something" PPD is not enough to print with CUPS (but it is *one* important component)
    The "cupsomatic" filter script (Perl) in /usr/lib/cups/filters/
    Perl to make cupsomatic run
    Ghostscript (because it is called and controlled by the PPD/cupsomatic combo in a way to fit your printermodel/driver combo.
    Ghostscript *must*, depending on the driver/model, contain support for a certain "device" (as shown by "gs -h")
    In the case of the "hpijs" driver, you need a Ghostscript version, which
+has "ijs" amongst its supported devices in "gs -h". In the case of
+"hpijs+foomatic", a valid ghostscript commandline would be reading like this:
           gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs       \
+             -sIjsServer=hpijsPageSize -dDuplex=Duplex Model        \
+             -rResolution,PS:MediaPosition=InputSlot -dIjsUseOutputFD \
+             -sOutputFile=- -
    Note, that with CUPS and the "hpijs+foomatic" PPD (plus Perl and cupsomatic)
+you don't need to remember this. You can choose the available print options
+thru a GUI print command (like "glp" from ESP's commercially supported
+PrintPro software, or KDE's "kprinter", or GNOME's "gtklp" or the independent
+"xpp") or the CUPS web interface via human-readable drop-down selection
+menus.
    If you use "ESP Ghostscript" (also under the GPL, provided by Easy Software
+Products, the makers of CUPS, downloadable from
+http://www.cups.org/software.html,
+co-maintained by the developers of linuxprinting.org), you are guaranteed to
+have in use the most uptodate, bug-fixed, enhanced and stable version of a Free
+Ghostscript. It contains support for ~300 devices, whereas plain vanilla
+GNU Ghostscript 7.05 only has ~200.
    If you print only one CUPS test page, from the web interface and when you try to
+print a windows test page, it acts like the job was never sent:
+
+
    Can you print "standard" jobs from the CUPS machine?
    Are the jobs from Windows visible in the Web interface on CUPS (http://localhost:631/)?
    Most important: What kind of printer driver are you using on the Windows clients?
    
+
+You can try to get a more detailed debugging info by setting "LogLevel debug" in
+/etc/cups/cupsd.conf, re-start cupsd and investigate /var/log/cups/error_log
+for the whereabouts of your Windows-originating printjobs:
    what does the "auto-typing" line say? which is the "MIME type" CUPS thinks is arriving from the Windows clients?
    are there "filter" available for this MIME type?
    are there "filter rules" defined in "/etc/cups/mime.convs" for this MIME type?
    14.10. Limiting the number of pages users can print
    The feature you want is dependent on the real print subsystem you're using.
+Samba's part is always to receive the job files from the clients (filtered
+*or* unfiltered) and hand it over to this printing subsystem.
    Of course one could "hack" things with one's own scripts.
    But there is CUPS (Common Unix Printing System). CUPS supports "quotas".
+Quotas can be based on sizes of jobs or on the number of pages or both,
+and are spanning any time period you want.
    This is an example command how root would set a print quota in CUPS,
+assuming an existing printer named "quotaprinter":
      lpadmin -p quotaprinter -o job-quota-period=604800 -o job-k-limit=1024 \
+       -o job-page-limit=100
    This would limit every single user to print 100 pages or 1024 KB of
+data (whichever comes first) within the last 604.800 seconds ( = 1 week).
    For CUPS to count correctly, the printfile needs to pass the CUPS "pstops" filter,
+otherwise it uses a "dummy" count of "1". Some printfiles don't pass it
+(eg: image files) but then those are mostly 1 page jobs anyway. This also means,
+proprietary drivers for the target printer running on the client computers and
+CUPS/Samba then spooling these files as "raw" (i.e. leaving them untouched, not
+filtering them), will be counted as "1-pagers" too!
    You need to send PostScript from the clients (i.e. run a PostScript driver there)
+for having the chance to get accounting done. If the printer is a non-PostScript model,
+you need to let CUPS do the job to convert the file to a print-ready format for the
+target printer. This will be working for currently ~1.000 different printer models, see
         http://www.linuxprinting.org/printer_list.cgi
    Before CUPS-1.1.16 your only option was to use the Adobe PostScript
+Driver on the Windows clients. The output of this driver was not always
+passed thru the "pstops" filter on the CUPS/Samba side, and therefor was
+not counted correctly (the reason is that it often --- depending on the
+"PPD" being used --- did write a "PJL"-header in front of the real
+PostScript which made CUPS to skip the pstops and go directy to
+the "pstoraster" stage).
    From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver
+for Windows NT/2K/XP clients" (it is tagged in the download area of
+http://www.cups.org/ as the "cups-samba-1.1.16.tar.gz" package).
+It is *not* working for Win9x/ME clients. But it:
    it guarantees to not write an PJL-header
    it guarantees to still read and support all PJL-options named in the driver PPD with its own means
    it guarantees the file going thru the "pstops" filter on the CUPS/Samba server
    it guarantees to page-count correctly the printfile
    You can read more about the setup of this combination in the
+manpage for "cupsaddsmb" (only present with CUPS installed, only
+current with CUPS 1.1.16).
    These are the items CUPS logs in the "page_log" for every single *page* of a job:
    Printer name
    User name
    Job ID
    Time of printing
    the page number
    the number of copies
    a billing info string (optional)
    Here is an extract of my CUPS server's page_log file to illustrate
+the format and included items:
    	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 1 2  #marketing
+	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 2 2  #marketing
+	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 3 2  #marketing
+	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 4 2  #marketing
+	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 5 2  #marketing
+	infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 6 2  #marketing
    This was Job ID "40", printed on "infotec_IS2027" by user "kurt", a 6-page job
+printed in 2 copies and billed to "#marketing"...
    What flaws or shortcomings are there?
    the ones named above
    	CUPS really counts the job pages being *processsed in software*
+	(going thru the "RIP") rather than the physical sheets successfully
+	leaving the printing device -- if there is a jam while printing
+	the 5th sheet out of 1000 and the job is aborted by the printer,
+	the "page count" will still show the figure of 1000 for that job
+	
    	all quotas are the same for all users (no flexibility to give the
+	boss a higher quota than the clerk) no support for groups
+	
    	no means to read out the current balance or "used-up" number of current quota
+	
    	a user having used up 99 sheets of 100 quota will still be able to send and print a 1.000 sheet job
+	
    	a user being denied a job because of a filled-up quota doesn't get a meaningful
+	error message from CUPS other than "client-error-not-possible".
+	
    But this is the best system out there currently. And there are
+huge improvements under development:
    page counting will go into the "backends" (these talk
+	directly to the printer and will increase the count in sync with the
+	 actual printing process -- a jam at the 5th sheet will lead to a stop in the counting)
    quotas will be handled more flexibly
    probably there will be support for users to inquire their "accounts" in advance
    probably there will be support for some other tools around this topic
    Other than the current stage of the CUPS development, I don't
+know any other ready-to-use tool which you could consider.
    You can download the driver files from
+http://www.cups.org/software.html.
+It is a separate package from the CUPS base software files, tagged as "CUPS 1.1.16
+Windows NT/2k/XP Printer Driver for SAMBA (tar.gz, 192k)". The filename to
+download is "cups-samba-1.1.16.tar.gz". Upon untar-/unzip-ping it will reveal
+the files:
    		   cups-samba.install
+	   cups-samba.license
+	   cups-samba.readme
+	   cups-samba.remove
+	   cups-samba.ss
+	
+	
    These have been packaged with the ESP meta packager software "EPM". The
+*.install and *.remove files are simple shell script, which untars the
+*.ss (which is nothing else than a tar-archive) and puts its contents
+into /usr/share/cups/drivers/. Its contents are 3 files:
    		   cupsdrvr.dll
+	   cupsui.dll
+	   cups.hlp
+	
+	
    Due to a bug one CUPS release puts the cups.hlp
+into /usr/share/drivers/ instead of
+/usr/share/cups/drivers/. To work around this, copy/move
+the file after running the "./cups-samba.install" script manually to the right place:
    	 cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/
+	
+	
    This new CUPS PostScript driver is currently binary-only, but free
+no source code is provided (yet). The reason is this: it has
+been developed with the help of the Microsoft Driver Developer Kit (DDK)
+and compiled with Microsoft Visual Studio 6. It is not clear to the driver
+developers if they are allowed to distribute the whole of the source code
+as Free Software. However, they will likely release the "diff" in source
+code under the GPL, so anybody with a license of Visual Studio and a DDK
+will be able to compile for him/herself.
    Once you have run the install script (and possibly manually moved the
+"cups.hlp" file to "/usr/share/cups/drivers/"), the driver is ready to be
+put into Samba's [print$] share (which often maps to "/etc/samba/drivers/"
+and contains a subdir tree with WIN40 and W32X86 branches), by running
+"cupsaddsmb" (see also "man cupsaddsmb" for CUPS 1.1.16). [Don't forget to
+put root into the smbpasswd file by running "smbpasswd" should you run
+this whole procedure for the first time.] Once the driver files are in the
+[print$] share, they are ready to be downloaded and installed by the
+Win NT/2k/XP clients.
    	Win 9x/ME clients won't work with this driver. For these you'd
+	still need to use the ADOBE*.* drivers as previously.
+	
    	It is not harming if you've still the ADOBE*.* driver files from
+	previous installations in the "/usr/share/cups/drivers/" directory.
+	The new cupsaddsmb (from 1.1.16) will automatically use the
+	"newest" installed driver (which here then is the CUPS drivers).
+	
    	Should your Win clients have had the old ADOBE*.* files and the
+	Adobe PostScript drivers installed, the download and installation
+	of the new CUPS PostScript driver for Windows NT/2k/XP will fail
+	at first.
+	
    	It is not enough to "delete" the printer (as the driver files
+	will still be kept by the clients and re-used if you try to
+	re-install the printer). To really get rid of the Adobe driver
+	files on the clients, open the "Printers" folder (possibly via
+	"Start --> Settings --> Control Panel --> Printers"), right-click
+	onto the folder background and select "Server Properties". A
+	new dialog opens; select the "Drivers" tab; on the list select
+	the driver you want to delete and click on the "Delete" button.
+	(This will only work if there is no single printer left which
+	uses that particular driver -- you need to "delete" all printers
+	using this driver in the "Printers" folder first.)
+	
    	Once you have successfully downloaded the CUPS PostScript driver
+	to a client, you can easily switch all printers to this one
+	by proceeding as described elsewhere in the "Samba HOWTO
+	Collection" to change a driver for an existing printer.
+	
    What are the benefits with the "CUPS PostScript driver for Windows NT/2k/XP"
+as compared to the Adobe drivers?
    • 	no hassle with the Adobe EULA
+	
    • 	no hassle with the question "where do I get the ADOBE*.* driver files from?"
+	
    • 	the Adobe drivers (depending on the printer PPD associated with them)
+	often put a PJL header in front of the core PostScript part of the print
+	file (thus the file starts with "1B%-12345X" or "escape%-12345X"
+	instead of "%!PS"). This leads to the CUPS daemon autotyping the
+	arriving file as a print-ready file, not requiring a pass thru the
+	"pstops" filter (to speak more technical, it is not regarded as the
+	generic MIME type "application/postscript", but as the more special
+	MIME type "application/cups.vnd-postscript"), which therefore also
+	leads to the page accounting in "/var/log/cups/page_log" not receiving
+	the exact mumber of pages; instead the dummy page number of "1" is
+	logged in a standard setup)
+	
    • 	the Adobe driver has more options to "mis-configure" the PostScript
+	generated by it (like setting it inadvertedly to "Optimize for Speed",
+	instead of "Optimize for Portability", which could lead to CUPS being
+	unable to process it)
+	
    • 	the CUPS PostScript driver output sent by Windows clients to the CUPS
+	server will be guaranteed to be auto-typed as generic MIME type
+	"application/postscript", thusly passing thru the CUPS "pstops" filter
+	and logging the correct number of pages in the page_log for accounting
+	and quota purposes
+	
    • 	the CUPS PostScript driver supports the sending of additional print
+	options by the Win NT/2k/XP clients, such as naming the CUPS standard
+	banner pages (or the custom ones, should they be installed at the time
+	of driver download), using the CUPS "page-label" option, setting a
+	job-priority and setting the scheduled time of printing (with the option
+	to support additional useful IPP job attributes in the future).
+	
    • 	the CUPS PostScript driver supports the inclusion of the new
+	"*cupsJobTicket" comments at the beginnig of the PostScript file (which
+	could be used in the future for all sort of beneficial extensions on
+	the CUPS side, but which will not disturb any other application as those
+	will regard it as a comment and simply ignore it).
+	
    • 	the CUPS PostScript driver will be the heart of the fully fledged CUPS
+	IPP client for Windows NT/2k/XP to be released soon (probably alongside
+	the first Beta release for CUPS 1.2).
+	
    14.11. Advanced Postscript Printing from MS Windows
    Let the Windows Clients use a PostScript driver to deliver poistscript to
+the samba print server (just like any Linux or Unix Client would also use
+PostScript to send to the server)
    Make the Unix printing subsystem to which Samba sends the job convert the
+incoming PostScript files to the native print format of the target printers
+(would be PCL if you have an HP printer)
    Now if you are afraid that this would just mean using a *Generic* PostScript
+driver for the clients that has no Simplex/Duplex selection, and no paper tray
+choice, but you need them to be able to set up print jobs, with all the bells
+and whistles of your printers:-
    Not possible with traditional spooling systems
    	But perfectly supported by CUPS (which uses "PPD" files to
+	describe how to control the print options for PostScript and
+	non-PostScript devices alike...
+	
    CUPS PPDs are working perfectly on Windows clients who use Adobe PostScript
+drivers (or the new CUPS PostScript driver for Windows NT/2K/XP). Clients can use
+them to setup the job to their liking and CUPS will use the received job options
+to make the (PCL-, ESC/P- or PostScript-) printer behave as required.
    If you want to have the additional benefit of page count logging and accounting
+then the CUPS PostScript driver is the best choice (better than the Adobe one).
    If you want to make the drivers downloadable for the clients then "cupsaddsmb" is
+your friend. It will setup the [print$] share on the Samba host to be ready to serve
+the clients for a "point and print" driver installation.
    What strings are attached?
    There are some. But, given the sheer CPU power you can buy nowadays,
+these can be overcome easily. The strings:
    Well, if the CUPS/Samba side will have to print to many printers serving many users,
+you probably will need to set up a second server (which can do automatic load balancing
+with the first one, plus a degree of fail-over mechanism). Converting the incoming
+PostScript jobs, "interpreting" them for non-PostScript printers, amounts to the work
+of a "RIP" (Raster Image Processor) done in software. This requires more CPU and RAM
+than for the mere "raw spooling" task your current setup is solving. It all depends
+on the avarage and peak printing load the server should be able to handle.
    14.12. Auto-Deletion of CUPS spool files
    Samba print files pass thru two "spool" directories. One the incoming directory
+managed by Samba, (set eg: in the path = /var/spool/samba directive in the [printers]
+section of smb.conf). Second is the spool directory of your UNIX print subsystem.
+For CUPS it is normally "/var/spool/cups/", as set by the cupsd.conf directive
+"RequestRoot /var/spool/cups".
    I am not sure, which one of your directories keeps the files.  From what you say,
+it is most likely the Samba part.
    For the CUPS part, you may want to consult:
    http://localhost:631/sam.html#PreserveJobFiles
    http://localhost:631/sam.html#PreserveJobHistory
    http://localhost:631/sam.html#MaxJobs
    There are the settings described for your CUPS daemon, which could lead to completed
+job files not being deleted.
    "PreserveJobHistory Yes" -- keeps some details of jobs in
+cupsd's mind (well it keeps the "c12345", "c12346" etc. files
+in the CUPS spool directory, which do a similar job as the
+old-fashioned BSD-LPD control files). This is set to "Yes"
+as a default.
    "PreserveJobFiles Yes" -- keeps the job files themselves in
+cupsd's mind (well it keeps the "d12345", "d12346" etc. files
+in the CUPS spool directory...). This is set to "No" as the
+CUPS default.
    "MaxJobs 500" -- this directive controls the maximum number
+of jobs that are kept in memory. Once the number of jobs
+reaches the limit, the oldest completed job is automatically
+purged from the system to make room for the new one. If all
+of the known jobs are still pending or active then the new
+job will be rejected. Setting the maximum to 0 disables this
+functionality. The default setting is 0.
    (There are also additional settings for "MaxJobsPerUser" and
+"MaxJobsPerPrinter"...)
    For everything to work as announced, you need to have three things:
    	a Samba-smbd which is compiled against "libcups" (Check on Linux by running ldd `which smbd`)
+	
    	a Samba-smb.conf setting of printing = cups
+	
    	another Samba-smb.conf setting of printcap = cups
+	
    Note, that in this case all other manually set printing-related
+commands (like "print command", "lpq command", "lprm command",
+"lppause command" or "lpresume command") are ignored and they
+should normally have no influence what-so-ever on your printing.
    If you want to do things manually, replace the "printing = cups"
+by "printing = bsd". Then your manually set commands may work
+(haven't tested this), and a "print command = lp -d %P %s; rm %s"
+may do what you need.
    You forgot to mention the CUPS version you're using. If you did
+set things up as described in the man pages, then the Samba
+spool files should be deleted. Otherwise it may be a bug. On
+the CUPS side, you can control the behaviour as described
+above.
    If you have more problems, post the output of these commands:
       grep -v ^# /etc/cups/cupsd.conf | grep -v ^$
+   grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"
    (adapt paths as needed). These commands sanitize the files
+and cut out the empty lines and lines with comments, providing
+the "naked settings" in a compact way.
    PrevHomeNext
    Printing SupportUpUnified Logons between Windows NT and UNIX using Winbind
    
\ No newline at end of file
diff --git a/docs/htmldocs/domain-member.html b/docs/htmldocs/domain-member.html
new file mode 100644
index 0000000000..97eaaf799d
--- /dev/null
+++ b/docs/htmldocs/domain-member.html
@@ -0,0 +1,446 @@
+
+Samba as a NT4 or Win2k domain member
    SAMBA Project Documentation
    PrevNext
    Chapter 10. Samba as a NT4 or Win2k domain member
    10.1. Joining an NT Domain with Samba 3.0
    Assume you have a Samba 3.0 server with a NetBIOS name of 
+	SERV1 and are joining an or Win2k NT domain called
+	DOM, which has a PDC with a NetBIOS name
+	of DOMPDC and two backup domain controllers 
+	with NetBIOS names DOMBDC1 and DOMBDC2
+	.
    Firstly, you must edit your smb.conf file to tell Samba it should
+	now use domain security.
    Change (or add) your 	security = line in the [global] section 
+	of your smb.conf to read:
    security = domain
    Next change the 	workgroup = line in the [global] section to read: 
    workgroup = DOM
    as this is the name of the domain we are joining. 
    You must also have the parameter 	encrypt passwords set to yes
+	 in order for your users to authenticate to the NT PDC.
    Finally, add (or modify) a 	password server = line in the [global]
+	section to read: 
    password server = DOMPDC DOMBDC1 DOMBDC2
    These are the primary and backup domain controllers Samba 
+	will attempt to contact in order to authenticate users. Samba will 
+	try to contact each of these servers in order, so you may want to 
+	rearrange this list in order to spread out the authentication load 
+	among domain controllers.
    Alternatively, if you want smbd to automatically determine 
+	the list of Domain controllers to use for authentication, you may 
+	set this line to be :
    password server = *
    This method, allows Samba to use exactly the same
+        mechanism that NT does. This 
+	method either broadcasts or uses a WINS database in order to
+	find domain controllers to authenticate against.
    In order to actually join the domain, you must run this
+        command:
    root# net rpc join -S DOMPDC
+	-UAdministrator%password
    as we are joining the domain DOM and the PDC for that domain 
+	(the only machine that has write access to the domain SAM database) 
+	is DOMPDC. The Administrator%password is 
+	the login name and password for an account which has the necessary 
+	privilege to add machines to the domain.  If this is successful 
+	you will see the message:
    Joined domain DOM.
+	or Joined 'SERV1' to realm 'MYREALM'
+	
    in your terminal window. See the 	net(8) man page for more details.
    This process joins the server to thedomain
+	without having to create the machine trust account on the PDC
+	beforehand.
    This command goes through the machine account password 
+	change protocol, then writes the new (random) machine account 
+	password for this Samba server into a file in the same directory 
+	in which an smbpasswd file would be stored - normally :
    /usr/local/samba/private/secrets.tdb
    This file is created and owned by root and is not 
+	readable by any other user. It is the key to the domain-level 
+	security for your system, and should be treated as carefully 
+	as a shadow password file.
    Finally, restart your Samba daemons and get ready for 
+	clients to begin using domain security!
    10.2. Why is this better than security = server?
    Currently, domain security in Samba doesn't free you from 
+	having to create local Unix users to represent the users attaching 
+	to your server. This means that if domain user DOM\fred
+	 attaches to your domain security Samba server, there needs 
+	to be a local Unix user fred to represent that user in the Unix 
+	filesystem. This is very similar to the older Samba security mode 
+	security = server, 
+	where Samba would pass through the authentication request to a Windows 
+	NT server in the same way as a Windows 95 or Windows 98 server would.
+	
    Please refer to the Winbind 
+	paper for information on a system to automatically
+	assign UNIX uids and gids to Windows NT Domain users and groups.
+	This code is available in development branches only at the moment,
+	but will be moved to release branches soon.
    The advantage to domain-level security is that the 
+	authentication in domain-level security is passed down the authenticated 
+	RPC channel in exactly the same way that an NT server would do it. This 
+	means Samba servers now participate in domain trust relationships in 
+	exactly the same way NT servers do (i.e., you can add Samba servers into 
+	a resource domain and have the authentication passed on from a resource
+	domain PDC to an account domain PDC.
    In addition, with security = server every Samba 
+	daemon on a server has to keep a connection open to the 
+	authenticating server for as long as that daemon lasts. This can drain 
+	the connection resources on a Microsoft NT server and cause it to run 
+	out of available connections. With security = domain, 
+	however, the Samba daemons connect to the PDC/BDC only for as long 
+	as is necessary to authenticate the user, and then drop the connection, 
+	thus conserving PDC connection resources.
    And finally, acting in the same manner as an NT server 
+	authenticating to a PDC means that as part of the authentication 
+	reply, the Samba server gets the user identification information such 
+	as the user SID, the list of NT groups the user belongs to, etc. 
     Much of the text of this document 
+	was first published in the Web magazine  	
+	LinuxWorld as the article Doing 
+	the NIS/NT Samba.
    PrevHomeNext
    Samba as a ADS domain memberUpAdvanced Configuration
    
\ No newline at end of file
diff --git a/docs/htmldocs/editreg.1.html b/docs/htmldocs/editreg.1.html
new file mode 100644
index 0000000000..571e50560c
--- /dev/null
+++ b/docs/htmldocs/editreg.1.html
@@ -0,0 +1,142 @@
+
+editreg
    editreg
    Name
    editreg -- A utility to report and change SIDs in registry files
+	
    Synopsis
    editreg  [-v] [-c file] {file}
    DESCRIPTION
    This tool is part of the Samba(7) suite.
    editreg is a utility that 
+	can visualize windows registry files (currently only NT4) and apply 
+	so-called commandfiles to them. 
+	
    OPTIONS
    registry_file
    Registry file to view or edit.  
    -v,--verbose
    Increases verbosity of messages. 
+		
    -c commandfile
    Read commands to execute on registry_file from commandfile. Currently not yet supported!
+		
    -h|--help
    Print a summary of command line options.
    VERSION
    This man page is correct for version 3.0 of the Samba 
+	suite.
    AUTHOR
    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.
    The editreg man page was written by Jelmer Vernooij. 
    
\ No newline at end of file
diff --git a/docs/htmldocs/interdomaintrusts.html b/docs/htmldocs/interdomaintrusts.html
new file mode 100644
index 0000000000..10efda81a2
--- /dev/null
+++ b/docs/htmldocs/interdomaintrusts.html
@@ -0,0 +1,451 @@
+
+Interdomain Trust Relationships
    SAMBA Project Documentation
    PrevNext
    Chapter 19. Interdomain Trust Relationships
    Samba-3 supports NT4 style domain trust relationships. This is feature that many sites
+will want to use if they migrate to Samba-3 from and NT4 style domain and do NOT want to
+adopt Active Directory or an LDAP based authentication back end. This section explains
+some background information regarding trust relationships and how to create them. It is now
+possible for Samba-3 to NT4 trust (and vice versa), as well as Samba3 to Samba3 trusts.
    19.1. Trust Relationship Background
    MS Windows NT3.x/4.0 type security domains employ a non-hierarchical security structure.
+The limitations of this architecture as it affects the scalability of MS Windows networking
+in large organisations is well known. Additionally, the flat-name space that results from
+this design significantly impacts the delegation of administrative responsibilities in
+large and diverse organisations.
    Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means
+of circumventing the limitations of the older technologies. Not every organisation is ready
+or willing to embrace ADS. For small companies the older NT4 style domain security paradigm
+is quite adequate, there thus remains an entrenched user base for whom there is no direct
+desire to go through a disruptive change to adopt ADS.
    Microsoft introduced with MS Windows NT the ability to allow differing security domains
+to affect a mechanism so that users from one domain may be given access rights and privileges
+in another domain. The language that describes this capability is couched in terms of
+Trusts. Specifically, one domain will trust the users
+from another domain. The domain from which users are available to another security domain is
+said to be a trusted domain. The domain in which those users have assigned rights and privileges
+is the trusting domain. With NT3.x/4.0 all trust relationships are always in one direction only,
+thus if users in both domains are to have privileges and rights in each others' domain, then it is
+necessary to establish two (2) relationships, one in each direction.
    In an NT4 style MS security domain, all trusts are non-transitive. This means that if there
+are three (3) domains (let's call them RED, WHITE, and BLUE) where RED and WHITE have a trust
+relationship, and WHITE and BLUE have a trust relationship, then it holds that there is no
+implied trust between the RED and BLUE domains. ie: Relationships are explicit and not
+transitive.
    New to MS Windows 2000 ADS security contexts is the fact that trust relationships are two-way
+by default. Also, all inter-ADS domain trusts are transitive. In the case of the RED, WHITE and BLUE
+domains above, with Windows 2000 and ADS the RED and BLUE domains CAN trust each other. This is
+an inherent feature of ADS domains. Samba-3 implements MS Windows NT4
+style Interdomain trusts and interoperates with MS Windows 200x ADS
+security domains in similar manner to MS Windows NT4 style domains.
    19.2. Native MS Windows NT4 Trusts Configuration
    There are two steps to creating an interdomain trust relationship.
    19.2.1. NT4 as the Trusting Domain (ie. creating the trusted account)
    For MS Windows NT4, all domain trust relationships are configured using the Domain User Manager.
+To affect a two way trust relationship it is necessary for each domain administrator to make
+available (for use by an external domain) it's security resources. This is done from the Domain
+User Manager Policies entry on the menu bar. From the Policy menu, select Trust Relationships, then
+next to the lower box that is labelled "Permitted to Trust this Domain" are two buttons, "Add" and
+"Remove". The "Add" button will open a panel in which needs to be entered the remote domain that
+will be able to assign user rights to your domain. In addition it is necessary to enter a password
+that is specific to this trust relationship. The password needs to be
+typed twice (for standard confirmation).
    19.2.2. NT4 as the Trusted Domain (ie. creating trusted account's password)
    A trust relationship will work only when the other (trusting) domain makes the appropriate connections
+with the trusted domain. To consumate the trust relationship the administrator will launch the
+Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the
+"Add" button that is next to the box that is labelled "Trusted Domains". A panel will open in
+which must be entered the name of the remote domain as well as the password assigned to that trust.
    19.3. Configuring Samba NT-style Domain Trusts
    This description is meant to be a fairly short introduction about how to set up a Samba server so
+that it could participate in interdomain trust relationships. Trust relationship support in Samba
+is in its early stage, so lot of things don't work yet.
    Each of the procedures described below is treated as they were performed with Windows NT4 Server on
+one end. The remote end could just as well be another Samba-3 domain. It can be clearly seen, after
+reading this document, that combining Samba-specific parts of what's written below leads to trust
+between domains in purely Samba environment.
    19.3.1. Samba-3 as the Trusting Domain
    In order to set Samba PDC to be trusted party of the relationship first you need
+to create special account for the domain that will be the trusting party. To do that,
+you can use the 'smbpasswd' utility. Creating the trusted domain account is very
+similiar to creating a trusted machine account. Suppose, your domain is
+called SAMBA, and the remote domain is called RUMBA. The first step
+will be to issue this command from your favourite shell:
        deity# smbpasswd -a -i rumba
+    	New SMB password: XXXXXXXX
+    	Retype SMB password: XXXXXXXX
+    	Added user rumba$
    
+
+where -a means to add a new account into the
+passdb database and -i means: ''create this
+account with the InterDomain trust flag''
    The account name will be 'rumba$' (the name of the remote domain)
    After issuing this command you'll be asked to enter the password for
+the account. You can use any password you want, but be aware that Windows NT will
+not change this password until 7 days following account creation.
+After the command returns successfully, you can look at the entry for new account
+(in the way depending on your configuration) and see that account's name is
+really RUMBA$ and it has 'I' flag in the flags field. Now you're ready to confirm
+the trust by establishing it from Windows NT Server.
    Open 'User Manager for Domains' and from menu 'Policies' select 'Trust Relationships...'.
+Right beside 'Trusted domains' list box press 'Add...' button. You will be prompted for
+the trusted domain name and the relationship password. Type in SAMBA, as this is
+your domain name, and the password used at the time of account creation.
+Press OK and, if everything went without incident, you will see 'Trusted domain relationship
+successfully established' message.
    19.3.2. Samba-3 as the Trusted Domain
    This time activities are somewhat reversed. Again, we'll assume that your domain
+controlled by the Samba PDC is called SAMBA and NT-controlled domain is called RUMBA.
    The very first thing requirement is to add an account for the SAMBA domain on RUMBA's PDC.
    Launch the Domain User Manager, then from the menu select 'Policies', 'Trust Relationships'.
+Now, next to 'Trusted Domains' box press the 'Add' button, and type in the name of the trusted
+domain (SAMBA) and password securing the relationship.
    The password can be arbitrarily chosen. It is easy to change it the password
+from Samba server whenever you want. After confirming the password your account is
+ready for use. Now it's Samba's turn.
    Using your favourite shell while being logged in as root, issue this command:
    deity# net rpc trustdom establish rumba
    You will be prompted for the password you just typed on your Windows NT4 Server box.
+Don not worry if you see an error message that mentions a returned code of
+NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT. It means the
+password you gave is correct and the NT4 Server says the account is
+ready for interdomain connection and not for ordinary
+connection. After that, be patient it can take a while (especially
+in large networks), you should see the 'Success' message. Congratulations! Your trust
+relationship has just been established.
    Note that you have to run this command as root because you must have write access to
+the secrets.tdb file.
    PrevHomeNext
    Desktop Profile ManagementUpPAM Configuration for Centrally Managed Authentication
    
\ No newline at end of file
diff --git a/docs/htmldocs/introsmb.html b/docs/htmldocs/introsmb.html
new file mode 100644
index 0000000000..52db6a8a95
--- /dev/null
+++ b/docs/htmldocs/introsmb.html
@@ -0,0 +1,659 @@
+
+Introduction to Samba
    SAMBA Project Documentation
    PrevNext
    Chapter 1. Introduction to Samba
    "If you understand what you're doing, you're not learning anything." 
+-- Anonymous
    Samba is a file and print server for Windows-based clients using TCP/IP as the underlying
+transport protocol. In fact, it can support any SMB/CIFS-enabled client. One of Samba's big
+strengths is that you can use it to blend your mix of Windows and Linux machines together
+without requiring a separate Windows NT/2000/2003 Server.  Samba is actively being developed
+by a global team of about 30 active programmers and was originally developed by Andrew Tridgell.
    1.1. Background
    Once long ago, there was a buzzword referred to as DCE/RPC. This stood for Distributed
+Computing Environment/Remote Procedure Calls and conceptually was a good idea. It was
+originally developed by Apollo/HP as NCA 1.0 (Network Computing Architecture) and only
+ran over UDP. When there was a need to run it over TCP so that it would be compatible
+with DECnet 3.0, it was redesigned, submitted to The Open Group, and officially became
+known as DCE/RPC. Microsoft came along and decided, rather than pay $20 per seat to
+license this technology, to reimplement DCE/RPC themselves as MSRPC. From this, the
+concept continued in the form of SMB (Server Message Block, or the "what") using the
+NetBIOS (Network Basic Input/Output System, or the "how") compatibility layer. You can
+run SMB (i.e., transport) over several different protocols; many different implementations
+arose as a result, including NBIPX (NetBIOS over IPX, NwLnkNb, or NWNBLink) and NBT
+(NetBIOS over TCP/IP, or NetBT). As the years passed, NBT became the most common form
+of implementation until the advance of "Direct-Hosted TCP" -- the Microsoft marketing
+term for eliminating NetBIOS entirely and running SMB by itself across TCP port 445
+only. As of yet, direct-hosted TCP has yet to catch on.
    Perhaps the best summary of the origins of SMB are voiced in the 1997 article titled, CIFS:
+Common Insecurities Fail Scrutiny:
    Several megabytes of NT-security archives, random whitepapers, RFCs, the CIFS spec, the Samba
+stuff, a few MS knowledge-base articles, strings extracted from binaries, and packet dumps have
+been dutifully waded through during the information-gathering stages of this project, and there
+are *still* many missing pieces... While often tedious, at least the way has been generously
+littered with occurrences of clapping hand to forehead and muttering 'crikey, what are they
+thinking?
    1.2. Terminology
    • 	SMB: Acronym for "Server Message Block". This is Microsoft's file and printer sharing protocol.
+	
    • 	CIFS: Acronym for "Common Internet File System". Around 1996, Microsoft apparently
+	decided that SMB needed the word "Internet" in it, so they changed it to CIFS.  
+	
    • 	Direct-Hosted: A method of providing file/printer sharing services over port 445/tcp
+	only using DNS for name resolution instead of WINS.
+	
    • 	IPC: Acronym for "Inter-Process Communication". A method to communicate specific
+	information between programs.
+	
    • 	Marshalling: - A method of serializing (i.e., sequential ordering of) variable data
+	suitable for transmission via a network connection or storing in a file. The source
+	data can be re-created using a similar process called unmarshalling.
+	
    • 	NetBIOS: Acronym for "Network Basic Input/Output System". This is not a protocol;
+	it is a method of communication across an existing protocol. This is a standard which
+	was originally developed for IBM by Sytek in 1983. To exaggerate the analogy a bit,
+	it can help to think of this in comparison your computer's BIOS -- it controls the
+	essential functions of your input/output hardware -- whereas NetBIOS controls the
+	essential functions of your input/output traffic via the network. Again, this is a bit
+	of an exaggeration but it should help that paradigm shift. What is important to realize
+	is that NetBIOS is a transport standard, not a protocol. Unfortunately, even technically
+	brilliant people tend to interchange NetBIOS with terms like NetBEUI without a second
+	thought; this will cause no end (and no doubt) of confusion.
+	
    • 	NetBEUI: Acronym for the "NetBIOS Extended User Interface". Unlike NetBIOS, NetBEUI
+	is a protocol, not a standard. It is also not routable, so traffic on one side of a
+	router will be unable to communicate with the other side. Understanding NetBEUI is
+	not essential to deciphering SMB; however it helps to point out that it is not the
+	same as NetBIOS and to improve your score in trivia at parties. NetBEUI was originally
+	referred to by Microsoft as "NBF", or "The Windows NT NetBEUI Frame protocol driver".
+	It is not often heard from these days.
+	
    • 	NBT: Acronym for "NetBIOS over TCP"; also known as "NetBT". Allows the continued use
+	of NetBIOS traffic proxied over TCP/IP. As a result, NetBIOS names are made 
+	to IP addresses and NetBIOS name types are conceptually equivalent to TCP/IP ports.
+	This is how file and printer sharing are accomplished in Windows 95/98/ME. They 
+	traditionally rely on three ports: NetBIOS Name Service (nbname) via UDP port 137, 
+	NetBIOS Datagram Service (nbdatagram) via UDP port 138, and NetBIOS Session Service 
+	(nbsession) via TCP port 139. All name resolution is done via WINS, NetBIOS broadcasts, 
+	and DNS. NetBIOS over TCP is documented in RFC 1001 (Concepts and methods) and RFC 1002 
+	(Detailed specifications).
+	
    • 	W2K: Acronym for Windows 2000 Professional or Server
+	
    • 	W3K: Acronym for Windows 2003 Server
+	
    If you plan on getting help, make sure to subscribe to the Samba Mailing List (available at 
+http://www.samba.org).  Optionally, you could just search mailing.unix.samba at http://groups.google.com
    1.3. Related Projects
    Currently, there are two projects that are directly related to Samba: SMBFS and CIFS network
+client file systems for Linux, both available in the Linux kernel itself.
    • 	SMBFS (Server Message Block File System) allows you to mount SMB shares (the protocol
+	that Microsoft Windows and OS/2 Lan Manager use to share files and printers 
+	over local networks) and access them just like any other Unix directory. This is useful 
+	if you just want to mount such filesystems without being a SMBFS server.
+	
    • 	CIFS (Common Internet File System) is the successor to SMB, and is actively being worked
+	on in the upcoming version of the Linux kernel. The intent of this module is to 
+	provide advanced network file system functionality including support for dfs (heirarchical 
+	name space), secure per-user session establishment, safe distributed caching (oplock), 
+	optional packet signing, Unicode and other internationalization improvements, and optional 
+	Winbind (nsswitch) integration.
+	
    Again, it's important to note that these are implementations for client filesystems, and have
+nothing to do with acting as a file and print server for SMB/CIFS clients.
    1.4. SMB Methodology
    Traditionally, SMB uses UDP port 137 (NetBIOS name service, or netbios-ns),
+UDP port 138 (NetBIOS datagram service, or netbios-dgm), and TCP port 139 (NetBIOS
+session service, or netbios-ssn). Anyone looking at their network with a good
+packet sniffer will be amazed at the amount of traffic generated by just opening
+up a single file. In general, SMB sessions are established in the following order:
    • 	"TCP Connection" - establish 3-way handshake (connection) to port 139/tcp
+    or 445/tcp.
+	
    • 	"NetBIOS Session Request" - using the following "Calling Names": The local
+    machine's NetBIOS name plus the 16th character 0x00; The server's NetBIOS
+    name plus the 16th character 0x20
+	
    • 	"SMB Negotiate Protocol" - determine the protocol dialect to use, which will
+    be one of the following: PC Network Program 1.0 (Core) - share level security
+    mode only; Microsoft Networks 1.03 (Core Plus) - share level security
+    mode only; Lanman1.0 (LAN Manager 1.0) - uses Challenge/Response
+    Authentication; Lanman2.1 (LAN Manager 2.1) - uses Challenge/Response
+    Authentication; NT LM 0.12 (NT LM 0.12) - uses Challenge/Response
+    Authentication
+	
    • 	SMB Session Startup. Passwords are encrypted (or not) according to one of
+    the following methods: Null (no encryption); Cleartext (no encryption); LM
+    and NTLM; NTLM; NTLMv2
+	
    • 	SMB Tree Connect: Connect to a share name (e.g., \\servername\share); Connect
+    to a service type (e.g., IPC$ named pipe)
+	
    A good way to examine this process in depth is to try out SecurityFriday's SWB program
+at http://www.securityfriday.com/ToolDownload/SWB/swb_doc.html.  It allows you to
+walk through the establishment of a SMB/CIFS session step by step.
    1.5. Additional Resources
    • 	CIFS: Common Insecurities Fail Scrutiny by "Hobbit", 
+	http://hr.uoregon.edu/davidrl/cifs.txt
+	
    • 	Doing the Samba on Windows by Financial Review,
+	http://afr.com/it/2002/10/01/FFXDF43AP6D.html
+	
    • 	Implementing CIFS by Christopher R. Hertel,
+	http://ubiqx.org/cifs/
+	
    • 	Just What Is SMB? by Richard Sharpe,
+	http://samba.anu.edu.au/cifs/docs/what-is-smb.html
+	
    • 	Opening Windows Everywhere by Mike Warfield,
+	http://www.linux-mag.com/1999-05/samba_01.html
+	
    • 	SMB HOWTO by David Wood,
+	http://www.tldp.org/HOWTO/SMB-HOWTO.html
+	
    • 	SMB/CIFS by The Root by "ledin",
+	http://www.phrack.org/phrack/60/p60-0x0b.txt
+	
    • 	The Story of Samba by Christopher R. Hertel,
+	http://www.linux-mag.com/1999-09/samba_01.html
+	
    • 	The Unofficial Samba HOWTO by David Lechnyr,
+	http://hr.uoregon.edu/davidrl/samba/
+	
    • 	Understanding the Network Neighborhood by Christopher R. Hertel,
+	http://www.linux-mag.com/2001-05/smb_01.html
+	
    • 	Using Samba as a PDC by Andrew Bartlett,
+	http://www.linux-mag.com/2002-02/samba_01.html
+	
    1.6. Epilogue
    "What's fundamentally wrong is that nobody ever had any taste when they
+did it. Microsoft has been very much into making the user interface look good,
+but internally it's just a complete mess. And even people who program for Microsoft
+and who have had years of experience, just don't know how it works internally.
+Worse, nobody dares change it. Nobody dares to fix bugs because it's such a
+mess that fixing one bug might just break a hundred programs that depend on
+that bug. And Microsoft isn't interested in anyone fixing bugs -- they're interested
+in making money. They don't have anybody who takes pride in Windows 95 as an
+operating system.
    People inside Microsoft know it's a bad operating system and they still
+continue obviously working on it because they want to get the next version out
+because they want to have all these new features to sell more copies of the
+system.
    The problem with that is that over time, when you have this kind of approach,
+and because nobody understands it, because nobody REALLY fixes bugs (other than
+when they're really obvious), the end result is really messy. You can't trust
+it because under certain circumstances it just spontaneously reboots or just
+halts in the middle of something that shouldn't be strange. Normally it works
+fine and then once in a blue moon for some completely unknown reason, it's dead,
+and nobody knows why. Not Microsoft, not the experienced user and certainly
+not the completely clueless user who probably sits there shivering thinking
+"What did I do wrong?" when they didn't do anything wrong at all.
    That's what's really irritating to me."
    -- Linus Torvalds, from an interview with BOOT Magazine, Sept 1998
+(http://hr.uoregon.edu/davidrl/boot.txt)
    1.7. Miscellaneous
    This chapter was lovingly handcrafted on a Dell Latitude C400 laptop running Slackware Linux 9.0,
+in case anyone asks.
    This chapter is Copyright  2003 David Lechnyr (david at lechnyr dot com).
+Permission is granted to copy, distribute and/or modify this document under the terms
+of the GNU Free Documentation License, Version 1.2 or any later version published by the Free
+Software Foundation. A copy of the license is available at http://www.gnu.org/licenses/fdl.txt.
    PrevHomeNext
    General installationUpHow to Install and Test SAMBA
    
\ No newline at end of file
diff --git a/docs/htmldocs/nt4migration.html b/docs/htmldocs/nt4migration.html
new file mode 100644
index 0000000000..6278a64371
--- /dev/null
+++ b/docs/htmldocs/nt4migration.html
@@ -0,0 +1,356 @@
+
+Migration from NT4 PDC to Samba-3 PDC
    SAMBA Project Documentation
    PrevNext
    Chapter 28. Migration from NT4 PDC to Samba-3 PDC
    This is a rough guide to assist those wishing to migrate from NT4 domain control to
+Samba-3 based domain control.
    28.1. Planning and Getting Started
    In the IT world there is often a saying that all problems are encountered because of
+poor planning. The corrollary to this saying is that not all problems can be anticpated
+and planned for. Then again, good planning will anticpate most show stopper type situations.
    Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control
+environment would do well to develop a detailed migration plan. So here are a few pointers to
+help migration get under way.
    28.1.1. Objectives
    The key objective for most organisations will be to make the migration from MS Windows NT4 
+to Samba-3 domain control as painless as possible. One of the challenges you may experience
+in your migration process may well be one of convincing management that the new environment
+should remain in place. Many who have introduced open source technologies have experienced
+pressure to return to a Microsoft based platform solution at the first sign of trouble. 
    It is strongly advised that before attempting a migration to a Samba-3 controlled network
+that every possible effort be made to gain all-round commitment to the change. Firstly, you
+should know precisely why the change is important for the organisation.
+Possible motivations to make a change include:
    • Improve network manageability
    • Obtain better user level functionality
    • Reduce network operating costs
    • Reduce exposure caused by Microsoft withdrawal of NT4 support
    • Avoid MS License 6 implications
    • Reduce organisation's dependency on Microsoft
    It is vital that oit be well recognised that Samba-3 is NOT MS Windows NT4. Samba-3 offers
+an alternative solution that is both different from MS Windows NT4 and that offers some
+advantages compared with it. It should also be recognised that Samba-3 lacks many of the
+features that Microsoft has promoted as core values in migration from MS Windows NT4 to 
+MS Windows 2000 and beyond (with or without Active Directory services).
    What are the features the Samba-3 can NOT provide?
    Active Directory Server
    Group Policy Objects (in Active Direcrtory)
    Machine Policy objects
    Logon Scripts in Active Directorty
    Software Application and Access Controls in Active Directory
    28.1.2. Steps In Migration Process
    This is not a definitive ste-by-step process yet - just a place holder so the info 
+is not lost.
+
+1. You will have an NT4 PDC that has the users, groups, policies and profiles to be migrated
+
+2. Samba-3 set up as a DC with netlogon share, profile share, etc.
+
+3. Process:
+	a. Create a BDC account for the samba server using NT Server Manager
+		- Samba must NOT be running
+
+	b. rpcclient NT4PDC -U Administrator%passwd
+		lsaquery
+
+		Note the SID returned by step b.
+
+	c. net getsid -S NT4PDC -w DOMNAME -U Administrator%passwd
+
+		Note the SID in step c.
+
+	d. net getlocalsid
+
+		Note the SID, now check that all three SIDS reported are the same!
+
+	e. net rpc join -S NT4PDC -w DOMNAME -U Administrator%passwd
+
+	f. net rpc vampire -S NT4PDC -U administrator%passwd
+
+	g. pdbedit -l
+
+		Note - did the users migrate?
+
+	h. initGrps.sh DOMNAME
+
+	i. smbgroupedit -v
+
+		Now check that all groups are recognised
+
+	j. net rpc campire -S NT4PDC -U administrator%passwd
+
+	k. pdbedit -lv
+
+		Note - check that all group membership has been migrated.
+
+
+Now it is time to migrate all the profiles, then migrate all policy files.
+
+Moe later.
    PrevHomeNext
    How to compile SAMBAUpPortability
    
\ No newline at end of file
diff --git a/docs/htmldocs/ntlm_auth.1.html b/docs/htmldocs/ntlm_auth.1.html
new file mode 100644
index 0000000000..95558aae38
--- /dev/null
+++ b/docs/htmldocs/ntlm_auth.1.html
@@ -0,0 +1,261 @@
+
+ntlm_auth
    ntlm_auth
    Name
    ntlm_auth -- tool to allow external access to Winbind's NTLM authentication function
    Synopsis
    ntlm_auth  [-d debuglevel] [-l logfile] [-s <smb config file>]
    DESCRIPTION
    This tool is part of the Samba(7) suite.
    ntlm_auth is a helper utility that authenticates 
+	users using NT/LM authentication. It returns 0 if the users is authenticated
+	successfully and 1 if access was denied. ntlm_auth uses winbind to access 
+	the user and authentication data for a domain. This utility 
+	is only to be used by other programs (currently squid).
+	
    OPTIONS
    --helper-protocol=PROTO
    	Operate as a stdio-based helper
+	
    --username=USERNAME
    	Specify username of user to authenticate
+	
    --domain=DOMAIN
    	Specify domain of user to authenticate
+	
    --workstation=WORKSTATION
    	Specify the workstation the user authenticated from
+	
    --challenge=STRING
    challenge (HEX encoded)
    --lm-response=RESPONSE
    LM Response to the challenge (HEX encoded)
    --nt-response=RESPONSE
    NT or NTLMv2 Response to the challenge (HEX encoded)
    --password=PASSWORD
    User's plaintext password
    --request-lm-key
    Retreive LM session key
    --request-nt-key
    Request NT key
    -V
    Prints the version number for 
+smbd.
    -s <configuration file>
    The file specified contains the 
+configuration details required by the server.  The 
+information in this file includes server-specific
+information such as what printcap file to use, as well 
+as descriptions of all the services that the server is 
+to provide. See smb.conf(5) for more information.
+The default configuration file name is determined at 
+compile time.
    -d|--debug=debuglevel
    debuglevel is an integer 
+from 0 to 10.  The default value if this parameter is 
+not specified is zero.
    The higher this value, the more detail will be 
+logged to the log files about the activities of the 
+server. At level 0, only critical errors and serious 
+warnings will be logged. Level 1 is a reasonable level for
+day to day running - it generates a small amount of 
+information about operations carried out.
    Levels above 1 will generate considerable 
+amounts of log data, and should only be used when 
+investigating a problem. Levels above 3 are designed for 
+use only by developers and generate HUGE amounts of log
+data, most of which is extremely cryptic.
    Note that specifying this parameter here will 
+override the log
+level parameter in the smb.conf(5) file.
    -l|--logfile=logbasename
    File name for log/debug files. The extension
+".client" will be appended. The log file is
+never removed by the client.
    -h|--help
    Print a summary of command line options.
    VERSION
    This man page is correct for version 3.0 of the Samba 
+	suite.
    AUTHOR
    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.
    The ntlm_auth manpage was written by Jelmer Vernooij.
    
\ No newline at end of file
diff --git a/docs/htmldocs/policymgmt.html b/docs/htmldocs/policymgmt.html
new file mode 100644
index 0000000000..65f50dc0fb
--- /dev/null
+++ b/docs/htmldocs/policymgmt.html
@@ -0,0 +1,758 @@
+
+System and Account Policies
    SAMBA Project Documentation
    PrevNext
    Chapter 17. System and Account Policies
    17.1. Creating and Managing System Policies
    Under MS Windows platforms, particularly those following the release of MS Windows
+NT4 and MS Windows 95) it is possible to create a type of file that would be placed
+in the NETLOGON share of a domain controller. As the client logs onto the network
+this file is read and the contents initiate changes to the registry of the client
+machine. This file allows changes to be made to those parts of the registry that
+affect users, groups of users, or machines.
    For MS Windows 9x/Me this file must be called Config.POL and may
+be generated using a tool called poledit.exe, better known as the
+Policy Editor. The policy editor was provided on the Windows 98 installation CD, but
+dissappeared again with the introduction of MS Windows Me (Millenium Edition). From
+comments from MS Windows network administrators it would appear that this tool became
+a part of the MS Windows Me Resource Kit.
    MS Windows NT4 Server products include the System Policy Editor
+under the Start -> Programs -> Administrative Tools menu item.
+For MS Windows NT4 and later clients this file must be called NTConfig.POL.
    New with the introduction of MS Windows 2000 was the Microsoft Management Console
+or MMC.  This tool is the new wave in the ever changing landscape of Microsoft
+methods for management of network access and security. Every new Microsoft product
+or technology seems to obsolete the old rules and to introduce newer and more
+complex tools and methods. To Microsoft's credit though, the MMC does appear to
+be a step forward, but improved functionality comes at a great price.
    Before embarking on the configuration of network and system policies it is highly
+advisable to read the documentation available from Microsoft's web site regarding
+Implementing Profiles and Policies in Windows NT 4.0 from http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp available from Microsoft.
+There are a large number of documents in addition to this old one that should also
+be read and understood. Try searching on the Microsoft web site for "Group Policies".
    What follows is a very brief discussion with some helpful notes. The information provided
+here is incomplete - you are warned.
    17.1.1. Windows 9x/Me Policies
    You need the Win98 Group Policy Editor to set Group Profiles up under Windows 9x/Me.
+It can be found on the Original full product Win98 installation CD under
+tools/reskit/netadmin/poledit.  Install this using the
+Add/Remove Programs facility and then click on the 'Have Disk' tab.
    Use the Group Policy Editor to create a policy file that specifies the location of
+user profiles and/or the My Documents etc.  stuff. Then
+save these settings in a file called Config.POL that needs to
+be placed in the root of the [NETLOGON] share. If Win98 is configured to log onto
+the Samba Domain, it will automatically read this file and update the Win9x/Me registry
+of the machine as it logs on.
    Further details are covered in the Win98 Resource Kit documentation.
    If you do not take the right steps, then every so often Win9x/Me will check the
+integrity of the registry and will restore it's settings from the back-up
+copy of the registry it stores on each Win9x/Me machine. Hence, you will
+occasionally notice things changing back to the original settings.
    Install the group policy handler for Win9x to pick up group policies. Look on the
+Win98 CD in \tools\reskit\netadmin\poledit.
+Install group policies on a Win9x client by double-clicking
+grouppol.inf. 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/Me machine that uses group policies.
    17.1.2. Windows NT4 Style Policy Files
    To create or edit ntconfig.pol you must use the NT Server
+Policy Editor, poledit.exe which is included with NT4 Server
+but not NT Workstation. There is a Policy Editor on a NT4
+Workstation but it is not suitable for creating Domain Policies.
+Further, although the Windows 95 Policy Editor can be installed on an NT4
+Workstation/Server, it will not work with NT clients. However, the files from
+the NT Server will run happily enough on an NT4 Workstation.
    You need poledit.exe, common.adm and winnt.adm.
+It is convenient to put the two *.adm files in  the c:\winnt\inf 
+directory which is where the binary will look for them unless told otherwise. Note also that that
+directory is normally 'hidden'.
    The Windows NT policy editor is also included with the Service Pack 3 (and
+later) for Windows NT 4.0. Extract the files using servicepackname /x,
+i.e. that's Nt4sp6ai.exe /x for service pack 6a.  The policy editor,
+poledit.exe 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.
    17.1.2.1. Registry Tattoos
    	With NT4 style registry based policy changes, a large number of settings are not
+	automatically reversed as the user logs off. Since the settings that were in the
+	NTConfig.POL file were applied to the client machine registry and that apply to the
+	hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known
+	as tattooing. It can have serious consequences down-stream and the administrator must
+	be extremely careful not to lock out the ability to manage the machine at a later date.
+	
    17.1.3. MS Windows 200x / XP Professional Policies
    Windows NT4 System policies allows setting of registry parameters specific to
+users, groups and computers (client workstations) that are members of the NT4
+style domain. Such policy file will work with MS Windows 2000 / XP clients also.
    New to MS Windows 2000 Microsoft introduced a new style of group policy that confers
+a superset of capabilities compared with NT4 style policies. Obviously, the tool used
+to create them is different, and the mechanism for implementing them is much changed.
    The older NT4 style registry based policies are known as Administrative Templates
+in MS Windows 2000/XP Group Policy Objects (GPOs). The later includes ability to set various security
+configurations, enforce Internet Explorer browser settings, change and redirect aspects of the
+users' desktop (including: the location of My Documents files (directory), as
+well as intrinsics of where menu items will appear in the Start menu). An additional new
+feature is the ability to make available particular software Windows applications to particular
+users and/or groups.
    Remember: NT4 policy files are named NTConfig.POL and are stored in the root
+of the NETLOGON share on the domain controllers. A Windows NT4 user enters a username, a password
+and selects the domain name to which the logon will attempt to take place. During the logon
+process the client machine reads the NTConfig.POL file from the NETLOGON share on the authenticating
+server, modifies the local registry values according to the settings in this file.
    Windows 2K GPOs are very feature rich. They are NOT stored in the NETLOGON share, rather part of
+a Windows 200x policy file is stored in the Active Directory itself and the other part is stored
+in a shared (and replicated) volume called the SYSVOL folder. This folder is present on all Active
+Directory domain controllers. The part that is stored in the Active Directory itself is called the
+group policy container (GPC), and the part that is stored in the replicated share called SYSVOL is
+known as the group policy template (GPT).
    With NT4 clients the policy file is read and executed upon only aas each user log onto the network.
+MS Windows 200x policies are much more complex - GPOs are processed and applied at client machine
+startup (machine specific part) and when the user logs onto the network the user specific part
+is applied. In MS Windows 200x style policy management each machine and/or user may be subject
+to any number of concurently applicable (and applied) policy sets (GPOs). Active Directory allows
+the administrator to also set filters over the policy settings. No such equivalent capability
+exists with NT4 style policy files.
    17.1.3.1. Administration of Win2K / XP Policies
    Instructions
    Instead of using the tool called "The System Policy Editor", commonly called Poledit (from the
+executable name poledit.exe), GPOs are created and managed using a Microsoft Management Console
+(MMC) snap-in as follows:
    1. Go to the Windows 200x / XP menu Start->Programs->Administrative Tools
+	and select the MMC snap-in called "Active Directory Users and Computers"
    2. Select the domain or organizational unit (OU) that you wish to manage, then right click
+to open the context menu for that object, select the properties item.
    3. Now left click on the Group Policy tab, then left click on the New tab. Type a name
+for the new policy you will create.
    4. Now left click on the Edit tab to commence the steps needed to create the GPO.
    All policy configuration options are controlled through the use of policy administrative
+templates. These files have a .adm extension, both in NT4 as well as in Windows 200x / XP.
+Beware however, since the .adm files are NOT interchangible across NT4 and Windows 200x.
+The later introduces many new features as well as extended definition capabilities. It is
+well beyond the scope of this documentation to explain how to program .adm files, for that
+the adminsitrator is referred to the Microsoft Windows Resource Kit for your particular
+version of MS Windows.
    The MS Windows 2000 Resource Kit contains a tool called gpolmig.exe. This tool can be used
+to migrate an NT4 NTConfig.POL file into a Windows 200x style GPO. Be VERY careful how you
+use this powerful tool. Please refer to the resource kit manuals for specific usage information.
    17.2. Managing Account/User Policies
    Policies can define a specific user's settings or the settings for a group of users. The resulting
+policy file contains the registry settings for all users, groups, and computers that will be using
+the policy file. Separate policy files for each user, group, or computer are not not necessary.
    If you create a policy that will be automatically downloaded from validating domain controllers,
+you should name the file NTconfig.POL. As system administrator, you have the option of renaming the
+policy file and, by modifying the Windows NT-based workstation, directing the computer to update
+the policy from a manual path. You can do this by either manually changing the registry or by using
+the System Policy Editor. This path can even be a local path such that each machine has its own policy file,
+but if a change is necessary to all machines, this change must be made individually to each workstation.
    When a Windows NT4/200x/XP machine logs onto the network the NETLOGON share on the authenticating domain 
+controller for the presence of the NTConfig.POL file. If one exists it is downloaded, parsed and then
+applied to the user's part of the registry.
    MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally,
+acquire policy settings through Group Policy Objects (GPOs) that are defined and stored in Active Directory
+itself. The key benefit of using AS GPOs is that they impose no registry tatooing effect.
+This has considerable advanage compared with the use of NTConfig.POL (NT4) style policy updates.
    Inaddition to user access controls that may be imposed or applied via system and/or group policies
+in a manner that works in conjunction with user profiles, the user management environment under
+MS Windows NT4/200x/XP allows per domain as well as per user account restrictions to be applied.
+Common restrictions that are frequently used includes:
    Logon Hours
    Password Aging
    Permitted Logon from certain machines only
    Account type (Local or Global)
    User Rights
    17.2.1. With Windows NT4/200x
    The tools that may be used to configure these types of controls from the MS Windows environment are:
+The NT4 User Manager for domains, the NT4 System and Group Policy Editor, the registry editor (regedt32.exe).
+Under MS Windows 200x/XP this is done using the Microsoft Managment Console (MMC) with approapriate
+"snap-ins", the registry editor, and potentially also the NT4 System and Group Policy Editor.
    17.2.2. With a Samba PDC
    With a Samba Domain Controller, the new tools for managing of user account and policy information includes:
+smbpasswd, pdbedit, smbgroupedit, net, rpcclient.. The administrator should read the
+man pages for these tools and become familiar with their use.
    17.3. System Startup and Logon Processing Overview
    The following attempts to document the order of processing of system and user policies following a system
+reboot and as part of the user logon:
    1. 	Network starts, then Remote Procedure Call System Service (RPCSS) and Multiple Universal Naming
+	Convention Provider (MUP) start
+	
    2. 	Where Active Directory is involved, an ordered list of Group Policy Objects (GPOs) is downloaded
+	and applied. The list may include GPOs that:
+
      Apply to the location of machines in a Directory
      Apply only when settings have changed
      Depend on configuration of scope of applicability: local, site, domain, organizational unit, etc.
      
+	No desktop user interface is presented until the above have been processed.
+	
    3. 	Execution of start-up scripts (hidden and synchronous by defaut).
+	
    4. 	A keyboard action to affect start of logon (Ctrl-Alt-Del).
+	
    5. 	User credentials are validated, User profile is loaded (depends on policy settings).
+	
    6. 	An ordered list of User GPOs is obtained. The list contents depends on what is configured in respsect of:
+
+
      Is user a domain member, thus subject to particular policies
      Loopback enablement, and the state of the loopback policy (Merge or Replace)
      Location of the Active Directory itself
      Has the list of GPOs changed. No processing is needed if not changed.
      
+	
    7. 	User Policies are applied from Active Directory. Note: There are several types.
+	
    8. 	Logon scripts are run. New to Win2K and Active Directory, logon scripts may be obtained based on Group
+	Policy objects (hidden and executed synchronously). NT4 style logon scripts are then run in a normal
+	window.
+	
    9. 	The User Interface as determined from the GPOs is presented. Note: In a Samba domain (like and NT4
+	Domain) machine (system) policies are applied at start-up, User policies are applied at logon.
+	
    PrevHomeNext
    Advanced Network ManangementUpDesktop Profile Management
    
\ No newline at end of file
diff --git a/docs/htmldocs/problems.html b/docs/htmldocs/problems.html
new file mode 100644
index 0000000000..7c0e1acab5
--- /dev/null
+++ b/docs/htmldocs/problems.html
@@ -0,0 +1,560 @@
+
+Analysing and solving samba problems
    SAMBA Project Documentation
    PrevNext
    Chapter 34. Analysing and solving samba problems
    There are many sources of information available in the form 
+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.
    34.1. Diagnostics tools
    One of the best diagnostic tools for debugging problems is Samba itself.  
+You can use the -d option for both smbd and nmbd to specify what 
+'debug level' at which to run.  See the man pages on smbd, nmbd  and 
+smb.conf for more information on debugging options.  The debug 
+level can range from 1 (the default) to 10 (100 for debugging passwords).
    Another helpful method of debugging is to compile samba using the 
+gcc -g  flag.   This will include debug 
+information in the binaries and allow you to attach gdb to the 
+running smbd / nmbd process.  In order to attach gdb to an smbd 
+process for an NT workstation, first get the workstation to make the 
+connection. Pressing ctrl-alt-delete and going down to the domain box 
+is sufficient (at least, on the first time you join the domain) to 
+generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation 
+maintains an open connection, and therefore there will be an smbd 
+process running (assuming that you haven't set a really short smbd 
+idle timeout)  So, in between pressing ctrl alt delete, and actually 
+typing in your password, you can gdb attach and continue.
    Some useful samba commands worth investigating:
    • testparam | more
    • smbclient -L //{netbios name of server}
    An SMB enabled version of tcpdump is available from 
+http://www.tcpdup.org/.
+Ethereal, another good packet sniffer for Unix and Win32
+hosts, can be downloaded from http://www.ethereal.com.
    For tracing things on the Microsoft Windows NT, Network Monitor 
+(aka. netmon) is available on the Microsoft Developer Network CD's, 
+the Windows NT Server install CD and the SMS CD's.  The version of 
+netmon that ships with SMS allows for dumping packets between any two 
+computers (i.e. placing the network interface in promiscuous mode).  
+The version on the NT Server install CD will only allow monitoring 
+of network traffic directed to the local NT box and broadcasts on the 
+local subnet.  Be aware that Ethereal can read and write netmon 
+formatted files.
    34.2. Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
    Installing netmon on an NT workstation requires a couple 
+of steps.  The following are for installing Netmon V4.00.349, which comes 
+with Microsoft Windows NT Server 4.0, on Microsoft Windows NT 
+Workstation 4.0.  The process should be similar for other version of 
+Windows NT / Netmon.  You will need both the Microsoft Windows 
+NT Server 4.0 Install CD and the Workstation 4.0 Install CD.
    Initially you will need to install 'Network Monitor Tools and Agent' 
+on the NT Server.  To do this 
    • Goto Start - Settings - Control Panel - 
+	Network - Services - Add 
    • Select the 'Network Monitor Tools and Agent' and 
+	click on 'OK'.
    • Click 'OK' on the Network Control Panel.
+	
    • Insert the Windows NT Server 4.0 install CD 
+	when prompted.
    At this point the Netmon files should exist in 
+%SYSTEMROOT%\System32\netmon\*.*.    
+Two subdirectories exist as well, parsers\ 
+which contains the necessary DLL's for parsing the netmon packet 
+dump, and captures\.
    In order to install the Netmon tools on an NT Workstation, you will 
+first need to install the 'Network  Monitor Agent' from the Workstation 
+install CD.
    • Goto Start - Settings - Control Panel - 
+	Network - Services - Add
    • Select the 'Network Monitor Agent' and click 
+	on 'OK'.
    • Click 'OK' on the Network Control Panel.
+	
    • Insert the Windows NT Workstation 4.0 install 
+	CD when prompted.
    Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* 
+to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set 
+permissions as  you deem appropriate for your site. You will need 
+administrative rights on the NT box to run netmon.
    To install Netmon on a Windows 9x box install the network monitor agent 
+from the Windows 9x CD (\admin\nettools\netmon).  There is a readme 
+file located with the netmon driver files on the CD if you need 
+information on how to do this.  Copy the files from a working 
+Netmon installation.
    34.3. Useful URL's
    34.4. Getting help from the mailing lists
    There are a number of Samba related mailing lists. Go to http://samba.org, click on your nearest mirror
+and then click on Support and then click on Samba related mailing lists.
    For questions relating to Samba TNG go to
+http://www.samba-tng.org/ 
+It has been requested that you don't post questions about Samba-TNG to the
+main stream Samba lists.
    If you post a message to one of the lists please observe the following guide lines :
    •  Always remember that the developers are volunteers, they are 
+not paid and they never guarantee to produce a particular feature at 
+a particular time. Any time lines are 'best guess' and nothing more.
    •  Always mention what version of samba you are using and what 
+operating system its running under. You should probably list the
+relevant sections of your smb.conf file, at least the options 
+in [global] that affect PDC support.
    • In addition to the version, if you obtained Samba via
+CVS mention the date when you last checked it out.
    •  Try and make your question clear and brief, lots of long, 
+convoluted questions get deleted before	they are completely read ! 
+Don't post html encoded messages (if you can select colour or font 
+size its html).
    •  If you run one of those nifty 'I'm on holidays' things when 
+you are away, make sure its configured	to not answer mailing lists.
    •  Don't cross post. Work out which is the best list to post to 
+and see what happens, i.e. don't post to both samba-ntdom and samba-technical.
+Many people active on the lists subscribe to more 
+than one list and get annoyed to see the same message two or more times. 
+Often someone will see a message and thinking it would be better dealt 
+with on another, will forward it on for you.
    • You might include partial
+log files written at a debug level set to as much as 20.  
+Please don't send the entire log but enough to give the context of the 
+error messages.
    • (Possibly) If you have a complete netmon trace ( from the opening of 
+the pipe to the error ) you can send the *.CAP file as well.
    • Please think carefully before attaching a document to an email.
+Consider pasting the relevant parts into the body of the message. The samba
+mailing lists go to a huge number of people, do they all need a copy of your 
+smb.conf in their attach directory?
    34.5. How to get off the mailinglists
    To have your name removed from a samba mailing list, go to the
+same place you went to to get on it. Go to http://lists.samba.org, 
+click on your nearest mirror and then click on Support and 
+then click on  Samba related mailing lists. Or perhaps see 
+here
    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...)
    PrevHomeNext
    The samba checklistUpReporting Bugs
    
\ No newline at end of file
diff --git a/docs/htmldocs/profilemgmt.html b/docs/htmldocs/profilemgmt.html
new file mode 100644
index 0000000000..8a101049e0
--- /dev/null
+++ b/docs/htmldocs/profilemgmt.html
@@ -0,0 +1,1753 @@
+
+Desktop Profile Management
    SAMBA Project Documentation
    PrevNext
    Chapter 18. Desktop Profile Management
    Table of Contents
    18.1. Roaming Profiles
    18.1.1. Samba Configuration for Profile Handling
    18.1.1.1. NT4/200x User Profiles
    18.1.1.2. Windows 9x / Me User Profiles
    18.1.1.3. Mixed Windows 9x / Me and Windows NT4/200x User Profiles
    18.1.2. Windows Client Profile Configuration Information
    18.1.2.1. Windows 9x / Me Profile Setup
    18.1.2.2. Windows NT4 Workstation
    18.1.2.3. Windows 2000/XP Professional
    18.1.3. Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    18.1.4. Profile Migration from Windows NT4/200x Server to Samba
    18.1.4.1. Windows NT4 Profile Management Tools
    18.1.4.2. Side bar Notes
    18.1.4.3. moveuser.exe
    18.1.4.4. Get SID
    18.2. Mandatory profiles
    18.3. Creating/Managing Group Profiles
    18.4. Default Profile for Windows Users
    18.4.1. MS Windows 9x/Me
    18.4.2. MS Windows NT4 Workstation
    18.4.3. MS Windows 200x/XP
    18.1. Roaming Profiles
    Roaming profiles support is different for Win9x / Me and Windows NT4/200x.
    Before discussing how to configure roaming profiles, it is useful to see how
+Windows 9x / Me and Windows NT4/200x clients implement these features.
    Windows 9x / Me 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 user's home share. This means that Win9X/Me
+profiles are restricted to being stored in the user's home directory.
    Windows NT4/200x  clients send a NetSAMLogon RPC request, which contains many fields,
+including a separate field for the location of the user's profiles.
    18.1.1. Samba Configuration for Profile Handling
    This section documents how to configure Samba for MS Windows client profile support.
    18.1.1.1. NT4/200x User Profiles
    To support Windowns NT4/200x clients, in the [global] section of smb.conf set the
+following (for example):
    	logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath
    
+
+	This is typically implemented like:
+
+
    		logon path = \\%L\Profiles\%u
    
+where %L translates to the name of the Samba server and %u translates to the user name
    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. Please refer to the man page for smb.conf in respect of the different
+symantics of %L and %N, as well as %U and %u.
    MS Windows NT/2K clients at times do not disconnect a connection to a server
+between logons. It is recommended to NOT use the homes
+meta-service name as part of the profile share path.
    18.1.1.2. Windows 9x / Me User Profiles
    To support Windows 9x / Me 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.
    By using the logon home parameter, you are restricted to putting Win9x / Me
+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:
    	logon home = \\%L\%U\.profiles
    then your Windows 9x / Me clients will dutifully put their clients in a subdirectory
+of your home directory called .profiles (thus making them hidden).
    Not only that, but net use/home will also work, because of a feature in
+Windows 9x / Me. 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.
    18.1.1.3. Mixed Windows 9x / Me and Windows NT4/200x User Profiles
    You can support profiles for both Win9X and WinNT clients by setting both the
+logon home and logon path parameters. For example:
    	logon home = \\%L\%u\.profiles
+	logon path = \\%L\profiles\%u
    18.1.2. Windows Client Profile Configuration Information
    18.1.2.1. Windows 9x / Me Profile Setup
    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 preserve case = 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.
    1.         On the Windows 9x / Me 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.
+        
    2.         On the Windows 9x / Me 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 9x / Me 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, it would seem!
    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 9x / Me 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 9x / Me 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 Windows 9x / Me 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 Windows 9x / Me 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-caching file in the c:\windows
+        directory, and delete it.
+        
    5.         log off the windows 9x / Me 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 ethereal or netmon.exe, and
+look for error messages.
    If you have access to an Windows NT4/200x server, then first set up roaming profiles
+and / or netlogons on the Windows NT4/200x server.  Make a packet trace, or examine
+the example packet traces provided with Windows NT4/200x server, and see what the
+differences are with the equivalent samba trace.
    18.1.2.2. Windows NT4 Workstation
    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.
    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 NT4 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
+for those situations where it might be created.)
    In the profile directory, Windows NT4 creates more folders than Windows 9x / Me. 
+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.
    The case of the profile is significant.  The file must be called
+NTuser.DAT or, for a mandatory profile, NTuser.MAN.
    18.1.2.3. Windows 2000/XP Professional
    You must first convert the profile from a local profile to a domain
+profile on the MS Windows workstation as follows:
    • 	Log on as the LOCAL workstation administrator.
+	
    • 	Right click on the 'My Computer' Icon, select 'Properties'
+	
    • 	Click on the 'User Profiles' tab
+	
    • 	Select the profile you wish to convert (click on it once)
+	
    • 	Click on the button 'Copy To'
+	
    • 	In the "Permitted to use" box, click on the 'Change' button.
+	
    • 	Click on the 'Look in" area that lists the machine name, when you click
+	here it will open up a selection box. Click on the domain to which the
+	profile must be accessible.
+	
      You will need to log on if a logon box opens up. Eg: In the connect
+	as: MIDEARTH\root, password: mypassword.
    • 	To make the profile capable of being used by anyone select 'Everyone'
+	
    • 	Click OK. The Selection box will close.
+	
    • 	Now click on the 'Ok' button to create the profile in the path you
+	nominated.
+	
    Done. You now have a profile that can be editted using the samba-3.0.0
+profiles tool.
    Under NT/2K the use of mandotory profiles forces the use of MS Exchange
+storage of mail data. That keeps desktop profiles usable.
    • This is a security check new to Windows XP (or maybe only
+Windows XP service pack 1).  It can be disabled via a group policy in
+Active Directory.  The policy is:
      "Computer Configuration\Administrative Templates\System\User
+Profiles\Do not check for user ownership of Roaming Profile Folders"
      ...and it should be set to "Enabled".
+Does the new version of samba have an Active Directory analogue?  If so,
+then you may be able to set the policy through this.
      If you cannot set group policies in samba, then you may be able to set
+the policy locally on each machine.  If you want to try this, then do
+the following (N.B. I don't know for sure that this will work in the
+same way as a domain group policy):
    • On the XP workstation log in with an Administrator account.
    • Click: "Start", "Run"
    • Type: "mmc"
    • Click: "OK"
    • A Microsoft Management Console should appear.
    • Click: File, "Add/Remove Snap-in...", "Add"
    • Double-Click: "Group Policy"
    • Click: "Finish", "Close"
    • Click: "OK"
    • In the "Console Root" window:
    • Expand: "Local Computer Policy", "Computer Configuration",
    • "Administrative Templates", "System", "User Profiles"
    • Double-Click: "Do not check for user ownership of Roaming Profile
    • Folders"
    • Select: "Enabled"
    • Click: OK"
    • Close the whole console.  You do not need to save the settings (this
+	refers to the console settings rather than the policies you have
+	changed).
    • Reboot
    18.1.3. Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Sharing of desktop profiles between Windows versions is NOT recommended.
+Desktop profiles are an evolving phenomenon and profiles for later versions
+of MS Windows clients add features that may interfere with earlier versions
+of MS Windows clients. Probably the more salient reason to NOT mix profiles
+is that when logging off an earlier version of MS Windows the older format
+of profile contents may overwrite information that belongs to the newer
+version resulting in loss of profile information content when that user logs
+on again with the newer version of MS Windows.
    If you then want to share the same Start Menu / Desktop with W9x/Me, you will
+need to specify a common location for the profiles. The smb.conf parameters
+that need to be common are logon path and
+logon home.
    If you have this set up correctly, you will find separate user.DAT and
+NTuser.DAT files in the same profile directory.
    18.1.4. Profile Migration from Windows NT4/200x Server to Samba
    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.
    18.1.4.1. Windows NT4 Profile Management Tools
    Unfortunately, the Resource Kit information is specific to the version of MS Windows
+NT4/200x. The correct resource kit is required for each platform.
    Here is a quick guide:
    • On your NT4 Domain Controller, right click on 'My Computer', then
+select the tab labelled 'User Profiles'.
    • Select a user profile you want to migrate and click on it.
      I am using the term "migrate" lossely. You can copy a profile to
+create a group profile. You can give the user 'Everyone' rights to the
+profile you copy this to. That is what you need to do, since your samba
+domain is not a member of a trust relationship with your NT4 PDC.
    • Click the 'Copy To' button.
    • In the box labelled 'Copy Profile to' add your new path, eg:
+	c:\temp\foobar
    • Click on the button labelled 'Change' in the "Permitted to use" box.
    • Click on the group 'Everyone' and then click OK. This closes the
+	'chose user' box.
    • Now click OK.
    Follow the above for every profile you need to migrate.
    18.1.4.2. Side bar Notes
    You should obtain the SID of your NT4 domain. You can use smbpasswd to do
+this. Read the man page.
    With Samba-3.0.0 alpha code you can import all you NT4 domain accounts
+using the net samsync method. This way you can retain your profile
+settings as well as all your users.
    18.1.4.3. moveuser.exe
    The W2K professional resource kit has moveuser.exe. moveuser.exe changes
+the security of a profile from one user to another.  This allows the account
+domain to change, and/or the user name to change.
    18.1.4.4. Get SID
    You can identify the SID by using GetSID.exe from the Windows NT Server 4.0
+Resource Kit.
    Windows NT 4.0 stores the local profile information in the registry under
+the following key:
+HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
    Under the ProfileList key, there will be subkeys named with the SIDs of the
+users who have logged on to this computer. (To find the profile information
+for the user whose locally cached profile you want to move, find the SID for
+the user with the GetSID.exe utility.) Inside of the appropriate user's
+subkey, you will see a string value named ProfileImagePath.
    18.2. Mandatory profiles
    A Mandatory Profile is a profile that the user does NOT have the ability to overwrite.
+During the user's session it may be possible to change the desktop environment, but
+as the user logs out all changes made will be lost. If it is desired to NOT allow the
+user any ability to change the desktop environment then this must be done through
+policy settings. See previous chapter.
    Under NO circumstances should the profile directory (or it's contents) be made read-only
+as this may render the profile un-usable.
    For MS Windows NT4/200x/XP the above method can be used to create mandatory profiles
+also. To convert a group profile into a mandatory profile simply locate the NTUser.DAT
+file in the copied profile and rename it to NTUser.MAN.
    For MS Windows 9x / Me it is the User.DAT file that must be renamed to User.MAN to
+affect a mandatory profile.
    18.3. Creating/Managing Group Profiles
    Most organisations are arranged into departments. There is a nice benenfit in
+this fact since usually most users in a department will require the same desktop
+applications and the same desktop layout. MS Windows NT4/200x/XP will allow the
+use of Group Profiles. A Group Profile is a profile that is created firstly using
+a template (example) user. Then using the profile migration tool (see above) the
+profile is assigned access rights for the user group that needs to be given access
+to the group profile.
    The next step is rather important. PLEASE NOTE: Instead of assigning a group profile
+to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned
+the now modified profile.
    	Be careful with group profiles, if the user who is a member of a group also
+	has a personal profile, then the result will be a fusion (merge) of the two.
+	
    18.4. Default Profile for Windows Users
    MS Windows 9x / Me and NT4/200x/XP will use a default profile for any user for whom
+a profile does not already exist. Armed with a knowledge of where the default profile
+is located on the Windows workstation, and knowing which registry keys affect the path
+from which the default profile is created, it is possible to modify the default profile
+to one that has been optimised for the site. This has significant administrative 
+advantages.
    18.4.1. MS Windows 9x/Me
    To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System
+Policy Editor or change the registry directly.
    To enable default per user profiles in Windows 9x / Me, launch the System Policy Editor, then
+select File -> Open Registry, then click on the Local Computer icon, click on Windows 98 System,
+select User Profiles, click on the enable box. Do not forget to save the registry changes.
    To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive
+HKEY_LOCAL_MACHINE\Network\Logon. Now add a DWORD type key with the name
+"User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0.
    18.4.1.1. How User Profiles Are Handled in Windows 9x / Me?
    When a user logs on to a Windows 9x / Me machine, the local profile path, 
+HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList, is checked
+for an existing entry for that user:
    If the user has an entry in this registry location, Windows 9x / Me checks for a locally cached
+version of the user profile. Windows 9x / Me also checks the user's home directory (or other
+specified directory if the location has been modified) on the server for the User Profile.
+If a profile exists in both locations, the newer of the two is used. If the User Profile exists
+on the server, but does not exist on the local machine, the profile on the server is downloaded
+and used. If the User Profile only exists on the local machine, that copy is used.
    If a User Profile is not found in either location, the Default User Profile from the Windows 9x / Me
+machine is used and is copied to a newly created folder for the logged on user. At log off, any
+changes that the user made are written to the user's local profile. If the user has a roaming
+profile, the changes are written to the user's profile on the server.
    18.4.2. MS Windows NT4 Workstation
    On MS Windows NT4 the default user profile is obtained from the location
+%SystemRoot%\Profiles which in a default installation will translate to
+C:\WinNT\Profiles. Under this directory on a clean install there will be
+three (3) directories: Administrator, All Users, Default User.
    The All Users directory contains menu settings that are common across all 
+system users. The Default User directory contains menu entries that are
+customisable per user depending on the profile settings chosen/created.
    When a new user first logs onto an MS Windows NT4 machine a new profile is created from:
    All Users settings
    Default User settings (contains the default NTUser.DAT file)
    When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain
+the following steps are followed in respect of profile handling:
    1. 	The users' account information which is obtained during the logon process contains
+	the location of the users' desktop profile. The profile path may be local to the
+	machine or it may be located on a network share. If there exists a profile at the location
+	of the path from the user account, then this profile is copied to the location
+	%SystemRoot%\Profiles\%USERNAME%. This profile then inherits the
+	settings in the All Users profile in the %SystemRoot%\Profiles
+	location.
+	
    2. 	If the user account has a profile path, but at it's location a profile does not exist,
+	then a new profile is created in the %SystemRoot%\Profiles\%USERNAME%
+	directory from reading the Default User profile.
+	
    3. 	If the NETLOGON share on the authenticating server (logon server) contains a policy file
+	(NTConfig.POL) then it's contents are applied to the NTUser.DAT
+	which is applied to the HKEY_CURRENT_USER part of the registry. 
+	
    4. 	When the user logs out, if the profile is set to be a roaming profile it will be written
+	out to the location of the profile. The NTuser.DAT file is then
+	re-created from the contents of the HKEY_CURRENT_USER contents.
+	Thus, should there not exist in the NETLOGON share an NTConfig.POL at the
+	next logon, the effect of the provious NTConfig.POL will still be held
+	in the profile. The effect of this is known as tatooing.
+	
    MS Windows NT4 profiles may be Local or Roaming. A Local profile
+will stored in the %SystemRoot%\Profiles\%USERNAME% location. A roaming profile will
+also remain stored in the same way, unless the following registry key is created:
    	HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
+	"DeleteRoamingCache"=dword:00000001
    
+
+In which case, the local copy (in %SystemRoot%\Profiles\%USERNAME%) will be
+deleted on logout.
    Under MS Windows NT4 default locations for common resources (like My Documents
+may be redirected to a network share by modifying the following registry keys. These changes may be affected
+via use of the System Policy Editor (to do so may require that you create your owns template extension
+for the policy editor to allow this to be done through the GUI. Another way to do this is by way of first
+creating a default user profile, then while logged in as that user, run regedt32 to edit the key settings.
    The Registry Hive key that affects the behaviour of folders that are part of the default user profile
+are controlled by entries on Windows NT4 is:
            HKEY_CURRENT_USER
+                \Software
+                        \Microsoft
+                                \Windows
+                                        \CurrentVersion
+                                                \Explorer
+                                                        \User Shell Folders\
    The above hive key contains a list of automatically managed folders. The default entries are:
            
            Name            Default Value
+        --------------  -----------------------------------------
+        AppData         %USERPROFILE%\Application Data
+        Desktop         %USERPROFILE%\Desktop
+        Favorites       %USERPROFILE%\Favorites
+        NetHood         %USERPROFILE%\NetHood
+        PrintHood       %USERPROFILE%\PrintHood
+        Programs        %USERPROFILE%\Start Menu\Programs
+        Recent          %USERPROFILE%\Recent
+        SendTo          %USERPROFILE%\SendTo
+        Start Menu      %USERPROFILE%\Start Menu
+        Startup         %USERPROFILE%\Start Menu\Programs\Startup
+        
    
+        
    The registry key that contains the location of the default profile settings is:
+
+
    	HKEY_LOCAL_MACHINE
+		\SOFTWARE
+			\Microsoft
+				\Windows
+					\CurrentVersion
+						\Explorer
+							\User Shell Folders
    
+
+The default entries are:
+
+
    	Common Desktop		%SystemRoot%\Profiles\All Users\Desktop
+	Common Programs		%SystemRoot%\Profiles\All Users\Programs
+	Common Start Menu	%SystemRoot%\Profiles\All Users\Start Menu
+	Common Startu	p	%SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup
    18.4.3. MS Windows 200x/XP
    	MS Windows XP Home Edition does use default per user profiles, but can not participate
+	in domain security, can not log onto an NT/ADS style domain, and thus can obtain the profile
+	only from itself. While there are benefits in doing this the beauty of those MS Windows
+	clients that CAN participate in domain logon processes allows the administrator to create
+	a global default profile and to enforce it through the use of Group Policy Objects (GPOs).
+	
    When a new user first logs onto MS Windows 200x/XP machine the default profile is obtained from
+C:\Documents and Settings\Default User. The administrator can modify (or change
+the contents of this location and MS Windows 200x/XP will gladly user it. This is far from the optimum
+arrangement since it will involve copying a new default profile to every MS Windows 200x/XP client
+workstation. 
    When MS Windows 200x/XP participate in a domain security context, and if the default user
+profile is not found, then the client will search for a default profile in the NETLOGON share
+of the authenticating server. ie: In MS Windows parlance:
+%LOGONSERVER%\NETLOGON\Default User and if one exits there it will copy this
+to the workstation to the C:\Documents and Settings\ under the Windows
+login name of the user.
    	This path translates, in Samba parlance, to the smb.conf [NETLOGON] share. The directory
+	should be created at the root of this share and msut be called Default Profile.
+	
    If a default profile does not exist in this location then MS Windows 200x/XP will use the local
+default profile.
    On loging out, the users' desktop profile will be stored to the location specified in the registry
+settings that pertain to the user. If no specific policies have been created, or passed to the client
+during the login process (as Samba does automatically), then the user's profile will be written to
+the local machine only under the path C:\Documents and Settings\%USERNAME%.
    Those wishing to modify the default behaviour can do so through up to three methods:
    • 	Modify the registry keys on the local machine manually and place the new default profile in the
+	NETLOGON share root - NOT recommended as it is maintenance intensive.
+	
    • 	Create an NT4 style NTConfig.POL file that specified this behaviour and locate this file
+	in the root of the NETLOGON share along with the new default profile.
+	
    • 	Create a GPO that enforces this through Active Directory, and place the new default profile
+	in the NETLOGON share.
+	
    The Registry Hive key that affects the behaviour of folders that are part of the default user profile
+are controlled by entries on Windows 200x/XP is:
    	HKEY_CURRENT_USER
+		\Software
+			\Microsoft
+				\Windows
+					\CurrentVersion
+						\Explorer
+							\User Shell Folders\
    The above hive key contains a list of automatically managed folders. The default entries are:
    	
    	Name		Default Value
+	--------------	-----------------------------------------
+	AppData		%USERPROFILE%\Application Data
+	Cache		%USERPROFILE%\Local Settings\Temporary Internet Files
+	Cookies		%USERPROFILE%\Cookies
+	Desktop		%USERPROFILE%\Desktop
+	Favorites	%USERPROFILE%\Favorites
+	History		%USERPROFILE%\Local Settings\History
+	Local AppData	%USERPROFILE%\Local Settings\Application Data
+	Local Settings	%USERPROFILE%\Local Settings
+	My Pictures	%USERPROFILE%\My Documents\My Pictures
+	NetHood		%USERPROFILE%\NetHood
+	Personal	%USERPROFILE%\My Documents
+	PrintHood	%USERPROFILE%\PrintHood
+	Programs	%USERPROFILE%\Start Menu\Programs
+	Recent		%USERPROFILE%\Recent
+	SendTo		%USERPROFILE%\SendTo
+	Start Menu	%USERPROFILE%\Start Menu
+	Startup		%USERPROFILE%\Start Menu\Programs\Startup
+	Templates	%USERPROFILE%\Templates
+	
    
+	
    There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all
+the others are of type REG_EXPAND_SZ.
    It makes a huge difference to the speed of handling roaming user profiles if all the folders are
+stored on a dedicated location on a network server. This means that it will NOT be necessary to
+write Outlook PST file over the network for every login and logout.
    To set this to a network location you could use the following examples:
+
+
    	%LOGONSERVER%\%USERNAME%\Default Folders
    
+
+This would store the folders in the user's home directory under a directory called "Default Folders"
+
+You could also use:
+
+
    	\\SambaServer\FolderShare\%USERNAME%
    
+
+in which case the default folders will be stored in the server named SambaServer
+in the share called FolderShare under a directory that has the name of the MS Windows
+user as seen by the Linux/Unix file system.
    Please note that once you have created a default profile share, you MUST migrate a user's profile
+(default or custom) to it.
    MS Windows 200x/XP profiles may be Local or Roaming.
+A roaming profile will be cached locally unless the following registry key is created:
    	HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
+	"DeleteRoamingCache"=dword:00000001
    
+
+In which case, the local cache copy will be deleted on logout.
    PrevHomeNext
    System and Account PoliciesUpInterdomain Trust Relationships
    
\ No newline at end of file
diff --git a/docs/htmldocs/profiles.1.html b/docs/htmldocs/profiles.1.html
new file mode 100644
index 0000000000..53deae6f28
--- /dev/null
+++ b/docs/htmldocs/profiles.1.html
@@ -0,0 +1,139 @@
+
+profiles
    profiles
    Name
    profiles -- A utility to report and change SIDs in registry files
+	
    Synopsis
    profiles  [-v] [-c SID] [-n SID] {file}
    DESCRIPTION
    This tool is part of the Samba(7) suite.
    profiles is a utility that 
+	reports and changes SIDs in windows registry files. It currently only 
+	supports NT.
+	
    OPTIONS
    file
    Registry file to view or edit.  
    -v,--verbose
    Increases verbosity of messages. 
+		
    -c SID1 -n SID2
    Change all occurences of SID1 in file by SID2.
+		
    -h|--help
    Print a summary of command line options.
    VERSION
    This man page is correct for version 3.0 of the Samba 
+	suite.
    AUTHOR
    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.
    The profiles man page was written by Jelmer Vernooij. 
    
\ No newline at end of file
diff --git a/docs/htmldocs/servertype.html b/docs/htmldocs/servertype.html
new file mode 100644
index 0000000000..c52ed3208b
--- /dev/null
+++ b/docs/htmldocs/servertype.html
@@ -0,0 +1,368 @@
+
+Nomenclature of Server Types
    SAMBA Project Documentation
    PrevNext
    Chapter 5. Nomenclature of Server Types
    Adminstrators of Microsoft networks often refer to there being three
+different type of servers:
    • Stand Alone Server
    • Domain Member Server
    • Domain Controller
      • Primary Domain Controller
      • Backup Domain Controller
      • ADS Domain Controller
    A network administrator who is familiar with these terms and who
+wishes to migrate to or use Samba will want to know what these terms mean
+within a Samba context.
    5.1. Stand Alone Server
    The term stand alone server means that the server
+will provide local authentication and access control for all resources
+that are available from it. In general this means that there will be a
+local user database. In more technical terms, it means that resources
+on the machine will either be made available in either SHARE mode or in
+USER mode. SHARE mode and USER mode security are documented under
+discussions regarding "security mode". The smb.conf configuration parameters
+that control security mode are: "security = user" and "security = share".
    No special action is needed other than to create user accounts. Stand-alone
+servers do NOT provide network logon services, meaning that machines that
+use this server do NOT perform a domain logon but instead make use only of
+the MS Windows logon which is local to the MS Windows workstation/server.
    Samba tends to blur the distinction a little in respect of what is
+a stand alone server. This is because the authentication database may be
+local or on a remote server, even if from the samba protocol perspective
+the samba server is NOT a member of a domain security context.
    Through the use of PAM (Pluggable Authentication Modules) and nsswitch
+(the name service switcher) the source of authentication may reside on 
+another server. We would be inclined to call this the authentication server.
+This means that the samba server may use the local Unix/Linux system
+password database (/etc/passwd or /etc/shadow), may use a local smbpasswd
+file (/etc/samba/smbpasswd or /usr/local/samba/lib/private/smbpasswd), or
+may use an LDAP back end, or even via PAM and Winbind another CIFS/SMB
+server for authentication.
    5.2. Domain Member Server
    This mode of server operation involves the samba machine being made a member
+of a domain security context. This means by definition that all user authentication
+will be done from a centrally defined authentication regime. The authentication
+regime may come from an NT3/4 style (old domain technology) server, or it may be
+provided from an Active Directory server (ADS) running on MS Windows 2000 or later.
    Of course it should be clear that the authentication back end itself could be from any
+distributed directory architecture server that is supported by Samba. This can be
+LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory Server, etc.
    Please refer to the section on Howto configure Samba as a Primary Domain Controller
+and for more information regarding how to create a domain machine account for a
+domain member server as well as for information regading how to enable the samba
+domain member machine to join the domain and to be fully trusted by it.
    5.3. Domain Controller
    Over the years public perceptions of what Domain Control really is has taken on an
+almost mystical nature. Before we branch into a brief overview of what Domain Control
+is the following types of controller are known:
    5.3.1. Domain Controller Types
    Primary Domain Controller
    Backup Domain Controller
    ADS Domain Controller
    The Primary Domain Controller or PDC plays an important role in the MS 
+Windows NT3 and NT4 Domain Control architecture, but not in the manner that so many
+expect. The PDC seeds the Domain Control database (a part of the Windows registry) and
+it plays a key part in synchronisation of the domain authentication database. 
    New to Samba-3.0.0 is the ability to use a back-end file that holds the same type of data as
+the NT4 style SAM (Security Account Manager) database (one of the registry files).
+The samba-3.0.0 SAM can be specified via the smb.conf file parameter "passwd backend" and
+valid options include  smbpasswd tdbsam ldapsam nisplussam plugin unixsam.
+The smbpasswd, tdbsam and ldapsam options can have a "_nua" suffix to indicate that No Unix
+Accounts need to be created. In other words, the Samba SAM will be independant of Unix/Linux
+system accounts, provided a uid range is defined from which SAM accounts can be created.
    The Backup Domain Controller or BDC plays a key role in servicing network
+authentication requests. The BDC is biased to answer logon requests so that on a network segment
+that has a BDC and a PDC the BDC will be most likely to service network logon requests. The PDC will
+answer network logon requests when the BDC is too busy (high load). A BDC can be promoted to
+a PDC. If the PDC is on line at the time that the BDC is promoted to PDC the previous PDC is
+automatically demoted to a BDC.
    At this time Samba is NOT capable of acting as an ADS Domain Controller.
    PrevHomeNext
    Type of installationUpSamba as Stand-Alone Server
    
\ No newline at end of file
diff --git a/docs/htmldocs/smbcquotas.1.html b/docs/htmldocs/smbcquotas.1.html
new file mode 100644
index 0000000000..334f08bbb9
--- /dev/null
+++ b/docs/htmldocs/smbcquotas.1.html
@@ -0,0 +1,391 @@
+
+smbcquotas
    smbcquotas
    Name
    smbcquotas -- Set or get QUOTAs of NTFS 5 shares
    Synopsis
    smbcquotas  {//server/share} [-u user] [-L] [-F] [-S QUOTA_SET_COMMAND] [-n] [-t] [-v] [-d debuglevel] [-s configfile] [-l logfilebase] [-V] [-U username] [-N] [-k] [-A]
    DESCRIPTION
    This tool is part of the Samba(7) suite.
    The smbcquotas program manipulates NT Quotas on SMB file shares. 
    OPTIONS
    The following options are available to the smbcquotas program. 
    -u user
     Specifies the user of whom the quotas are get or set.
+		By default the current user's username will be used.
    -L
    Lists all quota records of the share.
    -F
    Show the share quota status and default limits.
    -S QUOTA_SET_COMMAND
    This command set/modify quotas for a user or on the share,
+		depending on the QUOTA_SET_COMMAND parameter witch is described later
    -n
    This option displays all QUOTA information in numeric 
+		format.  The default is to convert SIDs to names and QUOTA limits 
+		to a readable string format.  
    -t
    		Don't actually do anything, only validate the correctness of 
+		the arguments.
+		
    -v
    		Be verbose.
+		
    -h|--help
    Print a summary of command line options.
    -V
    Prints the version number for 
+smbd.
    -s <configuration file>
    The file specified contains the 
+configuration details required by the server.  The 
+information in this file includes server-specific
+information such as what printcap file to use, as well 
+as descriptions of all the services that the server is 
+to provide. See smb.conf(5) for more information.
+The default configuration file name is determined at 
+compile time.
    -d|--debug=debuglevel
    debuglevel is an integer 
+from 0 to 10.  The default value if this parameter is 
+not specified is zero.
    The higher this value, the more detail will be 
+logged to the log files about the activities of the 
+server. At level 0, only critical errors and serious 
+warnings will be logged. Level 1 is a reasonable level for
+day to day running - it generates a small amount of 
+information about operations carried out.
    Levels above 1 will generate considerable 
+amounts of log data, and should only be used when 
+investigating a problem. Levels above 3 are designed for 
+use only by developers and generate HUGE amounts of log
+data, most of which is extremely cryptic.
    Note that specifying this parameter here will 
+override the log
+level parameter in the smb.conf(5) file.
    -l|--logfile=logbasename
    File name for log/debug files. The extension
+".client" will be appended. The log file is
+never removed by the client.
    -N
    If specified, this parameter suppresses the normal
+password prompt from the client to the user. This is useful when
+accessing a service that does not require a password. 
    Unless a password is specified on the command line or
+this parameter is specified, the client will request a
+password.
    -k
    Try to authenticate with kerberos. Only useful in
+an Active Directory environment.
    -A|--authfile=filename
    This option allows
+you to specify a file from which to read the username and
+password used in the connection.  The format of the file is
    username = <value>
+password = <value>
+domain   = <value>
    Make certain that the permissions on the file restrict 
+access from unwanted users. 
    -U|--user=username[%password]
    Sets the SMB username or username and password. 
    If %password is not specified, the user will be prompted. The
+client will first check the USER environment variable, then the
+LOGNAME variable and if either exists, the
+string is uppercased. If these environmental variables are not
+found, the username GUEST is used. 
    A third option is to use a credentials file which
+contains the plaintext of the username and password.  This
+option is mainly provided for scripts where the admin does not
+wish to pass the credentials on the command line or via environment
+variables. If this method is used, make certain that the permissions
+on the file restrict access from unwanted users.  See the
+-A for more details. 
    Be cautious about including passwords in scripts. Also, on
+many systems the command line of a running process may be seen
+via the ps command.  To be safe always allow
+rpcclient to prompt for a password and type
+it in directly. 
    QUOTA_SET_COMAND
    The format of an ACL is one or more ACL entries separated by 
+	either commas or newlines.  An ACL entry is one of the following: 
    	for user setting quotas for the specified by -u or the current username:
+	
    	UQLIM:<username><softlimit><hardlimit>
+	
    	for setting the share quota defaults limits:
+	
    	FSQLIM:<softlimit><hardlimit>
+	
    	for changing the share quota settings:
+	
    	FSQFLAGS:QUOTA_ENABLED/DENY_DISK/LOG_SOFTLIMIT/LOG_HARD_LIMIT
+	
    EXIT STATUS
    The smbcquotas program sets the exit status
+	depending on the success or otherwise of the operations performed.
+	The exit status may be one of the following values. 
    If the operation succeeded, smbcquotas returns an exit
+	status of 0.  If smbcquotas couldn't connect to the specified server,
+	or when there was an error getting or setting the quota(s), an exit status
+	of 1 is returned.  If there was an error parsing any command line
+	arguments, an exit status of 2 is returned. 
    VERSION
    This man page is correct for version 3.0 of the Samba suite.
    AUTHOR
    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.
    smbcacls was written by Stefan Metzmacher.
    
\ No newline at end of file
diff --git a/docs/htmldocs/smbtree.1.html b/docs/htmldocs/smbtree.1.html
new file mode 100644
index 0000000000..e3edbc8681
--- /dev/null
+++ b/docs/htmldocs/smbtree.1.html
@@ -0,0 +1,304 @@
+
+smbtree
    smbtree
    Name
    smbtree -- A text based smb network browser
+	
    Synopsis
    smbtree  [-b] [-D] [-S]
    DESCRIPTION
    This tool is part of the Samba(7) suite.
    smbtree is a smb browser program 
+	in text mode. It is similar to the "Network Neighborhood" found 
+	on Windows computers. It prints a tree with all 
+	the known domains, the servers in those domains and 
+	the shares on the servers.
+	
    OPTIONS
    -b
    Query network nodes by sending requests 
+		as broadcasts instead of querying the (domain) master browser.
+		
    -D
    Only print a list of all 
+		the domains known on broadcast or by the 
+		master browser
    -S
    Only print a list of 
+		all the domains and servers responding on broadcast or 
+		known by the master browser. 
+		
    -V
    Prints the version number for 
+smbd.
    -s <configuration file>
    The file specified contains the 
+configuration details required by the server.  The 
+information in this file includes server-specific
+information such as what printcap file to use, as well 
+as descriptions of all the services that the server is 
+to provide. See smb.conf(5) for more information.
+The default configuration file name is determined at 
+compile time.
    -d|--debug=debuglevel
    debuglevel is an integer 
+from 0 to 10.  The default value if this parameter is 
+not specified is zero.
    The higher this value, the more detail will be 
+logged to the log files about the activities of the 
+server. At level 0, only critical errors and serious 
+warnings will be logged. Level 1 is a reasonable level for
+day to day running - it generates a small amount of 
+information about operations carried out.
    Levels above 1 will generate considerable 
+amounts of log data, and should only be used when 
+investigating a problem. Levels above 3 are designed for 
+use only by developers and generate HUGE amounts of log
+data, most of which is extremely cryptic.
    Note that specifying this parameter here will 
+override the log
+level parameter in the smb.conf(5) file.
    -l|--logfile=logbasename
    File name for log/debug files. The extension
+".client" will be appended. The log file is
+never removed by the client.
    -N
    If specified, this parameter suppresses the normal
+password prompt from the client to the user. This is useful when
+accessing a service that does not require a password. 
    Unless a password is specified on the command line or
+this parameter is specified, the client will request a
+password.
    -k
    Try to authenticate with kerberos. Only useful in
+an Active Directory environment.
    -A|--authfile=filename
    This option allows
+you to specify a file from which to read the username and
+password used in the connection.  The format of the file is
    username = <value>
+password = <value>
+domain   = <value>
    Make certain that the permissions on the file restrict 
+access from unwanted users. 
    -U|--user=username[%password]
    Sets the SMB username or username and password. 
    If %password is not specified, the user will be prompted. The
+client will first check the USER environment variable, then the
+LOGNAME variable and if either exists, the
+string is uppercased. If these environmental variables are not
+found, the username GUEST is used. 
    A third option is to use a credentials file which
+contains the plaintext of the username and password.  This
+option is mainly provided for scripts where the admin does not
+wish to pass the credentials on the command line or via environment
+variables. If this method is used, make certain that the permissions
+on the file restrict access from unwanted users.  See the
+-A for more details. 
    Be cautious about including passwords in scripts. Also, on
+many systems the command line of a running process may be seen
+via the ps command.  To be safe always allow
+rpcclient to prompt for a password and type
+it in directly. 
    -h|--help
    Print a summary of command line options.
    VERSION
    This man page is correct for version 3.0 of the Samba 
+	suite.
    AUTHOR
    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.
    The smbtree man page was written by Jelmer Vernooij. 
    
\ No newline at end of file
diff --git a/docs/htmldocs/swat.html b/docs/htmldocs/swat.html
new file mode 100644
index 0000000000..b6f36034a8
--- /dev/null
+++ b/docs/htmldocs/swat.html
@@ -0,0 +1,233 @@
+
+SWAT - The Samba Web Admininistration Tool
    SAMBA Project Documentation
    PrevNext
    Chapter 31. SWAT - The Samba Web Admininistration Tool
    This is a rough guide to SWAT.
    31.1. SWAT Features and Benefits
    You must use at least the following ...
    31.1.2. Global Settings
    Document steps right here!
    31.1.3. The SWAT Wizard
    Lots of blah blah here.
    31.1.4. Share Settings
    Document steps right here!
    31.1.5. Printing Settings
    Document steps right here!
    31.1.6. The Status Page
    Document steps right here!
    31.1.7. The Password Change Page
    Document steps right here!
    PrevHomeNext
    Samba and other CIFS clientsUpSamba performance issues
    
\ No newline at end of file
diff --git a/docs/htmldocs/unicode.html b/docs/htmldocs/unicode.html
new file mode 100644
index 0000000000..89a70cbee8
--- /dev/null
+++ b/docs/htmldocs/unicode.html
@@ -0,0 +1,301 @@
+
+Unicode/Charsets
    SAMBA Project Documentation
    PrevNext
    Chapter 26. Unicode/Charsets
    26.1. What are charsets and unicode?
    Computers communicate in numbers. In texts, each number will be 
+translated to a corresponding letter. The meaning that will be assigned 
+to a certain number depends on the character set(charset) that is used. 
+A charset can be seen as a table that is used to translate numbers to 
+letters. Not all computers use the same charset (there are charsets 
+with German umlauts, Japanese characters, etc). Usually a charset contains 
+256 characters, which means that storing a character with it takes 
+exactly one byte. 
    There are also charsets that support even more characters, 
+but those need twice(or even more) as much storage space. These 
+charsets can contain 256 * 256 = 65536 characters, which
+is more then all possible characters one could think of. They are called 
+multibyte charsets (because they use more then one byte to 
+store one character). 
    A standardised multibyte charset is unicode, info available at 
+www.unicode.org. 
+Big advantage of using a multibyte charset is that you only need one; no 
+need to make sure two computers use the same charset when they are 
+communicating.
    Old windows clients used to use single-byte charsets, named 
+'codepages' by microsoft. However, there is no support for 
+negotiating the charset to be used in the smb protocol. Thus, you 
+have to make sure you are using the same charset when talking to an old client.
+Newer clients (Windows NT, 2K, XP) talk unicode over the wire.
    26.2. Samba and charsets
    As of samba 3.0, samba can (and will) talk unicode over the wire. Internally, 
+samba knows of three kinds of character sets: 
    unix charset
    		This is the charset used internally by your operating system. 
+		The default is ASCII, which is fine for most 
+		systems.
+		
    display charset
    This is the charset samba will use to print messages
+		on your screen. It should generally be the same as the unix charset.
+		
    dos charset
    This is the charset samba uses when communicating with 
+		DOS and Windows 9x clients. It will talk unicode to all newer clients.
+		The default depends on the charsets you have installed on your system.
+		Run testparm -v | grep "dos charset" to see 
+		what the default is on your system. 
+		
    26.3. Conversion from old names
    Because previous samba versions did not do any charset conversion, 
+characters in filenames are usually not correct in the unix charset but only 
+for the local charset used by the DOS/Windows clients.
    The following script from Steve Langasek converts all 
+filenames from CP850 to the iso8859-15 charset.
    #find /path/to/share -type f -exec bash -c 'CP="{}"; ISO=`echo -n "$CP" | iconv -f cp850 \
+  -t iso8859-15`; if [ "$CP" != "$ISO" ]; then mv "$CP" "$ISO"; fi' \;
    PrevHomeNext
    Securing SambaUpAppendixes
    
\ No newline at end of file
diff --git a/docs/manpages/editreg.1 b/docs/manpages/editreg.1
new file mode 100644
index 0000000000..b9b5b673f3
--- /dev/null
+++ b/docs/manpages/editreg.1
@@ -0,0 +1,45 @@
+.\" This manpage has been automatically generated by docbook2man 
+.\" from a DocBook document.  This tool can be found at:
+.\"  
+.\" Please send any bug reports, improvements, comments, patches, 
+.\" etc. to Steve Cheng .
+.TH "EDITREG" "1" "17 April 2003" "" ""
+
+.SH NAME
+editreg \- A utility to report and change SIDs in registry files
+.SH SYNOPSIS
+
+\fBeditreg\fR [ \fB-v\fR ] [ \fB-c file\fR ] \fBfile\fR
+
+.SH "DESCRIPTION"
+.PP
+This tool is part of the \fBSamba\fR(7) suite.
+.PP
+\fBeditreg\fR is a utility that 
+can visualize windows registry files (currently only NT4) and apply 
+so-called commandfiles to them. 
+.SH "OPTIONS"
+.TP
+\fBregistry_file\fR
+Registry file to view or edit.  
+.TP
+\fB-v,--verbose\fR
+Increases verbosity of messages. 
+.TP
+\fB-c commandfile\fR
+Read commands to execute on \fIregistry_file\fR from \fIcommandfile\fR. Currently not yet supported!
+.TP
+\fB-h|--help\fR
+Print a summary of command line options.
+.SH "VERSION"
+.PP
+This man page is correct for version 3.0 of the Samba 
+suite.
+.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 editreg man page was written by Jelmer Vernooij. 
diff --git a/docs/manpages/manpage.links b/docs/manpages/manpage.links
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/docs/manpages/manpage.refs b/docs/manpages/manpage.refs
new file mode 100644
index 0000000000..81323bebe1
--- /dev/null
+++ b/docs/manpages/manpage.refs
@@ -0,0 +1,39 @@
+{
+  '' => '',
+  'refentry:SMBGROUPEDIT.8' => 'smbgroupedit(8)',
+  'refentry:NET.8' => 'net(8)',
+  'refentry:SAMBA.7' => 'samba(7)',
+  'refentry:SMBSTATUS.1' => 'smbstatus(1)',
+  'refentry:SMBCACLS.1' => 'smbcacls(1)',
+  'refentry:WBINFO.1' => 'wbinfo(1)',
+  'refentry:NTLM-AUTH.1' => 'ntlm_auth(1)',
+  'refentry:SMBPASSWD.8' => 'smbpasswd(8)',
+  'refentry:SMB.CONF.5' => 'smb.conf(5)',
+  'refentry:FINDSMB.1' => 'findsmb(1)',
+  'refentry:SMBCONTROL.1' => 'smbcontrol(1)',
+  'refentry:TESTPRNS.1' => 'testprns(1)',
+  'refentry:SMBPASSWD.5' => 'smbpasswd(5)',
+  'refentry:SMBD.8' => 'smbd(8)',
+  'refentry:SMBTREE.1' => 'smbtree(1)',
+  'refentry:EDITREG.1' => 'editreg(1)',
+  'refentry:SMBCLIENT.1' => 'smbclient(1)',
+  'refentry:WINBINDD.8' => 'winbindd(8)',
+  'refentry:NMBLOOKUP' => 'nmblookup(1)',
+  'refentry:SMBMOUNT.8' => 'smbmount(8)',
+  'refentry:SMBCQUOTAS.1' => 'smbcquotas(1)',
+  'refentry:PDBEDIT.8' => 'pdbedit(8)',
+  'refentry:NTLM_AUTH.1' => 'ntlm_auth(1)',
+  'refentry:SWAT.8' => 'swat(8)',
+  'refentry:PROFILES.1' => 'profiles(1)',
+  'refentry:LMHOSTS.5' => 'lmhosts(5)',
+  'refentry:SMBMNT.8' => 'smbmnt(8)',
+  'refentry:SMBSH.1' => 'smbsh(1)',
+  'refentry:SMBSPOOL.8' => 'smbspool(8)',
+  'refentry:RPCCLIENT.1' => 'rpcclient(1)',
+  'refentry:VFSTEST.1' => 'vfstest(1)',
+  'refentry:NMBD.8' => 'nmbd(8)',
+  'refentry:TESTPARM.1' => 'testparm(1)',
+  'refentry:SMBUMOUNT.8' => 'smbumount(8)',
+  'refentry:SMBTAR.1' => 'smbtar(1)',
+  '' => ''
+}
diff --git a/docs/manpages/ntlm_auth.1 b/docs/manpages/ntlm_auth.1
new file mode 100644
index 0000000000..bb562fe964
--- /dev/null
+++ b/docs/manpages/ntlm_auth.1
@@ -0,0 +1,109 @@
+.\" This manpage has been automatically generated by docbook2man 
+.\" from a DocBook document.  This tool can be found at:
+.\"  
+.\" Please send any bug reports, improvements, comments, patches, 
+.\" etc. to Steve Cheng .
+.TH "NTLM_AUTH" "1" "17 April 2003" "" ""
+
+.SH NAME
+ntlm_auth \- tool to allow external access to Winbind's NTLM authentication function
+.SH SYNOPSIS
+
+\fBntlm_auth\fR [ \fB-d debuglevel\fR ] [ \fB-l logfile\fR ] [ \fB-s \fR ]
+
+.SH "DESCRIPTION"
+.PP
+This tool is part of the \fBSamba\fR(7) suite.
+.PP
+\fBntlm_auth\fR is a helper utility that authenticates 
+users using NT/LM authentication. It returns 0 if the users is authenticated
+successfully and 1 if access was denied. ntlm_auth uses winbind to access 
+the user and authentication data for a domain. This utility 
+is only to be used by other programs (currently squid).
+.SH "OPTIONS"
+.TP
+\fB--helper-protocol=PROTO\fR
+Operate as a stdio-based helper
+.TP
+\fB--username=USERNAME\fR
+Specify username of user to authenticate
+.TP
+\fB--domain=DOMAIN\fR
+Specify domain of user to authenticate
+.TP
+\fB--workstation=WORKSTATION\fR
+Specify the workstation the user authenticated from
+.TP
+\fB--challenge=STRING\fR
+challenge (HEX encoded)
+.TP
+\fB--lm-response=RESPONSE\fR
+LM Response to the challenge (HEX encoded)
+.TP
+\fB--nt-response=RESPONSE\fR
+NT or NTLMv2 Response to the challenge (HEX encoded)
+.TP
+\fB--password=PASSWORD\fR
+User's plaintext password
+.TP
+\fB--request-lm-key\fR
+Retreive LM session key
+.TP
+\fB--request-nt-key\fR
+Request NT key
+.TP
+\fB-V\fR
+Prints the version number for 
+\fBsmbd\fR.
+.TP
+\fB-s \fR
+The file specified contains the 
+configuration details required by the server.  The 
+information in this file includes server-specific
+information such as what printcap file to use, as well 
+as descriptions of all the services that the server is 
+to provide. See \fIsmb.conf(5)\fR for more information.
+The default configuration file name is determined at 
+compile time.
+.TP
+\fB-d|--debug=debuglevel\fR
+\fIdebuglevel\fR is an integer 
+from 0 to 10.  The default value if this parameter is 
+not specified is zero.
+
+The higher this value, the more detail will be 
+logged to the log files about the activities of the 
+server. At level 0, only critical errors and serious 
+warnings will be logged. Level 1 is a reasonable level for
+day to day running - it generates a small amount of 
+information about operations carried out.
+
+Levels above 1 will generate considerable 
+amounts of log data, and should only be used when 
+investigating a problem. Levels above 3 are designed for 
+use only by developers and generate HUGE amounts of log
+data, most of which is extremely cryptic.
+
+Note that specifying this parameter here will 
+override the log
+level file.
+.TP
+\fB-l|--logfile=logbasename\fR
+File name for log/debug files. The extension
+".client" will be appended. The log file is
+never removed by the client.
+.TP
+\fB-h|--help\fR
+Print a summary of command line options.
+.SH "VERSION"
+.PP
+This man page is correct for version 3.0 of the Samba 
+suite.
+.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 ntlm_auth manpage was written by Jelmer Vernooij.
diff --git a/docs/manpages/profiles.1 b/docs/manpages/profiles.1
new file mode 100644
index 0000000000..6ce5478e49
--- /dev/null
+++ b/docs/manpages/profiles.1
@@ -0,0 +1,45 @@
+.\" This manpage has been automatically generated by docbook2man 
+.\" from a DocBook document.  This tool can be found at:
+.\"  
+.\" Please send any bug reports, improvements, comments, patches, 
+.\" etc. to Steve Cheng .
+.TH "PROFILES" "1" "17 April 2003" "" ""
+
+.SH NAME
+profiles \- A utility to report and change SIDs in registry files
+.SH SYNOPSIS
+
+\fBprofiles\fR [ \fB-v\fR ] [ \fB-c SID\fR ] [ \fB-n SID\fR ] \fBfile\fR
+
+.SH "DESCRIPTION"
+.PP
+This tool is part of the \fBSamba\fR(7) suite.
+.PP
+\fBprofiles\fR is a utility that 
+reports and changes SIDs in windows registry files. It currently only 
+supports NT.
+.SH "OPTIONS"
+.TP
+\fBfile\fR
+Registry file to view or edit.  
+.TP
+\fB-v,--verbose\fR
+Increases verbosity of messages. 
+.TP
+\fB-c SID1 -n SID2\fR
+Change all occurences of SID1 in \fIfile\fR by SID2.
+.TP
+\fB-h|--help\fR
+Print a summary of command line options.
+.SH "VERSION"
+.PP
+This man page is correct for version 3.0 of the Samba 
+suite.
+.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 profiles man page was written by Jelmer Vernooij. 
diff --git a/docs/manpages/smb.conf.5 b/docs/manpages/smb.conf.5
index 70e1731220..64c5547dc5 100644
--- a/docs/manpages/smb.conf.5
+++ b/docs/manpages/smb.conf.5
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMB.CONF" "5" "07 april 2003" "" ""
+.TH "SMB.CONF" "5" "17 April 2003" "" ""
 
 .SH NAME
 smb.conf \- The configuration file for the Samba suite
@@ -2591,8 +2591,7 @@ This boolean controls whether encrypted passwords
 will be negotiated with the client. Note that Windows NT 4.0 SP3 and 
 above and also Windows 98 will by default expect encrypted passwords 
 unless a registry entry is changed. To use encrypted passwords in 
-Samba see the file ENCRYPTION.txt in the Samba documentation 
-directory \fIdocs/\fR shipped with the source code.
+Samba see the chapter User Database in the Samba HOWTO Collection.
 
 In order for encrypted passwords to work correctly
 \fBsmbd\fR(8) must either 
diff --git a/docs/manpages/smbcacls.1 b/docs/manpages/smbcacls.1
index b82871cd7f..48cac295cc 100644
--- a/docs/manpages/smbcacls.1
+++ b/docs/manpages/smbcacls.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBCACLS" "1" "07 april 2003" "" ""
+.TH "SMBCACLS" "1" "17 April 2003" "" ""
 
 .SH NAME
 smbcacls \- Set or get ACLs on an NT file or directory names
diff --git a/docs/manpages/smbclient.1 b/docs/manpages/smbclient.1
index 0b6a5a4679..449cd0863e 100644
--- a/docs/manpages/smbclient.1
+++ b/docs/manpages/smbclient.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBCLIENT" "1" "07 april 2003" "" ""
+.TH "SMBCLIENT" "1" "17 April 2003" "" ""
 
 .SH NAME
 smbclient \- ftp-like client to access SMB/CIFS resources  on servers
diff --git a/docs/manpages/smbcontrol.1 b/docs/manpages/smbcontrol.1
index 14ce9f5812..eab84a45ba 100644
--- a/docs/manpages/smbcontrol.1
+++ b/docs/manpages/smbcontrol.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBCONTROL" "1" "07 april 2003" "" ""
+.TH "SMBCONTROL" "1" "17 April 2003" "" ""
 
 .SH NAME
 smbcontrol \- send messages to smbd, nmbd or winbindd processes
diff --git a/docs/manpages/smbcquotas.1 b/docs/manpages/smbcquotas.1
new file mode 100644
index 0000000000..011cb26ef0
--- /dev/null
+++ b/docs/manpages/smbcquotas.1
@@ -0,0 +1,183 @@
+.\" This manpage has been automatically generated by docbook2man 
+.\" from a DocBook document.  This tool can be found at:
+.\"  
+.\" Please send any bug reports, improvements, comments, patches, 
+.\" etc. to Steve Cheng .
+.TH "SMBCQUOTAS" "1" "17 April 2003" "" ""
+
+.SH NAME
+smbcquotas \- Set or get QUOTAs of NTFS 5 shares
+.SH SYNOPSIS
+
+\fBsmbcquotas\fR \fB//server/share\fR [ \fB-u user\fR ] [ \fB-L\fR ] [ \fB-F\fR ] [ \fB-S QUOTA_SET_COMMAND\fR ] [ \fB-n\fR ] [ \fB-t\fR ] [ \fB-v\fR ] [ \fB-d debuglevel\fR ] [ \fB-s configfile\fR ] [ \fB-l logfilebase\fR ] [ \fB-V\fR ] [ \fB-U username\fR ] [ \fB-N\fR ] [ \fB-k\fR ] [ \fB-A\fR ]
+
+.SH "DESCRIPTION"
+.PP
+This tool is part of the \fBSamba\fR(7) suite.
+.PP
+The \fBsmbcquotas\fR program manipulates NT Quotas on SMB file shares. 
+.SH "OPTIONS"
+.PP
+The following options are available to the \fBsmbcquotas\fR program. 
+.TP
+\fB-u user\fR
+Specifies the user of whom the quotas are get or set.
+By default the current user's username will be used.
+.TP
+\fB-L\fR
+Lists all quota records of the share.
+.TP
+\fB-F\fR
+Show the share quota status and default limits.
+.TP
+\fB-S QUOTA_SET_COMMAND\fR
+This command set/modify quotas for a user or on the share,
+depending on the QUOTA_SET_COMMAND parameter witch is described later
+.TP
+\fB-n\fR
+This option displays all QUOTA information in numeric 
+format.  The default is to convert SIDs to names and QUOTA limits 
+to a readable string format.  
+.TP
+\fB-t\fR
+Don't actually do anything, only validate the correctness of 
+the arguments.
+.TP
+\fB-v\fR
+Be verbose.
+.TP
+\fB-h|--help\fR
+Print a summary of command line options.
+.TP
+\fB-V\fR
+Prints the version number for 
+\fBsmbd\fR.
+.TP
+\fB-s \fR
+The file specified contains the 
+configuration details required by the server.  The 
+information in this file includes server-specific
+information such as what printcap file to use, as well 
+as descriptions of all the services that the server is 
+to provide. See \fIsmb.conf(5)\fR for more information.
+The default configuration file name is determined at 
+compile time.
+.TP
+\fB-d|--debug=debuglevel\fR
+\fIdebuglevel\fR is an integer 
+from 0 to 10.  The default value if this parameter is 
+not specified is zero.
+
+The higher this value, the more detail will be 
+logged to the log files about the activities of the 
+server. At level 0, only critical errors and serious 
+warnings will be logged. Level 1 is a reasonable level for
+day to day running - it generates a small amount of 
+information about operations carried out.
+
+Levels above 1 will generate considerable 
+amounts of log data, and should only be used when 
+investigating a problem. Levels above 3 are designed for 
+use only by developers and generate HUGE amounts of log
+data, most of which is extremely cryptic.
+
+Note that specifying this parameter here will 
+override the log
+level file.
+.TP
+\fB-l|--logfile=logbasename\fR
+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
+If specified, this parameter suppresses the normal
+password prompt from the client to the user. This is useful when
+accessing a service that does not require a password. 
+
+Unless a password is specified on the command line or
+this parameter is specified, the client will request a
+password.
+.TP
+\fB-k\fR
+Try to authenticate with kerberos. Only useful in
+an Active Directory environment.
+.TP
+\fB-A|--authfile=filename\fR
+This option allows
+you to specify a file from which to read the username and
+password used in the connection.  The format of the file is
+
+
+.nf
+username = 
+password = 
+domain   = 
+.fi
+
+Make certain that the permissions on the file restrict 
+access from unwanted users. 
+.TP
+\fB-U|--user=username[%password]\fR
+Sets the SMB username or username and password. 
+
+If %password is not specified, the user will be prompted. The
+client will first check the \fBUSER\fR environment variable, then the
+\fBLOGNAME\fR variable and if either exists, the
+string is uppercased. If these environmental variables are not
+found, the username GUEST is used. 
+
+A third option is to use a credentials file which
+contains the plaintext of the username and password.  This
+option is mainly provided for scripts where the admin does not
+wish to pass the credentials on the command line or via environment
+variables. If this method is used, make certain that the permissions
+on the file restrict access from unwanted users.  See the
+\fI-A\fR for more details. 
+
+Be cautious about including passwords in scripts. Also, on
+many systems the command line of a running process may be seen
+via the \fBps\fR command.  To be safe always allow
+\fBrpcclient\fR to prompt for a password and type
+it in directly. 
+.SH "QUOTA_SET_COMAND"
+.PP
+The format of an ACL is one or more ACL entries separated by 
+either commas or newlines.  An ACL entry is one of the following: 
+.PP
+for user setting quotas for the specified by -u or the current username:
+.PP
+\fB UQLIM:
+\fR
+.PP
+for setting the share quota defaults limits:
+.PP
+\fB FSQLIM:
+\fR
+.PP
+for changing the share quota settings:
+.PP
+\fB FSQFLAGS:QUOTA_ENABLED/DENY_DISK/LOG_SOFTLIMIT/LOG_HARD_LIMIT
+\fR
+.SH "EXIT STATUS"
+.PP
+The \fBsmbcquotas\fR program sets the exit status
+depending on the success or otherwise of the operations performed.
+The exit status may be one of the following values. 
+.PP
+If the operation succeeded, smbcquotas returns an exit
+status of 0.  If \fBsmbcquotas\fR couldn't connect to the specified server,
+or when there was an error getting or setting the quota(s), an exit status
+of 1 is returned.  If there was an error parsing any command line
+arguments, an exit status of 2 is returned. 
+.SH "VERSION"
+.PP
+This man page is correct for version 3.0 of the Samba suite.
+.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
+\fBsmbcacls\fR was written by Stefan Metzmacher.
diff --git a/docs/manpages/smbd.8 b/docs/manpages/smbd.8
index e5139967e8..855705f861 100644
--- a/docs/manpages/smbd.8
+++ b/docs/manpages/smbd.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBD" "8" "07 april 2003" "" ""
+.TH "SMBD" "8" "17 April 2003" "" ""
 
 .SH NAME
 smbd \- server to provide SMB/CIFS services to clients
diff --git a/docs/manpages/smbgroupedit.8 b/docs/manpages/smbgroupedit.8
index cb3ce954c9..c866fef9df 100644
--- a/docs/manpages/smbgroupedit.8
+++ b/docs/manpages/smbgroupedit.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBGROUPEDIT" "8" "07 april 2003" "" ""
+.TH "SMBGROUPEDIT" "8" "17 April 2003" "" ""
 
 .SH NAME
 smbgroupedit \- Query/set/change UNIX - Windows NT group mapping
diff --git a/docs/manpages/smbmnt.8 b/docs/manpages/smbmnt.8
index c81428e3d7..424193da8c 100644
--- a/docs/manpages/smbmnt.8
+++ b/docs/manpages/smbmnt.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBMNT" "8" "07 april 2003" "" ""
+.TH "SMBMNT" "8" "17 April 2003" "" ""
 
 .SH NAME
 smbmnt \- helper utility for mounting SMB filesystems
diff --git a/docs/manpages/smbmount.8 b/docs/manpages/smbmount.8
index 2f158c3074..306e580834 100644
--- a/docs/manpages/smbmount.8
+++ b/docs/manpages/smbmount.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBMOUNT" "8" "07 april 2003" "" ""
+.TH "SMBMOUNT" "8" "17 April 2003" "" ""
 
 .SH NAME
 smbmount \- mount an smbfs filesystem
diff --git a/docs/manpages/smbpasswd.5 b/docs/manpages/smbpasswd.5
index 9d1ee8e275..0d061ef1a8 100644
--- a/docs/manpages/smbpasswd.5
+++ b/docs/manpages/smbpasswd.5
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBPASSWD" "5" "07 april 2003" "" ""
+.TH "SMBPASSWD" "5" "17 April 2003" "" ""
 
 .SH NAME
 smbpasswd \- The Samba encrypted password file
diff --git a/docs/manpages/smbpasswd.8 b/docs/manpages/smbpasswd.8
index 500c3b37da..bb21a4668b 100644
--- a/docs/manpages/smbpasswd.8
+++ b/docs/manpages/smbpasswd.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBPASSWD" "8" "07 april 2003" "" ""
+.TH "SMBPASSWD" "8" "17 April 2003" "" ""
 
 .SH NAME
 smbpasswd \- change a user's SMB password
diff --git a/docs/manpages/smbsh.1 b/docs/manpages/smbsh.1
index fb7d7e2495..a10f8d709b 100644
--- a/docs/manpages/smbsh.1
+++ b/docs/manpages/smbsh.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBSH" "1" "07 april 2003" "" ""
+.TH "SMBSH" "1" "17 April 2003" "" ""
 
 .SH NAME
 smbsh \- Allows access to Windows NT filesystem  using UNIX commands
diff --git a/docs/manpages/smbspool.8 b/docs/manpages/smbspool.8
index 3932d696be..c5498ce513 100644
--- a/docs/manpages/smbspool.8
+++ b/docs/manpages/smbspool.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBSPOOL" "8" "07 april 2003" "" ""
+.TH "SMBSPOOL" "8" "17 April 2003" "" ""
 
 .SH NAME
 smbspool \- send a print file to an SMB printer
diff --git a/docs/manpages/smbstatus.1 b/docs/manpages/smbstatus.1
index a27efef629..13bfab4723 100644
--- a/docs/manpages/smbstatus.1
+++ b/docs/manpages/smbstatus.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBSTATUS" "1" "07 april 2003" "" ""
+.TH "SMBSTATUS" "1" "17 April 2003" "" ""
 
 .SH NAME
 smbstatus \- report on current Samba connections
diff --git a/docs/manpages/smbtar.1 b/docs/manpages/smbtar.1
index e270cc4b5f..a9e274dda3 100644
--- a/docs/manpages/smbtar.1
+++ b/docs/manpages/smbtar.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBTAR" "1" "07 april 2003" "" ""
+.TH "SMBTAR" "1" "17 April 2003" "" ""
 
 .SH NAME
 smbtar \- shell script for backing up SMB/CIFS shares  directly to UNIX tape drives
diff --git a/docs/manpages/smbtree.1 b/docs/manpages/smbtree.1
new file mode 100644
index 0000000000..e2f61207d9
--- /dev/null
+++ b/docs/manpages/smbtree.1
@@ -0,0 +1,144 @@
+.\" This manpage has been automatically generated by docbook2man 
+.\" from a DocBook document.  This tool can be found at:
+.\"  
+.\" Please send any bug reports, improvements, comments, patches, 
+.\" etc. to Steve Cheng .
+.TH "SMBTREE" "1" "17 April 2003" "" ""
+
+.SH NAME
+smbtree \- A text based smb network browser
+.SH SYNOPSIS
+
+\fBsmbtree\fR [ \fB-b\fR ] [ \fB-D\fR ] [ \fB-S\fR ]
+
+.SH "DESCRIPTION"
+.PP
+This tool is part of the \fBSamba\fR(7) suite.
+.PP
+\fBsmbtree\fR is a smb browser program 
+in text mode. It is similar to the "Network Neighborhood" found 
+on Windows computers. It prints a tree with all 
+the known domains, the servers in those domains and 
+the shares on the servers.
+.SH "OPTIONS"
+.TP
+\fB-b\fR
+Query network nodes by sending requests 
+as broadcasts instead of querying the (domain) master browser.
+.TP
+\fB-D\fR
+Only print a list of all 
+the domains known on broadcast or by the 
+master browser
+.TP
+\fB-S\fR
+Only print a list of 
+all the domains and servers responding on broadcast or 
+known by the master browser. 
+.TP
+\fB-V\fR
+Prints the version number for 
+\fBsmbd\fR.
+.TP
+\fB-s \fR
+The file specified contains the 
+configuration details required by the server.  The 
+information in this file includes server-specific
+information such as what printcap file to use, as well 
+as descriptions of all the services that the server is 
+to provide. See \fIsmb.conf(5)\fR for more information.
+The default configuration file name is determined at 
+compile time.
+.TP
+\fB-d|--debug=debuglevel\fR
+\fIdebuglevel\fR is an integer 
+from 0 to 10.  The default value if this parameter is 
+not specified is zero.
+
+The higher this value, the more detail will be 
+logged to the log files about the activities of the 
+server. At level 0, only critical errors and serious 
+warnings will be logged. Level 1 is a reasonable level for
+day to day running - it generates a small amount of 
+information about operations carried out.
+
+Levels above 1 will generate considerable 
+amounts of log data, and should only be used when 
+investigating a problem. Levels above 3 are designed for 
+use only by developers and generate HUGE amounts of log
+data, most of which is extremely cryptic.
+
+Note that specifying this parameter here will 
+override the log
+level file.
+.TP
+\fB-l|--logfile=logbasename\fR
+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
+If specified, this parameter suppresses the normal
+password prompt from the client to the user. This is useful when
+accessing a service that does not require a password. 
+
+Unless a password is specified on the command line or
+this parameter is specified, the client will request a
+password.
+.TP
+\fB-k\fR
+Try to authenticate with kerberos. Only useful in
+an Active Directory environment.
+.TP
+\fB-A|--authfile=filename\fR
+This option allows
+you to specify a file from which to read the username and
+password used in the connection.  The format of the file is
+
+
+.nf
+username = 
+password = 
+domain   = 
+.fi
+
+Make certain that the permissions on the file restrict 
+access from unwanted users. 
+.TP
+\fB-U|--user=username[%password]\fR
+Sets the SMB username or username and password. 
+
+If %password is not specified, the user will be prompted. The
+client will first check the \fBUSER\fR environment variable, then the
+\fBLOGNAME\fR variable and if either exists, the
+string is uppercased. If these environmental variables are not
+found, the username GUEST is used. 
+
+A third option is to use a credentials file which
+contains the plaintext of the username and password.  This
+option is mainly provided for scripts where the admin does not
+wish to pass the credentials on the command line or via environment
+variables. If this method is used, make certain that the permissions
+on the file restrict access from unwanted users.  See the
+\fI-A\fR for more details. 
+
+Be cautious about including passwords in scripts. Also, on
+many systems the command line of a running process may be seen
+via the \fBps\fR command.  To be safe always allow
+\fBrpcclient\fR to prompt for a password and type
+it in directly. 
+.TP
+\fB-h|--help\fR
+Print a summary of command line options.
+.SH "VERSION"
+.PP
+This man page is correct for version 3.0 of the Samba 
+suite.
+.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 smbtree man page was written by Jelmer Vernooij. 
diff --git a/docs/manpages/smbumount.8 b/docs/manpages/smbumount.8
index 9e8daa81be..118bb37d52 100644
--- a/docs/manpages/smbumount.8
+++ b/docs/manpages/smbumount.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBUMOUNT" "8" "07 april 2003" "" ""
+.TH "SMBUMOUNT" "8" "17 April 2003" "" ""
 
 .SH NAME
 smbumount \- smbfs umount for normal users
diff --git a/docs/manpages/swat.8 b/docs/manpages/swat.8
index b773bb8fa2..a1a313c6ea 100644
--- a/docs/manpages/swat.8
+++ b/docs/manpages/swat.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SWAT" "8" "07 april 2003" "" ""
+.TH "SWAT" "8" "17 April 2003" "" ""
 
 .SH NAME
 swat \- Samba Web Administration Tool
diff --git a/docs/manpages/testparm.1 b/docs/manpages/testparm.1
index 7646fedde7..43412e12e3 100644
--- a/docs/manpages/testparm.1
+++ b/docs/manpages/testparm.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "TESTPARM" "1" "07 april 2003" "" ""
+.TH "TESTPARM" "1" "17 April 2003" "" ""
 
 .SH NAME
 testparm \- check an smb.conf configuration file for  internal correctness
diff --git a/docs/manpages/testprns.1 b/docs/manpages/testprns.1
index dccd997fc5..3d09445608 100644
--- a/docs/manpages/testprns.1
+++ b/docs/manpages/testprns.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "TESTPRNS" "1" "07 april 2003" "" ""
+.TH "TESTPRNS" "1" "17 April 2003" "" ""
 
 .SH NAME
 testprns \- check printer name for validity with smbd
diff --git a/docs/manpages/vfstest.1 b/docs/manpages/vfstest.1
index bb378142dd..5fcbd46a10 100644
--- a/docs/manpages/vfstest.1
+++ b/docs/manpages/vfstest.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "VFSTEST" "1" "07 april 2003" "" ""
+.TH "VFSTEST" "1" "17 April 2003" "" ""
 
 .SH NAME
 vfstest \- tool for testing samba VFS modules
diff --git a/docs/manpages/wbinfo.1 b/docs/manpages/wbinfo.1
index 9e11e47133..a23b08ab65 100644
--- a/docs/manpages/wbinfo.1
+++ b/docs/manpages/wbinfo.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "WBINFO" "1" "07 april 2003" "" ""
+.TH "WBINFO" "1" "17 April 2003" "" ""
 
 .SH NAME
 wbinfo \- Query information from winbind daemon
diff --git a/docs/manpages/winbindd.8 b/docs/manpages/winbindd.8
index a1e39fa172..7341746cde 100644
--- a/docs/manpages/winbindd.8
+++ b/docs/manpages/winbindd.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "WINBINDD" "8" "07 april 2003" "" ""
+.TH "WINBINDD" "8" "17 April 2003" "" ""
 
 .SH NAME
 winbindd \- Name Service Switch daemon for resolving names  from NT servers
-- 
cgit 


From a4c20fc76b3fd2f1f7f0322b5b6d4520d6a95ebe Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij 
Date: Thu, 17 Apr 2003 19:56:52 +0000
Subject: Add notes on Japanese charsets from Monyo (This used to be commit
 571e14bd07148d95e3e83167e83362bec0502d55)

---
 docs/docbook/projdoc/unicode.sgml | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/docs/docbook/projdoc/unicode.sgml b/docs/docbook/projdoc/unicode.sgml
index 2f794aadc2..42d2e1d50f 100644
--- a/docs/docbook/projdoc/unicode.sgml
+++ b/docs/docbook/projdoc/unicode.sgml
@@ -1,6 +1,12 @@
 
 
 	&author.jelmer;
+	
+		TAKAHASHIMotonobu
+		
+		
    monyo@home.monyo.com
    
+		    
+	    
 	25 March 2003
     
 
@@ -99,4 +105,24 @@ filenames from CP850 to the iso8859-15 charset.
 
 
 
+
+
+Japanese charsets
+
+Samba doesn't work correctly with Japanese charsets yet. Here are points of attention when setting it up:
+
+
+You should set mangling method = hash
+There are various iconv() implementations around and not all of 
+them work equally well. glibc2's iconv() has a critical problem in CP932. 
+libiconv-1.8 works with CP932 but still has some problems and does not 
+work with EUC-JP. 
+You should set dos charset = CP932, not Shift_JIS, SJIS...
+Currently only unix charset = CP932 will work (but still has some problems...) because of iconv() issues. unix charset = EUC-JP doesn't work well because of iconv() issues.
+Currently Samba 3.0 does not support unix charset = UTF8-MAC/CAP/HEX/JIS*
+
+
+More information (in Japanese) is available at: http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html.
+
+
     
-- 
cgit 


From cdb197135f504683112826d26f360d79a13ae346 Mon Sep 17 00:00:00 2001
From: Volker Lendecke 
Date: Fri, 18 Apr 2003 08:36:12 +0000
Subject: Survive a samdump with an alias that has no description

Volker
(This used to be commit 408a94b64d4d799f256c11a2009e161b27553cbb)
---
 source3/rpc_parse/parse_net.c | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/source3/rpc_parse/parse_net.c b/source3/rpc_parse/parse_net.c
index a660084250..259ca7fdc1 100644
--- a/source3/rpc_parse/parse_net.c
+++ b/source3/rpc_parse/parse_net.c
@@ -2277,9 +2277,12 @@ static BOOL net_io_sam_alias_info(const char *desc, SAM_ALIAS_INFO * info,
 	if (!smb_io_buffer4("buf_sec_desc", &info->buf_sec_desc,
                             info->hdr_sec_desc.buffer, ps, depth))
                 return False;
-	if (!smb_io_unistr2("uni_als_desc", &info->uni_als_desc,
-                            info->hdr_als_name.buffer, ps, depth))
-                return False;
+
+	if (info->hdr_als_desc.buffer != 0) {
+		if (!smb_io_unistr2("uni_als_desc", &info->uni_als_desc,
+				    info->hdr_als_name.buffer, ps, depth))
+			return False;
+	}
 
 	return True;
 }
-- 
cgit 


From 78f039f04347bf1fe4fa7b8f5ca56b444fc2d539 Mon Sep 17 00:00:00 2001
From: Gerald Carter 
Date: Fri, 18 Apr 2003 14:56:29 +0000
Subject: fix byte ordering when using CIDR notation in hosts allow/deny;
 spotted by Eloy Paris (This used to be commit
 c2580e15d6e7ad7c8dde81753e35670fa52636ff)

---
 source3/lib/access.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/source3/lib/access.c b/source3/lib/access.c
index 09676dbd58..9d07893c2f 100644
--- a/source3/lib/access.c
+++ b/source3/lib/access.c
@@ -40,6 +40,10 @@ static BOOL masked_match(const char *tok, const char *slash, const char *s)
 		DEBUG(0,("access: bad net/mask access control: %s\n", tok));
 		return (False);
 	}
+	
+	/* convert to network byte order */
+	mask = htonl(mask);
+	
 	return ((addr & mask) == net);
 }
 
-- 
cgit 


From db233b6970da2a87bb2c137cf45e99b2f208967f Mon Sep 17 00:00:00 2001
From: Richard Sharpe 
Date: Fri, 18 Apr 2003 19:32:58 +0000
Subject: More minor edits to add features ... (This used to be commit
 882799ca113566b91e42c3c852a9c1986552daaa)

---
 source3/utils/editreg.c | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/source3/utils/editreg.c b/source3/utils/editreg.c
index ad4417921c..1b7b3d587d 100644
--- a/source3/utils/editreg.c
+++ b/source3/utils/editreg.c
@@ -939,6 +939,24 @@ int nt_delete_reg_key(REG_KEY *key, int delete_name)
   return 1;
 }
 
+/*
+ * Add a value to the key specified ...
+ */
+REG_KEY *nt_add_reg_value(REG_KEY *key, char *name, int type, char *value)
+{
+
+  return NULL;
+}
+
+/*
+ * Delete a value. Should perhaps return the value ...
+ */
+REG_KEY *nt_delete_reg_valye(REG_KEY *key, char *name)
+{
+
+  return NULL;
+}
+
 /* 
  * Add a key to the tree ... We walk down the components matching until
  * we don't find any. There must be a match on the first component ...
@@ -2200,6 +2218,9 @@ struct cmd_line *get_cmd_line(int fd)
  *
  * If it parsed OK, return the  as a string, and the
  * value type and value-string in parameters.
+ *
+ * The value name can be empty. There can only be one empty name in 
+ * a list of values. A value of - removes the value entirely.  
  */
 
 char *dup_str(char *s, int len) 
-- 
cgit 


From 7d1ea0987d6d756fb3ceaf14c87676b3ae8d4d9b Mon Sep 17 00:00:00 2001
From: Gerald Carter 
Date: Fri, 18 Apr 2003 22:19:51 +0000
Subject: uidPool and gidPool don't use cn anymore (but we don't use thsi
 anyways) (This used to be commit 4c92994dfd231acb09411f89fd67a21a40400de0)

---
 examples/LDAP/samba.schema | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/examples/LDAP/samba.schema b/examples/LDAP/samba.schema
index a4435564ec..b95fbeb8ff 100644
--- a/examples/LDAP/samba.schema
+++ b/examples/LDAP/samba.schema
@@ -167,11 +167,11 @@ objectclass ( 1.3.6.1.4.1.7165.2.2.4 NAME 'sambaGroupMapping' SUP top AUXILIARY
 ##
 ## Used for Winbind experimentation
 ##
-objectclass ( 1.3.6.1.4.1.7165.1.2.2.3 NAME 'uidPool' SUP top AUXILIARY
-	DESC 'Pool for allocating UNIX uids'
-	MUST ( uidNumber $ cn ) )
+#objectclass ( 1.3.6.1.4.1.7165.1.2.2.3 NAME 'uidPool' SUP top AUXILIARY
+#	DESC 'Pool for allocating UNIX uids'
+#	MUST ( uidNumber ) )
 
-objectclass ( 1.3.6.1.4.1.7165.1.2.2.4 NAME 'gidPool' SUP top AUXILIARY
-	DESC 'Pool for allocating UNIX gids'
-	MUST ( gidNumber $ cn ) )
+#objectclass ( 1.3.6.1.4.1.7165.1.2.2.4 NAME 'gidPool' SUP top AUXILIARY
+#	DESC 'Pool for allocating UNIX gids'
+#	MUST ( gidNumber ) )
 
-- 
cgit 


From 0676a942f933685184626db24b3caca57d910310 Mon Sep 17 00:00:00 2001
From: Gerald Carter 
Date: Sat, 19 Apr 2003 06:04:17 +0000
Subject: [merge from SAMBA_3_0]

Merging smbgroupedit into 'net groupmap'.  Not entirely done.
Need to check on where the privilege code is sitting
and update the docs.

Examples:

root# bin/net help groupmap
net groupmap add
  Create a new group mapping
net groupmap modify
  Update a group mapping
net groupmap delete
  Remove a group mapping
net groupmap list
  List current group map

# bin/net groupmap add
Usage: net groupmap add rid= name= type= [comment=]

# bin/net groupmap delete
Usage: net groupmap delete name=

# bin/net groupmap modify
Usage: net groupmap modify name= [comment=] [type=]
(This used to be commit 0fd28bc3a803ca1ec3dcd8cc6236d4ecc3134584)
---
 source3/Makefile.in          |   4 +-
 source3/utils/net.c          |  21 +++
 source3/utils/net_groupmap.c | 411 +++++++++++++++++++++++++++++++++++++++++++
 source3/utils/net_help.c     |  21 +++
 4 files changed, 455 insertions(+), 2 deletions(-)
 create mode 100644 source3/utils/net_groupmap.c

diff --git a/source3/Makefile.in b/source3/Makefile.in
index 4e43882a2a..4ad76e4bbb 100644
--- a/source3/Makefile.in
+++ b/source3/Makefile.in
@@ -126,7 +126,7 @@ BIN_PROGS1 = bin/smbclient@EXEEXT@ bin/net@EXEEXT@ bin/smbspool@EXEEXT@ \
 BIN_PROGS2 = bin/smbcontrol@EXEEXT@ bin/smbtree@EXEEXT@ bin/tdbbackup@EXEEXT@ \
 	bin/nmblookup@EXEEXT@ bin/pdbedit@EXEEXT@
 BIN_PROGS3 = bin/smbpasswd@EXEEXT@ bin/rpcclient@EXEEXT@ bin/smbcacls@EXEEXT@ \
-	bin/profiles@EXEEXT@ bin/smbgroupedit@EXEEXT@ bin/ntlm_auth@EXEEXT@ \
+	bin/profiles@EXEEXT@ bin/ntlm_auth@EXEEXT@ \
 	bin/editreg@EXEEXT@ bin/smbcquotas@EXEEXT@
 
 TORTURE_PROGS = bin/smbtorture@EXEEXT@ bin/msgtest@EXEEXT@ \
@@ -483,7 +483,7 @@ CLIENT_OBJ = $(CLIENT_OBJ1) $(PARAM_OBJ) $(LIBSMB_OBJ) $(UBIQX_OBJ) \
 NET_OBJ1 = utils/net.o utils/net_ads.o utils/net_ads_cldap.o utils/net_help.o \
 	   utils/net_rap.o utils/net_rpc.o utils/net_rpc_samsync.o \
 	   utils/net_rpc_join.o utils/net_time.o utils/net_lookup.o \
-	   utils/net_cache.o
+	   utils/net_cache.o utils/net_groupmap.o
 
 NET_OBJ = $(NET_OBJ1) $(PARAM_OBJ) $(SECRETS_OBJ) $(LIBSMB_OBJ) \
 	  $(RPC_PARSE_OBJ) $(PASSDB_OBJ) $(GROUPDB_OBJ) \
diff --git a/source3/utils/net.c b/source3/utils/net.c
index a2ce1f5f1a..b404bac595 100644
--- a/source3/utils/net.c
+++ b/source3/utils/net.c
@@ -348,6 +348,26 @@ static int net_file(int argc, const char **argv)
 	return net_rap_file(argc, argv);
 }
 
+/***********************************************************
+ migrated functionality from smbgroupedit
+ **********************************************************/
+static int net_groupmap(int argc, const char **argv)
+{
+	if ( 0 == argc )
+		return net_help_groupmap( argc, argv );
+
+	if ( !StrCaseCmp( argv[0], "add" ) )
+		return net_groupmap_add(argc-1, argv+1);
+	else if ( !StrCaseCmp( argv[0], "modify" ) )
+		return net_groupmap_modify(argc-1, argv+1);
+	else if ( !StrCaseCmp( argv[0], "delete" ) )
+		return net_groupmap_delete(argc-1, argv+1);
+	else if ( !StrCaseCmp( argv[0], "list" ) )
+		return net_groupmap_list(argc-1, argv+1);
+	
+	return net_help_groupmap( argc, argv );
+}
+
 /*
  Retrieve our local SID or the SID for the specified name
  */
@@ -509,6 +529,7 @@ static struct functable net_func[] = {
 	{"PRINTQ", net_rap_printq},
 	{"USER", net_user},
 	{"GROUP", net_group},
+	{"GROUPMAP", net_groupmap},
 	{"VALIDATE", net_rap_validate},
 	{"GROUPMEMBER", net_rap_groupmember},
 	{"ADMIN", net_rap_admin},
diff --git a/source3/utils/net_groupmap.c b/source3/utils/net_groupmap.c
new file mode 100644
index 0000000000..e248cd84f9
--- /dev/null
+++ b/source3/utils/net_groupmap.c
@@ -0,0 +1,411 @@
+/*
+ *  Unix SMB/CIFS implementation.
+ *  RPC Pipe client / server routines
+ *  Copyright (C) Andrew Tridgell              1992-2000,
+ *  Copyright (C) Jean Franois Micouleau      1998-2001.
+ *  Copyright (C) Gerald Carter                2003.
+ *
+ *  This program is free software; you can redistribute it and/or modify
+ *  it under the terms of the GNU General Public License as published by
+ *  the Free Software Foundation; either version 2 of the License, or
+ *  (at your option) any later version.
+ *
+ *  This program is distributed in the hope that it will be useful,
+ *  but WITHOUT ANY WARRANTY; without even the implied warranty of
+ *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ *  GNU General Public License for more details.
+ *
+ *  You should have received a copy of the GNU General Public License
+ *  along with this program; if not, write to the Free Software
+ *  Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+ */
+
+
+#include "includes.h"
+#include "../utils/net.h"
+
+
+/*********************************************************
+ utility function to parse an integer parameter from 
+ "parameter = value"
+**********************************************************/
+static uint32 get_int_param( const char* param )
+{
+	char *p;
+	
+	p = strchr( param, '=' );
+	if ( !p )
+		return 0;
+		
+	return atoi(p+1);
+}
+
+/*********************************************************
+ utility function to parse an integer parameter from 
+ "parameter = value"
+**********************************************************/
+static char* get_string_param( const char* param )
+{
+	char *p;
+	
+	p = strchr( param, '=' );
+	if ( !p )
+		return NULL;
+		
+	return (p+1);
+}
+
+/*********************************************************
+ Figure out if the input was an NT group or a SID string.
+ Return the SID.
+**********************************************************/
+static BOOL get_sid_from_input(DOM_SID *sid, char *input)
+{
+	GROUP_MAP map;
+
+	if (StrnCaseCmp( input, "S-", 2)) {
+		/* Perhaps its the NT group name? */
+		if (!pdb_getgrnam(&map, input, MAPPING_WITHOUT_PRIV)) {
+			printf("NT Group %s doesn't exist in mapping DB\n", input);
+			return False;
+		} else {
+			*sid = map.sid;
+		}
+	} else {
+		if (!string_to_sid(sid, input)) {
+			printf("converting sid %s from a string failed!\n", input);
+			return False;
+		}
+	}
+	return True;
+}
+
+/*********************************************************
+ Dump a GROUP_MAP entry to stdout (long or short listing)
+**********************************************************/
+
+static void print_map_entry ( GROUP_MAP map, BOOL long_list )
+{
+	fstring string_sid;
+	fstring group_type;
+	fstring priv_text;
+	
+	decode_sid_name_use(group_type, map.sid_name_use);
+	sid_to_string(string_sid, &map.sid);
+	convert_priv_to_text(&(map.priv_set), priv_text);
+		
+	if (!long_list)
+		d_printf("%s (%s) -> %s\n", map.nt_name, string_sid, gidtoname(map.gid));
+	else {
+		d_printf("%s\n", map.nt_name);
+		d_printf("\tSID       : %s\n", string_sid);
+		d_printf("\tUnix group: %s\n", gidtoname(map.gid));
+		d_printf("\tGroup type: %s\n", group_type);
+		d_printf("\tComment   : %s\n", map.comment);
+		d_printf("\tPrivilege : %s\n\n", priv_text);
+	}
+
+}
+/*********************************************************
+ List the groups.
+**********************************************************/
+int net_groupmap_list(int argc, const char **argv)
+{
+	int entries;
+	BOOL long_list = False;
+	int i;
+	fstring ntgroup = "";
+	
+	/* get the options */
+	for ( i=0; i name= type= [comment=]\n");
+		return -1;
+	}
+	
+	sid_copy(&sid, get_global_sam_sid());
+	sid_append_rid(&sid, rid);
+	sid_to_string(string_sid, &sid);
+
+	if (ntcomment[0])
+		fstrcpy(ntcomment, "Local Unix group");
+		
+	if ( !(gid = nametogid(ntgroup)) ) {
+		d_printf("Can't lookup UNIX group %s\n", ntgroup);
+		return -1;
+	}
+	
+	init_privilege(&se_priv);
+#if 0
+	if (privilege!=NULL)
+		convert_priv_from_text(&se_priv, privilege);
+#endif
+
+	if (!add_initial_entry(gid, string_sid, sid_type, ntgroup,
+			      ntcomment, se_priv, PR_ACCESS_FROM_NETWORK) ) {
+		d_printf("adding entry for group %s failed!\n", ntgroup);
+		return -1;
+	}
+
+	free_privilege(&se_priv);
+		
+	d_printf("Successully added group %s to the mapping db\n", ntgroup);
+	return 0;
+}
+
+int net_groupmap_modify(int argc, const char **argv)
+{
+	DOM_SID sid;
+	GROUP_MAP map;
+	fstring ntcomment = "";
+	fstring type = "";
+	fstring ntgroup = "";
+	enum SID_NAME_USE sid_type = SID_NAME_UNKNOWN;
+	int i;
+
+	/* get the options */
+	for ( i=0; i [comment=] [type=\n");
+		return -1;
+	}
+	
+	if (!get_sid_from_input(&sid, ntgroup)) {
+		return -1;
+	}
+
+	/* Get the current mapping from the database */
+	if(!pdb_getgrsid(&map, sid, MAPPING_WITH_PRIV)) {
+		d_printf("Failure to local group SID in the database\n");
+		return -1;
+	}
+	
+	/*
+	 * Allow changing of group type only between domain and local
+	 * We disallow changing Builtin groups !!! (SID problem)
+	 */ 
+	if (sid_type==SID_NAME_ALIAS 
+	    || sid_type==SID_NAME_DOM_GRP 
+	    || sid_type==SID_NAME_UNKNOWN) 
+	{
+		if (map.sid_name_use==SID_NAME_ALIAS 
+		    || map.sid_name_use==SID_NAME_DOM_GRP
+		    || map.sid_name_use==SID_NAME_UNKNOWN) 
+		{
+			map.sid_name_use=sid_type;
+		} else {
+			printf("cannot change group type to builtin\n");
+		};
+	} else {
+		printf("cannot change group type from builtin\n");
+	}
+
+	/* Change comment if new one */
+	if ( ntcomment[0] )
+		fstrcpy( map.comment, ntcomment );
+
+#if 0
+	/* Change the privilege if new one */
+	if (privilege!=NULL)
+		convert_priv_from_text(&map.priv_set, privilege);
+#endif
+
+	if ( !pdb_update_group_mapping_entry(&map) ) {
+		d_printf("Could not update group database\n");
+		free_privilege(&map.priv_set);
+		return -1;
+	}
+	
+	free_privilege(&map.priv_set);
+	
+	d_printf("Updated mapping entry for %s\n", ntgroup);
+
+	return 0;
+}
+
+int net_groupmap_delete(int argc, const char **argv)
+{
+	DOM_SID sid;
+	fstring ntgroup = "";
+	int i;
+
+	/* get the options */
+	for ( i=0; i\n");
+		return -1;
+	}
+	
+	if ( !get_sid_from_input(&sid, ntgroup) ) {
+		d_printf("Unable to resolve group %s to a SID\n", ntgroup);
+		return -1;
+	}
+
+	if ( !pdb_delete_group_mapping_entry(sid) ) {
+		printf("Failed to removing group %s from the mapping db!\n", ntgroup);
+		return -1;
+	}
+
+	d_printf("Sucessfully removed %s from the mapping db\n", ntgroup);
+
+	return 0;
+}
+
diff --git a/source3/utils/net_help.c b/source3/utils/net_help.c
index 07409aec22..f24367f246 100644
--- a/source3/utils/net_help.c
+++ b/source3/utils/net_help.c
@@ -99,6 +99,25 @@ int net_help_group(int argc, const char **argv)
 	return -1;
 }
 
+int net_help_groupmap(int argc, const char **argv)
+{
+	if (getuid() != 0) {
+		d_printf("You must be root to edit group mappings.\nExiting...\n");
+		return -1;
+	}
+	
+	d_printf("net groupmap add"\
+		"\n  Create a new group mapping\n");
+	d_printf("net groupmap modify"\
+		"\n  Update a group mapping\n");
+	d_printf("net groupmap delete"\
+		"\n  Remove a group mapping\n");
+	d_printf("net groupmap list"\
+		"\n  List current group map\n");
+	
+	return -1;
+}
+
 
 int net_help_join(int argc, const char **argv)
 {
@@ -152,6 +171,7 @@ static int net_usage(int argc, const char **argv)
 		 "  net lookup\t\tto lookup host name or ip address\n"\
 		 "  net user\t\tto manage users\n"\
 		 "  net group\t\tto manage groups\n"\
+		 "  net groupmap\t\tto manage group mappings\n"\
 		 "  net join\t\tto join a domain\n"\
 		 "  net cache\t\tto operate on cache tdb file\n"\
 		 "  net getlocalsid [NAME]\tto get the SID for local name\n"\
@@ -184,6 +204,7 @@ int net_help(int argc, const char **argv)
 		{"PRINTQ", net_rap_printq_usage},
 		{"USER", net_help_user},
 		{"GROUP", net_help_group},
+		{"GROUPMAP", net_help_groupmap},
 		{"JOIN", net_help_join},
 		{"VALIDATE", net_rap_validate_usage},
 		{"GROUPMEMBER", net_rap_groupmember_usage},
-- 
cgit 


From ee88b8214e8ac65a0e60aca244486db78c950ece Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij 
Date: Sat, 19 Apr 2003 14:59:58 +0000
Subject: Regenerate docs (This used to be commit
 4f1865f7c234f3f4a7f5dba19db4a5d139db5a48)

---
 docs/Samba-Developers-Guide.pdf              |    4 +-
 docs/Samba-HOWTO-Collection.pdf              | 8493 +++++++++++++-------------
 docs/htmldocs/Samba-HOWTO-Collection.html    | 1037 ++--
 docs/htmldocs/ads.html                       |   14 +-
 docs/htmldocs/advancednetworkmanagement.html |   18 +-
 docs/htmldocs/browsing-quick.html            |   36 +-
 docs/htmldocs/bugreport.html                 |   24 +-
 docs/htmldocs/compiling.html                 |   50 +-
 docs/htmldocs/cups-printing.html             |   52 +-
 docs/htmldocs/diagnosis.html                 |   16 +-
 docs/htmldocs/domain-member.html             |    8 +-
 docs/htmldocs/improved-browsing.html         |   42 +-
 docs/htmldocs/install.html                   |   42 +-
 docs/htmldocs/integrate-ms-networks.html     |   44 +-
 docs/htmldocs/interdomaintrusts.html         |   28 +-
 docs/htmldocs/msdfs.html                     |    4 +-
 docs/htmldocs/nt4migration.html              |   16 +-
 docs/htmldocs/optional.html                  |    2 +-
 docs/htmldocs/other-clients.html             |   60 +-
 docs/htmldocs/pam.html                       |   12 +-
 docs/htmldocs/passdb.html                    |  100 +-
 docs/htmldocs/policymgmt.html                |   36 +-
 docs/htmldocs/portability.html               |   26 +-
 docs/htmldocs/printing.html                  |   88 +-
 docs/htmldocs/problems.html                  |   20 +-
 docs/htmldocs/profilemgmt.html               |   86 +-
 docs/htmldocs/samba-bdc.html                 |   36 +-
 docs/htmldocs/samba-howto-collection.html    |  319 +-
 docs/htmldocs/samba-pdc.html                 |   58 +-
 docs/htmldocs/securing-samba.html            |   24 +-
 docs/htmldocs/securitylevels.html            |   18 +-
 docs/htmldocs/servertype.html                |   14 +-
 docs/htmldocs/speed.html                     |   40 +-
 docs/htmldocs/swat.html                      |   16 +-
 docs/htmldocs/type.html                      |    2 +-
 docs/htmldocs/unicode.html                   |   81 +-
 docs/htmldocs/unix-permissions.html          |   36 +-
 docs/htmldocs/vfs.html                       |   36 +-
 docs/htmldocs/winbind.html                   |  104 +-
 docs/manpages/editreg.1                      |    2 +-
 docs/manpages/findsmb.1                      |    2 +-
 docs/manpages/lmhosts.5                      |    2 +-
 docs/manpages/net.8                          |    2 +-
 docs/manpages/nmbd.8                         |    2 +-
 docs/manpages/nmblookup.1                    |    2 +-
 docs/manpages/ntlm_auth.1                    |    2 +-
 docs/manpages/pdbedit.8                      |    2 +-
 docs/manpages/profiles.1                     |    2 +-
 docs/manpages/rpcclient.1                    |    2 +-
 docs/manpages/samba.7                        |    2 +-
 docs/manpages/smb.conf.5                     |    2 +-
 docs/manpages/smbcacls.1                     |    2 +-
 docs/manpages/smbclient.1                    |    2 +-
 docs/manpages/smbcontrol.1                   |    2 +-
 docs/manpages/smbcquotas.1                   |    2 +-
 docs/manpages/smbd.8                         |    2 +-
 docs/manpages/smbgroupedit.8                 |    2 +-
 docs/manpages/smbmnt.8                       |    2 +-
 docs/manpages/smbmount.8                     |    2 +-
 docs/manpages/smbpasswd.5                    |    2 +-
 docs/manpages/smbpasswd.8                    |    2 +-
 docs/manpages/smbsh.1                        |    2 +-
 docs/manpages/smbspool.8                     |    2 +-
 docs/manpages/smbstatus.1                    |    2 +-
 docs/manpages/smbtar.1                       |    2 +-
 docs/manpages/smbtree.1                      |    2 +-
 docs/manpages/smbumount.8                    |    2 +-
 docs/manpages/swat.8                         |    2 +-
 docs/manpages/testparm.1                     |    2 +-
 docs/manpages/testprns.1                     |    2 +-
 docs/manpages/vfstest.1                      |    2 +-
 docs/manpages/wbinfo.1                       |    2 +-
 docs/manpages/winbindd.8                     |    2 +-
 73 files changed, 5691 insertions(+), 5519 deletions(-)

diff --git a/docs/Samba-Developers-Guide.pdf b/docs/Samba-Developers-Guide.pdf
index bdf1740d06..ad043bf0ff 100644
--- a/docs/Samba-Developers-Guide.pdf
+++ b/docs/Samba-Developers-Guide.pdf
@@ -1,6 +1,6 @@
 %PDF-1.3
 %
-1 0 obj<>endobj
+1 0 obj<>endobj
 2 0 obj<>endobj
 3 0 obj<>endobj
 4 0 obj<>endobj
@@ -2728,7 +2728,7 @@ xref
 0000186776 00000 n 
 0000186871 00000 n 
 trailer
-<]>>
+<]>>
 startxref
 187413
 %%EOF
diff --git a/docs/Samba-HOWTO-Collection.pdf b/docs/Samba-HOWTO-Collection.pdf
index d06d23377a..a412abec6f 100644
--- a/docs/Samba-HOWTO-Collection.pdf
+++ b/docs/Samba-HOWTO-Collection.pdf
@@ -1,6 +1,6 @@
 %PDF-1.3
 %
-1 0 obj<>endobj
+1 0 obj<>endobj
 2 0 obj<>endobj
 3 0 obj<>endobj
 4 0 obj<>endobj
@@ -20,48 +20,48 @@ endobj
 16 0 obj<]/Interpolate true/Filter/FlateDecode/Width 24/Height 24/BitsPerComponent 8/Length 223       >>stream
 xUQ058@4wo%wR+8C+N"]ׂ*W
,D1|Ši"%~0)܁1lN!31T4HԆ<<~Z>yn.H>LKb؎џ'4Y}-?f&tA{27L}On4KI"	PBhïG]z$>.mcoendstream
 endobj
-17 0 obj<>endobj
-18 0 obj<>endobj
-19 0 obj<>endobj
-20 0 obj<>endobj
-21 0 obj<>endobj
-22 0 obj<>endobj
-23 0 obj<>endobj
-24 0 obj<>endobj
-25 0 obj<>endobj
-26 0 obj<>endobj
-27 0 obj<>endobj
-28 0 obj<>endobj
-29 0 obj<>endobj
-30 0 obj<>endobj
-31 0 obj<>endobj
-32 0 obj<>endobj
-33 0 obj<>endobj
-34 0 obj<>endobj
-35 0 obj<>endobj
-36 0 obj<>endobj
-37 0 obj<>endobj
-38 0 obj<>endobj
-39 0 obj<>endobj
-40 0 obj<>endobj
-41 0 obj<>endobj
-42 0 obj<>endobj
-43 0 obj<>endobj
-44 0 obj<>endobj
-45 0 obj<>endobj
-46 0 obj<>endobj
-47 0 obj<>endobj
-48 0 obj<>endobj
-49 0 obj<>endobj
-50 0 obj<>endobj
-51 0 obj<>endobj
-52 0 obj<>endobj
-53 0 obj<>endobj
-54 0 obj<>endobj
-55 0 obj<>endobj
-56 0 obj<>endobj
-57 0 obj<>endobj
-58 0 obj<>endobj
+17 0 obj<>endobj
+18 0 obj<>endobj
+19 0 obj<>endobj
+20 0 obj<>endobj
+21 0 obj<>endobj
+22 0 obj<>endobj
+23 0 obj<>endobj
+24 0 obj<>endobj
+25 0 obj<>endobj
+26 0 obj<>endobj
+27 0 obj<>endobj
+28 0 obj<>endobj
+29 0 obj<>endobj
+30 0 obj<>endobj
+31 0 obj<>endobj
+32 0 obj<>endobj
+33 0 obj<>endobj
+34 0 obj<>endobj
+35 0 obj<>endobj
+36 0 obj<>endobj
+37 0 obj<>endobj
+38 0 obj<>endobj
+39 0 obj<>endobj
+40 0 obj<>endobj
+41 0 obj<>endobj
+42 0 obj<>endobj
+43 0 obj<>endobj
+44 0 obj<>endobj
+45 0 obj<>endobj
+46 0 obj<>endobj
+47 0 obj<>endobj
+48 0 obj<>endobj
+49 0 obj<>endobj
+50 0 obj<>endobj
+51 0 obj<>endobj
+52 0 obj<>endobj
+53 0 obj<>endobj
+54 0 obj<>endobj
+55 0 obj<>endobj
+56 0 obj<>endobj
+57 0 obj<>endobj
+58 0 obj<>endobj
 59 0 obj[17 0 R
 18 0 R
 19 0 R
@@ -104,49 +104,49 @@ endobj
 56 0 R
 57 0 R
 58 0 R]endobj
-60 0 obj<>endobj
-61 0 obj<>endobj
-62 0 obj<>endobj
-63 0 obj<>endobj
-64 0 obj<>endobj
-65 0 obj<>endobj
-66 0 obj<>endobj
-67 0 obj<>endobj
-68 0 obj<>endobj
-69 0 obj<>endobj
-70 0 obj<>endobj
-71 0 obj<>endobj
-72 0 obj<>endobj
-73 0 obj<>endobj
-74 0 obj<>endobj
-75 0 obj<>endobj
-76 0 obj<>endobj
-77 0 obj<>endobj
-78 0 obj<>endobj
-79 0 obj<>endobj
-80 0 obj<>endobj
-81 0 obj<>endobj
-82 0 obj<>endobj
-83 0 obj<>endobj
-84 0 obj<>endobj
-85 0 obj<>endobj
-86 0 obj<>endobj
-87 0 obj<>endobj
-88 0 obj<>endobj
-89 0 obj<>endobj
-90 0 obj<>endobj
-91 0 obj<>endobj
-92 0 obj<>endobj
-93 0 obj<>endobj
-94 0 obj<>endobj
-95 0 obj<>endobj
-96 0 obj<>endobj
-97 0 obj<>endobj
-98 0 obj<>endobj
-99 0 obj<>endobj
-100 0 obj<>endobj
-101 0 obj<>endobj
-102 0 obj<>endobj
+60 0 obj<>endobj
+61 0 obj<>endobj
+62 0 obj<>endobj
+63 0 obj<>endobj
+64 0 obj<>endobj
+65 0 obj<>endobj
+66 0 obj<>endobj
+67 0 obj<>endobj
+68 0 obj<>endobj
+69 0 obj<>endobj
+70 0 obj<>endobj
+71 0 obj<>endobj
+72 0 obj<>endobj
+73 0 obj<>endobj
+74 0 obj<>endobj
+75 0 obj<>endobj
+76 0 obj<>endobj
+77 0 obj<>endobj
+78 0 obj<>endobj
+79 0 obj<>endobj
+80 0 obj<>endobj
+81 0 obj<>endobj
+82 0 obj<>endobj
+83 0 obj<>endobj
+84 0 obj<>endobj
+85 0 obj<>endobj
+86 0 obj<>endobj
+87 0 obj<>endobj
+88 0 obj<>endobj
+89 0 obj<>endobj
+90 0 obj<>endobj
+91 0 obj<>endobj
+92 0 obj<>endobj
+93 0 obj<>endobj
+94 0 obj<>endobj
+95 0 obj<>endobj
+96 0 obj<>endobj
+97 0 obj<>endobj
+98 0 obj<>endobj
+99 0 obj<>endobj
+100 0 obj<>endobj
+101 0 obj<>endobj
+102 0 obj<>endobj
 103 0 obj[60 0 R
 61 0 R
 62 0 R
@@ -190,48 +190,48 @@ endobj
 100 0 R
 101 0 R
 102 0 R]endobj
-104 0 obj<>endobj
-105 0 obj<>endobj
-106 0 obj<>endobj
-107 0 obj<>endobj
-108 0 obj<>endobj
-109 0 obj<>endobj
-110 0 obj<>endobj
-111 0 obj<>endobj
-112 0 obj<>endobj
-113 0 obj<>endobj
-114 0 obj<>endobj
-115 0 obj<>endobj
-116 0 obj<>endobj
-117 0 obj<>endobj
-118 0 obj<>endobj
-119 0 obj<>endobj
-120 0 obj<>endobj
-121 0 obj<>endobj
-122 0 obj<>endobj
-123 0 obj<>endobj
-124 0 obj<>endobj
-125 0 obj<>endobj
-126 0 obj<>endobj
-127 0 obj<>endobj
-128 0 obj<>endobj
-129 0 obj<>endobj
-130 0 obj<>endobj
-131 0 obj<>endobj
-132 0 obj<>endobj
-133 0 obj<>endobj
-134 0 obj<>endobj
-135 0 obj<>endobj
-136 0 obj<>endobj
-137 0 obj<>endobj
-138 0 obj<>endobj
-139 0 obj<>endobj
-140 0 obj<>endobj
-141 0 obj<>endobj
-142 0 obj<>endobj
-143 0 obj<>endobj
-144 0 obj<>endobj
-145 0 obj<>endobj
+104 0 obj<>endobj
+105 0 obj<>endobj
+106 0 obj<>endobj
+107 0 obj<>endobj
+108 0 obj<>endobj
+109 0 obj<>endobj
+110 0 obj<>endobj
+111 0 obj<>endobj
+112 0 obj<>endobj
+113 0 obj<>endobj
+114 0 obj<>endobj
+115 0 obj<>endobj
+116 0 obj<>endobj
+117 0 obj<>endobj
+118 0 obj<>endobj
+119 0 obj<>endobj
+120 0 obj<>endobj
+121 0 obj<>endobj
+122 0 obj<>endobj
+123 0 obj<>endobj
+124 0 obj<>endobj
+125 0 obj<>endobj
+126 0 obj<>endobj
+127 0 obj<>endobj
+128 0 obj<>endobj
+129 0 obj<>endobj
+130 0 obj<>endobj
+131 0 obj<>endobj
+132 0 obj<>endobj
+133 0 obj<>endobj
+134 0 obj<>endobj
+135 0 obj<>endobj
+136 0 obj<>endobj
+137 0 obj<>endobj
+138 0 obj<>endobj
+139 0 obj<>endobj
+140 0 obj<>endobj
+141 0 obj<>endobj
+142 0 obj<>endobj
+143 0 obj<>endobj
+144 0 obj<>endobj
+145 0 obj<>endobj
 146 0 obj[104 0 R
 105 0 R
 106 0 R
@@ -274,48 +274,48 @@ endobj
 143 0 R
 144 0 R
 145 0 R]endobj
-147 0 obj<>endobj
-148 0 obj<>endobj
-149 0 obj<>endobj
-150 0 obj<>endobj
-151 0 obj<>endobj
-152 0 obj<>endobj
-153 0 obj<>endobj
-154 0 obj<>endobj
-155 0 obj<>endobj
-156 0 obj<>endobj
-157 0 obj<>endobj
-158 0 obj<>endobj
-159 0 obj<>endobj
-160 0 obj<>endobj
-161 0 obj<>endobj
-162 0 obj<>endobj
-163 0 obj<>endobj
-164 0 obj<>endobj
-165 0 obj<>endobj
-166 0 obj<>endobj
-167 0 obj<>endobj
-168 0 obj<>endobj
-169 0 obj<>endobj
-170 0 obj<>endobj
-171 0 obj<>endobj
-172 0 obj<>endobj
-173 0 obj<>endobj
-174 0 obj<>endobj
-175 0 obj<>endobj
-176 0 obj<>endobj
-177 0 obj<>endobj
-178 0 obj<>endobj
-179 0 obj<>endobj
-180 0 obj<>endobj
-181 0 obj<>endobj
-182 0 obj<>endobj
-183 0 obj<>endobj
-184 0 obj<>endobj
-185 0 obj<>endobj
-186 0 obj<>endobj
-187 0 obj<>endobj
-188 0 obj<>endobj
+147 0 obj<>endobj
+148 0 obj<>endobj
+149 0 obj<>endobj
+150 0 obj<>endobj
+151 0 obj<>endobj
+152 0 obj<>endobj
+153 0 obj<>endobj
+154 0 obj<>endobj
+155 0 obj<>endobj
+156 0 obj<>endobj
+157 0 obj<>endobj
+158 0 obj<>endobj
+159 0 obj<>endobj
+160 0 obj<>endobj
+161 0 obj<>endobj
+162 0 obj<>endobj
+163 0 obj<>endobj
+164 0 obj<>endobj
+165 0 obj<>endobj
+166 0 obj<>endobj
+167 0 obj<>endobj
+168 0 obj<>endobj
+169 0 obj<>endobj
+170 0 obj<>endobj
+171 0 obj<>endobj
+172 0 obj<>endobj
+173 0 obj<>endobj
+174 0 obj<>endobj
+175 0 obj<>endobj
+176 0 obj<>endobj
+177 0 obj<>endobj
+178 0 obj<>endobj
+179 0 obj<>endobj
+180 0 obj<>endobj
+181 0 obj<>endobj
+182 0 obj<>endobj
+183 0 obj<>endobj
+184 0 obj<>endobj
+185 0 obj<>endobj
+186 0 obj<>endobj
+187 0 obj<>endobj
+188 0 obj<>endobj
 189 0 obj[147 0 R
 148 0 R
 149 0 R
@@ -358,50 +358,50 @@ endobj
 186 0 R
 187 0 R
 188 0 R]endobj
-190 0 obj<>endobj
-191 0 obj<>endobj
-192 0 obj<>endobj
-193 0 obj<>endobj
-194 0 obj<>endobj
-195 0 obj<>endobj
-196 0 obj<>endobj
-197 0 obj<>endobj
-198 0 obj<>endobj
-199 0 obj<>endobj
-200 0 obj<>endobj
-201 0 obj<>endobj
-202 0 obj<>endobj
-203 0 obj<>endobj
-204 0 obj<>endobj
-205 0 obj<>endobj
-206 0 obj<>endobj
-207 0 obj<>endobj
-208 0 obj<>endobj
-209 0 obj<>endobj
-210 0 obj<>endobj
-211 0 obj<>endobj
-212 0 obj<>endobj
-213 0 obj<>endobj
-214 0 obj<>endobj
-215 0 obj<>endobj
-216 0 obj<>endobj
-217 0 obj<>endobj
-218 0 obj<>endobj
-219 0 obj<>endobj
-220 0 obj<>endobj
-221 0 obj<>endobj
-222 0 obj<>endobj
-223 0 obj<>endobj
-224 0 obj<>endobj
-225 0 obj<>endobj
-226 0 obj<>endobj
-227 0 obj<>endobj
-228 0 obj<>endobj
-229 0 obj<>endobj
-230 0 obj<>endobj
-231 0 obj<>endobj
-232 0 obj<>endobj
-233 0 obj<>endobj
+190 0 obj<>endobj
+191 0 obj<>endobj
+192 0 obj<>endobj
+193 0 obj<>endobj
+194 0 obj<>endobj
+195 0 obj<>endobj
+196 0 obj<>endobj
+197 0 obj<>endobj
+198 0 obj<>endobj
+199 0 obj<>endobj
+200 0 obj<>endobj
+201 0 obj<>endobj
+202 0 obj<>endobj
+203 0 obj<>endobj
+204 0 obj<>endobj
+205 0 obj<>endobj
+206 0 obj<>endobj
+207 0 obj<>endobj
+208 0 obj<>endobj
+209 0 obj<>endobj
+210 0 obj<>endobj
+211 0 obj<>endobj
+212 0 obj<>endobj
+213 0 obj<>endobj
+214 0 obj<>endobj
+215 0 obj<>endobj
+216 0 obj<>endobj
+217 0 obj<>endobj
+218 0 obj<>endobj
+219 0 obj<>endobj
+220 0 obj<>endobj
+221 0 obj<>endobj
+222 0 obj<>endobj
+223 0 obj<>endobj
+224 0 obj<>endobj
+225 0 obj<>endobj
+226 0 obj<>endobj
+227 0 obj<>endobj
+228 0 obj<>endobj
+229 0 obj<>endobj
+230 0 obj<>endobj
+231 0 obj<>endobj
+232 0 obj<>endobj
+233 0 obj<>endobj
 234 0 obj[190 0 R
 191 0 R
 192 0 R
@@ -446,49 +446,49 @@ endobj
 231 0 R
 232 0 R
 233 0 R]endobj
-235 0 obj<>endobj
-236 0 obj<>endobj
-237 0 obj<>endobj
-238 0 obj<>endobj
-239 0 obj<>endobj
-240 0 obj<>endobj
-241 0 obj<>endobj
-242 0 obj<>endobj
-243 0 obj<>endobj
-244 0 obj<>endobj
-245 0 obj<>endobj
-246 0 obj<>endobj
-247 0 obj<>endobj
-248 0 obj<>endobj
-249 0 obj<>endobj
-250 0 obj<>endobj
-251 0 obj<>endobj
-252 0 obj<>endobj
-253 0 obj<>endobj
-254 0 obj<>endobj
-255 0 obj<>endobj
-256 0 obj<>endobj
-257 0 obj<>endobj
-258 0 obj<>endobj
-259 0 obj<>endobj
-260 0 obj<>endobj
-261 0 obj<>endobj
-262 0 obj<>endobj
-263 0 obj<>endobj
-264 0 obj<>endobj
-265 0 obj<>endobj
-266 0 obj<>endobj
-267 0 obj<>endobj
-268 0 obj<>endobj
-269 0 obj<>endobj
-270 0 obj<>endobj
-271 0 obj<>endobj
-272 0 obj<>endobj
-273 0 obj<>endobj
-274 0 obj<>endobj
-275 0 obj<>endobj
-276 0 obj<>endobj
-277 0 obj<>endobj
+235 0 obj<>endobj
+236 0 obj<>endobj
+237 0 obj<>endobj
+238 0 obj<>endobj
+239 0 obj<>endobj
+240 0 obj<>endobj
+241 0 obj<>endobj
+242 0 obj<>endobj
+243 0 obj<>endobj
+244 0 obj<>endobj
+245 0 obj<>endobj
+246 0 obj<>endobj
+247 0 obj<>endobj
+248 0 obj<>endobj
+249 0 obj<>endobj
+250 0 obj<>endobj
+251 0 obj<>endobj
+252 0 obj<>endobj
+253 0 obj<>endobj
+254 0 obj<>endobj
+255 0 obj<>endobj
+256 0 obj<>endobj
+257 0 obj<>endobj
+258 0 obj<>endobj
+259 0 obj<>endobj
+260 0 obj<>endobj
+261 0 obj<>endobj
+262 0 obj<>endobj
+263 0 obj<>endobj
+264 0 obj<>endobj
+265 0 obj<>endobj
+266 0 obj<>endobj
+267 0 obj<>endobj
+268 0 obj<>endobj
+269 0 obj<>endobj
+270 0 obj<>endobj
+271 0 obj<>endobj
+272 0 obj<>endobj
+273 0 obj<>endobj
+274 0 obj<>endobj
+275 0 obj<>endobj
+276 0 obj<>endobj
+277 0 obj<>endobj
 278 0 obj[235 0 R
 236 0 R
 237 0 R
@@ -532,48 +532,48 @@ endobj
 275 0 R
 276 0 R
 277 0 R]endobj
-279 0 obj<>endobj
-280 0 obj<>endobj
-281 0 obj<>endobj
-282 0 obj<>endobj
-283 0 obj<>endobj
-284 0 obj<>endobj
-285 0 obj<>endobj
-286 0 obj<>endobj
-287 0 obj<>endobj
-288 0 obj<>endobj
-289 0 obj<>endobj
-290 0 obj<>endobj
-291 0 obj<>endobj
-292 0 obj<>endobj
-293 0 obj<>endobj
-294 0 obj<>endobj
-295 0 obj<>endobj
-296 0 obj<>endobj
-297 0 obj<>endobj
-298 0 obj<>endobj
-299 0 obj<>endobj
-300 0 obj<>endobj
-301 0 obj<>endobj
-302 0 obj<>endobj
-303 0 obj<>endobj
-304 0 obj<>endobj
-305 0 obj<>endobj
-306 0 obj<>endobj
-307 0 obj<>endobj
-308 0 obj<>endobj
-309 0 obj<>endobj
-310 0 obj<>endobj
-311 0 obj<>endobj
-312 0 obj<>endobj
-313 0 obj<>endobj
-314 0 obj<>endobj
-315 0 obj<>endobj
-316 0 obj<>endobj
-317 0 obj<>endobj
-318 0 obj<>endobj
-319 0 obj<>endobj
-320 0 obj<>endobj
+279 0 obj<>endobj
+280 0 obj<>endobj
+281 0 obj<>endobj
+282 0 obj<>endobj
+283 0 obj<>endobj
+284 0 obj<>endobj
+285 0 obj<>endobj
+286 0 obj<>endobj
+287 0 obj<>endobj
+288 0 obj<>endobj
+289 0 obj<>endobj
+290 0 obj<>endobj
+291 0 obj<>endobj
+292 0 obj<>endobj
+293 0 obj<>endobj
+294 0 obj<>endobj
+295 0 obj<>endobj
+296 0 obj<>endobj
+297 0 obj<>endobj
+298 0 obj<>endobj
+299 0 obj<>endobj
+300 0 obj<>endobj
+301 0 obj<>endobj
+302 0 obj<>endobj
+303 0 obj<>endobj
+304 0 obj<>endobj
+305 0 obj<>endobj
+306 0 obj<>endobj
+307 0 obj<>endobj
+308 0 obj<>endobj
+309 0 obj<>endobj
+310 0 obj<>endobj
+311 0 obj<>endobj
+312 0 obj<>endobj
+313 0 obj<>endobj
+314 0 obj<>endobj
+315 0 obj<>endobj
+316 0 obj<>endobj
+317 0 obj<>endobj
+318 0 obj<>endobj
+319 0 obj<>endobj
+320 0 obj<>endobj
 321 0 obj[279 0 R
 280 0 R
 281 0 R
@@ -616,50 +616,50 @@ endobj
 318 0 R
 319 0 R
 320 0 R]endobj
-322 0 obj<>endobj
-323 0 obj<>endobj
-324 0 obj<>endobj
-325 0 obj<>endobj
-326 0 obj<>endobj
-327 0 obj<>endobj
-328 0 obj<>endobj
-329 0 obj<>endobj
-330 0 obj<>endobj
-331 0 obj<>endobj
-332 0 obj<>endobj
-333 0 obj<>endobj
-334 0 obj<>endobj
-335 0 obj<>endobj
-336 0 obj<>endobj
-337 0 obj<>endobj
-338 0 obj<>endobj
-339 0 obj<>endobj
-340 0 obj<>endobj
-341 0 obj<>endobj
-342 0 obj<>endobj
-343 0 obj<>endobj
-344 0 obj<>endobj
-345 0 obj<>endobj
-346 0 obj<>endobj
-347 0 obj<>endobj
-348 0 obj<>endobj
-349 0 obj<>endobj
-350 0 obj<>endobj
-351 0 obj<>endobj
-352 0 obj<>endobj
-353 0 obj<>endobj
-354 0 obj<>endobj
-355 0 obj<>endobj
-356 0 obj<>endobj
-357 0 obj<>endobj
-358 0 obj<>endobj
-359 0 obj<>endobj
-360 0 obj<>endobj
-361 0 obj<>endobj
-362 0 obj<>endobj
-363 0 obj<>endobj
-364 0 obj<>endobj
-365 0 obj<>endobj
+322 0 obj<>endobj
+323 0 obj<>endobj
+324 0 obj<>endobj
+325 0 obj<>endobj
+326 0 obj<>endobj
+327 0 obj<>endobj
+328 0 obj<>endobj
+329 0 obj<>endobj
+330 0 obj<>endobj
+331 0 obj<>endobj
+332 0 obj<>endobj
+333 0 obj<>endobj
+334 0 obj<>endobj
+335 0 obj<>endobj
+336 0 obj<>endobj
+337 0 obj<>endobj
+338 0 obj<>endobj
+339 0 obj<>endobj
+340 0 obj<>endobj
+341 0 obj<>endobj
+342 0 obj<>endobj
+343 0 obj<>endobj
+344 0 obj<>endobj
+345 0 obj<>endobj
+346 0 obj<>endobj
+347 0 obj<>endobj
+348 0 obj<>endobj
+349 0 obj<>endobj
+350 0 obj<>endobj
+351 0 obj<>endobj
+352 0 obj<>endobj
+353 0 obj<>endobj
+354 0 obj<>endobj
+355 0 obj<>endobj
+356 0 obj<>endobj
+357 0 obj<>endobj
+358 0 obj<>endobj
+359 0 obj<>endobj
+360 0 obj<>endobj
+361 0 obj<>endobj
+362 0 obj<>endobj
+363 0 obj<>endobj
+364 0 obj<>endobj
+365 0 obj<>endobj
 366 0 obj[322 0 R
 323 0 R
 324 0 R
@@ -704,20 +704,22 @@ endobj
 363 0 R
 364 0 R
 365 0 R]endobj
-367 0 obj<>endobj
-368 0 obj<>endobj
-369 0 obj<>endobj
-370 0 obj<>endobj
-371 0 obj<>endobj
-372 0 obj<>endobj
-373 0 obj<>endobj
-374 0 obj<>endobj
-375 0 obj<>endobj
-376 0 obj<>endobj
-377 0 obj<>endobj
-378 0 obj<>endobj
-379 0 obj<>endobj
-380 0 obj[367 0 R
+367 0 obj<>endobj
+368 0 obj<>endobj
+369 0 obj<>endobj
+370 0 obj<>endobj
+371 0 obj<>endobj
+372 0 obj<>endobj
+373 0 obj<>endobj
+374 0 obj<>endobj
+375 0 obj<>endobj
+376 0 obj<>endobj
+377 0 obj<>endobj
+378 0 obj<>endobj
+379 0 obj<>endobj
+380 0 obj<>endobj
+381 0 obj<>endobj
+382 0 obj[367 0 R
 368 0 R
 369 0 R
 370 0 R
@@ -729,45 +731,45 @@ endobj
 376 0 R
 377 0 R
 378 0 R
-379 0 R]endobj
-381 0 obj<>endobj
-382 0 obj<>endobj
-383 0 obj<>endobj
-384 0 obj<>endobj
-385 0 obj<>endobj
-386 0 obj<>endobj
-387 0 obj<>endobj
-388 0 obj<>endobj
-389 0 obj<>endobj
-390 0 obj<>endobj
-391 0 obj<>endobj
-392 0 obj<>endobj
-393 0 obj<>endobj
-394 0 obj<>endobj
-395 0 obj<>endobj
-396 0 obj<>endobj
-397 0 obj<>endobj
-398 0 obj<>endobj
-399 0 obj<>endobj
-400 0 obj<>endobj
-401 0 obj<>endobj
-402 0 obj<>endobj
-403 0 obj<>endobj
-404 0 obj<>endobj
-405 0 obj<>endobj
-406 0 obj<>endobj
-407 0 obj<>endobj
-408 0 obj<>endobj
-409 0 obj<>endobj
-410 0 obj<>endobj
-411 0 obj<>endobj
-412 0 obj<>endobj
-413 0 obj[382 0 R
-384 0 R
+379 0 R
+380 0 R
+381 0 R]endobj
+383 0 obj<>endobj
+384 0 obj<>endobj
+385 0 obj<>endobj
+386 0 obj<>endobj
+387 0 obj<>endobj
+388 0 obj<>endobj
+389 0 obj<>endobj
+390 0 obj<>endobj
+391 0 obj<>endobj
+392 0 obj<>endobj
+393 0 obj<>endobj
+394 0 obj<>endobj
+395 0 obj<>endobj
+396 0 obj<>endobj
+397 0 obj<>endobj
+398 0 obj<>endobj
+399 0 obj<>endobj
+400 0 obj<>endobj
+401 0 obj<>endobj
+402 0 obj<>endobj
+403 0 obj<>endobj
+404 0 obj<>endobj
+405 0 obj<>endobj
+406 0 obj<>endobj
+407 0 obj<>endobj
+408 0 obj<>endobj
+409 0 obj<>endobj
+410 0 obj<>endobj
+411 0 obj<>endobj
+412 0 obj<>endobj
+413 0 obj<>endobj
+414 0 obj<>endobj
+415 0 obj[384 0 R
 386 0 R
 388 0 R
 390 0 R
-391 0 R
 392 0 R
 393 0 R
 394 0 R
@@ -788,63 +790,63 @@ endobj
 409 0 R
 410 0 R
 411 0 R
-412 0 R]endobj
-414 0 obj<>endobj
-415 0 obj<>endobj
-416 0 obj<>endobj
-417 0 obj<>endobj
-418 0 obj<>endobj
-419 0 obj<>endobj
-420 0 obj<>endobj
-421 0 obj<>endobj
-422 0 obj<>endobj
-423 0 obj<>endobj
-424 0 obj<>endobj
-425 0 obj<>endobj
-426 0 obj<>endobj
-427 0 obj<>endobj
-428 0 obj<>endobj
-429 0 obj<>endobj
-430 0 obj<>endobj
-431 0 obj<>endobj
-432 0 obj<>endobj
-433 0 obj<>endobj
-434 0 obj<>endobj
-435 0 obj<>endobj
-436 0 obj<>endobj
-437 0 obj<>endobj
-438 0 obj<>endobj
-439 0 obj<>endobj
-440 0 obj<>endobj
-441 0 obj<>endobj
-442 0 obj<>endobj
-443 0 obj<>endobj
-444 0 obj<>endobj
-445 0 obj<>endobj
-446 0 obj<>endobj
-447 0 obj<>endobj
-448 0 obj<>endobj
-449 0 obj<>endobj
-450 0 obj<>endobj
-451 0 obj<>endobj
-452 0 obj<>endobj
-453 0 obj<>endobj
-454 0 obj<>endobj
-455 0 obj<>endobj
-456 0 obj<>endobj
-457 0 obj<>endobj
-458 0 obj<>endobj
-459 0 obj<>endobj
-460 0 obj<>endobj
-461 0 obj<>endobj
-462 0 obj<>endobj
-463 0 obj<>endobj
-464 0 obj<>endobj
-465 0 obj<>endobj
-466 0 obj<>endobj
-467 0 obj[414 0 R
-415 0 R
-416 0 R
+412 0 R
+413 0 R
+414 0 R]endobj
+416 0 obj<>endobj
+417 0 obj<>endobj
+418 0 obj<>endobj
+419 0 obj<>endobj
+420 0 obj<>endobj
+421 0 obj<>endobj
+422 0 obj<>endobj
+423 0 obj<>endobj
+424 0 obj<>endobj
+425 0 obj<>endobj
+426 0 obj<>endobj
+427 0 obj<>endobj
+428 0 obj<>endobj
+429 0 obj<>endobj
+430 0 obj<>endobj
+431 0 obj<>endobj
+432 0 obj<>endobj
+433 0 obj<>endobj
+434 0 obj<>endobj
+435 0 obj<>endobj
+436 0 obj<>endobj
+437 0 obj<>endobj
+438 0 obj<>endobj
+439 0 obj<>endobj
+440 0 obj<>endobj
+441 0 obj<>endobj
+442 0 obj<>endobj
+443 0 obj<>endobj
+444 0 obj<>endobj
+445 0 obj<>endobj
+446 0 obj<>endobj
+447 0 obj<>endobj
+448 0 obj<>endobj
+449 0 obj<>endobj
+450 0 obj<>endobj
+451 0 obj<>endobj
+452 0 obj<>endobj
+453 0 obj<>endobj
+454 0 obj<>endobj
+455 0 obj<>endobj
+456 0 obj<>endobj
+457 0 obj<>endobj
+458 0 obj<>endobj
+459 0 obj<>endobj
+460 0 obj<>endobj
+461 0 obj<>endobj
+462 0 obj<>endobj
+463 0 obj<>endobj
+464 0 obj<>endobj
+465 0 obj<>endobj
+466 0 obj<>endobj
+467 0 obj<>endobj
+468 0 obj<>endobj
+469 0 obj[416 0 R
 417 0 R
 418 0 R
 419 0 R
@@ -894,62 +896,62 @@ endobj
 463 0 R
 464 0 R
 465 0 R
-466 0 R]endobj
-468 0 obj<>endobj
-469 0 obj<>endobj
-470 0 obj<>endobj
-471 0 obj<>endobj
-472 0 obj<>endobj
-473 0 obj<>endobj
-474 0 obj<>endobj
-475 0 obj<>endobj
-476 0 obj<>endobj
-477 0 obj<>endobj
-478 0 obj<>endobj
-479 0 obj<>endobj
-480 0 obj<>endobj
-481 0 obj<>endobj
-482 0 obj<>endobj
-483 0 obj<>endobj
-484 0 obj<>endobj
-485 0 obj<>endobj
-486 0 obj<>endobj
-487 0 obj<>endobj
-488 0 obj<>endobj
-489 0 obj<>endobj
-490 0 obj<>endobj
-491 0 obj<>endobj
-492 0 obj<>endobj
-493 0 obj<>endobj
-494 0 obj<>endobj
-495 0 obj<>endobj
-496 0 obj<>endobj
-497 0 obj<>endobj
-498 0 obj<>endobj
-499 0 obj<>endobj
-500 0 obj<>endobj
-501 0 obj<>endobj
-502 0 obj<>endobj
-503 0 obj<>endobj
-504 0 obj<>endobj
-505 0 obj<>endobj
-506 0 obj<>endobj
-507 0 obj<>endobj
-508 0 obj<>endobj
-509 0 obj<>endobj
-510 0 obj<>endobj
-511 0 obj<>endobj
-512 0 obj<>endobj
-513 0 obj<>endobj
-514 0 obj<>endobj
-515 0 obj<>endobj
-516 0 obj<>endobj
-517 0 obj<>endobj
-518 0 obj<>endobj
-519 0 obj<>endobj
-520 0 obj[468 0 R
-469 0 R
-470 0 R
+466 0 R
+467 0 R
+468 0 R]endobj
+470 0 obj<>endobj
+471 0 obj<>endobj
+472 0 obj<>endobj
+473 0 obj<>endobj
+474 0 obj<>endobj
+475 0 obj<>endobj
+476 0 obj<>endobj
+477 0 obj<>endobj
+478 0 obj<>endobj
+479 0 obj<>endobj
+480 0 obj<>endobj
+481 0 obj<>endobj
+482 0 obj<>endobj
+483 0 obj<>endobj
+484 0 obj<>endobj
+485 0 obj<>endobj
+486 0 obj<>endobj
+487 0 obj<>endobj
+488 0 obj<>endobj
+489 0 obj<>endobj
+490 0 obj<>endobj
+491 0 obj<>endobj
+492 0 obj<>endobj
+493 0 obj<>endobj
+494 0 obj<>endobj
+495 0 obj<>endobj
+496 0 obj<>endobj
+497 0 obj<>endobj
+498 0 obj<>endobj
+499 0 obj<>endobj
+500 0 obj<>endobj
+501 0 obj<>endobj
+502 0 obj<>endobj
+503 0 obj<>endobj
+504 0 obj<>endobj
+505 0 obj<>endobj
+506 0 obj<>endobj
+507 0 obj<>endobj
+508 0 obj<>endobj
+509 0 obj<>endobj
+510 0 obj<>endobj
+511 0 obj<>endobj
+512 0 obj<>endobj
+513 0 obj<>endobj
+514 0 obj<>endobj
+515 0 obj<>endobj
+516 0 obj<>endobj
+517 0 obj<>endobj
+518 0 obj<>endobj
+519 0 obj<>endobj
+520 0 obj<>endobj
+521 0 obj<>endobj
+522 0 obj[470 0 R
 471 0 R
 472 0 R
 473 0 R
@@ -998,61 +1000,61 @@ endobj
 516 0 R
 517 0 R
 518 0 R
-519 0 R]endobj
-521 0 obj<>endobj
-522 0 obj<>endobj
-523 0 obj<>endobj
-524 0 obj<>endobj
-525 0 obj<>endobj
-526 0 obj<>endobj
-527 0 obj<>endobj
-528 0 obj<>endobj
-529 0 obj<>endobj
-530 0 obj<>endobj
-531 0 obj<>endobj
-532 0 obj<>endobj
-533 0 obj<>endobj
-534 0 obj<>endobj
-535 0 obj<>endobj
-536 0 obj<>endobj
-537 0 obj<>endobj
-538 0 obj<>endobj
-539 0 obj<>endobj
-540 0 obj<>endobj
-541 0 obj<>endobj
-542 0 obj<>endobj
-543 0 obj<>endobj
-544 0 obj<>endobj
-545 0 obj<>endobj
-546 0 obj<>endobj
-547 0 obj<>endobj
-548 0 obj<>endobj
-549 0 obj<>endobj
-550 0 obj<>endobj
-551 0 obj<>endobj
-552 0 obj<>endobj
-553 0 obj<>endobj
-554 0 obj<>endobj
-555 0 obj<>endobj
-556 0 obj<>endobj
-557 0 obj<>endobj
-558 0 obj<>endobj
-559 0 obj<>endobj
-560 0 obj<>endobj
-561 0 obj<>endobj
-562 0 obj<>endobj
-563 0 obj<>endobj
-564 0 obj<>endobj
-565 0 obj<>endobj
-566 0 obj<>endobj
-567 0 obj<>endobj
-568 0 obj<>endobj
-569 0 obj<>endobj
-570 0 obj<>endobj
-571 0 obj<>endobj
-572 0 obj[521 0 R
-522 0 R
-523 0 R
+519 0 R
+520 0 R
+521 0 R]endobj
+523 0 obj<>endobj
+524 0 obj<>endobj
+525 0 obj<>endobj
+526 0 obj<>endobj
+527 0 obj<>endobj
+528 0 obj<>endobj
+529 0 obj<>endobj
+530 0 obj<>endobj
+531 0 obj<>endobj
+532 0 obj<>endobj
+533 0 obj<>endobj
+534 0 obj<>endobj
+535 0 obj<>endobj
+536 0 obj<>endobj
+537 0 obj<>endobj
+538 0 obj<>endobj
+539 0 obj<>endobj
+540 0 obj<>endobj
+541 0 obj<>endobj
+542 0 obj<>endobj
+543 0 obj<>endobj
+544 0 obj<>endobj
+545 0 obj<>endobj
+546 0 obj<>endobj
+547 0 obj<>endobj
+548 0 obj<>endobj
+549 0 obj<>endobj
+550 0 obj<>endobj
+551 0 obj<>endobj
+552 0 obj<>endobj
+553 0 obj<>endobj
+554 0 obj<>endobj
+555 0 obj<>endobj
+556 0 obj<>endobj
+557 0 obj<>endobj
+558 0 obj<>endobj
+559 0 obj<>endobj
+560 0 obj<>endobj
+561 0 obj<>endobj
+562 0 obj<>endobj
+563 0 obj<>endobj
+564 0 obj<>endobj
+565 0 obj<>endobj
+566 0 obj<>endobj
+567 0 obj<>endobj
+568 0 obj<>endobj
+569 0 obj<>endobj
+570 0 obj<>endobj
+571 0 obj<>endobj
+572 0 obj<>endobj
+573 0 obj<>endobj
+574 0 obj[523 0 R
 524 0 R
 525 0 R
 526 0 R
@@ -1100,44 +1102,45 @@ endobj
 568 0 R
 569 0 R
 570 0 R
-571 0 R]endobj
-573 0 obj<>endobj
-574 0 obj<>endobj
-575 0 obj<>endobj
-576 0 obj<>endobj
-577 0 obj<>endobj
-578 0 obj<>endobj
-579 0 obj<>endobj
-580 0 obj<>endobj
-581 0 obj<>endobj
-582 0 obj<>endobj
-583 0 obj<>endobj
-584 0 obj<>endobj
-585 0 obj<>endobj
-586 0 obj<>endobj
-587 0 obj<>endobj
-588 0 obj<>endobj
-589 0 obj<>endobj
-590 0 obj<>endobj
-591 0 obj<>endobj
-592 0 obj<>endobj
-593 0 obj<>endobj
-594 0 obj<>endobj
-595 0 obj<>endobj
-596 0 obj<>endobj
-597 0 obj<>endobj
-598 0 obj<>endobj
-599 0 obj<>endobj
-600 0 obj<>endobj
-601 0 obj<>endobj
-602 0 obj<>endobj
-603 0 obj<>endobj
-604 0 obj<>endobj
-605 0 obj<>endobj
-606 0 obj<>endobj
-607 0 obj[573 0 R
-574 0 R
-575 0 R
+571 0 R
+572 0 R
+573 0 R]endobj
+575 0 obj<>endobj
+576 0 obj<>endobj
+577 0 obj<>endobj
+578 0 obj<>endobj
+579 0 obj<>endobj
+580 0 obj<>endobj
+581 0 obj<>endobj
+582 0 obj<>endobj
+583 0 obj<>endobj
+584 0 obj<>endobj
+585 0 obj<>endobj
+586 0 obj<>endobj
+587 0 obj<>endobj
+588 0 obj<>endobj
+589 0 obj<>endobj
+590 0 obj<>endobj
+591 0 obj<>endobj
+592 0 obj<>endobj
+593 0 obj<>endobj
+594 0 obj<>endobj
+595 0 obj<>endobj
+596 0 obj<>endobj
+597 0 obj<>endobj
+598 0 obj<>endobj
+599 0 obj<>endobj
+600 0 obj<>endobj
+601 0 obj<>endobj
+602 0 obj<>endobj
+603 0 obj<>endobj
+604 0 obj<>endobj
+605 0 obj<>endobj
+606 0 obj<>endobj
+607 0 obj<>endobj
+608 0 obj<>endobj
+609 0 obj<>endobj
+610 0 obj[575 0 R
 576 0 R
 577 0 R
 578 0 R
@@ -1168,1102 +1171,1109 @@ endobj
 603 0 R
 604 0 R
 605 0 R
-606 0 R]endobj
-608 0 obj<>endobj
-609 0 obj<>endobj
-610 0 obj<>endobj
-611 0 obj<>endobj
-612 0 obj<>endobj
-613 0 obj[609 0 R
-610 0 R
-611 0 R
-612 0 R]endobj
-614 0 obj<>endobj
-615 0 obj<>endobj
-616 0 obj[614 0 R
+606 0 R
+607 0 R
+608 0 R
+609 0 R]endobj
+611 0 obj<>endobj
+612 0 obj<>endobj
+613 0 obj<>endobj
+614 0 obj<>endobj
+615 0 obj<>endobj
+616 0 obj[612 0 R
+613 0 R
+614 0 R
 615 0 R]endobj
-617 0 obj<>endobj
-618 0 obj<>endobj
-619 0 obj<>endobj
-620 0 obj<>endobj
-621 0 obj<>endobj
-622 0 obj<>endobj
-623 0 obj<>endobj
-624 0 obj<>endobj
-625 0 obj<>endobj
-626 0 obj<>endobj
-627 0 obj<>endobj
-628 0 obj<>endobj
-629 0 obj<>endobj
-630 0 obj<>endobj
-631 0 obj<>endobj
-632 0 obj<>endobj
-633 0 obj[618 0 R
-620 0 R
-622 0 R
-624 0 R
-626 0 R
-628 0 R
-630 0 R
-632 0 R]endobj
-634 0 obj<>endobj
-635 0 obj<>endobj
-636 0 obj<>endobj
-637 0 obj<>endobj
-638 0 obj[635 0 R
-637 0 R]endobj
-639 0 obj<>endobj
-640 0 obj<>endobj
-641 0 obj<>endobj
-642 0 obj<>endobj
-643 0 obj<>endobj
-644 0 obj<>endobj
-645 0 obj<>endobj
-646 0 obj<>endobj
-647 0 obj<>endobj
-648 0 obj<>endobj
-649 0 obj<>endobj
-650 0 obj<>endobj
-651 0 obj<>endobj
-652 0 obj<>endobj
-653 0 obj[640 0 R
-642 0 R
-644 0 R
-646 0 R
-648 0 R
-650 0 R
-652 0 R]endobj
-654 0 obj<>endobj
-655 0 obj<>endobj
-656 0 obj[654 0 R
+617 0 obj<>endobj
+618 0 obj<>endobj
+619 0 obj[617 0 R
+618 0 R]endobj
+620 0 obj<>endobj
+621 0 obj<>endobj
+622 0 obj<>endobj
+623 0 obj<>endobj
+624 0 obj<>endobj
+625 0 obj<>endobj
+626 0 obj<>endobj
+627 0 obj<>endobj
+628 0 obj<>endobj
+629 0 obj<>endobj
+630 0 obj<>endobj
+631 0 obj<>endobj
+632 0 obj<>endobj
+633 0 obj<>endobj
+634 0 obj<>endobj
+635 0 obj<>endobj
+636 0 obj[621 0 R
+623 0 R
+625 0 R
+627 0 R
+629 0 R
+631 0 R
+633 0 R
+635 0 R]endobj
+637 0 obj<>endobj
+638 0 obj<>endobj
+639 0 obj<>endobj
+640 0 obj<>endobj
+641 0 obj[638 0 R
+640 0 R]endobj
+642 0 obj<>endobj
+643 0 obj<>endobj
+644 0 obj<>endobj
+645 0 obj<>endobj
+646 0 obj<>endobj
+647 0 obj<>endobj
+648 0 obj<>endobj
+649 0 obj<>endobj
+650 0 obj<>endobj
+651 0 obj<>endobj
+652 0 obj<>endobj
+653 0 obj<>endobj
+654 0 obj<>endobj
+655 0 obj<>endobj
+656 0 obj[643 0 R
+645 0 R
+647 0 R
+649 0 R
+651 0 R
+653 0 R
 655 0 R]endobj
-657 0 obj<>endobj
-658 0 obj<>endobj
-659 0 obj[658 0 R]endobj
-660 0 obj<>endobj
-661 0 obj<>endobj
-662 0 obj<>endobj
-663 0 obj<>endobj
-664 0 obj[661 0 R
-663 0 R]endobj
-665 0 obj<>endobj
-666 0 obj<>endobj
-667 0 obj<>endobj
-668 0 obj<>endobj
-669 0 obj[666 0 R
-668 0 R]endobj
-670 0 obj<>endobj
-671 0 obj<>endobj
-672 0 obj<>endobj
-673 0 obj<>endobj
-674 0 obj<>endobj
-675 0 obj<>endobj
-676 0 obj<>endobj
-677 0 obj<>endobj
-678 0 obj<>endobj
-679 0 obj<>endobj
-680 0 obj<>endobj
-681 0 obj<>endobj
-682 0 obj<>endobj
-683 0 obj<>endobj
-684 0 obj<>endobj
-685 0 obj<>endobj
-686 0 obj<>endobj
-687 0 obj<>endobj
-688 0 obj<>endobj
-689 0 obj<>endobj
-690 0 obj<>endobj
-691 0 obj<>endobj
-692 0 obj<>endobj
-693 0 obj<>endobj
-694 0 obj<>endobj
-695 0 obj<>endobj
-696 0 obj<>endobj
-697 0 obj<>endobj
-698 0 obj<>endobj
-699 0 obj<>endobj
-700 0 obj<>endobj
-701 0 obj<>endobj
-702 0 obj<>endobj
-703 0 obj<>endobj
-704 0 obj<>endobj
-705 0 obj<>endobj
-706 0 obj<>endobj
-707 0 obj<>endobj
-708 0 obj<>endobj
-709 0 obj<>endobj
-710 0 obj<>endobj
-711 0 obj<>endobj
-712 0 obj[671 0 R
-673 0 R
-675 0 R
-677 0 R
-679 0 R
-681 0 R
-683 0 R
-685 0 R
-687 0 R
-689 0 R
-691 0 R
-693 0 R
-695 0 R
-697 0 R
-699 0 R
-701 0 R
-703 0 R
-705 0 R
-707 0 R
-709 0 R
+657 0 obj<>endobj
+658 0 obj<>endobj
+659 0 obj[657 0 R
+658 0 R]endobj
+660 0 obj<>endobj
+661 0 obj<>endobj
+662 0 obj[661 0 R]endobj
+663 0 obj<>endobj
+664 0 obj<>endobj
+665 0 obj<>endobj
+666 0 obj<>endobj
+667 0 obj[664 0 R
+666 0 R]endobj
+668 0 obj<>endobj
+669 0 obj<>endobj
+670 0 obj<>endobj
+671 0 obj<>endobj
+672 0 obj[669 0 R
+671 0 R]endobj
+673 0 obj<>endobj
+674 0 obj<>endobj
+675 0 obj<>endobj
+676 0 obj<>endobj
+677 0 obj<>endobj
+678 0 obj<>endobj
+679 0 obj<>endobj
+680 0 obj<>endobj
+681 0 obj<>endobj
+682 0 obj<>endobj
+683 0 obj<>endobj
+684 0 obj<>endobj
+685 0 obj<>endobj
+686 0 obj<>endobj
+687 0 obj<>endobj
+688 0 obj<>endobj
+689 0 obj<>endobj
+690 0 obj<>endobj
+691 0 obj<>endobj
+692 0 obj<>endobj
+693 0 obj<>endobj
+694 0 obj<>endobj
+695 0 obj<>endobj
+696 0 obj<>endobj
+697 0 obj<>endobj
+698 0 obj<>endobj
+699 0 obj<>endobj
+700 0 obj<>endobj
+701 0 obj<>endobj
+702 0 obj<>endobj
+703 0 obj<>endobj
+704 0 obj<>endobj
+705 0 obj<>endobj
+706 0 obj<>endobj
+707 0 obj<>endobj
+708 0 obj<>endobj
+709 0 obj<>endobj
+710 0 obj<>endobj
+711 0 obj<>endobj
+712 0 obj<>endobj
+713 0 obj<>endobj
+714 0 obj<>endobj
+715 0 obj[674 0 R
+676 0 R
+678 0 R
+680 0 R
+682 0 R
+684 0 R
+686 0 R
+688 0 R
+690 0 R
+692 0 R
+694 0 R
+696 0 R
+698 0 R
+700 0 R
+702 0 R
+704 0 R
+706 0 R
+708 0 R
 710 0 R
-711 0 R]endobj
-713 0 obj<>endobj
-714 0 obj[713 0 R]endobj
-715 0 obj<>endobj
-716 0 obj<>endobj
+712 0 R
+713 0 R
+714 0 R]endobj
+716 0 obj<>endobj
 717 0 obj[716 0 R]endobj
-718 0 obj<>endobj
-719 0 obj<>endobj
-720 0 obj<>endobj
-721 0 obj[719 0 R
-720 0 R]endobj
-722 0 obj<>endobj
-723 0 obj<>endobj
-724 0 obj[723 0 R]endobj
-725 0 obj<>endobj
-726 0 obj<>endobj
-727 0 obj<>endobj
-728 0 obj[725 0 R
-726 0 R
-727 0 R]endobj
-729 0 obj<>endobj
-730 0 obj<>endobj
-731 0 obj<>endobj
-732 0 obj<>endobj
-733 0 obj<>endobj
-734 0 obj<>endobj
-735 0 obj<>endobj
-736 0 obj<>endobj
-737 0 obj[730 0 R
-732 0 R
-734 0 R
-736 0 R]endobj
-738 0 obj<>endobj
-739 0 obj<>endobj
-740 0 obj<>endobj
-741 0 obj<>endobj
-742 0 obj<>endobj
-743 0 obj<>endobj
-744 0 obj<>endobj
-745 0 obj<>endobj
-746 0 obj<>endobj
-747 0 obj<>endobj
-748 0 obj[739 0 R
-741 0 R
-743 0 R
-745 0 R
-747 0 R]endobj
-749 0 obj<>endobj
-750 0 obj<>endobj
-751 0 obj<>endobj
-752 0 obj<>endobj
-753 0 obj<>endobj
-754 0 obj<>endobj
-755 0 obj<>endobj
-756 0 obj<>endobj
-757 0 obj<>endobj
-758 0 obj<>endobj
-759 0 obj[750 0 R
-752 0 R
-754 0 R
-756 0 R
-758 0 R]endobj
-760 0 obj<>endobj
-761 0 obj<>endobj
-762 0 obj<>endobj
-763 0 obj<>endobj
-764 0 obj<>endobj
-765 0 obj<>endobj
-766 0 obj[761 0 R
-763 0 R
-765 0 R]endobj
-767 0 obj<>endobj
-768 0 obj<>endobj
-769 0 obj<>endobj
-770 0 obj<>endobj
-771 0 obj<>endobj
-772 0 obj<>endobj
-773 0 obj<>endobj
-774 0 obj<>endobj
-775 0 obj<>endobj
-776 0 obj<>endobj
-777 0 obj[768 0 R
-770 0 R
-772 0 R
-774 0 R
-776 0 R]endobj
-778 0 obj<>endobj
-779 0 obj<>endobj
-780 0 obj<>endobj
-781 0 obj<>endobj
-782 0 obj[779 0 R
-781 0 R]endobj
-783 0 obj<>endobj
-784 0 obj<>endobj
-785 0 obj<>endobj
-786 0 obj<>endobj
-787 0 obj<>endobj
-788 0 obj<>endobj
-789 0 obj<>endobj
-790 0 obj<>endobj
-791 0 obj[784 0 R
-786 0 R
-788 0 R
-790 0 R]endobj
-792 0 obj<>endobj
-793 0 obj<>endobj
-794 0 obj[793 0 R]endobj
-795 0 obj<>endobj
-796 0 obj<>endobj
+718 0 obj<>endobj
+719 0 obj<>endobj
+720 0 obj[719 0 R]endobj
+721 0 obj<>endobj
+722 0 obj<>endobj
+723 0 obj<>endobj
+724 0 obj[722 0 R
+723 0 R]endobj
+725 0 obj<>endobj
+726 0 obj<>endobj
+727 0 obj[726 0 R]endobj
+728 0 obj<>endobj
+729 0 obj<>endobj
+730 0 obj<>endobj
+731 0 obj[728 0 R
+729 0 R
+730 0 R]endobj
+732 0 obj<>endobj
+733 0 obj<>endobj
+734 0 obj<>endobj
+735 0 obj<>endobj
+736 0 obj<>endobj
+737 0 obj<>endobj
+738 0 obj<>endobj
+739 0 obj<>endobj
+740 0 obj[733 0 R
+735 0 R
+737 0 R
+739 0 R]endobj
+741 0 obj<>endobj
+742 0 obj<>endobj
+743 0 obj<>endobj
+744 0 obj<>endobj
+745 0 obj<>endobj
+746 0 obj<>endobj
+747 0 obj<>endobj
+748 0 obj<>endobj
+749 0 obj<>endobj
+750 0 obj<>endobj
+751 0 obj[742 0 R
+744 0 R
+746 0 R
+748 0 R
+750 0 R]endobj
+752 0 obj<>endobj
+753 0 obj<>endobj
+754 0 obj<>endobj
+755 0 obj<>endobj
+756 0 obj<>endobj
+757 0 obj<>endobj
+758 0 obj<>endobj
+759 0 obj<>endobj
+760 0 obj<>endobj
+761 0 obj<>endobj
+762 0 obj[753 0 R
+755 0 R
+757 0 R
+759 0 R
+761 0 R]endobj
+763 0 obj<>endobj
+764 0 obj<>endobj
+765 0 obj<>endobj
+766 0 obj<>endobj
+767 0 obj<>endobj
+768 0 obj<>endobj
+769 0 obj[764 0 R
+766 0 R
+768 0 R]endobj
+770 0 obj<>endobj
+771 0 obj<>endobj
+772 0 obj<>endobj
+773 0 obj<>endobj
+774 0 obj<>endobj
+775 0 obj<>endobj
+776 0 obj<>endobj
+777 0 obj<>endobj
+778 0 obj<>endobj
+779 0 obj<>endobj
+780 0 obj[771 0 R
+773 0 R
+775 0 R
+777 0 R
+779 0 R]endobj
+781 0 obj<>endobj
+782 0 obj<>endobj
+783 0 obj<>endobj
+784 0 obj<>endobj
+785 0 obj[782 0 R
+784 0 R]endobj
+786 0 obj<>endobj
+787 0 obj<>endobj
+788 0 obj<>endobj
+789 0 obj<>endobj
+790 0 obj<>endobj
+791 0 obj<>endobj
+792 0 obj<>endobj
+793 0 obj<>endobj
+794 0 obj[787 0 R
+789 0 R
+791 0 R
+793 0 R]endobj
+795 0 obj<>endobj
+796 0 obj<>endobj
 797 0 obj[796 0 R]endobj
-798 0 obj<>endobj
-799 0 obj<>endobj
+798 0 obj<>endobj
+799 0 obj<>endobj
 800 0 obj[799 0 R]endobj
-801 0 obj<>endobj
-802 0 obj<>endobj
-803 0 obj<>endobj
-804 0 obj<>endobj
-805 0 obj<>endobj
-806 0 obj<>endobj
-807 0 obj<>endobj
-808 0 obj<>endobj
-809 0 obj<>endobj
-810 0 obj<>endobj
-811 0 obj<>endobj
-812 0 obj<>endobj
-813 0 obj[802 0 R
-804 0 R
-806 0 R
-808 0 R
-810 0 R
-812 0 R]endobj
-814 0 obj<>endobj
-815 0 obj<>endobj
-816 0 obj[815 0 R]endobj
-817 0 obj<>endobj
-818 0 obj<>endobj
-819 0 obj<>endobj
-820 0 obj<>endobj
-821 0 obj<>endobj
-822 0 obj<>endobj
-823 0 obj<>endobj
-824 0 obj<>endobj
-825 0 obj[818 0 R
-820 0 R
-822 0 R
-824 0 R]endobj
-826 0 obj<>endobj
-827 0 obj<>endobj
-828 0 obj<>endobj
-829 0 obj<>endobj
-830 0 obj<>endobj
-831 0 obj<>endobj
-832 0 obj[827 0 R
-829 0 R
-831 0 R]endobj
+801 0 obj<>endobj
+802 0 obj<>endobj
+803 0 obj[802 0 R]endobj
+804 0 obj<>endobj
+805 0 obj<>endobj
+806 0 obj<>endobj
+807 0 obj<>endobj
+808 0 obj<>endobj
+809 0 obj<>endobj
+810 0 obj<>endobj
+811 0 obj<>endobj
+812 0 obj<>endobj
+813 0 obj<>endobj
+814 0 obj<>endobj
+815 0 obj<>endobj
+816 0 obj[805 0 R
+807 0 R
+809 0 R
+811 0 R
+813 0 R
+815 0 R]endobj
+817 0 obj<>endobj
+818 0 obj<>endobj
+819 0 obj[818 0 R]endobj
+820 0 obj<>endobj
+821 0 obj<>endobj
+822 0 obj<>endobj
+823 0 obj<>endobj
+824 0 obj<>endobj
+825 0 obj<>endobj
+826 0 obj<>endobj
+827 0 obj<>endobj
+828 0 obj[821 0 R
+823 0 R
+825 0 R
+827 0 R]endobj
+829 0 obj<>endobj
+830 0 obj<>endobj
+831 0 obj<>endobj
+832 0 obj<>endobj
 833 0 obj<>endobj
-834 0 obj<>endobj
-835 0 obj[834 0 R]endobj
-836 0 obj<>endobj
-837 0 obj<>endobj
+834 0 obj<>endobj
+835 0 obj[830 0 R
+832 0 R
+834 0 R]endobj
+836 0 obj<>endobj
+837 0 obj<>endobj
 838 0 obj[837 0 R]endobj
-839 0 obj<>endobj
-840 0 obj<>endobj
+839 0 obj<>endobj
+840 0 obj<>endobj
 841 0 obj[840 0 R]endobj
-842 0 obj<>endobj
-843 0 obj<>endobj
-844 0 obj<>endobj
-845 0 obj<>endobj
-846 0 obj<>endobj
-847 0 obj<>endobj
-848 0 obj[843 0 R
-845 0 R
-847 0 R]endobj
-849 0 obj<>endobj
-850 0 obj<>endobj
-851 0 obj<>endobj
-852 0 obj<>endobj
-853 0 obj<>endobj
-854 0 obj<>endobj
-855 0 obj<>endobj
-856 0 obj<>endobj
-857 0 obj<>endobj
-858 0 obj<>endobj
-859 0 obj[850 0 R
-852 0 R
-854 0 R
-856 0 R
-858 0 R]endobj
-860 0 obj<>endobj
-861 0 obj<>endobj
-862 0 obj<>endobj
-863 0 obj<>endobj
-864 0 obj<>endobj
-865 0 obj<>endobj
-866 0 obj<>endobj
-867 0 obj<>endobj
-868 0 obj[861 0 R
-863 0 R
-865 0 R
-867 0 R]endobj
-869 0 obj<>endobj
-870 0 obj<>endobj
-871 0 obj<>endobj
-872 0 obj<>endobj
-873 0 obj[870 0 R
-872 0 R]endobj
-874 0 obj<>endobj
-875 0 obj<>endobj
-876 0 obj<>endobj
-877 0 obj<>endobj
-878 0 obj[875 0 R
-877 0 R]endobj
-879 0 obj<>endobj
-880 0 obj<>endobj
-881 0 obj<>endobj
-882 0 obj<>endobj
-883 0 obj[880 0 R
-882 0 R]endobj
-884 0 obj<>endobj
-885 0 obj<>endobj
-886 0 obj[885 0 R]endobj
-887 0 obj<>endobj
-888 0 obj<>endobj
-889 0 obj<>endobj
-890 0 obj<>endobj
-891 0 obj<>endobj
-892 0 obj<>endobj
-893 0 obj[888 0 R
-890 0 R
-892 0 R]endobj
-894 0 obj<>endobj
-895 0 obj<>endobj
-896 0 obj[894 0 R
+842 0 obj<>endobj
+843 0 obj<>endobj
+844 0 obj[843 0 R]endobj
+845 0 obj<>endobj
+846 0 obj<>endobj
+847 0 obj<>endobj
+848 0 obj<>endobj
+849 0 obj<>endobj
+850 0 obj<>endobj
+851 0 obj[846 0 R
+848 0 R
+850 0 R]endobj
+852 0 obj<>endobj
+853 0 obj<>endobj
+854 0 obj<>endobj
+855 0 obj<>endobj
+856 0 obj<>endobj
+857 0 obj<>endobj
+858 0 obj<>endobj
+859 0 obj<>endobj
+860 0 obj<>endobj
+861 0 obj<>endobj
+862 0 obj[853 0 R
+855 0 R
+857 0 R
+859 0 R
+861 0 R]endobj
+863 0 obj<>endobj
+864 0 obj<>endobj
+865 0 obj<>endobj
+866 0 obj<>endobj
+867 0 obj<>endobj
+868 0 obj<>endobj
+869 0 obj<>endobj
+870 0 obj<>endobj
+871 0 obj[864 0 R
+866 0 R
+868 0 R
+870 0 R]endobj
+872 0 obj<>endobj
+873 0 obj<>endobj
+874 0 obj<>endobj
+875 0 obj<>endobj
+876 0 obj[873 0 R
+875 0 R]endobj
+877 0 obj<>endobj
+878 0 obj<>endobj
+879 0 obj<>endobj
+880 0 obj<>endobj
+881 0 obj[878 0 R
+880 0 R]endobj
+882 0 obj<>endobj
+883 0 obj<>endobj
+884 0 obj<>endobj
+885 0 obj<>endobj
+886 0 obj[883 0 R
+885 0 R]endobj
+887 0 obj<>endobj
+888 0 obj<>endobj
+889 0 obj[888 0 R]endobj
+890 0 obj<>endobj
+891 0 obj<>endobj
+892 0 obj<>endobj
+893 0 obj<>endobj
+894 0 obj<>endobj
+895 0 obj<>endobj
+896 0 obj[891 0 R
+893 0 R
 895 0 R]endobj
-897 0 obj<>endobj
-898 0 obj<>endobj
-899 0 obj[898 0 R]endobj
-900 0 obj<>endobj
-901 0 obj<>endobj
+897 0 obj<>endobj
+898 0 obj<>endobj
+899 0 obj[897 0 R
+898 0 R]endobj
+900 0 obj<>endobj
+901 0 obj<>endobj
 902 0 obj[901 0 R]endobj
-903 0 obj<>endobj
-904 0 obj<>endobj
-905 0 obj<>endobj
-906 0 obj<>endobj
-907 0 obj<>endobj
-908 0 obj<>endobj
-909 0 obj<>endobj
-910 0 obj<>endobj
-911 0 obj[904 0 R
-906 0 R
-908 0 R
-910 0 R]endobj
-912 0 obj<>endobj
-913 0 obj<>endobj
-914 0 obj<>endobj
-915 0 obj<>endobj
-916 0 obj[913 0 R
-915 0 R]endobj
-917 0 obj<>endobj
-918 0 obj<>endobj
-919 0 obj<>endobj
-920 0 obj<>endobj
-921 0 obj<>endobj
-922 0 obj<>endobj
-923 0 obj<>endobj
-924 0 obj<>endobj
-925 0 obj<>endobj
-926 0 obj<>endobj
-927 0 obj[918 0 R
-920 0 R
-922 0 R
-924 0 R
-926 0 R]endobj
-928 0 obj<>endobj
-929 0 obj<>endobj
-930 0 obj<>endobj
-931 0 obj<>endobj
-932 0 obj<>endobj
-933 0 obj<>endobj
-934 0 obj<>endobj
-935 0 obj<>endobj
-936 0 obj[929 0 R
-931 0 R
-933 0 R
-935 0 R]endobj
-937 0 obj<>endobj
-938 0 obj<>endobj
-939 0 obj[938 0 R]endobj
-940 0 obj<>endobj
-941 0 obj<>endobj
-942 0 obj<>endobj
-943 0 obj<>endobj
-944 0 obj<>endobj
-945 0 obj<>endobj
-946 0 obj[941 0 R
-943 0 R
-945 0 R]endobj
-947 0 obj<>endobj
-948 0 obj[947 0 R]endobj
-949 0 obj<>endobj
-950 0 obj<>endobj
-951 0 obj<>endobj
-952 0 obj<>endobj
-953 0 obj[950 0 R
-952 0 R]endobj
-954 0 obj<>endobj
-955 0 obj<>endobj
-956 0 obj<>endobj
-957 0 obj<>endobj
-958 0 obj<>endobj
-959 0 obj<>endobj
-960 0 obj<>endobj
-961 0 obj<>endobj
-962 0 obj<>endobj
-963 0 obj<>endobj
-964 0 obj<>endobj
-965 0 obj<>endobj
-966 0 obj<>endobj
-967 0 obj<>endobj
-968 0 obj<>endobj
-969 0 obj<>endobj
-970 0 obj[955 0 R
-957 0 R
-959 0 R
-961 0 R
+903 0 obj<>endobj
+904 0 obj<>endobj
+905 0 obj[904 0 R]endobj
+906 0 obj<>endobj
+907 0 obj<>endobj
+908 0 obj[907 0 R]endobj
+909 0 obj<>endobj
+910 0 obj<>endobj
+911 0 obj<>endobj
+912 0 obj<>endobj
+913 0 obj<>endobj
+914 0 obj<>endobj
+915 0 obj<>endobj
+916 0 obj<>endobj
+917 0 obj[910 0 R
+912 0 R
+914 0 R
+916 0 R]endobj
+918 0 obj<>endobj
+919 0 obj<>endobj
+920 0 obj<>endobj
+921 0 obj<>endobj
+922 0 obj[919 0 R
+921 0 R]endobj
+923 0 obj<>endobj
+924 0 obj<>endobj
+925 0 obj<>endobj
+926 0 obj<>endobj
+927 0 obj<>endobj
+928 0 obj<>endobj
+929 0 obj<>endobj
+930 0 obj<>endobj
+931 0 obj<>endobj
+932 0 obj<>endobj
+933 0 obj[924 0 R
+926 0 R
+928 0 R
+930 0 R
+932 0 R]endobj
+934 0 obj<>endobj
+935 0 obj<>endobj
+936 0 obj<>endobj
+937 0 obj<>endobj
+938 0 obj<>endobj
+939 0 obj<>endobj
+940 0 obj<>endobj
+941 0 obj<>endobj
+942 0 obj[935 0 R
+937 0 R
+939 0 R
+941 0 R]endobj
+943 0 obj<>endobj
+944 0 obj<>endobj
+945 0 obj[944 0 R]endobj
+946 0 obj<>endobj
+947 0 obj<>endobj
+948 0 obj<>endobj
+949 0 obj<>endobj
+950 0 obj<>endobj
+951 0 obj<>endobj
+952 0 obj[947 0 R
+949 0 R
+951 0 R]endobj
+953 0 obj<>endobj
+954 0 obj[953 0 R]endobj
+955 0 obj<>endobj
+956 0 obj<>endobj
+957 0 obj<>endobj
+958 0 obj<>endobj
+959 0 obj[956 0 R
+958 0 R]endobj
+960 0 obj<>endobj
+961 0 obj<>endobj
+962 0 obj<>endobj
+963 0 obj<>endobj
+964 0 obj<>endobj
+965 0 obj<>endobj
+966 0 obj<>endobj
+967 0 obj<>endobj
+968 0 obj<>endobj
+969 0 obj<>endobj
+970 0 obj<>endobj
+971 0 obj<>endobj
+972 0 obj<>endobj
+973 0 obj<>endobj
+974 0 obj<>endobj
+975 0 obj<>endobj
+976 0 obj[961 0 R
 963 0 R
 965 0 R
 967 0 R
-969 0 R]endobj
-971 0 obj<>endobj
-972 0 obj<>endobj
-973 0 obj<>endobj
-974 0 obj<>endobj
-975 0 obj[972 0 R
-974 0 R]endobj
-976 0 obj<>endobj
-977 0 obj<>endobj
-978 0 obj<>endobj
-979 0 obj<>endobj
-980 0 obj<>endobj
-981 0 obj<>endobj
-982 0 obj<>endobj
-983 0 obj[977 0 R
-979 0 R
-981 0 R
-982 0 R]endobj
-984 0 obj<>endobj
-985 0 obj<>endobj
-986 0 obj<>endobj
-987 0 obj<>endobj
-988 0 obj<>endobj
-989 0 obj<>endobj
-990 0 obj<>endobj
-991 0 obj<>endobj
-992 0 obj<>endobj
-993 0 obj<>endobj
-994 0 obj<>endobj
-995 0 obj<>endobj
-996 0 obj<>endobj
-997 0 obj<>endobj
-998 0 obj<>endobj
-999 0 obj<>endobj
-1000 0 obj<>endobj
-1001 0 obj<>endobj
-1002 0 obj<>endobj
-1003 0 obj<>endobj
-1004 0 obj<>endobj
-1005 0 obj<>endobj
-1006 0 obj<>endobj
-1007 0 obj<>endobj
-1008 0 obj<>endobj
-1009 0 obj<>endobj
-1010 0 obj<>endobj
-1011 0 obj<>endobj
-1012 0 obj<>endobj
-1013 0 obj<>endobj
-1014 0 obj<>endobj
-1015 0 obj<>endobj
-1016 0 obj<>endobj
-1017 0 obj<>endobj
-1018 0 obj<>endobj
-1019 0 obj<>endobj
-1020 0 obj<>endobj
-1021 0 obj<>endobj
-1022 0 obj<>endobj
-1023 0 obj<>endobj
-1024 0 obj<>endobj
-1025 0 obj<>endobj
-1026 0 obj<>endobj
-1027 0 obj<>endobj
-1028 0 obj<>endobj
-1029 0 obj<>endobj
-1030 0 obj<>endobj
-1031 0 obj<>endobj
-1032 0 obj<>endobj
-1033 0 obj<>endobj
-1034 0 obj<>endobj
-1035 0 obj<>endobj
-1036 0 obj<>endobj
-1037 0 obj<>endobj
-1038 0 obj<>endobj
-1039 0 obj<>endobj
-1040 0 obj<>endobj
-1041 0 obj<>endobj
-1042 0 obj<>endobj
-1043 0 obj<>endobj
-1044 0 obj<>endobj
-1045 0 obj<>endobj
-1046 0 obj<>endobj
-1047 0 obj<>endobj
-1048 0 obj<>endobj
-1049 0 obj<>endobj
-1050 0 obj<>endobj
-1051 0 obj<>endobj
-1052 0 obj<>endobj
-1053 0 obj<>endobj
-1054 0 obj<>endobj
-1055 0 obj<>endobj
-1056 0 obj<>endobj
-1057 0 obj<>endobj
-1058 0 obj<>endobj
-1059 0 obj<>endobj
-1060 0 obj<>endobj
-1061 0 obj<>endobj
-1062 0 obj<>endobj
-1063 0 obj<>endobj
-1064 0 obj<>endobj
-1065 0 obj<>endobj
-1066 0 obj<>endobj
-1067 0 obj<>endobj
-1068 0 obj<>endobj
-1069 0 obj<>endobj
-1070 0 obj<>endobj
-1071 0 obj<>endobj
-1072 0 obj<>endobj
-1073 0 obj<>endobj
-1074 0 obj<>endobj
-1075 0 obj<>endobj
-1076 0 obj<>endobj
-1077 0 obj<>endobj
-1078 0 obj<>endobj
-1079 0 obj<>endobj
-1080 0 obj<>endobj
-1081 0 obj<>endobj
-1082 0 obj<>endobj
-1083 0 obj<>endobj
-1084 0 obj<>endobj
-1085 0 obj<>endobj
-1086 0 obj<>endobj
-1087 0 obj<>endobj
-1088 0 obj<>endobj
-1089 0 obj<>endobj
-1090 0 obj<>endobj
-1091 0 obj<>endobj
-1092 0 obj<>endobj
-1093 0 obj<>endobj
-1094 0 obj<>endobj
-1095 0 obj<>endobj
-1096 0 obj<>endobj
-1097 0 obj<>endobj
-1098 0 obj<>endobj
-1099 0 obj<>endobj
-1100 0 obj<>endobj
-1101 0 obj<>endobj
-1102 0 obj<>endobj
-1103 0 obj<>endobj
-1104 0 obj<>endobj
-1105 0 obj<>endobj
-1106 0 obj<>endobj
-1107 0 obj<>endobj
-1108 0 obj<>endobj
-1109 0 obj<>endobj
-1110 0 obj<>endobj
-1111 0 obj<>endobj
-1112 0 obj<>endobj
-1113 0 obj<>endobj
-1114 0 obj<>endobj
-1115 0 obj<>endobj
-1116 0 obj<>endobj
-1117 0 obj<>endobj
-1118 0 obj<>endobj
-1119 0 obj<>endobj
-1120 0 obj<>endobj
-1121 0 obj<>endobj
-1122 0 obj<>endobj
-1123 0 obj<>endobj
-1124 0 obj<>endobj
-1125 0 obj<>endobj
-1126 0 obj<>endobj
-1127 0 obj<>endobj
-1128 0 obj<>endobj
-1129 0 obj<>endobj
-1130 0 obj<>endobj
-1131 0 obj<>endobj
-1132 0 obj<>endobj
-1133 0 obj<>endobj
-1134 0 obj<>endobj
-1135 0 obj<>endobj
-1136 0 obj<>endobj
-1137 0 obj<>endobj
-1138 0 obj<>endobj
-1139 0 obj<>endobj
-1140 0 obj<>endobj
-1141 0 obj<>endobj
-1142 0 obj<>endobj
-1143 0 obj<>endobj
-1144 0 obj<>endobj
-1145 0 obj<>endobj
-1146 0 obj<>endobj
-1147 0 obj<>endobj
-1148 0 obj<>endobj
-1149 0 obj<>endobj
-1150 0 obj<>endobj
-1151 0 obj<>endobj
-1152 0 obj<>endobj
-1153 0 obj<>endobj
-1154 0 obj<>endobj
-1155 0 obj<>endobj
-1156 0 obj<>endobj
-1157 0 obj<>endobj
-1158 0 obj<>endobj
-1159 0 obj<>endobj
-1160 0 obj<>endobj
-1161 0 obj<>endobj
-1162 0 obj<>endobj
-1163 0 obj<>endobj
-1164 0 obj<>endobj
-1165 0 obj<>endobj
-1166 0 obj<>endobj
-1167 0 obj<>endobj
-1168 0 obj<>endobj
-1169 0 obj<>endobj
-1170 0 obj<>endobj
-1171 0 obj<>endobj
-1172 0 obj<>endobj
-1173 0 obj<>endobj
-1174 0 obj<>endobj
-1175 0 obj<>endobj
-1176 0 obj<>endobj
-1177 0 obj<>endobj
-1178 0 obj<>endobj
-1179 0 obj<>endobj
-1180 0 obj<>endobj
-1181 0 obj<>endobj
-1182 0 obj<>endobj
-1183 0 obj<>endobj
-1184 0 obj<>endobj
-1185 0 obj<>endobj
-1186 0 obj<>endobj
-1187 0 obj<>endobj
-1188 0 obj<>endobj
-1189 0 obj<>endobj
-1190 0 obj<>endobj
-1191 0 obj<>endobj
-1192 0 obj<>endobj
-1193 0 obj<>endobj
-1194 0 obj<>endobj
-1195 0 obj<>endobj
-1196 0 obj<>endobj
-1197 0 obj<>endobj
-1198 0 obj<>endobj
-1199 0 obj<>endobj
-1200 0 obj<>endobj
-1201 0 obj<>endobj
-1202 0 obj<>endobj
-1203 0 obj<>endobj
-1204 0 obj<>endobj
-1205 0 obj<>endobj
-1206 0 obj<>endobj
-1207 0 obj<>endobj
-1208 0 obj<>endobj
-1209 0 obj<>endobj
-1210 0 obj<>endobj
-1211 0 obj<>endobj
-1212 0 obj<>endobj
-1213 0 obj<>endobj
-1214 0 obj<>endobj
-1215 0 obj<>endobj
-1216 0 obj<>endobj
-1217 0 obj<>endobj
-1218 0 obj<>endobj
-1219 0 obj<>endobj
-1220 0 obj<>endobj
-1221 0 obj<>endobj
-1222 0 obj<>endobj
-1223 0 obj<>endobj
-1224 0 obj<>endobj
-1225 0 obj<>endobj
-1226 0 obj<>endobj
-1227 0 obj<>endobj
-1228 0 obj<>endobj
-1229 0 obj<>endobj
-1230 0 obj<>endobj
-1231 0 obj<>endobj
-1232 0 obj<>endobj
-1233 0 obj<>endobj
-1234 0 obj<>endobj
-1235 0 obj<>endobj
-1236 0 obj<>endobj
-1237 0 obj<>endobj
-1238 0 obj<>endobj
-1239 0 obj<>endobj
-1240 0 obj<>endobj
-1241 0 obj<>endobj
-1242 0 obj<>endobj
-1243 0 obj<>endobj
-1244 0 obj<>endobj
-1245 0 obj<>endobj
-1246 0 obj<>endobj
-1247 0 obj<>endobj
-1248 0 obj<>endobj
-1249 0 obj<>endobj
-1250 0 obj<>endobj
-1251 0 obj<>endobj
-1252 0 obj<>endobj
-1253 0 obj<>endobj
-1254 0 obj<>endobj
-1255 0 obj<>endobj
-1256 0 obj<>endobj
-1257 0 obj<>endobj
-1258 0 obj<>endobj
-1259 0 obj<>endobj
-1260 0 obj<>endobj
-1261 0 obj<>endobj
-1262 0 obj<>endobj
-1263 0 obj<>endobj
-1264 0 obj<>endobj
-1265 0 obj<>endobj
-1266 0 obj<>endobj
-1267 0 obj<>endobj
-1268 0 obj<>endobj
-1269 0 obj<>endobj
-1270 0 obj<>endobj
-1271 0 obj<>endobj
-1272 0 obj<>endobj
-1273 0 obj<>endobj
-1274 0 obj<>endobj
-1275 0 obj<>endobj
-1276 0 obj<>endobj
-1277 0 obj<>endobj
-1278 0 obj<>endobj
-1279 0 obj<>endobj
-1280 0 obj<>endobj
-1281 0 obj<>endobj
-1282 0 obj<>endobj
-1283 0 obj<>endobj
-1284 0 obj<>endobj
-1285 0 obj<>endobj
-1286 0 obj<>endobj
-1287 0 obj<>endobj
-1288 0 obj<>endobj
-1289 0 obj<>endobj
-1290 0 obj<>endobj
-1291 0 obj<>endobj
-1292 0 obj<>endobj
-1293 0 obj<>endobj
-1294 0 obj<>endobj
-1295 0 obj<>endobj
-1296 0 obj<>endobj
-1297 0 obj<>endobj
-1298 0 obj<>endobj
-1299 0 obj<>endobj
-1300 0 obj<>endobj
-1301 0 obj<>endobj
-1302 0 obj<>endobj
-1303 0 obj<>endobj
-1304 0 obj<>endobj
-1305 0 obj<>endobj
-1306 0 obj<>endobj
-1307 0 obj<>endobj
-1308 0 obj<>endobj
-1309 0 obj<>endobj
-1310 0 obj<>endobj
-1311 0 obj<>endobj
-1312 0 obj<>endobj
-1313 0 obj<>endobj
-1314 0 obj<>endobj
-1315 0 obj<>endobj
-1316 0 obj<>endobj
-1317 0 obj<>endobj
-1318 0 obj<>endobj
-1319 0 obj<>endobj
-1320 0 obj<>endobj
-1321 0 obj<>endobj
-1322 0 obj<>endobj
-1323 0 obj<>endobj
-1324 0 obj<>endobj
-1325 0 obj<>endobj
-1326 0 obj<>endobj
-1327 0 obj<>endobj
-1328 0 obj<>endobj
-1329 0 obj<>endobj
-1330 0 obj<>endobj
-1331 0 obj<>endobj
-1332 0 obj<>endobj
-1333 0 obj<>endobj
-1334 0 obj<>endobj
-1335 0 obj<>endobj
-1336 0 obj<>endobj
-1337 0 obj<>endobj
-1338 0 obj<>endobj
-1339 0 obj<>endobj
-1340 0 obj<>endobj
-1341 0 obj<>endobj
-1342 0 obj<>endobj
-1343 0 obj<>endobj
-1344 0 obj<>endobj
-1345 0 obj<>endobj
-1346 0 obj<>endobj
-1347 0 obj<>endobj
-1348 0 obj<>endobj
-1349 0 obj<>endobj
-1350 0 obj<>endobj
-1351 0 obj<>endobj
-1352 0 obj<>endobj
-1353 0 obj<>endobj
-1354 0 obj<>endobj
-1355 0 obj<>endobj
-1356 0 obj<>endobj
-1357 0 obj<>endobj
-1358 0 obj<>endobj
-1359 0 obj<>endobj
-1360 0 obj<>endobj
-1361 0 obj<>endobj
-1362 0 obj<>endobj
-1363 0 obj<>endobj
-1364 0 obj<>endobj
-1365 0 obj<>endobj
-1366 0 obj<>endobj
-1367 0 obj<>endobj
-1368 0 obj<>endobj
-1369 0 obj<>endobj
-1370 0 obj<>endobj
-1371 0 obj<>endobj
-1372 0 obj<>endobj
-1373 0 obj<>endobj
-1374 0 obj<>endobj
-1375 0 obj<>endobj
-1376 0 obj<>endobj
-1377 0 obj<>endobj
-1378 0 obj<>endobj
-1379 0 obj<>endobj
-1380 0 obj<>endobj
+978 0 obj<>endobj
+979 0 obj<>endobj
+980 0 obj<>endobj
+981 0 obj[978 0 R
+980 0 R]endobj
+982 0 obj<>endobj
+983 0 obj<>endobj
+984 0 obj<>endobj
+985 0 obj<>endobj
+986 0 obj<>endobj
+987 0 obj<>endobj
+988 0 obj<>endobj
+989 0 obj[983 0 R
+985 0 R
+987 0 R
+988 0 R]endobj
+990 0 obj<>endobj
+991 0 obj<>endobj
+992 0 obj<>endobj
+993 0 obj<>endobj
+994 0 obj<>endobj
+995 0 obj<>endobj
+996 0 obj<>endobj
+997 0 obj<>endobj
+998 0 obj<>endobj
+999 0 obj<>endobj
+1000 0 obj<>endobj
+1001 0 obj<>endobj
+1002 0 obj<>endobj
+1003 0 obj<>endobj
+1004 0 obj<>endobj
+1005 0 obj<>endobj
+1006 0 obj<>endobj
+1007 0 obj<>endobj
+1008 0 obj<>endobj
+1009 0 obj<>endobj
+1010 0 obj<>endobj
+1011 0 obj<>endobj
+1012 0 obj<>endobj
+1013 0 obj<>endobj
+1014 0 obj<>endobj
+1015 0 obj<>endobj
+1016 0 obj<>endobj
+1017 0 obj<>endobj
+1018 0 obj<>endobj
+1019 0 obj<>endobj
+1020 0 obj<>endobj
+1021 0 obj<>endobj
+1022 0 obj<>endobj
+1023 0 obj<>endobj
+1024 0 obj<>endobj
+1025 0 obj<>endobj
+1026 0 obj<>endobj
+1027 0 obj<>endobj
+1028 0 obj<>endobj
+1029 0 obj<>endobj
+1030 0 obj<>endobj
+1031 0 obj<>endobj
+1032 0 obj<>endobj
+1033 0 obj<>endobj
+1034 0 obj<>endobj
+1035 0 obj<>endobj
+1036 0 obj<>endobj
+1037 0 obj<>endobj
+1038 0 obj<>endobj
+1039 0 obj<>endobj
+1040 0 obj<>endobj
+1041 0 obj<>endobj
+1042 0 obj<>endobj
+1043 0 obj<>endobj
+1044 0 obj<>endobj
+1045 0 obj<>endobj
+1046 0 obj<>endobj
+1047 0 obj<>endobj
+1048 0 obj<>endobj
+1049 0 obj<>endobj
+1050 0 obj<>endobj
+1051 0 obj<>endobj
+1052 0 obj<>endobj
+1053 0 obj<>endobj
+1054 0 obj<>endobj
+1055 0 obj<>endobj
+1056 0 obj<>endobj
+1057 0 obj<>endobj
+1058 0 obj<>endobj
+1059 0 obj<>endobj
+1060 0 obj<>endobj
+1061 0 obj<>endobj
+1062 0 obj<>endobj
+1063 0 obj<>endobj
+1064 0 obj<>endobj
+1065 0 obj<>endobj
+1066 0 obj<>endobj
+1067 0 obj<>endobj
+1068 0 obj<>endobj
+1069 0 obj<>endobj
+1070 0 obj<>endobj
+1071 0 obj<>endobj
+1072 0 obj<>endobj
+1073 0 obj<>endobj
+1074 0 obj<>endobj
+1075 0 obj<>endobj
+1076 0 obj<>endobj
+1077 0 obj<>endobj
+1078 0 obj<>endobj
+1079 0 obj<>endobj
+1080 0 obj<>endobj
+1081 0 obj<>endobj
+1082 0 obj<>endobj
+1083 0 obj<>endobj
+1084 0 obj<>endobj
+1085 0 obj<>endobj
+1086 0 obj<>endobj
+1087 0 obj<>endobj
+1088 0 obj<>endobj
+1089 0 obj<>endobj
+1090 0 obj<>endobj
+1091 0 obj<>endobj
+1092 0 obj<>endobj
+1093 0 obj<>endobj
+1094 0 obj<>endobj
+1095 0 obj<>endobj
+1096 0 obj<>endobj
+1097 0 obj<>endobj
+1098 0 obj<>endobj
+1099 0 obj<>endobj
+1100 0 obj<>endobj
+1101 0 obj<>endobj
+1102 0 obj<>endobj
+1103 0 obj<>endobj
+1104 0 obj<>endobj
+1105 0 obj<>endobj
+1106 0 obj<>endobj
+1107 0 obj<>endobj
+1108 0 obj<>endobj
+1109 0 obj<>endobj
+1110 0 obj<>endobj
+1111 0 obj<>endobj
+1112 0 obj<>endobj
+1113 0 obj<>endobj
+1114 0 obj<>endobj
+1115 0 obj<>endobj
+1116 0 obj<>endobj
+1117 0 obj<>endobj
+1118 0 obj<>endobj
+1119 0 obj<>endobj
+1120 0 obj<>endobj
+1121 0 obj<>endobj
+1122 0 obj<>endobj
+1123 0 obj<>endobj
+1124 0 obj<>endobj
+1125 0 obj<>endobj
+1126 0 obj<>endobj
+1127 0 obj<>endobj
+1128 0 obj<>endobj
+1129 0 obj<>endobj
+1130 0 obj<>endobj
+1131 0 obj<>endobj
+1132 0 obj<>endobj
+1133 0 obj<>endobj
+1134 0 obj<>endobj
+1135 0 obj<>endobj
+1136 0 obj<>endobj
+1137 0 obj<>endobj
+1138 0 obj<>endobj
+1139 0 obj<>endobj
+1140 0 obj<>endobj
+1141 0 obj<>endobj
+1142 0 obj<>endobj
+1143 0 obj<>endobj
+1144 0 obj<>endobj
+1145 0 obj<>endobj
+1146 0 obj<>endobj
+1147 0 obj<>endobj
+1148 0 obj<>endobj
+1149 0 obj<>endobj
+1150 0 obj<>endobj
+1151 0 obj<>endobj
+1152 0 obj<>endobj
+1153 0 obj<>endobj
+1154 0 obj<>endobj
+1155 0 obj<>endobj
+1156 0 obj<>endobj
+1157 0 obj<>endobj
+1158 0 obj<>endobj
+1159 0 obj<>endobj
+1160 0 obj<>endobj
+1161 0 obj<>endobj
+1162 0 obj<>endobj
+1163 0 obj<>endobj
+1164 0 obj<>endobj
+1165 0 obj<>endobj
+1166 0 obj<>endobj
+1167 0 obj<>endobj
+1168 0 obj<>endobj
+1169 0 obj<>endobj
+1170 0 obj<>endobj
+1171 0 obj<>endobj
+1172 0 obj<>endobj
+1173 0 obj<>endobj
+1174 0 obj<>endobj
+1175 0 obj<>endobj
+1176 0 obj<>endobj
+1177 0 obj<>endobj
+1178 0 obj<>endobj
+1179 0 obj<>endobj
+1180 0 obj<>endobj
+1181 0 obj<>endobj
+1182 0 obj<>endobj
+1183 0 obj<>endobj
+1184 0 obj<>endobj
+1185 0 obj<>endobj
+1186 0 obj<>endobj
+1187 0 obj<>endobj
+1188 0 obj<>endobj
+1189 0 obj<>endobj
+1190 0 obj<>endobj
+1191 0 obj<>endobj
+1192 0 obj<>endobj
+1193 0 obj<>endobj
+1194 0 obj<>endobj
+1195 0 obj<>endobj
+1196 0 obj<>endobj
+1197 0 obj<>endobj
+1198 0 obj<>endobj
+1199 0 obj<>endobj
+1200 0 obj<>endobj
+1201 0 obj<>endobj
+1202 0 obj<>endobj
+1203 0 obj<>endobj
+1204 0 obj<>endobj
+1205 0 obj<>endobj
+1206 0 obj<>endobj
+1207 0 obj<>endobj
+1208 0 obj<>endobj
+1209 0 obj<>endobj
+1210 0 obj<>endobj
+1211 0 obj<>endobj
+1212 0 obj<>endobj
+1213 0 obj<>endobj
+1214 0 obj<>endobj
+1215 0 obj<>endobj
+1216 0 obj<>endobj
+1217 0 obj<>endobj
+1218 0 obj<>endobj
+1219 0 obj<>endobj
+1220 0 obj<>endobj
+1221 0 obj<>endobj
+1222 0 obj<>endobj
+1223 0 obj<>endobj
+1224 0 obj<>endobj
+1225 0 obj<>endobj
+1226 0 obj<>endobj
+1227 0 obj<>endobj
+1228 0 obj<>endobj
+1229 0 obj<>endobj
+1230 0 obj<>endobj
+1231 0 obj<>endobj
+1232 0 obj<>endobj
+1233 0 obj<>endobj
+1234 0 obj<>endobj
+1235 0 obj<>endobj
+1236 0 obj<>endobj
+1237 0 obj<>endobj
+1238 0 obj<>endobj
+1239 0 obj<>endobj
+1240 0 obj<>endobj
+1241 0 obj<>endobj
+1242 0 obj<>endobj
+1243 0 obj<>endobj
+1244 0 obj<>endobj
+1245 0 obj<>endobj
+1246 0 obj<>endobj
+1247 0 obj<>endobj
+1248 0 obj<>endobj
+1249 0 obj<>endobj
+1250 0 obj<>endobj
+1251 0 obj<>endobj
+1252 0 obj<>endobj
+1253 0 obj<>endobj
+1254 0 obj<>endobj
+1255 0 obj<>endobj
+1256 0 obj<>endobj
+1257 0 obj<>endobj
+1258 0 obj<>endobj
+1259 0 obj<>endobj
+1260 0 obj<>endobj
+1261 0 obj<>endobj
+1262 0 obj<>endobj
+1263 0 obj<>endobj
+1264 0 obj<>endobj
+1265 0 obj<>endobj
+1266 0 obj<>endobj
+1267 0 obj<>endobj
+1268 0 obj<>endobj
+1269 0 obj<>endobj
+1270 0 obj<>endobj
+1271 0 obj<>endobj
+1272 0 obj<>endobj
+1273 0 obj<>endobj
+1274 0 obj<>endobj
+1275 0 obj<>endobj
+1276 0 obj<>endobj
+1277 0 obj<>endobj
+1278 0 obj<>endobj
+1279 0 obj<>endobj
+1280 0 obj<>endobj
+1281 0 obj<>endobj
+1282 0 obj<>endobj
+1283 0 obj<>endobj
+1284 0 obj<>endobj
+1285 0 obj<>endobj
+1286 0 obj<>endobj
+1287 0 obj<>endobj
+1288 0 obj<>endobj
+1289 0 obj<>endobj
+1290 0 obj<>endobj
+1291 0 obj<>endobj
+1292 0 obj<>endobj
+1293 0 obj<>endobj
+1294 0 obj<>endobj
+1295 0 obj<>endobj
+1296 0 obj<>endobj
+1297 0 obj<>endobj
+1298 0 obj<>endobj
+1299 0 obj<>endobj
+1300 0 obj<>endobj
+1301 0 obj<>endobj
+1302 0 obj<>endobj
+1303 0 obj<>endobj
+1304 0 obj<>endobj
+1305 0 obj<>endobj
+1306 0 obj<>endobj
+1307 0 obj<>endobj
+1308 0 obj<>endobj
+1309 0 obj<>endobj
+1310 0 obj<>endobj
+1311 0 obj<>endobj
+1312 0 obj<>endobj
+1313 0 obj<>endobj
+1314 0 obj<>endobj
+1315 0 obj<>endobj
+1316 0 obj<>endobj
+1317 0 obj<>endobj
+1318 0 obj<>endobj
+1319 0 obj<>endobj
+1320 0 obj<>endobj
+1321 0 obj<>endobj
+1322 0 obj<>endobj
+1323 0 obj<>endobj
+1324 0 obj<>endobj
+1325 0 obj<>endobj
+1326 0 obj<>endobj
+1327 0 obj<>endobj
+1328 0 obj<>endobj
+1329 0 obj<>endobj
+1330 0 obj<>endobj
+1331 0 obj<>endobj
+1332 0 obj<>endobj
+1333 0 obj<>endobj
+1334 0 obj<>endobj
+1335 0 obj<>endobj
+1336 0 obj<>endobj
+1337 0 obj<>endobj
+1338 0 obj<>endobj
+1339 0 obj<>endobj
+1340 0 obj<>endobj
+1341 0 obj<>endobj
+1342 0 obj<>endobj
+1343 0 obj<>endobj
+1344 0 obj<>endobj
+1345 0 obj<>endobj
+1346 0 obj<>endobj
+1347 0 obj<>endobj
+1348 0 obj<>endobj
+1349 0 obj<>endobj
+1350 0 obj<>endobj
+1351 0 obj<>endobj
+1352 0 obj<>endobj
+1353 0 obj<>endobj
+1354 0 obj<>endobj
+1355 0 obj<>endobj
+1356 0 obj<>endobj
+1357 0 obj<>endobj
+1358 0 obj<>endobj
+1359 0 obj<>endobj
+1360 0 obj<>endobj
+1361 0 obj<>endobj
+1362 0 obj<>endobj
+1363 0 obj<>endobj
+1364 0 obj<>endobj
+1365 0 obj<>endobj
+1366 0 obj<>endobj
+1367 0 obj<>endobj
+1368 0 obj<>endobj
+1369 0 obj<>endobj
+1370 0 obj<>endobj
+1371 0 obj<>endobj
+1372 0 obj<>endobj
+1373 0 obj<>endobj
+1374 0 obj<>endobj
+1375 0 obj<>endobj
+1376 0 obj<>endobj
+1377 0 obj<>endobj
+1378 0 obj<>endobj
+1379 0 obj<>endobj
+1380 0 obj<>endobj
+1381 0 obj<>endobj
+1382 0 obj<>endobj
+1383 0 obj<>endobj
+1384 0 obj<>endobj
+1385 0 obj<>endobj
+1386 0 obj<>endobj
+1387 0 obj<>endobj
-1381 0 obj<>/XObject<<>>>>>>endobj
-1382 0 obj<>stream
+1388 0 obj<>/XObject<<>>>>>>endobj
+1389 0 obj<>stream
 x+2T0BCs#c3\..}7K#4K=3cS`g`NvurT(JM.QpO.M+I,r
 endstream
 endobj
-1383 0 obj<>/XObject<<>>>>/Annots 59 0 R>>endobj
-1384 0 obj<>stream
+1390 0 obj<>/XObject<<>>>>/Annots 59 0 R>>endobj
+1391 0 obj<>stream
 x[ے}W-rUn劤Xd_%H`9=3 lk/I3螾LO'..$+t2/~_2oM5ʃurMR#M
 7)&͊IIb@4\
 auŤ^Ni-[ʊB~r"C
@@ -2283,8 +2293,8 @@ h
 ![0xj&r;wEqWw\D5pgGԷ_6`;-(zm~9D8iUFK|/'ͻs'iAWgx〠1Z	BڠNU(l2FtG,΅mܳN+8BNx;ˠER;{{~ƞ/bTBG%G!Zfh7yސc{;~ѯi
 ˎo9>hg@DA66Jj΅ӹ?P~I3|o=xGwHż!k7ɂK5u&$kF/G{^l
~h7{\,G {*[Sc팳a0`ӝx(tpБ~ͥ-ޡP^/>̝To*bO:wDNJϗZå}Y=Qz-/!-sk3Q<ޭ]ߝZQvSqW/N2FIf)lA2}ZvZQ0VXC"$ᓮZrIZ+$\+X^Ϟq1endstream
 endobj
-1385 0 obj<>/XObject<<>>>>/Annots 103 0 R>>endobj
-1386 0 obj<>stream
+1392 0 obj<>/XObject<<>>>>/Annots 103 0 R>>endobj
+1393 0 obj<>stream
 x[rG}WL*2sᐏegK1E[LxQH*>
(gXUt7Fh(PtUQOA9.KK1if纨g8yhԍsp]i	ũ[ո8%qY9eQC欪$)&ITr6n86.rӆBG&rNsiֲ80:p2@60rͤǐBf:vVS6M
\/L&sӘntؖ-#c=ۊXf846Vթ\:LȅpLzL/0Ց-6a$1flXt `P(TdQ=e:tO k\$`ss-d:;RzBՕ)jUqR)
 <)Fz}0	cbHj,Gˉd'nʔf
,br"A0h.ؒCd
@@ -2300,8 +2310,8 @@ x
 k>ڛqcʜ.xI7slwgDH1$wpY:	J7MC+cz|t;\ze0|CJ6fӡl7vup.6ruBMfk]Fl/5aNۅT.WF@9Tf8x'$me?5Ixf,,7CU&ߟkez׫'Sk3kM׵N{
.7oAm
 
pEV{2/7e<Mݎ/*o
k>gR=6HTcԹrx['im+|Ao*T|k+1[s݉;n>|r"5|oˌ,WK
y!wGr㩤nv}=^IIg~̃wv*^~'11bg-@j2\җpuqX]TN#^o 0[?
~|"(nk2Q?Z%53$_Q|1ؔJex]ê)np]꯻M{FG1r>~~ke{^އ+?u˿Mrp+S	^yS8՛;yCz/x_uyײQ!x|>է endstream
 endobj
-1387 0 obj<>/XObject<<>>>>/Annots 146 0 R>>endobj
-1388 0 obj<>stream
+1394 0 obj<>/XObject<<>>>>/Annots 146 0 R>>endobj
+1395 0 obj<>stream
 x͜[Gr+zFCtG8lڒ^Ѧ/i02뒧8E]Kfefeeh5Y;LG1˿/i7zQ?p7yJ;bv6Nf4SŰl&MvANJa瓳m?hvz`}g
 ds8990
 ,J\RRn׌.b
#Lۘ~kSŦٰ`SD{k[:۸a-@Wagwzh)F]qnQuV̈́
@@ -2327,8 +2337,8 @@ WZLྠ
 mp|?YGOKLu\Z6QʪΧjK-;͋?/7/q>4WS2c'b97~*~U	}K'H㮈okoP~k~,9hydGje[\cg_B}k{؉r*E/=ΰ;sUb)EQЗLo$吴^$E'=(<${y!&zrʇPn}Hw8bS		R/SpM	-kdC	$ˈv/˛|˵`ףṱ?BխLLd*(\*}竤SyY~885ʒ^v5L~mz]&2b@ri9bwcYȵH[+Bzc>HQ""gzC䰮$-~Zs
.t`\]Zto]&QnS%FdlhA54]	D'
 ]R[Aʅ8(vW=H{^|vjf '+(>:nK)uAc(^~qgbbYM]UڗԽߠ=>սQFcևT[{y-p	?ny6X5T5RuPdPNwۋ%>kr> 9un~pJLB-i;bxcrsG{ѥkqy~YEx-7+\'i-)7uDyˣ=^,Nx<m$mo7듇=p]{;^mSb+	endstream
 endobj
-1389 0 obj<>/XObject<<>>>>/Annots 189 0 R>>endobj
-1390 0 obj<>stream
+1396 0 obj<>/XObject<<>>>>/Annots 189 0 R>>endobj
+1397 0 obj<>stream
 x[]s[}}Hf*XqƝ:Zʸ3M(?gw$OII;vbY
T+ˋBqRM>!AZTp 'md:[kX?
@@ -2349,8 +2359,8 @@ n]}c,,SCnaVKx#{5P]rdk?4pBq~F`?Ƃ]VFkzZb)`&uI.RlWxxlxґlv;KO&
 >wO{(!#LEL/j^ODp?<8})folVtRJ/&k|^t?.Ǔendstream
 endobj
-1391 0 obj<>/XObject<<>>>>/Annots 234 0 R>>endobj
-1392 0 obj<>stream
+1398 0 obj<>/XObject<<>>>>/Annots 234 0 R>>endobj
+1399 0 obj<>stream
 x[]w7}ϯxtMs4'}UdQkI,$VN{N;w8@AgE"ʬjY>D>zY5Lng.sp
դtˬ1خԮˬ,Q[VulN:eݤðCьl3naª0a+	\hWkj'E8%C|k) ,_R`#=vR65j|;eA4#=+4}%'
 @5I\_B&,a`ᩍc&-H0M"GGgFtܚVжsjl	JG`"E.:NsXY)Ҙ
"4lI&U(1DXb}Щċԩ4rEUp0>NۆNN\0_u*1:-[m:jj`[:|o80#F(+SrF23W9t1v'gvRw8.+jF-Qj(F{8CdhRC0r̞gzt{:cP76ضĀ]0F(
 a0
@@ -2372,8 +2382,8 @@ E(
 Iy拼5仩~hPcࢃe(4/M$T(Uߤ-Jx>ԧ=עcgS?뒄_lO?J;g/tjO
 9BC"bi5J6R1:7_[+'
ڪԎs<>nUn7IGVM36;4P`>|q&Oj덴K\N
WpV_Ɯ7\C^g<պo]`7>s|g9Bendstream
 endobj
-1393 0 obj<>/XObject<<>>>>/Annots 278 0 R>>endobj
-1394 0 obj<>stream
+1400 0 obj<>/XObject<<>>>>/Annots 278 0 R>>endobj
+1401 0 obj<>stream
 x[ےG}+m
0˚3zf/h#3fu9YUْ»uɬUvGy6l\deMF~O5U.d\du=l"qlnNjK݁,ņV9Y[8d1,,1خv-eɢiIdtRJ%=[Ԑ7ڳCCʰUgE-nXA(Anx#=-P|S=pV[(c۴Tmkøa8 e=뮁P5&.H+jձ6:L5Pcu`&nc=kcۍ3;EU9lc=28UtZk%.+XCmձDQ
 'E)1UAù7]{(17L3v`kzc8{0l*uÆ18x-6A%=
6OlX:4anX&^Mǒ`L8IIpUD4Hܫ@cPX\FYi+%" xVJc/{D8SAl^)1X\ٰ
k%##N$1+UV/͏贉5qb1rGzcaI1/[1&T5mф~Ą'6c,1؂±s4"cj*9cڒ'Xv
iQh于* })Ѥ*x1I%$C'eEU[
Iҁ%*2M9sRR|j60rys Tg88L@"RTnnj296qJg5d&IxZ*ڔ^
 UTѢ?Jxq.2cp2@c/tvFc=z::`ۦ+HFp6cFwzcYؔ#wM	HMU?O
@@ -2392,52 +2402,54 @@ R}a
 6Ӊ$"j6[OcS\ej|(T	#6_ͧfZB6CM*E}1XX~v=;Q-U;);o;bWg?S鋾]9?L8=Uƾ1|O"b/<^i+9	A0y"s994`GV"7{39|Qjvw9]\e9lѯ/0XNiDY\>C
zup^@oka]*o+T[h[=j*nqrF^܈/ISmyOΪ9Q@KQNd%xt=GVfw{Z%RwIj$:݇Qb*{ru~^vW}}&tMJ3M؟pf}ov(=0?[t
֟*]^+/S~X!5؅jo+"+Z7Z矾
O&;x
xo6u
 /Οz4>nn׼da7u|nέѿendstream
 endobj
-1395 0 obj<>/XObject<<>>>>/Annots 321 0 R>>endobj
-1396 0 obj<>stream
-x[Ms
W!Uq#,Ŷ*+[do#f#r!)}n4kQIծ
i1"45lY6$5c
-,j$IhV!qŤ2`lY`yN22"nt^\A\lj|*u#"!k0še
&qc0E欌LLrUAPq"r2J:eHL`Eϊ5X	(ƦIM*]ng2k
-8YĒ)9b -UXҰEd5lYbX6eꌃà`qHTQbyJv`XHeEܒ.,
-ETW%9l 
k0	&T$`r%6lxQe)YtUʩsKg X<8xRJER7`@x㒄*)>`41EX -Y%=A0(Ms,AĤiIi1؊ʒ[n9d
n0@@B@Y=gt~AdA7.IäCŰudlLeR $LHiX0`t3Y9BbE+9SI5IF2:usĤqLj(i1ج`-L֙Y	]@9DC
-~H$nW`
-
-,Y63ct\)1PI
-+5bk0XM29$d!q<,KC#OVF}?x	g;4VmM#e'ӗ'F#][J * _n!#l0!p;b#k&ɳ͆j5L*:UˊlntKճeu,)߼n*N'{?@;bD3͜f'1MO^if2zg4pu,c)rXU#ӱ}- CȢrHtծBVۧeznߢl‘Cknx-1?sUoxM[{P\wK{{Ka""Z-6q!
OϏD%uJU7 lʿD9r|O
/ZE:ҭ硝䉾&OoS;GqNMDž(ln/qeVsס}Q7Z-?5m9轾Zc{sF(ԾНU&
D{(Iᦷ
-rIMLpHj:pƚsXjK?㖿`Se}kʟhzWl%.ϲ]H7s-͆'P|>cGww]{jw(Co4S9VcmɅ䠷0#zlli뤔GS)Gg8<;KvT$%w]l*!8`x͉Ozǫ~3LH{'6Jl4/;.C(i8ĝ*7}hw@d1}wAQ͛Qwn^ZnIKҵ{"U& -N4vz%wֱ"j]{=
9{$+[C滇uX}]N٥G3z-ZΎG8nIC\O.vhşCwU!Em|T
B4v"|QJzgec7غtZ#J.7x-ۡ3?`2#}&6*oG*:o&^䑾n}Ί^8^R5n:Z*8]߁F]lIj+V|wn} vjqu:Rᇻj̥v.~P|!;4hMQwrM{ƂfwZ0s$_I\L&n{a/ͤk9j]Y;_HCZOW|"M̕3.0YKVu
-o`ûc
ŧ!g!8L}dN"9;mKPCk/gWt1/Mp4I2kw)Rm|uQ]o*6Hz~A9J§KQ|_ǏI'kmc_ZKmPs;Gnsw*;#i5>ϭ
`\/1	6:駛>Ӫ+g}*nۓ~yσendstream
-endobj
-1397 0 obj<>/XObject<<>>>>/Annots 366 0 R>>endobj
-1398 0 obj<>stream
-x[r}WwR4٪l`/zYKPr9=RŋT%<{0Y"MoYW|b:/?Г*Z*I2ppr$	IM1 b`O
-Gzl APIؼf6
-hMi82@Vd0cs"qbi
-FzL ;aU51Yn,[lr\:iJK"="'ʊتeo%K&6p
98!4e;@
-[H8m"Fz6Ƭ`oa=[דڳl#l`sU%{jzmRh$;oeh͋Ѭ<[d#kxi	=[ֳm(XWI1-FzP"ȊX\͈'YqDZjcV+\W+lCXÐ\r03"\,ރ5a(Hc[\cGulacc&׷#5<0K}0S7d
-c[T4%cc&sֱP:LG=[#53}Q&fxd:(3mI3,:871Xl`bHPz&%5sfcraǤǤ)6c0TUyQZ@U)rFzLSc[Q`;ań2%Z{i9RҔN#=XbLT]D5&6pA3%=VMMؚJz쥁KSꅌt,6kub#G_V~IUvi
ILDc&]jxXy)`uw^%=X>QŲP W-lRJRdIZ@TdRǕ*KEg~akoPҮb-F"1Unm0
'ΈJU-Ke/d`!sB3Z:L)lAX\9!OHJK	PC)nyJ90(BGP$)v$:FPpJ"I.6@o*TPl"HL9HBKHNEEm4p25Plr$t(B3iBE
-iDr
-*)B#G3PST\sBA}H9c>(,M
VC0ZC4{Mp ᆱbloŦp	@?n|ӒhAh| )~S!7+bAR,G<N~C4;zR
-qw/^&,gQ-JϬ"[gXi77s1^|D(ưyJTUAeV
]bSD]=G%5WV_BK3Hg=L㣾LDp_GE8%8h^`V?=S{8(=/osl,W/IU'2y}Mta\z9g7/M5oCTRUFWnk8
-_]Ae}EozN+(MG
ex6יv1}KPVYPml"rePՙYhWN ދݎ6As\"~`	}74C6؊D]
A&Z.ج
-j[ElDOsBJjtXCv [I^BN
=N#"yMAX{6.]rn-GgޜpS*utכav1e-87O?/)
p|/ۀX_'0^,Cin(v-bb*[wڶ!CdVa%w
8~x~) :	o,(Vvl1֥r&GJX۩(!ZZ{Jt_wwKNIZn08
p>FB_btdqf}|MpԶ<MO@ԇ>!q5+o|Z̥
-ktt=uNnJHƟ.8qdK--~]=q&aEC/V)k::8!=w-4jyOc}^kwt;4Jiw$7w%ȝ[dtc!?P[zw;r~26z!8㬚/ǝO(Z(\	~V|[y'-ZpЪ9ye39a9S\Z4w;	S)zD2t>F]vyH'R_،_a4¦۟9O7STs4h̓Jh?FuZ@Y$Aۡ4ra]QVBϳNv^cNO;Untn'i|	:雀Wn-}nJ,3.+1ғ-hG16hnφ-=
kX܍?|o"]N18L6?!h)n,Ε)*5.&:z]uU8g	)Ŀl:mj}|z7_KQ쩴+'es)\1n'GMt|nuLf!LJdө-W/c\q>͖z_%ūw;lr9ǃ/#"xʵN+&Y\:G_ٓRn9N7g d4>_{'|0hY6<%Ht9Am2q9}$||~XDXc[.ۿFiԋfR	-qsq}%ß ޖ/E[xӦDz=>oA[ş˖N+>oIw+|ǟ	z҇0	ŋ/Ҭendstream
-endobj
-1399 0 obj<>/XObject<<>>>>/Annots 380 0 R>>endobj
-1400 0 obj<>stream
-xXMs8ϯa˶,또MbP'ce=vIUT==?d+'Ew,p*5%N]a.2.LKFr6,`+*2Vˠ.ݢ0FM!VҊe,Ԍ9Z:NdyZ$U 9R]aiQhd"90"Ż"z2|Lg|`+.`k9k?4̇i1炜HW+N .cB~$980XT1XC]&a9cd'cMviA4q8w	,-cox0EQe,
-ˆ%IY5$	%"dԒ" iKIW>,sEr)dA8] V@NBb 
-un8IhMN
$4L&Z:v\8!4	H+Ļ3N J-TCexztvJxtawkN
-+]Zv.Im8YmPLVvx}j61Ƕ>㖄ytk-svہ<>J23?9sLZhm_Ye龸o1TE+7ƾVEVӻ@U,SGӟGԒ?>/Cr䑄_hxAEX.lf?nVAYhLgO1A=?_[j='ߏMPQջv76pH[oG3Dڇt)(?Ene?B}+PcNJۜQiD~gLPP+3!KwX<3'?͡WSRi:7bGz.1h&MGV>mwGfgQ2!0mKgCv֧Zv,wmS'Y= ,X9a%Xܴ#[fcϰLx'h+vU.Z|0`H!5
-#0M>i$@T~4mzBdsX-y5`~a
o)sgR)}_};4SR|5oMfl_?AOyL4ݳ`Y/q
-M	]$Z;`âDԾC`m\_O:&-xMd_30xJ
~!o޺e)B{i^}3o[_^@z™q|^
Xa/
-4Nޞ$]əYvV3*Qi[^ZP,endstream
-endobj
-1401 0 obj<>/XObject<<>>>>/Annots 413 0 R>>endobj
-1402 0 obj<>stream
+1402 0 obj<>/XObject<<>>>>/Annots 321 0 R>>endobj
+1403 0 obj<>stream
+x[r
+f8~dVي%f;")7"Fc(*}M*Jt氻4@c9JM*2ϏQ'?Г<ʚQ}tud<*Qi8Qڐ-QcY5lSR36+IܬrV@8fg [*CZ6Fe
$Nl1*#C(+)Leuȧ*N\72)(c,YX`7
c
Gi(+(Wee'+g*SƍtVXU2nlԤLvF*㹦@,#bY%
k0X̲-Kk0ئL!cP08NW@L*(i1<%;`UEp$Xݲ"nI8,
+yTW883K&si1آ7$P>X*J>" (aKlċ*KbOZЬZ=DZ4p"5c3!@^'X$qĉW8.IxLaXA9!ML',PD0(Ms,AĤiIi1؊Z`eIFAXqrbrx]g Y u,XR:qF'+(g_P9YЍKRr0''o1daL`_a	i1-L03YĊWHs&4"jdDu\MIPbY
5`
+[5b+3s8
*4!q
\=+X(dMmf ,RbhWk0Y!`|+"UI@ (p@T;"4sTdY!q<,1qƀ(vJ)N:&u8)r
+	ɢ`+ո1Vs`3	`͒Ȱ@
.j1Xج%9v(5(02bZܐ2P_2G	}1``:t,oLM%1E@ZEQ{<
XDHkxkT@Xgc²EX`%af1M q	?UbŢ0`RH8zlRA$!#3K"`R%-=Me@KUt(f$erD	\R`>~%eyQxIsfӢN,khZ,D"QZL"C`eR*ri68Ί~D@Zi3b`	VE-&;PɰRa
vЙ-AC`R9DH?$@nQbR5'֤/Jy„:G/@x|pPa㒄a:A
HR0_`fMk0 ++Kr`qi10wH"xf
3Ek0DB9+K~_eIrNCx" _bt/^6
+jR/Lbe"[W)[9L봶1o>WRJJH{u}5Rg]$Gʣ	x⺽Fmt-z_1
+~Шc78a/Nzoh0&@ѳ:m|컇e6qw_Vg&Ss?b)Pa-doZz5<	Z%$pL8.x/q5]
+Yf,yj&O+fWZMQ:E*ntKBAe}Zq6m=zl$|?$)N^:Խz_#D2#?_q%|^wػ=TEop)8YQ7}lƮy17l7*P;UŖ'4CC\;p[9h.M_l>ކm)ʁBlnͻv6kðd$v2駫Ք؇*:
+UˊlntKՋzgu-Mo޶cIjdi^CUrɨW+%q}4T].+l&:zXd3^Ϻ
<@D
+rW@t(G_ˠ45urV;ݴ+pdS2i=U9]`xEQ
nߢ#9>ԹiG=ĪV[Ϸh/=ikkh4<<i*mWEܵd3tvs+Z"ҭsN|DBOߦ8wL㴱NMB6b6&ӗèW->H6̤zokk
+'/tFU<.NQm>!i\ڿ)	郢AMPsuNJwi3PqT$6&8Zym
ݜ㊭d{EYsfzn'NvÍ[lӕ~57bޔ{xV:ĪᓡpL7U1%3MI\|9	d>:xuB6JJn$U;람q ;4M?f/kjCl4'
f\YQvo+|c持8<,b{
+-܎?5u]uėV}kcPzmv٢gP.7wC}O!^E]f$Ozw*G+$Tunun\mˮJ )WjR-OKE4wCm]Dv!hѾAfﬓgz2w[ZZIS_;=G*?x|e7tg5>q5n&t.=FB"M->.ߞ1}CH$uM75;^yg$r|g5YI|2}pv5v7=>M҉q
+TzCj>8J*`*6HzC998E+ӫ>qg=OJQ~
x.ͻ&Z,V­_^wM4);!:[V.Q7ٚ.Z'HN#.6⫔ᆾ/rOzSJf-Nsķ7=4#>mzcVg6í9{w[voOkJlN>L'oB:lݱ?L7=M
+v/_?
+
+
+ߐ?%Ί.Ut֍7s|BK
+*nMvgendstream
+endobj
+1404 0 obj<>/XObject<<>>>>/Annots 366 0 R>>endobj
+1405 0 obj<>stream
+x[MsWrUawO)lUE1c0tYKPr{-"J۷31==3ߞI%yWϦ)?HOh*I2=spr$5Hh^N-$UL'yx^2d :IHƳmSBB6*G+	`dȱsp`(Mx9q)`
=&0ت	,NJ6'Uk\:iH&ClXeElY7%8Дl
)DJD@BDiwlVY{a=[דڳl`s
+>:=ۤ0k0B1{6/Fl1زcU:iݨ<TPkxJi1caL]\j%=V+m:7V\W+뱺Xzmqa-y03"\,?w`1M`k`_6ar};1YC\RY\fTcr}CX
XٸpДlƆ2arn>1غi1U`k`adEy[yVk0ضYRP= Y/pa*1/$f\ޱø
ڨf9vmpAοQ`OCΥ1Wų4RXˤ/?x{:9ֻ~~+Za$4;ɨvorAsfzXO·ͮ{X.vA",hxԖQc-uiMm"|KK)$4HY:&nI-m𗾻b-/7)JBl{T
+kHjٰ61%6*m^Bn
.ng]Gpo5Z5M᰻@;{Ռ=8mr|[fNi0/^쫰=p^~ݰ
j̓V?N턯ec~e)K%%F+ub~>
+8Űlݚae1_̅y|X_/mz"p8NcX<{!Bj rGUCbc108ni/Z8,:8݌'i|ԗunOo	`<.8Z?oqڷOOj|ToCzKoK8WkpO]Hhya]QfBONv+($qL۸{SM(%_U'}ptaխk`wƅ?zT73-(Ɩٰa_x>A|?
r6Zʆ[d%˟r%sJ{(
+.RPu…m
+>ct|M0m}]N3fɞJ{¿|2:X{9S/endstream
+endobj
+1406 0 obj<>/XObject<<>>>>/Annots 382 0 R>>endobj
+1407 0 obj<>stream
+xX[oF~ϯ7=SPRQXij&vuΙqH	H|3g}rת.TY$r?ӊLU`ޜxPfVY@t_.pi"%ƥ։mJNezNEV"n=/0Y
+gyL%K,X9rWmjrEYbmdFBgb`+t`<˛6eB๖9B#j+xWez-)"' jDJ5ǣEImR7b^,$;cLɅ쒔A2s
K`K:(BI,
+U
+ˆg%Y]sqr,qK
+tRĸ,,7	~Sѩ?*'O *ˌ֐ae}
+W~ױ;u|ʼ~a;
i_1Ef*'%tcnVE}ŧC4;5yf㸏Y]јI=(W8,40X
+G.t]qmXA"cMH{PDzVmXb8~Bii>pb`1~9y0guj`h	ΫC-vaEG5oB֥_z[Ƽsl#>/XObject<<>>>>/Annots 415 0 R>>endobj
+1409 0 obj<>stream
 xXrF}Wt%JFLk"GD/~!		XTT*tO@%!E["H	Utǫ)^,\okG6xpX20:P<"h7JlQDak(e4Lv3å 6FAP0xqfޜ„drΤ vlEh5E:X*ȑ2%$$.bib߱A 1UIkMO	K(*1LkM((TM˅Mu"&cV?@97)d9NA({9Rc!V
 P
 E-+/MDs&
@@ -2449,8 +2461,8 @@ c!;Va
 K(8ɥ8aT9B~68iR9qa:N$.9P|nS\cq-i{*!w/?^Om`^77ueSz Wk!O6+%a~:|zMyr5㣌o7ӊq3<*Ɋڛ>{i)xOW/.?4y2쌼1mViU{}jWvnGwFySUPRPw[\osB+FWMvi
;cGC]?&Yj,ꂺ/sHM#rn)CU&uCc
XWWgjD[܃Tϭ'aKqER[C$n~nL5Oú*sͧ_PQУ(ȅCVu^
\ѧ6]3q@発M}U*o
in=T^M2{;{jD,K{T-B67iR]UtvN=5Yob>/XObject<<>>>>/Annots 467 0 R>>endobj
-1404 0 obj<>stream
+1410 0 obj<>/XObject<<>>>>/Annots 469 0 R>>endobj
+1411 0 obj<>stream
 xZrF+8>C백yΆ%˖/	!G;JR^o8b"zWW5 ~1<YX5g~b1b6&dŨ8M9S6[
 [,FQ<-LqAQCQc<%`*&vf
 
@@ -2476,8 +2488,8 @@ H
 ׃f1Yn(O!r~>.|Ӊ+ԇz#.bǹN}-mU{a`
 5ºUbH/.u}OYt,UWڍ%6+]6-U<&Mw'XNn;˲GG8^*_9n..\p%`8Gyo<_/E?s~{ٟbendstream
 endobj
-1405 0 obj<>/XObject<<>>>>/Annots 520 0 R>>endobj
-1406 0 obj<>stream
+1412 0 obj<>/XObject<<>>>>/Annots 522 0 R>>endobj
+1413 0 obj<>stream
 xZKsFWQZQēQYWE^EDBbВ\iLv+UvZ^$n7K]Vb:'O\IʪL%r
h.fYcTdY
 PR Ӓj9KY'%=*(ɼF'+
E2`	.
7c` jQq4D>Pd3rң9³!bI<$4L'+yq)%*&"sa-E9	Ns#3d9V0e	+lUecb$.3cQֻ\ػlH\>kXDV0d:Lm
 S8}Q`Y?bi`9kYQ*S 7.G/k60)T%\#Y33d+,ˑ4#Y`u^Pb;2Ab&
@@ -2494,46 +2506,51 @@ CfV0
 !5dCSX`FW\X~v%2ł
 f#+V?a־DDV14[0#1pSa+,69d}vҎF6Ǔ
XsfMYW	UC^qP1hdKa/3ULf#͊9܌Qwٶ̢H!sY0`%V1ؒ{FX`}UW~?=)[x2~P\R 84I.
tZ֝9s|*D.Bp8Sή&Le^gbpL,BXÆDh\P~8rœuT:xcqoA!n)pU#g#vصր!Đ-ø#[\\"Jj+L>u%Ns}jv~uWwWj}|z>L2q[}mhXZ4nu}cwn?^9Z-gƮc-dD3~鞺!D}=DVͩ1zjmor׾Ӈ{wu嵮v[;>ru[ovͪ{Qh[ۿ۽[u߶^5+wnnb⾴[<5Mѡfw~x'-?URN [Yqp	3 vfﺧq8ufF޷A^v{ѹ6\oWykaG(_Mkap~TeY:e%R2} >{8hݛC]6\v=8?}ja#ziGS1?PGԟNa<].sGB|koa/6}^xΗb>u52||&Ȫw̻=O!S!Kd|9#ăykapK󸍙/;
gu[u,=8G?d~Aw3/?Z}[GXlkKù9Q[4Dָp1X]qI2C"CnVD'-}>/XObject<<>>>>/Annots 572 0 R>>endobj
-1408 0 obj<>stream
-xY]s|ׯ؇T%yL|O)YmUHW,ܑ{IRWuޙ홝;.\l:'eEo\AGkpf1<	rêiMÔ 15le
;/qQa9 öE{]
ܸy%2	)H\)HY!(L(hb-|GQ- 
޸⬦}UT͙	AV8O$ZsYfP+r"TY+-V`9ͳ**܏2ƂT[b8Fdz͂Udzhi=fRP5,Bg
f"˳+@.%F߹0퉚8sPHI2~!tg2A	3r24o!8$+f0HYMb!0qdK @NDB<Eh?
fEW-wPjݪZMڭ9,rø/e.Uz}J[+uھ}܇z.~CqCWUmCYv,PC6*`	4^5C+enVkjxm{ZϿsNnM]︉H}i]7+
-)B7/{&SEiıv,30L~^յOɱ„
-ߏvvÁ_~kqC:u
-Ӓgܻ~@]{9vuzHSi9ot,W79(o}l%-YvC+)QoțX`ݔ+<*W.*WKwjo<.z-J~AKr޾CmrE:\sD}z{uՋR_GIٟ.G=]Zקȸ/.qWUШx+: 3\vU~_Gko%-\٬Nmq4c$Ӳl9]$]
gOyڍk+נhCg]lU(}}e}.Vnz\,Q)^c%BCK]˯'Ĝ>Z1j܋alӰ==TT]s:ӝM9ڰ"7}_7eWq0 CI}J4tZ17pDŽ<2De0}s[BS~pCJ&p ~pw_+n8@7WbvhTW(t}͢Cx oawn8Ӈ-sWj]Ab=.~7,Cķ?G1Fv]ۊw1z1Vp×78rHm#.?gsCg}Q(:&dz/glendstream
-endobj
-1409 0 obj<>/XObject<<>>>>/Annots 607 0 R>>endobj
-1410 0 obj<>stream
-xXnF+sUIHV5-l|${\YZ9=UD!Ed2ڶ0ӪL"ߖ"ьYi6+LNA᥂fVeU˜-q՘2(J9%A*PY]ya3H 5U2b)a	")6CX9X0H`5\XW%c)	G,H*n3ʳ
--Rʳ
-ssL*0⡆1+H
=YdI	37D$
-
D" \s!VyI\nyqRA"U)XNQAK9N*ISޗ`SAN1Ksia4	]!\T֔-]X'LD-xDu҈.z6	l}
-RrZ–%:+NhF.`a}
+c䉔	8T0d'1Xrdlr|9vH(CB Ot.oD8`8b8%x9/b[FGZW"s$^!Rt!5**y||V%WSr E\Y'#$6kIFHv1gsL1^X%V`{Y`=*ܒ\i5+j6b,1k-+ȯ-%`eܽ‡CRf9|4Z/MsAFzao%U[r^0X9Y9ņՖPᒖP$RApF2Ul"!{Vax ]*顎U-jyɮv@:Er+R:Ly9܌ ߻p~N.$P9^XaGv15,ϳN>:x=`H3>p=(Ub1rR+;UYh41XT8׬
^Mb]P0/%6|HPWջ[=9m-f€nL]ů.ԯC|g>Q|>n/DŽ7ts%m-T]Em8
TmaAV~#U=]i2F@dF퓝 ,1]_@T)j?d~yCrQ,e/mtl}.(DeDLmz84玎R>5h&;*2"?i[\p,F%W44%ꦡ'%x5v4d,]wUxƾKy!lO%>C׏Si¬ʲ;SiW;}z˜Wag–fJw%\~d蓝&hg
}KVD9Izz1hihs?is]?*^qgosN9n?ɲzJvĺj(ѣþ&{k3loՄb>WVSyroCn'o-v4Uf/'.|E-YFendstream
-endobj
-1411 0 obj<>/XObject<<>>>>>>endobj
-1412 0 obj<>stream
+1414 0 obj<>/XObject<<>>>>/Annots 574 0 R>>endobj
+1415 0 obj<>stream
+xY]s|ׯ؇T%yL|O)Yl%G$+HBH@CQUݹwfzfwgOB7?#gn93_NI0sYihN,'AnX5ͣi$M `|[7.J 5l2td[A<F5p)Br"dRxSTųCPPZL-,[Ab=q1b**`„欄 *1, `Q=k0,b5ggFdk1Xdbj>'%GIA"`8g85lSg
;A5PdHXfY0`qĬfMh!ܔ ОT{`&qs=k0bP,4YL}<&A\9r'{B1ҭaі ʳff5ae&[
>QDZxdb'2bp4쎬+s-G	$> yI3YGE=k0۲r&b)a%xk0wg1v!q,8޳qS{`ʊVc
+G2:p	=k0؂
԰#[lUT:~,`.)HDҼ=+)NƏ(DTF:҇2{ł4YN=k0r2`e|1H6yVEx-l,HE+c|00L. gMeH⬡ʞ5aeLg5l	Ұ\y`Ċc}zAHN5Dq̰F`dXVn6pм
+@!JkE-k0X
+bl0xbnjK
+{Y#JY
.rbA`8Fg
L`eu0 4)BjBCi_c Z)*t6$
`|5UsHE%4Eʲ
+2E9dCր?MvGBrļb]jWUW~V퇺Jw]/owQCW/v^prm͢7B
+n9m"@U3T߻Rb^?ouj_{Tk޻zxE8@rSo;qu]W/MÿfzED(hywi2,\+Bm Ͷk_`蠟ynaAۗ{W>M&o&Tqmm7+pw]=8ұS*.;t2
C5춨췫Cz;O1dK헻c.nϮnhsp"wvKZ-*7[@c*}jt_$[&zmԸî,2OmQ(^~N}s})c]fЏuSv;ENz,V"$:\rw1qw,iLH7(ݺlip:z(0s4)q΁c2t܉#nsv].u==8P_w_#٭¤JD\PK2Y*dy+` 2ƇalAO0Eڄxl!
+Uendstream
+endobj
+1416 0 obj<>/XObject<<>>>>/Annots 610 0 R>>endobj
+1417 0 obj<>stream
+xXrF+ `;(;vRe.!r(¢4CJUzz^D'<$u~Z&)+2n)J ڣM ׬-au18o,Hm|`2(Y'MT,bU2<0<#gf5fJ:L ԁM ̳
+)DgL CWK< 6E"5kb뼭9*<Ҭ,"3s86 ɒl6c<0"e<0'	Rź4[RClh41<뿮(	"/o8
+~kZ=Yڇ-7mgjV}߰D}մHUm=01̉; %mzwVdg;QN^XjCc=M:0/tN"۟GjO+,\y^ϵ92?ԓl7\+`U"3"i2=GC\Q~u'ː?i754/-Qr,Mv<%MuS,;v2.guGc߈2b~HzUT8UM#I_UGTb$c\Cv#9>﷟>ibOyз4@mU7\:4蔩GnVfq项/ nvK9cU?Jqg1Oșx)
;d.iO=R=:hBv }&p>3/HUջ嗛%}v=ч~k1mRT߆,7F-
+aw}k2^>endstream
+endobj
+1418 0 obj<>/XObject<<>>>>>>endobj
+1419 0 obj<>stream
 x+2T0BCs#c3\..}7K#4BHP$YSO=5/(1G!3$1''$3?O3$BMr=!)f \CT&lendstream
 endobj
-1413 0 obj<>/XObject<<>>>>>>endobj
-1414 0 obj<>stream
+1420 0 obj<>/XObject<<>>>>>>endobj
+1421 0 obj<>stream
 x]N <\Vݤ&&4-nZh6Nfgt
 B;1-=;vp0=YTa:\P=")Lَ#,l~di!<^	]る'S^)EٍW:lG}|CVjeX׺/b^p_lendstream
 endobj
-1415 0 obj<>/XObject<<>>>>>>endobj
-1416 0 obj<>stream
+1422 0 obj<>/XObject<<>>>>>>endobj
+1423 0 obj<>stream
 xXn9}WŎ-g˞H~TndKQ~OjGIV_rԩ<Ft90Wل'}N:EdpwE!-װuq9eN3vuPFLp6odPJ[/h4JǓloOgkۆ+096"7(J%Ef6%;~56>y:?tiOֺTx?i+Ek6Jx,2Sr8=6*\Fpں{6XiˌRtZzIa7u|9f0-ʈU5Ȯ~o8eG8-6^`;ayMG)ӦBR-rsacNh`R-5q4_ ""#V{Z)+|5]a(J8BbgCdxQ-*4Nڈ^6S;Z:Lea.4<;Oe`υ"-=Ha{Lt_wmCn ?N?>=N3ZnP4#n5WMS[M2>vT`,tV)cWZU&)؍Ε@C0xmY5:zHOo* oҵiE
 %f8ōZv8=xh~blKTrUYԙʐ_x1RCF(;~sF2pqow^(,*}oJj#&giG߸8~3ULry~u}>f5Izx.etf3΃@CK)ǥmUaضE}&Ue,ȷ{z+-LlwpϊE
 \{x\RWx%i(+J5R>E3_#+-I	[H	}⓳JiY!q@טqȩPqi3=M𤾠$3d:BrKYc^yS^)}
fqN@#)D੸Wp0sc'L2,E##z6y['r?MJ*eQ.FwKV,`wܥ( vؘܕ@'7Lw",N
 	,q=r)@C9$2
_wql9CR]sawH1
I
ŋ0KZ&o	+]0LΓ\M'oendstream
 endobj
-1417 0 obj<>/XObject<<>>>>>>endobj
-1418 0 obj<>stream
+1424 0 obj<>/XObject<<>>>>>>endobj
+1425 0 obj<>stream
 xXr۸+NDKJVWnE$@˚ARR'IO
cD1M(.Άѐ&	~M4]ElpwISq5:!i_bSVh5Α$ߔJoƛ3?9/t"lBL#cVi{JM)JqR4Axb͞V{/_Hig6p([i3Dn{8(#)FTK_(BAL(U9M8巕?o+A5sR{%rJ+s1S>NLe{'PveJ8o/HSӫ!0-ؗB^12quM%7.3U4˄'TK$j[J}DOkYƢˌr;<$v|iѿ#5+&3gcU+]JSI)R3vgrR?$~1f% Sm3IKz{Ubrm	cOt)7(qFG'--9T{=#QPՐAz6iC0LM18qDƪAnuI03;@2lyށ=CA׉;@Wa=c(իg3VhfWE;fe*E`v*M
 h94xqw<)Y:Ym$%IZn 1dM)i".np7ޟF]]1>ľ}y&
 ei}3h>5sN̦tb䘴^sHM`xXޞШS@QwI'8"e+J$GۥQ|O	hP8=@I1\yUm{D2	qX%>R@G+i_U,Bo2m=&cn[NO%_Ozm5\+ǩ)ԟ5PĐbh4y3aሟ'^6ֈ$λ>!MB=1qUup8BunfqQ!ACgnhwBa8」0O>/XObject<<>>>>>>endobj
-1420 0 obj<>stream
+1426 0 obj<>/XObject<<>>>>>>endobj
+1427 0 obj<>stream
 xXO޿
 =T"vBB+E	(Ii5'{	y;wl'
]VJs_终ѰGwݠK`@!{g%-_wO߅#4]4iB4>~@s.5rakU^
49Z(Y>˪R
 cECJw~uBZJiU,X͕);}8zt7ǖq-Ҋ|d!7F[cXUwuYهhmf̃K\*2Vʥ$hiLBRBZ<2KLTڑYbP1-V82_ӏt;{Bj޻*QVJ7t%	Ā,gLaXiMefŶM!:AgrZlqg%֔2ƛ7gș?ˀ	/&~:1`Kgmto3iMp0FV1;:#-B(Y'x-2Y{qf)G}VLaA!-T!>a&qK*ttGD@`;¥_l
]&Wu'3>X+m&|.
/O
}?x_&g7g>/XObject<<>>>>>>endobj
-1422 0 obj<>stream
+1428 0 obj<>/XObject<<>>>>>>endobj
+1429 0 obj<>stream
 xmUn6|W,eN_r)
 8q[J\YL$%)+P.rwvvv 	bZNiL	?ъ%OLYbOEf0[P&CjII3&p\FFE4G6Ii$ӽJq&MMʟ;IfVxw!%r^Fmd2+}	FcxMCلSQ92B{vGΤӁS8j*OF$PGIsM_Yv!c*^"L֖
@I
 .V>G7<
W%YSc*j!hle$ |2u@Ȧz0.r^LwRm/\~6琇e0Ҝ]2 MO\7
@@ -2566,8 +2583,8 @@ xmU
 F%ӊQ$v
 |ك\AQJvOЧT~'izݯgz	Xi@\qݾUle1`JB͇ެf45,؃(RfMg{PXvn~н؉ꐞx)Z:^sUj,AI["귗+aGygq0B-:	emv*Qa`CԊc=k+99'[iFTc䕮	oX	v/	_?}c.~i:6AkNsX8GKNpqj!eDlKZE-4a}*|wc,yi=0||3;L@*e0G^]% 4tK쫤P.$.n;mnN@.B2ӿ::*2v7>tLAdlw.Ռf[<]\ӣ5Ϝw 9_Σb	81s!endstream
 endobj
-1423 0 obj<>/XObject<<>>>>/Annots 613 0 R>>endobj
-1424 0 obj<>stream
+1430 0 obj<>/XObject<<>>>>/Annots 616 0 R>>endobj
+1431 0 obj<>stream
 xVn6}֮߯}$5mA}$JZURzgHI{iҋ
ȹ3s?G!M*ْr4
2nZN`J%MVݏN؝Ondl7͂9-V`	zD݊mO%͢M0;=]cw9<-ri^H|ውy8E:tU/\
yn
ŰX#0[=hvCє_ִM_DHFmeQ$6tͫ?p\o .nT;+=Ҋ2mBQ0E(riIgހSURLDTIU3iC*LQq(]I(&Kɱt|C($T!GjvI\.ZdzATI]
 <ʌ.5d'GQԵѵQAUϼ"ExLwo-2 e6x\ueʐCխmjU
 g
@@ -2576,13 +2593,13 @@ x
 \|v|*v5#
F/o159grTr4쎠8UF&̛s39fq}n@dyj𲖛Y)ik@K|26"iT"a>~09DܜX_b^k9/TM{)8!FB=r8ehNiK+8-/t,BPP|gcnt[w~NF,%~>o9gJ%[W?4y{"OiNuE0+p<3HVAoċM7 /Iu"l-AS/a̝LE56CtAU"ˑyw%.8
 "@K
w:0M'}l1+(B#ÄF"
3cc9$K`ܓں4G,sbmw!BF]w1ylr|p1.w'eӸeʀB>q37P]KЂ9X`|hs*0xsp½;
cu?vJ8Xz,PxўbtA|)oP~㏭9?g-:_̓ra>lG7endstream
 endobj
-1425 0 obj<>/XObject<<>>>>>>endobj
-1426 0 obj<>stream
+1432 0 obj<>/XObject<<>>>>>>endobj
+1433 0 obj<>stream
 xV]o6|ϯXZIJe;C\quhHNYR%)	(&ݝ׳i6l
b4&4ea3]pfS(=16BR\Z
 kwJj$A=|hi	k9醫	BVdQGNU^bK?nqDjO{oQ|頂†"LJܬ,‚-Iccس>pÔb".}OhnM)1ng}Iqj)C6lJ'|jl2H
G
tɭ&l;處:{N	L~RK+('{4ҪgkMX.ĉewQ[&dk,WG@RC&3{{s˩_kiek	,_\	y8h:8t*X&.T:t5|(b{u[D6_=iRؔeGl	?E`-AyW[>`I~(O]
Y`<=$hD_5Oz	GbN2(U뿯f/l>ԧemZ|>raލA)@xhlmc;*zD<ӻ3smdЇϢ"~"=2-ݍ]yV)‰R_ӕ5 WoLȌU^cPa6rܞ*vOT]/lZ>@mA爩UDZtLZ4}[7aalX=ӗ蜤K(z"ǖ|dS0s0U$7W_nWCڔqhư9SzI+|_f
gsa^m+tJc'2o}~1MMn>C$u/X"\~:$M
!_g}Aendstream
 endobj
-1427 0 obj<>/XObject<<>>>>/Annots 616 0 R>>endobj
-1428 0 obj<>stream
+1434 0 obj<>/XObject<<>>>>/Annots 619 0 R>>endobj
+1435 0 obj<>stream
 xWko6_q/MXvtCR'C6icoA-Q5TEνG)h`}sCǿMt2<'}OɐF	>֔`0'GxaoͣA?lt
 {cG{_K$g{g{_K8wN)'v?IN'8~1~J/oڀ9O'>-ңw<<_n^Arv;쨪
B[U
`+^|w2xv_@9-V~4sU{W?/vD{q
*GQXMxtk:o<)?%o*)
 mGn)
@@ -2595,8 +2612,8 @@ K
 Vh!{CFo%A`}@	t![+#>-ǰ?Bɬ2be!'
 Ra;(׉8C?KjKn!Rop;)+o`NA	ժtono.I>]ڏw׋Knrp-y^p0r#ͥ)Lhנ!]Hʗ#?jھe
x;stߵ.36Y|Л;h2J&i|_~-endstream
 endobj
-1429 0 obj<>/XObject<>>>>>endobj
-1430 0 obj<>stream
+1436 0 obj<>/XObject<>>>>>endobj
+1437 0 obj<>stream
 xW]o6}ϯoMF8v4`MC^BKņ"Us)Җ݆#s/4٤{?قf	~~<[K_.KM'GZ{Mxqf7G\j
 KqQbut6X髞9.w),*2,94`0BwNh@D&+Er:cZQ)u-+c5!rr۽zQ
*EéB2
@@ -2605,15 +2622,15 @@ nu
 Lo0v@bSh^h4fXJ#[9G& SE4
4a|Upu50K
 7'"uSM2I~σ(qK*"l<Cw.t+*>(TؒQC,XBw165^[T7~FͪՃ$85yOF3;~V0>lN2PNGH@n0*:
nd5-Ԭ76SJ7Bi\.h]$&;V018؍,wZc[HI|{*|~PIe`gk\{4[kDPՑĐБWݵ7*D\0{LpM@/6`I~euƮ(]Tnq>fpowdzJp/_e.;q2ξ
5(endstream
 endobj
-1431 0 obj<>/XObject<<>>>>>>endobj
-1432 0 obj<>stream
+1438 0 obj<>/XObject<<>>>>>>endobj
+1439 0 obj<>stream
 xXnF}ẈHŎ$JA"X+qcrWᒖ=h$;sbJ|Mi19$I2o%isq{E62*#Lh.YB֕͞[itZ+-	QGL
 s [u!	f
 x.ugn)ʵwW4sb4[$swcf-3k(aI_"͕yleEu.UEe}{iIZxx?PL^x=HDtL٣գJ%Շ$d%8d4GS)~Hk*e*޵؛!x&W,D\ڥԩGZ(1'39"[Ki񯠯w|,Cyb?-WK*yhvl
E.c5E;!4	~gs;RHp\t%Q+ZK<(~#ђk^Nh-Qk{ӆ\s7lֲRԊbmpag]w(	!{VՍ%UQeGB< He>Kq@Z^J)H鐏# p^*YZvLzydH[$Grwxjt]|EY=N|0 l2^]g+y?N\}N&iʔHpOi.tn! =)LJ^|DEq q9(zٶe	u.%a|䧐rY8jGLS]L!쥏ۃw.CٸZt谬"6W\ͮV%<G=	+SШ6)yZp]@Ucrm<@YD0F>%Ӗɥi0+[G
 Va DX1%}0IljDFmi@R\܀1ڒeU?pv<şPHc;7 `'3)6 ߂6HWlp`:͍V֍Us{V2d0^8ڙz9rnrpO6A0\i*˘vNz=btX䏆I)/U* 74ҺRꁅ 6uNϹs(DPx#Ƒ	չ75|Dԣ2(}s}C(	PAƫ^'R-^2$$$t?/ϛendstream
 endobj
-1433 0 obj<>/XObject<<>>>>>>endobj
-1434 0 obj<>stream
+1440 0 obj<>/XObject<<>>>>>>endobj
+1441 0 obj<>stream
 xWmOHίoMb	T&:jco-nk'Ϳgf][(yygf
tDiyOtk˃E2>钦s]`ߧiڣץ4)k]mSM7T84dIv|u2OIxqڣ$I'g4pbx8b\{u_&g{QcH#=j8t؎L m*#|wRUН
 >nzMHe!ϼSYs1 guvYE[ܫd0Hɠ5J]]d4Ӵ0+mIׇ$XA+Ux&8=*UhfDq[>y
޹<^Gz8[,.-0fG@endstream
 endobj
-1435 0 obj<>/XObject<<>>>>>>endobj
-1436 0 obj<>stream
+1442 0 obj<>/XObject<<>>>>>>endobj
+1443 0 obj<>stream
 xls0([Rڤ5eib-J/80{L7ӧD|1BEA
B
I(4'$%QXQ	)R0ȆU+N
R2$*+RY5ڢrQcBB4Qr#?#@V=7Q$"a8diV)')!w) Ak5G+AJT<"Ao	A2z߶ Y8R[$($!tT i[(~R0Q#GWbݲj7,9|Hg*z{Btl>%a)|ø6*Mo	R,yu^wlŤiבkYv~΢·}$h46->PX"ΐVq8ٽI1A|0g=]̾=zypDSYd"3Yւ8,Cmw6vm-aͻȷҾ7R9k|\9/wNKc V8슟_&r4['Hy;^t+tu}#[4uUhv񌘕\q/CH_>_}wU.N֪RkK8+s{]g@?΋Ƅw֐zlKWA8u1僩Fy5wB?Ǽ8-EGiLU4xx4c{ch:5&On-z}PcLc®ZhU=|+Q7GRܽfwR5j߸
Vn>_+;ZWk8FUo<moopnike+Z.VÓU=A&c8]-jt%c8~+̧it3TK!3n}-k	|*t
6kaX<ϴ2:R@pIa:^raGUP^VAk
@@ -2636,13 +2653,13 @@ y
 
 fwp@fX@eslxR&*1t,y]/գ'JEi:7#hqWm*>Trug8k"u1,Ku|
bE}x3evq&sqE?hRksm#jDGoXYfrskKj+N,1ijiy8F*`^F%ty>(.}"_O$Q΃nMa|=|DF-1	~Ħ8DA;=H+ͺ7eq1#'?V4C#yɒʹy>~eqzQ,quy+&ģ|lrgs4ޛසaendstream
 endobj
-1437 0 obj<>/XObject<<>>>>>>endobj
-1438 0 obj<>stream
+1444 0 obj<>/XObject<<>>>>>>endobj
+1445 0 obj<>stream
 xVN#9}+jyHIJ.H;;$JHv{pYM)w!a4$v9Uſ']K'Cg1?{xYIY8莺ۃ}=n)OCqVԬMΚ4&Jpke&)yCK-ԆKDq.I=8o;:7OIJLYM+kIr
>qMu|uiL(iҢTxrTJ81K]89M\+iQ5iHrυ䋗FsL)1—BYRZd@GjD3kJPxD'5iÎ9iHGYLZN#c\RԳCHg]( XǑv.`Vo
:IVJɈef2k煣ϯh6+:gn~=OqZA"RW錪<@M=Nf
9WT/9i@UijsxM^zwAG(72e:?g @QV0_y{yxL"saC+u`xiH9D
ĵs0tY#%kÇ W.K(@(=c?ӚB'J{I;7λW5mYP,zr!/tуz?3IҘ;6gh_Q@[7
 B3;\HPyV MoEI=O]AİOi%,k/tɥZaem >f%{nh_whm޶~V!rUfhc}SzhHU1G}A\GD0k}X!6(=oK
A?m)[Fzh}K!m5l/x!q	ER[,.y80NVY0Jx2~4ޯὤTn@Np-;ѤnkօO,X6
jg(F/ɸOg+^,>3I 9A1k֨ 
X0ڝuנendstream
 endobj
-1439 0 obj<>/XObject<>>>>>endobj
-1440 0 obj<>stream
+1446 0 obj<>/XObject<>>>>>endobj
+1447 0 obj<>stream
 xWn8}WpjE/liBKŵD*$WgHɱU/(93gΌ.&4ƿ	-4[PZ]1ͧdA%~OJ/hL8$7xGpdA}}G1s^,oh$XKK;U:7^Mb#|'ؘ,<$Y{k&+&tqhtfRI93K4yS-92ψWLATAД2'oZJm[{& NV$&5U-,劼	
 rX!'5D}ٜ.9{=!X{ǥ3W(K<"t,8՚ػt?ޜ;B$K
R1YZ'? WeIFm\X92e0>$3F9FJY*mK
 ORd6
@@ -2656,8 +2673,8 @@ cFKG<
 *\4T$#ѡqΆ0OT0ˮoċc@U5~9S6a3G wEfWG;سJg~Y?^jx,Jd=TŬh̐ҝJq&(F5S"8YMHYid2On}0FB=rG8ajjД7hT0C7Ԕ-X(aEV~Vh^=畖u(ҟX=Zݯuu5&$#;|U7f;UpT
 	@am䯕>E2^贃3+ב[|o«,Yt5_|Oft'
aqi:X_|Kendstream
 endobj
-1441 0 obj<>/XObject<>>>>>endobj
-1442 0 obj<>stream
+1448 0 obj<>/XObject<>>>>>endobj
+1449 0 obj<>stream
 xW]S8}WܷvH#QYADŶ\I{awZے9犟!/iD' jCh|r',/c:`(1gS6_	+k蔥6yo0hsY[p	f1`+Y^}::glqo0q00#
 |yڥNendstream
 endobj
-1443 0 obj<>/XObject<<>>>>>>endobj
-1444 0 obj<>stream
+1450 0 obj<>/XObject<<>>>>>>endobj
+1451 0 obj<>stream
 xVoGbTUHg;vRU)R	i1e}w^}3{wM!̼yǗF|L۳Q6dӫ9~kZɇt͞Ϯ׋7X!jN`4E1N/_.>}8
 7
 SKSPtTl]k@'cKtqcc@ÌhO1pR	CpPf|C7n?UdVԸ8ƮIYiր" _fm ‘-rUdߪؚ>1(Ok_%P^㮝>{lu|]$5m4r1ˆLÇ=[G=]8Ft ca?Efa N|;V~`gyCɾ`wBqٷdN3*{V[b3DuI+7@8grYqzWZFsg%8gKQ{_\ڛeZ]ȍ}tlXѠX$*-NTUoO)m]@no.U♈Ʃz]/`poA]4΢C_[wNajك[7.h	?&PE%i e/λ.JPb(}P7WF3\Eб'*[N'0|u~bL5z8d{1E;yW`Fl(xWB@XUo,d伛웁PI[y·hddGNLM6xJB;1ڒaR?+A*_mepNJsM.ӴM,Ӽxs^7ՄfQP^{
 (ZS%EY:nd0|gW?g;9+endstream
 endobj
-1445 0 obj<>/XObject<<>>>>/Annots 633 0 R>>endobj
-1446 0 obj<>stream
+1452 0 obj<>/XObject<<>>>>/Annots 636 0 R>>endobj
+1453 0 obj<>stream
 xX]s۶}Kܙm꩓F>"A	5IhYgRe3d:"^4ğ#()oN}xu34[̢!4M*<EW'hF,`q1Fu0Y77Sxyi:흫~C6OEi_3LڃrKce])(lqҘ,_	=yLi$EL9C:f\`$,C;Vdi\b+tҙ2lzO
 ˏ͞%@sۙUwBdFVS9#e+ˈM7iŔ2yJ	f4Ilu.tm!_h0=[W6ES^B=$S#ov幘FHש!/'&4T,ϋCZBMYKvz؄H[wJԊ0t)y(;Y[6ϫ8=vr(+)dqm3L>,oi3wb\q*~ӯGTh5*+,0+<#7FME>ӠLvq9h|OiEaY`eqlG\87v_,>ݐP[27ᦣ5
#)IrtJ}@a',zNy枇w9{uۥJLgA0!lB	C3A;lŸq<]Tz/?%SϸdtuV5
qB	>X5(z@!V	F߼K6{v, Zc\=WO?-?0!o?χ7s'|ј_Y	uendstream
 endobj
-1447 0 obj<>/XObject<<>>>>/Annots 638 0 R>>endobj
-1448 0 obj<>stream
+1454 0 obj<>/XObject<<>>>>/Annots 641 0 R>>endobj
+1455 0 obj<>stream
 xW]SF}Wܙd3'6BB'ʹe-
V]]v8s>M4Sl}'4>gFq4>4
³N&80럞 :§ڰ7kf{4[ ɄfGMՊl."mΟR
3K:0"+	yBw2NܮTAN[I<7B[,u`9ЙS"?iHM2
 !|-T̿\zLTN.u]>
)t|=:(!p]
 kIYZ'JKBg0
@@ -2700,8 +2717,8 @@ kIYZ
 D	qQ0X~ wFڐ@wmHPFFk._myhr=C".B;/~%݅(\bs#8HACKϮN5^>ۈsm]xsfak9@`09PYp!b6؇8?b&rQn+z.+[!~ܘEm?	G:B7\rJpB
 aUjo>/XObject<<>>>>/Annots 653 0 R>>endobj
-1450 0 obj<>stream
+1456 0 obj<>/XObject<<>>>>/Annots 656 0 R>>endobj
+1457 0 obj<>stream
 xV[s8~W	%3`C-;;-m¿OoLwBb}I?>M2ق|04C/ys3?_ffު^dt?-sZYOSon_-瀞2oo=ղ*V[
 b9"1ݢldv2/za.}l|
 Z۷Xv9W˖^+}`oP|LMiEZMi"ΪS3:YʉmgܥA|M4
hdx	Np-4~M;Jw=Ԥ#`ARj[O+Qݔ\[P`"f_45N-5߯?^)̅ވN3
 ˃fx957ґ;~>܈4˹\ƒkf?3endstream
 endobj
-1451 0 obj<>/XObject<<>>>>/Annots 656 0 R>>endobj
-1452 0 obj<>stream
+1458 0 obj<>/XObject<<>>>>/Annots 659 0 R>>endobj
+1459 0 obj<>stream
 xW]s6|q]&фƳ)^k$h8G.`_]`vsOe._h0uq(K/Nzw}E
 T^$~>-"[X6ooJF[W\ҲTT4e:|iy~tҧͰtX1KDY/A$6bYDͺ8oV~t.hź(dTa>oLY'#Yцtqr
BХ4UV*yO	g;4(4]xX֕Jagh
4U_A̩KL^$-@yO#YBeAb	TeNRau٩TrKRvDg&uU@swowZEBoJK(Zpw7auS~r

 LK Syxn
=FWYBN},k`c7#1֙a"EF;6j#QI5D8{y\p~%ث^TYG,[ǏI)> d=x;M䌔S$![XvڈȚ,3O@Pi.:?/p)u	s/P?k+X
@@ -2719,8 +2736,8 @@ Z
 ፛m0I
S*`Fw{Z 2v\P@ZSj~cԉzhdZJ#ȣeX?`OD&anjg>Vf=.D1isq?dp䖘||׮%I;#zC, [ZKoA/)Mo8mQ{ţ!	=P*v:38lpȥb7oGg["^F߼WS
 +#37ߪU
xl:0Mke$t*@n'D쭍a`j-&6ro~'yܤ[W<$Mxn@wZ??cdw8\}pendstream
 endobj
-1453 0 obj<>/XObject<<>>>>/Annots 659 0 R>>endobj
-1454 0 obj<>stream
+1460 0 obj<>/XObject<<>>>>/Annots 662 0 R>>endobj
+1461 0 obj<>stream
 xX[oH~ϯ8JBT
M)I
U#-0cpb{gʿؘ[ETMws׃5E6uO^ͮץNm$|GW>G[סZ͎#-WgjhBAߣQ`oȯfU<̒En"R( SCJ"H4&&zki
 3LdR(\hPYkz&&5ZG^4-=͠)MpY,PűZE)WgTӱ\ݍڛ"~˴@ɺEAzHu.	gK6IZ^4>Kr#aLOp3?%ɍH&k]'s汬<QzgMilP
 co:;h7QPx]ppMz.HIHWyj&f8#5C>3U|̕p+rS
@@ -2729,39 +2746,39 @@ x
 MYLyfD{jqLĝo\вyT!ovCpk/r
 ysQ,-+Z,ÿc+G>~}	H#",Xf+iMs4
ځICT&[
Dr2[9Vo	b}& [RbKV	O	d(ؐlsBUu$›2lϘaw5~_Dؽ[G}|DnU]g_; z~={huD^|~G7h>^@Bǂߍ:K
endstream
 endobj
-1455 0 obj<>/XObject<<>>>>>>endobj
-1456 0 obj<>stream
+1462 0 obj<>/XObject<<>>>>>>endobj
+1463 0 obj<>stream
 xV]oF}W\EJ dd7[ڪ`f3ΌЪw<8!NvmA x=ss>&Ǐ޺>Z<+%1,20XSEh-ٲTh{PZH55E6K2LSQr
kVfoGRb8ZL/?š(bKJ9X^xdgh;jC!ra-0k6j@AcƁiv2^Vc`4XAu(	JdQΖ4}؟Y8
 Ć0~n~@B"<LHК*($-GDY)hrV
 s.ʋ-F,7?LLYu)?sJ*ϭ'sL9@
B:M["y
 JnFsZ4qQXW$Ӵ"lj˘)6¾v<3*@^H,uܵ;R7GT{1;Ϭ:w`j{'g0vcJH4q'0QKik(Κw|0O]xZaXa+{\,>L.xor</*0~/*yjv]'1(,@'ȍƓߏxzl7nwM|/$WI!r)E}?^#TyF}wo4L}8	Fa
VDqMS]|}7UgӂmX+~_j@;Kp#KjezV\
_~g#AX`5v#ckER'OǏv>]bGUvlj|͢DaC.~S<pI%)2W}/ltNŋimw]{nSF'??fjĵ6^PnTϘo+rkZ..Z72de5z3=5Qs>/XObject<>>>>>endobj
-1458 0 obj<>stream
+1464 0 obj<>/XObject<>>>>>endobj
+1465 0 obj<>stream
 xXko6_q˖IaH3-bb%L(5Ϳ߹ȎMVy}NBOH1Mf'`D,b1~sI`C\,5\31d)-]!&F`ͥ(Tb+)X+OAvJae9d"{z0eN>#jI"e(cD*-iZSbrw82L3V?A8sPdW3PR^e@K؞((#.ҽvCe?tO
 2X	乌#KJ+GqT56ϕISǕWu^E>ҿ_]ln-ZVN="&Y:mVAk{QlZ1}"`!m,Q2K8*K{]nTFZD;K֤6L%T(Ѻ,\	wnM^"3:Ix:
9~qkX5TMʱ9{GtGɡs#i:F5_=ST*)?>pyhq4|63
 XڬWZQ.nOhLB*Ox
QL"$?E]"E%+i5]!ҽ0Μ8IyLn4nJ#!glB1&:bQ$Z6/ub}M$lY0bgy,Lm?rqaQ컜=m"^>rqi]PkS!ڞ+m2ͺR{73sWCKc}F.5Qa;qVN,vAUsUbPbئXb5ݨ]+2ƤukDAy	.x,v,p6ǔWZsHwwjm#\P/zpP{PVpr[N;{el)do&y[UruZy0BķCa]7k1qIjnVdW#%lhx
U[&#?>?72SQY;CI~Xbz9Mĸa̳90^0v-OJ;"z̍	
 ۷[sg5Kq|"1Z.7Xx#Jpyrw{'MMaވ"6F(H+~QθgNszY[Tdxy">/XObject<<>>>>>>endobj
-1460 0 obj<>stream
+1466 0 obj<>/XObject<<>>>>>>endobj
+1467 0 obj<>stream
 xV]o8|7;N^i9H+-QItH*}gi+\rD.S}h8(oWF)3b8c/>0o]	bLfx	ͣeTDZtV5~z&JYtEdk'cjlh_z{1
 w
 CQmݜA_gBLˎy"t)١>-:W^P-4'NkQ48\(1:о QYFؼ|)+Rqo.o?1a@pNaH-=l
 K4'D+o2gbmaHSb%=O4kz$@RҼV#g0qn|2UZ}vȵI@暷C'|k3`{*My5^7Mϕx`U>}$C_S=uX\vp|蕥 \\|XGeQ)AUG"2rsLQ=?f!}$7\%jeSA/y6aH)EݘjXzO숗?@[6BRab8SvkmwAg5u@ЮC9_Mpz*V-g~ǹRYJG+?JcP)ۡNstEbwG2?t61ypCS{S87_@lj3ⴚ`?{ixxendstream
 endobj
-1461 0 obj<>/XObject<<>>>>>>endobj
-1462 0 obj<>stream
+1468 0 obj<>/XObject<<>>>>>>endobj
+1469 0 obj<>stream
 x+2T0BCs#c3\..}7K#4BHP$YSO! U!?M!3$1''$3?O3$BOzs=s3-!)Ɔ #\C&endstream
 endobj
-1463 0 obj<>/XObject<<>>>>>>endobj
-1464 0 obj<>stream
+1470 0 obj<>/XObject<<>>>>>>endobj
+1471 0 obj<>stream
 x]N0y8IZphyХ#:#IR!$d[O4b
 I
10
 ~;8W\wOJ>-cKn;=ؽq0;5`|%DRq|>bJTq	aB`KItFYmÑd#*7yOOC/]nvf|E|ȇZTendstream
 endobj
-1465 0 obj<>/XObject<<>>>>>>endobj
-1466 0 obj<>stream
+1472 0 obj<>/XObject<<>>>>>>endobj
+1473 0 obj<>stream
 xW]o9}ϯ;Tmm&bfx3cʿsmIZi?D
 sιG]hܧfоg%-Ao4~y~vֹ~fKitM/-]Rg,%MdHw1fE3vZTy+W5,=iw>^j5oȯ%,+o\-q&'gl-EQ{^&2#Rd
WјNA֔BilF{kBfV)=ع;d뵻AUC:>d^dO:;~{<UT|N.7B5SH0Tbֆ(Uk&Ɩ
 |iejj&ܐTTExtP`zf+LRHhߎ8`yg=q{ĵc&(QE.\F7j-p:uKȒ6lU.0(HTJ{	RADI爳QiBձҙbt"аb+T!ƚo'M+#Ta;:%Kb!ϗ2^fkaa~WǖCCBȎJ 8 	|g)Pd:>J7mk8r<{&^TT.CTo%lk$y~0E,ZU2VHhНPҳwL{΁;rk>/XObject<<>>>>>>endobj
-1468 0 obj<>stream
+1474 0 obj<>/XObject<<>>>>>>endobj
+1475 0 obj<>stream
 xVNH|+x
 1}aG*^ҪmNo
r.Uuϓ)M3ՌKJ˓I4th^<ܸMG7E޸O..i:8GzEqFH0P!VYzcHOo/^ϖgB
 'QS.-yC~'!29bjt5oD[U
@@ -2786,8 +2803,8 @@ x
 6:5
_Yl97޿*eO'og-w}%
 @ka8{onpMqr[b;D2&̤  eONXzz؊Aۆ|WwU
}`" q׫782ԮvVEs{o'P>=$:$7ĀDNF?nX=٣SYWv.Ds8xcPQ
~kΆBVv=pI	$
'xt_I/$%9]*07؞-Y/?_&W>q-Vh\x
=_0'5endstream
 endobj
-1469 0 obj<>/XObject<<>>>>>>endobj
-1470 0 obj<>stream
+1476 0 obj<>/XObject<<>>>>>>endobj
+1477 0 obj<>stream
 xWMo8W|N$v(b/zɅhD$o,+>m&͛73-t=Ǐ״/w/7g.|X]\z
6pX>*'8'ғ*׊Tl>y_8IW/Wafde2@h|Rܙ@Ag8~@MBU+4M.$[֘é1.ׁ7kOәG-8nwb:ӧ_k
S_uqj&tWӗ8yRE$0FRBT>wxZ}m)v};rpK"@F	nS3َ
1MD^gڼ24
POաQop*:R5?GMLsuXDV_Ѻ6^F׍iUUީVʇ
 <-WX
ͅ
ѻZXsJs*S̉^(^)Ժ@QN2T?)
 d.Ύm
wpeΣ!!H#7Ƈl
@@ -2798,16 +2815,16 @@ x
 8#l#/n)QDuų==V`තc8NGH>Hœe[@Iĉjk~6d;]+NkiPz͹ ͊QKVҾR'nK dN&A,Υ,rw_mlL!bܾ`_h]w~&F߇QO[Sb MxSqV^Wt8wL,n-͌6uj1cJ.[H޺ė?wU|LSxo[,IGڗ1rhqfB	`]x囓fu-oy_::0K"
 7X䁱k_05
fz^z8.yٻtxHXs..)endstream
 endobj
-1471 0 obj<>/XObject<<>>>>>>endobj
-1472 0 obj<>stream
+1478 0 obj<>/XObject<<>>>>>>endobj
+1479 0 obj<>stream
 xXMo8W|JXv!mZ`(腖hD$
Iɶܢh89o޼ŘF7nfWlD"t1	~[Oiƕ
 ш,g7=I"-=Y◼,xw8'EYi⥒/
ȥ[KuOo%9QDXț,/'8
7ل#85vRSa#:Gz@Q!]nJ$7/3#֞WDJ^¹EJΝ낄cf ⠻!jt==e@'񴶦)aL8Iŀ\xm@';GZx3]@P«EKOzx\bY:7eMCnkʘ9hl`dUvp'AHW/2:M1[b'1{*}ń
ό5?sM.unu	%£@Ws iogfz=v*Bm!CW(kcĭxjUC
 $Xk).W\#P8Y+P,WBpGEϫ{<<HVATUH"]C4ZGFY+o\*=(2}@"gУk,:3VBX\Cx"]IzFRLn>!lQ]*
zH[#SiYraF)$Ĩs`Dl^XBazTƬHcñÒ2aeaZE؂(PI`9N}n
6za_m6;L_ypt %
`08^sP0a'8Fe%FbX˪Ĝ;#*)%zLNyǧZˑJAA$hTb-ze#9DfkJ-?==¥![DONo'ق?ҁ۷h9dT9?NkG7kH?}ASv]e_xL2vM	l_^50Ԇ +vO9jsυ\`o#VI\hUXS\V)*p(hXjJW+Uy6Qteo1q͂1<-,gREQiE11x`Ӈ95F*SI@zKʭqfgP~ox(,j!/k'3Pe}]/涒"lQy(4}͠qe12Ww.@x!.`M9ye
 ^Uc,	Ⱦ6MZH&QATαS@)>w*T~cLB
 ١4ڶ-a쾩]?-@
ft;^,
J3l/[1c:f"Μqy5$0endstream
 endobj
-1473 0 obj<>/XObject<<>>>>/Annots 664 0 R>>endobj
-1474 0 obj<>stream
+1480 0 obj<>/XObject<<>>>>/Annots 667 0 R>>endobj
+1481 0 obj<>stream
 xW]o6}ϯԊx3lִtDl$%)'=d[mR[ǹ{lHtDʫA6ןg٘*
/%i6Oo4ƗlDc%3Oܸf׋1
X!lJ"8E[aՔyV6ŠJziBRRdAгO$5\-ɬ҅yvtByTo6yհ_^"En?+U{~N*v	v0FD^JaO1U.2:c_9Gc0z,V|Go(xOi/-l4	5Ǿ?r%\TKAϪ,	ܺIe6O=HJυb)\Kir2<sѻe.պD2Fܑk^AtA12ך1Y"+C-e!PK<>-y‹}J<zHIm~Jt_xFlDN"î	ƃG3cE*kb쿐$vMgt8]U;ϝdċt]-h{R7ױf=dQEжGFVE=;㙩[99.T$ݼ@1/=4rA5>0]dB%vR;m"H!XfeM֖ۯaHhOQ:nFC#z
 vb;>28}*k@yU%7"(,QJ|EFCXBvMT:Z	U>w{j,%Xd 0(sgReCzn\
 &l
L8iXptu'4iJ=6HZUN92pZ$f6ݣ?-TnC#16k 8ޖ3jǼMDɒ6ooFP[Q"#w@&QXPAo07lzccu
@@ -2818,14 +2835,14 @@ x
 h-C1d})k,nuNk/oM6\<sziPt;f!uMCRYl?ɤ..1[h$_ýF31vRLDDb?d͡2iraoEuD(/S{ƐD'ZbhT*ցСq$"Ap!<]~p0CpL?{5:SX[E4PJ酴*lhǕÐjRM7pRܭHB8ޑVOYz	^hg4/5-}&΍
 ^I;dm[qJqendstream
 endobj
-1475 0 obj<>/XObject<<>>>>/Annots 669 0 R>>endobj
-1476 0 obj<>stream
+1482 0 obj<>/XObject<<>>>>/Annots 672 0 R>>endobj
+1483 0 obj<>stream
 x}UMsF+|"[A !HU$Z&k/J
fXmdׯ_B7IDㄲ7
 Fxr[/ALqZR<+)fAgc6t7pϦETgO7\hF)̈ҬO폕YSLRnJOKoDpi~;2wZ̖?Zxdeu|߱pSz`(<^Rc]_ݑvM)uMNSn^IeYQn"Pa2QKPʌ+S4	:sW-(Eav=ar@Vꉾ('K&)jȽ8*TA$JL$ybk*䜓Yw\-ZAz1I춧\"oQ/|ݢ!G]cy+жC="j)20$IdiL_}}2k=C
 ۖ%b7
GZLctJlkY|/tuob)AE~>א0Gyx4go<>whJ;mӵ&FZFaqWɀ?[гV,8zAlڱkH742
k\Ni00Zuޙc1P#O/OF3`B,,&YY׬-+}j{=6IWPзZ)}B|;s0PԲh18ZGnY^fKYnPU;h1Hᆩ5Qe{q@ro
_5ShaF!{@{IO	\5u&%ҫNlL^cnծssp<R@rDa,Qlg·u!]merϞEC+\[޴
ݦcߏzse^&s:do'%$DXcTendstream
 endobj
-1477 0 obj<>/XObject<>>>>>endobj
-1478 0 obj<>stream
+1484 0 obj<>/XObject<>>>>>endobj
+1485 0 obj<>stream
 xVr6+譊(z:7?+eGk+|@Hš$$~{Rdoe˶̠{zvR'IF1ɲO4w8o_hJ$"M82+ݦ#6s9n)|Ǔ)sB>>gWkQ{eiУ(#Q|Hߺʞifu)KOlgצ+SykBY;R$IPV}h%r]!is"$c>qWܙ
IF!_kG2ՅNQ)
iJbQ(z~zOlnbK](GN٭xt\$|
 6/
*DOD^J;ưνkiwצׄkѿDt'c[[*cp+Ϗ[z$t)ʚM6Yal|+x
dU
 8PܡUBy`[Es|dnavj]b
@@ -2834,14 +2851,14 @@ pL
 >hUT-p@8
 eIO+Pɋ¼0J"	SW.P=-/X+FG.r
/Z!:Ɩ
*~4lܷFs9ZؽNj;XN
28D @GOg:QɑڂGw??%anC}N<}zO?Fh>);նBYgǘVIoj~$ӎ̢7WlEa
 nzU5ґˀXT0qq`HS޹M]cAcuװ18QPgKtOF-N=Ha@{JUJP|S7tek-hXYQ:.p;P=(_Ӂa-5,&ލvǫBКEb{UQoB)ZX#O1olu`.@<o{FޗB0}`BJ;>RQ`inj8GQ,K	!a+ ,tgn2;ʒt0aÙa2O#,sys;Bendstream
 endobj
-1479 0 obj<>/XObject<<>>>>/Annots 712 0 R>>endobj
-1480 0 obj<>stream
+1486 0 obj<>/XObject<<>>>>/Annots 715 0 R>>endobj
+1487 0 obj<>stream
 xWsF~_/%K2L'}hĝ>9H:;cҿI&G۟D7lLqJE}!i$9_in?޿>GAJ`L5itDE/J,ȅ[^$aE3
 sNi(J'b%91LzBlyq^E1t{j`^oB卑?q&'^A97bX-/xbe>xv$K^$COSqbN!^H9	Mؿ&ryfN<ɃP4&Pv	ID;vxqFXf/'%OspHtԀŸqxlLKsTYYbIڂj͢}J:]TeQ 诺}JPe8jtUmY=<~:	ÍSE(rݪzK6YwAku_e37K7Sv~.{*LS蕳]O(BysY4~(^Z
3]kJ^ɐs.LqfQ"*ZS2RZx5Jy`McT, y_9֨*@[*'**tu">Tppڏj{-9D<4ClMիJԸTӃ\_>>+3SG3JE`^(,)w+@J"=睫黷zЛݷf:~o{ϽyR٥YWsU{1*S
 Z~(B?U/iO;Yz[W>hI̎dgv:Pv4N4{փN5ZCƖ\'r?^75ÊgJYR(^_ek81[{]ŽZʴ/_eMsw]6Gz72y7b}(n;}njͼQxkbgKKSZ[:iͺ+]mujowfc~3[^^7E{uhKA)uUIDC-D-۳3I%Rn#^>9H֟vQ)v 2;xnGkێYG*g>>iNw;"85=@38p^}Q+~(E=aa:(HȆB{nQ})/C6YjT6N6?oO/+r4mcn_t2WёQJfyt5Ӡ79úLD?qt)+gt7b0YTt,#eiҼp''1*鸽%k'2ŚD> 1g!%Ydi['RWӓ?Nendstream
 endobj
-1481 0 obj<>/XObject<<>>>>/Annots 714 0 R>>endobj
-1482 0 obj<>stream
+1488 0 obj<>/XObject<<>>>>/Annots 717 0 R>>endobj
+1489 0 obj<>stream
 xXrF}Wt"kHole'ZM*Jm
!9AQܯs),]q%[)Lw>}_MiSZh$zŚ?go$mvv59ɚJ.&+MٲzE=M6%524kn#0tY+}Qoigt[S)CHU'J=|v70p"F#EQVѓuQM-2:|MSqF*Y$t]-Ad{UIM鶲޹kU[߉sw4*Y2t7΀q	Kv/,_ohe]Za`C{)c$9x^&) x*:=`E[.L*Bسh6;Lte"cP!ֻ!l!HHnV0=ZՕ5(Ihåu){-[#O\TmqtӈRr
OTe)8Z;dʆor^ƾ$B4L=ų]=>/m~1}iDw5U&29D#=6`+i$T27G*3IKזj41YfDe*cL`0;Q!
((p^#&Ѝќx#Q4ڹ)B6&+>QɁDAi!)H"\X\f/"xW0
 <`-04xZo<5e=~ET^]E)E[_wר,
dmPgv-
 Kz^պwN n	j9\S,.w|B9#Zo(2W KAZ@/ο*
@@ -2850,8 +2867,8 @@ Kz^
 6))gOxt;KLjC+rQ_ܣx/1
 J
_@뮂1eo2/؅(1y`uCiE2Oܭr>?90z5>9Y_sJ{wbn~/P4TqN@Wb8^=_zb]ě>v|x{Q4/ss&׼/l]JNGjke1ek6W/_endstream
 endobj
-1483 0 obj<>/XObject<>>>/Annots 717 0 R>>endobj
-1484 0 obj<>stream
+1490 0 obj<>/XObject<>>>/Annots 720 0 R>>endobj
+1491 0 obj<>stream
 xXrH}WtySedxդ⪭AŘ=='e 9}z(~"lLI~4t~>	G4'x?ī/hϧ?QCi<E|nm()
jR`L!SR\H>^_VI`!n̤*\	HK%'~I]JKw&i@&an84F=0
 .$ YU
Ŧēd4*@Sv	oEPFte%Dx|tjfbI{R)l
 `RPOuerQ55ЉɢvTn$S|5̲0(IHPR&u
mG21y.uc&\t3bCsQ
@@ -2860,15 +2877,15 @@ x
 5е<4Dx
~⡬lܼR>/XObject<<>>>>/Annots 721 0 R>>endobj
-1486 0 obj<>stream
+1492 0 obj<>/XObject<<>>>>/Annots 724 0 R>>endobj
+1493 0 obj<>stream
 xWao6_q0bYmAml)vk<òHl%%8{GJ0A+xw{G%'iJG1eY%4M9ůUlko4aq2ES*zeSA׽gsIdrIMHg)6Ni4xouSf0>u-Y̊Avq?NNTr$ȉyV]lB-}1ns[cUgc.*(?;\U'u"Vr
O_onk }D%*ԐijE
߀;^~J,.H/(PW;BKծ|ŒUpc֦)$gT^.
%쏃9gr-jZYI|^O>Wjw>LzTVۖ&SΓcyKgr^o3_PdJ訖=D`9yO.Y~oj跟ŚYl

՘;X׉+o5F0olb݉/$\:tv׊gJ|v1`Ũ R}zy^`M0cwl*|G:9Uc0wtPC
3pE't x.N|]~Qx;<N}=M}#p+f~/?2bZ!;wwtz#'%ʡ/Y0u , {C~9|h'yH_Wendstream
 endobj
-1487 0 obj<>/XObject<<>>>>>>endobj
-1488 0 obj<>stream
+1494 0 obj<>/XObject<<>>>>>>endobj
+1495 0 obj<>stream
 xW]o8|ϯ
 =$Ӈ+yh/PZm6T|7KJ(XrvvvvhL#9]L)/FوMٔ&K|N*>\<_ͲƗ4_lLsI`4y>etkztvYғ0>:g;O@e<7ra
M^R7'
?"hȈR8vqv>/XObject<<>>>>>>endobj
-1490 0 obj<>stream
+1496 0 obj<>/XObject<<>>>>>>endobj
+1497 0 obj<>stream
 xX]oF|ׯ-J; %6 $R|Yr;ɡgZ￿ኢζUM;~ObF%YvF<[i*ݸY~ZtJg-//hU9;U~&ku4R
)ux=~Vy+2aBz)0<MlUk2^U5{nn} 3aK޿{Omu#)Z2d:m??dBZ6
-?!?M&RRi*xHն4mճحuAB}m׍?Qȵ;AkE^g ǽ_Q^>Eή+]gt[Q Һqh.5b:tEEd>Иޒ
 A-i (%dk+5ݯ_f?ї%mNp(j׶^֚iWPqr|d=T[H6NK0sɞG$q'~OpǟƺZU՞
 1.M_gs
@@ -2896,16 +2913,16 @@ Um
 }4A4Of圖˳p}wsM
 :bX1]&gW<=Ӈb],/eO9'quWԞhendstream
 endobj
-1491 0 obj<>/XObject<>>>>>endobj
-1492 0 obj<>stream
+1498 0 obj<>/XObject<>>>>>endobj
+1499 0 obj<>stream
 xWko_1pQ,Ze=
 ۷Xm}YKscq{fvIL.ֱ<ф7ŔVGdLdIs4Y$:+s|©ɜ-&'y2Zh2uξ3ɺДF
5:A7v-bjw,7NM⩰)ӧRxr4q	of|k҂rhlnJz4u:w jOm(uLMUʢO\KzXOHқLwBq:m'UΓx*ԈiC\,q:q9KOi]ɶ{R؝NM?4&RsX;vSM-ڕ?Mt$}wl_X`uzO|mj{2V?OTA~OaK•>p{KïV7J=cj;,?DgAB#bxaiLoUb
 hì7޷xC5ADuұlRk+(g'7ƱEv*Ɖ< 2N>?|zˇIl]Z
Sm0*C\IUɄs;]=4lgK˻	nͧWGg>/XObject<<>>>>/Annots 724 0 R>>endobj
-1494 0 obj<>stream
+1500 0 obj<>/XObject<<>>>>/Annots 727 0 R>>endobj
+1501 0 obj<>stream
 xWn8}WЗql@Q
x$DH"Rq{lGIX
*˙3g&O3ɐƔ~ǛtgdDiҧdry:O!0'>L0Һp5^аObO4|(x\oDdEӄfX
 c]ҍ)tmL3t`$~y$8띍OAB?*YɧZY$"Sznh07WreԔ"k	B\n,!.VR!%F8W!5l9%m۰ZI
B!7$,eҦZ,OJأ%uej6Tk?їFL!hTK,*ST	|;ͅҙZ6Zlϰ',_e?tt|q΀2E|K0΀򣥍B	kL-
 OZ_P怩*xLh{E+YJr=
@@ -2917,8 +2934,8 @@ Q
 פ`[ka#Y%+CM/g*l対bm+À%QA]0d2sbNkBrXkf1A
 nʆ1m_IlրHcP%&D	H;ޅw!YTإe\02֬\M";),&~sF/:bmy}jxeNob@i\h2J&)΀<&W_4endstream
 endobj
-1495 0 obj<>/XObject<<>>>>>>endobj
-1496 0 obj<>stream
+1502 0 obj<>/XObject<<>>>>>>endobj
+1503 0 obj<>stream
 xWnH+C$ >eD$Y~V͐2Mۻ"0"in:H2h"iyOr:'CϦ<_eg/g2|	'>ddjwYD[;|n,sIJI-
 ]}0	cp
 f.	<׺1p{9~P^v¦ӕx+-jSu&k{7!ax}K%ksb/YnŨR˯)Z_Uvov:s`	$Tol@=L^mfuFdv6$am	sدR`ɣeL9Io?k8degty~?־endstream
 endobj
-1497 0 obj<>/XObject<<>>>>>>endobj
-1498 0 obj<>stream
+1504 0 obj<>/XObject<<>>>>>>endobj
+1505 0 obj<>stream
 xV]o6|Xb8p(hӴ6PMQPeN"7KIN( N3{-GTj^.knAJRe%$꩕&| 2pU[~eV7s!ޠӸ":~2^.9
 U[(8VAIWϠοB睫CpC #=ʆ`K-(8rllz}	``Ψ"`C)\]Ka!8.:!i<5Fo8c7/`v=IoGA|(zU)7szFN=Yvz={+kQNV=&Y&O9-7E,رLXo@o7$]wB{;~xYꦒPNyhɉ\4{ۆ	p*wpq>NZ7
  D5Yްb=l/
4U`TKr(jmrUfp*^g;!tB,e,k-]OQOY4	}H>dG5P(|0?5Ol|j+kTendstream
 endobj
-1499 0 obj<>/XObject<>>>/Annots 728 0 R>>endobj
-1500 0 obj<>stream
+1506 0 obj<>/XObject<>>>/Annots 731 0 R>>endobj
+1507 0 obj<>stream
 xV]o6}ܢQ$Y6tmP{%V#*E3KJyι2(oDiLʪQt13o$F_(J/Q0$Iw&ҕ~A_Ǔ0ף(_FICYREFTJ.K&ki*-M4ED(+>p}y}.
_
 ,
@@ -2943,14 +2960,14 @@ x
 UT(Әb{pMjKzߏ$@=R`en'`Z[Ұj9L
HkDB^:z`z{{
ڕ4WQWYXuUbˆ+i[iJʲ>/XObject<<>>>>>>endobj
-1502 0 obj<>stream
+1508 0 obj<>/XObject<<>>>>>>endobj
+1509 0 obj<>stream
 xU]oH}W\eiUTIh>UXVBOg˿3H!ܹsν5JhWB)2hO(KqFrS=4[[UO:ިq}dAeBi2
YLwF0'ȕ!ƹʽ<~J	t>6#oJdF"K#L-ZCV5F>*4;mN{YUhxI_q#[zRuGh&P0$uw a6αw7iqk{IwB(m\뺨uЏkUȽ7Q^-挗0uӦߎkv@P%"z3DsGyzf'TGR\|"_iuY:ƴ}${F-+o.=Sw4xWR(Gu.mץg	1=R*$Vzoit%
[g3!T{rJac^XᏴ@\@761EFƤV@Rkd*A?BĕYL?WRN,/C
 0>5jgq}7L4r_K[n֍qzP!Cϛ*gMxAi(󕳴5{vvn&%,Av[$=ynooOXp25Xo9iBOtƋl<	ynF"endstream
 endobj
-1503 0 obj<>/XObject<<>>>>/Annots 737 0 R>>endobj
-1504 0 obj<>stream
+1510 0 obj<>/XObject<<>>>>/Annots 740 0 R>>endobj
+1511 0 obj<>stream
 xWo6a;$eq2`2V{+ehHGRqIŊb)04HKw|w 4j0JFσ,hUN$JkfYrٝɔY2f49+oYYww
 49==KҸuEcm8wӌm$c[5vfɬYhۋ>bNiQtK>܈QBsQ-	KniCT=BWBo#:gVZJßy:Ώ'6	U5{rx$i0%'ڦ
mă6dyd	P0Z^Qp	xOQAH|@O#t	S.R}Wn
`s"|%Px34-E~lc)(׵3xIľŔSD89CJVƺrU5֑,me쫾˕*%9MN໧!<؍nʂj6v+(뵤!*)Gn-`M?1jrIK|)]3%b(~wL;9;tn#ē<hxvܯ5-DqLH:n,3v!;6{~D{҈le,7!sC1#AI4P;Ǽd_A`|4tk?kUC%
  ``bڃH@+gs*N߽vh:Q0{G_բغ;.
@@ -2960,8 +2977,8 @@ uB6Y
 #8$K>	Thix"si\XuZ$짛9‰@FںrV
 yb=.xXׯMk|#	~;s4\亪ƈmE\Fk]g)^h5$lsI膕Q6>USzeoYȐa2G?Lc>/XObject<>>>/Annots 748 0 R>>endobj
-1506 0 obj<>stream
+1512 0 obj<>/XObject<>>>/Annots 751 0 R>>endobj
+1513 0 obj<>stream
 xWr6}Wl֙Nlj;qJ"!			(hYH>t2	={o>O
'^ÛohLi2'*?V9yM;wVҪ3
oAQ⊯5׼;o؝Γa.}zɈqłk쎦ɸ:˻߀xOf3{ӥOx8c6Q`	 sw@<W@4Vc	{v^!8}Zy2""=(-3L!?n7/1n_B;'쟐7:Ň"zt>͋*-9.{)o$iOgob
@a@Lzr5D.6֚T:G_`O*voLi#^^
 >j.D+yijJ }f",YJJM2Zx)כ VS+
 vfB̅%ޤ&?ӚvV ]Sx|ӂC>.RPa%!&y'
@@ -2973,16 +2990,16 @@ x
 	Yt\H[
^L&D/C,X奡gܨgVܐ@aԖt3F/F3ژ042nihv"HpQkxY?c8
0.Mqx
-;匣uP-q@Wd6߭xĬQEz7Wc*MW<%! 7#h<0'֘;b3n`5+y,nr.gV-ׁG/QጤOC*ɠǷ4
7
+&2LZк-ЎOڣr	?QAXx"|RǗ~|xP׽U?%ـ&I2y޻y{A|AJCJ
 (k:ߤ!O{s>tL'3|Bxr/::t=zendstream
 endobj
-1507 0 obj<>/XObject<<>>>>>>endobj
-1508 0 obj<>stream
+1514 0 obj<>/XObject<<>>>>>>endobj
+1515 0 obj<>stream
 x+2T0BCs#c3\..}7K#4BHP$YSO1,1/95E9?/-3($3?O3$BUs=s3]!)& S\CQ)endstream
 endobj
-1509 0 obj<>/XObject<<>>>>>>endobj
-1510 0 obj<>stream
+1516 0 obj<>/XObject<<>>>>>>endobj
+1517 0 obj<>stream
 x]OAN0s\Ҵ+H@Ȧ$+${\u,{:Df&'1jIY<&voHF
s!ZյӍw@ܣ\bW`+žcW`9/rv)_VaviTDXpo.]ɣ.)߳|w^qY0|T>	{f?]endstream
 endobj
-1511 0 obj<>/XObject<>>>>>endobj
-1512 0 obj<>stream
+1518 0 obj<>/XObject<>>>>>endobj
+1519 0 obj<>stream
 xWMSH+rr@LFXKU|5Fɒ8lQlin<ZLivIiy&dIrEd7&'c\%3\NZnLɻ˓h:/WvƸnrUh2IzЮ4[{<*1M02NS=*8[Gofsdpߌޙj#V\U!~_O[ϗC{lj::UMoEr)-J*l8T0Ϛn}cVKψX-mf{j[e{nbL
^|`2炯rz-g)e,
 !vAڵ ~r=r؀VfS	SJ(:a>F*+M:$5&LX$W3)5̪$2?j]{6i9	",AYFjss:[红(l݆踱PW.==4P.J7Җ:@"@[UTkvZ[ @)#ƔВ\iTt)Ӑ$5X0̘-źCbKM:ݝ]	mwRKCmi|2/" ]CSbK	d&TZj\ja2t
 0Pq4sbx
*-M-ٶ>e-FqAhZ,._;kJrHݫzm%^Ljc压0aBl^sspc3=2#w2XI|q08(ATfY(ܔ{m|G^
@@ -2992,8 +3009,8 @@ x
 x;/6cU$8,Ow4r@	=J?GBmڎ,t q\a|g5{nճ2vv^Í&go
 [MYdۣL;,ne-|Z*z
_n*]:_̓ވa=.O>\endstream
 endobj
-1513 0 obj<>/XObject<<>>>>>>endobj
-1514 0 obj<>stream
+1520 0 obj<>/XObject<<>>>>>>endobj
+1521 0 obj<>stream
 xXMsHWtqTa^c&{eF0kI_g$I%qGׯ_䟓
gDsSCs9I?FlvI-8_MhzJ%9Mn-)#sG+
z1<_P*>vkeiҔrh35E$!"-Ym[mN20W#8i$Bl4T3iCQ/He%Ks9dA	0q~?pUb.jp|Arpu,Ï[>fjX[plmVI<[ua	îE:yX[9nVVqW8&*"l8?ˋ1,y奿xp^؆+%+r4#\]x|>e>|=Gp: МV/N[_.'
 WCz?a?NuPpendstream
 endobj
-1515 0 obj<>/XObject<<>>>>>>endobj
-1516 0 obj<>stream
+1522 0 obj<>/XObject<<>>>>>>endobj
+1523 0 obj<>stream
 xWMs6Wز$;қSLmi@$(!&	 M-RPf۷gA%ݬ(.97[ݬįf&ڬi納ۃ$+#WN(VFF6G*ɔJRqH)"WTN%Z4&FFZŜ7%Οb~xMi4j@O{˃(aHJ%ET(qaBv1쌕rhC[SY?B"r~{o"A=>;{H	U:>9d^z_}ѱJ >~tae8"UY):|2beT\Hv2a*z	v<=>qOiWg4|:BaKUJQ:zPeAespB]o涊^eVo
@@ -3015,8 +3032,8 @@ rwP
 oNDlʜ,/ǦBFFbrST1:3ifԻ>/XObject<<>>>>/Annots 759 0 R>>endobj
-1518 0 obj<>stream
+1524 0 obj<>/XObject<<>>>>/Annots 762 0 R>>endobj
+1525 0 obj<>stream
 xWn6}W%.(-_RYtS,It-;1"93g.>ic(-h/퟿$",E	Loql23>5^ĸ2&8R$_nnnDSƉS:[&p7\c7Y:ԙ<-+'9XUc
v5v(vb;o%)|\1-3=[irh3]V՞L{*JI{
 '>Z⒠J?:?^$6|Ov-i#Bti^
 1nQ=*wXz|
@@ -3025,15 +3042,15 @@ a
 iem''خDN/Ժ{-]Gs^/N>>&%/.o&y`eGJ	[GDq68H39֭aSBPPz$W#Z -לdN["/ty GQpsu]tGekd0AOk()0AY^O/J?
*T)n5>-|u]AW+^޹&յk9]wC”P_YIVꁫ~dе;ʍEafX3eT@_[\u_X{Ľ`.h%wR?'sʲ3adb#msn1Szk~{Yy<{ZasC	{,xͺ.vX"*TP;_JEn>9Zƍ(uqdږ2dߵWnB5ȫzJ7vpAnxbk0n;Vmyեt%@#gUiEW]J]ZiiU'`U6U=ڡ%PL4ꩈW`@iyS$8k.y^ōE5#'Jj
 LgD:[(3<x3~~xKVܣ_u-0F]5ǯ>4/nzdݛwtsx2Ol!nOoX??E*endstream
 endobj
-1519 0 obj<>/XObject<<>>>>>>endobj
-1520 0 obj<>stream
+1526 0 obj<>/XObject<<>>>>>>endobj
+1527 0 obj<>stream
 xMo0DN)8v]n-+Z[,AHW{Pm|%"/d
 D5,X|)Vt0Y^A@+"4:QIwSFV\!:99m@CS%9X0<+ʿAyF,tfo`)l5j?K}ZYhj™#T}ڹ԰
 c8D2档I$˴t-l[G&y_oﱵ/ڱWWn1c\_&{4ghh&2'7аY(Gw˯,F\RۆVHBj݉Mֵs'E(Et6okYIֈ4XqaWwۉΓy0շtk| endstream
 endobj
-1521 0 obj<>/XObject<<>>>>>>endobj
-1522 0 obj<>stream
+1528 0 obj<>/XObject<<>>>>>>endobj
+1529 0 obj<>stream
 xW]o6}ϯVlh^-i]y%Zb"I߹XBuby?9#,i%]t~IY}HuHRZ]_F.hŕ˫kZ<ɦh4LVQMAݵh[|;]?Ȋ`d^:~q8>S/:gQtF1vMnHYBUbSɄ֥3F6jJôROړ‚8+ESȇSZ4p;ްwosDUɜl'd\[L/XGq@8	Eفx	v])Rkp09%
O`8扈_nçc'	wc;}"8
J/T;N5\dNwUO~?e80WFf~)p2b7T")
$-1L9ƁJ^u]Ρŕo^}Fg_t	`,
Dj\b	YCj\]^wd{'mD(iendstream
 endobj
-1523 0 obj<>/XObject<>>>/Annots 766 0 R>>endobj
-1524 0 obj<>stream
+1530 0 obj<>/XObject<>>>/Annots 769 0 R>>endobj
+1531 0 obj<>stream
 xWRH}WUkdK	!SyXa,$h${ӣc\XӭND}D4i0>>>E.`Hq0prv!Aw r.P<|g&xl9UE#Xq?Q087ѐihm4{Y'>24KmFtbUˊA@*kU>ҴYtUξgQlopQ@7e]Ij9E;	,FKRyFSQ,֥'JQ/LV>B&KQ*SR*,k>oM{hUÇ))JO9iV1A&tbe[QމrʁD	x#i"S֔-zCzR^l۬|Re74o0](2"e-PgZ2K`wXN.8qNr5+]R*Q6:q썂17q/G_xQ^Q/Ӵ~*E.O	YštNFZJzޭdಮWo`J$yA)k
eb1voQԱd-dIдUN'}녙wg$$ѮI"+ӭ2 j{u˵u=7F9&^|p?jS#I Z5yFtPc$:ZV4X@Ҭ^|,v_#bhzR`Ke!eIF\>It5I$iD!3(2THBDfEI70=UYtAjjĂ]({u:&KO^`hUu.9
 ;p wjQs5>}D(-mQrUߖ lj͂ܭ˞0\o[XU#pŖg)S	=۾ZNR д^g1he%2`re	99t:P
 w5]&'a/Ckvyہ3Tڳ.ӽQЏ4iYr&NǢ>VɕAyn7;(dcs}!\|GYg~on8*TR``y'%:Aimb8p)r0۠L=Y*#4H{v!<-˜
XC[|>/XObject<>>>/Annots 777 0 R>>endobj
-1526 0 obj<>stream
+1532 0 obj<>/XObject<>>>/Annots 780 0 R>>endobj
+1533 0 obj<>stream
 xWo8ߟb8 )P/پbKt/5^6-1[ITI)d(Ù7oF_c
 ;ń B=</1xG9ͦd9W7
 MWQľ,¤21fWxpڻt!5m\6q$	i_V&;oHÖJ4/X4^HuYjSѳ6~4eEE:x<i86ɦuT0_Y.uL*|HbȨFbODMRXyYػ)TIOb]+ߐչ$yog^DVK:NIX*E^f*#ބddT+JIovdU%^w>w2VZA?DByKwCQ$W퍮a&v_GʪHvZJI{qѺ"eIebUeH1UpΕ[@?1R|8e:Ȋ|'FKq/v΀꒑,!] y,b&"`dsYknJ7̹
@@ -3063,8 +3080,8 @@ r
 ZzHerݠx[c.+4s=?Nv|*)@
 oo6[ä
$Wh)`]:M{H7/WzߦߗzWL^,O8?/de*sٚN>ޯ7gKga^4^ߞ]4[R-O=ly=}=?o6xaO;=
Bǽ)"P>*fYFc`JejٴNƳY\N($r=||wCk?k=W8ZrJEm*Jn]h96ˊ7ThʯO=Tendstream
 endobj
-1527 0 obj<>/XObject<<>>>>/Annots 782 0 R>>endobj
-1528 0 obj<>stream
+1534 0 obj<>/XObject<<>>>>/Annots 785 0 R>>endobj
+1535 0 obj<>stream
 xX]oF|X/KJ_
 'N
 É=^f4/Hj}zKo:bu],VN$1zIűj,6u\oUQƏz3TH
M#|RZ[5=hu2.Weq$ie:蒃BRQªJ2>Ը*z*&'q_hUD@.>YPtIS*s9^_@\%	mMw&1%aK։ws=)WDt+TgnĞANKiZyz|F#%z'?NA)(l*I屦}c<[1Y_ֈ/ic*Gͧ3Y);DZ/Gw
e_=oߖ66<GkG{S*ip-{\koPݽɀlIG
@@ -3074,8 +3091,8 @@ x
 m[F9FKQRyQC:
 "C'4f:O&[&XBBS>p'1F gq	|>{*S
w˫3+҂U˧xڲʚDu"BnB^ldDs3Y춐߮v?ȼf!zLp))I
2g3><^ޱj^'aT[D&a5{4Z-.xhp뾲1DW}Vd=j-/h/cfsog@vendstream
 endobj
-1529 0 obj<>/XObject<<>>>>/Annots 791 0 R>>endobj
-1530 0 obj<>stream
+1536 0 obj<>/XObject<<>>>>/Annots 794 0 R>>endobj
+1537 0 obj<>stream
 xWnF}WLQ&
ADE"&W%{f/2%8H46,k13gΜ%7~HEّ:=_!il}ܾ>je]49-3f-3
 ׮kXVDְ 3Rʾr˨^׮Z_YW[kkX'A8Ow+m*W[5Jw6lzְq,_4n5eFa;tNjt}ƺ>Mo/!NvqXEQȼWzOR樓
 YQ+cHdQ/>rtӥDh'yDYl";A}-
@@ -3087,8 +3104,8 @@ C
 Kǐ7KBuVLU2	9ƨhdH0ic8`X)ǩe"llEکK'2>'uCB6d{4Vgr4.ä][eXu!=Jn+FOKy)`QyuR⭈%eT-5Djos
 #GNGFa<|[joB!Bphy"B+} V8^o{2WOE7Y|\xEPm0)n_.ދK؜DKo]fpA5<tU|}9`x~.OʥIk`[:MxЦ^dbX}I*Z3$lw~o`޾z]|5=['endstream
 endobj
-1531 0 obj<>/XObject<<>>>>/Annots 794 0 R>>endobj
-1532 0 obj<>stream
+1538 0 obj<>/XObject<<>>>>/Annots 797 0 R>>endobj
+1539 0 obj<>stream
 xWkO8_qUʊՖIK[̠V#1K=; c)U;,3<{þ[/QH!Yq?4woifuc?b[
(A?FCJ7G@qqzOR8EZ4\HZȂkЏXº{KU_=oĝ3u
 Ew4UdL*p4+yrN$l;}}y1yMttMh%4OӦ`h7#9o8qN_^ǒklݢ$Yqc3m_@v:z;D&L&W*M-äwa/izhOhoXvsl~g˵
a!'[}qA'*.m8m-wkQHt+Fo4NœF?[mqendstream
 endobj
-1533 0 obj<>/XObject<<>>>>/Annots 797 0 R>>endobj
-1534 0 obj<>stream
+1540 0 obj<>/XObject<<>>>>/Annots 800 0 R>>endobj
+1541 0 obj<>stream
 xWMsHWѩŊ8e.!C.cilH3BkU) z_~v2~4dhL4]kI+~'Ed
 /p*裻W,\DQt>_$c'&/ӓK)]!BXP0GfyrPtSVҶԘ4Sd|glaL6*
	t{7ozԖ̊,|V:7ۆnSztdE'tejLYJ=!GW.UF?#F[b%5J6VT+iL[g7e=#V|&kKD２Y22^KZUckl9HT5%O8'F0ZJ\?2[IaĘeKNCi r'yA_}SU^h9(ґx႕*d597W1QY)
@@ -3109,8 +3126,8 @@ T
 <mC<0Iks{<3Zq0W:ۻЪ#;6:KH<7p!Gaq'ya
 ͂H=@Y0P1Ę. R[+l#;(/”iX{T	;us2;ԃP^ō$Uh}9}T</^'Ȍ@8ҟ1l[+ܡ0̅Ғd%*Uea	NrZע$(]瞣ܞàα2cy?e͏b)vҰ">	iK0Uջ9Y\	H"Q,kqoxnqR7`Y:ÂBuT`E|<װ9|_{/"'p>Bak~;t>M泅4gsMznendstream
 endobj
-1535 0 obj<>/XObject<<>>>>>>endobj
-1536 0 obj<>stream
+1542 0 obj<>/XObject<<>>>>>>endobj
+1543 0 obj<>stream
 xWn7}WIP#Fĭ@jhsk+Y!wmis;sptҧ4pLi~Kz4^$#M'x=ƢYaZ#i|^B3y	+߱s+mBոq
 6had+_1a'jdb)XS%+	ı:i.m~rAЃYMG,TbT̺oؾJU4Z-wRaSAb`BL)QM4axX=Ya|Ů$|uƓA"=@IἈ7gi:qv2MFd>/XObject<<>>>>>>endobj
-1538 0 obj<>stream
+1544 0 obj<>/XObject<<>>>>>>endobj
+1545 0 obj<>stream
 xWkOFί%%RfЂDDRZ*lYU=w6mcsϝۙ?ZL`Nq3i6
4;\#)y}dB&-Ϣryjyscz
j*ź(D1jkF*Gyeh,`2n[]gK8Yq좳y&]-kYG†:]o¸霡E$fҡ;RDDΝTrDdrE
ٍu kjG
 ]Ʌ2z#J7.8'.yp2#e^R6a9\"V.퐖YmKZllpyikJ*U2JIXCH"*Ćlt/Zat:l=

 WœH'L^3 ?{|s	xO~wJFL^{85,֑r-f[	&s/;	endstream
 endobj
-1539 0 obj<>/XObject<<>>>>>>endobj
-1540 0 obj<>stream
+1546 0 obj<>/XObject<<>>>>>>endobj
+1547 0 obj<>stream
 xWkoF_
6*y&yiEE~|gHaM$۝]=icZLh:8#OfW\O4e2z(><h4&^آeMU~`<)Z
 sRSɖxlD9.lC*ɮvOZq\UdjjKPEnI
⟸rf&zK^kv;훼F>Ncc|aO2Q9ulMmV\Z1HҶu*dnIC]'C*mZ;-=;c޼,`:qY@ʕ>2NhCm0׎JUh34ĮKN_TRߠdUB0
uHuDo'P"_^W"A9)zMYWSl
 [{Sg6m9>9lZ;Ԁ`v^/b(5ѷʔCh<
@@ -3141,19 +3158,19 @@ X1
 C;ٟܔ{-Eߞ!x\n7);?jf,zk%`B!֕{>JɿuvNrCzLL|۾}W.phIyq}	G$ނ~y>~s
|QINZSYnE½2L.wΡRD8CÀf"ATk9}XӒK9P7i*^7gLm|	A-s,6mRA|@.J`3-ɵs"34%vX Y1~5lgg
 <Tߏ\d~!jd2y(ah~c>/XObject<<>>>>>>endobj
-1542 0 obj<>stream
+1548 0 obj<>/XObject<<>>>>>>endobj
+1549 0 obj<>stream
 xW]OJ}WLiByHj)z++m5b{4?k^UǙ3g&;3wFC:ZPZL)^I4?^!9Mλ4M+cǧSIfG~1A`Yș"D,խNcN `wgd(OW'Hn"7SUSUcrܐ?RSO|SW	lhFktD%K'||Jo{2#FDee`8/캋Y(I
 ]Me󰵶#gMl5?Fq^}&juBn3f~w{\ W9V>kP';T=pjN%IfB!(Nuo<0Keq8k\y2-5)ps7v@GU5;[۶HltSF&}ժI%G漿^|v9]jS7Avh9Tih8@S4G&;IK*ve!6*&13SzWJ\SAt:U:g~[i./ݑA6r_yR@M
z%*8;ݍPQ"ےIm
-b
 av7UG/y4:"h1D4}7xC{$y"un#^M͸o@UvE+τX~|k5%g;!Cx>!N!Cc3@>X]\xHyႫm592Hq[:lZ#+lVzw_nf|g:>rw0alVZkb!k|9Oc|M|{?xCendstream
 endobj
-1543 0 obj<>/XObject<<>>>>>>endobj
-1544 0 obj<>stream
+1550 0 obj<>/XObject<<>>>>>>endobj
+1551 0 obj<>stream
 xTn@|W*UIM?:J#UЇ>am喤;wrV%ݏYD!>Z&T40)VALqi;8H^*\˅xy	|fEQLI%;)/Σei@_+wEWBmWi]~1EѸHy^ď0ft* C˘&2`ɯ"_,7^_uhS0K?pXwp>n81<.&Zm/am;8,뵽8,Tz@w'SIp vdSVtW6(-iLnj4Xa-~aaf?]876endstream
 endobj
-1545 0 obj<>/XObject<<>>>>/Annots 800 0 R>>endobj
-1546 0 obj<>stream
+1552 0 obj<>/XObject<<>>>>/Annots 803 0 R>>endobj
+1553 0 obj<>stream
 xWr}WnBUIeWmd'UUVL:vȱvf =Erd>}Ɍ;..)-O)N|Oh1[T|9~RJ]\4߯O&7oi>u+Zg'NA;-݊jںp&fhbot[g&
Vf*b띦,mE_*}j.i3bS)ONmA=նn
 (iKdO*(aS[g1>80ry
 iܴ95U]PHse$ve/u~LӾ)į׺"S?j2x6-Q$`2Q|X<v=)<|\WSeTs9Cu
@@ -3164,8 +3181,8 @@ x
 h1En	=B6yDΖd(w*CmB =+`x9ÝfYwudeǽ0/̗~fI"BL&at8덎\&Ũsv.Fw~wՁԼ*:WGccy\Tkzeי,9dQeG?uUh~-g،b
 3!_sDFC o6_}'-bQ@MM3d~ZsLDHп)D"gsa'-U01T>rsx	tz	i#dxv:dRs1bfӆ'Dv?knsZ]|͡TD[l3 za.Tz($A3-;*E3@Mu"ϊ/X>Ln7LJҩ@GexաέSm<|be,Zy%)NȑSF::">drlbߌ^-^X5y3iE5j(KXM=8bF-TRYLlfPb$er]Io _bs,cD9 Fk0u6Ğ`I0Tt@uM&#'fƋTB:FPKYk!/̝^K^GYeS\j֨B/^IQD9N刽m)&7WO_ԋel}\WG//?':/rIendstream
 endobj
-1547 0 obj<>/XObject<>>>>>endobj
-1548 0 obj<>stream
+1554 0 obj<>/XObject<>>>>>endobj
+1555 0 obj<>stream
 xWMs6W(%93=8N]{~ٙ^kga#=@'@hՐ\ bOMX{'8ݙv7?8\A\_*iÔ3dTcz7BӅvL8DSǍԼ0-uI
 dOʣp\Y!wϽ竦_8%7'$:N!+p.huX"]PW"%U(0bgqxn/\jp#PmP`vǟ={Wu`/m/̲ǖv,
-qiV{{+$Tv5)K~4CXP5t7$;(}2PSgq=lEGH&qECÅVb?kӡnB+zÚZ:t<7+Ѣx n[7_=Ɏ89F5GZFwJ|'%5]~@CrPP[F#|י4հ7yj
B7df3;dϯ'4	zyx}pUxc1R4|Blx2M%z<{7>	endstream
 endobj
-1549 0 obj<>/XObject<>>>>>endobj
-1550 0 obj<>stream
+1556 0 obj<>/XObject<>>>>>endobj
+1557 0 obj<>stream
 xXko_1] cxW?mM+PxEnH3õ$opfΙ3C#Mqߌ3:>9)pp1:?䲣Wӽch:ӳ	M+ᐦ~6AB7Mhn|p:P\4eM	R{-TFclE|V{CGGiZ7*󂦰X{S49]^\np쮏w*ʶ	FrskUq
mLsVؠ}}>o35@F#Wג+Ά.!նԇsrxgq3״TwPkXt=-Egg|Zsed')&.XVC(#/a|nt4c?3\*J%D@;+`e~Ng}
 xLFe;+{߾W$tfVV7rET1Qoy|I)јfa"r#'cdB۠t>̥th|Lѫ_2.jz}H+0+B[Y+
RzkGOaJE}6e({
 0:5P%V&*xeLq͝Y:sppdT|}|@	uTWOLI]˫&zr8󎕉u_F*q\i@xV=0an-"!*W"Zֲaheq1(O#ѿsz0hYP0b\	$33*>)t]^Ppl\
s5$FtX՝)bDu9jT*k5C 
@@ -3187,8 +3204,8 @@ x
 +'n٭9><_盪YdCK37:M7Cz||-":߈lAʒه雽r	!B/c][{yZ{(R0o17%41n)@쿜d3R'mQdA>&0$&rsLڑ.w#5eziǕf0%2Kih6ƠȄ-t1kok< tl!7=TH(vn,O/g?FbxvD>|uNW}Ƭ.
 	GaG>B qq)rNVl_"~w<9.&g`LNӽ?|endstream
 endobj
-1551 0 obj<>/XObject<<>>>>>>endobj
-1552 0 obj<>stream
+1558 0 obj<>/XObject<<>>>>>>endobj
+1559 0 obj<>stream
 xW]o9|h@o^z
 0P3ŘNH"9w6A["旣g!'L|:ӳ驜^ZG?-fWXr-g粬sYVǪe:[^u͓{	V־:Ht7ZVzW;7<>zWL0}|4RYTv?Jq6IZM9ˏ9i>BDTZSh\3{jiյaҺCMʲLJO!bmxp}w93 ӝVk^|MԢdsFrⲰ_*J| @I}kfz^oSY5;DdԧܘPԧUfx{BRR`U!^WUVU!1Vcw@%
[ML=.$h]Z8oײ6!q`
 ,}Ivj*1_a&D
U'ꪋje-8uϬYXYmRT/SCVY`K!A뛟%[-hHyX$9zp4^
@@ -3197,8 +3214,8 @@ x
 Liͣol2vܤ
i=/WFo@,n#tqĨʩ	-|vD4ZFx6;Piڅv+-@TCV`믵cJ>4CiFdAp
 R)`7aR>=T]L/4}rnzVEtl9NAxȃ{vB!:\fi:aߣcXHύٕz~N37^Edt^iÊԊ'MB+6`@(}WyPzс vP]OH	X
Vzaaɻa<+Gǔq!?H|
}P>p[\\Lrr26e(%[?x#g?Ky:N	V>7LxV'2ilyz~:=?PϘˣߏendstream
 endobj
-1553 0 obj<>/XObject<<>>>>>>endobj
-1554 0 obj<>stream
+1560 0 obj<>/XObject<<>>>>>>endobj
+1561 0 obj<>stream
 xWr6}Wl3~h21Q?ӫ(h:k%‹A?_F4|	39>uw6{(D-%UNfd4}V:3[׽̕ޝ3oJ2+43_V2E+G~#"3Ky<9SwpYh8Nq2
v2Z,sÕܸ[V!-ҘrygTPz{[coAG>&(iJ:*_AdpFQT`JQ\BiP:pA	׋cN0u8:A7¡pHȦD
#IA5yT.5"_pGUp6B!Vf![z*E4t'qKۺ0UH;Ơ8xsIQܛZ)Xq!S]Bu7+P=\V' $2 ;	z÷|+jp*bCϣOV
}#Q>wj).˲5	y=6)عuɔC	s΂}c?xa*OF
@@ -3211,8 +3228,8 @@ r0
 ${,2l
 l`9Hqt'_ֹY&~2N_\ANG[B9g=۟.OEIZ MP_=v@8p<(<wN=^{NKT/29eUu
D[`pgEW?Uy$֘ӯ z>񞍓iDɍ]M믂_S|ּ?n$f&xf+endstream
 endobj
-1555 0 obj<>/XObject<<>>>>/Annots 813 0 R>>endobj
-1556 0 obj<>stream
+1562 0 obj<>/XObject<<>>>>/Annots 816 0 R>>endobj
+1563 0 obj<>stream
 xXmSH* nQёܗ*Iw;?v'q/soA@]4QHQv4w
#_-hqyb!A1x̨	{4{ݞ4V?~ß{Gݢ;Zc>h`qcx#[n]F=>(8:
 pnlqЙv+Tn8/KQKa
 RO;Iuz%ΌqZ1)`0?۾I!(M`wJ|3P8l Ld$H<:`M@$*e]RZ[P8{FqXVi0E%^Fw&ԢMyȧs4py-9{y.O62̄isbMbV*MZ;S1Adze1o0w:;n}n?ևL.}ϟ&?qYm0σt"|*2jUl
@@ -3226,8 +3243,8 @@ z]
 eHg!y0CwN[W0Z
 (ۀ%6H%vm2\t&C˂R0o GḞ%9{5c&OWQbl*a~Ec!.G5o+r(Ynj@8Kddvc
5ֻ~nS2tΈ]#/k~PwensQ2q@܇,rNa0$ f&bfec;;å%ś=!\ҏ$w{ ʺ4[01]#~{1WsvD[⥀|2v]}w>/XObject<<>>>>>>endobj
-1558 0 obj<>stream
+1564 0 obj<>/XObject<<>>>>>>endobj
+1565 0 obj<>stream
 xXmoH_1*T@JhsJphx]{~=ADN*"wy晙u~dM
*urGaQau6Oizt1<2;UmNql#l,dH>/|Hd~$ɂI_391X(J0b>3?OC6	Eeb80_*ZZ8QFlMq_[e	1tg$}HE(ՈO쑏?E88A|p{Bh99(spX0"=ĦDbB,Xb[=:1bxTHM᤹"hVOc[:u.XhY$9TiU@X0+BV1Qsz zLx	Ȳz͊OhUԔ
d`- 
 B ÉEDÚZ&Βy^2(/-'3A+660aQ#&֋}@SD!uny} G`&>/XObject<<>>>>>>endobj
-1560 0 obj<>stream
+1566 0 obj<>/XObject<<>>>>>>endobj
+1567 0 obj<>stream
 xXmoF_1I$*HsR"^.>l/ٵMkNתz晷gfrd65bi䴌&5;m<ĜGӣzߤS.G8l4eUŸy#?Jxp'unmr4
̕Iyn(
 ]<ǓQ|G&,@GӻFHaspm*ٴ۴[E>9>Mitiؽz]_&ѐBwG`{(Nsf*M8_ܸ.WBud=	W,vI,dh%i01hV2Z\~R	pn3p^Cw{p:1n7exYղe8UqYVDzÇ߉ktq54J@8MȚNh[~Eֵ:#;|ֻoΦRmϪftc96
F2uj۠êra9Fwk<
wQ-SqA18Ve3mE,C7(^1}F(Y0u_ p	.DFȑInblÜ6i'Ne =%pO17"(K0ɥv]&7EOXu=1MX쯒pF"DZD|"1<@b++cUL,SdX30 Ҽ,X4S*iH]~'	o9
uiEO7]*`iQXӇ2VPkꇇ4ȇjttjz_mendstream
 endobj
-1561 0 obj<>/XObject<<>>>>>>endobj
-1562 0 obj<>stream
+1568 0 obj<>/XObject<<>>>>>>endobj
+1569 0 obj<>stream
 xV[o0~W/TjB2@i"H'^Lb$lStjIdɎ;5|]h_ev+pOBc;Q\wvdž(gz)a<	.hZmx%+02$ 3%|iH2*Pȧ6,ZslMXݩnf
4AJ$I素d30b
u?p̨B$A{V4t?@J*ρշc-*7%bQ˵ջ}	(Bo/ POήރ>hE=
Μxni=;?:~{ۈ\+"yNbnך(^tAp?6QD{5=[뫌Dp
 N2eeIX2VAzHhIqr0<$\]ʥ1++'YHE(s
 
@@ -3251,25 +3268,25 @@ x
 Х?kɺkUmGwTVu)+ B,3膕'
 BLyJ%(luocH[P؟hiG&.>Fi;/sjNZ햙ঋ?X-9ЪjZkX;5M@;E⏌mendstream
 endobj
-1563 0 obj<>/XObject<<>>>>>>endobj
-1564 0 obj<>stream
+1570 0 obj<>/XObject<<>>>>>>endobj
+1571 0 obj<>stream
 xW]s:}W/df&ĤIM~I,g	z4-N}6Ȏ˃l&wi|Bo#Mwd8	"(]@x#8έ=dv&3w6Ο[mR3kATI?uTI	=j5nqAM\/L,|O/`޼-\p?ʄZ2FWwALBljqZǶ?yGXF1E	$R|ǹH`ZӪ05_[кZ
y>\!|{ql쵎$t=,E/&_P;,zB?О
eQg~W){|g5GK+Jݪr\٬á&q+i~csmSAZ(eȦqM\PbyK(|EUjԮ:\x+;2^%wR[U%pԋ[XNM'ia@
cM[(9c<%MJ\̼s1ӧ.IR Wwq1xXf01s>VpaMzϔ׭fxrLazwa5^ɂfƿ.Bendstream
 endobj
-1565 0 obj<>/XObject<<>>>>>>endobj
-1566 0 obj<>stream
+1572 0 obj<>/XObject<<>>>>>>endobj
+1573 0 obj<>stream
 xV͏@WϠqyl_QE0GЕԕ5 daQ@fv1"KUPX!*0,Ծ3lG
|\8gai\VPa8"1r!S	40PAǪroNu@|`OPDM,"O`m.2AcJx:Scz0&H::Hanc<w2G7Pntf4]C.FFf#Ck
 GWB#}m74YJ;˅J1:YҢ"{&~^wz5q×Ͷڷo}@endstream
 endobj
-1567 0 obj<>/XObject<<>>>>>>endobj
-1568 0 obj<>stream
+1574 0 obj<>/XObject<<>>>>>>endobj
+1575 0 obj<>stream
 xWmo0ί8/tUL2`:@#O|	IfU]м0͉"9?=e@Ns%hw8m_YkGM{Nbf褋(WMOˤcx,~۔ێ	\;P#3vgdJ0_ǒb~57RxOYTb+	>2\Xc.YEXP|gۛWЋh%}!
 Ԋ’;3ܧR+W`㚓25뚼0VmLb3l)M5@xol=F3tX凊).
C{bc],5[ sr" SgNB=0q$wn)k1,5$G_
 i:6ҶEp;Px]F2	 %|P{=n͏I+~,Ko	K.2. x}>-,?{U/Ϗ!Y١
+s0\^ٖS$	7ݦ+k'MKf225%
 ŭ.FC	9N]+:ڑGsZGO~Ft	X_|1WiN(m%[V
endstream
 endobj
-1569 0 obj<>/XObject<<>>>>>>endobj
-1570 0 obj<>stream
+1576 0 obj<>/XObject<<>>>>>>endobj
+1577 0 obj<>stream
 xWQo8~W҇cwnԓX
 S_Lb!NR\Br
RU;7|3j_:gp~	=h>o\v|}	]_ܽyogg˧.W(RPL홬x9(Xsy^A5SڝPW^UgҹTW8-@Wd&m:k,UTd2`˜~V+@SǸInrmonϢjB]e"1y뛭!M)vW]40	lPif6Ɠkĝp?
 `s:Q>4*xk
i0!]2BWЩJ\4r@2xLJ	6rCz0i)>%*iW1IjSe
-ALM0vc1YX8n $:؁WZ2k3 }f!#6R|`$IPhH#1;;JRCd4]TG@pT$P+pDB04k3:falYX	o+cAmM1utjLN8C
@@ -3277,8 +3294,8 @@ x
 ^͗V{%%TF hMX@Ee\ZhjV<8kIs@A4Lդ>#Q/^.*{V;ӤQp."wFڸC,}l	{b鵵mT!ugC.FR	bR4zӵw]Ww=)'ʹ'tXf_$,Ŷ|Uta\궥6lI;]eNö?M/;o:yxٮD~SL~헟tgvFˎwi}{7{X
 yifz`w6n{cR͋΅׹>1A?TFendstream
 endobj
-1571 0 obj<>/XObject<<>>>>/Annots 816 0 R>>endobj
-1572 0 obj<>stream
+1578 0 obj<>/XObject<<>>>>/Annots 819 0 R>>endobj
+1579 0 obj<>stream
 xWmo8ίn7J{Bn+J'!L06sc'iyӦ*$yf<]tlCWz}%}}3/P7vk#
}$M+;C9mwffew`Rǫ./outFW9;8ߌ1Tn\:w>V;OGK
 %Oui,R
k!	^f>LLjkPuvt>H-1@[	;yk%ɗ
 ԪPJkyǕNj4MfTάq_T0y>B>A5}" O4d|}k+Am}?lpwӛJ_7q0_qOLzyP329V[iΘmEJl36*cn_
@@ -3287,15 +3304,15 @@ H
 R*Q[Qa?n$ij!]3I݁]NKޓI-@N\p%FxEP-2ƪ0"I|Zȍ
04Q`HSB}0V4qFKl1T0QDbNTsuz2E\i.xRMD$CM-0V/źjkDCU3S$!pM
&fQZk@n!2x/>gNdSò1Ex*s..Sh24UB|,`-ac	NQ}lBfRLR£[["v7ݶ5*Wendstream
 endobj
-1573 0 obj<>/XObject<>>>/Annots 825 0 R>>endobj
-1574 0 obj<>stream
+1580 0 obj<>/XObject<>>>/Annots 828 0 R>>endobj
+1581 0 obj<>stream
 xWOH_1Tl'!$SujеWzIu鴱7ɂuw7vJM?\	쏙ylL'Sʃa27?^74==OTx6yXN3^;=Ki?uk'?7:b-|q2l(|ⵯ4%?phv^z=:M.	Vhٌ|Hlâ aF:Z)Oavկt%ڨʩjhIVHdYՔgwb+	˺,e˜r6iHY[&QB׎’ X#L-6~gwiscͅ;qL-ZkUZ'*Gr*֚J7E8J%\N
 tc[ۣ{\%V$[k]HcDEYI#F77>btLWH+c-u.B	RtebN;Ѐ+yBІCLWX$ Vk+{֍h1qڪ$I%6N*^	k'!JzCW[d!0J&IR?I?SY86yxS1Lh.9ސǵ-*˨'8:k++>LV8Zc1:teQָE!"jU '6rXubeGǴ\@ ~hB[CQ{`S(i-6Uʸ}N~qⓖq%JcX&2ցoʏ-ZR60;큡	JzIᢍŠqL[U
 ́x0=1`VPm]-|Hb"3ș9h֢YHu$c7}S,/
ū]wrޯ'g0qHz5GY2<;oRS7޾oyܺG#lq &yBްt_Bs!U&=[/L8t6->ڐendstream
 endobj
-1575 0 obj<>/XObject<>>>/Annots 832 0 R>>endobj
-1576 0 obj<>stream
+1582 0 obj<>/XObject<>>>/Annots 835 0 R>>endobj
+1583 0 obj<>stream
 xWmOJί8$R6a+!&$j{\8)}̄p[*sрxH#Jˣ~Ǖ_>MF]wzqoxqȝ4ㆳ	ϓJף9#g"
4_h2y\2/=E-%,H|ǧLtWN	:F?%Q	q=?z_Qendstream
 endobj
-1577 0 obj<>/XObject<<>>>>>>endobj
-1578 0 obj<>stream
+1584 0 obj<>/XObject<<>>>>>>endobj
+1585 0 obj<>stream
 xWao6_qӗ&A$[8ikm@hD$߾wfBeM&2ɻ{ANc|t>8lg3`t5<
 [fsZ1-n#KzGfE[ZCt.5V^55Vi,ˣ׃3l.@U<\t[e;^`cF^p:*z;{B8o:2Dw
wl1z	]҆)d%rga'l%uI*)و>Q?D-
 \A+kEG.LnXwGY\ڦ1-|k.s!е5K7
sgd33,ߜXۮZs"BoC{HL'|XقP|u6(PXtdܜ$zYjX;1*NQ3--jY*pЂ:FWc^N>%NBah,%sW}ZqӼǓ)gs?Z1/o"d5@&da)G9P%7l)؃vƚAYt#vS	aӌt~R:C`\c+iXhX' &HZJƹYؘ4Λm+	Ahv
 ̈́FD
%e[dnzE?o~c0tw(/Iՠ pXvc$±k:eXc[@0XƒDRhwH/@V2:1aאNUw[t'iqUpQ?Jkk3؆KPdFÚVM[ldyBON "XEf)`xo/!g` yl9	pdač0|}
Ti`Eț(ÊCփu$ZmJYe^ʒ?%
ďAp+ŝVn9G%yqѢw4;S5oD&\x1fiv>g/8nydendstream
 endobj
-1579 0 obj<>/XObject<<>>>>>>endobj
-1580 0 obj<>stream
+1586 0 obj<>/XObject<<>>>>>>endobj
+1587 0 obj<>stream
 xWnF}W؇nHSw/E4hPkEQŒ\Ik\YR}("wr朙їh1ɜF#ZiL'cϒVIʏMZU{yKΛVT]ƶ.?~m㍭ժVSњ;rvoxGvWSUNV7GqJh?	kSjXSo`h8oK6JU"[eeR6:mW{mܗ{qѴ[b Er矶\ʶTf;/W]Cv/lZ14&/mKQ5Nm
MFDؐ$"8u|!<ɉQ$鯏ɔ^ma+.v"<P=98w]g,;0go>ڌ>92fR$"]}>b3m=fz\GZ'ٳd@uWߪܳjp
<|$>4bNҕ+SeW>{X䊘br^|v4_8MǗ2(MFwjodOcp'/mpg/mp}{~PrB4^U,h/FcE
U4E("ЏeAd=5@7Q<,luvh--:8ev3:m	]h)m
~	%$Gf6͵s.L g~et}BP-DOUSlq Vw#=Ѝhiv8fbx~Tg9[n5E(n_i9LmTd'fӡ Qb;@g
 
 C>/XObject<>>>/Annots 835 0 R>>endobj
-1582 0 obj<>stream
+1588 0 obj<>/XObject<>>>/Annots 838 0 R>>endobj
+1589 0 obj<>stream
 xSA!5?_vc~f1h՘Lmxɳ|*FȖsf-/r
 Wr۶}Wt&%Y%viӸc険	I@wmTh:mϙ8/k}4s_c&Vt>Kʪ5]Kfk8[Qzٌ[rE뜦b::;nM'_(h˒6\4zKS֑7[K-%2L[{d$L;dk8_;S)2NLHZFFglusr'9"ZkUy{??QTi
 grSXzyJ7d ]s:p˜2S;++S2D]]Y(ʭ~Bv[]*G[k**oޤnY8aCUU)'/ɩFZ52{ԂRH<$\	[']#JG߯c-Z]{yՅ~xϳ$F]-A%r$j#!{~ccjmn&H(Dd$4$|(t
=@ӃOT
}DKenE}
X/B%-GNzJyϔ%׷:@OKTéCT0qjJ_(2=8 ZK9ǐuϵ$;6+ HNMXq,{2jo^?J$mM]S,wsȎYN16OV>)yb>846TҦ} S+
@@ -3336,8 +3353,8 @@ x
 
 :a5^\H+./^Bvwef=6^':
BHܠeYbӛUn\,jBX"7m*`0-/tuN%ߟ-l*;]imTͻu/L~6vx*?]~8endstream
 endobj
-1583 0 obj<>/XObject<>>>>>endobj
-1584 0 obj<>stream
+1590 0 obj<>/XObject<>>>>>endobj
+1591 0 obj<>stream
 xXkO#ί;R$X1H7eG8|@3mK~}NØ^E𸧫ԩSU~8Ft6)ۃ3NFń\t׃a1yqF'39#iup8xB-V4Ngbz:EExm8Ey6*ZT$TcknH464uT(
Ϫ~YVB$A>|4Apu?iq)Kv$ݭ74e5q0ww(̫Z`:t/+k%g}dF杕p'uG
ٻ%ytdT41l1V'=V[eNGy_ΩfmqF4MwGpnq9[(FwH<'4ܹ)i.<
*%jy6@,N,du/n$	IΤVJ8`A/d56R橆]/81H^MyBpmg41c1נ~Ɠi_./ZO>7fg~uTqX[':sCQaKE(zg}4Sh'(Ohe$BknǨ:PTm-cdiT)cR
3bZ
@@ -3345,8 +3362,8 @@ x
 ̵jq,d)+L\3E})]#(|	W)M'/6tX,IniM%`6O~2dpg_=5,V<#V"}(<1{U1<8,Rq_iJT۵-YgEsAz\^7c,Dl !,~=&endstream
 endobj
-1585 0 obj<>/XObject<>>>>>endobj
-1586 0 obj<>stream
+1592 0 obj<>/XObject<>>>>>endobj
+1593 0 obj<>stream
 xWnF}W>؅EY";±h* >ȕ1evV=3K
 !ڝ˙3g_tc:r+OI|_)O
?.3q(1OOO}?ino5VfcǏ.O8IUhn}3u3U0ՊΖtuKLٵ?SNNЁBst^]Oפm9K.km/ʅ _x@yjÁ`jut_osZۦHJ^x]e,+_h,]unҜn%^6V;bԖ|w')4NKl*LҺRK[j	F;XbMd
 UEλ/Y)@r
@@ -3361,16 +3378,16 @@ _
 +ce]1+t;<	Wax
{9'å5R;9Zy@PX[>t:
s[Rtn\&>Dy+ѫ78+l^>+b}m8!JT=(!^ë]Ycvk?"͊l0,|}ՀB{p_twM?ɉ}4bxi&>s=`z/Apt	t	uykϚ˫
4Q2*y8ls/ZXb&=""ޟuJwzi
 gWoX
xL
*##O^7=&'Sc6n3Ɂendstream
 endobj
-1587 0 obj<>/XObject<>>>>>endobj
-1588 0 obj<>stream
+1594 0 obj<>/XObject<>>>>>endobj
+1595 0 obj<>stream
 xWko6_qhDWǂuE\Hj$R)w.%ʼn0lsϽ2i4SZP|UGf×^z7E#s|S))168;iEVpj4Uzu|<&Xx>Vev\fσ<gϬ3?x-µw69h\{UT㶊r.זi%JTt0uE/H
 U}Fmn)5u.)WB3Ur8$TIG.	.n;vy<M>(PҍR%k
 rKfî,eҺ"Ӓ'{甹x2gHy@ʥQ5-IfJ.uiH͊,WX2͌Ϯ^/z.S]iDm$rdSAL7ݿ9C?^~V;O!%_i(^noL@-V
~aZFc\CS ǰ_.HE[Zp7tzVw/19nڝu7ڙBk=XP!nTqe]i'')Άo\exV*-Q\"u6e3L=K3dGī住GD9V$\MhgQN4zW;#r2ktp|85*nU*}rvy!6H{ɳ[C\kYlUǛѓZJImIdubOynZ0px((;L8~۶ÁKxPHN1jiIP:R_3*1zLڵF*Brw2|
jQhajȚI/P7A/s"?y4||~'mnFQdQI0wKh	.ӔLJUE4!?k3EU1e9@{r:`ABz=+^.w9CO0l|qP0pA}9.x<8r'7C=0Yv'OLf_Sl\Lo?67endstream
 endobj
-1589 0 obj<>/XObject<<>>>>>>endobj
-1590 0 obj<>stream
+1596 0 obj<>/XObject<<>>>>>>endobj
+1597 0 obj<>stream
 xWMoFWrrP[drzK08n =".%(M-6l͛ד\k.\^KR\.j~5[fdb1x>y,.dF֩$rU5ؔOdF:eNk+M]nrɅ/0ql*n
Wrq87Jxl)ylB8vkUcE$.kFH׮梤C/#yTHJɋ{qS3_hjz\,a^Llm%s5S|ReT1CgN
 lr-ܨID5
 Aժ􂜔xW ,ظpi8)tsFV()+܉#¿߿D?nʛ$	IܩzgLf\7iJg
@@ -3383,8 +3400,8 @@ Y[
 })JA"tV0LD!esDVG?K
 s0v/;Bwa[ae|0.,+#x'Ԫy;#dXi1G٬X_aڦ͛㧧Ռݧ@oRf\-g8^_/Nendstream
 endobj
-1591 0 obj<>/XObject<<>>>>>>endobj
-1592 0 obj<>stream
+1598 0 obj<>/XObject<<>>>>>>endobj
+1599 0 obj<>stream
 xWrH+8ı1GCZ	Yb
 4D13ޯ3(Țn>ftsIWJdJW3/oMj9\z2듋shA!tJWΓ5TI6R
5^Zr&fK+剽Sk2o3\z/oMޯL|vZNia[C]&oq:He%vf+!I֑)Cs%KטQX)
}}nP$E}BfouXr
\*iQ-;Fj^DVNdg.\%Lkp*U%L6SK#ًP.EOޘw>
3ʢNlNv+32
SM&)n.-~)Z5AT"UL?to擛O:Mdžendstream
 endobj
-1593 0 obj<>/XObject<<>>>>>>endobj
-1594 0 obj<>stream
+1600 0 obj<>/XObject<<>>>>>>endobj
+1601 0 obj<>stream
 xX]o6}ϯK3 QlǵӾ
 [lv
Dl(Q%xޯ߹$rv($x?=~=4lh6e3?VR^goǷ4Ҫ
~)vF#Zc&ݫgJOWO7vOKiT.O/058a|\^d4_RTkA[h#T-[Ib{T۞?U]c+#j7]	{7|M5Fn,|:8\r)>>EڵD$0BJVxDkxxܩz)Yr@-`ocM8dGd+v{rdMxMrQzEO~T*j˲Ty0g
 %"TUeY3.Ǡ	0h1*Uɷߨ
@@ -3408,8 +3425,8 @@ x
 Y[[+zƮ>bAw~%}~U;1C+nLIxd1m 6mB$0LMF.!聡Gq7jx:pR;7I_U#BC	 DARDŽRh}(
!Fb(J'tE7Lw<ё!@Ɋ^%Sb@l@nySn410evkKPGIJ;AXn[6>ݷ2;?f=ާ7Lv7YBN\<`C(L`͋mtv`Pkb+'yj5
 	g'
ozφrPwo܌z'7i،g\<^po/ѝqL7:q.s?~Χ|vEM:?_iendstream
 endobj
-1595 0 obj<>/XObject<<>>>>/Annots 838 0 R>>endobj
-1596 0 obj<>stream
+1602 0 obj<>/XObject<<>>>>/Annots 841 0 R>>endobj
+1603 0 obj<>stream
 xXMs6W-LL[,+:vm>(2ӁHBL
 @Zѿ)13xX$}"ߎFt]|Je}tV%>
⼘=b<'^h4(^h:5gŨV'0Mi~Ы	F4_ZN>yy|g:Mm4!5TjxB
 6*ƭz[1aJC/|NFoٖHl.D^IwS6*^hW~}lXrm{ IuPlm*xG5W	쉉TNEOZ\ha`ꁗ!~7dKS6m?Վ0s/Sb
@@ -3423,8 +3440,8 @@ ucVY
 
 SI >=(]#pO x˕-ǀ!E?2
1ɠ@L|mw%BGʍj#8adwc.nqffӞ\hj+)/ P C1𡮛
FH[.R6?f4R%ǛN.^r2;fclz9~u/<@|endstream
 endobj
-1597 0 obj<>/XObject<<>>>>/Annots 841 0 R>>endobj
-1598 0 obj<>stream
+1604 0 obj<>/XObject<<>>>>/Annots 844 0 R>>endobj
+1605 0 obj<>stream
 xXMs8WTIԗÖwR)D[1	hZ} iqf*2FׯjN3zA%,:Zf_jv_j\4-m)WXgVѦ,ZV_z5#fMTB.2ʔXkKTKWwt&Uiwtԥ?2/zLޑդT=tI8וqv~Ռ&%ۥ#>Q3n}T9*\jg92jw~Ox6p//+}LVMHd*Gv&:O3[W|swrXJUd#lQ5INN2ͅo7|M2񷏴gsm`)u2l{D`d:eQ
 Njj҃]%mչ‚]6%
vuzO՚.ju-**e"0 7X~"ğ}>+Lq5C8_,D>	zt2>cF{eJP+o{i:\BǙsV48Eȁ|D;&W&d~Voq=
 
@@ -3436,8 +3453,8 @@ J&b,

 $%%F4`zhU%}1kB&w0i9‘ݦhE6KZ6]HX?0	ÇMlς_ z(i峟vW?.qendstream
 endobj
-1599 0 obj<>/XObject<<>>>>/Annots 848 0 R>>endobj
-1600 0 obj<>stream
+1606 0 obj<>/XObject<<>>>>/Annots 851 0 R>>endobj
+1607 0 obj<>stream
 xW[o6~8@1u%J
H׵Cm2Dl(w/lqlwnߡ%o)LPԣ0:.5ſV@e,yr1X_~0J36$MY5W	O
 nG)Zd~-Ml{ZyEce|)Ÿպ{j$n4ӸVyB7[>Ib{|Jm
D@Xx.J>|yy٘+00	3]P(ki`+JQ^uǷ	
1zFJ\E9?0fp+tk5E_
 uOb$S!dM>2ot-ke-n:2^Қ&MY*[Jacyv&s6gȁ63q7c+l_hl͐a\"FRھ!gܹy0C1\n~@\7a#lah	hxJ%\ʌ-A`UAdt"
@@ -3446,8 +3463,8 @@ r
 LXb3Qp0B8:Ke,F5mQ/Qߜ6uD
&ƭx-W-FKg^-5⁹Zl^sRνd= V2\dɣ\Dhenkjmt0Eq>slrCRSRVF Bj0?VJ\	FtGUlP~`ulXIB`F5|‰ػo>^-@j{ÏvN[f C$:*$o*,O,H19 |2d&8=g;W6}q_[
 cK6Y/<0SRo,%|5𹷲4[dl1I/oA|Wendstream
 endobj
-1601 0 obj<>/XObject<<>>>>/Annots 859 0 R>>endobj
-1602 0 obj<>stream
+1608 0 obj<>/XObject<<>>>>/Annots 862 0 R>>endobj
+1609 0 obj<>stream
 xVko6_qעŲ؎`&)2M(-ѶRTI)KR$.8`H1~t b~ 9bD	4DP]X	ֆ{&i8ESxM[Lͺ0K>x$>hʡ%7na`p)Hv2ŗ,JZ晥?TkJܗ6R䊖F7}=Gp7z\s^oDߝW(
 &RQZ^Pk
 K~%=o?ݙTxAvԢ EA{ZRRf2|AJnh%p54~~݅eUZJ2Mـ@@ՃWWya/9̅])
\jR3G"N;wqNA.4p&[K aWؼ\\-)euR|A]ӝ#Zޏ~zty{[gS`@qэO ^ۖk<+sDus ڳL%QHowP!/RZ0p|D7ta=uү9kNE1`߹?w2s10VZCy:ٕn^0@^.ۓyuvkjyL=oT. eBP
G>ik_|mizn 9#-vYx.rNMM^!u2s;t}i@lY*ڏѼЙ敶6d}/\
@@ -3456,15 +3473,15 @@ x
 p1HW07Uuȁ'_STSe[KG'`и{L"4)RsNqnH+Iߺ8gL.4,('+,1nKpa-6hayR+rp2A
hLB!(A,1lȪmp>/XObject<<>>>>>>endobj
-1604 0 obj<>stream
+1610 0 obj<>/XObject<<>>>>>>endobj
+1611 0 obj<>stream
 xV[oF~WHZ1BVZUIQ7.nJ2cĞagaQ|@E6({ΜZpՅ:WBR
k&xc01taԼmkho>rT4ALa2e"W$8hbơ@y甐BI֌("hQu^S@/)(JH
"/@XP
)0D^>8wYkcb~)..`*㦟+""v5~%ڋ7֛d\NnqUDFqn~SN>s~'UНZ4=.tG1|2<.14#p2{CddљE&k^X<¶NrY(0ar+9K>bZj̅^`䥲O*ʃPn?Jlz^נ`u2$;{p@-ѝ"JmVZ-EƖĺn/6"P͙oTG1Mɘtcf8]W"YZK3I#DQ&$O5 STUK fեZ)D]ֱ8쾍VY{y\ݼkSCһz1a;L{{4$[e'/?Eބ[4V@WHS4l~X5ȏ9cs\F 2ze
 
m(xziY/YHTɜ)1MQf}I7֞9C;Wq1x193
 3j1&Әu^q9KdGX)玢s#B$NY[U#LUSڎ9wa#ˉLvY8mͧ)4,]'.R*hU>/XObject<<>>>>>>endobj
-1606 0 obj<>stream
+1612 0 obj<>/XObject<<>>>>>>endobj
+1613 0 obj<>stream
 xVmoH_D4=կI݀ZAhtcoR{7x
Օ.i.!Ż3wI]a4v'Lɼx4)IAҾy2BbI&z>w$su>	'nxZVI*.\&ZyXE?BT%U)Z;Bͳw:A!;ad9[ZV*OKFPV.\)@Z9ҘR);8!጑`|:RF٫:=#^!7^اXR^1B?)Ys
:9SZD9%#b$,ZKrLdQeF*75~+0h)/UHh0UճYICT0944hA=E%u)P}>ޱ@_[ُO,]Ii*pR}@~^zJPՓ
 CwFn\qɕ}P%7Xj5kM
GӉnZk:wt\j
|]iT1e-,s:c74h:v)A,TfVMld,&4IL.-?N6'M,D
 uJXtf``n`PڝF<\;s
@@ -3472,14 +3489,14 @@ x
 tЬ'wljd
 dJ-FL-w춊k޵ykEC7VV=S8TP)_7kwN/>ͨ5ao#6NjtiADѴ~/Og)?DL]ltZ7WQӭ3eԖʞ$aH&#ꏍ_/Еendstream
 endobj
-1607 0 obj<>/XObject<<>>>>>>endobj
-1608 0 obj<>stream
+1614 0 obj<>/XObject<<>>>>>>endobj
+1615 0 obj<>stream
 xV]o6}HlJmdn=dÀ-6cTIFlζt8"׹ܫϝb$4pLiщYLGӉdFNt[/j<ŗ&iv?tb6AUTtIѩVX\K#2ZjCNV0').K.H9~}yl#O2YQpK&[٣
QJjEݒWkۣ6u٣FZRZ$
"jk\<|B3[?30bV~$~~yM"$UrU
 d4m{6>Wks޿?9Ay#ܑ\Ǯ9r
| u+"QTbY3_yF[婻݌(ITȫGryYlSUF(yN
:=y*FKZLBqM,+C`RM%dC6Ƈ~Up)d=bxڥ;-WU16[nIKٵBܷ#A7u.&q2dם)K)@(CmC`
pjP4
}o`03IjXFmQB܄27JPh1r54F^	t0jX {Ɠ
 c`+װUL"p{I;o~/Im(!98[v57v2ǂQ
y^K'Vd:3t(<ԥ%و\IaD˽~z 0}.&J9'paOqn:`NbcT~8:SJec潁.J$ՠ'{^e,ЩҨK!JGZ<ӭD@gˬEɽ4WA6V4l¬w
/K!^+dLu6yN8~kПh/I,}}oF)_~#üK+==endstream
 endobj
-1609 0 obj<>/XObject<<>>>>>>endobj
-1610 0 obj<>stream
+1616 0 obj<>/XObject<<>>>>>>endobj
+1617 0 obj<>stream
 xXn8}W/.v.N@Zt
E[?(hPKRu{mYQAvΙٔ&%]ͨ&ńfW5]K:I˳kNiđ-+	ٚJҋ<QQm\)*d4~l-eTK%mtEI]+YQ1mK5dk˱	]LK=}l
 [mhzo_][d}FZ-N?N0jg{P6Aѽ$)ӯg~GFI_'vֆ_ҧ7*z!Z
 j|
x}I/vN7MqUӂP>~|ͅ_R-UI^ff:\X*EfTVz26̑0*聾4>ː#@W\]Zשv	+ɯ
[:I,|i/M>-ufᤸEYƄJPE@S8&r%ӪPa&VRmJ	Ldc]-tN-Oho!O#HPVFh=T!A T6 1WI
@@ -3487,19 +3504,19 @@ x
 $I
h"T^p\l:2敃o@?M?9jB;)-PpKv&tkpa,;н^k@bA@L23xy_IÝKX=1ŤsA-d-I;7KXŤNKհ#ѕڷ^7vD&Gw;1k\IqNhY
DL|?)+C	yDcw^q~׿t;qNAԞG&N=:
cԮƯML[dYα7ye2빯CF o7oф.;(_׉XX^wvmMħM<-=|yRܛR"}l'wr:÷wW~ ^9?z}p.ƖMɴ]/n'X Q{{7
 =oK|Nng
9;lendstream
 endobj
-1611 0 obj<>/XObject<<>>>>>>endobj
-1612 0 obj<>stream
+1618 0 obj<>/XObject<<>>>>>>endobj
+1619 0 obj<>stream
 xWێH}+J!4[FBQfZi%QnCGvӗLo1dFca}ԩtB/ЬxDWU00U[V1 )Q9ɞ<-jpSN[}FQӃ$1Lٱï>/XObject<<>>>>>>endobj
-1614 0 obj<>stream
+1620 0 obj<>/XObject<<>>>>>>endobj
+1621 0 obj<>stream
 xVn6|W`,_b;}&
``@@K]ԒTCIquj̙`L1ǴtNI9.&hB'0/婅I<`t%m2/"%ďc$g~|4I>JLѢ QPۑIm?~YF(EL4&oO?U¹~&{DN}j7~'Dמ$tWOsOɱ76Nkt;!p2gHΐHS蝡BiI"%J{J o
ғU(-#9(Sjm!)䆤]C.j/ܛ=d뼰V rʕQb~gM]
 D8˛3}A\>!Ƌ?}R!Z[Q
 	t]n@(g9Bп)];)~vM[wp^rev\pPIziP\Be T-JpuG-oQ@sV~N{M2/$L~v3m}V	GzecZLZuD4l%Fh5e	urK#=?ԩFI"Zq5?8đa}8l*@=RG1z\C*ڵ؞BEnp9J[0[L*+0A4B95gkNƛCXLנg=Se*`	3%6ln%Ր!S`8͔k쁧MuQ-L2dښ[;]+m:dٗ8B-tA/`_<\*x5Z43ek2j`~96UVPr7R2R<Ÿ+,:NaN-a4i72_;"GPw'=?N֥@Tk*tk<=>\sɟY>3,8 'E	`FyKb>1^Ԕl>
M+#Tqgaʬ4C#5Ledk.Td \@K,kl=f<dzrJp>^у5qҍIN宆"ⳓl<:x'|tIendstream
 endobj
-1615 0 obj<>/XObject<<>>>>>>endobj
-1616 0 obj<>stream
+1622 0 obj<>/XObject<<>>>>>>endobj
+1623 0 obj<>stream
 xW[o6~ϯ8oN[If
P`I@7@KE5+.(X"{R^՚b,h.5npu{\?щwZ.hC
mrB>.
 8i(]'t:9=JwD-꽬d^m=+Jply,qP̜5	d8KNSOR#j
 iDIVi!	Tw7qt>Z"T3ic9ҫPh:܏8n<42eZt.hCBRkQ_5';%QV%ʌ–*s$)&	yCul*Yq{4;]Ծ5ӓ
@@ -3513,8 +3530,8 @@ $
 89CO1a=W
tf7yJ7#"أ9n-T ~Q ya,9e_U_(2NgS2~igtE*3ꝣѷh~
g
GeΊX
 *{,zuYNu{4ؘF>o6j6%춝@2xSo;(v;!ɩG2/H[YY\OFp:QU}@B6CCKoQA~qj>/XObject<>>>/Annots 868 0 R>>endobj
-1618 0 obj<>stream
+1624 0 obj<>/XObject<>>>/Annots 871 0 R>>endobj
+1625 0 obj<>stream
 xW]sF}o8S#Ўح[;I3SaZ*sW&t
#<[HZ4|,^ZӠWOgq04??![	^0<2!]/6էFl2
 BA7i@xD{ۥYrXp XʵԎ&|p.JYrdI)wd*yQzIFӻ?罥sp.>3KϯҵʺB84n[0K'w*MAy݋W&Nc!yj3QdŮ$I[Vw\ EVe1$$ZWl$L+38j!!
dJH[-hgJ&"%6f-*h.)/ %p{!hhiN8S:ŕ\X5EZW%\5.8ʇQ>HY!Ek]Qq\Pt)d̹8nX@QF'Au
\x\+ +-ve`K:7|].[Z%{	't!t#YJ)/Qĩw_?MZ"]W}ު]I5[
 =ҭRYVo&לU[cu:
@@ -3526,8 +3543,8 @@ Y
 KV0X)V-?~7):E+',Bpׂ
 sSRWSѝ`9:]Gj>/Բ
qIQѼ{sV(gM
[Zh?2Y^ *Zr>/XObject<<>>>>>>endobj
-1620 0 obj<>stream
+1626 0 obj<>/XObject<<>>>>>>endobj
+1627 0 obj<>stream
 xWmSF_uajf7lN2%`CN?TpNSNOݓ@t2aO>k	
iB.q;l4i?qN}pLLs!0e#d"w2Dj,R xʾS2K#<3\M+ԛ]=A`9EXq}`IcfO>Dd7rtzU_qf8yi#cB$"=	$@(wp#e:4.')c#zNyD)fC-3s/@08ere"ˤΙ	WusLNrEdqnSY@(VwH@ o(fI߿wl^`Z]SD(KA$(AM\V44PDp
/а~iEbMFh8T޵ͮ]=e0F@XrV7nm=Sxa:%U"5풗&L09I |8FE̱X Is/YXgpxikRX
:'%K+)
2B:͋X("
 H07ujKBj:֊ռuv)j67y'9TJ$Јj-\${,WW[.Er|mVxvaeBxGO.*CfG`2E1޽w2-dkIpm`i9%N+
@@ -3536,22 +3553,22 @@ x
 +T'b
 ߾mi/4C;*wzq$&~n07nOx*()vIRІeG~rs?I	?? `Vp`O[zaxF0mNBt!jϞz%|o8E5|&I~mn鞴p[
ZL+TrQͱendstream
 endobj
-1621 0 obj<>/XObject<<>>>>>>endobj
-1622 0 obj<>stream
+1628 0 obj<>/XObject<<>>>>>>endobj
+1629 0 obj<>stream
 xUmS1ίbgЙr'2S&Adj{7zvMgsWM:.i@=jاBR>c#]bxݷˣO_k;(ώex|^fýxZrND?q?ř+7:myán=;G/='%pe
l9!a(E. D!B
0H1)#1̤wp!
 %
8΍)3ay!l6Ao{-KS*&})FQ'h9aS^"Ԛ9U
 -;{\LvRN:q'NAl\ĶrT딖66u$3|Rȅ/EEqgQ=犎:Ēߪm&IiA`T		b$G^i3Љ\#	[YLS̭AݲzCo:SLjrpĄD#դQըذֽjmax0LfjhS6ADߴnW6u-9PŌ
%twDT'v)%$mU.xh@hCqz.g:q7Vendstream
 endobj
-1623 0 obj<>/XObject<<>>>>/Annots 873 0 R>>endobj
-1624 0 obj<>stream
+1630 0 obj<>/XObject<<>>>>/Annots 876 0 R>>endobj
+1631 0 obj<>stream
 xXoFb/qdYԉsUNZ.=\uwiE%%mAbSo޼揳1]Ϙn't=#]]eWϧgsicC(I׭5`B2HSnEWUXyi8%]#
jKhf.|m[6YbSC'۸6AGݜzXt3kL:&4]N\fsRsKؿbV%z,i׆0XZ/)b5#o³#(LHrs9bJPkMZ87y>d*Hq(J[QǍyN=^e
ϯ(Ր9agKoӦ5|t O{2^5K|m+E&09$GY~Rwg|d2}wA1sk{	Xt\iu%0 V^`.dÚH/b@شݭ&\f[	#ˍ!txWzA׾
9x|S!
 }!u^I<Խf^wL;0gnOendstream
 endobj
-1625 0 obj<>/XObject<<>>>>>>endobj
-1626 0 obj<>stream
+1632 0 obj<>/XObject<<>>>>>>endobj
+1633 0 obj<>stream
 xXr6}W5[6uvޜ;3vITHHBL
 ZtvDO>_Gcߘ'4QZ}&tvq'_jZӳQ2tz+~
oh<
 Af4F#+ڻ2G
@@ -3563,8 +3580,8 @@ B
 fn8:A
FV0i84]HֵJU)7,®Nc6(*T>C(K+UHa(aryX0w}B|a%kfY!::"-اnYq銉"pk(KY9;vL96J۴%0@;h2/r|3a',4YQ3>/*ji%WuYWqzRiڗX5d
 %?]K34@ņAFH41eE1MT'ivEu(=}uiŕ|a47Ak@8'ޤQبEVBVKOA]k+2XH++*Pd;OW.l0*x"4%C(N{vFf]׮]L|tu$6._bf7`^6r
(endstream
 endobj
-1627 0 obj<>/XObject<>>>>>endobj
-1628 0 obj<>stream
+1634 0 obj<>/XObject<>>>>>endobj
+1635 0 obj<>stream
 xXNJ}+Rbr>T%ВJLI23cBן\
 !ok_G}OSh@>4͏~QOe;Gc:?Et>nztz=~sq>iB04>.vTZGgG'ӟG=acՙfڽtDMMI5\e:!>szdzeYDwƅc6&}'MNaY݄jwCwl?4E]_&Oʋ!@VR>6M[2z\h:?{Cfw	$.98{{k]ѪK&㍴;bt>??LҀiendstream
 endobj
-1629 0 obj<>/XObject<<>>>>>>endobj
-1630 0 obj<>stream
+1636 0 obj<>/XObject<<>>>>>>endobj
+1637 0 obj<>stream
 xWn8}W.(8in\t-Q6[TI*~%QEıȹ9sf`JLtFI6$;)ƯTʃYv:nyp
MOiYlJ˂`2e>f.Ukct箵kОn\erwؘW4[ʨ?@TXMBsSZ-P1v )n%Pmȕru-^|>/XObject<<>>>>>>endobj
-1632 0 obj<>stream
+1638 0 obj<>/XObject<<>>>>>>endobj
+1639 0 obj<>stream
 xVr8+(WIHzI6E-%@)گ!EӖe[Ӄb+yBeq4&4]w|Wwi]l:'i
y4ѓK&/zl&S慾eWpS#y4Cz|Vk{#byK4<*قSl8upZeJ!yIpJPpTΩB ͍ 5Jfє/=H+9n
rglkw'3Iǻu^ZҳQ	}Q݃1w쁀j0+`386]WqD>kiyd{UHʑ2{2`V. <ҷ'9!9n`/jg2DYj%r'd%q`'|8$b@yGVm&`g'2`W^h<9Q̐NG[0/[(Xgꥮ.%4X4}e"UZm(N)/d'a?T$}5d]vKm(O/B@3K
耈H-ݵPx-AIq<dVw!@*ųlU#23&VQzD?0Ͳ딸WyL hPQQ#]3LJVڏ=}G=$jJhG
 rX
 L';88űe֛YWo$$
@@ -3600,14 +3617,14 @@ jF
 mwYplA)qjFKE"6/r[v;EHN'L&s A DlD`Utc[dGg^Obñh
 mc6Ѽ*Q0evVӽ:%cM>.P<Żk1!h|3a%>_.Jl^Ba4Ṇ+8(=ȦE4IC8q뫿;^endstream
 endobj
-1633 0 obj<>/XObject<>>>>>endobj
-1634 0 obj<>stream
+1640 0 obj<>/XObject<>>>>>endobj
+1641 0 obj<>stream
 xWo6V ز%;3`v]6^ں؀z(hH*Ru)ʮbR%ޯw1/B_Hs.=adؗW᜞+z{1	&4σ+--)u/p>p>
f}1~qMф)қ/NyL$<ۉȚe@ϥ~0ZY.V^4O[/yMgq`N"+｡vg|f>7SOX޳}uJzw<.w<4Fdȴ1.e7	g$zcdQqW|HmL#TatXfEaQKP$GB_ӏMr
0	hr093\fqn"}w(f54ƨrol}d؅xvhdA :%;m%'6GwDِ$lEUX6|7k87>J)r5$i/BaKqaEt+DVq[yrD(]"UYrV?axյf/e	kΛ+a~<~vU@@ks(j(⻇21bW}`ٶ-t
 o̮n=VIIb;褎WKOܤpO78v(egˀ٣Lz(PKs~ý
 \bp4YUvv=&oNM˜ֱZdz+BJ;#_ɄtڋC8.,c~:}8_5nABk_9޷z%G+\'ˈwY.8ү닷ECendstream
 endobj
-1635 0 obj<>/XObject<<>>>>>>endobj
-1636 0 obj<>stream
+1642 0 obj<>/XObject<<>>>>>>endobj
+1643 0 obj<>stream
 xWkoF_P$ZmE.y4hIamQʼn 'zm6D䩪L9mز?eG=yF*{NC\ȽSN:hz*wykI1;$9A
 3Ja%c),
 R>V^*7)u);s<=07r֗uw_[w#lws}$#i59z)EHYVm4
@@ -3620,8 +3637,8 @@ x
 5#ק-=Lvy~lGZ/e7tZCPJyoKOXd%͓׋5`:"/_:跣endstream
 endobj
-1637 0 obj<>/XObject<<>>>>>>endobj
-1638 0 obj<>stream
+1644 0 obj<>/XObject<<>>>>>>endobj
+1645 0 obj<>stream
 xX]sF|ׯK*")&uJXkXf =@P|WNʔ	t꯳MgFs\PVM8%7tusso$/.>]lF5^Y\2'<>2;$[IO3]ЃP)ӥ{0vWN!MJXI>RU>fA,)Mf229LIUQ7#~܊r%JsDVl4/05ʨxp#J;rQFjh\K[qHV)j'!|\q˭6<~TEd"ۢBg(N1ksG-bsI
hMZ;P9꧚JAxD_E>YqJ$RYkOXZ7fz5~8Hfۻ7z PUhd#]/&u_\P0?]-vڸ*yn`Bt$:}`vx5?
 =	podM
0Pxȍ=׹ %UkY1=t?͇YZR5*ǿ1qۢ:lܣgRLUlOFT*]YRpӴU{2jeMHq|?y)Tfp%gL˞) e~tб4VA
yl*\VrPCצ	1ڻ$!r5V,U)G@$ꌪlɀ8_m*{wNdM>\BU@Y7ےK}糄]dxRz߅>,?o~w<~L4o
 &&iKWeAv~gx͜p,Bo0d$Uoѥa+D˘ S0!%ĉ9uzJ"˯t-1/K/Zl~l9LWR`q*'L^cڇ(/y[p{BJGݲ7)۪%	xKꃏxa-B%g|NC"Cō'	b|{ڪԄ$ݭ=&(.8;<"~c_g^x:DrCDxy%X)Œ
@@ -3629,8 +3646,8 @@ T3
 ,10%?%AEypx1ʓ+h
 x
ݺ!Q
/SMԋOonY2ǟ~Pú9tzqk;GHCL?ph;h];x%c7rvJ{wzkt3efH.)$&poqF!{]ygLu>/XObject<>>>>>endobj
-1640 0 obj<>stream
+1646 0 obj<>/XObject<>>>>>endobj
+1647 0 obj<>stream
 xW]oH}ﯸK)/д-d	MIbj{gLȿsgl'1 -TH{9z|:tBq~0F41o%iqs/psoJk'7}9w?;O{\)\ dzNaBHr40>
 Wda
-TE?݇c*+H3I&AQ37G}H+M9KUq৻qܫS&G"ӊJ
 #Zfǽ#F0Ր+)SeZ,)-J|R#Uj~L{-jQgY/v[c)6:ETY"+c?KJKҩ+tpj(O+COɋ^5Q	oNmwiw-A+#fdYtO]|nLL`VYۤz΅WzHBZf?KlT9^R	|42QC
!5ZfƊHd
bPћBOQS6wFkd[!N'q]U[BUM(ymdN
@@ -3642,8 +3659,8 @@ W
 J>W`!3OrX˿o!i8qE`լ0%+rJ>pŵ7lzMF?|af3r	S:>]؟,ɻ_`
 >Kendstream
 endobj
-1641 0 obj<>/XObject<<>>>>>>endobj
-1642 0 obj<>stream
+1648 0 obj<>/XObject<<>>>>>>endobj
+1649 0 obj<>stream
 xW]OH}W\T"NoYU.q]=N3gLȿc;/ծHUUs9w~?N(^ϧl_H݁9/޴}p#}
 bϼAߧl'3
 "~cL{]R(Җ.tS$LDJ\H>ĞV*dʞR4ݓV$Ey|?Sz8>DIj;,Su]t~]EZUzӂLٍܦ]{r-leG߾kEbC
@@ -3652,8 +3669,8 @@ bϼAߧ
 6ahpe%:җ֢"D1TP`s_qA 1Ȳa!2"_5KLk\RחFLq^ɫ?|or#	2ko[Etz~\LBK(`5&14[$xb{0t9Dȣm	UwN!ڡqQ|3j'omoua@ZQDΫ/0Úlu1@W.2E2:<%ϩB]v.>겒f>JjL2Bx"cǦjߴ㌜]fV5o`v,_./[_oc_c==Bzs*\uw'eQ,<}p3d+@zN\%%'zxGErNu@7@F_Q?^ᇺ,m?B9z+\wW'6
 uF	;ޅԛ7O~EzFHlwP-ea]yB+05oMaP{WjJ0Mz{h6搓7o:Ȼ2-TY?~>/XObject<>>>>>endobj
-1644 0 obj<>stream
+1650 0 obj<>/XObject<>>>>>endobj
+1651 0 obj<>stream
 xWkoJ_1R	0Hyܢ4zJH^6]C%ꕪ(cq̙3O1/L<É7qK<=
ӥ/G}O
h4ǯr7yvqqtz=+D4Nh<O>I8T	U֥wGH珽gեBet3ktH%ֱ0a:ӼtdcQ!Z&+JD nDo4Oۃ+Ȣ밎ԜZ	U]ʥ.(rBєVȢ}: ѡkF"-4I6qL.֣pBokB#7Z]I3^.ճ4[Nv>\%u˅_>I#
 eUBMWdϴELW$8^˰5eaADX"V9my8,#QŜ'^r炡]:;hvG'omH4ݢ3P*Ln(6\ɇwu~X.Lru RE'qUb4!??~U5AcB:b
 ܂߮7-q!@x\0Ƶ-JWkj=
@@ -3666,8 +3683,8 @@ WJ
 KLH.!X~% C)4ɱC idRpk+.*`b[@-qm==7|(SSqa'Y+6
VS^
'-JG63-y
 >F>+]bEz8Cި	ɟ:,&){y7qoݺO.LN~w#yls4z|]-Tendstream
 endobj
-1645 0 obj<>/XObject<>>>>>endobj
-1646 0 obj<>stream
+1652 0 obj<>/XObject<>>>>>endobj
+1653 0 obj<>stream
 xWnF}WR(QuCŖ۠
 6&w.iI3KR&(45;3g,?}(H~?[~	So?v?WtcYhi8㹏?={~0yyvܿO<iQ{>&WhBːpףepE2
 T-%1eR&RP2(LՅIY
@@ -3679,8 +3696,8 @@ I5
 xw}m1UkZ*UI/X#tlk0U%E"6"MXgrK]w\
/!]PK5M-/!
r!1p9z0zңvp
3Xqlx9(.Xޕk^?4URIRTQ
7Ax{m\>熰w$tmҬ,5o`l@7n?&axM,X VV49zk jh'wC
wSs{w>jvp=]~ZKHbZݙ8i}Gbmׇ7T3s])Gtw6'ja5xIM>zjpwJOWݤ.No2?Ìtc%/fT9l/]|y_[
 endstream
 endobj
-1647 0 obj<>/XObject<<>>>>>>endobj
-1648 0 obj<>stream
+1654 0 obj<>/XObject<<>>>>>>endobj
+1655 0 obj<>stream
 xX]OH}WT"&_ЗUJӥZ]0[d28vq4+%GxrN~Lx#?'㇮(k),0pq.b
 (xS6wl,E -eaf8!
 9sZ:=g|?Dp׷7˫/YDoRMRcTr]Re*L<:kj_(@HdIaAbA0X:
I[iŗ$gHCeST]Lƽ-LE!	4~*&B3JT;E\
@@ -3688,8 +3705,8 @@ x
 TZ(K2x9;ץB26'(7ȁ+<jaMb>"'eiS
Ȥ:3Jo$ap[HK:z\k%_Hm_q1[UrDh"aPo$Զʘqy"zsۧ\'\o(2SOW&'\LJ4AҺ7mrSDl1:1kKjl4I,\ TӅ7Es8wjfvl1na@᠔6; mHk__N6~gtLx6lMqWaxAs;:]a;+:D;_U@N_s87;P/oh{b,>TMx8 ^̿vNN5Fgt#kҀVY\бQ\HlZr:Vyah+-T-0c`7F}n6ss
('Gnt{x6c̵>!{	@+]۫*+[t+nv17rrBe/a,kK)jū˴p5%Rq0V5`v;<
Qx6kɹF"Iɟ ?3VmQ|˰;Ki*HV0oG&'͙i>/XObject<<>>>>>>endobj
-1650 0 obj<>stream
+1656 0 obj<>/XObject<<>>>>>>endobj
+1657 0 obj<>stream
 xWmOHίUBJ%&!}H$pӪ%؛kB|ɱwg?ÿ>xAz;p1~Oz=8lX	wZ@XbmL~Qi!lmߗ6:=wTw0rh3]8VlZ,i!悥/	IJC30Y29ANi΅Їk|pp=l:fuh0KSqiR[;~]'?˥ʥ}=IĚ~Yr)ow<9cAn?!'<QD0ŏLف액ڪy
 Bf"
 (er	
؆|DHt0MQJ2
@@ -3699,8 +3716,8 @@ c-)*^
 !=*!z$3hϮ_YWldw=LiVyalf~krՃ6-r{2gjP-ϸ"l],8{.ް]-di94hʳMs t rg'Zerlɯ#|ZZr7r'GD]w3_5&QߋT
7	%2ͅm2w_Xe.//`BE;͎o鍏a4:_,K}'LCid[
 tO{vcgGۏO3:gm;_<*endstream
 endobj
-1651 0 obj<>/XObject<>>>>>endobj
-1652 0 obj<>stream
+1658 0 obj<>/XObject<>>>>>endobj
+1659 0 obj<>stream
 xXrH}WKP+ŹjɅ\[XhF1==%@Z cOt>};joPﴣ6
K#⧔|uE':Ó>!]hza;:|xxM'4Nrp	vu.f"K;Z+;dr[TeL&gYF,y9ӦVhI1,g3_{YQZEU~3|߀vx͐d.|	u^GՈ>"KCv[oЧΥFvZ]ur-ѹaB)-
UFR"SQeKZUܧie)FBh댌R*3҅/ンp	yeZ82lEisR,W~plB8cT)\Nt4'Δ,`du#Ɲ>vBnh)Kы$W2VR2pflàI.clWy9!xgA:Sn_e&{oo䥃&Qt	i.DQȥuJc9˴IM1EjUWp.4#!*UxԯZ]d5
-FEjtǚ]&P}ϑȧСTL>	5Q%HF f,@bS(UFWhӏd=P44MR:纘hXճ77ȯC2T-037+U8ĄQIvӂ4T"u?h܅[Sww酙})9Kwu&/T#{a;`,[@ѷ-
@@ -3709,21 +3726,21 @@ x
 Ϙoz>xD
S
 '7W*.o\dRv,G=vspy\7eg{x?z=.aS>[,ٴ,ZGm~7Oq48o(hw.;=eendstream
 endobj
-1653 0 obj<>/XObject<<>>>>>>endobj
-1654 0 obj<>stream
+1660 0 obj<>/XObject<<>>>>>>endobj
+1661 0 obj<>stream
 xWmOHί!UG}H!)HkO$[t&3~#1u.I;3<3%]:qdlh4c/yh/ >bc};aA/+
TZ2idH4X脺^/-%{(iAn(4	SԑȜIS
%Bh^+\d#UV/:tN=DVVE㓈3ق"-Յp6͝?ތo1vhs-ZEWC˵rK^ 3vCWIeڦݘƴZ
vLYU.[GXv%j5ě[]	ve
MU2[԰&buEDKc
 Ivn4\?MUzۀi*nV$u6}'YLmqEӭYȋ-̴m|?Z+GA4[dˆEk,$^SCB<
K'"%miR^2U1JWwPC&Nt0\t/ÕCyBlƢsخCIΰ~JW6QF%kDŸ75s&SRh\IUDLI,fHF،A9)?}QZF'RGx)Gk&7384evkO\?#6
 sU7͍%XPAM&\HrD0	=[1zzGO~wl|H,ڪ\|5~ޢ-%1EV]5^`5hunFNr`9|4"ee7L{~j٧/
|W|?uNK$ζ-NRKU	u5R'ȑ2	KNj"y(*TA퀶ٽ-eRޕiL-Gj^\GK>tdiQk TJMul_+=i,O7I3dA.uNڥDZW$_Ne}Su((UUJ3vJ!IKG-o{tyL.ؠw>|\h[z4zmWLVٞ
 %%3ei2	,m+ <ӣJ _-˿_^ߜW!J?inX֤UBLfApYP -|c_rK'K@1zlnYYi;;W0057KVt:'v*'Nh
g{Wendstream
 endobj
-1655 0 obj<>/XObject<<>>>>>>endobj
-1656 0 obj<>stream
+1662 0 obj<>/XObject<<>>>>>>endobj
+1663 0 obj<>stream
 x5OK1XIvc
 
 fSwKOwa`f3TFG&6+Ь/{vlBJ=I5p=a|w
(C@̾{}>bcW@b(GN|[@]jJ
nYCߎ!9UNύx
f1yB	VՖ륢*l8xFendstream
 endobj
-1657 0 obj<>/XObject<<>>>>>>endobj
-1658 0 obj<>stream
+1664 0 obj<>/XObject<<>>>>>>endobj
+1665 0 obj<>stream
 xWMs6WLX"۽934qX\|HHDCJֿ)QN${gğ	]OjNYuv9w7f7=?i%/&xڋgo?+_"'ؿēlPuԞ&cd+w2	REl(LԌ&dbzIUKuqEkcŌBܕZkQ1-
 WZBEQ0Qښ&h2+|w%]Lʬ8d]E槁e:]Fӽ:yXw-U9h2*NmVF闺|AƮYƮI`;M*ܖ>s>剾-Sjv]	6]K@K#EaW>+Pi@34
 1V+?0`]-MaH/X\BHT~&$\w;
@@ -3732,16 +3749,16 @@ Gڐs]
 FQ;8=i{ʫܬ+vA#
,՗V5e}&zm-zAP-,uK;C9~тZʂB+ٶNkm˛lM,x\hzYG4(͑Q
 f1+8VgMvԴc-,5`&lTcڶ"b0bl%̼YJq.9k(Piqy;3G/&hLODz09
aCG :dMfi&[t΢Sq(V!h!1WiLIcRRBR]kSQ$/<}cSN@2fV	"ΦFݪ
Q/n
5`%YƄksy-[4,XdUhL0CDL(GB:'IHeآ?Aa
ꊦ!QˀŐhND'$Vh2^=<*unׇ7O`?dRoK#4c:YY!5(0.c:wbL4Zbk|/8tnx2&=Zda c(VeS^1v8Ԇ[ah9]S%v*R,:t]\bZ찕 ыqaCvАZXfHJ.p栰|7D{!7,5+CK"U÷b︒/Ǖt)lX&NdyqўJ>ړsPgWf.,{|kBt&\>!^mpLyowS\h1g&
endstream
 endobj
-1659 0 obj<>/XObject<<>>>>>>endobj
-1660 0 obj<>stream
+1666 0 obj<>/XObject<<>>>>>>endobj
+1667 0 obj<>stream
 xW]O9}W\B%}VC+R>8=k{HkOTh~sO&4.4[PQGch~uߧ5Ѽki~)	cZgt4їTѴm>W+c^+yG"%p_/͜&f8{m;9'UUT&bUlؘ&BkzxhG>s4_Meգ#Z:ӛc[靮ݓ>J<L\5nzf.[\ٞ͠_UD'%stхY"yT!̓z]nM1DRB#xHOsvAcBB]ؿԁ2N-Fjv9>/XObject<>>>>>endobj
-1662 0 obj<>stream
+1668 0 obj<>/XObject<>>>>>endobj
+1669 0 obj<>stream
 xW]o9}WծD*BѤ]Em!
*Ě7MmO(~|@GyX5UPlsν44P]ѐk|⿕
CM)^Ec~uy_ѭo}cm&Rgl©^MaC4OPrb:b'@ zxaWZpRC?CI@65ZY쎕?e%؀ CC"Cu'5(Kߕ'Gpm@mG_Dmȩ)3XcM&Џi	V^A`(|DάC->]Kl9m&ial$8o^|fW[a5'w#RR#˩!de9P0D:EfX+Vr̩410Z3(EQa([y=oV
Fye+AVl6@5
@@ -3750,8 +3767,8 @@ e
 u4Tm]E$xh8)p05_,wn<<.q`šl+OR΃fބ⍭O	vxbaSZr]uy!fZyȞ.T ˅X/]9R^o=][iЍKE5Q3l
{QJBm+:FAL.tйI1(>ͱWpE$
 02C08u9Q?\\9?/WtHWA4aH֤tڇ
	?LGԿ{'hr_5(fkηZendstream
 endobj
-1663 0 obj<>/XObject<>>>>>endobj
-1664 0 obj<>stream
+1670 0 obj<>/XObject<>>>>>endobj
+1671 0 obj<>stream
 xWn8}W]4e;؇-}%"]~!)[v <Ħș9g?r/1M~P~*ȳNdS~9_GKΆohXSE6A7fb<aBKlPE8[[~]La>NsA”*R#sd+ۨ're~ o5tghԚ#z#UVz|L]SV?%LhIn1}e%;G`
!oiGUJ;$@\n3ɘl~&'GUH<4
 >Rl0(`JY()¶!(HGh%[ۦ<\
 /1WH`(}1™mXV3j
ႀ0hroyshpy׎Xl`&9Vj@u
@@ -3764,8 +3781,8 @@ Gh+
 GTQjZG  a'`:@^H	u3N6ZI
+1,j9bWʶFkӨnJs>QƯ
0ʜ݇qetrcFgZuȐ|c|zxF%-Тad()l]c\Wb`xt+(yQ|w`l1@4ifIƂZ]*M}1%$ җ16DzyLxFl*KۈEcM㩅ҧ-J79Uuyy^@*
 zW|&IHnsK!cjR45,r,Ak@/d7?''t/ue\Í;En.%1~ҢM+6dE	/@ mh*S趔kݥ73ͻ{pe;6XÐ:*U״6yD|}
z	s~ClܟѱTd۶m$~߁ekvk4}|R9צ yD"3fCm2%7Nb^dWS&ɘ~};wendstream
 endobj
-1665 0 obj<>/XObject<>>>>>endobj
-1666 0 obj<>stream
+1672 0 obj<>/XObject<>>>>>endobj
+1673 0 obj<>stream
 xX]o6}ϯ@14j#GP`R{+"eD\Re'vWذ(\{o'S.gtvAiy򍦗,irEo|70=>]o&^\ფI2LhRZR73NUM5TɄF	n]kR'¬|CyRImkZ.wN\뗼m+Ga(xL#XB6V.kJ%Eik\"ɶɻ~XGN>s|r-l:rN͍o4̌f\E(3EaֺZze]ߠښ%YU"Udc0
{ӧPWKO4uӜ`m\Jy0VX
 tjqE=C:VikʚuC pt1p
 \=;{'Q.6̐TUNq&kTM(/ܞKhkϮ1PR@}qaRQ;5~w^(f $9x2kt{2/&jUI|I|2ͥB*tƴ@ߎUHn,*vXFZZ"MWe%dAȩMCCh(5e`*ن#CBr#i4bOTE*҅+2\طR&]=(ȡ2kW}k!g)k&Mn,?CR{kwt4'{hLx3v!uPƞ>>gϭPƵA"+#U!6i&cT9z0;ЛFm!,=%2hSC+bC~KxYTjUpFahU>=`gvh-t<9*6aA2څ$Q0LQyK8QIZM:;[7cIxjj]7	"."ԃhq4_uV«ALe2?✩ԃŤH@CR&ڕ9a1|WZbzWy9@"SDWC ōJ=6mD|aBwUowbGxpУ;^&fC*yFPJ+a e**Z,uLAsdp-ޯښZ/n HGjS_\'䢉eD5M(A?*Y+
@@ -3773,32 +3790,32 @@ x
 1/3Sf2dϱ*~P#e"0J@ZH+~<&\yZlX¯uo:m?ϓ~Aׅnt}
 Y~bcvzqLht9NBK	PJSd]W[Q	&e8xdHendstream
 endobj
-1667 0 obj<>/XObject<<>>>>/Annots 878 0 R>>endobj
-1668 0 obj<>stream
+1674 0 obj<>/XObject<<>>>>/Annots 881 0 R>>endobj
+1675 0 obj<>stream
 xVMo6W̭3e{KSlk{	PmqW"U}#ɍb"͛7o(=)_L˄Ҍze*R):tJ,
:Tie@)N6*N5%{nn:y1l-VêZה+;˻kX^Ų*i6_nqNqL%HB,NvTuq5K
Qt!ViiDГ}TA6w=%kVR!$ZF::BeA/)C|(mצ'{>|ѕ5md^x{}z߯eUs$MAqH/We{m^
 %ȪA+0gI998S-<*@\^xBMz+KCp>me7mo/w$O8{t}MS
}vyY:'Qu9S)_!Vҁ~c%Wi
 eW?xq:wCM4S9Z~e*s-kC( +0IBF":MpSgk„9ٽ
έ(	el3}v ީ
w[6G̬FQG4|טtϛݏIH[Y%s
\KطMc]Z(1ٌ8[/w%6UP"OpS0nTalXҶ 
$s۲0x^y=G3_Y+AUaI
l!,O(-kW
 	RZؘ"^EKb;|O`(N8߉$FBaݹ	tO?R0<ٖEF)k[4]9~knĤVy)qט#U(>?R^^_^<">}ȇow^
WtžJ)MSeqC˃l޲C{.!eoy"$9e7c/גendstream
 endobj
-1669 0 obj<>/XObject<<>>>>>>endobj
-1670 0 obj<>stream
+1676 0 obj<>/XObject<<>>>>>>endobj
+1677 0 obj<>stream
 xVn6}Wc%K)E^
 q-EAS]ԒT}ϐ%m
Q9&8ʠ!a*z;'yJE18ٜhׂ&fx}Y^.FqO{TݡBt{I	V_z%iTLRBJ=9qR9
 ړВY9OiEۋ̜25m=T(ɒgWy4;D͆8<2t؞ZxV9y;:xߐ[ON8\d*hPXR('05Ш=ޡ20N`-G%|VzPQS"	yF8MQVRH!au‰V11;XrKr6kdl6_SVXmF:}Ȯ^Taklkz~a¢u4JF%ΘkBߟts1}_A==9ƕW"u7q8G7LOp;#s(8
 =TUNQNj*	OwJZQeeF1k9g7ՠDR0)]͏XtR1!,Gy,,˲Y.U6FqhS`_#ѯC0m4OyPt!LZHO7
n'-D0tH"NJaA,Y
FNn}4CL	50a)VFC9`tLa?يdiiytln6nLq ==pO)|HsRCսtwS|
Uk:_dYb2Z]rÍ'Lendstream
 endobj
-1671 0 obj<>/XObject<<>>>>/Annots 883 0 R>>endobj
-1672 0 obj<>stream
+1678 0 obj<>/XObject<<>>>>/Annots 886 0 R>>endobj
+1679 0 obj<>stream
 xVMo8WmS -)ܒM.@@KtD"$e{߾o(q\
 mJ$ͼG3JhOBf4SHd>8)Zʼn4[I60.ϗ?F)bF
FI*攧P~3/O
޸g.%'X!|A=NiQ=mQG,?$闏]KmO[vWPUIl36OTȺR6AB!)ixBvIh+X	,ɮ`Pi@aKNk[ؓmƟ){)
K+?}Νj5
 ψnntxBN຿W-lWTg^7xz
*cd,7DQAY?رq``18$C7%ŽճeL3^6K	~?MGc2yֺ#(rQ	t-lJX[ R
d)G*#u*o~P\Cd`׈N\ml!=cz| f'k㷦Ƭ|Ga\v1+pq	Vĸ8~xNUdlDr[[	UvQnRV~ME[ҵ}rctQńah%Cљ|\r)˱5x-ڤtLṗ2qgNd|tyA}Dҕ-:vX1Mx'YFs=nendstream
 endobj
-1673 0 obj<>/XObject<<>>>>/Annots 886 0 R>>endobj
-1674 0 obj<>stream
+1680 0 obj<>/XObject<<>>>>/Annots 889 0 R>>endobj
+1681 0 obj<>stream
 xeTKO@W8lb	7PKUTJҪ.{/ػfq_oM@Qěx3cf_	MIhtAY=	/g8x,Scx2H"l%fTSHugi`|;$MԋՒ6yxB\Zze4$)^ncousMJ6y%sڱf2jeGސ*R-k-_l%Sypӹj4vS;Y@"cwRJa(-[<ΰ#2b<^9gt6+WTZJBzmvf?OmiU)eAAbG)ƷQ,4y#&%h2c>]Q}s5m+ZK'PxŜrԇK
Sjh[:nBy)_k1z몧!c82ʼn\},	3eՔ,B[6*}EȔCG_Y]hccIwo/Bܨ8(!Qa]K=DvYS`p$d)IfyF'X]h&+0tO}~ ֮endstream
 endobj
-1675 0 obj<>/XObject<<>>>>/Annots 893 0 R>>endobj
-1676 0 obj<>stream
+1682 0 obj<>/XObject<<>>>>/Annots 896 0 R>>endobj
+1683 0 obj<>stream
 xVM6WCZnM&hEPt{$b".IR%"@ ̼7(ƴNh͢~8ZQEyh?Jz]}Vq:LֳhNu+%w(iwEd֟.;Z,p-{_|zӅӟ>lG7;Jfj}KC/u!NJjT'AUf;GouF9mT)_l?f4M2~<['+rFJ5=*lu83R#Bѻ)]`@Zd
0{kCov>\Z$\IQ[; 0z2QQuN22s(xupXi,I
%2ա8[;dՍ;t'm>#Qdi/ikGJRl5<HR%`D	PRQ:.h6TόDNΜt7_z[(KR
 >%q^G>S%BՒSqH2+B\SjPl,-U2d-Ri*,zW_P7\G'
 ~
}mi:ieݠǤZgFn}_fTpNh3/5^RK0%_o&m]I
@@ -3807,15 +3824,15 @@ x
 %^?y|/[&OO$k0^=D
TΪvn#PHW"Ac -QW`¾ďhdJӏNE(:A!gEA0}/t:cQY~Pubx4l6V#K5?^P@жj7zZjiLFf3n,@[HKύYēqW ߃AOT??cz2s?h8T9h+jn`ɬ|&҅~87N]U.Hk?tBu$ 1BԎaZ
'vpp?Ӹ=/*Bxq4
ӮQkksZ/geMSK_ʽg+/zIu59лPixdB7e5kAJY^JRcm*ǯDWEMƳ8gTc>/XObject<<>>>>>>endobj
-1678 0 obj<>stream
+1684 0 obj<>/XObject<<>>>>>>endobj
+1685 0 obj<>stream
 xuAs01GҔ[;N/\JJ2>&mi
 Ì-?g	-MhRgxAyKZ+tRՑ7}xǚ}g+JXvԛ:-	]zzA7ق4]9:2.IkH
 Mtts>/XObject<>>>>>endobj
-1680 0 obj<>stream
+1686 0 obj<>/XObject<>>>>>endobj
+1687 0 obj<>stream
 xWoH~_1D
 	poihtHr=xYbvM;]+T|ӰG+Jg)FhD=<4
p_7F]ǣhL=|?~i~ֹSKh̻xn6bKK~DS˵k7SHG*ߜ>R7-.(vo|9hJ
 O=ot_HEZr&+0"[%:weLq?qN+.LԔB5InEl
)7wkE[qv>a0eUԦsg2[ՍQa4*|F7\hH/43k~iDqctnMFS쇽*F&-B'.s
 0'V:4 -h
@@ -3824,8 +3841,8 @@ x
 Ehm^5ӟ/nA:=@9Mf:$I^`0,MJIvs尜<̘&a~aNc$OŭK&7)+;ɮяe=Tp"	Ј`~/`hr@K8.nʼ	Kh':6{-t+8eڭe韷09,`?CfRf9UaĕuSlF?=8W|[54>/XObject<<>>>>>>endobj
-1682 0 obj<>stream
+1688 0 obj<>/XObject<<>>>>>>endobj
+1689 0 obj<>stream
 xWn8}W)P˖:)(m}-Q6tI*gH%6MD&vΜi9]i2e#ٜ+>ƏT8dvJyN
 >f+Z-KK[UJ'x2k*eQnFpɭ/$47ʔ3y_<_/^h0eSr=ݔ%:uJy`KjY~gTki#D/k>A,FtH,b2](ힴ3@
 up,%%NJĤ2q*hE:{ZI2?kcp]2(2\R|1jب-lc8ވ;6@4Ωneb(2r(MZJ$9j*NTGYRiVd!Thok\^|Tf]iZYp612餄>/XObject<<>>>>>>endobj
-1684 0 obj<>stream
+1690 0 obj<>/XObject<<>>>>>>endobj
+1691 0 obj<>stream
 xWn6}W܇zDd-iKa}	Pmq#*IIɎ66Ab[Μ99Cs1)~gt3%4|7V~}1fZody7|:u>_glћ7͒x"}>,7z
4EGW8Kh*I0T|)IiQKpj2;]Fk؄UШ\TՁJ铴d6d52W[jG1)]ͮ9Gߚ2{>һ"4ǔ~~bWib>s2+iT'U!|>˖Rx9KIJ~c)1 тg$켖i\ǎC4*DC{7JgRf?iTywba/=jOn^Ə9r~e
 *6)s{cLۯ=95\㌽mܿ3p*ʿlNk$)̖Ie^
 iDգAUC%D*΅.&(6[]IƔEאeԄҴUAIxYF!}
@@ -3844,8 +3861,8 @@ x
 q.87}Dv\\cdO
 &+៹\SF7p '"apȮaA5][z|+,AqŋAwAM>[v{Xjݧ;jMf0w[pu3omjlvEl1g/8kKendstream
 endobj
-1685 0 obj<>/XObject<<>>>>>>endobj
-1686 0 obj<>stream
+1692 0 obj<>/XObject<<>>>>>>endobj
+1693 0 obj<>stream
 xX]S}WtlmXnnu]\l*yFf鞑m&U{|8}t4!xLYy0B'gx=iyp1?84ič^ӃͳCj}.8揮TiɅwxhc
}H?{WW?
4+tNWREA.rK?@m}f{\:+
 vL)
@@ -3862,8 +3879,8 @@ S
 ӮbI-4X뱉'/I_P֖kN)W7TՑIw{DHA^bs]G[D,}nEi"KһRe{$GXAh֋Z{¬0cOը]'E&0FAȜwل8-4lkn^lt#*rpGKeP>(ڲn3JxVj&n#mYjTO&$$&ԋ};;=t>1OOΧt2,6盽tw:߯Ogo#
 O?XOendstream
 endobj
-1687 0 obj<>/XObject<<>>>>>>endobj
-1688 0 obj<>stream
+1694 0 obj<>/XObject<<>>>>>>endobj
+1695 0 obj<>stream
 xXko6_q|Iص,Ma@f qX[Q@@KTE"UJKʎAڠ@+qιވч1PV
C:
=_+ػH_hDI#'(	d^UoO,
H
#M#-*Iʑ䗒2-!9C"ҙh*yljzVeI2)CZ*pPi6%
?:Ł6A|@
-m+@8iI9(ARXyi*#Sg5d'r;J._$ʒQ)
H6bi
dN=%E;	ʯz>Zd4W\/DFibܠtOdN*%;?f^&{ӸN&<[:H&drp1M?Og$M_hW?'4$oc8 3Pjwt44!j,Ȱb:\KTiۉBu3V#f
 jń3QuPg-[+҃,}GSU5mv6NuȻcXANT5HVIN4;,9?"wwk7NEpqZlhTޚ+ܭxYRseQ)yq`/IY*q)SAZ9?*FhyeWެ)9juξ\pbl$,nݒNANTpcuUգ\1[NiںOSr^Vi5XUךIWmJRJTVI{]6 ۽H[,+@~?Y$7:/
 N+'|^ӝ5C
te;j3!.>'Ƹ1${/endstream
 endobj
-1689 0 obj<>/XObject<<>>>>>>endobj
-1690 0 obj<>stream
+1696 0 obj<>/XObject<<>>>>>>endobj
+1697 0 obj<>stream
 xWmOHί$E#U'Y6lwͮ
3k;o{wggyA:yC҃NCAkHs|JZtطw:8hv蒂^CLPSSCN6,%]L1WwqzYތ$1oIG&ӛq]\RrCsIOIKi[tW~9WDtnQ$tl4"Q8I0S+	6ӭnuB*'Š(2t.(M2r4_5](re&;ˌH%[z)RF~`Hc0k
w˃>LFj"AKN")&cA>J|_&'E4@.
 [3̂=Gj{.>7ѴNNs_TT129!:—8|8aHO1G	a39i_
>LV$n+cYp
 öD"qu˖g;C#Ld*1J&м aDEXIc}|5]ѴNs$ua"΅=Uh.xEdUf+rz=Z;qmVězvlr&87j]ƍCXT]>%2/LVIbY2@pC`
@@ -3883,13 +3900,13 @@ x
 brfH~7m8"F3ࡴƿA πD4s	~q/5y,g3lmP]Qw#X3;jhg&^2sF*y)OOj7b_iq}H1?ʭ8k^<=q
4Ԕ <TXNbY[nQϧqԝr$딌䗂	BaPT+5tRwo(kP)^YK%W'0Hfr'Ew>
^fWW`'DKv~z6^g=T&tg|t}aendstream
 endobj
-1691 0 obj<>/XObject<<>>>>>>endobj
-1692 0 obj<>stream
+1698 0 obj<>/XObject<<>>>>>>endobj
+1699 0 obj<>stream
 xRN0+1y
H=DP"!n촩	n˒ٝ7'O'8DđW|x8dLnP8̹
 dLྏ,w3\Ej)j,^F5A\z^a'QR)o6T$뺦Z2[r\V]ث^,&.N40n*9/э&XK䣬B[$>Yo	;?X߯UbhT%MF5Q@Y398-W!"Z5jy:}M[輫T݊Եez4^YpfqQHI 6v9 Mendstream
 endobj
-1693 0 obj<>/XObject<>>>>>endobj
-1694 0 obj<>stream
+1700 0 obj<>/XObject<>>>>>endobj
+1701 0 obj<>stream
 xWn8}W[SK.[l[7E([TI^J(-kQ3gΜ8%LfJkJYrK|הM2GD?MWyjL/ƏhzI\2#D7BՍ4'TmtF+5KAU+~2\@$/7Fow+sLW7W^>ߓCLRTPքV;&-(-MTYRi+Mh8TX
 sD.&1T"yS	-bFB5PULsSjR6;m(0/@-gB{sm4Hpσ!Hm@"G@b5rGj@9d
 C2D0tp6
@@ -3901,15 +3918,15 @@ pSY׫+CB
 (UDdܱꙷe7At.Bƽ4A3ƂBqve5{3'v$7v*ຂLnZaխֲb622y.;B{񋃠Uwhn|JmDHtZ_
 PqoK409M7]60?g_Ebendstream
 endobj
-1695 0 obj<>/XObject<<>>>>>>endobj
-1696 0 obj<>stream
+1702 0 obj<>/XObject<<>>>>>>endobj
+1703 0 obj<>stream
 xW]oF|X2mJ,g;n6yPȣt1cxT
 ͤM;ȻIHS&,dv#^|KZ&8k:i9?e4Mq@ϥ]:QΦuelf&b9;]Sr6v/mBV紵N4=WJ&ȳ5%&մ7iJ[t5U^p>Gв8/@
k}~gbUN hM	tDf2rD͐Q%u nI&,Ut%*Mׇßz^.\mpg5|Uy,PqE9FI*ҡBa0wf0F#U# 8 7P7]r&6ƣU:'ف,SU-6:Zn3":b`8tcwA1LU	wY
`}A.k󸠏K#.Zf.|o--TV7uԬjZ^2o7N,@CnPDX
hޤ$RNZЎ)S9B"2ા7gE2hD
a1Q/X^-}5S/N4/s,\
 n5VTf]"Y
]lX\hWm%HֱVVH/p1wCu)7n/EjWW$FǽHE s'H>^uX7^r:xSCt*$Gn\dN'Y<]TCIl c
  bBH_B>k
k8׶n`VP–K]&R`:ϗ5$V(|œ/ij<9-upEYkrdP>ѪB"4n=I-Mrq%ݞDP Q3BJ[Cfo}GB@NnbrpGG4yu_*n{O_Hab^*^+ww0"J'S4CiD@39qLč Ǘˬsh>%z0v:Yg-fl?r}6t├ƚPԛidAiqLהwiT"cӭy"~@Fe)h竓c;E{(b=B|b4ds8׫ӲBmȫyǓk~7f@nQRCt\|{e,WI/eV?BlH4(HFTP|{nH!cb'0ʻ80w>~u._ʘFb~o}-_ vμBc29R&ϝwX`0hM3*V씖_$LE0DU
w/LC/Q<{(`1H I&AGΰT =p˳-W+_?㍟=σsjS׵O7-|m>]3k&p/D~7w63LR&pzy|ӝLgb\,'3>~y?nendstream
 endobj
-1697 0 obj<>/XObject<<>>>>>>endobj
-1698 0 obj<>stream
+1704 0 obj<>/XObject<<>>>>>>endobj
+1705 0 obj<>stream
 xX[OH~W7@M8J+K U{B8eŏq5̹|; R:hL`r>/giώhx[ߵ.uݺ꧃B[+&zVJwz}56AeGx3ԷOp,L~?BNLohh[]l)>$7l.6lY:~;'y˵o4
 ~>EO/ivpjzpK>4i9c.ti|$=y
==hpL.KYJSxNjnv5}i$JmYCJ<ƚBDGɐ/BҐ.I^0įO͋QEBKIs]KYZ\
 K(mՍRQIvq
@@ -3918,8 +3935,8 @@ K
 4	)}ֳVz5:w]ls1Fľ~cgt42[TTZf,&ntK1Բz
	1=q|0ɂtM[}ۛN~	u>Z8oT?Bttm;a*)ܘKxFVĐpg&&O=ϯ'Q`EJ>/XObject<<>>>>>>endobj
-1700 0 obj<>stream
+1706 0 obj<>/XObject<<>>>>>>endobj
+1707 0 obj<>stream
 xMo6s[Gq{G[^DGdVd}!)hMȔDμq"
 uLɌh]^Qf75mr
 0i].3AwvIR=k24k5]CZJ:ڈv54dDUi(RC\,oBFICnvRiBZȼGc!j 4{DTOjCQ2/B
@@ -3927,8 +3944,8 @@ x
 vߝ?V?W<
v[a01S׍ rϹ5Dhpui+{]̈́Nm#?ݏa7W}smr>qobX'+댷m`}m>؏7ߗCH+5R-KEmM:.>]kRiژBե>
 Z:41\0OmC
Q/EtfK$0Ϫ~oPT](ÁHK%6c[go%+	k)Rϭw;11$ 5`H]&4UCVeYSU4v}L?8LSf+816f#9p.ϘV]chB1BiL-+%H̝*x^2KNtZ@6~ȧY(h!4/6aP;Lo`e4>s ]]U*wo"'yOhP2m)ebxLvgE؋)}ܖUcm>jĶbUJyr@^*M-Ums@cc,c\XA?$|~W:m5!\^VsfA8OpAcqO"2\qҞ8u3J~Jp]*_U5||Wy0чlF<3endstream
 endobj
-1701 0 obj<>/XObject<<>>>>>>endobj
-1702 0 obj<>stream
+1708 0 obj<>/XObject<<>>>>>>endobj
+1709 0 obj<>stream
 xW]oF|X%Na"-v'(n-(8GwDm$LKσ&YJ'3I<4S:ŏT\/'tAOqLhҷO>zwy_&IKp$㴿FֱjdpuK~8Vok}p
 wy
Ws:Jo|y0 ;龹jA4.a|.A.7^\J,c}qۣk'Qn&3|>/XObject<<>>>>>>endobj
-1704 0 obj<>stream
+1710 0 obj<>/XObject<<>>>>>>endobj
+1711 0 obj<>stream
 xWnF}W[@%Y"`7Na4buVRbB*}쒔H)
 @aF935ɐƴ:OA0t6u9}?W	xO;\EWnID֒ݓYuܳX$jIi$=cHEhD
 ?#[p28ky* '|7#?܃c[EtIo$i>WWB%;$
B&+N>
{Vwf!?t}CW 0	 rլ46.bNs»Kb&KJO
@@ -3951,16 +3968,16 @@ u,-'%9
 *֢j:
 8hɢ\vG9JZ@z݄:5endstream
 endobj
-1705 0 obj<>/XObject<<>>>>/Annots 896 0 R>>endobj
-1706 0 obj<>stream
+1712 0 obj<>/XObject<<>>>>/Annots 899 0 R>>endobj
+1713 0 obj<>stream
 xWrFW*üJReYvJN4)-,hj
 KZfj8jUUbj|\,)<^Kv
 /wKvCĤbFxzR
%,הJ5HUnE	Ҳ&k )tUdG( jS,Ǚ\}"\ d(ؐBŢRZ`.pkĉݻLV.]qNi/jQJO.tq*e*Z&űXZ(!CFc	k.,݈i$*l}To;Ŧe#{dR-\MP^u"A*INS-eBfYX{;8UW&QaJӂ.UbU8wCrs5!3P(VꤧS`cXUx~ogrbNT)`@> ™1ͬ#o(%	֥
dqtah8;kvҁB@%DFh.Jv̕XՍԍ>-N)yA%2m%X\票;o!@Q,A!a tdn0Ӱ%guFjy!Gڍl.?ݒqDx "q0Ӂ!e>
N񣏆f01-MmmŘaD^hi1tj#DcFooR#SJcU)N-~LS8NsvGڡF#;0;V;ܺxL6_yxj[ue=q Jw1mQ2.\x˔mPi#6kAv@#,?L14wyc"a}9e|1;7@CGbo[F
1>LCYx[\1$m)10'/u2}0\oj1Ղo{6endstream
 endobj
-1707 0 obj<>/XObject<<>>>>>>endobj
-1708 0 obj<>stream
+1714 0 obj<>/XObject<<>>>>>>endobj
+1715 0 obj<>stream
 xW]oF}W+PHQl+Jy1]{ء;3&aWl`{=`BcLvJ7J8r-^fp8Ʉ69,niǴIjY^>~|i4]$3y9$㨔<)LSfTTM[)jzΟw$tFJ/WmjҦOk~z;}6G1M2`)3PRkkRZj4%)$OUMuʁ|[4t&'Pnl*R2B❬P̥"[vيޟj | j>G{Pe"*+b&W]Q^I2(4jiojkBtDZySEަv;Q׽ȗ.(IW$P]Z}0TW;z
 _{XXpw3yp^>2o%&E.jE!qiKLpzg&
S(g
56CUpV!s!j|[,viaщv1+t)H%uzؙt?T]izre*С|yY|)A\OKܯPFg<BJ|@\-sFw栙"Kћ()E"koS[Ը/ծA0Xy^C
 gX_'
+$&fCÃLCT"4y~[vz\#ͩB#%H!{3NVa|7]*JUƚWJAљ\
6`(ٽ{Qg׏K)2G7`YL.&;뷣m`Ws{)x>8DEbDTMY=X}/])|ʤȸ#}΋c|DaeD#G*g/3
@@ -3970,31 +3987,31 @@ KNjCJ
 KLKᘹ5E]@Dv
$^abvMIquZX$~5b\3TMOc'g}~k0-0D8P%[yk Ý;i|#}hyk1$4o:'DN&;I<#"AAOu5FBdyCm@A<
 
NCqpMOPC"#Bs6[髆 wq>ZDӁvv
sf2ư`rcwj@0|;IH'P1fX*~/A6攌Umt?u;"JhM´AXHN/E,W'9>/XObject<<>>>>>>endobj
-1710 0 obj<>stream
+1716 0 obj<>/XObject<<>>>>>>endobj
+1717 0 obj<>stream
 xUMO@W=ە$@ 0A,*'Ww#%ɔ,B!x8h3cuE#$zSqtz>:ZiluJXb<.MKW%WaSs>{ֵj+
 6A
I([5@Ʊ6רkӢ'ZoTtOuʘ->wn>jCI睵F)߼!.0'^C͎l߀Ł7J=ػhH=ǃ+=hUK/-zídf;=~4m
 1f·պTWpg	%ӸOEbn~1yWcZ`]Wlf>/XObject<<>>>>>>endobj
-1712 0 obj<>stream
+1718 0 obj<>/XObject<<>>>>>>endobj
+1719 0 obj<>stream
 xWMo7WMNᬵ,;rH0|Vrv)-]rKrpijFb}p93o{3)~J|IUw6-tjVhqs36|9/?h6A7	:ר>jOt5xctz&Oɗn_8ZtkwPEl:ή%]5&uQNR15EG)j7*h9L٨ʒz磲1Z5Oe9OqS[' 5!Èii-~Tb~VПqj\F5U>ƭNILSaD^qil-!7`jM{7x`$YwvOި'h:wmIUVRu@w/\Ю1UCV5Hl8"J`A>&B68@!@H{!q*4zI^W}rC֭>[rīPnxW#Qϥjm.}9|rݟv=m<;(2?C.l1-Rv,PAч$mLE^٭ 
+53տL_e.tq%r	)3`6f
 YO
>-_,2]Xso3}luj	}=\܎u72aLZ U4Gɓ
K,$Kp
HV?6KդS}mkv;hxPWսkN&$S	lZlEu`	;ͳVFUgFph+4$K`r8ȼG%
IdD!Ge'jO-/_Zt#X&KVXP@G#v%@ʇ1ȪF(VHܰw29a^	&N>Gtc.Qlkz@?[nېh:\2}F١cGLl&ad'pBa@afz9Qx};
X!s8DȬ'IJg:6Z"&d(
|'=R=	Aj:u];$PFeYt7v~4.i30~t
 WӘ̧IΝ''b*Z{"lS^ힷ8>/XObject<<>>>>/Annots 899 0 R>>endobj
-1714 0 obj<>stream
+1720 0 obj<>/XObject<<>>>>/Annots 902 0 R>>endobj
+1721 0 obj<>stream
 xVn8+@S %]443qWYmH
IEϹ\?Nc؀8C;(+eNz&)K|V|%<@$>}ey<]'9Քgd=|1&ʖӗoF32bM37vt-	tUmHN;ՉP*CRKOvԕ")ˇj󿷕O	=z+lRgS4)nZ\#&SZ}@A(O7&Cz[SeFef4Q=!&Ts [ʝmÏ0
U$:H[gP"g8EQ0J[6ИTࠄI2(0dp|ɭR.80>+U(mᣎx ^?ҶUyxKM%$NRmYvzebֳ&"_	~@8l*m0Q>BR*k{[WHrl
v֨pЁcE/ꍥ¢wC~DF zVg_aػw$[,'$pe&)G^r:"AfSD$5Fɠ9	!b>"J؂ +ڶjE*&Yzc-EPym
 _$tVI 1F^l5H3A8xh*^a
"E'.FCʚCm[~O}U+[cCb/BI9-Uqȃ(`sFj!,iKEjk0u{귓G4$+
B*z=ZЪxj0;ްa_@wu
6V:E1HuCHK)<֓m
 ~Top-
 8RJ/9|஍cb('b7~'[
?U2Sx;zp>XTg)~C7fp>/XObject<<>>>>/Annots 902 0 R>>endobj
-1716 0 obj<>stream
+1722 0 obj<>/XObject<<>>>>/Annots 905 0 R>>endobj
+1723 0 obj<>stream
 xW]o6|X%,]Zi"I+҇{IkTEʊΒ}(NFG";_cgL	Md'_^_LdN%RI(tshZ	Ւrb<[&W뻗4:GrĖētp5M	Uj2yg^{˰j:K&=qB‘@4'3j!߇32Y[SV
BZJMYr$)M)xMN~rvHRZUjm=9CԵљ;*	3x.мqaZӇd!d%uf p"x"efI\xRceM/RRĶXN6nf[0`qo
 @lA9wEU$喪8@L^Fޮ4eHGnzNUus	eн(϶hmq0v
Ͷhdsx:Rjxd00S4iApR8ᡔ-9,Jr=4XX.=Zdb7L\O߾yszplUAt~(iN3TxC퀛
0擵W|mRhT9
<g.fEFq|"ja؞ysu zb+06?kxw5KH&	ꁋv̼TҧmzU7t<C}O'D]#MZVUv$spCB_|(GÝiBFh¾67-/[ƫ8^Z>*hKՎ26v=y\҇ne8G7`"$AÀ))]@(SI's5(ڎ9r{D
 V>DPx,#|ĥʚjj>/XObject<<>>>>>>endobj
-1718 0 obj<>stream
-x]O0O4<Z6MM<g'g2VJ`ZhK{y0P,2
-CVIcdG)E&׷Z;KT~W孼0F_R`wh?nl+EAܛoAAlq-:
)6Ӝ	a6E]dُ
uTRpFG62zV,='roWXϟsZNσT&7VyӤU"<*@!}4]oF܋^,Lz>s^-kendstream
+1724 0 obj<>/XObject<<>>>>/Annots 908 0 R>>endobj
+1725 0 obj<>stream
+xTko6_q
[T,ȇK.aVZ*T`ߥdS40xyṏ/=Cy"$EoȆ	czR@￴	
+97˞{E)DM}e2] [qF:8DwpR$U<b"PHx4q)d?w8)L&Jw	j5E*r#NвyK:Fw9/x(3?#Qu-?`+M0?rP)14Rړ'Hzmx,|Xj3݉RUSn
+a292JȓxF#x-U&c5X,\[܀U*sA|iy tX)GHjidsTZd|Њq>/XObject<<>>>>>>endobj
-1720 0 obj<>stream
+1726 0 obj<>/XObject<<>>>>>>endobj
+1727 0 obj<>stream
 xm1
 A>Z8&lf,,vfAaeVB |ϓ#[0jR~GWHiȰ+9{2tk~ۣ>EG%-Avk.$endstream
 endobj
-1721 0 obj<>/XObject<<>>>>/Annots 911 0 R>>endobj
-1722 0 obj<>stream
+1728 0 obj<>/XObject<<>>>>/Annots 917 0 R>>endobj
+1729 0 obj<>stream
 xW]o6}KS V,ٱ<-n@Wlb@_hXKFRw.)يbC$2u9^IL3i|Ii5E3|s$^/-hM%2Jzqz;S8erz||byx'vfu>12Jsdܭ1wrl5egf7:M5m2
IqPW}$)UJI~xq&kdWRQ:jr$+ [GɈ67Ƀ,uSAt}MhCLR⽿HPkU#cOut(^u颾840TgJܝahM3@ۛo3:kSTCUpl_0RIet%Gs	׫7N[c.dA#d^L~[QZMXLVʽU-=1\o xi ҭFpf=[I£(u}zK@֙i~W4ͳpTfpFxMP3+ {-=qH8*kon"mvᯛ`UsR&)?YPuxI9ݖ*-Ovj>bZl4͉rH6 &t"
 P>A4"݋8-یES҇2ygČFQ,#Yi4#mݥsXɠVB?#=<;LC8}F(")KCi[GBĜ,lKE-~ke_fai;%B\qcd.13+tv4R/PGou8Hei2nY9\4apF+l>^Oq<"D>~Cjz9r>K(އщs4rw1Q[7[__EAdWbX*0>/XObject<<>>>>/Annots 916 0 R>>endobj
-1724 0 obj<>stream
+1730 0 obj<>/XObject<<>>>>/Annots 922 0 R>>endobj
+1731 0 obj<>stream
 xWnF|W-&u$/uun,$/$7&RK mX0̙|=&lAIu64_\j)~o;tvu/b(\t6[l;w{t]|:ép_rrrհ9M&θjIԗX2mHP#i7^ ʤrlm{,"&WHJtU:=}禌!E)]7V4׸݊j#bm.a{(κPv,)1R8RedS"R!BNZչ/a{V&SIU,c779oӋ|Ik]Fש%}ʭ,uS9#.:Շ.!mԴ7\?oڮD90BբB7T* .NAtP:n49|~^4YJa\zu[I	oY҂TnZ!~^|~6_b/|M.W,4evfEOucW(3] ?h:СWIY3btfe<45z{ExH_R:.)$<єdN<3ל&⊖!OHVhH݈ŧ
 ɨS#n>ףѓ݌Y,>)W-j]+ھaH"!([P'>H7 bW	t>BWK)׽a3eGN8vDWҖ҃VYvO;?58gMNQBOyҏߨv2g>/XObject<<>>>>>>endobj
-1726 0 obj<>stream
+1732 0 obj<>/XObject<<>>>>>>endobj
+1733 0 obj<>stream
 xV]oF|:Uo WIkiXP @q"WE{GZѿ쑴lq?bÐ%qvgfgϓ;!'}էpf4]!<:~1W˓WchF삖!OO˴w#esˤ)7;>ӟ(U-yWЍ.V&Tެ8K؛Iu|JSlI9@{s|O`(2n镫+|*TLak@bB
shn?̙ܚ[]3BNL#|O_A%XJ"ٔt5_<_4~dpQL2GM8Lmch낚AnOήL=L#W)3 rh<]W)H;Ѓ\hkPX;/{r%{ĠpZMm5U::'˜FBhoVhBSMPzd8mUv9	[$r^>l;iր)CJN
s(7D!U΂$̟9Y#>7Գ8j]i\
7Eir
 C{QhE?:hPqqi%n!ƫ,zPe|L^M,؝<=>>3[ŎrG	ocbe*wejY4cA*+f	n<z'Y%h\~|lLYO:J%.RwT%_w_\IH(mXʹ(wmY(:AqG0DNv~5aq.5zG 8i:cuUt
[YˋE`ܪzy1?^Р9n7	!77Wsz',uZ&]Dr}']d>/XObject<<>>>>>>endobj
-1728 0 obj<>stream
+1734 0 obj<>/XObject<<>>>>>>endobj
+1735 0 obj<>stream
 xV]o6}ϯblCvNm-ƆJlT2KId0(&yy瞫o)Ii1iFE}1NƔMɄf'qʸ0Bt~dJN8%}ܟ8Z̦01Cdy-.4^Y
 }.LW%ߋoɵ;T+a|omSIڊ{E"P/g?XA[C_Nz9Q0}(nA?ma\E+lױ5yHPm#qG3!Q@)xR^;k9J"pkAX8^PGhQ,Z٨&[v5yQps<O{U:Y+#QVJ`,}U$D0NE}7PV]R&ZT>/XObject<>>>>>endobj
-1730 0 obj<>stream
+1736 0 obj<>/XObject<>>>>>endobj
+1737 0 obj<>stream
 xVn6}WLчzXk-4h6X%:f"ZrR/q&F"r8IOJcʫN,4h</{W.}=-%
gIpkhip6p:V⨛dn|:$g?NzCJS-x:YA,|Od3]
 b%Y?n»[uBŚb,Zvm9Z;x&+up4Q'J#Iij].TT1;a}A
U"RVF;<8q@YGߟ;%Ŏʱ:&-%nq`.^.a`Qqe5
³ҹ BԪd
#^,_uGE!
@@ -4053,8 +4073,8 @@ x
 )\q7&u4CKIs].c	
utheI?e'&Iө;-J,q|}"1^
 a;n!\n90"hwxDśndCanťKznerSf[-sA잶04pL*o?:kk%.L&:ն?Pw҇B{p>/XObject<<>>>>>>endobj
-1732 0 obj<>stream
+1738 0 obj<>/XObject<<>>>>>>endobj
+1739 0 obj<>stream
 xWMoFW̭1
 RI/+rEnLK)}$%I$Eə73Y}5)h5EJY}5MNgɚ4e:M7W/n^|Jb5mrB)ɮߔ	|Н)
 -aOoP`WVM6_4/7KͺD˽Mina>˘#Jv#U/_Z(}B
f&2xv6?-p\XaL(s6˩̨kϤ}gɴŮLeɺq|ྞK9kϕH9^](wo%&)|UǍ}*ȢNNV"CIWKax-{{c 		ݎn/tUyaϏ^j;E짥9`WU!^yEGr𕊷xUa'^-
 ֠LhwVgc~%OLX<'$	9'̤Ox>p4})Ͻ7;->/XObject<<>>>>>>endobj
-1734 0 obj<>stream
+1740 0 obj<>/XObject<<>>>>>>endobj
+1741 0 obj<>stream
 xUQoF|WL*]xKEµ:pW{b/x9]ovJPp{g&_G`b:G^bb*-=U8e*||~c1/|cd9$Ǫm+KMXrOT៼~VXkroDLf#Ii*$ˊwRLD*u`gdM*HE8(A7:R;%EC<:m++*3b3UyA;pURRlB%LE,}i:њ54L+b5]T vd
 B YQ2G6l	zV\`*p57H'<R`kFts6.Pod#|+E~̂5M8mWZX5<[kϭt\rk[؆݇5'wIbKI@tG.^xXlWJ907lH@Ⅰ28tgʿ͗_Z5zv&L=V?A'o8B=˺}oe-mWfT;JO:q
kLl#:Ä0G:Ѓ7|7z5G*mRdG=m\۽R͠EF5gg|;V^q/K/1
 ƺc(2Ld:ǘgaTXZr<9TvD12dʪ+r9i,Hùj
 qbfcm\z$YU̞͗b~R)gG+Aendstream
 endobj
-1735 0 obj<>/XObject<<>>>>>>endobj
-1736 0 obj<>stream
+1742 0 obj<>/XObject<<>>>>>>endobj
+1743 0 obj<>stream
 x}Vo6}8vO].C,<D\$R%D"%w޽{ד!
H'd@E2|#YIy0]FI2~}urFZH2i&]D奥eBKcبBÛտ60n;zD7ёф*dJ29U𹱥M$)H%ok*kxrǂ88N=8&LMY	6LhʴA9癫dr"'c.F1@QPޒՎ9.%^pT:$Y?|O,#UV,%| UhkM]a듴}Ϝ
 a3ZvT*
 4Y8
+r?7RBLU!\?<{l<*,<7˳f`*+Ӣ@(zq19s'gjhT8ƩX6H<#h
C`g2%(m#7\QG΀2[cfY"\
yWth^fѕ̤5O-!&Yf*[F'g5OX%gj2Hڦ)AMHG<8+dέϯ"O' B/[J0PKf/')OMn-kv蚮h2EFOh+X8`gQb2ʊ \]-K0'
@@ -4081,21 +4101,21 @@ M'
 {O
 7/ຂoqXywއdlԲ9P&sQhT]t⺝5]&];0K6'T-6j.~y#i7ǖU۝2÷W	v~NG,96:@yTѵ]DJ)1:ұ:U`>^Lu7ށ[l1U%:wޯb\l%D_-.ørC}4O+~٠"d`?YC
0žO'tL/Fup:V'`endstream
 endobj
-1737 0 obj<>/XObject<<>>>>>>endobj
-1738 0 obj<>stream
+1744 0 obj<>/XObject<<>>>>>>endobj
+1745 0 obj<>stream
 xV]o6}H"ɪlC6@AKTĄ"]CJrg<%܏sMq$HiSLeS\iyIN+WstΧ=Iw"	HW5[FƉ/u>/XObject<<>>>>>>endobj
-1740 0 obj<>stream
+1746 0 obj<>/XObject<<>>>>>>endobj
+1747 0 obj<>stream
 xuTn0}Wחquv6(6kLw$%Ems!_R|2ZTԌ4IE*O7튲%jUFuKT7*Nhg\yncDІM}aҺwZP<N{q+REw19;%_F7)y[b
 ڳj)FC(v^,	"JHЃ0>HG=2ԋӖYdxxt?6oQnc3)c#YF܄=8 $GRQ':gBI;QXRڑ@X	=R;#Z&r	t'1qi{K#g<~8jIZ	C=@ky
 N?NHd GxI'z-yCn\	=['p/ы`Ö
ڭc12뻯@yϙ	N0M0GvO-c0
<55=fϓ[^RWѸ,h	Uq
 <>|`8$|(a뼚gǮqE1Oq=ZwMT£y3eqdztWur7Soa?m|"A$$yv8F|iyd%aUPYYӝ?qt	T9|LW;e9gM=<nendstream
 endobj
-1741 0 obj<>/XObject<<>>>>/Annots 927 0 R>>endobj
-1742 0 obj<>stream
+1748 0 obj<>/XObject<<>>>>/Annots 933 0 R>>endobj
+1749 0 obj<>stream
 xWn7}WbVź䥰]_)q
 (+Jb%7K{\I
 òKrϜ9C=~:4Ro@Y~tѠ7g4gLJߎ:dLA2I~4
#,Ω7īGɰ~i;wus~mȺ=,xnr^?mw繜o=#1\DeI"O	3'WL)JNg_O:O;JdRz/@XrBe–ʚ$n5ΰުO0t2޺6/,Kft醌]JHU@mɄrN^|9)y3ju1l%7<%ӣ2sv4>oG.cQfGKV~Cʹq]xU..h]*̲YG"}Z8ҁ $
@@ -4105,16 +4125,16 @@ _
 $R} yp]o ~ᒩ7ц}U40YX3i5zK*2R!)\C9>/XObject<<>>>>/Annots 936 0 R>>endobj
-1744 0 obj<>stream
+1750 0 obj<>/XObject<<>>>>/Annots 942 0 R>>endobj
+1751 0 obj<>stream
 xWQo6~8e)PI`HZgMѤY5a%V+(~#qQtkZɻx?1M)-{1/ϒD$[A^2>x,&; 1؃8,	N&_hًG'p2,ix<;6^$p1EhD|\ÁHC̆RR({YW4CmzcVic)BS
(#yv45d?bt98(	oݴik5kD_+EyZk
}8kJ'IM+8۲6ew`rTOQvvDj袵8K"A3x]7`*kSMhEOT
 Kź)4+X(eM[Ȣ 3qR+Mtص*>,o<y>M`½ifytzKf8ZHaa2zke_tH*iO28i+wo'aVvk,0hh@-Tұ*;/SfOM`sm2&rVPB`ѮV[Asq{35Zgu;eU"268|StV2;ƞkWxCA(ih[eiV!/"q= jIviU=dB3Ljz}bǚsSִu6>i㫛𕡑eC-@|͊GoY󯀽y%t?*>M$YWorvysʑTP\OB5$!!	<B6BORp]Պc
 TiYT6ϨMFjZVE˚RB>7
 ~> ꝳ83х&07c@r׶SZ+VH€ۻۻOtEvݙ[WDeo3eX{1bzRچl2l: !)إ^+y
b|kY<5X OT˪6GYN՘\
 }A;ڗ̞C_-hz*>tJYË.w\ݬpgpd+KO޳'vϱ9N6֑c+<nfi]#;tdݑ3ΫqAJwABߣ?&t.^nYGM}{eU:G(3NF@YvquwT{j04PnvE ӦE}n__~ة}r;|<{D>ʼVAZu&װa1Žeh^]c6=w^䘰Ξ[&Kvam>נXݬ;"a!w(&DP7-Ln4$|3xS)2^YHC|'1~s8;sۆozkҶļ&RF80?_$Iޯ7Xendstream
 endobj
-1745 0 obj<>/XObject<<>>>>/Annots 939 0 R>>endobj
-1746 0 obj<>stream
+1752 0 obj<>/XObject<<>>>>/Annots 945 0 R>>endobj
+1753 0 obj<>stream
 xWn8}WR/K
 Cb;Ej,(H+Rq{DȢ#\Ϝ:R4QDaz:4w0b1G
:×.7yJy*x⍚WIz@.1MGNeo%I'͒ᓡ(֐)(6yҡG;⤁FF$2RYTfV$T6$YMv+U^+ί/3r,s[+Qq4w4Ǻ"Y%1;2J쥵a^3BfޙiUi Qaۆ;k<"-H2
0EhS	>/XObject<>>>/Annots 946 0 R>>endobj
-1748 0 obj<>stream
+1754 0 obj<>/XObject<>>>/Annots 952 0 R>>endobj
+1755 0 obj<>stream
 xWS8~_ӗ3O: RR[!*Zv)߷[ !o|E7iL	%y/BN>{W)i87`Bq(t̚UFWAhrrin蓳
ko
fޠ|S`Oaw؁488UNn9r1,\8fx҉w~DQD-Gn2*u	ioHE%>߮>/_G/cHPk,l̏V^G?
 T2LyLz쥏1$v2kT[zI7u{R)KLReHi[,j'ec{@Nle
 z4uUSZmir	}6$WR2BʤPU|)uFNT*$Ȫ;*"[HEǨS(DZ窖Ճ)IKuۘrg`ـeOޟ˜h\}8ҩy(H)-D OQ-DA	&Kkm=zPծut%-b=(
@@ -4134,22 +4154,22 @@ x
 {F`..3uBr8P2s[\	EOFa1x$b6#S:5ȼkq>/-܏jF>M-qlZsOYaCmLaNx%esRkkppg@ډ7LvheT ׊eͶ$wm2{1avd_ِ&#|
;Wr(ڈLAͦY9gdL]	tĚ.WOMendstream
 endobj
-1749 0 obj<>/XObject<<>>>>>>endobj
-1750 0 obj<>stream
+1756 0 obj<>/XObject<<>>>>>>endobj
+1757 0 obj<>stream
 xMo0n!%96[vJ,J2
 ׏N@fP`S"#G.d8Qbd<]9^Q
i
r)YIDȐ9+d2dE,p.knKeMgyӟV=xmpeU^a(BH򺺭nU3#JcZa!
 RA˶sGiL]͑NnK-Tr#%bң;^r*90yLNCyZчlj0vmȂg0ϥjjt9WjV[}!`^jIK(9s=z8l״dA`/=ZEASƹ0Ȟ䩩{7ܓhD*StK7gTfRAOaxqWFߣWendstream
 endobj
-1751 0 obj<>/XObject<<>>>>>>endobj
-1752 0 obj<>stream
+1758 0 obj<>/XObject<<>>>>>>endobj
+1759 0 obj<>stream
 xV]O8}W\Haf݁٥J#I<$qv=-%B@{Li)]lNEw0&t>ds:~JLyNizsvxs贽n=->QT(R݇T)T55pUdn[y7vhK;YDj
ktv
>h(¶BSg}Ū4CiUKq=T+Fb*,	kToqruIߣ8f'K{9wyX^
HVo;5-x:ƕBڀFRiTr(62wIlmԩM")m[i*0awҗ#?
)Ow:z0_ހvQ4Tk1K7Nc8
 /ɛR:	lz'#eFX\}L#rR{	twpL
X[7xR/u_z`a7.Acjq]`"\i{Hq`#5A+1#'n:z
 o*H'9LvL')uyK~;/fCV0d"x?J1No+\BJܗ%笐1u;i}<9iVh'P9$`v2EnZzt?+~xԁ2@6_2a8mhޏeT{"Dp1dvp$NqzDlEi%6XT1dwyVؾ|
sH8`J&>c)TGpVƢuy8)I2MݧD1T-%IMSp.0,q>/XObject<<>>>>>>endobj
-1754 0 obj<>stream
+1760 0 obj<>/XObject<<>>>>>>endobj
+1761 0 obj<>stream
 xVMo6W|iC	v@Q J,n$R+Rq_7udoz($@ 3o޼yW3gF9-bJi4x6ܬܿXo&K'V۫46xmF@46ʒyM)ZMd)Ѿ\!Rf,L':#-I"M$PU*E3B7ZTmZЮD@a!2t,֟ŋrLIg ^j٨Jj'28PԘqN:rRxکJ!xyPICE8{UqPW	㬶NVNw{Etݠxv6JAk/$SZ7-eiRFrZKnhTy4b,?k)TRShr@![ Dgֲ(#ҏ4-$UFjPP[tgi1_[!
 Ej
@@ -4157,15 +4177,15 @@ x
 1tVG~OF]`ɢƁ7źF6W'(GnWB`4v`+֩`G'lТ5]˿ôMho{eP
 yeΛ~ػ7aytG5Rɤq/xÁzz˫mXz^󱟷W_۰endstream
 endobj
-1755 0 obj<>/XObject<<>>>>>>endobj
-1756 0 obj<>stream
+1762 0 obj<>/XObject<<>>>>>>endobj
+1763 0 obj<>stream
 xV]oH}ϯ⥩Ը!%t68}==wl
Ͷʇu9ד	iԣt|44?#i]Ň
 Gk8)J~]~/LuETٷX(A8.JNosI4VamLm#+S_phc4.d^>G$(1"N~x2{s6h,{Cֱs*KxhV-U	ĩL{"Eu&oe7ςT*̫Y6+	ZFT;C"O=3;HAF\omn(=Tǰ_١LmDj5meZxpԐ
5?
,(sD`/+Z&,d"2YύJRA q0NԂ9 5%x߲`R`æؓ;%#rsO?ӛ?botS&^KuGx@i;[z1Zw5-/?)j:BzyMfFLwF_]LIJmZZ͘HW9z1cIҏ6h#eemNT)ضPD
 M>xpT6t_xZ(3JaQ@V6=8qH+肑F>@AW_j@>/zvF0BI35^^[,{dvBrx(~O+s
Ckk|5TTOM]k4 K$5Q&AL/b~{!f>7cS@obiiAR[jˡze=nLV\UUAb-F<6NyvpVON)yj@fSLզh\-@ƌrF乍[,
QϿ~o״j4$ɟ'ɓendstream
 endobj
-1757 0 obj<>/XObject<<>>>>>>endobj
-1758 0 obj<>stream
+1764 0 obj<>/XObject<<>>>>>>endobj
+1765 0 obj<>stream
 xmUMSHWBjc1lr[]92F@QfF8}=X։)(i=u}WLҜn!"AYG6k*7}FqL
 5KB/.mJzid۾~׊:GҾ1MI2sS5uT$lJYEi!hQ
 'ʓ%.'?X~sQXkJe}L		G$55zA	u/28[8L`p=F)89,&4zp,Ftj}s^k4%4eZ>\"8@:(ј_
@@ -4173,8 +4193,8 @@ xmUMS
 	0M'хxSܛ
 
8c€š4V|)Oˊǐi7%s\MJz:|7״	D6/kQ^INЗq[o|Zendstream
 endobj
-1759 0 obj<>/XObject<>>>>>endobj
-1760 0 obj<>stream
+1766 0 obj<>/XObject<>>>>>endobj
+1767 0 obj<>stream
 xWMo8Wz,P˖N6)#M({%*UoH)p	EDg޼y3qRZd4S^M	NO%͖῕TtdќHa-Nq[UzB}">w7w)eZxlXҺ D5}%Z/-M	+INAy%[}o.tP1ӄVrLMgiHlRiIiP#ALI^:hg:EC5yCwBBxgCXN;i'em%"E+%0cF$0,a0a@2PJU">[Pt\_۾[2}=hcb
 پ0<꦳"NXQRP_;/t6mr,Bռ9z.hW}q5jH,M&QҰ!GeOQvBi`͗L}ѷxendstream
 endobj
-1761 0 obj<>/XObject<<>>>>>>endobj
-1762 0 obj<>stream
+1768 0 obj<>/XObject<<>>>>>>endobj
+1769 0 obj<>stream
 xW]oF|%
 `Ӓ?yW
 B~9Gb-wvdIhyܛkgDC!RV\Lv>hDh04_TSfJ9|ÆQa03]p/em@쾿m>|wkSvMAK!폎C$:m.ГE&'^khrypsOa&㩶grNg\}Pe#irlH*p$Z뜂%lqzᨳund#j87:`@I@m^=ijɘNea:%țʔma}*(R[R{`f{"ǫ*U8m&T fE;{VݣKozU7tsKS\lEtRAmk9;*G!ӥOy*)DFHQ/salB_wTA̮) *AH90T	_
R{4nf%sy"eAl7ip[>ykf$4
@@ -4194,8 +4214,8 @@ x
 AHnt%rJ^z["֠{4(0($ZIp|t-=
Yļc~AN..:{FDs0͔Ãf)g'ԢUwFR"_v[(mM.N(yUwBXy2!RY~kr#KqM`;ju^ڛI+Iݣ3“6ٽ
yCf~{8Ո{0c}FD®&l巴Uw=1.J*rK[wڪsJW,zڅ.Ue='BM]\3Al?jH3u'i^t@o$zsiW2Ba**u%f+ǁ243vCޜym,gyÎe_BX$jD^?ӏ~^͂`]幆gx@w0^z&8EuSqNgdS"Xs
JQœˊk.YM-!mll;iė@llvfS8OюAD緷]dCe2L`bH6,}m)*-hY(8T}=s1&6*Aբ
:0SV*BAqП#j0e{Iڗ[
*T@*W3?sȮYKK2B11Kd0bɦx Rx|^ҋEt|X^Y}⢵eUׁmZUiss<&CE0	KQsWCXX{i'U4,+4ԠmK]d:
 `i5]'y^\ZQX.XDZެ7n<jVLrcك'P0:X\I`""mx!9v(&X.op#p2B5alA'hZ2 ӓC4֏#~v=co,~endstream
 endobj
-1763 0 obj<>/XObject<>>>>>endobj
-1764 0 obj<>stream
+1770 0 obj<>/XObject<>>>>>endobj
+1771 0 obj<>stream
 xWaO8ί!JOfvi?-I*!oݸ$qj;l;Ɇcό߼y3y?1-4SRxM*1[DϏ#u|{M_ΗǴ\邖)MdBLi'RLjKJDm%Pym$5LYr:m&KHB{IiL82ZhBx0HS#%+SƒmU&s)9dryp4kHԘ[o{9m#uG݊b%(OL9D­=&*UXm?e4]W8`%htNW^{yCwwg."k68N׆%4HJ$mytiZ6RWdI+w.NL#	C4
 KD>=H'(Gk7`B*dqΕO]?N+08Qۋ}.A. ѠzudhI	t	*9vUˆB`A@ns\DӗwĵLII0"GlbTň	@{ɨM~ASH=h<96 Ǒ'Fq|
 Z8p?F]suiI|Ŷd ?Cۧ3`_5'ndбnp^?^Ӡv
@@ -4207,8 +4227,8 @@ H[
 :UJ]B{^"?1>/XObject<<>>>>>>endobj
-1766 0 obj<>stream
+1772 0 obj<>/XObject<<>>>>>>endobj
+1773 0 obj<>stream
 xXQs6~K,[v:ӇMn2snXss (wi~isŒKi52%ٌVv]Eg2kë~s-SiRN[^yc`5;H|\#Dz֤._tFֺɨ_b~hI-ԽaOu56jqPQn
 ~?ۻ6
[er^z|[Och!ag^'tn>QҶVQ={zwmR2c4SULz]W{~5f
 _خh"_ZںFV#JGR	g<#ݦ	vQ]5u,Sds+|4u]ʴ	{NKUU;J%m0Hi;"(DxBH{ڰ(dW#1X k ϥ#שyv[Vd)
@@ -4221,14 +4241,14 @@ _
 FwOi,w{S|8/ZytInYkGD
 7̲V^+ʝE_B@c\߿+$gOh)@֡ۮ5Sc(6ݎ=Ѫ>̹ې\.VWE&J!;kHd!;S;{Ik1wA]P`1D
@|PbHerE@woX/-g?|6j;:a=B5|>0yIWKf>N~;oOendstream
 endobj
-1767 0 obj<>/XObject<<>>>>/Annots 948 0 R>>endobj
-1768 0 obj<>stream
+1774 0 obj<>/XObject<<>>>>/Annots 954 0 R>>endobj
+1775 0 obj<>stream
 xTn0}WDcCD&U[섊uJJ_&D^{D/|i^prNx[(=8(Mgaҭ6AMYNޚc.0@n'ipEHsM#c|@.@4	Qlys^	{6S[8VlY7R0ɯҗ`Q4
'TxxpfΚP]de\cbr󧫆©Vm7qL߸0.Jz`
 B{;QcJ
 GސhL%s(gk^&/3oPZ%GZkw-CT##V{Vaˊ491}zrVT:ΫWA(&Ԧ,$@G^:ϧn	'O
z3Z\*>Ó.ӽRW2lm;ss E_U( (	g/[3GQdUN>_R|o4Cl*Ќ,Onu_?'&У`YTg4pKJ3ull}1IRp
)J+"J[Y߮@/W3.X%B]Fh"LfJR"|K_?endstream
 endobj
-1769 0 obj<>/XObject<<>>>>/Annots 953 0 R>>endobj
-1770 0 obj<>stream
+1776 0 obj<>/XObject<<>>>>/Annots 959 0 R>>endobj
+1777 0 obj<>stream
 xWMs6WMDIlɹ9vLLg|IBLZ}PN&ՏтULgVy4:zco$~|e/ђ9^l:|*~_̣3W1N)YQ>b"zylO^ ]p:+FA;\@Ql=y	~k/y2sjϯ69#oDpJ<ž=Ϝ%z56#_]\ndB
5	'x3JܩW9ZXFttKo-gS|#Lp-pm`ڴ%*HU-	g]"a|5孕v;^#}(|zP>5}, ^$ԡ
WK[d Eu_w8|_oa-|a3m/gQendstream
 endobj
-1771 0 obj<>/XObject<<>>>>/Annots 970 0 R>>endobj
-1772 0 obj<>stream
+1778 0 obj<>/XObject<<>>>>/Annots 976 0 R>>endobj
+1779 0 obj<>stream
 xX]o8}ϯ0Hf˶%̤.BKʼnDjH*_﹔8j;vbQԑL~{<4i48DhJ1[I[^LJ7gxMh1ѰyiyOcA4x:7^MYd&Tp6a 5oau48CBA#m߇v4ƫ]<]<@pb>^Wp8
 WoVg׼L-Gq:*
*xcS{wF{krz/Va}TMi(HY4笭ҋutJ7ZycieLH蔮wR*y /+
rXcN

wIER:5{GoW}H΋<3(L#=lxEx#׬Q9*ҵrUŭʑ.*OI>)a@Wߗ?{a^(^u^21ڤ"*謕	G{][;d
 qsh玶@	\j);FUQ^Պ>'[i26EP,mp}+DB ^}IS^![ex-eڕ҅H
gGcnd?4٣C|]G uMkHm!S&/]mgOmCZJ)_&{rqrAwD{4=⎊/Bᵊudv},YЦ04d޾Ax(z^t' X9oSϻYr?SZc5"3	_1'dH|Iath7,*2M ck]Rި'8lu
 54y_x0
!.ky@O~v`V	07|#a~Wƥk9O|X!%Ò}-_d/.<_h:F~}sMꋦiy
f>lpQa>/XObject<<>>>>/Annots 975 0 R>>endobj
-1774 0 obj<>stream
+1780 0 obj<>/XObject<<>>>>/Annots 981 0 R>>endobj
+1781 0 obj<>stream
 xWMs6WlO;/Kr/ǩ2ukM;E T-H*괙d}[`JjF%e`Lh1%3ZW'/obY2C`'S/;f6M)8zE<:M6qTI5t(Et?lA^TmH +#avY
 \c5&.ܼLh<#M>6:THZ@D˽08jG|=@Y}&5E;'7Bi9"$δu{2NFYH3E;1sJS--W]Pq~<;X֐s!
6fׁ:""1BW~}<"H -M$@sNY)'lR,
ۼrgCsڸcdOEC#} .NNbDڂhٍTnx@9TAJdzYTj^)8)r^[sȷ&i2Jz/vv؁	h.b5dzW5q*‘.^Tj.0znDk+%v)سH?HMJsq3b[3gp'uO-!Z|n
 !tuj[^ j/Y(RԵ4NdBG0tƟA	ڃAfQ	H	@Le̩T^pʊc7EHd,
@@ -4258,8 +4278,8 @@ j
 #Tʓ{(!4R$^XWT	韲KRhMJ>l<3+ \\sLKW/BŢwֳm-b9I
:@bwU1Ft&6}2f!E{,
/LW 26 ff
7H!N:B`Xɜz1DU*#'
&g3@.T6;xeS05>Bp|$z
 Hy^SLN//	Y6ʂu[Io)^DgdzC夭"NG{mj*󲁿V`caTְ8Y='JIШCTkVБ‘XDBo3!]]!X=Z_B&Jźbwĭ洪Mdyh],B(4Op]Q:tM`ό&z{`D%CQ*[kLi;)7p:va\S;6`?Ƚߓ$^;(Kׁ|}}/]yIm{5X`t(~~dqendstream
 endobj
-1775 0 obj<>/XObject<<>>>>/Annots 983 0 R>>endobj
-1776 0 obj<>stream
+1782 0 obj<>/XObject<<>>>>/Annots 989 0 R>>endobj
+1783 0 obj<>stream
 x}Wێ6}Wڦi}hEbUZgHUA.̙3g'sߜnP^OfO?LlK:[PM&[w>M֫lE"|x'/ٚVUzyt'/	-oWZ\8r2/ݰlѲ--f+fK"'կj;Z3ȭuA7z׸r~VZJP
 hEmd7]d1UL\+mHc充)^7GgOړW^?3Dd2mK$B1B_tlr*p^5:Wi
 [I);a*Qa90lG:(_>I0ŔGEC#SNL(#tFRѾ&[	1gV]^ɷ䐫FgSJSͰkF$RԳ	DNH.FU88۵dKj:V D1TS@7B}h@2Z as~s(,8 ufD!@zQ=۲mY:
#szqQ"0ad|W蝥ƂGwRCYL$TxTG.s[Yl5>>lDJbt\GaGnv3|y6DZ6BsRco
@@ -4267,8 +4287,8 @@ x}Wێ
 D/ϡx!hzJ{jY4,*~Qŋ>pNMF&JUR%ڃ2'bCO)1ikHYkؘO[vxAԂ"nC\-e! HɭC 'HøƿKc䰂.u-:4kD݉t-I5tj&MW0
 BԎ3hPZ8Ԉ$A"A/A2%~Pp(/BxaaD%ʍL8#d4#y(8.cو+2TsJCZ.1=Co%d#M!*ho΋<@Y!ÑWrml>/XObject<<>>>>>>endobj
-1778 0 obj<>stream
+1784 0 obj<>/XObject<<>>>>>>endobj
+1785 0 obj<>stream
 xWnF|WlRiɲe@4iH;hY=rhEHMgF4_PM)/ْΖ)zM8ϲ^N/~utrsF*Y,/hUL*&*єOzUNVkMIhpJ'm|8K_M[ڙh/^S꼫_'U
 km$c5)'s}0r}UmHY/AlTyU)_*\U1qϟD4:
 `^5f^+n:4\8_`jk*S(pSJX#c^
 օj/gm՞d5p \z=2S}D
q)zpERl_E`V F{tbJrrsI3~>endobj
-1780 0 obj<>endobj
-1781 0 obj<>endobj
-1782 0 obj<>endobj
-1783 0 obj<>endobj
-1784 0 obj<>endobj
-1785 0 obj<>endobj
-1786 0 obj<>endobj
-1787 0 obj<>endobj
-1788 0 obj<>endobj
-1789 0 obj<>endobj
-1790 0 obj<>endobj
-1791 0 obj<>endobj
-1792 0 obj<>endobj
-1793 0 obj<>endobj
-1794 0 obj<>endobj
-1795 0 obj<>endobj
-1796 0 obj<>endobj
-1797 0 obj<>endobj
-1798 0 obj<>endobj
-1799 0 obj<>endobj
-1800 0 obj<>endobj
-1801 0 obj<>endobj
-1802 0 obj<>endobj
-1803 0 obj<>endobj
-1804 0 obj<>endobj
-1805 0 obj<>endobj
-1806 0 obj<>endobj
-1807 0 obj<>endobj
-1808 0 obj<>endobj
-1809 0 obj<>endobj
-1810 0 obj<>endobj
-1811 0 obj<>endobj
-1812 0 obj<>endobj
-1813 0 obj<>endobj
-1814 0 obj<>endobj
-1815 0 obj<>endobj
-1816 0 obj<>endobj
-1817 0 obj<>endobj
-1818 0 obj<>endobj
-1819 0 obj<>endobj
-1820 0 obj<>endobj
-1821 0 obj<>endobj
-1822 0 obj<>endobj
-1823 0 obj<>endobj
-1824 0 obj<>endobj
-1825 0 obj<>endobj
-1826 0 obj<>endobj
-1827 0 obj<>endobj
-1828 0 obj<>endobj
-1829 0 obj<>endobj
-1830 0 obj<>endobj
-1831 0 obj<>endobj
-1832 0 obj<>endobj
-1833 0 obj<>endobj
-1834 0 obj<>endobj
-1835 0 obj<>endobj
-1836 0 obj<>endobj
-1837 0 obj<>endobj
-1838 0 obj<>endobj
-1839 0 obj<>endobj
-1840 0 obj<>endobj
-1841 0 obj<>endobj
-1842 0 obj<>endobj
-1843 0 obj<>endobj
-1844 0 obj<>endobj
-1845 0 obj<>endobj
-1846 0 obj<>endobj
-1847 0 obj<>endobj
-1848 0 obj<>endobj
-1849 0 obj<>endobj
-1850 0 obj<>endobj
-1851 0 obj<>endobj
-1852 0 obj<>endobj
-1853 0 obj<>endobj
-1854 0 obj<>endobj
-1855 0 obj<>endobj
-1856 0 obj<>endobj
-1857 0 obj<>endobj
-1858 0 obj<>endobj
-1859 0 obj<>endobj
-1860 0 obj<>endobj
-1861 0 obj<>endobj
-1862 0 obj<>endobj
-1863 0 obj<>endobj
-1864 0 obj<>endobj
-1865 0 obj<>endobj
-1866 0 obj<>endobj
-1867 0 obj<>endobj
-1868 0 obj<>endobj
-1869 0 obj<>endobj
-1870 0 obj<>endobj
-1871 0 obj<>endobj
-1872 0 obj<>endobj
-1873 0 obj<>endobj
-1874 0 obj<>endobj
-1875 0 obj<>endobj
-1876 0 obj<>endobj
-1877 0 obj<>endobj
-1878 0 obj<>endobj
-1879 0 obj<>endobj
-1880 0 obj<>endobj
-1881 0 obj<>endobj
-1882 0 obj<>endobj
-1883 0 obj<>endobj
-1884 0 obj<>endobj
-1885 0 obj<>endobj
-1886 0 obj<>endobj
-1887 0 obj<>endobj
-1888 0 obj<>endobj
-1889 0 obj<>endobj
-1890 0 obj<>endobj
-1891 0 obj<>endobj
-1892 0 obj<>endobj
-1893 0 obj<>endobj
-1894 0 obj<>endobj
-1895 0 obj<>endobj
-1896 0 obj<>endobj
-1897 0 obj<>endobj
-1898 0 obj<>endobj
-1899 0 obj<>endobj
-1900 0 obj<>endobj
-1901 0 obj<>endobj
-1902 0 obj<>endobj
-1903 0 obj<>endobj
-1904 0 obj<>endobj
-1905 0 obj<>endobj
-1906 0 obj<>endobj
-1907 0 obj<>endobj
-1908 0 obj<>endobj
-1909 0 obj<>endobj
-1910 0 obj<>endobj
-1911 0 obj<>endobj
-1912 0 obj<>endobj
-1913 0 obj<>endobj
-1914 0 obj<>endobj
-1915 0 obj<>endobj
-1916 0 obj<>endobj
-1917 0 obj<>endobj
-1918 0 obj<>endobj
-1919 0 obj<>endobj
-1920 0 obj<>endobj
-1921 0 obj<>endobj
-1922 0 obj<>endobj
-1923 0 obj<>endobj
-1924 0 obj<>endobj
-1925 0 obj<>endobj
-1926 0 obj<>endobj
-1927 0 obj<>endobj
-1928 0 obj<>endobj
-1929 0 obj<>endobj
-1930 0 obj<>endobj
-1931 0 obj<>endobj
-1932 0 obj<>endobj
-1933 0 obj<>endobj
-1934 0 obj<>endobj
-1935 0 obj<>endobj
-1936 0 obj<>endobj
-1937 0 obj<>endobj
-1938 0 obj<>endobj
-1939 0 obj<>endobj
-1940 0 obj<>endobj
-1941 0 obj<>endobj
-1942 0 obj<>endobj
-1943 0 obj<>endobj
-1944 0 obj<>endobj
-1945 0 obj<>endobj
-1946 0 obj<>endobj
-1947 0 obj<>endobj
-1948 0 obj<>endobj
-1949 0 obj<>endobj
-1950 0 obj<>endobj
-1951 0 obj<>endobj
-1952 0 obj<>endobj
-1953 0 obj<>endobj
-1954 0 obj<>endobj
-1955 0 obj<>endobj
-1956 0 obj<>endobj
-1957 0 obj<>endobj
-1958 0 obj<>endobj
-1959 0 obj<>endobj
-1960 0 obj<>endobj
-1961 0 obj<>endobj
-1962 0 obj<>endobj
-1963 0 obj<>endobj
-1964 0 obj<>endobj
-1965 0 obj<>endobj
-1966 0 obj<>endobj
-1967 0 obj<>endobj
-1968 0 obj<>endobj
-1969 0 obj<>endobj
-1970 0 obj<>endobj
-1971 0 obj<>endobj
-1972 0 obj<>endobj
-1973 0 obj<>endobj
-1974 0 obj<>endobj
-1975 0 obj<>endobj
-1976 0 obj<>endobj
-1977 0 obj<>endobj
-1978 0 obj<>endobj
-1979 0 obj<>endobj
-1980 0 obj<>endobj
-1981 0 obj<>endobj
-1982 0 obj<>endobj
-1983 0 obj<>endobj
-1984 0 obj<>endobj
-1985 0 obj<>endobj
-1986 0 obj<>endobj
-1987 0 obj<>endobj
-1988 0 obj<>endobj
-1989 0 obj<>endobj
-1990 0 obj<>endobj
-1991 0 obj<>endobj
-1992 0 obj<>endobj
-1993 0 obj<>endobj
-1994 0 obj<>endobj
-1995 0 obj<>endobj
-1996 0 obj<>endobj
-1997 0 obj<>endobj
-1998 0 obj<>endobj
-1999 0 obj<>endobj
-2000 0 obj<>endobj
-2001 0 obj<>endobj
-2002 0 obj<>endobj
-2003 0 obj<>endobj
-2004 0 obj<>endobj
-2005 0 obj<>endobj
-2006 0 obj<>endobj
-2007 0 obj<>endobj
-2008 0 obj<>endobj
-2009 0 obj<>endobj
-2010 0 obj<>endobj
-2011 0 obj<>endobj
-2012 0 obj<>endobj
-2013 0 obj<>endobj
-2014 0 obj<>endobj
-2015 0 obj<>endobj
-2016 0 obj<>endobj
-2017 0 obj<>endobj
-2018 0 obj<>endobj
-2019 0 obj<>endobj
-2020 0 obj<>endobj
-2021 0 obj<>endobj
-2022 0 obj<>endobj
-2023 0 obj<>endobj
-2024 0 obj<>endobj
-2025 0 obj<>endobj
-2026 0 obj<>endobj
-2027 0 obj<>endobj
-2028 0 obj<>endobj
-2029 0 obj<>endobj
-2030 0 obj<>endobj
-2031 0 obj<>endobj
-2032 0 obj<>endobj
-2033 0 obj<>endobj
-2034 0 obj<>endobj
-2035 0 obj<>endobj
-2036 0 obj<>endobj
-2037 0 obj<>endobj
-2038 0 obj<>endobj
-2039 0 obj<>endobj
-2040 0 obj<>endobj
-2041 0 obj<>endobj
-2042 0 obj<>endobj
-2043 0 obj<>endobj
-2044 0 obj<>endobj
-2045 0 obj<>endobj
-2046 0 obj<>endobj
-2047 0 obj<>endobj
-2048 0 obj<>endobj
-2049 0 obj<>endobj
-2050 0 obj<>endobj
-2051 0 obj<>endobj
-2052 0 obj<>endobj
-2053 0 obj<>endobj
-2054 0 obj<>endobj
-2055 0 obj<>endobj
-2056 0 obj<>endobj
-2057 0 obj<>endobj
-2058 0 obj<>endobj
-2059 0 obj<>endobj
-2060 0 obj<>endobj
-2061 0 obj<>endobj
-2062 0 obj<>endobj
-2063 0 obj<>endobj
-2064 0 obj<>endobj
-2065 0 obj<>endobj
-2066 0 obj<>endobj
-2067 0 obj<>endobj
-2068 0 obj<>endobj
-2069 0 obj<>endobj
-2070 0 obj<>endobj
-2071 0 obj<>endobj
-2072 0 obj<>endobj
-2073 0 obj<>endobj
-2074 0 obj<>endobj
-2075 0 obj<>endobj
-2076 0 obj<>endobj
-2077 0 obj<>endobj
-2078 0 obj<>endobj
-2079 0 obj<>endobj
-2080 0 obj<>endobj
-2081 0 obj<>endobj
-2082 0 obj<>endobj
-2083 0 obj<>endobj
-2084 0 obj<>endobj
-2085 0 obj<>endobj
-2086 0 obj<>endobj
-2087 0 obj<>endobj
-2088 0 obj<>endobj
-2089 0 obj<>endobj
-2090 0 obj<>endobj
-2091 0 obj<>endobj
-2092 0 obj<>endobj
-2093 0 obj<>endobj
-2094 0 obj<>endobj
-2095 0 obj<>endobj
-2096 0 obj<>endobj
-2097 0 obj<>endobj
-2098 0 obj<>endobj
-2099 0 obj<>endobj
-2100 0 obj<>endobj
-2101 0 obj<>endobj
-2102 0 obj<>endobj
-2103 0 obj<>endobj
-2104 0 obj<>endobj
-2105 0 obj<>endobj
-2106 0 obj<>endobj
-2107 0 obj<>endobj
-2108 0 obj<>endobj
-2109 0 obj<>endobj
-2110 0 obj<>endobj
-2111 0 obj<>endobj
-2112 0 obj<>endobj
-2113 0 obj<>endobj
-2114 0 obj<>endobj
-2115 0 obj<>endobj
-2116 0 obj<>endobj
-2117 0 obj<>endobj
-2118 0 obj<>endobj
-2119 0 obj<>endobj
-2120 0 obj<>endobj
-2121 0 obj<>endobj
-2122 0 obj<>endobj
-2123 0 obj<>endobj
-2124 0 obj<>endobj
-2125 0 obj<>endobj
-2126 0 obj<>endobj
-2127 0 obj<>1<>10<>15<>16<>17<>21<>24<>29<>40<>41<>42<>44<>48<>56<>59<>61<>63<>64<>65<>70<>71<>82<>104<>117<>121<>126<>138<>141<>144<>147<>149<>156<>165<>167<>169<>170<>175<>177<>180<>184<>185<>189<>194<>197<>]>>>>endobj
+1786 0 obj<>endobj
+1787 0 obj<>endobj
+1788 0 obj<>endobj
+1789 0 obj<>endobj
+1790 0 obj<>endobj
+1791 0 obj<>endobj
+1792 0 obj<>endobj
+1793 0 obj<>endobj
+1794 0 obj<>endobj
+1795 0 obj<>endobj
+1796 0 obj<>endobj
+1797 0 obj<>endobj
+1798 0 obj<>endobj
+1799 0 obj<>endobj
+1800 0 obj<>endobj
+1801 0 obj<>endobj
+1802 0 obj<>endobj
+1803 0 obj<>endobj
+1804 0 obj<>endobj
+1805 0 obj<>endobj
+1806 0 obj<>endobj
+1807 0 obj<>endobj
+1808 0 obj<>endobj
+1809 0 obj<>endobj
+1810 0 obj<>endobj
+1811 0 obj<>endobj
+1812 0 obj<>endobj
+1813 0 obj<>endobj
+1814 0 obj<>endobj
+1815 0 obj<>endobj
+1816 0 obj<>endobj
+1817 0 obj<>endobj
+1818 0 obj<>endobj
+1819 0 obj<>endobj
+1820 0 obj<>endobj
+1821 0 obj<>endobj
+1822 0 obj<>endobj
+1823 0 obj<>endobj
+1824 0 obj<>endobj
+1825 0 obj<>endobj
+1826 0 obj<>endobj
+1827 0 obj<>endobj
+1828 0 obj<>endobj
+1829 0 obj<>endobj
+1830 0 obj<>endobj
+1831 0 obj<>endobj
+1832 0 obj<>endobj
+1833 0 obj<>endobj
+1834 0 obj<>endobj
+1835 0 obj<>endobj
+1836 0 obj<>endobj
+1837 0 obj<>endobj
+1838 0 obj<>endobj
+1839 0 obj<>endobj
+1840 0 obj<>endobj
+1841 0 obj<>endobj
+1842 0 obj<>endobj
+1843 0 obj<>endobj
+1844 0 obj<>endobj
+1845 0 obj<>endobj
+1846 0 obj<>endobj
+1847 0 obj<>endobj
+1848 0 obj<>endobj
+1849 0 obj<>endobj
+1850 0 obj<>endobj
+1851 0 obj<>endobj
+1852 0 obj<>endobj
+1853 0 obj<>endobj
+1854 0 obj<>endobj
+1855 0 obj<>endobj
+1856 0 obj<>endobj
+1857 0 obj<>endobj
+1858 0 obj<>endobj
+1859 0 obj<>endobj
+1860 0 obj<>endobj
+1861 0 obj<>endobj
+1862 0 obj<>endobj
+1863 0 obj<>endobj
+1864 0 obj<>endobj
+1865 0 obj<>endobj
+1866 0 obj<>endobj
+1867 0 obj<>endobj
+1868 0 obj<>endobj
+1869 0 obj<>endobj
+1870 0 obj<>endobj
+1871 0 obj<>endobj
+1872 0 obj<>endobj
+1873 0 obj<>endobj
+1874 0 obj<>endobj
+1875 0 obj<>endobj
+1876 0 obj<>endobj
+1877 0 obj<>endobj
+1878 0 obj<>endobj
+1879 0 obj<>endobj
+1880 0 obj<>endobj
+1881 0 obj<>endobj
+1882 0 obj<>endobj
+1883 0 obj<>endobj
+1884 0 obj<>endobj
+1885 0 obj<>endobj
+1886 0 obj<>endobj
+1887 0 obj<>endobj
+1888 0 obj<>endobj
+1889 0 obj<>endobj
+1890 0 obj<>endobj
+1891 0 obj<>endobj
+1892 0 obj<>endobj
+1893 0 obj<>endobj
+1894 0 obj<>endobj
+1895 0 obj<>endobj
+1896 0 obj<>endobj
+1897 0 obj<>endobj
+1898 0 obj<>endobj
+1899 0 obj<>endobj
+1900 0 obj<>endobj
+1901 0 obj<>endobj
+1902 0 obj<>endobj
+1903 0 obj<>endobj
+1904 0 obj<>endobj
+1905 0 obj<>endobj
+1906 0 obj<>endobj
+1907 0 obj<>endobj
+1908 0 obj<>endobj
+1909 0 obj<>endobj
+1910 0 obj<>endobj
+1911 0 obj<>endobj
+1912 0 obj<>endobj
+1913 0 obj<>endobj
+1914 0 obj<>endobj
+1915 0 obj<>endobj
+1916 0 obj<>endobj
+1917 0 obj<>endobj
+1918 0 obj<>endobj
+1919 0 obj<>endobj
+1920 0 obj<>endobj
+1921 0 obj<>endobj
+1922 0 obj<>endobj
+1923 0 obj<>endobj
+1924 0 obj<>endobj
+1925 0 obj<>endobj
+1926 0 obj<>endobj
+1927 0 obj<>endobj
+1928 0 obj<>endobj
+1929 0 obj<>endobj
+1930 0 obj<>endobj
+1931 0 obj<>endobj
+1932 0 obj<>endobj
+1933 0 obj<>endobj
+1934 0 obj<>endobj
+1935 0 obj<>endobj
+1936 0 obj<>endobj
+1937 0 obj<>endobj
+1938 0 obj<>endobj
+1939 0 obj<>endobj
+1940 0 obj<>endobj
+1941 0 obj<>endobj
+1942 0 obj<>endobj
+1943 0 obj<>endobj
+1944 0 obj<>endobj
+1945 0 obj<>endobj
+1946 0 obj<>endobj
+1947 0 obj<>endobj
+1948 0 obj<>endobj
+1949 0 obj<>endobj
+1950 0 obj<>endobj
+1951 0 obj<>endobj
+1952 0 obj<>endobj
+1953 0 obj<>endobj
+1954 0 obj<>endobj
+1955 0 obj<>endobj
+1956 0 obj<>endobj
+1957 0 obj<>endobj
+1958 0 obj<>endobj
+1959 0 obj<>endobj
+1960 0 obj<>endobj
+1961 0 obj<>endobj
+1962 0 obj<>endobj
+1963 0 obj<>endobj
+1964 0 obj<>endobj
+1965 0 obj<>endobj
+1966 0 obj<>endobj
+1967 0 obj<>endobj
+1968 0 obj<>endobj
+1969 0 obj<>endobj
+1970 0 obj<>endobj
+1971 0 obj<>endobj
+1972 0 obj<>endobj
+1973 0 obj<>endobj
+1974 0 obj<>endobj
+1975 0 obj<>endobj
+1976 0 obj<>endobj
+1977 0 obj<>endobj
+1978 0 obj<>endobj
+1979 0 obj<>endobj
+1980 0 obj<>endobj
+1981 0 obj<>endobj
+1982 0 obj<>endobj
+1983 0 obj<>endobj
+1984 0 obj<>endobj
+1985 0 obj<>endobj
+1986 0 obj<>endobj
+1987 0 obj<>endobj
+1988 0 obj<>endobj
+1989 0 obj<>endobj
+1990 0 obj<>endobj
+1991 0 obj<>endobj
+1992 0 obj<>endobj
+1993 0 obj<>endobj
+1994 0 obj<>endobj
+1995 0 obj<>endobj
+1996 0 obj<>endobj
+1997 0 obj<>endobj
+1998 0 obj<>endobj
+1999 0 obj<>endobj
+2000 0 obj<>endobj
+2001 0 obj<>endobj
+2002 0 obj<>endobj
+2003 0 obj<>endobj
+2004 0 obj<>endobj
+2005 0 obj<>endobj
+2006 0 obj<>endobj
+2007 0 obj<>endobj
+2008 0 obj<>endobj
+2009 0 obj<>endobj
+2010 0 obj<>endobj
+2011 0 obj<>endobj
+2012 0 obj<>endobj
+2013 0 obj<>endobj
+2014 0 obj<>endobj
+2015 0 obj<>endobj
+2016 0 obj<>endobj
+2017 0 obj<>endobj
+2018 0 obj<>endobj
+2019 0 obj<>endobj
+2020 0 obj<>endobj
+2021 0 obj<>endobj
+2022 0 obj<>endobj
+2023 0 obj<>endobj
+2024 0 obj<>endobj
+2025 0 obj<>endobj
+2026 0 obj<>endobj
+2027 0 obj<>endobj
+2028 0 obj<>endobj
+2029 0 obj<>endobj
+2030 0 obj<>endobj
+2031 0 obj<>endobj
+2032 0 obj<>endobj
+2033 0 obj<>endobj
+2034 0 obj<>endobj
+2035 0 obj<>endobj
+2036 0 obj<>endobj
+2037 0 obj<>endobj
+2038 0 obj<>endobj
+2039 0 obj<>endobj
+2040 0 obj<>endobj
+2041 0 obj<>endobj
+2042 0 obj<>endobj
+2043 0 obj<>endobj
+2044 0 obj<>endobj
+2045 0 obj<>endobj
+2046 0 obj<>endobj
+2047 0 obj<>endobj
+2048 0 obj<>endobj
+2049 0 obj<>endobj
+2050 0 obj<>endobj
+2051 0 obj<>endobj
+2052 0 obj<>endobj
+2053 0 obj<>endobj
+2054 0 obj<>endobj
+2055 0 obj<>endobj
+2056 0 obj<>endobj
+2057 0 obj<>endobj
+2058 0 obj<>endobj
+2059 0 obj<>endobj
+2060 0 obj<>endobj
+2061 0 obj<>endobj
+2062 0 obj<>endobj
+2063 0 obj<>endobj
+2064 0 obj<>endobj
+2065 0 obj<>endobj
+2066 0 obj<>endobj
+2067 0 obj<>endobj
+2068 0 obj<>endobj
+2069 0 obj<>endobj
+2070 0 obj<>endobj
+2071 0 obj<>endobj
+2072 0 obj<>endobj
+2073 0 obj<>endobj
+2074 0 obj<>endobj
+2075 0 obj<>endobj
+2076 0 obj<>endobj
+2077 0 obj<>endobj
+2078 0 obj<>endobj
+2079 0 obj<>endobj
+2080 0 obj<>endobj
+2081 0 obj<>endobj
+2082 0 obj<>endobj
+2083 0 obj<>endobj
+2084 0 obj<>endobj
+2085 0 obj<>endobj
+2086 0 obj<>endobj
+2087 0 obj<>endobj
+2088 0 obj<>endobj
+2089 0 obj<>endobj
+2090 0 obj<>endobj
+2091 0 obj<>endobj
+2092 0 obj<>endobj
+2093 0 obj<>endobj
+2094 0 obj<>endobj
+2095 0 obj<>endobj
+2096 0 obj<>endobj
+2097 0 obj<>endobj
+2098 0 obj<>endobj
+2099 0 obj<>endobj
+2100 0 obj<>endobj
+2101 0 obj<>endobj
+2102 0 obj<>endobj
+2103 0 obj<>endobj
+2104 0 obj<>endobj
+2105 0 obj<>endobj
+2106 0 obj<>endobj
+2107 0 obj<>endobj
+2108 0 obj<>endobj
+2109 0 obj<>endobj
+2110 0 obj<>endobj
+2111 0 obj<>endobj
+2112 0 obj<>endobj
+2113 0 obj<>endobj
+2114 0 obj<>endobj
+2115 0 obj<>endobj
+2116 0 obj<>endobj
+2117 0 obj<>endobj
+2118 0 obj<>endobj
+2119 0 obj<>endobj
+2120 0 obj<>endobj
+2121 0 obj<>endobj
+2122 0 obj<>endobj
+2123 0 obj<>endobj
+2124 0 obj<>endobj
+2125 0 obj<>endobj
+2126 0 obj<>endobj
+2127 0 obj<>endobj
+2128 0 obj<>endobj
+2129 0 obj<>endobj
+2130 0 obj<>endobj
+2131 0 obj<>endobj
+2132 0 obj<>endobj
+2133 0 obj<>endobj
+2134 0 obj<>endobj
+2135 0 obj<>1<>10<>15<>16<>17<>21<>24<>29<>40<>41<>42<>44<>48<>56<>59<>61<>63<>64<>65<>70<>71<>82<>104<>117<>121<>126<>138<>141<>144<>147<>149<>156<>165<>167<>169<>170<>175<>177<>180<>184<>185<>189<>194<>197<>]>>>>endobj
 xref
-0 2128 
+0 2136 
 0000000000 65535 f 
 0000000015 00000 n 
 0000000247 00000 n 
@@ -4931,8 +4952,8 @@ xref
 0000034239 00000 n 
 0000034343 00000 n 
 0000034447 00000 n 
-0000034550 00000 n 
-0000034653 00000 n 
+0000034551 00000 n 
+0000034654 00000 n 
 0000034757 00000 n 
 0000034861 00000 n 
 0000034965 00000 n 
@@ -4943,12 +4964,12 @@ xref
 0000035485 00000 n 
 0000035589 00000 n 
 0000035693 00000 n 
-0000035796 00000 n 
+0000035797 00000 n 
 0000035900 00000 n 
 0000036004 00000 n 
 0000036108 00000 n 
 0000036212 00000 n 
-0000036315 00000 n 
+0000036316 00000 n 
 0000036419 00000 n 
 0000036523 00000 n 
 0000036626 00000 n 
@@ -4958,7 +4979,7 @@ xref
 0000037286 00000 n 
 0000037390 00000 n 
 0000037494 00000 n 
-0000037597 00000 n 
+0000037598 00000 n 
 0000037701 00000 n 
 0000037805 00000 n 
 0000037909 00000 n 
@@ -4974,7 +4995,7 @@ xref
 0000038949 00000 n 
 0000039053 00000 n 
 0000039157 00000 n 
-0000039260 00000 n 
+0000039261 00000 n 
 0000039364 00000 n 
 0000039468 00000 n 
 0000039572 00000 n 
@@ -4983,7 +5004,7 @@ xref
 0000039884 00000 n 
 0000039988 00000 n 
 0000040092 00000 n 
-0000040195 00000 n 
+0000040196 00000 n 
 0000040299 00000 n 
 0000040403 00000 n 
 0000040507 00000 n 
@@ -4994,7 +5015,7 @@ xref
 0000041027 00000 n 
 0000041131 00000 n 
 0000041235 00000 n 
-0000041338 00000 n 
+0000041339 00000 n 
 0000041442 00000 n 
 0000041545 00000 n 
 0000041647 00000 n 
@@ -5002,1766 +5023,1774 @@ xref
 0000042118 00000 n 
 0000042221 00000 n 
 0000042325 00000 n 
-0000042429 00000 n 
-0000042533 00000 n 
-0000042637 00000 n 
-0000042741 00000 n 
+0000042428 00000 n 
+0000042532 00000 n 
+0000042636 00000 n 
+0000042740 00000 n 
 0000042844 00000 n 
 0000042948 00000 n 
-0000043052 00000 n 
-0000043156 00000 n 
-0000043260 00000 n 
-0000043364 00000 n 
-0000043468 00000 n 
-0000043589 00000 n 
-0000043643 00000 n 
-0000043729 00000 n 
-0000043782 00000 n 
-0000043868 00000 n 
-0000043922 00000 n 
-0000044009 00000 n 
-0000044064 00000 n 
-0000044150 00000 n 
-0000044217 00000 n 
-0000044303 00000 n 
-0000044406 00000 n 
-0000044510 00000 n 
-0000044614 00000 n 
-0000044718 00000 n 
-0000044822 00000 n 
-0000044926 00000 n 
-0000045030 00000 n 
-0000045134 00000 n 
-0000045238 00000 n 
-0000045342 00000 n 
-0000045446 00000 n 
-0000045550 00000 n 
-0000045654 00000 n 
-0000045758 00000 n 
-0000045862 00000 n 
-0000045966 00000 n 
-0000046070 00000 n 
-0000046174 00000 n 
-0000046277 00000 n 
-0000046379 00000 n 
-0000046481 00000 n 
-0000046583 00000 n 
-0000046816 00000 n 
-0000046920 00000 n 
-0000047024 00000 n 
-0000047128 00000 n 
-0000047232 00000 n 
-0000047336 00000 n 
-0000047440 00000 n 
-0000047544 00000 n 
-0000047648 00000 n 
-0000047752 00000 n 
-0000047856 00000 n 
-0000047960 00000 n 
-0000048064 00000 n 
-0000048167 00000 n 
-0000048271 00000 n 
-0000048375 00000 n 
-0000048479 00000 n 
-0000048583 00000 n 
-0000048687 00000 n 
-0000048791 00000 n 
-0000048895 00000 n 
-0000048999 00000 n 
-0000049103 00000 n 
-0000049207 00000 n 
-0000049311 00000 n 
-0000049415 00000 n 
-0000049519 00000 n 
-0000049623 00000 n 
-0000049727 00000 n 
-0000049831 00000 n 
-0000049935 00000 n 
-0000050039 00000 n 
-0000050143 00000 n 
-0000050247 00000 n 
-0000050351 00000 n 
-0000050455 00000 n 
-0000050559 00000 n 
-0000050663 00000 n 
-0000050767 00000 n 
-0000050871 00000 n 
-0000050975 00000 n 
-0000051079 00000 n 
-0000051183 00000 n 
-0000051287 00000 n 
-0000051391 00000 n 
-0000051493 00000 n 
-0000051597 00000 n 
-0000051701 00000 n 
-0000051805 00000 n 
-0000051909 00000 n 
-0000052013 00000 n 
-0000052116 00000 n 
-0000052218 00000 n 
-0000052320 00000 n 
-0000052761 00000 n 
-0000052865 00000 n 
-0000052969 00000 n 
-0000053073 00000 n 
-0000053177 00000 n 
-0000053281 00000 n 
-0000053385 00000 n 
-0000053489 00000 n 
-0000053593 00000 n 
-0000053697 00000 n 
-0000053801 00000 n 
-0000053905 00000 n 
-0000054009 00000 n 
-0000054113 00000 n 
-0000054217 00000 n 
-0000054321 00000 n 
-0000054425 00000 n 
-0000054529 00000 n 
-0000054633 00000 n 
-0000054737 00000 n 
-0000054841 00000 n 
-0000054945 00000 n 
-0000055049 00000 n 
-0000055153 00000 n 
-0000055257 00000 n 
-0000055361 00000 n 
-0000055465 00000 n 
-0000055569 00000 n 
-0000055673 00000 n 
-0000055777 00000 n 
-0000055881 00000 n 
-0000055985 00000 n 
-0000056089 00000 n 
-0000056193 00000 n 
-0000056297 00000 n 
-0000056401 00000 n 
-0000056505 00000 n 
-0000056609 00000 n 
-0000056713 00000 n 
-0000056817 00000 n 
-0000056921 00000 n 
-0000057025 00000 n 
-0000057129 00000 n 
-0000057233 00000 n 
-0000057337 00000 n 
-0000057441 00000 n 
-0000057545 00000 n 
-0000057649 00000 n 
-0000057753 00000 n 
-0000057857 00000 n 
-0000057960 00000 n 
-0000058062 00000 n 
-0000058164 00000 n 
-0000058597 00000 n 
-0000058701 00000 n 
-0000058805 00000 n 
-0000058909 00000 n 
-0000059013 00000 n 
-0000059117 00000 n 
-0000059221 00000 n 
-0000059325 00000 n 
-0000059429 00000 n 
-0000059533 00000 n 
-0000059637 00000 n 
-0000059741 00000 n 
-0000059845 00000 n 
-0000059949 00000 n 
-0000060053 00000 n 
-0000060157 00000 n 
-0000060261 00000 n 
-0000060365 00000 n 
-0000060469 00000 n 
-0000060573 00000 n 
-0000060677 00000 n 
-0000060781 00000 n 
-0000060885 00000 n 
-0000060989 00000 n 
-0000061093 00000 n 
-0000061197 00000 n 
-0000061301 00000 n 
-0000061405 00000 n 
-0000061509 00000 n 
-0000061613 00000 n 
-0000061717 00000 n 
-0000061820 00000 n 
-0000061924 00000 n 
-0000062028 00000 n 
-0000062132 00000 n 
-0000062236 00000 n 
-0000062340 00000 n 
-0000062444 00000 n 
-0000062548 00000 n 
-0000062652 00000 n 
-0000062756 00000 n 
-0000062860 00000 n 
-0000062964 00000 n 
-0000063068 00000 n 
-0000063172 00000 n 
-0000063276 00000 n 
-0000063380 00000 n 
-0000063484 00000 n 
-0000063588 00000 n 
-0000063691 00000 n 
-0000063793 00000 n 
-0000063895 00000 n 
-0000064320 00000 n 
-0000064424 00000 n 
-0000064528 00000 n 
-0000064632 00000 n 
-0000064736 00000 n 
-0000064840 00000 n 
-0000064944 00000 n 
-0000065048 00000 n 
-0000065152 00000 n 
-0000065256 00000 n 
-0000065360 00000 n 
-0000065464 00000 n 
-0000065568 00000 n 
-0000065672 00000 n 
-0000065776 00000 n 
-0000065880 00000 n 
-0000065984 00000 n 
-0000066088 00000 n 
-0000066192 00000 n 
-0000066296 00000 n 
-0000066400 00000 n 
-0000066504 00000 n 
-0000066608 00000 n 
-0000066712 00000 n 
-0000066816 00000 n 
-0000066920 00000 n 
-0000067024 00000 n 
-0000067128 00000 n 
-0000067232 00000 n 
-0000067336 00000 n 
-0000067440 00000 n 
-0000067544 00000 n 
-0000067648 00000 n 
-0000067752 00000 n 
-0000067856 00000 n 
-0000068145 00000 n 
-0000068194 00000 n 
-0000068281 00000 n 
-0000068385 00000 n 
-0000068489 00000 n 
-0000068592 00000 n 
-0000068641 00000 n 
-0000068745 00000 n 
-0000068848 00000 n 
-0000068881 00000 n 
-0000068937 00000 n 
-0000069024 00000 n 
-0000069093 00000 n 
-0000069180 00000 n 
-0000069231 00000 n 
-0000069318 00000 n 
-0000069403 00000 n 
-0000069490 00000 n 
-0000069546 00000 n 
-0000069633 00000 n 
-0000069683 00000 n 
-0000069770 00000 n 
-0000069822 00000 n 
-0000069909 00000 n 
-0000069971 00000 n 
-0000070056 00000 n 
-0000070137 00000 n 
-0000070191 00000 n 
-0000070277 00000 n 
-0000070331 00000 n 
-0000070418 00000 n 
-0000070451 00000 n 
-0000070492 00000 n 
-0000070579 00000 n 
-0000070623 00000 n 
-0000070710 00000 n 
-0000070755 00000 n 
-0000070842 00000 n 
-0000070886 00000 n 
-0000070973 00000 n 
-0000071017 00000 n 
-0000071104 00000 n 
-0000071146 00000 n 
-0000071233 00000 n 
-0000071281 00000 n 
-0000071368 00000 n 
-0000071441 00000 n 
-0000071545 00000 n 
-0000071648 00000 n 
-0000071681 00000 n 
-0000071734 00000 n 
-0000071820 00000 n 
-0000071845 00000 n 
-0000071892 00000 n 
-0000071978 00000 n 
-0000072025 00000 n 
-0000072111 00000 n 
-0000072144 00000 n 
-0000072189 00000 n 
-0000072276 00000 n 
-0000072321 00000 n 
-0000072407 00000 n 
-0000072440 00000 n 
-0000072485 00000 n 
-0000072571 00000 n 
-0000072614 00000 n 
-0000072700 00000 n 
-0000072741 00000 n 
-0000072827 00000 n 
-0000072876 00000 n 
-0000072962 00000 n 
-0000073008 00000 n 
-0000073094 00000 n 
-0000073139 00000 n 
-0000073225 00000 n 
-0000073277 00000 n 
-0000073363 00000 n 
-0000073413 00000 n 
-0000073499 00000 n 
-0000073545 00000 n 
-0000073631 00000 n 
-0000073674 00000 n 
-0000073760 00000 n 
-0000073804 00000 n 
-0000073890 00000 n 
-0000073933 00000 n 
-0000074019 00000 n 
-0000074064 00000 n 
-0000074150 00000 n 
-0000074188 00000 n 
-0000074274 00000 n 
-0000074316 00000 n 
-0000074402 00000 n 
-0000074445 00000 n 
-0000074531 00000 n 
-0000074569 00000 n 
-0000074655 00000 n 
-0000074697 00000 n 
-0000074783 00000 n 
-0000074827 00000 n 
-0000074913 00000 n 
-0000074960 00000 n 
-0000075046 00000 n 
-0000075148 00000 n 
-0000075250 00000 n 
-0000075443 00000 n 
-0000075547 00000 n 
-0000075572 00000 n 
-0000075621 00000 n 
-0000075707 00000 n 
-0000075732 00000 n 
-0000075779 00000 n 
-0000075866 00000 n 
-0000075970 00000 n 
-0000076003 00000 n 
-0000076056 00000 n 
-0000076143 00000 n 
-0000076168 00000 n 
-0000076272 00000 n 
-0000076375 00000 n 
-0000076479 00000 n 
-0000076520 00000 n 
-0000076562 00000 n 
-0000076649 00000 n 
-0000076692 00000 n 
-0000076779 00000 n 
-0000076829 00000 n 
-0000076916 00000 n 
-0000076964 00000 n 
-0000077051 00000 n 
-0000077100 00000 n 
-0000077143 00000 n 
-0000077230 00000 n 
-0000077284 00000 n 
-0000077371 00000 n 
-0000077416 00000 n 
-0000077503 00000 n 
-0000077560 00000 n 
-0000077646 00000 n 
-0000077742 00000 n 
-0000077827 00000 n 
-0000077884 00000 n 
-0000077930 00000 n 
-0000078017 00000 n 
-0000078063 00000 n 
-0000078148 00000 n 
-0000078192 00000 n 
-0000078279 00000 n 
-0000078330 00000 n 
-0000078417 00000 n 
-0000078466 00000 n 
-0000078553 00000 n 
-0000078610 00000 n 
-0000078673 00000 n 
-0000078760 00000 n 
-0000078818 00000 n 
-0000078905 00000 n 
-0000078999 00000 n 
-0000079085 00000 n 
-0000079126 00000 n 
-0000079169 00000 n 
-0000079255 00000 n 
-0000079303 00000 n 
-0000079390 00000 n 
-0000079431 00000 n 
-0000079518 00000 n 
-0000079562 00000 n 
-0000079649 00000 n 
-0000079693 00000 n 
-0000079779 00000 n 
-0000079836 00000 n 
-0000079882 00000 n 
-0000079969 00000 n 
-0000080018 00000 n 
-0000080103 00000 n 
-0000080136 00000 n 
-0000080190 00000 n 
-0000080277 00000 n 
-0000080328 00000 n 
-0000080415 00000 n 
-0000080469 00000 n 
-0000080556 00000 n 
-0000080606 00000 n 
-0000080693 00000 n 
-0000080742 00000 n 
-0000080792 00000 n 
-0000080877 00000 n 
-0000080902 00000 n 
-0000080966 00000 n 
-0000081053 00000 n 
-0000081078 00000 n 
-0000081130 00000 n 
-0000081215 00000 n 
-0000081240 00000 n 
-0000081304 00000 n 
-0000081391 00000 n 
-0000081457 00000 n 
-0000081544 00000 n 
-0000081602 00000 n 
-0000081689 00000 n 
-0000081783 00000 n 
-0000081870 00000 n 
-0000081934 00000 n 
-0000082021 00000 n 
-0000082082 00000 n 
-0000082169 00000 n 
-0000082234 00000 n 
-0000082311 00000 n 
-0000082397 00000 n 
-0000082422 00000 n 
-0000082512 00000 n 
-0000082598 00000 n 
-0000082687 00000 n 
-0000082773 00000 n 
-0000082844 00000 n 
-0000082930 00000 n 
-0000083062 00000 n 
-0000083148 00000 n 
-0000083197 00000 n 
-0000083271 00000 n 
-0000083357 00000 n 
-0000083454 00000 n 
-0000083540 00000 n 
-0000083605 00000 n 
+0000043051 00000 n 
+0000043155 00000 n 
+0000043259 00000 n 
+0000043363 00000 n 
+0000043467 00000 n 
+0000043571 00000 n 
+0000043675 00000 n 
+0000043812 00000 n 
+0000043866 00000 n 
+0000043952 00000 n 
+0000044005 00000 n 
+0000044091 00000 n 
+0000044145 00000 n 
+0000044232 00000 n 
+0000044287 00000 n 
+0000044373 00000 n 
+0000044440 00000 n 
+0000044526 00000 n 
+0000044629 00000 n 
+0000044733 00000 n 
+0000044837 00000 n 
+0000044941 00000 n 
+0000045045 00000 n 
+0000045149 00000 n 
+0000045253 00000 n 
+0000045357 00000 n 
+0000045461 00000 n 
+0000045565 00000 n 
+0000045669 00000 n 
+0000045773 00000 n 
+0000045877 00000 n 
+0000045981 00000 n 
+0000046085 00000 n 
+0000046189 00000 n 
+0000046293 00000 n 
+0000046397 00000 n 
+0000046500 00000 n 
+0000046602 00000 n 
+0000046704 00000 n 
+0000046806 00000 n 
+0000047039 00000 n 
+0000047143 00000 n 
+0000047247 00000 n 
+0000047351 00000 n 
+0000047455 00000 n 
+0000047559 00000 n 
+0000047663 00000 n 
+0000047767 00000 n 
+0000047871 00000 n 
+0000047975 00000 n 
+0000048079 00000 n 
+0000048183 00000 n 
+0000048287 00000 n 
+0000048390 00000 n 
+0000048494 00000 n 
+0000048598 00000 n 
+0000048702 00000 n 
+0000048806 00000 n 
+0000048910 00000 n 
+0000049014 00000 n 
+0000049118 00000 n 
+0000049222 00000 n 
+0000049326 00000 n 
+0000049430 00000 n 
+0000049534 00000 n 
+0000049638 00000 n 
+0000049742 00000 n 
+0000049846 00000 n 
+0000049950 00000 n 
+0000050054 00000 n 
+0000050158 00000 n 
+0000050262 00000 n 
+0000050366 00000 n 
+0000050470 00000 n 
+0000050574 00000 n 
+0000050678 00000 n 
+0000050782 00000 n 
+0000050886 00000 n 
+0000050990 00000 n 
+0000051094 00000 n 
+0000051198 00000 n 
+0000051302 00000 n 
+0000051406 00000 n 
+0000051510 00000 n 
+0000051614 00000 n 
+0000051716 00000 n 
+0000051820 00000 n 
+0000051924 00000 n 
+0000052028 00000 n 
+0000052132 00000 n 
+0000052236 00000 n 
+0000052339 00000 n 
+0000052441 00000 n 
+0000052543 00000 n 
+0000052984 00000 n 
+0000053088 00000 n 
+0000053192 00000 n 
+0000053296 00000 n 
+0000053400 00000 n 
+0000053504 00000 n 
+0000053608 00000 n 
+0000053712 00000 n 
+0000053816 00000 n 
+0000053920 00000 n 
+0000054024 00000 n 
+0000054128 00000 n 
+0000054232 00000 n 
+0000054336 00000 n 
+0000054440 00000 n 
+0000054544 00000 n 
+0000054648 00000 n 
+0000054752 00000 n 
+0000054856 00000 n 
+0000054960 00000 n 
+0000055064 00000 n 
+0000055168 00000 n 
+0000055272 00000 n 
+0000055376 00000 n 
+0000055480 00000 n 
+0000055584 00000 n 
+0000055688 00000 n 
+0000055792 00000 n 
+0000055896 00000 n 
+0000056000 00000 n 
+0000056104 00000 n 
+0000056208 00000 n 
+0000056312 00000 n 
+0000056416 00000 n 
+0000056520 00000 n 
+0000056624 00000 n 
+0000056728 00000 n 
+0000056832 00000 n 
+0000056936 00000 n 
+0000057040 00000 n 
+0000057144 00000 n 
+0000057248 00000 n 
+0000057352 00000 n 
+0000057456 00000 n 
+0000057560 00000 n 
+0000057664 00000 n 
+0000057768 00000 n 
+0000057872 00000 n 
+0000057976 00000 n 
+0000058080 00000 n 
+0000058183 00000 n 
+0000058285 00000 n 
+0000058387 00000 n 
+0000058820 00000 n 
+0000058924 00000 n 
+0000059028 00000 n 
+0000059132 00000 n 
+0000059236 00000 n 
+0000059340 00000 n 
+0000059444 00000 n 
+0000059548 00000 n 
+0000059652 00000 n 
+0000059756 00000 n 
+0000059860 00000 n 
+0000059964 00000 n 
+0000060068 00000 n 
+0000060172 00000 n 
+0000060276 00000 n 
+0000060380 00000 n 
+0000060484 00000 n 
+0000060588 00000 n 
+0000060692 00000 n 
+0000060796 00000 n 
+0000060900 00000 n 
+0000061004 00000 n 
+0000061108 00000 n 
+0000061212 00000 n 
+0000061316 00000 n 
+0000061420 00000 n 
+0000061524 00000 n 
+0000061628 00000 n 
+0000061732 00000 n 
+0000061836 00000 n 
+0000061940 00000 n 
+0000062044 00000 n 
+0000062147 00000 n 
+0000062251 00000 n 
+0000062355 00000 n 
+0000062459 00000 n 
+0000062563 00000 n 
+0000062667 00000 n 
+0000062771 00000 n 
+0000062875 00000 n 
+0000062979 00000 n 
+0000063083 00000 n 
+0000063187 00000 n 
+0000063291 00000 n 
+0000063395 00000 n 
+0000063499 00000 n 
+0000063603 00000 n 
+0000063707 00000 n 
+0000063811 00000 n 
+0000063914 00000 n 
+0000064016 00000 n 
+0000064118 00000 n 
+0000064543 00000 n 
+0000064647 00000 n 
+0000064751 00000 n 
+0000064855 00000 n 
+0000064959 00000 n 
+0000065063 00000 n 
+0000065167 00000 n 
+0000065271 00000 n 
+0000065375 00000 n 
+0000065479 00000 n 
+0000065583 00000 n 
+0000065687 00000 n 
+0000065791 00000 n 
+0000065895 00000 n 
+0000065999 00000 n 
+0000066103 00000 n 
+0000066207 00000 n 
+0000066311 00000 n 
+0000066415 00000 n 
+0000066519 00000 n 
+0000066623 00000 n 
+0000066727 00000 n 
+0000066831 00000 n 
+0000066935 00000 n 
+0000067039 00000 n 
+0000067143 00000 n 
+0000067247 00000 n 
+0000067351 00000 n 
+0000067455 00000 n 
+0000067559 00000 n 
+0000067663 00000 n 
+0000067767 00000 n 
+0000067871 00000 n 
+0000067975 00000 n 
+0000068079 00000 n 
+0000068183 00000 n 
+0000068480 00000 n 
+0000068529 00000 n 
+0000068616 00000 n 
+0000068720 00000 n 
+0000068824 00000 n 
+0000068927 00000 n 
+0000068976 00000 n 
+0000069080 00000 n 
+0000069183 00000 n 
+0000069216 00000 n 
+0000069272 00000 n 
+0000069359 00000 n 
+0000069428 00000 n 
+0000069515 00000 n 
+0000069566 00000 n 
+0000069653 00000 n 
+0000069738 00000 n 
+0000069825 00000 n 
+0000069881 00000 n 
+0000069968 00000 n 
+0000070018 00000 n 
+0000070105 00000 n 
+0000070157 00000 n 
+0000070244 00000 n 
+0000070306 00000 n 
+0000070391 00000 n 
+0000070472 00000 n 
+0000070526 00000 n 
+0000070612 00000 n 
+0000070666 00000 n 
+0000070753 00000 n 
+0000070786 00000 n 
+0000070827 00000 n 
+0000070914 00000 n 
+0000070958 00000 n 
+0000071045 00000 n 
+0000071090 00000 n 
+0000071177 00000 n 
+0000071221 00000 n 
+0000071308 00000 n 
+0000071352 00000 n 
+0000071439 00000 n 
+0000071481 00000 n 
+0000071568 00000 n 
+0000071616 00000 n 
+0000071703 00000 n 
+0000071776 00000 n 
+0000071880 00000 n 
+0000071983 00000 n 
+0000072016 00000 n 
+0000072069 00000 n 
+0000072155 00000 n 
+0000072180 00000 n 
+0000072227 00000 n 
+0000072313 00000 n 
+0000072360 00000 n 
+0000072446 00000 n 
+0000072479 00000 n 
+0000072524 00000 n 
+0000072611 00000 n 
+0000072656 00000 n 
+0000072742 00000 n 
+0000072775 00000 n 
+0000072820 00000 n 
+0000072906 00000 n 
+0000072949 00000 n 
+0000073035 00000 n 
+0000073076 00000 n 
+0000073162 00000 n 
+0000073211 00000 n 
+0000073297 00000 n 
+0000073343 00000 n 
+0000073429 00000 n 
+0000073474 00000 n 
+0000073560 00000 n 
+0000073612 00000 n 
+0000073698 00000 n 
+0000073748 00000 n 
+0000073834 00000 n 
+0000073880 00000 n 
+0000073966 00000 n 
+0000074009 00000 n 
+0000074095 00000 n 
+0000074139 00000 n 
+0000074225 00000 n 
+0000074268 00000 n 
+0000074354 00000 n 
+0000074399 00000 n 
+0000074485 00000 n 
+0000074523 00000 n 
+0000074609 00000 n 
+0000074651 00000 n 
+0000074737 00000 n 
+0000074780 00000 n 
+0000074866 00000 n 
+0000074904 00000 n 
+0000074990 00000 n 
+0000075032 00000 n 
+0000075118 00000 n 
+0000075162 00000 n 
+0000075248 00000 n 
+0000075295 00000 n 
+0000075381 00000 n 
+0000075483 00000 n 
+0000075585 00000 n 
+0000075778 00000 n 
+0000075882 00000 n 
+0000075907 00000 n 
+0000075956 00000 n 
+0000076042 00000 n 
+0000076067 00000 n 
+0000076114 00000 n 
+0000076201 00000 n 
+0000076305 00000 n 
+0000076338 00000 n 
+0000076391 00000 n 
+0000076478 00000 n 
+0000076503 00000 n 
+0000076607 00000 n 
+0000076710 00000 n 
+0000076814 00000 n 
+0000076855 00000 n 
+0000076897 00000 n 
+0000076984 00000 n 
+0000077027 00000 n 
+0000077114 00000 n 
+0000077164 00000 n 
+0000077251 00000 n 
+0000077299 00000 n 
+0000077386 00000 n 
+0000077435 00000 n 
+0000077478 00000 n 
+0000077565 00000 n 
+0000077619 00000 n 
+0000077706 00000 n 
+0000077751 00000 n 
+0000077838 00000 n 
+0000077895 00000 n 
+0000077981 00000 n 
+0000078077 00000 n 
+0000078162 00000 n 
+0000078219 00000 n 
+0000078265 00000 n 
+0000078352 00000 n 
+0000078398 00000 n 
+0000078483 00000 n 
+0000078527 00000 n 
+0000078614 00000 n 
+0000078665 00000 n 
+0000078752 00000 n 
+0000078801 00000 n 
+0000078888 00000 n 
+0000078945 00000 n 
+0000079008 00000 n 
+0000079095 00000 n 
+0000079153 00000 n 
+0000079240 00000 n 
+0000079334 00000 n 
+0000079420 00000 n 
+0000079461 00000 n 
+0000079504 00000 n 
+0000079590 00000 n 
+0000079638 00000 n 
+0000079725 00000 n 
+0000079766 00000 n 
+0000079853 00000 n 
+0000079897 00000 n 
+0000079984 00000 n 
+0000080028 00000 n 
+0000080114 00000 n 
+0000080171 00000 n 
+0000080217 00000 n 
+0000080304 00000 n 
+0000080353 00000 n 
+0000080438 00000 n 
+0000080471 00000 n 
+0000080525 00000 n 
+0000080612 00000 n 
+0000080663 00000 n 
+0000080750 00000 n 
+0000080804 00000 n 
+0000080891 00000 n 
+0000080941 00000 n 
+0000081028 00000 n 
+0000081077 00000 n 
+0000081127 00000 n 
+0000081212 00000 n 
+0000081237 00000 n 
+0000081301 00000 n 
+0000081388 00000 n 
+0000081413 00000 n 
+0000081465 00000 n 
+0000081550 00000 n 
+0000081575 00000 n 
+0000081639 00000 n 
+0000081726 00000 n 
+0000081792 00000 n 
+0000081879 00000 n 
+0000081937 00000 n 
+0000082024 00000 n 
+0000082118 00000 n 
+0000082205 00000 n 
+0000082269 00000 n 
+0000082356 00000 n 
+0000082417 00000 n 
+0000082504 00000 n 
+0000082569 00000 n 
+0000082646 00000 n 
+0000082732 00000 n 
+0000082757 00000 n 
+0000082847 00000 n 
+0000082933 00000 n 
+0000083022 00000 n 
+0000083108 00000 n 
+0000083179 00000 n 
+0000083265 00000 n 
+0000083397 00000 n 
+0000083483 00000 n 
+0000083532 00000 n 
+0000083606 00000 n 
 0000083692 00000 n 
-0000083733 00000 n 
-0000083798 00000 n 
-0000083885 00000 n 
-0000083910 00000 n 
-0000083972 00000 n 
-0000084059 00000 n 
-0000084084 00000 n 
+0000083789 00000 n 
+0000083875 00000 n 
+0000083940 00000 n 
+0000084027 00000 n 
+0000084068 00000 n 
 0000084133 00000 n 
 0000084220 00000 n 
 0000084245 00000 n 
-0000084293 00000 n 
-0000084380 00000 n 
-0000084430 00000 n 
-0000084514 00000 n 
-0000084558 00000 n 
-0000084642 00000 n 
-0000084683 00000 n 
-0000084727 00000 n 
-0000084813 00000 n 
-0000084863 00000 n 
-0000084949 00000 n 
-0000084999 00000 n 
-0000085085 00000 n 
-0000085134 00000 n 
-0000085220 00000 n 
-0000085267 00000 n 
-0000085353 00000 n 
-0000085410 00000 n 
-0000085492 00000 n 
-0000085579 00000 n 
-0000085664 00000 n 
-0000085751 00000 n 
-0000085803 00000 n 
-0000085890 00000 n 
-0000085942 00000 n 
-0000086028 00000 n 
-0000086077 00000 n 
-0000086192 00000 n 
-0000086279 00000 n 
-0000086394 00000 n 
-0000086480 00000 n 
-0000086513 00000 n 
-0000086566 00000 n 
-0000086653 00000 n 
-0000086703 00000 n 
-0000086790 00000 n 
-0000086823 00000 n 
-0000086912 00000 n 
-0000086998 00000 n 
-0000087061 00000 n 
-0000087146 00000 n 
-0000087179 00000 n 
-0000087240 00000 n 
-0000087326 00000 n 
-0000087351 00000 n 
-0000087470 00000 n 
-0000087556 00000 n 
-0000087599 00000 n 
+0000084307 00000 n 
+0000084394 00000 n 
+0000084419 00000 n 
+0000084468 00000 n 
+0000084555 00000 n 
+0000084580 00000 n 
+0000084628 00000 n 
+0000084715 00000 n 
+0000084765 00000 n 
+0000084849 00000 n 
+0000084893 00000 n 
+0000084977 00000 n 
+0000085018 00000 n 
+0000085062 00000 n 
+0000085148 00000 n 
+0000085198 00000 n 
+0000085284 00000 n 
+0000085334 00000 n 
+0000085420 00000 n 
+0000085469 00000 n 
+0000085555 00000 n 
+0000085602 00000 n 
+0000085688 00000 n 
+0000085745 00000 n 
+0000085827 00000 n 
+0000085914 00000 n 
+0000085999 00000 n 
+0000086086 00000 n 
+0000086138 00000 n 
+0000086225 00000 n 
+0000086277 00000 n 
+0000086363 00000 n 
+0000086412 00000 n 
+0000086527 00000 n 
+0000086614 00000 n 
+0000086729 00000 n 
+0000086815 00000 n 
+0000086848 00000 n 
+0000086901 00000 n 
+0000086988 00000 n 
+0000087038 00000 n 
+0000087125 00000 n 
+0000087158 00000 n 
+0000087247 00000 n 
+0000087333 00000 n 
+0000087396 00000 n 
+0000087481 00000 n 
+0000087514 00000 n 
+0000087575 00000 n 
+0000087661 00000 n 
 0000087686 00000 n 
-0000087729 00000 n 
-0000087816 00000 n 
-0000087857 00000 n 
-0000087961 00000 n 
+0000087805 00000 n 
+0000087891 00000 n 
+0000087934 00000 n 
+0000088021 00000 n 
 0000088064 00000 n 
-0000088097 00000 n 
-0000088150 00000 n 
-0000088237 00000 n 
-0000088262 00000 n 
-0000088317 00000 n 
-0000088404 00000 n 
-0000088429 00000 n 
-0000088478 00000 n 
-0000088565 00000 n 
-0000088628 00000 n 
-0000088715 00000 n 
-0000088778 00000 n 
-0000088865 00000 n 
-0000088919 00000 n 
-0000089006 00000 n 
-0000089055 00000 n 
-0000089123 00000 n 
-0000089209 00000 n 
-0000089264 00000 n 
-0000089351 00000 n 
-0000089384 00000 n 
-0000089439 00000 n 
-0000089525 00000 n 
+0000088151 00000 n 
+0000088192 00000 n 
+0000088296 00000 n 
+0000088399 00000 n 
+0000088432 00000 n 
+0000088485 00000 n 
+0000088572 00000 n 
+0000088597 00000 n 
+0000088652 00000 n 
+0000088739 00000 n 
+0000088764 00000 n 
+0000088856 00000 n 
+0000088942 00000 n 
+0000088967 00000 n 
+0000089016 00000 n 
+0000089103 00000 n 
+0000089166 00000 n 
+0000089253 00000 n 
+0000089316 00000 n 
+0000089403 00000 n 
+0000089457 00000 n 
+0000089544 00000 n 
 0000089593 00000 n 
-0000089679 00000 n 
-0000089754 00000 n 
-0000089841 00000 n 
-0000089911 00000 n 
-0000089997 00000 n 
-0000090076 00000 n 
-0000090163 00000 n 
-0000090220 00000 n 
-0000090302 00000 n 
-0000090388 00000 n 
-0000090463 00000 n 
-0000090550 00000 n 
-0000090623 00000 n 
-0000090710 00000 n 
-0000090788 00000 n 
-0000090875 00000 n 
-0000090924 00000 n 
-0000090972 00000 n 
-0000091059 00000 n 
-0000091084 00000 n 
-0000091132 00000 n 
-0000091219 00000 n 
-0000091313 00000 n 
-0000091400 00000 n 
-0000091494 00000 n 
-0000091580 00000 n 
-0000091621 00000 n 
-0000091725 00000 n 
-0000091750 00000 n 
-0000091805 00000 n 
-0000091892 00000 n 
-0000091948 00000 n 
-0000092035 00000 n 
-0000092068 00000 n 
-0000092116 00000 n 
-0000092203 00000 n 
-0000092277 00000 n 
-0000092364 00000 n 
-0000092432 00000 n 
-0000092519 00000 n 
+0000089661 00000 n 
+0000089747 00000 n 
+0000089802 00000 n 
+0000089889 00000 n 
+0000089922 00000 n 
+0000089977 00000 n 
+0000090063 00000 n 
+0000090131 00000 n 
+0000090217 00000 n 
+0000090292 00000 n 
+0000090379 00000 n 
+0000090449 00000 n 
+0000090535 00000 n 
+0000090614 00000 n 
+0000090701 00000 n 
+0000090758 00000 n 
+0000090840 00000 n 
+0000090926 00000 n 
+0000091001 00000 n 
+0000091088 00000 n 
+0000091161 00000 n 
+0000091248 00000 n 
+0000091326 00000 n 
+0000091413 00000 n 
+0000091462 00000 n 
+0000091510 00000 n 
+0000091597 00000 n 
+0000091622 00000 n 
+0000091670 00000 n 
+0000091757 00000 n 
+0000091851 00000 n 
+0000091938 00000 n 
+0000092032 00000 n 
+0000092118 00000 n 
+0000092159 00000 n 
+0000092263 00000 n 
+0000092288 00000 n 
+0000092343 00000 n 
+0000092430 00000 n 
+0000092486 00000 n 
 0000092573 00000 n 
-0000092660 00000 n 
-0000092728 00000 n 
+0000092606 00000 n 
+0000092654 00000 n 
+0000092741 00000 n 
 0000092815 00000 n 
-0000092889 00000 n 
-0000092976 00000 n 
-0000093024 00000 n 
+0000092902 00000 n 
+0000092970 00000 n 
+0000093057 00000 n 
 0000093111 00000 n 
-0000093168 00000 n 
-0000093255 00000 n 
-0000093336 00000 n 
-0000093391 00000 n 
-0000093477 00000 n 
-0000093558 00000 n 
-0000093645 00000 n 
-0000093678 00000 n 
-0000093732 00000 n 
-0000093819 00000 n 
-0000093883 00000 n 
-0000093970 00000 n 
-0000094025 00000 n 
-0000094112 00000 n 
+0000093198 00000 n 
+0000093266 00000 n 
+0000093353 00000 n 
+0000093427 00000 n 
+0000093514 00000 n 
+0000093562 00000 n 
+0000093649 00000 n 
+0000093706 00000 n 
+0000093793 00000 n 
+0000093874 00000 n 
+0000093929 00000 n 
+0000094015 00000 n 
+0000094096 00000 n 
+0000094183 00000 n 
 0000094216 00000 n 
-0000094265 00000 n 
-0000094299 00000 n 
-0000094333 00000 n 
-0000101136 00000 n 
-0000101180 00000 n 
-0000101224 00000 n 
-0000101268 00000 n 
-0000101312 00000 n 
-0000101356 00000 n 
-0000101400 00000 n 
-0000101444 00000 n 
-0000101488 00000 n 
-0000101532 00000 n 
-0000101576 00000 n 
-0000101620 00000 n 
-0000101664 00000 n 
-0000101708 00000 n 
-0000101753 00000 n 
-0000101798 00000 n 
-0000101843 00000 n 
-0000101888 00000 n 
-0000101933 00000 n 
-0000101978 00000 n 
-0000102023 00000 n 
-0000102068 00000 n 
-0000102113 00000 n 
-0000102158 00000 n 
-0000102203 00000 n 
-0000102248 00000 n 
-0000102293 00000 n 
-0000102338 00000 n 
-0000102383 00000 n 
-0000102428 00000 n 
-0000102473 00000 n 
-0000102518 00000 n 
-0000102563 00000 n 
-0000102608 00000 n 
-0000102653 00000 n 
-0000102698 00000 n 
-0000102743 00000 n 
-0000102788 00000 n 
-0000102833 00000 n 
-0000102878 00000 n 
-0000102923 00000 n 
-0000102968 00000 n 
-0000103013 00000 n 
-0000103058 00000 n 
-0000103103 00000 n 
-0000103148 00000 n 
-0000103193 00000 n 
-0000103238 00000 n 
-0000103283 00000 n 
-0000103328 00000 n 
-0000103373 00000 n 
-0000103418 00000 n 
-0000103463 00000 n 
-0000103508 00000 n 
-0000103553 00000 n 
-0000103598 00000 n 
-0000103643 00000 n 
-0000103688 00000 n 
-0000103733 00000 n 
-0000103778 00000 n 
-0000103823 00000 n 
-0000103868 00000 n 
-0000103913 00000 n 
-0000103958 00000 n 
-0000104003 00000 n 
-0000104048 00000 n 
-0000104093 00000 n 
-0000104138 00000 n 
-0000104183 00000 n 
-0000104228 00000 n 
-0000104273 00000 n 
-0000104318 00000 n 
-0000104363 00000 n 
-0000104408 00000 n 
-0000104453 00000 n 
-0000104498 00000 n 
-0000104543 00000 n 
-0000104588 00000 n 
-0000104633 00000 n 
-0000104678 00000 n 
-0000104723 00000 n 
-0000104768 00000 n 
-0000104813 00000 n 
-0000104858 00000 n 
-0000104903 00000 n 
-0000104948 00000 n 
-0000104993 00000 n 
-0000105038 00000 n 
-0000105083 00000 n 
-0000105128 00000 n 
-0000105173 00000 n 
-0000105218 00000 n 
-0000105263 00000 n 
-0000105308 00000 n 
-0000105353 00000 n 
-0000105398 00000 n 
-0000105443 00000 n 
-0000105488 00000 n 
-0000105533 00000 n 
-0000105578 00000 n 
-0000105623 00000 n 
-0000105668 00000 n 
-0000105713 00000 n 
-0000105758 00000 n 
-0000105803 00000 n 
-0000105848 00000 n 
-0000105893 00000 n 
-0000105938 00000 n 
-0000105983 00000 n 
-0000106028 00000 n 
-0000106073 00000 n 
-0000106118 00000 n 
-0000106163 00000 n 
-0000106208 00000 n 
-0000106253 00000 n 
-0000106298 00000 n 
-0000106343 00000 n 
-0000106388 00000 n 
-0000106433 00000 n 
-0000106478 00000 n 
-0000106523 00000 n 
-0000106568 00000 n 
-0000106613 00000 n 
-0000106658 00000 n 
-0000106703 00000 n 
-0000106748 00000 n 
-0000106793 00000 n 
-0000106838 00000 n 
-0000106883 00000 n 
-0000106928 00000 n 
-0000106973 00000 n 
-0000107018 00000 n 
-0000107063 00000 n 
-0000107108 00000 n 
-0000107153 00000 n 
-0000107198 00000 n 
-0000107243 00000 n 
-0000107288 00000 n 
-0000107333 00000 n 
-0000107378 00000 n 
-0000107423 00000 n 
-0000107468 00000 n 
-0000107513 00000 n 
-0000107558 00000 n 
-0000107603 00000 n 
-0000107648 00000 n 
-0000107693 00000 n 
-0000107738 00000 n 
-0000107783 00000 n 
-0000107828 00000 n 
-0000107873 00000 n 
-0000107918 00000 n 
-0000107963 00000 n 
-0000108008 00000 n 
-0000108053 00000 n 
-0000108098 00000 n 
-0000108143 00000 n 
-0000108188 00000 n 
-0000108233 00000 n 
-0000108278 00000 n 
-0000108323 00000 n 
-0000108368 00000 n 
-0000108413 00000 n 
-0000108458 00000 n 
-0000108503 00000 n 
-0000108548 00000 n 
-0000108593 00000 n 
-0000108638 00000 n 
-0000108683 00000 n 
-0000108728 00000 n 
-0000108773 00000 n 
-0000108818 00000 n 
-0000108863 00000 n 
-0000108908 00000 n 
-0000108953 00000 n 
-0000108998 00000 n 
-0000109043 00000 n 
-0000109088 00000 n 
-0000109133 00000 n 
-0000109178 00000 n 
-0000109223 00000 n 
-0000109268 00000 n 
-0000109313 00000 n 
-0000109358 00000 n 
-0000109403 00000 n 
-0000109448 00000 n 
-0000109493 00000 n 
-0000109538 00000 n 
-0000109583 00000 n 
-0000109628 00000 n 
-0000109673 00000 n 
-0000109718 00000 n 
-0000109763 00000 n 
-0000109808 00000 n 
-0000109853 00000 n 
-0000109898 00000 n 
-0000109943 00000 n 
-0000109988 00000 n 
-0000110033 00000 n 
-0000110078 00000 n 
-0000110123 00000 n 
-0000110168 00000 n 
-0000110213 00000 n 
-0000110258 00000 n 
-0000110303 00000 n 
-0000110348 00000 n 
-0000110393 00000 n 
-0000110438 00000 n 
-0000110483 00000 n 
-0000110528 00000 n 
-0000110573 00000 n 
-0000110618 00000 n 
-0000110663 00000 n 
-0000110708 00000 n 
-0000110753 00000 n 
-0000110798 00000 n 
-0000110843 00000 n 
-0000110888 00000 n 
-0000110933 00000 n 
-0000110978 00000 n 
-0000111023 00000 n 
-0000111068 00000 n 
-0000111113 00000 n 
-0000111158 00000 n 
-0000111203 00000 n 
-0000111248 00000 n 
-0000111293 00000 n 
-0000111338 00000 n 
-0000111383 00000 n 
-0000111428 00000 n 
-0000111473 00000 n 
-0000111518 00000 n 
-0000111563 00000 n 
-0000111608 00000 n 
-0000111653 00000 n 
-0000111698 00000 n 
-0000111743 00000 n 
-0000111788 00000 n 
-0000111833 00000 n 
-0000111878 00000 n 
-0000111923 00000 n 
-0000111968 00000 n 
-0000112013 00000 n 
-0000112058 00000 n 
-0000112103 00000 n 
-0000112148 00000 n 
-0000112193 00000 n 
-0000112238 00000 n 
-0000112283 00000 n 
-0000112328 00000 n 
-0000112373 00000 n 
-0000112418 00000 n 
-0000112463 00000 n 
-0000112508 00000 n 
-0000112553 00000 n 
-0000112598 00000 n 
-0000112643 00000 n 
-0000112688 00000 n 
-0000112733 00000 n 
-0000112778 00000 n 
-0000112823 00000 n 
-0000112868 00000 n 
-0000112913 00000 n 
-0000112958 00000 n 
-0000113003 00000 n 
-0000113048 00000 n 
-0000113093 00000 n 
-0000113138 00000 n 
-0000113183 00000 n 
-0000113228 00000 n 
-0000113273 00000 n 
-0000113318 00000 n 
-0000113363 00000 n 
-0000113408 00000 n 
-0000113453 00000 n 
-0000113498 00000 n 
-0000113543 00000 n 
-0000113588 00000 n 
-0000113633 00000 n 
-0000113678 00000 n 
-0000113723 00000 n 
-0000113768 00000 n 
-0000113813 00000 n 
-0000113858 00000 n 
-0000113903 00000 n 
-0000113948 00000 n 
-0000113993 00000 n 
-0000114038 00000 n 
-0000114083 00000 n 
-0000114128 00000 n 
-0000114173 00000 n 
-0000114218 00000 n 
-0000114263 00000 n 
-0000114308 00000 n 
-0000114353 00000 n 
-0000114398 00000 n 
-0000114443 00000 n 
-0000114488 00000 n 
-0000114533 00000 n 
-0000114578 00000 n 
-0000114623 00000 n 
-0000114668 00000 n 
-0000114713 00000 n 
-0000114758 00000 n 
-0000114803 00000 n 
-0000114848 00000 n 
-0000114893 00000 n 
-0000114938 00000 n 
-0000114983 00000 n 
-0000115028 00000 n 
-0000115073 00000 n 
-0000115118 00000 n 
-0000115163 00000 n 
-0000115208 00000 n 
-0000115253 00000 n 
-0000115298 00000 n 
-0000115343 00000 n 
-0000115388 00000 n 
-0000115433 00000 n 
-0000115478 00000 n 
-0000115523 00000 n 
-0000115568 00000 n 
-0000115613 00000 n 
-0000115658 00000 n 
-0000115703 00000 n 
-0000115748 00000 n 
-0000115793 00000 n 
-0000115838 00000 n 
-0000115883 00000 n 
-0000115928 00000 n 
-0000115973 00000 n 
-0000116018 00000 n 
-0000116063 00000 n 
-0000116108 00000 n 
-0000116153 00000 n 
-0000116198 00000 n 
-0000116243 00000 n 
-0000116288 00000 n 
-0000116333 00000 n 
-0000116378 00000 n 
-0000116423 00000 n 
-0000116468 00000 n 
-0000116513 00000 n 
-0000116558 00000 n 
-0000116603 00000 n 
-0000116648 00000 n 
-0000116693 00000 n 
-0000116738 00000 n 
-0000116783 00000 n 
-0000116828 00000 n 
-0000116873 00000 n 
-0000116918 00000 n 
-0000116963 00000 n 
-0000117008 00000 n 
-0000117053 00000 n 
-0000117098 00000 n 
-0000117143 00000 n 
-0000117188 00000 n 
-0000117233 00000 n 
-0000117278 00000 n 
-0000117323 00000 n 
-0000117368 00000 n 
-0000117413 00000 n 
-0000117458 00000 n 
-0000117503 00000 n 
-0000117548 00000 n 
-0000117593 00000 n 
-0000117638 00000 n 
-0000117683 00000 n 
-0000117728 00000 n 
-0000117773 00000 n 
-0000117817 00000 n 
-0000117862 00000 n 
-0000117907 00000 n 
-0000117952 00000 n 
-0000117997 00000 n 
-0000118042 00000 n 
-0000118087 00000 n 
-0000118132 00000 n 
-0000118177 00000 n 
-0000118222 00000 n 
-0000118267 00000 n 
-0000118312 00000 n 
-0000118357 00000 n 
-0000118402 00000 n 
-0000118447 00000 n 
-0000118492 00000 n 
-0000118537 00000 n 
-0000118582 00000 n 
-0000118627 00000 n 
-0000118672 00000 n 
-0000118717 00000 n 
-0000118762 00000 n 
-0000118807 00000 n 
-0000120647 00000 n 
-0000120808 00000 n 
-0000120977 00000 n 
-0000121170 00000 n 
-0000125071 00000 n 
-0000125265 00000 n 
-0000129072 00000 n 
-0000129266 00000 n 
-0000134424 00000 n 
-0000134618 00000 n 
-0000138781 00000 n 
-0000138975 00000 n 
-0000142887 00000 n 
-0000143081 00000 n 
-0000146904 00000 n 
-0000147098 00000 n 
-0000150869 00000 n 
-0000151063 00000 n 
-0000155066 00000 n 
-0000155260 00000 n 
-0000156680 00000 n 
-0000156892 00000 n 
-0000158867 00000 n 
-0000159051 00000 n 
-0000162262 00000 n 
-0000162446 00000 n 
-0000165347 00000 n 
-0000165522 00000 n 
-0000168280 00000 n 
-0000168455 00000 n 
-0000170117 00000 n 
-0000170278 00000 n 
-0000170466 00000 n 
-0000170636 00000 n 
-0000170948 00000 n 
-0000171137 00000 n 
-0000173323 00000 n 
-0000173503 00000 n 
-0000175677 00000 n 
-0000175866 00000 n 
-0000178037 00000 n 
-0000178216 00000 n 
-0000179409 00000 n 
-0000179621 00000 n 
-0000181131 00000 n 
-0000181348 00000 n 
-0000182781 00000 n 
-0000182984 00000 n 
-0000184908 00000 n 
-0000185128 00000 n 
-0000186954 00000 n 
-0000187152 00000 n 
-0000189080 00000 n 
-0000189287 00000 n 
-0000191205 00000 n 
-0000191414 00000 n 
-0000193726 00000 n 
-0000193914 00000 n 
-0000195105 00000 n 
-0000195334 00000 n 
-0000197203 00000 n 
-0000197432 00000 n 
-0000198999 00000 n 
-0000199196 00000 n 
-0000200691 00000 n 
-0000200904 00000 n 
-0000203089 00000 n 
-0000203292 00000 n 
-0000205041 00000 n 
-0000205255 00000 n 
-0000206667 00000 n 
-0000206889 00000 n 
-0000208588 00000 n 
-0000208792 00000 n 
-0000210540 00000 n 
-0000210738 00000 n 
-0000211964 00000 n 
-0000212203 00000 n 
-0000213822 00000 n 
-0000214019 00000 n 
-0000215192 00000 n 
-0000215353 00000 n 
-0000215543 00000 n 
-0000215713 00000 n 
-0000216011 00000 n 
-0000216200 00000 n 
-0000217886 00000 n 
-0000218074 00000 n 
-0000219505 00000 n 
-0000219702 00000 n 
-0000221463 00000 n 
-0000221643 00000 n 
-0000223607 00000 n 
-0000223820 00000 n 
-0000225617 00000 n 
-0000225839 00000 n 
-0000226896 00000 n 
-0000227126 00000 n 
-0000228519 00000 n 
-0000228733 00000 n 
-0000230256 00000 n 
-0000230469 00000 n 
-0000232473 00000 n 
-0000232747 00000 n 
-0000234532 00000 n 
-0000234745 00000 n 
-0000236356 00000 n 
-0000236554 00000 n 
-0000238221 00000 n 
-0000238400 00000 n 
-0000240432 00000 n 
-0000240662 00000 n 
-0000242482 00000 n 
-0000242676 00000 n 
-0000244231 00000 n 
-0000244411 00000 n 
-0000246151 00000 n 
-0000246340 00000 n 
-0000247541 00000 n 
-0000247806 00000 n 
-0000249273 00000 n 
-0000249471 00000 n 
-0000250451 00000 n 
-0000250683 00000 n 
-0000252086 00000 n 
-0000252321 00000 n 
-0000254238 00000 n 
-0000254399 00000 n 
-0000254592 00000 n 
-0000254762 00000 n 
-0000255062 00000 n 
-0000255301 00000 n 
-0000257056 00000 n 
-0000257263 00000 n 
-0000259107 00000 n 
-0000259305 00000 n 
-0000260950 00000 n 
-0000261162 00000 n 
-0000262578 00000 n 
-0000262757 00000 n 
-0000263574 00000 n 
-0000263771 00000 n 
-0000265266 00000 n 
-0000265530 00000 n 
-0000267253 00000 n 
-0000267499 00000 n 
-0000269427 00000 n 
-0000269659 00000 n 
-0000271669 00000 n 
-0000271901 00000 n 
-0000273553 00000 n 
-0000273757 00000 n 
-0000275102 00000 n 
-0000275324 00000 n 
-0000276887 00000 n 
-0000277066 00000 n 
-0000278635 00000 n 
-0000278814 00000 n 
-0000280334 00000 n 
-0000280513 00000 n 
-0000282016 00000 n 
-0000282195 00000 n 
-0000283861 00000 n 
-0000284031 00000 n 
-0000284776 00000 n 
-0000284998 00000 n 
-0000286916 00000 n 
-0000287157 00000 n 
-0000288886 00000 n 
-0000289098 00000 n 
-0000291157 00000 n 
-0000291355 00000 n 
-0000293409 00000 n 
-0000293616 00000 n 
-0000295434 00000 n 
-0000295647 00000 n 
-0000297750 00000 n 
-0000297957 00000 n 
-0000299706 00000 n 
-0000299893 00000 n 
-0000301572 00000 n 
-0000301761 00000 n 
-0000302653 00000 n 
-0000302823 00000 n 
-0000303921 00000 n 
-0000304091 00000 n 
-0000304782 00000 n 
-0000304952 00000 n 
-0000305813 00000 n 
-0000305983 00000 n 
-0000307084 00000 n 
-0000307307 00000 n 
-0000308689 00000 n 
-0000308905 00000 n 
-0000310685 00000 n 
-0000310920 00000 n 
-0000312904 00000 n 
-0000313083 00000 n 
-0000314886 00000 n 
-0000315055 00000 n 
-0000316566 00000 n 
-0000316824 00000 n 
-0000319173 00000 n 
-0000319394 00000 n 
-0000321537 00000 n 
-0000321757 00000 n 
-0000323626 00000 n 
-0000323845 00000 n 
-0000325503 00000 n 
-0000325692 00000 n 
-0000327384 00000 n 
-0000327563 00000 n 
-0000329308 00000 n 
-0000329496 00000 n 
-0000331330 00000 n 
-0000331524 00000 n 
-0000333439 00000 n 
-0000333670 00000 n 
-0000335775 00000 n 
-0000335987 00000 n 
-0000337423 00000 n 
-0000337636 00000 n 
-0000339085 00000 n 
-0000339292 00000 n 
-0000340529 00000 n 
-0000340708 00000 n 
-0000341695 00000 n 
-0000341883 00000 n 
-0000343015 00000 n 
-0000343203 00000 n 
-0000344704 00000 n 
-0000344892 00000 n 
-0000345974 00000 n 
-0000346163 00000 n 
-0000347496 00000 n 
-0000347702 00000 n 
-0000349352 00000 n 
-0000349606 00000 n 
-0000351387 00000 n 
-0000351556 00000 n 
-0000352952 00000 n 
-0000353121 00000 n 
-0000353889 00000 n 
-0000354092 00000 n 
-0000356047 00000 n 
-0000356244 00000 n 
-0000358444 00000 n 
-0000358664 00000 n 
-0000360640 00000 n 
-0000360828 00000 n 
-0000362565 00000 n 
-0000362744 00000 n 
-0000364069 00000 n 
-0000364309 00000 n 
-0000365825 00000 n 
-0000366022 00000 n 
-0000367847 00000 n 
-0000368035 00000 n 
-0000370034 00000 n 
-0000370277 00000 n 
-0000372102 00000 n 
-0000372291 00000 n 
-0000373924 00000 n 
-0000374145 00000 n 
-0000375844 00000 n 
-0000376066 00000 n 
-0000377722 00000 n 
-0000377901 00000 n 
-0000379790 00000 n 
-0000379968 00000 n 
-0000381309 00000 n 
-0000381541 00000 n 
-0000383367 00000 n 
-0000383545 00000 n 
-0000384954 00000 n 
-0000385114 00000 n 
-0000385404 00000 n 
-0000385583 00000 n 
-0000387362 00000 n 
-0000387560 00000 n 
-0000389288 00000 n 
-0000389508 00000 n 
-0000391116 00000 n 
-0000391345 00000 n 
-0000392904 00000 n 
-0000393114 00000 n 
-0000394806 00000 n 
-0000395009 00000 n 
-0000396130 00000 n 
-0000396327 00000 n 
-0000397604 00000 n 
-0000397807 00000 n 
-0000398920 00000 n 
-0000399105 00000 n 
-0000399957 00000 n 
-0000400170 00000 n 
-0000401657 00000 n 
-0000401837 00000 n 
-0000402601 00000 n 
-0000402842 00000 n 
-0000404449 00000 n 
-0000404647 00000 n 
-0000406497 00000 n 
-0000406694 00000 n 
-0000408317 00000 n 
-0000408496 00000 n 
-0000410549 00000 n 
-0000410728 00000 n 
-0000412566 00000 n 
-0000412745 00000 n 
-0000414455 00000 n 
-0000414634 00000 n 
-0000415065 00000 n 
-0000415285 00000 n 
-0000417022 00000 n 
-0000417219 00000 n 
-0000419073 00000 n 
-0000419242 00000 n 
-0000420939 00000 n 
-0000421108 00000 n 
-0000422317 00000 n 
-0000422505 00000 n 
-0000424203 00000 n 
-0000424391 00000 n 
-0000425847 00000 n 
-0000426060 00000 n 
-0000427662 00000 n 
-0000427850 00000 n 
-0000429511 00000 n 
-0000429699 00000 n 
-0000430528 00000 n 
-0000430716 00000 n 
-0000432287 00000 n 
-0000432481 00000 n 
-0000433747 00000 n 
-0000433959 00000 n 
-0000435553 00000 n 
-0000435732 00000 n 
-0000436103 00000 n 
-0000436264 00000 n 
-0000436464 00000 n 
-0000436658 00000 n 
-0000438241 00000 n 
-0000438454 00000 n 
-0000439982 00000 n 
-0000440170 00000 n 
-0000441432 00000 n 
-0000441620 00000 n 
-0000442889 00000 n 
-0000443142 00000 n 
-0000444479 00000 n 
-0000444677 00000 n 
-0000446207 00000 n 
-0000446386 00000 n 
-0000447319 00000 n 
-0000447498 00000 n 
-0000449026 00000 n 
-0000449214 00000 n 
-0000450183 00000 n 
-0000450362 00000 n 
-0000451195 00000 n 
-0000451390 00000 n 
-0000453121 00000 n 
-0000453334 00000 n 
-0000455017 00000 n 
-0000455211 00000 n 
-0000456918 00000 n 
-0000457153 00000 n 
-0000458838 00000 n 
-0000459008 00000 n 
-0000459535 00000 n 
-0000459705 00000 n 
-0000461212 00000 n 
-0000461382 00000 n 
-0000462781 00000 n 
-0000462951 00000 n 
-0000464501 00000 n 
-0000464670 00000 n 
-0000465634 00000 n 
-0000465884 00000 n 
-0000467353 00000 n 
-0000467540 00000 n 
-0000469484 00000 n 
-0000469713 00000 n 
-0000471573 00000 n 
-0000471780 00000 n 
-0000473912 00000 n 
-0000474115 00000 n 
-0000474870 00000 n 
-0000475074 00000 n 
-0000476876 00000 n 
-0000477098 00000 n 
-0000478962 00000 n 
-0000479184 00000 n 
-0000480738 00000 n 
-0000480951 00000 n 
-0000482697 00000 n 
-0000482914 00000 n 
-0000484698 00000 n 
-0000484757 00000 n 
-0000484860 00000 n 
-0000485025 00000 n 
-0000485121 00000 n 
-0000485239 00000 n 
-0000485355 00000 n 
-0000485464 00000 n 
-0000485587 00000 n 
-0000485699 00000 n 
-0000485869 00000 n 
-0000485970 00000 n 
-0000486086 00000 n 
-0000486207 00000 n 
-0000486327 00000 n 
-0000486452 00000 n 
-0000486565 00000 n 
-0000486669 00000 n 
-0000486847 00000 n 
-0000486968 00000 n 
-0000487128 00000 n 
-0000487246 00000 n 
-0000487343 00000 n 
-0000487495 00000 n 
-0000487635 00000 n 
-0000487813 00000 n 
-0000487968 00000 n 
-0000488070 00000 n 
-0000488170 00000 n 
-0000488379 00000 n 
-0000488480 00000 n 
-0000488668 00000 n 
-0000488809 00000 n 
-0000488953 00000 n 
-0000489107 00000 n 
-0000489216 00000 n 
-0000489328 00000 n 
-0000489495 00000 n 
-0000489607 00000 n 
-0000489781 00000 n 
-0000489884 00000 n 
-0000490057 00000 n 
-0000490178 00000 n 
-0000490308 00000 n 
-0000490434 00000 n 
-0000490549 00000 n 
-0000490657 00000 n 
-0000490804 00000 n 
-0000490909 00000 n 
-0000491028 00000 n 
-0000491157 00000 n 
-0000491316 00000 n 
-0000491450 00000 n 
-0000491587 00000 n 
-0000491719 00000 n 
-0000491868 00000 n 
-0000492000 00000 n 
-0000492148 00000 n 
-0000492262 00000 n 
-0000492380 00000 n 
-0000492534 00000 n 
-0000492665 00000 n 
-0000492759 00000 n 
-0000492883 00000 n 
-0000492995 00000 n 
-0000493172 00000 n 
-0000493281 00000 n 
-0000493406 00000 n 
-0000493552 00000 n 
-0000493654 00000 n 
-0000493830 00000 n 
-0000493974 00000 n 
-0000494086 00000 n 
-0000494213 00000 n 
-0000494341 00000 n 
-0000494469 00000 n 
-0000494580 00000 n 
-0000494779 00000 n 
-0000494890 00000 n 
-0000495005 00000 n 
-0000495149 00000 n 
-0000495357 00000 n 
-0000495491 00000 n 
-0000495645 00000 n 
-0000495770 00000 n 
-0000495939 00000 n 
-0000496072 00000 n 
-0000496360 00000 n 
-0000496513 00000 n 
-0000496707 00000 n 
-0000496918 00000 n 
-0000497079 00000 n 
-0000497200 00000 n 
-0000497403 00000 n 
-0000497514 00000 n 
-0000497629 00000 n 
-0000497822 00000 n 
-0000497965 00000 n 
-0000498081 00000 n 
-0000498239 00000 n 
-0000498396 00000 n 
-0000498527 00000 n 
-0000498648 00000 n 
-0000498825 00000 n 
-0000498935 00000 n 
-0000499065 00000 n 
-0000499235 00000 n 
-0000499329 00000 n 
-0000499456 00000 n 
-0000499583 00000 n 
-0000499679 00000 n 
-0000499866 00000 n 
-0000499993 00000 n 
-0000500127 00000 n 
-0000500254 00000 n 
-0000500366 00000 n 
-0000500572 00000 n 
-0000500731 00000 n 
-0000500879 00000 n 
-0000501007 00000 n 
-0000501188 00000 n 
-0000501298 00000 n 
-0000501413 00000 n 
-0000501558 00000 n 
-0000501722 00000 n 
-0000501872 00000 n 
-0000502009 00000 n 
-0000502175 00000 n 
-0000502279 00000 n 
-0000502436 00000 n 
-0000502547 00000 n 
-0000502692 00000 n 
-0000502834 00000 n 
-0000502984 00000 n 
-0000503101 00000 n 
-0000503265 00000 n 
-0000503376 00000 n 
-0000503516 00000 n 
-0000503643 00000 n 
-0000503760 00000 n 
-0000503899 00000 n 
-0000504005 00000 n 
-0000504139 00000 n 
-0000504271 00000 n 
-0000504416 00000 n 
-0000504543 00000 n 
-0000504675 00000 n 
-0000504805 00000 n 
-0000504930 00000 n 
-0000505038 00000 n 
-0000505210 00000 n 
-0000505314 00000 n 
-0000505449 00000 n 
-0000505584 00000 n 
-0000505818 00000 n 
-0000505972 00000 n 
-0000506113 00000 n 
-0000506287 00000 n 
-0000506377 00000 n 
-0000506505 00000 n 
-0000506679 00000 n 
-0000506781 00000 n 
-0000506932 00000 n 
-0000507083 00000 n 
-0000507209 00000 n 
-0000507415 00000 n 
-0000507515 00000 n 
-0000507633 00000 n 
-0000507798 00000 n 
-0000507889 00000 n 
-0000508050 00000 n 
-0000508176 00000 n 
-0000508319 00000 n 
-0000508446 00000 n 
-0000508586 00000 n 
-0000508722 00000 n 
-0000508830 00000 n 
-0000509004 00000 n 
-0000509110 00000 n 
-0000509230 00000 n 
-0000509342 00000 n 
-0000509459 00000 n 
-0000509561 00000 n 
-0000509739 00000 n 
-0000509908 00000 n 
-0000510016 00000 n 
-0000510150 00000 n 
-0000510268 00000 n 
-0000510445 00000 n 
-0000510612 00000 n 
-0000510728 00000 n 
+0000094270 00000 n 
+0000094357 00000 n 
+0000094421 00000 n 
+0000094508 00000 n 
+0000094563 00000 n 
+0000094650 00000 n 
+0000094754 00000 n 
+0000094803 00000 n 
+0000094837 00000 n 
+0000094871 00000 n 
+0000101697 00000 n 
+0000101741 00000 n 
+0000101785 00000 n 
+0000101829 00000 n 
+0000101873 00000 n 
+0000101917 00000 n 
+0000101961 00000 n 
+0000102005 00000 n 
+0000102050 00000 n 
+0000102095 00000 n 
+0000102140 00000 n 
+0000102185 00000 n 
+0000102230 00000 n 
+0000102275 00000 n 
+0000102320 00000 n 
+0000102365 00000 n 
+0000102410 00000 n 
+0000102455 00000 n 
+0000102500 00000 n 
+0000102545 00000 n 
+0000102590 00000 n 
+0000102635 00000 n 
+0000102680 00000 n 
+0000102725 00000 n 
+0000102770 00000 n 
+0000102815 00000 n 
+0000102860 00000 n 
+0000102905 00000 n 
+0000102950 00000 n 
+0000102995 00000 n 
+0000103040 00000 n 
+0000103085 00000 n 
+0000103130 00000 n 
+0000103175 00000 n 
+0000103220 00000 n 
+0000103265 00000 n 
+0000103310 00000 n 
+0000103355 00000 n 
+0000103400 00000 n 
+0000103445 00000 n 
+0000103490 00000 n 
+0000103535 00000 n 
+0000103580 00000 n 
+0000103625 00000 n 
+0000103670 00000 n 
+0000103715 00000 n 
+0000103760 00000 n 
+0000103805 00000 n 
+0000103850 00000 n 
+0000103895 00000 n 
+0000103940 00000 n 
+0000103985 00000 n 
+0000104030 00000 n 
+0000104075 00000 n 
+0000104120 00000 n 
+0000104165 00000 n 
+0000104210 00000 n 
+0000104255 00000 n 
+0000104300 00000 n 
+0000104345 00000 n 
+0000104390 00000 n 
+0000104435 00000 n 
+0000104480 00000 n 
+0000104525 00000 n 
+0000104570 00000 n 
+0000104615 00000 n 
+0000104660 00000 n 
+0000104705 00000 n 
+0000104750 00000 n 
+0000104795 00000 n 
+0000104840 00000 n 
+0000104885 00000 n 
+0000104930 00000 n 
+0000104975 00000 n 
+0000105020 00000 n 
+0000105065 00000 n 
+0000105110 00000 n 
+0000105155 00000 n 
+0000105200 00000 n 
+0000105245 00000 n 
+0000105290 00000 n 
+0000105335 00000 n 
+0000105380 00000 n 
+0000105425 00000 n 
+0000105470 00000 n 
+0000105515 00000 n 
+0000105560 00000 n 
+0000105605 00000 n 
+0000105650 00000 n 
+0000105695 00000 n 
+0000105740 00000 n 
+0000105785 00000 n 
+0000105830 00000 n 
+0000105875 00000 n 
+0000105920 00000 n 
+0000105965 00000 n 
+0000106010 00000 n 
+0000106055 00000 n 
+0000106100 00000 n 
+0000106145 00000 n 
+0000106190 00000 n 
+0000106235 00000 n 
+0000106280 00000 n 
+0000106325 00000 n 
+0000106370 00000 n 
+0000106415 00000 n 
+0000106460 00000 n 
+0000106505 00000 n 
+0000106550 00000 n 
+0000106595 00000 n 
+0000106640 00000 n 
+0000106685 00000 n 
+0000106730 00000 n 
+0000106775 00000 n 
+0000106820 00000 n 
+0000106865 00000 n 
+0000106910 00000 n 
+0000106955 00000 n 
+0000107000 00000 n 
+0000107045 00000 n 
+0000107090 00000 n 
+0000107135 00000 n 
+0000107180 00000 n 
+0000107225 00000 n 
+0000107270 00000 n 
+0000107315 00000 n 
+0000107360 00000 n 
+0000107405 00000 n 
+0000107450 00000 n 
+0000107495 00000 n 
+0000107540 00000 n 
+0000107585 00000 n 
+0000107630 00000 n 
+0000107675 00000 n 
+0000107720 00000 n 
+0000107765 00000 n 
+0000107810 00000 n 
+0000107855 00000 n 
+0000107900 00000 n 
+0000107945 00000 n 
+0000107990 00000 n 
+0000108035 00000 n 
+0000108080 00000 n 
+0000108125 00000 n 
+0000108170 00000 n 
+0000108215 00000 n 
+0000108260 00000 n 
+0000108305 00000 n 
+0000108350 00000 n 
+0000108395 00000 n 
+0000108440 00000 n 
+0000108485 00000 n 
+0000108530 00000 n 
+0000108575 00000 n 
+0000108620 00000 n 
+0000108665 00000 n 
+0000108710 00000 n 
+0000108755 00000 n 
+0000108800 00000 n 
+0000108845 00000 n 
+0000108890 00000 n 
+0000108935 00000 n 
+0000108980 00000 n 
+0000109025 00000 n 
+0000109070 00000 n 
+0000109115 00000 n 
+0000109160 00000 n 
+0000109205 00000 n 
+0000109250 00000 n 
+0000109295 00000 n 
+0000109340 00000 n 
+0000109385 00000 n 
+0000109430 00000 n 
+0000109475 00000 n 
+0000109520 00000 n 
+0000109565 00000 n 
+0000109610 00000 n 
+0000109655 00000 n 
+0000109700 00000 n 
+0000109745 00000 n 
+0000109790 00000 n 
+0000109835 00000 n 
+0000109880 00000 n 
+0000109925 00000 n 
+0000109970 00000 n 
+0000110015 00000 n 
+0000110060 00000 n 
+0000110105 00000 n 
+0000110150 00000 n 
+0000110195 00000 n 
+0000110240 00000 n 
+0000110285 00000 n 
+0000110330 00000 n 
+0000110375 00000 n 
+0000110420 00000 n 
+0000110465 00000 n 
+0000110510 00000 n 
+0000110555 00000 n 
+0000110600 00000 n 
+0000110645 00000 n 
+0000110690 00000 n 
+0000110735 00000 n 
+0000110780 00000 n 
+0000110825 00000 n 
+0000110870 00000 n 
+0000110915 00000 n 
+0000110960 00000 n 
+0000111005 00000 n 
+0000111050 00000 n 
+0000111095 00000 n 
+0000111140 00000 n 
+0000111185 00000 n 
+0000111230 00000 n 
+0000111275 00000 n 
+0000111320 00000 n 
+0000111365 00000 n 
+0000111410 00000 n 
+0000111455 00000 n 
+0000111500 00000 n 
+0000111545 00000 n 
+0000111590 00000 n 
+0000111635 00000 n 
+0000111680 00000 n 
+0000111725 00000 n 
+0000111770 00000 n 
+0000111815 00000 n 
+0000111860 00000 n 
+0000111905 00000 n 
+0000111950 00000 n 
+0000111995 00000 n 
+0000112040 00000 n 
+0000112085 00000 n 
+0000112130 00000 n 
+0000112175 00000 n 
+0000112220 00000 n 
+0000112265 00000 n 
+0000112310 00000 n 
+0000112355 00000 n 
+0000112400 00000 n 
+0000112445 00000 n 
+0000112490 00000 n 
+0000112535 00000 n 
+0000112580 00000 n 
+0000112625 00000 n 
+0000112670 00000 n 
+0000112715 00000 n 
+0000112760 00000 n 
+0000112805 00000 n 
+0000112850 00000 n 
+0000112895 00000 n 
+0000112940 00000 n 
+0000112985 00000 n 
+0000113030 00000 n 
+0000113075 00000 n 
+0000113120 00000 n 
+0000113165 00000 n 
+0000113210 00000 n 
+0000113255 00000 n 
+0000113300 00000 n 
+0000113345 00000 n 
+0000113390 00000 n 
+0000113435 00000 n 
+0000113480 00000 n 
+0000113525 00000 n 
+0000113570 00000 n 
+0000113615 00000 n 
+0000113660 00000 n 
+0000113705 00000 n 
+0000113750 00000 n 
+0000113795 00000 n 
+0000113840 00000 n 
+0000113885 00000 n 
+0000113930 00000 n 
+0000113975 00000 n 
+0000114020 00000 n 
+0000114065 00000 n 
+0000114110 00000 n 
+0000114155 00000 n 
+0000114200 00000 n 
+0000114245 00000 n 
+0000114290 00000 n 
+0000114335 00000 n 
+0000114380 00000 n 
+0000114425 00000 n 
+0000114470 00000 n 
+0000114515 00000 n 
+0000114560 00000 n 
+0000114605 00000 n 
+0000114650 00000 n 
+0000114695 00000 n 
+0000114740 00000 n 
+0000114785 00000 n 
+0000114830 00000 n 
+0000114875 00000 n 
+0000114920 00000 n 
+0000114965 00000 n 
+0000115010 00000 n 
+0000115055 00000 n 
+0000115100 00000 n 
+0000115145 00000 n 
+0000115190 00000 n 
+0000115235 00000 n 
+0000115280 00000 n 
+0000115325 00000 n 
+0000115370 00000 n 
+0000115415 00000 n 
+0000115460 00000 n 
+0000115505 00000 n 
+0000115550 00000 n 
+0000115595 00000 n 
+0000115640 00000 n 
+0000115685 00000 n 
+0000115730 00000 n 
+0000115775 00000 n 
+0000115820 00000 n 
+0000115865 00000 n 
+0000115910 00000 n 
+0000115955 00000 n 
+0000116000 00000 n 
+0000116045 00000 n 
+0000116090 00000 n 
+0000116135 00000 n 
+0000116180 00000 n 
+0000116225 00000 n 
+0000116270 00000 n 
+0000116315 00000 n 
+0000116360 00000 n 
+0000116405 00000 n 
+0000116450 00000 n 
+0000116495 00000 n 
+0000116540 00000 n 
+0000116585 00000 n 
+0000116630 00000 n 
+0000116675 00000 n 
+0000116720 00000 n 
+0000116765 00000 n 
+0000116810 00000 n 
+0000116855 00000 n 
+0000116900 00000 n 
+0000116945 00000 n 
+0000116990 00000 n 
+0000117035 00000 n 
+0000117080 00000 n 
+0000117125 00000 n 
+0000117170 00000 n 
+0000117215 00000 n 
+0000117260 00000 n 
+0000117305 00000 n 
+0000117350 00000 n 
+0000117395 00000 n 
+0000117440 00000 n 
+0000117485 00000 n 
+0000117530 00000 n 
+0000117575 00000 n 
+0000117620 00000 n 
+0000117665 00000 n 
+0000117710 00000 n 
+0000117755 00000 n 
+0000117800 00000 n 
+0000117845 00000 n 
+0000117890 00000 n 
+0000117935 00000 n 
+0000117980 00000 n 
+0000118025 00000 n 
+0000118070 00000 n 
+0000118115 00000 n 
+0000118160 00000 n 
+0000118205 00000 n 
+0000118250 00000 n 
+0000118295 00000 n 
+0000118340 00000 n 
+0000118385 00000 n 
+0000118429 00000 n 
+0000118474 00000 n 
+0000118519 00000 n 
+0000118564 00000 n 
+0000118609 00000 n 
+0000118654 00000 n 
+0000118699 00000 n 
+0000118744 00000 n 
+0000118789 00000 n 
+0000118834 00000 n 
+0000118879 00000 n 
+0000118924 00000 n 
+0000118969 00000 n 
+0000119014 00000 n 
+0000119059 00000 n 
+0000119104 00000 n 
+0000119149 00000 n 
+0000119194 00000 n 
+0000119239 00000 n 
+0000119284 00000 n 
+0000119329 00000 n 
+0000119374 00000 n 
+0000119419 00000 n 
+0000121259 00000 n 
+0000121420 00000 n 
+0000121589 00000 n 
+0000121782 00000 n 
+0000125683 00000 n 
+0000125877 00000 n 
+0000129684 00000 n 
+0000129878 00000 n 
+0000135036 00000 n 
+0000135230 00000 n 
+0000139393 00000 n 
+0000139587 00000 n 
+0000143499 00000 n 
+0000143693 00000 n 
+0000147516 00000 n 
+0000147710 00000 n 
+0000151497 00000 n 
+0000151691 00000 n 
+0000155674 00000 n 
+0000155868 00000 n 
+0000157463 00000 n 
+0000157675 00000 n 
+0000159650 00000 n 
+0000159834 00000 n 
+0000163045 00000 n 
+0000163229 00000 n 
+0000166130 00000 n 
+0000166305 00000 n 
+0000169056 00000 n 
+0000169231 00000 n 
+0000170935 00000 n 
+0000171096 00000 n 
+0000171284 00000 n 
+0000171454 00000 n 
+0000171766 00000 n 
+0000171955 00000 n 
+0000174141 00000 n 
+0000174321 00000 n 
+0000176495 00000 n 
+0000176684 00000 n 
+0000178855 00000 n 
+0000179034 00000 n 
+0000180227 00000 n 
+0000180439 00000 n 
+0000181949 00000 n 
+0000182166 00000 n 
+0000183599 00000 n 
+0000183802 00000 n 
+0000185726 00000 n 
+0000185946 00000 n 
+0000187772 00000 n 
+0000187970 00000 n 
+0000189898 00000 n 
+0000190105 00000 n 
+0000192023 00000 n 
+0000192232 00000 n 
+0000194544 00000 n 
+0000194732 00000 n 
+0000195923 00000 n 
+0000196152 00000 n 
+0000198021 00000 n 
+0000198250 00000 n 
+0000199817 00000 n 
+0000200014 00000 n 
+0000201509 00000 n 
+0000201722 00000 n 
+0000203907 00000 n 
+0000204110 00000 n 
+0000205859 00000 n 
+0000206073 00000 n 
+0000207485 00000 n 
+0000207707 00000 n 
+0000209406 00000 n 
+0000209610 00000 n 
+0000211358 00000 n 
+0000211556 00000 n 
+0000212782 00000 n 
+0000213021 00000 n 
+0000214640 00000 n 
+0000214837 00000 n 
+0000216010 00000 n 
+0000216171 00000 n 
+0000216361 00000 n 
+0000216531 00000 n 
+0000216829 00000 n 
+0000217018 00000 n 
+0000218704 00000 n 
+0000218892 00000 n 
+0000220323 00000 n 
+0000220520 00000 n 
+0000222281 00000 n 
+0000222461 00000 n 
+0000224425 00000 n 
+0000224638 00000 n 
+0000226435 00000 n 
+0000226657 00000 n 
+0000227714 00000 n 
+0000227944 00000 n 
+0000229337 00000 n 
+0000229551 00000 n 
+0000231074 00000 n 
+0000231287 00000 n 
+0000233291 00000 n 
+0000233565 00000 n 
+0000235350 00000 n 
+0000235563 00000 n 
+0000237174 00000 n 
+0000237372 00000 n 
+0000239039 00000 n 
+0000239218 00000 n 
+0000241250 00000 n 
+0000241480 00000 n 
+0000243300 00000 n 
+0000243494 00000 n 
+0000245049 00000 n 
+0000245229 00000 n 
+0000246969 00000 n 
+0000247158 00000 n 
+0000248359 00000 n 
+0000248624 00000 n 
+0000250091 00000 n 
+0000250289 00000 n 
+0000251269 00000 n 
+0000251501 00000 n 
+0000252904 00000 n 
+0000253139 00000 n 
+0000255056 00000 n 
+0000255217 00000 n 
+0000255410 00000 n 
+0000255580 00000 n 
+0000255880 00000 n 
+0000256119 00000 n 
+0000257874 00000 n 
+0000258081 00000 n 
+0000259925 00000 n 
+0000260123 00000 n 
+0000261768 00000 n 
+0000261980 00000 n 
+0000263396 00000 n 
+0000263575 00000 n 
+0000264392 00000 n 
+0000264589 00000 n 
+0000266084 00000 n 
+0000266348 00000 n 
+0000268071 00000 n 
+0000268317 00000 n 
+0000270245 00000 n 
+0000270477 00000 n 
+0000272487 00000 n 
+0000272719 00000 n 
+0000274371 00000 n 
+0000274575 00000 n 
+0000275920 00000 n 
+0000276142 00000 n 
+0000277705 00000 n 
+0000277884 00000 n 
+0000279453 00000 n 
+0000279632 00000 n 
+0000281152 00000 n 
+0000281331 00000 n 
+0000282834 00000 n 
+0000283013 00000 n 
+0000284679 00000 n 
+0000284849 00000 n 
+0000285594 00000 n 
+0000285816 00000 n 
+0000287734 00000 n 
+0000287975 00000 n 
+0000289704 00000 n 
+0000289916 00000 n 
+0000291975 00000 n 
+0000292173 00000 n 
+0000294227 00000 n 
+0000294434 00000 n 
+0000296252 00000 n 
+0000296465 00000 n 
+0000298568 00000 n 
+0000298775 00000 n 
+0000300524 00000 n 
+0000300711 00000 n 
+0000302390 00000 n 
+0000302579 00000 n 
+0000303471 00000 n 
+0000303641 00000 n 
+0000304739 00000 n 
+0000304909 00000 n 
+0000305600 00000 n 
+0000305770 00000 n 
+0000306631 00000 n 
+0000306801 00000 n 
+0000307902 00000 n 
+0000308125 00000 n 
+0000309507 00000 n 
+0000309723 00000 n 
+0000311503 00000 n 
+0000311738 00000 n 
+0000313722 00000 n 
+0000313901 00000 n 
+0000315704 00000 n 
+0000315873 00000 n 
+0000317384 00000 n 
+0000317642 00000 n 
+0000319991 00000 n 
+0000320212 00000 n 
+0000322355 00000 n 
+0000322575 00000 n 
+0000324444 00000 n 
+0000324663 00000 n 
+0000326321 00000 n 
+0000326510 00000 n 
+0000328202 00000 n 
+0000328381 00000 n 
+0000330126 00000 n 
+0000330314 00000 n 
+0000332148 00000 n 
+0000332342 00000 n 
+0000334257 00000 n 
+0000334488 00000 n 
+0000336593 00000 n 
+0000336805 00000 n 
+0000338241 00000 n 
+0000338454 00000 n 
+0000339903 00000 n 
+0000340110 00000 n 
+0000341347 00000 n 
+0000341526 00000 n 
+0000342513 00000 n 
+0000342701 00000 n 
+0000343833 00000 n 
+0000344021 00000 n 
+0000345522 00000 n 
+0000345710 00000 n 
+0000346792 00000 n 
+0000346981 00000 n 
+0000348314 00000 n 
+0000348520 00000 n 
+0000350170 00000 n 
+0000350424 00000 n 
+0000352205 00000 n 
+0000352374 00000 n 
+0000353770 00000 n 
+0000353939 00000 n 
+0000354707 00000 n 
+0000354910 00000 n 
+0000356865 00000 n 
+0000357062 00000 n 
+0000359262 00000 n 
+0000359482 00000 n 
+0000361458 00000 n 
+0000361646 00000 n 
+0000363383 00000 n 
+0000363562 00000 n 
+0000364887 00000 n 
+0000365127 00000 n 
+0000366643 00000 n 
+0000366840 00000 n 
+0000368665 00000 n 
+0000368853 00000 n 
+0000370852 00000 n 
+0000371095 00000 n 
+0000372920 00000 n 
+0000373109 00000 n 
+0000374742 00000 n 
+0000374963 00000 n 
+0000376662 00000 n 
+0000376884 00000 n 
+0000378540 00000 n 
+0000378719 00000 n 
+0000380608 00000 n 
+0000380786 00000 n 
+0000382127 00000 n 
+0000382359 00000 n 
+0000384185 00000 n 
+0000384363 00000 n 
+0000385772 00000 n 
+0000385932 00000 n 
+0000386222 00000 n 
+0000386401 00000 n 
+0000388180 00000 n 
+0000388378 00000 n 
+0000390106 00000 n 
+0000390326 00000 n 
+0000391934 00000 n 
+0000392163 00000 n 
+0000393722 00000 n 
+0000393932 00000 n 
+0000395624 00000 n 
+0000395827 00000 n 
+0000396948 00000 n 
+0000397145 00000 n 
+0000398422 00000 n 
+0000398625 00000 n 
+0000399738 00000 n 
+0000399923 00000 n 
+0000400775 00000 n 
+0000400988 00000 n 
+0000402475 00000 n 
+0000402655 00000 n 
+0000403419 00000 n 
+0000403660 00000 n 
+0000405267 00000 n 
+0000405465 00000 n 
+0000407315 00000 n 
+0000407512 00000 n 
+0000409135 00000 n 
+0000409314 00000 n 
+0000411367 00000 n 
+0000411546 00000 n 
+0000413384 00000 n 
+0000413563 00000 n 
+0000415273 00000 n 
+0000415452 00000 n 
+0000415883 00000 n 
+0000416103 00000 n 
+0000417840 00000 n 
+0000418037 00000 n 
+0000419891 00000 n 
+0000420060 00000 n 
+0000421757 00000 n 
+0000421926 00000 n 
+0000423135 00000 n 
+0000423323 00000 n 
+0000425021 00000 n 
+0000425209 00000 n 
+0000426665 00000 n 
+0000426878 00000 n 
+0000428480 00000 n 
+0000428668 00000 n 
+0000430329 00000 n 
+0000430517 00000 n 
+0000431346 00000 n 
+0000431534 00000 n 
+0000433105 00000 n 
+0000433299 00000 n 
+0000434565 00000 n 
+0000434777 00000 n 
+0000436371 00000 n 
+0000436593 00000 n 
+0000437510 00000 n 
+0000437671 00000 n 
+0000437871 00000 n 
+0000438065 00000 n 
+0000439648 00000 n 
+0000439861 00000 n 
+0000441389 00000 n 
+0000441577 00000 n 
+0000442839 00000 n 
+0000443027 00000 n 
+0000444296 00000 n 
+0000444549 00000 n 
+0000445886 00000 n 
+0000446084 00000 n 
+0000447614 00000 n 
+0000447793 00000 n 
+0000448726 00000 n 
+0000448905 00000 n 
+0000450433 00000 n 
+0000450621 00000 n 
+0000451590 00000 n 
+0000451769 00000 n 
+0000452602 00000 n 
+0000452797 00000 n 
+0000454528 00000 n 
+0000454741 00000 n 
+0000456424 00000 n 
+0000456618 00000 n 
+0000458325 00000 n 
+0000458560 00000 n 
+0000460245 00000 n 
+0000460415 00000 n 
+0000460942 00000 n 
+0000461112 00000 n 
+0000462619 00000 n 
+0000462789 00000 n 
+0000464188 00000 n 
+0000464358 00000 n 
+0000465908 00000 n 
+0000466077 00000 n 
+0000467041 00000 n 
+0000467291 00000 n 
+0000468760 00000 n 
+0000468947 00000 n 
+0000470891 00000 n 
+0000471120 00000 n 
+0000472980 00000 n 
+0000473187 00000 n 
+0000475319 00000 n 
+0000475522 00000 n 
+0000476277 00000 n 
+0000476481 00000 n 
+0000478283 00000 n 
+0000478505 00000 n 
+0000480369 00000 n 
+0000480591 00000 n 
+0000482145 00000 n 
+0000482358 00000 n 
+0000484104 00000 n 
+0000484321 00000 n 
+0000486105 00000 n 
+0000486164 00000 n 
+0000486267 00000 n 
+0000486432 00000 n 
+0000486528 00000 n 
+0000486646 00000 n 
+0000486762 00000 n 
+0000486871 00000 n 
+0000486994 00000 n 
+0000487106 00000 n 
+0000487276 00000 n 
+0000487377 00000 n 
+0000487493 00000 n 
+0000487614 00000 n 
+0000487734 00000 n 
+0000487859 00000 n 
+0000487972 00000 n 
+0000488076 00000 n 
+0000488254 00000 n 
+0000488375 00000 n 
+0000488535 00000 n 
+0000488653 00000 n 
+0000488750 00000 n 
+0000488902 00000 n 
+0000489042 00000 n 
+0000489220 00000 n 
+0000489375 00000 n 
+0000489477 00000 n 
+0000489577 00000 n 
+0000489786 00000 n 
+0000489887 00000 n 
+0000490075 00000 n 
+0000490216 00000 n 
+0000490360 00000 n 
+0000490514 00000 n 
+0000490623 00000 n 
+0000490735 00000 n 
+0000490902 00000 n 
+0000491014 00000 n 
+0000491188 00000 n 
+0000491291 00000 n 
+0000491464 00000 n 
+0000491585 00000 n 
+0000491715 00000 n 
+0000491841 00000 n 
+0000491956 00000 n 
+0000492064 00000 n 
+0000492211 00000 n 
+0000492316 00000 n 
+0000492435 00000 n 
+0000492564 00000 n 
+0000492723 00000 n 
+0000492857 00000 n 
+0000492994 00000 n 
+0000493126 00000 n 
+0000493275 00000 n 
+0000493407 00000 n 
+0000493555 00000 n 
+0000493669 00000 n 
+0000493787 00000 n 
+0000493941 00000 n 
+0000494072 00000 n 
+0000494166 00000 n 
+0000494290 00000 n 
+0000494402 00000 n 
+0000494579 00000 n 
+0000494688 00000 n 
+0000494813 00000 n 
+0000494959 00000 n 
+0000495061 00000 n 
+0000495237 00000 n 
+0000495381 00000 n 
+0000495493 00000 n 
+0000495620 00000 n 
+0000495748 00000 n 
+0000495876 00000 n 
+0000495987 00000 n 
+0000496186 00000 n 
+0000496297 00000 n 
+0000496412 00000 n 
+0000496556 00000 n 
+0000496764 00000 n 
+0000496898 00000 n 
+0000497052 00000 n 
+0000497177 00000 n 
+0000497346 00000 n 
+0000497479 00000 n 
+0000497767 00000 n 
+0000497920 00000 n 
+0000498114 00000 n 
+0000498325 00000 n 
+0000498486 00000 n 
+0000498607 00000 n 
+0000498810 00000 n 
+0000498921 00000 n 
+0000499036 00000 n 
+0000499229 00000 n 
+0000499372 00000 n 
+0000499488 00000 n 
+0000499646 00000 n 
+0000499803 00000 n 
+0000499934 00000 n 
+0000500055 00000 n 
+0000500232 00000 n 
+0000500342 00000 n 
+0000500472 00000 n 
+0000500642 00000 n 
+0000500736 00000 n 
+0000500863 00000 n 
+0000500990 00000 n 
+0000501086 00000 n 
+0000501273 00000 n 
+0000501400 00000 n 
+0000501534 00000 n 
+0000501661 00000 n 
+0000501773 00000 n 
+0000501979 00000 n 
+0000502138 00000 n 
+0000502286 00000 n 
+0000502414 00000 n 
+0000502595 00000 n 
+0000502705 00000 n 
+0000502820 00000 n 
+0000502965 00000 n 
+0000503129 00000 n 
+0000503279 00000 n 
+0000503416 00000 n 
+0000503582 00000 n 
+0000503686 00000 n 
+0000503843 00000 n 
+0000503954 00000 n 
+0000504099 00000 n 
+0000504241 00000 n 
+0000504391 00000 n 
+0000504508 00000 n 
+0000504672 00000 n 
+0000504783 00000 n 
+0000504923 00000 n 
+0000505050 00000 n 
+0000505167 00000 n 
+0000505306 00000 n 
+0000505412 00000 n 
+0000505546 00000 n 
+0000505678 00000 n 
+0000505823 00000 n 
+0000505950 00000 n 
+0000506082 00000 n 
+0000506212 00000 n 
+0000506337 00000 n 
+0000506445 00000 n 
+0000506617 00000 n 
+0000506721 00000 n 
+0000506856 00000 n 
+0000506991 00000 n 
+0000507225 00000 n 
+0000507379 00000 n 
+0000507520 00000 n 
+0000507694 00000 n 
+0000507784 00000 n 
+0000507912 00000 n 
+0000508086 00000 n 
+0000508188 00000 n 
+0000508339 00000 n 
+0000508490 00000 n 
+0000508616 00000 n 
+0000508822 00000 n 
+0000508922 00000 n 
+0000509040 00000 n 
+0000509205 00000 n 
+0000509296 00000 n 
+0000509457 00000 n 
+0000509583 00000 n 
+0000509726 00000 n 
+0000509853 00000 n 
+0000509993 00000 n 
+0000510129 00000 n 
+0000510237 00000 n 
+0000510411 00000 n 
+0000510517 00000 n 
+0000510637 00000 n 
+0000510749 00000 n 
 0000510866 00000 n 
-0000511002 00000 n 
-0000511176 00000 n 
-0000511291 00000 n 
-0000511401 00000 n 
-0000511537 00000 n 
-0000511713 00000 n 
-0000511859 00000 n 
-0000511993 00000 n 
-0000512149 00000 n 
-0000512317 00000 n 
-0000512466 00000 n 
-0000512590 00000 n 
-0000512728 00000 n 
-0000512891 00000 n 
-0000513001 00000 n 
-0000513135 00000 n 
-0000513247 00000 n 
-0000513428 00000 n 
-0000513549 00000 n 
-0000513735 00000 n 
-0000513892 00000 n 
-0000514055 00000 n 
-0000514225 00000 n 
-0000514349 00000 n 
-0000514472 00000 n 
-0000514676 00000 n 
-0000514781 00000 n 
-0000514913 00000 n 
-0000515034 00000 n 
-0000515205 00000 n 
-0000515327 00000 n 
-0000515487 00000 n 
-0000515586 00000 n 
-0000515704 00000 n 
-0000515819 00000 n 
-0000515921 00000 n 
-0000516082 00000 n 
-0000516186 00000 n 
-0000516285 00000 n 
-0000516492 00000 n 
-0000516620 00000 n 
-0000516705 00000 n 
-0000516897 00000 n 
-0000517069 00000 n 
-0000517173 00000 n 
-0000517297 00000 n 
-0000517419 00000 n 
-0000517531 00000 n 
-0000517713 00000 n 
-0000517829 00000 n 
-0000517953 00000 n 
-0000518071 00000 n 
-0000518189 00000 n 
-0000518294 00000 n 
-0000518471 00000 n 
-0000518583 00000 n 
-0000518714 00000 n 
-0000518838 00000 n 
-0000519005 00000 n 
-0000519122 00000 n 
-0000519252 00000 n 
-0000519392 00000 n 
-0000519529 00000 n 
-0000519665 00000 n 
-0000519801 00000 n 
-0000519938 00000 n 
-0000520050 00000 n 
-0000520214 00000 n 
-0000520318 00000 n 
-0000520451 00000 n 
-0000520583 00000 n 
-0000520705 00000 n 
-0000520834 00000 n 
-0000520941 00000 n 
-0000521107 00000 n 
-0000521229 00000 n 
-0000521353 00000 n 
-0000521470 00000 n 
-0000521584 00000 n 
-0000521754 00000 n 
-0000521916 00000 n 
-0000522022 00000 n 
-0000522139 00000 n 
-0000522290 00000 n 
-0000522427 00000 n 
-0000522592 00000 n 
-0000522717 00000 n 
-0000522873 00000 n 
-0000522991 00000 n 
-0000523121 00000 n 
-0000523308 00000 n 
-0000523466 00000 n 
-0000523570 00000 n 
-0000523690 00000 n 
-0000523813 00000 n 
-0000523974 00000 n 
-0000524070 00000 n 
-0000524184 00000 n 
-0000524294 00000 n 
-0000524425 00000 n 
-0000524572 00000 n 
-0000524673 00000 n 
-0000524772 00000 n 
-0000524950 00000 n 
-0000525060 00000 n 
-0000525214 00000 n 
-0000525383 00000 n 
-0000525571 00000 n 
-0000525752 00000 n 
-0000525908 00000 n 
-0000526074 00000 n 
-0000526206 00000 n 
-0000526353 00000 n 
-0000526492 00000 n 
-0000526626 00000 n 
-0000526750 00000 n 
-0000526871 00000 n 
-0000527004 00000 n 
-0000527110 00000 n 
-0000527302 00000 n 
-0000527444 00000 n 
-0000527556 00000 n 
-0000527679 00000 n 
-0000527802 00000 n 
-0000527924 00000 n 
-0000528049 00000 n 
-0000528172 00000 n 
-0000528290 00000 n 
-0000528465 00000 n 
-0000528568 00000 n 
-0000528688 00000 n 
-0000528803 00000 n 
-0000528917 00000 n 
-0000529032 00000 n 
-0000529146 00000 n 
-0000529261 00000 n 
-0000529379 00000 n 
-0000529496 00000 n 
-0000529602 00000 n 
-0000529771 00000 n 
-0000529875 00000 n 
-0000529992 00000 n 
-0000530107 00000 n 
-0000530221 00000 n 
-0000530407 00000 n 
-0000530516 00000 n 
-0000530691 00000 n 
-0000530809 00000 n 
-0000530950 00000 n 
-0000531073 00000 n 
-0000531223 00000 n 
-0000531327 00000 n 
-0000531445 00000 n 
-0000531563 00000 n 
-0000531684 00000 n 
-0000531820 00000 n 
-0000531919 00000 n 
+0000510968 00000 n 
+0000511146 00000 n 
+0000511315 00000 n 
+0000511423 00000 n 
+0000511557 00000 n 
+0000511675 00000 n 
+0000511852 00000 n 
+0000512019 00000 n 
+0000512135 00000 n 
+0000512273 00000 n 
+0000512409 00000 n 
+0000512583 00000 n 
+0000512698 00000 n 
+0000512808 00000 n 
+0000512944 00000 n 
+0000513120 00000 n 
+0000513266 00000 n 
+0000513400 00000 n 
+0000513556 00000 n 
+0000513724 00000 n 
+0000513873 00000 n 
+0000513997 00000 n 
+0000514135 00000 n 
+0000514298 00000 n 
+0000514408 00000 n 
+0000514542 00000 n 
+0000514654 00000 n 
+0000514835 00000 n 
+0000514956 00000 n 
+0000515142 00000 n 
+0000515299 00000 n 
+0000515462 00000 n 
+0000515632 00000 n 
+0000515756 00000 n 
+0000515879 00000 n 
+0000516083 00000 n 
+0000516188 00000 n 
+0000516320 00000 n 
+0000516441 00000 n 
+0000516612 00000 n 
+0000516734 00000 n 
+0000516894 00000 n 
+0000516993 00000 n 
+0000517111 00000 n 
+0000517226 00000 n 
+0000517328 00000 n 
+0000517489 00000 n 
+0000517593 00000 n 
+0000517692 00000 n 
+0000517899 00000 n 
+0000518027 00000 n 
+0000518112 00000 n 
+0000518304 00000 n 
+0000518476 00000 n 
+0000518580 00000 n 
+0000518704 00000 n 
+0000518826 00000 n 
+0000518938 00000 n 
+0000519120 00000 n 
+0000519236 00000 n 
+0000519360 00000 n 
+0000519478 00000 n 
+0000519596 00000 n 
+0000519701 00000 n 
+0000519878 00000 n 
+0000519990 00000 n 
+0000520121 00000 n 
+0000520245 00000 n 
+0000520412 00000 n 
+0000520529 00000 n 
+0000520659 00000 n 
+0000520799 00000 n 
+0000520936 00000 n 
+0000521072 00000 n 
+0000521208 00000 n 
+0000521345 00000 n 
+0000521457 00000 n 
+0000521621 00000 n 
+0000521725 00000 n 
+0000521858 00000 n 
+0000521990 00000 n 
+0000522112 00000 n 
+0000522241 00000 n 
+0000522348 00000 n 
+0000522514 00000 n 
+0000522636 00000 n 
+0000522760 00000 n 
+0000522891 00000 n 
+0000523000 00000 n 
+0000523114 00000 n 
+0000523284 00000 n 
+0000523446 00000 n 
+0000523552 00000 n 
+0000523669 00000 n 
+0000523820 00000 n 
+0000523957 00000 n 
+0000524122 00000 n 
+0000524247 00000 n 
+0000524403 00000 n 
+0000524521 00000 n 
+0000524651 00000 n 
+0000524838 00000 n 
+0000524996 00000 n 
+0000525100 00000 n 
+0000525220 00000 n 
+0000525343 00000 n 
+0000525504 00000 n 
+0000525600 00000 n 
+0000525714 00000 n 
+0000525824 00000 n 
+0000525955 00000 n 
+0000526102 00000 n 
+0000526203 00000 n 
+0000526302 00000 n 
+0000526480 00000 n 
+0000526590 00000 n 
+0000526744 00000 n 
+0000526913 00000 n 
+0000527101 00000 n 
+0000527282 00000 n 
+0000527438 00000 n 
+0000527604 00000 n 
+0000527736 00000 n 
+0000527883 00000 n 
+0000528022 00000 n 
+0000528156 00000 n 
+0000528280 00000 n 
+0000528401 00000 n 
+0000528534 00000 n 
+0000528640 00000 n 
+0000528832 00000 n 
+0000528974 00000 n 
+0000529086 00000 n 
+0000529209 00000 n 
+0000529332 00000 n 
+0000529454 00000 n 
+0000529579 00000 n 
+0000529702 00000 n 
+0000529820 00000 n 
+0000529995 00000 n 
+0000530098 00000 n 
+0000530218 00000 n 
+0000530333 00000 n 
+0000530447 00000 n 
+0000530562 00000 n 
+0000530676 00000 n 
+0000530791 00000 n 
+0000530909 00000 n 
+0000531026 00000 n 
+0000531132 00000 n 
+0000531301 00000 n 
+0000531405 00000 n 
+0000531522 00000 n 
+0000531637 00000 n 
+0000531751 00000 n 
+0000531937 00000 n 
+0000532046 00000 n 
+0000532221 00000 n 
+0000532339 00000 n 
+0000532480 00000 n 
+0000532603 00000 n 
+0000532753 00000 n 
+0000532857 00000 n 
+0000532975 00000 n 
+0000533093 00000 n 
+0000533214 00000 n 
+0000533350 00000 n 
+0000533449 00000 n 
 trailer
-<<715f41d6c6f228bafa2b807ede00788a>]>>
+<<5f751223613f7429fc6149872788f647>]>>
 startxref
-533010
+534540
 %%EOF
diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html
index 5dd720ddb2..7147458209 100644
--- a/docs/htmldocs/Samba-HOWTO-Collection.html
+++ b/docs/htmldocs/Samba-HOWTO-Collection.html
@@ -176,34 +176,34 @@ HREF="#INSTALL"
 >
    2.1. Obtaining and installing samba
    2.2. Configuring samba
    2.3. Try listing the shares available on your 
 	server
    2.4. Try connecting with the unix client
    2.5. Try connecting from a DOS, WfWg, Win9x, WinNT, 
 	Win2k, OS/2, etc... client
    2.6. What If Things Don't Work?
    3.1. Discussion
    3.2. How browsing functions and how to deploy stable and 
 dependable browsing using Samba
    3.3. Use of the Remote Announce
    3.4. Use of the Remote Browse Sync
    3.5. Use of WINS
    3.6. Do NOT use more than one (1) protocol on MS Windows machines
    3.7. Name Resolution Order
    4.1. Introduction
    4.2. Important Notes About Security
    4.3. The smbpasswd Command
    4.4. Plain text
    4.5. TDB
    4.6. LDAP
    4.7. MySQL
    4.8. XML
    5.1. Stand Alone Server
    5.2. Domain Member Server
    5.3. Domain Controller
    6.1. User and Share security level
    7.1. Prerequisite Reading
    7.2. Background
    7.3. Configuring the Samba Domain Controller
    7.4. Creating Machine Trust Accounts and Joining Clients to the Domain
    7.5. Common Problems and Errors
    7.6. Domain Control for Windows 9x/ME
    8.1. Prerequisite Reading
    8.2. Background
    8.3. What qualifies a Domain Controller on the network?
    8.4. Can Samba be a Backup Domain Controller to an NT PDC?
    8.5. How do I set up a Samba BDC?
    9.1. Setup your smb.conf
    9.2. Setup your /etc/krb5.conf
    9.6. Notes
    10.1. Joining an NT Domain with Samba 3.0
    10.2. Why is this better than security = server?
    11.1. Viewing and changing UNIX permissions using the NT 
 	security dialogs
    11.2. How to view file security on a Samba share
    11.3. Viewing file ownership
    11.4. Viewing file or directory permissions
    11.5. Modifying file or directory permissions
    11.6. Interaction with the standard Samba create mask 
 	parameters
    11.7. Interaction with the standard Samba file attribute 
 	mapping
    13.1. Introduction
    13.2. Configuration
    13.3. The Imprints Toolset
    13.4. Diagnosis
    14.1. Introduction
    14.2. Configuring smb.conf
    14.3. CUPS - RAW Print Through Mode
    14.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe
 PostScript driver with CUPS-PPDs downloaded to clients
    14.5. Windows Terminal Servers (WTS) as CUPS clients
    14.6. Setting up CUPS for driver download
    14.7. Sources of CUPS drivers / PPDs
    14.8. The CUPS Filter Chains
    14.9. CUPS Print Drivers and Devices
    14.10. Limiting the number of pages users can print
    14.11. Advanced Postscript Printing from MS Windows
    14.12. Auto-Deletion of CUPS spool files
    15.1. Abstract
    15.2. Introduction
    15.3. What Winbind Provides
    15.4. How Winbind Works
    15.5. Installation and Configuration
    15.6. Limitations
    15.7. Conclusion
    16.1. Configuring Samba Share Access Controls
    16.2. Remote Server Administration
    16.3. Network Logon Script Magic
    17.1. Creating and Managing System Policies
    17.2. Managing Account/User Policies
    17.3. System Startup and Logon Processing Overview
    18.1. Roaming Profiles
    18.2. Mandatory profiles
    18.3. Creating/Managing Group Profiles
    18.4. Default Profile for Windows Users
    19.1. Trust Relationship Background
    19.2. Native MS Windows NT4 Trusts Configuration
    19.3. Configuring Samba NT-style Domain Trusts
    20.1. Samba and PAM
    20.2. Distributed Authentication
    20.3. PAM Configuration in smb.conf
    21.1. Introduction and configuration
    21.2. Included modules
    21.3. VFS modules available elsewhere
    22.1. Instructions
    23.1. Name Resolution in a pure Unix/Linux world
    23.2. Name resolution as used within MS Windows networking
    24.1. Overview of browsing
    24.2. Browsing support in samba
    24.3. Problem resolution
    24.4. Browsing across subnets
    24.5. Setting up a WINS server
    24.6. Setting up Browsing in a WORKGROUP
    24.7. Setting up Browsing in a DOMAIN
    24.9. Making samba the domain master
    24.10. Note about broadcast addresses
    24.11. Multiple interfaces
    25.1. Introduction
    25.2. Using host based protection
    25.3. Using interface protection
    25.4. Using a firewall
    25.5. Using a IPC$ share deny
    25.6. Upgrading Samba
    26.1. What are charsets and unicode?
    26.2. Samba and charsets
    26.3. Conversion from old names
    26.4. Japanese charsets
    27.1. Access Samba source code via CVS
    27.2. Accessing the samba sources via rsync and ftp
    27.3. Verifying Samba's PGP signature
    27.4. Building the Binaries
    27.5. Starting the smbd and nmbd
    28.1. Planning and Getting Started
    28.2. Managing Samba-3 Domain Control
    29.1. HPUX
    29.2. SCO Unix
    29.3. DNIX
    29.4. RedHat Linux Rembrandt-II
    29.5. AIX
    29.6. Solaris
    30.1. Macintosh clients?
    30.2. OS2 Client
    30.3. Windows for Workgroups
    30.4. Windows '95/'98
    30.5. Windows 2000 Service Pack 2
    30.6. Windows NT 3.1
    31.1. SWAT Features and Benefits
    32.1. Comparisons
    32.2. Socket options
    32.3. Read size
    32.4. Max xmit
    32.5. Log level
    32.6. Read raw
    32.7. Write raw
    32.8. Slow Clients
    32.9. Slow Logins
    32.10. Client tuning
    33.1. Introduction
    33.2. Assumptions
    33.3. The tests
    33.4. Still having troubles?
    34.1. Diagnostics tools
    34.2. Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
    34.3. Useful URL's
    34.4. Getting help from the mailing lists
    34.5. How to get off the mailinglists
    35.1. Introduction
    35.2. General info
    35.3. Debug levels
    35.4. Internal errors
    35.5. Attaching to a running process
    35.6. Patches
    2.1. Obtaining and installing samba
    2.2. Configuring samba
    2.2.1. Editing the smb.conf
    2.2.1.1. Test your config file with 
 	
    2.2.2. SWAT
    2.3. Try listing the shares available on your 
 	server
    2.4. Try connecting with the unix client
    2.5. Try connecting from a DOS, WfWg, Win9x, WinNT, 
 	Win2k, OS/2, etc... client
    2.6. What If Things Don't Work?
    2.6.1. Scope IDs
    2.6.2. Locking
    3.1. Discussion
    3.2. How browsing functions and how to deploy stable and 
 dependable browsing using Samba
    3.3. Use of the Remote Announce
    3.4. Use of the Remote Browse Sync
    3.5. Use of WINS
    3.5.1. WINS Replication
    3.5.2. Static WINS Entries
    3.6. Do NOT use more than one (1) protocol on MS Windows machines
    3.7. Name Resolution Order
    4.1. Introduction
    4.2. Important Notes About Security
    4.2.1. Advantages of SMB Encryption
    4.2.2. Advantages of non-encrypted passwords
    4.3. The smbpasswd Command
    4.4. Plain text
    4.5. TDB
    4.6. LDAP
    4.6.1. Introduction
    4.6.2. Introduction
    4.6.3. Supported LDAP Servers
    4.6.4. Schema and Relationship to the RFC 2307 posixAccount
    4.6.5. Configuring Samba with LDAP
    4.6.5.1. OpenLDAP configuration
    4.6.5.2. Configuring Samba
    4.6.6. Accounts and Groups management
    4.6.7. Security and sambaAccount
    4.6.8. LDAP specials attributes for sambaAccounts
    4.6.9. Example LDIF Entries for a sambaAccount
    4.7. MySQL
    4.7.1. Creating the database
    4.7.2. Configuring
    4.7.3. Using plaintext passwords or encrypted password
    4.7.4. Getting non-column data from the table
    4.8. XML
    Introduction
    5.1. Stand Alone Server
    5.2. Domain Member Server
    5.3. Domain Controller
    5.3.1. Domain Controller Types
    6.1. User and Share security level
    6.1.1. User Level Security
    6.1.2. Share Level Security
    6.1.3. Server Level Security
    6.1.3.1. Configuring Samba for Seemless Windows Network Integration
    6.1.3.2. Use MS Windows NT as an authentication server
    6.1.4. Domain Level Security
    6.1.4.1. Samba as a member of an MS Windows NT security domain
    6.1.5. ADS Level Security
    7.1. Prerequisite Reading
    7.2. Background
    7.3. Configuring the Samba Domain Controller
    7.4. Creating Machine Trust Accounts and Joining Clients to the Domain
    7.4.1. Manual Creation of Machine Trust Accounts
    7.4.2. "On-the-Fly" Creation of Machine Trust Accounts
    7.4.3. Joining the Client to the Domain
    7.5. Common Problems and Errors
    7.5.1. I cannot include a '$' in a machine name
    7.5.2. 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 trust account.
    7.5.3. The system can not log you on (C000019B)....
    7.5.4. The machine trust account for this computer either does not 
 exist or is not accessible.
    7.5.5. When I attempt to login to a Samba Domain from a NT4/W2K workstation,
 I get a message about my account being disabled.
    7.6. Domain Control for Windows 9x/ME
    7.6.1. Configuration Instructions:	Network Logons
    8.1. Prerequisite Reading
    8.2. Background
    8.3. What qualifies a Domain Controller on the network?
    8.3.1. How does a Workstation find its domain controller?
    8.3.2. When is the PDC needed?
    8.4. Can Samba be a Backup Domain Controller to an NT PDC?
    8.5. How do I set up a Samba BDC?
    8.5.1. How do I replicate the smbpasswd file?
    8.5.2. Can I do this all with LDAP?
    9.1. Setup your smb.conf
    9.2. Setup your /etc/krb5.conf
    9.3.1. Possible errors
    9.6. Notes
    10.1. Joining an NT Domain with Samba 3.0
    10.2. Why is this better than security = server?
    Introduction
    11.1. Viewing and changing UNIX permissions using the NT 
 	security dialogs
    11.2. How to view file security on a Samba share
    11.3. Viewing file ownership
    11.4. Viewing file or directory permissions
    11.4.1. File Permissions
    11.4.2. Directory Permissions
    11.5. Modifying file or directory permissions
    11.6. Interaction with the standard Samba create mask 
 	parameters
    11.7. Interaction with the standard Samba file attribute 
 	mapping
    13.1. Introduction
    13.2. Configuration
    13.2.1. Creating [print$]
    13.2.2. Setting Drivers for Existing Printers
    13.2.3. Support a large number of printers
    13.2.4. Adding New Printers via the Windows NT APW
    13.2.5. Samba and Printer Ports
    13.3. The Imprints Toolset
    13.3.1. What is Imprints?
    13.3.2. Creating Printer Driver Packages
    13.3.3. The Imprints server
    13.3.4. The Installation Client
    13.4. Diagnosis
    13.4.1. Introduction
    13.4.2. Debugging printer problems
    13.4.3. What printers do I have?
    13.4.4. Setting up printcap and print servers
    13.4.5. Job sent, no output
    13.4.6. Job sent, strange output
    13.4.7. Raw PostScript printed
    13.4.8. Advanced Printing
    13.4.9. Real debugging
    14.1. Introduction
    14.2. Configuring smb.conf
    14.3. CUPS - RAW Print Through Mode
    14.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe
 PostScript driver with CUPS-PPDs downloaded to clients
    14.5. Windows Terminal Servers (WTS) as CUPS clients
    14.6. Setting up CUPS for driver download
    14.7. Sources of CUPS drivers / PPDs
    14.7.1. cupsaddsmb
    14.8. The CUPS Filter Chains
    14.9. CUPS Print Drivers and Devices
    14.9.1. Further printing steps
    14.10. Limiting the number of pages users can print
    14.11. Advanced Postscript Printing from MS Windows
    14.12. Auto-Deletion of CUPS spool files
    15.1. Abstract
    15.2. Introduction
    15.3. What Winbind Provides
    15.3.1. Target Uses
    15.4. How Winbind Works
    15.4.1. Microsoft Remote Procedure Calls
    15.4.2. Microsoft Active Directory Services
    15.4.3. Name Service Switch
    15.4.4. Pluggable Authentication Modules
    15.4.5. User and Group ID Allocation
    15.4.6. Result Caching
    15.5. Installation and Configuration
    15.5.1. Introduction
    15.5.2. Requirements
    15.5.3. Testing Things Out
    15.5.3.1. Configure and compile SAMBA
    15.5.3.2. Configure nsswitch.conf
    15.5.3.3. Configure smb.conf
    15.5.3.4. Join the SAMBA server to the PDC domain
    15.5.3.5. Start up the winbindd daemon and test it!
    15.5.3.6. Fix the init.d startup scripts
    15.5.3.6.1. Linux
    15.5.3.6.2. Solaris
    15.5.3.6.3. Restarting
    15.5.3.7. Configure Winbind and PAM
    15.5.3.7.1. Linux/FreeBSD-specific PAM configuration
    15.5.3.7.2. Solaris-specific configuration
    15.6. Limitations
    15.7. Conclusion
    16.1. Configuring Samba Share Access Controls
    16.1.1. Share Permissions Management
    16.1.1.1. Windows NT4 Workstation/Server
    16.1.1.2. Windows 200x/XP
    16.2. Remote Server Administration
    16.3. Network Logon Script Magic
    17.1. Creating and Managing System Policies
    17.1.1. Windows 9x/Me Policies
    17.1.2. Windows NT4 Style Policy Files
    17.1.2.1. Registry Tattoos
    17.1.3. MS Windows 200x / XP Professional Policies
    17.1.3.1. Administration of Win2K / XP Policies
    17.2. Managing Account/User Policies
    17.2.1. With Windows NT4/200x
    17.2.2. With a Samba PDC
    17.3. System Startup and Logon Processing Overview
    18.1. Roaming Profiles
    18.1.1. Samba Configuration for Profile Handling
    18.1.1.1. NT4/200x User Profiles
    18.1.1.2. Windows 9x / Me User Profiles
    18.1.1.3. Mixed Windows 9x / Me and Windows NT4/200x User Profiles
    18.1.2. Windows Client Profile Configuration Information
    18.1.2.1. Windows 9x / Me Profile Setup
    18.1.2.2. Windows NT4 Workstation
    18.1.2.3. Windows 2000/XP Professional
    18.1.3. Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    18.1.4. Profile Migration from Windows NT4/200x Server to Samba
    18.1.4.1. Windows NT4 Profile Management Tools
    18.1.4.2. Side bar Notes
    18.1.4.3. moveuser.exe
    18.1.4.4. Get SID
    18.2. Mandatory profiles
    18.3. Creating/Managing Group Profiles
    18.4. Default Profile for Windows Users
    18.4.1. MS Windows 9x/Me
    18.4.1.1. How User Profiles Are Handled in Windows 9x / Me?
    18.4.2. MS Windows NT4 Workstation
    18.4.3. MS Windows 200x/XP
    19.1. Trust Relationship Background
    19.2. Native MS Windows NT4 Trusts Configuration
    19.2.1. NT4 as the Trusting Domain (ie. creating the trusted account)
    19.2.2. NT4 as the Trusted Domain (ie. creating trusted account's password)
    19.3. Configuring Samba NT-style Domain Trusts
    19.3.1. Samba-3 as the Trusting Domain
    19.3.2. Samba-3 as the Trusted Domain
    20.1. Samba and PAM
    20.2. Distributed Authentication
    20.3. PAM Configuration in smb.conf
    21.1. Introduction and configuration
    21.2. Included modules
    21.2.1. audit
    21.2.2. extd_audit
    21.2.3. recycle
    21.2.4. netatalk
    21.3. VFS modules available elsewhere
    21.3.1. DatabaseFS
    21.3.2. vscan
    22.1. Instructions
    22.1.1. Notes
    23.1. Name Resolution in a pure Unix/Linux world
    23.1.1. /etc/hosts
    23.1.2. /etc/resolv.conf
    23.1.3. /etc/host.conf
    23.1.4. /etc/nsswitch.conf
    23.2. Name resolution as used within MS Windows networking
    23.2.1. The NetBIOS Name Cache
    23.2.2. The LMHOSTS file
    23.2.3. HOSTS file
    23.2.4. DNS Lookup
    23.2.5. WINS Lookup
    24.1. Overview of browsing
    24.2. Browsing support in samba
    24.3. Problem resolution
    24.4. Browsing across subnets
    24.4.1. How does cross subnet browsing work ?
    24.5. Setting up a WINS server
    24.6. Setting up Browsing in a WORKGROUP
    24.7. Setting up Browsing in a DOMAIN
    24.9. Making samba the domain master
    24.10. Note about broadcast addresses
    24.11. Multiple interfaces
    25.1. Introduction
    25.2. Using host based protection
    25.3. Using interface protection
    25.4. Using a firewall
    25.5. Using a IPC$ share deny
    25.6. Upgrading Samba
    26.1. What are charsets and unicode?
    26.2. Samba and charsets
    26.3. Conversion from old names
    26.4. Japanese charsets
    Samba doesn't work correctly with Japanese charsets yet. Here are points of attention when setting it up:
    You should set mangling method = hash
    There are various iconv() implementations around and not all of 
+them work equally well. glibc2's iconv() has a critical problem in CP932. 
+libiconv-1.8 works with CP932 but still has some problems and does not 
+work with EUC-JP. 
    You should set dos charset = CP932, not Shift_JIS, SJIS...
    Currently only unix charset = CP932 will work (but still has some problems...) because of iconv() issues. unix charset = EUC-JP doesn't work well because of iconv() issues.
    Currently Samba 3.0 does not support unix charset = UTF8-MAC/CAP/HEX/JIS*
    More information (in Japanese) is available at: http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html.
    27.1. Access Samba source code via CVS
    27.1.1. Introduction
    27.1.2. CVS Access to samba.org
    27.1.2.1. Access via CVSweb
    27.1.2.2. Access via cvs
    27.2. Accessing the samba sources via rsync and ftp
    27.3. Verifying Samba's PGP signature
    27.4. Building the Binaries
    27.4.1. Compiling samba with Active Directory support
    27.4.1.1. Installing the required packages for Debian
    27.4.1.2. Installing the required packages for RedHat
    27.5. Starting the smbd and nmbd
    27.5.1. Starting from inetd.conf
    27.5.2. Alternative: starting it as a daemon
    28.1. Planning and Getting Started
    28.1.1. Objectives
    28.1.2. Steps In Migration Process
    28.2. Managing Samba-3 Domain Control
    29.1. HPUX
    29.2. SCO Unix
    29.3. DNIX
    29.4. RedHat Linux Rembrandt-II
    29.5. AIX
    29.5.1. Sequential Read Ahead
    29.6. Solaris
    30.1. Macintosh clients?
    30.2. OS2 Client
    30.2.1. How can I configure OS/2 Warp Connect or 
 		OS/2 Warp 4 as a client for Samba?
    30.2.2. How can I configure OS/2 Warp 3 (not Connect), 
 		OS/2 1.2, 1.3 or 2.x for Samba?
    30.2.3. Are there any other issues when OS/2 (any version) 
 		is used as a client?
    30.2.4. How do I get printer driver download working 
 		for OS/2 clients?
    30.3. Windows for Workgroups
    30.3.1. Use latest TCP/IP stack from Microsoft
    30.3.2. Delete .pwl files after password change
    30.3.3. Configure WfW password handling
    30.3.4. Case handling of passwords
    30.3.5. Use TCP/IP as default protocol
    30.4. Windows '95/'98
    30.5. Windows 2000 Service Pack 2
    30.6. Windows NT 3.1
    31.1. SWAT Features and Benefits
    31.1.1. The SWAT Home Page
    31.1.2. Global Settings
    31.1.3. The SWAT Wizard
    31.1.4. Share Settings
    31.1.5. Printing Settings
    31.1.6. The Status Page
    31.1.7. The Password Change Page
    32.1. Comparisons
    32.2. Socket options
    32.3. Read size
    32.4. Max xmit
    32.5. Log level
    32.6. Read raw
    32.7. Write raw
    32.8. Slow Clients
    32.9. Slow Logins
    32.10. Client tuning
    33.1. Introduction
    33.2. Assumptions
    33.3. The tests
    33.4. Still having troubles?
    34.1. Diagnostics tools
    34.2. Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
    34.3. Useful URL's
    34.4. Getting help from the mailing lists
    34.5. How to get off the mailinglists
    35.1. Introduction
    35.2. General info
    35.3. Debug levels
    35.4. Internal errors
    35.5. Attaching to a running process
    35.6. Patches
    9.1. Setup your smb.conf
    9.2. Setup your /etc/krb5.conf
    9.6. Notes
    9.1. Setup your smb.conf
    9.2. Setup your /etc/krb5.conf
    9.3.1. Possible errors
    9.6. Notes
    16.1. Configuring Samba Share Access Controls
    16.2. Remote Server Administration
    16.3. Network Logon Script Magic
    16.1. Configuring Samba Share Access Controls
    16.1.1. Share Permissions Management
    16.1.1.1. Windows NT4 Workstation/Server
    16.1.1.2. Windows 200x/XP
    16.2. Remote Server Administration
    16.3. Network Logon Script Magic
    3.1. Discussion
    3.2. How browsing functions and how to deploy stable and 
 dependable browsing using Samba
    3.3. Use of the Remote Announce
    3.4. Use of the Remote Browse Sync
    3.5. Use of WINS
    3.5.1. WINS Replication
    3.5.2. Static WINS Entries
    3.6. Do NOT use more than one (1) protocol on MS Windows machines
    3.7. Name Resolution Order
    3.1. Discussion
    3.2. How browsing functions and how to deploy stable and 
 dependable browsing using Samba
    3.3. Use of the Remote Announce
    3.4. Use of the Remote Browse Sync
    3.5. Use of WINS
    3.5.1. WINS Replication
    3.5.2. Static WINS Entries
    3.6. Do NOT use more than one (1) protocol on MS Windows machines
    3.7. Name Resolution Order
    35.1. Introduction
    35.2. General info
    35.3. Debug levels
    35.4. Internal errors
    35.5. Attaching to a running process
    35.6. Patches
    35.1. Introduction
    35.2. General info
    35.3. Debug levels
    35.4. Internal errors
    35.5. Attaching to a running process
    35.6. Patches
    27.1. Access Samba source code via CVS
    27.1.1. Introduction
    27.1.2. CVS Access to samba.org
    27.1.2.1. Access via CVSweb
    27.1.2.2. Access via cvs
    27.2. Accessing the samba sources via rsync and ftp
    27.3. Verifying Samba's PGP signature
    27.4. Building the Binaries
    27.5. Starting the smbd and nmbd
    27.5.1. Starting from inetd.conf
    27.5.2. Alternative: starting it as a daemon
    27.1. Access Samba source code via CVS
    27.1.1. Introduction
    27.1.2. CVS Access to samba.org
    27.1.2.1. Access via CVSweb
    27.1.2.2. Access via cvs
    27.2. Accessing the samba sources via rsync and ftp
    27.3. Verifying Samba's PGP signature
    27.4. Building the Binaries
    27.4.1. Compiling samba with Active Directory support
    27.4.1.1. Installing the required packages for Debian
    27.4.1.2. Installing the required packages for RedHat
    27.5. Starting the smbd and nmbd
    27.5.1. Starting from inetd.conf
    27.5.2. Alternative: starting it as a daemon
    14.1. Introduction
    14.2. Configuring smb.conf
    14.3. CUPS - RAW Print Through Mode
    14.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe
 PostScript driver with CUPS-PPDs downloaded to clients
    14.5. Windows Terminal Servers (WTS) as CUPS clients
    14.6. Setting up CUPS for driver download
    14.7. Sources of CUPS drivers / PPDs
    14.8. The CUPS Filter Chains
    14.9. CUPS Print Drivers and Devices
    14.10. Limiting the number of pages users can print
    14.11. Advanced Postscript Printing from MS Windows
    14.12. Auto-Deletion of CUPS spool files
    14.1. Introduction
    14.2. Configuring smb.conf
    14.3. CUPS - RAW Print Through Mode
    14.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe
 PostScript driver with CUPS-PPDs downloaded to clients
    14.5. Windows Terminal Servers (WTS) as CUPS clients
    14.6. Setting up CUPS for driver download
    14.7. Sources of CUPS drivers / PPDs
    14.7.1. cupsaddsmb
    14.8. The CUPS Filter Chains
    14.9. CUPS Print Drivers and Devices
    14.9.1. Further printing steps
    14.10. Limiting the number of pages users can print
    14.11. Advanced Postscript Printing from MS Windows
    14.12. Auto-Deletion of CUPS spool files
    33.1. Introduction
    33.2. Assumptions
    33.3. The tests
    33.4. Still having troubles?
    33.1. Introduction
    33.2. Assumptions
    33.3. The tests
    33.4. Still having troubles?
    10.1. Joining an NT Domain with Samba 3.0
    10.2. Why is this better than security = server?
    10.1. Joining an NT Domain with Samba 3.0
    10.2. Why is this better than security = server?
    24.1. Overview of browsing
    24.2. Browsing support in samba
    24.3. Problem resolution
    24.4. Browsing across subnets
    24.5. Setting up a WINS server
    24.6. Setting up Browsing in a WORKGROUP
    24.7. Setting up Browsing in a DOMAIN
    24.9. Making samba the domain master
    24.10. Note about broadcast addresses
    24.11. Multiple interfaces
    24.1. Overview of browsing
    24.2. Browsing support in samba
    24.3. Problem resolution
    24.4. Browsing across subnets
    24.4.1. How does cross subnet browsing work ?
    24.5. Setting up a WINS server
    24.6. Setting up Browsing in a WORKGROUP
    24.7. Setting up Browsing in a DOMAIN
    24.9. Making samba the domain master
    24.10. Note about broadcast addresses
    24.11. Multiple interfaces
    2.1. Obtaining and installing samba
    2.2. Configuring samba
    2.2.1. Editing the smb.conf
    2.2.2. SWAT
    2.3. Try listing the shares available on your 
 	server
    2.4. Try connecting with the unix client
    2.5. Try connecting from a DOS, WfWg, Win9x, WinNT, 
 	Win2k, OS/2, etc... client
    2.6. What If Things Don't Work?
    2.6.1. Scope IDs
    2.6.2. Locking
    2.1. Obtaining and installing samba
    2.2. Configuring samba
    2.2.1. Editing the smb.conf
    2.2.1.1. Test your config file with 
 	
    2.2.2. SWAT
    2.3. Try listing the shares available on your 
 	server
    2.4. Try connecting with the unix client
    2.5. Try connecting from a DOS, WfWg, Win9x, WinNT, 
 	Win2k, OS/2, etc... client
    2.6. What If Things Don't Work?
    2.6.1. Scope IDs
    2.6.2. Locking
    23.1. Name Resolution in a pure Unix/Linux world
    23.1.1. /etc/hosts
    23.1.2. /etc/resolv.conf
    23.1.3. /etc/host.conf
    23.1.4. /etc/nsswitch.conf
    23.2. Name resolution as used within MS Windows networking
    23.2.1. The NetBIOS Name Cache
    23.2.2. The LMHOSTS file
    23.2.3. HOSTS file
    23.2.4. DNS Lookup
    23.2.5. WINS Lookup
    23.1. Name Resolution in a pure Unix/Linux world
    23.1.1. /etc/hosts
    23.1.2. /etc/resolv.conf
    23.1.3. /etc/host.conf
    23.1.4. /etc/nsswitch.conf
    23.2. Name resolution as used within MS Windows networking
    23.2.1. The NetBIOS Name Cache
    23.2.2. The LMHOSTS file
    23.2.3. HOSTS file
    23.2.4. DNS Lookup
    23.2.5. WINS Lookup
    19.1. Trust Relationship Background
    19.2. Native MS Windows NT4 Trusts Configuration
    19.2.1. NT4 as the Trusting Domain (ie. creating the trusted account)
    19.2.2. NT4 as the Trusted Domain (ie. creating trusted account's password)
    19.3. Configuring Samba NT-style Domain Trusts
    19.3.1. Samba-3 as the Trusting Domain
    19.3.2. Samba-3 as the Trusted Domain
    19.1. Trust Relationship Background
    19.2. Native MS Windows NT4 Trusts Configuration
    19.2.1. NT4 as the Trusting Domain (ie. creating the trusted account)
    19.2.2. NT4 as the Trusted Domain (ie. creating trusted account's password)
    19.3. Configuring Samba NT-style Domain Trusts
    19.3.1. Samba-3 as the Trusting Domain
    19.3.2. Samba-3 as the Trusted Domain
    22.1. Instructions
    22.1.1. Notes
    28.1. Planning and Getting Started
    28.1.1. Objectives
    28.1.2. Steps In Migration Process
    28.2. Managing Samba-3 Domain Control
    28.1. Planning and Getting Started
    28.1.1. Objectives
    28.1.2. Steps In Migration Process
    28.2. Managing Samba-3 Domain Control
    Introduction
    30.1. Macintosh clients?
    30.2. OS2 Client
    30.2.1. How can I configure OS/2 Warp Connect or 
 		OS/2 Warp 4 as a client for Samba?
    30.2.2. How can I configure OS/2 Warp 3 (not Connect), 
 		OS/2 1.2, 1.3 or 2.x for Samba?
    30.2.3. Are there any other issues when OS/2 (any version) 
 		is used as a client?
    30.2.4. How do I get printer driver download working 
 		for OS/2 clients?
    30.3. Windows for Workgroups
    30.3.1. Use latest TCP/IP stack from Microsoft
    30.3.2. Delete .pwl files after password change
    30.3.3. Configure WfW password handling
    30.3.4. Case handling of passwords
    30.3.5. Use TCP/IP as default protocol
    30.4. Windows '95/'98
    30.5. Windows 2000 Service Pack 2
    30.6. Windows NT 3.1
    30.1. Macintosh clients?
    30.2. OS2 Client
    30.2.1. How can I configure OS/2 Warp Connect or 
 		OS/2 Warp 4 as a client for Samba?
    30.2.2. How can I configure OS/2 Warp 3 (not Connect), 
 		OS/2 1.2, 1.3 or 2.x for Samba?
    30.2.3. Are there any other issues when OS/2 (any version) 
 		is used as a client?
    30.2.4. How do I get printer driver download working 
 		for OS/2 clients?
    30.3. Windows for Workgroups
    30.3.1. Use latest TCP/IP stack from Microsoft
    30.3.2. Delete .pwl files after password change
    30.3.3. Configure WfW password handling
    30.3.4. Case handling of passwords
    30.3.5. Use TCP/IP as default protocol
    30.4. Windows '95/'98
    30.5. Windows 2000 Service Pack 2
    30.6. Windows NT 3.1
    20.1. Samba and PAM
    20.2. Distributed Authentication
    20.3. PAM Configuration in smb.conf
    20.1. Samba and PAM
    20.2. Distributed Authentication
    20.3. PAM Configuration in smb.conf
    4.1. Introduction
    4.2. Important Notes About Security
    4.2.1. Advantages of SMB Encryption
    4.2.2. Advantages of non-encrypted passwords
    4.3. The smbpasswd Command
    4.4. Plain text
    4.5. TDB
    4.6. LDAP
    4.6.1. Introduction
    4.6.2. Introduction
    4.6.3. Supported LDAP Servers
    4.6.4. Schema and Relationship to the RFC 2307 posixAccount
    4.6.5. Configuring Samba with LDAP
    4.6.5.1. OpenLDAP configuration
    4.6.5.2. Configuring Samba
    4.6.6. Accounts and Groups management
    4.6.7. Security and sambaAccount
    4.6.8. LDAP specials attributes for sambaAccounts
    4.6.9. Example LDIF Entries for a sambaAccount
    4.7. MySQL
    4.7.1. Creating the database
    4.7.2. Configuring
    4.7.3. Using plaintext passwords or encrypted password
    4.7.4. Getting non-column data from the table
    4.8. XML
    4.1. Introduction
    4.2. Important Notes About Security
    4.2.1. Advantages of SMB Encryption
    4.2.2. Advantages of non-encrypted passwords
    4.3. The smbpasswd Command
    4.4. Plain text
    4.5. TDB
    4.6. LDAP
    4.6.1. Introduction
    4.6.2. Introduction
    4.6.3. Supported LDAP Servers
    4.6.4. Schema and Relationship to the RFC 2307 posixAccount
    4.6.5. Configuring Samba with LDAP
    4.6.5.1. OpenLDAP configuration
    4.6.5.2. Configuring Samba
    4.6.6. Accounts and Groups management
    4.6.7. Security and sambaAccount
    4.6.8. LDAP specials attributes for sambaAccounts
    4.6.9. Example LDIF Entries for a sambaAccount
    4.7. MySQL
    4.7.1. Creating the database
    4.7.2. Configuring
    4.7.3. Using plaintext passwords or encrypted password
    4.7.4. Getting non-column data from the table
    4.8. XML
    17.1. Creating and Managing System Policies
    17.1.1. Windows 9x/Me Policies
    17.1.2. Windows NT4 Style Policy Files
    17.1.3. MS Windows 200x / XP Professional Policies
    17.2. Managing Account/User Policies
    17.2.1. With Windows NT4/200x
    17.2.2. With a Samba PDC
    17.3. System Startup and Logon Processing Overview
    17.1. Creating and Managing System Policies
    17.1.1. Windows 9x/Me Policies
    17.1.2. Windows NT4 Style Policy Files
    17.1.2.1. Registry Tattoos
    17.1.3. MS Windows 200x / XP Professional Policies
    17.1.3.1. Administration of Win2K / XP Policies
    17.2. Managing Account/User Policies
    17.2.1. With Windows NT4/200x
    17.2.2. With a Samba PDC
    17.3. System Startup and Logon Processing Overview
    29.1. HPUX
    29.2. SCO Unix
    29.3. DNIX
    29.4. RedHat Linux Rembrandt-II
    29.5. AIX
    29.6. Solaris
    29.1. HPUX
    29.2. SCO Unix
    29.3. DNIX
    29.4. RedHat Linux Rembrandt-II
    29.5. AIX
    29.5.1. Sequential Read Ahead
    29.6. Solaris
    13.1. Introduction
    13.2. Configuration
    13.2.1. Creating [print$]
    13.2.2. Setting Drivers for Existing Printers
    13.2.3. Support a large number of printers
    13.2.4. Adding New Printers via the Windows NT APW
    13.2.5. Samba and Printer Ports
    13.3. The Imprints Toolset
    13.3.1. What is Imprints?
    13.3.2. Creating Printer Driver Packages
    13.3.3. The Imprints server
    13.3.4. The Installation Client
    13.4. Diagnosis
    13.4.1. Introduction
    13.4.2. Debugging printer problems
    13.4.3. What printers do I have?
    13.4.4. Setting up printcap and print servers
    13.4.5. Job sent, no output
    13.4.6. Job sent, strange output
    13.4.7. Raw PostScript printed
    13.4.8. Advanced Printing
    13.4.9. Real debugging
    13.1. Introduction
    13.2. Configuration
    13.2.1. Creating [print$]
    13.2.2. Setting Drivers for Existing Printers
    13.2.3. Support a large number of printers
    13.2.4. Adding New Printers via the Windows NT APW
    13.2.5. Samba and Printer Ports
    13.3. The Imprints Toolset
    13.3.1. What is Imprints?
    13.3.2. Creating Printer Driver Packages
    13.3.3. The Imprints server
    13.3.4. The Installation Client
    13.4. Diagnosis
    13.4.1. Introduction
    13.4.2. Debugging printer problems
    13.4.3. What printers do I have?
    13.4.4. Setting up printcap and print servers
    13.4.5. Job sent, no output
    13.4.6. Job sent, strange output
    13.4.7. Raw PostScript printed
    13.4.8. Advanced Printing
    13.4.9. Real debugging
    34.1. Diagnostics tools
    34.2. Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
    34.3. Useful URL's
    34.4. Getting help from the mailing lists
    34.5. How to get off the mailinglists
    34.1. Diagnostics tools
    34.2. Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
    34.3. Useful URL's
    34.4. Getting help from the mailing lists
    34.5. How to get off the mailinglists
    18.1. Roaming Profiles
    18.1.1. Samba Configuration for Profile Handling
    18.1.1.1. NT4/200x User Profiles
    18.1.1.2. Windows 9x / Me User Profiles
    18.1.1.3. Mixed Windows 9x / Me and Windows NT4/200x User Profiles
    18.1.2. Windows Client Profile Configuration Information
    18.1.2.1. Windows 9x / Me Profile Setup
    18.1.2.2. Windows NT4 Workstation
    18.1.2.3. Windows 2000/XP Professional
    18.1.3. Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    18.1.4. Profile Migration from Windows NT4/200x Server to Samba
    18.1.4.1. Windows NT4 Profile Management Tools
    18.1.4.2. Side bar Notes
    18.1.4.3. moveuser.exe
    18.1.4.4. Get SID
    18.2. Mandatory profiles
    18.3. Creating/Managing Group Profiles
    18.4. Default Profile for Windows Users
    18.4.1. MS Windows 9x/Me
    18.4.2. MS Windows NT4 Workstation
    18.4.3. MS Windows 200x/XP
    18.1. Roaming Profiles
    18.1.1. Samba Configuration for Profile Handling
    18.1.1.1. NT4/200x User Profiles
    18.1.1.2. Windows 9x / Me User Profiles
    18.1.1.3. Mixed Windows 9x / Me and Windows NT4/200x User Profiles
    18.1.2. Windows Client Profile Configuration Information
    18.1.2.1. Windows 9x / Me Profile Setup
    18.1.2.2. Windows NT4 Workstation
    18.1.2.3. Windows 2000/XP Professional
    18.1.3. Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    18.1.4. Profile Migration from Windows NT4/200x Server to Samba
    18.1.4.1. Windows NT4 Profile Management Tools
    18.1.4.2. Side bar Notes
    18.1.4.3. moveuser.exe
    18.1.4.4. Get SID
    18.2. Mandatory profiles
    18.3. Creating/Managing Group Profiles
    18.4. Default Profile for Windows Users
    18.4.1. MS Windows 9x/Me
    18.4.1.1. How User Profiles Are Handled in Windows 9x / Me?
    18.4.2. MS Windows NT4 Workstation
    18.4.3. MS Windows 200x/XP
    8.1. Prerequisite Reading
    8.2. Background
    8.3. What qualifies a Domain Controller on the network?
    8.3.1. How does a Workstation find its domain controller?
    8.3.2. When is the PDC needed?
    8.4. Can Samba be a Backup Domain Controller to an NT PDC?
    8.5. How do I set up a Samba BDC?
    8.5.1. How do I replicate the smbpasswd file?
    8.5.2. Can I do this all with LDAP?
    8.1. Prerequisite Reading
    8.2. Background
    8.3. What qualifies a Domain Controller on the network?
    8.3.1. How does a Workstation find its domain controller?
    8.3.2. When is the PDC needed?
    8.4. Can Samba be a Backup Domain Controller to an NT PDC?
    8.5. How do I set up a Samba BDC?
    8.5.1. How do I replicate the smbpasswd file?
    8.5.2. Can I do this all with LDAP?
    2.1. Obtaining and installing samba
    2.2. Configuring samba
    2.3. Try listing the shares available on your 
 	server
    2.4. Try connecting with the unix client
    2.5. Try connecting from a DOS, WfWg, Win9x, WinNT, 
 	Win2k, OS/2, etc... client
    2.6. What If Things Don't Work?
    3.1. Discussion
    3.2. How browsing functions and how to deploy stable and 
 dependable browsing using Samba
    3.3. Use of the Remote Announce
    3.4. Use of the Remote Browse Sync
    3.5. Use of WINS
    3.6. Do NOT use more than one (1) protocol on MS Windows machines
    3.7. Name Resolution Order
    4.1. Introduction
    4.2. Important Notes About Security
    4.3. The smbpasswd Command
    4.4. Plain text
    4.5. TDB
    4.6. LDAP
    4.7. MySQL
    4.8. XML
    5.1. Stand Alone Server
    5.2. Domain Member Server
    5.3. Domain Controller
    6.1. User and Share security level
    7.1. Prerequisite Reading
    7.2. Background
    7.3. Configuring the Samba Domain Controller
    7.4. Creating Machine Trust Accounts and Joining Clients to the Domain
    7.5. Common Problems and Errors
    7.6. Domain Control for Windows 9x/ME
    8.1. Prerequisite Reading
    8.2. Background
    8.3. What qualifies a Domain Controller on the network?
    8.4. Can Samba be a Backup Domain Controller to an NT PDC?
    8.5. How do I set up a Samba BDC?
    9.1. Setup your smb.conf
    9.2. Setup your /etc/krb5.conf
    9.6. Notes
    10.1. Joining an NT Domain with Samba 3.0
    10.2. Why is this better than security = server?
    11.1. Viewing and changing UNIX permissions using the NT 
 	security dialogs
    11.2. How to view file security on a Samba share
    11.3. Viewing file ownership
    11.4. Viewing file or directory permissions
    11.5. Modifying file or directory permissions
    11.6. Interaction with the standard Samba create mask 
 	parameters
    11.7. Interaction with the standard Samba file attribute 
 	mapping
    13.1. Introduction
    13.2. Configuration
    13.3. The Imprints Toolset
    13.4. Diagnosis
    14.1. Introduction
    14.2. Configuring smb.conf
    14.3. CUPS - RAW Print Through Mode
    14.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe
 PostScript driver with CUPS-PPDs downloaded to clients
    14.5. Windows Terminal Servers (WTS) as CUPS clients
    14.6. Setting up CUPS for driver download
    14.7. Sources of CUPS drivers / PPDs
    14.8. The CUPS Filter Chains
    14.9. CUPS Print Drivers and Devices
    14.10. Limiting the number of pages users can print
    14.11. Advanced Postscript Printing from MS Windows
    14.12. Auto-Deletion of CUPS spool files
    15.1. Abstract
    15.2. Introduction
    15.3. What Winbind Provides
    15.4. How Winbind Works
    15.5. Installation and Configuration
    15.6. Limitations
    15.7. Conclusion
    16.1. Configuring Samba Share Access Controls
    16.2. Remote Server Administration
    16.3. Network Logon Script Magic
    17.1. Creating and Managing System Policies
    17.2. Managing Account/User Policies
    17.3. System Startup and Logon Processing Overview
    18.1. Roaming Profiles
    18.2. Mandatory profiles
    18.3. Creating/Managing Group Profiles
    18.4. Default Profile for Windows Users
    19.1. Trust Relationship Background
    19.2. Native MS Windows NT4 Trusts Configuration
    19.3. Configuring Samba NT-style Domain Trusts
    20.1. Samba and PAM
    20.2. Distributed Authentication
    20.3. PAM Configuration in smb.conf
    21.1. Introduction and configuration
    21.2. Included modules
    21.3. VFS modules available elsewhere
    22.1. Instructions
    23.1. Name Resolution in a pure Unix/Linux world
    23.2. Name resolution as used within MS Windows networking
    24.1. Overview of browsing
    24.2. Browsing support in samba
    24.3. Problem resolution
    24.4. Browsing across subnets
    24.5. Setting up a WINS server
    24.6. Setting up Browsing in a WORKGROUP
    24.7. Setting up Browsing in a DOMAIN
    24.9. Making samba the domain master
    24.10. Note about broadcast addresses
    24.11. Multiple interfaces
    25.1. Introduction
    25.2. Using host based protection
    25.3. Using interface protection
    25.4. Using a firewall
    25.5. Using a IPC$ share deny
    25.6. Upgrading Samba
    26.1. What are charsets and unicode?
    26.2. Samba and charsets
    26.3. Conversion from old names
    26.4. Japanese charsets
    27.1. Access Samba source code via CVS
    27.2. Accessing the samba sources via rsync and ftp
    27.3. Verifying Samba's PGP signature
    27.4. Building the Binaries
    27.5. Starting the smbd and nmbd
    28.1. Planning and Getting Started
    28.2. Managing Samba-3 Domain Control
    29.1. HPUX
    29.2. SCO Unix
    29.3. DNIX
    29.4. RedHat Linux Rembrandt-II
    29.5. AIX
    29.6. Solaris
    30.1. Macintosh clients?
    30.2. OS2 Client
    30.3. Windows for Workgroups
    30.4. Windows '95/'98
    30.5. Windows 2000 Service Pack 2
    30.6. Windows NT 3.1
    31.1. SWAT Features and Benefits
    32.1. Comparisons
    32.2. Socket options
    32.3. Read size
    32.4. Max xmit
    32.5. Log level
    32.6. Read raw
    32.7. Write raw
    32.8. Slow Clients
    32.9. Slow Logins
    32.10. Client tuning
    33.1. Introduction
    33.2. Assumptions
    33.3. The tests
    33.4. Still having troubles?
    34.1. Diagnostics tools
    34.2. Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
    34.3. Useful URL's
    34.4. Getting help from the mailing lists
    34.5. How to get off the mailinglists
    35.1. Introduction
    35.2. General info
    35.3. Debug levels
    35.4. Internal errors
    35.5. Attaching to a running process
    35.6. Patches
    7.1. Prerequisite Reading
    7.2. Background
    7.3. Configuring the Samba Domain Controller
    7.4. Creating Machine Trust Accounts and Joining Clients to the Domain
    7.4.1. Manual Creation of Machine Trust Accounts
    7.4.2. "On-the-Fly" Creation of Machine Trust Accounts
    7.4.3. Joining the Client to the Domain
    7.5. Common Problems and Errors
    7.5.1. I cannot include a '$' in a machine name
    7.5.2. 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 trust account.
    7.5.3. The system can not log you on (C000019B)....
    7.5.4. The machine trust account for this computer either does not 
 exist or is not accessible.
    7.5.5. When I attempt to login to a Samba Domain from a NT4/W2K workstation,
 I get a message about my account being disabled.
    7.6. Domain Control for Windows 9x/ME
    7.1. Prerequisite Reading
    7.2. Background
    7.3. Configuring the Samba Domain Controller
    7.4. Creating Machine Trust Accounts and Joining Clients to the Domain
    7.4.1. Manual Creation of Machine Trust Accounts
    7.4.2. "On-the-Fly" Creation of Machine Trust Accounts
    7.4.3. Joining the Client to the Domain
    7.5. Common Problems and Errors
    7.5.1. I cannot include a '$' in a machine name
    7.5.2. 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 trust account.
    7.5.3. The system can not log you on (C000019B)....
    7.5.4. The machine trust account for this computer either does not 
 exist or is not accessible.
    7.5.5. When I attempt to login to a Samba Domain from a NT4/W2K workstation,
 I get a message about my account being disabled.
    7.6. Domain Control for Windows 9x/ME
    7.6.1. Configuration Instructions:	Network Logons
    25.1. Introduction
    25.2. Using host based protection
    25.3. Using interface protection
    25.4. Using a firewall
    25.5. Using a IPC$ share deny
    25.6. Upgrading Samba
    25.1. Introduction
    25.2. Using host based protection
    25.3. Using interface protection
    25.4. Using a firewall
    25.5. Using a IPC$ share deny
    25.6. Upgrading Samba
    6.1. User and Share security level
    6.1.1. User Level Security
    6.1.2. Share Level Security
    6.1.3. Server Level Security
    6.1.3.1. Configuring Samba for Seemless Windows Network Integration
    6.1.3.2. Use MS Windows NT as an authentication server
    6.1.4. Domain Level Security
    6.1.4.1. Samba as a member of an MS Windows NT security domain
    6.1.5. ADS Level Security
    5.1. Stand Alone Server
    5.2. Domain Member Server
    5.3. Domain Controller
    5.1. Stand Alone Server
    5.2. Domain Member Server
    5.3. Domain Controller
    5.3.1. Domain Controller Types
    32.1. Comparisons
    32.2. Socket options
    32.3. Read size
    32.4. Max xmit
    32.5. Log level
    32.6. Read raw
    32.7. Write raw
    32.8. Slow Clients
    32.9. Slow Logins
    32.10. Client tuning
    32.1. Comparisons
    32.2. Socket options
    32.3. Read size
    32.4. Max xmit
    32.5. Log level
    32.6. Read raw
    32.7. Write raw
    32.8. Slow Clients
    32.9. Slow Logins
    32.10. Client tuning
    31.1. SWAT Features and Benefits
    31.1.1. The SWAT Home Page
    31.1.2. Global Settings
    31.1.3. The SWAT Wizard
    31.1.4. Share Settings
    31.1.5. Printing Settings
    31.1.6. The Status Page
    31.1.7. The Password Change Page
    Introduction
    26.1. What are charsets and unicode?
    26.2. Samba and charsets
    26.3. Conversion from old names
    26.4. Japanese charsets
    26.1. What are charsets and unicode?
    26.2. Samba and charsets
    26.3. Conversion from old names
    26.4. Japanese charsets
    Samba doesn't work correctly with Japanese charsets yet. Here are points of attention when setting it up:
    You should set mangling method = hash
    There are various iconv() implementations around and not all of 
+them work equally well. glibc2's iconv() has a critical problem in CP932. 
+libiconv-1.8 works with CP932 but still has some problems and does not 
+work with EUC-JP. 
    You should set dos charset = CP932, not Shift_JIS, SJIS...
    Currently only unix charset = CP932 will work (but still has some problems...) because of iconv() issues. unix charset = EUC-JP doesn't work well because of iconv() issues.
    Currently Samba 3.0 does not support unix charset = UTF8-MAC/CAP/HEX/JIS*
    More information (in Japanese) is available at: http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html.
    11.1. Viewing and changing UNIX permissions using the NT 
 	security dialogs
    11.2. How to view file security on a Samba share
    11.3. Viewing file ownership
    11.4. Viewing file or directory permissions
    11.4.1. File Permissions
    11.4.2. Directory Permissions
    11.5. Modifying file or directory permissions
    11.6. Interaction with the standard Samba create mask 
 	parameters
    11.7. Interaction with the standard Samba file attribute 
 	mapping
    11.1. Viewing and changing UNIX permissions using the NT 
 	security dialogs
    11.2. How to view file security on a Samba share
    11.3. Viewing file ownership
    11.4. Viewing file or directory permissions
    11.4.1. File Permissions
    11.4.2. Directory Permissions
    11.5. Modifying file or directory permissions
    11.6. Interaction with the standard Samba create mask 
 	parameters
    11.7. Interaction with the standard Samba file attribute 
 	mapping
    21.1. Introduction and configuration
    21.2. Included modules
    21.2.1. audit
    21.2.2. extd_audit
    21.2.3. recycle
    21.2.4. netatalk
    21.3. VFS modules available elsewhere
    21.3.1. DatabaseFS
    21.3.2. vscan
    21.1. Introduction and configuration
    21.2. Included modules
    21.2.1. audit
    21.2.2. extd_audit
    21.2.3. recycle
    21.2.4. netatalk
    21.3. VFS modules available elsewhere
    21.3.1. DatabaseFS
    21.3.2. vscan
    15.1. Abstract
    15.2. Introduction
    15.3. What Winbind Provides
    15.4. How Winbind Works
    15.4.1. Microsoft Remote Procedure Calls
    15.4.2. Microsoft Active Directory Services
    15.4.3. Name Service Switch
    15.4.4. Pluggable Authentication Modules
    15.4.5. User and Group ID Allocation
    15.4.6. Result Caching
    15.5. Installation and Configuration
    15.5.1. Introduction
    15.5.2. Requirements
    15.5.3. Testing Things Out
    15.5.3.1. Configure and compile SAMBA
    15.5.3.2. Configure nsswitch.conf
    15.5.3.3. Configure smb.conf
    15.5.3.4. Join the SAMBA server to the PDC domain
    15.5.3.5. Start up the winbindd daemon and test it!
    15.5.3.6. Fix the init.d startup scripts
    15.5.3.7. Configure Winbind and PAM
    15.6. Limitations
    15.7. Conclusion
    15.1. Abstract
    15.2. Introduction
    15.3. What Winbind Provides
    15.3.1. Target Uses
    15.4. How Winbind Works
    15.4.1. Microsoft Remote Procedure Calls
    15.4.2. Microsoft Active Directory Services
    15.4.3. Name Service Switch
    15.4.4. Pluggable Authentication Modules
    15.4.5. User and Group ID Allocation
    15.4.6. Result Caching
    15.5. Installation and Configuration
    15.5.1. Introduction
    15.5.2. Requirements
    15.5.3. Testing Things Out
    15.5.3.1. Configure and compile SAMBA
    15.5.3.2. Configure nsswitch.conf
    15.5.3.3. Configure smb.conf
    15.5.3.4. Join the SAMBA server to the PDC domain
    15.5.3.5. Start up the winbindd daemon and test it!
    15.5.3.6. Fix the init.d startup scripts
    15.5.3.6.1. Linux
    15.5.3.6.2. Solaris
    15.5.3.6.3. Restarting
    15.5.3.7. Configure Winbind and PAM
    15.5.3.7.1. Linux/FreeBSD-specific PAM configuration
    15.5.3.7.2. Solaris-specific configuration
    15.6. Limitations
    15.7. Conclusion
     
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "EDITREG" "1" "17 April 2003" "" ""
+.TH "EDITREG" "1" "19 april 2003" "" ""
 
 .SH NAME
 editreg \- A utility to report and change SIDs in registry files
diff --git a/docs/manpages/findsmb.1 b/docs/manpages/findsmb.1
index 37aa7565b5..ab79307106 100644
--- a/docs/manpages/findsmb.1
+++ b/docs/manpages/findsmb.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "FINDSMB" "1" "17 April 2003" "" ""
+.TH "FINDSMB" "1" "19 april 2003" "" ""
 
 .SH NAME
 findsmb \- list info about machines that respond to SMB  name queries on a subnet
diff --git a/docs/manpages/lmhosts.5 b/docs/manpages/lmhosts.5
index 84cd3e42fe..2ec8c256d4 100644
--- a/docs/manpages/lmhosts.5
+++ b/docs/manpages/lmhosts.5
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "LMHOSTS" "5" "17 April 2003" "" ""
+.TH "LMHOSTS" "5" "19 april 2003" "" ""
 
 .SH NAME
 lmhosts \- The Samba NetBIOS hosts file
diff --git a/docs/manpages/net.8 b/docs/manpages/net.8
index c22ecaadf1..ce864d0d70 100644
--- a/docs/manpages/net.8
+++ b/docs/manpages/net.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "NET" "8" "17 April 2003" "" ""
+.TH "NET" "8" "19 april 2003" "" ""
 
 .SH NAME
 net \- Tool for administration of Samba and remote CIFS servers.
diff --git a/docs/manpages/nmbd.8 b/docs/manpages/nmbd.8
index 2f62b4f549..b50356b82c 100644
--- a/docs/manpages/nmbd.8
+++ b/docs/manpages/nmbd.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "NMBD" "8" "17 April 2003" "" ""
+.TH "NMBD" "8" "19 april 2003" "" ""
 
 .SH NAME
 nmbd \- NetBIOS name server to provide NetBIOS  over IP naming services to clients
diff --git a/docs/manpages/nmblookup.1 b/docs/manpages/nmblookup.1
index fc8ae0b9f8..6154528a9a 100644
--- a/docs/manpages/nmblookup.1
+++ b/docs/manpages/nmblookup.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "NMBLOOKUP" "1" "17 April 2003" "" ""
+.TH "NMBLOOKUP" "1" "19 april 2003" "" ""
 
 .SH NAME
 nmblookup \- NetBIOS over TCP/IP client used to lookup NetBIOS  names
diff --git a/docs/manpages/ntlm_auth.1 b/docs/manpages/ntlm_auth.1
index bb562fe964..8cc6061ebb 100644
--- a/docs/manpages/ntlm_auth.1
+++ b/docs/manpages/ntlm_auth.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "NTLM_AUTH" "1" "17 April 2003" "" ""
+.TH "NTLM_AUTH" "1" "19 april 2003" "" ""
 
 .SH NAME
 ntlm_auth \- tool to allow external access to Winbind's NTLM authentication function
diff --git a/docs/manpages/pdbedit.8 b/docs/manpages/pdbedit.8
index 2f25a5479d..02046dc58e 100644
--- a/docs/manpages/pdbedit.8
+++ b/docs/manpages/pdbedit.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "PDBEDIT" "8" "17 April 2003" "" ""
+.TH "PDBEDIT" "8" "19 april 2003" "" ""
 
 .SH NAME
 pdbedit \- manage the SAM database
diff --git a/docs/manpages/profiles.1 b/docs/manpages/profiles.1
index 6ce5478e49..2aef96aa03 100644
--- a/docs/manpages/profiles.1
+++ b/docs/manpages/profiles.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "PROFILES" "1" "17 April 2003" "" ""
+.TH "PROFILES" "1" "19 april 2003" "" ""
 
 .SH NAME
 profiles \- A utility to report and change SIDs in registry files
diff --git a/docs/manpages/rpcclient.1 b/docs/manpages/rpcclient.1
index c01c3f92d0..e20b9a8029 100644
--- a/docs/manpages/rpcclient.1
+++ b/docs/manpages/rpcclient.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "RPCCLIENT" "1" "17 April 2003" "" ""
+.TH "RPCCLIENT" "1" "19 april 2003" "" ""
 
 .SH NAME
 rpcclient \- tool for executing client side  MS-RPC functions
diff --git a/docs/manpages/samba.7 b/docs/manpages/samba.7
index a0f69baf56..9f01169a5a 100644
--- a/docs/manpages/samba.7
+++ b/docs/manpages/samba.7
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SAMBA" "7" "17 April 2003" "" ""
+.TH "SAMBA" "7" "19 april 2003" "" ""
 
 .SH NAME
 Samba \- A Windows SMB/CIFS fileserver for UNIX
diff --git a/docs/manpages/smb.conf.5 b/docs/manpages/smb.conf.5
index 64c5547dc5..7560ea57f8 100644
--- a/docs/manpages/smb.conf.5
+++ b/docs/manpages/smb.conf.5
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMB.CONF" "5" "17 April 2003" "" ""
+.TH "SMB.CONF" "5" "19 april 2003" "" ""
 
 .SH NAME
 smb.conf \- The configuration file for the Samba suite
diff --git a/docs/manpages/smbcacls.1 b/docs/manpages/smbcacls.1
index 48cac295cc..918c2386de 100644
--- a/docs/manpages/smbcacls.1
+++ b/docs/manpages/smbcacls.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBCACLS" "1" "17 April 2003" "" ""
+.TH "SMBCACLS" "1" "19 april 2003" "" ""
 
 .SH NAME
 smbcacls \- Set or get ACLs on an NT file or directory names
diff --git a/docs/manpages/smbclient.1 b/docs/manpages/smbclient.1
index 449cd0863e..8a70aed551 100644
--- a/docs/manpages/smbclient.1
+++ b/docs/manpages/smbclient.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBCLIENT" "1" "17 April 2003" "" ""
+.TH "SMBCLIENT" "1" "19 april 2003" "" ""
 
 .SH NAME
 smbclient \- ftp-like client to access SMB/CIFS resources  on servers
diff --git a/docs/manpages/smbcontrol.1 b/docs/manpages/smbcontrol.1
index eab84a45ba..f865a6365f 100644
--- a/docs/manpages/smbcontrol.1
+++ b/docs/manpages/smbcontrol.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBCONTROL" "1" "17 April 2003" "" ""
+.TH "SMBCONTROL" "1" "19 april 2003" "" ""
 
 .SH NAME
 smbcontrol \- send messages to smbd, nmbd or winbindd processes
diff --git a/docs/manpages/smbcquotas.1 b/docs/manpages/smbcquotas.1
index 011cb26ef0..a06895656a 100644
--- a/docs/manpages/smbcquotas.1
+++ b/docs/manpages/smbcquotas.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBCQUOTAS" "1" "17 April 2003" "" ""
+.TH "SMBCQUOTAS" "1" "19 april 2003" "" ""
 
 .SH NAME
 smbcquotas \- Set or get QUOTAs of NTFS 5 shares
diff --git a/docs/manpages/smbd.8 b/docs/manpages/smbd.8
index 855705f861..17fd179d39 100644
--- a/docs/manpages/smbd.8
+++ b/docs/manpages/smbd.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBD" "8" "17 April 2003" "" ""
+.TH "SMBD" "8" "19 april 2003" "" ""
 
 .SH NAME
 smbd \- server to provide SMB/CIFS services to clients
diff --git a/docs/manpages/smbgroupedit.8 b/docs/manpages/smbgroupedit.8
index c866fef9df..cd6a79acb1 100644
--- a/docs/manpages/smbgroupedit.8
+++ b/docs/manpages/smbgroupedit.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBGROUPEDIT" "8" "17 April 2003" "" ""
+.TH "SMBGROUPEDIT" "8" "19 april 2003" "" ""
 
 .SH NAME
 smbgroupedit \- Query/set/change UNIX - Windows NT group mapping
diff --git a/docs/manpages/smbmnt.8 b/docs/manpages/smbmnt.8
index 424193da8c..6464567636 100644
--- a/docs/manpages/smbmnt.8
+++ b/docs/manpages/smbmnt.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBMNT" "8" "17 April 2003" "" ""
+.TH "SMBMNT" "8" "19 april 2003" "" ""
 
 .SH NAME
 smbmnt \- helper utility for mounting SMB filesystems
diff --git a/docs/manpages/smbmount.8 b/docs/manpages/smbmount.8
index 306e580834..1e78bd3a3f 100644
--- a/docs/manpages/smbmount.8
+++ b/docs/manpages/smbmount.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBMOUNT" "8" "17 April 2003" "" ""
+.TH "SMBMOUNT" "8" "19 april 2003" "" ""
 
 .SH NAME
 smbmount \- mount an smbfs filesystem
diff --git a/docs/manpages/smbpasswd.5 b/docs/manpages/smbpasswd.5
index 0d061ef1a8..e07da1172f 100644
--- a/docs/manpages/smbpasswd.5
+++ b/docs/manpages/smbpasswd.5
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBPASSWD" "5" "17 April 2003" "" ""
+.TH "SMBPASSWD" "5" "19 april 2003" "" ""
 
 .SH NAME
 smbpasswd \- The Samba encrypted password file
diff --git a/docs/manpages/smbpasswd.8 b/docs/manpages/smbpasswd.8
index bb21a4668b..1a27643b04 100644
--- a/docs/manpages/smbpasswd.8
+++ b/docs/manpages/smbpasswd.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBPASSWD" "8" "17 April 2003" "" ""
+.TH "SMBPASSWD" "8" "19 april 2003" "" ""
 
 .SH NAME
 smbpasswd \- change a user's SMB password
diff --git a/docs/manpages/smbsh.1 b/docs/manpages/smbsh.1
index a10f8d709b..b34a26329a 100644
--- a/docs/manpages/smbsh.1
+++ b/docs/manpages/smbsh.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBSH" "1" "17 April 2003" "" ""
+.TH "SMBSH" "1" "19 april 2003" "" ""
 
 .SH NAME
 smbsh \- Allows access to Windows NT filesystem  using UNIX commands
diff --git a/docs/manpages/smbspool.8 b/docs/manpages/smbspool.8
index c5498ce513..cc03bb1757 100644
--- a/docs/manpages/smbspool.8
+++ b/docs/manpages/smbspool.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBSPOOL" "8" "17 April 2003" "" ""
+.TH "SMBSPOOL" "8" "19 april 2003" "" ""
 
 .SH NAME
 smbspool \- send a print file to an SMB printer
diff --git a/docs/manpages/smbstatus.1 b/docs/manpages/smbstatus.1
index 13bfab4723..5990a81cc1 100644
--- a/docs/manpages/smbstatus.1
+++ b/docs/manpages/smbstatus.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBSTATUS" "1" "17 April 2003" "" ""
+.TH "SMBSTATUS" "1" "19 april 2003" "" ""
 
 .SH NAME
 smbstatus \- report on current Samba connections
diff --git a/docs/manpages/smbtar.1 b/docs/manpages/smbtar.1
index a9e274dda3..cba03cc03a 100644
--- a/docs/manpages/smbtar.1
+++ b/docs/manpages/smbtar.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBTAR" "1" "17 April 2003" "" ""
+.TH "SMBTAR" "1" "19 april 2003" "" ""
 
 .SH NAME
 smbtar \- shell script for backing up SMB/CIFS shares  directly to UNIX tape drives
diff --git a/docs/manpages/smbtree.1 b/docs/manpages/smbtree.1
index e2f61207d9..b4a1870dd8 100644
--- a/docs/manpages/smbtree.1
+++ b/docs/manpages/smbtree.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBTREE" "1" "17 April 2003" "" ""
+.TH "SMBTREE" "1" "19 april 2003" "" ""
 
 .SH NAME
 smbtree \- A text based smb network browser
diff --git a/docs/manpages/smbumount.8 b/docs/manpages/smbumount.8
index 118bb37d52..cadf8c53df 100644
--- a/docs/manpages/smbumount.8
+++ b/docs/manpages/smbumount.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SMBUMOUNT" "8" "17 April 2003" "" ""
+.TH "SMBUMOUNT" "8" "19 april 2003" "" ""
 
 .SH NAME
 smbumount \- smbfs umount for normal users
diff --git a/docs/manpages/swat.8 b/docs/manpages/swat.8
index a1a313c6ea..1965b030b9 100644
--- a/docs/manpages/swat.8
+++ b/docs/manpages/swat.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "SWAT" "8" "17 April 2003" "" ""
+.TH "SWAT" "8" "19 april 2003" "" ""
 
 .SH NAME
 swat \- Samba Web Administration Tool
diff --git a/docs/manpages/testparm.1 b/docs/manpages/testparm.1
index 43412e12e3..ea8a84a4a5 100644
--- a/docs/manpages/testparm.1
+++ b/docs/manpages/testparm.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "TESTPARM" "1" "17 April 2003" "" ""
+.TH "TESTPARM" "1" "19 april 2003" "" ""
 
 .SH NAME
 testparm \- check an smb.conf configuration file for  internal correctness
diff --git a/docs/manpages/testprns.1 b/docs/manpages/testprns.1
index 3d09445608..cb231510f5 100644
--- a/docs/manpages/testprns.1
+++ b/docs/manpages/testprns.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "TESTPRNS" "1" "17 April 2003" "" ""
+.TH "TESTPRNS" "1" "19 april 2003" "" ""
 
 .SH NAME
 testprns \- check printer name for validity with smbd
diff --git a/docs/manpages/vfstest.1 b/docs/manpages/vfstest.1
index 5fcbd46a10..fb9fa0efd0 100644
--- a/docs/manpages/vfstest.1
+++ b/docs/manpages/vfstest.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "VFSTEST" "1" "17 April 2003" "" ""
+.TH "VFSTEST" "1" "19 april 2003" "" ""
 
 .SH NAME
 vfstest \- tool for testing samba VFS modules
diff --git a/docs/manpages/wbinfo.1 b/docs/manpages/wbinfo.1
index a23b08ab65..18dbcbf306 100644
--- a/docs/manpages/wbinfo.1
+++ b/docs/manpages/wbinfo.1
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "WBINFO" "1" "17 April 2003" "" ""
+.TH "WBINFO" "1" "19 april 2003" "" ""
 
 .SH NAME
 wbinfo \- Query information from winbind daemon
diff --git a/docs/manpages/winbindd.8 b/docs/manpages/winbindd.8
index 7341746cde..00a28ab36f 100644
--- a/docs/manpages/winbindd.8
+++ b/docs/manpages/winbindd.8
@@ -3,7 +3,7 @@
 .\"  
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng .
-.TH "WINBINDD" "8" "17 April 2003" "" ""
+.TH "WINBINDD" "8" "19 april 2003" "" ""
 
 .SH NAME
 winbindd \- Name Service Switch daemon for resolving names  from NT servers
-- 
cgit 


From 84728c340001e4355f8c0cd668eb157090722c80 Mon Sep 17 00:00:00 2001
From: Simo Sorce 
Date: Sat, 19 Apr 2003 15:29:39 +0000
Subject: fixes

fix debug, add "idmap" string to the list of classes
fix idmap, check init failures, and enhance debugging
fix idmap_tdb, _do_ init uid and gid low,high states (too bad I missed that
before)
fix smbd/uid.c, use gid_t for gids and uid_t for uids
(This used to be commit bc95de4ebb014080bc70173e7df94c672cea8df6)
---
 source3/lib/debug.c     |  1 +
 source3/sam/idmap.c     |  9 ++++++---
 source3/sam/idmap_tdb.c | 14 ++++++++++++--
 source3/smbd/uid.c      |  2 ++
 4 files changed, 21 insertions(+), 5 deletions(-)

diff --git a/source3/lib/debug.c b/source3/lib/debug.c
index dc675037a0..fdbd54fafb 100644
--- a/source3/lib/debug.c
+++ b/source3/lib/debug.c
@@ -154,6 +154,7 @@ static const char *default_classname_table[] = {
 	"auth",              /* DBGC_AUTH         */
 	"winbind",           /* DBGC_WINBIND      */
 	"vfs",		     /* DBGC_VFS	  */
+	"idmap",	     /* DBGC_IDMAP	  */
 	NULL
 };
 
diff --git a/source3/sam/idmap.c b/source3/sam/idmap.c
index 8b5e23de25..771f4169a2 100644
--- a/source3/sam/idmap.c
+++ b/source3/sam/idmap.c
@@ -67,15 +67,18 @@ BOOL idmap_init(const char *remote_backend)
 {
 	if (!local_map) {
 		idmap_reg_tdb(&local_map);
-		local_map->init();
+		if (NT_STATUS_IS_ERR(local_map->init())) {
+			DEBUG(0, ("idmap_init: could not load or create local backend!\n"));
+			return False;
+		}
 	}
 	
 	if (!remote_map && remote_backend && *remote_backend != 0) {
-		DEBUG(3, ("load_methods: using '%s' as remote backend\n", remote_backend));
+		DEBUG(3, ("idmap_init: using '%s' as remote backend\n", remote_backend));
 		
 		remote_map = get_methods(remote_backend);
 		if (!remote_map) {
-			DEBUG(0, ("load_methods: could not load remote backend '%s'\n", remote_backend));
+			DEBUG(0, ("idmap_init: could not load remote backend '%s'\n", remote_backend));
 			return False;
 		}
 		remote_map->init();
diff --git a/source3/sam/idmap_tdb.c b/source3/sam/idmap_tdb.c
index c494cf595f..a43f5824a1 100644
--- a/source3/sam/idmap_tdb.c
+++ b/source3/sam/idmap_tdb.c
@@ -60,7 +60,7 @@ static NTSTATUS db_allocate_id(unid_t *id, int id_type)
 			}
 
 			if (hwm > idmap_state.uid_high) {
-				DEBUG(0, ("idmap Fatal Error: UID range full!!\n"));
+				DEBUG(0, ("idmap Fatal Error: UID range full!! (max: %u)\n", idmap_state.uid_high));
 				return NT_STATUS_UNSUCCESSFUL;
 			}
 
@@ -75,7 +75,7 @@ static NTSTATUS db_allocate_id(unid_t *id, int id_type)
 			}
 
 			if (hwm > idmap_state.gid_high) {
-				DEBUG(0, ("idmap Fatal Error: GID range full!!\n"));
+				DEBUG(0, ("idmap Fatal Error: GID range full!! (max: %u)\n", idmap_state.gid_high));
 				return NT_STATUS_UNSUCCESSFUL;
 			}
 
@@ -284,6 +284,16 @@ static NTSTATUS db_idmap_init(void)
 		}
 	}
 
+	if (!lp_idmap_uid(&idmap_state.uid_low, &idmap_state.uid_high)) {
+		DEBUG(0, ("idmap uid range missing or invalid\n"));
+		DEBUGADD(0, ("idmap will be unable to map foreign SIDs\n"));
+	}
+	
+	if (!lp_idmap_gid(&idmap_state.gid_low, &idmap_state.gid_high)) {
+		DEBUG(0, ("idmap gid range missing or invalid\n"));
+		DEBUGADD(0, ("idmap will be unable to map foreign SIDs\n"));
+	}
+	
 	return NT_STATUS_OK;
 }
 
diff --git a/source3/smbd/uid.c b/source3/smbd/uid.c
index 0fa65f47ca..0b67b53c71 100644
--- a/source3/smbd/uid.c
+++ b/source3/smbd/uid.c
@@ -873,6 +873,8 @@ BOOL sid_to_uid(const DOM_SID *psid, uid_t *puid, enum SID_NAME_USE *sidtype)
 
 	if (sid_compare_domain(get_global_sam_sid(), psid) == 0) {
 		BOOL result;
+
+		DEBUG(10,("sid_to_uid: sid is local [%s]\n", sid_string_static(get_global_sam_sid())));
 		become_root();
 		result = local_sid_to_uid(puid, psid, sidtype);
 		unbecome_root();
-- 
cgit 


From d97d6240e4a4f16339522e4d8e3c8bc250579519 Mon Sep 17 00:00:00 2001
From: Simo Sorce 
Date: Sat, 19 Apr 2003 15:32:16 +0000
Subject: use gid_t for gids not uid_t (This used to be commit
 dd8009bf599a6111440cd807dcc022039f19de15)

---
 source3/smbd/posix_acls.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source3/smbd/posix_acls.c b/source3/smbd/posix_acls.c
index d4d966a636..a38acc437d 100644
--- a/source3/smbd/posix_acls.c
+++ b/source3/smbd/posix_acls.c
@@ -2593,7 +2593,7 @@ BOOL set_nt_acl(files_struct *fsp, uint32 security_info_sent, SEC_DESC *psd)
 	 * Do we need to chown ?
 	 */
 
-	if (((user != (uid_t)-1) && (orig_uid != user)) || (( grp != (uid_t)-1) && (orig_gid != grp)))
+	if (((user != (uid_t)-1) && (orig_uid != user)) || (( grp != (gid_t)-1) && (orig_gid != grp)))
 		need_chown = True;
 
 	/*
-- 
cgit 


From e02a3f233611bb358a960822a83b4d1ad45eca13 Mon Sep 17 00:00:00 2001
From: Simo Sorce 
Date: Sat, 19 Apr 2003 15:40:32 +0000
Subject: some readline completion exancements still need working, does not
 complete remote names yet (This used to be commit
 625eee8e03c3905a245e078ef9f1c26200e33d7c)

---
 source3/client/client.c | 187 ++++++++++++++++++++++++++++++++++++++++++------
 source3/lib/readline.c  |  24 +++++++
 2 files changed, 188 insertions(+), 23 deletions(-)

diff --git a/source3/client/client.c b/source3/client/client.c
index b6c4b704a9..167f91ae16 100644
--- a/source3/client/client.c
+++ b/source3/client/client.c
@@ -2215,40 +2215,181 @@ static int process_command_string(char *cmd)
 	return rc;
 }	
 
-/****************************************************************************
-handle completion of commands for readline
-****************************************************************************/
-static char **completion_fn(char *text, int start, int end)
-{
 #define MAX_COMPLETIONS 100
-	char **matches;
-	int i, count=0;
 
-	/* for words not at the start of the line fallback to filename completion */
-	if (start) return NULL;
+typedef struct {
+	pstring dirmask;
+	char **matches;
+	int count, samelen;
+	const char *text;
+	int len;
+} completion_remote_t;
 
-	matches = (char **)malloc(sizeof(matches[0])*MAX_COMPLETIONS);
-	if (!matches) return NULL;
+static void completion_remote_filter(file_info *f, const char *mask, void *state)
+{
+	completion_remote_t *info = (completion_remote_t *)state;
 
-	matches[count++] = strdup(text);
-	if (!matches[0]) return NULL;
+	if ((info->count < MAX_COMPLETIONS - 1) && (strncmp(info->text, f->name, info->len) == 0) && (strcmp(f->name, ".") != 0) && (strcmp(f->name, "..") != 0)) {
+		if ((info->dirmask[0] == 0) && !(f->mode & aDIR))
+			info->matches[info->count] = strdup(f->name);
+		else {
+			pstring tmp;
 
-	for (i=0;commands[i].fn && count < MAX_COMPLETIONS-1;i++) {
-		if (strncmp(text, commands[i].name, strlen(text)) == 0) {
-			matches[count] = strdup(commands[i].name);
-			if (!matches[count]) return NULL;
-			count++;
+			if (info->dirmask[0] != 0)
+				pstrcpy(tmp, info->dirmask);
+			else
+				tmp[0] = 0;
+			pstrcat(tmp, f->name);
+			if (f->mode & aDIR)
+				pstrcat(tmp, "/");
+			info->matches[info->count] = strdup(tmp);
 		}
+		if (info->matches[info->count] == NULL)
+			return;
+		if (f->mode & aDIR)
+			smb_readline_ca_char(0);
+
+		if (info->count == 1)
+			info->samelen = strlen(info->matches[info->count]);
+		else
+			while (strncmp(info->matches[info->count], info->matches[info->count-1], info->samelen) != 0)
+				info->samelen--;
+		info->count++;
 	}
+}
+
+static char **remote_completion(const char *text, int len)
+{
+	pstring dirmask;
+	int i;
+	completion_remote_t info = { "", NULL, 1, len, text, len };
+
+	if (len >= PATH_MAX)
+		return(NULL);
+
+	info.matches = (char **)malloc(sizeof(info.matches[0])*MAX_COMPLETIONS);
+	if (!info.matches) return NULL;
+	info.matches[0] = NULL;
+
+	for (i = len-1; i >= 0; i--)
+		if ((text[i] == '/') || (text[i] == '\\'))
+			break;
+	info.text = text+i+1;
+	info.samelen = info.len = len-i-1;
 
-	if (count == 2) {
-		SAFE_FREE(matches[0]);
-		matches[0] = strdup(matches[1]);
+	if (i > 0) {
+		strncpy(info.dirmask, text, i+1);
+		info.dirmask[i+1] = 0;
+		snprintf(dirmask, sizeof(dirmask), "%s%*s*", cur_dir, i-1, text);
+	} else
+		snprintf(dirmask, sizeof(dirmask), "%s*", cur_dir);
+
+	if (cli_list(cli, dirmask, aDIR | aSYSTEM | aHIDDEN, completion_remote_filter, &info) < 0)
+		goto cleanup;
+
+	if (info.count == 2)
+		info.matches[0] = strdup(info.matches[1]);
+	else {
+		info.matches[0] = malloc(info.samelen+1);
+		if (!info.matches[0])
+			goto cleanup;
+		strncpy(info.matches[0], info.matches[1], info.samelen);
+		info.matches[0][info.samelen] = 0;
 	}
-	matches[count] = NULL;
-	return matches;
+	info.matches[info.count] = NULL;
+	return info.matches;
+
+cleanup:
+	for (i = 0; i < info.count; i++)
+		free(info.matches[i]);
+	free(info.matches);
+	return NULL;
 }
 
+static char **completion_fn(const char *text, int start, int end)
+{
+	smb_readline_ca_char(' ');
+
+	if (start) {
+		const char *buf, *sp;
+		int i;
+		char compl_type;
+
+		buf = smb_readline_get_line_buffer();
+		if (buf == NULL)
+			return NULL;
+		
+		sp = strchr(buf, ' ');
+		if (sp == NULL)
+			return NULL;
+		
+		for (i = 0; commands[i].name; i++)
+			if ((strncmp(commands[i].name, text, sp - buf) == 0) && (commands[i].name[sp - buf] == 0))
+				break;
+		if (commands[i].name == NULL)
+			return NULL;
+
+		while (*sp == ' ')
+			sp++;
+
+		if (sp == (buf + start))
+			compl_type = commands[i].compl_args[0];
+		else
+			compl_type = commands[i].compl_args[1];
+
+		if (compl_type == COMPL_REMOTE)
+			return remote_completion(text, end - start);
+		else /* fall back to local filename completion */
+			return NULL;
+	} else {
+		char **matches;
+		int i, len, samelen, count=1;
+
+		matches = (char **)malloc(sizeof(matches[0])*MAX_COMPLETIONS);
+		if (!matches) return NULL;
+		matches[0] = NULL;
+
+		len = strlen(text);
+		for (i=0;commands[i].fn && count < MAX_COMPLETIONS-1;i++) {
+			if (strncmp(text, commands[i].name, len) == 0) {
+				matches[count] = strdup(commands[i].name);
+				if (!matches[count])
+					goto cleanup;
+				if (count == 1)
+					samelen = strlen(matches[count]);
+				else
+					while (strncmp(matches[count], matches[count-1], samelen) != 0)
+						samelen--;
+				count++;
+			}
+		}
+
+		switch (count) {
+		case 0:	/* should never happen */
+		case 1:
+			goto cleanup;
+		case 2:
+			matches[0] = strdup(matches[1]);
+			break;
+		default:
+			matches[0] = malloc(samelen+1);
+			if (!matches[0])
+				goto cleanup;
+			strncpy(matches[0], matches[1], samelen);
+			matches[0][samelen] = 0;
+		}
+		matches[count] = NULL;
+		return matches;
+
+cleanup:
+		while (i >= 0) {
+			free(matches[i]);
+			i--;
+		}
+		free(matches);
+		return NULL;
+	}
+}
 
 /****************************************************************************
 make sure we swallow keepalives during idle time
diff --git a/source3/lib/readline.c b/source3/lib/readline.c
index 8b90c32c7f..ceb02ef749 100644
--- a/source3/lib/readline.c
+++ b/source3/lib/readline.c
@@ -115,6 +115,29 @@ char *smb_readline(char *prompt, void (*callback)(void),
 	return smb_readline_replacement(prompt, callback, completion_fn);
 }
 
+/****************************************************************************
+ * return line buffer text
+ ****************************************************************************/
+const char *smb_readline_get_line_buffer(void)
+{
+#if defined(HAVE_LIBREADLINE)
+	return rl_line_buffer;
+#else
+	return NULL;
+#endif
+}
+
+
+/****************************************************************************
+ * set completion append character
+ ***************************************************************************/
+void smb_readline_ca_char(char c)
+{
+#if defined(HAVE_LIBREADLINE)
+	rl_completion_append_character = c;
+#endif
+}
+
 /****************************************************************************
 history
 ****************************************************************************/
@@ -135,3 +158,4 @@ int cmd_history(void)
 
 	return 0;
 }
+
-- 
cgit 


From ef423a45209562436c83925b9dabb2aadb4ab72b Mon Sep 17 00:00:00 2001
From: Richard Sharpe 
Date: Sat, 19 Apr 2003 18:36:54 +0000
Subject: Squelch some warnings, and move a bit of code around to make some
 future things easier ... now on to more functionality.

Hope Jerry fixes the breakage, BTW :-)
(This used to be commit c7d39a7426e5970b15ece89737d2f0ba3d5c0835)
---
 source3/utils/editreg.c | 19 +++++++++++--------
 1 file changed, 11 insertions(+), 8 deletions(-)

diff --git a/source3/utils/editreg.c b/source3/utils/editreg.c
index 1b7b3d587d..d98076d8f9 100644
--- a/source3/utils/editreg.c
+++ b/source3/utils/editreg.c
@@ -1264,12 +1264,6 @@ int nt_free_regf(REGF *regf)
   if (regf->regfile_name) free(regf->regfile_name);
   if (regf->outfile_name) free(regf->outfile_name);
 
-  /* Free the mmap'd area */
-
-  if (regf->base) munmap(regf->base, regf->sbuf.st_size);
-  regf->base = NULL;
-  close(regf->fd);    /* Ignore the error :-) */
-
   nt_delete_reg_key(regf->root, False); /* Free the tree */
   free(regf->sk_map);
   regf->sk_count = regf->sk_map_size = 0;
@@ -1892,7 +1886,7 @@ REG_KEY *nt_get_key_tree(REGF *regf, NK_HDR *nk_hdr, int size, REG_KEY *parent)
   own = (REG_KEY *)LOCN(regf->base, own_off);
 
   if (verbose) fprintf(stdout, "  Owner offset: %0X, Our Offset: %0X\n", 
-		       own, nk_hdr);
+		       (unsigned int)own, (unsigned int)nk_hdr);
 
   /* 
    * We should verify that the owner field is correct ...
@@ -2017,6 +2011,15 @@ int nt_load_registry(REGF *regf)
 
   assert(regf->root != NULL);
 
+  /*
+   * Unmap the registry file, as we might want to read in another
+   * tree etc.
+   */
+
+  if (regf->base) munmap(regf->base, regf->sbuf.st_size);
+  regf->base = NULL;
+  close(regf->fd);    /* Ignore the error :-) */
+
   return 1;
 }
 
@@ -2504,7 +2507,7 @@ CMD *regedit4_get_cmd(int fd)
   cmd->cmd = CMD_NONE;
   cmd->key = NULL;
   cmd->val_spec_list = cmd->val_spec_last = NULL;
-  while (cl = get_cmd_line(fd)) {
+  while ((cl = get_cmd_line(fd))) {
 
     strip_comment(cl);     /* remove anything beyond a comment char */
     trim_trailing_spaces(cl);
-- 
cgit 


From 2029f3028cddaa0f2866092416bf49b6bfd8513a Mon Sep 17 00:00:00 2001
From: Volker Lendecke 
Date: Sat, 19 Apr 2003 18:45:03 +0000
Subject: Address gcc warnings.

I could not fix the "passing arg 5 of `ldap_search_s'" completely with
gcc -Wall. A non-developer compile does not complain though.

Volker
(This used to be commit dcbbbd66a9be799998476701a9e1059c14e4f061)
---
 source3/lib/ldap.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source3/lib/ldap.c b/source3/lib/ldap.c
index d0e72c4844..917e03a871 100644
--- a/source3/lib/ldap.c
+++ b/source3/lib/ldap.c
@@ -503,7 +503,7 @@ int smb_ldap_search(struct smb_ldap_privates *ldap_state,
 			continue;
 		
 		rc = ldap_search_s(ldap_state->ldap_struct, base, scope, 
-				   filter, attrs, attrsonly, res);
+				   filter, (char **)attrs, attrsonly, res);
 	}
 	
 	if (rc == LDAP_SERVER_DOWN) {
-- 
cgit 


From 2594944aad476dcf7355f5bda096ad0f426c37df Mon Sep 17 00:00:00 2001
From: Richard Sharpe 
Date: Sat, 19 Apr 2003 22:08:25 +0000
Subject: Some more work added ... (This used to be commit
 31ded623b1817156b247170130237c1e5fd67a5b)

---
 source3/utils/editreg.c | 25 ++++++++++++++++++++-----
 1 file changed, 20 insertions(+), 5 deletions(-)

diff --git a/source3/utils/editreg.c b/source3/utils/editreg.c
index d98076d8f9..43cd14d57d 100644
--- a/source3/utils/editreg.c
+++ b/source3/utils/editreg.c
@@ -310,7 +310,7 @@ Hope this helps....  (Although it was "fun" for me to uncover this things,
 
 #define False 0
 #define True 1
-#define REG_KEY_LIST_SIZE 10;
+#define REG_KEY_LIST_SIZE 10
 
 static int verbose = 0;
 static int print_security = 0;
@@ -990,13 +990,22 @@ REG_KEY *nt_create_reg_key1(char *name, REG_KEY *parent)
 }
 
 REG_KEY *nt_add_reg_key(REG_KEY *key, char *name, int create);
-REG_KEY *nt_add_reg_key_list(KEY_LIST *list, char * name, REG_KEY *parent, int create)
+REG_KEY *nt_add_reg_key_list(REG_KEY *key, char * name, int create)
 {
   int i;
   REG_KEY *ret;
+  KEY_LIST *list;
   char *lname, *c1, *c2;
 
-  if (!list || !name || !*name) return NULL;
+  if (!key || !name || !*name) return NULL;
+  
+  list = key->sub_keys;
+  if (!list) { /* Create an empty list */
+
+    list = (KEY_LIST *)malloc(sizeof(KEY_LIST) + (REG_KEY_LIST_SIZE - 1) * sizeof(REG_KEY *));
+    list->key_count = list->max_keys = 0;
+
+  }
 
   for (i = 0; i < list->key_count; i++) {
     if ((ret = nt_add_reg_key(list->keys[i], name, create)))
@@ -1022,7 +1031,13 @@ REG_KEY *nt_add_reg_key_list(KEY_LIST *list, char * name, REG_KEY *parent, int c
     list->key_count++;
   }
   else { /* Create more space in the list ... */
+    if (!(list = (KEY_LIST *)realloc(list, sizeof(KEY_LIST) + 
+				     (list->max_keys + REG_KEY_LIST_SIZE - 1) 
+				     * sizeof(REG_KEY *))));
+      goto error;
 
+    list->max_keys += REG_KEY_LIST_SIZE;
+    list->key_count++;
   }
 
   return NULL;
@@ -1063,7 +1078,7 @@ REG_KEY *nt_add_reg_key(REG_KEY *key, char *name, int create)
   if (strcmp(c1, key->name) != 0)
     goto error;
   
-  tmp = nt_add_reg_key_list(key->sub_keys, c2, key, True);
+  tmp = nt_add_reg_key_list(key, c2, True);
   free(lname);
   return tmp;
   
@@ -1782,7 +1797,7 @@ KEY_LIST *process_lf(REGF *regf, LF_HDR *lf_hdr, int size, REG_KEY *parent)
 }
 
 /*
- * This routine is passed a NK_HDR pointer and retrieves the entire tree
+ * This routine is passed an NK_HDR pointer and retrieves the entire tree
  * from there down. It returns a REG_KEY *.
  */
 REG_KEY *nt_get_key_tree(REGF *regf, NK_HDR *nk_hdr, int size, REG_KEY *parent)
-- 
cgit 


From 3291b9290dbedc77b1fae9d8e13fd86d60c0afc2 Mon Sep 17 00:00:00 2001
From: John Terpstra 
Date: Sat, 19 Apr 2003 22:32:53 +0000
Subject: Updates and additions. (This used to be commit
 9b35377f0cf5022519385a2b70237c05c7978158)

---
 docs/docbook/projdoc/AdvancedNetworkAdmin.sgml |  15 ++
 docs/docbook/projdoc/NT4Migration.sgml         | 233 ++++++++++++++++++++++---
 docs/docbook/projdoc/passdb.sgml               |  33 +++-
 3 files changed, 248 insertions(+), 33 deletions(-)

diff --git a/docs/docbook/projdoc/AdvancedNetworkAdmin.sgml b/docs/docbook/projdoc/AdvancedNetworkAdmin.sgml
index 138095e02c..dc2a78f5a6 100644
--- a/docs/docbook/projdoc/AdvancedNetworkAdmin.sgml
+++ b/docs/docbook/projdoc/AdvancedNetworkAdmin.sgml
@@ -269,8 +269,23 @@ Those wishing to use more elaborate or capable logon processing system should ch
 
 	http://www.craigelachie.org/rhacer/ntlogon
 	http://www.kixtart.org
+	http://support.microsoft.com/default.asp?scid=kb;en-us;189105
 
 
+
+Adding printers without user intervention
+
+
+Printers may be added automatically during logon script processing through the use of:
+
+
+	rundll32 printui.dll,PrintUIEntry /?
+
+
+See the documentation in the Microsoft knowledgebase article no: 189105 referred to above.
+
+
+
 
 
 
diff --git a/docs/docbook/projdoc/NT4Migration.sgml b/docs/docbook/projdoc/NT4Migration.sgml
index 3640c78942..6e40709081 100644
--- a/docs/docbook/projdoc/NT4Migration.sgml
+++ b/docs/docbook/projdoc/NT4Migration.sgml
@@ -74,70 +74,253 @@ MS Windows 2000 and beyond (with or without Active Directory services).
 
 
 
-What are the features the Samba-3 can NOT provide?
+What are the features that Samba-3 can NOT provide?
 
 
-
-    Active Directory Server
-    Group Policy Objects (in Active Direcrtory)
-    Machine Policy objects
-    Logon Scripts in Active Directorty
-    Software Application and Access Controls in Active Directory
-
+
+
+	Active Directory Server
+
+
+	Group Policy Objects (in Active Direcrtory)
+
+
+	Machine Policy objects
+
+
+	Logon Scripts in Active Directorty
+
+
+	Software Application and Access Controls in Active Directory
+
+
+
+
+The features that Samba-3 DOES provide and that may be of compelling interest to your site
+includes:
+
+
+
+
+	Lower Cost of Ownership
+
+
+	Global availability of support with no strings attached
+
+
+	Dynamic SMB Servers (ie:Can run more than one server per Unix/Linux system)
+
+
+	Creation of on-the-fly logon scripts
+
+
+	Creation of on-the-fly Policy Files
+
+
+	Greater Stability, Reliability, Performance and Availability
+
+
+	Manageability via an ssh connection
+
+
+	Flexible choices of back-end authentication technologies (tdbsam, ldapsam, mysqlsam)
+
+
+	Ability to implement a full single-signon architecture
+
+
+	Ability to distribute authentication systems for absolute minimum wide are network bandwidth demand
+
+
+
+
+Before migrating a network from MS Windows NT4 to Samba-3 it is vital that all necessary factors are
+considered. Users should be educated about changes they may experience so that the change will be a
+welcome one and not become an obstacle to the work they need to do. The following are some of the
+factors that will go into a successful migration:
+
+
+
+Domain Layout
+
+
+Samba-3 can be configured as a domain controller, a back-up domain controller (probably best called
+a secondary controller), a domain member, or as a stand-alone server. The Windows network security
+domain context should be sized and scoped before implementation. Particular attention needs to be
+paid to the location of the primary domain controller (PDC) as well as backup controllers (BDCs).
+It should be noted that one way in which Samba-3 differs from Microsoft technology is that if one
+chooses to use an LDAP authentication backend then the same database can be used by several different
+domains. This means that in a complex organisation there can be a single LDAP database, that itself
+can be distributed, that can simultaneously serve multiple domains (that can also be widely distributed).
+
+
+
+It is recommended that from a design perspective, the number of users per server, as well as the number
+of servers, per domain should be scaled according to needs and should also consider server capacity
+and network bandwidth.
+
+
+
+A physical network segment may house several domains, each of which may span multiple network segments.
+Where domains span routed network segments it is most advisable to consider and test the performance
+implications of the design and layout of a network. A Centrally located domain controller that is being
+designed to server mulitple route network segments may result in severe performance problems if the
+response time (eg: ping timing) between the remote segment and the PDC is more than 100 ms. In situations
+where the delay is too long it is highly recommended to locate a backup controller (BDC) to serve as
+the local authentication and access control server.
+
+
+
+
+Server Share and Directory Layout
+
+
+There are few cardinal rules to effective network design that can be broken with impunity.
+The most important rule of effective network management is that simplicity is king in every
+well controlled network. Every part of the infrastructure must be managed, the more complex
+it is, the greater will be the demand of keeping systems secure and functional.
+
+
+
+The nature of the data that must be stored needs to be born in mind when deciding how many
+shares must be created. The physical disk space layout should also be taken into account
+when designing where share points will be created. Keep in mind that all data needs to be
+backed up, thus the simpler the disk layout the easier it will be to keep track of what must
+be backed up to tape or other off-line storage medium. Always plan and implement for minimum
+maintenance. Leave nothing to chance in your design, above all, do not leave backups to chance:
+Backup and test, validate every backup, create a disaster recovery plan and prove that it works.
+
+
+
+Users should be grouped according to data access control needs. File and directory access 
+is best controlled via group permissions and the use of the "sticky bit" on group controlled
+directories may substantially avoid file access complaints from samba share users.
+
+
+
+Many network administrators who are new to the game will attempt to use elaborate techniques
+to set access controls, on files, directories, shares, as well as in share definitions.
+There is the ever present danger that that administrator's successor will not understand the
+complex mess that has been inherited. Remember, apparent job security through complex design
+and implementation may ultimately cause loss of operations and downtime to users as the new
+administrator learns to untangle your web. Keep access controls simple and effective and
+make sure that users will never be interrupted by the stupidity of complexity.
+
+
+
+
+Logon Scripts
+
+
+Please refer to the section of this document on Advanced Network Adminsitration for information
+regarding the network logon script options for Samba-3. Logon scripts can help to ensure that
+all users gain share and printer connections they need.
+
+
+
+Logon scripts can be created on-the-fly so that all commands executed are specific to the
+rights and privilidges granted to the user. The preferred controls should be affected through
+group membership so that group information can be used to custom create a logong script using
+the root preexec parameters to the NETLOGON share.
+
+
+
+Some sites prefer to use a tool such as kixstart to establish a controlled
+user environment. In any case you may wish to do a google search for logon script process controls.
+In particular, you may wish to explore the use of the Microsoft knowledgebase article KB189105 that
+deals with how to add printers without user intervention via the logon script process.
+
+
+
+
+Profile Migration/Creation
+
+
+User and Group Profiles may be migrated using the tools described in the section titled Desktop Profile
+Management.
+
+
+
+Profiles may also be managed using the Samba-3 tool profiles. This tool allows
+the MS Windows NT style security identifiers (SIDs) that are stored inside the profile NTuser.DAT file
+to be changed to the SID of the Samba-3 domain.
+
+
+
+
+User and Group Accounts
+
+
+It is possible to migrate all account settings from an MS Windows NT4 domain to Samba-3. Before
+ attempting to migrate user and group accounts it is STRONGLY advised to create in Samba-3 the
+groups that are present on the MS Windows NT4 domain AND to connect these to
+suitable Unix/Linux groups. Following this simple advice will mean that all user and group attributes
+should migrate painlessly.
+
+
 
 
+
 
 Steps In Migration Process
 
 
 This is not a definitive ste-by-step process yet - just a place holder so the info 
 is not lost.
+
 
-1. You will have an NT4 PDC that has the users, groups, policies and profiles to be migrated
+
+
+You will have an NT4 PDC that has the users, groups, policies and profiles to be migrated
+
 
-2. Samba-3 set up as a DC with netlogon share, profile share, etc.
+
+Samba-3 set up as a DC with netlogon share, profile share, etc.
+
+
 
-3. Process:
-	a. Create a BDC account for the samba server using NT Server Manager
+
+Process:
+	Create a BDC account for the samba server using NT Server Manager
 		- Samba must NOT be running
 
-	b. rpcclient NT4PDC -U Administrator%passwd
+	rpcclient NT4PDC -U Administrator%passwd
 		lsaquery
 
 		Note the SID returned by step b.
 
-	c. net getsid -S NT4PDC -w DOMNAME -U Administrator%passwd
+	net getsid -S NT4PDC -w DOMNAME -U Administrator%passwd
 
 		Note the SID in step c.
 
-	d. net getlocalsid
+	net getlocalsid
 
 		Note the SID, now check that all three SIDS reported are the same!
 
-	e. net rpc join -S NT4PDC -w DOMNAME -U Administrator%passwd
+	net rpc join -S NT4PDC -w DOMNAME -U Administrator%passwd
 
-	f. net rpc vampire -S NT4PDC -U administrator%passwd
+	net rpc vampire -S NT4PDC -U administrator%passwd
 
-	g. pdbedit -l
+	pdbedit -l
 
 		Note - did the users migrate?
 
-	h. initGrps.sh DOMNAME
+	initGrps.sh DOMNAME
 
-	i. smbgroupedit -v
+	smbgroupedit -v
 
 		Now check that all groups are recognised
 
-	j. net rpc campire -S NT4PDC -U administrator%passwd
+	net rpc campire -S NT4PDC -U administrator%passwd
 
-	k. pdbedit -lv
+	pdbedit -lv
 
 		Note - check that all group membership has been migrated.
+
 
-
+
 Now it is time to migrate all the profiles, then migrate all policy files.
-
-Moe later.
+More later.
 
 
 
diff --git a/docs/docbook/projdoc/passdb.sgml b/docs/docbook/projdoc/passdb.sgml
index 0de0376df8..776c79f095 100644
--- a/docs/docbook/projdoc/passdb.sgml
+++ b/docs/docbook/projdoc/passdb.sgml
@@ -341,8 +341,9 @@ include:
 
 The second item can be accomplished by using LDAP NSS and PAM modules.  LGPL
 versions of these libraries can be obtained from PADL Software
-(http://www.padl.com/).  However,
-the details of configuring these packages are beyond the scope of this document.
+(http://www.padl.com/). More
+information about the configuration of these packages may be found at "LDAP,
+System Administration; Gerald Carter, O'Reilly; Chapter 6: Replacing NIS".
 
 
 
@@ -375,7 +376,7 @@ Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in
 
 
 
-objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top STRUCTURAL
+objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top AUXILIARY
      DESC 'Samba Account'
      MUST ( uid $ rid )
      MAY  ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $
@@ -476,6 +477,11 @@ index rid           eq
 ##index gidNumber     eq
 ##index cn            eq
 ##index memberUid     eq
+
+# (both fetched via ldapsearch):
+index   primaryGroupID  eq
+index   displayName     pres,eq
+
 
 
 
@@ -485,16 +491,20 @@ index rid           eq
 
 
 The following parameters are available in smb.conf only with --with-ldapsam
-was included with compiling Samba.
+was included when compiling Samba.
 
 
 
+        passdb backend [ldapsam|ldapsam_nua]:url
 	ldap ssl
-	ldap server
 	ldap admin dn
 	ldap suffix
 	ldap filter
 	ldap port
+        ldap machine suffix
+        ldap user suffix
+        ldap delete dn
+
 
 
 
@@ -521,13 +531,20 @@ use with an LDAP directory could appear as
      # changes, this password will need to be reset.
      ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
 
-     #  specify the LDAP server's hostname (defaults to locahost)
-     ldap server = ahab.samba.org
-
      # Define the SSL option when connecting to the directory
      # ('off', 'start tls', or 'on' (default))
      ldap ssl = start tls
 
+     passdb backend ldapsam:ldap://ahab.samba.org
+
+     # smbpasswd -x delete the entire dn-entry
+     ldap delete dn = no
+
+     # the machine and user suffix added to the base suffix
+     # wrote WITHOUT quotes. NULL siffixes by default
+     ldap user suffix = ou=People
+     ldap machine suffix = ou=Systems
+
      # define the port to use in the LDAP session (defaults to 636 when
      # "ldap ssl = on")
      ldap port = 389
-- 
cgit 


From e94801be2d6fd61e3466cbbf43b202a12664a0a9 Mon Sep 17 00:00:00 2001
From: John Terpstra 
Date: Sat, 19 Apr 2003 22:38:47 +0000
Subject: Fix typo. (This used to be commit
 a4f89aabfa28a6763008a6eab944ad11dabf5e4c)

---
 docs/docbook/projdoc/NT4Migration.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docbook/projdoc/NT4Migration.sgml b/docs/docbook/projdoc/NT4Migration.sgml
index 6e40709081..385aa7810b 100644
--- a/docs/docbook/projdoc/NT4Migration.sgml
+++ b/docs/docbook/projdoc/NT4Migration.sgml
@@ -253,7 +253,7 @@ to be changed to the SID of the Samba-3 domain.
 
 It is possible to migrate all account settings from an MS Windows NT4 domain to Samba-3. Before
  attempting to migrate user and group accounts it is STRONGLY advised to create in Samba-3 the
-groups that are present on the MS Windows NT4 domain AND to connect these to
+groups that are present on the MS Windows NT4 domain AND to connect these to
 suitable Unix/Linux groups. Following this simple advice will mean that all user and group attributes
 should migrate painlessly.
 
-- 
cgit 


From 95b2ff81b5dcf7f090a36f8044b908b34f7579f1 Mon Sep 17 00:00:00 2001
From: John Terpstra 
Date: Sun, 20 Apr 2003 00:26:50 +0000
Subject: More update stuff - not finished (ofcourse!) (This used to be commit
 5d72c6cfca41accc783eda166d8b9154d21f4aec)

---
 docs/docbook/projdoc/NT4Migration.sgml | 103 +++++++++++++++++++++++++++++++++
 1 file changed, 103 insertions(+)

diff --git a/docs/docbook/projdoc/NT4Migration.sgml b/docs/docbook/projdoc/NT4Migration.sgml
index 385aa7810b..1a31def2fe 100644
--- a/docs/docbook/projdoc/NT4Migration.sgml
+++ b/docs/docbook/projdoc/NT4Migration.sgml
@@ -326,6 +326,109 @@ More later.
 
 
 
+
+Migration Options
+
+
+There are 3 major Site Types:
+
+
+
+<= 50 Users
+Want simple conversion with NO pain
+50 - 250 Users
+Want new features, can manage some in-house complexity
+Large Scale Sites
+Solution / Implementation MUST scale well, complex needs
+Cross departmental decision process
+Local expertise in most areas
+Planning for Success
+Decide which approach is needed - 3 Choices
+Simple Conversion (total replacement)
+Upgraded Conversion (could be one of integration)
+Complete Redesign (completely new solution)
+Take sufficient time
+Avoid Panic
+Test ALL assumptions
+Test full roll-out program, including workstation deployment
+Simple Conversion
+Make use of minimal OS specific features
+Can use No Unix Accounts Option
+Suck all accounts from NT4 into Samba-3
+Make least number of operational changes
+Take least amount of time to migrate
+Live versus Isolated Conversion
+Integrate Samba-3 then migrate while users are active
+Change of control (ie: swap out)
+Upgraded Conversion
+Translate NT4 features to new host OS features
+Copy and improve
+Old environment to Samba-3
+Make progressive improvements
+Minimise user impact
+Macimise functionality
+Take advantage of lower maintenance opportunity
+Complete Network Redesign
+Decide
+Authentication Regime (database locate and access)
+Desktop Management Methods
+Better Control of Desktops / Users
+Identify Needs for:
+Manageability, Scalability, Security, Availability
+Samba Implementation Choices
+Authentication database back end
+Winbind (external Samba or NT4/200x server)
+Can use pam_mkhomedir.so to auto-create home dirs
+External server could use Active Directory or NT4 Domain
+Database type
+smbpasswd, tdbsam, ldapsam, MySQLsam
+With local accounts or with No Unix Accounts (NUA option)
+Samba Implementation Choice - II
+Access Control Points
+On the Share itself (Use NT4 Server Manager)
+On the file system
+Unix permissions on files and directories
+Posix ACLs enablement in file system?
+Through Samba share parameters
+Not recommended - except as only resort
+Samba Implementation Choice - III
+Policies (migrate or create new ones)
+Group Policy Editor (NT4)
+Watch out for Tattoo effect
+User and Group Profiles
+Platform specific so use platform tool to change from a Local to a Roaming profile
+Can use new profiles tool to change SIDs (NTUser.DAT)
+Logon Scripts (Know how they work)
+Samba Implementation Choices - IV
+User and Group mapping to Unix/Linux
+username map facility may be needed
+Use smbgroupedit to connect NT4 groups to Unix groups
+Use pdbedit to set/change user configuration
+NOTE:
+If migrating to LDAP back end it may be easier to dump initial LDAP database to LDIF, then edit, then reload into LDAP
+Samba Implementation Choices - V
+OS specific scripts / programs may be needed
+Add / delete Users
+Note OS limits on size of name (Linux 8 chars)
+NT4 up to 254 chars
+Add / delete machines
+Applied only to domain members (note up to 16 chars)
+Add / delete Groups
+Note OS limits on size and nature
+Linux limit is 16 char, no spaces and no upper case chars (groupadd)
+Migration Tools
+Domain Control (NT4 Style)
+Profiles, Policies, Access Controls, Security
+Migration Tools
+Samba: net, rpcclient, smbpasswd, pdbedit, smbgroupedit, profiles
+Windows: NT4 Domain User Manager, Server Manager (NEXUS)
+Authentication
+New SAM back end (smbpasswd, tdbsam, ldapsam, mysqlsam)
+With of without Unix Accounts (NUA)
+
+
+
+
 
 Managing Samba-3 Domain Control
 
-- 
cgit 


From fdd5d9739a25209b091153a171352a9addcffc0f Mon Sep 17 00:00:00 2001
From: Richard Sharpe 
Date: Sun, 20 Apr 2003 02:30:24 +0000
Subject: MOre functionality ... got to test it. (This used to be commit
 e3c4f8c91394eecc8c77bbf0f9685cdb18c617b1)

---
 source3/utils/editreg.c | 26 +++++++++++++++++++++++---
 1 file changed, 23 insertions(+), 3 deletions(-)

diff --git a/source3/utils/editreg.c b/source3/utils/editreg.c
index 43cd14d57d..2c8f543690 100644
--- a/source3/utils/editreg.c
+++ b/source3/utils/editreg.c
@@ -993,7 +993,7 @@ REG_KEY *nt_add_reg_key(REG_KEY *key, char *name, int create);
 REG_KEY *nt_add_reg_key_list(REG_KEY *key, char * name, int create)
 {
   int i;
-  REG_KEY *ret;
+  REG_KEY *ret = NULL, *tmp = NULL;
   KEY_LIST *list;
   char *lname, *c1, *c2;
 
@@ -1003,7 +1003,8 @@ REG_KEY *nt_add_reg_key_list(REG_KEY *key, char * name, int create)
   if (!list) { /* Create an empty list */
 
     list = (KEY_LIST *)malloc(sizeof(KEY_LIST) + (REG_KEY_LIST_SIZE - 1) * sizeof(REG_KEY *));
-    list->key_count = list->max_keys = 0;
+    list->key_count = 0;
+    list->max_keys = REG_KEY_LIST_SIZE;
 
   }
 
@@ -1040,7 +1041,26 @@ REG_KEY *nt_add_reg_key_list(REG_KEY *key, char * name, int create)
     list->key_count++;
   }
 
-  return NULL;
+  /*
+   * add the new key at the new slot 
+   * FIXME: Sort the list someday
+   */
+
+  /*
+   * We want to create the key, and then do the rest
+   */
+
+  tmp = (REG_KEY *)malloc(sizeof(REG_KEY)); 
+
+  bzero(tmp, sizeof(REG_KEY));
+
+  list->keys[list->key_count - 1] = tmp;
+
+  if (c2) {
+    ret = nt_add_reg_key(key, name, True);
+  }
+
+  return ret;
  error:
   if (lname) free(lname);
   return NULL;
-- 
cgit 


From e5f79e7d960277775141f1b7acd4a1f65ac15454 Mon Sep 17 00:00:00 2001
From: Richard Sharpe 
Date: Sun, 20 Apr 2003 04:53:55 +0000
Subject: More functionality, esp around adding keys and inheritance of
 security descriptors etc ... (This used to be commit
 b8e85afefbe52701317632d1c1a446785ed66abf)

---
 source3/utils/editreg.c | 27 ++++++++++++++++++++++++++-
 1 file changed, 26 insertions(+), 1 deletion(-)

diff --git a/source3/utils/editreg.c b/source3/utils/editreg.c
index 2c8f543690..b8670eb8b6 100644
--- a/source3/utils/editreg.c
+++ b/source3/utils/editreg.c
@@ -989,6 +989,18 @@ REG_KEY *nt_create_reg_key1(char *name, REG_KEY *parent)
   return NULL;
 }
 
+/*
+ * We will implement inheritence that is based on what the parent's SEC_DESC
+ * says, but the Owner and Group SIDs can be overwridden from the command line
+ * and additional ACEs can be applied from the command line etc.
+ */
+KEY_SEC_DESC *nt_inherit_security(REG_KEY *key)
+{
+
+  if (!key) return NULL;
+  return key->security;
+}
+
 REG_KEY *nt_add_reg_key(REG_KEY *key, char *name, int create);
 REG_KEY *nt_add_reg_key_list(REG_KEY *key, char * name, int create)
 {
@@ -1054,14 +1066,27 @@ REG_KEY *nt_add_reg_key_list(REG_KEY *key, char * name, int create)
 
   bzero(tmp, sizeof(REG_KEY));
 
+  tmp->name = strdup(c1);
+  if (!tmp->name) goto error;
+  tmp->owner = key;
+  /*
+   * Next, pull security from the parent, but override by with
+   * anything passed in on the command line
+   */
+  tmp->security = nt_inherit_security(key);
+
   list->keys[list->key_count - 1] = tmp;
 
   if (c2) {
-    ret = nt_add_reg_key(key, name, True);
+    ret = nt_add_reg_key(key, c2, True);
   }
 
+  if (lname) free(lname);
+
   return ret;
+
  error:
+  if (tmp) free(tmp);
   if (lname) free(lname);
   return NULL;
 }
-- 
cgit 


From cb8f5d6affaa4be29b2528f6df9bc67aa55291d7 Mon Sep 17 00:00:00 2001
From: Richard Sharpe 
Date: Sun, 20 Apr 2003 08:55:10 +0000
Subject: The code is a bit of a mess right now.

Added code to add keys to the in-momory key tree.
Added code to convert SID strings to SIDs in memory format.
Added code to construct initial security descriptors and to inherit
security descriptors.

A couple of more hours should see the code to add keys and values complete.

Then I have to start on the code to write out a registry :-(
(This used to be commit fc691a9a5e86686ebd0b3bab75a286488ab6ca57)
---
 source3/utils/editreg.c | 197 +++++++++++++++++++++++++++++++++++-------------
 1 file changed, 146 insertions(+), 51 deletions(-)

diff --git a/source3/utils/editreg.c b/source3/utils/editreg.c
index b8670eb8b6..9d155a9a11 100644
--- a/source3/utils/editreg.c
+++ b/source3/utils/editreg.c
@@ -312,6 +312,22 @@ Hope this helps....  (Although it was "fun" for me to uncover this things,
 #define True 1
 #define REG_KEY_LIST_SIZE 10
 
+/*
+ * Structures for dealing with the on-disk format of the registry
+ */
+
+#define IVAL(buf) ((unsigned int) \
+                   (unsigned int)*((unsigned char *)(buf)+3)<<24| \
+                   (unsigned int)*((unsigned char *)(buf)+2)<<16| \
+                   (unsigned int)*((unsigned char *)(buf)+1)<<8| \
+                   (unsigned int)*((unsigned char *)(buf)+0)) 
+
+#define SVAL(buf) ((unsigned short) \
+                   (unsigned short)*((unsigned char *)(buf)+1)<<8| \
+                   (unsigned short)*((unsigned char *)(buf)+0)) 
+
+#define CVAL(buf) ((unsigned char)*((unsigned char *)(buf)))
+
 static int verbose = 0;
 static int print_security = 0;
 
@@ -337,6 +353,8 @@ typedef struct date_time_s {
 #define REG_SUB_KEY  2
 #define REG_SYM_LINK 3
 
+typedef struct key_sec_desc_s KEY_SEC_DESC;
+
 typedef struct reg_key_s {
   char *name;         /* Name of the key                    */
   char *class_name;
@@ -345,7 +363,7 @@ typedef struct reg_key_s {
   struct reg_key_s *owner;
   struct key_list_s *sub_keys;
   struct val_list_s *values;
-  struct key_sec_desc_s *security;
+  KEY_SEC_DESC *security;
 } REG_KEY;
 
 /*
@@ -403,12 +421,12 @@ typedef struct sec_desc_s {
 #define SEC_DESC_RES 1
 #define SEC_DESC_OCU 2
 
-typedef struct key_sec_desc_s {
+struct key_sec_desc_s {
   struct key_sec_desc_s *prev, *next;
   int ref_cnt;
   int state;
   SEC_DESC *sec_desc;
-} KEY_SEC_DESC; 
+}; 
 
 /* 
  * All of the structures below actually have a four-byte lenght before them
@@ -817,6 +835,7 @@ int nt_delete_key_by_name(REGF *regf, char *name)
   key = nt_find_key_by_name(regf->root, name);
 
   if (key) {
+    if (key == regf->root) regf->root = NULL;
     return nt_delete_reg_key(key, True);
   }
 
@@ -982,13 +1001,54 @@ REG_KEY *nt_create_reg_key1(char *name, REG_KEY *parent)
 
   if (!(tmp->name = strdup(name))) goto error;
 
-
-
  error:
   if (tmp) free(tmp);
   return NULL;
 }
 
+/*
+ * Convert a string of the form S-1-5-x[-y-z-r] to a SID
+ */
+int strng_to_sid(DOM_SID **sid, char *sid_str)
+{
+  int i = 0, auth;
+  char *lstr; 
+
+  *sid = (DOM_SID *)malloc(sizeof(DOM_SID));
+  if (!*sid) return 0;
+
+  bzero(*sid, sizeof(DOM_SID));
+
+  if (strncmp(sid_str, "S-1-5", 5)) {
+    fprintf(stderr, "Does not conform to S-1-5...: %s\n", sid_str);
+    return 0;
+  }
+
+  /* We only allow strings of form S-1-5... */
+
+  (*sid)->ver = 1;
+  (*sid)->auth[5] = 5;
+
+  lstr = sid_str + 5;
+
+  while (1) {
+    if (!lstr || !lstr[0] || sscanf(lstr, "-%u", &auth) == 0) {
+      if (i < 1) {
+	fprintf(stderr, "Not of form -d-d...: %s, %u\n", lstr, i);
+	return 0;
+      }
+      (*sid)->auths=i;
+      return 1;
+    }
+
+    (*sid)->sub_auths[i] = auth;
+    i++;
+    lstr = strchr(lstr + 1, '-'); 
+  }
+
+  return 1;
+}
+
 /*
  * We will implement inheritence that is based on what the parent's SEC_DESC
  * says, but the Owner and Group SIDs can be overwridden from the command line
@@ -1001,8 +1061,24 @@ KEY_SEC_DESC *nt_inherit_security(REG_KEY *key)
   return key->security;
 }
 
-REG_KEY *nt_add_reg_key(REG_KEY *key, char *name, int create);
-REG_KEY *nt_add_reg_key_list(REG_KEY *key, char * name, int create)
+/*
+ * Create an initial security descriptor and init other structures, if needed
+ * We assume that the initial security stuff is empty ...
+ */
+KEY_SEC_DESC *nt_create_init_sec(REGF *regf)
+{
+  KEY_SEC_DESC *tsec = NULL;
+  
+
+  return tsec;
+}
+
+REG_KEY *nt_add_reg_subkey(REGF *regf, REG_KEY *key, char *name, int create);
+
+/*
+ * Add a sub-key 
+ */
+REG_KEY *nt_add_reg_key_list(REGF *regf, REG_KEY *key, char * name, int create)
 {
   int i;
   REG_KEY *ret = NULL, *tmp = NULL;
@@ -1021,7 +1097,7 @@ REG_KEY *nt_add_reg_key_list(REG_KEY *key, char * name, int create)
   }
 
   for (i = 0; i < list->key_count; i++) {
-    if ((ret = nt_add_reg_key(list->keys[i], name, create)))
+    if ((ret = nt_add_reg_subkey(regf, key, name, create)))
       return ret;
   }
 
@@ -1069,6 +1145,7 @@ REG_KEY *nt_add_reg_key_list(REG_KEY *key, char * name, int create)
   tmp->name = strdup(c1);
   if (!tmp->name) goto error;
   tmp->owner = key;
+  tmp->type = REG_SUB_KEY;
   /*
    * Next, pull security from the parent, but override by with
    * anything passed in on the command line
@@ -1078,7 +1155,7 @@ REG_KEY *nt_add_reg_key_list(REG_KEY *key, char * name, int create)
   list->keys[list->key_count - 1] = tmp;
 
   if (c2) {
-    ret = nt_add_reg_key(key, c2, True);
+    ret = nt_add_reg_subkey(regf, key, c2, True);
   }
 
   if (lname) free(lname);
@@ -1091,17 +1168,27 @@ REG_KEY *nt_add_reg_key_list(REG_KEY *key, char * name, int create)
   return NULL;
 }
 
-REG_KEY *nt_add_reg_key(REG_KEY *key, char *name, int create)
+REG_KEY *nt_add_reg_subkey(REGF *regf, REG_KEY *key, char *name, int create)
+{
+
+  return NULL;
+}
+
+/*
+ * This routine only adds a key from the root down.
+ * It calls helper functions to handle sub-key lists and sub-keys
+ */
+REG_KEY *nt_add_reg_key(REGF *regf, char *name, int create)
 {
   char *lname = NULL, *c1, *c2;
-  REG_KEY * tmp;
+  REG_KEY * tmp = NULL, *key = NULL;
 
   /*
    * Look until we hit the first component that does not exist, and
    * then add from there. However, if the first component does not 
    * match and the path we are given is the root, then it must match
    */
-  if (!key || !name || !*name) return NULL;
+  if (!regf || !name || !*name) return NULL;
 
   lname = strdup(name);
   if (!lname) return NULL;
@@ -1114,37 +1201,44 @@ REG_KEY *nt_add_reg_key(REG_KEY *key, char *name, int create)
   }
 
   /*
-   * If we don't match, then we have to return error ...
-   * If we do match on this component, check the next one in the
-   * list, and if not found, add it ... short circuit, add all the
-   * way down
+   * If the root does not exist, create it and make it equal to the
+   * first component ...
    */
 
-  if (strcmp(c1, key->name) != 0)
-    goto error;
-  
-  tmp = nt_add_reg_key_list(key, c2, True);
+  if (!regf->root) {
+    
+    tmp = (REG_KEY *)malloc(sizeof(REG_KEY));
+    if (!tmp) goto error;
+    bzero(tmp, sizeof(REG_KEY));
+    tmp->name = strdup(c1);
+    if (!tmp->name) goto error;
+    tmp->security = nt_create_init_sec(regf);
+    if (!tmp->security) goto error;
+    regf->root = tmp;
+
+  }
+  else {
+    /*
+     * If we don't match, then we have to return error ...
+     * If we do match on this component, check the next one in the
+     * list, and if not found, add it ... short circuit, add all the
+     * way down
+     */
+
+    if (strcmp(c1, key->name) != 0)
+      goto error;
+  }
+
+  tmp = nt_add_reg_key_list(regf, key, c2, True);
   free(lname);
   return tmp;
   
  error:
+  if (tmp) free(tmp);
   if (lname) free(lname);
   return NULL;
 }
 
-/*
- * Create/delete value lists, add/delete values, count them
- */
-
-
-/*
- * Create/delete security descriptors, add/delete SIDS, count SIDS, etc.
- * We reference count the security descriptors. Any new reference increments 
- * the ref count. If we modify an SD, we copy the old one, dec the ref count
- * and make the change. We also want to be able to check for equality so
- * we can reduce the number of SDs in use.
- */
-
 /*
  * Load and unload a registry file.
  *
@@ -1177,22 +1271,6 @@ REG_KEY *nt_add_reg_key(REG_KEY *key, char *name, int create)
 
 #define REGF_HDR_BLKSIZ 0x1000 
 
-/*
- * Structures for dealing with the on-disk format of the registry
- */
-
-#define IVAL(buf) ((unsigned int) \
-                   (unsigned int)*((unsigned char *)(buf)+3)<<24| \
-                   (unsigned int)*((unsigned char *)(buf)+2)<<16| \
-                   (unsigned int)*((unsigned char *)(buf)+1)<<8| \
-                   (unsigned int)*((unsigned char *)(buf)+0)) 
-
-#define SVAL(buf) ((unsigned short) \
-                   (unsigned short)*((unsigned char *)(buf)+1)<<8| \
-                   (unsigned short)*((unsigned char *)(buf)+0)) 
-
-#define CVAL(buf) ((unsigned char)*((unsigned char *)(buf)))
-
 #define OFF(f) ((f) + REGF_HDR_BLKSIZ + 4) 
 #define LOCN(base, f) ((base) + OFF(f))
 
@@ -3030,10 +3108,27 @@ int main(int argc, char *argv[])
        * Now, apply the requests to the tree ...
        */
       switch (cmd->cmd) {
-      case CMD_ADD_KEY:
+      case CMD_ADD_KEY: {
+	REG_KEY *tmp = NULL;
 
-	break;
+	tmp = nt_find_key_by_name(regf->root, cmd->key);
+
+	/* If we found it, apply the other bits, else create such a key */
 
+	if (!tmp)
+	  tmp = nt_add_reg_key(regf, cmd->key, True);
+
+	if (tmp) {
+
+	}
+
+	while (cmd->val_count) {
+
+	}
+
+	break;
+      }
+      
       case CMD_DEL_KEY:
 	/* 
 	 * Any value does not matter ...
-- 
cgit 


From 093cd223717db3ea4d731cf991a96b553e9ed93b Mon Sep 17 00:00:00 2001
From: Richard Sharpe 
Date: Sun, 20 Apr 2003 16:31:11 +0000
Subject: Complete most of the coding for adding keys. We can now add a key.

Next, we have to add the code for adding values etc.
(This used to be commit 266fc6c9f2283c81de97e526e9f289288948cb27)
---
 source3/utils/editreg.c | 58 +++++++++++++++++++++++++++----------------------
 1 file changed, 32 insertions(+), 26 deletions(-)

diff --git a/source3/utils/editreg.c b/source3/utils/editreg.c
index 9d155a9a11..e82991edc5 100644
--- a/source3/utils/editreg.c
+++ b/source3/utils/editreg.c
@@ -740,7 +740,7 @@ REG_KEY *nt_find_key_in_list_by_name(KEY_LIST *list, char *key)
 
   if (!list || !key || !*key) return NULL;
 
-  for (i = 0; i<= list->key_count; i++)
+  for (i = 0; i < list->key_count; i++)
     if ((res = nt_find_key_by_name(list->keys[i], key)))
       return res;
   
@@ -970,7 +970,7 @@ REG_KEY *nt_add_reg_value(REG_KEY *key, char *name, int type, char *value)
 /*
  * Delete a value. Should perhaps return the value ...
  */
-REG_KEY *nt_delete_reg_valye(REG_KEY *key, char *name)
+REG_KEY *nt_delete_reg_value(REG_KEY *key, char *name)
 {
 
   return NULL;
@@ -1073,8 +1073,6 @@ KEY_SEC_DESC *nt_create_init_sec(REGF *regf)
   return tsec;
 }
 
-REG_KEY *nt_add_reg_subkey(REGF *regf, REG_KEY *key, char *name, int create);
-
 /*
  * Add a sub-key 
  */
@@ -1096,16 +1094,6 @@ REG_KEY *nt_add_reg_key_list(REGF *regf, REG_KEY *key, char * name, int create)
 
   }
 
-  for (i = 0; i < list->key_count; i++) {
-    if ((ret = nt_add_reg_subkey(regf, key, name, create)))
-      return ret;
-  }
-
-  /*
-   * If we reach here we could not find the the first component
-   * so create it ...
-   */
-
   lname = strdup(name);
   if (!lname) return NULL;
 
@@ -1116,6 +1104,19 @@ REG_KEY *nt_add_reg_key_list(REGF *regf, REG_KEY *key, char * name, int create)
     c2++;
   }
 
+  for (i = 0; i < list->key_count; i++) {
+    if (strcmp(list->keys[i]->name, c1) == 0) {
+      ret = nt_add_reg_key_list(regf, list->keys[i], c2, create);
+      free(lname);
+      return ret;
+    }
+  }
+
+  /*
+   * If we reach here we could not find the the first component
+   * so create it ...
+   */
+
   if (list->key_count < list->max_keys){
     list->key_count++;
   }
@@ -1147,7 +1148,7 @@ REG_KEY *nt_add_reg_key_list(REGF *regf, REG_KEY *key, char * name, int create)
   tmp->owner = key;
   tmp->type = REG_SUB_KEY;
   /*
-   * Next, pull security from the parent, but override by with
+   * Next, pull security from the parent, but override with
    * anything passed in on the command line
    */
   tmp->security = nt_inherit_security(key);
@@ -1155,7 +1156,7 @@ REG_KEY *nt_add_reg_key_list(REGF *regf, REG_KEY *key, char * name, int create)
   list->keys[list->key_count - 1] = tmp;
 
   if (c2) {
-    ret = nt_add_reg_subkey(regf, key, c2, True);
+    ret = nt_add_reg_key_list(regf, key, c2, True);
   }
 
   if (lname) free(lname);
@@ -1168,12 +1169,6 @@ REG_KEY *nt_add_reg_key_list(REGF *regf, REG_KEY *key, char * name, int create)
   return NULL;
 }
 
-REG_KEY *nt_add_reg_subkey(REGF *regf, REG_KEY *key, char *name, int create)
-{
-
-  return NULL;
-}
-
 /*
  * This routine only adds a key from the root down.
  * It calls helper functions to handle sub-key lists and sub-keys
@@ -1181,7 +1176,7 @@ REG_KEY *nt_add_reg_subkey(REGF *regf, REG_KEY *key, char *name, int create)
 REG_KEY *nt_add_reg_key(REGF *regf, char *name, int create)
 {
   char *lname = NULL, *c1, *c2;
-  REG_KEY * tmp = NULL, *key = NULL;
+  REG_KEY * tmp = NULL;
 
   /*
    * Look until we hit the first component that does not exist, and
@@ -1225,11 +1220,11 @@ REG_KEY *nt_add_reg_key(REGF *regf, char *name, int create)
      * way down
      */
 
-    if (strcmp(c1, key->name) != 0)
+    if (strcmp(c1, regf->root->name) != 0)
       goto error;
   }
 
-  tmp = nt_add_reg_key_list(regf, key, c2, True);
+  tmp = nt_add_reg_key_list(regf, regf->root, c2, True);
   free(lname);
   return tmp;
   
@@ -2644,9 +2639,20 @@ CMD *regedit4_get_cmd(int fd)
 
   cmd->cmd = CMD_NONE;
   cmd->key = NULL;
+  cmd->val_count = 0;
   cmd->val_spec_list = cmd->val_spec_last = NULL;
   while ((cl = get_cmd_line(fd))) {
 
+    /*
+     * If it is an empty command line, and we already have a key
+     * then exit from here ... FIXME: Clean up the parser
+     */
+
+    if (cl->line_len == 0 && cmd->key) {
+      free_cmd_line(cl);
+      break;
+    } 
+
     strip_comment(cl);     /* remove anything beyond a comment char */
     trim_trailing_spaces(cl);
     trim_leading_spaces(cl);
@@ -3123,7 +3129,7 @@ int main(int argc, char *argv[])
 	}
 
 	while (cmd->val_count) {
-
+	  cmd->val_count--;
 	}
 
 	break;
-- 
cgit 


From 5c87b058422a9879ff0ae8c1cb427f371ac2865f Mon Sep 17 00:00:00 2001
From: Richard Sharpe 
Date: Sun, 20 Apr 2003 18:14:28 +0000
Subject: Begin the code that handles key values ... Delete a key value and add
 a key value, and tidy up processing of key values when reading in the
 registry file ... (This used to be commit
 53ea4c0de88a350b99e36c0dc514c5f2821ff7f8)

---
 source3/utils/editreg.c | 62 +++++++++++++++++++++++++++++++++++++++++++++----
 1 file changed, 58 insertions(+), 4 deletions(-)

diff --git a/source3/utils/editreg.c b/source3/utils/editreg.c
index e82991edc5..fb75601f26 100644
--- a/source3/utils/editreg.c
+++ b/source3/utils/editreg.c
@@ -386,6 +386,7 @@ typedef struct val_key_s {
 
 typedef struct val_list_s {
   int val_count;
+  int max_vals;
   VAL_KEY *vals[1];
 } VAL_LIST;
 
@@ -562,6 +563,7 @@ typedef struct vk_struct {
   char dat_name[1]; /* Name starts here ... */
 } VK_HDR;
 
+#define REG_TYPE_DELETE    -1
 #define REG_TYPE_NONE      0
 #define REG_TYPE_REGSZ     1
 #define REG_TYPE_EXPANDSZ  2
@@ -792,6 +794,7 @@ int nt_delete_val_key(VAL_KEY *val_key)
 {
 
   if (val_key) {
+    if (val_key->name) free(val_key->name);
     if (val_key->data_blk) free(val_key->data_blk);
     free(val_key);
   };
@@ -959,20 +962,67 @@ int nt_delete_reg_key(REG_KEY *key, int delete_name)
 }
 
 /*
- * Add a value to the key specified ...
+ * Add a value to the key specified ... We have to parse the value some more
+ * based on the type to get it in the correct internal form
+ * An empty name will be converted to "" before here 
  */
 REG_KEY *nt_add_reg_value(REG_KEY *key, char *name, int type, char *value)
 {
+  int i;
+  VAL_KEY *tmp = NULL;
+
+  if (!key || !key->values || !name || !*name) return NULL;
+
+  assert(type != REG_TYPE_DELETE); /* We never process deletes here */
+
+  for (i = 0; i < key->values->val_count; i++) {
+    if (strcmp(name, key->values->vals[i]->name) == 0){ /* Change the value */
+
+
+    }
+  }
+
+  /* 
+   * If we get here, the name was not found, so insert it 
+   */
+
+  tmp = (VAL_KEY *)malloc(sizeof(VAL_KEY));
+  if (!tmp) goto error;
+
+  bzero(tmp, sizeof(VAL_KEY));
+  tmp->name = strdup(name);
+  if (!tmp->name) goto error;
+  tmp->data_type = type;
 
+ error:
+  if (tmp) nt_delete_val_key(tmp);
   return NULL;
 }
 
 /*
- * Delete a value. Should perhaps return the value ...
+ * Delete a value. We return the value and let the caller deal witj it. 
  */
-REG_KEY *nt_delete_reg_value(REG_KEY *key, char *name)
+VAL_KEY *nt_delete_reg_value(REG_KEY *key, char *name)
 {
+  int i, j;
+
+  if (!key || !key->values || !name || !*name) return NULL;
 
+  for (i = 0; i< key->values->val_count; i++) {
+    if (strcmp(name, key->values->vals[i]->name) == 0) {
+      VAL_KEY *val;
+
+      val = key->values->vals[i];
+
+      /* Shuffle down */
+      for (j = i + 1; j < key->values->val_count; j++)
+	key->values->vals[j - 1] = key->values->vals[j];
+
+      key->values->val_count--;
+
+      return val;
+    }
+  }
   return NULL;
 }
 
@@ -1819,7 +1869,7 @@ VAL_KEY *process_vk(REGF *regf, VK_HDR *vk_hdr, int size)
   return tmp;
 
  error:
-  /* XXX: FIXME, free the partially allocated struct */
+  if (tmp) nt_delete_val_key(tmp);
   return NULL;
 
 }
@@ -1855,6 +1905,7 @@ VAL_LIST *process_vl(REGF *regf, VL_TYPE vl, int count, int size)
   }
 
   tmp->val_count = count;
+  tmp->max_vals = count;
 
   return tmp;
 
@@ -2415,6 +2466,8 @@ int parse_value_type(char *tstr)
     return REG_TYPE_REGSZ;
   else if (strcmp(tstr, "REG_MULTI_SZ") == 0)
     return REG_TYPE_MULTISZ;
+  else if (strcmp(tstr, "-") == 0)
+    return REG_TYPE_DELETE;
 
   return 0;
 }
@@ -2624,6 +2677,7 @@ void trim_trailing_spaces(struct cmd_line *cl)
  * value ::= =':'
  *  is some path, possibly enclosed in quotes ...
  * We alctually look for the next key to terminate a previous key
+ * if  == '-', then it is a delete type.
  */
 CMD *regedit4_get_cmd(int fd)
 {
-- 
cgit 


From 963eff4b181cdd038e019c5a2a2bd0ab9dea222f Mon Sep 17 00:00:00 2001
From: Richard Sharpe 
Date: Sun, 20 Apr 2003 20:09:39 +0000
Subject: Add code to delete values ...

This needs a lot more testing and debugging, but it does delete values.

Next to see if it can add values ...
(This used to be commit 02e6782243a7ef9e182db449ad377b0d168a40b2)
---
 source3/utils/editreg.c | 113 ++++++++++++++++++++++++++++++++++++++++++++----
 1 file changed, 104 insertions(+), 9 deletions(-)

diff --git a/source3/utils/editreg.c b/source3/utils/editreg.c
index fb75601f26..5e79df1a14 100644
--- a/source3/utils/editreg.c
+++ b/source3/utils/editreg.c
@@ -961,12 +961,54 @@ int nt_delete_reg_key(REG_KEY *key, int delete_name)
   return 1;
 }
 
+/*
+ * Convert a string to a value ...
+ * FIXME: Error handling and convert this at command parse time ... 
+ */
+void *str_to_val(int type, char *val, int *len)
+{
+  unsigned int *dwordp = NULL;
+
+  if (!len || !val) return NULL;
+
+  switch (type) {
+  case REG_TYPE_REGSZ:
+    *len = strlen(val);
+    return (void *)val;
+
+  case REG_TYPE_DWORD:
+    dwordp = (unsigned int *)malloc(sizeof(unsigned int));
+    if (!dwordp) return NULL;
+    /* Allow for ddddd and 0xhhhhh and 0ooooo */
+    if (strncmp(val, "0x", 2) == 0 || strncmp(val, "0X", 2) == 0) {
+      sscanf(val, "0[xX]%X", dwordp);
+    }
+    else if (*val == '0') {
+      sscanf(val, "0%o", dwordp);
+    }
+    else { 
+      sscanf(val, "%d", dwordp);
+    }
+    *len = sizeof(unsigned int);
+    return (void *)dwordp;
+
+    /* FIXME: Implement more of these */
+
+  default:
+    return NULL;
+    break;
+  }
+
+  return NULL;
+}
+
 /*
  * Add a value to the key specified ... We have to parse the value some more
  * based on the type to get it in the correct internal form
- * An empty name will be converted to "" before here 
+ * An empty name will be converted to "" before here
+ * Hmmm, maybe not. has_name is for that
  */
-REG_KEY *nt_add_reg_value(REG_KEY *key, char *name, int type, char *value)
+VAL_KEY *nt_add_reg_value(REG_KEY *key, char *name, int type, char *value)
 {
   int i;
   VAL_KEY *tmp = NULL;
@@ -977,8 +1019,10 @@ REG_KEY *nt_add_reg_value(REG_KEY *key, char *name, int type, char *value)
 
   for (i = 0; i < key->values->val_count; i++) {
     if (strcmp(name, key->values->vals[i]->name) == 0){ /* Change the value */
-
-
+      free(key->values->vals[i]->data_blk);
+      key->values->vals[i]->data_blk = str_to_val(type, value, &
+						  key->values->vals[i]->data_len);
+      return key->values->vals[i];
     }
   }
 
@@ -991,8 +1035,30 @@ REG_KEY *nt_add_reg_value(REG_KEY *key, char *name, int type, char *value)
 
   bzero(tmp, sizeof(VAL_KEY));
   tmp->name = strdup(name);
+  tmp->has_name = True;
   if (!tmp->name) goto error;
   tmp->data_type = type;
+  tmp->data_blk = str_to_val(type, value, &tmp->data_len);
+
+  /* Now, add to val list */
+
+  if (key->values->val_count >= key->values->max_vals) {
+    /*
+     * Allocate some more space 
+     */
+
+    if ((key->values = (VAL_LIST *)realloc(key->values, sizeof(VAL_LIST) + 
+					   key->values->val_count - 1 +
+					   REG_KEY_LIST_SIZE))) {
+      key->values->max_vals += REG_KEY_LIST_SIZE;
+    }
+    else goto error;
+  }
+
+  i = key->values->val_count;
+  key->values->val_count++;
+  key->values->vals[i] = tmp;
+  return tmp;
 
  error:
   if (tmp) nt_delete_val_key(tmp);
@@ -1000,7 +1066,7 @@ REG_KEY *nt_add_reg_value(REG_KEY *key, char *name, int type, char *value)
 }
 
 /*
- * Delete a value. We return the value and let the caller deal witj it. 
+ * Delete a value. We return the value and let the caller deal with it. 
  */
 VAL_KEY *nt_delete_reg_value(REG_KEY *key, char *name)
 {
@@ -1008,8 +1074,11 @@ VAL_KEY *nt_delete_reg_value(REG_KEY *key, char *name)
 
   if (!key || !key->values || !name || !*name) return NULL;
 
+  /* FIXME: Allow empty value name */
   for (i = 0; i< key->values->val_count; i++) {
-    if (strcmp(name, key->values->vals[i]->name) == 0) {
+    if ((!key->values->vals[i]->has_name && !*name) || 
+	(key->values->vals[i]->has_name &&
+	 strcmp(name, key->values->vals[i]->name) == 0)) {
       VAL_KEY *val;
 
       val = key->values->vals[i];
@@ -2269,6 +2338,15 @@ typedef struct cmd_line {
   char *line;
 } CMD_LINE;
 
+void free_val_spec_list(VAL_SPEC_LIST *vl)
+{
+  if (!vl) return;
+  if (vl->name) free(vl->name);
+  if (vl->val) free(vl->val);
+  free(vl);
+
+}
+
 /* 
  * Some routines to handle lines of info in the command files
  */
@@ -2505,14 +2583,16 @@ char *parse_value(struct cmd_line *cl, int *vtype, char **val)
   while (*tstr == ' ') tstr++; /* Skip leading white space */
   p2 = strchr(p2, ':');
 
-  if (!p2) goto error;
-
-  *p2 = 0; p2++; /* split on the : */
+  if (p2) {
+    *p2 = 0; p2++; /* split on the : */
+  }
 
   *vtype = parse_value_type(tstr);
 
   if (!vtype) goto error;
 
+  if (!p2 || !*p2) return nstr;
+
   /* Now, parse the value string. It should return a newly malloc'd string */
   
   while (*p2 == ' ') p2++; /* Skip leading space */
@@ -2736,6 +2816,7 @@ CMD *regedit4_get_cmd(int fd)
 	vl = (struct val_spec_list *)malloc(sizeof(struct val_spec_list));
 	if (!vl) goto error;
 	vl->next = NULL;
+	vl->val = NULL;
 	vl->name = parse_value(cl, &vl->type, &vl->val);
 	if (!vl->name) goto error;
 	if (cmd->val_spec_list == NULL) {
@@ -3183,6 +3264,20 @@ int main(int argc, char *argv[])
 	}
 
 	while (cmd->val_count) {
+	  VAL_SPEC_LIST *val = cmd->val_spec_list;
+	  VAL_KEY *reg_val = NULL;
+	  
+	  if (val->type == REG_TYPE_DELETE) {
+	    reg_val = nt_delete_reg_value(tmp, val -> name);
+	    if (reg_val) nt_delete_val_key(reg_val);
+	  }
+	  else {
+	    reg_val = nt_add_reg_value(tmp, reg_val->name, val->type, 
+				       val->val);
+	  }
+
+	  cmd->val_spec_list = val->next;
+	  free_val_spec_list(val);
 	  cmd->val_count--;
 	}
 
-- 
cgit 


From 6f499782dcf6bd621f5e076046bffdc714fa01f9 Mon Sep 17 00:00:00 2001
From: Richard Sharpe 
Date: Sun, 20 Apr 2003 21:43:07 +0000
Subject: Well, we can now add keys and values and delete keys and values ...

Lots more to do, like handling regular expressions for keys, and input of
the security descriptors, etc. However, I now have to work on writing the
in-memory tree out to a file in a format that Windows can understand.
(This used to be commit 562b36510c704eba84b036aacdb1f984339afafc)
---
 source3/utils/editreg.c | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/source3/utils/editreg.c b/source3/utils/editreg.c
index 5e79df1a14..b35e278ab0 100644
--- a/source3/utils/editreg.c
+++ b/source3/utils/editreg.c
@@ -981,10 +981,10 @@ void *str_to_val(int type, char *val, int *len)
     if (!dwordp) return NULL;
     /* Allow for ddddd and 0xhhhhh and 0ooooo */
     if (strncmp(val, "0x", 2) == 0 || strncmp(val, "0X", 2) == 0) {
-      sscanf(val, "0[xX]%X", dwordp);
+      sscanf(&val[2], "%X", dwordp);
     }
     else if (*val == '0') {
-      sscanf(val, "0%o", dwordp);
+      sscanf(&val[1], "%o", dwordp);
     }
     else { 
       sscanf(val, "%d", dwordp);
@@ -1018,7 +1018,9 @@ VAL_KEY *nt_add_reg_value(REG_KEY *key, char *name, int type, char *value)
   assert(type != REG_TYPE_DELETE); /* We never process deletes here */
 
   for (i = 0; i < key->values->val_count; i++) {
-    if (strcmp(name, key->values->vals[i]->name) == 0){ /* Change the value */
+    if ((!key->values->vals[i]->has_name && !*name) || 
+	(key->values->vals[i]->has_name &&
+	 strcmp(name, key->values->vals[i]->name) == 0)){ /* Change the value */
       free(key->values->vals[i]->data_blk);
       key->values->vals[i]->data_blk = str_to_val(type, value, &
 						  key->values->vals[i]->data_len);
@@ -3272,7 +3274,7 @@ int main(int argc, char *argv[])
 	    if (reg_val) nt_delete_val_key(reg_val);
 	  }
 	  else {
-	    reg_val = nt_add_reg_value(tmp, reg_val->name, val->type, 
+	    reg_val = nt_add_reg_value(tmp, val->name, val->type, 
 				       val->val);
 	  }
 
-- 
cgit 


From 60801e810503a89ba1253e3e0b688a33f7465182 Mon Sep 17 00:00:00 2001
From: Richard Sharpe 
Date: Sun, 20 Apr 2003 21:52:55 +0000
Subject: Add a -f command-line flag to specify printing all paths or only
 terminal paths. (This used to be commit
 0741369c59bcb6057f6b32d3fe4f6dec08ce4ae3)

---
 source3/utils/editreg.c | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/source3/utils/editreg.c b/source3/utils/editreg.c
index b35e278ab0..1b148f3bd1 100644
--- a/source3/utils/editreg.c
+++ b/source3/utils/editreg.c
@@ -330,6 +330,7 @@ Hope this helps....  (Although it was "fun" for me to uncover this things,
 
 static int verbose = 0;
 static int print_security = 0;
+static int full_print = 0;
 
 /* 
  * These definitions are for the in-memory registry structure.
@@ -2990,7 +2991,7 @@ int print_key(const char *path, char *name, char *class_name, int root,
 	      int terminal, int vals)
 {
 
-  /*if (terminal)*/ fprintf(stdout, "[%s%s]\n", path, name);
+  if (full_print || terminal) fprintf(stdout, "[%s%s]\n", path, name);
 
   return 1;
 }
@@ -3142,9 +3143,10 @@ int print_val(const char *path, char *val_name, int val_type, int data_len,
 
 void usage(void)
 {
-  fprintf(stderr, "Usage: editreg [-v] [-p] [-k] [-s] [-c ] \n");
+  fprintf(stderr, "Usage: editreg [-f] [-v] [-p] [-k] [-s] [-c ] \n");
   fprintf(stderr, "Version: 0.1\n\n");
   fprintf(stderr, "\n\t-v\t sets verbose mode");
+  fprintf(stderr, "\n\t-f\t sets full print mode where non-terminals are printed");
   fprintf(stderr, "\n\t-p\t prints the registry");
   fprintf(stderr, "\n\t-s\t prints security descriptors");
   fprintf(stderr, "\n\t-c \t specifies a command file");
@@ -3172,7 +3174,7 @@ int main(int argc, char *argv[])
    * Now, process the arguments
    */
 
-  while ((opt = getopt(argc, argv, "spvko:c:")) != EOF) {
+  while ((opt = getopt(argc, argv, "fspvko:c:")) != EOF) {
     switch (opt) {
     case 'c':
       commands = 1;
@@ -3180,6 +3182,11 @@ int main(int argc, char *argv[])
       regf_opt += 2;
       break;
 
+    case 'f':
+      full_print = 1;
+      regf_opt++;
+      break;
+
     case 'o':
       out_file_name = optarg;
       regf_opt += 2;
@@ -3192,6 +3199,7 @@ int main(int argc, char *argv[])
 
     case 's':
       print_security++;
+      full_print++;
       regf_opt++;
       break;
 
-- 
cgit 


From ea67a9e0566bfa6659e5911dbdfa1054d4ee0c77 Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij 
Date: Mon, 21 Apr 2003 00:38:16 +0000
Subject: Pdb modules are in $libdir/pdb not $libdir/passdb (This used to be
 commit 9822af500cf36e83fce54e49a062a8847d1c5431)

---
 source3/passdb/pdb_interface.c | 17 +++++------------
 1 file changed, 5 insertions(+), 12 deletions(-)

diff --git a/source3/passdb/pdb_interface.c b/source3/passdb/pdb_interface.c
index 8adcd9dbfa..9224e784e0 100644
--- a/source3/passdb/pdb_interface.c
+++ b/source3/passdb/pdb_interface.c
@@ -43,13 +43,9 @@ BOOL smb_register_passdb(const char *name, pdb_init_function init, int version)
 
 	DEBUG(5,("Attempting to register passdb backend %s\n", name));
 
-	/* Check for duplicates */
-	while(entry) { 
-		if(strcasecmp(name, entry->name) == 0) { 
-			DEBUG(0,("There already is a passdb backend registered with the name %s!\n", name));
-			return False;
-		}
-		entry = entry->next;
+	if (pdb_find_backend_entry(name)) {
+		DEBUG(0,("There already is a passdb backend registered with the name %s!\n", name));
+		return False;
 	}
 
 	entry = smb_xmalloc(sizeof(struct pdb_init_function_entry));
@@ -64,12 +60,9 @@ BOOL smb_register_passdb(const char *name, pdb_init_function init, int version)
 static struct pdb_init_function_entry *pdb_find_backend_entry(const char *name)
 {
 	struct pdb_init_function_entry *entry = backends;
-	pstring stripped;
-
-	module_path_get_name(name, stripped);
 
 	while(entry) {
-		if (strequal(entry->name, stripped)) return entry;
+		if (strcasecmp(entry->name, name) == 0) return entry;
 		entry = entry->next;
 	}
 
@@ -431,7 +424,7 @@ static NTSTATUS make_pdb_methods_name(struct pdb_methods **methods, struct pdb_c
 	/* Try to find a module that contains this module */
 	if (!entry) { 
 		DEBUG(2,("No builtin backend found, trying to load plugin\n"));
-		if(smb_probe_module("passdb", module_name) && !(entry = pdb_find_backend_entry(module_name))) {
+		if(smb_probe_module("pdb", module_name) && !(entry = pdb_find_backend_entry(module_name))) {
 			DEBUG(0,("Plugin is available, but doesn't register passdb backend %s\n", module_name));
 			SAFE_FREE(module_name);
 			return NT_STATUS_UNSUCCESSFUL;
-- 
cgit 


From dcee9b58b95e7dd199e22495b5b83ab745e8fb1d Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij 
Date: Mon, 21 Apr 2003 01:56:13 +0000
Subject: Default to "passdb.xml" as default output filename instead of "-"
 (This used to be commit aa4c11370bb09bfd20d02da509ebdd6dc475439d)

---
 source3/modules/xml.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source3/modules/xml.c b/source3/modules/xml.c
index 1a4aeeeac0..d018175d38 100644
--- a/source3/modules/xml.c
+++ b/source3/modules/xml.c
@@ -554,7 +554,7 @@ NTSTATUS xmlsam_init(PDB_CONTEXT * pdb_context, PDB_METHODS ** pdb_method,
 
 	data = talloc(pdb_context->mem_ctx, sizeof(pdb_xml));
 	data->location =
-		(location ? talloc_strdup(pdb_context->mem_ctx, location) : "-");
+		(location ? talloc_strdup(pdb_context->mem_ctx, location) : "passdb.xml");
 	data->pwent = NULL;
 	data->written = 0;
 	(*pdb_method)->private_data = data;
-- 
cgit 


From 0bd549739c05e2c7a181d560ab8594cf02707467 Mon Sep 17 00:00:00 2001
From: Richard Sharpe 
Date: Mon, 21 Apr 2003 04:08:42 +0000
Subject: Some comments about the format of the on-disk reg file, as well as
 partially implement some routines to construct a default ACL and SEC DESC
 etc. (This used to be commit 043374a3c0be6769b4fee2228dcff42abbb74028)

---
 source3/utils/editreg.c | 93 +++++++++++++++++++++++++++++++++++++++++++++----
 1 file changed, 86 insertions(+), 7 deletions(-)

diff --git a/source3/utils/editreg.c b/source3/utils/editreg.c
index 1b148f3bd1..4df0b5f677 100644
--- a/source3/utils/editreg.c
+++ b/source3/utils/editreg.c
@@ -422,7 +422,7 @@ typedef struct sec_desc_s {
 #define SEC_DESC_NON 0
 #define SEC_DESC_RES 1
 #define SEC_DESC_OCU 2
-
+#define SEC_DESC_NBK 3
 struct key_sec_desc_s {
   struct key_sec_desc_s *prev, *next;
   int ref_cnt;
@@ -467,8 +467,8 @@ typedef struct hbin_sub_struct {
 
 typedef struct hbin_struct {
   DWORD HBIN_ID; /* hbin */
-  DWORD next_off;
   DWORD prev_off;
+  DWORD next_off;
   DWORD uk1;
   DWORD uk2;
   DWORD uk3;
@@ -594,6 +594,7 @@ struct regf_struct_s {
   REG_KEY *root;  /* Root of the tree for this file */
   int sk_count, sk_map_size;
   SK_MAP *sk_map;
+  SEC_DESC *def_sec_desc;
 };
 
 typedef struct regf_struct_s REGF;
@@ -1131,7 +1132,7 @@ REG_KEY *nt_create_reg_key1(char *name, REG_KEY *parent)
 /*
  * Convert a string of the form S-1-5-x[-y-z-r] to a SID
  */
-int strng_to_sid(DOM_SID **sid, char *sid_str)
+int string_to_sid(DOM_SID **sid, char *sid_str)
 {
   int i = 0, auth;
   char *lstr; 
@@ -1171,6 +1172,47 @@ int strng_to_sid(DOM_SID **sid, char *sid_str)
   return 1;
 }
 
+/*
+ * Create a default ACL
+ */
+ACL *nt_create_default_acl(REGF *regf)
+{
+  ACL *acl;
+
+  acl = (ACL *)malloc(sizeof(ACL));
+  if (!acl) goto error;
+
+  return acl;
+
+ error:
+  if (acl) nt_delete_acl(acl);
+}
+
+/*
+ * Create a default security descriptor. We pull in things from env
+ * if need be 
+ */
+SEC_DESC *nt_create_def_sec_desc(REGF *regf)
+{
+  SEC_DESC *tmp;
+
+  tmp = (SEC_DESC *)malloc(sizeof(SEC_DESC));
+  if (!tmp) return NULL;
+
+  tmp->rev = 1;
+  tmp->type = 0x8004;
+  if (!string_to_sid(&tmp->owner, "S-1-5-32-544")) goto error;
+  if (!string_to_sid(&tmp->group, "S-1-5-18")) goto error;
+  tmp->sacl = NULL;
+  tmp->dacl = nt_create_default_acl(regf);
+
+  return tmp;
+
+ error:
+  if (tmp) nt_delete_sec_desc(tmp);
+  return NULL;
+}
+
 /*
  * We will implement inheritence that is based on what the parent's SEC_DESC
  * says, but the Owner and Group SIDs can be overwridden from the command line
@@ -1191,6 +1233,13 @@ KEY_SEC_DESC *nt_create_init_sec(REGF *regf)
 {
   KEY_SEC_DESC *tsec = NULL;
   
+  tsec = (KEY_SEC_DESC *)malloc(sizeof(KEY_SEC_DESC));
+  if (!tsec) return NULL;
+
+  tsec->ref_cnt = 1;
+  tsec->state = SEC_DESC_NBK;
+
+  tsec->sec_desc = regf->def_sec_desc;
 
   return tsec;
 }
@@ -1727,6 +1776,8 @@ ACL *dup_acl(REG_ACL *acl)
   tmp->num_aces = num_aces;
   tmp->refcnt = 1;
   tmp->rev = SVAL(&acl->rev);
+  if (verbose) fprintf(stdout, "ACL: refcnt: %u, rev: %u\n", tmp->refcnt, 
+		       tmp->rev);
   ace = (REG_ACE *)&acl->aces;
   for (i=0; iaces[i] = dup_ace(ace);
@@ -1749,6 +1800,8 @@ SEC_DESC *process_sec_desc(REGF *regf, REG_SEC_DESC *sec_desc)
   
   tmp->rev = SVAL(&sec_desc->rev);
   tmp->type = SVAL(&sec_desc->type);
+  if (verbose) fprintf(stdout, "SEC_DESC Rev: %0X, Type: %0X\n", 
+		       tmp->rev, tmp->type);
   tmp->owner = dup_sid((DOM_SID *)((char *)sec_desc + IVAL(&sec_desc->owner_off)));
   if (!tmp->owner) {
     free(tmp);
@@ -2006,7 +2059,7 @@ KEY_LIST *process_lf(REGF *regf, LF_HDR *lf_hdr, int size, REG_KEY *parent)
   assert(size < 0);
 
   count = SVAL(&lf_hdr->key_count);
-
+  if (verbose) fprintf(stdout, "Key Count: %u\n", count);
   if (count <= 0) return NULL;
 
   /* Now, we should allocate a KEY_LIST struct and fill it in ... */
@@ -2023,6 +2076,7 @@ KEY_LIST *process_lf(REGF *regf, LF_HDR *lf_hdr, int size, REG_KEY *parent)
     NK_HDR *nk_hdr;
 
     nk_off = IVAL(&lf_hdr->hr[i].nk_off);
+    if (verbose) fprintf(stdout, "NK Offset: %0X\n", nk_off);
     nk_hdr = (NK_HDR *)LOCN(regf->base, nk_off);
     tmp->keys[i] = nt_get_key_tree(regf, nk_hdr, BLK_SIZE(nk_hdr), parent);
     if (!tmp->keys[i]) {
@@ -2114,6 +2168,7 @@ REG_KEY *nt_get_key_tree(REGF *regf, NK_HDR *nk_hdr, int size, REG_KEY *parent)
 
     clsnam_off = IVAL(&nk_hdr->clsnam_off);
     clsnamep = LOCN(regf->base, clsnam_off);
+    if (verbose) fprintf(stdout, "Class Name Offset: %0X\n", clsnam_off);
  
     bzero(cls_name, clsname_len);
     uni_to_ascii(clsnamep, cls_name, sizeof(cls_name), clsname_len);
@@ -2140,8 +2195,9 @@ REG_KEY *nt_get_key_tree(REGF *regf, NK_HDR *nk_hdr, int size, REG_KEY *parent)
 
   own_off = IVAL(&nk_hdr->own_off);
   own = (REG_KEY *)LOCN(regf->base, own_off);
+  if (verbose) fprintf(stdout, "Owner Offset: %0X\n", own_off);
 
-  if (verbose) fprintf(stdout, "  Owner offset: %0X, Our Offset: %0X\n", 
+  if (verbose) fprintf(stdout, "  Owner locn: %0X, Our locn: %0X\n", 
 		       (unsigned int)own, (unsigned int)nk_hdr);
 
   /* 
@@ -2156,11 +2212,12 @@ REG_KEY *nt_get_key_tree(REGF *regf, NK_HDR *nk_hdr, int size, REG_KEY *parent)
    */
 
   val_count = IVAL(&nk_hdr->val_cnt);
-
+  if (verbose) fprintf(stdout, "Val Count: %d\n", val_count);
   if (val_count) {
 
     val_off = IVAL(&nk_hdr->val_off);
     vl = (VL_TYPE *)LOCN(regf->base, val_off);
+    if (verbose) fprintf(stdout, "Val List Offset: %0X\n", val_off);
 
     tmp->values = process_vl(regf, *vl, val_count, BLK_SIZE(vl));
     if (!tmp->values) {
@@ -2175,6 +2232,7 @@ REG_KEY *nt_get_key_tree(REGF *regf, NK_HDR *nk_hdr, int size, REG_KEY *parent)
 
   sk_off = IVAL(&nk_hdr->sk_off);
   sk_hdr = (SK_HDR *)LOCN(regf->base, sk_off);
+  if (verbose) fprintf(stdout, "SK Offset: %0X\n", sk_off);
 
   if (sk_off != -1) {
 
@@ -2183,6 +2241,7 @@ REG_KEY *nt_get_key_tree(REGF *regf, NK_HDR *nk_hdr, int size, REG_KEY *parent)
   } 
 
   lf_off = IVAL(&nk_hdr->lf_off);
+  if (verbose) fprintf(stdout, "SubKey list offset: %0X\n", lf_off);
 
   /*
    * No more subkeys if lf_off == -1
@@ -2257,7 +2316,21 @@ int nt_load_registry(REGF *regf)
    * Get a pointer to the first key from the hreg_hdr
    */
 
+  if (verbose) fprintf(stdout, "First Key: %0X\n",
+		       IVAL(®f_hdr->first_key));
+
   first_key = (NK_HDR *)LOCN(regf->base, IVAL(®f_hdr->first_key));
+  if (verbose) fprintf(stdout, "First Key Offset: %0X\n", 
+		       IVAL(®f_hdr->first_key));
+
+  if (verbose) fprintf(stdout, "Data Block Size: %d\n",
+		       IVAL(®f_hdr->dblk_size));
+
+  if (verbose) fprintf(stdout, "Offset to next hbin block: %0X\n",
+		       IVAL(&hbin_hdr->next_off));
+
+  if (verbose) fprintf(stdout, "HBIN block size: %0X\n",
+		       IVAL(&hbin_hdr->blk_size));
 
   /*
    * Now, get the registry tree by processing that NK recursively
@@ -2280,7 +2353,13 @@ int nt_load_registry(REGF *regf)
 }
 
 /*
- * Story the registry in the output file
+ * Store the registry in the output file
+ * We write out the header and then each of the keys etc into the file
+ * We have to flatten the data structure ...
+ *
+ * The structures are stored in a breadth-first fashion, with all records
+ * aligned on 8-byte boundaries, with sub-keys and values layed down before
+ * the lists that contain them. SK records are layed down first, however.
  */
 int nt_store_registry(REGF *regf)
 {
-- 
cgit 


From 94b6f516af1d0400077a46c7a1eab9022e7f4ad0 Mon Sep 17 00:00:00 2001
From: Richard Sharpe 
Date: Mon, 21 Apr 2003 05:18:13 +0000
Subject: Start the outline of the code to store a registry tree ... (This used
 to be commit 03fce4ed0f73586928424e75bd6d7db9ff7105dd)

---
 source3/utils/editreg.c | 101 +++++++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 99 insertions(+), 2 deletions(-)

diff --git a/source3/utils/editreg.c b/source3/utils/editreg.c
index 4df0b5f677..72ae17a45f 100644
--- a/source3/utils/editreg.c
+++ b/source3/utils/editreg.c
@@ -331,6 +331,7 @@ Hope this helps....  (Although it was "fun" for me to uncover this things,
 static int verbose = 0;
 static int print_security = 0;
 static int full_print = 0;
+static char *def_owner_sid_str = NULL;
 
 /* 
  * These definitions are for the in-memory registry structure.
@@ -594,6 +595,7 @@ struct regf_struct_s {
   REG_KEY *root;  /* Root of the tree for this file */
   int sk_count, sk_map_size;
   SK_MAP *sk_map;
+  char *owner_sid_str;
   SEC_DESC *def_sec_desc;
 };
 
@@ -1172,6 +1174,27 @@ int string_to_sid(DOM_SID **sid, char *sid_str)
   return 1;
 }
 
+/*
+ * Create an ACE
+ */
+ACE *nt_create_ace(int type, int flags, unsigned int perms, char *sid)
+{
+  ACE *ace;
+
+  ace = (ACE *)malloc(sizeof(ACE));
+  if (!ace) goto error;
+  ace->type = type;
+  ace->flags = flags;
+  ace->perms = perms;
+  if (!string_to_sid(&ace->trustee, sid))
+    goto error;
+  return ace;
+
+ error:
+  if (ace) nt_delete_ace(ace);
+  return NULL;
+}
+
 /*
  * Create a default ACL
  */
@@ -1179,13 +1202,34 @@ ACL *nt_create_default_acl(REGF *regf)
 {
   ACL *acl;
 
-  acl = (ACL *)malloc(sizeof(ACL));
+  acl = (ACL *)malloc(sizeof(ACL) + 7*sizeof(ACE *));
   if (!acl) goto error;
 
+  acl->rev = 2;
+  acl->refcnt = 1;
+  acl->num_aces = 8;
+
+  acl->aces[0] = nt_create_ace(0x00, 0x0, 0xF003F, regf->owner_sid_str);
+  if (!acl->aces[0]) goto error;
+  acl->aces[1] = nt_create_ace(0x00, 0x0, 0xF003F, "S-1-5-18");
+  if (!acl->aces[1]) goto error;
+  acl->aces[2] = nt_create_ace(0x00, 0x0, 0xF003F, "S-1-5-32-544");
+  if (!acl->aces[2]) goto error;
+  acl->aces[3] = nt_create_ace(0x00, 0x0, 0x20019, "S-1-5-12");
+  if (!acl->aces[3]) goto error;
+  acl->aces[4] = nt_create_ace(0x00, 0x0B, 0x10000000, regf->owner_sid_str);
+  if (!acl->aces[4]) goto error;
+  acl->aces[5] = nt_create_ace(0x00, 0x0B, 0x10000000, "S-1-5-18");
+  if (!acl->aces[5]) goto error;
+  acl->aces[6] = nt_create_ace(0x00, 0x0B, 0x10000000, "S-1-5-32-544");
+  if (!acl->aces[6]) goto error;
+  acl->aces[7] = nt_create_ace(0x00, 0x0B, 0x80000000, "S-1-5-12");
+  if (!acl->aces[7]) goto error;
   return acl;
 
  error:
   if (acl) nt_delete_acl(acl);
+  return NULL;
 }
 
 /*
@@ -1556,6 +1600,7 @@ REGF *nt_create_regf(void)
   REGF *tmp = (REGF *)malloc(sizeof(REGF));
   if (!tmp) return tmp;
   bzero(tmp, sizeof(REGF));
+  tmp->owner_sid_str = def_owner_sid_str;
   return tmp;
 } 
 
@@ -2352,6 +2397,33 @@ int nt_load_registry(REGF *regf)
   return 1;
 }
 
+/*
+ * These structures keep track of the output format of the registry
+ */
+typedef struct hbin_blk_s {
+  struct hbin_blk_s *next;
+  unsigned int file_offset;  /* Offset in file                */
+  unsigned int free_space;    /* Amount of free space in block */
+  unsigned int fsp_off;      /* Start of free space in block  */
+} HBIN_BLK;
+
+/*
+ * Store a KEY in the file ...
+ */
+int nt_store_reg_key(REGF *regf, REG_KEY *key)
+{
+
+  return 0;
+}
+
+/*
+ * Store the registry header ...
+ */
+int nt_store_reg_header(REGF *regf){
+
+  return 0;
+}
+
 /*
  * Store the registry in the output file
  * We write out the header and then each of the keys etc into the file
@@ -3243,6 +3315,7 @@ int main(int argc, char *argv[])
   char *cmd_file_name = NULL;
   char *out_file_name = NULL;
   CMD_FILE *cmd_file = NULL;
+  DOM_SID *lsid;
 
   if (argc < 2) {
     usage();
@@ -3253,7 +3326,7 @@ int main(int argc, char *argv[])
    * Now, process the arguments
    */
 
-  while ((opt = getopt(argc, argv, "fspvko:c:")) != EOF) {
+  while ((opt = getopt(argc, argv, "fspvko:O:c:")) != EOF) {
     switch (opt) {
     case 'c':
       commands = 1;
@@ -3271,6 +3344,19 @@ int main(int argc, char *argv[])
       regf_opt += 2;
       break;
 
+    case 'O':
+      def_owner_sid_str = strdup(optarg);
+      regf_opt += 2;
+      if (!string_to_sid(&lsid, def_owner_sid_str)) {
+	fprintf(stderr, "Default Owner SID: %s is incorrectly formatted\n",
+		def_owner_sid_str);
+	free(def_owner_sid_str);
+	def_owner_sid_str = NULL;
+      }
+      else 
+	nt_delete_sid(lsid);
+      break;
+
     case 'p':
       print_keys++;
       regf_opt++;
@@ -3298,6 +3384,17 @@ int main(int argc, char *argv[])
     }
   }
 
+  /*
+   * We only want to complain about the lack of a default owner SID if
+   * we need one. This approximates that need 
+   */
+  if (!def_owner_sid_str) {
+    def_owner_sid_str = "S-1-5-21-1-2-3-4";
+    if (out_file_name || verbose)
+      fprintf(stderr, "Warning, default owner SID not set. Setting to %s\n",
+	      def_owner_sid_str);
+  }
+
   if ((regf = nt_create_regf()) == NULL) {
     fprintf(stderr, "Could not create registry object: %s\n", strerror(errno));
     exit(2);
-- 
cgit 


From cd8b806f1c2004dfaebb9da32664e06b92d7e24c Mon Sep 17 00:00:00 2001
From: Richard Sharpe 
Date: Mon, 21 Apr 2003 06:59:43 +0000
Subject: Correct comments about breadth first, as the registry tree is stored
 in a depth first fashion in the file.

Also add some more infrastructure needed to handle storing these trees.
(This used to be commit f993f7187c7ae49f443aa1966584aa88787bd7ca)
---
 source3/utils/editreg.c | 30 ++++++++++++++++++++++++++++--
 1 file changed, 28 insertions(+), 2 deletions(-)

diff --git a/source3/utils/editreg.c b/source3/utils/editreg.c
index 72ae17a45f..c00d9c22cb 100644
--- a/source3/utils/editreg.c
+++ b/source3/utils/editreg.c
@@ -328,6 +328,16 @@ Hope this helps....  (Although it was "fun" for me to uncover this things,
 
 #define CVAL(buf) ((unsigned char)*((unsigned char *)(buf)))
 
+#define SIVAL(buf, val) \
+                    ((unsigned char)buf[0]=(unsigned char)((val)&0xFF),\
+                     (unsigned char)buf[1]=(unsigned char)(((val)>>8)&0xFF),\
+                     (unsigned char)buf[2]=(unsigned char)(((val)>>16)&0xFF),\
+                     (unsigned char)buf[3]=(unsigned char)((val)>>24))
+
+#define SSVAL(buf, val) \
+                    ((unsigned char)buf[0]=(unsigned char)((val)&0xFF),\
+                     (unsigned char)buf[1]=(unsigned char)(((val)>>8)&0xFF))
+
 static int verbose = 0;
 static int print_security = 0;
 static int full_print = 0;
@@ -2403,15 +2413,29 @@ int nt_load_registry(REGF *regf)
 typedef struct hbin_blk_s {
   struct hbin_blk_s *next;
   unsigned int file_offset;  /* Offset in file                */
-  unsigned int free_space;    /* Amount of free space in block */
+  unsigned int free_space;   /* Amount of free space in block */
   unsigned int fsp_off;      /* Start of free space in block  */
+  int complete, stored;
 } HBIN_BLK;
 
+/*
+ * Allocate a new hbin block and link it to the others.
+ */
+int nt_create_hbin_blk(REGF *regf)
+{
+
+  return 0;
+}
+
 /*
  * Store a KEY in the file ...
+ *
+ * We store this depth first, and defer storing the lf struct until
+ * all the sub-keys have been stored.
  */
 int nt_store_reg_key(REGF *regf, REG_KEY *key)
 {
+  NK_HDR *nk_hdr; 
 
   return 0;
 }
@@ -2429,9 +2453,11 @@ int nt_store_reg_header(REGF *regf){
  * We write out the header and then each of the keys etc into the file
  * We have to flatten the data structure ...
  *
- * The structures are stored in a breadth-first fashion, with all records
+ * The structures are stored in a depth-first fashion, with all records
  * aligned on 8-byte boundaries, with sub-keys and values layed down before
  * the lists that contain them. SK records are layed down first, however.
+ * The lf fields are layed down after all sub-keys have been layed down, it
+ * seems, including the whole tree associated with each sub-key.
  */
 int nt_store_registry(REGF *regf)
 {
-- 
cgit 


From 61922ee4363bd090bafd7a9ea7e6b2f2b3709e87 Mon Sep 17 00:00:00 2001
From: Andrew Bartlett 
Date: Mon, 21 Apr 2003 11:45:46 +0000
Subject: Use fstrcpy/pstrcpy when that's what we really mean...

Andrew Bartlett
(This used to be commit e8aa615591dc44de4de85322d455a47b3122b9eb)
---
 source3/smbd/password.c | 6 +++---
 source3/smbd/service.c  | 7 ++++---
 2 files changed, 7 insertions(+), 6 deletions(-)

diff --git a/source3/smbd/password.c b/source3/smbd/password.c
index 784c1525c8..175c1ec3a9 100644
--- a/source3/smbd/password.c
+++ b/source3/smbd/password.c
@@ -249,7 +249,7 @@ void add_session_user(const char *user)
 
   if (!(passwd = Get_Pwnam(user))) return;
 
-  StrnCpy(suser,passwd->pw_name,sizeof(suser)-1);
+  fstrcpy(suser,passwd->pw_name);
 
   if (suser && *suser && !in_list(suser,session_users,False))
     {
@@ -447,7 +447,7 @@ and given password ok\n", user));
 	if (!ok && lp_username(snum)) {
 		char *auser;
 		pstring user_list;
-		StrnCpy(user_list,lp_username(snum),sizeof(pstring));
+		pstrcpy(user_list,lp_username(snum));
 		
 		pstring_sub(user_list,"%S",lp_servicename(snum));
 		
@@ -477,7 +477,7 @@ and given password ok (%s)\n", user));
 	/* check for a normal guest connection */
 	if (!ok && GUEST_OK(snum)) {
 		fstring guestname;
-		StrnCpy(guestname,lp_guestaccount(),sizeof(guestname)-1);
+		fstrcpy(guestname,lp_guestaccount());
 		if (Get_Pwnam(guestname)) {
 			fstrcpy(user,guestname);
 			ok = True;
diff --git a/source3/smbd/service.c b/source3/smbd/service.c
index 18a92bc82f..cfb5e0e414 100644
--- a/source3/smbd/service.c
+++ b/source3/smbd/service.c
@@ -486,13 +486,14 @@ static connection_struct *make_connection_snum(int snum, user_struct *vuser,
 		pstring tmp_gname;
 		BOOL user_must_be_member = False;
 		
-		StrnCpy(tmp_gname,lp_force_group(snum),sizeof(pstring)-1);
+		pstrcpy(tmp_gname,lp_force_group(snum));
 		
 		if (tmp_gname[0] == '+') {
 			user_must_be_member = True;
-			StrnCpy(gname,&tmp_gname[1],sizeof(pstring)-2);
+			/* even now, tmp_gname is null terminated */
+			pstrcpy(gname,&tmp_gname[1]);
 		} else {
-			StrnCpy(gname,tmp_gname,sizeof(pstring)-1);
+			pstrcpy(gname,tmp_gname);
 		}
 		/* default service may be a group name 		*/
 		pstring_sub(gname,"%S",lp_servicename(snum));
-- 
cgit 


From 76a0be1dbac56c8631a373151799dda2d64714f9 Mon Sep 17 00:00:00 2001
From: Andrew Bartlett 
Date: Mon, 21 Apr 2003 11:47:27 +0000
Subject: Remove unused (#ifdef'ed) code. (This used to be commit
 c11465b285d5eb3c42a84095a5dc41af7e07267d)

---
 source3/smbd/statcache.c | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/source3/smbd/statcache.c b/source3/smbd/statcache.c
index 0f42a3a83f..44bae48990 100644
--- a/source3/smbd/statcache.c
+++ b/source3/smbd/statcache.c
@@ -128,18 +128,6 @@ void stat_cache_add( const char *full_orig_name, const char *orig_translated_pat
 	  original_path_length = translated_path_length;
   }
 
-#if 0
-  /*
-   * We will only replace namelen characters 
-   * of full_orig_name.
-   * StrnCpy always null terminates.
-   */
-
-  smbStrnCpy(orig_name, full_orig_name, namelen);
-  if(!case_sensitive)
-    strupper( orig_name );
-#endif
-
   /*
    * Check this name doesn't exist in the cache before we 
    * add it.
-- 
cgit 


From af4ebfd970f55c315076b31373f2c4a23ecb709c Mon Sep 17 00:00:00 2001
From: Andrew Bartlett 
Date: Mon, 21 Apr 2003 12:17:02 +0000
Subject: For NTLM2 (not yet even close to real implementation) we must use the
 server hash for checking the server's signiture.

Andrew Bartlett
(This used to be commit 61255a2b3694ba13c72a2a33e5956d14c7d4d2c1)
---
 source3/libsmb/ntlmssp_sign.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source3/libsmb/ntlmssp_sign.c b/source3/libsmb/ntlmssp_sign.c
index 5426263fb9..86faf1f5e6 100644
--- a/source3/libsmb/ntlmssp_sign.c
+++ b/source3/libsmb/ntlmssp_sign.c
@@ -121,7 +121,7 @@ static NTSTATUS ntlmssp_make_packet_signiture(NTLMSSP_CLIENT_STATE *ntlmssp_stat
 			NTLMSSPcalc_ap(ntlmssp_state->cli_sign_hash,  sig->data, sig->length);
 			break;
 		case NTLMSSP_RECEIVE:
-			NTLMSSPcalc_ap(ntlmssp_state->cli_sign_hash,  sig->data, sig->length);
+			NTLMSSPcalc_ap(ntlmssp_state->srv_sign_hash,  sig->data, sig->length);
 			break;
 		}
 	} else {
-- 
cgit 


From a0a4b2b5950f8e495c51691e2fb9dcade2bfa2ce Mon Sep 17 00:00:00 2001
From: John Terpstra 
Date: Mon, 21 Apr 2003 14:39:16 +0000
Subject: More updates - still a work in progress. (This used to be commit
 63589f958b399534bc0bc8c50213ad2f6a380689)

---
 docs/docbook/projdoc/NT4Migration.sgml | 224 ++++++++++++++++++++++++++++-----
 1 file changed, 195 insertions(+), 29 deletions(-)

diff --git a/docs/docbook/projdoc/NT4Migration.sgml b/docs/docbook/projdoc/NT4Migration.sgml
index 1a31def2fe..98b5cbe995 100644
--- a/docs/docbook/projdoc/NT4Migration.sgml
+++ b/docs/docbook/projdoc/NT4Migration.sgml
@@ -66,7 +66,7 @@ Possible motivations to make a change include:
 
 
 
-It is vital that oit be well recognised that Samba-3 is NOT MS Windows NT4. Samba-3 offers
+It is vital that it be well recognised that Samba-3 is NOT MS Windows NT4. Samba-3 offers
 an alternative solution that is both different from MS Windows NT4 and that offers some
 advantages compared with it. It should also be recognised that Samba-3 lacks many of the
 features that Microsoft has promoted as core values in migration from MS Windows NT4 to 
@@ -164,7 +164,7 @@ and network bandwidth.
 A physical network segment may house several domains, each of which may span multiple network segments.
 Where domains span routed network segments it is most advisable to consider and test the performance
 implications of the design and layout of a network. A Centrally located domain controller that is being
-designed to server mulitple route network segments may result in severe performance problems if the
+designed to serve mulitple routed network segments may result in severe performance problems if the
 response time (eg: ping timing) between the remote segment and the PDC is more than 100 ms. In situations
 where the delay is too long it is highly recommended to locate a backup controller (BDC) to serve as
 the local authentication and access control server.
@@ -252,7 +252,7 @@ to be changed to the SID of the Samba-3 domain.
 
 
 It is possible to migrate all account settings from an MS Windows NT4 domain to Samba-3. Before
- attempting to migrate user and group accounts it is STRONGLY advised to create in Samba-3 the
+attempting to migrate user and group accounts it is STRONGLY advised to create in Samba-3 the
 groups that are present on the MS Windows NT4 domain AND to connect these to
 suitable Unix/Linux groups. Following this simple advice will mean that all user and group attributes
 should migrate painlessly.
@@ -265,8 +265,7 @@ should migrate painlessly.
 Steps In Migration Process
 
 
-This is not a definitive ste-by-step process yet - just a place holder so the info 
-is not lost.
+The approximate migration process is described below.
 
 
 
@@ -279,51 +278,218 @@ Samba-3 set up as a DC with netlogon share, profile share, etc.
 
 
 
-
-Process:
-	Create a BDC account for the samba server using NT Server Manager
-		- Samba must NOT be running
+The Account Migration Process
+	Create a BDC account for the samba server using NT Server Manager
+		Samba must NOT be running
+
+	
+	rpcclient NT4PDC -U Administrator%passwd
+		lsaquery
+		 	  Note the SID returned
+		
+	
+
+	net getsid -S NT4PDC -w DOMNAME -U Administrator%passwd
+		Note the SID
+	
 
-	rpcclient NT4PDC -U Administrator%passwd
-		lsaquery
+	net getlocalsid
+		
+		Note the SID, now check that all three SIDS reported are the same!
+		
+	
 
-		Note the SID returned by step b.
+	net rpc join -S NT4PDC -w DOMNAME -U Administrator%passwd
 
-	net getsid -S NT4PDC -w DOMNAME -U Administrator%passwd
+	net rpc vampire -S NT4PDC -U administrator%passwd
 
-		Note the SID in step c.
+	pdbedit -l
+		Note - did the users migrate?
+	
 
-	net getlocalsid
+	initGrps.sh DOMNAME
 
-		Note the SID, now check that all three SIDS reported are the same!
+	smbgroupedit -v
+		Now check that all groups are recognised
+	
 
-	net rpc join -S NT4PDC -w DOMNAME -U Administrator%passwd
+	net rpc campire -S NT4PDC -U administrator%passwd
+
+	pdbedit -lv
+		
+			Note - check that all group membership has been migrated
+		
+	
+
+
+
+Now it is time to migrate all the profiles, then migrate all policy files.
+More later.
+
 
-	net rpc vampire -S NT4PDC -U administrator%passwd
+
+
 
-	pdbedit -l
+
+Migration Options
 
-		Note - did the users migrate?
+
+Based on feedback from many sites as well as from actual installation and maintenance
+experience sites that wish to migrate from MS Windows NT4 Domain Control to a Samba
+based solution fit into three basic categories.
+
 
-	initGrps.sh DOMNAME
+The 3 Major Site Types
+
+	
+	Number of UsersDescription
+	
+	
+	< 50Want simple conversion with NO pain
+	50 - 250Want new features, can manage some in-house complexity
+	> 250Solution/Implementation MUST scale well, complex needs. Cross departmental decision process. Local expertise in most areas
+	
+
+
    
 
-	smbgroupedit -v
+
+Planning for Success
 
-		Now check that all groups are recognised
+
+There are three basic choices for sites that intend to migrate from MS Windwows NT4
+to Samba-3.
+
 
-	net rpc campire -S NT4PDC -U administrator%passwd
+
+	
+	Simple Conversion (total replacement)
+	
 
-	pdbedit -lv
+	
+	Upgraded Conversion (could be one of integration)
+	
 
-		Note - check that all group membership has been migrated.
-    
+	
+	Complete Redesign (completely new solution)
+	
+
 
 
-Now it is time to migrate all the profiles, then migrate all policy files.
-More later.
+No matter what choice you make, the following rules will minimise down-stream problems:
 
 
+
+	
+	Take sufficient time
+	
+
+	
+	Avoid Panic
+	
+
+	
+	Test ALL assumptions
+	
+
+	
+	Test full roll-out program, including workstation deployment
+	
+
+
+Nature of the Conversion Choices
+
+	
+	SimpleUpgradedRedesign
+	
+	
+	
+	Make use of minimal OS specific features
+	Translate NT4 features to new host OS features
+	Decide:
+	
+	
+	Suck all accounts from NT4 into Samba-3
+	Copy and improve:
+	Authentication Regime (database location and access)
+	
+	
+	Make least number of operational changes
+	Make progressive improvements
+	Desktop Management Methods
+	
+	
+	Take least amount of time to migrate
+	Minimise user impact
+	Better Control of Desktops / Users
+	
+	
+	Live versus Isolated Conversion
+	Maximise functionality
+	Identify Needs for: Manageability, Scalability, Security, Availability
+	
+	
+	Integrate Samba-3 then migrate while users are active, then Change of control (ie: swap out)
+	Take advantage of lower maintenance opportunity
+	
+	
+	
+
+
    
 
+
+
+Samba Implementation Choices
+
+
+Authentication database back end
+	Winbind (external Samba or NT4/200x server)
+	Can use pam_mkhomedir.so to auto-create home dirs
+	External server could use Active Directory or NT4 Domain
+Database type
+	smbpasswd, tdbsam, ldapsam, MySQLsam
+		With local accounts or with No Unix Accounts (NUA option)
+Access Control Points
+	On the Share itself (Use NT4 Server Manager)
+	On the file system
+	Unix permissions on files and directories
+	Posix ACLs enablement in file system?
+	Through Samba share parameters
+		Not recommended - except as only resort
+Policies (migrate or create new ones)
+	Group Policy Editor (NT4)
+	Watch out for Tattoo effect
+User and Group Profiles
+	Platform specific so use platform tool to change from a Local to a Roaming profile
+	Can use new profiles tool to change SIDs (NTUser.DAT)
+Logon Scripts (Know how they work)
+User and Group mapping to Unix/Linux
+	username map facility may be needed
+	Use smbgroupedit to connect NT4 groups to Unix groups
+	Use pdbedit to set/change user configuration
+NOTE:
+If migrating to LDAP back end it may be easier to dump initial LDAP database to LDIF, then edit, then reload into LDAP
+	OS specific scripts / programs may be needed
+		Add / delete Users
+			Note OS limits on size of name (Linux 8 chars)
+				NT4 up to 254 chars
+		Add / delete machines
+			Applied only to domain members (note up to 16 chars)
+		Add / delete Groups
+			Note OS limits on size and nature
+				Linux limit is 16 char, no spaces and no upper case chars (groupadd)
+
+Migration Tools
+	Domain Control (NT4 Style)
+	Profiles, Policies, Access Controls, Security
+Migration Tools
+	Samba: net, rpcclient, smbpasswd, pdbedit, smbgroupedit, profiles
+	Windows: NT4 Domain User Manager, Server Manager (NEXUS)
+Authentication
+	New SAM back end (smbpasswd, tdbsam, ldapsam, mysqlsam)
+		With of without Unix Accounts (NUA)
+
+
+
 
 
 
-- 
cgit 


From 9c356a379d0e42405ca4809beefd272697cc215b Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij 
Date: Mon, 21 Apr 2003 14:59:38 +0000
Subject: Remove obsolete information from Speed.sgml and move client-specific
 info to Other-Clients.sgml (This used to be commit
 b0d5e1b177808c3bd3494d0b2f6cf4c8c4bcfdd5)

---
 docs/docbook/projdoc/Other-Clients.sgml |  32 +++++-
 docs/docbook/projdoc/Speed.sgml         | 170 ++++----------------------------
 2 files changed, 52 insertions(+), 150 deletions(-)

diff --git a/docs/docbook/projdoc/Other-Clients.sgml b/docs/docbook/projdoc/Other-Clients.sgml
index 6177b4dcb6..73316927e0 100644
--- a/docs/docbook/projdoc/Other-Clients.sgml
+++ b/docs/docbook/projdoc/Other-Clients.sgml
@@ -168,7 +168,8 @@ packages, Samba, and Linux (and other UNIX-based systems) see
 Use latest TCP/IP stack from Microsoft
 
 Use the latest TCP/IP stack from microsoft if you use Windows
-for workgroups.
+for workgroups. 
+
 
 The early TCP/IP stacks had lots of bugs.
 
@@ -233,6 +234,24 @@ WfWg. For some reason if you leave Netbeui as the default
 it may break the print queue reporting on some systems.
 It is presumably a WfWg bug.
 
+
+
+
+Speed improvement
+
+
+Note that some people have found that setting DefaultRcvWindow in
+the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a
+big improvement. I don't know why.
+
+
+
+My own experience wth DefaultRcvWindow is that I get much better
+performance with a large value (16384 or larger). Other people have
+reported that anything over 3072 slows things down enourmously. One
+person even reported a speed drop of a factor of 30 when he went from
+3072 to 8192. I don't know why.
+
 
 
 
@@ -266,6 +285,17 @@ OutLook and you may also notice a significant speedup when accessing network
 neighborhood services.
 
 
+
+Speed improvement
+
+
+Configure the win95 TCPIP registry settings to give better
+performance. I use a program called MTUSPEED.exe which I got off the
+net. There are various other utilities of this type freely available.
+
+
+
+
 
 
 
diff --git a/docs/docbook/projdoc/Speed.sgml b/docs/docbook/projdoc/Speed.sgml
index 78b5935a9c..753810c1d8 100644
--- a/docs/docbook/projdoc/Speed.sgml
+++ b/docs/docbook/projdoc/Speed.sgml
@@ -62,7 +62,7 @@ line with the -O option, or in the smb.conf file.
 
 
 
-The "socket options" section of the smb.conf manual page describes how
+The socket options section of the &smb.conf; manual page describes how
 to set these and gives recommendations.
 
 
@@ -75,9 +75,9 @@ much. The correct settings are very dependent on your local network.
 
 The socket option TCP_NODELAY is the one that seems to make the
 biggest single difference for most networks. Many people report that
-adding "socket options = TCP_NODELAY" doubles the read performance of
-a Samba drive. The best explanation I have seen for this is that the
-Microsoft TCP/IP stack is slow in sending tcp ACKs.
+adding socket options = TCP_NODELAY doubles the read 
+performance of a Samba drive. The best explanation I have seen for this is
+that the Microsoft TCP/IP stack is slow in sending tcp ACKs.
 
 
 
@@ -86,9 +86,9 @@ Microsoft TCP/IP stack is slow in sending tcp ACKs.
 Read size
 
 
-The option "read size" affects the overlap of disk reads/writes with
-network reads/writes. If the amount of data being transferred in
-several of the SMB commands (currently SMBwrite, SMBwriteX and
+The option read size affects the overlap of disk
+reads/writes with network reads/writes. If the amount of data being
+transferred in several of the SMB commands (currently SMBwrite, SMBwriteX and
 SMBreadbraw) is larger than this value then the server begins writing
 the data before it has received the whole packet from the network, or
 in the case of SMBreadbraw, it begins writing to the network before
@@ -114,10 +114,10 @@ pointless and will cause you to allocate memory unnecessarily.
 Max xmit
 
 
-At startup the client and server negotiate a "maximum transmit" size,
+At startup the client and server negotiate a maximum transmit size,
 which limits the size of nearly all SMB commands. You can set the
-maximum size that Samba will negotiate using the "max xmit = " option
-in smb.conf. Note that this is the maximum size of SMB request that 
+maximum size that Samba will negotiate using the max xmit =  option
+in &smb.conf;. Note that this is the maximum size of SMB request that 
 Samba will accept, but not the maximum size that the *client* will accept.
 The client maximum receive size is sent to Samba by the client and Samba
 honours this limit.
@@ -139,7 +139,7 @@ In most cases the default is the best option.
 Log level
 
 
-If you set the log level (also known as "debug level") higher than 2
+If you set the log level (also known as debug level) higher than 2
 then you may suffer a large drop in performance. This is because the
 server flushes the log file after each operation, which can be very
 expensive. 
@@ -150,20 +150,20 @@ expensive.
 Read raw
 
 
-The "read raw" operation is designed to be an optimised, low-latency
+The read raw operation is designed to be an optimised, low-latency
 file read operation. A server may choose to not support it,
-however. and Samba makes support for "read raw" optional, with it
+however. and Samba makes support for read raw optional, with it
 being enabled by default.
 
 
 
-In some cases clients don't handle "read raw" very well and actually
+In some cases clients don't handle read raw very well and actually
 get lower performance using it than they get using the conventional
 read operations. 
 
 
 
-So you might like to try "read raw = no" and see what happens on your
+So you might like to try read raw = no and see what happens on your
 network. It might lower, raise or not affect your performance. Only
 testing can really tell.
 
@@ -174,43 +174,25 @@ testing can really tell.
 Write raw
 
 
-The "write raw" operation is designed to be an optimised, low-latency
+The write raw operation is designed to be an optimised, low-latency
 file write operation. A server may choose to not support it,
-however. and Samba makes support for "write raw" optional, with it
+however. and Samba makes support for write raw optional, with it
 being enabled by default.
 
 
 
-Some machines may find "write raw" slower than normal write, in which
+Some machines may find write raw slower than normal write, in which
 case you may wish to change this option.
 
 
 
 
-
-Slow Clients
-
-
-One person has reported that setting the protocol to COREPLUS rather
-than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).
-
-
-
-I suspect that his PC's (386sx16 based) were asking for more data than
-they could chew. I suspect a similar speed could be had by setting
-"read raw = no" and "max xmit = 2048", instead of changing the
-protocol. Lowering the "read size" might also help.
-
-
-
-
 
 Slow Logins
 
 
 Slow logins are almost always due to the password checking time. Using
-the lowest practical "password level" will improve things a lot. You
-could also enable the "UFC crypt" option in the Makefile.
+the lowest practical password level will improve things. 
 
 
 
@@ -221,118 +203,8 @@ could also enable the "UFC crypt" option in the Makefile.
 
 Often a speed problem can be traced to the client. The client (for
 example Windows for Workgroups) can often be tuned for better TCP
-performance.
-
-
-
-See your client docs for details. In particular, I have heard rumours
-that the WfWg options TCPWINDOWSIZE and TCPSEGMENTSIZE can have a
-large impact on performance.
-
-
-
-Also note that some people have found that setting DefaultRcvWindow in
-the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a
-big improvement. I don't know why.
-
-
-
-My own experience wth DefaultRcvWindow is that I get much better
-performance with a large value (16384 or larger). Other people have
-reported that anything over 3072 slows things down enourmously. One
-person even reported a speed drop of a factor of 30 when he went from
-3072 to 8192. I don't know why.
-
-
-
-It probably depends a lot on your hardware, and the type of unix box
-you have at the other end of the link.
-
-
-
-Paul Cochrane has done some testing on client side tuning and come 
-to the following conclusions:
-
-
-
-Install the W2setup.exe file from www.microsoft.com. This is an 
-update for the winsock stack and utilities which improve performance.
-
-
-
-Configure the win95 TCPIP registry settings to give better 
-perfomance. I use a program called MTUSPEED.exe which I got off the 
-net. There are various other utilities of this type freely available. 
-The setting which give the best performance for me are:
-
-
-
-
-MaxMTU                  Remove
-
-
-RWIN                    Remove
-
-
-MTUAutoDiscover         Disable
-
-
-MTUBlackHoleDetect      Disable
-
-
-Time To Live            Enabled
-
-
-Time To Live - HOPS     32
-
-
-NDI Cache Size          0
-
-
-
-
-I tried virtually all of the items mentioned in the document and 
-the only one which made a difference to me was the socket options. It 
-turned out I was better off without any!!!!!
-
-
-
-In terms of overall speed of transfer, between various win95 clients 
-and a DX2-66 20MB server with a crappy NE2000 compatible and old IDE 
-drive (Kernel 2.0.30). The transfer rate was reasonable for 10 baseT.
-
-
-
-
-The figures are:          Put              Get 
-P166 client 3Com card:    420-440kB/s      500-520kB/s
-P100 client 3Com card:    390-410kB/s      490-510kB/s
-DX4-75 client NE2000:     370-380kB/s      330-350kB/s
-
-
-
-
-I based these test on transfer two files a 4.5MB text file and a 15MB 
-textfile. The results arn't bad considering the hardware Samba is 
-running on. It's a crap machine!!!!
-
-
-
-The updates mentioned in 1 and 2 brought up the transfer rates from 
-just over 100kB/s in some clients.
-
-
-
-A new client is a P333 connected via a 100MB/s card and hub. The 
-transfer rates from this were good: 450-500kB/s on put and 600+kB/s 
-on get.
-
-
-
-Looking at standard FTP throughput, Samba is a bit slower (100kB/s 
-upwards). I suppose there is more going on in the samba protocol, but 
-if it could get up to the rate of FTP the perfomance would be quite 
-staggering.
+performance. Check the sections on the various clients in 
+Samba and Other Clients.
 
 
 
-- 
cgit 


From 156014a529479b0b3f585d43e7a1f13adc622103 Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij 
Date: Mon, 21 Apr 2003 15:19:16 +0000
Subject: Fix syntax error (This used to be commit
 e76eaf0f17de19eb2492572b0c79fc4b2657c504)

---
 docs/docbook/projdoc/NT4Migration.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/docbook/projdoc/NT4Migration.sgml b/docs/docbook/projdoc/NT4Migration.sgml
index 98b5cbe995..5799841feb 100644
--- a/docs/docbook/projdoc/NT4Migration.sgml
+++ b/docs/docbook/projdoc/NT4Migration.sgml
@@ -500,7 +500,7 @@ There are 3 major Site Types:
 
 
 
-<= 50 Users
+<= 50 Users
 Want simple conversion with NO pain
 50 - 250 Users
 Want new features, can manage some in-house complexity
@@ -591,7 +591,7 @@ Windows: NT4 Domain User Manager, Server Manager (NEXUS)
 Authentication
 New SAM back end (smbpasswd, tdbsam, ldapsam, mysqlsam)
 With of without Unix Accounts (NUA)
-
+
 
 
 
-- 
cgit 


From f66bbf3c088ee980876599343c083980f884d661 Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij 
Date: Mon, 21 Apr 2003 15:19:34 +0000
Subject: Create ../textdocs, ../htmldocs or ../manpages if they don't exist
 already (This used to be commit 8dc7087cf0306271e07a25ac2538206ef3eaa497)

---
 docs/docbook/Makefile.in | 30 ++++++++++++++++++++++--------
 1 file changed, 22 insertions(+), 8 deletions(-)

diff --git a/docs/docbook/Makefile.in b/docs/docbook/Makefile.in
index e44108401d..0739f43f84 100644
--- a/docs/docbook/Makefile.in
+++ b/docs/docbook/Makefile.in
@@ -68,19 +68,22 @@ everything: manpages ps pdf html-single html htmlman txt htmlfaq
 
 # Global rules
 
-manpages: $(MANPAGES)
-pdf: $(PDFDIR)/Samba-HOWTO-Collection.pdf ../Samba-Developers-Guide.pdf
-ps: $(PSDIR)/Samba-HOWTO-Collection.ps ../Samba-Developers-Guide.ps
-txt: $(TXTDIR)/Samba-HOWTO-Collection.txt $(TXTDIR)/Samba-Developers-Guide.txt
-htmlman:  $(MANPAGES_HTML)
-htmlfaq: 
+manpages: $(MANDIR) $(MANPAGES)
+pdf: $(PDFDIR) $(PDFDIR)/Samba-HOWTO-Collection.pdf ../Samba-Developers-Guide.pdf
+ps: $(PSDIR) $(PSDIR)/Samba-HOWTO-Collection.ps ../Samba-Developers-Guide.ps
+txt: $(TXTDIR) $(TXTDIR)/Samba-HOWTO-Collection.txt $(TXTDIR)/Samba-Developers-Guide.txt
+htmlman: $(HTMLDIR) $(MANPAGES_HTML)
+htmlfaq: $(HTMLDIR)
 	$(DOCBOOK2HTML) -d samba.dsl -o $(FAQDIR) $(FAQPROJDOC)/sambafaq.sgml
-html-single: $(HTMLDIR)/Samba-HOWTO-Collection.html  $(HTMLDIR)/Samba-Developers-Guide.html
-html:
+html-single: $(HTMLDIR) $(HTMLDIR)/Samba-HOWTO-Collection.html  $(HTMLDIR)/Samba-Developers-Guide.html
+html: $(HTMLDIR)
 	$(DOCBOOK2HTML) -d samba.dsl -o $(HTMLDIR) $(PROJDOC)/samba-doc.sgml
 
 # Text files
 
+$(TXTDIR): 
+	mkdir $(TXTDIR)
+
 $(TXTDIR)/Samba-HOWTO-Collection.txt: $(PROJDOC)/samba-doc.sgml
 	$(DOCBOOK2TXT) -d samba.dsl -o . $<
 	mv ./samba-doc.txt $@
@@ -91,6 +94,9 @@ $(TXTDIR)/Samba-Developers-Guide.txt: $(DEVDOC)/dev-doc.sgml
 
 # PostScript
 
+$(PSDIR):
+	mkdir $(PSDIR)
+
 $(PSDIR)/Samba-HOWTO-Collection.ps: $(PROJDOC)/samba-doc.sgml
 	$(DOCBOOK2PS) -d samba.dsl -o . $<
 	mv ./samba-doc.ps $@
@@ -109,6 +115,9 @@ $(PDFDIR)/Samba-Developers-Guide.pdf: $(HTMLDIR)/Samba-Developers-Guide.html
 
 # Single large HTML files
 
+$(HTMLDIR):
+	mkdir $(HTMLDIR)
+
 $(HTMLDIR)/Samba-HOWTO-Collection.html: $(PROJDOC)/samba-doc.sgml
 	$(DOCBOOK2HTML) -d samba.dsl -u -o . $<
 	mv ./samba-doc.html $@
@@ -121,6 +130,11 @@ $(HTMLDIR)/Samba-Developers-Guide.html: $(DEVDOC)/dev-doc.sgml
 $(HTMLDIR)/%.html: $(MANPROJDOC)/%.sgml
 	$(DOCBOOK2HTML) -d samba.dsl -u -o $(HTMLDIR) $<
 
+# Manpages
+
+$(MANDIR): 
+	mkdir $(MANDIR)
+
 $(MANDIR)/%: $(MANPROJDOC)/%.sgml 
 	$(DOCBOOK2MAN) -d samba.dsl -o $(MANDIR) $<
 	$(PERL) scripts/strip-links.pl < $@ > $@.temp
-- 
cgit 


From 78476119faf62ace4f6cbda66b56d00aa63a5ed6 Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij 
Date: Mon, 21 Apr 2003 16:04:54 +0000
Subject: Add new part 'Troubleshooting' (This used to be commit
 a24e89ea443fbe77924cccf7e7679aec80a05088)

---
 docs/docbook/projdoc/samba-doc.sgml | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/docs/docbook/projdoc/samba-doc.sgml b/docs/docbook/projdoc/samba-doc.sgml
index 328287ee04..de3c9e2974 100644
--- a/docs/docbook/projdoc/samba-doc.sgml
+++ b/docs/docbook/projdoc/samba-doc.sgml
@@ -95,6 +95,13 @@ for various environments.
 &unicode;
 
 
+
+Troubleshooting
+&Diagnosis;
+&problems;
+&BUGS;
+
+
 
 Appendixes
 &Compiling;
@@ -103,8 +110,5 @@ for various environments.
 &Other-Clients;
 &SWAT;
 &SPEED;
-&Diagnosis;
-&problems;
-&BUGS;
 
 
-- 
cgit 


From c0ac957fc2f177f3349b8b763fbd54ade14da56c Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij 
Date: Mon, 21 Apr 2003 16:16:31 +0000
Subject: Move information about locking to seperate chapter and information
 about scope id's to the faq (This used to be commit
 f2c333822f34be8a2bb85124319ead4dc44c2891)

---
 docs/docbook/projdoc/UNIX_INSTALL.sgml | 67 ----------------------------------
 docs/docbook/projdoc/locking.sgml      | 60 ++++++++++++++++++++++++++++++
 docs/docbook/projdoc/samba-doc.sgml    |  1 +
 3 files changed, 61 insertions(+), 67 deletions(-)
 create mode 100644 docs/docbook/projdoc/locking.sgml

diff --git a/docs/docbook/projdoc/UNIX_INSTALL.sgml b/docs/docbook/projdoc/UNIX_INSTALL.sgml
index 239ccd168b..1019e524f7 100644
--- a/docs/docbook/projdoc/UNIX_INSTALL.sgml
+++ b/docs/docbook/projdoc/UNIX_INSTALL.sgml
@@ -172,72 +172,5 @@
 	Samba has been successfully installed at thousands of sites worldwide,
 	so maybe someone else has hit your problem and has overcome it. 
 
-	
-		Scope IDs
-
-		By default Samba uses a blank scope ID. This means 
-		all your windows boxes must also have a blank scope ID. 
-		If you really want to use a non-blank scope ID then you will 
-		need to use the 'netbios scope' smb.conf option.
-        All your PCs will need to have the same setting for 
-		this to work. I do not recommend scope IDs.
-	
-
-	
-		Locking
-
-		One area which sometimes causes trouble is locking.
-
-		There are two types of locking which need to be 
-		performed by a SMB server. The first is "record locking" 
-		which allows a client to lock a range of bytes in a open file. 
-		The second is the "deny modes" that are specified when a file 
-		is open.
-
-		Record locking semantics under Unix is very
-		different from record locking under Windows. Versions
-		of Samba before 2.2 have tried to use the native
-		fcntl() unix system call to implement proper record
-		locking between different Samba clients. This can not
-		be fully correct due to several reasons. The simplest
-		is the fact that a Windows client is allowed to lock a
-		byte range up to 2^32 or 2^64, depending on the client
-		OS. The unix locking only supports byte ranges up to
-		2^31. So it is not possible to correctly satisfy a
-		lock request above 2^31. There are many more
-		differences, too many to be listed here.
-
-		Samba 2.2 and above implements record locking
-		completely independent of the underlying unix
-		system. If a byte range lock that the client requests
-		happens to fall into the range 0-2^31, Samba hands
-		this request down to the Unix system. All other locks
-		can not be seen by unix anyway.
-
-		Strictly a SMB server should check for locks before 
-		every read and write call on a file. Unfortunately with the 
-		way fcntl() works this can be slow and may overstress the 
-		rpc.lockd. It is also almost always unnecessary as clients 
-		are supposed to independently make locking calls before reads 
-		and writes anyway if locking is important to them. By default 
-		Samba only makes locking calls when explicitly asked
-		to by a client, but if you set "strict locking = yes" then it will
-		make lock checking calls on every read and write. 
-
-		You can also disable by range locking completely 
-		using "locking = no". This is useful for those shares that 
-		don't support locking or don't need it (such as cdroms). In 
-		this case Samba fakes the return codes of locking calls to 
-		tell clients that everything is OK.
-
-		The second class of locking is the "deny modes". These 
-		are set by an application when it opens a file to determine 
-		what types of access should be allowed simultaneously with 
-		its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE 
-		or DENY_ALL. There are also special compatibility modes called 
-		DENY_FCB and  DENY_DOS.
-
-		
-	
 	
 
diff --git a/docs/docbook/projdoc/locking.sgml b/docs/docbook/projdoc/locking.sgml
new file mode 100644
index 0000000000..ef65c16e2c
--- /dev/null
+++ b/docs/docbook/projdoc/locking.sgml
@@ -0,0 +1,60 @@
+
+
+	&author.jeremy;
+	&author.jelmer;
+
+
+Locking
+
+One area which sometimes causes trouble is locking.
+
+There are two types of locking which need to be 
+performed by a SMB server. The first is "record locking" 
+which allows a client to lock a range of bytes in a open file. 
+The second is the "deny modes" that are specified when a file 
+is open.
+
+Record locking semantics under Unix is very
+different from record locking under Windows. Versions
+of Samba before 2.2 have tried to use the native
+fcntl() unix system call to implement proper record
+locking between different Samba clients. This can not
+be fully correct due to several reasons. The simplest
+is the fact that a Windows client is allowed to lock a
+byte range up to 2^32 or 2^64, depending on the client
+OS. The unix locking only supports byte ranges up to
+2^31. So it is not possible to correctly satisfy a
+lock request above 2^31. There are many more
+differences, too many to be listed here.
+
+Samba 2.2 and above implements record locking
+completely independent of the underlying unix
+system. If a byte range lock that the client requests
+happens to fall into the range 0-2^31, Samba hands
+this request down to the Unix system. All other locks
+can not be seen by unix anyway.
+
+Strictly a SMB server should check for locks before 
+every read and write call on a file. Unfortunately with the 
+way fcntl() works this can be slow and may overstress the 
+rpc.lockd. It is also almost always unnecessary as clients 
+are supposed to independently make locking calls before reads 
+and writes anyway if locking is important to them. By default 
+Samba only makes locking calls when explicitly asked
+to by a client, but if you set "strict locking = yes" then it will
+make lock checking calls on every read and write. 
+
+You can also disable by range locking completely 
+using "locking = no". This is useful for those shares that 
+don't support locking or don't need it (such as cdroms). In 
+this case Samba fakes the return codes of locking calls to 
+tell clients that everything is OK.
+
+The second class of locking is the "deny modes". These 
+are set by an application when it opens a file to determine 
+what types of access should be allowed simultaneously with 
+its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE 
+or DENY_ALL. There are also special compatibility modes called 
+DENY_FCB and  DENY_DOS.
+
+
diff --git a/docs/docbook/projdoc/samba-doc.sgml b/docs/docbook/projdoc/samba-doc.sgml
index de3c9e2974..a0fc27fcb0 100644
--- a/docs/docbook/projdoc/samba-doc.sgml
+++ b/docs/docbook/projdoc/samba-doc.sgml
@@ -93,6 +93,7 @@ for various environments.
 &BROWSING;
 &SecuringSamba;
 &unicode;
+&locking;
 
 
 
-- 
cgit 


From ee399b147b37048ca21e715e41e069032ee0688f Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij 
Date: Mon, 21 Apr 2003 16:16:50 +0000
Subject: Add question about scope id's (This used to be commit
 2c258e5951aa35fc85b92cbf6d0b7ae1cbe8feb4)

---
 docs/docbook/faq/config.sgml   | 12 ++++++++++++
 docs/docbook/faq/general.sgml  | 41 +----------------------------------------
 docs/docbook/faq/printing.sgml |  1 +
 3 files changed, 14 insertions(+), 40 deletions(-)

diff --git a/docs/docbook/faq/config.sgml b/docs/docbook/faq/config.sgml
index db27102cdf..2c17c86c4e 100644
--- a/docs/docbook/faq/config.sgml
+++ b/docs/docbook/faq/config.sgml
@@ -22,4 +22,16 @@ add users to this database using "smbpasswd -a user-name".
 See also the "User database" chapter of the samba HOWTO Collection.
 
 
+
+
+How can I make samba use netbios scope ID's
+
+By default Samba uses a blank scope ID. This means 
+all your windows boxes must also have a blank scope ID. 
+If you really want to use a non-blank scope ID then you will 
+need to use the 'netbios scope' smb.conf option.
+All your PCs will need to have the same setting for 
+this to work. Scope ID's are not recommended.
+
+
 
diff --git a/docs/docbook/faq/general.sgml b/docs/docbook/faq/general.sgml
index 3f7c2074f9..54c620b382 100644
--- a/docs/docbook/faq/general.sgml
+++ b/docs/docbook/faq/general.sgml
@@ -35,7 +35,7 @@ unstable, and a series of alpha releases are distributed, for example
 doing.  The "alpha" in the filename will hopefully scare off those who
 are just looking for the latest version to install.
 
-When Andrew thinks that the alphas have stabilised to the point
+When the release manager, currently Jerry, thinks that the alphas have stabilised to the point
 where he would recommend new users install it, he renames it to the
 same version number without the alpha, for example 1.9.16.
 
@@ -128,43 +128,4 @@ Look at the samba mailing list
 
 
 
-
-Pizza supply details
-
-Those who have registered in the Samba survey as "Pizza Factory" will
-already know this, but the rest may need some help. Andrew doesn't ask
-for payment, but he does appreciate it when people give him
-pizza. This calls for a little organisation when the pizza donor is
-twenty thousand kilometres away, but it has been done.
-
-
-
-Method 1: Ring up your local branch of an international pizza chain
-and see if they honour their vouchers internationally. Pizza Hut do,
-which is how the entire Canberra Linux Users Group got to eat pizza
-one night, courtesy of someone in the US.
-
-
-
-Method 2: Ring up a local pizza shop in Canberra and quote a credit
-card number for a certain amount, and tell them that Andrew will be
-collecting it (don't forget to tell him.) One kind soul from Germany
-did this.
-
-
-
-Method 3: Purchase a pizza voucher from your local pizza shop that has
-no international affiliations and send it to Andrew. It is completely
-useless but he can hang it on the wall next to the one he already has
-from Germany :-)
-
-
-
-Method 4: Air freight him a pizza with your favourite regional
-flavours. It will probably get stuck in customs or torn apart by
-hungry sniffer dogs but it will have been a noble gesture.
-
-
-
-
 
diff --git a/docs/docbook/faq/printing.sgml b/docs/docbook/faq/printing.sgml
index 4a58c385bb..be2acbd905 100644
--- a/docs/docbook/faq/printing.sgml
+++ b/docs/docbook/faq/printing.sgml
@@ -1,4 +1,5 @@
 
+
 
 
 	RonanWaide
-- 
cgit 


From 185e897847a00f1ca4a145e7626c9df990816786 Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij 
Date: Mon, 21 Apr 2003 16:21:45 +0000
Subject: More docs are up to date now... (This used to be commit
 280ba59b8187a88f45c3b6db448e76839c3c6f1e)

---
 docs/docs-status | 30 +++++++-----------------------
 1 file changed, 7 insertions(+), 23 deletions(-)

diff --git a/docs/docs-status b/docs/docs-status
index 706f06bbe8..0f92f8af9b 100644
--- a/docs/docs-status
+++ b/docs/docs-status
@@ -5,50 +5,34 @@ Manifest
  - this should be updated
 docs/announce - out of date (announces 2.2.0)
  - this should be updated
-docs/docbook/manpages/smb.conf.5.sgml - 'restrict anonymous' isn't documented properly
- - this should be updated
 docs/docbook/projdoc/Integrating-with-Windows.sgml - Should slowly go a way. Contains a little bit information about wins, a little bit about domain membership, a little about winbind, etc
  - Has been cleaned up now - more to go.
 docs/docbook/projdoc/PAM-Authentication-And-Samba.sgml
  - this should be updated
-docs/docbook/projdoc/Printing.sgml - Cups is not documented, smbprint, printing /to/ a windows server... - Kurt Pfeifle
- - this is in hand by Kurt/jht
+docs/docbook/projdoc/Printing.sgml - Cups is not documented, smbprint, printing /to/ a windows server... - worked on by Kurt Pfeifle
 docs/docbook/projdoc/Samba-BDC-HOWTO.sgml - Needs update to 3.0
  - still being worked on
 docs/docbook/projdoc/passdb.sgml - LDAP part needs update to 3.0 ( http://www.unav.es/cti/ldap-smb/smb-ldap-3-howto.html )
  - this should be updated
-docs/docbook/projdoc/Speed.sgml - contains outdated and invalid information
- - this should be updated
-docs/docbook/projdoc/UNIX_INSTALL.sgml - Merge locking part with oplocks.sgml
- - this should be updated
-docs/docbook/projdoc/printer_driver2.sgml - Needs integration with printing.sgml, still up to date?
- - still being worked on
+docs/docbook/projdoc/printer_driver2.sgml - Needs integration with printing.sgml, still up to date? - Worked on by Kurt Pfeifle
 docs/docbook/projdoc/upgrading-to-3.0.sgml - not finished yet
  - this should be updated
-docs/textdocs/CUPS-PrintingInfo.txt - needs to be converted to sgml - Kurt Pfeifle
- - this is in hand by Kurt/jht
-docs/docbook/manpages/ntlm_auth.1.sgml - Is very basic at the moment, parameters need better descriptions - abartlet
- - this is in hand by Andrew Bartlett
- 
+docs/docbook/manpages/ntlm_auth.1.sgml - Is very basic at the moment, parameters need better descriptions - Worked on by Andrew Bartlett
 
 Stuff that needs to be documented:
 wrepld
  - I will do this - jht
 Windows NT 4.0 Style Trust Relationship
  - Done (mimir / jht) - not finished.
-Winbind in a samba controlled domain
- - I will do this - Jelmer
-One Time Migration script from a Windows NT 4.0 PDC to a Samba PDC
- - I will do this - jht
+Winbind in a samba controlled domain - Worked on by Jelmer
+One Time Migration script from a Windows NT 4.0 PDC to a Samba PDC - Worked on by jht
 ldap passwd sync
  - not yet reviewed - needs attention
 
-Can someone please take ownership of the following. Thanks - jht
-
 Not release-critical:
 docs/docbook/devdoc/* - most of these docs are outdated and need updates...
 docs/docbook/projdoc/Diagnosis.sgml - Needs extension
- - I will look at this towards the end of updating the HOWTO
+ - jht will look at this towards the end of updating the HOWTO
 docs/docbook/manpages/rpcclient.1.sgml - Some commands could be documented more extensively
 docs/history - needs updating (is current up to 1998 - merge with 10year.html ?)
 
@@ -61,9 +45,9 @@ profile acls             // protocol
 client lanman auth       // security
 client NTLMv2 auth       // security
 idmap backend            // security
-sam backend		 // security
 kernel change notify     // tuning
 lpq cache time           // tuning
 -valid			 // misc
 idmap uid		 // winbind
 idmap gid		 // winbind
+'restrict anonymous' isn't documented properly
-- 
cgit 


From cca63db35b2b20c823b57e0487c67325d29989e1 Mon Sep 17 00:00:00 2001
From: John Terpstra 
Date: Mon, 21 Apr 2003 16:25:38 +0000
Subject: Replacing file with correct version. (This used to be commit
 f0dc3e6da89728259ed5e10cb7f9193c711f65fc)

---
 docs/docbook/projdoc/NT4Migration.sgml | 103 ---------------------------------
 1 file changed, 103 deletions(-)

diff --git a/docs/docbook/projdoc/NT4Migration.sgml b/docs/docbook/projdoc/NT4Migration.sgml
index 5799841feb..84719b9a94 100644
--- a/docs/docbook/projdoc/NT4Migration.sgml
+++ b/docs/docbook/projdoc/NT4Migration.sgml
@@ -492,109 +492,6 @@ Authentication
 
 
 
-
-Migration Options
-
-
-There are 3 major Site Types:
-
-
-
-<= 50 Users
-Want simple conversion with NO pain
-50 - 250 Users
-Want new features, can manage some in-house complexity
-Large Scale Sites
-Solution / Implementation MUST scale well, complex needs
-Cross departmental decision process
-Local expertise in most areas
-Planning for Success
-Decide which approach is needed - 3 Choices
-Simple Conversion (total replacement)
-Upgraded Conversion (could be one of integration)
-Complete Redesign (completely new solution)
-Take sufficient time
-Avoid Panic
-Test ALL assumptions
-Test full roll-out program, including workstation deployment
-Simple Conversion
-Make use of minimal OS specific features
-Can use No Unix Accounts Option
-Suck all accounts from NT4 into Samba-3
-Make least number of operational changes
-Take least amount of time to migrate
-Live versus Isolated Conversion
-Integrate Samba-3 then migrate while users are active
-Change of control (ie: swap out)
-Upgraded Conversion
-Translate NT4 features to new host OS features
-Copy and improve
-Old environment to Samba-3
-Make progressive improvements
-Minimise user impact
-Macimise functionality
-Take advantage of lower maintenance opportunity
-Complete Network Redesign
-Decide
-Authentication Regime (database locate and access)
-Desktop Management Methods
-Better Control of Desktops / Users
-Identify Needs for:
-Manageability, Scalability, Security, Availability
-Samba Implementation Choices
-Authentication database back end
-Winbind (external Samba or NT4/200x server)
-Can use pam_mkhomedir.so to auto-create home dirs
-External server could use Active Directory or NT4 Domain
-Database type
-smbpasswd, tdbsam, ldapsam, MySQLsam
-With local accounts or with No Unix Accounts (NUA option)
-Samba Implementation Choice - II
-Access Control Points
-On the Share itself (Use NT4 Server Manager)
-On the file system
-Unix permissions on files and directories
-Posix ACLs enablement in file system?
-Through Samba share parameters
-Not recommended - except as only resort
-Samba Implementation Choice - III
-Policies (migrate or create new ones)
-Group Policy Editor (NT4)
-Watch out for Tattoo effect
-User and Group Profiles
-Platform specific so use platform tool to change from a Local to a Roaming profile
-Can use new profiles tool to change SIDs (NTUser.DAT)
-Logon Scripts (Know how they work)
-Samba Implementation Choices - IV
-User and Group mapping to Unix/Linux
-username map facility may be needed
-Use smbgroupedit to connect NT4 groups to Unix groups
-Use pdbedit to set/change user configuration
-NOTE:
-If migrating to LDAP back end it may be easier to dump initial LDAP database to LDIF, then edit, then reload into LDAP
-Samba Implementation Choices - V
-OS specific scripts / programs may be needed
-Add / delete Users
-Note OS limits on size of name (Linux 8 chars)
-NT4 up to 254 chars
-Add / delete machines
-Applied only to domain members (note up to 16 chars)
-Add / delete Groups
-Note OS limits on size and nature
-Linux limit is 16 char, no spaces and no upper case chars (groupadd)
-Migration Tools
-Domain Control (NT4 Style)
-Profiles, Policies, Access Controls, Security
-Migration Tools
-Samba: net, rpcclient, smbpasswd, pdbedit, smbgroupedit, profiles
-Windows: NT4 Domain User Manager, Server Manager (NEXUS)
-Authentication
-New SAM back end (smbpasswd, tdbsam, ldapsam, mysqlsam)
-With of without Unix Accounts (NUA)
-
-
-
-
 
 Managing Samba-3 Domain Control
 
-- 
cgit 


From 13c8154ccdfc36445e66472a7448bdd710a909ae Mon Sep 17 00:00:00 2001
From: Andrew Bartlett 
Date: Mon, 21 Apr 2003 17:26:37 +0000
Subject: Use the -W domain option to select the SID to show (This used to be
 commit 715bd4cf4e2d9d11db031ef3ed5e614b4c1a8a13)

---
 source3/utils/net.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/source3/utils/net.c b/source3/utils/net.c
index b404bac595..aa245a920a 100644
--- a/source3/utils/net.c
+++ b/source3/utils/net.c
@@ -425,13 +425,13 @@ static int net_getdomainsid(int argc, const char **argv)
 	sid_to_string(sid_str, &domain_sid);
 	d_printf("SID for domain %s is: %s\n", global_myname(), sid_str);
 
-	if (!secrets_fetch_domain_sid(lp_workgroup(), &domain_sid)) {
+	if (!secrets_fetch_domain_sid(opt_workgroup, &domain_sid)) {
 		d_printf("Could not fetch domain SID\n");
 		return 1;
 	}
 
 	sid_to_string(sid_str, &domain_sid);
-	d_printf("SID for domain %s is: %s\n", lp_workgroup(), sid_str);
+	d_printf("SID for domain %s is: %s\n", opt_workgroup, sid_str);
 
 	return 0;
 }
-- 
cgit 


From 3ac50a125e27911ec29f1c637417fa9ae1612a86 Mon Sep 17 00:00:00 2001
From: John Terpstra 
Date: Mon, 21 Apr 2003 20:00:38 +0000
Subject: Merged the two browsing documents into one. Added locking module to
 global.ent file. (This used to be commit
 1027525be23e7db97677e2ed3e2706d271ad0a0b)

---
 docs/docbook/global.ent                       |    7 +-
 docs/docbook/projdoc/Browsing-Quickguide.sgml |  416 --------
 docs/docbook/projdoc/Browsing.sgml            |  807 ----------------
 docs/docbook/projdoc/NetworkBrowsing.sgml     | 1288 +++++++++++++++++++++++++
 docs/docbook/projdoc/samba-doc.sgml           |    3 +-
 5 files changed, 1292 insertions(+), 1229 deletions(-)
 delete mode 100644 docs/docbook/projdoc/Browsing-Quickguide.sgml
 delete mode 100644 docs/docbook/projdoc/Browsing.sgml
 create mode 100644 docs/docbook/projdoc/NetworkBrowsing.sgml

diff --git a/docs/docbook/global.ent b/docs/docbook/global.ent
index c69b72d8a6..dcef1084d6 100644
--- a/docs/docbook/global.ent
+++ b/docs/docbook/global.ent
@@ -407,8 +407,7 @@ an Active Directory environment.
 
 
 
-
-
+
 
 
 
@@ -451,8 +450,7 @@ an Active Directory environment.
 
 
 
-
-
+
 
 
 
@@ -463,6 +461,7 @@ an Active Directory environment.
 
 
 
+
 
 
 
diff --git a/docs/docbook/projdoc/Browsing-Quickguide.sgml b/docs/docbook/projdoc/Browsing-Quickguide.sgml
deleted file mode 100644
index d8df57dcb9..0000000000
--- a/docs/docbook/projdoc/Browsing-Quickguide.sgml
+++ /dev/null
@@ -1,416 +0,0 @@
-
-
-	&author.jht;
-	July 5, 1998
-	Updated: March 15, 2003
-
-
-Quick Cross Subnet Browsing / Cross Workgroup Browsing guide
-
-
-This document should be read in conjunction with Browsing and may
-be taken as the fast track guide to implementing browsing across subnets
-and / or across workgroups (or domains). WINS is the best tool for resolution
-of NetBIOS names to IP addesses. WINS is NOT involved in browse list handling
-except by way of name to address mapping.
-
-
-
-MS Windows 2000 and later can be configured to operate with NO NetBIOS 
-over TCP/IP. Samba-3 and later also supports this mode of operation.
-
-
-
-
-Discussion
-
-
-Firstly, all MS Windows networking is based on SMB (Server Message
-Block) based messaging. SMB messaging may be implemented using NetBIOS or 
-without NetBIOS. Samba implements NetBIOS by encapsulating it over TCP/IP.
-MS Windows products can do likewise. NetBIOS based networking uses broadcast
-messaging to affect browse list management. When running NetBIOS over
-TCP/IP this uses UDP based messaging. UDP messages can be broadcast or unicast.
-
-
-
-Normally, only unicast UDP messaging can be forwarded by routers. The
-remote announce
-parameter to smb.conf helps to project browse announcements
-to remote network segments via unicast UDP. Similarly, the 
-remote browse sync parameter of smb.conf
-implements browse list collation using unicast UDP.
-
-
-
-Secondly, in those networks where Samba is the only SMB server technology
-wherever possible &nmbd; should be configured on one (1) machine as the WINS
-server. This makes it easy to manage the browsing environment. If each network
-segment is configured with it's own Samba WINS server, then the only way to
-get cross segment browsing to work is by using the 
-remote announce and the remote browse sync
-parameters to your smb.conf file.
-
-
-
-If only one WINS server is used for an entire multi-segment network then
-the use of the remote announce and the 
-remote browse sync parameters should NOT be necessary.
-
-
-
-As of Samba 3 WINS replication is being worked on. The bulk of the code has
-been committed, but it still needs maturation.
-
-
-
-Right now samba WINS does not support MS-WINS replication. This means that
-when setting up Samba as a WINS server there must only be one &nmbd; configured
-as a WINS server on the network. Some sites have used multiple Samba WINS
-servers for redundancy (one server per subnet) and then used 
-remote browse sync and remote announce
-to affect browse list collation across all
-segments. Note that this means clients will only resolve local names,
-and must be configured to use DNS to resolve names on other subnets in
-order to resolve the IP addresses of the servers they can see on other
-subnets. This setup is not recommended, but is mentioned as a practical
-consideration (ie: an 'if all else fails' scenario).
-
-
-
-Lastly, take note that browse lists are a collection of unreliable broadcast
-messages that are repeated at intervals of not more than 15 minutes. This means
-that it will take time to establish a browse list and it can take up to 45
-minutes to stabilise, particularly across network segments.
-
-
-
-
-
-How browsing functions and how to deploy stable and 
-dependable browsing using Samba
-
-
-
-As stated above, MS Windows machines register their NetBIOS names 
-(i.e.: the machine name for each service type in operation) on start 
-up. Also, as stated above, the exact method by which this name registration 
-takes place is determined by whether or not the MS Windows client/server 
-has been given a WINS server address, whether or not LMHOSTS lookup 
-is enabled, or if DNS for NetBIOS name resolution is enabled, etc.
-
-
-
-In the case where there is no WINS server all name registrations as 
-well as name lookups are done by UDP broadcast. This isolates name 
-resolution to the local subnet, unless LMHOSTS is used to list all 
-names and IP addresses. In such situations Samba provides a means by 
-which the samba server name may be forcibly injected into the browse 
-list of a remote MS Windows network (using the 
-remote announce parameter).
-
-
-
-Where a WINS server is used, the MS Windows client will use UDP 
-unicast to register with the WINS server. Such packets can be routed 
-and thus WINS allows name resolution to function across routed networks.
-
-
-
-During the startup process an election will take place to create a 
-local master browser if one does not already exist. On each NetBIOS network 
-one machine will be elected to function as the domain master browser. This 
-domain browsing has nothing to do with MS security domain control. 
-Instead, the domain master browser serves the role of contacting each local 
-master browser (found by asking WINS or from LMHOSTS) and exchanging browse 
-list contents. This way every master browser will eventually obtain a complete 
-list of all machines that are on the network. Every 11-15 minutes an election 
-is held to determine which machine will be the master browser. By the nature of 
-the election criteria used, the machine with the highest uptime, or the 
-most senior protocol version, or other criteria, will win the election 
-as domain master browser.
-
-
-
-Clients wishing to browse the network make use of this list, but also depend 
-on the availability of correct name resolution to the respective IP 
-address/addresses. 
-
-
-
-Any configuration that breaks name resolution and/or browsing intrinsics 
-will annoy users because they will have to put up with protracted 
-inability to use the network services.
-
-
-
-Samba supports a feature that allows forced synchonisation 
-of browse lists across routed networks using the remote 
-browse sync parameter in the smb.conf file. 
-This causes Samba to contact the local master browser on a remote network and 
-to request browse list synchronisation. This effectively bridges 
-two networks that are separated by routers. The two remote 
-networks may use either broadcast based name resolution or WINS 
-based name resolution, but it should be noted that the remote 
-browse sync parameter provides browse list synchronisation - and 
-that is distinct from name to address resolution, in other 
-words, for cross subnet browsing to function correctly it is 
-essential that a name to address resolution mechanism be provided. 
-This mechanism could be via DNS, /etc/hosts, 
-and so on.
-
-
-
-
-
-Use of the <command>Remote Announce</command> parameter
-
-The remote announce parameter of 
-smb.conf can be used to forcibly ensure
-that all the NetBIOS names on a network get announced to a remote network.
-The syntax of the remote announce parameter is:
-
-	remote announce = a.b.c.d [e.f.g.h] ...
-
-_or_
-
-	remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...
-
-
-where:
-
-a.b.c.d and 
-e.f.g.h
-is either the LMB (Local Master Browser) IP address
-or the broadcst address of the remote network.
-ie: the LMB is at 192.168.1.10, or the address
-could be given as 192.168.1.255 where the netmask
-is assumed to be 24 bits (255.255.255.0).
-When the remote announcement is made to the broadcast
-address of the remote network every host will receive
-our announcements. This is noisy and therefore
-undesirable but may be necessary if we do NOT know
-the IP address of the remote LMB.
-
-
-
-WORKGROUP
-is optional and can be either our own workgroup
-or that of the remote network. If you use the
-workgroup name of the remote network then our
-NetBIOS machine names will end up looking like
-they belong to that workgroup, this may cause
-name resolution problems and should be avoided.
-
-
-
-
-
-
-
-
-Use of the <command>Remote Browse Sync</command> parameter
-
-
-The remote browse sync parameter of 
-smb.conf is used to announce to
-another LMB that it must synchronise it's NetBIOS name list with our
-Samba LMB. It works ONLY if the Samba server that has this option is
-simultaneously the LMB on it's network segment.
-
-
-
-The syntax of the remote browse sync parameter is:
-
-
-remote browse sync = a.b.c.d
-
-
-where a.b.c.d is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.
-
-
-
-
-
-Use of WINS
-
-
-Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly
-recommended. Every NetBIOS machine registers it's name together with a
-name_type value for each of of several types of service it has available.
-eg: It registers it's name directly as a unique (the type 0x03) name.
-It also registers it's name if it is running the lanmanager compatible
-server service (used to make shares and printers available to other users)
-by registering the server (the type 0x20) name.
-
-
-
-All NetBIOS names are up to 15 characters in length. The name_type variable
-is added to the end of the name - thus creating a 16 character name. Any
-name that is shorter than 15 characters is padded with spaces to the 15th
-character. ie: All NetBIOS names are 16 characters long (including the
-name_type information).
-
-
-
-WINS can store these 16 character names as they get registered. A client
-that wants to log onto the network can ask the WINS server for a list
-of all names that have registered the NetLogon service name_type. This saves
-broadcast traffic and greatly expedites logon processing. Since broadcast
-name resolution can not be used across network segments this type of
-information can only be provided via WINS _or_ via statically configured
-lmhosts files that must reside on all clients in the
-absence of WINS.
-
-
-
-WINS also serves the purpose of forcing browse list synchronisation by all
-LMB's. LMB's must synchronise their browse list with the DMB (domain master
-browser) and WINS helps the LMB to identify it's DMB. By definition this
-will work only within a single workgroup. Note that the domain master browser
-has NOTHING to do with what is referred to as an MS Windows NT Domain. The
-later is a reference to a security environment while the DMB refers to the
-master controller for browse list information only.
-
-
-
-Use of WINS will work correctly only if EVERY client TCP/IP protocol stack
-has been configured to use the WINS server/s. Any client that has not been
-configured to use the WINS server will continue to use only broadcast based
-name registration so that WINS may NEVER get to know about it. In any case,
-machines that have not registered with a WINS server will fail name to address
-lookup attempts by other clients and will therefore cause workstation access
-errors.
-
-
-
-To configure Samba as a WINS server just add 
-wins support = yes to the smb.conf
-file [globals] section.
-
-
-
-To configure Samba to register with a WINS server just add
-"wins server = a.b.c.d" to your smb.conf file [globals] section.
-
-
-
-Never use both wins support = yes together
-with wins server = a.b.c.d
-particularly not using it's own IP address.
-Specifying both will cause &nmbd; to refuse to start!
-
-
-
-WINS Replication
-
-
-Samba-3 permits WINS replication through the use of the wrepld utility.
-This tool is not currently capable of being used as it is still in active development.
-As soon as this tool becomes moderately functional we will prepare man pages and enhance this
-section of the documentation to provide usage and technical details.
-
-
-
-
-Static WINS Entries
-
-
-New to Samba-3 is a tool called winsedit that may be used to add
-static WINS entries to the WINS database. This tool can be used also to modify entries
-existing in the WINS database.
-
-
-
-The development of the winsedit tool was made necessary due to the migration
-of the older style wins.dat file into a new tdb binary backend data store.
-
-
-
-
-
-
-Do NOT use more than one (1) protocol on MS Windows machines
-
-
-A very common cause of browsing problems results from installing more than
-one protocol on an MS Windows machine.
-
-
-
-Every NetBIOS machine takes part in a process of electing the LMB (and DMB)
-every 15 minutes. A set of election criteria is used to determine the order
-of precidence for winning this election process. A machine running Samba or
-Windows NT will be biased so that the most suitable machine will predictably
-win and thus retain it's role.
-
-
-
-The election process is "fought out" so to speak over every NetBIOS network
-interface. In the case of a Windows 9x machine that has both TCP/IP and IPX
-installed and has NetBIOS enabled over both protocols the election will be
-decided over both protocols. As often happens, if the Windows 9x machine is
-the only one with both protocols then the LMB may be won on the NetBIOS
-interface over the IPX protocol. Samba will then lose the LMB role as Windows
-9x will insist it knows who the LMB is. Samba will then cease to function
-as an LMB and thus browse list operation on all TCP/IP only machines will
-fail.
-
-
-
-Windows 95, 98, 98se, Me are referred to generically as Windows 9x.
-The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly
-referred to as the WinNT family, but it should be recognised that 2000 and
-XP/2003 introduce new protocol extensions that cause them to behave 
-differently from MS Windows NT4. Generally, where a server does NOT support
-the newer or extended protocol, these will fall back to the NT4 protocols.
-
-
-
-The safest rule of all to follow it this - USE ONLY ONE PROTOCOL!
-
-
-
-
-
-Name Resolution Order
-
-
-Resolution of NetBIOS names to IP addresses can take place using a number
-of methods. The only ones that can provide NetBIOS name_type information
-are:
-
-
-WINS: the best tool!
-LMHOSTS: is static and hard to maintain.
-Broadcast: uses UDP and can not resolve names across remote segments.
-
-
-
-Alternative means of name resolution includes:
-
-/etc/hosts: is static, hard to maintain, and lacks name_type info
-DNS: is a good choice but lacks essential name_type info.
-
-
-
-Many sites want to restrict DNS lookups and want to avoid broadcast name
-resolution traffic. The "name resolve order" parameter is of great help here.
-The syntax of the "name resolve order" parameter is:
-
-name resolve order = wins lmhosts bcast host
-
-_or_
-
-name resolve order = wins lmhosts  	(eliminates bcast and host)
-
-The default is:
-
-name  resolve order = host lmhost wins bcast
-.
-where "host" refers the the native methods used by the Unix system
-to implement the gethostbyname() function call. This is normally
-controlled by /etc/host.conf, /etc/nsswitch.conf and /etc/resolv.conf.
-
-
-
diff --git a/docs/docbook/projdoc/Browsing.sgml b/docs/docbook/projdoc/Browsing.sgml
deleted file mode 100644
index ca2f6dc57b..0000000000
--- a/docs/docbook/projdoc/Browsing.sgml
+++ /dev/null
@@ -1,807 +0,0 @@
-
-
-	
-		
-			Samba Team
-		
-	
-
-	 (5 July 1998) 
-
-
-Improved browsing in samba
-
-
-Overview of browsing
-
-
-SMB networking provides a mechanism by which clients can access a list
-of machines in a network, a so-called browse list.  This list
-contains machines that are ready to offer file and/or print services
-to other machines within the network. Thus it does not include
-machines which aren't currently able to do server tasks.  The browse
-list is heavily used by all SMB clients.  Configuration of SMB
-browsing has been problematic for some Samba users, hence this
-document.
-
-
-
-MS Windows 2000 and later, as with Samba 3 and later, can be
-configured to not use NetBIOS over TCP/IP. When configured this way
-it is imperative that name resolution (using DNS/LDAP/ADS) be correctly
-configured and operative. Browsing will NOT work if name resolution
-from SMB machine names to IP addresses does not function correctly.
-
-
-
-Where NetBIOS over TCP/IP is enabled use of a WINS server is highly
-recommended to aid the resolution of NetBIOS (SMB) names to IP addresses.
-WINS allows remote segment clients to obtain NetBIOS name_type information
-that can NOT be provided by any other means of name resolution.
-
-
-
-
-
-Browsing support in samba
-
-
-Samba facilitates browsing.  The browsing is supported by &nmbd;
-and is also controlled by options in the &smb.conf; file.
-Samba can act as a local browse master for a workgroup and the ability
-for samba to support domain logons and scripts is now available.
-
-
-
-Samba can also act as a domain master browser for a workgroup.  This
-means that it will collate lists from local browse masters into a
-wide area network server list.  In order for browse clients to
-resolve the names they may find in this list, it is recommended that
-both samba and your clients use a WINS server.
-
-
-
-Note that you should NOT set Samba to be the domain master for a
-workgroup that has the same name as an NT Domain: on each wide area
-network, you must only ever have one domain master browser per workgroup,
-regardless of whether it is NT, Samba or any other type of domain master
-that is providing this service.
-
-
-
-Nmbd can be configured as a WINS server, but it is not
-necessary to specifically use samba as your WINS server.  MS Windows
-NT4, Server or Advanced Server 2000 or 2003 can be configured as
-your WINS server.  In a mixed NT/2000/2003 server and samba environment on
-a Wide Area Network, it is recommended that you use the Microsoft
-WINS server capabilities.  In a samba-only environment, it is
-recommended that you use one and only one Samba server as your WINS server.
-
-
-
-To get browsing to work you need to run nmbd as usual, but will need
-to use the workgroup option in &smb.conf;
-to control what workgroup Samba becomes a part of.
-
-
-
-Samba also has a useful option for a Samba server to offer itself for
-browsing on another subnet.  It is recommended that this option is only
-used for 'unusual' purposes: announcements over the internet, for
-example.  See remote announce in the 
-&smb.conf; man page.  
-
-
-
-
-Problem resolution
-
-
-If something doesn't work then hopefully the log.nmb file will help
-you track down the problem.  Try a debug level of 2 or 3 for finding
-problems. Also note that the current browse list usually gets stored
-in text form in a file called browse.dat.
-
-
-
-Note that if it doesn't work for you, then you should still be able to
-type the server name as \\SERVER in filemanager then
-hit enter and filemanager should display the list of available shares.
-
-
-
-Some people find browsing fails because they don't have the global
-guest account set to a valid account.  Remember that the
-IPC$ connection that lists the shares is done as guest, and thus you must
-have a valid guest account.
-
-
-
-MS Windows 2000 and upwards (as with Samba) can be configured to disallow
-anonymous (ie: Guest account) access to the IPC$ share. In that case, the
-MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the
-name of the currently logged in user to query the IPC$ share. MS Windows
-9X clients are not able to do this and thus will NOT be able to browse
-server resources.
-
-
-
-The other big problem people have is that their broadcast address,
-netmask or IP address is wrong (specified with the "interfaces" option
-in &smb.conf;)
-
-
-
-
-Browsing across subnets
-
-Since the release of Samba 1.9.17(alpha1) Samba has been
-updated to enable it to support the replication of browse lists
-across subnet boundaries.  New code and options have been added to
-achieve this.  This section describes how to set this feature up
-in different settings.
-
-
-
-To see browse lists that span TCP/IP subnets (ie.  networks separated
-by routers that don't pass broadcast traffic) you must set up at least
-one WINS server.  The WINS server acts as a DNS for NetBIOS names, allowing
-NetBIOS name to IP address translation to be done by doing a direct
-query of the WINS server.  This is done via a directed UDP packet on
-port 137 to the WINS server machine.  The reason for a WINS server is
-that by default, all NetBIOS name to IP address translation is done
-by broadcasts from the querying machine.  This means that machines
-on one subnet will not be able to resolve the names of machines on
-another subnet without using a WINS server.
-
-
-
-Remember, for browsing across subnets to work correctly, all machines,
-be they Windows 95, Windows NT, or Samba servers must have the IP address
-of a WINS server given to them by a DHCP server, or by manual configuration 
-(for Win95 and WinNT, this is in the TCP/IP Properties, under Network 
-settings) for Samba this is in the &smb.conf; file.
-
-
-
-How does cross subnet browsing work ?
-
-
-Cross subnet browsing is a complicated dance, containing multiple
-moving parts.  It has taken Microsoft several years to get the code
-that achieves this correct, and Samba lags behind in some areas.
-Samba is capable of cross subnet browsing when configured correctly.
-
-
-
-Consider a network set up as follows :
-
-
-
-
-                                   (DMB)
-             N1_A      N1_B        N1_C       N1_D        N1_E
-              |          |           |          |           |
-          -------------------------------------------------------
-            |          subnet 1                       |
-          +---+                                      +---+
-          |R1 | Router 1                  Router 2   |R2 |
-          +---+                                      +---+
-            |                                          |
-            |  subnet 2              subnet 3          |
-  --------------------------       ------------------------------------
-  |     |     |      |               |        |         |           |
- N2_A  N2_B  N2_C   N2_D           N3_A     N3_B      N3_C        N3_D 
-                    (WINS)
-
-
-	
-
-Consisting of 3 subnets (1, 2, 3) connected by two routers
-(R1, R2) - these do not pass broadcasts.  Subnet 1 has 5 machines
-on it, subnet 2 has 4 machines, subnet 3 has 4 machines.  Assume
-for the moment that all these machines are configured to be in the
-same workgroup (for simplicities sake).  Machine N1_C on subnet 1
-is configured as Domain Master Browser (ie.  it will collate the
-browse lists for the workgroup).  Machine N2_D is configured as
-WINS server and all the other machines are configured to register
-their NetBIOS names with it.
-
-
-
-As all these machines are booted up, elections for master browsers
-will take place on each of the three subnets.  Assume that machine
-N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on
-subnet 3 - these machines are known as local master browsers for
-their particular subnet.  N1_C has an advantage in winning as the
-local master browser on subnet 1 as it is set up as Domain Master
-Browser.
-
-
-
-On each of the three networks, machines that are configured to 
-offer sharing services will broadcast that they are offering
-these services.  The local master browser on each subnet will
-receive these broadcasts and keep a record of the fact that
-the machine is offering a service.  This list of records is
-the basis of the browse list.  For this case, assume that
-all the machines are configured to offer services so all machines
-will be on the browse list.
-
-
-
-For each network, the local master browser on that network is
-considered 'authoritative' for all the names it receives via
-local broadcast.  This is because a machine seen by the local
-master browser via a local broadcast must be on the same 
-network as the local master browser and thus is a 'trusted'
-and 'verifiable' resource.  Machines on other networks that
-the local master browsers learn about when collating their
-browse lists have not been directly seen - these records are
-called 'non-authoritative'.
-
-
-
-At this point the browse lists look as follows (these are 
-the machines you would see in your network neighborhood if
-you looked in it on a particular network right now).
-
-
-
-
-Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
-
-
-
-
-Note that at this point all the subnets are separate, no
-machine is seen across any of the subnets.
-
-
-
-Now examine subnet 2.  As soon as N2_B has become the local
-master browser it looks for a Domain master browser to synchronize
-its browse list with.  It does this by querying the WINS server
-(N2_D) for the IP address associated with the NetBIOS name 
-WORKGROUP>1B<.  This name was registerd by the Domain master
-browser (N1_C) with the WINS server as soon as it was booted.
-
-
-
-Once N2_B knows the address of the Domain master browser it
-tells it that is the local master browser for subnet 2 by
-sending a MasterAnnouncement packet as a UDP port 138 packet.
-It then synchronizes with it by doing a NetServerEnum2 call.  This
-tells the Domain Master Browser to send it all the server
-names it knows about.  Once the domain master browser receives
-the MasterAnnouncement packet it schedules a synchronization
-request to the sender of that packet.  After both synchronizations
-are done the browse lists look like :
-
-
-
-
-Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
-
-Servers with a (*) after them are non-authoritative names.
-
-
-
-
-At this point users looking in their network neighborhood on
-subnets 1 or 2 will see all the servers on both, users on
-subnet 3 will still only see the servers on their own subnet.
-
-
-
-The same sequence of events that occured for N2_B now occurs
-for the local master browser on subnet 3 (N3_D).  When it
-synchronizes browse lists with the domain master browser (N1_A)
-it gets both the server entries on subnet 1, and those on
-subnet 2.  After N3_D has synchronized with N1_C and vica-versa
-the browse lists look like.
-
-
-
-
-Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*),
-                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-
-Servers with a (*) after them are non-authoritative names.
-
-
-
-
-At this point users looking in their network neighborhood on
-subnets 1 or 3 will see all the servers on all sunbets, users on
-subnet 2 will still only see the servers on subnets 1 and 2, but not 3.
-
-
-
-Finally, the local master browser for subnet 2 (N2_B) will sync again
-with the domain master browser (N1_C) and will recieve the missing
-server entries.  Finally - and as a steady state (if no machines
-are removed or shut off) the browse lists will look like :
-
-
-
-
-Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*),
-                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-	
-Servers with a (*) after them are non-authoritative names.
-
-
-
-
-Synchronizations between the domain master browser and local
-master browsers will continue to occur, but this should be a
-steady state situation.
-
-
-
-If either router R1 or R2 fails the following will occur:
-
-
-
-
-	
-	Names of computers on each side of the inaccessible network fragments
-	will be maintained for as long as 36 minutes, in the network neighbourhood
-	lists.
-	
-
-
-
-	
-	Attempts to connect to these inaccessible computers will fail, but the
-	names will not be removed from the network neighbourhood lists.
-	
-
-
-
-	
-	If one of the fragments is cut off from the WINS server, it will only
-	be able to access servers on its local subnet, by using subnet-isolated
-	broadcast NetBIOS name resolution.  The effects are similar to that of
-	losing access to a DNS server.
-	
-
-
-
-
-
-
-Setting up a WINS server
-
-
-Either a Samba machine or a Windows NT Server machine may be set up
-as a WINS server.  To set a Samba machine to be a WINS server you must
-add the following option to the &smb.conf; file on the selected machine :
-in the [globals] section add the line 
-
-
-
-		wins support = yes
-
-
-
-Versions of Samba prior to 1.9.17 had this parameter default to
-yes.  If you have any older versions of Samba on your network it is
-strongly suggested you upgrade to a recent version, or at the very
-least set the parameter to 'no' on all these machines.
-
-
-
-Machines with wins support = yes will keep a list of 
-all NetBIOS names registered with them, acting as a DNS for NetBIOS names.
-
-
-
-You should set up only ONE wins server.  Do NOT set the
-wins support = yes option on more than one Samba 
-server.
-
-
-
-To set up a Windows NT Server as a WINS server you need to set up
-the WINS service - see your NT documentation for details.  Note that
-Windows NT WINS Servers can replicate to each other, allowing more
-than one to be set up in a complex subnet environment.  As Microsoft
-refuse to document these replication protocols Samba cannot currently
-participate in these replications.  It is possible in the future that
-a Samba->Samba WINS replication protocol may be defined, in which
-case more than one Samba machine could be set up as a WINS server
-but currently only one Samba server should have the 
-wins support = yes parameter set.
-
-
-
-After the WINS server has been configured you must ensure that all
-machines participating on the network are configured with the address
-of this WINS server.  If your WINS server is a Samba machine, fill in
-the Samba machine IP address in the "Primary WINS Server" field of
-the "Control Panel->Network->Protocols->TCP->WINS Server" dialogs
-in Windows 95 or Windows NT.  To tell a Samba server the IP address
-of the WINS server add the following line to the [global] section of
-all &smb.conf; files :
-
-
-
-wins server = >name or IP address<
-
-
-
-where >name or IP address< is either the DNS name of the WINS server
-machine or its IP address.
-
-
-
-Note that this line MUST NOT BE SET in the &smb.conf; file of the Samba
-server acting as the WINS server itself.  If you set both the
-wins support = yes option and the 
-wins server = <name> option then
-nmbd will fail to start.
-
-
-
-There are two possible scenarios for setting up cross subnet browsing.
-The first details setting up cross subnet browsing on a network containing
-Windows 95, Samba and Windows NT machines that are not configured as
-part of a Windows NT Domain.  The second details setting up cross subnet
-browsing on networks that contain NT Domains.
-
-
-
-
-
-Setting up Browsing in a WORKGROUP
-
-
-To set up cross subnet browsing on a network containing machines
-in up to be in a WORKGROUP, not an NT Domain you need to set up one
-Samba server to be the Domain Master Browser (note that this is *NOT*
-the same as a Primary Domain Controller, although in an NT Domain the
-same machine plays both roles).  The role of a Domain master browser is
-to collate the browse lists from local master browsers on all the
-subnets that have a machine participating in the workgroup.  Without
-one machine configured as a domain master browser each subnet would
-be an isolated workgroup, unable to see any machines on any other
-subnet.  It is the presense of a domain master browser that makes
-cross subnet browsing possible for a workgroup.
-
-
-
-In an WORKGROUP environment the domain master browser must be a
-Samba server, and there must only be one domain master browser per
-workgroup name.  To set up a Samba server as a domain master browser,
-set the following option in the [global] section of the &smb.conf; file :
-
-
-
-domain master = yes
-
-
-
-The domain master browser should also preferrably be the local master
-browser for its own subnet.  In order to achieve this set the following
-options in the [global] section of the &smb.conf; file :
-
-
-
-
-domain master = yes
-local master = yes
-preferred master = yes
-os level = 65
-
-
-
-
-The domain master browser may be the same machine as the WINS
-server, if you require.
-
-
-
-Next, you should ensure that each of the subnets contains a
-machine that can act as a local master browser for the
-workgroup.  Any MS Windows NT/2K/XP/2003  machine should be
-able to do this, as will Windows 9x machines (although these
-tend to get rebooted more often, so it's not such a good idea
-to use these).  To make a Samba server a local master browser
-set the following options in the [global] section of the
-&smb.conf; file :
-
-
-
-
-domain master = no
-local master = yes
-preferred master = yes
-os level = 65
-
-
-
-
-Do not do this for more than one Samba server on each subnet,
-or they will war with each other over which is to be the local
-master browser.
-
-
-
-The local master parameter allows Samba to act as a
-local master browser.  The preferred master causes nmbd
-to force a browser election on startup and the os level
-parameter sets Samba high enough so that it should win any browser elections.
-
-
-
-If you have an NT machine on the subnet that you wish to
-be the local master browser then you can disable Samba from
-becoming a local master browser by setting the following
-options in the [global] section of the 
-&smb.conf; file :
-
-
-
-
-domain master = no
-local master = no
-preferred master = no
-os level = 0
-
-
-
-
-
-
-Setting up Browsing in a DOMAIN
-
-
-If you are adding Samba servers to a Windows NT Domain then
-you must not set up a Samba server as a domain master browser.
-By default, a Windows NT Primary Domain Controller for a Domain
-name is also the Domain master browser for that name, and many
-things will break if a Samba server registers the Domain master
-browser NetBIOS name (DOMAIN<1B>)
-with WINS instead of the PDC.
-
-
-
-For subnets other than the one containing the Windows NT PDC
-you may set up Samba servers as local master browsers as
-described.  To make a Samba server a local master browser set 
-the following options in the [global] section 
-of the &smb.conf; file :
-
-
-
-
-domain master = no
-local master = yes
-preferred master = yes
-os level = 65
-
-
-
-
-If you wish to have a Samba server fight the election with machines
-on the same subnet you may set the os level parameter
-to lower levels.  By doing this you can tune the order of machines that
-will become local master browsers if they are running.  For
-more details on this see the section 
-Forcing samba to be the master browser
-below.
-
-
-
-If you have Windows NT machines that are members of the domain
-on all subnets, and you are sure they will always be running then
-you can disable Samba from taking part in browser elections and
-ever becoming a local master browser by setting following options 
-in the [global] section of the &smb.conf;
-file :
-
-
-
-
-        domain master = no
-        local master = no
-        preferred master = no
-        os level = 0
-
-
-
-
-
-
-Forcing samba to be the master
-
-
-Who becomes the master browser is determined by an election
-process using broadcasts.  Each election packet contains a number of parameters
-which determine what precedence (bias) a host should have in the
-election.  By default Samba uses a very low precedence and thus loses
-elections to just about anyone else.
-
-
-
-If you want Samba to win elections then just set the os level global
-option in &smb.conf; to a higher number.  It defaults to 0.  Using 34
-would make it win all elections over every other system (except other
-samba systems!)
-
-
-
-A os level of 2 would make it beat WfWg and Win95, but not MS Windows
-NT/2K Server.  A MS Windows NT/2K Server domain controller uses level 32.
-
-
-The maximum os level is 255
-
-
-If you want samba to force an election on startup, then set the
-preferred master global option in &smb.conf; to "yes".  Samba will
-then have a slight advantage over other potential master browsers
-that are not preferred master browsers.  Use this parameter with
-care, as if you have two hosts (whether they are windows 95 or NT or
-samba) on the same local subnet both set with preferred master to
-"yes", then periodically and continually they will force an election
-in order to become the local master browser.
-
-
-
-If you want samba to be a domain master browser, then it is
-recommended that you also set preferred master to "yes", because
-samba will not become a domain master browser for the whole of your
-LAN or WAN if it is not also a local master browser on its own
-broadcast isolated subnet.
-
-
-
-It is possible to configure two samba servers to attempt to become
-the domain master browser for a domain.  The first server that comes
-up will be the domain master browser.  All other samba servers will
-attempt to become the domain master browser every 5 minutes.  They
-will find that another samba server is already the domain master
-browser and will fail.  This provides automatic redundancy, should
-the current domain master browser fail.
-
-
-
-
-
-Making samba the domain master
-
-
-The domain master is responsible for collating the browse lists of
-multiple subnets so that browsing can occur between subnets.  You can
-make samba act as the domain master by setting domain master = yes
-in &smb.conf;.  By default it will not be a domain master.
-
-
-
-Note that you should NOT set Samba to be the domain master for a
-workgroup that has the same name as an NT Domain.
-
-
-
-When samba is the domain master and the master browser it will listen
-for master announcements (made roughly every twelve minutes) from local
-master browsers on other subnets and then contact them to synchronise
-browse lists.
-
-
-
-If you want samba to be the domain master then I suggest you also set
-the os level high enough to make sure it wins elections, and set
-preferred master to "yes", to get samba to force an election on
-startup.
-
-
-
-Note that all your servers (including samba) and clients should be
-using a WINS server to resolve NetBIOS names.  If your clients are only
-using broadcasting to resolve NetBIOS names, then two things will occur:
-
-
-
-
-	
-	your local master browsers will be unable to find a domain master
-	browser, as it will only be looking on the local subnet.
-	
-
-
-
-	
-	if a client happens to get hold of a domain-wide browse list, and
-	a user attempts to access a host in that list, it will be unable to
-	resolve the NetBIOS name of that host.
-	
-
-
-
-
-If, however, both samba and your clients are using a WINS server, then:
-
-
-
-
-	
-	your local master browsers will contact the WINS server and, as long as
-	samba has registered that it is a domain master browser with the WINS
-	server, your local master browser will receive samba's ip address
-	as its domain master browser.
-	
-
-
-
-	
-	when a client receives a domain-wide browse list, and a user attempts
-	to access a host in that list, it will contact the WINS server to
-	resolve the NetBIOS name of that host.  as long as that host has
-	registered its NetBIOS name with the same WINS server, the user will
-	be able to see that host.  
-	
-
-
-
-
-
-
-Note about broadcast addresses
-
-
-If your network uses a "0" based broadcast address (for example if it
-ends in a 0) then you will strike problems.  Windows for Workgroups
-does not seem to support a 0's broadcast and you will probably find
-that browsing and name lookups won't work.
-
-
-
-
-Multiple interfaces
-
-
-Samba now supports machines with multiple network interfaces.  If you
-have multiple interfaces then you will need to use the interfaces
-option in &smb.conf; to configure them. 
-
-
-
diff --git a/docs/docbook/projdoc/NetworkBrowsing.sgml b/docs/docbook/projdoc/NetworkBrowsing.sgml
new file mode 100644
index 0000000000..c4b6a07777
--- /dev/null
+++ b/docs/docbook/projdoc/NetworkBrowsing.sgml
@@ -0,0 +1,1288 @@
+
+
+	&author.jht;
+	July 5, 1998
+	Updated: March 15, 2003
+
+
+Samba / MS Windows Network Browsing Guide
+
+
+This document contains detailed informataion as well as a fast track guide to
+implementing browsing across subnets and / or across workgroups (or domains).
+WINS is the best tool for resolution of NetBIOS names to IP addesses. WINS is
+NOT involved in browse list handling except by way of name to address resolution.
+
+
+
+MS Windows 2000 and later can be configured to operate with NO NetBIOS 
+over TCP/IP. Samba-3 and later also supports this mode of operation.
+When the use of NetBIOS over TCP/IP has been disabled then the primary
+means for resolution of MS Windows machine names is via DNS and Active Directory.
+The following information assumes that your site is running NetBIOS over TCP/IP.
+
+
+
+What is Browsing?
+
+
+To most people browsing means that they can see the MS Windows and Samba servers
+in the Network Neighborhood, and when the computer icon for a particular server is
+clicked, it opens up and shows the shares and printers available on the target server.
+
+
+
+What seems so simple is in fact a very complex interaction of different technologies.
+The technologies (or methods) employed in making all of this work includes:
+
+
+
+	MS Windows machines register their presence to the network
+	Machines announce themselves to other machines on the network
+	One or more machine on the network collates the local announcements
+	The client machine finds the machine that has the collated list of machines
+	The client machine is able to resolve the machine names to IP addresses
+	The client machine is able to connect to a target machine
+
+
+
+The samba application that controls/manages browse list management and name resolution is
+called nmbd. The configuration parameters involved in nmbd's operation are:
+
+
+
+	Browsing options:
+	-----------------
+		* os level
+		  lm announce
+		  lm interval
+		* preferred master
+		* local master
+		* domain master
+		  browse list
+		  enhanced browsing
+
+	Name Resolution Method:
+	-----------------------
+		* name resolve order
+
+	WINS options:
+	-------------
+		  dns proxy
+		  wins proxy
+		* wins server
+		* wins support
+		  wins hook
+
+
+
+WINS Server and WINS Support are mutually exclusive options. Those marked with an '*' are
+the only options that commonly MAY need to be modified. Even if not one of these parameters
+is set nmbd will still do it's job.
+
+
+
+
+Discussion
+
+
+Firstly, all MS Windows networking is based on SMB (Server Message
+Block) based messaging. SMB messaging may be implemented using NetBIOS or 
+without NetBIOS. Samba implements NetBIOS by encapsulating it over TCP/IP.
+MS Windows products can do likewise. NetBIOS based networking uses broadcast
+messaging to affect browse list management. When running NetBIOS over
+TCP/IP this uses UDP based messaging. UDP messages can be broadcast or unicast.
+
+
+
+Normally, only unicast UDP messaging can be forwarded by routers. The
+remote announce
+parameter to smb.conf helps to project browse announcements
+to remote network segments via unicast UDP. Similarly, the 
+remote browse sync parameter of smb.conf
+implements browse list collation using unicast UDP.
+
+
+
+Secondly, in those networks where Samba is the only SMB server technology
+wherever possible nmbd should be configured on one (1) machine as the WINS
+server. This makes it easy to manage the browsing environment. If each network
+segment is configured with it's own Samba WINS server, then the only way to
+get cross segment browsing to work is by using the 
+remote announce and the remote browse sync
+parameters to your smb.conf file.
+
+
+
+If only one WINS server is used for an entire multi-segment network then
+the use of the remote announce and the 
+remote browse sync parameters should NOT be necessary.
+
+
+
+As of Samba 3 WINS replication is being worked on. The bulk of the code has
+been committed, but it still needs maturation.
+
+
+
+Right now samba WINS does not support MS-WINS replication. This means that
+when setting up Samba as a WINS server there must only be one nmbd configured
+as a WINS server on the network. Some sites have used multiple Samba WINS
+servers for redundancy (one server per subnet) and then used 
+remote browse sync and remote announce
+to affect browse list collation across all
+segments. Note that this means clients will only resolve local names,
+and must be configured to use DNS to resolve names on other subnets in
+order to resolve the IP addresses of the servers they can see on other
+subnets. This setup is not recommended, but is mentioned as a practical
+consideration (ie: an 'if all else fails' scenario).
+
+
+
+Lastly, take note that browse lists are a collection of unreliable broadcast
+messages that are repeated at intervals of not more than 15 minutes. This means
+that it will take time to establish a browse list and it can take up to 45
+minutes to stabilise, particularly across network segments.
+
+
+
+
+
+How Browsing Functions
+
+
+As stated above, MS Windows machines register their NetBIOS names 
+(ie: the machine name for each service type in operation) on start 
+up. Also, as stated above, the exact method by which this name registration 
+takes place is determined by whether or not the MS Windows client/server 
+has been given a WINS server address, whether or not LMHOSTS lookup 
+is enabled, or if DNS for NetBIOS name resolution is enabled, etc.
+
+
+
+In the case where there is no WINS server all name registrations as 
+well as name lookups are done by UDP broadcast. This isolates name 
+resolution to the local subnet, unless LMHOSTS is used to list all 
+names and IP addresses. In such situations Samba provides a means by 
+which the samba server name may be forcibly injected into the browse 
+list of a remote MS Windows network (using the 
+remote announce parameter).
+
+
+
+Where a WINS server is used, the MS Windows client will use UDP 
+unicast to register with the WINS server. Such packets can be routed 
+and thus WINS allows name resolution to function across routed networks.
+
+
+
+During the startup process an election will take place to create a 
+local master browser if one does not already exist. On each NetBIOS network 
+one machine will be elected to function as the domain master browser. This 
+domain browsing has nothing to do with MS security domain control. 
+Instead, the domain master browser serves the role of contacting each local 
+master browser (found by asking WINS or from LMHOSTS) and exchanging browse 
+list contents. This way every master browser will eventually obtain a complete 
+list of all machines that are on the network. Every 11-15 minutes an election 
+is held to determine which machine will be the master browser. By the nature of 
+the election criteria used, the machine with the highest uptime, or the 
+most senior protocol version, or other criteria, will win the election 
+as domain master browser.
+
+
+
+Clients wishing to browse the network make use of this list, but also depend 
+on the availability of correct name resolution to the respective IP 
+address/addresses. 
+
+
+
+Any configuration that breaks name resolution and/or browsing intrinsics 
+will annoy users because they will have to put up with protracted 
+inability to use the network services.
+
+
+
+Samba supports a feature that allows forced synchonisation 
+of browse lists across routed networks using the remote 
+browse sync parameter in the smb.conf file. 
+This causes Samba to contact the local master browser on a remote network and 
+to request browse list synchronisation. This effectively bridges 
+two networks that are separated by routers. The two remote 
+networks may use either broadcast based name resolution or WINS 
+based name resolution, but it should be noted that the remote 
+browse sync parameter provides browse list synchronisation - and 
+that is distinct from name to address resolution, in other 
+words, for cross subnet browsing to function correctly it is 
+essential that a name to address resolution mechanism be provided. 
+This mechanism could be via DNS, /etc/hosts, 
+and so on.
+
+
+
+Setting up Browsing in a WORKGROUP
+
+
+To set up cross subnet browsing on a network containing machines
+in up to be in a WORKGROUP, not an NT Domain you need to set up one
+Samba server to be the Domain Master Browser (note that this is *NOT*
+the same as a Primary Domain Controller, although in an NT Domain the
+same machine plays both roles).  The role of a Domain master browser is
+to collate the browse lists from local master browsers on all the
+subnets that have a machine participating in the workgroup.  Without
+one machine configured as a domain master browser each subnet would
+be an isolated workgroup, unable to see any machines on any other
+subnet.  It is the presense of a domain master browser that makes
+cross subnet browsing possible for a workgroup.
+
+
+
+In an WORKGROUP environment the domain master browser must be a
+Samba server, and there must only be one domain master browser per
+workgroup name.  To set up a Samba server as a domain master browser,
+set the following option in the [global] section of the &smb.conf; file :
+
+
+
+
+	domain master = yes
+
+
+
+
+The domain master browser should also preferrably be the local master
+browser for its own subnet.  In order to achieve this set the following
+options in the [global] section of the &smb.conf; file :
+
+
+
+
+	domain master = yes
+	local master = yes
+	preferred master = yes
+	os level = 65
+
+
+
+
+The domain master browser may be the same machine as the WINS
+server, if you require.
+
+
+
+Next, you should ensure that each of the subnets contains a
+machine that can act as a local master browser for the
+workgroup.  Any MS Windows NT/2K/XP/2003  machine should be
+able to do this, as will Windows 9x machines (although these
+tend to get rebooted more often, so it's not such a good idea
+to use these).  To make a Samba server a local master browser
+set the following options in the [global] section of the
+&smb.conf; file :
+
+
+
+
+	domain master = no
+	local master = yes
+	preferred master = yes
+	os level = 65
+
+
+
+
+Do not do this for more than one Samba server on each subnet,
+or they will war with each other over which is to be the local
+master browser.
+
+
+
+The local master parameter allows Samba to act as a
+local master browser.  The preferred master causes nmbd
+to force a browser election on startup and the os level
+parameter sets Samba high enough so that it should win any browser elections.
+
+
+
+If you have an NT machine on the subnet that you wish to
+be the local master browser then you can disable Samba from
+becoming a local master browser by setting the following
+options in the [global] section of the 
+&smb.conf; file :
+
+
+
+
+	domain master = no
+	local master = no
+	preferred master = no
+	os level = 0
+
+
+
+
+
+
+Setting up Browsing in a DOMAIN
+
+
+If you are adding Samba servers to a Windows NT Domain then
+you must not set up a Samba server as a domain master browser.
+By default, a Windows NT Primary Domain Controller for a Domain
+name is also the Domain master browser for that name, and many
+things will break if a Samba server registers the Domain master
+browser NetBIOS name (DOMAIN<1B>)
+with WINS instead of the PDC.
+
+
+
+For subnets other than the one containing the Windows NT PDC
+you may set up Samba servers as local master browsers as
+described.  To make a Samba server a local master browser set 
+the following options in the [global] section 
+of the &smb.conf; file :
+
+
+
+
+	domain master = no
+	local master = yes
+	preferred master = yes
+	os level = 65
+
+
+
+
+If you wish to have a Samba server fight the election with machines
+on the same subnet you may set the os level parameter
+to lower levels.  By doing this you can tune the order of machines that
+will become local master browsers if they are running.  For
+more details on this see the section 
+Forcing samba to be the master browser
+below.
+
+
+
+If you have Windows NT machines that are members of the domain
+on all subnets, and you are sure they will always be running then
+you can disable Samba from taking part in browser elections and
+ever becoming a local master browser by setting following options 
+in the [global] section of the &smb.conf;
+file :
+
+
+
+
+        domain master = no
+        local master = no
+        preferred master = no
+        os level = 0
+
+
+
+
+
+
+Forcing samba to be the master
+
+
+Who becomes the master browser is determined by an election
+process using broadcasts.  Each election packet contains a number of parameters
+which determine what precedence (bias) a host should have in the
+election.  By default Samba uses a very low precedence and thus loses
+elections to just about anyone else.
+
+
+
+If you want Samba to win elections then just set the os level global
+option in &smb.conf; to a higher number.  It defaults to 0.  Using 34
+would make it win all elections over every other system (except other
+samba systems!)
+
+
+
+A os level of 2 would make it beat WfWg and Win95, but not MS Windows
+NT/2K Server.  A MS Windows NT/2K Server domain controller uses level 32.
+
+
+The maximum os level is 255
+
+
+If you want samba to force an election on startup, then set the
+preferred master global option in &smb.conf; to "yes".  Samba will
+then have a slight advantage over other potential master browsers
+that are not preferred master browsers.  Use this parameter with
+care, as if you have two hosts (whether they are windows 95 or NT or
+samba) on the same local subnet both set with preferred master to
+"yes", then periodically and continually they will force an election
+in order to become the local master browser.
+
+
+
+If you want samba to be a domain master browser, then it is
+recommended that you also set preferred master to "yes", because
+samba will not become a domain master browser for the whole of your
+LAN or WAN if it is not also a local master browser on its own
+broadcast isolated subnet.
+
+
+
+It is possible to configure two samba servers to attempt to become
+the domain master browser for a domain.  The first server that comes
+up will be the domain master browser.  All other samba servers will
+attempt to become the domain master browser every 5 minutes.  They
+will find that another samba server is already the domain master
+browser and will fail.  This provides automatic redundancy, should
+the current domain master browser fail.
+
+
+
+
+
+Making samba the domain master
+
+
+The domain master is responsible for collating the browse lists of
+multiple subnets so that browsing can occur between subnets.  You can
+make samba act as the domain master by setting domain master = yes
+in &smb.conf;.  By default it will not be a domain master.
+
+
+
+Note that you should NOT set Samba to be the domain master for a
+workgroup that has the same name as an NT Domain.
+
+
+
+When samba is the domain master and the master browser it will listen
+for master announcements (made roughly every twelve minutes) from local
+master browsers on other subnets and then contact them to synchronise
+browse lists.
+
+
+
+If you want samba to be the domain master then I suggest you also set
+the os level high enough to make sure it wins elections, and set
+preferred master to "yes", to get samba to force an election on
+startup.
+
+
+
+Note that all your servers (including samba) and clients should be
+using a WINS server to resolve NetBIOS names.  If your clients are only
+using broadcasting to resolve NetBIOS names, then two things will occur:
+
+
+
+
+	
+	your local master browsers will be unable to find a domain master
+	browser, as it will only be looking on the local subnet.
+	
+
+
+
+	
+	if a client happens to get hold of a domain-wide browse list, and
+	a user attempts to access a host in that list, it will be unable to
+	resolve the NetBIOS name of that host.
+	
+
+
+
+
+If, however, both samba and your clients are using a WINS server, then:
+
+
+
+
+	
+	your local master browsers will contact the WINS server and, as long as
+	samba has registered that it is a domain master browser with the WINS
+	server, your local master browser will receive samba's ip address
+	as its domain master browser.
+	
+
+
+
+	
+	when a client receives a domain-wide browse list, and a user attempts
+	to access a host in that list, it will contact the WINS server to
+	resolve the NetBIOS name of that host.  as long as that host has
+	registered its NetBIOS name with the same WINS server, the user will
+	be able to see that host.  
+	
+
+
+
+
+
+
+Note about broadcast addresses
+
+
+If your network uses a "0" based broadcast address (for example if it
+ends in a 0) then you will strike problems.  Windows for Workgroups
+does not seem to support a 0's broadcast and you will probably find
+that browsing and name lookups won't work.
+
+
+
+
+Multiple interfaces
+
+
+Samba now supports machines with multiple network interfaces.  If you
+have multiple interfaces then you will need to use the interfaces
+option in &smb.conf; to configure them. 
+
+
+
+Use of the <command>Remote Announce</command> parameter
+
+The remote announce parameter of 
+smb.conf can be used to forcibly ensure
+that all the NetBIOS names on a network get announced to a remote network.
+The syntax of the remote announce parameter is:
+
+	remote announce = a.b.c.d [e.f.g.h] ...
+
+_or_
+
+	remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...
+
+
+where:
+
+a.b.c.d and 
+e.f.g.h
+is either the LMB (Local Master Browser) IP address
+or the broadcst address of the remote network.
+ie: the LMB is at 192.168.1.10, or the address
+could be given as 192.168.1.255 where the netmask
+is assumed to be 24 bits (255.255.255.0).
+When the remote announcement is made to the broadcast
+address of the remote network every host will receive
+our announcements. This is noisy and therefore
+undesirable but may be necessary if we do NOT know
+the IP address of the remote LMB.
+
+
+
+WORKGROUP
+is optional and can be either our own workgroup
+or that of the remote network. If you use the
+workgroup name of the remote network then our
+NetBIOS machine names will end up looking like
+they belong to that workgroup, this may cause
+name resolution problems and should be avoided.
+
+
+
+
+
+
+
+
+Use of the <command>Remote Browse Sync</command> parameter
+
+
+The remote browse sync parameter of 
+smb.conf is used to announce to
+another LMB that it must synchronise it's NetBIOS name list with our
+Samba LMB. It works ONLY if the Samba server that has this option is
+simultaneously the LMB on it's network segment.
+
+
+
+The syntax of the remote browse sync parameter is:
+
+
+remote browse sync = a.b.c.d
+
+
+where a.b.c.d is either the IP address of the
+remote LMB or else is the network broadcast address of the remote segment.
+
+
+
+
+
+
+
+WINS - The Windows Internetworking Name Server
+
+
+Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly
+recommended. Every NetBIOS machine registers it's name together with a
+name_type value for each of of several types of service it has available.
+eg: It registers it's name directly as a unique (the type 0x03) name.
+It also registers it's name if it is running the lanmanager compatible
+server service (used to make shares and printers available to other users)
+by registering the server (the type 0x20) name.
+
+
+
+All NetBIOS names are up to 15 characters in length. The name_type variable
+is added to the end of the name - thus creating a 16 character name. Any
+name that is shorter than 15 characters is padded with spaces to the 15th
+character. ie: All NetBIOS names are 16 characters long (including the
+name_type information).
+
+
+
+WINS can store these 16 character names as they get registered. A client
+that wants to log onto the network can ask the WINS server for a list
+of all names that have registered the NetLogon service name_type. This saves
+broadcast traffic and greatly expedites logon processing. Since broadcast
+name resolution can not be used across network segments this type of
+information can only be provided via WINS _or_ via statically configured
+lmhosts files that must reside on all clients in the
+absence of WINS.
+
+
+
+WINS also serves the purpose of forcing browse list synchronisation by all
+LMB's. LMB's must synchronise their browse list with the DMB (domain master
+browser) and WINS helps the LMB to identify it's DMB. By definition this
+will work only within a single workgroup. Note that the domain master browser
+has NOTHING to do with what is referred to as an MS Windows NT Domain. The
+later is a reference to a security environment while the DMB refers to the
+master controller for browse list information only.
+
+
+
+Use of WINS will work correctly only if EVERY client TCP/IP protocol stack
+has been configured to use the WINS server/s. Any client that has not been
+configured to use the WINS server will continue to use only broadcast based
+name registration so that WINS may NEVER get to know about it. In any case,
+machines that have not registered with a WINS server will fail name to address
+lookup attempts by other clients and will therefore cause workstation access
+errors.
+
+
+
+To configure Samba as a WINS server just add 
+wins support = yes to the smb.conf
+file [globals] section.
+
+
+
+To configure Samba to register with a WINS server just add
+"wins server = a.b.c.d" to your smb.conf file [globals] section.
+
+
+
+Never use both wins support = yes together
+with wins server = a.b.c.d
+particularly not using it's own IP address.
+Specifying both will cause &nmbd; to refuse to start!
+
+
+
+Setting up a WINS server
+
+
+Either a Samba machine or a Windows NT Server machine may be set up
+as a WINS server.  To set a Samba machine to be a WINS server you must
+add the following option to the &smb.conf; file on the selected machine :
+in the [globals] section add the line 
+
+
+
+
+	wins support = yes
+
+
+
+
+Versions of Samba prior to 1.9.17 had this parameter default to
+yes.  If you have any older versions of Samba on your network it is
+strongly suggested you upgrade to a recent version, or at the very
+least set the parameter to 'no' on all these machines.
+
+
+
+Machines with wins support = yes will keep a list of 
+all NetBIOS names registered with them, acting as a DNS for NetBIOS names.
+
+
+
+You should set up only ONE wins server.  Do NOT set the
+wins support = yes option on more than one Samba 
+server.
+
+
+
+To set up a Windows NT Server as a WINS server you need to set up
+the WINS service - see your NT documentation for details.  Note that
+Windows NT WINS Servers can replicate to each other, allowing more
+than one to be set up in a complex subnet environment.  As Microsoft
+refuse to document these replication protocols Samba cannot currently
+participate in these replications.  It is possible in the future that
+a Samba->Samba WINS replication protocol may be defined, in which
+case more than one Samba machine could be set up as a WINS server
+but currently only one Samba server should have the 
+wins support = yes parameter set.
+
+
+
+After the WINS server has been configured you must ensure that all
+machines participating on the network are configured with the address
+of this WINS server.  If your WINS server is a Samba machine, fill in
+the Samba machine IP address in the "Primary WINS Server" field of
+the "Control Panel->Network->Protocols->TCP->WINS Server" dialogs
+in Windows 95 or Windows NT.  To tell a Samba server the IP address
+of the WINS server add the following line to the [global] section of
+all &smb.conf; files :
+
+
+
+
+	wins server = <name or IP address>
+
+
+
+
+where >name or IP address< is either the DNS name of the WINS server
+machine or its IP address.
+
+
+
+Note that this line MUST NOT BE SET in the &smb.conf; file of the Samba
+server acting as the WINS server itself.  If you set both the
+wins support = yes option and the 
+wins server = <name> option then
+nmbd will fail to start.
+
+
+
+There are two possible scenarios for setting up cross subnet browsing.
+The first details setting up cross subnet browsing on a network containing
+Windows 95, Samba and Windows NT machines that are not configured as
+part of a Windows NT Domain.  The second details setting up cross subnet
+browsing on networks that contain NT Domains.
+
+
+
+
+
+WINS Replication
+
+
+Samba-3 permits WINS replication through the use of the wrepld utility.
+This tool is not currently capable of being used as it is still in active development.
+As soon as this tool becomes moderately functional we will prepare man pages and enhance this
+section of the documentation to provide usage and technical details.
+
+
+
+
+Static WINS Entries
+
+
+New to Samba-3 is a tool called winsedit that may be used to add
+static WINS entries to the WINS database. This tool can be used also to modify entries
+existing in the WINS database.
+
+
+
+The development of the winsedit tool was made necessary due to the migration
+of the older style wins.dat file into a new tdb binary backend data store.
+
+
+
+
+
+
+Helpful Hints
+
+
+The following hints should be carefully considered as they are stumbling points
+for many new network administrators.
+
+
+
+Windows Networking Protocols
+
+
+Do NOT use more than one (1) protocol on MS Windows machines
+
+
+
+A very common cause of browsing problems results from installing more than
+one protocol on an MS Windows machine.
+
+
+
+Every NetBIOS machine takes part in a process of electing the LMB (and DMB)
+every 15 minutes. A set of election criteria is used to determine the order
+of precidence for winning this election process. A machine running Samba or
+Windows NT will be biased so that the most suitable machine will predictably
+win and thus retain it's role.
+
+
+
+The election process is "fought out" so to speak over every NetBIOS network
+interface. In the case of a Windows 9x machine that has both TCP/IP and IPX
+installed and has NetBIOS enabled over both protocols the election will be
+decided over both protocols. As often happens, if the Windows 9x machine is
+the only one with both protocols then the LMB may be won on the NetBIOS
+interface over the IPX protocol. Samba will then lose the LMB role as Windows
+9x will insist it knows who the LMB is. Samba will then cease to function
+as an LMB and thus browse list operation on all TCP/IP only machines will
+fail.
+
+
+
+Windows 95, 98, 98se, Me are referred to generically as Windows 9x.
+The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly
+referred to as the WinNT family, but it should be recognised that 2000 and
+XP/2003 introduce new protocol extensions that cause them to behave 
+differently from MS Windows NT4. Generally, where a server does NOT support
+the newer or extended protocol, these will fall back to the NT4 protocols.
+
+
+
+The safest rule of all to follow it this - USE ONLY ONE PROTOCOL!
+
+
+
+
+
+Name Resolution Order
+
+
+Resolution of NetBIOS names to IP addresses can take place using a number
+of methods. The only ones that can provide NetBIOS name_type information
+are:
+
+
+	WINS: the best tool!
+	LMHOSTS: is static and hard to maintain.
+	Broadcast: uses UDP and can not resolve names across remote segments.
+
+
+
+Alternative means of name resolution includes:
+
+/etc/hosts: is static, hard to maintain, and lacks name_type info
+DNS: is a good choice but lacks essential name_type info.
+
+
+
+Many sites want to restrict DNS lookups and want to avoid broadcast name
+resolution traffic. The "name resolve order" parameter is of great help here.
+The syntax of the "name resolve order" parameter is:
+
+name resolve order = wins lmhosts bcast host
+
+_or_
+
+name resolve order = wins lmhosts  	(eliminates bcast and host)
+
+The default is:
+
+name  resolve order = host lmhost wins bcast
+.
+where "host" refers the the native methods used by the Unix system
+to implement the gethostbyname() function call. This is normally
+controlled by /etc/host.conf, /etc/nsswitch.conf and /etc/resolv.conf.
+
+
+
+
+
+Technical Overview of browsing
+
+
+SMB networking provides a mechanism by which clients can access a list
+of machines in a network, a so-called browse list.  This list
+contains machines that are ready to offer file and/or print services
+to other machines within the network. Thus it does not include
+machines which aren't currently able to do server tasks.  The browse
+list is heavily used by all SMB clients.  Configuration of SMB
+browsing has been problematic for some Samba users, hence this
+document.
+
+
+
+MS Windows 2000 and later, as with Samba 3 and later, can be
+configured to not use NetBIOS over TCP/IP. When configured this way
+it is imperative that name resolution (using DNS/LDAP/ADS) be correctly
+configured and operative. Browsing will NOT work if name resolution
+from SMB machine names to IP addresses does not function correctly.
+
+
+
+Where NetBIOS over TCP/IP is enabled use of a WINS server is highly
+recommended to aid the resolution of NetBIOS (SMB) names to IP addresses.
+WINS allows remote segment clients to obtain NetBIOS name_type information
+that can NOT be provided by any other means of name resolution.
+
+
+
+Browsing support in samba
+
+
+Samba facilitates browsing.  The browsing is supported by &nmbd;
+and is also controlled by options in the &smb.conf; file.
+Samba can act as a local browse master for a workgroup and the ability
+for samba to support domain logons and scripts is now available.
+
+
+
+Samba can also act as a domain master browser for a workgroup.  This
+means that it will collate lists from local browse masters into a
+wide area network server list.  In order for browse clients to
+resolve the names they may find in this list, it is recommended that
+both samba and your clients use a WINS server.
+
+
+
+Note that you should NOT set Samba to be the domain master for a
+workgroup that has the same name as an NT Domain: on each wide area
+network, you must only ever have one domain master browser per workgroup,
+regardless of whether it is NT, Samba or any other type of domain master
+that is providing this service.
+
+
+
+Nmbd can be configured as a WINS server, but it is not
+necessary to specifically use samba as your WINS server.  MS Windows
+NT4, Server or Advanced Server 2000 or 2003 can be configured as
+your WINS server.  In a mixed NT/2000/2003 server and samba environment on
+a Wide Area Network, it is recommended that you use the Microsoft
+WINS server capabilities.  In a samba-only environment, it is
+recommended that you use one and only one Samba server as your WINS server.
+
+
+
+To get browsing to work you need to run nmbd as usual, but will need
+to use the workgroup option in &smb.conf;
+to control what workgroup Samba becomes a part of.
+
+
+
+Samba also has a useful option for a Samba server to offer itself for
+browsing on another subnet.  It is recommended that this option is only
+used for 'unusual' purposes: announcements over the internet, for
+example.  See remote announce in the 
+&smb.conf; man page.  
+
+
+
+
+Problem resolution
+
+
+If something doesn't work then hopefully the log.nmb file will help
+you track down the problem.  Try a debug level of 2 or 3 for finding
+problems. Also note that the current browse list usually gets stored
+in text form in a file called browse.dat.
+
+
+
+Note that if it doesn't work for you, then you should still be able to
+type the server name as \\SERVER in filemanager then
+hit enter and filemanager should display the list of available shares.
+
+
+
+Some people find browsing fails because they don't have the global
+guest account set to a valid account.  Remember that the
+IPC$ connection that lists the shares is done as guest, and thus you must
+have a valid guest account.
+
+
+
+MS Windows 2000 and upwards (as with Samba) can be configured to disallow
+anonymous (ie: Guest account) access to the IPC$ share. In that case, the
+MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the
+name of the currently logged in user to query the IPC$ share. MS Windows
+9X clients are not able to do this and thus will NOT be able to browse
+server resources.
+
+
+
+The other big problem people have is that their broadcast address,
+netmask or IP address is wrong (specified with the "interfaces" option
+in &smb.conf;)
+
+
+
+
+Browsing across subnets
+
+Since the release of Samba 1.9.17(alpha1) Samba has been
+updated to enable it to support the replication of browse lists
+across subnet boundaries.  New code and options have been added to
+achieve this.  This section describes how to set this feature up
+in different settings.
+
+
+
+To see browse lists that span TCP/IP subnets (ie.  networks separated
+by routers that don't pass broadcast traffic) you must set up at least
+one WINS server.  The WINS server acts as a DNS for NetBIOS names, allowing
+NetBIOS name to IP address translation to be done by doing a direct
+query of the WINS server.  This is done via a directed UDP packet on
+port 137 to the WINS server machine.  The reason for a WINS server is
+that by default, all NetBIOS name to IP address translation is done
+by broadcasts from the querying machine.  This means that machines
+on one subnet will not be able to resolve the names of machines on
+another subnet without using a WINS server.
+
+
+
+Remember, for browsing across subnets to work correctly, all machines,
+be they Windows 95, Windows NT, or Samba servers must have the IP address
+of a WINS server given to them by a DHCP server, or by manual configuration 
+(for Win95 and WinNT, this is in the TCP/IP Properties, under Network 
+settings) for Samba this is in the &smb.conf; file.
+
+
+
+How does cross subnet browsing work ?
+
+
+Cross subnet browsing is a complicated dance, containing multiple
+moving parts.  It has taken Microsoft several years to get the code
+that achieves this correct, and Samba lags behind in some areas.
+Samba is capable of cross subnet browsing when configured correctly.
+
+
+
+Consider a network set up as follows :
+
+
+
+
+                                   (DMB)
+             N1_A      N1_B        N1_C       N1_D        N1_E
+              |          |           |          |           |
+          -------------------------------------------------------
+            |          subnet 1                       |
+          +---+                                      +---+
+          |R1 | Router 1                  Router 2   |R2 |
+          +---+                                      +---+
+            |                                          |
+            |  subnet 2              subnet 3          |
+  --------------------------       ------------------------------------
+  |     |     |      |               |        |         |           |
+ N2_A  N2_B  N2_C   N2_D           N3_A     N3_B      N3_C        N3_D 
+                    (WINS)
+
+
+	
+
+Consisting of 3 subnets (1, 2, 3) connected by two routers
+(R1, R2) - these do not pass broadcasts.  Subnet 1 has 5 machines
+on it, subnet 2 has 4 machines, subnet 3 has 4 machines.  Assume
+for the moment that all these machines are configured to be in the
+same workgroup (for simplicities sake).  Machine N1_C on subnet 1
+is configured as Domain Master Browser (ie.  it will collate the
+browse lists for the workgroup).  Machine N2_D is configured as
+WINS server and all the other machines are configured to register
+their NetBIOS names with it.
+
+
+
+As all these machines are booted up, elections for master browsers
+will take place on each of the three subnets.  Assume that machine
+N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on
+subnet 3 - these machines are known as local master browsers for
+their particular subnet.  N1_C has an advantage in winning as the
+local master browser on subnet 1 as it is set up as Domain Master
+Browser.
+
+
+
+On each of the three networks, machines that are configured to 
+offer sharing services will broadcast that they are offering
+these services.  The local master browser on each subnet will
+receive these broadcasts and keep a record of the fact that
+the machine is offering a service.  This list of records is
+the basis of the browse list.  For this case, assume that
+all the machines are configured to offer services so all machines
+will be on the browse list.
+
+
+
+For each network, the local master browser on that network is
+considered 'authoritative' for all the names it receives via
+local broadcast.  This is because a machine seen by the local
+master browser via a local broadcast must be on the same 
+network as the local master browser and thus is a 'trusted'
+and 'verifiable' resource.  Machines on other networks that
+the local master browsers learn about when collating their
+browse lists have not been directly seen - these records are
+called 'non-authoritative'.
+
+
+
+At this point the browse lists look as follows (these are 
+the machines you would see in your network neighborhood if
+you looked in it on a particular network right now).
+
+
+
+
+Subnet           Browse Master   List
+------           -------------   ----
+Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E
+
+Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
+
+Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
+
+
+
+
+Note that at this point all the subnets are separate, no
+machine is seen across any of the subnets.
+
+
+
+Now examine subnet 2.  As soon as N2_B has become the local
+master browser it looks for a Domain master browser to synchronize
+its browse list with.  It does this by querying the WINS server
+(N2_D) for the IP address associated with the NetBIOS name 
+WORKGROUP>1B<.  This name was registerd by the Domain master
+browser (N1_C) with the WINS server as soon as it was booted.
+
+
+
+Once N2_B knows the address of the Domain master browser it
+tells it that is the local master browser for subnet 2 by
+sending a MasterAnnouncement packet as a UDP port 138 packet.
+It then synchronizes with it by doing a NetServerEnum2 call.  This
+tells the Domain Master Browser to send it all the server
+names it knows about.  Once the domain master browser receives
+the MasterAnnouncement packet it schedules a synchronization
+request to the sender of that packet.  After both synchronizations
+are done the browse lists look like :
+
+
+
+
+Subnet           Browse Master   List
+------           -------------   ----
+Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
+
+Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
+
+Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
+
+Servers with a (*) after them are non-authoritative names.
+
+
+
+
+At this point users looking in their network neighborhood on
+subnets 1 or 2 will see all the servers on both, users on
+subnet 3 will still only see the servers on their own subnet.
+
+
+
+The same sequence of events that occured for N2_B now occurs
+for the local master browser on subnet 3 (N3_D).  When it
+synchronizes browse lists with the domain master browser (N1_A)
+it gets both the server entries on subnet 1, and those on
+subnet 2.  After N3_D has synchronized with N1_C and vica-versa
+the browse lists look like.
+
+
+
+
+Subnet           Browse Master   List
+------           -------------   ----
+Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*),
+                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
+
+Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
+
+Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
+
+Servers with a (*) after them are non-authoritative names.
+
+
+
+
+At this point users looking in their network neighborhood on
+subnets 1 or 3 will see all the servers on all sunbets, users on
+subnet 2 will still only see the servers on subnets 1 and 2, but not 3.
+
+
+
+Finally, the local master browser for subnet 2 (N2_B) will sync again
+with the domain master browser (N1_C) and will recieve the missing
+server entries.  Finally - and as a steady state (if no machines
+are removed or shut off) the browse lists will look like :
+
+
+
+
+Subnet           Browse Master   List
+------           -------------   ----
+Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*),
+                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
+
+Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
+                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
+
+Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
+	
+Servers with a (*) after them are non-authoritative names.
+
+
+
+
+Synchronizations between the domain master browser and local
+master browsers will continue to occur, but this should be a
+steady state situation.
+
+
+
+If either router R1 or R2 fails the following will occur:
+
+
+
+
+	
+	Names of computers on each side of the inaccessible network fragments
+	will be maintained for as long as 36 minutes, in the network neighbourhood
+	lists.
+	
+
+
+
+	
+	Attempts to connect to these inaccessible computers will fail, but the
+	names will not be removed from the network neighbourhood lists.
+	
+
+
+
+	
+	If one of the fragments is cut off from the WINS server, it will only
+	be able to access servers on its local subnet, by using subnet-isolated
+	broadcast NetBIOS name resolution.  The effects are similar to that of
+	losing access to a DNS server.
+	
+
+
+
+
+
+
+
diff --git a/docs/docbook/projdoc/samba-doc.sgml b/docs/docbook/projdoc/samba-doc.sgml
index a0fc27fcb0..5c3793a1ba 100644
--- a/docs/docbook/projdoc/samba-doc.sgml
+++ b/docs/docbook/projdoc/samba-doc.sgml
@@ -50,7 +50,7 @@ PLEASE read this.
 
 &IntroSMB;
 &UNIX-INSTALL;
-&BROWSING-Quick;
+&NetworkBrowsing;
 &Passdb;
 
 
@@ -90,7 +90,6 @@ for various environments.
 &VFS;
 &MS-Dfs-Setup;
 &IntegratingWithWindows;
-&BROWSING;
 &SecuringSamba;
 &unicode;
 &locking;
-- 
cgit 


From 2dfd0555143fc21a3cb877d4a62acc787c817f59 Mon Sep 17 00:00:00 2001
From: John Terpstra 
Date: Mon, 21 Apr 2003 22:21:37 +0000
Subject: Updates. (This used to be commit
 27eafbec10ae82eb686a7326f23e2ad9de2369dd)

---
 docs/docbook/projdoc/NT4Migration.sgml    | 19 ++++++------
 docs/docbook/projdoc/NetworkBrowsing.sgml | 10 +++---
 docs/docbook/projdoc/SWAT.sgml            | 36 ++++++++++++++++++++--
 docs/docbook/projdoc/samba-doc.sgml       | 51 ++++++++++++++++++++-----------
 4 files changed, 80 insertions(+), 36 deletions(-)

diff --git a/docs/docbook/projdoc/NT4Migration.sgml b/docs/docbook/projdoc/NT4Migration.sgml
index 84719b9a94..60d9f121f4 100644
--- a/docs/docbook/projdoc/NT4Migration.sgml
+++ b/docs/docbook/projdoc/NT4Migration.sgml
@@ -445,9 +445,10 @@ Authentication database back end
 	Winbind (external Samba or NT4/200x server)
 	Can use pam_mkhomedir.so to auto-create home dirs
 	External server could use Active Directory or NT4 Domain
+
 Database type
 	smbpasswd, tdbsam, ldapsam, MySQLsam
-		With local accounts or with No Unix Accounts (NUA option)
+
 Access Control Points
 	On the Share itself (Use NT4 Server Manager)
 	On the file system
@@ -455,19 +456,24 @@ Access Control Points
 	Posix ACLs enablement in file system?
 	Through Samba share parameters
 		Not recommended - except as only resort
+
 Policies (migrate or create new ones)
 	Group Policy Editor (NT4)
 	Watch out for Tattoo effect
+
 User and Group Profiles
 	Platform specific so use platform tool to change from a Local to a Roaming profile
 	Can use new profiles tool to change SIDs (NTUser.DAT)
+
 Logon Scripts (Know how they work)
+
 User and Group mapping to Unix/Linux
 	username map facility may be needed
 	Use smbgroupedit to connect NT4 groups to Unix groups
 	Use pdbedit to set/change user configuration
 NOTE:
 If migrating to LDAP back end it may be easier to dump initial LDAP database to LDIF, then edit, then reload into LDAP
+
 	OS specific scripts / programs may be needed
 		Add / delete Users
 			Note OS limits on size of name (Linux 8 chars)
@@ -481,23 +487,16 @@ If migrating to LDAP back end it may be easier to dump initial LDAP database to
 Migration Tools
 	Domain Control (NT4 Style)
 	Profiles, Policies, Access Controls, Security
+
 Migration Tools
 	Samba: net, rpcclient, smbpasswd, pdbedit, smbgroupedit, profiles
 	Windows: NT4 Domain User Manager, Server Manager (NEXUS)
+
 Authentication
 	New SAM back end (smbpasswd, tdbsam, ldapsam, mysqlsam)
-		With of without Unix Accounts (NUA)
 
 
 
 
 
-
-Managing Samba-3 Domain Control
-
-
-Lots of blah blah here.
-
-
-
 
diff --git a/docs/docbook/projdoc/NetworkBrowsing.sgml b/docs/docbook/projdoc/NetworkBrowsing.sgml
index c4b6a07777..7743cb9c75 100644
--- a/docs/docbook/projdoc/NetworkBrowsing.sgml
+++ b/docs/docbook/projdoc/NetworkBrowsing.sgml
@@ -2,7 +2,7 @@
 
 	&author.jht;
 	July 5, 1998
-	Updated: March 15, 2003
+	Updated: April 21, 2003
 
 
 Samba / MS Windows Network Browsing Guide
@@ -220,7 +220,7 @@ and so on.
 
 
 
-Setting up Browsing in a WORKGROUP
+Setting up WORKGROUP Browsing
 
 
 To set up cross subnet browsing on a network containing machines
@@ -322,7 +322,7 @@ options in the [global] section of the
 
 
 
-Setting up Browsing in a DOMAIN
+Setting up DOMAIN Browsing
 
 
 If you are adding Samba servers to a Windows NT Domain then
@@ -743,7 +743,7 @@ all &smb.conf; files :
 
 
 
-where >name or IP address< is either the DNS name of the WINS server
+where <name or IP address> is either the DNS name of the WINS server
 machine or its IP address.
 
 
@@ -1147,7 +1147,7 @@ Now examine subnet 2.  As soon as N2_B has become the local
 master browser it looks for a Domain master browser to synchronize
 its browse list with.  It does this by querying the WINS server
 (N2_D) for the IP address associated with the NetBIOS name 
-WORKGROUP>1B<.  This name was registerd by the Domain master
+WORKGROUP<1B>.  This name was registerd by the Domain master
 browser (N1_C) with the WINS server as soon as it was booted.
 
 
diff --git a/docs/docbook/projdoc/SWAT.sgml b/docs/docbook/projdoc/SWAT.sgml
index 7326a49874..ad43fd7b8a 100644
--- a/docs/docbook/projdoc/SWAT.sgml
+++ b/docs/docbook/projdoc/SWAT.sgml
@@ -1,19 +1,49 @@
 
 
 	&author.jht;
-	April 3, 2003
+	April 21, 2003
 
 
 SWAT - The Samba Web Admininistration Tool
 
 
-This is a rough guide to SWAT.
+There are many and varied opinions regarding the usefulness or otherwise of SWAT.
+No matter how hard one tries to produce the perfect configuration tool it remains
+an object of personal taste. SWAT is a tool that will allow web based configuration
+of samba. It has a wizard that may help to get samba configured quickly, it has context
+sensitive help on each smb.conf parameter, it provides for monitoring of current state
+of connection information, and it allows network wide MS Windows network password
+management.
 
 
 
 SWAT Features and Benefits
 
-You must use at least the following ...
+
+There are network administrators who believe that it is a good idea to write systems
+documentation inside configuration files, for them SWAT will aways be a nasty tool. SWAT
+does not store the configuration file in any intermediate form, rather, it stores only the
+parameter settings, so when SWAT writes the smb.conf file to disk it will write only
+those parameters that are at other than the default settings. The result is that all comments
+will be lost from the smb.conf file. Additionally, the parameters will be written back in
+internal ordering.
+
+
+
+So before using SWAT please be warned - SWAT will completely replace your smb.conf with
+a fully optimised file that has been stripped of all comments you might have placed there
+and only non-default settings will be written to the file.
+
+
+
+SWAT should be installed to run via the network super daemon. Depending on which system
+your Unix/Linux system has you will have either an inetd or
+xinetd based system.
+
+
+
+The nature and location of the network super
+
 
 
 The SWAT Home Page
diff --git a/docs/docbook/projdoc/samba-doc.sgml b/docs/docbook/projdoc/samba-doc.sgml
index 5c3793a1ba..6048d60e5f 100644
--- a/docs/docbook/projdoc/samba-doc.sgml
+++ b/docs/docbook/projdoc/samba-doc.sgml
@@ -14,17 +14,29 @@
 	&person.jht;
 	&person.jerry;
 
-	Sunday 6 April
+	Monday April 21, 2003
 
 
 
 This book is a collection of HOWTOs added to Samba documentation over the years.
-Samba is always under development, and so is it's documentation.
-The most recent version of this document
-can be found at http://www.samba.org/
-on the "Documentation" page.  Please send updates to jerry@samba.org or 
-jelmer@samba.org.
+Samba is always under development, and so is it's documentation. This release of the
+documentation represents a major revision or layout as well as contents.
+The most recent version of this document can be found at
+http://www.samba.org/
+on the "Documentation" page.  Please send updates to
+jelmer@samba.org,
+jht@samba.org or
+jerry@samba.org.
+
+
+
+The Samba-Team would like to express sincere thanks to the many people who have with
+or without their knwoledge contributed to this update. The size and scope of this
+project would not have been possible without significant community contribution. A not
+insignificant number of ideas for inclusion (if not content itself) has been obtained
+from a number of Unofficial HOWTOs - to each such author a big "Thank-you" is also offered.
+Please keep publishing you Unofficial HOWTO's - they are a source of inspiration and
+application knowledge that is most to be desired by may Samba users and administrators.
 
 
 
@@ -41,26 +53,25 @@ url="http://www.fsf.org/licenses/gpl.txt">http://www.fsf.org/licenses/gpl.txt
 
-General installation
+General Installation
 
-Introduction
-This part contains general info on how to install samba 
+Preparing Samba for Configuration
+This section of the Samba-HOWTO-Collection contains general info on how to install samba 
 and how to configure the parts of samba you will most likely need.
 PLEASE read this.
 
 &IntroSMB;
 &UNIX-INSTALL;
-&NetworkBrowsing;
-&Passdb;
 
 
 
-Type of installation
+Server Configuration Basics
 
-Introduction
+First Steps in Server Configuration
 
-Samba can operate in various SMB networks. This part contains information on configuring samba 
-for various environments.
+Samba can operate in various modes within SMB networks. This HOWTO section contains information on
+configuring samba to function as the type of server your network requires. Please read this
+section carefully.
 
 
 &ServerType;
@@ -74,9 +85,13 @@ for various environments.
 
 Advanced Configuration
 
-Introduction
-Samba has several features that you might want or might not want to use. The chapters in this part each cover one specific feature.
+Valuable Nuts and Bolts Information
+
+Samba has several features that you might want or might not want to use. The chapters in this part each cover specific Samba features.
+
 
+&NetworkBrowsing;
+&Passdb;
 &NT-Security;
 &GROUP-MAPPING-HOWTO;
 &PRINTER-DRIVER2;
-- 
cgit