Any thoughts or idea’s about this. . . might be nice. . . maybe snapper, and btrfs-assistant will no longer be of use? The article was posted on Phoronix.com.
Rich;)
Any thoughts or idea’s about this. . . might be nice. . . maybe snapper, and btrfs-assistant will no longer be of use? The article was posted on Phoronix.com.
Rich;)
Serious answer:
It’s a GUI frontend for browsing snapshots and eventually restoring files, it wont set up the whole snapshot subsystem (e.g. snapper which KDE Linux is using) or allows to configure it with a GUI (e.g. btrfs-assistant). It’s a complementary tool serving a different purpose.
Hmmm…guess I’ll have to switch to KDE so I can disable this. ![]()
You would have to switch to KDE Linux…
Probably storage so cheap this days ![]()
Absolutely stupid idea in any general user case.
It can be useful only in very specific professional work scenarios.
But KDE Linux basically test poligon so ![]()
Btrfs snapshots take very little space unless you have a large rate of data change or keep them for a very long time.
Taking hourly snapshots and giving users an easy way to restore old versions sounds like a great feature for the majority of desktop users.
If you do not have large rate of data change, you do not need this at all.
And if you have. Oh boy.
Like photos and videos and stuff. Cats from imstagramm.
Tg can download 200Mb for 30 min.
Average user do not want this thing. And he will get trobles with it. And then will be angry when figure out what the hell it is.
Some user even have movies on their PCs ![]()
And sometimes even delete them.
And games. Like one game 50GB easy.
And then Average user deletes it in order to get space for another game.
Average users play games.
I take hourly snapshots myself and they have saved me many times.
That is no problem. When I say high rate of change, I am talking about huge quantities of data, not a few gigabytes.
Yes, so do I, that doesn’t cause any problems.
Yes, I have lots of games too.
It is also about having the proper snapshot retention. If you set it up properly, it works great and the average user would never see any issue from it. But they would get the benefits.
I snapshot my home folder. Imho that should be the default setup. I’m all for it. It’s very useful.
But then, steam games in the home folder or large (media) files will wreak havoc for a significant amount of users. That is a valid argument. It will be a constant point of conversation and create support demand by confused users.
Yes. But you, Dalto, by any way shape or form, not an average user.
You correct that this indeed can be usefull.
Browser cache will bring horror ![]()
Yes. But someone will need to do this correct setup.
And assume user will not deviate.
And users tend to put things on desktop.
Including games downloads and such. Files of any size or form. All in one place. Extract archive of home photos, find one, and delete whole thing.
And such setup reqire person to put files on different places and keep awareness of how it work.
For me personally - it would be too much. (I once in life had perfect organized files, and then I lost them in cursed wd hdd backup incident).
Only in case of this one special PC or laptop I am using for very specific important business professional stuff.
My personal home PC is incredible volitile for such stuff ![]()
BTW. I am working on system snapshots for Arch on bcachefs. But the more I progress there more doubts I have. It brings complexity I do not like at all ![]()
This is not a problem. Snapshots don’t work this way.
You can simply right click on a file and say show me the old versions of that file and pull out the one you want. It isn’t an all or nothing proposition. It is a simple solution made easy for the average user.
The issue is deleting. People expect you can uninstall a 100 GB game to make space and install another 100 GB game. If uninstalling don’t materialize in 100 GB of free space … well “I don’t ask for that” will ensue.
Hopefully KDE Linux will explain how to mitigate the issues brought up here. BTRFS is very flexible, if used correctly.
Direct and to the point . . . ‘if used correctly’. . . that’s it in a ‘nutshell’.
Rich ![]()