Used save from BookwormPup64 10.0.8 as save for v10.0.9 and v10.0.10

[bigpup]

Did a frugal install of BookwormPup64 10.0.9

Did a frugal install of BookwormPup64 10.0.10

Copied the save folder from frugal install directory of BookwormPup64 10.0.8 and placed it in the other frugal install directories.

Note:
Could also use the save from v10.0.9 in v10.0.10
That would get you what you had installed in v10.0.9

First boot using this save, did need to do some changes, so it is now setup for the newer version frugal install.
All of it was done automatically, during the boot process.
Just took a little longer to boot.
(does at times look like nothing being done, but it is doing what is being reported)
Nothing I had to do, but watch it report what was going on.
Booted to working desktop.

Seems to be working OK.

This older save was made for the same computer.
So all config setups, changes, etc... are working OK.

So, seems OK to use an older bookwormPup64 version save, with a newer version of BookwormPup64.

Note:
Anything you had in the old save that is kernel specific, is probably going to have to be replaced for the kernel in the newer BookwormPup64 version.
All versions use a different kernel.

I have the Nvidia driver package installed which is kernel specific.
This seems to be automatically getting changed to the specific kernel, now being used, in the specific BookwormPup64 v10.0.9, v10.0.10.
So not having to redo the Nvidia driver install.
Maybe DKMS feature is doing this auto change.

update info:
I did have in the old save, some SFS additional files being loaded (devx and kernel sources), that were specific to v10.0.8
So did need to unload them.
Download and load the devx and kernel sources SFS's specific for the now being used version.

[mikewalsh]

@bigpup :-

Yah, I remember this from radky's first DPup build a few years ago, Bigs.....DPup Stretch. So long as you were running it on the same hardware, the upgrades through rc3 -> rc4 -> rc5 worked perfectly with the existing save-file/folder. And this was "early days" for the 'portable' eco-system, too; everything carried on working even back then.....they're a bit more streamlined & simpler to use now than they were.

I've just 'upgraded' my frugal of 10.0.8 to 10.0.9. I'm not gonna test ATM, 'cos I'm now turning in for a few hours, but I have every confidence it'll fire straight up when I try it later on today.

Will confirm back here when I do.

Mike.

[mikewalsh]

@bigpup :-

Running smooth as silk. Upgraded from 10.0.8 to 10.0.9, and using the existing save-folder.

Just took a wee bit longer to reach the desktop, that's all. Looking good.

Portables all working fine, so far.....haven't got 'em all linked in yet, mind you. We shall see.

Mike.

[bigpup]

see update to the note: in first post.

[Governor]

see update to the note: in first post.

It seems far too complicated for me to "upgrade" to Bookworm 10.0.9 version. Why is it called an upgrade, and what are the specific improvements? How could I possibly know anything about kernel dependencies? Why doesn't someone create an easy upgrade? How is this better than Microsoft, when flaws are not fixed and I must "upgrade" in order to (hopefully) fix problems?

[bigpup]

Have you even tried this?

This tells you the difference between v10.0.8 and v10.0.9
https://forum.puppylinux.com/viewtopic. ... 021#p89021

[Governor]

Have you even tried this?

This tells you the difference between v10.0.8 and v10.0.9
viewtopic.php?p=89021#p89021

Can you tell me where the detailed upgrade instructions are, and is there only an ISO available, or can I download an image (like with EasyOS)?
Most importantly, can I boot with a backup file from v10.0.8?
Thanks!

[Clarity]

@Governor I wonder if you have considered what an IMG is vs an ISO? There has been a long standing mis-concept of these 2 deliverables for a running system.

BOTH are merely formats to deliver a running system. NOTHING MORE!

There is no "real" advantage that an ISO has versus an IMG for delivering a running system. BUT, 'some' will debate this. It reminds of the debate between Ferrari vs Lamborghini as which is faster or better.

I'm trying to understand if I can contribute to you to help.

I can see that the upgrade process is confusing you, but wonder if there is another way to explain what @BigPup is trying to get you to see.

May be the forum 'might' have a beginner's reference for a given distro that would cover the concern you reference, but, not sure if that would help.

[Clarity]

@bigpup and others, your reference to the kernel upgrade is important to all as it references the level of build some of the subsystems rely. This, for example, is important to users of nvidia video adapters. And there are other subsystems, too, that a kernel change will affect ... some minor others major.

More knowledgeable users would spot and know this. Lessors might miss this understanding.

Thanks @bigpup. There is much benefit in what you do.

[bigpup]

Have you even tried this?

This tells you the difference between v10.0.8 and v10.0.9
viewtopic.php?p=89021#p89021

Can you tell me where the detailed upgrade instructions are, and is there only an ISO available, or can I download an image (like with EasyOS)?
Most importantly, can I boot with a backup file from v10.0.8?
Thanks!

If you do not understand what is in this topics first post.
I can see this is going to need to be in a new topic you make on the forum.
So I can give you step by step what to do.
So start a new topic and I will answer your questions in it.
.
.

[bigpup]

Just did this for a frugal install of v10.0.10

Used the save from v10.0.9 frugal install.

Seems to also be working OK as the save for it.

Had the Nvidia driver package installed in the old save.
It seems to have automatically updated to the correct kernel now being used.
Maybe the DKMS feature is doing this change.

Debian Kernel DKMS
(Dynamic Kernel Module Support) is a framework that allows kernel modules to be automatically rebuilt when the kernel is updated.
It helps in maintaining kernel module compatibility with new kernel versions, which is particularly useful when using custom or third-party kernel modules that may not be included in the mainline kernel.

[mikewalsh]

Works for me too. No Nvidia driver here, but this is essentially the 'save' from 10.0.4, transplanted across through the updates. It just keeps on working!

Mike.