From owner-freebsd-current@freebsd.org Thu Sep 21 05:10:06 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 D3C04E138D3 for ; Thu, 21 Sep 2017 05:10:06 +0000 (UTC) (envelope-from ian@freebsd.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 B0B14695D5 for ; Thu, 21 Sep 2017 05:10:06 +0000 (UTC) (envelope-from ian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id AFFAFE138D2; Thu, 21 Sep 2017 05:10:06 +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 AF9AFE138D1 for ; Thu, 21 Sep 2017 05:10:06 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from nov-007-i577.relay.mailchannels.net (nov-007-i577.relay.mailchannels.net [46.232.183.131]) (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 525D4695D0 for ; Thu, 21 Sep 2017 05:10:01 +0000 (UTC) (envelope-from ian@freebsd.org) X-Sender-Id: _forwarded-from|73.78.92.27 Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id E751636A429 for ; Thu, 21 Sep 2017 03:50:56 +0000 (UTC) Received: from outbound1a.eu.mailhop.org (unknown [100.96.147.57]) (Authenticated sender: duocircle) by relay.mailchannels.net (Postfix) with ESMTPA id 53B88368A0B for ; Thu, 21 Sep 2017 03:50:56 +0000 (UTC) X-Sender-Id: _forwarded-from|73.78.92.27 Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [172.20.72.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.9.14); Thu, 21 Sep 2017 03:50:56 +0000 X-MC-Relay: Forwarding X-MailChannels-SenderId: _forwarded-from|73.78.92.27 X-MailChannels-Auth-Id: duocircle X-Spill-Descriptive: 6ea39ab13f4ee63b_1505965856714_550263714 X-MC-Loop-Signature: 1505965856714:2905040376 X-MC-Ingress-Time: 1505965856713 X-MHO-User: 0eab0e3c-9e80-11e7-a893-25625093991c X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 0eab0e3c-9e80-11e7-a893-25625093991c; Thu, 21 Sep 2017 03:50:51 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v8L3omOm014138; Wed, 20 Sep 2017 21:50:48 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1505965848.73082.69.camel@freebsd.org> Subject: Re: Pre-filled RAM disk. From: Ian Lepore To: Jon Brawn Cc: FreeBSD Current , Warner Losh Date: Wed, 20 Sep 2017 21:50:48 -0600 In-Reply-To: <7CD79E48-F62E-46CC-896F-A9C87047B85D@brawn.org> References: <1505964913.73082.65.camel@freebsd.org> <7CD79E48-F62E-46CC-896F-A9C87047B85D@brawn.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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 05:10:06 -0000 On Wed, 2017-09-20 at 22:47 -0500, Jon Brawn wrote: > On Sep 20, 2017, at 10:35 PM, Ian Lepore wrote: > >=20 > >=20 > > On Wed, 2017-09-20 at 21:23 -0600, Warner Losh wrote: > > >=20 > > > On Wed, Sep 20, 2017 at 9:16 PM, Warner Losh > > > wrote: > > >=20 > > > >=20 > > > > On Wed, Sep 20, 2017 at 8:50 PM, Jon Brawn > > > > wrote: > > > >=20 > > > > >=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 > > And the documentation (such as it is) for MFS_IMAGE is in the md(4) > > manpage.=A0=A0In a nutshell, it's a mechanism that lets you compile a= n > > existing filesystem image directly into the kernel and it is > > mounted as > > a memory filesystem at boot time.=A0=A0Hopefully being contained with= in > > 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! >=20 > Jon. > _______________________________________________ Another good place for help with freebsd on arm is the #bsdmips channel on efnet, if you're an irc-using kind of person. =A0Don't let the 'mips' in the name throw you, it's the channel where the arm, powerpc, and mips developers hang out. Oh, and of course, there is also the freebsd-arm@ mailing list. -- Ian