From owner-freebsd-current Thu Jan 17 1:59:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 95DBD37B402 for ; Thu, 17 Jan 2002 01:59:20 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g0H9wjm47072; Thu, 17 Jan 2002 11:58:45 +0200 (EET) (envelope-from ru) Date: Thu, 17 Jan 2002 11:58:45 +0200 From: Ruslan Ermilov To: Terry Lambert Cc: Timothy Aslat , freebsd-current@FreeBSD.ORG Subject: Re: Downgrading Message-ID: <20020117115845.K27310@sunbay.com> References: <20020117104901.24d09d36.tim@spyderweb.com.au> <3C462FFF.22701A04@mindspring.com> <20020117111734.H27310@sunbay.com> <3C4698EC.8FF8BB7D@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C4698EC.8FF8BB7D@mindspring.com> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jan 17, 2002 at 01:27:08AM -0800, Terry Lambert wrote: > Ruslan Ermilov wrote: > > FWIW, modern -CURRENT's should be able to downgrade to -STABLE > > without problems. If it's broken, please let me know, and I'll > > fix it. I mean "if it WILL be broken", as tonight's -CURRENT > > has successfully built -STABLE. Didn't test the `installworld' > > part, but I don't believe there are any problems with it. > > Config file changes are still a problem: they won't be > reflected back, due to version changes (if any). There > were a number of problems with /etc/pam.conf compatability > and OpenSSH v1 vs. v2 and already generated certs needing > to be regenerated as a result, last time I went back to 4.x > from a 5.x. > Um, what do you mean by "config file changes"? Of course you can't use stock 5.0-CURRENT config files, it's clear. As for config(8), it's in bootstrap-tools, and shouldn't be a problem. Buildkernel works fine here. > The MAKEDEV problem is more pronounced moving from -current, > since -current has devfs. > > My recommendation would be *against* using "makeinstallworld", > since with a CDROM approach, the devfs isn't mounted on /dev, > so the devices get made correctly (devfs would also throw a > wrench into the NFS mounted CDROM approach I talked about > before; sorry). > I avoid these problems by installing with DESTDIR=/STABLE. :-) > As I said before about boot blocks: all bets are off: I have > no idea whether or not they are capable of booting older > versions of the code correctly any more; there have been > some recent problems because of some changes, and because of > a bzero that Alfred was rumored to have lost from Jon Mini > and James Harris' contributions toward an updated FORTH-based > "nextboot"... ;^). > Not sure about this one. Perhaps the following would be safe: 1) You copy your /, /var, and /usr holding disks. 2) You mount copies to /mnt. 3) You ``installworld'' and ``installkernel'' with DESTDIR=/mnt 4) You install 4.x bootblocks (from /mnt/boot) to /mnt Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message