Bug 92421
| Summary: | How anaconda recognizes iso images of self-created installation disks(1,2,3) | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Van <k_tgiang> |
| Component: | anaconda | Assignee: | Michael Fulbright <msf> |
| Status: | CLOSED NOTABUG | QA Contact: | Mike McLean <mikem> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-06-06 02:04:42 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: | |||
The information is contained in the RedHat/base/hdlist file. See numerous posts on anaconda-devel-list (https://listman.redhat.com/mailman/listinfo/anaconda-devel-list) for information on how to create your own customized cds. |
Description of problem: (forgive me if this goes to the wrong question category): I can't find information how anaconda recognizes packages burned on different installation disks ( created by myself ). Specifically, I copy rpms packages from a ftp site and burned them onto 3 different CDs following the outlined configuration of directories and files in the manual, the first of which also has the isolinux.iso file made too by mkisofs. The first CD should automatically boot the anaconda installation program, but then how does it recognizes different packages burned among 3 CDs? It asks me for the 2nd CD while the package needed is in the 3rd CD. Is there a way to tell anaconda the list of packages burned on each CD? ( Does it have anything to do with TRANS.TLB file in each subdirectory ? ) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Following the outlined configuration of directories and files of each CD, and make an iso image for booting from CD #1, and burn all necessary rpm files on those 3 CDs. 2. Boot from the CD #1 and run in graphical mode of upgrade 3. It asks for CD#2 but the package needed is in the CD#3 Actual results: Expected results: Self-created CDs should work the same as Boxed-CDs. Additional info: I am trying to upgrade from Redhat8 to Redhat9 due to problems in gnome-volume-control bug in Redhat8, which was fixed in Redhat9 as told by some technician. The bug was that gnome-volume-control causes Unresolved Symbols when I used Alsa Sound Package for my Intel810 sound chipset.