Login | Register
My pages Projects Community openCollabNet

Discussions > users > Re: RedHat ES4 > Reply to message

Project highlights: Stable Version: 1.6.1, Development Version: 1.7.6

current
Reply to message

* = Required fields
* Subject
* Body
Attachments
Send reply to
Topic
Author (directly in email)
Please type the letters in the image above.

Original message

Author Trevor Astrope <astrope@tabbweb.com>
Full name Trevor Astrope <astrope@tabbweb.com>
Date 2005-04-18 18:51:44 PDT
Message On Mon, 18 Apr 2005, drew wrote:

> I have a similar setup, except I have valid subscriptions for all my
> linux boxes (numbering 20 or so). However, I too, would like to have
> one system download all the updates via RHN, then distribute them via
> current to the remaining machines on the network. This way, only one
> hole through the firewall is required, and I can choose which machines
> to update with which software, as I see fit (development boxes
> immediately, production boxes after a "burn in" period).

This is exactly what I'm doing. My situation is identical to yours, right
down to the number of subscribed machines.

All you need to do is get the nrh-up2date package from nrh-up2date.org and
install these 2 scripts: nrh-mirror-updates and nrh-clean-repository

You only need nrh-clean-repository if you want to easily remove old
packages from the repositories.

The configuration instructions are contained in the script, at the top.
They're pretty self-explanitory.

Just ignore the rest of nrh-up2date, as current is a better solution for
an up2date server and I don't think nrh-up2date is no longer maintained.

You will need to modify the nrh-mirror-updates script to import base64 and
modify the script to base64 decode the packageList before decompressing
it, like below:

                     packageList = base64.decodestring(​packageList)
                     packageList = zlib.decompress(packageList)

This only occurs twice in nrh-mirror-updates. I can send you a patch if
you want...

After configuring nrh-mirror-updates, it will download every package from
rhn for the channels you configured. On subsequent runs it will only
download newer packages. You can then use nrh-clean-repository to remove
the old packages from the repository.

I had repositories for 2.1 3 and 4, all on the same machine, as
nrh-mirror-updates looks for the systemid files in its own config
directory for each channel, so you can use it for multiple channels
simultaineously, as long as you have valid systemid files for each
channel. It won't touch your up2date configuration, so you can use up2date
on the same machine to update against the current server.

All you have to do is run `cadmin add_dir' against the nrh repository
directory for each channel. Then `cadmin scan_channel' to populate the
corresponding current channel.

Besides being able to use nrh-mirror-updates to get the updates from rhn
and up2date to get the updates from the current server, you have the added
advantage of having a completely up to date repository containing the most
recent versions of all packages, even the ones you haven't yet installed.

  As part of my goal to learn python, I am going to try and integrate
nrh-mirror-updates into cadmin, so you can do `cadmin update_channel' to
populate and update your current channels from an upstream repository.

Hope this helps,

Trevor


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@cu​rrent.tigris.org
For additional commands, e-mail: users-help at current dot tigris dot org