Bug 34174
Summary: | rc2 anaconda won't reset trashed MBR | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Bowe Strickland <bowe> |
Component: | anaconda | Assignee: | Matt Wilson <msw> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-09-17 20:17:43 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
Bowe Strickland
2001-03-30 21:50:17 UTC
We will consider different behavior in the future - admittedly your case is an extremely rare incidence (most users do not mess manually with the boot sector). You can just goto VC2 (cntl-alt-f2) when you get to this point in the install and mknod /tmp/hda fdisk /tmp/hda and reset it as you like. agreed, but note that VC2 is not an option for kickstart installs (where 'wipembr yes' has been defined!) (although inelegant scripting of fdisk through %pre would be possible). FWIW, i'm not sure it's "extremely rare" for someone to be handling an unitialized drive at install time. I've been frustrated with other "unnamed vendors ;)" providing an installer that demanded that I had an initialized MBR before. For an installer not to be able to trivially configure blank media seems a bad assumption. thanx! --bowe As msf said, this is something we will consider for the future. It's much too late in the cycle to consider this for the current release. Deferring. Should work better with roswell. |