[83] in testers
Re: attach: Badly formatted filesystem definition
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Fri Jul 14 05:11:31 1989
Date: Fri, 14 Jul 89 05:11:06 EDT
From: Theodore Ts'o <tytso@ATHENA.MIT.EDU>
To: Richard Basch <probe@ATHENA.MIT.EDU>
Cc: testers@ATHENA.MIT.EDU
In-Reply-To: Richard Basch's message of Fri, 14 Jul 89 04:24:38 -0400,
Reply-To: tytso@ATHENA.MIT.EDU
From: <probe@ATHENA.MIT.EDU>
Date: Fri, 14 Jul 89 04:24:38 -0400
Reply-To: Richard Basch <probe@ATHENA.MIT.EDU>
Address: 3 Ames Street Cambridge, MA 02139
Phone: (617) 225-6381
The following command seems to fail...
187% attach odie:site
Badly formatted filesystem definition
Operation aborted
Errr..... on odie, where I think you tried this....
% attach -d odie:site
odie:site resolves to:
xxx
Locking attachtab....Setting lock on /tmp/attach_odie:site: 5
Unlocking attachtab
Processing line xxx
Badly formatted filesystem definition
Operation aborted
Locking attachtab....Removing lock on /tmp/attach_odie:site
Unlocking attachtab
There is also one more thing I would like to add to the wish-list -- add
a "noexplicit" option to the configuration file to disallow -e
specifications. For instance, I can probably fool the system by using
an IP address or one of its many cnames...
Try this:
noallow {+}.*
or
noallow {+nfs,rvd}.*
which will disable explicit nfs and rvd attaches, but allow others.
Again, all will be explained in the (gradually coalescing) man pages.
- Ted
