From owner-freebsd-rc@FreeBSD.ORG Mon Nov 8 14:29:19 2004 Return-Path: Delivered-To: freebsd-rc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7807716A4CE; Mon, 8 Nov 2004 14:29:19 +0000 (GMT) Received: from telecom.net.et (sparrow.telecom.net.et [213.55.64.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BEC243D1D; Mon, 8 Nov 2004 14:29:16 +0000 (GMT) (envelope-from mtm@identd.net) Received: from [213.55.68.182] (HELO rogue.acs.lan) by telecom.net.et (CommuniGate Pro SMTP 3.4.8) with ESMTP id 62400441; Mon, 08 Nov 2004 17:21:58 +0300 Received: by rogue.acs.lan (Postfix, from userid 1000) id C1B20B851; Mon, 8 Nov 2004 17:20:19 +0300 (EAT) Date: Mon, 8 Nov 2004 17:20:19 +0300 From: Mike Makonnen To: Giorgos Keramidas Message-ID: <20041108142019.GA5922@rogue.acs.lan> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041108134132.GA38278@orion.daedalusnetworks.priv> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD/6.0-CURRENT (i386) cc: freebsd-rc@freebsd.org Subject: Re: RFC (fwd) Re: 5.3 tmpfs mount permissions X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to /etc/rc.d design and implementation. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 14:29:19 -0000 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 !