http://java.sun.com/javase/downloads/5u22/jdk

then

wget –limit-rate=24k -e http_proxy=10.151.38.xxx:1234 -np -nc -t 0 -w 1.5 -e robots=off -rbc -i target.txt

:g/branches/d

:%s/.\//http:\/\/svn.wp-plugins.org\//g

for i in `ls`; do if [ -d $i ]; then  touch $i/index.html; fi; done

chika@earth:~/try$ echo $path
Make It Happen/
chika@earth:~/try$ echo $path | tr -d ‘ ‘
MakeItHappen/
chika@earth:~/try$

imk
ai
metnum
rpl
rankaian digital
robotika

http://webchat.freenode.net

http://www.mibbit.com

$ ffmpeg -i lilin.kecil.flv -vn lilin.kecil.ogg

yes it works

Go forth and multiply

Documenting a Debian Linux system in order to reproduce it

Use cases

System Documentation

Every system administrator knows its a good idea to keep documentation about the servers he’s maintaining : you need it to prepare migrations, in recovery scenarios, to plan software roll-out or modifications to a configuration, or to look up configuration details when troubleshooting. Because most of this information is present in the system itself, you can find it there, but that doesn’t help if the server you need to know about has just crashed and you’re trying to rebuild an other one to replace it. Better collect that information in advance.

Most system administrators find this boring. So they put it off, and then forget to do it. Or they start with some documentation, then forget to keep it up to date, so the documentation of the system doesn’t reflect the actual configuration of the system (and when the time comes that you need to reproduce that tweaked daemon config, you don’t remember that final detail that makes it all work).

So, let’s see if we can document a server automatically, and keep the documentation up to date as well. Read the rest of this entry »