This freeware driver Ext2 Installable File System For Windows to be installed on Windows NT4.0/2000/XP/2003/Vista/2008 will mount ext2 file system as a separate drive letter. However permission may not be well handled due to Windows issue. To handle ext3, do read the FAQ found in the website

Saturday, June 25, 2011

*The subsequent commands will continue to execute independently whether the prior commands fail or not. This will have impact on subsequent commands
2. Executing Commands in Sequence (Interdependent)
(Put && operator in between commands)

# ./configure && make && make install

* The && is a logical operator. In other words, if the prior commands fail, the subsequent commands will fail

Wednesday, June 22, 2011

Today I encounter this strange error. At /var/log/messages "kernel: ib_srp: ASYNC event= 17 on device= mlx4_0".
I'm still not sure of it though

The IB disconnection to SCSI RDMA Protocol (SRP) target was able to be reconnected but since SRP Target driver is designed to work directly on top of OpenFabrics OFED or Infiniband drivers in Linux kernel tree. I guess the fix could be a upgrading and patching of the Kernel or OFED drivers.

Saturday, June 18, 2011

If you forget to use Screen Session to allow you to terminate your shell session without terminating the job that have been running in the foreground, and it is too late to do a nohup command, you may want to consider these alternatives.

You can use the shell command called disown that detach the process from theshell that started it. Here's how to do it

Step 1:
Use Ctrl + Z to suspend the running program

Step 2:
Type bg to restart it running in the background

# bg

Step 3: Get a list of jobs running in your shell

# jobs

Step 4: Detach it from the shell

# jobs %1

(Remember to put the % before the job number which in this example is 1)

Thursday, June 16, 2011

Git is a free & open source, distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Every Git clone is a full-fledged repository with complete history and full revision tracking capabilities, not dependent on network access or a central server. Branching and merging are fast and easy to do.

Tuesday, June 14, 2011

Sometimes whille connecting to another remote server via, there is this unplesant disconnection. How do we deal with it. You have to look at OpenSSH configuration

# /etc/ssh/sshd_config

ClientAliveInterval 15
ClientAliveCountMax 3

From the man page from ClientAliveIntervalSets a timeout interval in seconds after which if no data has been received from the client, sshd will send a message through the encrypted channel to request a response from the client. The default
is 0, indicating that these messages will not be sent to the client. This option applies to protocol version 2 only.

ClientAliveCountMaxSets the number of client alive messages (see above) which may be sent without sshd receiving any messages back from the client. If this threshold is reached while client alive messages are being
sent, sshd will disconnect the client, terminating the session.

If ClientAliveInterval (above) is set to 15, and ClientAliveCountMax is left 3, unresponsive ssh clients will be disconnected after approximately 45 seconds.

Do note that the ClientAlive messages are sent through the encrypted channel. On the other hand, The TCPKeepAlive Messages is not sent through encrypted Channel and thus spoofable.