From owner-freebsd-current Thu Mar 12 20:53:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20775 for freebsd-current-outgoing; Thu, 12 Mar 1998 20:53:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feldman.dyn.ml.org (green@1Cust1.max1.washington.dc.ms.uu.net [153.34.49.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20766 for ; Thu, 12 Mar 1998 20:52:54 -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 XAA02838; Thu, 12 Mar 1998 23:52:36 -0500 (EST) (envelope-from green@feldman.dyn.ml.org) Date: Thu, 12 Mar 1998 23:52:35 -0500 (EST) From: Brian Feldman To: Chuck Robey cc: Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: C++ libs are broken In-Reply-To: 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 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 they want. I know right now, Alpha stuff, ELF stuff, and soft-updates (bleh, it's SO unstable!), are getting worked on, but I think people really do need to test their changes and compile to make sure they didn't break anything like this. I really should read commit mail, but I have no good mail box to use, since this is just my dynamic IP'd 28.8 part-time dial-up anyway. *sigh* I need to go send a pr, because mounted synchronously, mount's output shows my drives with async (!) and sync write.... majorly weird. Maybe we need to get softupdates backed out a bit. Happy alpha-testing, Brian Feldman On Mon, 9 Mar 1998, Chuck Robey wrote: > On Mon, 9 Mar 1998, Brian Feldman wrote: > > > > > You know, I'm surprised I've only seen this twice (cut out the damn > > stackable FS talk, so we can talk about what's happening NOW!), and have > > noticed it quite a bit myself, that the newest C++ libraries ARE BROKEN! I > > wish someone might pay a tiny bit of attention to this, because it's > > really annoying (2.2.5-RELEASE's C++ libs are less than fully functional > > to use). Might someone want to see what commit changes have been made and > > fix these libraries? > > Keep some perspective ... current's been the target of some folks who > abused the privilege, but the stuff about the filesystems IS a good, and > really interesting "current" topic. You can ask about the C++ libs, but > not at the expense of what others are doing ... that's selfish. > > Besides, if you're reading the commit mail, you know that the C++ libs > are currently the topic of a lot of work, they haven't been badly busted > all that long, give them some time. They already know things are > unstable (the reason is because the ELF stuff *and* the Alpha stuff are > both hitting the C++ libs at the same time) so this just calls for a > little patience. A heads up ("this is broken") is a good thing, but not > calling off debate of important topics in design. > > > > > -Brian Feldman > > brianfeldman@hotmail.com > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@glue.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > (301) 220-2114 | version 3.0 current -- and great FUN! > ----------------------------+----------------------------------------------- > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message