Prevent overflow with fragmented packets
Reviewed by: wollman
Comment the UID games -> GID games change - mention the known problems with
it and ask for feedback on any unknown ones.
Remove HIDEGAME, it is not a game
Remove revoke privs, not needed
Put a system call not present checking wrapper around the call to
__getcwd().  I've got this libc code running on one of my machines
at the moment without the __getcwd() syscall being present.
Some adjustments for the resolver use of poll().  For some reason I thought
an unimplemented syscall returned ENOSYS, rather than EINVAL.  I have run
statically linked code with this wrapper and it does appear to work fine
on 2.2-stable which doesn't have poll().  ktrace shows the poll syscall fail
once and the fallback to select() working.
Police from style.9 and Bruce.
Make FDC_DEBUG a supported option.

Hide the bogus FDC ``chip type'' display behind a (mostly) undocumented
option, since people started to trust the bogus claim.  Once we're going
to handle 2.88 MB controllers, we have to redo the chip detection, by
now just leave it hidden.
Don't leak memory,  from sef.
Stylistic nits and a blunder, from bde.
Sigh, there's always one more buffer overflow. :-(
This one hinted to by the recently posted exploit (although not exploited by
it).
devfs changes to allow old (better) and newer (braindamaged) behaviour.
I'm going to try migrate back, while keeping the newer code.
Reject attempts to set an in-core label which says that the "disk"
or a partition is larger than the slice.

Now `disklabel -Brw sdX auto' should fail properly on sliced disks
without partition of type 165, e.g., on zip disks with the factory
default formatting.  Previously it set a bogus in-core label for
the compatibility slice and used this to corrupt the MBR (the slice
has offset 0 and size 0, but setting the label in effect corrupted
its size to nonzero).

`disklabel -Brw sdX auto' already failed properly on normally (not
dangerously dedicated) sliced disks _with_ partition of type 165,
because the compatibility slice has a nonzero offset so the MBR
remained inaccessible when the size was corrupted.

This bug only affected in-core labels.  On-disk labels are checked
carefully when they read and written.
MF22: pst's changes.
Submitted by:	pst
Backed out rev.1.136 and rev.1.144.  Force SHARED=symlinks in a different
way - for buildworld only.

Rev.1.136 broke the (deprecated) external includes target.  Rev.1.144 was
a half-baked backout of rev.1.136.  It broke SHARED=symlinks for the
buildworld target and installation of subdirs of src/include for the
includes target.
Removed installhdrs target.  It was an unnecessary complication.
Fixed gratuitous ANSIisms.
Fixed staticization.  buckets[] was staticized but was still declared
extern in <sys/malloc.h> and it should not have been staticized for
the !(KMEMSTATS || DIAGNOSTIC) case.

Fixed the !(KMEMSTATS || DIAGNOSTIC) case.  The MALLOC() and FREE()
macros are evil, but code generally doesn't allow for this and some code
involving else clauses did not compile.

Finished staticization.
Removed declaration of nonexistent function fuibyte().

Sorted some declarations.

Fixed missing __P(())'s.

Removed `timeout_func_t (pointer to timeout function) typedef.  It was
mainly used in bogus casts.  The more useful `timeout_t' (timeout function)
typedef should be used instead.

Cleaned up callout declarations and comments.
Cleaned up.
Fixed syntax errors in `#if 0' code.