After messing around with the SL scripts I have discovered exactly what the problem is. I just don't know what the solution is. The problem is the Java rpms. If I include the jre*.rpm and/or the jdk*.rpm the genhdlist always spits out the warning that "ordering not found" for those packages and the installation fails as soon as it gets to the Preparing for RPM installation stage. If I leave those packages out the install completes successfully. Does anyone have any ideas as to why the jre rpm wouldn't have an ordering? I am assuming that Sun left something out of them that anaconda needs? Thanks -Scott -----Original Message----- From: Connie Sieh [mailto:csieh@xxxxxxxx] Sent: Tuesday, September 27, 2005 9:26 AM To: Edwards, Scott (GE Healthcare) Cc: anaconda-devel-list@xxxxxxxxxx Subject: Re: I do want to customize my own distribution (was RE: I don't want to customize my own distribution.....) Scott, We saw the need to be able to customize RedHat based releases when we designed Scientific Linux. Scientific Linux is a RHEL 3/4 rebuild just as Centos is, but with the ability to customize it. We call these customizations "sites" as different "sites" might want customizations. Items that can be customized include Custom install images used by anaconda Custom version of anaconda(has to be based on RHEL 3/4 version) Added rpms Updated rpms Downgraded rpms including the kernel For more information see http://www.scientificlinux.org/documentation/howto/create.site The describes how to make a site, indicated for 3.0.x, same general instructions for 4.x . ftp://ftp.scientificlinux.org/linux/scientific/ For a example of a customized site ftp://ftp.scientificlinux.org/linux/scientific/303/i386/sites/Fermi/ As you can see from the above url, this is basically a release within a release, with only the changes in the site directory. -Connie Sieh Fermi National Accelerator Laboratory On Mon, 26 Sep 2005, Edwards, Scott (GE Healthcare) wrote: > > > Hello, > > I'm still having the same problem I was having almost a year ago, the famous failure after "Preparing RPM transaction...". I made a custom install for Fedora Core 2 which worked fine. Last year I tried to make a custom install of Fedora Core 3 using the exact same procedure, and it always failed after "Preparing RPM transaction...". I worked on it for a couple of weeks trying different things and never could get it to work. At the time there were some instructions on creating a custom Fedora Core 3 CD and I followed them exactly but it still failed. I had to finally abandon the project. > > I am trying to create a custom install now with CentOS and I get the same problem as I did with Fedora Core 3. Does anyone have any ideas as to what could have changed between Fedora Core 2 and 3 that would break the procedure? These are the steps I follow (after the CD directory is all prepared): > > /usr/lib/anaconda-runtime/genhdlist --productpath=CentOS $PWD > PYTHONPATH=/usr/lib/anaconda /usr/lib/anaconda-runtime/pkgorder $PWD i386 CentOS > $TEMP_DIR/pkgfile > /usr/lib/anaconda-runtime/genhdlist --withnumbers --fileorder $TEMP_DIR/pkgfile --productpath=CentOS $PWD > > Is there a step I need to add? > > I have just tried a Google Search and a search of the Fedora Wiki/Anaconda and I can't find instructions for creating a custom CD now. If someone could point me to those instructions on the Wiki, I will try them. > > Thanks > -Scott > > > -----Original Message----- > From: anaconda-devel-list-bounces@xxxxxxxxxx > [mailto:anaconda-devel-list-bounces@xxxxxxxxxx]On Behalf Of Greg Morgan > Sent: Wednesday, August 17, 2005 8:55 PM > To: anaconda-devel-list@xxxxxxxxxx > Subject: Re: I don't want to customize my own distribution..... > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > John Summerfied wrote: > > Dustin kirkland wrote: > > > >> Hey list- > >> > >> I think since I joined this list earlier this year, probably 3/4 of > >> the traffic has been requests to help customize distributions. > >> > >> I was wondering if it would make any sense at all to separate "the > >> further development of the anaconda toolset" and "the roll your own > >> distro starting with Fedora" into different lists? > > > > > > Not a lot I'd think. The volume is not high, those best able to answer > > would need to be on both lists to provide a service, and the questions > > here show what needs to be covered by anyone who feels an urge to document. > > > > > Speaking of feeling the urge to document, perhaps the list traffic will > change as more content is added to the Anaconda wiki, > http://fedoraproject.org/wiki/Anaconda. You almost have to have a brief > understanding of the anaconda development process at first to roll your > own. Hence, the traffic. The only problem is that once critical mass > has been attained few leave trails for others....but that's for the > Anaconda secrets book. ;-) If you have any brief snippets you'd like to > add to the wiki, then please let me know after you have added an account > here http://fedoraproject.org/wiki/UserPreferences. Adding content to > the wiki may be a better way to shape the traffic on this list than > dividing the list. > > Regards, > Greg > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.4 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iD8DBQFDA/iSxyxe5L6mr7IRAsQXAJ4jnGkNx0Mm0BmagzuckLNHHwWo6gCaA7dI > Q0jDEnuMLdt2qlbX0H9Nk80= > =3wS2 > -----END PGP SIGNATURE----- > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/anaconda-devel-list > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/anaconda-devel-list >
