RFC (fwd) Re: 5.3 tmpfs mount permissions

[Giorgos Keramidas]

On 2004-11-08 15:30, Giorgos Keramidas <keramida at freebsd.org> wrote:
> On 2004-11-08 13:47, Giorgos Keramidas <keramida at ceid.upatras.gr> wrote:
> > On 2004-11-08 12:01, "Simon L. Nielsen" <simon at freebsd.org> wrote:
> > > On 2004.11.08 12:51:20 +0200, Giorgos Keramidas wrote:
> > > > On 2004-11-08 02:50, Giorgos Keramidas <keramida at freebsd.org> wrote:
> > > > > Hi,
> > > > >
> > > > > Does the change outlined below seem like something I should commit?
> > > >
> > > > The patch posted previously had a few obvious bugs.  Here's an updated
> > > > version, which I have tested too :-)
> > >
> > > For consistency shouldn't the same be done for a /var MFS?
> >
> > You're probably right.  I saw varmfs near tmpfs in the rc.conf.5 manpage
> > and thought about adding varoptions="" to rc.conf too.  It's not very
> > difficult, now that I found out how to do it for tmpfs.
>
> Done, see below.
>
> Another tunable option that some users might find interesting at times is the
> softupdates support for the memory disks.
[...]

Hmmm, now that I look at the changes to mound_md() again, I don't like the way
it's headed.  Would it make more sense to add a tmpmfs_flags="" variable that
would surpass both the bytes-per-inode and the ones I tried adding?  This
introduces an incompatibility with the current state of mount_md(), but it's
easily extensible to include other options of mdmfs without having to invent
new funny ways of passing options to mdmfs through the rc.d scripts.