We don't need biosboot partitions, and the urls should point to rawhide.
On minimal installs dracut needs to have tar and dracut-network
explicitly included.
The directory where the --logfile is located is also used for other log
files and for the anaconda logs when using --no-virt. Create the parent
directories if they don't exist.
This package no longer contains anything that we actually use. Removing
it also removes gnome-themes, which we needed for the metacity theme but
which is now handled by anaconda, and gtk2-engines.
fedora-gnome-theme provides gnome-themes-standard, from which we remove
everything except a metacity theme file that metacity doesn't actually
use. Remove fedora-gnome-theme entirely and manually add the font
dependency that it was pulling in.
--make-pxe-live target generate live squashfs and initrd for pxe boot.
Also generates pxe config template.
--make-ostree-live is used for installations of Atomic Host. Additionally to
--make-pxe-live it ensures using deployment root instead of physical root of
installed disk image where needed. Atomic installation needs to be virt
installation with /boot on separate partition (the only way supported by
Anaconda currently). Content of boot partition is added to live root fs so that
ostree can find deployment by boot configuration.
Previously if there was an error during a novirt installation that
didn't exit the process there was no way to detect it. This uses the new
--remotelog option for anaconda to monitor the logs for errors using the
same criteria as it does when monitoring a virt install. If there is an
error the anaconda process will be terminated and the logs will be
gathered up into ./anaconda/
Virtual machines easily get starved for randomness, and Anaconda insists
on sufficient amounts of entropy when the user requests LUKS disk
encryption. As a result, such installations can hang until Anaconda gives
up (after 10 minutes) and makes do with whatever entropy is available.
The virtualization host can feed randomness to the guest, unblocking the
installation. However, the guest can only consume that randomness through
the virtio-rng module. Let's not remove that module.
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
Signed-off-by: Brian C. Lane <bcl@redhat.com>
Resolves: rhbz#1179000
Recently, Fedora has been trying to do a 3 product split. As part of
that, lorax was changed to do "installpkg lorax-product-*" via
provides.
I think that approach is awkward; a much simpler approach is to simply
specify the product package as input to lorax on the command line, via
external rel-eng scripts.
This patch therefore adds --includepkg (and we should probably add an
option to remove the implicit lorax-product-* glob).
As of fedora kernel kernel-3.17.4-302.fc21 aarch64 can sort out what to
use for the console on its own, so drop the console= from the aarch64
grub2-efi.cfg template.
Older versions of petitboot don't understand the for loop and won't
boot. We also don't shipt 32 bit media anymore so there is no reason
for this to remain.
To make it easier for users to add product and updates images look for
any packages that provide lorax-product-* or lorax-updates-*
Related: rhbz#1155228
This reverts commit bc9b40f18f.
anaconda-21.48.14-1 will revert to the below behavior, so remove the virtual
provide that was added for F21 Alpha/Beta.
You must include a repo in your installation environment that has an id
matching the lower case first part of your product name when split at the '-'
character.
If you don't do that closest mirror will not work.
For Fedora products this means including ONE repo with an id of
'fedora'.
