- Timestamp:
- Nov 24, 2016, 1:14:11 PM (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
vendor/current/docs-xml/Samba3-ByExample/SBE-UpgradingSamba.xml
r414 r988 2 2 <!DOCTYPE chapter PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc"> 3 3 <chapter id="upgrades"> 4 <title>Updating Samba -3</title>4 <title>Updating Samba</title> 5 5 6 6 <para> … … 17 17 <indexterm><primary>smbpasswd</primary></indexterm> 18 18 <indexterm><primary>passdb backend</primary></indexterm> 19 There has also been much talk about migration of Samba -3from an smbpasswd19 There has also been much talk about migration of Samba from an smbpasswd 20 20 passdb backend to the use of the tdbsam or ldapsam facilities that are new 21 to Samba -3.21 to Samba. 22 22 </para> 23 23 … … 232 232 <indexterm><primary>SAS</primary></indexterm> 233 233 <indexterm><primary>SID</primary></indexterm> 234 In Samba -3on a domain controller (PDC or BDC), the domain name controls the domain234 In Samba on a domain controller (PDC or BDC), the domain name controls the domain 235 235 SID. On all prior versions the hostname (computer name, or NetBIOS name) controlled 236 236 the SID. On a standalone server the hostname still controls the SID. … … 240 240 <indexterm><primary>net</primary><secondary>getlocalsid</secondary></indexterm> 241 241 <indexterm><primary>net</primary><secondary>setlocalsid</secondary></indexterm> 242 The local machine SID can be backed up using this procedure (Samba -3):242 The local machine SID can be backed up using this procedure (Samba): 243 243 <screen> 244 244 &rootprompt; net getlocalsid > /etc/samba/my-local-SID … … 262 262 <para> 263 263 Where the <filename>secrets.tdb</filename> file exists and a version of Samba 2.x or later 264 has been used, there is no specific need to go through this update process. Samba -3has the264 has been used, there is no specific need to go through this update process. Samba has the 265 265 ability to read the older tdb file and to perform an in-situ update to the latest tdb format. 266 266 This is not a reversible process &smbmdash; it is a one-way upgrade. … … 296 296 &rootprompt; rpcclient hostname lsaquery -Uroot%password 297 297 </screen> 298 This can also be done with Samba -3by executing:298 This can also be done with Samba by executing: 299 299 <screen> 300 300 &rootprompt; net rpc info -Uroot%password … … 431 431 <para> 432 432 <indexterm><primary>compile-time</primary></indexterm> 433 Samba -3provides a neat new way to track the location of all control files as well as to433 Samba provides a neat new way to track the location of all control files as well as to 434 434 find the compile-time options used as the Samba package was built. Here is how the dark 435 435 secrets of the internals of the location of control files within Samba executables can … … 482 482 <indexterm><primary>internationalization</primary></indexterm> 483 483 Samba-2.x had no support for Unicode; instead, all national language character-set support in file names 484 was done using particular locale codepage mapping techniques. Samba -3supports Unicode in file names, thus484 was done using particular locale codepage mapping techniques. Samba supports Unicode in file names, thus 485 485 providing true internationalization support. 486 486 </para> … … 496 496 <para> 497 497 <indexterm><primary>UTF-8</primary></indexterm> 498 Files that are created with Samba -3will use UTF-8 encoding. Should the file system ever end up with a498 Files that are created with Samba will use UTF-8 encoding. Should the file system ever end up with a 499 499 mix of codepage (unix charset)-encoded file names and UTF-8-encoded file names, the mess will take some 500 500 effort to set straight. … … 682 682 <para> 683 683 <indexterm><primary>parameters</primary></indexterm> 684 The following parameters are new to Samba -3and should be correctly configured.684 The following parameters are new to Samba and should be correctly configured. 685 685 Please refer to <link linkend="secure"/> through <link linkend="net2000users"/> 686 686 in this book for examples of use of the new parameters shown here: … … 710 710 <indexterm><primary>add user script</primary></indexterm> 711 711 The <parameter>add machine script</parameter> functionality was previously 712 handled by the <parameter>add user script</parameter>, which in Samba -3is712 handled by the <parameter>add user script</parameter>, which in Samba is 713 713 used exclusively to add user accounts. 714 714 </para> … … 749 749 Samba version 2.x could be compiled for use either with or without LDAP. 750 750 The LDAP control settings in the &smb.conf; file in this old version are 751 completely different (and less complete) than they are with Samba -3. This751 completely different (and less complete) than they are with Samba. This 752 752 means that after migrating the control files, it is necessary to reconfigure 753 753 the LDAP settings entirely. … … 828 828 * ldapsam - attribute rich account storage and retrieval 829 829 backend utilizing an LDAP directory. 830 * ldapsam_compat - a 2.2 backward compatible LDAP account831 backend832 830 833 831 Certain functions of the smbpasswd(8) tool have been split between the 834 832 new smbpasswd(8) utility, the net(8) tool, and the new pdbedit(8) 835 833 utility. See the respective man pages for details. 836 837 ######################################################################838 LDAP839 ####840 841 This section outlines the new features affecting Samba / LDAP842 integration.843 844 New Schema845 ----------846 847 A new object class (sambaSamAccount) has been introduced to replace848 the old sambaAccount. This change aids us in the renaming of849 attributes to prevent clashes with attributes from other vendors.850 There is a conversion script (examples/LDAP/convertSambaAccount) to851 modify and LDIF file to the new schema.852 853 Example:854 855 $ ldapsearch .... -b "ou=people,dc=..." > sambaAcct.ldif856 $ convertSambaAccount --sid=<Domain SID> \857 --input=sambaAcct.ldif --output=sambaSamAcct.ldif \858 --changetype=[modify|add]859 860 The <DOM SID> can be obtained by running 'net getlocalsid861 <DOMAINNAME>' on the Samba PDC as root. The changetype determines862 the format of the generated LDIF output--either create new entries863 or modify existing entries.864 865 The old sambaAccount schema may still be used by specifying the866 "ldapsam_compat" passdb backend. However, the sambaAccount and867 associated attributes have been moved to the historical section of868 the schema file and must be uncommented before use if needed.869 The 2.2 object class declaration for a sambaAccount has not changed870 in the 3.0 samba.schema file.871 872 Other new object classes and their uses include:873 874 * sambaDomain - domain information used to allocate rids875 for users and groups as necessary. The attributes are added876 in 'ldap suffix' directory entry automatically if877 an idmap uid/gid range has been set and the 'ldapsam'878 passdb backend has been selected.879 880 * sambaGroupMapping - an object representing the881 relationship between a posixGroup and a Windows882 group/SID. These entries are stored in the 'ldap883 group suffix' and managed by the 'net groupmap' command.884 885 * sambaUnixIdPool - created in the 'ldap idmap suffix' entry886 automatically and contains the next available 'idmap uid' and887 'idmap gid'888 889 * sambaIdmapEntry - object storing a mapping between a890 SID and a UNIX uid/gid. These objects are created by the891 idmap_ldap module as needed.892 893 * sambaSidEntry - object representing a SID alone, as a Structural894 class on which to build the sambaIdmapEntry.895 896 834 897 835 New Suffix for Searching … … 974 912 975 913 <sect2> 976 <title>Samba -3to Samba-3 Updates on the Same Server</title>914 <title>Samba to Samba-3 Updates on the Same Server</title> 977 915 978 916 <para> 979 917 The guidance in this section deals with updates to an existing 980 Samba -3server installation.918 Samba server installation. 981 919 </para> 982 920 … … 985 923 986 924 <para> 987 With the provision that the binary Samba -3package has been built988 with the same path and feature settings as the existing Samba -3989 package that is being updated, an update of Samba -3versions 3.0.0925 With the provision that the binary Samba package has been built 926 with the same path and feature settings as the existing Samba 927 package that is being updated, an update of Samba versions 3.0.0 990 928 through 3.0.4 can be updated to 3.0.5 without loss of functionality 991 929 and without need to change either the &smb.conf; file or, where … … 1001 939 <indexterm><primary>schema</primary></indexterm> 1002 940 <indexterm><primary>LDAP</primary><secondary>schema</secondary></indexterm> 1003 When updating versions of Samba -3prior to 3.0.6 to 3.0.6 through 3.0.10,941 When updating versions of Samba prior to 3.0.6 to 3.0.6 through 3.0.10, 1004 942 it is necessary only to update the LDAP schema (where LDAP is used). 1005 Always use the LDAP schema file that is shipped with the latest Samba -3943 Always use the LDAP schema file that is shipped with the latest Samba 1006 944 update. 1007 945 </para> … … 1065 1003 1066 1004 <sect2> 1067 <title>Migrating Samba -3to a New Server</title>1005 <title>Migrating Samba to a New Server</title> 1068 1006 1069 1007 <para>
Note:
See TracChangeset
for help on using the changeset viewer.
