[SCM] Samba Shared Repository - branch master updated

Stefan Metzmacher metze at samba.org
Mon Aug 29 01:29:03 UTC 2016

The branch, master has been updated
       via  3869663 Removed upgrading-samba4.txt
      from  f5401ff s3-util: Fix asking for username and password in smbget.


- Log -----------------------------------------------------------------
commit 38696630552d449ec3c8e1fbdf6fb8212a96d2c9
Author: Marc Muehlfeld <mmuehlfeld at samba.org>
Date:   Fri Aug 26 13:42:15 2016 +0200

    Removed upgrading-samba4.txt
    This file was about updating early Samba AD alpha versions.
    We describe all important things related to the update process in the Wiki:
    Signed-off-by: Marc Muehlfeld <mmuehlfeld at samba.org>
    Reviewed-by: Stefan Metzmacher <metze at samba.org>
    Autobuild-User(master): Stefan Metzmacher <metze at samba.org>
    Autobuild-Date(master): Mon Aug 29 03:28:11 CEST 2016 on sn-devel-144


Summary of changes:
 upgrading-samba4.txt | 28 ----------------------------
 1 file changed, 28 deletions(-)
 delete mode 100644 upgrading-samba4.txt

Changeset truncated at 500 lines:

diff --git a/upgrading-samba4.txt b/upgrading-samba4.txt
deleted file mode 100644
index 8c74f5a..0000000
--- a/upgrading-samba4.txt
+++ /dev/null
@@ -1,28 +0,0 @@
-Upgrading from an older samba4 installation.
-* Compile the new version of samba4 by following the HOWTO, but do
-  not install it yet, and do not run provision.
-* Stop any samba process
-* Backup your samba4 provision:
-  go into the directory where your samba4 provision is stored (/usr/local/samba by default)
-  do tar cf $HOME/backup.tar private etc var sysvol
-* do make install
-* run 'samba-tool dbcheck'
-This will do a consistency check of the data, and is all most existing
-installations will require.
-If you are upgrading from a quite old provision (Samba 4.0 alpha 13 or
-earlier) then running upgradeprovision will do an upgrade of security
-descriptors, and upgradeprovision --full will perform a more
-comprehensive upgrade of the data (including schema and display
-specifiers).  This attempts to do a new provision, and to then copy
-existing data into that database.
-If you are upgrading from a more recent version, particularly alpha16
-or later, then it is better *NOT* to run upgradeprovision as the
-database format has not changed.
-To upgrade from BIND9 flat files to the internal database store for
-Bind 9 DLZ, use ./source4/scripting/bin/samba_upgradedns

Samba Shared Repository

More information about the samba-cvs mailing list