- Arch-releng - lists.archlinux.org

[arch-releng] [PATCH] Enable network by default
by Pierre Schmitz 29 Jul '12

29 Jul '12

* add the network daemon to rc.conf * configure dhcpd to background immediatly so we don't timeout if network is not up yet Signed-off-by: Pierre Schmitz <pierre(a)archlinux.de> --- This default should make life easier for most people as we can assume dhcp is available in most networks. We should document though that this can be disabled by "rc.d stop network" or better setup rc.conf and restart the network daemon. configs/releng/root-image/etc/conf.d/dhcpcd | 6 ++++++ configs/releng/root-image/etc/rc.conf | 2 +- 2 Dateien geändert, 7 Zeilen hinzugefügt(+), 1 Zeile entfernt(-) create mode 100644 configs/releng/root-image/etc/conf.d/dhcpcd diff --git a/configs/releng/root-image/etc/conf.d/dhcpcd b/configs/releng/root-image/etc/conf.d/dhcpcd new file mode 100644 index 0000000..76b56ff --- /dev/null +++ b/configs/releng/root-image/etc/conf.d/dhcpcd @@ -0,0 +1,6 @@ +# +# Arguments to be passed to the DHCP client daemon +# + +DHCPCD_ARGS="-qb" + diff --git a/configs/releng/root-image/etc/rc.conf b/configs/releng/root-image/etc/rc.conf index f97ec88..a2e6ebf 100644 --- a/configs/releng/root-image/etc/rc.conf +++ b/configs/releng/root-image/etc/rc.conf @@ -8,7 +8,7 @@ # For more details on rc.conf see rc.conf(5). # -DAEMONS=(syslog-ng haveged pacman-init) +DAEMONS=(syslog-ng network haveged pacman-init) # Storage # -- 1.7.11.3

2 1

[arch-releng] [PATCH] Add dist function to Makefile
by Pierre Schmitz 29 Jul '12

29 Jul '12

This dist function creates a tar archive of a tag. Signed-off-by: Pierre Schmitz <pierre(a)archlinux.de> --- archiso/Makefile | 8 +++++++- 1 Datei geändert, 7 Zeilen hinzugefügt(+), 1 Zeile entfernt(-) diff --git a/archiso/Makefile b/archiso/Makefile index 03f9a16..6a73d00 100644 --- a/archiso/Makefile +++ b/archiso/Makefile @@ -1,3 +1,5 @@ +V=1 + all: install: install-program install-hooks install-examples install-doc @@ -54,4 +56,8 @@ uninstall: rm -f $(DESTDIR)/usr/lib/initcpio/install/archiso_kms rm -rf $(DESTDIR)/usr/share/archiso/ -.PHONY: install install-program install-hooks install-examples install-doc uninstall +dist: + git archive --format=tar --prefix=archiso-$(V)/ v$(V) | gzip -9 > archiso-$(V).tar.gz + gpg --detach-sign --use-agent archiso-$(V).tar.gz + +.PHONY: install install-program install-hooks install-examples install-doc uninstall dist -- 1.7.11.3

2 1

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