oh shit we have to do this manually ourselves? lol I forgot what it was like to use linux.
I'm still new to the whole ssd thing as well and more and more I dislike them lol. Had a couple data losses with the one i use and sleep mode using qubes. Its nice they don't break if something crashes but they sure lose data easy.
Got a machine linux and windows don't sleep right always ones with an ssd lol.
according to these qubes doc it says it can hurt performance though if added to fstab? It says to use a systemd or cron job instead. Also says templates and vms already have trim enabled automatically. it also says if we are using luks to add it to crypttab or it won't work?
But is this really nescessary to do in dom0? Will it make any difference if all the templates and vms already have discard by default? And so does that mean we make the cron job for dom0 we also have to add discard to crypttab?
https://www.qubes-os.org/doc/disk-trim/
I apologize if I misunderstand this stuff is confusing.
I dunno man I keep hearing about how newer ssd's are supposed to be better. but I got a windows system with an m.2 and its horrible. can't use sleep when using on board audio card. still disabled indexing, superfetch, search and anything else that causes hdd space cause it would cause instability and corruption.
Seems like right now every pc that has an old or new ssd using sleep mode, has instability after resume, no matter what os they are using.
My Qubes dom0 got corrupted once, cause I was using an ssd when resuming from sleep, its even worse in 4.0. and that kind of sucks cause without magic packet waking it up i considered sleep a security feature. but I guess with ssd you can just shut it off and on even better and same thing basically.
But are you saying in RC5 and on trim is enabled by default in dom0?