public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: nathans@debian.org, Mike Frysinger <vapier@gentoo.org>, xfs@oss.sgi.com
Subject: Re: moving libhandle to /usr
Date: Tue, 06 Oct 2009 19:53:18 -0500	[thread overview]
Message-ID: <4ACBE67E.8010502@sandeen.net> (raw)
In-Reply-To: <20091006234425.GA20561@infradead.org>

Christoph Hellwig wrote:
> On Tue, Oct 06, 2009 at 03:33:46PM -0400, Mike Frysinger wrote:
>> On Tuesday 06 October 2009 11:42:49 Christoph Hellwig wrote:
>>> Currently we install the versioned libhandle into /lib by default,
>>> and all other libraries into /usr.  Given that no program in / actually
>>> uses libhandle this seems rather awkward to me.  From Mike's comments
>>> in the past I think Gentoo already installs it into /usr anyway.
>>>
>>> Is there anything speaking against moving all libraries to /usr and
>>> switching Debian/Fedora to that aswell?
>> xfsdump uses it and xfsdump is installed into / by default right ?  so 
>> libhandle needs to be in /lib so long as xfsdump is in /sbin.
> 
> Indeed, the makefile configuration currently builds it into /, while
> the configure default uses /usr.  Yikes..

argh I did rpm -ql xfsprogs xfsdump | grep bin ... on a box that didn't 
have xfsdump installed.  Argh.

Thanks for the catch Mike ;)

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2009-10-07  0:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 15:42 moving libhandle to /usr Christoph Hellwig
2009-10-06 15:47 ` Eric Sandeen
2009-10-06 18:45   ` Nathan Scott
2009-10-06 19:33 ` Mike Frysinger
2009-10-06 23:44   ` Christoph Hellwig
2009-10-07  0:53     ` Eric Sandeen [this message]

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=4ACBE67E.8010502@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=hch@infradead.org \
    --cc=nathans@debian.org \
    --cc=vapier@gentoo.org \
    --cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox