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

Christian Hesse authored 9 years ago and Gerardo Pozzi committed 9 years ago

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>

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

Fix FS#44620, reported by Lukas B.

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

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

The name is more relevant since the usage is shared for both
dm-snapshot and overlayfs.

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

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>

Christian Hesse authored 10 years ago and Gerardo Pozzi committed 10 years ago

Signed-off-by: Christian Hesse <mail@eworm.de>

Christian Hesse authored 10 years ago and Gerardo Pozzi committed 10 years ago

Copying big amount of data results in bad performance as data is
written in chunks of 4kiB (8 * 512 bytes).

The default is not changed but can be overwritten.

Signed-off-by: Christian Hesse <mail@eworm.de>

Christian Hesse authored 10 years ago and Gerardo Pozzi committed 10 years ago

Signed-off-by: Christian Hesse <mail@eworm.de>

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

Since now cowspace_size == cowfile_size (only one file inside)

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

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

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

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

Move from percent to explicit size and set a default of 256M (sparse)

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

Signed-off-by: Thomas Bächler <thomas@archlinux.org>

This makes systemd generate a machine-id on early boot and prevents it from thinking we need
any "first boot" setup. We really don't want systemd thinking that, since we carefully prepared
our root file system.

This also ensures every live environment has a unique machine id.

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>

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

Lukas Fleischer authored 10 years ago and Gerardo Pozzi committed 10 years ago

Currently, when booting via HTTP, the airootfs.md5 file is downloaded to
/run/archiso/bootmnt/arch/. However, the checksum file is later assumed
to be located at "/run/archiso/bootmnt/arch/${arch}". Fix the _curl_get
invocation and directly place the file in the right directory.

Fixes a regression introduced in commit b3e1d313 ([archiso] Rework
checksum function, 2014-06-28).

Signed-off-by: Lukas Fleischer <archlinux@cryptocrack.de>

Lukas Fleischer authored 10 years ago and Gerardo Pozzi committed 10 years ago

Among other things, 36459f3a ([archiso] Drop aitab support, 2014-06-28)
removed the possibility to manually set a specific architecture by using
kernel parameters. This, however, is useful, e.g. when installing Arch
Linux on a device that reports itself as i586 but works fine with the
i686 flavor.

Signed-off-by: Lukas Fleischer <archlinux@cryptocrack.de>

Thanks Izumi Natsuka for reporting this.

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

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

The proper fix in now in mkinitcpio-18

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>