Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    MYSTIC    |    Mystic support echo    |    16,010 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 15,778 of 16,010    |
|    Paul Hayton to g00r00    |
|    Re: Builds    |
|    30 May 24 21:55:51    |
      TID: Mystic BBS 1.12 A48       MSGID: 3:770/100 9bc46546       REPLY: 1:129/215 3ad9b425       TZUTC: 1200       On 29 May 2024 at 10:12p, g00r00 pondered and said...                g0> This shoud be fixed in the latest prealpha build but still would of        g0> 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)       SEEN-BY: 90/1 103/705 105/81 106/201 124/5016 128/260 129/305 153/757       SEEN-BY: 153/7715 154/10 30 203/0 218/700 840 220/70 221/0 226/17       SEEN-BY: 226/30 100 227/114 229/110 111 112 113 206 275 300 307 317       SEEN-BY: 229/400 426 428 470 550 664 700 240/1120 5832 266/512 267/800       SEEN-BY: 280/464 5003 282/1038 291/111 292/854 8125 301/1 320/219       SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124       SEEN-BY: 467/888 633/280 712/848 770/1 3 100 340 772/210 220 230 5020/400       SEEN-BY: 5054/30 5075/35       PATH: 770/100 1 280/464 460/58 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca