I was reading another thread, and this stuck out at me: "This issue was fixed by the CentOS team (and integrated into our install CD) prior to it''s release by the upstream provider." As patches and such are released - are they integrated into the current CD''s right away? So say for example, I downloaded the server CD a few months ago, then re-downloaded, would the patches from point a to point b already be integrated into the cd''s? Thanks!
dnk spake the following on 3/20/2006 9:48 AM:> I was reading another thread, and this stuck out at me: > > "This issue was fixed by the CentOS team > (and integrated into our install CD) prior to it''s release by the > upstream provider." > > As patches and such are released - are they integrated into the current > CD''s right away? So say for example, I downloaded the server CD a few > months ago, then re-downloaded, would the patches from point a to point > b already be integrated into the cd''s? > > Thanks!No. When a CD is released, it is frozen at that state. I think the only reason it might be patched would be for some sort of installer problem, but that would most likely be caught in testing "before" the cd images were released. The 4.2 cd is the same now as it was when released, and will only be replaced with the 4.3 cd. You just run a "yum upgrade" after the install to bring the system current. After the yum upgrade, a system installed from a 4.2 cd will be the equivalent of a system installed with a 4.0 (or 4.1) cd. But only after the yum upgrade.
Thanks.... I had thought that was the case, but it was the quote below that threw me off. Just wanted to be sure. On 20-Mar-06, at 11:05 AM, Scott Silva wrote:> dnk spake the following on 3/20/2006 9:48 AM: >> I was reading another thread, and this stuck out at me: >> >> "This issue was fixed by the CentOS team >> (and integrated into our install CD) prior to it''s release by the >> upstream provider." >> >> As patches and such are released - are they integrated into the >> current >> CD''s right away? So say for example, I downloaded the server CD a few >> months ago, then re-downloaded, would the patches from point a to >> point >> b already be integrated into the cd''s? >> >> Thanks! > No. When a CD is released, it is frozen at that state. I think the > only reason > it might be patched would be for some sort of installer problem, > but that > would most likely be caught in testing "before" the cd images were > released. > The 4.2 cd is the same now as it was when released, and will only > be replaced > with the 4.3 cd. You just run a "yum upgrade" after the install to > bring the > system current. After the yum upgrade, a system installed from a > 4.2 cd will > be the equivalent of a system installed with a 4.0 (or 4.1) cd. But > only after > the yum upgrade. > > _______________________________________________ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.centos.org/pipermail/centos/attachments/20060320/631654f9/attachment.htm
On Mon, 2006-03-20 at 12:25 -0800, dnk wrote:> Thanks.... I had thought that was the case, but it was the quote below > that threw me off. Just wanted to be sure.That was rolled into the official CD for CentOS because ... we don''t want to roll out a CD that breaks something as important as NIS authentication. Once the CD is released, it is done. That is one reason why we take 2 weeks before we release the CDs :)> > > > On 20-Mar-06, at 11:05 AM, Scott Silva wrote: > > > dnk spake the following on 3/20/2006 9:48 AM: > > > I was reading another thread, and this stuck out at me: > > > > > > > > > "This issue was fixed by the CentOS team > > > (and integrated into our install CD) prior to it''s release by the > > > upstream provider." > > > > > > > > > As patches and such are released - are they integrated into the > > > current > > > CD''s right away? So say for example, I downloaded the server CD a > > > few > > > months ago, then re-downloaded, would the patches from point a to > > > point > > > b already be integrated into the cd''s? > > > > > > > > > Thanks! > > No. When a CD is released, it is frozen at that state. I think the > > only reason > > it might be patched would be for some sort of installer problem, but > > that > > would most likely be caught in testing "before" the cd images were > > released. > > The 4.2 cd is the same now as it was when released, and will only be > > replaced > > with the 4.3 cd. You just run a "yum upgrade" after the install to > > bring the > > system current. After the yum upgrade, a system installed from a 4.2 > > cd will > > be the equivalent of a system installed with a 4.0 (or 4.1) cd. But > > only after > > the yum upgrade. > > > > > > _______________________________________________ > > CentOS mailing list > > CentOS@centos.org > > http://lists.centos.org/mailman/listinfo/centos > > > _______________________________________________ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.centos.org/pipermail/centos/attachments/20060320/46ee40dc/attachment.bin
On Mon, 2006-03-20 at 17:20 -0600, Johnny Hughes wrote:> On Mon, 2006-03-20 at 12:25 -0800, dnk wrote: > > Thanks.... I had thought that was the case, but it was the quote below > > that threw me off. Just wanted to be sure. > > That was rolled into the official CD for CentOS because ... we don''t > want to roll out a CD that breaks something as important as NIS > authentication. > > Once the CD is released, it is done. > > That is one reason why we take 2 weeks before we release the CDs :)---- much to the chagrin of one Mr. Smith. ;-) Craig
Craig White spake the following on 3/20/2006 3:34 PM:> On Mon, 2006-03-20 at 17:20 -0600, Johnny Hughes wrote: >> On Mon, 2006-03-20 at 12:25 -0800, dnk wrote: >>> Thanks.... I had thought that was the case, but it was the quote below >>> that threw me off. Just wanted to be sure. >> That was rolled into the official CD for CentOS because ... we don''t >> want to roll out a CD that breaks something as important as NIS >> authentication. >> >> Once the CD is released, it is done. >> >> That is one reason why we take 2 weeks before we release the CDs :) > ---- > much to the chagrin of one Mr. Smith. > > ;-) > > CraigHe should just look out for Mrs. Smith :-D