Red Hat NETWORK SATELLITE 5.3.0 Deployment Manual page 43

beta distribution's contents to /var/satellite/custom-distro/rhel-i386-server-5.3-
beta/
4. Create a custom software channel with the Satellite web interface. (Navigate to Channel =>
Manage Software Channels => Create Channel) and create a base channel with an appropriate
name and label. In keeping with the example RHEL beta version above, we might use the label
rhel-5.3-beta.
5. Push the software packages (rpm files) from the tree location to the newly created software
channel. Given our example above, you would do so by running
rhnpush --server=http://localhost/APP -c 'rhel-5.3-beta' -d /var/satellite/custom-distro/
rhel-i386-server-5.3-beta/Server/
Note that the sub-directory within the tree may be different depending on your distribution. Once
this step is complete, you may delete all of the RPM files from the appropriate directory within the
tree path. In this example, run the following:
rm /var/satellite/custom-distro/rhel-i386-server-5.3-beta/Server/*.rpm
The packages are still stored on the Satellite server within the channel and thus are not needed
within the kickstart tree. Although this entire step is optional, having the packages in a software
channel allows them to be installed onto the system as needed (using yum) and not solely at the
time of kickstart.
6. Create the Distribution within the Satellite's web interface. Navigate to Systems => Kickstart =>
Distributions => Create New Distribution. Provide an appropriate label, the full tree path (/
var/satellite/custom-distro/rhel-i386-server-5.3-beta/ in our case), select the
base channel we created earlier, and then the correct Installer Generation. We would select Red
Hat Enterprise Linux 5 for this distribution. Finally select Create Kickstart Distribution.
7. You may want to clone a rhn-tools child channel from an existing Red Hat Enterprise Linux base
channel to be a child of your newly created base channel.
Manually Installed Kickstart Trees
35