From: Hubert Chan <hubert@uhoreg.ca>
To: reiserfs-list@namesys.com
Subject: Re: Debian and non-free
Date: Sun, 25 Apr 2004 19:47:32 -0400 [thread overview]
Message-ID: <874qr7y60b.fsf@uhoreg.ca> (raw)
In-Reply-To: 20040425145238.GQ19049@nysv.org
>>>>> "Markus" == Markus Törnqvist <mjt@nysv.org> writes:
Markus> Hi IANADD and all that, so where can I read about why Reiser4 is
Markus> unsuitable for even non-free?
debian-legal mailing list.
Markus> The way I read the license of Reiser4 is that it's GPL but one
Markus> can write plugins, derivative works of GPL, but keep the sources
Markus> by paying money?
Yes. Namesys is allowed to dual-license their code, since they own it
(and/or have been assigned the copyright by those who wrote it). So if
the GPL is not suitable for a company, then they can give Namesys
money, and obtain an alternative license.
This is the same as what TrollTech does with the Qt library. (As well
as a few other companies, with their software.)
Or companies can just keep the binary, and their sources, private
i.e. for internal use only. That kind of use is allowed by the GPL.
Markus> This seems like an internal conflict in the license itself;
Markus> without having paying money as a forced bribe of sorts to keep
Markus> the source closed, it would seem like a BSD-style license. BSD
Markus> should be ok by Debian Free even.
I don't understand what you are saying here. BSD is much more
permissive than GPL.
Markus> So why is it disqualified?
Some people have reservations with some of the clarifications to the
GPL that Namesys has added. (I have not read the clarifications in
detail, and I don't follow d-legal (yet), so I can't comment.)
Markus> Debian is often seen as the distro for people who like stability
Markus> and security. Reiser4 has stabilized by the bucket and at
Markus> latest views will bring along the strictest of security.
Debian is also very well known for being picky about copyright and
freedom.
Markus> It would be a shame if Debian users, such as I, would have to
Markus> continue bootstrapping Debian onto Reiser4 instead of just
Markus> installing. And there are a lot of Debian users out there as a
Markus> target audience.
Markus> Does Debian have anything against third party installers which
Markus> would use Reiser4? Probably not?
No. There are many Debian-based distros, such as Knoppix, Libranet,
Lindows (or whatever it's called today), etc. Debian has nothing
against them, and sometimes even encourages them (especially if they
contribute back to the community.)
Markus> Considering the centuries it would take for Debian to validate
Markus> Reiser4 for installer-inclusion.
I actually wouldn't be surprised if the installer for sarge+1 included
Reiser4. All that's really needed is for Reiser4 to get into the
stable kernel, and someone to write (good) support for debian-installer.
--
Hubert Chan <hubert@uhoreg.ca> - http://www.uhoreg.ca/
PGP/GnuPG key: 1024D/124B61FA
Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA
Key available at wwwkeys.pgp.net. Encrypted e-mail preferred.
next prev parent reply other threads:[~2004-04-25 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-25 14:52 Debian and non-free mjt
2004-04-25 21:34 ` Redeeman
2004-04-25 23:47 ` Hubert Chan [this message]
2004-04-26 6:33 ` mjt
2004-04-26 19:53 ` Hubert Chan
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=874qr7y60b.fsf@uhoreg.ca \
--to=hubert@uhoreg.ca \
--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.