<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>We have a number of vendors who require exact versions. We have several products that support exactly RHEL 6.2, down to specifying certain packages that can’t be patched from the version on the original media. We run RHEL on the production server, and
CentOS on the test and dev servers, and keep them at the same patch level. (Anything that doesn’t have weird vendor requirements goes on SLES). Also, we have a bureaucratic and fairly rigid change control process, so upgrading to the latest release (or even
applying patches) to many things is a huge ordeal. - this applies to most production systems that have a large user base. Luckily, I can usually get away with updating sshd and apache with only one meeting. A “zypper up” or “yum update” requires much more
red tape in most cases - depending on who owns the system, if it is high profile, etc…</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE">
<div>
<div>--</div>
<div>Allen Beddingfield</div>
<div>Systems Engineer</div>
<div>The University of Alabama</div>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>leam hall<br>
<span style="font-weight:bold">Reply-To: </span>Atlanta Linux Enthusiasts<br>
<span style="font-weight:bold">Date: </span>Thursday, May 7, 2015 at 4:41 PM<br>
<span style="font-weight:bold">To: </span>Atlanta Linux Enthusiasts<br>
<span style="font-weight:bold">Subject: </span>Re: [ale] CentOS repositories question<br>
</div>
<div><br>
</div>
<div>
<div>
<p dir="ltr">Why would you not stay with the current?</p>
<div class="gmail_quote">On May 7, 2015 5:36 PM, "Beddingfield, Allen" <<a href="mailto:allen@ua.edu">allen@ua.edu</a>> wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>
<div>
<div>Looks like I’m going to need a lot more disk space than I thought!</div>
<div>
<div>
<div>
<div>--</div>
<div>Allen Beddingfield</div>
<div>Systems Engineer</div>
<div>The University of Alabama</div>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
<div><br>
</div>
<span>
<div style="font-family:Calibri;font-size:12pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
<span style="font-weight:bold">From: </span>Brian Stanaland<br>
<span style="font-weight:bold">Reply-To: </span>Atlanta Linux Enthusiasts<br>
<span style="font-weight:bold">Date: </span>Thursday, May 7, 2015 at 4:33 PM<br>
<span style="font-weight:bold">To: </span>Atlanta Linux Enthusiasts<br>
<span style="font-weight:bold">Subject: </span>Re: [ale] CentOS repositories question<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">
<div>Jim's correct. This bit us once. We had systems set to update from "6" and were quite surprised when one of the packages we needed got updated. We changed to mirroring the 6.0 branch and everything was fine.<br>
<br>
</div>
--Brian<br>
<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, May 7, 2015 at 5:28 PM, Jim Kinney <span dir="ltr">
<<a href="mailto:jim.kinney@gmail.com" target="_blank">jim.kinney@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">The '6' repo is the latest in the 6 series. The 6.2 only has the release and patches for that exact version. That's why there's a 6.0 in the repo.</p>
<div class="gmail_quote">
<div>
<div>On May 7, 2015 5:24 PM, "Beddingfield, Allen" <<a href="mailto:allen@ua.edu" target="_blank">allen@ua.edu</a>> wrote:<br type="attribution">
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div>
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>I know there are a lot of CentOS users on the group, so I thought someone could answer this question….</div>
<div>Do the /centos/6/os/x86_64 and /centos/6/updates/x86_64 repos have all of the 6.x updates, or are these just for the 6.0 release? I noticed that there are variations for /centos/6.1/os/x86_64, /centos/6.1/updates/x86_64, all the way through 6.6. </div>
<div><br>
</div>
<div>Here is the reason I’m asking:</div>
<div>I’m finally getting around to pulling in the updates into our SUSE Manager server (Spacewalk-based), and I’m needing to pull down the repos into channels. Here is a brief description of that process:</div>
<div><a href="https://wiki.novell.com/index.php/SUSE_Manager/Managing_CentOS" target="_blank">https://wiki.novell.com/index.php/SUSE_Manager/Managing_CentOS</a></div>
<div><br>
</div>
<div>Do I actually need to pull down a separate set for 6 through 6.6, if I have systems at all those various releases, or will pulling down just “6” cover it? I was under the impression that it was the case, until I started poking around on one of the mirrors
and found specific ones for each release. I would just try it and find out, but it takes quite a while to pull one of these repos down.</div>
<div><br>
</div>
<div>Thanks.</div>
<div>Allen B.</div>
<div>
<div>
<div>
<div>--</div>
<div>Allen Beddingfield</div>
<div>Systems Engineer</div>
<div>The University of Alabama</div>
</div>
<div><br>
</div>
</div>
</div>
</div>
<br>
</div>
</div>
<span>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br>
</span></blockquote>
</div>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div>"Anyone who has never made a mistake has never tried anything new." -Albert Einstein<br>
<br>
</div>
</div>
</div>
</div>
</span></div>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br>
</blockquote>
</div>
</div>
</div>
</span>
</body>
</html>