Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 17 submissions in the queue.

Debian 6 Debuts Its Long Term Support Period

posted by LaminatorX on Wednesday June 18 2014, @11:40AM   Printer-friendly
from the If-ya-know-what-I-mean dept.

Blackmoore writes:

Debian 6 debuts its long term support period

June 16th, 2014

The Debian project is pleased to announce that the "Long Term Support (LTS)" infrastructure to provide security updates for Debian GNU/Linux 6.0 (code name "squeeze") until February 2016 is now in place. Users of this version should follow the instructions from the LTS wiki page to ensure that they get the LTS security updates.

 
This discussion has been archived. No new comments can be posted.
Debian 6 Debuts Its Long Term Support Period | Log In/Create an Account | Top | 9 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 0) by Anonymous Coward on Wednesday June 18 2014, @10:10PM

    by Anonymous Coward on Wednesday June 18 2014, @10:10PM (#57160)

    I'm confused as to why you need to add new repositories to apt-sources in order to get the updates. Why not put the updates in the regular squeeze repositories?

  • (Score: 3, Informative) by Marand on Thursday June 19 2014, @04:33AM

    by Marand (1081) on Thursday June 19 2014, @04:33AM (#57264) Journal

    I'm confused as to why you need to add new repositories to apt-sources in order to get the updates. Why not put the updates in the regular squeeze repositories?

    Most likely to avoid hitting the user with unexpected behaviour. If you want the LTS squeeze, you opt in by adding the repo. Otherwise, you either stick with what you've got or move to the next stable. Everything they do with regard to distribution upgrades tends to be cautious like that.

    Consider how they handle dist upgrades, for example:
    In addition to having their code names (wheezy, squeeze, jessie, sid, etc.) they maintain aliases that don't change: oldstable, stable, testing, unstable. You can get automatic updates from one stable release to another by setting your repo to "stable" instead of "squeeze", and some will want that, but they don't default to that, because it can introduce larger changes to the system than you'd expect.

    Within a release they're separated, too: distname, distname-updates, distname-backports. You choose if you want updates or not, and what sort (just security fixes, or new versions of software).

    It's all about control, rather than forcing updates on you.