From owner-freebsd-bugs Thu Jul 1 1:10: 3 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id B436914CB4 for ; Thu, 1 Jul 1999 01:10:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id BAA38327; Thu, 1 Jul 1999 01:10:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 1 Jul 1999 01:10:02 -0700 (PDT) Message-Id: <199907010810.BAA38327@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Josef Karthauser Subject: Re: misc/12468: reboot causes dumps core after a 2.2.X to 3.2 upgrade Reply-To: Josef Karthauser Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/12468; it has been noted by GNATS. From: Josef Karthauser To: Ruslan Ermilov Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: misc/12468: reboot causes dumps core after a 2.2.X to 3.2 upgrade Date: Thu, 1 Jul 1999 09:01:48 +0100 Excellent... I'm glad that that's be sorted. Trust me not to notice the obvious. I've been doing the aout-to-elf-install method by hand since since last Oct; it's a case of functional fixedness on my part - sorry. Thanks Ruslan, Joe On Thu, Jul 01, 1999 at 10:27:25AM +0300, Ruslan Ermilov wrote: > On Wed, Jun 30, 1999 at 09:46:26PM +0000, joe@tao.org.uk wrote: > > > > >Description: > > > > During the transition from a 2.2.X running operating > > system to 3.2 using 'cvsup' and 'make world', eventually > > one has to reboot the box onto the new kernel. The > > traditional way of doing this is to use a 'reboot' command. > > Unfortunately it seems that the reboot functionality doesn't > > survive during a upgrade and instead the operator is rewarded > > with a 'dumped core' instead. This isn't usually a problem > > if the server is in the physical locality of the operator, but > > is a 'right royal pain in the arse' if the server is located > > on a remote desert island ;) > > > > >How-To-Repeat: > > > > Start with a 2.2.X machine. > > Cvsup the source tree to 3.2-RELEASE, or 3.2-STABLE. > > Make upgrade (or aout-to-elf-build, install, move, etc) > > Use mergemaster to rebuild the /etc/ config, etc. > > Rebuild the kernel and install. > > Disklabel -B primarydrive - to install new boot blocks for elf kernel. > > Reboot --- bus error! Network is down. Machine sits happily > > in single user mode. > > As the first step of the install phase, ``upgrade'' saves the copies > of /bin/sh and /sbin/reboot into /usr/obj, and displays the following > message: > +-------------------------------------------------------------+ > | Saving a copy of programs required to shut the system down. | > +-------------------------------------------------------------+ > > After it has finished populating your system with the new ELF stuff, > ``upgrade'' will automatically install new boot blocks onto your root > hard drive (you were asked for), build and install new ELF kernel, > set the default obj format to ``ELF'' and ask you to reboot the system: > > +-------------------------------------------------------+ > | Your system has now been fully updated to elf! | > | | > | It's now time to reboot from your new ELF kernel. | > | You can type Ctrl-C to abort this (at your own risk) | > ^^^^^^^^^^^^^^^^ > | or press return to reboot the system. | > +-------------------------------------------------------+ > > I assume that you pressed Ctrl-C at this point, so this is what > "your own risk" mean -- you didn't knew how to reboot your system > correctly. The correct way is to execute /usr/obj/reboot. -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message