I just use genhdlist
genhdlist --withnumbers --hdlist RedHat/base/hdlist /var/ftp/pub/ia64
copy the rpms you want into your dist directory, {/var/ftp/pub/ia64} for
us, then run the above command.
you will need to download genhdlist from off the web. i'm not sure, but I
think it was part of an anaconda rpm, can't remember where I got it.
anyways, it will rebuild comps, hdlist and hdlist2 for you, provided you
don't have duplicate rpm's. I use the automrg command from the autoupdate
package to make sure there are no duplicates.
This is also a good way of keeping your distribution directory uptodate
with the latest updates in case you need to reinstall a machine and don't
feel like installing 500mb's of updates. Works good on our cluster. We
have quite a few custom rpm's and non standard stuff we include, and this
works nicely...
Jason P Holland
Texas Learning and Computation Center
http://www.tlc2.uh.edu
University of Houston
Philip G Hoffman Hall rm 207A
tel: 713-743-4850
cell: 281-451-5991
On Tue, 15 Jul 2003, Mike Smith wrote:
> Robert Denton said:
> > That didn't work with some of the packages I attempted such as mrtg. Is
> > there a way to tell wat the "package" name of an RPM is? Is there such a
> > repository of information?
>
>
> Yeah, that shouldn't work. Like the other user said. You must rebuild your comps,
> hdlists and the like.
>
> What we use to do for RPM's that we build in house, is we take care of all the
> install stuff in %post by doing an ncftpget to grab all our packages and then we
> issue a :
>
> rpm -ivh /tmp/*.rpm >> /tmp/post-install.log
>
> Not the cleanest way since it will fail if your dependancies aren't in order. Write
> a script to give it some logic and you'll be golden.
>
> - Mike
>
>
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/kickstart-list
>
