Running dosemu as a user

Running dosemu as a user

[Victor Warner]

  unable to run Dosemu as a user. When I try to run xdosemu or dosemu as a  
user I get
the following message: "bash: dosemu: command not found".

There no are problems running from root (eg su from Konsole). A copy of  
MSDOS 6.22
is installed in /home/victor/dos. Running Linspire 5.0.59

I compiled from source code. After compilation Dosemu (1.3.1, 1.3.2 or  
1.3.3) is placed in

1. /etc/dosemu (containing dosemu.conf, dosemu.users, global.conf)
2. /usr/local/bin (containing dosemu.bin etc)
3. /usr/local/share (containing commands directory, xfonts directory,  
freedos directory etc).
4. /root/.dosemu/ (containing drives directory, run directory, etc)

I have looked through all the documentation (INSTALL, readme.txt, etc) but  
cannot see the
specific command or setting to deal with this (or cannot understand  
significance of what is
written) (tried adding "victor c_all" to dosemu.users but the problem  
still present).

Help in solving this would be gratefully received.

Content of boot.log and /root/.dosemurc below

Victor Warner


/root/.dosemurc
$_hdimage = "/home/victor/dos"
$_printer_command = "lpr -l"
$_printer = "hplj3030"
$_layout="uk"
$_X_font="vga12x30"

/root/.dosemu/boot.log

CONF: config variable parser_version_3 set
CONF: config variable c_system set
CONF: Parsing built-in dosemu.conf file.
CONF: config variable version_3_style_used set
CONF: Parsing built-in global.conf file.
CONF: config variable version_3_style_used unset
CONF: config variable version_3_style_used set
CONF: opened include file /etc/dosemu/dosemu.conf
CONF: closed include file /etc/dosemu/dosemu.conf
CONF: opened include file /root/.dosemurc
CONF: closed include file /root/.dosemurc
CONF: config variable skip_dosrc set
CONF: mapping driver = 'auto'
debug flags: -a+cw
CONF: Disabling use of pentium timer
CONF: dosbanner on
CONF: timer freq=18, update=54925
CONF: CPU set to 386
CONF: 8192k bytes XMS memory
CONF: 2048k bytes EMS memory
CONF: EMS-frame = 0xe000
CONF: DPMI-Server on
CONF: PM DOS API Translator on
CONF: dosemu running on _xterm
SER: directory /var/lock namestub LCK.. binary No
MOUSE: no device specified, type 0 using internaldriver: yes,  
emulate3buttons: no
baudrate: 0
CONF: Keyboard-layout keyb-user
CONF: Keyboard-layout uk
device: /dev/fd0 type 2 h: 0  s: 0   t: 0 floppy A:
CONF: fastfloppy = 1
CONF: IPX support off
CONF(LPT0) f: (null)   c: lpr -l  o: -Phplj3030  t: 20  port: 0
CONF: not allowing speaker port access
CONF: Packet Driver disabled.
device: /home/victor/dos type 4 h: -1  s: -1   t: -1 drive C:
CONF: config variable c_system unset
CONF: running exclusively as ROOT: uid=0 (cached 0) gid=0 (cached 0)
DBG_FD already set
DOSEMU-1.3.1.0 is coming up on Linux version 2.6.10
CONF: reserving 640Kb at 0x00000 for 'd' (Base DOS memory (first 640K))
CONF: reserving 64Kb at 0xF0000 for 'r' (Dosemu reserved area)
CPU: Stack bottom 0xbfffe000, top 0xc0000000, esp=0xbffff6c0
major = 136 minor = 1
CONF: reserving 128Kb at 0xA0000 for 'v' (Video memory)
SERIAL $Header: /cvsroot/dosemu/dosemu/src/base/serial/ser_init.c,v 1.9  
2004/05/07
13:49:45 stsp Exp $
CONF: reserving 64Kb at 0xE0000 for 'E' (EMS page frame)
TIME: using 9154 usec for updating ALRM timer
DOS termination requested
leavedos(0|0x0) called - shutting down

Re: Running dosemu as a user

[Mike McCarty]

Victor Warner wrote:
>  unable to run Dosemu as a user. When I try to run xdosemu or dosemu as 
> a  user I get
> the following message: "bash: dosemu: command not found".

This indicates a likely error in your PATH variable. BASH uses
the PATH variable to search for command files.

> There no are problems running from root (eg su from Konsole). A copy of  
> MSDOS 6.22
> is installed in /home/victor/dos. Running Linspire 5.0.59
> 
> I compiled from source code. After compilation Dosemu (1.3.1, 1.3.2 or  
> 1.3.3) is placed in
> 
> 1. /etc/dosemu (containing dosemu.conf, dosemu.users, global.conf)
> 2. /usr/local/bin (containing dosemu.bin etc)

You probably need to add /usr/local/bin to your PATH variable.
A possible fix is to add in .profile, .bashrc, or wherever you prefer
a line like:

	export PATH=$PATH:/usr/local/bin

You may need to add other things to the PATH variable.

[snip]

> Help in solving this would be gratefully received.

HTH.

[snip]

Mike
-- 
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!

Re: Running dosemu as a user

[Victor Warner]

Thank you for your reply but this is the first time I have had to do this type 
of thing..

There is only only .profile (in /root) but several .bashrc (/root, /home/victor, 
 /etc/bash, etc). 

In which one of the files do I add "export PATH=$PATH:/usr/local/bin"?

Any further help would be very gratefully received.

Victor Warner

Re: Running dosemu as a user

[Mike McCarty]

Victor Warner wrote:
> Thank you for your reply but this is the first time I have had to do this type 
> of thing..

I had already managed to figure that out :-)

> There is only only .profile (in /root) but several .bashrc (/root, /home/victor, 
>  /etc/bash, etc). 
> 
> In which one of the files do I add "export PATH=$PATH:/usr/local/bin"?

For whichever user it is that is having the problem.

> Any further help would be very gratefully received.

I presume that you log in as user "victor". In that case, you put
the export line in

	/home/victor/.bashrc

If you also log in as "vwarner", then you would also put it
into

	/home/vwarner/.bashrc

This is only a convention, and you could put it elsewhere.

Here is how this works:

When you enter a command like

$ ls

your shell (bash in this case) first looks to see if it "knows"
this command itself. In this case (ls) it does not. It then
looks for an environment variable (just some information you
have given to bash and given a name) for a list of directories
to search for a file named "ls". The name of the environment
variable is "PATH". The entries in the PATH variable are
separated by the colon character (":"). To query what variables
you have told bash about, you use the "set" command, which
bash knows directly. Like this:

$ set

You'll see a bunch of stuff come out. Probably more than you
want. So you can use "less" to view it. Like this:

$ set | less

Or if you want to query your PATH, you can use grep, like this:

$ set | grep PATH

Mine looks like this...

$ set | grep PATH
PATH=/home/jmccarty/bin:/home/jmccarty/games/usr/games:/home/jmccarty/devtools/assemblers/asxxxx/asxv4pxx/asxmak/linux/exe:/usr/local/lib/lcc:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin

So, when I type in "ls fred", bash first sees that it doesn't know
about "ls" directly, and it then looks for /home/jmccarty/bin/ls.
It finds nothing. Then it looks for /home/jmccarty/games/usr/games/ls,
and still finds nothing. Then it looks in /home/jmccarty/de...
Eventually it looks for /bin/ls, and it finds an executable, which
it loads and runs.

To set a variable to a value, use

$ set VARIABLE="value to set"

This sets it only for the shell. To make the variable visible
to other programs the shell runs, you need to export it.

$ export VARIABLE

These two commands may be abbreviated into just the export, like this

$ export VARIBLE="value to set VARIABLE to"

Now, to use what is in a variable when setting a variable, use
the "$" symbol. Like this:

$ set VAR1="string 1"
$ set VAR2="$VAR1:string 2"

This sets VAR2 to "string 1:string 2". So,

$ export PATH="$PATH:/usr/local/bin"

sets PATH to whatever it already is, followed by a colon and
some more information.

It happens that there is a convention that applications use
an "rc" file to Read Configuration from. For bash, it is
~/.bashrc, which contains a bunch of commands which bash
executes upon startup.

Got it?

I suggest you use

$ man bash
$ info bash

to get more information.

Mike
-- 
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!

Re: Running dosemu as a user

[Victor Warner]

Mike 
 
Thank you very much for the detailed explanation. It helped to make much 
that was unclear clear.  
 
However, Linspire does not store the PATH for a user in .profile or .bashrc 
files (where ever they are located). 
 
Until I hear from Linspire technical support, I just copied the .dosemurc 
file to the home directory and got dosemu to run by 
typing  /usr/local/bin/xdosemu from Konsole.  
 
Victor Warner 
 
On Thu, 29 Dec 2005 19:45 , Mike McCarty <mike.mccarty@sbcglobal.net> sent: 
 
>Victor Warner wrote: 
>> Thank you for your reply but this is the first time I have had to do 
this type  
>> of thing.. 
> 
>I had already managed to figure that out :-) 
> 
>> There is only only .profile (in /root) but several .bashrc 
(/root, /home/victor,  
>>  /etc/bash, etc).  
>>  
>> In which one of the files do I add "export PATH=$PATH:/usr/local/bin"? 
> 
>For whichever user it is that is having the problem. 
> 
>> Any further help would be very gratefully received. 
> 
>I presume that you log in as user "victor". In that case, you put 
>the export line in 
> 
> /home/victor/.bashrc 
> 
>If you also log in as "vwarner", then you would also put it 
>into 
> 
> /home/vwarner/.bashrc 
> 
>This is only a convention, and you could put it elsewhere. 
> 
>Here is how this works: 
> 
>When you enter a command like 
> 
>$ ls 
> 
>your shell (bash in this case) first looks to see if it "knows" 
>this command itself. In this case (ls) it does not. It then 
>looks for an environment variable (just some information you 
>have given to bash and given a name) for a list of directories 
>to search for a file named "ls". The name of the environment 
>variable is "PATH". The entries in the PATH variable are 
>separated by the colon character (":"). To query what variables 
>you have told bash about, you use the "set" command, which 
>bash knows directly. Like this: 
> 
>$ set 
> 
>You'll see a bunch of stuff come out. Probably more than you 
>want. So you can use "less" to view it. Like this: 
> 
>$ set | less 
> 
>Or if you want to query your PATH, you can use grep, like this: 
> 
>$ set | grep PATH 
> 
>Mine looks like this... 
> 
>$ set | grep PATH 
>PATH=/home/jmccarty/bin:/home/jmccarty/games/usr/games:/home/jmccarty/devtools/assemblers/asxxxx/asxv4pxx/asxmak/linux/exe:/usr/local/lib/lcc:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin 
> 
>So, when I type in "ls fred", bash first sees that it doesn't know 
>about "ls" directly, and it then looks for /home/jmccarty/bin/ls. 
>It finds nothing. Then it looks for /home/jmccarty/games/usr/games/ls, 
>and still finds nothing. Then it looks in /home/jmccarty/de... 
>Eventually it looks for /bin/ls, and it finds an executable, which 
>it loads and runs. 
> 
>To set a variable to a value, use 
> 
>$ set VARIABLE="value to set" 
> 
>This sets it only for the shell. To make the variable visible 
>to other programs the shell runs, you need to export it. 
> 
>$ export VARIABLE 
> 
>These two commands may be abbreviated into just the export, like this 
> 
>$ export VARIBLE="value to set VARIABLE to" 
> 
>Now, to use what is in a variable when setting a variable, use 
>the "$" symbol. Like this: 
> 
>$ set VAR1="string 1" 
>$ set VAR2="$VAR1:string 2" 
> 
>This sets VAR2 to "string 1:string 2". So, 
> 
>$ export PATH="$PATH:/usr/local/bin" 
> 
>sets PATH to whatever it already is, followed by a colon and 
>some more information. 
> 
>It happens that there is a convention that applications use 
>an "rc" file to Read Configuration from. For bash, it is 
>~/.bashrc, which contains a bunch of commands which bash 
>executes upon startup. 
> 
>Got it? 
> 
>I suggest you use 
> 
>$ man bash 
>$ info bash 
> 
>to get more information. 
> 
>Mike 
>--  
>p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);} 
>This message made from 100% recycled bits. 
>You have found the bank of Larn. 
>I can explain it for you, but I can't understand it for you. 
>I speak only for myself, and I am unanimous in that! 
>- 
>To unsubscribe from this list: send the line "unsubscribe linux-msdos" in 
>the body of a message to majordomo@vger.kernel.org 
>More majordomo info at  http://vger.kernel.org/majordomo-info.html 
 
 

---- Message sent via Waitrose Webmail - http://www.waitrose.com/

Re: Running dosemu as a user

[Victor Warner]

Peter, 
 
Thank you for the information. Your very helpful explanation pre-empted a 
question: that if I just add a PATH variable for /usr/local/bin whether I 
would overwrite any PATH variables. It seems clear that this will not 
happen. 
 
Also thank for providing: 
"~/.bash_profile (not .bashrc) file: 
 
        if ! echo "$PATH" | grep "/usr/local/bin"; then 
           PATH="$PATH:/usr/local/bin" 
        fi 
        export PATH" 
 
What you and Mike have written has put a lot of information in context.  
 
I have never heard of Rube Goldberg. But looking at his web site I can see 
the resemblance... 
 
Victor Warner 
 
 
 
 
On Tue, 03 Jan 2006 09:03 , Peter B. Steiger <wyo_wl001@bresnan.net> sent: 
 
>On Tue, 2006-01-03 at 14:42 +0000, Victor Warner wrote: 
>> However, Linspire does not store the PATH for a user in .profile 
or .bashrc  
>> files (where ever they are located).  
> 
>Victor, 
>Linspire can't put PATH anywhere that other Linux distros put it; under 
>all the fancy decorations it's still running the startup (SysV init) and 
>console shell (probably bash) as any other Linux. 
> 
>Adding to what Mike said, the dotted files (.profile and .bashrc) are 
>only used for changes each user might want to make personally to what 
>the system sets up for all users.  For example, the system might decree 
>that only /bin and /usr/bin are in the path, but you might want to 
>add /usr/local/bin to that path.  Fred might want his path to include 
>his personal directory (/home/fred/bin), and so on.  When Mike talks 
>about ~/.profile, the tilde is a shortcut that means "the /home 
>directory for the login you are currently using".  If you are root, ~ 
>is /root.  If you are rumplestiltskin, ~ is /home/rumplestiltskin.  So 
>each ~/.profile is different for each login. 
> 
>Now, when you first log in, three environment setting scripts are run in 
>this order: /etc/security/pam_env.conf (if they use pluggable 
>authentication modules for security, which they probably do), 
>then /etc/profile, then ~/.bash_profile.  The first two are run for 
>every user as soon as you log in, so even if you don't have 
>a .bash_profile or .profile or .bashrc in your home directory, you will 
>have the same basic path set that everyone has. 
> 
>So, if the default path does not include a path to the dosemu binary, 
>add this to your ~/.bash_profile (not .bashrc) file: 
> 
>        if ! echo "$PATH" | grep "/usr/local/bin"; then 
>           PATH="$PATH:/usr/local/bin" 
>        fi 
>        export PATH 
>         
>The "if" line ensures that if /usr/local/bin is already part of the 
>path, it won't get re-added every time the shell invokes another child 
>copy - with the result that your path would include /usr/local/bin 
>numerous times. 
> 
>Clear as mud? {grin} I spent several hours one day tracing through the 
>login and shell startup processes to see which scripts get invoked when, 
>and I finally have a pretty good idea of how it all works.  A flowchart 
>would resemble a Rube Goldberg illustration! 
> 
>Regarding Mike's instructions on how to examine the current PATH value 
>from a console shell:  I've been using DOS in some form for 25 years, so 
>I added aliases to mimic DOS commands: 
>alias path='echo $PATH' 
>alias ver='cat /proc/ver' 
>alias del='rm' 
>alias dir='ls' 
> 
>I also renamed my /etc/rc.d/init.d/functions file to config.sys, 
>and /etc/rc.d/rc.sysinit to autoexec.bat, but that's just because I have 
>a sick sense of humor. 
> 
>--  
>Peter B. Steiger 
>Cheyenne, WY 
> 
> 
 
 

---- Message sent via Waitrose Webmail - http://www.waitrose.com/