All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Wilson <msw@amazon.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Mohammad Hedayati <hedayati.mo@gmail.com>,
	Thanos Makatos <thanos.makatos@citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: fsimage - no such file
Date: Tue, 19 Jun 2012 08:58:28 -0700	[thread overview]
Message-ID: <20120619155828.GA4296@US-SEA-R8XVZTX> (raw)
In-Reply-To: <1340103453.24176.7.camel@zakaz.uk.xensource.com>

On Tue, Jun 19, 2012 at 03:57:33AM -0700, Ian Campbell wrote:
> On Tue, 2012-06-19 at 09:35 +0100, Thanos Makatos wrote:
> > I have the same problem on xen-unstable 54c8c9eaee92+. I think
> > libfsimage comes with xen (in my repo it's under ./tools/libfsimage).
> > I've investigated a bit and found that in my occasion libfsimage tries
> > to access directory /usr/lib64/fs which doesn't exist,
> > whereas /usr/lib/fs does. I linked /usr/lib64/fs to /usr/lib/fs but
> > then I got other problems, don't remember what. I don't know if this
> > has to do with the fact that my dom0 is 64bit (Debian unstable), or
> > that the domU is 64bit (Debian unstable again), or both.
> 
> Aha I'd been puzzling over why people had been seeing this but I'm not! 
> 
> This very likely is to do with Debian and Ubuntu's transition to
> "multiarch" which has necessitated removing the old compatibility
> symlink /usr/lib64 -> /usr/lib.
> 
> lib64 is a RPMism which doesn't really apply to Debian and derivatives
> and therefore you need to tweak your Xen config before building. I use
> the following local configuration patch (I should probably do the
> equivalent in .config):

lib64 isn't an RPMism, its a Filesystem Hiarchary Standardism [1].

Pretty much every distribution but Debian (and derivatives) adopted
lib64 for all platforms where running 32-bit binaries was common place
(read: all platforms but Alpha and Itanium).

Matt Taggart proposed multiarch for Debian in 2004 (where Red Hat and
SUSE already had support for running a mix of 32-bit and 64-bit
applications on one system), which is captured in the Debian wiki [2].
Ubuntu added support for co-installing 32-bit and 64-bit software in
11.04 [3].

I'm a bit surprised that Debian and Ubuntu can't continue to have a
symlink for lib64 that points at lib/x86_64-linux-gnu. No matter since
I suppose the correct fix is to install the plugins in /usr/lib/$target/fs 
and define FSIMAGE_FSDIR to point there when building libfsimage on
systems that implement multiarch.

Matt

[1] http://www.pathname.com/fhs/
[2] http://wiki.debian.org/Multiarch/TheCaseForMultiarch
[3] https://wiki.ubuntu.com/MultiarchSpec

  parent reply	other threads:[~2012-06-19 15:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 22:24 fsimage - no such file Mohammad Hedayati
2012-06-19  8:35 ` Thanos Makatos
2012-06-19 10:57   ` Ian Campbell
2012-06-19 11:19     ` Mohammad Hedayati
2012-06-19 16:10       ` Matt Wilson
2012-06-19 16:36         ` Ian Campbell
2012-06-23 20:22           ` cyberhawk001
2012-06-23 20:56             ` Matt Wilson
2012-06-19 15:58     ` Matt Wilson [this message]
2012-06-19 16:13       ` Ian Campbell
2012-06-19 16:33         ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120619155828.GA4296@US-SEA-R8XVZTX \
    --to=msw@amazon.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=hedayati.mo@gmail.com \
    --cc=roger.pau@citrix.com \
    --cc=thanos.makatos@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.