IPNLINUX COMMUNITY VERSION 2

Install Mono 2.4 on Ubuntu

Ubuntu ships with Mono pre-installed, but due to the rapid release cycles on the Mono project, the version that ships with Ubuntu is

often outdated by the time the Ubuntu release ships. Due to the impressive release schedule of Mono, you do really need to keep up

with the new releases as every new release dramatically improves the entire framework.

Unfortunately for Ubuntu users, there are no dedicated Ubuntu packages for download from the Mono Project web site, which means that

you best bet is be to compile the project yourself. While I know that most Linux newbies find that concept intimidating, it actually

isn't nearly as hard as it sounds.

To that end, I'll walk you through compiling and installing the latest release of Mono (version 2.4 at time of writing) on Ubuntu.

Note that these instructions should also work on newer versions of Mono.

These instructions were created by installing Mono 2.4 on an absolutely fresh installation of Ubuntu. For those Windows users wishing

to try this out at home, I would suggest installing Ubuntu on a Virtual PC 2007 virtual machine. Arcanecode has an excellent post on

getting this to work first time.

IMPORTANT: If you're installing on a VPS, make sure that you have at least 400 MB of RAM available, or otherwise the mono compilation

process will fail.

WARNING

Following these instructions will result in all your pre-installed Mono applications being removed from your Ubuntu box. In most cases

the only way to get them back is going to be by installing them from source too (not always a bad idea).

If you'd like to play with Mono 2.4, but keep things like F-Spot and Beagle, I would suggest rather using the instructions

provided by Jan Dzik.

Update: I now have a script that automates the install, see this post: Mono Compile & Install Script

Installing Mono

Open a terminal window if you're using the Ubuntu GUI or log on using SSH if you're accessing a remote server.

All these instructions assume that you have root privileges, so if you're not logged in as root, enter the following and

enter you password when prompted.

$ sudo bash

First you need to remove the version of Mono that is pre-installed with Ubuntu.

$ apt-get remove mono-common

That will remove all the extra packages that are installed with mono as they all depend on it. Be aware that it will also remove

applications like f-spot and beagle, which will have to be re-installed after the mono upgrade if you wish to use them.

Next, create a folder for the source code you're about to compile:

$ mkdir /src

Then change to the src directory:

$ cd /src

Make sure that your /etc/apt/sources.list file has the universe and multiverse repositories included. If you installation didn't

have any internet connectivity, there may be a chance that the installer disabled those repositories due to being unable to verify

them. If that is the case, do the following:

$ nano /etc/apt/sources.list

Remove the # characters from the universe and multiverse entries and save the file (a Nano Basics Guide is available for people new

to nano). I personally just enable everything.

Refresh the apt-get database.

$ apt-get update

You now need to install some Mono build dependencies (and some optional enhancements):

$ apt-get install build-essential pkg-config libglib2.0-dev bison libcairo2-dev libungif4-dev libjpeg62-dev libtiff4-dev gettext

Download libgdiplus:

$ wget http://ftp.novell.com/pub/mono/sources/libgdiplus/libgdiplus-2.4.tar.bz2

$ tar -xvf libgdiplus-2.4.tar.bz2

$ cd libgdiplus-2.4/

Now we can compile libgdiplus and install it:

$ ./configure --prefix=/usr/local; make; make install

Now go make yourself a snack, especially if you're doing this on a VM

After the compilation finally finishes, we need to make sure the new packages are visible to the system:

$ sh -c “echo /usr/local/lib >> /etc/ld.so.conf”

$ /sbin/ldconfig

Now change back to the /src folder and download the latest release of mono (about 17 MB):

$ cd /src

$ wget http://ftp.novell.com/pub/mono/sources/mono/mono-2.4.tar.bz2

Extract the compressed file, change into the mono folder and compile:

$ tar -xvf mono-2.4.tar.bz2

$ cd mono-2.4

$ ./configure --prefix=/usr/local; make; make install

You can go make yourself a gourmet meal at this point as the compilation process takes a seriously long time (ok, maybe not that

long, but us generation X/Y types don't really have the patience for C++ compilation).

Add mono to the bash path:

$ nano ~/.bashrc

And add the following lines at the end:

PATH=/usr/local/bin:$PATH

LD_LIBRARY_PATH=/usr/local/lib/:$LD_LIBRARY_PATH

PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH

In order for the changes to take effect, you need to either close and open your terminal again, or simply type:

$ bash

to start a new instance of bash command line.

To check your new mono version, type:

$ mono -V

You should see the following:

Mono JIT compiler version 2.4 (tarball Wed Apr 1 04:49:16 CDT 2009)

Copyright (C) 2002-2008 Novell, Inc and Contributors. www.mono-project.com

TLS: __thread

GC: Included Boehm (with typed GC)

SIGSEGV: altstack

Notifications: epoll

Architecture: amd64

Disabled: none

Congratulations, you have a working copy of the latest Mono released installed on your Ubuntu machine!

Installing XSP

XSP is the Mono web server that Apache delegates to (via mod_mono) when serving ASP.NET pages on Linux. In order

to run ASP.NET pages

you will need to compile and build the XSP web server.

Change to your /src directory, download the XSP sources, unzip them and compile:

$ cd /src

$ wget http://ftp.novell.com/pub/mono/sources/xsp/xsp-2.4.tar.bz2

$ tar -xvf xsp-2.4.tar.bz2

$ cd xsp-2.4/

$ ./configure --prefix=/usr/local; make; make install

Once the compilation is done, we can test the XSP server. Change to the XSP test installation folder and run the XSP server:

$ cd /usr/local/lib/xsp/test

$ xsp2

You should see something like the following:

xsp2

Listening on address: 0.0.0.0

Root directory: /root

Listening on port: 8080 (non-secure)

Hit Return to stop the server.

Open your browser and point it to http://localhost:8080 (or your domain/ip if you're doing this remotely). You should see the XSP test page.

Installing Mod_Mono

Mod_mono is the name of the apache2 module that links the XSP server and apache. This allows for apache to handle all incoming

requests and hand them off to the XSP process in order to server your ASP.NET pages. You only need to install Mod_mono if you

plan on using Apache2 to serve web pages. You will also need to have apache2 (and it's development files) pre-installed to

compile mod_mono.

Install apache2 and the necessary build dependencies:

$ apt-get install apache2 apache2-threaded-dev

Once that's done, we can compile mod_mono.

Change to our source directory, download the mod_mono sources, unzip them and compile:

$ cd /src

$ wget http://ftp.novell.com/pub/mono/sources/mod_mono/mod_mono-2.4.tar.bz2

$ tar -xvf mod_mono-2.4.tar.bz2

$ cd mod_mono-2.4/

$ ./configure --prefix=/usr/local; make; make install

We need to include the mod_mono.conf file in the apache2 configuration file, so open the apache2.conf file in a text editor:

$ nano /etc/apache2/apache2.conf

Scroll to the bottom of the file and include the following line:

Include /etc/apache2/mod_mono.conf

Now lets copy the test content from XSP to our apache2 public folder to we can have an ASP.NET application with which to test the

mod_mono installation:

$ cp -r /usr/local/lib/xsp/test /var/www/test

When you compile Mod_mono from source, the necessary apache2 configuration files are not created for you, so we will have to do them manually.

Firstly, create the mod_mono.load file with a text editor:

$ nano /etc/apache2/mods-available/mod_mono.load

Add the following line to the file:

LoadModule mono_module /usr/lib/apache2/modules/mod_mono.so

Next we create the mod_mono.conf file:

$ nano /etc/apache2/mods-available/mod_mono.conf

Add the following to the file:

AddType application/x-asp-net .aspx .ashx .asmx .ascx .asax .config .ascx

DirectoryIndex index.aspx

include /usr/local/lib/mono/2.0/mono-server2-hosts.conf

Next, create the mono-server2-hosts.conf file:

$ nano /usr/local/lib/mono/2.0/mono-server2-hosts.conf

And add the following:

<IfModule mod_mono.c>

MonoUnixSocket /tmp/.mod_mono_server2

MonoServerPath /usr/local/lib/mono/2.0/mod-mono-server2.exe

AddType application/x-asp-net .aspx .ashx .asmx .ascx .asax .config .ascx

MonoApplicationsConfigDir /usr/local/lib/mono/2.0

MonoPath /usr/local/lib/mono/2.0:/usr/local/lib

</IfModule>

Configure Apache2 Virtual Hosts

The virtual hosts configuration really requires a tutorial on its own, but for now I'll just show you how to make the test application

the default site on your apache2 server.

Edit the default virtual host file for apache2:

$ nano /etc/apache2/sites-enabled/000-default

Replace the contents of the file with the following (you may want to backup the file first):

<VirtualHost *>

ServerName www.local.com

ServerAdmin webmaster@localhost

DocumentRoot /var/www/test

DirectoryIndex index.html index.aspx

MonoDocumentRootDir “/var/www/test”

MonoServerPath rootsite “/usr/local/bin/mod-mono-server2”

MonoApplications rootsite “/:/var/www/test”

<Directory /var/www/test>

MonoSetServerAlias rootsite

SetHandler mono

AddHandler mod_mono .aspx .ascx .asax .ashx .config .cs .asmx

</Directory>

</VirtualHost>

Now restart apache2:

$ /etc/init.d/apache2 restart

Now open your browser and navigate to http://localhost/. You should see the XSP test web app appear.

Restart Errors

When you restart apache2 using the command above, you are likely to see an error message similar to the following:

• Restarting web server apache2

[Fri Nov 06 00:41:41 2009] [crit] (13)Permission denied: Failed to attach to existing dashboard, and removing dashboard

file '/tmp/mod_mono_dashboard_XXGLOBAL_1' failed (Operation not permitted). Further action impossible.

This is quite normal and will not affect the operation of your Mono websites.

References:

• https://help.ubuntu.com/community/MonoFromSource
• http://docs.codehaus.org/display/BOO/Boo+on+Ubuntu
• http://go-mono.com/sources-stable/
• http://www.mono-project.com/Compiling_Mono
• http://www.mono-project.com/Mod_mono
• http://ubuntuforums.org/archive/index.php/t-288029.html

Calificaciones semestre agosto -diciembre 2009

Creación de la PC

By tognu.

INSTALL CUDA 2.3 ON UBUNTU 9.10

BY TOGNU

1. Open a terminal and paste the following commands to add the Launchpad repository:

-Ubuntu Karmic Koala

sudo add-apt-repository ppa:nvidia-vdpau/ppa

-Ubuntu Jaunty Jackalope, Intrepid Ibex, Hardy Heron:

sudo sh -c “echo 'deb http://ppa.launchpad.net/nvidia-vdpau/ppa/ubuntu UBUNTU_VERSION main' >> /etc/apt/sources.list”
 
sudo sh -c “echo 'deb-src http://ppa.launchpad.net/nvidia-vdpau/ppa/ubuntu UBUNTU_VERSION main' >> /etc/apt/sources.list”

In the two lines above, replace UBUNTU_VERSION with your Ubuntu version (in lowercase: jaunty, intrepid or hardy).

2. Import the GPG key (skip this for Karmic Koala if you used the add-apt-repository command):

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys CEC06767

3. Now you can install the Nvidia 190.xx stable drivers:

sudo apt-get update && sudo apt-get install nvidia-190-modaliases nvidia-glx-190

or 185.xx:

sudo apt-get update && sudo apt-get install nvidia-185-modaliases nvidia-glx-185

Install the drive using envyng

Code:

sudo apt-get install envyng-core;
 
envyng -t

use the option 1 Install the Nvidia driver,now the option 0 and restart you computer.

The new driver its showed

well, now open a terminal and put in

Code:

sudo apt-get install build-essential libglut3-devsudo
 
sudo apt-get install mesa-common-dev freeglut3-dev glutg3-dev libglut3
 
 

Furthermore we also need to get 3 more packages namely

sudo apt-get install libxmu-dev

sudo apt-get install libxmu-headers

sudo apt-get install libxi-dev

These can be installed with sudo apt-get in a terminal or by finding them in synaptic.

With these downloaded and installed we can continue and install the Nvidia driver. Note that this is on a fresh install and there are more steps to be taken if you are doing it with an older Nvidia driver already installed. There are already posts on the forum about that so I wont go into that here.

Next we need to install the toolkit. To do this we open a terminal and type in

Code:

chmod +x ./cudatoolkit_2.3_linux_64_ubuntu9.04.run
 
sudo ./cudatoolkit_2.3_linux_64_ubuntu9.04.run

You get to pick your install directory, here I will assume its in the default.

The next step is to add the necessary environment variables. In a terminal type in this. (Just type or copy it in one line at a time!)

Code:

echo "# CUDA stuff
 
PATH=\$PATH:/usr/local/cuda/bin
 
LD_LIBRARY_PATH=\$LD_LIBRARY_PATH:/usr/local/cuda/lib64
 
export PATH
 
export LD_LIBRARY_PATH" >> ~/.bashrc

Like the toolkit installer says, if you run a 32 bit version you must leave out the 64 part.

Next we install the SDK. In a terminal type in the following.

Code:

chmod +x ./cudasdk_2.3_linux.run
 
./cudasdk_2.3_linux.run

You dont need to be a superuser to install this.

First you get asked where you want to put the files, and where the CUDA toolkit was installed. (Check that this dir is the same as the one you installed it in, even if it says it located it. The dir need to be the same and not have additions of nvcc or the like!)

Last we need to compile the SDK files. In a terminal type (I assume default install dir)

Code:

sudo apt-get install gcc-4.1 g++-4.1

sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.1 60 --slave /usr/bin/g++ g++ /usr/bin/g++-4.1 
 
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.4 40 --slave /usr/bin/g++ g++ /usr/bin/g++-4.4

cd NVIDIA_GPU_Computing_SDK/C
 
make

Now it should unpack everything succesfully. You may get a lot of warnings during the process, but these can safely be ignored.

Once it is done you can test that everything does in fact work by going into

Code:

cd NVIDIA_GPU_Computing_SDK/C/bin/linux/release/

Examen Gramaticas CIDETEC 2009

Entregar antes del 17 de Noviembre de 2009.

Respuestas copiadas se tacharan.

Platicas de TOGNU en SITEC 2009

Saludos, publico las platicas de seguridad y de ubuntu del Congreso SITEC 2009

Realizado en la ciudad de Celaya.

Filosofia Ubuntu

Pen test

Google Hacking

Nuevo Ubuntu 9.10 Karmic Koala

Como abrir aplicaciones libres con formato RUNZ Extension en Ubuntu

undefinedPor TOGNUundefined undefinedExiste un número considerable de aplicaciones portables disponibles para Ubuntu (Linux)en formato “.RUNZ” el cual no es reconocido por ubuntu , es por eso que deberas de instalar un framework para correlo.undefined undefinedLa extension .RUNZ es como un archivo .EXE en Windows y como un archivo .DMG en la Mac.undefined undefinedPara poder interpretarlo será necesario instalar la extension .RUNZ ya que es un archivo tipo DEBundefined

Oración del Ubuntero

Por tognu

Que el Kernel de Linux este siempre con todos nosotros hermanos!

(Responde el resto)

Y con tu disco duro.

Orate-emos.

Mark Shuttleworth que estas en Canonical,

Santificado sea tu Ubuntu

Venga a nosotros tu aplicación

tanto en casa como el trabajo

Hágase tu voluntad así en el Desktop como en el Server.

Danos hoy la actualización de cada día

Y perdona nuestros errores en la consola

así como nosotros perdonamos a Windows,

no nos dejes caer en la tentación del software privativo

y más líbranos de los malvados bug`s.

Amen.

Démonos fraternalmente la ayuda.

Podemos compilar en paz.

Transmisión de Radio por Internet usando winamp

undefinedundefined undefinedPor tognu: Para locutores de Radiomax www.radiomax.com.mxundefined undefinedConsiste básicamente en un Servidor de Radio y en un plugin para Winamp donde reproduciremos la música. Ambas aplicaciones las ofrece SHOUTcast.undefined

• Web oficial de SHOUTcast: www.shoutcast.com
• Página de downloads SHOUTcast: www.shoutcast.com/download/

undefinedUtilizaremos dos programas:undefined undefined1. SHOUTcast DSP Plug-In for Winamp: es un programa que se acopla al Winamp (plugin) y se usa como reproductor y creador de playlists. Se compone de un conjunto de herramientas que toman el sonido reproducido en Winamp para enviarlo al Server.undefined undefined2. SHOUTcast Server: es el programa servidor, que va a enviar a nuestros oyentes el sonido que queremos emitir (streaming).undefined undefinedAmbos programas son gratuitos y pueden estar funcionando en la misma máquina. Para el Server hay versiones disponibles para Win32, FreeBSD, Linux y otros.undefined undefinedEmpecemos:undefined undefinedPaso 1. Bajar e instalar el “SHOUTcast DSP Plug-In for Winamp” (el 1). Para ello vamos a la Web de SHOUTcast y hacemos click en download, hacemos click en “Be a DJ“, descargamos el “SHOUTcast DSP Plug-In for Winamp”. Para instalarlo simplemente hacemos doble clic y luego Next.undefined undefinedPaso 2. Bajar e instalar el “SHOUTcast Server” (el 2); Para ello en la Web de SHOUTcast pinchamos en download, hacemos click en “Be a Server“, descargamos la última versión de SHOUTcast Server (Download the latest version of SHOUTcast Server). Aceptamos la licencia y pinchamos en “SHOUTcast WIN32 Console/GUI server v1.8.9″ que es el de Windows. Para instalarlo simplemente hacemos doble clic y luego Next.undefined undefinedPaso 3. Ejecutamos el “SHOUTcast Server” haciendo clic en su icono en Inicio/Programs/”SHOUTcast DNAS (GUI), ahora verás una consola de Windows diciéndote que tu servidor esta preparado para empezar a servir tu música (ver foto). Vemos que aparece un icono en la barra de tareas, eso es que esta activo. Pulsaremos en ‘Edit config’ para modificar la configuración de nuestro servidor. Es interesante cambiar el password y otras configuraciones. El password default es changeme (cambiame en ingles) y es el default del DPS por lo que funcionará sin cambiarlo, pero es conveniente. Con configurar las 3 primeras opciones (Required stuff) será suficiente.undefined undefinedundefined undefinedPaso 4. Abrimos WinAmp y configuramos “SHOUTcast DSP Plug-In for Winamp“; para ello abrimos Winamp y vamos al panel de ‘Preferences’ (Ctrl+P) en Plug-ins seleccionamos ‘DSP/Effect’, seleccionamos ‘Nullsoft SHOUTcast Source DSP’, una ventana de SHOUTcast se abrirá.undefined undefined undefined undefinedYa está todo preparado para emitir, aunque primero podemos dar un repaso a la configuración:undefined

• En Output podemos configurar: el equipo donde esta el servidor de radio (localhost si esta en la misma maquina), el Password es el password configurado en el Server que sirve para conectar al Server para emitir y acceder a configuración (cambiar en el servidor y aquí para impedir intrusos), conviene mantener el puerto 8000 que es el default del servidor.
• En Encoder podemos configurar el codec con el que emitiremos, muy recomendado mp3 de no mas de 24kbs ya que cuanto mas alto mas ancho de banda consume.
• En Input podemos indicar la procedencia del sonido: el Winamp o Soundcard Input; este último supongo que por ejemplo para hablar por micrófono o bien para pinchar un disco vinilo cuyo reproductor este conectada a la tarjeta de sonido.

undefinedPaso 5. Vamos a ponernos a emitir. Abrimos el Winamp y se abrirá el SHOUTcast Source. Pulsamos el botón “connect“; si el password configurado es el mismo del servidor conectará. Ahora vamos al Winamp y le damos al Play para que reproduzca una canción. Veremos que en ‘Status’, se mueve el tiempo y los bytes enviados. Nuestra radio esta emitiendo; en el paso 6 probaremos conectar desde otra máquina.undefined undefinedundefined undefinedPaso 6. Prueba tu servidor; abre un reproductor mp3 en otro ordenador e intenta conectar con tu servidor, la dirección será algo similar a http://tu IP:puerto/.

Prueba la página de tu servidor, abre tu navegador y ve a http://tu IP:puerto/ , aquí verás información importante sobre tu servidor, para acceso administrativo, haz click en Admin e introduce tu password.

Aclaración: ‘tu IP’ se refiere a la IP de la maquina servidor; para que se conecte alguien de Internet deberá ser la IP pública y si es un cliente de tu red local, será tu IP de red. Puerto se refiere al puerto configurado, normalmente el 8000. Si tienes router el puerto 8000 deberás tenerlo abierto. Supongo que estas familiarizado con esto de las IPs y de los puertos.undefined undefinedNota:

Prepara tu sonido para el streaming. Las canciones que pienses emitir has de comprimirlas en mp3 mono a 32 Kbps single-rate (como mucho), ya que así ahorrarás ancho de banda y muchas más personas podrán oir tu radio.

Ahora ya solo tienes que darle publicidad, la mejor forma es crear una página Web en la que indiques tu programación y tu horario de emisión, pero recuerda, que no todos tus oyentes viven en la misma franja horaria.