Hello There,

In an attempt to test MBSE I intalled a Ubuntu user "mbse" and then loaded the SETUP.sh file. First thing it complained about was that user mbse already existed, then promptly aborted. It would seem to me that installing as the intended user of the program would be the logical and prudent way to proceed. Is there a procedure to avoid this setup behavior?

Jeff

--- BBBS/Li6 v4.10 Dada-2
* Origin: The OuijaBoard - Anoka, MN (1:282/1031)

Hello There,
In an attempt to test MBSE I intalled a Ubuntu user "mbse" and then
loaded the SETUP.sh file. First thing it complained about was that
user mbse already existed, then promptly aborted. It would seem to
me that installing as the intended user of the program would be the
logical and prudent way to proceed. Is there a procedure to avoid
this setup behavior?
Jeff

In an attempt to work with the setup procedure. I deleted the user "mbse" and again loaded the SETUP.sh file as root. It then complained that user group "bbs" already existed and then again promptly aborted. User group "bbs" does already exist and I can not arbitrarily delete the group. It would seem that the setup of MBSE would be more flexible and be able to work with an existing environment. Instead of requiring that a system be reverse engineered to accommodate MBSE.


Jeff

--- BBBS/Li6 v4.10 Dada-2
* Origin: The OuijaBoard - Anoka, MN (1:282/1031)

On 02/27/16, Jeff Smith said the following...

In an attempt to test MBSE I intalled a Ubuntu user "mbse" and then
loaded the SETUP.sh file. First thing it complained about was that user mbse already existed, then promptly aborted. It would seem to me that installing as the intended user of the program would be the logical and prudent way to proceed. Is there a procedure to avoid this setup
behavior?

I think the SETUP.sh sets up your environment, including creating the mbse
user and then you log in as mbse and then build the BBS.

I guess you surprised the script by having an mbse user already in place. :)
I would delete that user and let the script create it again. It is going to place a few files in the mbse user directory.

Hope all is well out your way.. :)

Ttyl :-),
Al

--- Mystic BBS v1.12 A5 (Linux)
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On 02/27/16, Jeff Smith said the following...

In an attempt to work with the setup procedure. I deleted the user
"mbse" and again loaded the SETUP.sh file as root. It then complained
that user group "bbs" already existed and then again promptly aborted. User group "bbs" does already exist and I can not arbitrarily delete
the group. It would seem that the setup of MBSE would be more flexible
and be able to work with an existing environment. Instead of requiring that a system be reverse engineered to accommodate MBSE.

I agree, if the group bbs already exists the script should just carry on with what it needs to do.

If you can see in the script the line (or lines) that create the bbs group I suppose you could delete that part but the mbse developers can probably give you a better answer.

Ttyl :-),
Al

--- Mystic BBS v1.12 A5 (Linux)
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On 02/27/16, Jeff Smith said the following...

In an attempt to work with the setup procedure. I deleted the user
"mbse" and again loaded the SETUP.sh file as root. It then complained
that user group "bbs" already existed and then again promptly aborted.
User group "bbs" does already exist and I can not arbitrarily delete
the group. It would seem that the setup of MBSE would be more flexible
and be able to work with an existing environment. Instead of requiring
that a system be reverse engineered to accommodate MBSE.

I agree, if the group bbs already exists the script should just carry on with what it needs to do. If you can see in the script the line (or lines) that create the bbs group I suppose you could delete that part but the mbse developers can probably give you a better answer.

Agreed. I am weighing my desire to test MBSE against the work required to edit the setup procedure. I tried the MBSE install on a fresh install of Ubuntu v15.10. After the creation of user "mbse" and group "bbs" the install scipt (Run as root) generated a multitude of errors. Mostly related to directory and file creation. The the script ended indicating that the intsall had completed successfully. <sigh> Sadly, I see no point in continuing the testing process.


Jeff


--- BBBS/Li6 v4.10 Dada-2
* Origin: The OuijaBoard - Anoka, MN (1:282/1031)

Re: Re: Testing MBSE
By: Jeff Smith to Alan Ianson on Sat Feb 27 2016 01:52 pm

Agreed. I am weighing my desire to test MBSE against the work required to edit the setup procedure. I tried the MBSE install on a fresh install of Ubuntu v15.10. After the creation of user "mbse" and group "bbs" the install scipt (Run as root) generated a multitude of errors. Mostly related to directory and file creation. The the script ended indicating that the intsall had completed successfully. <sigh> Sadly, I see no point in continuing the testing process.

That's actually a dumb script, but it does some important things like adding example telnet lines to your inetd.conf and adding FTN mailer support to your /etc/services file.

It sounds like that script needs updating for newer versions of Ubuntu.

MBSE is definately worth a look though, a very tough FTN mailer and tosser for mail and files.. and a nice BBS too.. :)

Ttyl :-),
Al

... Never mind the Titanic - is there any news of the iceberg?
--- SBBSecho 2.33-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada - trmb.ca (1:153/757)

I think the SETUP.sh sets up your environment, including creating the mbse user and then you log in as mbse and then build the BBS.

You would be correct in this assumption. Reading the installation documentation FIRST before doing anything would have helped, too. :)

... If you believe in telekinesis, please raise my hand.
--- Wildcat! v6.4.454.2 (Nov 17 2011), Editor Mod v2.0
* Origin: Neptune;s Lair | Memphis, TN | winserver.org (1:116/18)

Jeff Smith wrote to All:

Hello There,

In an attempt to test MBSE I intalled a Ubuntu user "mbse" and then loaded the SETUP.sh file. First thing it complained about was that user mbse already existed, then promptly aborted. It would seem to me that installing as the intended user of the program would be the logical and prudent way to proceed. Is there a procedure to avoid this setup behavior?

I have also run in to many little gotcha's over the last little while with MBSE. I have found that Debian and it's variants are not the best environment for MBSE. Then again Arch Linux is also not 100% supported either because of the systemd scripts it uses. Either way I find the experience of setting up MBSE is the funnest and most frustrating part of it. Once it's up and running you don't have to pay much attention to it.

When I setup this Arch Linux box I already had my /opt/mbse directory and it was populated with all my BBS files as I had been running it under Linux Mint for a year. I ended up ignoring the setup script and just did the compile and install from make. One thing I did find from installing on Mint was that dependencies where hard to find. Getting all the little bits that where missing took some time and research. Watch the ./configure output and try to satisfy most of the missing dependancies. You can get them all (and you don't want to as some interfer with others). I also get lots of warnings when compiling but no hard errors. I also have issues after a successful compile with segfaults under Mint but not with Arch.

Hope this helps.

Stephen




---
The Bit Bucket BBS - telnet://bbs.thebitbucket.ca

--- MBSE BBS v1.0.6 (GNU/Linux-x86_64)
* Origin: The Bit Bucket BBS (1:342/13)

Hi Stephen!

03 Mar 16 08:48, you wrote to Jeff Smith:

Jeff Smith wrote to All:

Hello There,

In an attempt to test MBSE I intalled a Ubuntu user "mbse" and
then loaded the SETUP.sh file. First thing it complained about was
that user mbse already existed, then promptly aborted. It would
seem to me that installing as the intended user of the program
would be the logical and prudent way to proceed. Is there a
procedure to avoid this setup behavior?

I have also run in to many little gotcha's over the last little while
with MBSE. I have found that Debian and it's variants are not the
best environment for MBSE.

In what way? I've been running this older 32bit version on Debian for years, although that also means I don't necessarily remember what I had to go through to get it all working...

I'm also having issues getting a v1.06 versions working properly on a new 64bit system, but I'm not sure yet where the issue with that is...



RJ

--- GoldED+/LNX 1.1.5-b20110213
* Origin: ftn.rocasa.net (1:120/544)

RJ Clay wrote to Stephen Atkins:

Hi Stephen!

I have also run in to many little gotcha's over the last little while with MBSE. I have found that Debian and it's variants are not the best environment for MBSE.

In what way? I've been running this older 32bit version on Debian for years, although that also means I don't necessarily remember what I had to go
through to get it all working...

I'm also having issues getting a v1.06 versions working properly on a new
64bit system, but I'm not sure yet where the issue with that is...

When I tried compiling MBSE 1.0.6 and 1.0.4 under a fully updated Linux Mint (Debian variant) I kept getting all kinds of seg faults. At the time I didn't feel like sorting out what broke so I never investigated it. I was successful geting 1.0.4 to compile and run back in May 2013 using Linux Mint. So something changed between then and now that broke something. The only other hard parts was finding all the deb support packages. BTW both where on a 64 bit system.

Stephen

P.S. Sorry for the late reply. I've been a bit neglectful of my bbs the past couple of months.


---
The Bit Bucket BBS - telnet://bbs.thebitbucket.ca

--- MBSE BBS v1.0.6 (GNU/Linux-x86_64)
* Origin: The Bit Bucket BBS (1:342/13)

Hi Stephen!

15 Mar 16 13:56, you wrote to me:

RJ Clay wrote to Stephen Atkins:

I have also run in to many little gotcha's over the last
little while with MBSE. I have found that Debian and it's
variants are not the best environment for MBSE.

In what way? I've been running this older 32bit version on
Debian for years, although that also means I don't necessarily
remember what I had to go through to get it all working...

I'm also having issues getting a v1.06 versions working
properly on a new 64bit system, but I'm not sure yet where the
issue with that is...

When I tried compiling MBSE 1.0.6 and 1.0.4 under a fully updated
Linux Mint (Debian variant) I kept getting all kinds of seg faults.

My test install is on Debain v8 ('jessie'), and while it's not seg faulting (that I've seen...) there are also several issues with its operation.

At the time I didn't feel like sorting out what broke so I never investigated it. I was successful geting 1.0.4 to compile and run
back in May 2013 using Linux Mint. So something changed between then
and now that broke something.

If I can't make some progress with the test install, I me have to try to redo it with v1.04 instead of v1.06...

The only other hard parts was finding all the deb support packages.

I don't recall having any problem with that; but OTOH & considering the issues I'm having with the install, I've been wondering if I'm missing something.

BTW both where on a 64 bit system.

That's what the new system is; I'm planning to move 1:120/544 from a 32 bit Debian v6.0.10 install to a new 64 bit Debian v8 install.





RJ

--- GoldED+/LNX 1.1.5-b20110213
* Origin: ftn.rocasa.net (1:120/544)