All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ananth <cbananth@gmail.com>
Subject: Re: Re: Issues while running Xen with new RR scheduler
Date: Fri, 1 May 2009 15:59:34 +0100	[thread overview]
Message-ID: <18939.3670.462412.204541@mariner.uk.xensource.com> (raw)
In-Reply-To: <49FB0CFF.6020901@eu.citrix.com>

George Dunlap writes ("Re: [Xen-devel] Re: Issues while running Xen with new RR scheduler"):
> xterm scrollback:
>  * Is much more limited in scope, if you want to see what happened 5000 
>    lines ago

Of course this is configurable, and ...

>  * Can't be searched through / grepped easily
>  * May disappear if something in the boot path clears the screen.

... xterm also has the ability to log to a file, available from the
mouse menus.

> The last one is the most annoying to me.  But if it could be used with 
> script -f, I'd probably switch to it from minicom.  (We actually have 
> serial console devices here at the office, so I don't need minicom.)

I'm sure it would work with script too.

Ian.

  reply	other threads:[~2009-05-01 14:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 18:39 Issues while running Xen with new RR scheduler Ananth
2009-04-27 20:41 ` George Dunlap
2009-04-27 22:39   ` Ananth
2009-04-28 14:19     ` George Dunlap
2009-04-30 22:00       ` Ananth
2009-05-01 10:25         ` George Dunlap
2009-05-01 10:27           ` George Dunlap
2009-05-01 14:48           ` Ian Jackson
2009-05-01 14:53             ` George Dunlap
2009-05-01 14:59               ` Ian Jackson [this message]
2009-05-01 15:03                 ` George Dunlap
2009-05-04  9:59                   ` Ananth
2009-05-08 20:55                     ` Ananth
2009-05-08 21:41                       ` Ananth

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=18939.3670.462412.204541@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=cbananth@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.