From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Upgrading from beta 6 to beta 7
Date: Wed, 9 May 2001 09:37:27 +0000 [thread overview]
Message-ID: <20010509093727.C4918@sistina.com> (raw)
In-Reply-To: <989275349.1722.5.camel@localhost>; from raheesom@navpoint.com on Mon, May 07, 2001 at 06:42:29PM -0400
As Luca already pointed out in his answer:
you need to start with a *clean* kernel and do a full compile/install run.
Regards,
Heinz -- The LVM Guy --
On Mon, May 07, 2001 at 06:42:29PM -0400, Rupert Heesom wrote:
> Guys:
>
> I've currently got lvm beta6 RPMs installed on my PC, although I only
> have test vols in place.
>
> I think I ought to upgrade to beta 7 since there are now RPMs available.
> My question is in regard to patching the kernel. I assume that I just
> run the beta 7 patch onto the source which had the beta 6 patch applied.
>
> When then compiling the source to get the updated LVM module, do I need
> to recompile the whole kernel & put that in place first as well as
> compiling & installing the modules, or do I just need to compile the
> modules, and install (make modules; make modules_install) ?
>
> --
> regs
> rupert
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2001-05-09 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 22:42 [linux-lvm] Upgrading from beta 6 to beta 7 Rupert Heesom
2001-05-09 9:37 ` Heinz J. Mauelshagen [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=20010509093727.C4918@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 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.