Date: Tue, 30 Aug 2005 08:57:50 +0200 From: Gunther Nikl <gni@gecko.de> To: Chuck Swiger <cswiger@mac.com> Cc: freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. Message-ID: <20050830065750.GA67835@lorien.int.gecko.de> In-Reply-To: <4312AEE0.8080806@mac.com> References: <200508282330.09302.dinom@balstonresearch.com> <20050829033739.GV26920@bunrab.catwhisker.org> <200508290213.12978.dinom@balstonresearch.com> <4312A9CD.8040008@freebsd.org> <Pine.LNX.4.53.0508282332420.20467@riyal.ugcs.caltech.edu> <4312AEE0.8080806@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 29, 2005 at 02:44:48AM -0400, Chuck Swiger wrote: > Jon Dama wrote: > >yes, that's quite generous. > > > >why isn't /tmp just an mfs mount though? > > While I like that suggestion personally, some people get perturbed about > files in /tmp going away if the power fails or you reboot. I wish mount_mfs would be smarter on post 4.x systems. Using mount_mfs means it works in compatibility mode. This might seem to be a good idea but it praxis it prevents tuning the mfs parameters: in mfs mode I can't set UFS version, I can't inhibit the .snap directory. Gunther
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050830065750.GA67835>