*BSD News Article 97789


Return to BSD News archive

From: Todd Suess <root@cracked.inspace.net>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Problem with Sysinstall in 2.2.2
Date: 13 Jun 1997 16:07:39 GMT
Lines: 33
Message-ID: <5nrr8b$ief@news0-alterdial.uu.net>
References: <5nqqh4$3ht@news0-alterdial.uu.net> <33A10099.15FB7483@FreeBSD.org>
NNTP-Posting-Host: cracked.inspace.net
X-Newsreader: TIN [UNIX 1.3 unoff BETA 970527; i386 FreeBSD 2.2.2-RELEASE]
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.edu.au!cs.mu.OZ.AU!munnari.OZ.AU!news.Hawaii.Edu!news.lava.net!news.flex.com!www.nntp.primenet.com!nntp.primenet.com!feed1.news.erols.com!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!uunet!cracked.inspace.net!root
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:42996

Jordan K. Hubbard <jkh@FreeBSD.org> wrote:
> Todd Suess wrote:
> > 2.2.2 I have a small problem.  The first time sysinstall runs, it works
> > super, allowing me to install several programs from the ports
> > collection, etc..  However, on subsequent trys running /stand/sysinstall
> > the program will fail with a segmentation fault and dump the core (signal

> You're not alone - others have reported this problem and it's Damned
> Peculiar.  It's almost as if the binary is corrupting itself somehow. 
> This is going to prove interesting to track down, no doubt, and I've no
> guarantees as to how long that will take but I just thought I'd let you
> know that the problem is known and is being investigated.

> Thanks.

> P.S. If you have /usr/src/release on your system, one work-around is to
> go to /usr/src/release/sysinstall, do a make and then copy the resulting
> binary to /stand.  You'll toast all the utilities which are linked to it
> there, but at least sysinstall will work again. :)

> -- 
> - Jordan Hubbard
>   FreeBSD core team / Walnut Creek CDROM.

Thanks for the Tip, Jordan, however, I followed your suggestion, and even with a new
binary of sysinstall (which is, BTW much smaller than the original sysinstall (~360k>
vs. (~1.6M>, and it still gets the same segmentation fault..   :(  Only thing I can think
of is to reinstall and before running sysinstall make a backup of the binary and then 
trying to recopy it back into /stand once it fails, but I really don't want to reinstall
the whole system again....

Todd