public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: "Strange, John" <John.ws.Strange@marconi.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: include/linux/autoconf.h missing from 2.4.13?
Date: Wed, 31 Oct 2001 22:34:33 +0000	[thread overview]
Message-ID: <20011031223433.A4927@flint.arm.linux.org.uk> (raw)
In-Reply-To: <313680C9A886D511A06000204840E1CF3F0F02@whq-msgusr-02.pit.comms.marconi.com>
In-Reply-To: <313680C9A886D511A06000204840E1CF3F0F02@whq-msgusr-02.pit.comms.marconi.com>; from John.ws.Strange@marconi.com on Wed, Oct 31, 2001 at 03:37:35PM -0500

On Wed, Oct 31, 2001 at 03:37:35PM -0500, Strange, John wrote:
> This is really odd and I've double checked but for some reason a kernel that
> I downloaded from
> http://www.kernel.org/pub/linux/kernel/v2.4/linux-2.4.13.tar.gz doesn't seem
> to have the autoconf.h

The release kernels aren't supposed to have an autoconf.h - they're
generated by the make config / make menuconfig / make xconfig stage.

> Now the weird thing is that I downloaded this to another machine yesterday
> from the same url, which seems to have the autoconf.h???  I'm a little
> confused at the inconsistency and it worried me a little bit as possibly
> being tampered with?

You can always verify the integrity of your downloaded package - see
http://www.kernel.org/signature.html for instructions on this.  This
will show if any tampering has occured, but I doubt it.

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


      reply	other threads:[~2001-10-31 22:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-31 20:37 include/linux/autoconf.h missing from 2.4.13? Strange, John
2001-10-31 22:34 ` Russell King [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=20011031223433.A4927@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=John.ws.Strange@marconi.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