the transition between sleep and shutdown is a fluent one. a shutdown is just a sleep that is deep enough. when the sleep is deep enough, it might be worth decoupling from energy-hungry consumers such as spinning disks in a laptop.
Fucking with fstab without fully knowing what I was doing was a powerful early Linux lesson for me lol. Luckily I was using Time Shift so it was very easy to rollback.
Eventually got it working though, and now I understand how it works (though I haven't needed to edit it since switching to bazzite)
I took a while to figure out my error at the time, but I think I managed to unfuck it using recovery mode eventually. Now I know why people generally recommend mounting scripts instead of fstab.
Bazzite is atomic and immutable, so you cannot (or at the very least, it's made difficult, and its not recommended) alter anything on your OS partition. Like you literally don't have permission to. I couldn't edit fstab if I tried.
So you install programs with flatpak, distrobox (works very well), and on the occasion you really need to (like for VPN software or something), you can "layer" an app onto your OS image.
Basically, every time you turn the PC on, the OS initializes to the saved image. It's incredibly stable.
If you install something, nothing changes until you reboot. If an update breaks your OS install or anything like that (very very rare), you can just simply rollback to the previous OS image.
It's a little bit of a learning curve to figure out how to do some things, but once you get it, it's almost boring how stable it is lol.
I used to use Time Shift, and took regular snapshots, so I could rollback whenever I fucked up fstab or something else. So if you're not looking for something as drastic as an immutable OS, maybe look into that?
If you want more info, look up "ostree" and "rpm-ostree"
fstab table = filesystem table table
smh my head
rofl on the floor laughing