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