Grafpup Live CD with Puppy 2.0 Save Settings File
 

I am fairly new to Linux, Puppy + am running the Grafpup live cd for the first time, also I am not of the computer generation so please make your reply easy to follow. I am currently running Puppy 2.0 with Opera as a live cd. I want to run Grafpup with Opera, as a live cd, for the first time. Since I want to retain my bookmarks + email settings from the Pup_save.3fs file on my "C" drive, when I run Grafpup live cd, will the settings in my Pup_save.3fs file incorporate into the Grafpup live cd? Will I then not have to configure the settings in Grafpup because Grafpup will just come up with my Puppy 2.0 settings? Thanks.

Hi :)

Welcome to the forum. I think I know what you are asking, but I may be wrong. Often am lol :D

If you have a copy of puppylinux as well as grafpup, there is no difficulty in saving both on the same computer, without overwriting, because they both have a different naming scheme or policy for the save file, although both are a container of an ext2 file system.

Puppy uses a pup_save.2fs name, which can have your own customised addition like pup_save216.2fs which I use to denote it is the one to use with Version 216 of PuppyLinux. You can change the name by renaming it, but not while it is in use. It then appears in the boot-up menu.

grafpup uses the grf_save.2fs save file naming concept.

Saying that, you will need to manually import settings unless Nathan has worked out a way of importing from one into the other.

Edit
I just copied a pup_save file and called it grf_save215Ez.2fs although I had doubts about whether it would work.

I then rebooted and selected the new save file from the menu. That worked.
I got a text log-in screen "Welcome to Grafpup-2.0!"
I typed xwin at the prompt, X loaded, but the ice menu wasn't there, just a couple of items.

There ya go! as expected.

So you will need to transfer stuff across. Bookmarks in the Mozillas are usually in a file called bookmarks.html and you will need to search for them. May be in a hidden directory (they have a . before their name). They can then be copied across. If you need help, I'll go looking for you and see what we can resolve.

Although someone else may have already done it.

Hope this helps.

Thanks Eagles-Lair. Although much of your reply is too technical for me to process, I think I get the basic concept you are trying to convey. I think I will just experiment with Grafpup on its own, with its own save settings file. If I want to try Puppy 2.16 (now using 2.0), upon bootup, Puppy 2.16 will incorporate my 2.0 save settings file so I can retain both, in combination, such is the theory. In case this cannot work, I am burning my Pup_save.3fs file so that I can copy it back. Again, thanks for your excellent reply.

You are right. Puppy 2.16 will incorporate your 2.0 save settings file.

In actual fact, the first time 2.16 loads, it will take longer as it will upgrade the system. Watch for a statement that will stay on screen for maybe 30 seconds, about where it has saved the old files. Move them somewhere else (into a new directory) in case there is anything after the upgrade that it is going to throw away. Like custom icons you've used etc.

This is important because the temporary directory it puts them into will get wiped when you reboot, and you will have lost them for ever.

You will note that while 2.16 normally saves in an ext2fs format, your save file will remain an ext3 - don't worry, it won't affect anything :)

A suggestion.
copy your pup_save.3fs file to another name, like pup_save_upgrade.3fs and that way you will still have your original version 2 configuration in case you have to go back to it.

If you don't do this, you are unlikely to be able to run your earlier version again :( The upgrade will change many things and break compatibility backwards (that's been my experience anyway).

A good product. Keep trying things out. If you keep a backup, then breaking it won't hurt very much :)

Thanks again eagles-lair. As I was mentioning, in case something goes wrong with the bootup of Puppy 2.16 live cd, I am backing up my Puppy 2.0 Pup_save.3fs file, as is, to another cd. In case of a problem, I can just copy it back to my "C" drive, then continue to use 2.0 with all my settings intact. Renaming the Pup_save.3fs file just takes up too much room on my "C" drive. So I will tryout Grafpup 2.0, on its own, then try Puppy 2.16 as I was mentioning above. Thanks again for confirming my thoughts on this matter.

An import wizard is a neat idea. In the case of Opera it would just have to mount the other save file and copy /root/.opera over. It would be even more handy if it could import settings from Windows:D .

Nathan

Thanks Nathan for participating in my newbie topic. I am not of the computer generation so every new computing attempt for me is a challenge. I just think that the entire Puppy concept, the fact that it can be run live from ram, that a user can save settings after each use, that it is manageable in scope is very impressive. I am anxious to try Grafpup because of its multimedia focus (I currently use the Gimp for Windows as my digital photography tool). There are too many distros, new versions have not much to offer to warrant being called a "new version". My main problem with Linux is installing new programs, can't quite figure out the jargon, the process. The PupGet, DotPup installers in Puppy, I think, are the easiest, although many program installs continue to confuse me. Why can't we just install like a ".exe" program? I want to keep on experimenting, learning, an excellent intellectual challenge. I will try to report on my Grafpup experience. All the best. Ken.

Ken, I missed your burning the pup_save to CD before. This is a very good idea and I did it when I started with puppy (version 2.01/opera and 2.02/seamonkey).

Experimenting with save files on machine followed on, and I discovered by accident it was possible to select which customised by menu , as it hadn't been documented where I was searching at that time.

The .pet concept is about as close as you are likely to get to a windows installer. I'm familiar with two other systems, which are similar in enduser practice, but not similar "behind the scenes".

The original impetus was given in the days of "Lindows" which became Linspire. They created Click-n-Run (now an acronym CNR) and that is being ported to several other Linuxes (Linuces??)

Slightly later, and in parallel development, in the Free BSD world, the .pbi concept started being developed, and the version of Free-BSD called PC-BSD came about with pbi being part and parcel of the development. We are currently working (slowly) on version 1.4 alpha there.

So don't despair!

People all over the place are pedalling their bikes as fast as they can go, to create working installers as effective as the MS Windows one. I don't trust Windows as an OS, but there are many good things that have been created within it :)

Hope that answers your last point.

If you want to PM me at any time, feel free. Just remember I'm not a nerd, guru, nor expert, just a retired fella in his 70s with too much time on his hands, lol.

Open Source is a great concept of self-help, too :) :D

Richard in Adelaide
capital of South Australia