linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jeremy Maitin-Shepard <jbms@attbi.com>
Cc: linux-kernel@vger.kernel.org, Kendrick Hamilton <hamilton@sedsystems.ca>
Subject: Re: Linux Kernel and GPL section 2c
Date: Wed, 10 Dec 2003 01:16:52 +0100	[thread overview]
Message-ID: <20031210001652.GC618@elf.ucw.cz> (raw)
In-Reply-To: <87ptezgnfv.fsf@jay.local.invalid>

Hi!

> > Hello all,
> >     I noticed the discussion about linux kernel modules that happened last
> >     week. I was wondering about something with regards to the linux kernel and
> >     Section 2c of the GPL. Why doesn't the kernel on booting print something
> >     about the kernel being free software licensed under the GPL, and shouldn't
> >     it?
> 
> Presumably, 1) the kernel as a whole is not a "modified" work, but
> rather at least parts of it are the original work, 2) it does not read
> commands interactively when run, 3) it does not normally print such
> announcements.

I see such announcements. I think we should just kill them all:

Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
CSLIP: code copyright 1989 Regents of the University of California.
Linux agpgart interface v0.100 (c) Dave Jones
ip_tables: (C) 2000-2002 Netfilter core team

Or perhaps we can replace 'POSIX conformance testing by UNIFIX' with
'Distribute under GPLv2'?
									Pavel
-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

      reply	other threads:[~2003-12-10  0:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08 18:14 Linux Kernel and GPL section 2c Kendrick Hamilton
2003-12-08 18:43 ` Jeremy Maitin-Shepard
2003-12-10  0:16   ` Pavel Machek [this message]

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=20031210001652.GC618@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=hamilton@sedsystems.ca \
    --cc=jbms@attbi.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).