Bug 60417
Summary: | partition ordering inconsistent w/ autopartition | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Jeff Wiedemeier <jeff.wiedemeier> |
Component: | aboot | Assignee: | Beth Uptagrafft <bhu> |
Status: | CLOSED NOTABUG | QA Contact: | Beth Uptagrafft <bhu> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | msw |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | alpha | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-04-03 08:18:46 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
Jeff Wiedemeier
2002-02-27 16:40:58 UTC
Huh? /boot is forced to be the first partition because of the old 0.7 problem of addressing the disk beyond the 2Gb (was it 2 or 4?) extent limit I'm perhaps being nieve, but why is the ordering important to you? after all, autopartitioning is the 'I don't care, just make it work' option. People that do care would probably want to manually setup the disk partitioning as they see fit/expect. Phil =--= Yes, autopartitioning is the "just make it work" option, but the consistent ordering in the past was extremely useful when people would ask questions like "I can't boot my system, what do I do?" With the current aboot, you can poke around the disk and find the right partitions, but knowing that an autopartitioned disk had the root filesystem as /dev/sda2 gave a big head start. In any case, I guess I don't particularly care whether this is changed or not. I thought it was odd the two consectuve autopartitioned installs on the same system would choose different orders. Also, since it is different behavior than in the past, I wanted to call it out. If it's by design, fine. If it's a mistake... Well,... I suppose a way around that would be to dump the location of / and /boot into the comment field of aboot.conf Perhaps that might help? Phil =--= Umm any update? or shall we close this one? Phil =--= Closing.... |