Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.vbc.net!samba.rahul.net!rahul.net!a2i!news.PBI.net!news.mathworks.com!fu-berlin.de!cs.tu-berlin.de!unlisys!news.bb-data.de!news From: mib@ppe.bb-data.de Newsgroups: comp.unix.bsd.netbsd.misc Subject: Re: NetBSD-1.1 Memory File System Date: 07 Aug 1996 11:52:40 +0200 Organization: BB-DATA GmbH, Berlin, Germany Lines: 9 Sender: mib@LOSIRA Distribution: inet Message-ID: <uivavldw7.fsf@ppe.bb-data.de> References: <4ts8g2$n92@inet-nntp-gw-1.us.oracle.com> <4u36as$gbs@colwyn.owl.de> <6EHUjvqZo$B@rimki.toppoint.de> <4u7ogq$g7h@innocence.interface-business.de> <4u877j$dml@peippo.cs.tut.fi> NNTP-Posting-Host: 10.11.4.39 X-Newsreader: Gnus v5.3/Emacs 19.32 k125374@korppi.cs.tut.fi (Mika Kortelainen) writes: > Hmm, what is it used for then? If it were a "ram disk", I'd > understand (and use it because it would of course be > faster for e.g. temporary files during compilation). It is a RAM disk as long as enough RAM is available. If memory becomes sparse, mfs is paged just as everything else is. So you get the best of both worlds: speed and flexibility.