Get __STRICT_ALIGNMENT from <machine/endian.h> and decide upon it, rather
than defining it for not (i386 and amd64 (and sometimes s390)) only.

Compile-time tests remain compile-time tests, and runtime-test remain
runtime-test instead of being converted to compile-time tests, per matthew@'s
explicit demand (rationale: this makes sure the compiler checks your code even
if you won't run it).

No functional change except on s390 (which we don't run on) and vax (which we
run on, but noone cares about)

ok matthew@
Handle colour 8 properly in the 256 colour palette, from Timothy Allen.
Both the two previous ways of navigating panes by direction have
irritating flaws:

a) The old way of always using the top or left if the choice is
ambiguous is annoying when the layout is unbalanced.

b) The new way of remembering the last used pane is annoying if the
layout is balanced and the leftmost is obvious to the user (because
clearly if we go right from the top-left in a tiled set of four we want
to end up in top-right, even if we were last using the bottom-right).

So instead, use a combination of both: if there is only one possible
pane alongside the current pane, move to it, otherwise choose the most
recently used of the choice.
Plug a memory leak, from J Raynor.
+.Xr less 1 ,
- update DESCRIPTION and COMPATIBILITY WITH MORE
- Xr more 1

ok millert schwarze
whack some useless verbiage from DESCRIPTION, and merge some of it into
the env vars section; tidy up the env vars section and remove the commented
out stuff which relataes mainly to less on other systems;
Instead of forcing mouse scroll to 1 in choose mode, scale it down
instead. Means modifier keys still increase the line count, just not as
much. Based on a diff from Marcel Partap.
Send up and down keys for mouse wheel in alternate screen mode (when it
normally does nothing), from Marcel Partap.
Introduce two new route flags: RTF_LOCAL and RTF_BROADCAST.

Nothing use them for the moment, but here is the plan:

Since a route lookup is always necessary to output a packet it makes
sense to store all the information regarding how the packet should be
sent in the routing entry.  This will save us some expensive lookups
on address lists.

But once we have all the information about our addresses in the routing
table, we can even use it in the input path with the hope that the number
of lookups in the forwarding case can be reduce to one.

ok henning@, chris@
Sync flags with route.h
kill some more VMS ifdefs
ok miod@
Bring back restricted sockets, inadvertantly removed in
previous proc.c update

ok reyk@
inet(3) -> inet_net(3);
match relayd proc.c infrastructure with snmpd

okay reyk@
match iked proc.c infrastructure with proc.c

ok reyk@
Emergency knfectomie requested by tedu@.
knfectomie.
Plug one more xfer leak.

Now that aborting interrupt pipes does not prevent us from freeing
the associated xfer, make sure to flag this xfer as "done" even if
there's no need to abort it in hardware.
Pretty print MIB_ipNetToMediaPhysAddress'es;  ok blambert