(old)Puppy Linux Discussion Forum

Same topic at Additional Software » System:
http://www.murga-linux.com/puppy/viewtopic.php?t=76707

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-: 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.

PupsaveConfig home
Old topic

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.

Hi Shinobar,

As a tweaker I am of no help to this project. As a user I have a request for an option, that is to say

Most of the time I -do not want- to save session.

However, once you've saved a session every next time, it saves your session without asking if you "want to".

I've posted this before and sc0ttman came up with a tiny script which should fulfill my wish (however I do not know how to incorporate it).

http://www.murga-linux.com/puppy/viewto ... cdcdf83538

I think, but I am not sure, that he incorporated this feature in his "Puppy Arcade"

Looking forward.

nancy reagan wrote:Most of the time I -do not want- to save session.

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.



Or, use '-1' instead of '0'?
How do you think?

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: Launches and brief usage will be shown. 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.

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

Looks good to me.

Hi Shinobar,

I tested the above mentioned Pet in puppy-431 and found it is working OK.

charnisingh wrote:I tested the above mentioned Pet in puppy-431 and found it is working OK.

Thanks, charnisingh.
We are moving to next version and i appreciate if you also test the mockup.

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

Would this be a good time to make a backup of the pupsave file?

Maybe make it a simple option that you tick. Just a thought...

____________________________________________________

I've had the time to look through the app now, and I noticed some
spelling errors. So I made some pictures to show the words.
http://www.datafilehost.com/download-7abe7205.html

Also the word 'English' is supposed to have a capital... (I don't know why.)

I also included a design of a window in the situation when
the user is running low of free disk space.

Also when the user wants a password, wouldn't it be wise
to completely restrict the character set that is allowable?

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.

So I think it would be wise to state clearly in the password window
the following:

Choose your password from the following characters:

abcdefghijklmnopqrstuvwx 0123456789 and capital letters.

___________________________________________________

Thanks a lot for the kind correction, don.

don570 wrote: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!

I found a couple more errors in the windows.
I also show a design of a warning message if
the user uses a character that is restricted.
http://www.datafilehost.com/download-9df9bd36.html

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.


______________________________________________________

Thanks don. Your proposal sounds nice!

don570 wrote: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..

For North America yes, but most of the French speakers in Europe are still using AZERTY, seeing this forum i think.

I should have read all the entries but are in a hurry. Just wanted to second nancy reagan request that one have the option to not save too.

Sometimes one do things and realize it did not work and would be good to just delete it and start all over.

Now I try to achieve this by having a backup of pupsave in another directory.

But that is kind of much work to keep the backup updated.

Subject: Password entry

I think the best and safest way is to ask the user what
kind of keyboard he has.

There are 3 basic categories of keyboards,
QWERTY, AZERTY and 'others' As far as inputing the basic key
characters all QWERTY keyboards are the same except that "German'
keyboards switch the y and z. From reading on wikipedia I believe
all AZERTY keyboards are the same if one restricts input to
the basic character set.

Many Asians use a QWERTY compatible keyboard.

So I've designed a password window that I think is usable and safe.
Download it and see what you think.
http://www.datafilehost.com/download-e3a808ab.html


People who don't have a compatible keyboard are told to go 'Back'.
They could also be told to choose "Shutdown' or 'Reboot'
from the start menu and go through the legacy method of entering a
password.

Once a person chooses his password, the password has to be
examined for 'bad' characters, then the accepted password is transposed to
simple ascii characters appropriate for the encoding process.

In the case of the QWERTY keyboard this is a simple procedure because of
the restriction on y and z (Although I don't know about Asian keyboards...
you're the expert there)

In the case of AZERTY keyboards the transposing would be difficult but
not impossible. I'll give a couple of examples

France would be transposed to Frqnce
John55 would be transposed to John%%
Jacques would be transposed to Jqcaues

I think this can be hidden from user so he doesn't become
confused.

Pupsaveconfig would be successful in keeping most computer
users away from the console mode. That would be a great step
forward for Puppy linux.
_________________________________________________________

don570 wrote:France would be transposed to Frqnce
John55 would be transposed to John%%
Jacques would be transposed to Jqcaues

I think this can be hidden from user so he doesn't become
confused.

It can be a help for users to show what can happen.

This problem is not simple.
Well, we can manage as for the cases of North America and maybe of East Asia.
I'd like help of someone lives in Europe...

The encryption is recommended for the USB thumb drives.
We can carry it to another computers.

If you, don, carry the thumb drive on a trip to Europe, the problem may not be serious.
You can find qwerty keyboad in the internet café.
But some European may be able to manage the different kind of keyboard found there by chance.
Can be Belgian or Swiss, just my imagination.

In that case the safe characters are only the 20 alphabets and its upper case...

I hadn't thought about the situation a business or tourist who is
travelling from country to country where there is different keyboards.

So what I would do is explain this particular situation
to the AZERTY keyboard user, possibly giving him
an 'alternative' password to try in case of an emergency abroad.

But since the QWERTY keyboard is so dominant in the world,
I wouldn't even tell the QWERTY user about the problem. It would just
sow confusion in the mind. I am a North American so I know
how fragile the brain is.

___________________________________________________________

What if AZERTY keyboard user was to forget his 'alternative' password?

i.e. forget that France transposes to Frqnce,

That could be another great feature of Pupsaveconfig!!

Just input the password and click on button "Alternative Password'
in case of emergency abroad and France would be transposed to Frqnce.
Neat!
________________________________________________________________

Would it be easier to change the login script? It could first try what the user put in, then try to transpose it into QWERTY, then transpose the original to AZERTY format, and try that?

It would mean there are 3 different passwords that can get in, but it's still pretty safe.