linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Karlsson <andreas@proxel.se>
To: Christian Stroetmann <stroetmann@ontolinux.com>
Cc: Pavel Machek <pavel@ucw.cz>,
	Linux FS Devel <linux-fsdevel@vger.kernel.org>,
	Tux3 <tux3@tux3.org>,
	Daniel Phillips <daniel.raymond.phillips@gmail.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Tux3 Report: Meet Shardmap, the designated successor of HTree
Date: Mon, 24 Jun 2013 17:39:03 +0200	[thread overview]
Message-ID: <51C86817.6030304@proxel.se> (raw)
In-Reply-To: <51C862CC.1010606@ontolinux.com>

Hi,

I assume it is serious since ideas cannot be copyrighted in most (or 
maybe even all) countries.

 From the FAQ of the U.S. Copyright Office [1]:

"Copyright does not protect facts, ideas, systems, or methods of 
operation, although it may protect the way these things are expressed."

"How do I protect my idea?

Copyright does not protect ideas, concepts, systems, or methods of doing 
something. You may express your ideas in writing or drawings and claim 
copyright in your description, but be aware that copyright will not 
protect the idea itself as revealed in your written or artistic work."

Andreas

[1] http://www.copyright.gov/help/faq/faq-protect.html#what_protect

On 06/24/2013 05:16 PM, Christian Stroetmann wrote:
> Dear Mr. Pavel Machek:
>
> Is this a serious comment?
> Nevertheless, this is a copyrighted idea [1].
>
>
> Sincerely
> Christian Stroetmann
>
> [1] Log-Structured Hash-based File System (LogHashFS or LHFS;
> www.ontonics.com/innovation/pipeline.htm#loghashfs)
>
>> Hi!
>>
>>> At first you came up with a file system that can handle a great
>>> many/billions files and has ACID feature, which are both features of
>>> my Ontologic File System (OntoFS; see [1]). Both were said to be a
>>> no-go at that time (around 2007 and 2008).
>>> Then you came up, with my concept of a log-structured hashing based
>>> file system [2] and [3], presented it as your invention yesterday
>>> [4], and even integrated it with your Tux3 file system that already
>>> has or should have the said features of my OntoFS. I only waited for
>>> this step by somebody strongly connected with the company Samsung
>>> since the October 2012. AIso, I do think that both steps are very
>>> clear signs that shows what is going on behind the curtain.
>>> And now your are so bold and please me that I should credit these
>>> ideas in the sense of crediting your ideas. For sure, I always do
>>> claim for copyright of my ideas, and the true question is if you are
>>> allowed to implement them at all. In this conjunction, I would give
>> Fortunately, you can't copyright ideas. Chuck Norris managed to do it
>> once, but you can't.
>>
>> Pavel
>
>
>
> _______________________________________________
> Tux3 mailing list
> Tux3@phunq.net
> http://phunq.net/mailman/listinfo/tux3


-- 
Andreas Karlsson

  reply	other threads:[~2013-06-24 15:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 17:02 Tux3 Report: Meet Shardmap, the designated successor of HTree Daniel Phillips
2013-06-20 19:11 ` Christian Stroetmann
2013-06-20 20:27   ` Daniel Phillips
2015-04-15 18:00     ` Christian Stroetmann
2013-06-24 14:18   ` Pavel Machek
2013-06-24 15:16     ` Christian Stroetmann
2013-06-24 15:39       ` Andreas Karlsson [this message]
2013-06-24 17:19         ` Christian Stroetmann
2013-06-24 18:20           ` richard -rw- weinberger
2013-06-25  0:34             ` Christian Stroetmann
2013-06-25  0:15               ` David Lang
  -- strict thread matches above, loose matches on Subject: below --
2013-06-19  2:31 Daniel Phillips
2013-06-19 18:17 ` Christian Stroetmann

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=51C86817.6030304@proxel.se \
    --to=andreas@proxel.se \
    --cc=daniel.raymond.phillips@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=stroetmann@ontolinux.com \
    --cc=tux3@tux3.org \
    /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;
as well as URLs for NNTP newsgroup(s).