From owner-freebsd-current Wed Mar 18 18:43:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20803 for freebsd-current-outgoing; Wed, 18 Mar 1998 18:43:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feldman.dyn.ml.org (green@1Cust52.max2.washington.dc.ms.uu.net [153.34.49.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20798 for ; Wed, 18 Mar 1998 18:43:00 -0800 (PST) (envelope-from green@feldman.dyn.ml.org) Received: from localhost (green@localhost) by feldman.dyn.ml.org (8.8.8/8.8.8) with SMTP id VAA04887; Wed, 18 Mar 1998 21:42:22 -0500 (EST) (envelope-from green@feldman.dyn.ml.org) Date: Wed, 18 Mar 1998 21:42:22 -0500 (EST) From: Brian Feldman To: "Jordan K. Hubbard" cc: Brian Feldman , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: C++ libs are broken In-Reply-To: <19161.889784144@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That's correct, but I have had incredible luck with 3.0. It would be nice to be able to continue using it but it totally broke on me yesterday (almost every program sig1[0-2]'ed). So... I've gone back to 2.2.6-BETA and I'm fine with it, but I wish I had the _time_ to read the mailing lists more often. Oh well, I am content finding any syntax errors that creep into the source and seeing if I can't fix those (which is in my capability, you know, I've been reading =) Jordan: both Number-6 and I have introduced much improved versions of yes(1), and maybe you should consider letting one get into the source tree? Chuck: how good are the computer/programming classes at UMD? It would be nice to go somewhere and not be paying out-of-state-college-fees, you know? Best of luck, Brian "content with FreeBSD 2.2*" Feldman On Fri, 13 Mar 1998, Jordan K. Hubbard wrote: > > Yes, you're right. I was quite miffed when I wrote that message. It's just > > that 3.0 can be so stable, and working, I hate to see it get messed up all > > the time. Some people really take too much liberty committing any change > > Well, FWIW, we've talked before and I've already told you several > times that I didn't think you should be running -current; you haven't > got the prerequisites (you don't read the right mailing lists and you > definitely shouldn't be out on the bleeding edge in general). I don't > think -current should be blamed for inappropriate use here. > > Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message