From: Hans Reiser <reiser@namesys.com>
To: "Markus Törnqvist" <mjt@nysv.org>, reiserfs-list@namesys.com
Cc: flx@namesys.com
Subject: Re: On a free repacker
Date: Thu, 20 May 2004 10:28:13 -0700 [thread overview]
Message-ID: <200405201028.13184.reiser@namesys.com> (raw)
In-Reply-To: <20040519192831.GL24604@nysv.org>
flx, please create the donations acceptance wording for our website.
Hans
On Wednesday 19 May 2004 12:28, Markus Törnqvist wrote:
> Hi
>
> There was an IRC discussion earlier today, a short one, about the repacker.
>
> It appears that Reiser4 does not fragment much in normal use, but it can
> get badly fragmented with fsstress for example?
>
> Now, the idea is to sell the repacker.
>
> Basically:
>
> 1) It could be binary-only
> Enough buyers will open the source like with Blender
> There would be online statistics which describe how much to go
> before this happens.
>
> 2) You could sell the sources and the rights to do whatever you want,
> except redistribute it.
Yes, I think this.
>
> There was the point that Blender had gained some popularity before
> the source release, which Reiser4 does not yet have. That may make
> this difficult to push through. A free repacker would make the situation
> better, but I see it as one of those annoying chicken-and-egg problems.
>
> The pricing must be ok too. Not so high that regular people won't buy it
> but not so cheap that it doesn't generate revenue.
I think 5% of the cost of the storage hardware (including raid cards), which
is about $5 for most people.
>
> If the source code is sold, people may want to develop it further, but
> I'm sure if they pay 1000000000e for it, they will expect perfection
> and not contribute.
>
> Then there's some copy-protection issues. I hope it will not be too
> heavily laid with license keys and stuff like that, because it makes
> usage harder and doesn't stop anyone from being an asshole.
No copy protection. We will make money from large corporations and not worry
about individual pirates.
>
> I understood that a binary-only model would be in the form of a kernel
> module? It may be the easiest method.
only user space portion will be non-gpl.
>
> Hans, what's your take on this?
> Maybe a real donations page would be required to get the baby up and
> running, maybe some really basic repacker but one that's so rock-solid
> that people would buy it and know they'll get free updates and in
> the end it'll be all open...
>
> Just my two cents worth of rambling again :)
thanks for your thoughts.
next prev parent reply other threads:[~2004-05-20 17:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 19:28 On a free repacker mjt
2004-05-20 17:28 ` Hans Reiser [this message]
2004-05-20 18:40 ` mjt
2004-05-22 2:32 ` Hans Reiser
2004-05-21 15:48 ` Redeeman
2004-05-22 2:57 ` Hans Reiser
2004-05-21 16:02 ` Redeeman
2004-05-21 18:49 ` mjt
2004-05-21 18:44 ` mjt
2004-05-21 19:02 ` Valdis.Kletnieks
2004-05-24 20:30 ` mjt
2004-05-24 20:41 ` Carl-Daniel Hailfinger
2004-05-24 20:47 ` mjt
2004-05-24 21:23 ` Carl-Daniel Hailfinger
2004-05-25 7:51 ` mjt
2004-05-25 1:12 ` Michael Milverton
2004-05-24 21:54 ` Valdis.Kletnieks
2004-05-27 4:10 ` Hans Reiser
2004-05-21 19:15 ` Mike Benoit
2004-05-21 19:36 ` mjt
-- strict thread matches above, loose matches on Subject: below --
2004-05-19 19:57 Burnes, James
2004-05-19 20:07 ` mjt
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=200405201028.13184.reiser@namesys.com \
--to=reiser@namesys.com \
--cc=flx@namesys.com \
--cc=mjt@nysv.org \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.