From mboxrd@z Thu Jan 1 00:00:00 1970 From: aq Subject: Re: stable / unstable parallel install? Date: Tue, 31 May 2005 01:00:28 +0900 Message-ID: <9cde8bff0505300900dfa5ac7@mail.gmail.com> References: <20050530132249.GA12365@bytesex> <20050530155039.GC12702@bytesex> Reply-To: aq Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20050530155039.GC12702@bytesex> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Gerd Knorr Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 5/31/05, Gerd Knorr wrote: > > Have you tried a 'make dist' and then e.g., 'cp -a dist/install > > /opt/xen2', then add appropriate paths to the front of PATH, > > LD_LIBRARY_PATH, PYTHONPATH? >=20 > Works sort of. I have the 2.x versions in /usr now (normal suse > 9.3 rpms), 3.x in /opt/xen3/usr. xend complains that it can't > start xcs and doesn't come up. When I start xcs manually first > it works. I'd guess xend tries to start the 2.x version in > /usr/sbin although /opt/xen3/usr/sbin comes first in $PATH ... >=20 yes, that is the case, since in /usr/sbin/xend, we have: XCS_EXEC =3D "/usr/sbin/xcs" should we execute xcs without the full path?=20 regards, aq