I have been using tahrpup, trying to do some developing on a puppy, and have been plagued by a save file.
Save files are a big nuisance.
Here you are developing along , and start to have problems getting it to work.
You don't even know you have a save file on the drive.
When it dawns on you that maybe a save file is the root of all you problems, you can't even find it on the hard drive.
How does puppy linux manages to find them, I'll never know.
How do you find a tahrpup savefile?
How to I find a savefile on a hard drive?
Its default location would be in the same location as your other puppy files (the base sfs, vmlinuz, initrd.gz and zdrv) unless you decided to save it in another location. Its file extension will be either .2fs, .3fs or .4fs. Also, If you did not install puppy to a specific directory all the puppy files would be in the root directory of your drive called /mnt/home. BTW - Always make a backup of your savefile if you are going to use one. There are also ways to operate puppy without a savefile, eg. saving your changes to an sfs file.
-
- Posts: 1543
- Joined: Mon 22 Feb 2016, 19:43
Re: How to I find a savefile on a hard drive?
Is that so?Lassar wrote:How does puppy linux manages to find them, I'll never know.
https://github.com/puppylinux-woof-CE/w ... init#L1202
Really only .2fs .3fs.4fs ?
I have you to know, that I have saved a .sfs made by ram2sfs .sfs file, as a backup.
It was on a different partition: Not on the boot partition.
And Xenialpup used that as a save file.
And on another time, Xenialpup grabbed the save file, even before I even got to the prompt.
Geez, does no good to choose pfix=ram, if puppy linux has already grabbed the save file.
And you wonder why I hate save files.
It was on a different partition: Not on the boot partition.
And Xenialpup used that as a save file.
And on another time, Xenialpup grabbed the save file, even before I even got to the prompt.
Geez, does no good to choose pfix=ram, if puppy linux has already grabbed the save file.
And you wonder why I hate save files.
Because you're a hillbilly, that's why!!!Lassar wrote:I have you to know, that I have saved a .sfs made by ram2sfs .sfs file, as a backup.
It was on a different partition: Not on the boot partition.
And Xenialpup used that as a save file.
And on another time, Xenialpup grabbed the save file, even before I even got to the prompt.
Geez, does no good to choose pfix=ram, if puppy linux has already grabbed the save file.
And you wonder why I hate save files.
Anybody who tries to offend a Puppy savefile will have to deal with me.
You got that, Lassar? You respect pupsave files or you find yourself
another distro. Are we clear about this?
If you have pfix=ram on your GRUB launch line, NO pupsave file is ever
loaded. Your problem has to be somewhere else.
What you describe is impossible.
If you're on tahrPup, if pfix=ram is NOT on your GRUB line, it will try to
find a pupsave file named tahrsave*.?fs and nothing else.
If you're on xenialPup, if pfix=ram is NOT on your GRUB line, it will try to
find a pupsave file named xenialsave*.?fs and nothing else. Puppies do
not inter-breed.
If you loaded your ram2something sfs file with sfs_load, what you
describe could be remotely possible. But nothing can ever be saved to
an sfs file.
Please inform yourself properly before speaking once more through your
hat? Thank you in advance. (One Pelo per forum is already too many...)
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Following Up
Hi Lassar,
I hated doors. You have to open them before passing their thresholds. Then someone taught me that doors come with knobs. I don't hate them as much.
As musher0 said, a Puppy will always use a SaveFile/Folder unless you've instructed it not to with a boot command. The boot commands which work are either:
kernel /vmlinuz ... pfix=fsck,ram
or kernel /vmlinuz ... pfix=ram
You can, of course, include other arguments on the "kernel" line. I just wanted to show the proper "ram" argument to use with pfix and to point out that if it is used with fsck, ram is separated from fsck by a COMMA and nothing else.
One other argument is valuable when working with SaveFiles/Folder. If you start with a Puppy's required files within a folder --rather than at the root/top of a partition-- Puppies will create their SaveFile/Folders within that folder. Consequently you can specify exactly where Puppy, on bootup, should look for a SaveFile/Folder. For example, if you placed Tahrpup64's files in a folder named "tahr64", your kernel boot line could look like this:
kernel /tahr64/vmlinuz psubdir=tahr64 pfix=fsck
psubdir=tahr64 tells Tahrpup64 to look for a SaveFile/Folder within the tahr64 folder FIRST.
If you haven't specified a folder, or located your SaveFile/Folder elsewhere, your Puppy will search every partition of every drive connected to your computer for a SaveFile/Folder; [unless, of course, you've used the pfix=ram argument]. So, if you have two or more SaveFiles/Folders which your Puppy could you, it will stop the boot process and present you with a list of all possibles PLUS NONE until you make a selection.
If you've created a "backup" SaveFile/Folder and want neither the boot process interrupted nor the backup accidentally used, you can place it where Puppy won't look. Puppy, in searching partitions only looks two levels deep: at a partition's root, and within the folders just below the root. A SaveFile/Folder placed in
/sdX/Puppy/Protected won't be discovered and offered.
mikesLr
I hated doors. You have to open them before passing their thresholds. Then someone taught me that doors come with knobs. I don't hate them as much.
As musher0 said, a Puppy will always use a SaveFile/Folder unless you've instructed it not to with a boot command. The boot commands which work are either:
kernel /vmlinuz ... pfix=fsck,ram
or kernel /vmlinuz ... pfix=ram
You can, of course, include other arguments on the "kernel" line. I just wanted to show the proper "ram" argument to use with pfix and to point out that if it is used with fsck, ram is separated from fsck by a COMMA and nothing else.
One other argument is valuable when working with SaveFiles/Folder. If you start with a Puppy's required files within a folder --rather than at the root/top of a partition-- Puppies will create their SaveFile/Folders within that folder. Consequently you can specify exactly where Puppy, on bootup, should look for a SaveFile/Folder. For example, if you placed Tahrpup64's files in a folder named "tahr64", your kernel boot line could look like this:
kernel /tahr64/vmlinuz psubdir=tahr64 pfix=fsck
psubdir=tahr64 tells Tahrpup64 to look for a SaveFile/Folder within the tahr64 folder FIRST.
If you haven't specified a folder, or located your SaveFile/Folder elsewhere, your Puppy will search every partition of every drive connected to your computer for a SaveFile/Folder; [unless, of course, you've used the pfix=ram argument]. So, if you have two or more SaveFiles/Folders which your Puppy could you, it will stop the boot process and present you with a list of all possibles PLUS NONE until you make a selection.
If you've created a "backup" SaveFile/Folder and want neither the boot process interrupted nor the backup accidentally used, you can place it where Puppy won't look. Puppy, in searching partitions only looks two levels deep: at a partition's root, and within the folders just below the root. A SaveFile/Folder placed in
/sdX/Puppy/Protected won't be discovered and offered.
mikesLr
-
- Posts: 1543
- Joined: Mon 22 Feb 2016, 19:43
Re: Really only .2fs .3fs.4fs ?
My guess is that Lassar booted a CD-R (one burn) and is trying to use the puppy splash screen to boot with puppy pfix=ram.Lassar wrote:And on another time, Xenialpup grabbed the save file, even before I even got to the prompt.
Geez, does no good to choose pfix=ram, if puppy linux has already grabbed the save file.
And you wonder why I hate save files.
- Attachments
-
- splash.png
- (3.81 KiB) Downloaded 405 times