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