linux-um archives
 help / color / mirror / Atom feed
From: Jack Cummings <jack@mudshark.org>
To: linux-abi-devel@lists.sourceforge.net,
	user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Linux-abi and UML?
Date: Fri, 28 Nov 2003 17:21:53 -0800	[thread overview]
Message-ID: <20031129012153.GA20038@ice.mudshark.org> (raw)

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


Hello, 

I'm curious as to whether it is worthwhile to pursue using Linux-ABI under UML,
or if there is too much low level x86 evil to make it worthwhile.

--Jack 


--
John ( Jack ) Cummings                     http://mudshark.org/jack 
Key fingerprint: 0774 D073 E386 B70B 6B16  2D2B 1DD8 F8B0 CCF0 FAEE
Now playing on Prime:    Wedding in Sarajevo -- Screaming Headless Torsos
Now playing on Remedial: When in Rome -- Billy Joel

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-11-29  1:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-29  1:21 Jack Cummings [this message]
2003-12-06  0:05 ` [uml-devel] Linux-abi and UML? Jeff Dike

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=20031129012153.GA20038@ice.mudshark.org \
    --to=jack@mudshark.org \
    --cc=linux-abi-devel@lists.sourceforge.net \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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