Laptop MX Linux

[MXtones]

Well, the linux community is somewhat divided regarding systemd. MX Linux is "systemd-ready", but utilizes sysvinit by default. If you want to know more, this is a good place to start:

https://wiki.archlinux.org/index.php/Systemd

Cheers

[tone2]

Well, the linux community is somewhat divided regarding systemd. MX Linux is "systemd-ready", but utilizes sysvinit by default.

Hi MXtones,

Yes I had noticed that!

Well I prefer simplicity of comprehension, I'm sure systemd is great, but I'm not after any bells and whistles, so if I can avoid it I suppose I will...until I'm more proficient at least.

If no one sees any issue then I guess I'll just re-try what I described earlier in making a new swapfile and see what happens now I've cleared 15G space on my SSD.

Cheers,

[MXtones]

I've never tried to create a swapfile manually. If in doubt about the commands, manpages are your friend, which exist for a lot of commands/programs - simply type "man APPNAME", e.g.:

Code: Select all

man gparted

Gparted is the gui for "parted" which is a partition manager that you could use to create a swapfile.

The fstab entry for your swap looks correct, assuming that the UUID is correct as well.

[MXtones]

So I went and set up a swapfile following this tutorial:

https://www.howtogeek.com/455981/how-to ... -on-linux/

The author advises not to use 'fallocate' for that, but 'dd' instead.
Another thing I realized is that the swapfile is just that: a file - as opposed to a partition, so one doesn't have to add an UUID in fstab (technically everything's a file in linux).
I'm still testing, but so far everything is working as expected.

You might also wanna look into this:

https://mxlinux.org/wiki/other/zram/

[Stevo]

If you do want to mess around with your system's guts, it's a good idea to make restore points with Timeshift.

In fact, it's never a bad idea to have restore points, period.

[tone2]

If you do want to mess around with your system's guts, it's a good idea to make restore points with Timeshift.

In fact, it's never a bad idea to have restore points, period.

I haven't lost interest in this thread, I just haven't had a chance to get back to working it out. But I should on the weekend.

And yes, I take your point, I really need to learn how to use Timeshift.

Cheers,

[Stevo]

Timeshift has a firstrun setup wizard, so really is pretty dead simple to use. By default, it only backs up your system, not any data you have in your home or other data partitions, and it doesn't compress the files.

[tone2]

I have an update....

So following the approach I previously outlined, I tried using 'sudo s2disk'. And I thought it all seemed to work however I realised every time the system started up the same things were open (folders and programmes) irrespective of what was open when I shut down. It was like it kept loading the same snapshot in time.

Then after trying a variety of things like I noticed that in /etc/uswsusp.conf the "resume device" kept changing to be set as: /dev/sda2. It is currently = dev/disk/by-uuid/f6fa5d86-ca03-41b8-b59e-ce427520787a

For some reason, which it change to itself to be.

Similarly when I type: sudo swapon --show, then it shows: /dev/sda2 partition 2G 0B -2
is still present.

But the strangest thing is that even though I've removed the modification line I previously added in the /etc/fstab file and I've sudo rm /swapfile, (so I've removed the swapfile I created) NOW EVERYTIME I RESET OR SHUTDOWN and Boot normally, it restores the system as it was when I shutdown!! That is to say what is currently open, ironically just like you would expect from a Hibernation. Its the strangest thing, I have no idea how/why it's doing it.

So I'm pretty baffled lol. Can anyone explain maybe why this is so?

Cheers,

[MXtones]

Please compare the steps you've taken with the explanation given here:

https://wiki.debian.org/Hibernation/Hib ... _Partition

[tone2]

Please compare the steps you've taken with the explanation given here:

https://wiki.debian.org/Hibernation/Hib ... _Partition

Hi MXtones, thanks for the reply.

I think it's functionally the same with the following exceptions:

(Note, this is not an exception but please note in following them I changed suwsusp.conf line back to: resume device = /dev/sda1)

I modified the resume device = /dev/sda1 into the suwsusp.conf as it was previously like SSID or something automatically (which I defined from typing: swap-offset /swap)

Then I ran:
update-initramfs -u

And I think those are the only differences.

I will say I think running sudo s2disk worked much better this time. However, whenever I Shutdown or Restart it still saves my session like a hibernate. Do you have any idea how or why it's doing this, and how I can turn that off? (admittedly not the worst problem in the world, kind of 'be careful what you wish for' lol).

Thanks in advance,