Using gnu screen

Screen is a full-screen window manager that multiplexes a physical terminal between several processes. In short, you can have a few virtual terminal by using only one physical terminal. Screen is useful when you are accessing servers remotely, or running jobs on the background. When you want to run jobs on the background, it is very useful to run it inside one screen so that you can detached it, and simply log out without worry. Below are a few useful command to be used with screen to get you started.

To start using screen
# screen

To start using screen with sessionname
# screen -S sessionname

To list out all available screen
# screen -ls

To attach to a detached screen
# screen -r

To attach to a detached screen with certain pid
# screen -r pidnumber

To attach to a non detached screen session (multi display mode). Using this mode, you can make other people see what you are doing on your screen
# screen -x

When inside screen:

To kill current screen
ctrl-a k

To detach current screen
ctrl-a d

You cannot use the scroll function when inside screen. To scroll, you have to use screen's copy mode, then you can scroll up or down using your arrow key, pageup and pageup. To exit copy mode, press 'Esc'. To enter copy mode:
ctrl-a [
or
ctrl-a Esc

To monitor terminal for activity (start or stop)
ctrl-a M

To monitor terminal for 30-seconds silence (start or stop)
ctrl-a _

Give name to the terminal
ctrl-a shift-a

View all opened screen (interactive)
ctrl-a "

View all opened screen (non-interactive)
ctrl-a w

Move to the next screen
ctrl-a n

Move to the previous screen
ctrl-a p

Move to screen number
ctrl-a N where N is the number of the screen

Lock screen
ctrl-a x

Kill all windows and terminate screen
ctrl-a \

View help for screen
ctrl-a ?

Creating translation for dotproject

Dotproject is an open source project management system. It is built by default based in English language but whomever wants to translate it to their own native language, dotproject provide language management where the user can use other language in their dotproject. There are two ways to do this translation. First, if available, you can download the pre-translated configuration files from the internet and embed it in your dotproject system. Second, if there is no translation for your language available, you can create your own translation files and do the translation yourself. In this guide, I would like to show you how to do the translation yourself.
The steps:

1. Create a new directory under dotproject/locales directory and name it according to your language iso code. Give appropriate permission to this folder (ex: write permission for others). The code can be found at http://ftp.ics.uci.edu/pub/ietf/http/related/iso639.txtCreate locales.php inside yor newly created folder. This is the content of the file(put it inside php tags):

$dir = basename(dirname(__FILE__));
$LANGUAGE['aa_BB'] = array($dir, 'Language Name (in English)', 'Language name (in Language)', 'xxx');

• aa_BB is the iso 2 character language code 'aa', followed by the ISO 2 character country code 'BB' (http://www.bcpl.net/~j1m5path/isocodes.html)

• The first instance of the language name should be in English The second should be in the native language. The last field 'xxx' is the Microsoft language code (http://msdn2.microsoft.com/en-us/library/ms533052.aspx)

Example of locales.php file for Bahasa Melayu(put it inside php tags):

$dir = basename(dirname(__FILE__));
$LANGUAGES['ms_MY'] = array($dir, 'Malay', 'Bahasa Melayu', 'msl');

2. Create file lang.php inside the newly created folder. The content of the file is similar to the locales.php

3. Log in as system admin to your dotproject system. Go to System Admin > Translation Management and choose your language from the drop down menu. Start translating. DO NOT attempt to edit the INC files directly to create your translation - it won't work.