big size puppy for small ram

For discussions about programming, programming questions/advice, and projects that don't really have anything to do with Puppy.
Post Reply
Message
Author
User avatar
pri
Posts: 342
Joined: Fri 09 Oct 2009, 18:31
Location: Bandung Indonesia
Contact:

big size puppy for small ram

#1 Post by pri »

puppy 4.3.1 is always copied sfs to ram, so ram it mustbe bigger than sfs.

the problem is i made some puppy and make it bigger than ram size. how to make it not copied to ram ?
pfix=noram not work, if work mybe it will be solution :D

i see an other puppy like tenpup that biger than ram size, but can run well on 128mb ram even it more time to boot up but its okey as long it work.
Learning by Doing

seaside
Posts: 934
Joined: Thu 12 Apr 2007, 00:19

#2 Post by seaside »

pri,

If your SFS file is bigger than the available ram, then the SFS file won't load in memory.

If you want to be sure that it DOES NOT load into memory (even if enough ram is available) then you need to change the puppy "initrd.gz" startup file, since the "NORAM" option has been eliminated.

I think you may have to change the "initrd" code. As I recall, it is set at around 230M.

If you search for "COPY2RAM" in the "initrd" file and then look further for a test for "RAMSIZE", you could change "RAMSIZE" to some lower number.

I'm not sure why you would want to do this, and maybe I don't understand the question.

Cheers,
s

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#3 Post by smokey01 »

If you had a Linux swap partition I believe this would be used like ram although slower.

User avatar
abushcrafter
Posts: 1418
Joined: Fri 30 Oct 2009, 16:57
Location: England
Contact:

#4 Post by abushcrafter »


User avatar
technosaurus
Posts: 4853
Joined: Mon 19 May 2008, 01:24
Location: Blue Springs, MO
Contact:

#5 Post by technosaurus »

the init in woof already has the fix I proposed in the thread abushcrafter posted - you can build the initrd.gz with woof and manually swap it out using isomaster (just make sure your versions match ... 431 on init requires 431 in the sfs in /etc/puppyversion and /etc/DISTROSPECS)
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].

User avatar
abushcrafter
Posts: 1418
Joined: Fri 30 Oct 2009, 16:57
Location: England
Contact:

#6 Post by abushcrafter »

technosaurus wrote:the init in woof already has the fix I proposed in the thread abushcrafter posted - you can build the initrd.gz with woof and manually swap it out using isomaster (just make sure your versions match ... 431 on init requires 431 in the sfs in /etc/puppyversion and /etc/DISTROSPECS)
oh I might do that for my remaster...

User avatar
pri
Posts: 342
Joined: Fri 09 Oct 2009, 18:31
Location: Bandung Indonesia
Contact:

#7 Post by pri »

build initrd.gz with woof ? i cant find it :D give me a clue :)
Learning by Doing

User avatar
technosaurus
Posts: 4853
Joined: Mon 19 May 2008, 01:24
Location: Blue Springs, MO
Contact:

#8 Post by technosaurus »

thus far the only way to get woof is to download bones from the quirky repo on ibiblio and follow the instructions at bkhome.org/bones ... AFAIK there are no snapshot tarballs or anything (I think there is a howto in the forum as well)
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].

User avatar
sunburnt
Posts: 5090
Joined: Wed 08 Jun 2005, 23:11
Location: Arizona, U.S.A.

#9 Post by sunburnt »

Same problem I had with MediaPup, it tried to load a 320MB SFS file into 256MB of ram!
If you don`t have a swap Puppy doesn`t account for that, not good...
The pfix=noram is tossed out and ignored during bootup. I had to hack fix it to make it work.

Post Reply