Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762798AbYBFLkc (ORCPT ); Wed, 6 Feb 2008 06:40:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757757AbYBFLkW (ORCPT ); Wed, 6 Feb 2008 06:40:22 -0500 Received: from sovereign.computergmbh.de ([85.214.69.204]:43559 "EHLO sovereign.computergmbh.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754508AbYBFLkV (ORCPT ); Wed, 6 Feb 2008 06:40:21 -0500 Date: Wed, 6 Feb 2008 12:40:20 +0100 (CET) From: Jan Engelhardt To: Jeff Chua cc: lkml Subject: Re: where is the capset kernel module? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 834 Lines: 25 On Feb 6 2008 18:43, Jeff Chua wrote: >On Feb 6, 2008 4:13 PM, Jeff Chua wrote: >> Latest linux git complained about this ... >> >> named: capset failed: Operation not permitted: please ensure that the >> capset kernel module is loaded. see insmod(8) > >How this started was that with the latest git linux, I got this warning ... > >warning: `named' uses 32-bit capabilities (legacy support in use) Yes it is a really interesting case I have seen before, but did not bother to investigate. Is CONFIG_SECURITY=y CONFIG_SECURITY_CAPABILITIES=m or y working? -- 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/