Arch Linux Newsletter

Jan 22, 2006
Jason Chu
Jason "CanyonKnight"


Welcome to the Arch Linux Newsletter. This document attempts to give you an "at a glance" look at the world of Arch Linux.
This week we have a major recap of the past few months, which means a lot has changed in the Arch Linux world. In order to keep the newsletter to a reasonable length, highlights are given for the large changes in Arch Linux. Some of the front page news was also about upcoming changes and package problems, the information will not be copied word for word into front page news but the summary will be given in the package highlights section.

Table Of Contents

  1. Front Page News
  2. Devland
  3. Forum Highlights
  4. Mailing List Highlights
  5. Package Highlights
  6. FAQ
  7. ArchStats
  8. Seti@home
  9. folding@home
  10. Bugs
  11. Closing

Front Page News

  1. Arch Linux 0.7.1 (Noodle) Released

    ...and it only took a year. :)
    Here it is, folks. All the Arch goodness you know and love, only half the fat. We've added some better hardware detection, stock initrd support for neat things like encrypted root filesystems, network profiles, and more little goodies here n' there. Thanks for the patience, everyone. As always, read the the docs before installing. You'll find ISO images in the usual location. Torrents too.


  1. The Archlinux developers have set up a blog ( If you are doing anything related to Archlinux, feel free to ask for access so you can post on it. The Archlinux blog is also distributed through Planet Archlinux.
  2. I'm sure you've probably heard of the libification of pacman. The project has been trucking along for quite some time now, they've opened the cvs up publically, and created a mailing list. The mailing list is here:
  3. With kernel 2.6.14, Archlinux now sports a shiny new initrd. I just wanted to take the time to recognize tpowa, phrakture, and Judd for all the work they put in to getting it run smoothly. Oh yeah, and the community, without everyone's input this update never would have happened.
  4. We've added quite a large number of developers since the last newsletter. Welcome Alexandar Baldeck, Mark Rosenstand, Paul Hoy, and Aaron Griffin.
  5. We've also lost a developer since the last newsletter. Everyone say goodbye to Roberto Carvajal.
  6. Talk has begun about moving GNOME out of /opt. We'll see what happens on the next upgrade.

Forum Highlights

  1. iphitus gave an update on all the work going into the archck patchset and users gave feedback to help development for another great release.
  2. droog talks with other bittorent users to see what everyone likes.
  3. arooaroo has released a new version of Jacman, a graphical frontend to Pacman.
  4. Neotuli explains about the Arch rolling release system.
  5. The_Nerd wants to know what filesystems people use in Arch
  6. Komodo has set up a programming competition with challenges each month.

Mailing List Highlights

  1. The new release of has arrived ( 7.0). Comments were given on the status of the migration. Work is still being done as 7.0 currently resides in [testing].
  2. The proper way to change /home and keep the correct permissions.
  3. Talk of shell choice in Arch Linux was brought up.

Package Highlights

  1. The standard Arch Linux kernel is now built with initrd as the standard. This allows the maintainers to build more parts of the kernel as modules and still have the users run their kernel smoothly.
  2. The initscripts now feature the useful hwdetect tool for detection of hardware on the machine. It uses the kernel for dynamic detection allowing you to have the proper modules loaded at boot.
  3. Udev replaces the importance of hotplug when using the kernel26 package. Users who use the kernel24 package can still have access to hotplug as the old kernel does not use udev.
  4. is in [testing] and provides modular support as opposed to the monolithic method. This means that the packages can be greatly broken up and you will have access to the packages that you need for your specific computer.
  5. Libtool files have been removed from packages. (A Few exceptions because on some packages libtool files are required.)


Q: What is the difference between AUR, COMMUNITY, and UNSUPPORTED?

A: AUR(Arch User Repository) is the name of the whole new system which is maintained by the TUs(Trusted Users). It lets anybody that signs up to upload PKGBUILDs to UNSUPPORTED but only TUs have access to COMMUNITY which is a binary repo that you can use with Pacman.

Q: Why aren't all packages in UNSUPPORTED added to COMMUNITY?

A: There are several reasons for that. The most important is that the package hasn't got many votes. It's also important that you vote for packages that already are in COMMUNITY, otherwise they could be disowned by the TUs and moved to UNSUPPORTED. Other reasons could be that the package is unmaintained upstreams or got a license problem. Last but not least, no TU wants to do it.

Q: I want this very cool feature A added to AUR and also this B thing would be nice. Can you do that?

A: There is a team of developers coding on AUR and they will for the moment focus on getting the current featureset bugfree instead of adding new things. AUR is still pretty young so there will be more features added as time goes by. :)


To Participate, visit:

Number of registered systems: 630
Longest recorded uptime: 496 days, 9 hours, 22 minutes, 38 seconds.
Average uptime: 7 days, 3 hours, 51 minutes, 24 seconds.
Least packages installed on a system: 88
Average installed packages: 387
Most packages installed on a system: 2539
Lowest Bogomips: 266.19
Average Bogomips: 3502.02
Highest Bogomips: 6995.96


To Participate, visit:

Members: 13
Total credit: 108,785.21


Arch Linux Team Page

Team Number: 45032
Members: 28
Score: 256545
Ranking: 930 of 42309



That's it for this time folks. If you have any opinions on the newsletter or have some things you wanna add, just send us a mail and we'll look into it.
Very best regards / Team Arch