From owner-freebsd-current Wed Jul 29 09:14:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23856 for freebsd-current-outgoing; Wed, 29 Jul 1998 09:14:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23787 for ; Wed, 29 Jul 1998 09:14:41 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.HIP.Berkeley.EDU (sji-ca7-55.ix.netcom.com [209.109.235.55]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id JAA22744; Wed, 29 Jul 1998 09:13:44 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id JAA02200; Wed, 29 Jul 1998 09:13:39 -0700 (PDT) Date: Wed, 29 Jul 1998 09:13:39 -0700 (PDT) Message-Id: <199807291613.JAA02200@silvia.HIP.Berkeley.EDU> To: smoergrd@oslo.geco-prakla.slb.com CC: muck@ida.net, nik@iii.co.uk, wwoods@cybcon.com, current@FreeBSD.ORG In-reply-to: (smoergrd@oslo.geco-prakla.slb.com) Subject: Re: Upgrading from 2.2.7 to Current From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Indeedeedoo. BTW, I can confirm that this works perfectly in the other * direction, too; I've upgraded my scratch box from 3.0-SNAP-980222 to * 3.0-CURRENT and "downgraded" it back to 2.2.7-STABLE with absolutely * no sign of trouble. Be careful though. I don't remember if there are currently any shared library version differences between 2.2.7 and 3.0 (which of course will cause your newly build 2.2.7 libraries to be very effectively ignored), but some things in /usr/include that only exist in 3.0 will cause some ports to mistake your OS version and blow up. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message