>Number:         4968
>Category:       kern
>Synopsis:       file-system UNION is not visibly marked as being unstable.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Feb 10 00:50:02 1998
>Last-Modified:
>Originator:     Eric Haszlakiewicz
>Organization:
>Release:        2/8/98
>Environment:
System: NetBSD realms.isdn.uiuc.edu 1.3C NetBSD 1.3C (REALMS) #0: Sun Feb 8 20:40:50 CST 1998 root@realms.isdn.uiuc.edu:/REALMS i386


>Description:
	Anyone taking a brief glance at the kernel options won't
notice that the union filesystem has problems until too late.
>How-To-Repeat:
>Fix:
	change the
"file-system UNION	# union file system"
	to say
"file-system UNION	# union file system.  (unstable, see options(4))"

In each kernel config file which has it.
Probably a good idea to put a more descriptive blurb in the options
man page.  Maybe even in the bugs section of the mount_union page.
LFS should probably have something like this too.

*** /tmp/options.4      Tue Feb 10 02:05:59 1998
--- options.4   Tue Feb 10 02:27:10 1998
***************
*** 409,414 ****
--- 409,421 ----
  system. See
  .Xr mount_union 8
  for details.
+ .Pp
+ .sY
+ Warning:
+ .nO
+ The union file system has some significant locking problems.  Use this
+ filesystem at your own risk.  If you do decide to use it it would be best
+ to avoid allowing several processes to access both layers at the same time.
  .El
  .Ss File System Options
  .Bl -ohang

>Audit-Trail:
>Unformatted: