From owner-freebsd-sparc64@FreeBSD.ORG Sat Feb 11 05:52:19 2006 Return-Path: X-Original-To: freebsd-sparc64@freebsd.org Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 79E8616A420 for ; Sat, 11 Feb 2006 05:52:19 +0000 (GMT) (envelope-from jrtanis@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id C69FD43D46 for ; Sat, 11 Feb 2006 05:52:18 +0000 (GMT) (envelope-from jrtanis@gmail.com) Received: by nproxy.gmail.com with SMTP id x37so10508nfc for ; Fri, 10 Feb 2006 21:52:17 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=COaDb+/TTtKGpImewJEmhB1C82llnBSNApcI/2gULehSwUfGhLod3YpoASFx+PTz7qP9wCyE6oaQTPwr+wEuJ0e1CpTxc0Okt03JS+VGcb6REqRb+vtFGj4SgS15lK7tZ6jLa0h4SpOKvWrUz6zCHyY2MlWXB8kxVlB7Ew6oJew= Received: by 10.48.248.6 with SMTP id v6mr23401nfh; Fri, 10 Feb 2006 21:52:17 -0800 (PST) Received: by 10.49.34.9 with HTTP; Fri, 10 Feb 2006 21:52:17 -0800 (PST) Message-ID: <65dcde740602102152r2fa8b788r1d035222a66ec958@mail.gmail.com> Date: Sat, 11 Feb 2006 00:52:17 -0500 From: James Tanis Sender: jrtanis@gmail.com To: Kris Kennaway In-Reply-To: <20060210201417.GC67059@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43EA72B9.5070307@gmail.com> <20060209203330.GA11506@xor.obsecurity.org> <65dcde740602100951k17bf8330o15e1b78bd2ee55be@mail.gmail.com> <20060210201417.GC67059@xor.obsecurity.org> Cc: freebsd-sparc64@freebsd.org Subject: Re: moving disks between archs X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Feb 2006 05:52:19 -0000 On 2/10/06, Kris Kennaway wrote: > On Fri, Feb 10, 2006 at 12:51:18PM -0500, James Tanis wrote: > > Tar will work, but not a drive formatted on an i386 with a tar file on > > it. > > Not if you store the tar file in a UFS filesystem on the drive, but I > suggested writing it to the raw disk where it is just a stream of bits > and therefore endian-neutral. > That would imply that endianness is a function of the OS/filesystem rather than the architecture, which is wrong. If you don't take my word for it, a quick google will find you, (http://developers.sun.com/solaris/articles/support_for_x86.html).. "File systems are neutral to endianness in general, and swapping files between Solaris SPARC and x86 is not an issue. But applications storing raw data that can be shared between platforms would be an issue. For example, if an application on the Solaris SPARC platform writes the data structures in a raw format to the files, then the data stored in these files would be endian-dependent." > > P.S. Don't top-post, it ruins continuity. > Bah, think outside the box. > If its a sparc, why not just plug it into the network temporarily? > > Ive never seen a sparc without an integrated ethernet card. > > > > On 2/9/06, Kris Kennaway wrote: > > > On Wed, Feb 08, 2006 at 11:37:45PM +0100, Paolino wrote: > > > > I'm using a disk to bring data to an network-isolated machine runn= ing > > > > sparc. What filesystem can I use to get some compatibility? > > > > > > > > Having placed an UFS from an i386, makes it unreadable on the sparc= , IRC > > > > guys tought me it's an endiannes problem. > > > > > > > > Is tar going to work ? > > > > > > tar will work, so you can always write the tar file to the raw disk > > > (i.e. use no filesystem). > > > > > > Kris > > > > > > > > > > > > > > > -- > > James Tanis > > jtanis@pycoder.org > > http://pycoder.org > > > > > -- James Tanis jtanis@pycoder.org http://pycoder.org