LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Does anyone know how to dual-boot Puppy 525 using LILO? (https://www.linuxquestions.org/questions/slackware-14/does-anyone-know-how-to-dual-boot-puppy-525-using-lilo-892388/)

psionl0 07-21-2011 12:43 AM

If you backed up slackware 13.37 using clonezilla then you have an easy way to restore the system to the way it was before you tried a full install of puppy 5.25. You can still use sda6 to copy the files from the puppy CD to as long as the partition is mounted when you use lilo.

Puppy just doesn't work as well when you do a full install. (For a start, you can't automount .sfs files when you boot up). Grub is just an unnecessary additional complication when you have lilo and the puppy files.

Robert.Thompson 07-21-2011 07:26 AM

Quote:

Originally Posted by psionl0 (Post 4420842)
If you backed up slackware 13.37 using clonezilla then you have an easy way to restore the system to the way it was before you tried a full install of puppy 5.25. You can still use sda6 to copy the files from the puppy CD to as long as the partition is mounted when you use lilo.

Puppy just doesn't work as well when you do a full install. (For a start, you can't automount .sfs files when you boot up). Grub is just an unnecessary additional complication when you have lilo and the puppy files.

Thanks psion, you are absolutely right! :)

I got so lost in trying to 'fix' lilo that I forgot all about my back up!!!!!:o :o :o

I do not know much about Puppy. I had read, in some 'install puppy post', that when you do a FULL install, you select DO NOT SAVE (the session) at the end of the install - that's why I did it that way.

Puppy has not 'asked' me to save the .sfs file since. Is that bad?

Are the other reasons not to do a FULL install? What am I missing out on?

Thanks again for the 'back up' reminder,


Edit: Found this -

Quote:

Full versus Frugal

When you do a full install, all of the data in the core Puppy files is extracted from the CD into a filesystem on your hard drive. Any software you install or files you save are added to the filesystem, so the total number of files and folders gradually increases.

In a frugal install, Puppy creates another file named pup_save.2fs. When you boot up, the filesystem stored in the core Puppy files is loaded into memory, but remains read-only. The pupsave file is used to hold all the new content you add. These two are merged together so it appears that you are working with a single filesystem. You get the effect of a full install while Puppy is running, but all you actually see on your hard drive are the core files and the pupsave.

The main advantage of a frugal install is that you always boot with pristine copies of the core Puppy files. If your install gets corrupted, it's just a matter of restoring the single pupsave file from a backup copy.

But what if your pupsave file gets filled up? Puppy has a utility for increasing its size. Or you can store content on your hard drive outside of the savefile, like you would with a full install.

Another advantage is the ability to put a frugal install almost anywhere. You can even stick it inside a full install of Puppy or another Linux. Or you can have multiple frugal installs in the same partition.
I guess I'll restore Slackware and then do a 'FRUGAL' install of Puppy.

psionl0 07-22-2011 01:18 AM

Quote:

Originally Posted by Robert.Thompson (Post 4421139)
I guess I'll restore Slackware and then do a 'FRUGAL' install of Puppy.

Cool! Just remember, copy the puppy files into your partition. Do not use puppy's "frugal install" tool or you will get stuck with all this grub business again.


All times are GMT -5. The time now is 02:42 PM.