Messages in this thread | | | From | Steven Cole <> | Subject | Re: linux-2.5.4-pre1 - bitkeeper testing | Date | Mon, 11 Mar 2002 15:19:52 -0700 |
| |
On Monday 11 March 2002 02:54 pm, Richard B. Johnson wrote: > On Mon, 11 Mar 2002, Steven Cole wrote: > > 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: > > [SNIPPED] > > > 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 > > - > > $ SET PROC/PRIV=ALL > $ SET DEF DISK:[000000] > $ PURGE > $ RENAME *.* ;1 > > > Cheers, > Dick Johnson
Sure, that cleans up everything and sets all the version numbers back to ;1, but what I was pointing out is that previously created directories and previously created files retain whatever version_limit setting they were created with. After running your four lines, the disk is cleaner, but you'll still get multiple versions even if you don't want multiple versions for those previously created directories and files. I know, I just tried it with VMS 5.5-2. But this is all rather moot, since the real topic at hand is not what VMS does or didn't do in the past, but rather what we _might_ want certain linux filesystems to do (and not do) in the future.
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/
| |