Date: Fri, 13 Mar 1998 00:31:15 -0500 (EST) From: Chuck Robey <chuckr@glue.umd.edu> To: Brian Feldman <green@feldman.dyn.ml.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: C++ libs are broken Message-ID: <Pine.BSF.3.96.980313001452.438q-100000@localhost> In-Reply-To: <Pine.BSF.3.96.980312234755.2804C-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 12 Mar 1998, Brian Feldman 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 > 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 Well, really, current _is for_ alpha-testing. It's not for production systems. What you should be asking for, is for your favorite features that are in current and not in 2.2.5, to be brought in, not (please!) for current to be moved back! Softupdates really isn't in current yet, at least not the most of it. The breakage normally in the past has been attributable to a couple of people breaking things haphazardly, whilst doing things that, while needed, weren't truly of primary importance (stuff like style changes). This time, it's been improvements to the NFS and VM system, which is a completely different animal, and (in my mind) truly excuseable because: a) it's really difficult (monstrously so) and really does need the testing efforts of all the current users, and b) it's of major importance to speed, filesystem, and memory usage. Since it's got such importance, it's so terribly hard to do, and needs the testing, there isn't any other choice. It's actually the real reason that current exists. Take my advice and really read the commit mail. The guys doing the (take your pick: ELF upgrades, Alpha port introduction, VM system improvements, NFS improvements, softupdates introduction) are making groundbreaking changes in FreeBSD, and we haven't seen such an exciting group of MAJOR things like this all at one time in years! Personally, I wonder why the FreeBSD web page, and WC's advertising, hasn't picked up on this, and begun some early PR work? The potential, inside the next year, is astounding! Anybody who follows up on this, please do it in FreeBSD-chat ... this doesn't belong in current anymore, and I won't reply here in current. ----------------------------+----------------------------------------------- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980313001452.438q-100000>