- Arch-general - lists.archlinux.org

[arch-general] Why is makepkg not using rc.d/functions?
by Andres Perera 25 Jan '10

25 Jan '10

Is it strictly because it shouldn't depend on initscripts, or is there another reason?

2 1

[arch-general] [signoff] pcmciautils-016-1
by Tobias Powalowski 25 Jan '10

25 Jan '10

Hi bump to latest version, please signoff. Changes to initcpio pcmcia hook were needed and added in git tree, on next mkinitcpio bump they will be included. - udev rules and helper programs are now installed to /lib/udev/ greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

3 2

[arch-general] mkinitcpio 0.6 alpha - testing and help needed
by Thomas Bächler 24 Jan '10

24 Jan '10

Quoted from http://bugs.archlinux.org/task/17298 (which is also to be used for feedback, besides the threads on these mailing lists): So, now something can be tested. I recommend using it in conjunction with testing/udev only: [kill-klibc] Server = http://dev.archlinux.org/~thomas/kill-klibc/i686/ or [kill-klibc] Server = http://dev.archlinux.org/~thomas/kill-klibc/x86_64/ The standard hooks work, so do keymap, lvm2, encrypt. What does NOT work is raid/mdadm/dmraid and root on NFS. I would appreciate any input and patches w.r.t. those, as well as any testing. The v86d package also needs to be fixed, but that is trivial. device-mapper, lvm2 and cryptsetup have a weird "1.local" pkgrel so they won't collide with the ones from the repo, sorry if that bothers anyone. If you upgrade to this repositories, your existing mkinitcpio will be replaced and all klibc packages will be gone too. So, if you try it, please save your existing initramfs to a different filename as a fallback, and do not perform kernel upgrades until you either confirmed that it works, or downgraded to the klibc-based mkinitcpio.

1 0

[arch-general] initramfs: execute own script
by AlannY 24 Jan '10

24 Jan '10

Hi there. I'm newbie in Archlinux's boot process. I need to run my own script in early userspace (initramfs). It must be after mounting root file system, but before switch root. I've opened default initramfs (kernel26.img) and reviewed it's content. So, Archlinux uses some kind of tool called 'kinit'. And it seems, that this tool mounts root and then switch. How to run my own script in kinit? Where can be found documentation of kinit? Thanks for patience. -- )\._.,--....,'``. /, _.. \ _\ (`._ ,. `._.-(,_..'--(,_..'`-.;.'

10 13

[arch-general] Two tiny patches for archweb_dev's ToDo lists
by Evangelos Foutras 24 Jan '10

24 Jan '10

I tested both patches locally and they appear to work. They are really tiny and straightforward so they should be safe to apply to the live dev site with little/no further testing. (I'm not sure who is maintaining the web interface nowadays, so I'm sending the patches to this ML.)

2 3

[arch-general] Confusion About /etc/hosts File
by Carlos Williams 24 Jan '10

24 Jan '10

I have never understood Arch's approach to properly setting a FQDN on a server. According to the Wiki...and I will quote: "Add your hostname, coinciding with the one specified in /etc/rc.conf, as an alias, so that it looks like this: 127.0.0.1 localhost.localdomain localhost yourhostname If you use a static IP, add another line using the syntax: <static-IP> <hostname.domainname.org> <hostname> e.g.: 192.168.1.100 yourhostname.domain.org yourhostname" Now this does not work for me and maybe I am not understanding this but my server hostname is "mail" and it will be managing a domain called "iamghost.com" so I need my output of the command 'hostname -f' to result in 'mail.iamghost.com' and when I follow the guide, that is not what I get. Obviously my server has a static IP so I followed the Wiki as shown below: #<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 localhost.localdomain localhost mail 10.1.1.200 mail.iamghost.com mail The above gives me the correct output when I run the 'hostname' command = 'mail' but when I run the 'hostname -f' command, I get localhost.localdomain. This will cause severe failures in MySQL and Postfix. Not to mention all my certificates I self sign / generate will not have the proper info. Can someone please explain to me why this does not work for me? Normally in distributions like CentOS, Debian, Slackware, etc etc etc...I am able to just enter a hostname and domain name for the system. Thanks!

4 4

[arch-general] [signoff] kernel 2.6.32.5-1
by Tobias Powalowski 24 Jan '10

24 Jan '10

Hi guys, bump to latest bugfix version. Please signoff both arches, greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

2 1

[arch-general] Why Is My RAID Installing Failing?
by Carlos Williams 23 Jan '10

23 Jan '10

OK - I am once again attempting to use Arch install for 2010 on my system which has two identical hard drives and I simply want to mirror both drives in a RAID1 array. I have read the Wiki so much at this point it has become memorized. I am NOT using LVM or anything, just a Arch user who wants RAID1, very simple, right? Well wait, it gets easier. I am not even attempting to add my MBR /dev/sda1 (/boot) to the RAID1 array. Crazy simple, huh? You might even ask well why am I even asking for help then...well because I hate the Arch installer and not because its CLI only. No, I love the simplicity of the installer and not being graphical but the RAID configuration is a complete mess. I am booting from a fresh 2009.08 Netinstall ISO disk. I select the 1st option and login as root (requires no password). Before I just junp into the installer (/arch/setup), I need to configure a few things: 1 - I use 'cfdisk' to configure /dev/sda & /dev/sdb. - /dev/sda1 = 4096 MB (bootable) 83 - /dev/sda2 = The rest of the disk (selecting 'fd' type) - /dev/sdb1 = 4096 MB (SWAP) 82 - /dev/sdb2 = The rest of the disk (selecting 'fd' type) 2. I need to load my RAID1 modules using the following command: #modprobe raid1 3. Now I need to create my RAID1 mirror using the following command: #mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sda2 /dev/sdb2 4. Check to make sure the RAID is rebuilding and both devices show [UU] #cat /proc/mdstat So now everything is working fine and going as it should be via the Wiki. Now the Wiki in my opinion is way too bloated and tries to do too much so I am cutting and pasting what I feel applies to me. Which is why I am showing you everything I am doing here in this email to see why I am failing. Now I need to update the /etc/mdadm.conf file with my new RAID1 I created with the following command: #mdadm -D --scan >> /etc/mdadm.conf And I also verify that my info was correctly populated into the /etc/mdadm.conf file using the following command: #cat /etc/mdadm.com So now I am ready to run the /arch/setup command from the CLI to begine configuring the install / my new system. 1 - Select Source = I configure my install method and all my network variables 2 - Set Clock = I configure my Time Zone and stuff 3 - Prepare Hard Drive(s) = Here I can skip to section sub menu 3 since I already did most of this above. I simply now just select mount points for my existing partitions: sda1 = /boot (ext3) sdb2 = swap (swap) md0 = / (ext4) 4 - Select Packages = I select the base packages and what I feel is required for my setup. 5 - Install packages = I let the system download and install the packages from my mirror. 6 - Configure System = This is where I feel my confusion comes into play. Perhaps I am missing something: */etc/rc/conf = I simply add the changes below: - In 'Hardware' section add "MODULES=(md_mod raid) - HOSTNAME="mypc" - "sshd" added to the "DAEMONS" line */etc/mkinitcpio.conf - add 'mdadm' on the 'HOOKS' line after "sata" & before "filesystems" as noted in the Wiki. */etc/resolv.conf - Check to make sure DNS looks good...it does. */etc/hosts - Add my FQDN here as follows: 127.0.0.1 mypc.mydomain.tld mypc *Root-Password - Create a secure root password. Now that is it. I select 'Done' and let it build 'initcpio' images. 7 - Install Bootloader = Here I select "Grub" and then review the default menu.lst it produces. I then select /dev/sda to install Grub on. "Grub was successfully installed" Now I am done and back at the bash shell logged in as root. I then run the following command: #cp -a /etc/mdadm.conf /mnt/etc/mdadm.conf to make sure when the system boots, it is aware of my RAID1 mirror. Now I reboot because I assume I am done. Here is my error: ::Running Hook [mdadm] Waiting 10 seconds for device /dev/md0 Root device '/dev/md0' doesn't exist, attempting to create it ERROR: Failed to parse block device for ids for /dev/md0 ERROR: Unable to detect or create root device /dev/md0 You are being dropped into a recovery shell Type reboot to reboot Type exit to try and continue booting If the device /dev/md0 gets created while you are here, try adding 'rootdelay=10 or higher to the kernel command line. ramfs$ _

9 32

[arch-general] nitrogen libpng rebuild information
by pyther 23 Jan '10

23 Jan '10

As nitrogen is currently orphaned I am sending this message here in hopes to avoid duplicate efforts. Two issues: -Nitrogen won't build against libpng 14 -Nitrogen crashes with "terminate called after throwing an instance of 'Gdk::PixbufError'" According to the developer: "It had a stray include of a libpng file that it hasnt needed in years that just sorta stayed there and recent libpng updates made that line problematic." He states that debian has a patch for this. However, he also states: "That's been long fixed in git. You can clone master if you want and grab it, or wait a few days, 1.5 has been in rc for a few weeks and no complaints about it so far so i'll release it soon." He stated it can be as soon as today. The crashes occur with both nitrogen 1.4.2 (from the extra repo) and git (soon to by 1.5). As I am writing this message, I am currently working with the developer to resolve this issue. He has given me a patch, which essential catches the error and prints some debug info to stderr. With this patch nitrogen git runs flawlessly. So I believe it is going to be a simple fix that should be hopefully be applied to git in the next few hours. With this said, I suggest that we wait for nitrogen 1.5 to be released. Even if we were to patch 1.4.2 we would still have the issue of the gdk::PixbufError crashes. ~pyther

2 4

[arch-general] tor new version
by nblock 22 Jan '10

22 Jan '10

Hi, The torproject released a new version of tor that fix some security problems. I updated the PKGBUILD, here is the patch: Index: PKGBUILD =================================================================== --- PKGBUILD (Revision 64847) +++ PKGBUILD (Arbeitskopie) @@ -3,7 +3,7 @@ # Contributor: simo <simo(a)archlinux.org> pkgname=tor -pkgver=0.2.1.21 +pkgver=0.2.1.22 pkgrel=1 pkgdesc="Anonymizing overlay network" arch=('i686' 'x86_64') @@ -15,7 +15,7 @@ source=(http://www.torproject.org/dist/tor-${pkgver}.tar.gz 'tor.conf' 'tor.rc') -md5sums=('54f7a801d824cd9c13ce672d483926d6' +md5sums=('583501a989ed0c39e209b604c3671ecd' '56c75d4e8a66f34167d31e38c43793dd' '23348b8e3b38c6ed2a45b4be42a7de8e') full PKGBUILD: # $Id: PKGBUILD 62137 2010-01-03 11:07:08Z andrea $ # Maintainer: # Contributor: simo <simo(a)archlinux.org> pkgname=tor pkgver=0.2.1.22 pkgrel=1 pkgdesc="Anonymizing overlay network" arch=('i686' 'x86_64') url="http://www.torproject.org/" license=('BSD') depends=('openssl' 'libevent' 'tsocks' 'bash') backup=('etc/tor/torrc' 'etc/tor/torrc-dist' 'etc/tor/tor-tsocks.conf') install=tor.install source=(http://www.torproject.org/dist/tor-${pkgver}.tar.gz 'tor.conf' 'tor.rc') md5sums=('583501a989ed0c39e209b604c3671ecd' '56c75d4e8a66f34167d31e38c43793dd' '23348b8e3b38c6ed2a45b4be42a7de8e') build() { cd ${srcdir}/${pkgname}-${pkgver} ./configure --prefix=/usr \ --sysconfdir=/etc \ --localstatedir=/var || return 1 make || return 1 make DESTDIR="$pkgdir" install || return 1 install -d ${pkgdir}/var/lib/tor || return 1 mv "$pkgdir/etc/tor/torrc.sample" "$pkgdir/etc/tor/torrc-dist" || return 1 install -D -m644 "$srcdir/tor.conf" "$pkgdir/etc/tor/torrc" || return 1 install -D -m755 "$srcdir/tor.rc" "$pkgdir/etc/rc.d/tor" || return 1 install -Dm644 LICENSE "$pkgdir/usr/share/licenses/tor/LICENSE" || return 1 } greetings, -- nblock

2 1