From owner-freebsd-hackers Sun Jul 30 13:36:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 6724A37B7A9; Sun, 30 Jul 2000 13:36:10 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Sun, 30 Jul 2000 16:36:03 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Michael Bacarella Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: /tmp on a ramdisk? In-Reply-To: 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 Sun, 30 Jul 2000, Michael Bacarella wrote: > This is more out of curiousity than criticism; > > ..but why not just make a charecter device that corresponds to a chunk > of VM and simply run newfs on that? > > You would still have a relatively proven filesystem (like FFS) and you > also get the "benefits" of having it memory resident. Perhaps certain > properties of FFS would be less than ideal for this, but you get the idea. > > Wouldn't this have the same problems as mfs but still avoid existing as a > seperate filesystem (and thus, a seperate code base)? This avoids certain MFS problems, yes. Please see vnconfig(8) =) > -MB -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message