Date: Wed, 20 Sep 2017 22:47:12 -0500 From: Jon Brawn <jon@brawn.org> To: Ian Lepore <ian@freebsd.org> Cc: FreeBSD Current <current@freebsd.org>, Warner Losh <imp@bsdimp.com> Subject: Re: Pre-filled RAM disk. Message-ID: <7CD79E48-F62E-46CC-896F-A9C87047B85D@brawn.org> In-Reply-To: <1505964913.73082.65.camel@freebsd.org> References: <AEDBF95D-5D91-41A0-AEFF-56840FAB755C@brawn.org> <CANCZdfqGk6euOtHrBjvd=L%2BC5uaEeYomcW1xEJwYDadzjW6G6A@mail.gmail.com> <CANCZdfrV5NaoOTTGUaXwaDXeoCcmjR3L1b9MnA6QF=__RUZanA@mail.gmail.com> <1505964913.73082.65.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 20, 2017, at 10:35 PM, Ian Lepore <ian@freebsd.org> 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 <imp@bsdimp.com> wrote: >>=20 >>> On Wed, Sep 20, 2017 at 8:50 PM, Jon Brawn <jon@brawn.org> wrote: >>>=20 >>>>=20 >>>> Wotcha! >>>>=20 >>>> <chomp> >>>> 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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7CD79E48-F62E-46CC-896F-A9C87047B85D>