19 Jul 15 00:05, you wrote to me:

 ml>> i do that with /home as a matter of principle... especially since i
 ml>> don't want to break an user's private installs and such ;)

 SD> I've installed MBSE four times under four different distros and NOT
 SD> ONCE did I have a problem installing it to /opt.

i haven't said there was a problem installing to /opt... i said that i
normally have my /home as a separate drive/partition so that i can more
easily save users' home directories with their private installs as so many
packages seem to do if one doesn't have root access... eg: one system has
no less then four separate complete repositories and installations of FPC
and Lazarus, one for each of the four users using them... a system-wide
installation fails when one has to rebuild the compiler's or lazarus'
sources for a new version... individual installations allow for such with
no need to bother the BOfH...

 SD> So you're willing to install a publicly accessable server into your
 SD> home directory?  Do you leave your home unlocked when you leave?
 SD> That's just asking for problems.  MBSE is a system install, not a
 SD> private user install, and it's set up that way...

i didn't say it would be installed in my or any other user's home
directory... it would have its own home directory the same way that sbbs
has its own on another machine...

 SD> Not only that, but /home is actually an optional directory and not all
 SD> systems even use /home.

i'm not using any other systems ;)

 SD> From the MBSE manual:

 SD> "MBSE BBS is default installed in /opt/mbse. It should be possible to
 SD> install the bbs in a different location but this is not supported.
 SD> Many have tried, and and only a few have succeeded. See Filesystem
 SD> Hierarchy Standard for more info."

 SD> It's done that way so the software will work correctly under every
 SD> install, that's why.  You should realize this.

that's all fine and good but it is not really how i would like to install it...

[trim]

 SD> So if you want to go breaking MBSE from its official distribution, go right
 SD>  ahead and do it.

whoa... there was a release that did install to /home... that change was
reverted in the repo but the change to /home was still done to start with
and it was done for a good reason...

 SD> I didn't have any problem following directions, but just because
 SD> others do, that doesn't mean you can go around breaking software just
 SD> because of your ineptitude in INSTALLING IT.  I mean, if you can't
 SD> even install the software right, perhaps you shouldn't be using it!

my deity, man... what are you frustrated about and why are you taking this out on me?

 SD> This isn't Windows where you can stick a program wherever you want and
 SD> not worry about it. :)

no shit... we have only one winwhatever system around here any more...
that's one laptop that hasn't seen any real use since december... it was
only being used due to a dead workstation but since that workstation has
been replaced with yet another *nix system, that laptop is no longer used
and sits in the corner running dnet, mystic, taurus and dbridge... those
last three being a full node and two points...

 SD> I've several patches I'm going to be giving Andrew (hopefully soon). I
 SD> won't support any patches I've made unless MBSE is installed
 SD> correctly. After nearly 20 years of supporting Cheepware, I've come to
 SD> the conclusion that a majority of sysops are lazy and don't bother
 SD> reading the directions. In the MBSE manual, it says that all distros
 SD> may not work with MBSE, but it seems people overlook that fact and
 SD> claim MBSE is broken.

whatever...

)\/(ark

... ... And a partridge in a pear tree.
---