From: Anton Ivanov <anton.ivanov@kot-begemot.co.uk>
To: Rob Landley <rob@landley.net>,
richard.weinberger@gmail.com,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Fwd: Mail delivery failed: returning message to sender
Date: Tue, 23 Sep 2014 16:40:48 +0100 [thread overview]
Message-ID: <54219480.7060906@kot-begemot.co.uk> (raw)
In-Reply-To: <54218A8B.5030808@landley.net>
On 23/09/14 15:58, Rob Landley wrote:
> On 09/22/14 13:39, Anton Ivanov wrote:
>> Hi RIchard, hi list,
>>
>> There is some problem with the list on sourceforge. It has bounced one
>> of the patches - no 4.
>>
>> I can resend this for book-keeping purposes.
>>
>> If memory serves me right there are no changes in this particular one so
>> the earlier version (3) from ~ 2 weeks ago can be used instead.
>>
>> A.
> As long as somebody's paying attention to UML again: what would be
> involved in adding support for arm/mips/sh4/sparc...
That is a different cattle of fish compared to fixing general
performance and networking. Some of that may be quite difficult too. I
also wanted to look at arm at some point, but never got around to do it :)
By the way, I am not paying attention to just UML - the same vNICs which
use direct attachment to overlay (or network) are ported to QEMU too.
In fact, despite all of this being written originally for UML, the QEMU
L2TPv3 vNIC has ended up being published first. It is part of QEMU 2.1.
The other ones (GRE, RAW) will follow when I get around to do them
(hopefully before year end).
A.
>
> I've mostly wandered off to use qemu these days, and I package system
> images with native compilers you can boot up and compile software in:
>
> http://landley.net/aboriginal/bin/
>
> (Grab a system-image-$ARCH.tar.bz2 and ./run-emulator.sh in that, or
> ./dev-environment.sh if you want it to truncate and ext2 format a
> scratch space block device and and mount it on /home in the emulated
> system so you have persistent storage.)
>
> I'm under the impression that user mode linux would need some glue code
> to run on powerpc, but dunno what it would actually be...
>
> Rob
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2014-09-23 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XW6rt-0005E0-Pl@sog-mx-2.v43.ch3.sourceforge.com>
2014-09-22 18:39 ` [uml-devel] Fwd: Mail delivery failed: returning message to sender Anton Ivanov
2014-09-23 14:58 ` Rob Landley
2014-09-23 15:13 ` Richard Weinberger
2014-09-23 15:40 ` Anton Ivanov [this message]
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=54219480.7060906@kot-begemot.co.uk \
--to=anton.ivanov@kot-begemot.co.uk \
--cc=richard.weinberger@gmail.com \
--cc=rob@landley.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