[linux notes]

SSH without password

ssh-keygen -t rsa
cat .ssh/id_rsa.pub | ssh user@server ‘cat >> .ssh/authorized_keys’
enter password: ****

Running LaTeX in GUI




Remote connect with linux/unix system in windows platform

I used to use putty to connect to my office computer and the supercomputer. It is very convenient if you just type in comand lines. But when it comes to graphic connection it’s a pain… Using Xming is fine but not very friendly and sometimes has problems. BTW you need to have admin privileges to launch Xserver.

However today I encountered this problem when I was using library computer trying to launch Xming.

I find a better tool when you have to open and edit some code files without admin rights: MobaXterm.




Just ran some tests. I found it’s not very stable when using xserver… Most likely you will end up with failures in saving modified files ( I guess it uses some protocol similar to sftp to transfer our modified temporary file to the remote system… )

Nothing can be perfect=( Maybe time to go back to my simple putty.

Install Scilab in 64-bit Centos6

As I am using Unix cluster which has a Centos6 OS without matlab application, I am looking for some alternatives. Because I was always bothering transferring all my raw data to my own linux system which owns matlab to do post-processing– that’s way off convenience! I got crazy everytime I did this: do scp, type in passwd, login my own system again. I setup an authorized key to skip passwd steps–this may save some time however still hasn’t solve the problem.

Scilab, at first glance, not as famous as matlab, is a not bad alternative as long as you don’t own a matlab license  but want almost everything with matlab language or mat-files. And it’s free and open source and easy to install. So why not?!

I installed it in my own 64-bit ubuntu14.04 as well as the 64-bits Centos6 – Unix. However I believe it is the same with 32-bit.

At first I tried the lastest version (5.5.0). However it never works, reporting “GLIBC_2.14 not found”. I googled but seemed that the best way to solve this problem is to recompile the scilab — unless I understand how to perform it. The alternative is to upgrade GLIBC to the higher version(>2.4) but this may induce some unforeseen harm to other applications that depend on GLIBC… I am rather new to Linux/Unix OS, so the first thing is to explore this new realm without causing deadly damage-at least not do it on clusters… (I’ll take some adventures in my own computer but urgently I want to install Scilab safely)

Well the simplest way is always quite simple. 64-bit system is always not a thorny dude to deal with but you can just try another version(perhaps older version) to test the compatibility with it. And of course I did and good thing is I succeeded!

The only older version Scilab provided so far is 5.4.1 .

The next steps just following the simple two-step installation provided by Scilab official site.

Launch it by simply

cd <scilab-path>  

#enter the directory you unzip your file


choose whether you would run it in non-graphics mode or not by chooting scilab or scilab-cli (there are other options please refer to the README file in its main directory)

And its done!




anyway I have to say learning a new language is not easy. Even if it is similar to what you have known. Especially when Scilab is not so popular and it’s hard to find any answer to your problem through community forum posts. Sigh~