similar to: meta data stored in separate file?

how do you backup system files like /etc/ over ssh to another machine and keep permissions the same on the remote backup location ? i tried using -a flag, but because i'm connecting through ssh i'm not using Rsync module on the remote computer and therefore i cant write files as root so -a flag is not working. all the files are being written with owner SSH_USER and group SSH_USER_GROUP i

Is there a way to backup files to a remote machine on which I don't have root permission, while preserving their uids/gids? I know that only the super-user can set the owner and group of a file, so what I am actually looking for is a tool that would store the actual uids/gids of all files that are backuped by rsync in a kind of meta-file. This file could then be used to restore the files

i (and others) have missed messages on centos-devel as well. did other people not see the 4.7 announcement message? i'm wondering if the centos list server is having some kind of issue.

while in firefox if i use arrow keys in text fields, it acts very oddly. starting at the beginning of the line it works fine for a few characters and then jumps to the end of the line. backarrow jumps backwards from the end of line to within a few chars of the beginning. anyone else seeing this?

after this latest centos 5 kernel update, i am seeing 40 second delays on automount points. nothing in the rpm changelog looks obviously related to autofs and the autofs module seems to be the same as the previous kernel. i'm starting to do some strace'ing and other debugging, but nothing has jumped out at me yet. i'm hoping someone else has seen it so i know i'm not alone

Right now, if you want a faithful backup of a system, you must either have root access on the target machine (for chown, mknod, ...), or you have to arrange for fakeroot/pretendroot to wrap itself around the rsync server to catch all these permissions/etc and keep them in a database file. Also, the fakeroot approach isn't exactly reliable (premature exit -> all SAVED permission

I have a client who has a bunch of macs accessing some samba shares, and they write these ._filename and .DS_STORE files all over the place, he would perfer it to not write these files at all. Anyone ran into this issue? what would be the best way to prevent these files from getting written onto the shares? veto? -- Matt Pruett <entelin@logicaldreams.net>

i see one available in the repos, but i don't recall seeing any announcement about it. from googling, it does seem to be real, but still a bit disconcerting to not have an announcement about it.

sorry i figured this out after deleting the other parts of the thread. just run vino-preferences as the user who runs the main x display. it will have various options to enable and as soon as you do that you can get to hostname:0 via vnc. works quite well.

i've downloaded the new 2.6.9-34 kernel src rpm and keep getting signature issues or md5 issues if i tell rpm to ignore signatures. it seems that maybe the master copy is corrupted?

there doesn't seem to be a src.rpm for the newest kernel up on mirror.centos.org. i need to apply a local patch. is it the same as the upstream version? also, the centosplus unsupported version is either missing the -doc package or people need to know to do some manual intervention to get the regular version to replace the old unsupported version.

Hello everybody! Out of curiosity: What (backup) solutions do you use to let rsync store device files and ownership permissions without root privileges? I found out about "fakeroot" so far. Is there actually a practical use for the "--super" option? I didn't find anything as fakeroot doesn't need it... Additionally it would be a nice idea to refer to

redhat did apply the opendesktop patch to build the iso8859-1 fonts, but then they forgot to rebuild the fonts-xorg package to pick them up. they have done some magic with how that happens such that you have to build the full xorg-x11 with a special %define set, and then go rpm2cpio stuff and tar that and blah blah blah. i am trying to work through this and i have whined at redhat again. and

I have setup two samba domain controllers, both have basicly the same configs and use the same ldap database backend. Often however when logging in users will get a "domain cannot be contacted" error, attempting to login multiple times will eventually get them in and it will work fine from then on. The question is, is there anything else I really need to do to make this work correctly?

Hi, I installed "osmar". Q: How do I learn what methods it contains. I tried > Help, things like that.... Thanks cellurl [[alternative HTML version deleted]]

the rsync in centos 4 (a recompile of rhel4) is version 2.6.3. and under certain circumstances it will segfault when run in daemon mode. i have tracked it down to the nss code in libc. so this could be a general libc bug, but it is possible that rsync is doing things that don't help matters any. the problem manifests when you have chroot mode on (which seems to be the default), have

Hi Chris, > There's a couple of headless systems on the LAN where login security > is important to me and I've been thinking about the relative merits of > password and public-key authentication. > <snip> At home, I have a smaller LAN than you, but at $DAYJOB I work with much bigger fleets. Whether at home or work, everything is Linux-based, and OpenSSH is the primary

Hello, I am testing mail_crypt plugin with per account encryption and wanted to generate a new keypair for an account but noticed that I now end up with 2 keypairs where one is active and the other inactive as you can see below: $ doveadm mailbox cryptokey list -u email at domain.tld -U Folder Active Public ID yes 7b140b4f3d6d68eed2c59259ac5e6f6a280dc82990292dc415b4100d6c797f67

Dear All, I just tried to use 8192bit keypair for Tinc VPN connection. The connection is unable to build up. After reduce the bit of keypair from 8192bit to 4096bit. Everything is resumed to normal. How large of public/private RSA keypair can support for TINC VPN 1.0.22 on Windows platform? Regards, ERIC P Please consider your environmental responsibility. Before printing this e-mail

It seems that users may be disclosing unintended public key info when logging into remote hosts. Use of the words keypair/keyid/etc have been bastardized. Signature is likely better. Note also, the author may be without clue. Setup: [g] - refers to an administrative group of hosts [n] - refers to a host within that group ws[g][n] - management workstations [trusted] User ssh-add's keys for