https://wiki.archlinux.org/api.php?action=feedcontributions&user=Droog&feedformat=atomArchWiki - User contributions [en]2024-03-28T11:14:50ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Browser_plugins&diff=68172Browser plugins2009-05-04T09:12:23Z<p>Droog: /* OSS */</p>
<hr />
<div>[[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 />
= 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 />
=== OSS ===<br />
If you use OSS, sound may not work with Flash videos (but videos will still play), you may need to download <code>libflashsupport</code><br />
<br />
pacman -S libflashsupport<br />
<br />
This gives OSS support for the Flash plugin; no restarts, even on Firefox are necessary once the library is installed.<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 />
==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 />
= 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 bad support for 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 bad support for 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 />
=For Arch64 users=<br />
[[Install Flash on Arch64]]</div>Drooghttps://wiki.archlinux.org/index.php?title=Convert_a_single_drive_system_to_RAID&diff=67133Convert a single drive system to RAID2009-04-19T02:34:34Z<p>Droog: /* Rebuild initcpio */</p>
<hr />
<div>[[Category:Storage (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
You already have a fully functional system setup on a single drive, but you would like to add some redundancy to the setup by using RAID-1 to mirror your data across 2 drives. This guide follows the following steps to make the required changes, without losing data.<br />
* Create a single-disk RAID-1 array with our new disk<br />
* Move all your data from the old-disk to the new RAID-1 array<br />
* Verify the data move was successful<br />
* Wipe the old disk and add it to the new RAID-1 array<br />
<br />
'''WARNING: Make a backup first. Even though our aim is to convert to a RAID setup without losing data, there's no guarantees the process will be perfect, and there is a high risk of accidents happening.'''<br />
<br />
== Assumptions ==<br />
* I will assume for the sake of the guide that the disk currently in your system is ''/dev/sda'' and your new disk is ''/dev/sdb''.<br />
* We will create the following configuration:<br />
1 x RAID-1 array for the file-system (using 2 x partitions, 1 on each disk)<br />
2 x Swap Partitions using 1 partition on each disk.<br />
The swap partitions will not be in a RAID array as having swap on RAID serves no purpose. Refer to this article for reasons why: [[http://unthought.net/Software-RAID.HOWTO/Software-RAID.HOWTO-2.html#ss2.3]]<br />
<br />
* To minimize the risk of Data on Disk (DoD) changing in the middle of our changes, I suggest you drop to single user mode before you start by using the ''init 1'' command.<br />
<br />
* You will need to be the root user for the entire process.<br />
<br />
== Create New RAID Array ==<br />
First we need to create a single-disk RAID array using the new disk.<br />
=== Partition the Disk ===<br />
Use fdisk or your partitioning program of choice to setup 2 primary partitions on your new disk. Make the swap partition half the size of the total swap you want (the other half will go on the other disk).<br />
<br />
[root@arch ~]# fdisk -l /dev/sdb<br />
Disk /dev/sdb: 80.0 GB, 80025280000 bytes<br />
255 heads, 63 sectors/track, 9729 cylinders<br />
Units = cylinders of 16065 * 512 = 8225280 bytes<br />
Disk identifier: 0x00000000<br />
<br />
Device Boot Start End Blocks Id System<br />
/dev/sdb1 1 66 530113+ 82 Linux swap / Solaris<br />
/dev/sdb2 67 9729 77618047+ fd Linux raid autodetect<br />
<br />
Make sure your your partition types are set correctly. "Linux Swap" is type 82 and "Linux raid autodetect" is type FD<br />
<br />
=== Create the RAID Device ===<br />
Next, create the single-disk RAID-1 array. Note the 'missing' keyword is specified as one of our devices.<br />
[root@arch ~]# mdadm --create /dev/md0 --level=1 --raid-devices=2 missing /dev/sdb2<br />
mdadm: array /dev/md0 started.<br />
<br />
Make sure the array has been created correctly by checking /proc/mdstat<br />
[root@arch ~]# cat /proc/mdstat<br />
Personalities : [linear] [raid0] [raid1] [raid5] [multipath] [raid6] [raid10]<br />
md0 : active raid1 sdb2[1]<br />
40064 blocks [2/1] [_U]<br />
<br />
unused devices: <none><br />
<br />
The devices are intact, however in a degraded state (because it's missing half the array!)<br />
<br />
=== Make File Systems ===<br />
Use whatever filesystem is your preference here. I'll use ext3 for this guide.<br />
[root@arch ~]# mkfs -t ext3 -j /dev/md0<br />
mke2fs 1.38 (30-Jun-2005)<br />
Filesystem label=<br />
OS type: Linux<br />
Block size=4096 (log=2)<br />
Fragment size=4096 (log=2)<br />
10027008 inodes, 20027008 blocks<br />
1001350 blocks (5.00%) reserved for the super user<br />
First data block=0<br />
612 block groups<br />
32768 blocks per group, 32768 fragments per group<br />
16384 inodes per group<br />
Superblock backups stored on blocks:<br />
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,<br />
4096000, 7962624, 11239424<br />
<br />
Writing inode tables: done<br />
Creating journal (32768 blocks): done<br />
Writing superblocks and filesystem accounting information: done<br />
<br />
This filesystem will be automatically checked every 25 mounts or<br />
180 days, whichever comes first. Use tune2fs -c or -i to override.<br />
<br />
Make a file system on the swap partition.<br />
[root@arch ~]# mkswap /dev/sdb1<br />
Setting up swapspace version 1, size = 271314 kB<br />
no label, UUID=9d746813-2d6b-4706-a56a-ecfd108f3fe9<br />
<br />
== Copy Data ==<br />
The new RAID-1 array is ready to start accepting data! So now we need to mount the array, and copy everything from the old system to the new system<br />
<br />
=== Mount the Array ===<br />
[root@arch ~]# mkdir /mnt/new-raid<br />
[root@arch ~]# mount /dev/md0 /mnt/new-raid<br />
<br />
=== Copy the Data ===<br />
[root@arch ~]# cd /mnt/new-raid<br />
[root@arch mnt]# tar -C / -clspf - . | tar -xlspvf -<br />
<br />
=== Update GRUB ===<br />
Use your preferred text editor to open /mnt/new-raid/boot/grub/menu.lst<br />
<br />
--- SNIP ---<br />
default 0<br />
color light-blue/black light-cyan/blue<br />
<br />
## fallback<br />
fallback 1<br />
<br />
# (0) Arch Linux<br />
title Arch Linux - Original Disc<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda1<br />
<br />
# (1) Arch Linux<br />
title Arch Linux - New RAID<br />
root (hd1,0)<br />
#kernel /vmlinuz26 root=/dev/sda1 ro<br />
kernel /vmlinuz26 root=/dev/md0<br />
--- SNIP ---<br />
Notice we added the ''fallback'' line and duplicated the Arch Linux entry with a different ''root'' directive on the kernel line.<br />
<br />
=== Alter fstab ===<br />
You need to tell fstab on the '''new''' disk where to find the new devices<br />
[root@arch ~]# cat /mnt/new-raid/etc/fstab<br />
/dev/md0 / ext3 defaults 0 1<br />
/dev/sdb1 swap swap defaults 0 0<br />
<br />
=== Rebuild initcpio ===<br />
[root@arch ~]# mount --bind /sys /mnt/new-raid/sys<br />
[root@arch ~]# mount --bind /proc /mnt/new-raid/proc<br />
[root@arch ~]# mount --bind /dev /mnt/new-raid/dev<br />
[root@arch ~]# chroot /mnt/new-raid/<br />
[root ~]# chroot /mnt/new-raid/<br />
You are now chrooted in what will become the root of your RAID-1 system. Edit /etc/mkinitcpio.conf to include 'raid' in the HOOKS array. Place it before 'autodetect' but after 'sata', 'scsi' and 'pata' (whichever is appropriate for your hardware)<br />
[root ~]# mkinitcpio -g /boot/kernel26.img<br />
[root ~]# exit<br />
<br />
=== Install GRUB on the RAID Array ===<br />
[root@arch /]# grub<br />
grub> root (hd1,1)<br />
Filesystem type is ext2fs, partition type 0xfd<br />
<br />
grub> setup (hd1)<br />
Checking if "/boot/grub/stage1" exists... yes<br />
Checking if "/boot/grub/stage2" exists... yes<br />
Checking if "/boot/grub/e2fs_stage1_5" exists... yes<br />
Running "embed /boot/grub/e2fs_stage1_5 (hd1)"... 16 sectors are embedded. succeeded<br />
Running "install /boot/grub/stage1 (hd1) (hd1)1+16 p (hd1,0)/boot/grub/stage2 /boot/grub/grub.conf"... succeeded<br />
Done<br />
grub>quit<br />
<br />
== Verify Success ==<br />
Reboot your computer, making sure it boots from the new raid disk (/dev/sdb) and not the original disk (/dev/sda). You may need to change the boot device priorities in your BIOS to do this.<br />
<br />
Once the GRUB on the '''new''' disk loads, make sure you select to boot the new entry you created in menu.lst earlier.<br />
<br />
Verify you have booted from the RAID array by looking at the output of mount. you should have a line similar to the following in the output:<br />
[root@arch ~]# mount<br />
/dev/md0 on / type ext3 (rw)<br />
Also ''swapon -s''<br />
[root@arch ~]# swapon -s<br />
Filename Type Size Used Priority<br />
/dev/sdb1 partition 4000144 16 -1<br />
Note it is the swap partition on ''sdb'' that is in use, nothing from ''sda''<br />
<br />
If system boots fine, and the output of the above commands is correct, then congratulations! You're now running off the degraded RAID array. We can add the original disk to the array now to bring it up to full performance.<br />
<br />
== Add Original Disk to Array ==<br />
<br />
=== Partition Original Disk ===<br />
Take the output of fdisk -l on your new disk, and make the partitions on your original disk look the same.<br />
[root@arch ~]# fdisk -l /dev/sda<br />
Disk /dev/sda: 80.0 GB, 80025280000 bytes<br />
255 heads, 63 sectors/track, 9729 cylinders<br />
Units = cylinders of 16065 * 512 = 8225280 bytes<br />
Disk identifier: 0x00000000<br />
<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 1 66 530113+ 82 Linux swap / Solaris<br />
/dev/sda2 67 9729 77618047+ fd Linux raid autodetect<br />
<br />
=== Add Disk to Array ===<br />
[root@svn ~]# mdadm /dev/md0 -a /dev/sda2<br />
mdadm: hot added /dev/sda2<br />
<br />
Verify that the RAID array is being rebuilt.<br />
[root@arch ~]# cat /proc/mdstat<br />
Personalities : [linear] [raid0] [raid1] [raid5] [multipath] [raid6] [raid10]<br />
md0 : active raid1 sda2[2] sdb2[1]<br />
80108032 blocks [2/1] [_U]<br />
[>....................] recovery = 1.2% (1002176/80108032) finish=42.0min speed=31318K/sec<br />
<br />
unused devices: <none></div>Drooghttps://wiki.archlinux.org/index.php?title=Convert_a_single_drive_system_to_RAID&diff=67131Convert a single drive system to RAID2009-04-19T02:30:57Z<p>Droog: /* Create the RAID Device */</p>
<hr />
<div>[[Category:Storage (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
You already have a fully functional system setup on a single drive, but you would like to add some redundancy to the setup by using RAID-1 to mirror your data across 2 drives. This guide follows the following steps to make the required changes, without losing data.<br />
* Create a single-disk RAID-1 array with our new disk<br />
* Move all your data from the old-disk to the new RAID-1 array<br />
* Verify the data move was successful<br />
* Wipe the old disk and add it to the new RAID-1 array<br />
<br />
'''WARNING: Make a backup first. Even though our aim is to convert to a RAID setup without losing data, there's no guarantees the process will be perfect, and there is a high risk of accidents happening.'''<br />
<br />
== Assumptions ==<br />
* I will assume for the sake of the guide that the disk currently in your system is ''/dev/sda'' and your new disk is ''/dev/sdb''.<br />
* We will create the following configuration:<br />
1 x RAID-1 array for the file-system (using 2 x partitions, 1 on each disk)<br />
2 x Swap Partitions using 1 partition on each disk.<br />
The swap partitions will not be in a RAID array as having swap on RAID serves no purpose. Refer to this article for reasons why: [[http://unthought.net/Software-RAID.HOWTO/Software-RAID.HOWTO-2.html#ss2.3]]<br />
<br />
* To minimize the risk of Data on Disk (DoD) changing in the middle of our changes, I suggest you drop to single user mode before you start by using the ''init 1'' command.<br />
<br />
* You will need to be the root user for the entire process.<br />
<br />
== Create New RAID Array ==<br />
First we need to create a single-disk RAID array using the new disk.<br />
=== Partition the Disk ===<br />
Use fdisk or your partitioning program of choice to setup 2 primary partitions on your new disk. Make the swap partition half the size of the total swap you want (the other half will go on the other disk).<br />
<br />
[root@arch ~]# fdisk -l /dev/sdb<br />
Disk /dev/sdb: 80.0 GB, 80025280000 bytes<br />
255 heads, 63 sectors/track, 9729 cylinders<br />
Units = cylinders of 16065 * 512 = 8225280 bytes<br />
Disk identifier: 0x00000000<br />
<br />
Device Boot Start End Blocks Id System<br />
/dev/sdb1 1 66 530113+ 82 Linux swap / Solaris<br />
/dev/sdb2 67 9729 77618047+ fd Linux raid autodetect<br />
<br />
Make sure your your partition types are set correctly. "Linux Swap" is type 82 and "Linux raid autodetect" is type FD<br />
<br />
=== Create the RAID Device ===<br />
Next, create the single-disk RAID-1 array. Note the 'missing' keyword is specified as one of our devices.<br />
[root@arch ~]# mdadm --create /dev/md0 --level=1 --raid-devices=2 missing /dev/sdb2<br />
mdadm: array /dev/md0 started.<br />
<br />
Make sure the array has been created correctly by checking /proc/mdstat<br />
[root@arch ~]# cat /proc/mdstat<br />
Personalities : [linear] [raid0] [raid1] [raid5] [multipath] [raid6] [raid10]<br />
md0 : active raid1 sdb2[1]<br />
40064 blocks [2/1] [_U]<br />
<br />
unused devices: <none><br />
<br />
The devices are intact, however in a degraded state (because it's missing half the array!)<br />
<br />
=== Make File Systems ===<br />
Use whatever filesystem is your preference here. I'll use ext3 for this guide.<br />
[root@arch ~]# mkfs -t ext3 -j /dev/md0<br />
mke2fs 1.38 (30-Jun-2005)<br />
Filesystem label=<br />
OS type: Linux<br />
Block size=4096 (log=2)<br />
Fragment size=4096 (log=2)<br />
10027008 inodes, 20027008 blocks<br />
1001350 blocks (5.00%) reserved for the super user<br />
First data block=0<br />
612 block groups<br />
32768 blocks per group, 32768 fragments per group<br />
16384 inodes per group<br />
Superblock backups stored on blocks:<br />
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,<br />
4096000, 7962624, 11239424<br />
<br />
Writing inode tables: done<br />
Creating journal (32768 blocks): done<br />
Writing superblocks and filesystem accounting information: done<br />
<br />
This filesystem will be automatically checked every 25 mounts or<br />
180 days, whichever comes first. Use tune2fs -c or -i to override.<br />
<br />
Make a file system on the swap partition.<br />
[root@arch ~]# mkswap /dev/sdb1<br />
Setting up swapspace version 1, size = 271314 kB<br />
no label, UUID=9d746813-2d6b-4706-a56a-ecfd108f3fe9<br />
<br />
== Copy Data ==<br />
The new RAID-1 array is ready to start accepting data! So now we need to mount the array, and copy everything from the old system to the new system<br />
<br />
=== Mount the Array ===<br />
[root@arch ~]# mkdir /mnt/new-raid<br />
[root@arch ~]# mount /dev/md0 /mnt/new-raid<br />
<br />
=== Copy the Data ===<br />
[root@arch ~]# cd /mnt/new-raid<br />
[root@arch mnt]# tar -C / -clspf - . | tar -xlspvf -<br />
<br />
=== Update GRUB ===<br />
Use your preferred text editor to open /mnt/new-raid/boot/grub/menu.lst<br />
<br />
--- SNIP ---<br />
default 0<br />
color light-blue/black light-cyan/blue<br />
<br />
## fallback<br />
fallback 1<br />
<br />
# (0) Arch Linux<br />
title Arch Linux - Original Disc<br />
root (hd0,0)<br />
kernel /vmlinuz26 root=/dev/sda1<br />
<br />
# (1) Arch Linux<br />
title Arch Linux - New RAID<br />
root (hd1,0)<br />
#kernel /vmlinuz26 root=/dev/sda1 ro<br />
kernel /vmlinuz26 root=/dev/md0<br />
--- SNIP ---<br />
Notice we added the ''fallback'' line and duplicated the Arch Linux entry with a different ''root'' directive on the kernel line.<br />
<br />
=== Alter fstab ===<br />
You need to tell fstab on the '''new''' disk where to find the new devices<br />
[root@arch ~]# cat /mnt/new-raid/etc/fstab<br />
/dev/md0 / ext3 defaults 0 1<br />
/dev/sdb1 swap swap defaults 0 0<br />
<br />
=== Rebuild initcpio ===<br />
[root@arch ~]# mount --bind /sys /mnt/new-raid/sys<br />
[root@arch ~]# mount --bind /proc /mnt/new-raid/proc<br />
[root@arch ~]# mount --bind /dev /mnt/new-raid/dev<br />
[root@arch ~]# chroot /mnt/new-raid/<br />
[root ~]# chroot /mnt/new-raid/<br />
You are now chrooted in the what will become the root of your RAID-1 system. Edit /etc/mkinitcpio.conf to include 'raid' in the HOOKS array. Place it before 'autodetect' but after 'sata', 'scsi' and 'pata' (whichever is appropriate for your hardware)<br />
[root ~]# mkinitcpio -g /boot/kernel26.img<br />
[root ~]# exit<br />
<br />
=== Install GRUB on the RAID Array ===<br />
[root@arch /]# grub<br />
grub> root (hd1,1)<br />
Filesystem type is ext2fs, partition type 0xfd<br />
<br />
grub> setup (hd1)<br />
Checking if "/boot/grub/stage1" exists... yes<br />
Checking if "/boot/grub/stage2" exists... yes<br />
Checking if "/boot/grub/e2fs_stage1_5" exists... yes<br />
Running "embed /boot/grub/e2fs_stage1_5 (hd1)"... 16 sectors are embedded. succeeded<br />
Running "install /boot/grub/stage1 (hd1) (hd1)1+16 p (hd1,0)/boot/grub/stage2 /boot/grub/grub.conf"... succeeded<br />
Done<br />
grub>quit<br />
<br />
== Verify Success ==<br />
Reboot your computer, making sure it boots from the new raid disk (/dev/sdb) and not the original disk (/dev/sda). You may need to change the boot device priorities in your BIOS to do this.<br />
<br />
Once the GRUB on the '''new''' disk loads, make sure you select to boot the new entry you created in menu.lst earlier.<br />
<br />
Verify you have booted from the RAID array by looking at the output of mount. you should have a line similar to the following in the output:<br />
[root@arch ~]# mount<br />
/dev/md0 on / type ext3 (rw)<br />
Also ''swapon -s''<br />
[root@arch ~]# swapon -s<br />
Filename Type Size Used Priority<br />
/dev/sdb1 partition 4000144 16 -1<br />
Note it is the swap partition on ''sdb'' that is in use, nothing from ''sda''<br />
<br />
If system boots fine, and the output of the above commands is correct, then congratulations! You're now running off the degraded RAID array. We can add the original disk to the array now to bring it up to full performance.<br />
<br />
== Add Original Disk to Array ==<br />
<br />
=== Partition Original Disk ===<br />
Take the output of fdisk -l on your new disk, and make the partitions on your original disk look the same.<br />
[root@arch ~]# fdisk -l /dev/sda<br />
Disk /dev/sda: 80.0 GB, 80025280000 bytes<br />
255 heads, 63 sectors/track, 9729 cylinders<br />
Units = cylinders of 16065 * 512 = 8225280 bytes<br />
Disk identifier: 0x00000000<br />
<br />
Device Boot Start End Blocks Id System<br />
/dev/sda1 1 66 530113+ 82 Linux swap / Solaris<br />
/dev/sda2 67 9729 77618047+ fd Linux raid autodetect<br />
<br />
=== Add Disk to Array ===<br />
[root@svn ~]# mdadm /dev/md0 -a /dev/sda2<br />
mdadm: hot added /dev/sda2<br />
<br />
Verify that the RAID array is being rebuilt.<br />
[root@arch ~]# cat /proc/mdstat<br />
Personalities : [linear] [raid0] [raid1] [raid5] [multipath] [raid6] [raid10]<br />
md0 : active raid1 sda2[2] sdb2[1]<br />
80108032 blocks [2/1] [_U]<br />
[>....................] recovery = 1.2% (1002176/80108032) finish=42.0min speed=31318K/sec<br />
<br />
unused devices: <none></div>Drooghttps://wiki.archlinux.org/index.php?title=AUR_Cleanup_Day/2010&diff=42500AUR Cleanup Day/20102008-06-03T03:57:32Z<p>Droog: /* Package List */</p>
<hr />
<div>'''NOTE: TU's are currently working through the list'''. You can still add packages but please check the whole page first.<br />
<br />
<br />
The AUR has a large number of obsolete packages which could use cleaning up. Examples of packages that may be cleaned up are:<br />
*packages that have been renamed or replaced<br />
*old and unmaintained developmental (cvs/svn/etc) packages<br />
<br />
Post suggestions of packages on this pages. Trusted Users will get together and go though the list in a couple of weeks and confirm which packages should be removed. '''Please DO NOT REMOVE suggestions from the wiki page but add a comment on why it should be kept instead.''' TUs will not delete any useful package.<br />
<br />
==Package List==<br />
'''Add new packages here''' - check for the package in the sorted lists below before adding<br />
<br />
* [http://aur.archlinux.org/packages.php?ID=13014 advi] - seems to be unmaintainable for the following reasons<br />
** The newest version 1.7.3 needs camlimages 3.0.0, which cannot be found on the net<br />
** camlimages' cvs-sources do not compile<br />
** package advi 1.6.0 has a patchfile of 102k size<br />
* [http://aur.archlinux.org/packages.php?ID=9026 audacious-docklet] - Doesnt work with latest audacious, not needed anymore either<br />
* [http://aur.archlinux.org/packages.php?ID=1731 ecamegapedal] - Do not to compile.<br />
* [http://aur.archlinux.org/packages.php?ID=4493 eclipse-kde] - Dead<br />
* [http://aur.archlinux.org/packages.php?ID=1926 fvwm-trans] last updated over 2 years ago and replaced with [http://aur.archlinux.org/packages.php?ID=7195 fvwm-patched] in AUR<br />
* [http://aur.archlinux.org/packages.php?ID=3698 galeon] - doesn't compile (not even the latest version)<br />
* [http://aur.archlinux.org/packages.php?ID=6069 gnuserv] - Deprecated in emacs-22+<br />
* [http://aur.archlinux.org/packages.php?ID=5207 gshare] - The package didn't function for me with the latest gnome. Furthermore it looks like this project is dead (website is down, source is no longer available)<br />
* [http://aur.archlinux.org/packages.php?ID=3689 ii-hg] - outdated, probably discontinued as the project website isn't available anymore (moved maybe?)<br />
** The project website is available at http://www.suckless.org/wiki/tools/irc/irc_it, so it's not dead. It only needs some changes to work again. --[[User:CuleX|CuleX]]<br />
* [http://aur.archlinux.org/packages.php?ID=7884 jfduke3d] - Is not updated by his author anymore, [http://aur.archlinux.org/packages.php?ID=15513 eduke32] was made to remplace it<br />
* [http://aur.archlinux.org/packages.php?ID=7037 kanola] - probably dead project, didn't went past the 0.0.1 release since 2006<br />
* [http://aur.archlinux.org/packages.php?ID=3429 lam 7.1.3-1] - Doesn't compile and is orphaned. The successor openmpi works.<br />
* [http://aur.archlinux.org/packages.php?ID=16889 libqglviewer-latest] - the same package as [http://aur.archlinux.org/packages.php?ID=7801 libqglviewer]<br />
* [http://aur.archlinux.org/packages.php?ID=14220 linuxdcpp-cvs] - Old, orphaned CVS version of a package in community<br />
* [http://aur.archlinux.org/packages.php?ID=7264 mencode] - outdated, tells aur is its homepage<br />
** The package is to install a perl script included in the AUR tarball so it doesn't really have a home page. So it could be kept if the script can still be useful or, at least, the script could be moved to the wiki if there is a page for scripts. --[[User:Snowman|Snowman]]<br />
* [http://aur.archlinux.org/packages.php?ID=5408 mlame] - just a small bash script, no project page, could be moved to the wiki maybe<br />
* [http://aur.archlinux.org/packages.php?ID=11581 mouseemu] - Project not updated since 2006; xautomation also allows mouse emulation.<br />
* [http://aur.archlinux.org/packages.php?ID=11498 mpd-pausemode] - "Website" is orig. contributor's email addr.; orphaned by this contributor, so presumably no longer developed.<br />
* [http://aur.archlinux.org/packages.php?ID=15401 org] - Out of date; also, included in Emacs 22+<br />
* [http://aur.archlinux.org/packages.php?ID=10514 rt61-cvs] - This driver is included in linus's tree and is therefore obsolete<br />
* [http://aur.archlinux.org/packages.php?ID=494 sonic-rainbow] - dead project, does not compile --[[User:Snowman|Snowman]]<br />
* [http://aur.archlinux.org/packages.php?ID=2612 stepmania-bin] - orphan, replaced by [http://aur.archlinux.org/packages.php?ID=5453 stepmania]<br />
* [http://aur.archlinux.org/packages.php?ID=15678 swt-devel] - I only created it to compile tuxguitar against it, but that's not needed. And it seems nobody is using it. <br />
* [http://aur.archlinux.org/packages.php?ID=3947 viki-svn] - old, pkgbuild is broken<br />
* [http://aur.archlinux.org/packages.php?ID=12067 pidgimpd-svn] - This package is orphaned and it doesn't build. There is mpd support in musictracker.<br />
* [http://aur.archlinux.org/packages.php?ID=6686 sizzle] - No upstream maintenance, does not compile.<br />
<br />
==TU Working Area==<br />
<br />
'''For editing by TUs only!''' The wiki has a history so do not think you can get away with ignoring this... --[[User:Allan|Allan]]<br />
<br />
===Packages to Remove===<br />
* [http://aur.archlinux.org/packages.php?ID=16166 jacman] - Jacman doesn't work correctly with pacman3. --[[User:Partition|Partition]]<br />
* [http://aur.archlinux.org/packages.php?ID=14992 slim-theme-darch] - in archlinux-themes-slim --[[User:Allan|Allan]]<br />
In community:<br />
* [http://aur.archlinux.org/packages.php?ID=12993 ion-modules] - ion3 is not part of official repos anymore, move to AUR --[[User:Allan|Allan]]<br />
* [http://aur.archlinux.org/packages.php?ID=9102 lmctl] - replaced by lomoco --[[User:Allan|Allan]]<br />
* [http://aur.archlinux.org/packages.php?ID=8958 wildfire] - Replaced by openfire. --[[User:pressh|pressh]]<br />
<br />
===Packages to Keep===<br />
* [http://aur.archlinux.org/packages.php?ID=14946 mplayer-w32codecs] - not duplicate package as has more codecs than the "codecs" package.<br />
** Should rename to "codecs-extra" and not provide same files as codecs package --[[User:Allan|Allan]]<br />
<br />
==Remove from Filesystem==<br />
<br />
This is a list of files on the AUR filesystem that have been created when poorly formed packages were uploaded. This is a secondary consideration.<br />
<br />
There are also directories in /packages/ for which the package no longer exists. These probably need to be removed as well. Examples are 4c, 1394commander and 8kingdoms. Also, all the packages that moved to community ALSO still exist here; for example 915resolution.<br />
<br />
<pre><br />
/packages/0verkill-0.16.tar.gz/<br />
/packages/0verkill-0.16/<br />
/packages/2007.02.17-2/<br />
/packages/abakus-0.91-1/<br />
/packages/abakus-0.91.tar.gz/<br />
/packages/abakus-0.91/<br />
/packages/akgregator/<br />
/packages/akregator/<br />
/packages/akregator1.0.2/<br />
/packages/akregator_1.0.2/<br />
/packages/amsn-0.97ec1/<br />
/packages/amsn-0.97rc1/<br />
/packages/amsn-097rc1-1/<br />
/packages/amsn-097rc1/<br />
/packages/amsn-cvs/<br />
/packages/amsn-svn_update/<br />
/packages/amsn096/<br />
/packages/amsn096rc1/<br />
/packages/bashstyle-5.0<br />
/packages/bashstyle-5.0rc1.tar.gz/<br />
/packages/bashstyle-5.0rc1.tar.gz1/<br />
/packages/bashstyle-5.0rc1/<br />
/packages/bashstyle.tar.gz/<br />
/packages/bashstyle-ng/<br />
/packages/bashstyle1/<br />
/packages/braero-svn<br />
/packages/braser-cvs/<br />
/packages/brasero-cvs/<br />
/packages/brasero.svn/<br />
/packages/brlcad-cvs/<br />
/packages/ccd2iso-0.3/<br />
/packages/cdcollect-0.6.0/<br />
/packages/centerim-4.22.2/<br />
/packages/centerim/<br />
/packages/ploticus-test/<br />
/packages/test-louipc/<br />
/packages/test/<br />
/packages/test_pkg/<br />
/packages/yacas-1.1.17-2/<br />
/packages/yacas-1.2.2/<br />
/packages/yacas-1.17-2/<br />
/packages/yacas-new/<br />
/packages/yacasnew/<br />
/packages/zzztest/<br />
/packages/zzzztest/<br />
</pre><br />
<br />
==Remove from Filesystem (AUR Bugs)==<br />
<br />
This is a list of files that need to be removed due to AUR bugs as they hinder proper submission and maintenance of packages.<br />
<br />
AUR Bugs<br />
* FS#8672 - http://bugs.archlinux.org/task/8672<br />
<br />
<pre><br />
/packages/advanceutils<br />
/packages/isight-firmware-tools<br />
/packages/mlt-svn<br />
/packages/perl-devel-stacktrace<br />
/packages/psi-qt4<br />
/packages/xcursor-industrial<br />
/packages/zaptel<br />
</pre><br />
<br />
/packages/lib32-dbus is now in community - Allan</div>Drooghttps://wiki.archlinux.org/index.php?title=AUR_Cleanup_Day/2010&diff=42499AUR Cleanup Day/20102008-06-03T03:55:56Z<p>Droog: /* Packages to Remove */</p>
<hr />
<div>'''NOTE: TU's are currently working through the list'''. You can still add packages but please check the whole page first.<br />
<br />
<br />
The AUR has a large number of obsolete packages which could use cleaning up. Examples of packages that may be cleaned up are:<br />
*packages that have been renamed or replaced<br />
*old and unmaintained developmental (cvs/svn/etc) packages<br />
<br />
Post suggestions of packages on this pages. Trusted Users will get together and go though the list in a couple of weeks and confirm which packages should be removed. '''Please DO NOT REMOVE suggestions from the wiki page but add a comment on why it should be kept instead.''' TUs will not delete any useful package.<br />
<br />
==Package List==<br />
'''Add new packages here''' - check for the package in the sorted lists below before adding<br />
<br />
* [http://aur.archlinux.org/packages.php?ID=13014 advi] - seems to be unmaintainable for the following reasons<br />
** The newest version 1.7.3 needs camlimages 3.0.0, which cannot be found on the net<br />
** camlimages' cvs-sources do not compile<br />
** package advi 1.6.0 has a patchfile of 102k size<br />
* [http://aur.archlinux.org/packages.php?ID=9026 audacious-docklet] - Doesnt work with latest audacious, not needed anymore either<br />
* [http://aur.archlinux.org/packages.php?ID=1731 ecamegapedal] - Do not to compile.<br />
* [http://aur.archlinux.org/packages.php?ID=4493 eclipse-kde] - Dead<br />
* [http://aur.archlinux.org/packages.php?ID=3698 galeon] - doesn't compile (not even the latest version)<br />
* [http://aur.archlinux.org/packages.php?ID=6069 gnuserv] - Deprecated in emacs-22+<br />
* [http://aur.archlinux.org/packages.php?ID=5207 gshare] - The package didn't function for me with the latest gnome. Furthermore it looks like this project is dead (website is down, source is no longer available)<br />
* [http://aur.archlinux.org/packages.php?ID=3689 ii-hg] - outdated, probably discontinued as the project website isn't available anymore (moved maybe?)<br />
** The project website is available at http://www.suckless.org/wiki/tools/irc/irc_it, so it's not dead. It only needs some changes to work again. --[[User:CuleX|CuleX]]<br />
* [http://aur.archlinux.org/packages.php?ID=7884 jfduke3d] - Is not updated by his author anymore, [http://aur.archlinux.org/packages.php?ID=15513 eduke32] was made to remplace it<br />
* [http://aur.archlinux.org/packages.php?ID=7037 kanola] - probably dead project, didn't went past the 0.0.1 release since 2006<br />
* [http://aur.archlinux.org/packages.php?ID=3429 lam 7.1.3-1] - Doesn't compile and is orphaned. The successor openmpi works.<br />
* [http://aur.archlinux.org/packages.php?ID=16889 libqglviewer-latest] - the same package as [http://aur.archlinux.org/packages.php?ID=7801 libqglviewer]<br />
* [http://aur.archlinux.org/packages.php?ID=14220 linuxdcpp-cvs] - Old, orphaned CVS version of a package in community<br />
* [http://aur.archlinux.org/packages.php?ID=7264 mencode] - outdated, tells aur is its homepage<br />
** The package is to install a perl script included in the AUR tarball so it doesn't really have a home page. So it could be kept if the script can still be useful or, at least, the script could be moved to the wiki if there is a page for scripts. --[[User:Snowman|Snowman]]<br />
* [http://aur.archlinux.org/packages.php?ID=5408 mlame] - just a small bash script, no project page, could be moved to the wiki maybe<br />
* [http://aur.archlinux.org/packages.php?ID=11581 mouseemu] - Project not updated since 2006; xautomation also allows mouse emulation.<br />
* [http://aur.archlinux.org/packages.php?ID=11498 mpd-pausemode] - "Website" is orig. contributor's email addr.; orphaned by this contributor, so presumably no longer developed.<br />
* [http://aur.archlinux.org/packages.php?ID=15401 org] - Out of date; also, included in Emacs 22+<br />
* [http://aur.archlinux.org/packages.php?ID=10514 rt61-cvs] - This driver is included in linus's tree and is therefore obsolete<br />
* [http://aur.archlinux.org/packages.php?ID=494 sonic-rainbow] - dead project, does not compile --[[User:Snowman|Snowman]]<br />
* [http://aur.archlinux.org/packages.php?ID=2612 stepmania-bin] - orphan, replaced by [http://aur.archlinux.org/packages.php?ID=5453 stepmania]<br />
* [http://aur.archlinux.org/packages.php?ID=15678 swt-devel] - I only created it to compile tuxguitar against it, but that's not needed. And it seems nobody is using it. <br />
* [http://aur.archlinux.org/packages.php?ID=3947 viki-svn] - old, pkgbuild is broken<br />
* [http://aur.archlinux.org/packages.php?ID=12067 pidgimpd-svn] - This package is orphaned and it doesn't build. There is mpd support in musictracker.<br />
* [http://aur.archlinux.org/packages.php?ID=6686 sizzle] - No upstream maintenance, does not compile.<br />
<br />
==TU Working Area==<br />
<br />
'''For editing by TUs only!''' The wiki has a history so do not think you can get away with ignoring this... --[[User:Allan|Allan]]<br />
<br />
===Packages to Remove===<br />
* [http://aur.archlinux.org/packages.php?ID=16166 jacman] - Jacman doesn't work correctly with pacman3. --[[User:Partition|Partition]]<br />
* [http://aur.archlinux.org/packages.php?ID=14992 slim-theme-darch] - in archlinux-themes-slim --[[User:Allan|Allan]]<br />
In community:<br />
* [http://aur.archlinux.org/packages.php?ID=12993 ion-modules] - ion3 is not part of official repos anymore, move to AUR --[[User:Allan|Allan]]<br />
* [http://aur.archlinux.org/packages.php?ID=9102 lmctl] - replaced by lomoco --[[User:Allan|Allan]]<br />
* [http://aur.archlinux.org/packages.php?ID=8958 wildfire] - Replaced by openfire. --[[User:pressh|pressh]]<br />
<br />
===Packages to Keep===<br />
* [http://aur.archlinux.org/packages.php?ID=14946 mplayer-w32codecs] - not duplicate package as has more codecs than the "codecs" package.<br />
** Should rename to "codecs-extra" and not provide same files as codecs package --[[User:Allan|Allan]]<br />
<br />
==Remove from Filesystem==<br />
<br />
This is a list of files on the AUR filesystem that have been created when poorly formed packages were uploaded. This is a secondary consideration.<br />
<br />
There are also directories in /packages/ for which the package no longer exists. These probably need to be removed as well. Examples are 4c, 1394commander and 8kingdoms. Also, all the packages that moved to community ALSO still exist here; for example 915resolution.<br />
<br />
<pre><br />
/packages/0verkill-0.16.tar.gz/<br />
/packages/0verkill-0.16/<br />
/packages/2007.02.17-2/<br />
/packages/abakus-0.91-1/<br />
/packages/abakus-0.91.tar.gz/<br />
/packages/abakus-0.91/<br />
/packages/akgregator/<br />
/packages/akregator/<br />
/packages/akregator1.0.2/<br />
/packages/akregator_1.0.2/<br />
/packages/amsn-0.97ec1/<br />
/packages/amsn-0.97rc1/<br />
/packages/amsn-097rc1-1/<br />
/packages/amsn-097rc1/<br />
/packages/amsn-cvs/<br />
/packages/amsn-svn_update/<br />
/packages/amsn096/<br />
/packages/amsn096rc1/<br />
/packages/bashstyle-5.0<br />
/packages/bashstyle-5.0rc1.tar.gz/<br />
/packages/bashstyle-5.0rc1.tar.gz1/<br />
/packages/bashstyle-5.0rc1/<br />
/packages/bashstyle.tar.gz/<br />
/packages/bashstyle-ng/<br />
/packages/bashstyle1/<br />
/packages/braero-svn<br />
/packages/braser-cvs/<br />
/packages/brasero-cvs/<br />
/packages/brasero.svn/<br />
/packages/brlcad-cvs/<br />
/packages/ccd2iso-0.3/<br />
/packages/cdcollect-0.6.0/<br />
/packages/centerim-4.22.2/<br />
/packages/centerim/<br />
/packages/ploticus-test/<br />
/packages/test-louipc/<br />
/packages/test/<br />
/packages/test_pkg/<br />
/packages/yacas-1.1.17-2/<br />
/packages/yacas-1.2.2/<br />
/packages/yacas-1.17-2/<br />
/packages/yacas-new/<br />
/packages/yacasnew/<br />
/packages/zzztest/<br />
/packages/zzzztest/<br />
</pre><br />
<br />
==Remove from Filesystem (AUR Bugs)==<br />
<br />
This is a list of files that need to be removed due to AUR bugs as they hinder proper submission and maintenance of packages.<br />
<br />
AUR Bugs<br />
* FS#8672 - http://bugs.archlinux.org/task/8672<br />
<br />
<pre><br />
/packages/advanceutils<br />
/packages/isight-firmware-tools<br />
/packages/mlt-svn<br />
/packages/perl-devel-stacktrace<br />
/packages/psi-qt4<br />
/packages/xcursor-industrial<br />
/packages/zaptel<br />
</pre><br />
<br />
/packages/lib32-dbus is now in community - Allan</div>Drooghttps://wiki.archlinux.org/index.php?title=AUR_Cleanup_Day/2010&diff=42498AUR Cleanup Day/20102008-06-03T03:54:08Z<p>Droog: /* TU Working Area */</p>
<hr />
<div>'''NOTE: TU's are currently working through the list'''. You can still add packages but please check the whole page first.<br />
<br />
<br />
The AUR has a large number of obsolete packages which could use cleaning up. Examples of packages that may be cleaned up are:<br />
*packages that have been renamed or replaced<br />
*old and unmaintained developmental (cvs/svn/etc) packages<br />
<br />
Post suggestions of packages on this pages. Trusted Users will get together and go though the list in a couple of weeks and confirm which packages should be removed. '''Please DO NOT REMOVE suggestions from the wiki page but add a comment on why it should be kept instead.''' TUs will not delete any useful package.<br />
<br />
==Package List==<br />
'''Add new packages here''' - check for the package in the sorted lists below before adding<br />
<br />
* [http://aur.archlinux.org/packages.php?ID=13014 advi] - seems to be unmaintainable for the following reasons<br />
** The newest version 1.7.3 needs camlimages 3.0.0, which cannot be found on the net<br />
** camlimages' cvs-sources do not compile<br />
** package advi 1.6.0 has a patchfile of 102k size<br />
* [http://aur.archlinux.org/packages.php?ID=9026 audacious-docklet] - Doesnt work with latest audacious, not needed anymore either<br />
* [http://aur.archlinux.org/packages.php?ID=1731 ecamegapedal] - Do not to compile.<br />
* [http://aur.archlinux.org/packages.php?ID=4493 eclipse-kde] - Dead<br />
* [http://aur.archlinux.org/packages.php?ID=3698 galeon] - doesn't compile (not even the latest version)<br />
* [http://aur.archlinux.org/packages.php?ID=6069 gnuserv] - Deprecated in emacs-22+<br />
* [http://aur.archlinux.org/packages.php?ID=5207 gshare] - The package didn't function for me with the latest gnome. Furthermore it looks like this project is dead (website is down, source is no longer available)<br />
* [http://aur.archlinux.org/packages.php?ID=3689 ii-hg] - outdated, probably discontinued as the project website isn't available anymore (moved maybe?)<br />
** The project website is available at http://www.suckless.org/wiki/tools/irc/irc_it, so it's not dead. It only needs some changes to work again. --[[User:CuleX|CuleX]]<br />
* [http://aur.archlinux.org/packages.php?ID=7884 jfduke3d] - Is not updated by his author anymore, [http://aur.archlinux.org/packages.php?ID=15513 eduke32] was made to remplace it<br />
* [http://aur.archlinux.org/packages.php?ID=7037 kanola] - probably dead project, didn't went past the 0.0.1 release since 2006<br />
* [http://aur.archlinux.org/packages.php?ID=3429 lam 7.1.3-1] - Doesn't compile and is orphaned. The successor openmpi works.<br />
* [http://aur.archlinux.org/packages.php?ID=16889 libqglviewer-latest] - the same package as [http://aur.archlinux.org/packages.php?ID=7801 libqglviewer]<br />
* [http://aur.archlinux.org/packages.php?ID=14220 linuxdcpp-cvs] - Old, orphaned CVS version of a package in community<br />
* [http://aur.archlinux.org/packages.php?ID=7264 mencode] - outdated, tells aur is its homepage<br />
** The package is to install a perl script included in the AUR tarball so it doesn't really have a home page. So it could be kept if the script can still be useful or, at least, the script could be moved to the wiki if there is a page for scripts. --[[User:Snowman|Snowman]]<br />
* [http://aur.archlinux.org/packages.php?ID=5408 mlame] - just a small bash script, no project page, could be moved to the wiki maybe<br />
* [http://aur.archlinux.org/packages.php?ID=11581 mouseemu] - Project not updated since 2006; xautomation also allows mouse emulation.<br />
* [http://aur.archlinux.org/packages.php?ID=11498 mpd-pausemode] - "Website" is orig. contributor's email addr.; orphaned by this contributor, so presumably no longer developed.<br />
* [http://aur.archlinux.org/packages.php?ID=15401 org] - Out of date; also, included in Emacs 22+<br />
* [http://aur.archlinux.org/packages.php?ID=10514 rt61-cvs] - This driver is included in linus's tree and is therefore obsolete<br />
* [http://aur.archlinux.org/packages.php?ID=494 sonic-rainbow] - dead project, does not compile --[[User:Snowman|Snowman]]<br />
* [http://aur.archlinux.org/packages.php?ID=2612 stepmania-bin] - orphan, replaced by [http://aur.archlinux.org/packages.php?ID=5453 stepmania]<br />
* [http://aur.archlinux.org/packages.php?ID=15678 swt-devel] - I only created it to compile tuxguitar against it, but that's not needed. And it seems nobody is using it. <br />
* [http://aur.archlinux.org/packages.php?ID=3947 viki-svn] - old, pkgbuild is broken<br />
* [http://aur.archlinux.org/packages.php?ID=12067 pidgimpd-svn] - This package is orphaned and it doesn't build. There is mpd support in musictracker.<br />
* [http://aur.archlinux.org/packages.php?ID=6686 sizzle] - No upstream maintenance, does not compile.<br />
<br />
==TU Working Area==<br />
<br />
'''For editing by TUs only!''' The wiki has a history so do not think you can get away with ignoring this... --[[User:Allan|Allan]]<br />
<br />
===Packages to Remove===<br />
* [http://aur.archlinux.org/packages.php?ID=1926 fvwm-trans] last updated over 2 years ago and replaced with fvwm-patched in AUR<br />
* [http://aur.archlinux.org/packages.php?ID=16166 jacman] - Jacman doesn't work correctly with pacman3. --[[User:Partition|Partition]]<br />
* [http://aur.archlinux.org/packages.php?ID=14992 slim-theme-darch] - in archlinux-themes-slim --[[User:Allan|Allan]]<br />
In community:<br />
* [http://aur.archlinux.org/packages.php?ID=12993 ion-modules] - ion3 is not part of official repos anymore, move to AUR --[[User:Allan|Allan]]<br />
* [http://aur.archlinux.org/packages.php?ID=9102 lmctl] - replaced by lomoco --[[User:Allan|Allan]]<br />
* [http://aur.archlinux.org/packages.php?ID=8958 wildfire] - Replaced by openfire. --[[User:pressh|pressh]]<br />
<br />
===Packages to Keep===<br />
* [http://aur.archlinux.org/packages.php?ID=14946 mplayer-w32codecs] - not duplicate package as has more codecs than the "codecs" package.<br />
** Should rename to "codecs-extra" and not provide same files as codecs package --[[User:Allan|Allan]]<br />
<br />
==Remove from Filesystem==<br />
<br />
This is a list of files on the AUR filesystem that have been created when poorly formed packages were uploaded. This is a secondary consideration.<br />
<br />
There are also directories in /packages/ for which the package no longer exists. These probably need to be removed as well. Examples are 4c, 1394commander and 8kingdoms. Also, all the packages that moved to community ALSO still exist here; for example 915resolution.<br />
<br />
<pre><br />
/packages/0verkill-0.16.tar.gz/<br />
/packages/0verkill-0.16/<br />
/packages/2007.02.17-2/<br />
/packages/abakus-0.91-1/<br />
/packages/abakus-0.91.tar.gz/<br />
/packages/abakus-0.91/<br />
/packages/akgregator/<br />
/packages/akregator/<br />
/packages/akregator1.0.2/<br />
/packages/akregator_1.0.2/<br />
/packages/amsn-0.97ec1/<br />
/packages/amsn-0.97rc1/<br />
/packages/amsn-097rc1-1/<br />
/packages/amsn-097rc1/<br />
/packages/amsn-cvs/<br />
/packages/amsn-svn_update/<br />
/packages/amsn096/<br />
/packages/amsn096rc1/<br />
/packages/bashstyle-5.0<br />
/packages/bashstyle-5.0rc1.tar.gz/<br />
/packages/bashstyle-5.0rc1.tar.gz1/<br />
/packages/bashstyle-5.0rc1/<br />
/packages/bashstyle.tar.gz/<br />
/packages/bashstyle-ng/<br />
/packages/bashstyle1/<br />
/packages/braero-svn<br />
/packages/braser-cvs/<br />
/packages/brasero-cvs/<br />
/packages/brasero.svn/<br />
/packages/brlcad-cvs/<br />
/packages/ccd2iso-0.3/<br />
/packages/cdcollect-0.6.0/<br />
/packages/centerim-4.22.2/<br />
/packages/centerim/<br />
/packages/ploticus-test/<br />
/packages/test-louipc/<br />
/packages/test/<br />
/packages/test_pkg/<br />
/packages/yacas-1.1.17-2/<br />
/packages/yacas-1.2.2/<br />
/packages/yacas-1.17-2/<br />
/packages/yacas-new/<br />
/packages/yacasnew/<br />
/packages/zzztest/<br />
/packages/zzzztest/<br />
</pre><br />
<br />
==Remove from Filesystem (AUR Bugs)==<br />
<br />
This is a list of files that need to be removed due to AUR bugs as they hinder proper submission and maintenance of packages.<br />
<br />
AUR Bugs<br />
* FS#8672 - http://bugs.archlinux.org/task/8672<br />
<br />
<pre><br />
/packages/advanceutils<br />
/packages/isight-firmware-tools<br />
/packages/mlt-svn<br />
/packages/perl-devel-stacktrace<br />
/packages/psi-qt4<br />
/packages/xcursor-industrial<br />
/packages/zaptel<br />
</pre><br />
<br />
/packages/lib32-dbus is now in community - Allan</div>Drooghttps://wiki.archlinux.org/index.php?title=Xorg&diff=41862Xorg2008-05-24T19:33:49Z<p>Droog: /* Display Size/DPI */</p>
<hr />
<div>[[Category:X Server (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|Dansk|Xorg (Dansk)}}<br />
{{i18n_entry|English|Xorg}}<br />
{{i18n_entry|Español|Configurando Xorg (Español)}}<br />
{{i18n_entry|Polski|Xorg_(Polski)}}<br />
{{i18n_entry|Русский|Xorg (Русский)}}<br />
{{i18n_entry|Česky|Xorg (Česky)}}<br />
{{i18n_entry|Italiano|Xorg (Italiano)}}<br />
{{i18n_entry|简体中文|Xorg (简体中文)}}<br />
{{i18n_links_end}}<br />
<br />
== Introduction ==<br />
<br />
'''Xorg''' is the public, open-source implementation of the X11 X Window System. (See the [http://en.wikipedia.org/wiki/X.Org_Server X.org Wikipedia Article] or [http://wiki.x.org/wiki/ X.org] for details.) Basically, if you want a GUI atop Arch, you will want xorg.<br />
<br />
==Installing Xorg==<br />
<br />
Before beginning, make sure you do the following:<br />
#Make sure that [[pacman]] is configured and refreshed.<br />
#If you are running another X server you can close it now. <code>ctrl+alt+backspace</code><br />
#Make a note about third-party drivers (e.g., nVidia or ATI drivers). <br />
<br />
First let us install the complete 'xorg' group:<br />
<br />
# pacman -S xorg-server<br />
<br />
The default 'vesa' driver is merely a fallback (not accelerated and doesn't support many resolutions), so you will need a proper video driver too. You can type this command to list all the video drivers available:<br />
<br />
# pacman -Ss xf86-video<br />
<br />
Look for the appropriate driver for your card and install it with pacman -S. To check your card, if hwd is installed, run 'hwd -s', or run 'lspci' (look for 'VGA compatible controller'). <br />
<br />
If Xorg installed OK, it's time to make <code>xorg.conf</code><br />
<br />
==Configuring xorg==<br />
<br />
Before you can run xorg, you need to configure it so that it knows about your graphics card, monitor, mouse and keyboard. There are several methods of automating the process:<br />
<br />
===hwd===<br />
<br />
Perhaps the easiest way of getting Xorg up and running quickly is to use <tt>hwd</tt>, a tool written by users in the Arch Linux community. It's basically a hardware-detection tool that has multiple uses, one of which is setting up an X server. Fortunately, hwd is much more streamlined than <code>xorgconf</code> and doesn't require any input at all.<br />
<br />
First, install the <tt>hwd</tt> package:<br />
# pacman -S hwd<br />
<br />
Now simply run the following command as root to generate a default <code>xorg.conf</code> file:<br />
# hwd -xa<br />
<br />
This will overwrite any existing /etc/X11/xorg.conf file with a practical set of defaults, based on what <tt>hwd</tt> detected for your hardware.<br />
<br />
Alternatively, you can generate a sample Xorg config (/etc/X11/xorg.conf.hwd) without overwriting your existing settings. To do so, run <tt>hwd</tt> with the '''-x''' flag instead:<br />
# hwd -x<br />
<br />
Sample result:<br />
/etc/X11/xorg.conf.ati<br />
/etc/X11/xorg.conf.vesa<br />
<br />
Your sample file(s) ready, rename 'xorg.conf'.<br />
If unsure first try 'vesa' (default).<br />
<br />
To use the sample config(s), you must manually rename it. Sample:<br />
# mv /etc/X11/xorg.conf.vesa /etc/X11/xorg.conf<br />
<br />
AD: In my experience hwd creates XF86Config-4 file and if there is not xorg.conf present Xorg uses it automatically.<br />
<br />
===xorgconfig===<br />
<br />
To start up <tt>xorgconfig</tt>:<br />
<br />
# xorgconfig<br />
<br />
or<br />
<br />
# xorgcfg -textmode<br />
<br />
These will generate a new <tt>xorg.conf</tt>.<br />
<br />
Answer the questions, and the program will make the file for you.<br />
This program is not really good but it's a start, and you can fill in special stuff manually afterwards.<br />
<br />
===Xorg -configure===<br />
You can also use<br />
# Xorg -configure<br />
or<br />
# X -configure<br />
<br />
===nvidia-xconfig===<br />
nVidia users can also use<br />
# nvidia-xconfig<br />
when they have official nvidia drivers [[NVIDIA|installed]].<br />
<br />
Comment the line<br />
<br />
Load "type1"<br />
<br />
in the Module section since recent versions of xorg-server does not include the type1 font module (completely replaced by freetype).<br />
<br />
==Editing xorg.conf==<br />
<br />
You may wish to edit the config after it's been generated. To open in your favourite text-editor, such as Vim (you need root privileges):<br />
<br />
# vim /etc/X11/xorg.conf<br />
<br />
or use Xorg Configuration toolkit:<br />
<br />
# xorgcfg -textmode<br />
<br />
If you want to set up mouse wheel support, see [[Get All Mouse Buttons Working]].<br />
<br />
===Monitor Settings===<br />
<br />
Depending on your hardware, Xorg may fail to detect your monitor capabilities correctly, or you may simply wish to use a lower resolution than your monitor is capable of. You might want to look up the following values in your monitor's manual before setting them.<br />
The following settings are specified in the Monitor section:<br />
<br />
====Horizontal Sync====<br />
<br />
HorizSync 28-64<br />
<br />
====Refresh Rate====<br />
<br />
VertRefresh 60<br />
<br />
The following are specified in the Screen section:<br />
<br />
====Colour Depth====<br />
<br />
Depth 24<br />
<br />
====Resolution====<br />
<br />
Modes "1280x1024" "1024x768" "800x600"<br />
<br />
=== Keyboard Settings ===<br />
<br />
Xorg may fail to detect your keyboard correctly. This might give problems with your keyboard layout or keyboard model not being set correctly.<br />
<br />
To see a full list of keyboard models, layouts, variants and options, open.<br />
<br />
<br />
/usr/share/X11/xkb/rules/xorg.lst<br />
<br />
==== Keyboard Layout ====<br />
<br />
To change the keyboard layout, use the XkbLayout option in the keyboard InputDevice section. For example, if you have a keyboard with English layout:<br />
<br />
Option "XkbLayout" "gb"<br />
<br />
To be able to easily switch keyboard layouts, for example between a US and a Swedish layout use this instead:<br />
<br />
Option "XkbLayout" "us, se"<br />
Option "XkbOptions" "grp:caps_toggle"<br />
<br />
This makes your Caps Lock key switch between the different layouts. This is mainly useful if you run don't run a Desktop Environment which takes care of keyboard layouts for you.<br />
<br />
==== Keyboard Model ====<br />
<br />
To change the keyboard model, use the XkbModel option in the keyboard <br />
InputDevice section. For example, if you have a Microsoft Wireless Multimedia Keyboard:<br />
<br />
Option "XkbModel" "microsoftmult"<br />
<br />
===Display Size/DPI===<br />
<br />
In order to get correct sizing for fonts the display size must be set for your desired DPI. In the section <code>"Monitor"</code> put in your display size in mm:<br />
<br />
Section "Monitor"<br />
...<br />
DisplaySize 336 252 # 96 DPI @ 1280x960<br />
...<br />
EndSection<br />
<br />
<br />
The formula for calculating the DisplaySize values is Width x 25.4 / DPI and Height x 25.4 / DPI. If you're running Xorg with a resolution of 1024x768 and want a DPI of 96, use 1024 x 25.4 / 96 and 768 x 25.4 / 96. Round numbers down.<br />
<br />
# calc: (x|y)pixels * 25.4 / dpi<br />
# DisplaySize 168 126 # 96 DPI @ 640x480<br />
# DisplaySize 210 157 # 96 DPI @ 800x600<br />
# DisplaySize 269 201 # 96 DPI @ 1024x768<br />
# DisplaySize 302 227 # 96 DPI @ 1152x864<br />
# DisplaySize 336 252 # 96 DPI @ 1280x960<br />
# DisplaySize 336 210 # 96 DPI @ 1280x800 (non 4:3 aspect)<br />
# DisplaySize 339 271 # 96 DPI @ 1280x1024 (non 4:3 aspect)<br />
# DisplaySize 370 277 # 96 DPI @ 1400x1050<br />
# DisplaySize 420 315 # 96 DPI @ 1600x1200<br />
# DisplaySize 444 277 # 96 DPI @ 1680x1050<br />
# DisplaySize 506 315 # 96 DPI @ 1920x1200 (non 4:3 aspect)<br />
<br />
<br />
For nVidia drivers you may have to disable automatic detection of DPI to set it manually. There is also an easier way to set DPI on these cards. Either or both of the following lines can be set in the device section for your nVidia card.<br />
<br />
Option "UseEdidDpi" "false"<br />
Option "DPI" "96 x 96"<br />
<br />
<br />
Results can be checked by issuing the following command, which should return 96x96 dots per inch if you set DPI @ 96.<br />
<br />
$ xdpyinfo | grep -B1 dot<br />
<br />
===Proprietary Drivers===<br />
<br />
If you wish to use third-party graphics drivers, do check first that the X server runs OK first. Xorg should run smoothly without official drivers, which are typically needed only for advanced features such as 3D-accelerated rendering for games, dual-screen setups, and TV-out. Refer to the [[NVIDIA]] and [[ATI]] wikis for help with driver installation.<br />
<br />
===Fonts===<br />
<br />
There some tips for setting up fonts in [[Xorg Font Configuration]].<br />
<br />
=== Sample Xorg.conf Files ===<br />
Anyone who has an Xorg.conf file written up that works, go ahead and post a link to it here for others to look at! Please don't inline the entire conf file; upload it somewhere else and link. Thanks!<br />
* Shadowhand (nv and nvidia drivers): http://people.os-zen.net/shadowhand/configs/xorg.conf<br />
* Cerebral (fglrx and radeon drivers): http://www.student.cs.uwaterloo.ca/~tjwillar/configs/xorg.conf<br />
* raskolnikov (via unichrome and synaptics drivers): http://athanatos.free.fr/Arch/xorg.conf<br />
* Leigh (Three independent screens - Three nvidia cards): http://files.myopera.com/allisonleigh/linuxbackup/xorg.conf<br />
* Mr.Elendig (nvidia with composite and "stuff") http://arch.har-ikkje.net/stuff/xorg.conf<br />
<br />
==Running Xorg==<br />
<br />
This is done simply by typing:<br />
<br />
$ startx<br />
<br />
The default X environment is rather bare, and you will typically seek to install window managers or desktop environments to supplement X. <br />
<br />
To test the config file you have created:<br />
<br />
$ X -config ''<your config file>''<br />
<br />
If a problem occurs, then view the log at <tt>/var/log/Xorg.0.log</tt>. Be on the lookout for any lines beginning with ''(EE)'' which represent errors, and also ''(WW)'' which are warnings that could indicate other issues.<br />
<br />
'''*Please Note*'''<br />
Using startx requires a ''~/.xinitrc'' file, so that X knows what to run when it starts. Your best option is to copy ''/etc/skel/.xinitrc'' to your home directory and edit it. Comment out the 'exec' lines you don't want, and add or uncomment one for the WM you want to use. If you are using GNOME it is best to start GNOME through gdm to avoid HAL permission problems.<br />
<br />
In addition, you can also install twm and xterm (via pacman), which will be used as a fallback if ~/.xinitrc does not exist (as stated in /etc/X11/xinit/xinitrc).<br />
<br />
==X startup (/usr/bin/startx) tweaking==<br />
For X's option reference see<br />
<br />
$ man Xserver<br />
<br />
The following options have to be appended to the variable "defaultserverargs" in the /usr/bin/startx file.<br />
<br />
prevent X from listening on tcp:<br />
-nolisten tcp<br />
getting rid of the gray weave pattern while X is starting and let X set a black root window:<br><br />
-br<br />
enable deferred glyph loading for 16 bit fonts:<br />
-deferglyphs 16<br />
<br />
Note: If you start X with kdm, the startx script does not seem to be executed. X options must be appended to the variable "ServerCmd" in the /opt/kde/share/config/kdm/kdmrc file. By default kdm options are<br />
<br />
ServerCmd=/usr/bin/X -br -nolisten tcp<br />
<br />
== Changes with modular Xorg ==<br />
<br />
=== Most Common Packages ===<br />
<br />
Make sure you install drivers for mouse, keyboard and videocard. For mouse and keyboard, '''xf86-input-keyboard''' and '''xf86-input-mouse''' should get installed. Other '''xf86-input-*''' packages are available for different input devices.<br />
<br />
For the videocard, find out which driver is required and install the right '''xf86-video-*''' package. ATI and Nvidia users may wish to install the non-free drivers for their hardware instead ([[NVIDIA]], [[ATI]]).<br />
<br />
To install all drivers in one run, the '''xorg-input-drivers''' and '''xorg-video-drivers''' are available.<br />
<br />
=== OpenGL 3D Acceleration ===<br />
<br />
X.Org 7.0 on Arch Linux uses a modular design for mesa, the OpenGL rendering system. Several implementations are available:<br />
* libgl-dri: Open-source DRI OpenGL implementation. Falls back to software rendering when no DRI driver is installed<br />
* some other driver providing libGL (ati, nvidia)<br />
<br />
When pacman installs an application that needs mesa, it will install one of these packages. To be sure about the right library for your setup, install the library you want prior to installing Xorg. Installing the right package afterwards is also possible, though this gives some dependency errors sometimes, which can be ignored with the -d switch.<br />
<br />
=== Glxgears and Glxinfo ===<br />
<br />
These apps are included in the mesa package.<br />
<br />
=== Changed paths (and configuration) ===<br />
<br />
'''See this entry for additional upgrade info:''' http://www.archlinux.org/blog/2006/01/02/how-to-upgrade-xorg/<br />
<br />
Modular X.Org 7 installs everything in <code>/usr</code>, where the older versions installed in <code>/usr/X11R6</code>. Several configuration files need updates:<br />
* ''/etc/X11/xorg.conf''<br />
** Fontpaths live in /usr/share/fonts now<br />
** RGB database is in /usr/share/X11/rgb<br />
** module path is /usr/lib/xorg/modules<br />
<br />
Also note that some X configuration tools might stop working. The easiest way to configure X.org is by installing the correct driver packages and running ''Xorg -configure'', which results in a <code>/root/xorg.conf.new</code> which only needs modification in the resolutions, mouse configuration and keyboard layouts.<br />
<br />
Some packages have hard-coded references to <code>/usr/X11R6</code>. These packages need fixing. In the meantime, look what packages install files in <code>/usr/X11R6</code>, uninstall those, make a symlink from <code>/usr</code> to <code>/usr/X11R6</code> and reinstall the affected packages. Another option is to move the contents of <code>/usr/X11R6</code> to <code>/usr</code> and make the symlink.<br />
<br />
Or you can just add a second module path via <code/>ModulePath "/usr/X11R6/lib/modules"</code> <br />
This works e.g. for Nvidia 76.76<br />
<br />
== Troubleshooting ==<br />
<br />
=== Xorg "can't see" the resolutions your monitor supports ===<br />
I found myself in a situation where if i used one of my monitors(a gnr ts902) Xorg would only present me with the options 640x480 and 320x480 which ofcourse was less than i desired. After a lot of research i found through read-edid(in aur) that part of my EDID was corrupt and so i could only read my HorizSync with read-edid. This fortunately was enough and after adding the right Horisync line to the xorg.conf's Monitor section(didn't have to add VertRefresh...) I restarted X to see the right resolution :)<br />
<br />
note: I'm not sure:<br />
<br />
Option "ModeValidation" "NoEdidModes"<br />
Option "UseEdid" "false"<br />
<br />
in Device section in xorg config are needed aswell, to lazy now to test without them :)<br />
<br />
=== Keyboard Problems ===<br />
<br />
Auto-generated xorg.conf files may cause you problems. If you cannot get to tty1 by holding CTRL-ALT and pressing F1 or cannot get the £ sign for gb people, check to see if the following entries are in your /etc/X11/xorg.conf:<br />
<br />
Option "XkbLayout" "uk" #"uk" is not a real layout, look in /usr/share/X11/xkb/symbols/ for a list of real ones.<br />
Option "XkbRules" "xfree86" #this should be "xorg"<br />
Option "XkbVariant" "nodeadkeys" #This line is also known to cause the problems described, try commenting it out.<br />
<br />
To switch between layouts with Alt+Shift:<br />
Option "XkbOptions" "grp:alt_shift_toggle,grp_led:scroll"<br />
<br />
===A Quick Fix for the Bitstream-Vera Conflict===<br />
If you see a message that ttf-bitstream-vera conflicts with xorg:<br />
#Exit the pacman session by answering no.<br />
#Run <code>pacman -Rd xorg</code><br />
#Run <code>pacman -Syu</code><br />
#Run <code>pacman -S xorg</code><br />
#Update your paths in /etc/X11/xorg.conf<br />
<br />
===A Quick Fix for file conflicts in /usr/include===<br />
If you see messages about file conflicts in /usr/include/X11 and /usr/include/GL:<br />
#Run <code>rm /usr/include/{GL,X11}</code><br />
#Run <code>pacman -Su</code><br />
The symlinked directories removed by this operation are replaced by real directories in the new xorg package, causing these file conflicts to appear.<br />
<br />
=== libgl-dri conflicts ===<br />
<br />
If you get a message similar to:<br />
:: libgl-dri conflicts with nvidia-legacy. Remove nvidia-legacy? [Y/n]<br />
this is due to the multiple OpenGL implementations explained in the OpenGL section above - pacman is attempting to install libgl-dri to satisfy this dependency, but also trying to upgrade your existing video driver, and they conflict. To solve, try:<br />
<br />
* Updating your video driver before a full system update: <br />
# pacman -S nvidia-legacy<br />
# pacman -Syu<br />
<br />
Or, if that doesn't work,<br />
* Remove your existing video driver, do the update, then reinstall your driver:<br />
# pacman -Rd nvidia-legacy<br />
# pacman -Syu<br />
# pacman -S nvidia-legacy<br />
:: nvidia-legacy conflicts with libgl-dri. Remove libgl-dri? [Y/n] '''Y'''<br />
<br />
=== Mouse wheel not working ===<br />
The "Auto" protocol doesn't seem to work properly in Xorg 7 any more. In the InputDevice section for your mouse, change:<br />
Option "Protocol" "auto"<br />
to<br />
Option "Protocol" "IMPS/2"<br />
or<br />
Option "Protocol" "ExplorerPS/2"<br />
<br />
=== Extra mouse buttons not working ===<br />
USB Mice users should read [[Get_All_Mouse_Buttons_Working]].<br />
<br />
Intellimouse (ExplorerPS/2) users might find their scroll and side buttons aren't behaving as they used to. Previously xorg.conf needed:<br />
Option "Buttons" "7"<br />
Option "ZAxisMapping" "6 7"<br />
and users also had to run xmodmap to get the side buttons working with a command like:<br />
xmodmap -e "pointer = 1 2 3 6 7 4 5"<br />
Now xmodmap is no longer required. Instead, make xorg.conf look like this:<br />
Option "Buttons" "5"<br />
Option "ZAxisMapping" "4 5"<br />
Option "ButtonMapping" "1 2 3 6 7"<br />
and the side buttons on a 7-button Intellimouse will work like they used to, without needing to run xmodmap.<br />
<br />
===Keyboard problems===<br />
Some keyboard layouts have changed. I wondered why:<br />
* I wasn't able to Ctrl+Alt+Fx to switch to console<br />
* I wasn't able to use layouts<br />
The problem was that the ''sk_qwerty'' layout doesn't exist anymore. I had to replace<br />
Option "XkbLayout" "us,sk_qwerty"<br />
with<br />
Option "XkbLayout" "us,sk"<br />
Option "XkbVariant" ",qwerty"<br />
<br />
Another thing to look for if your keyboard isn't properly functioning is the XkbRules option:<br><br />
You'll need to change<br />
Option "XkbRules" "xfree86"<br />
to<br />
Option "XkbRules" "xorg"<br />
<br />
==== AltGR (Compose Key) not working properly ====<br />
<br />
If, after the update, you can't use the AltGr key as expected any more, try adding this to your keyboard section:<br />
Option "XkbOptions" "compose:ralt"<br />
<br />
This is not the correct way to activate the AltGr Key on a German keyboard (for example, to use the '|' and '@' keys on German keyboards).<br />
Just choose a valid keyboard variant for it to work again, for example (the example is for a German keyboard):<br />
Option "XkbLayout" "de"<br />
Option "XkbVariant" "nodeadkeys"<br />
<br />
The solutions above don't work on an Italian keyboard. To activate the AltGr key on an Italian keyboard make sure you have the following lines set up properly:<br />
Driver "kbd"<br />
Option "XkbRules" "xorg"<br />
Option "XkbVariant" ""<br />
<br />
This might still not be enough for a swedish keyboard. Try the above, but with lv3 instead of compose. (Thank you wyvern!)<br />
That is:<br />
Option "XkbLayout" "se"<br />
Option "XkbVariant" "nodeadkeys"<br />
Option "XkbOptions" "lv3:ralt_switch"<br />
<br />
==== Can't set qwerty layouts using the setxkbmap command ====<br />
<br />
After the update, there aren't qwerty layouts as for example sk_qwerty. If you want to switch your present keyboard layout to any qwerty keyboard layout use this command:<br />
$ setxkbmap NAME_OF_THE_LAYOUT qwerty<br />
e.g.: for sk_qwerty use:<br />
$ setxkbmap sk qwerty<br />
<br />
After the update, trying the above command I had this message "Error loading new keyboard description".<br />
I find out that the xserver doesn't have the rights to write, execute, read in the directory /var/tmp<br />
So give the permissions to that directory. Restart the xserver and you will have your deadkeys back!<br />
Don't believe? Try out the code e.g.: it layout<br />
$ setxkbmap -layout it<br />
<br />
==== Setup French Canadian (old ca_enhanced) layout ====<br />
<br />
With Xorg7, "ca_enhanced" is no more. You have to do a little trick to get the same layout that you are used to:<br />
Switch the old:<br />
Option "XkbLayout" "ca_enhanced"<br />
To:<br />
Option "XkbLayout" "ca"<br />
Option "XkbVariant" "fr"<br />
<br />
It will be similar with other layout, I presume. You can refer to Gentoo HowTo there: http://www.gentoo.org/proj/en/desktop/x/x11/modular-x-howto.xml<br />
<br />
<br />
<br />
=== Missing libraries ===<br />
* '''Help! I get an error message running my favourite app saying "libXsomething" doesn't exist!'''<br><br />
In most cases, all you need to do is take the name of the library (eg libXau.so.1), convert it all to lowercase, remove the extension, and pacman for it:<br />
# pacman -S libxau<br />
<br />
This will install the library you're missing, and all will be well again!<br />
<br />
=== Some packages fail to build and complain about missing X11 includes ===<br />
<br />
Just reinstall the packages xproto and libx11, even if they are already installed.<br />
<br />
=== Unable to load font '(null)' ===<br />
* '''Some programs don't work and say unable to load font `(null)'.'''<br><br />
These packages would like some extra fonts. Some programs only work with bitmap fonts.<br />
Two major packages with bitmap fonts are available, xorg-fonts-75dpi and xorg-fonts-100dpi. You don't need both; one should be enough. To find out which one would be better in your case, try this:<br />
<br />
$ xdpyinfo | grep resolution<br />
<br />
and grab what is closer to you (75 or 100 instead of XX)<br />
<br />
# pacman -S xorg-fonts-XXdpi<br />
<br />
=== KDE Taskbar/Desktop Icons Broken ===<br />
* '''KDE taskbar doesn't work and the desktop icons disappear'''<br><br />
Install the packages libxcomposite and libxss. It will be fine.<br />
<br />
# pacman -S libxcomposite libxss<br />
<br />
=== Updating from testing version to extra (missing files) ===<br />
<br />
If you've updated from Xorg 7 in testing to Xorg 7 in extra and are finding that many files seem to be missing (including startx, /usr/share/X11/rgb.txt, and others), you may have lost many files due to the xorg-clients package splitting from a single package into many smaller sub packages. <br><br />
<br />
You need to reinstall all the packages that are dependencies of xorg-clients:<br />
# pacman -S xorg-apps xorg-font-utils xorg-res-utils xorg-server-utils \<br />
xorg-twm xorg-utils xorg-xauth xorg-xdm xorg-xfs xorg-xfwp \<br />
xorg-xinit xorg-xkb-utils xorg-xsm<br />
<br />
This should fix the problem.<br />
<br />
=== Problem with MIME types in various desktop environments ===<br />
<br />
If you noticed icons missing and can't click-open files in desktop environments, add the following lines to /etc/profile or your preferred init script and reboot.<br />
XDG_DATA_DIRS=$XDG_DATA_DIRS:/usr/share<br />
export XDG_DATA_DIRS<br />
<br />
=== DRI stops working with Matrox cards ===<br />
<br />
If you use a Matrox card and DRI stops working after upgrading to xorg7, try adding the line<br />
Option "OldDmaInit" "On"<br />
to the Device section that references the video card in xorg.conf.<br />
<br />
=== Cannot start any clients under Xephyr ===<br />
<br />
The client connections are rejected by the X server's security mechanism, you can find a complete explanation and solution in [http://wiki.debian.org/XStrikeForce/FAQ#howtoxnest].<br />
<br />
=== Cannot start X clients as root using "su" ===<br />
<br />
If you're getting "Client is not authorized to connect to server", try adding the line <br />
<br />
session optional pam_xauth.so<br />
<br />
to the file /etc/pam.d/su. <br />
pam_xauth will properly set environment variables and handle xauth keys.<br />
<br />
== Links ==<br />
See also:<br />
<br />
* [[Enabling a DM]]<br />
* [[Start X at boot]]<br />
* [[Xorg Font Configuration]]<br />
* Proprietary Video Drivers<br />
** [[ATI]]<br />
** [[NVIDIA]]<br />
* [[Desktop Environment]]<br />
** [[KDE]]<br />
** [[GNOME]]<br />
** [[Xfce]]<br />
** [[Enlightenment]]<br />
** [[Fluxbox]]<br />
** [[Openbox]]<br />
== External Links ==<br />
<br />
* [http://en.wikipedia.org/wiki/X.Org_Server X.org Wikipedia Article]<br />
* [http://wiki.x.org/wiki/ X.org]<br />
* [http://archux.com/page/installing-and-setting-xorg Installing and setting up Xorg]</div>Drooghttps://wiki.archlinux.org/index.php?title=Synchronization_and_backup_programs&diff=41807Synchronization and backup programs2008-05-23T19:21:46Z<p>Droog: /* Not rsync-based */</p>
<hr />
<div>[[Category:System (English)]]<br />
<br />
== Intro ==<br />
<br />
This wiki page contains information about various backup programs. It's a good idea to ''have'' regular backups of important data, most notably configuration files (<tt>/etc/*</tt>) and local pacman database (usually <tt>/var/lib/pacman/local/*</tt>).<br />
<br />
Few words to end the introduction: before you start trying programs out, try to think about your needs, e.g. consider the following questions:<br />
* What backup medium do I have available?<br />
** cd / dvd<br />
** remote server (With what access? Ssh? Can I install some software on it (necessary for e.g. rsync-based solutions)?)<br />
** external harddrive<br />
* How often do I plan to backup?<br />
** daily?<br />
** weekly?<br />
** less often?<br />
* What goodies do I expect from the backup solution?<br />
** compression? (what algorithms?)<br />
** encryption? (gpg or something more straightforward?)<br />
* Most importantly: how do I plan to restore backups if needed?<br />
<br />
All right, enough with this, let's see some options!<br />
<br />
== Incremental backups ==<br />
<br />
The point with these is that they remember what has been backed up during the last run, and back up only what has changed. Great if you back up often.<br />
<br />
=== Rsync-type backups ===<br />
<br />
The main characteristic of this type of backups is that they maintain a copy of the directory you want to keep a backup of, together with files which describe how did the contents change from the last backup (the so-called 'diffs'). Hence, they are inherently incremental, but usually they don't have compression/encryption. On the other hand, a working copy of everything is immediately available, no decompression/decryption needed. Finally the way it works makes it hard to burn backups to cd/dvd..<br />
<br />
===== command line based =====<br />
*[http://www.samba.org/rsync/ rsync] (in extra repo)<br />
*[http://www.nongnu.org/rdiff-backup/ rdiff-backup] (in community repo)<br />
*[http://www.rsnapshot.org rsnapshot] (in community repo)<br />
*[http://safekeep.sourceforge.net/ safekeep] (in AUR)<br />
* [http://www.scottlu.com/Content/Link-Backup.html Link-Backup] ([http://aur.archlinux.org/packages.php?ID=16929 AUR] may be patched with additional features) is similar to rsync based scripts, but does not use rsync<br />
** creates hard links between a series of backed-up trees (snapshots)<br />
** intelligently handles renames, moves, and duplicate files without additional storage or transfer<br />
** dstdir/.catalog is a catalog of all unique file instances; backup trees hard-link to the catalog<br />
** if a backup tree would be identical to the previous backup tree, it won't be needlessly created<br />
** transfer occurs over standard I/O locally or remotely between a client and server instance of this script<br />
** it copies itself to the server; it does not need to be installed on the server<br />
** remote backups rely on SSH<br />
** it resumes stopped backups; it can even be told to run for n minutes<br />
<br />
===== gui based =====<br />
*[http://www.flyback-project.org/ flyback] (in AUR)<br />
*[http://areca.sourceforge.net/ areca] (in AUR)<br />
*[https://wiki.ubuntu.com/TimeVault timevault] (in AUR)<br />
<br />
=== Not rsync-based ===<br />
<br />
They tend to create (big) archive files (like tar.bz2), and (of course) keep track of what's been archived. Now creating tar.bz2 or tar.gz archives has the advantage that you can extract the backups with just tar/bzip2/gzip, so you don't need to have the backup program around.<br />
<br />
* [[Backup with arch-backup|arch-backup]] (in community repo); [http://code.google.com/p/archlinux-stuff/ website]); trivial backup scripts with simple configuration:<br />
** compression method can be configured<br />
** possible to specify more directories to backup<br />
<br />
* [[Backup with hdup|hdup]] (in extra repo; [http://miek.nl/projects/hdup2/ website]; it's no longer developed, the author develops rdup now (below); but it's still a decent one):<br />
** creates tar.gz or tar.bz2 archives<br />
** supports gpg encryption<br />
** supports pushing over ssh<br />
** possible to specify more directories to backup<br />
<br />
* [http://miek.nl/projects/rdup rdup] (in [http://aur.archlinux.org/packages.php?ID=3728 AUR]) successor to hdup: the program *just determines* which files have changed since the last backup. It's completely up to you what do you want to do with that list. Some helper scripts are supplied, and with them it supports:<br />
** creating tar.gz archives '''or''' rsync-type copy<br />
** encryption (gpg and usual strong (eg. blowfish)), also applies for rsync-type copy<br />
** compression (also for rsync-type copy)<br />
<br />
* [http://www.nongnu.org/duplicity/ duplicity] (in community repo) is similar to hdup, supports tarring and encrypting. But:<br />
** the files backed up are "randomly" distributed between encrypted tar archives, which makes it harder to recover a particular file<br />
** you can backup just one directory at a time (while with hdup you can specify as many as you want in one backup profile)<br />
<br />
* [http://dar.linux.free.fr/ dar] (in community repo): <br />
** it uses its own format for archives (so you need to have it around when you want to restore)<br />
** supports splitting backups into more files by size<br />
** makefile-type config files, some custom scripts are available along with it<br />
** supports basic encryption (not gpg; but also strong, but you need to supply a password every time)<br />
** some gui tools for inspecting backups are also available (kdar, in [http://aur.archlinux.org/packages.php?ID=7586 AUR], but current dar needs beta version)<br />
** a script suitable for running from cron is [http://sarab.sourceforge.net/ sarab] (in [http://aur.archlinux.org/packages.php?ID=17044 AUR]): supports pretty much any backup scheme (Towers of Hanoi, Grandfather-Father-Son, etc..)<br />
<br />
== Not incremental backups ==<br />
<br />
* "Just copy everything into one big archive, but support writing to cd/dvd"-type: [http://www2.backup-manager.org/ backup-manager] (in [http://aur.archlinux.org/packages.php?ID=4351 AUR])<br />
<br />
== Versioning systems ==<br />
<br />
These are traditionally used for keeping track of software development; but if you want to have a simple way to manage your config files in one directory, it might be a good solution.<br />
<br />
* [http://www.selenic.com/mercurial/wiki/ mercurial] or [http://git.or.cz/ git] (both in extra repo)<br />
<br />
== Articles ==<br />
<br />
* [http://www.halfgaar.net/backing-up-unix Backing up Linux and other Unix(-like) systems]</div>Droog