Deleting old sfs files

Message

Lancer · #1 Post by **Lancer** » Sat 16 Apr 2011, 03:59

I have made two different Puppy CDs (different programs installed) from the same original Puppy-Lucid 520.

My problem is that when I boot from either disk, they always show the same programs in my main laptop, even though I know the contents of the CDs are different (when I try them in other laptops, they aren't the same).

I'm guessing that the pup startup files are stored on my hard drive and are confusing Puppy, overriding the programs it things are on the boot disk.

So how do I locate and delete the puppy-buffer? I've been looking for lupup stuff on my hard drive and can't find anything. I think puppy might have put it in /dev/sda5 which is a swap partition (I normally use Ubuntu) and I can't seem to get in there.

Shep · #2 Post by **Shep** » Sat 16 Apr 2011, 04:24

Lancer wrote:I have made two different Puppy CDs (different programs installed) from the same original Puppy-Lucid 520.

You re-mastered your installation? wow!

Are you looking for .2sf or .sfs files?

Go to the command line, MENU >Utility >rxvt or similar, and to find the pathnames fo those pesky files, type:

find / -name '*.sfs'

(that's an asterisk dot sfs)

jpeps · #3 Post by **jpeps** » Sat 16 Apr 2011, 04:34

Sounds like it's loading a pupsave file. Try booting with pfix=ram.

Lancer · #4 Post by **Lancer** » Sat 16 Apr 2011, 05:36

Can't seem to find any other .sfs files, except for a few in build directories that is.

The pfix option sounds like the right idea, but neither ram, clean or purge made any difference.

jpeps · #5 Post by **jpeps** » Sat 16 Apr 2011, 06:18

hmm...somethings not right. If you boot pfix=ram, it wouldn't load any other files from the hard drive, and no SFS's.

#6 Post by **BÃ©Ã¨m** » Sat 16 Apr 2011, 06:35

Lancer,
Start with the beginning.
How did you create those CD's?
Please provide the detailed steps you took.

Lancer · #7 Post by **Lancer** » Sat 16 Apr 2011, 07:06

I think I more or less solved the problem now (see end) though why it works quite like it is, is still a mystery.

To make the CDs / USBs....

First, I made a bootable USB from the options within Puppy; USB flash creator. This worked and I had a bootable USB.
This enabled me to install various programs etc and get the USB flash drive to how I wanted puppy to look.
Then, booting from the USB itself I used the "remaster CD" program. to bake the current setup as a new ISO image on /dev/sda1 (my actual hard drive) as an ISO (did not burn a CD at this point). During this process, I added the directory /root/.pwidgets to the temporary setup because I realised that this file was typically forgotten by puppy and without it, changing desktop wallpaper (Nathan changer) was problematic. The remaster CD program asked for an original CD when I did this, although someone in the pigdin chat program assured me it wouldn't cause me to have an old image.
Now - the ISO image for a CD it made is correct. I have no problem booting from it in a new machine and seeing all my new programs. It's only when I boot from the machine which was used to create my images that I seem to see all the older programs (which aren't even on the CD anymore!).

Anyway - I found, sort of, what's happening. Because I'd used this laptop to make the CDs as ISOs, the result was some puppy_build folders on the /dev/sda drive which themselves contained lupu_520.sfs files. For some reason, when I boot from the CD, it seems to detect the presence of these folders and adopts their content (an older setup). What puzzles me now is why it would do this, even if I tell puppy to boot with the boot: puppy pfix=ram option.

After moving the build folders into other folders, booting from a CD takes longer and does load up with the correct files (the ones from the CD) in this machine.

#8 Post by **BÃ©Ã¨m** » Sat 16 Apr 2011, 07:44

The CD boot works that way.
In order to speed up booting it looks for lupxxx.sfs files and load them from HDD instead of CD.
So, delete them or rename them and see if the CD boots correctly now.

Lancer · #9 Post by **Lancer** » Sat 16 Apr 2011, 11:13

Yes, I can see that. I don't know why jpeps's pfix=ram option didn't work though.

#10 Post by **BÃ©Ã¨m** » Sat 16 Apr 2011, 11:28

What in your mind is a jpeps's option?
I am several years in puppy now and never heard about it.

glene77is · #11 Post by **glene77is** » Sat 16 Apr 2011, 11:59

Béèm wrote:What in your mind is a jpeps's option?
I am several years in puppy now and never heard about it.

Beem:

Quote/

jpeps
Joined: 31 May 2008
Posts: 692

EndQuote/

nooby · #12 Post by **nooby** » Sat 16 Apr 2011, 12:14

Lancer refer to this post above.
http://www.murga-linux.com/puppy/viewto ... 687#513687

Hahah glene77is beat me to it.

glene77is · #13 Post by **glene77is** » Sat 16 Apr 2011, 12:59

nooby wrote: Lancer refer to this post above.
http://www.murga-linux.com/puppy/viewto ... 687#513687
Hahah glene77is beat me to it.

#################
Nooby from Sweden:

I am very happy to see that you have continued to be part of the Puppy Group.

When I first saw your early postings in the forum,
I was fearful that you would become discouraged, and go away.
You were shooting for results and solutions everywhere,
like shooting at a rat in the dark forrest, HaHa

Stay in the forums, continue to help the Puppy-itos,
and you will learn to stay focused on one topic all the way to the end,
and then you will see the solution.

I frequently have three questions,
but I must focus on one question at a time.

Otherwise, this old man will wander around
still looking for the sunshine.

I like the Puppy distro very much,
because of the Squash File System,
and the compact code system.
But,

I still cannot find my way around the subdir system.
Maybe I need a 'road-map' into the garden,
so I can see more than just the first bushes in the garden.

Buena suerta,

jpeps · #14 Post by **jpeps** » Sat 16 Apr 2011, 17:40

Lancer wrote:Yes, I can see that. I don't know why jpeps's pfix=ram option didn't work though.

I think it needs to be "puppy pfix=ram"

#15 Post by **BÃ©Ã¨m** » Sat 16 Apr 2011, 17:50

glene77is wrote:
Béèm wrote:What in your mind is a jpeps's option?
I am several years in puppy now and never heard about it.
Beem:

Quote/

jpeps
Joined: 31 May 2008
Posts: 692

EndQuote/

OK realize now it is a user's name.

#16 Post by **BÃ©Ã¨m** » Sat 16 Apr 2011, 17:53

jpeps wrote:
Lancer wrote:Yes, I can see that. I don't know why jpeps's pfix=ram option didn't work though.
I think it needs to be "puppy pfix=ram"

Sorry about the confusion of your name.

pfix=ram is used when booting is done from grub.
puppy pfix=ram when booting from CD.

Lancer · #17 Post by **Lancer** » Sat 16 Apr 2011, 18:45

Yes, sorry for the name confusion; I was referring to when jpeps mentioned the boot options earlier on in this thread. The problem is now solved (by removing the build directories) but I was curious as to why jpeps's option didn't seem to work, as it does seem to be right on the ball. I was indeed using puppy pfix=ram (did not miss the puppy at the start as I saw this in the F2/F2 bootup help) in order to boot the CD, but there was no difference.

#18 Post by **BÃ©Ã¨m** » Sat 16 Apr 2011, 19:00

Yes Lancer, that's what I advised you

I explained also that pfix=ram or puppy pfix=ram doesn't prevent a puppyxxx.sfs from being loaded from HDD.

So that's why jpepps's advice didn't work.

jpeps · #19 Post by **jpeps** » Sat 16 Apr 2011, 19:59

Béèm wrote:
I explained also that pfix=ram or puppy pfix=ram doesn't prevent a puppyxxx.sfs from being loaded from HDD

It would think it should...that's the point of pfix=ram, after all. I just tried with a USB and CD, and it worked as expected.

#20 Post by **BÃ©Ã¨m** » Sat 16 Apr 2011, 20:05

(puppy) pfix=ram only prevents a save file to be loaded.
The base sfs is always loaded from HDD if one is there before looking elsewhere.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Deleting old sfs files

Deleting old sfs files

Re: Deleting old sfs files