Date: Sun, 17 Dec 2006 14:22:23 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Astrodog <astrodog@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Am I an Idiot? Message-ID: <4585C31F.5040804@FreeBSD.org> In-Reply-To: <2fd864e0612171355u1183779ds2eb2086442e13da6@mail.gmail.com> References: <4579EB08.8080704@intersonic.se> <20061210.230622.-1844001233.imp@bsdimp.com> <45845F8B.3060304@intersonic.se> <45851DBC.9010604@FreeBSD.org> <2fd864e0612170807x20ff699x42538cfa497c1398@mail.gmail.com> <4585B4EC.1070906@FreeBSD.org> <2fd864e0612171355u1183779ds2eb2086442e13da6@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Astrodog wrote:
> The kind of testing needed in -CURRENT is controlled, in my opinion.
You are, of course, welcome to your opinions. You will, of course,
please make allowances for the facts that,
A) You might be wrong, and
B) Even if you are right within some limited sphere, your knowledge
and experience only extend so far, and others who have different
knowledge and/or experience may not find them useful.
For example, as a FreeBSD developer I am always quite gratified when
people run my -current code in a real world environment, since I find
anecdotes useful. Of course I'd always rather hear, "It works!" but
even if the answer is that it doesn't work, it gives me a direction to
look in that I didn't have before.
So let me summarize. Yes, there are potential problems with running
-current in production. As I said very early in this thread, the
safest way of doing so is to run -current on a limited number of
systems, and have -stable hardware ready to swap in if needed. The OP
says he understands the issues at hand, and is willing to jump into
the deep end of the pool. He seems like a grown-up to me, let's leave
him alone and move on to other things, shall we?
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4585C31F.5040804>