Hi All!

Others may have already seen this but I was looking over the MBSE source code again, looking at what might be necessary in order to get MBSE to be more FHS complient and it looks to be that the main issue is that the paths for the configuration data files are hard coded to be "$MBSE_ROOT/etc/*.data".

Not sure how best to correct that in the code, but I think I'll start testing the idea by (manually) moving the /opt/mbse/etc directory and those *.data files to a different directory and making /opt/mbse/etc to be a sym link to that directory. If that works well enough, I'll update the debian packaging to install to the more standard FHS directories and install symlinks where appropriate, and see how that works...



Jame

--- GoldED+/LNX 1.1.5--b20111217
* Origin: RJC eeePC (1:120/419)

Hi All!

07 Apr 13 19:46, I wrote to all:

.... and it looks to be that the main issue is that the paths for the configuration data files are hard coded to be "$MBSE_ROOT/etc/*.data".

An example of how it does that in the code is as follows (mbtask/mbtask.c):

snprintf(cfgfn, PATH_MAX, "%s/etc/config.data", getenv("MBSE_ROOT"));

One relatively easy way (besides that there are so many places where it would need to be changed...<g>) to correct it would be to use a different environmental variable, perhaps MBSE_ETC or just MBSE_VAR, and drop that "/etc" out of the path.






Jame

--- GoldED+/LNX 1.1.5--b20111217
* Origin: RJC eeePC (1:120/419)

08 Apr 13 08:49, I wrote to all:

07 Apr 13 19:46, I wrote to all:

One relatively easy way (besides that there are so many places where
it would need to be changed...<g>) to correct it would be to use a different environmental variable, perhaps MBSE_ETC or just MBSE_VAR,

Found at least one instance of the same kind of issue for a 'var/' path file (var/mailer.hist in mbcico/answer.c), so perhaps MBSE_VAR would be better...


Jame


--- GoldED+/LNX 1.1.5--b20111217
* Origin: RJC eeePC (1:120/419)

Hi Jame,

Rj Clay wrote to All:

08 Apr 13 08:49, I wrote to all:

07 Apr 13 19:46, I wrote to all:

One relatively easy way (besides that there are so many places where it would need to be changed...<g>) to correct it would be to use a different environmental variable, perhaps MBSE_ETC or just MBSE_VAR,

Found at least one instance of the same kind of issue for a 'var/' path

file (var/mailer.hist in mbcico/answer.c), so perhaps MBSE_VAR would be better...

FHS still leaves room for /opt. There were two things that made me use /opt. When I started mbsebbs, FHS was still on the drawing board. And even now,
not everyone strctly uses FHS. The very first versions were using FHS but
that made it impossible to use on some distributions. Today this is not an issue anymore.

But the most important thing is the typical access and ownership of all the directories that mbse uses. For instance, never mix mbsebbs home directories with system home directories. It breaks for things that build hardcoded
paths on the mbse_root setting. Where would you point that to? Most stuff expects all files on that directory.


So ask yourself this, is it worth changing it?

gtx, Michiel.



Greetings, Michiel Broek

Email: mbse at fido dot mbse dot eu
Fidonet: Michiel Broek at 2:280/2802

... Stupidity is its own punishment!

--- MBSE BBS v0.95.15 (GNU/Linux-i386)
* Origin: MBSE Linux BBS. Made in the Netherlands (2:280/2802)

Hi Michiel!

09 Apr 13 19:57, you wrote to me:

Rj Clay wrote to All:

08 Apr 13 08:49, I wrote to all:

07 Apr 13 19:46, I wrote to all:

One relatively easy way (besides that there are so many places where
it would need to be changed...<g>) to correct it would be to use a
different environmental variable, perhaps MBSE_ETC or just MBSE_VAR,

Found at least one instance of the same kind of issue for a
'var/' path

file (var/mailer.hist in mbcico/answer.c), so perhaps MBSE_VAR
would be better...

FHS still leaves room for /opt.

Indeed it does.<g> But keep in mind that '/opt/*' is not really free form (see '/var/opt/<subdir>', for instance.). Usage of /srv/* is entirely free form but I thought that if I'm going to try changing it at all, why not just use the more standard directories. Also, keep in mind that I'm also thinking of this from the point of view of a packager, where it's not at all a good idea to install to '/opt' or '/srv' or '/usr/local/' because those are for the local system admin not the package manager.

But the most important thing is the typical access and ownership of
all the directories that mbse uses.

True, but I think that all taken care of.

For instance, never mix mbsebbs home directories with system home directories. It breaks for things that build hardcoded paths on the mbse_root setting.

Like? And keep in mind that I'm for the idea of changing all instances of that in the code...

Where would you point that to?

Which "that" are you referring to there? If to MBSE_ROOT itself, that I would default to '/usr/lib/mbsebbs'. The *.data files I'd default to having in '/var/lib/mbsebbs' which would require code changes. (I've thought of just trying a sym link as an initial change to the Debian packaging; that appears to work with, for instance, /opt/mbse/etc as a sym link to /var/lib/mbsebbs...)

Most stuff expects all files on that directory.

"stuff" = ?

So ask yourself this, is it worth changing it?

I think it is...<g> And at least for whatever I do for the Debian packaging, I'll be doing so.




Jame


--- GoldED+/LNX 1.1.5--b20111217
* Origin: RJC eeePC (1:120/419)

Hi Jame,

Indeed it does.<g> But keep in mind that '/opt/*' is not really free form
(see '/var/opt/<subdir>', for instance.). Usage of /srv/* is entirely free
form but I thought that if I'm going to try changing it at all, why not just
use the more standard directories. Also, keep in mind that I'm also thinking
of this from the point of view of a packager, where it's not at all a good

idea to install to '/opt' or '/srv' or '/usr/local/' because those are for

the
local system admin not the package manager.

But the most important thing is the typical access and ownership of all the directories that mbse uses.

True, but I think that all taken care of.

Ok.

For instance, never mix mbsebbs home directories with system home directories. It breaks for things that build hardcoded paths on the mbse_root setting.

Like? And keep in mind that I'm for the idea of changing all instances

of
that in the code...

Where would you point that to?

Which "that" are you referring to there? If to MBSE_ROOT itself, that would default to '/usr/lib/mbsebbs'. The *.data files I'd default to having
in '/var/lib/mbsebbs' which would require code changes. (I've thought of just
trying a sym link as an initial change to the Debian packaging; that appears
to work with, for instance, /opt/mbse/etc as a sym link to /var/lib/mbsebbs...)

Since most data then would go into /var/lib/mbsebbs I would point the
MBSE_ROOT variable to that location.

/usr/lib/mbsebbs is more for fixed data/libs etc. Thinking of that, on
Slackware that is /usr/lib64/mbsebbs, and I think on Gentoo as well.
I think Deb and buntu allways use /usr/lib but you know that better then me.

Most stuff expects all files on that directory.

"stuff" = ?

So ask yourself this, is it worth changing it?

I think it is...<g> And at least for whatever I do for the Debian packaging, I'll be doing so.

Let me know when it's finished, I'm just curious how it goes.

gtx, Michiel.


Greetings, Michiel Broek

Email: mbse at fido dot mbse dot eu
Fidonet: Michiel Broek at 2:280/2802

... Fools rush in wherever lottery tickets are sold

--- MBSE BBS v0.95.15 (GNU/Linux-i386)
* Origin: MBSE Linux BBS. Made in the Netherlands (2:280/2802)

Hi Michiel!

19 Apr 13 20:20, you wrote to me:

But the most important thing is the typical access and ownership
of all the directories that mbse uses.

True, but I think that all taken care of.

Ok.

At least in so far as that is initially set up during the package install. That it continues and maintains file access and ownership as necessary and without issues during operation is another thing entirely ...<g>

Where would you point that to?

Which "that" are you referring to there? If to MBSE_ROOT
itself, that would default to '/usr/lib/mbsebbs'. The *.data
files I'd default to having in '/var/lib/mbsebbs' which would
require code changes. ....

Since most data then would go into /var/lib/mbsebbs I would point the MBSE_ROOT variable to that location.

But isn't that variable also used for things like running the binaries?

So ask yourself this, is it worth changing it?

I think it is...<g> And at least for whatever I do for the
Debian packaging, I'll be doing so.

Let me know when it's finished, I'm just curious how it goes.

I'll do that; at least by posting here about it.





Jame


--- GoldED+/LNX 1.1.5--b20111217
* Origin: RJC eeePC (1:120/419)

Hi Michiel!

20 Apr 13 13:40, I wrote to you:

Let me know when it's finished, I'm just curious how it goes.

I did some work on the debian packaging [1], and a manual conversion of the MBSE BBS I have on this system. Now have it running locally using the following layout:

/usr/lib/mbsebbs
drwxr-xr-x 3 mbse bbs 4096 Apr 21 10:23 bin
lrwxrwxrwx 1 mbse bbs 16 Apr 21 09:23 etc -> /var/lib/mbsebbs
lrwxrwxrwx 1 mbse bbs 21 Apr 21 09:23 home -> /var/lib/mbsebbs/home lrwxrwxrwx 1 mbse bbs 28 Apr 21 09:23 html -> /usr/share/doc/mbsebbs/html lrwxrwxrwx 1 mbse bbs 20 Apr 21 13:27 log -> /var/lib/mbsebbs/log
lrwxrwxrwx 1 mbse bbs 16 Apr 21 12:45 share -> /var/lib/mbsebbs
lrwxrwxrwx 1 mbse bbs 20 Apr 21 10:56 tmp -> /var/lib/mbsebbs/tmp
lrwxrwxrwx 1 mbse bbs 16 Apr 21 10:56 var -> /var/lib/mbsebbs




Jame
[1] https://github.com/jame/mbsebbs/tree/debian-dev/debian

--- GoldED+/LNX 1.1.5--b20111217
* Origin: RJC eeePC (1:120/419)

Hello Rj!

07 Apr 2013 19:46, Rj Clay wrote to All:

configuration data files are hard coded to be "$MBSE_ROOT/etc/*.data".

it should really use /usr/local/etc since its installing with make install, if it create a package ebuild it should NOT use /usr/local/etc

or anything in /usr/local

first step is to make c code changes, then next step fix makefile to /usr/local/etc for config files

please dont make helpness in symlinks


Regards Benny

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

--- Msged/LNX 6.2.0 (Linux/3.9.6-gentoo (i686))
* Origin: duggi.junc.org where qico is waiting (2:230/0)

Hello Rj!

08 Apr 2013 08:49, Rj Clay wrote to All:

snprintf(cfgfn, PATH_MAX, "%s/etc/config.data", getenv("MBSE_ROOT"));

is should really just use $HOME, since mbse does not use any binding ports below 1024, telnet not even if its done with xinetd setups

$HOME/mbse/config.data


Regards Benny

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

--- Msged/LNX 6.2.0 (Linux/3.9.6-gentoo (i686))
* Origin: duggi.junc.org where qico is waiting (2:230/0)

Hello Rj!

09 Apr 2013 08:40, Rj Clay wrote to All:

Found at least one instance of the same kind of issue for a 'var/'
path file (var/mailer.hist in mbcico/answer.c), so perhaps MBSE_VAR would be better...

/etc is not binaries data files, this config go into /var, ascii config should be in /etc or $HOME


Regards Benny

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

--- Msged/LNX 6.2.0 (Linux/3.9.6-gentoo (i686))
* Origin: duggi.junc.org where qico is waiting (2:230/0)

Hello Michiel!

19 Apr 2013 20:20, Michiel Broek wrote to Rj Clay:

Since most data then would go into /var/lib/mbsebbs I would point the MBSE_ROOT variable to that location.

NO DONT

/usr/lib/mbsebbs is more for fixed data/libs etc. Thinking of that, on
Slackware that is /usr/lib64/mbsebbs, and I think on Gentoo as well.

what ?, /usr/lib64/ is for program code not data files

I think Deb and buntu allways use /usr/lib but you know that better
then me.

for current arch, remember /usr/lib on 64bit is symlinked to /usr/lib64 and /usr/lib32 is 32bit elf versions for program libs

be very carefull with that !


Regards Benny

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

--- Msged/LNX 6.2.0 (Linux/3.9.6-gentoo (i686))
* Origin: duggi.junc.org where qico is waiting (2:230/0)

Benny Pedersen wrote to Rj Clay:

Hello Rj!

08 Apr 2013 08:49, Rj Clay wrote to All:

snprintf(cfgfn, PATH_MAX, "%s/etc/config.data", getenv("MBSE_ROOT"));

is should really just use $HOME, since mbse does not use any binding ports

below 1024, telnet not even if its done with xinetd setups

$HOME/mbse/config.data

And where doe $HOME points to when user benny logis in? /opt/mbse/home/benny

Michiel

* Origin: duggi.junc.org where qico is waiting (2:230/0)

Greetings, Michiel Broek

Email: mbse at fido dot mbse dot eu
Fidonet: Michiel Broek at 2:280/2802

... The more one produces, the less one gets.

--- MBSE BBS v0.95.15 (GNU/Linux-i386)
* Origin: MBSE Linux BBS. Made in the Netherlands (2:280/2802)

Hello Michiel!

20 Jul 2013 14:02, Michiel Broek wrote to Benny Pedersen:

And where doe $HOME points to when user benny logis in? /opt/mbse/home/benny

mbse makes home dirs in chroot ?


Regards Benny

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

--- Msged/LNX 6.2.0 (Linux/3.10.1-gentoo (i686))
* Origin: duggi.junc.org where qico is waiting (2:230/0)

Benny Pedersen wrote to Michiel Broek:

Hello Michiel!

20 Jul 2013 14:02, Michiel Broek wrote to Benny Pedersen:

And where doe $HOME points to when user benny logis in? /opt/mbse/home/benny

mbse makes home dirs in chroot ?

No, but $MBSE_ROOT and $HOME are different for bbs users and. A normal bbs
user logs in and gets mbsebbs as shell, but they are all members of the
group bbs so that right on message bases etc are correct set. MBSE_ROOT
plays a role in that, $HOME is not really used if I remember that correctly.
So anything you do with these variables is playing with fire.

Ok, this might be my last reaction, I'm leaving fido and are disconnecting
all mail and files areas.

gtx, Michiel




Greetings, Michiel Broek

Email: mbse at fido dot mbse dot eu
Fidonet: Michiel Broek at 2:280/2802

... One night I came home very late. It was the next night

--- MBSE BBS v0.95.15 (GNU/Linux-i386)
* Origin: MBSE Linux BBS. Made in the Netherlands (2:280/2802)

Hello Michiel!

22 Jul 2013 10:31, Michiel Broek wrote to Benny Pedersen:

Benny Pedersen wrote to Michiel Broek:

Hello Michiel!

20 Jul 2013 14:02, Michiel Broek wrote to Benny Pedersen:

And where doe $HOME points to when user benny logis in?
/opt/mbse/home/benny

mbse makes home dirs in chroot ?

No, but $MBSE_ROOT and $HOME are different for bbs users and. A normal bbs user logs in and gets mbsebbs as shell, but they are all members of the group bbs so that right on message bases etc are correct set.

confussuion to me

MBSE_ROOT plays a role in that, $HOME is not really used if I remember

that

correctly.

but useradd does use ~ so what was the point in createing unix users ?

So anything you do with these variables is playing with fire.

chroot needs ~ somewhere :)

if mbse set it to /dev/null its works well

Ok, this might be my last reaction, I'm leaving fido and are disconnecting all mail and files areas.

so real life takes over :(

sad to see one more good linux programmer go


Regards Benny

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

--- Msged/LNX 6.2.0 (Linux/3.10.1-gentoo (i686))
* Origin: duggi.junc.org where qico is waiting (2:230/0)

Hi Benny!

30 Jun 13 14:28, you wrote to me:

09 Apr 2013 08:40, Rj Clay wrote to All:

Found at least one instance of the same kind of issue for a
'var/' path file (var/mailer.hist in mbcico/answer.c), so perhaps
MBSE_VAR would be better...

/etc is not binaries data files, this config go into /var, ascii
config should be in /etc or $HOME

Nothing in what you quoted mentions /etc, so I'm not sure what you're talking about...




Jame

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

Benny,

30 Jun 13 14:31, you wrote to Michiel Broek:

19 Apr 2013 20:20, Michiel Broek wrote to Rj Clay:

Since most data then would go into /var/lib/mbsebbs I would point
the MBSE_ROOT variable to that location.

NO DONT

Why not?


Jame

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

Hello RJ!

03 Aug 13 10:25, you wrote to Benny Pedersen:

Since most data then would go into /var/lib/mbsebbs I would
point the MBSE_ROOT variable to that location.

NO DONT

Why not?

As I run multi distro setups I prefer the standard method and path of /opt/mbse
and yes I did try and use /home/mbse many moons ago but had too many problems so have left it in /opt along with a stack of other apps.

I just have to remember to copy over /opt AND /home/vince to a new system.

Also using /var/lib could be in a restricted space area that is unique to the distro, another bag of worms.


Just my 5 penny worth.

For all: I have today release the latest and last mbse release from Michiel (that I received today) which is mbb10000.rar into fido land in the MBSE_BBS area so you should all see this within the next 3 - 24 hours.


Vince

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

Hi Vince!

03 Aug 13 20:11, you wrote to me:

03 Aug 13 10:25, you wrote to Benny Pedersen:

As I run multi distro setups I prefer the standard method and path of /opt/mbse

And /opt is for local admins, not for package systems. In case it wasn't clear; the reason I brought the discussion up was to figure out what changes would be necessary to configure the paths at build time (for the Debian packaging I'm doing, for instance), not so that the paths could be hard coded to something else.

I just have to remember to copy over /opt AND /home/vince to a new
system.

Also using /var/lib could be in a restricted space area that is unique
to the distro, another bag of worms.

Well for a locally built install, I imagine that would be somewhere in /var/local/. For the Debian packaging; I'd like to be able to configure the installed package to use /var/lib/mbsebbs...




Jame

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

Hello Vince.

03 Aug 13 20:11, you wrote to RJ Clay:

For all: I have today release the latest and last mbse release from Michiel (that I received today) which is mbb10000.rar into fido land
in the MBSE_BBS area so you should all see this within the next 3 - 24 hours.

Centos 6.4 32bit, latest updates.
mbse v1 from Michiel's website.


gcc -O2 -fno-strict-aliasing -Wall -Wshadow -Wwrite-strings -Wstrict-prototypes
-D_REENTRANT -I/usr/local/include -c
charset.c
gcc -O2 -fno-strict-aliasing -Wall -Wshadow -Wwrite-strings -Wstrict-prototypes
-D_REENTRANT -I/usr/local/include -c
remask.c
gmake[1]: *** No rule to make target `ftscprod.???', needed by `ftscprod.c'. Stop.
gmake[1]: Leaving directory `/opt/mbse/mbsebbs-1.0.0/lib'
make: *** [all] Error 2





Stephen

--- GoldED-NSF/LNX 1.1.5-b20130414
* Origin: Dragon's Lair BBS, Telnet: bbs.vk3heg.net (3:633/280)

Hello Stephen!

Mon Aug 05 2013, Stephen Walsh wrote to Vince Coen:

Hello Vince.

For all: I have today release the latest and last mbse release from
Michiel (that I received today) which is mbb10000.rar into fido land
in the MBSE_BBS area so you should all see this within the next 3 - 24
hours.

Centos 6.4 32bit, latest updates.
mbse v1 from Michiel's website.

gcc -O2 -fno-strict-aliasing -Wall -Wshadow -Wwrite-strings
-Wstrict-prototypes -D_REENTRANT -I/usr/local/include -c
charset.c
gcc -O2 -fno-strict-aliasing -Wall -Wshadow -Wwrite-strings
-Wstrict-prototypes -D_REENTRANT -I/usr/local/include -c
remask.c
gmake[1]: *** No rule to make target `ftscprod.???', needed by
`ftscprod.c'. Stop.
gmake[1]: Leaving directory `/opt/mbse/mbsebbs-1.0.0/lib'
make: *** [all] Error 2

ftscprod.012 and ftscprod.013 can be getting on ftp://ftp.kofobbs.dk/net/ftsc/


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)

Hello Stephen!

Monday August 05 2013 11:39, Stephen Walsh wrote to Vince Coen:

Centos 6.4 32bit, latest updates.
mbse v1 from Michiel's website.

gcc -O2 -fno-strict-aliasing -Wall -Wshadow -Wwrite-strings -Wstrict-prototypes -D_REENTRANT -I/usr/local/include
-c charset.c gcc -O2 -fno-strict-aliasing -Wall -Wshadow
-Wwrite-strings -Wstrict-prototypes -D_REENTRANT -I/usr/local/include
-c remask.c gmake[1]: *** No rule to make target `ftscprod.???',
needed by `ftscprod.c'. Stop. gmake[1]: Leaving directory `/opt/mbse/mbsebbs-1.0.0/lib'
make: *** [all] Error 2

Download ftscprod.013 from the FTSC website (http://ftsc.org) and copy it into mbsebbs-1.0.0/lib, then run make again.

Regards,

Andrew

---
* Origin: Bits & Bytes BBS * V.Everything! * 860/535-4284 (1:320/119)

Hello RJ!

03 Aug 2013 10:24, RJ Clay wrote to Benny Pedersen:

Found at least one instance of the same kind of issue for a
'var/' path file (var/mailer.hist in mbcico/answer.c), so perhaps
MBSE_VAR would be better...

/etc is not binaries data files, this config go into /var, ascii
config should be in /etc or $HOME

Nothing in what you quoted mentions /etc, so I'm not sure what
you're talking about...

FHS and MBSE_ROOT (chroot)

useradd defaults to /home/newuser, but its still possible to make mbse users have MBSE_ROOT/home/newuser, its just imho not FHS then


Regards Benny

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

--- Msged/LNX 6.2.0 (Linux/3.10.4-gentoo (i686))
* Origin: duggi.junc.org where qico is waiting (2:230/0)

Hello RJ!

03 Aug 2013 10:25, RJ Clay wrote to Benny Pedersen:

Since most data then would go into /var/lib/mbsebbs I would point
the MBSE_ROOT variable to that location.

NO DONT

Why not?

mbse would be the first one to break FHS then

postfix use /var/lib/postfix to berkdb database files, and /var/spool/postfix for mailqueue, and /etc/postfix for configuration, adding MBSE_ROOT will break more then just mbse, eg selinux


Regards Benny

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

--- Msged/LNX 6.2.0 (Linux/3.10.4-gentoo (i686))
* Origin: duggi.junc.org where qico is waiting (2:230/0)

Hello RJ!

05 Aug 2013 18:26, RJ Clay wrote to Vince Coen:

Well for a locally built install, I imagine that would be somewhere
in /var/local/. For the Debian packaging; I'd like to be able to configure the installed package to use /var/lib/mbsebbs...

well if its build in dep file then you most NOT use dirs that says local, if you build like freebsd where "make install" then you must use /usr/local, this is to prevent make install not overwriteing os files

in linux if i make with:

./configure
make
make install

then it should use /usr/local as MBSE_ROOT (prefixing)

/opt is for systems that does NOT use make install


Regards Benny

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

--- Msged/LNX 6.2.0 (Linux/3.10.4-gentoo (i686))
* Origin: duggi.junc.org where qico is waiting (2:230/0)

Hello RJ!

05 Aug 2013 18:26, RJ Clay wrote to Vince Coen:

And /opt is for local admins, not for package systems. In case it
wasn't

/opt is more for package manament of binaries that is not delivered with source
code compiled, it here on gentoo was such things as bitdefender and f-prot, and
unfree rar, precompiled from the author


Regards Benny

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

--- Msged/LNX 6.2.0 (Linux/3.10.4-gentoo (i686))
* Origin: duggi.junc.org where qico is waiting (2:230/0)

Hello Andrew.

06 Aug 13 08:09, you wrote to Stephen Walsh:

Monday August 05 2013 11:39, Stephen Walsh wrote to Vince Coen:

Centos 6.4 32bit, latest updates.
mbse v1 from Michiel's website.

gcc -O2 -fno-strict-aliasing -Wall -Wshadow -Wwrite-strings
-Wstrict-prototypes -D_REENTRANT -I/usr/local/include
-c charset.c gcc -O2 -fno-strict-aliasing -Wall -Wshadow
-Wwrite-strings -Wstrict-prototypes -D_REENTRANT
-I/usr/local/include -c remask.c gmake[1]: *** No rule to make
target `ftscprod.???', needed by `ftscprod.c'. Stop. gmake[1]:
Leaving directory `/opt/mbse/mbsebbs-1.0.0/lib'
make: *** [all] Error 2

Download ftscprod.013 from the FTSC website (http://ftsc.org) and copy
it into mbsebbs-1.0.0/lib, then run make again.

It will still have a error for Gentoo user as the init.gentoo script file in mbse-1.0.0/script not is working and been changed to the right command for PATH line
PATH=/sbin:/bin:/usr/sbin:/usr/bin:${MBSE_ROOT}/bin
shall be
PATH=${PATH}:${MBSE_ROOT}/bin

Gert

--- GoldED+/LNX 1.1.5-b20100314
* Origin: The Kofo System II BBS telnet://fido2.kofobbs.net (2:230/152)

Hello Andrew!

Tue Aug 06 2013, Andrew Leary wrote to Stephen Walsh:

Centos 6.4 32bit, latest updates.
mbse v1 from Michiel's website.

gcc -O2 -fno-strict-aliasing -Wall -Wshadow -Wwrite-strings
-Wstrict-prototypes -D_REENTRANT -I/usr/local/include
-c charset.c gcc -O2 -fno-strict-aliasing -Wall -Wshadow
-Wwrite-strings -Wstrict-prototypes -D_REENTRANT -I/usr/local/include
-c remask.c gmake[1]: *** No rule to make target `ftscprod.???',
needed by `ftscprod.c'. Stop. gmake[1]: Leaving directory
`/opt/mbse/mbsebbs-1.0.0/lib'
make: *** [all] Error 2

Download ftscprod.013 from the FTSC website (http://ftsc.org) and copy
it into mbsebbs-1.0.0/lib, then run make again.

This is not enough for Gentoo why the init.gentoo script file still has the same error from 2009 in its path line.
mbsebbs-1.0.0/script/init.gentoo PATH=/sbin:/bin:/usr/sbin:/usr/bin:${MBSE_ROOT}/bin
is not working after a reboot of the pc.
So the line shall changed to be:
PATH=${PATH}:${MBSE_ROOT}/bin
and it shall be before done of command .configure

Take care,
Gert

- Get the best with linux -

--- Msged/LNX 6.2.0 (Linux/2.6.39-gentoo-r1 (x86_64))
* Origin: * One step from heaven is not enough * (2:230/150)

Benny,

06 Aug 13 15:17, you wrote to me:

Hello RJ!

03 Aug 2013 10:25, RJ Clay wrote to Benny Pedersen:

Since most data then would go into /var/lib/mbsebbs I would
point the MBSE_ROOT variable to that location.

NO DONT

Why not?

mbse would be the first one to break FHS then

postfix use /var/lib/postfix to berkdb database files, and /var/spool/postfix for mailqueue, and /etc/postfix for configuration, adding MBSE_ROOT will break more then just mbse, eg selinux

Only if "MBSE_ROOT" is the only config item for the installation paths and it only points to one base directory. Which is what I would like to see fixed.


Jame


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

Hello Andrew.

06 Aug 13 08:09, you wrote to me:

Centos 6.4 32bit, latest updates.
mbse v1 from Michiel's website.

gcc -O2 -fno-strict-aliasing -Wall -Wshadow -Wwrite-strings
-Wstrict-prototypes -D_REENTRANT -I/usr/local/include
-c charset.c gcc -O2 -fno-strict-aliasing -Wall -Wshadow
-Wwrite-strings -Wstrict-prototypes -D_REENTRANT
-I/usr/local/include -c remask.c gmake[1]: *** No rule to make
target `ftscprod.???', needed by `ftscprod.c'. Stop. gmake[1]:
Leaving directory `/opt/mbse/mbsebbs-1.0.0/lib'
make: *** [all] Error 2

Download ftscprod.013 from the FTSC website (http://ftsc.org) and copy
it into mbsebbs-1.0.0/lib, then run make again.

Thnaks. Have now been able to compile v1!


Stephen

--- GoldED-NSF/LNX 1.1.5-b20130414
* Origin: Dragon's Lair BBS, Telnet: bbs.vk3heg.net (3:633/280)

is to prevent make install not overwriteing os files

in linux if i make with:

./configure
make
make install

then it should use /usr/local as MBSE_ROOT (prefixing)

/opt is for systems that does NOT use make install

Hmm, I was always taught that /opt was for the installation of OPTional packages/software?

--- BBBS/Li6 v4.10 Dada-1
* Origin: RiverNet BBS | Memphis TN | IP: 50.194.33.3 (1:116/18)

Hello Robert!

Fri Aug 09 2013, Robert Wolfe wrote to Benny Pedersen:

is to prevent make install not overwriteing os files

in linux if i make with:

./configure
make
make install

then it should use /usr/local as MBSE_ROOT (prefixing)

/opt is for systems that does NOT use make install

Hmm, I was always taught that /opt was for the installation of OPTional
packages/software?

If you using linux then is the mbsebbs give problem with change the default install or upgrade of old install to new install in /opt/
So for first time install is it a file named SETUP.sh there do the setup for mbsebbs and create setup as root for mbsebbs.
It makes the new user for mbse and group as bbs with permissions.
so default setup and install af mbsebbs is to set be /opt/mbse
have as root /root/tmp and a copy of mbse-1.01.01.tar.bz2 in /tmp
as root
tar vfxj mbsebbs.*.tar.bz2 (or version of mbsebbs)
cd in to mbsebbs-1.01.01
run ./SETUP.sh or sh ./SETUP.sh
when this is done and SETUP.sh has made new user mbse and group bbs - check it out of then new user and broup is working fine.
login as user mbse and try 'tar xfxj mbsebbs-1.01.01.tar.bz2
./configure
make
su root
make install

you have to run the last command make install to install mbsebbs and it binary files.
mbse is then been installed at and into /opt/mbse
then check if mbse is working.
for prefixing can it come to have problems to where mbsebbs mbse_root and binaries if found.
For Gentoo users can one file have to be changed a little for the path to be found for mbse bins.

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)

Hmm, I was always taught that /opt was for the installation of OPTional
packages/software?

If you using linux then is the mbsebbs give problem with change the default install or upgrade of old install to new install in /opt/
So for first time install is it a file named SETUP.sh there do the setup for mbsebbs and create setup as root for mbsebbs.
It makes the new user for mbse and group as bbs with permissions.
so default setup and install af mbsebbs is to set be /opt/mbse
have as root /root/tmp and a copy of mbse-1.01.01.tar.bz2 in /tmp
as root
tar vfxj mbsebbs.*.tar.bz2 (or version of mbsebbs)
cd in to mbsebbs-1.01.01
run ./SETUP.sh or sh ./SETUP.sh
when this is done and SETUP.sh has made new user mbse and group bbs - check it
out of then new user and broup is working fine.
login as user mbse and try 'tar xfxj mbsebbs-1.01.01.tar.bz2
./configure
make
su root
make install

Yes, Gert, I know all of this :) I've run MBSE at least twice before :) But, I suppose it is good that you posted this for the good of any newbies here :)

--- BBBS/Li6 v4.10 Dada-1
* Origin: RiverNet BBS | Memphis TN | IP: 50.194.33.3 (1:116/18)

* Reply to message originally in area CarbonArea

Hello Robert!

Fri Aug 09 2013, Robert Wolfe wrote to Gert Andersen:

* Forwarded from area 'MBSE'

Hmm, I was always taught that /opt was for the installation of OPTional
packages/software?

If you using linux then is the mbsebbs give problem with change the
default install or upgrade of old install to new install in /opt/
So for first time install is it a file named SETUP.sh there do the setup
for mbsebbs and create setup as root for mbsebbs.
It makes the new user for mbse and group as bbs with permissions.
so default setup and install af mbsebbs is to set be /opt/mbse
have as root /root/tmp and a copy of mbse-1.01.01.tar.bz2 in /tmp
as root
tar vfxj mbsebbs.*.tar.bz2 (or version of mbsebbs)
cd in to mbsebbs-1.0.01
run ./SETUP.sh or sh ./SETUP.sh
when this is done and SETUP.sh has made new user mbse and group bbs -
check it out of then new user and broup is working fine.
login as user mbse and try 'tar vfxj mbsebbs-1.0.01.tar.bz2
./configure
make
su root
make install

Yes, Gert, I know all of this :) I've run MBSE at least twice before
:) But, I suppose it is good that you posted this for the good of any
newbies here :)

Yes a I know and special for Gentoo users is there a little correction in a scripts file in mbsebbs-1.0.01/script/init.gentoo
the line for PATH can be made to have: PATH=${PATH}:/sbin:/bin:/usr/sbin:/usr/bin:${MBSE_ROOT}/bin

What there stand now in the line is: PATH=/sbin:/bin:/usr/sbin:/usr/bin:${MBSE_ROOT}/bin
by adding a ${PATH} right after the = sign will work for Gentoo users.
I have tried out on a installation of mbsebbs-1.0.01.

Btw: I have send you a email and a netmail to you is too on way to by Janis.


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)

Hello Robert!

09 Aug 13 00:23, you wrote to Benny Pedersen:

is to prevent make install not overwriteing os files

in linux if i make with:

./configure
make
make install

then it should use /usr/local as MBSE_ROOT (prefixing)

/opt is for systems that does NOT use make install

Hmm, I was always taught that /opt was for the installation of
OPTional packages/software?

Totally agree with you and is the standard now for many packages that I have installed:

Adobe
F-Prot
LibreOffice
Calibre
VirtualBox

and mbse


Vince

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

Hello Vince!

10 Aug 2013 12:57, Vince Coen wrote to Robert Wolfe:

Hello Robert!

09 Aug 13 00:23, you wrote to Benny Pedersen:

is to prevent make install not overwriteing os files

in linux if i make with:

./configure
make
make install

then it should use /usr/local as MBSE_ROOT (prefixing)

/opt is for systems that does NOT use make install

Hmm, I was always taught that /opt was for the installation of
OPTional packages/software?

Totally agree with you and is the standard now for many packages that
I have
installed:

Adobe
F-Prot
LibreOffice
Calibre
VirtualBox

and mbse

if mbse is precompiled non opensource its should install in /opt, if one compiles local it should stick to fhs with /usr/local prefixing, simple to break things if one wants

when i get around to do the gentoo ebuild it would be using fhs prefixing with /usr

i will for the last time say:

/opt : is for optical packages that is not installed via opensource that is compiled local
/usr/local : bsd default make, make install, did you see freebsd use /usr ? /usr : linux default native local compile prefixing


Regards Benny

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

--- Msged/LNX 6.2.0 (Linux/3.10.9-gentoo (i686))
* Origin: duggi.junc.org where qico is waiting (2:230/0)