• Roll call results

    From Vince Coen@2:250/1 to All on Thu Aug 8 19:05:45 2013
    Hello All!

    Well it looks like everyone is on dual core type cpu's and most using x64 variants of mbse with at least one sysop who has not responded but I can see from his allfix-file annoucements that he is on a x64 version of 95.13.

    In compiling v1.0.0 I have found a few errors namely that the
    one file that had been changed was not present not that it stopped the compile but it did add one s/w product, also the version had not been changed along with the copyright notice which has all been done on my version so I will release a 1.0.01 version to cover these silly points.

    The only other point is that we still get 12 warnings during the compile and I would like to clean this up if it is not too time consuming and do a 1.0.02 release in a week or two.




    Vince

    --- Linux/Mbse/GoldED+/LNX 1.1.5-b20120229
    * Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)
  • From mark lewis@1:3634/12.71 to Vince Coen on Thu Aug 8 21:31:52 2013

    On Thu, 08 Aug 2013, Vince Coen wrote to All:

    Well it looks like everyone is on dual core type cpu's and most
    using x64 variants of mbse

    not over here if/when i can get around to installing it again... single core 32bit unless i can dredge up some resources on one of the dual CPU (not dual core) 32 boxen ;)

    i didn't feel a need to respond earlier because most roll calls take several days or weeks and one sees the posted responses... i haven't seen much of anything in here since the roll call :(

    )\/(ark

    --- FMail/Win32 1.60
    * Origin: (1:3634/12.71)
  • From Gert Andersen@2:230/150 to Vince Coen on Fri Aug 9 15:34:06 2013
    Hello Vince!

    Thu Aug 08 2013, Vince Coen wrote to All:

    Well it looks like everyone is on dual core type cpu's and most using
    x64
    variants of mbse with at least one sysop who has not responded but I
    can see
    from his allfix-file annoucements that he is on a x64 version of 95.13.

    In compiling v1.0.0 I have found a few errors namely that the
    one file that had been changed was not present not that it stopped the
    compile
    but it did add one s/w product, also the version had not been changed
    along
    with the copyright notice which has all been done on my version so I
    will
    release a 1.0.01 version to cover these silly points.

    The only other point is that we still get 12 warnings during the
    compile and I
    would like to clean this up if it is not too time consuming and do a
    1.0.02
    release in a week or two.


    Then should you to look at the init.gentoo script file in mbsebbs-1.01.01/script/
    So this is working well.
    For my Linux gentoo have I installed my 2 mbsebbs in /opt/mbse/ and the one path line in init.gentoo is not working with PATH=/sbin:/bin:/usr/sbin:/usr/bin:
    Where I have to change the line to be;
    PATH=${PATH}:${MBSE_ROOT}/bin

    Else will my 2 mbsebbs not work as it not can find out where mbse_root is find.

    Take care,
    Gert

    - Get the best with linux -

    --- Msged/LNX 6.2.0 (Linux/2.6.39-gentoo-r1 (x86_64))
    * Origin: http://www.kofobbs.dk (2:230/150)
  • From Vince Coen@2:250/1 to Gert Andersen on Sat Aug 10 13:14:14 2013
    Hello Gert!

    09 Aug 13 15:34, you wrote to me:

    Then should you to look at the init.gentoo script file in mbsebbs-1.01.01/script/ So this is working well. For my Linux gentoo
    have I installed my 2 mbsebbs in /opt/mbse/ and the one path line in init.gentoo is not working
    with PATH=/sbin:/bin:/usr/sbin:/usr/bin: Where I have to change the
    line to be; PATH=${PATH}:${MBSE_ROOT}/bin

    Else will my 2 mbsebbs not work as it not can find out where mbse_root
    is find.

    You have something wrong in your set up.

    Here PATH for mbse is:

    PATH=/opt/mbse/bin:/usr/lib64/icecc/bin:/usr/local/bin:/usr/bin:/usr/games:/usr /

    It is the first item in the line and this is set up using the SETUP.sh script in mbsebbs/scripts in line 328 see {

    export PATH=\$HOME/bin:\$PATH
    export MBSE_ROOT=\$HOME
    }

    The gentoo script seems to have errors in that regard BUT I do not run gentoo so cannot confirm it. Also I could be talking a lot of twadle !




    Vince

    --- Linux/Mbse/GoldED+/LNX 1.1.5-b20120229
    * Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)
  • From Vince Coen@2:250/1 to Gert Andersen on Sat Aug 10 13:23:40 2013
    Hello Gert!

    10 Aug 13 13:14, I wrote to you:


    Here PATH for mbse is:

    PATH=/opt/mbse/bin:/usr/lib64/icecc/bin:/usr/local/bin:/usr/bin:/usr/g ames:/usr /

    It is the first item in the line and this is set up using the SETUP.sh script in mbsebbs/scripts in line 328 see {

    export PATH=\$HOME/bin:\$PATH
    export MBSE_ROOT=\$HOME
    }

    The gentoo script seems to have errors in that regard BUT I do not run gentoo so cannot confirm it. Also I could be talking a lot of twadle !


    Now had a closer look at that script and the above statement is total rubbish as it is used to run mbse not set it up. SETUP.sh is still used so the path should have been created corrrectly unless you did not run it.




    Vince

    --- Linux/Mbse/GoldED+/LNX 1.1.5-b20120229
    * Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)
  • From Gert Andersen@2:230/150 to Vince Coen on Sun Aug 11 10:01:04 2013
    * Reply to message originally in area CarbonArea

    Hello Vince!

    Sat Aug 10 2013, Vince Coen wrote to Gert Andersen:

    Here PATH for mbse is:

    PATH=/opt/mbse/bin:/usr/lib64/icecc/bin:/usr/local/bin:/usr/bin:/usr/g
    ames:/usr /

    It is the first item in the line and this is set up using the SETUP.sh
    script in mbsebbs/scripts in line 328 see {

    export PATH=\$HOME/bin:\$PATH
    export MBSE_ROOT=\$HOME
    }

    The gentoo script seems to have errors in that regard BUT I do not run
    gentoo so cannot confirm it. Also I could be talking a lot of twadle !


    Now had a closer look at that script and the above statement is total
    rubbish
    as it is used to run mbse not set it up. SETUP.sh is still used so the
    path
    should have been created corrrectly unless you did not run it.


    AS I have used MBSEBBS from version 0.0.92 and upgraded it up to 0.95.15 --> 1.0.0 with only upgraded way for it and SETUP.sh only been used once for version 0.0.92 and the other other versions used old setup there was done.
    So I used the working setting and I just unpack from /opt/mbse as tar xfvj /opt/mbsebbs-1.0.0.tar.bz2
    ./configure
    make
    su -> root pwd
    make install

    the used init.gentoo script to be :
    PATH=${PATH}:${MBSE_ROOT}/bin
    and the setting in init.gentoo have default as PATH=/sbin:/bin:/usr/sbin:/usr/bin:${MBSE_ROOT}/bin

    For last mbse 2 install on my sysop point 1 mbse install have I just tried something new with in init.gentoo script for version 1.0.01 to do this. PATH=${PATH}:/sbin:/bin:/usr/sbin:/usr/bin:${MBSE_ROOT}/bin
    and it is working fine.


    Take care,
    Gert

    - Get the best with linux -

    --- Msged/LNX 6.2.0 (Linux/2.6.39-gentoo-r1 (x86_64))
    * Origin: * The KofoBBS at http://www.kofobbs.dk * (2:230/150)
  • From Vince Coen@2:250/1 to Gert Andersen on Mon Aug 12 17:51:45 2013
    Hello Gert!

    11 Aug 13 10:01, you wrote to me:

    the used init.gentoo script to be :
    PATH=${PATH}:${MBSE_ROOT}/bin
    and the setting in init.gentoo have default as PATH=/sbin:/bin:/usr/sbin:/usr/bin:${MBSE_ROOT}/bin

    For last mbse 2 install on my sysop point 1 mbse install have I just
    tried something new with in init.gentoo script for version 1.0.01 to
    do this. PATH=${PATH}:/sbin:/bin:/usr/sbin:/usr/bin:${MBSE_ROOT}/bin a
    nd it is working fine.



    Looks ok but for (as on mine) setting the mbse path is in front of the others so that is searched first to speed up loading of the more common executables (used in mbse), e.g., PATH=$(MBSE_ROOT/bin:$PATH etc.



    Vince

    --- Linux/Mbse/GoldED+/LNX 1.1.5-b20120229
    * Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)