[gentoo-user] How and whether to take action on elog message from sys-fs/lvm2-2.02.73

[gentoo-user] How and whether to take action on elog message from sys-fs/lvm2-2.02.73

[Kevin O'Gorman]

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

I read the logs, but it doesn't always help.  This one apparently used to
build statically,
and is now using shared libraries.  Here's the message:
=======================================================
*Subject:* [portage] ebuild log for sys-fs/lvm2-2.02.73 on
treat.kosmanor.com

LOG: setup
Warning, we no longer overwrite /sbin/lvm and /sbin/dmsetup with
their static versions. If you need the static binaries,
you must append .static the filename!
=======================================================
**
It's not clear to me that I would need this package when dynamically loading
is inactive,
partly because I don't think that happens -- /usr/lib is not on a separate
partition, so
it's always there.

Leaving that aside, the message does not state *which* filename to append
".static" to,
and where to change it, so I'm baffled as to how to take action on this
message, even
if I thought it important to do.

Anyone have a clue?

-- 
Kevin O'Gorman, PhD

[-- Attachment #2: Type: text/html, Size: 1304 bytes --]

Re: [gentoo-user] How and whether to take action on elog message from sys-fs/lvm2-2.02.73

[Alan McKinnon]

Apparently, though unproven, at 18:55 on Friday 27 August 2010, Kevin O'Gorman 
did opine thusly:

> I read the logs, but it doesn't always help.  This one apparently used to
> build statically,
> and is now using shared libraries.  Here's the message:
> =======================================================
> *Subject:* [portage] ebuild log for sys-fs/lvm2-2.02.73 on
> treat.kosmanor.com
> 
> LOG: setup
> Warning, we no longer overwrite /sbin/lvm and /sbin/dmsetup with
> their static versions. If you need the static binaries,
> you must append .static the filename!
> =======================================================
> **
> It's not clear to me that I would need this package when dynamically
> loading is inactive,
> partly because I don't think that happens -- /usr/lib is not on a separate
> partition, so
> it's always there.
> 
> Leaving that aside, the message does not state *which* filename to append
> ".static" to,
> and where to change it, so I'm baffled as to how to take action on this
> message, even
> if I thought it important to do.
> 
> Anyone have a clue?


I should think it's quite obvious actually. The elog mentions /usr/lib 
nowhere, it does mention /sbin. It also explicitly mentions two filenames:

/sbin/lvm
/sbin/dmsetup

then says that they are no longer overwritten with static versions. So, 
presumably, /sbin/{lvm|dmsetup} exists (probably statically linked), and the 
ebuild writes dynamically linked versions in their place. If you want static 
versions, you must rename the two old files to lvm.static and dmsetup.static.

It is not a problem to have these binaries dynamically linked as

a. they are in /sbin and /lib which by convention are mandated to be on the 
same partition as / and therefore always available,
b. /usr/ is referenced nowhere. Witness:

nazgul ~ # ldd /sbin/lvm
        linux-vdso.so.1 =>  (0x00007ffffa3ff000)
        libdl.so.2 => /lib/libdl.so.2 (0x00007ff2c5aed000)
        libdevmapper-event.so.1.02 => /lib/libdevmapper-event.so.1.02 
(0x00007ff2c58e7000)
        libdevmapper.so.1.02 => /lib/libdevmapper.so.1.02 (0x00007ff2c56c1000)
        libreadline.so.6 => /lib/libreadline.so.6 (0x00007ff2c547c000)
        libm.so.6 => /lib/libm.so.6 (0x00007ff2c51f9000)
        libudev.so.0 => /lib/libudev.so.0 (0x00007ff2c4feb000)
        libc.so.6 => /lib/libc.so.6 (0x00007ff2c4c74000)
        /lib64/ld-linux-x86-64.so.2 (0x00007ff2c5cf1000)
        libncurses.so.5 => /lib/libncurses.so.5 (0x00007ff2c4a23000)
nazgul ~ # ldd /sbin/dmsetup 
        linux-vdso.so.1 =>  (0x00007fff925ff000)
        libdevmapper.so.1.02 => /lib/libdevmapper.so.1.02 (0x00007fb0e5a8d000)
        libudev.so.0 => /lib/libudev.so.0 (0x00007fb0e587f000)
        libc.so.6 => /lib/libc.so.6 (0x00007fb0e5508000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fb0e5cb3000)

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] How and whether to take action on elog message from sys-fs/lvm2-2.02.73

[felix]

On Fri, Aug 27, 2010 at 09:55:58AM -0700, Kevin O'Gorman wrote:

> Leaving that aside, the message does not state *which* filename to
> append ".static" to, and where to change it, so I'm baffled as to
> how to take action on this message, even if I thought it important
> to do.

Itis a confusing message, but I finally figured it out.

Try this:

    ls -l /sbin|grep lvm

You'll see that all lvm commands (vgscan etc) are symlinked to lvm.

You'll also see there's an "lvm.static" command.

So if you want to run one of the lvm commands in static mode, you
probably have to change its symlink to point to lvm.static instead of
lvm.

There may be other similar lvm commands, I do not know.  A similar ls
-l|grep for "static" shows other commands, but I do not think they are lvm.

That's all.  Simple once you see it :-)

-- 
            ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
     Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o