From owner-freebsd-stable Mon Sep 6 10:50:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dt011n65.san.rr.com (dt010nb9.san.rr.com [204.210.12.185]) by hub.freebsd.org (Postfix) with ESMTP id 7A2861596F for ; Mon, 6 Sep 1999 10:50:30 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.9.3/8.8.8) with ESMTP id KAA95320; Mon, 6 Sep 1999 10:49:51 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37D3FEBF.6CA1CB00@gorean.org> Date: Mon, 06 Sep 1999 10:49:51 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0904 i386) X-Accept-Language: en MIME-Version: 1.0 To: Kiril Mitev Cc: freebsd-stable@freebsd.org Subject: Re: recent kernel build failures - question References: <199909061519.PAA08041@loki.ideaglobal.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This might sound like criticism, but I'm just grumpy this morning. Kiril Mitev wrote: > > Hi All > > Have all the problems wrt cvsupp-ed kernel builds been sorted out then ? > Or should 'to be upgraded' boxes hold back for a couple more days ? You should never cvsup new sources then just build a kernel. Changes between kernel interfaces and userland code can render your system unusable. Also, if your freebsd machines are mission critical you should have at least one spare machine with as close to an identical configuration as possible and use it for a test build before going ahead with the upgrades (or better yet, build once, install many times via NFS). That way you can be sure that the most recent sources will work for _you_, which is always your best bet anyway. Good luck, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message