3 ms·
> but did you try that in practice? Not with TrueCrypt. You can just ignore the warnings (if it doesn't cause a crash). "chattr +i" makes a file really read-on
by slashdotaccount 13y ago
> but did you try that in practice?
Not with TrueCrypt. You can just ignore the warnings (if it doesn't cause a crash). "chattr +i" makes a file really read-only (you can undo it with "chattr -i"). GTK library wants to write recently accessed files there, and fails, emits the warnings. It's safe to ignore them.
- tverr_bjelke 13y agoOK I did that and the result was the above output. And then still in same truecrypt session I saw my recently used file - while the bookmarking file still was empty. So closing truecrypt reopening the recently used files list was empty. So that seems to work. thx Question for me is, how the hell can a normal process trigger root-owned read only filed to becom overwritten and chowned to normal user? What is GTK magic doing there?? I dont understand the above session! maybe someone can explai that to me?