Return to BSD News archive
Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!crcnis1.unl.edu!wupost!darwin.sura.net!europa.eng.gtefsd.com!library.ucla.edu!agate!usenet.ins.cwru.edu!news.csuohio.edu!stever
From: stever@csuohio.edu (Steve Ratliff)
Subject: Re: FreeBSD upgrade...
Message-ID: <1993Oct13.161139.19300@news.csuohio.edu>
Sender: news@news.csuohio.edu (USENET News System)
Organization: Cleveland State University
X-Newsreader: Tin 1.1 PL5
References: <haley.750498537@husc8>
Date: Wed, 13 Oct 1993 16:11:39 GMT
Lines: 40
This is a "me to" post with annotations ;)
Elizabeth Haley (haley@husc8.harvard.edu) wrote:
: O.K. So I attempt the installation via the update script...
:
had this problem
: Problems:
: 1. update is the name of a utility on the PATH.
: solution: run ./update to force the issue... Still, it's
: namespace pollution.
1.a The latest and greatest now official script is still set up for
the GAMMA source packaging and not the new EPSILON source
packaging. Minor hack, but still a pain.
:
Big problem with this as it bombed half way through the install of gcc
overwriting the 1.39 version and leaving me without a working compiler.
: 2. Failure to complete make of gcc1 due to absence of libgnumalloc.
: ??? Was This SUPPOSED to be there??? I was never informed. I was
: previously running 386bsd-0.1 + pk 0.2.4.
:
: solution: find and install same... Mayhap need to make sure
: this is compiled and installed FIRST.
Wasn't lucky enough to have spare gcc.
: 3. O.K. So at this point I have hacked off the front part of the
: update script to prevent it from doing things over again.
: Everything runs vaguely O.K. Though I have to terminate it and "fg" to
: get it to break a lockup at one point. I have no idea of the effects
: of this. It is during the (re) compilation of gcc, but I happen to
: already have gcc compiled in /usr/local, so I forge ahead. Until we
: hit making the kernel.
Also ran with pk 2.4 kernel for same reasoning.:
: I didn't follow the initial advice of running on the FreeBSD kernel,
: because my 386bsd-0.1 + pk0.2.4 kernel was quite stableon it's own,
: having never crashed.
[kernel make problems plus rest deleted] I didn't get that far because
of problem #2.
I am planning on now trying the binary upgrade. Though if that
fails I guess I'll have to do a complete re-install.