linux-kernel - Re: Versioning file system

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 16 Jun 2007 16:39:26 -0400
From:	Jan Harkes <jaharkes@...cmu.edu>
To:	"Jeffrey V. Merkey" <jmerkey@...fmountaingroup.com>
Cc:	Jack Stone <jack@...keye.stone.uk.eu.org>,
	alan <alan@...eserver.org>, hpa@...or.com,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	akpm@...ux-foundation.org, viro@...iv.linux.org.uk
Subject: Re: Versioning file system

On Sat, Jun 16, 2007 at 02:03:49PM -0600, Jeffrey V. Merkey wrote:
> Jan Harkes wrote:
> >implementation, just a high level description. Finally advising anyone
> >(who is not an actual patent lawyer that could correctly interpret the
> >language and scope of a patent) to go search out patents seems pretty
> >bad advice. That can only result in not even attempting to research some
> >potentially new and innovative approach.
> >
> >Researching prior published work in the area is considerably more
> >helpful. Especially when something is complex beyond belief it has
> >probably attracted various researchers over time and there are most
> >likely various different solutions that have been explored previously.
> >Such existing work can form a good basis for further work.
>
> When you get into the recycling issues with storage, the patents come 
> into play. Also, using the file name to reference revisions is already 
> the subject of a patent previously filed (I no longer own the patent, I 
> sold them to Canopy). There is a third one about to be issued.

Congratulations on obtaining those patents, I hope they will be used
wisely. I am however not a patent lawyer and as such in no position to
evaluate their claims.

As a more useful response, the original poster may want to look at some
of the prior work in this area, I just picked a couple,

  (Cedar File System from Xerox PARC)
    A Caching File System for a Programmer's Workstation (1985)
    Michael D. Schroeder, David K. Gifford, Roger M. Needham

  (Vax/VMS System Software Handbook)
  (TOPS-20 User's Manual)

  (Plan 9 (file system))
    Plan 9 from Bell Labs (1990)
    Rob Pike, Dave Presotto, Sean Dorward, Bob Flandrena, Ken Thompson,
    Howard Trickey, Phil Winterbottom

  (Elephant File System)
    Elephant: The File System that Never Forgets (1999)
    Douglas J. Santry, Michael J. Feeley, Norman C. Hutchinson
    Workshop on Hot Topics in Operating Systems

    Deciding when to forget in the Elephant file system (1999)
    Douglas S. Santry, Michael J. Feeley, Norman C. Hutchinson,
    Alistair C. Veitch, Ross W. Carton, Jacob Otir

  (Ext3Cow)
    Ext3cow: The Design, Implementation, and Analysis of Metadata for a
    Time-Shifting File System (2003)
    Zachary N. J. Peterson, Randal C. Burns

Sites like portal.acm.org and citeseer.ist.psu.edu are good places to
find copies of these papers. They also provide links to other work that
either is cited by, or cites these papers which is a convenient way to
find other papers in this area.

Researching, designing and implementing such systems is a lot of fun,
admittedly often more fun than long term debugging and/or maintaining,
but that is life. Don't get too upset if the end result cannot be
included in the main kernel. Just start over from scratch, you may just
end up with an even better design the second time around.

Jan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/