From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Wilcox Subject: Re: Btrfs v0.14 Released Date: Fri, 2 May 2008 08:38:12 -0600 Message-ID: <20080502143811.GC14976@parisc-linux.org> References: <200804291601.32945.chris.mason@oracle.com> <200805020852.51125.chris.mason@oracle.com> <200805021034.08358.chris.mason@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: jeffschroeder@computer.org, Jan Engelhardt , Jeff Mahoney , Tim Gardner , linux-fsdevel@vger.kernel.org, kernel-team@lists.ubuntu.com, linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org, John Johansen To: Chris Mason Return-path: Received: from palinux.external.hp.com ([192.25.206.14]:41036 "EHLO mail.parisc-linux.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758847AbYEBOiN (ORCPT ); Fri, 2 May 2008 10:38:13 -0400 Content-Disposition: inline In-Reply-To: <200805021034.08358.chris.mason@oracle.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, May 02, 2008 at 10:34:07AM -0400, Chris Mason wrote: > Thanks, but this uses CONFIG_SECURITY_APPARMOR which isn't enough to tell if > the kernel has the patch. Lets go back to Jeff's suse patch: Do we really need to support kernels compiled with the apparmour patch applied but not enabled? That would be a custom kernel build, and I get the impression that people Just Don't Do That -- if they want a newer kernel, they fetch one from kernel.org. Maybe I'm wrong though. -- Intel are signing my paycheques ... these opinions are still mine "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step."