From owner-freebsd-stable Tue Jun 5 6:40:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by hub.freebsd.org (Postfix) with ESMTP id 9670E37B405 for ; Tue, 5 Jun 2001 06:40:15 -0700 (PDT) (envelope-from Jan.Grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Tue, 5 Jun 2001 14:40:03 +0100 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 3.16 #1) id 157H2g-0000yo-00; Tue, 05 Jun 2001 14:38:42 +0100 Date: Tue, 5 Jun 2001 14:38:42 +0100 (BST) From: Jan Grant To: freebsd-stable Subject: vn/md/mfs and 5.0-release Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If mfs is going the way of the dodo, I'd like to know how much work is going to be required to track stable across (say) the 5.0-release point. For instance, with a couple of lines in /etc/fstab /dev/ad0s4b none swap sw 0 0 /dev/ad0s4b /tmp mfs rw,nosuid,nodev,nosymfollow 0 0 I get a temporary swap-backed /tmp FS* recreated on boot. What is the new route to duplicate this kind of behaviour with md/vn-backed file systems? Is a line in fstab ever likely to suffice or am I going to have to write a small script to build the FS on boot? Cheers, jan * at least, it's always been my understanding that that's what this gives me. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287163 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk YKYBPTMRogueW... you try to move diagonally in vi. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message