SOLVED: Any way NOT to load Puppy in RAM at boot ??

Using applications, configuring, problems
Message
Author
GeexBoxer
Posts: 17
Joined: Thu 22 Nov 2007, 17:35

#21 Post by GeexBoxer »

Pizzasgood wrote:It looks like if Puppy realizes you use an internal harddrive and that you have more than 280MB of ram, then it decides to ignore your wishes and copy into ram anyways.

If you really don't want it to, you could edit the initrd.gz file to adjust it.
I haven't tested this myself though, so there might be another line causing problems too. So let me know if it doesn't work and I'll look deeper.
First of all, thank you for writing very detailed instructions. I did what you told me to but puppy still copies to ram. btw I didn't create a pup_save file yet. could that be a problem? or maybe I should add pfix=noramsfs?

User avatar
Pizzasgood
Posts: 6183
Joined: Wed 04 May 2005, 20:28
Location: Knoxville, TN, USA

#22 Post by Pizzasgood »

Yeah, I think that the lack of a pup_save.2fs file might be the problem. I'm saying that from foggy memory, without looking at the code. There are a number of exemptions scattered around, and one of them had to do with the first boot.

I'll look into it tomorrow evening and try to get it working on my end.

It definitely isn't pfix=noramsfs. I just checked (using grep) and the string 'noramsfs' doesn't occur at all in the init script.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]

GeexBoxer
Posts: 17
Joined: Thu 22 Nov 2007, 17:35

#23 Post by GeexBoxer »

You are right Pizzasgood. It was the lack of pup_save file and now it is working. Thank you for your help, I appreciate it.

So the rough procedure was
1) edit initrd.gz file
2) adding "pfix=noram" to menu.1st file at the end of the kernel
3) make sure pup_save file exists.

Post Reply