-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Back In Time (root)" problem claimed in a blog post (lacking details) #819
Comments
I asked the blogger to add more informations to this issue here. |
Hello, That's all I did. those are the packages were installed: 'backintime-common' and 'backintime-kde4' here are some info of the packages: Name : backintime-kde4 Name : backintime-kde4 Name : backintime-kde4 0 ✓ root@workstation ~ $ urpmq -i backintime-common Name : backintime-common Name : backintime-common Name : backintime-common And I'm using Mageia 5. Linux 4.4.88-desktop-1.mga5 #1 SMP Thu Sep 14 00:03:58 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Thanks |
Do you still use version Please feel free to ask if you need help to build/install the development version. |
Closed as outdated and not reproducable. |
Has anybody come across this issue as described in the blog URL below?
http://unix.cafe/wp/en/2017/09/restore-ownership-octal-permissions-backup
Quoting here; this is not something I experienced myself
I was able to see the /root contents. I mean my normal daily used user was able to read and write to /root, /boot, /usr …etc. WTH! I said! When I checked their permissions I found that they were really a mess. Some of them were even being owned by my user instead of the right owner.!
I ran to the older snapshots I have, that were taken by CrashPlan, and compared the permissions. Guess what? Yeah you’re right they were indeed different. Then I realized that, there must be a real nasty bug in the Back In Time. Fortunately, I was lucky enough to discover this issue before it was kinda too late.
End Quote
The blog post lacks all detail as to how this problem was triggered, so I'm just wondering.
Thanks.
Ken
The text was updated successfully, but these errors were encountered: