Date: Mon, 8 Nov 2004 17:20:19 +0300 From: Mike Makonnen <mtm@identd.net> To: Giorgos Keramidas <keramida@ceid.upatras.gr> Cc: freebsd-rc@freebsd.org Subject: Re: RFC (fwd) Re: 5.3 tmpfs mount permissions Message-ID: <20041108142019.GA5922@rogue.acs.lan> In-Reply-To: <20041108134132.GA38278@orion.daedalusnetworks.priv> References: <20041108005007.GB57736@gothmog.gr> <20041108105120.GA952@orion.daedalusnetworks.priv> <20041108110105.GD756@zaphod.nitro.dk> <20041108114726.GA16509@orion.daedalusnetworks.priv> <20041108133051.GC24926@orion.daedalusnetworks.priv> <20041108134132.GA38278@orion.daedalusnetworks.priv>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 08, 2004 at 03:41:32PM +0200, Giorgos Keramidas wrote: > > 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. If we're using mdmfs from more than one place, then we need to do some re-factoring. If you don't have the time I'll be playing with diskless machines at $real_job soon, so I'll probably have time to look at it. Cheers. -- Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc mtm@identd.net | Fingerprint: AC7B 5672 2D11 F4D0 EBF8 5279 5359 2B82 7CD4 1F55 mtm@FreeBSD.Org| FreeBSD - Unleash the Daemon !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041108142019.GA5922>