Re: [Xen-devel] rationale behind pygrub with TERM=vt100

Ian Campbell wrote:  [Tue May 15 2007, 02:06:18AM EDT]
> I think it's because of cset 13540:5f998c3170f7 (Plumb bootloader
> I/O through xenconsole) which meant that there was no sane $TERM to
> be passed into pygrub anymore since you can't know the $TERM of the
> eventual xenconsole client. vt100 is a good low common denominator.

Thanks, that's helpful.  I missed the connection between those
changesets...

Aron

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] rationale behind pygrub with TERM=vt100, Aron Griffis Re: [Xen-devel] rationale behind pygrub with TERM=vt100, Ian Campbell Re: [Xen-devel] rationale behind pygrub with TERM=vt100, Aron Griffis <=

Previous by Date:

[Xen-devel] vmx status report against cset 15072 - one blocker issue, Zhao, Yunfeng

Next by Date:

Re: [Xen-devel] trap/interrupt gate for hypercall, Keir Fraser

Previous by Thread:

Re: [Xen-devel] rationale behind pygrub with TERM=vt100, Ian Campbell

Next by Thread:

[Xen-devel] [ANNOUNCE] virtbench now has xen support, Rusty Russell

Indexes:

[Date] [Thread] [Top] [All Lists]