From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How do I disable -curses mode?
Date: Fri, 9 Oct 2009 00:15:27 -0500 [thread overview]
Message-ID: <200910090015.27696.rob@landley.net> (raw)
In-Reply-To: <200910080303.26027.rob@landley.net>
On Thursday 08 October 2009 03:03:25 Rob Landley wrote:
> I'm running qemu -nographic from a script, booting up a linux -kernel with
> a serial console and driving it via "expect" to feed data to its stdin and
> parse its output.
>
> This worked fine under 0.10.0, but under 0.11.0 it craps curses escape
> sequences all over the place, ala:
Nevermind, the curses issue got fixed during the development series. The
escape sequences I was still seeing were busybox ash trying to query the TTY
size at the other end of the serial console. (That I can work around easily
enough, and are deterministically placed anyway.)
My bad, carry on. :)
Rob
--
Latency is more important than throughput. It's that simple. - Linus Torvalds
prev parent reply other threads:[~2009-10-09 5:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 8:03 [Qemu-devel] How do I disable -curses mode? Rob Landley
2009-10-09 5:15 ` Rob Landley [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=200910090015.27696.rob@landley.net \
--to=rob@landley.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).