MX Linux Forum

Posted: **Tue Feb 21, 2023 8:48 am**

What do you use Snapshot for.?

I get the impression that we can use that MX tool almost to make our own distros.
We can configure MX for any purpose we like and after that we can use Snapshot to create a complete install disk with exactly the same settings.
And it will work just as smooth as the normal MX install on any PC.
I find it hard to believe it is that easy, so before my imagination runs too wild I hope some of you good people with experience wants to calibrate my expectations to real life by chatting about the possible bumps and bugs on the road.

Thanks.

Posted: **Tue Feb 21, 2023 9:00 am**

We can configure MX for any purpose we like and after that we can use Snapshot to create a complete install disk with exactly the same settings.

Yep. The only thing to consider is that if you do "reset accounts" type of snapshot the configuration in /home won't be preserved. It's not about settings it's about adding/removing programs and only configurations in /etc would be preserved.

Use cases? I don't know have a Live flashdrive with whatever programs you need? Installing an already updated ISO (By the way, that's what I use to create monthly snapshots, we even make the current x64 Xfce snapshot the default download on sourceforge, that gets downloaded a lot and I haven't heard comments that it doesn't work just like our regular release).

Posted: **Tue Feb 21, 2023 9:03 am**

Backup. At least, one kind of backup. Works like a peach.

Posted: **Tue Feb 21, 2023 9:42 am**

Test a new install on a spare machine, configure it how you like it, then use the Snapshot to install on your main machine.

It means the main machine is only out of use for 15 minutes or so.

Chris

Posted: **Tue Feb 21, 2023 10:05 am**

I could be wrong, and I don't have much experience with either, particularly "resetting accounts" but….

"Preserving accounts" is best is used for the same user that it was created from, if you try to then use it for other users (particularly ones to whom you wouldn't want to have access to sensitive data) you'll have to make different changes, creating another user, probably changing ownership and/or permissions; and as I've been informed, some sensitive data could still be exposed to the new owners. For redistribution to yourself, it's great.

Also, as Huck has recently stated – paraphrased, you can also take any MX iso (that's what MX Snapshot creates also), create a Full-featured writable iso with MX-Live-USB-Maker, modify it, remaster it and basically do the thing.
HTH

Posted: **Tue Feb 21, 2023 10:31 am**

Jakob77 wrote: Tue Feb 21, 2023 8:48 am ...
We can configure MX for any purpose we like and after that we can use Snapshot to create a complete install disk with exactly the same settings.
...

That is exactly what I use MX Snapshot for. I not only have several copies of my working MX-19.4 installation in a Snapshot iso file but have writen that iso file to an encrypted USB flash drive (I encrypt the flash drive because my installation is encrypted and want to keep personal things private). The reason I write the iso file to a USB flash drive is to easily restore my installation as well as provide a little insurance against any of the Snapshot iso files that were backed up to not be available (fire, theft, etc.). Even if the Snapshot iso files are available on my backup drives it is MUCH faster and easier to just insert a ready-made (encrypted) Snapshot of my installation available for immediate use.

Jakob77 wrote: Tue Feb 21, 2023 8:48 am ...
I find it hard to believe it is that easy, so before my imagination runs too wild I hope some of you good people with experience wants to calibrate my expectations to real life by chatting about the possible bumps and bugs on the road.
...

Yes, it is that easy (at least for me). I have never experienced any bugs with MX Snapshot but there are some points to be aware of. This is because a Snapshot is intended to be written to many computers and not just the computer it was created from. I only use the Personal Snapshots ("Preserving accounts") option but this also applies to the General Snapshots ("Resetting accounts") option in MX Snapshot.

I only use the base MX installation to make the Snapshot. In other words, I exclude any personal data (documents, multimedia files, etc.) from the Snapshot.

I have my user directory on the root partition and in my user directory I have all my personal data in a separate directory. That personal data directory is excluded when making the Snapshot. (Some users have their user account on a separate partition - I prefer it on my root partition.)

Excluding my personal data allows for a smaller Snapshot. My personal data is not important to making a Snapshot since my personal data is backed up on a number of drives and I simply copy my back up to the directory in the new installation.
I keep a meticulous record of any changes I make to my installed system. On that list I show when a Snapshot was made so if a Snapshot is used to make an installation I will know exactly what changes I need to make. This allows a long time between Snapshots since it is a simple matter to refer to this list to manually make the changes. This really only works if all changes to the system is religiously entered in the list.
I usually make a new Snapshot at the beginning of each year. My running list of configuration changes allows for a long time between Snapshots or even with an installation from a base (official) iso.

Remember that MX Snapshot is intended for installating on many computers so some configurations will still be needed after a Snapshot is installed. For example:

Installing will still require the basic installation parameters. I know exactly how to configure an installation because I have a very detailed installation guide that I made and keep up to date. For example, the below is what I have listed to either configure or confirm during and after a Snapshot installation:
During the installation phase I:
Add the Computer Name (hostname which appears on the terminal bash prompt)
disable "Samba"
clock to 24 hours
"Advanced" > disable bluetooth, saned (scanner), and cups (printer), none of which I have any use for.
After the Snapshot is installed I configure or confirm the following is configured (remember, this is for my installation - others may differ):
"Removable Drives and Media" > enable "Mount removable drives when hot-plugged" (this is normally the default now).
Change the Network DNS servers to 1.1.1.1, 1.0.0.1 (an installation will use the default DNS servers which is none).
I use a DAC for my audio so I change to that setting in PulseAudio Mixer > Configuration tab > "PCM2704 16-bit stereo audio DAC" from the drop-down menu select "Digital Stereo (IEC959) Output."

Posted: **Wed Feb 22, 2023 3:10 am**

I remember how proud I was a long time ago when I first learnt to restore my DOS system fast and easy on almost any computer.
After DOS it only got slower and more complicated but I sense Snapshot might be a turning point.

In my first test making an iso file it runs very well but when done the file is too big for a normal copy.
I am looking at zip and arj to put the iso file into smaller files but I guess there are other ways to handle it.?

Posted: **Wed Feb 22, 2023 6:26 am**

MX Snapshot has 5 different compression algorithms to select from. This is done on the second window in the Snapshot setup dialogue - see the below image for the compression algorithm options and a brief description of the differences (the highlighted entry in the image will make the smallest file at the cost of taking the longest time to do so.):

MX_Snapshot_compression_algorithm_options.png

As an example, I have a total system file size of 14 GiB for Snapshot to copy. Using lz4 will compress that to 5.4 GiB and takes 2:44 to do so. Using zstd will compress it to 3.9 GiB and takes 5:52 to do so. Of the 5 compression options zstd is the best compromise between file size and creation time. I always use lz4 for my Snapshots because I have plenty of storage space for the iso files so the file size is not an issue. As shown in the above image "xz" will give you the smallest file but it will take the longest time to create (no file size or creation time is given because I have not tested it).

Also, I do the following to reduce the total file size for Snapshot to create. There have been some times when I have reduced a 15-16 GiB total file size by well over a gigabyte of "useless" used space. Here are three main things I do:

Remove deb files in the archive directory which can easily free up a gigabyte of space depending on time between cleanups. It is completely safe to clear this cache that is created by apt when a package is installed (upgraded). It is simply clearing the local repository of downloaded package files that are no longer needed. The below command will remove the contents of the archives directory except for two files, the lock file and the partial directory. They have special permissions that will not allow them to be deleted. They need to be on the system they were created for in order for proper package updating.

These Debian files are from upgrades that the system uses when it installs the package. When a package is installed using apt or apt-get it downloads the package and dependencies in .deb format and keeps it in /var/cache/apt/archives, however the deb package is first kept in /var/cache/apt/archives/partial by apt while downloading. When the deb package is completely downloaded, it is moved to /var/cache/apt/archives. At this point, after the package has been installed, the package is really no longer needed and can be safely deleted.

The first command below will show the size of the archives directory. The "-s" option is to output a total or summary of the size. The second command will delete all the retrieved Debian package files in the archives directory.

Note that sudo apt autoclean is another command to clean the apt cache but unlike clean, autoclean only removes packages that are not possible to download from the repositories such as old versions of packages. Thus this command will likely leave some Debian file packages remaining that, for the most part, have no use and are just taking up space:
Code: Select all
```
sudo du -sh /var/cache/apt/archives/

sudo apt clean
```

Delete the browser cache directories (they will be re-created when the browser is used again). The below code window shows the cache directories I delete:

Code: Select all

Chrome browser:
~/.cache/google-chrome/Default/Cache/Cache_Data/
~/.cache/google-chrome/Default/Code Cache/js/

Firefox directory:
~/.cache/mozilla/firefox/xxxxxxxx.default-release/cache2/entries/

Delete all thumbnails in ~/.cache/thumbnails/large and /normal

Posted: **Wed Feb 22, 2023 11:13 am**

Stuart_M

Wow, you are thorough. :-)
I would probably just splurge and buy a bigger USB key.
If there is room enough on the USB-key, the iso file probably cannot be too large for 'burning'.

I don't know if it is a tunar thing or an old computer issue but I do get an error if I try to copy the 4.6 Gb iso file to another folder.
There could maybe be a small need for that somewhere for instance in a daily backup routine.
For me it was just for testing and playing purposes and it looks like arj can do it.

I don't know if instructions or warnings are appropriate but with these arguments

Code: Select all

-v100000k -m0 -y

arj as fast as copy made me 50 files 100 Mb each.

Posted: **Mon Mar 13, 2023 10:48 pm**

Now I have made a snapshot backup with all default settings and put it on a USB-key.

A fast test indicates that I can boot up on it on almost any computer and in that way get access to all my data from when the backup was taken.

That is really great.

This 2. part is a little harder to test, and I hope maybe someone wants to verify or correct my understanding of it:

I can not really install this simple version of a snapshot backup on a random computer.
If I want to restore the whole system it has to be on the same hardware from where the backup was taken.
And if that is the case it can all be restored just by booting up live and enter the command "minstall" in a root terminal.

Posted: **Mon Mar 13, 2023 11:00 pm**

NO, that is incorrect. I have created several snapshots in VM's and also in hardware installs, built the entire machine, created a snapshot and then installed to WIDELY different hardware and it has worked successfully.

My new method to create a new version install is this way, (ie build it in a vm first!, then install on hardware) and it seems to work VERY well.

Posted: **Tue Mar 14, 2023 5:29 am**

Jakob77 wrote: Mon Mar 13, 2023 10:48 pm...
I can not really install this simple version of a snapshot backup on a random computer.
If I want to restore the whole system it has to be on the same hardware from where the backup was taken.

You can (and that's the beauty / one of the most useful sides of this tool). Just "naturally" not 64bit to/on 32 . (It'll pick/load the required drivers according to the "current" hw/pc like a generic (official) iso. (It won't record/compare/demand anything related to the original system/hw and won't say "but it was so in the source system"..).

Btw. you can also do everything different when installing on another pc. Say, different partitioning (i.e. home or boot was separate but now not), encryption (some were encrypted but now you may not encrypt or the vice versa..) .. User name and pw... Shortly: Like installing anew, from a downloaded official iso. The difference is: The existing and non-existing software are determined by you :)

Jakob77 wrote: Mon Mar 13, 2023 10:48 pm... and enter the command "minstall" in a root terminal.

Yes but no.

Normally the install icon is on desktop, just on personal snapshots you may not see that. Then just a normal (user) terminal and

Code: Select all

sudo minstall

or

Code: Select all

sudo minstall-launcher

(there are -launcher versions of many commands, to make it better compatible for different DEs )

Posted: **Tue Mar 14, 2023 11:30 am**

@Jakob77
At the very bottom of the exclusion file in MX Snapshot you'll see something like the following. Maybe different depending on you computer, I don't know, I'm a newb; but if you wanted to not exclude - thereby including – a particular driver(s), you could comment-out "#" the following video drivers.

Code: Select all

# This stops any video drivers from loading - safe option.
etc/X11/xorg.conf
etc/X11/xorg.conf.d/20-nvidia.conf
etc/X11/xorg.conf.d/20-intel.conf
etc/X11/xorg.conf.d/20-radeon.conf
etc/X11/xorg.conf.d/20-amd.conf

I could be wrong, but barring changing this, I don't think that the snapshots should inherently have any problems functioning on different hardware or another computer.

To reaffirm what others have said, install away! – HTH.

Posted: **Tue Mar 14, 2023 11:38 am**

These are purposely in exclusion list, to enable you boot on different-card machines.

Otherwise when included (# means that) such files will force it to use , say amdgpu for xorg when it's Intel... or the vice versa ... (=> black screen)

This way (when they're not included) it'll load whichever is required, say Nouveau when it's an Nvidia machine ...

Posted: **Tue Mar 14, 2023 11:53 am**

@Huckleberry Finn Yes, Huck, that's exactly as I understood it and what I meant.
I hope I did state that.

Posted: **Tue Mar 14, 2023 2:28 pm**

Huckleberry Finn wrote: Tue Mar 14, 2023 5:29 am
Jakob77 wrote: Mon Mar 13, 2023 10:48 pm...
I can not really install this simple version of a snapshot backup on a random computer.
If I want to restore the whole system it has to be on the same hardware from where the backup was taken.
You can (and that's the beauty / one of the most useful sides of this tool). Just "naturally" not 64bit to/on 32 . (It'll pick/load the required drivers according to the "current" hw/pc like a generic (official) iso. (It won't record/compare/demand anything related to the original system/hw and won't say "but it was so in the source system"..).

Btw. you can also do everything different when installing on another pc. Say, different partitioning (i.e. home or boot was separate but now not), encryption (some were encrypted but now you may not encrypt or the vice versa..) .. User name and pw... Shortly: Like installing anew, from a downloaded official iso. The difference is: The existing and non-existing software are determined by you :)

Jakob77 wrote: Mon Mar 13, 2023 10:48 pm... and enter the command "minstall" in a root terminal.
Yes but no.

Normally the install icon is on desktop, just on personal snapshots you may not see that. Then just a normal (user) terminal and
Code: Select all
sudo minstall
or
Code: Select all
sudo minstall-launcher
(there are -launcher versions of many commands, to make it better compatible for different DEs )

Thank you very much.

All in all it is the most amazing progress I have ever seen in Linux.

The potential must be huge.
I wonder if we are ready for 100 new forum users next week and 1000 the week after, and 10.000 the week after that and...
I guess Eadwine Rose will need a bigger comb for all those new profiles with long messy hair.

Posted: **Tue Mar 14, 2023 2:33 pm**

Jakob77 wrote: Tue Mar 14, 2023 2:28 pm... All in all it is the most amazing progress I have ever seen in Linux...

Yes, that's maybe the most outstanding feature of MX .. there were similar trials on other distros but they were really complicated (many options/buttons like a cockpit) and were deprecated.

Posted: **Tue Mar 14, 2023 2:41 pm**

@Jakob77 wrote:

The potential must be huge.
I wonder if we are ready for 100 new forum users next week and 1000 the week after, and 10.000 the week after that and...

Moderator Hat On

The potential is there but the desire is not. We like it the way it is.

Posted: **Tue Mar 14, 2023 2:43 pm**

I JUST read about penguin-eggs which is a command line iso tool to do this. I chuckled all the way through the article because the MX Snapshot tool is SO much more advanced. (imo )

https://www.linuxuprising.com/2023/03/h ... em-to.html

MX Linux FTW!!

Posted: **Wed Mar 15, 2023 5:21 am**

Huckleberry Finn wrote: Tue Mar 14, 2023 2:33 pm
Jakob77 wrote: Tue Mar 14, 2023 2:28 pm... All in all it is the most amazing progress I have ever seen in Linux...
Yes, that's maybe the most outstanding feature of MX .. there were similar trials on other distros but they were really complicated (many options/buttons like a cockpit) and were deprecated.

I still can't get my head around all the possibilities.
For instance the mail backup. I have some old databases I would like to compare with a newer one.
That might not be possible or a huge job because I need different older versions of Thunderbird to read them.
But if I 10 years ago had made a snapshot with a mail database I would today have been able to just plug it in and read everything off-line.
I think that is also something to think about for the future.
I need to buy some more USB-keys.

When I used Snapshot to move the installation to my old HP I had to do adjustments for the display. That was expected and all I noticed at first.
Now I have also found that the procedure has turned off the firewall.
It is still almost nothing in the big picture but I don't know if that is supposed to be or if we perhaps have a list with settings we are supposed to verify afterwards.?

However I think we have to tell the amazing developers that they have forgotten a very important feature.
It is really a disappointment that Snapshot can't multi clone and export this forum yet. We need a lot more of them to meet the demand.!

Posted: **Wed Apr 12, 2023 3:53 pm**

I have two questions for the Snapshot gurus:
1) I cannot find the Edit Configuration File button that is discussed and shown in the Help.
2) More importantly-- I have a 2 TB disk, which I partitioned to have Windows on one partition, MX Linux on another, and I wanted to put backups on the third. I can tell Snapshot to put the Sanpshot on an SD card, but it does not show the third partition, the one I wanted to use for backups. Gparted sees it and formatted it (ext4) with no problems. What am I doing wrong?

Code: Select all

Snapshot created on: 20221126_0604
System:    Kernel: 5.19.0-2mx-amd64 [5.19.11-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.19.0-2mx-amd64 
           root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.3_x64 Wildflower November 26  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Dell product: XPS 13 9310 v: N/A serial: <filter> Chassis: 
           type: 10 serial: <filter> 
           Mobo: Dell model: 0MRT12 v: A00 serial: <filter> UEFI: Dell v: 3.13.1 date: 02/20/2023 
Battery:   ID-1: BAT0 charge: 47.0 Wh (99.2%) condition: 47.4/51.0 Wh (93.0%) volts: 8.5 min: 7.6 
           model: BYD DELL FP86V09 type: Li-poly serial: <filter> status: Charging 
CPU:       Info: Quad Core model: 11th Gen Intel Core i7-1185G7 bits: 64 type: MT MCP 
           arch: Tiger Lake family: 6 model-id: 8C (140) stepping: 1 microcode: A4 cache: 
           L2: 12 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 47923 
           Speed: 844 MHz min/max: 400/4800 MHz Core speeds (MHz): 1: 1004 2: 604 3: 3000 4: 3000 
           5: 1200 6: 1120 7: 3000 8: 523 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data status: Not affected 
           Type: retbleed status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Enhanced IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: SW sequence 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: Dell driver: i915 v: kernel 
           bus-ID: 00:02.0 chip-ID: 8086:9a49 class-ID: 0300 
           Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 3-6:3 
           chip-ID: 0c45:672a class-ID: 0e02 
           Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.18.0 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3") 
           s-diag: 583mm (23") 
           Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 169 size: 288x180mm (11.3x7.1") 
           diag: 340mm (13.4") 
           OpenGL: renderer: Mesa Intel Xe Graphics (TGL GT2) v: 4.6 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel Tiger Lake-LP Smart Sound Audio vendor: Dell 
           driver: sof-audio-pci-intel-tgl alternate: snd_hda_intel,snd_sof_pci_intel_tgl 
           bus-ID: 00:1f.3 chip-ID: 8086:a0c8 class-ID: 0401 
           Sound Server-1: ALSA v: k5.19.0-2mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Qualcomm QCA6390 Wireless Network Adapter vendor: Rivet Networks 
           driver: ath11k_pci v: kernel port: efa0 bus-ID: 72:00.0 chip-ID: 17cb:1101 
           class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 2.1 TiB used: 300.8 GiB (14.0%) 
           ID-1: /dev/mmcblk0 maj-min: 179:0 model: FE4S5 size: 238.75 GiB block-size: 
           physical: 512 B logical: 512 B type: SSD serial: <filter> scheme: MBR 
           SMART Message: Unknown smartctl error. Unable to generate data. 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-2: /dev/nvme0n1 maj-min: 259:0 vendor: KIOXIA model: KXG60PNV2T04 NVMe 2048GB 
           size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 
           type: SSD serial: <filter> rev: 10704104 temp: 43.9 C scheme: GPT 
Partition: ID-1: / raw-size: 949.97 GiB size: 933.99 GiB (98.32%) used: 300.71 GiB (32.2%) 
           fs: ext4 dev: /dev/nvme0n1p4 maj-min: 259:4 
           ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 86.2 MiB (89.8%) fs: vfat 
           dev: /dev/nvme0n1p1 maj-min: 259:1 
Swap:      Alert: No swap data was found. 
Sensors:   System Temperatures: cpu: 49.0 C mobo: 43.0 C 
           Fan Speeds (RPM): cpu: 0 fan-2: 0 
Repos:     Packages: 2546 note: see --pkg apt: 2540 lib: 1123 flatpak: 6 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirror.cogentco.com/pub/linux/mxlinux/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/nordvpn.list 
           1: deb https://repo.nordvpn.com//deb/nordvpn/debian stable main
           Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           1: deb [arch=amd64] https://repo.skype.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/surfshark.list 
           1: deb https://ocean.surfshark.com/debian stretch main
           Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
           1: deb http://linux.teamviewer.com/deb stable main
Info:      Processes: 255 Uptime: 24m wakeups: 1575 Memory: 31.08 GiB used: 2.51 GiB (8.1%) 
           Init: systemd v: 247 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI

Posted: **Wed Apr 12, 2023 4:06 pm**

1. There's an "Edit exclusion file" in the second screen after you press "Next", is that what you talk about? Config file doesn't have an edit button you could edit it manually by opening in your favorite file editor this file: /etc/mx-snapshot/mx-snapshot.conf

2. I don't see the 2rd drive in QSI, did you run it when you have that SD card plugged in? If you see it in Thunar it should show up in MX Snapshot too, maybe it's not mounted.

Posted: **Thu Apr 13, 2023 6:23 pm**

1) If you click on Help in Snapshot you could clearly see an EDIT CONFIGURATION FILE above the list of excludable folders.
2) Alas, Thunar cannot see the partition I wanted to use for the Snapshot backup, even though Gparted can. I used sudo umanout -a but it did not help. Not sure at this point why it is hidden. I did run Snapshot with the SD card plugged in (it is always plugged in), but I do not see why that would hide an SSD partition from Thunar of PCmanFM.

Posted: **Thu Apr 13, 2023 6:48 pm**

Ah, OK, I forgot about that, I remove that button at some point in time, the Help file needs to be adjusted.

Posted: **Fri Apr 14, 2023 7:36 am**

In my opinion first and foremost it is wrong not to give the whole disk to MX.

For Windows users: Take a backup before you write "sudo minstall-launcher" in the Terminal.

Snapshot is the greatest tool I have ever seen in a OS.

Also if you make a Snapshot from your private computer and use it live on a rescue mission or if you just want to borrow a computer. You boot up on the plug in, and the computer will look and work the same as the one at home. Data, programs, the panel, your scripts, everything is there ready to be used.
If you think it feels strange the first time you are not alone.
Just remember to save data on the plug in disk on the partition built for it, or you might miss them next time you boot up.

I don't know if there is a procedure to save live configuration changes permanently on the USB-medium. Maybe if you save the session when you log out.?

I just wiped out Windows and installed MX 21.3 on a Dell Latitude E7240 with a Snapshot made on a Lenovo stationary.
It was easy and fast.

A little screen and panel adjustments.
Somehow it lost the background color and some shortcuts on the desktop had lost permission to start programs.
That was almost nothing and everything else seems to work perfectly.

About the hardware examination and installation I assume Snapshot is just as good an thorough as the original installation iso
Is that not right.?

Posted: **Fri Apr 14, 2023 8:11 am**

If you have some problems, best course of action is, to start your own dedicated thread for it, so potential help can focus on it. Here your posts will be lost among other posts.

venik212 wrote: Thu Apr 13, 2023 6:23 pm 2) Alas, Thunar cannot see the partition I wanted to use for the Snapshot backup

Here you have an answer, why Snapshot can't see it. Since it is currently not available to you. Why not? That is another question that would need to be researched.

venik212 wrote: Thu Apr 13, 2023 6:23 pm ...even though Gparted can...

This is completely different thing, you can't compare these two. Gparted is designed to see things low level and unmounted. Gparted can see, what you in your user space cant. Gparted actually can't work on mounted devices. On another hand, if something for example is not mounted , you (or Thunar or PCmanFM etc...) will not see it and will not have access to it.

Posted: **Fri Apr 14, 2023 9:05 am**

I suspected that much, but it still does not tell me how to fix it. sudo umount -a did show another partition, but it was, somehow, inaccessible. I got errors trying to write to it.

Posted: **Fri Apr 14, 2023 9:18 am**

As long as it is with low expectations I think it is very cosy also to have some nut cracking chat.

venik212 wrote: Wed Apr 12, 2023 3:53 pm I partitioned to have Windows on one partition, MX Linux on another, and I wanted to put backups on the third.

Sorry, I am a little slow and I don't read that well, but does it mean that you already have installed MX on the computer.?

How big is the SD-card.?
I find that mounting problems often can be solved by safe remove if visible, and then unplug for some seconds, and then plug in again.

Posted: **Fri Apr 14, 2023 3:38 pm**

Let's chat some more about Snapshot.

Whom one loves one chastises. ( I wonder if that makes sense in English lol ).

Can we find some bugs.?

I don't think it is really fair to talk about bugs just because a little some configuration is missing after an install with a live Snapshot.
But life is rarely fair.

Posted: **Fri Apr 14, 2023 3:53 pm**

From the testing that I have done, a snapshot written to a live usb is really good and delivered everything.

In-fact, I have created new machine loads all in a VM, then once ready created a snapshot, written to a live usb, booted the new machine with that live usb and then installed. In every single case, I had a "duplicate" computer up and going.

This is now my preferred method of creating a new machine.

AND, both my big every day computer, my laptop, and 3 other testing machines have been built this way and work without issue. Different hardware, different ram sizes, different CPU, sized disks, etc. Really good!!

Posted: **Fri Apr 14, 2023 8:14 pm**

CharlesV wrote: Fri Apr 14, 2023 3:53 pm From the testing that I have done, a snapshot written to a live usb is really good and delivered everything.

In-fact, I have created new machine loads all in a VM, then once ready created a snapshot, written to a live usb, booted the new machine with that live usb and then installed. In every single case, I had a "duplicate" computer up and going.

This is now my preferred method of creating a new machine.

AND, both my big every day computer, my laptop, and 3 other testing machines have been built this way and work without issue. Different hardware, different ram sizes, different CPU, sized disks, etc. Really good!!

I can spend a long time thinking about what computer to start with and how to move on.
Is it best to start rich or lean and build the first on a computer with a big or small screen or both and so on.
It might not be smart to build in more users in the iso file because it will be more configuration to adjust after install.
To do it and be really efficient the best would be if all the computers were identical.

Posted: **Fri Apr 14, 2023 10:57 pm**

About the hardware examination and installation I assume Snapshot is just as good an thorough as the original installation iso
Is that not right.?

That question that you asked was what I was referring too. And yes, it could be smarter to get as generic as possible on hardware, however, the install, configs and certain setup is what is best to carry over. AND it seems to adapt, install and work well, even adjusting for hardware.

As a backup of your rig, or to move to a new rig... I think this method rocks!

If you wanted a rescue disk, then really a standard live USB is good. (That was where I started with AntiX , as a rescue usb.)

Posted: **Sat Apr 15, 2023 7:03 am**

CharlesV wrote: Fri Apr 14, 2023 10:57 pm
About the hardware examination and installation I assume Snapshot is just as good an thorough as the original installation iso
Is that not right.?
That question that you asked was what I was referring too. And yes, it could be smarter to get as generic as possible on hardware, however, the install, configs and certain setup is what is best to carry over. AND it seems to adapt, install and work well, even adjusting for hardware.

As a backup of your rig, or to move to a new rig... I think this method rocks!

I want to be different so I think it rolls!

It seems to me Snapshot with 'sudo minstall-launcher' is running and using the whole hardware examination, but I guess only the developers has a chance to know it for sure.

Posted: **Sat Apr 15, 2023 7:10 pm**

CharlesV wrote: Fri Apr 14, 2023 10:57 pm
If you wanted a rescue disk, then really a standard live USB is good. (That was where I started with AntiX , as a rescue usb.)

Thank you.
I have never used AntiX but others, and I never liked it much. I miss too many things, but with Snapshot exactly that has changed.
Do you know how to save config changes permanently to a live install USB-key or Snapshot, and if it will do changes to it's installation procedure when used for that later on.?

Posted: **Sat Apr 15, 2023 7:24 pm**

I believe the places you have to watch for that is in two spots:

1) Snapshot, second page, "Type of Snapshot"

2) and then when you install.

If I am using for my own personal installs, I just leave them default. If you dont want your account brought over you have to uncheck that in the Type of Snapshot.

Posted: **Sun Apr 16, 2023 3:10 pm**

CharlesV

Today I decided to show the external screen who was in charge, so I used my original USB that I used for installing MX Wildflower 21.3
But that seemed worse... maybe because it was some weeks old.
Then I made a fresh Snapshot and did it again.
And that seemed better.
I write "seemed" because I was also trained along the way.

However, I am slowly starting to believe that if you update your computer and afterwards make a Snapshot install USB then it will be as updated as the newest install iso you can download.

What do you say, do you buy it.?

Posted: **Sun Apr 16, 2023 4:23 pm**

I say ....
THAT is precisely what I was trying to tell you! :-)

Using snapshot, you can setup your computer exactly how you want it, drivers, settings, kernel versions, etc etc.. and THEN use that as a backup... OR ... as a fresh installation ( but keeping ALL your settings!)

Posted: **Mon Apr 17, 2023 4:26 pm**

I don't even know if I buy it myself, yet.

The updating force I sense can be other things or bugs being removed and holes patched.
Last night I installed MX Wildflower on one more identical Dell and the configuration was transferred perfectly to all users.

But if you have a computer on edge and it is missing drivers that are too complicated to install both manually and with automatic update but they are added to the install iso, it could perhaps be an idea to look more into it.
If it is the case you can likely just make a fresh Snapshot and do a restore with it. Then the hardware will be examined all over again and the newest drivers will be installed along with your data.
I don't really believe it is, and I don't know enough about it to imagine how far it can be taken.

I have had my doubts but what I know for sure now is that Snapshot IRL begins to bring my computer platform up on a much higher level.
Before snapshot I was always going for a minimalist configuration.
An important reason for that was to save time because I had to do it on five computers.
Now I can spend much more time making a better configuration, and when I am done I can copy it to other computers very fast and easy. Especially if they are identical.

I have decided to start middle weight with the basic setup I use the most on my private computer.
It will be geared up with five users and a design I like.
If a computer is going out of the house there will only be very little private data to remove before it is ready.
Also the time it takes to remove a user is nothing compared to the time it takes to set one up, so there is no need to be thrifty with them in the basic configuration.

I agree ... it rocks.!... and rolls.!

Posted: **Mon Apr 17, 2023 4:47 pm**

Jakob77 wrote: Sun Apr 16, 2023 3:10 pm CharlesV

Today I decided to show the external screen who was in charge, so I used my original USB that I used for installing MX Wildflower 21.3
But that seemed worse... maybe because it was some weeks old.
Then I made a fresh Snapshot and did it again.
And that seemed better.
I write "seemed" because I was also trained along the way.

However, I am slowly starting to believe that if you update your computer and afterwards make a Snapshot install USB then it will be as updated as the newest install iso you can download.

What do you say, do you buy it.?

I'll give you an example of how this works. My new HP 15 laptop was not working properly at all. Wifi was non-existent and the Ethernet connection was sporadic. I discovered in my research that the Liquorix 6.2.xxx kernel available through MXPi would likely solve most of the problems. Without internet access, I couldn't install it directly on to the HP 15. Instead, I installed the Liquorix kernel on to my desktop, made a snapshot of the desktop. and wrote the snapshot to a USB drive which I used to do a fresh install on the HP 15. It worked a treat.

Posted: **Tue Apr 18, 2023 4:07 am**

Yes, that was smart.

Posted: **Sun Apr 30, 2023 12:06 pm**

If your USB-stick is all too big for your snapshot iso don't start crying about the waste of space.
In advanced options you can just make a partition for data and use that as normal without booting on it.

MX-USB-creator-snap-and-data-partition.png

That is a good thing because the installation USB with MX Wildflower and Snapshot has an exiting tendency to breed.
And along with a list of setup things to remember my USB library is growing.

https://forum.mxlinux.org/download/file ... &mode=view

Some users in other distros can do a backup.

In MX we can make history.

Posted: **Tue May 16, 2023 4:27 pm**

I have installed MX on two computers with Snapshot from USB-sick today.

That gave me the output

Code: Select all

QProcess::UnknownError

295 times.

Who knows what the unknown can be.?

And how can the install still seem to work okay with so many errors.?

Some files on the desktop got their permissions changed but so far that is the only unexpected thing I have seen.

However I think it might be a good rule not just to rely on a snapshot iso file.
In my system I have decided a Snapshot backup is not really done before I have a test passed USB-stick in my hand.

And a question I have had some fun thinking about and want to share:
To do a md5 checksum test on the iso file right after it is made.
Is that silly or not.?

Posted: **Tue May 16, 2023 5:40 pm**

I believe that is a QT error, but without a real code... ??

I think it wouldnt hurt to know that the iso is good. As I said before, I have not had issues with writing iso's.

In walking through the steps, I use etcher to write ISO's .. never thought about that before, but that is a difference.

Posted: **Tue May 16, 2023 6:26 pm**

What exactly gave you the error? The installer? Anything else that can give us an idea? We are lacking context to understand what is going on. If for example you see in a log QProcess::UnknownError it might be useful to know what command was tried to be executed which might be listed before the error...

Posted: **Tue May 16, 2023 10:26 pm**

QProcess::UnknownError doesn't mean anything per se, and it depends on other parameters. The installer logs other codes also, for instance, if it looks like this then it is likely that the process executed successfully:

Code: Select all

Exit #8: 0 QProcess::NormalExit QProcess::UnknownError

That "#8" can be any number, and has nothing to do with the error. The first field after "Exit #...:" is the return code (should be 0 in most cases), the exit status (should be QProcess::Normal Exit) and the error code (defaults to QProcess::UnknownError).

Posted: **Wed May 17, 2023 2:42 am**

Thank you for asking. Yes that is mainly what it is:

Code: Select all

Exit #1: 0 QProcess::NormalExit QProcess::UnknownError

Exit #157: 0 QProcess::NormalExit QProcess::UnknownError

Maybe it can occur if the USB is hardly big enough but the target computers still don't seem to mind.

Posted: **Wed May 17, 2023 4:39 am**

CharlesV wrote: Tue May 16, 2023 5:40 pm In walking through the steps, I use etcher to write ISO's .. never thought about that before, but that is a difference.

Yes, and very good to know it is tested that the snapshot iso file is also compatible with Etcher.

So if we want to restore an iso file 10 years later we are not necessarily depending on snapshots USB Maker to be that much backward compatible.
I just think the Snapshot USB Maker is so nice and straight forward when I for instance also want to add a data partition.

Posted: **Wed May 17, 2023 11:04 am**

Jakob77 wrote: Wed May 17, 2023 4:39 am
So if we want to restore an iso file 10 years later we are not necessarily depending on snapshots USB Maker to be that much backward compatible.
I just think the Snapshot USB Maker is so nice and straight forward when I for instance also want to add a data partition.

I have no idea what your asking / saying here about backward compatible.

And just to clarify, there are two different tools we are talking about here :
1) MX Snapshot ( Creates an iso of your computer )
2) MX Live USB Maker ( Writes an ISO to USB)

And if your asking about a writable partition ( ie .. persistence ) , then yes the MX Live USB Maker is the way to go.

Posted: **Thu May 18, 2023 3:16 am**

CharlesV

I have seen so many "smart" backup systems that works really well for people until the day they need a restore.
Windows backup systems, DOS programs, Windows programs, Outlook and Thunderbird mail databases, forum databases and so on.
Therefore I like that it has been confirmed the snapshot iso file is a normal iso being compatible with more than just one peace of software.

Posted: **Thu May 18, 2023 10:04 am**

And this is *exactly* why you should ***test*** your backups routinely!

A backup is ONLY as good as the ability to restore it! I learned long ago that if you want to be sure, you must test backups, and so every three months I test my backups. Timeshift, Snapshot and BackInTime - all are tested!

Posted: **Thu May 18, 2023 10:09 am**

Jakob77 wrote: Wed May 17, 2023 2:42 am Thank you for asking. Yes that is mainly what it is:
Code: Select all
Exit #1: 0 QProcess::NormalExit QProcess::UnknownError

Exit #157: 0 QProcess::NormalExit QProcess::UnknownError
Maybe it can occur if the USB is hardly big enough but the target computers still don't seem to mind.

This looks good to me. If it all installed successfully and everything in the live log is green (with a sprinkling of yellow entries) then all is well. The log file is mostly for developers, so it is very verbose and noisy to capture all information that could be relevant to diagnose a problem.

As for backups, no matter how dumb or smart the backup method is, it is vital to test it. If practical, add a file that contains checksums of the backed up data, you can verify regularly that the checksums still match.

Posted: **Thu May 18, 2023 10:27 am**

CharlesV wrote: Thu May 18, 2023 10:04 am And this is *exactly* why you should ***test*** your backups routinely!

A backup is ONLY as good as the ability to restore it! I learned long ago that if you want to be sure, you must test backups, and so every three months I test my backups. Timeshift, Snapshot and BackInTime - all are tested!

Yep. First thing I do after making a snapshot and using the live usb maker is boot from it. See if that works. If it doesn't, I can make 50 of those that will never work until I find out what error -I- made.

Posted: **Thu May 18, 2023 11:12 am**

Perfect! In fact, the instructions on making a snapshot / live usb should not end with "writing it" .. they should end with testing it :-) ( They already might actually, but I do not recall seeing that :-) )

Posted: **Thu May 18, 2023 11:14 am**

CharlesV wrote: Thu May 18, 2023 11:12 am Perfect! In fact, the instructions on making a snapshot / live usb should not end with "writing it" .. they should end with testing it :-) ( They already might actually, but I do not recall seeing that :-) )

Well, people would get an ISO and they didn't know what to do with it. That's why we thought it makes sense to point them to the right direction, which tool to use the write the ISO to the USB drive.

Posted: **Thu May 18, 2023 11:15 am**

Adrian wrote: Thu May 18, 2023 11:14 am
CharlesV wrote: Thu May 18, 2023 11:12 am Perfect! In fact, the instructions on making a snapshot / live usb should not end with "writing it" .. they should end with testing it :-) ( They already might actually, but I do not recall seeing that :-) )
Well, people would get an ISO and they didn't know what to do with it. That's why we thought it makes sense to point them to the right direction, which tool to use the write the ISO to the USB drive.

Perfect sense, and I am certainly not complaining :-) ... I love the way you all have setup it all up! OUTSTANDING Job!!

Posted: **Thu May 18, 2023 12:36 pm**

I agree with the sentiments hinted above.

Q: Who needs most help?
A: the one's who think they do not need it

I'd guess that most experienced computer user are up to the challenge and in a sense that is both the beauty and the curse of Linux?

It isn't difficult but it isn't hard? To emerging nascent or developing skills computer users Linux seems to be a great environment - and that is not intended to offend commercial alternatives out there.
To an extent they all follow similar patterns with differing limitations= Great!

Posted: **Thu May 18, 2023 3:06 pm**

I would like to know more about how Snapshot is to maintain.
If there are events that makes it harder than others.
If there is a time of the year the users can expect more or less stability.
When for instance file permissions on the desktop are changed and the small problem seems to be solved but later it falls back again is it copy failure can it be because a new kernel was installed in the meantime or what can be going on.?

Posted: **Thu May 18, 2023 3:42 pm**

Well.. do not make a snapshot while there is a full moon. Not scientifically proven, though.

You asked for time of year

Posted: **Thu May 18, 2023 4:04 pm**

Jakob77 wrote: Thu May 18, 2023 3:06 pm I would like to know more about how Snapshot is to maintain.
If there are events that makes it harder than others.
If there is a time of the year the users can expect more or less stability.
When for instance file permissions on the desktop are changed and the small problem seems to be solved but later it falls back again is it copy failure can it be because a new kernel was installed in the meantime or what can be going on.?

I SO like Eadwine's answer :-) !!

@Jakob77 , this is opensource... the only guarantee you really have is that you *should* be able to download it. (And its free, so seriously no guarantee or any other "thing" that the devs or anyone else has to do - They do it out of love and devotion to their product and their people!!) And these are VERY good Dev's who care about both !!

YOU do have some options though. Learning about the code, about the releases, about the release notes :-) .. ALL very doable, and ALL on you - you want to know... I would suggest that you have a look here https://github.com/MX-Linux/mx-snapshot and start answering your questions.

If you have a specific issue with snapshot, then that is what the forum is all about. You should really ask the question in the help section.

However, attempting to second guess where it will break, or when it will ... I dont really think so.

Posted: **Thu May 18, 2023 4:06 pm**

Another good place might be to find out about getting into the testing of snapshot - you certainly could learn a bunch about testing it!!

Posted: **Fri May 19, 2023 4:51 am**

CharlesV

I have never seen they miss anyone.
I also don't see how there can be any real issues with a machine that makes miracles and unique history.
If it made perfect results all the time they would not be miracles.

I just have to keep an eye on the moon.

Posted: **Fri Sep 15, 2023 10:41 am**

You can not use the calendar if you want to know when the moon is full.
And the developers never say a word about it.
Or do they.?

Yes, maybe they do. It might just be a matter of knowing what code to look for.

Not long ago dolphin_oracle presented some new re-spins.

THAT was the moment when we all ought to realize that the moon was full.
And I guess it still is. I made a snapshot yesterday and except for a forgotten keyboard language it was absolutely perfect.

Do you want to thank me for a good bullet proof moon tip.? LOL

You can thank me by telling me how I can create a Snapshot that I can save files and config changes to live.
It might be simple, I just haven't found the trick yet. I keep on saving data that I can't find the next time I boot up.

Posted: **Tue Dec 12, 2023 8:37 am**

I have just upgraded from MX-21.3 Wildflower to MX-23.1 Libretto

It went very well so I should just be happy but I am not.
And it makes med feel ashamed because when I compare, I can't find anything seriously wrong with Libretto.
On the contrary almost everything is the same or seems even better, and I have to give the developers a lot of stars because they have been listening to the users wishes.

I know it is silly but I just can't help feeling sad because I have to say goodbye to Wildflower, and being ashamed doesn't make it any better.
Wildflower has been the best Linux distro I have ever used before.
With some years without support I had (and still have) a lot of basic things to pick up, and for me it has been a wild ride in the Wildflower field teaching me more about Linux and Xfce than ever before.

The gravestone I have made for Wildflower is a well working Snapshot that I can plug in to remember it by, and that helps a little.

Thank you Wildflower and goodbye, I will never forget you.

Posted: **Tue Dec 12, 2023 9:05 am**

@Jakob77
If you are using the default 6.1.xxx kernel you should immediately use MXPI to upgrade to the Liquorix 6.6.3-1 kernel. There is a serious bug that is affecting the current default kernel. The Liquorix kernels are not affected.

Posted: **Tue Dec 12, 2023 2:13 pm**

j2mcgreg wrote: Tue Dec 12, 2023 9:05 am @Jakob77
If you are using the default 6.1.xxx kernel you should immediately use MXPI to upgrade to the Liquorix 6.6.3-1 kernel. There is a serious bug that is affecting the current default kernel. The Liquorix kernels are not affected.

Thank you very much for telling me but you mess with my kernel strategy that is to trust the automatic update to give me what I need.
My philosophy is that if the default kernel goes down most of the MX users will also go down and it is not likely the developers will let that happen.
Do I have a point or am I just like one of the fools on Titanic that would not go into the first lifeboat that was launched.?
I did see something that was held back in an update, and I had to wait a day before I could complete it. So I assume they got it under control.
But maybe I better make one more snapshot of MX 23.1 soon. ;-)

Code: Select all

System:
  Kernel: 6.1.0-15-amd64 [6.1.66-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-15-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.1_x64 Libretto October 15  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Laptop System: Dell product: Latitude E7240 v: 00 serial: <superuser required> Chassis:
    type: 9 serial: <superuser required>
  Mobo: Dell model: 08YF01 v: A00 serial: <superuser required> BIOS: Dell v: A29 date: 06/13/2019
Battery:
  ID-1: BAT0 charge: 37.7 Wh (100.0%) condition: 37.7/45.1 Wh (83.5%) volts: 8.5 min: 7.4
    model: SMP DELL KWFFN33 type: Li-ion serial: <filter> status: full
CPU:
  Info: model: Intel Core i5-4310U bits: 64 type: MT MCP arch: Haswell gen: core 4 level: v3
    note: check built: 2013-15 process: Intel 22nm family: 6 model-id: 0x45 (69) stepping: 1
    microcode: 0x26
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 1446 high: 1585 min/max: 800/3000 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 1585 2: 1426 3: 1408 4: 1368 bogomips: 20751
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB
    filling, PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Haswell-ULT Integrated Graphics vendor: Dell driver: i915 v: kernel arch: Gen-7.5
    process: Intel 22nm built: 2013 ports: active: DP-2 off: eDP-1 empty: DP-1, DP-3, DP-4,
    HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:0a16 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26") s-diag: 583mm (22.95")
  Monitor-1: DP-2 mapped: DP-1-1 pos: primary model: Dell U2713HM serial: <filter> built: 2013
    res: 1920x1080 hz: 60 dpi: 82 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27")
    ratio: 16:9 modes: max: 2560x1440 min: 720x400
  Monitor-2: eDP-1 note: disabled model: BOE Display 0x05da built: 2013 res: 1920x1080 dpi: 125
    gamma: 1.2 size: 277x156mm (10.91x6.14") diag: 318mm (12.5") ratio: 16:9 modes: 1366x768
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 4400 (HSW GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Haswell-ULT HD Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:03.0
    chip-ID: 8086:0a0c class-ID: 0403
  Device-2: Intel 8 Series HD Audio vendor: Dell 8 driver: snd_hda_intel v: kernel
    bus-ID: 00:1b.0 chip-ID: 8086:9c20 class-ID: 0403
  API: ALSA v: k6.1.0-15-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I218-LM vendor: Dell driver: e1000e v: kernel port: f080 bus-ID: 00:19.0
    chip-ID: 8086:155a class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel modules: wl pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:08b1 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-1.3:3
    chip-ID: 8087:07dc class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 5 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
    sub-v: 500 hci-v: 4.0 rev: 500
  Info: acl-mtu: 1021:5 sco-mtu: 96:5 link-policy: rswitch hold sniff
    link-mode: peripheral accept service-classes: rendering, capturing, audio, telephony
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 port: f060
    bus-ID: 00:1f.2 chip-ID: 8086:282a rev: N/A class-ID: 0104
Drives:
  Local Storage: total: 119.24 GiB used: 58.28 GiB (48.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: LITE-ON IT model: LMT-128L9M-11 MSATA 128GB
    size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD
    serial: <filter> rev: 10B scheme: MBR
Partition:
  ID-1: / raw-size: 119.24 GiB size: 116.81 GiB (97.96%) used: 58.28 GiB (49.9%) fs: ext4
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 3 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 55.0 C mobo: 43.0 C sodimm: SODIMM C
  Fan Speeds (RPM): cpu: 3992
Repos:
  Packages: pm: dpkg pkgs: 2153 libs: 1091 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirrors.dotsrc.org/mx-packages/mx/repo/ bookworm main non-free
Info:
  Processes: 213 Uptime: 4h 12m wakeups: 2 Memory: 7.66 GiB used: 2.28 GiB (29.7%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)

Posted: **Tue Dec 12, 2023 2:19 pm**

The automatic update was broken. Whatever your philosophy is, that one went under with that boat.

Posted: **Tue Dec 12, 2023 2:20 pm**

I personally work at it like this...

- All my production and programming machines - are never on an automated anything. I decide what is updated and when. (including OS - still on MX 21.3 - and I love it! )

- My laptop is on mx21, but with the latest kernel updates turned on - And, I process these regularly and then watch them close. When I am comfortable with the new kernel here - then I update my big machines.

- My Testing, and test VM's, are all mx23, and I use this both to test things out, as well as push myself into MX23. When I am confident that I like ALL of it, and it will work as I want, then I begin migration.

Posted: **Wed Dec 13, 2023 11:00 am**

I am so completely under qualified to make that kind of choices.
Normally I am not first in line to download automatic updates but I do want them especially to keep Firefox safe.
If I have to do some important work on the Internet I might even search for updates first.
So if the MX update system goes down I will go down with it standing close to the bridge giving a full salute.
It will be awful but my backup is a life-jacket I have to trust. If a bug like a nasty hidden worm has affected ext4 on all drives it can maybe lead to a serious setback but I will have to see that start to happen or hear a very loud scream from the bridge before I believe it.
And no matter how hard it all crashes I can't imagine a situation where the snapshots I have made and tested some days ago suddenly won't work anymore.

Posted: **Wed Dec 13, 2023 11:06 am**

I do love your theatrical sense of drama.

If it breaks, I assume you have a recent snapshot that you can put back. Or you install clean. Fun fact: nobody dies.

Posted: **Wed Dec 13, 2023 11:20 am**

@Eadwine Rose you made me chuckle :-) Love it!

Posted: **Sun Dec 17, 2023 1:57 am**

Jakob77 wrote: Tue Dec 12, 2023 2:13 pmThank you very much for telling me but you mess with my kernel strategy that is to trust the automatic update to give me what I need.
My philosophy is that if the default kernel goes down most of the MX users will also go down and it is not likely the developers will let that happen.
Do I have a point or am I just like one of the fools on Titanic that would not go into the first lifeboat that was launched.?
I did see something that was held back in an update, and I had to wait a day before I could complete it. So I assume they got it under control.

It's all good, the Titanic is unsinkable, so you don't need to regularly make backups.

Posted: **Sun Dec 17, 2023 3:37 am**

Looks like the thread has lived its purpose, locking it.

MX Linux Forum

Chat about Snapshot

Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot

Re: Chat about Snapshot