This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] [OT] How to move from pygrub to pv-grub?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] [OT] How to move from pygrub to pv-grub?
From: John Haxby <john.haxby@xxxxxxxxxx>
Date: Tue, 23 Dec 2008 12:53:37 +0000
Delivery-date: Tue, 23 Dec 2008 04:54:27 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <VA.00003566.16179345@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <VA.00003562.1195dcce@xxxxxxxxxxxxxxxxxx> <20081222005520.GD26058@xxxxxxxxxxxxxxxxxxx> <VA.00003566.16179345@xxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20081119)
Kai Schaetzl wrote:
Btw, I get garbled characters from your header displayed that should not display at all. X-GC-3.12: what is that? AFAIK, dots are not allowed in headers, that's why my reader doesn't like that line. Can you change that to use an underscore for instance?

I think your reader is broken.   From RFC 2822, §2.2, Header Fields:

   Header fields are lines composed of a field name, followed by a colon
   (":"), followed by a field body, and terminated by CRLF.  A field
   name MUST be composed of printable US-ASCII characters (i.e.,
   characters that have values between 33 and 126, inclusive), except
and in §3.6.8, Optional Fields, it gives the ABNF corresponding to that description so there's no excuse for getting it wrong :-) I did wonder if the obsolete comment field had any restrictions over its non-obsolete counterpart, but it doesn't.


Xen-users mailing list