[tools] of mrepo, RHN, and managing Entitlements....

[Jason Murphy]

>From our legal teams point of view, we need to have a 1:1 association,
>meaning that whether we use RHN or not for updates, we need to have
each >system registered with RHN(or satellite in the future) and have a
valid RHN >update entitlement for each system that is registered.

I spoke to a Red Hat sales person (Specifically, one that handles
government and defense contractor sales) and I had them make it clear
that our servers and desktops did not have to register with RHN but we
had to make sure we has licenses for all of our Red Hat products in
either paper form or in RHN. I simply told them that it was not possible
for many of our servers and desktops to talk to RHN. They understood
that we simply did not want any server talking to the outside world.

--
Jason Murphy
Jason.Murphy at uav.com
Unix/Linux Systems Administrator
General Atomics Aeronautical Systems, Inc.


Thanks,
Brent C.

 
On 1/2/08, Caerie Houchins <cdhouch at gmail.com> wrote: 

	On Jan 2, 2008 10:01 AM, Ray Van Dolson <rvandolson at esri.com>
wrote: 
	> > Would like to know what people do in this case as well :)
	
	My understanding has always been that as long as you don't
depend on
	RedHat for support, you don't need to register a system on RHN.
We 
	never bother with RHN and simply have one license per type of
system
	we have, use mrepo to sync the channels down locally, then feed
all
	the systems off of that.
	
	Did we misunderstand how that works?
	-- 
	Caerie Houchins
	_______________________________________________
	tools mailing list
	tools at lists.rpmforge.net
	http://lists.rpmforge.net/mailman/listinfo/tools
<http://lists.rpmforge.net/mailman/listinfo/tools>