[arch-releng] [RFC] Finalized work about install_dir
All this work is in my install_dir branch (based on experimental). Tested and works. http://github.com/djgera/archiso/compare/experimental...install_dir Today images sizes: (*dual build with -T split, otherwise core-dual is 725M and net-dual 355M): 666M archlinux-2010.10.21-core-dual.iso 357M archlinux-2010.10.21-core-i686.iso 374M archlinux-2010.10.21-core-x86_64.iso 297M archlinux-2010.10.21-netinstall-dual.iso 176M archlinux-2010.10.21-netinstall-i686.iso 185M archlinux-2010.10.21-netinstall-x86_64.iso
-D
Am 21.10.2010 05:38, schrieb Gerardo Exequiel Pozzi:
-D
allow to select install directory on target media defaults to "arch". There is a new %INSTALL_DIR% macro for syslinux.cfg.
This is how ISO will look now: /syslinux only syslinux related files (syslinux.cfg, *.c32, etc) /arch/ isomounts + *.sqfs images /arch/boot/ Linux + initramfs + Memtest86+ + other files for early boot stage
Signed-off-by: Gerardo Exequiel Pozzi
Why don't we unify this layout with the -dual layout and move architecture-specific files to /arch/${arch} and /arch/boot/${arch}?
On 10/21/2010 04:06 AM, Thomas Bächler wrote:
Am 21.10.2010 05:38, schrieb Gerardo Exequiel Pozzi:
-D
allow to select install directory on target media defaults to "arch". There is a new %INSTALL_DIR% macro for syslinux.cfg.
This is how ISO will look now: /syslinux only syslinux related files (syslinux.cfg, *.c32, etc) /arch/ isomounts + *.sqfs images /arch/boot/ Linux + initramfs + Memtest86+ + other files for early boot stage
Signed-off-by: Gerardo Exequiel Pozzi
Why don't we unify this layout with the -dual layout and move architecture-specific files to /arch/${arch} and /arch/boot/${arch}?
Yes thats is my idea, I asked this here: http://mailman.archlinux.org/pipermail/arch-releng/2010-October/001255.html I can work on this over my install_dir branch. -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
Am 21.10.2010 17:29, schrieb Gerardo Exequiel Pozzi:
Why don't we unify this layout with the -dual layout and move architecture-specific files to /arch/${arch} and /arch/boot/${arch}?
Yes thats is my idea, I asked this here: http://mailman.archlinux.org/pipermail/arch-releng/2010-October/001255.html
I can work on this over my install_dir branch.
Oh, seems I didn't respond. I say go for it, it makes the merging in archiso2dual much easier.
This is how ISO will look now:
/syslinux only syslinux related files (syslinux.cfg, *.c32, etc)
/arch/ isomounts + *.sqfs images
/arch/boot/ Linux + initramfs + Memtest86+ + other files for early boot stage
Signed-off-by: Gerardo Exequiel Pozzi
Am 21.10.2010 05:38, schrieb Gerardo Exequiel Pozzi:
This is how ISO will look now: /syslinux only syslinux related files (syslinux.cfg, *.c32, etc) /arch/ isomounts + *.sqfs images /arch/boot/ Linux + initramfs + Memtest86+ + other files for early boot stage
Signed-off-by: Gerardo Exequiel Pozzi
While all this is looking good, we might be able to contain it more in /arch. In principle, syslinux now has a 'cd' call to change the 'current directory'. /syslinux could then only contain isolinux.cfg and a syslinux.cfg file (and maybe a few .c32) that changes the directory to /arch/boot/syslinux/ and loads syslinux.cfg from there. On the syslinux command line, this is easy: cd.c32 /arch/boot/syslinux config.c32 syslinux.cfg In a config file, I don't know if it'll work, but we'll see. Maybe we need to script it in lua, as I know of no way to call two .c32 files in a row. This way (if I can figure out how it works), it would be possible to dump /boot completely and only copy /arch when switching to a different bootloader.
This is how ISO will look now:
/syslinux only syslinux related files (syslinux.cfg, *.c32, etc)
/arch/ isomounts
/arch/any *.sqfs only on -T full or -T split
/arch/i686 *.sqfs
/arch/x86_64 *.sqfs
/arch/boot Memtest86+ + other files for early boot stage
/arch/boot/i686 Linux + initramfs
/arch/boot/x86_64 Linux + initramfs
Signed-off-by: Gerardo Exequiel Pozzi
participants (2)
-
Gerardo Exequiel Pozzi
-
Thomas Bächler