Bug 207331
Summary: | EDD support updates needed in RHEL5 Beta1 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Rezwanul Kabir <rezwanul_kabir> | ||||||
Component: | anaconda | Assignee: | Jeremy Katz <katzj> | ||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 5.0 | CC: | wwlinuxengineering | ||||||
Target Milestone: | --- | Keywords: | FutureFeature | ||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | pm-20060928 | ||||||||
Fixed In Version: | 5.0.0 | Doc Type: | Enhancement | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2006-11-28 21:39: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: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 184191 | ||||||||
Attachments: |
|
Description
Rezwanul Kabir
2006-09-20 18:40:37 UTC
Created attachment 136763 [details]
Patch the solve EDD support issues in RHEL4
This patch introduces a couple of regressions at a glance: * It doesn't ensure that /tmp/biosdev gets closed. This will then lead to errors later when doing partitioning * I'm not sure it'll actually build with -Werror as you've removed the assignment of the result from sscanf which raises a warning. I'm also not sure that it's an okay generic assumption to make that duplicate signatures are okay. Some people do use the functionality for other BIOS disks and I think it's important to not break that. Why aren't you having unique sigs across all the disks? 1. In Dell Server Assistant based installations, the customers usually do a reinstall of the OS. In this circumstances, the installer ensures that there is a unique signature for the biosdisk 0x80 but does not want to touch the rest of the disks so as to not corrupt any data/metadata on those. The idea is, since the installation will be done on the first BIOS disk and that is already ensured there is logically no reason to label others. 2. As I have mentioned in the description, as long as a user specifies a certain biosdisk ( say biosdisk 0x82 ) in the ks.cfg, and eddsupport.c can identify unique signature for that biosdisk, the install will go on otherwise it will error out. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering. This request is not yet committed for inclusion in release. Okay, can you clean up the regressions I pointed out? Created attachment 136950 [details]
Modified patch per Jeremy's comments
Jeremy, here you go..
Jeremy- Does the patch Rez submitted look good ? It looks good, holding off until after branching from FC6 to add it as I'm just not _quite_ comfortable changing that codepath at this point in the fc6 cycle Committed to HEAD and rhel5-branch Rez- Can you please verify with the build we received from RH yesterday and post results here ASAP so we can mark this as VERIFIED. Verified the patch in weekly build 2006-11-07. Thanks. This can be closed now. |