ptyname[] must not be static, the contents are modified later in the routine
g/c #if 0'ed code
move dupfd from struct proc to struct lwp - it's per-LWP, not per-process; we
use curlwp where the lwp is not directly available, i.e. in device open
routines

briefly discussed on tech-kern
Bump version to 1.6ZA - struct proc and struct lwp changes
Deja vu ...
note the LKM versioning change
Update pkg_install to 20030913.  Changes from version 20020912 are quieting
the file removal when deleting linkfarms if the expected file doesn't
exist.  Since the symlink isn't there, the mission is already accomplished,
so why bother with the warning?
Add a regression test for testing that here documents don't confuse the
exit status of the previous command ($?).  Fixed long ago on -current,
but forgot to commit this test...
Use HW_USERMEM64 to fetch the amount of memory available.
Remove a variable that is assigned to but not used.
Fix a tyop, wrap some long lines.
fix description of Intel PRO/100 VM Network Controller with 82562ET/EZ PHY
don't activate any quirks for VM_6 variant
problem reported by Lars Heidieker on current-users

also don't activate any quirks for VM_3 - VM_5 variants, neither
VE_2 - VE_4, in anticipation that the more modern variants don't need
the quirks
Remove an unreachable return statement (and fix a whitespace nit).
regen - fix description of one Intel PRO/100 VM variant, as reported
by Lars Heidieker on current-users@
Make some variables unsigned since that's the type of parameter they're
passed as to other functions.
Add COMPAT_16 to most arm based kernels.  Mainly in preperation for doing
SA_SIGINFO work.
Commit changes proposed in
http://mail-index.netbsd.org/tech-kern/2003/09/06/0001.html
http://mail-index.netbsd.org/tech-kern/2003/09/06/0006.html
to avoid compat problems with old ffsv1 by reuse of the old FS_SWAPPED
value for FS_FLAGS_UPDATED, and use of new, larger fields:
- Don't use FS_FLAGS_UPDATED to see if we need to update new fields from
  old fields in ffsv1 case.
- when writing back the superblock, copy back the flags to the old location
  if only old flags are set (FS_FLAGS_UPDATED won't be set in this case)
  in ffsv1 case.
Remove spurious whitespace.
make sure to not get flags which are for internal use only from the on-disk
superblock.
Proposed in http://mail-index.netbsd.org/tech-kern/2003/09/06/0005.html
Tidy up a couple of bits to avoid duplication within the switch.
Make sure the "raw partition" can always be opened again.