Bug 135851
Summary: | No option to create boot disk | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Need Real Name <lsof> |
Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | barryn, nobody+pnasrat |
Target Milestone: | --- | Keywords: | StringChange |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-04-08 21:27:11 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: |
Description
Need Real Name
2004-10-15 12:35:58 UTC
If the message is removed, there's still the problem (and the bug) that the newly installed Linux is inaccessible. Surely the boot disk stage is required? No, not necessarily. You could boot from a rescue CD (that includes the FC installer's rescue mode) and set up whatever boot method you're really going to use, for instance. Or another example is that you could boot into another existing Linux installation and edit its bootloader configuration. There are tons of possibilities which have nothing to do with a boot disk. Good point. A reminder that "the system will not be bootable into Linux" would be appropriate then, possibly what Jeremy Katz meant by StringChange.. Fixed in CVS Close? Assuming fixed. |