Date: Fri, 17 Apr 2015 09:28:24 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-arch@freebsd.org Cc: Stefan Esser <se@freebsd.org>, Konstantin Belousov <kostikbel@gmail.com>, "freebsd-arch@freebsd.org" <arch@freebsd.org>, peter@freebsd.org, Oliver Pinter <oliver.pinter@hardenedbsd.org> Subject: Re: Removal of the 6.x kernel compat code from libc Message-ID: <14081053.n6WdaDRXXc@ralph.baldwin.cx> In-Reply-To: <5531059F.4060500@freebsd.org> References: <20150417075942.GI2390@kib.kiev.ua> <20150417121034.GN2390@kib.kiev.ua> <5531059F.4060500@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, April 17, 2015 03:07:43 PM Stefan Esser wrote: > Could we get rid of check_utility_compat(3) on that occasion? > > It is only used (AFAIK) to select FreeBSD-4 compatible behaviour of > expr(1), which can also be selected with option "-e" and env variable > COMPAT_EXPR. > > I doubt that anybody relies on non-POSIX behaviour that has been > deprecated for some 15 years ... > > We'll need to preserve a stub function for check_utility_compat(3), > I'm afraid, but I think we can remove the environment variable and > the actual checking for a sym-link named "/etc/compat-FreeBSD-4-util" > at startup of expr. (I bet, nobody even knew that the behaviour of > expr could be changed with above sym-link ...) > > If there is consensus, I could prepare a patch to remove the check > and to update the man-page for expr (just for -CURRENT, no MFC). I would not be surprised if Y!BSD depends on this and uses it in 11 FWIW. :) -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14081053.n6WdaDRXXc>