If you have *deleted* any packages from base group, you'll have to modify
comps file one way or other:
1) you need to remove corresponding packages from definition of base group.
or
2) If you are listing ALL package names in %package section (as you do if
you generate ks.cfg by mkkickstart util), then you should turn off automatic
installation of all groups by changing the leading number "1" to "0" on the
line where the groups are defined.
For these changes, you don't need to run genhdlist util.
Yiping
> 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.
>
> 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.
>
> Second, will I just need to modify comps like Yiping suggested or
> am I going to have to use the genhdlist utility?
>
> 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?
>
> Am I going about this all wrong?
>
> Mike
>
>
> Michael Barsalou
> barjunk@xxxxxxxxxxxxx
>
>
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://listman.redhat.com/mailman/listinfo/kickstart-list
>
