Gustin Johnson wrote: > > Everything is fine for the file .DCOPserver_linux-y532__0, but the > owner > > and group for the link .DCOPserver_linux-y532_:0 are set to "root - > > root" instead of "spinymouse - users". > > It is possible that the DCOP process put those files in your home > directory and set the permissions to be what they are. On my Xubuntu > UPMC they are owned by my user, so I am not sure what is happening there. > > If I am archiving my user directory, I tend to do so from another > account or via a live CD/USB, but then I rarely archive my home folders. > All important data lives on a server. I have an archive of the basics > (.ssh .gnupg .vimrc .screenrc .bashrc) so I can get up and running > quickly. But other than that I really don't care about my home directory.
You are right, I didn't think about that /home is just /home and the files aren't relevant for the whole Linux. I only need personal files, KDE settings, .bashrc and some audio settings. I run rsync to backup Suse from 64 Studio and to backup 64 Studio I run it from Suse. > > Because of -a and rsync running as root, owner and group should be > > preserved?! > > The -a should preserve existing permissions, running as root should > prevent access denied issues. Of course if extended ACLs are used, then > running as root does not guarantee that you will be able to read the > file, at least not without changing the ACLs first (similar to how > Windows servers do file/directory ACLs). > > Hth, Hm? I have to read about that, but not within the next days. The next days I only will make music with Linux. I think everything is backuped and I can ignore that "pseudo"-errors for the moment. Thank you.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
