From owner-freebsd-stable Thu Mar 16 11:44:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 562F337C244; Thu, 16 Mar 2000 11:44:32 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id LAA64351; Thu, 16 Mar 2000 11:44:32 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 16 Mar 2000 11:44:32 -0800 (PST) From: Kris Kennaway To: "Jeffrey J. Libman" Cc: Daniel Boyd , stable@FreeBSD.ORG Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Mar 2000, Jeffrey J. Libman wrote: > interesting. i have managed to do my "make installworld" updates on 3.4 > without dropping to single user in the past. i know this is often > ill-advised...but i seem to get away with it. is this not possible in > future releases? or is this only super critical with the 3.4->4.0 upgrade? It's always the recommended practise, but it's only critical when major things change. In particular, you're likely not even to be able to boot into multi-user mode at the point when you've installed a 4.0 kernel but haven't yet done the installworld, if you try and load things like KLD modules (e.g. if you have linux_enable="Yes" the system will probably panic at boot time because of the very stale KLD). Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message