@TZ: ffffc12c
! Fixed all known issues with MIS and STDIO redirection. DOSEMU works
great now, and is pretty easy to setup. Check the new section in the
Linux installation document for a tutorial on how to set up a DOS door
in DOSEMU with Mystic!

OK I give in. What linux installation document? I have checked the /docs directory and all be danged if it is there anywhere. Oddly, there IS a windows document. what I would want with that from a linux install package
I am not at all sure.

So where it is hidden?

Sorry if I come across a little testy. I found a real nice website the
other day that detailed adding a dos door with dosemu so of course now that
I want to see it I cannot find it again. :(

Mike
---
þ Synchronet þ CCO BBS * capcity2.synchro.net * 1-502-875-8938


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

OK I give in. What linux installation document? I have checked the
/docs directory and all be danged if it is there anywhere. Oddly, there IS a windows document. what I would want with that from a linux install package I am not at all sure.

You should have a "unix.install.txt" file in the folder after you unzip/unrar the download from the Mystic website.

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)

You should have a "unix.install.txt" file in the folder after you unzip/unrar the download from the Mystic website.

I did not extract the whole thing. :)

Following the directions in the document leads to a couple of other issue, however.

First off, version 1.12A31 is not offering me a 'DG' option. Only 'DD' and 'D3'.

Second, no matter which one of those I try, I get the following (paraphrased) errors:

cannot create /root/.dosemu/run
cannot open /root/.dosemu/boot.log for writing

I know I have to "sudo" to start mis, but why is it (still) trying to do
things as "root" once it is running? ps reports that the 'mis' and 'mystic' processes belong to the non-root BBS activity user, so I am failing to understand why it is trying to spawn dosemu as the root user or, at least, trying to create directories and logs in the /root directory.


Mike

---
þ SLMR 2.1a þ "Einstein? Who's he? Another troublemaker?" - H.Baines


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

On 10/26/16, Mike Powell said the following...

First off, version 1.12A31 is not offering me a 'DG' option. Only 'DD' and 'D3'.

I believe D3 produces all doorfiles at once now so there is no need to
specify a door.sys dropfile. I could be wrong though as I'm on a Pi and I
don't run DOS games locally.

cannot create /root/.dosemu/run
cannot open /root/.dosemu/boot.log for writing

Hopefully someone else can give you a hand with this. I took a different approach to installing Mystic by installing it in my home folder to avoid
using root at all.

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)

Following the directions in the document leads to a couple of other
issue, however.

First off, version 1.12A31 is not offering me a 'DG' option. Only 'DD' and 'D3'.

Yea the DG and other D* commands seem to have been all rolled into one 'DD' entry, so I guess Mystic creates all dropfile types at once so you dont have
to have a different doortype command for each door, much easier to setup the individual doors to supported droptype.. 'D3' is for Door32.sys and I believe only works on the Win32 version of Mystic (plain DOS mode cannot run 32bit doors)

Second, no matter which one of those I try, I get the following (paraphrased) errors:

cannot create /root/.dosemu/run
cannot open /root/.dosemu/boot.log for writing

Don't run MIS or MIS2 using sudo to set root.. run it as the actual root user by either logging in as root acct (if root is disabled you need to set a password to unlock the acct by tying sudo passwd root) or you need to change
to superuser by using the command: sudo su

Once MIS/MIS2 are running as the root user all will be happy and dosemu will
be able to access it's folders because it is being called from SUID0

I know I have to "sudo" to start mis, but why is it (still) trying to do things as "root" once it is running? ps reports that the 'mis' and 'mystic' processes belong to the non-root BBS activity user, so I am failing to understand why it is trying to spawn dosemu as the root user or, at least, trying to create directories and logs in the /root directory.

Here is another thing you can try.. first, login with the user account that
you use for the BBS, then start dosemu as THAT account so it will create it's folders in your $HOME/user/.dosemu folder .. I know I had problems with it in the past but I _DID_ get it to work, but unfortunatly now my BBS is running
on the Pi and dosemu is not supported by the ARM/v7+ processor.. hopefully
the devs wake up and realize that the Pi is a rising force in the microPC world.

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: internal dimension ÷ idbbs.dlinkddns.com ÷ port 59 (21:1/178)

³ MP> cannot create /root/.dosemu/run
³ MP> cannot open /root/.dosemu/boot.log for writing
³ MP>
³
³ Hopefully someone else can give you a hand with this. I took a different
³ approach to installing Mystic by installing it in my home folder to avoid
³ using root at all.

It is in my home folder also. I still have to start mis with "sudo ./mis"
but the owner of the process is the BBS user, and the files reside in that
user home folder.

Trying it as root would cause too many issues. :)

Mike

##Mmr 2.61á. !link ZR 10-27-16 07:37


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

On 10/27/16, Mike Powell said the following...

³ MP> cannot create /root/.dosemu/run
³ MP> cannot open /root/.dosemu/boot.log for writing
³ MP>
³
³ Hopefully someone else can give you a hand with this. I took a
different ³ approach to installing Mystic by installing it in my home folder to avoid ³ using root at all.

It is in my home folder also. I still have to start mis with "sudo
./mis" but the owner of the process is the BBS user, and the files
reside in that user home folder.

Trying it as root would cause too many issues. :)

You will need to do a chown to the folder above so like this.

sudo chown root:user /root -R

Replace the user with whatever your user account is on the machine, this will keep the folder secured under root but allow you permissions as well.

Let us know if you have any other questions!

Cheers!
Pequito

|08+- |10$s.s$s.s$ |08------------------------------------+
|08| |10$ý"$$$"ý$ |15tbbs.homeip.net |08|
|08| |10 .$$$. winkle |02BB|10S |07tbbs.homeip.net:8080 |08|
|08+--|10 .$$$$$. |08-------------------------------------+
|10 $ý"~"ý$ |07Christopher Malo |15aka |07Pequito!

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Twinkle BBS (21:1/126)

On 10/27/16, Night Stalker said the following...

Don't run MIS or MIS2 using sudo to set root.. run it as the actual root user by either logging in as root acct (if root is disabled you need to set a password to unlock the acct by tying sudo passwd root) or you need to change to superuser by using the command: sudo su

G00r00 designed it to run from sudo under the user, it should bind to the
port (<1000) then switch back to that user. If using a port above 1000 you shouldn't have to do that. Remember to set ownership:
sudo chown -R name:name /msytic

Here is another thing you can try.. first, login with the user account that you use for the BBS, then start dosemu as THAT account so it will create it's folders in your $HOME/user/.dosemu folder .. I know I had problems with it in the past but I _DID_ get it to work, but
unfortunatly now my BBS is running on the Pi and dosemu is not supported by the ARM/v7+ processor.. hopefully the devs wake up and realize that
the Pi is a rising force in the microPC world.

The ARM does have DOSBox and it works (very slow on early units like A & B). Though I think doorparty is the way to go with the Pi.

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

G00r00 designed it to run from sudo under the user, it should bind to the port (<1000) then switch back to that user. If using a port above 1000
you shouldn't have to do that. Remember to set ownership:
sudo chown -R name:name /msytic

Yea I'm aware of that, but it's 100% easier to have the BBS running as root because I don't know too many sysops that use a telnet port over 1000 .. it's just a matter of convenience for me to just have everything SUID0 to start it all from rc scripts at boot time.

The ARM does have DOSBox and it works (very slow on early units like A & B). Though I think doorparty is the way to go with the Pi.

I have the Pi 3 .. I wasn't even aware that dosbox was ported to any Linux .. I'm all over that like white on rice! I'll have a look see at it later today and see what I can come up with. I'll post results

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: internal dimension ÷ idbbs.dlinkddns.com ÷ port 59 (21:1/178)

On 10/28/16, Night Stalker said the following...

Yea I'm aware of that, but it's 100% easier to have the BBS running as root because I don't know too many sysops that use a telnet port over
1000 .. it's just a matter of convenience for me to just have everything SUID0 to start it all from rc scripts at boot time.

The BBS may be have to run as root, but the folder owner should be the user account, mystic when drops to load an app/door changes to who-ever owns the folder.

I have the Pi 3 .. I wasn't even aware that dosbox was ported to any
Linux .. I'm all over that like white on rice! I'll have a look see at
it later today and see what I can come up with. I'll post results

Guess this pends but there are other ways fro the Pi to run external doors as well that might run better on Pi vs DOSEMU and or DOSBOX since its an ARM.

Cheers!
Pequito

|08+- |10$s.s$s.s$ |08------------------------------------+
|08| |10$ý"$$$"ý$ |15tbbs.homeip.net |08|
|08| |10 .$$$. winkle |02BB|10S |07tbbs.homeip.net:8080 |08|
|08+--|10 .$$$$$. |08-------------------------------------+
|10 $ý"~"ý$ |07Christopher Malo |15aka |07Pequito!

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Twinkle BBS (21:1/126)

On 10/27/16, bcw142 pondered and said...

On 10/27/16, Night Stalker said the following...

Don't run MIS or MIS2 using sudo to set root.. run it as the actual r user by either logging in as root acct (if root is disabled you need set a password to unlock the acct by tying sudo passwd root) or you n to change to superuser by using the command: sudo su

G00r00 designed it to run from sudo under the user, it should bind to the port (<1000) then switch back to that user. If using a port above 1000
you shouldn't have to do that. Remember to set ownership:
sudo chown -R name:name /msytic

I agree with this.

From unix.install

[snip]

When running in Linux/OSX keep in mind that by default the
operating system will not let a service bind to a port less than
1025 unless it is a ROOT user (in Linux) and NOT AT ALL in OS/X.

In Linux, MIS has the ability to switch from root back to whatever the user
and group is that owns the executable AFTER it binds to the ports it needs
for the server. So in Linux you can simply do a:

sudo ./mis

Or if you want to run it as a DAEMON you can do:

sudo ./mis -d

As mentioned, it will NOT run as root. It will only use root until it binds
to your ports, and then it will switch to the user who owns the executable.

[snip]

I would not suggest that you run it all as root, that seems inherently risky
to me and not necessary.

Best, Paul

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

bcw142 wrote to Night Stalker <=-

G00r00 designed it to run from sudo under the user, it should bind to
the port (<1000) then switch back to that user. If using a port above
1000 you shouldn't have to do that. Remember to set ownership:
sudo chown -R name:name /msytic

The DOSemu issue looks like an environment issue to me, specifically, the setting of $HOME. Another approach could be to use a wrapper script to set the environment variables. This could be done in one of 2 places:

Either when MIS is started (e.g. sudo /mystic/startmis - a script which sets $HOME and then loads mis/mis2), or when calling DOSemu to run a door.

The ARM does have DOSBox and it works (very slow on early units like A
& B). Though I think doorparty is the way to go with the Pi.

Doorparty sounds a lot simpler. :)


... In every revolution, there's one man with a vision. Kirk, stardate unknown --- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

The BBS may be have to run as root, but the folder owner should be the user account, mystic when drops to load an app/door changes to who-ever owns the folder.

Yeah, which makes me wonder why it was trying to call /root/.dosemu instead
of /home/user/.dosemu. That directory exists and is owned by the user.

Mike
---
þ SLMR 2.1a þ Isn't this where....


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

As mentioned, it will NOT run as root. It will only use root until it

binds

to your ports, and then it will switch to the user who owns the executable. [snip]
I would not suggest that you run it all as root, that seems inherently risky to me and not necessary.

I read that, too, but since all of the necessary directories belong to the
user and mystic is trying to access /root/.dosemu, methinks there is
something not quite right. It could be my setup but I am not seeing what.

/home/user
/home/user/mystic
/home/user/.dosemu

All are owned by the user with permissions rwxr-xr-x.

/root/.dosemu does not exist and, IMHO, should have no reason to be accessed.

ONE THING to note... I am trying to set this up from the matrix menu. Could the dang thing still be running as root until a user logs into mystic?

Mike

---
þ SLMR 2.1a þ "Did you open the Microwave door before the 'ding'"?


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

The DOSemu issue looks like an environment issue to me, specifically, the setting of $HOME. Another approach could be to use a wrapper script to set the environment variables. This could be done in one of 2 places:

Either when MIS is started (e.g. sudo /mystic/startmis - a script which sets $HOME and then loads mis/mis2), or when calling DOSemu to run a door.

Do you mean by adding a line such as this to one of the scripts?:

export HOME=/home/user

I have that set in other scripts so I will try it. How would one try it directly when calling DOSemu to run the door?

Thanks!
Mike
---
þ SLMR 2.1a þ Politically incorrect...and proud of it!!!


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

Mike Powell wrote to Vk3jed <=-

Do you mean by adding a line such as this to one of the scripts?:

export HOME=/home/user

Precisely.

I have that set in other scripts so I will try it. How would one try
it directly when calling DOSemu to run the door?

Well, if it's set before calling mystic, you shouldn't need to, but in case, in the BBS, you'd call the script instead of DOSemu, and the script would look like:

#!/bin/bash

export HOME=/home/user
dosemu $@


... Some people are just for looks.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

On 10/28/16, Mike Powell said the following...

Yeah, which makes me wonder why it was trying to call /root/.dosemu instead of /home/user/.dosemu. That directory exists and is owned by
the user.
Mike
---
þ SLMR 2.1a þ Isn't this where....

Because he thinks it's easier. I know we used to do stuff that way back in the early 1990's Linux,he seems to want to do things that way to get around permissions I guess. In this day and age it's going to be an uphill battle, but that's the way he wants to do things. It should make DOSBox easier to use. When you setup as root under any year 2000+ Linux for the most part you end up in /root by default not under /home. It might be changed by editing the passwd data or other such methods.

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