Chat about Snapshot

[Jakob77]

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.

[Jakob77]

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.

[Jakob77]

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.

[j2mcgreg]

@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.

[Jakob77]

@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)

[Eadwine Rose]

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

[CharlesV]

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.

[Jakob77]

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.

[Eadwine Rose]

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.

[CharlesV]

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