I'm hoping to switch off my old SPARC hardware soon (anyone want a
Sparcstation10?) and onto Intel hardware. I'm wondering if I can just
unplug my chain of scsi disks from one machine and plug them into the
new one and have the filesystems mount intact, or if I will have to move
the data across a network?

Thanks,
chris

* Christopher (cak@dimebank.com) wrote:
> new one and have the filesystems mount intact, or if I will have to move
> the data across a network?

The "data" will be fine, yet the bootloader, kernel and the whole
userland binaries are sparc and thus wont run on the intel.

"Reinstall" the OS, but any "data" would be fine wrt to you subject -
byte ordering doesnt apply here.


ciao
--
"Unix was the first OS where you could carry the media and system
documentation around in a briefcase. This was fixed in BSD4.2."

On Tue, 4 Nov 2003, Christopher A. Kantarjiev wrote:

> I'm hoping to switch off my old SPARC hardware soon (anyone want a
> Sparcstation10?) and onto Intel hardware. I'm wondering if I can just
> unplug my chain of scsi disks from one machine and plug them into the
> new one and have the filesystems mount intact, or if I will have to move
> the data across a network?

network. ffs data structures are stored in host-endian format.

--
"The contagious people of Washington have stood firm against diversity
during this long period of increment weather."
- M. Barry, Mayor of Washington, DC

Christopher A. Kantarjiev <cak@dimebank.com> wrote:

> I'm hoping to switch off my old SPARC hardware soon (anyone want a
> Sparcstation10?) and onto Intel hardware. I'm wondering if I can just
> unplug my chain of scsi disks from one machine and plug them into the
> new one and have the filesystems mount intact,

I don't think OpenBSD/i386 can read a Sun disklabel.
FFS on-disk structures are written in the host endian order, and
OpenBSD doesn't support accessing a differently endianed FFS.

> or if I will have to move the data across a network?

Yes.
And of course some of that data may be endian-sensitive, too.

--
Christian "naddy" Weisgerber naddy@mips.inka.de