The pupsaveconfig is now built in many puplets.
You can test the pupsaveconfig really working.

I know Barry made shutdownconfig and implemented it in Racy.
http://www.murga-linux.com/puppy/viewtopic.php?t=71911
The idea 'pupdialog' is nice, but i think the user interface must be different between keyboard base and the mouse in X.
I think my pausaveconfig is mature and it is time to release the stable.

Download pupsaveconfig-2.2.5.pet (2012-10-30)
(a bug is found in pupsaveconfig-2.2.4)
from http://shino.pos.to/linux/puppy/.
Install on any Puppy-4.x/5.x running with RAM only mode for precise test.
Think stable but still open for your feed back.

For pupplet developers:
If you want to, edit /usr/bin/pupsaveconfig for some ajustables at line 51-:

Code:

# adjustables
EXT4SUPPORT="yes" # EXT4SUPPORT="" to disable ext4 support ("yes" to support if available)
HIDEADVANCED="" # 'yes' to hide advanced file options, ''(null) to show all options
TIMELIMIT=120 # in second, time limit before shutdown
MINMB=64 # smallest savefile size in MB, to show smaller than 64
STDMB=512 # standard savefile size
MAXMB=2048 # largest savefile size in choice, to show larger than 2048

Warning on Puppy-43x and its derivatives:[/b]
The pupsaveconfig-2.0 makes ext4 internal file system of the savefile as the default if the kernel supports ext4.
The kernel of the Puppy-43x supports ext4 but the init script cannot read pupsave.4fs.
Solution:
Option 1 - Edit /usr/bin/pupsaveconfig and set EXT4SUPPORT=""
Option 2 - Update the init script in the initrd.gz to support pupsave.4fs.

INTRODUCTION
At the shutting down process after the first bootup of Puppy Linux, means without 'pup_save.2fs', it asks to create the personal storage file named 'pup_save.2fs' on its console. But it is not friendly to the users not familiar with Puppy.
PupSaveConfig is a GUI tool to setup the personal storage file, to customise the name of the file, where to save, password and etc. It can be done before going down to the console. One of the attractive idea is to launch the GUI at the BEGINNING of the first boot.
PupSaveConfig runs on X, and it is easy to internationalise like other Gtk programs. As for the multi-byte characters, most of asian languages, has the problem to display on the console (Think recent puppies cannot display non-ascii characters on console). But PupSaveConfig can.
A previous version of PupSaveConfig is embedded in the Japanese version of Puppy, Puppy Linux 4.20JP and 4.3.1JP. It is useful for Puplet (Puppy Linux derivatives) builders. It works on Puppy and puplets 4.x/5.x.

And as the new feature, the pupsaveconfig-1.9.x allows not to save session at shutdown for frugal install on flash.

WHATS THE NEXT
Next version of the pupsaveconfig should have more simple interface, all the settings at a glance.
Well documented help file, of course with translations.
I believe it shall be one of the key for the most user-friendly Puppy.
The test release is available above to see how the GUI works.

NEED YOUR HELP
Saving the session is the core feature of Puppy. Reliable work is expected.
The Puppy installation is very flexible, so the behaviour of the script is fairly complex.
Variety of the boot device, variety of the hardware, variety of the installation, some has multiple installation, etc. and etc.

TRANSLATION:
The pot file is at '/usr/share/doc/nls/pupsaveconfig/pupsaveconfig.pot'.
The help document is at '/usr/share/doc/help/C/pupsaveconfig.txt'.
You can place the translated help document at '/usr/share/doc/help/??/pupsaveconfig.txt', where '??' is your language code._________________Downloads for Puppy Linux http://shino.pos.to/linux/downloads.htmlLast edited by shinobar on Wed 14 May 2014, 21:00; edited 40 times in total

It was not the original scope of pupsaveconfig, but i know there is such a needs.
My proposal is to change the interpretation of the RAMSAVEINTERVAL written in /etc/eventmanager.

Current Puppy does: The saving is performed only by manual and automatically at shutdown if RAMSAVEINTERVAL=0.
My proposal: The saving is performed only by manual and never automatically even at shutdown if RAMSAVEINTERVAL=0.

Now attached the mock-up sample, pupsaveconfig2 v.1.9d.
Extract the gzip'ed file, place it at /root/my-applications/bin or anywhere with excutable permission.
From the virtual terminal, type:

Code:

pupsaveconfig2 --debug

Launches and brief usage will be shown.

Code:

# pupsaveconfig2 --debug
pupsaveconfig2 debug mode usage:
pupsaveconfig2 --debug # run as if pfix=ram
pupsaveconfig2 --debug cd # run as if cd boot
pupsaveconfig2 PUPMODE=3 # run as if full install
# You can set any valuables apear in /etc/rc.d/PUPSTATE
pupsaveconfig2 <variable>=<value> {<variable2>=<value2> ...}

PUPMODE=5
PUPSFS=sda3,ext3,/luci/luci-230.sfs

This mock-up makes a file /etc/rc.d/pupsave.conf as the result but does nothing more.
Can run on any Puppy 4.x/5.x.
No help documents, no tranlation at this point.

This sounds like a good idea. I've struggled with the
text based system that Barry has given us.

My first thought:

Is it possible that your PupSaveConfig window have some information
regarding empty space remaining in the partition where
the Puppy kernel is located and where I always store
my pupsave file. ...and maybe a warning message if
empty space is getting low.

A few things:
- when you select ext3, the save file text area still says .2fs (lupusave- *text area* .2fs)
- The installer doesn't check if there is - in the save file name. (maybe not allow the user to type it?)
- When you select 32 mb, the "Please Confirm" page still says 512mb

For example the German keyboard switches the position of
the y and z keys which I am told causes a great deal of confusion
during bootup.

Ah. I already said somewhere that i am only used to japanese and 'us' keyboards. They are the same layout as for the alphanumeric letters.

I realized now you nicely pointed out. QWERZ keyboard swaps y and z,
AZERTY both q/a and w/z, moreover, numerics are upper case instead of lower...
Then we can use only 20 alphabets! _________________Downloads for Puppy Linux http://shino.pos.to/linux/downloads.htmlLast edited by shinobar on Sat 06 Nov 2010, 23:18; edited 1 time in total

In my proposal I don't suggest that Puppy restrict the
keyboard that is being used or the keyboard layout.
Instead I propose that the characters that are inputed by the
user be examined and vetted i.e. evaluated.
I would suggest that once the user has inputed his
entire password and clicked 'OK' that the vetting or examination
process begin.

As well, aren't the French smart enough to deal with their bizarre keyboard
designs? French-Canadians (here in Canada) use a QWERTY design
keyboard which helps them avoid a lot of problems with software. During
the 1980's it allowed them to use text processors like WordPerfect
which was popular in North America..

A huge number of people in Central Europe (including non-Germans)
use the German design of keyboard which is why I suggest
restricting the use of y and z albeit many Germans I'm sure know the problem
exists and can deal with it.

But if their password didn't have a y or z then they could bootup in the
'Legacy' mode and be guaranteed no hassles.

As well, aren't the French smart enough to deal with their bizarre keyboard
designs? French-Canadians (here in Canada) use a QWERTY design
keyboard which helps them avoid a lot of problems with software. During
the 1980's it allowed them to use text processors like WordPerfect
which was popular in North America..

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum