4.2 EPM on coLinux

Installing the coLinux version of EPM

At first, you need to download coLinux from http://www.colinux.org/ and install it onto your PC. Next, download the coLinux image that contains EPM from http://www.empirical.jp/ and unzip it (to the coLinux directory). Edit the paths in EPM092.coLinux.xml according to your environment.

e.g.
<block_device index="0" path="\DosDevices\C:\coLinux\img\epm092_deb_e.img" enabled="true" />
<block_device index="1" path="\DosDevices\C:\coLinux\img\blank_256.img" enabled="true" />

From the command prompt, run coLinux. The Cooperative Linux console will appear.

e.g. C:\colinx\coliux-daemon.exe -c img\EPM092.coLinux.xml
(when you install coLinux in "C:\coLinux". (Default is "C:\Program Files\coLinux".))

Login (default account: root, password: empirical) and edit the network settings according to your environment.

e.g. # vi /etc/networking/interfaces /etc/resolv.conf

Restart the network drivers to reflect the change.

e.g.# /etc/init.d/networkinging restart

Using a browser, you can see the EPM webpage (e.g. http://192.168.154.1/index.html).

About the initial settings

Initially, you have two projects as follows.

All accounts use "empirical" as the initial password. We recommend changing it and deleting unnecessary accounts when you use EPM as the server for supporting your software development.

The default IP addresses (eth0) and host name are as follows.

address: 192.168.154.1
gateway: 192.168.154.254
netmask: 255.255.255.0
hostname: empirical.localdomain

The DNS server address specified in /etc/resolv.conf is 192.168.154.254. Modify these addresses depending on your needs.

When using the coLinux version of EPM through the network, you need configurations such as "the connection to an external sever and clients." By doing this, you can use the coLinux version of EPM with the addresses as follows.

e.g.
URL: http://empirical.localdomain/
mail address: epm@empirical.localdomain

When changing the default IP address and host name, you need to modify the following files. (note: we might not have listed all files. For the details on how to change the files, see the manuals of Debian GNU/Linux, Postfix, Apache, Gnatsweb, Mailman, and ViewCVS.

The connection to an external sever and clients

The current version of coLinux seem not to support dynamic IP allocation using DHCP. When using the coLinux version of EPM, use the IP addresses allowed by your organization.

In addition, you need to register a host name with a DNS server since clients using some functions of open source tools need to use the hostname. If this is impossible, you can register IP addresses and host names with all clients.

e.g.
WindowsXP: C:\WINDOWS\system32\drivers\etc\hosts

# Copyright (c) 1993-1999 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
#102.54.94.97rhino.acme.com# source server
#38.25.63.10x.acme.com# x client host

127.0.0.1 localhost
192.168.154.1 empirical.localdomain

Linux: /etc/hosts

# Do not remove the following line, or various programs
# that require network functionality will fail.

127.0.0.1 localhost
192.168.154.1 empirical.localdomain

If you forward mails from a mail server on the internet to Postfix and Mailman on the EPM server, it is necessary to refer to the host name of the EPM server from an external sever. Carefully use or change host names.

Adding a new project to EPM

When adding a new project, you need the following operations. This example adds the “test_prj” project. See the documents for each tool for more details.

misc.

The coLinux version of EPM uses Debian GNU/Linux. This section omits descriptions on backup and maintenance for each open source tool. You can backup the entire system by copying image files.

Using the coLinux version of EPM

This is an example of how to use the coLinux version of EPM for development. The example assumes the use of Window PCs as client machines, “default project” as your project, and “empirical.localdomain” as the initial host name.

Prepare a browser, mailer, CVS client (WinCVS or Eclipse). Configure the host name by using the DNS server in the network or adding to the hosts file as mentioned above.

Replace XXXXX by each developer (user01-user20) in the following decription.

When using SSH, CVSROOT for operating CVS of WinCVS (or Eclipse) will be use xxxxx@empirical.localdomain:/var/cvsroot/default. In other cases, modify the configuration according to your needs. If you want to view a repository, you can see it from http://empirical.localdomain/viewcvs/viewcvs.cgi/?cvsroot=Default by using ViewCVS.

You can use SMTP and POP3 because postfix and popa3d are installed. The server name is empirical.localdomain. The email address for each developer is XXXXX@empirical.localdomain. The address for the project is default@empirical.localdomain. As an initial setting, epm@empirical.localdomain and user01@empirical.localdomain ~ user20@empirical.localdomain are registered. Modify these depending on your needs. You can manage MLs from http://empirical.localdomain/mailman/admin/default and GNATS from http://empirical.localdomain/cgi-bin/gnatsweb.pl?database=default.


Copyright(C)2004-2005 Nara Institute of Science and Technology, National University Corporation