From owner-freebsd-current Sun Mar 26 11:53:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA23075 for current-outgoing; Sun, 26 Mar 1995 11:53:42 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA23067 for ; Sun, 26 Mar 1995 11:53:39 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id LAA05385; Sun, 26 Mar 1995 11:53:29 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id LAA00456; Sun, 26 Mar 1995 11:53:29 -0800 Message-Id: <199503261953.LAA00456@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Bruce Evans cc: current@FreeBSD.org Subject: Re: shared library versioning In-reply-to: Your message of "Mon, 27 Mar 95 05:45:16 +1000." <199503261945.FAA29708@godzilla.zeta.org.au> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 26 Mar 1995 11:53:28 -0800 Sender: current-owner@FreeBSD.org Precedence: bulk >>>The recent change to the msync() interface strictly requires incrementing >>>the major number of libc.so. > >> I don't agree. The library itself should remain unchanged. Things would be >>different if I had added a new syscall...but that's not what happend - I just >>added an additional argument, and libc doesn't know about how many arguments a >>syscall has. > >Yes, this problem can't be solved in the library. A new syscall is required. >Old callers don't supply the additional arg. In other cases this would be true...but msync has never worked correctly in FreeBSD - it always returned EINVAL because of bugs in it. I just fixed this a few days ago. In the current scheme, passing garbage to msync() for the flags will be no worse than the previous behavior. I suggest we just leave it alone unless you have some other reason to bump the libc major number. -DG