*BSD News Article 97642


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!como.dpie.gov.au!news.gan.net.au!act.news.telstra.net!news.telstra.net!psgrain!iafrica.com!uct.uni.net.za!csir.uni.net.za!howland.erols.net!newsfeed.nacamar.de!news1.best.com!nntp2.ba.best.com!not-for-mail
From: "Jordan K. Hubbard" <jkh@FreeBSD.org>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Problem with Sysinstall in 2.2.2
Date: Fri, 13 Jun 1997 01:11:05 -0700
Organization: Walnut Creek CDROM
Lines: 22
Message-ID: <33A10099.15FB7483@FreeBSD.org>
References: <5nqqh4$3ht@news0-alterdial.uu.net>
NNTP-Posting-Host: time.cdrom.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-STABLE i386)
To: Todd Suess <root@cracked.inspace.net>
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:42833

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.