From owner-freebsd-current@freebsd.org Thu Sep 21 03:47:18 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 26E17E0FC1C for ; Thu, 21 Sep 2017 03:47:18 +0000 (UTC) (envelope-from jon@brawn.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 05BB366E2B for ; Thu, 21 Sep 2017 03:47:18 +0000 (UTC) (envelope-from jon@brawn.org) Received: by mailman.ysv.freebsd.org (Postfix) id 050E1E0FC1B; Thu, 21 Sep 2017 03:47:18 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04A9FE0FC1A for ; Thu, 21 Sep 2017 03:47:18 +0000 (UTC) (envelope-from jon@brawn.org) Received: from mx2.ahs1.r4l.com (mx2.ahs1.r4l.com [192.95.23.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CC37A66E2A; Thu, 21 Sep 2017 03:47:17 +0000 (UTC) (envelope-from jon@brawn.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=brawn.org; s=default; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date: In-Reply-To:From:Subject:Mime-Version:Content-Type:Sender:Reply-To:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe :List-Post:List-Owner:List-Archive; bh=VjFtQXS0OxVIWuiSIjpxMb96jekGbWPj4z9iRos+2kw=; b=UBbPCB/3WmVKlYxDgWdQyz77Cl Hkbe5Y5npz79v0AlZmBDHdSAT3MCcz1Jz2UUYZz0zRL1Diq7SJnWgDOU8+TB7NkCMkDoeipW/Vk6f WJTAoIil9YlYIDfVTkLbUoVW8pje4mOVo3mEE3gU4mnY3QxvMoMPOJh+xabKIjH4pza4S/vQLkKpK L2fDARp/4sGW3zTDA83kcPy3JBDPsbuDAenvjkE3fyg4o/fpjH+h8RBVbk5t2N9jYMEqGvjjNdCFU Vy+aw/8jhWliUxs+Eh5gi8q1fVO44XzYgzlWK/e170UsQDuUEMxlx38IRZ2gwvoa8c9HaJuMQNgTK ULlE4uMg==; Received: from [136.62.171.86] (port=49878 helo=[192.168.1.159]) by ahs1.r4l.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1dusSJ-004EtY-Ql; Wed, 20 Sep 2017 23:47:16 -0400 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Pre-filled RAM disk. From: Jon Brawn In-Reply-To: <1505964913.73082.65.camel@freebsd.org> Date: Wed, 20 Sep 2017 22:47:12 -0500 Cc: FreeBSD Current , Warner Losh Content-Transfer-Encoding: quoted-printable Message-Id: <7CD79E48-F62E-46CC-896F-A9C87047B85D@brawn.org> References: <1505964913.73082.65.camel@freebsd.org> To: Ian Lepore X-Mailer: Apple Mail (2.3273) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ahs1.r4l.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - brawn.org X-Get-Message-Sender-Via: ahs1.r4l.com: authenticated_id: jon@brawn.org X-Authenticated-Sender: ahs1.r4l.com: jon@brawn.org X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Sep 2017 03:47:18 -0000 On Sep 20, 2017, at 10:35 PM, Ian Lepore wrote: >=20 > On Wed, 2017-09-20 at 21:23 -0600, Warner Losh wrote: >> On Wed, Sep 20, 2017 at 9:16 PM, Warner Losh wrote: >>=20 >>> On Wed, Sep 20, 2017 at 8:50 PM, Jon Brawn wrote: >>>=20 >>>>=20 >>>> Wotcha! >>>>=20 >>>> >>>> So, what does FreeBSD have to offer in the way of ramdisk >>>> functionality? >>>>=20 >>> Yes. >>>=20 >>> See MD_ROOT and friends. >>>=20 >> The MFS_IMAGE kernel option has replaced this. >>=20 >> Warner >=20 > And the documentation (such as it is) for MFS_IMAGE is in the md(4) > manpage. In a nutshell, it's a mechanism that lets you compile an > existing filesystem image directly into the kernel and it is mounted = as > a memory filesystem at boot time. Hopefully being contained within = the > kernel will make the problem of loading it at a fixed physical address > go away for you. >=20 > -- Ian >=20 I really need to bring more of my work problems to this list, obviously. = Thanks folks! Jon.=