From owner-freebsd-fs Thu Aug 12 3:47:27 1999 Delivered-To: freebsd-fs@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.41.238]) by hub.freebsd.org (Postfix) with ESMTP id A495914FDF for ; Thu, 12 Aug 1999 03:47:24 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id LAA00331; Thu, 12 Aug 1999 11:05:34 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Patrik Sundberg Cc: freebsd-fs@FreeBSD.ORG Subject: Re: mfs and imagefile (/usr/src/sbin/newfs/mkfs.c) In-reply-to: Your message of "Tue, 10 Aug 1999 16:32:45 +0200." <19990810163402.B10448@radiac.sickla.raditex.se> Date: Thu, 12 Aug 1999 11:05:33 +0200 Message-ID: <329.934448733@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >We asked Andrzej Bialecki(picobsd) about it and he too thought the -F flag was >the way to accomplish this, but later came to the same conclusion as we did. The -F flag was added because we didn't have a working vn(4) at the time and Jordan and I were sick and tired of make release falling over because of sick floppy disks. It works the opposite of what you want: it preserves the contents of the MFS after you unmount it. Feel free to add code for what you suggest, but make it read the input from a filedescriptor so that I can gunzip < mfs.image.gz | mount_mfs ... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message