public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: jankomEarthlink <janosk@earthlink.net>
To: Jegunn <jeg@astro.princeton.edu>
Cc: Frantisek Hanzlik <franta@hanzlici.cz>, linux-msdos@vger.kernel.org
Subject: Re: Problem with dosemu
Date: Tue, 22 Apr 2014 23:25:29 -0400	[thread overview]
Message-ID: <535732A9.5060609@earthlink.net> (raw)
In-Reply-To: <alpine.LFD.2.03.1404212259310.22518@astro.princeton.edu>

Thanks Jegunn for your interest in helping with this issue.

On 04/21/2014 11:08 PM, Jegunn wrote:
> Sorry to be so slow/indecisive, but is this not the old problem with
> the memory fence pointer, which used to be fixable with the creation
> of a file in /etc/sysctl.d/, say
I have an old, and somewhat mangled Fedora-3 distro and it does not have 
sysctl.d/90-low-memory-access.conf

> vm.mmap_min_addr=0.
Consequently I don't know how to make the mmap adjustment.

> One also needed to
> keep the kernel from randomizing virtual address space with
>
> echo 0 > /proc/sys/kernel/randomize_va_space
I tried that but segfault is still there.

> this with modern kernels because I run dosemu (1.4) on a 32-bit
My kernel is 2.6.20, configured and compiled by myself.

I just tried dosemu on the same box (32bit AMD) booted into xubuntu 
12.04. I installed dosemu 1.4.0.1 from ubuntu's software center. It was 
flawless, fast, and worked immediately.

CONCLUSION: there is nothing wrong with dosemu. My difficulty is 
probably due to kernel configuration.

I still would like to be able to compile and run it on my FC-3 boot 
environment as well. It is such a learning experience for me to discover 
and understand the inner workings of Unix/Linux/C world.

Janos


  reply	other threads:[~2014-04-23  3:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26  2:32 Problem with dosemu jankomEarthlink
2014-03-30 18:49 ` Frantisek Hanzlik
2014-03-30 23:22   ` jankomEarthlink
2014-03-31  7:31     ` Frantisek Hanzlik
2014-04-14 15:26       ` jankomEarthlink
2014-04-14 22:22         ` Frantisek Hanzlik
2014-04-15  2:24           ` jankomEarthlink
2014-04-21 20:19             ` Frantisek Hanzlik
2014-04-22  2:31               ` jankomEarthlink
2014-04-22  3:08                 ` Jegunn
2014-04-23  3:25                   ` jankomEarthlink [this message]
2014-04-23 11:38                     ` Jegunn
2014-04-22 22:10                 ` Frantisek Hanzlik
     [not found]                   ` <5357347D.1010401@earthlink.net>
2014-04-23  7:06                     ` Frantisek Hanzlik
2014-04-23 19:08                       ` jankomEarthlink
2014-05-04 11:20                         ` Frantisek Hanzlik
2014-05-05  1:57                           ` jankomEarthlink
2014-05-05  8:46                             ` Frantisek Hanzlik
  -- strict thread matches above, loose matches on Subject: below --
2014-04-16 19:52 jankomEarthlink
2014-04-15 21:52 Janos G. Komaromi
2014-04-16  0:47 ` Ivan Baldo
2014-04-16 14:52   ` jankomEarthlink
2014-04-15  3:02 jankomEarthlink
2014-03-25 22:51 jankomEarthlink
2014-03-25 23:35 ` Ivan Baldo
2014-03-25 23:38 ` Frank Cox
2003-08-29 14:06 Problem with DOSEMU scroowhar

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=535732A9.5060609@earthlink.net \
    --to=janosk@earthlink.net \
    --cc=franta@hanzlici.cz \
    --cc=jeg@astro.princeton.edu \
    --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