Date: Sun, 16 Nov 2008 07:39:48 -0800
From: Arjan van de Ven <arjan@infradead.org>
To: Bernhard Walle <bwalle@suse.de>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
       crash-utility@redhat.com, Bernhard Walle <bwalle@suse.de>
Subject: Re: Turn CONFIG_STRICT_DEVMEM in sysctl dev.mem.restricted
Message-ID: <20081116073948.02aea58c@infradead.org>
In-Reply-To: <1226846868-9595-1-git-send-email-bwalle@suse.de>
References: <1226846868-9595-1-git-send-email-bwalle@suse.de>
Organization: Intel
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 986
Lines: 27

On Sun, 16 Nov 2008 15:47:45 +0100
Bernhard Walle <bwalle@suse.de> wrote:

> While the original submission of CONFIG_STRICT_DEVMEM mentions that
> the option has been in RHEL and Fedora for 4 years without problems,
> that's only a half of the story. The truth is that at least RHEL
> has /dev/crash exactly to circumvent that /dev/mem restriction. Don't
> tell me that this is better than having that sysctl entry. ;-)

I assume /dev/crash is read only


but your series still makes absolutely no sense to me...
really. Nak.

You either want this at compile time or you don't want it at all.


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/