From: Nix <nix@esperi.org.uk>
To: Valdis.Kletnieks@vt.edu
Cc: David Lang <david.lang@digitalinsight.com>,
Lee Revell <rlrevell@joe-job.com>, Hua Zhong <hzhong@gmail.com>,
marekw1977@yahoo.com.au, linux-kernel@vger.kernel.org
Subject: Re: Automatic Configuration of a Kernel
Date: Thu, 15 Sep 2005 21:50:48 +0100 [thread overview]
Message-ID: <877jdixdg7.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <200509152036.j8FKapjw025768@turing-police.cc.vt.edu> (Valdis Kletnieks's message of "Thu, 15 Sep 2005 16:36:51 -0400")
On Thu, 15 Sep 2005, Valdis Kletnieks murmured woefully:
> 1) This patch is pointless without other kernel magic to guarantee that
> even root can't open /dev/kmem - either SELinux and/or the 'devmem.patch'
> that's in current Fedora kernels. There's well-known ways to do the equivalent of
> an insmod even if the kernel is built with 'CONFIG_MODULES=n'.
Agreed; I use it in conjunction with a one-liner to remove CAP_RAWIO
from the capability bounding set.
> 2) Guess it's time to re-post my sysctl patch to provide a general-purpose
> one-shot... (Diffed against 2.6.11-mm4, but applies cleanly to 2.6.13-mm1 as well).
Yes, much nicer. (My goal, to get a better patch by posting my ugly one,
is achieved! ;) )
--
`One cannot, after all, be expected to read every single word
of a book whose author one wishes to insult.' --- Richard Dawkins
next prev parent reply other threads:[~2005-09-15 20:51 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 22:38 Automatic Configuration of a Kernel Ahmad Reza Cheraghi
2005-09-14 22:53 ` Michal Piotrowski
2005-09-14 23:49 ` Daniel Thaler
2005-09-15 0:09 ` Marek W
2005-09-15 0:37 ` Hua Zhong
2005-09-15 2:03 ` David Lang
2005-09-15 3:04 ` Lee Revell
2005-09-15 3:37 ` Daniel Thaler
2005-09-15 4:16 ` Lee Revell
2005-09-15 8:12 ` Ahmad Reza Cheraghi
2005-09-15 11:20 ` Masoud Sharbiani
2005-09-15 20:58 ` Ahmad Reza Cheraghi
2005-09-15 21:04 ` Jesper Juhl
2005-09-15 4:18 ` Marek W
2005-09-15 6:18 ` Valdis.Kletnieks
2005-09-15 7:33 ` Marek W
2005-09-15 9:48 ` Ahmad Reza Cheraghi
2005-09-15 10:44 ` David Lang
2005-09-15 10:26 ` David Lang
2005-09-15 14:58 ` Nix
2005-09-15 17:08 ` David Lang
2005-09-15 20:36 ` Valdis.Kletnieks
2005-09-15 20:50 ` Nix [this message]
2005-09-15 8:53 ` Chris White
2005-09-15 7:58 ` Ahmad Reza Cheraghi
2005-09-15 9:12 ` Emmanuel Fleury
2005-09-15 9:56 ` Ahmad Reza Cheraghi
2005-09-16 4:02 ` Chris White
2005-09-16 7:12 ` Emmanuel Fleury
2005-09-16 17:38 ` Pavel Machek
2005-09-16 17:50 ` Enrico Weigelt
2005-09-15 11:21 ` Roman Zippel
2005-09-15 12:01 ` Emmanuel Fleury
2005-09-15 13:02 ` Ahmad Reza Cheraghi
2005-09-15 13:28 ` Emmanuel Fleury
2005-09-15 13:03 ` Ahmad Reza Cheraghi
2005-09-17 1:27 ` Roman Zippel
2005-09-16 8:11 ` Coywolf Qi Hunt
2005-09-16 8:19 ` Emmanuel Fleury
2005-09-16 8:32 ` Ahmad Reza Cheraghi
2005-09-16 8:50 ` Emmanuel Fleury
2005-09-16 9:19 ` Ahmad Reza Cheraghi
-- strict thread matches above, loose matches on Subject: below --
2005-09-26 12:08 Ahmad Reza Cheraghi
2005-09-26 13:57 ` Michal Piotrowski
2005-09-26 14:06 ` Michal Piotrowski
2005-09-27 8:05 ` Coywolf Qi Hunt
2005-09-27 8:11 ` Emmanuel Fleury
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=877jdixdg7.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=Valdis.Kletnieks@vt.edu \
--cc=david.lang@digitalinsight.com \
--cc=hzhong@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marekw1977@yahoo.com.au \
--cc=rlrevell@joe-job.com \
/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.