Bug 19337
Summary: | Problem with Auto Partitioning | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Jarin Satterlee <hex7b1> |
Component: | anaconda | Assignee: | Michael Fulbright <msf> |
Status: | CLOSED DUPLICATE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | dr |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-10-27 21:51:47 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
Jarin Satterlee
2000-10-18 20:54:42 UTC
Install Try #1: It isn't clear to me what you are saying, so let me see if I understand. You did a custom install, specified that LILO should be written to the MBR and also you created a new boot floppy when asked? Install Try #2: There is already a request for enhancement for the issue you have brought up, bug number 17085. Install try #1: Yes, I did lilo to mbr and made boot disk at the end of the graphical installation. On reboot I got (without the boot floppy) just an L out of lilo. When I tried the boot floppy it started to boot up and then got a kernel panic. I didn't save the information and frankly I don't really care about try #1. It is what happened in install #2 that pissed me off. I only included the info on the first try to illustrate what I was doing. RH7 is running just fine on the machine now (though taking up both disks) as was RH6.2. It was the partitioning over and formating my primary drive that is the problem. Thanks being such a drone in your response to the real issue. BTW: I get the following results when I try to view bug 17085 that you referred to: Permission denied. Sorry; you do not have the permissions necessary to see bug 17085. Sorry my fault the bug should be viewable now. |