[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Default number of overwrites in shred
From: |
Philip Rowlands |
Subject: |
Re: Default number of overwrites in shred |
Date: |
Sun, 6 May 2007 01:06:24 +0100 (BST) |
On Fri, 4 May 2007, Paul Eggert wrote:
Anyway, 'shred' currently does the first, but not the second, as it
doesn't verify what it's written. That should get fixed, no?
Is there a way to ensure reading directly from disk? On Linux I see only
a whole-system, root-level way to drop cached files [1].
Cheers,
Phil
[1] http://www.linuxinsight.com/proc_sys_vm_drop_caches.html
- Re: Default number of overwrites in shred, (continued)
- Re: Default number of overwrites in shred, Paul Eggert, 2007/05/03
- Re: Default number of overwrites in shred, Peter Eckersley, 2007/05/03
- Re: Default number of overwrites in shred, Jim Meyering, 2007/05/04
- Re: Default number of overwrites in shred, Peter Eckersley, 2007/05/04
- Re: Default number of overwrites in shred, Jim Meyering, 2007/05/04
- Re: Default number of overwrites in shred, Paul Eggert, 2007/05/04
- Re: Default number of overwrites in shred, Jim Meyering, 2007/05/04
- Re: Default number of overwrites in shred, Peter Eckersley, 2007/05/04
- Re: Default number of overwrites in shred,
Philip Rowlands <=
- Re: Default number of overwrites in shred, Pádraig Brady, 2007/05/06
- Re: Default number of overwrites in shred, Paul Eggert, 2007/05/08
- Re: Default number of overwrites in shred, John Cowan, 2007/05/04
- Re: Default number of overwrites in shred, Peter Eckersley, 2007/05/04