From nobody@FreeBSD.ORG Tue Sep 21 14:32:04 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id D5FE114EF0; Tue, 21 Sep 1999 14:32:04 -0700 (PDT)
Message-Id: <19990921213204.D5FE114EF0@hub.freebsd.org>
Date: Tue, 21 Sep 1999 14:32:04 -0700 (PDT)
From: jim@reptiles.org
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: 3.3-RELEASE /stand/sysinstall wants XF86331, dist has XF86335
X-Send-Pr-Version: www-1.0

>Number:         13886
>Category:       conf
>Synopsis:       3.3-RELEASE /stand/sysinstall wants XF86331, dist has XF86335
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Sep 21 14:40:01 PDT 1999
>Closed-Date:    Sun Oct 10 17:36:12 PDT 1999
>Last-Modified:  Sun Oct 10 17:36:34 PDT 1999
>Originator:     Jim Mercer
>Release:        3.3-RELEASE
>Organization:
Reptilian Research
>Environment:
(sorry, not currently running)
>Description:
when using the install floppies (kern.flp/mfsroot.flp) to install
3.3-RELEASE, the attempt to install Xfree86 fails as it attempts
to install from a directory of XF86331. the distribution has the
directory XF86335.

>How-To-Repeat:
# /stand/sysinstall
-> Configure
  -> Install XFree86

>Fix:
quick, symlink the directory in the distribution
longterm, adjust source for /stand/sysinstall


>Release-Note:
>Audit-Trail:

From: Matt Behrens <mbehrens@globaldsl.com>
To: freebsd-gnats-submit@freebsd.org, jim@reptiles.org
Cc:  
Subject: Re: conf/13886: 3.3-RELEASE /stand/sysinstall wants XF86331, dist has 
 XF86335
Date: Wed, 06 Oct 1999 14:59:04 -0400

 I'm inclined to think that Jim just had a really weird corrupt floppy
 (maybe a corrupt floppy image?) where the 3rd LSB bit on one of the
 bytes was displaced. :-)  Actually, it's not really that weird, and
 might be indicative of bad memory -- when I was compiling once on a
 machine with bad cache RAM, the program refused to link because a symbol
 name was corrupted on just one of the bits.  I would think the same
 could happen between network and local disk, or perhaps disk image and
 floppy.
 
 In any event, the following diff illustrates that dist.c was, in fact,
 changed correctly for 3.3-RELEASE:
 
 http://www.freebsd.org/cgi/cvsweb.cgi/src/release/sysinstall/dist.c.diff?r1=1.132.2.11&r2=1.132.2.12
 
 I recommend that Jim try a new set of floppies and this PR be closed.
 
State-Changed-From-To: open->closed 
State-Changed-By: steve 
State-Changed-When: Sun Oct 10 17:36:12 PDT 1999 
State-Changed-Why:  
I have to agree with Matt on this one. :) 
>Unformatted:
