[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: RH8 Package specification in Kickstart



Dave,

I think I understand what your customer is doing, it's something I do all
the time, but it takes a bit of work!

First up, you need to understand what is going on with package groups in the
comps file.

There are some key groups you can't get away from installing. Anaconda will
always install @base, and @base requires @core and @dialup.

You can only trim this basic list of packages by explicitly removing the
packages, which is done by preceding the package name with "-".

Some packages simply can't be removed from the list (usually because they're
prerequisites for other things you want, eg cyrus-sasl-*), and some things
are dangerous to remove (eg authconfig, which anaconda needs)

So I use a mixture, coupled with exhaustive refinement. I explicitly do not
install any package I don't want, and explicitly install the ones I do (I
find selecting whole groups just dragged in too much crud). Then, in the
postinstall script, I remove the stuff I don't want, or no longer need, with
a "rpm -e --nodeps <list>"

So, an example might help (warning: this build is not for the
faint-hearted!), from RH9, rather than RH8.0, but you'll get the idea:

------ <Cut Here>------
#Package install information
%packages --resolvedeps
#Core
-ash
-hotplug
-setserial
-lilo
#Base
-acl
-anacron
-apmd
-at
-authconfig
-autofs
-bc
-bind-utils
-cyrus-sasl-plain
-cyrus-sasl
-dhclient
-dos2unix
-dosfstools
-dump
-ethtool
-expat
-fbset
-finger
-ftp
-gmp
-hesiod
-iptables
-irda-utils
-kbdconfig
-ksymoops
-libuser
-lilo
-lokkit
-mailcap
-man
-man-pages
-mkbootdisk
-pcre
-procmail
-quota
-reiserfs-utils
-sendmail
-setuptool
-specspo
-timeconfig
-usbutils
-usermode
binutils
compat-libstdc++
cpp
cproto
db3-devel
dev86
gcc
glibc-devel
glibc-kernheaders
gmp
gmp-devel
gnupg
libcap
make
ncompress
ncurses-devel
openssl-devel
ntp
patch
perl
perl-CPAN
pam-devel
stat
tcpdump
zlib-devel

%post
    
# Remove RPMs we don't like
rpm -e --nodeps authconfig setserial raidtools pciutils rmt openldap
cyrus-sasl cyrus-sasl-md5 krb5-libs indexhtml eject kudzu dhcpd
------ <Cut Here>------

Does that help?

Regards,

Mike

-----Original Message-----
From: Dave Mackintosh [mailto:redhat-list xdroop com]
Sent: Saturday, 18 October 2003 12:48 AM
To: kickstart-list redhat com
Subject: RH8 Package specification in Kickstart


Greetings, list
 
I've had some moderate success with RedHat 7.2, 7.3, and 8.0 doing
basic Kickstarts (ones where the packages are specified as
@Everything).  However we've hit a situation where one customer has
decided he wants every RedHat 8.0 machine to only have a specific
list of packages installed.

I've tried just putting the list of packages in the ks.cfg (ie, no @
groups) but I get the dreaded anaconda python death.

There has been at least one other request of this nature to the list
(http://www.redhat.com/archives/kickstart-list/2003-April/msg00099.html)
but other than a suggestion to change the CD image (do I have to edit
comps.xml if I do this?) I don't see much in the way of answers.

Can anyone give me pointers to where I might find how to proceed?
Is ordering important?

Thanks for your time.

-- 
 /\oo/\
/ /()\ \ David Mackintosh | 


_______________________________________________
Kickstart-list mailing list
Kickstart-list redhat com
https://www.redhat.com/mailman/listinfo/kickstart-list


IMPORTANT NOTICE
This communication including any file attachments is intended solely for the use
of the individual or entity to whom it is addressed. If you are not the intended recipient,
or the person responsible for delivering this communication to the intended recipient,
please immediately notify the sender by e-mail and delete the original transmission and
its contents. Any unauthorised use, dissemination, forwarding, printing, or copying of
this communication including any file attachments is prohibited.

It is your responsibility to scan this communication including any file attachments for
viruses and other defects. To the extent permitted by law, ING and its associates
will not be liable for any loss or damage arising in any way from this communication
including any file attachments.




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]