Unless there is a major change made that can not be altered by apt re-installing a package, then yes you should be able to continue using it.  Personally, I do not foresee this happening.  I am sure that this will be mentioned again, but you will need to alter your /etc/apt/sources.list file after daedalus goes stable.  Right now, only the "main" repo is available in daedalus.

There are a lot of possibilities here and I will throw out the one example that I use the most:  Xephyr, Xming, and SSH and the technology is called Nested Xsessions.

Xephyr is a linux program which runs nested X sessions on the client (local) system.  Xming is the windows program that displays the remote system on a local windows computer.  SSH is the tunnel to transport the xsession from remote to local.  You might have to also use Putty with windows and Xming.  At the time, I had never heard of "nested Xsessions" before so this was all new to me.  I prefer it over VNC, X11vnc, etc. as you do not have to have an Xsession running on the remote system.  It only has to be installed, and you start the remote xsession from the local machine and it displays within the Xephyr window on the local desktop.

There is a lot written about this on the web, so check if you think it may fit your needs.  The many tutorials written on the web explains it better than I can.  The hardest part for me to get it working initially was getting the Display number right.  Also, you might have to make a few configuration changes on the server involving ssh xforwarding, so root access would be required there.

For my needs, I use it to access a remote server that is running in headless mode which has a lightweight xserver installed on it (Xfce).  It is not perfect but it is the best that I have used to access a remote server which does not have a X session running.  I have two aliases configured in my local client bash profile so it is easy and quick to access the remote server.

My goal is to get JWM on the remote server instead of Xfce, since it is uses less resources.  This is a work in progress.

Thank you for the newer post links.  I did a search and responded to the thread that showed first.  Sorry about posting in the oldest thread.

Thank you for your work / contribution.

I learned something new today.  I will install it now so my kernel does not get left behind on the update process. 

Thanks HOAS.

Edit:
migf,
The same would be true for the header files as well.

I had a similar issue two weeks ago.  I had a 5 or 6 year old HP laptop in good condition but the wifi card in it was only 2.4ghz and I wanted a 5ghz card for the speed.  So I bought one off of ebay.  It was a RTL8821CE 802.11ac.  It did not work with the stock kernel in chimaera, so I installed a newer kernel from chimaera-backports.  The dkms module built fine then and it works like a charm.  It was the first time I ever needed a newer backported kernel.

Installed the necessary firmware:

Add the backports line to the  /etc/apt/sources.list  file

Then:

apt update

Install the backported kernel:
apt install -t chimaera-backports linux-image-5.18-(whatever the version is in backports).

Might be best to install the kernel before the firmware.

It appears that this firmware-realtek package may support your RTL8852 card.  From the debian package page showing supported hardware:

Yea, I was surprised to see this also.  If a Pep based theme were to break it could possibly be fixed with a reinstall of the package.

Now that was just humorous.  I got a good laugh from that.  No disrespect intended to HOAS, none at all.

I have the Peppermint-dev installed and I admit ... when I look at my grub boot screen and it displays multiple linux OSs, lately my Pep-dev install gets the click to boot, as in boot into.  It has a good "feel" to it.  That's about as technical as I can get... (-:

First of all, I am far from being an expert using rsync.  I acquired that line of code from somewhere on the internet from someone who uses rsync to backup and restore their system.  I will try to explain, and I hope that I do not give you any bad advice... (-;

It depends on if you tell it to, or not.  (-;  Currently, as the code is displayed, it would copy the /home folder and all its contents because it is not shown in the excluded section.

Let's look at this line of code in some detail.  Here is the entire line of code:

rsync -aAXv --exclude={"/swapfile","/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/media/*","/mnt/*","/lost+found"} /* /backup/folder/location/ --delete

Let's take it apart:
- "rsync -aAXv" type "man rsync" in the terminal to see what these flags are
- "/* /backup/folder/location/" This is the source and destination of data to be copied.
- "--delete" means to delete the file in the destination location if it does not exist in the source location.  Respect this --delete, as it can be very destructive.
 
Explanations:
--  The above is telling you to rsync (copy) the entire root filesystem "/*" but to exclude (omit from the copy) these folders/files:
--  the  /swapfile, because it is can be large
--  /dev , /proc , /sys , /tmp , /run .  These folders are populated with content as the system boots so they need not be copied over, but the empty folders should be copied over to make it easier if you had to restore the backup. The /lost+found is leftover data which need not be retained.
--  /media , /mnt  These are normally mount points so their data need not be copied over.

Notes:
- within the exclude section of the code, "/dev/*" will copy only the /dev folder with no content within it, whereas "/dev" will omit the entire folder and its contents.
- to make the backup simpler, you could remove the swapfile from the exclude section.  Then it would be copied over and thus included in the restore - moving the destination folder back into the source location.  Within the line of code  "/* /backup/folder/location/", these are the source and destination locations.
- You mentioned the /home folder.  It can easily be omitted during the copying by including it within the exclude section of the code.  For example the exclude section would look like this

--exclude={"/swapfile","/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/media/*","/mnt/*","/lost+found","/home/*"}

Restore the backup:
You could reverse the source and destination locations and it should work.  For clarity, now the source and destination are reversed.  The source is the backup and the destination is the original source location of the root folder.

So, this is an example of the restore code, it is almost identical but slightly altered by reversing the source and destination locations:

rsync -aAXv --exclude={"/swapfile","/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/media/*","/mnt/*","/lost+found"} /backup/folder/location/* / --delete

But beware of the /media and /mnt part of the code.  Make sure that there are no mounted partitions, remote locations, etc. mounted on the system!  Otherwise, including the mnt and media sections will --delete their contents!  Run as root "umount -a" in the terminal and verify that there is no mounted content.
- the resore command above will not move the swapfile back into position, thus it would have to be re-created.  Adjust the code to include or exclude the swapfile based on your need.

It terrified me too.  The way that I learned to trust this process is by moving a local system created in virtualbox into a remote system on a vps or another virtualbox guest system.  The process is the same, the only difference is the destination location in the code.  I have on several instances used this code to move a local system onto a remote virtual private server, which is the same process as "restore" as you mention above.
The only problems that I have seen are with two files: /etc/fstab  and  /etc/network/interfaces .  To get around this I make sure that the necessary files are included in the source files before transferring.  Or, I alter the files to be correct before attempting to reboot.
You may have an issue with the boot process hanging initially with a message referring to "unable to ... suspend or remove..." or something like that.  If so, wait until it boots, and run as root

update-initramfs -u

This will rebuild the initramfs boot image.

Questions?  I will be glad to help, if I can.  But I would test this myself before I actually "trusted" it.  You are on the right path in thinking about the restore process before it is actually needed.  For me, testing within and across virtual machines was necessary and very helpful.

Last pointers:
For testing purposes, the sources and destination folders can be local folders or remote ssh filesystem locations, which would make the line of code pretty long.  Don't get discouraged as it will function as it should.
Second, know the difference between locations shown with a  /folder  and  /folder/* .  "/folder/*" will copy/restore the folder and its contents. 
Lastly, please respect the --delete function.  For this reason, in the event of a catastrophic system failure, I would not mind doing the restore in several commands and not a one-line command.  I am not an expert and I would not want to move the backup back into the root folder location unless I copied all the files.  In simpler words, the --delete command may delete all of the original files when you did not copy but some of the files.  I know I sound confusing, but testing will give you an idea of what this entire command can do.  It is pretty powerful.

Sorry to be so long, but this is a powerful piece of code, and very helpful.  It is worth testing and using.  In writing it up, I realize that I need to test a few things to understand it better than I do.

Hi ComputerBob,
For future reference, to install the set of refractatools that will allow you to build and install a custom iso, try this command:

These two programs will allow you to create and install a custom iso with the commands

and

from the command line.  These are not gui programs.  Although they are not gui programs, they can probably satisfactorily create and install most snapshots.

You have already found the command for the gui programs so I will not mention those.

I will assume that you did not install the nvidia drivers with the "--no-install-recommends" part.  If not, then it will install the nvidia-persistenced package.  I seem to recall seeing this error before and the easy fix is to uninstall the package "nvidia-persistenced".

As for the other error message, I don't know about that.

I do understand the concept of "no support" but I hope it will not hurt to ask if there are packages missing.

My instance of nextcloud is throwing up an error about missing the php module "imagick".  I can only see the "php-imagick" package available with the deb.devuan.org repository now.  The php*-imagick packages from the tdrnetworks repo are not showing up:

Whereas the deb.sury repos shows all the individual modules for each version of php.  I activated this repo only for this info:

My sources.list includes

I have no related "apt pinning" in preferences.d folder, nor do I have any packages on "hold".  This command returns nothing:

Other packages from the tdrnetworks repo are showing, for example:

Are these "missing" php*-imagick packages, or is there a reason why the tdrnetworks packages are not showing up at all?