nixlists wrote:
On Thu, Mar 4, 2010 at 10:44 AM, Chris Bennett
<ch...@bennettconstruction.biz> wrote:
-current is typically safer by default since all those errata in release
versions are already fixed in -current snapshots. No patches, no builds.
just update to latest snapshots, other than time to update packages, maybe
10-15 minutes or less
But where are the latest security issues and stability issues likely
to be found? In either release or current or just current, since
current is being developed?
You are talking about two separate issues.
Stability is not related to security directly.
The two are intricately combined but not the same.
That is why there are two common errata for release:
Reliability
Security
If you don't want to run -current, then don't.
But if you use a package where a security or reliability issue comes up,
and it is fixed in -current, you will need to backport it yourself.
Hopefully you will send your work to -stable
--
A human being should be able to change a diaper, plan an invasion,
butcher a hog, conn a ship, design a building, write a sonnet, balance
accounts, build a wall, set a bone, comfort the dying, take orders,
give orders, cooperate, act alone, solve equations, analyze a new
problem, pitch manure, program a computer, cook a tasty meal, fight
efficiently, die gallantly. Specialization is for insects.
-- Robert Heinlein
