Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    SYNC_SYSOPS    |    Synchronet Multinode BBS Software Suppor    |    33,243 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 32,474 of 33,243    |
|    Digital Man to Sniper    |
|    KIA BBS issues    |
|    14 Sep 25 13:13:27    |
      TZUTC: -0700       MSGID: 58597.sync_sys@1:103/705 2d2d3ccc       REPLY: 58594.sync_sys@1:103/705 2d2cf2d5       PID: Synchronet 3.21a-Linux master/7acaccaf1 Sep 08 2025 GCC 12.2.0       TID: SBBSecho 3.29-Linux master/7acaccaf1 Sep 08 2025 GCC 12.2.0       COLS: 80       BBSID: VERT       CHRS: CP437 2       FORMAT: flowed       NOTE: FSEditor.js v1.105        Re: KIA BBS issues        By: Sniper to Digital Man on Sun Sep 14 2025 09:22 am               > Ok, I will rerun it. To expand. I attempted this multiple times,        > initially, I tried to do the upgrade directly to 3.20 directly as was noted        > in the documentation. That failed badly, wouldn't load after the upgrade,        > and yes, I ran the jsexec update. So on the next attempt, I decided to do        > each update indivudually, 17, 18, 19 and 20. After 3.20 upgrade, and doing        > the jsexec update, the system reverted to new install. I verified each        > upgrade, 17, system was working, doors weren't. Next 18, after the update,        > the system worked, not the doors, and 19 worked, and the doors worked. When        > I did 3.20, the system was destroyed, and was walking me through the initial        > install, as I stated.              The old (v3.19) *.cnf files are still there. Nothing was "destroyed". If you       ran v3.20 withOUT running 'jsexec update' first (e.g. as an accident), you       could have stock/new install .ini files ni your ctrl directory. In that case,       running 'jsexec upgrade_to_v320' would fix that situation.               > Currently, I did the individual upgrades again, and        > stopped this time at 3.19, which is what I'm currently running. However I'm        > getting the error mentioned, not finding the sbbs.ini. So I will attempt a        > rerun of the jsexec update, and see if that fixes it. I'll let you know in        > a few. :)              "error finding sbbs.ini" doesn't sound like an upgrade issue. That sounds like       your SBBSCTRL environment variable isn't set correctly.       --         digital man (rob)              Sling Blade quote #15:       Doyle Hargraves: What'cha doin' with that lawn mower blade Karl?       Norco, CA WX: 75.1øF, 69.0% humidity, 4 mph WSW wind, 0.00 inches rain/24hrs       --- SBBSecho 3.29-Linux        * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)       SEEN-BY: 19/10 80/1 103/13 705 105/81 106/201 128/187 129/14 153/757       SEEN-BY: 153/7715 154/10 110 218/700 840 220/70 221/1 6 360 226/17       SEEN-BY: 226/30 227/114 229/110 206 317 400 426 428 470 700 705 240/1120       SEEN-BY: 266/512 267/800 280/464 5003 291/111 301/1 113 320/219 322/757       SEEN-BY: 335/364 341/66 234 342/200 396/45 423/81 460/58 633/267 280       SEEN-BY: 633/281 384 410 418 420 2744 712/848 770/1 100 340 772/220       SEEN-BY: 772/230 902/26 5020/1042 5075/35       PATH: 103/705 301/1 221/1 6 218/840 770/1 633/280 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca