From owner-freebsd-current@FreeBSD.ORG Fri Oct 15 08:13:57 2004 Return-Path: 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 BB43916A4CE for ; Fri, 15 Oct 2004 08:13:57 +0000 (GMT) Received: from mail.parodius.com (mail.parodius.com [64.62.145.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96E0543D3F for ; Fri, 15 Oct 2004 08:13:57 +0000 (GMT) (envelope-from jdc@pentarou.parodius.com) Received: from pentarou.parodius.com (jdc@localhost [127.0.0.1]) by mail.parodius.com (8.13.1/8.13.1) with ESMTP id i9F8Dup8025199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 15 Oct 2004 01:13:57 -0700 (PDT) (envelope-from jdc@pentarou.parodius.com) Received: (from jdc@localhost) by pentarou.parodius.com (8.13.1/8.13.1/Submit) id i9F8Dukd025198 for freebsd-current@freebsd.org; Fri, 15 Oct 2004 01:13:56 -0700 (PDT) (envelope-from jdc) Date: Fri, 15 Oct 2004 01:13:56 -0700 From: Jeremy Chadwick To: freebsd-current@freebsd.org Message-ID: <20041015081356.GA25136@parodius.com> Mail-Followup-To: freebsd-current@freebsd.org 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2004 08:13:57 -0000 Not this exact problem, but I did report some bizarre behaviour with bash (2.x and 3.x) in another thread. Possibly related to your situation, possibly not; hard to tell. http://lists.freebsd.org/pipermail/freebsd-current/2004-October/039841.html I still need to bust out tcpdump and compare systems/networks, either that or simply try another NIC to see if it's bge-related. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. | On Fri, Oct 15, 2004 at 04:09:45PM +0800, Jiawei Ye wrote: > On Wed, 13 Oct 2004 09:22:08 -0400, Brandon S. Allbery KF8NH > 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? > > Jiawei > -- > "Without the userland, the kernel is useless." > --inspired by The Tao of Programming > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"