- Arch-releng - lists.archlinux.org

Re: [arch-releng] A TODO draft for next installation media.
by Gerardo Exequiel Pozzi 11 Feb '10

11 Feb '10

On 02/06/2010 11:23 AM, Sven-Hendrik Haase wrote: > On 05.02.2010 06:50, Gerardo Exequiel Pozzi wrote: >> Hello >> >> I am writing a kind of draft of things that I think that should be >> kept in mind for the next release: >> >> * Release archiso (2010.02) with the current [core], the previous >> intent was for 2009.12. (I guess this will be the last release with >> mkinitcpio based on klibc) >> * Merge the all pending changes to archiso from Svenstaro [#1] >> * Merge the all pending changes to archiso from me [#2] >> * Make an updated aif package with latest fixes. >> * Make all four hybrid ISO images core-{i686,x86_64} and >> net-{i686,x86_64} (images for testing) >> * Update the very very old "archiso" package in extra at this point. >> * ISOs should be uploaded after KDE SC 4.4 hits extra to avoid mirror >> issues. >> * Any other things? Please add it. >> >> I recently builded an "archiso-2010.02" on i686 without any issues, >> boot fine on KVM in both modes (as disk and as cdrom). >> When all this is done, a branch ""kill-klibc"" can be created in >> archiso, for working with new mkinitcpio 0.6. (I made some testings >> here, with a trivial patch [#3] [#4]). >> Also a dual-arch ISO can be started for next archiso release. >> >> >> All comments are welcomed. Good luck! > > Good list! I agree to every point. Good :) > > So basically the only thing we have to do is wait until KDE 4.4 > releases since everything else is done? Maybe now wait for mkinitcpio-0.6 hit [core] (when I wrote this TODO, mkinitcpio was alpha, but the progress was fast in last days). > Is there an existing bug report on the dual architecture stuff? I think that dual, will be for next release, there is nothing finished for that. -- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D

1 0

[arch-releng] A TODO draft for next installation media.
by Gerardo Exequiel Pozzi 06 Feb '10

06 Feb '10

Hello I am writing a kind of draft of things that I think that should be kept in mind for the next release: * Release archiso (2010.02) with the current [core], the previous intent was for 2009.12. (I guess this will be the last release with mkinitcpio based on klibc) * Merge the all pending changes to archiso from Svenstaro [#1] * Merge the all pending changes to archiso from me [#2] * Make an updated aif package with latest fixes. * Make all four hybrid ISO images core-{i686,x86_64} and net-{i686,x86_64} (images for testing) * Update the very very old "archiso" package in extra at this point. * ISOs should be uploaded after KDE SC 4.4 hits extra to avoid mirror issues. * Any other things? Please add it. I recently builded an "archiso-2010.02" on i686 without any issues, boot fine on KVM in both modes (as disk and as cdrom). When all this is done, a branch ""kill-klibc"" can be created in archiso, for working with new mkinitcpio 0.6. (I made some testings here, with a trivial patch [#3] [#4]). Also a dual-arch ISO can be started for next archiso release. All comments are welcomed. Good luck! [#1] http://github.com/Svenstaro/archiso-lglive [#2] http://github.com/djgera/archiso/tree/djgera [#3] http://mailman.archlinux.org/pipermail/arch-releng/2010-February/000797.html [#4] http://github.com/djgera/archiso/tree/experimental -- Gerardo Exequiel Pozzi ( djgera ) http://www.djgera.com.ar KeyID: 0x1B8C330D Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D

2 2

Re: [arch-releng] [arch-dev-public] LTS install ISOs (was: makechrootpkg without aufs2)
by Dieter Plaetinck 24 Jan '10

24 Jan '10

On Sun, 24 Jan 2010 13:07:28 +0200 Ionut Biru <biru.ionut(a)gmail.com> wrote: > On 01/24/2010 09:55 AM, Aaron Griffin wrote: > > Hmmm. LTS install ISOs is an interesting idea, but not sure how > > people feel about that. I mean, the kernel for the install ISO is > > just the running kernel. You can still install the LTS kernel from > > a non-LTS ISO. > > > > Does anyone have a strong opinion on this? > > i don't see any reason to have that. > what's the purpose of the LTS kernel again? it's basically to make kernel update cycles of your system longer, right? so instead of getting a new major version every 3 months, you jump from LTS to LTS. I can see why some people want that on their installed box [and hence the possibility to install it using any installation medium]. our goal with the installation media (we're failing at that goal right now), is to have a set of media for each new kernel release. why? optimal hardware support. so the question is simple: do LTS kernels get driver updates like the normal kernels do? but even if they do, they probably run behind on filesystems support and such. so i do not see any advantages for installation media running an LTS kernel. Dieter

1 0

[arch-releng] new release images?
by Dieter Plaetinck 30 Nov '09

30 Nov '09

Hi guys, how do you feel about working again on some new images? for the upcoming 2.6.32 kernel? I personally wouldn't like to invest as much time as the previous times, but for 2009.08 Gerhard and i have done a lot of "infrastructure" & "process" work of which we should now feel the benefits: building new images should be smoother. So I would suggest to start working on new images in which we fix the biggest issues from last time, and add some useful features (such as http://bugs.archlinux.org/task/13213 and/or http://bugs.archlinux.org/task/10753) I've been to build.archlinux.org again to check out the state of our chroots, but I wondered: can i safely upgrade all packages (including kernel stuff)? what's the state of archiso? did we do any manual modifications to scripts such as archiso? should I install archiso from git (master) or is there a new package? Maybe we should just put an archiso git checkout in /home/archiso because it will keep on getting improvements anyway. Anything else I'm forgetting before we can start to actually build images in the chroot? Also, Gerardo has been doing great work on our bugtracker and many nice patches for archiso, and he will gladly help us out. Dieter

3 3

[arch-releng] what should AIF depend on?
by Dieter Plaetinck 27 Nov '09

27 Nov '09

dieter@dieter-ws-a7n8x-arch ~ pacman -Si aif Depends On : bash pacman Optional Deps : markdown: to generate the html installation guide is this enough? should i include coreutils and grub? (requested @ http://bugs.archlinux.org/task/16205?project=6&status[0]= ) afaik there was some stuff "that is always assumed to be installed" such as packages in the base group. But i can't find back the info about that on the developerwiki.. Dieter

2 1

[arch-releng] [PATCH 13/13] Only lock the optical drive if mounted from this
by Gerardo Exequiel Pozzi 17 Nov '09

17 Nov '09

Check if FSTYPE is iso9660 or UDF, and only in this case look the optical drive. Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> --- archiso/hooks/archiso | 8 +++++--- 1 files changed, 5 insertions(+), 3 deletions(-) diff --git a/archiso/hooks/archiso b/archiso/hooks/archiso index cf13e3d..336a014 100644 --- a/archiso/hooks/archiso +++ b/archiso/hooks/archiso @@ -124,9 +124,11 @@ run_hook () # Bind our bootmnt dir into the live system _mnt_bind /bootmnt /bootmnt - if [ -d /proc/sys/dev/cdrom ]; then - echo 0 > /proc/sys/dev/cdrom/lock - echo 0 > /proc/sys/dev/cdrom/autoeject + if [ "${FSTYPE}" = "iso9660" -o "${FSTYPE}" = "udf" ]; then + if [ -d /proc/sys/dev/cdrom ]; then + echo 0 > /proc/sys/dev/cdrom/lock + echo 0 > /proc/sys/dev/cdrom/autoeject + fi fi if [ "${break}" = "y" ]; then -- 1.6.5.2

1 0

[arch-releng] [PATCH 12/12] Rename ramdisk_size parameter to tmpfs_size to avoid conflict
by Gerardo Exequiel Pozzi 17 Nov '09

17 Nov '09

Rename ramdisk_size parameter to tmpfs_size to avoid conflict with the kernel parameter that is for old ramdisk based blockdevs (/dev/ramN) and confusion to users. The kernel parameter ramdisk_size=N is in "N * k size", while tmpfs size=N is in "N * [ k | m | g ] byte size" or "in N% of RAM", like is used by default on archiso. This parameter is used only for tmpfs in size option. Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> --- archiso/hooks/archiso | 8 ++++---- configs/default/menu.lst | 2 +- configs/install-iso/boot-files/grub/menu.lst | 4 ++-- .../install-iso/boot-files/isolinux/isolinux.cfg | 4 ++-- configs/xfce4/overlay/boot/grub/menu.lst | 2 +- 5 files changed, 10 insertions(+), 10 deletions(-) diff --git a/archiso/hooks/archiso b/archiso/hooks/archiso index aeaded2..cf13e3d 100644 --- a/archiso/hooks/archiso +++ b/archiso/hooks/archiso @@ -46,8 +46,8 @@ run_hook () arch="$(uname -m)" fi - if [ "x${ramdisk_size}" = "x" ]; then - ramdisk_size="75%" + if [ "x${tmpfs_size}" = "x" ]; then + tmpfs_size="75%" fi if [ "x${isomounts}" != "x" ]; then @@ -56,8 +56,8 @@ run_hook () isomounts="/bootmnt/isomounts" fi - msg -n ":: Mounting tmpfs, size=${ramdisk_size}..." - mount -t tmpfs -o "size=${ramdisk_size}" tmpfs /tmpfs + msg -n ":: Mounting tmpfs, size=${tmpfs_size}..." + mount -t tmpfs -o "size=${tmpfs_size}" tmpfs /tmpfs msg "done." msg ":: Waiting for boot device..." diff --git a/configs/default/menu.lst b/configs/default/menu.lst index 0852720..8cad364 100644 --- a/configs/default/menu.lst +++ b/configs/default/menu.lst @@ -4,7 +4,7 @@ color light-blue/blue black/light-grey splashimage=/boot/splash.xpm.gz title Boot Arch Linux Live CD -kernel /boot/vmlinuz26 lang=en locale=en_US.UTF-8 ramdisk_size=75% +kernel /boot/vmlinuz26 lang=en locale=en_US.UTF-8 tmpfs_size=75% initrd /boot/archiso.img title Shutdown the Computer diff --git a/configs/install-iso/boot-files/grub/menu.lst b/configs/install-iso/boot-files/grub/menu.lst index 41a72f9..07bfd71 100644 --- a/configs/install-iso/boot-files/grub/menu.lst +++ b/configs/install-iso/boot-files/grub/menu.lst @@ -4,11 +4,11 @@ color light-blue/blue black/light-grey splashimage=/boot/splash.xpm.gz title Boot Arch Linux Live CD -kernel /boot/vmlinuz26 lang=en locale=en_US.UTF-8 archisolabel=XXX ramdisk_size=75% +kernel /boot/vmlinuz26 lang=en locale=en_US.UTF-8 archisolabel=XXX tmpfs_size=75% initrd /boot/archiso_pata.img title Boot Arch Linux Live CD [Legacy IDE, no SATA] -kernel /boot/vmlinuz26 lang=en locale=en_US.UTF-8 archisolabel=XXX ramdisk_size=75% +kernel /boot/vmlinuz26 lang=en locale=en_US.UTF-8 archisolabel=XXX tmpfs_size=75% initrd /boot/archiso_ide.img title Release Notes diff --git a/configs/install-iso/boot-files/isolinux/isolinux.cfg b/configs/install-iso/boot-files/isolinux/isolinux.cfg index 793271e..5686af3 100644 --- a/configs/install-iso/boot-files/isolinux/isolinux.cfg +++ b/configs/install-iso/boot-files/isolinux/isolinux.cfg @@ -8,11 +8,11 @@ DEFAULT arch LABEL arch KERNEL /boot/vmlinuz26 -APPEND lang=en locale=en_US.UTF-8 archisolabel=XXX ramdisk_size=75% initrd=/boot/archiso_pata.img +APPEND lang=en locale=en_US.UTF-8 archisolabel=XXX tmpfs_size=75% initrd=/boot/archiso_pata.img LABEL archide KERNEL /boot/vmlinuz26 -APPEND lang=en locale=en_US.UTF-8 archisolabel=XXX ramdisk_size=75% initrd=/boot/archiso_ide.img +APPEND lang=en locale=en_US.UTF-8 archisolabel=XXX tmpfs_size=75% initrd=/boot/archiso_ide.img LABEL memtest KERNEL /boot/memtest diff --git a/configs/xfce4/overlay/boot/grub/menu.lst b/configs/xfce4/overlay/boot/grub/menu.lst index 4cd24a3..a9c964a 100644 --- a/configs/xfce4/overlay/boot/grub/menu.lst +++ b/configs/xfce4/overlay/boot/grub/menu.lst @@ -4,7 +4,7 @@ color light-blue/blue black/light-grey splashimage=/boot/splash.xpm.gz title Boot Arch Linux Live CD -kernel /boot/vmlinuz26 lang=en locale=en_US.UTF-8 ramdisk_size=75% +kernel /boot/vmlinuz26 lang=en locale=en_US.UTF-8 tmpfs_size=75% initrd /boot/archiso.img title Tools... -- 1.6.5.2

1 0

[arch-releng] [PATCH 11/11] Add a default install-iso/overlay/etc/hosts with archiso alias
by Gerardo Exequiel Pozzi 11 Nov '09

11 Nov '09

With this add if some program is started and query about hostname, no annoying delay of ~10 seconds will occur. Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> --- configs/install-iso/overlay/etc/hosts | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-) create mode 100644 configs/install-iso/overlay/etc/hosts diff --git a/configs/install-iso/overlay/etc/hosts b/configs/install-iso/overlay/etc/hosts new file mode 100644 index 0000000..b6f25e3 --- /dev/null +++ b/configs/install-iso/overlay/etc/hosts @@ -0,0 +1,8 @@ +# +# /etc/hosts: static lookup table for host names +# + +#<ip-address> <hostname.domain.org> <hostname> +127.0.0.1 localhost.localdomain localhost archiso + +# End of file -- 1.6.5.2

1 0

[arch-releng] [PATCH] Avoid force/rebuild of squashfs images if already updated.
by Gerardo Exequiel Pozzi 10 Nov '09

10 Nov '09

Check if there are any modification of files/directories inside the target directory for squashfs image. Implements in some way this item in TODO: * Add 'needsupdate' function to check if a squashfs image in the iso dir is up to date, if so, skip it; else rebuild it. No more need for the -f flag Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> --- archiso/mkarchiso | 10 +++++----- 1 files changed, 5 insertions(+), 5 deletions(-) diff --git a/archiso/mkarchiso b/archiso/mkarchiso index b6d0f54..e71660e 100755 --- a/archiso/mkarchiso +++ b/archiso/mkarchiso @@ -159,13 +159,13 @@ _mksquash () { sqimg="${work_dir}/iso/$(basename ${1}).sqfs" echo "====> Generating SquashFS image for '${1}'" if [ -e "${sqimg}" ]; then - if [ "${FORCE}" = "y" ]; then - echo -n "Removing old SquashFS image..." + dirhaschanged=$(find ${1} -newer ${sqimg}) + if [ "${dirhaschanged}" != "" ]; then + echo "SquashFS image '${sqimg}' is not up to date, rebuilding..." rm "${sqimg}" - echo "done." else - echo "error: SquashFS image '${sqimg}' already exists, aborting." - exit 1 + echo "SquashFS image '${sqimg}' is up to date, skipping." + return fi fi -- 1.6.5.2

1 0

[arch-releng] [PATCH] Support custom isomounts in archiso hook.
by Gerardo Exequiel Pozzi 26 Oct '09

26 Oct '09

Implement this feature request: FS#16835 - isomounts file whithin archiso hook is inflexible Add an optional "isomounts" kernel command line parameter. In this way, can have differents combinations of kernels/ramdisk/filesystems.sqfs on the same media. Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> --- archiso/hooks/archiso | 13 ++++++++++--- 1 files changed, 10 insertions(+), 3 deletions(-) diff --git a/archiso/hooks/archiso b/archiso/hooks/archiso index 8ff23a3..aeaded2 100644 --- a/archiso/hooks/archiso +++ b/archiso/hooks/archiso @@ -49,6 +49,13 @@ run_hook () if [ "x${ramdisk_size}" = "x" ]; then ramdisk_size="75%" fi + + if [ "x${isomounts}" != "x" ]; then + isomounts="/bootmnt/${isomounts}" + else + isomounts="/bootmnt/isomounts" + fi + msg -n ":: Mounting tmpfs, size=${ramdisk_size}..." mount -t tmpfs -o "size=${ramdisk_size}" tmpfs /tmpfs msg "done." @@ -73,10 +80,10 @@ run_hook () _FSTYPE=$FSTYPE fi if mount -r -t "${_FSTYPE}" /dev/archiso /bootmnt >/dev/null 2>&1; then - if [ -e "/bootmnt/isomounts" ]; then + if [ -e "${isomounts}" ]; then echo "SUCCESS: Mounted archiso volume successfully." else - echo "ERROR: Mounting was successful, but the isomounts file does not exist." + echo "ERROR: Mounting was successful, but the ${isomounts} file does not exist." exit 1 fi else @@ -112,7 +119,7 @@ run_hook () elif [ "${type}" = "squashfs" ]; then _mnt_squashfs "/bootmnt/${img}" "${mountpoint}" fi - done < "/bootmnt/isomounts" + done < "${isomounts}" # Bind our bootmnt dir into the live system _mnt_bind /bootmnt /bootmnt -- 1.6.5.1

1 0