From Fedora Project Wiki
No edit summary |
(s/inst.repo=/inst.stage2= : this mechanism only works for stage2 at present) |
||
Line 9: | Line 9: | ||
# Copy the {{filename|updates.img}} into the {{filename|images/}} directory of your local installation source | # Copy the {{filename|updates.img}} into the {{filename|images/}} directory of your local installation source | ||
|actions= | |actions= | ||
# Boot the installer using the <code>inst. | # Boot the installer using the <code>inst.stage2=</code> option at boot directing to the modified installation source where the {{filename|updates.img}} was published. See [[Anaconda/Options]] for information on supported boot options. | ||
#* If you have a full repository mirrored, you can use any boot medium. | #* If you have a full repository mirrored, you can use any boot medium. | ||
#* If you have just a test compose files mirrored, you need to use direct kernel boot (PXE or a kernel boot in a virtual machine). It will use the provided <code>inst.repo</code> as a source of Anaconda's stage2 image and it should also apply {{filename|updates.img}}, if available. The online repositories will then be used as the package source. | #* If you have just a test compose files mirrored, you need to use direct kernel boot (PXE or a kernel boot in a virtual machine). It will use the provided <code>inst.repo</code> as a source of Anaconda's stage2 image and it should also apply {{filename|updates.img}}, if available. The online repositories will then be used as the package source. |
Revision as of 19:35, 25 June 2013
Description
This test will verify that anaconda can download and apply a updates.img
that is inside the remote installation source without extra input from the user. For help preparing updates.img
, see Anaconda/Updates
Setup
- Prepare a local installation source by mirroring an existing online source. You can either mirror a whole repository for Fedora Branched, or you can mirror just a single test compose.
- When mirroring the whole Fedora Branched repository, mirror
/pub/fedora/linux/development/41/<arch>/os/
directory from one of the official mirrors. This amounts to dozens of GBs of space, but you will be able to use a standardnetinst.iso
/DVD.iso
/Live.iso
with it. - When mirroring a single test compose, mirror
/Fedora/<arch>/os/
directory from the compose. This is just hundreds of MBs, but you will need to use direct kernel boot (PXE or a kernel boot in a virtual machine) to test it.
- When mirroring the whole Fedora Branched repository, mirror
- Make the installation source accessible over one of the supported network protocols (HTTP, FTP, NFS).
- Prepare a valid
updates.img
file. See this page for image creation instructions. A good thing to change in theupdates.img
is the "What language would you like to use during the installation process?" text inpyanaconda/ui/gui/spokes/welcome.glade
, as this text is displayed on one of the first screens. - Copy the
updates.img
into theimages/
directory of your local installation source
How to test
- Boot the installer using the
inst.stage2=
option at boot directing to the modified installation source where theupdates.img
was published. See Anaconda/Options for information on supported boot options.- If you have a full repository mirrored, you can use any boot medium.
- If you have just a test compose files mirrored, you need to use direct kernel boot (PXE or a kernel boot in a virtual machine). It will use the provided
inst.repo
as a source of Anaconda's stage2 image and it should also applyupdates.img
, if available. The online repositories will then be used as the package source.
- Proceed with installation
Expected Results
- Anaconda prepares the
updates.img
and copies its content to/tmp/updates/
. Any changes you included in the updates.img file are applied - Anaconda proceeds without related errors