Date: Thu, 25 Jun 2009 00:33:23 +0200 From: Polytropon <freebsd@edvax.de> To: cpghost <cpghost@cordula.ws> Cc: Roland Smith <rsmith@xs4all.nl>, freebsd-questions@freebsd.org Subject: Re: Versioning File System for FreeBSD? Message-ID: <20090625003323.cd7021a3.freebsd@edvax.de> In-Reply-To: <20090624215734.GA3720@phenom.cordula.ws> References: <20090624150422.GA2307@phenom.cordula.ws> <20090624163755.GA71757@slackbox.xs4all.nl> <20090624175918.GA2948@phenom.cordula.ws> <20090624191125.GA75991@slackbox.xs4all.nl> <20090624215734.GA3720@phenom.cordula.ws>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 24 Jun 2009 23:57:34 +0200, cpghost <cpghost@cordula.ws> wrote: > Yep, you're right. I thought about a way to extend the API in a > backwards compatible way, but that's not as easy or straight > forward as it seems. In fact, it opens a whole can of worms. > > If the versioned file system isn't also POSIX compatible (where > everything happens in HEAD unless specified otherwise), it's > practically useless. The question is: Do you want to take versioning support into the file system intendedly? FreeBSD keeps most things on a per-file basis (ordinary files, devices, processes etc.). Versioning can always be added as a separate solution (using versioning systems as separate programs) that does not make any assumptions on the file system used. As you concluded, the file system's complexity would of course grow with those requirements. In addition to your arguments, just imagine how a fsck for such a file system would have to be implemented... -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090625003323.cd7021a3.freebsd>