From: Keith Owens <kaos@ocs.com.au>
To: root@chaos.analogic.com
Cc: Horst von Brand <vonbrand@inf.utfsm.cl>, linux-kernel@vger.kernel.org
Subject: Re: kernel size
Date: Wed, 10 Oct 2001 11:29:31 +1000 [thread overview]
Message-ID: <7568.1002677371@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 09 Oct 2001 11:53:48 -0400." <Pine.LNX.3.95.1011009114946.4152A-100000@chaos.analogic.com>
On Tue, 9 Oct 2001 11:53:48 -0400 (EDT),
"Richard B. Johnson" <root@chaos.analogic.com> wrote:
>Yes. It shows in /proc/kcore. Just wasted. It does mean something
>on an embedded system.
kcore shows all the kernel buffers, including user space stuff being
processed by the loader. My tests show that all the strings that you
are complaining about have been stripped from the kernel before it is
loaded.
next prev parent reply other threads:[~2001-10-10 1:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 14:16 kernel size VDA
2001-10-09 13:26 ` [solid]
2001-10-09 13:28 ` Nikita Danilov
2001-10-10 9:10 ` kernel size, kcore fun Helge Hafting
2001-10-09 14:16 ` kernel size Richard B. Johnson
2001-10-09 14:43 ` Ingo Oeser
2001-10-09 14:52 ` Richard B. Johnson
2001-10-09 15:43 ` Horst von Brand
2001-10-09 15:53 ` Richard B. Johnson
2001-10-10 1:29 ` Keith Owens [this message]
2001-10-10 13:00 ` Richard B. Johnson
2001-10-10 14:47 ` vda
2001-10-11 12:41 ` vda
2001-10-10 1:30 ` Kenneth Johansson
2001-10-09 15:55 ` Jakub Jelinek
2001-10-10 1:27 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2001-12-13 4:38 Kernel size rohit prasad
2001-12-07 8:53 kernel size rohit prasad
2001-12-07 16:46 ` Eli Carter
2001-10-04 13:11 Security question: "Text file busy" overwriting executables but not shared libraries? Eric W. Biederman
2001-10-04 14:24 ` Kernel size Richard B. Johnson
2001-10-13 20:35 ` Aaron Lehmann
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=7568.1002677371@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=vonbrand@inf.utfsm.cl \
/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