> 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
I've not looked, but I suspect you will find the list contains package names truncated at the lest-most '-[0-9]' and that there will only be one match (except in those cases where there are architecture-dependent choices as i686 for P II and later, i386 for pre- P II). For example, an entry of "kernel-" (or kernel) would match kernel-2.4.7-13 or kernel-0.2 but not kernel-BOOT. It would be an error to have more than one match. My RHL 7.2 package has RedHat/base/comps - a text file with contents like this: [summer@numbat base]$ grep kernel comps kernel i386: kernel-pcmcia-cs kernel-headers kernel-source [summer@numbat base]$ The kernel entry would not match kernel-pcmcio-cs, kernel-headers etc. > > 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. As does this format. > -- Cheers John Summerfield Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Note: mail delivered to me is deemed to be intended for me, for my disposition.
