| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Christian Hesse <mail@eworm.de>
|
|
Umount detaches the loop device automatically, but let's make it
explicit to be sure. Additionally losetup gives:
losetup: /dev/loop0: detach failed: No such device or address
This is kind of expected, let's silent the error message.
Signed-off-by: Christian Hesse <mail@eworm.de>
|
|
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>
|
|
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>
|
|
Signed-off-by: Christian Hesse <mail@eworm.de>
|
|
Since now cowspace_size == cowfile_size (only one file inside)
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>
|
|
Among other things, 0bb94de ([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>
|
|
|
|
* 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.
|
|
|
|
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: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
|
|
This fixes FS#31815
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
|
|
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
|
|
Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
|
|
Fixes FS#10206
Setting the drive to autoeject causes
udevadm trigger to always eject the device
if it isn't mounted.
Signed-off-by: Simo Leone <simo@archlinux.org>
|
|
udev doesn't modprobe loop by itself so we have
to ask it nicely.
Signed-off-by: Simo Leone <simo@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
Signed-off-by: Simo Leone <simo@archlinux.org>
|
|
Also improved variable naming.
Signed-off-by: Simo Leone <simo@archlinux.org>
|
|
No longer assume the image is in the addons
directory.
Signed-off-by: Simo Leone <simo@archlinux.org>
|
|
The check for a comment line wasn't actually working
before. Shell quoting ftl.
Signed-off-by: Simo Leone <simo@archlinux.org>
|
|
This allows the root image to remain a [mostly] pristine
image, and turns default liveCD configurations into an
overlay, rather than copying them into the root image.
Signed-off-by: Simo Leone <simo@archlinux.org>
|
|
Moved addon mounting code into functions.
Signed-off-by: Simo Leone <simo@archlinux.org>
|
|
For now all it handles is bind mounting and squashfs
images that have to overlay at the root. The config
file syntax is obviously borrowed from fstab. This
is far from final, much of it could use some cleanup.
Signed-off-by: Simo Leone <simo@archlinux.org>
|
|
If asked to do so, mkarchiso simply copies a
directory full of addons to the iso root.
On boot, after union-mounting /real_root, the
archiso hook will look for and source an addon
config file. This file is a plain old bash
script, which makes it quite flexible. The addon
config should be written to take care of any
mounting that needs to be done, an example of
typical tasks is also included.
Signed-off-by: Simo Leone <simo@archlinux.org>
|
|
* Get rid of unnecessary trailing slash on BOOT_MOUNT variable
* Fix -eq/= mixup- we are comparing strings, not numbers
* Don't unmount /dev, as it was never mounted
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Usually initcpio's init takes care of this, but
it never executes that far, so this is copypasta.
Signed-off-by: Simo Leone <simo@archlinux.org>
|
|
Move the vim modelines to the bottom, and add the tab settings.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Appears to have been changed to archlive.sqfs,
a couple hooks refered to the old name and didn't work.
Signed-off-by: Simo Leone <simo@archlinux.org>
|
|
This reverts commit 42d794561c1f3809f95299e4aa04cd3f28d4239b.
My bad. Bad logic on removing, it was an option anyway.
|
|
This implies a memory requirement for the running system, since
the sqfs image needs to be able to fit onto the ramdisk, which
breaks lowmem systems like qemu.
Signed-off-by: Simo Leone <simo@archlinux.org>
|
|
Several small changes just as a shim to get everything to work.
Signed-off-by: Simo Leone <simo@archlinux.org>
|
|
00a9fe69-e71b-0410-bb23-df0e5024db41
|