From owner-freebsd-arch@FreeBSD.ORG Thu Jan 5 07:57:47 2012 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4FD5106566C; Thu, 5 Jan 2012 07:57:47 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4BB158FC08; Thu, 5 Jan 2012 07:57:45 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so336778vbb.13 for ; Wed, 04 Jan 2012 23:57:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=NnUQm+so8EsZCtaRNLd0CSQelC9+kFIQk6Xgde9em1w=; b=dM9coviIXtFZFHyY3f09uWHj93jSfTLn5H25GtlcgIOEzbPsvzMyvqwmV2XwoOVZ/z rLHPo1Uam6hzw1+VTcPCRV3rzzn82fTYq6dzsqxh1l2SrV5IDymjSXEiZ9GSI1BjsjfE p0TAvXSKuPADOAQOAGX1SAo4ybFL0Je59/DEw= MIME-Version: 1.0 Received: by 10.52.33.99 with SMTP id q3mr381210vdi.100.1325750264895; Wed, 04 Jan 2012 23:57:44 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.36.5 with HTTP; Wed, 4 Jan 2012 23:57:44 -0800 (PST) Date: Wed, 4 Jan 2012 23:57:44 -0800 X-Google-Sender-Auth: deumgNbsHau7Q5Qgx30ieF70xUA Message-ID: From: Adrian Chadd To: freebsd-arch@freebsd.org, freebsd-current , freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Is it possible to make subr_acl_nfs4 and subr_acl_posix1e disabled? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2012 07:57:47 -0000 Hi, I'm trying to slim down the freebsd kernel to fit on some devices with 4MB of flash. Since I'm not using NFS or UFS_ACL, I wondered if that code required. It turns out I can just build a kernel with those two disabled. Would it be possible to remove them from "standard" and make them optional? Or is there a reason to keep it in base? If so (eg so things can be kldload'ed that uses the ACL code) can we make it a build-time option, and/or a pair of loadable kernel modules? Thanks, Adrian