Gotta vent...
<SIGH>
WHY do browser writers insist they know more about the operating
environment than the user...?
Used Mozilla to download 9.2beta1 to *MY* choice of target disk (yup, I
finally have partitions available to test...); yet after over 300MB EACH
downloaded, cd1 bombed out for lack of disk space... wasted 330M of
bandwidth... :^PPPPPPPP
I KNOW WHERE there is enough disk space to d/l the 3 images, so I tell
Mozilla to d/l them there, yet the dumb fsck insists on d/l'ing to /tmp...
Lesseee..... Moz logic:
cd1 at 665M < available /tmp at 985M => fits!
cd2 at 664M < available /tmp at 985M => fits!
cd3 at 666M < available /tmp at 985M => fits!
so cd{1,2,3} *must* fit on /tmp...
Yeah, Right...! YUCH!!!!!
Since Moz is too dumb to realize that it should look at the SUM of the
downloads, I've also had to abort the cd3 d/l, hoping I can resume it via
ftp reget; otherwise, another 330M wasted bandwidth...
Better, if browsers would just *accept* the user's choice of d/l location,
we'd surely be happier... What's the point of d/l'ing to /tmp, only to
copy it to the final destination, when d/l'ing to the final location with
just a rename would suffice -- and avoid stupid design flaws like
forgetting to use the SUM of downloads... not to mention needing TWICE
the amount of disk space for ANY download!
</SIGH>
If there's a way to override this behaviour, it's not obvious and/or I'm
too pissed to find it...
Then, there were the failed downloads overnight... appears that
ibiblio.unc.edu removed the images during those downloads; yet, Moz
claimed "Finished" after ~20M each...
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
