SLimpup is using isolinux 4.03 which has incompatibilities with some older machines (at least one of my test machines anyhow) and will not boot. replacing it with isolinux version 3.x (ie any version prior to 4.x) and set it as the boot image works great though.

Strange thing, Tried macpup on a USB drive whilst plugged into a relatively new notebook and guess what?? On shutdown the screen immediately goes blank and eventual shuts down without ever creating a savefile..

Ok I got to ask because this is killing me... Does the Prefix -- used often with a command/function have any specific meaning in bash? As I understand it after the function has run the -- will disable other options pertaining to that function to run and terminate the command cleanly. ie: --version, ...

Newest ISOLINUX 4.3 as used in puppy 5.2.5 hangs on first line of text echoed to screen and will not continue to successful boot. Equipment effected: Dell Inspiron 7500 Puppy 5.2.5 & Ubuntu 11.04 (and other distro's using Isolinux 4.x) A workaround is to replace the 4.x version of isolinux (and ...

The most efficient, effective and secure method I know of to clean any drive is to send an ATA Secure Erase command to the drive. Every modern drive's controller has this feature built in, just needs activating. This can be accomplished easily using PartedMagic from here http://partedmagic.com/doku....

looks like we're narrowing down the culprits, cool

One thing though, I had to pass on that great macpuppy, was just to heavy for this project. My latest issues with the i attribute have been with mijnpup, much lighter without enlightenment.

Clearly there are many variables involved. Under the above described test conditions the issue of prix=ram is 100% reproducible. Who knows, maybe it's related to the old machine I'm working with? maybe I should test the condition on another machine? Bottom line is there should not be an issue with b...

nooby wrote: the chattr +i command is used to protect the files on HDD ie the frugal install. chattr -i would unprotect them.

I'm sorry it was a typo but fixed now

The point about booting using pfix=ram to avoid the sfs file on the hard drive being booted from is an important point also raised. Thank you for you thoughts but may I suggest getting up to speed on this issue because it has been said several time already that pfix=ram does not prevent the core.sf...

I hear you however pfix=ram didn't work on my repeated efforts using various v5.x puppies. Every live cd I tried failed to boot using pfix=ram, although "pfix=nocopy" prevented the sfs files from being read at all. Maybe this only effects ext3 formating?

True there is great potential there too, but I think the dd commands would be less frustrating, at least the live cd would boot. a malicious hacker needs only to set the i attribute on the main sfs file of any frugal install and the system will not boot . Additionally a live cd will also not boot . ...

Still yet another snag since puppy fails to continue loading when the lupu_520.sfs is copied into memory where the kernal crashes attempting to create a layered file system.. Confirmed. Something has changed with the layered filesystem that prevents you from chattr-ing the main sfs file. It also le...

the chattr +i command is used to protect the files on HDD ie the frugal install. chattr -i would unprotect them. Still yet another snag since puppy fails to continue loading when the lupu_520.sfs is copied into memory where the kernal crashes attempting to create a layered file system.. Works great ...

The other issue is protecting the boot and pupy files because it appears that the chattr +i command can be reversed by anyone using the chattr -i command.. maybe this is dependent on which root user is using the chattr +i command? Just thinking out loud..

Success!!

The modified initrd file with and protected save file method as per this thread is a success, thanks rcrsn51

I really like Grub4Dos :) Grub4Dos helped make the configuration of a gfxmenu with a Frugal Install painless.. To be honest I couldn't find many posts with an efficient method to boot a Frugal install using Grub2 with a gfxmenu. Thanks to "mikeb" for adding his knowledge to the gfxmenu for...

Most (all?) applications will save by default to /root, so any user data would be lost on a reboot. But there are ways around this. In Firefox, you can move the hidden profile from /root/.mozilla to /mnt/home outside of the pup_save and replace it with a symlink. You could do the same thing with an...

The graphix menu worked like a charm on a full install, but since trying many puppies and settling on a mijnpup Frugal install I was temporarily baffled with combining gfxmenu to Grub4Dos and the alternative complexity of Grub2 booting a Frugal install.. Thanks to CatDude for all his hard word on th...

Q1 at every reboot puppy will overwrite the *save.3fs with the contents of *save.bak But what if the contents did not change? is the file overwritten regardless? Yes. The lines of code you added to the initrd don't check to see if the save file changed in the previous session. But it only takes a f...

Ok how about this one. in the /mnt/home/puppy520 directory i have two files (but others also) namely a *save.bak & *save.3fs Q1 at every reboot puppy will overwrite the *save.3fs with the contents of *save.bak But what if the contents did not change? is the file overwritten regardless? What abou...