From owner-freebsd-hackers Sat Oct 5 05:28:03 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA13765 for hackers-outgoing; Sat, 5 Oct 1996 05:28:03 -0700 (PDT) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA13727 for ; Sat, 5 Oct 1996 05:27:52 -0700 (PDT) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.7.6/BSD4.4) id WAA17950 Sat, 5 Oct 1996 22:26:01 +1000 (EST) From: michael butler Message-Id: <199610051226.WAA17950@asstdc.scgt.oz.au> Subject: Re: 2.1.5-???? in priduction -- once again In-Reply-To: <199610050809.MAA11352@unicorn.ww.net> from Alexis Yushin at "Oct 5, 96 12:09:46 pm" To: alexis@ww.net Date: Sat, 5 Oct 1996 22:26:00 +1000 (EST) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Alexis Yushin writes: > So back to the issue. One wants to build as-robust-as-possible- > -with-FreeBSD solution. It seems obviously that he takes 2.1.5-RELEASE. > But there is a number of patches which are usefull to be applied .. There doesn't seem to be a separate list (unless you want to wade through the CVS commit logs). My approach has been to install 2.1.5-release, sup 2.1.5-stable from my local archive, 'make world', transport to customer and integrate (simple reconfiguration) into their network. All five of my internal "mission-critical" servers were built this way and several of my customers'. I have very few problems with this strategy since the hardware gets "stress tested" at the time of install rather than when the customer goes to use it. More problems are caused by "pilot error" than anything else :-( michael