Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site drivax.UUCP Path: utzoo!watmath!clyde!cbosgd!ihnp4!zehntel!hplabs!amdahl!drivax!steve From: steve@drivax.UUCP (Steve Williams) Newsgroups: net.eunice Subject: Re: mkdir refuses to Message-ID: <61@drivax.UUCP> Date: Fri, 7-Dec-84 01:47:55 EST Article-I.D.: drivax.61 Posted: Fri Dec 7 01:47:55 1984 Date-Received: Mon, 10-Dec-84 01:43:58 EST References: <1504@sdcrdcf.UUCP> Organization: Digital Research, Monterey, CA Lines: 23 > 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