Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 02 Dec 2009 09:05:29 -0700 (MST)
From:      "M. Warner Losh" <imp@bsdimp.com>
To:        kostikbel@gmail.com
Cc:        fluffy@fluffy.khv.ru, svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: svn commit: r199827 - in head: include lib/libc/compat-43 sys/sys
Message-ID:  <20091202.090529.1219863310.imp@bsdimp.com>
In-Reply-To: <20091202132904.GH2368@deviant.kiev.zoral.com.ua>
References:  <200911261349.nAQDnco2083469@svn.freebsd.org> <200912021926.02346.fluffy@fluffy.khv.ru> <20091202132904.GH2368@deviant.kiev.zoral.com.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20091202132904.GH2368@deviant.kiev.zoral.com.ua>
            Kostik Belousov <kostikbel@gmail.com> writes:
: On Wed, Dec 02, 2009 at 07:25:56PM +1000, Dima Panov wrote:
: > On Thursday 26 November 2009 23:49:38 Konstantin Belousov wrote:
: > > Author: kib
: > > Date: Thu Nov 26 13:49:37 2009
: > > New Revision: 199827
: > > URL: http://svn.freebsd.org/changeset/base/199827
: > > 
: > > Log:
: > >   Implement sighold, sigignore, sigpause, sigrelse, sigset functions
: > >   from SUSv4 XSI. Note that the functions are obsoleted, and only
: > >   provided to ease porting from System V-like systems. Since sigpause
: > >   already exists in compat with different interface, XSI sigpause is
: > >   named xsi_sigpause.
: > > 
: > >   Reviewed by:	davidxu
: > >   MFC after:	3 weeks
: > > 
: > > Modified:
: > >   head/include/signal.h
: > >   head/lib/libc/compat-43/Makefile.inc
: > >   head/lib/libc/compat-43/Symbol.map
: > >   head/lib/libc/compat-43/sigcompat.c
: > >   head/lib/libc/compat-43/sigpause.2
: > >   head/sys/sys/signal.h
: > >   head/sys/sys/signalvar.h
: > 
: > kib, you forgot about osversion bump, it is strongly needed.
: No. My interpretation of __FreeBSD_version is that the bump indicates
: incompatible change in the interfaces. Sometime it is used to mark the
: point where big changes hit the tree, possibly not related to interface
: change.
: 
: Also, __FreeBSD_version denotes the kernel "version". We do support
: running earlier usermode on the later kernels. Think about kernel-only
: upgrades, compatXx libs and jails which can run arbitrary earlier
: usermode. (The change in question is purely libc).
: 
: Said this, I think it is actually harmful practice to bump
: __FreeBSD_version after API additions or feature implementation.
: 
: I can bump version for this case, but due to the above reason,
: it would not make much sense.

In the past, __FreeBSD_version has been used to expose changes in
interfaces (both plus, minus and delta) that are necessary for the
entire system.  Adding an interface definitely qualifies because this
is a build-time issue, not a run time one.

Unfortunately, __FreeBSD_version has also been used to force kernel
recompiles lately since it is encoded in the kernel modules.  Despite
this, it isn't just for kernels...

Warner

: > This changeset caused jdk (may be not only jdk) breakage, as jdk-bsd-patches
: > always provide own implementations of sigingnore() for FreeBSD.
: > 
: > Patch for jdk16 port will be ready soon.
: 
: Ok, thanks for working on this.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091202.090529.1219863310.imp>