Date: Sat, 9 Dec 2006 15:38:03 -0500 From: "David Stanford" <dthomas53@gmail.com> To: davidn@datalinktech.com.au Cc: freebsd-current@freebsd.org Subject: Re: Am I an Idiot? Message-ID: <f2c91f770612091238v747a82fdy2908da9276c20801@mail.gmail.com> In-Reply-To: <457A3B9B.5000304@datalinktech.com.au> References: <4579EB08.8080704@intersonic.se> <457A3B9B.5000304@datalinktech.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
It has been some years since running -current on any critical production > server, but I have never had any qualms about doing so on a system I use > constantly. In some cases that includes what are essentially > "production" systems in that they support use for development and > pre-deployment internal to an organisation or project and while not > serving a critical role they are still heavily relied upon (and some of > those systems also run applications built from HEAD branch of their > respective repositories). > > However there is always sufficient expertise around to handle the bumps > and inconveniences associated with -current including working around > long-standing problems on -current that occasionally do occur (inability > to run threaded apps compiled in 6.x, for example, where upgrade via > rebuild is not an option - a problem which I've never personally had to > address since 100% of what I run on a BSD box is open source). > > Scanning this list regularly is almost a requirement when running > -current, although src/UPDATING will get you ~50% of what you need to > know. > > This is a somewhat OT question, but what needs to be done to turn off the on-by-default debugging features when running -CURRENT? Just curious... -David -- [root@fbsd ~]# fortune Happiness is just an illusion, filled with sadness and confusion.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f2c91f770612091238v747a82fdy2908da9276c20801>