[2020] in testers
decmips 7.4E: attach(1)
daemon@ATHENA.MIT.EDU (mhpower@Athena.MIT.EDU)
Thu Jun 4 20:45:01 1992
From: mhpower@Athena.MIT.EDU
To: testers@Athena.MIT.EDU
Date: Thu, 04 Jun 92 20:44:31 EDT
System name: podge
Type and version: KN01 7.4E (1 update(s) to same version)
Display type: PMAX-MFB
What were you trying to do?
Get more information on the details on attach.
What's wrong:
The man page has a missing word, misspellings,
inconsistencies, and references to an obsolete program name.
What should have happened:
This patch should fix much of this:
*** attach.1.old Thu Jun 4 20:22:33 1992
--- attach.1 Thu Jun 4 20:27:29 1992
***************
*** 12,18 ****
.fi
.SH DESCRIPTION
! \fIAttach\fP is a filesystem-independent utility which allows you
attach a filesystem to a directory hierarchy on your
workstation. The following filesystems are currently supported: NFS
(Network File Protocol), RVD (Remote Virtual Disk), UFS (Unix file
--- 12,18 ----
.fi
.SH DESCRIPTION
! \fIAttach\fP is a filesystem-independent utility which allows you to
attach a filesystem to a directory hierarchy on your
workstation. The following filesystems are currently supported: NFS
(Network File Protocol), RVD (Remote Virtual Disk), UFS (Unix file
***************
*** 21,32 ****
Attach looks up \fIfilesystem\fP in attach.conf(5) or by
using Hesiod(3) to retrieve the file system type, the server host, the
name by which the file system is known to the server (e.g., an RVD
! locker name or NFS server mountpoint), and the default mount point and
mode (read-only, read-write). The user may also explicitly specify
this information, as described below under the -explicit option.
! Using the various options specified below, it is possible to supercede
! the default mount point and mode. In addition, the user can specify
that a filesystem be nosuid, so that the operating system will not
honor setuid or setgid permissions on the foreign filesystem. The
system maintainer may also forcibly set a filesystem so that it will
--- 21,32 ----
Attach looks up \fIfilesystem\fP in attach.conf(5) or by
using Hesiod(3) to retrieve the file system type, the server host, the
name by which the file system is known to the server (e.g., an RVD
! locker name or NFS server mountpoint), and the default mountpoint and
mode (read-only, read-write). The user may also explicitly specify
this information, as described below under the -explicit option.
! Using the various options specified below, it is possible to supersede
! the default mountpoint and mode. In addition, the user can specify
that a filesystem be nosuid, so that the operating system will not
honor setuid or setgid permissions on the foreign filesystem. The
system maintainer may also forcibly set a filesystem so that it will
***************
*** 66,72 ****
Display verbose information about a mounted filesystem, such as the
NFS or RVD server and the server's filesystem name, if the attach is
successful. This is the default. Use of this option automatically
! supresses the -printpath option.
.IP "-quiet or -q"
Don't display verbose information. Error messages will still be printed.
.IP "-force or -f"
--- 66,72 ----
Display verbose information about a mounted filesystem, such as the
NFS or RVD server and the server's filesystem name, if the attach is
successful. This is the default. Use of this option automatically
! suppresses the -printpath option.
.IP "-quiet or -q"
Don't display verbose information. Error messages will still be printed.
.IP "-force or -f"
***************
*** 85,91 ****
to source a C shell command file relative to this pathname, which
presumably can set up execution paths and other environment variables
appropriate for the use of this filesystem. Use of this option
! automatically surpresses the -verbose option.
.IP "-lookup or -l"
This option causes \fIattach\fP to lookup the filesystem definition
using either attach.conf(5) or Hesiod(3) and print out the definition,
--- 85,91 ----
to source a C shell command file relative to this pathname, which
presumably can set up execution paths and other environment variables
appropriate for the use of this filesystem. Use of this option
! automatically suppresses the -verbose option.
.IP "-lookup or -l"
This option causes \fIattach\fP to lookup the filesystem definition
using either attach.conf(5) or Hesiod(3) and print out the definition,
***************
*** 114,122 ****
.IP "-readonly or -r, -write or -w"
Overrides the default access mode for the next filesystem.
"-r" indicates read-only access, and "-w" indicates write access.
! .IP "-mountpoint \fImount-point\fP or -m \fImount-point\fP"
! Overrides the default mount point for the next filesystem. The
! \fImount-point\fP must be an absolute pathname.
.IP "-noexplicit or -x"
Tell \fIattach\fP to interpret the \fIfilesystem\fP as a Hesiod name.
This if the default.
--- 114,122 ----
.IP "-readonly or -r, -write or -w"
Overrides the default access mode for the next filesystem.
"-r" indicates read-only access, and "-w" indicates write access.
! .IP "-mountpoint \fImountpoint\fP or -m \fImountpoint\fP"
! Overrides the default mountpoint for the next filesystem. The
! \fImountpoint\fP must be an absolute pathname.
.IP "-noexplicit or -x"
Tell \fIattach\fP to interpret the \fIfilesystem\fP as a Hesiod name.
This if the default.
***************
*** 125,131 ****
now interpreted as \fIhost:directory\fP (in the case of NFS) or
\fIhost:pack\fP (in the case of RVD) instead of as a Hesiod name.
This allows arbitrary directories to be attached. When this option is
! used, the default mount point is \fI/host/directory\fP for NFS
filesystems (\fI/host/root\fP for host:/), and \fI/host/pack\fP for
RVDs. This can still be overridden by the -m option.
.IP "-type \fIfilesystem-type\fP or -t \fIfilesystem-type\fP"
--- 125,131 ----
now interpreted as \fIhost:directory\fP (in the case of NFS) or
\fIhost:pack\fP (in the case of RVD) instead of as a Hesiod name.
This allows arbitrary directories to be attached. When this option is
! used, the default mountpoint is \fI/host/directory\fP for NFS
filesystems (\fI/host/root\fP for host:/), and \fI/host/pack\fP for
RVDs. This can still be overridden by the -m option.
.IP "-type \fIfilesystem-type\fP or -t \fIfilesystem-type\fP"
***************
*** 169,175 ****
specified.
.PP
! If the default mount-point for a filesystem (or the mount-point
specified with the -m option) does not exist, it is created. Any
directories in the path that do not exist are also created. If a
directory can't be created, the attach fails. When the filesystem is
--- 169,175 ----
specified.
.PP
! If the default mountpoint for a filesystem (or the mountpoint
specified with the -m option) does not exist, it is created. Any
directories in the path that do not exist are also created. If a
directory can't be created, the attach fails. When the filesystem is
***************
*** 203,209 ****
Attach the filesystem \fIx11\fP to the mountpoint /mymount/X11 in
read-only mode. Then attach the filesystem \fIgnu\fP
! to its default mount point in write mode. Don't print success
messages for either mount.
.SH DIAGNOSTICS
--- 203,209 ----
Attach the filesystem \fIx11\fP to the mountpoint /mymount/X11 in
read-only mode. Then attach the filesystem \fIgnu\fP
! to its default mountpoint in write mode. Don't print success
messages for either mount.
.SH DIAGNOSTICS
***************
*** 224,230 ****
Internal fatal error.
.TP 5
10
! Keberos failure.
.TP 5
11
Host communication failure.
--- 224,230 ----
Internal fatal error.
.TP 5
10
! Kerberos failure.
.TP 5
11
Host communication failure.
***************
*** 268,276 ****
the exit status 2 after attempting to attach all the other filesystems.
.SH NOTE
! The programs \fIattach(1)\fP, \fIdetach(1)\fP, \fInfsid(1)\fP, and
\fIzinit(8)\fP are all really the same program. Typically
! \fIdetach(1)\fP, \fInfsid(1)\fP and \fIzinit(8)\fP are links to
\fIattach\fP. Argv[0] is used to determine which one of the four
programs are run. This may be overridden by specifying -P
\fIprogname\fP, where \fIprogname\fP should be one of the above four
--- 268,276 ----
the exit status 2 after attempting to attach all the other filesystems.
.SH NOTE
! The programs \fIattach(1)\fP, \fIdetach(1)\fP, \fIfsid(1)\fP, and
\fIzinit(8)\fP are all really the same program. Typically
! \fIdetach(1)\fP, \fIfsid(1)\fP and \fIzinit(8)\fP are links to
\fIattach\fP. Argv[0] is used to determine which one of the four
programs are run. This may be overridden by specifying -P
\fIprogname\fP, where \fIprogname\fP should be one of the above four
***************
*** 283,289 ****
.SH "SEE ALSO"
! detach(1), nfsid(1), zinit(1), zephyr(1), hesiod(3)
.br
`Hesiod - Project Athena Technical Plan -- Name Service'
.br
--- 283,289 ----
.SH "SEE ALSO"
! detach(1), fsid(1), zinit(1), zephyr(1), hesiod(3)
.br
`Hesiod - Project Athena Technical Plan -- Name Service'
.br
Please describe any relevant documentation references:
attach(1)
