From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Linuxemu
Date: Thu, 28 Nov 2002 11:33:10 -0500 [thread overview]
Message-ID: <7b7b420200424ead0c949d6b3cf8ff9d@plan9.bell-labs.com> (raw)
> thanks a lot for linuxemu! However, I was only able to run the stuff
> included with /bin. Other linux progs (sort, bc...) did not work
> (see below). May it be they were dynamically linked with glibc?
> Thus, isn't there a dosemu around there? (Perhaps it would be easier
right, /bin is typically statically linked, while /usr/bin
is dynamically linked. like i said, it wouldn't be too hard
to make dynamic linking work. in theory,
linuxemu ld-linux.so.1 bin/a.dynamic
is supposed to work, but unfortunately ld-linux.so.1
wants to be loaded where the linuxemu text segment is.
you'd need to move the linuxemu text segment somewhere
else and then segdetach it before calling elfload. it's entirely
doable, especially since x86 code is position independent.
dosemu is much harder because you have to deal with
all the weird 16-bit processor modes. at that point it's easier
just to simulate the 16-bit processor than to get plan 9 to
set up the processor the way you want it. the other problem
with dosemu is that the set of system calls doesn't map as
nicely to plan 9 system calls. i wrote one of those too, but
only enough to execute the vga bios code. the theory was
that this might be significantly easier than the kernel support
required. i still think that's true, but it didn't just work. there
are some things that need certain timing to work out properly,
and the simulator is too slow. at least, that's my theory.
i think there's still hope for it -- you could hard code certain
sequences that had to run nearer to full speed and run them
as one pseudo-op in the simulator.
next reply other threads:[~2002-11-28 16:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 16:33 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-18 19:15 [9fans] LinuxEMU David Leimbach
2010-01-18 20:01 ` ron minnich
2010-01-18 20:11 ` David Leimbach
2010-01-18 20:23 ` ron minnich
2010-01-18 22:43 ` cinap_lenrek
2010-01-18 23:16 ` David Leimbach
2010-01-18 23:20 ` David Leimbach
2010-01-18 23:46 ` Eric Van Hensbergen
2010-01-27 14:42 ` Ethan Grammatikidis
2010-02-06 1:08 ` Enrico Weigelt
2010-02-06 17:56 ` cinap_lenrek
2010-02-06 18:26 ` David Leimbach
2003-02-11 11:19 [9fans] Linuxemu peter a. cejchan
2002-11-28 8:17 Petr Cejchan
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=7b7b420200424ead0c949d6b3cf8ff9d@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).