From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Patching Linus' pre- kernels?
Date: Mon, 28 May 2001 11:22:24 +0000 [thread overview]
Message-ID: <20010528112224.I26710@sistina.com> (raw)
In-Reply-To: <20010525162619.D24299@carfax>; from hugo@carfax.org.uk on Fri, May 25, 2001 at 04:26:19PM +0100
Hugo,
there's 2 optional solutions:
- change get_hardblocksize to get_hardsect_size and recompile -or-
- get the recent LVM code from CVS at www.sistina.com
Regards,
Heinz -- The LVM Guy --
On Fri, May 25, 2001 at 04:26:19PM +0100, Hugo Mills wrote:
> Hi -
>
> I've just tried to patch a recent, but otherwise virgin, Linus
> kernel, and had the kernel compile fail:
>
> make[2]: Leaving directory `/usr/src/linux-2.4.5-pre3/arch/i386/lib'
> ld -m elf_i386 -T /usr/src/linux-2.4.5-pre3/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o \
> --start-group \
> arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \
> drivers/block/block.o drivers/char/char.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/parport/driver.o drivers/char/agp/agp.o drivers/char/drm/drm.o drivers/ide/idedriver.o drivers/scsi/scsidrv.o drivers/cdrom/driver.o drivers/pci/driver.o drivers/video/video.o drivers/md/mddev.o \
> net/network.o \
> /usr/src/linux-2.4.5-pre3/arch/i386/lib/lib.a /usr/src/linux-2.4.5-pre3/lib/lib.a /usr/src/linux-2.4.5-pre3/arch/i386/lib/lib.a \
> --end-group \
> -o vmlinux
> drivers/md/mddev.o: In function `__update_hardblocksize':
> drivers/md/mddev.o(.text+0x22f1): undefined reference to `get_hardblocksize'
> drivers/md/mddev.o(.text+0x2332): undefined reference to `get_hardblocksize'
> make[1]: *** [vmlinux] Error 1
> make[1]: Leaving directory `/usr/src/linux-2.4.5-pre3'
> make: *** [stamp-build] Error 2
>
> I'm using:
> Debian testing
> Kernel 2.4.5-pre3
> LVM 0.9.1-beta7
>
> Is the beta7 LVM expected to patch against Linus' pre- kernels? If
> it is, what have I done wrong? If not, which kernels should I be able
> to patch against?
>
> Also, are there any potential problems with running LVM and devfs
> together?
>
> Thanks,
> Hugo.
>
> --
> ---- Hugo Mills --- The Creature from the Black Logon ----
> hugo@lug.org.uk hugo@carfax.nildram.co.uk hugo@soton.ac.uk
> ---- "We did a risk management review. We concluded ----
> that there was no risk of any management."
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
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-05-28 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-25 15:26 [linux-lvm] Patching Linus' pre- kernels? Hugo Mills
2001-05-28 11:22 ` Heinz J. Mauelshagen [this message]
2001-05-28 13:40 ` hugo
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=20010528112224.I26710@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.