* First, After you download and burn the appropriate ISO file from the Ubuntu web site.
* Boot the system from the CD-ROM drive.
* At the boot prompt you will be asked to select the language. Then the installation process begins by asking for your keyboard layout. You can say “No”. The installer then discovers your hardware configuration, and configures the network settings using DHCP or configure the network manually.
* Next, the installer asks for the system’s hostname and Time Zone.
* You can then choose from several options to configure the hard drive layout. Please remember that you should not install LAMP package at this initial set up.
* After Ubuntu base system is then installed, a new user is setup, this user will have root access through the sudo utility. After the user is setup, you will be asked to encrypt your home directory.
* The next step in the installation process is to decide how you want to update the system.
* Finally, the last step before rebooting is to set the clock to UTC.

[Note]

At some point during the installation process you may want to read the help screen provided by the installation system. To do this, press F1.

For the software used, please refer toSimple Rails production server setup in Ubuntu post.

First you need to set up Ubuntu server. You can get Ubuntu server edition. There is an excellent post showing you how to set up Ubuntu server. I will show you very simple way late when I have time.

Install the following packages.
MySQL database software; server application, client application, and client libraries
Apache web server v 2.0 or later
Ruby language interpreter v 1.8.6 or later, with mySQL support, Ruby on Rails libraries, and the Mongrel application server
Mail Transport Agent, such as Postfix or Sendmail
Cron scheduling daemon
SSHd server application for secure management.

Then put up the following third party plugins.
The ruby on rails application contains the following third party plugins.

sql_session_store
quickbooks_integration
BlueCloth-1.0.0
activeresource
uuidtools-1.0.3

Final set up production.

Stay tuned.

MySQL database software; server application, client application, and client libraries
Apache web server v 2.0 or later
Ruby language interpreter v 1.8.6 or later, with mySQL support, Ruby on Rails libraries, and the Mongrel application server
Mail Transport Agent, such as Postfix or Sendmail
Cron scheduling daemon
SSHd server application for secure management.

The ruby on rails application contains the following third party plugins.

sql_session_store
quickbooks_integration
BlueCloth-1.0.0
activeresource
uuidtools-1.0.3

I will show you how to set up  step by step.

Stay tune!

Please do not panic.

You may try the following steps to boot your PC.
1.Insert the Windows XP CD-ROM into the CD-ROM drive, and then restart the computer.

Click to select any options that are required to start the computer from the CD-ROM drive if you are prompted.

2.When the “Welcome to Setup” screen appears, press R to start the Recovery Console.

3.If you have a dual-boot or multiple-boot computer, select the installation that you must access from the Recovery Console.

4.When you are prompted, type the Administrator password. If the administrator password is blank, just press ENTER.

5.At the command prompt, type chkdsk /r , and then press ENTER. It took about 2 hours to finish.

6.At the command prompt, type exit , and then press ENTER to restart your computer.

This takes a bit longer, but the system should boot back into Windows.

Here is an example of a statement that retrieves information from INFORMATION_SCHEMA.

mysql>

SELECT table_name, table_type FROM information_schema.tables WHERE table_schema = ‘yourdatabasename ORDER BY table_name DESC;

You can use stored procedure to do the same thing.

mysql>

DROP PROCEDURE GetAlltables;
DELIMITER /
CREATE PROCEDURE GetAlltables()
BEGIN
SELECT table_name FROM information_schema.tables WHERE table_schema = ‘yourdatabasename’ ORDER BY table_name DESC;
END /
DELIMITER ;

Then call

CALL GetAlltables();

For Windows system, follow the steps listed below.

Use the following procedure for resetting the password for any MySQL root accounts on Windows:

For unix kind of system,follow the steps listed below.

1.  Log on to your system as the Unix mysql user that the mysqld server runs as.
2.  Locate the .pid file that contains the server’s process ID. The exact location and name of this file depend on your distribution, host name, and configuration. Common locations are /var/lib/mysql/, /var/run/mysqld/, and /usr/local/mysql/data/. Generally, the file name has an extension of .pid and begins with either mysqld or your system’s host name.

You can stop the MySQL server by sending a normal kill (not kill -9) to the mysqld process, using the path name of the .pid file in the following command:

shell> kill `cat /mysql-data-directory/host_name.pid`

3. Create a text file and place the following statements in it. Replace the password with the password that you want to use.

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

The FLUSH statement tells the server to reload the grant tables into memory.
4.  Save the file. For this example, the file will be named /home/me/mysql-init.
5.  Start the MySQL server with the special –init-file option:

shell> mysqld_safe –init-file=/home/me/mysql-init &
6. After the server has started successfully, delete /home/me/mysql-init.

You should now be able to connect to MySQL as root using the new password.

You can also set the new password using the mysql client if this is run under your local box:

1. Stop mysqld and restart it with the –skip-grant-tables option.
2. Connect to the mysqld server with this command:

shell> mysql

3. Issue the following statements in the mysql client. Replace the password with the password that you want to use.

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

You should now be able to connect to MySQL as root using the new password.

You may argue that Defects/KLOC doesn’t supply enough information about Product Quality. But one thing for sure is if the rate of Defects/KLOC for the similar products is high, there is certainly something wrong with development process or developer skills.

I noticed that if development follows well defined architecture might help reduce such Defects/KLOC rate. This is what I noticed from evaluating one of Ruby on Rails projects.

If you have any questions, comments and suggestions, please let me know. Thanks.