- Arch-releng - lists.archlinux.org

[arch-releng] [PATCH] [archiso] Refactor: Use losetup from util-linux
by Gerardo Exequiel Pozzi 11 Jan '12

11 Jan '12

New losetup from util-linux 2.21 uses new /dev/loop-control from Linux 3.1. Needs mkinitcpio-0.8.2+ (provides modules.devname, or workaround with earlymodules=loop) Get advantages from it! Removing custom shell code. (tested and working, will be merged when next util-linux/mkinitcpio hits [core]) Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> --- archiso/hooks/archiso | 37 +++---------------------------------- archiso/hooks/archiso_loop_mnt | 10 ++++------ archiso/install/archiso | 1 + 3 files changed, 8 insertions(+), 40 deletions(-) diff --git a/archiso/hooks/archiso b/archiso/hooks/archiso index 2635a4c..3518d16 100644 --- a/archiso/hooks/archiso +++ b/archiso/hooks/archiso @@ -1,27 +1,3 @@ -# Initialize loopback device logic (we using on-demand mode) -# args: none -_init_loop_dev() { - loop_dev_count=99 - loop_dev_range=$(cat /sys/block/loop0/range) - loop_dev_minor=$((loop_dev_count*loop_dev_range)) -} - -# Call this function before _make_loop_dev() each time. -# args: none -_next_loop_dev() { - loop_dev_count=$((loop_dev_count+1)) - loop_dev_minor=$((loop_dev_count*loop_dev_range)) -} - -# Setup a loopback device for image passed as argument and echo the path to loopback device used. -# args: /path/to/image_file -_make_loop_dev() { - local img="${1}" - mknod /dev/loop${loop_dev_count} b 7 ${loop_dev_minor} &> /dev/null - losetup /dev/loop${loop_dev_count} "${img}" &> /dev/null - echo /dev/loop${loop_dev_count} -} - # args: source, newroot, mountpoint _mnt_fs() { local img="${1}" @@ -34,8 +10,7 @@ _mnt_fs() { mkdir -p "${newroot}${mnt}" - _next_loop_dev - ro_dev=$(_make_loop_dev "${img}") + ro_dev=$(losetup --find --show "${img}") ro_dev_size=$(blockdev --getsz ${ro_dev}) if [[ "${cow_persistent}" == "P" ]]; then @@ -54,8 +29,7 @@ _mnt_fs() { dd of="/run/archiso/cowspace/${cow_directory}/${img_name}.cow" count=0 seek=${ro_dev_size} &> /dev/null fi - _next_loop_dev - rw_dev=$(_make_loop_dev "/run/archiso/cowspace/${cow_directory}/${img_name}.cow") + rw_dev=$(losetup --find --show "/run/archiso/cowspace/${cow_directory}/${img_name}.cow") echo "0 ${ro_dev_size} snapshot ${ro_dev} ${rw_dev} ${cow_persistent} 8" | dmsetup create ${dm_snap_name} @@ -85,9 +59,8 @@ _mnt_sfs() { img="/run/archiso/copytoram/${img_fullname}" msg "done." fi - _next_loop_dev msg ":: Mounting '${img}' (SquashFS) to '${mnt}'" - if ! mount -r $(_make_loop_dev "${img}") "${mnt}" &> /dev/null ; then + if ! mount -r "${img}" "${mnt}" &> /dev/null ; then echo "ERROR: while mounting '${img}' to '${mnt}'" launch_interactive_shell fi @@ -130,8 +103,6 @@ _verify_checksum() { } run_hook() { - modprobe loop - [[ -z "${arch}" ]] && arch="$(uname -m)" [[ -z "${cowspace_size}" ]] && cowspace_size="75%" [[ -z "${copytoram_size}" ]] && copytoram_size="75%" @@ -166,8 +137,6 @@ run_hook() { archiso_mount_handler() { local newroot="${1}" - _init_loop_dev - mountpoint -q "/run/archiso/bootmnt" || _mnt_dev "${archisodevice}" "/run/archiso/bootmnt" "-r" if [[ ! -f "${aitab}" ]]; then diff --git a/archiso/hooks/archiso_loop_mnt b/archiso/hooks/archiso_loop_mnt index e52dc69..664f3a5 100644 --- a/archiso/hooks/archiso_loop_mnt +++ b/archiso/hooks/archiso_loop_mnt @@ -10,15 +10,13 @@ run_hook () { archiso_loop_mount_handler () { newroot="${1}" + local _dev_loop + msg ":: Setup a loop device from ${img_loop} located at device ${img_dev}" _mnt_dev "${img_dev}" "/run/archiso/img_dev" "-r" - _dev_loop=$(losetup -f) - if ! losetup "${_dev_loop}" "/run/archiso/img_dev/${img_loop}"; then - echo "ERROR: Setting loopback device '${_dev_loop}'" - echo " for file '/run/archiso/img_dev/${img_loop}'" - echo " Falling back to interactive prompt" - echo " You can try to fix the problem manually, log out when you are finished" + if ! _dev_loop=$(losetup --find --show "/run/archiso/img_dev/${img_loop}"); then + echo "ERROR: Setting loopback device for file '/run/archiso/img_dev/${img_loop}'" launch_interactive_shell fi diff --git a/archiso/install/archiso b/archiso/install/archiso index 3b4e223..db0fc3a 100644 --- a/archiso/install/archiso +++ b/archiso/install/archiso @@ -8,6 +8,7 @@ build () add_binary /lib/udev/cdrom_id add_binary /sbin/blockdev add_binary /sbin/dmsetup + add_binary /sbin/losetup add_binary /bin/mountpoint add_file /lib/udev/rules.d/60-cdrom_id.rules -- 1.7.8.1

1 0

[arch-releng] archiso rebuild
by gt 05 Jan '12

05 Jan '12

Hello folks I asked this question on arch-general, but was referred here. Anyway, here's the original mail. ---------------------------------------------------------------------- I was wondering if there is a way to rebuild a custom live disc, using archiso, without having to download all the packages over again. The problem is that after making a few changes to the configuration, mainly inside root-image directory, i want to rebuild the iso. But, running build.sh says that everything is up-to-date. Alternatively, i tried removing the root squashfs file, and ran build.sh again. But, it started downloading ~500MB of packages all over again :( I'll probably have to do some more fine tuning before finalising the iso, and i don't want this to repeat itself. Please help. -- O< ascii ribbon campaign - stop html mail - www.asciiribbon.org

2 3

[arch-releng] grub install not listing partitions
by Dieter Plaetinck 05 Jan '12

05 Jan '12

Why exactly don't we list partitions anymore? (see https://github.com/Dieterbe/aif/commit/55190c0c81fc76f8b2b3983e790f2c7aacf4…) IIRC you said it shouldn't be really needed, but turns out it is: https://bugs.archlinux.org/task/25726 see also http://mailman.archlinux.org/pipermail/arch-releng/2011-March/001557.html so we should probably list again all blockdevices (partitions and devices themselves) Dieter

9 26

[arch-releng] Arch Linux Official Installation Guide in git
by Karol Blazewicz 26 Dec '11

26 Dec '11

Is http://projects.archlinux.org/aif.git/plain/doc/official_installation_guide… the latest version? It says so on https://wiki.archlinux.org/index.php/Official_Installation_Guide. Will the Official Installation Guide that's in the wiki be updated?

2 3

[arch-releng] Christmas Release?
by Thomas Bächler 26 Dec '11

26 Dec '11

I am not sure what happened in AIF, but archiso has seen some improvements. Should we push out a Christmas Release with the latest stuff? Once the pacman 4/signing stuff is finished and in core, tweaks to AIF will be needed which will probably delay another release, so better do one now, before that happens. What do you guys think?

4 6

[arch-releng] rc.conf documentation
by Dieter Plaetinck 25 Dec '11

25 Dec '11

Hi, rc.conf is a bit documented in several places: 1) in rc.conf itself, although documentation there is a bit limited (not always explaining what things are for exactly) but it does contain stuff like examples for networking. 2) in the official installation guide, which has historically been more extensive in describing what things are for and how to make your choice, although it lags behind because it is not tightly coupled to rc.conf, usually I update it when I notice (or somebody tells me) it's out of date. 3) https://wiki.archlinux.org/index.php/Rc.conf which is similar to (2) but with a few more tips, it seems to be maintained by the community. Also I notice there is no manpage for rc.conf. How can we improve this situation? Maybe by maintaining a man page for rc.conf which is as extensive as what currently in the official install guide? then, in the official installation guide, I can just refer to the rc.conf manpage, meaning the documentation is always in sync, at the same time it would also allow to make the documentation in rc.conf a bit more minimal. Dieter

1 0

[arch-releng] rc.conf documentation
by Dieter Plaetinck 25 Dec '11

25 Dec '11

Hi, rc.conf is a bit documented in several places: 1) in rc.conf itself, although documentation there is a bit limited (not always explaining what things are for exactly) but it does contain stuff like examples for networking. 2) in the official installation guide, which has historically been more extensive in describing what things are for and how to make your choice, although it lags behind because it is not tightly coupled to rc.conf, usually I update it when I notice (or somebody tells me) it's out of date. 3) https://wiki.archlinux.org/index.php/Rc.conf which is similar to (2) but with a few more tips, it seems to be maintained by the community. Also I notice there is no manpage for rc.conf. How can we improve this situation? Maybe by maintaining a man page for rc.conf which is as extensive as what currently in the official install guide? then, in the official installation guide, I can just refer to the rc.conf manpage, meaning the documentation is always in sync, at the same time it would also allow to make the documentation in rc.conf a bit more minimal. Dieter

1 0

[arch-releng] WIP: qemu-kvm helper for testing VM's
by Dieter Plaetinck 24 Dec '11

24 Dec '11

Hi, i created a simple script to run test/install VM's based on qemu-kvm. i started off with http://blog.falconindy.com/articles/build-a-virtual-army.html i didn't test the networking yet (in fact, i have networking disabled for now) but the useful thing about this script is it automatically adds the right serial/console parameters to the kernel args, when booting archiso, using xdotool (for this to work, ttyS0 needs to be setup in inittab). two problems: 1) i can't do the same xdotool trick yet when booting the actual system, because syslinux doesn't appear in the terminal when booting the system, whereas it does appear when booting archiso. (this is why for now you get to see both the terminal and a vga window in vm_run()) 2) when booting the target system, the kernel doesn't seem to find the blockdevice at all. (whereas it just works when booting archiso). here's what I have so far, maybe somebody finds it useful: feedback very welcome. #!/bin/bash mem=1024 cpus=2 net='nic,model=virtio' drive='file=arch-testbox,if=virtio' cdrom=$HOME/downloads/archlinux-2011.12.24_10-40-01-core-i686.iso vm_install () { (sleep 2; xdotool key Tab ; sleep 1; xdotool type --delay 30 " serial=tty0 console=ttyS0,115200n8"; xdotool key Return) & qemu-kvm -m $mem -smp $cpus -net $net -drive $drive -cdrom $cdrom -boot d -serial /dev/tty -nographic } vm_run () { # TODO: fix this, syslinux doesn't appear on tty (whereas it does appear when booting archiso) #(sleep 2; xdotool key Tab ; sleep 1; xdotool type --delay 30 " serial=tty0 console=ttyS0,115200n8"; xdotool key Return) & qemu-kvm -m $mem -smp $cpus -net $net -drive $drive -cdrom $cdrom -serial /dev/tty } #vm_install vm_run

1 0

[arch-releng] grub install not listing partitions
by Eric Fernandez 15 Dec '11

15 Dec '11

Hi, I am the original reporter of https://bugs.archlinux.org/task/25726 and as Desmond Cox explained, it is more practical to use chainloading than having one grub. Maintenance is more difficult when having several kernels from different distribution in one grub, and increases risks of having one distribution wrongly editing entries when updating their own kernel options. Like Desmond, I never experienced any problem installing grub in a partition. Removing the possibility to install grub in a partition is in my opinion contrary to KISS, especially if there are no stable alternatives (I shall try syslinux, as you recommend, but other posts make me wonder if this would work for me). Is it possible to allow installing grub on partitions as an "advanced" option? Thanks a lot in advance.

1 0

[arch-releng] [RFC] one more step forward to become archiso as self-pxe-server...
by Gerardo Exequiel Pozzi 04 Dec '11

04 Dec '11

Hello Current releng images are enabled to be used as self-PXE-server enviroment with: dnsmasq: For DHCP and TFTP nbd: for NBD nfs-utils: for NFS I like to add (They do not carry any extra dependency) Name : vsftpd Installed Size : 216.00 K Name : darkhttpd Installed Size : 36.00 K With these two tiny packages we will cover all protocols supported by archiso at this moment. The wiki page[#1] describe how to use live-enviroment to do this tasks. This also makes my life much easier when I want to test these things :) Any objections? Thanks. [#1] https://wiki.archlinux.org/index.php/Archiso_as_pxe_server#HTTP.2FFTP_and_N… -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

2 13