From mboxrd@z Thu Jan 1 00:00:00 1970 From: Akio Takebe Subject: Re: [PATCH] [1/4] put xen console message into syslogbutxm dmesg is not affected Date: Wed, 12 Jul 2006 17:49:00 +0900 Message-ID: <3CC6A59004C94Btakebe_akio@jp.fujitsu.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser , MINAI Katsuhito Cc: Akio Takebe , Hans-Christian Armingeon , xen-devel@lists.xensource.com, Mark Williamson List-Id: xen-devel@lists.xenproject.org Hi, Keir I think xen need to have a pointer of xenlogd. In the case of this implementation, because xenlogd manage the pointer to read dmesg, if xenlogd restart, xenlogd read the same log and write the same log into /var/log/messages. What do you think about this? Best Regards, Akio Takebe > >On 12 Jul 2006, at 09:30, MINAI Katsuhito wrote: > >> Thanks for your advice. >> If Xen return the index of the 'first' byte, it seems to return >> the same value when an out-of-range index is specified. >> But in out-of-range case, Xen give the caller no console message. >> I understood that the Xen interface became simple than returning >> the 'last' byte. > >Let's see how it looks in the patch. > > -- Keir