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

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

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

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

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

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

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

According to ip-address(8) flushing an interface requires the
keyword 'dev'.
Also add proper quoting.

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

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

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

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

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

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

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

Thanks Daniel Hillenbrand.

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

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>

This should fix FS#36749

Also flush address on specified device (default)

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

Requested at FS#48591

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

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

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

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"

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

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

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

If the ARCHISO_GNUPG_FD environment variable is set, its contents will be interpreted as an open file
descriptor and its contents will be used to create a keyring in the initramfs in /gpg.

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

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

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

Having files on btrfs subvolumes requires to give mount options. Add
boot params archisoflags= and cow_flags= for this purpose. Boot
parameters could look like this:

... archisodevice=/dev/sdaX archisoflags=subvolume=isos
cow_device=/dev/sdaX cow_flags=subvolume=persist ...

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

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

If old behaviour is needed use "... -s sfs prepare".

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

Adam Purkrt authored 9 years ago and Gerardo Pozzi committed 9 years ago

Currently, when booting loopmounted iso file, it is necessary to
specify not only img_dev and img_loop (which should be sufficient),
but also archisolabel or archisodevice. With this patch, archisodevice
is directly populated with the correct loop device, and it is not
necessary to specify the label when booting from loopmounted iso,
which makes for leaner and cleaner grub.cfg.

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>

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

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>

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

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

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

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

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

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>

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