Hi Vince!

15 Mar 14 19:51, you wrote to Nicholas Boel:

12 Mar 14 18:46, you wrote to me:

I would like to reinstall mbse so that it installs to /home/mbse
and NOT /opt.

Was just curious what others have done ..

For the Debian packageing, I plan to patch to it to install to /usr/bin/mbsebbs, plus sym links as necessary. (the old package install to /opt/mbse.)

I put my proramming hat on and changed the code (v1.01.02) to use /home/mbse instead of /opt/mbse.

Have you made that public yet? If so, where?

Solves all of the problems, well it was once I ran mbfile in -f to
force new file indexes as they were pointing to the wrong place.

I am making some other mods to the code over the next few weeks
subject to what happens to the system and spare time, e.g, what other errors pop up.

I may not have a chance to work it myself as soon I as I would like, but I would be interested in seeing what you're working on...



Jame


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

Hello All!

Having been using mbse since the days of v0.33 I have until 2012 used one partition for the whole of the Linux system.

Since then I have used a boot partition (12GB or 20GB) containing /

and another partition of 500GB or 1TB to hold /home that is mounted to /

Ok so far?

Well maybe not.

Building a new system drive (3TB WD Red - no not recommended as only 5400 rpm, not that the paperwork says that!),

I created it as a GPT, installed Win 7 X64 with 1Tb, then three 20GB Linux boot
partitions, 4GB swap, 1TB home, 500Gb Win backup and the remainding unused.

Installed Mageia v4 to the first boot part. and Mageia v3 to the next.
This in itself has problems booting to Windows as I get a sector 0 error, however I transgress, Now installed mbse (onto the M v4 part) along with all the other s/w needed and again linked mbse to /home.

Now the problem: With the new drive mounted as well as the older drive I cleared out the old mbse directory having copied its contents to the new drive.

This resulted in both old and new drive having the mbse directory deleted.

Not good as I had no choice to revert back to an older drive with a 2 year old copy and currently still rebuilding the system.

I then went into the setup to change all of the paths to point to /home/mbse including all of the file groups & areas, ditto for the message base along with
everything else BUT not all moves as the logs and some other stuff cannot be moved using this approach, but the idea is to only have the programs etc on opt
therefore reducing the mbse storage requirements.


This brings me to the point:

I would like to reinstall mbse so that it installs to /home/mbse and NOT /opt.

This issue applies to anyone who wishes to use a boot partition and a seperate one for /home.

IS there a working solution to do this at the point of building the mbse system, e.g., ./configure&make&make install ?

I do not wish to have to do this again!

In any event my attempt of moving all the paths I can to /home/mbse does not fully work (see above as some paths at /opt/mbse are not changeable (var/log to
name but one).


A very tired,


Vince

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

Hello Vince,

On 12 Mar 14 13:18, Vince Coen wrote to All:

This brings me to the point:

I would like to reinstall mbse so that it installs to /home/mbse and
NOT /opt.

This issue applies to anyone who wishes to use a boot partition and a seperate one for /home.

IS there a working solution to do this at the point of building the
mbse system, e.g., ./configure&make&make install ?

No offense intended here, but.. aren't you the current developer? Shouldn't you
know if there is a solution to this in the configure/build/install phase?

(If you are not the current developer, but only keep it active, then I apologize for assuming you were something you are not)

I do not wish to have to do this again!

I would have to agree with you there. That doesn't sound like it was any fun at
all!

A very tired,

:)

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20130910
* Origin: Dark Sorrow | darksorrow.us (1:154/701)

Hello Nicholas!

12 Mar 14 18:46, you wrote to me:

I would like to reinstall mbse so that it installs to /home/mbse
and NOT /opt.

Was just curious what others have done ..

I put my proramming hat on and changed the code (v1.01.02) to use /home/mbse instead of /opt/mbse.

Solves all of the problems, well it was once I ran mbfile in -f to force new file indexes as they were pointing to the wrong place.

I am making some other mods to the code over the next few weeks subject to what
happens to the system and spare time, e.g, what other errors pop up.



Vince

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

Hello Vince,

On 15 Mar 14 19:51, Vince Coen wrote to Nicholas Boel:

I would like to reinstall mbse so that it installs to /home/mbse
and NOT /opt.

Was just curious what others have done ..

Ahh okay. I suppose some reassurance goes a long way in making sure a fix is necessary.

I put my proramming hat on and changed the code (v1.01.02) to use /home/mbse instead of /opt/mbse.

That could even be something that might be requested to be user configurable even. Who knows.

Solves all of the problems, well it was once I ran mbfile in -f to
force new file indexes as they were pointing to the wrong place.

I am making some other mods to the code over the next few weeks
subject to what happens to the system and spare time, e.g, what other errors pop up.

Cool. It's always good to see BBS package being worked on these days, as many have been left for good and many with no released source to continue with them.
:(

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20130910
* Origin: Dark Sorrow | darksorrow.us (1:154/701)

Hello RJ!

18 Mar 14 19:03, you wrote to me:

I put my proramming hat on and changed the code (v1.01.02) to use
/home/mbse instead of /opt/mbse.

Have you made that public yet? If so, where?

As an ex professional programmer I am still testing the update.

Solves all of the problems, well it was once I ran mbfile in -f
to force new file indexes as they were pointing to the wrong
place.

I am making some other mods to the code over the next few weeks
subject to what happens to the system and spare time, e.g, what
other errors pop up.

I may not have a chance to work it myself as soon I as I would
like, but I would be interested in seeing what you're working on...

I will advise through the echo if I do anything but so far have changed some of
the scripts to reflect the change of install directory as well as detailed notes in the Changelog file.

Have also updated ftscprod to the latest (016) as well (plus the .h/c codebase.

No doubt I will need to do more if I spot any more issues but after this w/e will rename the /opt/mbse directory to something else and see what breaks :)

This, is the Murphy testing technique and if that fails there is always sods!

Vince

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

Hi Vince!

18 Mar 14 19:03, you wrote to me:
No doubt I will need to do more if I spot any more issues but after this w/e will rename the /opt/mbse directory to something else and see what breaks :)

I have the debian package build patched to install to /usr/lib/mbsebbs and there's a lot of things that break...<g> There's quite a few places where the paths are hardcoded, which is it what I'll be working to when I can. I use the
git repo the SF project [1] (which I also figure to mirror to Github[2], although there the default branch is set to 'debian'). Once I have those patched, I'll try a package build and install again. I currently working against v1.01...



Jame
[1] http://sourceforge.net/p/mbsebbs/code/ci/debian/tree/debian/patches/ [2] https://github.com/ftnapps/mbsebbs

--- BBBS/Li6 v4.10 Dada-1
* Origin: BBBS Info at Rocasa (1:120/546)

Hello Rj!

31 Mar 14 13:53, you wrote to me:

18 Mar 14 19:03, you wrote to me:
No doubt I will need to do more if I spot any more issues but after
this w/e will rename the /opt/mbse directory to something else and
see what breaks :)

I have the debian package build patched to install to
/usr/lib/mbsebbs and there's a lot of things that break...<g> There's
quite a few places where the paths are hardcoded, which is it what
I'll be working to when I can. I use the git repo the SF project [1]
(which I also figure to mirror to Github[2], although there the
default branch is set to 'debian'). Once I have those patched, I'll
try a package build and install again. I currently working against
v1.01...

Hmm not so many as it is all created from the mbse_root setting but yes there is a few that is not adjusted in the make file. Even more so if you have it already running at /opt.

Your setting of usr/lib is no better and if anything worse if you are a user who splits the system in two elements, e.g., / for system with a partition of say 12 - 20 Gb and /home that is mounted to / as the second partition.

This allows /home to be placed on any version or distro without changing any user settings other than creating the user accounts tied to specific uid's etc.

As I run 3 - 4 as well as additional drives and now am installing a SSD I do not want mbse to be on the root/boot partition.

This also in the event of a major system failure I can remove the drive containing /home and plug it in to my laptop with the users pre installed and can run the system from there until I get the server box back up and running.

Belts and braces.

Vince

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

Hello Vince!

Saturday April 05 2014 13:56, Vince Coen wrote to Rj Clay:

Your setting of usr/lib is no better and if anything worse if you are
a user who splits the system in two elements, e.g., / for system with
a partition of say 12 - 20 Gb and /home that is mounted to / as the
second partition.

I partitioned my MBSE system with /opt as the second partition. That way MBSE isn't disturbed when I upgrade to a newer version of Slackware. As you say below, all I need to do is create user accounts on the new / partition with the
same uid's etc.

This allows /home to be placed on any version or distro without
changing any user settings other than creating the user accounts tied
to specific uid's etc.

As I run 3 - 4 as well as additional drives and now am installing a
SSD I do not want mbse to be on the root/boot partition.

Mine never has been. I've always setup /opt as a separate partition.

This also in the event of a major system failure I can remove the
drive containing /home and plug it in to my laptop with the users pre installed and can run the system from there until I get the server box back up and running.

With my setup, the complete BBS is on a separate partition. In your changes, are you still creating BBS user home directories under the MBSE_ROOT directory?
ie: $MBSE_ROOT/home/username When upgrading to 1.0.2, will we have to rename /opt/mbse to /home/mbsebbs and then create a symlink from /opt/mbse to /home/mbsebbs?

Andrew

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

Hello Andrew!

05 Apr 14 11:53, you wrote to me:

With my setup, the complete BBS is on a separate partition. In your changes, are you still creating BBS user home directories under the MBSE_ROOT directory? ie: $MBSE_ROOT/home/username When upgrading to
1.0.2, will we have to rename /opt/mbse to /home/mbsebbs and then
create a symlink from /opt/mbse to /home/mbsebbs?

Yes it is all the same the only difference is that the mbse directory is located /home instead of /opt.

If the previously installed scripts as well as any new ones still have the code
that sets up $MBSE_ROOT and exports it all will be fine.

Some manual changes are needed however if updating an existing system previously under /opt but nothing complicated.

I will have a go and producing a script that deals with that using a standard distro environment.

Stopping mbse.

Clearly the new system has to be created into a temp directory and the system compiled as per normal, then the existing /etc/passwd has to be changed for mbse, bbs and any bbs users to point to /home instead of /opt.


ditto changes to /etc/xinetd.d/mbsebbs to replace '/opt' to '/home'.

and some others.

but after that it is just a :
cd /home
sudo mv mbse build-mbse
sudo mv /opt/mbse /home

and restart mbse.

Above is by memory but I am creating notes of the changes and once that is complete I can start looking at a script to try and do most of the donkey work.


Vince

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