[2026] in testers
decmips 7.4E: attach(1), attach.conf(5), detach(1), fsid(1)
daemon@ATHENA.MIT.EDU (mhpower@Athena.MIT.EDU)
Fri Jun 5 14:48:55 1992
From: mhpower@Athena.MIT.EDU
To: testers@Athena.MIT.EDU
Date: Fri, 05 Jun 92 14:48:12 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?
Find various information about attach and related programs.
What's wrong:
There's an obsolete path (/afs/athena/mit/andrew/@sys/aklog),
references to the name nfsid (rather than fsid), missing words,
spurious extra words, misspellings, and other formatting problems.
What should have happened:
*** attach.1.old Fri Jun 5 13:24:04 1992
--- attach.1 Fri Jun 5 13:25:28 1992
***************
*** 147,153 ****
nosuid.
.IP "-override or -O"
\fIAttach\fP can be set up so that normal users cannot attach certain
! filsystems. A trusted user can use this option to override these
restrictions. See attach.conf(5) for more information.
.IP "-skipfsck or -F"
This option indicates that the \fIfsck\fP command should not be run.
--- 147,153 ----
nosuid.
.IP "-override or -O"
\fIAttach\fP can be set up so that normal users cannot attach certain
! filesystems. A trusted user can use this option to override these
restrictions. See attach.conf(5) for more information.
.IP "-skipfsck or -F"
This option indicates that the \fIfsck\fP command should not be run.
*** attach.conf.5.old Fri Jun 5 12:58:17 1992
--- attach.conf.5 Fri Jun 5 13:18:06 1992
***************
*** 5,11 ****
The behavior of
.IR Attach , detach ,
and
! .I nfsid
are controlled by attach.conf. These programs read /etc/athena/attach.conf
when they start up, so the system administrator can customize their
behavior without needing to recompile the programs.
--- 5,11 ----
The behavior of
.IR Attach , detach ,
and
! .I fsid
are controlled by attach.conf. These programs read /etc/athena/attach.conf
when they start up, so the system administrator can customize their
behavior without needing to recompile the programs.
***************
*** 38,44 ****
applies if the regular expression matches the filesystem being
attached or detached.
.IP regexp-list
! Keywords of type regexp-list take oneor more arguments, which are
regular expressions.
.PP
The following keywords are supported in attach.conf:
--- 38,44 ----
applies if the regular expression matches the filesystem being
attached or detached.
.IP regexp-list
! Keywords of type regexp-list take one or more arguments, which are
regular expressions.
.PP
The following keywords are supported in attach.conf:
***************
*** 47,53 ****
printed as each filesystem is attached or detached. If this option is
off, only error messages are printed.
.IP "debug (type boolean) (default: off)"
! If this option is on, then various debuging messages are printed as
the attach or detach operation proceeds. This is normally only of
interest to attach developers.
.IP "ownercheck (type boolean) (default: off)"
--- 47,53 ----
printed as each filesystem is attached or detached. If this option is
off, only error messages are printed.
.IP "debug (type boolean) (default: off)"
! If this option is on, then various debugging messages are printed as
the attach or detach operation proceeds. This is normally only of
interest to attach developers.
.IP "ownercheck (type boolean) (default: off)"
***************
*** 74,80 ****
mounted directory. If
.I nfs-root-hack
is on, then if the remotely mounted directory is the root (/), it is
! replaced by ``/root'' for the purposes of contructing the default
mount point.
.IP "nfs-mount-dir (type string) (default: /)"
This option affects the construction of the default mount point for
--- 74,80 ----
mounted directory. If
.I nfs-root-hack
is on, then if the remotely mounted directory is the root (/), it is
! replaced by ``/root'' for the purposes of constructing the default
mount point.
.IP "nfs-mount-dir (type string) (default: /)"
This option affects the construction of the default mount point for
***************
*** 92,102 ****
mtab to be in /etc, it is probably unwise to change the location of
this file.
.IP "aklog (type string)"
! (default: /afs/athena/mit/andrew/@sys/aklog)
This keyword specifies the location of the
.I aklog
! - program. It is used to authenticate the user to the AFS system.
.IP "fsck (type string) (default: /etc/fsck)"
This option specifies the location of
.IR fsck(8) ,
--- 92,102 ----
mtab to be in /etc, it is probably unwise to change the location of
this file.
.IP "aklog (type string)"
! (default: /bin/athena/aklog)
This keyword specifies the location of the
.I aklog
! program. It is used to authenticate the user to the AFS system.
.IP "fsck (type string) (default: /etc/fsck)"
This option specifies the location of
.IR fsck(8) ,
***************
*** 113,130 ****
(if ownercheck is enabled) and the ability to force a filesystem to be
mounted without the nosuid mount option.
.IP "nosetuid or nosuid (type regexp-list)"
! Filesystems which match the regular expresions listed as arguments are
mounted with the nosuid flag. This instructs the operating system to
disregard set-uid flags found on files in the mounted filesystem.
(See mount(8) for more information.)
.IP "setuid or suid (type regexp-list)"
! Filesystems which match the regular expresions listed as arguments are
mounted without the nosuid flag.
.IP "allow (type regexp-list)"
! Filesystems which match the regular expresions listed as arguments may
be mounted with attach.
.IP "noallow (type regexp-list)"
! Filesystems which match the regular expresions listed as arguments may
not be mounted with attach. This prohibition can be bypassed with the
-override (-O) flag, if the user is one of the ``trusted users.''
.IP "mountpoint (type regexp-list)"
--- 113,130 ----
(if ownercheck is enabled) and the ability to force a filesystem to be
mounted without the nosuid mount option.
.IP "nosetuid or nosuid (type regexp-list)"
! Filesystems which match the regular expressions listed as arguments are
mounted with the nosuid flag. This instructs the operating system to
disregard set-uid flags found on files in the mounted filesystem.
(See mount(8) for more information.)
.IP "setuid or suid (type regexp-list)"
! Filesystems which match the regular expressions listed as arguments are
mounted without the nosuid flag.
.IP "allow (type regexp-list)"
! Filesystems which match the regular expressions listed as arguments may
be mounted with attach.
.IP "noallow (type regexp-list)"
! Filesystems which match the regular expressions listed as arguments may
not be mounted with attach. This prohibition can be bypassed with the
-override (-O) flag, if the user is one of the ``trusted users.''
.IP "mountpoint (type regexp-list)"
***************
*** 137,148 ****
.IP "filesystem (type string-argument)"
This keyword allows the system administrator to give a filesystem
definition for a filesystem. Definitions in attach.conf take
! precedence over Hesiod(3) definitions..
.IP "options (type regexp-argument)"
! Filesystems which match the regular expresions listed as arguments are
mounted with the specified argument as a mount option. This is
particularly useful in forcing the NFS packet size to something which
! can be handled by local gateways. This can be done including the
following line in attach.conf:
.IP
options {nfs}:.* rsize=1024,wsize=1024
--- 137,148 ----
.IP "filesystem (type string-argument)"
This keyword allows the system administrator to give a filesystem
definition for a filesystem. Definitions in attach.conf take
! precedence over Hesiod(3) definitions.
.IP "options (type regexp-argument)"
! Filesystems which match the regular expressions listed as arguments are
mounted with the specified argument as a mount option. This is
particularly useful in forcing the NFS packet size to something which
! can be handled by local gateways. This can be done by including the
following line in attach.conf:
.IP
options {nfs}:.* rsize=1024,wsize=1024
***************
*** 152,158 ****
filesystem should be attached. These definitions can be found either
in attach.conf or by performing Hesiod(3) lookup. In general, the
definition consists of a filesystem type (NFS, RVD, UFS, etc.)
! followed by information specific to that fileststem type. Here are
some typical filesystem definitions, as would be found in
attach.conf (in Hesiod, the first two fields would be absent and the
definition would be keyed to a filesystem name):
--- 152,158 ----
filesystem should be attached. These definitions can be found either
in attach.conf or by performing Hesiod(3) lookup. In general, the
definition consists of a filesystem type (NFS, RVD, UFS, etc.)
! followed by information specific to that filesystem type. Here are
some typical filesystem definitions, as would be found in
attach.conf (in Hesiod, the first two fields would be absent and the
definition would be keyed to a filesystem name):
***************
*** 166,172 ****
filesystem games ERR Sorry, the games filesystem is not available
.fi
.PP
! The following are the supported filesystem types and the format a
filesystem definition for that type:
.IP NFS
.IP RVD
--- 166,172 ----
filesystem games ERR Sorry, the games filesystem is not available
.fi
.PP
! The following are the supported filesystem types and the format of a
filesystem definition for that type:
.IP NFS
.IP RVD
***************
*** 173,179 ****
.IP UFS
.IP AFS
.IP ERR
! .SH "EXTENSIONS TO REGEULAR EXPRESIONS"
Regular expressions in an attach.conf file can be prefixed by a
.IR type-delimiter ,
an optional string delimited by curly braces and followed a colon. If
--- 173,179 ----
.IP UFS
.IP AFS
.IP ERR
! .SH "EXTENSIONS TO REGULAR EXPRESSIONS"
Regular expressions in an attach.conf file can be prefixed by a
.IR type-delimiter ,
an optional string delimited by curly braces and followed a colon. If
***************
*** 195,204 ****
.I type-delimiter
may be further optionally prefixed with either a plus (+) or minus (-) sign.
If present, the plus sign indicates that the regular expression should
! be considered only if the filesystem was explicitly definied on the
command line. Likewise, the minus sign indicates that the regular
expression should be considered only if the filesystem was not
! explicitly definied.
.SH BUGS
.SH FILES
--- 195,204 ----
.I type-delimiter
may be further optionally prefixed with either a plus (+) or minus (-) sign.
If present, the plus sign indicates that the regular expression should
! be considered only if the filesystem was explicitly defined on the
command line. Likewise, the minus sign indicates that the regular
expression should be considered only if the filesystem was not
! explicitly defined.
.SH BUGS
.SH FILES
*** detach.1.old Fri Jun 5 12:39:57 1992
--- detach.1 Fri Jun 5 12:51:15 1992
***************
*** 55,61 ****
This is the default.
.IP "-force or -f"
Ordinarily, \fIdetach\fP will not attempt to detach a filesystem which
! it believes it thinks is being attached or detached by another
process. This flag overrides this behavior and \fIforces\fP the
filesystem to be detached. This option can be dangerous if used
indiscriminately.
--- 55,61 ----
This is the default.
.IP "-force or -f"
Ordinarily, \fIdetach\fP will not attempt to detach a filesystem which
! it believes is being attached or detached by another
process. This flag overrides this behavior and \fIforces\fP the
filesystem to be detached. This option can be dangerous if used
indiscriminately.
***************
*** 96,102 ****
Internal fatal error.
.TP 5
10
! Keberos failure.
.TP 5
11
Host communication failure.
--- 96,102 ----
Internal fatal error.
.TP 5
10
! Kerberos failure.
.TP 5
11
Host communication failure.
***************
*** 126,134 ****
the exit status 2 after attempting to detach 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
--- 126,134 ----
the exit status 2 after attempting to detach 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
***************
*** 141,147 ****
.SH "SEE ALSO"
! attach(1), nfsid(1), zinit(8), zephyr(1), hesiod(3)
.br
`Hesiod - Project Athena Technical Plan -- Name Service'
.br
--- 141,147 ----
.SH "SEE ALSO"
! attach(1), fsid(1), zinit(8), zephyr(1), hesiod(3)
.br
`Hesiod - Project Athena Technical Plan -- Name Service'
.br
*** fsid.1.old Fri Jun 5 12:57:30 1992
--- fsid.1 Fri Jun 5 12:56:56 1992
***************
*** 54,60 ****
.IP "-all or -a"
Perform the current mapping operation for all hosts associated with
filesystems in /usr/tmp/attachtab (see \fIattach(1)\fP). Note that a host
! may be referenced more than once if more than once filesystem is
located on that host.
.IP "-user \fIuser\fP or -U \fIuser\fP"
Perform the mapping on behalf of the specified user.
--- 54,60 ----
.IP "-all or -a"
Perform the current mapping operation for all hosts associated with
filesystems in /usr/tmp/attachtab (see \fIattach(1)\fP). Note that a host
! may be referenced more than once if more than one filesystem is
located on that host.
.IP "-user \fIuser\fP or -U \fIuser\fP"
Perform the mapping on behalf of the specified user.
***************
*** 99,105 ****
Internal fatal error.
.TP 5
10
! Keberos failure.
.TP 5
11
Host communication failure.
--- 99,105 ----
Internal fatal error.
.TP 5
10
! Kerberos failure.
.TP 5
11
Host communication failure.
Please describe any relevant documentation references:
attach(1), attach.conf(5), detach(1), fsid(1)
