From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jan Willem Stumpel <jstumpel@planet.nl>
Subject: Re: cannot map temp file pool
Date: Tue, 19 Sep 2006 17:24:32 +0200
Message-ID: <45100BB0.2020905@my.home>
References: <450FE24A.30906@my.home> <450FEFA0.5070800@modsoftsys.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7BIT
Return-path: <linux-msdos-owner@vger.kernel.org>
In-reply-to: <450FEFA0.5070800@modsoftsys.com>
Sender: linux-msdos-owner@vger.kernel.org
List-Id: <linux-msdos.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: Damyan Ivanov <dam@modsoftsys.com>
Cc: Jan Willem Stumpel <jstumpel@planet.nl>, dosemu <linux-msdos@vger.kernel.org>

Damyan Ivanov wrote:

>>WTH is this? No idea what "map temp file pool" means. I hope
>>someone is still around who can answer this. The dosemu font was
>>always OK, BTW.
> 
> 
> I'd run xdosemu under strace and look for "permission denied" errors
> there.

I tried that -- but could not make sense of it. I get things like

open("/dev/shm/dosemu_16975", O_RDWR|O_CREAT|O_TRUNC|O_NOFOLLOW,
0600) = 5
fcntl64(5, F_GETFD)                     = 0
fcntl64(5, F_SETFD, FD_CLOEXEC)         = 0
unlink("/dev/shm/dosemu_16975")         = 0
ftruncate(5, 0)                         = 0
ftruncate(5, 15794176)                  = 0
mmap2(NULL, 15794176, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_SHARED,
5, 0) = -1 EPERM (Operation not permitted)
write(4, "ERROR: MAPPING: cannot map temp "..., 67) = 67
write(2, "ERROR: MAPPING: cannot map temp "..., 67) = 67

15794176 is some suspiciously "round" number (hex 00F10000).

I'd appreciate any ideas.

Regards, Jan