"Ken D'Ambrosio" <k...@jots.org> writes:
>
> On Thu, 05 Apr 2012 12:40:35 -0400 Joshua Judson Rosen <roz...@geekspace.com>
> wrote
> 
> > Have you considered upgrading to Debian 6.0/Squeeze? It really sounds
> > more like what you want...:
> > 
> >     http://www.debian.org/News/2011/20110205a
> > 
> > I use the same Compiz/GNOME setup as you're describing. I don't use btrfs,
> > but it looks like it went into this release.
> 
> Huh.  I actually *did* consider Debian, but when I checked the site,
> it seemed it was incredibly old kernels with Gnome 2.x, or newer
> kernels with Gnome 3.x.  If there's a btrfs/Gnome 2.x intersection
> in Squeeze, I just might be willing to give it a try.

If it turns out that you do for-some-reason need a newer line of kernels
than the one that shipped as part of the Squeeze release, there's also
the `backports' section--which Debian uses to make newer versions
of packages available for stable releases while still allowing the
releases to remain as `stable = unchanging' to whatever extent
people need that; e.g.:

        http://packages.debian.org/squeeze-backports/linux-image-amd64

... as opposed to:

        http://packages.debian.org/squeeze/linux-image-amd64

> How long is it due to be supported?

Security updates are provided until 1 year after the *next* release:

    http://www.debian.org/security/faq#lifespan

Going by the patterns in Debian's release-history, and what they said
they were going to aim for after Squeeze was release, you've probably got
2 years from ~now (until early 2014) before Squeeze's security udpates
stop.

    https://en.wikipedia.org/wiki/Debian#Release_history

    http://www.debian.org/News/2009/20090729


Of course I have to point out: if you join in and help prepare for
Wheezy's release, you could make Squeeze's EOL come sooner ;)

-- 
"Don't be afraid to ask (λf.((λx.xx) (λr.f(rr))))."

_______________________________________________
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

Reply via email to