User manual REDHAT NETWORK SATELLITE 5.1.0 CHANNEL MANAGEMENT

[. . . ] Red Hat Network Satellite Channel Management Guide 5. 1. 0 5. 1 ISBN: N/A Publication date: Red Hat Network Satellite Red Hat Network Satellite: Channel Management Guide 5. 1. 0 Copyright © 2008 Red Hat, Inc. Copyright © 2008 Red Hat, Inc. This material may only be distributed subject to the terms and conditions set forth in the Open Publication License, V1. 0 or later with the restrictions noted below (the latest version of the OPL is presently available at http://www. opencontent. org/openpub/). Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder. Distribution of the work or derivative of the work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder. [. . . ] Click Confirm to complete the action. Important This list differs from the package list available through the standard Software Channel Details page in that it displays all versions of a package remaining in the database, rather than just the latest. You may revert to a previous version of a package simply by removing the latest version. · Add -- Enables the addition of packages to the channel. To see available packages, select an option from the View dropdown menu and click View. To add packages to the channel you are editing, select the appropriate checkboxes and click Add Packages. Refer to Section 6, "Assigning Packages to Software Channels" for a discussion of this process. · Compare -- Enables the comparison of package lists between different channels. To see the differences, select another channel from the Compare to: dropdown menu and click Compare. A list appears showing all packages not contained by both channels and indicating the existing channel location of each. 4. Manage Software Packages In addition to adding and removing packages within channels, you also have the option of deleting packages entirely from both the database and file system. Removal from the file system is delayed by about one hour. This can be done through the Software Package Management page, accessed by clicking Manage Software Packages on the left navigation bar. Warning Although deleting packages from the database can be undone by uploading them again, they lose their association with any errata. Upon reloading, they must be re-associated with errata manually. Refer to Chapter 5, Custom Errata 16 Creating a Software Channel Management for instructions. To remove packages from the database, in the Software Package Management page, select an option containing them from the View dropdown menu and click View. Then select the appropriate checkboxes and click Delete Packages. A confirmation page appears with the packages listed. Click Confirm to delete the packages entirely. Since the actual packages are stored on the RHN Proxy Server, its custom packages cannot be downloaded through the RHN website, although they are listed. They must be retrieved by the client system using up2date. Since the RHN Satellite Server provides its own website, its custom packages are accessible via HTTP or Red Hat Update Agent. To obtain custom packages, the client system must be subscribed to the channel containing the packages. 5. Creating a Software Channel Before uploading packages to the server, a custom channel can be created to house them. Refer to Chapter 6, Uploading and Maintaining Custom Packages for instructions. [. . . ] Forces RHN Push to drop the username and password cache, then accept or ask for new ones. This is useful if you make a mistake entering them the first time. Push only the packages that are newer than those on the server. Note that source packages are special in that their versions are never compared to each other. -u , --username USERNAME -p , --password PASSWORD -s, --stdin -X, --exclude GLOB --force --nosig --new-cache --newest 30 Using the RHN Push application Option Description Their newness is dependent on their associated binary packages. [. . . ]