processing the error SIGPIPE comes because the client closed the connection,
and then we end up calling error() while processing the error which prints
silly messages on the console because it logs with LOG_EMERG.
- Make these defines and functions private to vfs_vnode.c:
VC_MASK, VC_LOCK, DOCLOSE, VI_IANCTREDO and VI_INACTNOW
vclean() and vrelel()
- Remove the long time unused lwp argument from vrecycle().
- Remove vtryget(), it is responsible for ugly hacks and doesn't
look that effective.
Presented on tech-kern.
Welcome to 6.99.25
The major reason for this update is to support the just-imported lutok-0.3
and, in turn, support the eventual update of the in-tree lua to 5.2.
Changes:
Experimental version released on October 18th, 2013.
* Made failures from testers more resilent. If a tester fails, the
corresponding test case will be marked as broken instead of causing
kyua to exit.
* Added the '--results-filter' option to the 'report-html' command and
set its default value to skip passed results from HTML reports. This
is to keep these reports more succint and to avoid generating tons of
detail files that will be, in general, useless.
* Switched to use Lutok 0.3 to gain compatibility with Lua 5.2.
* Issue 69: Cope with the lack of AM_PROG_AR in configure.ac, which
first appeared in Automake 1.11.2. Fixes a problem in Ubuntu 10.04
LTS, which appears stuck in 1.11.1.
The main reason for this update is the addition of support for Lua 5.2,
which we will want to import sometime.
Released on 2013/06/14.
* Issue 1: Added support for Lua 5.2 while maintaining support for Lua
5.1. Applications using Lutok can be modified to use the new
interface in this new version and thus support both Lua releases.
However, because of incompatible changes to the Lua API, this release
of Lutok is incompatible with previous releases as well.
* Issue 3: Tweaked configure to look for Lua using the pkg-config names
lua-5.2 and lua-5.1. These are the names used by FreeBSD.
Interface changes:
* New global constants: registry_index.
* New methods added to the state class: get_global_table.
* Removed global constants: globals_index.
"bfd_configure.lineno" instead of "configure.lineno" as the name of the
a version of the script that has had all uses of $LINENO converted to
literal line numbers.
Now building tools via "MKCROSSGDB=yes build.sh tools" works again, even
if the shell does not support $LINENO.
The previous problem was caused by an interaction
between the way .../gdb/dist/opcodes/configure executes
"${srcdir}/../bfd/configure --version", and the way both configure
scripts tried to create and then execute configure.lineno scripts.
Both configure.lineno scripts were created in the same OBJDIR,
with the configure.lineno from .../bfd/configure overwriting the
configure.lineno from .../opcodes/configure, while the latter was
still running.
