HAND-HELD ELECTRONIC ENCLOSURE GAINTA

GAINTA, a privately owned Taiwan company, is one of the largest enclosure manufacturers in Asia, and is the market leader in thermoplastic enclosures used for protecting electrical and electronic components operating in hostile environments. GAINTA enclosures are manufactured in modern factories located in Taiwan

Whatever your application, the GAINTA enclosure family features the widest range of high quality enclosures for the packaging and protection of electrical and electronic components and systems. Enclosures can be delivered in standard off the shelf configurations or customized to your exact specifications. .

Continuous Product Development
The GAINTA enclosure range features over 700 different standard enclosures made of polycarbonate, ABS, fiberglass and aluminium. GAINTA is the industry leader in developing both new products and new technologies for molding thermoplastic enclosures. At GAINTA, we consider molding technology an essential part of product development.

But more important than technical leadership, is the GAINTA commitment to understanding the needs of its customers. All our products are designed in close cooperation with our customers. We use input from our global customer base to produce new enclosure ranges, useful accessories and on-going product improvements and enhancements.

Please click here to see enclosure.

Our local dealers will delivered in banglore.

Warning: Remote Host Identification Has Changed error and solution

When I run ssh command I get an error which read as follows:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
5c:9b:16:56:a6:cd:11:10:3a:cd:1b:a2:91:cd:e5:1c.
Please contact your system administrator.
Add correct host key in /home/user/.ssh/known_hosts to get rid of this message.
Offending key in /home/user/.ssh/known_hosts:1
RSA host key for ras.mydomain.com has changed and you have requested strict checking.
Host key verification failed.

How do I get rid of this message?

If you have reinstalled Linux or UNIX with OpenSSH, you will get the above error. To get rid of this problem:

Solution #1: Remove keys

Use the -R option to removes all keys belonging to hostname from a known_hosts file. This option is useful to delete hashed hosts. If your remote hostname is server.example.com, enter:
$ ssh-keygen -R {server.name.com}
$ ssh-keygen -R {ssh.server.ip.address}
$ ssh-keygen -R server.example.com
Sample output:

/home/vivek/.ssh/known_hosts updated.
Original contents retained as /home/vivek/.ssh/known_hosts.old

Now, you can connect to the host without a problem.

Solution #2: Add correct host key in /home/user/.ssh/known_hosts

It is not necessary to delete the entire known_hosts file, just the offending line in that file. For example if you have 3 server as follows.
myserver1.com,64.2.5.111 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEA11FV0EnGahT2EK8qElocjuHTsu1jaCfxkyIgBTlxlrOIRchb2pw8IzJLOs2bcuYYfa8nSXGEcWyaFD1ifUjfHelj94AAAAB3NzaC1yc2EAAAABIwAAAIEA11FV0E
nGahT2EK8qElocjuHTsu1jaCfxkyIgBTlxlrOIRchb2pw8IzJLOs2bcuYYfa8nSXGEcWyaFD1ifUjfHelj94H+uv304/ZDz6xZb9ZWsdm+264qReImZzruAKxnwTo4dcHkgKXKHeefnBKyEvvp/2ExMV9WT5DVe1viVwk=
myserver2.com,125.1.12.5 ssh-rsa
AAAAB3NzaC1yc2EAAAABIwAAAQEAtDiERucsZzJGx/1kUNIOYhJbczbZHN2Z1gCnTjvO/0mO2R6KiQUP4hOdLppIUc9GNvlp1kGc3w7B9tREH6kghXFiBjrIn6VzUO4uwrnsMbnAnscD5EktgI7fG4ZcNUP 5+J7sa3o+rtmOuiFxCA690DXUJ8nX8yDHaJfzMUTKTGxQz4M/H2P8L2R//qLj5s3ofzNmgSM9lSEhZL/IyI4NxHhhpltYZKW/Qz4M/H2P8L2R//qLj5s3ofzNmgSM9lSEhZL/M7L0vKeTObue1SgAsXADtK3162a/Z6MGnAazIviHBldxtGrFwvEnk82+GznkO3IBZt5vOK2heBnqQBfw=
myserver3.com,125.2.1.15 ssh-rsa
5+J7sa3o+rtmOuiFxCA690DXUJ8nX8yDHaJfzMUTKTGx0lVkphVsvYD5hJzm0eKHv+oUXRT9v+QMIL+um/IyI4NxHhhpltYZKW
as3533dka//sd33433////44632Z6MGnAazIviHBldxtGrFwvEnk82/Qz4M/H2P8L2R//qLj5s3ofzNmgSM9lSEhZL/M7L0vKeTObue1SgAsXADtK3162a/Z6MGnAazIviHBldxtGrFwvEnk82+GznkO3IBZt5vOK2heBnqQBfw==

To delete 2nd server (myserver.com), open file:
# vi +2 .ssh/known_hosts
And hit dd command to delete line. Save and close the file. Or use following
$ vi ~/.ssh/known_hosts
Now go to line # 2, type the following command
:2
Now delete line with dd and exit:
dd
:wq


Solution 3: Just delete the known_hosts file If you have only used one ssh server

$ cd
$ rm .ssh/known_hosts
$ ssh ras.mydomain.com


Now you should be able to connect your server via ssh.

AT91RM9200 Documents

Please check the below link. you will get all details.
http://opencircuits.com/Linuxstamp#Description

Linux driver source code

Below web site will help you to get source file.
http://www.mjmwired.net/kernel/Documentation/rtc.txt

Circuit and PCB

The Below website will help you to get PCB and circuit diagram.
http://www.microbuilder.eu

GNOME2 IP Messenger

A few things about GNOME2 IP Messenger (g2ipmsg), though.

Make sure you have all dependencies installed:

• libxml-parser-perl


• libgnomeui-dev


• libpanel-applet2-dev

(UPDATE 2008-07-06 2:35AM -- additional dependencies)

• gettext


• intltool

How to install these depends on the Linux distribution. The easiest way is to use the graphical Package Manager.

(MAJOR UPDATE 2008-07-07 5:27PM)
Randell reported that he couldn't find the dependencies in Fedora -- I was surprised! I did a search and found out that libxml-parser-perl was perl-XML-parser in Fedora! I suppose that the rest of the dependencies are only for Debian-based distros. Randell said that he'd look up the rest, and post a Fedora instructional soon. With that, I'm slapping the apt-get command back into the list below.

After assuring that you have the above dependencies, you can do a conventional build and install from source. Assuming that the current working directory is where g2ipmsg-0.9.5.tar.gz is located:

 $ tar zxf g2ipmsg-0.9.5.tar.gz
 $ cd g2ipmsg-0.9.5/
 $ sudo apt-get install libxml-parser-perl libgnomeui-dev libpanel-applet2-dev gettext intltool
 $ ./configure
 $ make
 $ sudo make install
 $ sudo g2ipmsg

Make sure to execute sudo g2ipmsg right after installation. You'll only be able to run it without the sudo after a reboot -- I don't know why, though.

I suddenly posted something like this because while researching specifically about this, the search results with definite instructions were non-English sites.

Cross Compile SSH Server Dropbear For ARM

Requirements:

• ubuntu 8.04
• gcc 4.2.3
• arm_v5t_le-gcc 3.4.3

Source:

• [http://www.zlib.net/ Zlib]
• [http://www.ucc.asn.au/~matt/dropbear/dropbear.html Dropbear]

Install Zlib:

• wget http://www.zlib.net/zlib-1.2.3.tar.gz

• tar zxvf zlib-1.2.3.tar.gz

• mkdir zlib

• cd zlib-1.2.3/

• CC=arm_v5t_le-gcc ./configure --prefix=/home/border/work/SMG/build-tools/zlib

• make

• make install

Install Dropbear:

• wget http://matt.ucc.asn.au/dropbear/releases/dropbear-0.51.tar.gz

• tar zxvf dropbear-0.51.tar.gz

• mkdir dropbear-build

• cd dropbear-build/

• mkdir build

• ../dropbear-0.51/configure --prefix=/home/border/work/SMG/build-tools/dropbear-build/build/ \
     --with-zlib=/home/border/work/SMG/build-tools/zlib/ CC=arm_v5t_le-gcc --host=arm

• make

• make scp

• sudo make install

• sudo cp scp build/bin/

border@b0rder:~/work/SMG/build-tools/dropbear-build/build$ tree
.
|-- bin
|   |-- dbclient
|   |-- dropbearconvert
|   |-- dropbearkey
|   `-- scp
`-- sbin
    `-- dropbear

Server Key:

• cd /etc

• mkdir dropbear

• cd dropbear

• dropbearkey -t rsa -f dropbear_rsa_host_key

• dropbearkey -t dss -f dropbear_dss_host_key