From owner-freebsd-hackers Wed May 31 17:14:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.avantgo.com (ws1.avantgo.com [207.214.200.194]) by hub.freebsd.org (Postfix) with ESMTP id 249FA37B935 for ; Wed, 31 May 2000 17:14:08 -0700 (PDT) (envelope-from scott@avantgo.com) Received: from river.avantgo.com (river.avantgo.com [10.0.128.30]) by hermes.avantgo.com (Postfix) with ESMTP id 5AE3C20; Wed, 31 May 2000 17:14:08 -0700 (PDT) Date: Wed, 31 May 2000 17:14:23 -0700 (PDT) From: Scott Hess To: Michael Lucas Cc: hackers@FreeBSD.ORG Subject: Re: Proper uses for MFS? In-Reply-To: <200005251705.NAA67491@blackhelicopters.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 25 May 2000, Michael Lucas wrote: > I'm writing an article on Memory File System, just because I think > it's massively cool. > > We had a thread some time ago on why MFS wasn't useful for certain > applications. I searched through the mail archives, and found lots of > things MFS wouldn't be right for, but not much of the other way around. > > What are some good, reasonable use for MFS nowadays? I've used it to store lockfiles in a simple database server. There are a variety of fast alternatives I could have used, but none of them were nearly as simple as using filesystem operations. MFS makes the simple implementation more than fast enough that I don't care to do the extra work... Later, scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message