Date: Fri, 03 Mar 2000 20:47:57 -0600 (CST) From: Jim Bryant <jbryant@ppp-207-193-2-159.kscymo.swbell.net> To: rminnich@lanl.gov (Ronald G. Minnich) Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Copy-on-write filesystem Message-ID: <200003040248.UAA10045@ppp-207-193-2-159.kscymo.swbell.net> In-Reply-To: <Pine.LNX.4.20.0003031140080.921-100000@mini.acl.lanl.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
In reply: > On Fri, 3 Mar 2000, Michael Bacarella wrote: > > > Can someone tell me why copy-on-write filesystems would be bad? > > It's a good idea. Peter Braam and I have written a device (called memdev) > for linux (sorry!) that implements a virtual-memory-backed copy-on-write > block device (like the loopback device, but uses anon vm pages for store). > > It's pretty interesting. It's quite fast, and copy-on-write does seem to > work OK for a filesystem. I'm using this thing as one of two pieces of a > new private name space implementation that would also work quite well on > freebsd. Ever experience CDC Cyber NOS? Interesting private-space filesystem with many apps today. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ KC5VDJ - HF to 23cm KC5VDJ@NW0I.#NEKS.KS.USA.NOAM kc5vdj@swbell.net IC-706MkII, IC-T81A, HTX-202, HTX-212, HTX-404, KPC3+, PK-232MBX Grid: EM28px ------------------------------------------------------------------------------ ET has one helluva sense of humor, always anal-probing right-wing schizos! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003040248.UAA10045>