From owner-freebsd-sparc64@FreeBSD.ORG  Fri Feb 10 20:14:18 2006
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
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 9650B16A420
	for <freebsd-sparc64@freebsd.org>; Fri, 10 Feb 2006 20:14:18 +0000 (GMT)
	(envelope-from kris@obsecurity.org)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5129043D45
	for <freebsd-sparc64@freebsd.org>; Fri, 10 Feb 2006 20:14:18 +0000 (GMT)
	(envelope-from kris@obsecurity.org)
Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196])
	by elvis.mu.org (Postfix) with ESMTP id 35DB71A3C1B;
	Fri, 10 Feb 2006 12:14:18 -0800 (PST)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id 8E9985214D; Fri, 10 Feb 2006 15:14:17 -0500 (EST)
Date: Fri, 10 Feb 2006 15:14:17 -0500
From: Kris Kennaway <kris@obsecurity.org>
To: James Tanis <jtanis@pycoder.org>
Message-ID: <20060210201417.GC67059@xor.obsecurity.org>
References: <43EA72B9.5070307@gmail.com>
	<20060209203330.GA11506@xor.obsecurity.org>
	<65dcde740602100951k17bf8330o15e1b78bd2ee55be@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="OBd5C1Lgu00Gd/Tn"
Content-Disposition: inline
In-Reply-To: <65dcde740602100951k17bf8330o15e1b78bd2ee55be@mail.gmail.com>
User-Agent: Mutt/1.4.2.1i
Cc: freebsd-sparc64@freebsd.org, Kris Kennaway <kris@obsecurity.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 <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>, 
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2006 20:14:18 -0000


--OBd5C1Lgu00Gd/Tn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.

Kris

P.S. Don't top-post, it ruins continuity.

 If its a sparc, why not just plug it into the network temporarily?
> Ive never seen a sparc without an integrated ethernet card.
>=20
> On 2/9/06, Kris Kennaway <kris@obsecurity.org> 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  running
> > > 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
> >
> >
> >
>=20
>=20
> --
> James Tanis
> jtanis@pycoder.org
> http://pycoder.org
>=20

--OBd5C1Lgu00Gd/Tn
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iD8DBQFD7PQYWry0BWjoQKURAjWTAKDXUzPH6IwMm97vr9JKL3qaPrrvZgCg8aOY
9/yiwCpyl+eknxr78VjdNK4=
=oJDC
-----END PGP SIGNATURE-----

--OBd5C1Lgu00Gd/Tn--