Puppy Does Not Load Saved Files

My Puppy does not load saved files.

Puppy is loaded on harddrive sda1. sda1 contains 4 different saved files for tahr64-6.0.5, including save-tom-1, save-tom-2.

I boot from the hard drive. I know I'm booting from hard drive right now because there is no usb or cd inserted into the computer and there wasn't when I boot up. I have to be in sda1.

root# blkid
/dev/sdb1: LABEL="CDROM" TYPE="iso9660"
/dev/sdb: LABEL="CDROM" TYPE="iso9660"
/dev/sda5: UUID="c71be305-376b-4e17-9cd4-86c31d59aa54" TYPE="swap"
/dev/sda1: UUID="8ae294bb-b247-4896-b93c-8011503c4892" TYPE="ext4"
/dev/loop4: TYPE="squashfs"
/dev/loop0: TYPE="squashfs"

root# fdisk -l (for sda1)

Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0000ce8a

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 304291839 152144896 83 Linux
/dev/sda2 304293886 312580095 4143105 5 Extended
/dev/sda5 304293888 312580095 4143104 82 Linux swap / Solari

root# fdisk -l /dev/sda1

Disk /dev/sda1: 145.1 GiB, 155796373504 bytes, 304289792 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

I've been a linux user for 10 years but I'm getting real discouraged with PuppyLinux. I've followed all the shut down menus and usually chosen the defaults.

I've never had a problem with any Linux distribution until Puppy.

I'm real tired of setting up Puppy everytime I boot up. So far I've spent over 40 hours trying to find the answer to this problem. Nothing works of everything I've read and researched. I am about ready to shoot Puppy.

So what I'm I doing wrong or what is wrong?

I would greatly appreciated any help. I can work from the command line..prefer it acutally.

Thanks..tinman

What's on the small extended partition /dev/sda2?

maybe start here

http://www.aztcs.org/meeting_notes/l...ux-install.pdf

Pete and Swan....thanks for responding.

Pete...it doesn't matter what is on sdb2...I took Puppy off the hard drive and went back to the Live usb.
When I exited the first time I set up a save file location on sda1. Puppy DOES SAVE the save file in the location. I verified it. The file is in the correct folder.

But on reloading it DOES NOT find the file. So I searched some more. Found one sources that said I needed to put "slocate:x:159:" into the /etc/group folder. I did that. Found another source that said I needed to put "slocate:x:114:root,spot,fido: into the same file. I did that. Verified that.

By the way there is already an entry in the /etc/group file for "mlocate:x:114:" .

Then I exited and rebooted. Puppy still DOES NOT load the saved file.

Two questions: 1) in /etc/group there is a "group" and a "group -" file. Is the 'group -" a backup? I put the entries noted above in both group files.

Second question: On bootup why does Puppy state "Searching for Save File" or something to that effect. Why is it searching if it already knows exactly where the saved file is?

Swan...I have already read your link, thank you. If a program is missing a vital piece of data or there is a bug in the software it makes no difference what you read if it doesn't not address the specific program you're having. Your link is good but it just describes the normal setup procedure.

Setting up Puppy is simple and easy. It's the little things like the problem I'm having that takes time to fix. What I don't understand is I can't be the first person with this problem so why isn't the solution posted somewhere easy to find?

Any other ideas based on this post?

thank again
tinman

maybe boot parameter: Psave /dev/sda1/< savefile>

Color Purple,

Thanks for your help. At first I didn't understand, to me, your cyptic message. Then I searched for puppy parameters and got that sorted out. There is a pfix for setting Puppy to ignore a saved file but none to tell it to load a saved file. I'm
assuming loading a saved file is default. Which would also mean something else needs to be set so it will load a saved file.

In regards to your Psave /dev/sda1/< savefile> are you telling me to boot to command line and entering that with <savefile> the name of my saved file? If so, is there a way to automate that on every bootup? Problem I see with that would be Puppy appends a -number to the saved file if there is already one present. Or will it just choose the latest saved file?

And another question...I've read on the forums there is a general feeling that the save,saved,saving files procedure could be improved.

Seems to me it would make more sense to make the Remaster method simple. Copy everything from / down and just over write the necessary file on your Puppy mounted location. Then when you exit Puppy could ask if you want to save and if you click yes it would do a simply remaster and an over write procedure. The entire code for saving a file, finding it and loading it would be eliminated would would probably speed things up overall. Just a thought.

Anyway, thanks again.

tinman

At the boot menu before puppy boots

Color Purple,

Thanks again.

I entered your suggestion several different ways. Nothing.
I read in a forum the parameters are case sensitive and you have a capital "P". So I thought that was the problem.
I would appreciate it if you put in quotes EXACTLY what I need to enter into boot to get Puppy to find the saved file.
By exactly I mean what needs to be entered as the paramater prior to the /dev/sda1/

There are over 200 views to this thread. Most of them would probably like to know as well....
Thank you.
tinman

apparently puppy has changed how things are done. Do you have a SAVEMARK text file with just the number 1 in it in your puppy folder with your vmlinuz and sfs?

maybe this will help: http://distro.ibiblio.org/fatdog/web...t-options.html

I doubt that link will be much use, TBH.

Although FatDog originated in the Puppy world, for several releases now it has been its own unique distro. These days, Kirk and jamesbond build it from the ground up, using LFS as a base.....it has very little in common with Puppy any more.

I've never heard of anyone having a problem like this before. I've been using Puppy for years, and, although usually I only ever have the one, single save-file at any given time (why so many? Any particular reason?), on the rare occasion I've wanted to choose between two different ones Puppy will simply ask you which one you want to boot. You make your selection, hit 'Enter', and away you go.

Don't ask me to explain the process, though. Although I'm active in the Puppy Forums, helping out newbies, trying out new 'spins' and releases, building the odd software package here and there (amongst other things), I have very little comprehension of the general boot/init process in Puppy. Even by Linux standards, Pup's considered 'odd'..!!

I know the use of multiple save-files can simulate the different user accounts in a true, multi-user system. Personally, with running a 'baker's dozen' of Puppies, I have enough trouble keeping on top of all those, never mind wishing to use multiple accounts for every one. I'm the only one who uses it; where would be the point?


Mike.

save-tom-1

is that the name of your saved file or is it tahr64save-tom-1?

not sure how accurate these are but may help.
puppylinux.org/wikka/BootParametersPuppy
http://www.murga-linux.com/puppy/viewtopic.php?t=35003

Yep. Back when I ran Puppy. You had to add pupsave options to show up during boot process as a choice from a text menu on a black screen.

rok_pupsave_1
rok_pupsave_2
rok_pupsave_3

or

rok_firefoxsave_1
rok_operasave_2
rok_libreofficesave_3

If I wanted to remember why I made that save file. Then type in the number 1,2,or 3 and load that save file on boot.

Been awhile though since I ran Puppy full time.

Link left
for good luck. Notv a spam link. Search engine link for Puppy Linux instead.

Edit. Not sure if frugal or full install was mentioned yet in this thread.