mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ph. Marek" <philipp.marek@bmlv.gv.at>
To: linux-kernel@vger.kernel.org
Cc: phillips@istop.com
Subject: TUX2 filesystem
Date: Thu, 21 Jun 2007 07:05:34 +0200	[thread overview]
Message-ID: <200706210705.34702.philipp.marek@bmlv.gv.at> (raw)

Hello Daniel,
hello everbody else,


in Oct 2000 there's been some discussion "Tux2 - evil patents sighted" 
(http://www.ussg.iu.edu/hypermail/linux/kernel/0010.0/0343.html), and in Aug 
2002 (http://www.uwsg.iu.edu/hypermail/linux/kernel/0208.3/0332.html) Daniel 
wrote
> It's well down my list of priorities because of uncertainties due to
> the U.S. patent system. 
> Does anybody want to know if patent chill exists, and is it hurting
> open source? The answer is yes. 


With the recent Supreme Court decisions 
(http://www.groklaw.net/article.php?story=20070430121005424) and the fact 
that Daniel wrote that he did most of his work in *1989* (which is now 18 
years ago!) is there a chance for newer developments?


It seems to me that this kind of filesystem could solve a few problems that 
are currently attacked:
- Atomic snapshots. Make a new superblock, and mount this copy in another
  directory. As long as it's not overwritten, it stays consistent.
- Speed/Consistency for Flash media. There is a list of superblocks, and when
  the new block has been written the pointer from the old gets set - until the
  first block in the list gets re-written.

There may be some other nice things I didn't think about - but just having 
this filesystem for harddisks might be good, too.


Regards,

Phil

             reply	other threads:[~2007-06-21  5:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21  5:05 Ph. Marek [this message]
2007-06-21 17:57 ` James Bruce
2007-06-21 22:26   ` Zach Brown
2007-06-22  0:57     ` Bron Gondwana
2007-06-22  9:15   ` Jörn Engel

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=200706210705.34702.philipp.marek@bmlv.gv.at \
    --to=philipp.marek@bmlv.gv.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@istop.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

Powered by JetHome