From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: nathans@debian.org, vapier@gentoo.org, xfs@oss.sgi.com
Subject: Re: moving libhandle to /usr
Date: Tue, 06 Oct 2009 10:47:18 -0500 [thread overview]
Message-ID: <4ACB6686.9080205@sandeen.net> (raw)
In-Reply-To: <20091006154249.GA1411@infradead.org>
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?
>
Seems fine to me;
/sbin/fsck.xfs:
not a dynamic executable
/sbin/mkfs.xfs:
libuuid.so.1 => /lib64/libuuid.so.1 (0x0000003327e00000)
librt.so.1 => /lib64/librt.so.1 (0x0000003df3e00000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003df2e00000)
libc.so.6 => /lib64/libc.so.6 (0x0000003df2200000)
/lib64/ld-linux-x86-64.so.2 (0x0000003df1e00000)
/sbin/xfs_repair:
libuuid.so.1 => /lib64/libuuid.so.1 (0x0000003327e00000)
librt.so.1 => /lib64/librt.so.1 (0x0000003df3e00000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003df2e00000)
libc.so.6 => /lib64/libc.so.6 (0x0000003df2200000)
/lib64/ld-linux-x86-64.so.2 (0x0000003df1e00000)
As you say, nothing in /sbin needs it AFAICT.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-10-06 15:45 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 [this message]
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
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=4ACB6686.9080205@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 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.