[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] [Qube2] Bad package file.
- Subject: RE: [cobalt-users] [Qube2] Bad package file.
- From: Jerry Waugh <jwaugh@xxxxxxxxxxx>
- Date: Mon Apr 17 06:05:44 2000
http://trueblue.cobalt.com/newsletter/mar2000.content.html
2) Cobalt's Update numbering system:
Here's how Cobalt's update numbering system works.
The first number (2) indicates the generation and the second (x) is version.
So, when the version changes within a generation, (2.1 to 2.2 for example),
network administrators must install EACH incremental update. A 2.2 upgrade
may not have, but may need, updated material in 2.1. You can't go from 2.0
to 2.2, without first installing 2.1 or vulnerability corrected by 2.1 may
still exist.
A new generation, on the other hand, --3.0 in this example-includes all of
the previous generation's incremental updates--all the 2.x's--and only the
previous generation's incremental updated--not 1.x's.
On the RaQ 2(English), all of these Updates should be on everyone's system:
RaQ 2-Security-2.94.pkg
RaQ 2-Security-2.93.pkg
RaQ 2-Security-2.92.pkg
All-Kernel_mips-1.0.pkg
RaQ 2-Security-2.7.pkg
RaQ 2-Security-2.3.pkg
RaQ2-Update-MFG-2.1.pkg
RaQ 2-Security-2.2.pkg
RaQ 2-Security-2.1.pkg
RaQ 2-Security-2.0.pkg
RaQ2-Update-OS-2.0.pkg
RaQ2-Update-OS-1.0.pkg
>