Chapter 2. Client Applications
2.1. Deploying the Latest Red Hat Network Client RPMs
yum, and Red Hat Network Registration Client (
rhn_register) on Red Hat Enterprise Linux 5 (
up2dateon earlier versions of Red Hat Enterprise Linux) are prerequisites for using much of Red Hat Network's enterprise functionality. It is crucial to install them on client systems before attempting to use RHN Proxy Server or RHN Satellite Server in your environment.
up2dateif earlier version of Red Hat Enterprise Linux) do not need to be performed. Those client tools should have no issues connecting to your RHN Satellite or Proxy environment. These discussion below assumes that the "out of box"
up2date) are not the latest and do not work for your environment.
firstbootafter installation or use the rhn_register. Systems running Red Hat Enterprise Linux 3 and 4 can use the registration functionality built into the Red Hat Update Agent.
up2date) for the first time by an administrator assuming the machines don't already have a working RHN. The administrator has populated the
/var/www/html/pub/directory with a copy of the
up2date) RPMs that the client systems need, and then has simply deployed those RPMs onto the client systems with a simple
rpm -Uvhcommand. Run from a client, this command installs the RPMs to that client, assuming the domain name, paths, and RPM versions are correct (note that this command has been split into multiple lines for print and PDF purposes but should be typed as one line at a shell prompt):
rpm -Uvh http://your_proxy_or_sat.your_domain.com/pub/rhn-setup-0.4.17-8.el5.i386.rpm http://your_proxy_or_sat.your_domain.com/pub/yum-3.2.8-9.el5.i386.rpm http://your_proxy_or_sat.your_domain.com/pub/pirut-1.3.28-13.3l5.noarch.rpm
i386) may need to be altered depending on the systems to be served.