These are my first three steps to create a Ubuntu instance in Amazon EC2.
1) Ubuntu Official AMI's are published by user with Amazon ID '099720109477'.
after the instance get launched you can access the instance with the public DNS and the AWS pem file.
2) ssh -i awskey.pem ubuntu@ec2-01-02-03-04.compute-1.amazonaws.com
To facilitate ssh, i prefer to send my own key to the instance with ssh-copy-id. Here is the link to create your own key pair.
3)cat id_rsa.pub | ssh -i testkey.pem ubuntu@ec2-01-02-03-04.compute-1.amazonaws.com "cat>> .ssh/authorized_keys"
At this point my instance is ready, and easily accessible with my own rsa credentials.
Saturday, June 18, 2011
Saturday, February 20, 2010
These are the instructions to compile transmission in a sheevaplug. From elBradford. http://bradford.law-family.org/success-building-transmission-1-80-from-source-on-sheevaplug/ This link was down on February 20, 2010. I get access to it from google cache.
1) I think the last 3 package are not really required, for a non gtk installation
2) Download the latest transmission from:
http://download.m0k.org/transmission/files/
# wget "and the actual link to the latest file"
3) Extract the files
# tar –xvf transmission-1.90.tar.bz2
4) Enter in directory and:
# ./configure –-disable-gtk --disable-cli
5) First Backup your current settings.json and purge current installed torrent.
# aptitude purge transmission-daemon
5) Build
# make
# make install
6) Setup init scrip as per this link.
7) edit init script transmission-home to point /etc/transmission instead of default /root/.conf/transmission
Create transmission user: adduser Make sure transmission user has access is the owner of the directory.
8) Configure /etc/transmission/settings.json
9) start transmission
# /etc/init.d/transmission-daemon start
10) Add rc links
#update-rc.d transmission-daemon defaults
1) I think the last 3 package are not really required, for a non gtk installation
* now libevent-dev is required, a had to download it and compile it.# apt-get install build-essential automake autoconf libtool pkg-config
libcurl4-openssl-dev intltool libxml2-dev libgtk2.0-dev libnotify-dev libglib2.0-dev
2) Download the latest transmission from:
http://download.m0k.org/transmission/files/
# wget "and the actual link to the latest file"
3) Extract the files
# tar –xvf transmission-1.90.tar.bz2
4) Enter in directory and:
# ./configure –-disable-gtk --disable-cli
5) First Backup your current settings.json and purge current installed torrent.
# aptitude purge transmission-daemon
5) Build
# make
# make install
6) Setup init scrip as per this link.
7) edit init script transmission-home to point /etc/transmission instead of default /root/.conf/transmission
Create transmission user: adduser Make sure transmission user has access is the owner of the directory.
8) Configure /etc/transmission/settings.json
9) start transmission
# /etc/init.d/transmission-daemon start
10) Add rc links
#update-rc.d transmission-daemon defaults
Sunday, February 05, 2006
Ubuntu mount and read permits in a NTFS partition
Problema.
No puedo "mount" ni ver los files en una particion NTFS como USER solo los puedo montar y accesar como root. No me interesa el escribir la particion esto puede afectar la particion. La solucion esta en la opcion de umask en el file fstab, users y ro "read only".
Users permite que cualquier usuario pueda "mount" la particion.
ro modo de solo lectura
umask=0222 permite que todos los user puedan leer el contenido de la particion.
/dev/hdb1 /media/win ntfs users,ro,umask=0222 0 0
No puedo "mount" ni ver los files en una particion NTFS como USER solo los puedo montar y accesar como root. No me interesa el escribir la particion esto puede afectar la particion. La solucion esta en la opcion de umask en el file fstab, users y ro "read only".
Users permite que cualquier usuario pueda "mount" la particion.
ro modo de solo lectura
umask=0222 permite que todos los user puedan leer el contenido de la particion.
/dev/hdb1 /media/win ntfs users,ro,umask=0222 0 0
Booting W2k from a slave HD using GRUB
Problema,
W2K se reusa a bootiar de un disco esclavo "slave".
Para lograr que windows arranque hay que hacer un pequeño engaño a windows desde grub.
map (hd0) (hd1) logra que windows vea el disco master como slave
map (hd1) (hd0) y el slave como master
/boot/grub/menu.lst
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title Microsoft Windows 2000 Professional
map (hd0) (hd1)
map (hd1) (hd0)
root (hd1,0)
savedefault
makeactive
chainloader +1
W2K se reusa a bootiar de un disco esclavo "slave".
Para lograr que windows arranque hay que hacer un pequeño engaño a windows desde grub.
map (hd0) (hd1) logra que windows vea el disco master como slave
map (hd1) (hd0) y el slave como master
/boot/grub/menu.lst
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title Microsoft Windows 2000 Professional
map (hd0) (hd1)
map (hd1) (hd0)
root (hd1,0)
savedefault
makeactive
chainloader +1
Wheelmouse in Knoppix
Luego de installar Knoppix en el hard drive el wheel mouse dejo de funcionar. Como siempre una busqueda en google mostro la solucion. Es necesario el seleccionar el protocolo imps/2,device /dev/psaux y "ZAxisMapping" "4 5".
/etc/X11/XF86config-4
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "imps/2"
Option "Device" "/dev/psaux"
Option "ZAxisMapping" "4 5"
/etc/X11/XF86config-4
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "imps/2"
Option "Device" "/dev/psaux"
Option "ZAxisMapping" "4 5"
Subscribe to:
Posts (Atom)