From mboxrd@z Thu Jan 1 00:00:00 1970 From: "John Stoffel" Subject: Re: The argument for fs assistance in handling archives Date: Thu, 2 Sep 2004 10:35:10 -0400 Message-ID: <16695.12190.58678.877396@gargle.gargle.HOWL> References: <20040826150202.GE5733@mail.shareable.org> <4136E0B6.4000705@namesys.com> <1117111836.20040902115249@tnonline.net> <200409021327.22998.v13@priest.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <200409021327.22998.v13@priest.com> List-Id: Content-Type: text/plain; charset="us-ascii" To: V13 Cc: Spam , Hans Reiser , Linus Torvalds , David Masover , Jamie Lokier , Horst von Brand , Adrian Bunk , viro@parcelfarce.linux.theplanet.co.uk, Christoph Hellwig , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Alexander Lyamin aka FLX , ReiserFS List V13> I believe you mean something simillar to: V13> file1.txt;1 V13> file1.txt;2 V13> file1.txt;3 (yeap, it's VMS) Or TOPS-20, a precursor to VMS in some ways. It was a nice feature. V13> where you'll have to cleanup old versions when you don't need V13> them any more... AFAIK that this is older than HDDs It was usually an automatic cleanup past a certain point or if you went over disk quota. In any case, while I do like this feature, I'm not sure how we would cleanly implement this inside the unix namespace, or if inside a new namespace, how that new namespace would be joined with a standard Unix one. John