You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Karl Chen <qu...@eecs.berkeley.edu> on 2004/10/07 03:12:56 UTC
svnfs
Hi, I am thinking about writing a file system for Linux that
transparently use a Subversion repository or working copy. Since
this will do a lot of extra commits, I think the "Eric goes to
lunch"/svk distributed model will work well together when editing
source code. It will transparently add useful versioning to many
applications (without needing svk-type two-layer version control).
Comments/suggestions?
Example command-line usage:
% svnmount http://svn.quarl.org/repos/foo ~/foo
% cd ~/foo
% diff -u main.C main.C@123 # like 'svn diff -r 123 main.C'
% mv a.py b.py # like 'svn mv a.py b.py'
Issues:
- whether to automatically commit each action; this could be a
run-time per-WC option
- whether to automatically add or ignore a new file? e.g., object
and temporary files should be ignored. Will the svn:ignore
feature be good enough to handle this?
- is it easy to arrange for 'cp a b' to be 'svn cp a b', if cp is
implemented as 'cat a > b'?
- how to support normal svn clients; perhaps instead of the mount
above use:
svn co http://svn.quarl.org/repos/foo ~/foo-wc
svnmount ~/foo-wc ~/foo
Without the intermediate WC, svnfs would have to operate in
automatic-commit mode.
For example, I have my /etc stored in a Subversion repository.
But often this WC is manipulated by scripts that create, move,
delete files, and I have to manually tell svn that and also
commit; I would rather just have it be automatically versioned.
--
Karl 2004-10-06 19:48
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svnfs
Posted by Ben Collins-Sussman <su...@collab.net>.
On Oct 8, 2004, at 3:19 AM, Timothee Besset wrote:
> You should have a look at YAM. I completed basic SVNFS read capability
> yesterday. (Using FUSE for the userland filesystem frontend, and the
> python bindings as the repository access backend).
>
Is it really possible to implement a real fs, if libsvn_fs/libsvn_repos
have no concept of locking yet?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svnfs
Posted by Timothee Besset <tt...@idsoftware.com>.
You should have a look at YAM. I completed basic SVNFS read capability
yesterday. (Using FUSE for the userland filesystem frontend, and the
python bindings as the repository access backend).
See
http://zerowing.idsoftware.com/yam/
http://zerowing.idsoftware.com/yam/YAM_200_2e1_2e2_20Design
Note that we are *always* looking for developers, contributors, etc.
TTimo
On Wed, 06 Oct 2004 20:12:56 -0700
Karl Chen <qu...@eecs.berkeley.edu> wrote:
>
> Hi, I am thinking about writing a file system for Linux that
> transparently use a Subversion repository or working copy. Since
> this will do a lot of extra commits, I think the "Eric goes to
> lunch"/svk distributed model will work well together when editing
> source code. It will transparently add useful versioning to many
> applications (without needing svk-type two-layer version control).
>
> Comments/suggestions?
>
> Example command-line usage:
>
> % svnmount http://svn.quarl.org/repos/foo ~/foo
> % cd ~/foo
> % diff -u main.C main.C@123 # like 'svn diff -r 123 main.C'
> % mv a.py b.py # like 'svn mv a.py b.py'
>
> Issues:
>
> - whether to automatically commit each action; this could be a
> run-time per-WC option
>
> - whether to automatically add or ignore a new file? e.g., object
> and temporary files should be ignored. Will the svn:ignore
> feature be good enough to handle this?
>
> - is it easy to arrange for 'cp a b' to be 'svn cp a b', if cp is
> implemented as 'cat a > b'?
>
> - how to support normal svn clients; perhaps instead of the mount
> above use:
>
> svn co http://svn.quarl.org/repos/foo ~/foo-wc
> svnmount ~/foo-wc ~/foo
>
> Without the intermediate WC, svnfs would have to operate in
> automatic-commit mode.
>
> For example, I have my /etc stored in a Subversion repository.
> But often this WC is manipulated by scripts that create, move,
> delete files, and I have to manually tell svn that and also
> commit; I would rather just have it be automatically versioned.
>
>
>
>
>
> --
> Karl 2004-10-06 19:48
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svnfs
Posted by Hans Reiser <re...@namesys.com>.
solo turn wrote:
>hallo hans,
>
>i think i read once something that you wrote towards version control,
>but i cannot find it again.
>
>given the possibilities of reiser4, where would you put which
>functionality to have good version control?
>
>-solo.
>
>
>On Fri, 8 Oct 2004 15:53:17 -0400, Bryan Donlan <bd...@gmail.com> wrote:
>
>
>>On Fri, 08 Oct 2004 11:18:35 -0700, Paul Querna <chip@force-elite.com > wrote:
>>
>>
>>>Archie Cobbs wrote:
>>>
>>>
>>>>>% diff -u main.C main.C@123 # like 'svn diff -r 123 main.C'
>>>>>
>>>>>
>>>>This implies every revision foo@NNN appears in the directory.. ?
>>>>Might get crowded... maybe put them in a .revisions subdirectory?
>>>>
>>>>Where do properties appear? You could create a ".properties" subdirectory.
>>>>
>>>>
>>>See Reiser 4. Files are directories.
>>>
>>>eg: diff -u main.C main.C/r/123
>>>
>>>Or to access properties
>>>
>>>cat main.C/p/svn-eolstyle
>>>echo "foobar" > main.C/p/my-property
>>>
>>>It seems that it would be best to follow that model, since a major
>>>filesystem is already going that route.
>>>
>>>
>>How do you access properties or revisions of directories?
>>--
>>bd
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>>For additional commands, e-mail: dev-help@subversion.tigris.org
>>
>>
>>
>>
>
>
>
>
see www.namesys.com/blackbox_security.html. It is the first step towards
the infrastructure needed for version control.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svnfs
Posted by solo turn <so...@gmail.com>.
hallo hans,
i think i read once something that you wrote towards version control,
but i cannot find it again.
given the possibilities of reiser4, where would you put which
functionality to have good version control?
-solo.
On Fri, 8 Oct 2004 15:53:17 -0400, Bryan Donlan <bd...@gmail.com> wrote:
> On Fri, 08 Oct 2004 11:18:35 -0700, Paul Querna <chip@force-elite.com > wrote:
> > Archie Cobbs wrote:
> > >>% diff -u main.C main.C@123 # like 'svn diff -r 123 main.C'
> > >
> > >
> > > This implies every revision foo@NNN appears in the directory.. ?
> > > Might get crowded... maybe put them in a .revisions subdirectory?
> > >
> > > Where do properties appear? You could create a ".properties" subdirectory.
> >
> >
> > See Reiser 4. Files are directories.
> >
> > eg: diff -u main.C main.C/r/123
> >
> > Or to access properties
> >
> > cat main.C/p/svn-eolstyle
> > echo "foobar" > main.C/p/my-property
> >
> > It seems that it would be best to follow that model, since a major
> > filesystem is already going that route.
>
> How do you access properties or revisions of directories?
> --
> bd
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svnfs
Posted by Bryan Donlan <bd...@gmail.com>.
On Fri, 08 Oct 2004 11:18:35 -0700, Paul Querna <ch...@force-elite.com> wrote:
> Archie Cobbs wrote:
> >>% diff -u main.C main.C@123 # like 'svn diff -r 123 main.C'
> >
> >
> > This implies every revision foo@NNN appears in the directory.. ?
> > Might get crowded... maybe put them in a .revisions subdirectory?
> >
> > Where do properties appear? You could create a ".properties" subdirectory.
>
>
> See Reiser 4. Files are directories.
>
> eg: diff -u main.C main.C/r/123
>
> Or to access properties
>
> cat main.C/p/svn-eolstyle
> echo "foobar" > main.C/p/my-property
>
> It seems that it would be best to follow that model, since a major
> filesystem is already going that route.
How do you access properties or revisions of directories?
--
bd
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svnfs
Posted by Paul Querna <ch...@force-elite.com>.
Archie Cobbs wrote:
>>% diff -u main.C main.C@123 # like 'svn diff -r 123 main.C'
>
>
> This implies every revision foo@NNN appears in the directory.. ?
> Might get crowded... maybe put them in a .revisions subdirectory?
>
> Where do properties appear? You could create a ".properties" subdirectory.
See Reiser 4. Files are directories.
eg: diff -u main.C main.C/r/123
Or to access properties
cat main.C/p/svn-eolstyle
echo "foobar" > main.C/p/my-property
It seems that it would be best to follow that model, since a major
filesystem is already going that route.
-Paul Querna
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svnfs
Posted by Archie Cobbs <ar...@dellroad.org>.
Karl Chen wrote:
> Hi, I am thinking about writing a file system for Linux that
> transparently use a Subversion repository or working copy. Since
> this will do a lot of extra commits, I think the "Eric goes to
> lunch"/svk distributed model will work well together when editing
> source code. It will transparently add useful versioning to many
> applications (without needing svk-type two-layer version control).
>
> Comments/suggestions?
Crazy^H^H^H^H^HInteresting idea!
> % diff -u main.C main.C@123 # like 'svn diff -r 123 main.C'
This implies every revision foo@NNN appears in the directory.. ?
Might get crowded... maybe put them in a .revisions subdirectory?
Where do properties appear? You could create a ".properties" subdirectory.
> - whether to automatically commit each action; this could be a
> run-time per-WC option
>
> - whether to automatically add or ignore a new file? e.g., object
> and temporary files should be ignored. Will the svn:ignore
> feature be good enough to handle this?
You could commit whenever there were no longer any open files
in the directory (this could take arbitrarily long to happen).
You could also just commit every N seconds.
How would you handle hard links? Ownership? Permissions? Locking?
Special files? You'd need to store some meta-information in the
repository for stuff like that.. perhaps in special svnfs: properties.
> - is it easy to arrange for 'cp a b' to be 'svn cp a b', if cp is
> implemented as 'cat a > b'?
You could hash the contents of each file present in a directory.
This would allow you to detect copies.
More generally, keep all files in a suffix tree or whatever, and
new files would be auto-correlated with the nearest existing file
revision that was close enough to be heuristically determined to
be an ancestor.
> - how to support normal svn clients; perhaps instead of the mount
> above use:
>
> svn co http://svn.quarl.org/repos/foo ~/foo-wc
> svnmount ~/foo-wc ~/foo
>
> Without the intermediate WC, svnfs would have to operate in
> automatic-commit mode.
>
> For example, I have my /etc stored in a Subversion repository.
> But often this WC is manipulated by scripts that create, move,
> delete files, and I have to manually tell svn that and also
> commit; I would rather just have it be automatically versioned.
This might actually be a more useful idea. svnfs would be a file
system "layer". It would convert e.g. "mv x y" into "svn mv x y",
"cp a b" into "svn cp a b", etc. Underneath, it would just be
manipulating a WC. When you're done, unmount the file system and
commit (or use some special svnfs-specific command).
On the other hand, this doesn't have to be implemented as a file
system. You could simply have a daemon that did periodic "snapshots"
of some directory hierarchy and committed them automatically. This
would be useful for backing up /etc .. e.g., have a snapshot taken
and commited to the repository at 3am every night.
-Archie
__________________________________________________________________________
Archie Cobbs * CTO, Awarix * http://www.awarix.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org