From owner-freebsd-current Fri Dec 6 12:35:17 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA09919 for current-outgoing; Fri, 6 Dec 1996 12:35:17 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA09914 for ; Fri, 6 Dec 1996 12:35:15 -0800 (PST) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0vW6yT-0003wwC; Fri, 6 Dec 96 12:34 PST Received: from critter.tfs.com (localhost.phk.dk [127.0.0.1]) by critter.tfs.com (8.8.2/8.8.2) with ESMTP id VAA09957; Fri, 6 Dec 1996 21:35:36 +0100 (MET) To: Paulo Menezes cc: current@freebsd.org Subject: Re: mount_mfs In-reply-to: Your message of "Fri, 06 Dec 1996 20:23:42 GMT." Date: Fri, 06 Dec 1996 21:35:35 +0100 Message-ID: <9955.849904535@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> What I do is this: >> >> server:/somewhere/machine/root mounted ro on / >> server:/somewhere/machine/usr mounted ro on /usr >> server:/somewhere/machine/`hostname -s`/var mounted rw on /var >> server:/somewhere/machine/`hostname -s`/etc mounted rw on /etc >> server:/somewhere/machine/`hostname -s`/tmp mounted rw on /tmp >> >Ok, that is a solution! But what about mfs? I would not like to create a >/var /etc /tmp for each of the machines. The real question is can mfs be >used to create an empty ram-disk rw for /tmp? Well, mfs has no real speed advantage over any "real" filesystem since we got the share VM/buffer code, so I generally avoid it. Remember that it isn't really a mfs but more like a swap-partition-fs. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail.