On 29 May 2024 at 10:12p, g00r00 pondered and said...

This shoud be fixed in the latest prealpha build but still would of
course be mostly untested.

Hi there.

Just a note that I tried the 32bit RPi build installer and it failed to allow me to install to /mystic/ from the root directory. I tried the sudo ./install option and that did not work either. Just hit the unable to create /mystic/ message.

If I opted for F5 use home directory it showed me the root path of /root/mystic so I can confirm I was acting with root privileges when I invoked sudo but hit the above mentioned problem.

Also during an earlier test on the last 64 bit build I found I was having problems using 'mis poll 21:1/100' when I set up 21:1/100 as a BinkP echomail node in Mystic.

For whatever reason it looked like mis was polling out to the BinkP server but the receiving system on another machine on my LAN did not see any incoming connection from MIS on the Rpi..

So just flagging there *may* be something in the Rpi code that *might* be amiss when 'mis poll' is calling a binkP style echomail node?

Another thing I spotted in the mutil.ini there's a reference in whatsnew.txt to the new function EchoUnlink.

; exclude=MYSTIC
; exclude=FSX_*

But the reason I mention this because I wanted to let you know that you've omitted the function call at the top of the mutil.ini

; EchoUnlink = false

[time passes]

I also ran a test using the exclude=FSX_* but have found it does not honour the switch, the reports I am generating 'action_mode=0' are still flagging fsxNet bases that should be excluded. So something is may be up there also.

I ran the function from mutil directly using ./mutil -run EcoUnlink

Best, Paul

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

On 30 May 2024 at 09:55p, Paul Hayton pondered and said...

Also during an earlier test on the last 64 bit build I found I was having problems using 'mis poll 21:1/100' when I set up 21:1/100 as a BinkP echomail node in Mystic.

Just as an addendum to this report, I tested the latest build for 32 bit and there was no problem getting mis poll to poll out to another system on my LAN.

Mystic BBS v1.12 A49 Raspberry Pi/32 Compiled 2024/05/29 19:07:23

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Welcome back, hope you're doing well.

Just copying this post I sent you last year, not sure if you saw it / there is/was any issues with the 64 bit build but just wanted to spotlight this should you be doing any checking/work on Mystic in the coming period.

Also do you envisage a release of A49 in the coming months? If yes, I going to hold off any any video updates until after that's out.

On 30 May 2024 at 09:55p, Paul Hayton pondered and said...

On 29 May 2024 at 10:12p, g00r00 pondered and said...

This shoud be fixed in the latest prealpha build but still would of course be mostly untested.

Hi there.

Just a note that I tried the 32bit RPi build installer and it failed to allow me to install to /mystic/ from the root directory. I tried the
sudo ./install option and that did not work either. Just hit the unable
to create /mystic/ message.

If I opted for F5 use home directory it showed me the root path of /root/mystic so I can confirm I was acting with root privileges when I invoked sudo but hit the above mentioned problem.

Also during an earlier test on the last 64 bit build I found I was having problems using 'mis poll 21:1/100' when I set up 21:1/100 as a BinkP echomail node in Mystic.

For whatever reason it looked like mis was polling out to the BinkP
server but the receiving system on another machine on my LAN did not see any incoming connection from MIS on the Rpi..

So just flagging there *may* be something in the Rpi code that *might*
be amiss when 'mis poll' is calling a binkP style echomail node?

Another thing I spotted in the mutil.ini there's a reference in whatsnew.txt to the new function EchoUnlink.

; exclude=MYSTIC
; exclude=FSX_*

But the reason I mention this because I wanted to let you know that
you've omitted the function call at the top of the mutil.ini

; EchoUnlink = false

[time passes]

I also ran a test using the exclude=FSX_* but have found it does not honour the switch, the reports I am generating 'action_mode=0' are still flagging fsxNet bases that should be excluded. So something is may be
up there also.

I ran the function from mutil directly using ./mutil -run EcoUnlink

Best, Paul

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)