From: Rupert Heesom <raheesom@navpoint.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Patching my kernel.
Date: 10 May 2001 18:48:44 -0400 [thread overview]
Message-ID: <989534925.7891.0.camel@localhost> (raw)
In-Reply-To: <20010509195843.A1351@66bassett.freeserve.co.uk>
Well, Joe:
It worked this time. As I write this, the kernel is compiling itself
after the patch install.
I think I know what went wrong last time......I'd just finished
discussing with someone how to retain the kernel config settings from
the previously used source tree. What I did last time was to copy the
old .config file into /usr/src/linux. Do the "make oldconfig" command,
THEN do the patch install.
Obviously from what I've seen now, I need to to the patch install before
the "make oldconfig". I should have mentioned it in my post to you,
but I probably didn't think of it!
On 09 May 2001 19:58:43 +0100, Joe Thornber wrote:
> On Wed, May 09, 2001 at 07:43:14AM -0400, Rupert Heesom wrote:
>
> hmmmm... not sure what you've done here. It looks like the patch
> generation has gone astray. My advice is to start with a fresh LVM dir:
>
> untar clean kernel
> untar LVM_beta7
> cd LVM
> ./configure
> cd PATCHES
> make
> cd /usr/src/linux
> patch -p1 < <where ever>/LVM/PATCHES/lvm-0.9.1_beta7-2.4.3.patch
>
> If this doesn't work please send me (off list) the LVM patch so I can
> see what has gone wrong.
>
> Also please be aware that beta7 needs an extra little patch to fix the
> get_hardblocksize -> hardsectsize name change. Search this mailing
> list for it, or grab code from CVS.
I forgot about this.... but looking at the msgs regarding what you
mentioned here, looks like it's s/390 code, so not something that will
affect my intel processor.
>
> > What a learning curve!! What next?
>
> Please persevere, it gets easy once you've done it a couple of times.
Yes, I didn't mean that to come across sharply. I *ALWAYS* persevere!
When I first started with Linux, it took me 2 WEEKS to get diald working
on my PC so that I could use the internet the way I wanted (2 days
because of a pw typed into the config file wrong!).
--
regs
rupert
next prev parent reply other threads:[~2001-05-10 22:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 23:11 [linux-lvm] Patching my kernel Rupert Heesom
2001-05-09 6:51 ` Luca Berra
2001-05-09 8:29 ` Joe Thornber
2001-05-09 10:39 ` Rupert Heesom
2001-05-09 14:43 ` Patrick Caulfield
2001-05-09 15:03 ` Joe Thornber
2001-05-09 11:43 ` Rupert Heesom
2001-05-09 18:58 ` Joe Thornber
2001-05-10 22:48 ` Rupert Heesom [this message]
2001-05-09 11:55 ` David Vidal Rodriguez
2001-05-09 13:11 ` Joe Thornber
2001-05-09 14:21 ` David Vidal Rodriguez
2001-05-09 17:29 ` Luca Berra
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=989534925.7891.0.camel@localhost \
--to=raheesom@navpoint.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