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