4.8 is redhat-release-4ES-9 5.5 is redhat-release-5Server-5.5.0.2 So 5 might be relatively clean, but 4 won't be, at least for the minor. Rob Marti -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of inode0 Sent: Monday, June 28, 2010 2:54 PM To: General Red Hat Linux discussion list Subject: Re: /etc/redhat-release On Mon, Jun 28, 2010 at 2:15 PM, Stainforth, Matthew (SD/DS) <Matthew.Stainforth@xxxxxx> wrote: >> The "pain point" I mentioned was the inconsistent treatment of >> /etc/redhat-release which causes maintenance work for those of us who >> do need to parse it in scripts over time. We can expect distinct >> cases for each major release of RHEL but there have also been >> occasions where this file has changed in unpredictable ways across >> minor update levels as well. > > Have you thought about parsing the output of "rpm -q redhat-release"? > I have need of the same functionality and was going to use this approach. I just began with RHEL3 ... and over time it grew into a bit of a mess. If I were starting over I might consider this but I don't think the rpm release versions map all that cleanly onto major.minor release numbers either. If you find a slick way to do that though do share it. John -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
