1. 14 May, 2021 2 commits
  2. 09 Mar, 2021 2 commits
    • nl6720's avatar
      Support EROFS · bc67933a
      nl6720 authored
      EROFS, like Squashfs, is a read-only file system. It can be used to store airootfs in an image file.
      Its advantage is the support for POSIX ACLs. EROFS downside is that currently it only supports LZ4 compression (LZMA support is not yet fully implemented).
      A difference from Squashfs is that, EROFS stores change time (ctime) not modification time (mtime). The reverse is true for Squashfs.
      Implements #59
    • nl6720's avatar
      archiso/initcpio/hooks/archiso: remove redundant /sfs/ from airootfs mount point · 711ab4cd
      nl6720 authored
      Remove /run/archiso/bootmnt directory if nothing is mounted there. An empty directory is just confusing.
  3. 11 Aug, 2020 1 commit
  4. 29 Jul, 2020 1 commit
    • David Runge's avatar
      Add license and basic documentation · e264b446
      David Runge authored
      Add GPL-3.0 license.
      Add SPDX license identifier.
      Add SPDX license identifier.
      Install the `run_archiso.sh` script as global executable `run_archiso`.
      Use -D and -t flags to install to install files more generically (without a previous call to install the directory).
      Add README outlining the project's scope, how to build images from the profiles and how to test.
      Add list of all direct contributors to the repository.
      Add basic contribution guidelines, explaining the linter and the license in use.
      Closes #7
      Closes #3
  5. 17 Jul, 2020 1 commit
  6. 11 Jul, 2020 1 commit
    • David Runge's avatar
      Adding linting for initcpio scripts · e2032db4
      David Runge authored
      Setting bash shebang for all scripts and making them comform with shellcheck.
      Setting ash shebang for all scripts and making them comform with shellcheck (for dash, as shellcheck has no ash specific
      ruleset). Essentially the ash based scripts should be POSIX compliant as much as possible to have an easier time
      writing, debugging and maintaining them.
      Ensuring that variables are not treated as options and introducing variable quoting.
      Integrating shellcheck for initcpio scripts.
      Closes #32
  7. 29 Jun, 2018 1 commit
  8. 18 Oct, 2017 1 commit
  9. 28 Feb, 2016 1 commit
  10. 05 Feb, 2016 1 commit
  11. 13 Dec, 2015 1 commit
  12. 29 May, 2015 2 commits
  13. 27 Jan, 2015 2 commits
    • Gerardo Exequiel Pozzi's avatar
      [archiso] Rename cowfile_size to cow_spacesize= · 9322a0d3
      Gerardo Exequiel Pozzi authored
      The name is more relevant since the usage is shared for both
      dm-snapshot and overlayfs.
      Signed-off-by: default avatarGerardo Exequiel Pozzi <vmlinuz386@gmail.com>
    • 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>
  14. 02 Jan, 2015 2 commits
  15. 13 Dec, 2014 1 commit
  16. 14 Oct, 2014 1 commit
  17. 08 Aug, 2014 1 commit
  18. 28 Jun, 2014 3 commits
  19. 08 Jan, 2013 1 commit
  20. 13 Oct, 2012 1 commit
    • Gerardo Exequiel Pozzi's avatar
      [archiso] Introduce cowfile_size= bootparam · 1746e310
      Gerardo Exequiel Pozzi authored
      If not set, nothing is changed in current behaviour.
      Since dm-snapshot allows to use as "COW" a file with any size,
      without caring about the the size of "origin", we can avoid creating a
      "COW" file of the same size as the "origin". This is really useful,
      when using as cow_device= a filesystem that is VFAT where sparse files
      are not supported, so if root-image.fs is 1000M, passing cowfile_size=25%
      will create a root-image.cow of 250M instead of 1000M.
      Signed-off-by: default avatarGerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
  21. 05 Oct, 2012 1 commit
  22. 25 Aug, 2012 1 commit
  23. 19 Apr, 2012 1 commit
  24. 23 Feb, 2012 5 commits
  25. 11 Jan, 2012 1 commit
  26. 05 Jan, 2012 2 commits
  27. 03 Dec, 2011 1 commit
  28. 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>