From owner-freebsd-current Mon Feb 16 00:37:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01232 for freebsd-current-outgoing; Mon, 16 Feb 1998 00:37:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from silvia.HIP.Berkeley.EDU (ala-ca37-18.ix.netcom.com [207.93.141.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01224 for ; Mon, 16 Feb 1998 00:37:20 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id AAA10551; Mon, 16 Feb 1998 00:36:57 -0800 (PST) Date: Mon, 16 Feb 1998 00:36:57 -0800 (PST) Message-Id: <199802160836.AAA10551@silvia.HIP.Berkeley.EDU> To: root@krabi.mbp.ee CC: current@FreeBSD.ORG In-reply-to: (message from Superuser on Sun, 15 Feb 1998 22:50:53 +0200 (EET)) Subject: Re: Preferred way (or FAQ) for upgrading 2.2 to 3.0-CURRENT From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * I have 2*200PPro system running 2.2-STABLE and would like to use second * CPU as well... have successfully tested 3.0-CURRENT on monoprocessor 486 * system. I have upgraded about 20 systems a couple of months ago. It was pretty much just make world, make kernel, and reboot. They are now running a "97.12.26.08.00.00" system and have been pretty stable. One hitch was that the new "reboot" won't work with the old kernel (it will dump core and hang the system cold), so I had to make a backup of /sbin/reboot and use it to restart the system. Also, you will need to recompile a lot of ports due to changed utmp sizes, but I already had our 2.2-stable systems running with 16-byte usernames so this wasn't a problem for us. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message