[Clip] clip.ks and setools package

Gallucci, John (US SSA) john.gallucci at baesystems.com
Mon Apr 25 19:10:26 CDT 2011


Since the @base group is the very first package listed, I imagine it means that your yum repository to the local DVD isn't setup correctly.  I would double check that you have properly configured your yum repo.  The best way to test it out is to manually configure a running Linux machine with the yum configuration and do a 'yum -y install clip' (or any other package on the DVD) and verify that packages can be successfully installed from the DVD.

I think during the kickstart installation you can change to TTY3 (or TTY2 I can't remember) and issue that command.

-John.


-----Original Message-----
From: Ted Toth [mailto:txtoth at gmail.com] 
Sent: Monday, April 25, 2011 5:04 PM
To: Gallucci, John (US SSA)
Cc: clip at oss.tresys.com
Subject: Re: [Clip] clip.ks and setools package

Thanks I'll try this. I'm also having a problem when I do an install using the clip iso where it complains that there is no base group have you seen this issue? I looked at the comps.xml in the iso but it isn't text (XML) it looks like binary data.

Ted

On Mon, Apr 25, 2011 at 3:12 PM, Gallucci, John (US SSA) <john.gallucci at baesystems.com> wrote:
> The packages under "Remove Packages for PL4 Compliance" needs to be updated.  Last month I submitted a modified kickstart configuration for review and have yet to receive any feedback.  About 90% of the packages that are being explicitly removed are not installed in the first place.  This is due to the fact that the package groups are commented out (the sections with the @).  Because the groups are not installed, it is not necessary to explicitly remove these packages.  I imagine these were just left behind in case someone wanted to enable a packages (e.g. base-x) and needed to know which ones from that group need to be removed.
>
> Since this form isn't attachment friendly, below is the package section for the modified kickstart I have suggested.  In my testing this truncated kickstart yields the same package installation footprint as the original clip.ks file.
>
> -----------------begin section of clip.ks------------------------- # 
> Install Packages.  This is site specific.
> %packages
> @base
>
> #########################
> # Add Packages for CLIP #
> #########################
> aide
> audit
> policycoreutils-newrole
> ruby
> setools
> sysstat
> vlock
>
> #####################################
> # Remove tcpdump per STIG gen003865 #
> #####################################
> -tcpdump
>
> ############################################
> # Remove (BASE) Packages for PL4 compliance# 
> ############################################
> -NetworkManager
> -autofs
> -bluez-utils
> -finger
> -irda-utils
> -nfs-utils
> -rsh
> -telnet
> -wireless-tools
> -ypbind
> -yum-updatesd
> ----------------end section of clip.ks---------------------------
>
> John Gallucci IV | Senior Systems Engineer
> Phone: 858.592.5499 | Cell: 858.776.6820 BAE Systems, Inc., 
> Information Solutions
> 10920 Technology Pl. | San Diego, CA 92129
>
> -----Original Message-----
> From: clip-bounces at oss.tresys.com [mailto:clip-bounces at oss.tresys.com] 
> On Behalf Of Ted Toth
> Sent: Monday, April 25, 2011 2:26 PM
> To: clip at oss.tresys.com
> Subject: [Clip] clip.ks and setools package
>
> Why does the kickstart include and then exclude the setools package?
>
> Ted
> _______________________________________________
> Clip mailing list
> Clip at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/clip
>


More information about the Clip mailing list