Thanks Daniel Hillenbrand.

Thanks Philip Müller.

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

Should be fixed FS#49314 first

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

Starting with dosfstools 4.0-1 the mkfs executable is called 'mkfs.fat'.

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

Requested at FS#48591

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

Current build leaves ~800K free of 31M in the FAT filesystem, adding 9M.

Going beyond 65535 sectors of 512-byte is a bit special,
but works for EFI. Image size is reported a zero in boot catalog,
but xorriso does a good job, and writes right value in hybrid-partition.

Tested booting in qemu in both modes (cd-rom and hybrid) and works fine.

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

FS#48382

Thomas Bächler authored 9 years ago and Gerardo Pozzi committed 9 years ago

A new option -g <keyid> is added to build.sh set the key id. If it is set, the squashfs files will be signed
by gpg and the gpg key will be added to archiso.img. In order to use this option, a gpg agent must be running.
Since build.sh is executed as root, it may be necessary to set the GNUPGHOME environment variable, for
example

$ su -c "GNUPGHOME=/home/youruser/.gnupg /path/to/build.sh -g yourkeyid"

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>

Requested at FS#45563

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>

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>

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>

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.

Thanks Izumi Natsuka for reporting this.

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

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

Simplify logic a lot.

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

Fix FS#40049

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

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

Ucode updates correct problems with the processor. Without this (or a firmware update),
some machines fail to work in a stable manner. Make sure that the installation is smooth
by providing the ucode on the live system.

(While we're at it, sort packages.both alphabetically.)

Commit a526d961 broke this rule for virtio and other
devices where no ID_NET_* is exported.

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>

FS#36780

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 only under QEMU using OVMF SecureBoot enabled firmware plus lockdown-ms.

Both loader.efi (gummiboot) and vmlinuz.efi should be hashed before boot in secure mode.

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