On 6/7/2011 7:04, Invisible wrote:
> On 07/06/2011 02:47 PM, Darren New wrote:
>> On 6/7/2011 5:00, Invisible wrote:
>>> Still, why it can't build an image of what the final disk layout will
>>> look
>>> like in RAM and then write it all to disk in the most efficient order, I
>>> don't know. That's how I would probably do it.
>>
>> It's a removable disk.
>
> And?

And it has to be not completely corrupted if you remove it?

> Because it's a trivially easy optimisation?

Not really.  What happens if you have multiple processes writing to the disk 
at the same time?  You're looking at one specific use case, and complaining 
that the general tool isn't optimized for that use case.

-- 
Darren New, San Diego CA, USA (PST)
   "Coding without comments is like
    driving without turn signals."

Post a reply to this message