From owner-freebsd-small Mon Nov 29 14: 9:37 1999 Delivered-To: freebsd-small@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 8114914E58 for ; Mon, 29 Nov 1999 14:09:33 -0800 (PST) (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 XAA23782; Mon, 29 Nov 1999 23:08:54 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Kim and Chet Golding Cc: small@FreeBSD.ORG Subject: Re: md - memory disk wishlist ? In-reply-to: Your message of "Mon, 29 Nov 1999 14:00:19 PST." Date: Mon, 29 Nov 1999 23:08:53 +0100 Message-ID: <23780.943913333@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Kim and Chet Golding writes: > >Great Question! > >1. Mirror or Raid mode would be very cool. For a memory disk ? >2. A cluster hook of some sort would be super if you had multiple systems >and could config/treat a memory disk as a single unit and let the unit >take care of passing updates to another system. (Maybe on boot this >could reload itself from another systems md based on a switch-file or >test-condition script in /etc... or after network was up.. failing over >to something in /etc/defaults if network is unreachable..) Uhm. This is a network filesystem, isn't it ? >3. Snap effect... Something like a .bak but with versions say up to 16 >working in a lifo manner. Would be good for some situations. Giving you >a version cache device for sql tables or floppy build versions. Hmm, that could be made rather simply I think. It's on the list. -- 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-small" in the body of the message