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 > <allbery_at_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_at_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_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"Received on Fri Oct 15 2004 - 06:13:57 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:17 UTC