From owner-freebsd-stable Mon Mar 20 18:35:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 28EE137B8F2; Mon, 20 Mar 2000 18:35:45 -0800 (PST) (envelope-from jim@nasby.net) Received: from nasby.net (sysnasby@2.nasby.dsl.enteract.com [216.80.51.18]) by mail.enteract.com (8.9.3/8.9.3) with ESMTP id UAA56872; Mon, 20 Mar 2000 20:35:30 -0600 (CST) (envelope-from jim@nasby.net) Message-ID: <38D6DFF3.2142EFAA@nasby.net> Date: Mon, 20 Mar 2000 20:35:31 -0600 From: "Jim C. Nasby" Organization: distributed.net X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en-US,en MIME-Version: 1.0 To: Greg Lehey Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: How to upgrade to 4.0 with vinum [was: Re: 3.4-4.0 and vinum] References: <38D48D3D.1DBA8F5D@nasby.net> <20000320141715.C3675@mojave.worldwide.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yup, absolutely correct Greg. For everyone else, here's the steps that you need to take to upgrade to 4.0 if your /usr is on a vinum volume. (If you're running vinum but /usr is on a 'normal' device then I think you'll be ok). 1) Follow the instructions in /usr/src/UPDATING up to the reboot (don't reboot yet), but make sure that you keep an backup copy of your 3.4 kernel 2) You need to install the new vinum kernel module and userland, but before you do this, I very, very strongly recommend you back up the old files. If something goes wrong and you have to go back, you're in big trouble without them. To back them up: cp /modules/vinum.ko /modules/vinum.3; cp /sbin/vinum /sbin/vinum.3 3) Install the new vinum software. cd /usr/src/sys/modules/vinum && make install && cd /usr/src/sbin/vinum && make install 4) You should now be able to reboot to single-user and continue on. I don't know if this is normal for a non-vinum machine or not, but my machine doesn't do any mounting of devices when booted to single-user. In order to get your filesystems up and running, do this as soon as you have a shell: vinum start fsck -p mount -a You should now be good to go. Greg/anyone else: I did this over 3 days and finished very late last night, so if I screwed anything up here, please correct me. Good luck! :) Greg Lehey wrote: > > On Sunday, 19 March 2000 at 2:18:05 -0600, Jim C. Nasby wrote: > > For those of you who are running vinum, make damn sure you keep an old > > kernel around while upgrading... it seems that you can't load vinum > > after booting with the new kernel... I'm hoping that a make install in > > the vinum directory will remedy this situation... I'll post an update > > once I know what's going on, but in the meantime, this is a heads-up for > > everyone running vinum. > > This appears to be a problem that the upgrade doesn't install the klds > for the new kernel. If you install them, you should be OK. > > Greg > -- > When replying to this message, please copy the original recipients. > For more information, see http://www.lemis.com/questions.html > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers -- Jim C. Nasby (aka Decibel!) /^\ jim@nasby.net /___\ Freelance lighting designer and database developer / | \ Member: Triangle Fraternity, Sports Car Club of America /___|___\ Give your computer some brain candy! www.distributed.net Team #1828 Get paid to surf!! http://www.enteract.com/~nasby/alladvantage.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message