Agregador de noticias

La fundación Wikimedia anuncia la migración de sus 400 servidores que actualmente trabajaban con Red Hat Enterprise Linux y Fedora a Ubuntu 8.04 LTS.

Con esto se pretende entregar un mejor servicio así como una mejor administración.

      

En el sitio web de Ubuntu proporcionan dos widgets con una cuenta regresiva hasta el día del lanzamiento de Ubuntu 8.10

Es una manera de promocionar esta distribución.

Opción 1: Banner oscuro

Si deseas agregar este banner en tu sitio web o blog, solamente agrega el siguiente código javascript:

<script type="text/javascript" src="http://www.ubuntu.com/files/countdown/display.js"></script>

Opción 2: Banner claro

Este banner me gusta más, colores que resaltan más. Si deseas agregar este banner en tu sitio web o blog, solamente agrega el siguiente código javascript:

<script type="text/javascript" src="http://www.ubuntu.com/files/countdown/display2.js"></script>

Lamentablemente los blogs de wordpress.com no pueden agregar estos banners ya que no está permitido la inclusión de javascript en ninguna parte del blog, la solución que se me ocurre es agregar a tu blog un banner estático que encontrarás aqui o agregar las imagenes todos los días manualmente… ni modo :S

Igual la idea es difundir ubuntu

      

En Softpedia tienen disponible una serie de pantallazos de la versión beta de Ubuntu 8.10 “intrepid Ibex”.

Aún nada está dicho, pero el entorno gráfico parece que se queda como el de Hardy… quién sabe.

      

El día de hoy ha sido lanzada la versión beta de Ubuntu 8.10 “Intrepid Ibex”.

Entre sus principales características se encuentra la versión 2.6.27 del Kernel, GNOME 2.24 y X.Org 7.4 .

Todos los detalles de esta versión y su descarga aquí.

      

Los LoCo Teams Aprobados de Ubuntu ya pueden pre-ordenar CDs de Intrepid, la idea es que se disponga de CDs para las fiestas de lanzamiento, eventos cercanos o publicitar este lanzamiento de alguna manera con CDs justo a tiempo para obsequiar
Es solamente una pre-orden, serán enviados a los LoCo Teams a penas sea el lanzamiento oficial, no antes.

Esta vez la cantidad de entrega es un poco mayor:

• Ubuntu: PC: 230
• Kubuntu: PC: 50
• Server PC: PC: 50
• Server 64bit: PC: 20

Más información: https://wiki.ubuntu.com/LoCoGettingCds

      

hahaha lol

Vía: David Nielsen

      

The ubuntu counter project, como su nombre bien lo dice, es un proyecto por el cual se pretende tener un conteo de todos los usuario de Ubuntu, tratando, de alguna manera, registrar el número de máquinas con este sistema operativo y especificando también la versión.

Por qué? simple, Ubuntu rocks!

Según esta web soy el usuario ubuntu número:

Como un dato, en las estadísticas de este sitio, muestra que actualmente hay 24059 usuarios de Ubuntu, es muy poco me imagino por la cantidad de usuarios registrados (recuerden las declaraciones de Mark que daban como 6 millones de usuarios en la actualidad), de todos modos es un buen sitio para mantener un conteo, eso si todos se registraran, anímate!

Enlace: The Ubuntu Counter Project

      

Tengo una impresora Canon i250 hace ya varios años, hasta ahora no he tenido una razón suficiente como para pensar en una nueva compra, no la uso demasiado, así que si es ligera, barata y cumple con lo que necesito, pues que siga de compañía

Ha sido un poco difícil configurar este modelo de impresora, Ubuntu no la reconoce automáticamente y no figura en la lista de modelos soportados… hay que buscarse los drivers por algún lugar de internet.

Me encontré con el blog de dannyman, donde explican los pasos para hacerla funcionar, las instrucciones son para Ubuntu 7.04 específicamente, pero no he tenido ningún problema en hacer lo mismo en Ubuntu 8.04 con los mismos buenos resultados.
Los pasos necesarios:

Instalamos unos cuantos paquetes previos necesarios:

sudo apt-get install libpng3 libtiff4 cupsys alien

Vamos al directorio tmp
cd /tmp

Descargamos los drivers de la web de Canon, son paquetes del tipo .rpm, tenemos que convertirlos a .deb para poder usarlos en Ubuntu:

wget http://download.canon.com.au/bj/i250linux/bjfilteri250-2.3-0.i386.rpm
wget http://download.canon.com.au/bj/i250linux/bjfiltercups-2.3-0.i386.rpm

Los convertimos a .deb:

sudo alien –scripts bjfilteri250-2.3-0.i386.rpm
sudo alien –scripts bjfiltercups-2.3-0.i386.rpm

Instalamos estos nuevos paquetes y los eliminamos, una vez instalados ya no son necesarios:

sudo dpkg -i bjfiltercups_2.3-1_i386.deb bjfilteri250_2.3-1_i386.deb rm
bjfiltercups-2.3-0.i386.rpm bjfilteri250_2.3-1_i386.deb bjfiltercups_2.3-1_i386.deb
bjfilteri250-2.3-0.i386.rpm

Hacemos enlaces simbólicos necesarios en algunos archivos:

sudo ln -s /usr/lib/libtiff.so.4 /usr/lib/libtiff.so.3
sudo ln -s /usr/lib/libpng.so.3 /usr/lib/libpng.so.2

Reiniciamos CUPS:

sudo /etc/init.d/cupsys restart

Listo, con esto tu impresora Canon i250 funcionará sin problemas en Ubuntu, dirígete a Sistema/Administración/Impresoras y sigue el asistente de configuración, en la lista de modelos Canon aparecerá la i250.

Si aún si, no figura el modelo en la lista, puedes optar por la segunda opción: “Proporciona archivo PPD”, la ruta donde se encuentra este archivo es: /usr/share/cups/model/canoni250.ppd

Seleccionalo y con eso ya va todo sin problemas.
Como tengo esta impresora, y seguro que la tendré bastante tiempo más, si por ahí algún día los drivers que descargamos de la web de Canon dejan de estar disponibles dejan un comentario con algún email de contacto y sin mayor problema les envío los archivos, a mi me ha costado buscar la manera de hacer funcionar esta impresora y seguro que a más de uno le interesa.

      

CISAISI 2008 (Congreso Internacional Sud-Americano de Ingeniría de Sistemas, Computación e Informática 2008), is an International Latin American event of Systems Engineers, Computing and Informatics. This event is on its XII edition and it will be in Arequipa - Perú, from the 6 to the 10th of October, at Universidad Católica de Santa María - UCSM, which is the University where I’ve studied.

This event was created to do courses and debates, give conferences and summit scientific work. On the present edition of the CISAISI 2008, a new feature has been added, which is the “Poster Contest”, that allows young people, such as students, to summit any scientific work they are working on, related to Informatics.

On this edition, I summited my Thesis as a paper for this “Poster Contest”. This means that I’ll be presenting my Thesis (”Designing a Model to Implement High Availability Web Servers”), and talk about it during the event. This event is very important because many people from different cities around Latin America are going to be present. This is a good chance to promote Ubuntu in Cluster utilization, since my Thesis was done creating clusters in Ubuntu. This will show to many people that Linux, and specially Ubuntu, is a powerful OS to create High Availability Clusters. This will also introduce DRBD to the Latin American Market.

So, whish me luck!! :).

      

As you may know, I applied for JJ UDS Sponsorship. I think that today was the last that people could summit their ideas. But, people can still support them I guess. Since I have been pretty busy the past few days, I just got some time to explain my ideas a little more.

My first idea is Centralized Cluster Administration. This idea is related to the creation of an application that will help us implement and manage LVS Based Clusters. I got this idea because, as you may know, I did my thesis about Designing a Model to Implement High Availability Web Servers using LVS based clusters.

My second idea is Ubuntu Centralized Image Installation/Recovery/Backup. This idea is related to the creation of an application that will help us install Ubuntu from a centralized server on a LAN, similar to what RIS is. It will also allow us to create images, and be able to recover them and create backups, and so on.

So, if you think they are good ideas, it would be great to have your support. Thanks :).

      

As I did with hardy alpha 6 , i downloaded the iso un Sunday, willing to tested on a vmachine.

But on Monday I changed my mind , decided to install it on my laptop (also have a little talk with nxvl)

Here are my impresions about the all process

Boot & Installation

• Cd boot as spected
• Properly displayed the menu
• Direct intallation never boot
• Live Session worked fine
• Installation from live was ok (like the new partition graphics)

Installation process reported no problem

Log in &  hardware Configuratión

• GDM worked
• my display resolution was 800×600 (I have a Nvidia chipset)
• Sound worked
• USB ports worked
• Keyboard worked except from some fn keys (they worked good on hardy)
• Touchpad a little slow
• Integrated Webcam worked (checked with Gnome cheese)
• Jockey crash, couldn’t test atheros driver provided for it

For my nvidia chipset configuration I traid EnvyNG but it never opened, i manually download the driver and installed after i return with a better resolution.

Customization & Software

• Great look
• New human Theme Rocks!
• Pidgin works fine
• OpenOffice 2.4 is quite fast now (waiting ooo 3)
• Rhythmbox works very
• Terminator didn’t open
• The new network configuration interfase works fine but can be a little confuse

here is my Desktop

To Do.

• Test sound recording
• Test LiveUSB from live session
• Test Suspend and Hibernate
• Test DVD playback
• Tray to make work the applications that didn’t work

So far Intrepid is rocking!!

Posted in Planet, Ubuntu      

Right now checking mails, news and stuff

also testing Intrepid Ibex Alpha 6

1. Take a picture of yourself right now.
2. Don’t change your clothes, don’t fix your hair…just take a picture.
3. Post that picture with NO editing.
4. Post these instructions with your picture.

Posted in Planet, Ubuntu      

After a few weeks of being very very busy… I finally have finished most of the things I had to do and finally have some time to continue contributing to Ubuntu.

The first thing I’ve done, is to add some ideas to brainstorm and apply for JJ UDS Sponsorship. My Ideas are the following:

• Ubuntu Centralized Image Installation/Recovery/Backup
• Centralized Cluster Administration

Now, as you may know, translations are open again so let’s start translating.

And finally, I need to request my MOTU mentorship again, since I had to leave it while I was busy… so during this week… I might be restarting my Mentorship Process.

For those who have been waiting me to finish the article of DRBD/NFS and DRBD/MySQL… I will post it soon :).

Btw, if someone who works in FIU (Florida International University) gets to read this, and is willing to help me with information in admissions/assistanships (MS in Telecommunications & Networking or Computer Science) and stuff like that, please contact me or leave me your contact information. Thanks :).

From Software Freedom Day ‘08

SpaceCube una computadora realmente pequeña
SpaceCube es una computadora que mide 2×2x2 pulgadas, tiene forma de cubo y ejecuta Linux.
Algunas de sus especificaciones son:

• Procesador: VR5701CPU 300MHz
• RAM: 64Mb
• Disco Duro: 16Mb tipo flash
• Red: 100/MBs Ethernet
• SO: Versión de Red Hat que se ejecuta en una memoria CompactFlash de un 1Gb.
• Salida VGA, puerto USB

fuente : Artìculo dado a conocer en sala apesol del server freenode x Ju4npE

• http://www.shimafuji.co.jp/product/semc5701a01.html
• http://comulinux.blogspot.com/2008/08/spacecube-una-computadora-realmente.html

El reconocido Jon “maddog” Hall, Presidente y Director Ejecutivo de Linux, sistema operativo tipo Unix que se distribuye bajo la l El reconocido Jon “maddog” Hall, Presidente y Director Ejecutivo de Linux, sistema operativo tipo Unix que se distribuye bajo la licencia pública y que es base del buscador Firefox, entre otros programas. Estuvo en el Campus Party 2008 en Bogotá y con su testimonio dió una verdadera clase de las ventajas que tiene un software libre frente a uno cerrado.

En los últimos años el software libre ha venido ganando terreno dentro de las empresas tradicionales. Las instituciones públicas y privadas más importantes alrededor del mundo apuestan hoy en día por incluir tanto aplicaciones como sistemas operativos de código abierto completos en sus labores cotidianas de negocio. Descubre cómo conjugar el software libre con la visión empresarial a través de los conocimientos de Jon “maddog” Hall, director ejecutivo de Linux Internacional

fuente:

http://www.campus-party.com.co//index.php3

A unas horas de Global Bug Jam en Peru /  A few hours for Global Bug Jam in Peru.

Detalles del Evento / Event Details

Donde: Facultad de Ingeniería de Sistemas, Cómputo y Telecomunicaciones
Universidad Inca Garcilaso de la Vega

Av. Bolivar 1848, Pueblo Libre - Lima, Perú

Cuando: 9 de Agosto

Hora: 11:30hrs

—–

Where: Inca Garcilazo de la Vega University - System Engenering Faculty

Av. Bolivar 1848, Pueblo Libre - Lima, Perú

When: August 9th

Time: 11:30hrs

—

Lest squash those bugs!!!

Ubuntu needs you, join your LoCO team bug squasher unit

Would you like to know more? >>

Hola amigos, me encontre con este interesante libro y que decidi compartirloes un eBook que tiene como tópico principal PyQT la integración completa entre Python y las librerías gráficas QT. Esta guía se encuentra bajo licencia Creative Commons, y es posible distribuirla totalmente libre, de hecho es posible colaborar, aportando nueva documentación, ejemplos, reportando errores, etc..

Espero les aproveche.

Fuente y Desacarga de libro

http://www.elcodigok.com.ar/2008/07/pyqt-desarrollando-aplicaciones-de-escritorios/

As you know, in a previous post I showed how to install DRBD in Hardy Heron, in an active/passive configuration. Now, I’m gonna show you how to install and configure Heartbeat to automatically monitor this active/passive configuration, and provide High Availability. This means I’ll show you how to integrate DRBD in a simple Heartbeat V1 configuration, and as a plus, I’ll show you how to use the meatware software provided by STONITH.

To do this, we have to install Heartbeat and make changes in three files, which are /etc/ha.d/ha.cf, /etc/ha.d/haresources and /etc/ha.d/authkeys. First of all we install Heartbeat as follows, in both nodes:

sudo apt-get install heartbeat-2

After the installation is completed, the first file we need to configure, in both nodes, is /etc/ha.d/ha.cf as follows:

logfile /var/log/ha-log
keepalive 2
deadtime 30
udpport 695
bcast eth0
auto_failback off
node drbd1 drbd2

Note: Notice that the auto_failback option is in off. This means that if the drbd1 fails, drbd2 will take control over the service, and if drbd1 comes back online, drbd2 will not failback to drbd1 and drbd2 will remain as the active node.

Now, as you know this is an active/passive configuration, so we have to decide which node is going to be the primary and which node is going to be the secondary one, for the Heartbeat configuration. (If you have followed my previous post, the drbd1 node is going to be our primary node, and drbd2 will be our secondary node). We also have to consider here is where are we going to mount the DRBD resource in our filesystem, and which IP address is going to used as the VIP (The Virtual IP is going to be used to access a service, or a DRBD resource, over the network, since we are going to use DRBD for NFS and/or MySQL).

So, assuming drbd1 is the primary node, the VIP is 172.16.0.135 and we are going to mount the DRBD resource in /data (so create the directory in both nodes), we edit /etc/ha.d/haresources as follows, in both nodes:

drbd1  IPaddr::172.16.0.135/24/eth0 drbddisk::testing Filesystem::/dev/drbd0::/data::ext3

Note: Notice that we are specifying the DRBD resource with the drbddisk option.

Then, we have to edit the /etc/ha.d/authkeys file, which is going to be used by Heartbeat to authenticate with the other node. So, we edit it as follows in both nodes:

auth 3
3 md5 DesiredPassword

Finally, we change file permissions to this last file as follows:

sudo chmod 600 /etc/ha.d/authkeys

Now that we have both nodes configured, I recommend you to power off both nodes and boot the node we want to have as primary. In our case, it is drbd1. After booting up this node, we need to verify that Heartbeat has started the DRBD resource (we can see this with cat /proc/drbd) and mounted it in /data. If it has, start the secondary node and verify that it is the secondary one.

If everything has gone right, try the failover process powering off the primary node. You will notice that the node that had the DRBD resource as secondary, it’s now the primary one and it has control over the service. Also verify is the VIP address is working (should appear as eth0:0 issuing ifconfig).

After verifying everything is working as expected, it is always recommendable to have a Fencing device to ensure data integrity. This fencing device will prevent an Split-Brain condition. A well-known Fencing mechanism is known as STONITH (Shoot the Other Node in the Head). This mechanism will basically power off or reset a node which is supposed to be dead. This means that if drbd1 is supposed to be dead, drbd2 will take control of the service or, in this case, the DRBD resource. But, if drbd1 is not actually dead and drbd2 tries to take control over the shared DRBD resource, an Split-Brain condition will occur. So STONITH will ensure that drbd1 has been reseted or powered off so that drbd2 can take control of the DRBD resource.

To do this, there is an stonith package that is used to work with STONITH/Fencing devices in Heartbeat. But, since we don’t have a real Fencing device, we will use meatware. Meatware is a software provided by STONITH, that simulates the use of a STONITH/Fencing device, by not allowing the secondary node (drbd2) to take control over the shared resources If there has not been a confirmation that the primary node (drbd1) has been powered off or rebooted. This requires operator intervention. So to integrate the meatware software with Heartbeat we do as follows:

sudo apt-get install stonith

Then, we have to modify /etc/ha.d/ha.cf like this (in both nodes):

... [Output Ommitted]
auto_failback off
stonith_host drbd1 meatware drbd2
stonith_host drbd2 meatware drbd1
node drbd1 drbd2

Then we power off the primary node (in this case drbd1) and reboot secondary node (drbd2). After reboot, take a look at /var/log/ha-log until you see something like this:

As you can see, STONITH is sending a message that says that we need to confirm that drbd1 has been rebooted so that drbd2 can take control over the service. So, take a look at /proc/drbd and you will see that the DRBD resource is still as secondary. So, we do as follows:

sudo meatclient -c drbd1

And we will see something like this:

Now, we confirm that it has been rebooted and we can now see that drbd2 will take control of the resource by setting the DRBD resource as primary (cat /proc/drbd).

So we can now start drbd1. Everytime the primary node fails, the secondary node will display a message on /var/log/ha-log saying that we should confirm that the primary has been rebooted so that the secondary can take control of the service and become the new primary.

In a next post I’ll cover how to make NFS make use of DRBD. Any comments, suggestions, etc, you know where to find me :).

debian

El 26 de julio se ha anuncio la publicación de la cuarta revisión de Debian 4.0 (”Etch”). Además de la habitual corrección de bugs, por primera vez en la historia de Debian se añade nueva funcionalidad a una distribución estable ya publicada, en la forma de soporte de nuevo hardware. Los componentes que no eran detectados por el instalador original de Etch, lo podrán ser ahora a través de la instalación de un kernel 2.6.24, así como de una nueva versión de X.org.

fuente :http://debian.barrapunto.com/debian/08/07/28/1054204.shtml