>>>>> "p" == pixel <[EMAIL PROTECTED]> writes:
>> What went wrong? Disk space. The installation does not
>> properly estimate the required diskspace (it was out by over a
>> gigabyte) and when it runs out, ka-bam.
p> could you give the list of package you installed so that i can
p> reproduce exactly?
Sorry, you're right, it's an upgrade of 8.2; there were over 400 packages
in my list.
>> - XFConfig86 set my max resolution to 1024 when the prior
>> config was clearly 1152. Should be an easy fix.
p> yeah, easy to divinate your hardware ;p
Curious that the modelines for 1152 were all missing from XFConfig-4;
I added them and got my resolution back.
p> would you mind giving more information? (well if you want it
p> fixed of course)
The fix is really quite simple to state, but probably very difficult
to effect: the install program needs to check diskspace as it adds
each package, or have an exit strategy for when writing to the rpmdb
fails to ensure that the installation just stops adding packages or
pauses to alert the operator that the installation is in trouble.
more information is difficult since it's difficult to roll-back and
re-create the scenario. This suggests a new feature: Could we have
a utility in the pre-release distros that keeps a detailed log and/or
uses an optional network connection to spool the install log to some
other location?
--
Gary Lawrence Murphy <[EMAIL PROTECTED]> TeleDynamics Communications Inc
Business Advantage through Community Software : http://www.teledyn.com
"Computers are useless. They can only give you answers."(Pablo Picasso)
