Subj : Re: Migration Journey repost
To : All
From : DavidG
Date : Tue Jan 14 2025 05:30 pm
On 1/14/2025 7:40, poindexter FORTRAN wrote:
Thanks for taking the time.
> Re: Migration Journey repost
> By: DavidG to All on Tue Jan 14 2025 11:46 am
>
> > step: migrating my Mystic BBS from Windows 10 (32-bit) to a Raspberry Pi 3
> > running Linux. Sounds simple, right? Well, it wasn't quite as smooth as you'
>
>
> Doesn't sound simple at all. I've tried a couple of times and given up.
It seems and feels overwhelming at first, then you get the gist, also
backups are a nice thing to have just in case.
It might not be OK on the first try, just roll back and start over,
that's what I did.
> > After struggling to make Synchronet BBS work (spoiler: it didn't), I had a
> > frustrating realization about Fidonet. It's hard not to notice how some folk
> > prefer to guard their knowledge like buried treasure, watching others
> > flounder instead of lending a hand. It's ironic, really, because hoarding
> > knowledge doesn't help anyone. In Colombia, we say, "No one takes their
> I'd disagree. There's a user-contributed Wiki. Mystic guy has tons of videos on Youtube. Digital Man
> has his own video channel. Sure, there are some people out there who are less than supportive, but as
long as you read the manual/wiki and ask intelligent questions,
there's a lot of support out there.
I love that wiki, do not get me wrong, I've spent 1 or 2 lifetimes
there, struggling and screwing things up, but I've learned and advanced
a whole lo, it's sad to see people that can help just saying RTFM, why?,
you could spend a couple of minutes sending that, why don't you help?, I
don't think it's that hard.... Anywho, I'm far from perfect and my
skill-set need a lot of work but I've learned the hard way, which for
many people is the right way, not for me as an educator you can not take
joy on people failures, but that's me.... ok let me not get started..
> > But back to the story. Installing Mystic on Linux turned out to be
> > surprisingly quick and easy. Using WinSCP, I copied my *.ini and *.dat files
> > as well as the data, echomail, msgs, files, and themes directories, to
> > /home/sbbs/mystic. Then I ran mystic -cfg, adjusted the System Paths, and
> > updated the QWK General Settings to remove references to Windows paths.
>
> > The real challenge came with the message bases. I have around 350 echomail
> > areas, and changing them one by one was simply not an option. While explorin
> > the Message Base Editor, I realized the paths were relative
> > ($mystic\path\msgs\) instead of absolute. That sparked an idea: why not use
> > the Global option to update the path? I tested it with a few FSXNet areas,
> > and it worked!
>
>
> I have a ton of message bases I'd like to preserve, but they're in Synchronet's format. I've been playing with Mystic and could export the message areas from Synchronet and probably import them into Mystic, but I couldn't export the messages.
I'm not sure if there's a direct way, but what I'd do is to set up a
separate node/point running mystic and from there subscribe with Areafix
to alkl of the areas, perform a full rescan of all areas and you'll have
your message base migrated, maybe that's a silly way but I did that and
it seemed to have worked just fine.
If you try please write here, if you need any help, I can share what I
humbly know.
