Using the sync operation with list option fails with --sysroot when
signed database files are around. Instead use the query operation, which
uses the local databases of installed pakages only.

The only downside is that we do no longer record the originating
repository.
Signed-off-by: Christian Hesse <mail@eworm.de>

https://lists.archlinux.org/pipermail/arch-releng/2018-June/003834.html

Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>

Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>

Fix for FS#58473
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>

The '-d' in pacstrap is a noop nowadays, keeping it may cause confusion
Signed-off-by: Sean Enck <enckse@gmail.com>

Nobody wants to use md5 these days...
Signed-off-by: Christian Hesse <mail@eworm.de>

FS#48382

A new option -g <keyid> is added to set the key id. The squashfs files are only signed if
this option is set.

If old behaviour is needed use "... -s sfs prepare".
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>

I see cases where a stale loop device stays around and fills up my
partition as image file is still in use and does not get unlinked.

Explicitly detach loop device on umount to fix that.
Signed-off-by: Christian Hesse <mail@eworm.de>

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: Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>

Remove unused feature, just to save space
sizeof ext4 image (empty): 4.3M vs 403K (du airootfs.img)
sizeof used space (empty):  48M vs  20K (df)

Thanks Christian Hesse for initial tip.
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>

This is done better with run_once() in build.sh

This is done better with run_once() in build.sh

This is a task done in some way by run_once() on build.sh

Also remove _show_space_usage() irrelevant now when fs size is fixed and big

* Make it ISO9660 friendly (extra dot "." is replaced by "_")
* Was used when support both .fs.sfs and .sfs

Always create one filesystem of a fixed size (32G), format (ext4) and
know name "airootfs".

Simplify logic a lot.

There is no big overhead.
Space usage in ext4-1G is ~0.4M while in ext4-32G is ~4M.
Just use a big value to make all people happy.

Two purposes:
 * systemd filename friendly: "-" is used for "/" and must be escaped with "\x20"
 * ISO9660 filename friendly: "-" is replaced with "_"

Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>

Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>

Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>

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: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>

Fix FS#34075
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>

Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>

Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>

Ensure that all inode table is initialized at filesystem creation.
(Anyway filesystem is small, so at first mount is may quickly initialized)

This avoid possible COW usage during runtime ;)
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>

Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>

This was recently enabled in [systemd] package.
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>

/tmp is mounted as tmpfs since archiso implements own chroot code.
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>

/etc/mtab symlink is part of [filesystem] since long time
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>

It does not make sense, since filesystem inside the imege is re-formated.
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>

Implements FS#30378
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>

Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>