the receive code so that it correctly chains receive descriptors together
and handles the case that only a part of a packet is done at the time
we get here.
the string "FreeBSD". Use the .Fx macro instead. Also did some
minor re-wording/formatting to work around a deficiency with
the .Fx macro when it comes to puncuation characters other than
periods and commas.
tells that tun unit to prepend a four byte address family to packets
queued for tunread() and to expect a four byte address family at the
front of data received by tunwrite().
We queue any protocol received from the interface for tunread(), but
only accept INET, INET6, IPX and NETATALK from tunwrite(). There is
support for Xerox's NS stuff, but AFAICT config(8) doesn't ever
define NS.
Oh why did I select a first project that needed to touch release/Makefile..
The fact that my release-building Alpha panics on me does not help either :(
From "Alexander N. Kabaev" <ak03@gte.com>:
The problem is that default builtin_setjmp implementation does not restore
any registers except for stack pointers when doing nonlocal jump. This
means, that every platform, that needs to store/restore some other state
between jumps, has to provide appropriate definitions for
builtin_setjmp_setup and builtin_setjmp_receiver RTL expansions.
Every plaftorm which needs to do some additional processing at setjmp
receive point, such as restoring additional information previously saved by
builtin_setjmp_setup, can provide definition for builtin_setjmp_receiver
RTL expansion. [That is what the previous commit does.] The i386 code
compiled with -fpic option requires the value of the PIC register (EBX) to
be restored in order to function properly. One should not provide
expansion for builtin_setjmp_setup because GCC documentation explicitly
states that values should be recalculated if possibe, rather than stored in
setjmp buffer and proper value for EBX can easlity be determined from the
current EIP contents.
invalidation code cannot wait for paging to complete while holding a
vnode lock, so we don't wait. Instead we simply allow the lower level
code to simply block on any busy pages it encounters. I think Yahoo
may be the only entity in the entire world that actually uses this
msync feature :-).
Bug reported by: Paul Saab <paul@mu.org>
in [i386,alpha]HARDWARE.TXT. This particular file is destined to be
the generic HARDWARE.TXT. In [i386,alpha]HARWDARE.TXT the machdep
information will live from now on. This should fix the make release
failures people were experiencing.
Reviewed by: Peter Wemm
o Make sure every entry has a logger event on insert/delete
o Make sure that the order of loggers is consistant
o Add D-Link DEF-650
o use /sbin/ifconfig consistantly
o Add Elecom Laneed LD-CDE, NTT DoCoMo Paldio 321S and 341S
(from shige@FreeBSD.org)
