In the linux world, I posted that I've got a student working on it...
There's also NILFS <http://www.nilfs.org>, version 2 recently accepted
into Linux kernel 2.6.30. Not exactly file versions, but regular
snapshotting of the filesystem with independent access to any snapshot.
--
Alec Kojaev
St.Petersburg, Russia [30E18 59N56]
Too bad there still isn't something like VMS. I'm starting to do some
development on Linux, and I'd live the simplicity of SET/FILE/VERSION=
for just the sources. I don't want to add RCS/CVS/whatever to the stuff
I'm learning to use.
Interesting, but it sounds like another flavor of CVS and, being IBM, a
more complicated flavor.
I know that OpenVMS handles file versions quite nicely.
John Savard
Well, Clearcase is something IBM bought rather than built but yes, it is a more complicated equivalent
of CVS. But yes part of the added complication is that it does manage to present it's tree as a virtual file
system that (at least on Solaris, which is the only platform I've used it) does present itself to
users as just a file system.
--
--------
Sarr Blumson sarr.b...@alum.dartmouth.org
http://www-personal.umich.edu/~sarr/
we had developed our own source management system in CMS. It was used
for virtual machine related projects.
clear was used for os360 lineage ... although some number of those
products did majority of their stuff (using cms tools) and then were
forced to morph them into proscribed tools (JES was major example for a
long time).
this became less of a concern to customers after OCO-wars in the early
80s, where company stopped shipping source.
an old folklore from the period was a sensitive gov. agency asked the
corporation for the "exact" source corresponding to running MVS
product. supposedly there was a $5m investigation that eventually
concluded that it wasn't feasible or practical (this was when virtual
machine customers were still getting source and building their running
systems from the shipped source).
past posts mentioning cms-based source management
http://www.garlic.com/~lynn/2001e.html#57 line length (was Re: Babble from "JD" <dy...@jdyson.com>)
http://www.garlic.com/~lynn/2003.html#58 Card Columns
http://www.garlic.com/~lynn/2003k.html#47 Slashdot: O'Reilly On The Importance Of The Mainframe Heritage
http://www.garlic.com/~lynn/2004o.html#36 Integer types for 128-bit addressing
http://www.garlic.com/~lynn/2005i.html#30 Status of Software Reuse?
http://www.garlic.com/~lynn/2005p.html#45 HASP/ASP JES/JES2/JES3
http://www.garlic.com/~lynn/2006f.html#5 3380-3390 Conversion - DISAPPOINTMENT
http://www.garlic.com/~lynn/2006f.html#38 Over my head in a JES exit
http://www.garlic.com/~lynn/2006n.html#45 sorting
http://www.garlic.com/~lynn/2006o.html#14 SEQUENCE NUMBERS
http://www.garlic.com/~lynn/2006o.html#19 Source maintenance was Re: SEQUENCE NUMBERS
http://www.garlic.com/~lynn/2006o.html#21 Source maintenance was Re: SEQUENCE NUMBERS
http://www.garlic.com/~lynn/2006o.html#34 Source maintenance was Re: SEQUENCE NUMBERS
http://www.garlic.com/~lynn/2006u.html#26 Assembler question
http://www.garlic.com/~lynn/2006w.html#42 vmshare
http://www.garlic.com/~lynn/2007f.html#12 FBA rant
http://www.garlic.com/~lynn/2007m.html#11 John W. Backus, 82, Fortran developer, dies
http://www.garlic.com/~lynn/2007m.html#15 Patents, Copyrights, Profits, Flex and Hercules
http://www.garlic.com/~lynn/2007n.html#3 Is Parallel Programming Just Too Hard?
http://www.garlic.com/~lynn/2007n.html#32 What I miss in my OS
http://www.garlic.com/~lynn/2008q.html#52 TOPS-10
http://www.garlic.com/~lynn/2009h.html#48 Book on Poughkeepsie
http://www.garlic.com/~lynn/2009i.html#36 SEs & History Lessons
--
40+yrs virtualization experience (since Jan68), online at home since Mar1970
"Proscribed" means "prohibited." "Prescribed" is closer to the word you
want.
Louis
As does TOPS-20 and its ancestor TENEX. VMS simply followed its ancestor
RSX-11M.
--
Rich Alderson "You get what anybody gets. You get a lifetime."
ne...@alderson.users.panix.com --Death, of the Endless
> Quadibloc <jsa...@ecn.ab.ca> writes:
>
>> On Jun 15, 3:49=A0pm, Peter Flass <Peter_Fl...@Yahoo.com> wrote:
>
>>> A few days ago someone posted the name of a filesystem that handles file
>>> versions. I just spent 1/2 hour with Google today, and I'll be darned
>>> if I could find the post. Could I impose on you to repost the name? Thanks.
>
>> I know that OpenVMS handles file versions quite nicely.
>
> As does TOPS-20 and its ancestor TENEX. VMS simply followed its ancestor
> RSX-11M.
And TENEX got it from ITS
> Rich Alderson <ne...@alderson.users.panix.com> writes:
>> Quadibloc <jsa...@ecn.ab.ca> writes:
Good point. Was it original to ITS, or did someone somewhere publish a paper
that the ITS developers for certain read? There's always the possibility of
parallel developments, of course.
> cst...@news.dtpq.com (Christopher C. Stacy) writes:
>
>> Rich Alderson <ne...@alderson.users.panix.com> writes:
>
>>> Quadibloc <jsa...@ecn.ab.ca> writes:
>
>>>> On Jun 15, 3:49=A0pm, Peter Flass <Peter_Fl...@Yahoo.com> wrote:
>
>>>>> A few days ago someone posted the name of a filesystem that handles file
>>>>> versions. I just spent 1/2 hour with Google today, and I'll be darned
>>>>> if I could find the post. Could I impose on you to repost the name? Thanks.
>
>>>> I know that OpenVMS handles file versions quite nicely.
>
>>> As does TOPS-20 and its ancestor TENEX. VMS simply followed its ancestor
>>> RSX-11M.
>
>> And TENEX got it from ITS
>
> Good point. Was it original to ITS, or did someone somewhere publish a paper
> that the ITS developers for certain read? There's always the possibility of
> parallel developments, of course.
I think it was original on ITS; not sure which individual was responsible for it.
It was before my time, but I believe the filesystem that they were looking at was CTSS.
> cst...@news.dtpq.com (Christopher C. Stacy) writes:
>
>> Rich Alderson <ne...@alderson.users.panix.com> writes:
>
>>> Quadibloc <jsa...@ecn.ab.ca> writes:
>
>>>> On Jun 15, 3:49=A0pm, Peter Flass <Peter_Fl...@Yahoo.com> wrote:
>
>>>>> A few days ago someone posted the name of a filesystem that handles file
>>>>> versions. I just spent 1/2 hour with Google today, and I'll be darned
>>>>> if I could find the post. Could I impose on you to repost the name? Thanks.
>
>>>> I know that OpenVMS handles file versions quite nicely.
>
>>> As does TOPS-20 and its ancestor TENEX. VMS simply followed its ancestor
>>> RSX-11M.
>
>> And TENEX got it from ITS
>
> Good point.
Oh, and after TENEX gave it to TOPS-20 (well, and VMS), the Lisp Machine
picked it up for its native file system(s). (The Symbolics file system
also picked up "generation retention count", which ITS did not have.)
On an unrelated note (file system versions were a filesystem/kernel thing),
the Lisp Machine also took the TOPS-20 command line prompting/processing ideas
to a new level. The LispM took a number of ideas from ITS, TENEX/TOPS-20,
Multics, and other places. This happened not because of publications,
but because the team was composed of people who were familiar with all
those systems (as both users and often as developers).
That (developers familiar with other OS features) is how a lot of
things got implemented on other systems. It's why DEC OSes
look similar (except for the one that NIH syndrome for its first
5 years).
/BAH