From: Nikita Danilov <Nikita@Namesys.COM>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jgarzik@pobox.com>,
"Albert D. Cahalan" <acahalan@cs.uml.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kentborg@borg.org
Subject: Re: Where is ext2/3 secure delete ("s") attribute?
Date: Fri, 22 Nov 2002 16:27:32 +0300 [thread overview]
Message-ID: <15838.12484.46897.60190@laputa.namesys.com> (raw)
In-Reply-To: <1037972308.11846.7.camel@irongate.swansea.linux.org.uk>
Alan Cox writes:
> On Fri, 2002-11-22 at 01:30, Jeff Garzik wrote:
> > Albert D. Cahalan wrote:
> >
> > > Forget the shred program. It's less useful than having the
> > > filesystem simply zero the blocks, because it's slow and you
> > > can't be sure to hit the OS-visible blocks.
> >
> >
> > Why not?
> >
> > Please name a filesystem that moves allocated blocks around on you. And
> > point to code, too.
>
> Anything on IDE or SCSI or Flash. Just its done below you
Journalling file systems also may leave copies of data in the journal area(s).
>
Nikita.
next prev parent reply other threads:[~2002-11-22 13:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 1:22 Albert D. Cahalan
2002-11-22 1:30 ` Jeff Garzik
2002-11-22 2:41 ` Albert D. Cahalan
2002-11-22 4:39 ` Jeff Garzik
2002-11-22 5:55 ` Albert D. Cahalan
2002-11-22 7:12 ` Ingo Oeser
2002-11-22 13:38 ` Alan Cox
2002-11-22 13:27 ` Nikita Danilov [this message]
2002-11-22 2:06 ` Mike Dresser
2002-11-22 14:13 ` Jesse Pollard
2002-11-22 21:31 ` Krzysztof Halasa
-- strict thread matches above, loose matches on Subject: below --
2002-11-24 6:40 Albert D. Cahalan
2002-11-21 18:20 Marc-Christian Petersen
2002-11-21 22:43 ` Harald Arnesen
2002-11-21 17:52 Kent Borg
2002-11-21 18:24 ` Jeff Garzik
2002-11-21 18:39 ` Kent Borg
2002-11-21 19:20 ` Alan Cox
2002-11-21 19:05 ` Kent Borg
2002-11-21 19:14 ` Jeff Garzik
2002-11-21 20:28 ` Alan Cox
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=15838.12484.46897.60190@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=acahalan@cs.uml.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=kentborg@borg.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®