Date: Mon, 12 Jun 2000 06:40:37 -0700 From: Emmanuel Gravel <egravel@earthlink.net> To: freebsd-questions@FreeBSD.ORG Subject: Re: Upgrade woes Message-ID: <3944E855.5D01F089@earthlink.net> References: <39447959.D9C9E185@earthlink.net> <20000611232527.D16019@dialin-client.earthlink.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I had followed /usr/src/UPDATING on the last try with buildworld. That's how I commented out openssh from make.conf, among other things (that helped quite a bit, it too was causing compiler crashes). The last time it had crashed was with signal 4 somewhere in compiling rogue. The time before that was signal 10 compiling yp_xrd.c (no warnings or errors). That's what was strange about it. It crashed with no warnings. That's what I meant about mid-way, at least for the compilation process. As for the installation process, both times I had other things to do so I let it run unattended, and when I got back to it all I saw was a slew of error messages about getty and/or sh crashing/coredumping, so I don't know where in the process that things went haywire, or why. Here what I mean by both times, is installworld for the first time and /stand/sysinstall for the second. So what I'll do now is just burn myself a CD with 4.0 and boot from it to upgrade. That seems to be, at least for now and for me, the most trouble free method. Thanks, Emmanuel Gravel "Crist J. Clark" wrote: > > On Sun, Jun 11, 2000 at 10:47:05PM -0700, Emmanuel Gravel wrote: > > I have 3.3 release installed on a P90 with 32 MB of RAM. > > Fairly basic install. Tried upgrading to 4.0 in these > > ways: > > > > 1- cvsup the source and make buildworld > > 2- /stand/sysinstall with FTP set to ftp.freebsd.org and > > release set to /.0/FreeBSD/release/i386/4.0-RELEASE > > > > Problems in the first case: often had compiler crashes > > (signal 11, signal 10 and signal 4). Got it finally working > > after running with -DNOCLEAN -DNOGAMES. Then tried installworld > > and it crashed midway, unrecoverable (finally froze). Had > > to reinstall 3.3 from CD's (minimal, saved most of my config). > > Did you follow the instructions in /usr/src/UPDATING? > > > Problems in the second case: also ended up crashing mid-way > > leaving me with a completely unstable system. As when after > > the installworld, even the shell core dumped (so did df, du, > > bash, getty, most everything crashed). Had to wipe the system > > (two HD's, so I had partial backup) but it was still a pain. > > Mixing the 3.x /stand/sysinstall with a FTP install is not a good > idea. Get the install floppies and use the 4.0 sysinstall. > > > Now resorting to downloading the 4.0 release ISO to burn a > > copy. However it still doesn't explain why I'm getting so > > much trouble upgrading the system. > > If you did not follow /usr/src/UPDATING it does. > > > I was able (on different > > systems, however) to do the troublesome upgrade from 2.2.7 to > > 3.0 last year, and that seemed to go without too much trouble > > compared to this. Would anyone have any idea whatsoever why > > buildworld kept crashing, > > A buildworld should actually go. > > > installworld failed miserably and > > left me with an unstable system, > > The installworld is the usual catch in the process. The new binaries > will not run properly. You need to boot a 4.0 kernel... But you do > need to install certain binaries before the reboot. > > > and downloading the binary > > install with FTP from the main site left my system in even > > worse state? > > Could be the old sysinstall with the new version or the previous > damage to the system. > > > All I want to do is understand what's happening > > so I don't repeat the same mistakes over and over mindlessly. > > I mean, how hard can it be to upgrade FreeBSD from 3.x to 4.x? > > What am I missing? Or is it just something that can't be helped > > with my system? > > /usr/src/UPDATING > > -- > Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3944E855.5D01F089>