/tmp, /var/log, /var/tmp as /dev/md - why?

[Ian Lepore]

On Thu, 2014-07-03 at 11:49 -0600, Warren Block wrote:
> On Thu, 3 Jul 2014, Ian Lepore wrote:
> > On Thu, 2014-07-03 at 12:55 +0200, John Hay wrote:
> >> On Thu, Jul 03, 2014 at 04:47:24AM -0600, Warren Block wrote:
> >>>
> >>> So a limited-size tmpfs will be faster and use less memory overall.  A
> >>> benchmark comparison would be interesting.
> >>
> >> Last time I looked the rc scripts that create /etc, /var and /tmp
> >> ramdisks only did it using md devices. It would be great if it was
> >> easily tunable from say rc.conf or if could detect which one is
> >> available and use that.
> >
> > I have patches ready to commit that do exactly that, but they weren't
> > exactly enthusiastically received when I posted them on arch@ for
> > review.
> 
> This thread?
> http://lists.freebsd.org/pipermail/freebsd-arch/2014-March/015141.html
> 
> Have not read it fully yet, but it sounds exactly right: everything acts 
> the same, the user can just pick tmpfs or mfs.

Yeah, that one.  I've reworked it this morning to incorporate the
earlier suggestion to avoid adding a FEATURE macro to indicate the
presence of tmpfs.  With today's changes it will work right if tmpfs is
either already in the kernel or available to load as tmpfs.ko.  I'll
attach the updated patchset in case anyone wants to test it.

The only blocker to committing it at this point is that the mdmfs(8)
manpage needs a lot of changes to become less md(4)-centric and more
about how it configures and mounts memory filesystems.  I'm not sure
when I'll find time for that.

-- Ian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mdmfs_tmpfs2.diff
Type: text/x-patch
Size: 7293 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-arm/attachments/20140708/ecda6885/attachment.bin>