En Debian Etch se encuentra el paquete firebird2-super-server pero la versión de firebird que contiene corresponde a la rama 1.5.x y no a la 2.0.x.

Para instalar la versión de firebird correspondiente a la rama 2.0.x debemos instalar el paquete firebird2.0-super que se encuentra en el repositorio de backports http://packages.debian.org/etch-backports/firebird2.0-super

Nota: La instalación fue realizada en una PC con la versión de Debian Etch en inglés, por lo que los mensajes y pantallas que se muestran contienen los textos en inglés pero el proceso que se debe seguir en la versión en español es el mismo.

Lo primero que debemos hacer es agregar el repositorio de backports al archivo de fuentes /etc/apt/sources.list para lo cual insertamos las siguientes lineas:

deb http://www.backports.org/debian etch-backports main contrib non-free
deb-src http://www.backports.org/debian etch-backports main contrib non-free

Despues hacemos sudo apt-get update
Cuando termina, al final nos muestra un mensaje como el siguiente:

Reading package lists… Done
W: GPG error: http://www.backports.org etch-backports Release: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY EA8E8B2116BA136C

No hay problema, el error es porque no tenemos la clave para la autenticación del repositorio backports.
Lo solucionamos instalando el paquete debian-backports-keyring:

sudo apt-get install debian-backports-keyring

Aparece el siguiente mensaje:

Reading package lists… Done
Building dependency tree… Done
The following NEW packages will be installed:
debian-backports-keyring
0 upgraded, 1 newly installed, 0 to remove and 86 not upgraded.
Need to get 3310B of archives.
After unpacking 49.2kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
debian-backports-keyring
Install these packages without verification [y/N]?

Decimos que si y la instalación continúa

Get:1 http://www.backports.org etch-backports/main debian-backports-keyring 2007.06.10 [3310B]
Fetched 3310B in 2s (1640B/s)
Selecting previously deselected package debian-backports-keyring.
(Reading database … 43431 files and directories currently installed.)
Unpacking debian-backports-keyring (from …/debian-backports-keyring_2007.06.10_all.deb) …
Setting up debian-backports-keyring (2007.06.10) …
OK

Ahora si procedemos a instalar firebird 2.0 en su arquitectura super server

sudo apt-get install firebird2.0-super

Al final muestra este mensaje

Setting up firebird2.0-super (2.0.3.12981.ds1-14~bpo40+1) …
Created default security.fdb
Firebird 2.0 server manager not running.
* Not starting Firebird 2.0 server manager
* Use `dpkg-reconfigure firebird2.0-super’ to enable.

Ejecutamos sudo dpkg-reconfigure firebird2.0-super y en la pantalla que aparece seleccionamos Yes

En la siguiente pantalla ponemos un password para el usuario SYSDBA

y después de dar OK la instalación termina indicandonos que el servidor ya esta funcionando.

Firebird 2.0 server manager not running.
Starting Firebird 2.0 server manager…done.
GSEC> GSEC> Firebird 2.0 server manager already running.

Para verificar que está corriendo el servidor ejecutamos

top -b -n1 | grep fb

Debe aparecer un proceso llamado fbguard y uno llamado fbserver

2353 firebird  20   0  3720 1492 1240 S  0.0  0.8   0:00.00 fbguard
2354 firebird  19   0 36272 4192 3060 S  0.0  2.2   0:00.05 fbserver

Creamos un directorio en donde pondremos la base de datos que será accesible desde los clientes remotos con Windows

sudo mkdir /database

Ponemos como propietario del directorio al usuario firebird

sudo chown firebird.firebird /database

Copiamos a este directorio la base de datos, en este caso se llama baseprueba.fdb.
Ya que tenemos la base de datos en ese directorio, ponemos como propietario al usuario firebird

cd /database
sudo chown firebird.firebird baseprueba.fdb

Ahora vamos al directorio /etc/firebird/2.0 y editamos el archivo aliases.conf para crear un alias para la base de datos indicando la ruta en que se encuentra:

Agregamos la siguiente linea al final del archivo aliases.conf
baseprueba.fdb = /database/baseprueba.fdb

Eso es todo, la ruta que deben usar las maquinas cliente en windows para accesar a la base de datos es la IP del servidor, seguido de dos puntos y el alias de la base de datos.

Por ejemplo 192.168.1.10:baseprueba.fdb

Para información de firebird en español se puede consultar el siguiente enlace http://www.firebird.com.mx

A maior diferença que sempre achei entre o Ubuntu e o Debian é o Bluetooth Manager que deixa a coisa muito mais fácil no Ubuntu

Mas depois de pesquisar um pouquinho achei um método fácil de transferencia de fotos e arquivos no Debian Etch.

Basta:

* conectar o dongle bluetooth
* colocar em modo localizável: hciconfig hci0 piscan
* habilitar a recepção: obexpushd -B

Depois disso é so enviar o(s) arquivos do celular p/ o computador (cada aparelho tem sua maneira de fazer isso) os arquivos enviados estão na pasta /home/nomedousuario

E p/ localizar novos dispositivos:

* obexftp -b

Here’s a nice post on setting up Nginx with PHP-FPM, Xcache on Debian Etch.

This set up interestingly serves around three times more requests per second than apache2 mod_php xcache.

Nginx PHP-FPM Xcache Debian Etch.

debian etch


#ifconfig eth0:1 192.168.1.7
#ifconfig eth0:2 192.168.1.8


restart the networking service

#/etc/init.d/networking restart


By ppepote1

1.- Abrir konsole o gnome-terminal.

2.- Escribir su en el caso de Debian o sudo en caso de Ubuntu.

3.- Introducir la contraseña del super-usuario en el caso de Debian, o la contraseña del usuario en el caso de Ubuntu.

4.- Aparece este signo: #

5.- Para instalar libqt4-core, escribir el siguiente comando despues de ese signo.

6.- aptitude install libqt4-core

7.- Dar a intro enter. Y se instala con todas sus dependencias.

NOTA: Actualizar diariamente, para tener un sistema perfecto, con los siguientes comandos.

aptitude update

aptitude dist-upgrade

Saludos.

Ecco un’immagine per Xen e QEMU (KVM) di Debian Etch:

Debian GNU/Linux è una distribuzione GNU/Linux molto usata, è sviluppata mediante la collaborazione di volontari da ogni parte del mondo. Si tratta di un sistema operativo per computer composto esclusivamente da software libero. L’8 aprile 2007 è stata rilasciata la versione Etch di Debian

http://www.oszoo.org/ftp/images/DebianEtch24112006.zip.torrent

in the passed days i thought of posting but i was busy of setting up a Linux server
i had one running but my HD crashed only the first 100 clusters where us full but the
rest was gone (it was a 80GB HD )…. and back than i fore got to run backups so i lost everything
(database (MySQL) scripts(running on apache2)and same other stuff)
so it’s always was to run backups besides i must admit it’s a freaky way to lose a HD
and before i run a Linux server i had a windows 2k server but that is 5~6 years a go (bakaserv.mine.nu / shadowcore.mine.nu)

any way back to the subject

hardware specification :
CPU : Intel Pentium IV 2530 MHz
internal memory : 1536 MB (3×512MB)
video : ati radian 9250 (256MB)
hd1 : 40 GB (western digital)
optic : DVD-ROM (x4)
lan1 : 10/100 (on board)
lan2 : 10/100 (3com)

i myself am a new to Linux and don’t now much about it but just to say how simple it got
to set one up and i followed the following how to.

The Perfect Server – Ubuntu Hardy Heron (Ubuntu 8.04 LTS Server) – by falko (Contact Author)
is a 7 page how to and it’s simple and self exp lend whit same images to guide you true.
you will get the basics on how to install en get use to the command line (shell).

IPSConfig – by ispconfig.org maual
again pretty simple , follow the install.

ISPConfig 2.x – First Steps (Creating Web Sites, Email Addresses, Etc.) – by o.meyer (Contact Author)
if never seen the inside of ISPConfig than must read. anyways it’s a nice way to guide you true the
web interface end settings

Forced Ads On ISPConfig With Debian Etch – by webcave (Contact Author)
there are many discussions about this but ill keep it sort
(No comment at the moment)

keep in mind that if your running your own server at home on broadband ore adsl
that everything will run local whit out a hitch but if you wont access from the Internet
than u have to configure your router /modem that u still can access your server.
ports you have to keep in mind :

• port 21 (FTP)
• port 22 (ssh – which you need if your running your main PC on windows)
• port 80 (http)
• port 81 (ispconfig control panel (is true http ore https))
• port 443 (https)

The other week I thought I’d upgrade the desktop machine from Debian Etch to Lenny (the testing branch, to be marked stable, well, sometime soon anyway). I was in for some surprises, which I’ll tell you about, but luckily there was a backup at hand, and on the second attempt I had a fairly smooth upgrade. I believe that was still somewhat by chance rather than by any wisdom though, so please don’t do what I describe here!

In imprecise terms, I ran into a problem with (pseudo-)circular dependencies – if packages are upgraded in the wrong order (which should only happen if some of them don’t strictly adhere to best-practices of package management) you may end up with a package in an unconfigured state, while it is needed to upgrade other packages, including the packages on which it itself depends for further configuration.

Or something like that.

Ignorant as I am, I didn’t look into any of the release-critical bugs that still keep Lenny from release, and ran into such a problem with perl. I had no clue why my package manager ground to a halt, and then made things worse by accepting its obviously bad attempts at restoring order – it suggested the removal of a few hundred packages…  and I accepted the suggestion.

Short break for you to stop laughing.

So only then did I go and look for information, and came across this bug report, which probably summarises the problem I had run into. I also found these notes, which could have saved me had I not further borked the upgrade after it got stuck.

What these issues highlight, I think, is what an amazing system we have for package management; despite the tens of thousands of packages in the repositories, which presumably will have highly non-trivial interactions amongst them, problems like this hardly ever occur and in fact it seems they only do occur when mistakes are made in packaging. I cannot imagine how someone has ever managed architecting this system.

In the end I gave up and restored the backup I made just before dist-upgrading. Better prepared this time, I helped the package manager a bit with planning the upgrade: I started by issuing a “dpkg -i perl_5.10.0-13_i386.deb perl-base_5.10.0-13_i386.deb perl-modules_5.10.0-13_all.deb” (from the archives dir, see below) – which didn’t succeed of course, but it did change the order of upgrades sufficiently that this time everything went smoothly. The next two steps were a normal upgrade, then a dist-upgrade (in the new aptitude version these are called safe-upgrade and full-upgrade).

So, my advice then: don’t do as I did, and read up a bit on the task before diving in, and of course run a backup first. In addition, I was happy I had fetched the upgrade-packages in a separate step (if you use aptitude, you can use the “-d” switch for this) – this way at least I didn’t have to load the network again to re-fetch a couple of hundred MBs after restoring the backup. In my case, I had made the packages part of the backup, but there are more efficient ways I suppose. The packages are cached in /var/cache/apt/archives. Have fun!

Untuk mengakses partisi NTFS di Debian Etch ternyata tidak semudah di Ubuntu Linux, Mandriva atau OpenSUSE. Berikut adalah panduan instalasi package NTFS-3g yang memungkinkan kamu mengakses filesystem NTFS. Pertama, download 2 package yakni ntfs-3g dan libntfs-3g. Kamu bisa menggunakan aplikasi wget untuk mengunduh / mendownload kedua package tadi.

wget http://snapshot.debian.net/archive/2007/03/01/debian/pool/main/n/ntfs-3g/libntfs-3g0_0.0.0+20061031-6_i386.deb
wget http://snapshot.debian.net/archive/2007/03/01/debian/pool/main/n/ntfs-3g/ntfs-3g_0.0.0+20061031-6_i386.deb

Selanjutnya, kita menginstal dependensi dengan perintah berikut.

debian:/home/debian# apt-get install fuse-utils libfuse2
Readung package lists … DOne
Building dependency there … Done
The following NEW packages will be istalled : fuse-utils libfuse2
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get OB/108kB of archives.
After unpacking 295kB of additional disk space will be used.
Selecting previously deselected package fuse-utils.
(Reading database … 84862 files and directories currently installed)
Unpacking fuse-utils (from …/use-utils_2.5.3-4.4_i386.deb) …
Selecting previously deselected package libfuse2.
Unpacking libfuse2 (from …/libfuse2_2.5.3-4.4_i386.deb) …
Setting up fuse-utils (2.5.3-4.4) …
creating fuse device node …
udev active, devices will be created in /dev/.static/dev/
creating fuse group …
Adding group ‘fuse’(GID 112) …
Done.
Setting up libfuse2 (2.5.3-4.4) …

Kini, kita menginstall package ntfs-3g (menggunakan 2 package Debian yang telah di unduh sebelum nya).

debian:/home/debian# dpkg -1 libntfs-3g0_0.0.0+20061031-6_i386.deb
Selecting previously deselcted package libntfs-390.
(Reading database … 84884 files and directories currently installed.)
Unpacking libntfs-3g0 (from libntfs-3g0_0.0.0+20061031-6_i386.deb) …
Setting up libntfs-3g0 (0.0.0+20061031-6) …

debian :/home/debian# dpkg -i ntfs-3g_0.0.0+2–61031-6_i386.deb
Selecting previosly deselected package ntfs-3g.
(Reading database … 84893 files and directories currently installed.)
Unpacking ntfs-3g (from ntfs-39_0.0.0+20061031-6_i386.deb)…
Setting up ntfs-3g (0.0.0+20061031-6) …
Setting ntfs-3g suid root with group fuse … done Users from ‘fuse’ group can now mount NTFS volume.

Sejenak kemudian muncul window configuring ntfs.3g . Pilih OK dan tekan Enter. Bagi pengguna Debian Sid, Ubuntu Edgy atau Ubuntu Feisty, kamu tidak perlu mendownload apapun, atau menginstall dependensi. Selanjutnya kita menginstall package ntfs-3g.

# apt-get install ntfs-3g

Mount Partisi NTFS
# mount -t ntfs-39 / dev/sda1 / mnt/windows -o
umask=0,nls=utl8

Perintah di atas akan meng-mount partisi (/dev/sda1, sesuaikan dengan setting komputer kamu) di direktori /mnt/windows, menggunakan character set utf8 (untuk memaksimalkan kompatibilitas) dan menghadirkan permission read/write/execute ke setiap orang.  Jika perintah tadi sudah berjalan di komputer, kamu bisa menambahkan entry ini ke dile /etc/fstab dengan baris perintah sebagai berikut.

/dev/sda1 /mnt/windows ntfs-39
umask=0,nls=utf8 0 0

Untuk meng-umount, perintahnya # umount /dev/sda1 dan perintah fdisk -|| grep -i ntfs akan memberi tahu lokasi partisi Windows.

Essa dica é para instalação no Debian Etch, primeiro vamos baixar o Skype no seguinte endereço :

http://www.skype.com/intl/pt/download/skype/linux/choose/

Selecione a versão Debian Etch.

Será feito o download de um pacote .deb, após isso é só clicar com o botão direito do mouse sobre o pacote e abrir com Gdebi Package Installer.

Abrirá uma nova janela, é só clicar em instalar pacote, aparecerá uma mensagem dizendo que existem duas dependências a serem resolvidas, clique em sim e a instalação será feita.

Após finalizar vá em aplicações/internet/skype, o programa exibirá o contrato, clique em aceitar e agora é só aproveitar!

Hola a tothom,

Ja soc aquí amb un altre tema interesant a comentar sobre linux, i aquest cop es tracta de com treballar amb la controladora SAS (Serial Ata SCSI) LSI 1068 a GNU/Linux i més concretament a Debian Etch. Aquesta controladora, ja té actualment drivers per a gnu/linux, però només per a dos distribucions, en aquest cas de pagament, que són Red Hat i SLES però no per a Debian etch. Abans de començar amb els passos, vull agrair-li tota la ajuda que m’ha donat a l’Adam Cecile que es qui a “purtat” tota la interficie dels drivers de redhat a debian.

Per compilar i instalar aquest driver a debian etch seguirem els passos següents:

Instalem tots els paquetes necessaris per la compilació:

• #> aptitude install linux-image-2.6.18-6-486 (la versió 486 o 686
  dependrà del vostre ordinador) linux-header-2.6.18-6-486
  module-assistant build-essential devscripts

Descarreguem el codi font del mòdul

• #> dget -x http://mentors.debian.net/debian/pool/non-free/
  /m/megasr/megasr_09.21.0914.2007-1.dsc

Accedim al directori del codi font

• #> cd megasr-09.21.0914.2007

Generem el paquet, l’instalem i el compilem

• #>debuild -sa

• #> dpkg -i ../megasr-source*.deb

• #> m-a build megasr -l 2.6.18-4-486 (el 486 també
  depen del vostre kernel)

Instalem el mòdul resultant

• #> dpkg -i /usr/src/megasr-modules-*

Arribats aquest punt, ja hauriem de ser capaços de ‘montar’(mount) cualsevol disk de la controladora. Per fer-ho, primer haurem de carregar el modul:

• #> depmod

• #> modprobe megasr

Ara a /dev ja tindrem els dispositius. Si no heu d’arrancar des del disc de la controladora, serà tan sencill com agefir al modul a /etc/modules per a que us carregui al iniciar. Si al contrari, el que voleu fer es carregar des del disk, haureu de generar un nou initrd amb la següent comanda:

• #> echo "megasr" > /etc/initramfs-tools/initramfs.conf

• #> mkinitramfs -o /boot/initrd.img-2.6.18-6-686 2.6.18-6-686

Arribats aquest punt ja hem conseguit tot el que ens haviem proposat.

Howto LSI 1068 in Debian Etch (megasr)

First we have to install the packages needed for compilation

• #> aptitude install linux-image-2.6.18-6-486
  linux-header-2.6.18-6-486 module-assistant build-essential devscripts

We download the source code

• #> dget -x http://mentors.debian.net/debian/pool/non-free/
  m/megasr/megasr_09.21.0914.2007-1.dsc

We go to the source directory

• #> cd megasr-09.21.0914.2007

We make the package, we install it and we compile the module

• #>debuild -sa

• #> dpkg -i ../megasr-source*.deb

• #> m-a build megasr -l 2.6.18-4-486

We install the compiled module

• #> dpkg -i /usr/src/megasr-modules-*

Now we should be able to access to the attached disks. To do it we have to load the module:

• #> depmod

• #> modprobe megasr

Now in /dev we should see the disks. If you don’t want to boot from this drivers, you only will have to add ‘megasr’ in /etc/modules. If you want to boot from the disks make the following steps:

• #> echo "megasr" > /etc/initramfs-tools/initramfs.conf

• #> mkinitramfs -o /boot/initrd.img-2.6.18-6-686 2.6.18-6-686

So now we have finished!!! I want to thanks a lot to Adam Cecile who has help me a lot to be able to do this! THANKS

If you are interested in trying out open source ILS options our migration may be of interest to you.  We signed a contract with LibLime to migrate to Koha this year.  The contract was for  bibliographic record mapping, training and support for three years.  Our users and circ records are migrating too. We chose Koha because we didn’t have to rebarcode our collection and because Koha will allow us to get our records in an XML format which makes converting them easier into other metadata schema.  We control our records, and that is a good thing. 

Right now we are getting ready to migrate.  We have weekly conference calls with our LibLime assistant and she helps keep us on track with the data collection and matching our old information and classification from Winnebago’s Spectrum 5 to Koha’s. So tomorrow we should have an idea if we are on track for a go live date of Sept. 1. I have a fourteen page check list to complete before we go live. 

We have scheduled a webinar for the 28th of July for a two hour training for the staff.

Our server is sitting outside my office door.  We cannibalized an old Gateway server and upped the ram to 1 Gig. It will do fine for us to start. We also will have a server at a remote location to serve as a virtual server. It will shadow what we are doing on the library server, it will allow us to expand in the future and it also acts as a back up server.

These are the recommended configurations from a Koha  comrade for our server for those of you who like this kinda stuff.

Recommended Hardware specifications for Butte Public Library

Configuration:
  Single Server

Processor:
   Xeon / Opteron Dual Core

Memory:
   4 Gb ECC [6+G preferred] , 8-16 G will give considerable performance boost.

HDD:
  2 * 80 Gb SATA [4 * 40GB preferred], formatted as XFS
  RAID 1 (Mirrored disks) — [ Hardware RAID ]
   
Network:
  Dual GB NICs.

OS:
Debian Etch

Planning for system growth:

The single server configuration above is suitable for the collection and circulation requirements of BPL, giving moderate and stable performance.
Koha’s system requirements can be expected to outgrow this configuration as the number of supported libraries increases.
At this stage, a two- or three-server environment must be implemented, splitting the Zebra indexing engine and/or MySQL RDBMS services from the  application + web server.
These services can be moved to new servers without affecting the core application/web server, thus allowing a relatively seamless hardware upgrade process, continuing to utilize the original server that supported the entire application.

Further considerations:

Koha is comprised of three distinct services, each with its own resource usage profile.
Loosely, they are:
Web + Application services ,  cpu-intensive.
RDBMS (MySQL) service,  memory and disk intensive.
Zebra indexing service,  disk intensive.

Well that’s it for this entry- I’ll be back tomorrow with a progress report.

Lee

Seit einigen Tagen läuft auf meinem Server (Core 2 Quad 6600 mit 4x 2,4GHz und 8GB RAM) eine virtuelle Maschine: Debian Lenny.

Zunächst hatte ich VMware Server 2.0 Beta installiert, das mich wirklich positiv überrascht hat.
Die Weboberfläche des VMware Virtual Infrastructure glänzt durch eine ausgezeichnete Ajax-Oberfläche, die alle paar Sekunden aktualisiert wird, und den selben Funktionsumfang bietet, wie die alte VMware Server Console, über die ich bisher auf VMware Server 1.0 zugegriffen habe.

Ich hatte übers Wochenende einen dedizierten Team Fortress 2 Server mit 24 Spielern laufen, der auch durchgehend voll belegt war – es haben eben viele Menschen die Gelegenheit genutzt, kostenlos in TF2 reinschnuppern zu können.
Dieser lief absolut lagfrei und belastete einen Kern des Core 2 Quad mit rund 70%.
Die Pingzeiten waren traumhaft und insgesamt war die Performance wirklich in Ordnung.

Es störte nur etwas, dass die Vmware Server 2.0 Beta standardmäßig im Debug-Modus lief.
Hier wird ein ziemlicher Teil der Performance verschenkt.

Und genau aus diesem Grund wechselte ich gerade eben zu VMware Server 1.06.
Die Installation lief nicht ganz fehlerfrei ab, da ich einen amd64-Kernel fahre.

Es tauchten mehrere kleine Fehlermeldungen währen der Konfiguration über das Perlscript vmware-configure.pl auf – auch mein Serial wurde nicht akzeptiert!
Die Ursache war ganz einfach, dass einige Teile des VMware-Setups nur in einer 32bit-Umgebung funktionieren.
Nach der Installation des Paketes ia32-libs konnte die Installation dann abgeschlossen werden – und auch mein Serial wurde akzeptiert .

Das schöne Webinterface habe ich jetzt zwar nicht mehr, dafür kann ich über die VMware Server Console auf die virtuelle Maschine zugreifen.

To be continued…

#20080620

#Please note: Thank you to the people who was talking here about the gtk-engines and for their links and feedbacks.

#Please note: This is working in progress and, as usual, I am in a hurry. If you think these informations are wrong write a note. If they work for you leave a note too (if you want to…of course ).

#Please note: These engines require gtk+ version 2.12.0 or later. So I think you will have troubles if you want to use them with older versions of gtk+.

#Please note: These notes are my starting point.

1st Section : Build the gtk-engines-2.15.1 and install them as a non-root user

1. Install through aptitude/synaptic some of the packages the gtk-engines-2.15.1 depends upon. Here is the list of what I had to install (do you think we can slim it down ?):
   • The package intltool. All its dependencies are handled automatically.
2. Choose a folder/subfolder in the home directory where the gtk-engines will be installed. I will call it <folderofchoice> from now on. I chose the folder where in the previous post I installed all the libraries and binaries related to the gtk+ package. But you can choose it your way.
3. Fetch and install the package gtk-engines-2.15.1. I did this step as a non root user, with its drawbacks. But I like it and it s convenient to my system.
   • Open a console.
   • Unzip and untar the package somewhere in the home folder.
   • Change the current working directory to the main gtk-engines package directory.
   • Modify the environment variable PKG_CONFIG_PATH so that its content is the path to gtk+ 2.12.10’s pkgconfig directory. Oh, well here we go if you are using BASH :
     export PKG_CONFIG_PATH=$HOME/<folderofchoice>/lib/pkgconfig.
   • Modify the environment variable LD_RUN_PATH so that its content is the path to the gtk+ 2.12.10’s libraries. If you are using BASH here is the command
     export LD_RUN_PATH=$HOME/<folderofchoice>/lib
   • Execute the script configure located in the gtk-engines main folder. I had to pass configure the following parameter –prefix=$HOME/<folderofchoice> so that the gtk-engines could be completely rooted to <folderofchoice>. The command was the following : ./configure –prefix=$HOME/<folderofchoice>.
   • Execute the command make install. After that you should have gtk-engines-2.15.1 built and rooted in a subfolder of $HOME/<folderofchoice>. To test this you can ls the contents of $HOME/<folderofchoice>/lib/gtk-2.0.

   Okay, you are done. The engines and also some themes are there, here is the list (as my configure says..) :

   • ClearLooks
   • Crux
   • HC
   • Industrial
   • Mist
   • Redmond
   • Glide
   • Smooth
   • ThinIce

   and you can use them, but how ? First, as I understand, it is good to know that the engines are used by control options and lay on bottom of them. For our purposes we will be using the themes/control options and we will not be using directly the engines.

#Please note: I am not an expert in this field, so sorry if I lack of terminology.

2nd Section : Configuring and Using those themes in your gtk+ applications (i.e. Firefox 3).

Way one – Do it by hand (not that ! )

Two different goals we can reach.

• Goal 1 – Set the aspect of EVERY gtk application in the system (not recommended)
  #Please note: this is not recommended because as of my tests here the new themes do not work fine if some of your applications are still using the “old” gtk+s libraries and, also, some of these themes we just installed do not contain informations about windows borders or icons.
  • Open for writing the file .gtkrc-2.0, that is located in your home folder, with a (simple) text editor. If this file does not exist, create it.
  • There should exist a line like this:
    include “…./themes/….”
  • (If you found a line like that, comment it out with a # and) add this new line, replacing the missing informations and always according to your installation:
    include “<full_path_to_folder_of_choice>/<folderofchoice>/
    share/themes/<theme_name>/gtk-2.0/gtkrc”
  • Launch a gtk application. Its controls have a “new style”.

  is it working ?

• Goal 2 – Set the aspect of a SINGLE gtk application in the system (i.e. Firefox 3)
  #Please note: this is good I think if you want only a specific (or set of specific) application(s) make use of the new engines.
  • Think of a name. Let’s suppose it to be <mygtkrc>.
  • Create the file ~/.<mygtkrc> and open it for writing. (If that file alreadys exist Think of another name).
  • add this new line to ~/.<mygtkrc> (adding the missing informations and always according to your installation):
    include “<full_path_to_<folder_of_choice>>/<folderofchoice>/
    share/themes/<theme_name>/gtk-2.0/gtkrc”
  • Create a (wrapper) script (if you already have one for this application modify it) somewhere in the home folder, replacing the missing informations:
    #!/bin/sh
    export GTK2_RC_FILES=$HOME/.<mygtkrc>
    <full_path_to_the_gtk_application_you_want_to_wrap>/<x_application_name>
  • Launch the SCRIPT. The application controls have a “new style”.

  is it working ?

Way two – Do it with software products

<STUB_NOT_DONE>

3rd Section : Icon themes for firefox 3.

Once you are done with the gtk theme customization of Firefox (as explained before) you can choose an “icon theme” (I mean a theme that preserves the current gtk theme) for Firefox and install it.

[I hope I can collect links to themes for Firefox 3 which are not too intrusive. If you know of any nice theme send the link and I will update the following list.]

Here is the first, In my opinion it is very nice !

1. Phoenity ;

d

#20080610#20080626#20080827

#Please note: It’s many months now that I wrote these steps. Libraries may have changed and I did not update the links. So you have two choices :

- directly follow the links I wrote: in this case these instructions will help you but you will have slightly old libraries.

- search for new versions of the libraries: if something has changed these instructions will not be able to cover the new subject.

anyways, choose as you like

Another note: Lenny is about to be released …  I suppose we will have iceweasel version 3 by default .

#Please note : this _is_ and _will remain_ work in progress. Before executing the steps think of what I wrote : I am in a hurry and the informations lack of completeness here and there. Any suggestions/corrections are welcome. At present it seemed they worked fine for many people.

#Please note: Every change to the environment variables described here vanishes if you do not store it somewhere (i.e. bashrc or something).

#Please note : some steps need root privileges. I installed all the libs as a non-root user . if you want to do it differently modify the steps according to your taste.

#Please note: I just found a writing about the use of LD_LIBRARY_PATH. And it is a bit “scary”… See http://www.eyrie.org/~eagle/notes/rpath.html . Setting the value of LD_LIBRARY_PATH influences all our next compilations and execution of programs that use the libraries we are going to install- it’s useful to remember this. So do we need to change something in the following lines ? Do we need to compile FireFox from source and link everything statically ?? Suggestions greatly appreciated. UPDATE: Okay, thank to that page, I found the solution, that is explained in the 2nd section.

1st Section – Build the libraries gtk+ 2.12 and install them as a non-root user.

1. Install through aptitude/synaptic some of the packages gtk+2.12 depends upon. Here is the list of what I had to install (do you think that we can slim down this list ?) :
   • The package xorg-dev. All its dependencies are handled automatically.
   • The package libtiff4-dev. All its dependencies are handled automatically.
   • The package libpng12-dev. All its dependencies are handled automatically.
   • The package libpango1.0-dev. All its dependencies are handled automatically.
   • The package libatk1.0-dev. All its dependencies are handled automatically.
   • The package libgtk2.0-dev. All its dependencies are handled automatically.
   • The package gettext. All its dependencies are handled automatically.
   • The package libxul-dev. All its dependencies are handled automatically. (NEW)
2. Choose a folder/subfolder in the home directory where all the libraries,binaries man pages will be installed. I will call it <folderofchoice> from now on.
3. Fetch and install the package glib 2.16. I did this step as a non root user, with its drawbacks. But I like it and it s convenient to my system.
   • Open a console.
   • Unzip and untar the package somewhere in the home folder.
   • Change the current working directory to the main glib package directory.
   • Execute the script configure located in the glib 2.16 main folder. I had to pass configure the following parameter –prefix=$HOME/<folderofchoice> so that glib could be completely rooted to <folderofchoice>. The command was the following : ./configure –prefix=$HOME/<folderofchoice>.
   • Execute the command make install. After that you should have glib 2.16 built and rooted at $HOME/<folderofchoice>. To test this you can ls the contents of $HOME/<folderofchoice>.
4. Fetch and install the package pango 1.20. I did this step as a non root user, with its drawbacks. But I like it and it s convenient to my system. Please note that pango 1.20 requires glib 2.14 or newer. Glib 2.12.4 is installed system-wide so We must tell pango to use the glib 2.16 we installed in the previous step. Look :
   • Open a console.
   • Unzip and untar the package pango 1.20 somewhere in the home folder.
   • Change the current working directory to the main pango package directory.
   • Modify the environment variable PKG_CONFIG_PATH so that its content is the path to glib 2.16’s pkgconfig directory. Oh, well here we go if you are using BASH :
     export PKG_CONFIG_PATH=$HOME/<folderofchoice>/lib/pkgconfig.
   • Modify the environment variable LD_RUN_PATH so that its content is the path to the newly installed libraries. If you are using BASH here is the command
     export LD_RUN_PATH=$HOME/<folderofchoice>/lib .
   • Execute the script configure located in the pango 1.20 main folder. I had to pass configure the following parameter –prefix=$HOME/<folderofchoice> so that pango could be completely rooted to <folderofchoice>. The command was the following : ./configure –prefix=$HOME/<folderofchoice>.
   • Execute the command make install. After that you should have pango 1.20 built and rooted at $HOME/<folderofchoice>. To test this you can ls the contents of $HOME/<folderofchoice>.
5. Fetch and install the package gtk+2.12 . I did this step as a non root user, with its drawbacks. But I like it and it s convenient to my system. Please note that gtk+2.12 requires glib 2.14 or newer. Glib 2.12.4 is installed system-wide so We must tell gtk+2.12 to use the glib 2.16 and pango 1.20 we installed in the previous steps.
   • Open a console.
   • Unzip and untar the package gtk+2.12 somewhere in the home folder.
   • Change the current working directory to the main gtk+ package directory.
   • Modify the environment variable PKG_CONFIG_PATH so that its content is the path to glib 2.16’s pkgconfig directory. Oh, well here we go if you are using BASH :
     export PKG_CONFIG_PATH=$HOME/<folderofchoice>/lib/pkgconfig.
   • Modify the environment variable LD_RUN_PATH so that its content is the path to the newly installed libraries. If you are using BASH here is the command
     export LD_RUN_PATH=$HOME/<folderofchoice>/lib .
   • Execute the script configure located in the gtk+2.12 main folder. I had to pass configure the following parameter –prefix=$HOME/<folderofchoice> so that gtk+ could be completely rooted to <folderofchoice>. The command was the following :
     ./configure –prefix=$HOME/<folderofchoice>.
   • At this point you should have configured the gtk package. One problem arises. In my system if I next give the command ‘make’ the build process stops complaining libtool has an invalid argument. A temporary workaround is the following.
     • Open with a text editor the Makefile located in the gtk+2.12 main folder.
     • Search for the word ‘tests’ and delete it. The result is that the gtk tests will not be built but the package will be built correctly. I hope I can find the correct fix, anyways.
   • Execute the command make install. After that you should have gtk+2.12 built and rooted at $HOME/<folderofchoice>. To test this you can list the contents of $HOME/<folderofchoice>.

   That’s it ! You should have everything set up to run Firefox 3. Let’s try it !

2nd Section – Fetch and install Firefox 3.

1. Fetch the Firefox 3 binary package that you like the most and execute it making sure that the environment variable LD_LIBRARY_PATH stores the path to the newly installed libraries.
   • Open a console.
   • Unzip and untar the package firefoxXXX somewhere in the home folder.
   • Change the current working directory to the main firefoxXXX package directory.
   • Now, you can fallow one of two ways :
     Way one
     #Please Note: this way the scope of LD_LIBRARY_PATH is the whole shell environment.
     • Modify the environment variable LD_LIBRARY_PATH so that its content is the path to the newly installed libraries. If you are using BASH here is the command
       export LD_LIBRARY_PATH=$HOME/<folderofchoice>/lib .
     • Run the local copy of Firefox 3. Here is the command : ./firefox. It is important that you tell the shell to run the local copy of firefox otherwise the “system wide” firefox will be executed.

     Way two (I think “safer”)
     #Please Note: this way the scope of LD_LIBRARY_PATH should be only the program we are executing, not system wide scope.

     • Create a wrapper script that has the following 3 lines (sorry, I had to cut the “export” in 2 lines). NOte: this is a very basic script. I mean I am just passing one parameter to the “real” firefox (i.e. an URL). To allow more complex situations you have to modify it.
       #!/bin/sh
       export LD_LIBRARY_PATH
       =$LD_LIBRARY_PATH:$HOME/<folderofchoice>/lib
       <full_path_firefox_folder>/firefox $1
     • Save the script with a non-conflicting-name that you like in the main firefoxXXX package folder (the current folder, if you followed the steps). Let’s suppose to call the script startfox.
     • Change the permission of the script so that it can be executed :
       chmod u+x ./startfox
     • Run the script startfox.
   • is it running ?

Here are some notes about the customization of the gtk theme

Linked articles (thanks to the senders) :

• http://ddesani.blogspot.com/2008/06/firefox-3-debian-etch.html (Portuguese)
  
  

cheers !

d

Pidgin é um excelente client de mensagens instantâneas, que suporta os mais conhecidos protocolos (e os não tão conhecidos também), tais como: MSN, Google Talk, IRC, ICQ, Yahoo!, AIM, XMPP dentre muitos outros.

Vou descrever como instalar a última versão do Pidgin, já que a que está nos repositórios do Etch é véia pakas =p

Primeiramente é necessário a instalação de algumas dependências: aptitude install libxml-parser-perl libgtk2.0-dev libxml2-dev libgnutls-dev libstartup-notification0-dev libgstreamer0.10-dev libgtkspell-dev libmeanwhile-dev libavahi-glib-dev libdbus-1-dev libdbus-glib-1-dev network-manager-dev libperl-dev tcl8.4-dev tk8.4-dev

Agora baixe o fonte do pidgin diretamente do site: http://www.pidgin.im/download/source

Descompacte o arquivo com o comando tar -jxf pidgin-2.2.0.tar.bz2 e entre no diretório criado.

Crie o Makefile para compilação com o comando: ./configure

Para compilar e instalar o programa: make && make install

Agora basta reiniciar seu gerenciador de janelas que o pidgin estará no menu Aplicações. =D

On the subject of social sites, my current aim is to develop a freely available core social network. To be able to do so, I did some online search. I begun with a search for a Bulletin Board System based on Rails. But I didn’t go into depth until now.

What I found somtime amidst it was a book on developing a social network using Rails. Unfortunately, only some teasers of that book are available online.

Aside of that Rails stuff, there are some news available on the subject of social networks:

1. Nick O’Neill tells us about Word Press x Buddy Press: “BuddyPress will completely transform a vanilla installation of WordPress MU into a fully functional social network platform.”
2. Google’s David Glazer serves some background insight into “Google’s” OpenSocial and where to go.
3. Finally, at TechCrunch I found some figures on the user base sizes of Facebook, MySpace, Ning and others.

And a more or less personal note: My Rails box got broken lately, and until now I was unable to set up an alternative: There were some hassles doing so on a Debian Etch and, unfortunately too, the works-like-a-breeze tutorial of how to install Rails on a Debian Etch box did not work. (I might post a solution for this issue explicitly, soon.)