From: Omen Wild <omen@vicinity.com>
To: linux-kernel@vger.kernel.org
Cc: "Richard B. Johnson" <root@chaos.analogic.com>,
Dan Maas <dmaas@dcine.com>, "Rose, Billy" <wrose@loislaw.com>
Subject: Re: ext3 and undeletion (libtrash)
Date: Mon, 25 Feb 2002 17:05:09 -0500 [thread overview]
Message-ID: <20020225220509.GY1916@frenzy.vicinity.com> (raw)
In-Reply-To: <05cb01c1be1e$c490ba00$1a01a8c0@allyourbase> <Pine.LNX.3.95.1020225125900.26412A-100000@chaos.analogic.com> <20020225184021.GA27211@matchmail.com> <20020225124953.M12832@lynx.adilger.int>
In-Reply-To: <20020225124953.M12832@lynx.adilger.int>
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
Quoting Andreas Dilger <adilger@turbolabs.com> on Mon, Feb 25 12:49:
>
> While I've seen this "change unlink in libc" suggestion many, many times
> I don't think I've ever seen it implemented.
libtrash does this: http://www.m-arriaga.net/software/libtrash/
I've never actually used it, but I've been meaning to look at it for
quite a while.
Omen
--
"What is this talk of 'release'? Klingons do not make software
'releases'. Our software 'escapes,' leaving a bloody trail of
designers and quality assurance people in its wake."
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
prev parent reply other threads:[~2002-02-25 22:05 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.n4lfl6v.h4chor@ifi.uio.no>
2002-02-25 17:06 ` ext3 and undeletion Dan Maas
2002-02-25 17:20 ` Mike Fedyk
2002-02-25 23:33 ` Tom Rauschenbach
2002-02-26 0:27 ` Bernd Eckenfels
2002-02-26 5:53 ` H. Peter Anvin
2002-02-26 16:05 ` Mike Fedyk
2002-02-26 16:31 ` H. Peter Anvin
2002-02-26 16:40 ` Mike Fedyk
2002-02-26 16:55 ` H. Peter Anvin
2002-02-26 17:12 ` Mike Fedyk
2002-02-26 16:36 ` Martin Dalecki
2002-02-26 16:43 ` Mike Fedyk
2002-02-26 16:54 ` Martin Dalecki
2002-02-26 17:05 ` Mike Fedyk
2002-02-26 17:07 ` Martin Dalecki
2002-02-26 17:16 ` Mike Fedyk
2002-02-26 17:22 ` Rik van Riel
2002-02-26 17:38 ` Mike Fedyk
2002-02-26 18:14 ` Andreas Ferber
2002-02-26 18:55 ` Andreas Dilger
2002-02-26 22:04 ` Mike Fedyk
2002-02-26 18:34 ` Richard B. Johnson
2002-02-26 18:34 ` H. Peter Anvin
2002-02-26 18:47 ` Richard B. Johnson
2002-02-26 18:52 ` Andreas Dilger
2002-02-28 15:05 ` Andreas Ferber
2002-02-28 22:37 ` Andreas Dilger
2002-02-28 22:55 ` James D Strandboge
2002-03-01 4:44 ` Mike Fedyk
2002-03-04 16:26 ` Pavel Machek
2002-03-05 21:29 ` Andreas Ferber
2002-03-06 11:30 ` Pavel Machek
2002-03-05 22:07 ` Richard B. Johnson
2002-02-26 17:22 ` Mike Fedyk
2002-03-01 0:19 ` Rick Lindsley
2002-03-01 1:02 ` Andreas Dilger
2002-02-26 17:54 ` Andreas Dilger
2002-02-26 18:24 ` Alan Cox
2002-03-04 15:40 ` Pavel Machek
2002-02-25 18:08 ` Richard B. Johnson
2002-02-25 18:40 ` Mike Fedyk
2002-02-25 19:49 ` Andreas Dilger
2002-02-25 22:05 ` Omen Wild [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020225220509.GY1916@frenzy.vicinity.com \
--to=omen@vicinity.com \
--cc=dmaas@dcine.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=wrose@loislaw.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox