Hello,

as written in the subject, I have prepared a fresh Mystic BBS latest alpha install on my local server, running Debian 8 64bit. Privileges, permissions
and basic configuration is ready, like also ports NAT and start/check
scripts. I would like to ask your help, driving me in the rightest way to migrate all my MBBS configuration *lot of* from my RPi1 to this machine, thanks!

Regards,


 I N D R I D / C O L D 
First come smiles / Then come lies / Last is gunfire 

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Miskatonic BBS | telnet://rasppi.servebbs.org (21:1/165)

On 03/16/17, Indrid Cold said the following...

Hello,

as written in the subject, I have prepared a fresh Mystic BBS latest
alpha install on my local server, running Debian 8 64bit. Privileges, permissions and basic configuration is ready, like also ports NAT and start/check scripts. I would like to ask your help, driving me in the rightest way to migrate all my MBBS configuration *lot of* from my RPi1
to this machine, thanks!

Surely,

`cd / && sudo tar czf - mystic | ssh new-server 'cat > mystic.tar.gz'`

will create a backup copy in the file '$HOME/mystic.tar.gz' on your new
server. Then login to your new machine and simply untar:

`cd / && sudo tar xzf $HOME/mystic.tar.gz`

?

--- Mystic BBS v1.12 A31 (Windows)
* Origin: ACiD Telnet HQ / blackflag.acid.org (21:1/112)

`cd / && sudo tar czf - mystic | ssh new-server 'cat > mystic.tar.gz'`

I can't do this easily, because the architecture of the Mystic package is different as different is the architecture of the hardware where it's
currently installed. I've to save the configs and bring them with me from
Rasp ARM 32bit platform to x86_A64 new one.

Regards,


 I N D R I D / C O L D 
First come smiles / Then come lies / Last is gunfire 

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Miskatonic BBS | telnet://rasppi.servebbs.org (21:1/165)

On 03/17/17, Indrid Cold said the following...

`cd / && sudo tar czf - mystic | ssh new-server 'cat > mystic.tar.gz'

I can't do this easily, because the architecture of the Mystic package is different as different is the architecture of the hardware where it's currently installed. I've to save the configs and bring them with me from Rasp ARM 32bit platform to x86_A64 new one.

Ah, when you said "64 bit" you were referring to x86 instead of 64-bit ARM (e.g., aarch64 as on newer Raspberry Pis, etc). If you were running on e.g.
a Raspberry Pi 3 or ODROID-C2, you could just run the 32-bit ARM binaries
on the newer machine (they'd execute in aarch32 mode).

There are a couple of things at work here. First, you can use that command
I sent earlier to copy over your configurations etc and then simply layer
the new binaries over the ARM installation, overwriting the ARM binaries
with x86 binaries. That assumes the *data files* written on a 32-bit ARM
system are compatible with 64-bit x86. There would be two reasons why they *may* not be: byte ordering and type widths. x86 is little endian and ARM
is ambidextrous, but I think most Pi's are run in little endian mode so you should be ok with byte ordering. However, long integers and the like may
be wider on an x86_64 machine than on ARMv6 (e.g., 64-bit long is 8 bytes
vs 32-bit long being 4). I have no idea if Mystic uses explicit type widths
in its data files, however.

If the source code for Mystic (current alphas) was available, one could conceivably write programs to dump the contents of its data files to text
and then restore them from that text representation. But that code isn't available and I've got no idea whether such things exist already or not.
Sorry I can't be more help!

--- Mystic BBS v1.12 A31 (Windows)
* Origin: ACiD Telnet HQ / blackflag.acid.org (21:1/112)

On 03/17/17, Indrid Cold said the following...

I can't do this easily, because the architecture of the Mystic package is different as different is the architecture of the hardware where it's currently installed. I've to save the configs and bring them with me from Rasp ARM 32bit platform to x86_A64 new one.

With Mystic it isn't too bad, I have done it more than once from the Pi to Ubuntu 14.04 & 16.04. The data is fine the structures don't have to change, only the executables change. You do it much like the updates and replace all the executables, recompile the MPLs and things should work. If users end up with the same index "MBBSUTIL -fixindex" will fix that. You might want to run mutil and repack stuff, but it should work without that.

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)