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