From owner-freebsd-current@FreeBSD.ORG  Fri Oct 15 13:50:33 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4A3D716A520
	for <freebsd-current@freebsd.org>;
	Fri, 15 Oct 2004 13:50:33 +0000 (GMT)
Received: from CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com
	(CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com [69.193.222.195])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C737B43D6E
	for <freebsd-current@freebsd.org>;
	Fri, 15 Oct 2004 13:50:28 +0000 (GMT)
	(envelope-from mikej@rogers.com)
Received: from cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com
	(localhost [127.0.0.1])with ESMTP id AFDAC29542A;
	Fri, 15 Oct 2004 09:50:26 -0400 (EDT)
Received: from 66.11.183.178
        (SquirrelMail authenticated user mikej);
        by cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com with 
     HTTP;
        Fri, 15 Oct 2004 09:50:26 -0400 (EDT)
Message-ID: <1076.66.11.183.178.1097848226.squirrel@66.11.183.178>
In-Reply-To: <c21e92e204101501097e14bf6e@mail.gmail.com>
References: <1542.192.168.0.188.1097646528.squirrel@192.168.0.188> 
    <416D2482.2090000@gamersimpact.com> 
    <1099.66.11.183.178.1097672454.squirrel@66.11.183.178> 
    <1097673727.10151.0.camel@rushlight.kf8nh.com>
    <c21e92e204101501097e14bf6e@mail.gmail.com>
Date: Fri, 15 Oct 2004 09:50:26 -0400 (EDT)
From: "Mike Jakubik" <mikej@rogers.com>
To: "Jiawei Ye" <leafy7382@gmail.com>
User-Agent: SquirrelMail/1.4.3a
X-Mailer: SquirrelMail/1.4.3a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-wettoast-MailScanner-Information: Please contact the ISP for more
	information
X-wettoast-MailScanner: Found to be clean
X-MailScanner-From: mikej@rogers.com
cc: Ryan Sommers <ryans@gamersimpact.com>
cc: freebsd-current@freebsd.org
Subject: Re: Odd behaviour from bash after recent cvsup and world...
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2004 13:50:33 -0000

Jiawei Ye said:
> On Wed, 13 Oct 2004 09:22:08 -0400, Brandon S. Allbery KF8NH
> <allbery@ece.cmu.edu> wrote:
>> On Wed, 2004-10-13 at 09:00, Mike Jakubik wrote:
>> > Ah, no problem, its not a big deal. I did miss it, was it a HEADSUP?
>>
>> Yes.  (Well, a mini heads-up.)
>>
>> --
>> brandon s. allbery    [linux,solaris,freebsd,perl]     allbery@kf8nh.com
> syscons seems to be unbroken now, but bash problem persists. Anyone
> else seeing this as well?

Yes, me. I cvsuped and made world yesterday around 2pm EST, and its still
broken.