https://wiki.archlinux.org/api.php?action=feedcontributions&user=Thajan&feedformat=atomArchWiki - User contributions [en]2024-03-28T15:17:48ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Talk:Installing_with_Software_RAID_or_LVM&diff=72647Talk:Installing with Software RAID or LVM2009-07-24T17:09:32Z<p>Thajan: /* The "mdadm" approach doesn't work well with raid0 */</p>
<hr />
<div>It was pointed out here:<br />
http://bbs.archlinux.org/viewtopic.php?p=121424#121495<br />
that software RAIDing your swap is not useful, and even slows performance.<br />
<br />
== bug in /etc/rc.sysinit?? ==<br />
<br />
I think there is a problem with /etc/rc.sysinit as it not loads the module for the device mapper. This is lvm specific. I just modified the file like this:<br />
<br />
if [ "$USELVM" = "yes" -o "$USELVM" = "YES" ]; then<br />
if [ -f /etc/lvmtab -a -x /sbin/vgchange ]; then<br />
# Kernel 2.4.x, LVM1 groups<br />
stat_busy "Activating LVM1 groups"<br />
/sbin/vgchange -a y<br />
stat_done<br />
elif [ -x /sbin/lvm -a -d /sys/block ]; then<br />
# Kernel 2.6.x, LVM2 groups<br />
stat_busy "Activating LVM2 groups"<br />
/sbin/modprobe dm_mod # <<-----Here is my change<br />
/sbin/lvm vgscan --ignorelockingfailure<br />
/sbin/lvm vgchange --ignorelockingfailure -a y<br />
stat_done<br />
fi<br />
fi<br />
<br />
i use the standard arch kernel<br />
<br />
== What about root on LVM ? ==<br />
I can't figure out how to make it...<br />
mkinitrd variable LVM_ROOT= what to set here??<br />
i am using grub and partition is like this:<br />
<br />
<div><br />
/dev/sda1 ext2 /boot<br />
/dev/sda2 LVM<br />
vg_name: linux<br />
lv_name: system / ext3<br />
home /home ext3<br />
swap none sw<br />
</div><br />
<br />
I've tryed <br />
LVM_ROOT=/dev/linux/system, <br />
grub kernel ... root=/dev/mapper/linux-system or root=/dev/linux/system<br />
i have USELVM=YES and in initrd LVM is enabled...<br />
<br />
lvm partitions was made with lvm2 - but i can activate and mount them manually<br />
where am i wrong??? - <br />
still blocked in bussybox with err - can't mount root - or so... or can't switch [don't remember] - <br />
lvm partitions are disabled - i have to enable and mount them manually<br />
<br />
--[[User:Suw|Suw]] 06:24, 8 April 2006 (EDT)<br />
<br />
== Lousy guide ==<br />
<br />
This has to be the worst, most crappy designed guide i have seen in all of my time with OpenSource, restructure this thing, and strip the old stuff for 7.1, it is VERY outdated. I must say that i would feel more confident just jumping head on out into raid on my own, than following this guid, get som structure in it.<br />
<br />
== Not completly lousy ==<br />
I did an install today and used this guide as a guideline, next to my common sense and other documentation on the mighty internet. Looking at this guide from an abstract point of view one will find that the principles are still the same. Going into basic details, you'll also get the gist. But several specifics are inaccurate and the overall structure could be improved. The guidance goes flaky once you get to the "Install and Configure Arch" part and beyond. Because it is so outdated.<br />
That's where I had to use outside sources and apply my own knowhow to get the system running.<br />
Perhaps i'll edit some bits here and there to patch it up a little. I have a general idea of what I did to get it right. And i'll enter a new GRUB example, because the kernel with the mdadm hook can detect arrays, or get it right by reading /etc/mdadm.conf.<br />
<br />
--[[User:Ultraman|Ultraman]] 2:47, 3 May 2008 (CEST)<br />
<br />
== rebuild from chroot to avoid getting dropped to ramfs after grub install ==<br />
<br />
for some reason the initcpio was not giving me my raid volumes after i tried to boot into the new system as instructed by the article. this problem went away after i used the install cd to boot, loaded raid1, raid5, and dm_mod modules manually, assembled arrays, activated the volume group, mounted the partitions, chrooted into the new system and rebuilt kernel26 (and therefore the initcpio). notably, i needed to mount /sys in addition to /proc and /dev prior to chrooting in order to get this to work. i only mention this because it seems like this article and several others omit /sys as a source of device files when instructing users to chroot. assuming that grub desires some access to devices when installing, i am wondering why only /proc and /dev are sufficient in the example outlined in the article but not in my case?<br />
<br />
NB- in the course of my troubleshooting i added definition of the raid1 array on which my / is located to the kernel line in menu.lst and i can say that this alone is insufficient to confer bootability to the installation as defined in the article. i have not tried my configuration without this (it shouldn't be necessary with the mdadm hook in mkinitcpio.conf)<br />
<br />
--[[User:Poopship21|Poopship21]] 21:24, 28 June 2009 (EDT)<br />
<br />
== The "mdadm" approach doesn't work well with raid0 ==<br />
<br />
Note that loading the "mdadm" hook doesn't always work with raid0. I've found out the hard way that this wiki just isn't complete.<br />
<br />
I had to load the "raid" hook instaid of the "mdadm" hook and had to load it ''before'' autodetect for it to work, like so:<br />
<div><br />
<br />
HOOKS="base udev raid autodetect pata scsi sata filesystems"<br />
<br />
</div><br />
I puzzled this together by combining the wiki together with a "how to set up RAID during installation" guide I found on the ARCH forums.<br />
<br />
I had to do this in a chroot and only really used the setup for the packages.<br />
<br />
--[[User:Thajan|Thajan]] 13:07, 24 July 2009 (EDT)</div>Thajanhttps://wiki.archlinux.org/index.php?title=Talk:Installing_with_Software_RAID_or_LVM&diff=72646Talk:Installing with Software RAID or LVM2009-07-24T17:08:32Z<p>Thajan: /* The "mdadm" approach doesn't work well with raid0 */</p>
<hr />
<div>It was pointed out here:<br />
http://bbs.archlinux.org/viewtopic.php?p=121424#121495<br />
that software RAIDing your swap is not useful, and even slows performance.<br />
<br />
== bug in /etc/rc.sysinit?? ==<br />
<br />
I think there is a problem with /etc/rc.sysinit as it not loads the module for the device mapper. This is lvm specific. I just modified the file like this:<br />
<br />
if [ "$USELVM" = "yes" -o "$USELVM" = "YES" ]; then<br />
if [ -f /etc/lvmtab -a -x /sbin/vgchange ]; then<br />
# Kernel 2.4.x, LVM1 groups<br />
stat_busy "Activating LVM1 groups"<br />
/sbin/vgchange -a y<br />
stat_done<br />
elif [ -x /sbin/lvm -a -d /sys/block ]; then<br />
# Kernel 2.6.x, LVM2 groups<br />
stat_busy "Activating LVM2 groups"<br />
/sbin/modprobe dm_mod # <<-----Here is my change<br />
/sbin/lvm vgscan --ignorelockingfailure<br />
/sbin/lvm vgchange --ignorelockingfailure -a y<br />
stat_done<br />
fi<br />
fi<br />
<br />
i use the standard arch kernel<br />
<br />
== What about root on LVM ? ==<br />
I can't figure out how to make it...<br />
mkinitrd variable LVM_ROOT= what to set here??<br />
i am using grub and partition is like this:<br />
<br />
<div><br />
/dev/sda1 ext2 /boot<br />
/dev/sda2 LVM<br />
vg_name: linux<br />
lv_name: system / ext3<br />
home /home ext3<br />
swap none sw<br />
</div><br />
<br />
I've tryed <br />
LVM_ROOT=/dev/linux/system, <br />
grub kernel ... root=/dev/mapper/linux-system or root=/dev/linux/system<br />
i have USELVM=YES and in initrd LVM is enabled...<br />
<br />
lvm partitions was made with lvm2 - but i can activate and mount them manually<br />
where am i wrong??? - <br />
still blocked in bussybox with err - can't mount root - or so... or can't switch [don't remember] - <br />
lvm partitions are disabled - i have to enable and mount them manually<br />
<br />
--[[User:Suw|Suw]] 06:24, 8 April 2006 (EDT)<br />
<br />
== Lousy guide ==<br />
<br />
This has to be the worst, most crappy designed guide i have seen in all of my time with OpenSource, restructure this thing, and strip the old stuff for 7.1, it is VERY outdated. I must say that i would feel more confident just jumping head on out into raid on my own, than following this guid, get som structure in it.<br />
<br />
== Not completly lousy ==<br />
I did an install today and used this guide as a guideline, next to my common sense and other documentation on the mighty internet. Looking at this guide from an abstract point of view one will find that the principles are still the same. Going into basic details, you'll also get the gist. But several specifics are inaccurate and the overall structure could be improved. The guidance goes flaky once you get to the "Install and Configure Arch" part and beyond. Because it is so outdated.<br />
That's where I had to use outside sources and apply my own knowhow to get the system running.<br />
Perhaps i'll edit some bits here and there to patch it up a little. I have a general idea of what I did to get it right. And i'll enter a new GRUB example, because the kernel with the mdadm hook can detect arrays, or get it right by reading /etc/mdadm.conf.<br />
<br />
--[[User:Ultraman|Ultraman]] 2:47, 3 May 2008 (CEST)<br />
<br />
== rebuild from chroot to avoid getting dropped to ramfs after grub install ==<br />
<br />
for some reason the initcpio was not giving me my raid volumes after i tried to boot into the new system as instructed by the article. this problem went away after i used the install cd to boot, loaded raid1, raid5, and dm_mod modules manually, assembled arrays, activated the volume group, mounted the partitions, chrooted into the new system and rebuilt kernel26 (and therefore the initcpio). notably, i needed to mount /sys in addition to /proc and /dev prior to chrooting in order to get this to work. i only mention this because it seems like this article and several others omit /sys as a source of device files when instructing users to chroot. assuming that grub desires some access to devices when installing, i am wondering why only /proc and /dev are sufficient in the example outlined in the article but not in my case?<br />
<br />
NB- in the course of my troubleshooting i added definition of the raid1 array on which my / is located to the kernel line in menu.lst and i can say that this alone is insufficient to confer bootability to the installation as defined in the article. i have not tried my configuration without this (it shouldn't be necessary with the mdadm hook in mkinitcpio.conf)<br />
<br />
--[[User:Poopship21|Poopship21]] 21:24, 28 June 2009 (EDT)<br />
<br />
== The "mdadm" approach doesn't work well with raid0 ==<br />
<br />
Note that loading the "mdadm" hook doesn't always work with raid0. I've found out the hard way that this wiki just isn't complete.<br />
<br />
I had to load the "raid" hook instaid of the "mdadm" hook and had to load it ''before'' autodetect for it to work, like so:<br />
<div>HOOKS="base udev raid autodetect pata scsi sata filesystems"</div><br />
I puzzled this together by combining the wiki together with a "how to set up RAID during installation" guide I found on the ARCH forums.<br />
<br />
I had to do this in a chroot and only really used the setup for the packages.<br />
<br />
--[[User:Thajan|Thajan]] 13:07, 24 July 2009 (EDT)</div>Thajanhttps://wiki.archlinux.org/index.php?title=Talk:Installing_with_Software_RAID_or_LVM&diff=72645Talk:Installing with Software RAID or LVM2009-07-24T17:07:32Z<p>Thajan: /* The "mdadm" approach doesn't work well with raid0 */</p>
<hr />
<div>It was pointed out here:<br />
http://bbs.archlinux.org/viewtopic.php?p=121424#121495<br />
that software RAIDing your swap is not useful, and even slows performance.<br />
<br />
== bug in /etc/rc.sysinit?? ==<br />
<br />
I think there is a problem with /etc/rc.sysinit as it not loads the module for the device mapper. This is lvm specific. I just modified the file like this:<br />
<br />
if [ "$USELVM" = "yes" -o "$USELVM" = "YES" ]; then<br />
if [ -f /etc/lvmtab -a -x /sbin/vgchange ]; then<br />
# Kernel 2.4.x, LVM1 groups<br />
stat_busy "Activating LVM1 groups"<br />
/sbin/vgchange -a y<br />
stat_done<br />
elif [ -x /sbin/lvm -a -d /sys/block ]; then<br />
# Kernel 2.6.x, LVM2 groups<br />
stat_busy "Activating LVM2 groups"<br />
/sbin/modprobe dm_mod # <<-----Here is my change<br />
/sbin/lvm vgscan --ignorelockingfailure<br />
/sbin/lvm vgchange --ignorelockingfailure -a y<br />
stat_done<br />
fi<br />
fi<br />
<br />
i use the standard arch kernel<br />
<br />
== What about root on LVM ? ==<br />
I can't figure out how to make it...<br />
mkinitrd variable LVM_ROOT= what to set here??<br />
i am using grub and partition is like this:<br />
<br />
<div><br />
/dev/sda1 ext2 /boot<br />
/dev/sda2 LVM<br />
vg_name: linux<br />
lv_name: system / ext3<br />
home /home ext3<br />
swap none sw<br />
</div><br />
<br />
I've tryed <br />
LVM_ROOT=/dev/linux/system, <br />
grub kernel ... root=/dev/mapper/linux-system or root=/dev/linux/system<br />
i have USELVM=YES and in initrd LVM is enabled...<br />
<br />
lvm partitions was made with lvm2 - but i can activate and mount them manually<br />
where am i wrong??? - <br />
still blocked in bussybox with err - can't mount root - or so... or can't switch [don't remember] - <br />
lvm partitions are disabled - i have to enable and mount them manually<br />
<br />
--[[User:Suw|Suw]] 06:24, 8 April 2006 (EDT)<br />
<br />
== Lousy guide ==<br />
<br />
This has to be the worst, most crappy designed guide i have seen in all of my time with OpenSource, restructure this thing, and strip the old stuff for 7.1, it is VERY outdated. I must say that i would feel more confident just jumping head on out into raid on my own, than following this guid, get som structure in it.<br />
<br />
== Not completly lousy ==<br />
I did an install today and used this guide as a guideline, next to my common sense and other documentation on the mighty internet. Looking at this guide from an abstract point of view one will find that the principles are still the same. Going into basic details, you'll also get the gist. But several specifics are inaccurate and the overall structure could be improved. The guidance goes flaky once you get to the "Install and Configure Arch" part and beyond. Because it is so outdated.<br />
That's where I had to use outside sources and apply my own knowhow to get the system running.<br />
Perhaps i'll edit some bits here and there to patch it up a little. I have a general idea of what I did to get it right. And i'll enter a new GRUB example, because the kernel with the mdadm hook can detect arrays, or get it right by reading /etc/mdadm.conf.<br />
<br />
--[[User:Ultraman|Ultraman]] 2:47, 3 May 2008 (CEST)<br />
<br />
== rebuild from chroot to avoid getting dropped to ramfs after grub install ==<br />
<br />
for some reason the initcpio was not giving me my raid volumes after i tried to boot into the new system as instructed by the article. this problem went away after i used the install cd to boot, loaded raid1, raid5, and dm_mod modules manually, assembled arrays, activated the volume group, mounted the partitions, chrooted into the new system and rebuilt kernel26 (and therefore the initcpio). notably, i needed to mount /sys in addition to /proc and /dev prior to chrooting in order to get this to work. i only mention this because it seems like this article and several others omit /sys as a source of device files when instructing users to chroot. assuming that grub desires some access to devices when installing, i am wondering why only /proc and /dev are sufficient in the example outlined in the article but not in my case?<br />
<br />
NB- in the course of my troubleshooting i added definition of the raid1 array on which my / is located to the kernel line in menu.lst and i can say that this alone is insufficient to confer bootability to the installation as defined in the article. i have not tried my configuration without this (it shouldn't be necessary with the mdadm hook in mkinitcpio.conf)<br />
<br />
--[[User:Poopship21|Poopship21]] 21:24, 28 June 2009 (EDT)<br />
<br />
== The "mdadm" approach doesn't work well with raid0 ==<br />
<br />
Note that loading the "mdadm" hook doesn't always work with raid0. I've found out the hard way that this wiki just isn't complete.<br />
<br />
I had to load the "raid" hook instaid of the "mdadm" hook and had to load it ''before'' autodetect for it to work, like so:<br />
HOOKS="base udev raid autodetect pata scsi sata filesystems"<br />
<br />
I puzzled this together by combining the wiki together with a "how to set up RAID during installation" guide I found on the ARCH forums.<br />
<br />
I had to do this in a chroot and only really used the setup for the packages.<br />
<br />
--[[User:Thajan|Thajan]] 13:07, 24 July 2009 (EDT)</div>Thajanhttps://wiki.archlinux.org/index.php?title=Talk:Installing_with_Software_RAID_or_LVM&diff=72644Talk:Installing with Software RAID or LVM2009-07-24T17:05:39Z<p>Thajan: /* The "mdadm" approach doesn't work well with raid0 */ new section</p>
<hr />
<div>It was pointed out here:<br />
http://bbs.archlinux.org/viewtopic.php?p=121424#121495<br />
that software RAIDing your swap is not useful, and even slows performance.<br />
<br />
== bug in /etc/rc.sysinit?? ==<br />
<br />
I think there is a problem with /etc/rc.sysinit as it not loads the module for the device mapper. This is lvm specific. I just modified the file like this:<br />
<br />
if [ "$USELVM" = "yes" -o "$USELVM" = "YES" ]; then<br />
if [ -f /etc/lvmtab -a -x /sbin/vgchange ]; then<br />
# Kernel 2.4.x, LVM1 groups<br />
stat_busy "Activating LVM1 groups"<br />
/sbin/vgchange -a y<br />
stat_done<br />
elif [ -x /sbin/lvm -a -d /sys/block ]; then<br />
# Kernel 2.6.x, LVM2 groups<br />
stat_busy "Activating LVM2 groups"<br />
/sbin/modprobe dm_mod # <<-----Here is my change<br />
/sbin/lvm vgscan --ignorelockingfailure<br />
/sbin/lvm vgchange --ignorelockingfailure -a y<br />
stat_done<br />
fi<br />
fi<br />
<br />
i use the standard arch kernel<br />
<br />
== What about root on LVM ? ==<br />
I can't figure out how to make it...<br />
mkinitrd variable LVM_ROOT= what to set here??<br />
i am using grub and partition is like this:<br />
<br />
<div><br />
/dev/sda1 ext2 /boot<br />
/dev/sda2 LVM<br />
vg_name: linux<br />
lv_name: system / ext3<br />
home /home ext3<br />
swap none sw<br />
</div><br />
<br />
I've tryed <br />
LVM_ROOT=/dev/linux/system, <br />
grub kernel ... root=/dev/mapper/linux-system or root=/dev/linux/system<br />
i have USELVM=YES and in initrd LVM is enabled...<br />
<br />
lvm partitions was made with lvm2 - but i can activate and mount them manually<br />
where am i wrong??? - <br />
still blocked in bussybox with err - can't mount root - or so... or can't switch [don't remember] - <br />
lvm partitions are disabled - i have to enable and mount them manually<br />
<br />
--[[User:Suw|Suw]] 06:24, 8 April 2006 (EDT)<br />
<br />
== Lousy guide ==<br />
<br />
This has to be the worst, most crappy designed guide i have seen in all of my time with OpenSource, restructure this thing, and strip the old stuff for 7.1, it is VERY outdated. I must say that i would feel more confident just jumping head on out into raid on my own, than following this guid, get som structure in it.<br />
<br />
== Not completly lousy ==<br />
I did an install today and used this guide as a guideline, next to my common sense and other documentation on the mighty internet. Looking at this guide from an abstract point of view one will find that the principles are still the same. Going into basic details, you'll also get the gist. But several specifics are inaccurate and the overall structure could be improved. The guidance goes flaky once you get to the "Install and Configure Arch" part and beyond. Because it is so outdated.<br />
That's where I had to use outside sources and apply my own knowhow to get the system running.<br />
Perhaps i'll edit some bits here and there to patch it up a little. I have a general idea of what I did to get it right. And i'll enter a new GRUB example, because the kernel with the mdadm hook can detect arrays, or get it right by reading /etc/mdadm.conf.<br />
<br />
--[[User:Ultraman|Ultraman]] 2:47, 3 May 2008 (CEST)<br />
<br />
== rebuild from chroot to avoid getting dropped to ramfs after grub install ==<br />
<br />
for some reason the initcpio was not giving me my raid volumes after i tried to boot into the new system as instructed by the article. this problem went away after i used the install cd to boot, loaded raid1, raid5, and dm_mod modules manually, assembled arrays, activated the volume group, mounted the partitions, chrooted into the new system and rebuilt kernel26 (and therefore the initcpio). notably, i needed to mount /sys in addition to /proc and /dev prior to chrooting in order to get this to work. i only mention this because it seems like this article and several others omit /sys as a source of device files when instructing users to chroot. assuming that grub desires some access to devices when installing, i am wondering why only /proc and /dev are sufficient in the example outlined in the article but not in my case?<br />
<br />
NB- in the course of my troubleshooting i added definition of the raid1 array on which my / is located to the kernel line in menu.lst and i can say that this alone is insufficient to confer bootability to the installation as defined in the article. i have not tried my configuration without this (it shouldn't be necessary with the mdadm hook in mkinitcpio.conf)<br />
<br />
--[[User:Poopship21|Poopship21]] 21:24, 28 June 2009 (EDT)<br />
<br />
== The "mdadm" approach doesn't work well with raid0 ==<br />
<br />
Note that loading the "mdadm" hook doesn't always work with raid0. I've found out the hard way that this wiki just isn't complete.<br />
<br />
I had to load the "raid" hook instaid of the "mdadm" hook and had to load it ''before'' autodetect for it to work, like so:<br />
HOOKS="base udev raid autodetect pata scsi sata filesystems"<br />
<br />
I puzzled this together by combining the wiki together with a "how to set up RAID during installation" guide I found on the ARCH forums.<br />
<br />
I had to do this in a chroot and only really used the setup for the packages.</div>Thajanhttps://wiki.archlinux.org/index.php?title=Arch_Linux_(Nederlands)&diff=71904Arch Linux (Nederlands)2009-07-11T15:11:12Z<p>Thajan: Editted to fix some of the typos and to make it more conform with the English version. Made sure the essence of the article was practically the same</p>
<hr />
<div>[[Category:Nederlandstalig]]<br />
{{Arch Linux i18n Links}}<br />
<br />
== Wat is Arch Linux? ==<br />
Arch Linux is een onafhankelijke en voor i686-geoptimaliseerde distributie voor gevorderde gebruikers. Oorspronkelijk was Arch Linux gebaseerd op CRUX, een Linux distributie ontwikkeld door Per Lidén.<br />
De eerste versie van Arch (Versie 0.1, codenaam "Homer") werd uitgebracht op 11 maart, 2002.<br />
<br />
== Voordelen ==<br />
Arch is snel, licht, flexibel en simpel. Dit zijn misschien populaire sleutelwoorden maar ze zijn wel allen waar. Arch is geoptimaliseerd voor de i686 architectuur, waardoor er optimaal gebruik wordt gemaakt van de modernere processoren. Arch is licht vergeleken met Red Hat etc., en het simpele ontwerp maakt het makkelijk uit te breiden zoals de gebruiker het wil.<br />
<br />
== Uniek pakketten-beheer ==<br />
Arch wordt ondersteund door een makkelijk te gebruiken binair pakkettensysteem - [[pacman]]. Pacman staat u toe het gehele systeem te upgraden met één commando. Arch gebruikt ook een op ports lijkend pakkettensysteem ([[Arch Build System]]) om makkelijk zelf pakketten te kunnen maken. Ook de ([[Arch Build System]]) kan bijgewerkt worden met één commando. Het is zelfs mogelijk het gehele systeem te herbouwen met één commando. Alles wordt hierdoor op een simpele en transparante manier uitgevoerd.<br />
<br />
== Alleen het beste ==<br />
Arch Linux streeft ernaar om altijd de laatste (stabiele) versies van de software te hebben. Op dit moment hebben is er een gestroomlijnde hoofd pakkettenset met een groeiende collectie van extra pakketten die gemaakt worden door gebruikers en ontwikkelaars.<br />
<br />
== Simpelheid is de sleutel ==<br />
Met als doel simpel en licht te zijn, zijn de relatief nutteloze delen van een Linux systeem weggelaten, dingen als /usr/doc en de info pagina's. Deze worden nauwelijks gebruikt en vergelijkbare informatie kan van het internet worden gehaald. Ook kunnen man-pages gebruikt worden.<br />
<br />
== Moderne hulpmiddelen ==<br />
Arch Linux streeft er naar om Linux gebruikers de nieuwste stabiele software te laten gebruiken. Dit betekend, onder andere, moderne filesystems (Ext2/3/4, Reiser, XFS, JFS), software RAID, udev ondersteuning en de allerlaatste kernels.<br />
<br />
== Verder lezen ==<br />
Arch' website is te vinden op http://www.archlinux.org. Hier kan men ook een forum, officiële documentatie en andere informatie over Arch gerelateerde onderwerpen vinden. Ook kan men ''The Arch Way'' lezen voor meer inzicht over de filosofie achter Arch Linux.</div>Thajan