From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problems with 1.0
Date: Fri, 17 Aug 2001 11:00:43 +0200 [thread overview]
Message-ID: <20010817110043.A10370@sistina.com> (raw)
In-Reply-To: <BJEHIDHMNHMANMFJEKAPCEAGCAAA.tren@eotnetworks.com>; from tren@eotnetworks.com on Thu, Aug 16, 2001 at 10:55:35PM -0600
On Thu, Aug 16, 2001 at 10:55:35PM -0600, Tren Blackburn wrote:
> Hi List;
>
> I had installed the 1.0 driver into my 2.4.8 kernel, and rebooted.
> Everything came up fine, so I installed the user tools and forgot about
> them...until I had to reboot this evening...Now the LVM tools are
> dynamically linked (Looking for libgcc_s.so.1)? Or so it seems. I am no
> a C programmer and don't fully understand how linking works, but it seems
> to me that the beta 8 tools were statically linked as they didn't need any
> external libraries, but the 1.0 user tools are dynamically linked.
>
> Now this probably doesn't seem like a problem, but when your libraries are
> mounted on a LVM volume and you have no tools to activate your volume
> with...well...you can probably guess =) Luckilly I had an identically
> configured machine that I hadn't upgraded to 1.0 yet (same gcc 3.0
> compiler, etc) so I just copied the tools across to the other machine
> (beta 8 tools) and all is fine again.
>
> If I am completely off base as to what is happening here, please correct
> me, and please also let me know how to solve this problem.
Tren,
that shouldn't be a problem because the default installation directory for
shared libraries is /lib which belongs to the root directory. LVM tools just
access any shread libraries from there unless you use the --libdir configure
option to chosse a different one.
If you are not able to mount the root filesystem (no matter on which block
device including a logical volume it sits) you are in trouble anyway ;-)
>
> As always I appreciate all help this list gives.
>
> Regards,
>
> Tren.
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-08-17 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 4:55 [linux-lvm] Problems with 1.0 Tren Blackburn
2001-08-17 9:00 ` Heinz J . Mauelshagen [this message]
2001-08-17 9:58 ` Patrick Caulfield
-- strict thread matches above, loose matches on Subject: below --
2001-08-17 14:28 Tren Blackburn
2001-08-21 8:24 ` Jan Schreckenbach
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=20010817110043.A10370@sistina.com \
--to=mauelshagen@sistina.com \
--cc=linux-lvm@sistina.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