[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: subversion filesystem

From: Greg Stein <gstein_at_lyra.org>
Date: 2004-03-05 22:56:57 CET

On Thu, Mar 04, 2004 at 10:37:08AM -0500, Greg Hudson wrote:
> On Thu, 2004-03-04 at 08:05, Walter White wrote:
> > Hi All,
> >
> > I was thinking about how subversion or any RCS could be improved. If
> > subversion implemented a filesystem or daemon that can be configured to run
> > on a directory or filesystem only
>
> We sort of have that, because a Subversion repository can be mounted as
> a DAV filesystem on most operating systems. Take a look at
> http://svnbook.red-bean.com/book.html#svn-ap-c (maybe there's a better
> source of information about this, but it mostly seems to be there).

Yup. It would also be possible to follow a format similar to the DAVFS2
project (dav.sf.net). That project uses an operating system's CODA
filesystem, which is implemented (mostly) by a user-space daemon. The
daemon can be replaced to do the filesystem operations against other
sources. In the DAVFS2 case, it uses Neon to talk to a DAV server, which
allows you to mount a DAV server under Linux or Solaris (or other OSes
with CODA support).

In this particular case, you can write a new daemon that binds against
libsvn_repos and/or libsvn_fs (which stores files in a local repository).

The writing of a CODA-based deamon can be simplified through the uservfs
project (see uservfs.sf.net). There is another, similar system for Linux
called FUSD (http://www.circlemud.org/~jelson/software/fusd/)

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 5 22:54:04 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.