CentOS - Apr 2015 - [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

Le 02/04/2015 18:22, Les Mikesell a ?crit :
>> Note that any CentOS machine, updated to the same point in time,
>> >regardless of where and how it was privisioned should give you the
same
>> >functional package set. This is an important thing.
> Yes, but how do you explain that relationship to someone who only has
> a summary of the RH releases or where the Centos release stands
> compared to it.  For example, what would you have said a few days ago?
Notice that a new minor release includes new drivers for new servers, so 
it is important to know if you can install at all the system on your 
server, before any updates !

Alain

-- 
Administrateur Syst?me/R?seau
Laboratoire de Photonique et Nanostructures (LPN/CNRS - UPR20)
Centre de Recherche Alcatel Data IV - Marcoussis
route de Nozay - 91460 Marcoussis
Tel : 01-69-63-61-34

On 04/02/2015 11:30 AM, Alain P?an wrote:
> Le 02/04/2015 18:22, Les Mikesell a ?crit :
>>> Note that any CentOS machine, updated to the same point in time,
>>> >regardless of where and how it was privisioned should give you
the same
>>> >functional package set. This is an important thing.
>> Yes, but how do you explain that relationship to someone who only has
>> a summary of the RH releases or where the Centos release stands
>> compared to it.  For example, what would you have said a few days ago?
> 
> Notice that a new minor release includes new drivers for new servers, so
> it is important to know if you can install at all the system on your
> server, before any updates !
what does that have to do with an ISO name?  Updates are not done via
ISO except for some very small number of off line servers.  Updates
usually happen from the tree.  And the default setup point to /7/ for
updates.  We have been going that for 10 years (pointing updates to /4/,
/5/, /6/, /7/, and not 6.1 or 6.2 or 6.3, etc.

Here is the default mirrorlist and baseurl info from CentOS-5:

==========================================mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os

#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
==========================================
It is the same for CentOS-5, CentOS-6, and CentOS-7 ... if someone has
something different, then they are making changes that they want to
make.  The name on the ISO has no impact on updates.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.centos.org/pipermail/centos/attachments/20150402/4aaaa308/attachment-0001.sig>

Le 02/04/2015 18:41, Johnny Hughes a ?crit :
>> Notice that a new minor release includes new drivers for new servers,
so
>> >it is important to know if you can install at all the system on
your
>> >server, before any updates !
> what does that have to do with an ISO name?
If you use the iso that does not include the correct drivers for your 
new server, it could be impossible to install the server. And with the 
confusing naming, it could be difficult to know if the iso you have at 
hand has indeed have the drivers you need...

Alain

-- 
Administrateur Syst?me/R?seau
Laboratoire de Photonique et Nanostructures (LPN/CNRS - UPR20)
Centre de Recherche Alcatel Data IV - Marcoussis
route de Nozay - 91460 Marcoussis
Tel : 01-69-63-61-34

On Thu, Apr 2, 2015 at 11:41 AM, Johnny Hughes <johnny at centos.org>
wrote:
> On 04/02/2015 11:30 AM, Alain P?an wrote:
>>
>> Notice that a new minor release includes new drivers for new servers,
so
>> it is important to know if you can install at all the system on your
>> server, before any updates !
>
> what does that have to do with an ISO name?
How, without a cross reference of some sort, do you know if a given
CentOS iso will install on hardware where you know that the needed
driver was added in an RH minor rev?

-- 
   Les Mikesell
     lesmikesell at gmail.com