X-Spam-Check-By: sourceware.org Message-Id: <200601272351.k0RNpKPV025534@tigris.pounder.sol.net> From: cygwin AT trodman DOT com (Tom Rodman) to: cygwin AT cygwin DOT com Subject: Re: Warning: Never use M$ files+settings transfer wizard to move a cygwin installation. In-reply-to: <002201c622a1$f1ebf690$a501a8c0@CAM.ARTIMI.COM> References: <002201c622a1$f1ebf690$a501a8c0 AT CAM DOT ARTIMI DOT COM> Date: Fri, 27 Jan 2006 17:51:19 -0600 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Thu 1/26/06 17:57 GMT "Dave Korn" wrote: --snip > I made the terrible mistake of trying to use M$ migwiz.exe to > recover my old cygwin installation from a dead machine's drive to a > new one. > > I thought it might be just a simple archiver that would conveniently > help move all my stuff across without losing ACLs and so on. I use ntbackup (backing up to a file), it preserves the DACL, owner and posix group. I have a wrapper bash script for ntbackup , so I can call it from with in an ssh session. If your moving to a new domain, you can do all sorts of DACL, owner, and posix group, (recursive) edits with "setacl": http://setacl.sourceforge.net/html/examples.html -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/