Arch-releng August 2013

arch-releng@lists.archlinux.org

5 participants
4 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] [archiso] syslinux 6 status
by Gerardo Exequiel Pozzi 22 Oct '13

22 Oct '13

Good news :) With syslinux-6.01-pre5 all things tested seems to work! Finally! Boot from: cdrom (ISOLINUX): OK disk (SYSLINUX [VFAT]): OK disk (SYSLINUX [EXT4]): OK disk (ISOHYBRID-MBR): OK network (PXELINUX): OK Also tested, all other menu items, reboot, hdt, memtest, etc... Tests was made under qemu-1.5.1. PS: Since syslinux 6 supports EFI, maybe in a future (2013.08 or 2013.09), if all things work, I am going to replace gummiboot with syslinux. -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

6 13

[arch-releng] Release ISO size regressions.
by Kyle Sanderson 22 Aug '13

22 Aug '13

I may be nit-picking, but I used to be able to install (or run Arch linux) from my trusty 512MB pen drive. The images that were shipped included both i686 and amd64, and if I can remember correctly, were about 450MB in size (multilib, single architecture they were around 220MB). I have no idea how old the image is now, but it's on my recovery usb drive. The new media requirements are now 526.0MB, which sadly means I can't successfully dd a new copy of Arch Linux to my faithful USB drive. While this is a very serious regression to me, maybe there's a very good reason a lot more packages are part of the installation media? This was Task 36582 on the bug tracker; apparently the mailing list is a better place to discuss package inclusion? Unfortunately the archive doesn't provide much in style, hopefully this is alright. Thanks, Kyle.

1 0

Re: [arch-releng] [arch-general] mkarchiso operates poorly with new glibc-2.18 built without pt_chown
by Thomas Bächler 17 Aug '13

17 Aug '13

Am 15.08.2013 18:00, schrieb Vadim Ushakov: > mkarchiso init executes command mount -t devpts devpts > ${work_dir}/root-image/dev/pts > Executing that command seems to drop mount options of /dev/pts, now we > have both devpts mount points have the same options: > vadim@aquila:~$ mount -t devpts First, this seems like a kernel bug. The old mount point should not be changed in this case - if they necessarily must have the same option, the new mount point should get the options of the existing one. One should either use a --bind mount call or use the 'newinstance' option. The latter brings a few small issues, but those can be worked around.

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Arch-releng August 2013