https://wiki.archlinux.org/api.php?action=feedcontributions&user=Zaggynl&feedformat=atom
ArchWiki - User contributions [en]
2024-03-28T11:58:28Z
User contributions
MediaWiki 1.41.0
https://wiki.archlinux.org/index.php?title=Browser_plugins&diff=75111
Browser plugins
2009-09-04T07:25:31Z
<p>Zaggynl: /* Performance */</p>
<hr />
<div>{{Message_box|<br />
id = out of date|<br />
backgroundcolor = beige|<br />
signalcolor = beige|<br />
signal = [[Image:Tango-dialog-warning.png]]|<br />
heading = This article is out of date.|<br />
message = It may contain old, confusing and wrong information.}}<br />
<br />
[[Category:Internet and Email (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Flash_and_Adobe_Acrobat_browser_plugins}}<br />
{{i18n_entry|简体中文|Flash 和 Adobe Acrobat 浏览器插件}}<br />
{{i18n_entry|Español|Plugins de Flash y Adobe Acrobat para el browser (Español)}}<br />
{{i18n_entry|Français|Plugins Flash et Adobe Acrobat pour le navigateur (Français)}}<br />
{{i18n_entry|Türkçe|Flash ve Adobe Acrobat Eklentileri}}<br />
{{i18n_links_end}}<br />
<br />
{{Note| Because web browser plugins are standardized take a look at [[Firefox#Useful_plugins|The Firefox Page]] on how to install them}}<br />
<br />
= Updated Information for new installations! Use the information in this section =<br />
==Flash and Java plugins==<br />
To install Flash Player and Java, run<br />
# pacman -S flashplugin jre<br />
That should work!<br />
<br />
'''''Note:''' You may need to install ttf-ms-fonts (<code>pacman -S ttf-ms-fonts</code>) for flashplayer to render text properly.''<br />
<br />
'''''Note for Arch64:''' j2re will still not work for your browser - at this point in time (Dec 9 2008), there is still no support in jre-64 for java applets... See http://java.com/en/download/manual.jsp#note''<br />
<br />
=== Troubleshooting ===<br />
If plugins don't work at all in Firefox check the permissions of /usr/lib/mozilla. In my case only root was allowed to read files.<br />
<br />
$ cd /usr/lib/mozilla<br />
cd: permission denied: /usr/lib/mozilla<br />
<br />
# chmod 755 /usr/lib/mozilla<br />
# chmod 755 /usr/lib/mozilla/extensions<br />
<br />
You will also have to logout and back into your user before flash will work.<br />
<br />
=== Performance ===<br />
<br />
Adobe's flashplugin has some serious performance issus (June 2009) especially when cpu frequency scaling is used. (there seems to be a policy not to use the whole cpu workload, so the frequency scaling govenor soes not clock the cpu any higher.) To work around this issue the folowing can be applied: http://wiki.archlinux.org/index.php/Cpufreq Section: Changing the Ondemand Governor's threshold<br />
<br />
If you have an ATI card, try disabling AIGLX: <br /><br />
sudo nano /etc/X11/xorg.conf<br /><br />
Option "AIGLX" "false"<br />
<br />
=== Configuration ===<br />
To change your general plugin preferences (especially the privacy settings), you have to go to the Macromedia website. There a flash animation will give you access to your local settings.<br />
<br />
[http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager.html Macromedia Flash Settings]<br />
<br />
== Adobe Reader ==<br />
Due to licensing restrictions, Adobe Reader cannot be distributed from any of the normal Arch repos. There is a version available on the AUR [http://aur.archlinux.org/packages.php?ID=16980 here].<br />
<br />
There are [http://aur.archlinux.org/packages.php?O=0&K=acroread-&do_Search=Go localisations] available in many languages, check the AUR for your language.<br />
<br />
Due to a missing PATH you have to run:<br />
$ ln -s /usr/share/Adobe/Reader8/bin/acroread /usr/bin<br />
Please note that no matter how many votes it receives, this package will never be included in the community repo. See comment by Snowman [http://aur.archlinux.org/packages.php?ID=16980 here].<br />
<br />
<br />
= Old information for reference on old installations... Or whatever (OUTDATED) =<br />
<br />
==Using Mozilla==<br />
<br />
===For Adobe Acrobat Reader plugin===<br />
After installing acroread:<br />
# ln -s /opt/mozilla-plugins/nppdf.so /opt/mozilla/lib/mozilla/plugins/<br />
<br />
===For Shockwave Flash===<br />
# pacman -S flashplugin<br />
# ln -s /opt/mozilla-plugins/flashplayer.xpt /opt/mozilla/lib/mozilla/plugins/<br />
# ln -s /opt/mozilla-plugins/libflashplayer.so /opt/mozilla/lib/mozilla/plugins/<br />
<br />
Restart Mozilla if it was running.<br />
<br />
'''Note:''' Flash is known to have poor support for GNU/Linux.<br />
Flash Player 7 has problems regarding sound output with a lot of people.<br />
Flash versions older than 10 have bad PulseAudio support.<br />
<br />
There is a GNU project going on (Gnash) that should be an open source alternative for showing Flash.<br />
As of 17 may 2006 it is still in development, but it is already able to run a lot of Flash 7 content.<br />
<br />
==Using Mozilla Firefox==<br />
<br />
===For Adobe Acrobat Reader plugin===<br />
After installing acroread:<br />
# ln -s /opt/mozilla-plugins/nppdf.so /opt/mozilla/lib/firefox/plugins/<br />
<br />
'''Note:''' the step above may be unnecessary.<br />
<br />
===For Shockwave Flash===<br />
# pacman -S flashplugin ttf-ms-fonts<br />
# ln -s /opt/mozilla-plugins/flashplayer.xpt /opt/mozilla/lib/firefox/plugins/<br />
# ln -s /opt/mozilla-plugins/libflashplayer.so /opt/mozilla/lib/firefox/plugins/<br />
<br />
'''Note:''' Flash is known to have poor support for GNU/Linux.<br />
Flash Player 7 has problems regarding sound output with a lot of people.<br />
Flash versions older than 10 have bad PulseAudio support.<br />
<br />
'''Note:''' Also works with Firefox3; replace <code>/opt/mozilla/lib/firefox/plugins</code> with <code>/opt/mozilla/lib/firefox-3.0/plugins</code><br />
<br />
There is a GNU project going on (Gnash) that should be an open source alternative for showing Flash.<br />
As of 17 may 2006 it is still in development, but it is already able to run a lot of Flash 7 content.<br />
<br />
====Alternate way====<br />
Visit http://www.adobe.com/products/flashplayer/ and download the Adobe Flash player .tar.gz file. Unpack it and execute the flashplayer-installer as root.<br />
# ./flashplayer-installer<br />
<br />
The script will ask for location of the browser. For Firefox, enter<br />
/usr/lib/firefox<br />
<br />
Note that the target directory must contain a directory called plugins in order for the offical installer to work. An invalid install path error can be solved by executing<br />
mkdir /usr/lib/firefox/plugins<br />
<br />
Restart Firefox. Repeat for any browsers installed.<br />
<br />
===For Java Plugin===<br />
# pacman -S jre<br />
# ln -s /opt/java/jre/plugin/i386/ns7-gcc29/libjavaplugin_oji.so /opt/mozilla/lib/firefox/plugins/<br />
<br />
(For me it's: <code>ln -s /opt/java/jre/plugin/i386/ns7/libjavaplugin_oji.so /opt/mozilla/lib/firefox/plugins/</code>, note the missing gcc29)<br />
<br />
Use the Tab key to navigate easier through the directories.<br />
<br />
==Fixing Flash in Konqueror==<br />
# pacman -S kmplayer<br />
<br />
Run kmplayer to make sure it creates a config file and then close kmplayer. Open "~/.kde/share/config/kmplayerrc" (or "~/.kde4/share/config/kmplayerrc" if you use KDE4's konqueror) with a text editor of your choice and add this to the ending:<br />
<br />
[application/x-shockwave-flash]<br />
player=npp<br />
plugin=/usr/lib/mozilla/plugins/libflashplayer.so<br />
<br />
Check the plugin line if it is correct by doing:<br />
$ slocate libflashplayer.so<br />
<br />
If it is not correct then change it to the correct filepath. Open Konqueror and go to Settings > Configure Konqueror > File Associations, navigate to "application/x-shockwave-flash" and click on the "Embedding" tab and click "Add.." and select "Embedded MPlayer for KDE" and click "Ok". Make sure "Embedded MPlayer for KDE" is on the top. Click "Ok". Now it should work, if it doesn't you might have to restart konqueror and/or KDE.<br />
<br />
Reference: http://mikearthur.co.uk/?p=171<br />
<br />
----<br />
<br />
<br />
=For Arch64 users=<br />
[[Install 32bit Flash on a 64bit System]]</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Browser_plugins&diff=75110
Browser plugins
2009-09-04T07:25:01Z
<p>Zaggynl: </p>
<hr />
<div>{{Message_box|<br />
id = out of date|<br />
backgroundcolor = beige|<br />
signalcolor = beige|<br />
signal = [[Image:Tango-dialog-warning.png]]|<br />
heading = This article is out of date.|<br />
message = It may contain old, confusing and wrong information.}}<br />
<br />
[[Category:Internet and Email (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Flash_and_Adobe_Acrobat_browser_plugins}}<br />
{{i18n_entry|简体中文|Flash 和 Adobe Acrobat 浏览器插件}}<br />
{{i18n_entry|Español|Plugins de Flash y Adobe Acrobat para el browser (Español)}}<br />
{{i18n_entry|Français|Plugins Flash et Adobe Acrobat pour le navigateur (Français)}}<br />
{{i18n_entry|Türkçe|Flash ve Adobe Acrobat Eklentileri}}<br />
{{i18n_links_end}}<br />
<br />
{{Note| Because web browser plugins are standardized take a look at [[Firefox#Useful_plugins|The Firefox Page]] on how to install them}}<br />
<br />
= Updated Information for new installations! Use the information in this section =<br />
==Flash and Java plugins==<br />
To install Flash Player and Java, run<br />
# pacman -S flashplugin jre<br />
That should work!<br />
<br />
'''''Note:''' You may need to install ttf-ms-fonts (<code>pacman -S ttf-ms-fonts</code>) for flashplayer to render text properly.''<br />
<br />
'''''Note for Arch64:''' j2re will still not work for your browser - at this point in time (Dec 9 2008), there is still no support in jre-64 for java applets... See http://java.com/en/download/manual.jsp#note''<br />
<br />
=== Troubleshooting ===<br />
If plugins don't work at all in Firefox check the permissions of /usr/lib/mozilla. In my case only root was allowed to read files.<br />
<br />
$ cd /usr/lib/mozilla<br />
cd: permission denied: /usr/lib/mozilla<br />
<br />
# chmod 755 /usr/lib/mozilla<br />
# chmod 755 /usr/lib/mozilla/extensions<br />
<br />
You will also have to logout and back into your user before flash will work.<br />
<br />
=== Performance ===<br />
<br />
Adobe's flashplugin has some serious performance issus (June 2009) especially when cpu frequency scaling is used. (there seems to be a policy not to use the whole cpu workload, so the frequency scaling govenor soes not clock the cpu any higher.) To work around this issue the folowing can be applied: http://wiki.archlinux.org/index.php/Cpufreq Section: Changing the Ondemand Governor's threshold<br />
<br />
If you have an ATI card, try disabling AIGLX:<br />
sudo nano /etc/X11/xorg.conf<br />
Option "AIGLX" "false"<br />
<br />
<br />
<br />
<br />
=== Configuration ===<br />
To change your general plugin preferences (especially the privacy settings), you have to go to the Macromedia website. There a flash animation will give you access to your local settings.<br />
<br />
[http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager.html Macromedia Flash Settings]<br />
<br />
== Adobe Reader ==<br />
Due to licensing restrictions, Adobe Reader cannot be distributed from any of the normal Arch repos. There is a version available on the AUR [http://aur.archlinux.org/packages.php?ID=16980 here].<br />
<br />
There are [http://aur.archlinux.org/packages.php?O=0&K=acroread-&do_Search=Go localisations] available in many languages, check the AUR for your language.<br />
<br />
Due to a missing PATH you have to run:<br />
$ ln -s /usr/share/Adobe/Reader8/bin/acroread /usr/bin<br />
Please note that no matter how many votes it receives, this package will never be included in the community repo. See comment by Snowman [http://aur.archlinux.org/packages.php?ID=16980 here].<br />
<br />
<br />
= Old information for reference on old installations... Or whatever (OUTDATED) =<br />
<br />
==Using Mozilla==<br />
<br />
===For Adobe Acrobat Reader plugin===<br />
After installing acroread:<br />
# ln -s /opt/mozilla-plugins/nppdf.so /opt/mozilla/lib/mozilla/plugins/<br />
<br />
===For Shockwave Flash===<br />
# pacman -S flashplugin<br />
# ln -s /opt/mozilla-plugins/flashplayer.xpt /opt/mozilla/lib/mozilla/plugins/<br />
# ln -s /opt/mozilla-plugins/libflashplayer.so /opt/mozilla/lib/mozilla/plugins/<br />
<br />
Restart Mozilla if it was running.<br />
<br />
'''Note:''' Flash is known to have poor support for GNU/Linux.<br />
Flash Player 7 has problems regarding sound output with a lot of people.<br />
Flash versions older than 10 have bad PulseAudio support.<br />
<br />
There is a GNU project going on (Gnash) that should be an open source alternative for showing Flash.<br />
As of 17 may 2006 it is still in development, but it is already able to run a lot of Flash 7 content.<br />
<br />
==Using Mozilla Firefox==<br />
<br />
===For Adobe Acrobat Reader plugin===<br />
After installing acroread:<br />
# ln -s /opt/mozilla-plugins/nppdf.so /opt/mozilla/lib/firefox/plugins/<br />
<br />
'''Note:''' the step above may be unnecessary.<br />
<br />
===For Shockwave Flash===<br />
# pacman -S flashplugin ttf-ms-fonts<br />
# ln -s /opt/mozilla-plugins/flashplayer.xpt /opt/mozilla/lib/firefox/plugins/<br />
# ln -s /opt/mozilla-plugins/libflashplayer.so /opt/mozilla/lib/firefox/plugins/<br />
<br />
'''Note:''' Flash is known to have poor support for GNU/Linux.<br />
Flash Player 7 has problems regarding sound output with a lot of people.<br />
Flash versions older than 10 have bad PulseAudio support.<br />
<br />
'''Note:''' Also works with Firefox3; replace <code>/opt/mozilla/lib/firefox/plugins</code> with <code>/opt/mozilla/lib/firefox-3.0/plugins</code><br />
<br />
There is a GNU project going on (Gnash) that should be an open source alternative for showing Flash.<br />
As of 17 may 2006 it is still in development, but it is already able to run a lot of Flash 7 content.<br />
<br />
====Alternate way====<br />
Visit http://www.adobe.com/products/flashplayer/ and download the Adobe Flash player .tar.gz file. Unpack it and execute the flashplayer-installer as root.<br />
# ./flashplayer-installer<br />
<br />
The script will ask for location of the browser. For Firefox, enter<br />
/usr/lib/firefox<br />
<br />
Note that the target directory must contain a directory called plugins in order for the offical installer to work. An invalid install path error can be solved by executing<br />
mkdir /usr/lib/firefox/plugins<br />
<br />
Restart Firefox. Repeat for any browsers installed.<br />
<br />
===For Java Plugin===<br />
# pacman -S jre<br />
# ln -s /opt/java/jre/plugin/i386/ns7-gcc29/libjavaplugin_oji.so /opt/mozilla/lib/firefox/plugins/<br />
<br />
(For me it's: <code>ln -s /opt/java/jre/plugin/i386/ns7/libjavaplugin_oji.so /opt/mozilla/lib/firefox/plugins/</code>, note the missing gcc29)<br />
<br />
Use the Tab key to navigate easier through the directories.<br />
<br />
==Fixing Flash in Konqueror==<br />
# pacman -S kmplayer<br />
<br />
Run kmplayer to make sure it creates a config file and then close kmplayer. Open "~/.kde/share/config/kmplayerrc" (or "~/.kde4/share/config/kmplayerrc" if you use KDE4's konqueror) with a text editor of your choice and add this to the ending:<br />
<br />
[application/x-shockwave-flash]<br />
player=npp<br />
plugin=/usr/lib/mozilla/plugins/libflashplayer.so<br />
<br />
Check the plugin line if it is correct by doing:<br />
$ slocate libflashplayer.so<br />
<br />
If it is not correct then change it to the correct filepath. Open Konqueror and go to Settings > Configure Konqueror > File Associations, navigate to "application/x-shockwave-flash" and click on the "Embedding" tab and click "Add.." and select "Embedded MPlayer for KDE" and click "Ok". Make sure "Embedded MPlayer for KDE" is on the top. Click "Ok". Now it should work, if it doesn't you might have to restart konqueror and/or KDE.<br />
<br />
Reference: http://mikearthur.co.uk/?p=171<br />
<br />
----<br />
<br />
<br />
=For Arch64 users=<br />
[[Install 32bit Flash on a 64bit System]]</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Newcomers_Guide&diff=58750
Newcomers Guide
2009-01-21T16:00:39Z
<p>Zaggynl: </p>
<hr />
<div>Oops, I've been editing the wrong page, sorry.<br />
Here's the correct version of this page: [[http://wiki.archlinux.org/index.php?title=Beginners_Guide&oldid=58738]]<br />
<br />
--zaggynl</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Newcomers_Guide&diff=58749
Newcomers Guide
2009-01-21T15:57:17Z
<p>Zaggynl: Removing all content from page</p>
<hr />
<div></div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Newcomers_Guide&diff=58748
Newcomers Guide
2009-01-21T15:54:21Z
<p>Zaggynl: </p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{Article summary start}}<br />
{{Article summary text|General installation documentation for the Arch Linux distribution.}}<br />
{{Article summary heading|Available Languages}}<br />
{{i18n_entry|English|Official Arch Linux Install Guide}}<br />
{{i18n_entry|&#31616;&#20307;&#20013;&#25991;|Arch Linux &#23448;&#26041;&#23433;&#35013;&#25351;&#21335;}}<br />
{{i18n_entry|&#27491;&#39636;&#20013;&#25991;|Arch Linux &#23448;&#26041;&#23433;&#35037;&#25351;&#21335;}}<br />
{{i18n_entry|&#268;esky|Oficiální instala&#269;ní p&#345;íru&#269;ka (&#268;esky)}}<br />
{{i18n_entry|&#1056;&#1091;&#1089;&#1089;&#1082;&#1080;&#1081;|&#1056;&#1091;&#1082;&#1086;&#1074;&#1086;&#1076;&#1089;&#1090;&#1074;&#1086; &#1087;&#1086; &#1091;&#1089;&#1090;&#1072;&#1085;&#1086;&#1074;&#1082;&#1077;}}<br />
{{i18n_entry|Español|Guía oficial de Instalación}}<br />
{{i18n_entry|Italiano|Official Arch Linux Install Guide (Italiano)}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|Beginners Guide}} (If you are new to Arch)<br />
{{Article summary end}}<br />
<br />
<br />
==Introduction==<br />
<br />
===What is Arch Linux?===<br />
<br />
Arch Linux is an independently developed i686/x86-64-optimized GNU/Linux distribution. Development is focused on a balance of simplicity, elegance, code-correctness and bleeding edge software.<br />
<br />
The Arch system and binary packages are compiled for i686 or x86-64 processors. Its lightweight and simple design makes it easy to extend and mold into whatever kind of system you're building.<br />
<br />
===License===<br />
<br />
Arch Linux, pacman, documentation, and scripts are copyright<br />
©2002-2007 by Judd Vinet, ©2007-2008 by Aaron Griffin and are licensed under the GNU General Public License Version 2.<br />
<br />
==Installing Arch Linux==<br />
<br />
===Pre-Installation===<br />
<br />
Arch Linux is optimized for the i686 processor and therefore will not<br />
run on any lower or incompatible generations of x86 CPUs<br />
(i386,i486,i586). A Pentium II or AMD Athlon processor or higher is<br />
required. Modern VIA C3 processors are also supported. x86-64 architectures are also officially supported.<br />
<br />
There is a community-driven project that provides packages for i586<br />
and ppc. See this site for more information.<br />
<br />
Before installing Arch Linux, you should decide which installation<br />
method you would like to use. Arch Linux provides two different<br />
bootable ISO images for a CD-ROM installation. Installing Arch from a USB stick or from within another already installed OS is also supported.<br />
<br />
As the preferred method of installation is the flexible CD-ROM based<br />
installation, we offer you two variants of the installation medium<br />
which only differ in terms of supplied packages. You can instruct the<br />
installer to obtain the packages via FTP using any of these images,<br />
and all images can also be used as fully functional live cds.<br />
<br />
* The core iso (~300MB) is a live environment which contains a snapshot of the entire /core repository. Packages are divided into 4 categories: BASE, SUPPORT, DEVEL and LIB. RAID/LVM are fully supported; all necessary packages are included within /core. Installing from a medium created with this image results in a completely functional GNU/Linux system, without any frills, expecting to be used from the command line; the Linux kernel, GNU toolchain and a few extra modules and libraries. This image is ideally suited for those who have a rather slow or nonexistent internet connection on the candidate machine, making an FTP install unfeasible. The name of the iso will be "archlinux-i686-2008.xx-x.core.iso", according to your architecture<br />
* The FTP iso (~175MB) is a live environment, containing no packages at all, but rather pulls in all software over your internet connection. If you have access to a fast and easily setup internet connection, this method may be preferred, since the completed system will be completely up-to-date, without requiring further upgrades from the package versions included on the Core CD. Of course all packages you choose to install have to be downloaded from somewhere, but at least you don't have to update the system directly after installation, saving yourself some hassle. If your network connection is cheap and fast, choose this image. <br />
{{Box Note | When choosing a pacman mirror during installation, keep in mind that archlinux.org is throttled to 50Kb/s.}}<br />
<br />
If you do not have a CD-ROM drive attached to your computer, you may refer to [[Install_from_USB_stick | this guide]] to install Arch Linux using a USB stick. If you do not have a USB stick, there are [[Hard_Disk_Installation | instructions]] for installing from a hard disk partition, such as a swap partition. If you want to use an existing distribution to install Arch Linux, please follow this [[Install_From_Existing_Linux | guide]].<br />
<br />
You can also purchase a cd online from OSDisc, shipping nearly<br />
world-wide.<br />
<br />
Using a dialup PPP connection to gain access to the internet during<br />
the install process is now supported. ppp utilities, rp-pppoe<br />
and the ISDN userspace utilities are included in the installation<br />
media.<br />
<br />
Since version 2007.08, isos are true live systems and run like any installed arch system.<br />
<br />
Some highlights: <br />
* pacman is included, to allow installation of any other needed packages for install environment.<br />
* complete /etc/rc.d/ and /etc/rc.conf support<br />
* complete Arch network support, including ssh,telnet and portmap services<br />
* custom config files support: any media with /config directory and files can be copied to /etc/ install environment<br />
* loading packages as addons during boot: any media with /packages directory including pacman packages can be installed during bootup.<br />
* '''links''' and '''naim''' included to be able to communicate over the internet.<br />
* complete kexec support<br />
<br />
If, during the installation process, you find you require a more verbose guide or explanation, you may also find the Arch Linux [[Beginners Guide]] helpful. <br />
<br />
What You Will Need<br />
<br />
* a working knowledge of GNU/Linux and the candidate machine's hardware<br />
* Arch Linux installation media (see the mirror list)<br />
* an i686 or x86-64 processor (PPro, Pentium 2 or higher, Athlon/Duron, etc. Note that AMD K6, Transmeta Crusoe, CyrixIII, and VIA-C3 are NOT supported.)<br />
* 160 MB RAM<br />
* some time to kill<br />
<br />
===Acquiring Arch Linux===<br />
<br />
You can download Arch Linux from any of the Arch Linux [http://www.archlinux.org/download/ mirrors]. Just follow the links into the "iso" directory and choose the version you wish to install. In general, you are advised to download the latest version as this helps avoid any difficulties during your initial update.<br />
<br />
===Preparing Installation Media===<br />
<br />
*Download <mirror>/iso/<your_architecture>/archlinux-<version>.iso (path relative to mirror root)<br />
*Download <mirror>/iso/<your_architecture>/md5sum-<version>.txt<br />
*Verify the integrity of the .iso image using md5sum:<br />
md5sum archlinux-<version>.iso<br />
*Burn the .iso image to a blank CD-R (this step varies depending on the OS/software you're using). If you want to download the core, ftp or a beta ISO instead, use the appropriate filename, ie: arch-0.8-core.iso instead of arch-0.8.iso, likewise for the md5sum.<br />
*Write down all your network settings so you can enter them into setup later, if you want to install via FTP:<br />
**IP Address<br />
**Subnet Mask<br />
**Gateway<br />
**Ethernet Module for your network card (eg.: eepro100, 8139too, ne2k-pci, etc.)<br />
<br />
===Using the CD-ROM===<br />
If you are familiar with the boot process, you may skip this <br />
explanation and continue with [[#Common Installation Procedure | Common Installation Procedure]], which outlines <br />
the actual process of installing Arch Linux.<br />
<br />
Reboot your computer with the Arch Linux Installation CD in the drive.<br />
Make sure your BIOS is configured to boot from your CD-ROM.<br />
Refer to your motherboard manual or system manufacturer documentation for<br />
details.<br />
<br />
At the end of the boot procedure, you shall be dropped into a root<br />
shell. At this point you are ready to commence the actual<br />
installation.<br />
<br />
===Common Installation Procedure===<br />
<br />
Installation Steps:<br />
<br />
#Loading a non-US Keymap<br />
#Running Setup<br />
#Configure Network (FTP Install only)<br />
#Prepare Hard Drive<br />
##Auto-Prepare<br />
##Partition Hard Drives<br />
##Set Filesystem Mountpoints<br />
#Select Packages<br />
#Install Packages<br />
#Configure System<br />
#Install Bootloader<br />
#Exit Install<br />
<br />
Using the available shell tools, experienced users are also able to<br />
prepare the hard drive or any devices needed for the installation<br />
before starting the installer. You may simply skip this paragraph if<br />
you don't see any immediate need for further manual interaction. Note<br />
that the Arch Linux installation media also contains a /arch/quickinst<br />
script for experienced users. This script installs the "base" set of<br />
packages to a user-specified destination directory. If you are doing<br />
an exotic install with fun things like RAID and LVM, or do not want to<br />
use the installer at all, you will probably want to use the quickinst<br />
script. All the cool kids are doing it.<br />
<br />
====Login and Loading a non-US Keymap====<br />
<br />
Login as 'root'. If you have a non-US keyboard layout do:<br />
km<br />
at the prompt.<br />
<br />
====Running Setup====<br />
<br />
Begin the installer script:<br />
/arch/setup<br />
After an informational message you will be prompted for the installation method<br />
of your choice. If you have a fast internet connection, you might<br />
prefer the FTP installation to ensure you get the latest packages<br />
instead of using the potentially outdated CD contents. <br />
<br />
When navigating the setup script, make sure to select DONE from<br />
the submenus after performing each step. This saves any settings you<br />
make in preparation for the next step. Further, avoid arbitrary steps<br />
throughout the installation process as this can also confuse the<br />
installer.<br />
<br />
It's actually rather easy to set up your own FTP package mirror or<br />
create your own bootable installation CD with the packages you need,<br />
making the task of installing several instances of Arch Linux across<br />
multiple machines rather simple, while at the same time saving a lot<br />
of mirror bandwidth. Make your life and ours easier, and look into<br />
these alternatives!<br />
<br />
When choosing a CD-ROM or OTHER SOURCE install you will only be able<br />
to install packages contained on the CD, which may be quite old, or<br />
packages stored on a medium you were able to mount (DVD, USB stick or<br />
similar) somewhere in the filesystem tree manually. Of course, it has<br />
the advantage of not needing an internet connection, and is therefore<br />
the recommended choice for dialup users or those unable or unwilling to download the entire package set via ftp.<br />
<br />
Next, you will be presented with the installer menu, listing the necessary steps in the order in which they should be completed.<br />
<br />
Virtual consoles 1-6 are active in the live environment. At any point in the install process, you can switch to your 5th virtual console (ALT-F5) to view the shell output from installer script. Use (ALT-F1) to get back to your first console where<br />
the installer is running.<br />
<br />
====Configure Network (FTP Install only)====<br />
<br />
Configure Network will allow you to install and configure your network<br />
device.<br />
<br />
A list of all currently available network devices is presented to you.<br />
If no ethernet device is available, load the necessary modules manually from another virtual console. Alternatively,<br />
you may probe for a network module on the following screen by selecting the Probe command. <br />
<br />
When the correct module is loaded, your network card will be<br />
listed. Select the ethernet device you wish to configure<br />
and you will be given the option to configure your network with DHCP.<br />
If you're connected to a DHCP server, hit YES and let the installer do<br />
the rest. If you select NO, you will be asked to enter the networking<br />
information manually.<br />
Either way, your network should be successfully configured, and if<br />
you're of the skeptical kind, you may check connectivity using<br />
standard tools like ping on another console.<br />
<br />
As automations are not perfect, you may not be able to successfully<br />
use the installer to set up your network. In these rare cases, set up you network device manually in one of the consoles.<br />
<br />
====Prepare Hard Drive====<br />
<br />
Prepare Hard Drive presents a submenu offering two<br />
alternatives of preparing the target drive for installation.<br />
<br />
The first choice is Auto-Prepare, which will automatically partition<br />
your hard drive into a /boot, swap, and root partition, and then<br />
create filesystems on all three. These partitions will also be<br />
automatically mounted in the proper place. To be exact, this option<br />
will create:<br />
* 32 MB ext2 /boot partition<br />
* 256 MB swap partition<br />
* root and /home partition with the remaining space. (Root and /home will share the same file system type if choosing the auto-prepare option).<br />
<br />
Actual sizes may vary slightly, due to different hard disk geometries.<br />
You can choose this option if you don't know much about hard drive<br />
partitions, but be warned:<br />
<br />
AUTO-PREPARE WILL ERASE ALL DATA ON THE CHOSEN HARD DRIVE!<br />
Read the warning presented by the installer very carefully, and make<br />
sure the correct device is about to be partitioned!<br />
<br />
A way to verify your choice for a device to partition would be to open<br />
another terminal (ALT-F2, Enter) and enter<br />
cfdisk -P s <name of device><br />
<br />
This will display the current partition table of the selected device,<br />
which should suffice to identify the hard disk.<br />
<br />
If you prefer to do the partitioning manually, use '''Partition Hard Drives''' and '''Set Filesystem Mountpoints''' to prepare the target media according to your specifications, as outlined below. After successful preparation, choose Return to Main Menu.<br />
<br />
====Partition Hard Drives====<br />
<br />
Partition Hard Drives should be skipped if you chose Auto-Prepare<br />
already!<br />
<br />
Otherwise you should select the disk(s) you want to partition, and<br />
you'll be dropped into the cfdisk program where you can freely modify<br />
the partitioning information until you [Write] and [Quit].<br />
<br />
You will need at least a root partition to continue the installation,<br />
and it's helpful to note somewhere which partition you're going to<br />
mount where, as you'll be asked exactly that in the next step.<br />
<br />
====Set Filesystem Mountpoints====<br />
<br />
Set Filesystem Mountpoints should also be skipped if you chose to<br />
Auto-Prepare your hard drive. You should select this option once the<br />
partition information is edited to your liking with the previous menu<br />
selection, or already existent through whatever other means.<br />
<br />
First, select the previously created swap partition from the list, or NONE, if you<br />
do not want to use a swap partition. Using a swap ''file'' is not directly<br />
supported by the installer; Instead choose NONE here, finish the<br />
mountpoint associations, and activate a swap file on your desired,<br />
formatted partition with the swapon command.<br />
<br />
After setting up the swap partition, you will be asked to specify the<br />
partition to be used as the root partition. This is mandatory.<br />
<br />
The association process is then repeated until you choose DONE from<br />
the list, ideally after all listed partitions have been associated<br />
with their intended mountpoints. The installer will suggest /boot for<br />
all following mountpoints after choosing swap and root.<br />
<br />
Each time a partition to mount is specified, you will be asked if you<br />
want to create a filesystem on the respective partition. Selecting<br />
YES, will prompt you for the filesystem type to create. The partition will then be<br />
formatted with the chosen filesystem type, destroying all data in the<br />
process. <br />
<br />
If additional mountpoints are desired, for example, a separate /boot or /home partition, you will be able to do so. Simply<br />
* select a partition to mount<br />
* choose a filesystem (if you want to create one instead of keeping existing data)<br />
* enter a unique mountpoint for the partition<br />
<br />
Repeat these steps until satisfied, then select DONE to create<br />
any filesystems and mount the partitions in their respective places.<br />
Before the actual formatting is done, the installer will present to<br />
you a list of all choices for review. After formatting and<br />
mounting all partitions, you may return to the Main Menu and proceed<br />
with the next step.<br />
<br />
===Select Packages===<br />
Now we shall select packages to install in our system.<br />
*Core ISO: Choose CD as source and select the appropriate CD drive if you have more than one.<br />
*FTP ISO: Select an FTP/HTTP mirror. ''Note that archlinux.org is throttled to 50KB/s''. ''Note also that some mirrors doesn't support resuming in case of download failure (e.g. ftp.free.fr)''<br />
<br />
The installer will always install a basic working system. You are given the option to install some basic development tools, such as GCC, autoconf, automake, make and some other useful packages such as openssh, sudo, iptable and some wifi packages.<br />
<br />
If you want to install any of the extra packages during the installation, you need to select the one and only package category '''BASE-DEVEL''' using the space bar.<br />
<br />
The next screen will present you with the selected packages within '''BASE-DEVEL'''.<br />
<br />
Once you're done selecting the packages you need, leave the selection<br />
screen and continue to the next step, Install Packages.<br />
<br />
====Install Packages====<br />
<br />
Install Packages will now install the base system and any other packages you<br />
selected with resolved dependencies onto your harddisk. Don't be<br />
surprised if more packages are installed than you selected! Those<br />
packages are dependencies for your selection, and the installer will<br />
not explicitly ask for permission to install these extra packages, as<br />
it assumes you know what you're doing.<br />
<br />
After the package selection, the installer will not check for free<br />
space on the target! This seemingly trivial task would eat up<br />
considerable time, and therefore the installer simply assumes to have<br />
enough free space on the target partition(s). In case it doesn't, the<br />
installation will fail in various funny ways. A df -h in another<br />
terminal might show that one or more of the targets mounted below /mnt<br />
have been filled up, causing mischief. Consider repartitioning or<br />
selecting a smaller set of packages.<br />
<br />
Error messages and debugging output is echoed to vc/5 (ALT-F5). After the packages have been installed, proceed to the next step, Configure System.<br />
<br />
Pacman will ask you whether it should keep the installed packages in cache. As you can delete them later using 'pacman -Scc', selecting 'yes' is recommended.<br />
<br />
==Configure System==<br />
<br />
Configure System allows you to edit the configuration files crucial<br />
for your newly installed system. Initially you will be asked whether<br />
to allow the hwdetect script to try and detect your hardware, and<br />
produce some (even more) sensible defaults for your configuration<br />
files. Unless you're having problems/crashes, you should let it have<br />
its way, and work from what it generates.<br />
<br />
Answer the following questions about RAID, LVM and encrypted volumes<br />
with Yes, if your root partition resides on a RAID, LVM or encrypted<br />
volume, respectively, to automatically add the necessary HOOKS to the<br />
mkinitcpio.conf. Otherwise you will get a kernel panic during boot, as<br />
your root partition will not be accessible at the time of boot. Most<br />
people will answer these questions with No, though, and not waste a<br />
second thought about it.<br />
<br />
After this automatic preconfiguration you'll be asked for your<br />
favourite editor to use for manually fine-tuning the generated<br />
configuration files, either VIM or nano. When in doubt, choose nano.<br />
<br />
===Configuration Files===<br />
These are the core configuration files for Arch Linux, to be configured with a text-editor. Only the most basic configuration<br />
files are listed here. If you need help configuring a specific<br />
service, please read the appropriate manpage or refer to any online<br />
documentation you need. In many cases, the Arch Linux Wiki and forums<br />
are a rich source for help as well.<br />
<br />
{{Box Note | Arch Linux does not use any abstraction layers to administrate your system. As a result, you can usually stick to any instructions published by the author of a particular software package, or whatever you find in a search engine of your choice, and it likely will work without confusing your system, because your system simply does not 'care'.}}<br />
<br />
'''List of Configuration Files'''<br />
* Setup-relevant configuration files:<br />
** /etc/rc.conf<br />
** /etc/hosts<br />
** [[Fstab | /etc/fstab]]<br />
** /etc/mkinitcpio.conf<br />
** /etc/modprobe.conf<br />
** /etc/resolv.conf<br />
** /etc/locale.gen<br />
** /boot/grub/menu.lst<br />
** /etc/lilo.conf<br />
* Additional configuration files:<br />
** /etc/conf.d/*<br />
** /etc/profile<br />
<br />
<br />
'''/etc/rc.conf'''<br />
<br />
This is the main configuration file for Arch Linux. It allows you to<br />
set your keyboard, timezone, hostname, network, daemons to run and<br />
modules to load at bootup, profiles, and more. You should read through<br />
all the settings in this file and make sure you understand them, and<br />
change them where appropriate:<br />
<br />
LOCALE<br />
This sets your system language, which will be used by all<br />
i18n-friendly applications and utilities. See locale.gen below<br />
for available options. This setting's default is fine for US <br />
English users.<br />
<br />
HARDWARECLOCK<br />
Either UTC if your BIOS clock is set to UTC, or localtime if<br />
your BIOS clock is set to your local time. If you have an OS<br />
installed which cannot handle UTC BIOS times correctly, like<br />
Windows, choose localtime here, otherwise you should prefer<br />
UTC, which makes daylight savings time a non-issue and has a<br />
few other positive aspects.<br />
<br />
TIMEZONE<br />
Specifies your time zone. Possible time zones are the relative<br />
path to a zoneinfo file starting from the directory<br />
/usr/share/zoneinfo. For example, a german timezone would be<br />
Europe/Berlin, which refers to the file<br />
/usr/share/zoneinfo/Europe/Berlin. If you don't know the exact<br />
name of your timezone file, worry about it later.<br />
<br />
KEYMAP<br />
Defines the keymap to load with the loadkeys program on bootup.<br />
Possible keymaps are found in /usr/share/kbd/keymaps. Please<br />
note that this setting is only valid for your TTYs, not any<br />
graphical window managers or X! Again, the default is fine for<br />
US users.<br />
<br />
CONSOLEFONT<br />
Defines the console font to load with the setfont program on<br />
bootup. Possible fonts are found in<br />
/usr/share/kbd/consolefonts.<br />
<br />
CONSOLEMAP<br />
Defines the console map to load with the setfont program on<br />
bootup. Possible maps are found in /usr/share/kbd/consoletrans.<br />
You will want to set this to a map suitable for your locale<br />
(8859-1 for Latin1, for example) if you're using an utf8 locale<br />
above, and use programs that generate 8-bit output. If you're<br />
using X11 for everyday work, don't bother, as it only affects<br />
the output of GNU/Linux console applications.<br />
<br />
USECOLOR<br />
Enable (or disable) colorized status messages during boot-up.<br />
<br />
MOD_AUTOLOAD<br />
If set to "yes", Arch will scan your hardware at bootup and<br />
attempt to automatically load the proper modules for your<br />
system. This is done with the hwdetect utility.<br />
<br />
MOD_BLACKLIST<br />
This is an array of modules that you do not want to be loaded<br />
at bootup. For example, if you don't want that annoying PC<br />
speaker, you could blacklist the pcspkr module.<br />
<br />
MODULES<br />
In this array you can list the names of modules you want to<br />
load during bootup without the need to bind them to a hardware<br />
device as in the modprobe.conf. Simply add the name of the<br />
module here, and put any options into the modprobe.conf if need<br />
be. Prepending a module with a bang ('!') will not load the<br />
module during bootup (this is not the same as MOD_BLACKLIST!),<br />
thus allowing to "comment out" certain modules if necessary. A<br />
benefit of specifying networking modules here is that ethernet<br />
cards covered by the listed modules will always be detected in<br />
the order the modules are listed. This prevents the dreaded<br />
interface confusion where your ethernet hardware is assigned to<br />
seemingly random interfaces after each boot. An even better way<br />
to handle this is using static interface labels by configuring<br />
udev appropriately, though.<br />
<br />
USELVM<br />
Set to "YES" to run a vgchange during sysinit, thus activating<br />
any LVM groups. If you have no idea what this means, don't<br />
bother.<br />
<br />
HOSTNAME<br />
Set this to the hostname of the machine, without the domain<br />
part. This is totally your choice, as long as you stick to<br />
letters, digits and a few common special characters like the<br />
dash. Don't be too creative here, though, and when in doubt,<br />
use the default.<br />
<br />
INTERFACES<br />
Here you define the settings for your networking interfaces.<br />
The default lines and the included comments explain the setup<br />
well enough. If you use DHCP, 'eth0="dhcp"' should work for you. If you do not use DHCP to configure a device, just<br />
keep in mind that the value of the variable (whose name must be<br />
equal to the name of the device which is supposed to be<br />
configured) equals the line which would be appended to the<br />
ifconfig command if you were to configure the device manually<br />
in the shell.<br />
<br />
ROUTES<br />
You can define your own static network routes with arbitrary<br />
names here. Look at the example for a default gateway to get<br />
the idea. Basically the quoted part is identical to what you'd<br />
pass to a manual route add command, therefore reading man route<br />
is recommended if you don't know what to write here, or simply<br />
leave this alone.<br />
<br />
[[Network_Profiles | NET_PROFILES]]<br />
Enables certain network profiles at bootup. Network profiles<br />
provide a convenient way of managing multiple network<br />
configurations, and are intended to replace the standard<br />
INTERFACES/ROUTES setup that is still recommended for systems<br />
with only one network configuration. If your computer will be<br />
participating in various networks at various times (eg, a<br />
laptop) then you should take a look at the<br />
/etc/network-profiles/ directory to set up some profiles. There<br />
is a template file included there that can be used to create<br />
new profiles.<br />
<br />
DAEMONS<br />
This array simply lists the names of those scripts contained in<br />
/etc/rc.d/ which are supposed to be started during the boot<br />
process, as well as the order in which they start. If a script name is prefixed with a bang (!), it is<br />
not executed. If a script is prefixed with an "at" symbol (@),<br />
then it will be executed in the background, ie. the startup<br />
sequence will not wait for successful completion before<br />
continuing. Usually you do not need to change the defaults to<br />
get a running system, but you are going to edit this array<br />
whenever you install system services like sshd, and want to<br />
start these automatically during bootup. This is basically<br />
Arch's way of handling what others handle with various symlinks<br />
to an init.d directory.<br />
<br />
<br />
'''/etc/hosts'''<br />
<br />
This is where you stick hostname/ip associations of computers on your<br />
network. If a hostname isn't known to your DNS, you can add it here to<br />
allow proper resolving, or override DNS replies. You usually don't<br />
need to change anything here, but you might want to add the hostname<br />
and hostname + domain of the local machine to this file, resolving to<br />
the IP of your network interface. Some services, postfix for example,<br />
will bomb otherwise. If you don't know what you're doing, leave this<br />
file alone until you read man hosts.<br />
<br />
<br />
'''[[Fstab | /etc/fstab]]'''<br />
<br />
Your filesystem settings and mountpoints are configured here. The<br />
installer should have created the necessary entries for you, but you<br />
should look over it and make sure it's right, especially when using an<br />
encrypted root device, LVM or RAID.<br />
<br />
With the current kernel, an important change has been introduced<br />
pertaining to the ATA/IDE subsystem. The new pata (Parallel ATA)<br />
drivers replace the legacy IDE subsystem, and one important change is<br />
that the naming scheme for IDE disks has changed from the old hda,<br />
hdb, etc. to also use device names of the type sda, sdb, etc, just<br />
like SCSI and SATA devices do. Because of this, when using the new<br />
pata driver in the HOOKS of the /etc/mkinitcpio.conf, remember to use<br />
the appropriate device names in your /etc/fstab and bootloader<br />
configuration! Alternatively, you could use the /dev/disk/by-uuid/...<br />
or /dev/disk/by-label/... representations of your disk drives where<br />
available to make absolutely sure you're referring to the right<br />
partitions, and save yourself the trouble of sorting out whether<br />
you're supposed to use sda or hda. If that's not an option, here's the<br />
rundown; If you're using pata instead of ide in the HOOKS array of the<br />
/etc/mkinitcpio.conf, you'll be using the sd? names. If not, use the<br />
old style hd? names. It is therefore crucial to check the HOOKS array<br />
in the /etc/mkinitcpio.conf, to be able to adapt the other files<br />
accordingly.<br />
<br />
<br />
'''/etc/mkinitcpio.conf'''<br />
<br />
This file allows you to fine-tune the initial ramdisk (also commonly<br />
referred to as the "initrd") for your system. The initrd is a gzipped<br />
image that is read by the kernel during bootup. The purpose of the<br />
initrd is to bootstrap the system to the point where it can access the<br />
root filesystem. This means it has to load any modules that are<br />
required to "see" things like IDE, SCSI, or SATA drives (or USB/FW, if<br />
you are booting off a USB/FW drive). Once the initrd loads the proper<br />
modules, either manually or through udev, it passes control to the<br />
Arch system and your bootup continues. For this reason, the initrd<br />
only needs to contain the modules necessary to access the root<br />
filesystem. It does not need to contain every module you would ever<br />
want to use. The majority of your everyday modules will be loaded<br />
later on by udev, during the init process.<br />
<br />
By default, mkinitcpio.conf is configured to provide all known modules<br />
for IDE, SCSI, or SATA systems through so-called HOOKS. This means the<br />
default initrd should work for almost everybody. The downside to this<br />
is that there are many modules loaded that you will not need. This is<br />
easily visible by examining your module table after booting up (with<br />
the lsmod command). While this doesn't actually hurt anything, some<br />
people find it annoying. To cull this list down to only what you<br />
actually need, you can edit mkinitcpio.conf and remove the subsystem<br />
HOOKS (ie, IDE, SCSI, RAID, USB, etc) that you don't need.<br />
<br />
You can customize even further by specifying the exact modules you<br />
need in the MODULES array and remove even more of the hooks, but take<br />
heed to the comments in the file, as this is a touchy place to go<br />
crazy with removing entries!<br />
<br />
If you're using RAID or encryption on your root filesystem, then<br />
you'll have to tweak the RAID/CRYPT settings near the bottom. See the<br />
wiki pages for RAID/LVM, filesystem encryption, and mkinitcpio for<br />
more info.<br />
<br />
When you're finished tweaking mkinitcpio.conf, you must run mkinitcpio<br />
-p kernel26 as root to regenerate the images, unless you're still<br />
installing the system; In that case this step will be done<br />
automatically after choosing Install Kernel later in the process.<br />
<br />
WARNING: If you fail to set up your mkinitcpio.conf correctly, your<br />
system will not boot! For this reason, you should be especially<br />
careful when tweaking this file.<br />
<br />
If you do manage to render your system unbootable, you can try using<br />
the fallback image that is installed alongside the stock kernel. A<br />
boot option for this is included in the default GRUB and LILO <br />
configuration.<br />
<br />
Read the warning about the pata transition problems elaborated in the<br />
fstab section carefully!<br />
<br />
<br />
'''/etc/modprobe.conf'''<br />
<br />
This tells the kernel which modules it needs to load for system<br />
devices, and what options to set. For example, to have the kernel load<br />
your Realtek 8139 ethernet module when it starts the network (ie.<br />
tries to setup eth0), use this line:<br />
alias eth0 8139too<br />
<br />
The syntax of this file is nearly identical to the old modules.conf<br />
scheme, unless you use some of the more exotic options like<br />
post-install. Then you should invest a little time into reading man<br />
modprobe.conf.<br />
<br />
Most people will not need to edit this file.<br />
<br />
<br />
'''/etc/resolv.conf'''<br />
<br />
Use this file to manually setup your nameserver(s) that you want to<br />
use. It should basically look like this:<br />
search domain.tld<br />
nameserver 192.168.0.1<br />
nameserver 192.168.0.2<br />
<br />
Replace domain.tld and the ip addresses with your settings. The<br />
so-called search domain specifies the default domain that is appended<br />
to unqualified hostnames automatically. By setting this, a ping myhost<br />
will effectively become a ping myhost.domain.tld with the above<br />
values. These settings usually aren't mighty important, though, and<br />
most people should leave them alone for now. If you use DHCP, this<br />
file will be replaced with the correct values automatically when<br />
networking is started, meaning you can and should happily ignore this<br />
file.<br />
<br />
<br />
'''/etc/locale.gen'''<br />
<br />
This file contains a list of all supported locales and charsets<br />
available to you. When choosing a LOCALE in your /etc/rc.conf or when<br />
starting a program, it is required to uncomment the respective locale<br />
in this file, to make a "compiled" version available to the system,<br />
and run the locale-gen command as root to generate all uncommented<br />
locales and put them in their place afterwards. You should uncomment<br />
all locales you intend to use.<br />
<br />
During the installation process, you do not need to run locale-gen<br />
manually, this will be taken care of automatically after saving your<br />
changes to this file.<br />
<br />
By default, all locales are commented out, including the default<br />
en_US.utf8 locale referred to in the /etc/rc.conf file. To make your<br />
system work smoothly, you must edit this file and uncomment at least<br />
the one locale you're using in your rc.conf.<br />
<br />
<br />
'''/boot/grub/menu.lst'''<br />
<br />
GRUB is the default bootloader for Arch Linux. You should check and<br />
modify this file to accommodate your boot setup if you want to use<br />
GRUB, otherwise read on about the LILO configuration.<br />
<br />
Make sure you read the warning regarding the pata transition<br />
elaborated on in the fstab section!<br />
<br />
Configuring GRUB is quite easy, the biggest hurdle is that it uses yet<br />
another device naming scheme different from /dev; Your hard disks as a<br />
whole are referred to as (hd0), (hd1), etc., sequentially numbered in<br />
order of appearance on the IDE/SCSI bus, just like the hda, hdb, etc.<br />
names in GNU/Linux. The partitions of a disk are referred to with (hd0,0),<br />
(hd0,1) and so on, with 0 meaning the first partition. A few<br />
conversion examples are included in the default menu.lst to aid your<br />
understanding.<br />
<br />
Once you grasped the concept of device naming, all you need to do is<br />
to choose a nice title for your boot section(s), supply the correct<br />
root partition device as a parameter to the root option to have it<br />
mounted as / on bootup, and create a kernel line that includes the<br />
partition and path where the kernel is located as well as any boot<br />
parameters. If using the stock Arch 2.6.x kernel, you'll also need an<br />
initrd line that points to the kernel26.img file in your /boot<br />
directory. The path you put on your initrd line should be the same as<br />
the path to vmlinuz26 that you provide on the kernel line. You should<br />
be fine with the defaults, just check whether the partition<br />
information is correct in the root and kernel lines, especially in<br />
regard to the pata issue!<br />
<br />
To create a boot option that loads the bootsector of a different OS,<br />
the following example might be helpful. You will probably succeed in<br />
starting any Microsoft-based operating system with it, just add this<br />
block to the file after any other sections, and modify the partition<br />
device accordingly to refer to the partition containing the bootsector<br />
of the OS you are intending to boot.<br />
(1) Other OS<br />
title My Other OS<br />
rootnoverify (hd0,1)<br />
makeactive<br />
chainloader +1<br />
<br />
For advanced configuration of other OSes, please refer to the online<br />
GRUB manual.<br />
<br />
After checking your bootloader configuration for correctness, you'll<br />
be prompted for a partition to install the loader to. Unless you're<br />
using yet another boot loader, you should install GRUB to the MBR of<br />
the installation disk, which is usually represented by the appropriate<br />
device name without a number suffix.<br />
<br />
<br />
'''/etc/lilo.conf'''<br />
<br />
This is the configuration file for the LILO bootloader. Make sure you<br />
check this one and get it right if you want to use LILO to boot your<br />
system. See LILO documentation for help on this.<br />
<br />
Things you should check are the root= lines in the image sections and<br />
the boot= line right at the beginning of the file. The root lines<br />
specify the device which shall be mounted as the root filesystem on<br />
bootup. If you don't know what is supposed to be entered here, change<br />
to another terminal and type mount to see a list of all currently<br />
mounted drives, and look for the line which displays a device name<br />
mounted on /mnt type [...]. The device path at the beginning of this<br />
very line should be entered in the root lines of your lilo.conf.<br />
Change if necessary, and keep the pata issue in mind!<br />
<br />
The boot line should be okay by default in most cases. Unless you have<br />
a weird boot manager setup in mind with multiple OSes, the device<br />
referenced here should be having the same prefix your root lines have,<br />
but not end with a number. For example, a root of /dev/hda3 means you<br />
probably want to install LILO into the Master Boot Record of the hard<br />
disk, so you would set boot to /dev/hda, which references the disk as<br />
a whole. During installation, the boot device must be the current name<br />
of the device where you want to write the boot sector to; This may<br />
differ from the name of the device after the first boot, thanks to the<br />
pata transition! Check carefully what device to write to during the<br />
installation stage, for example with the mount command.<br />
<br />
To prevent some serious grief, you should make sure you know how to<br />
restore the bootsector of your other OSes, for example with Windows's<br />
FIXBOOT/FIXMBR tools.<br />
<br />
To be on the safe side, you should keep the option lba32 listed. This<br />
will prevent some geometry issues from happening.<br />
<br />
In some cases, depending on your BIOS, LILO will not run on bootup and<br />
spill out an error code infinitely. In most cases you either removed<br />
the lba32 option, or your hardware setup is a little special, meaning<br />
that maybe your CD-ROM drive is primary master and the hard disk you<br />
installed secondary slave. This can very well confuse your BIOS, and<br />
thus stop the boot process. To prevent that you can try and make the<br />
install drive the primary master on your IDE bus. If you've got a<br />
mixed IDE and SCSI system and the problem persists, you'll probably<br />
need some experimentation with the disk and bios options of LILO to<br />
provide a working mapping; The disk drives in your system are numbered<br />
sequentially by your BIOS, starting with 0x80. If you're lucky your<br />
SCSI controller tells you which drive has which BIOS ID, but usually<br />
you're not. How the drives are effectively numbered is depending on<br />
your BIOS, so in the worst case you can only guess until it works. A<br />
typical disk line would look like this:<br />
boot=/dev/hda<br />
disk=/dev/hda bios=0x80<br />
<br />
The disk option maps a BIOS ID to the disk device known to the system. Note<br />
that there is still no guarantee that things will work as other things<br />
can be wrong, so do not despair if all your tries fail, but rather try<br />
rearranging your hardware in a way that's not totally odd. In this<br />
area too much can go wrong and needs special handling to be explained<br />
here. In most cases the lba32 option will suffice anyway. Old hard<br />
drives will usually need a little more special care until they do as<br />
told.<br />
<br />
Don't become fidgety when reading this section, I (Dennis) just<br />
happened to stumble over this problem when experimenting with a rather<br />
odd system, and figured it'd be a good idea to mention this show<br />
stopper and workarounds here. You probably won't ever experience this,<br />
as you should be using GRUB anyway.<br />
<br />
How to recreate a LILO boot sector with only a rescue disk is<br />
explained later in this document.<br />
<br />
<br />
'''/etc/conf.d/*'''<br />
<br />
During setup, this is totally unimportant. Consider this as reference<br />
for the interested.<br />
<br />
Some daemon scripts will have a matching configuration file in this<br />
directory that contains some more-or-less useful default values. When<br />
a daemon is started, it will first source the settings from its<br />
config file within this directory, and then source the /etc/rc.conf.<br />
This means you can easily centralize all your daemon configuration<br />
options in your /etc/rc.conf simply by setting an appropriate variable<br />
value, or split up your configuration over multiple files if you<br />
prefer a decentralized approach to this issue. Isn't life great if<br />
it's all just simple scripting?<br />
<br />
<br />
'''/etc/profile'''<br />
<br />
This script is run on each user login to initialize the system. It is<br />
kept quite simple under Arch Linux, as most things are. You may wish<br />
to edit or customize it to suit your needs.<br />
<br />
====Kernel====<br />
<br />
The CD-ROM includes the latest kernel available at time of release. If you are using the FTP<br />
Installation method, the kernel about to be installed will be the<br />
current version waiting on your FTP source, and might therefore<br />
introduce changes and/or incompatibilities unknown at the present<br />
time. This is unlikely, but keep it in mind.<br />
<br />
====Install Bootloader====<br />
<br />
Install Bootloader will install a bootloader on your hard drive,<br />
either GRUB (recommended) or LILO, depending on your personal<br />
preference.<br />
<br />
Before installing the bootloader, the setup script will want you to<br />
examine the appropriate configuration file to confirm the proper<br />
settings. <br />
<br />
If you choose to install LILO, the bootloader will be automatically<br />
installed according to your settings in the configuration file, whilst<br />
GRUB demands the selection of a partition to install the bootloader<br />
to. Here you should choose what you would enter as the boot option of<br />
LILO, which is usually the entry named /dev/hda, as it refers the<br />
master boot record of the first hard disk. Detailed error messages can<br />
be found as usual on VC5 (virtual console 5), if anything goes wrong.<br />
<br />
If you plan on setting up a multiboot system, you may wish to install the bootloader in your / or /boot partition, and<br />
refer to that boot sector from whatever other boot loader you want to<br />
reside in the master boot record. (chainloading)<br />
<br />
Installing a boot loader in the MBR will relentlessly overwrite any<br />
existing bootloader! Make sure you understand the implications of that<br />
if you're running a multiboot system, or want to preserve an installed<br />
bootloader from another OS!<br />
<br />
====Exit Install====<br />
<br />
Exit the Installer, eject the CD, and:<br />
reboot<br />
<br />
Login as root and add a user as outlined in the<br />
[[User_Management | User Management]] section, and set up your Internet Connection.<br />
<br />
Congratulations! Welcome to your new Arch Linux base system!<br />
<br />
==APPENDIX==<br />
===Adding a Window Manager/Desktop Environment===<br />
*[[KDE]] <br />
*[[KDEmod]]<br />
*[[GNOME]]<br />
*[[Xfce]]<br />
*[[Openbox]]<br />
*[[Wmii]]<br />
*[[Fluxbox]]<br />
*[[LXDE]]<br />
*[[E17]]<br />
*[[Xmonad]]<br />
See also [[.xinitrc]]<br />
<br />
===Boot Scripts===<br />
<br />
Arch Linux uses a fairly simple bootup sequence quite similar to *BSDs. The first boot script to run is /etc/rc.sysinit. When it's done, /etc/rc.multi will be called (in a normal bootup). The last script to run will be /etc/rc.local. When started in runlevel 1, the single user mode, the script /etc/rc.single is run instead of /etc/rc.multi. You will not find an endless symlink collection in the /etc/rc?.d/ directories to define the bootup sequence for all possible runlevels. In fact, due to this approach Arch only really has three runlevels, if you take starting up X in runlevel 5 into account. The boot scripts are using the variables and definitions found in the /etc/rc.conf file and also a set of general functions defined in the<br />
/etc/rc.d/functions script. If you plan to write your own daemon<br />
files, you should consider having a look at this file and existing<br />
daemon scripts.<br />
<br />
Boot Script Overview<br />
<br />
#/etc/rc.sysinit<br />
#/etc/rc.single<br />
#/etc/rc.multi<br />
#/etc/rc.local<br />
#/etc/rc.shutdown<br />
#/etc/rc.local.shutdown<br />
#/etc/rc.d/*<br />
<br />
<br />
'''/etc/rc.sysinit'''<br />
<br />
The main system boot script. It does boot-critical things like<br />
mounting filesystems, running udev, activating swap, loading modules,<br />
setting localization parameters, etc. You will most likely never need<br />
to edit this file!<br />
<br />
<br />
'''/etc/rc.single'''<br />
<br />
Single-user startup. Not used in a normal boot-up. If the system is<br />
started in single-user mode, for example with the kernel parameter 1<br />
before booting or during normal multi-user operation with the command<br />
init 1, this script makes sure no daemons are running except for the<br />
bare minimum; syslog-ng and udev. The single-user mode is useful if<br />
you need to make any changes to the system while making sure that no<br />
remote user can do anything that might cause data loss or damage.<br />
<br />
For desktop users, this mode usually is useless as crud. You should<br />
have no need to edit this script, either.<br />
<br />
<br />
'''/etc/rc.multi'''<br />
<br />
Multi-user startup script. It starts all daemons you configured in the<br />
DAEMONS array (set in /etc/rc.conf) after which it calls<br />
/etc/rc.local. You shouldn't feel a pressing need to edit this file.<br />
<br />
<br />
'''/etc/rc.local'''<br />
<br />
Local multi-user startup script. It is a good place to put any<br />
last-minute commands you want the system to run at the very end of the<br />
bootup process. This is finally the one and only script you should<br />
modify if needed, and you have total freedom on what to add to this<br />
script.<br />
<br />
Most common system configuration tasks, like loading modules, changing<br />
the console font or setting up devices, usually have a dedicated place<br />
where they belong. To avoid confusion, you should make sure that<br />
whatever you intend to add to your rc.local isn't feeling just as home<br />
in /etc/profile.d/ or any other already existant config location<br />
instead.<br />
<br />
<br />
'''/etc/rc.shutdown'''<br />
<br />
System shutdown script. It stops daemons, unmounts filesystems,<br />
deactivates the swap, etc. Just don't touch.<br />
<br />
<br />
'''/etc/rc.local.shutdown'''<br />
<br />
Analogous to the /etc/rc.local file, this file may contain any<br />
commands you want to run right before the common rc.shutdown is<br />
executed. Please note that this file does not exist by default, and<br />
for it to work properly, it must be set as executable.<br />
<br />
<br />
'''/etc/rc.d/*'''<br />
<br />
This directory contains the daemon scripts referred to from the<br />
rc.conf's DAEMONS array. In addition to being called on bootup, you<br />
can use these scripts when the system is running to manage the<br />
services of your system. For example the command<br />
/etc/rc.d/postfix stop<br />
<br />
will stop the postfix daemon. Of course a script only exists when the<br />
appropriate package has been installed (in this case postfix). With a<br />
basic system install, you don't have many scripts in here, but rest<br />
assured that all relevant daemon scripts end up here. This directory<br />
is pretty much the equivalent to the /etc/rc3.d/ or /etc/init.d/<br />
directories of other distributions, without all the symlink hassle.<br />
<br />
===User Management===<br />
<br />
Users and groups can be added and deleted with the standard commands<br />
provided in the util-linux package: useradd, userdel, groupadd,<br />
groupdel, passwd, and gpasswd. The typical way of adding a user is<br />
similar to this procedure:<br />
useradd -m -s /bin/bash johndoe<br />
passwd johndoe<br />
<br />
The first command will add the user named johndoe to the system,<br />
create a home directory for him at /home/johndoe, and place some<br />
default login files in his home directory. It will also set his login<br />
shell to be /bin/bash. The second command will ask you for a password<br />
for the johndoe user. A password is required to activate the account.<br />
<br />
As an alternative to the useradd command, the adduser script is also<br />
available to interactively create new users on your system simply by<br />
answering questions.<br />
<br />
See the manpages for more information on the remaining commands. It is<br />
a good idea to create one or multiple normal users for your day-to-day<br />
work to fully use the available security features and minimize<br />
potential damage that may be the result of using the root user for<br />
anything but system administration tasks.<br />
<br />
===Internet Access===<br />
<br />
Due to a lack of developers for dialup issues, connecting Arch to the<br />
Internet with a dialup line is requiring a lot of manual setup. If at<br />
all possible, set up a dedicated router which you can then use as a<br />
default gateway on the Arch box.<br />
<br />
There are quite a few dialup related documents in the Arch Linux Wiki<br />
<br />
====Analog Modem====<br />
<br />
To be able to use a Hayes-compatible, external, analog modem, you need<br />
to at least have the ppp package installed. Modify the file<br />
/etc/ppp/options to suit your needs and according to man pppd. You<br />
will need to define a chat script to supply your username and password<br />
to the ISP after the initial connection has been established. The<br />
manpages for pppd and chat have examples in them that should suffice<br />
to get a connection up and running if you're either experienced or<br />
stubborn enough. With udev, your serial ports usually are /dev/tts/0</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Newcomers_Guide&diff=58747
Newcomers Guide
2009-01-21T15:53:05Z
<p>Zaggynl: </p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{Article summary start}}<br />
{{Article summary text|General installation documentation for the Arch Linux distribution.}}<br />
{{Article summary heading|Available Languages}}<br />
{{i18n_entry|English|Official Arch Linux Install Guide}}<br />
{{i18n_entry|&#31616;&#20307;&#20013;&#25991;|Arch Linux &#23448;&#26041;&#23433;&#35013;&#25351;&#21335;}}<br />
{{i18n_entry|&#27491;&#39636;&#20013;&#25991;|Arch Linux &#23448;&#26041;&#23433;&#35037;&#25351;&#21335;}}<br />
{{i18n_entry|&#268;esky|Oficiální instala&#269;ní p&#345;íru&#269;ka (&#268;esky)}}<br />
{{i18n_entry|&#1056;&#1091;&#1089;&#1089;&#1082;&#1080;&#1081;|&#1056;&#1091;&#1082;&#1086;&#1074;&#1086;&#1076;&#1089;&#1090;&#1074;&#1086; &#1087;&#1086; &#1091;&#1089;&#1090;&#1072;&#1085;&#1086;&#1074;&#1082;&#1077;}}<br />
{{i18n_entry|Español|Guía oficial de Instalación}}<br />
{{i18n_entry|Italiano|Official Arch Linux Install Guide (Italiano)}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|Beginners Guide}} (If you are new to Arch)<br />
{{Article summary end}}<br />
<br />
<br />
==Introduction==<br />
<br />
===What is Arch Linux?===<br />
<br />
Arch Linux is an independently developed i686/x86-64-optimized GNU/Linux distribution. Development is focused on a balance of simplicity, elegance, code-correctness and bleeding edge software.<br />
<br />
The Arch system and binary packages are compiled for i686 or x86-64 processors. Its lightweight and simple design makes it easy to extend and mold into whatever kind of system you're building.<br />
<br />
===License===<br />
<br />
Arch Linux, pacman, documentation, and scripts are copyright<br />
©2002-2007 by Judd Vinet, ©2007-2008 by Aaron Griffin and are licensed under the GNU General Public License Version 2.<br />
<br />
==Installing Arch Linux==<br />
<br />
===Pre-Installation===<br />
<br />
Arch Linux is optimized for the i686 processor and therefore will not<br />
run on any lower or incompatible generations of x86 CPUs<br />
(i386,i486,i586). A Pentium II or AMD Athlon processor or higher is<br />
required. Modern VIA C3 processors are also supported. x86-64 architectures are also officially supported.<br />
<br />
There is a community-driven project that provides packages for i586<br />
and ppc. See this site for more information.<br />
<br />
Before installing Arch Linux, you should decide which installation<br />
method you would like to use. Arch Linux provides two different<br />
bootable ISO images for a CD-ROM installation. Installing Arch from a USB stick or from within another already installed OS is also supported.<br />
<br />
As the preferred method of installation is the flexible CD-ROM based<br />
installation, we offer you two variants of the installation medium<br />
which only differ in terms of supplied packages. You can instruct the<br />
installer to obtain the packages via FTP using any of these images,<br />
and all images can also be used as fully functional live cds.<br />
<br />
* The core iso (~300MB) is a live environment which contains a snapshot of the entire /core repository. Packages are divided into 4 categories: BASE, SUPPORT, DEVEL and LIB. RAID/LVM are fully supported; all necessary packages are included within /core. Installing from a medium created with this image results in a completely functional GNU/Linux system, without any frills, expecting to be used from the command line; the Linux kernel, GNU toolchain and a few extra modules and libraries. This image is ideally suited for those who have a rather slow or nonexistent internet connection on the candidate machine, making an FTP install unfeasible. The name of the iso will be "archlinux-i686-2008.xx-x.core.iso", according to your architecture<br />
* The FTP iso (~175MB) is a live environment, containing no packages at all, but rather pulls in all software over your internet connection. If you have access to a fast and easily setup internet connection, this method may be preferred, since the completed system will be completely up-to-date, without requiring further upgrades from the package versions included on the Core CD. Of course all packages you choose to install have to be downloaded from somewhere, but at least you don't have to update the system directly after installation, saving yourself some hassle. If your network connection is cheap and fast, choose this image. <br />
{{Box Note | When choosing a pacman mirror during installation, keep in mind that archlinux.org is throttled to 50Kb/s.}}<br />
<br />
If you do not have a CD-ROM drive attached to your computer, you may refer to [[Install_from_USB_stick | this guide]] to install Arch Linux using a USB stick. If you do not have a USB stick, there are [[Hard_Disk_Installation | instructions]] for installing from a hard disk partition, such as a swap partition. If you want to use an existing distribution to install Arch Linux, please follow this [[Install_From_Existing_Linux | guide]].<br />
<br />
You can also purchase a cd online from OSDisc, shipping nearly<br />
world-wide.<br />
<br />
Using a dialup PPP connection to gain access to the internet during<br />
the install process is now supported. ppp utilities, rp-pppoe<br />
and the ISDN userspace utilities are included in the installation<br />
media.<br />
<br />
Since version 2007.08, isos are true live systems and run like any installed arch system.<br />
<br />
Some highlights: <br />
* pacman is included, to allow installation of any other needed packages for install environment.<br />
* complete /etc/rc.d/ and /etc/rc.conf support<br />
* complete Arch network support, including ssh,telnet and portmap services<br />
* custom config files support: any media with /config directory and files can be copied to /etc/ install environment<br />
* loading packages as addons during boot: any media with /packages directory including pacman packages can be installed during bootup.<br />
* '''links''' and '''naim''' included to be able to communicate over the internet.<br />
* complete kexec support<br />
<br />
If, during the installation process, you find you require a more verbose guide or explanation, you may also find the Arch Linux [[Beginners Guide]] helpful. <br />
<br />
What You Will Need<br />
<br />
* a working knowledge of GNU/Linux and the candidate machine's hardware<br />
* Arch Linux installation media (see the mirror list)<br />
* an i686 or x86-64 processor (PPro, Pentium 2 or higher, Athlon/Duron, etc. Note that AMD K6, Transmeta Crusoe, CyrixIII, and VIA-C3 are NOT supported.)<br />
* 160 MB RAM<br />
* some time to kill<br />
<br />
===Acquiring Arch Linux===<br />
<br />
You can download Arch Linux from any of the Arch Linux [http://www.archlinux.org/download/ mirrors]. Just follow the links into the "iso" directory and choose the version you wish to install. In general, you are advised to download the latest version as this helps avoid any difficulties during your initial update.<br />
<br />
===Preparing Installation Media===<br />
<br />
*Download <mirror>/iso/<your_architecture>/archlinux-<version>.iso (path relative to mirror root)<br />
*Download <mirror>/iso/<your_architecture>/md5sum-<version>.txt<br />
*Verify the integrity of the .iso image using md5sum:<br />
md5sum archlinux-<version>.iso<br />
*Burn the .iso image to a blank CD-R (this step varies depending on the OS/software you're using). If you want to download the core, ftp or a beta ISO instead, use the appropriate filename, ie: arch-0.8-core.iso instead of arch-0.8.iso, likewise for the md5sum.<br />
*Write down all your network settings so you can enter them into setup later, if you want to install via FTP:<br />
**IP Address<br />
**Subnet Mask<br />
**Gateway<br />
**Ethernet Module for your network card (eg.: eepro100, 8139too, ne2k-pci, etc.)<br />
<br />
===Using the CD-ROM===<br />
If you are familiar with the boot process, you may skip this <br />
explanation and continue with [[#Common Installation Procedure | Common Installation Procedure]], which outlines <br />
the actual process of installing Arch Linux.<br />
<br />
Reboot your computer with the Arch Linux Installation CD in the drive.<br />
Make sure your BIOS is configured to boot from your CD-ROM.<br />
Refer to your motherboard manual or system manufacturer documentation for<br />
details.<br />
<br />
At the end of the boot procedure, you shall be dropped into a root<br />
shell. At this point you are ready to commence the actual<br />
installation.<br />
<br />
===Common Installation Procedure===<br />
<br />
Installation Steps:<br />
<br />
#Loading a non-US Keymap<br />
#Running Setup<br />
#Configure Network (FTP Install only)<br />
#Prepare Hard Drive<br />
##Auto-Prepare<br />
##Partition Hard Drives<br />
##Set Filesystem Mountpoints<br />
#Select Packages<br />
#Install Packages<br />
#Configure System<br />
#Install Bootloader<br />
#Exit Install<br />
<br />
Using the available shell tools, experienced users are also able to<br />
prepare the hard drive or any devices needed for the installation<br />
before starting the installer. You may simply skip this paragraph if<br />
you don't see any immediate need for further manual interaction. Note<br />
that the Arch Linux installation media also contains a /arch/quickinst<br />
script for experienced users. This script installs the "base" set of<br />
packages to a user-specified destination directory. If you are doing<br />
an exotic install with fun things like RAID and LVM, or do not want to<br />
use the installer at all, you will probably want to use the quickinst<br />
script. All the cool kids are doing it.<br />
<br />
====Login and Loading a non-US Keymap====<br />
<br />
Login as 'root'. If you have a non-US keyboard layout do:<br />
km<br />
at the prompt.<br />
<br />
====Running Setup====<br />
<br />
Begin the installer script:<br />
/arch/setup<br />
After an informational message you will be prompted for the installation method<br />
of your choice. If you have a fast internet connection, you might<br />
prefer the FTP installation to ensure you get the latest packages<br />
instead of using the potentially outdated CD contents. <br />
<br />
When navigating the setup script, make sure to select DONE from<br />
the submenus after performing each step. This saves any settings you<br />
make in preparation for the next step. Further, avoid arbitrary steps<br />
throughout the installation process as this can also confuse the<br />
installer.<br />
<br />
It's actually rather easy to set up your own FTP package mirror or<br />
create your own bootable installation CD with the packages you need,<br />
making the task of installing several instances of Arch Linux across<br />
multiple machines rather simple, while at the same time saving a lot<br />
of mirror bandwidth. Make your life and ours easier, and look into<br />
these alternatives!<br />
<br />
When choosing a CD-ROM or OTHER SOURCE install you will only be able<br />
to install packages contained on the CD, which may be quite old, or<br />
packages stored on a medium you were able to mount (DVD, USB stick or<br />
similar) somewhere in the filesystem tree manually. Of course, it has<br />
the advantage of not needing an internet connection, and is therefore<br />
the recommended choice for dialup users or those unable or unwilling to download the entire package set via ftp.<br />
<br />
Next, you will be presented with the installer menu, listing the necessary steps in the order in which they should be completed.<br />
<br />
Virtual consoles 1-6 are active in the live environment. At any point in the install process, you can switch to your 5th virtual console (ALT-F5) to view the shell output from installer script. Use (ALT-F1) to get back to your first console where<br />
the installer is running.<br />
<br />
====Configure Network (FTP Install only)====<br />
<br />
Configure Network will allow you to install and configure your network<br />
device.<br />
<br />
A list of all currently available network devices is presented to you.<br />
If no ethernet device is available, load the necessary modules manually from another virtual console. Alternatively,<br />
you may probe for a network module on the following screen by selecting the Probe command. <br />
<br />
When the correct module is loaded, your network card will be<br />
listed. Select the ethernet device you wish to configure<br />
and you will be given the option to configure your network with DHCP.<br />
If you're connected to a DHCP server, hit YES and let the installer do<br />
the rest. If you select NO, you will be asked to enter the networking<br />
information manually.<br />
Either way, your network should be successfully configured, and if<br />
you're of the skeptical kind, you may check connectivity using<br />
standard tools like ping on another console.<br />
<br />
As automations are not perfect, you may not be able to successfully<br />
use the installer to set up your network. In these rare cases, set up you network device manually in one of the consoles.<br />
<br />
====Prepare Hard Drive====<br />
<br />
Prepare Hard Drive presents a submenu offering two<br />
alternatives of preparing the target drive for installation.<br />
<br />
The first choice is Auto-Prepare, which will automatically partition<br />
your hard drive into a /boot, swap, and root partition, and then<br />
create filesystems on all three. These partitions will also be<br />
automatically mounted in the proper place. To be exact, this option<br />
will create:<br />
* 32 MB ext2 /boot partition<br />
* 256 MB swap partition<br />
* root and /home partition with the remaining space. (Root and /home will share the same file system type if choosing the auto-prepare option).<br />
<br />
Actual sizes may vary slightly, due to different hard disk geometries.<br />
You can choose this option if you don't know much about hard drive<br />
partitions, but be warned:<br />
<br />
AUTO-PREPARE WILL ERASE ALL DATA ON THE CHOSEN HARD DRIVE!<br />
Read the warning presented by the installer very carefully, and make<br />
sure the correct device is about to be partitioned!<br />
<br />
A way to verify your choice for a device to partition would be to open<br />
another terminal (ALT-F2, Enter) and enter<br />
cfdisk -P s <name of device><br />
<br />
This will display the current partition table of the selected device,<br />
which should suffice to identify the hard disk.<br />
<br />
If you prefer to do the partitioning manually, use '''Partition Hard Drives''' and '''Set Filesystem Mountpoints''' to prepare the target media according to your specifications, as outlined below. After successful preparation, choose Return to Main Menu.<br />
<br />
====Partition Hard Drives====<br />
<br />
Partition Hard Drives should be skipped if you chose Auto-Prepare<br />
already!<br />
<br />
Otherwise you should select the disk(s) you want to partition, and<br />
you'll be dropped into the cfdisk program where you can freely modify<br />
the partitioning information until you [Write] and [Quit].<br />
<br />
You will need at least a root partition to continue the installation,<br />
and it's helpful to note somewhere which partition you're going to<br />
mount where, as you'll be asked exactly that in the next step.<br />
<br />
====Set Filesystem Mountpoints====<br />
<br />
Set Filesystem Mountpoints should also be skipped if you chose to<br />
Auto-Prepare your hard drive. You should select this option once the<br />
partition information is edited to your liking with the previous menu<br />
selection, or already existent through whatever other means.<br />
<br />
First, select the previously created swap partition from the list, or NONE, if you<br />
do not want to use a swap partition. Using a swap ''file'' is not directly<br />
supported by the installer; Instead choose NONE here, finish the<br />
mountpoint associations, and activate a swap file on your desired,<br />
formatted partition with the swapon command.<br />
<br />
After setting up the swap partition, you will be asked to specify the<br />
partition to be used as the root partition. This is mandatory.<br />
<br />
The association process is then repeated until you choose DONE from<br />
the list, ideally after all listed partitions have been associated<br />
with their intended mountpoints. The installer will suggest /boot for<br />
all following mountpoints after choosing swap and root.<br />
<br />
Each time a partition to mount is specified, you will be asked if you<br />
want to create a filesystem on the respective partition. Selecting<br />
YES, will prompt you for the filesystem type to create. The partition will then be<br />
formatted with the chosen filesystem type, destroying all data in the<br />
process. <br />
<br />
If additional mountpoints are desired, for example, a separate /boot or /home partition, you will be able to do so. Simply<br />
* select a partition to mount<br />
* choose a filesystem (if you want to create one instead of keeping existing data)<br />
* enter a unique mountpoint for the partition<br />
<br />
Repeat these steps until satisfied, then select DONE to create<br />
any filesystems and mount the partitions in their respective places.<br />
Before the actual formatting is done, the installer will present to<br />
you a list of all choices for review. After formatting and<br />
mounting all partitions, you may return to the Main Menu and proceed<br />
with the next step.<br />
<br />
===Select Packages===<br />
Now we shall select packages to install in our system.<br />
*Core ISO: Choose CD as source and select the appropriate CD drive if you have more than one.<br />
*FTP ISO: Select an FTP/HTTP mirror. ''Note that archlinux.org is throttled to 50KB/s''. ''Note also that some mirrors doesn't support resuming in case of download failure (e.g. ftp.free.fr)''<br />
<br />
The installer will always install a basic working system. You are given the option to install some basic development tools, such as GCC, autoconf, automake, make and some other useful packages such as openssh, sudo, iptable and some wifi packages.<br />
<br />
If you want to install any of the extra packages during the installation, you need to select the one and only package category '''BASE-DEVEL''' using the space bar.<br />
<br />
The next screen will present you with the selected packages within '''BASE-DEVEL'''.<br />
<br />
Once you're done selecting the packages you need, leave the selection<br />
screen and continue to the next step, Install Packages.<br />
<br />
====Install Packages====<br />
<br />
Install Packages will now install the base system and any other packages you<br />
selected with resolved dependencies onto your harddisk. Don't be<br />
surprised if more packages are installed than you selected! Those<br />
packages are dependencies for your selection, and the installer will<br />
not explicitly ask for permission to install these extra packages, as<br />
it assumes you know what you're doing.<br />
<br />
After the package selection, the installer will not check for free<br />
space on the target! This seemingly trivial task would eat up<br />
considerable time, and therefore the installer simply assumes to have<br />
enough free space on the target partition(s). In case it doesn't, the<br />
installation will fail in various funny ways. A df -h in another<br />
terminal might show that one or more of the targets mounted below /mnt<br />
have been filled up, causing mischief. Consider repartitioning or<br />
selecting a smaller set of packages.<br />
<br />
Error messages and debugging output is echoed to vc/5 (ALT-F5). After the packages have been installed, proceed to the next step, Configure System.<br />
<br />
Pacman will ask you whether it should keep the installed packages in cache. As you can delete them later using 'pacman -Scc', selecting 'yes' is recommended.<br />
<br />
==Configure System==<br />
<br />
Configure System allows you to edit the configuration files crucial<br />
for your newly installed system. Initially you will be asked whether<br />
to allow the hwdetect script to try and detect your hardware, and<br />
produce some (even more) sensible defaults for your configuration<br />
files. Unless you're having problems/crashes, you should let it have<br />
its way, and work from what it generates.<br />
<br />
Answer the following questions about RAID, LVM and encrypted volumes<br />
with Yes, if your root partition resides on a RAID, LVM or encrypted<br />
volume, respectively, to automatically add the necessary HOOKS to the<br />
mkinitcpio.conf. Otherwise you will get a kernel panic during boot, as<br />
your root partition will not be accessible at the time of boot. Most<br />
people will answer these questions with No, though, and not waste a<br />
second thought about it.<br />
<br />
After this automatic preconfiguration you'll be asked for your<br />
favourite editor to use for manually fine-tuning the generated<br />
configuration files, either VIM or nano. When in doubt, choose nano.<br />
<br />
===Configuration Files===<br />
These are the core configuration files for Arch Linux, to be configured with a text-editor. Only the most basic configuration<br />
files are listed here. If you need help configuring a specific<br />
service, please read the appropriate manpage or refer to any online<br />
documentation you need. In many cases, the Arch Linux Wiki and forums<br />
are a rich source for help as well.<br />
<br />
{{Box Note | Arch Linux does not use any abstraction layers to administrate your system. As a result, you can usually stick to any instructions published by the author of a particular software package, or whatever you find in a search engine of your choice, and it likely will work without confusing your system, because your system simply does not 'care'.}}<br />
<br />
'''List of Configuration Files'''<br />
* Setup-relevant configuration files:<br />
** /etc/rc.conf<br />
** /etc/hosts<br />
** [[Fstab | /etc/fstab]]<br />
** /etc/mkinitcpio.conf<br />
** /etc/modprobe.conf<br />
** /etc/resolv.conf<br />
** /etc/locale.gen<br />
** /boot/grub/menu.lst<br />
** /etc/lilo.conf<br />
* Additional configuration files:<br />
** /etc/conf.d/*<br />
** /etc/profile<br />
<br />
<br />
'''/etc/rc.conf'''<br />
<br />
This is the main configuration file for Arch Linux. It allows you to<br />
set your keyboard, timezone, hostname, network, daemons to run and<br />
modules to load at bootup, profiles, and more. You should read through<br />
all the settings in this file and make sure you understand them, and<br />
change them where appropriate:<br />
<br />
LOCALE<br />
This sets your system language, which will be used by all<br />
i18n-friendly applications and utilities. See locale.gen below<br />
for available options. This setting's default is fine for US <br />
English users.<br />
<br />
HARDWARECLOCK<br />
Either UTC if your BIOS clock is set to UTC, or localtime if<br />
your BIOS clock is set to your local time. If you have an OS<br />
installed which cannot handle UTC BIOS times correctly, like<br />
Windows, choose localtime here, otherwise you should prefer<br />
UTC, which makes daylight savings time a non-issue and has a<br />
few other positive aspects.<br />
<br />
TIMEZONE<br />
Specifies your time zone. Possible time zones are the relative<br />
path to a zoneinfo file starting from the directory<br />
/usr/share/zoneinfo. For example, a german timezone would be<br />
Europe/Berlin, which refers to the file<br />
/usr/share/zoneinfo/Europe/Berlin. If you don't know the exact<br />
name of your timezone file, worry about it later.<br />
<br />
KEYMAP<br />
Defines the keymap to load with the loadkeys program on bootup.<br />
Possible keymaps are found in /usr/share/kbd/keymaps. Please<br />
note that this setting is only valid for your TTYs, not any<br />
graphical window managers or X! Again, the default is fine for<br />
US users.<br />
<br />
CONSOLEFONT<br />
Defines the console font to load with the setfont program on<br />
bootup. Possible fonts are found in<br />
/usr/share/kbd/consolefonts.<br />
<br />
CONSOLEMAP<br />
Defines the console map to load with the setfont program on<br />
bootup. Possible maps are found in /usr/share/kbd/consoletrans.<br />
You will want to set this to a map suitable for your locale<br />
(8859-1 for Latin1, for example) if you're using an utf8 locale<br />
above, and use programs that generate 8-bit output. If you're<br />
using X11 for everyday work, don't bother, as it only affects<br />
the output of GNU/Linux console applications.<br />
<br />
USECOLOR<br />
Enable (or disable) colorized status messages during boot-up.<br />
<br />
MOD_AUTOLOAD<br />
If set to "yes", Arch will scan your hardware at bootup and<br />
attempt to automatically load the proper modules for your<br />
system. This is done with the hwdetect utility.<br />
<br />
MOD_BLACKLIST<br />
This is an array of modules that you do not want to be loaded<br />
at bootup. For example, if you don't want that annoying PC<br />
speaker, you could blacklist the pcspkr module.<br />
<br />
MODULES<br />
In this array you can list the names of modules you want to<br />
load during bootup without the need to bind them to a hardware<br />
device as in the modprobe.conf. Simply add the name of the<br />
module here, and put any options into the modprobe.conf if need<br />
be. Prepending a module with a bang ('!') will not load the<br />
module during bootup (this is not the same as MOD_BLACKLIST!),<br />
thus allowing to "comment out" certain modules if necessary. A<br />
benefit of specifying networking modules here is that ethernet<br />
cards covered by the listed modules will always be detected in<br />
the order the modules are listed. This prevents the dreaded<br />
interface confusion where your ethernet hardware is assigned to<br />
seemingly random interfaces after each boot. An even better way<br />
to handle this is using static interface labels by configuring<br />
udev appropriately, though.<br />
<br />
USELVM<br />
Set to "YES" to run a vgchange during sysinit, thus activating<br />
any LVM groups. If you have no idea what this means, don't<br />
bother.<br />
<br />
HOSTNAME<br />
Set this to the hostname of the machine, without the domain<br />
part. This is totally your choice, as long as you stick to<br />
letters, digits and a few common special characters like the<br />
dash. Don't be too creative here, though, and when in doubt,<br />
use the default.<br />
<br />
INTERFACES<br />
Here you define the settings for your networking interfaces.<br />
The default lines and the included comments explain the setup<br />
well enough. If you use DHCP, 'eth0="dhcp"' should work for you. If you do not use DHCP to configure a device, just<br />
keep in mind that the value of the variable (whose name must be<br />
equal to the name of the device which is supposed to be<br />
configured) equals the line which would be appended to the<br />
ifconfig command if you were to configure the device manually<br />
in the shell.<br />
<br />
ROUTES<br />
You can define your own static network routes with arbitrary<br />
names here. Look at the example for a default gateway to get<br />
the idea. Basically the quoted part is identical to what you'd<br />
pass to a manual route add command, therefore reading man route<br />
is recommended if you don't know what to write here, or simply<br />
leave this alone.<br />
<br />
[[Network_Profiles | NET_PROFILES]]<br />
Enables certain network profiles at bootup. Network profiles<br />
provide a convenient way of managing multiple network<br />
configurations, and are intended to replace the standard<br />
INTERFACES/ROUTES setup that is still recommended for systems<br />
with only one network configuration. If your computer will be<br />
participating in various networks at various times (eg, a<br />
laptop) then you should take a look at the<br />
/etc/network-profiles/ directory to set up some profiles. There<br />
is a template file included there that can be used to create<br />
new profiles.<br />
<br />
DAEMONS<br />
This array simply lists the names of those scripts contained in<br />
/etc/rc.d/ which are supposed to be started during the boot<br />
process, as well as the order in which they start. If a script name is prefixed with a bang (!), it is<br />
not executed. If a script is prefixed with an "at" symbol (@),<br />
then it will be executed in the background, ie. the startup<br />
sequence will not wait for successful completion before<br />
continuing. Usually you do not need to change the defaults to<br />
get a running system, but you are going to edit this array<br />
whenever you install system services like sshd, and want to<br />
start these automatically during bootup. This is basically<br />
Arch's way of handling what others handle with various symlinks<br />
to an init.d directory.<br />
<br />
<br />
'''/etc/hosts'''<br />
<br />
This is where you stick hostname/ip associations of computers on your<br />
network. If a hostname isn't known to your DNS, you can add it here to<br />
allow proper resolving, or override DNS replies. You usually don't<br />
need to change anything here, but you might want to add the hostname<br />
and hostname + domain of the local machine to this file, resolving to<br />
the IP of your network interface. Some services, postfix for example,<br />
will bomb otherwise. If you don't know what you're doing, leave this<br />
file alone until you read man hosts.<br />
<br />
<br />
'''[[Fstab | /etc/fstab]]'''<br />
<br />
Your filesystem settings and mountpoints are configured here. The<br />
installer should have created the necessary entries for you, but you<br />
should look over it and make sure it's right, especially when using an<br />
encrypted root device, LVM or RAID.<br />
<br />
With the current kernel, an important change has been introduced<br />
pertaining to the ATA/IDE subsystem. The new pata (Parallel ATA)<br />
drivers replace the legacy IDE subsystem, and one important change is<br />
that the naming scheme for IDE disks has changed from the old hda,<br />
hdb, etc. to also use device names of the type sda, sdb, etc, just<br />
like SCSI and SATA devices do. Because of this, when using the new<br />
pata driver in the HOOKS of the /etc/mkinitcpio.conf, remember to use<br />
the appropriate device names in your /etc/fstab and bootloader<br />
configuration! Alternatively, you could use the /dev/disk/by-uuid/...<br />
or /dev/disk/by-label/... representations of your disk drives where<br />
available to make absolutely sure you're referring to the right<br />
partitions, and save yourself the trouble of sorting out whether<br />
you're supposed to use sda or hda. If that's not an option, here's the<br />
rundown; If you're using pata instead of ide in the HOOKS array of the<br />
/etc/mkinitcpio.conf, you'll be using the sd? names. If not, use the<br />
old style hd? names. It is therefore crucial to check the HOOKS array<br />
in the /etc/mkinitcpio.conf, to be able to adapt the other files<br />
accordingly.<br />
<br />
<br />
'''/etc/mkinitcpio.conf'''<br />
<br />
This file allows you to fine-tune the initial ramdisk (also commonly<br />
referred to as the "initrd") for your system. The initrd is a gzipped<br />
image that is read by the kernel during bootup. The purpose of the<br />
initrd is to bootstrap the system to the point where it can access the<br />
root filesystem. This means it has to load any modules that are<br />
required to "see" things like IDE, SCSI, or SATA drives (or USB/FW, if<br />
you are booting off a USB/FW drive). Once the initrd loads the proper<br />
modules, either manually or through udev, it passes control to the<br />
Arch system and your bootup continues. For this reason, the initrd<br />
only needs to contain the modules necessary to access the root<br />
filesystem. It does not need to contain every module you would ever<br />
want to use. The majority of your everyday modules will be loaded<br />
later on by udev, during the init process.<br />
<br />
By default, mkinitcpio.conf is configured to provide all known modules<br />
for IDE, SCSI, or SATA systems through so-called HOOKS. This means the<br />
default initrd should work for almost everybody. The downside to this<br />
is that there are many modules loaded that you will not need. This is<br />
easily visible by examining your module table after booting up (with<br />
the lsmod command). While this doesn't actually hurt anything, some<br />
people find it annoying. To cull this list down to only what you<br />
actually need, you can edit mkinitcpio.conf and remove the subsystem<br />
HOOKS (ie, IDE, SCSI, RAID, USB, etc) that you don't need.<br />
<br />
You can customize even further by specifying the exact modules you<br />
need in the MODULES array and remove even more of the hooks, but take<br />
heed to the comments in the file, as this is a touchy place to go<br />
crazy with removing entries!<br />
<br />
If you're using RAID or encryption on your root filesystem, then<br />
you'll have to tweak the RAID/CRYPT settings near the bottom. See the<br />
wiki pages for RAID/LVM, filesystem encryption, and mkinitcpio for<br />
more info.<br />
<br />
When you're finished tweaking mkinitcpio.conf, you must run mkinitcpio<br />
-p kernel26 as root to regenerate the images, unless you're still<br />
installing the system; In that case this step will be done<br />
automatically after choosing Install Kernel later in the process.<br />
<br />
WARNING: If you fail to set up your mkinitcpio.conf correctly, your<br />
system will not boot! For this reason, you should be especially<br />
careful when tweaking this file.<br />
<br />
If you do manage to render your system unbootable, you can try using<br />
the fallback image that is installed alongside the stock kernel. A<br />
boot option for this is included in the default GRUB and LILO <br />
configuration.<br />
<br />
Read the warning about the pata transition problems elaborated in the<br />
fstab section carefully!<br />
<br />
<br />
'''/etc/modprobe.conf'''<br />
<br />
This tells the kernel which modules it needs to load for system<br />
devices, and what options to set. For example, to have the kernel load<br />
your Realtek 8139 ethernet module when it starts the network (ie.<br />
tries to setup eth0), use this line:<br />
alias eth0 8139too<br />
<br />
The syntax of this file is nearly identical to the old modules.conf<br />
scheme, unless you use some of the more exotic options like<br />
post-install. Then you should invest a little time into reading man<br />
modprobe.conf.<br />
<br />
Most people will not need to edit this file.<br />
<br />
<br />
'''/etc/resolv.conf'''<br />
<br />
Use this file to manually setup your nameserver(s) that you want to<br />
use. It should basically look like this:<br />
search domain.tld<br />
nameserver 192.168.0.1<br />
nameserver 192.168.0.2<br />
<br />
Replace domain.tld and the ip addresses with your settings. The<br />
so-called search domain specifies the default domain that is appended<br />
to unqualified hostnames automatically. By setting this, a ping myhost<br />
will effectively become a ping myhost.domain.tld with the above<br />
values. These settings usually aren't mighty important, though, and<br />
most people should leave them alone for now. If you use DHCP, this<br />
file will be replaced with the correct values automatically when<br />
networking is started, meaning you can and should happily ignore this<br />
file.<br />
<br />
<br />
'''/etc/locale.gen'''<br />
<br />
This file contains a list of all supported locales and charsets<br />
available to you. When choosing a LOCALE in your /etc/rc.conf or when<br />
starting a program, it is required to uncomment the respective locale<br />
in this file, to make a "compiled" version available to the system,<br />
and run the locale-gen command as root to generate all uncommented<br />
locales and put them in their place afterwards. You should uncomment<br />
all locales you intend to use.<br />
<br />
During the installation process, you do not need to run locale-gen<br />
manually, this will be taken care of automatically after saving your<br />
changes to this file.<br />
<br />
By default, all locales are commented out, including the default<br />
en_US.utf8 locale referred to in the /etc/rc.conf file. To make your<br />
system work smoothly, you must edit this file and uncomment at least<br />
the one locale you're using in your rc.conf.<br />
<br />
<br />
'''/boot/grub/menu.lst'''<br />
<br />
GRUB is the default bootloader for Arch Linux. You should check and<br />
modify this file to accommodate your boot setup if you want to use<br />
GRUB, otherwise read on about the LILO configuration.<br />
<br />
Make sure you read the warning regarding the pata transition<br />
elaborated on in the fstab section!<br />
<br />
Configuring GRUB is quite easy, the biggest hurdle is that it uses yet<br />
another device naming scheme different from /dev; Your hard disks as a<br />
whole are referred to as (hd0), (hd1), etc., sequentially numbered in<br />
order of appearance on the IDE/SCSI bus, just like the hda, hdb, etc.<br />
names in GNU/Linux. The partitions of a disk are referred to with (hd0,0),<br />
(hd0,1) and so on, with 0 meaning the first partition. A few<br />
conversion examples are included in the default menu.lst to aid your<br />
understanding.<br />
<br />
Once you grasped the concept of device naming, all you need to do is<br />
to choose a nice title for your boot section(s), supply the correct<br />
root partition device as a parameter to the root option to have it<br />
mounted as / on bootup, and create a kernel line that includes the<br />
partition and path where the kernel is located as well as any boot<br />
parameters. If using the stock Arch 2.6.x kernel, you'll also need an<br />
initrd line that points to the kernel26.img file in your /boot<br />
directory. The path you put on your initrd line should be the same as<br />
the path to vmlinuz26 that you provide on the kernel line. You should<br />
be fine with the defaults, just check whether the partition<br />
information is correct in the root and kernel lines, especially in<br />
regard to the pata issue!<br />
<br />
To create a boot option that loads the bootsector of a different OS,<br />
the following example might be helpful. You will probably succeed in<br />
starting any Microsoft-based operating system with it, just add this<br />
block to the file after any other sections, and modify the partition<br />
device accordingly to refer to the partition containing the bootsector<br />
of the OS you are intending to boot.<br />
(1) Other OS<br />
title My Other OS<br />
rootnoverify (hd0,1)<br />
makeactive<br />
chainloader +1<br />
<br />
For advanced configuration of other OSes, please refer to the online<br />
GRUB manual.<br />
<br />
After checking your bootloader configuration for correctness, you'll<br />
be prompted for a partition to install the loader to. Unless you're<br />
using yet another boot loader, you should install GRUB to the MBR of<br />
the installation disk, which is usually represented by the appropriate<br />
device name without a number suffix.<br />
<br />
<br />
'''/etc/lilo.conf'''<br />
<br />
This is the configuration file for the LILO bootloader. Make sure you<br />
check this one and get it right if you want to use LILO to boot your<br />
system. See LILO documentation for help on this.<br />
<br />
Things you should check are the root= lines in the image sections and<br />
the boot= line right at the beginning of the file. The root lines<br />
specify the device which shall be mounted as the root filesystem on<br />
bootup. If you don't know what is supposed to be entered here, change<br />
to another terminal and type mount to see a list of all currently<br />
mounted drives, and look for the line which displays a device name<br />
mounted on /mnt type [...]. The device path at the beginning of this<br />
very line should be entered in the root lines of your lilo.conf.<br />
Change if necessary, and keep the pata issue in mind!<br />
<br />
The boot line should be okay by default in most cases. Unless you have<br />
a weird boot manager setup in mind with multiple OSes, the device<br />
referenced here should be having the same prefix your root lines have,<br />
but not end with a number. For example, a root of /dev/hda3 means you<br />
probably want to install LILO into the Master Boot Record of the hard<br />
disk, so you would set boot to /dev/hda, which references the disk as<br />
a whole. During installation, the boot device must be the current name<br />
of the device where you want to write the boot sector to; This may<br />
differ from the name of the device after the first boot, thanks to the<br />
pata transition! Check carefully what device to write to during the<br />
installation stage, for example with the mount command.<br />
<br />
To prevent some serious grief, you should make sure you know how to<br />
restore the bootsector of your other OSes, for example with Windows's<br />
FIXBOOT/FIXMBR tools.<br />
<br />
To be on the safe side, you should keep the option lba32 listed. This<br />
will prevent some geometry issues from happening.<br />
<br />
In some cases, depending on your BIOS, LILO will not run on bootup and<br />
spill out an error code infinitely. In most cases you either removed<br />
the lba32 option, or your hardware setup is a little special, meaning<br />
that maybe your CD-ROM drive is primary master and the hard disk you<br />
installed secondary slave. This can very well confuse your BIOS, and<br />
thus stop the boot process. To prevent that you can try and make the<br />
install drive the primary master on your IDE bus. If you've got a<br />
mixed IDE and SCSI system and the problem persists, you'll probably<br />
need some experimentation with the disk and bios options of LILO to<br />
provide a working mapping; The disk drives in your system are numbered<br />
sequentially by your BIOS, starting with 0x80. If you're lucky your<br />
SCSI controller tells you which drive has which BIOS ID, but usually<br />
you're not. How the drives are effectively numbered is depending on<br />
your BIOS, so in the worst case you can only guess until it works. A<br />
typical disk line would look like this:<br />
boot=/dev/hda<br />
disk=/dev/hda bios=0x80<br />
<br />
The disk option maps a BIOS ID to the disk device known to the system. Note<br />
that there is still no guarantee that things will work as other things<br />
can be wrong, so do not despair if all your tries fail, but rather try<br />
rearranging your hardware in a way that's not totally odd. In this<br />
area too much can go wrong and needs special handling to be explained<br />
here. In most cases the lba32 option will suffice anyway. Old hard<br />
drives will usually need a little more special care until they do as<br />
told.<br />
<br />
Don't become fidgety when reading this section, I (Dennis) just<br />
happened to stumble over this problem when experimenting with a rather<br />
odd system, and figured it'd be a good idea to mention this show<br />
stopper and workarounds here. You probably won't ever experience this,<br />
as you should be using GRUB anyway.<br />
<br />
How to recreate a LILO boot sector with only a rescue disk is<br />
explained later in this document.<br />
<br />
<br />
'''/etc/conf.d/*'''<br />
<br />
During setup, this is totally unimportant. Consider this as reference<br />
for the interested.<br />
<br />
Some daemon scripts will have a matching configuration file in this<br />
directory that contains some more-or-less useful default values. When<br />
a daemon is started, it will first source the settings from its<br />
config file within this directory, and then source the /etc/rc.conf.<br />
This means you can easily centralize all your daemon configuration<br />
options in your /etc/rc.conf simply by setting an appropriate variable<br />
value, or split up your configuration over multiple files if you<br />
prefer a decentralized approach to this issue. Isn't life great if<br />
it's all just simple scripting?<br />
<br />
<br />
'''/etc/profile'''<br />
<br />
This script is run on each user login to initialize the system. It is<br />
kept quite simple under Arch Linux, as most things are. You may wish<br />
to edit or customize it to suit your needs.<br />
<br />
====Kernel====<br />
<br />
The CD-ROM includes the latest kernel available at time of release. If you are using the FTP<br />
Installation method, the kernel about to be installed will be the<br />
current version waiting on your FTP source, and might therefore<br />
introduce changes and/or incompatibilities unknown at the present<br />
time. This is unlikely, but keep it in mind.<br />
<br />
====Install Bootloader====<br />
<br />
Install Bootloader will install a bootloader on your hard drive,<br />
either GRUB (recommended) or LILO, depending on your personal<br />
preference.<br />
<br />
Before installing the bootloader, the setup script will want you to<br />
examine the appropriate configuration file to confirm the proper<br />
settings. <br />
<br />
If you choose to install LILO, the bootloader will be automatically<br />
installed according to your settings in the configuration file, whilst<br />
GRUB demands the selection of a partition to install the bootloader<br />
to. Here you should choose what you would enter as the boot option of<br />
LILO, which is usually the entry named /dev/hda, as it refers the<br />
master boot record of the first hard disk. Detailed error messages can<br />
be found as usual on VC5 (virtual console 5), if anything goes wrong.<br />
<br />
If you plan on setting up a multiboot system, you may wish to install the bootloader in your / or /boot partition, and<br />
refer to that boot sector from whatever other boot loader you want to<br />
reside in the master boot record. (chainloading)<br />
<br />
Installing a boot loader in the MBR will relentlessly overwrite any<br />
existing bootloader! Make sure you understand the implications of that<br />
if you're running a multiboot system, or want to preserve an installed<br />
bootloader from another OS!<br />
<br />
====Exit Install====<br />
<br />
Exit the Installer, eject the CD, and:<br />
reboot<br />
<br />
Login as root and add a user as outlined in the<br />
[[User_Management | User Management]] section, and set up your Internet Connection.<br />
<br />
Congratulations! Welcome to your new Arch Linux base system!<br />
<br />
==APPENDIX==<br />
===Adding a Window Manager/Desktop Environment===<br />
*[[KDE]] <br />
*[[KDEmod]]<br />
*[[GNOME]]<br />
*[[Xfce]]<br />
*[[Openbox]]<br />
*[[Wmii]]<br />
*[[Fluxbox]]<br />
*[[LXDE]]<br />
*[[E17]]<br />
*[[Xmonad]]<br />
See also [[.xinitrc]]<br />
<br />
===Boot Scripts===<br />
<br />
Arch Linux uses a fairly simple bootup sequence quite similar to *BSDs. The first boot script to run is /etc/rc.sysinit. When it's done, /etc/rc.multi will be called (in a normal bootup). The last script to run will be /etc/rc.local. When started in runlevel 1, the single user mode, the script /etc/rc.single is run instead of /etc/rc.multi. You will not find an endless symlink collection in the /etc/rc?.d/ directories to define the bootup sequence for all possible runlevels. In fact, due to this approach Arch only really has three runlevels, if you take starting up X in runlevel 5 into account. The boot scripts are using the variables and definitions found in the /etc/rc.conf file and also a set of general functions defined in the<br />
/etc/rc.d/functions script. If you plan to write your own daemon<br />
files, you should consider having a look at this file and existing<br />
daemon scripts.<br />
<br />
Boot Script Overview<br />
<br />
#/etc/rc.sysinit<br />
#/etc/rc.single<br />
#/etc/rc.multi<br />
#/etc/rc.local<br />
#/etc/rc.shutdown<br />
#/etc/rc.local.shutdown<br />
#/etc/rc.d/*<br />
<br />
<br />
'''/etc/rc.sysinit'''<br />
<br />
The main system boot script. It does boot-critical things like<br />
mounting filesystems, running udev, activating swap, loading modules,<br />
setting localization parameters, etc. You will most likely never need<br />
to edit this file!<br />
<br />
<br />
'''/etc/rc.single'''<br />
<br />
Single-user startup. Not used in a normal boot-up. If the system is<br />
started in single-user mode, for example with the kernel parameter 1<br />
before booting or during normal multi-user operation with the command<br />
init 1, this script makes sure no daemons are running except for the<br />
bare minimum; syslog-ng and udev. The single-user mode is useful if<br />
you need to make any changes to the system while making sure that no<br />
remote user can do anything that might cause data loss or damage.<br />
<br />
For desktop users, this mode usually is useless as crud. You should<br />
have no need to edit this script, either.<br />
<br />
<br />
'''/etc/rc.multi'''<br />
<br />
Multi-user startup script. It starts all daemons you configured in the<br />
DAEMONS array (set in /etc/rc.conf) after which it calls<br />
/etc/rc.local. You shouldn't feel a pressing need to edit this file.<br />
<br />
<br />
'''/etc/rc.local'''<br />
<br />
Local multi-user startup script. It is a good place to put any<br />
last-minute commands you want the system to run at the very end of the<br />
bootup process. This is finally the one and only script you should<br />
modify if needed, and you have total freedom on what to add to this<br />
script.<br />
<br />
Most common system configuration tasks, like loading modules, changing<br />
the console font or setting up devices, usually have a dedicated place<br />
where they belong. To avoid confusion, you should make sure that<br />
whatever you intend to add to your rc.local isn't feeling just as home<br />
in /etc/profile.d/ or any other already existant config location<br />
instead.<br />
<br />
<br />
'''/etc/rc.shutdown'''<br />
<br />
System shutdown script. It stops daemons, unmounts filesystems,<br />
deactivates the swap, etc. Just don't touch.<br />
<br />
<br />
'''/etc/rc.local.shutdown'''<br />
<br />
Analogous to the /etc/rc.local file, this file may contain any<br />
commands you want to run right before the common rc.shutdown is<br />
executed. Please note that this file does not exist by default, and<br />
for it to work properly, it must be set as executable.<br />
<br />
<br />
'''/etc/rc.d/*'''<br />
<br />
This directory contains the daemon scripts referred to from the<br />
rc.conf's DAEMONS array. In addition to being called on bootup, you<br />
can use these scripts when the system is running to manage the<br />
services of your system. For example the command<br />
/etc/rc.d/postfix stop<br />
<br />
will stop the postfix daemon. Of course a script only exists when the<br />
appropriate package has been installed (in this case postfix). With a<br />
basic system install, you don't have many scripts in here, but rest<br />
assured that all relevant daemon scripts end up here. This directory<br />
is pretty much the equivalent to the /etc/rc3.d/ or /etc/init.d/<br />
directories of other distributions, without all the symlink hassle.<br />
<br />
===User Management===<br />
<br />
Users and groups can be added and deleted with the standard commands<br />
provided in the util-linux package: useradd, userdel, groupadd,<br />
groupdel, passwd, and gpasswd. The typical way of adding a user is<br />
similar to this procedure:<br />
useradd -m -s /bin/bash johndoe<br />
passwd johndoe<br />
<br />
The first command will add the user named johndoe to the system,<br />
create a home directory for him at /home/johndoe, and place some<br />
default login files in his home directory. It will also set his login<br />
shell to be /bin/bash. The second command will ask you for a password<br />
for the johndoe user. A password is required to activate the account.<br />
<br />
As an alternative to the useradd command, the adduser script is also<br />
available to interactively create new users on your system simply by<br />
answering questions.<br />
<br />
See the manpages for more information on the remaining commands. It is<br />
a good idea to create one or multiple normal users for your day-to-day<br />
work to fully use the available security features and minimize<br />
potential damage that may be the result of using the root user for<br />
anything but system administration tasks.<br />
<br />
===Internet Access===<br />
<br />
Due to a lack of developers for dialup issues, connecting Arch to the<br />
Internet with a dialup line is requiring a lot of manual setup. If at<br />
all possible, set up a dedicated router which you can then use as a<br />
default gateway on the Arch box.<br />
<br />
There are quite a few dialup related documents in the Arch Linux Wiki<br />
<br />
====Analog Modem====<br />
<br />
To be able to use a Hayes-compatible, external, analog modem, you need<br />
to at least have the ppp package installed. Modify the file<br />
/etc/ppp/options to suit your needs and according to man pppd. You<br />
will need to define a chat script to supply your username and password<br />
to the ISP after the initial connection has been established. The<br />
manpages for pppd and chat have examples in them that should suffice<br />
to get a connection up and running if you're either experienced or<br />
stubborn enough. With udev, your serial ports usually are /dev/tts/0<br />
and /dev/tts/1.<br />
<br />
Instead of fighting a glorious battle with the plain pppd, you may opt<br />
to install wvdial or a similar tool to ease the setup process<br />
considerably.<br />
<br />
In case you're using a so called WinModem, which is basically a PCI<br />
plugin card working as an internal analog modem, you should indulge in<br />
the vast information found on the LinModem homepage.<br />
<br />
====ISDN====<br />
<br />
Setting up ISDN is done in three steps:<br />
#Install and configure hardware<br />
#Install and configure the ISDN utilities<br />
#Add settings for your ISP<br />
<br />
The current Arch stock kernels include the necessary ISDN modules,<br />
meaning that you won't need to recompile your kernel unless you're<br />
about to use rather odd or old ISDN hardware. After physically<br />
installing your ISDN card in your machine or plugging in your USB<br />
<br />
ISDN-Box, you can try loading the modules with modprobe. Nearly all<br />
passive ISDN PCI cards are handled by the hisax module which needs two<br />
parameters; type and protocol. You must set protocol to '1' if your<br />
country uses the 1TR6 standard, '2' if it uses EuroISDN (EDSS1), '3'<br />
if you're hooked to a so called leased-line without D-channel, and '4'<br />
for US NI1.<br />
<br />
Details on all those settings and how to set them is included in the<br />
kernel documentation, more specifically in the isdn subdirectory,<br />
available online. The type parameter depends on your card; A list of<br />
all possible types is to be found in the README.HiSax kernel<br />
documentation. Choose your card and load the module with the<br />
appropriate options like this:<br />
modprobe hisax type=18 protocol=2<br />
<br />
This will load the hisax module for my (Dennis) ELSA Quickstep<br />
1000PCI, being used in Germany with the EDSS1 protocol. You should<br />
find helpful debugging output in your /var/log/everything.log file in<br />
which you should see your card being prepared for action. Please note<br />
that you will probably need to load some usb modules before you can<br />
work with an external USB ISDN Adapter.<br />
<br />
Once you confirmed that your card works with certain settings, you can<br />
add the module options to your /etc/modprobe.conf:<br />
<br />
alias ippp0 hisax<br />
options hisax type=18 protocol=2<br />
<br />
Alternatively you can only add the options line here, and add hisax to<br />
your MODULES array in the rc.conf. Your choice, really, but this<br />
example has the advantage that the module will not be loaded until<br />
it's really needed.<br />
<br />
That being done you should have working, supported hardware. Now you<br />
need the basic utilities to actually use it!<br />
<br />
Install the isdn4k-utils package, and read the manpage to isdnctrl,<br />
it'll get you started. Further down in the manpage you will find<br />
explanations on how to create a configuration file that can be parsed<br />
by isdnctrl, as well as some helpful setup examples.<br />
<br />
Please note that you have to add your SPID to your MSN setting<br />
separated by a colon if you use US NI1.<br />
<br />
After you configured your ISDN card with the isdnctrl utility, you<br />
should be able to dial into the machine you specified with the<br />
PHONE_OUT parameter, but fail the username and password<br />
authentication. To make this work add your username and password to<br />
/etc/ppp/pap-secrets or /etc/ppp/chap-secrets as if you were<br />
configuring a normal analogous PPP link, depending on which protocol<br />
your ISP uses for authentication. If in doubt, put your data into both<br />
files.<br />
<br />
If you set up everything correctly, you should now be able to<br />
establish a dialup connection with isdnctrl dial ippp0 as root. If you<br />
have any problems, remember to check the logfiles!<br />
<br />
====DSL (PPPoE)====<br />
<br />
These instructions are only relevant to you if your PC itself is<br />
supposed to manage the connection to your ISP. You do not need to do<br />
anything but define a correct default gateway if you are using a<br />
separate router of some sort to do the grunt work.<br />
<br />
Before you can use your DSL online connection, you will have to<br />
physically install the network card that is supposed to be connected<br />
to the DSL-Modem into your computer. After adding your newly installed<br />
network card to the modprobe.conf or the MODULES array, you should<br />
install the rp-pppoe package and run the pppoe-setup script to<br />
configure your connection. After you have entered all required data,<br />
you can connect and disconnect your line with<br />
<br />
# /etc/rc.d/adsl start<br />
# /etc/rc.d/adsl stop<br />
<br />
respectively. The setup usually is rather easy and straightforward,<br />
but feel free to read the manpages for hints. If you want to<br />
automatically dial in on bootup, add adsl to your DAEMONS array,<br />
and put a ! before the network entry, since the network is handled<br />
by adsl now.<br />
<br />
==Package Management==<br />
<br />
===Pacman===<br />
<br />
[[pacman|Pacman]] is the package manager which tracks all the software installed<br />
on your system. It has simple dependency support and uses the standard<br />
gzipped tar archive format for all packages. Some common tasks are<br />
explained below with the respective commands in long and short option<br />
form. For an up to date explanation of pacman's options, read man<br />
pacman. This overview is merely scratching the surface of pacman's<br />
current capabilities.<br />
<br />
Typical tasks:<br />
<br />
====Adding/Upgrading a package with a package file====<br />
<br />
pacman --upgrade foo.pkg.tar.gz<br />
pacman -U foo.pkg.tar.gz<br />
<br />
This will install the foo.pkg.tar.gz package on the system. If<br />
dependencies are missing, pacman will exit with an error and report<br />
the missing deps, but not attempt to resolve the dependencies<br />
automatically. Look at the --sync option if you expect this<br />
functionality. Adding multiple package files is possible, and if the<br />
listed files depend on each other, the packages will be automatically<br />
installed in the correct order. This will additionally upgrade an already-installed package at no extra cost.<br />
<br />
====Removing packages====<br />
<br />
pacman --remove foo<br />
pacman -R foo<br />
<br />
This will remove all files belonging to the package named foo, except<br />
for configuration files that have been edited. Only supply the name of<br />
the package to this command, without the pkg.tar.gz suffix.<br />
<br />
To remove any and all trace of a package, add the --nosave option to<br />
the above command.<br />
<br />
====Refreshing the package list====<br />
<br />
pacman --sync --refresh<br />
pacman -Sy<br />
<br />
This will retrieve a fresh master package list from the repositories<br />
defined in the /etc/pacman.conf file and uncompress it into the<br />
database area. You should use this before using --sysupgrade to make<br />
sure you get the newest packages. Depending on your pacman.conf<br />
settings, this command may require a working internet connection to<br />
access FTP/HTTP-based repositories. This option is quite similar to<br />
Debian's apt-get update command.<br />
<br />
====Upgrading the system====<br />
<br />
pacman --sync --sysupgrade<br />
pacman -Su<br />
<br />
This command will upgrade all packages that are out-of-date on your<br />
system by comparing the local package version to the versions in the<br />
master package list that get downloaded with the --refresh command.<br />
It's a good idea to run this regularly to keep your system up to date.<br />
Note that this command does NOT implicitly refresh the master package<br />
list, so it's usually wiser to combine both commands into one like<br />
this:<br />
pacman --sync --refresh --sysupgrade<br />
pacman -Syu<br />
<br />
With these options pacman will automatically retrieve the current<br />
master package list and do a full system upgrade to the latest<br />
packages with all dependencies being automagically resolved. You will<br />
want to run this quite often.<br />
<br />
====Adding/Upgrading a package from the repositories====<br />
<br />
pacman --sync foo<br />
pacman -S foo<br />
<br />
Retrieve and install package foo, complete with all dependencies it<br />
requires. Before using any sync option, make sure you refreshed the<br />
package list, or add --refresh or -y to the options to do it before<br />
the installation attempt. Unlike --add, the --sync option does not<br />
differ between installing and upgrading packages. Depending on your<br />
pacman.conf settings this function requires working internet access.<br />
<br />
Receiving strange errors when downloading packages from the server,<br />
ie. broken downloads or files that aren't found, usually are either<br />
caused by not refreshing the package list with --sync, or if you're<br />
unlucky enough to try downloading from a mirror while it's syncing<br />
its contents, and is thus in an inconsistent state.<br />
<br />
====Searching for packages====<br />
<br />
pacman -Ss foo<br />
<br />
Search for package foo.</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Newcomers_Guide&diff=58746
Newcomers Guide
2009-01-21T15:52:24Z
<p>Zaggynl: Removing all content from page</p>
<hr />
<div></div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Newcomers_Guide&diff=58745
Newcomers Guide
2009-01-21T15:52:03Z
<p>Zaggynl: </p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{Article summary start}}<br />
{{Article summary text|General installation documentation for the Arch Linux distribution.}}<br />
{{Article summary heading|Available Languages}}<br />
{{i18n_entry|English|Official Arch Linux Install Guide}}<br />
{{i18n_entry|&#31616;&#20307;&#20013;&#25991;|Arch Linux &#23448;&#26041;&#23433;&#35013;&#25351;&#21335;}}<br />
{{i18n_entry|&#27491;&#39636;&#20013;&#25991;|Arch Linux &#23448;&#26041;&#23433;&#35037;&#25351;&#21335;}}<br />
{{i18n_entry|&#268;esky|Oficiální instala&#269;ní p&#345;íru&#269;ka (&#268;esky)}}<br />
{{i18n_entry|&#1056;&#1091;&#1089;&#1089;&#1082;&#1080;&#1081;|&#1056;&#1091;&#1082;&#1086;&#1074;&#1086;&#1076;&#1089;&#1090;&#1074;&#1086; &#1087;&#1086; &#1091;&#1089;&#1090;&#1072;&#1085;&#1086;&#1074;&#1082;&#1077;}}<br />
{{i18n_entry|Español|Guía oficial de Instalación}}<br />
{{i18n_entry|Italiano|Official Arch Linux Install Guide (Italiano)}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|Beginners Guide}} (If you are new to Arch)<br />
{{Article summary end}}<br />
<br />
<br />
==Introduction==<br />
<br />
===What is Arch Linux?===<br />
<br />
Arch Linux is an independently developed i686/x86-64-optimized GNU/Linux distribution. Development is focused on a balance of simplicity, elegance, code-correctness and bleeding edge software.<br />
<br />
The Arch system and binary packages are compiled for i686 or x86-64 processors. Its lightweight and simple design makes it easy to extend and mold into whatever kind of system you're building.<br />
<br />
===License===<br />
<br />
Arch Linux, pacman, documentation, and scripts are copyright<br />
©2002-2007 by Judd Vinet, ©2007-2008 by Aaron Griffin and are licensed under the GNU General Public License Version 2.<br />
<br />
==Installing Arch Linux==<br />
<br />
===Pre-Installation===<br />
<br />
Arch Linux is optimized for the i686 processor and therefore will not<br />
run on any lower or incompatible generations of x86 CPUs<br />
(i386,i486,i586). A Pentium II or AMD Athlon processor or higher is<br />
required. Modern VIA C3 processors are also supported. x86-64 architectures are also officially supported.<br />
<br />
There is a community-driven project that provides packages for i586<br />
and ppc. See this site for more information.<br />
<br />
Before installing Arch Linux, you should decide which installation<br />
method you would like to use. Arch Linux provides two different<br />
bootable ISO images for a CD-ROM installation. Installing Arch from a USB stick or from within another already installed OS is also supported.<br />
<br />
As the preferred method of installation is the flexible CD-ROM based<br />
installation, we offer you two variants of the installation medium<br />
which only differ in terms of supplied packages. You can instruct the<br />
installer to obtain the packages via FTP using any of these images,<br />
and all images can also be used as fully functional live cds.<br />
<br />
* The core iso (~300MB) is a live environment which contains a snapshot of the entire /core repository. Packages are divided into 4 categories: BASE, SUPPORT, DEVEL and LIB. RAID/LVM are fully supported; all necessary packages are included within /core. Installing from a medium created with this image results in a completely functional GNU/Linux system, without any frills, expecting to be used from the command line; the Linux kernel, GNU toolchain and a few extra modules and libraries. This image is ideally suited for those who have a rather slow or nonexistent internet connection on the candidate machine, making an FTP install unfeasible. The name of the iso will be "archlinux-i686-2008.xx-x.core.iso", according to your architecture<br />
* The FTP iso (~175MB) is a live environment, containing no packages at all, but rather pulls in all software over your internet connection. If you have access to a fast and easily setup internet connection, this method may be preferred, since the completed system will be completely up-to-date, without requiring further upgrades from the package versions included on the Core CD. Of course all packages you choose to install have to be downloaded from somewhere, but at least you don't have to update the system directly after installation, saving yourself some hassle. If your network connection is cheap and fast, choose this image. <br />
{{Box Note | When choosing a pacman mirror during installation, keep in mind that archlinux.org is throttled to 50Kb/s.}}<br />
<br />
If you do not have a CD-ROM drive attached to your computer, you may refer to [[Install_from_USB_stick | this guide]] to install Arch Linux using a USB stick. If you do not have a USB stick, there are [[Hard_Disk_Installation | instructions]] for installing from a hard disk partition, such as a swap partition. If you want to use an existing distribution to install Arch Linux, please follow this [[Install_From_Existing_Linux | guide]].<br />
<br />
You can also purchase a cd online from OSDisc, shipping nearly<br />
world-wide.<br />
<br />
Using a dialup PPP connection to gain access to the internet during<br />
the install process is now supported. ppp utilities, rp-pppoe<br />
and the ISDN userspace utilities are included in the installation<br />
media.<br />
<br />
Since version 2007.08, isos are true live systems and run like any installed arch system.<br />
<br />
Some highlights: <br />
* pacman is included, to allow installation of any other needed packages for install environment.<br />
* complete /etc/rc.d/ and /etc/rc.conf support<br />
* complete Arch network support, including ssh,telnet and portmap services<br />
* custom config files support: any media with /config directory and files can be copied to /etc/ install environment<br />
* loading packages as addons during boot: any media with /packages directory including pacman packages can be installed during bootup.<br />
* '''links''' and '''naim''' included to be able to communicate over the internet.<br />
* complete kexec support<br />
<br />
If, during the installation process, you find you require a more verbose guide or explanation, you may also find the Arch Linux [[Beginners Guide]] helpful. <br />
<br />
What You Will Need<br />
<br />
* a working knowledge of GNU/Linux and the candidate machine's hardware<br />
* Arch Linux installation media (see the mirror list)<br />
* an i686 or x86-64 processor (PPro, Pentium 2 or higher, Athlon/Duron, etc. Note that AMD K6, Transmeta Crusoe, CyrixIII, and VIA-C3 are NOT supported.)<br />
* 160 MB RAM<br />
* some time to kill<br />
<br />
===Acquiring Arch Linux===<br />
<br />
You can download Arch Linux from any of the Arch Linux [http://www.archlinux.org/download/ mirrors]. Just follow the links into the "iso" directory and choose the version you wish to install. In general, you are advised to download the latest version as this helps avoid any difficulties during your initial update.<br />
<br />
===Preparing Installation Media===<br />
<br />
*Download <mirror>/iso/<your_architecture>/archlinux-<version>.iso (path relative to mirror root)<br />
*Download <mirror>/iso/<your_architecture>/md5sum-<version>.txt<br />
*Verify the integrity of the .iso image using md5sum:<br />
md5sum archlinux-<version>.iso<br />
*Burn the .iso image to a blank CD-R (this step varies depending on the OS/software you're using). If you want to download the core, ftp or a beta ISO instead, use the appropriate filename, ie: arch-0.8-core.iso instead of arch-0.8.iso, likewise for the md5sum.<br />
*Write down all your network settings so you can enter them into setup later, if you want to install via FTP:<br />
**IP Address<br />
**Subnet Mask<br />
**Gateway<br />
**Ethernet Module for your network card (eg.: eepro100, 8139too, ne2k-pci, etc.)<br />
<br />
===Using the CD-ROM===<br />
If you are familiar with the boot process, you may skip this <br />
explanation and continue with [[#Common Installation Procedure | Common Installation Procedure]], which outlines <br />
the actual process of installing Arch Linux.<br />
<br />
Reboot your computer with the Arch Linux Installation CD in the drive.<br />
Make sure your BIOS is configured to boot from your CD-ROM.<br />
Refer to your motherboard manual or system manufacturer documentation for<br />
details.<br />
<br />
At the end of the boot procedure, you shall be dropped into a root<br />
shell. At this point you are ready to commence the actual<br />
installation.<br />
<br />
===Common Installation Procedure===<br />
<br />
Installation Steps:<br />
<br />
#Loading a non-US Keymap<br />
#Running Setup<br />
#Configure Network (FTP Install only)<br />
#Prepare Hard Drive<br />
##Auto-Prepare<br />
##Partition Hard Drives<br />
##Set Filesystem Mountpoints<br />
#Select Packages<br />
#Install Packages<br />
#Configure System<br />
#Install Bootloader<br />
#Exit Install<br />
<br />
Using the available shell tools, experienced users are also able to<br />
prepare the hard drive or any devices needed for the installation<br />
before starting the installer. You may simply skip this paragraph if<br />
you don't see any immediate need for further manual interaction. Note<br />
that the Arch Linux installation media also contains a /arch/quickinst<br />
script for experienced users. This script installs the "base" set of<br />
packages to a user-specified destination directory. If you are doing<br />
an exotic install with fun things like RAID and LVM, or do not want to<br />
use the installer at all, you will probably want to use the quickinst<br />
script. All the cool kids are doing it.<br />
<br />
====Login and Loading a non-US Keymap====<br />
<br />
Login as 'root'. If you have a non-US keyboard layout do:<br />
km<br />
at the prompt.<br />
<br />
====Running Setup====<br />
<br />
Begin the installer script:<br />
/arch/setup<br />
After an informational message you will be prompted for the installation method<br />
of your choice. If you have a fast internet connection, you might<br />
prefer the FTP installation to ensure you get the latest packages<br />
instead of using the potentially outdated CD contents. <br />
<br />
When navigating the setup script, make sure to select DONE from<br />
the submenus after performing each step. This saves any settings you<br />
make in preparation for the next step. Further, avoid arbitrary steps<br />
throughout the installation process as this can also confuse the<br />
installer.<br />
<br />
It's actually rather easy to set up your own FTP package mirror or<br />
create your own bootable installation CD with the packages you need,<br />
making the task of installing several instances of Arch Linux across<br />
multiple machines rather simple, while at the same time saving a lot<br />
of mirror bandwidth. Make your life and ours easier, and look into<br />
these alternatives!<br />
<br />
When choosing a CD-ROM or OTHER SOURCE install you will only be able<br />
to install packages contained on the CD, which may be quite old, or<br />
packages stored on a medium you were able to mount (DVD, USB stick or<br />
similar) somewhere in the filesystem tree manually. Of course, it has<br />
the advantage of not needing an internet connection, and is therefore<br />
the recommended choice for dialup users or those unable or unwilling to download the entire package set via ftp.<br />
<br />
Next, you will be presented with the installer menu, listing the necessary steps in the order in which they should be completed.<br />
<br />
Virtual consoles 1-6 are active in the live environment. At any point in the install process, you can switch to your 5th virtual console (ALT-F5) to view the shell output from installer script. Use (ALT-F1) to get back to your first console where<br />
the installer is running.<br />
<br />
====Configure Network (FTP Install only)====<br />
<br />
Configure Network will allow you to install and configure your network<br />
device.<br />
<br />
A list of all currently available network devices is presented to you.<br />
If no ethernet device is available, load the necessary modules manually from another virtual console. Alternatively,<br />
you may probe for a network module on the following screen by selecting the Probe command. <br />
<br />
When the correct module is loaded, your network card will be<br />
listed. Select the ethernet device you wish to configure<br />
and you will be given the option to configure your network with DHCP.<br />
If you're connected to a DHCP server, hit YES and let the installer do<br />
the rest. If you select NO, you will be asked to enter the networking<br />
information manually.<br />
Either way, your network should be successfully configured, and if<br />
you're of the skeptical kind, you may check connectivity using<br />
standard tools like ping on another console.<br />
<br />
As automations are not perfect, you may not be able to successfully<br />
use the installer to set up your network. In these rare cases, set up you network device manually in one of the consoles.<br />
<br />
====Prepare Hard Drive====<br />
<br />
Prepare Hard Drive presents a submenu offering two<br />
alternatives of preparing the target drive for installation.<br />
<br />
The first choice is Auto-Prepare, which will automatically partition<br />
your hard drive into a /boot, swap, and root partition, and then<br />
create filesystems on all three. These partitions will also be<br />
automatically mounted in the proper place. To be exact, this option<br />
will create:<br />
* 32 MB ext2 /boot partition<br />
* 256 MB swap partition<br />
* root and /home partition with the remaining space. (Root and /home will share the same file system type if choosing the auto-prepare option).<br />
<br />
Actual sizes may vary slightly, due to different hard disk geometries.<br />
You can choose this option if you don't know much about hard drive<br />
partitions, but be warned:<br />
<br />
AUTO-PREPARE WILL ERASE ALL DATA ON THE CHOSEN HARD DRIVE!<br />
Read the warning presented by the installer very carefully, and make<br />
sure the correct device is about to be partitioned!<br />
<br />
A way to verify your choice for a device to partition would be to open<br />
another terminal (ALT-F2, Enter) and enter<br />
cfdisk -P s <name of device><br />
<br />
This will display the current partition table of the selected device,<br />
which should suffice to identify the hard disk.<br />
<br />
If you prefer to do the partitioning manually, use '''Partition Hard Drives''' and '''Set Filesystem Mountpoints''' to prepare the target media according to your specifications, as outlined below. After successful preparation, choose Return to Main Menu.<br />
<br />
====Partition Hard Drives====<br />
<br />
Partition Hard Drives should be skipped if you chose Auto-Prepare<br />
already!<br />
<br />
Otherwise you should select the disk(s) you want to partition, and<br />
you'll be dropped into the cfdisk program where you can freely modify<br />
the partitioning information until you [Write] and [Quit].<br />
<br />
You will need at least a root partition to continue the installation,<br />
and it's helpful to note somewhere which partition you're going to<br />
mount where, as you'll be asked exactly that in the next step.<br />
<br />
====Set Filesystem Mountpoints====<br />
<br />
Set Filesystem Mountpoints should also be skipped if you chose to<br />
Auto-Prepare your hard drive. You should select this option once the<br />
partition information is edited to your liking with the previous menu<br />
selection, or already existent through whatever other means.<br />
<br />
First, select the previously created swap partition from the list, or NONE, if you<br />
do not want to use a swap partition. Using a swap ''file'' is not directly<br />
supported by the installer; Instead choose NONE here, finish the<br />
mountpoint associations, and activate a swap file on your desired,<br />
formatted partition with the swapon command.<br />
<br />
After setting up the swap partition, you will be asked to specify the<br />
partition to be used as the root partition. This is mandatory.<br />
<br />
The association process is then repeated until you choose DONE from<br />
the list, ideally after all listed partitions have been associated<br />
with their intended mountpoints. The installer will suggest /boot for<br />
all following mountpoints after choosing swap and root.<br />
<br />
Each time a partition to mount is specified, you will be asked if you<br />
want to create a filesystem on the respective partition. Selecting<br />
YES, will prompt you for the filesystem type to create. The partition will then be<br />
formatted with the chosen filesystem type, destroying all data in the<br />
process. <br />
<br />
If additional mountpoints are desired, for example, a separate /boot or /home partition, you will be able to do so. Simply<br />
* select a partition to mount<br />
* choose a filesystem (if you want to create one instead of keeping existing data)<br />
* enter a unique mountpoint for the partition<br />
<br />
Repeat these steps until satisfied, then select DONE to create<br />
any filesystems and mount the partitions in their respective places.<br />
Before the actual formatting is done, the installer will present to<br />
you a list of all choices for review. After formatting and<br />
mounting all partitions, you may return to the Main Menu and proceed<br />
with the next step.<br />
<br />
===Select Packages===<br />
Now we shall select packages to install in our system.<br />
*Core ISO: Choose CD as source and select the appropriate CD drive if you have more than one.<br />
*FTP ISO: Select an FTP/HTTP mirror. ''Note that archlinux.org is throttled to 50KB/s''. ''Note also that some mirrors doesn't support resuming in case of download failure (e.g. ftp.free.fr)''<br />
<br />
The installer will always install a basic working system. You are given the option to install some basic development tools, such as GCC, autoconf, automake, make and some other useful packages such as openssh, sudo, iptable and some wifi packages.<br />
<br />
If you want to install any of the extra packages during the installation, you need to select the one and only package category '''BASE-DEVEL''' using the space bar.<br />
<br />
The next screen will present you with the selected packages within '''BASE-DEVEL'''.<br />
<br />
Once you're done selecting the packages you need, leave the selection<br />
screen and continue to the next step, Install Packages.<br />
<br />
====Install Packages====<br />
<br />
Install Packages will now install the base system and any other packages you<br />
selected with resolved dependencies onto your harddisk. Don't be<br />
surprised if more packages are installed than you selected! Those<br />
packages are dependencies for your selection, and the installer will<br />
not explicitly ask for permission to install these extra packages, as<br />
it assumes you know what you're doing.<br />
<br />
After the package selection, the installer will not check for free<br />
space on the target! This seemingly trivial task would eat up<br />
considerable time, and therefore the installer simply assumes to have<br />
enough free space on the target partition(s). In case it doesn't, the<br />
installation will fail in various funny ways. A df -h in another<br />
terminal might show that one or more of the targets mounted below /mnt<br />
have been filled up, causing mischief. Consider repartitioning or<br />
selecting a smaller set of packages.<br />
<br />
Error messages and debugging output is echoed to vc/5 (ALT-F5). After the packages have been installed, proceed to the next step, Configure System.<br />
<br />
Pacman will ask you whether it should keep the installed packages in cache. As you can delete them later using 'pacman -Scc', selecting 'yes' is recommended.<br />
<br />
==Configure System==<br />
<br />
Configure System allows you to edit the configuration files crucial<br />
for your newly installed system. Initially you will be asked whether<br />
to allow the hwdetect script to try and detect your hardware, and<br />
produce some (even more) sensible defaults for your configuration<br />
files. Unless you're having problems/crashes, you should let it have<br />
its way, and work from what it generates.<br />
<br />
Answer the following questions about RAID, LVM and encrypted volumes<br />
with Yes, if your root partition resides on a RAID, LVM or encrypted<br />
volume, respectively, to automatically add the necessary HOOKS to the<br />
mkinitcpio.conf. Otherwise you will get a kernel panic during boot, as<br />
your root partition will not be accessible at the time of boot. Most<br />
people will answer these questions with No, though, and not waste a<br />
second thought about it.<br />
<br />
After this automatic preconfiguration you'll be asked for your<br />
favourite editor to use for manually fine-tuning the generated<br />
configuration files, either VIM or nano. When in doubt, choose nano.<br />
<br />
===Configuration Files===<br />
These are the core configuration files for Arch Linux, to be configured with a text-editor. Only the most basic configuration<br />
files are listed here. If you need help configuring a specific<br />
service, please read the appropriate manpage or refer to any online<br />
documentation you need. In many cases, the Arch Linux Wiki and forums<br />
are a rich source for help as well.<br />
<br />
{{Box Note | Arch Linux does not use any abstraction layers to administrate your system. As a result, you can usually stick to any instructions published by the author of a particular software package, or whatever you find in a search engine of your choice, and it likely will work without confusing your system, because your system simply does not 'care'.}}<br />
<br />
'''List of Configuration Files'''<br />
* Setup-relevant configuration files:<br />
** /etc/rc.conf<br />
** /etc/hosts<br />
** [[Fstab | /etc/fstab]]<br />
** /etc/mkinitcpio.conf<br />
** /etc/modprobe.conf<br />
** /etc/resolv.conf<br />
** /etc/locale.gen<br />
** /boot/grub/menu.lst<br />
** /etc/lilo.conf<br />
* Additional configuration files:<br />
** /etc/conf.d/*<br />
** /etc/profile<br />
<br />
<br />
'''/etc/rc.conf'''<br />
<br />
This is the main configuration file for Arch Linux. It allows you to<br />
set your keyboard, timezone, hostname, network, daemons to run and<br />
modules to load at bootup, profiles, and more. You should read through<br />
all the settings in this file and make sure you understand them, and<br />
change them where appropriate:<br />
<br />
LOCALE<br />
This sets your system language, which will be used by all<br />
i18n-friendly applications and utilities. See locale.gen below<br />
for available options. This setting's default is fine for US <br />
English users.<br />
<br />
HARDWARECLOCK<br />
Either UTC if your BIOS clock is set to UTC, or localtime if<br />
your BIOS clock is set to your local time. If you have an OS<br />
installed which cannot handle UTC BIOS times correctly, like<br />
Windows, choose localtime here, otherwise you should prefer<br />
UTC, which makes daylight savings time a non-issue and has a<br />
few other positive aspects.<br />
<br />
TIMEZONE<br />
Specifies your time zone. Possible time zones are the relative<br />
path to a zoneinfo file starting from the directory<br />
/usr/share/zoneinfo. For example, a german timezone would be<br />
Europe/Berlin, which refers to the file<br />
/usr/share/zoneinfo/Europe/Berlin. If you don't know the exact<br />
name of your timezone file, worry about it later.<br />
<br />
KEYMAP<br />
Defines the keymap to load with the loadkeys program on bootup.<br />
Possible keymaps are found in /usr/share/kbd/keymaps. Please<br />
note that this setting is only valid for your TTYs, not any<br />
graphical window managers or X! Again, the default is fine for<br />
US users.<br />
<br />
CONSOLEFONT<br />
Defines the console font to load with the setfont program on<br />
bootup. Possible fonts are found in<br />
/usr/share/kbd/consolefonts.<br />
<br />
CONSOLEMAP<br />
Defines the console map to load with the setfont program on<br />
bootup. Possible maps are found in /usr/share/kbd/consoletrans.<br />
You will want to set this to a map suitable for your locale<br />
(8859-1 for Latin1, for example) if you're using an utf8 locale<br />
above, and use programs that generate 8-bit output. If you're<br />
using X11 for everyday work, don't bother, as it only affects<br />
the output of GNU/Linux console applications.<br />
<br />
USECOLOR<br />
Enable (or disable) colorized status messages during boot-up.<br />
<br />
MOD_AUTOLOAD<br />
If set to "yes", Arch will scan your hardware at bootup and<br />
attempt to automatically load the proper modules for your<br />
system. This is done with the hwdetect utility.<br />
<br />
MOD_BLACKLIST<br />
This is an array of modules that you do not want to be loaded<br />
at bootup. For example, if you don't want that annoying PC<br />
speaker, you could blacklist the pcspkr module.<br />
<br />
MODULES<br />
In this array you can list the names of modules you want to<br />
load during bootup without the need to bind them to a hardware<br />
device as in the modprobe.conf. Simply add the name of the<br />
module here, and put any options into the modprobe.conf if need<br />
be. Prepending a module with a bang ('!') will not load the<br />
module during bootup (this is not the same as MOD_BLACKLIST!),<br />
thus allowing to "comment out" certain modules if necessary. A<br />
benefit of specifying networking modules here is that ethernet<br />
cards covered by the listed modules will always be detected in<br />
the order the modules are listed. This prevents the dreaded<br />
interface confusion where your ethernet hardware is assigned to<br />
seemingly random interfaces after each boot. An even better way<br />
to handle this is using static interface labels by configuring<br />
udev appropriately, though.<br />
<br />
USELVM<br />
Set to "YES" to run a vgchange during sysinit, thus activating<br />
any LVM groups. If you have no idea what this means, don't<br />
bother.<br />
<br />
HOSTNAME<br />
Set this to the hostname of the machine, without the domain<br />
part. This is totally your choice, as long as you stick to<br />
letters, digits and a few common special characters like the<br />
dash. Don't be too creative here, though, and when in doubt,<br />
use the default.<br />
<br />
INTERFACES<br />
Here you define the settings for your networking interfaces.<br />
The default lines and the included comments explain the setup<br />
well enough. If you use DHCP, 'eth0="dhcp"' should work for you. If you do not use DHCP to configure a device, just<br />
keep in mind that the value of the variable (whose name must be<br />
equal to the name of the device which is supposed to be<br />
configured) equals the line which would be appended to the<br />
ifconfig command if you were to configure the device manually<br />
in the shell.<br />
<br />
ROUTES<br />
You can define your own static network routes with arbitrary<br />
names here. Look at the example for a default gateway to get<br />
the idea. Basically the quoted part is identical to what you'd<br />
pass to a manual route add command, therefore reading man route<br />
is recommended if you don't know what to write here, or simply<br />
leave this alone.<br />
<br />
[[Network_Profiles | NET_PROFILES]]<br />
Enables certain network profiles at bootup. Network profiles<br />
provide a convenient way of managing multiple network<br />
configurations, and are intended to replace the standard<br />
INTERFACES/ROUTES setup that is still recommended for systems<br />
with only one network configuration. If your computer will be<br />
participating in various networks at various times (eg, a<br />
laptop) then you should take a look at the<br />
/etc/network-profiles/ directory to set up some profiles. There<br />
is a template file included there that can be used to create<br />
new profiles.<br />
<br />
DAEMONS<br />
This array simply lists the names of those scripts contained in<br />
/etc/rc.d/ which are supposed to be started during the boot<br />
process, as well as the order in which they start. If a script name is prefixed with a bang (!), it is<br />
not executed. If a script is prefixed with an "at" symbol (@),<br />
then it will be executed in the background, ie. the startup<br />
sequence will not wait for successful completion before<br />
continuing. Usually you do not need to change the defaults to<br />
get a running system, but you are going to edit this array<br />
whenever you install system services like sshd, and want to<br />
start these automatically during bootup. This is basically<br />
Arch's way of handling what others handle with various symlinks<br />
to an init.d directory.<br />
<br />
<br />
'''/etc/hosts'''<br />
<br />
This is where you stick hostname/ip associations of computers on your<br />
network. If a hostname isn't known to your DNS, you can add it here to<br />
allow proper resolving, or override DNS replies. You usually don't<br />
need to change anything here, but you might want to add the hostname<br />
and hostname + domain of the local machine to this file, resolving to<br />
the IP of your network interface. Some services, postfix for example,<br />
will bomb otherwise. If you don't know what you're doing, leave this<br />
file alone until you read man hosts.<br />
<br />
<br />
'''[[Fstab | /etc/fstab]]'''<br />
<br />
Your filesystem settings and mountpoints are configured here. The<br />
installer should have created the necessary entries for you, but you<br />
should look over it and make sure it's right, especially when using an<br />
encrypted root device, LVM or RAID.<br />
<br />
With the current kernel, an important change has been introduced<br />
pertaining to the ATA/IDE subsystem. The new pata (Parallel ATA)<br />
drivers replace the legacy IDE subsystem, and one important change is<br />
that the naming scheme for IDE disks has changed from the old hda,<br />
hdb, etc. to also use device names of the type sda, sdb, etc, just<br />
like SCSI and SATA devices do. Because of this, when using the new<br />
pata driver in the HOOKS of the /etc/mkinitcpio.conf, remember to use<br />
the appropriate device names in your /etc/fstab and bootloader<br />
configuration! Alternatively, you could use the /dev/disk/by-uuid/...<br />
or /dev/disk/by-label/... representations of your disk drives where<br />
available to make absolutely sure you're referring to the right<br />
partitions, and save yourself the trouble of sorting out whether<br />
you're supposed to use sda or hda. If that's not an option, here's the<br />
rundown; If you're using pata instead of ide in the HOOKS array of the<br />
/etc/mkinitcpio.conf, you'll be using the sd? names. If not, use the<br />
old style hd? names. It is therefore crucial to check the HOOKS array<br />
in the /etc/mkinitcpio.conf, to be able to adapt the other files<br />
accordingly.<br />
<br />
<br />
'''/etc/mkinitcpio.conf'''<br />
<br />
This file allows you to fine-tune the initial ramdisk (also commonly<br />
referred to as the "initrd") for your system. The initrd is a gzipped<br />
image that is read by the kernel during bootup. The purpose of the<br />
initrd is to bootstrap the system to the point where it can access the<br />
root filesystem. This means it has to load any modules that are<br />
required to "see" things like IDE, SCSI, or SATA drives (or USB/FW, if<br />
you are booting off a USB/FW drive). Once the initrd loads the proper<br />
modules, either manually or through udev, it passes control to the<br />
Arch system and your bootup continues. For this reason, the initrd<br />
only needs to contain the modules necessary to access the root<br />
filesystem. It does not need to contain every module you would ever<br />
want to use. The majority of your everyday modules will be loaded<br />
later on by udev, during the init process.<br />
<br />
By default, mkinitcpio.conf is configured to provide all known modules<br />
for IDE, SCSI, or SATA systems through so-called HOOKS. This means the<br />
default initrd should work for almost everybody. The downside to this<br />
is that there are many modules loaded that you will not need. This is<br />
easily visible by examining your module table after booting up (with<br />
the lsmod command). While this doesn't actually hurt anything, some<br />
people find it annoying. To cull this list down to only what you<br />
actually need, you can edit mkinitcpio.conf and remove the subsystem<br />
HOOKS (ie, IDE, SCSI, RAID, USB, etc) that you don't need.<br />
<br />
You can customize even further by specifying the exact modules you<br />
need in the MODULES array and remove even more of the hooks, but take<br />
heed to the comments in the file, as this is a touchy place to go<br />
crazy with removing entries!<br />
<br />
If you're using RAID or encryption on your root filesystem, then<br />
you'll have to tweak the RAID/CRYPT settings near the bottom. See the<br />
wiki pages for RAID/LVM, filesystem encryption, and mkinitcpio for<br />
more info.<br />
<br />
When you're finished tweaking mkinitcpio.conf, you must run mkinitcpio<br />
-p kernel26 as root to regenerate the images, unless you're still<br />
installing the system; In that case this step will be done<br />
automatically after choosing Install Kernel later in the process.<br />
<br />
WARNING: If you fail to set up your mkinitcpio.conf correctly, your<br />
system will not boot! For this reason, you should be especially<br />
careful when tweaking this file.<br />
<br />
If you do manage to render your system unbootable, you can try using<br />
the fallback image that is installed alongside the stock kernel. A<br />
boot option for this is included in the default GRUB and LILO <br />
configuration.<br />
<br />
Read the warning about the pata transition problems elaborated in the<br />
fstab section carefully!<br />
<br />
<br />
'''/etc/modprobe.conf'''<br />
<br />
This tells the kernel which modules it needs to load for system<br />
devices, and what options to set. For example, to have the kernel load<br />
your Realtek 8139 ethernet module when it starts the network (ie.<br />
tries to setup eth0), use this line:<br />
alias eth0 8139too<br />
<br />
The syntax of this file is nearly identical to the old modules.conf<br />
scheme, unless you use some of the more exotic options like<br />
post-install. Then you should invest a little time into reading man<br />
modprobe.conf.<br />
<br />
Most people will not need to edit this file.<br />
<br />
<br />
'''/etc/resolv.conf'''<br />
<br />
Use this file to manually setup your nameserver(s) that you want to<br />
use. It should basically look like this:<br />
search domain.tld<br />
nameserver 192.168.0.1<br />
nameserver 192.168.0.2<br />
<br />
Replace domain.tld and the ip addresses with your settings. The<br />
so-called search domain specifies the default domain that is appended<br />
to unqualified hostnames automatically. By setting this, a ping myhost<br />
will effectively become a ping myhost.domain.tld with the above<br />
values. These settings usually aren't mighty important, though, and<br />
most people should leave them alone for now. If you use DHCP, this<br />
file will be replaced with the correct values automatically when<br />
networking is started, meaning you can and should happily ignore this<br />
file.<br />
<br />
<br />
'''/etc/locale.gen'''<br />
<br />
This file contains a list of all supported locales and charsets<br />
available to you. When choosing a LOCALE in your /etc/rc.conf or when<br />
starting a program, it is required to uncomment the respective locale<br />
in this file, to make a "compiled" version available to the system,<br />
and run the locale-gen command as root to generate all uncommented<br />
locales and put them in their place afterwards. You should uncomment<br />
all locales you intend to use.<br />
<br />
During the installation process, you do not need to run locale-gen<br />
manually, this will be taken care of automatically after saving your<br />
changes to this file.<br />
<br />
By default, all locales are commented out, including the default<br />
en_US.utf8 locale referred to in the /etc/rc.conf file. To make your<br />
system work smoothly, you must edit this file and uncomment at least<br />
the one locale you're using in your rc.conf.<br />
<br />
<br />
'''/boot/grub/menu.lst'''<br />
<br />
GRUB is the default bootloader for Arch Linux. You should check and<br />
modify this file to accommodate your boot setup if you want to use<br />
GRUB, otherwise read on about the LILO configuration.<br />
<br />
Make sure you read the warning regarding the pata transition<br />
elaborated on in the fstab section!<br />
<br />
Configuring GRUB is quite easy, the biggest hurdle is that it uses yet<br />
another device naming scheme different from /dev; Your hard disks as a<br />
whole are referred to as (hd0), (hd1), etc., sequentially numbered in<br />
order of appearance on the IDE/SCSI bus, just like the hda, hdb, etc.<br />
names in GNU/Linux. The partitions of a disk are referred to with (hd0,0),<br />
(hd0,1) and so on, with 0 meaning the first partition. A few<br />
conversion examples are included in the default menu.lst to aid your<br />
understanding.<br />
<br />
Once you grasped the concept of device naming, all you need to do is<br />
to choose a nice title for your boot section(s), supply the correct<br />
root partition device as a parameter to the root option to have it<br />
mounted as / on bootup, and create a kernel line that includes the<br />
partition and path where the kernel is located as well as any boot<br />
parameters. If using the stock Arch 2.6.x kernel, you'll also need an<br />
initrd line that points to the kernel26.img file in your /boot<br />
directory. The path you put on your initrd line should be the same as<br />
the path to vmlinuz26 that you provide on the kernel line. You should<br />
be fine with the defaults, just check whether the partition<br />
information is correct in the root and kernel lines, especially in<br />
regard to the pata issue!<br />
<br />
To create a boot option that loads the bootsector of a different OS,<br />
the following example might be helpful. You will probably succeed in<br />
starting any Microsoft-based operating system with it, just add this<br />
block to the file after any other sections, and modify the partition<br />
device accordingly to refer to the partition containing the bootsector<br />
of the OS you are intending to boot.<br />
(1) Other OS<br />
title My Other OS<br />
rootnoverify (hd0,1)<br />
makeactive<br />
chainloader +1<br />
<br />
For advanced configuration of other OSes, please refer to the online<br />
GRUB manual.<br />
<br />
After checking your bootloader configuration for correctness, you'll<br />
be prompted for a partition to install the loader to. Unless you're<br />
using yet another boot loader, you should install GRUB to the MBR of<br />
the installation disk, which is usually represented by the appropriate<br />
device name without a number suffix.<br />
<br />
<br />
'''/etc/lilo.conf'''<br />
<br />
This is the configuration file for the LILO bootloader. Make sure you<br />
check this one and get it right if you want to use LILO to boot your<br />
system. See LILO documentation for help on this.<br />
<br />
Things you should check are the root= lines in the image sections and<br />
the boot= line right at the beginning of the file. The root lines<br />
specify the device which shall be mounted as the root filesystem on<br />
bootup. If you don't know what is supposed to be entered here, change<br />
to another terminal and type mount to see a list of all currently<br />
mounted drives, and look for the line which displays a device name<br />
mounted on /mnt type [...]. The device path at the beginning of this<br />
very line should be entered in the root lines of your lilo.conf.<br />
Change if necessary, and keep the pata issue in mind!<br />
<br />
The boot line should be okay by default in most cases. Unless you have<br />
a weird boot manager setup in mind with multiple OSes, the device<br />
referenced here should be having the same prefix your root lines have,<br />
but not end with a number. For example, a root of /dev/hda3 means you<br />
probably want to install LILO into the Master Boot Record of the hard<br />
disk, so you would set boot to /dev/hda, which references the disk as<br />
a whole. During installation, the boot device must be the current name<br />
of the device where you want to write the boot sector to; This may<br />
differ from the name of the device after the first boot, thanks to the<br />
pata transition! Check carefully what device to write to during the<br />
installation stage, for example with the mount command.<br />
<br />
To prevent some serious grief, you should make sure you know how to<br />
restore the bootsector of your other OSes, for example with Windows's<br />
FIXBOOT/FIXMBR tools.<br />
<br />
To be on the safe side, you should keep the option lba32 listed. This<br />
will prevent some geometry issues from happening.<br />
<br />
In some cases, depending on your BIOS, LILO will not run on bootup and<br />
spill out an error code infinitely. In most cases you either removed<br />
the lba32 option, or your hardware setup is a little special, meaning<br />
that maybe your CD-ROM drive is primary master and the hard disk you<br />
installed secondary slave. This can very well confuse your BIOS, and<br />
thus stop the boot process. To prevent that you can try and make the<br />
install drive the primary master on your IDE bus. If you've got a<br />
mixed IDE and SCSI system and the problem persists, you'll probably<br />
need some experimentation with the disk and bios options of LILO to<br />
provide a working mapping; The disk drives in your system are numbered<br />
sequentially by your BIOS, starting with 0x80. If you're lucky your<br />
SCSI controller tells you which drive has which BIOS ID, but usually<br />
you're not. How the drives are effectively numbered is depending on<br />
your BIOS, so in the worst case you can only guess until it works. A<br />
typical disk line would look like this:<br />
boot=/dev/hda<br />
disk=/dev/hda bios=0x80<br />
<br />
The disk option maps a BIOS ID to the disk device known to the system. Note<br />
that there is still no guarantee that things will work as other things<br />
can be wrong, so do not despair if all your tries fail, but rather try<br />
rearranging your hardware in a way that's not totally odd. In this<br />
area too much can go wrong and needs special handling to be explained<br />
here. In most cases the lba32 option will suffice anyway. Old hard<br />
drives will usually need a little more special care until they do as<br />
told.<br />
<br />
Don't become fidgety when reading this section, I (Dennis) just<br />
happened to stumble over this problem when experimenting with a rather<br />
odd system, and figured it'd be a good idea to mention this show<br />
stopper and workarounds here. You probably won't ever experience this,<br />
as you should be using GRUB anyway.<br />
<br />
How to recreate a LILO boot sector with only a rescue disk is<br />
explained later in this document.<br />
<br />
<br />
'''/etc/conf.d/*'''<br />
<br />
During setup, this is totally unimportant. Consider this as reference<br />
for the interested.<br />
<br />
Some daemon scripts will have a matching configuration file in this<br />
directory that contains some more-or-less useful default values. When<br />
a daemon is started, it will first source the settings from its<br />
config file within this directory, and then source the /etc/rc.conf.<br />
This means you can easily centralize all your daemon configuration<br />
options in your /etc/rc.conf simply by setting an appropriate variable<br />
value, or split up your configuration over multiple files if you<br />
prefer a decentralized approach to this issue. Isn't life great if<br />
it's all just simple scripting?<br />
<br />
<br />
'''/etc/profile'''<br />
<br />
This script is run on each user login to initialize the system. It is<br />
kept quite simple under Arch Linux, as most things are. You may wish<br />
to edit or customize it to suit your needs.<br />
<br />
====Kernel====<br />
<br />
The CD-ROM includes the latest kernel available at time of release. If you are using the FTP<br />
Installation method, the kernel about to be installed will be the<br />
current version waiting on your FTP source, and might therefore<br />
introduce changes and/or incompatibilities unknown at the present<br />
time. This is unlikely, but keep it in mind.<br />
<br />
====Install Bootloader====<br />
<br />
Install Bootloader will install a bootloader on your hard drive,<br />
either GRUB (recommended) or LILO, depending on your personal<br />
preference.<br />
<br />
Before installing the bootloader, the setup script will want you to<br />
examine the appropriate configuration file to confirm the proper<br />
settings. <br />
<br />
If you choose to install LILO, the bootloader will be automatically<br />
installed according to your settings in the configuration file, whilst<br />
GRUB demands the selection of a partition to install the bootloader<br />
to. Here you should choose what you would enter as the boot option of<br />
LILO, which is usually the entry named /dev/hda, as it refers the<br />
master boot record of the first hard disk. Detailed error messages can<br />
be found as usual on VC5 (virtual console 5), if anything goes wrong.<br />
<br />
If you plan on setting up a multiboot system, you may wish to install the bootloader in your / or /boot partition, and<br />
refer to that boot sector from whatever other boot loader you want to<br />
reside in the master boot record. (chainloading)<br />
<br />
Installing a boot loader in the MBR will relentlessly overwrite any<br />
existing bootloader! Make sure you understand the implications of that<br />
if you're running a multiboot system, or want to preserve an installed<br />
bootloader from another OS!<br />
<br />
====Exit Install====<br />
<br />
Exit the Installer, eject the CD, and:<br />
reboot<br />
<br />
Login as root and add a user as outlined in the<br />
[[User_Management | User Management]] section, and set up your Internet Connection.<br />
<br />
Congratulations! Welcome to your new Arch Linux base system!<br />
<br />
==APPENDIX==<br />
===Adding a Window Manager/Desktop Environment===<br />
*[[KDE]] <br />
*[[KDEmod]]<br />
*[[GNOME]]<br />
*[[Xfce]]<br />
*[[Openbox]]<br />
*[[Wmii]]<br />
*[[Fluxbox]]<br />
*[[LXDE]]<br />
*[[E17]]<br />
*[[Xmonad]]<br />
See also [[.xinitrc]]<br />
<br />
===Boot Scripts===<br />
<br />
Arch Linux uses a fairly simple bootup sequence quite similar to *BSDs. The first boot script to run is /etc/rc.sysinit. When it's done, /etc/rc.multi will be called (in a normal bootup). The last script to run will be /etc/rc.local. When started in runlevel 1, the single user mode, the script /etc/rc.single is run instead of /etc/rc.multi. You will not find an endless symlink collection in the /etc/rc?.d/ directories to define the bootup sequence for all possible runlevels. In fact, due to this approach Arch only really has three runlevels, if you take starting up X in runlevel 5 into account. The boot scripts are using the variables and definitions found in the /etc/rc.conf file and also a set of general functions defined in the<br />
/etc/rc.d/functions script. If you plan to write your own daemon<br />
files, you should consider having a look at this file and existing<br />
daemon scripts.<br />
<br />
Boot Script Overview<br />
<br />
#/etc/rc.sysinit<br />
#/etc/rc.single<br />
#/etc/rc.multi<br />
#/etc/rc.local<br />
#/etc/rc.shutdown<br />
#/etc/rc.local.shutdown<br />
#/etc/rc.d/*<br />
<br />
<br />
'''/etc/rc.sysinit'''<br />
<br />
The main system boot script. It does boot-critical things like<br />
mounting filesystems, running udev, activating swap, loading modules,<br />
setting localization parameters, etc. You will most likely never need<br />
to edit this file!<br />
<br />
<br />
'''/etc/rc.single'''<br />
<br />
Single-user startup. Not used in a normal boot-up. If the system is<br />
started in single-user mode, for example with the kernel parameter 1<br />
before booting or during normal multi-user operation with the command<br />
init 1, this script makes sure no daemons are running except for the<br />
bare minimum; syslog-ng and udev. The single-user mode is useful if<br />
you need to make any changes to the system while making sure that no<br />
remote user can do anything that might cause data loss or damage.<br />
<br />
For desktop users, this mode usually is useless as crud. You should<br />
have no need to edit this script, either.<br />
<br />
<br />
'''/etc/rc.multi'''<br />
<br />
Multi-user startup script. It starts all daemons you configured in the<br />
DAEMONS array (set in /etc/rc.conf) after which it calls<br />
/etc/rc.local. You shouldn't feel a pressing need to edit this file.<br />
<br />
<br />
'''/etc/rc.local'''<br />
<br />
Local multi-user startup script. It is a good place to put any<br />
last-minute commands you want the system to run at the very end of the<br />
bootup process. This is finally the one and only script you should<br />
modify if needed, and you have total freedom on what to add to this<br />
script.<br />
<br />
Most common system configuration tasks, like loading modules, changing<br />
the console font or setting up devices, usually have a dedicated place<br />
where they belong. To avoid confusion, you should make sure that<br />
whatever you intend to add to your rc.local isn't feeling just as home<br />
in /etc/profile.d/ or any other already existant config location<br />
instead.<br />
<br />
<br />
'''/etc/rc.shutdown'''<br />
<br />
System shutdown script. It stops daemons, unmounts filesystems,<br />
deactivates the swap, etc. Just don't touch.<br />
<br />
<br />
'''/etc/rc.local.shutdown'''<br />
<br />
Analogous to the /etc/rc.local file, this file may contain any<br />
commands you want to run right before the common rc.shutdown is<br />
executed. Please note that this file does not exist by default, and<br />
for it to work properly, it must be set as executable.<br />
<br />
<br />
'''/etc/rc.d/*'''<br />
<br />
This directory contains the daemon scripts referred to from the<br />
rc.conf's DAEMONS array. In addition to being called on bootup, you<br />
can use these scripts when the system is running to manage the<br />
services of your system. For example the command<br />
/etc/rc.d/postfix stop<br />
<br />
will stop the postfix daemon. Of course a script only exists when the<br />
appropriate package has been installed (in this case postfix). With a<br />
basic system install, you don't have many scripts in here, but rest<br />
assured that all relevant daemon scripts end up here. This directory<br />
is pretty much the equivalent to the /etc/rc3.d/ or /etc/init.d/<br />
directories of other distributions, without all the symlink hassle.<br />
<br />
===User Management===<br />
<br />
Users and groups can be added and deleted with the standard commands<br />
provided in the util-linux package: useradd, userdel, groupadd,<br />
groupdel, passwd, and gpasswd. The typical way of adding a user is<br />
similar to this procedure:<br />
useradd -m -s /bin/bash johndoe<br />
passwd johndoe<br />
<br />
The first command will add the user named johndoe to the system,<br />
create a home directory for him at /home/johndoe, and place some<br />
default login files in his home directory. It will also set his login<br />
shell to be /bin/bash. The second command will ask you for a password<br />
for the johndoe user. A password is required to activate the account.<br />
<br />
As an alternative to the useradd command, the adduser script is also<br />
available to interactively create new users on your system simply by<br />
answering questions.<br />
<br />
See the manpages for more information on the remaining commands. It is<br />
a good idea to create one or multiple normal users for your day-to-day<br />
work to fully use the available security features and minimize<br />
potential damage that may be the result of using the root user for<br />
anything but system administration tasks.<br />
<br />
===Internet Access===<br />
<br />
Due to a lack of developers for dialup issues, connecting Arch to the<br />
Internet with a dialup line is requiring a lot of manual setup. If at<br />
all possible, set up a dedicated router which you can then use as a<br />
default gateway on the Arch box.<br />
<br />
There are quite a few dialup related documents in the Arch Linux Wiki<br />
<br />
====Analog Modem====<br />
<br />
To be able to use a Hayes-compatible, external, analog modem, you need<br />
to at least have the ppp package installed. Modify the file<br />
/etc/ppp/options to suit your needs and according to man pppd. You<br />
will need to define a chat script to supply your username and password<br />
to the ISP after the initial connection has been established. The<br />
manpages for pppd and chat have examples in them that should suffice<br />
to get a connection up and running if you're either experienced or</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Newcomers_Guide&diff=58744
Newcomers Guide
2009-01-21T15:50:14Z
<p>Zaggynl: Removing all content from page</p>
<hr />
<div></div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Open_Sound_System&diff=49093
Open Sound System
2008-09-09T07:03:23Z
<p>Zaggynl: /* Unstable version */</p>
<hr />
<div>[[Category:Sound (English)]]<br />
[[Category:Audio/Video (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|OSS}}<br />
{{i18n_entry|简体中文|OSS (简体中文)}}<br />
{{i18n_links_end}}<br />
<br />
= Introduction =<br />
The Open Sound System (OSS) from [http://www.opensound.com www.opensound.com] is a commercially-supported sound driver that works on several unix-like systems, including Linux, FreeBSD, and Solaris.<br />
<br />
The OSS was previously proprietary and being open-sourced recently, it has nothing to do with the sub-quality OSS/free in early linux kernels.<br />
<br />
Pros:<br />
* Transparent software mixing in kernel space ('''virtual mixer'''), up to 18 virtual sound devices (unlike ALSA's dmix, which works in user-space via ALSA lib).<br />
* Per-application mixer volume.<br />
* Much better sound quality for several onboard audio chips.<br />
<br />
Cons:<br />
* Software-emulated 3D enhancement, reverb effect, and equalizer have not yet been added to the new mixing engine in oss v4.<br />
<br />
= Installation =<br />
* Install package<br />
** Get the PKGBUILD:<br />
*** http://aur.archlinux.org/packages.php?do_Details=1&ID=14421<br />
*** Or the experimental http://aur.archlinux.org/packages.php?ID=17029<br />
** Extract the files from the tarball:<br />
*** <tt>tar -zxvf oss-filename.tar.gz</tt><br />
**Enter the directory created by expanding the tarball and install the package:<br />
*** <tt>makepkg -i</tt><br />
NOTE: Perform this command as a normal user. Do not run it as root or with sudo.<br />
<br />
* Start oss-linux:<br />
** Add ''!soundcore'' to <tt>MODULES</tt> in ''/etc/rc.conf'' to blacklist it.<br />
** Reboot to clean up alsa drivers, or manually unload the module ''soundcore'' and all other modules depending on it.<br />
** Run <tt>/etc/rc.d/oss-linux-free start</tt> (or oss-linux in case of the older, proprietary package), or add it to <tt>DAEMONS</tt> in ''/etc/rc.conf''<br />
<br />
= Configuration =<br />
''Your sound card should not need any configuration to work properly''<br />
<br />
Config files used to load oss drivers are under ''/usr/lib/oss/conf''. Do not edit these files directly, instead you should use ''/etc/modprobe.conf''. Every file under /usr/lib/oss/conf is named MODULE_NAME.conf and all the options are passed to modprobe when you're starting oss-linux. So the following two methods are actually doing the same thing:<br />
<br />
(/usr/lib/oss/conf/osscore.conf)<br />
max_intrate=1000<br />
src_quality=4<br />
(/etc/modprobe.conf)<br />
options osscore max_intrate=1000 src_quality=4<br />
<small>NOTE: This is merely an example, it is ''not'' recommended to use these parameters unless you know what you're doing.</small><br />
<br />
To get the list of the drivers you use, run <tt>ossdetect -v</tt> and check the file <tt>/usr/lib/oss/etc/installed_drivers</tt>.<br />
<br />
Other parameters: see the comments in<br />
/usr/lib/oss/conf/osscore.conf<br />
/usr/lib/oss/conf/ossusb.conf<br />
/usr/lib/oss/conf/YOUR_AUDIO_DRIVER.conf<br />
<br />
= Programs =<br />
* '''/etc/rc.d/oss-linux''': oss-linux service.<br />
* '''/etc/rc.d/oss-linux-free''': same as above, but for the free version.<br />
* '''ossinfo''': show list of sound devices and their status; passing argument "-v9" to get details including which programs use them.<br />
* '''ossmix''': command-line mixer, where you can configure volume, recording source and special sound effects (surround, reverb, etc).<br />
* '''ossxmix''': same as ossmix except for that it provides a GUI using gtk2.<br />
* '''savemixer''': save your current mixer settings (need superuser) or restore them, called automatically when the oss-linux service is stopped.<br />
* '''ossrecord''': simple command-line recording program.<br />
* '''ossplay''': simple command-line playing program. Supports WAV, AU, VOC and a few other containers.<br />
<br />
= Troubleshooting =<br />
* Like ALSA, you have to lower the main volume and PCM volume to certain degree to avoid noises (depending on your audio chip. I use vol=65,pcm=65 for my via8237)<br />
<br />
* See [http://4front-tech.com/forum/viewtopic.php?t=2358 here] how to set the default soundcard, in case the default choice isn't optimal.<br />
<br />
* If you have a problem getting sound from an application, the 4front wiki may have the [http://www.4front-tech.com/wiki/index.php/Configuring_Applications_for_OSSv4 answer].<br />
<br />
* If you have other issues, try and search or post on the forums at: http://www.4front-tech.com/forum/<br />
<br />
== Skype ==<br />
There's a special Skype version for OSS (QT static build), you can get the PKGBUILD here [http://aur.archlinux.org/packages.php?do_Details=1&ID=13003&O=0&L=0&C=0&K=skype&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd].<br />
A binary is available from skype's download page [http://skype.com/go/getskype-linux-oss].<br />
<br />
= Tips and Tricks =<br />
<br />
== ALSA compatibility ==<br />
OSS provides 2 layers for ALSA compatibility: kernel and alsa lib. The kernel module ("cuckoo") was 100% compatible with all the apps but it no longer works with latest OSS version; The alsa emulation lib in oss distribution is outdated and I don't know where to get the latest version.<br />
<br />
What you can have now is to use ALSA's oss plugin:<br />
# Install alsa-plugins<br />
# Edit ''/etc/asound.conf'':<br />
pcm.oss {<br />
type oss<br />
device /dev/dsp<br />
}<br />
<br />
pcm.!default {<br />
type oss<br />
device /dev/dsp<br />
}<br />
<br />
ctl.oss {<br />
type oss<br />
device /dev/mixer<br />
}<br />
<br />
ctl.!default {<br />
type oss<br />
device /dev/mixer<br />
}<br />
This method doesn't work with programs that detect hardware sound devices (skype 1.3, gizmo, ..)<br />
<br />
== Using your multimedia keys with OSS ==<br />
<br />
Wanting to raise-lower-mute-unmute the sound with your multimedia keys using OSS v4? <br />
<br />
Just make three "scripts" like these (I am assuming you have the bc package installed):<br />
<br />
lowervolume.sh:<br />
VOL=$(ossmix | grep misc.pcm1 | awk '{print $4}' | awk -F : '{print $1}')<br />
VOL=$(echo $VOL-2 | bc)<br />
ossmix misc.pcm1 $VOL:$VOL<br />
<br />
raisevolume.sh:<br />
VOL=$(ossmix | grep misc.pcm1 | awk '{print $4}' | awk -F : '{print $1}')<br />
VOL=$(echo $VOL+2 | bc)<br />
ossmix misc.pcm1 $VOL:$VOL<br />
<br />
mute.sh:<br />
#!/bin/bash<br />
VOLUME=$(cat $HOME/.volume)<br />
if [ -z "$VOLUME" ]; then<br />
VOLUME=$(ossmix | grep misc.pcm1 | awk '{print $4}' | awk -F : '{print $1}')<br />
ossmix misc.pcm1 0:0<br />
echo $VOLUME > $HOME/.volume<br />
else<br />
ossmix misc.pcm1 $VOLUME:$VOLUME<br />
> $HOME/.volume<br />
fi<br />
This will restore the previous volume levels when unmuting. Issue a:<br />
touch $HOME/.volume<br />
before using the first time.<br />
<br />
Then you just have to chmod +x these and set the keyboard shortcuts on your VM.<br />
<br />
== System-wide (software) equalizer effects ==<br />
<br />
NOTES: This requires the use of the old softoss module (the predecessor of vmix) which may not be as good as vmix, wine and gstreamer do not play nice with softoss, and the module will not work with sample rates higher than 48khz.<br />
<br />
We must do a few things to gain access to these effects.<br />
<br />
* If you're running the oss-linux-free daemon right now, stop it by running (as root):<br />
/etc/rc.d/oss-linux-free stop<br />
** On builds 1015 and older, in /usr/lib/oss/etc/installed_drivers remove<br />
vmix<br />
** On 1016 and newer, you should instead pass "vmix_disabled=1" parameter to osscore (via /usr/lib/oss/conf/osscore.conf) to disable vmix.<br />
*in /usr/lib/oss/etc/installed_drivers add<br />
softoss<br />
* in /etc/rc.d/oss-linux-free comment out lines 15 through 20 so that it looks kinda like this<br />
#!/bin/bash<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
case "$1" in<br />
start)<br />
stat_busy "Starting OSS/Open source driver"<br />
# start<br />
/usr/sbin/soundon<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
grep '^softoss' /proc/modules >/dev/null 2>/dev/null<br />
# if [ $? -eq 0 ]; then<br />
# stat_busy "Replacing old \"softoss\" module with \"vmix\""<br />
# rmmod softoss<br />
# modprobe vmix<br />
# sed -i 's/^softoss.*$/vmix/' /usr/lib/oss/etc/installed_drivers<br />
# fi<br />
add_daemon oss4<br />
stat_done<br />
fi<br />
;;<br />
stop)<br />
stat_busy "Saving OSS mixer"<br />
/usr/sbin/savemixer<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
stat_done<br />
fi<br />
grep '^"cuckoo"' /proc/modules >/dev/null 2>/dev/null<br />
if [ $? -eq 0 ]; then<br />
stat_busy "Removing \"cuckoo\" module"<br />
rmmod \"cuckoo\"<br />
fi<br />
stat_busy "Stopping OSS/Open source driver"<br />
/usr/sbin/soundoff<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
rm_daemon oss4<br />
stat_done<br />
fi<br />
;;<br />
restart)<br />
$0 stop<br />
sleep 1<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}"<br />
esac<br />
This keeps the oss-linux-free daemon from replacing softoss with vmix. (Very useful if you wish to switch between softoss and vmix.)<br />
<br />
* start the daemon again (as root of course)<br />
/etc/rc.d/oss-linux-free start<br />
* If no errors are reported, then you may now see/use the effects with either ossmix or ossxmix with<br />
ossmix -d1<br />
or<br />
ossxmix<br />
* you must turn off bipass to actually use the effects<br />
ossmix -d1 effects.eq.bypass OFF<br />
or just uncheck bypass in ossxmix<br />
<br />
* enjoy<br />
<br />
= Unstable version =<br />
<br />
Installing the latest version of Opensound by zaggynl<br /><br />
Status: draft<br /><br />
Allows for: stereo sound from multiple sources<br /><br />
Known issues: recording not properly working[[http://4front-tech.com/forum/viewtopic.php?p=10289#10289]], hissing before and after playback (play a Youtube video to temporarily stop that)<br /><br />
<br /><br />
Prerequisites: Working soundcard, your user is in the audio group, no other sound systems that may intervene (such as ALSA)<br/ ><br />
Execute below commands:<br /><br />
(installing mercurial -distributed version control system-, downloading latest OSS source, compiling and installing, sound test)<br />
* sudo pacman -S mercurial<br />
* cd /usr/src<br />
* sudo hg clone http://mercurial.opensound.com/ oss-devel<br />
* cd ~/<br />
* mkdir oss41build<br />
* cd oss41build/<br />
* sudo sh /usr/src/oss-devel/configure<br />
* sudo make<br />
* sudo make install<br />
* osstest <br />
You should hear a soundtest now :)<br /><br />
<br />
Installing as daemon:<br />
* wget http://aur.archlinux.org/packages/oss-testing/oss-testing/oss.rc && sudo cp oss.rc /etc/rc.d/oss<br />
* add oss to DAEMONS in rc.conf<br />
<br />
OSS 4.1 (current at time of writing) allowed me to use my Creative X-Fi ExtremeGamer soundcard!<br /><br />
I got my info from https://help.ubuntu.com/community/OpenSound</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Open_Sound_System&diff=49092
Open Sound System
2008-09-09T06:59:36Z
<p>Zaggynl: /* Unstable version */</p>
<hr />
<div>[[Category:Sound (English)]]<br />
[[Category:Audio/Video (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|OSS}}<br />
{{i18n_entry|简体中文|OSS (简体中文)}}<br />
{{i18n_links_end}}<br />
<br />
= Introduction =<br />
The Open Sound System (OSS) from [http://www.opensound.com www.opensound.com] is a commercially-supported sound driver that works on several unix-like systems, including Linux, FreeBSD, and Solaris.<br />
<br />
The OSS was previously proprietary and being open-sourced recently, it has nothing to do with the sub-quality OSS/free in early linux kernels.<br />
<br />
Pros:<br />
* Transparent software mixing in kernel space ('''virtual mixer'''), up to 18 virtual sound devices (unlike ALSA's dmix, which works in user-space via ALSA lib).<br />
* Per-application mixer volume.<br />
* Much better sound quality for several onboard audio chips.<br />
<br />
Cons:<br />
* Software-emulated 3D enhancement, reverb effect, and equalizer have not yet been added to the new mixing engine in oss v4.<br />
<br />
= Installation =<br />
* Install package<br />
** Get the PKGBUILD:<br />
*** http://aur.archlinux.org/packages.php?do_Details=1&ID=14421<br />
*** Or the experimental http://aur.archlinux.org/packages.php?ID=17029<br />
** Extract the files from the tarball:<br />
*** <tt>tar -zxvf oss-filename.tar.gz</tt><br />
**Enter the directory created by expanding the tarball and install the package:<br />
*** <tt>makepkg -i</tt><br />
NOTE: Perform this command as a normal user. Do not run it as root or with sudo.<br />
<br />
* Start oss-linux:<br />
** Add ''!soundcore'' to <tt>MODULES</tt> in ''/etc/rc.conf'' to blacklist it.<br />
** Reboot to clean up alsa drivers, or manually unload the module ''soundcore'' and all other modules depending on it.<br />
** Run <tt>/etc/rc.d/oss-linux-free start</tt> (or oss-linux in case of the older, proprietary package), or add it to <tt>DAEMONS</tt> in ''/etc/rc.conf''<br />
<br />
= Configuration =<br />
''Your sound card should not need any configuration to work properly''<br />
<br />
Config files used to load oss drivers are under ''/usr/lib/oss/conf''. Do not edit these files directly, instead you should use ''/etc/modprobe.conf''. Every file under /usr/lib/oss/conf is named MODULE_NAME.conf and all the options are passed to modprobe when you're starting oss-linux. So the following two methods are actually doing the same thing:<br />
<br />
(/usr/lib/oss/conf/osscore.conf)<br />
max_intrate=1000<br />
src_quality=4<br />
(/etc/modprobe.conf)<br />
options osscore max_intrate=1000 src_quality=4<br />
<small>NOTE: This is merely an example, it is ''not'' recommended to use these parameters unless you know what you're doing.</small><br />
<br />
To get the list of the drivers you use, run <tt>ossdetect -v</tt> and check the file <tt>/usr/lib/oss/etc/installed_drivers</tt>.<br />
<br />
Other parameters: see the comments in<br />
/usr/lib/oss/conf/osscore.conf<br />
/usr/lib/oss/conf/ossusb.conf<br />
/usr/lib/oss/conf/YOUR_AUDIO_DRIVER.conf<br />
<br />
= Programs =<br />
* '''/etc/rc.d/oss-linux''': oss-linux service.<br />
* '''/etc/rc.d/oss-linux-free''': same as above, but for the free version.<br />
* '''ossinfo''': show list of sound devices and their status; passing argument "-v9" to get details including which programs use them.<br />
* '''ossmix''': command-line mixer, where you can configure volume, recording source and special sound effects (surround, reverb, etc).<br />
* '''ossxmix''': same as ossmix except for that it provides a GUI using gtk2.<br />
* '''savemixer''': save your current mixer settings (need superuser) or restore them, called automatically when the oss-linux service is stopped.<br />
* '''ossrecord''': simple command-line recording program.<br />
* '''ossplay''': simple command-line playing program. Supports WAV, AU, VOC and a few other containers.<br />
<br />
= Troubleshooting =<br />
* Like ALSA, you have to lower the main volume and PCM volume to certain degree to avoid noises (depending on your audio chip. I use vol=65,pcm=65 for my via8237)<br />
<br />
* See [http://4front-tech.com/forum/viewtopic.php?t=2358 here] how to set the default soundcard, in case the default choice isn't optimal.<br />
<br />
* If you have a problem getting sound from an application, the 4front wiki may have the [http://www.4front-tech.com/wiki/index.php/Configuring_Applications_for_OSSv4 answer].<br />
<br />
* If you have other issues, try and search or post on the forums at: http://www.4front-tech.com/forum/<br />
<br />
== Skype ==<br />
There's a special Skype version for OSS (QT static build), you can get the PKGBUILD here [http://aur.archlinux.org/packages.php?do_Details=1&ID=13003&O=0&L=0&C=0&K=skype&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd].<br />
A binary is available from skype's download page [http://skype.com/go/getskype-linux-oss].<br />
<br />
= Tips and Tricks =<br />
<br />
== ALSA compatibility ==<br />
OSS provides 2 layers for ALSA compatibility: kernel and alsa lib. The kernel module ("cuckoo") was 100% compatible with all the apps but it no longer works with latest OSS version; The alsa emulation lib in oss distribution is outdated and I don't know where to get the latest version.<br />
<br />
What you can have now is to use ALSA's oss plugin:<br />
# Install alsa-plugins<br />
# Edit ''/etc/asound.conf'':<br />
pcm.oss {<br />
type oss<br />
device /dev/dsp<br />
}<br />
<br />
pcm.!default {<br />
type oss<br />
device /dev/dsp<br />
}<br />
<br />
ctl.oss {<br />
type oss<br />
device /dev/mixer<br />
}<br />
<br />
ctl.!default {<br />
type oss<br />
device /dev/mixer<br />
}<br />
This method doesn't work with programs that detect hardware sound devices (skype 1.3, gizmo, ..)<br />
<br />
== Using your multimedia keys with OSS ==<br />
<br />
Wanting to raise-lower-mute-unmute the sound with your multimedia keys using OSS v4? <br />
<br />
Just make three "scripts" like these (I am assuming you have the bc package installed):<br />
<br />
lowervolume.sh:<br />
VOL=$(ossmix | grep misc.pcm1 | awk '{print $4}' | awk -F : '{print $1}')<br />
VOL=$(echo $VOL-2 | bc)<br />
ossmix misc.pcm1 $VOL:$VOL<br />
<br />
raisevolume.sh:<br />
VOL=$(ossmix | grep misc.pcm1 | awk '{print $4}' | awk -F : '{print $1}')<br />
VOL=$(echo $VOL+2 | bc)<br />
ossmix misc.pcm1 $VOL:$VOL<br />
<br />
mute.sh:<br />
#!/bin/bash<br />
VOLUME=$(cat $HOME/.volume)<br />
if [ -z "$VOLUME" ]; then<br />
VOLUME=$(ossmix | grep misc.pcm1 | awk '{print $4}' | awk -F : '{print $1}')<br />
ossmix misc.pcm1 0:0<br />
echo $VOLUME > $HOME/.volume<br />
else<br />
ossmix misc.pcm1 $VOLUME:$VOLUME<br />
> $HOME/.volume<br />
fi<br />
This will restore the previous volume levels when unmuting. Issue a:<br />
touch $HOME/.volume<br />
before using the first time.<br />
<br />
Then you just have to chmod +x these and set the keyboard shortcuts on your VM.<br />
<br />
== System-wide (software) equalizer effects ==<br />
<br />
NOTES: This requires the use of the old softoss module (the predecessor of vmix) which may not be as good as vmix, wine and gstreamer do not play nice with softoss, and the module will not work with sample rates higher than 48khz.<br />
<br />
We must do a few things to gain access to these effects.<br />
<br />
* If you're running the oss-linux-free daemon right now, stop it by running (as root):<br />
/etc/rc.d/oss-linux-free stop<br />
** On builds 1015 and older, in /usr/lib/oss/etc/installed_drivers remove<br />
vmix<br />
** On 1016 and newer, you should instead pass "vmix_disabled=1" parameter to osscore (via /usr/lib/oss/conf/osscore.conf) to disable vmix.<br />
*in /usr/lib/oss/etc/installed_drivers add<br />
softoss<br />
* in /etc/rc.d/oss-linux-free comment out lines 15 through 20 so that it looks kinda like this<br />
#!/bin/bash<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
case "$1" in<br />
start)<br />
stat_busy "Starting OSS/Open source driver"<br />
# start<br />
/usr/sbin/soundon<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
grep '^softoss' /proc/modules >/dev/null 2>/dev/null<br />
# if [ $? -eq 0 ]; then<br />
# stat_busy "Replacing old \"softoss\" module with \"vmix\""<br />
# rmmod softoss<br />
# modprobe vmix<br />
# sed -i 's/^softoss.*$/vmix/' /usr/lib/oss/etc/installed_drivers<br />
# fi<br />
add_daemon oss4<br />
stat_done<br />
fi<br />
;;<br />
stop)<br />
stat_busy "Saving OSS mixer"<br />
/usr/sbin/savemixer<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
stat_done<br />
fi<br />
grep '^"cuckoo"' /proc/modules >/dev/null 2>/dev/null<br />
if [ $? -eq 0 ]; then<br />
stat_busy "Removing \"cuckoo\" module"<br />
rmmod \"cuckoo\"<br />
fi<br />
stat_busy "Stopping OSS/Open source driver"<br />
/usr/sbin/soundoff<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
rm_daemon oss4<br />
stat_done<br />
fi<br />
;;<br />
restart)<br />
$0 stop<br />
sleep 1<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}"<br />
esac<br />
This keeps the oss-linux-free daemon from replacing softoss with vmix. (Very useful if you wish to switch between softoss and vmix.)<br />
<br />
* start the daemon again (as root of course)<br />
/etc/rc.d/oss-linux-free start<br />
* If no errors are reported, then you may now see/use the effects with either ossmix or ossxmix with<br />
ossmix -d1<br />
or<br />
ossxmix<br />
* you must turn off bipass to actually use the effects<br />
ossmix -d1 effects.eq.bypass OFF<br />
or just uncheck bypass in ossxmix<br />
<br />
* enjoy<br />
<br />
= Unstable version =<br />
<br />
Installing the latest version of Opensound by zaggynl<br /><br />
Status: draft<br /><br />
Allows for: stereo sound from multiple sources<br /><br />
Known issues: recording not properly working[[http://4front-tech.com/forum/viewtopic.php?p=10289#10289]], hissing before and after playback (play a Youtube video to temporarily stop that)<br /><br />
<br /><br />
Prerequisites: Working soundcard, your user is in the audio group, no other sound systems that may intervene (such as ALSA)<br/ ><br />
Execute below commands:<br /><br />
(installing mercurial -distributed version control system-, downloading latest OSS source, compiling and installing, sound test)<br />
* sudo pacman -S mercurial<br />
* cd /usr/src<br />
* sudo hg clone http://mercurial.opensound.com/ oss-devel<br />
* cd ~/<br />
* mkdir oss41build<br />
* cd oss41build/<br />
* sudo sh /usr/src/oss-devel/configure<br />
* sudo make<br />
* sudo make install<br />
* osstest <br />
You should hear a soundtest now :)<br /><br />
<br />
* Get http://aur.archlinux.org/packages/oss-testing/oss-testing/oss.rc and put it as /etc/rc.d/oss<br />
* add oss to DAEMONS in rc.conf<br />
<br />
OSS 4.1 (current at time of writing) allowed me to use my Creative X-Fi ExtremeGamer soundcard!<br /><br />
I got my info from https://help.ubuntu.com/community/OpenSound</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Open_Sound_System&diff=49091
Open Sound System
2008-09-09T06:58:23Z
<p>Zaggynl: /* Unstable version */</p>
<hr />
<div>[[Category:Sound (English)]]<br />
[[Category:Audio/Video (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|OSS}}<br />
{{i18n_entry|简体中文|OSS (简体中文)}}<br />
{{i18n_links_end}}<br />
<br />
= Introduction =<br />
The Open Sound System (OSS) from [http://www.opensound.com www.opensound.com] is a commercially-supported sound driver that works on several unix-like systems, including Linux, FreeBSD, and Solaris.<br />
<br />
The OSS was previously proprietary and being open-sourced recently, it has nothing to do with the sub-quality OSS/free in early linux kernels.<br />
<br />
Pros:<br />
* Transparent software mixing in kernel space ('''virtual mixer'''), up to 18 virtual sound devices (unlike ALSA's dmix, which works in user-space via ALSA lib).<br />
* Per-application mixer volume.<br />
* Much better sound quality for several onboard audio chips.<br />
<br />
Cons:<br />
* Software-emulated 3D enhancement, reverb effect, and equalizer have not yet been added to the new mixing engine in oss v4.<br />
<br />
= Installation =<br />
* Install package<br />
** Get the PKGBUILD:<br />
*** http://aur.archlinux.org/packages.php?do_Details=1&ID=14421<br />
*** Or the experimental http://aur.archlinux.org/packages.php?ID=17029<br />
** Extract the files from the tarball:<br />
*** <tt>tar -zxvf oss-filename.tar.gz</tt><br />
**Enter the directory created by expanding the tarball and install the package:<br />
*** <tt>makepkg -i</tt><br />
NOTE: Perform this command as a normal user. Do not run it as root or with sudo.<br />
<br />
* Start oss-linux:<br />
** Add ''!soundcore'' to <tt>MODULES</tt> in ''/etc/rc.conf'' to blacklist it.<br />
** Reboot to clean up alsa drivers, or manually unload the module ''soundcore'' and all other modules depending on it.<br />
** Run <tt>/etc/rc.d/oss-linux-free start</tt> (or oss-linux in case of the older, proprietary package), or add it to <tt>DAEMONS</tt> in ''/etc/rc.conf''<br />
<br />
= Configuration =<br />
''Your sound card should not need any configuration to work properly''<br />
<br />
Config files used to load oss drivers are under ''/usr/lib/oss/conf''. Do not edit these files directly, instead you should use ''/etc/modprobe.conf''. Every file under /usr/lib/oss/conf is named MODULE_NAME.conf and all the options are passed to modprobe when you're starting oss-linux. So the following two methods are actually doing the same thing:<br />
<br />
(/usr/lib/oss/conf/osscore.conf)<br />
max_intrate=1000<br />
src_quality=4<br />
(/etc/modprobe.conf)<br />
options osscore max_intrate=1000 src_quality=4<br />
<small>NOTE: This is merely an example, it is ''not'' recommended to use these parameters unless you know what you're doing.</small><br />
<br />
To get the list of the drivers you use, run <tt>ossdetect -v</tt> and check the file <tt>/usr/lib/oss/etc/installed_drivers</tt>.<br />
<br />
Other parameters: see the comments in<br />
/usr/lib/oss/conf/osscore.conf<br />
/usr/lib/oss/conf/ossusb.conf<br />
/usr/lib/oss/conf/YOUR_AUDIO_DRIVER.conf<br />
<br />
= Programs =<br />
* '''/etc/rc.d/oss-linux''': oss-linux service.<br />
* '''/etc/rc.d/oss-linux-free''': same as above, but for the free version.<br />
* '''ossinfo''': show list of sound devices and their status; passing argument "-v9" to get details including which programs use them.<br />
* '''ossmix''': command-line mixer, where you can configure volume, recording source and special sound effects (surround, reverb, etc).<br />
* '''ossxmix''': same as ossmix except for that it provides a GUI using gtk2.<br />
* '''savemixer''': save your current mixer settings (need superuser) or restore them, called automatically when the oss-linux service is stopped.<br />
* '''ossrecord''': simple command-line recording program.<br />
* '''ossplay''': simple command-line playing program. Supports WAV, AU, VOC and a few other containers.<br />
<br />
= Troubleshooting =<br />
* Like ALSA, you have to lower the main volume and PCM volume to certain degree to avoid noises (depending on your audio chip. I use vol=65,pcm=65 for my via8237)<br />
<br />
* See [http://4front-tech.com/forum/viewtopic.php?t=2358 here] how to set the default soundcard, in case the default choice isn't optimal.<br />
<br />
* If you have a problem getting sound from an application, the 4front wiki may have the [http://www.4front-tech.com/wiki/index.php/Configuring_Applications_for_OSSv4 answer].<br />
<br />
* If you have other issues, try and search or post on the forums at: http://www.4front-tech.com/forum/<br />
<br />
== Skype ==<br />
There's a special Skype version for OSS (QT static build), you can get the PKGBUILD here [http://aur.archlinux.org/packages.php?do_Details=1&ID=13003&O=0&L=0&C=0&K=skype&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd].<br />
A binary is available from skype's download page [http://skype.com/go/getskype-linux-oss].<br />
<br />
= Tips and Tricks =<br />
<br />
== ALSA compatibility ==<br />
OSS provides 2 layers for ALSA compatibility: kernel and alsa lib. The kernel module ("cuckoo") was 100% compatible with all the apps but it no longer works with latest OSS version; The alsa emulation lib in oss distribution is outdated and I don't know where to get the latest version.<br />
<br />
What you can have now is to use ALSA's oss plugin:<br />
# Install alsa-plugins<br />
# Edit ''/etc/asound.conf'':<br />
pcm.oss {<br />
type oss<br />
device /dev/dsp<br />
}<br />
<br />
pcm.!default {<br />
type oss<br />
device /dev/dsp<br />
}<br />
<br />
ctl.oss {<br />
type oss<br />
device /dev/mixer<br />
}<br />
<br />
ctl.!default {<br />
type oss<br />
device /dev/mixer<br />
}<br />
This method doesn't work with programs that detect hardware sound devices (skype 1.3, gizmo, ..)<br />
<br />
== Using your multimedia keys with OSS ==<br />
<br />
Wanting to raise-lower-mute-unmute the sound with your multimedia keys using OSS v4? <br />
<br />
Just make three "scripts" like these (I am assuming you have the bc package installed):<br />
<br />
lowervolume.sh:<br />
VOL=$(ossmix | grep misc.pcm1 | awk '{print $4}' | awk -F : '{print $1}')<br />
VOL=$(echo $VOL-2 | bc)<br />
ossmix misc.pcm1 $VOL:$VOL<br />
<br />
raisevolume.sh:<br />
VOL=$(ossmix | grep misc.pcm1 | awk '{print $4}' | awk -F : '{print $1}')<br />
VOL=$(echo $VOL+2 | bc)<br />
ossmix misc.pcm1 $VOL:$VOL<br />
<br />
mute.sh:<br />
#!/bin/bash<br />
VOLUME=$(cat $HOME/.volume)<br />
if [ -z "$VOLUME" ]; then<br />
VOLUME=$(ossmix | grep misc.pcm1 | awk '{print $4}' | awk -F : '{print $1}')<br />
ossmix misc.pcm1 0:0<br />
echo $VOLUME > $HOME/.volume<br />
else<br />
ossmix misc.pcm1 $VOLUME:$VOLUME<br />
> $HOME/.volume<br />
fi<br />
This will restore the previous volume levels when unmuting. Issue a:<br />
touch $HOME/.volume<br />
before using the first time.<br />
<br />
Then you just have to chmod +x these and set the keyboard shortcuts on your VM.<br />
<br />
== System-wide (software) equalizer effects ==<br />
<br />
NOTES: This requires the use of the old softoss module (the predecessor of vmix) which may not be as good as vmix, wine and gstreamer do not play nice with softoss, and the module will not work with sample rates higher than 48khz.<br />
<br />
We must do a few things to gain access to these effects.<br />
<br />
* If you're running the oss-linux-free daemon right now, stop it by running (as root):<br />
/etc/rc.d/oss-linux-free stop<br />
** On builds 1015 and older, in /usr/lib/oss/etc/installed_drivers remove<br />
vmix<br />
** On 1016 and newer, you should instead pass "vmix_disabled=1" parameter to osscore (via /usr/lib/oss/conf/osscore.conf) to disable vmix.<br />
*in /usr/lib/oss/etc/installed_drivers add<br />
softoss<br />
* in /etc/rc.d/oss-linux-free comment out lines 15 through 20 so that it looks kinda like this<br />
#!/bin/bash<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
case "$1" in<br />
start)<br />
stat_busy "Starting OSS/Open source driver"<br />
# start<br />
/usr/sbin/soundon<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
grep '^softoss' /proc/modules >/dev/null 2>/dev/null<br />
# if [ $? -eq 0 ]; then<br />
# stat_busy "Replacing old \"softoss\" module with \"vmix\""<br />
# rmmod softoss<br />
# modprobe vmix<br />
# sed -i 's/^softoss.*$/vmix/' /usr/lib/oss/etc/installed_drivers<br />
# fi<br />
add_daemon oss4<br />
stat_done<br />
fi<br />
;;<br />
stop)<br />
stat_busy "Saving OSS mixer"<br />
/usr/sbin/savemixer<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
stat_done<br />
fi<br />
grep '^"cuckoo"' /proc/modules >/dev/null 2>/dev/null<br />
if [ $? -eq 0 ]; then<br />
stat_busy "Removing \"cuckoo\" module"<br />
rmmod \"cuckoo\"<br />
fi<br />
stat_busy "Stopping OSS/Open source driver"<br />
/usr/sbin/soundoff<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
rm_daemon oss4<br />
stat_done<br />
fi<br />
;;<br />
restart)<br />
$0 stop<br />
sleep 1<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}"<br />
esac<br />
This keeps the oss-linux-free daemon from replacing softoss with vmix. (Very useful if you wish to switch between softoss and vmix.)<br />
<br />
* start the daemon again (as root of course)<br />
/etc/rc.d/oss-linux-free start<br />
* If no errors are reported, then you may now see/use the effects with either ossmix or ossxmix with<br />
ossmix -d1<br />
or<br />
ossxmix<br />
* you must turn off bipass to actually use the effects<br />
ossmix -d1 effects.eq.bypass OFF<br />
or just uncheck bypass in ossxmix<br />
<br />
* enjoy<br />
<br />
= Unstable version =<br />
<br />
Installing the latest version of Opensound by zaggynl<br /><br />
Status: draft<br /><br />
Allows for: stereo sound from multiple sources<br /><br />
Known issues: recording not properly working[[http://4front-tech.com/forum/viewtopic.php?p=10289#10289]], hissing before and after playback (play a Youtube video to temporarily stop that)<br /><br />
<br /><br />
Prerequisites: Working soundcard, your user is in the audio group, no other sound systems that may intervene (such as ALSA)<br/ ><br />
Execute below commands:<br /><br />
(installing mercurial -distributed version control system-, downloading latest OSS source, compiling and installing, sound test)<br />
* pacman -S mercurial<br />
* cd /usr/src<br />
* sudo hg clone http://mercurial.opensound.com/ oss-devel<br />
* cd ~/<br />
* mkdir oss41build<br />
* cd oss41build/<br />
* sudo sh /usr/src/oss-devel/configure<br />
* sudo make<br />
* sudo make install<br />
* osstest <br />
You should hear a soundtest now :)<br /><br />
<br />
* Get http://aur.archlinux.org/packages/oss-testing/oss-testing/oss.rc and put it as /etc/rc.d/oss<br />
* add oss to DAEMONS in rc.conf<br />
<br />
OSS 4.1 (current at time of writing) allowed me to use my Creative X-Fi ExtremeGamer soundcard!<br /><br />
I got my info from https://help.ubuntu.com/community/OpenSound</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Open_Sound_System&diff=48855
Open Sound System
2008-09-05T09:46:00Z
<p>Zaggynl: /* Unstable version */</p>
<hr />
<div>[[Category:Sound (English)]]<br />
[[Category:Audio/Video (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|OSS}}<br />
{{i18n_entry|简体中文|OSS (简体中文)}}<br />
{{i18n_links_end}}<br />
<br />
= Introduction =<br />
The Open Sound System (OSS) from [http://www.opensound.com www.opensound.com] is a commercially-supported sound driver that works on several unix-like systems, including Linux, FreeBSD, and Solaris.<br />
<br />
The OSS was previously proprietary and being open-sourced recently, it has nothing to do with the sub-quality OSS/free in early linux kernels.<br />
<br />
Pros:<br />
* Transparent software mixing in kernel space ('''virtual mixer'''), up to 18 virtual sound devices (unlike ALSA's dmix, which works in user-space via ALSA lib).<br />
* Per-application mixer volume.<br />
* Much better sound quality for several onboard audio chips.<br />
<br />
Cons:<br />
* Software-emulated 3D enhancement, reverb effect, and equalizer have not yet been added to the new mixing engine in oss v4.<br />
<br />
= Installation =<br />
* Install package<br />
** Get the PKGBUILD:<br />
*** http://aur.archlinux.org/packages.php?do_Details=1&ID=14421<br />
*** Or the experimental http://aur.archlinux.org/packages.php?ID=17029<br />
** Extract the files from the tarball:<br />
*** <tt>tar -zxvf oss-filename.tar.gz</tt><br />
**Enter the directory created by expanding the tarball and install the package:<br />
*** <tt>makepkg -i</tt><br />
NOTE: Perform this command as a normal user. Do not run it as root or with sudo.<br />
<br />
* Start oss-linux:<br />
** Add ''!soundcore'' to <tt>MODULES</tt> in ''/etc/rc.conf'' to blacklist it.<br />
** Reboot to clean up alsa drivers, or manually unload the module ''soundcore'' and all other modules depending on it.<br />
** Run <tt>/etc/rc.d/oss-linux-free start</tt> (or oss-linux in case of the older, proprietary package), or add it to <tt>DAEMONS</tt> in ''/etc/rc.conf''<br />
<br />
= Configuration =<br />
''Your sound card should not need any configuration to work properly''<br />
<br />
Config files used to load oss drivers are under ''/usr/lib/oss/conf''. Do not edit these files directly, instead you should use ''/etc/modprobe.conf''. Every file under /usr/lib/oss/conf is named MODULE_NAME.conf and all the options are passed to modprobe when you're starting oss-linux. So the following two methods are actually doing the same thing:<br />
<br />
(/usr/lib/oss/conf/osscore.conf)<br />
max_intrate=1000<br />
src_quality=4<br />
(/etc/modprobe.conf)<br />
options osscore max_intrate=1000 src_quality=4<br />
<small>NOTE: This is merely an example, it is ''not'' recommended to use these parameters unless you know what you're doing.</small><br />
<br />
To get the list of the drivers you use, run <tt>ossdetect -v</tt> and check the file <tt>/usr/lib/oss/etc/installed_drivers</tt>.<br />
<br />
Other parameters: see the comments in<br />
/usr/lib/oss/conf/osscore.conf<br />
/usr/lib/oss/conf/ossusb.conf<br />
/usr/lib/oss/conf/YOUR_AUDIO_DRIVER.conf<br />
<br />
= Programs =<br />
* '''/etc/rc.d/oss-linux''': oss-linux service.<br />
* '''/etc/rc.d/oss-linux-free''': same as above, but for the free version.<br />
* '''ossinfo''': show list of sound devices and their status; passing argument "-v9" to get details including which programs use them.<br />
* '''ossmix''': command-line mixer, where you can configure volume, recording source and special sound effects (surround, reverb, etc).<br />
* '''ossxmix''': same as ossmix except for that it provides a GUI using gtk2.<br />
* '''savemixer''': save your current mixer settings (need superuser) or restore them, called automatically when the oss-linux service is stopped.<br />
* '''ossrecord''': simple command-line recording program.<br />
* '''ossplay''': simple command-line playing program. Supports WAV, AU, VOC and a few other containers.<br />
<br />
= Troubleshooting =<br />
* Like ALSA, you have to lower the main volume and PCM volume to certain degree to avoid noises (depending on your audio chip. I use vol=65,pcm=65 for my via8237)<br />
<br />
* See [http://4front-tech.com/forum/viewtopic.php?t=2358 here] how to set the default soundcard, in case the default choice isn't optimal.<br />
<br />
* If you have a problem getting sound from an application, the 4front wiki may have the [http://www.4front-tech.com/wiki/index.php/Configuring_Applications_for_OSSv4 answer].<br />
<br />
* If you have other issues, try and search or post on the forums at: http://www.4front-tech.com/forum/<br />
<br />
== Skype ==<br />
There's a special Skype version for OSS (QT static build), you can get the PKGBUILD here [http://aur.archlinux.org/packages.php?do_Details=1&ID=13003&O=0&L=0&C=0&K=skype&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd].<br />
A binary is available from skype's download page [http://skype.com/go/getskype-linux-oss].<br />
<br />
= Tips and Tricks =<br />
<br />
== ALSA compatibility ==<br />
OSS provides 2 layers for ALSA compatibility: kernel and alsa lib. The kernel module ("cuckoo") was 100% compatible with all the apps but it no longer works with latest OSS version; The alsa emulation lib in oss distribution is outdated and I don't know where to get the latest version.<br />
<br />
What you can have now is to use ALSA's oss plugin:<br />
# Install alsa-plugins<br />
# Edit ''/etc/asound.conf'':<br />
pcm.oss {<br />
type oss<br />
device /dev/dsp<br />
}<br />
<br />
pcm.!default {<br />
type oss<br />
device /dev/dsp<br />
}<br />
<br />
ctl.oss {<br />
type oss<br />
device /dev/mixer<br />
}<br />
<br />
ctl.!default {<br />
type oss<br />
device /dev/mixer<br />
}<br />
This method doesn't work with programs that detect hardware sound devices (skype 1.3, gizmo, ..)<br />
<br />
== Using your multimedia keys with OSS ==<br />
<br />
Wanting to raise-lower-mute-unmute the sound with your multimedia keys using OSS v4? <br />
<br />
Just make three "scripts" like these (I am assuming you have the bc package installed):<br />
<br />
lowervolume.sh:<br />
VOL=$(ossmix | grep misc.pcm1 | awk '{print $4}' | awk -F : '{print $1}')<br />
VOL=$(echo $VOL-2 | bc)<br />
ossmix misc.pcm1 $VOL:$VOL<br />
<br />
raisevolume.sh:<br />
VOL=$(ossmix | grep misc.pcm1 | awk '{print $4}' | awk -F : '{print $1}')<br />
VOL=$(echo $VOL+2 | bc)<br />
ossmix misc.pcm1 $VOL:$VOL<br />
<br />
mute.sh:<br />
#!/bin/bash<br />
VOLUME=$(cat $HOME/.volume)<br />
if [ -z "$VOLUME" ]; then<br />
VOLUME=$(ossmix | grep misc.pcm1 | awk '{print $4}' | awk -F : '{print $1}')<br />
ossmix misc.pcm1 0:0<br />
echo $VOLUME > $HOME/.volume<br />
else<br />
ossmix misc.pcm1 $VOLUME:$VOLUME<br />
> $HOME/.volume<br />
fi<br />
This will restore the previous volume levels when unmuting. Issue a:<br />
touch $HOME/.volume<br />
before using the first time.<br />
<br />
Then you just have to chmod +x these and set the keyboard shortcuts on your VM.<br />
<br />
== System-wide (software) equalizer effects ==<br />
<br />
NOTES: This requires the use of the old softoss module (the predecessor of vmix) which may not be as good as vmix, wine and gstreamer do not play nice with softoss, and the module will not work with sample rates higher than 48khz.<br />
<br />
We must do a few things to gain access to these effects.<br />
<br />
* If you're running the oss-linux-free daemon right now, stop it by running (as root):<br />
/etc/rc.d/oss-linux-free stop<br />
** On builds 1015 and older, in /usr/lib/oss/etc/installed_drivers remove<br />
vmix<br />
** On 1016 and newer, you should instead pass "vmix_disabled=1" parameter to osscore (via /usr/lib/oss/conf/osscore.conf) to disable vmix.<br />
*in /usr/lib/oss/etc/installed_drivers add<br />
softoss<br />
* in /etc/rc.d/oss-linux-free comment out lines 15 through 20 so that it looks kinda like this<br />
#!/bin/bash<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
case "$1" in<br />
start)<br />
stat_busy "Starting OSS/Open source driver"<br />
# start<br />
/usr/sbin/soundon<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
grep '^softoss' /proc/modules >/dev/null 2>/dev/null<br />
# if [ $? -eq 0 ]; then<br />
# stat_busy "Replacing old \"softoss\" module with \"vmix\""<br />
# rmmod softoss<br />
# modprobe vmix<br />
# sed -i 's/^softoss.*$/vmix/' /usr/lib/oss/etc/installed_drivers<br />
# fi<br />
add_daemon oss4<br />
stat_done<br />
fi<br />
;;<br />
stop)<br />
stat_busy "Saving OSS mixer"<br />
/usr/sbin/savemixer<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
stat_done<br />
fi<br />
grep '^"cuckoo"' /proc/modules >/dev/null 2>/dev/null<br />
if [ $? -eq 0 ]; then<br />
stat_busy "Removing \"cuckoo\" module"<br />
rmmod \"cuckoo\"<br />
fi<br />
stat_busy "Stopping OSS/Open source driver"<br />
/usr/sbin/soundoff<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
rm_daemon oss4<br />
stat_done<br />
fi<br />
;;<br />
restart)<br />
$0 stop<br />
sleep 1<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}"<br />
esac<br />
This keeps the oss-linux-free daemon from replacing softoss with vmix. (Very useful if you wish to switch between softoss and vmix.)<br />
<br />
* start the daemon again (as root of course)<br />
/etc/rc.d/oss-linux-free start<br />
* If no errors are reported, then you may now see/use the effects with either ossmix or ossxmix with<br />
ossmix -d1<br />
or<br />
ossxmix<br />
* you must turn off bipass to actually use the effects<br />
ossmix -d1 effects.eq.bypass OFF<br />
or just uncheck bypass in ossxmix<br />
<br />
* enjoy<br />
<br />
= Unstable version =<br />
<br />
Installing the latest version of Opensound by zaggynl<br /><br />
Status: draft<br /><br />
Allows for stereo sound from multiple sources but hisses before and after playback sometimes, haven't found out what the cause it :(<br /><br />
<br /><br />
prerequisites: working soundcard, your user is in the audio group, no other sound systems that may intervene<br/ ><br />
<br />
* pacman -S mercurial<br />
* cd /usr/src<br />
* sudo hg clone http://mercurial.opensound.com/ oss-devel<br />
* cd ~/<br />
* mkdir oss41build<br />
* cd oss41build/<br />
* sudo sh /usr/src/oss-devel/configure<br />
* sudo make<br />
* sudo make install<br />
* osstest <br />
You should hear a soundtest now :)<br /><br />
<br />
* Get http://aur.archlinux.org/packages/oss-testing/oss-testing/oss.rc and put it as /etc/rc.d/oss<br />
* add oss to DAEMONS in rc.conf<br />
<br />
OSS 4.1 (current at time of writing) allowed me to use my Creative X-Fi ExtremeGamer soundcard!<br />
I got my info from https://help.ubuntu.com/community/OpenSound</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Opensound&diff=48792
Opensound
2008-09-04T16:20:00Z
<p>Zaggynl: Replacing page with 'http://wiki.archlinux.org/index.php/OSS'</p>
<hr />
<div>http://wiki.archlinux.org/index.php/OSS</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Open_Sound_System&diff=48790
Open Sound System
2008-09-04T16:17:44Z
<p>Zaggynl: </p>
<hr />
<div>[[Category:Sound (English)]]<br />
[[Category:Audio/Video (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|OSS}}<br />
{{i18n_entry|简体中文|OSS (简体中文)}}<br />
{{i18n_links_end}}<br />
<br />
= Introduction =<br />
The Open Sound System (OSS) from [http://www.opensound.com www.opensound.com] is a commercially-supported sound driver that works on several unix-like systems, including Linux, FreeBSD, and Solaris.<br />
<br />
The OSS was previously proprietary and being open-sourced recently, it has nothing to do with the sub-quality OSS/free in early linux kernels.<br />
<br />
Pros:<br />
* Transparent software mixing in kernel space ('''virtual mixer'''), up to 18 virtual sound devices (unlike ALSA's dmix, which works in user-space via ALSA lib).<br />
* Per-application mixer volume.<br />
* Much better sound quality for several onboard audio chips.<br />
<br />
Cons:<br />
* Software-emulated 3D enhancement, reverb effect, and equalizer have not yet been added to the new mixing engine in oss v4.<br />
<br />
= Installation =<br />
* Install package<br />
** Get the PKGBUILD:<br />
*** http://aur.archlinux.org/packages.php?do_Details=1&ID=14421<br />
** Extract the files from the tarball:<br />
*** <tt>tar -zxvf oss-filename.tar.gz</tt><br />
**Enter the directory created by expanding the tarball and install the package:<br />
*** <tt>makepkg -i</tt><br />
NOTE: Perform this command as a normal user. Do not run it as root or with sudo.<br />
<br />
* Start oss-linux:<br />
** Add ''!soundcore'' to <tt>MODULES</tt> in ''/etc/rc.conf'' to blacklist it.<br />
** Reboot to clean up alsa drivers, or manually unload the module ''soundcore'' and all other modules depending on it.<br />
** Run <tt>/etc/rc.d/oss-linux-free start</tt> (or oss-linux in case of the older, proprietary package), or add it to <tt>DAEMONS</tt> in ''/etc/rc.conf''<br />
<br />
= Configuration =<br />
''Your sound card should not need any configuration to work properly''<br />
<br />
Config files used to load oss drivers are under ''/usr/lib/oss/conf''. Do not edit these files directly, instead you should use ''/etc/modprobe.conf''. Every file under /usr/lib/oss/conf is named MODULE_NAME.conf and all the options are passed to modprobe when you're starting oss-linux. So the following two methods are actually doing the same thing:<br />
<br />
(/usr/lib/oss/conf/osscore.conf)<br />
max_intrate=1000<br />
src_quality=4<br />
(/etc/modprobe.conf)<br />
options osscore max_intrate=1000 src_quality=4<br />
<small>NOTE: This is merely an example, it is ''not'' recommended to use these parameters unless you know what you're doing.</small><br />
<br />
To get the list of the drivers you use, run <tt>ossdetect -v</tt> and check the file <tt>/usr/lib/oss/etc/installed_drivers</tt>.<br />
<br />
Other parameters: see the comments in<br />
/usr/lib/oss/conf/osscore.conf<br />
/usr/lib/oss/conf/ossusb.conf<br />
/usr/lib/oss/conf/YOUR_AUDIO_DRIVER.conf<br />
<br />
= Programs =<br />
* '''/etc/rc.d/oss-linux''': oss-linux service.<br />
* '''/etc/rc.d/oss-linux-free''': same as above, but for the free version.<br />
* '''ossinfo''': show list of sound devices and their status; passing argument "-v9" to get details including which programs use them.<br />
* '''ossmix''': command-line mixer, where you can configure volume, recording source and special sound effects (surround, reverb, etc).<br />
* '''ossxmix''': same as ossmix except for that it provides a GUI using gtk2.<br />
* '''savemixer''': save your current mixer settings (need superuser) or restore them, called automatically when the oss-linux service is stopped.<br />
* '''ossrecord''': simple command-line recording program.<br />
* '''ossplay''': simple command-line playing program. Supports WAV, AU, VOC and a few other containers.<br />
<br />
= Troubleshooting =<br />
* Like ALSA, you have to lower the main volume and PCM volume to certain degree to avoid noises (depending on your audio chip. I use vol=65,pcm=65 for my via8237)<br />
<br />
* See [http://4front-tech.com/forum/viewtopic.php?t=2358 here] how to set the default soundcard, in case the default choice isn't optimal.<br />
<br />
* If you have a problem getting sound from an application, the 4front wiki may have the [http://www.4front-tech.com/wiki/index.php/Configuring_Applications_for_OSSv4 answer].<br />
<br />
* If you have other issues, try and search or post on the forums at: http://www.4front-tech.com/forum/<br />
<br />
== Skype ==<br />
There's a special Skype version for OSS (QT static build), you can get the PKGBUILD here [http://aur.archlinux.org/packages.php?do_Details=1&ID=13003&O=0&L=0&C=0&K=skype&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd].<br />
A binary is available from skype's download page [http://skype.com/go/getskype-linux-oss].<br />
<br />
= Tips and Tricks =<br />
<br />
== ALSA compatibility ==<br />
OSS provides 2 layers for ALSA compatibility: kernel and alsa lib. The kernel module ("cuckoo") was 100% compatible with all the apps but it no longer works with latest OSS version; The alsa emulation lib in oss distribution is outdated and I don't know where to get the latest version.<br />
<br />
What you can have now is to use ALSA's oss plugin:<br />
# Install alsa-plugins<br />
# Edit ''/etc/asound.conf'':<br />
pcm.oss {<br />
type oss<br />
device /dev/dsp<br />
}<br />
<br />
pcm.!default {<br />
type oss<br />
device /dev/dsp<br />
}<br />
<br />
ctl.oss {<br />
type oss<br />
device /dev/mixer<br />
}<br />
<br />
ctl.!default {<br />
type oss<br />
device /dev/mixer<br />
}<br />
This method doesn't work with programs that detect hardware sound devices (skype 1.3, gizmo, ..)<br />
<br />
== Using your multimedia keys with OSS ==<br />
<br />
Wanting to raise-lower-mute-unmute the sound with your multimedia keys using OSS v4? <br />
<br />
Just make three "scripts" like these (I am assuming you have the bc package installed):<br />
<br />
lowervolume.sh:<br />
VOL=$(ossmix | grep misc.pcm1 | awk '{print $4}' | awk -F : '{print $1}')<br />
VOL=$(echo $VOL-2 | bc)<br />
ossmix misc.pcm1 $VOL:$VOL<br />
<br />
raisevolume.sh:<br />
VOL=$(ossmix | grep misc.pcm1 | awk '{print $4}' | awk -F : '{print $1}')<br />
VOL=$(echo $VOL+2 | bc)<br />
ossmix misc.pcm1 $VOL:$VOL<br />
<br />
mute.sh:<br />
#!/bin/bash<br />
VOLUME=$(cat $HOME/.volume)<br />
if [ -z "$VOLUME" ]; then<br />
VOLUME=$(ossmix | grep misc.pcm1 | awk '{print $4}' | awk -F : '{print $1}')<br />
ossmix misc.pcm1 0:0<br />
echo $VOLUME > $HOME/.volume<br />
else<br />
ossmix misc.pcm1 $VOLUME:$VOLUME<br />
> $HOME/.volume<br />
fi<br />
This will restore the previous volume levels when unmuting. Issue a:<br />
touch $HOME/.volume<br />
before using the first time.<br />
<br />
Then you just have to chmod +x these and set the keyboard shortcuts on your VM.<br />
<br />
== System-wide (software) equalizer effects ==<br />
<br />
NOTES: This requires the use of the old softoss module (the predecessor of vmix) which may not be as good as vmix, wine and gstreamer do not play nice with softoss, and the module will not work with sample rates higher than 48khz.<br />
<br />
We must do a few things to gain access to these effects.<br />
<br />
* If you're running the oss-linux-free daemon right now, stop it by running (as root):<br />
/etc/rc.d/oss-linux-free stop<br />
** On builds 1015 and older, in /usr/lib/oss/etc/installed_drivers remove<br />
vmix<br />
** On 1016 and newer, you should instead pass "vmix_disabled=1" parameter to osscore (via /usr/lib/oss/conf/osscore.conf) to disable vmix.<br />
*in /usr/lib/oss/etc/installed_drivers add<br />
softoss<br />
* in /etc/rc.d/oss-linux-free comment out lines 15 through 20 so that it looks kinda like this<br />
#!/bin/bash<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
case "$1" in<br />
start)<br />
stat_busy "Starting OSS/Open source driver"<br />
# start<br />
/usr/sbin/soundon<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
grep '^softoss' /proc/modules >/dev/null 2>/dev/null<br />
# if [ $? -eq 0 ]; then<br />
# stat_busy "Replacing old \"softoss\" module with \"vmix\""<br />
# rmmod softoss<br />
# modprobe vmix<br />
# sed -i 's/^softoss.*$/vmix/' /usr/lib/oss/etc/installed_drivers<br />
# fi<br />
add_daemon oss4<br />
stat_done<br />
fi<br />
;;<br />
stop)<br />
stat_busy "Saving OSS mixer"<br />
/usr/sbin/savemixer<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
stat_done<br />
fi<br />
grep '^"cuckoo"' /proc/modules >/dev/null 2>/dev/null<br />
if [ $? -eq 0 ]; then<br />
stat_busy "Removing \"cuckoo\" module"<br />
rmmod \"cuckoo\"<br />
fi<br />
stat_busy "Stopping OSS/Open source driver"<br />
/usr/sbin/soundoff<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
rm_daemon oss4<br />
stat_done<br />
fi<br />
;;<br />
restart)<br />
$0 stop<br />
sleep 1<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}"<br />
esac<br />
This keeps the oss-linux-free daemon from replacing softoss with vmix. (Very useful if you wish to switch between softoss and vmix.)<br />
<br />
* start the daemon again (as root of course)<br />
/etc/rc.d/oss-linux-free start<br />
* If no errors are reported, then you may now see/use the effects with either ossmix or ossxmix with<br />
ossmix -d1<br />
or<br />
ossxmix<br />
* you must turn off bipass to actually use the effects<br />
ossmix -d1 effects.eq.bypass OFF<br />
or just uncheck bypass in ossxmix<br />
<br />
* enjoy<br />
<br />
= Unstable version =<br />
<br />
Installing the latest version of Opensound by zaggynl<br /><br />
Status: draft<br /><br />
Allows for stereo sound from multiple sources but hisses before and after playing something, haven't found out what the cause it :(<br /><br />
<br /><br />
prerequisites: working soundcard, your user is in the audio group, no other sound systems that may intervene<br/ ><br />
<br />
* pacman -S mercurial<br />
* cd /usr/src<br />
* sudo hg clone http://mercurial.opensound.com/ oss-devel<br />
* cd ~/<br />
* mkdir oss41build<br />
* cd oss41build/<br />
* sudo sh /usr/src/oss-devel/configure<br />
* sudo make<br />
* sudo make install<br />
* osstest <br />
Uou should hear a soundtest now :)<br /><br />
<br />
* nano /etc/rc.d/oss<br />
* copy below text into nano<br />
<br />
#!/bin/bash<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
case "$1" in<br />
start)<br />
stat_busy "Starting OSS/Open source driver"<br />
# start<br />
/usr/sbin/soundon<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
grep '^softoss' /proc/modules >/dev/null 2>/dev/null<br />
if [ $? -eq 0 ]; then<br />
stat_busy "Replacing old \"softoss\" module with \"vmix\""<br />
rmmod softoss<br />
modprobe vmix<br />
sed -i 's/^softoss.*$/vmix/' /usr/lib/oss/etc/installed_drivers<br />
fi<br />
add_daemon oss4<br />
stat_done<br />
fi<br />
;;<br />
stop)<br />
stat_busy "Saving OSS mixer"<br />
/usr/sbin/savemixer<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
stat_done<br />
fi<br />
grep '^"cuckoo"' /proc/modules >/dev/null 2>/dev/null<br />
if [ $? -eq 0 ]; then<br />
stat_busy "Removing \"cuckoo\" module"<br />
rmmod \"cuckoo\"<br />
fi<br />
stat_busy "Stopping OSS/Open source driver"<br />
/usr/sbin/soundoff<br />
if [ $? -gt 0 ]; then<br />
stat_fail<br />
else<br />
rm_daemon oss4<br />
stat_done<br />
fi<br />
;;<br />
restart)<br />
$0 stop<br />
sleep 1<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}"<br />
esac<br />
<br />
* save and exit (Ctrl+O, Ctrl+X)<br />
* add oss to DAEMONS in rc.conf<br />
<br />
<br />
ossxmix or ossmix for controlling volume/muting and the such.<br />
OSS 4.1 (current at time of writing) allowed me to use my Creative X-Fi ExtremeGamer soundcard!<br />
I got my info from https://help.ubuntu.com/community/OpenSound</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Opensound&diff=48735
Opensound
2008-09-02T19:00:20Z
<p>Zaggynl: </p>
<hr />
<div>'''Installing the latest version of Opensound''' by zaggynl <br /><br />
status: draft<br /><br />
Allows for stereo sound from multiple sources but hisses before and after playing something, haven't found out what the cause it :(<br /><br />
<br /><br />
prerequisites: working soundcard, your user is in the audio group<br />
*pacman -S mercurial<br />
*cd /usr/src<br />
*sudo hg clone http://mercurial.opensound.com/ oss-devel<br />
*cd ~/<br />
*mkdir oss41build<br />
*cd oss41build/<br />
*sudo sh /usr/src/oss-devel/configure<br />
*sudo make<br />
*sudo make install<br />
*osstest<br />
<br /><br />
you should hear a soundtest now :)<br />
<br /><br />
ossxmix or ossmix for controlling volume/muting and the such.<br />
<br /><br />
OSS 4.1 (current at time of writing) allowed me to use my Creative X-Fi ExtremeGamer soundcard!<br />
<br /><br />
I got my info from https://help.ubuntu.com/community/OpenSound</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Opensound&diff=48734
Opensound
2008-09-02T18:59:29Z
<p>Zaggynl: </p>
<hr />
<div>'''Installing the latest version of Opensound''' by zaggynl <br /><br />
status: draft<br /><br />
Allows for stereo sound from multiple sources but hisses before and after playing something, haven't found out what the cause it :(<br /><br />
<br /><br />
prerequisites: working soundcard, your user is in the audio group<br />
*pacman -S mercurial<br />
*cd /usr/src<br />
*sudo hg clone http://mercurial.opensound.com/ oss-devel<br />
*cd ~/<br />
*mkdir oss41build<br />
*cd oss41build/<br />
*sudo sh /usr/src/oss-devel/configure<br />
*sudo make<br />
*sudo make install<br />
*osstest<br />
<br /><br />
you should hear a soundtest now :)<br />
<br /><br />
ossxmix or ossmix for controlling volume/muting and the such.<br />
<br /><br />
OSS 4.1 (current at time of writing) allowed me to use my Creative X-Fi ExtremeGamer soundcard!<br />
<br /><br />
I got my info from https://help.ubuntu.com/community/OpenSound?action=fullsearch&context=180&value=foobar2000&titlesearch=Titles</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Opensound&diff=48733
Opensound
2008-09-02T18:58:01Z
<p>Zaggynl: </p>
<hr />
<div>'''Installing the latest version of Opensound''' by zaggynl <br /><br />
status: draft<br /><br />
Allows for stereo sound from multiple sources but hisses before and after playing something, haven't found out what the cause it :(<br /><br />
<br /><br />
*pacman -S mercurial<br />
*cd /usr/src<br />
*sudo hg clone http://mercurial.opensound.com/ oss-devel<br />
*cd ~/<br />
*mkdir oss41build<br />
*cd oss41build/<br />
*sudo sh /usr/src/oss-devel/configure<br />
*sudo make<br />
*sudo make install<br />
*osstest<br />
<br /><br />
you should hear a soundtest now :)<br />
<br /><br />
ossxmix or ossmix for controlling volume/muting and the such.<br />
<br /><br />
OSS 4.1 (current at time of writing) allowed me to use my Creative X-Fi ExtremeGamer soundcard!<br />
<br /><br />
I got my info from https://help.ubuntu.com/community/OpenSound?action=fullsearch&context=180&value=foobar2000&titlesearch=Titles</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=Opensound&diff=48732
Opensound
2008-09-02T18:44:42Z
<p>Zaggynl: New page: '''Installing the latest version of Opensound''' <br /> status: draft<br /> Allows for stereo sound from multiple sources but hisses before and after playing something, haven't found out w...</p>
<hr />
<div>'''Installing the latest version of Opensound''' <br /><br />
status: draft<br /><br />
Allows for stereo sound from multiple sources but hisses before and after playing something, haven't found out what the cause it :(<br /><br />
<br /><br />
*pacman -S mercurial<br />
*cd /usr/src<br />
*sudo hg clone http://mercurial.opensound.com/ oss-devel<br />
*cd ~/<br />
*mkdir oss41build<br />
*cd oss41build/<br />
*sudo sh /usr/src/oss-devel/configure<br />
*sudo make<br />
*sudo make install<br />
*osstest<br />
<br /><br />
you should hear a soundtest now :)<br />
<br /><br />
ossxmix or ossmix for controlling volume/muting and the such.<br />
<br /><br />
OSS 4.1 (current at time of writing) allowed me to use my Creative X-Fi ExtremeGamer soundcard!<br />
<br /><br />
I got my info from https://help.ubuntu.com/community/OpenSound?action=fullsearch&context=180&value=foobar2000&titlesearch=Titles</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=X11vnc&diff=41823
X11vnc
2008-05-23T20:21:33Z
<p>Zaggynl: </p>
<hr />
<div>disclaimer: I just wrote this, might break/not work/explode in your face.<br />
<br />
Very short howto on getting x11vnc to work over ssh with PuTTy<br />
<br />
Requirements: sshd installed and configured<br />
<br />
First, install x11vnc: pacman -S x11vnc<br />
<br />
start the X environment:<br />
startx (from non-root shell)<br />
or<br />
sudo /etc/rc.d/gdm start (or just as root)<br />
<br />
<br />
run as user:(using startx)<br /><br />
x11vnc -display :0 -ncache 10 -localhost -loop<br />
<br />
run as root: (if you have gdm running, sudo doesn't seem to work with this?)<br /><br />
x11vnc -display :0 -auth /var/lib/gdm/:0.Xauth -ncache 10 -localhost -loop<br /><br />
<br />
<br />
x11vnc will now run verbose mode, that is, spamming all over the terminal.<br /><br />
To put the spam in a logfile and keep it quiet, you can run it like this:<br /><br />
x11vnc -display :0 -auth /var/lib/gdm/:0.Xauth -ncache 10 -localhost -loop >> /var/log/x11vnc.log 2>&1 &<br /><br />
<br />
to keep track of things if you want (as root): tail -f /var/log/x11vnc.log<br /><br />
<br />
picture and tunneling howto borrowed from: [http://tombuntu.com/index.php/2007/06/27/remote-access-from-windows-x11vnc/]<br /><br />
<br />
Enter the connection details - DONT HIT OPEN YET<br /><br />
ip address and port, for example: 192.168.2.123 1234<br /><br />
[[Image:http://img297.imageshack.us/img297/369/putty1qz0.jpg]]<br />
<br />
Goto SSH->Tunnels<br /><br />
at Source port: 5900<br /><br />
at Destination: localhost:5900<br /><br />
leave the radiobuttons below it as they are.<br /><br />
[[Image:http://img382.imageshack.us/img382/2130/putty2dd1.jpg]]<br />
<br />
now hit Open<br />
<br />
now open a vncviewer<br /><br />
I've used realvnc(free) for win32: [http://www.realvnc.com/cgi-bin/download.cgi] (hit download and click the green download button after "VNC Personal Edition Viewer for Windows (x86, x64 & ia64)")<br /><br />
Connect to localhost:5900<br />
<br />
Note: every user that can connect to your pc with ssh can now use X!</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=X11vnc&diff=41822
X11vnc
2008-05-23T20:21:15Z
<p>Zaggynl: </p>
<hr />
<div>disclaimer: I just wrote this, might break/not work/explode in your face.<br />
<br />
Very short howto on getting x11vnc to work over ssh with PuTTy<br />
<br />
Requirements: sshd installed and configured<br />
<br />
First, install x11vnc: pacman -S x11vnc<br />
<br />
start the X environment:<br />
startx (from non-root shell)<br />
or<br />
sudo /etc/rc.d/gdm start (or just as root)<br />
<br />
<br />
run as user:(using startx)<br /><br />
x11vnc -display :0 -ncache 10 -localhost -loop<br />
<br />
run as root: (if you have gdm running, sudo doesn't seem to work with this?)<br /><br />
x11vnc -display :0 -auth /var/lib/gdm/:0.Xauth -ncache 10 -localhost -loop<br /><br />
<br />
<br />
x11vnc will now run verbose mode, that is, spamming all over the terminal.<br /><br />
To put the spam in a logfile and keep it quiet, you can run it like this:<br /><br />
x11vnc -display :0 -auth /var/lib/gdm/:0.Xauth -ncache 10 -localhost -loop >> /var/log/x11vnc.log 2>&1 &<br /><br />
<br />
to keep track of things if you want (as root): tail -f /var/log/x11vnc.log<br /><br />
<br />
picture and tunneling howto borrowed from: [http://tombuntu.com/index.php/2007/06/27/remote-access-from-windows-x11vnc/]<br /><br />
<br />
Enter the connection details - DONT HIT OPEN YET<br /><br />
ip address and port, for example: 192.168.2.123 1234<br /><br />
[[Image:http://img297.imageshack.us/img297/369/putty1qz0.jpg]]<br />
<br />
Goto SSH->Tunnels<br /><br />
at Source port: 5900<br /><br />
at Destination: localhost:5900<br /><br />
leave the radiobuttons below it as they are.<br /><br />
[[Image:http://img382.imageshack.us/img382/2130/putty2dd1.jpg]]<br />
<br />
Connect to ssh, login<br />
<br />
now open a vncviewer<br /><br />
I've used realvnc(free) for win32: [http://www.realvnc.com/cgi-bin/download.cgi] (hit download and click the green download button after "VNC Personal Edition Viewer for Windows (x86, x64 & ia64)")<br /><br />
Connect to localhost:5900<br />
<br />
Note: every user that can connect to your pc with ssh can now use X!</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=X11vnc&diff=41821
X11vnc
2008-05-23T20:15:47Z
<p>Zaggynl: </p>
<hr />
<div>disclaimer: I just wrote this, might break/not work/explode in your face.<br />
<br />
Very short howto on getting x11vnc to work over ssh with PuTTy<br />
<br />
Requirements: sshd installed and configured<br />
<br />
First, install x11vnc: pacman -S x11vnc<br />
<br />
start the X environment:<br />
startx (from non-root shell)<br />
or<br />
sudo /etc/rc.d/gdm start (or just as root)<br />
<br />
<br />
run as user:(using startx)<br /><br />
x11vnc -display :0 -ncache 10 -localhost -loop<br />
<br />
run as root: (if you have gdm running, sudo doesn't seem to work with this?)<br /><br />
x11vnc -display :0 -auth /var/lib/gdm/:0.Xauth -ncache 10 -localhost -loop<br /><br />
<br />
<br />
x11vnc will now run verbose mode, that is, spamming all over the terminal.<br /><br />
To put the spam in a logfile and keep it quiet, you can run it like this:<br /><br />
x11vnc -display :0 -auth /var/lib/gdm/:0.Xauth -ncache 10 -localhost -loop >> /var/log/x11vnc.log 2>&1 &<br /><br />
<br />
to keep track of things if you want (as root): tail -f /var/log/x11vnc.log<br /><br />
<br />
picture and tunneling howto borrowed from: [http://tombuntu.com/index.php/2007/06/27/remote-access-from-windows-x11vnc/]<br /><br />
<br />
Enter the connection details - DONT HIT OPEN YET<br /><br />
ip address and port, for example: 192.168.2.123 1234<br /><br />
[[Image:http://img297.imageshack.us/img297/369/putty1qz0.jpg]]<br />
<br />
Goto SSH->Tunnels<br /><br />
at Source port: 5900<br /><br />
at Destination: localhost:5900<br /><br />
leave the radiobuttons below it as they are.<br /><br />
[[Image:http://img382.imageshack.us/img382/2130/putty2dd1.jpg]]<br />
<br />
Connect to ssh, login<br />
<br />
now open a vncviewer<br />
I've used realvnc(free) for win32: [http://www.realvnc.com/cgi-bin/download.cgi] (hit download and click the green download button after "VNC Personal Edition Viewer for Windows (x86, x64 & ia64)")<br /><br />
Connect to localhost:5900<br />
<br />
Note: every user that can connect to your pc with ssh can now use X!</div>
Zaggynl
https://wiki.archlinux.org/index.php?title=X11vnc&diff=41819
X11vnc
2008-05-23T20:08:24Z
<p>Zaggynl: New page: Very short howto on getting x11vnc to work over ssh with PuTTy Requirements: sshd installed and configured First, install x11vnc: pacman -S x11vnc start the X environment: startx (from ...</p>
<hr />
<div>Very short howto on getting x11vnc to work over ssh with PuTTy<br />
<br />
Requirements: sshd installed and configured<br />
<br />
First, install x11vnc: pacman -S x11vnc<br />
<br />
start the X environment:<br />
startx (from non-root shell)<br />
or<br />
sudo /etc/rc.d/gdm start (or just as root)<br />
<br />
<br />
run as user:(using startx)<br /><br />
x11vnc -display :0 -ncache 10 -localhost -loop<br />
<br />
run as root: (if you have gdm running, sudo doesn't seem to work with this?)<br /><br />
x11vnc -display :0 -auth /var/lib/gdm/:0.Xauth -ncache 10 -localhost -loop<br /><br />
<br />
<br />
x11vnc will now run verbose mode, that is, spamming all over the terminal.<br /><br />
To put the spam in a logfile and keep it quiet, you can run it like this:<br /><br />
x11vnc -display :0 -auth /var/lib/gdm/:0.Xauth -ncache 10 -localhost -loop >> /var/log/x11vnc.log 2>&1 &<br /><br />
<br />
to keep track of things if you want (as root): tail -f /var/log/x11vnc.log<br /><br />
<br />
picture and tunneling howto borrowed from: [http://tombuntu.com/index.php/2007/06/27/remote-access-from-windows-x11vnc/]<br /><br />
<br />
Enter the connection details - DONT HIT OPEN YET<br /><br />
ip address and port, for example: 192.168.2.123 1234<br /><br />
[[Image:http://img297.imageshack.us/img297/369/putty1qz0.jpg]]<br />
<br />
Goto SSH->Tunnels<br /><br />
at Source port: 5900<br /><br />
at Destination: localhost:5900<br /><br />
leave the radiobuttons below it as they are.<br /><br />
[[Image:http://img382.imageshack.us/img382/2130/putty2dd1.jpg]]<br />
<br />
Connect to ssh, login<br />
<br />
now open a vncviewer<br />
I've used realvnc(free) for win32: [http://www.realvnc.com/cgi-bin/download.cgi] (hit download and click the green download button after "VNC Personal Edition Viewer for Windows (x86, x64 & ia64)")<br /><br />
Connect to localhost:5900<br />
<br />
Note: every user that can connect to your pc with ssh can now use X!</div>
Zaggynl