Bug 215209
| Summary: | [enh] install boot loader earlier within install | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Timms <dtimms> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-03-15 22:08:35 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
err1: point _where_ packages
err2: amount of time it takes for _yum_ to {I'm awake now}.
There would also the possibility of using the multi-threading capability to
begin partitioning and formatting in the background while package resolution is
taking place; and if this completes before package resolution begins to start
downloading the first packages required; this could also be extended to
downloading packages {network} while installing {disk}.
Note: with kickstart and limited package selection it is possible to be running
in about 15-20 minutes in any case {on a fast machine}.
It's not quite that simple. The boot loader is arch specific. If we split the installation in to two transactions, one for the boot loader set and one for everything else, we still have the problem of figuring out what else should be in the boot loader set that would make a system not only bootable, but also usable. And once you've reached that point, what is the point really? You've gained the same that the rescue CD gives you, but added a ton of complexity to the installer. It's a nice idea, but I think we provide enough recovery methods in the cases where the installation fails and the system is unbootable. |
Description of problem: If something goes wrong during an install, the boot loader might not get installed since it is the last thing that happens before completing the install. Version-Release number of selected component (if applicable): fc6 dvd i386 release Expected results: Bootloader could / should be installed / configured as soon as appropriate files are on the disk. Additional info: In the {occasional} times when an install fails to reach the end, it would have been good to have a bootable system. Perhaps the yum transaction could be split into two parts. First would get to the point packages installed so far would allow grub-install would be run, so that worst case, the machine could actually boot. Secondly, yum would install the rest of the selected packages. Given the amount of time it takes for grub to do it's thing before packages are actually installed, there might also be an advantage in reduced total package resolution time because each transaction would be involving fewer packages ?