At least if you don’t, please apologize to the neighbours before you get back in.
2 Likes
I too make sure to be p-less before going out, all the extra p I put in folder names for fun
I think the wiki should be updated if possible.. or even better there should be some module in Systemsettings that handles everything automagically.
2 Likes
The wiki is being actively worked on at present. Suggestions are of course welcome. 
While that would be nice, SystemSettings, at least the application systemsettings is a KDE application, not a Manjaro one.
As far as I know if one uses all the defaults on install calamares will create a swap partition or subvolume, depending on your choice of file system (EXT4 or BTRFS). In my experience the swap partition (or subvolume) will be too small for Hibernating, (if one choose swap with hibernate).
As far as having a graphical module, that is anyone’s guess.
Keep in mind that to set up the physical parameters of the swap subvolume or partion may also mean resizing other subvolumes or partitions, so an automagic solution might well be not doable.
1 Like
@acca85, I need to correct something I said earlier.
I had unknowingly recommended a method that disables CoW for the entire file system.
If you used the nodatacow mount option on @swapp, that option does not apply only to that subvolume, it applies to the whole btrfs filesystem on that device. Since you’re using Timeshift, you definitely don’t want CoW disabled.
If you made that change, nothing is broken. But snapshots will grow much larger and lose their space efficiency until you remove it. Just remove nodatacow from your fstab and reboot, and things will go back to normal.
Sorry about that! Now I know! 
Things are still improved, and your swapp file is still in a happier isolated place in its own subvolume.
I’ve been using btrfs for a few years, always playing with it and learning new things. I was actually unaware you couldn’t disable CoW for a specific subvolume.
“You can do files and folders, subvolumes is even easier, right?”
Wrong. Mount options affect the whole file system In Linux of course. And this no-CoW exception only works per inode.
1 Like