Okay, if you are not ready to publicize alarm, I will leave that undocumented
on Solaris. It also sounds like vpath and vmap are not usable on Solaris,
so I will leave those out as well.
Thanks,
April
> Date: Tue, 8 Aug 2006 10:04:34 -0400 (EDT)
> From: David Korn <dgk at research.att.com>
> Mime-Version: 1.0
> Content-Transfer-Encoding: 7bit
> To: ksh93-integration-discuss at opensolaris.org
> Subject: Re: [ksh93-integration-discuss] ksh93 manpages for vmap, alarm,
vpath built-ins?
> Cc: April.Chin at eng.sun.com
>
>
> April Chin wrote:
> > I'm in the process of filing manpage bugs for ksh93 to include
> > changes to existing pages and new manpages for ksh93(1) and its
> > builtins (builtin(1), disown(1)).
> >
> > CR 6457823 New manpages needed for ksh93
> >
> > However, I do not see any manpages for vmap(1), alarm(1), or vpath(1).
> > Are there any? nroff versions would be preferable, as this could make
> > the manpage work easier. I do have nroff versions for the others.
>
>
> alarm(1) is an undocumented feature that allows multiple event
> timeouts. I have concerns about how it might interact with future
> planned extensions so I have not advertized it. I might consider adding
> a self generating man page for it.
>
> vpath and vmap require the 3D file system. I have included an old man
> page for vpath.1 below.
>
> The 3d file system allows users to virtually overlay file trees
> to create a single view with copy-on-write semantics to the
> top layer. It did this by intercepting path name system calls
> with a preload library. The vpath built-in was used to set
> up the overlays. Without the preload library vpath fails because
> of an invalid mount() call which would have been picked up
> only if the LD_PRELOAD library is used.
>
> Another 3d extension was the ability to support multiple versions
> of the same file in a single file using a delta format.
> You could reference each version instance explicitly with
> using foo.c/instance or get the latest version of foo using foo.c.
> The vmap builtin controlled the order of the version search
> and defined the instance name for newly created versions.
>
> ====================vpath.1=============================
> .\"
> .\" G. S. Fowler
> .\" D. G. Korn
> .\" AT&T Bell Laboratories
> .\"
> .\" @(#)vpath.1 (dgk at research.att.com) 10/22/91
> .\"
> .de L \" literal font
> .ft 5
> .it 1 }N
> .if !\\$1 \&\\$1 \\$2 \\$3 \\$4 \\$5 \\$6
> ..
> .de LR
> .}S 5 1 \& "\\$1" "\\$2" "\\$3" "\\$4" "\\$5" "\\$6"
> ..
> .de RL
> .}S 1 5 \& "\\$1" "\\$2" "\\$3" "\\$4" "\\$5" "\\$6"
> ..
> .de EX \" start example
> .ta 1i 2i 3i 4i 5i 6i
> .PP
> .RS
> .PD 0
> .ft 5
> .nf
> ..
> .de EE \" end example
> .fi
> .ft
> .PD
> .RE
> .PP
> ..
> .TH VPATH 1
> .SH NAME
> vpath \- Modify or display the viewpath table for 3d filesystem
> .SH SYNOPSIS
> .B vpath
> [
> .I top
> .I bottom
> ] ...
> .SH DESCRIPTION
> If at least one
> .I bottom
> is specified,
> each pair of arguments specifies a top level file tree followed
> by the file tree that it is to cover.
> If
> .I bottom
> is null, the previous
> mapping for
> .I top
> will be removed from the table.
> .PP
> If one
> .I top
> is specified,
> and
> .I bottom
> is not specified,
> .B vpath
> applies the existing path mappings to
> .I top
> and
> prints an absolute pathame that does not contain any
> .BR . ,
> .BR .. ,
> or
> .B ...
> components.
> .PP
> If
> .B vpath
> is invoked without arguments,
> it writes the current viewpath mapping table, one map pair per line,
> with the top listed first.
> .PP
> Because
> .B vpath
> effects the current process environment, it is implemented as
> a shell built-in.
> .PP
> .SH "SEE ALSO"
> vmap(1),
> 2d(1),
> opaque(1),
> 3d(1),
> ksh(1),
> ====================vpath.1=============================
>
> David Korn
> dgk at research.att.com
