Michael Barsalou wrote:
Here is how I was planning to use kickstart:
First, I was going to setup the machine to have all the packages
that I wanted and remove those that I didn't.
Then I was going to use the mkkickstart utility to create my ks.cfg.
That way I would have a ks.cfg file that could potentially put the
machine back together just by putting in the boot disk and the CD-
rom.
I haven't had much luck with mkkickstart, but I haven't tried it in well
over a year, so I guess it has improved much since then.
However, I see a few problems:
First, I don't need two CD's. The rpm's that I am using only take up
about 140mb of diskspace.
You can burn a fresh CD with just the ones you need (from both
disks)...I don't even use CD's at all, I've just copied them into a
single directory on a NFS server. I always regen my hdlist, so this may
not work without rerunning genhdlist.
Second, will I just need to modify comps like Yiping suggested or
am I going to have to use the genhdlist utility?
I think it depends on whether the packages change. I compile several of
my own RPMs, so I have to run it for sure.
If I do have to use genhdlist utility, is there a way just to get the
binary of that? I tried using the anaconda rpm, but the machine
has no development stuff loaded on it. Maybe there is an easier
way?
I had to strip it out of the anaconda package and compile it by hand
(since I didn't have an X equipped machine handy and the anaconda
package has a ton of dependencies). I hollered about it on BugZilla,
and the good folks at Red Hat have fixed this for 7.2, I think.
Am I going about this all wrong?
Nope. Just about right, I think.
--
Joe Cooper <joe@xxxxxxxxxxxxx>
Affordable Web Caching Proxy Appliances
http://www.swelltech.com
