Re: Problem: DOSEMU ignores Linux user file access settings -solved

["Mgr. Peter Tuharsky" <tuharsky@misbb.sk>]

Thank You very much.

I tested the way You suggested and I figured out that fault was mine. 
Maybe it was matter of too much stress :o)

The bash.profile umask was set ok, but when I ran DOSEMU directly from X 
and not from terminal, the bash.profile was of course not interpreted. 
Solution was quite simple -add umask command to dosemu start script.

Your help was valuable cause I was able to find and solve problem thanks 
to Your advice.

Thanks to You all that answered my question. Also thanks to DOSEMU team 
for their great work!

Sincerely Peter


Bart Oldeman wrote:

>On Mon, 19 Jan 2004, Mgr. Peter Tuharsky wrote:
>
>  
>
>>    DOSEMU uses one strict policy when creating new file from inside
>>emulated environment: It creates new file with 600 attrib mask and
>>user-only gid/uid. DOSEMU fully IGNORES both bash.profile setting, and
>>folder's SetUid/SetGid setting!! And this is the reason of my big problem.
>>    
>>
>
>no, DOSEMU doesn't ignore them. Be careful here. What is your umask
>setting from bash.profile? Try a simple
>umask
>to be sure about that (in Linux)
>
>If it's 007 then new DOSEMU files (with archive bit set) are
>normally created as
>-rw-rw----
>
>Also DOSEMU doesn't do chown on files so I can't see how it could ignore
>setgid attributes on directories -- the files will have the same
>owner/group as a simple file created with
>echo hello > file
>would do. Try this command in Linux *and* in DOSEMU in the same
>directory and look at the permissions.
>
>  
>
>>directory dosen't help either, because DOSEMU takes .dosemurc strictly
>>from user's home directory and this way the printing is directed to only
>>one printer.
>>    
>>
>
>Try -f. Also the environment variable dosemu__printer can do the trick as
>long as you do *not* define it in .dosemurc.
>
>Bart
>
>  
>