Prev: iPad musings
Next: iPad ad
From: Jim on
On 2010-06-02, James Jolley <jrjolley(a)me.com> wrote:
>>>
>>> You didn't have to use onyx to do it, command plus option plus shift
>>> plus escape, held down would have managed this.
>>
>> James, Conor isn't an octopus. ;-)
>>
>
> See what you mean, but you can do the command option Shift bit with
> your right hand. It's an odd command granted, but imagine the amount of
> bloody VoiceOver commands i've had to just get on with and learn.

More to the point, if I understand it correctly then Secure Erase won't care
about how _many_ items you're erasing, but rather what their total file size
is. It's overwriting the actual file contents repeatedly, not just whatever
HFS+'s version of the File Allocation Table is. If the files were sizeable
it could very well take a long time.

Jim
--
Twitter:@GreyAreaUK

"If you have enough book space, I don't want to talk to you."
Terry Pratchett
From: Jim on
On 2010-06-02, James Jolley <jrjolley(a)me.com> wrote:
> I bet it took such a long time because of the size of the files. I
> think the secure empty does what the disk utility does when using
> secure erase, overwrites the files with 0's.

Yep. See my other reply. Metaphorically speaking.

Jim
--
Twitter:@GreyAreaUK

"If you have enough book space, I don't want to talk to you."
Terry Pratchett
From: Chris Ridd on
On 2010-06-02 17:07:00 +0100, Jim said:

> On 2010-06-02, James Jolley <jrjolley(a)me.com> wrote:
>> I bet it took such a long time because of the size of the files. I
>> think the secure empty does what the disk utility does when using
>> secure erase, overwrites the files with 0's.
>
> Yep. See my other reply. Metaphorically speaking.

It used to overwrite the file with random data, perhaps in multiple
passes. I believe srm(1) describes the algorithms.
--
Chris

From: James Jolley on
On 2010-06-02 17:09:51 +0100, Chris Ridd <chrisridd(a)mac.com> said:

> On 2010-06-02 17:07:00 +0100, Jim said:
>
>> On 2010-06-02, James Jolley <jrjolley(a)me.com> wrote:
>>> I bet it took such a long time because of the size of the files. I
>>> think the secure empty does what the disk utility does when using
>>> secure erase, overwrites the files with 0's.
>>
>> Yep. See my other reply. Metaphorically speaking.
>
> It used to overwrite the file with random data, perhaps in multiple
> passes. I believe srm(1) describes the algorithms.

Fair enough. Can see then for large files it'll take ages.

From: Jim on
On 2010-06-02, Chris Ridd <chrisridd(a)mac.com> wrote:
> On 2010-06-02 17:07:00 +0100, Jim said:
>
>> On 2010-06-02, James Jolley <jrjolley(a)me.com> wrote:
>>> I bet it took such a long time because of the size of the files. I
>>> think the secure empty does what the disk utility does when using
>>> secure erase, overwrites the files with 0's.
>>
>> Yep. See my other reply. Metaphorically speaking.
>
> It used to overwrite the file with random data, perhaps in multiple
> passes. I believe srm(1) describes the algorithms.

I think it's eight passes. On big files that could easily take a long, long
time.

Jim
--
Twitter:@GreyAreaUK

"If you have enough book space, I don't want to talk to you."
Terry Pratchett
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5 6
Prev: iPad musings
Next: iPad ad