Puppy Linux Discussion Forum

[rcrsn51]

[Indy'spup]

I know this is entirely user error lol plz bear with me here..

Fugal install to a ext3 primary partition. /mnt/sda1/puppy520 is the location of this installation when viewed and mounted using the macpup520 live cd

[Indy'spup]

WOW!!

I have no idea what I just did but rebooted to the fugal install and this time it's working, go figure..

brb

[Indy'spup]

Well, I managed to edit the the initrd file (still not sure how this was possible) but if a day of extraordinary effort didn't blow my mind then the next step will for sure...

lol


What is the significance of the Data directory?

[rcrsn51]

[Indy'spup]

Sorry was just coming back to that..

this data directory?

mount /dev/sda1 /mnt/data
cp /mnt/data/puppy431/pup_save.bak /mnt/data/puppy431/pup_save.2fs
umount /mnt/data

[sc0ttman]

rcrsn51 I like your approach.. Looks nice.. I think I have another method, any thoughts or ideas are welcome... It is not yet made, or tested, although I see no problems in making this a reality.

Anyway... Here's the method:

I plan to make a 'kiosk' (locked down) mode for puppy, by editing the initrd.gz and adding a new pfix option ('pfix=kiosk', of course)... Booting with 'pfix=kiosk' will add an entry into /etc/PUPSTATE (as I believe this is already done from the init script), that says KIOSK=true.

If KIOSK=true, the save interval in the Puppy Event Manager wil be forced to zero (no scheduled saves).. Also, rc.shutdown will be updated, so that it checks for kiosk mode in PUPSTATE and skips saving to the save file at shutdown.

I also have made a 'delaysave' pfix option, which simply forces PUPMODE 13 into PUPMODE 12 - which disables real-time saving to the save file. Kiosk mode, which must also force the 'delaysave' option, would create a locked-down puppy, that can be enabled and disabled at boot, regardless of which save file is being used.

This is much more complicated than your method, but I think it's really quite flexible, and I will give it a go! Just thought I'd share the approach that I was thinking of using, take it or leave it!

Hope I'm not invading the thread!

[Indy'spup]

The reason is that a /mnt/data directory doesn't exist in my fugal install. so I created one, ie: a data directory along with the nested directory puppy520, inside this I copied the file macpup_save.bak and edited the initrd entry accordingly.

only thing is (I know you guessed it!) the darn sav.bak file is never read or copied at boot time..

Must be related to it's location, which is why I wondered about the significance of the data directory.




I need to go back to square one I think.. and RTFM

[rcrsn51]

[rcrsn51]

[Indy'spup]

lol ok I understand I'm not looking in the correct places 90% of the time

sorry for hijacking the thread, maybe a moderator can move my posts back to my original thread..?


Meanwhile, is this a valid entry?

#######END MODULE LOADING TO ACCESS DRIVES##########

mount /mnt/sda1/puppy520
cp /mnt/sda1/puppy520/macpup_save.bak /mnt/sda1/puppy520/macpup_save.2fs
umount /mnt/sda1/puppy520


#########FINDING PUPPY FILES#############

[rcrsn51]

This is correct.

[Indy'spup]

OK thanks I'm going to give this a whirl now

[Indy'spup]

Oh Brother....!!

I must be missing something.. back to the manual!

lol

[Indy'spup]

I've been under the impression that puppy will load any save file which ends in .2fs now I'm not so sure of that criteria..

Am also not so sure it was wise to configure the puppy installation saved to the puppy save file prior to editing the initrd script..

Since I've not been successful in keeping the save file after a reboot I've commented out the changes in the initrd script until I can get puppy to load the save file previously created..


brb