RAM FULL again
Posted: Tue 13 Oct 2009, 20:15
Today I downloaded the 4.3.1RC1 105MB and, whilst having a spot of bother getting an MD5 check, saved to DVD and rebooted ...
Oops, the dreaded RAM FULL message! OK, pfix=1, now back in business with 4.3.1RC1 on a new disk with most stuff saved, but a couple of questions:
If only I could suppress/hide that 105MB file (which I have belatedly copied to a spare hard drive, but cannot of course erase from the DVD) I could save the rest of the stuff en bloc. Is there a crafty way to kill it, using ISOmaster or otherwise?
Afterwards, <free> and me thought that there should have been loads of memory, if only my swap partitions had been engaged.
I suspect that the multisession boot process seeks to read saved sessions before enabling swap - is that right? If so, is reversing that order of events a practical improvement for the future?
Edit - should have specified - DVD-R
Oops, the dreaded RAM FULL message! OK, pfix=1, now back in business with 4.3.1RC1 on a new disk with most stuff saved, but a couple of questions:
If only I could suppress/hide that 105MB file (which I have belatedly copied to a spare hard drive, but cannot of course erase from the DVD) I could save the rest of the stuff en bloc. Is there a crafty way to kill it, using ISOmaster or otherwise?
Afterwards, <free> and me thought that there should have been loads of memory, if only my swap partitions had been engaged.
I suspect that the multisession boot process seeks to read saved sessions before enabling swap - is that right? If so, is reversing that order of events a practical improvement for the future?
Edit - should have specified - DVD-R