From: David Rees <dbr@greenhydrant.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18 - Full tarball is OK
Date: Mon, 25 Feb 2002 14:40:15 -0800 [thread overview]
Message-ID: <20020225144015.A32006@greenhydrant.com> (raw)
In-Reply-To: <200202252149.g1PLnwe13182@directcommunications.net>
In-Reply-To: <200202252149.g1PLnwe13182@directcommunications.net>; from chris@directcommunications.net on Mon, Feb 25, 2002 at 09:49:58PM +0000
On Mon, Feb 25, 2002 at 09:49:58PM +0000, Chris Funderburg wrote:
>
> FYI - The full tarball already has the missing patch...
>
> So, I think, it's only patch-2.4.18 that has the problem...
Uh, no, it doesn't. Using linux-2.4.18.tar.bz2 dated Feb 25, 2002 11:40am:
diff -urN linux-2.4.18-rc4/Makefile linux-2.4.18/Makefile
--- linux-2.4.18-rc4/Makefile Mon Feb 25 14:35:52 2002
+++ linux-2.4.18/Makefile Mon Feb 25 11:37:52 2002
@@ -1,7 +1,7 @@
VERSION = 2
PATCHLEVEL = 4
SUBLEVEL = 18
-EXTRAVERSION = -rc4
+EXTRAVERSION =
KERNELRELEASE=$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION)
diff -urN linux-2.4.18-rc4/fs/binfmt_elf.c linux-2.4.18/fs/binfmt_elf.c
--- linux-2.4.18-rc4/fs/binfmt_elf.c Mon Feb 25 14:35:55 2002
+++ linux-2.4.18/fs/binfmt_elf.c Mon Feb 25 11:38:08 2002
@@ -564,9 +564,6 @@
// printk(KERN_WARNING "ELF: Ambiguous type, using
ELF\n");
interpreter_type = INTERPRETER_ELF;
}
- } else {
- /* Executables without an interpreter also need a
personality */
- SET_PERSONALITY(elf_ex, ibcs2_interpreter);
}
/* OK, we are done with that, now set up the arg stuff,
next prev parent reply other threads:[~2002-02-25 22:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 21:49 Linux 2.4.18 - Full tarball is OK Chris Funderburg
2002-02-25 22:37 ` Alan Cox
2002-02-25 22:32 ` Rik van Riel
2002-02-25 22:40 ` H. Peter Anvin
2002-02-25 22:49 ` Alan Cox
2002-02-25 22:34 ` Beezly
2002-02-25 22:38 ` Dan Chen
2002-02-25 23:09 ` Alan Cox
2002-02-25 22:40 ` David Rees [this message]
2002-02-25 23:02 ` Bernd Eckenfels
-- strict thread matches above, loose matches on Subject: below --
2002-02-25 21:49 Chris Funderburg
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=20020225144015.A32006@greenhydrant.com \
--to=dbr@greenhydrant.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 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.