From owner-freebsd-arch Tue May 29 14:43:49 2001 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 244FD37B422; Tue, 29 May 2001 14:43:43 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f4TLhZf33927; Tue, 29 May 2001 23:43:35 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org, arch@freebsd.org Subject: MFS gone... From: Poul-Henning Kamp Date: Tue, 29 May 2001 23:43:35 +0200 Message-ID: <33925.991172615@critter> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG MFS is gone now except from the newfs(8) manpage. If anybody better at mdoc than me would take on the surgical task of censoring that page I would be most happy. The command name "mount_mfs" is now available for use for other purposes like a md(4) based facility, I'm not happy about "stealing" a name from the mount_*(8) api for doing something which isn't really that. The opposite argument could be made successfully though, that by stealing the name we allow people to write something sensible in their /etc/fstab and then later when we get a _real_ memory filesystem, they will not have to fiddle it again. As usual I revert to the safety of "whoever writes the code make decisions as well..." -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message