lwall@sdcrdcf.UUCP (Larry Wall) (11/28/84)
Anybody got any bright ideas why /bin/mkdir.exe would suddenly stop working?
CREATE/DIR still works fine. I've wracked my brain, run strings on it
(mkdir, not my brain), checked all kinds of protection codes, and still can't
come up with anything. Nothing peculiar about the name of the directory.
Doesn't matter if I'm priveledged or not. Doesn't matter if I fully qualify
the name of the directory. It isn't aliased in any way.
/bin/mkdir.exe foo
mkdir: cannot create foo/
or some such message. I've seen it happen on two different Eunice machines
now. I've got a mkdir shell script to work around it, but it's SLOW.
Somebody help the poor boy!
Larry Wall
{allegra,burdvax,cbosgd,hplabs,ihnp4,sdcsvax}!sdcrdcf!lwallperolov@lth.UUCP (Per-Olov Nilsson) (12/03/84)
mkdir also suddenly stopped working at our site,
it was around Nov 12-14.
We have set EUNICE_FULL_FILENAMES = 4 and
EUNICE_1VERSION ON. The strange thing is that
on another site also running Eunice with the same
setting it still works fine.
Also in desperate need for help.
Per-Olov Nilsson
{seismo,decvax,philabs}!mcvax!enea!lth!perolovsteve@drivax.UUCP (Steve Williams) (12/07/84)
> Anybody got any bright ideas why /bin/mkdir.exe would suddenly stop working? > CREATE/DIR still works fine. I've wracked my brain, run strings on it > (mkdir, not my brain), checked all kinds of protection codes, and still can't > come up with anything. Nothing peculiar about the name of the directory. > Doesn't matter if I'm priveledged or not. Doesn't matter if I fully qualify > the name of the directory. It isn't aliased in any way. > > /bin/mkdir.exe foo > mkdir: cannot create foo/ > > or some such message. I've seen it happen on two different Eunice machines > now. I've got a mkdir shell script to work around it, but it's SLOW. > Somebody help the poor boy! > *** REPLACE THIS LINE WITH YOUR MESSAGE *** You didn't say which version of Eunice or VMS you have. We had a similar problem with Eunice 3.1 with VMS 3.5. If you set the protection for the [000000] (root) directory on a volume to prohibit read access, then Eunice couldn't create directories anymore. The problem is fixed in Eunice 3.2. -Steve Williams {ihnp4,mot,ucscc,amdahl}!drivax!steve
jdd@wucs.UUCP (John DeHart) (12/10/84)
> mkdir also suddenly stopped working at our site, > it was around Nov 12-14. > We have set EUNICE_FULL_FILENAMES = 4 and > EUNICE_1VERSION ON. The strange thing is that > on another site also running Eunice with the same > setting it still works fine. > > Also in desperate need for help. > > Per-Olov Nilsson > {seismo,decvax,philabs}!mcvax!enea!lth!perolov We had a lot of trouble installing the IP/TCP software on EUNICE 3.2 because we had EUNICE_FULL_FILENAMES set to 4. The TWG support people told us that having EUNICE_FULL_FILENAMES set to anything caused problems in Eunice 3.2. We do not have it defined now and IP/TCP works fine. mkdir also works fine. These problems with EUNICE_FULL_FILENAMES are supposed to be fixed in the next release. John DeHart (314)-889-6160 Box 1045 Washington Univ. ..!ihnp4!wucs!jdd St. Louis Mo. 63130 USA -- --- John D. DeHart ..ihnp4!wucs!jdd Box 1045 Washington Univ. (314) 889-6160 St. Louis Mo. 63130 USA