Hi,
I have the following queries regarding "yum.conf" :
1. How can I define the channels for specific groups.
2. How can I let the groups have access to certains channels only.
3. How a normal user exclude the packages he/she doesn;t want to install
without specifying anything in the yum.conf (as he doesn't have the access
for modifying the file)
Looking forward to your help
Thanks in advance,,,,,
Regards, Harish Chauhan
yum-request@xxxxxxxxxxxxxxxxxxxx
Sent by: yum-bounces@xxxxxxxxxxxxxxxxxxxx
12/11/2003 12:00 PM
Please respond to
yum
To
yum@xxxxxxxxxxxxxxxxxxxx
cc
Subject
Yum Digest, Vol 5, Issue 13
Send Yum mailing list submissions to
yum@xxxxxxxxxxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.dulug.duke.edu/mailman/listinfo/yum
or, via email, send a message with subject or body 'help' to
yum-request@xxxxxxxxxxxxxxxxxxxx
You can reach the person managing the list at
yum-owner@xxxxxxxxxxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Yum digest..."
Today's Topics:
1. Re: Retrieving packages from Red Hat Network (Ian Masterson)
2. Re: Retrieving packages from Red Hat Network (Ian Masterson)
3. Re: Retrieving packages from Red Hat Network (Jim Wildman)
4. Re: Retrieving packages from Red Hat Network (Robert G. Brown)
5. Re: Retrieving packages from Red Hat Network (seth vidal)
6. Re: Retrieving packages from Red Hat Network (Jim Wildman)
----------------------------------------------------------------------
Message: 1
Date: Wed, 10 Dec 2003 13:58:54 -0800 (PST)
From: Ian Masterson <ian@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [Yum] Retrieving packages from Red Hat Network
To: "Yellowdog Updater, Modified" <yum@xxxxxxxxxxxxxxxxxxxx>
Message-ID:
<Pine.LNX.4.58.0312101335080.22856@xxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Tue, 9 Dec 2003, Joseph Tate wrote:
> You could go through a caching web proxy.
> If you have enough systems to warrant it, you can purchase the RHN to
> run locally (though I can't remember what this product is called, or how
> much it costs).
We have a local RHN proxy. It is sold along with the RHEL licenses, since
Red Hat would (understandably) prefer that they provide only the bandwidth
required to send packages to your site once rather than to every computer
individually.
Unfortunately, we'd have the same problem as running 'up2date -d'. The RHN
proxy only caches those packages which have been requested by clients. It
doesn't seem to be any easier to get all packages from an RHN proxy than
it is to do the same directly from RHN.
> Generally, however, unless bandwidth on your end is a limiting factor,
> using up2date on each server is recommended, as there's a whole lot more
> that you can do with RHN than keep your servers up to date.
I agree that RHN is nifty, but there are things we can do with yum that
aren't as easy (or perhaps possible) with RHN.
Thanks,
Ian Masterson
Dept. of Electrical Engineering (SSLI)
University of Washington, Seattle
------------------------------
Message: 2
Date: Wed, 10 Dec 2003 14:01:34 -0800 (PST)
From: Ian Masterson <ian@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [Yum] Retrieving packages from Red Hat Network
To: "Yellowdog Updater, Modified" <yum@xxxxxxxxxxxxxxxxxxxx>
Message-ID:
<Pine.LNX.4.58.0312101359560.22856@xxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Wed, 10 Dec 2003, seth vidal wrote:
> I'm pretty sure this is a way to request the packages available via the
> xmlrpc interface to rhn. You should ask your sales rep about this. I
> know it's not something they object to.
>
> -sv
Thanks, Seth. I'll see if he has anything to suggest.
-Ian
------------------------------
Message: 3
Date: Wed, 10 Dec 2003 17:03:40 -0500 (EST)
From: Jim Wildman <jawildman@xxxxxxxxxxxxx>
Subject: Re: [Yum] Retrieving packages from Red Hat Network
To: "Yellowdog Updater, Modified" <yum@xxxxxxxxxxxxxxxxxxxx>
Message-ID:
<Pine.LNX.4.58.0312101702170.3197@xxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Wed, 10 Dec 2003, Ian Masterson wrote:
>
> Unfortunately, we'd have the same problem as running 'up2date -d'. The
RHN
> proxy only caches those packages which have been requested by clients.
It
> doesn't seem to be any easier to get all packages from an RHN proxy than
> it is to do the same directly from RHN.
So grab an old box, put 'everything' on it and register it. Or
designate one of your newer boxes for the same purpose. And mark, 'save
packages after installation' and 'retrieve source rpms'.
------------------------------------------------------------------------
Jim Wildman, CISSP, RHCE jim@xxxxxxxxxxxxx
http://www.rossberry.com
------------------------------
Message: 4
Date: Wed, 10 Dec 2003 17:10:13 -0500 (EST)
From: "Robert G. Brown" <rgb@xxxxxxxxxxxx>
Subject: Re: [Yum] Retrieving packages from Red Hat Network
To: "Yellowdog Updater, Modified" <yum@xxxxxxxxxxxxxxxxxxxx>
Message-ID:
<Pine.LNX.4.44.0312101706130.12467-100000@xxxxxxxxxxxxxxxxxxx>
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Wed, 10 Dec 2003, Jim Wildman wrote:
> On Wed, 10 Dec 2003, Ian Masterson wrote:
>
> >
> > Unfortunately, we'd have the same problem as running 'up2date -d'. The
RHN
> > proxy only caches those packages which have been requested by clients.
It
> > doesn't seem to be any easier to get all packages from an RHN proxy
than
> > it is to do the same directly from RHN.
>
> So grab an old box, put 'everything' on it and register it. Or
> designate one of your newer boxes for the same purpose. And mark, 'save
> packages after installation' and 'retrieve source rpms'.
Or beat RH about the head and ears about wanting a trivial software tool
that doesn't require hundreds of users to burn an entire computer doing
something that is clearly a useful and common thing to do well within
the capabilities of simple software.
That would work even better.
I'm not sure that "everything" would install on any single box. What
are you going to do about installing smp kernels on a non-SMP box? What
about add-on packages? What about package dependency conflicts (which
should not exist, of course:-)?
Maybe they should just provide a button that says "build local yum
repository"...
rgb
>
> ------------------------------------------------------------------------
> Jim Wildman, CISSP, RHCE jim@xxxxxxxxxxxxx
> http://www.rossberry.com
> _______________________________________________
> Yum mailing list
> Yum@xxxxxxxxxxxxxxxxxxxx
> https://lists.dulug.duke.edu/mailman/listinfo/yum
>
Robert G. Brown
http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567 Fax: 919-660-2525 email:rgb@xxxxxxxxxxxx
------------------------------
Message: 5
Date: 10 Dec 2003 17:15:59 -0500
From: seth vidal <skvidal@xxxxxxxxxxxx>
Subject: Re: [Yum] Retrieving packages from Red Hat Network
To: "Yellowdog Updater, Modified" <yum@xxxxxxxxxxxxxxxxxxxx>
Message-ID: <1071094559.32740.75.camel@opus>
Content-Type: text/plain
On Wed, 2003-12-10 at 17:03, Jim Wildman wrote:
> On Wed, 10 Dec 2003, Ian Masterson wrote:
>
> >
> > Unfortunately, we'd have the same problem as running 'up2date -d'. The
RHN
> > proxy only caches those packages which have been requested by clients.
It
> > doesn't seem to be any easier to get all packages from an RHN proxy
than
> > it is to do the same directly from RHN.
>
> So grab an old box, put 'everything' on it and register it. Or
> designate one of your newer boxes for the same purpose. And mark, 'save
> packages after installation' and 'retrieve source rpms'.
Short of a --force you can't install i686 and athlon kernels on the same
system.
-sv
------------------------------
Message: 6
Date: Wed, 10 Dec 2003 18:20:03 -0500 (EST)
From: Jim Wildman <jawildman@xxxxxxxxxxxxx>
Subject: Re: [Yum] Retrieving packages from Red Hat Network
To: "Yellowdog Updater, Modified" <yum@xxxxxxxxxxxxxxxxxxxx>
Message-ID:
<Pine.LNX.4.58.0312101818190.3197@xxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Wed, 10 Dec 2003, seth vidal wrote:
> Short of a --force you can't install i686 and athlon kernels on the same
> system.
Good point. But it goes a long way.
------------------------------------------------------------------------
Jim Wildman, CISSP, RHCE jim@xxxxxxxxxxxxx
http://www.rossberry.com
------------------------------
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxxxxx
https://lists.dulug.duke.edu/mailman/listinfo/yum
End of Yum Digest, Vol 5, Issue 13
**********************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.dulug.duke.edu/pipermail/yum/attachments/20031211/6b5bde13/attachment.htm
