Search results

{{anchor|release-blocking-images-must-boot}} ==== Release-blocking images must boot ====

{{anchor|release-blocking-images-must-boot}} ==== Release-blocking images must boot ====

...ng of the Linux boot process in general, an understanding of the Kickstart boot process in particular, and some skill with scripting. If you use this appro ...be used to alter the behaviour of the program itself: define installation methods, set network parameters, etc. What can you do, though, when you want to get

For each [[Editions|Edition]], the installer must be clearly identified as that Edition in all of that Edition's install {{anchor|release-blocking-images-must-boot}}

...expect when you work with the new installer and some known issues with the installer that will be resolved in later releases of Fedora. = Why rewrite the installer? =

...ng /etc/selinux/config in the installed system prior to rebooting from the installer ...g with different images, and various issues that show up when you boot the installer from USB rather than a spinning disc.

For each [[Editions|Edition]], the installer must be clearly identified as that Edition in all of that Edition's install {{anchor|release-blocking-images-must-boot}}

For each [[Editions|Edition]], the installer must be clearly identified as that Edition in all of that Edition's install {{anchor|release-blocking-images-must-boot}}

The Beta release is available through the following download methods: ==== Anaconda Installer Improvements ====

{{anchor|release-blocking-images-must-boot}} ==== Release-blocking images must boot ====

For each [[Editions|Edition]], the installer must be clearly identified as that Edition in all of that Edition's install {{anchor|release-blocking-images-must-boot}}

For each [[Editions|Edition]], the installer must be clearly identified as that Edition in all of that Edition's install {{anchor|release-blocking-images-must-boot}}

* AGREED: [[rhbug:806749]] is accepted as a blocker per alpha criterion "The installer must be able to use the HTTP, FTP and NFS remote package source options" * AGREED: [[rhbug:806708]] is a blocker per alpha criterion "The installer must be able to use the HTTP, FTP and NFS remote package source options", n

| style="color: #854685" | #info May impact Alpha criteria "The installer must be able to report failures to Bugzilla, with appropriate information i | style="color: #407a40" | proposed #agreed 692433 - AcceptedBlocker - The installer must be able to report failures to Bugzilla, with appropriate information i

| Boot Methods | Boot Methods

For each [[Editions|Edition]], the installer must be clearly identified as that Edition in all of that Edition's install {{anchor|release-blocking-images-must-boot}}

==== Network '''''enablement''''' in installer ==== ...storage. The configuration can be supplied with [[Anaconda/Network#boot | boot parameters]], or [[Anaconda/Network#kickstart | kickstart]], or if needed u

...ision: see [[Anaconda/NewInstaller|the known design limitations of the new installer]] in Fedora 18, and [[Common_F18_bugs#Installation_issues|known significant ...emd provides most of the upgrade functionality, doing the work in a unique boot environment.

* some installer test discussion * '''wwoods''' - begin stubbing out interoperability (dual-boot) test cases in F9 Install Test Plan

For each [[Editions|Edition]], the installer must be clearly identified as that Edition in all of that Edition's install {{anchor|release-blocking-images-must-boot}}