Hi All,

I'm running A43 on Debian Stretch 9.11 x64. For some reason, I've been unable to get any .mpy scripts to run at all. The inter BBS oneliner script just disconnects my terminal when I run it, and the build in pythondemo script
just seems to return me to the demos menu.

I checked to ensure python 2.7 is installed. It's currently /usr/bin/python.
I also confirmed that libpython2.7.so.1.0 exists via ldconfig -p. I know it's working because the MRC python script is working fine.

I tried to compile 2.7 from scratch, which worked. It was a slightly newer version (2.7.15 instead of 2.7.13 that comes with debian). When I did that using instructions from the mystic wiki, it put it in /usr/local/bin for some reason. Either way, it behaved the same way.

Any tips or tricks anyone can share? Would love to get this working.

Thanks,
Mike

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

On 08 Oct 2019, lemonlime said the following...

I checked to ensure python 2.7 is installed. It's currently /usr/bin/python. I also confirmed that libpython2.7.so.1.0 exists via ldconfig -p. I know it's working because the MRC python script is
working fine.

you using the 2.7.15 version?

|08 .|05ú|13ù|15Dr|07e|08am Ma|07st|15er|13ù|05ú|08.
|08 øù|05ú|13ùø |13øù|05ú|08ùø
|11 DoRE|03!|11ACiDiC|03!|11Demonic
|08[|15bbs|09.|15dreamlandbbs|09.|15org|08]

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)

you using the 2.7.15 version?

I tried 2.7.13 that comes with Debian, and compiled both 2.7.15 and 2.7.16 - always getting the same behaviour.

Interestingly, I see that the interbbs oneliner mpy script seems to be
crashing out and isn't related to python problems. From the node logs I see a "corrupted memory" error, followed by "shutdown".

But I still can't get the python demo script to work either that ships with mystic. It just returns me to the demo menu with no output that I can see.

Thanks,
Mike

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

On 08 Oct 2019 at 10:03a, lemonlime pondered and said...

Hi All,

I'm running A43 on Debian Stretch 9.11 x64. For some reason, I've been unable to get any .mpy scripts to run at all. The inter BBS oneliner

I;m on windows at the moment but moving to Debian (slowly) so when I am up
and running I'll be able to test to see if this is an issue for me also.
Under windows I think things are fine.

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

you using the 2.7.15 version?

I tried 2.7.13 that comes with Debian, and compiled both 2.7.15 and
2.7.16 - always getting the same behaviour.

I think you broke debian. In fact, I'm sure of it. If you install a package, you shouldn't also go compile and manually install a newer version of it. Debian is one of those distros where you should stick to what's in the apt repos 99.999% of the time, with rare exceptions.

Any chance you can blow away your OS and start from scratch? Back up the BBS and rebuild your OS?

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: monterey bbs (21:1/168)

I tried 2.7.13 that comes with Debian, and compiled both 2.7.15
and 2.7.16 - always getting the same behaviour.

I think you broke debian. In fact, I'm sure of it.

Why?

If you install a
package, you shouldn't also go compile and manually install a newer version of it.

A compiled Python installs to /usr/local by default. You always can remove those files. Nothing should be broke and no reason to resintall Debian.


* Origin: 🌈 (21:1/151)

On 08 Oct 2019, lemonlime said the following...

you using the 2.7.15 version?

I tried 2.7.13 that comes with Debian, and compiled both 2.7.15 and
2.7.16 - always getting the same behaviour.

oh i did not know there was a .16. thought they were stopping there. gonna have to upgrade.

But I still can't get the python demo script to work either that ships with mystic. It just returns me to the demo menu with no output that I
can see.

have you checked the mystic wiki?

|08 .|05ú|13ù|15Dr|07e|08am Ma|07st|15er|13ù|05ú|08.
|08 øù|05ú|13ùø |13øù|05ú|08ùø
|11 DoRE|03!|11ACiDiC|03!|11Demonic
|08[|15bbs|09.|15dreamlandbbs|09.|15org|08]

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)

On 09 Oct 2019, Oli said the following...

I tried 2.7.13 that comes with Debian, and compiled both 2.7.15
and 2.7.16 - always getting the same behaviour.

I think you broke debian. In fact, I'm sure of it.

Why?

heh...lemonlime broke the Google :)

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Vger.Cloud - NOMAD Internetwork (21:2/104)

I;m on windows at the moment but moving to Debian (slowly) so when I am
up and running I'll be able to test to see if this is an issue for me also. Under windows I think things are fine.

Thanks Avon! I'll be very curious to see if you have the same problems in
your new deployment. Are you using Debian Buster (10.x)?

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

I think you broke debian. In fact, I'm sure of it. If you install a package, you shouldn't also go compile and manually install a newer version of it. Debian is one of those distros where you should stick to what's in the apt repos 99.999% of the time, with rare exceptions.

Any chance you can blow away your OS and start from scratch? Back up the BBS and rebuild your OS?

Because I was worried about this as well, I did this in a test Debian VM with snapshots so that I could revert after each failed attempt. After messing up
my Debian install a few weeks back, I stopped testing things "in production" :)

I also removed the python2.7 install using apt-get each time I compiled one
of the other versions to test.

Cheers,
Mike

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

A compiled Python installs to /usr/local by default. You always can
remove those files. Nothing should be broke and no reason to resintall Debian.

I was wondering about this as well as python 2.7 doesn't provision a 'make uninstall' option. Is it enough to just remove the python files from /usr/local?

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

oh i did not know there was a .16. thought they were stopping there. gonna have to upgrade.

Yeah, I was surprised too. I know all development and support of 2.7 was supposed to stop in 2020.

have you checked the mystic wiki?

Yeah, the steps I tried when compiling python from scratch were from the
wiki in the troubleshooting section. I verified the other checks in the wiki
as well. The only thing I didn't try yet was to set the environment variables they talk about - I wasn't clear on how to properly do that. Going to look
more into that next.

Cheers,
Mike

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

heh...lemonlime broke the Google :)

Haha that's what it feels like when I start troubleshooting. A total path of destruction left in my wake :)

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

A compiled Python installs to /usr/local by default. You always
can remove those files. Nothing should be broke and no reason to
resintall Debian.

I was wondering about this as well as python 2.7 doesn't provision a
'make uninstall' option. Is it enough to just remove the python files
from /usr/local?

It's unfortunate that there is no uninstall script. I'm not an expert on this, but I think everything is in /usr/local. What I hate about /usr/local is that the files are all over the place (bin/, etc/, include/, man/, share/, ...).

Debian's python creates some folders in /usr/local too. So maybe keep this (or (re)install Python after the removal)

$ ls /usr/local/lib/python2.7
dist-packages site-packages

I found this today: https://help.ubuntu.com/community/CheckInstall "CheckInstall keeps track of all files installed by a 'make install' or equivalent, creates a Slackware, RPM, or Debian package with those files, and adds it to the installed packages database, allowing for easy package removal or distribution."


* Origin: 🌈 (21:1/151)

A compiled Python installs to /usr/local by default. You always can
remove those files. Nothing should be broke and no reason to resintall Debian.

it also compiles a bunch of libraries that overwrite the apt package managed ones, not just the executable

|15frank |08// |15netsurge
|07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://scinet-ftn.org

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)

I found this today: https://help.ubuntu.com/community/CheckInstall "CheckInstall keeps track of all files installed by a 'make install' or equivalent, creates a Slackware, RPM, or Debian package with those
files, and adds it to the installed packages database, allowing for easy package removal or distribution."

Yeah, I found that as well - interesting concept. I gave it a try but it
would hang trying to create the .deb file for some reason. Seems like a good workaround if I could get it to work. For now, been using snapshots to revert if my compiled versions of python don't work.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

On 09 Oct 2019, Oli said the following...

A compiled Python installs to /usr/local by default. You always
can remove those files. Nothing should be broke and no reason to
resintall Debian.

Debian's python creates some folders in /usr/local too. So maybe keep
this (or (re)install Python after the removal)

Another thing he should consider is that many things install symlinks too, so an ls -la before whacking anything to identify those and if one isn't comfortable using rm then they can safely remove those symlinks with
'unlink'.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Vger.Cloud - NOMAD Internetwork (21:2/104)

Still no luck, unfortunately. I ruined several test VMs compining and
tinkering with python. Is there anyone out there running .mpy python scripts
on an x64 Linux or raspberry pi platform? Just curious if anyone has got this to work on any modern distro?

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

Still no luck, unfortunately. I ruined several test VMs compining and tinkering with python. Is there anyone out there running .mpy python scripts on an x64 Linux or raspberry pi platform? Just curious if anyone has got this to work on any modern distro?

yeah...I'm using ubuntu 18.04 and having no issues. Also tested in arch about
a month ago.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: monterey bbs (21:1/168)

yeah...I'm using ubuntu 18.04 and having no issues. Also tested in arch about a month ago.

Thanks Ryan - Did you have to do anything special to get it going or did
the built-in python 2.7 work fine?

Thanks,
Mike

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

Thanks Ryan - Did you have to do anything special to get it going or did the built-in python 2.7 work fine?

Built-in python works fine. Are any error messages being spit out? What is
your OS bitrate (32/64 bit), mystic bitrate, and python bitrate?

Any errors at all? It should work OOTB.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: monterey bbs (21:1/168)

Built-in python works fine. Are any error messages being spit out? What
is your OS bitrate (32/64 bit), mystic bitrate, and python bitrate?

Any errors at all? It should work OOTB.

Everything is 64-bit. I don't see any errors at all in mis.log, node#.log, syslog etc, which is making this very hard to troubleshoot :(

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

Looks like I made some progress in troubleshooting. Turns out some scripts to run correctly. I had been under the assumption that testpython.mpy was a good test that should definitely work, but I can't get it to run. I ran the 'testparams.mpy' script that also comes with Mystic, and that works just
fine! So clearly MPY scripts are functional to some degree.

I tried two other scripts, one for 'inter-bbs oneliners' and another for 'inter-bbs last callers' and both seem to crash out and I get disconnected.
If I look in node1.log, I see instances of the following:

2019.11.10 14:32:28 MYSTIC 001 An error has occured: Corrupted memory (216) 2019.11.10 14:54:02 MYSTIC 001 An error has occured: Corrupted memory (216)

No idea how to troubleshoot this. Any suggestions?

Thanks,
Mike

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

2019.11.10 14:32:28 MYSTIC 001 An error has occured: Corrupted memory (216) 2019.11.10 14:54:02 MYSTIC 001 An error has occured: Corrupted memory (216)

I think we need g00r00 on this one :/

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: monterey bbs (21:1/168)

2019.11.10 14:32:28 MYSTIC 001 An error has occured: Corrupted memory (216) 2019.11.10 14:54:02 MYSTIC 001 An error has occured: Corrupted memory (216)

No idea how to troubleshoot this. Any suggestions?

Go to: http://wiki.mysticbbs.com/doku.php?id=python_install

And look in the Troubleshooting section.

You will most likely need to recompile Python yourself using the instructions from the Wiki. Many Linux distributions ship with a version of Python that is compiled with the shared option disabled. This means that any application
that tries to emebedd Python will fail, so it has to be recompiled.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

On 15 Oct 2019 at 12:49p, g00r00 pondered and said...

Go to: http://wiki.mysticbbs.com/doku.php?id=python_install

And look in the Troubleshooting section.

Nice to see you active again. Welcome back, trust things are going well for you.

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

You will most likely need to recompile Python yourself using the instructions from the Wiki. Many Linux distributions ship with a
version of Python that is compiled with the shared option disabled.
This means that any application that tries to emebedd Python will fail,
so it has to be recompiled.

Thanks g00r00! The corrupted memory errors were with the out of the box
version of python 2.7.13 with Debian 9. I followed those instructions in
the wiki to compile 2.7.16 earlier but couldn't get certain scripts to run either. I'm going to try again to see if it is still the corrupted memory errors or something different with the compiled version.

Thanks again!

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

You will most likely need to recompile Python yourself using the instructions from the Wiki. Many Linux distributions ship with a
version of Python that is compiled with the shared option disabled.
This means that any application that tries to emebedd Python will fail,
so it has to be recompiled.

Looks like I made some progress today. Debian 9 comes pre-loaded with Python 2.7.13, but even after purging everything python 2.7 related and compiling 2.7.16 correctly, I still see the same problem. There must be some remnants
of the boxed version in the system somewhere.

I tried out Ubuntu Server 18.04 instead, which has Python 3.x out of the box, but not 2.7. I compiled 2.7.16 per the wiki instruxtions and ran ldconfig. Lo and behold, it worked perfectly! I was able to run the interbbs oneliner
script without issue.

I may do some more testing with Debian, and will report back if I have any luck.

Thanks again for the help.
Mike

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

Well, I had no luck with Debian so wound up migrating my BBS over to Ubuntu Server 18.04 LTS. It didn't have Python 2.7 installed by default, so I was
able to compile Python 2.7.16 from scratch as described in the wiki. Python scripts have been working great.

One thing that caught me was the new /usr/local/bin installation location instead of /usr/bin. Some .py scripts (like MRC for example) reference #!/usr/bin/python at the top. Simple to correct. I may try to create a sym
link in /usr/bin but was simple to just modify the script.

I've been using Debian for years and didn't want to move to Ubutnu, but since
I don't use a GUI and am CLI only they are very similar. Pleased so far!

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

On 17 Oct 2019 at 10:33p, lemonlime pondered and said...

I've been using Debian for years and didn't want to move to Ubutnu, but since I don't use a GUI and am CLI only they are very similar. Pleased
so far!

Hmm this fills me with a bit of fear and dread given I am down the track of trying to migrate to a Debian box. Thanks for the info..

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Hmm this fills me with a bit of fear and dread given I am down the track of trying to migrate to a Debian box. Thanks for the info..

It doesn't sound very user friendly does it?

I don't know anything about python but I wonder if the scripts can be
changed to work with the current version of python being deployed?

Ttyl :-)
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Hmm this fills me with a bit of fear and dread given I am down the
of trying to migrate to a Debian box. Thanks for the info..

It doesn't sound very user friendly does it?

I don't know anything about python but I wonder if the scripts can be changed to work with the current version of python being deployed?

I don't think it's the scripts, but rather that gOOrOO has to pick a
version of python to compile mystic against, and given the nature of
Linux distributions that does not necessarily match the one packaged for
your system.

Andrew

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: HappyLand (21:1/126)

On 17 Oct 2019, lemonlime said the following...

I've been using Debian for years and didn't want to move to Ubutnu, but since I don't use a GUI and am CLI only they are very similar. Pleased
so far!

I like both, but I've only ever used Rasbian and Linux Mint.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: throwbackbbs.com -\- meriden, ct -\- (21:1/114)

I don't know anything about python but I wonder if the scripts can
be changed to work with the current version of python being
deployed?

I don't think it's the scripts, but rather that gOOrOO has to pick a version of python to compile mystic against, and given the nature of
Linux distributions that does not necessarily match the one packaged
for your system.

That's one reason why you shouldn't use closed source software with Linux ;)

Seriously, I thought the version you compile against is libpython 2.7 and it should make no difference if you have libpython 2.7.13 or 2.7.16 installed.

If you install libpython2.7 it should work on any Linux.

* Origin: 🌈 (21:1/151)

Hmm this fills me with a bit of fear and dread given I am down the
track of trying to migrate to a Debian box. Thanks for the info..

It doesn't sound very user friendly does it?

I don't know anything about python but I wonder if the scripts can be changed to work with the current version of python being deployed?

Python 2.7 is included in _every_ Linux distribution and will be for a long time.


* Origin: 🌈 (21:1/151)

Well, I had no luck with Debian so wound up migrating my BBS over to Ubuntu Server 18.04 LTS. It didn't have Python 2.7 installed by
default, so I was able to compile Python 2.7.16 from scratch as
described in the wiki. Python scripts have been working great.

Have you tried to install libpython2.7 in Ubuntu, just in case it works out of the box ...?

One thing that caught me was the new /usr/local/bin installation
location instead of /usr/bin.

/usr/bin is reserved for packages from the distribution. Most software you compile from source uses /usr/local as the default path for installation.

Some .py scripts (like MRC for example)
reference #!/usr/bin/python at the top. Simple to correct. I may try
to create a sym link in /usr/bin but was simple to just modify the
script.

You can also use:
#!/usr/bin/env python2.7

* Origin: 🌈 (21:1/151)

Seriously, I thought the version you compile against is libpython 2.7
and it should make no difference if you have libpython 2.7.13 or
2.7.16 installed.

You would think so, but apparently it doesn't.

Andrew

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: HappyLand (21:1/126)

Seriously, I thought the version you compile against is libpython
2.7 and it should make no difference if you have libpython 2.7.13
or 2.7.16 installed.

You would think so, but apparently it doesn't.

I just downloaded mystic 64bit linux and tried it on Debian 9 (Stretch) and 10 (Buster). The Python demo worked on both. I only had to install libpython2.7

Debian 9: libpython 2.7.13
Debian 10: libpython 2.7.16

The idea that you need to compile Python, because the version in the distribution does not support X or is the wrong version is nothing more than a urban myth (IMHO).

* Origin: 🌈 (21:1/151)

I just downloaded mystic 64bit linux and tried it on Debian 9 (Stretch) and 10 (Buster). The Python demo worked on both. I only had to install libpython2.7

Debian 9: libpython 2.7.13
Debian 10: libpython 2.7.16

The idea that you need to compile Python, because the version in the distribution does not support X or is the wrong version is nothing more than a urban myth (IMHO).

Thanks for the testing Oli - I'm going to look more into this. I actually
just deployed a Debian 10 VM and will try what you suggested. The part that g00r00 was mentioning could be a problem is that some distro versions aren't configured as "enable-shared". In 2.7.16 that comes with Buster, it looks like it is..

root:~# python
Python 2.7.16 (default, Apr 6 2019, 01:42:57)
[GCC 8.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.

import sysconfig
sysconfig.get_config_vars('Py_ENABLE_SHARED')

[1]

So this is promising! I'll report back with my findings.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

Have you tried to install libpython2.7 in Ubuntu, just in case it works out of the box ...?

Well, I don't know what I was doing wrong in Debian 9, but I just installed libpython2.7 in Buster and it's working perfectly out of the box! I have a feeling all my tinkering messed up my old system. No compiling was required.

I was meaning to use Debian 10 eventually anyhow, so this will just
accelerate my plans. Thanks again, Oli! I was over-thinking this way too much :)

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

Well, I don't know what I was doing wrong in Debian 9, but I just installed libpython2.7 in Buster and it's working perfectly out of the box! I have a feeling all my tinkering messed up my old system. No compiling was required.

I was meaning to use Debian 10 eventually anyhow, so this will just accelerate my plans. Thanks again, Oli! I was over-thinking this way too much :)

Well, looks like I responded too quickly. Yes, the built-in testpython script works great, but I'm getting the 216 corrupted memory errors again any time I try to run the inter-bbs oneliner script as well as the inter-bbs last caller script. I'm not sure what about these scripts mystic's embedded python doesn't like.

Of course I only realized this once I migrated the BBS over to the Debian 10 VM! Oh well. This didn't happen with the Ubuntu 18.04 machine with compiled 2.7.16. I'm going to spin up another test buster VM and tinker with it.

Cheers,
Mike

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

Well, looks like I responded too quickly. Yes, the built-in testpython script works great, but I'm getting the 216 corrupted memory errors
again any time I try to run the inter-bbs oneliner script as well as
the inter-bbs last caller script. I'm not sure what about these
scripts mystic's embedded python doesn't like.

Where do I find these inter-bbs scripts?

Of course I only realized this once I migrated the BBS over to the
Debian 10 VM! Oh well. This didn't happen with the Ubuntu 18.04
machine with compiled 2.7.16. I'm going to spin up another test buster
VM and tinker with it.

I'm sorry :(

* Origin: 🌈 (21:1/151)

Well, looks like I responded too quickly. Yes, the built-in
testpython script works great, but I'm getting the 216 corrupted
memory errors again any time I try to run the inter-bbs oneliner
script as well as the inter-bbs last caller script. I'm not sure
what about these scripts mystic's embedded python doesn't like.

Where do I find these inter-bbs scripts?

I can reproduce this with Debian 10 and the msgread.mpy script, which works in Ubuntu 18.04 with libpython2.7 from the repository.


* Origin: 🌈 (21:1/151)

I can reproduce this with Debian 10 and the msgread.mpy script, which works in Ubuntu 18.04 with libpython2.7 from the repository.

Good to know! thanks for trying it out. I may try to do some more thorough testing with both Ubuntu 18.04 and Debian 10 later today.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

I can reproduce this with Debian 10 and the msgread.mpy script,
which works in Ubuntu 18.04 with libpython2.7 from the
repository.

Good to know! thanks for trying it out. I may try to do some more
thorough testing with both Ubuntu 18.04 and Debian 10 later today.

Okay, I did some tests with different Debian, Ubuntu and Python versions (from the distribution and sources). It seems it only works with the exact Python version 2.7.15. This is the version that is shipped with Ubuntu 18.04. Debian 10 has Python 2.7.16, which didn't work, but 2.7.15 from the sources does.

The dependency on a specific patch-level version is unusual.


* Origin: 🌈 (21:1/151)

Well, looks like I responded too quickly. Yes, the built-in testpython script works great, but I'm getting the 216
corrupted memory errors again any time I try to run the
inter-bbs oneliner script as well as the inter-bbs last caller
script. I'm not sure what about these scripts mystic's embedded
python doesn't like.

Where do I find these inter-bbs scripts?

The one for Mystic was written by xqtr from Another Droid BBS. You could
grab those from his BBS, it's an interbbs one liner.

I was going to point you to a copy I have here but my stuff is a bit of a
mess currently and I can't find it. ;)

Ttyl :-)
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Python 2.7 is included in _every_ Linux distribution and will be for a long time.

Yep, my first use for python was a game called pysol late in the 90's.

I don't use python myself much but there are a number of nice FTN python scripts around. I used one to convert the nodelist to a format binkd
could use.

It's pretty amazing what can be done with python.

Ttyl :-)
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

The one for Mystic was written by xqtr from Another Droid BBS. You could grab those from his BBS, it's an interbbs one liner.

I was going to point you to a copy I have here but my stuff is a bit of a mess currently and I can't find it. ;)

Wait a minute.. ;)

The InterBBS oneliners was written by Gryphon. You can grab it from his
BBS, Cyberia or I have a copy here..

ftp://trmb.ca/bbs/mystic/mpl/gy-ibol04.zip

That is a BBBS ftp server and IPv6 is broken. It'll happily log you in
but it won't do anything for you after that so use IPv4 if you have IPv6
there.

Ttyl :-)
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Well, I don't know what I was doing wrong in Debian 9, but I just installed libpython2.7 in Buster and it's working perfectly out of the box! I have a feeling all my tinkering messed up my old system. No compiling was required.

I knew it! You broke debian! Haha. I've done it a million times. Fortunately linux makes things easy to back up and restore.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: monterey bbs (21:1/168)

Okay, I did some tests with different Debian, Ubuntu and Python versions (from the distribution and sources). It seems it only works with the
exact Python version 2.7.15. This is the version that is shipped with Ubuntu 18.04. Debian 10 has Python 2.7.16, which didn't work, but 2.7.15 from the sources does.

The dependency on a specific patch-level version is unusual.

Very strange indeed. I actually got 2.7.16 to work at one point on Ubuntu
18.04 when compiled from source per g00r00's wiki instructions. That Ubuntu Server 18.04 install did not include 2.7.x out of the box, only python3.x.

Did you remove python 2.7.16 before compiling 2.7.15 from source on the
Debian 10 test that you did? If so, how did you strip it out?

Thanks again for all your help with this! Really appreciate the time you put
in testing!

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

I knew it! You broke debian! Haha. I've done it a million times. Fortunately linux makes things easy to back up and restore.

LOL - yeah, it was inevitable I think :)

Thankfully Mystic is super easy to backup and restore.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

Okay, I did some tests with different Debian, Ubuntu and Python
versions (from the distribution and sources). It seems it only
works with the exact Python version 2.7.15. This is the version
that is shipped with Ubuntu 18.04. Debian 10 has Python 2.7.16,
which didn't work, but 2.7.15 from the sources does.

The dependency on a specific patch-level version is unusual.

Very strange indeed. I actually got 2.7.16 to work at one point on
Ubuntu 18.04 when compiled from source per g00r00's wiki instructions. That Ubuntu Server 18.04 install did not include 2.7.x out of the box, only python3.x.

I haven't tested all possible combinations yesterday. Today I tried Python 2.7.16 compiled from source on Ubuntu 18.04 and indeed it works fine.
But it gets even funnier: on Ubuntu 19.04 I had no success at all with any version. Something else is going on. Maybe it is related to the gcc version or to some library that is used by Python. I have no idea.

(... more testing ...)

Fascinating! Success with Python 2.7.14 on Ubuntu 18.04 too.

I would say Mystic's Python support is broken for any distribution that is not Ubuntu 18.04

Did you remove python 2.7.16 before compiling 2.7.15 from source on
the Debian 10 test that you did? If so, how did you strip it out?

I didn't. I'm using lxc containers and the Debian 10 image from lxc/lxd has only Python 3 pre-installed.

Thanks again for all your help with this! Really appreciate the time
you put in testing!

No problem. Fortunately it takes only one command and a couple of seconds to start any Debian and Ubuntu version in a container.

* Origin: 🌈 (21:1/151)

Dear g00r00,

I'm glad to see You again. May I kindly ask You what would You suggest
when it's impossible by default to connect via ssh client to Mysic BBS
ssh? I heard from friend of mine (I don't have a Mac) he couldn't connect
that way. Any hint on what to try?

Thank You & best regards

|08Shinobi <.Phenom.>

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Infoline BBS (21:1/153)

I knew it! You broke debian! Haha. I've done it a million times. Fortunately linux makes things easy to back up and restore.

LOL - yeah, it was inevitable I think :)

Thankfully Mystic is super easy to backup and restore.

FWIW, "Don't break debian" isn't intended to be pejorative. We've all been there. In a lot of debian specific forums (and forums dedicated to debian derivative distros), "don't break debian" is a sort of mantra preached to
teach people how to best use the distro and provide the most sustainability
and security. IMO, it works pretty well OOTB without doing much
customization, and once I really understood the intent and how to leverage that, instead of breaking it, I had overwhelmingly positive experiences.

Not to derail, but I've since switched to Ubuntu for my servers. A lot of people may head-scratch at this...but it turns out the debian "release when ready" methodology means things can become pretty stale on the current stable branch, which also makes version-to-version upgrades scary since so many
things will make so many large horizontal jumps. Ubuntu LTS-to-LTS migrations are a bit less scary and all I incur in the mean time is more potential daily update maintenance. To me, this is an easier pill to swallow :)

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: monterey bbs (21:1/168)

I'm glad to see You again. May I kindly ask You what would You suggest when it's impossible by default to connect via ssh client to Mysic BBS ssh? I heard from friend of mine (I don't have a Mac) he couldn't connect that way. Any hint on what to try?

From macos, syncterm.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: monterey bbs (21:1/168)

I'm glad to see You again. May I kindly ask You what would You suggest when it's impossible by default to connect via ssh client to Mysic BBS ssh? I heard from friend of mine (I don't have a Mac) he couldn't connect that way. Any hint on what to try?

I'm not a Mac user and likely never will be, but I'm pretty sure there's a SyncTerm for MacOS.

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Northern Borderlands: northernborderlands.ddns.net (21:2/107)

Not to derail, but I've since switched to Ubuntu for my servers. A lot of people may head-scratch at this...but it turns out the debian "release when ready" methodology means things can become pretty stale on the current stable branch, which also makes version-to-version upgrades
scary since so many things will make so many large horizontal jumps. Ubuntu LTS-to-LTS migrations are a bit less scary and all I incur in the mean time is more potential daily update maintenance. To me, this is an easier pill to swallow :)

Very good points! Thanks for sharing.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

On 18 Oct 2019, lemonlime said the following...

Well, looks like I responded too quickly. Yes, the built-in testpython script works great, but I'm getting the 216 corrupted memory errors
again any time I try to run the inter-bbs oneliner script as well as the inter-bbs last caller script. I'm not sure what about these scripts mystic's embedded python doesn't like.

This is the error I always got with the same scripts. It crashes on the msg_seek call here, but something seems to happen during the msg_open call immediately preceding that to trigger the issue because if I try to exit the script after the open but before the seek it will still result in a 216. I'm running on an unusual setup that's a bit of a test bed for aggressive security measures so I'd just attributed it to that and I'm surprised to see people on regular distributions running into what looks like the same thing.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Subcarrier BBS (21:2/140)

This is the error I always got with the same scripts. It crashes on the msg_seek call here, but something seems to happen during the msg_open
call immediately preceding that to trigger the issue because if I try to exit the script after the open but before the seek it will still result
in a 216. I'm running on an unusual setup that's a bit of a test bed for aggressive security measures so I'd just attributed it to that and I'm surprised to see people on regular distributions running into what looks like the same thing.

I recall upgrading ibol03 to 04 shortly after it was released and running
into a problem, probably this same issue.

IIRC and it was a while ago I went back to ibol03 and that worked.

So, for those running into this wall it might be worth trying ibol03 and
see if that works OK.

Ttyl :-)
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 21 Oct 2019, Al said the following...

I recall upgrading ibol03 to 04 shortly after it was released and running into a problem, probably this same issue.

IIRC and it was a while ago I went back to ibol03 and that worked.

I've tried older versions of ibol but they do the same thing at the same function call. It even affects the msgread python test script that's bundled with Mystic.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Subcarrier BBS (21:2/140)

I recall upgrading ibol03 to 04 shortly after it was released and
running into a problem, probably this same issue.

IIRC and it was a while ago I went back to ibol03 and that
worked.

I've tried older versions of ibol but they do the same thing at the
same function call. It even affects the msgread python test script
that's bundled with Mystic.

\__/ \__/ \__/ \__/ \__/
(oo) (o-) (@@) (xx) (--)
//||\\ //||\\ //||\\ //||\\ //||\\
bug bug bug/w dead bug
winking hangover bug sleeping

--- GoldED+/LNX 1.1.5-b20180707
* Origin: (21:1/151)

Oli wrote to Static <=-

\__/ \__/ \__/ \__/ \__/
(oo) (o-) (@@) (xx) (--)
//||\\ //||\\ //||\\ //||\\ //||\\
bug bug bug/w dead bug
winking hangover bug sleeping

And this is bugz, replying to a message about bugs. ;)

Take care,
bugz

... All taglines are busy..One will be with you shortly.

___ MultiMail/Linux v0.49

--- Mystic BBS/QWK v1.12 A43 2019/03/02 (Linux/64)
* Origin: BZ&BZ BBS (21:4/110)

This is the error I always got with the same scripts. It crashes on the msg_seek call here, but something seems to happen during the msg_open
call immediately preceding that to trigger the issue because if I try to exit the script after the open but before the seek it will still result
in a 216. I'm running on an unusual setup that's a bit of a test bed for aggressive security measures so I'd just attributed it to that and I'm surprised to see people on regular distributions running into what looks like the same thing.

Thanks for the additional info - good to know at what point it's crashing out. It has now been solid for me on Ubuntu Server 18.04 with the packaged version of python 2.7.15. I wonder if there is the potential for g00r00 to implement
a fix for this to make is less dependent on specific python builds etc. It doesn't appear to be due to the "enable shared" compiling option as was originally suspected.

Cheers,
Mike

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

On 21 Oct 2019, lemonlime said the following...

dependent on specific python builds etc. It doesn't appear to be due to the "enable shared" compiling option as was originally suspected.

Not having that enabled is probably a common source of problems, but in this case it's something different. Running 2.7.16 here with enable-shared right now. It had the same behavior on 2.7.13 prior to this as well.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Subcarrier BBS (21:2/140)

Not having that enabled is probably a common source of problems, but in this case it's something different. Running 2.7.16 here with
enable-shared right now. It had the same behavior on 2.7.13 prior to
this as well.

Yep, agreed. Seems Debian and Ubuntu 18.04 have enable-shared on by default
in their packaged based python implementations anyhow.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Stellar Darkness BBS (21:4/162)

I've tried older versions of ibol but they do the same thing at the same function call. It even affects the msgread python test script that's bundled with Mystic.

Yep, that's a bummer.

Does this issue also affect windows or is it a problem on linux only?

Ttyl :-)
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 21 Oct 2019, Al said the following...

Does this issue also affect windows or is it a problem on linux only?

I didn't even realize anyone else was affected in this particular manner. No idea about the impact on Windows but I'd guess not since most users are going to be using the exact same set of binaries and consequently those would be
the most tested.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Subcarrier BBS (21:2/140)

I didn't even realize anyone else was affected in this particular manner. No idea about the impact on Windows but I'd guess not since most users
are going to be using the exact same set of binaries and consequently those would be the most tested.

I just took a walk backwards in the fsx_dat area and see quite a few
mystic BBSs posting onliners, windows and linux versions, so not everyone
is affected. A tough situation for those that are though.

Ttyl :-)
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Nice to see you active again. Welcome back, trust things are going well for you.

Things have been pretty hectic for me lately but I am still very slowly
working on things. I've been meaning to dial out for a while now I just
never seem to get around to having a big enough window of time that I feel should be spent trying to catch up on 6 months of messages :)

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

I tried out Ubuntu Server 18.04 instead, which has Python 3.x out of the box, but not 2.7. I compiled 2.7.16 per the wiki instruxtions and ran ldconfig. Lo and behold, it worked perfectly! I was able to run the interbbs oneliner script without issue.

I may do some more testing with Debian, and will report back if I have
any luck.

Thanks please let me know if you find anything. To be perfectly honest I
don't have a lot of time to install that OS and version and do testing at the moment.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

I don't know anything about python but I wonder if the scripts can be changed to work with the current version of python being deployed?

Python 3 is an entirely different language than Python 2, its not compatible.

The reason I selected Python 2 was because Python 3 at the time was very new, and the functions and syntax were actually changing, including the
programming API. On the flipside, Python 2 is locked in and should not be changing, which would offer us the best long term compatibility.

At the time, Python 2.7 was still the default for most Linux systems as well
as MacOS. Its relatively effortless to install Python 2.7 on most systems
that may have switched to Python 3, and many already come with it available to install automatically (although the issue with the shared option sort of
ruins that).

For me to switch to Python 3, I would probably end up having to support both Python 2 and 3. I may end up doing it though, I myself have to study up on Python 3 before I can though.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

Seriously, I thought the version you compile against is libpython 2.7
and it should make no difference if you have libpython 2.7.13 or 2.7.16 installed.

This is true. Any 2.7 version released in the last X (X being a long time
that I am unsure of exactly without researching) should work fine.

The issue only is that the operating systems that come with 2.7 by default seem to often compile it with the ability to embed it disabled. This makes it not worth no only with Mythic, but lots of other applications that use a Python subsystem. I don't know why the operating systems do this, I've seen plenty
of people complaining about it over the years.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

I don't know anything about python but I wonder if the scripts can be changed to work with the current version of python being deployed?

Python 3 is an entirely different language than Python 2, its not compatible.

Yep, when I say current version being deployed I mean 2.7.

I wish distro's would enable sharing.


Just a quick note. There are a couple things we are hoping you can look
at when time permits.

Just a couple niggles I think but they are impacting.

I have sent my comments to Avon who I think will share them with you but
I am never far away and can give comments or help with testing /
discovering if that would help in any way.


Ttyl :-)
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

I haven't tested all possible combinations yesterday. Today I tried
Python 2.7.16 compiled from source on Ubuntu 18.04 and indeed it works fine. But it gets even funnier: on Ubuntu 19.04 I had no success at all with any version. Something else is going on. Maybe it is related to the gcc version or to some library that is used by Python. I have no idea.

Did you read the wiki on mysticbbs.com by chance? Its not just the enabled_shared option its also the character encoding that may different from system to system. I wonder if that could be factor in any of this?

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

Thanks for the additional info - good to know at what point it's
crashing out. It has now been solid for me on Ubuntu Server 18.04 with
the packaged version of python 2.7.15. I wonder if there is the
potential for g00r00 to implement a fix for this to make is less
dependent on specific python builds etc. It doesn't appear to be due to the "enable shared" compiling option as was originally suspected.

I have tested in the past with various Python versions. Any 2.7 version released in the past like 6 years or more *should* be fine (thats just an estimate).

As the wiki notes, there are two issues (that I found anyway) that can cause issues one is the shared option and the other is the codepage the RTL is compiled using or something like that, it has to match the operating system.

Its also possible there is a bug of course, but I have very much struggled to find issues with the actual Mystic functions. In theory if it works in Windows it should work in Linux assuming whatever environmental requirements are met.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

Yep, agreed. Seems Debian and Ubuntu 18.04 have enable-shared on by default in their packaged based python implementations anyhow.

From my experience this is not true. The defaults were absolutely not
compiled that way, at least not at the time I had tested (which was the final 18 LTS).

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

Hi g00r00!

Seriously, I thought the version you compile against is libpython
2.7 and it should make no difference if you have libpython 2.7.13
or 2.7.16 installed.

This is true. Any 2.7 version released in the last X (X being a long
time that I am unsure of exactly without researching) should work
fine.

This seems to apply only to Ubuntu 18.04. We tested different 2.7.x version on Debian and most of them didn't work properly with Mystic.

The issue only is that the operating systems that come with 2.7 by
default seem to often compile it with the ability to embed it
disabled. This makes it not worth no only with Mythic, but lots of
other applications that use a Python subsystem. I don't know why the operating systems do this, I've seen plenty of people complaining
about it over the years.

Ubuntu and Debian both have libpython, which is also used by other packages in Debian/Ubunutu and they happily use any version of libpython2.7.

I don't think the problem we discovered has anything to do with a missing --enable-shared build option. But I don't have a good explantation what causes it and I don't see any clear pattern.

--- GoldED+/LNX 1.1.5-b20180707
* Origin: format of this message has been mangled by Mystic BBS (21:1/151)

Yep, agreed. Seems Debian and Ubuntu 18.04 have enable-shared on
by default in their packaged based python implementations anyhow.

From my experience this is not true. The defaults were absolutely not compiled that way, at least not at the time I had tested (which was
the final 18 LTS).

Maybe I misunderstand what --shared-enabled does. The fact is that Mystic's Python support works on Ubuntu without the need to compile Python.

--- GoldED+/LNX 1.1.5-b20180707
* Origin: format of this message has been mangled by Mystic BBS (21:1/151)

I have sent my comments to Avon who I think will share them with you but
I am never far away and can give comments or help with testing / discovering if that would help in any way.

I am sure he will pass them along! I haven't had time to get my BBS back up and see where I am with that, so Avon may be waiting for me to get more organized to share what he has collected, assuming he has collected things :)

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)

I haven't tested all possible combinations yesterday. Today I
tried Python 2.7.16 compiled from source on Ubuntu 18.04 and
indeed it works fine. But it gets even funnier: on Ubuntu 19.04 I
had no success at all with any version. Something else is going
on. Maybe it is related to the gcc version or to some library
that is used by Python. I have no idea.

Did you read the wiki on mysticbbs.com by chance? Its not just the enabled_shared option its also the character encoding that may
different from system to system. I wonder if that could be factor in
any of this?

Yeah, I did and I followed the steps in the wiki to build Python.

I wonder, would it make a difference, if Mystic were compiled from sources on the distribution it runs? Would the problem dissapear, if it were compiled on Debian?

--- GoldED+/LNX 1.1.5-b20180707
* Origin: format of this message has been mangled by Mystic BBS (21:1/151)

On 25 Oct 2019 at 08:54p, g00r00 pondered and said...

Things have been pretty hectic for me lately but I am still very slowly working on things. I've been meaning to dial out for a while now I just never seem to get around to having a big enough window of time that I
feel should be spent trying to catch up on 6 months of messages :)

I'd just pick up from the here now vs. trying to review too much old stuff, that way the tidal wave doesn't wash over you too much. I confess I have days when I do very little in the BBS realm and others when I do more as the mood takes me. Anyways nice to see you active again and (as always) let me know
how I can be of help to anything you're spit balling or working on as
time / inclination permit :)

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 25 Oct 2019 at 10:26p, g00r00 pondered and said...

I am sure he will pass them along! I haven't had time to get my BBS
back up and see where I am with that, so Avon may be waiting for me to
get more organized to share what he has collected, assuming he has collected things :)

I do have a few notes. I figured I'd just send them as a netmail to your fsxNet address if that works for you? You could pick them up from 21:1/100 when
you're ready. If you would like them another way, just let me know :)

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 10-25-19 20:54, g00r00 wrote to Avon <=-

Nice to see you active again. Welcome back, trust things are going well for you.

Things have been pretty hectic for me lately but I am still very slowly working on things. I've been meaning to dial out for a while now I
just never seem to get around to having a big enough window of time
that I feel should be spent trying to catch up on 6 months of messages
:)

Welcome back g00r00. :)



... This tagline is umop apisdn
=== MultiMail/Linux v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

On 25 Oct 2019 at 10:26p, g00r00 pondered and said...

I am sure he will pass them along! I haven't had time to get my BBS

Done :)

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

As the wiki notes, there are two issues (that I found anyway) that can cause issues one is the shared option and the other is the codepage the RTL is compiled using or something like that, it has to match the operating system.

Its also possible there is a bug of course, but I have very much
struggled to find issues with the actual Mystic functions. In theory if it works in Windows it should work in Linux assuming whatever environmental requirements are met.

Thanks g00r00 - I noticed that the 'enable shared' option was enabled out
of the box for most of the Debian and Ubuntu releases I tried. As you mentioned, I also wonder if it could be the codepage or something else that is different. If I get some time I'll see if I can pull that information out of Debian/Ubuntu. So far, Ubuntu 18.04 with the out of the box version of 2.7.15 is working great.

Thanks,
Mike

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Stellar Darkness BBS (21:4/162)

From my experience this is not true. The defaults were absolutely not compiled that way, at least not at the time I had tested (which was the final 18 LTS).

Interesting - I wonder if this is because I'm using Amazon EC2 AMIs instead
of the usual ISO based images. Here is the output from my BBS VM with the
OOTB version of 2.7.15:

Python 2.7.15+ (default, Oct 7 2019, 17:39:04)
[GCC 7.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.

import sysconfig
sysconfig.get_config_vars('Py_ENABLE_SHARED')

[1]

I'll see if I can check this with Debian 9/10, which was giving the problems earlier as well.

Thanks again!
Mike

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Stellar Darkness BBS (21:4/162)

On Tue, 29 Oct 2019 12:41:28 +0000
"lemonlime -> g00r00" <0@162.4.21> wrote:

From my experience this is not true. The defaults were absolutely not
compiled that way, at least not at the time I had tested (which was the
final 18 LTS).

Interesting - I wonder if this is because I'm using Amazon EC2 AMIs instead of the usual ISO based images. Here is the output from my BBS VM with the OOTB version of 2.7.15:

Python 2.7.15+ (default, Oct 7 2019, 17:39:04)
[GCC 7.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.

import sysconfig
sysconfig.get_config_vars('Py_ENABLE_SHARED')

[1]

I'll see if I can check this with Debian 9/10, which was giving the

problems

earlier as well.

I don't know if anything has changed since the initial release of Ubuntu 18.04,
but it's definitely enabled in Ubuntu 18.04.3 LTS. Same with Raspbian 10 (Buster).

---
* Origin: (21:1/151)