public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Milind Dumbare <milind@linsyssoft.com>
Cc: linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: CheckFS: Checkpoints and Block Level Incremental Backup (BLIB)
Date: Fri, 22 Jul 2005 15:54:26 -0400	[thread overview]
Message-ID: <20050722195423.GA6851@thunk.org> (raw)
In-Reply-To: <1122041079.3556.18.camel@matrix.linsyssoft.com>

On Fri, Jul 22, 2005 at 07:34:38PM +0530, Milind Dumbare wrote:
> Hi,
> 
> 	LinSysSoft Technologies  has taken up the challenge to incorporate
> Checkpoint and Block Level Incremental Backup (BLIB) support in the open
> source's Ext3 File System, which is very well known for its stability,
> to create a new file system called CheckFS. Block Level Incremental
> Backup enables truly efficient backup and restore mechanisms.
> Checkpoints provide administrators to create point-in-time copies of a
> live file system by keeping track of the data blocks modified in real
> time. 
> 
> For further information and a downloadable working prototype of this
> technology go to : http://checkfs.linsyssoft.com

This looks like very interesting technology, but out of curiosity, why
did you develop this as separate filesystem with a new filesystem
name, and doing a global search-and-replace of "ext3" with "checkfs"
in the source files, instead of simply just modifying ext3 and posting
diffs?  Especially since that the apparent intention is to keep ext3
compatibility using the same ext3 magic numbers, data formats, and
user-mode utilities.

I'll reserve the superblock fields and compatibility bitmap fields
used by your code in e2fsprogs to help avoid the possibility of other
folks working on ext3 extensions from colliding with the codepoints
which you "borrowed", but in the future, it would be good if people
contact me in advance so I ensure that there are no collisions with
other development groups.

What version of the source base did you originally fork checkfs from?
That way we can do a "s/checkfs/ext3/g" search and replace and then
generate some diffs to see what you changed, or alternatively, it
would be even better if you minimized differences between your version
and mainline and generated the diffs yourself.

Thanks, regards, 

						- Ted


  reply	other threads:[~2005-07-22 19:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-22 14:04 CheckFS: Checkpoints and Block Level Incremental Backup (BLIB) Milind Dumbare
2005-07-22 19:54 ` Theodore Ts'o [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-23  6:00 Amit S. Kale
2005-07-23 15:25 ` Theodore Ts'o
2005-07-24 14:23 ` Pavel Machek
2005-07-24 15:14   ` Jan Engelhardt
2005-07-25  5:54     ` Amit S. Kale
2005-07-25 12:32       ` Theodore Ts'o
2005-07-25 12:52         ` Amit S. Kale
2005-08-01  7:50 Milind Dumbare
2005-08-01 10:08 ` Theodore Ts'o
2005-08-02  7:05   ` Milind Dumbare

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050722195423.GA6851@thunk.org \
    --to=tytso@mit.edu \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=milind@linsyssoft.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox