All of lore.kernel.org
 help / color / mirror / Atom feed
From: mjt@nysv.org
To: Hans Reiser <reiser@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: On a free repacker
Date: Fri, 21 May 2004 21:44:51 +0300	[thread overview]
Message-ID: <20040521184451.GS24604@nysv.org> (raw)
In-Reply-To: <40AEBBA0.6060606@namesys.com>

On Fri, May 21, 2004 at 07:32:00PM -0700, Hans Reiser wrote:
>Markus Törnqvist wrote:

>>I'm not sure I follow. Buyers will tell you what hardware they have and
>>you will price it accordingly?
>>Good for large customers, bad for individuals...
>Don't understand the last sentence.
>
>We will throw in full reiser4 support, with cell phones of developers 
>for persons spending at least $500.

So let's say the average guy has 100GB of hard drive at the cost of $5.
The pricing starts to suck if it's too closely tied to drive capacity
for private people. "Yeah, you pay 2.50 for it, you 10" and so on.

Doesn't work.

However, large customers should be able to see that there's a corporate
pricing as well. If someone from a major ISP wants to buy a private
license for $5, it's a warning that they may abuse this :)

I just hope it stays affordable and simple for private people and
profitable for corporations :)

>>At the price of five bucks, I won't mind paying even if it isn't
>>ransomware, but I think ransomware will be more widely accepted...
>I don't think the need for more reiserfs features whose development 
>needs to be paid for is finite....

I'm just thinking along the lines of making enough profit from the
repacker to cover expenses and then some, releasing it and having
the next feature as ransomware.

Basically some friends and I have had long talks about that as a
business model, but have reached no better concensus than "might work"
This has never been talked about for a project that has wages to pay,
though...

>but hey, if some distro comes along and offers to sponsor us in return 
>for a free resizer, they know where to email me.....

Or a distro buys the resizer (with source code, as I hope is always the
case) and develops it with you, and everyone who bought it is entitled
to an upgrade, yes? no?

That's probably the next best thing after money ;)

>I need a business model that works well enough to pay the bills.  The 
>resizer is just one more experiment towards finding it.

Hope one evolves and other people may use it too.

-- 
mjt


  parent reply	other threads:[~2004-05-21 18:44 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
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 [this message]
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=20040521184451.GS24604@nysv.org \
    --to=mjt@nysv.org \
    --cc=reiser@namesys.com \
    --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.