SCIENTIFIC-LINUX-USERS Archives

May 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Akemi Yagi <[log in to unmask]>
Reply To:
Akemi Yagi <[log in to unmask]>
Date:
Wed, 25 May 2011 08:02:59 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
On Wed, May 25, 2011 at 7:42 AM, Troy Dawson <[log in to unmask]> wrote:
> On 05/25/2011 02:31 AM, Marc Muehlfeld wrote:

>> Question 2: The default *.repo uses the $releasever variable, which is
>> resolved to "6.0". If we plan to always have the newest (minor) version
>> after
>> every update, I think I have to replace that. Is there an other variable
>> for
>> that or do I have to hardcode it?
>>
>
> There are two ways to do this.
> 1 - Hardcode it to point to 6x or 6
> (Will have to do this after each update)
> 2 - yum install yum-conf-sl6x
> (This installs another yum yum repository that points to 6x.  Because it is
> separate from sl-release, it can remain constant what the sl-release is
> updated.)

Troy, you could have referred to your own FAQ [1]  :-)

By the way, are you going to update it to include 6.x? There seems to
be many "former" CentOS users and this is one of the things that are
different between the two distros.  In CentOS, 'yum update'
automatically takes the system to the latest point release. So, the
description in the FAQ :

"It is not required that administrators upgrade their release, because
the security errata will be updated for all releases."

is a rather new concept for people who are new to SL.

Akemi

[1] https://www.scientificlinux.org/documentation/howto/upgrade.5x

ATOM RSS1 RSS2