From owner-freebsd-hackers Thu Sep 9 22: 0: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [205.159.88.46]) by hub.freebsd.org (Postfix) with ESMTP id 5105C1524B for ; Thu, 9 Sep 1999 21:59:58 -0700 (PDT) (envelope-from ben@ben.com) Received: from pulsar.ben.com (max4-198-201.cust.aracnet.com [216.99.198.201]) by mail4.aracnet.com (8.9.3/8.9.3) with ESMTP id VAA24027 for ; Thu, 9 Sep 1999 21:59:13 -0700 Received: (from bjj@localhost) by pulsar.ben.com (8.9.3/8.6.12) id WAA00530 for freebsd-hackers@freebsd.org; Thu, 9 Sep 1999 22:00:46 -0700 (PDT) Date: Thu, 9 Sep 1999 22:00:46 -0700 (PDT) From: Ben Jackson Message-Id: <199909100500.WAA00530@pulsar.ben.com> To: freebsd-hackers@freebsd.org Subject: upgrade issue from 2.2.x -> 3.2 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just did that upgrade (been with freebsd since 1.1!) and everything seems pretty smooth. I did a 2.2->3.1 upgrade on another machine so I'm probably glossing over some aout issues (mainly that you have to find them and move them into a separate directory). One thing that confused me for several days and I just figured out: sysctl moved from /usr/sbin to /sbin. I have /usr/sbin in my path first, so I was getting to old one. It almost works, but not quite. It only displays about 15 `kern.' variables and then quits. Perhaps the upgrade option should at least warn of that possibility (maybe obvious, but somewhat unexpected) or even include a list of files that once existed in FreeBSD but no longer do (to facilitate removing them). I'm thinking about digging out a 2.2.x install cd to build that list for myself. --Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message