UPDATE: I’ve also written a HOWTO on adding support for mrsid image format in MapServer5.

• This first item is just for the sake of comfort, I don’t like to walk to our datacenter to change a CD/DVD, so I import the CD images using NFS and then loop mount them. So, first of all, we’ll mount the CD Images:
  for i in `seq 1 5`; do mount -t iso9660 -o loop /RedHatCDs/rhel-5-server-i386-disc$i.iso /mnt/cd$i; done
• WEB SERVER

  We need a web server with PHP and freetds support. (FreeTDS is needed to access Microsoft SQLServer or Sybase databases). We’ll start with apache rpm’s and some dependencies:

  rpm -i /mnt/cd2/Server/unixODBC-2.2.11-7.1.i386.rpm
rpm -i /mnt/cd2/Server/mx-2.0.6-2.2.2.i386.rpm
rpm -i /mnt/cd2/Server/httpd-2.2.3-6.el5.i386.rpm
rpm -i /mnt/cd2/Server/unixODBC-devel-2.2.11-7.1.i386.rpm

  Now we are ready to compile freetds from source. We must rename the tgz package as freetds-version.tar.gz else rpmbuild won’t work.

  cd
wget http://ibiblio.org/pub/Linux/ALPHA/freetds/stable/freetds-stable.tgz
mv freetds-stable.tgz freetds-0.64.tar.gz
rpmbuild -ta freetds-0.64.tar.gz
rpm -i /usr/src/redhat/RPMS/i386/freetds-0.64-1.i386.rpm
rpm -i /usr/src/redhat/RPMS/i386/freetds-devel-0.64-1.i386.rpm

  rpm -i /usr/src/redhat/RPMS/i386/freetds-unixodbc-0.64-1.i386.rpm
rpm -i /usr/src/redhat/RPMS/i386/freetds-devel-0.64-1.i386.rpm

  Now we’ll simply install PHP packages.

  rpm -i /mnt/cd2/Server/php-cli-5.1.6-5.el5.i386.rpm \
/mnt/cd2/Server/php-common-5.1.6-5.el5.i386.rpm \
/mnt/cd2/Server/php-5.1.6-5.el5.i386.rpm \
/mnt/cd3/Server/php-gd-5.1.6-5.el5.i386.rpm \
/mnt/cd3/Server/php-pgsql-5.1.6-5.el5.i386.rpm \
/mnt/cd2/Server/php-odbc-5.1.6-5.el5.i386.rpm \
/mnt/cd2/Server/php-pdo-5.1.6-5.el5.i386.rpm

  Some PHP parameters have to be tweaked in /etc/php.ini:

  max_execution_time = 150
  max_input_time = 200
  memory_limit = 256M
  error_reporting = E_ALL & ~E_NOTICE
  display_errors = On ; To debug errors
  register_long_arrays = On
  extension_dir = “/usr/lib/php/modules”

  /etc/httpd/conf/httpd.conf also needs some slight changes. First one is under dir_module section

  <IfModule dir_module>
  DirectoryIndex index.php index.html
  </if module>

  Second one is in AddType block, we’ll add php extensions there:

  AppType application/x-httpd-php .php .phtml
  AddType application/x-httpd-php-source .phps

  Now we’ll test the server.

  /etc/init.d/httpd start

  Any browser should be able to show Apache’s start page.

  lynx http://localhost

  To test php, we’ll write an ultra tiny page and browse there.

  echo "<?php phpinfo (); ?>" > /var/www/html/info.php
lynx http://localhost/info.php

  All PHP options and Apache should be on that page. If everything is OK, it’s time to add apache to autostart scripts.

  chkconfig httpd on

  Our web server is ready for the fiesta It’s time to move on and work on the database backend.

• POSTGRES

  We’ll work from source here, so we have to download, configure, make and install. Easy stuff!

  cd
wget http://ftp5.es.postgresql.org/mirror/postgresql//source/v8.2.6/postgresql-8.2.6.tar.bz2
tar xjvf postgresql-8.2.6.tar.bz2 -C /usr/local/
cd /usr/local/postgresql-8.2.6/
LDFLAGS=-lstdc++ ./configure \
--prefix=/usr/local/pgsql \
--with-perl \
--with-python \
--with-krb5 \
--with-openssl
make
make install

  We still have to configure everything.

  First of all, we create the data directory.

  mkdir /usr/local/pgsql/data

  This directory must be owned by user postgres and group postgres, so we need them both:

  groupadd -r postgres
adduser postgres -g postgres
chown postgres:postgres /usr/local/pgsql/data/

  We should use user postgres everytime we use the database. It’s a good time to set a password for it.

  passwd postgres
su - postgres
/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data/ -U postgres -W
/usr/local/pgsql/bin/pg_ctl -D /usr/local/pgsql/data/ -l /usr/local/pgsql/data/logfile
exit

  If everything works, we also have to write an script for the autostart of the server in/etc/init.d/postgresql:

  
#!/bin/sh
# postgresql This is the init script for starting up the
# PostgreSQL server
# chkconfig: - 85 15
# description: Starts and stops the PostgreSQL backend daemon that handles all database requests.
# processname: postmaster
# pidfile: /usr/local/pgsql/data/postmaster.pid
#
# Source function library.
. /etc/rc.d/init.d/functions
# Get config.
. /etc/sysconfig/network
# Check that networking is up.
# Pretty much need it for postmaster.
[ ${NETWORKING} = "no" ] && exit 0
[ -f /usr/local/pgsql/bin/postmaster ] || exit 0
# See how we were called.
case "$1" in
start)
pid=`pidof pg_ctl`
if [ $pid ]
then
echo "Postgres already running."
else
echo -n "Starting postgresql service: "
su -l postgres -c '/usr/local/pgsql/bin/pg_ctl -D /usr/local/pgsql/data/ -l /usr/local/pgsql/data/logfile start'
sleep 1
echo
exit
fi
;;
stop)
echo -n "Stopping postgresql service: "
su -l postgres -c '/usr/local/pgsql/bin/pg_ctl -D /usr/local/pgsql/data/ stop'
sleep 2
rm -f /usr/local/pgsql/data/postmaster.pid
echo
;;
restart)
$0 stop
$0 start
;;
status)
su -l postgres -c '/usr/local/pgsql/bin/pg_ctl -D /usr/local/pgsql/data/ status'
;;
*)
echo "Usage: postgresql {start|stop|restart|status}"
exit 1
esac
exit 0

  These are the orders to write it an add to autostart:

  vi /etc/init.d/postgresql
chmod 700 /etc/init.d/postgresql
/etc/init.d/postgresql restart
/etc/init.d/postgresql status
chkconfig --add postgresql

• POSTGIS

  We’ll need Proj library, but it’s pretty easy to build.

  wget ftp://ftp.remotesensing.org/proj/proj-4.5.0.tar.gz
tar -xvzf proj-4.5.0.tar.gz -C /usr/local/
cd /usr/local/proj-4.5.0/
./configure
make
make install

  GEOS library should be easy too.

  cd
wget http://geos.refractions.net/downloads/geos-3.0.0.tar.bz2
tar xjvf geos-3.0.0.tar.bz2 -C /usr/local/
cd /usr/local/geos-3.0.0/
./configure
make
make install

  PostGIS compilation won’t start the problems yet

  cd
wget http://www.postgis.org/download/postgis-1.3.2.tar.gz
tar xvzf postgis-1.3.2.tar.gz -C /usr/local/postgresql-8.2.6/contrib/
cd /usr/local/postgresql-8.2.6/contrib/postgis-1.3.2/
./configure --with-pgsql=/usr/local/pgsql/bin/pg_config
make
make install

  Installation deserves some more talking. First we need to add one line to /etc/ld.so.conf so the libraries are usable in exec time.

  echo "/usr/local/lib" >> /etc/ld.so.conf

  Binaries are in /usr/local/pgsql/bin, it may be worth to add this to th path.

  Libraries are in /usr/local/pgsql/lib, so we add this to /etc/ld.so.conf too.
  echo "/usr/local/pgsql/lib" >> /etc/ld.so.conf
rm /usr/local/pgsql/lib/libpq.so.5
ln -s /usr/local/pgsql/lib/libpq.so.5.0 /usr/local/pgsql/lib/libpq.so.5
ldconfig

  This ends PostGIS Installation. You can create a test db and add the extensions as a test:

  /usr/local/pgsql/bin/createdb --encoding latin1 test -u
/usr/local/pgsql/bin/createlang plpgsql test -u
/usr/local/pgsql/bin/psql -d test -f /usr/local/pgsql/share/lwpostgis.sql -u
/usr/local/pgsql/bin/psql -d test -f /usr/local/pgsql/share/spatial_ref_sys.sql -u

  Last two orders should end with COMMIT and VACUUM respectively, if all went as expected.

• MAPSERVER

  Now, all the infraestructure is in place so it’s time to start with the libraries that MapServer will use.

  GDAL permits to use most common GIS formats.

  cd
wget http://download.osgeo.org/gdal/gdal-1.5.0.tar.gz
tar xvzf gdal-1.5.0.tar.gz -C /usr/local/
cd /usr/local/gdal-1.5.0/
./configure --with-png --with-libtiff --with-jpeg --with-gif --with-pg=/usr/local/pgsql/bin/pg_config --with-geos --with-odbc
make
make install
ldconfig

  Every other dependency has a rpm package. One exception, AGG also has an rpm but MapServer won’t build with that version, we’ll build from source that one.

  rpm -i /mnt/cd3/Server/php-devel-5.1.6-5.el5.i386.rpm
rpm -i /mnt/cd1/Server/gd-2.0.33-9.3.fc6.i386.rpm
rpm -i /mnt/cd2/Server/gd-devel-2.0.33-9.3.fc6.i386.rpm \
/mnt/cd2/Server/fontconfig-devel-2.4.1-6.el5.i386.rpm \
/mnt/cd2/Server/freetype-devel-2.2.1-16.el5.i386.rpm \
/mnt/cd2/Server/libX11-devel-1.0.3-8.el5.i386.rpm \
/mnt/cd2/Server/libXpm-devel-3.5.5-3.i386.rpm \
/mnt/cd2/Server/libjpeg-devel-6b-37.i386.rpm \
/mnt/cd2/Server/libpng-devel-1.2.10-7.i386.rpm \
/mnt/cd2/Server/libXau-devel-1.0.1-3.1.i386.rpm \
/mnt/cd2/Server/libXdmcp-devel-1.0.1-2.1.i386.rpm \
/mnt/cd2/Server/xorg-x11-proto-devel-7.1-9.fc6.i386.rpm \
/mnt/cd2/Server/mesa-libGL-devel-6.5.1-7.2.el5.i386.rpm
rpm -i /mnt/cd2/Server/SDL-1.2.10-8.el5.i386.rpm
rpm -i /mnt/cd2/Server/SDL-devel-1.2.10-8.el5.i386.rpm \
/mnt/cd2/Server/alsa-lib-devel-1.0.12-3.el5.i386.rpm \
/mnt/cd2/Server/mesa-libGLU-devel-6.5.1-7.2.el5.i386.rpm \
/mnt/cd2/Server/libXext-devel-1.0.1-2.1.i386.rpm \
/mnt/cd2/Server/libXrandr-devel-1.1.1-3.1.i386.rpm \
/mnt/cd2/Server/libXrender-devel-0.9.1-3.1.i386.rpm \
/mnt/cd2/Server/libXt-devel-1.0.2-3.1.fc6.i386.rpm \
/mnt/cd2/Server/libSM-devel-1.0.1-3.1.i386.rpm \
/mnt/cd2/Server/libICE-devel-1.0.1-2.1.i386.rpm
wget http://www.antigrain.com/agg-2.5.tar.gz
tar xzvf agg-2.5.tar.gz -C /usr/local/
cd /usr/local/agg-2.5/
aclocal
autoheader
autoconf
libtoolize --force
automake --foreign --add-missing --ignore-deps
./configure
make
make install

  Almost done. Before compiling, one detail, max number of symbol objects in a dataset is defined in mapsymbol.h (/usr/local/mapserver-5.0.0/mapsymbol.h after untaring) in line:

  #define MS_SYMBOL_ALLOCSIZE 64 /* number of symbolObj ptrs to allocate for a symbolset at once */

  If you use more than 64 symbols (I do), change it before compiling.

  
cd
wget http://download.osgeo.org/mapserver/mapserver-5.0.0.tar.gz
tar xvzf mapserver-5.0.0.tar.gz -C /usr/local/
cd /usr/local/mapserver-5.0.0/
./configure \
--with-proj=/usr/local/proj-4.5.0 \
--with-geos=/usr/local/bin/geos-config \
--with-ogr=/usr/local/bin/gdal-config \
--with-gdal=/usr/local/bin/gdal-config \
--with-postgis=/usr/local/pgsql/bin/pg_config \
--with-curl-config=/usr/bin/curl-config \
--with-httpd=/usr/sbin/httpd \
--with-php=/usr/include/php \
--with-wfs \
--with-wfsclient \
--with-wmsclient \
--enable-debug \
--with-threads \
--with-wcs \
--with-wcsclient \
--with-sos \
--with-gd \
--with-freetype \
--with-jpeg \
--with-agg=/usr/local/
make clean
make

  Installation is made ‘by hand’:

  
echo "cp mapserv legend scalebar shp2img shptree shptreetst shptreevis sortshp tile4ms /var/www/cgi-bin/"> install.sh
echo "./mapserv -v" >> install.sh
echo "service httpd reload" >> install.sh
chmod +x install.sh
./install.sh


  To test it:

  ./mapserv -v

  The server will answer with its installled features. Then copy the PHP module to it’s place and reload Apache.

  cp /usr/local/mapserver-5.0.0/mapscript/php3/php_mapscript.so /usr/lib/php/modules/
service httpd reload

  Done!!!.

• DEMO

  If you want to test your brand new server, you can use Itasca demo:

  
cd
wget http://maps.dnr.state.mn.us/mapserver_demos/workshop-5.0.zip
unzip workshop-5.0.zip
mv workshop-5.0 /var/www/html/
chown apache:apache /var/www/*
chown -R apache:apache /var/www/html/workshop-5.0/
mkdir /var/www/html/tmp
chmod 777 /var/www/html/tmp

  Before toying with it, change these lines in /var/www/html/workshop-5.0/index.html:

  // EDIT THE NEXT 2 LINES TO MATCH YOUR SETUP
var snippet = "IMAGEPATH '/var/www/html/tmp/'";
snippet += " IMAGEURL '/tmp/'";


  Browse to http://localhost/workshop-5.0/index.html and enjoy!

• THE END

1. A working PCMCIA port
2. To have the card detected as 3 USB Serial ports
3. PPP Drivers
4. Wvdial installed and configured

I’ll assume you have the pcmcia subsystem up and working (else google is your friend).

Secondly, you need the usbserial module. If you don’t have it available, you’ll need a kernel recompilation, else just load it with modprobe usbserial. Once loaded, when you plug the card on the PCMCIA slot, you’ll see a bunch of messages in your syslog, look for these three:


[...]
Jan 11 19:47:50 acsev-109 pl2303 6-1:1.0: pl2303 converter detected
Jan 11 19:47:50 acsev-109 usb 6-1: pl2303 converter now attached to ttyUSB0
Jan 11 19:47:50 acsev-109 pl2303 6-1:1.1: usb_probe_interface
Jan 11 19:47:50 acsev-109 pl2303 6-1:1.1: usb_probe_interface - got id
Jan 11 19:47:50 acsev-109 pl2303 6-1:1.1: pl2303 converter detected
Jan 11 19:47:50 acsev-109 usb 6-1: pl2303 converter now attached to ttyUSB1
Jan 11 19:47:50 acsev-109 pl2303 6-1:1.2: usb_probe_interface
Jan 11 19:47:50 acsev-109 pl2303 6-1:1.2: usb_probe_interface - got id
Jan 11 19:47:50 acsev-109 pl2303 6-1:1.2: pl2303 converter detected
Jan 11 19:47:50 acsev-109 usb 6-1: pl2303 converter now attached to ttyUSB2
Jan 11 19:47:50 acsev-109 usbcore: registered new interface driver pl2303
Jan 11 19:47:50 acsev-109 drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver
Jan 11 19:47:50 acsev-109 drivers/usb/serial/usb-serial.c: USB Serial support registered for GSM modem (1-port)
Jan 11 19:47:50 acsev-109 usbcore: registered new interface driver option
Jan 11 19:47:50 acsev-109 drivers/usb/serial/option.c: USB Driver for GSM modems: v0.7.1


If you can’t see those three messages, it just won’t work (again, google is your friend)

Install PPP: modprobe ppp.

Install and configure wvdial. Install it your preferred way (apt-get it, install from source, use emerge or rpm or whatever), then edit the file /etc/wvdial.conf. These are the settings needed for Vodafone users in Spain. People from other countries should try Tazz Tux’ files on mybroadband.co.za forums.


[Dialer Defaults]

Although there’s a PIN section in the code, I have never been able to use any of my cards with PIN code enabled so I’ll just disable it (I’ve put the SIM card in my phone and told it not to ask for PIN anymore). Then just exec wvdial: wvdial option internet. Enjoy!

Feedback is welcome

1. Descargamos desde la página de Apache el paquete Ready-for-the-fiesta. El paquete es tan completo que viene con mod_perl, php, Apache::ASP y varias cosas más. Instala el paquete en un directorio que no contenga espacios en blanco en su nombre (las cosas de güindows). El instalador nos hará varias preguntas.

   • ¿Instalar nmake? Sí
   • ¿Crear HTML docs? Sí
   • ¿Configurar CPAN? Sí
   • Ahora se abrirá la consola de CPAN y debes teclear
     o conf init
     con lo que comenzará la configuración. Puedes aceptar todos los valores por defecto. Al final debes elegir tu continente, país (España está en la 2ª página de Europa, pulsa return tras la primera página de países y te aparecerán el resto.) y seleccionar algunos de los mirrors de paquetes que te aparezcan.
2. Añade al PATH los directorios [directorio donde instalaste el paquete]/apache2/bin y [directorio donde instalaste el paquete]/perl/bin
3. Crea una carpeta para tus páginas ASP en [directorio donde instalaste el paquete]/apache2/htdocs/ y copia en ellas el archivo .htaccess del directorio con los ejemplos en ASP ([directorio donde instalaste el paquete]/apache2/htdocs/ASP/eg/

Y a disfrutar (si se puede disfrutar con el ASP, claro)

Qué debemos hacer y qué necesitamos:

1. Desinstalar todo lo relacionado con nvidia
   Si, como era mi caso, tu anterior tarjeta era una nvidia, desinstálala ahora mismo, te ahorrará muchos quebraderos de cabeza más adelante. Para ello, ejecuta:

   /usr/bin/nvidia-installer --uninstall

2. Fuentes del kernel
   Necesitarás las fuentes del kernel para poder compilar el módulo que necesitamos. Si has compilado tu propio kernel esto no es ningún problema, si no, si estas usando un kernel de Debian, puedes obtener los paquetes ya creados de la página de Flavio Stanchina (está en inglés)
3. Opciones del kernel
   Tu kernel debe estar compilado con las siguientes opciones, de lo contrario tendrás problemas bien al compilar, bien al intentar cargar el módulo:
   • CONFIG_MODULES=y
   • CONFIG_MODULE_UNLOAD=y
   • CONFIG_KMOD=y
   • # CONFIG_MODVERSIONS is not set
   • CONFIG_MTRR=y
   • CONFIG_AGP=m
   • CONFIG_AGP_chipset=m
   • CONFIG_DRM=m
   • CONFIG_DRM_RADEON=m
   • # CONFIG_FB is not set
   • # CONFIG_FB_RADEON is not set
   • CONFIG_TMPFS=y
4. Obtener el instalador y generar los paquetes
   Para ello primero debes descargar el instalador de la página de ATI. Teniendo en cuenta si tienes instalado el servidor de X de XFree para i386, de XFree para ia64 o de XOrg, deberás bajarte un instalador u otro. Bájate el archivo .run que es el que te permitirá crear los páquetes para debian.
   Una vez descargado, ejecútalo

   chmod u+x ati-driver-installer-8.16.20-i386.run
   ./ati-driver-installer-8.16.20-i386.run

   Por supuesto, es probable que en tu caso, la versión del archivo cambie, usa el sentido común
   Selecciona la opción generar paquetes para una distribución específica y elige tu versión de Debian, en mi caso Debian/unstable, en el tuyo la que tengas instalada.
   Los paquetes que crea estarán en el directorio /tmp.

5. Instalar los paquetes
   De los cinco paquetes que aparecen en el directorio /tmp, sólo dos son fundamentales y son los que instalaremos

   dpkg -i /tmp/fglrx-driver_8.16.20-1_i386.deb
   dpkg -i /tmp/fglrx-kernel-src_8.16.20-1_i386.deb

6. Compilar el módulo del kernel e instalarlo
   Primero eliminamos cualquier fuente del driver que pudiesemos tener de pruebas anteriores, ejecutando

   rm -rf /usr/src/modules/fglrx*

   Después descomprimimos las fuentes del módulo (sabemos que están ahí porque se han creado al instalar el paquete fglrx-kernel-src_8.16.20-1_i386.deb en el paso anterior).

   cd /usr/src
   tar xjf fglrx.tar.bz2

   Para compilar el módulo hay tantos métodos como formas de compilaar el kernel, yo siempre recomiendo hacerlo The Debian Way, es decir usando el comando make-kpkg. Para ello iremos al directorio con las fuentes del núcleo y crearemos un paquete con el módulo

   cd linux
   make-kpkg --added-modules fglrx modules_image

   Es probable, que, según con que opciones compilases tu kernel, necesites añadir bien –append-to-version “[nombre]“, bien –revision “[revision]” o incluso ambas opciones.
   El paquete generado estará en el directorio /usr/src, lo instalamos como siempre con

   dpkg -i fglrx-[version].deb

   Por último, hemos de cargarlo con

   modprobe fglrx

   Si tienes algún problema ejecuta dmesg y actua en consecuencia, lo más usual es que tengas cargado algún otro módulo de drm. Puedes ver los módulos que tienes cargados con lsmod.

7. Configura las X
   Edita el fichero de configuración /etc/X11/XF86Config-4 (o el fichero de configuración de XOrg [/etc/X11/xorg.conf] si es lo que usas tú) y asegurate que en la seccion Device tienes en la línea Driver la cadena “fglrx”. Por ejemplo

   Section "Device"
   Identifier "ATI_Radeon"
   Driver     "fglrx"

   Reinicia las X y ejecuta

   glxinfo

   Debes obtener algo parecido a

   name of display: :0.0
   display: :0  screen: 0
   direct rendering: Yes
   server glx vendor string: SGI
   server glx version string: 1.2
   server glx extensions:
   GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
   client glx vendor string: ATI
   client glx version string: 1.3
   client glx extensions:
   GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
   GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_ATI_pixel_format_float,
   GLX_ATI_render_texture

Referencias. La mayoría de la información necesaria para crear este tutorial viene de diversos foros, y de la página de Flavio Stanchina y de Gentoo ATI Radeon FAQ. Ambas páginas en inglés-]]>

apt-get updateapt-get install wpasupplicant

Una vez instalado, en /usr/share/doc/wpasupplicant/examples/ tenemos una versión anotada y con múltiples ejemplos del archivo de configución wpa_supplicant.conf, debemos copiarlo al directorio /etc

cp /usr/share/doc/wpasupplicant/examples/wpa_supplicant.conf

Ahora editamos el archivo /etc/wpa_supplicant.conf
Primero eliminamos, todas las entradas network que hay al final del archivo y las cambiamos por una que represente nuestra red, así, si lo queremos conectar al router SpeedTouch 580, añadiremos (sirve para casi cualquier router):

network={
ssid="[ElSidDeTuPuntoDeAcceso]"
#psk="[LaClavePSKEnTextoPlano]"
psk=[LaClavePSKEnHexadecimal]
key_mgmt=WPA-PSK
proto=WPA
priority=2
}

Podéis ver que he comentado la clave en texto plano y la he puesto en hexadecimal, esto es recomendable por que así el wpa_supplicant no tendráque calcularla cada vez. Para obtenerla debéis ejecutar

wpa_passphrase [ElSsidDeTuPuntoDeAcceso] [LaClavePSKEnTextoPlano]

El Ssid es el que hayáis configurado en el punto de acceso (en el SpeedTouch 580 en la pestaña inalámbrica) y la clave PSK, la que hayáis configurado en el punto de acceso (en el SpeedTouch 580 en la pestaña seguridad dentro de inalámbrica (tenéis que tener activada la seguridad de nivel 2))
Ya sólodebéis levantar la interfaz inalámbrica

ifconfig wlan0 ip [TuIP]

Y arrancar el wpa_supplicant

wpa_supplicant -Dndiswrapper -iwlan0 -c/etc/wpa_supplicant.conf -dd

Con la opción -dd lo que hacemos es que nos de mucha información sobre lo que está haciendo. De todos modos, siguiendo estos pasos debería funcionar sin problemas, con lo que tras comprobar que funciona bien podemos eliminarlo y arrancarlo como demonio.]]>

There are two ways to do it:

1. Non geek version
   If you’re pretty new to Debian this may be the best way for you:
   • Install the binary packages and the kernel for them. In this moment newest version for a pentium IV is

     apt-get install ndiswrapper-modules-2.6.8-2-686 kernel-image-2.6.8-2

   • Boot the machine with this kernel. Simply turn off the computer and boot it again. In the boot manager (whether grub, or lilo) choose linux-2.6.8-2.
   • Download the driver for Windows (yes, it’s not April’s Fool, I said the seven chars O.S.) from SpeedTouch. The ETSI driver is for E.U. and the FCC one for the U.S.A. (and allows two channels less than the ETSI one)
   • Unzip the file.

     unzip Windows_Instaler_ST121g_R1.0_ETSI.zip

   • Look for a file called BT4501G.inf which is under Installer/Driver/
   • Rename the file to BT4501G.INF

     mv BT4501G.inf BT4501G.INF

   • Plug the SpeedTouch 121g in any USB dock.
   • Let’s install the driver with ndiswrapper.

     ndiswrapper -i BT4501G.INF

   • Type

     ndiswrapper -l

     A message will appear saying that the driver is installed and the hardware present.

   • Now we must load the kernel module

     modprobe ndiswrapper

   • A green light will appear in the USB dongle, now let’s config the wlan.

     iwconfig wlan0 mode "Managed"
     iwconfig wlan0 essid "[YourNetworkName]"
     iwconfig wlan0 key "s:[YourNetworkPassword]"

     I was only able to make this work with a 12 chars password

   • Finaly we bring up the interface

     ifconfig wlan0 [ip] netmask [máscara] up

   • Example:

     iwconfig wlan0 mode "Managed"
     iwconfig wlan0 essid "SuperCoco"
     iwconfig wlan0 key "s:EstoEsArriba"
     ifconfig wlan0 192.168.0.128 netmask 255.255.255.0

2. Normal Version
   If you compiled your own kernel:
   • Get the source code for ndiswrapper

     apt-get install ndiswrapper-source

   • Go to /usr/src and untar the source

     cd /usr/srctar xjvf ndiswrapper-source.tar.bz2

   • Now it depends how you compiled your kernel
     1. If you did it The Debian Way (best option I think, There is a good tutorial in myrddin), you must just type

        cd linuxmake-kpkg modules-image --added-modules ndiswrapper

        Finally install the debian package that will be under /usr/src using dpkg

     2. If you compiled your kernel ‘as ussual’ you should know how to build the kernel module
   • From here on just follow the instructions for non-geeks