Linux MS DOS discussions
 help / color / mirror / Atom feed
From: Damyan Ivanov <dam@modsoftsys.com>
To: Jan Willem Stumpel <jstumpel@planet.nl>
Cc: dosemu <linux-msdos@vger.kernel.org>
Subject: Re: cannot map temp file pool
Date: Tue, 19 Sep 2006 16:24:48 +0300	[thread overview]
Message-ID: <450FEFA0.5070800@modsoftsys.com> (raw)
In-Reply-To: <450FE24A.30906@my.home>

[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]

[resent with list included]
Jan Willem Stumpel -- 19.09.2006 15:27 --:
> I did 'nothing' (apart from the usual Debian dist-upgrades) to my
> beautifully-working dosemu installation and now I get this.. sigh..
> 
>  jws@vega:~$ xdosemu
> 
>    You do not have the DOSEMU vga font installed and are running
>    remote X. You need to install the vga font on your _local_
>    Xserver.
>    Look at the readme for details. For now we start with an fixed
>    font, which does not display all national characters correctly.
>    ... be warned
> 
>  ERROR: MAPPING: cannot map temp file pool, Operation not
>  permitted
>  ERROR: MAPPING: cannot map temp file pool, Operation not
>  permitted
>  Segmentation fault
>  jws@vega:~$
> 
> 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.



	dam
-- 
Damyan Ivanov                           Modular Software Systems
dam@modsoftsys.com
phone +359(2)928-2611, 929-3993              fax +359(2)920-0994
mobile +359(88)856-6067             dam@jabber.minus273.org/Gaim


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2006-09-19 13:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-19 12:27 cannot map temp file pool Jan Willem Stumpel
2006-09-19 13:24 ` Damyan Ivanov [this message]
2006-09-19 15:24   ` Jan Willem Stumpel
2006-09-19 16:21     ` Robert Komar
2006-09-19 16:48     ` Mike McCarty
2006-09-19 18:12       ` Jan Willem Stumpel
2006-09-19 18:34         ` Robert Komar
2006-09-19 19:16           ` Jan Willem Stumpel
2006-09-19 20:17             ` Bart Oldeman
2006-09-19 20:58               ` Mike McCarty
2006-09-19 21:05                 ` Bart Oldeman
2006-09-20  9:56               ` Jan Willem Stumpel
2006-09-20 16:21                 ` Mike McCarty
2006-09-20 17:03                   ` Jan Willem Stumpel
2006-09-20 17:11                     ` Mike McCarty
2006-09-20 22:06                     ` Claudia Neumann
2006-09-21 11:17                       ` Jan Willem Stumpel
2006-09-21 17:56                         ` Claudia Neumann
2006-09-19 19:15         ` Alain M.
  -- strict thread matches above, loose matches on Subject: below --
2006-09-24 17:37 Stas Sergeev
2006-09-24 20:41 ` Jan Willem Stumpel
2006-09-25  3:45   ` Stas Sergeev
2006-09-25  8:54     ` Jan Willem Stumpel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=450FEFA0.5070800@modsoftsys.com \
    --to=dam@modsoftsys.com \
    --cc=jstumpel@planet.nl \
    --cc=linux-msdos@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox