https://wiki.archlinux.org/api.php?action=feedcontributions&user=Ik12&feedformat=atomArchWiki - User contributions [en]2024-03-28T21:48:09ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Activating_numlock_on_bootup_(Espa%C3%B1ol)&diff=66428Activating numlock on bootup (Español)2009-04-07T20:59:48Z<p>Ik12: Add a in18 entry for the French translation.</p>
<hr />
<div>[[Category:Proceso de arranque (Español)]]<br />
[[Category:Entornos de escritorio (Español)]]<br />
[[Category:Otros recursos para el usuario de escritorio (Español)]]<br />
[[Category:CÓMOs (Español)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Activating Numlock on Bootup}}<br />
{{i18n_entry|简体中文|启动时打开数字键}}<br />
{{i18n_entry|Español|Cómo activar Numlock en el arranque (Español)}}<br />
{{i18n_entry|Français|Activer le pavé numérique au démarrage}}<br />
{{i18n_links_end}}<br />
<br />
===Consolas virtuales 1-6===<br />
<br />
Para activar la tecla numlock durante el arranque normal en las consolas 1-6 (vc/n), añada la siguiente línea a <code>/etc/rc.local</code>:<br />
for i in $(seq 6); do /usr/bin/setleds -D +num < /dev/vc/${i} >/dev/null; done<br />
<br />
<br />
===X window===<br />
<br />
Si utiliza la orden startx para iniciar una sesión de X window, sólo tiene que instalar el paquete numlockx y añadirlo a su archivo <code>~/.xinitrc</code>.<br />
<br />
<br />
Install <code>numlockx</code>:<br />
pacman -S numlockx<br />
<br />
<br />
Añada esto a <code>~/.xinitrc</code> antes de <code>exec</code>:<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Ejecutado por startx (lance su gestor de ventanas desde aquí)<br />
#<br />
<br />
numlockx &<br />
<br />
exec your_window_manager<br />
<br />
<br />
===KDM===<br />
<br />
Si utiliza KDM como gestor de ingreso, añada :<br />
numlockx on<br />
a su archivo <code>/opt/kde/share/config/kdm/Xsetup</code>.<br />
<br />
===Usuarios de KDE ===<br />
<br />
Como alternativa también puede añadir un guión a su directorio ~/.kde/Autostart :<br />
nano ~/.kde/Autostart/numlockx<br />
Añada lo siguiente: <br />
#!/bin/sh<br />
numlockx on<br />
Y hágalo ejecutable:<br />
chmod +x ~/.kde/Autostart/numlockx<br />
<br />
===GDM===<br />
<br />
Los usuarios de GDM pueden añadir el siguiente código al archivo /etc/gdm/Init/Default :<br />
if [ -x /usr/bin/numlockx ]; then<br />
/usr/bin/numlockx on<br />
fi</div>Ik12https://wiki.archlinux.org/index.php?title=Activating_numlock_on_bootup&diff=66427Activating numlock on bootup2009-04-07T20:59:24Z<p>Ik12: Add a in18 entry for the French translation.</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
[[Category:Desktop environments (English)]]<br />
[[Category:Other desktop user's resources (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Activating Numlock on Bootup}}<br />
{{i18n_entry|简体中文|启动时打开数字键}}<br />
{{i18n_entry|Español|Cómo activar Numlock en el arranque}}<br />
{{i18n_entry|Français|Activer le pavé numérique au démarrage}}<br />
{{i18n_links_end}}<br />
<br />
== Virtual Consoles 1-6 ==<br />
<br />
To activate the numlock during normal bootup in virtual consoles 1-6 (vc/n), add the following line to <code>/etc/rc.local</code>:<br />
for vc in /dev/vc/*; do /usr/bin/setleds -D +num < "$vc"; done<br />
<br />
== X Window ==<br />
If you use startx to start your X window session, simply install the numlockx package and add it to your <code>~/.xinitrc</code> file.<br />
<br />
Install <code>numlockx</code>:<br />
# pacman -S numlockx<br />
<br />
Add it to <code>~/.xinitrc</code> before <code>exec</code>:<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
#<br />
<br />
numlockx &<br />
<br />
exec your_window_manager<br />
<br />
=== KDM ===<br />
If you use KDM as a login manager, add :<br />
numlockx on<br />
to your <code>/usr/share/config/kdm/Xsetup</code>.<br />
<br />
=== KDE Users ===<br />
You may alternatively add a script to your ~/.kde/Autostart directory:<br />
$ nano ~/.kde/Autostart/numlockx<br />
Add the following: <br />
#!/bin/sh<br />
numlockx on<br />
And make it executable:<br />
$ chmod +x ~/.kde/Autostart/numlockx<br />
<br />
'''Note:''' There is an option in kcontrol (for kde3) and systemsettings (for kde4) to activate numlock at kde start. but it is currently broken because noone dare to fix something that someone broke (it was working one day ..)<br />
<br />
===GDM===<br />
First make sure that you have numlockx (from extra) installed. Then, GDM users may add the following code to /etc/gdm/Init/Default:<br />
if [ -x /usr/bin/numlockx ]; then<br />
/usr/bin/numlockx on<br />
fi</div>Ik12https://wiki.archlinux.org/index.php?title=Advanced_Linux_Sound_Architecture&diff=65989Advanced Linux Sound Architecture2009-03-30T14:49:14Z<p>Ik12: Added a i18n entry for the french page</p>
<hr />
<div>[[Category:Sound (English)]]<br />
[[Category:Audio/Video (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|ALSA}}<br />
{{i18n_entry|Español|ALSA (Español)}}<br />
{{i18n_entry|Deutsch|ALSA Einrichten}}<br />
{{i18n_entry|Italiano|ALSA (Italiano)}}<br />
{{i18n_entry|Nederlands|ALSA instellen}}<br />
{{i18n_entry|Русский|ALSA_(Russian)}}<br />
{{i18n_entry|Slovensky|Nastavenie ALSA}}<br />
{{i18n_entry|Česky|ALSA (Česky)}}<br />
{{i18n_entry|简体中文|ALSA 安装设置 (简体中文)}}<br />
{{i18n_entry|עברית|הגדרת ALSA}}<br />
{{i18n_entry|Рolski|ALSA Setup (Polski)}}<br />
{{i18n_entry|Português do Brasil|Instalação ALSA}}<br />
{{i18n_entry|ไทย|ALSA Setup (ไทย)}}<br />
{{i18n_entry|Türkçe|ALSA (Türkçe)}}<br />
{{i18n_entry|Français|ALSA (Français)}}<br />
{{i18n_links_end}}<br />
<br />
= Introduction =<br />
The Advanced Linux Sound Architecture (ALSA) is a Linux kernel component intended to provide device drivers for sound cards.<br />
<br />
See [[OSS]] if you are looking for alternatives.<br />
<br />
This document tells how to get ALSA working with 2.6 kernels. Also see how to <br />
[[Allow_multiple_programs_to_play_sound_at_once|allow multiple programs to play sound at once]].<br />
<br />
=Installation=<br />
<br />
==Kernel drivers==<br />
<br />
ALSA has been included in the 2.6 kernels and is included in all arch '''kernel26*''' packages. If you build a custom kernel, do not forget to enable the correct ALSA driver.<br />
<br />
All necessary modules should be detected and loaded automatically by udev. No special configuration has to be done unless you use ISA cards. '''NEVER''' use alsaconf if you have a PCI or ISAPNP sound card, as the entries alsaconf adds to the modprobe.conf file might break udev's autodetection.<br />
<br />
==Userspace utilities==<br />
<br />
* Required for native ALSA programs and administration<br />
# pacman -Sy alsa-lib alsa-utils<br />
* Recommended if you want to use applications with OSS sound support in combination with dmix:<br />
# pacman -S alsa-oss<br />
<br />
All ALSA programs will most likely have alsa-lib as a dependency.<br />
<br />
=Configuration=<br />
==Make sure snd_pcsp gets loaded last==<br />
<br />
By default the kernel ships with snd_pcsp. In most cases this gets loaded before your "actual" sound card. snd_pcsp is an alsa module for your internal pc speaker.<br />
<br />
To have snd_pcsp load last, add the following to<br />
<br />
/etc/modprobe.conf<br />
options snd-pcsp index=2<br />
<br />
If you do not want snd_pcsp to load at all you can add the following to<br />
<br />
/etc/rc.conf<br />
MODULES=(... !snd_pcsp)<br />
<br />
{{Box Note | You will need to unload all your sound modules and reload them for the changes to take affect. It might be easier to reboot. Your choice. }}<br />
<br />
==Making sure the sound modules are loaded==<br />
<br />
You can assume that udev will autodetect your sound properly, including the OSS compatibility modules. You can check this with the command<br />
<br />
$ lsmod|grep '^snd'<br />
snd_usb_audio 69696 0 <br />
snd_usb_lib 13504 1 snd_usb_audio<br />
snd_rawmidi 20064 1 snd_usb_lib<br />
snd_hwdep 7044 1 snd_usb_audio<br />
snd_seq_oss 29412 0 <br />
snd_seq_midi_event 6080 1 snd_seq_oss<br />
snd_seq 46220 4 snd_seq_oss,snd_seq_midi_event<br />
snd_seq_device 6796 3 snd_rawmidi,snd_seq_oss,snd_seq<br />
snd_pcm_oss 45216 0 <br />
snd_mixer_oss 15232 1 snd_pcm_oss<br />
snd_intel8x0 27932 0 <br />
snd_ac97_codec 87648 1 snd_intel8x0<br />
snd_ac97_bus 1792 1 snd_ac97_codec<br />
snd_pcm 76296 4 snd_usb_audio,snd_pcm_oss,snd_intel8x0,snd_ac97_codec<br />
snd_timer 19780 2 snd_seq,snd_pcm<br />
snd 43776 12 snd_usb_audio,snd_rawmidi,snd_hwdep,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer<br />
snd_page_alloc 7944 2 snd_intel8x0,snd_pcm<br />
<br />
If the output looks similar, your sound drivers have been successfully autodetected (note that in this case, snd_intel8x0 and snd_usb_audio are the drivers for the hardware devices). You might also want to check the directory '''/dev/snd''' for the right device files:<br />
<br />
$ ls -l /dev/snd/<br />
total 0<br />
crw-rw---- 1 root audio 116, 0 Apr 8 14:17 controlC0<br />
crw-rw---- 1 root audio 116, 32 Apr 8 14:17 controlC1<br />
crw-rw---- 1 root audio 116, 24 Apr 8 14:17 pcmC0D0c<br />
crw-rw---- 1 root audio 116, 16 Apr 8 14:17 pcmC0D0p<br />
crw-rw---- 1 root audio 116, 25 Apr 8 14:17 pcmC0D1c<br />
crw-rw---- 1 root audio 116, 56 Apr 8 14:17 pcmC1D0c<br />
crw-rw---- 1 root audio 116, 48 Apr 8 14:17 pcmC1D0p<br />
crw-rw---- 1 root audio 116, 1 Apr 8 14:17 seq<br />
crw-rw---- 1 root audio 116, 33 Apr 8 14:17 timer<br />
<br />
If you have at least the devices '''controlC0''' and '''pcmC0D0p''' or similar, then your sound modules have been detected and loaded properly.<br />
<br />
<br />
If this is not the case, your sound modules have not been detected properly. '''If you want any help on IRC or the forums, please post the output of the above commands.''' To solve this, you can try loading the modules manually:<br />
<br />
* Locate the module for your soundcard: [http://www.alsa-project.org/main/index.php/Matrix:Main ALSA Soundcard Matrix] The module will be prefixed with 'snd-' (for example: 'snd-via82xx').<br />
* Load modules:<br />
# modprobe snd-NAME-OF-MODULE<br />
# modprobe snd-pcm-oss<br />
* Check for the device files in '''/dev/snd''' (see above) and/or try if '''alsamixer''' or '''amixer''' have reasonable output.<br />
* Add '''snd-NAME-OF-MODULE''' and '''snd-pcm-oss''' to the list of MODULES in '''/etc/rc.conf''' to ensure they are loaded next time (make sure '''snd-NAME-OF-MODULE''' is before '''snd-pcm-oss''').<br />
<br />
==Unmute the channels and test==<br />
<br />
In this section, we assume that you are logged in as root. If you want to perform these steps as an unprivileged user, you have to skip to the next section ''Setup Permissions'' first.<br />
<br />
* Unmute Soundcard<br />
<br />
The current version of ALSA installs with all channels '''muted by default''', so even if installation completes successfully and all devices are working properly you will hear no sound. You will need to unmute the channels manually. It is recommended to use '<code>alsamixer</code>' to accomplish this. From the alsamixer text ui, the label "MM" below a channel indicates that the channel is muted, and "00" indicates that it is open. Press the 'm' key to toggle MM/00. Use arrow-keys left and right to navigate through the channels and the arrow-keys up and down to adjust the volume. Such things as Master and PCM and possibly Speaker will need to unmuted for your sound to work.<br><br><br />
'''NOTE:''' When using '''<code>amixer</code>''', be sure to '''unmute''' as well as bring volumes up to a specific level in percent, i.e you need to use that % sign. '''<code>amixer</code>''' understands the percent sign (%), not numbers. If you use a number (say, 90) then '''<code>amixer</code>''' will take it as 100%, which can harm your speakers.<br />
<br />
# amixer set Master 90% unmute<br />
# amixer set PCM 85% unmute<br />
<br />
* Try to play a WAV file<br />
<br />
# aplay /usr/share/sounds/alsa/Front_Center.wav<br />
<br />
'''NOTE:''' Some cards need to have digital output muted/turned off in order to hear analog sound. For the Soundblaster Audigy LS mute the IEC958 channel.<br />
<br />
If you cannot hear anything, double check your mixer settings, being sure to unmute PCM, MASTER (and some machines such as the IBM Thinkpad have an additional 'SPEAKER' channel) and try the alsaconf utility as root:<br />
# alsaconf<br />
<br />
* [[Allow multiple programs to play sound at once]]<br />
<br />
==Setup Permissions==<br />
<br />
To be able to use the sound card as a user, follow these steps:<br />
<br />
* Add your user to the audio group:<br />
# gpasswd -a USERNAME audio<br />
<br />
* Log your user out and back in to ensure the audio group is loaded.<br />
<br />
==Restore ALSA Mixer settings at startup==<br />
<br />
* Run 'alsactl' once to create '<code>/etc/asound.state</code>'<br />
<br />
alsactl store<br />
<br />
* Edit '/etc/rc.conf' and add 'alsa' to the list of daemons to start on boot-up. This will store the mixer settings on every shutdown and restore them when you boot.<br />
<br />
* If the mixer settings are not loaded on boot-up, add the following line to '<code>/etc/rc.local</code>'<br />
<br />
alsactl restore<br />
<br />
==Getting SPDIF output==<br />
<br />
(from gralves from the Gentoo forums)<br />
* In GNOME Volume Control, under the Options tab, change the IEC958 to PCM. This option can be enabled in the preferences.<br />
* If you don't have GNOME Volume Control installed,<br />
** Edit /etc/asound.state. This file is where alsasound stores your mixer settings.<br />
** Find a line that says: 'IEC958 Playback Switch'. Near it you will find a line saying value:false. Change it to value:true.<br />
** Now find this line: 'IEC958 Playback AC97-SPSA'. Change its value to 0.<br />
** Restart ALSA.<br />
<br />
Alternative way to enable SPDIF output automatically on login (tested on SoundBlaster Audigy):<br />
* add following lines to /etc/rc.local:<br />
<br />
# Use COAX-digital output<br />
amixer set 'IEC958 Optical' 100 unmute<br />
amixer set 'Audigy Analog/Digital Output Jack' on<br />
<br />
You can see the name of your card's digital output with:<br />
<br />
amixer scontrols<br />
<br />
==KDE Settings==<br />
* Start up KDE:<br />
# startx<br />
<br />
* Set up the volumes as you want them for this user (each user has their own settings):<br />
# alsamixer<br />
<br />
log out and log back in as user xyz to get sound to work (I had to kill x logout then log back in as user xyz, then start x and open firefox and bam audio working on youtube)<br />
<br />
* <b>KDE 3.3</b> Go to K Menu > Multimedia > KMix<br />
** Choose Settings > Configure KMix...<br />
** Uncheck the option "Restore volumes on logon"<br />
** Press OK, and you should be all set. Now your volumes will be the same from the command line or within KDE.<br />
<br />
==System-Wide Equalizer==<br />
Note: This method requires the use of a ladspa plugin which might use quite a bit of cpu when sound plays. In addition, this was made with stereophonic sound (e.g. headphones) in mind.<br />
<br />
* you will need, in addition to the aforementioned userspace utilities, alsa-plugins<br />
pacman -S alsa-plugins<br />
* get the ladspa and swh-plugins packages too if you don't already have them<br />
pacman -S ladspa swh-plugins<br />
* if you haven't already created either an ~/.asoundrc or a /etc/asound.conf file, then create either one<br />
vim ~/.asoundrc<br />
* insert the following into your alsa configuration file (~/.asoundrc or /etc/asound.conf)<br />
pcm.eq {<br />
type ladspa<br><br />
# The output from the EQ can either go direct to a hardware device<br />
# (if you have a hardware mixer, e.g. SBLive/Audigy) or it can go<br />
# to the software mixer shown here.<br />
#slave.pcm "plughw:0,0"<br />
slave.pcm "plug:dmix"<br><br />
# Sometimes you may need to specify the path to the plugins,<br />
# especially if you've just installed them. Once you've logged<br />
# out/restarted this shouldn't be necessary, but if you get errors<br />
# about being unable to find plugins, try uncommenting this.<br />
#path "/usr/lib/ladspa"<br><br />
plugins [<br />
{<br />
label mbeq<br />
id 1197<br />
input {<br />
#this setting is here by example, edit to your own taste<br />
#bands: 50hz, 100hz, 156hz, 220hz, 311hz, 440hz, 622hz, 880hz, 1250hz, 1750hz, 25000hz,<br />
#50000hz, 10000hz, 20000hz<br />
controls [ -5 -5 -5 -5 -5 -10 -20 -15 -10 -10 -10 -10 -10 -3 -2 ]<br />
}<br />
}<br />
]<br />
}<br><br />
# Redirect the default device to go via the EQ - you may want to do<br />
# this last, once you're sure everything is working. Otherwise all<br />
# your audio programs will break/crash if something has gone wrong.<br><br />
pcm.!default {<br />
type plug<br />
slave.pcm "eq"<br />
}<br><br />
# Redirect the OSS emulation through the EQ too (when programs are running through "aoss")<br><br />
pcm.dsp0 {<br />
type plug<br />
slave.pcm "eq"<br />
}<br />
<br />
*reload your alsa settings (as root)<br />
/etc/rc.d/alsa restart<br />
<br />
*you should be good to go (if not, ask in the forum)<br />
<br />
=Troubleshooting=<br />
==Still Getting No Sound?==<br />
<br />
Remember, ALSA installs with all channels '''muted by default''' (see previous section, [[ALSA#Unmuting_the_channels_and_testing_the_sound_card|unmuting your soundcard]]).<br />
<br />
However, if you're sure nothing is muted, that your drivers are installed correctly, and that your volume is right, but you still do not hear anything, then try blacklisting snd_pcsp from your modules array in rc.conf:<br />
<br />
MODULES=(!snd_pcsp ... )<br />
<br />
Note that this will disable your PC's internal speaker.<br />
If that doesn't work, then try adding the following line to <code>/etc/modprobe.conf</code>:<br />
<br />
options snd-NAME-OF-MODULE ac97_quirk=0<br />
<br />
The above fix has been observed to work with <code>via82xx</code><br />
options snd-NAME-OF-MODULE ac97_quirk=1<br />
The above fix has been reported to work with <code>snd_intel8x0</code><br />
<br />
==No Sound with Onboard Intel Sound Card==<br />
<br />
There may be an issue with two conflicting modules loaded, namely <code>snd_intel8x0</code> and <code>snd_intel8x0m</code>. In this case, edit <code>rc.conf</code> and in the MODULES array blacklist the latter one so that it reads <code>!snd_intel8x0m</code> afterwards.<br />
<br />
''Muting'' the "External Amplifier" in <code>alsamixer</code> or <code>amixer</code> may also help. See [http://alsa.opensrc.org/index.php/Intel8x0#Dell_Inspiron_8600_.28and_probably_others.29 the ALSA wiki].<br />
<br />
With '''Intel Corporation 82801 I (ICH9 Family) HD Audio Controller''' on laptop, you may need to add this line to<br />
<br />
/etc/modprobe.d/sound<br />
options snd-hda-intel model=laptop<br />
<br />
or<br />
options snd-hda-intel model=laptop enable=1 index=0<br />
<br />
Otherwise, the pcspkr may not work, and only the headphone have sound. See more on model in [http://en.opensuse.org/SDB:Intel-HDA_sound_problems]<br />
<br />
==Poor Sound Quality?==<br />
<br />
If you experience poor sound quality, try setting the PCM volume (in alsamixer) to a level such that gain is 0.<br />
<br />
==Pops when Starting and Stopping Playback?==<br />
<br />
Some modules can power off your sound card when not in use. this can make an audible noise when powering down your sound card. If you find this annoying try "modinfo snd-MY-MODULE", and look for a module option that adjusts or disables this feature. <br />
<br />
for example: to disable the power saving mode using snd-hda-intel add "options snd-hda-intel power_save=0" in /etc/modprobe.conf. or try it with "modprobe snd-hda-intel power_save=0"<br />
<br />
==Alsamixer does not run==<br />
If running alsamixer does not work and you wind up with the following error<br />
alsamixer: function snd_ctl_open failed for default: No such device or directory<br />
<br />
You should first check /etc/group to ensure that your current user is in the 'audio' group. Don't forget to log out and log in again for the group changes.<br />
<br />
Then you might need to re-install your kernel. Run 'pacman -S kernel26' or whichever patchset you prefer to use.<br />
<br />
==S/PDIF output does not work==<br />
If the optical/coaxial digital output of your motherboard/sound card is not working or stopped working, and have already enabled and unmuted it in alsamixer, try running<br />
iecset audio on<br />
<br />
as root.<br />
<br />
You can also put this command in rc.local as it sometimes it may stop working after a reboot.<br />
<br />
==No adjustable PCM channel==<br />
You may find that you lack adjustable PCM channel. In this case try to remove all sound-related stuff from MODULES section in /etc/rc.conf, except for snd-NAME-OF-MODULE and snd-pcm-oss.<br />
<br />
== HP TX2500 ==<br />
<br />
Add these 2 lines into /etc/modprobe.conf:<br />
<br />
options snd-cmipci mpu_port=0x330 fm_port=0x388<br />
<br />
options snd-hda-intel index=0 model=toshiba position_fix=1<br />
<br />
And don't forget to enable 'hal' in the DAEMONS section of your /etc/rc.conf<br />
<br />
== Skipping sound when playing MP3's ==<br />
<br />
If you have sound skipping when playing MP3 files and you have more then 2 speakers attacked to your computer (i.e. > 2 speaker system), run alsamixer and disable the channels for the speakers that you '''DON'T''' have (i.e. don't enable the sound for the center speaker if you don't have a center speaker<br />
<br />
= External Resources =<br />
More info can be found here<br />
* [http://alsa.opensrc.org/index.php/Main_Page Unofficial ALSA Wiki]<br />
* [http://alsa.opensrc.org/index.php/Aadebug A simple shell script to aid ALSA audio debugging]<br />
* [http://bbs.archlinux.org/viewtopic.php?id=36815 HOWTO: Compile driver from svn]<br />
* [http://gentoo-wiki.com/HOWTO_Set_up_a_system-wide_equaliser_with_ALSA_and_LADSPA HOWTO Set up a system-wide equaliser with ALSA and LADSPA]<br />
* [http://www.mjmwired.net/kernel/Documentation/sound/alsa/ALSA-Configuration.txt Advanced ALSA module configuration]</div>Ik12https://wiki.archlinux.org/index.php?title=User_talk:Ik12&diff=65753User talk:Ik122009-03-26T11:43:14Z<p>Ik12: </p>
<hr />
<div>Hi Ik12,<br />
<br />
Where do you come from? Your french is very good! Keep the good job.<br />
<br />
I’m a french guy and I made some (minor) french corrections to the [[32bit_chroot_(Fran%C3%A7ais)|32bit chroot français]] page.<br />
<br />
I think I’ll make some french translation in the future…<br />
<br />
À bientôt !<br />
<br />
<br />
Salut!<br />
<br />
thanks, that nice :) <br />
<br />
It is very kind, I appreciate it, 'cause I have a lot of doubt when writing and it is hard to keep concentrated on grammar, orthographic things and all... <br />
I live now in Luxembourg (where a lot of people speak french, so it helps). My main language was russian, I am too loazy to learn the layout of the keyboard so I do not translate in russian (besides, there is a good team I saw).<br />
<br />
Nice to have you here.</div>Ik12https://wiki.archlinux.org/index.php?title=Official_repositories&diff=64987Official repositories2009-03-14T01:12:13Z<p>Ik12: Add a in18 entry for the French translation.</p>
<hr />
<div>[[Category:Package management (English)]]<br />
[[Category:About Arch (English)]]<br />
[[Category:General (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|Official Repositories}}<br />
{{i18n_entry|Türkçe|Resmi Depolar}}<br />
{{i18n_entry|Česky|Oficiální repozitáře (Česky)}}<br />
{{i18n_entry|Español|Repositorios Oficiales}}<br />
{{i18n_entry|Italiano|Official_Repositories_(Italiano)}}<br />
{{i18n_entry|简体中文|官方软件仓库}}<br />
{{i18n_entry|Português|Official Repositories (Português)}}<br />
{{i18n_entry|Nederlands|Officiële Repositories (Nederlands)}}<br />
{{i18n_entry|Français|Dépôts Officiels (Français)}}<br />
{{i18n_links_end}}<br />
<br />
:''As there is much confusion about the official repositories, this article attempts to explain their meaning:''<br />
<br />
= Historical background =<br />
<br />
Most of the repository splits are for historical reasons. Originally, when Arch Linux was used by very few users, there was only one repository known as [official] (now [core]). At the time, [official] basically contained Judd Vinet's preferred applications. It was designed to contain one of each "type" of program -- one DE, one major browser, etc.<br />
<br />
There were users back then that didn't like Judd's selection, so since [[ABS - The Arch Build System | ABS]] is so easy to use, they created packages of their own. These packages went into a repository called [unofficial], and were maintained by developers other than Judd. Eventually, the two repositories were both considered equally supported by the developers, so the names [official] and [unofficial] no longer reflected their true purpose. They were subsequently renamed to [current] and [extra] sometime near the release version 0.5.<br />
<br />
Shortly after the 2007.8.1 release, [current] was renamed [core] in order to prevent confusion over what exactly it contains. The repositories are now more or less equal in the eyes of the developers and the community, but [core] does have some differences. The main distinction is that packages used for Installation CDs and release snapshots are taken only from [core]. This repository still gives a complete Linux system, though it may not be the Linux system you want.<br />
<br />
Now, sometime around 0.5 or 0.6, they found there were a lot of packages that the developers didn't want to maintain. One of the developers (Xentac) set up the "Trusted User Repositories", which were unofficial repositories in which trusted users could place packages they had created. There was a [staging] repository where packages could be promoted into the official repositories by one of the Arch Linux developers, but other than this, the developers and trusted users were more or less distinct.<br />
<br />
This worked for a while, but not when trusted users got bored with their repositories, and not when untrusted users wanted to share their own packages. This led to the development of the [http://aur.archlinux.org/ AUR]. The TUs were conglomerated into a more closely knit group, and they now collectively maintain the [community] repository. The Trusted Users are still a separate group from the Arch Linux developers, and there isn't a lot of communication between them. However, popular packages are still promoted from [community] to [extra] on occasion. The [http://aur.archlinux.org/ AUR] also supports allowing untrusted users to submit PKGBUILDs for other users to use if they wish. These packages are unsupported, and the packages are sometimes called the [unsupported] repository, though since no binary packages are distributed, unsupported isn't really a repository. Trusted users can adopt packages from unsupported into [community] at their discretion, whether it is because the package is popular or because they are interested in maintaining it.<br />
<br />
= List of repositories =<br />
<br />
== [core] ==<br />
<br />
The [core] repository can be found in ''core/os/i686'' or ''core/os/x86_64'' on your favorite mirror. It contains Arch core packages and some additional software, and will provide you with a fully functional base system.<br />
<br />
''The installation cd simply contains an installer script, and a snapshot of the core repository.''<br />
<br />
== [extra] ==<br />
<br />
The [extra] repository can be found in ''extra/os/i686'' or ''extra/os/x86_64'' on your favorite mirror. It contains all packages that don't fit in [core]<br><br />
Example: X.org, window managers, web servers, media players, languages like Python, Ruby and Perl, and a lot more.<br />
<br />
== [community] ==<br />
<br />
The [community] repository can be found in ''community/os/i686'' or ''community/os/x86_64'' on your favorite mirror. It is maintained by the ''Trusted Users (TUs)'' and is part of the ''Arch User Repository (AUR)''. It contains packages from the ''AUR'' that have enough votes and were adopted by a ''TU''.<br />
<br />
== [testing] ==<br />
<br />
The [testing] repository can be found in ''testing/os/i686'' on your favorite mirror. [testing] is special. It contains packages that are candidates for the [core] or [extra] repositories. New packages go into [testing] if:<br />
* they are expected to break something on update and need to be tested first<br />
* they require other packages to be rebuilt. In this case, all packages that need to be rebuilt are put into [testing] first and when all rebuilds are done, they are moved back to the other repositories.<br />
<br />
[testing] is the only repository that can have name collisions with any of the other official repositories. If enabled, it has to be the first repo listed in your ''pacman.conf'' file.<br />
<br />
Be careful when enabling [testing]. Your system may break after you update with [testing] enabled. Only experienced users should use it.<br />
<br />
== [unsupported] ==<br />
<br />
The [unsupported] repository is not really a repository at all. It refers to a database of user-submitted build scripts known as [[PKGBUILD]] files, thus the [unsupported] repository truly is unofficial. Users cannot download or install packages from [unsupported] using [[pacman]]. They must download the [[PKGBUILD]] files manually and compile the binaries themselves, or use one of the popular [[AUR Helpers]] to automate this task.</div>Ik12https://wiki.archlinux.org/index.php?title=User:Ik12&diff=64099User:Ik122009-03-06T00:06:24Z<p>Ik12: </p>
<hr />
<div>Hi!<br />
<br />
I tranlsate articles in French.<br />
Note that French is not my main language and I may do some errors. Please let me know if you notice some.<br />
<br />
I'm now tranlsating the Arch64 category (5 articles left). However, one I will have finish, I will update the Main page (the french one) and I will update/tranlsate articles the same way ls -R is doing:<br />
Category -> subcat -> articles<br />
Other Category -> articles -> eventuall subcat<br />
Third Category -> articles<br />
...<br />
<br />
<br />
<br />
You can contacte me by:<br />
<br />
email: cydanil@gmail.com<br />
jabber: cydanil@gmail.com<br />
skype: itwelve</div>Ik12https://wiki.archlinux.org/index.php?title=User:Ik12&diff=64098User:Ik122009-03-06T00:06:12Z<p>Ik12: </p>
<hr />
<div>Hi!<br />
<br />
I tranlsate articles in French.<br />
Note that French is not my main language and I may do some errors. Please let me know if you notice somes.<br />
<br />
I'm now tranlsating the Arch64 category (5 articles left). However, one I will have finish, I will update the Main page (the french one) and I will update/tranlsate articles the same way ls -R is doing:<br />
Category -> subcat -> articles<br />
Other Category -> articles -> eventuall subcat<br />
Third Category -> articles<br />
...<br />
<br />
<br />
<br />
You can contacte me by:<br />
<br />
email: cydanil@gmail.com<br />
jabber: cydanil@gmail.com<br />
skype: itwelve</div>Ik12https://wiki.archlinux.org/index.php?title=User:Ik12&diff=64097User:Ik122009-03-06T00:05:34Z<p>Ik12: </p>
<hr />
<div>Hi!<br />
<br />
I tranlsate articles in French.<br />
Note that French is not my main language and I may do some errors. Please let me know.<br />
<br />
I'm now tranlsating the Arch64 category (5 articles left). However, one I will have finish, I will update the Main page (the french one) and I will update/tranlsate articles the same way ls -R is doing:<br />
Category -> subcat -> articles<br />
Other Category -> articles -> eventuall subcat<br />
Third Category -> articles<br />
...<br />
<br />
<br />
<br />
You can contacte me by:<br />
<br />
email: cydanil@gmail.com<br />
jabber: cydanil@gmail.com<br />
skype: itwelve</div>Ik12https://wiki.archlinux.org/index.php?title=User:Ik12&diff=64096User:Ik122009-03-06T00:03:44Z<p>Ik12: </p>
<hr />
<div>Hi!<br />
<br />
I tranlsate articles in French.<br />
<br />
I'm now tranlsating the Arch64 category (5 articles left). However, one I will have finish, I will update the Main page (the french one) and I will update/tranlsate articles the same way ls -R is doing:<br />
Category -> subcat -> articles<br />
Other Category -> articles -> eventuall subcat<br />
Third Category -> articles<br />
...<br />
<br />
<br />
<br />
You can contacte me by:<br />
<br />
email: cydanil@gmail.com<br />
jabber: cydanil@gmail.com<br />
skype: itwelve</div>Ik12https://wiki.archlinux.org/index.php?title=User:Ik12&diff=64036User:Ik122009-03-05T12:12:10Z<p>Ik12: </p>
<hr />
<div>Hi!<br />
<br />
You can contacte me:<br />
<br />
email: cydanil@gmail.com<br />
jabber: cydanil@gmail.com<br />
skype: itwelve</div>Ik12https://wiki.archlinux.org/index.php?title=User:Ik12&diff=64035User:Ik122009-03-05T12:11:55Z<p>Ik12: Created page with 'Hi! You can contacte me: email: cydanil@gmail.com jabber: cydanil@gmail.com skype: itwelve'</p>
<hr />
<div>Hi!<br />
<br />
You can contacte me:<br />
<br />
email: cydanil@gmail.com<br />
jabber: cydanil@gmail.com<br />
skype: itwelve</div>Ik12https://wiki.archlinux.org/index.php?title=Install_bundled_32-bit_system_in_64-bit_system_(%C4%8Cesky)&diff=64012Install bundled 32-bit system in 64-bit system (Česky)2009-03-05T01:14:43Z<p>Ik12: </p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|English|:Arch64_Install_bundled_32bit_system}}<br />
{{i18n_entry|Česky|:32bit chroot (Česky)}}<br />
{{i18n_entry|Français|:32bit_chroot_(Français)}}<br />
{{i18n_links_end}}<br />
Instalace Arch64 svázaná s 32bit systémem<br />
<br />
Tento článek je určený především pro ty, kdo opravdu potřebují používat 32bitové aplikace. Protože Arch64 se snaží být čistě 64bitovou distribucí, bývá občas problém sehnat knihovny pro 32bit emulaci. Tento postup vytvoří čistě 32bitovou instalaci ArchLinuxu ve vaší stávající 64bitové.<br />
<br />
== Instalace základních balíčků ==<br />
Nejprve vytvoříme místo, kam stahovat a instalovat balíčky:<br />
mkdir /opt/arch32<br />
<br />
V libovolném editoru (třeba ''nano'') upravte soubor ''/etc/pacman.d/core'', případně (u pacmana>=3.1) ''/etc/pacman.d/mirrorlist'':<br />
<br />
nano /etc/pacman.d/core<br />
nano /etc/pacman.d/mirrorlist<br />
<br />
V těchto souborech nahraďte ''x86_64'' za ''i686'' (raději u více serverů, ale teoreticky stačí i jen jeden)<br />
<br />
'''Nezapomeňte nakonec vrátit tyto soubory do původního stavu!!!'''<br />
<br />
Dále je vhodné vytvořit pro 32bitovou instalaci samostatný log. '''Opět nezapomeňte po skončení tohoto návodu následující změnu zase vrátit zpátky.'''<br />
<br />
nano /etc/pacman.conf<br />
<br />
Upravte položku 'LogFile' podle potřeby (například ''/var/log/pacman_32.log'').<br />
<br />
Aktuální verze pacmana vyžaduje vytvořit adresářovou strukturu pro databázi:<br />
<br />
mkdir -p /opt/arch32/var/lib/pacman<br />
<br />
Nyní proveďte aktualizaci repozitářů:<br />
<br />
pacman --root /opt/arch32 -Sy<br />
<br />
A teď už můžeme nainstalovat základní balíčky (pokud nehodláte v chrootu kompilovat balíčky, můžete skupinu ''base-devel'' vynechat):<br />
<br />
pacman --root /opt/arch32 -S base base-devel<br />
<br />
'''Nyní vraťte zpátky změny v nastavení pacmana - /etc/pacman.d/core resp. /etc/pacman.d/mirrorlist a /etc/pacman.conf'''.<br />
<br />
== /etc/rc.d/arch32 rc skript ==<br />
<br />
Pro spuštění 32bitového prostředí při bootování vytvořte v /etc/rc.d skript a nazvěte ho ''arch32'':<br />
<br />
nano /etc/rc.d/arch32<br />
<br />
#!/bin/bash<br />
<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
<br />
case $1 in<br />
start)<br />
stat_busy "Starting Arch32 chroot"<br />
mount --bind /proc /opt/arch32/proc<br />
mount --bind /proc/bus/usb /opt/arch32/proc/bus/usb<br />
mount --bind /dev /opt/arch32/dev<br />
mount --bind /dev/pts /opt/arch32/dev/pts<br />
mount --bind /dev/shm /opt/arch32/dev/shm<br />
mount --bind /sys /opt/arch32/sys<br />
mount --bind /tmp /opt/arch32/tmp<br />
mount --bind /home /opt/arch32/home<br />
add_daemon arch32<br />
stat_done<br />
;;<br />
stop)<br />
stat_busy "Stopping Arch32 chroot"<br />
umount /opt/arch32/proc/bus/usb<br />
umount /opt/arch32/proc<br />
umount /opt/arch32/dev/pts<br />
umount /opt/arch32/dev/shm<br />
umount /opt/arch32/dev<br />
umount /opt/arch32/sys<br />
umount /opt/arch32/tmp<br />
umount /opt/arch32/home<br />
rm_daemon arch32<br />
stat_done<br />
;;<br />
restart)<br />
$0 stop<br />
sleep 1<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}"<br />
esac<br />
exit 0<br />
<br />
Ještě udělejte soubor spustitelným:<br />
<br />
chmod +x /etc/rc.d/arch32<br />
<br />
A přidejte daemona do ''/etc/rc.conf'':<br />
<br />
DAEMONS=(syslog-ng network netfs crond arch32 gdm)<br />
<br />
== Konfigurace ==<br />
Nejprve je nutné zkopírovat pár souborů s nastavením<br />
<br />
cd /opt/arch32/etc<br />
<br />
cp /etc/passwd* ./<br />
cp /etc/shadow* ./<br />
cp /etc/group* ./<br />
cp /etc/rc.conf ./<br />
ln /etc/resolv.conf ./<br />
cp -a /etc/localtime ./<br />
cp /etc/locale.gen ./<br />
cp /etc/profile.d/locale.sh profile.d<br />
cp /etc/mtab ./<br />
<br />
Abychom zabránili kolizi binárek, je nutné upravit ještě nastavení 32bitového pacmana. Adresářovou strukturu pro pacmana není nutné vytvářet, tu si pacman udělá sám.<br />
<br />
nano /opt/arch32/etc/pacman.conf<br />
[options]<br />
LogFile = /var/log/pacman_32.log<br />
DBPath = /var/lib/pacman_32<br />
CacheDir = /var/cache/pacman_32<br />
<br />
a následně:<br />
<br />
mv /opt/arch32/var/lib/pacman /opt/arch32/var/lib/pacman_32<br />
mv /opt/arch32/var/cache/pacman /opt/arch32/var/cache/pacman_32<br />
<br />
Nyní můžete chrootovat do 32bitového systému (jako root):<br />
<br />
/etc/rc.d/arch32 start<br />
xhost +<br />
chroot /opt/arch32<br />
<br />
Ještě poslední doladění:<br />
<br />
/usr/sbin/locale-gen<br />
pacman -Sy ttf-bitstream-vera ttf-ms-fonts<br />
<br />
Samozřejmě můžete nainstalovat libovolné jiné fonty, ale je nutné nainstaloval alespoň jedno písmo, jinak nebudou fungovat grafické aplikace.<br />
<br />
Nyní můžete nainstalovat libovolné aplikace podle potřeby:<br />
<br />
pacman -S acroread opera<br />
pacman -S mozilla-firefox<br />
pacman -S libxmu flashplugin<br />
pacman -S mplayer-plugin<br />
<br />
Pokud ještě chcete získat nějaké do místo navíc, můžete smazat stažené balíčky:<br />
<br />
pacman -Scc<br />
<br />
A ještě můžete odstranit pár drobností. '''Nezapomeňte, že /home adresář je provázaný s vaším normálním /home adresářem! Dávejte pozor na to co mažete!!!'''<br />
<br />
rmdir /home/ftp<br />
<br />
pacman -Rd mkinitcpio<br />
<br />
== Spouštění 32bitových aplikací z 64bitového systému ==<br />
<br />
<br />
=== Stáhněte a nainstalujte schroot ===<br />
<br />
Nainstalujte ''schroot'' z repozitáře ''community'':<br />
<br />
pacman -S schroot<br />
<br />
=== Nastavení ===<br />
<br />
Schroot již obsahuje připravené nastavení pro Arch32 chroot. Pouze zkontrolujte, že nastavení v /etc/schroot/schroot.conf v sekci [Arch32] odpovídá vašemu skutečnému nastavení.<br />
<br />
=== Spuštění aplikací ===<br />
<br />
Pro spuštění 32bitové aplikace instalované v chrootu použijte:<br />
<br />
schroot -p opera -notrayicon<br />
<br />
Tento příklad spustí Operu, instalovanou v 32bitovém chrootu bez ikony v tray.<br />
<br />
=== Zvuk ===<br />
Nejpoužívanější aplikací v 32 bitovém systému je flash, například pro Youtube.<br />
Aby flash ve Firefoxu přehrával hudbu, otevřete terminál a chrootujte do 32bitového systému:<br />
<br />
chroot /opt/arch32<br />
<br />
Odtud nainstalujte ''alsa-oss'':<br />
pacman -S alsa-oss<br />
<br />
Potom napište:<br />
export FIREFOX_DSP="aoss"<br />
<br />
A spusťte FireFox</div>Ik12https://wiki.archlinux.org/index.php?title=Install_bundled_32-bit_system_in_64-bit_system&diff=64011Install bundled 32-bit system in 64-bit system2009-03-05T01:13:34Z<p>Ik12: </p>
<hr />
<div>[[Category:Arch64 (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|:Arch64_Install_bundled_32bit_system}}<br />
{{i18n_entry|Czech|:32bit chroot}}<br />
{{i18n_entry|Français|:32bit_chroot_(Français)}}<br />
{{i18n_links_end}}<br />
<br />
Note that this script doesn't try to change anything out of the 32bit directory. I'm no expert so there is maybe errors or some "bad things".<br />
<br />
This howto is just for those who really need to run 32 bit apps and to install it easily. As Arch64 tries to be a pure 64 bit distro, it seems the devs won't provide any compatibility libs, this system seems to me the cleaner.<br />
<br />
NOTE: If you have a custom kernel config, you need to make sure that this option is set: "CONFIG_IA32_EMULATION=y". Otherwise, your 64-bit kernel will not be able to access your 32-bit chrooted environment. The stock Arch64 kernels generally have this set properly by default.<br />
<br />
== Install the base 32 bit system ==<br />
We create the repository.<br />
mkdir /opt/arch32<br />
vim /etc/pacman.d/mirrorlist<br />
Here you'll have to replace in the first address x86_64 by i686.<br />
'''Don't forget to revert it at the end of the howto or your system can be screwed when you install something.'''<br />
<br />
As soon as you use the ''--root'' switch to the pacman command below, all the files ''/var/log/pacman.log'' ''/var/lib/pacman/db.lck'' will be created inside your ''/opt/arch32'' directory.<br />
So the log of pacman will be ''/opt/arch32/var/log/pacman.log'' and will NOT mess up with your 64bit installation. There is no need for a ''LogFile'' directive in ''/etc/pacman.conf'' or a ''--logfile'' switch unless you want the log file to be elsewhere.<br />
<br />
The ''--cachedir'' switch is for the package to be cached in the ''/opt/arch32/var/cache/pacman/pkg'' directory instead of /var/cache/pacman/pkg<br />
<br />
We now create that directory, just to be sure:<br />
<br />
mkdir -p /opt/arch32/var/{cache/pacman/pkg,lib/pacman}<br />
<br />
Now proceed to sync up pacman:<br />
<br />
pacman --root /opt/arch32 --cachedir /opt/arch32/var/cache/pacman/pkg -Sy<br />
<br />
Now we can install the base packages:<br />
<br />
pacman --root /opt/arch32 --cachedir /opt/arch32/var/cache/pacman/pkg -S base base-devel<br />
<br />
If you don't intend to compile packages inside this chroot, you can omit the base-devel group:<br />
<br />
pacman --root /opt/arch32 --cachedir /opt/arch32/var/cache/pacman/pkg -S base<br />
<br />
'''Note:''' You may have to update pacman and install the base packages with one big swoop:<br />
<br />
pacman --root /opt/arch32 --cachedir /opt/arch32/var/cache/pacman/pkg -Sy base base-devel<br />
<br />
'''You can now revert your pacman.d/mirrorlist file to x86_64.'''<br />
<br />
== /etc/rc.d/arch32 rc script ==<br />
<br />
To initiate the 32bit environment at startup, create a script in /etc/rc.d/ called "arch32":<br />
<br />
#!/bin/bash<br />
<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
<br />
case $1 in<br />
start)<br />
stat_busy "Starting Arch32 chroot"<br />
mount --bind /proc /opt/arch32/proc<br />
mount --bind /proc/bus/usb /opt/arch32/proc/bus/usb<br />
mount --bind /dev /opt/arch32/dev<br />
mount --bind /dev/pts /opt/arch32/dev/pts<br />
mount --bind /dev/shm /opt/arch32/dev/shm<br />
mount --bind /sys /opt/arch32/sys<br />
mount --bind /tmp /opt/arch32/tmp<br />
mount --bind /home /opt/arch32/home<br />
add_daemon arch32<br />
stat_done<br />
;;<br />
stop)<br />
stat_busy "Stopping Arch32 chroot"<br />
umount /opt/arch32/proc/bus/usb<br />
umount /opt/arch32/proc<br />
umount /opt/arch32/dev/pts<br />
umount /opt/arch32/dev/shm<br />
umount /opt/arch32/dev<br />
umount /opt/arch32/sys<br />
umount /opt/arch32/tmp<br />
umount /opt/arch32/home<br />
rm_daemon arch32<br />
stat_done<br />
;;<br />
restart)<br />
$0 stop<br />
sleep 1<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}"<br />
esac<br />
exit 0<br />
<br />
Then allow execution of this script:<br />
<br />
chmod +x /etc/rc.d/arch32<br />
<br />
And add it to "/etc/rc.conf":<br />
<br />
DAEMONS=(syslog-ng network netfs crond arch32 gdm)<br />
<br />
== Configure the new installed system ==<br />
First, copy some meaningful config files over....<br />
<br />
cd /opt/arch32/etc<br />
<br />
ln -f /etc/passwd* .<br />
ln -f /etc/shadow* .<br />
ln -f /etc/group* .<br />
<br />
ln -f /etc/rc.conf .<br />
ln -f /etc/resolv.conf .<br />
<br />
ln -f /etc/localtime .<br />
ln -f /etc/locale.gen .<br />
ln -f /etc/profile.d/locale.sh profile.d<br />
<br />
cp /etc/vimrc .<br />
cp /etc/mtab .<br />
<br />
Now chroot in your new system<br />
/etc/rc.d/arch32 start<br />
xhost +local:<br />
chroot /opt/arch32<br />
<br />
I recommend that you use a custom bash prompt inside your ''32bit chroot installation'' to know where you are (i.e. inside the 32bit chroot). You can, for example, add a '''ARCH32''' string to your '''PS1''' string that you may have defined in ''.bashrc'' or other config file.<br />
<br />
Fix some future locale issues<br />
/usr/sbin/locale-gen<br />
pacman -S ttf-bitstream-vera ttf-ms-fonts<br />
<br />
'''Note''' that you can install any other font. You just need one or your apps won't display any text.<br />
<br />
Also, keep in mind that the "/etc/pacman.conf" file from the 32bit environment is the default one. The [community] repo is enabled by default now.<br />
<br />
Now you can install any apps you need (*note for firefox with the nonfree flash plugin, you will need to install libxmu as well! Apparently this dependency has not been taken care of yet; see [http://bugs.archlinux.org/task/5583 Flyspray]).<br />
<br />
pacman -S acroread opera<br />
pacman -S mozilla-firefox<br />
pacman -S libxmu flashplugin<br />
pacman -S mplayer-plugin<br />
<br />
You can also clean up to win back some space by removing some unnecessary packages.<br />
This cleanup is for your '''32 bit root" environment''' and must then be done inside it after '''chrooting'''!<br />
Below is a list of package you '''might''' want to remove...<br />
<br />
pacman -Rd mkinitcpio<br />
pacman -R kernel26<br />
pacman -R grub<br />
pacman -R dhcpcd<br />
pacman -R rp-pppoe<br />
pacman -R ppp<br />
pacman -R xfsprogs<br />
pacman -R reiserfsprogs<br />
pacman -R jfsutils<br />
pacman -R hdparm<br />
pacman -R hwdetect<br />
pacman -R syslog-ng<br />
pacman -R logrotate<br />
pacman -R lvm2<br />
pacman -R dcron<br />
pacman -R wpa_supplicant<br />
pacman -R pcmciautils<br />
<br />
===Consider also clearing out your pacman cache (regularly)===<br />
'''Note''': this is '''not''' a command that you'll only have to run just once. As packages accumulate, you'll have to keep doing this if you want to clear out the space from the pacman cache:<br />
pacman -Scc<br />
<br />
== Execute a 32bit apps from a 64bit env ==<br />
<br />
<br />
=== Download and install schroot ===<br />
<br />
Install "schroot" to your 64-bit installation from the community repository:<br />
<br />
pacman -S schroot<br />
<br />
=== Configuration ===<br />
<br />
Schroot is already configured for Arch32 chroot, so you just should check /etc/schroot/schroot.conf, section [Arch32] if all informations match your configuration.<br />
<br />
<br />
=== Execute 32bit apps ===<br />
<br />
Finally, to use your 32bit apps:<br />
<br />
schroot -p -- opera -notrayicon<br />
<br />
It will launch Opera, without the systray icon, from your 32bit environment. <br />
<br />
If you want to, I wrote a small program to replace 64-bit version of firefox in your system, paste it into geany, save as cpp file named firefox.cpp and compile by pressing F9:<br />
#include <iostream><br />
#include <string><br />
#include <cstdlib><br />
using namespace std;<br />
<br />
int main(int argc, char **argv)<br />
{<br />
string temp="schroot -p firefox ";<br />
if (argc>=2) temp+=+argv[1];<br />
system(temp.c_str());<br />
return 0;<br />
}<br />
Now replace firefox binary file in /usr/lib/firefox-3.0.1 with the compiled file. (note: the directory may be different, because of version of firefox)<br />
<br />
=== Using sound ===<br />
The most used application in 32 bits is flash, for YouTube for example. <br />
<br />
To get sound from the flash player in firefox, open a terminal and chroot inside the 32-bit system:<br />
chroot /opt/arch32<br />
<br />
From there, install alsa-oss:<br />
pacman -S alsa-oss<br />
<br />
Then type:<br />
export FIREFOX_DSP="aoss"<br />
<br />
Every chroot into the 32-bit system will require this export command to be entered so it may be best to incorporate it into a script.<br />
<br />
Finally, launch Firefox.<br />
<br />
=== Example script for Firefox with sound ===<br />
Open a text editor and save the following in /usr/bin/firefox32 (as root, use sudo):<br />
<br />
<pre>#!/bin/sh<br />
schroot -p firefox $1;export FIREFOX_DSP="aoss"</pre><br />
<br />
Make it executable:<br />
<br />
sudo chmod +x /usr/bin/firefox32<br />
<br />
Now you can make an alias for firefox if you want:<br />
<br />
alias firefox="firefox32"<br />
<br />
Add this to your $HOME/.bashrc file at the end, and type it into bash to make the alias available immediately. Or you can just change all your DE launchers to firefox32 if you still want 64 bit firefox to be available.<br />
<br />
=== Note ===<br />
If you still use dchroot instead of current schroot, you should use ''-d'' switch instead of ''-s''.</div>Ik12https://wiki.archlinux.org/index.php?title=Install_bundled_32-bit_system_in_64-bit_system_(%C4%8Cesky)&diff=64007Install bundled 32-bit system in 64-bit system (Česky)2009-03-05T01:09:27Z<p>Ik12: Add a in18 entry for the French translation.</p>
<hr />
<div>{{i18n_links_start}}<br />
{{i18n_entry|English|:Arch64_Install_bundled_32bit_system}}<br />
{{i18n_entry|Česky|:32bit chroot (Česky)}}<br />
{{i18n_entry|Français|:32bit_chroot_Français}}<br />
{{i18n_links_end}}<br />
Instalace Arch64 svázaná s 32bit systémem<br />
<br />
Tento článek je určený především pro ty, kdo opravdu potřebují používat 32bitové aplikace. Protože Arch64 se snaží být čistě 64bitovou distribucí, bývá občas problém sehnat knihovny pro 32bit emulaci. Tento postup vytvoří čistě 32bitovou instalaci ArchLinuxu ve vaší stávající 64bitové.<br />
<br />
== Instalace základních balíčků ==<br />
Nejprve vytvoříme místo, kam stahovat a instalovat balíčky:<br />
mkdir /opt/arch32<br />
<br />
V libovolném editoru (třeba ''nano'') upravte soubor ''/etc/pacman.d/core'', případně (u pacmana>=3.1) ''/etc/pacman.d/mirrorlist'':<br />
<br />
nano /etc/pacman.d/core<br />
nano /etc/pacman.d/mirrorlist<br />
<br />
V těchto souborech nahraďte ''x86_64'' za ''i686'' (raději u více serverů, ale teoreticky stačí i jen jeden)<br />
<br />
'''Nezapomeňte nakonec vrátit tyto soubory do původního stavu!!!'''<br />
<br />
Dále je vhodné vytvořit pro 32bitovou instalaci samostatný log. '''Opět nezapomeňte po skončení tohoto návodu následující změnu zase vrátit zpátky.'''<br />
<br />
nano /etc/pacman.conf<br />
<br />
Upravte položku 'LogFile' podle potřeby (například ''/var/log/pacman_32.log'').<br />
<br />
Aktuální verze pacmana vyžaduje vytvořit adresářovou strukturu pro databázi:<br />
<br />
mkdir -p /opt/arch32/var/lib/pacman<br />
<br />
Nyní proveďte aktualizaci repozitářů:<br />
<br />
pacman --root /opt/arch32 -Sy<br />
<br />
A teď už můžeme nainstalovat základní balíčky (pokud nehodláte v chrootu kompilovat balíčky, můžete skupinu ''base-devel'' vynechat):<br />
<br />
pacman --root /opt/arch32 -S base base-devel<br />
<br />
'''Nyní vraťte zpátky změny v nastavení pacmana - /etc/pacman.d/core resp. /etc/pacman.d/mirrorlist a /etc/pacman.conf'''.<br />
<br />
== /etc/rc.d/arch32 rc skript ==<br />
<br />
Pro spuštění 32bitového prostředí při bootování vytvořte v /etc/rc.d skript a nazvěte ho ''arch32'':<br />
<br />
nano /etc/rc.d/arch32<br />
<br />
#!/bin/bash<br />
<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
<br />
case $1 in<br />
start)<br />
stat_busy "Starting Arch32 chroot"<br />
mount --bind /proc /opt/arch32/proc<br />
mount --bind /proc/bus/usb /opt/arch32/proc/bus/usb<br />
mount --bind /dev /opt/arch32/dev<br />
mount --bind /dev/pts /opt/arch32/dev/pts<br />
mount --bind /dev/shm /opt/arch32/dev/shm<br />
mount --bind /sys /opt/arch32/sys<br />
mount --bind /tmp /opt/arch32/tmp<br />
mount --bind /home /opt/arch32/home<br />
add_daemon arch32<br />
stat_done<br />
;;<br />
stop)<br />
stat_busy "Stopping Arch32 chroot"<br />
umount /opt/arch32/proc/bus/usb<br />
umount /opt/arch32/proc<br />
umount /opt/arch32/dev/pts<br />
umount /opt/arch32/dev/shm<br />
umount /opt/arch32/dev<br />
umount /opt/arch32/sys<br />
umount /opt/arch32/tmp<br />
umount /opt/arch32/home<br />
rm_daemon arch32<br />
stat_done<br />
;;<br />
restart)<br />
$0 stop<br />
sleep 1<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}"<br />
esac<br />
exit 0<br />
<br />
Ještě udělejte soubor spustitelným:<br />
<br />
chmod +x /etc/rc.d/arch32<br />
<br />
A přidejte daemona do ''/etc/rc.conf'':<br />
<br />
DAEMONS=(syslog-ng network netfs crond arch32 gdm)<br />
<br />
== Konfigurace ==<br />
Nejprve je nutné zkopírovat pár souborů s nastavením<br />
<br />
cd /opt/arch32/etc<br />
<br />
cp /etc/passwd* ./<br />
cp /etc/shadow* ./<br />
cp /etc/group* ./<br />
cp /etc/rc.conf ./<br />
ln /etc/resolv.conf ./<br />
cp -a /etc/localtime ./<br />
cp /etc/locale.gen ./<br />
cp /etc/profile.d/locale.sh profile.d<br />
cp /etc/mtab ./<br />
<br />
Abychom zabránili kolizi binárek, je nutné upravit ještě nastavení 32bitového pacmana. Adresářovou strukturu pro pacmana není nutné vytvářet, tu si pacman udělá sám.<br />
<br />
nano /opt/arch32/etc/pacman.conf<br />
[options]<br />
LogFile = /var/log/pacman_32.log<br />
DBPath = /var/lib/pacman_32<br />
CacheDir = /var/cache/pacman_32<br />
<br />
a následně:<br />
<br />
mv /opt/arch32/var/lib/pacman /opt/arch32/var/lib/pacman_32<br />
mv /opt/arch32/var/cache/pacman /opt/arch32/var/cache/pacman_32<br />
<br />
Nyní můžete chrootovat do 32bitového systému (jako root):<br />
<br />
/etc/rc.d/arch32 start<br />
xhost +<br />
chroot /opt/arch32<br />
<br />
Ještě poslední doladění:<br />
<br />
/usr/sbin/locale-gen<br />
pacman -Sy ttf-bitstream-vera ttf-ms-fonts<br />
<br />
Samozřejmě můžete nainstalovat libovolné jiné fonty, ale je nutné nainstaloval alespoň jedno písmo, jinak nebudou fungovat grafické aplikace.<br />
<br />
Nyní můžete nainstalovat libovolné aplikace podle potřeby:<br />
<br />
pacman -S acroread opera<br />
pacman -S mozilla-firefox<br />
pacman -S libxmu flashplugin<br />
pacman -S mplayer-plugin<br />
<br />
Pokud ještě chcete získat nějaké do místo navíc, můžete smazat stažené balíčky:<br />
<br />
pacman -Scc<br />
<br />
A ještě můžete odstranit pár drobností. '''Nezapomeňte, že /home adresář je provázaný s vaším normálním /home adresářem! Dávejte pozor na to co mažete!!!'''<br />
<br />
rmdir /home/ftp<br />
<br />
pacman -Rd mkinitcpio<br />
<br />
== Spouštění 32bitových aplikací z 64bitového systému ==<br />
<br />
<br />
=== Stáhněte a nainstalujte schroot ===<br />
<br />
Nainstalujte ''schroot'' z repozitáře ''community'':<br />
<br />
pacman -S schroot<br />
<br />
=== Nastavení ===<br />
<br />
Schroot již obsahuje připravené nastavení pro Arch32 chroot. Pouze zkontrolujte, že nastavení v /etc/schroot/schroot.conf v sekci [Arch32] odpovídá vašemu skutečnému nastavení.<br />
<br />
=== Spuštění aplikací ===<br />
<br />
Pro spuštění 32bitové aplikace instalované v chrootu použijte:<br />
<br />
schroot -p opera -notrayicon<br />
<br />
Tento příklad spustí Operu, instalovanou v 32bitovém chrootu bez ikony v tray.<br />
<br />
=== Zvuk ===<br />
Nejpoužívanější aplikací v 32 bitovém systému je flash, například pro Youtube.<br />
Aby flash ve Firefoxu přehrával hudbu, otevřete terminál a chrootujte do 32bitového systému:<br />
<br />
chroot /opt/arch32<br />
<br />
Odtud nainstalujte ''alsa-oss'':<br />
pacman -S alsa-oss<br />
<br />
Potom napište:<br />
export FIREFOX_DSP="aoss"<br />
<br />
A spusťte FireFox</div>Ik12https://wiki.archlinux.org/index.php?title=Install_bundled_32-bit_system_in_64-bit_system&diff=64006Install bundled 32-bit system in 64-bit system2009-03-05T01:08:39Z<p>Ik12: Add a in18 entry for the French translation.</p>
<hr />
<div>[[Category:Arch64 (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|:Arch64_Install_bundled_32bit_system}}<br />
{{i18n_entry|Czech|:32bit chroot}}<br />
{{i18n_entry|Français|:32bit_chroot_Français}}<br />
{{i18n_links_end}}<br />
<br />
Note that this script doesn't try to change anything out of the 32bit directory. I'm no expert so there is maybe errors or some "bad things".<br />
<br />
This howto is just for those who really need to run 32 bit apps and to install it easily. As Arch64 tries to be a pure 64 bit distro, it seems the devs won't provide any compatibility libs, this system seems to me the cleaner.<br />
<br />
NOTE: If you have a custom kernel config, you need to make sure that this option is set: "CONFIG_IA32_EMULATION=y". Otherwise, your 64-bit kernel will not be able to access your 32-bit chrooted environment. The stock Arch64 kernels generally have this set properly by default.<br />
<br />
== Install the base 32 bit system ==<br />
We create the repository.<br />
mkdir /opt/arch32<br />
vim /etc/pacman.d/mirrorlist<br />
Here you'll have to replace in the first address x86_64 by i686.<br />
'''Don't forget to revert it at the end of the howto or your system can be screwed when you install something.'''<br />
<br />
As soon as you use the ''--root'' switch to the pacman command below, all the files ''/var/log/pacman.log'' ''/var/lib/pacman/db.lck'' will be created inside your ''/opt/arch32'' directory.<br />
So the log of pacman will be ''/opt/arch32/var/log/pacman.log'' and will NOT mess up with your 64bit installation. There is no need for a ''LogFile'' directive in ''/etc/pacman.conf'' or a ''--logfile'' switch unless you want the log file to be elsewhere.<br />
<br />
The ''--cachedir'' switch is for the package to be cached in the ''/opt/arch32/var/cache/pacman/pkg'' directory instead of /var/cache/pacman/pkg<br />
<br />
We now create that directory, just to be sure:<br />
<br />
mkdir -p /opt/arch32/var/{cache/pacman/pkg,lib/pacman}<br />
<br />
Now proceed to sync up pacman:<br />
<br />
pacman --root /opt/arch32 --cachedir /opt/arch32/var/cache/pacman/pkg -Sy<br />
<br />
Now we can install the base packages:<br />
<br />
pacman --root /opt/arch32 --cachedir /opt/arch32/var/cache/pacman/pkg -S base base-devel<br />
<br />
If you don't intend to compile packages inside this chroot, you can omit the base-devel group:<br />
<br />
pacman --root /opt/arch32 --cachedir /opt/arch32/var/cache/pacman/pkg -S base<br />
<br />
'''Note:''' You may have to update pacman and install the base packages with one big swoop:<br />
<br />
pacman --root /opt/arch32 --cachedir /opt/arch32/var/cache/pacman/pkg -Sy base base-devel<br />
<br />
'''You can now revert your pacman.d/mirrorlist file to x86_64.'''<br />
<br />
== /etc/rc.d/arch32 rc script ==<br />
<br />
To initiate the 32bit environment at startup, create a script in /etc/rc.d/ called "arch32":<br />
<br />
#!/bin/bash<br />
<br />
. /etc/rc.conf<br />
. /etc/rc.d/functions<br />
<br />
case $1 in<br />
start)<br />
stat_busy "Starting Arch32 chroot"<br />
mount --bind /proc /opt/arch32/proc<br />
mount --bind /proc/bus/usb /opt/arch32/proc/bus/usb<br />
mount --bind /dev /opt/arch32/dev<br />
mount --bind /dev/pts /opt/arch32/dev/pts<br />
mount --bind /dev/shm /opt/arch32/dev/shm<br />
mount --bind /sys /opt/arch32/sys<br />
mount --bind /tmp /opt/arch32/tmp<br />
mount --bind /home /opt/arch32/home<br />
add_daemon arch32<br />
stat_done<br />
;;<br />
stop)<br />
stat_busy "Stopping Arch32 chroot"<br />
umount /opt/arch32/proc/bus/usb<br />
umount /opt/arch32/proc<br />
umount /opt/arch32/dev/pts<br />
umount /opt/arch32/dev/shm<br />
umount /opt/arch32/dev<br />
umount /opt/arch32/sys<br />
umount /opt/arch32/tmp<br />
umount /opt/arch32/home<br />
rm_daemon arch32<br />
stat_done<br />
;;<br />
restart)<br />
$0 stop<br />
sleep 1<br />
$0 start<br />
;;<br />
*)<br />
echo "usage: $0 {start|stop|restart}"<br />
esac<br />
exit 0<br />
<br />
Then allow execution of this script:<br />
<br />
chmod +x /etc/rc.d/arch32<br />
<br />
And add it to "/etc/rc.conf":<br />
<br />
DAEMONS=(syslog-ng network netfs crond arch32 gdm)<br />
<br />
== Configure the new installed system ==<br />
First, copy some meaningful config files over....<br />
<br />
cd /opt/arch32/etc<br />
<br />
ln -f /etc/passwd* .<br />
ln -f /etc/shadow* .<br />
ln -f /etc/group* .<br />
<br />
ln -f /etc/rc.conf .<br />
ln -f /etc/resolv.conf .<br />
<br />
ln -f /etc/localtime .<br />
ln -f /etc/locale.gen .<br />
ln -f /etc/profile.d/locale.sh profile.d<br />
<br />
cp /etc/vimrc .<br />
cp /etc/mtab .<br />
<br />
Now chroot in your new system<br />
/etc/rc.d/arch32 start<br />
xhost +local:<br />
chroot /opt/arch32<br />
<br />
I recommend that you use a custom bash prompt inside your ''32bit chroot installation'' to know where you are (i.e. inside the 32bit chroot). You can, for example, add a '''ARCH32''' string to your '''PS1''' string that you may have defined in ''.bashrc'' or other config file.<br />
<br />
Fix some future locale issues<br />
/usr/sbin/locale-gen<br />
pacman -S ttf-bitstream-vera ttf-ms-fonts<br />
<br />
'''Note''' that you can install any other font. You just need one or your apps won't display any text.<br />
<br />
Also, keep in mind that the "/etc/pacman.conf" file from the 32bit environment is the default one. The [community] repo is enabled by default now.<br />
<br />
Now you can install any apps you need (*note for firefox with the nonfree flash plugin, you will need to install libxmu as well! Apparently this dependency has not been taken care of yet; see [http://bugs.archlinux.org/task/5583 Flyspray]).<br />
<br />
pacman -S acroread opera<br />
pacman -S mozilla-firefox<br />
pacman -S libxmu flashplugin<br />
pacman -S mplayer-plugin<br />
<br />
You can also clean up to win back some space by removing some unnecessary packages.<br />
This cleanup is for your '''32 bit root" environment''' and must then be done inside it after '''chrooting'''!<br />
Below is a list of package you '''might''' want to remove...<br />
<br />
pacman -Rd mkinitcpio<br />
pacman -R kernel26<br />
pacman -R grub<br />
pacman -R dhcpcd<br />
pacman -R rp-pppoe<br />
pacman -R ppp<br />
pacman -R xfsprogs<br />
pacman -R reiserfsprogs<br />
pacman -R jfsutils<br />
pacman -R hdparm<br />
pacman -R hwdetect<br />
pacman -R syslog-ng<br />
pacman -R logrotate<br />
pacman -R lvm2<br />
pacman -R dcron<br />
pacman -R wpa_supplicant<br />
pacman -R pcmciautils<br />
<br />
===Consider also clearing out your pacman cache (regularly)===<br />
'''Note''': this is '''not''' a command that you'll only have to run just once. As packages accumulate, you'll have to keep doing this if you want to clear out the space from the pacman cache:<br />
pacman -Scc<br />
<br />
== Execute a 32bit apps from a 64bit env ==<br />
<br />
<br />
=== Download and install schroot ===<br />
<br />
Install "schroot" to your 64-bit installation from the community repository:<br />
<br />
pacman -S schroot<br />
<br />
=== Configuration ===<br />
<br />
Schroot is already configured for Arch32 chroot, so you just should check /etc/schroot/schroot.conf, section [Arch32] if all informations match your configuration.<br />
<br />
<br />
=== Execute 32bit apps ===<br />
<br />
Finally, to use your 32bit apps:<br />
<br />
schroot -p -- opera -notrayicon<br />
<br />
It will launch Opera, without the systray icon, from your 32bit environment. <br />
<br />
If you want to, I wrote a small program to replace 64-bit version of firefox in your system, paste it into geany, save as cpp file named firefox.cpp and compile by pressing F9:<br />
#include <iostream><br />
#include <string><br />
#include <cstdlib><br />
using namespace std;<br />
<br />
int main(int argc, char **argv)<br />
{<br />
string temp="schroot -p firefox ";<br />
if (argc>=2) temp+=+argv[1];<br />
system(temp.c_str());<br />
return 0;<br />
}<br />
Now replace firefox binary file in /usr/lib/firefox-3.0.1 with the compiled file. (note: the directory may be different, because of version of firefox)<br />
<br />
=== Using sound ===<br />
The most used application in 32 bits is flash, for YouTube for example. <br />
<br />
To get sound from the flash player in firefox, open a terminal and chroot inside the 32-bit system:<br />
chroot /opt/arch32<br />
<br />
From there, install alsa-oss:<br />
pacman -S alsa-oss<br />
<br />
Then type:<br />
export FIREFOX_DSP="aoss"<br />
<br />
Every chroot into the 32-bit system will require this export command to be entered so it may be best to incorporate it into a script.<br />
<br />
Finally, launch Firefox.<br />
<br />
=== Example script for Firefox with sound ===<br />
Open a text editor and save the following in /usr/bin/firefox32 (as root, use sudo):<br />
<br />
<pre>#!/bin/sh<br />
schroot -p firefox $1;export FIREFOX_DSP="aoss"</pre><br />
<br />
Make it executable:<br />
<br />
sudo chmod +x /usr/bin/firefox32<br />
<br />
Now you can make an alias for firefox if you want:<br />
<br />
alias firefox="firefox32"<br />
<br />
Add this to your $HOME/.bashrc file at the end, and type it into bash to make the alias available immediately. Or you can just change all your DE launchers to firefox32 if you still want 64 bit firefox to be available.<br />
<br />
=== Note ===<br />
If you still use dchroot instead of current schroot, you should use ''-d'' switch instead of ''-s''.</div>Ik12https://wiki.archlinux.org/index.php?title=64-bit_FAQ&diff=6398664-bit FAQ2009-03-04T20:20:01Z<p>Ik12: Add a link in the i18n to the french version.</p>
<hr />
<div>[[Category:Arch64 (English)]]<br />
[[Category:FAQs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Česky|Arch64 FAQ (Česky)}}<br />
{{i18n_entry|English|Arch64 FAQ}}<br />
{{i18n_entry|Español|Arch64 FAQ (Español)}}<br />
{{i18n_entry|Ελληνικά|Arch64 FAQ (Ελληνικά)}}<br />
{{i18n_entry|Français|Arch64 FAQ (Français)}}<br />
{{i18n_entry|Italiano|Arch64 FAQ (Italiano)}}<br />
{{i18n_entry|简体中文|Arch64问答_(简体中文)}}<br />
{{i18n_entry|Русский|Arch64 FAQ (Русский)}}<br />
{{i18n_links_end}}<br />
<br />
Below is a list of frequently asked questions about Arch64.<br />
<br />
==How can I install Arch64?==<br />
Just use our [http://www.archlinux.org/download/ official install ISO CD].<br />
<br />
==How complete is the port? Will I have all the packages from my Arch32 Environment?==<br />
Core+Extra repos are ported and almost everything is up to date, only hours or a few days at most behind Arch Linux i686. Our TU's are trying to port the Community repo now.<br />
<br />
The port is ready for daily use in a desktop or server environment.<br />
<br />
==Does 64-bit mean a great speed improvement?==<br />
For applications using the 64-bit CPU registers (large databases and such) this is true in most cases. Some multimedia applications will also run noticeably faster. If you know an application which is known to be much faster when using SSE3 extensions you can rebuild the package yourself. We ''only'' compile with SSE2 support(from march=x86_64) and -O2 optimizations.<br />
For more read http://forums.gentoo.org/viewtopic.php?t=221045 or http://www.thejemreport.com/mambo/content/view/74/74/ .<br />
<br />
For the rest of the system: It doesn't make any difference if the keyboard waits. <br />
<br />
For further details watch our [[Arch64_ToDoS]]. There you will find a list comparing arch32/arch64 package versions.<br />
<br />
For certain boot problems try these special kernel boot flags: http://www.x86-64.org/lists/discuss/msg03747.html (dead link)<br />
<br />
I have three 64-bit Archies running now, and they perform noticeably better under heavy load. It just seems to deliver more punch.<br />
<br />
==How can I file bugs?==<br />
Simply use Arch's flyspray but select x86_64 in the Architecture field if you think it's a port-related problem!<br />
<br />
==What repos should I set up for pacman to use?==<br />
All repos are supported for the port.<br />
<br />
==How can I patch existing PKGBUILDs for use with Arch64?==<br />
We add to all ported packages this variable:<br />
arch=('i686' 'x86_64') <br />
Add small patches directly to the sources and md5sums area but use for complete different sources:<br />
[ "$CARCH" = "x86_64" ] && source=(${source[@]} 'other source')<br />
[ "$CARCH" = "x86_64" ] && md5sums=(${md5sums[@]} 'other md5sum')<br />
For any small fix use this in the build area:<br />
[ "$CARCH" = "x86_64" ] && (patch -Np0 -i ../foo_x86_64.patch || return 1)<br />
Or when you need more changes:<br />
if [ "$CARCH" = "x86_64" ]; then<br />
configure/patch/sed # for x86_64<br />
else configure/patch/sed # for i686<br />
fi<br />
<br />
==What will I miss in Arch64?==<br />
The following applications are known not to be 64-bit compatible:<br />
<br />
* Closed-source apps like Skype, TeamSpeak, some games<br />
* Packages that use x86 32-bit assembler code (some emulators like zsnes and syslinux) although at least zsnes is available as 32-bit binary for Arch64 in the [[AUR]]<br />
* [[Wine]] (a x86_64 port is in the works)<br />
<br />
Almost everything else should be portable. If you miss any Arch32 package in our port and you know that it will compile on x86_64 (e.g. you have found it in another 64-bit distribution without using multilibs), just contact the devs.<br />
<br />
Wine, Skype and Zsnes are now easy to install with [[Yaourt]]:<br />
yaourt -S bin32-wine bin32-skype zsnes<br />
<br />
==Can I build 32-bit packages for i686 inside Arch64?==<br />
<br />
Yes. You need a working i686 chroot (installation with i686 iso "quickinstall" is recommended for the quick way to install it inside Arch64 or see [[Arch64 Install bundled 32bit system]]). Install "linux32" wrapper pkg from current to make the chroot behave like a real i686 system. Then use this script to login into the chroot environment as root:<br />
<br />
#!/bin/bash<br />
mount --bind /dev /path-to-your-chroot/dev<br />
mount --bind /dev/pts /path-to-your-chroot/dev/pts<br />
mount --bind /dev/shm /path-to-your-chroot/dev/shm<br />
mount -t proc none /path-to-your-chroot/proc<br />
mount -t sysfs none /path-to-your-chroot/sys<br />
linux32 chroot /path-to-your-chroot<br />
<br />
If you keep the sources on the x86_64 host system you can add<br />
"mount --bind /path-to-your-stored-sources /path-to-your-chroot/path-to-your-stored-sources" <br />
to share sources from host to chroot system for pkg building used in /etc/makepkg.conf.<br />
<br />
==Can I run 32-bit apps inside Arch64?==<br />
Yes! <br />
<br />
# You can install lib32-* libs from comunity repository for a Multilib system.<br />
# Or you can create another chroot with 32bit system:<br />
<br />
Boot into Arch64, startx, open a term.<br />
$ xhost +local:<br />
$ su<br />
# mount /dev/sda1 /mnt/arch32<br />
# mount --bind /proc /mnt/arch32/proc<br />
# chroot /mnt/arch32<br />
# su your32bitusername<br />
$ /usr/bin/command-you want # or eg: /opt/mozilla/bin/firefox<br />
<br />
Some 32-bit apps (like OpenOffice) may require additional bindings. The following lines can be placed in rc.local to ensure you get all you need for the 32-bit apps (assuming /mnt/arch32 is mounted in fstab):<br />
mount --bind /dev /mnt/arch32/dev<br />
mount --bind /dev/pts /mnt/arch32/dev/pts<br />
mount --bind /dev/shm /mnt/arch32/dev/shm<br />
mount --bind /proc /mnt/arch32/proc<br />
mount --bind /proc/bus/usb /mnt/arch32/proc/bus/usb<br />
mount --bind /sys /mnt/arch32/sys<br />
mount --bind /tmp /mnt/arch32/tmp<br />
#comment the following line if you do not use the same home folder<br />
mount --bind /home /mnt/arch32/home<br />
You can then type in a term:<br />
$ xhost +localhost<br />
$ sudo chroot /mnt/arch32 su your32bitusername /opt/openoffice/program/soffice<br />
<br />
==Can I upgrade/switch my system from i686 to x86_64 without reinstalling?==<br />
- No. However, you can start the system with the Arch64 install CD, mount the disk, backup anything you may want to keep that isn't a 32-bit binary (e.g: /home & /etc), and install.</div>Ik12https://wiki.archlinux.org/index.php?title=Talk:64-bit_FAQ&diff=63985Talk:64-bit FAQ2009-03-04T20:18:25Z<p>Ik12: </p>
<hr />
<div>===Flash===<br />
I removed the line about Flash because Flash for x86_64 is not alpha anymore.<br />
<br />
<br />
===32 bits apps in Arch64===<br />
Using_32-bit-applications_on_Arch64 mentions lib32-* being in community. Also, emul-* from gentoo are in the AUR.<br />
<br />
So maybe this should be updated: "Maybe we will place them into the AUR or community repo"<br />
<br />
===Switching from i686 to x86_64===<br />
I've just translated this page in French and at the end (the section concerning switching), I've mentionned the usage of pacman -Qq to get a file with all the installed packages. Maybe would it be a good idea to add that?</div>Ik12https://wiki.archlinux.org/index.php?title=GRUB_(%C4%8Ce%C5%A1tina)&diff=63961GRUB (Čeština)2009-03-04T18:08:07Z<p>Ik12: I've add an entry concerning the translantion in French of this page.</p>
<hr />
<div>[[Category:Boot process (Česky)]]<br />
[[Category:HOWTOs (Česky)]]<br />
{{Article summary start}}<br />
{{Article summary text|Shrnuje různé aspekty příští generace GRand Unified Bootloader (GRUB2).}}<br />
<br />
{{Article summary heading|Dostupné v jazycích}}<br />
{{i18n_entry|English|GRUB2}}<br />
{{i18n_entry|Česky|GRUB2 (Česky)}}<br />
{{i18n_entry|Français|GRUB2 (Français)}}<br />
{{Article summary end}}<br />
<br />
== Úvod ==<br />
'''Varování:''' Příští generace GRand Unified Bootloader (GRUB2) je stále pod vývojem a proto platí všechny obvyklé body. GRUB2 může zavařit váš počítač, zapálit váš dům nebo sníst vaši kočku. Byli jste varováni! Pro většinu lidí kromě těch s exotičtějšími konfiguracemi by GRUB2 měl prostě fungovat.<br />
<br />
Mezi GRUBem a GRUB2 proběhly změny v příkazech. Než budete pokračovat, můžete se s nimi chtít seznámit.<br />
Např.: "find" bylo změněno na "search".<br />
<br />
http://grub.enbug.org/CommandList<br />
<br />
== Instalace balíčku grub2 ==<br />
<br />
Nejdříve nainstalujte grub2 pomocí pacmana:<br />
# pacman -Sy grub2<br />
<br />
Upravte konfigurační soubor grub2 podle svého nastavení. "Starý" soubor menu.lst je nahrazen novým souborem pod názvem grub.cfg.<br />
# nano /boot/grub/grub.cfg<br />
<br />
'''''Poznámka:''' Používejte hd[a-z] pro ide a sd[a-z] pro scsi a sata''<br />
<br />
Zde je příklad jednoduchého konfiguračního souboru:<br />
# Config file for GRUB2 - The GNU GRand Unified Bootloader<br />
# /boot/grub/grub.cfg<br />
<br />
# DEVICE NAME CONVERSIONS<br />
#<br />
# Linux Grub<br />
# -------------------------<br />
# /dev/fd0 (fd0)<br />
# /dev/sda (hd0)<br />
# /dev/sdb2 (hd1,2)<br />
# /dev/sda3 (hd0,3)<br />
#<br />
<br />
# Timeout for menu<br />
set timeout=5<br />
<br />
# Set default boot entry as Entry 0<br />
set default=0<br />
<br />
# (0) Arch Linux<br />
menuentry "Arch Linux" {<br />
set root=(hd0,1)<br />
linux /vmlinuz26 root=/dev/sda1 ro<br />
initrd /kernel26.img<br />
}<br />
<br />
## (1) Windows<br />
#menuentry "Windows" {<br />
#set root=(hd0,3)<br />
#chainloader +1<br />
#}<br />
<br />
Pokud nemáte zvlášť oddělený bootovací oddíl, musí být do grub.cfg přidáno '<code>/boot</code>'. Příklad:<br />
<br />
# (0) Arch Linux<br />
menuentry "Arch Linux" {<br />
set root=(hd0,1)<br />
linux /boot/vmlinuz26 root=/dev/sda1 ro<br />
initrd /boot/kernel26.img<br />
}<br />
<br />
== Instalace nebo obnova GRUBu do hlavního spouštěcího záznamu (MBR) ==<br />
GRUB může být nainstalován buď z live prostředí nebo přímo z běžící instalace Arch Linuxu.<br />
<br />
Ve většině případů je instalace grub2 tak jednoduchá jako spuštění příkazu '''grub-install''' pod rootem:<br />
# grub-install /dev/sda<br />
kde /dev/sda je cíl instalace (v tomto případě MBR prvního SATA disku).<br />
<br />
Pokud toto selže s chybou:<br />
grub-probe: error: Cannot get the real path of `/dev/fd0'<br />
Auto-detection of a filesystem module failed.<br />
Please specify the module with the option `--modules' explicitly.<br />
Zkuste do parametrů přidat <code>--recheck</code> takto:<br />
# grub-install --recheck /dev/sda<br />
<br />
Případně byste měli být schopni nainstalovat grub2 nabootováním do systému a spuštěním příkazu '''grub''' pod rootem:<br />
# grub<br />
{tato sekce je stále nedokončená, měly by být přidány další kroky!!!}<br />
(grub2 nemá interaktivní prompt)<br />
<br />
== Konfigurace zavaděče ==<br />
Konfigurace grubu se provádí v tomto souboru:<br />
/boot/grub/grub.cfg<br />
<br />
Tato část zatím není kompletní, můžete sem přidat všechny chybějící konfigurační volby!<br />
<br />
* ''(hdn,m)'' &ndash; je oddíl ''m'' na disku ''n'', čísla oddílů začínají od 1, čísla disků začínají od 0<br />
* ''set default=n'' &ndash;je výchozí položka pro zavedení, jenž je automaticky zvolena po časovém limitu pro akce od uživatele<br />
* ''set timeout=m'' &ndash;čas ''m'' v sekundách, po který se má čekat na výběr uživatele, než je zavedena výchozí položka<br />
* ''menuentry "str"{volby položky}'' &ndash; titulek ''str'' pro položku a základní rozvržení<br />
* ''set root=(hdn,m)'' &ndash;základní diskový oddíl, kde je uloženo jádro<br />
* ''linux /path ro root=/dev/device initrd /initrd.img'' &ndash; volbu root použijte, pokud kernel není umístěn v /<br />
* ''chainloader +1'' &ndash; nastaví root jako aktivní a předá řízení jeho zavaděči (pro Windows, např.)<br />
<br />
Pro UUID záznamy:<br />
bash-3.2# blkid<br />
<br />
<br />
=== Dual booting ===<br />
Toto jsou dvě nejčastější cesty konfigurace souboru grub.cfg. Pro složitější účely sem klidně můžete přidat vysvětlení.<br />
<br />
====Dual booting s Windows====<br />
Přidejte toto na konec /boot/grub/menu.lst. Předpokládá se zde, že váš oddíl s Windows je [s/h]da3.<br />
<br />
# (2) Windows XP<br />
menuentry "Windows XP" {<br />
set root=(hd0,3)<br />
chainloader +1<br />
}<br />
<br />
Poznámka: Přestože se v to obecně věří, Windows 2000 a pozdější nemusí být na prvním oddílu, aby se spustily. Pokud oddíl s Windows změní číslo (např. když přidáte nový oddíl před oddíl s Windows), musíte upravit soubor boot.ini, abyste odrazili tuto změnu (viz [http://vlaurie.com/computers2/Articles/bootini.htm tento článek] pro detaily o tom, jak to udělat).<br />
<br />
====Dual booting s jinými distribucemi Linuxu====<br />
Toto se provede přesně tím samým způsobem, jak je zaveden Arch Linux. Zde předpokládáme, že další distribuce je na oddílu [s/h]da2.<br />
<br />
menuentry "Other Linux" {<br />
set root=(hd0,2)<br />
linux /boot/vmlinuz (add other options here as required)<br />
initrd /boot/initrd.img (if the other kernel uses/needs one)<br />
}<br />
<br />
==Tipy a triky==<br />
<br />
===Barvy v menu===<br />
Pro změnu barev v GRUB2 uveďte v /boot/grub/grub.cfg tyto dvě volby:<br />
<br />
set menu_color_normal=light-blue/black<br />
set menu_color_highlight=light-cyan/blue<br />
<br />
Toto jsou výchozí barvy pro verzi GRUB-legacy v Arch Linuxu. Dostupné barvy jsou zatím nezdokumentované, ale pravděpodobně se shodují s barvami GRUB-legacy.<br />
<br />
== Řešení problémů ==<br />
Sem by měla být přidána všechna řešení problémů.<br />
<br />
== Další zdroje ==<br />
* [http://www.gnu.org/software/grub/ GRUB Homepage]<br />
* [http://grub.enbug.org/ GRUB wiki]</div>Ik12https://wiki.archlinux.org/index.php?title=GRUB&diff=63960GRUB2009-03-04T18:07:20Z<p>Ik12: I've add an entry concerning the translantion in French of this page.</p>
<hr />
<div>[[Category:Boot process (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{Article summary start}}<br />
{{Article summary text|Covers various aspects of the next generation of the GRand Unified Bootloader (GRUB2).}}<br />
<br />
{{Article summary heading|Available in languages}}<br />
{{i18n_entry|English|GRUB2}}<br />
{{i18n_entry|Česky|GRUB2 (Česky)}}<br />
{{i18n_entry|Français|GRUB2 (Français)}}<br />
{{Article summary end}}<br />
<br />
== Introduction ==<br />
'''Warning:''' The next generation of the GRand Unified Bootloader (GRUB2) is still under development and therefore all usual points apply. GRUB2 may fry your computer, burn your house, or eat your cat. You've been warned! For most people, except those with more exotic configurations, GRUB2 should just work.<br />
<br />
Commands - changes between GRUB and GRUB2. You may want to familiarise yourself with these before proceeding.<br />
E.g.: "find" has been replaced with "search"<br />
<br />
http://grub.enbug.org/CommandList<br />
<br />
== Installing Grub2 package ==<br />
<br />
First install grub2 with pacman:<br />
# pacman -Sy grub2<br />
<br />
Edit the grub2 configuration file with your settings. The 'old' menu.lst is replaced by a new file called grub.cfg<br />
# nano /boot/grub/grub.cfg<br />
<br />
'''''Note:''' Use hd[a-z] for ide and sd[a-z] for scsi and sata''<br />
<br />
Here is an example of a simple configuration file:<br />
# Config file for GRUB2 - The GNU GRand Unified Bootloader<br />
# /boot/grub/grub.cfg<br />
<br />
# DEVICE NAME CONVERSIONS<br />
#<br />
# Linux Grub<br />
# -------------------------<br />
# /dev/fd0 (fd0)<br />
# /dev/sda (hd0)<br />
# /dev/sdb2 (hd1,2)<br />
# /dev/sda3 (hd0,3)<br />
#<br />
<br />
# Timeout for menu<br />
set timeout=5<br />
<br />
# Set default boot entry as Entry 0<br />
set default=0<br />
<br />
# (0) Arch Linux<br />
menuentry "Arch Linux" {<br />
set root=(hd0,1)<br />
linux /vmlinuz26 root=/dev/sda1 ro<br />
initrd /kernel26.img<br />
}<br />
<br />
## (1) Windows<br />
#menuentry "Windows" {<br />
#set root=(hd0,3)<br />
#chainloader +1<br />
#}<br />
<br />
If you do not have a seperate boot-partition, '<code>/boot</code>' must be added to grub.cfg. Example:<br />
<br />
# (0) Arch Linux<br />
menuentry "Arch Linux" {<br />
set root=(hd0,1)<br />
linux /boot/vmlinuz26 root=/dev/sda1 ro<br />
initrd /boot/kernel26.img<br />
}<br />
<br />
== Installing or Restoring GRUB to the Master Boot Record ==<br />
GRUB may be installed from a live environment, or directly from a running Arch install.<br />
<br />
In most cases, installing grub2 would be as easy as running the '''grub-install''' command as root:<br />
# grub-install /dev/sda<br />
where /dev/sda is the destination of the installation (in this case the MBR of the first SATA disc)<br />
<br />
If this fails with the error:<br />
grub-probe: error: Cannot get the real path of `/dev/fd0'<br />
Auto-detection of a filesystem module failed.<br />
Please specify the module with the option `--modules' explicitly.<br />
Try adding <code>--recheck</code> to the arguments as follows:<br />
# grub-install --recheck /dev/sda<br />
<br />
Alternatively, you should be able to install grub2 by booting the system and running the '''grub''' command as root:<br />
# grub<br />
{this section is still incomplete, some steps should be added!!!}<br />
(grub2 doesn't have an interactive prompt)<br />
<br />
== Boot loader configuration ==<br />
The grub configuration is done in this file:<br />
/boot/grub/grub.cfg<br />
<br />
Be warned this section is incomplete, feel free to put all missing configuration options here!<br />
<br />
* ''(hdn,m)'' is the partition ''m'' on disc ''n'', partition numbers starting with 1, disc numbers starting with 0<br />
* ''set default=n'' is the default boot entry, that is choosen after timout for user action<br />
* ''set timeout=m'' time ''m'' to wait in seconds for a user selection, before default is booted<br />
* ''menuentry "str"{entry options}'' title string 'str' for a boot entry & basic layout<br />
* ''set root=(hdn,m)'' base partition, where the kernel is stored to<br />
* ''linux /path ro root=/dev/device initrd /initrd.img'' use the root option, if the kernel not placed in /<br />
* ''chainloader +1'' sets ''root'' active and gives booting procedure to its boot-loader (for Windows, f.e.)<br />
<br />
For UUID entries:<br />
bash-3.2# blkid<br />
<br />
<br />
=== Dual booting===<br />
These are the two most common ways of configuring the grub.cfg file. For more complex uses, feel free to add descriptions here.<br />
<br />
====Dual booting with Windows====<br />
Add this at the end of your /boot/grub/menu.lst. This assumes that your Windows partition is [s/h]da3.<br />
<br />
# (2) Windows XP<br />
menuentry "Windows XP" {<br />
set root=(hd0,3)<br />
chainloader +1<br />
}<br />
<br />
Note, that although commonly believed to be the case, Windows 2000 and later versions do not need to be on the first partition to boot. If the Windows partition changes number (i.e. if you after install add a partition before the windows partition), you will need to edit the Windows boot.ini file to reflect the change (see [http://vlaurie.com/computers2/Articles/bootini.htm this article] for details on how to do that).<br />
<br />
====Dual booting with other linux distros====<br />
This is done exactly the same way that Arch linux is loaded. Here we assume that the other distro is on partition [s/h]da2.<br />
menuentry "Other Linux" {<br />
set root=(hd0,2)<br />
linux /boot/vmlinuz (add other options here as required)<br />
initrd /boot/initrd.img (if the other kernel uses/needs one)<br />
}<br />
<br />
==Tips and tricks==<br />
<br />
===Menu Colors===<br />
<br />
To change the colors in GRUB2 you would specify two options in /boot/grub/grub.cfg:<br />
<br />
set menu_color_normal=light-blue/black<br />
set menu_color_highlight=light-cyan/blue<br />
<br />
These are the default colors for Arch's release of GRUB-legacy. The available colors are undocumented as of yet, but they probably match GRUB-legacy's colors.<br />
<br />
== Troubleshooting ==<br />
Any troubleshooting should be added here.<br />
<br />
== More Resources ==<br />
* [http://www.gnu.org/software/grub/ GRUB Homepage]<br />
* [http://grub.enbug.org/ GRUB wiki]</div>Ik12