Hi,

I apologize if this has been discussed before. However, I'd like to know if
it is possible to migrate the Raspberry Pi version of Mystic into x86-64. I'm thinking of running my BBS from a cheap 1and1 virtual cloud server running CentOS 7.

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: A 90's Manila BBS telnet://a90smanilabbs.ddns.net (21:1/192)

On 02/02/17, Balky pondered and said...

I apologize if this has been discussed before. However, I'd like to know if it is possible to migrate the Raspberry Pi version of Mystic into x86-64. I'm thinking of running my BBS from a cheap 1and1 virtual cloud server running CentOS 7.

Yes I think this can be done.

I would install a fresh copy of Mystic on the Windows 64 bit system

Then I would copy your Mystic root directory from the Pi system across to
the newly installed Windows directory but *not* include any .EXE files in
your copying of old system > new system.

Copying the mystic.dat and your .ini files across from the Pi system is important.

I would then copy from the Pi system the following dirs

- data
- text
- echomail
- files
- menus
- msgs
- scripts - do this one only if you have unique scripts you have created since
install.. and only copy the .MPS files you need to over, not the .EXE files

- text

Then I'd follow some of the FAQ steps on the Wiki you would take to migrate from Windows to Linux as I think they are still applicable if you are heading the the opposite direction.

[snip]

Once the files are copied, you must run "mystic" with the -paths option on the new operating system, and change the paths to match your new Mystic location.

Now run "mystic" again with the -cfg option. Each theme has its own text, menu, and scripts directory so go into the Themes editor and change those directories to match your new directories. Each message base also has its
own message base path which needs to be updated. This can be done all at
once by using the Global Message Base Editor.

Note that one pain point is converting over file base directories, meaning
the actual directories where files are stored for each base. These often
have to be manually edited per file base, since those directories are
specific to each base.

[snip]

Now I *think* that will likely do the trick but it's late as I type this and others may well spot some errors or suggest some additional things to
consider :)

Hope that helps.

Best, Paul

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 02/02/17, Avon said the following...

On 02/02/17, Balky pondered and said...

I apologize if this has been discussed before. However, I'd like to k if it is possible to migrate the Raspberry Pi version of Mystic into x86-64. I'm thinking of running my BBS from a cheap 1and1 virtual clo server running CentOS 7.

Yes I think this can be done.

I would install a fresh copy of Mystic on the Windows 64 bit system

Then I would copy your Mystic root directory from the Pi system across to the newly installed Windows directory but *not* include any .EXE files in your copying of old system > new system.

This is all correct except for the install would ahve to be the mystic linux install not windows since CentOS is linux.

+- $s.s$s.s$ ----------------------------------------+
| $ý"$$$"ý$ twinklebbs.homeip.net |
| .$$$. winkle BBS twinklebbs.homeip.net:8080 |
+-- .$$$$$. -----------------------------------------+
$ý"~"ý$ Christopher Malo aka Pequito!

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Twinkle BBS (21:1/126)

On 02/02/2017 10:37 AM, Balky wrote:

Hi,

I apologize if this has been discussed before. However, I'd like to know if it is possible to migrate the Raspberry Pi version of Mystic into x86-64. I'm thinking of running my BBS from a cheap 1and1 virtual cloud server running CentOS 7.

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: A 90's Manila BBS telnet://a90smanilabbs.ddns.net (21:1/192)

From what I've found Avon was correct in the start, but you can do it
the other way around and copy everything over, then pretty much do an
upgrade to Mystic 64 bit on the CentOS server. That's pretty much what I
did on my .2 AlphaTest system which is Ubuntu x86 64 Bit (so much the
same as the CentOS one). The normal upgrade is copy over all the
executable files. I do that by installing a fresh copy to /nmystic and
then coping the executable files over to /mystic. Normally the
executable files in Pi show up as green using color ls which is the
default on the Pi which makes it easier to see.

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

Avon wrote to Balky <=-

Yes I think this can be done.

I'd think it would be easy, especially if the paths were kept the same on both systems, like in my case, I'd put the BBS in /mystic on the new system. If everything is there, then a copy should be straightforward.

I would install a fresh copy of Mystic on the Windows 64 bit system

Then I would copy your Mystic root directory from the Pi system across
to the newly installed Windows directory but *not* include any .EXE
files in your copying of old system > new system.

He's running Linux on the new system, just x84_64, instead of ARM. :)

Copying the mystic.dat and your .ini files across from the Pi system is important.

If everything is under the same path (like on my system, it's all in /mystic), I would copy the entire BBS across, then replace the binaries with the x86 ones. As the paths and everything would be the same, there should be no need to tweak those.

If you have to change the root path, that would need tweaking, same if your filebase paths need tweaking.

I would then copy from the Pi system the following dirs

- data
- text
- echomail
- files
- menus
- msgs
- scripts - do this one only if you have unique scripts you have
created since
install.. and only copy the .MPS files you need to over, not the .EXE files

- text

Why do this last. It's easier to copy the while hierarchy, then replace the bits that need changing, than to do a piecemeal copy like this after changing the binaries.

Then I'd follow some of the FAQ steps on the Wiki you would take to migrate from Windows to Linux as I think they are still applicable if
you are heading the the opposite direction.

He's doing Linux - Linux. Other than replacing the binaries, it should be more straightforward, depending on his exact configuration.

[snip]

Once the files are copied, you must run "mystic" with the -paths option
on the new operating system, and change the paths to match your new
Mystic location.

May or may not be needed (see above).

Now run "mystic" again with the -cfg option. Each theme has its own
text, menu, and scripts directory so go into the Themes editor and
change those directories to match your new directories. Each message
base also has its own message base path which needs to be updated.
This can be done all at once by using the Global Message Base Editor.

Note that one pain point is converting over file base directories,
meaning the actual directories where files are stored for each base.
These often have to be manually edited per file base, since those directories are specific to each base.

[snip]

Now I *think* that will likely do the trick but it's late as I type
this and others may well spot some errors or suggest some additional things to consider :)

Your method would work, but with Linux - Linux, there may be some shortcuts, depending on how the directories are structured on the two systems. Easiest case is where the paths are the same.

One other step, make sure the permissions are correct... I'd create a user for mystic then do:

chown -R mystic.mystic /mystic (assuming the BBS is in /mystic).



... My computer has EMS... Won't you help?
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

bcw142 wrote to All <=-

then coping the executable files over to /mystic. Normally the
executable files in Pi show up as green using color ls which is the default on the Pi which makes it easier to see.

Or use a script like my upgrade script to copy the executables. It would work in this scenario as well. :)


... Man, that lightning sounds closõ¯¨©~®Ô NO CARRIER
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

On 02/03/17, Vk3jed pondered and said...

He's running Linux on the new system, just x84_64, instead of ARM. :)

Ah that's where I should have turned left instead of right :)

Yep it's a lot more simple than I wrote. I thought is was a request to
migrate to a Windows based system.

Copying the mystic.dat and your .ini files across from the Pi system important.

If everything is under the same path (like on my system, it's all in /mystic), I would copy the entire BBS across, then replace the binaries with the x86 ones. As the paths and everything would be the same, there should be no need to tweak those.

Yep agreed.

If you have to change the root path, that would need tweaking, same if your filebase paths need tweaking.

Agreed also.

files
- text

Why do this last. It's easier to copy the while hierarchy, then replace the bits that need changing, than to do a piecemeal copy like this after changing the binaries.

It's hardly last... but that aside, I just prefer to copy only the folders I think I need to come across to a new install vs. copying them all. Remember this was set in context of updating files after a fresh install not moving an old install over in it's entirety and then cherry picking the files you
needed to revise. Linux <> Linus does make the whole thing a lot easier :)

He's doing Linux - Linux. Other than replacing the binaries, it should
be more straightforward, depending on his exact configuration.

Yep just agreed with that :)

Your method would work, but with Linux - Linux, there may be some shortcuts, depending on how the directories are structured on the two systems. Easiest case is where the paths are the same.

One other step, make sure the permissions are correct... I'd create a user for mystic then do:

Yes, good point permissions would need to be checked.

Best, Paul

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Avon wrote to Vk3jed <=-nstead of right :)

Yep it's a lot more simple than I wrote. I thought is was a request to migrate to a Windows based system.

Yeah, when I saw your reply, I had to double check what I had previously read. :)

Yep agreed.

If you have to change the root path, that would need tweaking, same if your filebase paths need tweaking.

Agreed also.

Seems we're in violent agreement. ;)

files
- text

Why do this last. It's easier to copy the while hierarchy, then replace the bits that need changing, than to do a piecemeal copy like this after changing the binaries.

It's hardly last... but that aside, I just prefer to copy only the
folders I think I need to come across to a new install vs. copying them all. Remember this was set in context of updating files after a fresh install not moving an old install over in it's entirety and then cherry picking the files you needed to revise. Linux <> Linus does make the
whole thing a lot easier :)

I tend to avoid fiddly jobs, doesn't play nicely with the ADHD like side of me. :)

Yes, good point permissions would need to be checked.

They can trip you up. ;)


... Can I blame my spelling on Line Noise?
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)