Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 18 Oct 2019, 14:52
All times are UTC - 4
 Forum index » Taking the Puppy out for a walk » Announcements
If this goes through at woof-CE, let Puppy die.
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 3 of 3 [36 Posts]   Goto page: Previous 1, 2, 3
Author Message
musher0

Joined: 04 Jan 2009
Posts: 14407
Location: Gatineau (Qc), Canada

PostPosted: Mon 18 Feb 2019, 20:05    Post subject:  

666philb wrote:
just did a fresh 32bit buster build with the latest woofce testing, chose xenials kernel and keyboard, touchpad, wifi & sound are all working for me.

Hi Phil.

I'm glad you succeeded. Will you be keeping it to yourself or will you make
it available to Puppyists?

As I mentioned in the DPupBuster development thread, someone with more
experience and/or talent comes up with a version, I step back. My interest is
little-known WMs, not "woofing".

BFN.

_________________
musher0
~~~~~~~~~~
Je suis né pour aimer et non pas pour haïr. (Sophocle) /
I was born to love and not to hate. (Sophocles)
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 12734
Location: S.C. USA

PostPosted: Mon 18 Feb 2019, 21:04    Post subject:  

foxpup wrote:
I am not sure I understand correctly. It seems to be about updating and upgrading Puppy Shocked
What righteous Puppy-user ever bothers about updates? Maybe change a kernel, yes, but upgrade? I know some flavours offer it, but it is not really Puppy, is it?
If it works, it works. If you want something else you install another Puppy entirely.

And I do not see what it has to do with the Pupsave.
Please explain.

For years it has been possible to use a older save made in the same named Puppy version series.
Example:
A save made in Slacko 5.0 should be able to be used in Slacko 5.3 and 5.5 and 5.7 etc...... When it is used, it is updated to the newer Slacko version.
The update is about changing some identifying names, in the save, to say it is the save for the newer Slacko version.
It is code in the boot process that automatically does this.

It has always been stated that if the named Puppy version changes to a new series (Slacko 6.0) that no save from Slacko 5 series will work and a completely new save has to be done.

This is more about using an older save, that has a bunch of programs, settings, setups, etc..... in it and making it still usable in a newer version of that named Puppy version.
It has always been about, just how much has changed between the two Puppy versions.
If it is too much, the save is not going to carry over very well.

If I understand what they are saying about Woof-CE.
There are enough changes in the core Puppy processes, programs, setup, etc.... in a newer Woof-CE version.
That too much has changed in Puppy to be able to use a save that works in a Puppy that was made using a older version of Woof-CE.

_________________
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
YaPI(any iso installer) http://www.murga-linux.com/puppy/viewtopic.php?t=107601
Back to top
View user's profile Send private message 
mistfire

Joined: 04 Nov 2008
Posts: 1218
Location: PH

PostPosted: Tue 19 Feb 2019, 03:49    Post subject:  

In order to solve this issue just give the user an option whether to load save files or not if the WOOF versions are different.

UPDATE: wdlkmpx implemented that option
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 12734
Location: S.C. USA

PostPosted: Tue 19 Feb 2019, 08:45    Post subject:  

I hope he or they also but a big warning with it that this may or may not work.
The save is not 100% a sure thing to completely work.
For sure, anything in the save that is kernel specific, will only work with that specific Linux kernel.

_________________
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
YaPI(any iso installer) http://www.murga-linux.com/puppy/viewtopic.php?t=107601
Back to top
View user's profile Send private message 
foxpup


Joined: 29 Jul 2016
Posts: 949
Location: europa near northsea

PostPosted: Tue 19 Feb 2019, 10:16    Post subject:  

Thank you bigpup!
This I understand much better. Cool

I have not used a pupsave of one Puppy in another often.
I may do it between different RC's or between updates from peebee or mistfire.
I took installs with pupsave along when I migrated from my old machine to my 2 newer ones.
I never had much trouble with it.
I did not realise there was an update of the pupsave in the background. May have seen some note about it, now I think about it.
It is not possible I moved a pupsave from Tahr to Slacko? I thought I did one time.

But overall, it is nothing important to me, since I try to keep my pupsave slim, very slim.
I have most addons/apps 'outside' available for all or most Puppys and derivatives I run. Also some configuration like .mozilla.
I use Puppys mostly as they are.

This topic from shinobar should be mandatory reading for Puppy-users, shouldn't it:
Keep your savefile slim and healthy
I love the way shinobar uses the possibilities of Puppy. It's similar to what RSH does, I think.

Last edited by foxpup on Tue 19 Feb 2019, 15:00; edited 1 time in total
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 14407
Location: Gatineau (Qc), Canada

PostPosted: Tue 19 Feb 2019, 12:30    Post subject:  

mistfire wrote:
In order to solve this issue just give the user an option whether to load save files or not if the WOOF versions are different.

UPDATE: wdlkmpx implemented that option

Hello mistfire and all.

That's a wise move on the part of "wdlkmpx", IMO.

Except no Puppy dev has yet come up with code to improve pupsave
portability. AFAIK, pupsave portability is still limited to "same breed of
Pup, nearest up version".
-- same breed of Pup
(e.g. slacko to slacko, lupu to lupu, xenial to xenial, and similar.)
-- nearest up version (e.g. slacko-5.9 to slacko-6.0). If you go the other
way around, e.g. try to load a pupsave created in slacko-6 in slacko-5.9,
expect trouble.

I believe that a wider portability of pupsaves is what Puppy would need to
reduce frustration for users -- and retain them!

E.g. (that I know of), slacko-type Pups have the doc dir under /usr directly,
whereas Ubuntu- or Debian-derived Pups have it under /usr/share. Does
that pose a problem for portability? What other big differences are there?
Linux is Linux, no?

Also, IMO, the user should be able to incorporate such code in older Pups.
Like a "retrofit"; or the pupsave itself maybe could have code in some sort
of "header" or "footer" to manage its own portability?

IHTH. BFN.

_________________
musher0
~~~~~~~~~~
Je suis né pour aimer et non pas pour haïr. (Sophocle) /
I was born to love and not to hate. (Sophocles)
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 3 of 3 [36 Posts]   Goto page: Previous 1, 2, 3
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Taking the Puppy out for a walk » Announcements
Jump to:  

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


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1056s ][ Queries: 12 (0.0332s) ][ GZIP on ]