TID: Mystic BBS 1.12 A48
MSGID: 1:134/303 d5b9910f
REPLY: 1:129/215 9a043a1e
TZUTC: -0600
 g0> Unfortunately I do not have a Pi that I can install the latest OS on at
 g0> the moment to test with so it will be a little more difficult to look
 g0> into this.

I just wanted to thank you again for your response on this and also let you
know that you can probably ignore it.

I'm not sure what has caused things to go sideways but I first tried Mystic
with a fresh install of Raspberry Pi OS Bullseye. Python3 worked out of the
box, no need to point it to libpython3.8.so.1.0.

I then installed mystic into a new directory on the same RPi as my existing
board. Again Python 3 worked out of the box. I'm not sure what is broken in my
main board but I think I'll just try migrating my BBS to a fresh install of
Mystic and see if I can sort things out that way.

It's possible that because I had my board on a drive that was using LVM then
linked the directory back to /mystic that something went awry there. I'll play
around with a few different scenarios and see if I can figure out how I broke
things.

Thanks again!

... A .GIF is worth a thousand .TXT.

--- Mystic BBS v1.12 A48 2022/03/26 (Raspberry Pi/32)
 * Origin: CaNerDUH BBS (1:134/303)
SEEN-BY: 1/123 15/0 90/1 105/81 106/201 120/340 123/131 129/305 330
SEEN-BY: 129/331 134/0 100 101 303 153/105 757 7083 7715 154/10 218/700
SEEN-BY: 218/840 221/6 226/30 227/114 229/110 206 307 317 400 424
SEEN-BY: 229/426 428 452 550 664 700 240/5832 266/512 280/464 282/1038
SEEN-BY: 292/854 301/1 317/3 320/219 322/757 342/200 396/45 460/58
SEEN-BY: 633/280 712/848
PATH: 134/303 101 100 153/757 221/6 229/664 426