public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Frantisek Hanzlik <franta@hanzlici.cz>
To: Javier Tarifa <xavier.tarifa@adbosch.es>
Cc: linux-msdos@vger.kernel.org
Subject: Re: Compilation options used in the binary distribution
Date: Tue, 20 Jan 2009 23:08:34 +0100	[thread overview]
Message-ID: <49764B62.1060708@hanzlici.cz> (raw)
In-Reply-To: <4975F22B.90509@adbosch.es>

Javier Tarifa wrote:
> I'd like to know exactly how was compiled the binary distribution that
> you get when you download dosemu-1.4.0-bin.tgz.
> I've done a little change to the terminal code and when I a run a
> program with my own compiled version, the program dies saying something
> about too many users when I have more than one dosemu running it. But
> when I use the binary distribution this doesn't happen, I can have
> multiple dosemus using it without problems.
> Can someone help me?
-- 
You want run multiple dosemus under one user account? Then maybe will
be usefull start individual instances with unique "-o logfile" log file
specification (instead of default "~/.dosemu/boot.log"). Or You can
specify log/debug filespec in individual .dosemurc files with option
"$_debugout = "filespec".

Although I use and have dosemu 1.4 compiled for several Fedora distributions,
and it works fine when simultaneously run couple of them from one user,
even without specifying different boot.log file - they all use implicit
one (lsof says)(it's smut way, but dosemus curiously works)

You can too look for my build options in RPM .spec files at:

http://hanzlici.cz/packages/fedora/dosemu/

Regards,
Franta Hanzlik

  reply	other threads:[~2009-01-20 22:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 15:47 Compilation options used in the binary distribution Javier Tarifa
2009-01-20 22:08 ` Frantisek Hanzlik [this message]
2009-01-21 14:51   ` Javier Tarifa

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=49764B62.1060708@hanzlici.cz \
    --to=franta@hanzlici.cz \
    --cc=linux-msdos@vger.kernel.org \
    --cc=xavier.tarifa@adbosch.es \
    /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