Install the Oracle JDK 6 in Linux

Due to license issues Ubuntu will no longer distribute Oracle's JDK and JRE. There are no more supported java releases from Ubuntu - Ubuntu officially supports OpenJDK and OpenJRE implementation of Java which is the base for Oracle's own implementation. The instructions below provide a guide to install the official Oracle JDK 6. You will need to regularly update this manually to ensure your installation maintains recommended security and stability fixes. 1, Download the 32bit or 64bit Linux "compressed binary file" - it has a ".bin" file extension 2,Give it permissions to execute              chmod 777 [version]-linux-i586.bin 3, Extract it.               ./[version]-linux-i586.bin 4, JDK 6 package is extracted into ./jdk1.6.0_x directory, for example ./jdk1.6.0_30. 5,   Just rename it to jdk and move to /usr/lib/jvm        mv jdk1.6.0_30 jdk       sudo mkdir /usr/lib/jvm      sudo mv jdk /usr/lib/jvm 6, Update system paths in /etc/environment                      JAVA_HOME=/usr/lib/jvm/jdk PATH=$PATH:$HOME/bin:$JAVA_HOME/bin export JAVA_HOME export JAVA_BIN export PATH ...................................................................................................................................Vijay.

RESETTING MYSQL ROOT PASSWORD IN WINDOWS

1. Log on to your system as Administrator.
2. Stop the MySQL server if it is running. For a server that is running as a Windows service, go to the Services manager: From the Start menu, select Control Panel, then Administrative Tools, then Services. Find the MySQL service in the list and stop it.
   If your server is not running as a service, you may need to use the Task Manager to force it to stop.
   
3. Create a text file containing the following statements. Replace the password with the password that you want to use.
   

   UPDATE mysql.user SET Password=PASSWORD('MyNewPass') WHERE User='root';
   FLUSH PRIVILEGES;

   Write the UPDATE and FLUSH statements each on a single line. The UPDATE statement resets the password for all root accounts, and the FLUSH statement tells the server to reload the grant tables into memory so that it notices the password change.
   
4. Save the file. For this example, the file will be named C:\mysql-init.txt.
5. Open a console window to get to the command prompt: From the Start menu, select Run, then enter cmd as the command to be run.
6. Start the MySQL server with the special --init-file option (notice that the backslash in the option value is doubled):
   

   C:\> C:\mysql\bin\mysqld-nt --init-file=C:\\mysql-init.txt
   

   If you installed MySQL to a location other than C:\mysql, adjust the command accordingly.
   The server executes the contents of the file named by the --init-file option at startup, changing each root account password.
   You can also add the --console option to the command if you want server output to appear in the console window rather than in a log file.
   If you installed MySQL using the MySQL Installation Wizard, you may need to specify a --defaults-file option:
   

   C:\> "C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt.exe"
            --defaults-file="C:\\Program Files\\MySQL\\MySQL Server 5.0\\my.ini"
            --init-file=C:\\mysql-init.txt
   

   The appropriate --defaults-file setting can be found using the Services Manager: From the Start menu, select Control Panel, then Administrative Tools, then Services. Find the MySQL service in the list, right-click it, and choose the Properties option. The Path to executable field contains the --defaults-file setting.
   
7. After the server has started successfully, delete C:\mysql-init.txt.

Bash script to create multiple database with different username and password - using by reading multiple files with bash.

#!/bin/bash
## copyright vijayakumarcs

MYSQLADM="root"
MYSQLADMPASS="password"
MYSQLADMIP="localhost"
function readfiles()
{
local FD1=7
local FD3=9
    local FD2=8
    local file1=$1
    local file2=$2
        local file3=$3
    local eof1=0
    local eof2=0
local eof3=0
exec 9<$file3
exec 7<$file1
exec 8<$file2

while [[ $eof1 -eq 0 ]]
    do
if read data1 <&$FD1;  
then
read data2 <&$FD2
read data3 <&$FD3
           



mysql -u "$MYSQLADM" -h "$MYSQLADMIP" -p"$MYSQLADMPASS" mysql -e "CREATE DATABASE $data1; GRANT ALL PRIVILEGES ON  $data1.* TO $data2@localhost IDENTIFIED BY '$data3';"
else
eof1=1
   
fi
    done
}

readfiles user1 user2 user3

FSMO Roles in Active Directory

Windows 2000/2003 Multi-Master Model

A multi-master enabled database, such as the Active Directory, provides the flexibility of allowing changes to occur at any DC in the enterprise, but it also introduces the possibility of conflicts that can potentially lead to problems once the data is replicated to the rest of the enterprise. One way Windows 2000/2003 deals with conflicting updates is by having a conflict resolution algorithm handle discrepancies in values by resolving to the DC to which changes were written last (that is, "the last writer wins"), while discarding the changes in all other DCs. Although this resolution method may be acceptable in some cases, there are times when conflicts are just too difficult to resolve using the "last writer wins" approach. In such cases, it is best to prevent the conflict from occurring rather than to try to resolve it after the fact.
For certain types of changes, Windows 2000/2003 incorporates methods to prevent conflicting Active Directory updates from occurring.

Windows 2000/2003 Single-Master Model

To prevent conflicting updates in Windows 2000/2003, the Active Directory performs updates to certain objects in a single-master fashion.
In a single-master model, only one DC in the entire directory is allowed to process updates. This is similar to the role given to a primary domain controller (PDC) in earlier versions of Windows (such as Microsoft Windows NT 4.0), in which the PDC is responsible for processing all updates in a given domain.
In a forest, there are five FSMO roles that are assigned to one or more domain controllers. The five FSMO roles are:

Schema Master:

The schema master domain controller controls all updates and modifications to the schema. Once the Schema update is complete, it is replicated from the schema master to all other DCs in the directory. To update the schema of a forest, you must have access to the schema master. There can be only one schema master in the whole forest.

Domain naming master:

The domain naming master domain controller controls the addition or removal of domains in the forest. This DC is the only one that can add or remove a domain from the directory. It can also add or remove cross references to domains in external directories. There can be only one domain naming master in the whole forest.

Infrastructure Master:

When an object in one domain is referenced by another object in another domain, it represents the reference by the GUID, the SID (for references to security principals), and the DN of the object being referenced. The infrastructure FSMO role holder is the DC responsible for updating an object's SID and distinguished name in a cross-domain object reference. At any one time, there can be only one domain controller acting as the infrastructure master in each domain.
Note: The Infrastructure Master (IM) role should be held by a domain controller that is not a Global Catalog server (GC). If the Infrastructure Master runs on a Global Catalog server it will stop updating object information because it does not contain any references to objects that it does not hold. This is because a Global Catalog server holds a partial replica of every object in the forest. As a result, cross-domain object references in that domain will not be updated and a warning to that effect will be logged on that DC's event log. If all the domain controllers in a domain also host the global catalog, all the domain controllers have the current data, and it is not important which domain controller holds the infrastructure master role.

Relative ID (RID) Master:

The RID master is responsible for processing RID pool requests from all domain controllers in a particular domain. When a DC creates a security principal object such as a user or group, it attaches a unique Security ID (SID) to the object. This SID consists of a domain SID (the same for all SIDs created in a domain), and a relative ID (RID) that is unique for each security principal SID created in a domain.  Each DC in a domain is allocated a pool of RIDs that it is allowed to assign to the security principals it creates. When a DC's allocated RID pool falls below a threshold, that DC issues a request for additional RIDs to the domain's RID master. The domain RID master responds to the request by retrieving RIDs from the domain's unallocated RID pool and assigns them to the pool of the requesting DC. At any one time, there can be only one domain controller acting as the RID master in the domain.

PDC Emulator:
 
The PDC emulator is necessary to synchronize time in an enterprise. Windows 2000/2003 includes the W32Time (Windows Time) time service that is required by the Kerberos authentication protocol. All Windows 2000/2003-based computers within an enterprise use a common time. The purpose of the time service is to ensure that the Windows Time service uses a hierarchical relationship that controls authority and does not permit loops to ensure appropriate common time usage.
The PDC emulator of a domain is authoritative for the domain. The PDC emulator at the root of the forest becomes authoritative for the enterprise, and should be configured to gather the time from an external source. All PDC FSMO role holders follow the hierarchy of domains in the selection of their in-bound time partner.
In a Windows 2000/2003 domain, the PDC emulator role holder retains the following functions:

• Password changes performed by other DCs in the domain are replicated preferentially to the PDC emulator.
• Authentication failures that occur at a given DC in a domain because of an incorrect password are forwarded to the PDC emulator before a bad password failure message is reported to the user.
• Account lockout is processed on the PDC emulator.
• Editing or creation of Group Policy Objects (GPO) is always done from the GPO copy found in the PDC Emulator's SYSVOL share, unless configured not to do so by the administrator.
• The PDC emulator performs all of the functionality that a Microsoft Windows NT 4.0 Server-based PDC or earlier PDC performs for Windows NT 4.0-based or earlier clients.

This part of the PDC emulator role becomes unnecessary when all workstations, member servers, and domain controllers that are running Windows NT 4.0 or earlier are all upgraded to Windows 2000/2003. The PDC emulator still performs the other functions as described in a Windows 2000/2003 environment.
At any one time, there can be only one domain controller acting as the PDC emulator master in each domain in the forest.

LDAP Authentication for Subversion on Ubuntu Feisty

A useful post regarding svn configuration on ubuntu severs... This URL will give you more information regarding svn server and its configuration files.

http://www.itguyonline.com/blog/2007/05/02/ldap-authentication-for-subversion-on-ubuntu-feisty/

https://help.ubuntu.com/community/Subversion