export HOME=/home/user

Precisely.

OK, so that is not the problem. That line is in the script that calls mis
and I still get the "/root/.dosemu" errors. Very frustrating because this is actually my second choice at a solution.

I have my DOS BBS software running on a separate machine under OS/2 using VMODEM to accept telnet calls. The mystic matrix menu is set up to telnet to that system, as well as to telnet to the local system (on Port 26) to call Synchronet. That works, but I would really like to get everything running
on the debian box.

So, a long time back I set up xinetd and telnetd to call a bbs script that would load dosemu on port 27 on the debian box. I can telnet to:

localhost 27

using telnet or syncterm, and telnetd will call the bbs script, loading
dosemu and the bbs. However, although mystic will telnet to the other
box, and will call up synchronet on port 26 on the same box, I cannot get the bbs script to fire if I telnet from mystic. Something causes telnetd to not call the script, and I get no error messages. I get a "connected" and that
is that.

So, I was trying to set the BBS to be called up from the matrix menu as if it was a DOS door. Since mystic is refusing to use /home/user/.dosemu, that is turning out to be a futile effort also.

However, something you said got me thinking of a *third* way... having the mystic matrix call telnetd's bbs script directly, instead of using telnet or calling it as a door.

THAT seems to work! :o

It does leave me with one other cosmetic issue, which I will address in a separate message. :)

Thanks!
Mike

---
þ SLMR 2.1a þ "Mmmmmmmm.....pie pants."


--- GTMail 1.26
* Origin: CCO BBS * 502/875-8938 * capcity2.synchro.net (21:1/175.0)

Mike Powell wrote to Vk3jed <=-

@MSGID: <581544AA.1101.fsx_mys@freeway.apana.org.au>

export HOME=/home/user

Precisely.

OK, so that is not the problem. That line is in the script that calls
mis and I still get the "/root/.dosemu" errors. Very frustrating
because this is actually my second choice at a solution.

I have my DOS BBS software running on a separate machine under OS/2
using VMODEM to accept telnet calls. The mystic matrix menu is set up
to telnet to that system, as well as to telnet to the local system (on Port 26) to call Synchronet. That works, but I would really like to
get everything running on the debian box.

Hmm, OK, now I'm confuused, because you've got a complex system, but no real information on _where_ DOSemu is actually being called from (a slightly important detail ;) ). Because if DOSemu is not running on the same box as Mystic, then tweaking the environment variables before calling mis will definitely not work. :)

So, a long time back I set up xinetd and telnetd to call a bbs script
that would load dosemu on port 27 on the debian box. I can telnet to:

localhost 27

using telnet or syncterm, and telnetd will call the bbs script, loading dosemu and the bbs. However, although mystic will telnet to the other box, and will call up synchronet on port 26 on the same box, I cannot
get the bbs script to fire if I telnet from mystic. Something causes telnetd to not call the script, and I get no error messages. I get a "connected" and that is that.

So, I was trying to set the BBS to be called up from the matrix menu as
if it was a DOS door. Since mystic is refusing to use
/home/user/.dosemu, that is turning out to be a futile effort also.

Ahh, this I see.

However, something you said got me thinking of a *third* way... having
the mystic matrix call telnetd's bbs script directly, instead of using telnet or calling it as a door.

THAT seems to work! :o

A possible solution? :)

It does leave me with one other cosmetic issue, which I will address in
a separate message. :)

OK. ;)



... Gone crazy, be back later, please leave message.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)