Messages in this thread | | | From | Steven Cole <> | Subject | Re: linux-2.5.4-pre1 - bitkeeper testing | Date | Mon, 11 Mar 2002 14:33:55 -0700 |
| |
On Monday 11 March 2002 12:15 pm, Hans Reiser wrote: > Steven Cole wrote: > >I fiddled around a bit with VMS, and it looks like the following command > > set things up for me so that I only have one version for any new files I > > create: > > > >SET DIRECTORY/VERSION_LIMIT=1 SYS$SYSDEVICE:[USERS.STEVEN] > > > >This change was persistant across logins. Hope this helps. > > > >Steven > > This affects all directories and all files for user steven, or just one > directory?
The above example affected all subsequently created files and subsequently created directories under user steven, such as DKA300:[USERS.STEVEN.TESTTHIS]. Previously created directories retain their previous version_limit setting, which I checked in DKA300:[USERS.STEVEN.HELLOWORLD]. Previously created files also retain their previous version_limit setting.
I also set the version_limit for the whole disk (as SYSTEM) with SET DIRECTORY/VERSION_LIMIT=1 DKA300:[000000], but again this only affected subsequently created files and directories along with the files they contain.
I have not figured out how to set the version_limit retroactively; perhaps it is not possible with a simple command. Obviously, you could do this with a DCL script if you really wanted to.
Steven - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |