From owner-freebsd-hackers Fri Apr 16 13:51:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (Postfix) with ESMTP id 589D3159C4 for ; Fri, 16 Apr 1999 13:51:13 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.2/8.9.1) id NAA43009; Fri, 16 Apr 1999 13:48:47 -0700 (PDT) (envelope-from mph) Date: Fri, 16 Apr 1999 13:48:46 -0700 From: Matthew Hunt To: The Classiest Man Alive Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Entombing for FreeBSD Message-ID: <19990416134846.A42425@wopr.caltech.edu> References: <199904161955.MAA59781@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from The Classiest Man Alive on Fri, Apr 16, 1999 at 04:26:18PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 16, 1999 at 04:26:18PM -0400, The Classiest Man Alive wrote: > For that matter, does it offer anything that a set of intelligent > scripts/wrappers for common destructive commands wouldn't give you? I hardly ever lose data. I don't alias rm or cp or mv or anything else, I'm just good at typing what I mean. But on the rare occasions that I do lose data, it's almost always because I overwrite a file inside an application or something like that, which aliasing commands wouldn't help with. I think the technology under discussion here does preserve overwritten data and would help. Matt, backing up as he types this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message