On 30/08/2019 05:08, Peter Suetterlin wrote:
Anton Aylward wrote:
On 26/08/2019 12:23, Knurpht-openSUSE wrote:
IME btrfs is rockstable. Combined with snapper snapshots it allows you to roll back to a previous state of the fs, f.e. when updates mess up things. Shouldn't happen, but still. I use the feature a lot: install something to support a user, when done rollback to before the install of that something. Awesome.
Gee WOW! And here an I doing simply "zypper install/zypper remove" to achieve much the same thing.
So zypper allows you to roll back to packages that are no longer in the repository? That was the reason for the only rollback I've done in 3 years TW (broken X packages).
Well MY use case that annoyed me immensely was that snapper took a snapshot EVERY TIME I ran zypper to install a package to try out, and 'addition'; that goes for kernel updates, and it's why I update kernel rather than patch the kernel!. I can't say that the "no longer in the repository" situation is one I've met ... ... EXCEPT ... ... when I've been forced to upgrade, for example from 42.3 to the 15.x because of the repositories going away. No so much "no longer IN the repository" as "no longer THE repository"!
One thing I sometimes use is the simple way of checking which files have changed, and to easily do a diff between versions (e.g., of config files).
Ah. Well perhaps you've never used VAX VMS ... Yes, I've done diff between the config files; zypper has this thing that it won't simply update them if the original has been changed, so I have lots of later .rpm files under /etc that I can 'diff' toe see what updates I'm supposed to be getting BEFORE I install them, often using 'sdiff' to pick and choose between the old and the new. Nothing whatsoever to do with snapper, thank you! In other areas I set up my applications to take backups or snapshots as I'm working; in a development IDE I have a RCS system in place. Its not simply about 'snapshots' its often about documenting the snapshots and sometimes branching as ideas develop and I try them out. Failed ideas are valuable too and need to be preserved. And WHY they failed needs to be documented. A good RCS allows for all this. So sorry, its not just snapper that annoyed the hell out of me, even after much configuration, it was BtrFS as well.
personally, I found that on a single user, personal machine having btrFS, 3spcially saving images for every zypper update change, was too much overhead.
I sort of agree there, that's why I removed/commented <!-- <solvable match="w">*</solvable> --> in /etc/snapper/zypp-plugin.conf.
Right. I configured the hell out of that, removed modules and more, but as I said, the root of the problem was BtrFS. I got rid of that, am using Ext4 for my, mostly, stable RootFS. -- 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