Installare applicazioni per kde

./configure --prefix=`kde-config --prefix`
make
make install

in caso di errori, se non trova Qt aggiungere:
--with-qt-dir=$QTDIR --with-qt-libraries=$QTDIR/lib --with-extra-libs=$QTDIR/lib
opuure a mano
--with-qt-dir=/usr/lib/qt-3.3 --with-qt-libraries=/usr/lib/qt-3.3/lib --with-extra-libs=/usr/lib/qt-3.3/lib --with-qt-include=/usr/lib/qt-3.3/include

Fedora 7 like mac osx with baghira

Ecco come fare:

yum install kdelibs-devel kdebase-devel libXtst-devel rpm-build

wget http://www.kde-look.org/CONTENT/content-files/59592-baghira.spec
mv 59592-baghira.spec /usr/src/redhat/SPECS/baghira.spec

wget http://mesh.dl.sourceforge.net/sourceforge/baghira/baghira-0.8.tar.bz2
mv baghira-0.8.tar.bz2 /usr/src/redhat/SOURCES

cd /usr/src/redhat/SPECS/
rpmbuild -bb baghira.spec

cd ../RPMS/i386/
rpm -Uhv baghira-0.8-1.i386.rpm

Adesso nel pannello di controllo di kde possiamo scegliere baghira come
tema e decorazione.

Saluti

Fedora java runtime engine jre e java development kit jdk e firefox plugin

Installo i pacchetti necessari:
yum install compat-libstdc++-296.i386 compat-libstdc++-33.i386
Installiamo la jre e la jdk
Andiamo su
http://java.sun.com/javase/downloads/index.jsp
e scarichiamo la jdk (ultima versione formato rpm)

chmod ugo+x jdk-6u1-linux-i586-rpm.bin
./jdk-6u1-linux-i586-rpm.bin
rispondere yes per accettare la licenza

[root@trinity2 ~]# ls /usr/bin/java -la
lrwxrwxrwx 1 root root 22 12 giu 20:56 /usr/bin/java ->
/etc/alternatives/java
[root@trinity2 ~]# ls -la /etc/alternatives/java
lrwxrwxrwx 1 root root 35 12 giu 20:56 /etc/alternatives/java ->
/usr/lib/jvm/jre-1.5.0-gcj/bin/java
[root@trinity2 ~]# rm /etc/alternatives/java
rm: rimuovere link simbolico `/etc/alternatives/java'? y
[root@trinity2 ~]# ln -s /usr/java/jdk1.6.0_01/bin/java
/etc/alternatives/java

[root@trinity2 ~]# java -version
java version "1.6.0_01"
Java(TM) SE Runtime Environment (build 1.6.0_01-b06)
Java HotSpot(TM) Client VM (build 1.6.0_01-b06, mixed mode, sharing)

adesso abilitiamo il plugin per firefox
[root@trinity2 ~]# ln -s
/usr/java/jdk1.6.0_01/jre/plugin/i386/ns7/libjavaplugin_oji.so
/usr/lib/firefox-2.0.0.4/plugins/

Beryl su Fedora 7

Dopo aver risolto i problemi della scheda video (v. post precedente - che però segue questo :-) )
ho installato beryl

yum install beryl-kde

con questo cmd mi ha installato tutte le dipendenze e i pacchetti necessari

beryl-core.i386
beryl-kde.i386
beryl-manager.i386
beryl-plugins.i386
beryl-settings.i386
beryl-settings-simple.i386

A questo punto per attivare beryl non devo far altro che lanciare
beryl-manager

Per configurare beryl:
http://lunapark6.com/?p=2916&cp=3

Se si vuole lanciarlo in automatico... consiglio il seguente link.

Automatic installation of XGL, compiz and beryl on Fedora

http://nicofo.tuxfamily.org/dotclear/index.php/2007/02/23/25-automatic-installation-of-xgl-compiz-and-beryl-on-fedora

Fedora 7 nvidia driver e direct rendering problem

Oggi ho provato a installare i driver nvidia abilitando il direct rendering
non ce l'ho fatta.
Ho provato di tutto, ma l'installazione tramite i pacchetti rpm e yum
non ha dato nessun risultato.
Ogni volta che provavo il comando
glxinfo | grep rend

ottenevo
direct rendering: No

Alla fine, stufo e quasi rassegnato mi sono deciso e ho fatto
l'installazione manuale.
Ecco i passi necessari:

Scarico
http://us.download.nvidia.com/XFree86/Linux-x86/100.14.09/NVIDIA-Linux-x86-100.14.09-pkg1.run

poi un bel

telinit 3

yum remove kmod-nvidia.i686
yum install kernel-devel gcc

chmod ugo+x NVIDIA-Linux-x86-100.14.09-pkg1.run

./NVIDIA-Linux-x86-100.14.09-pkg1.run

seguo i passi necessari

quando ha finito ho dato un bel telinit 5

e.... magia...

glxinfo | grep rend
direct rendering: Yes
OpenGL renderer string: GeForce Go 7300/PCI/SSE2

Rimborso per Windows preinstallato, il parere dell'Aduc

Fonte: http://attivissimo.blogspot.com/2006/08/rimborso-windows-garante-sancisce.html

Questo articolo vi arriva grazie alle gentili donazioni di "foucault66" e "f.graniglia".

L'Aduc ha pubblicato oggi un comunicato a proposito della controversia sul diritto negato al rimborso per Windows preinstallato e non utilizzato, come previsto da una poco nota clausola della licenza Microsoft. La questione (e il mio successo nell'ottenere il rimborso, seguito da quello di pochi altri testardi) è raccontata in dettaglio nella mia pagina apposita.

L'associazione di consumatori aveva denunciato Microsoft all'Autorità Garante della Concorrenza e del Mercato per abuso di posizione dominante, proprio perché è praticamente impossibile acquistare un PC senza Windows preinstallato (specialmente nel settore dei portatili e la clausola di rimborso prevista nella licenza viene sistematicamente boicottata da rivenditori e produttori. In questo senso, anzi, Aduc ha citato in giudizio HP e ha predisposto un modulo per la richiesta di rimborso.

Il comunicato Aduc di oggi cita la risposta dell'Autorità Garante, che non sono riuscito a trovare sul sito del Garante ma che secondo ADUC è in una "lettera 28300/06 del 27/7/2006" nell'ambito del procedimento DC/5073 (sarebbe interessante leggerla per intero, ho già chiesto all'Aduc):

...L'Autorità, dopo la seduta dello scorso 20 luglio 2006, ci ha comunicato che secondo lei questo abuso non c'è: per Microsoft l'Autorità ritiene che quanto da noi segnalato non vi è riferibile, ma lo sarebbe per le imprese produttrici di hardware che pre-installano Windows nei computer. "Dalle informazioni raccolte –continua l'Autorita' garante della Concorrenza e del Mercato- è inoltre emerso che sul mercato vi sono imprese che offrono prodotti che non installano tale sistema operativo e che comunque i consumatori possono rifiutare l'installazione di Windows e ricevere un rimborso".

Microsoft non è colpevole, insomma, ma lo sono i rivenditori e i produttori che non consentono l'applicazione corretta della licenza. Al tempo stesso, le parole del Garante ribadiscono il diritto del consumatore a ricevere un rimborso.

Aduc riassume lucidamente il problema del rimborso. A parte la faccenda di arricchire ulteriormente Microsoft con un prodotto che il consumatore non vuole (perché vuole installare Linux o ha già una licenza valida di Windows) ma è costretto a pagare,

i consumatori vorrebbero poter scegliere "UN PC SENZA SISTEMA OPERATIVO" alla stregua di "UN VASO SENZA FIORI"; o perlomeno, i fiori vorrebbero poterli scegliere da soli!

Parole sante.

Intel ipw3945 on Fedora 7

Intel ipw3945 on Fedora 7

---

Taken from the following website link. Copied and pasted hence the layout.

http://forums.fedoraforum.org/showthread.php?p=805589#post805589
http://fedoramobile.org/Members/ops...45-on-fedora-7/

This howto will show you how to blacklist/remove iwl3945 / mac80211 in Fedora 7 and install / use the "known working" ipw3945 kernel module / driver, microcode firmware, regulatory daemon and startup init script. For this you will need to have root privileges and have roots path/environment.

Applicable to Fedora Versions

* Fedora Core 7

Requirements
Explanation of requirements.

1. kernel-devel (kernel development files for building modules against the running kernel)
2. gcc (C++ compiler)
3. ipw3945-1.2.1.tgz (driver / kernel module)
4. ipw3945-ucode-1.14.2.tgz (microcode / firmware)
5. ipw3945d-1.7.22.tgz (regulatory daemon)
6. ipw3945 (startup init script)

Doing the Work

Basic description of what will be done and what is expected. Learn to become root here.

1. Blacklisting the offending modules:

Code:

#nano /etc/modprobe.d/blacklist

add these exact lines at the bottom then save and exit:

Code:

# iwl3945  blacklist iwl3945    blacklist mac80211

2. Reboot the system:

Code:

#] reboot

3. Create a temp directory on your desktop called 'ipw3945' and download the following files into it:

Code:

 $] mkdir /home/$user/Desktop/ipw3945 (replace $user with your username)

http://prdownloads.sourceforge.net/....1.tgz?download
http://bughost.org/ipw3945/ucode/ip...code-1.14.2.tgz
http://bughost.org/ipw3945/daemon/ipw3945d-1.7.22.tgz
http://fedoraos.org/ipw3945/ipw3945

4. Install kernel development packages and gcc compiler:

Code:

#] yum install kernel-devel gcc

5. Unpack the gzipped tarballs into the directory on your desktop called 'ipw3945' that we created earlier:

Code:

$] tar xvfz ipw3945-1.2.1.tgz     
$] tar xvfz ipw3945-ucode-1.14.2.tgz     
$] tar xvfz ipw3945d-1.7.22.tgz

6. Copy ucode firmware and regulatory daemon to their respective locations:

Code:

cp ipw3945-ucode-1.14.2/ipw3945-ucode /lib/firmware
cp ipw3945d-1.7.22/ipw3945d /sbin

(or choose the version for x86_64 if necessary)

7. Compile and copy the resuling kernel module to the correct location (for more options here see 'more information' below):

Code:

 $] cd ipw3945-1.2.1 && make    
$] su --login     
#] cp /home/$user/Desktop/ipw3945/ipw3945-1.2.1/ipw3945.ko /lib/modules/2.6.21-1.3212.fc7/kernel/drivers/net/wireless/     
#] chmod 744 /lib/modules/2.6.21-1.3212.fc7/kernel/drivers/net/wireless/ipw3945.ko
#] depmod -ae

8. Install startup init script:

Code:

#] cp /home/$user/Desktop/ipw3945/ipw3945 /etc/init.d     
#] chmod +x /etc/init.d/ipw3945     
#] chkconfig --add ipw3945 && chkconfig ipw3945 on

9. Reboot the system:

Code:

#] reboot

Troubleshooting
How to test
Explanation troubleshooting basics and expectations.

1. Configure the device:

Code:

 #] system-config-network

new --> wireless connection --> Intel Corporation PRO/Wireless 3945ABG Network Connection --> forward

2. Restart the network:

Once you have disabled all other network cards, configured your ip address, gateway, DNS, subnet mask,
SSID, wifi channel, and encryption key:

Code:

 # service network restart

Common problems and fixes

Many laptops with built in wireless have a WLAN switch that is a toggle switch for enabling/disabling the wireless radio.

Please make sure you check this is on, or your ipw3945 wireless adapter will not detect correctly or work at all.

Also, disable all other network cards before attempting to use the ipw3945.
More Information

Special Notes:

If you'd like Monitor Mode, Promiscuous Mode or RadioTap enabled for this device you will need to edit the Makefile in

Step 7 before compiling the kernel module uncomment the corresponding line(s):

Code:

 CONFIG_IPW3945_MONITOR=y
CONFIG_IEEE80211_RADIOTAP=y
CONFIG_IPW3945_PROMISCUOUS=y 

Added Reading

* http://fedoraos.org

Fedora e Acrobat Reader - expr: errore di sintassi

Ho installato Acrobat Reader AdobeReader_ita-7.0.8-1.i386.rpm preso dal
sito Adobe.
Quando lo lancio, ottengo questo errore:
||

$ acroread

expr: errore di sintassi
expr: errore di sintassi
expr: errore di sintassi
...

all'infinito, finché non premo ctrl+c

SOLUZIONE:
A chi mai servisse, ho trovato la soluzione in rete in questo forum:
Link:
<https://fcp.surfsite.org/modules/newbb/viewtopic.php?topic_id=26864&forum=12&post_id=114769>

In pratica, bisogna aprire lo script /usr/bin/acroread e fare le
seguenti sostituzioni:
||

418# echo $mfile| sed
's/libgtk-x11-\([0-9]*\).0.so.0.\([0-9]\)00.\([0-9]*\)\|\(.*\)/\1\2\3/g'
419 echo $mfile| sed
's/libgtk-x11-\([0-9]*\).0.so.0.\([0-9]*\)00.\([0-9]*\)\|\(.*\)/\1\2\3/g'

644# MIN_GTK_VERSION="240"
645 MIN_GTK_VERSION="2040"

I numeri all'inizio sono i numeri di riga...
In realtà, a me bastava solo la prima delle due.
C'era un errore di sintassi nella riga di sed.

Usiamo vim di default su fedora

Come fare in modo che vi corrisponda a vim

Iniziamo:
yum -y update

VI=VIM

vi /etc/profile.d/vim.sh

It should look like this:

if [ -n "$BASH_VERSION" -o -n "$KSH_VERSION" -o -n "$ZSH_VERSION" ]; then

[ -x /usr/bin/id ] || return

[ `/usr/bin/id -u` -le 100 ] && return

# for bash and zsh, only if no alias is already set

alias vi >/dev/null 2>&1 || alias vi=vim

fi

Add a # sign in front of lines 2 and 3, so that it looks like this:

if [ -n "$BASH_VERSION" -o -n "$KSH_VERSION" -o -n "$ZSH_VERSION" ]; then

# [ -x /usr/bin/id ] || return

# [ `/usr/bin/id -u` -le 100 ] && return

# for bash and zsh, only if no alias is already set

alias vi >/dev/null 2>&1 || alias vi=vim

fi

Link utili per l'installazione e configurazione di Fedora

Riferimenti:
http://www.freespamfilter.org/FC4.html
http://wiki.dovecot.org/DovecotLDAPostfixAdminMySQL
http://postfix.pentachron.net/
http://wiki.dovecot.org/FrontPage?highlight=%28%28DovecotLDAPostfixAdminMySQL%29%29
http://flakshack.com/anti-spam/wiki/index.php?page=Installing+Needed+Perl+Modules
http://www.hostingsoftware.net/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=56
ftp://ftp.esat.net/mirrors/ftp.porcupine.org/mirrors/postfix-release/index.html
http://www.maiamailguard.com/maia/wiki/Install
http://download.fedora.redhat.com/pub/fedora/linux/core/development/source/SRPMS/

--  principio di Napoleone: non attribuire a malintenzione cio' che puo' essere semplicemente spiegato come imbecillita' MaoX Blog: Problemi e soluzioni di un sistemista informatico: http://maox.blogspot.com

Dovecot con supporto mysql su fedora - creare il proprio rpm

DOVECOT con supporto mysql 

La stessa cosa vista x postfix la si può fare x Dovecot: 
wget http://download.fedora.redhat.com/pub/fedora/linux/core/development/source/SRPMS/dovecot-1.0-2.rc17.fc7.src.rpm 
rpm -Uhv dovecot-1.0-2.rc17.fc7.src.rpm 
wget http://www.dovecot.org/releases/dovecot-1.0.rc22.tar.gz 
cp dovecot-1.0.rc22.tar.gz /usr/src/redhat/SOURCES/ 
cd /usr/src/redhat/SPECS 
vi dovecot.specs 
cambio  
%define build_postgres 0 
Release .......   
yum install gettext-devel  
rpmbuild -ba dovecot.specs 
rpmbuild -bb dovecot.specs  
cd /usr/src/redhat/RPMS/i386/  
rpm -Uhv ./dovecot-*   
Seguo  http://wiki.dovecot.org/DovecotLDAPostfixAdminMySQL

Postfix con supporto mysql su fedora - creare il proprio rpm

Postfix con supporto mysql su Fedora

Get the latest source rpm fromFedora Core Developmentand install it
or here:
http://download.fedora.redhat.com/pub/fedora/linux/updates/7/SRPMS/

(Note: the src.rpm not the i386.rpm) with:

rpm -Uvh postfix-2.3.x-1.src.rpm   

If it still not the latest get the latest source from any of thePostfix Download Siteand put int into
rpm/SOURCES/ directory. In postfix.spec modify the version and add MySQL support (%define MYSQL 1) and build it:

rpmbuild -ba postfix.spec
rpmbuild -bb postfix.spec

Cioè:
scarico l'RPM con i sorgenti,
poi scarico l'ultima versione di postfix e lo installo
Tutto va a finire in /usr/src/redhat/SOURCES/
qui sostituisco
postfix-2.3.6.tar.gz
con
postfix-2.3.7.tar.gz
poi in
/usr/src/redhat/SPECS/
modifico
postfix.spec
%define MYSQL 1 Version: 2.3.7
e poi lancio
rpmbuild -ba postfix.spec
rpmbuild -bb postfix.spec
in
/usr/src/redhat/RPMS/i386
trovo i pacchetti RPM  e quindi
cd /usr/src/redhat/RPMS/i386
rpm -Uhv ./*

FATTO!!!!

[da http://dailypackage.fedorabook.com/index.php?/archives/6-Wednesday-Why-The-Alternatives-System.html]

To select one of these two packages interactively, the alternatives command is used with the --config option and the generic name of the feature that is being configured:

# alternatives --config mta

There are 2 programs which provide 'mta'.

Selection Command
-----------------------------------------------
*+ 1 /usr/sbin/sendmail.sendmail
2 /usr/sbin/sendmail.postfix

Enter to keep the current selection[+], or type selection number:

Note that the highest-priority alternative is marked with an astrisk (*), and the currently-selected option is marked with a plus-sign (+). Press enter to keep the current setting or enter a number to select another value.

To select an alternative directly from the command line, use the --set option:

# alternatives --set mta /usr/sbin/sendmail.postfix

You can see the current value by using the --display option:

# alternatives --display mta
mta - status is manual.
link currently points to /usr/sbin/sendmail.sendmail
/usr/sbin/sendmail.sendmail - priority 90
slave mta-pam: /etc/pam.d/smtp.sendmail
slave mta-mailq: /usr/bin/mailq.sendmail
slave mta-newaliases: /usr/bin/newaliases.sendmail
slave mta-rmail: /usr/bin/rmail.sendmail
slave mta-sendmail: /usr/lib/sendmail.sendmail
slave mta-mailqman: /usr/share/man/man1/mailq.sendmail.1.gz
slave mta-newaliasesman: /usr/share/man/man1/newaliases.sendmail.1.gz
slave mta-aliasesman: /usr/share/man/man5/aliases.sendmail.5.gz
slave mta-sendmailman: /usr/share/man/man8/sendmail.sendmail.8.gz
/usr/sbin/sendmail.postfix - priority 30
slave mta-pam: /etc/pam.d/smtp.postfix
slave mta-mailq: /usr/bin/mailq.postfix
slave mta-newaliases: /usr/bin/newaliases.postfix
slave mta-rmail: /usr/bin/rmail.postfix
slave mta-sendmail: /usr/lib/sendmail.postfix
slave mta-mailqman: /usr/share/man/man1/mailq.postfix.1.gz
slave mta-newaliasesman: /usr/share/man/man1/newaliases.postfix.1.gz
slave mta-aliasesman: /usr/share/man/man5/aliases.postfix.5.gz
slave mta-sendmailman: /usr/share/man/man1/sendmail.postfix.1.gz
Current `best' version is /usr/sbin/sendmail.sendmail.

Instead of selecting the alternative manually, you can choose to have the highest-priority option automatically selected. This will enable an automatic change as packages are added and removed:

# alternatives --auto mta

The most common use of the alternatives system is to select between implementations of Java, the print server, and the mail transfer agent. Fedora's implementation of alternatives is a rewrite and extension of the alternatives system used in Debian.

(Why is the generic name linked to a name in /etc/alternatives which is symlinked to the target, instead of the generic name being directly symlinked to the target? This was done so that the configuration information is contained in the /etc directory, centralizing the location of configuration data).

Windows 2000 non vede il disco superiore a 137GB

Windows 2000 non vede il disco superiore a 137GB
A me riconosceva un disco da 250GB com uno da 128GB

SOLUZIONE:

http://support.microsoft.com/default.aspx?scid=kb;en-us;q305098

Occorre creare la seguente chiave di registro:
In
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Atapi\Parameters

Value name: EnableBigLba
Data type: REG_DWORD
Value data: 0x1

riavviare e tutto funziona.

[TROJAN] - avv.Ubaldo Santarelli - rimozione manuale 2

Questo riepilogo non è disponibile. Fai clic qui per visualizzare il post.

[TROJAN] - avv.Ubaldo Santarelli - rimozione manuale

Marco Giuliani, esperto di sicurezza che collabora con la società di
sicurezza Prevx, ha pubblicato interessanti informazioni su un nuovo
messaggio e-mail che sta circolando nelle inbox degli italiani inviato
da un fantomatico avvocato con allegato un codice malware. Simili tipi
di attacchi di ingegneria sociale erano già emersi negli ultimi mesi del
2006 (dettagli pubblicati su PC Al Sicuro). Si tratta di messaggi di
posta scritti in perfetto italiano che tentano di indurre i malcapitati
destinatari a seguire link che conducono a siti web malintenzionati.

Il testo della nuova e-mail nociva:

CITAZIONE
"Egregio Signore/a Come da Raccomandata a.r. Oggetto: Messa in mora del
debitore ex art. 1219 c.c. La mia assistita mi informa che a tutt'oggi
risulta un credito nei Vostri confronti di complessivi €. 900,00, come
risulta dalla documentazione allegata. Per quanto precede Vi rendo noto
che, in difetto di ricezione, entro e non oltre dieci giorni dal
ricevimento della presente, del complessivo importo di €. 900,00 oltre
gli interessi dal dovuto al saldo di € 670,00, agirò legalmente nei
Vostri confronti, con sensibile aggravio di spese. Rimango in attesa di
un Vostro riscontro in merito – nel termine di cui sopra – e
distintamente Vi saluto. Avv. Ubaldo Santarelli".

Il link fornito nell'e-mail invita l'utente ad aprire una pagina web in
cui si comunica la messa in mora e viene mostrato il documento in
dimensioni molto ridotte. L'utente, invitato a cliccare sul file per
leggere il documento, scaricherà un trojan.hijacker dalle dimensioni di
32.512 bytes.

Il Trojan aggiunge una serie di domini nocivi nell'elenco dei siti
attendibili di internet. La home page di Internet Explorer viene
reindirizzata a gooogle.bz (analisi) e le zone di Internet Explorer
vengono alterate. Vengono creati I file:
C:\WINDOWS\system32\winsvc\svc\google.exe e C:\WINDOWS\gratis.pbk (per
le connessioni dialer) e viene creata una chiave di registro che crea
l'icona Connessione Veloce presente all'interno di Risorse del computer.

Il codice nocivo crea inoltre due collegamenti, chiamate Explorer.lnk e
Internet.lnk, sul desktop e nei programmi del menu avvio. Hanno la
stessa icona di Internet Explorer, per cui l'utente crede di lanciare il
browser di Microsoft. Il trojan ha anche funzioni di dialer: 8993993**
Wind Telecomunicazioni S.p.A, 8990325** CSINFO S.p.A, 8994511** Wind
Telecomunicazioni S.p.A

Giuliani ha pubblicato anche una procedura per la rimozione manuale
dell'infezione:

- Attraverso regedit (START - Esegui - "regedit") eliminiamo - se
presenti - le seguenti chiavi di registro:
HKEY_CLASSES_ROOT\CLSID\{16C7013F-912E-42ac-AA8E-A10A180DFF51}

- Riavviamo il computer. Al riavvio cancelliamo il file
C:\WINDOWS\system32\winsvc\svc\google.exe

- Cancelliamo la falsa icona di Internet Explorer sul desktop. La
riconosciamo cliccando con il tasto destro sull'icona e cliccando su
proprietà. Se vedremo nel campo destinazione la voce analcord.com quella
è l'icona da eliminare. Lo stesso facciamo nel menu start - programmi,
cerchiamo il collegamento che richiama analcord.com.

- Apriamo risorse del computer, dove prima c'era la connessione veloce
ora ci dovrebbe essere un riquadro bianco. Facciamo click con il tasto
destro e poi elimina.

- Dobbiamo modificare la home page di Internet Explorer, la quale punta
ancora a gooogle.bz. Per fare ciò, senza scomodare il registro di
sistema, possiamo aprire Internet Explorer cliccando con il tasto destro
sull'icona del programma e cliccando su proprietà internet. Rimuoviamo
gooogle.bz quindi dalla home page e modifichiamo anche l'elenco dei siti
attendibili, Protezione - Siti attendibili - Siti.

--
principio di Napoleone:
non attribuire a malintenzione cio' che puo'
essere semplicemente spiegato come imbecillita'
--
MaoX Blog:
http://maox.blogspot.com

Ottimo CRM - Gestione Clienti

http://www.sugarcrm.com

--
principio di Napoleone: non attribuire a malintenzione cio' che puo' essere semplicemente spiegato come imbecillita'
MaoX Blog:
Problemi e soluzioni di un sistemista informatico:
http://maox.blogspot.com

Ricompilare il kernel su fedora

http://fedoraserver.unipa.it/fedora/desktop/fedora-7/come-compilare-il-kernel-di-fedora-7-partendo-dai-sorgenti/

--
principio di Napoleone: non attribuire a malintenzione cio' che puo' essere semplicemente spiegato come imbecillita'
MaoX Blog:
Problemi e soluzioni di un sistemista informatico:
http://maox.blogspot.com

Tutorial: How to Crack WPA/WPA2

Tutorial: How to Crack WPA/WPA2

fonte: http://www.aircrack-ng.org/doku.php?id=cracking_wpa

Version: 1.05 May 16, 2007
By: darkAudax
Introduction

This tutorial walks you through cracking WPA/WPA2 networks which use
pre-shared keys. I recommend you do some background reading to better
understand what WPA/WPA2 is. The Wiki links page has a WPA/WPA2 section.

WPA/WPA2 supports many types of authentication beyond pre-shared keys.
aircrack-ng can ONLY crack pre-shared keys. So make sure airodump-ng
shows the network as having the authentication type of PSK, otherwise,
don't bother trying to crack it.

There is another important difference between cracking WPA/WPA2 and WEP.
This is the approach used to crack the WPA/WPA2 pre-shared key. Unlike
WEP, where statistical methods can be used to speed up the cracking
process, only plain brute force techniques can be used against WPA/WPA2.
That is, because the key is not static, so collecting IVs like when
cracking WEP encryption, does not speed up the attack. The only thing
that does give the information to start an attack is the handshake
between client and AP. Handshaking is done when the client connects to
the network. Although not absolutely true, for the purposes of this
tutorial, consider it true. Since the pre-shared key can be from 8 to 63
characters in length, it effectively becomes impossible to crack the
pre-shared key.

The only time you can crack the pre-shared key is if it is a dictionary
word or relatively short in length. Conversely, if you want to have an
unbreakable wireless network at home, use WPA/WPA2 and a 63 character
password composed of random characters including special symbols.

The impact of having to use a brute force approach is substantial.
Because it is very compute intensive, a computer can only test 50 to 300
possible keys per second depending on the computer CPU. It can take
hours, if not days, to crunch through a large dictionary. If you are
thinking about generating your own password list to cover all the
permutations and combinations of characters and special symbols, check
out this brute force time calculator first. You will be very surprised
at how much time is required.

There is no difference between cracking WPA or WPA2 networks. The
authentication methodology is basically the same between them. So the
techniques you use are identical.

It is recommended that you experiment with your home wireless access
point to get familiar with these ideas and techniques. If you do not own
a particular access point, please remember to get permission from the
owner prior to playing with it.

I would like to acknowledge and thank the Aircrack-ng team for producing
such a great robust tool.

Please send me any constructive feedback, positive or negative.
Additional troubleshooting ideas and tips are especially welcome.
Assumptions

First, this solution assumes:

*
You are using drivers patched for injection. Use the injection
test to confirm your card can inject.
*
You are physically close enough to send and receive access point
and wireless client packets. Remember that just because you can receive
packets from them does not mean you may will be able to transmit packets
to them. The wireless card strength is typically less then the AP
strength. So you have to be physically close enough for your transmitted
packets to reach and be received by both the AP and the wireless client.
You can confirm that you can communicate with the specific AP by
following these instructions.
*
You are using v0.9 of aircrack-ng. If you use a different version
then some of the command options may have to be changed.

Ensure all of the above assumptions are true, otherwise the advice that
follows will not work. In the examples below, you will need to change
"ath0" to the interface name which is specific to your wireless card.

In the examples, the option "double dash bssid" is shown as "- -bssid".
Remember to remove the space between the two dashes when using it in
real life. This also applies to "- -ivs", "- -arpreplay", "- -deauth",
"- -channel", "- -arp" and "- -fakeauth".
Equipment used

To follow this tutorial at home, you must have two wireless cards.

In this tutorial, here is what was used:

*
MAC address of PC running aircrack-ng suite: 00:0F:B5:88:AC:82
*
MAC address of the wireless client using WPA2: 00:0F:B5:FD:FB:C2
*
BSSID (MAC address of access point): 00:14:6C:7E:40:80
*
ESSID (Wireless network name): teddy
*
Access point channel: 9
*
Wireless interface: ath0

You should gather the equivalent information for the network you will be
working on. Then just change the values in the examples below to the
specific network.
Solution
Solution Overview

The objective is to capture the WPA/WPA2 authentication handshake and
then use aircrack-ng to crack the pre-shared key.

This can be done either actively or passively. "Actively" means you will
accelerate the process by deauthenticating an existing wireless client.
"Passively" means you simply wait for a wireless client to authenticate
to the WPA/WPA2 network. The advantage of passive is that you don't
actually need injection capability and thus the Windows version of
aircrack-ng can be used.

Here are the basic steps we will be going through:

1.
Start the wireless interface in monitor mode on the specific AP
channel
2.
Start airodump-ng on AP channel with filter for bssid to collect
authentication handshake
3.
Use aireplay-ng to deauthenticate the wireless client
4.
Run aircrack-ng to crack the pre-shared key using the
authentication handshake

Step 1 - Start the wireless interface in monitor mode

The purpose of this step is to put your card into what is called monitor
mode. Monitor mode is the mode whereby your card can listen to every
packet in the air. Normally your card will only "hear" packets addressed
to you. By hearing every packet, we can later capture the WPA/WPA2 4-way
handshake. As well, it will allow us to optionally deauthenticate a
wireless client in a later step.

First stop ath0 by entering:

airmon-ng stop ath0

The system responds:

Interface Chipset Driver

wifi0 Atheros madwifi-ng
ath0 Atheros madwifi-ng VAP (parent: wifi0) (VAP
destroyed)

Enter "iwconfig" to ensure there are no other athX interfaces. It should
look similar to this:

lo no wireless extensions.

eth0 no wireless extensions.

wifi0 no wireless extensions.

If there are any remaining athX interfaces, then stop each one. When you
are finished, run "iwconfig" to ensure there are none left.

Now, enter the following command to start the wireless card on channel 9
in monitor mode:

airmon-ng start wifi0 9

Note: In this command we use "wifi0" instead of our wireless interface
of "ath0". This is because the madwifi-ng drivers are being used.

The system will respond:

Interface Chipset Driver

wifi0 Atheros madwifi-ng
ath0 Atheros madwifi-ng VAP (parent: wifi0)
(monitor mode enabled)

You will notice that "ath0" is reported above as being put into monitor
mode.

To confirm the interface is properly setup, enter "iwconfig".

The system will respond:

lo no wireless extensions.

wifi0 no wireless extensions.

eth0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"" Nickname:""
Mode:Monitor Frequency:2.452 GHz Access Point:
00:0F:B5:88:AC:82
Bit Rate:0 kb/s Tx-Power:18 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

In the response above, you can see that ath0 is in monitor mode, on the
2.452GHz frequency which is channel 9 and the Access Point shows the MAC
address of your wireless card. Only the madwifi-ng drivers show the card
MAC address in the AP field, other drivers do not. So everything is
good. It is important to confirm all this information prior to
proceeding, otherwise the following steps will not work properly.

To match the frequency to the channel, check out:

http://www.rflinx.com/help/calculations/#2.4ghz_wifi_channels then
select the "Wifi Channel Selection and Channel Overlap" tab. This will
give you the frequency for each channel.
Step 2 - Start airodump-ng to collect authentication handshake

The purpose of this step is run airodump-ng to capture the 4-way
authentication handshake for the AP we are interested in.

Enter:

airodump-ng -c 9 - -bssid 00:14:6C:7E:40:80 -w psk ath0

Where:

*
-c 9 is the channel for the wireless network
*
- -bssid 00:14:6C:7E:40:80 is the access point MAC address. This
eliminate extraneous traffic.
*
-w psk is the file name prefix for the file which will contain
the IVs.
*
ath0 is the interface name.

Important: Do NOT use the "- -ivs" option. You must capture the full
packets.

Here what it looks like if a wireless client is connected to the network:

CH 9 ][ Elapsed: 4 s ][ 2007-03-24 16:58

BSSID PWR RXQ Beacons #Data, #/s CH MB ENC
CIPHER AUTH ESSID

00:14:6C:7E:40:80 39 100 51 116 14 9 54 WPA2 CCMP
PSK teddy

BSSID STATION PWR Lost Packets Probes

00:14:6C:7E:40:80 00:0F:B5:FD:FB:C2 35 0 116

Here it is with no connected wireless clients:

CH 9 ][ Elapsed: 4 s ][ 2007-03-24 17:51

BSSID PWR RXQ Beacons #Data, #/s CH MB ENC
CIPHER AUTH ESSID

00:14:6C:7E:40:80 39 100 51 0 0 9 54 WPA2 CCMP
PSK teddy

BSSID STATION PWR Lost Packets Probes

Step 3 - Use aireplay-ng to deauthenticate the wireless client

This step is optional. You only perform this step if you opted to
actively speed up the process. The other constraint is that there must
be a wireless client currently associated with the AP. If there is no
wireless client currently associated with the AP, then move onto the
next step and be patient. Needless to say, if a wireless client shows up
later, you can backtrack and perform this step.

What this step does is send a message to the wireless client saying that
that it is no longer associated with the AP. The wireless client will
then hopefully reauthenticate with the AP. The reauthentication is what
generates the 4-way authentication handshake we are interested in
collecting. This what we use to break the WPA/WPA2 pre-shared key.

Based on the output of airodump-ng in the previous step, you determine a
client which is currently connected. You need the MAC address for the
following. Open another console session and enter:

aireplay-ng -0 1 -a 00:14:6C:7E:40:80 -c 00:0F:B5:FD:FB:C2 ath0

Where:

*
-0 means deauthentication
*
1 is the number of deauths to send (you can send muliple if you wish)
*
-a 00:14:6C:7E:40:80 is the MAC address of the access point
*
-c 00:0F:B5:FD:FB:C2 is the MAC address of the client you are
deauthing
*
ath0 is the interface name

Here is what the output looks like:

11:09:28 Sending DeAuth to station -- STMAC: [00:0F:B5:34:30:30]

With luck this causes the client to reauthenticate and yield the 4-way
handshake.
Troubleshooting Tips

*
The deauthentication packets are sent directly from your PC to
the clients. So you must be physically close enough to the clients for
your wireless card transmissions to reach them.

Step 4 - Run aircrack-ng to crack the pre-shared key

The purpose of this step is to actually crack the WPA/WPA2 pre-shared
key. To do this, you need a dictionary of words as input. Basically,
aircrack-ng takes each word and tests to see if this is in fact the
pre-shared key.

There is a small dictionary that comes with aircrack-ng -
"password.lst". The Wiki FAQ has an extensive list of dictionary
sources. You can use John the Ripper (JTR) to generate your own list and
pipe them into aircrack-ng. Using JTR in conjunction with aircrack-ng is
beyond the scope of this tutorial.

Open another console session and enter:

aircrack-ng -w password.lst -b 00:14:6C:7E:40:80 psk*.cap

Where:

*
-w password.lst is the name of the dictionary file. Remember to
specify the full path if the file is not located in the same directory.
*
*.cap is name of group of files containing the captured packets.
Notice in this case that we used the wildcard * to include multiple files.

Here is typical output when there are no handshakes found:

Opening psk-01.cap
Opening psk-02.cap
Opening psk-03.cap
Opening psk-04.cap
Read 1827 packets.

No valid WPA handshakes found.

When this happens you either have to redo step 3 (deauthenticating the
wireless client) or wait longer if you are using the passive approach.
When using the passive approach, you have to wait until a wireless
client authenticates to the AP.

Here is typical output when handshakes are found:

Opening psk-01.cap
Opening psk-02.cap
Opening psk-03.cap
Opening psk-04.cap
Read 1827 packets.

# BSSID ESSID Encryption

1 00:14:6C:7E:40:80 teddy WPA (1 handshake)

Choosing first network as target.

Now at this point, aircrack-ng will start attempting to crack the
pre-shared key. Depending on the speed of your CPU and the size of the
dictionary, this could take a long time, even days.

Here is what successfully cracking the pre-shared key looks like:

Aircrack-ng 0.8

[00:00:00] 2 keys tested (37.20 k/s)

KEY FOUND! [ 12345678 ]

Master Key : CD 69 0D 11 8E AC AA C5 C5 EC BB 59 85 7D 49 3E
B8 A6 13 C5 4A 72 82 38 ED C3 7E 2C 59 5E AB FD

Transcient Key : 06 F8 BB F3 B1 55 AE EE 1F 66 AE 51 1F F8 12 98
CE 8A 9D A0 FC ED A6 DE 70 84 BA 90 83 7E CD 40
FF 1D 41 E1 65 17 93 0E 64 32 BF 25 50 D5 4A 5E
2B 20 90 8C EA 32 15 A6 26 62 93 27 66 66 E0 71

EAPOL HMAC : 4E 27 D9 5B 00 91 53 57 88 9C 66 C8 B1 29 D1 CB

--
principio di Napoleone:
non attribuire a malintenzione cio' che puo'
essere semplicemente spiegato come imbecillita'
--
MaoX Blog:
http://maox.blogspot.com

Quicker Database Oracle Installs on Unbrekable Linux with the oracle-validated RPM

Fonte:
http://www.orablogs.com/sergio/archives/linux/index.html

In an earlier post I wrote about the Oracle channel on the Unbreakable Linux Network (ULN) and how to subscribe to it. This channel just got a great new addition in the form of the oracle-validated RPM. When you install this RPM using up2date and ULN, it will automatically install all packages required by the Oracle database installer.

[root@localhost ~]# up2date --install oracle-validated  Fetching Obsoletes list for channel: el4_i386_addons...  Fetching Obsoletes list for channel: el4_i386_oracle...  Fetching Obsoletes list for channel: el4_i386_latest...  Fetching rpm headers... ########################################  Name                                    Version        Rel      ---------------------------------------------------------- oracle-validated                        1.0.0          3.el4             i386     Testing package set / solving RPM inter-dependencies... ######################################## oracle-validated-1.0.0-3.el ########################## Done.                    elfutils-libelf-devel-0.97. ########################## Done.                    gcc-3.4.6-3.1.0.1.i386.rpm: ########################## Done.                    gcc-c++-3.4.6-3.1.0.1.i386. ########################## Done.                    glibc-devel-2.3.4-2.25.i386 ########################## Done.                    glibc-headers-2.3.4-2.25.i3 ########################## Done.                    glibc-kernheaders-2.4-9.1.9 ########################## Done.                    libstdc++-devel-3.4.6-3.1.0 ########################## Done.                    sysstat-5.0.5-11.rhel4.i386 ########################## Done.                    Preparing              ########################################### [100%]  Installing...    1:libstdc++-devel        ########################################### [100%]    2:glibc-kernheaders      ########################################### [100%]    3:glibc-headers          ########################################### [100%]    4:glibc-devel            ########################################### [100%]    5:gcc                    ########################################### [100%]    6:gcc-c++                ########################################### [100%]    7:sysstat                ########################################### [100%]    8:elfutils-libelf-devel  ########################################### [100%]    9:oracle-validated       ########################################### [100%] insmod /lib/modules/2.6.9-42.EL/kernel/drivers/net/e1000/e1000.ko  insmod /lib/modules/2.6.9-42.EL/kernel/drivers/char/hangcheck-timer.ko hangcheck_reboot=1 The following packages were added to your selection to satisfy dependencies:  Name                                    Version        Release -------------------------------------------------------------- elfutils-libelf-devel                   0.97.1         3                    gcc                                     3.4.6          3.1.0.1              gcc-c++                                 3.4.6          3.1.0.1              glibc-devel                             2.3.4          2.25                 glibc-headers                           2.3.4          2.25                 glibc-kernheaders                       2.4            9.1.98.EL            libstdc++-devel                         3.4.6          3.1.0.1              sysstat                                 5.0.5          11.rhel4              [root@localhost ~]#  

Named after Validated Configurations, oracle-validated also creates an oracle OS user and an oinstall and dba group. Kernel parameters are also set properly, ensuring that the Oracle Universal Installer will proceed without complaints. Very nice!

--  principio di Napoleone: non attribuire a malintenzione cio' che puo' essere semplicemente spiegato come imbecillita' MaoX Blog: Problemi e soluzioni di un sistemista informatico: http://maox.blogspot.com

Installation of Oracle 9i (R2) on (Oracle) Enterprise Linux

Installation of Oracle 9i (R2) on (Oracle) Enterprise Linux

fonte:
http://ivan.kartik.sk/oracle/install_ora9_elinux.html

This paper (HOWTO) describes step-by-step installation of Oracle 9i database software on Enteprise Linux. Installation steps are valid for 32 bit (x86) and 64 bit (x86_64) architectures.

This paper covers following steps:

• Pre-Instalation Tasks
• Download & Install
• Post-Instalation Tasks
• Common Installation Errors

Pre-Instalation Tasks

1. Create oracle User Account

Login as root and create te user oracle which belongs to dba group.

su -
# groupadd dba
# groupadd oinstall
# useradd -g oinstall -G dba oracle

2. Setting System parameters
Edit the /etc/sysctl.conf and add following lines:

kernel.sem = 250 32000 100 128
kernel.shmmax = 2147483648
kernel.shmmni = 128
kernel.shmall = 2097152
kernel.msgmnb = 65536
kernel.msgmni = 2878
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000

Note: You need execute "sysctl -p" or reboot system to apply above settings.

Edit the /etc/security/limits.conf file and add following lines:

* - nproc 16384
* - nofile 16384

3. Setting Oracle Enviroment
Edit the /home/oracle/.bash_profile file and add following lines:

Use this settings for 32bit (x86) architecture.

ORACLE_BASE=/opt/oracle
ORACLE_HOME=$ORACLE_BASE/920
ORACLE_SID=MYORACLE
LD_LIBRARY_PATH=$ORACLE_HOME/lib
LD_ASSUME_KERNEL=2.4.19
PATH=$PATH:$ORACLE_HOME/bin

export ORACLE_BASE ORACLE_HOME ORACLE_SID LD_LIBRARY_PATH LD_ASSUME_KERNEL PATH

Use this settings for 64bit (x86_64) architecture.

ORACLE_BASE=/opt/oracle
ORACLE_HOME=$ORACLE_BASE/920
ORACLE_SID=MYORACLE
LD_LIBRARY_PATH=$ORACLE_HOME/lib
LD_LIBRARY_PATH_32=$ORACLE_HOME/lib32
PATH=$PATH:$ORACLE_HOME/bin

export ORACLE_BASE ORACLE_HOME ORACLE_SID LD_LIBRARY_PATH LD_LIBRARY_PATH_32 PATH

Save the .bash_profile and execute following commands for load new enviroment:

cd /home/oracle
. .bash_profile

4. Create base directory for Oracle

Login as root and create base directory for Oracle ($ORACLE_BASE).

su -
# cd /opt
# mkdir oracle
# chown oracle:dba oracle

Download & Install

1. Install required .rpm packages

Some additional packages are required for succesful instalation of Oracle software. To check whether required packages are installed on your operating system one of following commands:

rpm -q compat-db compat-gcc-32 compat-gcc-32-c++ compat-libcom_err compat-libcwait compat-libgcc-296 compat-libstdc++-296 compat-libstdc++-33 gcc gcc-c++ glibc glibc-common glibc-devel glibc-headers glibc-kernheaders libgcc make

or

rpm -qa --qf '%{name}-%{version}-%{release}.%{arch}\n'|egrep 'compat|glibc|gcc'|sort

Required packages for 32bit (x86) architecture:

binutils-2.15.92.0.2-21
compat-db-4.1.25-9
compat-gcc-32-3.2.3-47.3
compat-gcc-32-c++-3.2.3-47.3
compat-libcom_err-1.0-5
compat-libcwait-2.1-1
compat-libgcc-296-2.96-132.7.2
compat-libstdc++-296-2.96-132.7.2
compat-libstdc++-33-3.2.3-47.3
gcc-3.4.6-3.1
gcc-c++-3.4.6-3.1
glibc-2.3.4-2.25
glibc-common-2.3.4-2.25
glibc-devel-2.3.4-2.25
glibc-headers-2.3.4-2.25
glibc-kernheaders-2.4-9.1.98.EL
libgcc-3.4.6-3.1
make-3.80-6.EL4.i386

Note: Package compat-libcwait-2.1-1.i386.rpm is not included in Enterpise Linux installation media. You can download this package here.

Required packages for 64bit (x86_64) architecture:

binutils-2.15.92.0.2-21.x86_64
compat-db-4.1.25-9.i386
compat-db-4.1.25-9.x86_64
compat-gcc-32-3.2.3-47.3.x86_64
compat-gcc-32-c++-3.2.3-47.3.x86_64
compat-libcom_err-1.0-5.i386
compat-libcom_err-1.0-5.x86_64
compat-libgcc-296-2.96-132.7.2.i386
compat-libstdc++-296-2.96-132.7.2.i386
compat-libstdc++-33-3.2.3-47.3.i386
compat-libstdc++-33-3.2.3-47.3.x86_64
gcc-3.4.6-3.1.x86_64
gcc-c++-3.4.6-3.1.x86_64
glibc-2.3.4-2.25.i686
glibc-2.3.4-2.25.x86_64
glibc-common-2.3.4-2.25.x86_64
glibc-devel-2.3.4-2.25.i386
glibc-devel-2.3.4-2.25.x86_64
glibc-headers-2.3.4-2.25.x86_64
glibc-kernheaders-2.4-9.1.98.EL.x86_64
libgcc-3.4.6-3.1.i386
libgcc-3.4.6-3.1.x86_64
make-3.80-6.EL4.x86_64

Install the required packages using the rpm command:

# rpm -ivh <package_name>.rpm

If all required packages were installed succesfuly then login as root and switch the GCC 3.4 compiler binary with GCC 3.2 compiler binary as following:

su -
# cd /usr/bin
# mv ./gcc ./gcc34
# mv ./gcc32 ./gcc

2. Download the Oracle 9i (9.2.0.4) software from Oracle website for apropriate architecture.
Direct link to Oracle Database 32bit (x86)
Direct link to Oracle Database 64bit (x86_64)

Extract the files using following command (for 32bit architecture):

gunzip ship_9204_linux_disk1.cpio.gz
gunzip ship_9204_linux_disk2.cpio.gz
gunzip ship_9204_linux_disk3.cpio.gz

cpio -idmv < ship_9204_linux_disk1.cpio
cpio -idmv < ship_9204_linux_disk2.cpio
cpio -idmv < ship_9204_linux_disk3.cpio

or for 64bit architecture:

gunzip amd64_db_9204_Disk1.cpio.gz
gunzip amd64_db_9204_Disk2.cpio.gz
gunzip amd64_db_9204_Disk3.cpio.gz

cpio -idmv < amd64_db_9204_Disk1.cpio
cpio -idmv < amd64_db_9204_Disk2.cpio
cpio -idmv < amd64_db_9204_Disk3.cpio

When all archives were extracted you've got three directories Disk1, Disk2 and Disk3.


3. Start the Oracle software installation process.

Now the system is prepared for Oracle software installation. To start the installation process execute the following commands (as oracle):

cd Disk1
./runInstaller

Post-Instalation Tasks

1. Switch back the GCC binaries

su -
# cd /usr/bin
# mv ./gcc ./gcc32
# mv ./gcc34 ./gcc

2. (Optional) You may consider to use rlwrap for comfortable work with sqlplus. RPM package for RedHat compatible (x86) distribution you can download here. RPM for x86_64 architecture you can download here.

su -
# rpm -ivh rlwrap-0.24-rh.i386.rpm
# exit
echo "alias sqlplus='rlwrap sqlplus'" >> /home/oracle/.bash_profile
. /home/oracle/.bash_profile

Common Installation Errors

Unable to load native library: /tmp/OraInstall2006-12-20_11-11-34AM/jre/lib/i386/libjava.so: symbol __libc_wait, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
Solution: Install new JRE 1.3.1 version. Edit the Disk1/install/linux/oraparam.ini and set path to new JRE for JRE_LOCATION variable. For more information see Download & Install section.

/opt/oracle/jre/1.1.8/bin/../lib/i686/native_threads/libzip.so: symbol errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference (libzip.so)
Solution: Set the LD_ASSUME_KERNEL=2.4.19

/tmp/OraInstall2006-12-20_11-38-19AM/jre/lib/i386/libawt.so: libXp.so.6: cannot open shared object file: No such file or directory
Solution: Install the xorg-x11-deprecated-libs package.

Starting Oracle Intelligent Agent.../opt/oracle/920/bin/dbsnmpwd: line 156: 10736 Segmentation fault nohup $ORACLE_HOME/bin/dbsnmp $* >>$DBSNMP_WDLOGFILE 2>&1
/opt/oracle/920/bin/dbsnmpwd: line 156: 10749 Segmentation fault nohup $ORACLE_HOME/bin/dbsnmp $* >>$DBSNMP_WDLOGFILE 2>&1
/opt/oracle/920/bin/dbsnmpwd: line 156: 10761 Segmentation fault nohup $ORACLE_HOME/bin/dbsnmp $* >>$DBSNMP_WDLOGFILE 2>&1
/opt/oracle/920/bin/dbsnmpwd: line 156: 10773 Segmentation fault nohup $ORACLE_HOME/bin/dbsnmp $* >>$DBSNMP_WDLOGFILE 2>&1
Solution: Download and apply patch nr.: 3238244 from http://metalink.oracle.com.

Exception in thread "main" java.lang.InternalError: Can't connect to X11 window server using 'localhost:0.0' as the value of the DISPLAY variable.
Solution: Execute "export DISPLAY=:0.0" (as oracle user) and "xhost +" as user who has opened X session (for example logged in KDE, GNOME, etc.). If the value is other than 127.0.0.1 or localhost you should "xhost +" on client machine.

Error in invoking target install of makefile /opt/oracle/920/ctx/lib/ins_ctx.mk
Error in invoking target install of makefile /opt/oracle/920/precomp/lib/ins_precomp.mk
Error in invoking target install of makefile /opt/oracle/920/plsql/lib/ins_plsql.mk
Error in invoking ntcontab.o of makfile /opt/oracle/920/network/lib/ins_net_client.mk
Solution: Some of required packages is missing (not installed on your OS) or GCC binaries wasn't changed. For more information see Download & Install section.

--  principio di Napoleone: non attribuire a malintenzione cio' che puo' essere semplicemente spiegato come imbecillita' MaoX Blog: Problemi e soluzioni di un sistemista informatico: http://maox.blogspot.com

Nut - Configurazioni

http://opensource.mgeups.com/howto.htm#test-cfg
http://opensource.mgeups.com/ups.htm
http://opensource.mgeups.com/install/debian.htm
http://www.mscs.dal.ca/~selinger/ups/backups.html

--
principio di Napoleone:
non attribuire a malintenzione cio' che puo'
essere semplicemente spiegato come imbecillita'
MaoX Blog:
http://maox.blogspot.com