From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 18 02:49:08 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFD1737B401 for ; Fri, 18 Jul 2003 02:49:08 -0700 (PDT) Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.86.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 098DA43FA3 for ; Fri, 18 Jul 2003 02:49:08 -0700 (PDT) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (port757.uc1-esp.isdn-lan.cybercity.dk [212.242.98.245]) by phk.freebsd.dk (8.12.8/8.12.8) with ESMTP id h6I9n5V3022908; Fri, 18 Jul 2003 09:49:05 GMT (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h6I9n1Mu000848; Fri, 18 Jul 2003 11:49:02 +0200 (CEST) (envelope-from phk@phk.freebsd.dk) To: netch@lucky.net From: "Poul-Henning Kamp" In-Reply-To: Your message of "Fri, 18 Jul 2003 12:12:48 +0300." <20030718091248.GO76126@lucky.net> Date: Fri, 18 Jul 2003 11:49:01 +0200 Message-ID: <847.1058521741@critter.freebsd.dk> cc: hackers@freebsd.org Subject: Re: complicated downgrade X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 09:49:09 -0000 In message <20030718091248.GO76126@lucky.net>, Valentin Nechayev writes: >(Cc'ed to phk@ as to main GEOM and DEVFS developer; see corresponding >questions below.) I'm on vacation right now, and sort of semi offline (you know, the undocumented ACPI S-1 "wife mandated offline state" :-) In addition to what you already have discovered, you _may_ have an issue with your bsd disklabels (too). I would probably do it like this (assuming you have remote console): Put 4.8 kernel and a 4.8 mfsroot image (with plenty of fixit like stuff, size is not a big issue if you boot this from disk) on the 5.x system, boot that kernel using the mfsroot as root filesystem and try to do the surgery from there. The advantage to this approach is that you can explore the issues returning to your 5.x installation and adjust your approach. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.