As my understand so far, there are many good candidates, they have their own blog, so i would use this chance to recruite them. I will search around blog Yahoo 360*, Blogger, Opera to find candidate, anyway, if you like this information, or know someone else, please drop me a message
This position is to work for CSC Vietnam, the most competitive, and attractive company in Vietnam
Leadership & Project Management
Wednesday, September 24, 2008
Tuesday, September 23, 2008
Travel: some interesting, useful pages/links
Using Tcl/Expect to automate your administration work, test telecom
After this post, i would like to add more about my project, the project's purpose is to provide ability to do remote commnand (on Windows, Linux, Unix, etc.) and file transfer.
This is a part of my research to do the project's purpose
plink (in putty package) to provide remote command ability
expect to provide ability to interact console application
Tcl/Expect commands:
I'm new to Tcl/Tk/Expect commands, syntax, so this is what i know so far
This is a part of my research to do the project's purpose
plink (in putty package) to provide remote command ability
expect to provide ability to interact console application
Tcl/Expect commands:
I'm new to Tcl/Tk/Expect commands, syntax, so this is what i know so far
Monday, September 22, 2008
Using sharpSSH (C#) to write/customize your own sshclient
or even winscp (open source), or putty (is it possible?)
I was trying to do many investigations on SSH protocol, or some tools/ways like JRE. The purpose to do a remote command-line, and file transfer on all platforms: Windows, Linux, Unix, etc.
1. The first approach is to implement JRE application, but we need to maintain it by the time
2. Try to implement again with C# (and Mono) stupid way
3. Try to implement sharpSSH
Actually, I knew many way/tools to do that, but by the time, i forgot. Now, i'm going back. And i was tried PUTTY command-line family, and it was so impressive
Beside doing: compatibility test, between SSH protocol version, we need to do some test for sheel specification stuff (windows shell, cmd.exe, command.exe, bash, csh shell, etc.) convention between Windows, Linux
plink, pscp, psftp, so great! to do file transfer and remote command-line
That i was told about "client-side"
And here is server-side, for Unix, we used OS-standard, default sshd packages. But on Windows we used openSSH package, or copssh, the reason is, sometime sharpSsh cannot work with openSSH but copssh
Process special character like "\", "/", """, "'", "\\"
We are thinking about Cygwin as Linux env. for another linux-like ssh server
I was trying to do many investigations on SSH protocol, or some tools/ways like JRE. The purpose to do a remote command-line, and file transfer on all platforms: Windows, Linux, Unix, etc.
1. The first approach is to implement JRE application, but we need to maintain it by the time
2. Try to implement again with C# (and Mono) stupid way
3. Try to implement sharpSSH
Actually, I knew many way/tools to do that, but by the time, i forgot. Now, i'm going back. And i was tried PUTTY command-line family, and it was so impressive
Beside doing: compatibility test, between SSH protocol version, we need to do some test for sheel specification stuff (windows shell, cmd.exe, command.exe, bash, csh shell, etc.) convention between Windows, Linux
plink, pscp, psftp, so great! to do file transfer and remote command-line
That i was told about "client-side"
And here is server-side, for Unix, we used OS-standard, default sshd packages. But on Windows we used openSSH package, or copssh, the reason is, sometime sharpSsh cannot work with openSSH but copssh
Process special character like "\", "/", """, "'", "\\"
We are thinking about Cygwin as Linux env. for another linux-like ssh server
XDMP (X-Window protocol) for remoting export GUI on Unix/Linux
If you want to launch (export) a Unix/Linux GUI program on Windows or other Unix/Linux OS
First of all, on the local Unix/Linux, we need to "export" an environment variable "DISPLAY" to your destination host and the port number, eg:
# export DISPLAY=172.16.49.86:0.0
Then of the remote OS (destination), where you want to host your GUI program, you need to install an XDMP Server (eg: xming, Xmanager)
This is basic idea, you can google more information, I will add detail later. Don't forget to turn off any virus scanner programs, firewall
First of all, on the local Unix/Linux, we need to "export" an environment variable "DISPLAY" to your destination host and the port number, eg:
# export DISPLAY=172.16.49.86:0.0
Then of the remote OS (destination), where you want to host your GUI program, you need to install an XDMP Server (eg: xming, Xmanager)
This is basic idea, you can google more information, I will add detail later. Don't forget to turn off any virus scanner programs, firewall
Automation Testing experience
if you want to build your own Automation Testing (Framework). Below is my experience:
- Don't ever fall into situation: test "automation testing tools". Yeap, it is absolutely, this is a loop forever. You build a tools to do the test, and you need to test your tools, does it make sense?
So, please use any available to adapt your requirement, save time, effort, and don't have to "test your test tools"
- Don't ever fall into situation: test "automation testing tools". Yeap, it is absolutely, this is a loop forever. You build a tools to do the test, and you need to test your tools, does it make sense?
So, please use any available to adapt your requirement, save time, effort, and don't have to "test your test tools"
Working directory in Solaris - /export/home
The reason I mention about this is some of us, usually put too much data into /root, but this folder is mounted for system working only. So if disk slices get full, your system couldn't do anything
And, by default, /export/home is the place for you to put any, as much data as you want, without any corruptions to system working directory
And, by default, /export/home is the place for you to put any, as much data as you want, without any corruptions to system working directory
Subscribe to:
Posts (Atom)