January 2011 - Arch-releng - lists.archlinux.org

[arch-releng] [PATCH 2/2] Use globbing and parameter expansion to get the raid slave devices
by pyther＠pyther.net 23 Jan '11

23 Jan '11

Uses bash globbing and parameter expansion to find all of the slaves for a raid device. This is a much better method then using ls. Also, by looking at DEVNAME in the uevent file we provide support for block device that are not in the root of /dev. call die_error if a block device is not passed into device_is_raid() --- src/core/libs/lib-blockdevices-filesystems.sh | 12 ++++++++---- 1 files changed, 8 insertions(+), 4 deletions(-) diff --git a/src/core/libs/lib-blockdevices-filesystems.sh b/src/core/libs/lib-blockdevices-filesystems.sh index 8451f15..f388d5b 100644 --- a/src/core/libs/lib-blockdevices-filesystems.sh +++ b/src/core/libs/lib-blockdevices-filesystems.sh @@ -921,7 +921,8 @@ get_blockdevice_size () # $1 blockdevice (ex: /dev/md0 or /dev/sda1) # All MD RAID block devices have a major id of 9 device_is_raid() { - [[ $1 && -f /proc/mdstat ]] || return 1 + [[ -b "$1" ]] || die_error "device_is_raid needs a blockdevice as \$1 ($1 given)" + [[ -f /proc/mdstast ]] || return 1 local devmajor=$(stat -c %t "$1") (( devmajor == 9 )) } @@ -942,10 +943,13 @@ mdraid_slave0 () # ex: /dev/md0 has slaves: "/dev/sda1 /dev/sdb2 /dev/sdc2" mdraid_all_slaves () { + shopt -s nullglob local slave= - local slaves= - for slave in $(ls /sys/class/block/$(basename $1)/slaves/); do - slaves=$slaves"/dev/"$slave" " + local slaves= + for slave in /sys/class/block/${1##*/}/slaves/*; do + source "$slave/uevent" + slaves="$slaves/dev/$DEVNAME " + unset DEVNAME done echo $slaves } -- 1.7.3.5

1 0

[arch-releng] [PATCH 1/2] Renamed mdraid_is_raid to device_is_raid
by pyther＠pyther.net 23 Jan '11

23 Jan '11

device_is_raid now uses dev major number to determine if a device is a raid device. A major ID of 8 is a /dev/sd? device whereas a major ID of 9 is a 'metadata' (raid) device. --- src/core/libs/lib-blockdevices-filesystems.sh | 20 ++++++-------------- src/core/libs/lib-ui-interactive.sh | 2 +- 2 files changed, 7 insertions(+), 15 deletions(-) diff --git a/src/core/libs/lib-blockdevices-filesystems.sh b/src/core/libs/lib-blockdevices-filesystems.sh index 8573b19..8451f15 100644 --- a/src/core/libs/lib-blockdevices-filesystems.sh +++ b/src/core/libs/lib-blockdevices-filesystems.sh @@ -919,20 +919,12 @@ get_blockdevice_size () # $1 blockdevice (ex: /dev/md0 or /dev/sda1) -# return true when blockdevice is an md raid, otherwise return a unset value -mdraid_is_raid() -{ - local israid - if [ -z $1 ]; then - # Don't call mdadm on empty blockdevice parameter! - israid="" - elif [ "$(mdadm --query $1 | cut -d':' -f2)" == " is not an md array" ]; then - israid="" - else - israid=true - fi - echo $israid -} +# All MD RAID block devices have a major id of 9 +device_is_raid() { + [[ $1 && -f /proc/mdstat ]] || return 1 + local devmajor=$(stat -c %t "$1") + (( devmajor == 9 )) +} # $1 md raid blockdevice (ex: /dev/md0) # return the array member device which is slave 0 in the given array diff --git a/src/core/libs/lib-ui-interactive.sh b/src/core/libs/lib-ui-interactive.sh index 881af90..829556a 100644 --- a/src/core/libs/lib-ui-interactive.sh +++ b/src/core/libs/lib-ui-interactive.sh @@ -878,7 +878,7 @@ interactive_grub() { bootdev=$(mount | grep $var_TARGET_DIR/boot | cut -d' ' -f 1) # check if bootdev or PART_ROOT is on a md raid array # This dialog is only shown when we detect / or /boot on a raid device. - if [ -n "$(mdraid_is_raid $bootdev)" -o -n "$(mdraid_is_raid $PART_ROOT)" ]; then + if device_is_raid $bootdev || device_is_raid $PART_ROOT; then ask_yesno "Do you have your system installed on software raid?\nAnswer 'YES' to install grub to another hard disk." no if [ $? -eq 0 ]; then onraid=true -- 1.7.3.5

1 0

[arch-releng] [PATCH] Renamed mdraid_is_raid to device_is_raid; new mdraid_all_slaves function
by pyther＠pyther.net 23 Jan '11

23 Jan '11

Renamed mdraid_is_raid to device_is_raid falconindy rewrote the device_is_raid and mdraid_all_slaves functions device_is_raid now uses dev major number to determine if a device is a raid device. A major ID of 8 is a /dev/sd? device whereas a major ID of 9 is a 'metadata' (raid) device. mdraid_all_slaves now uses a parameter expansion, reads the uevents file to get the DEVNAME and appends /dev to DEVNAME --- src/core/libs/lib-blockdevices-filesystems.sh | 31 +++++++++---------------- src/core/libs/lib-ui-interactive.sh | 2 +- 2 files changed, 12 insertions(+), 21 deletions(-) diff --git a/src/core/libs/lib-blockdevices-filesystems.sh b/src/core/libs/lib-blockdevices-filesystems.sh index 8573b19..2bb0a74 100644 --- a/src/core/libs/lib-blockdevices-filesystems.sh +++ b/src/core/libs/lib-blockdevices-filesystems.sh @@ -920,19 +920,11 @@ get_blockdevice_size () # $1 blockdevice (ex: /dev/md0 or /dev/sda1) # return true when blockdevice is an md raid, otherwise return a unset value -mdraid_is_raid() -{ - local israid - if [ -z $1 ]; then - # Don't call mdadm on empty blockdevice parameter! - israid="" - elif [ "$(mdadm --query $1 | cut -d':' -f2)" == " is not an md array" ]; then - israid="" - else - israid=true - fi - echo $israid -} +device_is_raid() { + [[ $1 && -f /proc/mdstat ]] || return 1 + local devmajor=$(stat -c %t "$1") + (( devmajor == 9 )) +} # $1 md raid blockdevice (ex: /dev/md0) # return the array member device which is slave 0 in the given array @@ -948,12 +940,11 @@ mdraid_slave0 () # $1 md raid blockdevice (ex: /dev/md0) # return a list of array members from given md array # ex: /dev/md0 has slaves: "/dev/sda1 /dev/sdb2 /dev/sdc2" -mdraid_all_slaves () -{ - local slave= - local slaves= - for slave in $(ls /sys/class/block/$(basename $1)/slaves/); do - slaves=$slaves"/dev/"$slave" " +mdraid_all_slaves () { + shopt -s nullglob + for slave in /sys/class/block/${1##*/}/slaves/*; do + eval $(cat $slave/uevent) + echo /dev/$DEVNAME + unset DEVNAME done - echo $slaves } diff --git a/src/core/libs/lib-ui-interactive.sh b/src/core/libs/lib-ui-interactive.sh index 881af90..829556a 100644 --- a/src/core/libs/lib-ui-interactive.sh +++ b/src/core/libs/lib-ui-interactive.sh @@ -878,7 +878,7 @@ interactive_grub() { bootdev=$(mount | grep $var_TARGET_DIR/boot | cut -d' ' -f 1) # check if bootdev or PART_ROOT is on a md raid array # This dialog is only shown when we detect / or /boot on a raid device. - if [ -n "$(mdraid_is_raid $bootdev)" -o -n "$(mdraid_is_raid $PART_ROOT)" ]; then + if device_is_raid $bootdev || device_is_raid $PART_ROOT; then ask_yesno "Do you have your system installed on software raid?\nAnswer 'YES' to install grub to another hard disk." no if [ $? -eq 0 ]; then onraid=true -- 1.7.3.5

3 2

[arch-releng] [PATCH] Renamed mdraid_is_raid, new device_is_raid mdraid_all_slaves function
by pyther＠pyther.net 21 Jan '11

21 Jan '11

Renamed mdraid_is_raid to device_is_raid falconindy rewrote the device_is_raid and mdraid_all_slaves functions device_is_raid now uses dev major number to determine if a device is a raid device. A major ID of 8 is a /dev/sd? device whereas a major ID of 9 is a 'metadata' (raid) device. mdraid_all_slaves now uses a parameter expansion to get the basename of the device --- src/core/libs/lib-blockdevices-filesystems.sh | 30 +++++++----------------- src/core/libs/lib-ui-interactive.sh | 2 +- 2 files changed, 10 insertions(+), 22 deletions(-) diff --git a/src/core/libs/lib-blockdevices-filesystems.sh b/src/core/libs/lib-blockdevices-filesystems.sh index 8573b19..a0ca15f 100644 --- a/src/core/libs/lib-blockdevices-filesystems.sh +++ b/src/core/libs/lib-blockdevices-filesystems.sh @@ -920,19 +920,11 @@ get_blockdevice_size () # $1 blockdevice (ex: /dev/md0 or /dev/sda1) # return true when blockdevice is an md raid, otherwise return a unset value -mdraid_is_raid() -{ - local israid - if [ -z $1 ]; then - # Don't call mdadm on empty blockdevice parameter! - israid="" - elif [ "$(mdadm --query $1 | cut -d':' -f2)" == " is not an md array" ]; then - israid="" - else - israid=true - fi - echo $israid -} +device_is_raid() { + [[ $1 && -f /proc/mdadm ]] || return 1 + local devmajor=$(stat -c %t "$1") + (( devmajor == 9 )) +} # $1 md raid blockdevice (ex: /dev/md0) # return the array member device which is slave 0 in the given array @@ -948,12 +940,8 @@ mdraid_slave0 () # $1 md raid blockdevice (ex: /dev/md0) # return a list of array members from given md array # ex: /dev/md0 has slaves: "/dev/sda1 /dev/sdb2 /dev/sdc2" -mdraid_all_slaves () -{ - local slave= - local slaves= - for slave in $(ls /sys/class/block/$(basename $1)/slaves/); do - slaves=$slaves"/dev/"$slave" " - done - echo $slaves +mdraid_all_slaves () { + shopt -s nullglob + local slaves=(/sys/class/block/${1##*/}/slaves/*) + echo "${slaves[@]##*/}" } diff --git a/src/core/libs/lib-ui-interactive.sh b/src/core/libs/lib-ui-interactive.sh index 881af90..41c035b 100644 --- a/src/core/libs/lib-ui-interactive.sh +++ b/src/core/libs/lib-ui-interactive.sh @@ -878,7 +878,7 @@ interactive_grub() { bootdev=$(mount | grep $var_TARGET_DIR/boot | cut -d' ' -f 1) # check if bootdev or PART_ROOT is on a md raid array # This dialog is only shown when we detect / or /boot on a raid device. - if [ -n "$(mdraid_is_raid $bootdev)" -o -n "$(mdraid_is_raid $PART_ROOT)" ]; then + if [ -n "$(device_is_raid $bootdev)" -o -n "$(device_is_raid $PART_ROOT)" ]; then ask_yesno "Do you have your system installed on software raid?\nAnswer 'YES' to install grub to another hard disk." no if [ $? -eq 0 ]; then onraid=true -- 1.7.3.5

2 1

Re: [arch-releng] Playing with unionfs-fuse (was: Status of AUFS2.1)
by Gerardo Exequiel Pozzi 18 Jan '11

18 Jan '11

On 01/17/2011 07:18 PM, Thomas Bächler wrote: > Am 17.01.2011 20:40, schrieb Tobias Powalowski: >> Hi guys, >> i'm getting tired of building aufs2 into the standard kernel, >> there are no stable snapshots, everytime you need grab patches and at the >> moment the utils don't even build without any real reason. >> Can we ditch aufs2 support? >> Does archiso really need this filesystem? >> >> Thanks for clarification, i would be happy if we can remove this. > We need a unioning file system. But I don't we think we actually need > the utils. As far as I know, aufs is the most feature-complete and > stable unioning file system. We could maintain an extra kernel only for > the live CD if that is easier. > I am currently playing with unionfs-fuse and archiso, so no need for extra modules. Two issues: 1) There is no "append" feature like with aufs, so all branchs should be mounted in one step. 2) Since is an userspace solution and there is no support for "omit_pid" [#1] in initscripts at the time, shutdown and reboot fails. Notes: 1) I never used it so I do not know how stable is. 2) No patches at this moment I just experimenting from ramfs# command line. [#1] https://bugs.archlinux.org/task/10536 PS: I am back from vacation :) -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

1 1

[arch-releng] Syslinux Installer / Update Script - Testers Needed
by Matthew Gyurgyik 16 Jan '11

16 Jan '11

Hello Community, Over the last few weeks I have been working on Syslinux support for the installer. With the help Thomas and Dieter I am nearing the completion of this project. As part of this project, I have written a script that will help install and update Syslinux (similar to that of grub-install). Some key features of the script: syslinux-install_update.sh * Install Syslinux to the FS + Partition Boot Loader (extlinux --install /boot/syslinux) * Install Syslinux MBR * Detect and optionally set the boot flag on the boot partition * Update Syslinux – copy files and execute (extilnux --update /boot/syslinux) * Support for GPT disks * Support for RAID configurations The goal is to include this script in the official Syslinux package. Therefore we need your help to test it. syslinux-install_update.sh -i -a -m ..... install Syslinux, set the boot flag (if needed), and install the MBR We need tests for the following setups: / + /boot on the *same* partition / + /boot on the *same* partition - RAID /boot + root on *separate* partition /boot + root on *separate* partition - RAID All of the above using but using the GPT partition layout NOTE: This is an alpha/beta stage script. The script modifies the first 440 bytes of the disk (using dd) and the partition table (using either sfdisk or sgdisk). Although the script should be safe to run, I am not responsible for any data loss that may occur. Let us know the following: * Did the script work for you? * What was your partition setup? (see above) * What version did you use? * If the script did not work, please provide as much information as possible Get the script here: https://gist.github.com/772138 Syslinux Sample Config File: http://projects.archlinux.org/svntogit/packages.git/plain/syslinux/trunk/sy… The Syslinux package in testing includes the above configuration file. Cheers, pyther

3 2

[arch-releng] [test iso 2011.01.09] testing results
by Thomas Dziedzic 14 Jan '11

14 Jan '11

I have decided to test the iso since I heard testing is at an all time low. I have filed 3 bugs from my experience so far: https://bugs.archlinux.org/task/22427 FS#22427 - [test iso 2011.01.09] aif fails to ask for mountpoint when creating btrfs partition. This really was the blocker for me because it didn't mount a / partition, so I was unable to install correctly. https://bugs.archlinux.org/task/22428 FS#22428 - [test iso 2011.01.09] aif package selection should be sorted more naturally. This issue is more of a human interface bug. I'm just requesting the reorganization of a list, otherwise, there are no problems with it. https://bugs.archlinux.org/task/22429 FS#22429 - [test iso 2011.01.09] aif during install truncates target list. Though this isn't really necessary, I would like to see the full list of targets rather then the first 3 packages (out of 100) displayed on a single line. My overall experience with the iso was pleasant, though it definitely needs more work on the btrfs side. I would like to thank Dieter and any other devs that are actively working on getting the next iso out the door.

1 0

[arch-releng] mention `pacman -Syu` in official install guide
by Andre "Osku" Schmidt 11 Jan '11

11 Jan '11

hi, just noticed that theres no mention at all about `pacman -Syu` in https://wiki.archlinux.org/index.php/Official_Arch_Linux_Install_Guide and now that we can do `pacman -Syu foobar` i would think it should be the first(ish) command to tell the users? anyone good with words? ;) cheers .andre ps. or is there a reason not to have it mentioned in this guide?

2 1

[arch-releng] from now on: automatic testbuilds + heads-up on changes
by Dieter Plaetinck 09 Jan '11

09 Jan '11

Hi, I want to inform you of two things: 1) new testbuilds available! A whole bunch of changes, both in the actual build environment, as well as AIF itself, where the changes are mostly related to how we automatically export configuration to the target system (locales, networking, initcpio, etc). for users, the main thing to remember is that we now always export the network config to the target system, whereas we used to ask for confirmation before. actually, so much has changed that despite my own tests it would suprise me if i already found/fixed all the regressions. for hackers: the aif code is now more readable :) Please have a look at the changelog: http://releng.archlinux.org/isos/Changelog Known issues: - when selecting source 'net', "install packages" won't realize the step has completed successfully. so you can do only do core installs, but the fix is already in git and will be on the next images. - some kind of kernel/vbox bug wrt virtual memory: http://mailman.archlinux.org/pipermail/arch-general/2011-January/017713.html - btrfs-progs, nilfs-utils and dosfstools packages cannot be installed to the target system (although you should be able to use those FS'es fine) 2) automatic builds: from now on, there will be automatic builds available @ http://releng.archlinux.org/isos/ i'm still playing around with the parameters, probably the builds will be daily or weekly. I would appreciate it if people could test these images and post their findings. Checklist of things which need to be verified. (when you test, you can obviously verify as many things as you want in one run) * dual arch image boot (pick your arch of preference at boot) * i686 image boot * x86_64 image boot * pxe boot * automatic install generic example * automatic install fancy example * net install manual spec (check that it works + rc.conf, resolv.conf, mirrorlist) * net install dhcp (check that it works + rc.conf) * core install * autoprepare (check the installed system, incl fstab) * manual partitioning/FS (with optionally: encryption, nilfs2, lvm,btrfs). (check also fstab, menu.lst, initcpio.conf and crypttab if appropriate) * doing a rollback and re-doing autoprepare or manual config TODO: - some kind of web app /wiki page where users can mark things in the checklist as "working with testbuild $version" ? that would give a good indication of when we can promote testbuilds to official releases - some way to give these more visibility (post to al.org frontpage? can we mirror first?..?) Dieter

2 3

[arch-releng] [PATCH] Define grubmenu as a global variable instead of multiple local variables
by pyther＠pyther.net 08 Jan '11

08 Jan '11

--- src/core/libs/lib-ui-interactive.sh | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/core/libs/lib-ui-interactive.sh b/src/core/libs/lib-ui-interactive.sh index 2297078..11cde02 100644 --- a/src/core/libs/lib-ui-interactive.sh +++ b/src/core/libs/lib-ui-interactive.sh @@ -1,6 +1,9 @@ #!/bin/bash # A library which allows you to do backend stuff by using user interfaces +# Global Variables +grubmenu="$var_TARGET_DIR/boot/grub/menu.lst" + # check if a worker has completed successfully. if not -> tell user he must do it + return 1 # if ok -> don't warn anything and return 0 check_depend () @@ -855,7 +858,6 @@ interactive_install_bootloader () { interactive_grub() { get_grub_map - local grubmenu="$var_TARGET_DIR/boot/grub/menu.lst" [ ! -f $grubmenu ] && show_warning "No grub?" "Error: Couldn't find $grubmenu. Is GRUB installed?" && return 1 debug FS "starting interactive_grub" @@ -995,7 +997,6 @@ interactive_grub() { } generate_grub_menulst() { - local grubmenu="$var_TARGET_DIR/boot/grub/menu.lst" get_device_with_mount '/' || return 1 local _rootpart=$ANSWER_DEVICE @@ -1128,7 +1129,6 @@ EOF } interactive_grub_menulst () { - local grubmenu="$var_TARGET_DIR/boot/grub/menu.lst" generate_grub_menulst helptext= grep -q '^/dev/mapper' $TMP_FSTAB && helptext=" /dev/mapper/ users: Pay attention to the kernel line!" -- 1.7.3.4

3 5