From owner-freebsd-doc Mon Dec 7 02:57:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14496 for freebsd-doc-outgoing; Mon, 7 Dec 1998 02:57:19 -0800 (PST) (envelope-from owner-freebsd-doc@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14491; Mon, 7 Dec 1998 02:57:17 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id CAA81613; Mon, 7 Dec 1998 02:56:08 -0800 (PST) To: Pavel Stepchenko cc: freebsd-doc@FreeBSD.ORG, freebsd-bug@FreeBSD.ORG Subject: Re: Some bugs after upgrade 2.2.7-RELEASE to 2.2.8-RELEASE In-reply-to: Your message of "Mon, 07 Dec 1998 14:48:44 +0500." Date: Mon, 07 Dec 1998 02:56:08 -0800 Message-ID: <81609.913028168@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Yesterday i'm upgrading 2.2.7-RELEASE to 2.2.8-RELEASE via > /stand/sysinstall, (FreeBSD 2.2.8-RELEASE i get from ftp.freebsd.org at Hmmmm. /stand/sysinstall would be the old 2.2.7 version you're talking about? It's generally better to do your upgrades from the installation floppy of the version you're trying to upgrade to since otherwise you're using the older upgrade tool bits to upgrade with and won't get the benefit of any fixes we've made to the upgrade process. For a system properly upgraded from the boot floppy, I can't see how the bug you list with sysctl can happen. > 2.Language of FAQ. Unfortunately, that's a known bug. Not much I can do about it now though. :( - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message