On 02/09/2015 03:19 PM, John Andersen wrote:
Meanwhile perhaps someone can explain how I can set snapper not to snapshot tmp at all.
As I said. Having /tmp on a separate file system allows for a number of "security" advantages. I've already mentioned having tyat mounted nosuid,noexec, and how a runaway process that fills /tmp still leaves the rest of the system usable. Having a separate /home as well will let the user log in; we're back to the crazy idea of everything being the one BtrFS which I see as high risk. Yes, the optimization available with BtrFS is wonderful. So is the idea of having your system snapshotted, even /home, so that changes, for whatever reason, can be reversed. But do a proper risk analysis/needs analysis rather than just blue sky this. I can see changes to syustem config, rolling back an instalation of a new library to the old one, things like that, but at some point the 'everyting and the kitchen sink' gets to be too much. Yes, if snapper could easily exclude certain directories, specifying them in the config, some of these objections could be ignored. But I see nothing in any of the documents and man pages indicating this capability. Perhaps snapper doesn't need to be as complex as, say, rsync, but an exclusion list would be valuable. And I think /tmp should be a default in such a list. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org