All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: Travis Crump <pretzalz@techhouse.org>
Cc: Marcel Weber <mmweber@ncpro.com>,
	Hans Reiser <reiser@namesys.com>,
	Vitaly Fertman <vitaly@namesys.com>,
	reiserfs-list@namesys.com, debian-testing@lists.debian.org,
	Ed Boraas <ed@debian.org>,
	debian-devel@lists.debian.org
Subject: Re: plagiarism of reiserfs by Debian
Date: Sat, 19 Apr 2003 16:55:55 -0400	[thread overview]
Message-ID: <20030419205555.GY2528@phunnypharm.org> (raw)
In-Reply-To: <3EA19DEC.3090202@techhouse.org>

> all that was removed was *code* that gets compiled.  If the maintainer 
> cannot arbitrarily change any code he wants, then it is not clear that 
> the program is DFSG-free.

Amen. Making part of the code immutable is not what I call free
software. What if I want to use parts of the code and I respect the
copyright and license...does that mean I also have to take this part of
the code and output the credits? What if environment doesn't provide a
way to output the credits. What if I am implementing the reiser tools on
an embedded system that will never show any such output?

What about programs that execute the reiserfs tools (like bootup
scripts)...are they not allowed to redirect or filter this output?

If any of this is questionable, then I suspect reiserfs tools isn't DFSG
compliant and belongs in non-free with all it's flakiness.

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo       - http://www.deqo.com/

  reply	other threads:[~2003-04-19 20:55 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-18 12:04 reiserfsck infinite loop at pass2 (built by Debian) Vitaly Fertman
2003-04-18 15:10 ` Dieter Nützel
2003-04-18 15:11   ` Oleg Drokin
2003-04-18 15:26     ` Dieter Nützel
2003-04-18 15:27       ` Oleg Drokin
2003-04-19 16:07 ` plagiarism of reiserfs by Debian Hans Reiser
2003-04-19 17:29   ` Ben Collins
2003-04-19 18:40     ` Jarno Elonen
2003-04-19 19:24     ` Matt Ryan
2003-04-19 20:56       ` Ben Collins
2003-04-20 19:39         ` Matt Ryan
2003-04-19 18:02   ` Marcel Weber
2003-04-19 19:05     ` Travis Crump
2003-04-19 20:55       ` Ben Collins [this message]
2003-04-19 21:13         ` Anders Widman
2003-04-19 21:09           ` Ben Collins
2003-04-19 22:25         ` Andreas Dilger
2003-04-19 23:06           ` Chris Cheney
2003-04-20  0:49             ` Marcel Weber
2003-04-20  3:41               ` Glenn Maynard
2003-04-20  6:17                 ` Manuel Krause
2003-04-20  6:44                   ` Manuel Krause
2003-04-22  2:28                 ` Anthony DeRobertis
2003-04-23 15:17                   ` Hans Reiser
2003-04-23 15:35                     ` Anthony DeRobertis
2003-04-23 20:10                     ` Adam Heath
2003-04-21  6:03       ` Oleg Drokin
2003-04-21  8:47         ` Yury Umanets
2003-04-19 18:30   ` Florian Weimer
2003-04-19 20:51     ` Lukas Geyer
2003-04-19 23:24       ` Wouter Verhelst
2003-04-21 18:49         ` Walter Landry
2003-04-22  1:15         ` Brian M. Carlson
2003-04-21 13:22     ` bscott
2003-04-20  1:18   ` Matt Zimmerman
2003-04-20  1:20     ` Matt Zimmerman
2003-04-20 11:42   ` Marcelo E. Magallon

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=20030419205555.GY2528@phunnypharm.org \
    --to=bcollins@debian.org \
    --cc=debian-devel@lists.debian.org \
    --cc=debian-testing@lists.debian.org \
    --cc=ed@debian.org \
    --cc=mmweber@ncpro.com \
    --cc=pretzalz@techhouse.org \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=vitaly@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.