https://wiki.archlinux.org/api.php?action=feedcontributions&user=Psykopear&feedformat=atomArchWiki - User contributions [en]2024-03-28T15:28:38ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=E17_(Italiano)&diff=62830E17 (Italiano)2009-02-22T09:23:55Z<p>Psykopear: Traduzione in italiano</p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|English|E17}}<br />
{{i18n_entry|Русский|E17 (Русский)}}<br />
{{i18n_entry|Español|E17 (Español)}}<br />
{{i18n_entry|Italiano|E17 (Italiano)}}<br />
{{i18n_links_end}}<br />
<br />
E17 è la versione in sviluppo DR17 dell'ambiente desktop Enlightenment.<br />
<br />
E17 è attualmente in uno stato di forte sviluppo, ed è in uno stato di pre-alpha. Anche se è molto giovane, E17 è comunque abbastanza stabile. Molte persone lo usano come ambiente desktop per tutti i giorni. <br />
<br />
Le nuove versioni sono disponibili ogni giorno via SVN, ma sono forniti anche degli snapshot per una più semplice installazione. Sotto ci sono le istruzioni su come installare la versione da SVN e la versione dai repository community di Arch.<br />
<br />
== Installare E17 dai repository community ==<br />
<br />
* Prima di tutto, modificare il file /etc/pacman.conf e decommenta il repository community rimuovendo il cancelletto all'inizio della linea. Dovrebbe presentarsi più meno così:<br />
<br />
[community]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist<br />
<br />
* In seguito sincronizzare e aggiornare i repository:<br />
pacman -Syu<br />
* Installare il gruppo e17:<br />
pacman -S e17-svn<br />
* Installare moduli aggiuntivi ed applicazioni per e17:<br />
pacman -S desktop-file-utils e17-extra-svn<br />
<br />
* Se c'è bisogno di pacchetti per e17 che non sono (ancora) disponibili nel repository [community], controllare se sono disponibili su [http://aur.archlinux.org/ AUR].<br />
<br />
* Ora si può partire con e17. Lo si può fare in più modi:<br />
** Aggiungere una riga 'enlightenment_start' al proprio ~/.xinitrc<br />
** Far partire il login manager entranced (disponibile nel gruppo e17-extra-svn) aggiungendo 'entranced' nei demoni in /etc/rc.conf<br />
** Far partire il login manager entrance usando la linea 'x:5:respawn:/usr/sbin/entranced -nodaemon >& /dev/null' nel file /etc/inittab<br />
<br />
<br />
NB: e17 è un software ancora in stato di alpha. In alcuni casi nel futuro le cose potrebbero non funzionare come voluto. Anche se tutti i pacchetti sono testati prima di essere aggiunti nel repository [community], le cose potrebbero smettere di funzionare. E' consigliabile tenere i pacchetti della versione precedente sul computer, in modo che, se necessario, sia possibile effettuare una retrocessione di versione.<br />
<br />
Se si riscontra un comportamento indesiderato, ci sono un po di cose che si possono fare. Prima di tutto, provare se lo stesso comportamento si presenta con il tema di default. In secondo luogo, provare a rimuovere ~/.e (magari facendone un backup prima). Se sei sicuro di aver trovato un bug, è consigliabile riportarlo direttamente agli svilupatori. Se non si è sicuri se sia un bug del software o del pacchetto, riportarlo nel bug tracker di [community].<br />
<br />
==== Avere i pacchetti di e17 aggiornati più spesso ====<br />
Si possono compilare i proprio pacchetti di e17 per Arch Linux grazie un piccolo script in python, chiamato ArchE17. Per maggiori informazioni e per scaricare l'ultima versione dello script, vedere [http://www.archlinux.org/~ronald/e17.html http://www.archlinux.org/~ronald/e17.html]<br />
<br />
== Installare E17 usando easy_e17.sh ==<br />
Il motivo per usare quest'altro metodo rispetto a quello menzionato sopra, è dipendente da ciò che si vuole, anche se questo script è più semplice da usar (assieme ad altri tool) perchè fornisce un maggior controllo quando E17 è aggiornato dello script in python. Lo script permette di installare componenti dal repository di E17 senza dovere rifare un nuovo PKGBUILD. Con questo script, quando si disinstalla il pacchetto, tutto ciò che è stato installate con lo script verrà eliminato. Per maggiori informazione, vedere [http://ubuntuforums.org/showthread.php?t=916690 the thread for it on ubuntuforums.org].<br />
<br />
Per installare E17 usando questo script, aggiungere questo repo nel proprio /etc/pacman.conf:<br />
<br />
[rfad]<br />
# Repository made by haxit | Contact: requiem [at] archlinux.us for package suggestions!<br />
Server = http://web.ncf.ca/ey723/archlinux/repo/<br />
<br />
E poi lanciare:<br />
<br />
pacman -Sy easy-e17<br />
<br />
In alternativa, si può [scaricare l'archivio da AUR], estrarlo in una nuova cartella, e lanciare makepkg. Poi lanciare come root pacman -U *.pkg.tar.gz. Puoi anche usare yaourt per installare facilmente questo pacchetto. Per fare ciò, lanciare:<br />
<br />
yaourt -S easy-e17<br />
<br />
<br />
Verranno poste un pò di domande, e poi verrà installato. Per far partire E17 sarà necessario mettere questa riga nel proprio ~/.xinitrc:<br />
<br />
exec /opt/e17/bin/enlightenment_start<br />
<br />
Potrebbe inoltre essere comodo mettere /opt/e17/bin nel prprio PATH, così da non dover mettere /opt/e17/bin davanti a ogni programma da far partire. Per fare ciò, modifica questa linea nel /etc/profile:<br />
<br />
PATH="/bin:/usr/bin:/sbin:/usr/sbin"<br />
<br />
In modo da farla diventare:<br />
<br />
PATH="/bin:/usr/bin:/sbin:/usr/sbin:/opt/e17/bin"<br />
<br />
Se si riscontrare errori installando E17, prima di tutto controollare che non sia un errore di dipendenze. Se lo è, installare le dipendenze e continuare ad installare E17 lanciando questo comando da root:<br />
<br />
easy_e17.sh -i<br />
<br />
Per installare una delle tante applicazioni dal repository SVN di E17, semplicemente rimuovere il nome di quel programma da /etc/easy_e17.conf, e lanciare questo comano da root (scambiando name2 con il nome del programma che è stato rimosso da easy_e17.conf):<br />
<br />
easy_e17.sh -i --only=''name'',''name2''<br />
<br />
Per aggiornare E17 senza usare il programma sotto descritto, lanciare da root questo comando:<br />
<br />
easy_e17.sh -u<br />
<br />
=== Update_e17.sh ===<br />
Un altro pacchetto, lo script update_e17 di OzOs, è utile quando usato in contemporanea conm questo script, dato che può ripristinare il ramo svn di E17 (nel caso ci siano stati errori), come anche portarlo indietro ad una versione specifica (sempre in caso di problemi) o anche mettere al corrente quando una nuova revisione è stata rilasciata nel ramo svn.Vedi [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] per altre informazioni sui suoi componenti aggiuntivi. Per installarlo, usare uno dei procedimenti descritti sopra. Il pacchetto in AUR si trova [http://aur.archlinux.org/packages.php?ID=23227 qui]. Per installarlo con yaourt, lanciare:<br />
<br />
yaourt -S oz-e17-tools<br />
<br />
== Installare i temi ==<br />
<br />
Più temi per modificare l'aspetto di E17 sono repoeribili a [http://exchange.enlightenment.org/ exchange.enlightenment.org].<br />
Controllare anche [http://www.e17-stuff.org e17-stuff.org].<br />
<br />
I temi (in formato .edj) possono essere isntallati nella finestra di configurazione.<br />
<br />
E' anche possibile cambiare il tema per il toolkit etk (quello usate da exhibit). Far partire la finestra di configurazione per cambiare il toolkit etc lanciando /usr/bin/etk_prefs<br />
<br />
[http://aur.archlinux.org/packages.php?ID=7896 e17-themes] (pacchetto di aur), automatizza il download e l'installazione di molti temi da exchange.enlightenment.org<br />
<br />
== Troubleshooting ==<br />
* Se X manda errori riguardo il cursore di X chenon è disponibile, installare il pacchetto 'libxcursor'.<br />
<br />
== Link Esterni ==<br />
* [http://exchange.enlightenment.org/ Exchange.enlightenment.org, un nuovo sito integrato che rimpiazza il vecchio get-.org]<br />
<br />
* [http://get-e.org Portale di Enlightenment DR17 con temi, sfondi, moduli, etc.]<br />
* [http://get-e.org/E17_User_Guide/English/ Guide di Enlightenment DR 17 ]<br />
* [http://get-e.org/EFL_User_Guide/English/ Guida dell'Enlightenment Foundation Libraries]<br />
* [http://gentoo-wiki.com/HOWTO_emerge_e17 e17 Howto di gentoo];<br />
** Specificatamente, [http://gentoo-wiki.com/HOWTO_emerge_e17#Adding_Apps_to_ibar Aggiungere applicazioni a iBar]</div>Psykopearhttps://wiki.archlinux.org/index.php?title=E17&diff=62825E172009-02-22T08:33:17Z<p>Psykopear: </p>
<hr />
<div>[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|E17}}<br />
{{i18n_entry|Русский|E17 (Русский)}}<br />
{{i18n_entry|Español|E17 (Español)}}<br />
{{i18n_entry|Italiano|E17 (Italiano)}}<br />
{{i18n_links_end}}<br />
<br />
E17 is the Development Release 17 (DR17) of the Enlightenment Desktop Environment.<br />
<br />
E17 is currently under heavy development, and is in the pre-alpha stages. Even though it is only young, E17 is still quite stable. Many people use it as a day-to-day Environment. <br />
<br />
New versions are available daily via SVN, but snapshots are also taken for easy installation. Below are instructions on how to install a SVN snapshot from the Arch community repositories.<br />
<br />
== Installing E17 from the community repository ==<br />
<br />
* First, edit your /etc/pacman.conf file and uncomment the community repositories by removing the hash at the start of that line; you should end up with something like the following:<br />
<br />
[community]<br />
# Add your preferred servers here, they will be used first<br />
Include = /etc/pacman.d/mirrorlist<br />
<br />
* Next, sync, update, and upgrade using the new community repository:<br />
pacman -Syu<br />
* Install e17 group:<br />
pacman -S e17-svn<br />
* Install additional e17 modules and applications:<br />
pacman -S desktop-file-utils e17-extra-svn<br />
<br />
* If you need an e17 package which is not (yet) available in the [community] repo, see if it is available in the [http://aur.archlinux.org/ AUR].<br />
<br />
* You are now ready to start e17. You can do this in a number of ways:<br />
** Add a line reading 'enlightenment_start' to your ~/.xinitrc<br />
** Start the entrance login manager (available in the e17-extra-svn group) by adding 'entranced' to the daemons array in /etc/rc.conf<br />
** Start the entrance login manager by using the line 'x:5:respawn:/usr/sbin/entranced -nodaemon >& /dev/null' in /etc/inittab<br />
<br />
Enjoy!<br />
<br />
<br />
Note : e17 is still alpha software. At some point in the future things may not work as expected anymore. Although all packages are tested before added to the [community] repo, things may stop working for you. You are therefore encouraged to keep packages for the previous version on your computer, allowing you to downgrade if needed.<br />
<br />
If you find some unexpected behavior, there is a few things you can do. First try if the same behavior exists with the default theme. Second remove ~/.e (you may want to make a backup first). If you are sure you found a bug please report it directly upstream. If you are not sure if it is a bug in the software or in the package, report it on the [community] bug tracker.<br />
<br />
==== I want my e17 packages updated more often ====<br />
You can build your own Arch Linux e17 packages with a small python script called ArchE17. For more information and to download the latest version of the script, see [http://www.archlinux.org/~ronald/e17.html http://www.archlinux.org/~ronald/e17.html]<br />
<br />
== Installing E17 using easy_e17.sh ==<br />
The reason to use this meathod over the one mentioned before is mostly based on what you want to do, but I find it easier because the script (along with an extra tool) can give those who want more control over when E17 is updated than the aforementioned python script. It allows you to install components from E17's repository without having to go through and make a new PKGBUILD for it. With this script, when you uninstall this package, everything that was installed with the script is uninstalled. If you want to learn more about this script, see [http://ubuntuforums.org/showthread.php?t=916690 the thread for it on ubuntuforums.org].<br />
<br />
To install E17 using this script, add this repo to your /etc/pacman.conf:<br />
<br />
[rfad]<br />
# Repository made by haxit | Contact: requiem [at] archlinux.us for package suggestions!<br />
Server = http://web.ncf.ca/ey723/archlinux/repo/<br />
<br />
Then, run:<br />
<br />
pacman -Sy easy-e17<br />
<br />
Alternatively, you can [download the tarball from AUR], extract it to a new directory, and run makepkg. Then run as root pacman -U *.pkg.tar.gz. You can even use yaourt to easily install this package. To do so, run this command:<br />
<br />
yaourt -S easy-e17<br />
<br />
It will ask you a few questions and then install. You will need to put this in your .xinitrc in order to start E17:<br />
<br />
exec /opt/e17/bin/enlightenment_start<br />
<br />
It may be helpful to put /opt/e17/bin in your PATH, as then you won't have to add /opt/e17/bin in front of each program in order to run it. To do that, modify this line in /etc/profile:<br />
<br />
PATH="/bin:/usr/bin:/sbin:/usr/sbin"<br />
<br />
So that it reads instead:<br />
<br />
PATH="/bin:/usr/bin:/sbin:/usr/sbin:/opt/e17/bin"<br />
<br />
If you encounter any errors while trying to install E17, first check to make sure it isn't a dependancy problem. If it is, install the dependancy and continue installing e17 by running this command as root:<br />
<br />
easy_e17.sh -i<br />
<br />
To install one of the many applications from E17's svn repository, simply remove that program's name from /etc/easy_e17.conf, and then run this command as root (replacing name and name2 by the name of the program(s) you removed from easy_e17.conf):<br />
<br />
easy_e17.sh -i --only=''name'',''name2''<br />
<br />
To update E17 without using the program mentioned below, run this command as root:<br />
<br />
easy_e17.sh -u<br />
<br />
=== Update_e17.sh ===<br />
Another package, for OzOs's update_e17.sh script, is helpful when used in conjuntion with this script, as it can backup and restore your E17 svn tree (in case there is breakage), as well ass roll it back to a specific revision (again, in case of breakage) or even let you know when a new revision has come around on E17's svn tree. See [http://cafelinux.org/OzOs/content/how-administer-your-ozos-e17-desktop this page] for more information on this optional component. To install this, use either of the above meathods. The AUR page is located [http://aur.archlinux.org/packages.php?ID=23227 here]. To install it via yaourt, run:<br />
<br />
yaourt -S oz-e17-tools<br />
<br />
== Installing Themes ==<br />
More themes to customise the look of e17 are available from [http://exchange.enlightenment.org/ exchange.enlightenment.org].<br />
Make sure you also check out [http://www.e17-stuff.org e17-stuff.org].<br />
<br />
You can install the themes (coming in .edj format) from the configuration dialog.<br />
<br />
You can also change the theme for the etk toolkit (the one which is used by exhibit). You can start the dialog to change the etk toolkit by starting /usr/bin/etk_prefs<br />
<br />
[http://aur.archlinux.org/packages.php?ID=7896 e17-themes] (aur package), can automate the download and install of lots of themes from exchange.enlightenment.org<br />
<br />
== Troubleshooting ==<br />
* If X complains about X cursors not being available, get the package 'libxcursor'.<br />
<br />
== External Links ==<br />
* [http://exchange.enlightenment.org/ Exchange.enlightenment.org, a new, integrated site that replaces the former get-e.org. get-e.org will close in August, 2008.]<br />
<br />
* [http://get-e.org Enlightenment DR17 Portal, with themes, backgrounds, modules, etc.]<br />
* [http://get-e.org/E17_User_Guide/English/ Enlightenment DR 17 Users Guide]<br />
* [http://get-e.org/EFL_User_Guide/English/ Enlightenment Foundation Libraries User Guide]<br />
* is not anymore> [http://gentoo-wiki.com/HOWTO_emerge_e17 Gentoo's e17 Howto];<br />
** Specifically, [http://gentoo-wiki.com/HOWTO_emerge_e17#Adding_Apps_to_ibar Adding Apps to iBar]</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Fluxbox_(Italiano)&diff=58720Fluxbox (Italiano)2009-01-21T12:40:31Z<p>Psykopear: Tolta dalla categoria translate me</p>
<hr />
<div>[[Category:Desktop environments (Italiano)]]<br />
[[Category:HOWTOs (Italiano)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Fluxbox}}<br />
{{i18n_entry|Italiano|Fluxbox (Italiano)}}<br />
{{i18n_links_end}}<br />
<br />
===Installare Fluxbox===<br />
Installa fluxbox dai repository. I nuovi utenti potrebbero voler installare anche menumaker e/o fluxconf.<br />
pacman -Sy fluxbox fluxconf<br />
<br />
Menumaker è stato spostato in unsupported, per installarlo avrai bisogno dell'archivio su AUR.<br />
wget http://aur.archlinux.org/packages/menumaker/menumaker.tar.gz<br />
tar xvf menumaker.tar.gz<br />
cd menumaker<br />
makepkg<br />
Installazione:<br />
pacman -U menumaker-0.99.7-2-i686.pkg.tar.gz<br />
Modificalo se ti sembra necessario.<br />
<br />
Rimuovi fluxconf e menumaker se vuoi un'installazione minima, sarà spiegato come utilizzarli ma non sono richiesti.<br />
<br />
===Avvio di Fluxbox===<br />
====Metodo 1: kdm/gdm====<br />
Entrambi aggiungeranno la voce fluxbox al menu. Selezionatela.<br />
<br />
''Note:'' Si dovrà avere un '''login manager''' attivato. Per istruzioni su come fare ciò, guarda [[Adding_a_login_manager_(KDM%2C_GDM%2C_or_XDM)_to_automatically_boot_on_startup|qui]].<br />
<br />
====Metodo 2: xinitrc====<br />
Nella tua home aggiungi questo codice alla fine del file .xinitrc<br />
exec fluxbox <br />
o se preferisci usare 'startfluxbox' inserisci:<br />
exec startfluxbox <br />
E' consigliato usare 'startfluxbox', perchè solo in questo modo il file ~/.fluxbox/startup verrà letto.<br />
Ricorda: ci può essere una solo linea exec in .xinitrc<br />
<br />
''Note'' : se si interrompe l'avvio, potresti avere problemi con locale.. Imposta LC_ALL al valore "C", ma se continua a non avviarsi. [http://bbs.archlinux.org/viewtopic.php?t=25797 1]<br />
Puoi avviare fluxbox con il comando startx.<br />
<br />
===Configurare Fluxbox===<br />
====Menu====<br />
=====Metodo veloce:=====<br />
dai il comando:<br />
fluxbox-generate_menu<br />
questo comando genera il file .fluxbox/menu/ basato sui programmi installati. C'è anche un "helper / regenerate menu" nel menu di fluxbox.<br />
<br />
======Archlinux xdg menu======<br />
Richiede [http://aur.archlinux.org/packages.php?do_Details=1&ID=10535&O=0&L=0&C=0&K=archlinux-xdg-menu&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=ndarchlinux-xdg-menu Archlinux xdg menu] <br><br />
xdg_menu --fullmenu --format fluxbox --root-menu /etc/xdg/menus/arch-applications.menu >~/.fluxbox/menu<br />
Suggerimento: sostituisci xterm/urxvt<br />
sed -i 's/xterm/urxvt/g' ~/.fluxbox/menu<br />
Altre informazioni<br />
xdg_menu --help<br />
Vedi anche: <br />
[[XdgMenu|Archlinux xdg menu]]<br />
<br />
=====Crea un menu personalizzato con fluxconf=====<br />
Per iniziare la sezione del menu di fluxconf, esegui::<br />
fluxmenu<br />
Nella finestra che apparirà, noterete tre colonne: Type, Title, e Command/Comment.<br><br />
Cliccare su una scrittura, vi permetterà di modificarla.<br><br />
Cliccare su "Add sub" aggiungerà un sottomenu.<br><br />
Cliccare su "Add exec" aggiungerà un comando da eseguire.<br><br />
<br />
la colonna type ha molte opzioni valide:<br />
#begin, indica l'inizio del file del menurequired to start the menu file. L'opzione title è il titolo del menu.<br><br />
#submenu, una "cartella" all'interno del menù. Title è il nome del suttomenù.<br><br />
#exec, un comando. Title è il testo che verrà visualizzato e Command/Comment è il comando da eseguire.<br />
#separator, un divisore all'interno del menù. Non ci sono argomenti per questa opzione.<br />
#workspaces, un elenco delle aree di lavoro e delle applicazioni in esecuzione in ciascuna di esse. Title è ciò che sarà mostrato all'utente.<br />
#stylesdir, una cartella contentente stili. Title è il percorso della cartella. E' raccomandabile mettere questo elemento in un sottomenù dedicato poiché può essere un cosa piuttosto "grande". Cartelle da utilizzare: /usr/share/fluxbox/styles ~/.fluxbox/styles .<br />
#config, un menù con diverse opzioni per modificare l'aspetto di fluxbox. Title è il nome del menù mostrato all'utente.<br />
#reconfig, ricarica il file di configurazione. Title è il nome mostrato all'utente.<br />
#restart, riavvia fluxbox. Title è il nome mostrato all'utente.<br />
#exit, termina fluxbox, si tornerà indietro al desktop manager o si terminerà X a seconda del metodo di avvio della sessione grafica che utilizziamo. Title è il nome mostrato all'utente.<br />
<br />
Ricorda di salvare prima di uscire.<br />
=====Manualmente=====<br />
Usa il comando:<br />
nano ~/.fluxbox/menu<br />
Ora puoi aggiungere le righe che vuoi secondo questo schema:<br />
[exec] (name) {command}<br />
Se vuoi creare un sottomenù scrivi:<br />
[submenu] (Name)<br />
...<br />
...<br />
[end]<br />
Una volta finito, salva ed esci. Non è necessario riavviare fluxbox.<br />
<br />
====Scorciatoie da tastiera (Hotkeys)====<br />
Fluxbox permette di configurare delle semplici scorciatoie da tastiera. Il file da editare è:<br />
~/.fluxbox/keys<br />
E' possibile configurare le scorciatoie anche attraverso una GUI lanciabile col comando:<br />
fluxkeys<br />
Il tasto Mod1 corrisponde ad Alt e Mod4 corrisponde a Meta (non è un tasto standard ma in molti casi è presente come tasto win)<br><br />
La prima casella di testo è per la scorciatoia, la seconda per l'azione. Seleziona execCommand per far corrispondere la scorciatoia al comando che scriverai nella terza casella di testo.<br />
<br />
Oltre alla funzione execCommand ce ne sono altre che possono essere utilizzate nella seconda casella di testo (comunque c'è un menù a tendina) <br />
====Aree di lavoro (workspaces)====<br />
Di default Fluxbox mette a disposizione dell'utente quattro aree di lavoro. Si visualizza l'una o l'altra con i tasti alt+F1-4 o con le freccie nella toolbar accanto a dove c'è scritto "one" (o il nome dell'area di lavoro)<br><br />
Click destro sul desktop e andando nel sottomenù Workspaces (utenti di menumaker: FluxBox>Workspaces, utenti di fluxconf: workspaces) potrai interagire con le aree di lavoro.<br />
<br />
Workspaces Menu:<br />
Icons - mostra le applicazioni minimizzate<br />
--separator--<br />
Workspaces names (default: one,two,three,four) - Mostra le applicazioni su quel desktop<br />
--separator--<br />
New Workspace - Aggiunge un'area di lavoro<br />
Edit Current workspace name - Ti permette di impostare il nome che vuoi per le tue aree di lavoro. Lo vedrai all'estremo sinistro della toolbar <br />
Remove Last - Rimuove l'ultima area di lavoro della lista, sposta tutte le applicazioni di quel desktop su quello precedente (che adesso è diventato l'ultimo)<br />
====Background====<br />
Per impostare lo sfondo è necessario che tu usi un programma dedicato che puoi installare con uno i questi pacchetti:<br />
*eterm (raccomandato)<br />
*feh (manca la trasparenza dei menù)<br />
ce ne sono anche altri, ma questi sono i due più utilizzati, per altri papabili puoi consultare la documentazione di fbsetbg nella sezione "Additional Links section"<br />
Per impostare lo sfondo:<br />
fbsetbg /path/to/background.image<br />
Al prossimo riavvio fluxbox non imposterà il tuo sfondo, ma puoi fare in modo che lo faccia aggiungendo il comando:<br />
fbsetbg -l<br />
al tuo script di avvio.<br />
(Questo ricorderà l'ultimo sfondo che hai impostato, quindi se non imposti uno sfondo col comando di prima, non avrai nessun risultato)<br />
<br />
Puoi anche aggiungere (o modificare) la seguente linea del file ~/.fluxbox/init in qualcosa del genere:<br />
session.screen0.rootCommand: fbsetbg /path/to/wallpaper<br />
<br />
O più semplicemente:<br />
session.screen0.rootCommand: fbsetbg -l<br />
<br />
<br />
Note aggiuntive per chi ama cambiare spesso sfondo.<br />
<br />
Metti questo sottomenù nel tuo menù di fluxbox:<br />
<br />
[submenu] (Backgrounds)<br />
[wallpapers] (~/.fluxbox/backgrounds)<br />
[wallpapers] (/usr/share/fluxbox/backgrounds)<br />
[end]<br />
<br />
Ora metto le tue immagini di sfondo in ~/.fluxbox/backgrounds o in una qualsiasi altra cartella che hai specificato, appariranno allo stesso modo dei tuoi stili.<br />
<br />
====Theming====<br />
Qui di seguito ci sono alcuni link a siti dove puoi trovare dei temi.<br><br />
Per installare un tema estrai l'archivio in una cartella per temi, quelle di default sono:<br />
*globale - /usr/share/fluxbox/styles <br />
*solo un utente - ~/.fluxbox/styles <br />
====Avvio automatico delle applicazioni====<br />
Chi fa uso di xinitrc dovrebbe inserire tutto il suo codice nel suo .xinitrc. Ad ogni modo, anche fluxbox offre la possibilità di avviare automaticamente le applicazioni.<br><br />
Il file ~/.fluxbox/startup è uno script per l'avvio automatico delle applicazioni contestualmente all'avvio di fluxbox.<br><br />
Il simbolo <nowiki>#</nowiki> precede un commento.<br><br />
<br />
Un file di esempio:<br />
fbsetbg -l <nowiki>#</nowiki> imosta l'ultimo sfondo utilizzato, molto utile e raccomandato.<br />
<nowiki>#</nowiki> Nei seguenti comandi il simbolo "e commerciale" (&) è richiesto per tutte quelle applicazioni <br />
<nowiki>#</nowiki> che non terminano immediatamente, se mancasse, lo script aspetterebbe il termine e non procederebbe <br />
<nowiki>#</nowiki> nell'esecuzione delle applicazioni successive, tra cui fluxbox stessa. <br />
idesk & <br />
xterm &<br />
<nowiki>#</nowiki> exec è per avviare fluxbox stessa, nonmettere (&) dopo uqesto comando o fluxbox terminerebbe appena avviata<br />
exec /usr/bin/fluxbox<br />
<nowiki>#</nowiki> o e vuoi tenere un log, decommenta il comando qui sotto e commenta questo sopra:<br />
<nowiki>#</nowiki> exec /usr/bin/fluxbox -log ~/.fluxbox/log<br />
===Link ad altre risorse===<br />
<br />
[http://fluxbox.sourceforge.net/ Fluxbox Homepage]<br><br />
[http://gentoo-wiki.com/HOWTO_Fluxbox gentoo-wiki Fluxbox HowTo]<br><br />
[http://www.gentoo.org/doc/en/fluxbox-config.xml gentoo Fluxbox Documentation]<br><br />
[http://box-look.org/ Themes for Fluxbox]<br><br />
[http://fluxbox-wiki.org/ Fluxbox Wiki]<br><br />
[http://www.xs4all.nl/~hanb/software/fbsetbg/fbsetbg.html fbsetbg documentation]<br></div>Psykopearhttps://wiki.archlinux.org/index.php?title=SLiM_(Italiano)&diff=42934SLiM (Italiano)2008-06-12T20:38:24Z<p>Psykopear: /* Singolo ambienti desktop */</p>
<hr />
<div>[[Category:Display managers (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|SLiM}}<br />
{{i18n_entry|简体中文|SLIM (简体中文)}}<br />
{{i18n_entry|Italiano|SLiM (Italiano)}}<br />
{{i18n_links_end}}<br />
<br />
=Introduzione=<br />
SLiM è l'acronimo di Simple Login Manager (semplice gestore di login). SLiM è un login manager semplice, leggero e facilmente configurabile, adatto per essere usato su piattaforme con poche risorse. SLiM è molto utile anche a chi vuole un login manager che non dipenda da gnome o kde, ed è perfetto per chi usa xfce, openbox fluxboc ecc.<br />
<br />
=Installazione=<br />
SLiM è installabile dai repo /extra:<br />
# pacman -S slim<br />
E c'è anche un pacchetto per i temi<br />
# pacman -S slim-themes<br />
<br />
=Configurazione=<br />
<br />
==Abilitare SLiM==<br />
Vedi [[Adding a login manager (KDM, GDM, or XDM) to automatically boot on startup]].<br />
<br />
==Singolo ambiente desktop==<br />
<br />
Per configurare SLiM per caricare un particolare ambiente, basta semplicemente editare il file ~./xinitrc, in modo che sia simile al seguente:<br />
<br />
<pre><br />
#!/bin/sh<br />
<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
<br />
exec [session-command]<br />
</pre><br />
<br />
*Nota: se non hai un file ~./xinitrc, ne puoi creare uno (per esempio con nano)<br />
<br />
Sostituisci '''''[session-command]''''' con il comando appropriato. Per esempio:<br />
<br />
Per lanciare Openbox:<br />
# Openbox<br />
exec openbox-session<br />
Per lanciare Fluxbox:<br />
# Fluxbox<br />
exec fluxbox<br />
# Either fluxbox or startfluxbox is acceptable<br />
Per lanciare Xfce:<br />
# Xfce<br />
exec startxfce4<br />
Per lanciare GNOME:<br />
# GNOME<br />
exec gnome-session<br />
Per lanciare KDE:<br />
# KDE<br />
exec startkde<br />
Se l'ambiente utilizzato non è elencato qui, fare riferimento alla documentazione del software.<br />
<br />
==Ambienti multipli==<br />
Se si ha il bisogno di caricare più ambienti desktop, SLiM può essere configurato in modo da poter scegliere quale.<br />
<br />
Put a case statement similar to this one in your /etc/X11/xinit/xinitrc file and edit the sessions variable in /etc/slim.conf. <br />
You can choose the session at login time by pressing F1. Note that this feature is experimental<br />
<br />
<pre><br />
# The following variable defines the session which is started if the user doesn't explicitly select a session<br />
<br />
DEFAULT_SESSION=twm<br />
<br />
case $1 in<br />
kde)<br />
exec startkde<br />
;;<br />
xfce4)<br />
exec startxfce4<br />
;;<br />
icewm)<br />
icewmbg &<br />
icewmtray &<br />
exec icewm<br />
;;<br />
wmaker)<br />
exec wmaker<br />
;;<br />
blackbox)<br />
exec blackbox<br />
;;<br />
*)<br />
exec $DEFAULT_SESSION<br />
;;<br />
esac<br />
</pre><br />
<br />
Source for sample: http://svn.berlios.de/svnroot/repos/slim/trunk/xinitrc.sample<br />
<br />
Slim documentation: http://slim.berlios.de/manual.php<br />
<br />
==Themes==<br />
<br />
Install the slim-themes package:<br />
<br />
pacman -S slim-themes archlinux-themes-slim<br />
<br />
Edit the current_theme line in /etc/slim.conf from "default" to one of your choice: <br />
nano /etc/slim.conf<br />
<br />
#current_theme default<br />
current_theme archlinux<br />
(Slim-themes located in /usr/share/slim/themes)<br />
<br />
To preview a theme, run:<br />
<br />
slim -p /usr/share/slim/themes/<theme name><br />
<br />
= Tips & Tricks =<br />
==Slim and Desktop share a theme==<br />
A simple way of sharing wallpaper between Slim and your desktop is to create a symbolic link from your desktop wallpaper file to the default Slim theme:<br />
mv /usr/share/slim/themes/default/background.jpg /usr/share/slim/themes/default/background.old.jpg<br />
ln -s /path/to/mywallpaper.jpg /usr/share/slim/themes/default/background.jpg<br />
Now your Slim theme and desktop wallpaper will be the same, smoothing the transition while loading the desktop. (Obviously you must keep the default theme setting in /etc/slim.conf for the above trick to work.)<br />
<br />
==Shutdown, Reboot, Suspend, Exit, Launch Terminal from SLiM==<br />
You may shutdown, reboot, suspend, exit or even launch a terminal from the SLiM login screen. To do so, enter the appropriate value in the username field, and the root password in the password field:<br />
<br />
*To launch a terminal, enter '''console''' as the username (defaults to xterm which must be installed separately... edit <tt>/etc/slim.conf</tt> to change terminal preference)<br />
<br />
*For shutdown, enter '''halt''' as the username<br />
<br />
*For reboot, enter '''reboot''' as the username<br />
<br />
*To exit to bash, enter '''exit''' as the username<br />
<br />
*For suspend, enter '''suspend''' as the username (Suspend is disabled by default, edit <tt>/etc/slim.conf</tt> as root to uncomment the <tt>suspend_cmd</tt> line and, if necessary modify the suspend command itself (e.g. change '''''/usr/sbin/suspend''''' to '''''sudo /usr/sbin/pm-suspend'''''))<br />
<br />
= Weblinks =<br />
[http://slim.berlios.de/ SLiM homepage]</div>Psykopearhttps://wiki.archlinux.org/index.php?title=SLiM_(Italiano)&diff=42933SLiM (Italiano)2008-06-12T20:38:01Z<p>Psykopear: New page: Category:Display managers (English) {{i18n_links_start}} {{i18n_entry|English|SLiM}} {{i18n_entry|简体中文|SLIM (简体中文)}} {{i18n_entry|Italiano|SLiM (Italiano)}} {{i18n_lin...</p>
<hr />
<div>[[Category:Display managers (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|SLiM}}<br />
{{i18n_entry|简体中文|SLIM (简体中文)}}<br />
{{i18n_entry|Italiano|SLiM (Italiano)}}<br />
{{i18n_links_end}}<br />
<br />
=Introduzione=<br />
SLiM è l'acronimo di Simple Login Manager (semplice gestore di login). SLiM è un login manager semplice, leggero e facilmente configurabile, adatto per essere usato su piattaforme con poche risorse. SLiM è molto utile anche a chi vuole un login manager che non dipenda da gnome o kde, ed è perfetto per chi usa xfce, openbox fluxboc ecc.<br />
<br />
=Installazione=<br />
SLiM è installabile dai repo /extra:<br />
# pacman -S slim<br />
E c'è anche un pacchetto per i temi<br />
# pacman -S slim-themes<br />
<br />
=Configurazione=<br />
<br />
==Abilitare SLiM==<br />
Vedi [[Adding a login manager (KDM, GDM, or XDM) to automatically boot on startup]].<br />
<br />
==Singolo ambienti desktop==<br />
<br />
Per configurare SLiM per caricare un particolare ambiente, basta semplicemente editare il file ~./xinitrc, in modo che sia simile al seguente:<br />
<br />
<pre><br />
#!/bin/sh<br />
<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
<br />
exec [session-command]<br />
</pre><br />
<br />
*Nota: se non hai un file ~./xinitrc, ne puoi creare uno (per esempio con nano)<br />
<br />
Sostituisci '''''[session-command]''''' con il comando appropriato. Per esempio:<br />
<br />
Per lanciare Openbox:<br />
# Openbox<br />
exec openbox-session<br />
Per lanciare Fluxbox:<br />
# Fluxbox<br />
exec fluxbox<br />
# Either fluxbox or startfluxbox is acceptable<br />
Per lanciare Xfce:<br />
# Xfce<br />
exec startxfce4<br />
Per lanciare GNOME:<br />
# GNOME<br />
exec gnome-session<br />
Per lanciare KDE:<br />
# KDE<br />
exec startkde<br />
Se l'ambiente utilizzato non è elencato qui, fare riferimento alla documentazione del software.<br />
<br />
==Ambienti multipli==<br />
Se si ha il bisogno di caricare più ambienti desktop, SLiM può essere configurato in modo da poter scegliere quale.<br />
<br />
Put a case statement similar to this one in your /etc/X11/xinit/xinitrc file and edit the sessions variable in /etc/slim.conf. <br />
You can choose the session at login time by pressing F1. Note that this feature is experimental<br />
<br />
<pre><br />
# The following variable defines the session which is started if the user doesn't explicitly select a session<br />
<br />
DEFAULT_SESSION=twm<br />
<br />
case $1 in<br />
kde)<br />
exec startkde<br />
;;<br />
xfce4)<br />
exec startxfce4<br />
;;<br />
icewm)<br />
icewmbg &<br />
icewmtray &<br />
exec icewm<br />
;;<br />
wmaker)<br />
exec wmaker<br />
;;<br />
blackbox)<br />
exec blackbox<br />
;;<br />
*)<br />
exec $DEFAULT_SESSION<br />
;;<br />
esac<br />
</pre><br />
<br />
Source for sample: http://svn.berlios.de/svnroot/repos/slim/trunk/xinitrc.sample<br />
<br />
Slim documentation: http://slim.berlios.de/manual.php<br />
<br />
==Themes==<br />
<br />
Install the slim-themes package:<br />
<br />
pacman -S slim-themes archlinux-themes-slim<br />
<br />
Edit the current_theme line in /etc/slim.conf from "default" to one of your choice: <br />
nano /etc/slim.conf<br />
<br />
#current_theme default<br />
current_theme archlinux<br />
(Slim-themes located in /usr/share/slim/themes)<br />
<br />
To preview a theme, run:<br />
<br />
slim -p /usr/share/slim/themes/<theme name><br />
<br />
= Tips & Tricks =<br />
==Slim and Desktop share a theme==<br />
A simple way of sharing wallpaper between Slim and your desktop is to create a symbolic link from your desktop wallpaper file to the default Slim theme:<br />
mv /usr/share/slim/themes/default/background.jpg /usr/share/slim/themes/default/background.old.jpg<br />
ln -s /path/to/mywallpaper.jpg /usr/share/slim/themes/default/background.jpg<br />
Now your Slim theme and desktop wallpaper will be the same, smoothing the transition while loading the desktop. (Obviously you must keep the default theme setting in /etc/slim.conf for the above trick to work.)<br />
<br />
==Shutdown, Reboot, Suspend, Exit, Launch Terminal from SLiM==<br />
You may shutdown, reboot, suspend, exit or even launch a terminal from the SLiM login screen. To do so, enter the appropriate value in the username field, and the root password in the password field:<br />
<br />
*To launch a terminal, enter '''console''' as the username (defaults to xterm which must be installed separately... edit <tt>/etc/slim.conf</tt> to change terminal preference)<br />
<br />
*For shutdown, enter '''halt''' as the username<br />
<br />
*For reboot, enter '''reboot''' as the username<br />
<br />
*To exit to bash, enter '''exit''' as the username<br />
<br />
*For suspend, enter '''suspend''' as the username (Suspend is disabled by default, edit <tt>/etc/slim.conf</tt> as root to uncomment the <tt>suspend_cmd</tt> line and, if necessary modify the suspend command itself (e.g. change '''''/usr/sbin/suspend''''' to '''''sudo /usr/sbin/pm-suspend'''''))<br />
<br />
= Weblinks =<br />
[http://slim.berlios.de/ SLiM homepage]</div>Psykopearhttps://wiki.archlinux.org/index.php?title=SLiM&diff=42932SLiM2008-06-12T20:26:57Z<p>Psykopear: </p>
<hr />
<div>[[Category:Display managers (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|SLiM}}<br />
{{i18n_entry|简体中文|SLIM (简体中文)}}<br />
{{i18n_entry|Italiano|SLiM (Italiano)}}<br />
{{i18n_links_end}}<br />
<br />
=Introduction=<br />
SLiM is an acronym for Simple Login Manager (SLiM). SLiM is simple, lightweight and easily configurable allowing it be used on low and high end systems with relative ease. SLiM is also very convenient for those who want a login manager without the dependencies of Gnome or KDE making it perfect for users running Xfce, Openbox, Fluxbox, etc. <br />
<br />
=Installation=<br />
SLiM is available from the /extra repositories:<br />
# pacman -S slim<br />
There is also a themes package:<br />
# pacman -S slim-themes<br />
<br />
=Configuration=<br />
<br />
==Enabling SLiM==<br />
Refer to [[Adding a login manager (KDM, GDM, or XDM) to automatically boot on startup]].<br />
<br />
==Single Environments==<br />
<br />
To configure SLiM to load a particular environment, simply edit '''~/.xinitrc''' to look like the following:<br />
<br />
<pre><br />
#!/bin/sh<br />
<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
<br />
exec [session-command]<br />
</pre><br />
<br />
*Note: If you do not have have a ~/.xinitrc file, you can create one (with, for example, nano).<br />
<br />
Replace '''''[session-command]''''' with the appropriate session command. For example:<br />
<br />
To launch Openbox:<br />
# Openbox<br />
exec openbox-session<br />
To launch Fluxbox:<br />
# Fluxbox<br />
exec fluxbox<br />
# Either fluxbox or startfluxbox is acceptable<br />
To launch Xfce:<br />
# Xfce<br />
exec startxfce4<br />
To launch GNOME:<br />
# GNOME<br />
exec gnome-session<br />
To launch KDE:<br />
# KDE<br />
exec startkde<br />
If your environment is not listed here, refer to the documentation provided by your software.<br />
<br />
==Multiple Environments==<br />
If you require the ability to load multiple desktop environments, SLiM can be setup to log you into whichever you choose.<br />
<br />
Put a case statement similar to this one in your /etc/X11/xinit/xinitrc file and edit the sessions variable in /etc/slim.conf. <br />
You can choose the session at login time by pressing F1. Note that this feature is experimental<br />
<br />
<pre><br />
# The following variable defines the session which is started if the user doesn't explicitly select a session<br />
<br />
DEFAULT_SESSION=twm<br />
<br />
case $1 in<br />
kde)<br />
exec startkde<br />
;;<br />
xfce4)<br />
exec startxfce4<br />
;;<br />
icewm)<br />
icewmbg &<br />
icewmtray &<br />
exec icewm<br />
;;<br />
wmaker)<br />
exec wmaker<br />
;;<br />
blackbox)<br />
exec blackbox<br />
;;<br />
*)<br />
exec $DEFAULT_SESSION<br />
;;<br />
esac<br />
</pre><br />
<br />
Source for sample: http://svn.berlios.de/svnroot/repos/slim/trunk/xinitrc.sample<br />
<br />
Slim documentation: http://slim.berlios.de/manual.php<br />
<br />
==Themes==<br />
<br />
Install the slim-themes package:<br />
<br />
pacman -S slim-themes archlinux-themes-slim<br />
<br />
Edit the current_theme line in /etc/slim.conf from "default" to one of your choice: <br />
nano /etc/slim.conf<br />
<br />
#current_theme default<br />
current_theme archlinux<br />
(Slim-themes located in /usr/share/slim/themes)<br />
<br />
To preview a theme, run:<br />
<br />
slim -p /usr/share/slim/themes/<theme name><br />
<br />
= Tips & Tricks =<br />
==Slim and Desktop share a theme==<br />
A simple way of sharing wallpaper between Slim and your desktop is to create a symbolic link from your desktop wallpaper file to the default Slim theme:<br />
mv /usr/share/slim/themes/default/background.jpg /usr/share/slim/themes/default/background.old.jpg<br />
ln -s /path/to/mywallpaper.jpg /usr/share/slim/themes/default/background.jpg<br />
Now your Slim theme and desktop wallpaper will be the same, smoothing the transition while loading the desktop. (Obviously you must keep the default theme setting in /etc/slim.conf for the above trick to work.)<br />
<br />
==Shutdown, Reboot, Suspend, Exit, Launch Terminal from SLiM==<br />
You may shutdown, reboot, suspend, exit or even launch a terminal from the SLiM login screen. To do so, enter the appropriate value in the username field, and the root password in the password field:<br />
<br />
*To launch a terminal, enter '''console''' as the username (defaults to xterm which must be installed separately... edit <tt>/etc/slim.conf</tt> to change terminal preference)<br />
<br />
*For shutdown, enter '''halt''' as the username<br />
<br />
*For reboot, enter '''reboot''' as the username<br />
<br />
*To exit to bash, enter '''exit''' as the username<br />
<br />
*For suspend, enter '''suspend''' as the username (Suspend is disabled by default, edit <tt>/etc/slim.conf</tt> as root to uncomment the <tt>suspend_cmd</tt> line and, if necessary modify the suspend command itself (e.g. change '''''/usr/sbin/suspend''''' to '''''sudo /usr/sbin/pm-suspend'''''))<br />
<br />
= Weblinks =<br />
[http://slim.berlios.de/ SLiM homepage]</div>Psykopearhttps://wiki.archlinux.org/index.php?title=SLiM&diff=42931SLiM2008-06-12T20:26:45Z<p>Psykopear: </p>
<hr />
<div>[[Category:Display managers (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|SLiM}}<br />
{{i18n_entry|简体中文|SLIM (简体中文)}}<br />
{{i18n_entry|Italian|SLiM (Italiano)}}<br />
{{i18n_links_end}}<br />
<br />
=Introduction=<br />
SLiM is an acronym for Simple Login Manager (SLiM). SLiM is simple, lightweight and easily configurable allowing it be used on low and high end systems with relative ease. SLiM is also very convenient for those who want a login manager without the dependencies of Gnome or KDE making it perfect for users running Xfce, Openbox, Fluxbox, etc. <br />
<br />
=Installation=<br />
SLiM is available from the /extra repositories:<br />
# pacman -S slim<br />
There is also a themes package:<br />
# pacman -S slim-themes<br />
<br />
=Configuration=<br />
<br />
==Enabling SLiM==<br />
Refer to [[Adding a login manager (KDM, GDM, or XDM) to automatically boot on startup]].<br />
<br />
==Single Environments==<br />
<br />
To configure SLiM to load a particular environment, simply edit '''~/.xinitrc''' to look like the following:<br />
<br />
<pre><br />
#!/bin/sh<br />
<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
<br />
exec [session-command]<br />
</pre><br />
<br />
*Note: If you do not have have a ~/.xinitrc file, you can create one (with, for example, nano).<br />
<br />
Replace '''''[session-command]''''' with the appropriate session command. For example:<br />
<br />
To launch Openbox:<br />
# Openbox<br />
exec openbox-session<br />
To launch Fluxbox:<br />
# Fluxbox<br />
exec fluxbox<br />
# Either fluxbox or startfluxbox is acceptable<br />
To launch Xfce:<br />
# Xfce<br />
exec startxfce4<br />
To launch GNOME:<br />
# GNOME<br />
exec gnome-session<br />
To launch KDE:<br />
# KDE<br />
exec startkde<br />
If your environment is not listed here, refer to the documentation provided by your software.<br />
<br />
==Multiple Environments==<br />
If you require the ability to load multiple desktop environments, SLiM can be setup to log you into whichever you choose.<br />
<br />
Put a case statement similar to this one in your /etc/X11/xinit/xinitrc file and edit the sessions variable in /etc/slim.conf. <br />
You can choose the session at login time by pressing F1. Note that this feature is experimental<br />
<br />
<pre><br />
# The following variable defines the session which is started if the user doesn't explicitly select a session<br />
<br />
DEFAULT_SESSION=twm<br />
<br />
case $1 in<br />
kde)<br />
exec startkde<br />
;;<br />
xfce4)<br />
exec startxfce4<br />
;;<br />
icewm)<br />
icewmbg &<br />
icewmtray &<br />
exec icewm<br />
;;<br />
wmaker)<br />
exec wmaker<br />
;;<br />
blackbox)<br />
exec blackbox<br />
;;<br />
*)<br />
exec $DEFAULT_SESSION<br />
;;<br />
esac<br />
</pre><br />
<br />
Source for sample: http://svn.berlios.de/svnroot/repos/slim/trunk/xinitrc.sample<br />
<br />
Slim documentation: http://slim.berlios.de/manual.php<br />
<br />
==Themes==<br />
<br />
Install the slim-themes package:<br />
<br />
pacman -S slim-themes archlinux-themes-slim<br />
<br />
Edit the current_theme line in /etc/slim.conf from "default" to one of your choice: <br />
nano /etc/slim.conf<br />
<br />
#current_theme default<br />
current_theme archlinux<br />
(Slim-themes located in /usr/share/slim/themes)<br />
<br />
To preview a theme, run:<br />
<br />
slim -p /usr/share/slim/themes/<theme name><br />
<br />
= Tips & Tricks =<br />
==Slim and Desktop share a theme==<br />
A simple way of sharing wallpaper between Slim and your desktop is to create a symbolic link from your desktop wallpaper file to the default Slim theme:<br />
mv /usr/share/slim/themes/default/background.jpg /usr/share/slim/themes/default/background.old.jpg<br />
ln -s /path/to/mywallpaper.jpg /usr/share/slim/themes/default/background.jpg<br />
Now your Slim theme and desktop wallpaper will be the same, smoothing the transition while loading the desktop. (Obviously you must keep the default theme setting in /etc/slim.conf for the above trick to work.)<br />
<br />
==Shutdown, Reboot, Suspend, Exit, Launch Terminal from SLiM==<br />
You may shutdown, reboot, suspend, exit or even launch a terminal from the SLiM login screen. To do so, enter the appropriate value in the username field, and the root password in the password field:<br />
<br />
*To launch a terminal, enter '''console''' as the username (defaults to xterm which must be installed separately... edit <tt>/etc/slim.conf</tt> to change terminal preference)<br />
<br />
*For shutdown, enter '''halt''' as the username<br />
<br />
*For reboot, enter '''reboot''' as the username<br />
<br />
*To exit to bash, enter '''exit''' as the username<br />
<br />
*For suspend, enter '''suspend''' as the username (Suspend is disabled by default, edit <tt>/etc/slim.conf</tt> as root to uncomment the <tt>suspend_cmd</tt> line and, if necessary modify the suspend command itself (e.g. change '''''/usr/sbin/suspend''''' to '''''sudo /usr/sbin/pm-suspend'''''))<br />
<br />
= Weblinks =<br />
[http://slim.berlios.de/ SLiM homepage]</div>Psykopearhttps://wiki.archlinux.org/index.php?title=SLiM&diff=42930SLiM2008-06-12T20:26:18Z<p>Psykopear: </p>
<hr />
<div>[[Category:Display managers (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|SLiM}}<br />
{{i18n_entry|简体中文|SLIM (简体中文)}}<br />
{{i18n_entry|Italiano|SLiM (Italiano=}}<br />
{{i18n_links_end}}<br />
<br />
=Introduction=<br />
SLiM is an acronym for Simple Login Manager (SLiM). SLiM is simple, lightweight and easily configurable allowing it be used on low and high end systems with relative ease. SLiM is also very convenient for those who want a login manager without the dependencies of Gnome or KDE making it perfect for users running Xfce, Openbox, Fluxbox, etc. <br />
<br />
=Installation=<br />
SLiM is available from the /extra repositories:<br />
# pacman -S slim<br />
There is also a themes package:<br />
# pacman -S slim-themes<br />
<br />
=Configuration=<br />
<br />
==Enabling SLiM==<br />
Refer to [[Adding a login manager (KDM, GDM, or XDM) to automatically boot on startup]].<br />
<br />
==Single Environments==<br />
<br />
To configure SLiM to load a particular environment, simply edit '''~/.xinitrc''' to look like the following:<br />
<br />
<pre><br />
#!/bin/sh<br />
<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
<br />
exec [session-command]<br />
</pre><br />
<br />
*Note: If you do not have have a ~/.xinitrc file, you can create one (with, for example, nano).<br />
<br />
Replace '''''[session-command]''''' with the appropriate session command. For example:<br />
<br />
To launch Openbox:<br />
# Openbox<br />
exec openbox-session<br />
To launch Fluxbox:<br />
# Fluxbox<br />
exec fluxbox<br />
# Either fluxbox or startfluxbox is acceptable<br />
To launch Xfce:<br />
# Xfce<br />
exec startxfce4<br />
To launch GNOME:<br />
# GNOME<br />
exec gnome-session<br />
To launch KDE:<br />
# KDE<br />
exec startkde<br />
If your environment is not listed here, refer to the documentation provided by your software.<br />
<br />
==Multiple Environments==<br />
If you require the ability to load multiple desktop environments, SLiM can be setup to log you into whichever you choose.<br />
<br />
Put a case statement similar to this one in your /etc/X11/xinit/xinitrc file and edit the sessions variable in /etc/slim.conf. <br />
You can choose the session at login time by pressing F1. Note that this feature is experimental<br />
<br />
<pre><br />
# The following variable defines the session which is started if the user doesn't explicitly select a session<br />
<br />
DEFAULT_SESSION=twm<br />
<br />
case $1 in<br />
kde)<br />
exec startkde<br />
;;<br />
xfce4)<br />
exec startxfce4<br />
;;<br />
icewm)<br />
icewmbg &<br />
icewmtray &<br />
exec icewm<br />
;;<br />
wmaker)<br />
exec wmaker<br />
;;<br />
blackbox)<br />
exec blackbox<br />
;;<br />
*)<br />
exec $DEFAULT_SESSION<br />
;;<br />
esac<br />
</pre><br />
<br />
Source for sample: http://svn.berlios.de/svnroot/repos/slim/trunk/xinitrc.sample<br />
<br />
Slim documentation: http://slim.berlios.de/manual.php<br />
<br />
==Themes==<br />
<br />
Install the slim-themes package:<br />
<br />
pacman -S slim-themes archlinux-themes-slim<br />
<br />
Edit the current_theme line in /etc/slim.conf from "default" to one of your choice: <br />
nano /etc/slim.conf<br />
<br />
#current_theme default<br />
current_theme archlinux<br />
(Slim-themes located in /usr/share/slim/themes)<br />
<br />
To preview a theme, run:<br />
<br />
slim -p /usr/share/slim/themes/<theme name><br />
<br />
= Tips & Tricks =<br />
==Slim and Desktop share a theme==<br />
A simple way of sharing wallpaper between Slim and your desktop is to create a symbolic link from your desktop wallpaper file to the default Slim theme:<br />
mv /usr/share/slim/themes/default/background.jpg /usr/share/slim/themes/default/background.old.jpg<br />
ln -s /path/to/mywallpaper.jpg /usr/share/slim/themes/default/background.jpg<br />
Now your Slim theme and desktop wallpaper will be the same, smoothing the transition while loading the desktop. (Obviously you must keep the default theme setting in /etc/slim.conf for the above trick to work.)<br />
<br />
==Shutdown, Reboot, Suspend, Exit, Launch Terminal from SLiM==<br />
You may shutdown, reboot, suspend, exit or even launch a terminal from the SLiM login screen. To do so, enter the appropriate value in the username field, and the root password in the password field:<br />
<br />
*To launch a terminal, enter '''console''' as the username (defaults to xterm which must be installed separately... edit <tt>/etc/slim.conf</tt> to change terminal preference)<br />
<br />
*For shutdown, enter '''halt''' as the username<br />
<br />
*For reboot, enter '''reboot''' as the username<br />
<br />
*To exit to bash, enter '''exit''' as the username<br />
<br />
*For suspend, enter '''suspend''' as the username (Suspend is disabled by default, edit <tt>/etc/slim.conf</tt> as root to uncomment the <tt>suspend_cmd</tt> line and, if necessary modify the suspend command itself (e.g. change '''''/usr/sbin/suspend''''' to '''''sudo /usr/sbin/pm-suspend'''''))<br />
<br />
= Weblinks =<br />
[http://slim.berlios.de/ SLiM homepage]</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Very_Secure_FTP_Daemon_(Italiano)&diff=39775Very Secure FTP Daemon (Italiano)2008-04-13T08:21:51Z<p>Psykopear: </p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|English|Very Secure FTP Daemon}}<br />
{{i18n_entry|Русский|Very Secure FTP Daemon (russian)}}<br />
{{i18n_entry|Italiano|Very secure ftp daemon (Italian)}}<br />
{{i18n_links_end}}<br />
<br />
vsftpd sta per "Very secure ftp daemon" (Demone ftp molto sicuro). E' un piccolo (ed efficente) server ftp di cui potresti avere bisogno.<br />
<br />
Può funzionare sia con che senza xinetd, ma verrà descritto solo il metodo senza xinetd.<br />
<br />
Prima di tutto, installa il pacchetto necessario con pacman<br />
pacman -Sy vsftpd<br />
<br />
/etc/vsftpd.conf e' un file di configurazione molto ben documentato, ma queste sono le cose basilar da configurare (per il resto leggi i commenti del file)<br />
<pre><br />
listen=YES<br />
anonymous_enable=YES # Se vuoi che si possa accedere al server in modo anonimo<br />
local_enable=YES # Questo permette agli utenti locali di accedere al server ftp<br />
write_enable=YES # Stai attento ad usare questo con anonymous_enable=YES<br />
tcp_wrappers=YES # Usa tcp_wrappers per controllare le connessioni. <br />
</pre><br />
<br />
Infine aggiungi vsftpd ai demoni nella riga DAEMON= nell'/etc/rc.conf<br />
<br />
Una volta riavviato, potrai accedere al tuo server ftp dal link ftp://localhost, mentre per gli utilizzatori esterni il punto di accesso sarà ftp://tuo_ip (l'ip lo puoi controllare con ifconfig).<br />
<br />
Per aggiungere dei file al server, basta metterli nella cartella /home/ftp che viene creata con l'installazione di arch. Se si vuole poter aggiungere i file in tale cartella anche da utente, basta cambiargli proprietario con <br />
<br />
chown nomeutente:users /home/ftp<br />
<br />
NOTA per gli utenti fastweb: essendo fastweb una rete chiusa, potranno accedere al tuo server esclusivamente gli utenti interni alla rete fastweb, a meno che non si paghi per ottenere un ip pubblico o non si usi una vpn con hamachi</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Very_Secure_FTP_Daemon&diff=39774Very Secure FTP Daemon2008-04-13T08:21:31Z<p>Psykopear: </p>
<hr />
<div>[[Category:Networking (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Very Secure FTP Daemon}}<br />
{{i18n_entry|Italiano|Very secure ftp daemon (Italian)}}<br />
{{i18n_entry|Русский|Very Secure FTP Daemon (russian)}}<br />
{{i18n_links_end}}<br />
vsftpd is the "very secure ftp daemon." It's a nice little ftp server should you need one.<br />
<br />
It will run either with or without xinetd, but I'll describe how to use it with xinetd.<br />
<br />
First, grab the packages you'll need with pacman:<br />
pacman -Sy xinetd vsftpd<br />
<br />
The following config files will need to be changed:<br />
<br />
/etc/xinetd.d/vsftpd:<br />
<pre><br />
service ftp<br />
{<br />
socket_type = stream<br />
wait = no<br />
user = root<br />
server = /usr/sbin/vsftpd<br />
log_on_success += HOST DURATION<br />
log_on_failure += HOST<br />
disable = no<br />
}<br />
</pre><br />
<br />
/etc/vsftpd.conf is a very well documented config file, but here are the basics you'll probably want to set:<br />
<pre><br />
anonymous_enable=NO # Assuming you don't want anonymous ftp<br />
local_enable=YES # This lets local machine users log in<br />
write_enable=YES # Be really careful using this with anonymous_enable=YES<br />
tcp_wrappers=YES # Use tcp_wrappers to control connections. Then allow in hosts.allow<br />
</pre><br />
<br />
Finally, add xinetd to your daemons line in /etc/rc.conf. You don't need to add vsftpd, as it will be called by xinetd whenever necessary.<br />
<br />
If you get errors like <br />
500 OOPS: cap_set_proc<br />
when connecting to the server, you need to add ''capability'' in MODULES= line in /etc/rc.conf.</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Very_Secure_FTP_Daemon_(Italiano)&diff=39772Very Secure FTP Daemon (Italiano)2008-04-13T08:21:04Z<p>Psykopear: Vsftpd(Italiano) moved to Very secure ftp daemon (Italian): Adattamento ai nomi delle altre lingue</p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|English|Very Secure FTP Daemon}}<br />
{{i18n_entry|Русский|Very Secure FTP Daemon (russian)}}<br />
{{i18n_entry|Italiano|Vsftpd(Italiano)}}<br />
{{i18n_links_end}}<br />
<br />
vsftpd sta per "Very secure ftp daemon" (Demone ftp molto sicuro). E' un piccolo (ed efficente) server ftp di cui potresti avere bisogno.<br />
<br />
Può funzionare sia con che senza xinetd, ma verrà descritto solo il metodo senza xinetd.<br />
<br />
Prima di tutto, installa il pacchetto necessario con pacman<br />
pacman -Sy vsftpd<br />
<br />
/etc/vsftpd.conf e' un file di configurazione molto ben documentato, ma queste sono le cose basilar da configurare (per il resto leggi i commenti del file)<br />
<pre><br />
listen=YES<br />
anonymous_enable=YES # Se vuoi che si possa accedere al server in modo anonimo<br />
local_enable=YES # Questo permette agli utenti locali di accedere al server ftp<br />
write_enable=YES # Stai attento ad usare questo con anonymous_enable=YES<br />
tcp_wrappers=YES # Usa tcp_wrappers per controllare le connessioni. <br />
</pre><br />
<br />
Infine aggiungi vsftpd ai demoni nella riga DAEMON= nell'/etc/rc.conf<br />
<br />
Una volta riavviato, potrai accedere al tuo server ftp dal link ftp://localhost, mentre per gli utilizzatori esterni il punto di accesso sarà ftp://tuo_ip (l'ip lo puoi controllare con ifconfig).<br />
<br />
Per aggiungere dei file al server, basta metterli nella cartella /home/ftp che viene creata con l'installazione di arch. Se si vuole poter aggiungere i file in tale cartella anche da utente, basta cambiargli proprietario con <br />
<br />
chown nomeutente:users /home/ftp<br />
<br />
NOTA per gli utenti fastweb: essendo fastweb una rete chiusa, potranno accedere al tuo server esclusivamente gli utenti interni alla rete fastweb, a meno che non si paghi per ottenere un ip pubblico o non si usi una vpn con hamachi</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Very_Secure_FTP_Daemon&diff=39771Very Secure FTP Daemon2008-04-13T08:18:44Z<p>Psykopear: </p>
<hr />
<div>[[Category:Networking (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Very Secure FTP Daemon}}<br />
{{i18n_entry|Italiano|Vsftpd(Italiano)}}<br />
{{i18n_entry|Русский|Very Secure FTP Daemon (russian)}}<br />
{{i18n_links_end}}<br />
vsftpd is the "very secure ftp daemon." It's a nice little ftp server should you need one.<br />
<br />
It will run either with or without xinetd, but I'll describe how to use it with xinetd.<br />
<br />
First, grab the packages you'll need with pacman:<br />
pacman -Sy xinetd vsftpd<br />
<br />
The following config files will need to be changed:<br />
<br />
/etc/xinetd.d/vsftpd:<br />
<pre><br />
service ftp<br />
{<br />
socket_type = stream<br />
wait = no<br />
user = root<br />
server = /usr/sbin/vsftpd<br />
log_on_success += HOST DURATION<br />
log_on_failure += HOST<br />
disable = no<br />
}<br />
</pre><br />
<br />
/etc/vsftpd.conf is a very well documented config file, but here are the basics you'll probably want to set:<br />
<pre><br />
anonymous_enable=NO # Assuming you don't want anonymous ftp<br />
local_enable=YES # This lets local machine users log in<br />
write_enable=YES # Be really careful using this with anonymous_enable=YES<br />
tcp_wrappers=YES # Use tcp_wrappers to control connections. Then allow in hosts.allow<br />
</pre><br />
<br />
Finally, add xinetd to your daemons line in /etc/rc.conf. You don't need to add vsftpd, as it will be called by xinetd whenever necessary.<br />
<br />
If you get errors like <br />
500 OOPS: cap_set_proc<br />
when connecting to the server, you need to add ''capability'' in MODULES= line in /etc/rc.conf.</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Very_Secure_FTP_Daemon_(Italiano)&diff=39770Very Secure FTP Daemon (Italiano)2008-04-13T08:18:22Z<p>Psykopear: </p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|English|Very Secure FTP Daemon}}<br />
{{i18n_entry|Русский|Very Secure FTP Daemon (russian)}}<br />
{{i18n_entry|Italiano|Vsftpd(Italiano)}}<br />
{{i18n_links_end}}<br />
<br />
vsftpd sta per "Very secure ftp daemon" (Demone ftp molto sicuro). E' un piccolo (ed efficente) server ftp di cui potresti avere bisogno.<br />
<br />
Può funzionare sia con che senza xinetd, ma verrà descritto solo il metodo senza xinetd.<br />
<br />
Prima di tutto, installa il pacchetto necessario con pacman<br />
pacman -Sy vsftpd<br />
<br />
/etc/vsftpd.conf e' un file di configurazione molto ben documentato, ma queste sono le cose basilar da configurare (per il resto leggi i commenti del file)<br />
<pre><br />
listen=YES<br />
anonymous_enable=YES # Se vuoi che si possa accedere al server in modo anonimo<br />
local_enable=YES # Questo permette agli utenti locali di accedere al server ftp<br />
write_enable=YES # Stai attento ad usare questo con anonymous_enable=YES<br />
tcp_wrappers=YES # Usa tcp_wrappers per controllare le connessioni. <br />
</pre><br />
<br />
Infine aggiungi vsftpd ai demoni nella riga DAEMON= nell'/etc/rc.conf<br />
<br />
Una volta riavviato, potrai accedere al tuo server ftp dal link ftp://localhost, mentre per gli utilizzatori esterni il punto di accesso sarà ftp://tuo_ip (l'ip lo puoi controllare con ifconfig).<br />
<br />
Per aggiungere dei file al server, basta metterli nella cartella /home/ftp che viene creata con l'installazione di arch. Se si vuole poter aggiungere i file in tale cartella anche da utente, basta cambiargli proprietario con <br />
<br />
chown nomeutente:users /home/ftp<br />
<br />
NOTA per gli utenti fastweb: essendo fastweb una rete chiusa, potranno accedere al tuo server esclusivamente gli utenti interni alla rete fastweb, a meno che non si paghi per ottenere un ip pubblico o non si usi una vpn con hamachi</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Very_Secure_FTP_Daemon_(Italiano)&diff=39769Very Secure FTP Daemon (Italiano)2008-04-13T08:17:18Z<p>Psykopear: </p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|English|Very Secure FTP Daemon}}<br />
{{i18n_entry|Русский|Very Secure FTP Daemon (russian)}}<br />
{{i18n_entry|Italiano|Very Secure FTP Daemon (Italian)}}<br />
{{i18n_links_end}}<br />
<br />
vsftpd sta per "Very secure ftp daemon" (Demone ftp molto sicuro). E' un piccolo (ed efficente) server ftp di cui potresti avere bisogno.<br />
<br />
Può funzionare sia con che senza xinetd, ma verrà descritto solo il metodo senza xinetd.<br />
<br />
Prima di tutto, installa il pacchetto necessario con pacman<br />
pacman -Sy vsftpd<br />
<br />
/etc/vsftpd.conf e' un file di configurazione molto ben documentato, ma queste sono le cose basilar da configurare (per il resto leggi i commenti del file)<br />
<pre><br />
listen=YES<br />
anonymous_enable=YES # Se vuoi che si possa accedere al server in modo anonimo<br />
local_enable=YES # Questo permette agli utenti locali di accedere al server ftp<br />
write_enable=YES # Stai attento ad usare questo con anonymous_enable=YES<br />
tcp_wrappers=YES # Usa tcp_wrappers per controllare le connessioni. <br />
</pre><br />
<br />
Infine aggiungi vsftpd ai demoni nella riga DAEMON= nell'/etc/rc.conf<br />
<br />
Una volta riavviato, potrai accedere al tuo server ftp dal link ftp://localhost, mentre per gli utilizzatori esterni il punto di accesso sarà ftp://tuo_ip (l'ip lo puoi controllare con ifconfig).<br />
<br />
Per aggiungere dei file al server, basta metterli nella cartella /home/ftp che viene creata con l'installazione di arch. Se si vuole poter aggiungere i file in tale cartella anche da utente, basta cambiargli proprietario con <br />
<br />
chown nomeutente:users /home/ftp<br />
<br />
NOTA per gli utenti fastweb: essendo fastweb una rete chiusa, potranno accedere al tuo server esclusivamente gli utenti interni alla rete fastweb, a meno che non si paghi per ottenere un ip pubblico o non si usi una vpn con hamachi</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Very_Secure_FTP_Daemon&diff=39768Very Secure FTP Daemon2008-04-13T08:15:43Z<p>Psykopear: </p>
<hr />
<div>[[Category:Networking (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Very Secure FTP Daemon}}<br />
{{i18n_entry|Italiano|Very Secure FTP Daemon (Italiano)}}<br />
{{i18n_entry|Русский|Very Secure FTP Daemon (russian)}}<br />
{{i18n_links_end}}<br />
vsftpd is the "very secure ftp daemon." It's a nice little ftp server should you need one.<br />
<br />
It will run either with or without xinetd, but I'll describe how to use it with xinetd.<br />
<br />
First, grab the packages you'll need with pacman:<br />
pacman -Sy xinetd vsftpd<br />
<br />
The following config files will need to be changed:<br />
<br />
/etc/xinetd.d/vsftpd:<br />
<pre><br />
service ftp<br />
{<br />
socket_type = stream<br />
wait = no<br />
user = root<br />
server = /usr/sbin/vsftpd<br />
log_on_success += HOST DURATION<br />
log_on_failure += HOST<br />
disable = no<br />
}<br />
</pre><br />
<br />
/etc/vsftpd.conf is a very well documented config file, but here are the basics you'll probably want to set:<br />
<pre><br />
anonymous_enable=NO # Assuming you don't want anonymous ftp<br />
local_enable=YES # This lets local machine users log in<br />
write_enable=YES # Be really careful using this with anonymous_enable=YES<br />
tcp_wrappers=YES # Use tcp_wrappers to control connections. Then allow in hosts.allow<br />
</pre><br />
<br />
Finally, add xinetd to your daemons line in /etc/rc.conf. You don't need to add vsftpd, as it will be called by xinetd whenever necessary.<br />
<br />
If you get errors like <br />
500 OOPS: cap_set_proc<br />
when connecting to the server, you need to add ''capability'' in MODULES= line in /etc/rc.conf.</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Very_Secure_FTP_Daemon&diff=39767Very Secure FTP Daemon2008-04-13T08:14:48Z<p>Psykopear: </p>
<hr />
<div>[[Category:Networking (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Very Secure FTP Daemon}}<br />
{{i18n_entry|Italiano|Very Secure FTP Daemon (Italian)}}<br />
{{i18n_entry|Русский|Very Secure FTP Daemon (russian)}}<br />
{{i18n_links_end}}<br />
vsftpd is the "very secure ftp daemon." It's a nice little ftp server should you need one.<br />
<br />
It will run either with or without xinetd, but I'll describe how to use it with xinetd.<br />
<br />
First, grab the packages you'll need with pacman:<br />
pacman -Sy xinetd vsftpd<br />
<br />
The following config files will need to be changed:<br />
<br />
/etc/xinetd.d/vsftpd:<br />
<pre><br />
service ftp<br />
{<br />
socket_type = stream<br />
wait = no<br />
user = root<br />
server = /usr/sbin/vsftpd<br />
log_on_success += HOST DURATION<br />
log_on_failure += HOST<br />
disable = no<br />
}<br />
</pre><br />
<br />
/etc/vsftpd.conf is a very well documented config file, but here are the basics you'll probably want to set:<br />
<pre><br />
anonymous_enable=NO # Assuming you don't want anonymous ftp<br />
local_enable=YES # This lets local machine users log in<br />
write_enable=YES # Be really careful using this with anonymous_enable=YES<br />
tcp_wrappers=YES # Use tcp_wrappers to control connections. Then allow in hosts.allow<br />
</pre><br />
<br />
Finally, add xinetd to your daemons line in /etc/rc.conf. You don't need to add vsftpd, as it will be called by xinetd whenever necessary.<br />
<br />
If you get errors like <br />
500 OOPS: cap_set_proc<br />
when connecting to the server, you need to add ''capability'' in MODULES= line in /etc/rc.conf.</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Very_Secure_FTP_Daemon&diff=39766Very Secure FTP Daemon2008-04-13T08:12:15Z<p>Psykopear: </p>
<hr />
<div>[[Category:Networking (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Very Secure FTP Daemon}}<br />
{{i18n_entry|Italiano|Very Secure FTP Daemon}}<br />
{{i18n_entry|Русский|Very Secure FTP Daemon (russian)}}<br />
{{i18n_links_end}}<br />
vsftpd is the "very secure ftp daemon." It's a nice little ftp server should you need one.<br />
<br />
It will run either with or without xinetd, but I'll describe how to use it with xinetd.<br />
<br />
First, grab the packages you'll need with pacman:<br />
pacman -Sy xinetd vsftpd<br />
<br />
The following config files will need to be changed:<br />
<br />
/etc/xinetd.d/vsftpd:<br />
<pre><br />
service ftp<br />
{<br />
socket_type = stream<br />
wait = no<br />
user = root<br />
server = /usr/sbin/vsftpd<br />
log_on_success += HOST DURATION<br />
log_on_failure += HOST<br />
disable = no<br />
}<br />
</pre><br />
<br />
/etc/vsftpd.conf is a very well documented config file, but here are the basics you'll probably want to set:<br />
<pre><br />
anonymous_enable=NO # Assuming you don't want anonymous ftp<br />
local_enable=YES # This lets local machine users log in<br />
write_enable=YES # Be really careful using this with anonymous_enable=YES<br />
tcp_wrappers=YES # Use tcp_wrappers to control connections. Then allow in hosts.allow<br />
</pre><br />
<br />
Finally, add xinetd to your daemons line in /etc/rc.conf. You don't need to add vsftpd, as it will be called by xinetd whenever necessary.<br />
<br />
If you get errors like <br />
500 OOPS: cap_set_proc<br />
when connecting to the server, you need to add ''capability'' in MODULES= line in /etc/rc.conf.</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Games_(Italiano)&diff=39012Games (Italiano)2008-03-22T16:06:01Z<p>Psykopear: \* Giochi per arch *\</p>
<hr />
<div>= Giochi in arch =<br />
Questa pagina nasce con l'intento di fare un elenco serio e completo dei migliori titoli testati e funzionanti su Arch (a 32 e a 64 bit)<br />
<br />
= Giochi nativi =<br />
== Arch 32-bit ==<br />
DA INIZIARE<br />
== Arch 64-bit ==<br />
DA INIZIARE<br />
<br />
= Giochi emulati con wine =<br />
== Arch 32-bit ==<br />
DA INIZIARE<br />
== Arch 64-bit ==</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Arch_Build_System_(Italiano)&diff=38956Arch Build System (Italiano)2008-03-21T15:23:11Z<p>Psykopear: /* Why would I want to use ABS? */</p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|Česky|ABS - The Arch Build System (Česky)}}<br />
{{i18n_entry|Dansk|ABS_(Dansk)}}<br />
{{i18n_entry|English|ABS - The Arch Build System}}<br />
{{i18n_entry|正體中文|ABS - The Arch Build System (正體中文)}}<br />
{{i18n_entry|Polski|ABS - The Arch Build System (Polski)}}<br />
{{i18n_entry|Русский|ABS - The Arch Build System (Russian)}}<br />
{{i18n_entry|简体中文|ABS (简体中文)}}<br />
{{i18n_entry|Italiano|ABS - Il Sistema Di Compilazione di Arch (Italiano)}}<br />
{{i18n_links_end}}<br />
<br />
<br />
==== Cosa è ABS? ====<br />
ABS è l'acronimo di "Arch Build System", Sistema di costruzione (dei pacchetti) di arch. E' un sistema per fare pacchetti del codice sorgente. Mentre pacman è il tool di Arch specializzato nella gestione dei pacchetti binari (inclusi i pacchetti fatti con ABS), ABS è il tool specializzato nella compilazione dei sorgenti in un pacchetto .pkg.tar.gz installabile<br />
=====Cos'è un sistema ports-like?=====<br />
"Ports" è il sistema usato da FreeBSD che permette di scaricare, scompattare, patchare, compilare e installare i pacchetti con i codici sorgenti. "Un 'port' è solo una piccola cartella nel computer dell'utente, chiamata come il corrispondente software che ci verrà installato, che contiene un po' di file con le istruzioni per scaricare ed installare il pacchetto dai sorgenti", solitamente entrando nella cartella, o port, e dando 'make' e 'make install'. Il sistema si occuperà di scaricare, compilare ed installare il software desiderato.<br />
====='''ABS''' è un concetto simile.=====<br />
"ABS" è costituito da un'albero di dircetory (the "ABS Tree"), che sta in /var/abs, che contiene molte sottodirectory, ognuna dentro una categoria, e ognuna chiamata con il rispettivo pacchetto installabile contenuto al suo interno. Si può considerare ogni sottodirectory chiamata come un pacchetto un "ABS", più o meno allo stesso modo con cui ci si potrebbe riferire ad un "Port". Questi "ABS", o sottodirectory, "non contengono il pacchetto del software, nè tantomeno il codice sorgente", bensì contengono un file "PKGBUILD" (e a volte altri file). Un PKGBUILD è un semplice script, un file di testo contenente le istruzioni per la compilazione e la pacchettizzazione, ma anche l'url dell'apposito pacchetto di sorgenti da scaricare. "I componenti più importanti di ABS sono proprio i PKGBUILD"<br />
<br />
=====Veloce esempio=====<br />
Avviare "ABS" da root crea l'albero di ABS sincronizzandolo con il sistema cvs. Se volessi compilare nano da sorgenti, per esempio, dovresti copiare /var/abs/core/base/nano in una cartella di lavoro, entrare in quella cartella e dare "maepkg". È semplice come sembra. Makepkg si occuperà di leggere ed eseguire le istruzioni contenute nel PKGBUILD. Il pacchetto appropriato sarà scaricato, scompattato, compilato secondo le CFLAGS specificato nel file /etc/makepkg.conf, e infine compresse in u pacchetto con l'estensione .pkg.tar.gz, come per le istruzioni del PKGBUILD. L'installazione è altrettanto semplice, basta dare 'pacman -U nano.pkg.tar.gz'. La rimozione del pacchetto è gestita da pacman.<br />
<br />
Il PKGBUILD e molti altri file, ovviamente, possono essere modificati secondo le tue esigenze, e tu puoi decidere di usare la funzione makepkg di ABS per fare i tuoi pacchetti personalizzati dai sorgenti. (Guarda il prototipo di PKGBUILD e installa i fil sotto /var/abs/core/)<br />
-----<br />
"Con l'"ABS tree" a posto, un utente Arch ha tutto il software per Arch disponibile a portata di mano, da compilare da sorgenti e creare in automatico pacchetti .pkg.tar.gz<br />
<br />
=====Descrizione generale di ABS=====<br />
"ABS" potrebbe essere usato come un termine "ad ombrello", in quanto include, ed è formato, da molti altri componenti. Pertanto, parlando in termini non proprio tecnici, "ABS" fò riferimento alla seguente struttura come un toolkit completo:<br />
<br />
* '''L'albero ABS:''' La struttura di directory di ABS sotto /var/abs/. Contiene molte sottodirectory, chiamate con il nome di ogni software cvs disponibile per arch, ma non i pacchetti stessi<br />
* '''ABS:''' Un insieme do strumenti per scaricare e costruire PKGBUILD ufficiali di Arch. Sono inclusi anche dei PKGBUILD di esempio<br />
* '''PKGBUILG:''' File di testo che si trovano nelle directory di ABS, con le istruzioni per costruire i pacchetti e l'url dei sorgenti.<br />
* '''[[makepkg]]:''' Il comando da shell di ABS che legge il PKGBUILD, compila il sorgente e crea il .pkg.tar.gz<br />
* '''[[Pacman]]:''' Pacman è completamente separato, ma è necessario invocarlo o dal makepkg o manualmente, per installare e rimuovere i pacchetti costruiti, e per risolvere le dipendenze<br />
* '''[[AUR]]:''' Il repository degli utenti della comunità di Arcch è separato da ABS, ma i PKGBUILD non supportati di [[AUR]] possono essere usati con il tool makepkg di ABS, per compilare e impacchettare il software. AUR contiene PKGBUILD degli utenti che potrebbero non essere presenti come pacchetti ufficiali di Arch<br />
<br />
==== Perchè dovrei usare ABS? ====<br />
L'"Arch Buil Sustem" (abbreviato con ABS) è usato per<br />
<br />
* Creare nuovi pacchetti da codice sorgente, di software per i quali non sono ancora disponibili pacchetti (Vedi anche [[The Arch package making HOW-TO - with guidelines]])<br />
* Modificare pacchetti esistenti per adattarli ai tuoi bisogni (abilitando o disabilitando le opzioni)<br />
* Ricompilare il tuo intero sistema utilizzando flag di compilazione "a la FreeBSD"<br />
* Pacchettizzare e installare in modo pulito il tuo kernel personalizzato. (Vedi [[Kernel Compilation]])<br />
* Utilizzare moduli del kernel che funzionino col tuo kernel personalizzato<br />
<br />
ABS non è necessario per usare Arch Linux, ma è utile per un processo sicuro di compilazione dei sorgenti.<br />
<br />
Questo how-to prova a darti una visione generale di ABS e dei pacchetti di Arch; non è una guida di riferimento completa! Se vuoi saperne di più, dovresti leggere le man page<br />
<br />
== Get Started: Install Packages ==<br />
<br />
To use abs, you first need to install '''abs''' from the core repository; this can be done simply by:<br />
<br />
<pre><br />
pacman -Sy abs</pre><br />
<br />
This will grab any necessary dependencies.<br />
<br />
==== /etc/abs/abs.conf ====<br />
edit /etc/abs/abs.conf to include your desired repositories:<br />
nano /etc/abs/abs.conf<br />
Remove the ! in front of the appropriate repos, e.g.:<br />
SUPFILES=(core extra unstable community !testing)<br />
<br />
==== Create the ABS tree ====<br />
As root, do:<br />
abs<br />
Your ABS tree is now created under /var/abs. Note the appropriate branches of the ABS tree now exist and correspond to the ones you specified in /etc/abs/abs.conf. <br />
<br />
''The abs command should also be used to periodically sync and update your ABS Tree.''<br />
<br />
==== /etc/makepkg.conf ====<br />
<br />
/etc/makepkg.conf specifies global environment variables and compiler flags which you may wish to edit if you are using an SMP system. The default settings are for i686 and x86_64 optimizations which will work fine for those architectures on single-cpu systems. (The defaults will work on SMP machines, but will only utilize one core/CPU- see [[Safe Cflags]].).<br />
<br />
==== The ABS tree ====<br />
<br />
When you run abs for the first time, it synchronizes the ABS tree with the Arch server using the cvs system. So what exactly is the ABS tree? It is located under /var/abs and looks like this:<br />
<br />
<pre><br />
| -- core/<br />
| || -- base/<br />
| || || -- acl/<br />
| || || || -- PKGBUILD<br />
| || || -- attr/<br />
| || || || -- PKGBUILD<br />
| || || -- ...<br />
| || -- devel/<br />
| || || -- abs/<br />
| || || || -- PKGBUILD<br />
| || || -- autoconf/<br />
| || || || -- PKGBUILD<br />
| || || -- ...<br />
| || -- ...<br />
| -- extra/<br />
| || -- daemons/<br />
| || || -- acpid/<br />
| || || || -- PKGBUILD<br />
| || || || -- ...<br />
| || || -- apache/<br />
| || || || -- ...<br />
| || || -- ...<br />
| || -- ...<br />
| -- community/<br />
| || -- ...<br />
</pre><br />
<br />
So the ABS tree has exactly the same structure as the package database:<br />
* first-level directory represents categories<br />
* second-level directories represents the ABS themselves, whose names actually correspond to the packages you want to build<br />
* PKGBUILD files contain all information needed concerning the package<br />
* Further, an ABS directory can contain patches and/or other files needed for building the package. <br />
''It is important to understand that the actual source code for the package is not present in the ABS directory.'' Instead, the '''PKGBUILD''' file contains a URL from which ABS will automatically download from.<br />
=====Create a Build Directory=====<br />
You must create a build directory, where the actual compiling will take place. This is where you'll do everything; you should never modify the ABS Tree by building within it. It is good practice to use your home directory, though some Arch users prefer to create a 'local' directory under /var/abs/, owned by normal user. Copy the ABS from the tree (var/abs/branch/category/pkgname) to the build directory, /path/to/build/dir.<br />
<br />
Create your build directory. e.g.:<br />
mkdir -p /home/yourusername/abs/local/<br />
<br />
NOTE: The first download of the abs tree is the biggest, then only minor updates are needed, so don't be afraid about the data to download if you've got only a 56k connection; it's only text files and is compressed during the transfer''.<br />
<br />
Now that you know what the ABS tree is, how can we use it ?<br />
<br />
==== The build function, traditional method ====<br />
<br />
If you're not familiar with compiling from source, you should know that most packages (but not all) can be built from source in this '''traditional way''':<br />
* Download source tarball from remote server, using web browser, ftp, wget or alternate method.<br />
* decompress the source file:<br />
<br />
<pre><br />
tar -xzf foo-0.99.tar.gz<br />
tar -xjf foo-0.99.tar.bz2</pre><br />
<br />
* enter the directory<br />
<br />
<pre>cd foo-0.99</pre><br />
<br />
* configure the package: generally, there is a little script called <code>configure</code> in the source directory that is used to configure the package (add or remove support for things, choose the install destination, etc.) and check that your computer has all the software needed by the package. It can be run by:<br />
<br />
<pre>./configure [[option]]</pre><br />
<br />
You should first try the help to better understand how it works:<br />
<br />
<pre>./configure --help</pre><br />
If a --prefix option is not passed to the script, ''most'' scripts will use /usr/local as the install path, but others will use /usr. For the sake of consistency, it is generally advised to pass the --prefix=/usr/local option. It is good practice to install personal programs in /usr/local, and to have the ones being managed by the distro, in /usr. This ensures personal program versions can coexist with those being managed by the distro's package manager- in Arch's case, ''pacman''.<br />
./configure --prefix=/usr/local<br />
* compile the sources:<br />
<br />
<pre>make</pre><br />
<br />
* install<br />
<br />
<pre>make install</pre><br />
* Uninstalling would be accomplished by entering the source directory and running:<br />
make uninstall<br />
<br />
However, you should always read the <code>INSTALL</code> file to know how the package should be built and installed! '''Not all packages use the <code>configure; make; make install</code> system!<br />
<br />
''The above traditional method of compiling source tarballs can, of course, still be used on Arch Linux, but ABS offers a streamlined, simple, and elegant alternative, as you shall see.''<br />
<br />
==== The build function, the ABS way ====<br />
<br />
ABS is an elegant tool which allows for powerful assistance and customization for the build process, and creates a package file for installation. The ABS method involves copying an ABS from the Tree to a build directory, and doing makepkg. In our example, we will build the ''slim'' display manager package.<br />
<br />
*1. Copy the slim ABS from the ABS Tree to a build directory.<br />
cp /var/abs/extra/x11/slim/* /home/yourusername/abs/local/slim<br />
*2. Navigate to the build directory<br />
cd /home/yourusername/abs/local/slim<br />
*3. Do makepkg as normal user:<br />
makepkg -c<br />
Install as root:<br />
# pacman -U slim 1.3.0-2-i686.pkg.tar.gz<br />
<br />
That's it. You have just built slim from source and cleanly installed it to your system with pacman. Package removal is also handled by pacman- (pacman -R slim)<br />
<br />
* ''The ABS method adds a level of convenience and automation, while still maintaining complete transparency and control of the build and installation functions by including them in the PKGBUILD.''<br />
<br />
See [[ABS PKGBUILD Explained]] for a complete overview of a sample PKGBUILD.<br />
<br />
==== More ABS and related info ====<br />
* [[ABS PKGBUILD Explained]]<br />
* [[Makepkg]]<br />
* [[The Arch package making HOW-TO - with guidelines]]<br />
* [[Safe Cflags]]<br />
* [[Kernel Compilation with ABS]]<br />
* [[ArchLinux User-community Repository (AUR)]]<br />
* [[Custom local repository with ABS and gensync]]</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Arch_Build_System_(Italiano)&diff=38951Arch Build System (Italiano)2008-03-21T13:54:56Z<p>Psykopear: /* Descrizione generale di ABS */</p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|Česky|ABS - The Arch Build System (Česky)}}<br />
{{i18n_entry|Dansk|ABS_(Dansk)}}<br />
{{i18n_entry|English|ABS - The Arch Build System}}<br />
{{i18n_entry|正體中文|ABS - The Arch Build System (正體中文)}}<br />
{{i18n_entry|Polski|ABS - The Arch Build System (Polski)}}<br />
{{i18n_entry|Русский|ABS - The Arch Build System (Russian)}}<br />
{{i18n_entry|简体中文|ABS (简体中文)}}<br />
{{i18n_entry|Italiano|ABS - Il Sistema Di Compilazione di Arch (Italiano)}}<br />
{{i18n_links_end}}<br />
<br />
<br />
==== Cosa è ABS? ====<br />
ABS è l'acronimo di "Arch Build System", Sistema di costruzione (dei pacchetti) di arch. E' un sistema per fare pacchetti del codice sorgente. Mentre pacman è il tool di Arch specializzato nella gestione dei pacchetti binari (inclusi i pacchetti fatti con ABS), ABS è il tool specializzato nella compilazione dei sorgenti in un pacchetto .pkg.tar.gz installabile<br />
=====Cos'è un sistema ports-like?=====<br />
"Ports" è il sistema usato da FreeBSD che permette di scaricare, scompattare, patchare, compilare e installare i pacchetti con i codici sorgenti. "Un 'port' è solo una piccola cartella nel computer dell'utente, chiamata come il corrispondente software che ci verrà installato, che contiene un po' di file con le istruzioni per scaricare ed installare il pacchetto dai sorgenti", solitamente entrando nella cartella, o port, e dando 'make' e 'make install'. Il sistema si occuperà di scaricare, compilare ed installare il software desiderato.<br />
====='''ABS''' è un concetto simile.=====<br />
"ABS" è costituito da un'albero di dircetory (the "ABS Tree"), che sta in /var/abs, che contiene molte sottodirectory, ognuna dentro una categoria, e ognuna chiamata con il rispettivo pacchetto installabile contenuto al suo interno. Si può considerare ogni sottodirectory chiamata come un pacchetto un "ABS", più o meno allo stesso modo con cui ci si potrebbe riferire ad un "Port". Questi "ABS", o sottodirectory, "non contengono il pacchetto del software, nè tantomeno il codice sorgente", bensì contengono un file "PKGBUILD" (e a volte altri file). Un PKGBUILD è un semplice script, un file di testo contenente le istruzioni per la compilazione e la pacchettizzazione, ma anche l'url dell'apposito pacchetto di sorgenti da scaricare. "I componenti più importanti di ABS sono proprio i PKGBUILD"<br />
<br />
=====Veloce esempio=====<br />
Avviare "ABS" da root crea l'albero di ABS sincronizzandolo con il sistema cvs. Se volessi compilare nano da sorgenti, per esempio, dovresti copiare /var/abs/core/base/nano in una cartella di lavoro, entrare in quella cartella e dare "maepkg". È semplice come sembra. Makepkg si occuperà di leggere ed eseguire le istruzioni contenute nel PKGBUILD. Il pacchetto appropriato sarà scaricato, scompattato, compilato secondo le CFLAGS specificato nel file /etc/makepkg.conf, e infine compresse in u pacchetto con l'estensione .pkg.tar.gz, come per le istruzioni del PKGBUILD. L'installazione è altrettanto semplice, basta dare 'pacman -U nano.pkg.tar.gz'. La rimozione del pacchetto è gestita da pacman.<br />
<br />
Il PKGBUILD e molti altri file, ovviamente, possono essere modificati secondo le tue esigenze, e tu puoi decidere di usare la funzione makepkg di ABS per fare i tuoi pacchetti personalizzati dai sorgenti. (Guarda il prototipo di PKGBUILD e installa i fil sotto /var/abs/core/)<br />
-----<br />
"Con l'"ABS tree" a posto, un utente Arch ha tutto il software per Arch disponibile a portata di mano, da compilare da sorgenti e creare in automatico pacchetti .pkg.tar.gz<br />
<br />
=====Descrizione generale di ABS=====<br />
"ABS" potrebbe essere usato come un termine "ad ombrello", in quanto include, ed è formato, da molti altri componenti. Pertanto, parlando in termini non proprio tecnici, "ABS" fò riferimento alla seguente struttura come un toolkit completo:<br />
<br />
* '''L'albero ABS:''' La struttura di directory di ABS sotto /var/abs/. Contiene molte sottodirectory, chiamate con il nome di ogni software cvs disponibile per arch, ma non i pacchetti stessi<br />
* '''ABS:''' Un insieme do strumenti per scaricare e costruire PKGBUILD ufficiali di Arch. Sono inclusi anche dei PKGBUILD di esempio<br />
* '''PKGBUILG:''' File di testo che si trovano nelle directory di ABS, con le istruzioni per costruire i pacchetti e l'url dei sorgenti.<br />
* '''[[makepkg]]:''' Il comando da shell di ABS che legge il PKGBUILD, compila il sorgente e crea il .pkg.tar.gz<br />
* '''[[Pacman]]:''' Pacman è completamente separato, ma è necessario invocarlo o dal makepkg o manualmente, per installare e rimuovere i pacchetti costruiti, e per risolvere le dipendenze<br />
* '''[[AUR]]:''' Il repository degli utenti della comunità di Arcch è separato da ABS, ma i PKGBUILD non supportati di [[AUR]] possono essere usati con il tool makepkg di ABS, per compilare e impacchettare il software. AUR contiene PKGBUILD degli utenti che potrebbero non essere presenti come pacchetti ufficiali di Arch<br />
<br />
==== Why would I want to use ABS? ====<br />
The Arch Build System (ABS for short) is used to<br />
<br />
* Make new packages from source, of software for which no packages are yet available (See [[The Arch package making HOW-TO - with guidelines]]) <br />
* Customize existing packages to fit your needs (enabling or disabling options)<br />
* Rebuild your entire system using your compiler flags, "a la FreeBSD" <br />
* Cleanly build and install your own custom kernel. (See [[Kernel Compilation]])<br />
* Get kernel modules working with your custom kernel.<br />
<br />
ABS is not necessary to use Arch Linux, but it is useful for automating certain tasks of source compilation.<br />
<br />
This how-to tries to give you an overview of ABS and Arch packages; it's not a complete reference guide! If you want more, you should try to read the man pages.<br />
<br />
== Get Started: Install Packages ==<br />
<br />
To use abs, you first need to install '''abs''' from the core repository; this can be done simply by:<br />
<br />
<pre><br />
pacman -Sy abs</pre><br />
<br />
This will grab any necessary dependencies.<br />
<br />
==== /etc/abs/abs.conf ====<br />
edit /etc/abs/abs.conf to include your desired repositories:<br />
nano /etc/abs/abs.conf<br />
Remove the ! in front of the appropriate repos, e.g.:<br />
SUPFILES=(core extra unstable community !testing)<br />
<br />
==== Create the ABS tree ====<br />
As root, do:<br />
abs<br />
Your ABS tree is now created under /var/abs. Note the appropriate branches of the ABS tree now exist and correspond to the ones you specified in /etc/abs/abs.conf. <br />
<br />
''The abs command should also be used to periodically sync and update your ABS Tree.''<br />
<br />
==== /etc/makepkg.conf ====<br />
<br />
/etc/makepkg.conf specifies global environment variables and compiler flags which you may wish to edit if you are using an SMP system. The default settings are for i686 and x86_64 optimizations which will work fine for those architectures on single-cpu systems. (The defaults will work on SMP machines, but will only utilize one core/CPU- see [[Safe Cflags]].).<br />
<br />
==== The ABS tree ====<br />
<br />
When you run abs for the first time, it synchronizes the ABS tree with the Arch server using the cvs system. So what exactly is the ABS tree? It is located under /var/abs and looks like this:<br />
<br />
<pre><br />
| -- core/<br />
| || -- base/<br />
| || || -- acl/<br />
| || || || -- PKGBUILD<br />
| || || -- attr/<br />
| || || || -- PKGBUILD<br />
| || || -- ...<br />
| || -- devel/<br />
| || || -- abs/<br />
| || || || -- PKGBUILD<br />
| || || -- autoconf/<br />
| || || || -- PKGBUILD<br />
| || || -- ...<br />
| || -- ...<br />
| -- extra/<br />
| || -- daemons/<br />
| || || -- acpid/<br />
| || || || -- PKGBUILD<br />
| || || || -- ...<br />
| || || -- apache/<br />
| || || || -- ...<br />
| || || -- ...<br />
| || -- ...<br />
| -- community/<br />
| || -- ...<br />
</pre><br />
<br />
So the ABS tree has exactly the same structure as the package database:<br />
* first-level directory represents categories<br />
* second-level directories represents the ABS themselves, whose names actually correspond to the packages you want to build<br />
* PKGBUILD files contain all information needed concerning the package<br />
* Further, an ABS directory can contain patches and/or other files needed for building the package. <br />
''It is important to understand that the actual source code for the package is not present in the ABS directory.'' Instead, the '''PKGBUILD''' file contains a URL from which ABS will automatically download from.<br />
=====Create a Build Directory=====<br />
You must create a build directory, where the actual compiling will take place. This is where you'll do everything; you should never modify the ABS Tree by building within it. It is good practice to use your home directory, though some Arch users prefer to create a 'local' directory under /var/abs/, owned by normal user. Copy the ABS from the tree (var/abs/branch/category/pkgname) to the build directory, /path/to/build/dir.<br />
<br />
Create your build directory. e.g.:<br />
mkdir -p /home/yourusername/abs/local/<br />
<br />
NOTE: The first download of the abs tree is the biggest, then only minor updates are needed, so don't be afraid about the data to download if you've got only a 56k connection; it's only text files and is compressed during the transfer''.<br />
<br />
Now that you know what the ABS tree is, how can we use it ?<br />
<br />
==== The build function, traditional method ====<br />
<br />
If you're not familiar with compiling from source, you should know that most packages (but not all) can be built from source in this '''traditional way''':<br />
* Download source tarball from remote server, using web browser, ftp, wget or alternate method.<br />
* decompress the source file:<br />
<br />
<pre><br />
tar -xzf foo-0.99.tar.gz<br />
tar -xjf foo-0.99.tar.bz2</pre><br />
<br />
* enter the directory<br />
<br />
<pre>cd foo-0.99</pre><br />
<br />
* configure the package: generally, there is a little script called <code>configure</code> in the source directory that is used to configure the package (add or remove support for things, choose the install destination, etc.) and check that your computer has all the software needed by the package. It can be run by:<br />
<br />
<pre>./configure [[option]]</pre><br />
<br />
You should first try the help to better understand how it works:<br />
<br />
<pre>./configure --help</pre><br />
If a --prefix option is not passed to the script, ''most'' scripts will use /usr/local as the install path, but others will use /usr. For the sake of consistency, it is generally advised to pass the --prefix=/usr/local option. It is good practice to install personal programs in /usr/local, and to have the ones being managed by the distro, in /usr. This ensures personal program versions can coexist with those being managed by the distro's package manager- in Arch's case, ''pacman''.<br />
./configure --prefix=/usr/local<br />
* compile the sources:<br />
<br />
<pre>make</pre><br />
<br />
* install<br />
<br />
<pre>make install</pre><br />
* Uninstalling would be accomplished by entering the source directory and running:<br />
make uninstall<br />
<br />
However, you should always read the <code>INSTALL</code> file to know how the package should be built and installed! '''Not all packages use the <code>configure; make; make install</code> system!<br />
<br />
''The above traditional method of compiling source tarballs can, of course, still be used on Arch Linux, but ABS offers a streamlined, simple, and elegant alternative, as you shall see.''<br />
<br />
==== The build function, the ABS way ====<br />
<br />
ABS is an elegant tool which allows for powerful assistance and customization for the build process, and creates a package file for installation. The ABS method involves copying an ABS from the Tree to a build directory, and doing makepkg. In our example, we will build the ''slim'' display manager package.<br />
<br />
*1. Copy the slim ABS from the ABS Tree to a build directory.<br />
cp /var/abs/extra/x11/slim/* /home/yourusername/abs/local/slim<br />
*2. Navigate to the build directory<br />
cd /home/yourusername/abs/local/slim<br />
*3. Do makepkg as normal user:<br />
makepkg -c<br />
Install as root:<br />
# pacman -U slim 1.3.0-2-i686.pkg.tar.gz<br />
<br />
That's it. You have just built slim from source and cleanly installed it to your system with pacman. Package removal is also handled by pacman- (pacman -R slim)<br />
<br />
* ''The ABS method adds a level of convenience and automation, while still maintaining complete transparency and control of the build and installation functions by including them in the PKGBUILD.''<br />
<br />
See [[ABS PKGBUILD Explained]] for a complete overview of a sample PKGBUILD.<br />
<br />
==== More ABS and related info ====<br />
* [[ABS PKGBUILD Explained]]<br />
* [[Makepkg]]<br />
* [[The Arch package making HOW-TO - with guidelines]]<br />
* [[Safe Cflags]]<br />
* [[Kernel Compilation with ABS]]<br />
* [[ArchLinux User-community Repository (AUR)]]<br />
* [[Custom local repository with ABS and gensync]]</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Arch_Build_System_(Italiano)&diff=38940Arch Build System (Italiano)2008-03-21T09:26:16Z<p>Psykopear: /* Descrizione generale di ABS */</p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|Česky|ABS - The Arch Build System (Česky)}}<br />
{{i18n_entry|Dansk|ABS_(Dansk)}}<br />
{{i18n_entry|English|ABS - The Arch Build System}}<br />
{{i18n_entry|正體中文|ABS - The Arch Build System (正體中文)}}<br />
{{i18n_entry|Polski|ABS - The Arch Build System (Polski)}}<br />
{{i18n_entry|Русский|ABS - The Arch Build System (Russian)}}<br />
{{i18n_entry|简体中文|ABS (简体中文)}}<br />
{{i18n_entry|Italiano|ABS - Il Sistema Di Compilazione di Arch (Italiano)}}<br />
{{i18n_links_end}}<br />
<br />
<br />
==== Cosa è ABS? ====<br />
ABS è l'acronimo di "Arch Build System", Sistema di costruzione (dei pacchetti) di arch. E' un sistema per fare pacchetti del codice sorgente. Mentre pacman è il tool di Arch specializzato nella gestione dei pacchetti binari (inclusi i pacchetti fatti con ABS), ABS è il tool specializzato nella compilazione dei sorgenti in un pacchetto .pkg.tar.gz installabile<br />
=====Cos'è un sistema ports-like?=====<br />
"Ports" è il sistema usato da FreeBSD che permette di scaricare, scompattare, patchare, compilare e installare i pacchetti con i codici sorgenti. "Un 'port' è solo una piccola cartella nel computer dell'utente, chiamata come il corrispondente software che ci verrà installato, che contiene un po' di file con le istruzioni per scaricare ed installare il pacchetto dai sorgenti", solitamente entrando nella cartella, o port, e dando 'make' e 'make install'. Il sistema si occuperà di scaricare, compilare ed installare il software desiderato.<br />
====='''ABS''' è un concetto simile.=====<br />
"ABS" è costituito da un'albero di dircetory (the "ABS Tree"), che sta in /var/abs, che contiene molte sottodirectory, ognuna dentro una categoria, e ognuna chiamata con il rispettivo pacchetto installabile contenuto al suo interno. Si può considerare ogni sottodirectory chiamata come un pacchetto un "ABS", più o meno allo stesso modo con cui ci si potrebbe riferire ad un "Port". Questi "ABS", o sottodirectory, "non contengono il pacchetto del software, nè tantomeno il codice sorgente", bensì contengono un file "PKGBUILD" (e a volte altri file). Un PKGBUILD è un semplice script, un file di testo contenente le istruzioni per la compilazione e la pacchettizzazione, ma anche l'url dell'apposito pacchetto di sorgenti da scaricare. "I componenti più importanti di ABS sono proprio i PKGBUILD"<br />
<br />
=====Veloce esempio=====<br />
Avviare "ABS" da root crea l'albero di ABS sincronizzandolo con il sistema cvs. Se volessi compilare nano da sorgenti, per esempio, dovresti copiare /var/abs/core/base/nano in una cartella di lavoro, entrare in quella cartella e dare "maepkg". È semplice come sembra. Makepkg si occuperà di leggere ed eseguire le istruzioni contenute nel PKGBUILD. Il pacchetto appropriato sarà scaricato, scompattato, compilato secondo le CFLAGS specificato nel file /etc/makepkg.conf, e infine compresse in u pacchetto con l'estensione .pkg.tar.gz, come per le istruzioni del PKGBUILD. L'installazione è altrettanto semplice, basta dare 'pacman -U nano.pkg.tar.gz'. La rimozione del pacchetto è gestita da pacman.<br />
<br />
Il PKGBUILD e molti altri file, ovviamente, possono essere modificati secondo le tue esigenze, e tu puoi decidere di usare la funzione makepkg di ABS per fare i tuoi pacchetti personalizzati dai sorgenti. (Guarda il prototipo di PKGBUILD e installa i fil sotto /var/abs/core/)<br />
-----<br />
"Con l'"ABS tree" a posto, un utente Arch ha tutto il software per Arch disponibile a portata di mano, da compilare da sorgenti e creare in automatico pacchetti .pkg.tar.gz<br />
<br />
=====Descrizione generale di ABS=====<br />
'ABS' may be used as an umbrella term, since it includes and relies on several other components. Therefore, though not technically accurate, 'ABS' can refer to the following structure and tools as a complete toolkit:<br />
<br />
* '''The ABS tree:''' The ABS directory structure under /var/abs/. It contains many subdirectories, named for all available Arch cvs software, but not the packages themselves.<br />
* '''ABS:''' A set of tools to retrieve and build official Arch Linux PKGBUILDs. Example PKGBUILDs are also included.<br />
* '''PKGBUILDs:''' Text files residing under the ABS directories, with instructions for building packages and the URL of the sources. <br />
* '''[[makepkg]]:''' ABS shell command tool which reads the PKGBUILDs, compiles the sources and creates a .pkg.tar.gz.<br />
* '''[[Pacman]]:''' Pacman is completely separate, but is necessarily invoked either by makepkg or manually, to install and remove the built packages, and for fetching dependencies.<br />
<br />
* '''[[AUR]]:''' The Arch User-Community Repository is separate from ABS but [[AUR]] [unsupported] PKGBUILDs can be used via the ABS makepkg tool, to compile and package up software. The AUR contains user-contributed PKGBUILDs for software which may be unavailable as an official Arch package.<br />
<br />
==== Why would I want to use ABS? ====<br />
The Arch Build System (ABS for short) is used to<br />
<br />
* Make new packages from source, of software for which no packages are yet available (See [[The Arch package making HOW-TO - with guidelines]]) <br />
* Customize existing packages to fit your needs (enabling or disabling options)<br />
* Rebuild your entire system using your compiler flags, "a la FreeBSD" <br />
* Cleanly build and install your own custom kernel. (See [[Kernel Compilation]])<br />
* Get kernel modules working with your custom kernel.<br />
<br />
ABS is not necessary to use Arch Linux, but it is useful for automating certain tasks of source compilation.<br />
<br />
This how-to tries to give you an overview of ABS and Arch packages; it's not a complete reference guide! If you want more, you should try to read the man pages.<br />
<br />
== Get Started: Install Packages ==<br />
<br />
To use abs, you first need to install '''abs''' from the core repository; this can be done simply by:<br />
<br />
<pre><br />
pacman -Sy abs</pre><br />
<br />
This will grab any necessary dependencies.<br />
<br />
==== /etc/abs/abs.conf ====<br />
edit /etc/abs/abs.conf to include your desired repositories:<br />
nano /etc/abs/abs.conf<br />
Remove the ! in front of the appropriate repos, e.g.:<br />
SUPFILES=(core extra unstable community !testing)<br />
<br />
==== Create the ABS tree ====<br />
As root, do:<br />
abs<br />
Your ABS tree is now created under /var/abs. Note the appropriate branches of the ABS tree now exist and correspond to the ones you specified in /etc/abs/abs.conf. <br />
<br />
''The abs command should also be used to periodically sync and update your ABS Tree.''<br />
<br />
==== /etc/makepkg.conf ====<br />
<br />
/etc/makepkg.conf specifies global environment variables and compiler flags which you may wish to edit if you are using an SMP system. The default settings are for i686 and x86_64 optimizations which will work fine for those architectures on single-cpu systems. (The defaults will work on SMP machines, but will only utilize one core/CPU- see [[Safe Cflags]].).<br />
<br />
==== The ABS tree ====<br />
<br />
When you run abs for the first time, it synchronizes the ABS tree with the Arch server using the cvs system. So what exactly is the ABS tree? It is located under /var/abs and looks like this:<br />
<br />
<pre><br />
| -- core/<br />
| || -- base/<br />
| || || -- acl/<br />
| || || || -- PKGBUILD<br />
| || || -- attr/<br />
| || || || -- PKGBUILD<br />
| || || -- ...<br />
| || -- devel/<br />
| || || -- abs/<br />
| || || || -- PKGBUILD<br />
| || || -- autoconf/<br />
| || || || -- PKGBUILD<br />
| || || -- ...<br />
| || -- ...<br />
| -- extra/<br />
| || -- daemons/<br />
| || || -- acpid/<br />
| || || || -- PKGBUILD<br />
| || || || -- ...<br />
| || || -- apache/<br />
| || || || -- ...<br />
| || || -- ...<br />
| || -- ...<br />
| -- community/<br />
| || -- ...<br />
</pre><br />
<br />
So the ABS tree has exactly the same structure as the package database:<br />
* first-level directory represents categories<br />
* second-level directories represents the ABS themselves, whose names actually correspond to the packages you want to build<br />
* PKGBUILD files contain all information needed concerning the package<br />
* Further, an ABS directory can contain patches and/or other files needed for building the package. <br />
''It is important to understand that the actual source code for the package is not present in the ABS directory.'' Instead, the '''PKGBUILD''' file contains a URL from which ABS will automatically download from.<br />
=====Create a Build Directory=====<br />
You must create a build directory, where the actual compiling will take place. This is where you'll do everything; you should never modify the ABS Tree by building within it. It is good practice to use your home directory, though some Arch users prefer to create a 'local' directory under /var/abs/, owned by normal user. Copy the ABS from the tree (var/abs/branch/category/pkgname) to the build directory, /path/to/build/dir.<br />
<br />
Create your build directory. e.g.:<br />
mkdir -p /home/yourusername/abs/local/<br />
<br />
NOTE: The first download of the abs tree is the biggest, then only minor updates are needed, so don't be afraid about the data to download if you've got only a 56k connection; it's only text files and is compressed during the transfer''.<br />
<br />
Now that you know what the ABS tree is, how can we use it ?<br />
<br />
==== The build function, traditional method ====<br />
<br />
If you're not familiar with compiling from source, you should know that most packages (but not all) can be built from source in this '''traditional way''':<br />
* Download source tarball from remote server, using web browser, ftp, wget or alternate method.<br />
* decompress the source file:<br />
<br />
<pre><br />
tar -xzf foo-0.99.tar.gz<br />
tar -xjf foo-0.99.tar.bz2</pre><br />
<br />
* enter the directory<br />
<br />
<pre>cd foo-0.99</pre><br />
<br />
* configure the package: generally, there is a little script called <code>configure</code> in the source directory that is used to configure the package (add or remove support for things, choose the install destination, etc.) and check that your computer has all the software needed by the package. It can be run by:<br />
<br />
<pre>./configure [[option]]</pre><br />
<br />
You should first try the help to better understand how it works:<br />
<br />
<pre>./configure --help</pre><br />
If a --prefix option is not passed to the script, ''most'' scripts will use /usr/local as the install path, but others will use /usr. For the sake of consistency, it is generally advised to pass the --prefix=/usr/local option. It is good practice to install personal programs in /usr/local, and to have the ones being managed by the distro, in /usr. This ensures personal program versions can coexist with those being managed by the distro's package manager- in Arch's case, ''pacman''.<br />
./configure --prefix=/usr/local<br />
* compile the sources:<br />
<br />
<pre>make</pre><br />
<br />
* install<br />
<br />
<pre>make install</pre><br />
* Uninstalling would be accomplished by entering the source directory and running:<br />
make uninstall<br />
<br />
However, you should always read the <code>INSTALL</code> file to know how the package should be built and installed! '''Not all packages use the <code>configure; make; make install</code> system!<br />
<br />
''The above traditional method of compiling source tarballs can, of course, still be used on Arch Linux, but ABS offers a streamlined, simple, and elegant alternative, as you shall see.''<br />
<br />
==== The build function, the ABS way ====<br />
<br />
ABS is an elegant tool which allows for powerful assistance and customization for the build process, and creates a package file for installation. The ABS method involves copying an ABS from the Tree to a build directory, and doing makepkg. In our example, we will build the ''slim'' display manager package.<br />
<br />
*1. Copy the slim ABS from the ABS Tree to a build directory.<br />
cp /var/abs/extra/x11/slim/* /home/yourusername/abs/local/slim<br />
*2. Navigate to the build directory<br />
cd /home/yourusername/abs/local/slim<br />
*3. Do makepkg as normal user:<br />
makepkg -c<br />
Install as root:<br />
# pacman -U slim 1.3.0-2-i686.pkg.tar.gz<br />
<br />
That's it. You have just built slim from source and cleanly installed it to your system with pacman. Package removal is also handled by pacman- (pacman -R slim)<br />
<br />
* ''The ABS method adds a level of convenience and automation, while still maintaining complete transparency and control of the build and installation functions by including them in the PKGBUILD.''<br />
<br />
See [[ABS PKGBUILD Explained]] for a complete overview of a sample PKGBUILD.<br />
<br />
==== More ABS and related info ====<br />
* [[ABS PKGBUILD Explained]]<br />
* [[Makepkg]]<br />
* [[The Arch package making HOW-TO - with guidelines]]<br />
* [[Safe Cflags]]<br />
* [[Kernel Compilation with ABS]]<br />
* [[ArchLinux User-community Repository (AUR)]]<br />
* [[Custom local repository with ABS and gensync]]</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Arch_Build_System_(Italiano)&diff=38939Arch Build System (Italiano)2008-03-21T09:06:11Z<p>Psykopear: /* Veloce esempio */</p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|Česky|ABS - The Arch Build System (Česky)}}<br />
{{i18n_entry|Dansk|ABS_(Dansk)}}<br />
{{i18n_entry|English|ABS - The Arch Build System}}<br />
{{i18n_entry|正體中文|ABS - The Arch Build System (正體中文)}}<br />
{{i18n_entry|Polski|ABS - The Arch Build System (Polski)}}<br />
{{i18n_entry|Русский|ABS - The Arch Build System (Russian)}}<br />
{{i18n_entry|简体中文|ABS (简体中文)}}<br />
{{i18n_entry|Italiano|ABS - Il Sistema Di Compilazione di Arch (Italiano)}}<br />
{{i18n_links_end}}<br />
<br />
<br />
==== Cosa è ABS? ====<br />
ABS è l'acronimo di "Arch Build System", Sistema di costruzione (dei pacchetti) di arch. E' un sistema per fare pacchetti del codice sorgente. Mentre pacman è il tool di Arch specializzato nella gestione dei pacchetti binari (inclusi i pacchetti fatti con ABS), ABS è il tool specializzato nella compilazione dei sorgenti in un pacchetto .pkg.tar.gz installabile<br />
=====Cos'è un sistema ports-like?=====<br />
"Ports" è il sistema usato da FreeBSD che permette di scaricare, scompattare, patchare, compilare e installare i pacchetti con i codici sorgenti. "Un 'port' è solo una piccola cartella nel computer dell'utente, chiamata come il corrispondente software che ci verrà installato, che contiene un po' di file con le istruzioni per scaricare ed installare il pacchetto dai sorgenti", solitamente entrando nella cartella, o port, e dando 'make' e 'make install'. Il sistema si occuperà di scaricare, compilare ed installare il software desiderato.<br />
====='''ABS''' è un concetto simile.=====<br />
"ABS" è costituito da un'albero di dircetory (the "ABS Tree"), che sta in /var/abs, che contiene molte sottodirectory, ognuna dentro una categoria, e ognuna chiamata con il rispettivo pacchetto installabile contenuto al suo interno. Si può considerare ogni sottodirectory chiamata come un pacchetto un "ABS", più o meno allo stesso modo con cui ci si potrebbe riferire ad un "Port". Questi "ABS", o sottodirectory, "non contengono il pacchetto del software, nè tantomeno il codice sorgente", bensì contengono un file "PKGBUILD" (e a volte altri file). Un PKGBUILD è un semplice script, un file di testo contenente le istruzioni per la compilazione e la pacchettizzazione, ma anche l'url dell'apposito pacchetto di sorgenti da scaricare. "I componenti più importanti di ABS sono proprio i PKGBUILD"<br />
<br />
=====Veloce esempio=====<br />
Avviare "ABS" da root crea l'albero di ABS sincronizzandolo con il sistema cvs. Se volessi compilare nano da sorgenti, per esempio, dovresti copiare /var/abs/core/base/nano in una cartella di lavoro, entrare in quella cartella e dare "maepkg". È semplice come sembra. Makepkg si occuperà di leggere ed eseguire le istruzioni contenute nel PKGBUILD. Il pacchetto appropriato sarà scaricato, scompattato, compilato secondo le CFLAGS specificato nel file /etc/makepkg.conf, e infine compresse in u pacchetto con l'estensione .pkg.tar.gz, come per le istruzioni del PKGBUILD. L'installazione è altrettanto semplice, basta dare 'pacman -U nano.pkg.tar.gz'. La rimozione del pacchetto è gestita da pacman.<br />
<br />
Il PKGBUILD e molti altri file, ovviamente, possono essere modificati secondo le tue esigenze, e tu puoi decidere di usare la funzione makepkg di ABS per fare i tuoi pacchetti personalizzati dai sorgenti. (Guarda il prototipo di PKGBUILD e installa i fil sotto /var/abs/core/)<br />
-----<br />
"Con l'"ABS tree" a posto, un utente Arch ha tutto il software per Arch disponibile a portata di mano, da compilare da sorgenti e creare in automatico pacchetti .pkg.tar.gz<br />
<br />
=====ABS Overview=====<br />
'ABS' may be used as an umbrella term, since it includes and relies on several other components. Therefore, though not technically accurate, 'ABS' can refer to the following structure and tools as a complete toolkit:<br />
<br />
* '''The ABS tree:''' The ABS directory structure under /var/abs/. It contains many subdirectories, named for all available Arch cvs software, but not the packages themselves.<br />
* '''ABS:''' A set of tools to retrieve and build official Arch Linux PKGBUILDs. Example PKGBUILDs are also included.<br />
* '''PKGBUILDs:''' Text files residing under the ABS directories, with instructions for building packages and the URL of the sources. <br />
* '''[[makepkg]]:''' ABS shell command tool which reads the PKGBUILDs, compiles the sources and creates a .pkg.tar.gz.<br />
* '''[[Pacman]]:''' Pacman is completely separate, but is necessarily invoked either by makepkg or manually, to install and remove the built packages, and for fetching dependencies.<br />
<br />
* '''[[AUR]]:''' The Arch User-Community Repository is separate from ABS but [[AUR]] [unsupported] PKGBUILDs can be used via the ABS makepkg tool, to compile and package up software. The AUR contains user-contributed PKGBUILDs for software which may be unavailable as an official Arch package.<br />
<br />
==== Why would I want to use ABS? ====<br />
The Arch Build System (ABS for short) is used to<br />
<br />
* Make new packages from source, of software for which no packages are yet available (See [[The Arch package making HOW-TO - with guidelines]]) <br />
* Customize existing packages to fit your needs (enabling or disabling options)<br />
* Rebuild your entire system using your compiler flags, "a la FreeBSD" <br />
* Cleanly build and install your own custom kernel. (See [[Kernel Compilation]])<br />
* Get kernel modules working with your custom kernel.<br />
<br />
ABS is not necessary to use Arch Linux, but it is useful for automating certain tasks of source compilation.<br />
<br />
This how-to tries to give you an overview of ABS and Arch packages; it's not a complete reference guide! If you want more, you should try to read the man pages.<br />
<br />
== Get Started: Install Packages ==<br />
<br />
To use abs, you first need to install '''abs''' from the core repository; this can be done simply by:<br />
<br />
<pre><br />
pacman -Sy abs</pre><br />
<br />
This will grab any necessary dependencies.<br />
<br />
==== /etc/abs/abs.conf ====<br />
edit /etc/abs/abs.conf to include your desired repositories:<br />
nano /etc/abs/abs.conf<br />
Remove the ! in front of the appropriate repos, e.g.:<br />
SUPFILES=(core extra unstable community !testing)<br />
<br />
==== Create the ABS tree ====<br />
As root, do:<br />
abs<br />
Your ABS tree is now created under /var/abs. Note the appropriate branches of the ABS tree now exist and correspond to the ones you specified in /etc/abs/abs.conf. <br />
<br />
''The abs command should also be used to periodically sync and update your ABS Tree.''<br />
<br />
==== /etc/makepkg.conf ====<br />
<br />
/etc/makepkg.conf specifies global environment variables and compiler flags which you may wish to edit if you are using an SMP system. The default settings are for i686 and x86_64 optimizations which will work fine for those architectures on single-cpu systems. (The defaults will work on SMP machines, but will only utilize one core/CPU- see [[Safe Cflags]].).<br />
<br />
==== The ABS tree ====<br />
<br />
When you run abs for the first time, it synchronizes the ABS tree with the Arch server using the cvs system. So what exactly is the ABS tree? It is located under /var/abs and looks like this:<br />
<br />
<pre><br />
| -- core/<br />
| || -- base/<br />
| || || -- acl/<br />
| || || || -- PKGBUILD<br />
| || || -- attr/<br />
| || || || -- PKGBUILD<br />
| || || -- ...<br />
| || -- devel/<br />
| || || -- abs/<br />
| || || || -- PKGBUILD<br />
| || || -- autoconf/<br />
| || || || -- PKGBUILD<br />
| || || -- ...<br />
| || -- ...<br />
| -- extra/<br />
| || -- daemons/<br />
| || || -- acpid/<br />
| || || || -- PKGBUILD<br />
| || || || -- ...<br />
| || || -- apache/<br />
| || || || -- ...<br />
| || || -- ...<br />
| || -- ...<br />
| -- community/<br />
| || -- ...<br />
</pre><br />
<br />
So the ABS tree has exactly the same structure as the package database:<br />
* first-level directory represents categories<br />
* second-level directories represents the ABS themselves, whose names actually correspond to the packages you want to build<br />
* PKGBUILD files contain all information needed concerning the package<br />
* Further, an ABS directory can contain patches and/or other files needed for building the package. <br />
''It is important to understand that the actual source code for the package is not present in the ABS directory.'' Instead, the '''PKGBUILD''' file contains a URL from which ABS will automatically download from.<br />
=====Create a Build Directory=====<br />
You must create a build directory, where the actual compiling will take place. This is where you'll do everything; you should never modify the ABS Tree by building within it. It is good practice to use your home directory, though some Arch users prefer to create a 'local' directory under /var/abs/, owned by normal user. Copy the ABS from the tree (var/abs/branch/category/pkgname) to the build directory, /path/to/build/dir.<br />
<br />
Create your build directory. e.g.:<br />
mkdir -p /home/yourusername/abs/local/<br />
<br />
NOTE: The first download of the abs tree is the biggest, then only minor updates are needed, so don't be afraid about the data to download if you've got only a 56k connection; it's only text files and is compressed during the transfer''.<br />
<br />
Now that you know what the ABS tree is, how can we use it ?<br />
<br />
==== The build function, traditional method ====<br />
<br />
If you're not familiar with compiling from source, you should know that most packages (but not all) can be built from source in this '''traditional way''':<br />
* Download source tarball from remote server, using web browser, ftp, wget or alternate method.<br />
* decompress the source file:<br />
<br />
<pre><br />
tar -xzf foo-0.99.tar.gz<br />
tar -xjf foo-0.99.tar.bz2</pre><br />
<br />
* enter the directory<br />
<br />
<pre>cd foo-0.99</pre><br />
<br />
* configure the package: generally, there is a little script called <code>configure</code> in the source directory that is used to configure the package (add or remove support for things, choose the install destination, etc.) and check that your computer has all the software needed by the package. It can be run by:<br />
<br />
<pre>./configure [[option]]</pre><br />
<br />
You should first try the help to better understand how it works:<br />
<br />
<pre>./configure --help</pre><br />
If a --prefix option is not passed to the script, ''most'' scripts will use /usr/local as the install path, but others will use /usr. For the sake of consistency, it is generally advised to pass the --prefix=/usr/local option. It is good practice to install personal programs in /usr/local, and to have the ones being managed by the distro, in /usr. This ensures personal program versions can coexist with those being managed by the distro's package manager- in Arch's case, ''pacman''.<br />
./configure --prefix=/usr/local<br />
* compile the sources:<br />
<br />
<pre>make</pre><br />
<br />
* install<br />
<br />
<pre>make install</pre><br />
* Uninstalling would be accomplished by entering the source directory and running:<br />
make uninstall<br />
<br />
However, you should always read the <code>INSTALL</code> file to know how the package should be built and installed! '''Not all packages use the <code>configure; make; make install</code> system!<br />
<br />
''The above traditional method of compiling source tarballs can, of course, still be used on Arch Linux, but ABS offers a streamlined, simple, and elegant alternative, as you shall see.''<br />
<br />
==== The build function, the ABS way ====<br />
<br />
ABS is an elegant tool which allows for powerful assistance and customization for the build process, and creates a package file for installation. The ABS method involves copying an ABS from the Tree to a build directory, and doing makepkg. In our example, we will build the ''slim'' display manager package.<br />
<br />
*1. Copy the slim ABS from the ABS Tree to a build directory.<br />
cp /var/abs/extra/x11/slim/* /home/yourusername/abs/local/slim<br />
*2. Navigate to the build directory<br />
cd /home/yourusername/abs/local/slim<br />
*3. Do makepkg as normal user:<br />
makepkg -c<br />
Install as root:<br />
# pacman -U slim 1.3.0-2-i686.pkg.tar.gz<br />
<br />
That's it. You have just built slim from source and cleanly installed it to your system with pacman. Package removal is also handled by pacman- (pacman -R slim)<br />
<br />
* ''The ABS method adds a level of convenience and automation, while still maintaining complete transparency and control of the build and installation functions by including them in the PKGBUILD.''<br />
<br />
See [[ABS PKGBUILD Explained]] for a complete overview of a sample PKGBUILD.<br />
<br />
==== More ABS and related info ====<br />
* [[ABS PKGBUILD Explained]]<br />
* [[Makepkg]]<br />
* [[The Arch package making HOW-TO - with guidelines]]<br />
* [[Safe Cflags]]<br />
* [[Kernel Compilation with ABS]]<br />
* [[ArchLinux User-community Repository (AUR)]]<br />
* [[Custom local repository with ABS and gensync]]</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Arch_Build_System_(Italiano)&diff=38938Arch Build System (Italiano)2008-03-21T09:05:35Z<p>Psykopear: /* Quick Walkthrough */</p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|Česky|ABS - The Arch Build System (Česky)}}<br />
{{i18n_entry|Dansk|ABS_(Dansk)}}<br />
{{i18n_entry|English|ABS - The Arch Build System}}<br />
{{i18n_entry|正體中文|ABS - The Arch Build System (正體中文)}}<br />
{{i18n_entry|Polski|ABS - The Arch Build System (Polski)}}<br />
{{i18n_entry|Русский|ABS - The Arch Build System (Russian)}}<br />
{{i18n_entry|简体中文|ABS (简体中文)}}<br />
{{i18n_entry|Italiano|ABS - Il Sistema Di Compilazione di Arch (Italiano)}}<br />
{{i18n_links_end}}<br />
<br />
<br />
==== Cosa è ABS? ====<br />
ABS è l'acronimo di "Arch Build System", Sistema di costruzione (dei pacchetti) di arch. E' un sistema per fare pacchetti del codice sorgente. Mentre pacman è il tool di Arch specializzato nella gestione dei pacchetti binari (inclusi i pacchetti fatti con ABS), ABS è il tool specializzato nella compilazione dei sorgenti in un pacchetto .pkg.tar.gz installabile<br />
=====Cos'è un sistema ports-like?=====<br />
"Ports" è il sistema usato da FreeBSD che permette di scaricare, scompattare, patchare, compilare e installare i pacchetti con i codici sorgenti. "Un 'port' è solo una piccola cartella nel computer dell'utente, chiamata come il corrispondente software che ci verrà installato, che contiene un po' di file con le istruzioni per scaricare ed installare il pacchetto dai sorgenti", solitamente entrando nella cartella, o port, e dando 'make' e 'make install'. Il sistema si occuperà di scaricare, compilare ed installare il software desiderato.<br />
====='''ABS''' è un concetto simile.=====<br />
"ABS" è costituito da un'albero di dircetory (the "ABS Tree"), che sta in /var/abs, che contiene molte sottodirectory, ognuna dentro una categoria, e ognuna chiamata con il rispettivo pacchetto installabile contenuto al suo interno. Si può considerare ogni sottodirectory chiamata come un pacchetto un "ABS", più o meno allo stesso modo con cui ci si potrebbe riferire ad un "Port". Questi "ABS", o sottodirectory, "non contengono il pacchetto del software, nè tantomeno il codice sorgente", bensì contengono un file "PKGBUILD" (e a volte altri file). Un PKGBUILD è un semplice script, un file di testo contenente le istruzioni per la compilazione e la pacchettizzazione, ma anche l'url dell'apposito pacchetto di sorgenti da scaricare. "I componenti più importanti di ABS sono proprio i PKGBUILD"<br />
<br />
=====Quick Walkthrough=====<br />
Avviare "ABS" da root crea l'albero di ABS sincronizzandolo con il sistema cvs. Se volessi compilare nano da sorgenti, per esempio, dovresti copiare /var/abs/core/base/nano in una cartella di lavoro, entrare in quella cartella e dare "maepkg". È semplice come sembra. Makepkg si occuperà di leggere ed eseguire le istruzioni contenute nel PKGBUILD. Il pacchetto appropriato sarà scaricato, scompattato, compilato secondo le CFLAGS specificato nel file /etc/makepkg.conf, e infine compresse in u pacchetto con l'estensione .pkg.tar.gz, come per le istruzioni del PKGBUILD. L'installazione è altrettanto semplice, basta dare 'pacman -U nano.pkg.tar.gz'. La rimozione del pacchetto è gestita da pacman.<br />
<br />
Il PKGBUILD e molti altri file, ovviamente, possono essere modificati secondo le tue esigenze, e tu puoi decidere di usare la funzione makepkg di ABS per fare i tuoi pacchetti personalizzati dai sorgenti. (Guarda il prototipo di PKGBUILD e installa i fil sotto /var/abs/core/)<br />
-----<br />
"Con l'"ABS tree" a posto, un utente Arch ha tutto il software per Arch disponibile a portata di mano, da compilare da sorgenti e creare in automatico pacchetti .pkg.tar.gz<br />
<br />
=====ABS Overview=====<br />
'ABS' may be used as an umbrella term, since it includes and relies on several other components. Therefore, though not technically accurate, 'ABS' can refer to the following structure and tools as a complete toolkit:<br />
<br />
* '''The ABS tree:''' The ABS directory structure under /var/abs/. It contains many subdirectories, named for all available Arch cvs software, but not the packages themselves.<br />
* '''ABS:''' A set of tools to retrieve and build official Arch Linux PKGBUILDs. Example PKGBUILDs are also included.<br />
* '''PKGBUILDs:''' Text files residing under the ABS directories, with instructions for building packages and the URL of the sources. <br />
* '''[[makepkg]]:''' ABS shell command tool which reads the PKGBUILDs, compiles the sources and creates a .pkg.tar.gz.<br />
* '''[[Pacman]]:''' Pacman is completely separate, but is necessarily invoked either by makepkg or manually, to install and remove the built packages, and for fetching dependencies.<br />
<br />
* '''[[AUR]]:''' The Arch User-Community Repository is separate from ABS but [[AUR]] [unsupported] PKGBUILDs can be used via the ABS makepkg tool, to compile and package up software. The AUR contains user-contributed PKGBUILDs for software which may be unavailable as an official Arch package.<br />
<br />
==== Why would I want to use ABS? ====<br />
The Arch Build System (ABS for short) is used to<br />
<br />
* Make new packages from source, of software for which no packages are yet available (See [[The Arch package making HOW-TO - with guidelines]]) <br />
* Customize existing packages to fit your needs (enabling or disabling options)<br />
* Rebuild your entire system using your compiler flags, "a la FreeBSD" <br />
* Cleanly build and install your own custom kernel. (See [[Kernel Compilation]])<br />
* Get kernel modules working with your custom kernel.<br />
<br />
ABS is not necessary to use Arch Linux, but it is useful for automating certain tasks of source compilation.<br />
<br />
This how-to tries to give you an overview of ABS and Arch packages; it's not a complete reference guide! If you want more, you should try to read the man pages.<br />
<br />
== Get Started: Install Packages ==<br />
<br />
To use abs, you first need to install '''abs''' from the core repository; this can be done simply by:<br />
<br />
<pre><br />
pacman -Sy abs</pre><br />
<br />
This will grab any necessary dependencies.<br />
<br />
==== /etc/abs/abs.conf ====<br />
edit /etc/abs/abs.conf to include your desired repositories:<br />
nano /etc/abs/abs.conf<br />
Remove the ! in front of the appropriate repos, e.g.:<br />
SUPFILES=(core extra unstable community !testing)<br />
<br />
==== Create the ABS tree ====<br />
As root, do:<br />
abs<br />
Your ABS tree is now created under /var/abs. Note the appropriate branches of the ABS tree now exist and correspond to the ones you specified in /etc/abs/abs.conf. <br />
<br />
''The abs command should also be used to periodically sync and update your ABS Tree.''<br />
<br />
==== /etc/makepkg.conf ====<br />
<br />
/etc/makepkg.conf specifies global environment variables and compiler flags which you may wish to edit if you are using an SMP system. The default settings are for i686 and x86_64 optimizations which will work fine for those architectures on single-cpu systems. (The defaults will work on SMP machines, but will only utilize one core/CPU- see [[Safe Cflags]].).<br />
<br />
==== The ABS tree ====<br />
<br />
When you run abs for the first time, it synchronizes the ABS tree with the Arch server using the cvs system. So what exactly is the ABS tree? It is located under /var/abs and looks like this:<br />
<br />
<pre><br />
| -- core/<br />
| || -- base/<br />
| || || -- acl/<br />
| || || || -- PKGBUILD<br />
| || || -- attr/<br />
| || || || -- PKGBUILD<br />
| || || -- ...<br />
| || -- devel/<br />
| || || -- abs/<br />
| || || || -- PKGBUILD<br />
| || || -- autoconf/<br />
| || || || -- PKGBUILD<br />
| || || -- ...<br />
| || -- ...<br />
| -- extra/<br />
| || -- daemons/<br />
| || || -- acpid/<br />
| || || || -- PKGBUILD<br />
| || || || -- ...<br />
| || || -- apache/<br />
| || || || -- ...<br />
| || || -- ...<br />
| || -- ...<br />
| -- community/<br />
| || -- ...<br />
</pre><br />
<br />
So the ABS tree has exactly the same structure as the package database:<br />
* first-level directory represents categories<br />
* second-level directories represents the ABS themselves, whose names actually correspond to the packages you want to build<br />
* PKGBUILD files contain all information needed concerning the package<br />
* Further, an ABS directory can contain patches and/or other files needed for building the package. <br />
''It is important to understand that the actual source code for the package is not present in the ABS directory.'' Instead, the '''PKGBUILD''' file contains a URL from which ABS will automatically download from.<br />
=====Create a Build Directory=====<br />
You must create a build directory, where the actual compiling will take place. This is where you'll do everything; you should never modify the ABS Tree by building within it. It is good practice to use your home directory, though some Arch users prefer to create a 'local' directory under /var/abs/, owned by normal user. Copy the ABS from the tree (var/abs/branch/category/pkgname) to the build directory, /path/to/build/dir.<br />
<br />
Create your build directory. e.g.:<br />
mkdir -p /home/yourusername/abs/local/<br />
<br />
NOTE: The first download of the abs tree is the biggest, then only minor updates are needed, so don't be afraid about the data to download if you've got only a 56k connection; it's only text files and is compressed during the transfer''.<br />
<br />
Now that you know what the ABS tree is, how can we use it ?<br />
<br />
==== The build function, traditional method ====<br />
<br />
If you're not familiar with compiling from source, you should know that most packages (but not all) can be built from source in this '''traditional way''':<br />
* Download source tarball from remote server, using web browser, ftp, wget or alternate method.<br />
* decompress the source file:<br />
<br />
<pre><br />
tar -xzf foo-0.99.tar.gz<br />
tar -xjf foo-0.99.tar.bz2</pre><br />
<br />
* enter the directory<br />
<br />
<pre>cd foo-0.99</pre><br />
<br />
* configure the package: generally, there is a little script called <code>configure</code> in the source directory that is used to configure the package (add or remove support for things, choose the install destination, etc.) and check that your computer has all the software needed by the package. It can be run by:<br />
<br />
<pre>./configure [[option]]</pre><br />
<br />
You should first try the help to better understand how it works:<br />
<br />
<pre>./configure --help</pre><br />
If a --prefix option is not passed to the script, ''most'' scripts will use /usr/local as the install path, but others will use /usr. For the sake of consistency, it is generally advised to pass the --prefix=/usr/local option. It is good practice to install personal programs in /usr/local, and to have the ones being managed by the distro, in /usr. This ensures personal program versions can coexist with those being managed by the distro's package manager- in Arch's case, ''pacman''.<br />
./configure --prefix=/usr/local<br />
* compile the sources:<br />
<br />
<pre>make</pre><br />
<br />
* install<br />
<br />
<pre>make install</pre><br />
* Uninstalling would be accomplished by entering the source directory and running:<br />
make uninstall<br />
<br />
However, you should always read the <code>INSTALL</code> file to know how the package should be built and installed! '''Not all packages use the <code>configure; make; make install</code> system!<br />
<br />
''The above traditional method of compiling source tarballs can, of course, still be used on Arch Linux, but ABS offers a streamlined, simple, and elegant alternative, as you shall see.''<br />
<br />
==== The build function, the ABS way ====<br />
<br />
ABS is an elegant tool which allows for powerful assistance and customization for the build process, and creates a package file for installation. The ABS method involves copying an ABS from the Tree to a build directory, and doing makepkg. In our example, we will build the ''slim'' display manager package.<br />
<br />
*1. Copy the slim ABS from the ABS Tree to a build directory.<br />
cp /var/abs/extra/x11/slim/* /home/yourusername/abs/local/slim<br />
*2. Navigate to the build directory<br />
cd /home/yourusername/abs/local/slim<br />
*3. Do makepkg as normal user:<br />
makepkg -c<br />
Install as root:<br />
# pacman -U slim 1.3.0-2-i686.pkg.tar.gz<br />
<br />
That's it. You have just built slim from source and cleanly installed it to your system with pacman. Package removal is also handled by pacman- (pacman -R slim)<br />
<br />
* ''The ABS method adds a level of convenience and automation, while still maintaining complete transparency and control of the build and installation functions by including them in the PKGBUILD.''<br />
<br />
See [[ABS PKGBUILD Explained]] for a complete overview of a sample PKGBUILD.<br />
<br />
==== More ABS and related info ====<br />
* [[ABS PKGBUILD Explained]]<br />
* [[Makepkg]]<br />
* [[The Arch package making HOW-TO - with guidelines]]<br />
* [[Safe Cflags]]<br />
* [[Kernel Compilation with ABS]]<br />
* [[ArchLinux User-community Repository (AUR)]]<br />
* [[Custom local repository with ABS and gensync]]</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Arch_Build_System_(Italiano)&diff=38936Arch Build System (Italiano)2008-03-21T08:21:18Z<p>Psykopear: </p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|Česky|ABS - The Arch Build System (Česky)}}<br />
{{i18n_entry|Dansk|ABS_(Dansk)}}<br />
{{i18n_entry|English|ABS - The Arch Build System}}<br />
{{i18n_entry|正體中文|ABS - The Arch Build System (正體中文)}}<br />
{{i18n_entry|Polski|ABS - The Arch Build System (Polski)}}<br />
{{i18n_entry|Русский|ABS - The Arch Build System (Russian)}}<br />
{{i18n_entry|简体中文|ABS (简体中文)}}<br />
{{i18n_entry|Italiano|ABS - Il Sistema Di Compilazione di Arch (Italiano)}}<br />
{{i18n_links_end}}<br />
<br />
<br />
==== Cosa è ABS? ====<br />
ABS è l'acronimo di "Arch Build System", Sistema di costruzione (dei pacchetti) di arch. E' un sistema per fare pacchetti del codice sorgente. Mentre pacman è il tool di Arch specializzato nella gestione dei pacchetti binari (inclusi i pacchetti fatti con ABS), ABS è il tool specializzato nella compilazione dei sorgenti in un pacchetto .pkg.tar.gz installabile<br />
=====Cos'è un sistema ports-like?=====<br />
"Ports" è il sistema usato da FreeBSD che permette di scaricare, scompattare, patchare, compilare e installare i pacchetti con i codici sorgenti. "Un 'port' è solo una piccola cartella nel computer dell'utente, chiamata come il corrispondente software che ci verrà installato, che contiene un po' di file con le istruzioni per scaricare ed installare il pacchetto dai sorgenti", solitamente entrando nella cartella, o port, e dando 'make' e 'make install'. Il sistema si occuperà di scaricare, compilare ed installare il software desiderato.<br />
====='''ABS''' è un concetto simile.=====<br />
"ABS" è constituito da un'albero di dircetory (the "ABS Tree"), che sta in /var/abs, che contiene molte sottodirectory, ognuna dentro una categoria, e ognuna chiamata con il rispettivo pacchetto installabile contenuto al suo interno. Si può considerare ogni sottodirectory chiamata come un pacchetto un "ABS", più o meno allo stesso modo con cui ci si potrebbe riferire ad un "Port". Questi "ABS", o sottodirectory, "non contengono il pacchetto del software, nè tantomeno il codice sorgente", bensì contengono un file "PKGBUILD" (e a volte altri file). Un PKGBUILD è un semplice script, un file di testo contenente le istruzioni per la compilazione e la pacchettizzazione, ma anche l'url dell'apposito pacchetto di sorgenti da scaricare. "I componenti più importanti di ABS sono proprio i PKGBUILD"<br />
=====Quick Walkthrough=====<br />
Running 'abs' as root creates the ABS tree by synchronizing with the cvs system. If you wanted to build nano from '''source''', for instance, you would copy /var/abs/core/base/nano to a build directory, navigate to the build directory and do '''makepkg'''. It's as simple as that. Makepkg will attempt to read and execute the instructions contained within the PKGBUILD. The appropriate source tarball will automatically be downloaded, unpacked, compiled according to CFLAGS specified in /etc/makepkg.conf, and finally squeezed into a package with the extension .pkg.tar.gz, as per the instructions in the PKGBUILD. Installing is as easy as doing pacman -U nano.pkg.tar.gz. Package removal is also handled by pacman.<br />
<br />
The PKGBUILD and other files may, of course, be customized to suit your needs, and you may choose to use the ABS makepkg function to make your own custom packages from outside sources. (See the prototype PKGBUILD and install files under /var/abs/core/)<br />
-----<br />
''With the '''ABS Tree''' in place, an Arch user has all available Arch software at their fingertips, to compile from source and automatically package as a .pkg.tar.gz.''<br />
<br />
=====ABS Overview=====<br />
'ABS' may be used as an umbrella term, since it includes and relies on several other components. Therefore, though not technically accurate, 'ABS' can refer to the following structure and tools as a complete toolkit:<br />
<br />
* '''The ABS tree:''' The ABS directory structure under /var/abs/. It contains many subdirectories, named for all available Arch cvs software, but not the packages themselves.<br />
* '''ABS:''' A set of tools to retrieve and build official Arch Linux PKGBUILDs. Example PKGBUILDs are also included.<br />
* '''PKGBUILDs:''' Text files residing under the ABS directories, with instructions for building packages and the URL of the sources. <br />
* '''[[makepkg]]:''' ABS shell command tool which reads the PKGBUILDs, compiles the sources and creates a .pkg.tar.gz.<br />
* '''[[Pacman]]:''' Pacman is completely separate, but is necessarily invoked either by makepkg or manually, to install and remove the built packages, and for fetching dependencies.<br />
<br />
* '''[[AUR]]:''' The Arch User-Community Repository is separate from ABS but [[AUR]] [unsupported] PKGBUILDs can be used via the ABS makepkg tool, to compile and package up software. The AUR contains user-contributed PKGBUILDs for software which may be unavailable as an official Arch package.<br />
<br />
==== Why would I want to use ABS? ====<br />
The Arch Build System (ABS for short) is used to<br />
<br />
* Make new packages from source, of software for which no packages are yet available (See [[The Arch package making HOW-TO - with guidelines]]) <br />
* Customize existing packages to fit your needs (enabling or disabling options)<br />
* Rebuild your entire system using your compiler flags, "a la FreeBSD" <br />
* Cleanly build and install your own custom kernel. (See [[Kernel Compilation]])<br />
* Get kernel modules working with your custom kernel.<br />
<br />
ABS is not necessary to use Arch Linux, but it is useful for automating certain tasks of source compilation.<br />
<br />
This how-to tries to give you an overview of ABS and Arch packages; it's not a complete reference guide! If you want more, you should try to read the man pages.<br />
<br />
== Get Started: Install Packages ==<br />
<br />
To use abs, you first need to install '''abs''' from the core repository; this can be done simply by:<br />
<br />
<pre><br />
pacman -Sy abs</pre><br />
<br />
This will grab any necessary dependencies.<br />
<br />
==== /etc/abs/abs.conf ====<br />
edit /etc/abs/abs.conf to include your desired repositories:<br />
nano /etc/abs/abs.conf<br />
Remove the ! in front of the appropriate repos, e.g.:<br />
SUPFILES=(core extra unstable community !testing)<br />
<br />
==== Create the ABS tree ====<br />
As root, do:<br />
abs<br />
Your ABS tree is now created under /var/abs. Note the appropriate branches of the ABS tree now exist and correspond to the ones you specified in /etc/abs/abs.conf. <br />
<br />
''The abs command should also be used to periodically sync and update your ABS Tree.''<br />
<br />
==== /etc/makepkg.conf ====<br />
<br />
/etc/makepkg.conf specifies global environment variables and compiler flags which you may wish to edit if you are using an SMP system. The default settings are for i686 and x86_64 optimizations which will work fine for those architectures on single-cpu systems. (The defaults will work on SMP machines, but will only utilize one core/CPU- see [[Safe Cflags]].).<br />
<br />
==== The ABS tree ====<br />
<br />
When you run abs for the first time, it synchronizes the ABS tree with the Arch server using the cvs system. So what exactly is the ABS tree? It is located under /var/abs and looks like this:<br />
<br />
<pre><br />
| -- core/<br />
| || -- base/<br />
| || || -- acl/<br />
| || || || -- PKGBUILD<br />
| || || -- attr/<br />
| || || || -- PKGBUILD<br />
| || || -- ...<br />
| || -- devel/<br />
| || || -- abs/<br />
| || || || -- PKGBUILD<br />
| || || -- autoconf/<br />
| || || || -- PKGBUILD<br />
| || || -- ...<br />
| || -- ...<br />
| -- extra/<br />
| || -- daemons/<br />
| || || -- acpid/<br />
| || || || -- PKGBUILD<br />
| || || || -- ...<br />
| || || -- apache/<br />
| || || || -- ...<br />
| || || -- ...<br />
| || -- ...<br />
| -- community/<br />
| || -- ...<br />
</pre><br />
<br />
So the ABS tree has exactly the same structure as the package database:<br />
* first-level directory represents categories<br />
* second-level directories represents the ABS themselves, whose names actually correspond to the packages you want to build<br />
* PKGBUILD files contain all information needed concerning the package<br />
* Further, an ABS directory can contain patches and/or other files needed for building the package. <br />
''It is important to understand that the actual source code for the package is not present in the ABS directory.'' Instead, the '''PKGBUILD''' file contains a URL from which ABS will automatically download from.<br />
=====Create a Build Directory=====<br />
You must create a build directory, where the actual compiling will take place. This is where you'll do everything; you should never modify the ABS Tree by building within it. It is good practice to use your home directory, though some Arch users prefer to create a 'local' directory under /var/abs/, owned by normal user. Copy the ABS from the tree (var/abs/branch/category/pkgname) to the build directory, /path/to/build/dir.<br />
<br />
Create your build directory. e.g.:<br />
mkdir -p /home/yourusername/abs/local/<br />
<br />
NOTE: The first download of the abs tree is the biggest, then only minor updates are needed, so don't be afraid about the data to download if you've got only a 56k connection; it's only text files and is compressed during the transfer''.<br />
<br />
Now that you know what the ABS tree is, how can we use it ?<br />
<br />
==== The build function, traditional method ====<br />
<br />
If you're not familiar with compiling from source, you should know that most packages (but not all) can be built from source in this '''traditional way''':<br />
* Download source tarball from remote server, using web browser, ftp, wget or alternate method.<br />
* decompress the source file:<br />
<br />
<pre><br />
tar -xzf foo-0.99.tar.gz<br />
tar -xjf foo-0.99.tar.bz2</pre><br />
<br />
* enter the directory<br />
<br />
<pre>cd foo-0.99</pre><br />
<br />
* configure the package: generally, there is a little script called <code>configure</code> in the source directory that is used to configure the package (add or remove support for things, choose the install destination, etc.) and check that your computer has all the software needed by the package. It can be run by:<br />
<br />
<pre>./configure [[option]]</pre><br />
<br />
You should first try the help to better understand how it works:<br />
<br />
<pre>./configure --help</pre><br />
If a --prefix option is not passed to the script, ''most'' scripts will use /usr/local as the install path, but others will use /usr. For the sake of consistency, it is generally advised to pass the --prefix=/usr/local option. It is good practice to install personal programs in /usr/local, and to have the ones being managed by the distro, in /usr. This ensures personal program versions can coexist with those being managed by the distro's package manager- in Arch's case, ''pacman''.<br />
./configure --prefix=/usr/local<br />
* compile the sources:<br />
<br />
<pre>make</pre><br />
<br />
* install<br />
<br />
<pre>make install</pre><br />
* Uninstalling would be accomplished by entering the source directory and running:<br />
make uninstall<br />
<br />
However, you should always read the <code>INSTALL</code> file to know how the package should be built and installed! '''Not all packages use the <code>configure; make; make install</code> system!<br />
<br />
''The above traditional method of compiling source tarballs can, of course, still be used on Arch Linux, but ABS offers a streamlined, simple, and elegant alternative, as you shall see.''<br />
<br />
==== The build function, the ABS way ====<br />
<br />
ABS is an elegant tool which allows for powerful assistance and customization for the build process, and creates a package file for installation. The ABS method involves copying an ABS from the Tree to a build directory, and doing makepkg. In our example, we will build the ''slim'' display manager package.<br />
<br />
*1. Copy the slim ABS from the ABS Tree to a build directory.<br />
cp /var/abs/extra/x11/slim/* /home/yourusername/abs/local/slim<br />
*2. Navigate to the build directory<br />
cd /home/yourusername/abs/local/slim<br />
*3. Do makepkg as normal user:<br />
makepkg -c<br />
Install as root:<br />
# pacman -U slim 1.3.0-2-i686.pkg.tar.gz<br />
<br />
That's it. You have just built slim from source and cleanly installed it to your system with pacman. Package removal is also handled by pacman- (pacman -R slim)<br />
<br />
* ''The ABS method adds a level of convenience and automation, while still maintaining complete transparency and control of the build and installation functions by including them in the PKGBUILD.''<br />
<br />
See [[ABS PKGBUILD Explained]] for a complete overview of a sample PKGBUILD.<br />
<br />
==== More ABS and related info ====<br />
* [[ABS PKGBUILD Explained]]<br />
* [[Makepkg]]<br />
* [[The Arch package making HOW-TO - with guidelines]]<br />
* [[Safe Cflags]]<br />
* [[Kernel Compilation with ABS]]<br />
* [[ArchLinux User-community Repository (AUR)]]<br />
* [[Custom local repository with ABS and gensync]]</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Arch_Build_System_(Italiano)&diff=38934Arch Build System (Italiano)2008-03-21T08:17:01Z<p>Psykopear: /* Cosa è ABS? */</p>
<hr />
<div>==== Cosa è ABS? ====<br />
ABS è l'acronimo di "Arch Build System", Sistema di costruzione (dei pacchetti) di arch. E' un sistema per fare pacchetti del codice sorgente. Mentre pacman è il tool di Arch specializzato nella gestione dei pacchetti binari (inclusi i pacchetti fatti con ABS), ABS è il tool specializzato nella compilazione dei sorgenti in un pacchetto .pkg.tar.gz installabile<br />
=====Cos'è un sistema ports-like?=====<br />
"Ports" è il sistema usato da FreeBSD che permette di scaricare, scompattare, patchare, compilare e installare i pacchetti con i codici sorgenti. "Un 'port' è solo una piccola cartella nel computer dell'utente, chiamata come il corrispondente software che ci verrà installato, che contiene un po' di file con le istruzioni per scaricare ed installare il pacchetto dai sorgenti", solitamente entrando nella cartella, o port, e dando 'make' e 'make install'. Il sistema si occuperà di scaricare, compilare ed installare il software desiderato.<br />
====='''ABS''' è un concetto simile.=====<br />
"ABS" è constituito da un'albero di dircetory (the "ABS Tree"), che sta in /var/abs, che contiene molte sottodirectory, ognuna dentro una categoria, e ognuna chiamata con il rispettivo pacchetto installabile contenuto al suo interno. Si può considerare ogni sottodirectory chiamata come un pacchetto un "ABS", più o meno allo stesso modo con cui ci si potrebbe riferire ad un "Port". Questi "ABS", o sottodirectory, "non contengono il pacchetto del software, nè tantomeno il codice sorgente", bensì contengono un file "PKGBUILD" (e a volte altri file). Un PKGBUILD è un semplice script, un file di testo contenente le istruzioni per la compilazione e la pacchettizzazione, ma anche l'url dell'apposito pacchetto di sorgenti da scaricare. "I componenti più importanti di ABS sono proprio i PKGBUILD"<br />
=====Quick Walkthrough=====<br />
Running 'abs' as root creates the ABS tree by synchronizing with the cvs system. If you wanted to build nano from '''source''', for instance, you would copy /var/abs/core/base/nano to a build directory, navigate to the build directory and do '''makepkg'''. It's as simple as that. Makepkg will attempt to read and execute the instructions contained within the PKGBUILD. The appropriate source tarball will automatically be downloaded, unpacked, compiled according to CFLAGS specified in /etc/makepkg.conf, and finally squeezed into a package with the extension .pkg.tar.gz, as per the instructions in the PKGBUILD. Installing is as easy as doing pacman -U nano.pkg.tar.gz. Package removal is also handled by pacman.<br />
<br />
The PKGBUILD and other files may, of course, be customized to suit your needs, and you may choose to use the ABS makepkg function to make your own custom packages from outside sources. (See the prototype PKGBUILD and install files under /var/abs/core/)<br />
-----<br />
''With the '''ABS Tree''' in place, an Arch user has all available Arch software at their fingertips, to compile from source and automatically package as a .pkg.tar.gz.''<br />
<br />
=====ABS Overview=====<br />
'ABS' may be used as an umbrella term, since it includes and relies on several other components. Therefore, though not technically accurate, 'ABS' can refer to the following structure and tools as a complete toolkit:<br />
<br />
* '''The ABS tree:''' The ABS directory structure under /var/abs/. It contains many subdirectories, named for all available Arch cvs software, but not the packages themselves.<br />
* '''ABS:''' A set of tools to retrieve and build official Arch Linux PKGBUILDs. Example PKGBUILDs are also included.<br />
* '''PKGBUILDs:''' Text files residing under the ABS directories, with instructions for building packages and the URL of the sources. <br />
* '''[[makepkg]]:''' ABS shell command tool which reads the PKGBUILDs, compiles the sources and creates a .pkg.tar.gz.<br />
* '''[[Pacman]]:''' Pacman is completely separate, but is necessarily invoked either by makepkg or manually, to install and remove the built packages, and for fetching dependencies.<br />
<br />
* '''[[AUR]]:''' The Arch User-Community Repository is separate from ABS but [[AUR]] [unsupported] PKGBUILDs can be used via the ABS makepkg tool, to compile and package up software. The AUR contains user-contributed PKGBUILDs for software which may be unavailable as an official Arch package.</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Very_Secure_FTP_Daemon_(Italiano)&diff=38823Very Secure FTP Daemon (Italiano)2008-03-19T10:25:54Z<p>Psykopear: </p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|English|Very Secure FTP Daemon}}<br />
{{i18n_entry|Русский|Very Secure FTP Daemon (russian)}}<br />
{{i18n_entry|Italiano|Very Secure FTP Daemon (Italian)}}<br />
{{i18n_links_end}}<br />
<br />
vsftpd sta per "Very secure ftp daemon" (Demone ftp molto sicuro). E' un piccolo (ed efficente) server ftp di cui potresti avere bisogno.<br />
<br />
Può funzionare sia con che senza xinetd, ma verrà descritto solo il metodo senza xinetd.<br />
<br />
Prima di tutto, installa il pacchetto necessario con pacman<br />
pacman -Sy vsftpd<br />
<br />
/etc/vsftpd.conf e' un file di configurazione molto ben documentato, ma queste sono le cose basilar da configurare (per il resto leggi i commenti del file)<br />
<pre><br />
listen=YES<br />
anonymous_enable=YES # Se vuoi che si possa accedere al server in modo anonimo<br />
local_enable=YES # Questo permette agli utenti locali di accedere al server ftp<br />
write_enable=YES # Stai attento ad usare questo con anonymous_enable=YES<br />
tcp_wrappers=YES # Usa tcp_wrappers per controllare le connessioni. <br />
</pre><br />
<br />
Infine aggiungi vsftpd ai demoni nella riga DAEMON= nell'/etc/rc.conf<br />
<br />
Una volta riavviato, potrai accedere al tuo server ftp dal link ftp://localhost, mentre per gli utilizzatori esterni il punto di accesso sarà ftp://tuo_ip (l'ip lo puoi controllare con ifconfig).<br />
<br />
Per aggiungere dei file al server, basta metterli nella cartella /home/ftp che viene creata con l'installazione di arch. Se si vuole poter aggiungere i file in tale cartella anche da utente, basta cambiargli proprietario con <br />
<br />
chown nomeutente:users /home/ftp<br />
<br />
NOTA per gli utenti fastweb: essendo fastweb una rete chiusa, potranno accedere al tuo server esclusivamente gli utenti interni alla rete fastweb, a meno che non si paghi per ottenere un ip pubblico</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Very_Secure_FTP_Daemon_(Italiano)&diff=38822Very Secure FTP Daemon (Italiano)2008-03-19T10:20:27Z<p>Psykopear: New page: {{i18n_links_start}} {{i18n_entry|English|Very Secure FTP Daemon}} {{i18n_entry|Русский|Very Secure FTP Daemon (russian)}} {{i18n_entry|Italiano|Very Secure FTP Daemon (Italian)}} {...</p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|English|Very Secure FTP Daemon}}<br />
{{i18n_entry|Русский|Very Secure FTP Daemon (russian)}}<br />
{{i18n_entry|Italiano|Very Secure FTP Daemon (Italian)}}<br />
{{i18n_links_end}}<br />
<br />
vsftpd sta per "Very secure ftp daemon" (Demone ftp molto sicuro). E' un piccolo (ed efficente) server ftp di cui potresti avere bisogno.<br />
<br />
Può funzionare sia con che senza xinetd, ma verrà descritto solo il metodo senza xinetd.<br />
<br />
Prima di tutto, installa il pacchetto necessario con pacman<br />
pacman -Sy vsftpd<br />
<br />
/etc/vsftpd.conf e' un file di configurazione molto ben documentato, ma queste sono le cose basilar da configurare (per il resto leggi i commenti del file)<br />
<pre><br />
listen=YES<br />
anonymous_enable=YES # Se vuoi che si possa accedere al server in modo anonimo<br />
local_enable=YES # Questo permette agli utenti locali di accedere al server ftp<br />
write_enable=YES # Stai attento ad usare questo con anonymous_enable=YES<br />
tcp_wrappers=YES # Usa tcp_wrappers per controllare le connessioni. <br />
</pre><br />
<br />
Infine aggiungi vsftpd ai demoni nella riga DAEMON= nell'/etc/rc.conf<br />
<br />
Una volta riavviato, potrai accedere al tuo server ftp dal link ftp://localhost, mentre per gli utilizzatori esterni il punto di accesso sarà ftp://tuo_ip (l'ip lo puoi controllare con ifconfig).<br />
<br />
NOTA per gli utenti fastweb: essendo fastweb una rete chiusa, potranno accedere al tuo server esclusivamente gli utenti interni alla rete fastweb, a meno che non si paghi per ottenere un ip pubblico</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Compiz_Fusion&diff=37587Compiz Fusion2008-02-23T19:08:20Z<p>Psykopear: /* Starting Compiz Fusion */</p>
<hr />
<div>[[Category:Eye candy (English)]]<br />
[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|:Compiz Fusion}}<br />
{{i18n_entry|Português de Brasil|:Compiz Fusion (Português)}}<br />
{{i18n_entry|简体中文|Compiz Fusion(简体中文)}}<br />
{{i18n_links_end}}<br />
<br />
= Installazione =<br />
L'installazione di base può essere fatta usando i repository community (guarda sotto).<br />
<br />
Un'altra possibilità è usare i pacchetti git di nesl. Vedi la guida [[Compiz_Fusion_Git]] per maggiori info.<br />
<br />
<br />
== Installazione dai repo Community ==<br />
<br />
Assicurati che il repository community sia abilitato e dai questo comando da root per installare tutto:<br />
pacman -S compiz-fusion<br />
Dai invece questo se vuoi installare i pacchetti per gtk:<br />
pacman -S compiz-fusion-gtk<br />
O questo se vuoi solo i pacchetti per kde:<br />
pacman -S compiz-fusion-kde <br />
<br />
Se vuoi selezionare i pacchetti personalmente, ecco una lista:<br />
=== Lista dei pacchetti per gruppo ===<br />
<br />
DA FARE<br />
<br />
=== Effetti Fusion ===<br />
<br />
Devi installarel<br />
<br />
* compiz-fusion-plugins-main<br />
* compiz-fusion-plugins-extra<br />
<br />
Per avere tutti gli effetti di compiz-fusion, come expo, il riflesso del cubo..<br />
<br />
pacman -S compiz-fusion-plugins-main compiz-fusion-plugins-extra<br />
<br />
= Avvio di Compiz Fusion =<br />
<br />
== Manuale (con "fusion-icon") ==<br />
<br />
Lancia l'icona del vassoio di sistema di compiz-fusion:<br />
<br />
fusion-icon<br />
<br />
nota: se fallisce, potrsti provare a lanciarlo con dbus-launch:<br />
<br />
dbus-launch "fusion-icon"<br />
<br />
Fai tasto destro sull'icona nel pannello e vai a "seleziona il window manager". Scegli "Compiz" se non è gia selezionato, e doresti essere a posto.<br />
<br />
Se non ci riesci, puoi far partire compiz-fusion usando i seguenti comandi<br />
<br />
fusion-icon<br />
emerald --replace<br />
compiz-manager<br />
<br />
== KDE ==<br />
<br />
=== Manuale (senza "fusion-icon") ===<br />
<br />
Una volta installato, lancia compiz con il seguente comando:<br />
<br />
compiz --replace ccp &<br />
<br />
Avvia il gestore delle configurazioni:<br />
ccsm &<br />
<br />
Seleziona tutti i plugin che vuoi, compreso il plugin "decoration", aggiungi<br />
kde-window-decorator --replace<br />
come comando nella casella del plugin "decoration".<br />
<br />
<!-- We need some more consistency with the autostart guides. The KDE version suggests starting compiz directly while the GNOME version tells you to use fusion-icon. --><br />
<br />
=== Autostart (con "fusion-icon") ===<br />
<br />
Devi aggiungere un link simbolico dell'eseguibile di fusion-icon nela cartella di autostart di KDE (solitamente ~/.kde/Autostart) con:<br />
<br />
ln -s /usr/bin/fusion-icon ~/.kde/Autostart/fusion-icon<br />
<br />
La prossima volta che avvierai KDE fusion-icon verrà avviato automaticamente.<br />
<br />
=== Autostart (senza "fusion-icon") ===<br />
<br />
==== Method 1 - Autostart Link ====<br />
<br />
* You can ensure that Compiz Fusion will always start at login by appending a desktop entry to the KDE autostart directory. Create the file ''~/.kde/Autostart/compiz.desktop'' with the following contents:<br />
<br />
[Desktop Entry]<br />
Encoding=UTF-8<br />
Exec=compiz --replace ccp<br />
StartupNotify=false<br />
Terminal=false<br />
Type=Application<br />
X-KDE-autostart-after=kdesktop<br />
<br />
* If you want to use the optional <tt>fusion-icon</tt> application, launch ''fusion-icon''. If you log out normally with ''fusion-icon'' running, KDE should restore your session and launch ''fusion-icon'' the next time you log in if this setting is enabled. If it doesn't appear to be working, ensure you have the following line in ''~/.kde/share/config/ksmserverrc'':<br />
<br />
loginMode=restorePreviousLogout<br />
<br />
==== Method 2 - export KDEWM (avoid KWIN) ====<br />
<br />
Using this method will load Compiz-Fusion as the default window manager instead of KWIN from the start. This method is faster then loading Compiz-Fusion in the ~/.kde/Autostart/ (method 1) because it avoids loading KDE's default WM (kwin) first. This way also stops that annoying black screen flicker you might see using other methods (when kwin switches to Compiz on KDE's desktop loading screens).<br />
<br />
As root you must create a short script by doing the following in your terminal. This will allow you to load compiz with the switches because doing it directly via export KDEWM="compiz --replace ccp --sm-disable" doesn't seem to work.<br />
<br />
echo "compiz --replace ccp --sm-disable &" > /usr/bin/compiz-fusion<br />
chmod +x /usr/bin/compiz-fusion<br />
<br />
Now just edit your ~/.bashrc and add the following so KDE will load compiz (via the script you just created) instead of loading kwin.<br />
<br />
export KDEWM="compiz-fusion"<br />
<br />
== GNOME ==<br />
<br />
=== Autostart (without "compiz-fusion") ===<br />
<br />
TO DO<br />
<br />
=== Autostart (with "compiz-fusion") ===<br />
<br />
To start Compiz fusion automatically when starting a session add<br />
"Compiz Fusion" (Name:)<br />
and <br />
"fusion-icon" (Command:)<br />
to the applications that start with your session. You can do this by going to:<br />
<br />
[System] -> [Preferences] -> [Sessions] -> [Startup Programs]<br />
Adding "Compiz Fusion" to the list might be a good idea too so you can switch back to Metacity if need be.<br />
<br />
== Xfce ==<br />
<br />
=== Xfce autostart (without "compiz-fusion") ===<br />
<br />
TO DO<br />
<br />
=== Xfce autostart (with "compiz-fusion") ===<br />
<br />
Start "Autostarted Applications"<br />
<br />
Add<br />
(Name:) Compiz Fusion<br />
and <br />
(Command:) fusion-icon<br />
<br />
= Troubleshooting =<br />
<br />
* make sure that the environmental variable $XLIB_SKIP_ARGB_VISUALS is not set<br />
<br />
See [[Compiz_Troubleshooting]]<br />
<br />
= Additional Resources =<br />
*[[AIGLX]]<br />
*[[Xgl]]<br />
*[[Composite]] -- A Xorg extension required by composite managers<br />
*[[Compiz Fusion]] -- A composite and window manager offering a rich 3D accelerated desktop environment<br />
*[[Compiz]] -- The original composite/window manager from Novell<br />
*[[Xcompmgr]] -- A simple composite manager capable of drop shadows and primitive transparency<br />
*[[Beryl]] -- <strike>A composite/window manager forked from Compiz</strike> (since merged to become [[Compiz Fusion]])<br />
*Wikipedia: [http://en.wikipedia.org/wiki/Compositing_window_manager Compositing Window Managers]</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Compiz_Fusion&diff=37586Compiz Fusion2008-02-23T19:01:23Z<p>Psykopear: /* Installazione */</p>
<hr />
<div>[[Category:Eye candy (English)]]<br />
[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|:Compiz Fusion}}<br />
{{i18n_entry|Português de Brasil|:Compiz Fusion (Português)}}<br />
{{i18n_entry|简体中文|Compiz Fusion(简体中文)}}<br />
{{i18n_links_end}}<br />
<br />
= Installazione =<br />
L'installazione di base può essere fatta usando i repository community (guarda sotto).<br />
<br />
Un'altra possibilità è usare i pacchetti git di nesl. Vedi la guida [[Compiz_Fusion_Git]] per maggiori info.<br />
<br />
<br />
== Installazione dai repo Community ==<br />
<br />
Assicurati che il repository community sia abilitato e dai questo comando da root per installare tutto:<br />
pacman -S compiz-fusion<br />
Dai invece questo se vuoi installare i pacchetti per gtk:<br />
pacman -S compiz-fusion-gtk<br />
O questo se vuoi solo i pacchetti per kde:<br />
pacman -S compiz-fusion-kde <br />
<br />
Se vuoi selezionare i pacchetti personalmente, ecco una lista:<br />
=== Lista dei pacchetti per gruppo ===<br />
<br />
DA FARE<br />
<br />
=== Effetti Fusion ===<br />
<br />
Devi installarel<br />
<br />
* compiz-fusion-plugins-main<br />
* compiz-fusion-plugins-extra<br />
<br />
Per avere tutti gli effetti di compiz-fusion, come expo, il riflesso del cubo..<br />
<br />
pacman -S compiz-fusion-plugins-main compiz-fusion-plugins-extra<br />
<br />
= Starting Compiz Fusion =<br />
<br />
== Manual (with "fusion-icon") ==<br />
<br />
Launch the Compiz Fusion tray icon:<br />
<br />
fusion-icon<br />
<br />
note: if it fails, you may try it with dbus-launch<br />
<br />
dbus-launch "fusion-icon"<br />
<br />
Right click on the icon in the panel and go to 'select window manager'. Choose "Compiz" if it isn't selected already, and you should be set.<br />
<br />
If this fails you can start compiz-fusion by using the following commands<br />
<br />
fusion-icon<br />
emerald --replace<br />
compiz-manager<br />
<br />
== KDE ==<br />
<br />
=== Manual (without "fusion-icon") ===<br />
<br />
Launch Compiz with the following command once installation is done :<br />
<br />
compiz --replace ccp &<br />
<br />
Start new settings manager:<br />
ccsm &<br />
<br />
Select all the plugins you like including “decoration” plugin, Add<br />
kde-window-decorator --replace<br />
as command string under ‘decoration’ plugin.<br />
<br />
<!-- We need some more consistency with the autostart guides. The KDE version suggests starting compiz directly while the GNOME version tells you to use fusion-icon. --><br />
<br />
=== Autostart (with "fusion-icon") ===<br />
<br />
You should add a symbolic link to the fusion-icon executable in your KDE Autostart directory (generally located on ~/.kde/Autostart):<br />
<br />
ln -s /usr/bin/fusion-icon ~/.kde/Autostart/fusion-icon<br />
<br />
Next time you start KDE it will load fusion-icon automatically.<br />
<br />
=== Autostart (without "fusion-icon") ===<br />
<br />
==== Method 1 - Autostart Link ====<br />
<br />
* You can ensure that Compiz Fusion will always start at login by appending a desktop entry to the KDE autostart directory. Create the file ''~/.kde/Autostart/compiz.desktop'' with the following contents:<br />
<br />
[Desktop Entry]<br />
Encoding=UTF-8<br />
Exec=compiz --replace ccp<br />
StartupNotify=false<br />
Terminal=false<br />
Type=Application<br />
X-KDE-autostart-after=kdesktop<br />
<br />
* If you want to use the optional <tt>fusion-icon</tt> application, launch ''fusion-icon''. If you log out normally with ''fusion-icon'' running, KDE should restore your session and launch ''fusion-icon'' the next time you log in if this setting is enabled. If it doesn't appear to be working, ensure you have the following line in ''~/.kde/share/config/ksmserverrc'':<br />
<br />
loginMode=restorePreviousLogout<br />
<br />
==== Method 2 - export KDEWM (avoid KWIN) ====<br />
<br />
Using this method will load Compiz-Fusion as the default window manager instead of KWIN from the start. This method is faster then loading Compiz-Fusion in the ~/.kde/Autostart/ (method 1) because it avoids loading KDE's default WM (kwin) first. This way also stops that annoying black screen flicker you might see using other methods (when kwin switches to Compiz on KDE's desktop loading screens).<br />
<br />
As root you must create a short script by doing the following in your terminal. This will allow you to load compiz with the switches because doing it directly via export KDEWM="compiz --replace ccp --sm-disable" doesn't seem to work.<br />
<br />
echo "compiz --replace ccp --sm-disable &" > /usr/bin/compiz-fusion<br />
chmod +x /usr/bin/compiz-fusion<br />
<br />
Now just edit your ~/.bashrc and add the following so KDE will load compiz (via the script you just created) instead of loading kwin.<br />
<br />
export KDEWM="compiz-fusion"<br />
<br />
== GNOME ==<br />
<br />
=== Autostart (without "compiz-fusion") ===<br />
<br />
TO DO<br />
<br />
=== Autostart (with "compiz-fusion") ===<br />
<br />
To start Compiz fusion automatically when starting a session add<br />
"Compiz Fusion" (Name:)<br />
and <br />
"fusion-icon" (Command:)<br />
to the applications that start with your session. You can do this by going to:<br />
<br />
[System] -> [Preferences] -> [Sessions] -> [Startup Programs]<br />
Adding "Compiz Fusion" to the list might be a good idea too so you can switch back to Metacity if need be.<br />
<br />
== Xfce ==<br />
<br />
=== Xfce autostart (without "compiz-fusion") ===<br />
<br />
TO DO<br />
<br />
=== Xfce autostart (with "compiz-fusion") ===<br />
<br />
Start "Autostarted Applications"<br />
<br />
Add<br />
(Name:) Compiz Fusion<br />
and <br />
(Command:) fusion-icon<br />
<br />
= Troubleshooting =<br />
<br />
* make sure that the environmental variable $XLIB_SKIP_ARGB_VISUALS is not set<br />
<br />
See [[Compiz_Troubleshooting]]<br />
<br />
= Additional Resources =<br />
*[[AIGLX]]<br />
*[[Xgl]]<br />
*[[Composite]] -- A Xorg extension required by composite managers<br />
*[[Compiz Fusion]] -- A composite and window manager offering a rich 3D accelerated desktop environment<br />
*[[Compiz]] -- The original composite/window manager from Novell<br />
*[[Xcompmgr]] -- A simple composite manager capable of drop shadows and primitive transparency<br />
*[[Beryl]] -- <strike>A composite/window manager forked from Compiz</strike> (since merged to become [[Compiz Fusion]])<br />
*Wikipedia: [http://en.wikipedia.org/wiki/Compositing_window_manager Compositing Window Managers]</div>Psykopearhttps://wiki.archlinux.org/index.php?title=Compiz&diff=37585Compiz2008-02-23T18:54:53Z<p>Psykopear: /* Introduzione */</p>
<hr />
<div>[[Category:Eye candy (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
= Introduzione =<br />
Compiz è un [http://en.wikipedia.org/wiki/Compositing_window_manager gestore di finestre con compositing]. Compiz ha il suo personale Window Manager, che non può essere usato insieme ad altri WM come [[Openbox]], [[Fluxbox]], [[Enlightenment]], o anche Metacity di GNOME--gli utenti di quest'ultimo vorranno provare [[Xcompmgr]] invece.<br />
<br />
Compiz è il cuore del progetto [[Compiz Fusion]]. Entrambi i progetti sono attivi e sotto costante aggiornamenti. Per maggiori informazione, vedi l'articolo, [http://wiki.compiz-fusion.org/CompizFusionVsCompiz Compiz Fusion vs. Compiz].<br />
<br />
= Installation =<br />
There are binary packages available in the ''Community'' repository. Install compiz using one of the following commands:<br />
# pacman -S compiz-core<br />
<br />
# pacman -S compiz-decorator-gtk<br />
<br />
# pacman -S compiz-decorator-kde <br />
<br />
= Configuration =<br />
== Preparing Xorg for Compiz ==<br />
<br />
Compiz, at this moment, has only one rendering paths. The "Texture from Pixmap" path runs faster but doesn't work on all hardware yet.<br />
<br />
=== Using "Texture from Pixmap" rendering ===<br />
<br />
The GLX_EXT_texture_from_pixmap extension is needed for this rendering path. This extension is currently provided by Xorg if you either use the 9xxx nvidia drivers or the AIGLX extension. It is also provided by Xgl. Refer to the [[Composite]] wiki for more information.<br />
<br />
== Starting Compiz ==<br />
<br />
=== Using compiz-manager ===<br />
<br />
In order to use compiz-manager, you need to install it from community:<br />
pacman -Sy compiz-manager<br />
<br />
Compiz-manager, that now is installed in /usr/bin/compiz-manager, is a simple wrapper for compiz and ALL its options. For example, you can run <br />
compiz-manager <br />
and see that console returns. You can use it in all the scripts that start compiz. Very simple!<br />
<br />
=== GNOME ===<br />
System > Preferences > Sessions > Startup Programs<br />
<br />
Add:<br />
gtk-window-decorator --replace<br />
<br />
compiz --replace --use-cow gconf<br />
<br />
====GNOME Compiz Manager====<br />
[http://gandalfn.wordpress.com/gnome-compiz-manager/ Gnome-compiz-manager], available in the [[AUR]], provides a tray icon (compiz-tray-icon) and a compiz settings manager (gnome-compiz-preferences). <br />
Add compiz-tray-icon to the Startup Programs list in the Sessions preferences to autostart the program.<br />
<br />
=== KDE ===<br />
<br />
In your KDE desktop, open Konsole and type:<br />
<br />
compiz --replace gconf & kde-window-decorator &<br />
<br />
==== Autostart Compiz with KDE ====<br />
<br />
In order to start compiz automatically when log on to KDE. Create a new file ~/.kde/Autostart/compiz.desktop, with the following content:<br />
<br />
[Desktop Entry]<br />
Encoding=UTF-8<br />
Exec=compiz –replace gconf & kde-window-decorator &<br />
GenericName[en_US]=<br />
StartupNotify=false<br />
Terminal=false<br />
TerminalOptions=<br />
Type=Application<br />
X-KDE-autostart-after=kdesktop<br />
<br />
== Additional Compiz Configurations ==<br />
<br />
To achieve more satisfying results from Compiz, you can tweak its config with gconf-editor:<br />
<br />
gconf-editor &<br />
<br />
Note that now compiz-core isn't builded with gconf support; It is now on compiz-decorator-gtk. So, you need to install it if you want to use gconf-editor to edit compiz configuration.<br />
Compiz config is in <b>apps</b> > <b>compiz</b> > <b>general</b> > <b>allscreens</b> > <b>options</b><br />
<br />
Active plugins is where you specify the plugins you would like to use, simply edit the key and add in value(refer to <b>apps</b> > <b>compiz</b> > <b>plugins</b>). Plugins I’ve found useful are screenshot, png, fade, minimize. Please do not remove those enabled by default.<br />
<br />
== Keyboard Shortcuts ==<br />
Default plugin keyboard shortcuts<br />
<br />
* Switch windows = Alt + Tab<br />
* Arrange and View All Windows = F12 turns on or off; clicking a window will zoom it to the front<br />
* Switch desktops on cube = Ctrl + Alt + Left/Right Arrow<br />
* Switch desktops on cube - with active window following = Ctrl + Shift + Alt + Left/Right Arrow<br />
* Rotate cube manually = Ctrl + Alt + left-click<br />
* Make window translucent/opaque = Ctrl + Alt + wheel mouse OR Alt + wheel mouse<br />
* Zoom-in once = Super-key right-click<br />
* Zoom-in manually = Super-key + wheel mouse up OR WIN-key + wheel mouse up<br />
* Zoom-out manually = Super-key + wheel mouse down OR WIN-key + wheel mouse down<br />
* Move window = Alt + left-click<br />
* Snap Move window (will stick to borders) = Ctrl + Alt + left-click<br />
* Resize window = Alt + right-click<br />
* Bring up the window below the top window = Alt + middle-click<br />
* Slow-motion = Shift + F10<br />
* Water = hold Ctrl + Super key<br />
* Rain = Shift-F9 <br />
* Film effect - changing desktop = Ctrl + Alt + Down Arrow (Compiz-quinn: Ctrl + Alt + Page Down)<br />
* Expose - Point your mouse to the TOP RIGHT CORNER of your screens.<br />
* Screenshot - Super Key + Left-Click Drag(Select a region)<br />
This is another useful features when you have many windows opened at once without minimizing them. You can get to the window you want right away.<br />
<br />
Source: [http://en.opensuse.org/Compiz#Default_plugin_keyboard_shortcuts Compiz - openSUSE]<br />
<br />
= Troubleshooting =<br />
<br />
See [[Compiz_Troubleshooting]]<br />
<br />
= Additional Resources =<br />
*[[AIGLX]]<br />
*[[Xgl]]<br />
*[[Composite]] -- A Xorg extension required by composite managers<br />
*[[Compiz Fusion]] -- A composite and window manager offering a rich 3D accelerated desktop environment<br />
*[[Compiz]] -- The original composite/window manager from Novell<br />
*[[Xcompmgr]] -- A simple composite manager capable of drop shadows and primitive transparency<br />
*[[Beryl]] -- <strike>A composite/window manager forked from Compiz</strike> (since merged to become [[Compiz Fusion]])<br />
*Wikipedia: [http://en.wikipedia.org/wiki/Compositing_window_manager Compositing Window Managers]</div>Psykopearhttps://wiki.archlinux.org/index.php?title=64-bit_FAQ_(Italiano)&diff=3758464-bit FAQ (Italiano)2008-02-23T18:49:08Z<p>Psykopear: /* Posso upgradare il mio sistema da i686 a x86_64 senza reinstallare? */</p>
<hr />
<div>[[Category:Arch64 (Italiano)]]<br />
[[Category:FAQs (Italiano)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Arch64 FAQ}}<br />
{{i18n_entry|Español|Arch64 FAQ (Español)}}<br />
{{i18n_entry|Italiano|Arch64 FAQ (Italiano)}}<br />
{{i18n_entry|简体中文|Arch64 问答}}<br />
{{i18n_links_end}}<br />
<br />
Di seguito è riportato un elenco di domande frequenti su Arch64. <br />
<br />
==Come faccio a installare Arch64?==<br />
Basta utilizzare il nostro [http://www.archlinux.org/download/ CD di installazione ufficiale].<br />
<br />
==A che punto è il port? Avrò tutti i pacchetti del mio ambiente Arch32?==<br />
I repository Core+Extra sono pronti e quasi tutto è aggiornato, solo poche ore o giorni al massimo dietro Arch Linux i686. I nostri TU stanno provando ad eseguire il port in Community proprio adesso.<br />
<br />
Il port è pronto per l'uso quotidiano in un ambiente desktop o server.<br />
<br />
==64 bit significa un grande aumento di velocità?==<br />
Per le applicazioni che utilizzano una CPU con registri a 64-bit (grandi database e simili), questo è vero nella maggior parte dei casi. Alcune applicazioni multimediali gireranno anche notevolmente più veloce. Se conosci un'applicazione che è notoriamente molto più veloce quando si utilizzano le estensioni SSE3 è possibile ricostruire il pacchetto da sé. Noi ''soltanto''compiliamo con il supporto SSE2 (da marzo=x86_64)e ottimizzazioni -O2.<br />
Per saperne di più leggi http://forums.gentoo.org/viewtopic.php?t=221045 oppure http://www.thejemreport.com/mambo/content/view/74/74/.<br />
<br />
For the rest of the system: It doesn't make any difference if the keyboard waits. <br />
<br />
For further details watch our [[Arch64_ToDoS]]. There you will find a list comparing arch32/arch64 package versions.<br />
<br />
For certain boot problems try these special kernel boot flags: http://www.x86-64.org/lists/discuss/msg03747.html (dead link)<br />
<br />
I have three 64-bit Archies running now, and they perform noticeably better under heavy load. It just seems to deliver more punch.<br />
<br />
==Attenzione quando aggiorni glibc da una versione inferiore alla 2.4!==<br />
E' importante se aggiorni glibc da una versione inferiore alla 2.4 che tu lo faccia a parte. Quindi dai prima pacman -Sy glibc e, se non ci sono problemi, dai pacman -Su. Altrimenti l'aggiornamento della libreria potrebbe fallire e sarai costretto ad usare pacman.static per correggere l'errore.<br />
<br />
==How can I file bugs?==<br />
Simply use Arch's flyspray but note x86_64 in the topic if you think it's a port-related problem!<br />
<br />
==C'è una mailing-list?==<br />
Si, c'è una [http://archlinux.org/mailman/listinfo/arch-ports mailing list] generica riguardante i ports di arch.<br />
<br />
==Quali repository dovrei utilizzare per pacman?==<br />
Tutti i repository sono suppoartati per la versione 64 bit.<br />
<br />
==Come posso reperire i PKGBUILD di Arch64?==<br />
C'è ""ABS"" come per arch 32-bit. La directory raccomandata per metterli è "/var/abs". "ABS" recupera tutti i pacchetti CVS da archlinux.org taggati con CURRENT-64<br />
<br />
==Come posso fare un pacchetto per Arch64 usando un PKGBUILD esistente per la 32-bit?==<br />
Abbiamo i PKGBUILD in comune con Arch32. Puoi prendere quelli non ancora "portati" da CVS: http://www.archlinux.org/cvs/<br />
<br />
==How can I patch existing PKGBUILDs for use with Arch64?==<br />
We add to all ported packages this variable:<br />
arch=('i686' 'x86_64') <br />
Add small patches directly to the sources and md5sums area but use for complete different sources:<br />
[ "$CARCH" = "x86_64" ] && source=(${source[@]} 'other source')<br />
[ "$CARCH" = "x86_64" ] && md5sums=(${md5sums[@]} 'other md5sum')<br />
For any small fix use this in the build area:<br />
[ "$CARCH" = "x86_64" ] && (patch -Np0 -i ../foo_x86_64.patch || return 1)<br />
Or when you need more changes:<br />
if [ "$CARCH" = "x86_64" ]; then<br />
configure/patch/sed # for x86_64<br />
else configure/patch/sed # for i686<br />
fi<br />
For the devs:<br />
cvs commit -m "x86_64 updated/fixed or whatever"<br />
cvs tag -cFR CURRENT-64 foo-package-directory (even for extra, community, unstable and testing)<br />
<br />
==Cosa mi mancherà in Arch64?==<br />
Le seguenti applicazioni non sono ancora compatibili con i 64-bit:<br />
<br />
* La Sun non rilascia il java plugin; Konqueror di KDE ha il suo JavaPlugin integrato! E' la migliore soluzione per utilizzare le applicazioni java oggigiorno. C'è anche il gcj-web-plugin (chiamato gcjplugin in AUR) per usare le applicazioni java nei browser Gecko.<br />
* In realtà Flash supporta solo in parte x86_64 con i prodotti GPL gnash o swfdec che si trovano nei reporitory "extra"<br />
* Macromedia/Adobe non rilascia un Flashplugin nativo, però è possibile utilizzare il plugin a 32-bit installando le lib32. Vedi la guida [[Install Flash on Arch64]]<br />
* Applicazione closed source come skype, opera, necessitano di librerie a 32-bit<br />
** '''Note:'' per l'ultima beta di opera (la 9.50), c'è un port per x86_64. Quindi ci sarà un porting nativo per la prossima release.<br />
* I codec win32 (...che in realtà non servono a nessuno)<br />
* Pacchetti che usano codice assembler per x86 32-bit (alcuni emulatori come zsnes e syslinux)<br />
<br />
<br />
Più o meno tutto il resto dovrebbe essere utilizzabile. Se ti manca un qualsiasi pacchetto per Arch32 nel nostro port, e sai può essere compilato in x86_64 (per esempio perchè l'hai compilato in un altra distro a 64bit senza usare librerie per il 32), semplicemente contatta gli sviluppatori.<br />
<br />
==Can I build 32-bit packages for i686 inside Arch64?==<br />
<br />
Yes. You need a working i686 chroot (installation with i686 iso "quickinstall" is recommended for the quick way to install it inside Arch64). Install "linux32" wrapper pkg from current to make the chroot behave like a real i686 system. Then use this script to login into the chroot environment as root:<br />
<br />
#!/bin/bash<br />
mount --bind /dev /path-to-your-chroot/dev<br />
mount --bind /dev/pts /path-to-your-chroot/dev/pts<br />
mount --bind /dev/shm /path-to-your-chroot/dev/shm<br />
mount -t proc none /path-to-your-chroot/proc<br />
mount -t sysfs none /path-to-your-chroot/sys<br />
linux32 chroot /path-to-your-chroot<br />
<br />
If you keep the sources on the x86_64 host system you can add<br />
"mount --bind /path-to-your-stored-sources /path-to-your-chroot/path-to-your-stored-sources" <br />
to share sources from host to chroot system for pkg building used in /etc/makepkg.conf.<br />
<br />
==Can I run 32-bit apps inside Arch64?==<br />
Yes! <br />
<br />
'''BUT: Our goal is to be the most bleeding-edge distribution around! 32-bit is old-fashioned. We want Arch64 to be modern and pure 64-bit. So we don't have a Multilib system. We won't take any package into the repos improving 32-bit compatibility. Maybe we will place them into the AUR or community repo.'''<br />
'''''Don't expect any support from the devs getting 32-bit apps running on Arch64!'''''<br />
<br />
Boot into Arch64, startx, open a term.<br />
xhost +local:<br />
su<br />
mount /dev/sda1 /mnt/arch32<br />
mount --bind /proc /mnt/arch32/proc<br />
chroot /mnt/arch32<br />
su your32bitusername<br />
/usr/bin/command-you want # or eg: /opt/mozilla/bin/firefox<br />
<br />
Some 32-bit apps (like OpenOffice) may require additional bindings. The following lines can be placed in rc.local to ensure you get all you need for the 32-bit apps (assuming /mnt/arch32 is mounted in fstab):<br />
mount --bind /dev /mnt/arch32/dev<br />
mount --bind /dev/pts /mnt/arch32/dev/pts<br />
mount --bind /dev/shm /mnt/arch32/dev/shm<br />
mount --bind /proc /mnt/arch32/proc<br />
mount --bind /proc/bus/usb /mnt/arch32/proc/bus/usb<br />
mount --bind /sys /mnt/arch32/sys<br />
mount --bind /tmp /mnt/arch32/tmp<br />
#comment the following line if you do not use the same home folder<br />
mount --bind /home /mnt/arch32/home<br />
You can then type in a term:<br />
xhost +localhost<br />
sudo chroot /mnt/arch32 su your32bitusername /opt/openoffice/program/soffice<br />
<br />
==Posso upgradare il mio sistema da i686 a x86_64 senza reinstallare?==<br />
No. Comunque, puoi far partire il sistema con il cd di installazione di Arch64, montare il disco, salvare tutto quello che vuoi tenere che non sia un binario per 32-bit (esempio /home & /etc) e installare</div>Psykopearhttps://wiki.archlinux.org/index.php?title=64-bit_FAQ_(Italiano)&diff=3758264-bit FAQ (Italiano)2008-02-23T18:46:28Z<p>Psykopear: /* Cosa mi mancherà in Arch64? */</p>
<hr />
<div>[[Category:Arch64 (Italiano)]]<br />
[[Category:FAQs (Italiano)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Arch64 FAQ}}<br />
{{i18n_entry|Español|Arch64 FAQ (Español)}}<br />
{{i18n_entry|Italiano|Arch64 FAQ (Italiano)}}<br />
{{i18n_entry|简体中文|Arch64 问答}}<br />
{{i18n_links_end}}<br />
<br />
Di seguito è riportato un elenco di domande frequenti su Arch64. <br />
<br />
==Come faccio a installare Arch64?==<br />
Basta utilizzare il nostro [http://www.archlinux.org/download/ CD di installazione ufficiale].<br />
<br />
==A che punto è il port? Avrò tutti i pacchetti del mio ambiente Arch32?==<br />
I repository Core+Extra sono pronti e quasi tutto è aggiornato, solo poche ore o giorni al massimo dietro Arch Linux i686. I nostri TU stanno provando ad eseguire il port in Community proprio adesso.<br />
<br />
Il port è pronto per l'uso quotidiano in un ambiente desktop o server.<br />
<br />
==64 bit significa un grande aumento di velocità?==<br />
Per le applicazioni che utilizzano una CPU con registri a 64-bit (grandi database e simili), questo è vero nella maggior parte dei casi. Alcune applicazioni multimediali gireranno anche notevolmente più veloce. Se conosci un'applicazione che è notoriamente molto più veloce quando si utilizzano le estensioni SSE3 è possibile ricostruire il pacchetto da sé. Noi ''soltanto''compiliamo con il supporto SSE2 (da marzo=x86_64)e ottimizzazioni -O2.<br />
Per saperne di più leggi http://forums.gentoo.org/viewtopic.php?t=221045 oppure http://www.thejemreport.com/mambo/content/view/74/74/.<br />
<br />
For the rest of the system: It doesn't make any difference if the keyboard waits. <br />
<br />
For further details watch our [[Arch64_ToDoS]]. There you will find a list comparing arch32/arch64 package versions.<br />
<br />
For certain boot problems try these special kernel boot flags: http://www.x86-64.org/lists/discuss/msg03747.html (dead link)<br />
<br />
I have three 64-bit Archies running now, and they perform noticeably better under heavy load. It just seems to deliver more punch.<br />
<br />
==Attenzione quando aggiorni glibc da una versione inferiore alla 2.4!==<br />
E' importante se aggiorni glibc da una versione inferiore alla 2.4 che tu lo faccia a parte. Quindi dai prima pacman -Sy glibc e, se non ci sono problemi, dai pacman -Su. Altrimenti l'aggiornamento della libreria potrebbe fallire e sarai costretto ad usare pacman.static per correggere l'errore.<br />
<br />
==How can I file bugs?==<br />
Simply use Arch's flyspray but note x86_64 in the topic if you think it's a port-related problem!<br />
<br />
==C'è una mailing-list?==<br />
Si, c'è una [http://archlinux.org/mailman/listinfo/arch-ports mailing list] generica riguardante i ports di arch.<br />
<br />
==Quali repository dovrei utilizzare per pacman?==<br />
Tutti i repository sono suppoartati per la versione 64 bit.<br />
<br />
==Come posso reperire i PKGBUILD di Arch64?==<br />
C'è ""ABS"" come per arch 32-bit. La directory raccomandata per metterli è "/var/abs". "ABS" recupera tutti i pacchetti CVS da archlinux.org taggati con CURRENT-64<br />
<br />
==Come posso fare un pacchetto per Arch64 usando un PKGBUILD esistente per la 32-bit?==<br />
Abbiamo i PKGBUILD in comune con Arch32. Puoi prendere quelli non ancora "portati" da CVS: http://www.archlinux.org/cvs/<br />
<br />
==How can I patch existing PKGBUILDs for use with Arch64?==<br />
We add to all ported packages this variable:<br />
arch=('i686' 'x86_64') <br />
Add small patches directly to the sources and md5sums area but use for complete different sources:<br />
[ "$CARCH" = "x86_64" ] && source=(${source[@]} 'other source')<br />
[ "$CARCH" = "x86_64" ] && md5sums=(${md5sums[@]} 'other md5sum')<br />
For any small fix use this in the build area:<br />
[ "$CARCH" = "x86_64" ] && (patch -Np0 -i ../foo_x86_64.patch || return 1)<br />
Or when you need more changes:<br />
if [ "$CARCH" = "x86_64" ]; then<br />
configure/patch/sed # for x86_64<br />
else configure/patch/sed # for i686<br />
fi<br />
For the devs:<br />
cvs commit -m "x86_64 updated/fixed or whatever"<br />
cvs tag -cFR CURRENT-64 foo-package-directory (even for extra, community, unstable and testing)<br />
<br />
==Cosa mi mancherà in Arch64?==<br />
Le seguenti applicazioni non sono ancora compatibili con i 64-bit:<br />
<br />
* La Sun non rilascia il java plugin; Konqueror di KDE ha il suo JavaPlugin integrato! E' la migliore soluzione per utilizzare le applicazioni java oggigiorno. C'è anche il gcj-web-plugin (chiamato gcjplugin in AUR) per usare le applicazioni java nei browser Gecko.<br />
* In realtà Flash supporta solo in parte x86_64 con i prodotti GPL gnash o swfdec che si trovano nei reporitory "extra"<br />
* Macromedia/Adobe non rilascia un Flashplugin nativo, però è possibile utilizzare il plugin a 32-bit installando le lib32. Vedi la guida [[Install Flash on Arch64]]<br />
* Applicazione closed source come skype, opera, necessitano di librerie a 32-bit<br />
** '''Note:'' per l'ultima beta di opera (la 9.50), c'è un port per x86_64. Quindi ci sarà un porting nativo per la prossima release.<br />
* I codec win32 (...che in realtà non servono a nessuno)<br />
* Pacchetti che usano codice assembler per x86 32-bit (alcuni emulatori come zsnes e syslinux)<br />
<br />
<br />
Più o meno tutto il resto dovrebbe essere utilizzabile. Se ti manca un qualsiasi pacchetto per Arch32 nel nostro port, e sai può essere compilato in x86_64 (per esempio perchè l'hai compilato in un altra distro a 64bit senza usare librerie per il 32), semplicemente contatta gli sviluppatori.<br />
<br />
==Can I build 32-bit packages for i686 inside Arch64?==<br />
<br />
Yes. You need a working i686 chroot (installation with i686 iso "quickinstall" is recommended for the quick way to install it inside Arch64). Install "linux32" wrapper pkg from current to make the chroot behave like a real i686 system. Then use this script to login into the chroot environment as root:<br />
<br />
#!/bin/bash<br />
mount --bind /dev /path-to-your-chroot/dev<br />
mount --bind /dev/pts /path-to-your-chroot/dev/pts<br />
mount --bind /dev/shm /path-to-your-chroot/dev/shm<br />
mount -t proc none /path-to-your-chroot/proc<br />
mount -t sysfs none /path-to-your-chroot/sys<br />
linux32 chroot /path-to-your-chroot<br />
<br />
If you keep the sources on the x86_64 host system you can add<br />
"mount --bind /path-to-your-stored-sources /path-to-your-chroot/path-to-your-stored-sources" <br />
to share sources from host to chroot system for pkg building used in /etc/makepkg.conf.<br />
<br />
==Can I run 32-bit apps inside Arch64?==<br />
Yes! <br />
<br />
'''BUT: Our goal is to be the most bleeding-edge distribution around! 32-bit is old-fashioned. We want Arch64 to be modern and pure 64-bit. So we don't have a Multilib system. We won't take any package into the repos improving 32-bit compatibility. Maybe we will place them into the AUR or community repo.'''<br />
'''''Don't expect any support from the devs getting 32-bit apps running on Arch64!'''''<br />
<br />
Boot into Arch64, startx, open a term.<br />
xhost +local:<br />
su<br />
mount /dev/sda1 /mnt/arch32<br />
mount --bind /proc /mnt/arch32/proc<br />
chroot /mnt/arch32<br />
su your32bitusername<br />
/usr/bin/command-you want # or eg: /opt/mozilla/bin/firefox<br />
<br />
Some 32-bit apps (like OpenOffice) may require additional bindings. The following lines can be placed in rc.local to ensure you get all you need for the 32-bit apps (assuming /mnt/arch32 is mounted in fstab):<br />
mount --bind /dev /mnt/arch32/dev<br />
mount --bind /dev/pts /mnt/arch32/dev/pts<br />
mount --bind /dev/shm /mnt/arch32/dev/shm<br />
mount --bind /proc /mnt/arch32/proc<br />
mount --bind /proc/bus/usb /mnt/arch32/proc/bus/usb<br />
mount --bind /sys /mnt/arch32/sys<br />
mount --bind /tmp /mnt/arch32/tmp<br />
#comment the following line if you do not use the same home folder<br />
mount --bind /home /mnt/arch32/home<br />
You can then type in a term:<br />
xhost +localhost<br />
sudo chroot /mnt/arch32 su your32bitusername /opt/openoffice/program/soffice<br />
<br />
==Can I upgrade/switch my system from i686 to x86_64 without reinstalling?==<br />
No. However, you can start the system with the Arch64 install CD, mount the disk, delete anything you may want to keep that isn't a 32-bit binary (e.g: /home & /etc), and install.</div>Psykopearhttps://wiki.archlinux.org/index.php?title=64-bit_FAQ_(Italiano)&diff=3757964-bit FAQ (Italiano)2008-02-23T18:31:37Z<p>Psykopear: /* How can I build new Arch64 packages using existing 32-bit PKGBUILDs? */</p>
<hr />
<div>[[Category:Arch64 (Italiano)]]<br />
[[Category:FAQs (Italiano)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Arch64 FAQ}}<br />
{{i18n_entry|Español|Arch64 FAQ (Español)}}<br />
{{i18n_entry|Italiano|Arch64 FAQ (Italiano)}}<br />
{{i18n_entry|简体中文|Arch64 问答}}<br />
{{i18n_links_end}}<br />
<br />
Di seguito è riportato un elenco di domande frequenti su Arch64. <br />
<br />
==Come faccio a installare Arch64?==<br />
Basta utilizzare il nostro [http://www.archlinux.org/download/ CD di installazione ufficiale].<br />
<br />
==A che punto è il port? Avrò tutti i pacchetti del mio ambiente Arch32?==<br />
I repository Core+Extra sono pronti e quasi tutto è aggiornato, solo poche ore o giorni al massimo dietro Arch Linux i686. I nostri TU stanno provando ad eseguire il port in Community proprio adesso.<br />
<br />
Il port è pronto per l'uso quotidiano in un ambiente desktop o server.<br />
<br />
==64 bit significa un grande aumento di velocità?==<br />
Per le applicazioni che utilizzano una CPU con registri a 64-bit (grandi database e simili), questo è vero nella maggior parte dei casi. Alcune applicazioni multimediali gireranno anche notevolmente più veloce. Se conosci un'applicazione che è notoriamente molto più veloce quando si utilizzano le estensioni SSE3 è possibile ricostruire il pacchetto da sé. Noi ''soltanto''compiliamo con il supporto SSE2 (da marzo=x86_64)e ottimizzazioni -O2.<br />
Per saperne di più leggi http://forums.gentoo.org/viewtopic.php?t=221045 oppure http://www.thejemreport.com/mambo/content/view/74/74/.<br />
<br />
For the rest of the system: It doesn't make any difference if the keyboard waits. <br />
<br />
For further details watch our [[Arch64_ToDoS]]. There you will find a list comparing arch32/arch64 package versions.<br />
<br />
For certain boot problems try these special kernel boot flags: http://www.x86-64.org/lists/discuss/msg03747.html (dead link)<br />
<br />
I have three 64-bit Archies running now, and they perform noticeably better under heavy load. It just seems to deliver more punch.<br />
<br />
==Attenzione quando aggiorni glibc da una versione inferiore alla 2.4!==<br />
E' importante se aggiorni glibc da una versione inferiore alla 2.4 che tu lo faccia a parte. Quindi dai prima pacman -Sy glibc e, se non ci sono problemi, dai pacman -Su. Altrimenti l'aggiornamento della libreria potrebbe fallire e sarai costretto ad usare pacman.static per correggere l'errore.<br />
<br />
==How can I file bugs?==<br />
Simply use Arch's flyspray but note x86_64 in the topic if you think it's a port-related problem!<br />
<br />
==C'è una mailing-list?==<br />
Si, c'è una [http://archlinux.org/mailman/listinfo/arch-ports mailing list] generica riguardante i ports di arch.<br />
<br />
==Quali repository dovrei utilizzare per pacman?==<br />
Tutti i repository sono suppoartati per la versione 64 bit.<br />
<br />
==Come posso reperire i PKGBUILD di Arch64?==<br />
C'è ""ABS"" come per arch 32-bit. La directory raccomandata per metterli è "/var/abs". "ABS" recupera tutti i pacchetti CVS da archlinux.org taggati con CURRENT-64<br />
<br />
==Come posso fare un pacchetto per Arch64 usando un PKGBUILD esistente per la 32-bit?==<br />
Abbiamo i PKGBUILD in comune con Arch32. Puoi prendere quelli non ancora "portati" da CVS: http://www.archlinux.org/cvs/<br />
<br />
==How can I patch existing PKGBUILDs for use with Arch64?==<br />
We add to all ported packages this variable:<br />
arch=('i686' 'x86_64') <br />
Add small patches directly to the sources and md5sums area but use for complete different sources:<br />
[ "$CARCH" = "x86_64" ] && source=(${source[@]} 'other source')<br />
[ "$CARCH" = "x86_64" ] && md5sums=(${md5sums[@]} 'other md5sum')<br />
For any small fix use this in the build area:<br />
[ "$CARCH" = "x86_64" ] && (patch -Np0 -i ../foo_x86_64.patch || return 1)<br />
Or when you need more changes:<br />
if [ "$CARCH" = "x86_64" ]; then<br />
configure/patch/sed # for x86_64<br />
else configure/patch/sed # for i686<br />
fi<br />
For the devs:<br />
cvs commit -m "x86_64 updated/fixed or whatever"<br />
cvs tag -cFR CURRENT-64 foo-package-directory (even for extra, community, unstable and testing)<br />
<br />
==What will I miss in Arch64?==<br />
The following applications are known not to be 64-bit compatible:<br />
<br />
* no Java plugin shipped by Sun; KDE's Konqueror has its own native running 64-bit JavaPlugin built in! Best solution to browse JavaApplets these days. There is also a gcj-web-plugin (called gcjplugin in AUR) to use Java-Applets in Gecko browsers.<br />
* true x86_64 Flash support only in parts with GPL gnash or swfdec package from extra repo<br />
* no native Flash plugin shipped by Macromedia/Adobe - nspluginwrapper package from community allows use of 32-bit plugins but forces installation of lib32 packages - follow this guide on how to [[Install Flash on Arch64]]<br />
* Closed-source apps like Skype, Opera - where they don't provide 100% statically built binaries so 32-bit libs are still needed<br />
** '''Note:''' for the last opera 9.50 beta 1, there is a x86_64 port. So for the next release of opera, a native port to x86_64 is expected.<br />
* additional win32 codecs (... that nobody really needs)<br />
* packages that use x86 32-bit assembler code (some emulators like zsnes and syslinux)<br />
<br />
<br />
Almost everything else should be portable. If you miss any Arch32 package in our port and you know that it will compile on x86_64 (e.g. you have found it in another 64-bit distribution without using multilibs), just contact the devs.<br />
<br />
==Can I build 32-bit packages for i686 inside Arch64?==<br />
<br />
Yes. You need a working i686 chroot (installation with i686 iso "quickinstall" is recommended for the quick way to install it inside Arch64). Install "linux32" wrapper pkg from current to make the chroot behave like a real i686 system. Then use this script to login into the chroot environment as root:<br />
<br />
#!/bin/bash<br />
mount --bind /dev /path-to-your-chroot/dev<br />
mount --bind /dev/pts /path-to-your-chroot/dev/pts<br />
mount --bind /dev/shm /path-to-your-chroot/dev/shm<br />
mount -t proc none /path-to-your-chroot/proc<br />
mount -t sysfs none /path-to-your-chroot/sys<br />
linux32 chroot /path-to-your-chroot<br />
<br />
If you keep the sources on the x86_64 host system you can add<br />
"mount --bind /path-to-your-stored-sources /path-to-your-chroot/path-to-your-stored-sources" <br />
to share sources from host to chroot system for pkg building used in /etc/makepkg.conf.<br />
<br />
==Can I run 32-bit apps inside Arch64?==<br />
Yes! <br />
<br />
'''BUT: Our goal is to be the most bleeding-edge distribution around! 32-bit is old-fashioned. We want Arch64 to be modern and pure 64-bit. So we don't have a Multilib system. We won't take any package into the repos improving 32-bit compatibility. Maybe we will place them into the AUR or community repo.'''<br />
'''''Don't expect any support from the devs getting 32-bit apps running on Arch64!'''''<br />
<br />
Boot into Arch64, startx, open a term.<br />
xhost +local:<br />
su<br />
mount /dev/sda1 /mnt/arch32<br />
mount --bind /proc /mnt/arch32/proc<br />
chroot /mnt/arch32<br />
su your32bitusername<br />
/usr/bin/command-you want # or eg: /opt/mozilla/bin/firefox<br />
<br />
Some 32-bit apps (like OpenOffice) may require additional bindings. The following lines can be placed in rc.local to ensure you get all you need for the 32-bit apps (assuming /mnt/arch32 is mounted in fstab):<br />
mount --bind /dev /mnt/arch32/dev<br />
mount --bind /dev/pts /mnt/arch32/dev/pts<br />
mount --bind /dev/shm /mnt/arch32/dev/shm<br />
mount --bind /proc /mnt/arch32/proc<br />
mount --bind /proc/bus/usb /mnt/arch32/proc/bus/usb<br />
mount --bind /sys /mnt/arch32/sys<br />
mount --bind /tmp /mnt/arch32/tmp<br />
#comment the following line if you do not use the same home folder<br />
mount --bind /home /mnt/arch32/home<br />
You can then type in a term:<br />
xhost +localhost<br />
sudo chroot /mnt/arch32 su your32bitusername /opt/openoffice/program/soffice<br />
<br />
==Can I upgrade/switch my system from i686 to x86_64 without reinstalling?==<br />
No. However, you can start the system with the Arch64 install CD, mount the disk, delete anything you may want to keep that isn't a 32-bit binary (e.g: /home & /etc), and install.</div>Psykopearhttps://wiki.archlinux.org/index.php?title=64-bit_FAQ_(Italiano)&diff=3757864-bit FAQ (Italiano)2008-02-23T18:28:55Z<p>Psykopear: /* Come posso reperire i PKGBUILD di Arch64? */</p>
<hr />
<div>[[Category:Arch64 (Italiano)]]<br />
[[Category:FAQs (Italiano)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Arch64 FAQ}}<br />
{{i18n_entry|Español|Arch64 FAQ (Español)}}<br />
{{i18n_entry|Italiano|Arch64 FAQ (Italiano)}}<br />
{{i18n_entry|简体中文|Arch64 问答}}<br />
{{i18n_links_end}}<br />
<br />
Di seguito è riportato un elenco di domande frequenti su Arch64. <br />
<br />
==Come faccio a installare Arch64?==<br />
Basta utilizzare il nostro [http://www.archlinux.org/download/ CD di installazione ufficiale].<br />
<br />
==A che punto è il port? Avrò tutti i pacchetti del mio ambiente Arch32?==<br />
I repository Core+Extra sono pronti e quasi tutto è aggiornato, solo poche ore o giorni al massimo dietro Arch Linux i686. I nostri TU stanno provando ad eseguire il port in Community proprio adesso.<br />
<br />
Il port è pronto per l'uso quotidiano in un ambiente desktop o server.<br />
<br />
==64 bit significa un grande aumento di velocità?==<br />
Per le applicazioni che utilizzano una CPU con registri a 64-bit (grandi database e simili), questo è vero nella maggior parte dei casi. Alcune applicazioni multimediali gireranno anche notevolmente più veloce. Se conosci un'applicazione che è notoriamente molto più veloce quando si utilizzano le estensioni SSE3 è possibile ricostruire il pacchetto da sé. Noi ''soltanto''compiliamo con il supporto SSE2 (da marzo=x86_64)e ottimizzazioni -O2.<br />
Per saperne di più leggi http://forums.gentoo.org/viewtopic.php?t=221045 oppure http://www.thejemreport.com/mambo/content/view/74/74/.<br />
<br />
For the rest of the system: It doesn't make any difference if the keyboard waits. <br />
<br />
For further details watch our [[Arch64_ToDoS]]. There you will find a list comparing arch32/arch64 package versions.<br />
<br />
For certain boot problems try these special kernel boot flags: http://www.x86-64.org/lists/discuss/msg03747.html (dead link)<br />
<br />
I have three 64-bit Archies running now, and they perform noticeably better under heavy load. It just seems to deliver more punch.<br />
<br />
==Attenzione quando aggiorni glibc da una versione inferiore alla 2.4!==<br />
E' importante se aggiorni glibc da una versione inferiore alla 2.4 che tu lo faccia a parte. Quindi dai prima pacman -Sy glibc e, se non ci sono problemi, dai pacman -Su. Altrimenti l'aggiornamento della libreria potrebbe fallire e sarai costretto ad usare pacman.static per correggere l'errore.<br />
<br />
==How can I file bugs?==<br />
Simply use Arch's flyspray but note x86_64 in the topic if you think it's a port-related problem!<br />
<br />
==C'è una mailing-list?==<br />
Si, c'è una [http://archlinux.org/mailman/listinfo/arch-ports mailing list] generica riguardante i ports di arch.<br />
<br />
==Quali repository dovrei utilizzare per pacman?==<br />
Tutti i repository sono suppoartati per la versione 64 bit.<br />
<br />
==Come posso reperire i PKGBUILD di Arch64?==<br />
C'è ""ABS"" come per arch 32-bit. La directory raccomandata per metterli è "/var/abs". "ABS" recupera tutti i pacchetti CVS da archlinux.org taggati con CURRENT-64<br />
<br />
==How can I build new Arch64 packages using existing 32-bit PKGBUILDs?==<br />
We have common PKGBUILDs with Arch32. You can get not-yet-ported 32-bit PKGBUILDs from CVS: http://www.archlinux.org/cvs/<br />
<br />
==How can I patch existing PKGBUILDs for use with Arch64?==<br />
We add to all ported packages this variable:<br />
arch=('i686' 'x86_64') <br />
Add small patches directly to the sources and md5sums area but use for complete different sources:<br />
[ "$CARCH" = "x86_64" ] && source=(${source[@]} 'other source')<br />
[ "$CARCH" = "x86_64" ] && md5sums=(${md5sums[@]} 'other md5sum')<br />
For any small fix use this in the build area:<br />
[ "$CARCH" = "x86_64" ] && (patch -Np0 -i ../foo_x86_64.patch || return 1)<br />
Or when you need more changes:<br />
if [ "$CARCH" = "x86_64" ]; then<br />
configure/patch/sed # for x86_64<br />
else configure/patch/sed # for i686<br />
fi<br />
For the devs:<br />
cvs commit -m "x86_64 updated/fixed or whatever"<br />
cvs tag -cFR CURRENT-64 foo-package-directory (even for extra, community, unstable and testing)<br />
<br />
==What will I miss in Arch64?==<br />
The following applications are known not to be 64-bit compatible:<br />
<br />
* no Java plugin shipped by Sun; KDE's Konqueror has its own native running 64-bit JavaPlugin built in! Best solution to browse JavaApplets these days. There is also a gcj-web-plugin (called gcjplugin in AUR) to use Java-Applets in Gecko browsers.<br />
* true x86_64 Flash support only in parts with GPL gnash or swfdec package from extra repo<br />
* no native Flash plugin shipped by Macromedia/Adobe - nspluginwrapper package from community allows use of 32-bit plugins but forces installation of lib32 packages - follow this guide on how to [[Install Flash on Arch64]]<br />
* Closed-source apps like Skype, Opera - where they don't provide 100% statically built binaries so 32-bit libs are still needed<br />
** '''Note:''' for the last opera 9.50 beta 1, there is a x86_64 port. So for the next release of opera, a native port to x86_64 is expected.<br />
* additional win32 codecs (... that nobody really needs)<br />
* packages that use x86 32-bit assembler code (some emulators like zsnes and syslinux)<br />
<br />
<br />
Almost everything else should be portable. If you miss any Arch32 package in our port and you know that it will compile on x86_64 (e.g. you have found it in another 64-bit distribution without using multilibs), just contact the devs.<br />
<br />
==Can I build 32-bit packages for i686 inside Arch64?==<br />
<br />
Yes. You need a working i686 chroot (installation with i686 iso "quickinstall" is recommended for the quick way to install it inside Arch64). Install "linux32" wrapper pkg from current to make the chroot behave like a real i686 system. Then use this script to login into the chroot environment as root:<br />
<br />
#!/bin/bash<br />
mount --bind /dev /path-to-your-chroot/dev<br />
mount --bind /dev/pts /path-to-your-chroot/dev/pts<br />
mount --bind /dev/shm /path-to-your-chroot/dev/shm<br />
mount -t proc none /path-to-your-chroot/proc<br />
mount -t sysfs none /path-to-your-chroot/sys<br />
linux32 chroot /path-to-your-chroot<br />
<br />
If you keep the sources on the x86_64 host system you can add<br />
"mount --bind /path-to-your-stored-sources /path-to-your-chroot/path-to-your-stored-sources" <br />
to share sources from host to chroot system for pkg building used in /etc/makepkg.conf.<br />
<br />
==Can I run 32-bit apps inside Arch64?==<br />
Yes! <br />
<br />
'''BUT: Our goal is to be the most bleeding-edge distribution around! 32-bit is old-fashioned. We want Arch64 to be modern and pure 64-bit. So we don't have a Multilib system. We won't take any package into the repos improving 32-bit compatibility. Maybe we will place them into the AUR or community repo.'''<br />
'''''Don't expect any support from the devs getting 32-bit apps running on Arch64!'''''<br />
<br />
Boot into Arch64, startx, open a term.<br />
xhost +local:<br />
su<br />
mount /dev/sda1 /mnt/arch32<br />
mount --bind /proc /mnt/arch32/proc<br />
chroot /mnt/arch32<br />
su your32bitusername<br />
/usr/bin/command-you want # or eg: /opt/mozilla/bin/firefox<br />
<br />
Some 32-bit apps (like OpenOffice) may require additional bindings. The following lines can be placed in rc.local to ensure you get all you need for the 32-bit apps (assuming /mnt/arch32 is mounted in fstab):<br />
mount --bind /dev /mnt/arch32/dev<br />
mount --bind /dev/pts /mnt/arch32/dev/pts<br />
mount --bind /dev/shm /mnt/arch32/dev/shm<br />
mount --bind /proc /mnt/arch32/proc<br />
mount --bind /proc/bus/usb /mnt/arch32/proc/bus/usb<br />
mount --bind /sys /mnt/arch32/sys<br />
mount --bind /tmp /mnt/arch32/tmp<br />
#comment the following line if you do not use the same home folder<br />
mount --bind /home /mnt/arch32/home<br />
You can then type in a term:<br />
xhost +localhost<br />
sudo chroot /mnt/arch32 su your32bitusername /opt/openoffice/program/soffice<br />
<br />
==Can I upgrade/switch my system from i686 to x86_64 without reinstalling?==<br />
No. However, you can start the system with the Arch64 install CD, mount the disk, delete anything you may want to keep that isn't a 32-bit binary (e.g: /home & /etc), and install.</div>Psykopearhttps://wiki.archlinux.org/index.php?title=64-bit_FAQ_(Italiano)&diff=3757664-bit FAQ (Italiano)2008-02-23T18:25:52Z<p>Psykopear: /* Quali repository dovrei utilizzare per pacman? */</p>
<hr />
<div>[[Category:Arch64 (Italiano)]]<br />
[[Category:FAQs (Italiano)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Arch64 FAQ}}<br />
{{i18n_entry|Español|Arch64 FAQ (Español)}}<br />
{{i18n_entry|Italiano|Arch64 FAQ (Italiano)}}<br />
{{i18n_entry|简体中文|Arch64 问答}}<br />
{{i18n_links_end}}<br />
<br />
Di seguito è riportato un elenco di domande frequenti su Arch64. <br />
<br />
==Come faccio a installare Arch64?==<br />
Basta utilizzare il nostro [http://www.archlinux.org/download/ CD di installazione ufficiale].<br />
<br />
==A che punto è il port? Avrò tutti i pacchetti del mio ambiente Arch32?==<br />
I repository Core+Extra sono pronti e quasi tutto è aggiornato, solo poche ore o giorni al massimo dietro Arch Linux i686. I nostri TU stanno provando ad eseguire il port in Community proprio adesso.<br />
<br />
Il port è pronto per l'uso quotidiano in un ambiente desktop o server.<br />
<br />
==64 bit significa un grande aumento di velocità?==<br />
Per le applicazioni che utilizzano una CPU con registri a 64-bit (grandi database e simili), questo è vero nella maggior parte dei casi. Alcune applicazioni multimediali gireranno anche notevolmente più veloce. Se conosci un'applicazione che è notoriamente molto più veloce quando si utilizzano le estensioni SSE3 è possibile ricostruire il pacchetto da sé. Noi ''soltanto''compiliamo con il supporto SSE2 (da marzo=x86_64)e ottimizzazioni -O2.<br />
Per saperne di più leggi http://forums.gentoo.org/viewtopic.php?t=221045 oppure http://www.thejemreport.com/mambo/content/view/74/74/.<br />
<br />
For the rest of the system: It doesn't make any difference if the keyboard waits. <br />
<br />
For further details watch our [[Arch64_ToDoS]]. There you will find a list comparing arch32/arch64 package versions.<br />
<br />
For certain boot problems try these special kernel boot flags: http://www.x86-64.org/lists/discuss/msg03747.html (dead link)<br />
<br />
I have three 64-bit Archies running now, and they perform noticeably better under heavy load. It just seems to deliver more punch.<br />
<br />
==Attenzione quando aggiorni glibc da una versione inferiore alla 2.4!==<br />
E' importante se aggiorni glibc da una versione inferiore alla 2.4 che tu lo faccia a parte. Quindi dai prima pacman -Sy glibc e, se non ci sono problemi, dai pacman -Su. Altrimenti l'aggiornamento della libreria potrebbe fallire e sarai costretto ad usare pacman.static per correggere l'errore.<br />
<br />
==How can I file bugs?==<br />
Simply use Arch's flyspray but note x86_64 in the topic if you think it's a port-related problem!<br />
<br />
==C'è una mailing-list?==<br />
Si, c'è una [http://archlinux.org/mailman/listinfo/arch-ports mailing list] generica riguardante i ports di arch.<br />
<br />
==Quali repository dovrei utilizzare per pacman?==<br />
Tutti i repository sono suppoartati per la versione 64 bit.<br />
<br />
==How can I get the Arch64 PKGBUILDs?==<br />
We have '''''ABS''''' as Arch 32-bit. Recommended place to store is ''/var/abs''. ''abs'' fetches all CVS entries from archlinux.org tagged with CURRENT-64.<br />
<br />
==How can I build new Arch64 packages using existing 32-bit PKGBUILDs?==<br />
We have common PKGBUILDs with Arch32. You can get not-yet-ported 32-bit PKGBUILDs from CVS: http://www.archlinux.org/cvs/<br />
<br />
==How can I patch existing PKGBUILDs for use with Arch64?==<br />
We add to all ported packages this variable:<br />
arch=('i686' 'x86_64') <br />
Add small patches directly to the sources and md5sums area but use for complete different sources:<br />
[ "$CARCH" = "x86_64" ] && source=(${source[@]} 'other source')<br />
[ "$CARCH" = "x86_64" ] && md5sums=(${md5sums[@]} 'other md5sum')<br />
For any small fix use this in the build area:<br />
[ "$CARCH" = "x86_64" ] && (patch -Np0 -i ../foo_x86_64.patch || return 1)<br />
Or when you need more changes:<br />
if [ "$CARCH" = "x86_64" ]; then<br />
configure/patch/sed # for x86_64<br />
else configure/patch/sed # for i686<br />
fi<br />
For the devs:<br />
cvs commit -m "x86_64 updated/fixed or whatever"<br />
cvs tag -cFR CURRENT-64 foo-package-directory (even for extra, community, unstable and testing)<br />
<br />
==What will I miss in Arch64?==<br />
The following applications are known not to be 64-bit compatible:<br />
<br />
* no Java plugin shipped by Sun; KDE's Konqueror has its own native running 64-bit JavaPlugin built in! Best solution to browse JavaApplets these days. There is also a gcj-web-plugin (called gcjplugin in AUR) to use Java-Applets in Gecko browsers.<br />
* true x86_64 Flash support only in parts with GPL gnash or swfdec package from extra repo<br />
* no native Flash plugin shipped by Macromedia/Adobe - nspluginwrapper package from community allows use of 32-bit plugins but forces installation of lib32 packages - follow this guide on how to [[Install Flash on Arch64]]<br />
* Closed-source apps like Skype, Opera - where they don't provide 100% statically built binaries so 32-bit libs are still needed<br />
** '''Note:''' for the last opera 9.50 beta 1, there is a x86_64 port. So for the next release of opera, a native port to x86_64 is expected.<br />
* additional win32 codecs (... that nobody really needs)<br />
* packages that use x86 32-bit assembler code (some emulators like zsnes and syslinux)<br />
<br />
<br />
Almost everything else should be portable. If you miss any Arch32 package in our port and you know that it will compile on x86_64 (e.g. you have found it in another 64-bit distribution without using multilibs), just contact the devs.<br />
<br />
==Can I build 32-bit packages for i686 inside Arch64?==<br />
<br />
Yes. You need a working i686 chroot (installation with i686 iso "quickinstall" is recommended for the quick way to install it inside Arch64). Install "linux32" wrapper pkg from current to make the chroot behave like a real i686 system. Then use this script to login into the chroot environment as root:<br />
<br />
#!/bin/bash<br />
mount --bind /dev /path-to-your-chroot/dev<br />
mount --bind /dev/pts /path-to-your-chroot/dev/pts<br />
mount --bind /dev/shm /path-to-your-chroot/dev/shm<br />
mount -t proc none /path-to-your-chroot/proc<br />
mount -t sysfs none /path-to-your-chroot/sys<br />
linux32 chroot /path-to-your-chroot<br />
<br />
If you keep the sources on the x86_64 host system you can add<br />
"mount --bind /path-to-your-stored-sources /path-to-your-chroot/path-to-your-stored-sources" <br />
to share sources from host to chroot system for pkg building used in /etc/makepkg.conf.<br />
<br />
==Can I run 32-bit apps inside Arch64?==<br />
Yes! <br />
<br />
'''BUT: Our goal is to be the most bleeding-edge distribution around! 32-bit is old-fashioned. We want Arch64 to be modern and pure 64-bit. So we don't have a Multilib system. We won't take any package into the repos improving 32-bit compatibility. Maybe we will place them into the AUR or community repo.'''<br />
'''''Don't expect any support from the devs getting 32-bit apps running on Arch64!'''''<br />
<br />
Boot into Arch64, startx, open a term.<br />
xhost +local:<br />
su<br />
mount /dev/sda1 /mnt/arch32<br />
mount --bind /proc /mnt/arch32/proc<br />
chroot /mnt/arch32<br />
su your32bitusername<br />
/usr/bin/command-you want # or eg: /opt/mozilla/bin/firefox<br />
<br />
Some 32-bit apps (like OpenOffice) may require additional bindings. The following lines can be placed in rc.local to ensure you get all you need for the 32-bit apps (assuming /mnt/arch32 is mounted in fstab):<br />
mount --bind /dev /mnt/arch32/dev<br />
mount --bind /dev/pts /mnt/arch32/dev/pts<br />
mount --bind /dev/shm /mnt/arch32/dev/shm<br />
mount --bind /proc /mnt/arch32/proc<br />
mount --bind /proc/bus/usb /mnt/arch32/proc/bus/usb<br />
mount --bind /sys /mnt/arch32/sys<br />
mount --bind /tmp /mnt/arch32/tmp<br />
#comment the following line if you do not use the same home folder<br />
mount --bind /home /mnt/arch32/home<br />
You can then type in a term:<br />
xhost +localhost<br />
sudo chroot /mnt/arch32 su your32bitusername /opt/openoffice/program/soffice<br />
<br />
==Can I upgrade/switch my system from i686 to x86_64 without reinstalling?==<br />
No. However, you can start the system with the Arch64 install CD, mount the disk, delete anything you may want to keep that isn't a 32-bit binary (e.g: /home & /etc), and install.</div>Psykopearhttps://wiki.archlinux.org/index.php?title=64-bit_FAQ_(Italiano)&diff=3757564-bit FAQ (Italiano)2008-02-23T18:24:20Z<p>Psykopear: /* C'è una mailing-list? */</p>
<hr />
<div>[[Category:Arch64 (Italiano)]]<br />
[[Category:FAQs (Italiano)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Arch64 FAQ}}<br />
{{i18n_entry|Español|Arch64 FAQ (Español)}}<br />
{{i18n_entry|Italiano|Arch64 FAQ (Italiano)}}<br />
{{i18n_entry|简体中文|Arch64 问答}}<br />
{{i18n_links_end}}<br />
<br />
Di seguito è riportato un elenco di domande frequenti su Arch64. <br />
<br />
==Come faccio a installare Arch64?==<br />
Basta utilizzare il nostro [http://www.archlinux.org/download/ CD di installazione ufficiale].<br />
<br />
==A che punto è il port? Avrò tutti i pacchetti del mio ambiente Arch32?==<br />
I repository Core+Extra sono pronti e quasi tutto è aggiornato, solo poche ore o giorni al massimo dietro Arch Linux i686. I nostri TU stanno provando ad eseguire il port in Community proprio adesso.<br />
<br />
Il port è pronto per l'uso quotidiano in un ambiente desktop o server.<br />
<br />
==64 bit significa un grande aumento di velocità?==<br />
Per le applicazioni che utilizzano una CPU con registri a 64-bit (grandi database e simili), questo è vero nella maggior parte dei casi. Alcune applicazioni multimediali gireranno anche notevolmente più veloce. Se conosci un'applicazione che è notoriamente molto più veloce quando si utilizzano le estensioni SSE3 è possibile ricostruire il pacchetto da sé. Noi ''soltanto''compiliamo con il supporto SSE2 (da marzo=x86_64)e ottimizzazioni -O2.<br />
Per saperne di più leggi http://forums.gentoo.org/viewtopic.php?t=221045 oppure http://www.thejemreport.com/mambo/content/view/74/74/.<br />
<br />
For the rest of the system: It doesn't make any difference if the keyboard waits. <br />
<br />
For further details watch our [[Arch64_ToDoS]]. There you will find a list comparing arch32/arch64 package versions.<br />
<br />
For certain boot problems try these special kernel boot flags: http://www.x86-64.org/lists/discuss/msg03747.html (dead link)<br />
<br />
I have three 64-bit Archies running now, and they perform noticeably better under heavy load. It just seems to deliver more punch.<br />
<br />
==Attenzione quando aggiorni glibc da una versione inferiore alla 2.4!==<br />
E' importante se aggiorni glibc da una versione inferiore alla 2.4 che tu lo faccia a parte. Quindi dai prima pacman -Sy glibc e, se non ci sono problemi, dai pacman -Su. Altrimenti l'aggiornamento della libreria potrebbe fallire e sarai costretto ad usare pacman.static per correggere l'errore.<br />
<br />
==How can I file bugs?==<br />
Simply use Arch's flyspray but note x86_64 in the topic if you think it's a port-related problem!<br />
<br />
==C'è una mailing-list?==<br />
Si, c'è una [http://archlinux.org/mailman/listinfo/arch-ports mailing list] generica riguardante i ports di arch.<br />
<br />
==What repos should I set up for pacman to use?==<br />
All repos are supported for the port.<br />
<br />
==How can I get the Arch64 PKGBUILDs?==<br />
We have '''''ABS''''' as Arch 32-bit. Recommended place to store is ''/var/abs''. ''abs'' fetches all CVS entries from archlinux.org tagged with CURRENT-64.<br />
<br />
==How can I build new Arch64 packages using existing 32-bit PKGBUILDs?==<br />
We have common PKGBUILDs with Arch32. You can get not-yet-ported 32-bit PKGBUILDs from CVS: http://www.archlinux.org/cvs/<br />
<br />
==How can I patch existing PKGBUILDs for use with Arch64?==<br />
We add to all ported packages this variable:<br />
arch=('i686' 'x86_64') <br />
Add small patches directly to the sources and md5sums area but use for complete different sources:<br />
[ "$CARCH" = "x86_64" ] && source=(${source[@]} 'other source')<br />
[ "$CARCH" = "x86_64" ] && md5sums=(${md5sums[@]} 'other md5sum')<br />
For any small fix use this in the build area:<br />
[ "$CARCH" = "x86_64" ] && (patch -Np0 -i ../foo_x86_64.patch || return 1)<br />
Or when you need more changes:<br />
if [ "$CARCH" = "x86_64" ]; then<br />
configure/patch/sed # for x86_64<br />
else configure/patch/sed # for i686<br />
fi<br />
For the devs:<br />
cvs commit -m "x86_64 updated/fixed or whatever"<br />
cvs tag -cFR CURRENT-64 foo-package-directory (even for extra, community, unstable and testing)<br />
<br />
==What will I miss in Arch64?==<br />
The following applications are known not to be 64-bit compatible:<br />
<br />
* no Java plugin shipped by Sun; KDE's Konqueror has its own native running 64-bit JavaPlugin built in! Best solution to browse JavaApplets these days. There is also a gcj-web-plugin (called gcjplugin in AUR) to use Java-Applets in Gecko browsers.<br />
* true x86_64 Flash support only in parts with GPL gnash or swfdec package from extra repo<br />
* no native Flash plugin shipped by Macromedia/Adobe - nspluginwrapper package from community allows use of 32-bit plugins but forces installation of lib32 packages - follow this guide on how to [[Install Flash on Arch64]]<br />
* Closed-source apps like Skype, Opera - where they don't provide 100% statically built binaries so 32-bit libs are still needed<br />
** '''Note:''' for the last opera 9.50 beta 1, there is a x86_64 port. So for the next release of opera, a native port to x86_64 is expected.<br />
* additional win32 codecs (... that nobody really needs)<br />
* packages that use x86 32-bit assembler code (some emulators like zsnes and syslinux)<br />
<br />
<br />
Almost everything else should be portable. If you miss any Arch32 package in our port and you know that it will compile on x86_64 (e.g. you have found it in another 64-bit distribution without using multilibs), just contact the devs.<br />
<br />
==Can I build 32-bit packages for i686 inside Arch64?==<br />
<br />
Yes. You need a working i686 chroot (installation with i686 iso "quickinstall" is recommended for the quick way to install it inside Arch64). Install "linux32" wrapper pkg from current to make the chroot behave like a real i686 system. Then use this script to login into the chroot environment as root:<br />
<br />
#!/bin/bash<br />
mount --bind /dev /path-to-your-chroot/dev<br />
mount --bind /dev/pts /path-to-your-chroot/dev/pts<br />
mount --bind /dev/shm /path-to-your-chroot/dev/shm<br />
mount -t proc none /path-to-your-chroot/proc<br />
mount -t sysfs none /path-to-your-chroot/sys<br />
linux32 chroot /path-to-your-chroot<br />
<br />
If you keep the sources on the x86_64 host system you can add<br />
"mount --bind /path-to-your-stored-sources /path-to-your-chroot/path-to-your-stored-sources" <br />
to share sources from host to chroot system for pkg building used in /etc/makepkg.conf.<br />
<br />
==Can I run 32-bit apps inside Arch64?==<br />
Yes! <br />
<br />
'''BUT: Our goal is to be the most bleeding-edge distribution around! 32-bit is old-fashioned. We want Arch64 to be modern and pure 64-bit. So we don't have a Multilib system. We won't take any package into the repos improving 32-bit compatibility. Maybe we will place them into the AUR or community repo.'''<br />
'''''Don't expect any support from the devs getting 32-bit apps running on Arch64!'''''<br />
<br />
Boot into Arch64, startx, open a term.<br />
xhost +local:<br />
su<br />
mount /dev/sda1 /mnt/arch32<br />
mount --bind /proc /mnt/arch32/proc<br />
chroot /mnt/arch32<br />
su your32bitusername<br />
/usr/bin/command-you want # or eg: /opt/mozilla/bin/firefox<br />
<br />
Some 32-bit apps (like OpenOffice) may require additional bindings. The following lines can be placed in rc.local to ensure you get all you need for the 32-bit apps (assuming /mnt/arch32 is mounted in fstab):<br />
mount --bind /dev /mnt/arch32/dev<br />
mount --bind /dev/pts /mnt/arch32/dev/pts<br />
mount --bind /dev/shm /mnt/arch32/dev/shm<br />
mount --bind /proc /mnt/arch32/proc<br />
mount --bind /proc/bus/usb /mnt/arch32/proc/bus/usb<br />
mount --bind /sys /mnt/arch32/sys<br />
mount --bind /tmp /mnt/arch32/tmp<br />
#comment the following line if you do not use the same home folder<br />
mount --bind /home /mnt/arch32/home<br />
You can then type in a term:<br />
xhost +localhost<br />
sudo chroot /mnt/arch32 su your32bitusername /opt/openoffice/program/soffice<br />
<br />
==Can I upgrade/switch my system from i686 to x86_64 without reinstalling?==<br />
No. However, you can start the system with the Arch64 install CD, mount the disk, delete anything you may want to keep that isn't a 32-bit binary (e.g: /home & /etc), and install.</div>Psykopearhttps://wiki.archlinux.org/index.php?title=64-bit_FAQ_(Italiano)&diff=3757464-bit FAQ (Italiano)2008-02-23T18:22:10Z<p>Psykopear: /* Attenzione quando aggiorni glibc da una versione inferiore alla 2.4! */</p>
<hr />
<div>[[Category:Arch64 (Italiano)]]<br />
[[Category:FAQs (Italiano)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Arch64 FAQ}}<br />
{{i18n_entry|Español|Arch64 FAQ (Español)}}<br />
{{i18n_entry|Italiano|Arch64 FAQ (Italiano)}}<br />
{{i18n_entry|简体中文|Arch64 问答}}<br />
{{i18n_links_end}}<br />
<br />
Di seguito è riportato un elenco di domande frequenti su Arch64. <br />
<br />
==Come faccio a installare Arch64?==<br />
Basta utilizzare il nostro [http://www.archlinux.org/download/ CD di installazione ufficiale].<br />
<br />
==A che punto è il port? Avrò tutti i pacchetti del mio ambiente Arch32?==<br />
I repository Core+Extra sono pronti e quasi tutto è aggiornato, solo poche ore o giorni al massimo dietro Arch Linux i686. I nostri TU stanno provando ad eseguire il port in Community proprio adesso.<br />
<br />
Il port è pronto per l'uso quotidiano in un ambiente desktop o server.<br />
<br />
==64 bit significa un grande aumento di velocità?==<br />
Per le applicazioni che utilizzano una CPU con registri a 64-bit (grandi database e simili), questo è vero nella maggior parte dei casi. Alcune applicazioni multimediali gireranno anche notevolmente più veloce. Se conosci un'applicazione che è notoriamente molto più veloce quando si utilizzano le estensioni SSE3 è possibile ricostruire il pacchetto da sé. Noi ''soltanto''compiliamo con il supporto SSE2 (da marzo=x86_64)e ottimizzazioni -O2.<br />
Per saperne di più leggi http://forums.gentoo.org/viewtopic.php?t=221045 oppure http://www.thejemreport.com/mambo/content/view/74/74/.<br />
<br />
For the rest of the system: It doesn't make any difference if the keyboard waits. <br />
<br />
For further details watch our [[Arch64_ToDoS]]. There you will find a list comparing arch32/arch64 package versions.<br />
<br />
For certain boot problems try these special kernel boot flags: http://www.x86-64.org/lists/discuss/msg03747.html (dead link)<br />
<br />
I have three 64-bit Archies running now, and they perform noticeably better under heavy load. It just seems to deliver more punch.<br />
<br />
==Attenzione quando aggiorni glibc da una versione inferiore alla 2.4!==<br />
E' importante se aggiorni glibc da una versione inferiore alla 2.4 che tu lo faccia a parte. Quindi dai prima pacman -Sy glibc e, se non ci sono problemi, dai pacman -Su. Altrimenti l'aggiornamento della libreria potrebbe fallire e sarai costretto ad usare pacman.static per correggere l'errore.<br />
<br />
==How can I file bugs?==<br />
Simply use Arch's flyspray but note x86_64 in the topic if you think it's a port-related problem!<br />
<br />
==Do you have a mailing list?==<br />
Yes, there is a generic [http://archlinux.org/mailman/listinfo/arch-ports mailing list about arch-ports].<br />
<br />
==What repos should I set up for pacman to use?==<br />
All repos are supported for the port.<br />
<br />
==How can I get the Arch64 PKGBUILDs?==<br />
We have '''''ABS''''' as Arch 32-bit. Recommended place to store is ''/var/abs''. ''abs'' fetches all CVS entries from archlinux.org tagged with CURRENT-64.<br />
<br />
==How can I build new Arch64 packages using existing 32-bit PKGBUILDs?==<br />
We have common PKGBUILDs with Arch32. You can get not-yet-ported 32-bit PKGBUILDs from CVS: http://www.archlinux.org/cvs/<br />
<br />
==How can I patch existing PKGBUILDs for use with Arch64?==<br />
We add to all ported packages this variable:<br />
arch=('i686' 'x86_64') <br />
Add small patches directly to the sources and md5sums area but use for complete different sources:<br />
[ "$CARCH" = "x86_64" ] && source=(${source[@]} 'other source')<br />
[ "$CARCH" = "x86_64" ] && md5sums=(${md5sums[@]} 'other md5sum')<br />
For any small fix use this in the build area:<br />
[ "$CARCH" = "x86_64" ] && (patch -Np0 -i ../foo_x86_64.patch || return 1)<br />
Or when you need more changes:<br />
if [ "$CARCH" = "x86_64" ]; then<br />
configure/patch/sed # for x86_64<br />
else configure/patch/sed # for i686<br />
fi<br />
For the devs:<br />
cvs commit -m "x86_64 updated/fixed or whatever"<br />
cvs tag -cFR CURRENT-64 foo-package-directory (even for extra, community, unstable and testing)<br />
<br />
==What will I miss in Arch64?==<br />
The following applications are known not to be 64-bit compatible:<br />
<br />
* no Java plugin shipped by Sun; KDE's Konqueror has its own native running 64-bit JavaPlugin built in! Best solution to browse JavaApplets these days. There is also a gcj-web-plugin (called gcjplugin in AUR) to use Java-Applets in Gecko browsers.<br />
* true x86_64 Flash support only in parts with GPL gnash or swfdec package from extra repo<br />
* no native Flash plugin shipped by Macromedia/Adobe - nspluginwrapper package from community allows use of 32-bit plugins but forces installation of lib32 packages - follow this guide on how to [[Install Flash on Arch64]]<br />
* Closed-source apps like Skype, Opera - where they don't provide 100% statically built binaries so 32-bit libs are still needed<br />
** '''Note:''' for the last opera 9.50 beta 1, there is a x86_64 port. So for the next release of opera, a native port to x86_64 is expected.<br />
* additional win32 codecs (... that nobody really needs)<br />
* packages that use x86 32-bit assembler code (some emulators like zsnes and syslinux)<br />
<br />
<br />
Almost everything else should be portable. If you miss any Arch32 package in our port and you know that it will compile on x86_64 (e.g. you have found it in another 64-bit distribution without using multilibs), just contact the devs.<br />
<br />
==Can I build 32-bit packages for i686 inside Arch64?==<br />
<br />
Yes. You need a working i686 chroot (installation with i686 iso "quickinstall" is recommended for the quick way to install it inside Arch64). Install "linux32" wrapper pkg from current to make the chroot behave like a real i686 system. Then use this script to login into the chroot environment as root:<br />
<br />
#!/bin/bash<br />
mount --bind /dev /path-to-your-chroot/dev<br />
mount --bind /dev/pts /path-to-your-chroot/dev/pts<br />
mount --bind /dev/shm /path-to-your-chroot/dev/shm<br />
mount -t proc none /path-to-your-chroot/proc<br />
mount -t sysfs none /path-to-your-chroot/sys<br />
linux32 chroot /path-to-your-chroot<br />
<br />
If you keep the sources on the x86_64 host system you can add<br />
"mount --bind /path-to-your-stored-sources /path-to-your-chroot/path-to-your-stored-sources" <br />
to share sources from host to chroot system for pkg building used in /etc/makepkg.conf.<br />
<br />
==Can I run 32-bit apps inside Arch64?==<br />
Yes! <br />
<br />
'''BUT: Our goal is to be the most bleeding-edge distribution around! 32-bit is old-fashioned. We want Arch64 to be modern and pure 64-bit. So we don't have a Multilib system. We won't take any package into the repos improving 32-bit compatibility. Maybe we will place them into the AUR or community repo.'''<br />
'''''Don't expect any support from the devs getting 32-bit apps running on Arch64!'''''<br />
<br />
Boot into Arch64, startx, open a term.<br />
xhost +local:<br />
su<br />
mount /dev/sda1 /mnt/arch32<br />
mount --bind /proc /mnt/arch32/proc<br />
chroot /mnt/arch32<br />
su your32bitusername<br />
/usr/bin/command-you want # or eg: /opt/mozilla/bin/firefox<br />
<br />
Some 32-bit apps (like OpenOffice) may require additional bindings. The following lines can be placed in rc.local to ensure you get all you need for the 32-bit apps (assuming /mnt/arch32 is mounted in fstab):<br />
mount --bind /dev /mnt/arch32/dev<br />
mount --bind /dev/pts /mnt/arch32/dev/pts<br />
mount --bind /dev/shm /mnt/arch32/dev/shm<br />
mount --bind /proc /mnt/arch32/proc<br />
mount --bind /proc/bus/usb /mnt/arch32/proc/bus/usb<br />
mount --bind /sys /mnt/arch32/sys<br />
mount --bind /tmp /mnt/arch32/tmp<br />
#comment the following line if you do not use the same home folder<br />
mount --bind /home /mnt/arch32/home<br />
You can then type in a term:<br />
xhost +localhost<br />
sudo chroot /mnt/arch32 su your32bitusername /opt/openoffice/program/soffice<br />
<br />
==Can I upgrade/switch my system from i686 to x86_64 without reinstalling?==<br />
No. However, you can start the system with the Arch64 install CD, mount the disk, delete anything you may want to keep that isn't a 32-bit binary (e.g: /home & /etc), and install.</div>Psykopearhttps://wiki.archlinux.org/index.php?title=64-bit_FAQ_(Italiano)&diff=3757364-bit FAQ (Italiano)2008-02-23T18:21:32Z<p>Psykopear: /* Attenzione quando aggiorni glibc da una versione minore della 2.4! */</p>
<hr />
<div>[[Category:Arch64 (Italiano)]]<br />
[[Category:FAQs (Italiano)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Arch64 FAQ}}<br />
{{i18n_entry|Español|Arch64 FAQ (Español)}}<br />
{{i18n_entry|Italiano|Arch64 FAQ (Italiano)}}<br />
{{i18n_entry|简体中文|Arch64 问答}}<br />
{{i18n_links_end}}<br />
<br />
Di seguito è riportato un elenco di domande frequenti su Arch64. <br />
<br />
==Come faccio a installare Arch64?==<br />
Basta utilizzare il nostro [http://www.archlinux.org/download/ CD di installazione ufficiale].<br />
<br />
==A che punto è il port? Avrò tutti i pacchetti del mio ambiente Arch32?==<br />
I repository Core+Extra sono pronti e quasi tutto è aggiornato, solo poche ore o giorni al massimo dietro Arch Linux i686. I nostri TU stanno provando ad eseguire il port in Community proprio adesso.<br />
<br />
Il port è pronto per l'uso quotidiano in un ambiente desktop o server.<br />
<br />
==64 bit significa un grande aumento di velocità?==<br />
Per le applicazioni che utilizzano una CPU con registri a 64-bit (grandi database e simili), questo è vero nella maggior parte dei casi. Alcune applicazioni multimediali gireranno anche notevolmente più veloce. Se conosci un'applicazione che è notoriamente molto più veloce quando si utilizzano le estensioni SSE3 è possibile ricostruire il pacchetto da sé. Noi ''soltanto''compiliamo con il supporto SSE2 (da marzo=x86_64)e ottimizzazioni -O2.<br />
Per saperne di più leggi http://forums.gentoo.org/viewtopic.php?t=221045 oppure http://www.thejemreport.com/mambo/content/view/74/74/.<br />
<br />
For the rest of the system: It doesn't make any difference if the keyboard waits. <br />
<br />
For further details watch our [[Arch64_ToDoS]]. There you will find a list comparing arch32/arch64 package versions.<br />
<br />
For certain boot problems try these special kernel boot flags: http://www.x86-64.org/lists/discuss/msg03747.html (dead link)<br />
<br />
I have three 64-bit Archies running now, and they perform noticeably better under heavy load. It just seems to deliver more punch.<br />
<br />
==Attenzione quando aggiorni glibc da una versione minore della 2.4!==<br />
E' importante se aggiorni glibc da una versione inferiore alla 2.4 che tu lo faccia a parte. Quindi dai prima pacman -Sy glibc e, se non ci sono problemi, dai pacman -Su. Altrimenti l'aggiornamento della libreria potrebbe fallire e sarai costretto ad usare pacman.static per correggere l'errore.<br />
<br />
==How can I file bugs?==<br />
Simply use Arch's flyspray but note x86_64 in the topic if you think it's a port-related problem!<br />
<br />
==Do you have a mailing list?==<br />
Yes, there is a generic [http://archlinux.org/mailman/listinfo/arch-ports mailing list about arch-ports].<br />
<br />
==What repos should I set up for pacman to use?==<br />
All repos are supported for the port.<br />
<br />
==How can I get the Arch64 PKGBUILDs?==<br />
We have '''''ABS''''' as Arch 32-bit. Recommended place to store is ''/var/abs''. ''abs'' fetches all CVS entries from archlinux.org tagged with CURRENT-64.<br />
<br />
==How can I build new Arch64 packages using existing 32-bit PKGBUILDs?==<br />
We have common PKGBUILDs with Arch32. You can get not-yet-ported 32-bit PKGBUILDs from CVS: http://www.archlinux.org/cvs/<br />
<br />
==How can I patch existing PKGBUILDs for use with Arch64?==<br />
We add to all ported packages this variable:<br />
arch=('i686' 'x86_64') <br />
Add small patches directly to the sources and md5sums area but use for complete different sources:<br />
[ "$CARCH" = "x86_64" ] && source=(${source[@]} 'other source')<br />
[ "$CARCH" = "x86_64" ] && md5sums=(${md5sums[@]} 'other md5sum')<br />
For any small fix use this in the build area:<br />
[ "$CARCH" = "x86_64" ] && (patch -Np0 -i ../foo_x86_64.patch || return 1)<br />
Or when you need more changes:<br />
if [ "$CARCH" = "x86_64" ]; then<br />
configure/patch/sed # for x86_64<br />
else configure/patch/sed # for i686<br />
fi<br />
For the devs:<br />
cvs commit -m "x86_64 updated/fixed or whatever"<br />
cvs tag -cFR CURRENT-64 foo-package-directory (even for extra, community, unstable and testing)<br />
<br />
==What will I miss in Arch64?==<br />
The following applications are known not to be 64-bit compatible:<br />
<br />
* no Java plugin shipped by Sun; KDE's Konqueror has its own native running 64-bit JavaPlugin built in! Best solution to browse JavaApplets these days. There is also a gcj-web-plugin (called gcjplugin in AUR) to use Java-Applets in Gecko browsers.<br />
* true x86_64 Flash support only in parts with GPL gnash or swfdec package from extra repo<br />
* no native Flash plugin shipped by Macromedia/Adobe - nspluginwrapper package from community allows use of 32-bit plugins but forces installation of lib32 packages - follow this guide on how to [[Install Flash on Arch64]]<br />
* Closed-source apps like Skype, Opera - where they don't provide 100% statically built binaries so 32-bit libs are still needed<br />
** '''Note:''' for the last opera 9.50 beta 1, there is a x86_64 port. So for the next release of opera, a native port to x86_64 is expected.<br />
* additional win32 codecs (... that nobody really needs)<br />
* packages that use x86 32-bit assembler code (some emulators like zsnes and syslinux)<br />
<br />
<br />
Almost everything else should be portable. If you miss any Arch32 package in our port and you know that it will compile on x86_64 (e.g. you have found it in another 64-bit distribution without using multilibs), just contact the devs.<br />
<br />
==Can I build 32-bit packages for i686 inside Arch64?==<br />
<br />
Yes. You need a working i686 chroot (installation with i686 iso "quickinstall" is recommended for the quick way to install it inside Arch64). Install "linux32" wrapper pkg from current to make the chroot behave like a real i686 system. Then use this script to login into the chroot environment as root:<br />
<br />
#!/bin/bash<br />
mount --bind /dev /path-to-your-chroot/dev<br />
mount --bind /dev/pts /path-to-your-chroot/dev/pts<br />
mount --bind /dev/shm /path-to-your-chroot/dev/shm<br />
mount -t proc none /path-to-your-chroot/proc<br />
mount -t sysfs none /path-to-your-chroot/sys<br />
linux32 chroot /path-to-your-chroot<br />
<br />
If you keep the sources on the x86_64 host system you can add<br />
"mount --bind /path-to-your-stored-sources /path-to-your-chroot/path-to-your-stored-sources" <br />
to share sources from host to chroot system for pkg building used in /etc/makepkg.conf.<br />
<br />
==Can I run 32-bit apps inside Arch64?==<br />
Yes! <br />
<br />
'''BUT: Our goal is to be the most bleeding-edge distribution around! 32-bit is old-fashioned. We want Arch64 to be modern and pure 64-bit. So we don't have a Multilib system. We won't take any package into the repos improving 32-bit compatibility. Maybe we will place them into the AUR or community repo.'''<br />
'''''Don't expect any support from the devs getting 32-bit apps running on Arch64!'''''<br />
<br />
Boot into Arch64, startx, open a term.<br />
xhost +local:<br />
su<br />
mount /dev/sda1 /mnt/arch32<br />
mount --bind /proc /mnt/arch32/proc<br />
chroot /mnt/arch32<br />
su your32bitusername<br />
/usr/bin/command-you want # or eg: /opt/mozilla/bin/firefox<br />
<br />
Some 32-bit apps (like OpenOffice) may require additional bindings. The following lines can be placed in rc.local to ensure you get all you need for the 32-bit apps (assuming /mnt/arch32 is mounted in fstab):<br />
mount --bind /dev /mnt/arch32/dev<br />
mount --bind /dev/pts /mnt/arch32/dev/pts<br />
mount --bind /dev/shm /mnt/arch32/dev/shm<br />
mount --bind /proc /mnt/arch32/proc<br />
mount --bind /proc/bus/usb /mnt/arch32/proc/bus/usb<br />
mount --bind /sys /mnt/arch32/sys<br />
mount --bind /tmp /mnt/arch32/tmp<br />
#comment the following line if you do not use the same home folder<br />
mount --bind /home /mnt/arch32/home<br />
You can then type in a term:<br />
xhost +localhost<br />
sudo chroot /mnt/arch32 su your32bitusername /opt/openoffice/program/soffice<br />
<br />
==Can I upgrade/switch my system from i686 to x86_64 without reinstalling?==<br />
No. However, you can start the system with the Arch64 install CD, mount the disk, delete anything you may want to keep that isn't a 32-bit binary (e.g: /home & /etc), and install.</div>Psykopear