Dave, You're looking at the wrong file, s390/RedHat/base/packages.server, and not s390/RedHat/base/list. If you look at s390/RedHat/base/list, you'll see fully qualified file names.
My guess is that what is happening during the install process is grossly something like this: for pkgname in `cat base/$packagelist `;do rpmname=`grep $pkgname base/list; install_package_named $rpmname;done This would allow them to keep the server.package, etc., files fairly constant, and only update the master "list" file with the new names of the RPM files. The method also avoids the need to parse the output of the FTP server, making it possible to use any kind of FTP server for the installation CDs. Mark Post -----Original Message----- From: Dave Myers [mailto:[EMAIL PROTECTED]] Sent: Monday, January 28, 2002 6:12 PM To: [EMAIL PROTECTED] Subject: Re: RH rhsetup "server" install did not install Samba RPM's In a message dated 1/28/2002 3:03:20 PM Mountain Standard Time, [EMAIL PROTECTED] writes: > Dave, > > Make sure that the file name in s390/RedHat/base/list matches _exactly_ the > RPM name in s390/RedHat/RPMS. Getting the "list" file out of sync with the > real RPM names can cause this kind of problem. > > Mark Post > It doesn't look to me like ANY of the filenames in the list match the RPM name exactly.... just the first node. For example, the list has this: samba-common samba samba-client wu-ftpd anonftp cpp perl-DBI curl I noticed that 30 RPMs did not get installed and the list spelling looks correct. Do you think the "rhsetup" install.log will point out why these 30 did not get installed or do I need to tweak "rhsetup" first to add some (-v ?) flag to the embedded rpm command ?????? Tia Dave
