Wednesday, November 19, 2008
Monday, November 10, 2008
lameness day on hotnews.ro
It's "Lameness Day" on hotnews.ro ... probably the S&P ratings news depressed them so much they are unable to think and write.
It's Oscar Wilde day among my friends, it seems: most got lines from "Reading" on YM.
It's Oscar Wilde day among my friends, it seems: most got lines from "Reading" on YM.
Thursday, November 6, 2008
skype on debian lenny amd64
http://www.skype.com/go/getskype-linux-ubuntu-amd64
prerequisite:
apt-get install ia32-libs lib32asound2 libasound2-plugins ia32-libs lib32asound2 libasound2-plugins
prerequisite:
apt-get install ia32-libs lib32asound2 libasound2-plugins ia32-libs lib32asound2 libasound2-plugins
have eclipse, will travel ... on debian lenny amd64
Installed eclipse, but cannot install plugins:
An error occurred during provisioning.
Cannot connect to keystore.
Uninitialized keystore.
On my debian lenny for amd64, the problem was eclipse was using gcj instead of sun java.
check your available jvm:
sudo update-java-alternatives --list
I got:
emilper@main:~$ sudo update-java-alternatives --list
[sudo] password for emilper:
java-1.5.0-sun 53 /usr/lib/jvm/java-1.5.0-sun
java-6-openjdk 1061 /usr/lib/jvm/java-6-openjdk
java-6-sun 63 /usr/lib/jvm/java-6-sun
java-gcj 1042 /usr/lib/jvm/java-gcj
then set to your favorite, in my case the sun version:
sudo update-java-alternatives --set java-6-sun
After that all went fine.
An error occurred during provisioning.
Cannot connect to keystore.
Uninitialized keystore.
On my debian lenny for amd64, the problem was eclipse was using gcj instead of sun java.
check your available jvm:
sudo update-java-alternatives --list
I got:
emilper@main:~$ sudo update-java-alternatives --list
[sudo] password for emilper:
java-1.5.0-sun 53 /usr/lib/jvm/java-1.5.0-sun
java-6-openjdk 1061 /usr/lib/jvm/java-6-openjdk
java-6-sun 63 /usr/lib/jvm/java-6-sun
java-gcj 1042 /usr/lib/jvm/java-gcj
then set to your favorite, in my case the sun version:
sudo update-java-alternatives --set java-6-sun
After that all went fine.
Tuesday, November 4, 2008
backup your files from a remote computer using ssh and tar
step 0, mandatory: get a unix or GNU/Linux computer
step 1, optional:
ssh-keygen -t rsa
you might want to use a password, or not; it's more secure if you set a password for the key, but then you'll have to do some more configurations I won't get into here in order to avoid entering a password any time you use the connections secured by this key
Upload your public key on the computer you want to backup files from, and add it to the ~/.ssh/authorized_keys files; for example:
scp .ssh/id_rsa.pub yourname@example.com:/home/yourname/id_rsa.pub_from_home
then login to that computer, then
cat id_rsa.pub_from_home >> ~/.ssh/authorized_keys
at this stage you should be able enter "ssh example.com" and connect without having to add any password
step 2. now you can add cron jobs to make backups of your home directory on the remote host.
this is the command line you need:
ssh -l yourname example.com "tar cjvf - /home/yourname " > ~/backups/example.com_home_dir_`date +'%Y_%m_%d_%H_%M_%S'`.tar.bz2
This will result in the contents of your home directory on the remote host being archived and the resulting tar-ed and bzip2-ed file being deposited in the ~/backups/ directory on your local machine. The resulting archive filename will look like: example.com_home_dir_2008_11_04_22_13_45.tar.bz2
If you prefer gzip instead of bzip2 for compression (though I don't see a reason you would):
ssh -l yourname example.com "tar czvf - /home/yourname " > ~/backups/example.com_home_dir_`date +'%Y_%m_%d_%H_%M_%S'`.tar.gz
step 3. add this to cron (using crontab -e) , to run once a week, on Sunday at 4:30 AM
30 4 * * 7 /usr/bin/ssh -l yourname example.com "tar cjvf - /home/yourname " > /home/yourlocaluser/backups/example.com_home_dir_`date +'%Y_%m_%d_%H_%M_%S'`.tar.bz2
step 4, optional: buy a bigger hard drive, and set the script to run every two hours every day of the week:
1 0-23/2 * * * /usr/bin/ssh -l yourname example.com "tar cjvf - /home/yourname " > /home/localuser/backups/example.com_home_dir_`date +'%Y_%m_%d_%H_%M_%S'`.tar.bz2
or, more useful, make backups of your mysql databases from the remote host once a day at 2:25 AM:
25 2 * * * /usr/bin/ssh -l remoteuser example.com "mysqldump -u root -pyour_mysql_root_password --opt --all-databases| bzip2 " > /home/localuser/backups/example.com_complete_mysql_dump_`date +'%Y_%m_%d_%H_%M_%S'`.sql.bz2
step 1, optional:
ssh-keygen -t rsa
you might want to use a password, or not; it's more secure if you set a password for the key, but then you'll have to do some more configurations I won't get into here in order to avoid entering a password any time you use the connections secured by this key
Upload your public key on the computer you want to backup files from, and add it to the ~/.ssh/authorized_keys files; for example:
scp .ssh/id_rsa.pub yourname@example.com:/home/yourname/id_rsa.pub_from_home
then login to that computer, then
cat id_rsa.pub_from_home >> ~/.ssh/authorized_keys
at this stage you should be able enter "ssh example.com" and connect without having to add any password
step 2. now you can add cron jobs to make backups of your home directory on the remote host.
this is the command line you need:
ssh -l yourname example.com "tar cjvf - /home/yourname " > ~/backups/example.com_home_dir_`date +'%Y_%m_%d_%H_%M_%S'`.tar.bz2
This will result in the contents of your home directory on the remote host being archived and the resulting tar-ed and bzip2-ed file being deposited in the ~/backups/ directory on your local machine. The resulting archive filename will look like: example.com_home_dir_2008_11_04_22_13_45.tar.bz2
If you prefer gzip instead of bzip2 for compression (though I don't see a reason you would):
ssh -l yourname example.com "tar czvf - /home/yourname " > ~/backups/example.com_home_dir_`date +'%Y_%m_%d_%H_%M_%S'`.tar.gz
step 3. add this to cron (using crontab -e) , to run once a week, on Sunday at 4:30 AM
30 4 * * 7 /usr/bin/ssh -l yourname example.com "tar cjvf - /home/yourname " > /home/yourlocaluser/backups/example.com_home_dir_`date +'%Y_%m_%d_%H_%M_%S'`.tar.bz2
step 4, optional: buy a bigger hard drive, and set the script to run every two hours every day of the week:
1 0-23/2 * * * /usr/bin/ssh -l yourname example.com "tar cjvf - /home/yourname " > /home/localuser/backups/example.com_home_dir_`date +'%Y_%m_%d_%H_%M_%S'`.tar.bz2
or, more useful, make backups of your mysql databases from the remote host once a day at 2:25 AM:
25 2 * * * /usr/bin/ssh -l remoteuser example.com "mysqldump -u root -pyour_mysql_root_password --opt --all-databases| bzip2 " > /home/localuser/backups/example.com_complete_mysql_dump_`date +'%Y_%m_%d_%H_%M_%S'`.sql.bz2
Tuesday, October 14, 2008
Subscribe to:
Posts (Atom)
