On 4/1/2013 11:41 AM, kpn...@pobox.com wrote:
Copyright covers expressions of ideas. It does not cover the ideas themselves.
You can't copyright a concept, you can't copyright filesystems, and I
believe in the past few years a high court in the EU ruled that you can't
copyright a programming lang
On Mon, 01 Apr 2013 10:26:15 -0400
Joe wrote:
> snip
>
> How do you explain all the forks of UNIX each claiming their own
> copyright.
Look very carefully at the copyrights involved, you will see
copyright attributions retained very carefully (see for example the
file /usr/src/COPY
Hi,
On Mon, 01 Apr 2013 10:26:15 -0400
Joe wrote:
> snip
>
> How do you explain all the forks of UNIX each claiming their own
> copyright. They all provide the same concept, use the same names for
> their commands, use the same programming language, have a filesystem
> as their base. Just
snip
How do you explain all the forks of UNIX each claiming their own
copyright. They all provide the same concept, use the same names for
their commands, use the same programming language, have a filesystem as
their base. Just where is the line drawn between a fork and a rewrite?
___
On Sun, 31 Mar 2013 16:43:27 +0200, Michael Ross wrote:
> On Sun, 31 Mar 2013 16:31:43 +0200, Polytropon wrote:
>
> > On Sun, 31 Mar 2013 09:39:29 -0400, Joe wrote:
> >> Does one have to file legal paper work with the government to be issued
> >> a copyright on software?
> >
> > With _which_ gove
On Sun, 31 Mar 2013 16:31:43 +0200, Polytropon wrote:
On Sun, 31 Mar 2013 09:39:29 -0400, Joe wrote:
Does one have to file legal paper work with the government to be issued
a copyright on software?
With _which_ government? :-)
Basic understanding of copyright is: The stuff _you_ write
happe
On Sun, 31 Mar 2013 09:39:29 -0400, Joe wrote:
> Does one have to file legal paper work with the government to be issued
> a copyright on software?
With _which_ government? :-)
Basic understanding of copyright is: The stuff _you_ write
happens "automatically" under _your_ copyright, because you
On Mar 31, 2013, at 6:39 AM, Joe wrote:
> kpn...@pobox.com wrote:
>> On Sat, Mar 30, 2013 at 09:22:22AM -0400, Maikoda Sutter wrote:
>>> If I use the kernel as a basis for my own system and modify the kernel
>>> should I still maintain the licensing of the kernel bits, or could release
>>> it un
kpn...@pobox.com wrote:
On Sat, Mar 30, 2013 at 09:22:22AM -0400, Maikoda Sutter wrote:
If I use the kernel as a basis for my own system and modify the kernel
should I still maintain the licensing of the kernel bits, or could release
it under it's own license?
For example: I would like to rewri
