- 12 Sep, 2015 1 commit
-
-
Gerardo Exequiel Pozzi authored
Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 12 Aug, 2015 1 commit
-
-
Gerardo Exequiel Pozzi authored
Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 30 Jul, 2015 1 commit
-
-
Gerardo Exequiel Pozzi authored
Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 20 Jul, 2015 1 commit
-
-
Gerardo Exequiel Pozzi authored
Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 18 Jul, 2015 1 commit
-
-
Gerardo Exequiel Pozzi authored
Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 09 Jul, 2015 1 commit
-
-
Gerardo Exequiel Pozzi authored
Requested at FS#45563 Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 25 Jun, 2015 3 commits
-
-
Gerardo Exequiel Pozzi authored
Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
Gerardo Exequiel Pozzi authored
Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
Christian Hesse authored
We received an IP address from DHCP server and configure it statically. This is required if we continue to use network connectivity to access the root device (for example via NBD or NFS). The lease is not updated, though. This can cause trouble in networks with low lease times. So let's flush the addresses if root filesystem has been copied to RAM. A dhcp client in main system can handle the network connectivity then. Signed-off-by:
Christian Hesse <mail@eworm.de>
-
- 29 May, 2015 3 commits
-
-
Christian Hesse authored
Signed-off-by:
Christian Hesse <mail@eworm.de>
-
Christian Hesse authored
Signed-off-by:
Christian Hesse <mail@eworm.de>
-
Christian Hesse authored
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>
-
- 24 Apr, 2015 1 commit
-
-
Gerardo Exequiel Pozzi authored
Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 21 Apr, 2015 1 commit
-
-
Christian Hesse authored
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>
-
- 19 Apr, 2015 1 commit
-
-
Gerardo Exequiel Pozzi authored
Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 17 Apr, 2015 2 commits
-
-
Gerardo Exequiel Pozzi authored
Fix FS#44620, reported by Lukas B. Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
Gerardo Exequiel Pozzi authored
Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 27 Jan, 2015 2 commits
-
-
Gerardo Exequiel Pozzi authored
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>
-
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:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 02 Jan, 2015 3 commits
-
-
Christian Hesse authored
Signed-off-by:
Christian Hesse <mail@eworm.de>
-
Christian Hesse authored
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
Signed-off-by:
Christian Hesse <mail@eworm.de>
-
- 21 Dec, 2014 1 commit
-
-
Gerardo Exequiel Pozzi authored
Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 13 Dec, 2014 1 commit
-
-
Gerardo Exequiel Pozzi authored
Since now cowspace_size == cowfile_size (only one file inside) Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 01 Nov, 2014 2 commits
-
-
Gerardo Exequiel Pozzi authored
Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
Gerardo Exequiel Pozzi authored
Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 29 Oct, 2014 1 commit
-
-
Gerardo Exequiel Pozzi authored
Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 14 Oct, 2014 1 commit
-
-
Gerardo Exequiel Pozzi authored
Move from percent to explicit size and set a default of 256M (sparse) Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 02 Sep, 2014 2 commits
-
-
Thomas Bächler authored
Signed-off-by:
Thomas Bächler <thomas@archlinux.org>
-
Thomas Bächler authored
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.
-
- 28 Aug, 2014 1 commit
-
-
Gerardo Exequiel Pozzi authored
Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 22 Aug, 2014 1 commit
-
-
Gerardo Exequiel Pozzi authored
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>
-
- 12 Aug, 2014 2 commits
-
-
Gerardo Exequiel Pozzi authored
Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
Lukas Fleischer authored
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>
-
- 08 Aug, 2014 1 commit
-
-
Lukas Fleischer authored
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>
-
- 28 Jul, 2014 1 commit
-
-
Gerardo Exequiel Pozzi authored
Thanks Izumi Natsuka for reporting this. Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 26 Jul, 2014 2 commits
-
-
Gerardo Exequiel Pozzi authored
Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
Gerardo Exequiel Pozzi authored
The proper fix in now in mkinitcpio-18 Signed-off-by:
Gerardo Exequiel Pozzi <vmlinuz386@gmail.com>
-
- 28 Jun, 2014 2 commits
-
-
Gerardo Exequiel Pozzi authored
-
Gerardo Exequiel Pozzi authored
This is done better with run_once() in build.sh
-