From owner-freebsd-arm@FreeBSD.ORG Fri Mar 7 00:43:43 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 491AD624 for ; Fri, 7 Mar 2014 00:43:43 +0000 (UTC) Received: from mail-pd0-f174.google.com (mail-pd0-f174.google.com [209.85.192.174]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1597021C for ; Fri, 7 Mar 2014 00:43:42 +0000 (UTC) Received: by mail-pd0-f174.google.com with SMTP id y13so3261922pdi.19 for ; Thu, 06 Mar 2014 16:43:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=a8jgxV8pBMDlgB6Qx5opVfeu/BkRzHevV3OoRUrm8qQ=; b=WPxHxkkQmBFpjKnwL10YTUQZvKngFwIZDXzd2w6ui4L6q64/oHOQsOwO5MwtvXU3Zv 6CGG/AgYPP3yyBkC1/bDrmUC2cvkh1H0fW+cu/JF1CNCswGGlKAZiA7wIClpA7Kg6yGD zA0Fnz6kO0zjtEGCsctblSvn3wBh/5ZBv6/1zjbCXOXB5ieRICHVBgRvvEW/LTTI9dmF RtYydTKWEE7RiHZBWMoktMx+9BuKCSCHs6EmMjRAHZDfTIIxvBIqk1QAukH9IO/TTYJP pZN7X3ZRenkr78rsTmUj9zGyIZo2sGG43NcLw0V1pjEhQ/Sf1hwuhiH6n/YBRCcJY99l YDug== X-Gm-Message-State: ALoCoQkS6F78T4/ZhhTBGCJoDX2wfNjUVafJ2BrBRVmSdHaty5zMCi9h8EQAaBFcRKM1MylBlBw8 X-Received: by 10.66.141.197 with SMTP id rq5mr18427693pab.64.1394153022509; Thu, 06 Mar 2014 16:43:42 -0800 (PST) Received: from lglt-nvaradarajan.corp.netflix.com (dc1-prod.netflix.com. [69.53.236.251]) by mx.google.com with ESMTPSA id vb7sm24075264pbc.13.2014.03.06.16.43.41 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 06 Mar 2014 16:43:41 -0800 (PST) Sender: Warner Losh Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: TMPFS in kernels From: Warner Losh In-Reply-To: <20140307003610.GE87036@glenbarber.us> Date: Thu, 6 Mar 2014 17:43:42 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <5314016B.1000107@ceetonetechnology.com> <20140303061136.GB85204@zibbi.meraka.csir.co.za> <1394148799.1149.354.camel@revolution.hippie.lan> <53190F52.7030605@ceetonetechnology.com> <1394151627.1149.357.camel@revolution.hippie.lan> <1394152175.1149.360.camel@revolution.hippie.lan> <20140307003610.GE87036@glenbarber.us> To: Glen Barber X-Mailer: Apple Mail (2.1874) Cc: "freebsd-arm@freebsd.org" , Ian Lepore X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Mar 2014 00:43:43 -0000 On Mar 6, 2014, at 5:36 PM, Glen Barber wrote: > On Thu, Mar 06, 2014 at 05:29:35PM -0700, Ian Lepore wrote: >> On Thu, 2014-03-06 at 17:25 -0700, Warner Losh wrote: >>> On Mar 6, 2014, at 5:20 PM, Ian Lepore wrote: >>>=20 >> [...] >>>> Yeah, for the kernel side of it, I'm just adding TMPFS to >>>> arm/conf/DEFAULTS since the concensus seems to be that we want it = in all >>>> kernels. I'm waiting for a universe-kernels build to finish and if = it's >>>> clean I'll commit that tonight. >>>=20 >>> DEFAULTS was never intended for something like this.. Only for = things that >>> must be mandatory or very nearly mandatory for the system to = operate. While >>> useful, this isn=92t mandatory by any stretch of the imagination. I = strongly object >>> to putting it there, so please don=92t commit it to DEFAULTS. >>=20 >>=20 >> Ooops, your email and the commit passed each other on the wires. >>=20 >> But... really? An option we want in every kernel we should paste = into >> 70+ files instead of into the one file that they all include? >>=20 >=20 > Why not include it by default, and exclude it where not needed/wanted? DEFAULTS isn=92t the place for this. Warner