From owner-freebsd-current Wed Mar 13 08:42:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA07794 for current-outgoing; Wed, 13 Mar 1996 08:42:05 -0800 (PST) Received: from covina.lightside.com (covina.lightside.com [198.81.209.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA07788 for ; Wed, 13 Mar 1996 08:42:03 -0800 (PST) Received: by covina.lightside.com (Smail3.1.28.1 #6) id m0twtcf-0004HvC; Wed, 13 Mar 96 08:42 PST Date: Wed, 13 Mar 1996 08:41:59 -0800 (PST) From: Jake Hamby To: current@FreeBSD.ORG Subject: Questions for current hackers.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have a few questions about recent developments in -current. These are just for my own curiosity, don't take them as complaints or criticism because they aren't. I was only added to the CVS mailing list recently so I haven't been keeping up with the reasoning behind recent changes. 1) Why was libc's major version number bumped to 3? Was this to incorporate changes to make it thread-safe or for some other reason(s)? Is it safe to assume that the version won't be bumped again before 2.2-RELEASE? 2) Over the last several months, various changes have been made to the VM code that have, at times, left -current in a rather unstable state (Sig 11's and whatnot). A number of people experienced problems just recently, with the 3/3 SNAP and kernels built around this time. What exactly is the reasoning behind all of these VM changes, are they to boost performance, reduce swap utilization, or what? Thanks in advance.. ---Jake