Quoting Niall Walsh (linux at esatclear.ie):
> There are security updates on sarge, but the security updates on testing
> will stop once it becomes etch instead of sarge.
_Automated_ ones will. So, you include "unstable" source lines in
/etc/apt/sources.list, include these lines in /etc/apt/preferences :
Package: *
Pin: release a=unstable
Pin-Priority: 50
...subscribe to the Debian Security Advisories (DSAs) mailing list, and
apt-get fetch as required whichever branch's packages fixes
vulnerabilities as you determine that they affect your system.
See also:
"Testing Security" on http://linuxmafia.com/kb/Debian/
[When the "testing" symlink gets switched from sarge to etch:]
> And you could get yourself in a mess (though you probably shouldn't
> but you could end up running without security patches) if you go
> updating to testing without realising it has become etch since you
> installed.
Rule of thumb: Don't _ever_ merely rely on the Debian Security Team's
updates auto-flowing out to your system on anything other than a pure
Debian-stable system. On anything else, you can't just switch off your
brain and mindlessly type "apt-get update && apt-get dist-upgrade" with
complete, unthinking confidence, as you typically can on Debian-stable.
> Using stable is always best....
Feh.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
