<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>waelchatila.com - Unix/Linux category</title>
  <link>http://waelchatila.com:80/categories/unixlinux/</link>
  <description>Notes on Software, Engineering and Science</description>
  <language>en</language>
  <copyright>Wael Chatila</copyright>
  <lastBuildDate>Fri, 23 May 2008 05:27:00 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>RXTX on Gumstix</title>
    <link>http://waelchatila.com:80/2007/08/24/1187975400000.html</link>
    
      
        <description>
          &lt;p&gt;
Since it could be tricky to get the RXTX sources compiling properly for the gumstix platforms I thought I&#039;d spare anyone the pain by providing my binaries. 
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#034;http://www.icegreen.com/rxtx_gumstix/librxtxSerial_PXA255.so&#034;&gt;librxtxSerial_PXA255.so &lt;/a&gt; (Connex / Basix)&lt;/li&gt;
&lt;li&gt;&lt;a href=&#034;http://www.icegreen.com/rxtx_gumstix/librxtxSerial_PXA270.so&#034;&gt;librxtxSerial_PXA270.so &lt;/a&gt; (Verdex)&lt;/li&gt;
&lt;/ul&gt;

However, since you&#039;re here, I would advise against using java on the gum. Sure, the programs themselves are a breeze to develop, but getting jam and classpath to compile and run properly can very well take a considerable amount of time. Just think of the reason why you are reading this. Chances are you probably have troubles getting the RXTX sources to compile or run smoothly. Just do yourself a favor, write it in small fast c/c++ or something.
        </description>
      
      
    
    
    
    <category>Unix/Linux</category>
    
    <comments>http://waelchatila.com:80/2007/08/24/1187975400000.html#comments</comments>
    <guid isPermaLink="true">http://waelchatila.com:80/2007/08/24/1187975400000.html</guid>
    <pubDate>Fri, 24 Aug 2007 17:10:00 GMT</pubDate>
  </item>
  
  <item>
    <title>How to move a subversion repository to another server</title>
    <link>http://waelchatila.com:80/2007/03/06/1173223980000.html</link>
    
      
        <description>
          My closet server died last night. No big deal it was over ten years old and was running at 233MHz...besides it was my wife&#039;s old computer hehe. My friend Imran gave me one of his old work machines and I&#039;ve been moving stuff over. Since I had a svn repository on the old machine the situation presented itself with a problem to move the whole repository. Luckily the good people behind svn have thought about this and provide out-of-the box commands to do this. &lt;p/&gt;On the old server machine do.
&lt;div class=&#034;codeSample&#034;&gt;
svnadmin dump &lt;i&gt;repositoryPath&lt;/i&gt; &amp;gt; repository.dumpfile&lt;br&gt;
&lt;/div&gt;

File transfer the &lt;i&gt;repository.dumpfile&lt;/i&gt; file to the new server machine and over there do

&lt;div class=&#034;codeSample&#034;&gt;
cd /path/to/new-repository-parent-directory&lt;br&gt;
svnadmin create &lt;i&gt;repository-name&lt;/i&gt;&lt;br&gt;
svnadmin load &lt;i&gt;repository-name&lt;/i&gt; &lt; repository.dumpfile&lt;br&gt;
&lt;/div&gt;

Then on your client type 
&lt;div class=&#034;codeSample&#034;&gt;
svn switch --relocate &lt;i&gt;oldurl&lt;/i&gt; &lt;i&gt;newurl&lt;/i&gt;
&lt;/div&gt;
        </description>
      
      
    
    
    
    <category>Unix/Linux</category>
    
    <category>Windows</category>
    
    <comments>http://waelchatila.com:80/2007/03/06/1173223980000.html#comments</comments>
    <guid isPermaLink="true">http://waelchatila.com:80/2007/03/06/1173223980000.html</guid>
    <pubDate>Tue, 06 Mar 2007 23:33:00 GMT</pubDate>
  </item>
  
  <item>
    <title>AJAX Remote Controlled Lego Robot</title>
    <link>http://waelchatila.com:80/2006/07/13/1152788433678.html</link>
    
      
      
        <description>
          This article shows how to remote control a real world lego robot using AJAX technology.&lt;p&gt;&lt;a href=&#034;http://waelchatila.com:80/2006/07/13/1152788433678.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
          &lt;p&gt;&lt;a href="http://waelchatila.com:80/2006/07/13/1152788433678.html"&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
    
    
    <category>Unix/Linux</category>
    
    <category>C++</category>
    
    <category>AJAX</category>
    
    <category>Hardware</category>
    
    <category>Games &amp; Fun</category>
    
    <comments>http://waelchatila.com:80/2006/07/13/1152788433678.html#comments</comments>
    <guid isPermaLink="true">http://waelchatila.com:80/2006/07/13/1152788433678.html</guid>
    <pubDate>Thu, 13 Jul 2006 11:00:33 GMT</pubDate>
  </item>
  
  <item>
    <title>Installing ZyXEL G-360 Wireless 802.11g+ on Fedora Core 4</title>
    <link>http://waelchatila.com:80/2006/01/16/1137404001340.html</link>
    
      
        <description>
          Instructions are based and extended on the instruction found on &lt;a href=&#034;http://acx100.sourceforge.net/wiki/ACX&#034;&gt;http://acx100.sourceforge.net/wiki/ACX&lt;/a&gt;
&lt;br&gt;&lt;br&gt;
The ZyXEL PCI card is using the Texas Instruments ACX 111 chipset. There is a great open source project located at &lt;a href=&#034;http://acx100.sourceforge.net&#034;&gt;http://acx100.sourceforge.net&lt;/a&gt; providing drivers for Linux users.&lt;br&gt;
Although it might be possible to use the &lt;a href=&#034;http://ndiswrapper.sourceforge.net&#034;&gt;NdisWrapper&lt;/a&gt; project, you might have problems finding a working windows driver if you have a 64bit processor (which I do). (As of the date of this blog entry, ZyXEL has no 64bit driver for this card). 
&lt;br&gt;&lt;br&gt;The ACX100 project should work with both 32- and 64-bit systems.
&lt;p&gt;
The Installation requires
&lt;ul&gt;
&lt;li&gt;Downloading the Source&lt;/li&gt;
&lt;li&gt;Downloading Kernel Source&lt;/li&gt;
&lt;li&gt;Downloading Firmware&lt;/li&gt;
&lt;li&gt;Compiling Source&lt;/li&gt;
&lt;li&gt;Configuration&lt;/li&gt;
&lt;/ul&gt;
&lt;/p&gt;

&lt;!-- - - - - - - - - - - - - - - - - - --&gt;
&lt;h2&gt;Downloading the Source&lt;/h2&gt;
Run the following commands as root
&lt;div class=&#034;codeSample&#034;&gt;
mkdir /usr/src/acx-20051202
cd /usr/src/acx-20051202
wget http://acx100.erley.org/acx-20051202.tar.bz2
tar xjvf acx-20051202.tar.bz2
&lt;/div&gt;
&lt;!-- - - - - - - - - - - - - - - - - - --&gt;
&lt;h2&gt;Downloading Kernel Source&lt;/h2&gt;
Most probably its already on your machine, if not run
&lt;div class=&#034;codeSample&#034;&gt;
yum install kernel-devel
&lt;/div&gt;
&lt;!-- - - - - - - - - - - - - - - - - - --&gt;
&lt;h2&gt;Downloading Firmware&lt;/h2&gt;
Download and install the firmware with the following commands
&lt;div class=&#034;codeSample&#034;&gt;
cd /lib/firmware
wget http://acx100.erley.org/acx_fw/acx111_netgear_wg311v2/fw1/FwRad16.bin_1.2.1.34
ln -s FwRad16.bin_1.2.1.34 tiacx111c16
ln -s FwRad16.bin_1.2.1.34 FwRad16.bin
&lt;/div&gt;
&lt;!-- - - - - - - - - - - - - - - - - - --&gt;
&lt;h2&gt;Compiling Source&lt;/h2&gt;
I found that I had to modify the sources a tiny bit to only compile the PCI parts by commenting out the USB parts, in order to get things to work.
&lt;p&gt;
Edit the following line in /usr/src/acx-20051202/Makefile 
&lt;div class=&#034;codeSample&#034;&gt;
&lt;font color=&#034;red&#034;&gt;&lt;strike&gt;acx-obj-y += usb.o&lt;/strike&gt;&lt;/font&gt;
#acx-obj-y += usb.o
&lt;/div&gt;

And in /usr/src/acx-20051202/acx_config.h, edit the following line
&lt;div class=&#034;codeSample&#034;&gt;
&lt;font color=&#034;red&#034;&gt;&lt;strike&gt;#define CONFIG_ACX_USB 1&lt;/strike&gt;&lt;/font&gt;
//#define CONFIG_ACX_USB 1
&lt;/div&gt;

Now compile with
&lt;div class=&#034;codeSample&#034;&gt;
make -C /lib/modules/`uname -r`/build M=`pwd`
&lt;/div&gt;
(Note the difference between back ticks ` and single quote &#039;)
&lt;!-- - - - - - - - - - - - - - - - - - --&gt;
&lt;h2&gt;Configuration and Installation&lt;/h2&gt;
The following instructions assumes the new wireless device is called &lt;i&gt;wlan0&lt;/i&gt;, if you are installing multiple devices, replace wlan0 with the device name you&#039;d prefer.
&lt;br&gt;&lt;br&gt;Load the driver with
&lt;div class=&#034;codeSample&#034;&gt;
cd /usr/src/acx-20051202
insmod acx.ko
&lt;/div&gt;
If this looks ok and &lt;i&gt;dmesg&lt;/i&gt; looks ok too, then the driver was successfully loaded into the kernel and the driver is ready to be installed under &lt;i&gt;/lib&lt;/i&gt;
&lt;div class=&#034;codeSample&#034;&gt;
cd /usr/src/acx-20051202
make -C /lib/modules/`uname -r`/build M=`pwd` modules_install
&lt;/div&gt;
All modules installed under &lt;i&gt;/lib/modules/...&lt;/i&gt; get loaded at startup. However if the module file (in our case acx.ko) is not executable it seems it is not getting loaded. The install script above copies the &lt;i&gt;acx.ko&lt;/i&gt; file to &lt;i&gt;/lib/modules/&amp;lt;kernel-version&amp;gt;/extra/acx.ko&lt;/i&gt; but without the proper execution bit. Therefore you must do
&lt;div class=&#034;codeSample&#034;&gt;
chmod 744 /lib/modules/`uname -r`/extra/acx.ko
&lt;/div&gt;
Next, edit &lt;i&gt;/etc/modprobe.conf&lt;/i&gt; and add the following line
&lt;div class=&#034;codeSample&#034;&gt;&lt;font color=&#034;green&#034;&gt;alias wlan0 acx&lt;/font&gt;&lt;/div&gt;
This will tell your system that there exists a wireless card with the acx.ko driver.
&lt;br&gt;&lt;br&gt;Next type
&lt;div class=&#034;codeSample&#034;&gt;
system-config-network&lt;/div&gt;
Click &lt;i&gt;New&lt;/i&gt; in the upper left corner and basically follow the GUI wizard, here are screen shots of the first few steps. After the final step the system is gonna try connect to your wireless network. Don&#039;t get discouraged if it doesn&#039;t work right away, just continue reading.
&lt;br&gt;&lt;br&gt;&lt;img src=&#034;http://waelchatila.com:80/images/wireless_neat.jpg&#034;&gt;
&lt;br&gt;&lt;img src=&#034;http://waelchatila.com:80/images/wireless_new.jpg&#034;&gt;
&lt;br&gt;&lt;img src=&#034;http://waelchatila.com:80/images/wireless_wlan0.jpg&#034;&gt;
&lt;br&gt;&lt;img src=&#034;http://waelchatila.com:80/images/wireless_name_pwd.jpg&#034;&gt;
&lt;br&gt;&lt;br&gt;
If the wizard fails to connect, try the following
&lt;div class=&#034;codeSample&#034;&gt;iwlist wlan0 scan&lt;/div&gt;
and compare the channel id with the one found in &lt;i&gt;/etc/sysconfig/network-scripts/ifcfg-wlan0&lt;/i&gt;
&lt;br&gt;&lt;br&gt;
Where I live, this is what &lt;i&gt;iwlist wlan0 scan&lt;/i&gt; returns
&lt;div class=&#034;codeSample&#034;&gt;
iwlist wlan0 scan
wlan0     Scan completed :
          Cell 01 - Address: 00:11:14:FA:2B:C3
                    ESSID:&#034;icegreen&#034;
                    Mode:Master
                    Frequency:2.437 GHz (Channel 6)
                    Quality=41/100  Signal level=18/100  Noise level=0/100
                    Encryption key:on
                    Bit Rate:54 Mb/s
&lt;/div&gt;
This is the &lt;i&gt;ifcfg-wlan0&lt;/i&gt; file I ended up with
&lt;div class=&#034;codeSample&#034;&gt;
IPV6INIT=no
ONBOOT=yes
USERCTL=yes
GATEWAY=
TYPE=Wireless
DEVICE=wlan0
HWADDR=00:51:75:12:d1:10
BOOTPROTO=dhcp
NETMASK=
DHCP_HOSTNAME=
IPADDR=
DOMAIN=
ESSID=icegreen
CHANNEL=6
MODE=Managed
&lt;/div&gt;

After editing your &lt;i&gt;ifcfg-wlan0&lt;/i&gt; file you don&#039;t have to restart your computer, just type 
&lt;div class=&#034;codeSample&#034;&gt;service network restart&lt;/div&gt; which gives better visual feedback over
&lt;div class=&#034;codeSample&#034;&gt;ifconfig wlan0 up&lt;/div&gt;

Note the &lt;i&gt;ONBOOT=yes&lt;/i&gt; which will enable your wireless each time you boot up your machine.

&lt;!-- - - - - - - - - - - - - - - - - - --&gt;
&lt;h2&gt;Other References&lt;/h2&gt;
&lt;a href=&#034;http://www.houseofcraig.net/acx100_howto.php&#034;&gt;
http://www.houseofcraig.net/acx100_howto.php&lt;/a&gt;


&lt;!-- - - - - - - - - - - - - - - - - - --&gt;
&lt;h2&gt;Did it Work?&lt;/h2&gt;
It would be nice to hear if my efforts in writing up my experiences with this card are helping others. Please feel free to post a comment or email me if it did.
        </description>
      
      
    
    
    
    <category>Unix/Linux</category>
    
    <category>Hardware</category>
    
    <comments>http://waelchatila.com:80/2006/01/16/1137404001340.html#comments</comments>
    <guid isPermaLink="true">http://waelchatila.com:80/2006/01/16/1137404001340.html</guid>
    <pubDate>Mon, 16 Jan 2006 09:33:21 GMT</pubDate>
  </item>
  
  <item>
    <title>Installing Tomcat with commons-daemon (jsvc)</title>
    <link>http://waelchatila.com:80/2005/12/13/1134504717808.html</link>
    
      
      
        <description>
          Most installation that I&#039;ve seen of Tomcat is made with tomcat running as root. This could potentially be a disasters security hole. Most Linux systems only allow the root to listen to port 80...which is why many users of tomcat under Linux run tomcat as root. With jscv, the process will start off as root but later on will change owner to a user of your choice.&lt;p&gt;&lt;a href=&#034;http://waelchatila.com:80/2005/12/13/1134504717808.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
          &lt;p&gt;&lt;a href="http://waelchatila.com:80/2005/12/13/1134504717808.html"&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
    
    
    <category>Unix/Linux</category>
    
    <category>Java</category>
    
    <category>Web</category>
    
    <comments>http://waelchatila.com:80/2005/12/13/1134504717808.html#comments</comments>
    <guid isPermaLink="true">http://waelchatila.com:80/2005/12/13/1134504717808.html</guid>
    <pubDate>Tue, 13 Dec 2005 20:11:57 GMT</pubDate>
  </item>
  
  </channel>
</rss>
