• Mystic not working in 32-bot Linux

    From bcw142@21:1/145 to Avon on Sunday, November 11, 2018 20:32:16
    I know you wonder what goes on with weird things like my Mystic not working anymore under 32-bit Linux. The Linux itself broke down a month after that,
    so it was something in the way fpc codes under Linux (all Linux programs including Firefox and such worked fine at the time, now it doesn't even boot). I used Universal Boot CD 5.33 to boot the system and changed all the paths in general and it showed an error in QWK so went in to Networking and updated the QWK path and it started booting. Found I had to update a couple of other paths in A39 to make it all work, but then it works fine booting off USB stick or CD. Mounted the old drive under /linux so changed all the paths to start with /linux/mystic which makes everything work. So the disk was working in the mystic area, was having issues with kernel or other OS stuff. The odd thing at first was it was only mystic that had issues. In time it stopped booting so then things made more sense. It's a really old disk, just need to replace it with something that will boot that system (old Dell).
    So nothing new and nothing really wrong with mystic, it was the system hardware, in this case an old hard drive with too many bad sectors. It was
    just mystic that showed the problems first and for some reason everything
    else seemed OK at the time (did run RAM tests and that works fine - Universal Boot CD is really running out of RAM).

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
  • From nugax@21:1/107 to All on Monday, November 12, 2018 08:03:17
    That sounds painful!

    I had to rebuild my BBS. Linux and/or Mystic starting just randomly stopping.
    I have a feeling it was Ubuntu server not mystic, and it was some of the dev packages Ubuntu installs causing an issue. I read online about similar
    issues, not bbs related.

    So I switched to Debian headless as my os and installed mystic fresh which is
    a pain.


    Seems to run well now, on Debian instead of Ubuntu.

    On 13:32 11/11 , bcw142 wrote:
    I know you wonder what goes on with weird things like my Mystic not working >anymore under 32-bit Linux. The Linux itself broke down a month after that, >so it was something in the way fpc codes under Linux (all Linux programs >including Firefox and such worked fine at the time, now it doesn't even boot). >I used Universal Boot CD 5.33 to boot the system and changed all the paths in >general and it showed an error in QWK so went in to Networking and updated the >QWK path and it started booting. Found I had to update a couple of other paths >in A39 to make it all work, but then it works fine booting off USB stick or CD.
    Mounted the old drive under /linux so changed all the paths to start with >/linux/mystic which makes everything work. So the disk was working in the >mystic area, was having issues with kernel or other OS stuff. The odd thing at >first was it was only mystic that had issues. In time it stopped booting so >then things made more sense. It's a really old disk, just need to replace it >with something that will boot that system (old Dell).
    So nothing new and nothing really wrong with mystic, it was the system >hardware, in this case an old hard drive with too many bad sectors. It was >just mystic that showed the problems first and for some reason everything >else seemed OK at the time (did run RAM tests and that works fine - Universal >Boot CD is really running out of RAM).

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)


    --
    yrNews Usenet Reader for iOS
    http://appstore.com/yrNewsUsenetReader

    --- Mystic BBS/NNTP v1.12 A39 2018/04/21 (Linux/64)
    * Origin: The ByteXchange BBS | bbs.thebytexchange.com (21:1/107)
  • From bcw142@21:1/145 to nugax on Wednesday, November 14, 2018 00:29:56
    On 11/12/18, nugax said the following...

    That sounds painful!

    On 13:32 11/11 , bcw142 wrote:
    So nothing new and nothing really wrong with mystic, it was the system >hardware, in this case an old hard drive with too many bad sectors. It wa >just mystic that showed the problems first and for some reason everything >else seemed OK at the time (did run RAM tests and that works fine - Unive >Boot CD is really running out of RAM).

    Just need to get a new SATA drive to replace the old one ;)

    _________________________________
    < A penny saved is a penny taxed. >
    ---------------------------------
    \ ^__^
    \ (oo)\_______
    (__)\ )\/\
    ||----w |
    || ||

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
  • From Avon@21:1/101 to bcw142 on Wednesday, November 14, 2018 20:33:16
    On 11/11/18, bcw142 pondered and said...

    Dell). So nothing new and nothing really wrong with mystic, it was the system hardware, in this case an old hard drive with too many bad
    sectors. It was just mystic that showed the problems first and for some

    interesting, thanks for the report.

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