qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] handling SIGWINCH with qemu -nographic
Date: Fri, 19 Oct 2007 19:24:10 -0500	[thread overview]
Message-ID: <200710191924.11085.rob@landley.net> (raw)
In-Reply-To: <47152451.7020803@mail.berlios.de>

On Tuesday 16 October 2007 3:51:29 pm Stefan Weil wrote:
> Jeff Carr schrieb:
> > On 10/15/07 19:32, Paul Brook wrote:
> >> qemu emulates a real machine. Signals are an operating system
> >> concept, so your
> >> question makes no sense. Configure your guest OS exactly the same way
> >> you
> >> would a real machine with a serial console.
> >
> > OK. I thought there might be a way.
>
> I think your question is quite reasonable. Imagine a Linux host
> running X Windows and a terminal like xterm or kconsole.

This is why ssh was invented.  That passes through terminal information just 
fine.  QEMU does have a virtual network...

> Then run a program like "top" or "less" in this terminal.
> When a user changes the size of the console window, top, less
> and other console applications get notified of this change by SIGWINCH.

You can also set the environment variables COLUMNS and LINES to the 
appropriate values.  Most things will parse that and use it if the tty info 
isn't available.

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

  parent reply	other threads:[~2007-10-20  3:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16  1:15 [Qemu-devel] handling SIGWINCH with qemu -nographic Jeff Carr
2007-10-16  2:32 ` Paul Brook
2007-10-16 18:21   ` Jeff Carr
2007-10-16 20:51     ` Stefan Weil
2007-10-16 21:21       ` Paul Brook
2007-10-20  0:24       ` Rob Landley [this message]
2007-10-16 14:04 ` Stuart Brady
2007-10-20  0:22 ` Rob Landley

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=200710191924.11085.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).