Arch-releng November 2013

arch-releng@lists.archlinux.org

5 participants
5 discussions

[arch-releng] archiso with cowfile_size > 100
by Christian Hesse 20 Mar '14

20 Mar '14

Hello everybody, actually cowfile_size is limited to values smaller or equal to 100. That way you have to decide at iso build time what size your filesystems should have. I have added a feature to allow values bigger than 100: In this case the read only device is linearly assembled with a sparse file (we do not have to care about size on disk as no write go to this file), this device is used for read only device then. After chroot (or when the system has bootet up) you can grow your filesystem to the new size. Growing the filesystem in initramfs would be possible, but we would have to add userspace utilities (resize2fs, xfs_growfs, ...) there... The patch is attached. What do you think? -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Chris get my mail address: */=0;b=c[a++];) putchar(b-1/(/* gcc -o sig sig.c && ./sig */b/42*2-3)*42);}

3 20

[arch-releng] Arch iso packages; clonezilla?
by Jonathan Steel 04 Jan '14

04 Jan '14

Hi, I would like to propose including clonezilla [1][2] in the installation media. It provides an ncurses menu for backing up and restoring partitions/disks using partclone, which is already included (I maintain both). As well as being a small and useful tool, I have another motive for getting it added. Clonezilla currently offer live media iso files of Debian and Ubuntu-based operating systems running clonezilla. By including clonezilla in our installation media they are happy to add it as an alternative version, offering an Arch-based iso that you can run clonezilla on. Are there any objections to this? Thanks, [1] https://www.archlinux.org/packages/community/any/clonezilla/ [2] http://clonezilla.org -- Jonathan Steel Trusted User

4 5

[arch-releng] [PATCH] [archiso] Workaround broken BIOS for ISOLINUX
by Gerardo Exequiel Pozzi 28 Nov '13

28 Nov '13

Avoiding different issues like instant reboot or error messages. This ensure that isolinux.bin is located on the most low extent possible (LBA 34) just after boot.cat (LBA 33). Directory listing of /ISOLINUX/ d--------- 0 0 0 2048 Nov 25 2013 [ 21 02] . d--------- 0 0 0 2048 Nov 25 2013 [ 19 02] .. ---------- 0 0 0 2048 Nov 25 2013 [ 33 00] BOOT.CAT;1 ---------- 0 0 0 38912 Nov 25 2013 [ 34 00] ISOLINUX.BIN;1 More details at http://www.syslinux.org/archives/2013-November/021169.html Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> --- archiso/mkarchiso | 1 + 1 file changed, 1 insertion(+) diff --git a/archiso/mkarchiso b/archiso/mkarchiso index 9655167..434ca1f 100755 --- a/archiso/mkarchiso +++ b/archiso/mkarchiso @@ -409,6 +409,7 @@ command_iso () { -no-emul-boot -boot-load-size 4 -boot-info-table \ -isohybrid-mbr ${work_dir}/iso/isolinux/isohdpfx.bin \ ${_iso_efi_boot_args} \ + --sort-weight 1 isolinux/isolinux.bin \ -output "${out_dir}/${img_name}" \ "${work_dir}/iso/" _msg_info "Done! | $(ls -sh ${out_dir}/${img_name})" -- 1.8.4.2

2 7

Re: [arch-releng] Fix for unbooteable ISOLINUX on broken BIOS
by Gerardo Exequiel Pozzi 28 Nov '13

28 Nov '13

On 11/27/2013 01:29 PM, Tobias Powalowski wrote: > Am 26.11.2013 22:54, schrieb Gerardo Exequiel Pozzi: >> On 11/26/2013 12:17 PM, Thomas Bächler wrote: >>> Am 26.11.2013 16:15, schrieb Thomas Bächler: >>>> Am 26.11.2013 16:05, schrieb Gerardo Exequiel Pozzi: >>>>> The cause and bug is trivially fixed: >>>>> ---- >>>>> diff --git a/core/isolinux.asm b/core/isolinux.asm >>>>> index bd4e9556922d..c4db4133e274 100644 >>>>> --- a/core/isolinux.asm >>>>> +++ b/core/isolinux.asm >>>>> @@ -420,7 +420,7 @@ MaxLMA equ 384*1024 ; Reasonable limit (384K) >>>>> call getlinsec >>>>> pop eax >>>>> pop cx >>>>> - mov dx,cx >>>>> + movzx edx,cx >>>>> pop bp >>>>> pop bx >>>>> ---- >>>>> >>>>> @Tobias: Could you rebuild syslinux with patch [#2] included? Thanks! >>>> I don't think we rebuild the asm code in our syslinux package, as >>>> upstream doesn't recommend it. Instead, we only build the syslinux >>>> installer and use the shipped binaries. >>> Oh, it seems that was reverted. So this should work fine. >>> >>> >> Yes. Can be great if the new pkg goes to [core] before next 2013.12 ;) >> >> Thanks >> > Done > Gracias :) -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

1 0

[arch-releng] [arch-install-scripts] [PATCH] common: mount efivarfs if possible, but don't bail out if it fails
by Thomas Bächler 16 Nov '13

16 Nov '13

Installing EFI bootloaders during pacstrap is broken right now, as is installing manually in arch-chroot. Therefore, mount efivarfs if the host kernel supports it. --- common | 1 + 1 file changed, 1 insertion(+) diff --git a/common b/common index 950b452..2078b56 100644 --- a/common +++ b/common @@ -66,6 +66,7 @@ api_fs_mount() { { mountpoint -q "$1" || track_mount "$1" "$1" --bind; } && track_mount proc "$1/proc" -t proc -o nosuid,noexec,nodev && track_mount sys "$1/sys" -t sysfs -o nosuid,noexec,nodev && + { [[ -d "$1/sys/firmware/efi/efivars" ]] && track_mount efivarfs "$1/sys/firmware/efi/efivars" -t efivarfs -o nosuid,noexec,nodev || true; } && track_mount udev "$1/dev" -t devtmpfs -o mode=0755,nosuid && track_mount devpts "$1/dev/pts" -t devpts -o mode=0620,gid=5,nosuid,noexec && track_mount shm "$1/dev/shm" -t tmpfs -o mode=1777,nosuid,nodev && -- 1.8.4.2

2 9

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Arch-releng November 2013