Prev: Setting global environment variables
Next: Follow-Up Re: Daisy Chain Problem
From: David Empson on 15 Apr 2010 11:28
Jeffrey Goldberg <nobody(a)goldmark.org> wrote:

> On Wed, 14 Apr 2010, in <1jgzqfb.v2d9oi8q3v5rN%dempson(a)actrix.gen.nz>
> David...:
>
> > Jeffrey Goldberg <nobody(a)goldmark.org> wrote:
> >
> >> Time for a security update (restart will be required). This one fixes
> >> the vulnerability that was successfully used in the Pwn2Own
> >> competition.
> >
> > Rather annoying for Leoaprd users that this security update fixes a
> > single problem but incorporates all the earlier security updates,
> > resulting in another multi-hundred megabyte download just two weeks
> > after the previous one.
>
> Is it "all earlier security updates" or are they the "new" updates that
> come with the massive security fixes from 10.6.2 -> 10.6.3. That OS
> update had what must be a record number of security fixes.

Note that I said "Leopard" (with a typo) in the above paragraph.

The reference point for "all earlier security updates" is the most
recent minor version of the appropriate major version of Mac OS X.

Security Update 2010-003 for Leopard incorporates all earlier security
updates since 10.5.8 was released, i.e. everything in 2009-004 through
2010-002, plus the new single item.

Future security updates for Leopard will continue to get bigger, as they
will include every security fix since 10.5.8, and any new ones.

So far, Snow Leopard has had at most one security update between minor
version updates. Each security update has only needed to include the
batch of fixes described for that update.

If Snow Leopard has two or more security updates between minor versions,
the second and subsequent consecutive update will grow in size as more
fixes are included.

Minor version updates include all security fixes since the previous
minor version. In effect, the size of the separate security updates are
reset each time there is a minor version update.

Once 10.7 is released, Snow Leopard will stop getting minor version
updates, and subsequent security updates for Snow Leopard will keep
growing, like Leopard's ones are now. (Leopard will stop getting
security updates at this point.)

--
David Empson
dempson(a)actrix.gen.nz
From: Steven Fisher on 16 Apr 2010 11:43
In article <g.kreme-8916AE.01352816042010(a)news.iad.newshosting.com>,
Lewis <g.kreme(a)gmail.com.dontemailme> wrote:

> Er.. no, it was like a 2 second download. No way was it even 10MB much
> less 200MB+
>
> It went so far I didn't even register the size.

6.3MB. Pretty light-weight.


Steve
From: Barry Margolin on 16 Apr 2010 22:38
In article <g.kreme-8916AE.01352816042010(a)news.iad.newshosting.com>,
Lewis <g.kreme(a)gmail.com.dontemailme> wrote:

> In article <Qctxn.1817$Z6.1134(a)edtnps82>, me(a)home.spamsucks.ca (Kir�ly)
> wrote:
>
> > Jeffrey Goldberg <nobody(a)goldmark.org> wrote:
> > > Time for a security update (restart will be required). This one fixes
> > > the
> > > vulnerability that was successfully used in the Pwn2Own competition.
> >
> > It's a whopper at 210MB. I don't remember ever seeing such a big size
> > for a one-item security update.
>
> Er.. no, it was like a 2 second download. No way was it even 10MB much
> less 200MB+
>
> It went so far I didn't even register the size.

Read the rest of the thread. It's small on Snow Leopard, huge on
Leopard.

--
Barry Margolin, barmar(a)alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
First  |  Prev  | 
Pages: 1 2 3
Prev: Setting global environment variables
Next: Follow-Up Re: Daisy Chain Problem