All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Tomlinson <tomlins@cam.org>
To: linux-kernel@vger.kernel.org
Cc: linux-openlvm@nl.linux.org, linux-lvm@sistina.com,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: [linux-lvm] [BUG] lvm beta7 and ac11 problems
Date: Sat, 21 Apr 2001 10:00:22 -0400	[thread overview]
Message-ID: <01042110002200.00707@oscar> (raw)

Hi,

building a kernel with 2.4.3-ac11 and lvm beta7 + vfs_locking_patch-2.4.2 yields:

oscar# depmod -ae 2.4.3-ac11 
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac11/kernel/drivers/md/lvm-mod.o
depmod:         get_hardblocksize

ideas?

Ed Tomlinson

WARNING: multiple messages have this Message-ID (diff)
From: Ed Tomlinson <tomlins@cam.org>
To: linux-kernel@vger.kernel.org
Cc: linux-openlvm@nl.linux.org, linux-lvm@sistina.com,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: [BUG] lvm beta7 and ac11 problems
Date: Sat, 21 Apr 2001 10:00:22 -0400	[thread overview]
Message-ID: <01042110002200.00707@oscar> (raw)

Hi,

building a kernel with 2.4.3-ac11 and lvm beta7 + vfs_locking_patch-2.4.2 yields:

oscar# depmod -ae 2.4.3-ac11 
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac11/kernel/drivers/md/lvm-mod.o
depmod:         get_hardblocksize

ideas?

Ed Tomlinson

             reply	other threads:[~2001-04-21 14:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-21 14:00 Ed Tomlinson [this message]
2001-04-21 14:00 ` [BUG] lvm beta7 and ac11 problems Ed Tomlinson
2001-04-21 14:20 ` [linux-lvm] " Jens Axboe
2001-04-21 14:20   ` Jens Axboe
2001-04-23  8:51   ` [linux-lvm] " Martin Dalecki
2001-04-23  8:51     ` Martin Dalecki
2001-04-23 13:16     ` [linux-lvm] " Jeff Chua
2001-04-23 13:16       ` Jeff Chua
2001-04-23 13:18       ` [linux-lvm] " Martin Dalecki
2001-04-23 13:18         ` Martin Dalecki
2001-04-21 15:33 ` [linux-lvm] " Alan Cox
2001-04-21 15:33   ` Alan Cox

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=01042110002200.00707@oscar \
    --to=tomlins@cam.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-lvm@sistina.com \
    --cc=linux-openlvm@nl.linux.org \
    /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.