10. Samba Team Notes: 2This package is targeted at the woody release of debian distribution 3running on a 2.4.x kernel. 4This package has been made by Simo Sorce on behalf of the Samba Team. 5Do not use Debian BTS to report bugs, it's not a debian project package. 6Thanks to Eloy Paris and Steve "Vorlon" Langasek for the work they've done 7and continue to do on debian unstable packages. That made me possible to 8build up debian packages for the Team. 9 10 11ATTENTION: This package works correctly only with recent 2.4.x kernels due to 12deep optimizations that samba uses when compiled on such kernels. 13 14 15Original README.Debian foolows. 16----------------------------------------------------------------------------- 17 18Samba for Debian 19---------------- 20 21This package was built by Eloy Paris <peloy@debian.org> and Steve Langasek 22<vorlon@debian.org>, current maintainers of the Samba packages for Debian, 23based on previous work from Bruce Perens <Bruce@Pixar.com>, Andrew 24Howell <andrew@it.com.au>, Klee Dienes <klee@debian.org> and Michael 25Meskes <meskes@topsystem.de>, all previous maintainers of the packages 26samba and sambades (merged together for longer than we can remember.) 27 28Contents of this README file: 29 301. Notes 312. Upgrading from Samba 2.2 323. Packages Generated from the Samba Sources 334. Support for NT Domains 345. Reporting bugs 35 36 371. Notes 38-------- 39 40- As of Samba 2.0.6-1, the Debian version of Samba is compiled with 41 Pluggable Authentication Modules (PAM) support. PAM support was 42 discontinued during the libc5 -> libc6 migration process and I never 43 brought it back until 2.0.6-1. 44 45- The smbfs package does not support the 2.0.x Linux kernels anymore. 46 This has been the case since the very first packages of the CVS sources 47 that eventually became Samba 2.2. To use the smbfs package you need to 48 run a 2.2.x kernel or later. 49 50- Starting with the Debian packages for Samba 2.2, the Samba log files (for 51 nmbd and smbd) have been moved to a new location: /var/log/samba/. The 52 files also have new names: log.nmbd and log.smbd. The old files 53 (/var/log/{nmb,smb} were moved to the new location. 54 55 562. Upgrading from Samba 2.2 57--------------------------- 58 59Samba 3.0 provides greatly improved support for modern Windows systems, 60including support for Unicode and LDAP. In the process, Samba 3.0 61necessarily also breaks backward compatiblity with past releases. These 62issues are documented herein; if you are aware of other problems related 63to upgrading from Samba 2.2, please let us know at 64<samba@packages.debian.org>. 65 66Samba and LDAP 67-------------- 68Starting with Samba 2.999+3.0cvs20020723-1 we are building Samba with 69LDAP support. However, the LDAP schema for Samba 3.0 differs 70substantially from the schema used by many sites with Samba 2.2 (not 71enabled in the Debian packages). If upgrading from an LDAP-enabled 2.2, 72you will need to run the convertSambaAccount script found in 73/usr/share/doc/samba-doc/examples/LDAP. A copy of the schema itself can 74also be found at /usr/share/doc/samba-doc/examples/LDAP/samba.schema. 75 76Character Sets 77-------------- 78Samba 3.0 introduces support for negotiating Unicode (UCS-2LE) with 79Windows clients. Owing to the close similarity between Windows and Unix 80NLS charsets, in the past, many users were able to pass filenames 81containing non-ASCII characters between clients and servers without 82configuring Samba to know what character set was in use. Now, Samba 83must be able to convert Unix filenames to Unicode before sending to the 84client, so Samba must know what character set the filenames are being 85converted from. If you will be sharing files with non-ASCII names, and 86the filenames are not encoded with UTF-8, you will need to tell Samba 87which character set to use with the 'unix charset' option. 88 89If you had previously specified 'character set' and 'client code page' 90options under 2.2, these settings should be automatically converted for 91you. 92 93 943. Packages Generated from the Samba Sources 95-------------------------------------------- 96 97Currently, the Samba sources produce the following binary packages: 98 99samba: A LanManager like file and printer server for Unix. 100samba-common: Samba common files used by both the server and the client. 101smbclient: A LanManager like simple client for Unix. 102swat: Samba Web Administration Tool 103samba-doc: Samba documentation. 104smbfs: Mount and umount commands for the smbfs (works with 2.2.x and 105 above kernels, not with 2.0.x kernels.) 106libpam-smbpass: pluggable authentication module for SMB password 107 database. 108libsmbclient: Shared library that allows applications to talk to SMB servers. 109libsmbclient-dev: libsmbclient shared libraries. 110winbind: Service to resolve user and group information from a Windows NT 111 server. 112python2.2-samba: Python bindings that allow access to various aspects of 113 Samba. 114 115Please note that the package smbwrapper (a shared library that provides 116SMB client services that existed between Samba 2.0.0-1 and Samba-2.0.5a-4 117does not exist any more. The reason is that starting with Samba 2.0.6-1, that 118code does not even compile, and the upstream author (Andrew Tridgell) 119recommended to disable the compilation of smbwrapper until some issues 120with glibc2.1 get cleared out (the problem is with glibc, not with Samba 121itself). 122 123 1244. Support for NT Domains 125------------------------- 126 127Samba 2.2 includes preliminary support for NT domains. A Samba server 128can now be part of a Windows NT domain whose Primary Domain Controller 129is a Windows NT server. This feature is supposed to be stable although I 130haven't tried it myself. Read the documentation in the samba-doc package 131for help on how to do this (hint: "security = domain" in the smb.conf 132file). 133 134Samba 2.2 has also experimental support for Primary Domain 135Controller. This means that a Samba server can act now as a PDC. There 136are no special flags needed to compile Samba with NT domain PDC 137support. Please read the NTDOM PDC FAQ at www.samba.org (Documentation 138section). 139 140Please note that NT domain PDC support is far from complete and is still 141experimental. 142 143 1445. Reporting Bugs 145----------------- 146 147**** NOTE: This package is distributed by the Samba Team based on Debian 148 packages, please submit bus to https://bugzilla.samba.org instead **** 149 150If you believe you have found a bug please make sure the possible bug 151also exists in the latest version of Samba that is available for the 152unstable Debian distribution. If you are running Debian stable this 153means that you will probably have to build your own packages. And if the 154problem does not exist in the latest version of Samba we have packaged it 155means that you will have to run the version of Samba you built yourself 156since it is not easy to upload new packages to the stable distribution, 157unless they fix critical security problems. 158 159If you can reproduce the problem in the latest version of Samba then 160it is likely to be a real bug. Your best shot is to search the Samba 161mailing lists to see if it is something that has already been reported 162and fixed - if it is a simple fix we can add the patch to our packages 163without waiting for a new Samba release. 164 165If you decide that your problem deserves to be submitted to the Debian 166Bug Tracking System (BTS) we expect you to be responsive if we request 167more information. If we request more information and do not receive 168any in a reasonable time frame expect to see your bug closed without 169explanation - we can't fix bugs we can't reproduce, and most of the 170time we need more information to be able to reproduce them. 171 172When submitting a bug to the Debian BTS please include the version of 173the Debian package you are using as well as the Debian distribution you 174are using. Think _twice_ about the severity you assign to the bug: we 175are _very_ sensitive about bug severities; the fact that it doesn't 176work for you doesn't mean that the severity must be such that it holds 177a major Debian release. In fact, that it doesn't work for you it 178doesn't mean that it doesn't work for others. So again: think _twice_. 179 180 181Eloy A. Paris <peloy@debian.org> 182Steve Langasek <vorlon@debian.org> 183 184