- Arch-releng - lists.archlinux.org

[arch-releng] Linux-lts
by Mr Green 25 Apr '12

25 Apr '12

Hi, Thinking of creating an iso based on linux-lts kernel and am thinking about the best way to do it. Only way I can think of is building base then adding lts kernel and removing linux [stock kernel] Or create a new base-lts pkgbuild ? MrG

4 5

[arch-releng] [RFC] [PATCH] [archiso] README: add: alternative boot methods
by Gerardo Exequiel Pozzi 19 Apr '12

19 Apr '12

Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> --- README | 114 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 114 insertions(+) diff --git a/README b/README index 5f1d253..a59d524 100644 --- a/README +++ b/README @@ -16,6 +16,13 @@ INDEX * PC-BIOS (MBR) * PC-BIOS (ISOHYBRID-MBR) * PC-EFI (GPT) [x86_64 only] +* Alternative boot methods (configs/releng) + * ISO in loopback mode + * ISO in memdisk mode + * Network booting (PXE) [first stage] + * DHCP + TFTP + * DHCP + HTTP + * HTTP/NFS/NBD [second stage] * Build requirements * Image types generated by mkarchiso. * File format for aitab. @@ -273,6 +280,113 @@ Note: Using here a GPT partition mode as example, but MBR should also works +*** Alternative boot methods (configs/releng) + +** ISO in loopback mode. + +Note: Described method is for using with GRUB2. + GRUB2 is installed on target media and archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso + is at path <TARGET-PATH> on disk <D> and partition , + where filesystem is labeled as <TARGET-FS-LABEL>. + +menuentry "Arch Linux (x86_64)" { + set isofile="/<TARGET-PATH>/archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso" + loopback loop (hd<D>,)$isofile + linux (loop)/arch/boot/x86_64/vmlinuz archisolabel=<FS-LABEL> img_label=<TARGET-FS-LABEL> img_loop=$isofile + initrd (loop)/arch/boot/x86_64/archiso.img +} + +menuentry "Arch Linux (i686)" { + set isofile="/<TARGET-PATH>/archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso" + loopback loop (hd<D>,)$isofile + linux (loop)/arch/boot/i686/vmlinuz archisolabel=<FS-LABEL> img_label=<TARGET-FS-LABEL> img_loop=$isofile + initrd (loop)/arch/boot/i686/archiso.img +} + + +** ISO in memdisk mode. + +Note: Described method is for using with SYSLINUX. Anyway MEMDISK from SYSLINUX can work + with other bootloaders. + SYSLINUX is installed on target media and archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso + is at path <TARGET-PATH>. + On 32-bit systems, is needed to pass vmalloc=nnM to the kernel, where nn is the size + of the ISO image plus 64 MiB (or 128 MiB). + + +LABEL arch_x64 + LINUX memdisk + INITRD /<TARGET-PATH>/archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso + APPEND iso + +LABEL arch_x32 + LINUX memdisk + INITRD /<TARGET-PATH>/archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso + APPEND iso + + +** Network booting (PXE). + +All ISOs are ready to act as PXE server, some manual steps are needed +to setup desired PXE boot mode. +Alternativelly is possible to use an already PXE server following the same logic. +Note: Setup network first, adjust IP adresses, and respect all slashes "/". + +First stage is for loading kernel and initramfs via PXE, two methods described here: + +* DHCP + TFTP + +Note: All NIC firmwares should support this. + +# dnsmasq --port=0 \ + --enable-tftp \ + --tftp-root=/run/archiso/bootmnt \ + --dhcp-range=192.168.0.2,192.168.0.254,86400 \ + --dhcp-boot=/arch/boot/syslinux/gpxelinux.0 \ + --dhcp-option-force=209,boot/syslinux/archiso.cfg \ + --dhcp-option-force=210,/arch/ + +* DHCP + HTTP + +Note: Not all NIC firmware supports HTTP and DNS (if domain name is used). + At least this works with iPXE and gPXE. + +# dnsmasq --port=0 \ + --dhcp-range=192.168.0.2,192.168.0.254,86400 \ + --dhcp-boot=http://192.168.0.7/arch/boot/syslinux/gpxelinux.0 \ + --dhcp-option-force=209,boot/syslinux/archiso.cfg \ + --dhcp-option-force=210,http://192.168.0.7/arch/ + + +Once kernel is started from PXE, SquashFS files and other misc files +inside "arch" directory must be loaded (second stage). One of the follow +methods can be used to serve the rest of live-medium. + +* HTTP + +# darkhttpd /run/archiso/bootmnt + + +* NFS + +# echo "/run/archiso/bootmnt 192.168.0.*(ro,no_subtree_check,no_root_squash)" >> /etc/exports +# rc.d start rpcbind nfs-common nfs-server + + +* NBD + +Note: Adjust ARCH_201204 as needed. + +# cat << EOF > /tmp/nbd-server.conf +[generic] +[archiso] + readonly = true + exportname = /dev/disk/by-label/ARCH_201204 +EOF +# nbd-server -C /tmp/nbd-server.conf + + + *** Build requirements ** For mkarchiso script needs these packages (build host): -- 1.7.9.6

3 4

[arch-releng] [DRAFT] End-User visible changes for ISOs since 2011.08.19
by Gerardo Exequiel Pozzi 19 Apr '12

19 Apr '12

** This is a list of end-user visible features/fixes since 2011.08.19 from "archiso side". Features: * COW persistent: COW files can be stored in any place (see cow_*= boot params) * New boot parm img_label= for ISO loopback boot method * /bootmnt is now at /run/archiso/bootmnt * Network boot (PXE) via HTTP and NFS with DNS support from initramfs * Syslinux menu for selecting boot method (HTTP/NFS/NBD) when PXE is used * Setting up a PXE from live-enviroment is now trivially since syslinux *.cfg reorder/unification. * KMS modules added to initramfs * checksum= option is performed only for SquashFS images * EFI boot support on CD-ROM via "El Torito" (very basic and trivial but functional) Instructions provided to make an "USB-key" EFI-ready from ISO, is documented on README. * README update with much more documentation. Fixes: * ISO loopback boot method (no more earlymodules=loop workaround needed) * Serial console not enabled in dual-isos at syslinux. * Updated needed parts to match current packages changes. ** From dev-user (who want to build ISOs yourself), there are lots of interesting changes and fixes see the git log for details since commit 61114497b219efa865ae2ecda414e23a689a66bd :) -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

2 2

[arch-releng] [RFC] [PATCH] [archiso] README: add: Transfer ISO file to target medium
by Gerardo Exequiel Pozzi 19 Apr '12

19 Apr '12

Please review, since my english is not the best. Thanks. (Otherwise I will merge in about one week) Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> --- README | 115 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) diff --git a/README b/README index 5df3128..f5577bb 100644 --- a/README +++ b/README @@ -10,6 +10,7 @@ INDEX * hooks/archiso_loop_mnt * Boot parameters (only for configs/releng) * etc/rc.conf +* Transfer ISO file to target medium (configs/releng) * Build requirements * Image types generated by mkarchiso. * File format for aitab. @@ -147,6 +148,120 @@ if nothing is specified on command line. +*** Transfer ISO image to target medium (configs/releng) + +ISO images names consist of: archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso + +Where: + <YYYY> Year + <MM> Month + <DD> Day + <TYPE> netinstall | core + <ARCH> i686 | x86_64 | dual(*) + +(*) "dual" includes both i686 and x86_64 architectures. + + +** To -> CD / DVD / BD +Note: All ISO images are booteable on a PC-BIOS via "El Torito" in no-emulation mode, + All x86_64 ISO images are booteable on a PC-EFI via "El Torito" in no-emulation mode. + +Nomeclature: + scsibus number + <T> target number + <L> lun number + (Note: see cdrecord -scanbus, for these numbers) + + +1) Write it directly using your favorite recording program. +# cdrecord dev=,<T>,<L> -dao archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso + + +** To -> USB Flash Drive (USB-key) / Memory card (SD) / + Hard-Disk Drive (HDD) / Solid-State Drive (SSD) + +Note: These steps are the general workflow, you can skip some of them, + using another filesystem if your bootloader supports it, + or installing to another directory than "arch/". + Just ensure that main boot params options (archisolabel= and + archisobasedir=) are set correctly according to your setup. + +Nomeclature: +<DEV-TARGET>: Device node of the drive where ISO contents should be copied + (example: /dev/sdx) +<DEV-TARGET-N>: Device node of the partition on <DEV-TARGET> + (example: /dev/sdx1) +<MNT-TARGET-N>: Mount point path where <DEV-TARGET-N> is mounted + (example: /mnt/sdx/1) +<ISO-SOURCE>: Path to the ISO file archlinux-<YYYY>.<MM>.<DD>-<TYPE>-<ARCH>.iso + (example: ~/archlinux-2012.04.16-netinstall-x86_64.iso) +<FS-LABEL>: Represents the filesystem label of the <ISO-SOURCE> + (example: ARCH_201204 [for all ~/archlinux-2012.04.*.iso]) + + +* PC-BIOS (MBR): + +1) Create one partition entry in MBR (of type "b" for FAT32 or "83" for EXTFS) + and mark it as "active" (booteable). +# fdisk <DEV-TARGET> + +2) Create a FAT32 or EXTFS filesystem on such partition and setup a label. +# mkfs.vfat -F 32 -n <FS-LABEL> <DEV-TARGET-N> +# mkfs.ext2 -L <FS-LABEL> <DEV-TARGET-N> + +3) Mount target filesystem. +# mount <DEV-TARGET-N> <MNT-TARGET-N> + +4) Extract ISO image on target filesystem. +# bsdtar -x --exclude=isolinux/ --exclude=EFI/ -f <ISO-SOURCE> -C <MNT-TARGET-N> + +5) Install syslinux bootloader on target filesystem. +# extlinux -i <MNT-TARGET-N>/arch/boot/syslinux + +6) Unmount target filesystem. +# umount <MNT-TARGET-N> + +7) Install syslinux MBR boot code on target drive. +# dd bs=440 count=1 conv=notrunc if=/usr/lib/syslinux/mbr.bin of=<DEV-TARGET> + + +* PC-BIOS (ISOHYBRID-MBR): + +This method is the most easily, quick and dirty, +but is the most limited if you want to use your target medium for other purposes. + +1) Dump ISO file to target medium. +# dd if=<ISO-SOURCE> of=<DEV-TARGET> + + +* PC-EFI (GPT) [x86_64 only] + +Note: Using here a GPT partition mode, but MBR should also work. + Optionally you can use your favorite EFI boot manager instead of an efi-shell+startup.nsh. + +1) Create one partition entry in GPT (of type "ef00") +# gdisk <DEV-TARGET> + +2) Create a FAT32 filesystem on such partition and setup a label. +# mkfs.vfat -F 32 -n <FS-LABEL> <DEV-TARGET-N> + +3) Mount target filesystem. +# mount <DEV-TARGET-N> <MNT-TARGET-N> + +4) Extract ISO image on target filesystem. +# bsdtar -x --exclude=isolinux/ --exclude=arch/boot/syslinux/ -f <ISO-SOURCE> -C <MNT-TARGET-N> + +5) Extract efiboot.img on EFI/ on target filesystem. +# mcopy -s -i <MNT-TARGET-N>/EFI/archiso/efiboot.img ::/EFI <MNT-TARGET-N>/ + +6) Remove uneeded efiboot.img +# rm <MNT-TARGET-N>/EFI/archiso/efiboot.img + +7) Unmount target filesystem. +# umount <MNT-TARGET-N> + + + *** Build requirements ** For mkarchiso script needs these packages (build host): -- 1.7.9.6

3 5

[arch-releng] [releng-scripts]: add dosfstools to releng-chroot-manager
by Gerardo Exequiel Pozzi 17 Apr '12

17 Apr '12

- extrapkgs="vim mc base-devel git svn cvs mkinitcpio libisoburn squashfs-tools devtools libui-sh" + extrapkgs="vim mc base-devel git svn cvs mkinitcpio libisoburn squashfs-tools dosfstools devtools libui-sh" otherwise x86_64 isos does not build. -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

3 5

[arch-releng] can archiso automatically yield a list of all packages on the iso?
by Dieter Plaetinck 12 Apr '12

12 Apr '12

Similar to the package lists on release wikipages ( https://wiki.archlinux.org/index.php/DeveloperWiki:2011.08.19#Package_versi… and https://wiki.archlinux.org/index.php/DeveloperWiki:2011.08.19#Package_versi… ) (which I do manually until now) I would like package lists for all builds generated by archiso, automatically. * for "packages used to build live environment" and "packages included in core repo" * including which repo it comes from (i.e. something like testing/linux-3.3.1-1-i686.pkg.tar.xz) is this possible?

2 11

[arch-releng] Linux-3.3 now hits [core], enable or not EFI on ISOs?
by Gerardo Exequiel Pozzi 11 Apr '12

11 Apr '12

Hello I want to get a "yes" or "no" about pushing my EFI patch [#1] in archiso that enables EFI CD-ROM booting via "El Torito" method. At least from Thomas or Dieter, since I did not get feedback from other people than Keshav P R (Thanks you). Just for remember this patch just increses the size of all x86_64 isos in 20MiB. [#1] https://github.com/djgera/archiso/commit/e3531ebd91b458c02dbfc5a2225a8c5397… Thanks. -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

2 3

[arch-releng] aif profile for EFI/GPT with grub2, dm_crypt+lvm2 on SSD, archiso EFI?
by Dieter Plaetinck 09 Apr '12

09 Apr '12

based on a script somebody made https://bbs.archlinux.org/viewtopic.php?id=129885 I wrote a profile for aif -p automatic: http://pastie.org/3737804 For creating the filesystems, i leverage the aif functionality (it supports everything needed). For partitioning and installing the bootloader I use 2 custom functions as aif currently does not support gpt/efi/grub2 The install seems to run fine, but since archiso currently boots through bios, i cannot make the efi entries with efibootmgr (no efi vars after loading efivars module). I saw the recent patches for archiso EFI support, what's the current status of that? Is there a method to create a usb stick similar as described here https://wiki.archlinux.org/index.php/USB_Installation_Media#Without_overwri… that is: an EFI-booting usb stick with archiso, which you can easily mount to put custom files on? If only I can figure out how to make the system boot, I think I'm pretty close :) Dieter

3 6

[arch-releng] archiso testbuilds built with testing repo enabled
by Dieter Plaetinck 09 Apr '12

09 Apr '12

http://releng.archlinux.org/isos/2012.04.08_15-47-01-testing/ the testbuild versions will now also have the suffix -testing if they were built with testing enabled. Dieter

2 6

[arch-releng] [RFCv4] [PATCH] [configs/releng] Add UEFI boot support via Linux >= 3.3 EFI boot stub on x86_64
by Gerardo Exequiel Pozzi 08 Apr '12

08 Apr '12

Makes an efiboot.img (FAT16) for "El Torito" (additional). Under an EFI-system, implies that this .ISO works only if is used as "CD-ROM/DVD-ROM" not in ISO-HYBRID-MBR mode. If you want, an EFI-ready USB-key, just unpack this "<ISO>/EFI/efiboot.img" (FAT16) to "<USB-key-FAT-formatted>/EFI" then copy "<ISO>/arch" and setup the filesystem label. An aditional EFI shell is provided with an startup script for automatic booting until EFI_STUB supports "linux.conf" to pass boot parms to kernel. Anyway I think that is a good idea to keep this shell, so can customize boot parms, or for doing other tasks on systems without an EFI-shell. RFCv1: Initial efiboot.img build with vmlinuz.efi (Linux with EFI_STUB enabled) and archiso.img (initramfs). RFCv2: Use an startup.nsh with EFI-Shell 2.0 (generated from build.sh) for automatic boot. RFCv3: Use and older EFI-Shell 1.0 instead of 2.0, since not all UEFI-systems are compatible with 2.3+ specs. RFCv4: The script "startup.nsh" improved by Keshav P R, using a for-loop (see notes below from original commit), now that has more than 1-line, I moved it to an independent file and is parsed by build.sh. ---- About startup.nsh: Author: Keshav P R <the.ridikulus.rat(a)gmail.com> Date: Thu Apr 5 10:33:20 2012 +0530 [configs/releng] Search in all existing UEFI FS mountpoints for archiso efistub kernel file There is no guarantee that the efistub kernel will always be in fs0: (similar to the case inside linux OS where the sda, sdb confusion exists, hence the need for UUIDs), especially when USB (instead os CD/ISO) is used for booting. Hence loop through all possible fs mountpoints (in UEFI) in startup.nsh and try to launch the first mountpoint that contains the archiso files. Cd's into the fs%m:\EFI\archiso directory also may remove future issues with efistub's linux.conf where the efistub might have problems identifying the directory from which the kernel was launched. Also add an helpful echo message showing the user the UEFI PATH to the archiso kernel file being launched by startup.nsh . Hopefully this should work in both CD and USB. Tested in Tianocore UDK/EDK2 DuetPkg X64 UEFI 2.3.1 firmware with EdkShellBinPkg's Shell. ---- Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> --- README | 3 +++ configs/releng/build.sh | 38 +++++++++++++++++++++++++++ configs/releng/efiboot/EFI/boot/startup.nsh | 10 +++++++ 3 files changed, 51 insertions(+) create mode 100644 configs/releng/efiboot/EFI/boot/startup.nsh diff --git a/README b/README index 57c87e3..711e51d 100644 --- a/README +++ b/README @@ -153,6 +153,9 @@ if nothing is specified on command line. + squashfs-tools for mksquashfs + libisoburn for xorriso +** For configs/releng build.sh needs theses packages (build host): + + dosfstools for mkfs.vfat + ** For these hooks needs these packages (on target root-image) * archiso + (none) diff --git a/configs/releng/build.sh b/configs/releng/build.sh index 2faf210..7cffeaf 100755 --- a/configs/releng/build.sh +++ b/configs/releng/build.sh @@ -58,6 +58,43 @@ make_boot() { fi } +# Prepare EFI "El Torito" boot image (using Linux >= 3.3 EFI boot stub) +make_boot_efi() { + if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then + if [[ ${arch} == "x86_64" ]]; then + mkdir -p ${work_dir}/iso/EFI/archiso + dd of=${work_dir}/iso/EFI/archiso/efiboot.img bs=1 seek=20M count=0 + mkfs.vfat ${work_dir}/iso/EFI/archiso/efiboot.img + + mkdir -p ${work_dir}/efiboot + mount ${work_dir}/iso/EFI/archiso/efiboot.img ${work_dir}/efiboot + + mkdir -p ${work_dir}/efiboot/EFI/archiso + cp ${work_dir}/iso/${install_dir}/boot/x86_64/vmlinuz ${work_dir}/efiboot/EFI/archiso/vmlinuz.efi + cp ${work_dir}/iso/${install_dir}/boot/x86_64/archiso.img ${work_dir}/efiboot/EFI/archiso/archiso.img + + # There are plans to support command line options via a config file (not yet in linux-3.3) + #cp ${work_dir}/iso/${install_dir}/boot/x86_64/vmlinuz ${work_dir}/efiboot/EFI/boot/bootx64.efi + #cp ${work_dir}/iso/${install_dir}/boot/x86_64/archiso.img ${work_dir}/efiboot/EFI/boot/linux.img + #echo "archisolabel=${iso_label} initrd=\EFI\boot\linux.img" | iconv -f ascii -t ucs2 > ${work_dir}/iso/EFI/boot/linux.conf + + # For now, provide an EFI-shell until 'linux.conf' hits mainline. + mkdir -p ${work_dir}/efiboot/EFI/boot + # EFI Shell 2.0 for UEFI 2.3+ ( http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=UEFI_Shell ) + #wget -O ${work_dir}/efiboot/EFI/boot/bootx64.efi https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/ShellBinPkg/UefiSh… + # EFI Shell 1.0 for non UEFI 2.3+ ( http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Efi-shell ) + wget -O ${work_dir}/efiboot/EFI/boot/bootx64.efi https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/EdkShellBinPkg/Ful… + + # Add an EFI shell script for automatic boot if ESC-key is not pressed within 5 seconds timeout. + sed "s|%ARCHISO_LABEL%|${iso_label}|g; + s|%INSTALL_DIR%|${install_dir}|g" ${script_path}/efiboot/EFI/boot/startup.nsh > ${work_dir}/efiboot/EFI/boot/startup.nsh + + umount ${work_dir}/efiboot + fi + : > ${work_dir}/build.${FUNCNAME} + fi +} + # Prepare /${install_dir}/boot/syslinux make_syslinux() { if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then @@ -259,6 +296,7 @@ make_common_single() { make_packages make_setup_mkinitcpio make_boot + make_boot_efi make_syslinux make_isolinux make_customize_root_image diff --git a/configs/releng/efiboot/EFI/boot/startup.nsh b/configs/releng/efiboot/EFI/boot/startup.nsh new file mode 100644 index 0000000..1188d2a --- /dev/null +++ b/configs/releng/efiboot/EFI/boot/startup.nsh @@ -0,0 +1,10 @@ +echo -off + +for %m in (0 9) + if exist fs%m:\EFI\archiso\vmlinuz.efi then + fs%m: + cd fs%m:\EFI\archiso + echo "Launching Arch Linux ISO Kernel fs%m:\EFI\archiso\vmlinuz.efi" + vmlinuz.efi archisobasedir=%INSTALL_DIR% archisolabel=%ARCHISO_LABEL% initrd=\EFI\archiso\archiso.img + endif +endfor -- 1.7.9.5

2 3