Login | Register
My pages Projects Community openCollabNet

Discussions > users > Re: using current to distribute packages from RHN

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

current
Discussion topic

2020-03-13: This site is going to be decommissioned and shut down very soon. Please copy and archive any data you wish to keep ASAP

Hide all messages in topic

All messages in topic

Re: using current to distribute packages from RHN

Reply

Author darwinscusp
Full name Drew Myers
Date 2005-04-18 19:35:14 PDT
Message * Trevor Astrope (astrope at tabbweb dot com) wrote:
> On Mon, 18 Apr 2005, drew wrote:
>
> Yes. See my previous post regarding nrh-mirror-updates. Just use
> cadmin to create the channels, as described in the current guide.
> The tricky part is getting the correct release string. For rhel 3
> and rhel 4 it is 3ES and 4ES (thank you Jack!). I'm not sure about
> 2.1, but do an `rpm -q redhat-release' and use the field right
> after redhat-release in the package version.

Perfect, as usual. Thanks again!


drew
--

Courage is resistance to fear, mastery of fear - not absence of fear.
    - Mark Twain

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

Re: using current to distribute packages from RHN

Reply

Author Trevor Astrope <astrope at tabbweb dot com>
Full name Trevor Astrope <astrope at tabbweb dot com>
Date 2005-04-18 19:03:22 PDT
Message On Mon, 18 Apr 2005, drew wrote:

> I have several linux boxes (17) that run RHEL3, all of which have valid
> subscriptions. I have 2 other servers that run RHAS2.1, both of which
> have valid subscriptions. I'd like to use current to handle the
> necessary patching for these servers, but I'm not sure how to go about
> it.

Just create 2 channels with cadmin with the correct release string for
each channel.

> become available. What I'm curious about is 1) how do I then integrate
> these downloaded packages for use by current, and 2) is it possible to
> make one system download packages from RHN for an OS not installed on
> that system? In other words, could I designate a RHEL3 machine to
> download all packages for RHEL3 via RHN, *and* download all packages for
> RHAS2.1 via RHN, from the same system?

Yes. See my previous post regarding nrh-mirror-updates. Just use cadmin to
create the channels, as described in the current guide. The tricky part is
getting the correct release string. For rhel 3 and rhel 4 it is 3ES and
4ES (thank you Jack!). I'm not sure about 2.1, but do an `rpm -q
redhat-release' and use the field right after redhat-release in the
package version.


Hth,

Trevor

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

Re: using current to distribute packages from RHN

Reply

Author darwinscusp
Full name Drew Myers
Date 2005-04-18 16:05:31 PDT
Message * Josh (josh2780 at yahoo dot com) wrote:

<snip>

> How about allowing one of the RHAS2.1 machines up2date
> themselves, downloading the packages, and rsync them
> to your up2date / Current server?

Yes, I'm afraid that's the road I'll have to take. It doesn't seem
like this is such an unusual request, but I guess that's why RedHat
has a software package available for purchase to handle it.

Any takers for #1?


drew
--

Always acknowledge a fault. This will throw those in authority off their guard and give you an opportunity to commit more.
    - Mark Twain

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

Re: using current to distribute packages from RHN

Reply

Author Josh <josh2780 at yahoo dot com>
Full name Josh <josh2780 at yahoo dot com>
Date 2005-04-18 16:00:02 PDT
Message To answer #2... I've given this some thought in the
past as well. Because up2date compares your current
rpm database to the channel you are subscribed to, it
would seem you would have to maintain 2 seperate rpm
databases to get this to work... that is, if you
wanted to fetch the updates from RHN as it seems you
do. This wasn't such a big deal on previous versions
of RH since you could download the packages from a
redhat mirror to fetch packages for all sorts of
releases. So my first thought would be "No" this
couldn't work by using up2date and RHN. Someone may
have a different opinion or know of a piece of
software that can handle this.

How about allowing one of the RHAS2.1 machines up2date
themselves, downloading the packages, and rsync them
to your up2date / Current server?




--- drew <drew at sundawg dot org> wrote:
> Hi,
>
> This question was introduced in a different thread,
> but I have an
> additional wrinkle, so I'll pose it separately.
>
> I have several linux boxes (17) that run RHEL3, all
> of which have valid
> subscriptions. I have 2 other servers that run
> RHAS2.1, both of which
> have valid subscriptions. I'd like to use current
> to handle the
> necessary patching for these servers, but I'm not
> sure how to go about
> it.
>
> I realize I can use up2date to download packages
> from RHN from one
> machine. I could probably even reconfigure that
> machine so it carries
> every available package, so I can download all
> package updates as they
> become available. What I'm curious about is 1) how
> do I then integrate
> these downloaded packages for use by current, and 2)
> is it possible to
> make one system download packages from RHN for an OS
> not installed on
> that system? In other words, could I designate a
> RHEL3 machine to
> download all packages for RHEL3 via RHN, *and*
> download all packages for
> RHAS2.1 via RHN, from the same system?
>
> Thanks,
>
>
> drew
> --
>
> There are only two ways of telling the complete
> truth--anonymously and posthumously.
> - Thomas Sowell (1930 - )
>
>
--------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail:
> users-unsubscribe@cu​rrent.tigris.org
> For additional commands, e-mail:
> users-help at current dot tigris dot org
>
>

____________________​____________________​__________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

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

using current to distribute packages from RHN

Reply

Author darwinscusp
Full name Drew Myers
Date 2005-04-18 15:50:11 PDT
Message Hi,

This question was introduced in a different thread, but I have an
additional wrinkle, so I'll pose it separately.

I have several linux boxes (17) that run RHEL3, all of which have valid
subscriptions. I have 2 other servers that run RHAS2.1, both of which
have valid subscriptions. I'd like to use current to handle the
necessary patching for these servers, but I'm not sure how to go about
it.

I realize I can use up2date to download packages from RHN from one
machine. I could probably even reconfigure that machine so it carries
every available package, so I can download all package updates as they
become available. What I'm curious about is 1) how do I then integrate
these downloaded packages for use by current, and 2) is it possible to
make one system download packages from RHN for an OS not installed on
that system? In other words, could I designate a RHEL3 machine to
download all packages for RHEL3 via RHN, *and* download all packages for
RHAS2.1 via RHN, from the same system?

Thanks,


drew
--

There are only two ways of telling the complete truth--anonymously and posthumously.
    - Thomas Sowell (1930 - )

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