From owner-freebsd-isp@FreeBSD.ORG Thu Apr 24 09:50:57 2003 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 559B637B401 for ; Thu, 24 Apr 2003 09:50:57 -0700 (PDT) Received: from federation.addy.com (addy.com [208.11.142.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id D555343F85 for ; Thu, 24 Apr 2003 09:50:55 -0700 (PDT) (envelope-from jim@federation.addy.com) Received: from localhost (jim@localhost) by federation.addy.com (8.9.3/8.9.3) with ESMTP id MAA56054; Thu, 24 Apr 2003 12:50:53 -0400 (EDT) (envelope-from jim@federation.addy.com) Date: Thu, 24 Apr 2003 12:50:53 -0400 (EDT) From: Jim Sander To: "Dave [Hawk-Systems]" In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-isp@freebsd.org Subject: RE: disaster recovery after rootkit -> MySQL and user accounts X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Apr 2003 16:50:57 -0000 > mysql daemon will not start Piece o' cake man... I've copied many a binary .ISM file between systems and never had a problem- I just recently copied quite a lot of data from a redhat box to FreeBSD without any glitches simply by scp'ing the whole mysql datadir. I doubt Debian does anything too terribly different. MySQL has its own data file format(s) so there's not a lot to worry about except in HUGE version jumps. MySQL is *very* good about remaining backward compatible, and allowing for easy "upconvert" of data. The only trouble I've had has been moving database files from FreeBSD to a Mac OS-X, and I suspect that's more an Endian-ness issue. -=Jim=-