Hello,
I'm using Puppy Linux 4.31 frugal install. I have Eee PC 4G with 3.8 Gb HDD and 512 Mb RAM. How can I make pup-431.sfs not lo load to RAM at bootup, but load from the hard disk instead?
I know that loading from RAM speeds up the working process, but I had such an experience when I had to convert some audio files in Puppy and it ate my save file to 0, so I couldn't boot any more and had to reinstall the save file again.
As a matter of fact, I'd like to load everything (incl. the main sfs-file, other sfs's and the save file) from HDD and make very little RAM in use. Or then return back to the default mode if this works out worse.
How can this be done?
Thank you.
How to make Puppy not to load pup-431.sfs to RAM?
Thanks for such a quick response.
But I prefer to have a small save file (as small as 32-64 Mb for now), because it's very easy to reinstall then and because I use very little additional apps.
And frugal install in much better for me, as I can use sfs-modules.
I mean - is there a cheatcode opposite to "pfix=ram", something like "pfix=hdd" or whatever?
But I prefer to have a small save file (as small as 32-64 Mb for now), because it's very easy to reinstall then and because I use very little additional apps.
And frugal install in much better for me, as I can use sfs-modules.
I mean - is there a cheatcode opposite to "pfix=ram", something like "pfix=hdd" or whatever?
The cheatcode is puppy pfix=noram.Cyril wrote:Thanks for such a quick response.
But I prefer to have a small save file (as small as 32-64 Mb for now), because it's very easy to reinstall then and because I use very little additional apps.
And frugal install in much better for me, as I can use sfs-modules.
I mean - is there a cheatcode opposite to "pfix=ram", something like "pfix=hdd" or whatever?
Not sure it works though.
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
Re: How to make Puppy not to load pup-431.sfs to RAM?
Maybe pfix=noram is the user defined variable, which Puppy recognizes, which means; 'don't use a pup_save file'Cyril wrote:Hello,
<text cut>
How can this be done?
Thank you.
(I suspect so based on the behavior of 4.00)
I changed the 'init' file inside initrd.gz to make it so the pup_400.sfs file would never be copied to RAM.
In answer to your question:
1) expand the contents of initrd.gz
2) modify init at the place where Puppy makes the decision if it will copy pup_xxx.sfs to RAM.
I spoofed the variable to show a machine that only has 128MB RAM.
The reason being: Puppy doesn't copy the .sfs file to RAM on a machine with 128MB RAM.
3) pack initrd.gz and use it with the modification
~
Thanks guys, I also found some instructions by chance:
http://www.murga-linux.com/puppy/viewtopic.php?t=24899
http://208.109.22.214/puppy/viewtopic.p ... e9953f5bfa
But hacking initrd.gz and then adding "pfix=noram" only gave me a kernel panic... Well, I also got the new Quirky 1.00 because it has FFconvert and I'll try to do all the "dirty" work there.
http://www.murga-linux.com/puppy/viewtopic.php?t=24899
http://208.109.22.214/puppy/viewtopic.p ... e9953f5bfa
But hacking initrd.gz and then adding "pfix=noram" only gave me a kernel panic... Well, I also got the new Quirky 1.00 because it has FFconvert and I'll try to do all the "dirty" work there.