- Arch-general - lists.archlinux.org

[arch-general] No Compiz with current Kernels - but compiz with Linux alchemy 2.6.32-lts OK - Huh?
by David C. Rankin 12 Jul '10

12 Jul '10

Guys, On my box I continue to have problems with the current kernels on, booting lts works fine with compiz - how is that so? IIRC - lts used to be cli only, now it boots into runlevel 5 just fine. Any thoughts on why compiz won't run on 2.6.34-2 or 2.6.34.1-1? I'll keep tinkering, but any help would be appreciated... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

3 4

[arch-general] ABS Barfs
by ProfessorTomoe 12 Jul '10

12 Jul '10

I tried to pull down an abs update a few minutes ago and wound up getting everything but the "community," "any," and "local" directories completely removed from my /var/abs directory. I deleted and re-updated a few minutes later but still got nothing but the "community" and "any" repositories from the download. Any idea what's going on?

2 3

[arch-general] [PATCH] mkinitcpio: mount real root device instead of symlink
by Dave Reisner 12 Jul '10

12 Jul '10

If a symlink such as /dev/disk/by-uuid/xxxxx is provided on the kernel cmdline, resolve it and mount that device instead of the symlink. This prevents some ugliness in the output of commands such as mount or df. Signed-off-by: Dave Reisner <d(a)falconindy.com> --- init_functions | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/init_functions b/init_functions index 1ae844b..37b9ebb 100644 --- a/init_functions +++ b/init_functions @@ -93,5 +93,8 @@ default_mount_handler() { else rwopt="ro" fi + if [ -L "${root}" ]; then + root=$(readlink -f "${root}") + fi mount ${fstype:+-t ${fstype}} -o ${rwopt}${rootflags:+,${rootflags}} "${root}" "$1" } -- 1.7.1.1

2 1

[arch-general] [signoff] udev-160-1
by Tobias Powalowski 12 Jul '10

12 Jul '10

Hi guys, udev 160 ======== Bugfixes. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

1 0

[arch-general] boo package failure: /tmp/alpm_CTaAvu/.INSTALL: line 6: pre_remove: command not found
by David C. Rankin 12 Jul '10

12 Jul '10

Guys, Just thought I would pass this upgrade failure along: ( 2/13) upgrading boo [#####################################] 100% /tmp/alpm_CTaAvu/.INSTALL: line 6: pre_remove: command not found error: command failed to execute correctly Let me know if you want me to open a bug or if this is a spin-off of the current changes going on. Thanks. P.S. - what the hell is 'boo'? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

2 2

[arch-general] chroot failed to run command `/bin/bash`: Exec format error ??
by David C. Rankin 12 Jul '10

12 Jul '10

Guys, Booting from the dual install media, attempting to chroot again and I got an error I've never seen before: "chroot failed to run command `/bin/bash`: Exec format error" I checked with mount and all partitions and dev proc and sys where all mounted where they should be, but the box wouldn't chroot to my mount point under /mnt/a. Anybody recognize the error or what the cause could be? Thanks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

2 2

[arch-general] [PATCH 1/1] Make umounting filesystems much more paranoid.
by Victor Lowther 11 Jul '10

11 Jul '10

In addition to just umounting filesystems, we also try to tear down volume groups, crypt mappings, and loopback devices. We skip /, /proc, /sys, and /dev when umounting filesystems. We do all of the above in a loop, escalating how forcible we are in umounting filesystems up to the point where we give up and try to just remount filesystems read-only. We do not escalate how forcible we are until we stop making progress in umounting filesystems. This patch does not print anything when tearing down crypt devices, deactivating volume groups, or tearing down loopback devices. It does this because root on lvm and root on dm_crypt are fairly common cases, and figuring out which of these is the case and avoiding that volume group or dm_crypt mapping is tricky. We also no longer rely on /etc/crypttab at all for shutdown to tear down dm_crypt mappings. --- rc.shutdown | 112 +++++++++++++++++++++++++++++++++++++++++++++++----------- 1 files changed, 90 insertions(+), 22 deletions(-) diff --git a/rc.shutdown b/rc.shutdown index 2a561e4..d430dce 100755 --- a/rc.shutdown +++ b/rc.shutdown @@ -64,30 +64,98 @@ stat_busy "Deactivating Swap" /sbin/swapoff -a stat_done -stat_busy "Unmounting Filesystems" -/bin/umount -a -r -t noramfs,notmpfs,nosysfs,noproc,nodevtmpfs -O no_netdev -stat_done +# reverse an array +reverse() { + res=() + [[ $1 ]] || return 0 + local i=("$@") j=0 + for ((j=${#i[@]}-1; j>=0; j--)); do + res+=("${i[j]}") + done +} -# Kill non-root encrypted partition mappings -if [[ -f /etc/crypttab && $CS ]]; then - stat_busy "Deactivating encrypted volumes:" - do_lock() { - stat_append "${1}.." - if $CS remove "$1" >/dev/null 2>&1; then - stat_append "ok " - else - stat_append "failed " - fi - } - read_crypttab do_lock - stat_done -fi +# Get mounted filesystems +fs=() +ignore_re='^/(proc|sys|dev)?$' +while read dev mntpt rest; do + [[ $mntpt =~ $ignore_re ]] && continue + fs+=("$mntpt") +done < /proc/self/mounts +# reverse list of filesystems to let us umount them in reverse order +reverse "${fs[@]}" +fs=("${res[@]}") + +# get volume groups +vg=() +which lvm >/dev/null 2>&1 && \ + vg=($(lvm vgs --unbuffered --noheadings -o vg_name)) +# reverse list of volume groups to grab more of them at once. +reverse "${vg[@]}" +vg=("${res[@]}") + +# get crypto devices +crypt=() +[[ $CS ]] && { + for dev in /dev/mapper/*; do + "$CS" status "${dev##*/}" >/dev/null 2>&1 || continue + crypt+=(${dev##*/}) + done +} +# don't bother reversing crypt, it is in no defined order anyways. + +# get loopback devices in use +loops=() +which losetup >/dev/null 2>&1 && { + while read dev rest; do + loops+=("${dev%:}") + done < <(losetup -a) +} +reverse "${loops[@]}" +loops=("${res[@]}") + +do_umount() { + local ret=0 i j pass=$1 umountopts='' last + # do not umount anything that matches this regex + case $pass in + 2) umountopts='-f';; #next try forcing the umount + 3) umountopts='-r'; last=true;; #next try remounting readonly + esac + + # first, try umounting filesystems. + for i in "${!fs[@]}"; do + if status "Unmounting ${fs[i]} (pass $pass)" /bin/umount -d $umountopts \ + "${fs[i]}"; then + unset fs[$i] + else + ((ret++)) + fi + done + + # Second, deactivate any LVM groups that we can free up + for i in "${!vg[@]}"; do + /sbin/lvm vgchange --sysinit -an "${vg[i]}" >/dev/null 2>&1 && \ + unset vg[$i] + done + + # Third, tear down as many cryptsetup devices as we can. + for i in "${!crypt[@]}"; do + $CS remove "${crypt[i]}" >/dev/null 2>&1 && unset crypt[$i] + done + + # Last, tear down as many loop devices as we can + for i in "${!loops[@]}"; do + losetup -d "${loops[i]}" >/dev/null 2>&1 && unset loops[$i] + done + [[ $last = true ]] && return 0 + return $ret +} -if [[ $USELVM =~ yes|YES && -x /sbin/lvm && -d /sys/block ]]; then - stat_busy "Deactivating LVM2 groups" - /sbin/lvm vgchange --ignorelockingfailure -an >/dev/null 2>&1 - stat_done -fi +# Loop and try to umount filesystems +for ((pass=1,fses=${#fs[@]}; ;fses=${#fs[@]})); do + do_umount $pass && break; # if we umounted all the filesystems, break. + # only escalate if we did not make progress unmounting filesystems. + ((fses == ${#fs[@]})) && ((pass++)) +done stat_busy "Remounting Root Filesystem Read-only" /bin/mount -n -o remount,ro / -- 1.7.1.1

2 3

Re: [arch-general] [arch-dev-public] System update on all Arch Servers
by Emmanuel Benisty 11 Jul '10

11 Jul '10

On Sun, Jul 11, 2010 at 6:52 PM, Thomas Bächler <thomas(a)archlinux.org> wrote: > Hello, > > I -Syu'd and rebooted all our servers, let me know if there are any > problems. > > no idea if it's related or if I missed something but abs'ing yesterday was fine, today I get: [root@blackout ~]# abs ==> Starting ABS sync... Unexpected remote arg: rsync.archlinux.org::abs/i686/ rsync error: syntax or usage error (code 1) at main.c(1204) [sender=3.0.7]

3 3

[arch-general] [PATCH 1/2] Add daemon-functions to the initscripts package.
by Victor Lowther 11 Jul '10

11 Jul '10

This file encapsulates most common rc.d daemon script idioms, and should allow most of then to be about 6 lines long (not including whitespace) Using it will require some modifications to the /etc/conf.d files, as the generic functions expect all daemon options to be in $OPTS Among other things, this will close feature request# 18654 It was written on top of my bashification patch series, but is mostly independent of it. --- daemon-functions | 72 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ functions | 2 + 2 files changed, 74 insertions(+), 0 deletions(-) diff --git a/daemon-functions b/daemon-functions new file mode 100755 index 0000000..5f7660a --- /dev/null +++ b/daemon-functions @@ -0,0 +1,72 @@ +#!/bin/bash +# This file contains helper functions for initscripts in /etc/rc.d. +# I am keeping it seperate from the main /etc/rc.d/functions for now. +# Using this file makes most /etc/rc.d files as simple as +# #!/bin/bash +# DAEMON=/path/to/daemon +# case $1 in +# start|stop|restart|status) $1;; +# *) usage;; +# esac + +shopt -s extglob + +# first, source our usual files. +. /etc/rc.conf +. /etc/rc.d/functions + +# Next, declare some useful helper functions +have_daemon() { + local f + [[ $DAEMON && -x $DAEMON ]] || return 1 + [[ $DAEMONNAME ]] || DAEMONNAME="${0##*/}" + PIDS=($(pidof -o %PPID "$DAEMON")) + [[ $DAEMONCONF ]] || \ + for f in "$DAEMONNAME" "$DAEMONNAME.conf"; do + [[ -f /etc/conf.d/$f ]] || continue + DAEMONCONF="/etc/conf.d/$f" + break + done + return 0 +} + +start() { + have_daemon || exit 1 + [[ -f $DAEMONCONF ]] && . "$DAEMONCONF" + stat_busy "Starting $DAEMONNAME" + if [[ ! $PIDS ]] && "$DAEMON" $OPTS >/dev/null 2>&1; then + add_daemon "$DAEMONNAME" + stat_done + else + stat_fail + fi +} + +stop() { + have_daemon || exit 1 + stat_busy "Stopping $DAEMONNAME" + if [[ $PIDS ]] && kill "${PIDS[@]}" >/dev/null 2>&1; then + rm_daemon "$DAEMONNAME" + stat_done + else + stat_fail + fi +} + +restart() { + have_daemon || exit 1 + stat_busy "Restarting $DAEMONNAME" + "$0" stop + sleep 1 + "$0" start +} + +status() { + have_daemon || exit 1 + stat_busy "Checking status of $DAEMONNAME" + ck_status "$DAEMONNAME" +} + +usage() { + echo "Usage: $0 {start|stop|restart|status}" +} \ No newline at end of file diff --git a/functions b/functions index 5e9a3b5..83f8fb7 100644 --- a/functions +++ b/functions @@ -197,8 +197,10 @@ status_stopped() { ck_status() { if ! ck_daemon "$1"; then status_started + return 0 else status_stopped + return 1 fi } -- 1.7.1.1

1 1

Re: [arch-general] [arch-dev-public] [signoff] hdparm-9.29-1
by Emmanuel Benisty 11 Jul '10

11 Jul '10

On Sun, Jul 11, 2010 at 8:34 PM, Tobias Powalowski <t.powa(a)gmx.de> wrote: > Am Sonntag 11 Juli 2010 schrieb Ionuț Bîru: >> On 07/06/2010 02:49 PM, Ionuț Bîru wrote: >> > On 07/06/2010 02:46 PM, Tobias Powalowski wrote: >> >> Am Montag 05 Juli 2010 schrieb Tobias Powalowski: >> >>> Hi guys, >> >>> bump to latest version, added wiper.sh script. >> >>> please signoff both arches >> >>> >> >>> greetings >> >>> tpowa >> >> >> >> bump >> > >> > signoff x86_64 >> >> i'm canceling this signoff. happens when you have the output redirected >> into /dev/null >> >> hdparm -B 254 /dev/sda >> >> /dev/sda: >> setting Advanced Power Management level to 0xfe (254) >> HDIO_DRIVE_CMD failed: Input/output error >> HDIO_DRIVE_CMD(identify) failed: Input/output error > I get this here too, but i don't know if this have to work for each drive. what do you mean "for each drive" ? AFAIC, I have only one on this machine (it's a laptop). cheers

2 2