From owner-freebsd-arm@FreeBSD.ORG Mon Mar 3 04:13:45 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 17FA6D9 for ; Mon, 3 Mar 2014 04:13:45 +0000 (UTC) Received: from feynman.konjz.org (feynman.konjz.org [64.147.119.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D2ECE37E for ; Mon, 3 Mar 2014 04:13:44 +0000 (UTC) Received: from 127.0.0.1 (fiber19415337171.heldenvannu.net [37.153.194.171] (may be forged)) (authenticated bits=0) by feynman.konjz.org (8.14.7/8.14.4) with ESMTP id s234DZNd025311 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sun, 2 Mar 2014 23:13:41 -0500 (EST) (envelope-from george@ceetonetechnology.com) Message-ID: <5314016B.1000107@ceetonetechnology.com> Date: Sun, 02 Mar 2014 23:13:31 -0500 From: George Rosamond MIME-Version: 1.0 To: freebsd-arm@freebsd.org Subject: Re: TMPFS in kernels References: <5313D0FE.8010008@ceetonetechnology.com> <1393818974.1149.270.camel@revolution.hippie.lan> In-Reply-To: <1393818974.1149.270.camel@revolution.hippie.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: Mon, 03 Mar 2014 04:13:45 -0000 Ian Lepore: > On Sun, 2014-03-02 at 19:46 -0500, George Rosamond wrote: >> Is there a reason why TMPFS(5) is not in the 10-Stable's ALIX and RPI-B >> kernels, yet in BEAGLEBONE? Haven't checked the others. >> >> Seems like a strong and mature replacement for md(4) from my >> experiences, and probably belongs in the Crochet fstabs. I have been >> using on Alix, RPis, x86 for a long while, and never had any >> (noticeable) issues. >> >> g > > I agree. Should we add it to all configs, or just to armv6 configs? > I'd assume we should have it all the kernels.. especially since most of them are running off flash-type media, which makes memory-based disks pretty vital. g