PROBLEM:	(HPAQC854C, QAR 46335)	(Patch ID: OSF375-365034)
********
This patch fixes a problem in which the nfsportmon command does not
allow the root directory to be mounted from either a Solaris system
or from an ULTRIX Version 4.2A system.

There is a program making it's way around the internet that allows
non-priviledged users to mount filesystems, even if the nfs server is
configured to only allow root users to mount (NONROOTMOUNTS=0 in
/etc/rc.config).  In order to protect against this, customers are using
nfsportmon to enhance the check mechanism.  nfsportmon checks to make sure
that file access requests were generated by the client kernel rather than a
forged application.

However, with nfsportmon turned on, Sun Solaris clients cannot mount
anything, even as root.

For example, if you have a Digital UNIX v3.2c nfs server, and
NONROOTMOUNTS=0 and nfsportmon is on, the root user on another Digital UNIX
system can mount exported directories fine, but the root user on a Solaris
system cannot.  The root user on a Solaris system gets the following error:

# mount sandpiper:/mnt /staff/ajs/mnt
nfs mount: sandpiper: NFS service not responding
nfs mount: retrying: /staff/ajs/mnt

With nfsportmon turned off, the directory mounts fine from Solaris.

In addition to Solaris clients failing, ULTRIX v4.2a clients also fail with
the same error.

PROBLEM:	(CLD HPXQ9722E)		(Patch ID: OSF375-365053-1)
********
This patch allows some third-party NFS v2 clients to experience a
performance improvement.  Candidate applications are ones that
perform read/write operations to a memory mapped file over NFS.

NOTES:

1) This patch must be enabled _BEFORE_ NFS is started because it needs
   to perform some configuration operations before client requests start
   arriving.  This why the dbx patch is to the /vmunix file and not to memory.
   If the patch is applied to memory, it will be ignored, since the
   initialization routine only runs when NFS is started.

2) Affects NFS V2 only.  NFS v3 connections are unaffected.

3) Files that are only read or only written will not be affected.

4) The NFS Dup cache and NFS Write Gathering are disabled by this patch.

 To enable the patch, perform the following steps:

     % dbx -k /vmunix
     (dbx) patch stall_write_patch_enabled=1
     (dbx) quit
     % reboot

5) Steps 1-4 NEED to be performed after any Kernel Rebuild that includes
   this Patch to Enable this Patch.

PROBLEM:        (CLD FNO100139) (Patch ID: OSF375-365063)
********
When a directory path on an NFS server is deleted, any process attempting
to access the missing path will cause NFS stale file handle messages
to be printed on the server's console.

This patch will greatly reduce the number of these messages.

PROBLEM:        (QAR 60285,MCGM91LZQ,UVO105302,EVT102394) (Patch ID: OSF375-157)
********
This patch fixes a problem where the umount of a filesystem will fail
with "mount device busy", but no processes are accessing files in the
filesystem.

PROBLEM:        (QAR 58388)     (Patch ID: OSF375-179)
********
A potential security vulnerability has been discovered, where under certain 
circumstances, system integrity may be compromised. This may be in the form of 
improper file or privilege management.  Digital has corrected this potential 
vulnerability.

PROBLEM:  (QAR 62353, QAR 61253)    (Patch ID: OSF375-220)
********
This patch fixes a problem with NFS conversion of a file's vnode number to
a file handle number.  When a SUN client accessed files on a DIGITAL UNIX
server, the file id was truncated immproperly during the conversion, generating
EOVERFLOW errors.  As a result, a NFS client was receiving EOVERFLOW errors.