From owner-freebsd-arch@FreeBSD.ORG Sat Mar 8 14:24:38 2014 Return-Path: Delivered-To: freebsd-arch@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 46E858B8; Sat, 8 Mar 2014 14:24:38 +0000 (UTC) Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EBC4882C; Sat, 8 Mar 2014 14:24:37 +0000 (UTC) Received: by mail-oa0-f49.google.com with SMTP id g12so5339687oah.36 for ; Sat, 08 Mar 2014 06:24:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=s5CFWtJqPqzYLDANsAuTSQV9pW5Ds/mR2DACmLBZ35U=; b=SqCRyUbx7DqZesLdZRi+ZAlLn39M3+LeYIGPONmZU/ZPP3KOv1XgZoNveBXPYMDowE d9rxrPNQU48FZlMZDkRXjjHZUdY8c7h6zKiuTY2xsz4cS2KHa5Yu7CLdFC5eoznBezPA AwNRQcxLlufKoTem4S8y86cTcSKlwy0nkk3QfUxkKLCsf7Y80IcpE8SMRlSxVzBka3k4 AFou+ahoBywFepxxp+Sxsnwg9jfARnqecW6gdaiQtkpj3fkg+tfzgGOCH/5tgn75Zc8k Vu6lkLtOVeinGalrT+Pvt+ygJZQmGIrQ3JD2IWR6omoB1OIVJHoWXoTadLdeOuh+FoEV iLxA== X-Received: by 10.60.115.129 with SMTP id jo1mr16256116oeb.0.1394288677357; Sat, 08 Mar 2014 06:24:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.80.194 with HTTP; Sat, 8 Mar 2014 06:24:07 -0800 (PST) In-Reply-To: <1394199416.1149.367.camel@revolution.hippie.lan> References: <1394148413.1149.348.camel@revolution.hippie.lan> <1394199416.1149.367.camel@revolution.hippie.lan> From: Jia-Shiun Li Date: Sat, 8 Mar 2014 22:24:07 +0800 Message-ID: Subject: Re: Teach mdmfs about tmpfs and use tmpfs in rc scripts To: Ian Lepore Content-Type: text/plain; charset=UTF-8 Cc: freebsd-rc@freebsd.org, freebsd-arch X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Mar 2014 14:24:38 -0000 On Fri, Mar 7, 2014 at 9:36 PM, Ian Lepore wrote: > I'm not sure what you mean. If the device on the command line is md the > program behaves as it always has. If you ask for 'auto' you get the > "best" memory filesystem available for some definition of "best". If > you don't trust someone else's definition of best (like you need failure > at allocation time) then you choose the one that behaves the way you > like. ehh.. sorry read too fast and did not realize you 'added' new options in addition to existing 'md'. My bad. I did not use mdmfs often. My understanding is that it is the help to simplify mdconfig-newfs-mount process to replace a one-step mount_mfs. Then I agree with Konstantin, it does not look too appealing. If the goal is to merge all memory-backed fs to single versatile command, then the proposal does the job. Otherwise one mount_tmpfs comamnd does all user needs for tmpfs, and I am not sure the auto decision is good if user did not know what he need or care. It seems better to leave the decision to user. And for rc usage, I think we can just change it to tmpfs. If in the future tmpfs grows ability to populate content with e.g. a cpio archive at boot time or passed from command line, md usage can be further replaced. -Jia-Shiun.