1. 21 Apr, 2015 1 commit
  2. 27 Jan, 2015 1 commit
    • Gerardo Exequiel Pozzi's avatar
      [archiso] Add optional OverlayFS support · a637bdb8
      Gerardo Exequiel Pozzi authored
      This is the first attemp to test overlayfs in archiso.
      The current dm-snapshot mode is keep and is enabled by default,
      while the new mode is enabled via "-s sfs" to mkarchiso.
      No new boot parameters are added, since archiso hooks detects
      if the .sfs file is for dm-snapshot (airootfs.img inside)
      or for overlayfs.
      Persistence is supported in overlayfs mode using the same options
      (cowlabel or cowdevice), but warning while in dm-snapshot mode,
      only one file is used (airootfs.cow), in overlayfs mode internal
      files for workdir/ and upperdir/ are allocated, so you can not use
      VFAT or NTFS.
      To test this, you need to enable [testing] in pacman.conf from
      releng profile and edit build.sh then add "-s sfs" in make_prepare()
      Look at:
          setarch ${arch} mkarchiso ${verbose} -w "${work_dir}" -D "${install_dir}" prepare
      Replace with:
          setarch ${arch} mkarchiso ${verbose} -w "${work_dir}" -s sfs -D "${install_dir}" prepare
      The build requires just half of space that the build for dm-snapshot,
      since there is no ext4 img ;)
      Just to remember: there is no space gain in .sfs (just about 2M)
      There is at least one thing during boot with machine-id service:
      Dec 24 03:31:39 archiso systemd-machine-id-commit[183]: Failed to unmount transient /etc/machine-id file in our private namespace: Invalid argument
      Signed-off-by: default avatarGerardo Exequiel Pozzi <vmlinuz386@gmail.com>
  3. 22 Aug, 2014 1 commit
  4. 28 Jun, 2014 13 commits
  5. 02 Oct, 2013 1 commit
  6. 21 Sep, 2013 2 commits
  7. 20 Jun, 2013 1 commit
    • Gerardo Exequiel Pozzi's avatar
      [archiso] Add support to isohybrid-gpt for EFI boot · f19f6173
      Gerardo Exequiel Pozzi authored
      Tested and works fine under qemu using seabios and ovmf
      $ qemu-system-x86_64 -enable-kvm -drive file=~/archlinux-2013.06.20-dual.iso
      $ qemu-system-x86_64 -enable-kvm -drive file=~/archlinux-2013.06.20-dual.iso,media=cdrom
      $ qemu-system-x86_64 -enable-kvm -bios ~/arch/OVMF/bios.bin -drive file=~/archlinux-2013.06.20-dual.iso
      $ qemu-system-x86_64 -enable-kvm -bios ~/arch/OVMF/bios.bin -drive file=~/archlinux-2013.06.20-dual.iso,media=cdrom
      Signed-off-by: default avatarGerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
  8. 03 Mar, 2013 1 commit
  9. 16 Dec, 2012 2 commits
  10. 10 Dec, 2012 2 commits
  11. 24 Oct, 2012 3 commits
  12. 01 Aug, 2012 1 commit
  13. 20 Jul, 2012 1 commit
  14. 30 May, 2012 1 commit
  15. 09 Apr, 2012 1 commit
  16. 01 Apr, 2012 2 commits
  17. 17 Mar, 2012 2 commits
  18. 16 Mar, 2012 1 commit
  19. 03 Dec, 2011 1 commit
  20. 28 Nov, 2011 1 commit
    • Gerardo Exequiel Pozzi's avatar
      [archiso] Checksum only aitab and *.sfs (per architecture) · cd359bc3
      Gerardo Exequiel Pozzi authored
      We are currently checksuming all files inside $archisobasedir
      (aitab, *sfs, kernel/initramfs and boot/syslinux related files)
      this is stored in one file only. Its works good for now,
      but I think we only need to checksum only aitab and *.sfs if they are needed.
      Currently if you boot a dual-iso in i686, also checksum is done
      for *.sfs of x86_64. Not a big issue, this just take a bit more time.
      The real issue is when booting via PXE with HTTP/FTP methods,
      since they download only aitab and needed *.sfs files,
      can not use directly the only one file where checksums are stored.
      This patch does:
      (1) Do not checksum syslinux related files, anyway you are already reach initramfs stage.
      (2) Do not checksum kernel/initramfs files, for the same as (1)
      (3) Two checksum.${arch}.md5 for each i686 and x86_64 for only aitab and *.sfs.
      Signed-off-by: default avatarGerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
  21. 15 Oct, 2011 1 commit