public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Telford002@aol.com
To: <c_marinas@yahoo.com>, <newby@teco-xaco.com>
Cc: <roy@karlsbakk.net>, <linux-kernel@vger.kernel.org>
Subject: Re: opening a bzImage?
Date: Tue, 05 Feb 2002 19:25:33 EST	[thread overview]
Message-ID: <147.902cabc.2991d1fd@aol.com> (raw)

If I am not mistaken, nothing more than the
autoconf.h used in building the kernel is needed.
The .config can be regenerated therefrom if necessary.

Joachim Martillo

In a message dated Tue, 5 Feb 2002  6:02:16 PM Eastern Standard Time, Catalin Marinas <c_marinas@yahoo.com> writes:

> On Tue, 5 Feb 2002, Daniel A. Newby wrote:
> 
> > > Btw.. Does GPL require them to give me the .config file?
> >
> > definition files, plus the scripts used to control compilation and
> > installation of the executable."
> >
> > IMHO, .config is a "script used to control compilation".
> 
> I think (though I might be wrong) this is not considered a "script used to
> control compilation" in GPL acception, even if it does this. It is not
> included in the kernel sources, it is generated by other scripts
> (kconfig.tk for example, which is also generated). This is like, for
> example, intermediar .s files generated from .c ones. Nobody would bother
> to include this in the sources.
> 
> I don't think it should be included in the kernel sources because you
> can generate it by yourself (of course, you want to know theirs). So, they
> might not be forced to give you the .config file.
> 
> Regards.
> 
> -- 
> Catalin
> 
> 
> ________________________________________________________________________
> This email has been scanned for all viruses by the MessageLabs SkyScan
> service. For more information on a proactive anti-virus service working
> around the clock, around the globe, visit http://www.messagelabs.com
> ________________________________________________________________________
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/



             reply	other threads:[~2002-02-06  0:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-06  0:25 Telford002 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-05 14:42 opening a bzImage? Roy Sigurd Karlsbakk
2002-02-05 14:54 ` Drew P. Vogel
2002-02-05 15:05   ` Roy Sigurd Karlsbakk
2002-02-05 15:07     ` Drew P. Vogel
2002-02-05 15:13       ` Roy Sigurd Karlsbakk
2002-02-05 15:29         ` Drew P. Vogel
2002-02-05 15:40           ` Roy Sigurd Karlsbakk
2002-02-06  9:03             ` Horst von Brand
2002-02-06 14:40               ` Drew P. Vogel
2002-02-05 15:15   ` Chris Funderburg
2002-02-05 17:22 ` Catalin Marinas
2002-02-06  7:40   ` Daniel Phillips
2002-02-05 18:19 ` Daniel A. Newby
2002-02-05 22:55   ` Catalin Marinas
2002-02-06 10:14     ` Horst von Brand
2002-02-06 17:21     ` Tommy Reynolds

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=147.902cabc.2991d1fd@aol.com \
    --to=telford002@aol.com \
    --cc=c_marinas@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=newby@teco-xaco.com \
    --cc=roy@karlsbakk.net \
    /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