From owner-freebsd-arm@FreeBSD.ORG Mon Mar 3 00:47:09 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 2714B228 for ; Mon, 3 Mar 2014 00:47:09 +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 C60611C28 for ; Mon, 3 Mar 2014 00:47:08 +0000 (UTC) Received: from 127.0.0.1 (exit1.torproxy.org [89.187.142.208]) (authenticated bits=0) by feynman.konjz.org (8.14.7/8.14.4) with ESMTP id s230ktaI021034 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sun, 2 Mar 2014 19:46:58 -0500 (EST) (envelope-from george@ceetonetechnology.com) Message-ID: <5313D0FE.8010008@ceetonetechnology.com> Date: Sun, 02 Mar 2014 19:46:54 -0500 From: George Rosamond MIME-Version: 1.0 To: "freebsd-arm@freebsd.org" Subject: TMPFS in kernels Content-Type: text/plain; charset=UTF-8 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 00:47:09 -0000 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