I am doing a small update to the installation, nothing special of note really but I have a question:

Does anyone really see the need for Mystic to allow all of the paths to be configured upon initial installation? I was thinking of simplifying it so that the installation only asks for the root Mystic directory.

As I continue to build on Mystic more and more paths will be configurable, so its going to become overwhelming if I keep adding paths to the installation utility.

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 01/04/18, g00r00 pondered and said...

Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.

As I continue to build on Mystic more and more paths will be
configurable, so its going to become overwhelming if I keep adding paths to the installation utility.

I think on first thought it seems fine to do as you suggest. Another idea is that you might want to offer a separate menu option on the initial installer page that users could access to change any default paths so it separates
things out a bit... and make the 'Install Mystic BBS' more as you say, the user can just set the root Mystic directory from that screen then press F2 to install.

I also suggest you change the default Outbound Echomail path to use %system path%\echomail\out only and drop \fidonet as this may confuse some if they are not actually running fidonet from first install.

Best, Paul


`I'm not expendable, I'm not stupid, and I'm not going' - Kerr Avon, Blake's 7

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

I don't think many people change those. I don't

On 08:30 04/01 , g00r00 wrote:

I am doing a small update to the installation, nothing special of note really >but I have a question:

Does anyone really see the need for Mystic to allow all of the paths to be >configured upon initial installation? I was thinking of simplifying it so that
the installation only asks for the root Mystic directory.

As I continue to build on Mystic more and more paths will be configurable, so >its going to become overwhelming if I keep adding paths to the installation >utility.

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A38 2018/01/01 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

You should consider an upgrade option to.. somehow

On 03:38 05/01 , Avon wrote:

On 01/04/18, g00r00 pondered and said...

Does anyone really see the need for Mystic to allow all of the paths to be configured upon initial installation? I was thinking of simplifying it so that the installation only asks for the root Mystic directory.

As I continue to build on Mystic more and more paths will be configurable, so its going to become overwhelming if I keep adding paths to the installation utility.

I think on first thought it seems fine to do as you suggest. Another idea is >that you might want to offer a separate menu option on the initial installer >page that users could access to change any default paths so it separates >things out a bit... and make the 'Install Mystic BBS' more as you say, the >user can just set the root Mystic directory from that screen then press F2 to >install.

I also suggest you change the default Outbound Echomail path to use %system >path%\echomail\out only and drop \fidonet as this may confuse some if they are >not actually running fidonet from first install.

Best, Paul

`I'm not expendable, I'm not stupid, and I'm not going' - Kerr Avon, Blake's 7

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A38 2018/01/01 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

* An ongoing debate between g00r00 and All rages on ...

Does anyone really see the need for Mystic to allow all of the paths
to be configured upon initial installation? I was thinking of
simplifying it so that the installation only asks for the root Mystic directory.

I would like to see a small confirmation appear when changing the main directory (like to \mystic\install\) so I know the inserted data (\install) propagated everywhere else, otherwise no need that I can see. :-)


.- Keep the faith, --------------------------------------------------.
| |
| Ben aka cMech Web: http|ftp|binkp|telnet://cmech.dynip.com |
| Email: fido4cmech(at)lusfiber.net |
| Home page: http://cmech.dynip.com/homepage/ |
| | `-------- WildCat! BBS 24/7 +1-337-984-4794 any BAUD 8,N,1 -------'

... Wherever you go, there you are.
--- GoldED+/W32-MSVC v1.1.5-b20170303 + Mystic BBS v1.12 A37
* Origin: FSXNet - Positronium: telnet://cmech.dynip.com (21:2/117)

On 01/04/18, g00r00 said the following...

Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.

That's entirely sensible. Starting with defaults and reconfiguring later is probably what most users do anyway.

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Subcarrier BBS (21:2/140)

On 01/04/18, g00r00 said the following...

I am doing a small update to the installation, nothing special of note really but I have a question:
Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.

As I continue to build on Mystic more and more paths will be
configurable, so its going to become overwhelming if I keep adding paths to the installation utility.

yeah i think it's better if you show the one path since the tree would be the sub paths to the root..

|08 .|05ú|13ù|15Dr|07e|08am Ma|07st|15er|13ù|05ú|08.
|08 øù|05ú|13ùø |13øù|05ú|08ùø
|11 DoRE|03!|11ACiDiC|03!|11Demonic |08[|15dreamland|09.|15darktech|09.|15org|08]

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/64)
* Origin: |08--[|15!|07dreamland BBS dreamland.darktech.org (21:1/163)

On 01/04/18, g00r00 said the following...

I am doing a small update to the installation, nothing special of note really but I have a question:

Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.

As I continue to build on Mystic more and more paths will be
configurable, so its going to become overwhelming if I keep adding paths to the installation utility.

I only ever change the main bbs path in the install settings. So yeah, I
don't see a need to have to also change the other paths in the install program.

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Cyberia BBS | cyberia.darktech.org | San Jose, CA (21:1/120)

On 01/04/18, g00r00 said the following...

Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.

I know I only change the root location and or name. I've never changed the subdirectories. The question comes when you add themes there needs to be a system to it, but that could stay as it is.

--- Mystic BBS v1.12 A38 2018/01/01 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

On 01/04/18, g00r00 said the following...

Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.

In my opinion, just have the user set up the root directory for Mystic, and
let Mystic create the sub-directories as it needs. As long as they can be changed later, if needed, there shouldn't be a problem.

Keep up the great work! ;)


---

Black Panther
a.k.a. Dan Richter
Sysop - Castle Rock BBS (RCS)
The sparrows are flying again....

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

I also suggest you change the default Outbound Echomail path to use %system path%\echomail\out only and drop \fidonet as this may confuse
some if they are not actually running fidonet from first install.

Funny you mention that because I just changed the default last night in A39 to:

\root\echomail\out\primary\

So this will always work and provide a clean directory structure, because primary will always be the primary and then the rest will be the domain.zone.

So if FSX is the primary and FidoNet is added you might have:

\root\echomail\out\fidonet.001\
\root\echomail\out\fidonet.002\
\root\echomail\out\fidonet.003\
\root\echomail\out\primary\

--- Mystic BBS v1.12 A39 2018/01/04 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

I would like to see a small confirmation appear when changing the main directory (like to \mystic\install\) so I know the inserted data (\install) propagated everywhere else, otherwise no need that I can see. :-)

I'm sorry, I'm not quite sure I am following you here so instead I'll paint a picture of what I had in mind: The new installation would probably look something like this:

Root Path | c:\mystic\
BBS Name | New Mystic BBS
BBS Location | Somewhere, USA
Sysop Handle | Sysop
Real Name | Sysop
E-mail |

[F2] Begin Installation [ESC] Abort

It would then create your Sysop account as well, and configure the BBS name, location, and Sysop name.

--- Mystic BBS v1.12 A39 2018/01/04 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 01/04/18, g00r00 said the following...

I am doing a small update to the installation, nothing special of note really but I have a question:

Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.

As I continue to build on Mystic more and more paths will be
configurable, so its going to become overwhelming if I keep adding paths to the installation utility.

Keep the install simple, I agree with just having the location of the mystic folder vs having to file crazy number of paths. :)

Cheers!
Pequito

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Twinkle BBS # (21:1/126)

* An ongoing debate between g00r00 and Cmech rages on ...

I would like to see a small confirmation appear when changing the
main directory (like to \mystic\install\) so I know the inserted
data (\install) propagated everywhere else, otherwise no need
that I can see.
:-)

I'm sorry, I'm not quite sure I am following you here so instead I'll paint a picture of what I had in mind: The new installation would probably look something like this:

Root Path | c:\mystic\
BBS Name | New Mystic BBS
BBS Location | Somewhere, USA
Sysop Handle | Sysop
Real Name | Sysop
E-mail |

[F2] Begin Installation [ESC] Abort

It would then create your Sysop account as well, and configure the BBS name, location, and Sysop name.

Looks great so far, and for the very 1st install it would work perfect that I can see, but on subsequent installs/upgrades the very 1st thing I do is change the Root Path to c:\mystic\install\

Currently when I do this then advance to the 2nd path entry the \install\ addon

propagates to every path so I can see it "worked". Your new format would not indicate these changes (assumption time). I would like to see a short message to the right of the Root Path data indicating the propagation took place. Not a

deal breaker, just a nice confirmation :-)


.- Keep the faith, --------------------------------------------------.
| |
| Ben aka cMech Web: http|ftp|binkp|telnet://cmech.dynip.com |
| Email: fido4cmech(at)lusfiber.net |
| Home page: http://cmech.dynip.com/homepage/ |
| | `-------- WildCat! BBS 24/7 +1-337-984-4794 any BAUD 8,N,1 -------'

... I'm sorry, that line is busy till Monday. Would you hold please?
--- GoldED+/W32-MSVC v1.1.5-b20170303 + Mystic BBS v1.12 A37
* Origin: FSXNet - Positronium: telnet://cmech.dynip.com (21:2/117)

On 01/04/18, g00r00 pondered and said...

Funny you mention that because I just changed the default last night in A39 to:

\root\echomail\out\primary\

Spooky stuff :) Thanks!

Best, Paul


`I'm not expendable, I'm not stupid, and I'm not going' - Kerr Avon, Blake's 7

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 01/04/18, g00r00 pondered and said...

It would then create your Sysop account as well, and configure the BBS name, location, and Sysop name.

Nice +1 here

Best, Paul


`I'm not expendable, I'm not stupid, and I'm not going' - Kerr Avon, Blake's 7

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 01/04/18, g00r00 considered the following...

Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.

Maybe include it in the upgrade script. If it's not there.... it will be, if its not.... there ya go. :-)

Mick

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Central Ontario Remote (21:1/156)

Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.

I don't think it's totally necessary. Things like files and doors are good to have in their own discrete locations (not within /mystic/) for the purposes
of simplifying bbs data/message backups, but a barebones vanilla installation doesn't provision any of that, so it's probably not super important.

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/32)
* Origin: lo fidelity bbs (21:2/142)

g00r00 wrote to All <=-

I am doing a small update to the installation, nothing special of note really but I have a question:

Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.

I only ever change the root directory and let the others be the defaults, because I install each version to a temporary path, then use my scripts to backup the old version and copy the new binaries across.


... Does fuzzy logic tickle?
___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A36 2017/12/04 (Raspberry Pi/32)
* Origin: The Bridge - bridge.vkradio.com (21:1/143)

Avon wrote to g00r00 <=-

I also suggest you change the default Outbound Echomail path to use %system path%\echomail\out only and drop \fidonet as this may confuse
some if they are not actually running fidonet from first install.

On my SBBS system I use outbound/ for the default. That's my default, though I'm flexible. Moot point now, since I now have only established systems.


... A pnp transistor will be an npn.
___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A36 2017/12/04 (Raspberry Pi/32)
* Origin: The Bridge - bridge.vkradio.com (21:1/143)

g00r00 wrote to Avon <=-

I also suggest you change the default Outbound Echomail path to use %system path%\echomail\out only and drop \fidonet as this may confuse
some if they are not actually running fidonet from first install.

Funny you mention that because I just changed the default last night in A39 to:

\root\echomail\out\primary\

Good idea. :)


... ALWAYS tell the truth - Unless something better is handy.
___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A36 2017/12/04 (Raspberry Pi/32)
* Origin: The Bridge - bridge.vkradio.com (21:1/143)

g00r00 wrote to Cmech <=-

It would then create your Sysop account as well, and configure the BBS name, location, and Sysop name.

That will be a pain for those of us upgrading. All I need to specify is the root path. The other information should be separate, since only new sysops need it. Remember that installing a new copy of Mystic is also the first step to upgrading.


... Archaeologist: A person whose career lies in ruins.
___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A36 2017/12/04 (Raspberry Pi/32)
* Origin: The Bridge - bridge.vkradio.com (21:1/143)

On 01/05/18, Tony Langdon pondered and said...

It would then create your Sysop account as well, and configure the BB name, location, and Sysop name.

That will be a pain for those of us upgrading. All I need to specify is the root path. The other information should be separate, since only new sysops need it. Remember that installing a new copy of Mystic is also
the first step to upgrading.

Perhaps there could be some switches added to the installer that allow you to pass the key fields via command line? That could speed things up if you're trying to automate a fresh install and copying files across from it. Just a thought?

Best, Paul


`I'm not expendable, I'm not stupid, and I'm not going' - Kerr Avon, Blake's 7

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

That will be a pain for those of us upgrading. All I need to specify is the root path. The other information should be separate, since only new sysops need it. Remember that installing a new copy of Mystic is also
the first step to upgrading.

It will be the identical number of keypresses as it is now, you change the path and press F2.

--- Mystic BBS v1.12 A39 2018/01/04 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Avon wrote to vk3jed <=-

Perhaps there could be some switches added to the installer that allow
you to pass the key fields via command line? That could speed things up
if you're trying to automate a fresh install and copying files across from it. Just a thought?

To be honest, all I care about is the root directory, because all I'm going to do with a new installation is copy out the binaries and maybe a couple of other files. The rest, if needed, should be configured through an "initial configuration script", in my opinion.

How would this work?

Install Mystic - installer asks for the root directory for installation. And away you go.

In the newly installed Mystic, if you need to, run "mystic-setup in the root directory". Here it asks for the BBS details (sysop name, BBS name, location, etc), and makes it ready for use.


... A life? Where can I download that?
___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A36 2017/12/04 (Raspberry Pi/32)
* Origin: The Bridge - bridge.vkradio.com (21:1/143)

On 01/05/18, Tony Langdon said the following...

That will be a pain for those of us upgrading. All I need to specify is the root path.

I'd imagine everything would have defaults and you wouldn't have to change anything beyond the root path for an upgrade install like you already do.

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Subcarrier BBS (21:2/140)

On 01/04/18, g00r00 said the following...

Funny you mention that because I just changed the default last night in A39 to:

\root\echomail\out\primary\

If you really wanted to get anal about it, you could probably drop the subdirectories of the /out/ subdirectory altogether and go with the defaults most other mailers do:

\root\echomail\outbound (primary)

Then obviously all the other directories would be in ..\echomail as well, rather than another subdirectory. May lead to less confusion. *shrug*

Regards,
Nick

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

I think just the root path is fine.
Ray

National Incident Alerts
telnet://niabbs.com
www.nationalincidentalerts.com

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: NIA BBS (21:2/108)

\root\echomail\outbound (primary)

Then obviously all the other directories would be in ..\echomail as well, rather than another subdirectory. May lead to less confusion. *shrug*

I don't like that as a default. I tried it in the very beginning but it leaves us cluttered by the stupid way BSO works:

c:\mystic\out
c:\mystic\fsxnet.021
c:\mystic\agoranet.046

^^ Whats the point of having an OUT directory if the directories used aren't within the out directory! I hate that BSO works that way, and I can't imagine why they did it the way they did.

Anyway having primary isn't the best solution but it keeps it all under the same bucket which I like (and is much better than fidonet lol)

c:\mystic\out\primary
c:\mystic\out\fsxnet.021
c:\mystic\out\agoranet.046

Of course its completely configurable so if someone doesn't like my defaults they can change it. For now I am going to try out primary in the next alpha as a default.

--- Mystic BBS v1.12 A39 2018/01/05 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 01/05/18, g00r00 said the following...

^^ Whats the point of having an OUT directory if the directories used aren't within the out directory! I hate that BSO works that way, and I can't imagine why they did it the way they did.

Because the "out" or "outbound" directory *IS* the primary outbound
directory. Seems to me they went with the KISS method (ie: naming primary outbound "outbound").

Although this may have been adopted back when 4D BSO was the 'thing' and 5D wasn't quite there yet, and they just kept the defaults for 4D and
incorporated the new stuff.

Anyway having primary isn't the best solution but it keeps it all under the same bucket which I like (and is much better than fidonet lol)

c:\mystic\out\primary
c:\mystic\out\fsxnet.021
c:\mystic\out\agoranet.046

I agree. Much better than "fidonet". But "primary" is just as much a solution as "outbound" is all I was getting at. Naming it anything other than what the actual network is, is redundancy. I believe what was originally intended for 5D BSO is whatever network you setup as your "main" aka would not have a hex extention after it. For example:

[ fsxnet primary ]

\mystic\echomail\out\fsxnet
\mystic\echomail\out\agoranet.02e
\mystic\echomail\out\fidonet.001

[ fidonet primary ]

\mystic\echomail\out\fidonet
\mystic\echomail\out\agoranet.02e
\mystic\echomail\out\fsxnet.021

[ agoranet primary ]

\mystic\echomail\out\agoranet
\mystic\echomail\out\fidonet.001
\mystic\echomail\out\fsxnet.021

So in that case, the default starting directory would be \mystic\echomail\out (is 'out' even needed?) and nothing further until you setup your primary network. That would not have an extension, and the rest would.

Of course its completely configurable so if someone doesn't like my defaults they can change it. For now I am going to try out primary in
the next alpha as a default.

However you see fit, mah dude!

Regards,
Nick

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

g00r00 wrote to vk3jed <=-

It will be the identical number of keypresses as it is now, you change
the path and press F2.

No probs, so those other ones just go to default values then.


... If you don't go to other people's funerals, they won't come to yours.
___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A36 2017/12/04 (Raspberry Pi/32)
* Origin: The Bridge - bridge.vkradio.com (21:1/143)

Static wrote to vk3jed <=-

On 01/05/18, Tony Langdon said the following...

That will be a pain for those of us upgrading. All I need to specify is the root path.

I'd imagine everything would have defaults and you wouldn't have to
change anything beyond the root path for an upgrade install like you already do.

Works for me. :)


... You cannot be too careful in the choice of your enemies.
___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A36 2017/12/04 (Raspberry Pi/32)
* Origin: The Bridge - bridge.vkradio.com (21:1/143)

g00r00 wrote to Accession <=-

\root\echomail\outbound (primary)

Then obviously all the other directories would be in ..\echomail as well, rather than another subdirectory. May lead to less confusion. *shrug*

I don't like that as a default. I tried it in the very beginning but
it leaves us cluttered by the stupid way BSO works:

I see where you're coming from. I've seen this myself when enabling 5D support on my SBBS system. :)


... We are operating on many levels here.
___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A36 2017/12/04 (Raspberry Pi/32)
* Origin: The Bridge - bridge.vkradio.com (21:1/143)

Hello g00r00!

Anyway having primary isn't the best solution but it keeps it all
under the same bucket which I like (and is much better than fidonet
lol)

c:\mystic\out\primary
c:\mystic\out\fsxnet.021
c:\mystic\out\agoranet.046

I like the "Primary" idea as it keeps all the BSO directory confusion in a
more localized directory


Jeff


--- GoldED+/LNX 1.1.5-b20170303 / Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: The Ouijaboard II - Anoka, MN (21:1/128)

So in that case, the default starting directory would be \mystic\echomail\out (is 'out' even needed?) and nothing further until
you setup your primary network. That would not have an extension, and
the rest would.

This is how Mystic 2 works. It just appends the domain name of whatever your primary address is to the configured "outbound" directory. In Mystic 1, its up to you to decide whatever that should be (in the default case its now "primary")

Unfortunately I don't think I can make that change in Mystic 1 because it will confuse the shit out of people lol

--- Mystic BBS v1.12 A39 2018/01/06 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 01/06/18, g00r00 said the following...

Unfortunately I don't think I can make that change in Mystic 1 because
it will confuse the shit out of people lol

You haven't "officially" made any changes yet, including the "primary" thing you had discussed the past couple days. ;)

Most people don't understand 5D BSO anyways, since most tossers from
yesteryear never supported it.

Regards,
Nick

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

You haven't "officially" made any changes yet, including the "primary" thing you had discussed the past couple days. ;)

Yeah I've been sitting on the first A39 pre-alpha for a bit in case I think
of some more changes I want to do with the record formats, so no one has seen it but the default is primary in A39.

Most people don't understand 5D BSO anyways, since most tossers from yesteryear never supported it.

I agree. This is part of the reason I want to make a outbound packet viewer
so people have a view into what is going on without having to understand that stuff.

--- Mystic BBS v1.12 A39 2018/01/08 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 01/08/18, g00r00 said the following...

Yeah I've been sitting on the first A39 pre-alpha for a bit in case I think of some more changes I want to do with the record formats, so no
one has seen it but the default is primary in A39.

No worries. I don't run default, so it really doesn't matter whether I care
for it or not. ;)

I agree. This is part of the reason I want to make a outbound packet viewer so people have a view into what is going on without having to understand that stuff.

Stop that! You're making it entirely too easy. lol

Regards,
Nick

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

On 01/04/18, g00r00 said the following...

I am doing a small update to the installation, nothing special of note really but I have a question:

Does anyone really see the need for Mystic to allow all of the paths to
be configured upon initial installation? I was thinking of simplifying
it so that the installation only asks for the root Mystic directory.

I don't. Every time I do a Mystic installation, what matters is the main Mystic directory. What comes along doesn't matter much.

----
Regards from Nighthawk - AKA Flavio Bessa
Sysop of Saturn's Orbit BBS - Rio de Janeiro, Brazil
fcbessa@gmail.com - saturnsorbit.hopto.org

--- Mystic BBS v1.12 A38 2018/01/01 (macOS/64)
* Origin: Chiron, orbiting Saturn - Brazil (21:1/146.1)