Manage Config Channels - Red Hat NETWORK 4.0.5 Reference Manual

128 Chapter 6. Red Hat Network Website
To list all packages in the channel, click the List / Remove Packages link. Check the box
to the left of any package you wish to remove, then click the Remove Packages button in
the lower right of the page.
To add packages, click the Add Packages link. Choose a channel from which to select
packages from the drop-down menu and click the View button to continue. Check the box
to the left of any package you wish to add to the channel, then click the Add Packages
button in the bottom right of the screen.
To compare packages within the current channel with those of another channel, select the
other channel from the drop-down menu and click the Compare button. All packages
present in either channel are compared, and the results displayed on the next screen. This
information includes the architecture and version of each package.
To make the two channels identical, click the Merge Differences button in the lower right.
The following screen allows you to select how conflicts are resolved. Click the Preview
Merge button to view the results of the merging without making any changes to the chan-
nels. Finally, select those packages that you wish to merge and click the Merge Packages
button followed by the Confirm button to perform the merge.
6.6.5.2. Manage Software Channels ⇒ Manage Software Packages
This tab allows you to manage custom software packages owned by your organization. You
may view a list of all custom software or view only those packages in a selected custom
channel. To select the channel whose custom packages you wish to view, select the channel
from the drop-down menu and click the View button.
6.6.6. Manage Config Channels —
Provides the means to create and oversee channels containing configuration files. You must
be a Configuration Administrator or Organization Administrator to view this section of the
website. Like software channels, configuration channels store files to be installed on sys-
tems. Unlike software packages, various versions of configuration files may prove useful
to a system at any given time. Further, RHN allows you to include variables, or macros,
that allow you to treat your configuration files as templates that can be deployed across
your organization, with the relevant values populated upon individual system installation.
Please note that whenever a configuration file is deployed via RHN, a backup of the previ-
ous file including its full path is made in the directory on
/var/lib/rhncfg/backups/
the affected system. The backup retains its filename but has a exten-
.rhn-cfg-backup
sion appended.