From owner-freebsd-current Thu Oct 8 07:01:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01164 for freebsd-current-outgoing; Thu, 8 Oct 1998 07:01:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.kersur.net (mail.kersur.net [199.79.199.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01159 for ; Thu, 8 Oct 1998 07:01:51 -0700 (PDT) (envelope-from druber@mail.kersur.net) Received: from localhost (druber@localhost) by mail.kersur.net (8.8.8/8.8.8) with SMTP id KAA01517 for ; Thu, 8 Oct 1998 10:01:45 -0400 (EDT) Date: Thu, 8 Oct 1998 10:01:45 -0400 (EDT) From: Dan Swartzendruber To: freebsd-current@FreeBSD.ORG Subject: migration from 2.2.7-STABLE to 3.0? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've re-cvsupped everything and I think I know how to upgrade the system the sources live on. I just want to make sure there's no gotchas with upgrading a remote client vis-a-vis the aout->elf stuff. e.g. what I have been doing in the past is cvsupping to pick up new changes, doing make buildworld on the source server and make installworld on a (less critical) client to make sure everything works okay. Then, I upgrade everything else. Will this work with the stable -> current? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message