On Dec 7, 2015, at 1:52 PM, Greg Lindahl <lindahl at pbm.com> wrote:> > On Mon, Dec 07, 2015 at 08:57:01PM +0100, Zdenek Sedlak wrote: > >> AFAIK, the 7(1503) format is used only on the websites, and internally >> CentOS uses 7.1.1503. Do you see this as an issue? > > Yes. It confuses humans. There have been a bunch of examples given of > how it confuses humans. A simple fix for this human issue is to use > 7.1.1503 on the website, here on the mailing list, etc.And then we?re right back in the same old boat: With every new release, the same old thread will pop up, ?How do I make my servers stay on CentOS 7.1?? Give up on the point release idea. It?s CentOS 7; there is no CentOS 7.1. The only reason there?s a YYMM part is that it?s a media respin. Best ignore that wherever practical.
J Martin Rushton
2015-Dec-07 23:42 UTC
[CentOS] Version numbering vis a vis CentOS and RHEL
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/12/15 22:37, Warren Young wrote:> On Dec 7, 2015, at 1:52 PM, Greg Lindahl <lindahl at pbm.com> wrote: >> >> On Mon, Dec 07, 2015 at 08:57:01PM +0100, Zdenek Sedlak wrote: >> >>> AFAIK, the 7(1503) format is used only on the websites, and >>> internally CentOS uses 7.1.1503. Do you see this as an issue? >> >> Yes. It confuses humans. There have been a bunch of examples >> given of how it confuses humans. A simple fix for this human >> issue is to use 7.1.1503 on the website, here on the mailing >> list, etc. > > And then we?re right back in the same old boat: With every new > release, the same old thread will pop up, ?How do I make my servers > stay on CentOS 7.1?? > > Give up on the point release idea. It?s CentOS 7; there is no > CentOS 7.1. The only reason there?s a YYMM part is that it?s a > media respin. Best ignore that wherever practical.So if we are to give up on the point release does that mean I don't have to update my machines until CentOS 8 comes along? ;-) Seriously though, since I have to build my own repos (air gap) and build the images for the diskless machines the point releases are important in tracking roughly which version particular nodes are on. Running yum update on a regular basis is just not an option. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJWZhltAAoJEAF3yXsqtyBlyAoP/2/kIa8gzhiNKoCRPFbFW/AT 2B15B/BDdBhIYN66Ux58cScMwfBt5Z9McozvWp2yJurr5CSrxG4wywXS6sfyRrYw 7J4oplTc5lmaxZkyQIidYVJ0Rwf9h0gCPx2TW7aoPcjh9YcqtjS4zZP1AHRuMY56 Wkt2RfuAaq3LUlRD4TwPNA3UMgvR18N3L9H7p2hXxYvswmKzWzTNt0M1AD8BeLBf S9cUSKGgAHikexjm6gmKQ2Nxb6xGcQE4lgPRCP/57cM5hX3rvhvTH4URj1+VUGw0 hd135wVk//AeK+lHXbm3ejNV/UC/sRx/JAOsaC2FYsBvfggsCuc0CUUxaGAOLZtt cfDLJgqKQdy59XAuWjRzw3Z4m+IPqSxeBopPDTwzUOiZQYxxOq2LZO2XQHzxbO+d VMqarwOp3n4nZvBDUeq+Q80LrrZtMGRlPtVA/YFHazVJPZ9Xo5ugV9QrdZrPO4kE LzrwjWevRT64g1mOInSSyWrOqFbXXMrZbAeJ88csUSTAaGwVDU3vZ3tAMuar8IKa k2IJBDBBDYQB5XZEkny5wTecS+/0B2M2ylEVyWe6GvvS5er+O6iop0Ej74O4OwGy FA7OwV7pzmWxnyzn4L/YUxAYSsSVL5rTdEAUGpFcetDd4oQssyV0Z9OtWKNeJIkx P+ZlCDMcxY08ajJenqm8 =SSct -----END PGP SIGNATURE-----
On Mon, Dec 07, 2015 at 03:37:27PM -0700, Warren Young wrote:> On Dec 7, 2015, at 1:52 PM, Greg Lindahl <lindahl at pbm.com> wrote: > > Yes. It confuses humans. There have been a bunch of examples given of > > how it confuses humans. A simple fix for this human issue is to use > > 7.1.1503 on the website, here on the mailing list, etc. > > And then we?re right back in the same old boat: With every new release, the same old thread will pop up, ?How do I make my servers stay on CentOS 7.1??I'm missing the connection. That's the kind of thing that's a FAQ. If you look back in this list archive, you'll see me answering that question here, and pointing out that the answer is buried in the FAQ on the website. (Never fixed despite many comments, but hey, why fix things that are problems?) I don't see why putting the same thing in /etc/centos-release and the website causes this problem to be significantly worse. I do see how the current "7 (1503)" on the website confuses many humans, including experienced CentOS admins.
On 7 Dec 2015 23:43, "J Martin Rushton" <martinrushton56 at btinternet.com> wrote:> > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 07/12/15 22:37, Warren Young wrote: > > On Dec 7, 2015, at 1:52 PM, Greg Lindahl <lindahl at pbm.com> wrote: > >> > >> On Mon, Dec 07, 2015 at 08:57:01PM +0100, Zdenek Sedlak wrote: > >> > >>> AFAIK, the 7(1503) format is used only on the websites, and > >>> internally CentOS uses 7.1.1503. Do you see this as an issue? > >> > >> Yes. It confuses humans. There have been a bunch of examples > >> given of how it confuses humans. A simple fix for this human > >> issue is to use 7.1.1503 on the website, here on the mailing > >> list, etc. > > > > And then we?re right back in the same old boat: With every new > > release, the same old thread will pop up, ?How do I make my servers > > stay on CentOS 7.1?? > > > > Give up on the point release idea. It?s CentOS 7; there is no > > CentOS 7.1. The only reason there?s a YYMM part is that it?s a > > media respin. Best ignore that wherever practical. > > So if we are to give up on the point release does that mean I don't > have to update my machines until CentOS 8 comes along? ;-) > > Seriously though, since I have to build my own repos (air gap) and > build the images for the diskless machines the point releases are > important in tracking roughly which version particular nodes are on. > Running yum update on a regular basis is just not an option.You should be updating during the lifecycle to each milestone though... To not do so is to leave yourself open to numerous bugs and attacks. As it is, as pointed out, you can still check the installed files from the centos-release package for the upstream it's based on and the YYMM respin date... Common configuration management systems (you should be using one of these given you say you have many systems) will also report the relevant details correctly. On top of this if you are maintaining your own internal air gapped repo you should be paying attention to announcements which will inform you at these milestone points... Given the workflow you state nothing has changed for you with the EL7.X releases...
On 07/12/15 23:42, J Martin Rushton wrote:> So if we are to give up on the point release does that mean I don't > have to update my machines until CentOS 8 comes along? ;-)on the flip side, ignore the point in time, assume you run /7/ and need to update as you go along, with the YYmm telling you how far adrift you are... in workloads where there is no real update in place ( think cloud, container, atomic etc ), its the only reference you get to a single package set. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc