1 |
On Friday 15 February 2008, Dale wrote: |
2 |
> Alan McKinnon wrote: |
3 |
> > On Thursday 14 February 2008, Uwe Thiem wrote: |
4 |
> >> That aside, how would gaps *between* files ever translate into |
5 |
> >> fragmentation unless the author of that particular piece of |
6 |
> >> software managed to kill his very last brain cell? |
7 |
> > |
8 |
> > Oops. I had a brain fart there. |
9 |
> |
10 |
> You two are so funny. |
11 |
|
12 |
Thank you. We try to please :-) |
13 |
|
14 |
> I found this too: |
15 |
> http://www.oo-software.com/home/en/products/oodefrag/ Seems someone |
16 |
> is trying to make money. I have also read that most Linux file |
17 |
> systems do this automatically somehow. After doing my test, I tend |
18 |
> to agree. So why have a commercial product for this? Is it just |
19 |
> money? |
20 |
|
21 |
Yeah, pretty much just money. Microsoft's business model is to trap the |
22 |
market, never perform at any level higher than mediocrity, and create |
23 |
an ecosystem that needs thousands of support apps just to keep the OS |
24 |
limping along. Then shaft all of them with vendor-lockin |
25 |
|
26 |
Coping with file fragmentation has to be one of the easiest algorithms |
27 |
around, it isn't even hard. Write a file, and look to see how the |
28 |
blocks are distributed. If it can be improved, then do so. Otherwise |
29 |
leave it as is |
30 |
|
31 |
But then again, if you have written a file system so that everything is |
32 |
just mushed onto the same device, all higeldypigeldy with no sane |
33 |
structure at all ... then I suppose you would need stuff like defrag to |
34 |
come along once a week and save your ass :-) |
35 |
|
36 |
|
37 |
|
38 |
-- |
39 |
Alan McKinnon |
40 |
alan dot mckinnon at gmail dot com |
41 |
|
42 |
-- |
43 |
gentoo-user@l.g.o mailing list |