Has anyone bin able to install the 32 bit version of Mystic on Debian 32 running on a Ras Pi 5. The installer seems to work but the mis program will not start for me. It almost seems like that program was compiled with the 64 bit ARM libs. Other programs seem to work fine,

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: 13 Leader BBS (21:3/195)

Has anyone bin able to install the 32 bit version of Mystic on Debian 32 running on a Ras Pi 5. The installer seems to work but the mis program will not start for me. It almost seems like that program was compiled with the 64 bit ARM libs. Other programs seem to work fine,

I doubt the 32bit mis is compiled for 64bit unless there was an error.

What does ldd have to say about mis?

ldd ./mis might provide some insight.

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

What does ldd have to say about mis?

ldd ./mis might provide some insight.

Here you are:

lld ./mis

lld is a generic driver.
Invoke ld.lld (Unix), ld64.lld (macOS), lld-link (Windows), wasm-ld (WebAssembly) instead

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: 13 Leader BBS (21:3/195)

I doubt the 32bit mis is compiled for 64bit unless there was an error.

Sorry, below is what happens with I run it, from the correct folder.

-bash: ./mis: cannot execute:

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: 13 Leader BBS (21:3/195)

paul wrote to Al <=-

What does ldd have to say about mis?

ldd ./mis might provide some insight.

Here you are:

lld ./mis

lld is a generic driver.

It's a 3-letter "word". You mis-spelled it. :(



... He does the work of 3 Men...Moe, Larry & Curly
=== MultiMail/Linux v0.52
--- SBBSecho 3.22-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

What does ldd have to say about mis?

ldd ./mis might provide some insight.

Here you are:

lld ./mis

Be sure you run ldd. ldd will print shared object dependencies.

I am not sure what lld will provide.

When I run ldd against my bbbs executible I see this.

linux-vdso.so.1 (0x00007f26b76e2000)

libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f26b76b2000)

libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f26b76ad000)

libc.so.6 => /usr/lib/libc.so.6 (0x00007f26b74c7000)

/lib64/ld-linux-x86-64.so.2 (0x00007f26b76e4000)

All the above files are found and BBBS runs as expected. If you see any files listed in red (missing) then your software will not run.

When I run ldd against a recent 64bit mis it is fine, if I run ldd against a recent 32 bit mis it says the file is not executible.

Be sure you are running a Pi version of Mystic on a Pi. A linux executible probably will not run on a Pi.

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 25 Nov 2024, paul said the following...

Here you are:

lld ./mis

lld is a generic driver.

Make sure you are starting mis with the server option

./mis -server


|11 Bucko |14- |06Wrong Number Family Of BBS' |07- |03www.wrgnbr.com

... No one knows what's next, but everybody does it.

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

On 25 Nov 2024, Bucko said the following...

Here you are:

lld ./mis

lld is a generic driver.

Make sure you are starting mis with the server option

./mis -server

Also check the ownership of the folder Mystic is in, make sure it is not root:root...


|11 Bucko |14- |06Wrong Number Family Of BBS' |07- |03www.wrgnbr.com

... If a pig loses its voice, is it disgruntled?

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

It's a 3-letter "word". You mis-spelled it. :(

Well that was kinda dumb! Sorry about that. The folder should be fine and
does not make a differnace when run as root:

$ ldd ./mis -server
./mis:/usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so => /usr/lib/arm-linux-gnueabihf/libarmmem-v8l.so (0xf7820000)libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0xf7835000)libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0xf780a000)libutil.so.1 => /lib/arm-linux-gnueabihf/libutil.so.1 (0xf7807000)libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xf768e000)/lib/ld-linux.so.3 => /lib/ld-linux-armhf.so.3 (0xf783b000)

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: 13 Leader BBS (21:3/195)

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: 13 Leader BBS (21:3/195)

One other thing is that Mystic A39 runs with no problems at all, as you can
see above.

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: 13 Leader BBS (21:3/195)

One other thing is that Mystic A39 runs with no problems at all, as you can see above.

On linux I can run 32bit applications if I have multilib enabled (I don't).

Is your OS 32bit or 64bit? If 64bit you may need some sort of multilib support to run 32bit apps.

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On linux I can run 32bit applications if I have multilib enabled (I don't).

This is the 32 bit version of Raspberry Pi OS for sure. I was only trying to upgrade to the current verion of Mystic - 32 or 64. I have tried in the
past and the jump from A39 to the current never works for me. Just too many versions and too much has changed.

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: 13 Leader BBS (21:3/195)

This is the 32 bit version of Raspberry Pi OS for sure.

OK, it should run a 32bit Pi Mystic, I would think/hope.

I should have suggested the file command. It will give you some details about a binary file, even if it won't run. It should tell you if a file is for 32 or 64 bit.

file mis

I was only trying to upgrade to the current verion of Mystic - 32 or 64. I have tried in the past and the jump from A39 to the current never works for me. Just too many versions and too much has changed.

I have been there. A39 was one of the versions of Mystic I ran some time ago.

You might want to back up your message/file base, install a fresh Mystic (if it runs for you) and start from scratch. Quite a bit of work but doable.

Recent versions of Mystic only support Jam message bases. If your message bases are squish you won't be able to use them with newer version of Mystic.

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

OK, it should run a 32bit Pi Mystic, I would think/hope.

I should have suggested the file command. It will give you some details about a binary file, even if it won't run. It should tell you if a file
is for 32 or 64 bit.

file mis

So I found the problem and it was a simple fix. It seems debian bookworm is missing a sym link to ld-linux.so.3 - at least for the Pi 5. When I created the link mis runs without an issue. Found the fix in this thread on the Pi forums --> https://forums.raspberrypi.com/viewtopic.php?t=369895

Explains why anything not using ld-linux.so.3 works but mis and mystic failed.

Who woulda thot :)

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: 13 Leader BBS (21:3/195)

Ok I have another simple mystic question for version a48.

When creating messages bases for EchoMail,the base type does not list
echomail as an option. Just Netmail, Local, Network and Newsgroup are
options.

What's with that?

P.

--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: 13 Leader BBS (21:3/195)

OK, it should run a 32bit Pi Mystic, I would think/hope.

I should have suggested the file command. It will give you some details
about a binary file, even if it won't run. It should tell you if a file
is for 32 or 64 bit.

file mis

So I found the problem and it was a simple fix. It seems debian bookworm is missing a sym link to ld-linux.so.3 - at least for the Pi 5. When I created the link mis runs without an issue. Found the fix in this thread on the Pi forums --> https://forums.raspberrypi.com/viewtopic.php?t=369895

Explains why anything not using ld-linux.so.3 works but mis and mystic failed.

A sneaky one huh? :)

Who woulda thot :)

Yep, that happens sometimes. I remember yoears ago creating a libhunspell.so symlink for Mystic's spell checker because my distro didn't have one.

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Ok I have another simple mystic question for version a48.

When creating messages bases for EchoMail,the base type does not list echomail as an option. Just Netmail, Local, Network and Newsgroup are options.

What's with that?

Use Network for echomail and Netmail for netmail areas.

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 27 Nov 2024, paul said the following...

When creating messages bases for EchoMail,the base type does not list echomail as an option. Just Netmail, Local, Network and Newsgroup are options.

What's with that?

From whatsnew.txt:

+ Renamed the "Echo/Qwk" message base type setting to "Networked"


I think this was renamed to make it more apparent that you'd use this setting for networked QWK areas (e.g. DOVE-Net) as well as FTN style echomail areas.

It was/is common for new Mystic systems joining DOVE-Net to leave the message base type set to "Local" where no Tear or Origin lines are added to posted messages.


Jay

... Whenever I try to eat healthy a chocolate bar looks at me and Snickers

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Northern Realms (21:3/110)

Yep, that happens sometimes. I remember yoears ago creating a libhunspell.so symlink for Mystic's spell checker because my distro
didn't have one.

Seems like it. I was just lucky to find it in the Pi forums. The post was not about Mystic at all.

... Nine times out of ten the statisticians are wrong

--- Mystic BBS v1.12 A48 (Raspberry Pi/32)
* Origin: https://13leader.net (21:3/195)

I think this was renamed to make it more apparent that you'd use this setting for networked QWK areas (e.g. DOVE-Net) as well as FTN style echomail areas.

Yes. that could be.

... Tech support is just a busy signal away

--- Mystic BBS v1.12 A48 (Raspberry Pi/32)
* Origin: https://13leader.net (21:3/195)