From owner-freebsd-questions  Sun Mar 30 13:31:27 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA14103
          for questions-outgoing; Sun, 30 Mar 1997 13:31:27 -0800 (PST)
Received: from seagull.rtd.com (seagull.rtd.com [198.102.68.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA14096;
          Sun, 30 Mar 1997 13:31:22 -0800 (PST)
Received: (from dgy@localhost) by seagull.rtd.com (8.7.5/8.7.3) id OAA02640; Sun, 30 Mar 1997 14:31:11 -0700 (MST)
From: Don Yuniskis <dgy@rtd.com>
Message-Id: <199703302131.OAA02640@seagull.rtd.com>
Subject: Re: Another 2.1.7 upgrade & no bin dist
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Sun, 30 Mar 1997 14:31:11 -0700 (MST)
Cc: dwhite@resnet.uoregon.edu, dgy@rtd.com, jkh@freebsd.org, jbarrm@panix.com,
        questions@freebsd.org
In-Reply-To: <20380.859754392@time.cdrom.com> from "Jordan K. Hubbard" at Mar 30, 97 12:39:52 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > > >   DEBUG: Parsing attributes file for distribution bin
> > > >   DEBUG: Parse config: Invalid character 'P' at line 0
> > > >   ...
> > 
> > Hm, unusual.  It's having trouble parsing the bin.inf file.  It looks okay
> > on the 2.1.7 CD -- it matches the one on the 2.1.6 CD pretty closely.
> > Make sure that the /cdrom/bin/bin.inf file looks okay, it should look like
> > this (the first few lines):
> 
> I know this one - it's a bug which has been in sysinstall since day
> one and it only happens occasionally, making it very hard to find

Hmmm... for me, spell "occasionally" as "A-L-W-A-Y-S" (at least the
three different attempts I made to install...  )

> (some data being corrupted somewhere on the 1st pass, so when you
> come through on the 2nd to install more stuff, blooie).
> 
> For 2.2.1, I finally just re-wrote all of that attribute code in
> frustration at not being able to find the bug (and what I ended up
> with was much nicer in the end) and I haven't seen it since.

Grrrr... doesn't much help for a 2.1.7R install now, does it?  :-(

--don