• TEMP directory changes?

    From g00r00@21:1/108 to All on Saturday, February 16, 2019 15:32:35
    Hey everyone, I am looking for options and feedback.

    I have wanted to change the "temp" directory structure for a long time now but I have not because a lot of people may have door configurations that need to be updated.

    For example: If you have a door with a command line that is the "old" way of doing things where you use the TEMP directory and %3 or %N to point to the
    path where the door files are then you'd need to change it:

    OLD: c:\doors\mydoor.exe c:\mystic\temp%3\door.sys
    NEW c:\doors\mydoor.exe %Pdoor.sys

    If you use an asshole design door like LORD where you have to set up the drop file path for each individual node within its configuration, then you'd need to update those as well. I only know of LORD that does this but there may be others.

    My question is: How many people would have a huge problem with me doing this change? I may not do it for a while or at all I just wanted to get a feeling of opinions.

    The reason for the change is for a couple of reasons:

    1. Its cleaner. Alongside these changes there will only be a single TEMP
    directory and all other directories will be included as a subdirectory:

    OLD: \mystic\temp1\ \mystic\temp2\ \mystic\tempmis\
    NEW: \mystic\temp\1\ \mystic\temp\2\ mystic\temp\mis\

    So you'd no longer have 23420 temp directories in c:\mystic just one.

    2, Option to put TEMP in a ram disk or other location for distributions that
    run on slow media. This will increase performance in some areas on those
    devices at the expense of needing memory for the RAM disk.

    --- Mystic BBS v1.12 A43 2019/02/15 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From Immortal@21:1/185 to g00r00 on Saturday, February 16, 2019 21:04:20
    On 16 Feb 2019, g00r00 said the following...

    Hey everyone, I am looking for options and feedback.

    I have wanted to change the "temp" directory structure for a long time
    now but I have not because a lot of people may have door configurations that need to be updated.

    For example: If you have a door with a command line that is the "old"
    way of doing things where you use the TEMP directory and %3 or %N to
    point to the path where the door files are then you'd need to change it:

    OLD: c:\doors\mydoor.exe c:\mystic\temp%3\door.sys
    NEW c:\doors\mydoor.exe %Pdoor.sys

    If you use an asshole design door like LORD where you have to set up the drop file path for each individual node within its configuration, then you'd need to update those as well. I only know of LORD that does this but there may be others.

    My question is: How many people would have a huge problem with me doing this change? I may not do it for a while or at all I just wanted to get
    a feeling of opinions.

    I say go ahead and change it if you'd like. I would have to go in and change
    a few things but its not really a big deal.

    Immortal

    --- Mystic BBS v1.12 A43 2019/02/10 (Linux/64)
    * Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)
  • From Avon@21:1/101 to g00r00 on Sunday, February 17, 2019 18:26:50
    On 16 Feb 2019 at 02:32p, g00r00 pondered and said...

    I have wanted to change the "temp" directory structure for a long time
    now but I have not because a lot of people may have door configurations that need to be updated.

    I think with respect to doors running them stand alone on a BBS is declining with the rise of the door servers many now use. I still run several as standalone on Agency and others using the same games do for the inter-bbs BRE for Zone 21... that said I agree it's time to move and standardise this to a single directory.

    1. Its cleaner. Alongside these changes there will only be a single TEMP
    directory and all other directories will be included as a
    subdirectory:

    OLD: \mystic\temp1\ \mystic\temp2\ \mystic\tempmis\
    NEW: \mystic\temp\1\ \mystic\temp\2\ mystic\temp\mis\

    So you'd no longer have 23420 temp directories in c:\mystic just
    one.

    I support this.

    2, Option to put TEMP in a ram disk or other location for distributions that run on slow media. This will increase performance in some areas on those devices at the expense of needing memory for the RAM disk.

    I personally wouldn't be using that.

    My question is: How many people would have a huge problem with me doing this change? I may not do it for a while or at all I just wanted to get
    a feeling of opinions.

    Yep suggest you do this and make it a fixed thing of any alphas for 1.13 once 1.12 is out.

    Better to let folks know that 1.12 respects the current state of play then
    make changes for 1.13

    Perhaps 1.13 can roll in some of the other standardised directories beeing mooted for Mystic 2.0 but please merge the concept into 1.0 rather than force us to pick up a whole new UI etc. that was in the 2.0 demo.

    better to move ideas across from 2.0 into the 1.0 branch IMHO :)

    Hope that helps.

    Best, Paul

    --- E:avon@bbs.nz ------ W:bbs.nz ---
    --- K:keybase.io/avon --------------

    --- Mystic BBS v1.12 A43 2019/02/15 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Vk3jed@21:1/109 to g00r00 on Sunday, February 17, 2019 18:12:00
    On 02-16-19 14:32, g00r00 wrote to All <=-

    Hey everyone, I am looking for options and feedback.

    I have wanted to change the "temp" directory structure for a long time
    now but I have not because a lot of people may have door configurations that need to be updated.

    I'm not running any legacy doors, so no issue for me.


    ... Error: Bad Or Missing Mouse Driver. Blame The Cat?? (Y/n)
    === MultiMail/Linux v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Vk3jed@21:1/109 to Avon on Sunday, February 17, 2019 18:14:00
    On 02-17-19 17:26, Avon wrote to g00r00 <=-

    2, Option to put TEMP in a ram disk or other location for distributions that run on slow media. This will increase performance in some areas on those devices at the expense of needing memory for the RAM disk.

    I personally wouldn't be using that.

    And I may consider doing that. One way to reduce SD card wear. :)


    ... If It's Bug Free, It's Time to Make Changes
    === MultiMail/Linux v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From MeaTLoTioN@21:1/158 to Avon on Sunday, February 17, 2019 12:14:47
    Hey Paul,

    On 17 Feb 2019, Avon said the following...

    On 16 Feb 2019 at 02:32p, g00r00 pondered and said...

    I have wanted to change the "temp" directory structure for a long tim now but I have not because a lot of people may have door configuratio that need to be updated.

    I think with respect to doors running them stand alone on a BBS is declining with the rise of the door servers many now use. I still run several as standalone on Agency and others using the same games do for
    the inter-bbs BRE for Zone 21... that said I agree it's time to move and standardise this to a single directory.

    1. Its cleaner. Alongside these changes there will only be a single
    directory and all other directories will be included as a subdirectory:

    OLD: \mystic\temp1\ \mystic\temp2\ \mystic\tempmis\
    NEW: \mystic\temp\1\ \mystic\temp\2\ mystic\temp\mis\

    So you'd no longer have 23420 temp directories in c:\mystic just one.

    I support this.


    Me too, this would be an excellent idea, along with the themes and other
    folder too that could be done this way.


    2, Option to put TEMP in a ram disk or other location for distributio that run on slow media. This will increase performance in some areas those devices at the expense of needing memory for the RAM disk.

    I personally wouldn't be using that.


    I don't think I would either but it's a neat and useful idea.


    My question is: How many people would have a huge problem with me doi this change? I may not do it for a while or at all I just wanted to a feeling of opinions.

    Yep suggest you do this and make it a fixed thing of any alphas for 1.13 once 1.12 is out.

    Better to let folks know that 1.12 respects the current state of play
    then make changes for 1.13

    Perhaps 1.13 can roll in some of the other standardised directories
    beeing mooted for Mystic 2.0 but please merge the concept into 1.0
    rather than force us to pick up a whole new UI etc. that was in the 2.0 demo.

    better to move ideas across from 2.0 into the 1.0 branch IMHO :)

    Hope that helps.

    Yep, totally agree with everything Avon says here... this would definitely be
    a good change. How difficult would it be to put some sort of parser in so the update would leave current systems as they are, and in the configuration
    there would be an option to "move" current structures to new structures and
    to do the folder moving and parse the relevant .mnu files and other files
    that would look for /mystic/tempX/ and change to /mystic/temp/X/ etc?

    |14Best regards,
    |11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

    |07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÄ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ

    --- Mystic BBS v1.12 A43 2019/02/10 (Linux/64)
    * Origin: The Quantum Wormhole, Ramsgate, UK. bbs.erb.pw (21:1/158)
  • From deon@21:2/116.1 to g00r00 on Sunday, February 17, 2019 14:08:04
    On 16 Feb 2019, g00r00 said the following...
    Hey everyone, I am looking for options and feedback.

    So I'm all for your proposed changes - but I dont run any doors on a Pi where those door problems would be an issue.

    To help those transition, could you have a "flag" that is set at install
    time, that toggles an installation either way.

    EG: Default new install, TEMP dirs as you propose, unless you tick "old TEMP path", which then uses the old way. You could also offer a "BOTH" option,
    that would be more work for mystic, but it would write the door stuff in the old and new locations, so that folks can transition over time.

    That would at least allow folks to transition to the new way - and you could introduce some "reminderware" to let folks know to update configs.

    ...deon

    _--_|\ | Deon George
    / \ | Chinwag BBS - A BBS on a PI in Docker!
    \_.__.*/ |
    V | Coming from the 'burbs of Melbourne, Australia

    --- Mystic BBS v1.12 A42 2018/12/27 (Raspberry Pi/32)
    * Origin: Chinwag | MysticBBS in Docker on a Pi! (21:2/116.1)
  • From g00r00@21:1/108 to MeaTLoTioN on Sunday, February 17, 2019 08:48:47
    Yep, totally agree with everything Avon says here... this would
    definitely be a good change. How difficult would it be to put some sort
    of parser in so the update would leave current systems as they are, and

    Assuming I understand what you're asking for, this will not be an option, sorry. :(

    The goal of these changes are to simplify the directory structure to make
    it easier to move Mystic to different drives and root directory names as well as to reduce the number of directories and configuration options.

    If I tried to build some old and new way thing it would take what is already too complex and make it more difficult to work with than it already is.

    --- Mystic BBS v1.12 A43 2019/02/15 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From MeaTLoTioN@21:1/158 to g00r00 on Sunday, February 17, 2019 17:36:48
    Assuming I understand what you're asking for, this will not be an option, sorry. :(

    The goal of these changes are to simplify the directory structure to make it easier to move Mystic to different drives and root directory names as well as to reduce the number of directories and configuration options.

    If I tried to build some old and new way thing it would take what is already too complex and make it more difficult to work with than it already is.

    That makes sense. I was thinking more on the upgrade process only, if the upgrade is from a bbs with the old structure, it would be able to parse all
    the data files and move the folders to their new location, updating the data files to replicate these new folder structure, but it answers my question. Probably a good idea to do it manually anyway to keep an eye on everything.

    Thanks for the info =)

    |14Best regards,
    |11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

    |07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÄ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ

    --- Mystic BBS v1.12 A43 2019/02/10 (Linux/64)
    * Origin: The Quantum Wormhole, Ramsgate, UK. bbs.erb.pw (21:1/158)
  • From Black Panther@21:1/186 to g00r00 on Sunday, February 17, 2019 19:47:14
    g00r00 wrote to All <=-

    My question is: How many people would have a huge problem with me doing this change? I may not do it for a while or at all I just wanted to
    get a feeling of opinions.

    I would not have a problem with this at all.

    The reason for the change is for a couple of reasons:

    1. Its cleaner. Alongside these changes there will only be a single
    TEMP
    directory and all other directories will be included as a
    subdirectory:

    OLD: \mystic\temp1\ \mystic\temp2\ \mystic\tempmis\
    NEW: \mystic\temp\1\ \mystic\temp\2\ mystic\temp\mis\

    So you'd no longer have 23420 temp directories in c:\mystic just
    one.

    It would be cleaner. If I did use the actual directory location in any door data lines, it would get me off my butt to get them fixed. :)



    ---

    Black Panther
    A.K.A. - Dan Richter
    Sysop - Castle Rock BBS
    telnet://bbs.castlerockbbs.com
    http://www.castlerockbbs.com
    The sparrows are flying again...


    ... "Junior, quit playing with your floppy!"

    ___ MultiMail/Linux v0.51

    --- Mystic BBS/QWK v1.12 A43 2019/02/08 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)
  • From Avon@21:1/101 to Black Panther on Monday, February 18, 2019 20:20:06
    On 17 Feb 2019 at 06:47p, Black Panther pondered and said...

    It would be cleaner. If I did use the actual directory location in any door data lines, it would get me off my butt to get them fixed. :)

    so in a way it's going to help you burn calories and become the man you want
    to be :)

    Best, Paul

    --- E:avon@bbs.nz ------ W:bbs.nz ---
    --- K:keybase.io/avon --------------

    --- Mystic BBS v1.12 A43 2019/02/15 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Black Panther@21:1/186 to Avon on Monday, February 18, 2019 18:35:53
    On 18 Feb 2019, Avon said the following...

    It would be cleaner. If I did use the actual directory location in an door data lines, it would get me off my butt to get them fixed. :)

    so in a way it's going to help you burn calories and become the man you want to be :)

    I think it'll take more than that to become the man I want to be... :)


    ---

    Black Panther(RCS)
    a.k.a. Dan Richter
    Sysop - Castle Rock BBS
    telnet://bbs.castlerockbbs.com
    http://www.castlerockbbs.com
    The sparrows are flying again....

    --- Mystic BBS v1.12 A43 2019/02/08 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)
  • From g00r00@21:1/120 to Gryphon on Sunday, March 10, 2019 07:41:18
    Such a change will break the original MRC python client. But I'm sure a coordinated rollout of an updated client would solve the issue.

    Also, I know that several of my MPL apps use the user's temp directory
    for stuff. I think I use the CfgTempPath variable. I assume that under the new plan, the variable will point to the proper directory, yes? If
    so, then I don't think that my apps will break because of it.

    Anything that uses CfgTempPath would be fine, as that would change to the new format. Using %P in your door configuration instead of "/tempath<node>" is both easier to do and will of course still work after the change.

    I am not going to change it just yet anyway. A44 is going to be one of this super big releases with tons of new things, the new theme system, more Python stuff, probably a new index reader for message bases, maybe some new theme stuff, etc. So changing the paths, I'll just hold off on that for a bit longer.

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)