1 - In the docs regarding dosemu, can you add a bit about preferring to use a 32 bit kernel? 16 bit dpmi support is removed in recent 64 bit kernels, and a lot of doors either won't work or won't work fully as expected in 64 bit recent kernels.
2 - Can we add a -quiet to the default dosemu command, before the -I
3 - I can't use 'mis' system events to run the default commands you have listed for mail tossing. I have to script them and make my default run command something like 'sh /mystic/whateverScript.sh' and in that script,
2 - Can we add a -quiet to the default dosemu command, before the -I
Default dosemu command?
3 - I can't use 'mis' system events to run the default commands you h listed for mail tossing. I have to script them and make my default ru command something like 'sh /mystic/whateverScript.sh' and in that scr
It works fine here executing from the current directory. eg:
./mutil importmail.ini
Hey g00r00,
Running 112a36 for linux (32 bit, but noticed same with 64 bit) there
are some things I'd like to mention -
1 - In the docs regarding dosemu, can you add a bit about preferring to use a 32 bit kernel? 16 bit dpmi support is removed in recent 64 bit kernels, and a lot of doors either won't work or won't work fully as expected in 64 bit recent kernels.
2 - Can we add a -quiet to the default dosemu command, before the -I virtual part? Also, at the end of the line, if we do 2>/dev/null
/dev/null >/dev/null results in the best user experience - no dosemu output other than the game, no "press enter to continue" prompt from dosemu or anything.
3 - I can't use 'mis' system events to run the default commands you have listed for mail tossing. I have to script them and make my default run command something like 'sh /mystic/whateverScript.sh' and in that script, switch to the mystic directory. It won't run the mutil blah|fido blah commands in there by default. It also won't run them if I put /mystic/
in my $PATH.
4 - When creating new message bases, configuring them to be echomail bases, assigning my local address, and then assigning a node for export, the export node doesn't save a lot of the time. I have to go back and re-check a couple times to get the export node to 'stick'. I'm not sure
if this crops up repeatedly over time or if it works after configuring right the first time...but some exports don't go out for me and this was why :(
Thanks! Otherwise it's great!
--- Mystic BBS v1.12 A36 2017/12/03 (Linux/32)
* Origin: lo fidelity bbs (21:2/142)
Your event in mis is defined as ./mutil importmail.ini ? Or you can just type that from the command line? Because my issue is with the former - running it via the event service (i.e., on semaphore detection) isn't resulting in the binary actually being run. I have to abstract it into a bash script and run it in the event service as 'sh /mystic/whateverscript.sh'. This isn't the end of the world, but it's
1) Something we should probably also document somewhere? and
2) Something g00r00 may not be explicitly tracking which he may want to fix
Yeah, sorry. The command recommended in the docs we ship with Mystic.
Your event in mis is defined as ./mutil importmail.ini ? Or you can just
Gonna be honest I am running x64 Debian and have not come into any door that I can not run long as it is not 32bit. Also the docs included
where user submitted and not meant to be a bible of how it should be
done but more a guide line for those who are starting out. :)
You must be semi new to linux, there are several commands you can do one of them is -t when running from mystic. Also make sure this is set properly, I made this change in the rc.local file so it does it on boot.
sysctl -w vm.mmap_min_addr="0"
In the events you can do ./mutil import.ini as it should show you when installed, this just means it runs from the mystic folder where ever you did install it. You might want to check your permissions, is /mystic set root:root or your user:user account? This is important due to mystic
when it drops to a door it runs it at the level of the mystic folder permissions.
How are you creating the bases, this is very vague. Are you using the mutil to import the bases into mystic or manually inserting each base,
the second would be painful seeing how many bases you would be adding
for an echomail network.
Sounds like its taking more effort then it should but I hope to have answered some of the questions you had here, feel free to scribble back with any concerns.
With that said, you have to run events with the full path to the binary, ie:
/home/bbs/mystic/mutil importmail.ini
And I do believe that is documented somewhere already (whatsnew.txt I'm guessing).
Yeah, sorry. The command recommended in the docs we ship with Mystic.
Ah. "command > /dev/null 2>&1" is a little more terse way to merge
stdout and stderr together and dump both right into the bitbucket,
Your event in mis is defined as ./mutil importmail.ini ? Or you can j
The event is defined this way. I didn't put the mystic directory into the path or anything like that so it didn't even occur to me to try it any other way. I don't know if MIS even preserves the variable for shells it spawns once it's daemonized.
files point to the right places. Did I miss something in the
documentation which references setting an environment variable to point
to the mystic directory?
files point to the right places. Did I miss something in the documentation which references setting an environment variable to poi to the mystic directory?
If you've put mystic into your path, are you invoking MIS itself from outside the mystic directory? If it can't even find its data directory
it sounds like it's trying to use the wrong working directory entirely.
Accession wrote to esc <=-
I'm guessing you don't have your Mystic directory setup in your PATH
(it's fine, neither do I)..
With that said, you have to run events with the full path to the
binary, ie:
/home/bbs/mystic/mutil importmail.ini
Gonna be honest I am running x64 Debian and have not come into any do that I can not run long as it is not 32bit. Also the docs included where user submitted and not meant to be a bible of how it should be done but more a guide line for those who are starting out. :)
What kernel are you running? 4.8(or so) disables DPMI and sort of
disables 16 bit compatibility on 64 bit kernels, rendering things like Tradewars 2002 and pkunzip completely unusable.
You must be semi new to linux, there are several commands you can do of them is -t when running from mystic. Also make sure this is set properly, I made this change in the rc.local file so it does it on bo
sysctl -w vm.mmap_min_addr="0"
I have this set. I also am not using ubuntu, so rc.local isn't really a thing - debian is all systemd. For what it's worth, I am far from new to linux. :) At the end of the day, the vm.mmap_min_addr has been set on my server, in spite of rc.local not being a thing - this won't make a difference with newer 64 bit kernels, unfortunately.
In the events you can do ./mutil import.ini as it should show you whe installed, this just means it runs from the mystic folder where ever did install it. You might want to check your permissions, is /mystic root:root or your user:user account? This is important due to mystic when it drops to a door it runs it at the level of the mystic folder permissions.
No offense, but not at all what I was referring to. I can run it
manually via a cli from within the bbs directory just fine. I was just commenting that the default 'mis' event to run 'mutil' and 'fidopoll' doesn't work. If adding a ./ to the beginning makes it work, fantastic;
we should probably document that somewhere.
How are you creating the bases, this is very vague. Are you using th mutil to import the bases into mystic or manually inserting each base the second would be painful seeing how many bases you would be adding for an echomail network.
Manual creation. I create my echomail node in the System config, create the HUB (with all instructions to reach it), create the message base in the Message Base Editor, and connect it to my node. I also add an export node. The export node doesn't 'stick' or 'save' much of the time, and I have to go re-add it to get messages to export.
Sounds like its taking more effort then it should but I hope to have answered some of the questions you had here, feel free to scribble ba with any concerns.
I appreciate the help, genuinely. That said, and while trying to not
sound like a jerk or ungrateful, rest assured I am pretty well versed in linux, permissions, running commands, and configuring things. :)
Not a problem, can try to keep up with the thread and see if can help further with the setup etc. Believe me took me a while to get things working even with experience with linux myself.
Odd all works for me, and no I wont use ubuntu again in this lifetime
they are OK and seem to be doing better again but wont risk a server on it.
Curious if you are using dosemu what does your dosemu.conf look like, a lot of the time its the main culprit as well, here is mine.
$_cpu = "80586"
$_hogthreshold = (10)
$_dpmi_base = (0x10000000)
$_external_char_set = "cp437"
$_internal_char_set = "cp437"
$_layout = "us"
$_com1 = "virtual"
With this the whole -I from the mystic unix install did not work well
for me so I created an ksh file to create and load the door/games. I
can share parts of this on request if it will help. =)
Possible, I do run an ksh script for this as well so it never overlaps with the busy or if it never finishes by the time the event starts
again. So I can agree doing it vis shell script is a better way. :)
I would check into the mutil and the ini file that comes with it, makes adding echomail nodes much easier and can do the export etc all in one step.
dosemu conf at this point, it's a kernel level issue. Presumably you're
on a 3.x kernel, right? My suspicion is once you upgrade to something current, some/many of your dos doors will break.
cd doors\tw2002D:\DOORS\TW2002>tedit
cd arcD:\ARC>pkzip
Well Debian Stretch is on 4.9, which I can confirm does the same thing every other 64bit kernel that recent does. You can give dosemu access to the lower 64k but there's no ldt16 interface and it bombs on DPMI calls with an exception 0e like usual.
Ah, k, gotcha. I just assumed what was bundled in a default installation would be sufficient. I keep neglecting to read the changelog, which is silly considering I'm using something that's an alpha.
For what it's worth, I _did_ add it to my path and attempt running it without the absolute file path, and it complained about not knowing
where to find the .ini file I referenced. When I explicitly added the absolute path to the .ini file, it complained about not knowing where to find the data directory (I may be slightly off on which directory, but some intrinsically important Mystic BBS directory). I think that for whatever reason for me it's necessary to write a script to cd into the mystic directory to run everything.
And that's it. I always use MIS in daemon mode, but I wouldn't think that should matter any.
Do you start your MIS daemon from the actual Mystic directory? Or do you have a systemd bootup thing made which may run it from outside the Mystic directory? If so, you may need to add your Mystic directory to your PATH. Although it seems like it's running if it lets you know it can't find
your .ini file..?
switch to the mystic directory. It won't run the mutil blah|fido blah commands in there by default. It also won't run them if I put /mystic/
in my $PATH.
4 - When creating new message bases, configuring them to be echomail bases, assigning my local address, and then assigning a node for export, the export node doesn't save a lot of the time. I have to go back and
I haven't done a data file format update in a long time to be able to
add in OS-specific event configurations like the archive and protocols have but that is something I might do.
4 - When creating new message bases, configuring them to be echomail bases, assigning my local address, and then assigning a node for expo the export node doesn't save a lot of the time. I have to go back and
I just did a few tests and they all worked, but I made a note of it and will try some more. If there is something you can reproduce every time that would be helpful. This is specifically when adding the export from the message base editor?
That said, I'm happy to make Mystic wiki edits or docs edits, is there a place to submit changes? How do I get a wiki account? :)
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 369 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 88:41:43 |
| Calls: | 7,896 |
| Calls today: | 2 |
| Files: | 12,968 |
| Messages: | 5,792,270 |