From: Andre Tomt <andre@tomt.net>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Cc: Linda Walsh <lkml@tlinx.org>
Subject: Re: Save 320K on production machines?
Date: Sun, 26 Mar 2006 12:39:29 +0200 [thread overview]
Message-ID: <44266F61.9050209@tomt.net> (raw)
In-Reply-To: <4426515B.5040307@tlinx.org>
Linda Walsh wrote:
<snip>
> To minimize
> problems, I disable unused hardware, and all _used_ hardware
> is compiled in (no module loading overhead, no chances for
> arbitrary code insertion).
FYI, rootkits have been able to cope with inserting kernel code without
using the modules support for ages. It is only makes it marginally harder.
--
André Tomt
next prev parent reply other threads:[~2006-03-26 10:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 8:31 Save 320K on production machines? Linda Walsh
2006-03-26 9:24 ` Jan Engelhardt
2006-03-26 10:06 ` Adrian Bunk
2006-03-27 10:22 ` Linda Walsh
2006-03-27 11:36 ` Paulo Marques
2006-03-30 21:34 ` Linda Walsh
2006-03-31 9:43 ` Adrian Bunk
2006-03-31 9:48 ` Jörn Engel
2006-03-26 10:39 ` Andre Tomt [this message]
2006-03-27 10:05 ` Linda Walsh
2006-03-28 14:29 ` Jan Engelhardt
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=44266F61.9050209@tomt.net \
--to=andre@tomt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.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.