• Hiatus

    From Sean Dennis@1:18/200 to All on Tue Jan 11 19:39:14 2022
    Hi everyone,

    Due to a loss in the family of one of the MBSE team members, we will be
    taking a hiatus for an unspecified amount of time in development but we will
    be working on releasing version 1.0.8 of MBSE soon.

    -- Sean

    ___ MultiMail/FreeBSD v0.52

    --- Maximus/2 3.01
    * Origin: Outpost BBS (1:18/200)
  • From Vincent Coen@2:250/1 to Sean Dennis on Wed Jan 12 16:41:39 2022
    Hello Sean!

    Tuesday January 11 2022 19:39, you wrote to All:

    Hi everyone,

    Due to a loss in the family of one of the MBSE team members, we will
    be taking a hiatus for an unspecified amount of time in development
    but we will be working on releasing version 1.0.8 of MBSE soon.

    Please pass on my condolences for his loss.


    Vincent
    --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Sean Dennis@1:18/200 to Vincent Coen on Wed Jan 12 12:55:05 2022
    Hello Vincent,

    Wednesday January 12 2022 16:41, you wrote to me:

    Please pass on my condolences for his loss.

    I will, thanks.

    I am busy working on a README.FreeBSD right now and Andrew is wanting to get out another release. I am trying to teach myself enough C to start fixing a few things here and there.

    -- Sean

    ... Hold a true friend with both your hands. - Nigerian proverb
    --- GoldED/2 3.0.1
    * Origin: Outpost BBS Sysop Console (1:18/200)
  • From Vincent Coen@2:250/1 to Sean Dennis on Wed Jan 12 19:17:01 2022
    Hello Sean!

    Wednesday January 12 2022 12:55, you wrote to me:

    Hello Vincent,

    Wednesday January 12 2022 16:41, you wrote to me:

    Please pass on my condolences for his loss.

    I will, thanks.

    I am busy working on a README.FreeBSD right now and Andrew is wanting
    to get out another release. I am trying to teach myself enough C to
    start fixing a few things here and there.

    Weel if you want some possible tasks / functions -

    1. Simple editor to deal with file descriptions. Low.

    2. Procedure to allow sysop to restrict characters used in file descriptions such as outside A - Z, a - z, 0 - 9, single period, comma, equals semmi-comma (;) etc that the sysop can define in a field with mbsetup. That way if they screw it up it is down to them to correct. Mid to High.

    3. Check and if not fix for auto respond to ALLFIX, Filemgr requests by send response back to originator during the transmission but if not send response back as a poll after. Notice some system do this but have not seen mbse do it. Mid.

    4. Fix up some of the reported issues / bugs etc, if still open and sensible.

    5. Consider converting the internal data bases files to sqlite3 or mysql etc.
    This is not that easy as the DB code going by my memory of it, is all over
    the shop instead of their own modules that are called when required - but I
    could be wrong as that would be very sloppy programming but the code is very
    old.

    I would help but my eye sight is not as good as it was and I am very rusty with
    C, - Still do some programming in Cobol but that about it these days.

    Not that I am fond of C - way to close to Assembler and that goes back to the mid 60's to 70's when I was programming in such. I do not miss it - too easy to
    make mistakes at that low level :(

    Just a starter for 10 :)

    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Vincent Coen@2:250/1 to Sean Dennis on Wed Jan 12 21:12:31 2022
    Hello Sean!

    Got one more for you hopefully an easier one,

    When running mbsetup have parameter does does NOT stop the system from answering call/polls or making them - On the basis that the system not being changed but as back up protection if needed that any change about to be make when in this mode that the system is put on pause as current and released after
    a change (any change that effect the way the system works)

    OR

    just state that changes not permitted as mbsetup ruuning in system operating mode or words that that effect.


    I seem to be going into mbsetup just to look at setting such as aka's (7) to see what nodes are the system and general type settings and not change a thing as I am only looking say when writing a netmail.

    Suggestion, that if setting this mode a flag is set that can be read by all programs that refuses any changes with a error message OR pauses mbse operations as at present until changes are made the mbsetup exits.
    Its a screw up once, then it sticks to default until mbsetup exits.

    Out of interest there a a number of settings that could be made with the system
    fully operational but it would require going through them to see what fits that
    scenario.


    Vincent
    --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)