From: Jeremy Katz Subject: Re: [PATCH] /sys/hypervisor/uuid Date: Fri, 19 May 2006 12:43:46 -0400 Message-ID: <1148057026.9927.22.camel@aglarond.local> References: <87y7wzmeqb.fsf@pike.pond.sub.org> <20060519074112.GF2724@moss.sous-sol.org> <3d8eece20605190243v626b894bp1f5e6f4ff23e56d1@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <3d8eece20605190243v626b894bp1f5e6f4ff23e56d1@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Fri, 2006-05-19 at 10:43 +0100, Christian Limpach wrote: > Also, the guest domain xenstore interface was never really intended to > be used in anger, it was only added to support driver domains getting > information about the devices to configure. The immediate issue would > be that access to xenstore is through a file in /proc/xen and I'd > expect that to change at some point. Might be good to already add the > new path to all tools as a fallback option now. Any suggestions for > where this would end up in /sys I presume? Actually, I'd suggest just taking it out and shooting it altogether. What was the _intended_ use of having this exposed to the guest, especially given that anything exposed shouldn't be considered a stable ABI/API? Jeremy