Savefolder without 'mount -o bind' - works

[gyro]

Updated packages are now available for:

Slacko 5.7
http://www.fishprogs.software/puppy/slacko/initrd.gz
http://www.fishprogs.software/puppy/sla ... ko_5.7.sfs

Dpup Squeeze 5.X.3.4.12
http://www.fishprogs.software/puppy/squeeze/initrd.gz
http://www.fishprogs.software/puppy/squ ... 3.4.12.sfs

Dpup Squeeze 5.X.3.6.2.1
http://www.fishprogs.software/puppy/squeeze36/initrd.gz
http://www.fishprogs.software/puppy/squ ... .6.2.1.sfs

In each case:
1) Download both files.
2) Rename current 'initrd.gz' as a backup.
3) Move both downloaded files into directory containing the frugal install.
4) Reboot.

Note: As for the 'raring' implementation, the 'squeeze' zdrv acts like a ydrv.

gyro

[rg66]

Thanks gyro!

[gyro]

I have updated the following:
http://www.fishprogs.software/puppy/rar ... .9.9.2.sfs
http://www.fishprogs.software/puppy/sla ... ko_5.7.sfs
http://www.fishprogs.software/puppy/sla ... _5.9.3.sfs
http://www.fishprogs.software/puppy/squ ... 3.4.12.sfs
http://www.fishprogs.software/puppy/squ ... .6.2.1.sfs
http://www.fishprogs.software/puppy/tah ... hr_6.0.sfs
http://www.fishprogs.software/puppy/whe ... 5.2.11.sfs
They now contain the latest 'savefile2dir' version 1.2, http://murga-linux.com/puppy/viewtopic.php?t=96472

gyro

[Marv]

Testing in X-slacko-2.2.1n. Frugal install to CF card, pmedia=ATAFLASH, PUPMODE=13. The appearance of the 'save' dialog or not on shutdown does not track the RAMSAVEINTERVAL set in Puppy Event Manager and saved in /etc/eventmanager. Normal behavior would be that setting 0 would result in the dialog, anything else just a straight save with no dialog.

Looking at rc.shutdown, a variable ASKTOSAVE is present but not set. I added the following code at line 99 and the above behavior is obtained. May be a cleaner way to do this, just a suggestion.

Code: Select all

if [ $RAMSAVEINTERVAL = 0 ] ; then  #141118, Marv
  ASKTOSAVE=true
else
  ASKTOSAVE=false
fi

[mavrothal]

Looking at rc.shutdown, a variable ASKTOSAVE is present but not set.

Not in X-slacko currently but in Tahr/Slacko6 the ASKTOSAVE variable is set from the eventmanager > Save Session tab.
As soon as "Save interval" is set to "0" an 'ask to save' checkbox appears.

[Marv]

Looking at rc.shutdown, a variable ASKTOSAVE is present but not set.

Not in X-slacko currently but in Tahr/Slacko6 the ASKTOSAVE variable is set from the eventmanager > Save Session tab.
As soon as "Save interval" is set to "0" an 'ask to save' checkbox appears.

Thanks, that makes sense. For now I'll export it (set to false) from /etc/profile.local in X-slacko leaving rc.shutdown untouched.

[gyro]

I've done more testing of pupmode=13 in Wheezy 3.5.2.11, and have come up with 2 suggestions for extra patches for 'snapmergepuppy'.

Patch to tidy up symbolic link stuff:

Code: Select all

--- snapmergepuppy.orig	2014-10-06 18:01:55.000000000 +1000
+++ snapmergepuppy	2014-11-24 04:36:28.138255092 +1000
@@ -62,6 +62,7 @@
 
 if [ -L $BASE ]; then #we have savefolder based on symbolic links
  BASEMTP="/initrd${PUP_HOME}"
+ BASE="`readlink -n -m $BASE`"
 else
  BASEMTP="$BASE"
 fi

This is just an efficiency thing, since $BASE is used a lot in the following code, decode the link once here so the system doesn't have to do it lots of times later. I've no idea if it makes any significant difference.

Patch to fix saving of '/dev':

Code: Select all

--- snapmergepuppy.orig	2014-11-27 03:29:05.466244219 +1000
+++ snapmergepuppy	2014-11-27 03:17:33.000000000 +1000
@@ -143,6 +143,8 @@
 while read N
 do
 
+ [ "${N%%/*}" = "dev" ] && [ "${N:4:3}" = "tty" ] && continue
+
  #v4.01 graceful exit if shutdown X (see /usr/X11R7/bin/restartwm,wmreboot,wmpoweroff)...
  [ "$XRUNNING" = "yes" ] && [ -f /tmp/wmexitmode.txt ] && exit
 

This causes 'snapmergepuppy' to ignore '/dev/tty*'.
This should probably be done by modifying the 'find' line.
In Dpup Wheezy 3.5.2.11 with a savefolder using symbolic links, the partition was not unmounted cleanly. Omitting '/dev/tty*' from the file copy in 'snapmergepuppy' produced a clean unmount.
This does not make any sense to me. I fail to discern the connection. But it seems to work this way.
Interestingly Wheezy didn't seem to mind if I omitted '/dev' altogether.
Edit: Adding "|^dev/tty" to the list of exceptions on the first 'grep' on the 'find' line works, and is a neater solution.

Note: TahrPup 6.0 does not have this problem.

Since I'm already modifying 'init', I add an 'e2fsck' command in 'mnt_fnc', in my puppies.

gyro

[gyro]

I have updated the following:
http://www.fishprogs.software/puppy/rar ... .9.9.2.sfs
http://www.fishprogs.software/puppy/sla ... ko_5.7.sfs
http://www.fishprogs.software/puppy/sla ... _5.9.3.sfs
http://www.fishprogs.software/puppy/squ ... 3.4.12.sfs
http://www.fishprogs.software/puppy/squ ... .6.2.1.sfs
http://www.fishprogs.software/puppy/tah ... hr_6.0.sfs
http://www.fishprogs.software/puppy/whe ... 5.2.11.sfs
They now contain the latest 'savefile2dir' version 1.3, http://murga-linux.com/puppy/viewtopic.php?t=96472,
and the latest 'snapmergepuppy'.

Hopefully this is the last update.

gyro

[gyro]

Just in case it is useful to somebody, I have atached the real patch file for Dpup Wheezy's 'snapmergrepuppy' to omit '/dev/tty*' from the list of files to copy.
(It doesn't look very clear in the forum as "code" because the long lines wrap.)

gyro

[gyro]

Updated packages are now available for Slacko64 5.9.1:
http://www.fishprogs.software/puppy/slacko64/initrd.gz
http://www.fishprogs.software/puppy/sla ... _5.9.1.sfs

gyro

[rufwoof]

Could a savefolder be the slowest and most complicated full install ever

[gyro]

Could a savefolder be the slowest and most complicated full install ever

Definitely not a full install.
I can still do a "fresh install" by renaming a single file.
gyro

[mikeb]

And a fresh boot with a pfix=ram (or no changes= for slax)... for those floaty moments if say you want to partition or test or compile..

and cleanly load and unload sfs files.... and ...oh well

mike

[gyro]

And multiple puppies on a single partition.
And.....
gyro

[mikeb]

Its good to remember why we get our hands dirty in this stuff

mike

[rufwoof]

Interesting (at least to newbie me, likely not for you old hats )

Fresh puppy (frugal, ram booted). Copy /root to /mnt/puppy/sda4/root

#!/bin/bash
export HOME=/mnt/sda4/puppy/root
cd /
mv root root-orig
ln -s /mnt/sda4/puppy/root root

then restart x

Now all changes to app configurations etc. are stored in /mnt/sda4/puppy/root i.e. HDD (preserved).

I tried changing the gtk_theme, rebooted and the original theme seen, re-ran the above redirection code/script retarted jwm and the new theme showed.

[mikeb]

Well that sort of reproduces puppy 1 in a fashion which could only save part of the filesystem I suppose.

A save file or folder contains changes to all the system folders.

All this linking out of configs seems odd to me anyway...better to stop the configs being so large....and if yer system is a pile of links to a hard drive use a full install. ..not of puppy I may add cos thats not what its built for.

hairy knees

mike

[rufwoof]

Savefile/no savefile is all or nothing. With linking you have the flexibility of anywhere between the two. Modularity. My core puppy is minimal : leafpad (notes), galculator (calculator), mplayer (play/burn DVD's etc), Osmo diary/calendar etc. All booted from read only, so secure. That's expanded by a sfs load that adds in Libre Office (i.e. more advanced text editing, drawing, calculating) and Multi-Media (Openshot video editing, Blender 3D animating, Inkscape, Audacity sound editing), Again from read only medium so secure. Which is further expandable via adding in additional SFS's - Skype ...etc.

Switching (linking) enables either the fixed copy only to be used - or not, so for example load up Libre with its initial read only copy defaults, edit a document, shutdown, or for a pre-configured/adjusted version to be switched in (out), where that might be configured to particular non standard settings and where any changes to that configuration are preserved. Similar for browser. Option to use either the fixed read only copy, or switch to using a pre-configured one where the bookmarks etc from previous sessions are preserved. Most of the time I don't want any binaries/libs (core) changes to occur. The core works well and if changes/additions are required then I'll just make the changes and remaster a new core - typically infrequently. Most of the time I want application level changes to be preserved - if for instance I opt for a new choice of theme for Libre Office - typically more often.

The other factor is updates. When Libre Office is a sfs then swapping that out for another (usually later) version doesn't involve having to remaster. For instance my core puppy has no browser, so the browser used is whichever I select to load as a sfs (or download from Mozilla/wherever).

For online banking I typically boot the core read only copy, run a script that downloads the latest browser direct from the provider and surf to the banks web site using that - all 100% in (clean) ram, with no HDD's mounted. Afterwards I'll reset and load up a more general purpose arrangement that in having been more widely exposed is less secure.

With savefile (or no savefile) its all or nothing, binaries, libs, application configs etc. With linking its modular e.g. no save of bin's/lib's save of app's or ... whatever.

Sounds more complicated than it is in practice. For example for Osmo the CASE statement is

(Osmo)
cd ~
rm -rf ./.osmo
ln -s $APP_DIR/root/.osmo .osmo
/usr/bin/osmo &
exit;;

so any changes are preserved having been pointed to be the HDD version of the .osmo config files. So I either start Osmo via the normal Puppy menu, in which case (being ram booted with no save file) is the original default osmo settings where any changes aren't preserved, or I load Osmo via a gtk dialog list box, that pops up when a second taskbar button (red book) to the right of the main puppy menu button (green go button) is clicked that loads the version of Osmo where changes are preserved across reboots.

[mikeb]

I don't think this thread is the place to learn about your complicated lifestyle though well done for making puppys overstuffed menu even fuller ....

mike

[rufwoof]

I don't use "puppys overstuffed menu" that much, mainly my own secondary less-full menu.

I never liked the main puppy menu from the start personally, all the cryptic names that are pretty meaningless to newbie's, "Text editor", "Calculator" ...etc type menu's IMO are easier.

I can see the reasoning - guiding new users to learn app/program names by having those as the first part of each menu item, followed by a brief description of that that app/program does, but even now I seem to scan/search around the menu tree quite a lot when using things that I use less regularly.