Hello mark!

Sunday July 19 2015 11:04, you wrote to Sean Dennis:



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

They don't - that does supprise me - present in one form or another even on 
IBM
iron - but that does use HLQs.

 SD>> From the MBSE manual:

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

That like most of the html docs is very old (the docs have rarely been 
updated)
although I did try for my changes.


 SD>> It's done that way so the software will work correctly under
 SD>> every 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
 SD>> distribution, go right
 SD>>  ahead and do it.

SD - The offical distro before and since leaving Michael has not changed and a
param to the configure function will allow the change from /opt to /home
although I have not tested that for 1.0.5 - more further down.

 > 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...

That was my 1.0.4 which changed /opt to /home but still alowed an otherride 
via
configure param to go elsewhere.

 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
 SD>> just because of your ineptitude in INSTALLING IT.  I mean, if you
 SD>> can't even install the software right, perhaps you shouldn't be
 SD>> using it!

SD - changing the install location will not break mbse - MB allowed for that
via the configure routines.

 > 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
 SD>> want and not worry about it. :)

SD - Nope but changing the config allows you to do it pre compiling the 
package
as you can with many others under Linux.

 > 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
 SD>> soon). I won't support any patches I've made unless MBSE is
 SD>> installed correctly. After nearly 20 years of supporting
 SD>> Cheepware, I've come to the conclusion that a majority of sysops
 SD>> are lazy and don't bother reading the directions. In the MBSE
 SD>> manual, it says that all distros may not work with MBSE, but it
 SD>> seems people overlook that fact and claim MBSE is broken.

That is MB covering his arse. I would do the same if needed.
The root path for the package (mbse) is tied to one variable in both compile
scripts and likewise the install script.

The real problem is if you wish to go from one to the other e.g., from /opt to
/home in that you have to runs scripts on one type or another to change all of
the echo, file system paths that point to the individual echo's or file areas.

It was the one task that I had not automated mostly because of my eye sight 
but
also that I hadn't a clue of how to do it and still don't !!

For a fresh install though it is not a problem as as to why do it - that is
simple -- I run multiple boot environments on both the SSD drive as well as 
the
DASD. In the later case at one point around five or six and I did not want to
do a fresh mbse install for them all and yes I know that I could have used the
link command but that does cause some issues from root (/) and even more if
more than one boot partition is mounted which I can easily have.  That one
causes major problem even if only used for a few minutes.

Using /home on a common home partition clear all of the issues even to the
extent of using other drives (dasd or ssd's).

Yes I have a wee bit of experience with O/S's going back to CPM, MPM,
MS&IBM&PC Dos, Windows (from v2.0 it was a dog) OS/2, Unix, DEC 8/11, George
(ICL 1900), VME (series 29 & 39), Forgotten (IBM 1401, 7094), IBM 360, 370 and
later (MVS ! OS/390 ! Z/OS etc) working as a programmer, A/P, Project, Program
and Test Managers, since 1961 to recent - Now I only seem to do is Cobol
systems migration from one compiler to another in my so called retirement but
have to top up the pensions for the little extras in life.


Vince

--- Mageia Linux v4/Mbse v1.0.4/GoldED+/LNX 1.1.5-b20130910