Hi.
Please, don't get confused. I just could re-activate my old RSH account.
sunburnt wrote:So many Puppy users that are a part of the community, and shouldn`t be minimalized or ignored.
Yes, this is especially true in the case of my work on the forum as well as of my work on LazY Puppy. Most of the time it has been a single German user who has made the testings as well as he did 'swallow' my 'treatments' on him while developing that whole bunch of ideas and programs.
Some might remember:
LazY Puppy 528-4, the first version ever, did already come with its SFS-Concept. It has loaded SFS-Suites (several programs in a category based/named sfs) directly by a script without to use sfs_load manually.
But:
It did not execute any application.
So, the basic idea, to refine the scripts to load the sfs first. and after that directly to execute the program was offered also by this single German user (incl. the LazY Puppy VarioMenu with hard work by himself and SFR)!
Meanwhile he did install it at his public school as main OS on 20 computers - Windows removed!
What I want to say, is: the problem is the goodness of Puppy Linux and Linux in general. The problem is on the developers side/hand.
The (Puppy Linux) developer decides what to do. If it doesn't fit into his needs he would probably not work on any suggestion made. Why should he care if it doesn't work for anyone else, as long as it works for him.
I did it and am still doing it that way!
And if I would be able to do all the things needed to be done, I would like to do the following:
- LazY Puppy architecture as the basic application handling (SFS-Concept)
- Restructuring the menu (Expert and User should be enough)
- Adding the ADRV-Concept for applications
- Adding the WDRV-Concept for Window Managers (so, the desktop sfs discussion would become real)
- Adding LazY Puppy's Personal Data SFS (this is not available in the 2.0.2-005 web version) (as mavrothal mentioned it is similar to something used in tiny core)
The above as a basic construction for each Puppy OS to produce.
Then there is some stuff in ArchPup (heard about it, did never checked) which is similar to some I did made over here for my private setup, like a file wherein are some settings defined for example like to set keyboard layout and/or path's etc.pp.
As far as I know ArchPup does this file somewhere in /root.
I do have this at boot partition, because my OS always knows its boot partition and boot directory. Using the above named file I do have directly access to files and directories at boot partition and directory inside a openbox menu pipe and am able to send them files to its related applications.
This is quite comfortable but might be too very special in front to reach/achieve common sense of a new/refined/changed development basement.
RSH (also known as R-S-H
)