From owner-freebsd-questions Thu Feb 27 13:17:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA19034 for questions-outgoing; Thu, 27 Feb 1997 13:17:27 -0800 (PST) Received: from galanga.ip.org (galanga.ip.org [206.30.205.26]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA19028 for ; Thu, 27 Feb 1997 13:17:20 -0800 (PST) Received: (from erich@localhost) by galanga.ip.org (8.8.4/8.8.4) id QAA02164 for freebsd-questions@freebsd.org; Thu, 27 Feb 1997 16:17:04 -0500 (EST) From: "Eric L. Hinson" Message-Id: <199702272117.QAA02164@galanga.ip.org> Subject: upgrading 2.1.6 to 2.1.7 w/o interuption of service? To: freebsd-questions@freebsd.org Date: Thu, 27 Feb 1997 16:17:03 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi there, I have several systems that I maintain for an ISP that I would like to upgrade to 2.1.7. (one is a 2.1.6.1 machine, and the other is an older 2.1-STABLE (shortly after after 2.1.0-RELEASE came out). However, I'm unclear as to which method I should use to facilitate this switch with as little disruption to users as possible. Any insight would be most appreciated. Thanks for your time and help with this matter. Eric -- Eric L. Hinson Unix Systems Administrator Personal E-Mail: erich@ip.org AugLink E-Mail: erich@aug.com "Always keep the enemy on the defensive, and in a state of uncertainty as to where the next blow may fall." -- Louis L'Amour's "The Walking Drum"