Server and Client software to interoperate with Windows machines
Go to file
2017-07-06 07:48:15 +02:00
.gitignore Update to Samba 4.7.0rc1 2017-07-05 08:23:19 +02:00
filter-requires-samba.sh Fix and mention bogus perl dependency removal. 2009-02-03 18:45:43 +00:00
gpgkey-52FBC0B86D954B0843324CDC6F33915B6568B7EA.gpg Verify the tarball with the gpg key and amror file from Samba 2017-02-01 15:34:35 +01:00
pam_winbind.conf Update to 3.3.4 2009-04-29 14:26:55 +00:00
README.dc Update the README.dc which is packaged if we do not build the AD DC 2017-07-05 11:09:47 +02:00
README.downgrade Update to 4.0.0rc1. 2012-09-26 14:23:24 +02:00
samba-4.7.0-Do-not-install-_ldb_text.py-if-we-have-system-libldb.patch Do not install conflicting file _ldb_text.py 2017-07-06 07:48:15 +02:00
samba-4.7.0-unittests-Add-missing-stdint.h-include.patch Package Samba with AD DC 2017-07-05 09:43:31 +02:00
samba-4.7.0-unittests-Do-not-install-the-test_dummy-rpc-module.patch Fix build without the testsuite enabled 2017-07-05 11:00:39 +02:00
samba-4.7.0-waf-Only-build-unit-tests-with-selftest-enabled.patch Fix build without the testsuite enabled 2017-07-05 11:00:39 +02:00
samba.log * Wed Oct 8 2007 Simo Sorce <ssorce@redhat.com> 3.2.0-0.pre1.fc9 2007-10-08 21:13:15 +00:00
samba.pamd Update to Samba 4.0.0rc6. 2012-12-04 15:38:51 +01:00
samba.spec Do not install conflicting file _ldb_text.py 2017-07-06 07:48:15 +02:00
smb.conf.example Small fix to the example smb.conf file 2016-06-20 09:41:05 +02:00
smb.conf.vendor Update to Samba 4.4.4 2016-06-07 14:36:53 +02:00
sources Update to Samba 4.7.0rc1 2017-07-05 08:23:19 +02:00

Downgrading Samba
=================

Short version: data-preserving downgrades between Samba versions are not supported

Long version:
With Samba development there are cases when on-disk database format evolves.
In general, Samba Team attempts to maintain forward compatibility and
automatically upgrade databases during runtime when requires.
However, when downgrade is required Samba will not perform downgrade to
existing databases. It may be impossible if new features that caused database
upgrade are in use. Thus, one needs to consider a downgrade procedure before
actually downgrading Samba setup.

Please always perform back up prior both upgrading and downgrading across major
version changes. Restoring database files is easiest and simplest way to get to
previously working setup.

Easiest way to downgrade is to remove all created databases and start from scratch.
This means losing all authentication and domain relationship data, as well as
user databases (in case of tdb storage), printers, registry settings, and winbindd
caches.

Remove databases in following locations:
/var/lib/samba/*.tdb
/var/lib/samba/private/*.tdb

In particular, registry settings are known to prevent running downgraded versions
(Samba 4 to Samba 3) as registry format has changed between Samba 3 and Samba 4.