Puppy Linux Discussion Forum

pri · Joined: 09 Oct 2009 Posts: 330 Location: Bandung Indonesia

thanks... pizzasgood now my puppy will be run, even it fat Very Happy

.

already have multiuser for easy use too ? Very Happy

lee321987 · Joined: 27 Apr 2010 Posts: 3

Hello.

Every time I do this (even tried using Pizzasgoods' patch file), the boot screen does this:

Pizzasgood · Posted: Tue 27 Apr 2010, 21:20 Post subject:

Turns out the problem isn't my changes. For Puppy 4.3.x, it looks like you need to use the -R option when running mkisofs. Otherwise the init script won't be able to locate the pup-431.sfs on the iso you build.

(Thank goodness for Qemu or it would have taken me about ten times as long to figure that out and verify it.)

gjuhasz · Joined: 29 Sep 2008 Posts: 120

I am happy to find this topic. The pfix=noram option is an ultimate solution if we have little RAM installed. Of course, Puppy becomes slower this case.

But...

What to do if you like some puppy variants, such as Bruno, but they are slow because you have 256 MB of RAM only? In my favorite distros, there are many nice-to-have packages (as parts of the distros' main sfs file) that could be better to lay in the hard disk. Per se, different users want different files to exile to the hard drive. How to replace a subset of files from the read-only sfs with links to the hard disk?

Don't try to move files from the sfs to the hard disk then put links in their original folder. Beyond response time and/or speed issues, Aufs/Unionfs punishes you with more RAM occupied.

A more complex but successful method to delete files from the read-only sfs (then replace them with links of course) is like this:

http://forum.eeeuser.com/viewtopic.php?id=71821 (I don't know whether this method has been applied for Puppies, please advise... I would prefer a simple "drag&drop" utility in the System menu for this purpose.)

A simple workaround is selecting a fat-free puppy then placing static packages (Skype, Zoiper, Opera52, Iron etc.) on the hard drive. This keeps the system being fast and prevents consuming RAM.

I know, dynamic sfs inclusion is well implemented in choicepup. I like it. Choicepup is very flexible, but unfortunately not too comfortable for some users such as my mother-in-low...

lee321987 · Joined: 27 Apr 2010 Posts: 3

What file do I need to put 'mkisofs -R' in?

gjuhasz · Joined: 29 Sep 2008 Posts: 120

Sorry Duplicate posted (How to delete a post?)

abushcrafter · Joined: 30 Oct 2009 Posts: 1447 Location: England

How do I have "pfix=noram" with the big puplets copy2ram fix: Barry Kauler Blog please?

Pizzasgood · Posted: Wed 02 Jun 2010, 00:19 Post subject:

I guess it would be the same as for 431, except for the final part. Instead of what I said before at the end, change the code like this:

lobo115 · Joined: 06 May 2010 Posts: 11

hello
I use it in lightpup but it appear a checksum error.
thanks

Pizzasgood · Posted: Thu 03 Jun 2010, 18:14 Post subject:

I'm going to need more information than you've given me. I'm not sure what you mean by "it appear a checksum error".

Like I said, I haven't tested this with anything newer than 4.3.1, so if Lighthouse Pup is based on something newer, it might not work. (I can play with Puppy 5.0 this weekend though.)

lobo115 · Joined: 06 May 2010 Posts: 11

hello thanks for your answer, i add the lines the problem is that when i try to boot it appaaer checksum error and i cant use it. Thanks

Pizzasgood · Posted: Fri 04 Jun 2010, 20:48 Post subject:

What things does it say before it says "checksum error"?

Which of the sets of directions did you follow?

abushcrafter · Joined: 30 Oct 2009 Posts: 1447 Location: England

Thanks. Back from holiday now so I will now test this out but first I need to find the doc on the commands to make the initrd.gz.

[Edit]Found this HowTo: Puppy Linux Discussion Forum :: View topic - Howto unpack, edit and repack initrd.gz.

abushcrafter · Joined: 30 Oct 2009 Posts: 1447 Location: England

When booting I get:

Pizzasgood · Posted: Sun 06 Jun 2010, 21:32 Post subject:

Huh. I just tested it with 5.0 and it worked here. (Well, I didn't verify that pfix=noram actually performed as advertised with this version, but I verified that it booted ok.)

It could be that something went wrong when you extracted and then rebuilt the initrd.gz file. Did you do it on a Linux partition? If you try to extract it on a Windows partition (like the outside of a USB drive) it will screw up stuff like file permissions. If you don't have real Linux partitions on your harddrives, you could still use the inside of your savefile, or the /tmp directory.