From: mjt@nysv.org
To: "Dr. Giovanni A. Orlando" <gorlando@futuretg.com>,
Ramachandra K <ariston@gmail.com>,
reiserfs-list@namesys.com, reiser@namesys.com
Subject: Re: implementing reiserfs in C++ for a new OS
Date: Mon, 9 Aug 2004 20:24:37 +0300 [thread overview]
Message-ID: <20040809172437.GP1284@nysv.org> (raw)
In-Reply-To: <20040809170145.GE5429@parcelfarce.linux.theplanet.co.uk>
On Mon, Aug 09, 2004 at 06:01:45PM +0100, Chris Dukes wrote:
>So, how do you feel about the closed source licenses for Reiserfs
>that namesys.com sells?
Namesys can double-lincense as they want.
Anyway, I'd like some final clarity on this point, as Hans has said
that all is GPL, totally, but the README doesn't confirm this yet.
Just for the record, also, I would buy whatever closed-source stuff
Namesys sells, if it works and if it doesn't cause me more trouble than
it's worth, by, say, not giving free updates or requiring a certain
kernel with certain configurations.
Because it's the right thing to do.
They have the right to sell it and they need the money.
But still I think ransomware is the best way to go if in a pinch,
there will always be a next feature that could be held as ransomware,
after enough money has been gathered.
--
mjt
next prev parent reply other threads:[~2004-08-09 17:24 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-07 13:11 implementing reiserfs in C++ for a new OS Ramachandra K
2004-08-07 14:54 ` Redeeman
2004-08-07 15:05 ` Dr. Giovanni A. Orlando
2004-08-07 15:11 ` Redeeman
2004-08-07 17:51 ` Hans Reiser
2004-08-09 14:36 ` Ramachandra K
2004-08-09 14:52 ` Dr. Giovanni A. Orlando
2004-08-09 15:09 ` Marcelo Pacheco
2004-08-09 15:12 ` mjt
2004-08-09 15:22 ` Dr. Giovanni A. Orlando
2004-08-09 15:35 ` mjt
2004-08-09 17:01 ` Chris Dukes
2004-08-09 17:24 ` mjt [this message]
2004-08-10 5:26 ` Ramachandra K
2004-08-10 19:12 ` Quinn Harris
2004-08-10 19:51 ` Hans Reiser
2004-08-10 21:19 ` mjt
2004-08-10 22:05 ` Hans Reiser
2004-08-11 4:54 ` Spam
2004-08-11 6:08 ` Hans Reiser
2004-08-11 10:11 ` Nikita Danilov
2004-08-11 16:43 ` Hans Reiser
2004-08-11 16:47 ` mjt
2004-08-11 16:55 ` Nikita Danilov
2004-08-11 17:36 ` Hans Reiser
2004-08-11 17:42 ` Dr. Giovanni A. Orlando
2004-08-11 17:44 ` Nikita Danilov
2004-08-11 20:40 ` Dr. Giovanni A. Orlando
2004-08-11 23:12 ` Hans Reiser
2004-08-11 17:16 ` Chris Dukes
2004-08-11 17:26 ` Nikita Danilov
2004-08-11 17:40 ` mjt
2004-08-11 17:42 ` Hans Reiser
2004-08-11 17:16 ` Alex Zarochentsev
2004-08-11 17:42 ` Hans Reiser
2004-08-11 20:21 ` Spam
2004-08-12 14:44 ` mjt
2004-08-11 7:39 ` mjt
2004-08-11 7:51 ` Hans Reiser
2004-08-11 8:01 ` mjt
2004-08-11 8:10 ` Dr. Giovanni A. Orlando
2004-08-11 8:28 ` Hans Reiser
2004-08-11 9:00 ` mjt
2004-08-11 9:44 ` Dr. Giovanni A. Orlando
2004-08-11 9:55 ` Rudy L. Zijlstra
2004-08-11 10:18 ` Nikita Danilov
2004-08-11 16:51 ` Hans Reiser
2004-08-11 10:54 ` mjt
2004-08-11 11:07 ` Christophe Saout
2004-08-11 12:12 ` Dr. Giovanni A. Orlando
2004-08-11 12:39 ` mjt
2004-08-11 13:04 ` Dr. Giovanni A. Orlando
2004-08-11 13:21 ` mjt
2004-08-11 23:22 ` Tom Vier
2004-08-12 14:47 ` mjt
2004-08-11 22:04 ` David Greaves
2004-08-09 15:17 ` Jonathan Briggs
[not found] <20040808020024.746D415C29@mail03.powweb.com>
2004-08-08 2:11 ` David Dabbs
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=20040809172437.GP1284@nysv.org \
--to=mjt@nysv.org \
--cc=ariston@gmail.com \
--cc=gorlando@futuretg.com \
--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.