I use Virtualmin GPL for my web hosting panel, so I thought I'd try integrating
it with the MBSE setup on this node. I had to delete mbse and my users, and the bbs group temporarily, then delete the domain in Virtualmin and recreate it, then recreate the MBSE users and group, but everything seems to be working so far, at least for mail, after I fixed some permission. Still working on the
web server and ftp setup, but that doesn't look like much of a problem. I do have $MBSE_ROOT=/home/mbse, and linked Virtualmin's homes directory to /home/mbse/home.

Anyone else tried this?


Greetings, James Digriz
email: jbdigriz@bbs.dragonsweb.org

--- MBSE BBS v1.0.7.4 (GNU/Linux-x86_64)
* Origin: DragonsWeb Labs (1:123/755)

James Digriz wrote to All:

I use Virtualmin GPL for my web hosting panel, so I thought I'd try integrating
it with the MBSE setup on this node. I had to delete mbse and my users, and
the bbs group temporarily, then delete the domain in Virtualmin and recreate
it, then recreate the MBSE users and group, but everything seems to be working
so far, at least for mail, after I fixed some permission. Still working on the
web server and ftp setup, but that doesn't look like much of a problem. I do
have $MBSE_ROOT=/home/mbse, and linked Virtualmin's homes directory to /home/mbse/home.

If you do this, you of course want to back up /home/mbse, and then move back in
place of the /home/mbse that virtualmin creates, and also move relevant contents from /home/mbse.virtualmin in to the restored /home/mbse hierarchy. What I did, anyway. Sorry for replying to myself; just wanted to spare any heartache. :-)


Greetings, James Digriz
email: jbdigriz@bbs.dragonsweb.org

--- MBSE BBS v1.0.7.4 (GNU/Linux-x86_64)
* Origin: DragonsWeb Labs (1:123/755)

Hello James!

Sunday April 08 2018 17:06, you wrote to All:

I use Virtualmin GPL for my web hosting panel, so I thought I'd try integrating
it with the MBSE setup on this node. I had to delete mbse and my
users, and the bbs group temporarily, then delete the domain in
Virtualmin and recreate it, then recreate the MBSE users and group,
but everything seems to be working so far, at least for mail, after I
fixed some permission. Still working on the web server and ftp setup,
but that doesn't look like much of a problem. I do have $MBSE_ROOT=/home/mbse, and linked Virtualmin's homes directory
to /home/mbse/home.

Anyone else tried this?

For interest to all :

If using the althernative install directory such as using ./configure --PREFIX=/home/mbse

The bbs will install into that directory BUT the SETUP.sh script is not changed
and will be wrong and so you will have to manually change the path used
e.g., MHOME=/opt/mbse
to =/home/mbse

You must do this before using otherwise the users created will have incorrect settings and will have to manually change the mbse, bbs users that it creates.

Would be nice if the configure script does this but . . .


Vince

--- Mageia Linux v5.1/Mbse v1.0.7.6/GoldED+/LNX 1.1.501-b20150715
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Vince Coen wrote to James Digriz:

Hello James!

Sunday April 08 2018 17:06, you wrote to All:

I use Virtualmin GPL for my web hosting panel, so I thought I'd try integrating
it with the MBSE setup on this node. I had to delete mbse and my

^^^^
user mbse

users, and the bbs group temporarily, then delete the domain in Virtualmin and recreate it, then recreate the MBSE users and group,

^^^^^^^^^^^^^^^
unix users and group

but everything seems to be working so far, at least for mail, after I fixed some permission. Still working on the web server and ftp setup, but that doesn't look like much of a problem. I do have $MBSE_ROOT=/home/mbse, and linked Virtualmin's homes directory
to /home/mbse/home.

Anyone else tried this?

For interest to all :

If using the althernative install directory such as using ./configure --PREFIX=/home/mbse

The bbs will install into that directory BUT the SETUP.sh script is not changed
and will be wrong and so you will have to manually change the path used e.g., MHOME=/opt/mbse
to =/home/mbse

You must do this before using otherwise the users created will have incorrect
settings and will have to manually change the mbse, bbs users that it creates.

Would be nice if the configure script does this but . . .

Vince

--- Mageia Linux v5.1/Mbse v1.0.7.6/GoldED+/LNX 1.1.501-b20150715
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Right, should have mentioned that. Thanks, Vince.

I should also note that I ended up with UID's and GID's both =${USER}, not ${USER}.BBS as a I believe MBSE expects. Doing more testing and checking today to make sure there aren't any surprises, or corrections needed, there.

Greetings, James Digriz
email: jbdigriz@bbs.dragonsweb.org

--- MBSE BBS v1.0.7.4 (GNU/Linux-x86_64)
* Origin: DragonsWeb Labs (1:123/755)

Hello Vince!

09 Apr 18 15:39, you wrote to James Digriz:

For interest to all :

If using the althernative install directory such as using ./configure --PREFIX=/home/mbse

The bbs will install into that directory BUT the SETUP.sh script is
not changed and will be wrong and so you will have to manually change
the path used e.g., MHOME=/opt/mbse to =/home/mbse

You must do this before using otherwise the users created will have incorrect settings and will have to manually change the mbse, bbs
users that it creates.

Would be nice if the configure script does this but . . .

I will look into this. However, from my initial reading of the SETUP.sh, it will require more than just replacing the MHOME value at the top of the script. I'll have to experiment on a test system to see if I can figure out what else will break in these cases.

Andrew

--- GoldED+/LNX 1.1.5-b20170303
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Andrew Leary wrote to Vince Coen:

Would be nice if the configure script does this but . . .

I will look into this. However, from my initial reading of the SETUP.sh, it
will require more than just replacing the MHOME value at the top of the script. I'll have to experiment on a test system to see if I can figure out
what else will break in these cases.

Andrew

That's all I did and everything seems to be working fine. MBSE on CentOS 6.9 + Virtualmin, Apache, Postfix, Dovecot, Proftpd, etc. Haven't tried on any other OS.

Finally found the hg repository and now running the latest snapshot. Kept getting errors trying to clone it, so downloaded the zip.



Greetings, James Digriz
email: jbdigriz@bbs.dragonsweb.org

--- MBSE BBS v1.0.7.6 (GNU/Linux-x86_64)
* Origin: DragonsWeb Labs (1:123/755)

Hello James!

22 Apr 18 18:46, you wrote to me:

Would be nice if the configure script does this but . . .

I will look into this. However, from my initial reading of the
SETUP.sh, it will require more than just replacing the MHOME value
at the top of the script. I'll have to experiment on a test system
to see if I can figure out what else will break in these cases.

Andrew

That's all I did and everything seems to be working fine. MBSE on
CentOS 6.9 + Virtualmin, Apache, Postfix, Dovecot, Proftpd, etc.
Haven't tried on any other OS.

OK. I haven't had the chance to actually test it yet. On my own systems I leave MBSE in the default /opt/mbse location.

Finally found the hg repository and now running the latest snapshot.
Kept getting errors trying to clone it, so downloaded the zip.

Thanks for reminding me; I need to check and see if the Git repository is up to date. To this point, the Hg repository has been the primary development repository. At some point in the near future, I will probably be switching to Git as primary.

Andrew

--- GoldED+/LNX 1.1.5-b20170303
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Andrew Leary wrote to James Digriz:

Hello James!

22 Apr 18 18:46, you wrote to me:

Would be nice if the configure script does this but . . .

I will look into this. However, from my initial reading of the
SETUP.sh, it will require more than just replacing the MHOME value
at the top of the script. I'll have to experiment on a test system
to see if I can figure out what else will break in these cases.

Andrew

That's all I did and everything seems to be working fine. MBSE on CentOS 6.9 + Virtualmin, Apache, Postfix, Dovecot, Proftpd, etc. Haven't tried on any other OS.

OK. I haven't had the chance to actually test it yet. On my own systems leave MBSE in the default /opt/mbse location.

It just seemed to me more straight-forward to use /home rather than /opt with Virtualmin. It might be possible to use the default MBSE setup with judicious use of bind mounts and/or symlinks, or you could recompile Virtualmin's modified httpd, but I haven't tried.

Finally found the hg repository and now running the latest snapshot. Kept getting errors trying to clone it, so downloaded the zip.

Thanks for reminding me; I need to check and see if the Git repository is up
to date. To this point, the Hg repository has been the primary development
repository. At some point in the near future, I will probably be switching to
Git as primary.

I tried the git repo the other day, it was up to 1.0.7.3. Had problems cloning it, too. That is probably my internet connection.

Thanks guys for keeping this software going.

Greetings, James Digriz
email: jbdigriz@bbs.dragonsweb.org

--- MBSE BBS v1.0.7.6 (GNU/Linux-x86_64)
* Origin: DragonsWeb Labs (1:123/755)

Hello James & Andrew!

Sunday April 22 2018 18:46, you wrote to Andrew Leary:

Andrew Leary wrote to Vince Coen:

Would be nice if the configure script does this but . . .

I will look into this. However, from my initial reading of the
SETUP.sh, it will require more than just replacing the MHOME value
at the top of the script. I'll have to experiment on a test system
to see if I can figure out what else will break in these cases.

Andrew

That's all I did and everything seems to be working fine. MBSE on
CentOS 6.9 + Virtualmin, Apache, Postfix, Dovecot, Proftpd, etc.
Haven't tried on any other OS.

Looking at the script SETUP.sh the obvious one is ths HOME setting but
There are other instances of /opt being used and I suggest that a new variable be setup say $HOMEROOT set as =/opt

With all the scripts vars using /opt changed to use HOMEROOT.

So now we have two vars near the beginning that need to be changed when the --prefix param is used in configure somehow.

If that is done then the SETUP script will work.

Just a question of working out how :)

.. and now I do not know how configure work in order to try it.

Any one volunteering ?


Vince

--- Mageia Linux v5.1/Mbse v1.0.7.6/GoldED+/LNX 1.1.501-b20150715
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Vince Coen wrote to James Digriz:

There are other instances of /opt being used and I suggest that a new variable
be setup say $HOMEROOT set as =/opt

With all the scripts vars using /opt changed to use HOMEROOT.

So now we have two vars near the beginning that need to be changed when the
--prefix param is used in configure somehow.

If that is done then the SETUP script will work.

Just a question of working out how :)

.. and now I do not know how configure work in order to try it.

Any one volunteering ?

Vince

I'd say you're assesment is correct. Since I brought it up, I'll take a shot at
it.


Greetings, James Digriz
email: jbdigriz@bbs.dragonsweb.org

--- MBSE BBS v1.0.7.6 (GNU/Linux-x86_64)
* Origin: DragonsWeb Labs (1:123/755)

Vince Coen wrote to James Digriz:

Looking at the script SETUP.sh the obvious one is ths HOME setting but There are other instances of /opt being used and I suggest that a new variable
be setup say $HOMEROOT set as =/opt

With all the scripts vars using /opt changed to use HOMEROOT.

So now we have two vars near the beginning that need to be changed when the
--prefix param is used in configure somehow.

If that is done then the SETUP script will work.

Just a question of working out how :)

.. and now I do not know how configure work in order to try it.

Any one volunteering ?

Vince

Ok, it turns out there's not a whole lot to do. Configure doesn't touch SETUP.sh or those scripts, and $HOME is already set in user mbse's profile, so all that has to be done in SETUP.sh is to break $MHOME down:
MHOME_ROOT=/home (for example), or /opt, or whatever you need. Then MHOME=$MHOME_ROOT/mbse.

You can then cd to the script directory and (again, for example):

sed s@/opt/@/home@/g rundoor.sh bbsdoor.sh

You can then go back to the top-level source dir and do the same with SETUP.sh
at
this point, but if you're compiling on *BSD you'll need then to readjust the BSD
references. I haven't done that since I'm not sure where Virtualmin puts its user homes under BSD. I'll check into it when I get a chance.

Now, change AC_DEFAULT_PREFIX=/opt/mbse to AC_DEFAULT_PREFIX=$HOME, run autoconf, and you're good to go. Unless I've missed something, the only thing left is to change any menu items needed. Configure or anything else doesn't touch any
of those that I can see. That's something that might be addressed if/when the code base is overhauled for new features or whatever.

later,




Greetings, James Digriz
email: jbdigriz@bbs.dragonsweb.org

--- MBSE BBS v1.0.7.6 (GNU/Linux-x86_64)
* Origin: DragonsWeb Labs (1:123/755)

Vince Coen wrote to James Digriz:

Looking at the script SETUP.sh the obvious one is ths HOME setting but There are other instances of /opt being used and I suggest that a new variable
be setup say $HOMEROOT set as =/opt

With all the scripts vars using /opt changed to use HOMEROOT.

So now we have two vars near the beginning that need to be changed when the
--prefix param is used in configure somehow.

If that is done then the SETUP script will work.

Just a question of working out how :)

.. and now I do not know how configure work in order to try it.

Any one volunteering ?

Vince

Aaargh! In my last reply that should have been:

AC_PREFIX_DEFAULT(/opt/mbse) change to AC_PREFIX_DEFAULT($HOME)

in configure.ac

The important point being that SETUP.sh runs first, and by the time you log
in as mbse, $HOME is already set to $MHOME_ROOT/mbse, or per your
naming, $HOMEROOT/mbse (or whatever), so that all you have to do is run autoconf one time, and configure will pick it up and pass it along anywhere it's used in the code.

The initial MBSE setup could be redone to make things easier for packagers. Wasn't somebody doing a .deb? Wonder how they handled it? Have to look.

later,

Greetings, James Digriz
email: jbdigriz@bbs.dragonsweb.org

--- MBSE BBS v1.0.7.6 (GNU/Linux-x86_64)
* Origin: DragonsWeb Labs (1:123/755)

James Digriz wrote to Vince Coen:

Vince Coen wrote to James Digriz:

The initial MBSE setup could be redone to make things easier for packagers.
Wasn't somebody doing a .deb? Wonder how they handled it? Have to look.

I was and have been but have not had a chance to work on it for awhile.
(see https://github.com/ftnapps/mbsebbs for instance.) What I do recall is that using /opt/mbse is hardcoded in quite a few places and that should really be fixed.

I also have had (and have been testing) a separately named test project that has that all changed (mostly<g>, since it's not working properly) but haven't been able to work on that recently either.


Jame


Greetings, Rj Clay
email: admftn@ftn.rocasa.net

--- MBSE BBS v1.0.6.8 (GNU/Linux-i386)
* Origin: ftn.rocasa.net (1:120/544)

Rj Clay wrote to James Digriz:

James Digriz wrote to Vince Coen:

Vince Coen wrote to James Digriz:

The initial MBSE setup could be redone to make things easier for packagers.
Wasn't somebody doing a .deb? Wonder how they handled it? Have to

look.

I was and have been but have not had a chance to work on it for awhile. (see https://github.com/ftnapps/mbsebbs for instance.) What I do recall is
that using /opt/mbse is hardcoded in quite a few places and that should really
be fixed.

With the changes I made I haven't had any problems that I've noticed, and virtualmin works as expected as well. I'm like you, though, and haven't had a chance yet to do any more extensive testing or submit changes. I have a lot on my plate right now,
including refurbishing, moving into, and setting up a new facility, and
a road
trip coming up. Hopefully I will get to it soon, as well as some other projects
on the back burner.

I also have had (and have been testing) a separately named test project that
has that all changed (mostly<g>, since it's not working properly) but haven't
been able to work on that recently either.

I'll be interested to see that.

later,


Greetings, James Digriz
email: jbdigriz@bbs.dragonsweb.org

--- MBSE BBS v1.0.7.6 (GNU/Linux-x86_64)
* Origin: DragonsWeb Labs (1:123/755)

James Digriz wrote to Rj Clay:

Rj Clay wrote to James Digriz:

I also have had (and have been testing) a separately named test project that
has that all changed (mostly<g>, since it's not working properly) but haven't been able to work on that recently either.

I'll be interested to see that.

That's at https://github.com/ftnapps/FTNd. The debian packaging is in the 'debian' branch. I have it installing to /usr/lib/ftnd & still use symlinks because I don't know that I have all of the '/opt/mbse' hard codeing fixed.
I only have it running on my laptop... (It's a test system, after all...)



Jame



Greetings, Rj Clay
email: admftn@ftn.rocasa.net

--- MBSE BBS v1.0.6.8 (GNU/Linux-i386)
* Origin: ftn.rocasa.net (1:120/544)

Hello Rj!

13 Jun 2018 06:16, Rj Clay wrote to James Digriz:

I only have it running on my laptop... (It's a test system, after all...)

it says me that mbse needs more linux fixing if it needs symlinks

and i need to provide more gentoo stable ebuilds for husky, work in slow progress here, current is done from cvs, where all fails :)


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.1.2 (Linux/4.17.2-gentoo (x86_64))
* Origin: I will always keep a PC running CPM 3.0 (2:230/0)

Benny,

Benny Pedersen wrote to Rj Clay:

Hello Rj!

13 Jun 2018 06:16, Rj Clay wrote to James Digriz:

I only have it running on my laptop... (It's a test system, after all...)

it says me that mbse needs more linux fixing if it needs symlinks

Exactly. I don't know that it still _requires_ them but in order to be able to run a test system, I figured it's easy to provide them just in case.

and i need to provide more gentoo stable ebuilds for husky, work in slow progress here, current is done from cvs, where all fails :)

I've been wanting to update the husky debian packages but all I've had a chance to do is make them available at the package repo at ftn.rocasa.net/debian/. They all show as i386 and source pkg builds being available but I've not really had a chance to test any of them very much. Really need to try rebuilding them as amd64, although I don't really know if such old versions will run or even build properly.



Jame


Greetings, Rj Clay
email: admftn@ftn.rocasa.net

--- MBSE BBS v1.0.6.8 (GNU/Linux-i386)
* Origin: ftn.rocasa.net (1:120/544)