July 2012 - Arch-releng - lists.archlinux.org

Re: [arch-releng] arch-releng Digest, Vol 40, Issue 8
by Mr Green 28 Jul '12

28 Jul '12

On 28/07/12 01:48, arch-releng-request(a)archlinux.org wrote Hi Gerardo, Yes have asked on ArchBang forums and the developer was very helpful, managed to solve the problem. Thanks for your help MrG > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 26 Jul 2012 16:31:13 -0300 > From: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> > To: Arch Linux Release Engineering <arch-releng(a)archlinux.org> > Subject: Re: [arch-releng] Iso booting > Message-ID: <50119B01.20302(a)yahoo.com.ar> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 07/26/2012 04:28 PM, Mr Green wrote: >> Have an odd problem, trying to boot an iso from grub2 using >> >> menuentry "Archlinux-2011.08.19-netinstall-x86_64.iso" { >> set isofile="/iso/archlinux-2012.07.15-netinstall-dual.iso" >> loopback loop (hd0,1)$isofile >> linux (loop)/arch/boot/x86_64/vmlinuz archisolabel=ARCH_201207 >> img_dev=/dev/sda1 img_loop=$isofile earlymodules=loop >> initrd (loop)/arch/boot/x86_64/archiso.img >> } >> >> menuentry "ArchBang" { >> set isofile="/iso/archbang-2012.07.26-x86_64.iso" >> loopback loop (hd0,1)$isofile >> linux (loop)/arch/boot/x86_64/vmlinuz archisolabel=ARCHBANG >> img_dev=/dev/sda1 img_loop=$isofile earlymodules=loop >> initrd (loop)/arch/boot/x86_64/archiso.img >> } >> >> The first menuentry works fine but ArchBang refuses to boot, both are >> in the same directory on the same disc. >> >> Odd thing is that /dev/disk/by-label is not created in Archbang, both >> isos have the same hooks loops, tried with latest archiso from git but >> no joy. >> >> Can anyone shed any light on the problem? >> >> MrG >> > Ask in ArchBang >

1 0

Re: [arch-releng] About AIF and Arch Linux
by Dieter Plaetinck 27 Jul '12

27 Jul '12

On Mon, 23 Jul 2012 11:40:55 +0200 Alexander Rødseth <rodseth(a)gmail.com> wrote: > Hello Dieter, > > I see that you've done a lot of good work on AIF and I am sad to see > it gone from the default Arch ISO. I wish Arch to do well and think > some sort of installation script/program is in order. > > The things I love about AIF is that the look is really minimalistic > and nostalgic, that it is easy and quick to navigate with a keyboard > and that it fits in with the no-compromise and minimalistic approach > of Arch. > However, I also wonder, if you were to write AIF from scratch, how > would you do it? if i would rewrite it, i'ld do it in python. bash has many limitations which i needed to work around (specifically wrt modules that need to override/inherit stuff, datastructures to describe complicated filesystem arrangements (json, yaml?) and other datastructures to pass data around (lists, dictionaries) would be useful) that said, you often just want to execute commands directly. for that, it's hard to beat bash. > Would it make sense to have auto detection of what > type of computer it is on? maybe, a bit. depends on what you mean > And, would it make sense to have "machine configuration packages" that > could be search and installed by users, so that setting up an Arch box > as say, a media server, would be as easy as "aif -S mediaserver"? a package is not the right thing to use. it's not easy to quickly customize, and you're bound by the limits of what a package can do. a config file for an installer (like aif) is more appropriate. also integration with existing tools like ansible, chef or puppet is something worth looking into. (ansible being way easier, and also in python) augeas is interesting too, though it adds a lot of complexity for only a small gain (maybe if it has a good python api, worth looking into) being compatible with kickstart configs would be nice too, although kickstart is aimed to be very imperative; aif allows to just define a filesystems structure in plaintext declaritively and it'll do the right thing (and figure out how to roll back if anything fails, although it seems that feature rarely or never got used). it's hard to match that with what kickstart does. > > I really like the Go programming language and the idea of > configuration-packages that are declarative. The thought of creating > AIF2, has struck my mind. sounds complex. as a user you want to be able to define complicated things, so if you want declarative configs, your format must support many complicated setups, and actually get the system into the configured state. AIF actually does this for some "basic" things (like filesystem settings), but adding users, configuring software should be done by executing commands and/or editing config files directly. usually it's easier for both the user and your implementation to make it imperative. > > If possible, I would like to both pick up the AIF-ball, and also > become an Arch Linux developer. I'm not sure if and how much I would > have to prove myself for the current crowd of Arch Linux developers > and trusted users for this to be feasible. > I do however have a sort of vision for what AIF could become, a few > years of programming behind me, moderate communication skills, good > intentions and a healthy dose of "stick to it"-attitude. > > What do you think? Could something positive come of this? maybe.

2 1

[arch-releng] Iso booting
by Mr Green 26 Jul '12

26 Jul '12

Have an odd problem, trying to boot an iso from grub2 using menuentry "Archlinux-2011.08.19-netinstall-x86_64.iso" { set isofile="/iso/archlinux-2012.07.15-netinstall-dual.iso" loopback loop (hd0,1)$isofile linux (loop)/arch/boot/x86_64/vmlinuz archisolabel=ARCH_201207 img_dev=/dev/sda1 img_loop=$isofile earlymodules=loop initrd (loop)/arch/boot/x86_64/archiso.img } menuentry "ArchBang" { set isofile="/iso/archbang-2012.07.26-x86_64.iso" loopback loop (hd0,1)$isofile linux (loop)/arch/boot/x86_64/vmlinuz archisolabel=ARCHBANG img_dev=/dev/sda1 img_loop=$isofile earlymodules=loop initrd (loop)/arch/boot/x86_64/archiso.img } The first menuentry works fine but ArchBang refuses to boot, both are in the same directory on the same disc. Odd thing is that /dev/disk/by-label is not created in Archbang, both isos have the same hooks loops, tried with latest archiso from git but no joy. Can anyone shed any light on the problem? MrG

2 1

[arch-releng] [PATCH] Add installation guide
by Pierre Schmitz 25 Jul '12

25 Jul '12

Download and add the current installation guide as plain text. Signed-off-by: Pierre Schmitz <pierre(a)archlinux.de> --- README | 1 + configs/releng/build.sh | 1 + configs/releng/root-image/root/install.txt | 3 +++ 3 Dateien geändert, 5 Zeilen hinzugefügt(+) create mode 100644 configs/releng/root-image/root/install.txt diff --git a/README b/README index c548bd1..58071ff 100644 --- a/README +++ b/README @@ -401,6 +401,7 @@ EOF ** For configs/releng build.sh needs theses packages (build host): + dosfstools for mkfs.vfat + patch for patch + * lynx for fetching the latest installation guide ** For these hooks needs these packages (on target root-image) * archiso diff --git a/configs/releng/build.sh b/configs/releng/build.sh index 62709ac..5352000 100755 --- a/configs/releng/build.sh +++ b/configs/releng/build.sh @@ -145,6 +145,7 @@ make_customize_root_image() { chmod 440 ${work_dir}/root-image/etc/sudoers.d/g_wheel mkdir -p ${work_dir}/root-image/etc/pacman.d wget -O ${work_dir}/root-image/etc/pacman.d/mirrorlist 'https://www.archlinux.org/mirrorlist/?country=all&protocol=http&use_mirror_…' + lynx -dump -nolist 'https://wiki.archlinux.org/index.php/Installation_Guide?action=render' >> ${work_dir}/root-image/root/install.txt sed -i "s/#Server/Server/g" ${work_dir}/root-image/etc/pacman.d/mirrorlist patch ${work_dir}/root-image/usr/bin/pacman-key < ${script_path}/pacman-key-4.0.3_unattended-keyring-init.patch sed -i 's/#$en_US\.UTF-8$/\1/' ${work_dir}/root-image/etc/locale.gen diff --git a/configs/releng/root-image/root/install.txt b/configs/releng/root-image/root/install.txt new file mode 100644 index 0000000..3c8f171 --- /dev/null +++ b/configs/releng/root-image/root/install.txt @@ -0,0 +1,3 @@ +View this installation guide online at +https://wiki.archlinux.org/index.php/Installation_Guide + -- 1.7.11.3

2 3

[arch-releng] [archiso] issue with syslinux and "config-jump-trick" with relative path
by Gerardo Exequiel Pozzi 24 Jul '12

24 Jul '12

Looks like something was changed in 4.05, since this thing [#1] was tested (4.04)... this is when using SYSLINUX (this is when copy "arch" and installing syslinux manually, not using hybrid method that ISOLINUX is used) ------ booting --------- SYSLINUX 4.05 0x4f5727e3 Copyright (C) 1994-2011 H. Peter Anvin et al Could not find kernel image: boot/syslinux/whichsys.c32 boot: syslinux/pwd /arch/boot/syslinux/../ boot: ------------------------- ----- syslinux.cfg ----- DEFAULT loadconfig LABEL loadconfig CONFIG archiso.cfg APPEND ../../ -------------------------- Workaround for now is using absolute path on destination medium| sed -i "s|../../|/arch|" /mnt/arch/boot/syslinux/syslinux.cfg| [#1] https://projects.archlinux.org/archiso.git/commit/?id=87e84261c99b8bfabf3f6… -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

1 1

[arch-releng] How about removing support for including [core]
by Pierre Schmitz 24 Jul '12

24 Jul '12

hi, as it seems we will only provide netinstall isos anyway, we probably can simplify the releng part of archiso a bit by. Maybe we can also remove the need to create the arch specific isos and just create one single dual iso. And finally we could also the no longer useful dual-netinstall prefix from the iso names. Any thoughts about this? Greetings, Pierre -- Pierre Schmitz, https://pierre-schmitz.com

2 2

Re: [arch-releng] [arch-dev-public] draft for new isos
by PReP Arch 23 Jul '12

23 Jul '12

Hello there arch-releng mailinglist folks (in case it is possible to reply and you even see this) I just gave the new ISO release a go in a VM, to get up to speed, And i would like to give some positive feedback. I do miss the good ol'e AIF, but following the arch install scripts wiki, i got it working without any particular issues - so good work there. I also harbour a suggestion; Might we perhaps have the arch-install-scripts-wiki guide available on the install-iso somehow? Even as a simple text-file, or even a bash-alias cat'ing it to the screen, i.e: "alias install='cat /doc/arch_install_scripts.text' or similar. Keep up the good work anyways :) /PReP

2 1

[arch-releng] [PATCH 1/2] testiso: remove booting from scsi as this is not supported by our qemu package
by Pierre Schmitz 23 Jul '12

23 Jul '12

Signed-off-by: Pierre Schmitz <pierre(a)archlinux.de> --- archiso/testiso | 16 ++++++---------- 1 Datei geändert, 6 Zeilen hinzugefügt(+), 10 Zeilen entfernt(-) diff --git a/archiso/testiso b/archiso/testiso index 71e85e1..7a4d5f1 100755 --- a/archiso/testiso +++ b/archiso/testiso @@ -1,26 +1,22 @@ #!/bin/bash if [[ $# -eq 0 ]]; then - echo "usage: testiso <isofile> [id|ic|sd|sc|vd|vc]" + echo "usage: testiso <isofile> [id|ic|vd|vc]" echo echo "id boot .iso as IDE disk" echo "ic boot .iso as IDE cd-rom" - echo "sd boot .iso as SCSI disk" - echo "sc boot .iso as SCSI cd-rom" echo "vd boot .iso as virtio disk" -# echo "vc boot .iso as virtio cd-rom" + echo "vc boot .iso as virtio cd-rom" exit 1 fi case "${2}" in id) IF="ide"; MEDIA="disk";; ic) IF="ide"; MEDIA="cdrom";; - sd) IF="scsi"; MEDIA="disk";; - sc) IF="scsi"; MEDIA="cdrom";; vd) IF="virtio"; MEDIA="disk";; -# vc) IF="virtio"; MEDIA="cdrom";; - *) IF="scsi"; MEDIA="cdrom";; + vc) IF="virtio"; MEDIA="cdrom";; + *) IF="ide"; MEDIA="cdrom";; esac -echo qemu-system-x86_64 -m 256 -drive file=${1},if=${IF},media=${MEDIA},boot=on -qemu-system-x86_64 -m 256 -drive file=${1},if=${IF},media=${MEDIA},boot=on +echo qemu-system-x86_64 -m 256 -drive file=${1},if=${IF},media=${MEDIA} +qemu-system-x86_64 -m 256 -drive file=${1},if=${IF},media=${MEDIA} -- 1.7.11

2 5

[arch-releng] [RFC] [PATCH] [configs/releng] Remove [core] ISO generation
by Gerardo Exequiel Pozzi 23 Jul '12

23 Jul '12

Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> --- README | 29 ++++---- configs/releng/aitab | 4 + configs/releng/aitab.core | 6 -- configs/releng/aitab.netinstall | 4 - configs/releng/build.sh | 146 +++++-------------------------------- configs/releng/core.exclude.i686 | 4 - configs/releng/core.exclude.x86_64 | 4 - 7 files changed, 38 insertions(+), 159 deletions(-) create mode 100644 configs/releng/aitab delete mode 100644 configs/releng/aitab.core delete mode 100644 configs/releng/aitab.netinstall delete mode 100644 configs/releng/core.exclude.i686 delete mode 100644 configs/releng/core.exclude.x86_64 diff --git a/README b/README index dd22eb0..8778a25 100644 --- a/README +++ b/README @@ -165,13 +165,12 @@ if nothing is specified on command line. *** Transfer ISO image to target medium (configs/releng) -ISO images names consist of: archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso +ISO images names consist of: archlinux-<YYYY>.<MM>.<DD>-<ARCH>.iso Where: <YYYY> Year <MM> Month <DD> Day - <TYPE> netinstall | core <ARCH> i686 | x86_64 | dual(*) (*) "dual" includes both i686 and x86_64 architectures. @@ -190,7 +189,7 @@ Nomeclature: 1) Write it directly using your favorite recording program. -# cdrecord dev=,<T>,<L> -dao archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso +# cdrecord dev=,<T>,<L> -dao archlinux-<YYYY>.<MM>.<DD>-<ARCH>.iso ** To -> USB Flash Drive (USB-key) / Memory card (SD) / @@ -209,10 +208,10 @@ Nomeclature: (example: /dev/sdx1) <MNT-TARGET-N>: Mount point path where <DEV-TARGET-N> is mounted (example: /mnt/sdx/1) -<ISO-SOURCE>: Path to the ISO file archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso - (example: ~/archlinux-2012.04.16-netinstall-x86_64.iso) +<ISO-SOURCE>: Path to the ISO file archlinux-<YYYY>.<MM>.<DD>-<ARCH>.iso + (example: ~/archlinux-2012.07.22-x86_64.iso) <FS-LABEL>: Represents the filesystem label of the <ISO-SOURCE> - (example: ARCH_201204 [for all ~/archlinux-2012.04.*.iso]) + (example: ARCH_201207 [for all ~/archlinux-2012.07.*.iso]) * PC-BIOS (MBR): @@ -288,19 +287,19 @@ Note: Using here a GPT partition mode as example, but MBR should also works ** ISO in loopback mode. Note: Described method is for using with GRUB2. - GRUB2 is installed on target media and archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso + GRUB2 is installed on target media and archlinux-<YYYY>.<MM>.<DD>-<ARCH>.iso is at path <TARGET-PATH> on disk <D> and partition , where filesystem is labeled as <TARGET-FS-LABEL>. menuentry "Arch Linux (x86_64)" { - set isofile="/<TARGET-PATH>/archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso" + set isofile="/<TARGET-PATH>/archlinux-<YYYY>.<MM>.<DD>-<ARCH>.iso" loopback loop (hd<D>,)$isofile linux (loop)/arch/boot/x86_64/vmlinuz archisolabel=<FS-LABEL> img_label=<TARGET-FS-LABEL> img_loop=$isofile initrd (loop)/arch/boot/x86_64/archiso.img } menuentry "Arch Linux (i686)" { - set isofile="/<TARGET-PATH>/archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso" + set isofile="/<TARGET-PATH>/archlinux-<YYYY>.<MM>.<DD>-<ARCH>.iso" loopback loop (hd<D>,)$isofile linux (loop)/arch/boot/i686/vmlinuz archisolabel=<FS-LABEL> img_label=<TARGET-FS-LABEL> img_loop=$isofile initrd (loop)/arch/boot/i686/archiso.img @@ -311,7 +310,7 @@ menuentry "Arch Linux (i686)" { Note: Described method is for using with SYSLINUX. Anyway MEMDISK from SYSLINUX can work with other bootloaders. - SYSLINUX is installed on target media and archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso + SYSLINUX is installed on target media and archlinux-<YYYY>.<MM>.<DD>-<ARCH>.iso is at path <TARGET-PATH>. On 32-bit systems, is needed to pass vmalloc=nnM to the kernel, where nn is the size of the ISO image plus 64 MiB (or 128 MiB). @@ -319,12 +318,12 @@ Note: Described method is for using with SYSLINUX. Anyway MEMDISK from SYSLINUX LABEL arch_x64 LINUX memdisk - INITRD /<TARGET-PATH>/archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso + INITRD /<TARGET-PATH>/archlinux-<YYYY>.<MM>.<DD>-<ARCH>.iso APPEND iso LABEL arch_x32 LINUX memdisk - INITRD /<TARGET-PATH>/archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso + INITRD /<TARGET-PATH>/archlinux-<YYYY>.<MM>.<DD>-<ARCH>.iso APPEND iso @@ -378,13 +377,13 @@ methods can be used to serve the rest of live-medium. * NBD -Note: Adjust ARCH_201204 as needed. +Note: Adjust ARCH_201207 as needed. # cat << EOF > /tmp/nbd-server.conf [generic] [archiso] readonly = true - exportname = /dev/disk/by-label/ARCH_201204 + exportname = /dev/disk/by-label/ARCH_201207 EOF # nbd-server -C /tmp/nbd-server.conf @@ -494,6 +493,6 @@ used to build official images with much more things. # make -C archiso/archiso install * Build them! - # /usr/share/archiso/configs/releng/build.sh build all all + # /usr/share/archiso/configs/releng/build.sh build all Note: See build.sh -h for more options. diff --git a/configs/releng/aitab b/configs/releng/aitab new file mode 100644 index 0000000..ede4033 --- /dev/null +++ b/configs/releng/aitab @@ -0,0 +1,4 @@ +# <img> <mnt> <arch> <sfs_comp> <fs_type> <fs_size> +root-image / %ARCH% xz ext4 50% +usr-lib-modules /usr/lib/modules %ARCH% xz ext4 50% +usr-share /usr/share any xz ext4 50% diff --git a/configs/releng/aitab.core b/configs/releng/aitab.core deleted file mode 100644 index ffceeda..0000000 --- a/configs/releng/aitab.core +++ /dev/null @@ -1,6 +0,0 @@ -# <img> <mnt> <arch> <sfs_comp> <fs_type> <fs_size> -root-image / %ARCH% xz ext4 50% -usr-lib-modules /usr/lib/modules %ARCH% xz ext4 50% -usr-share /usr/share any xz ext4 50% -repo-core-%ARCH% /repo/core/%ARCH% %ARCH% xz none 0 -repo-core-any /repo/core/any any xz none 0 diff --git a/configs/releng/aitab.netinstall b/configs/releng/aitab.netinstall deleted file mode 100644 index ede4033..0000000 --- a/configs/releng/aitab.netinstall +++ /dev/null @@ -1,4 +0,0 @@ -# <img> <mnt> <arch> <sfs_comp> <fs_type> <fs_size> -root-image / %ARCH% xz ext4 50% -usr-lib-modules /usr/lib/modules %ARCH% xz ext4 50% -usr-share /usr/share any xz ext4 50% diff --git a/configs/releng/build.sh b/configs/releng/build.sh index 62709ac..cdebdf9 100755 --- a/configs/releng/build.sh +++ b/configs/releng/build.sh @@ -174,51 +174,11 @@ make_usr_share() { fi } -# Make [core] repository, keep "any" pkgs in a separate fs (makes more "dual-iso" friendly) -make_core_repo() { - if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then - local _url _urls _pkg_name _dst _pkgs _cache_dir - mkdir -p ${work_dir}/repo-core-any - mkdir -p ${work_dir}/repo-core-${arch} - mkdir -p ${work_dir}/pacman.db/var/lib/pacman - pacman --config "${pacman_conf}" -Sy -r ${work_dir}/pacman.db - _pkgs=$(comm -2 -3 <(pacman --config "${pacman_conf}" -Sql -r ${work_dir}/pacman.db core | sort | sed 's@^@core/@') \ - <(grep -v ^# ${script_path}/core.exclude.${arch} | sort | sed 's@^@core/@')) - _urls=$(pacman --config "${pacman_conf}" -Sddp -r ${work_dir}/pacman.db ${_pkgs}) - pacman --config "${pacman_conf}" -Swdd -r ${work_dir}/pacman.db --noprogressbar --noconfirm ${_pkgs} - for _url in ${_urls}; do - _pkg_name=${_url##*/} - _dst=${work_dir}/repo-core-${arch}/${_pkg_name} - for _cache_dir in ${cache_dirs[@]}; do - if [[ -e "${_cache_dir}/${_pkg_name}" ]]; then - cp "${_cache_dir}/${_pkg_name}" ${_dst} - fi - done - # download the package signature - curl -sC - -f "${_url}.sig" > "${_dst}.sig" - repo-add -q ${work_dir}/repo-core-${arch}/core.db.tar.gz ${_dst} - # remove the signature file again as it is now included in the db file - rm -f "${_dst}.sig" - if [[ ${_pkg_name} == *any.pkg.tar* ]]; then - mv ${_dst} ${work_dir}/repo-core-any/${_pkg_name} - ln -sf ../any/${_pkg_name} ${_dst} - fi - done - # Remove old copy of db file - rm -f ${work_dir}/repo-core-${arch}/core.db.tar.gz.old - mkdir -p ${work_dir}/iso/${install_dir} - pacman --config "${pacman_conf}" -Sp -r ${work_dir}/pacman.db --print-format "%r/%n-%v" ${_pkgs} | sort > ${work_dir}/iso/${install_dir}/pkglist.repo-core.${arch}.txt - : > ${work_dir}/build.${FUNCNAME} - fi -} - # Process aitab -# args: $1 (core | netinstall) make_aitab() { - local _iso_type=${1} - if [[ ! -e ${work_dir}/build.${FUNCNAME}_${_iso_type} ]]; then - sed "s|%ARCH%|${arch}|g" ${script_path}/aitab.${_iso_type} > ${work_dir}/iso/${install_dir}/aitab - : > ${work_dir}/build.${FUNCNAME}_${_iso_type} + if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then + sed "s|%ARCH%|${arch}|g" ${script_path}/aitab > ${work_dir}/iso/${install_dir}/aitab + : > ${work_dir}/build.${FUNCNAME} fi } @@ -229,18 +189,14 @@ make_prepare() { } # Build ISO -# args: $1 (core | netinstall) make_iso() { - local _iso_type=${1} mkarchiso ${verbose} -w "${work_dir}" -C "${pacman_conf}" -D "${install_dir}" checksum - mkarchiso ${verbose} -w "${work_dir}" -C "${pacman_conf}" -D "${install_dir}" -L "${iso_label}" -o "${out_dir}" iso "${iso_name}-${iso_version}-${_iso_type}-${arch}.iso" + mkarchiso ${verbose} -w "${work_dir}" -C "${pacman_conf}" -D "${install_dir}" -L "${iso_label}" -o "${out_dir}" iso "${iso_name}-${iso_version}-${arch}.iso" } # Build dual-iso images from ${work_dir}/i686/iso and ${work_dir}/x86_64/iso -# args: $1 (core | netinstall) make_dual() { - local _iso_type=${1} - if [[ ! -e ${work_dir}/dual/build.${FUNCNAME}_${_iso_type} ]]; then + if [[ ! -e ${work_dir}/dual/build.${FUNCNAME} ]]; then if [[ ! -d ${work_dir}/i686/iso || ! -d ${work_dir}/x86_64/iso ]]; then echo "ERROR: i686 or x86_64 builds does not exist." _usage 1 @@ -258,29 +214,15 @@ make_dual() { cp -a -l -n ${_src_two} ${work_dir}/dual rm -f ${work_dir}/dual/iso/${install_dir}/aitab rm -f ${work_dir}/dual/iso/${install_dir}/boot/syslinux/*.cfg - if [[ ${_iso_type} == "core" ]]; then - if [[ ! -e ${work_dir}/dual/iso/${install_dir}/any/repo-core-any.sfs || - ! -e ${work_dir}/dual/iso/${install_dir}/i686/repo-core-i686.sfs || - ! -e ${work_dir}/dual/iso/${install_dir}/x86_64/repo-core-x86_64.sfs ]]; then - echo "ERROR: core_iso_single build is not found." - _usage 1 - fi - else - rm -f ${work_dir}/dual/iso/${install_dir}/any/repo-core-any.sfs - rm -f ${work_dir}/dual/iso/${install_dir}/i686/repo-core-i686.sfs - rm -f ${work_dir}/dual/iso/${install_dir}/x86_64/repo-core-x86_64.sfs - rm -f ${work_dir}/dual/iso/${install_dir}/pkglist.repo-core.i686.txt - rm -f ${work_dir}/dual/iso/${install_dir}/pkglist.repo-core.x86_64.txt - fi - paste -d"\n" <(sed "s|%ARCH%|i686|g" ${script_path}/aitab.${_iso_type}) \ - <(sed "s|%ARCH%|x86_64|g" ${script_path}/aitab.${_iso_type}) | uniq > ${work_dir}/dual/iso/${install_dir}/aitab + paste -d"\n" <(sed "s|%ARCH%|i686|g" ${script_path}/aitab) \ + <(sed "s|%ARCH%|x86_64|g" ${script_path}/aitab) | uniq > ${work_dir}/dual/iso/${install_dir}/aitab for _cfg in ${script_path}/syslinux.dual/*.cfg; do sed "s|%ARCHISO_LABEL%|${iso_label}|g; s|%INSTALL_DIR%|${install_dir}|g" ${_cfg} > ${work_dir}/dual/iso/${install_dir}/boot/syslinux/${_cfg##*/} done mkarchiso ${verbose} -w "${work_dir}/dual" -D "${install_dir}" checksum - mkarchiso ${verbose} -w "${work_dir}/dual" -D "${install_dir}" -L "${iso_label}" -o "${out_dir}" iso "${iso_name}-${iso_version}-${_iso_type}-dual.iso" - : > ${work_dir}/dual/build.${FUNCNAME}_${_iso_type} + mkarchiso ${verbose} -w "${work_dir}/dual" -D "${install_dir}" -L "${iso_label}" -o "${out_dir}" iso "${iso_name}-${iso_version}-dual.iso" + : > ${work_dir}/dual/build.${FUNCNAME} fi } @@ -351,8 +293,8 @@ _usage () echo " -h This help message" echo echo " Commands:" - echo " build <mode> <type>" - echo " Build selected .iso by <mode> and <type>" + echo " build <mode>" + echo " Build selected .iso by <mode>" echo " purge <mode>" echo " Clean working directory except iso/ directory of build <mode>" echo " clean <mode>" @@ -360,7 +302,6 @@ _usage () echo echo " Command options:" echo " <mode> Valid values 'single', 'dual' or 'all'" - echo " <type> Valid values 'netinstall', 'core' or 'all'" exit ${1} } @@ -421,14 +362,6 @@ if [[ $# -lt 2 ]]; then fi command_mode="${2}" -if [[ ${command_name} == "build" ]]; then - if [[ $# -lt 3 ]]; then - echo "No build type specified" - _usage 1 - fi -command_type="${3}" -fi - if [[ ${command_mode} == "all" && ${arch} != "x86_64" ]]; then echo "This mode <all> needs to be run on x86_64" _usage 1 @@ -444,58 +377,19 @@ case "${command_name}" in build) case "${command_mode}" in single) - case "${command_type}" in - netinstall) - make_common_single netinstall - ;; - core) - make_core_repo - make_common_single core - ;; - all) - make_common_single netinstall - make_core_repo - make_common_single core - ;; - *) - echo "Invalid build type '${command_type}'" - _usage 1 - ;; - esac + make_common_single ;; dual) - case "${command_type}" in - netinstall) - make_dual netinstall - ;; - core) - make_dual core - ;; - all) - make_dual netinstall - make_dual core - ;; - *) - echo "Invalid build type '${command_type}'" - _usage 1 - ;; - esac + make_dual ;; all) - case "${command_type}" in - netinstall|core|all) - $0 ${cmd_args} build single ${command_type} - $0 ${cmd_args} purge single - linux32 $0 ${cmd_args} build single ${command_type} - linux32 $0 ${cmd_args} purge single - $0 ${cmd_args} build dual ${command_type} - $0 ${cmd_args} purge dual - ;; - *) - echo "Invalid build type '${command_type}'" - _usage 1 - ;; - esac + $0 ${cmd_args} build single + $0 ${cmd_args} purge single + linux32 $0 ${cmd_args} build single + linux32 $0 ${cmd_args} purge single + $0 ${cmd_args} build dual + $0 ${cmd_args} purge dual + ;; ;; *) echo "Invalid build mode '${command_mode}'" diff --git a/configs/releng/core.exclude.i686 b/configs/releng/core.exclude.i686 deleted file mode 100644 index a04ceef..0000000 --- a/configs/releng/core.exclude.i686 +++ /dev/null @@ -1,4 +0,0 @@ -gcc-ada -gcc-fortran -gcc-go -gcc-objc diff --git a/configs/releng/core.exclude.x86_64 b/configs/releng/core.exclude.x86_64 deleted file mode 100644 index a04ceef..0000000 --- a/configs/releng/core.exclude.x86_64 +++ /dev/null @@ -1,4 +0,0 @@ -gcc-ada -gcc-fortran -gcc-go -gcc-objc -- 1.7.11.2

2 3

Re: [arch-releng] [arch-dev-public] draft for new isos
by Gerardo Exequiel Pozzi 20 Jul '12

20 Jul '12

On 07/17/2012 06:41 PM, Pierre Schmitz wrote: > Hi, > > we really need to write a news istem about new isos etc.. Here are some > points we should mention: > > * removed aif for now > * looking for aif contributors and/or maintainer (need to ask Dieter if > he likes to guide applicants or never wants to toch aif again -)) > * new arch install scripts > * keyring is initialized on bootup; signature verification is enabled > by default. keyring is copied to target system in pacstrap > * need community help with documentation > * only one single iso (for both arches, no core repo included) > * regular (can we agree on monthly here?) releases > * we should mention that the iso itself is signed and that it really > should be verified > > Anything I missed? Would anybody like to write up some actual text? :-) > > Greetings, > > Pierre > ** This is a list of end-user visible features/fixes since 2011.08.19 from "archiso side". Features: * COW persistent: COW files can be stored in any place (see cow_*= boot params) * New boot parm img_label= for ISO loopback boot method * /bootmnt is now at /run/archiso/bootmnt * Network boot (PXE) via HTTP and NFS with DNS support from initramfs * Syslinux menu for selecting boot method (HTTP/NFS/NBD) when PXE is used * Setting up a PXE from live-enviroment is now trivially since syslinux *.cfg reorder/unification. * KMS modules added to initramfs * checksum= option is performed only for SquashFS images * EFI boot support on CD-ROM via "El Torito" (very basic and trivial but functional) Instructions provided to make an "USB-key" EFI-ready from ISO, is documented on README. * README update with much more documentation. Fixes: * ISO loopback boot method (no more earlymodules=loop workaround needed) * Serial console not enabled in dual-isos at syslinux. * Updated needed parts to match current packages changes. ** From dev-user (who want to build ISOs yourself), there are lots of interesting changes and fixes see the git log for details since commit 61114497b219efa865ae2ecda414e23a689a66bd -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

2 2